Unnamed: 0 int64 0 832k | id float64 2.49B 32.1B | type stringclasses 1 value | created_at stringlengths 19 19 | repo stringlengths 5 112 | repo_url stringlengths 34 141 | action stringclasses 3 values | title stringlengths 1 757 | labels stringlengths 4 664 | body stringlengths 3 261k | index stringclasses 10 values | text_combine stringlengths 96 261k | label stringclasses 2 values | text stringlengths 96 232k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
744,352 | 25,939,823,323 | IssuesEvent | 2022-12-16 17:14:55 | brave/brave-browser | https://api.github.com/repos/brave/brave-browser | closed | [Android] Rewards settings `brave://rewards` page blank (v1.39.x and higher) | bug feature/rewards priority/P2 intermittent-issue regression OS/Android | ## Description
https://community.brave.com/t/blank-page-in-brave-rewards/406301/3
This was fixed in the past here: https://github.com/brave/brave-browser/issues/21649 But it looks like the issue may be back. | 1.0 | [Android] Rewards settings `brave://rewards` page blank (v1.39.x and higher) - ## Description
https://community.brave.com/t/blank-page-in-brave-rewards/406301/3
This was fixed in the past here: https://github.com/brave/brave-browser/issues/21649 But it looks like the issue may be back. | non_defect | rewards settings brave rewards page blank x and higher description this was fixed in the past here but it looks like the issue may be back | 0 |
278,465 | 21,081,600,761 | IssuesEvent | 2022-04-03 01:06:01 | tonyketcham/p5-svelte | https://api.github.com/repos/tonyketcham/p5-svelte | closed | Docs site shows incorrect import statement in examples | bug documentation | **Describe the bug**
In doc site examples (see [Vectors](https://p5-svelte.netlify.app/examples/vectors), etc.) the P5 component import statement is the relative path to where `P5.svelte` lives inside the repo rather than the user-facing import path of `p5-svelte`.
**Currently**
```ts
import P5 from "$lib/P5.svelte";
```
**Should change to**
```ts
import P5 from "p5-svelte";
``` | 1.0 | Docs site shows incorrect import statement in examples - **Describe the bug**
In doc site examples (see [Vectors](https://p5-svelte.netlify.app/examples/vectors), etc.) the P5 component import statement is the relative path to where `P5.svelte` lives inside the repo rather than the user-facing import path of `p5-svelte`.
**Currently**
```ts
import P5 from "$lib/P5.svelte";
```
**Should change to**
```ts
import P5 from "p5-svelte";
``` | non_defect | docs site shows incorrect import statement in examples describe the bug in doc site examples see etc the component import statement is the relative path to where svelte lives inside the repo rather than the user facing import path of svelte currently ts import from lib svelte should change to ts import from svelte | 0 |
94,067 | 8,468,428,348 | IssuesEvent | 2018-10-23 19:43:12 | ktraunmueller/Compositor | https://api.github.com/repos/ktraunmueller/Compositor | closed | Deleting line in \author command may leave line break | automated test bug | _Note: the following steps require that issue #301 is already fixed; the issue will not be reproducible in this way with e.g. 1.5.3._
Select a line in the author scope:
<img width="281" alt="screen shot 2018-10-22 at 23 12 44" src="https://user-images.githubusercontent.com/650763/47319853-1605b280-d650-11e8-8fe6-614f32c6d023.png">
Hit delete (backwards):
<img width="251" alt="screen shot 2018-10-22 at 23 14 10" src="https://user-images.githubusercontent.com/650763/47319938-49484180-d650-11e8-88d0-2ebf6e38a826.png">
This will leave a trailing line break in the `\author` command
<img width="212" alt="screen shot 2018-10-22 at 23 14 32" src="https://user-images.githubusercontent.com/650763/47319971-61b85c00-d650-11e8-8d57-75c8764358c1.png">
After unfocusing and focusing the author scope, the end-of-paragraph marker will no longer be shown:
<img width="273" alt="screen shot 2018-10-22 at 23 17 24" src="https://user-images.githubusercontent.com/650763/47320069-ab08ab80-d650-11e8-840a-f5d3922cedfd.png"> | 1.0 | Deleting line in \author command may leave line break - _Note: the following steps require that issue #301 is already fixed; the issue will not be reproducible in this way with e.g. 1.5.3._
Select a line in the author scope:
<img width="281" alt="screen shot 2018-10-22 at 23 12 44" src="https://user-images.githubusercontent.com/650763/47319853-1605b280-d650-11e8-8fe6-614f32c6d023.png">
Hit delete (backwards):
<img width="251" alt="screen shot 2018-10-22 at 23 14 10" src="https://user-images.githubusercontent.com/650763/47319938-49484180-d650-11e8-88d0-2ebf6e38a826.png">
This will leave a trailing line break in the `\author` command
<img width="212" alt="screen shot 2018-10-22 at 23 14 32" src="https://user-images.githubusercontent.com/650763/47319971-61b85c00-d650-11e8-8d57-75c8764358c1.png">
After unfocusing and focusing the author scope, the end-of-paragraph marker will no longer be shown:
<img width="273" alt="screen shot 2018-10-22 at 23 17 24" src="https://user-images.githubusercontent.com/650763/47320069-ab08ab80-d650-11e8-840a-f5d3922cedfd.png"> | non_defect | deleting line in author command may leave line break note the following steps require that issue is already fixed the issue will not be reproducible in this way with e g select a line in the author scope img width alt screen shot at src hit delete backwards img width alt screen shot at src this will leave a trailing line break in the author command img width alt screen shot at src after unfocusing and focusing the author scope the end of paragraph marker will no longer be shown img width alt screen shot at src | 0 |
7,379 | 2,610,365,876 | IssuesEvent | 2015-02-26 19:58:12 | chrsmith/scribefire-chrome | https://api.github.com/repos/chrsmith/scribefire-chrome | closed | Can't add blog | auto-migrated Priority-Medium Type-Defect | ```
What's the problem?
I am unable to add my blog to Scribefire. I had it installed on an older
MacBook Pro and when I migrated to this one, the Scribefire came across but not
the blog. I add the blog via the form and it reports success but the blog
isn't added.
What browser are you using?
Google Chrome.
What version of ScribeFire are you running?
4.1. Just downloaded it from Google.
```
-----
Original issue reported on code.google.com by `dlpeters...@gmail.com` on 15 Feb 2013 at 5:30 | 1.0 | Can't add blog - ```
What's the problem?
I am unable to add my blog to Scribefire. I had it installed on an older
MacBook Pro and when I migrated to this one, the Scribefire came across but not
the blog. I add the blog via the form and it reports success but the blog
isn't added.
What browser are you using?
Google Chrome.
What version of ScribeFire are you running?
4.1. Just downloaded it from Google.
```
-----
Original issue reported on code.google.com by `dlpeters...@gmail.com` on 15 Feb 2013 at 5:30 | defect | can t add blog what s the problem i am unable to add my blog to scribefire i had it installed on an older macbook pro and when i migrated to this one the scribefire came across but not the blog i add the blog via the form and it reports success but the blog isn t added what browser are you using google chrome what version of scribefire are you running just downloaded it from google original issue reported on code google com by dlpeters gmail com on feb at | 1 |
11,164 | 13,957,694,143 | IssuesEvent | 2020-10-24 08:11:10 | alexanderkotsev/geoportal | https://api.github.com/repos/alexanderkotsev/geoportal | opened | DK: Missing resources in Geoportal | DK - Denmark Geoportal Harvesting process | Collected from the Geoportal Workshop online survey answers:
A harvesting was done from our national catalogue Friday 10th of Dec. First, we were surprised to see that
the number of downloadable data set had decreased. However, after a closer look at our data set atom feed
we noticed that there was no value in "length" in each entry in the data set feeds. The Geoportal Browser
reported that data has no "DATA_DOWNLOAD_LINK_IS_AVAILABLE". We have so far concluded that this
single information "length" in the data set atom feed has a vital meaning in the Geoportal. Can you confirm
that our conclusion is correct? In addition, if that is correct we think the chances for a successful harvesting
is depending too much on a single tag/information deep down in data set atom feed. | 1.0 | DK: Missing resources in Geoportal - Collected from the Geoportal Workshop online survey answers:
A harvesting was done from our national catalogue Friday 10th of Dec. First, we were surprised to see that
the number of downloadable data set had decreased. However, after a closer look at our data set atom feed
we noticed that there was no value in "length" in each entry in the data set feeds. The Geoportal Browser
reported that data has no "DATA_DOWNLOAD_LINK_IS_AVAILABLE". We have so far concluded that this
single information "length" in the data set atom feed has a vital meaning in the Geoportal. Can you confirm
that our conclusion is correct? In addition, if that is correct we think the chances for a successful harvesting
is depending too much on a single tag/information deep down in data set atom feed. | non_defect | dk missing resources in geoportal collected from the geoportal workshop online survey answers a harvesting was done from our national catalogue friday of dec first we were surprised to see that the number of downloadable data set had decreased however after a closer look at our data set atom feed we noticed that there was no value in quot length quot in each entry in the data set feeds the geoportal browser reported that data has no quot data download link is available quot we have so far concluded that this single information quot length quot in the data set atom feed has a vital meaning in the geoportal can you confirm that our conclusion is correct in addition if that is correct we think the chances for a successful harvesting is depending too much on a single tag information deep down in data set atom feed | 0 |
1,592 | 6,420,520,914 | IssuesEvent | 2017-08-09 00:29:17 | City-Bureau/documenters-aggregator | https://api.github.com/repos/City-Bureau/documenters-aggregator | opened | how to handle events that require registration? | architecture: spiders priority: high (must have) support: conversation | @mwgalloway raised this issue. @diaholliday might have some thoughts about how to structure this as the open civic data specification doesn't account for it | 1.0 | how to handle events that require registration? - @mwgalloway raised this issue. @diaholliday might have some thoughts about how to structure this as the open civic data specification doesn't account for it | non_defect | how to handle events that require registration mwgalloway raised this issue diaholliday might have some thoughts about how to structure this as the open civic data specification doesn t account for it | 0 |
288,189 | 21,689,849,562 | IssuesEvent | 2022-05-09 14:29:27 | Cavonstavant/PLAZAAAAAAAAAAAAAAAAAAAAAAA | https://api.github.com/repos/Cavonstavant/PLAZAAAAAAAAAAAAAAAAAAAAAAA | opened | Core - Create a "Fridge" | documentation enhancement | Create a Class / Enum / ... something where you can check the number of the ingredients left | 1.0 | Core - Create a "Fridge" - Create a Class / Enum / ... something where you can check the number of the ingredients left | non_defect | core create a fridge create a class enum something where you can check the number of the ingredients left | 0 |
51,515 | 13,207,506,395 | IssuesEvent | 2020-08-14 23:22:10 | icecube-trac/tix4 | https://api.github.com/repos/icecube-trac/tix4 | opened | icetray parameter tests failing on python 2.3.4 (Trac #560) | IceTray Incomplete Migration Migrated from Trac defect | <details>
<summary><em>Migrated from <a href="https://code.icecube.wisc.edu/projects/icecube/ticket/560">https://code.icecube.wisc.edu/projects/icecube/ticket/560</a>, reported by blaufussand owned by troy</em></summary>
<p>
```json
{
"status": "closed",
"changetime": "2014-11-23T03:37:56",
"_ts": "1416713876862109",
"description": "This maybe intentional/unavoidable:\n\nicetray/scripts/parameter_abuse.py\nfailing on el4 machines:\n\n[slave@akuma build_debug]$ ./icetray/resources/scripts/parameter_abuse.py \nLogging configured from file ./log4cplus.conf\n/build/slave_build/manual/offline-software/src/icetray/public/icetray/I3Module.h:330: ERROR: Error in AllParametersModule module 'apm2', getting parameter 'intvec_param'\nOK, threw as expected\nTraceback (most recent call last):\n File \"./icetray/resources/scripts/parameter_abuse.py\", line 34, in ?\n exit(0)\nTypeError: 'str' object is not callable\n",
"reporter": "blaufuss",
"cc": "",
"resolution": "fixed",
"time": "2009-06-12T20:37:59",
"component": "IceTray",
"summary": "icetray parameter tests failing on python 2.3.4",
"priority": "normal",
"keywords": "",
"milestone": "",
"owner": "troy",
"type": "defect"
}
```
</p>
</details>
| 1.0 | icetray parameter tests failing on python 2.3.4 (Trac #560) - <details>
<summary><em>Migrated from <a href="https://code.icecube.wisc.edu/projects/icecube/ticket/560">https://code.icecube.wisc.edu/projects/icecube/ticket/560</a>, reported by blaufussand owned by troy</em></summary>
<p>
```json
{
"status": "closed",
"changetime": "2014-11-23T03:37:56",
"_ts": "1416713876862109",
"description": "This maybe intentional/unavoidable:\n\nicetray/scripts/parameter_abuse.py\nfailing on el4 machines:\n\n[slave@akuma build_debug]$ ./icetray/resources/scripts/parameter_abuse.py \nLogging configured from file ./log4cplus.conf\n/build/slave_build/manual/offline-software/src/icetray/public/icetray/I3Module.h:330: ERROR: Error in AllParametersModule module 'apm2', getting parameter 'intvec_param'\nOK, threw as expected\nTraceback (most recent call last):\n File \"./icetray/resources/scripts/parameter_abuse.py\", line 34, in ?\n exit(0)\nTypeError: 'str' object is not callable\n",
"reporter": "blaufuss",
"cc": "",
"resolution": "fixed",
"time": "2009-06-12T20:37:59",
"component": "IceTray",
"summary": "icetray parameter tests failing on python 2.3.4",
"priority": "normal",
"keywords": "",
"milestone": "",
"owner": "troy",
"type": "defect"
}
```
</p>
</details>
| defect | icetray parameter tests failing on python trac migrated from json status closed changetime ts description this maybe intentional unavoidable n nicetray scripts parameter abuse py nfailing on machines n n icetray resources scripts parameter abuse py nlogging configured from file conf n build slave build manual offline software src icetray public icetray h error error in allparametersmodule module getting parameter intvec param nok threw as expected ntraceback most recent call last n file icetray resources scripts parameter abuse py line in n exit ntypeerror str object is not callable n reporter blaufuss cc resolution fixed time component icetray summary icetray parameter tests failing on python priority normal keywords milestone owner troy type defect | 1 |
76,639 | 26,526,248,152 | IssuesEvent | 2023-01-19 08:59:06 | zed-industries/feedback | https://api.github.com/repos/zed-industries/feedback | opened | lsp installation shouldn't respect local npm config | defect triage | ### Check for existing issues
- [X] Completed
### Describe the bug / provide steps to reproduce it
So, I'm on latest Zed version, but typescript/json LSP doesn't work. Check around and I find out that my LSP version is `typescript-4.9.4/server-2.2.0` while the latest is `typescript-4.9.4/server-3.0.2` (figured out from another issue). I tried delete this directory and Zed keeps downloading the old version. Turned out because of my local npm config has `prefer-offline=true` and Zed doesn't check for an update.
### Environment
```
Zed: 0.69.2 (stable)
OS: macOS 13.2.0
Memory: 32 GiB
Architecture: aarch64
```
### If applicable, add mockups / screenshots to help explain present your vision of the feature
_No response_
### If applicable, attach your `~/Library/Logs/Zed/Zed.log` file to this issue.
If you only need the most recent lines, you can run the `zed: open log` command palette action to see the last 1000.
```
08:36:35 [INFO] ========== starting zed ==========
08:36:35 [INFO] set environment variables from shell:/opt/homebrew/bin/fish, path:/Users/t/.bun/bin:/Users/t/.local/share/nvm/v18.13.0/bin:/Users/t/.cargo/bin:/Users/t/.local/share/pnpm-global/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin
08:36:35 [INFO] Opening main db
08:36:35 [INFO] Opening main db
08:36:35 [INFO] open paths ["/Users/t/Desktop/playground"]
08:36:35 [INFO] Opening main db
08:36:37 [ERROR] Os { code: 20, kind: NotADirectory, message: "Not a directory" }
08:36:37 [ERROR] No such file or directory (os error 2)
``` | 1.0 | lsp installation shouldn't respect local npm config - ### Check for existing issues
- [X] Completed
### Describe the bug / provide steps to reproduce it
So, I'm on latest Zed version, but typescript/json LSP doesn't work. Check around and I find out that my LSP version is `typescript-4.9.4/server-2.2.0` while the latest is `typescript-4.9.4/server-3.0.2` (figured out from another issue). I tried delete this directory and Zed keeps downloading the old version. Turned out because of my local npm config has `prefer-offline=true` and Zed doesn't check for an update.
### Environment
```
Zed: 0.69.2 (stable)
OS: macOS 13.2.0
Memory: 32 GiB
Architecture: aarch64
```
### If applicable, add mockups / screenshots to help explain present your vision of the feature
_No response_
### If applicable, attach your `~/Library/Logs/Zed/Zed.log` file to this issue.
If you only need the most recent lines, you can run the `zed: open log` command palette action to see the last 1000.
```
08:36:35 [INFO] ========== starting zed ==========
08:36:35 [INFO] set environment variables from shell:/opt/homebrew/bin/fish, path:/Users/t/.bun/bin:/Users/t/.local/share/nvm/v18.13.0/bin:/Users/t/.cargo/bin:/Users/t/.local/share/pnpm-global/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin
08:36:35 [INFO] Opening main db
08:36:35 [INFO] Opening main db
08:36:35 [INFO] open paths ["/Users/t/Desktop/playground"]
08:36:35 [INFO] Opening main db
08:36:37 [ERROR] Os { code: 20, kind: NotADirectory, message: "Not a directory" }
08:36:37 [ERROR] No such file or directory (os error 2)
``` | defect | lsp installation shouldn t respect local npm config check for existing issues completed describe the bug provide steps to reproduce it so i m on latest zed version but typescript json lsp doesn t work check around and i find out that my lsp version is typescript server while the latest is typescript server figured out from another issue i tried delete this directory and zed keeps downloading the old version turned out because of my local npm config has prefer offline true and zed doesn t check for an update environment zed stable os macos memory gib architecture if applicable add mockups screenshots to help explain present your vision of the feature no response if applicable attach your library logs zed zed log file to this issue if you only need the most recent lines you can run the zed open log command palette action to see the last starting zed set environment variables from shell opt homebrew bin fish path users t bun bin users t local share nvm bin users t cargo bin users t local share pnpm global bin opt homebrew bin opt homebrew sbin usr local bin usr bin bin usr sbin sbin library apple usr bin opening main db opening main db open paths opening main db os code kind notadirectory message not a directory no such file or directory os error | 1 |
68,174 | 21,529,026,736 | IssuesEvent | 2022-04-28 21:44:14 | vector-im/element-web | https://api.github.com/repos/vector-im/element-web | closed | status.im mxids for Matthew & Amandine are higher in the matrix.org user dir results than for matrix.org | T-Defect P1 S-Major Z-Synapse | This seems very strange; surely the matrix.org MXIDs should be weighted higher as we are in 100x times more rooms with them than with our status.im IDs... | 1.0 | status.im mxids for Matthew & Amandine are higher in the matrix.org user dir results than for matrix.org - This seems very strange; surely the matrix.org MXIDs should be weighted higher as we are in 100x times more rooms with them than with our status.im IDs... | defect | status im mxids for matthew amandine are higher in the matrix org user dir results than for matrix org this seems very strange surely the matrix org mxids should be weighted higher as we are in times more rooms with them than with our status im ids | 1 |
214,106 | 7,266,773,032 | IssuesEvent | 2018-02-20 00:10:54 | MattyAyOh/NimbusPOS | https://api.github.com/repos/MattyAyOh/NimbusPOS | closed | Make the time control more touch-friendly | frontend high priority | Currently the control is not possible to set a time with a touch-screen, as it must be typed
You can press the "Start" "Stop" buttons to set the current time in, but sometimes they will need to manually input a time
| 1.0 | Make the time control more touch-friendly - Currently the control is not possible to set a time with a touch-screen, as it must be typed
You can press the "Start" "Stop" buttons to set the current time in, but sometimes they will need to manually input a time
| non_defect | make the time control more touch friendly currently the control is not possible to set a time with a touch screen as it must be typed you can press the start stop buttons to set the current time in but sometimes they will need to manually input a time | 0 |
15,565 | 5,145,321,811 | IssuesEvent | 2017-01-12 21:14:22 | ihmcrobotics/ihmc-open-robotics-software | https://api.github.com/repos/ihmcrobotics/ihmc-open-robotics-software | closed | SDFLoader project is cleaned up | code-cleanup Epic user-story | We should create another project (e.g. IHMCRobotModels) that contains all of the non-SDF stuff such as the various FullRobotModel implementations, so that the SDFLoader doesn't have to do a bunch of kinematics/screw tools operations.
| 1.0 | SDFLoader project is cleaned up - We should create another project (e.g. IHMCRobotModels) that contains all of the non-SDF stuff such as the various FullRobotModel implementations, so that the SDFLoader doesn't have to do a bunch of kinematics/screw tools operations.
| non_defect | sdfloader project is cleaned up we should create another project e g ihmcrobotmodels that contains all of the non sdf stuff such as the various fullrobotmodel implementations so that the sdfloader doesn t have to do a bunch of kinematics screw tools operations | 0 |
59,743 | 17,023,226,968 | IssuesEvent | 2021-07-03 00:57:08 | tomhughes/trac-tickets | https://api.github.com/repos/tomhughes/trac-tickets | closed | http://trac.openstreetmap.org/report/7 doesn't work in this Trac | Component: admin Priority: minor Resolution: worksforme Type: defect | **[Submitted to the original trac issue database at 11.24pm, Tuesday, 25th March 2008]**
http://trac.openstreetmap.org/report/7 (My Tickets) doesn't work on this Trac installation. I get
```
{7} My Tickets
This report demonstrates the use of the automatically set $USER dynamic variable, replaced with the username of the logged in user when executed.
No matches found.
```
| 1.0 | http://trac.openstreetmap.org/report/7 doesn't work in this Trac - **[Submitted to the original trac issue database at 11.24pm, Tuesday, 25th March 2008]**
http://trac.openstreetmap.org/report/7 (My Tickets) doesn't work on this Trac installation. I get
```
{7} My Tickets
This report demonstrates the use of the automatically set $USER dynamic variable, replaced with the username of the logged in user when executed.
No matches found.
```
| defect | doesn t work in this trac my tickets doesn t work on this trac installation i get my tickets this report demonstrates the use of the automatically set user dynamic variable replaced with the username of the logged in user when executed no matches found | 1 |
9,555 | 2,615,162,328 | IssuesEvent | 2015-03-01 06:41:40 | chrsmith/reaver-wps | https://api.github.com/repos/chrsmith/reaver-wps | opened | 15 characters PIN ? | auto-migrated Priority-Triage Type-Defect | ```
What version of Reaver are you using? (Only defects against the latest version
will be considered.)
Use Latest version
1. What operating system are you using (Linux is the only supported OS)?
Backtrack 5 R2 KDE
2. Is your wireless card in monitor mode (yes/no)?
Yes
3. What is the signal strength of the Access Point you are trying to crack?
-20/-30 at the router
4. What is the manufacturer and model # of the device you are trying to
crack?
mon0 Atheros AR9287 ath9k - [phy0]
wlan0 Atheros AR9287 ath9k - [phy0]
5. What is the entire command line string you are supplying to reaver?
reaver -i mon0 -b 00:24:17:73:DD:3D -vv
6. Please describe what you think the issue is.
STOP cracking on 90.90%
My suggestion
if start crack PIN then generate file wo have keys from 0000 to 9999 if all
tested then END on 90.90%,
i think all routers wo STOP on 90.90% don't have WPS "old" where use PINS
i look new WPS where to connect to the network you press the button on the
router
i capute Pcap file and look Serial number 15 characters, normal WPS routers
have 8 characters Serial numbers, i think Serial number in wireshark are Router
PIN
```
Original issue reported on code.google.com by `wiruspol...@gmail.com` on 1 May 2012 at 9:49 | 1.0 | 15 characters PIN ? - ```
What version of Reaver are you using? (Only defects against the latest version
will be considered.)
Use Latest version
1. What operating system are you using (Linux is the only supported OS)?
Backtrack 5 R2 KDE
2. Is your wireless card in monitor mode (yes/no)?
Yes
3. What is the signal strength of the Access Point you are trying to crack?
-20/-30 at the router
4. What is the manufacturer and model # of the device you are trying to
crack?
mon0 Atheros AR9287 ath9k - [phy0]
wlan0 Atheros AR9287 ath9k - [phy0]
5. What is the entire command line string you are supplying to reaver?
reaver -i mon0 -b 00:24:17:73:DD:3D -vv
6. Please describe what you think the issue is.
STOP cracking on 90.90%
My suggestion
if start crack PIN then generate file wo have keys from 0000 to 9999 if all
tested then END on 90.90%,
i think all routers wo STOP on 90.90% don't have WPS "old" where use PINS
i look new WPS where to connect to the network you press the button on the
router
i capute Pcap file and look Serial number 15 characters, normal WPS routers
have 8 characters Serial numbers, i think Serial number in wireshark are Router
PIN
```
Original issue reported on code.google.com by `wiruspol...@gmail.com` on 1 May 2012 at 9:49 | defect | characters pin what version of reaver are you using only defects against the latest version will be considered use latest version what operating system are you using linux is the only supported os backtrack kde is your wireless card in monitor mode yes no yes what is the signal strength of the access point you are trying to crack at the router what is the manufacturer and model of the device you are trying to crack atheros atheros what is the entire command line string you are supplying to reaver reaver i b dd vv please describe what you think the issue is stop cracking on my suggestion if start crack pin then generate file wo have keys from to if all tested then end on i think all routers wo stop on don t have wps old where use pins i look new wps where to connect to the network you press the button on the router i capute pcap file and look serial number characters normal wps routers have characters serial numbers i think serial number in wireshark are router pin original issue reported on code google com by wiruspol gmail com on may at | 1 |
221,354 | 17,334,731,599 | IssuesEvent | 2021-07-28 08:50:08 | mennaelkashef/eShop | https://api.github.com/repos/mennaelkashef/eShop | opened | No description entered by the user. | DOES-NOT-CONTAIN-STRING Hello! RULE-GOT-APPLIED Rule-works-on-convert-to-bug instabug test | # :clipboard: Bug Details
>No description entered by the user.
key | value
--|--
Reported At | 2021-07-28 08:49:46 UTC
Categories | Report a bug, Cat 2
Tags | test, Hello!, RULE-GOT-APPLIED, DOES-NOT-CONTAIN-STRING, Rule-works-on-convert-to-bug, instabug
App Version | 1.0-kotlin (1)
Session Duration | 9
Device | Google Android SDK built for x86, OS Level 24
Display | 1080x1920 (xhdpi)
Location | Giza, Egypt (en)
## :point_right: [View Full Bug Report on Instabug](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7958?utm_source=github&utm_medium=integrations) :point_left:
___
# :chart_with_downwards_trend: Session Profiler
Here is what the app was doing right before the bug was reported:
Key | Value
--|--
Used Memory | 30.0% - 0.44/1.48 GB
Used Storage | 4.5% - 0.26/5.81 GB
Connectivity | LTE - Android
Battery | 100% - plugged
Orientation | portrait
Find all the changes that happened in the parameters mentioned above during the last 60 seconds before the bug was reported here: :point_right: **[View Full Session Profiler](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7958?show-session-profiler=true&utm_source=github&utm_medium=integrations)** :point_left:
___
# :bust_in_silhouette: User Info
### User Attributes
```
key_name -2005597073: key value bla bla bla la
key_name -342890808: key value bla bla bla la
key_name -1610989224: key value bla bla bla la
```
___
# :mag_right: Logs
### User Steps
Here are the last 10 steps done by the user right before the bug was reported:
```
08:49:39 In activity com.example.app.main.MainActivity: fragment com.example.app.main.MainFragment was started.
08:49:39 In activity com.example.app.main.MainActivity: fragment com.example.app.main.MainFragment was resumed.
08:49:40 com.example.app.main.MainActivity was resumed.
08:49:40 com.example.app.splash.SplashActivity was stopped.
08:49:40 com.example.app.splash.SplashActivity was destroyed.
08:49:43 Tap in "Sdk version: 10..." of type "androidx.appcompat.widget.AppCompatTextView" in "com.example.app.main.MainActivity"
08:49:44 com.example.app.main.MainActivity was paused.
08:49:44 In activity com.example.app.main.MainActivity: fragment com.example.app.main.MainFragment was paused.
08:49:45 Tap in "androidx.constraintlayout.widget.ConstraintLayout" in "com.example.app.main.MainActivity"
08:49:46 Tap in "androidx.constraintlayout.widget.ConstraintLayout" in "com.example.app.main.MainActivity"
```
Find all the user steps done by the user throughout the session here: :point_right: **[View All User Steps](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7958?show-logs=user_steps&utm_source=github&utm_medium=integrations)** :point_left:
### Console Log
Here are the last 10 console logs logged right before the bug was reported:
```
08:49:54 D/EGL_emulation( 5332): eglMakeCurrent: 0x924f7060: ver 2 0 (tinfo 0x924db260)
08:49:54 D/EGL_emulation( 5332): eglMakeCurrent: 0x924f7060: ver 2 0 (tinfo 0x924db260)
08:49:54 I/IB-StringUtility( 5332): trimming string to 15
08:49:55 D/IB-BaseReportingPresenter( 5332): onEmailChanged set live bug with email:te
08:49:55 D/IB-BaseReportingPresenter( 5332): onEmailChanged set live bug with email:t
08:49:55 D/IB-BaseReportingPresenter( 5332): onEmailChanged set live bug with email:
08:49:56 D/IB-BaseReportingPresenter( 5332): checkUserEmailValid :
08:49:56 D/IB-BaseReportingPresenter( 5332): onEmailChanged set live bug with email:
08:49:56 D/IB-ActionsOrchestrator( 5332): runAction
08:49:56 D/IB-AttachmentsUtility( 5332): encryptAttachments
```
Find all the logged console logs throughout the session here: :point_right: **[View All Console Log](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7958?show-logs=console_log&utm_source=github&utm_medium=integrations)** :point_left:
___
# :camera: Images
[](https://d38gnqwzxziyyy.cloudfront.net/attachments/bugs/16379585/c01cb7fca708f9cd71ade48bcbd36fd1_original/22160652/bug_1627462184017_.jpg?Expires=4783135807&Signature=JYAhimG9V9R97WW5BYyx4GqQKr3wisbRzd8oW2c1HymD4PEYoEM8WrwCGDadmiJKbitZVFCs8IiXvd9P173z1NbOxV7Hk4RetZhZyYtTX0opic8S42IGs0WCZ47HsjK5rEwUELdgSOIEPBwLRa~leKC6QxLmKyqL9siP9WTGcIRqIDLwki15exW8xrYoKLju~Ai4XumVX1uTFSTU09mg4CtkgU5v6buWgtQYAQU7~baoR7qY6QHA31RH8l3cTnpFPHuDOw0FVqdAYzzpvheRioSgJnXvySxmudi3lutQOQdl8oEZ0hxD2p7T94JkIzB4a0McRiFyhNuVx7F6A3xnVg__&Key-Pair-Id=APKAIXAG65U6UUX7JAQQ)
___
# :warning: Looking for More Details?
1. **Network Log**: we are unable to capture your network requests automatically. If you are using HttpUrlConnection or Okhttp requests, [**check the details mentioned here**](https://docs.instabug.com/docs/android-logging?utm_source=github&utm_medium=integrations#section-network-logs).
2. **User Events**: start capturing custom User Events to send them along with each report. [**Find all the details in the docs**](https://docs.instabug.com/docs/android-logging?utm_source=github&utm_medium=integrations).
3. **Instabug Log**: start adding Instabug logs to see them right inside each report you receive. [**Find all the details in the docs**](https://docs.instabug.com/docs/android-logging?utm_source=github&utm_medium=integrations). | 1.0 | No description entered by the user. - # :clipboard: Bug Details
>No description entered by the user.
key | value
--|--
Reported At | 2021-07-28 08:49:46 UTC
Categories | Report a bug, Cat 2
Tags | test, Hello!, RULE-GOT-APPLIED, DOES-NOT-CONTAIN-STRING, Rule-works-on-convert-to-bug, instabug
App Version | 1.0-kotlin (1)
Session Duration | 9
Device | Google Android SDK built for x86, OS Level 24
Display | 1080x1920 (xhdpi)
Location | Giza, Egypt (en)
## :point_right: [View Full Bug Report on Instabug](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7958?utm_source=github&utm_medium=integrations) :point_left:
___
# :chart_with_downwards_trend: Session Profiler
Here is what the app was doing right before the bug was reported:
Key | Value
--|--
Used Memory | 30.0% - 0.44/1.48 GB
Used Storage | 4.5% - 0.26/5.81 GB
Connectivity | LTE - Android
Battery | 100% - plugged
Orientation | portrait
Find all the changes that happened in the parameters mentioned above during the last 60 seconds before the bug was reported here: :point_right: **[View Full Session Profiler](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7958?show-session-profiler=true&utm_source=github&utm_medium=integrations)** :point_left:
___
# :bust_in_silhouette: User Info
### User Attributes
```
key_name -2005597073: key value bla bla bla la
key_name -342890808: key value bla bla bla la
key_name -1610989224: key value bla bla bla la
```
___
# :mag_right: Logs
### User Steps
Here are the last 10 steps done by the user right before the bug was reported:
```
08:49:39 In activity com.example.app.main.MainActivity: fragment com.example.app.main.MainFragment was started.
08:49:39 In activity com.example.app.main.MainActivity: fragment com.example.app.main.MainFragment was resumed.
08:49:40 com.example.app.main.MainActivity was resumed.
08:49:40 com.example.app.splash.SplashActivity was stopped.
08:49:40 com.example.app.splash.SplashActivity was destroyed.
08:49:43 Tap in "Sdk version: 10..." of type "androidx.appcompat.widget.AppCompatTextView" in "com.example.app.main.MainActivity"
08:49:44 com.example.app.main.MainActivity was paused.
08:49:44 In activity com.example.app.main.MainActivity: fragment com.example.app.main.MainFragment was paused.
08:49:45 Tap in "androidx.constraintlayout.widget.ConstraintLayout" in "com.example.app.main.MainActivity"
08:49:46 Tap in "androidx.constraintlayout.widget.ConstraintLayout" in "com.example.app.main.MainActivity"
```
Find all the user steps done by the user throughout the session here: :point_right: **[View All User Steps](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7958?show-logs=user_steps&utm_source=github&utm_medium=integrations)** :point_left:
### Console Log
Here are the last 10 console logs logged right before the bug was reported:
```
08:49:54 D/EGL_emulation( 5332): eglMakeCurrent: 0x924f7060: ver 2 0 (tinfo 0x924db260)
08:49:54 D/EGL_emulation( 5332): eglMakeCurrent: 0x924f7060: ver 2 0 (tinfo 0x924db260)
08:49:54 I/IB-StringUtility( 5332): trimming string to 15
08:49:55 D/IB-BaseReportingPresenter( 5332): onEmailChanged set live bug with email:te
08:49:55 D/IB-BaseReportingPresenter( 5332): onEmailChanged set live bug with email:t
08:49:55 D/IB-BaseReportingPresenter( 5332): onEmailChanged set live bug with email:
08:49:56 D/IB-BaseReportingPresenter( 5332): checkUserEmailValid :
08:49:56 D/IB-BaseReportingPresenter( 5332): onEmailChanged set live bug with email:
08:49:56 D/IB-ActionsOrchestrator( 5332): runAction
08:49:56 D/IB-AttachmentsUtility( 5332): encryptAttachments
```
Find all the logged console logs throughout the session here: :point_right: **[View All Console Log](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7958?show-logs=console_log&utm_source=github&utm_medium=integrations)** :point_left:
___
# :camera: Images
[](https://d38gnqwzxziyyy.cloudfront.net/attachments/bugs/16379585/c01cb7fca708f9cd71ade48bcbd36fd1_original/22160652/bug_1627462184017_.jpg?Expires=4783135807&Signature=JYAhimG9V9R97WW5BYyx4GqQKr3wisbRzd8oW2c1HymD4PEYoEM8WrwCGDadmiJKbitZVFCs8IiXvd9P173z1NbOxV7Hk4RetZhZyYtTX0opic8S42IGs0WCZ47HsjK5rEwUELdgSOIEPBwLRa~leKC6QxLmKyqL9siP9WTGcIRqIDLwki15exW8xrYoKLju~Ai4XumVX1uTFSTU09mg4CtkgU5v6buWgtQYAQU7~baoR7qY6QHA31RH8l3cTnpFPHuDOw0FVqdAYzzpvheRioSgJnXvySxmudi3lutQOQdl8oEZ0hxD2p7T94JkIzB4a0McRiFyhNuVx7F6A3xnVg__&Key-Pair-Id=APKAIXAG65U6UUX7JAQQ)
___
# :warning: Looking for More Details?
1. **Network Log**: we are unable to capture your network requests automatically. If you are using HttpUrlConnection or Okhttp requests, [**check the details mentioned here**](https://docs.instabug.com/docs/android-logging?utm_source=github&utm_medium=integrations#section-network-logs).
2. **User Events**: start capturing custom User Events to send them along with each report. [**Find all the details in the docs**](https://docs.instabug.com/docs/android-logging?utm_source=github&utm_medium=integrations).
3. **Instabug Log**: start adding Instabug logs to see them right inside each report you receive. [**Find all the details in the docs**](https://docs.instabug.com/docs/android-logging?utm_source=github&utm_medium=integrations). | non_defect | no description entered by the user clipboard bug details no description entered by the user key value reported at utc categories report a bug cat tags test hello rule got applied does not contain string rule works on convert to bug instabug app version kotlin session duration device google android sdk built for os level display xhdpi location giza egypt en point right point left chart with downwards trend session profiler here is what the app was doing right before the bug was reported key value used memory gb used storage gb connectivity lte android battery plugged orientation portrait find all the changes that happened in the parameters mentioned above during the last seconds before the bug was reported here point right point left bust in silhouette user info user attributes key name key value bla bla bla la key name key value bla bla bla la key name key value bla bla bla la mag right logs user steps here are the last steps done by the user right before the bug was reported in activity com example app main mainactivity fragment com example app main mainfragment was started in activity com example app main mainactivity fragment com example app main mainfragment was resumed com example app main mainactivity was resumed com example app splash splashactivity was stopped com example app splash splashactivity was destroyed tap in sdk version of type androidx appcompat widget appcompattextview in com example app main mainactivity com example app main mainactivity was paused in activity com example app main mainactivity fragment com example app main mainfragment was paused tap in androidx constraintlayout widget constraintlayout in com example app main mainactivity tap in androidx constraintlayout widget constraintlayout in com example app main mainactivity find all the user steps done by the user throughout the session here point right point left console log here are the last console logs logged right before the bug was reported d egl emulation eglmakecurrent ver tinfo d egl emulation eglmakecurrent ver tinfo i ib stringutility trimming string to d ib basereportingpresenter onemailchanged set live bug with email te d ib basereportingpresenter onemailchanged set live bug with email t d ib basereportingpresenter onemailchanged set live bug with email d ib basereportingpresenter checkuseremailvalid d ib basereportingpresenter onemailchanged set live bug with email d ib actionsorchestrator runaction d ib attachmentsutility encryptattachments find all the logged console logs throughout the session here point right point left camera images warning looking for more details network log we are unable to capture your network requests automatically if you are using httpurlconnection or okhttp requests user events start capturing custom user events to send them along with each report instabug log start adding instabug logs to see them right inside each report you receive | 0 |
362,047 | 25,358,650,181 | IssuesEvent | 2022-11-20 16:39:14 | cdklabs/cdk-nag | https://api.github.com/repos/cdklabs/cdk-nag | opened | doc: Resolving Tokens when inspecting CDK stack | documentation needs-triage | ### Describe your issue?
I am inspecting stack objects in the following way.
```ts
// Add CDK NAG resource suppressions for Lambda Functions.
stack.node.findAll().forEach(item => {
if (!(item instanceof cdk.aws_lambda.Function)) {
return
}
const fn = item as cdk.aws_lambda.Function;
console.log(fn.runtime);
console.log(fn.functionName);
return
});
```
The output:
```
Runtime {
name: 'python3.9',
supportsInlineCode: true,
family: 2,
bundlingDockerImage: DockerImage {
image: 'public.ecr.aws/sam/build-python3.9',
_imageHash: undefined
},
bundlingImage: DockerImage {
image: 'public.ecr.aws/sam/build-python3.9',
_imageHash: undefined
},
supportsCodeGuruProfiling: true
}
${Token[TOKEN.987]}
```
What is the way to resolve the name behind `${Token[TOKEN.987]}`? | 1.0 | doc: Resolving Tokens when inspecting CDK stack - ### Describe your issue?
I am inspecting stack objects in the following way.
```ts
// Add CDK NAG resource suppressions for Lambda Functions.
stack.node.findAll().forEach(item => {
if (!(item instanceof cdk.aws_lambda.Function)) {
return
}
const fn = item as cdk.aws_lambda.Function;
console.log(fn.runtime);
console.log(fn.functionName);
return
});
```
The output:
```
Runtime {
name: 'python3.9',
supportsInlineCode: true,
family: 2,
bundlingDockerImage: DockerImage {
image: 'public.ecr.aws/sam/build-python3.9',
_imageHash: undefined
},
bundlingImage: DockerImage {
image: 'public.ecr.aws/sam/build-python3.9',
_imageHash: undefined
},
supportsCodeGuruProfiling: true
}
${Token[TOKEN.987]}
```
What is the way to resolve the name behind `${Token[TOKEN.987]}`? | non_defect | doc resolving tokens when inspecting cdk stack describe your issue i am inspecting stack objects in the following way ts add cdk nag resource suppressions for lambda functions stack node findall foreach item if item instanceof cdk aws lambda function return const fn item as cdk aws lambda function console log fn runtime console log fn functionname return the output runtime name supportsinlinecode true family bundlingdockerimage dockerimage image public ecr aws sam build imagehash undefined bundlingimage dockerimage image public ecr aws sam build imagehash undefined supportscodeguruprofiling true token what is the way to resolve the name behind token | 0 |
248,471 | 7,931,573,468 | IssuesEvent | 2018-07-07 01:49:42 | brave/browser-laptop | https://api.github.com/repos/brave/browser-laptop | closed | Cookies are not persisted across restart | bug feature/cookies priority/P2 regression regression-range-wanted | ### Description
On a fresh profile, logging in to a site (or any other operation that creates cookies that can be read back later) does not persist after a browser restart.
### Steps to Reproduce
#### Explicit cookie check
1. Fresh profile (delete existing)
2. Start browser
3. Open http://www.html-kit.com/tools/cookietester/
4. Click 'Set Test Cookie'
5. Restart browser
6. Visit http://www.html-kit.com/tools/cookietester/ again
**Actual result:**
`Number of cookies received: 0`
**Expected result:**
`Number of cookies received: 1`
**Reproduces how often:**
100%
#### Real world login check
1. Fresh profile (delete existing)
2. Start browser
3. Open http://www.google.com
4. Sign-in with valid credentials
5. Observe correctly logged in with avatar icon on google.com
5. Restart browser
6. Visit http://www.google.com again
**Actual result:**
No avatar present. 'Sign In' button is there instead.
**Expected result:**
Avatar shown for user which was used to login before restart. No 'Sign In' button present.
**Reproduces how often:**
100% however see notes below re: opening another site before the restart.
### Brave Version
**about:brave info:**
Brave: 0.23.19
V8: 6.7.288.46
rev: 178c3fbc045a0cbdbe098db08307503cce952081
Muon: 7.1.3
OS Release: 17.5.0
Update Channel: Release
OS Architecture: x64
OS Platform: macOS
Node.js: 7.9.0
Tor: 0.3.3.7 (git-035a35178c92da94)
Brave Sync: v1.4.2
libchromiumcontent: 67.0.3396.87
**Reproducible on current live release:**
Yes
### Additional Information
This may be more restricted to the most recently visited site as does not seem to reproduce 100% on the 2nd or 3rd most recently visited site that sets cookies. Or it could be to do with which tab is active. @srirambv reports that he can retain login when he has a different tab active for approx. 1 minute before closing the browser. | 1.0 | Cookies are not persisted across restart - ### Description
On a fresh profile, logging in to a site (or any other operation that creates cookies that can be read back later) does not persist after a browser restart.
### Steps to Reproduce
#### Explicit cookie check
1. Fresh profile (delete existing)
2. Start browser
3. Open http://www.html-kit.com/tools/cookietester/
4. Click 'Set Test Cookie'
5. Restart browser
6. Visit http://www.html-kit.com/tools/cookietester/ again
**Actual result:**
`Number of cookies received: 0`
**Expected result:**
`Number of cookies received: 1`
**Reproduces how often:**
100%
#### Real world login check
1. Fresh profile (delete existing)
2. Start browser
3. Open http://www.google.com
4. Sign-in with valid credentials
5. Observe correctly logged in with avatar icon on google.com
5. Restart browser
6. Visit http://www.google.com again
**Actual result:**
No avatar present. 'Sign In' button is there instead.
**Expected result:**
Avatar shown for user which was used to login before restart. No 'Sign In' button present.
**Reproduces how often:**
100% however see notes below re: opening another site before the restart.
### Brave Version
**about:brave info:**
Brave: 0.23.19
V8: 6.7.288.46
rev: 178c3fbc045a0cbdbe098db08307503cce952081
Muon: 7.1.3
OS Release: 17.5.0
Update Channel: Release
OS Architecture: x64
OS Platform: macOS
Node.js: 7.9.0
Tor: 0.3.3.7 (git-035a35178c92da94)
Brave Sync: v1.4.2
libchromiumcontent: 67.0.3396.87
**Reproducible on current live release:**
Yes
### Additional Information
This may be more restricted to the most recently visited site as does not seem to reproduce 100% on the 2nd or 3rd most recently visited site that sets cookies. Or it could be to do with which tab is active. @srirambv reports that he can retain login when he has a different tab active for approx. 1 minute before closing the browser. | non_defect | cookies are not persisted across restart description on a fresh profile logging in to a site or any other operation that creates cookies that can be read back later does not persist after a browser restart steps to reproduce explicit cookie check fresh profile delete existing start browser open click set test cookie restart browser visit again actual result number of cookies received expected result number of cookies received reproduces how often real world login check fresh profile delete existing start browser open sign in with valid credentials observe correctly logged in with avatar icon on google com restart browser visit again actual result no avatar present sign in button is there instead expected result avatar shown for user which was used to login before restart no sign in button present reproduces how often however see notes below re opening another site before the restart brave version about brave info brave rev muon os release update channel release os architecture os platform macos node js tor git brave sync libchromiumcontent reproducible on current live release yes additional information this may be more restricted to the most recently visited site as does not seem to reproduce on the or most recently visited site that sets cookies or it could be to do with which tab is active srirambv reports that he can retain login when he has a different tab active for approx minute before closing the browser | 0 |
25,982 | 4,540,072,148 | IssuesEvent | 2016-09-09 13:33:00 | stunpix/stacklessexamples | https://api.github.com/repos/stunpix/stacklessexamples | closed | error in StacklessNonblockModules/socketlibevent.py | auto-migrated Priority-Medium Type-Defect | ```
In wiki/StacklessNonblockModules/socketlibevent.py
Line 98: def create_connection(address, timeout=0.1):
If try:
>>>urllib2.urlopen("http://www.google.com").read(12)
get error:
TypeError: create_connection() takes at most 2 arguments (3 given)
I think this more correctly:
Line 98: def create_connection(address, timeout=0.1, sourse_address=''):
```
Original issue reported on code.google.com by `Faun...@gmail.com` on 8 Jan 2014 at 4:42 | 1.0 | error in StacklessNonblockModules/socketlibevent.py - ```
In wiki/StacklessNonblockModules/socketlibevent.py
Line 98: def create_connection(address, timeout=0.1):
If try:
>>>urllib2.urlopen("http://www.google.com").read(12)
get error:
TypeError: create_connection() takes at most 2 arguments (3 given)
I think this more correctly:
Line 98: def create_connection(address, timeout=0.1, sourse_address=''):
```
Original issue reported on code.google.com by `Faun...@gmail.com` on 8 Jan 2014 at 4:42 | defect | error in stacklessnonblockmodules socketlibevent py in wiki stacklessnonblockmodules socketlibevent py line def create connection address timeout if try urlopen get error typeerror create connection takes at most arguments given i think this more correctly line def create connection address timeout sourse address original issue reported on code google com by faun gmail com on jan at | 1 |
37,246 | 8,243,745,513 | IssuesEvent | 2018-09-11 02:07:37 | triplea-game/triplea | https://api.github.com/repos/triplea-game/triplea | closed | Change TripleA versioning | category: admin category: code improvement ice box - close and revisit later | I'm a huge fan of semantic versioning and I believe triplea should go for it as well.
Because of travis we need to keep the build numbers though!
I'd like to have `major.minor.patch.build` e.g. `1.9.0.4313` instead of `1.9.0.0.4313`.
Every time we'd like to evaluate the versions we'd just cut off the build number.
Read more about semantic versioning [here](http://semver.org/#summary). | 1.0 | Change TripleA versioning - I'm a huge fan of semantic versioning and I believe triplea should go for it as well.
Because of travis we need to keep the build numbers though!
I'd like to have `major.minor.patch.build` e.g. `1.9.0.4313` instead of `1.9.0.0.4313`.
Every time we'd like to evaluate the versions we'd just cut off the build number.
Read more about semantic versioning [here](http://semver.org/#summary). | non_defect | change triplea versioning i m a huge fan of semantic versioning and i believe triplea should go for it as well because of travis we need to keep the build numbers though i d like to have major minor patch build e g instead of every time we d like to evaluate the versions we d just cut off the build number read more about semantic versioning | 0 |
55,625 | 8,015,921,125 | IssuesEvent | 2018-07-25 11:42:25 | mlr-org/mlr | https://api.github.com/repos/mlr-org/mlr | closed | Wrong links in readme | type-documentation | Two links in the readme text (see below) do not work:
Some parts of the package were created as part of other publications. If you use these parts, please cite the relevant work appropriately. An overview of all mlr related publications can be found here.
A list of publications that cite mlr can be found in the wiki. | 1.0 | Wrong links in readme - Two links in the readme text (see below) do not work:
Some parts of the package were created as part of other publications. If you use these parts, please cite the relevant work appropriately. An overview of all mlr related publications can be found here.
A list of publications that cite mlr can be found in the wiki. | non_defect | wrong links in readme two links in the readme text see below do not work some parts of the package were created as part of other publications if you use these parts please cite the relevant work appropriately an overview of all mlr related publications can be found here a list of publications that cite mlr can be found in the wiki | 0 |
84,067 | 15,720,827,972 | IssuesEvent | 2021-03-29 01:20:22 | ysmanohar/myRetail | https://api.github.com/repos/ysmanohar/myRetail | opened | CVE-2020-11113 (High) detected in jackson-databind-2.7.4.jar | security vulnerability | ## CVE-2020-11113 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.7.4.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: /myRetail/myRetail/pom.xml</p>
<p>Path to vulnerable library: 2/repository/com/fasterxml/jackson/core/jackson-databind/2.7.4/jackson-databind-2.7.4.jar</p>
<p>
Dependency Hierarchy:
- :x: **jackson-databind-2.7.4.jar** (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>
FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.openjpa.ee.WASRegistryManagedRuntime (aka openjpa).
<p>Publish Date: 2020-03-31
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-11113>CVE-2020-11113</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.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11113">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11113</a></p>
<p>Release Date: 2020-03-31</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.9.10.4;2.10.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-11113 (High) detected in jackson-databind-2.7.4.jar - ## CVE-2020-11113 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.7.4.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: /myRetail/myRetail/pom.xml</p>
<p>Path to vulnerable library: 2/repository/com/fasterxml/jackson/core/jackson-databind/2.7.4/jackson-databind-2.7.4.jar</p>
<p>
Dependency Hierarchy:
- :x: **jackson-databind-2.7.4.jar** (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>
FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.openjpa.ee.WASRegistryManagedRuntime (aka openjpa).
<p>Publish Date: 2020-03-31
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-11113>CVE-2020-11113</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.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11113">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11113</a></p>
<p>Release Date: 2020-03-31</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.9.10.4;2.10.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_defect | cve high detected in jackson databind jar cve high severity vulnerability vulnerable library jackson databind jar general data binding functionality for jackson works on core streaming api library home page a href path to dependency file myretail myretail pom xml path to vulnerable library repository com fasterxml jackson core jackson databind jackson databind jar dependency hierarchy x jackson databind jar vulnerable library vulnerability details fasterxml jackson databind x before mishandles the interaction between serialization gadgets and typing related to org apache openjpa ee wasregistrymanagedruntime aka openjpa publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact 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 com fasterxml jackson core jackson databind step up your open source security game with whitesource | 0 |
666,723 | 22,365,171,476 | IssuesEvent | 2022-06-16 02:42:25 | alibaba/GraphScope | https://api.github.com/repos/alibaba/GraphScope | closed | GraphScope Gremlin 引擎问题反馈 | priority:high component:gaia | **Describe the bug**
使用 Gremlin 查询过程中遇到的问题，都反馈到这个 issues 下面， 麻烦 @yecol 统一看一下，感谢！
- [x] nodejs id 不一致
- [x] valueMap 支持
- [x] gremlin 3.5.1 patch 包发布
- [x] `bothE` failed
- [x] `both().bothE()` failed
- [x] `valueMap` 为 None 的点也返回
- [ ] 边属性 (#1723 )
- [x] 模式匹配：JSON 转 Gremlin 语句，查询结果
- [ ] ~~g.V().has('id', 'xxx')，报错 key id must be positive number~~
- [ ] repeat operator support (#1722 ) | 1.0 | GraphScope Gremlin 引擎问题反馈 - **Describe the bug**
使用 Gremlin 查询过程中遇到的问题，都反馈到这个 issues 下面， 麻烦 @yecol 统一看一下，感谢！
- [x] nodejs id 不一致
- [x] valueMap 支持
- [x] gremlin 3.5.1 patch 包发布
- [x] `bothE` failed
- [x] `both().bothE()` failed
- [x] `valueMap` 为 None 的点也返回
- [ ] 边属性 (#1723 )
- [x] 模式匹配：JSON 转 Gremlin 语句，查询结果
- [ ] ~~g.V().has('id', 'xxx')，报错 key id must be positive number~~
- [ ] repeat operator support (#1722 ) | non_defect | graphscope gremlin 引擎问题反馈 describe the bug 使用 gremlin 查询过程中遇到的问题，都反馈到这个 issues 下面， 麻烦 yecol 统一看一下，感谢！ nodejs id 不一致 valuemap 支持 gremlin patch 包发布 bothe failed both bothe failed valuemap 为 none 的点也返回 边属性 模式匹配：json 转 gremlin 语句，查询结果 g v has id xxx ，报错 key id must be positive number repeat operator support | 0 |
21,014 | 3,670,543,551 | IssuesEvent | 2016-02-21 22:32:07 | gustafl/lexeme | https://api.github.com/repos/gustafl/lexeme | opened | Implement cookies | design future server | At some point, I probably need to keep track of users with cookies. The last module in this course seem like a good starting point:
https://app.pluralsight.com/library/courses/xhttp-fund/table-of-contents | 1.0 | Implement cookies - At some point, I probably need to keep track of users with cookies. The last module in this course seem like a good starting point:
https://app.pluralsight.com/library/courses/xhttp-fund/table-of-contents | non_defect | implement cookies at some point i probably need to keep track of users with cookies the last module in this course seem like a good starting point | 0 |
81,033 | 10,221,067,250 | IssuesEvent | 2019-08-15 23:46:48 | gatsbyjs/gatsby | https://api.github.com/repos/gatsbyjs/gatsby | closed | [docs][recipes] Images: querying with GraphQL and gatsby-image | effort: med impact: high topic: GraphQL topic: images/media topic: recipes type: documentation | ## Summary
To improve key learning workflows in the Recipes section of the docs, there should be a short, actionable recipe on querying for images with gatsby-image. This should come after #14985 and #14986.
This recipe should briefly mention the benefits of Gatsby's data layer and show how to query for an image with GraphQL _inline_ as concisely as possible. It should include code snippets and potentially an embedded example. The [Gatsby Image doc](https://www.gatsbyjs.org/docs/gatsby-image/) and other [image docs](https://www.gatsbyjs.org/docs/using-gatsby-image/) can be used for reference.
Because the various methods we want to show for images are such small tweaks (and would carry a lot of boilerplate if all broken out individually), this issue covers multiple variations that can be slotted into the "Step-by-step instructions" part of the recipe.
Recipes now follow this format:
- Requirements or prerequisites
- Step-by-step instructions
- Relevant links to any relevant information
- Gatsby Image API https://www.gatsbyjs.org/docs/gatsby-image/
- Using Gatsby Image https://www.gatsbyjs.org/docs/using-gatsby-image/
- More on working with images in Gatsby https://www.gatsbyjs.org/docs/working-with-images/
- Link to a live example
Techniques this issue should cover:
- [ ] Querying by relativePath
- [ ] from a directory
- [ ] from post frontmatter
- [ ] fixed width and height
- [ ] fixed maxWidth
- [ ] fluid maxWidth and quality
- [ ] fluid but limited by height
- [ ] with inline styles applied
- [ ] with a fragment like `GatsbyImageSharpFixed`
- [ ] preserving an aspectRatio
These recipes should go into a new section of [`docs/docs/recipes.md`](https://github.com/gatsbyjs/gatsby/blob/master/docs/docs/recipes.md) titled "Images" (if it isn't already created). There is a recipe template in the contributing docs, including tips on adding a new section: https://www.gatsbyjs.org/contributing/docs-templates/#recipes
For reference, the new recipe collection is also listed in a spreadsheet: https://docs.google.com/spreadsheets/d/1yNUQi_-3TsuDtE98hCIJQvLZ6X1YHlDmC-EJwOGxiHk/edit#gid=1252007048 | 1.0 | [docs][recipes] Images: querying with GraphQL and gatsby-image - ## Summary
To improve key learning workflows in the Recipes section of the docs, there should be a short, actionable recipe on querying for images with gatsby-image. This should come after #14985 and #14986.
This recipe should briefly mention the benefits of Gatsby's data layer and show how to query for an image with GraphQL _inline_ as concisely as possible. It should include code snippets and potentially an embedded example. The [Gatsby Image doc](https://www.gatsbyjs.org/docs/gatsby-image/) and other [image docs](https://www.gatsbyjs.org/docs/using-gatsby-image/) can be used for reference.
Because the various methods we want to show for images are such small tweaks (and would carry a lot of boilerplate if all broken out individually), this issue covers multiple variations that can be slotted into the "Step-by-step instructions" part of the recipe.
Recipes now follow this format:
- Requirements or prerequisites
- Step-by-step instructions
- Relevant links to any relevant information
- Gatsby Image API https://www.gatsbyjs.org/docs/gatsby-image/
- Using Gatsby Image https://www.gatsbyjs.org/docs/using-gatsby-image/
- More on working with images in Gatsby https://www.gatsbyjs.org/docs/working-with-images/
- Link to a live example
Techniques this issue should cover:
- [ ] Querying by relativePath
- [ ] from a directory
- [ ] from post frontmatter
- [ ] fixed width and height
- [ ] fixed maxWidth
- [ ] fluid maxWidth and quality
- [ ] fluid but limited by height
- [ ] with inline styles applied
- [ ] with a fragment like `GatsbyImageSharpFixed`
- [ ] preserving an aspectRatio
These recipes should go into a new section of [`docs/docs/recipes.md`](https://github.com/gatsbyjs/gatsby/blob/master/docs/docs/recipes.md) titled "Images" (if it isn't already created). There is a recipe template in the contributing docs, including tips on adding a new section: https://www.gatsbyjs.org/contributing/docs-templates/#recipes
For reference, the new recipe collection is also listed in a spreadsheet: https://docs.google.com/spreadsheets/d/1yNUQi_-3TsuDtE98hCIJQvLZ6X1YHlDmC-EJwOGxiHk/edit#gid=1252007048 | non_defect | images querying with graphql and gatsby image summary to improve key learning workflows in the recipes section of the docs there should be a short actionable recipe on querying for images with gatsby image this should come after and this recipe should briefly mention the benefits of gatsby s data layer and show how to query for an image with graphql inline as concisely as possible it should include code snippets and potentially an embedded example the and other can be used for reference because the various methods we want to show for images are such small tweaks and would carry a lot of boilerplate if all broken out individually this issue covers multiple variations that can be slotted into the step by step instructions part of the recipe recipes now follow this format requirements or prerequisites step by step instructions relevant links to any relevant information gatsby image api using gatsby image more on working with images in gatsby link to a live example techniques this issue should cover querying by relativepath from a directory from post frontmatter fixed width and height fixed maxwidth fluid maxwidth and quality fluid but limited by height with inline styles applied with a fragment like gatsbyimagesharpfixed preserving an aspectratio these recipes should go into a new section of titled images if it isn t already created there is a recipe template in the contributing docs including tips on adding a new section for reference the new recipe collection is also listed in a spreadsheet | 0 |
369,681 | 25,863,495,707 | IssuesEvent | 2022-12-13 18:47:43 | iobroker-community-adapters/ioBroker.snmp | https://api.github.com/repos/iobroker-community-adapters/ioBroker.snmp | closed | [Documentation] Tables incorrectly formatted at german guide | bug fixed documentation | Tables are not formatted as tables in german deocument.
Might be incorrec t in russian version too. | 1.0 | [Documentation] Tables incorrectly formatted at german guide - Tables are not formatted as tables in german deocument.
Might be incorrec t in russian version too. | non_defect | tables incorrectly formatted at german guide tables are not formatted as tables in german deocument might be incorrec t in russian version too | 0 |
6,873 | 2,867,140,695 | IssuesEvent | 2015-06-05 11:22:36 | TinyModularThings/IC2Classic | https://api.github.com/repos/TinyModularThings/IC2Classic | closed | Nuclear Jetpack | In Testing Textures Needed | I like the idea.
Logic is still breeding (like a breeder xD) in my head but i think i will implement that to classic.
It has its good a bad side, for sure.
But it will be fun.
(Worst case: Nuclear explosion at the air because overheated xD) | 1.0 | Nuclear Jetpack - I like the idea.
Logic is still breeding (like a breeder xD) in my head but i think i will implement that to classic.
It has its good a bad side, for sure.
But it will be fun.
(Worst case: Nuclear explosion at the air because overheated xD) | non_defect | nuclear jetpack i like the idea logic is still breeding like a breeder xd in my head but i think i will implement that to classic it has its good a bad side for sure but it will be fun worst case nuclear explosion at the air because overheated xd | 0 |
13,866 | 8,700,446,024 | IssuesEvent | 2018-12-05 08:46:03 | agazso/postmodern | https://api.github.com/repos/agazso/postmodern | closed | after adding a feed, it is unclear if it's added, or it was just found / validated | idea usability | ### Possible solutions
##### Short term
After adding a feed, move to the tab where we show the content, and refresh it automatically
##### Long term
There should be a view for an individual feed, we should open it after adding the feed
| True | after adding a feed, it is unclear if it's added, or it was just found / validated - ### Possible solutions
##### Short term
After adding a feed, move to the tab where we show the content, and refresh it automatically
##### Long term
There should be a view for an individual feed, we should open it after adding the feed
| non_defect | after adding a feed it is unclear if it s added or it was just found validated possible solutions short term after adding a feed move to the tab where we show the content and refresh it automatically long term there should be a view for an individual feed we should open it after adding the feed | 0 |
24,078 | 3,907,575,900 | IssuesEvent | 2016-04-19 13:20:25 | sky-map-team/stardroid | https://api.github.com/repos/sky-map-team/stardroid | closed | Constants are being modified | auto-migrated Priority-Medium Type-Defect | ```
When ApplicationConstants.INITIAL_SOUTH and INITIAL_DOWN are being assigned to
variables, this leads to these constants getting modified by the code.
Wherever the constants are assigned to variables, there needs to be a .copy().
```
Original issue reported on code.google.com by `arpruss` on 23 Oct 2013 at 11:25 | 1.0 | Constants are being modified - ```
When ApplicationConstants.INITIAL_SOUTH and INITIAL_DOWN are being assigned to
variables, this leads to these constants getting modified by the code.
Wherever the constants are assigned to variables, there needs to be a .copy().
```
Original issue reported on code.google.com by `arpruss` on 23 Oct 2013 at 11:25 | defect | constants are being modified when applicationconstants initial south and initial down are being assigned to variables this leads to these constants getting modified by the code wherever the constants are assigned to variables there needs to be a copy original issue reported on code google com by arpruss on oct at | 1 |
3,996 | 6,823,885,786 | IssuesEvent | 2017-11-08 02:30:52 | cobalt-org/liquid-rust | https://api.github.com/repos/cobalt-org/liquid-rust | opened | Pass variables to `include`d partial? | shopify-compatibility | Shopify and Jekyll seem to handle this different.
Shopify seems to put the variable in the global namespace and uses ":" for assignment
- https://help.shopify.com/themes/liquid/tags/theme-tags#include
Jekyll seems to scope the variables to the partial's name and uses `=` for assignment
- https://jekyllrb.com/docs/includes/#passing-parameters-to-includes | True | Pass variables to `include`d partial? - Shopify and Jekyll seem to handle this different.
Shopify seems to put the variable in the global namespace and uses ":" for assignment
- https://help.shopify.com/themes/liquid/tags/theme-tags#include
Jekyll seems to scope the variables to the partial's name and uses `=` for assignment
- https://jekyllrb.com/docs/includes/#passing-parameters-to-includes | non_defect | pass variables to include d partial shopify and jekyll seem to handle this different shopify seems to put the variable in the global namespace and uses for assignment jekyll seems to scope the variables to the partial s name and uses for assignment | 0 |
45,207 | 7,166,358,990 | IssuesEvent | 2018-01-29 16:59:24 | CICE-Consortium/Icepack | https://api.github.com/repos/CICE-Consortium/Icepack | closed | clean up index of variables | Documentation | Remove anything not in Icepack, and make sure all of the namelist options are included (bullets).
This one is extremely tedious, and I welcome all the help I can get. We could divide up the alphabet... I'll take X! | 1.0 | clean up index of variables - Remove anything not in Icepack, and make sure all of the namelist options are included (bullets).
This one is extremely tedious, and I welcome all the help I can get. We could divide up the alphabet... I'll take X! | non_defect | clean up index of variables remove anything not in icepack and make sure all of the namelist options are included bullets this one is extremely tedious and i welcome all the help i can get we could divide up the alphabet i ll take x | 0 |
309,112 | 9,461,648,995 | IssuesEvent | 2019-04-17 13:54:42 | project-koku/koku | https://api.github.com/repos/project-koku/koku | closed | OCP order_by derived and infrastructure costs | bug priority - medium | ## User Story
As a user, I want to sort the OCP details page by derived and infrastructure cost.
It appears that `order_by[derived_cost]=asc` and `order_by[infrastructure_cost]=asc` are not supported parameters of the reports/openshift/costs API.
## Impacts
Ex. API, UI, Docs
## Role
User
## Assumptions
-
-
## API Details
| API | Detail|
| --- | --- |
| **Method** | GET |
| **Path** | /api/v1/reports/openshift/costs/ |
| **Body** | &order_by[derived_cost]=asc |
| **Response** | |
| API | Detail|
| --- | --- |
| **Method** | GET |
| **Path** | /api/v1/reports/openshift/costs/ |
| **Body** | &order_by[infrastructure_cost]=asc |
| **Response** | |
<img width="1177" alt="Screen Shot 2019-04-07 at 10 57 55 AM" src="https://user-images.githubusercontent.com/17481322/55685481-d93f2680-5924-11e9-8a8c-79e6ff6d7ead.png">
<img width="1193" alt="Screen Shot 2019-04-07 at 10 57 22 AM" src="https://user-images.githubusercontent.com/17481322/55685483-dd6b4400-5924-11e9-970e-6c1a15b37ef3.png">
## UI Details
We want to update the Cost details page with derived and infrastructure columns, like so:
<img width="1262" alt="Screen Shot 2019-04-07 at 11 00 03 AM" src="https://user-images.githubusercontent.com/17481322/55685463-92513100-5924-11e9-9548-a975046177be.png">
## Acceptance Criteria
- [ ] Sort by derived cost
- [ ] Sort by infrastructure cost
| 1.0 | OCP order_by derived and infrastructure costs - ## User Story
As a user, I want to sort the OCP details page by derived and infrastructure cost.
It appears that `order_by[derived_cost]=asc` and `order_by[infrastructure_cost]=asc` are not supported parameters of the reports/openshift/costs API.
## Impacts
Ex. API, UI, Docs
## Role
User
## Assumptions
-
-
## API Details
| API | Detail|
| --- | --- |
| **Method** | GET |
| **Path** | /api/v1/reports/openshift/costs/ |
| **Body** | &order_by[derived_cost]=asc |
| **Response** | |
| API | Detail|
| --- | --- |
| **Method** | GET |
| **Path** | /api/v1/reports/openshift/costs/ |
| **Body** | &order_by[infrastructure_cost]=asc |
| **Response** | |
<img width="1177" alt="Screen Shot 2019-04-07 at 10 57 55 AM" src="https://user-images.githubusercontent.com/17481322/55685481-d93f2680-5924-11e9-8a8c-79e6ff6d7ead.png">
<img width="1193" alt="Screen Shot 2019-04-07 at 10 57 22 AM" src="https://user-images.githubusercontent.com/17481322/55685483-dd6b4400-5924-11e9-970e-6c1a15b37ef3.png">
## UI Details
We want to update the Cost details page with derived and infrastructure columns, like so:
<img width="1262" alt="Screen Shot 2019-04-07 at 11 00 03 AM" src="https://user-images.githubusercontent.com/17481322/55685463-92513100-5924-11e9-9548-a975046177be.png">
## Acceptance Criteria
- [ ] Sort by derived cost
- [ ] Sort by infrastructure cost
| non_defect | ocp order by derived and infrastructure costs user story as a user i want to sort the ocp details page by derived and infrastructure cost it appears that order by asc and order by asc are not supported parameters of the reports openshift costs api impacts ex api ui docs role user assumptions api details api detail method get path api reports openshift costs body order by asc response api detail method get path api reports openshift costs body order by asc response img width alt screen shot at am src img width alt screen shot at am src ui details we want to update the cost details page with derived and infrastructure columns like so img width alt screen shot at am src acceptance criteria sort by derived cost sort by infrastructure cost | 0 |
73,057 | 24,433,221,383 | IssuesEvent | 2022-10-06 09:36:24 | vector-im/element-web | https://api.github.com/repos/vector-im/element-web | closed | Unread notification not associated with a room | T-Defect P1 A-Room-List A-Notifications | ### Description
Messages sent (by others) to a particular room result in an unread messages notification badge on the rooms section header, but there is no notifications badge for the corresponding room. This makes it very hard to track down where the notification is coming from (and clear it).
This behaviour is seen on all of my devices and was observed before enabling edits / reactions.
As requested by @dbkr - Here are my push notification rules.
```
{
"global": {
"underride": [
{
"conditions": [
{
"kind": "event_match",
"key": "type",
"pattern": "m.call.invite"
}
],
"actions": [
"notify",
{
"set_tweak": "sound",
"value": "ring"
},
{
"set_tweak": "highlight",
"value": false
}
],
"rule_id": ".m.rule.call",
"default": true,
"enabled": true
},
{
"conditions": [
{
"kind": "room_member_count",
"is": "2"
},
{
"kind": "event_match",
"key": "type",
"pattern": "m.room.message"
}
],
"actions": [
"notify",
{
"set_tweak": "sound",
"value": "default"
},
{
"set_tweak": "highlight",
"value": false
}
],
"rule_id": ".m.rule.room_one_to_one",
"default": true,
"enabled": true
},
{
"conditions": [
{
"kind": "room_member_count",
"is": "2"
},
{
"kind": "event_match",
"key": "type",
"pattern": "m.room.encrypted"
}
],
"actions": [
"notify",
{
"set_tweak": "sound",
"value": "default"
},
{
"set_tweak": "highlight",
"value": false
}
],
"rule_id": ".m.rule.encrypted_room_one_to_one",
"default": true,
"enabled": true
},
{
"conditions": [
{
"kind": "event_match",
"key": "type",
"pattern": "m.room.message"
}
],
"actions": [
"notify",
{
"set_tweak": "highlight",
"value": false
}
],
"rule_id": ".m.rule.message",
"default": true,
"enabled": true
},
{
"conditions": [
{
"kind": "event_match",
"key": "type",
"pattern": "m.room.encrypted"
}
],
"actions": [
"notify",
{
"set_tweak": "highlight",
"value": false
}
],
"rule_id": ".m.rule.encrypted",
"default": true,
"enabled": true
}
],
"sender": [],
"room": [
{
"actions": [
"dont_notify"
],
"rule_id": "!zVpPeWAObqutioiNzB:jki.re",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!nOUsIUkdCEMFqwiMXO:matrix.org",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!FPUfgzXYWTKgIrwKxW:matrix.org",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!yjVgJUsMLYLAONsoii:jki.re",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!OYyXUbcTKVsDBUniNn:matrix.eclabs.de",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!DdJkzRliezrwpNebLk:matrix.org",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!UmtgDmQCkKlaIkLEyH:half-shot.uk",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!qXkGwIopNrIUglrMJT:lant.uk",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!svJUttHBtRMdXmEhEy:matrix.org",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!TfGOBljmIFILPqKYwQ:matrix.org",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!yZHTGeDKZUeKaqeTeU:matrix.org",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!DYgXKezaHgMbiPMzjX:matrix.org",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!YkZelGRiqijtzXZODa:matrix.org",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!RbKRuLTvHIhArQcvjr:matrix.org",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!JJWoPvaGeOhPudCOMt:matrix.org",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!iNmaIQExDMeqdITdHH:matrix.org",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!UwfyezyoefyCIPOOXS:matrix.org",
"enabled": true
}
],
"content": [
{
"actions": [
"notify",
{
"set_tweak": "sound",
"value": "default"
},
{
"set_tweak": "highlight"
}
],
"pattern": "rxl881",
"rule_id": ".m.rule.contains_user_name",
"default": true,
"enabled": true
}
],
"override": [
{
"conditions": [],
"actions": [
"dont_notify"
],
"rule_id": ".m.rule.master",
"default": true,
"enabled": false
},
{
"conditions": [
{
"kind": "event_match",
"key": "content.msgtype",
"pattern": "m.notice"
}
],
"actions": [
"dont_notify"
],
"rule_id": ".m.rule.suppress_notices",
"default": true,
"enabled": true
},
{
"conditions": [
{
"kind": "event_match",
"key": "type",
"pattern": "m.room.member"
},
{
"kind": "event_match",
"key": "content.membership",
"pattern": "invite"
},
{
"kind": "event_match",
"key": "state_key",
"pattern": "@rxl881:vector.modular.im"
}
],
"actions": [
"notify",
{
"set_tweak": "sound",
"value": "default"
},
{
"set_tweak": "highlight",
"value": false
}
],
"rule_id": ".m.rule.invite_for_me",
"default": true,
"enabled": true
},
{
"conditions": [
{
"kind": "event_match",
"key": "type",
"pattern": "m.room.member"
}
],
"actions": [
"dont_notify"
],
"rule_id": ".m.rule.member_event",
"default": true,
"enabled": true
},
{
"conditions": [
{
"kind": "contains_display_name"
}
],
"actions": [
"notify",
{
"set_tweak": "sound",
"value": "default"
},
{
"set_tweak": "highlight"
}
],
"rule_id": ".m.rule.contains_display_name",
"default": true,
"enabled": true
},
{
"conditions": [
{
"kind": "event_match",
"key": "content.body",
"pattern": "@room"
},
{
"kind": "sender_notification_permission",
"key": "room"
}
],
"actions": [
"notify",
{
"set_tweak": "highlight",
"value": true
}
],
"rule_id": ".m.rule.roomnotif",
"default": true,
"enabled": true
},
{
"conditions": [
{
"kind": "event_match",
"key": "type",
"pattern": "m.room.tombstone"
}
],
"actions": [
"notify",
{
"set_tweak": "highlight",
"value": true
}
],
"rule_id": ".m.rule.tombstone",
"default": true,
"enabled": true
}
]
},
"device": {}
}
```
- **Platform**: web (in-browser) or desktop?
For the web app:
- **Browser**: Chrome
- **OS**: macOS, Ubuntu
- **URL**: riot.im/develop
| 1.0 | Unread notification not associated with a room - ### Description
Messages sent (by others) to a particular room result in an unread messages notification badge on the rooms section header, but there is no notifications badge for the corresponding room. This makes it very hard to track down where the notification is coming from (and clear it).
This behaviour is seen on all of my devices and was observed before enabling edits / reactions.
As requested by @dbkr - Here are my push notification rules.
```
{
"global": {
"underride": [
{
"conditions": [
{
"kind": "event_match",
"key": "type",
"pattern": "m.call.invite"
}
],
"actions": [
"notify",
{
"set_tweak": "sound",
"value": "ring"
},
{
"set_tweak": "highlight",
"value": false
}
],
"rule_id": ".m.rule.call",
"default": true,
"enabled": true
},
{
"conditions": [
{
"kind": "room_member_count",
"is": "2"
},
{
"kind": "event_match",
"key": "type",
"pattern": "m.room.message"
}
],
"actions": [
"notify",
{
"set_tweak": "sound",
"value": "default"
},
{
"set_tweak": "highlight",
"value": false
}
],
"rule_id": ".m.rule.room_one_to_one",
"default": true,
"enabled": true
},
{
"conditions": [
{
"kind": "room_member_count",
"is": "2"
},
{
"kind": "event_match",
"key": "type",
"pattern": "m.room.encrypted"
}
],
"actions": [
"notify",
{
"set_tweak": "sound",
"value": "default"
},
{
"set_tweak": "highlight",
"value": false
}
],
"rule_id": ".m.rule.encrypted_room_one_to_one",
"default": true,
"enabled": true
},
{
"conditions": [
{
"kind": "event_match",
"key": "type",
"pattern": "m.room.message"
}
],
"actions": [
"notify",
{
"set_tweak": "highlight",
"value": false
}
],
"rule_id": ".m.rule.message",
"default": true,
"enabled": true
},
{
"conditions": [
{
"kind": "event_match",
"key": "type",
"pattern": "m.room.encrypted"
}
],
"actions": [
"notify",
{
"set_tweak": "highlight",
"value": false
}
],
"rule_id": ".m.rule.encrypted",
"default": true,
"enabled": true
}
],
"sender": [],
"room": [
{
"actions": [
"dont_notify"
],
"rule_id": "!zVpPeWAObqutioiNzB:jki.re",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!nOUsIUkdCEMFqwiMXO:matrix.org",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!FPUfgzXYWTKgIrwKxW:matrix.org",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!yjVgJUsMLYLAONsoii:jki.re",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!OYyXUbcTKVsDBUniNn:matrix.eclabs.de",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!DdJkzRliezrwpNebLk:matrix.org",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!UmtgDmQCkKlaIkLEyH:half-shot.uk",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!qXkGwIopNrIUglrMJT:lant.uk",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!svJUttHBtRMdXmEhEy:matrix.org",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!TfGOBljmIFILPqKYwQ:matrix.org",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!yZHTGeDKZUeKaqeTeU:matrix.org",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!DYgXKezaHgMbiPMzjX:matrix.org",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!YkZelGRiqijtzXZODa:matrix.org",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!RbKRuLTvHIhArQcvjr:matrix.org",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!JJWoPvaGeOhPudCOMt:matrix.org",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!iNmaIQExDMeqdITdHH:matrix.org",
"enabled": true
},
{
"actions": [
"dont_notify"
],
"rule_id": "!UwfyezyoefyCIPOOXS:matrix.org",
"enabled": true
}
],
"content": [
{
"actions": [
"notify",
{
"set_tweak": "sound",
"value": "default"
},
{
"set_tweak": "highlight"
}
],
"pattern": "rxl881",
"rule_id": ".m.rule.contains_user_name",
"default": true,
"enabled": true
}
],
"override": [
{
"conditions": [],
"actions": [
"dont_notify"
],
"rule_id": ".m.rule.master",
"default": true,
"enabled": false
},
{
"conditions": [
{
"kind": "event_match",
"key": "content.msgtype",
"pattern": "m.notice"
}
],
"actions": [
"dont_notify"
],
"rule_id": ".m.rule.suppress_notices",
"default": true,
"enabled": true
},
{
"conditions": [
{
"kind": "event_match",
"key": "type",
"pattern": "m.room.member"
},
{
"kind": "event_match",
"key": "content.membership",
"pattern": "invite"
},
{
"kind": "event_match",
"key": "state_key",
"pattern": "@rxl881:vector.modular.im"
}
],
"actions": [
"notify",
{
"set_tweak": "sound",
"value": "default"
},
{
"set_tweak": "highlight",
"value": false
}
],
"rule_id": ".m.rule.invite_for_me",
"default": true,
"enabled": true
},
{
"conditions": [
{
"kind": "event_match",
"key": "type",
"pattern": "m.room.member"
}
],
"actions": [
"dont_notify"
],
"rule_id": ".m.rule.member_event",
"default": true,
"enabled": true
},
{
"conditions": [
{
"kind": "contains_display_name"
}
],
"actions": [
"notify",
{
"set_tweak": "sound",
"value": "default"
},
{
"set_tweak": "highlight"
}
],
"rule_id": ".m.rule.contains_display_name",
"default": true,
"enabled": true
},
{
"conditions": [
{
"kind": "event_match",
"key": "content.body",
"pattern": "@room"
},
{
"kind": "sender_notification_permission",
"key": "room"
}
],
"actions": [
"notify",
{
"set_tweak": "highlight",
"value": true
}
],
"rule_id": ".m.rule.roomnotif",
"default": true,
"enabled": true
},
{
"conditions": [
{
"kind": "event_match",
"key": "type",
"pattern": "m.room.tombstone"
}
],
"actions": [
"notify",
{
"set_tweak": "highlight",
"value": true
}
],
"rule_id": ".m.rule.tombstone",
"default": true,
"enabled": true
}
]
},
"device": {}
}
```
- **Platform**: web (in-browser) or desktop?
For the web app:
- **Browser**: Chrome
- **OS**: macOS, Ubuntu
- **URL**: riot.im/develop
| defect | unread notification not associated with a room description messages sent by others to a particular room result in an unread messages notification badge on the rooms section header but there is no notifications badge for the corresponding room this makes it very hard to track down where the notification is coming from and clear it this behaviour is seen on all of my devices and was observed before enabling edits reactions as requested by dbkr here are my push notification rules global underride conditions kind event match key type pattern m call invite actions notify set tweak sound value ring set tweak highlight value false rule id m rule call default true enabled true conditions kind room member count is kind event match key type pattern m room message actions notify set tweak sound value default set tweak highlight value false rule id m rule room one to one default true enabled true conditions kind room member count is kind event match key type pattern m room encrypted actions notify set tweak sound value default set tweak highlight value false rule id m rule encrypted room one to one default true enabled true conditions kind event match key type pattern m room message actions notify set tweak highlight value false rule id m rule message default true enabled true conditions kind event match key type pattern m room encrypted actions notify set tweak highlight value false rule id m rule encrypted default true enabled true sender room actions dont notify rule id zvppewaobqutioinzb jki re enabled true actions dont notify rule id nousiukdcemfqwimxo matrix org enabled true actions dont notify rule id fpufgzxywtkgirwkxw matrix org enabled true actions dont notify rule id yjvgjusmlylaonsoii jki re enabled true actions dont notify rule id oyyxubctkvsdbuninn matrix eclabs de enabled true actions dont notify rule id ddjkzrliezrwpneblk matrix org enabled true actions dont notify rule id umtgdmqckklaikleyh half shot uk enabled true actions dont notify rule id qxkgwiopnriuglrmjt lant uk enabled true actions dont notify rule id svjutthbtrmdxmehey matrix org enabled true actions dont notify rule id tfgobljmifilpqkywq matrix org enabled true actions dont notify rule id yzhtgedkzuekaqeteu matrix org enabled true actions dont notify rule id dygxkezahgmbipmzjx matrix org enabled true actions dont notify rule id ykzelgriqijtzxzoda matrix org enabled true actions dont notify rule id rbkrultvhiharqcvjr matrix org enabled true actions dont notify rule id jjwopvageohpudcomt matrix org enabled true actions dont notify rule id inmaiqexdmeqditdhh matrix org enabled true actions dont notify rule id uwfyezyoefycipooxs matrix org enabled true content actions notify set tweak sound value default set tweak highlight pattern rule id m rule contains user name default true enabled true override conditions actions dont notify rule id m rule master default true enabled false conditions kind event match key content msgtype pattern m notice actions dont notify rule id m rule suppress notices default true enabled true conditions kind event match key type pattern m room member kind event match key content membership pattern invite kind event match key state key pattern vector modular im actions notify set tweak sound value default set tweak highlight value false rule id m rule invite for me default true enabled true conditions kind event match key type pattern m room member actions dont notify rule id m rule member event default true enabled true conditions kind contains display name actions notify set tweak sound value default set tweak highlight rule id m rule contains display name default true enabled true conditions kind event match key content body pattern room kind sender notification permission key room actions notify set tweak highlight value true rule id m rule roomnotif default true enabled true conditions kind event match key type pattern m room tombstone actions notify set tweak highlight value true rule id m rule tombstone default true enabled true device platform web in browser or desktop for the web app browser chrome os macos ubuntu url riot im develop | 1 |
26,706 | 4,777,613,997 | IssuesEvent | 2016-10-27 16:46:59 | wheeler-microfluidics/microdrop | https://api.github.com/repos/wheeler-microfluidics/microdrop | closed | Fix startup behaviour (Trac #35) | defect microdrop Migrated from Trac | Fix problems with initial startup (e.g., when no device is loaded,
disable protocol menu and other relevant controls, etc.).
Migrated from http://microfluidics.utoronto.ca/ticket/35
```json
{
"status": "closed",
"changetime": "2014-04-17T19:39:01",
"description": "Fix problems with initial startup (e.g., when no device is loaded,\ndisable protocol menu and other relevant controls, etc.).",
"reporter": "cfobel",
"cc": "",
"resolution": "fixed",
"_ts": "1397763541728826",
"component": "microdrop",
"summary": "Fix startup behaviour",
"priority": "major",
"keywords": "",
"version": "0.1",
"time": "2012-01-06T21:40:02",
"milestone": "Microdrop 1.0",
"owner": "cfobel",
"type": "defect"
}
```
| 1.0 | Fix startup behaviour (Trac #35) - Fix problems with initial startup (e.g., when no device is loaded,
disable protocol menu and other relevant controls, etc.).
Migrated from http://microfluidics.utoronto.ca/ticket/35
```json
{
"status": "closed",
"changetime": "2014-04-17T19:39:01",
"description": "Fix problems with initial startup (e.g., when no device is loaded,\ndisable protocol menu and other relevant controls, etc.).",
"reporter": "cfobel",
"cc": "",
"resolution": "fixed",
"_ts": "1397763541728826",
"component": "microdrop",
"summary": "Fix startup behaviour",
"priority": "major",
"keywords": "",
"version": "0.1",
"time": "2012-01-06T21:40:02",
"milestone": "Microdrop 1.0",
"owner": "cfobel",
"type": "defect"
}
```
| defect | fix startup behaviour trac fix problems with initial startup e g when no device is loaded disable protocol menu and other relevant controls etc migrated from json status closed changetime description fix problems with initial startup e g when no device is loaded ndisable protocol menu and other relevant controls etc reporter cfobel cc resolution fixed ts component microdrop summary fix startup behaviour priority major keywords version time milestone microdrop owner cfobel type defect | 1 |
30,615 | 6,194,260,517 | IssuesEvent | 2017-07-05 09:27:57 | contao/standard-edition | https://api.github.com/repos/contao/standard-edition | closed | Add basic security | defect | I would like to add the [NelmioSecurityBundle](https://github.com/nelmio/NelmioSecurityBundle) to our default configuration and configure it with the following basic settings:
```yaml
# Security configuration
nelmio_security:
clickjacking:
paths:
'^/.*': SAMEORIGIN
content_type:
nosniff: true
referrer_policy:
enabled: true
policies:
- 'origin-when-cross-origin'
xss_protection:
enabled: true
mode_block: true
```
These basic settings should apply (and should be applied :smile:) to every website.
@contao/developers Any objections?
| 1.0 | Add basic security - I would like to add the [NelmioSecurityBundle](https://github.com/nelmio/NelmioSecurityBundle) to our default configuration and configure it with the following basic settings:
```yaml
# Security configuration
nelmio_security:
clickjacking:
paths:
'^/.*': SAMEORIGIN
content_type:
nosniff: true
referrer_policy:
enabled: true
policies:
- 'origin-when-cross-origin'
xss_protection:
enabled: true
mode_block: true
```
These basic settings should apply (and should be applied :smile:) to every website.
@contao/developers Any objections?
| defect | add basic security i would like to add the to our default configuration and configure it with the following basic settings yaml security configuration nelmio security clickjacking paths sameorigin content type nosniff true referrer policy enabled true policies origin when cross origin xss protection enabled true mode block true these basic settings should apply and should be applied smile to every website contao developers any objections | 1 |
26,765 | 4,778,175,888 | IssuesEvent | 2016-10-27 18:30:02 | wheeler-microfluidics/microdrop | https://api.github.com/repos/wheeler-microfluidics/microdrop | closed | Problem installing task-scheduler (Trac #151) | defect microdrop Migrated from Trac | I am getting the following error when running the `pip install -r requirements.txt` file. The problems seems to be intermittent (i.e., it doesn't happen every time), but I was able to reproduce it on a clean repository.
```
Obtaining task-scheduler from git+https://github.com/cfobel/task_scheduler.git@master#egg=task-scheduler-dev (from -r requirements.txt (line 17))
Cloning https://github.com/cfobel/task_scheduler.git (to master) to c:\users\ryan\documents\dev\python\microdrop\src\task-scheduler
Unpacking objects: 100% (30/30), done.
Running setup.py egg_info for package task-scheduler
Traceback (most recent call last):
File "<string>", line 14, in <module>
File "C:\Users\ryan\Documents\dev\python\microdrop\src\task-scheduler\setup.py", line 7, in <module>
version=version.getVersion(),
File "version.py", line 116, in getVersion
raise ValueError('Cannot find the version number')
ValueError: Cannot find the version number
Complete output from command python setup.py egg_info:
Traceback (most recent call last):
File "<string>", line 14, in <module>
File "C:\Users\ryan\Documents\dev\python\microdrop\src\task-scheduler\setup.py", line 7, in <module>
version=version.getVersion(),
File "version.py", line 116, in getVersion
raise ValueError('Cannot find the version number')
ValueError: Cannot find the version number
----------------------------------------
Command python setup.py egg_info failed with error code 1
```
Migrated from http://microfluidics.utoronto.ca/microdrop/ticket/151
```json
{
"status": "closed",
"changetime": "2014-04-17T19:39:01",
"description": "I am getting the following error when running the `pip install -r requirements.txt` file. The problems seems to be intermittent (i.e., it doesn't happen every time), but I was able to reproduce it on a clean repository.\n\n{{{\nObtaining task-scheduler from git+https://github.com/cfobel/task_scheduler.git@master#egg=task-scheduler-dev (from -r requirements.txt (line 17))\n Cloning https://github.com/cfobel/task_scheduler.git (to master) to c:\\users\\ryan\\documents\\dev\\python\\microdrop\\src\\task-scheduler\nUnpacking objects: 100% (30/30), done.\n Running setup.py egg_info for package task-scheduler\n Traceback (most recent call last):\n File \"<string>\", line 14, in <module>\n File \"C:\\Users\\ryan\\Documents\\dev\\python\\microdrop\\src\\task-scheduler\\setup.py\", line 7, in <module>\n version=version.getVersion(),\n File \"version.py\", line 116, in getVersion\n raise ValueError('Cannot find the version number')\n ValueError: Cannot find the version number\n Complete output from command python setup.py egg_info:\n Traceback (most recent call last):\n File \"<string>\", line 14, in <module>\n File \"C:\\Users\\ryan\\Documents\\dev\\python\\microdrop\\src\\task-scheduler\\setup.py\", line 7, in <module>\n version=version.getVersion(),\n File \"version.py\", line 116, in getVersion\n raise ValueError('Cannot find the version number')\nValueError: Cannot find the version number\n\n----------------------------------------\nCommand python setup.py egg_info failed with error code 1\n}}}",
"reporter": "ryan",
"cc": "",
"resolution": "fixed",
"_ts": "1397763541728826",
"component": "microdrop",
"summary": "Problem installing task-scheduler",
"priority": "major",
"keywords": "",
"version": "0.1",
"time": "2014-03-14T02:14:25",
"milestone": "Microdrop 1.0",
"owner": "",
"type": "defect"
}
```
| 1.0 | Problem installing task-scheduler (Trac #151) - I am getting the following error when running the `pip install -r requirements.txt` file. The problems seems to be intermittent (i.e., it doesn't happen every time), but I was able to reproduce it on a clean repository.
```
Obtaining task-scheduler from git+https://github.com/cfobel/task_scheduler.git@master#egg=task-scheduler-dev (from -r requirements.txt (line 17))
Cloning https://github.com/cfobel/task_scheduler.git (to master) to c:\users\ryan\documents\dev\python\microdrop\src\task-scheduler
Unpacking objects: 100% (30/30), done.
Running setup.py egg_info for package task-scheduler
Traceback (most recent call last):
File "<string>", line 14, in <module>
File "C:\Users\ryan\Documents\dev\python\microdrop\src\task-scheduler\setup.py", line 7, in <module>
version=version.getVersion(),
File "version.py", line 116, in getVersion
raise ValueError('Cannot find the version number')
ValueError: Cannot find the version number
Complete output from command python setup.py egg_info:
Traceback (most recent call last):
File "<string>", line 14, in <module>
File "C:\Users\ryan\Documents\dev\python\microdrop\src\task-scheduler\setup.py", line 7, in <module>
version=version.getVersion(),
File "version.py", line 116, in getVersion
raise ValueError('Cannot find the version number')
ValueError: Cannot find the version number
----------------------------------------
Command python setup.py egg_info failed with error code 1
```
Migrated from http://microfluidics.utoronto.ca/microdrop/ticket/151
```json
{
"status": "closed",
"changetime": "2014-04-17T19:39:01",
"description": "I am getting the following error when running the `pip install -r requirements.txt` file. The problems seems to be intermittent (i.e., it doesn't happen every time), but I was able to reproduce it on a clean repository.\n\n{{{\nObtaining task-scheduler from git+https://github.com/cfobel/task_scheduler.git@master#egg=task-scheduler-dev (from -r requirements.txt (line 17))\n Cloning https://github.com/cfobel/task_scheduler.git (to master) to c:\\users\\ryan\\documents\\dev\\python\\microdrop\\src\\task-scheduler\nUnpacking objects: 100% (30/30), done.\n Running setup.py egg_info for package task-scheduler\n Traceback (most recent call last):\n File \"<string>\", line 14, in <module>\n File \"C:\\Users\\ryan\\Documents\\dev\\python\\microdrop\\src\\task-scheduler\\setup.py\", line 7, in <module>\n version=version.getVersion(),\n File \"version.py\", line 116, in getVersion\n raise ValueError('Cannot find the version number')\n ValueError: Cannot find the version number\n Complete output from command python setup.py egg_info:\n Traceback (most recent call last):\n File \"<string>\", line 14, in <module>\n File \"C:\\Users\\ryan\\Documents\\dev\\python\\microdrop\\src\\task-scheduler\\setup.py\", line 7, in <module>\n version=version.getVersion(),\n File \"version.py\", line 116, in getVersion\n raise ValueError('Cannot find the version number')\nValueError: Cannot find the version number\n\n----------------------------------------\nCommand python setup.py egg_info failed with error code 1\n}}}",
"reporter": "ryan",
"cc": "",
"resolution": "fixed",
"_ts": "1397763541728826",
"component": "microdrop",
"summary": "Problem installing task-scheduler",
"priority": "major",
"keywords": "",
"version": "0.1",
"time": "2014-03-14T02:14:25",
"milestone": "Microdrop 1.0",
"owner": "",
"type": "defect"
}
```
| defect | problem installing task scheduler trac i am getting the following error when running the pip install r requirements txt file the problems seems to be intermittent i e it doesn t happen every time but i was able to reproduce it on a clean repository obtaining task scheduler from git from r requirements txt line cloning to master to c users ryan documents dev python microdrop src task scheduler unpacking objects done running setup py egg info for package task scheduler traceback most recent call last file line in file c users ryan documents dev python microdrop src task scheduler setup py line in version version getversion file version py line in getversion raise valueerror cannot find the version number valueerror cannot find the version number complete output from command python setup py egg info traceback most recent call last file line in file c users ryan documents dev python microdrop src task scheduler setup py line in version version getversion file version py line in getversion raise valueerror cannot find the version number valueerror cannot find the version number command python setup py egg info failed with error code migrated from json status closed changetime description i am getting the following error when running the pip install r requirements txt file the problems seems to be intermittent i e it doesn t happen every time but i was able to reproduce it on a clean repository n n nobtaining task scheduler from git from r requirements txt line n cloning to master to c users ryan documents dev python microdrop src task scheduler nunpacking objects done n running setup py egg info for package task scheduler n traceback most recent call last n file line in n file c users ryan documents dev python microdrop src task scheduler setup py line in n version version getversion n file version py line in getversion n raise valueerror cannot find the version number n valueerror cannot find the version number n complete output from command python setup py egg info n traceback most recent call last n file line in n file c users ryan documents dev python microdrop src task scheduler setup py line in n version version getversion n file version py line in getversion n raise valueerror cannot find the version number nvalueerror cannot find the version number n n ncommand python setup py egg info failed with error code n reporter ryan cc resolution fixed ts component microdrop summary problem installing task scheduler priority major keywords version time milestone microdrop owner type defect | 1 |
816,063 | 30,586,863,016 | IssuesEvent | 2023-07-21 14:00:57 | kytos-ng/telemetry_int | https://api.github.com/repos/kytos-ng/telemetry_int | opened | UI: placeholder to refine the UI | priority_low epic_telemetry_int_v1 | The minimal UI to enable INT in a single EVC will be covered on `mef_eline`'s UI https://github.com/kytos-ng/mef_eline/issues/180
But still it's desirable to have UI fully supporting these endpoints:
- `POST v1/evc/enable`
- `POST v1/evc/disable`
- `GET v1/evc`
It still needs refined, but I'll go ahead and capture this on this issue, based on our last planning `2023.2`, it's desirable to have, it's our tentative list, so I'll leave it with priority_low at this time | 1.0 | UI: placeholder to refine the UI - The minimal UI to enable INT in a single EVC will be covered on `mef_eline`'s UI https://github.com/kytos-ng/mef_eline/issues/180
But still it's desirable to have UI fully supporting these endpoints:
- `POST v1/evc/enable`
- `POST v1/evc/disable`
- `GET v1/evc`
It still needs refined, but I'll go ahead and capture this on this issue, based on our last planning `2023.2`, it's desirable to have, it's our tentative list, so I'll leave it with priority_low at this time | non_defect | ui placeholder to refine the ui the minimal ui to enable int in a single evc will be covered on mef eline s ui but still it s desirable to have ui fully supporting these endpoints post evc enable post evc disable get evc it still needs refined but i ll go ahead and capture this on this issue based on our last planning it s desirable to have it s our tentative list so i ll leave it with priority low at this time | 0 |
1,767 | 2,571,135,844 | IssuesEvent | 2015-02-10 14:52:05 | pydata/pandas | https://api.github.com/repos/pydata/pandas | closed | Groupby behaves differently when using levels and list of column keys | API Design Groupby | When grouping by several levels of a MultiIndex, groupby evaltuates all possible combinations of the groupby keys. When grouping by column name, it only evaluates what exist in the DataFrame. Also, this behavior does not exist in 0.14.1, but does in all final releases from 0.15.0 on.
This may be a new feature, not a bug, but I couldn't find anything in the [docs](http://pandas.pydata.org/pandas-docs/stable/generated/pandas.DataFrame.groupby.html#pandas.DataFrame.groupby), open or closed issues, etc. (closest was Issue #8138). If this is the intended behavior, it would be nice to have in the docs.
```python
import pandas as pd
import numpy as np
df = pd.DataFrame(np.arange(12).reshape(-1, 3))
df.index = pd.MultiIndex.from_tuples([(1, 1), (1, 2), (3, 4), (5, 6)])
idx_names = ['x', 'y']
df.index.names = idx_names
# Adds nan's for (x, y) combinations that aren't in the data
by_levels = df.groupby(level=idx_names).mean()
# This does not add missing combinations of the groupby keys
by_columns = df.reset_index().groupby(idx_names).mean()
print by_levels
print by_columns
# This passes in 0.14.1, but not >=0.15.0 final
assert by_levels.equals(by_columns)
```
INSTALLED VERSIONS
------------------
commit: None
python: 2.7.7.final.0
python-bits: 64
OS: Windows
OS-release: 7
machine: AMD64
processor: Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
byteorder: little
LC_ALL: None
LANG: None
pandas: 0.15.2
nose: 1.3.4
Cython: 0.20.1
numpy: 1.9.1
scipy: 0.15.1
statsmodels: 0.7.0.dev-161a0f8
IPython: 2.3.0
sphinx: 1.2.2
patsy: 0.3.0
dateutil: 1.5
pytz: 2014.9
bottleneck: 0.8.0
tables: 3.1.1
numexpr: 2.3.1
matplotlib: 1.4.2
openpyxl: 1.8.5
xlrd: 0.9.3
xlwt: 0.7.5
xlsxwriter: 0.5.5
lxml: 3.3.5
bs4: 4.3.1
html5lib: None
httplib2: None
apiclient: None
rpy2: None
sqlalchemy: 0.9.4
pymysql: None
psycopg2: None | 1.0 | Groupby behaves differently when using levels and list of column keys - When grouping by several levels of a MultiIndex, groupby evaltuates all possible combinations of the groupby keys. When grouping by column name, it only evaluates what exist in the DataFrame. Also, this behavior does not exist in 0.14.1, but does in all final releases from 0.15.0 on.
This may be a new feature, not a bug, but I couldn't find anything in the [docs](http://pandas.pydata.org/pandas-docs/stable/generated/pandas.DataFrame.groupby.html#pandas.DataFrame.groupby), open or closed issues, etc. (closest was Issue #8138). If this is the intended behavior, it would be nice to have in the docs.
```python
import pandas as pd
import numpy as np
df = pd.DataFrame(np.arange(12).reshape(-1, 3))
df.index = pd.MultiIndex.from_tuples([(1, 1), (1, 2), (3, 4), (5, 6)])
idx_names = ['x', 'y']
df.index.names = idx_names
# Adds nan's for (x, y) combinations that aren't in the data
by_levels = df.groupby(level=idx_names).mean()
# This does not add missing combinations of the groupby keys
by_columns = df.reset_index().groupby(idx_names).mean()
print by_levels
print by_columns
# This passes in 0.14.1, but not >=0.15.0 final
assert by_levels.equals(by_columns)
```
INSTALLED VERSIONS
------------------
commit: None
python: 2.7.7.final.0
python-bits: 64
OS: Windows
OS-release: 7
machine: AMD64
processor: Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
byteorder: little
LC_ALL: None
LANG: None
pandas: 0.15.2
nose: 1.3.4
Cython: 0.20.1
numpy: 1.9.1
scipy: 0.15.1
statsmodels: 0.7.0.dev-161a0f8
IPython: 2.3.0
sphinx: 1.2.2
patsy: 0.3.0
dateutil: 1.5
pytz: 2014.9
bottleneck: 0.8.0
tables: 3.1.1
numexpr: 2.3.1
matplotlib: 1.4.2
openpyxl: 1.8.5
xlrd: 0.9.3
xlwt: 0.7.5
xlsxwriter: 0.5.5
lxml: 3.3.5
bs4: 4.3.1
html5lib: None
httplib2: None
apiclient: None
rpy2: None
sqlalchemy: 0.9.4
pymysql: None
psycopg2: None | non_defect | groupby behaves differently when using levels and list of column keys when grouping by several levels of a multiindex groupby evaltuates all possible combinations of the groupby keys when grouping by column name it only evaluates what exist in the dataframe also this behavior does not exist in but does in all final releases from on this may be a new feature not a bug but i couldn t find anything in the open or closed issues etc closest was issue if this is the intended behavior it would be nice to have in the docs python import pandas as pd import numpy as np df pd dataframe np arange reshape df index pd multiindex from tuples idx names df index names idx names adds nan s for x y combinations that aren t in the data by levels df groupby level idx names mean this does not add missing combinations of the groupby keys by columns df reset index groupby idx names mean print by levels print by columns this passes in but not final assert by levels equals by columns installed versions commit none python final python bits os windows os release machine processor family model stepping genuineintel byteorder little lc all none lang none pandas nose cython numpy scipy statsmodels dev ipython sphinx patsy dateutil pytz bottleneck tables numexpr matplotlib openpyxl xlrd xlwt xlsxwriter lxml none none apiclient none none sqlalchemy pymysql none none | 0 |
48,277 | 13,067,594,027 | IssuesEvent | 2020-07-31 00:57:50 | icecube-trac/tix2 | https://api.github.com/repos/icecube-trac/tix2 | closed | [spline-reco] Bug leads to segmentation violation in case of an 'anomalously large charge' (Trac #2119) | Migrated from Trac analysis defect | In `I3SplineRecoLikelihood::KS0Limit(int npulses, int level)` an array is accessed with `ks_test[npulses - 1]` but does not check if `npulses < 1`.
I saw a couple of events that call this function with `npulses = 0` but apparently it didn't break the execution. However, I found a case with
```text
I3HitOm.h:111 WARNING: got anomalously large charge=1.64923e+10 PE in OM at (x,y,z)=(429.8,351.0,-344.9)
```
that leads to an overflow of `totalcharge` in `I3SplineRecoLikelihood::GetApprovedCharge`. Finally, `npulses` is small enough (e.g. `npulses = -2147483648`) to cause a segmentation violation.
http://code.icecube.wisc.edu/projects/icecube/browser/IceCube/projects/spline-reco/trunk/private/spline-reco/I3SplineRecoLikelihood.cxx?rev=157082#L867
This bug blocks processing of a pass2 file.
Migrated from https://code.icecube.wisc.edu/ticket/2119
```json
{
"status": "closed",
"changetime": "2019-02-13T14:14:55",
"description": "In `I3SplineRecoLikelihood::KS0Limit(int npulses, int level)` an array is accessed with `ks_test[npulses - 1]` but does not check if `npulses < 1`.\n\nI saw a couple of events that call this function with `npulses = 0` but apparently it didn't break the execution. However, I found a case with\n\n{{{\nI3HitOm.h:111 WARNING: got anomalously large charge=1.64923e+10 PE in OM at (x,y,z)=(429.8,351.0,-344.9)\n}}}\n\nthat leads to an overflow of `totalcharge` in `I3SplineRecoLikelihood::GetApprovedCharge`. Finally, `npulses` is small enough (e.g. `npulses = -2147483648`) to cause a segmentation violation.\n\nhttp://code.icecube.wisc.edu/projects/icecube/browser/IceCube/projects/spline-reco/trunk/private/spline-reco/I3SplineRecoLikelihood.cxx?rev=157082#L867\n\nThis bug blocks processing of a pass2 file.",
"reporter": "joertlin",
"cc": "",
"resolution": "fixed",
"_ts": "1550067295757382",
"component": "analysis",
"summary": "[spline-reco] Bug leads to segmentation violation in case of an 'anomalously large charge'",
"priority": "critical",
"keywords": "",
"time": "2017-12-01T21:22:27",
"milestone": "",
"owner": "kjmeagher",
"type": "defect"
}
```
| 1.0 | [spline-reco] Bug leads to segmentation violation in case of an 'anomalously large charge' (Trac #2119) - In `I3SplineRecoLikelihood::KS0Limit(int npulses, int level)` an array is accessed with `ks_test[npulses - 1]` but does not check if `npulses < 1`.
I saw a couple of events that call this function with `npulses = 0` but apparently it didn't break the execution. However, I found a case with
```text
I3HitOm.h:111 WARNING: got anomalously large charge=1.64923e+10 PE in OM at (x,y,z)=(429.8,351.0,-344.9)
```
that leads to an overflow of `totalcharge` in `I3SplineRecoLikelihood::GetApprovedCharge`. Finally, `npulses` is small enough (e.g. `npulses = -2147483648`) to cause a segmentation violation.
http://code.icecube.wisc.edu/projects/icecube/browser/IceCube/projects/spline-reco/trunk/private/spline-reco/I3SplineRecoLikelihood.cxx?rev=157082#L867
This bug blocks processing of a pass2 file.
Migrated from https://code.icecube.wisc.edu/ticket/2119
```json
{
"status": "closed",
"changetime": "2019-02-13T14:14:55",
"description": "In `I3SplineRecoLikelihood::KS0Limit(int npulses, int level)` an array is accessed with `ks_test[npulses - 1]` but does not check if `npulses < 1`.\n\nI saw a couple of events that call this function with `npulses = 0` but apparently it didn't break the execution. However, I found a case with\n\n{{{\nI3HitOm.h:111 WARNING: got anomalously large charge=1.64923e+10 PE in OM at (x,y,z)=(429.8,351.0,-344.9)\n}}}\n\nthat leads to an overflow of `totalcharge` in `I3SplineRecoLikelihood::GetApprovedCharge`. Finally, `npulses` is small enough (e.g. `npulses = -2147483648`) to cause a segmentation violation.\n\nhttp://code.icecube.wisc.edu/projects/icecube/browser/IceCube/projects/spline-reco/trunk/private/spline-reco/I3SplineRecoLikelihood.cxx?rev=157082#L867\n\nThis bug blocks processing of a pass2 file.",
"reporter": "joertlin",
"cc": "",
"resolution": "fixed",
"_ts": "1550067295757382",
"component": "analysis",
"summary": "[spline-reco] Bug leads to segmentation violation in case of an 'anomalously large charge'",
"priority": "critical",
"keywords": "",
"time": "2017-12-01T21:22:27",
"milestone": "",
"owner": "kjmeagher",
"type": "defect"
}
```
| defect | bug leads to segmentation violation in case of an anomalously large charge trac in int npulses int level an array is accessed with ks test but does not check if npulses i saw a couple of events that call this function with npulses but apparently it didn t break the execution however i found a case with text h warning got anomalously large charge pe in om at x y z that leads to an overflow of totalcharge in getapprovedcharge finally npulses is small enough e g npulses to cause a segmentation violation this bug blocks processing of a file migrated from json status closed changetime description in int npulses int level an array is accessed with ks test but does not check if npulses n ni saw a couple of events that call this function with npulses but apparently it didn t break the execution however i found a case with n n h warning got anomalously large charge pe in om at x y z n n nthat leads to an overflow of totalcharge in getapprovedcharge finally npulses is small enough e g npulses to cause a segmentation violation n n bug blocks processing of a file reporter joertlin cc resolution fixed ts component analysis summary bug leads to segmentation violation in case of an anomalously large charge priority critical keywords time milestone owner kjmeagher type defect | 1 |
418,953 | 28,133,424,673 | IssuesEvent | 2023-04-01 04:58:39 | Lekuini/Tp1_grupal_Prog3 | https://api.github.com/repos/Lekuini/Tp1_grupal_Prog3 | closed | Ejercicio 1 - Aporte 1 | documentation | 1 - Creación del formulario "Ejercicio 1".
2 - Modificación de las propiedades nombre y texto.
3 - Agregar el código dentro del evento Click del botón "ejercicio 1" del formulario principal.
4 - Agregar todos elementos que componen el formulario "Nombres" | 1.0 | Ejercicio 1 - Aporte 1 - 1 - Creación del formulario "Ejercicio 1".
2 - Modificación de las propiedades nombre y texto.
3 - Agregar el código dentro del evento Click del botón "ejercicio 1" del formulario principal.
4 - Agregar todos elementos que componen el formulario "Nombres" | non_defect | ejercicio aporte creación del formulario ejercicio modificación de las propiedades nombre y texto agregar el código dentro del evento click del botón ejercicio del formulario principal agregar todos elementos que componen el formulario nombres | 0 |
97,059 | 20,158,279,907 | IssuesEvent | 2022-02-09 18:36:04 | sourcegraph/sourcegraph | https://api.github.com/repos/sourcegraph/sourcegraph | closed | Focus search input issues when using keyboard navigation | bug team/growth-and-integrations vscode-extension | Issue 1: search input not adding cursor when using keybindings to navigate back and forth between tabs.
#### Expected behavior:
When keyboard navigating back and forth between other files back to Sourcegraph search file, users expect that hitting tab once in the Sourcegraph search will highlight input field and add cursor to edit.
#### Actual behavior:
Taken from [internal feedback](https://sourcegraph.slack.com/archives/C02E3HHDZ98/p1643662302885139). When user keyboard navigates to a different VS Code file then returns to the Sourcegraph search file (using keyboard nav), hitting tab once on the Sourcegraph search file highlights the search input field, but does not include a cursor for a user to edit. | 1.0 | Focus search input issues when using keyboard navigation - Issue 1: search input not adding cursor when using keybindings to navigate back and forth between tabs.
#### Expected behavior:
When keyboard navigating back and forth between other files back to Sourcegraph search file, users expect that hitting tab once in the Sourcegraph search will highlight input field and add cursor to edit.
#### Actual behavior:
Taken from [internal feedback](https://sourcegraph.slack.com/archives/C02E3HHDZ98/p1643662302885139). When user keyboard navigates to a different VS Code file then returns to the Sourcegraph search file (using keyboard nav), hitting tab once on the Sourcegraph search file highlights the search input field, but does not include a cursor for a user to edit. | non_defect | focus search input issues when using keyboard navigation issue search input not adding cursor when using keybindings to navigate back and forth between tabs expected behavior when keyboard navigating back and forth between other files back to sourcegraph search file users expect that hitting tab once in the sourcegraph search will highlight input field and add cursor to edit actual behavior taken from when user keyboard navigates to a different vs code file then returns to the sourcegraph search file using keyboard nav hitting tab once on the sourcegraph search file highlights the search input field but does not include a cursor for a user to edit | 0 |
64,901 | 18,957,074,134 | IssuesEvent | 2021-11-18 21:41:10 | matrix-org/synapse | https://api.github.com/repos/matrix-org/synapse | opened | Incremental `/sync` and `/transactions query events differently | z-application-service z-sync T-Defect | *As discovered in https://github.com/matrix-org/synapse/pull/11265#discussion_r745413607*
---
`/sync` looks for `stream_ordering` but excludes all `outliers`.
https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/storage/databases/main/stream.py#L519-L527
Whereas `/transactions`(Application service API) only cares about `stream_ordering`.
https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/storage/databases/main/appservice.py#L358-L368
The behavior of these two endpoints should probably return and push the same events.
Here is the history behind why we added `AND not outlier` to the incremental sync endpoint, "Don't return outliers when we get recent events for rooms.", https://github.com/matrix-org/synapse/commit/1505055334ecff6516c0b388efe4c5759e59fad0 but it doesn't explain the why or which interaction creates `outlier` events that aren't `backfilled`.
## What does the spec say?
For `/transactions`, the spec doesn't distinguish which events a homeserver should and shouldn't push, https://spec.matrix.org/v1.1/application-service-api/#put_matrixappv1transactionstxnid
For [`/sync`](https://spec.matrix.org/v1.1/client-server-api/#get_matrixclientv3sync), there is also nothing so clear cut but it's obvious using the `since` pagination query parameter that it should return anything after which equates to `stream_ordering` in Synapse land.
## Potential solutions
### Exclude `outliers` in both
Perhaps we should exclude `outliers` in `/transactions` so they both just match?
@richvdh had some critique about this approach though:
> the outlier flag seems like a poor way to decide whether we should push this data. (Yes, outliers shouldn't be sent over `/transactions`, but there are probably many other events which shouldn't be sent).
>
> `FederationEventHandler._process_received_pdu` has a `backfilled` parameter (see [`synapse/handlers/federation_event.py#L945`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/handlers/federation_event.py#L945)), whose purpose is slightly unclear, but I *think* one of its jobs is this sort of thing. Maybe we should use similar logic to that, somehow?
>
> [*-- @richvdh, https://github.com/matrix-org/synapse/pull/11265#discussion_r746523400*](https://github.com/matrix-org/synapse/pull/11265#discussion_r746523400)
But for `/transactions`, we can't tell whether the event was `backfilled`. The only indication is that the `stream_ordering` would be negative which is what the `/transactions` code already takes into account.
### Only exclude `backfilled` events
This means only relying on `stream_ordering`.
Then any interaction creating `outliers` that we don't want to appear down `/sync`/`/transactions`, should be updated to be marked as `backfilled`.
## Dev notes
### `/sync` stack trace
- [`SyncRestServlet.on_GET`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/rest/client/sync.py#L113)
- [`wait_for_sync_for_user`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/handlers/sync.py#L299)
- [`_wait_for_sync_for_user`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/handlers/sync.py#L329)
- [`current_sync_for_user`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/handlers/sync.py#L399)
- [`generate_sync_result`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/handlers/sync.py#L1039)
- [`_generate_sync_entry_for_rooms`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/handlers/sync.py#L1455)
- [`_get_rooms_changed`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/handlers/sync.py#L1614)
- [`get_room_events_stream_for_rooms`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/storage/databases/main/stream.py#L409)
- [`get_room_events_stream_for_room`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/storage/databases/main/stream.py#L478-L527)
### `/transactions` stack trace
- [`notify_interested_services`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/handlers/appservice.py#L66-L87)
- [`_notify_interested_services`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/handlers/appservice.py#L90-L135)
- [`get_new_events_for_appservice`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/storage/databases/main/appservice.py#L353-L368)
- [`submit_event_for_as`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/handlers/appservice.py#L133-L135)
[`submit_event_for_as`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/appservice/scheduler.py#L94-L95) ->
- [`enqueue_event`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/appservice/scheduler.py#L129-L131)
- [`_send_request`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/appservice/scheduler.py#L137-L157)
- `appservice.scheduler.send`
- [`create_appservice_txn`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/appservice/scheduler.py#L196-L201)
- [`AppServiceTransaction.send`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/appservice/__init__.py#L338)
- [`push_bulk`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/appservice/api.py#L202)
- [`/transactions`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/appservice/api.py#L220)
| 1.0 | Incremental `/sync` and `/transactions query events differently - *As discovered in https://github.com/matrix-org/synapse/pull/11265#discussion_r745413607*
---
`/sync` looks for `stream_ordering` but excludes all `outliers`.
https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/storage/databases/main/stream.py#L519-L527
Whereas `/transactions`(Application service API) only cares about `stream_ordering`.
https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/storage/databases/main/appservice.py#L358-L368
The behavior of these two endpoints should probably return and push the same events.
Here is the history behind why we added `AND not outlier` to the incremental sync endpoint, "Don't return outliers when we get recent events for rooms.", https://github.com/matrix-org/synapse/commit/1505055334ecff6516c0b388efe4c5759e59fad0 but it doesn't explain the why or which interaction creates `outlier` events that aren't `backfilled`.
## What does the spec say?
For `/transactions`, the spec doesn't distinguish which events a homeserver should and shouldn't push, https://spec.matrix.org/v1.1/application-service-api/#put_matrixappv1transactionstxnid
For [`/sync`](https://spec.matrix.org/v1.1/client-server-api/#get_matrixclientv3sync), there is also nothing so clear cut but it's obvious using the `since` pagination query parameter that it should return anything after which equates to `stream_ordering` in Synapse land.
## Potential solutions
### Exclude `outliers` in both
Perhaps we should exclude `outliers` in `/transactions` so they both just match?
@richvdh had some critique about this approach though:
> the outlier flag seems like a poor way to decide whether we should push this data. (Yes, outliers shouldn't be sent over `/transactions`, but there are probably many other events which shouldn't be sent).
>
> `FederationEventHandler._process_received_pdu` has a `backfilled` parameter (see [`synapse/handlers/federation_event.py#L945`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/handlers/federation_event.py#L945)), whose purpose is slightly unclear, but I *think* one of its jobs is this sort of thing. Maybe we should use similar logic to that, somehow?
>
> [*-- @richvdh, https://github.com/matrix-org/synapse/pull/11265#discussion_r746523400*](https://github.com/matrix-org/synapse/pull/11265#discussion_r746523400)
But for `/transactions`, we can't tell whether the event was `backfilled`. The only indication is that the `stream_ordering` would be negative which is what the `/transactions` code already takes into account.
### Only exclude `backfilled` events
This means only relying on `stream_ordering`.
Then any interaction creating `outliers` that we don't want to appear down `/sync`/`/transactions`, should be updated to be marked as `backfilled`.
## Dev notes
### `/sync` stack trace
- [`SyncRestServlet.on_GET`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/rest/client/sync.py#L113)
- [`wait_for_sync_for_user`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/handlers/sync.py#L299)
- [`_wait_for_sync_for_user`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/handlers/sync.py#L329)
- [`current_sync_for_user`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/handlers/sync.py#L399)
- [`generate_sync_result`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/handlers/sync.py#L1039)
- [`_generate_sync_entry_for_rooms`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/handlers/sync.py#L1455)
- [`_get_rooms_changed`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/handlers/sync.py#L1614)
- [`get_room_events_stream_for_rooms`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/storage/databases/main/stream.py#L409)
- [`get_room_events_stream_for_room`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/storage/databases/main/stream.py#L478-L527)
### `/transactions` stack trace
- [`notify_interested_services`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/handlers/appservice.py#L66-L87)
- [`_notify_interested_services`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/handlers/appservice.py#L90-L135)
- [`get_new_events_for_appservice`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/storage/databases/main/appservice.py#L353-L368)
- [`submit_event_for_as`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/handlers/appservice.py#L133-L135)
[`submit_event_for_as`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/appservice/scheduler.py#L94-L95) ->
- [`enqueue_event`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/appservice/scheduler.py#L129-L131)
- [`_send_request`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/appservice/scheduler.py#L137-L157)
- `appservice.scheduler.send`
- [`create_appservice_txn`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/appservice/scheduler.py#L196-L201)
- [`AppServiceTransaction.send`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/appservice/__init__.py#L338)
- [`push_bulk`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/appservice/api.py#L202)
- [`/transactions`](https://github.com/matrix-org/synapse/blob/b09d90cac9179f84024d4cb3ab4574480c1fd1df/synapse/appservice/api.py#L220)
| defect | incremental sync and transactions query events differently as discovered in sync looks for stream ordering but excludes all outliers whereas transactions application service api only cares about stream ordering the behavior of these two endpoints should probably return and push the same events here is the history behind why we added and not outlier to the incremental sync endpoint don t return outliers when we get recent events for rooms but it doesn t explain the why or which interaction creates outlier events that aren t backfilled what does the spec say for transactions the spec doesn t distinguish which events a homeserver should and shouldn t push for there is also nothing so clear cut but it s obvious using the since pagination query parameter that it should return anything after which equates to stream ordering in synapse land potential solutions exclude outliers in both perhaps we should exclude outliers in transactions so they both just match richvdh had some critique about this approach though the outlier flag seems like a poor way to decide whether we should push this data yes outliers shouldn t be sent over transactions but there are probably many other events which shouldn t be sent federationeventhandler process received pdu has a backfilled parameter see whose purpose is slightly unclear but i think one of its jobs is this sort of thing maybe we should use similar logic to that somehow but for transactions we can t tell whether the event was backfilled the only indication is that the stream ordering would be negative which is what the transactions code already takes into account only exclude backfilled events this means only relying on stream ordering then any interaction creating outliers that we don t want to appear down sync transactions should be updated to be marked as backfilled dev notes sync stack trace transactions stack trace appservice scheduler send | 1 |
30,656 | 6,218,141,313 | IssuesEvent | 2017-07-08 21:53:29 | codenautas/taller-simple | https://api.github.com/repos/codenautas/taller-simple | closed | Alguien tiene que controlar antes de despacharlas que las URL recibidas sean válidas | auto-migrated Priority-Medium Type-Defect | ```
para que no pidan por ejemplo agregar una entidad que no existe (o que no está
permitidas)
```
Original issue reported on code.google.com by `RaquelZS...@gmail.com` on 2 Oct 2014 at 3:58
| 1.0 | Alguien tiene que controlar antes de despacharlas que las URL recibidas sean válidas - ```
para que no pidan por ejemplo agregar una entidad que no existe (o que no está
permitidas)
```
Original issue reported on code.google.com by `RaquelZS...@gmail.com` on 2 Oct 2014 at 3:58
| defect | alguien tiene que controlar antes de despacharlas que las url recibidas sean válidas para que no pidan por ejemplo agregar una entidad que no existe o que no está permitidas original issue reported on code google com by raquelzs gmail com on oct at | 1 |
29,256 | 5,630,025,132 | IssuesEvent | 2017-04-05 11:03:14 | buildo/react-components | https://api.github.com/repos/buildo/react-components | closed | Dropdown: no style for focus | breaking defect waiting for merge | ## description
Border-color should change when the dropdown is focused
## how to reproduce
- focus on a dropdown
## specs
- Add a new variable: `$border-color-focused` (with default value `$waterBlue`) and use it when needed
## misc
{optional: other useful info}
| 1.0 | Dropdown: no style for focus - ## description
Border-color should change when the dropdown is focused
## how to reproduce
- focus on a dropdown
## specs
- Add a new variable: `$border-color-focused` (with default value `$waterBlue`) and use it when needed
## misc
{optional: other useful info}
| defect | dropdown no style for focus description border color should change when the dropdown is focused how to reproduce focus on a dropdown specs add a new variable border color focused with default value waterblue and use it when needed misc optional other useful info | 1 |
416,718 | 12,150,820,629 | IssuesEvent | 2020-04-24 18:42:24 | TheCodeXTeam/Kandahar-IHS | https://api.github.com/repos/TheCodeXTeam/Kandahar-IHS | closed | CSS sizes need fix | Effort: 2 For: UI Priority: Low Status: Completed Type: Bug | # Environment
- The width of the browser 1280px and height is 619px.
- All the sizes need to be change due to new design.
# Steps to reproduce
See CSS file.
# Expected behavior
Consistency in design.
# Actual behavior
Inconsistent design. | 1.0 | CSS sizes need fix - # Environment
- The width of the browser 1280px and height is 619px.
- All the sizes need to be change due to new design.
# Steps to reproduce
See CSS file.
# Expected behavior
Consistency in design.
# Actual behavior
Inconsistent design. | non_defect | css sizes need fix environment the width of the browser and height is all the sizes need to be change due to new design steps to reproduce see css file expected behavior consistency in design actual behavior inconsistent design | 0 |
279,863 | 30,761,176,389 | IssuesEvent | 2023-07-29 18:17:37 | hinoshiba/news | https://api.github.com/repos/hinoshiba/news | closed | [SecurityWeek] CardioComm Takes Systems Offline Following Cyberattack | SecurityWeek Stale |
Canadian medical software provider CardioComm has taken systems offline to contain a cyberattack.
The post [CardioComm Takes Systems Offline Following Cyberattack](https://www.securityweek.com/cardiocomm-takes-systems-offline-following-cyberattack/) appeared first on [SecurityWeek](https://www.securityweek.com).
<https://www.securityweek.com/cardiocomm-takes-systems-offline-following-cyberattack/>
| True | [SecurityWeek] CardioComm Takes Systems Offline Following Cyberattack -
Canadian medical software provider CardioComm has taken systems offline to contain a cyberattack.
The post [CardioComm Takes Systems Offline Following Cyberattack](https://www.securityweek.com/cardiocomm-takes-systems-offline-following-cyberattack/) appeared first on [SecurityWeek](https://www.securityweek.com).
<https://www.securityweek.com/cardiocomm-takes-systems-offline-following-cyberattack/>
| non_defect | cardiocomm takes systems offline following cyberattack canadian medical software provider cardiocomm has taken systems offline to contain a cyberattack the post appeared first on | 0 |
158,925 | 24,919,326,578 | IssuesEvent | 2022-10-30 19:20:26 | nextcloud/server | https://api.github.com/repos/nextcloud/server | closed | [Bug]: Menu elements not display block | bug design good first issue | ### ⚠️ This issue respects the following points: ⚠️
- [X] This is a **bug**, not a question or a configuration/webserver/proxy issue.
- [X] This issue is **not** already reported on Github _(I've searched it)_.
- [X] Nextcloud Server **is** up to date. See [Maintenance and Release Schedule](https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule) for supported versions.
- [X] Nextcloud Server **is** running on 64bit capable CPU, PHP and OS.
- [X] I agree to follow Nextcloud's [Code of Conduct](https://nextcloud.com/contribute/code-of-conduct/).
### Bug description
Menu items not display block.
See animation:
### Steps to reproduce
1. open the menu of a file
2. the entries not 100% width
### Expected behavior
full width is clickable for a user
### Installation method
Community Manual installation with Archive
### Operating system
Debian/Ubuntu
### PHP engine version
PHP 8.1
### Web server
Apache (supported)
### Database engine version
MariaDB
### Is this bug present after an update or on a fresh install?
Updated to a major version (ex. 22.2.3 to 23.0.1)
### Are you using the Nextcloud Server Encryption module?
Encryption is Enabled
### What user-backends are you using?
- [ ] Default user-backend _(database)_
- [X] LDAP/ Active Directory
- [ ] SSO - SAML
- [ ] Other
### Configuration report
_No response_
### List of activated Apps
```shell
default
```
### Nextcloud Signing status
_No response_
### Nextcloud Logs
_No response_
### Additional info
_No response_ | 1.0 | [Bug]: Menu elements not display block - ### ⚠️ This issue respects the following points: ⚠️
- [X] This is a **bug**, not a question or a configuration/webserver/proxy issue.
- [X] This issue is **not** already reported on Github _(I've searched it)_.
- [X] Nextcloud Server **is** up to date. See [Maintenance and Release Schedule](https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule) for supported versions.
- [X] Nextcloud Server **is** running on 64bit capable CPU, PHP and OS.
- [X] I agree to follow Nextcloud's [Code of Conduct](https://nextcloud.com/contribute/code-of-conduct/).
### Bug description
Menu items not display block.
See animation:
### Steps to reproduce
1. open the menu of a file
2. the entries not 100% width
### Expected behavior
full width is clickable for a user
### Installation method
Community Manual installation with Archive
### Operating system
Debian/Ubuntu
### PHP engine version
PHP 8.1
### Web server
Apache (supported)
### Database engine version
MariaDB
### Is this bug present after an update or on a fresh install?
Updated to a major version (ex. 22.2.3 to 23.0.1)
### Are you using the Nextcloud Server Encryption module?
Encryption is Enabled
### What user-backends are you using?
- [ ] Default user-backend _(database)_
- [X] LDAP/ Active Directory
- [ ] SSO - SAML
- [ ] Other
### Configuration report
_No response_
### List of activated Apps
```shell
default
```
### Nextcloud Signing status
_No response_
### Nextcloud Logs
_No response_
### Additional info
_No response_ | non_defect | menu elements not display block ⚠️ this issue respects the following points ⚠️ this is a bug not a question or a configuration webserver proxy issue this issue is not already reported on github i ve searched it nextcloud server is up to date see for supported versions nextcloud server is running on capable cpu php and os i agree to follow nextcloud s bug description menu items not display block see animation steps to reproduce open the menu of a file the entries not width expected behavior full width is clickable for a user installation method community manual installation with archive operating system debian ubuntu php engine version php web server apache supported database engine version mariadb is this bug present after an update or on a fresh install updated to a major version ex to are you using the nextcloud server encryption module encryption is enabled what user backends are you using default user backend database ldap active directory sso saml other configuration report no response list of activated apps shell default nextcloud signing status no response nextcloud logs no response additional info no response | 0 |
79,765 | 7,724,396,302 | IssuesEvent | 2018-05-24 14:58:57 | test4gloirin/m | https://api.github.com/repos/test4gloirin/m | closed | 0000046:
add controller and backend tests for role managemnt | Feature Request Unittests | **Reported by pschuele on 2 May 2008 18:20**
- complete tests for Admin_Controller
- complete tests for Tinebase_Acl_Roles
| 1.0 | 0000046:
add controller and backend tests for role managemnt - **Reported by pschuele on 2 May 2008 18:20**
- complete tests for Admin_Controller
- complete tests for Tinebase_Acl_Roles
| non_defect | add controller and backend tests for role managemnt reported by pschuele on may complete tests for admin controller complete tests for tinebase acl roles | 0 |
216,833 | 16,671,368,804 | IssuesEvent | 2021-06-07 11:18:58 | p-s-vishnu/cassava_app | https://api.github.com/repos/p-s-vishnu/cassava_app | closed | Update readme | documentation | - [ ] Deployment links / guides
- [ ] How to run app
- [x] streamlit link [](https://share.streamlit.io/yourGitHubName/yourRepo/yourApp/)
- [x] gif demos
right now i can only think of these if you have anything else add in comments @VpkPrasanna | 1.0 | Update readme - - [ ] Deployment links / guides
- [ ] How to run app
- [x] streamlit link [](https://share.streamlit.io/yourGitHubName/yourRepo/yourApp/)
- [x] gif demos
right now i can only think of these if you have anything else add in comments @VpkPrasanna | non_defect | update readme deployment links guides how to run app streamlit link gif demos right now i can only think of these if you have anything else add in comments vpkprasanna | 0 |
243,417 | 18,714,015,451 | IssuesEvent | 2021-11-03 00:19:53 | apac-mcm-aiops-asset/mcm-aiops-gitops | https://api.github.com/repos/apac-mcm-aiops-asset/mcm-aiops-gitops | opened | Tidy up repositories and re-name to more meaningful names | documentation enhancement help wanted | Currently the repositories follow the same standard as the cloud-native-toolkit/multi-tenancy-gitops format.
mcm-aiops-gitops - Main Repository which is used to bootstrap and enable/disable the objects within the Hub Cluster
mcm-aiops-gitops-infra - This repository determines the Infrastructure components (e.g. machinesets, storage, infra nodes etc) within the Hub Cluster
mcm-aiops-gitops-services - This repository determines the services deployed into the Hub Cluster (MCM, RHACM, Turbonomics etc)
mcm-aiops-gitops-apps - This repository covers the Clusters imported, created and infrastructure components within MCM and RHACM. It also includes Cloud Paks.
I believe we should rename the repositories to represent the asset created (maybe ztp-for-multi-cloud as an example, as well as separate the Cluster and Cloud Paks into their own repositories.
Further discussion should be held and a decision made. | 1.0 | Tidy up repositories and re-name to more meaningful names - Currently the repositories follow the same standard as the cloud-native-toolkit/multi-tenancy-gitops format.
mcm-aiops-gitops - Main Repository which is used to bootstrap and enable/disable the objects within the Hub Cluster
mcm-aiops-gitops-infra - This repository determines the Infrastructure components (e.g. machinesets, storage, infra nodes etc) within the Hub Cluster
mcm-aiops-gitops-services - This repository determines the services deployed into the Hub Cluster (MCM, RHACM, Turbonomics etc)
mcm-aiops-gitops-apps - This repository covers the Clusters imported, created and infrastructure components within MCM and RHACM. It also includes Cloud Paks.
I believe we should rename the repositories to represent the asset created (maybe ztp-for-multi-cloud as an example, as well as separate the Cluster and Cloud Paks into their own repositories.
Further discussion should be held and a decision made. | non_defect | tidy up repositories and re name to more meaningful names currently the repositories follow the same standard as the cloud native toolkit multi tenancy gitops format mcm aiops gitops main repository which is used to bootstrap and enable disable the objects within the hub cluster mcm aiops gitops infra this repository determines the infrastructure components e g machinesets storage infra nodes etc within the hub cluster mcm aiops gitops services this repository determines the services deployed into the hub cluster mcm rhacm turbonomics etc mcm aiops gitops apps this repository covers the clusters imported created and infrastructure components within mcm and rhacm it also includes cloud paks i believe we should rename the repositories to represent the asset created maybe ztp for multi cloud as an example as well as separate the cluster and cloud paks into their own repositories further discussion should be held and a decision made | 0 |
69,664 | 22,599,142,492 | IssuesEvent | 2022-06-29 07:32:50 | vector-im/element-web | https://api.github.com/repos/vector-im/element-web | closed | Notification dot on ThreadsList in compact modern=group layout is not aligned to timestamp | T-Defect | ### Steps to reproduce
1. Enable compact modern layout
2. Open a room with unread threads
### Outcome
#### What did you expect?
The dot should be aligned to the timestamp.
#### What happened instead?
It is not aligned to the timestamp.
### Operating system
Debian
### Browser information
Firefox ESR 91
### URL for webapp
localhost
### Application version
develop branch
### Homeserver
_No response_
### Will you send logs?
No | 1.0 | Notification dot on ThreadsList in compact modern=group layout is not aligned to timestamp - ### Steps to reproduce
1. Enable compact modern layout
2. Open a room with unread threads
### Outcome
#### What did you expect?
The dot should be aligned to the timestamp.
#### What happened instead?
It is not aligned to the timestamp.
### Operating system
Debian
### Browser information
Firefox ESR 91
### URL for webapp
localhost
### Application version
develop branch
### Homeserver
_No response_
### Will you send logs?
No | defect | notification dot on threadslist in compact modern group layout is not aligned to timestamp steps to reproduce enable compact modern layout open a room with unread threads outcome what did you expect the dot should be aligned to the timestamp what happened instead it is not aligned to the timestamp operating system debian browser information firefox esr url for webapp localhost application version develop branch homeserver no response will you send logs no | 1 |
12,630 | 9,703,230,125 | IssuesEvent | 2019-05-27 10:48:03 | astrolabsoftware/fink-broker | https://api.github.com/repos/astrolabsoftware/fink-broker | closed | Reintroduce tool to monitor the stream | missing services | **Describe the issue**
In PR #162, the `monitor` service has been removed. It was valuable for test purposes, and we should re-introduce something similar.
Action item: add a new service called `checkstream` whose function is to monitor the stream of alerts (measure rates). | 1.0 | Reintroduce tool to monitor the stream - **Describe the issue**
In PR #162, the `monitor` service has been removed. It was valuable for test purposes, and we should re-introduce something similar.
Action item: add a new service called `checkstream` whose function is to monitor the stream of alerts (measure rates). | non_defect | reintroduce tool to monitor the stream describe the issue in pr the monitor service has been removed it was valuable for test purposes and we should re introduce something similar action item add a new service called checkstream whose function is to monitor the stream of alerts measure rates | 0 |
160,575 | 20,110,368,344 | IssuesEvent | 2022-02-07 14:34:38 | shiriivtsan/NodeGoat | https://api.github.com/repos/shiriivtsan/NodeGoat | opened | grunt-npm-install-0.3.1.tgz: 29 vulnerabilities (highest severity is: 9.8) | security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>grunt-npm-install-0.3.1.tgz</b></p></summary>
<p></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/npm/node_modules/fstream/package.json</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/shiriivtsan/NodeGoat/commit/98fe87a557b23eb3b41abbc356778283c8f192d8">98fe87a557b23eb3b41abbc356778283c8f192d8</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2021-3918](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3918) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | json-schema-0.2.3.tgz | Transitive | N/A | ❌ |
| [CVE-2018-16492](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-16492) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | extend-3.0.0.tgz | Transitive | N/A | ❌ |
| [CVE-2021-23807](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23807) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | jsonpointer-4.0.0.tgz | Transitive | N/A | ❌ |
| [WS-2020-0344](https://github.com/mafintosh/is-my-json-valid/commit/3419563687df463b4ca709a2b46be8e15d6a2b3d) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | is-my-json-valid-2.15.0.tgz | Transitive | N/A | ❌ |
| [WS-2020-0345](https://github.com/janl/node-jsonpointer/commit/234e3437019c6c07537ed2ad1e03b3e132b85e34) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.2 | jsonpointer-4.0.0.tgz | Transitive | N/A | ❌ |
| [CVE-2019-16776](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-16776) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.1 | npm-3.10.10.tgz | Transitive | N/A | ❌ |
| [CVE-2021-32804](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-32804) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.1 | tar-2.2.1.tgz | Transitive | N/A | ❌ |
| [CVE-2018-20834](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20834) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | tar-2.2.1.tgz | Transitive | N/A | ❌ |
| [CVE-2017-15010](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-15010) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | tough-cookie-2.3.1.tgz | Transitive | N/A | ❌ |
| [WS-2020-0180](https://github.com/npm/npm-user-validate/commit/c8a87dac1a4cc6988b5418f30411a8669bef204e) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | npm-user-validate-0.1.5.tgz | Transitive | N/A | ❌ |
| [WS-2018-0069](https://github.com/mafintosh/is-my-json-valid/commit/b3051b277f7caa08cd2edc6f74f50aeda65d2976) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | is-my-json-valid-2.15.0.tgz | Transitive | N/A | ❌ |
| [CVE-2017-1000048](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-1000048) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | qs-6.2.1.tgz | Transitive | N/A | ❌ |
| [CVE-2020-7754](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7754) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | npm-user-validate-0.1.5.tgz | Transitive | N/A | ❌ |
| [CVE-2018-3737](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3737) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | sshpk-1.10.1.tgz | Transitive | N/A | ❌ |
| [CVE-2017-18077](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-18077) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | brace-expansion-1.1.6.tgz | Transitive | N/A | ❌ |
| [WS-2020-0342](https://github.com/mafintosh/is-my-json-valid/commit/c3fc04fc455d40e9b29537f8e2c73a28ce106edb) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | is-my-json-valid-2.15.0.tgz | Transitive | N/A | ❌ |
| [CVE-2019-13173](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-13173) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | fstream-1.0.10.tgz | Transitive | N/A | ❌ |
| [CVE-2020-7788](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7788) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.3 | ini-1.3.4.tgz | Transitive | N/A | ❌ |
| [CVE-2018-21270](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-21270) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | stringstream-0.0.5.tgz | Transitive | N/A | ❌ |
| [CVE-2020-8244](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8244) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | bl-1.1.2.tgz | Transitive | N/A | ❌ |
| [CVE-2019-16775](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-16775) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | npm-3.10.10.tgz | Transitive | N/A | ❌ |
| [CVE-2019-16777](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-16777) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | npm-3.10.10.tgz | Transitive | N/A | ❌ |
| [CVE-2020-7598](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7598) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.6 | minimist-0.0.8.tgz | Transitive | N/A | ❌ |
| [CVE-2017-16032](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16032) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.5 | brace-expansion-1.1.6.tgz | Transitive | N/A | ❌ |
| [CVE-2021-23362](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23362) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | hosted-git-info-2.1.5.tgz | Transitive | N/A | ❌ |
| [CVE-2018-1107](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1107) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | is-my-json-valid-2.15.0.tgz | Transitive | N/A | ❌ |
| [WS-2018-0103](https://hackerone.com/reports/321670) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 4.8 | stringstream-0.0.5.tgz | Transitive | N/A | ❌ |
| [CVE-2020-15095](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15095) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 4.4 | npm-3.10.10.tgz | Transitive | N/A | ❌ |
| [CVE-2017-18869](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-18869) | <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low | 2.5 | chownr-1.0.1.tgz | Transitive | N/A | ❌ |
## Details
> Partial details (11 vulnerabilities) are displayed below due to a content size limitation in GitHub. To view information on the remaining vulnerabilities, navigate to the WhiteSource Application.<br>
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-3918</summary>
### Vulnerable Library - <b>json-schema-0.2.3.tgz</b></p>
<p>JSON Schema validation and specifications</p>
<p>Library home page: <a href="https://registry.npmjs.org/json-schema/-/json-schema-0.2.3.tgz">https://registry.npmjs.org/json-schema/-/json-schema-0.2.3.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/json-schema/package.json,/node_modules/npm/node_modules/request/node_modules/http-signature/node_modules/jsprim/node_modules/json-schema/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- npm-3.10.10.tgz
- request-2.75.0.tgz
- http-signature-1.1.1.tgz
- jsprim-1.3.1.tgz
- :x: **json-schema-0.2.3.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shiriivtsan/NodeGoat/commit/98fe87a557b23eb3b41abbc356778283c8f192d8">98fe87a557b23eb3b41abbc356778283c8f192d8</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
json-schema is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
<p>Publish Date: 2021-11-13
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3918>CVE-2021-3918</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-3918">https://nvd.nist.gov/vuln/detail/CVE-2021-3918</a></p>
<p>Release Date: 2021-11-13</p>
<p>Fix Resolution: json-schema - 0.4.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2018-16492</summary>
### Vulnerable Library - <b>extend-3.0.0.tgz</b></p>
<p>Port of jQuery.extend for node.js and the browser</p>
<p>Library home page: <a href="https://registry.npmjs.org/extend/-/extend-3.0.0.tgz">https://registry.npmjs.org/extend/-/extend-3.0.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/npm/node_modules/request/node_modules/extend/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- npm-3.10.10.tgz
- request-2.75.0.tgz
- :x: **extend-3.0.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shiriivtsan/NodeGoat/commit/98fe87a557b23eb3b41abbc356778283c8f192d8">98fe87a557b23eb3b41abbc356778283c8f192d8</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A prototype pollution vulnerability was found in module extend <2.0.2, ~<3.0.2 that allows an attacker to inject arbitrary properties onto Object.prototype.
<p>Publish Date: 2019-02-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-16492>CVE-2018-16492</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://hackerone.com/reports/381185">https://hackerone.com/reports/381185</a></p>
<p>Release Date: 2019-02-01</p>
<p>Fix Resolution: extend - v3.0.2,v2.0.2</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-23807</summary>
### Vulnerable Library - <b>jsonpointer-4.0.0.tgz</b></p>
<p>Simple JSON Addressing.</p>
<p>Library home page: <a href="https://registry.npmjs.org/jsonpointer/-/jsonpointer-4.0.0.tgz">https://registry.npmjs.org/jsonpointer/-/jsonpointer-4.0.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/npm/node_modules/request/node_modules/har-validator/node_modules/is-my-json-valid/node_modules/jsonpointer/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- npm-3.10.10.tgz
- request-2.75.0.tgz
- har-validator-2.0.6.tgz
- is-my-json-valid-2.15.0.tgz
- :x: **jsonpointer-4.0.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shiriivtsan/NodeGoat/commit/98fe87a557b23eb3b41abbc356778283c8f192d8">98fe87a557b23eb3b41abbc356778283c8f192d8</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
This affects the package jsonpointer before 5.0.0. A type confusion vulnerability can lead to a bypass of a previous Prototype Pollution fix when the pointer components are arrays.
<p>Publish Date: 2021-11-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23807>CVE-2021-23807</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23807">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23807</a></p>
<p>Release Date: 2021-11-03</p>
<p>Fix Resolution: jsonpointer - 5.0.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> WS-2020-0344</summary>
### Vulnerable Library - <b>is-my-json-valid-2.15.0.tgz</b></p>
<p>A JSONSchema validator that uses code generation to be extremely fast</p>
<p>Library home page: <a href="https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.15.0.tgz">https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.15.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/npm/node_modules/request/node_modules/har-validator/node_modules/is-my-json-valid/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- npm-3.10.10.tgz
- request-2.75.0.tgz
- har-validator-2.0.6.tgz
- :x: **is-my-json-valid-2.15.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shiriivtsan/NodeGoat/commit/98fe87a557b23eb3b41abbc356778283c8f192d8">98fe87a557b23eb3b41abbc356778283c8f192d8</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Arbitrary Code Execution vulnerability was found in is-my-json-valid before 2.20.3 via the fromatName function.
<p>Publish Date: 2020-06-09
<p>URL: <a href=https://github.com/mafintosh/is-my-json-valid/commit/3419563687df463b4ca709a2b46be8e15d6a2b3d>WS-2020-0344</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/mafintosh/is-my-json-valid/commit/c3fc04fc455d40e9b29537f8e2c73a28ce106edb">https://github.com/mafintosh/is-my-json-valid/commit/c3fc04fc455d40e9b29537f8e2c73a28ce106edb</a></p>
<p>Release Date: 2020-06-09</p>
<p>Fix Resolution: is-my-json-valid - 2.20.3</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> WS-2020-0345</summary>
### Vulnerable Library - <b>jsonpointer-4.0.0.tgz</b></p>
<p>Simple JSON Addressing.</p>
<p>Library home page: <a href="https://registry.npmjs.org/jsonpointer/-/jsonpointer-4.0.0.tgz">https://registry.npmjs.org/jsonpointer/-/jsonpointer-4.0.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/npm/node_modules/request/node_modules/har-validator/node_modules/is-my-json-valid/node_modules/jsonpointer/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- npm-3.10.10.tgz
- request-2.75.0.tgz
- har-validator-2.0.6.tgz
- is-my-json-valid-2.15.0.tgz
- :x: **jsonpointer-4.0.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shiriivtsan/NodeGoat/commit/98fe87a557b23eb3b41abbc356778283c8f192d8">98fe87a557b23eb3b41abbc356778283c8f192d8</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Prototype Pollution vulnerability was found in jsonpointer before 4.1.0 via the set function.
<p>Publish Date: 2020-07-03
<p>URL: <a href=https://github.com/janl/node-jsonpointer/commit/234e3437019c6c07537ed2ad1e03b3e132b85e34>WS-2020-0345</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.2</b>)
<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: Low
- Availability Impact: High
</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://github.com/janl/node-jsonpointer/releases/tag/v4.1.0">https://github.com/janl/node-jsonpointer/releases/tag/v4.1.0</a></p>
<p>Release Date: 2020-07-03</p>
<p>Fix Resolution: jsonpointer - 4.1.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-16776</summary>
### Vulnerable Library - <b>npm-3.10.10.tgz</b></p>
<p>a package manager for JavaScript</p>
<p>Library home page: <a href="https://registry.npmjs.org/npm/-/npm-3.10.10.tgz">https://registry.npmjs.org/npm/-/npm-3.10.10.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/npm/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- :x: **npm-3.10.10.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shiriivtsan/NodeGoat/commit/98fe87a557b23eb3b41abbc356778283c8f192d8">98fe87a557b23eb3b41abbc356778283c8f192d8</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Versions of the npm CLI prior to 6.13.3 are vulnerable to an Arbitrary File Write. It fails to prevent access to folders outside of the intended node_modules folder through the bin field. A properly constructed entry in the package.json bin field would allow a package publisher to modify and/or gain access to arbitrary files on a user's system when the package is installed. This behavior is still possible through install scripts. This vulnerability bypasses a user using the --ignore-scripts install option.
<p>Publish Date: 2019-12-13
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-16776>CVE-2019-16776</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://blog.npmjs.org/post/189618601100/binary-planting-with-the-npm-cli">https://blog.npmjs.org/post/189618601100/binary-planting-with-the-npm-cli</a></p>
<p>Release Date: 2020-10-07</p>
<p>Fix Resolution: npm - 6.13.3;yarn - 1.21.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-32804</summary>
### Vulnerable Library - <b>tar-2.2.1.tgz</b></p>
<p>tar for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-2.2.1.tgz">https://registry.npmjs.org/tar/-/tar-2.2.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/npm/node_modules/tar/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- npm-3.10.10.tgz
- :x: **tar-2.2.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shiriivtsan/NodeGoat/commit/98fe87a557b23eb3b41abbc356778283c8f192d8">98fe87a557b23eb3b41abbc356778283c8f192d8</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The npm package "tar" (aka node-tar) before versions 6.1.1, 5.0.6, 4.4.14, and 3.3.2 has a arbitrary File Creation/Overwrite vulnerability due to insufficient absolute path sanitization. node-tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the `preservePaths` flag is not set to `true`. This is achieved by stripping the absolute path root from any absolute file paths contained in a tar file. For example `/home/user/.bashrc` would turn into `home/user/.bashrc`. This logic was insufficient when file paths contained repeated path roots such as `////home/user/.bashrc`. `node-tar` would only strip a single path root from such paths. When given an absolute file path with repeating path roots, the resulting path (e.g. `///home/user/.bashrc`) would still resolve to an absolute path, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.2, 4.4.14, 5.0.6 and 6.1.1. Users may work around this vulnerability without upgrading by creating a custom `onentry` method which sanitizes the `entry.path` or a `filter` method which removes entries with absolute paths. See referenced GitHub Advisory for details. Be aware of CVE-2021-32803 which fixes a similar bug in later versions of tar.
<p>Publish Date: 2021-08-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-32804>CVE-2021-32804</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/npm/node-tar/security/advisories/GHSA-3jfq-g458-7qm9">https://github.com/npm/node-tar/security/advisories/GHSA-3jfq-g458-7qm9</a></p>
<p>Release Date: 2021-08-03</p>
<p>Fix Resolution: tar - 3.2.2, 4.4.14, 5.0.6, 6.1.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2018-20834</summary>
### Vulnerable Library - <b>tar-2.2.1.tgz</b></p>
<p>tar for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-2.2.1.tgz">https://registry.npmjs.org/tar/-/tar-2.2.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/npm/node_modules/tar/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- npm-3.10.10.tgz
- :x: **tar-2.2.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shiriivtsan/NodeGoat/commit/98fe87a557b23eb3b41abbc356778283c8f192d8">98fe87a557b23eb3b41abbc356778283c8f192d8</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A vulnerability was found in node-tar before version 4.4.2 (excluding version 2.2.2). An Arbitrary File Overwrite issue exists when extracting a tarball containing a hardlink to a file that already exists on the system, in conjunction with a later plain file with the same name as the hardlink. This plain file content replaces the existing file content. A patch has been applied to node-tar v2.2.2).
<p>Publish Date: 2019-04-30
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20834>CVE-2018-20834</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16082">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16082</a></p>
<p>Release Date: 2019-04-30</p>
<p>Fix Resolution: 2.2.2,4.4.2</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2017-15010</summary>
### Vulnerable Library - <b>tough-cookie-2.3.1.tgz</b></p>
<p>RFC6265 Cookies and Cookie Jar for node.js</p>
<p>Library home page: <a href="https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.3.1.tgz">https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.3.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/npm/node_modules/request/node_modules/tough-cookie/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- npm-3.10.10.tgz
- request-2.75.0.tgz
- :x: **tough-cookie-2.3.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shiriivtsan/NodeGoat/commit/98fe87a557b23eb3b41abbc356778283c8f192d8">98fe87a557b23eb3b41abbc356778283c8f192d8</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A ReDoS (regular expression denial of service) flaw was found in the tough-cookie module before 2.3.3 for Node.js. An attacker that is able to make an HTTP request using a specially crafted cookie may cause the application to consume an excessive amount of CPU.
<p>Publish Date: 2017-10-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-15010>CVE-2017-15010</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-15010">https://nvd.nist.gov/vuln/detail/CVE-2017-15010</a></p>
<p>Release Date: 2017-10-04</p>
<p>Fix Resolution: 2.3.3</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> WS-2020-0180</summary>
### Vulnerable Library - <b>npm-user-validate-0.1.5.tgz</b></p>
<p>User validations for npm</p>
<p>Library home page: <a href="https://registry.npmjs.org/npm-user-validate/-/npm-user-validate-0.1.5.tgz">https://registry.npmjs.org/npm-user-validate/-/npm-user-validate-0.1.5.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/npm/node_modules/npm-user-validate/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- npm-3.10.10.tgz
- :x: **npm-user-validate-0.1.5.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shiriivtsan/NodeGoat/commit/98fe87a557b23eb3b41abbc356778283c8f192d8">98fe87a557b23eb3b41abbc356778283c8f192d8</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The package npm-user-validate prior to version 1.0.1 is vulnerable to REDoS. The regex that validates a user's email took exponentially longer to process input strings that begin with the '@' character.
<p>Publish Date: 2020-10-16
<p>URL: <a href=https://github.com/npm/npm-user-validate/commit/c8a87dac1a4cc6988b5418f30411a8669bef204e>WS-2020-0180</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-xgh6-85xh-479p">https://github.com/advisories/GHSA-xgh6-85xh-479p</a></p>
<p>Release Date: 2020-10-16</p>
<p>Fix Resolution: 1.0.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> WS-2018-0069</summary>
### Vulnerable Library - <b>is-my-json-valid-2.15.0.tgz</b></p>
<p>A JSONSchema validator that uses code generation to be extremely fast</p>
<p>Library home page: <a href="https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.15.0.tgz">https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.15.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/npm/node_modules/request/node_modules/har-validator/node_modules/is-my-json-valid/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- npm-3.10.10.tgz
- request-2.75.0.tgz
- har-validator-2.0.6.tgz
- :x: **is-my-json-valid-2.15.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shiriivtsan/NodeGoat/commit/98fe87a557b23eb3b41abbc356778283c8f192d8">98fe87a557b23eb3b41abbc356778283c8f192d8</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Version of is-my-json-valid before 1.4.1 or 2.17.2 are vulnerable to regular expression denial of service (ReDoS) via the email validation function.
<p>Publish Date: 2018-02-14
<p>URL: <a href=https://github.com/mafintosh/is-my-json-valid/commit/b3051b277f7caa08cd2edc6f74f50aeda65d2976>WS-2018-0069</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nodesecurity.io/advisories/572">https://nodesecurity.io/advisories/572</a></p>
<p>Release Date: 2018-02-14</p>
<p>Fix Resolution: 1.4.1</p>
</p>
<p></p>
</details>
<!-- <REMEDIATE>[{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"json-schema","packageVersion":"0.2.3","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;request:2.75.0;http-signature:1.1.1;jsprim:1.3.1;json-schema:0.2.3","isMinimumFixVersionAvailable":true,"minimumFixVersion":"json-schema - 0.4.0","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-3918","vulnerabilityDetails":"json-schema is vulnerable to Improperly Controlled Modification of Object Prototype Attributes (\u0027Prototype Pollution\u0027)","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3918","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"extend","packageVersion":"3.0.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;request:2.75.0;extend:3.0.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"extend - v3.0.2,v2.0.2","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-16492","vulnerabilityDetails":"A prototype pollution vulnerability was found in module extend \u003c2.0.2, ~\u003c3.0.2 that allows an attacker to inject arbitrary properties onto Object.prototype.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-16492","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"jsonpointer","packageVersion":"4.0.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;request:2.75.0;har-validator:2.0.6;is-my-json-valid:2.15.0;jsonpointer:4.0.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"jsonpointer - 5.0.0","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-23807","vulnerabilityDetails":"This affects the package jsonpointer before 5.0.0. A type confusion vulnerability can lead to a bypass of a previous Prototype Pollution fix when the pointer components are arrays.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23807","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"is-my-json-valid","packageVersion":"2.15.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;request:2.75.0;har-validator:2.0.6;is-my-json-valid:2.15.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"is-my-json-valid - 2.20.3","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2020-0344","vulnerabilityDetails":"Arbitrary Code Execution vulnerability was found in is-my-json-valid before 2.20.3 via the fromatName function.","vulnerabilityUrl":"https://github.com/mafintosh/is-my-json-valid/commit/3419563687df463b4ca709a2b46be8e15d6a2b3d","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"jsonpointer","packageVersion":"4.0.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;request:2.75.0;har-validator:2.0.6;is-my-json-valid:2.15.0;jsonpointer:4.0.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"jsonpointer - 4.1.0","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2020-0345","vulnerabilityDetails":"Prototype Pollution vulnerability was found in jsonpointer before 4.1.0 via the set function.","vulnerabilityUrl":"https://github.com/janl/node-jsonpointer/commit/234e3437019c6c07537ed2ad1e03b3e132b85e34","cvss3Severity":"high","cvss3Score":"8.2","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"Low"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"npm","packageVersion":"3.10.10","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10","isMinimumFixVersionAvailable":true,"minimumFixVersion":"npm - 6.13.3;yarn - 1.21.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2019-16776","vulnerabilityDetails":"Versions of the npm CLI prior to 6.13.3 are vulnerable to an Arbitrary File Write. It fails to prevent access to folders outside of the intended node_modules folder through the bin field. A properly constructed entry in the package.json bin field would allow a package publisher to modify and/or gain access to arbitrary files on a user\u0027s system when the package is installed. This behavior is still possible through install scripts. This vulnerability bypasses a user using the --ignore-scripts install option.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-16776","cvss3Severity":"high","cvss3Score":"8.1","cvss3Metrics":{"A":"None","AC":"Low","PR":"Low","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"tar","packageVersion":"2.2.1","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;tar:2.2.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"tar - 3.2.2, 4.4.14, 5.0.6, 6.1.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-32804","vulnerabilityDetails":"The npm package \"tar\" (aka node-tar) before versions 6.1.1, 5.0.6, 4.4.14, and 3.3.2 has a arbitrary File Creation/Overwrite vulnerability due to insufficient absolute path sanitization. node-tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the `preservePaths` flag is not set to `true`. This is achieved by stripping the absolute path root from any absolute file paths contained in a tar file. For example `/home/user/.bashrc` would turn into `home/user/.bashrc`. This logic was insufficient when file paths contained repeated path roots such as `////home/user/.bashrc`. `node-tar` would only strip a single path root from such paths. When given an absolute file path with repeating path roots, the resulting path (e.g. `///home/user/.bashrc`) would still resolve to an absolute path, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.2, 4.4.14, 5.0.6 and 6.1.1. Users may work around this vulnerability without upgrading by creating a custom `onentry` method which sanitizes the `entry.path` or a `filter` method which removes entries with absolute paths. See referenced GitHub Advisory for details. Be aware of CVE-2021-32803 which fixes a similar bug in later versions of tar.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-32804","cvss3Severity":"high","cvss3Score":"8.1","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"Required","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"tar","packageVersion":"2.2.1","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;tar:2.2.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"2.2.2,4.4.2","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-20834","vulnerabilityDetails":"A vulnerability was found in node-tar before version 4.4.2 (excluding version 2.2.2). An Arbitrary File Overwrite issue exists when extracting a tarball containing a hardlink to a file that already exists on the system, in conjunction with a later plain file with the same name as the hardlink. This plain file content replaces the existing file content. A patch has been applied to node-tar v2.2.2).","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20834","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"tough-cookie","packageVersion":"2.3.1","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;request:2.75.0;tough-cookie:2.3.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"2.3.3","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2017-15010","vulnerabilityDetails":"A ReDoS (regular expression denial of service) flaw was found in the tough-cookie module before 2.3.3 for Node.js. An attacker that is able to make an HTTP request using a specially crafted cookie may cause the application to consume an excessive amount of CPU.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-15010","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"npm-user-validate","packageVersion":"0.1.5","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;npm-user-validate:0.1.5","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.0.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2020-0180","vulnerabilityDetails":"The package npm-user-validate prior to version 1.0.1 is vulnerable to REDoS. The regex that validates a user\u0027s email took exponentially longer to process input strings that begin with the \u0027@\u0027 character.","vulnerabilityUrl":"https://github.com/npm/npm-user-validate/commit/c8a87dac1a4cc6988b5418f30411a8669bef204e","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"is-my-json-valid","packageVersion":"2.15.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;request:2.75.0;har-validator:2.0.6;is-my-json-valid:2.15.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.4.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2018-0069","vulnerabilityDetails":"Version of is-my-json-valid before 1.4.1 or 2.17.2 are vulnerable to regular expression denial of service (ReDoS) via the email validation function.","vulnerabilityUrl":"https://github.com/mafintosh/is-my-json-valid/commit/b3051b277f7caa08cd2edc6f74f50aeda65d2976","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"qs","packageVersion":"6.2.1","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;request:2.75.0;qs:6.2.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"qs - 6.0.4,6.1.2,6.2.3,6.3.2","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2017-1000048","vulnerabilityDetails":"the web framework using ljharb\u0027s qs module older than v6.3.2, v6.2.3, v6.1.2, and v6.0.4 is vulnerable to a DoS. A malicious user can send a evil request to cause the web framework crash.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-1000048","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"npm-user-validate","packageVersion":"0.1.5","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;npm-user-validate:0.1.5","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.0.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-7754","vulnerabilityDetails":"This affects the package npm-user-validate before 1.0.1. The regex that validates user emails took exponentially longer to process long input strings beginning with @ characters.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7754","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"sshpk","packageVersion":"1.10.1","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;request:2.75.0;http-signature:1.1.1;sshpk:1.10.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.13.2","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-3737","vulnerabilityDetails":"sshpk is vulnerable to ReDoS when parsing crafted invalid public keys.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3737","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"brace-expansion","packageVersion":"1.1.6","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;read-package-json:2.0.4;glob:6.0.4;minimatch:3.0.3;brace-expansion:1.1.6","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.1.7","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2017-18077","vulnerabilityDetails":"index.js in brace-expansion before 1.1.7 is vulnerable to Regular Expression Denial of Service (ReDoS) attacks, as demonstrated by an expand argument containing many comma characters.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-18077","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"is-my-json-valid","packageVersion":"2.15.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;request:2.75.0;har-validator:2.0.6;is-my-json-valid:2.15.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"is-my-json-valid - 2.20.2","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2020-0342","vulnerabilityDetails":"Regular Expression Denial of Service (ReDoS) vulnerability was found in is-my-json-valid before 2.20.2 via the style format.","vulnerabilityUrl":"https://github.com/mafintosh/is-my-json-valid/commit/c3fc04fc455d40e9b29537f8e2c73a28ce106edb","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"fstream","packageVersion":"1.0.10","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;fstream:1.0.10","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.0.12","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2019-13173","vulnerabilityDetails":"fstream before 1.0.12 is vulnerable to Arbitrary File Overwrite. Extracting tarballs containing a hardlink to a file that already exists in the system, and a file that matches the hardlink, will overwrite the system\u0027s file with the contents of the extracted file. The fstream.DirWriter() function is vulnerable.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-13173","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"ini","packageVersion":"1.3.4","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;ini:1.3.4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"v1.3.6","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-7788","vulnerabilityDetails":"This affects the package ini before 1.3.6. If an attacker submits a malicious INI file to an application that parses it with ini.parse, they will pollute the prototype on the application. This can be exploited further depending on the context.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7788","cvss3Severity":"high","cvss3Score":"7.3","cvss3Metrics":{"A":"Low","AC":"Low","PR":"None","S":"Unchanged","C":"Low","UI":"None","AV":"Network","I":"Low"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"stringstream","packageVersion":"0.0.5","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;request:2.75.0;stringstream:0.0.5","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.0.6","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-21270","vulnerabilityDetails":"Versions less than 0.0.6 of the Node.js stringstream module are vulnerable to an out-of-bounds read because of allocation of uninitialized buffers when a number is passed in the input stream (when using Node.js 4.x).","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-21270","cvss3Severity":"medium","cvss3Score":"6.5","cvss3Metrics":{"A":"High","AC":"High","PR":"None","S":"Unchanged","C":"Low","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"bl","packageVersion":"1.1.2","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;request:2.75.0;bl:1.1.2","isMinimumFixVersionAvailable":true,"minimumFixVersion":"bl - 1.2.3,2.2.1,3.0.1,4.0.3","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-8244","vulnerabilityDetails":"A buffer over-read vulnerability exists in bl \u003c4.0.3, \u003c3.0.1, \u003c2.2.1, and \u003c1.2.3 which could allow an attacker to supply user input (even typed) that if it ends up in consume() argument and can become negative, the BufferList state can be corrupted, tricking it into exposing uninitialized memory via regular .slice() calls.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8244","cvss3Severity":"medium","cvss3Score":"6.5","cvss3Metrics":{"A":"Low","AC":"Low","PR":"None","S":"Unchanged","C":"Low","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"npm","packageVersion":"3.10.10","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10","isMinimumFixVersionAvailable":true,"minimumFixVersion":"npm - 6.13.3;yarn - 1.21.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2019-16775","vulnerabilityDetails":"Versions of the npm CLI prior to 6.13.3 are vulnerable to an Arbitrary File Write. It is possible for packages to create symlinks to files outside of thenode_modules folder through the bin field upon installation. A properly constructed entry in the package.json bin field would allow a package publisher to create a symlink pointing to arbitrary files on a user\u0027s system when the package is installed. This behavior is still possible through install scripts. This vulnerability bypasses a user using the --ignore-scripts install option.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-16775","cvss3Severity":"medium","cvss3Score":"6.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"Low","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"npm","packageVersion":"3.10.10","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10","isMinimumFixVersionAvailable":true,"minimumFixVersion":"npm - 6.13.4","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2019-16777","vulnerabilityDetails":"Versions of the npm CLI prior to 6.13.4 are vulnerable to an Arbitrary File Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a serve binary, any subsequent installs of packages that also create a serve binary would overwrite the previous serve binary. This behavior is still allowed in local installations and also through install scripts. This vulnerability bypasses a user using the --ignore-scripts install option.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-16777","cvss3Severity":"medium","cvss3Score":"6.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"Low","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"minimist","packageVersion":"0.0.8","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;mkdirp:0.5.1;minimist:0.0.8","isMinimumFixVersionAvailable":true,"minimumFixVersion":"minimist - 0.2.1,1.2.3","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-7598","vulnerabilityDetails":"minimist before 1.2.2 could be tricked into adding or modifying properties of Object.prototype using a \"constructor\" or \"__proto__\" payload.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7598","cvss3Severity":"medium","cvss3Score":"5.6","cvss3Metrics":{"A":"Low","AC":"High","PR":"None","S":"Unchanged","C":"Low","UI":"None","AV":"Network","I":"Low"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"brace-expansion","packageVersion":"1.1.6","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;read-package-json:2.0.4;glob:6.0.4;minimatch:3.0.3;brace-expansion:1.1.6","isMinimumFixVersionAvailable":true,"minimumFixVersion":"v1.1.7","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2017-16032","vulnerabilityDetails":"brace-expansion before 1.1.7 are vulnerable to a regular expression denial of service.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16032","cvss3Severity":"medium","cvss3Score":"5.5","cvss3Metrics":{"A":"High","AC":"High","PR":"Low","S":"Unchanged","C":"Low","UI":"Required","AV":"Local","I":"Low"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"hosted-git-info","packageVersion":"2.1.5","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;hosted-git-info:2.1.5","isMinimumFixVersionAvailable":true,"minimumFixVersion":"hosted-git-info - 2.8.9,3.0.8","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-23362","vulnerabilityDetails":"The package hosted-git-info before 3.0.8 are vulnerable to Regular Expression Denial of Service (ReDoS) via regular expression shortcutMatch in the fromUrl function in index.js. The affected regular expression exhibits polynomial worst-case time complexity.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23362","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"Low","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"is-my-json-valid","packageVersion":"2.15.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;request:2.75.0;har-validator:2.0.6;is-my-json-valid:2.15.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"is-my-json-valid - 1.4.1, 2.17.2","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-1107","vulnerabilityDetails":"It was discovered that the is-my-json-valid JavaScript library used an inefficient regular expression to validate JSON fields defined to have email format. A specially crafted JSON file could cause it to consume an excessive amount of CPU time when validated.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1107","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"Low","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"stringstream","packageVersion":"0.0.5","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;request:2.75.0;stringstream:0.0.5","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.0.6","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2018-0103","vulnerabilityDetails":"All versions of stringstream are vulnerable to out-of-bounds read as it allocates uninitialized Buffers when number is passed in input stream on Node.js 4.x and below.","vulnerabilityUrl":"https://hackerone.com/reports/321670","cvss3Severity":"medium","cvss3Score":"4.8","cvss3Metrics":{"A":"Low","AC":"High","PR":"None","S":"Unchanged","C":"Low","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"npm","packageVersion":"3.10.10","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10","isMinimumFixVersionAvailable":true,"minimumFixVersion":"npm - 6.14.6","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-15095","vulnerabilityDetails":"Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like \"\u003cprotocol\u003e://[\u003cuser\u003e[:\u003cpassword\u003e]@]\u003chostname\u003e[:\u003cport\u003e][:][/]\u003cpath\u003e\". The password value is not redacted and is printed to stdout and also to any generated log files.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15095","cvss3Severity":"medium","cvss3Score":"4.4","cvss3Metrics":{"A":"None","AC":"High","PR":"Low","S":"Unchanged","C":"High","UI":"Required","AV":"Local","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"chownr","packageVersion":"1.0.1","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;chownr:1.0.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.1.0","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2017-18869","vulnerabilityDetails":"A TOCTOU issue in the chownr package before 1.1.0 for Node.js 10.10 could allow a local attacker to trick it into descending into unintended directories via symlink attacks.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-18869","cvss3Severity":"low","cvss3Score":"2.5","cvss3Metrics":{"A":"None","AC":"High","PR":"Low","S":"Unchanged","C":"None","UI":"None","AV":"Local","I":"Low"},"extraData":{}}]</REMEDIATE> --> | True | grunt-npm-install-0.3.1.tgz: 29 vulnerabilities (highest severity is: 9.8) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>grunt-npm-install-0.3.1.tgz</b></p></summary>
<p></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/npm/node_modules/fstream/package.json</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/shiriivtsan/NodeGoat/commit/98fe87a557b23eb3b41abbc356778283c8f192d8">98fe87a557b23eb3b41abbc356778283c8f192d8</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2021-3918](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3918) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | json-schema-0.2.3.tgz | Transitive | N/A | ❌ |
| [CVE-2018-16492](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-16492) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | extend-3.0.0.tgz | Transitive | N/A | ❌ |
| [CVE-2021-23807](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23807) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | jsonpointer-4.0.0.tgz | Transitive | N/A | ❌ |
| [WS-2020-0344](https://github.com/mafintosh/is-my-json-valid/commit/3419563687df463b4ca709a2b46be8e15d6a2b3d) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | is-my-json-valid-2.15.0.tgz | Transitive | N/A | ❌ |
| [WS-2020-0345](https://github.com/janl/node-jsonpointer/commit/234e3437019c6c07537ed2ad1e03b3e132b85e34) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.2 | jsonpointer-4.0.0.tgz | Transitive | N/A | ❌ |
| [CVE-2019-16776](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-16776) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.1 | npm-3.10.10.tgz | Transitive | N/A | ❌ |
| [CVE-2021-32804](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-32804) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.1 | tar-2.2.1.tgz | Transitive | N/A | ❌ |
| [CVE-2018-20834](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20834) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | tar-2.2.1.tgz | Transitive | N/A | ❌ |
| [CVE-2017-15010](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-15010) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | tough-cookie-2.3.1.tgz | Transitive | N/A | ❌ |
| [WS-2020-0180](https://github.com/npm/npm-user-validate/commit/c8a87dac1a4cc6988b5418f30411a8669bef204e) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | npm-user-validate-0.1.5.tgz | Transitive | N/A | ❌ |
| [WS-2018-0069](https://github.com/mafintosh/is-my-json-valid/commit/b3051b277f7caa08cd2edc6f74f50aeda65d2976) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | is-my-json-valid-2.15.0.tgz | Transitive | N/A | ❌ |
| [CVE-2017-1000048](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-1000048) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | qs-6.2.1.tgz | Transitive | N/A | ❌ |
| [CVE-2020-7754](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7754) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | npm-user-validate-0.1.5.tgz | Transitive | N/A | ❌ |
| [CVE-2018-3737](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3737) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | sshpk-1.10.1.tgz | Transitive | N/A | ❌ |
| [CVE-2017-18077](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-18077) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | brace-expansion-1.1.6.tgz | Transitive | N/A | ❌ |
| [WS-2020-0342](https://github.com/mafintosh/is-my-json-valid/commit/c3fc04fc455d40e9b29537f8e2c73a28ce106edb) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | is-my-json-valid-2.15.0.tgz | Transitive | N/A | ❌ |
| [CVE-2019-13173](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-13173) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | fstream-1.0.10.tgz | Transitive | N/A | ❌ |
| [CVE-2020-7788](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7788) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.3 | ini-1.3.4.tgz | Transitive | N/A | ❌ |
| [CVE-2018-21270](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-21270) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | stringstream-0.0.5.tgz | Transitive | N/A | ❌ |
| [CVE-2020-8244](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8244) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | bl-1.1.2.tgz | Transitive | N/A | ❌ |
| [CVE-2019-16775](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-16775) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | npm-3.10.10.tgz | Transitive | N/A | ❌ |
| [CVE-2019-16777](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-16777) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | npm-3.10.10.tgz | Transitive | N/A | ❌ |
| [CVE-2020-7598](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7598) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.6 | minimist-0.0.8.tgz | Transitive | N/A | ❌ |
| [CVE-2017-16032](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16032) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.5 | brace-expansion-1.1.6.tgz | Transitive | N/A | ❌ |
| [CVE-2021-23362](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23362) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | hosted-git-info-2.1.5.tgz | Transitive | N/A | ❌ |
| [CVE-2018-1107](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1107) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | is-my-json-valid-2.15.0.tgz | Transitive | N/A | ❌ |
| [WS-2018-0103](https://hackerone.com/reports/321670) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 4.8 | stringstream-0.0.5.tgz | Transitive | N/A | ❌ |
| [CVE-2020-15095](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15095) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 4.4 | npm-3.10.10.tgz | Transitive | N/A | ❌ |
| [CVE-2017-18869](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-18869) | <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low | 2.5 | chownr-1.0.1.tgz | Transitive | N/A | ❌ |
## Details
> Partial details (11 vulnerabilities) are displayed below due to a content size limitation in GitHub. To view information on the remaining vulnerabilities, navigate to the WhiteSource Application.<br>
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-3918</summary>
### Vulnerable Library - <b>json-schema-0.2.3.tgz</b></p>
<p>JSON Schema validation and specifications</p>
<p>Library home page: <a href="https://registry.npmjs.org/json-schema/-/json-schema-0.2.3.tgz">https://registry.npmjs.org/json-schema/-/json-schema-0.2.3.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/json-schema/package.json,/node_modules/npm/node_modules/request/node_modules/http-signature/node_modules/jsprim/node_modules/json-schema/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- npm-3.10.10.tgz
- request-2.75.0.tgz
- http-signature-1.1.1.tgz
- jsprim-1.3.1.tgz
- :x: **json-schema-0.2.3.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shiriivtsan/NodeGoat/commit/98fe87a557b23eb3b41abbc356778283c8f192d8">98fe87a557b23eb3b41abbc356778283c8f192d8</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
json-schema is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
<p>Publish Date: 2021-11-13
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3918>CVE-2021-3918</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-3918">https://nvd.nist.gov/vuln/detail/CVE-2021-3918</a></p>
<p>Release Date: 2021-11-13</p>
<p>Fix Resolution: json-schema - 0.4.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2018-16492</summary>
### Vulnerable Library - <b>extend-3.0.0.tgz</b></p>
<p>Port of jQuery.extend for node.js and the browser</p>
<p>Library home page: <a href="https://registry.npmjs.org/extend/-/extend-3.0.0.tgz">https://registry.npmjs.org/extend/-/extend-3.0.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/npm/node_modules/request/node_modules/extend/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- npm-3.10.10.tgz
- request-2.75.0.tgz
- :x: **extend-3.0.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shiriivtsan/NodeGoat/commit/98fe87a557b23eb3b41abbc356778283c8f192d8">98fe87a557b23eb3b41abbc356778283c8f192d8</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A prototype pollution vulnerability was found in module extend <2.0.2, ~<3.0.2 that allows an attacker to inject arbitrary properties onto Object.prototype.
<p>Publish Date: 2019-02-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-16492>CVE-2018-16492</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://hackerone.com/reports/381185">https://hackerone.com/reports/381185</a></p>
<p>Release Date: 2019-02-01</p>
<p>Fix Resolution: extend - v3.0.2,v2.0.2</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-23807</summary>
### Vulnerable Library - <b>jsonpointer-4.0.0.tgz</b></p>
<p>Simple JSON Addressing.</p>
<p>Library home page: <a href="https://registry.npmjs.org/jsonpointer/-/jsonpointer-4.0.0.tgz">https://registry.npmjs.org/jsonpointer/-/jsonpointer-4.0.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/npm/node_modules/request/node_modules/har-validator/node_modules/is-my-json-valid/node_modules/jsonpointer/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- npm-3.10.10.tgz
- request-2.75.0.tgz
- har-validator-2.0.6.tgz
- is-my-json-valid-2.15.0.tgz
- :x: **jsonpointer-4.0.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shiriivtsan/NodeGoat/commit/98fe87a557b23eb3b41abbc356778283c8f192d8">98fe87a557b23eb3b41abbc356778283c8f192d8</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
This affects the package jsonpointer before 5.0.0. A type confusion vulnerability can lead to a bypass of a previous Prototype Pollution fix when the pointer components are arrays.
<p>Publish Date: 2021-11-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23807>CVE-2021-23807</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23807">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23807</a></p>
<p>Release Date: 2021-11-03</p>
<p>Fix Resolution: jsonpointer - 5.0.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> WS-2020-0344</summary>
### Vulnerable Library - <b>is-my-json-valid-2.15.0.tgz</b></p>
<p>A JSONSchema validator that uses code generation to be extremely fast</p>
<p>Library home page: <a href="https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.15.0.tgz">https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.15.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/npm/node_modules/request/node_modules/har-validator/node_modules/is-my-json-valid/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- npm-3.10.10.tgz
- request-2.75.0.tgz
- har-validator-2.0.6.tgz
- :x: **is-my-json-valid-2.15.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shiriivtsan/NodeGoat/commit/98fe87a557b23eb3b41abbc356778283c8f192d8">98fe87a557b23eb3b41abbc356778283c8f192d8</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Arbitrary Code Execution vulnerability was found in is-my-json-valid before 2.20.3 via the fromatName function.
<p>Publish Date: 2020-06-09
<p>URL: <a href=https://github.com/mafintosh/is-my-json-valid/commit/3419563687df463b4ca709a2b46be8e15d6a2b3d>WS-2020-0344</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/mafintosh/is-my-json-valid/commit/c3fc04fc455d40e9b29537f8e2c73a28ce106edb">https://github.com/mafintosh/is-my-json-valid/commit/c3fc04fc455d40e9b29537f8e2c73a28ce106edb</a></p>
<p>Release Date: 2020-06-09</p>
<p>Fix Resolution: is-my-json-valid - 2.20.3</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> WS-2020-0345</summary>
### Vulnerable Library - <b>jsonpointer-4.0.0.tgz</b></p>
<p>Simple JSON Addressing.</p>
<p>Library home page: <a href="https://registry.npmjs.org/jsonpointer/-/jsonpointer-4.0.0.tgz">https://registry.npmjs.org/jsonpointer/-/jsonpointer-4.0.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/npm/node_modules/request/node_modules/har-validator/node_modules/is-my-json-valid/node_modules/jsonpointer/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- npm-3.10.10.tgz
- request-2.75.0.tgz
- har-validator-2.0.6.tgz
- is-my-json-valid-2.15.0.tgz
- :x: **jsonpointer-4.0.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shiriivtsan/NodeGoat/commit/98fe87a557b23eb3b41abbc356778283c8f192d8">98fe87a557b23eb3b41abbc356778283c8f192d8</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Prototype Pollution vulnerability was found in jsonpointer before 4.1.0 via the set function.
<p>Publish Date: 2020-07-03
<p>URL: <a href=https://github.com/janl/node-jsonpointer/commit/234e3437019c6c07537ed2ad1e03b3e132b85e34>WS-2020-0345</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.2</b>)
<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: Low
- Availability Impact: High
</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://github.com/janl/node-jsonpointer/releases/tag/v4.1.0">https://github.com/janl/node-jsonpointer/releases/tag/v4.1.0</a></p>
<p>Release Date: 2020-07-03</p>
<p>Fix Resolution: jsonpointer - 4.1.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-16776</summary>
### Vulnerable Library - <b>npm-3.10.10.tgz</b></p>
<p>a package manager for JavaScript</p>
<p>Library home page: <a href="https://registry.npmjs.org/npm/-/npm-3.10.10.tgz">https://registry.npmjs.org/npm/-/npm-3.10.10.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/npm/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- :x: **npm-3.10.10.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shiriivtsan/NodeGoat/commit/98fe87a557b23eb3b41abbc356778283c8f192d8">98fe87a557b23eb3b41abbc356778283c8f192d8</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Versions of the npm CLI prior to 6.13.3 are vulnerable to an Arbitrary File Write. It fails to prevent access to folders outside of the intended node_modules folder through the bin field. A properly constructed entry in the package.json bin field would allow a package publisher to modify and/or gain access to arbitrary files on a user's system when the package is installed. This behavior is still possible through install scripts. This vulnerability bypasses a user using the --ignore-scripts install option.
<p>Publish Date: 2019-12-13
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-16776>CVE-2019-16776</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://blog.npmjs.org/post/189618601100/binary-planting-with-the-npm-cli">https://blog.npmjs.org/post/189618601100/binary-planting-with-the-npm-cli</a></p>
<p>Release Date: 2020-10-07</p>
<p>Fix Resolution: npm - 6.13.3;yarn - 1.21.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-32804</summary>
### Vulnerable Library - <b>tar-2.2.1.tgz</b></p>
<p>tar for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-2.2.1.tgz">https://registry.npmjs.org/tar/-/tar-2.2.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/npm/node_modules/tar/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- npm-3.10.10.tgz
- :x: **tar-2.2.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shiriivtsan/NodeGoat/commit/98fe87a557b23eb3b41abbc356778283c8f192d8">98fe87a557b23eb3b41abbc356778283c8f192d8</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The npm package "tar" (aka node-tar) before versions 6.1.1, 5.0.6, 4.4.14, and 3.3.2 has a arbitrary File Creation/Overwrite vulnerability due to insufficient absolute path sanitization. node-tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the `preservePaths` flag is not set to `true`. This is achieved by stripping the absolute path root from any absolute file paths contained in a tar file. For example `/home/user/.bashrc` would turn into `home/user/.bashrc`. This logic was insufficient when file paths contained repeated path roots such as `////home/user/.bashrc`. `node-tar` would only strip a single path root from such paths. When given an absolute file path with repeating path roots, the resulting path (e.g. `///home/user/.bashrc`) would still resolve to an absolute path, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.2, 4.4.14, 5.0.6 and 6.1.1. Users may work around this vulnerability without upgrading by creating a custom `onentry` method which sanitizes the `entry.path` or a `filter` method which removes entries with absolute paths. See referenced GitHub Advisory for details. Be aware of CVE-2021-32803 which fixes a similar bug in later versions of tar.
<p>Publish Date: 2021-08-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-32804>CVE-2021-32804</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/npm/node-tar/security/advisories/GHSA-3jfq-g458-7qm9">https://github.com/npm/node-tar/security/advisories/GHSA-3jfq-g458-7qm9</a></p>
<p>Release Date: 2021-08-03</p>
<p>Fix Resolution: tar - 3.2.2, 4.4.14, 5.0.6, 6.1.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2018-20834</summary>
### Vulnerable Library - <b>tar-2.2.1.tgz</b></p>
<p>tar for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-2.2.1.tgz">https://registry.npmjs.org/tar/-/tar-2.2.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/npm/node_modules/tar/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- npm-3.10.10.tgz
- :x: **tar-2.2.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shiriivtsan/NodeGoat/commit/98fe87a557b23eb3b41abbc356778283c8f192d8">98fe87a557b23eb3b41abbc356778283c8f192d8</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A vulnerability was found in node-tar before version 4.4.2 (excluding version 2.2.2). An Arbitrary File Overwrite issue exists when extracting a tarball containing a hardlink to a file that already exists on the system, in conjunction with a later plain file with the same name as the hardlink. This plain file content replaces the existing file content. A patch has been applied to node-tar v2.2.2).
<p>Publish Date: 2019-04-30
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20834>CVE-2018-20834</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16082">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16082</a></p>
<p>Release Date: 2019-04-30</p>
<p>Fix Resolution: 2.2.2,4.4.2</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2017-15010</summary>
### Vulnerable Library - <b>tough-cookie-2.3.1.tgz</b></p>
<p>RFC6265 Cookies and Cookie Jar for node.js</p>
<p>Library home page: <a href="https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.3.1.tgz">https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.3.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/npm/node_modules/request/node_modules/tough-cookie/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- npm-3.10.10.tgz
- request-2.75.0.tgz
- :x: **tough-cookie-2.3.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shiriivtsan/NodeGoat/commit/98fe87a557b23eb3b41abbc356778283c8f192d8">98fe87a557b23eb3b41abbc356778283c8f192d8</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A ReDoS (regular expression denial of service) flaw was found in the tough-cookie module before 2.3.3 for Node.js. An attacker that is able to make an HTTP request using a specially crafted cookie may cause the application to consume an excessive amount of CPU.
<p>Publish Date: 2017-10-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-15010>CVE-2017-15010</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-15010">https://nvd.nist.gov/vuln/detail/CVE-2017-15010</a></p>
<p>Release Date: 2017-10-04</p>
<p>Fix Resolution: 2.3.3</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> WS-2020-0180</summary>
### Vulnerable Library - <b>npm-user-validate-0.1.5.tgz</b></p>
<p>User validations for npm</p>
<p>Library home page: <a href="https://registry.npmjs.org/npm-user-validate/-/npm-user-validate-0.1.5.tgz">https://registry.npmjs.org/npm-user-validate/-/npm-user-validate-0.1.5.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/npm/node_modules/npm-user-validate/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- npm-3.10.10.tgz
- :x: **npm-user-validate-0.1.5.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shiriivtsan/NodeGoat/commit/98fe87a557b23eb3b41abbc356778283c8f192d8">98fe87a557b23eb3b41abbc356778283c8f192d8</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The package npm-user-validate prior to version 1.0.1 is vulnerable to REDoS. The regex that validates a user's email took exponentially longer to process input strings that begin with the '@' character.
<p>Publish Date: 2020-10-16
<p>URL: <a href=https://github.com/npm/npm-user-validate/commit/c8a87dac1a4cc6988b5418f30411a8669bef204e>WS-2020-0180</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-xgh6-85xh-479p">https://github.com/advisories/GHSA-xgh6-85xh-479p</a></p>
<p>Release Date: 2020-10-16</p>
<p>Fix Resolution: 1.0.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> WS-2018-0069</summary>
### Vulnerable Library - <b>is-my-json-valid-2.15.0.tgz</b></p>
<p>A JSONSchema validator that uses code generation to be extremely fast</p>
<p>Library home page: <a href="https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.15.0.tgz">https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.15.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/npm/node_modules/request/node_modules/har-validator/node_modules/is-my-json-valid/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- npm-3.10.10.tgz
- request-2.75.0.tgz
- har-validator-2.0.6.tgz
- :x: **is-my-json-valid-2.15.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shiriivtsan/NodeGoat/commit/98fe87a557b23eb3b41abbc356778283c8f192d8">98fe87a557b23eb3b41abbc356778283c8f192d8</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Version of is-my-json-valid before 1.4.1 or 2.17.2 are vulnerable to regular expression denial of service (ReDoS) via the email validation function.
<p>Publish Date: 2018-02-14
<p>URL: <a href=https://github.com/mafintosh/is-my-json-valid/commit/b3051b277f7caa08cd2edc6f74f50aeda65d2976>WS-2018-0069</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nodesecurity.io/advisories/572">https://nodesecurity.io/advisories/572</a></p>
<p>Release Date: 2018-02-14</p>
<p>Fix Resolution: 1.4.1</p>
</p>
<p></p>
</details>
<!-- <REMEDIATE>[{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"json-schema","packageVersion":"0.2.3","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;request:2.75.0;http-signature:1.1.1;jsprim:1.3.1;json-schema:0.2.3","isMinimumFixVersionAvailable":true,"minimumFixVersion":"json-schema - 0.4.0","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-3918","vulnerabilityDetails":"json-schema is vulnerable to Improperly Controlled Modification of Object Prototype Attributes (\u0027Prototype Pollution\u0027)","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3918","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"extend","packageVersion":"3.0.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;request:2.75.0;extend:3.0.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"extend - v3.0.2,v2.0.2","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-16492","vulnerabilityDetails":"A prototype pollution vulnerability was found in module extend \u003c2.0.2, ~\u003c3.0.2 that allows an attacker to inject arbitrary properties onto Object.prototype.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-16492","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"jsonpointer","packageVersion":"4.0.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;request:2.75.0;har-validator:2.0.6;is-my-json-valid:2.15.0;jsonpointer:4.0.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"jsonpointer - 5.0.0","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-23807","vulnerabilityDetails":"This affects the package jsonpointer before 5.0.0. A type confusion vulnerability can lead to a bypass of a previous Prototype Pollution fix when the pointer components are arrays.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23807","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"is-my-json-valid","packageVersion":"2.15.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;request:2.75.0;har-validator:2.0.6;is-my-json-valid:2.15.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"is-my-json-valid - 2.20.3","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2020-0344","vulnerabilityDetails":"Arbitrary Code Execution vulnerability was found in is-my-json-valid before 2.20.3 via the fromatName function.","vulnerabilityUrl":"https://github.com/mafintosh/is-my-json-valid/commit/3419563687df463b4ca709a2b46be8e15d6a2b3d","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"jsonpointer","packageVersion":"4.0.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;request:2.75.0;har-validator:2.0.6;is-my-json-valid:2.15.0;jsonpointer:4.0.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"jsonpointer - 4.1.0","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2020-0345","vulnerabilityDetails":"Prototype Pollution vulnerability was found in jsonpointer before 4.1.0 via the set function.","vulnerabilityUrl":"https://github.com/janl/node-jsonpointer/commit/234e3437019c6c07537ed2ad1e03b3e132b85e34","cvss3Severity":"high","cvss3Score":"8.2","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"Low"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"npm","packageVersion":"3.10.10","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10","isMinimumFixVersionAvailable":true,"minimumFixVersion":"npm - 6.13.3;yarn - 1.21.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2019-16776","vulnerabilityDetails":"Versions of the npm CLI prior to 6.13.3 are vulnerable to an Arbitrary File Write. It fails to prevent access to folders outside of the intended node_modules folder through the bin field. A properly constructed entry in the package.json bin field would allow a package publisher to modify and/or gain access to arbitrary files on a user\u0027s system when the package is installed. This behavior is still possible through install scripts. This vulnerability bypasses a user using the --ignore-scripts install option.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-16776","cvss3Severity":"high","cvss3Score":"8.1","cvss3Metrics":{"A":"None","AC":"Low","PR":"Low","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"tar","packageVersion":"2.2.1","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;tar:2.2.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"tar - 3.2.2, 4.4.14, 5.0.6, 6.1.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-32804","vulnerabilityDetails":"The npm package \"tar\" (aka node-tar) before versions 6.1.1, 5.0.6, 4.4.14, and 3.3.2 has a arbitrary File Creation/Overwrite vulnerability due to insufficient absolute path sanitization. node-tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the `preservePaths` flag is not set to `true`. This is achieved by stripping the absolute path root from any absolute file paths contained in a tar file. For example `/home/user/.bashrc` would turn into `home/user/.bashrc`. This logic was insufficient when file paths contained repeated path roots such as `////home/user/.bashrc`. `node-tar` would only strip a single path root from such paths. When given an absolute file path with repeating path roots, the resulting path (e.g. `///home/user/.bashrc`) would still resolve to an absolute path, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.2, 4.4.14, 5.0.6 and 6.1.1. Users may work around this vulnerability without upgrading by creating a custom `onentry` method which sanitizes the `entry.path` or a `filter` method which removes entries with absolute paths. See referenced GitHub Advisory for details. Be aware of CVE-2021-32803 which fixes a similar bug in later versions of tar.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-32804","cvss3Severity":"high","cvss3Score":"8.1","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"Required","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"tar","packageVersion":"2.2.1","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;tar:2.2.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"2.2.2,4.4.2","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-20834","vulnerabilityDetails":"A vulnerability was found in node-tar before version 4.4.2 (excluding version 2.2.2). An Arbitrary File Overwrite issue exists when extracting a tarball containing a hardlink to a file that already exists on the system, in conjunction with a later plain file with the same name as the hardlink. This plain file content replaces the existing file content. A patch has been applied to node-tar v2.2.2).","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20834","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"tough-cookie","packageVersion":"2.3.1","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;request:2.75.0;tough-cookie:2.3.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"2.3.3","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2017-15010","vulnerabilityDetails":"A ReDoS (regular expression denial of service) flaw was found in the tough-cookie module before 2.3.3 for Node.js. An attacker that is able to make an HTTP request using a specially crafted cookie may cause the application to consume an excessive amount of CPU.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-15010","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"npm-user-validate","packageVersion":"0.1.5","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;npm-user-validate:0.1.5","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.0.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2020-0180","vulnerabilityDetails":"The package npm-user-validate prior to version 1.0.1 is vulnerable to REDoS. The regex that validates a user\u0027s email took exponentially longer to process input strings that begin with the \u0027@\u0027 character.","vulnerabilityUrl":"https://github.com/npm/npm-user-validate/commit/c8a87dac1a4cc6988b5418f30411a8669bef204e","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"is-my-json-valid","packageVersion":"2.15.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;request:2.75.0;har-validator:2.0.6;is-my-json-valid:2.15.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.4.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2018-0069","vulnerabilityDetails":"Version of is-my-json-valid before 1.4.1 or 2.17.2 are vulnerable to regular expression denial of service (ReDoS) via the email validation function.","vulnerabilityUrl":"https://github.com/mafintosh/is-my-json-valid/commit/b3051b277f7caa08cd2edc6f74f50aeda65d2976","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"qs","packageVersion":"6.2.1","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;request:2.75.0;qs:6.2.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"qs - 6.0.4,6.1.2,6.2.3,6.3.2","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2017-1000048","vulnerabilityDetails":"the web framework using ljharb\u0027s qs module older than v6.3.2, v6.2.3, v6.1.2, and v6.0.4 is vulnerable to a DoS. A malicious user can send a evil request to cause the web framework crash.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-1000048","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"npm-user-validate","packageVersion":"0.1.5","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;npm-user-validate:0.1.5","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.0.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-7754","vulnerabilityDetails":"This affects the package npm-user-validate before 1.0.1. The regex that validates user emails took exponentially longer to process long input strings beginning with @ characters.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7754","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"sshpk","packageVersion":"1.10.1","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;request:2.75.0;http-signature:1.1.1;sshpk:1.10.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.13.2","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-3737","vulnerabilityDetails":"sshpk is vulnerable to ReDoS when parsing crafted invalid public keys.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3737","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"brace-expansion","packageVersion":"1.1.6","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;read-package-json:2.0.4;glob:6.0.4;minimatch:3.0.3;brace-expansion:1.1.6","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.1.7","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2017-18077","vulnerabilityDetails":"index.js in brace-expansion before 1.1.7 is vulnerable to Regular Expression Denial of Service (ReDoS) attacks, as demonstrated by an expand argument containing many comma characters.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-18077","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"is-my-json-valid","packageVersion":"2.15.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;request:2.75.0;har-validator:2.0.6;is-my-json-valid:2.15.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"is-my-json-valid - 2.20.2","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2020-0342","vulnerabilityDetails":"Regular Expression Denial of Service (ReDoS) vulnerability was found in is-my-json-valid before 2.20.2 via the style format.","vulnerabilityUrl":"https://github.com/mafintosh/is-my-json-valid/commit/c3fc04fc455d40e9b29537f8e2c73a28ce106edb","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"fstream","packageVersion":"1.0.10","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;fstream:1.0.10","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.0.12","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2019-13173","vulnerabilityDetails":"fstream before 1.0.12 is vulnerable to Arbitrary File Overwrite. Extracting tarballs containing a hardlink to a file that already exists in the system, and a file that matches the hardlink, will overwrite the system\u0027s file with the contents of the extracted file. The fstream.DirWriter() function is vulnerable.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-13173","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"ini","packageVersion":"1.3.4","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;ini:1.3.4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"v1.3.6","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-7788","vulnerabilityDetails":"This affects the package ini before 1.3.6. If an attacker submits a malicious INI file to an application that parses it with ini.parse, they will pollute the prototype on the application. This can be exploited further depending on the context.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7788","cvss3Severity":"high","cvss3Score":"7.3","cvss3Metrics":{"A":"Low","AC":"Low","PR":"None","S":"Unchanged","C":"Low","UI":"None","AV":"Network","I":"Low"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"stringstream","packageVersion":"0.0.5","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;request:2.75.0;stringstream:0.0.5","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.0.6","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-21270","vulnerabilityDetails":"Versions less than 0.0.6 of the Node.js stringstream module are vulnerable to an out-of-bounds read because of allocation of uninitialized buffers when a number is passed in the input stream (when using Node.js 4.x).","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-21270","cvss3Severity":"medium","cvss3Score":"6.5","cvss3Metrics":{"A":"High","AC":"High","PR":"None","S":"Unchanged","C":"Low","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"bl","packageVersion":"1.1.2","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;request:2.75.0;bl:1.1.2","isMinimumFixVersionAvailable":true,"minimumFixVersion":"bl - 1.2.3,2.2.1,3.0.1,4.0.3","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-8244","vulnerabilityDetails":"A buffer over-read vulnerability exists in bl \u003c4.0.3, \u003c3.0.1, \u003c2.2.1, and \u003c1.2.3 which could allow an attacker to supply user input (even typed) that if it ends up in consume() argument and can become negative, the BufferList state can be corrupted, tricking it into exposing uninitialized memory via regular .slice() calls.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8244","cvss3Severity":"medium","cvss3Score":"6.5","cvss3Metrics":{"A":"Low","AC":"Low","PR":"None","S":"Unchanged","C":"Low","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"npm","packageVersion":"3.10.10","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10","isMinimumFixVersionAvailable":true,"minimumFixVersion":"npm - 6.13.3;yarn - 1.21.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2019-16775","vulnerabilityDetails":"Versions of the npm CLI prior to 6.13.3 are vulnerable to an Arbitrary File Write. It is possible for packages to create symlinks to files outside of thenode_modules folder through the bin field upon installation. A properly constructed entry in the package.json bin field would allow a package publisher to create a symlink pointing to arbitrary files on a user\u0027s system when the package is installed. This behavior is still possible through install scripts. This vulnerability bypasses a user using the --ignore-scripts install option.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-16775","cvss3Severity":"medium","cvss3Score":"6.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"Low","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"npm","packageVersion":"3.10.10","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10","isMinimumFixVersionAvailable":true,"minimumFixVersion":"npm - 6.13.4","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2019-16777","vulnerabilityDetails":"Versions of the npm CLI prior to 6.13.4 are vulnerable to an Arbitrary File Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a serve binary, any subsequent installs of packages that also create a serve binary would overwrite the previous serve binary. This behavior is still allowed in local installations and also through install scripts. This vulnerability bypasses a user using the --ignore-scripts install option.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-16777","cvss3Severity":"medium","cvss3Score":"6.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"Low","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"minimist","packageVersion":"0.0.8","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;mkdirp:0.5.1;minimist:0.0.8","isMinimumFixVersionAvailable":true,"minimumFixVersion":"minimist - 0.2.1,1.2.3","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-7598","vulnerabilityDetails":"minimist before 1.2.2 could be tricked into adding or modifying properties of Object.prototype using a \"constructor\" or \"__proto__\" payload.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7598","cvss3Severity":"medium","cvss3Score":"5.6","cvss3Metrics":{"A":"Low","AC":"High","PR":"None","S":"Unchanged","C":"Low","UI":"None","AV":"Network","I":"Low"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"brace-expansion","packageVersion":"1.1.6","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;read-package-json:2.0.4;glob:6.0.4;minimatch:3.0.3;brace-expansion:1.1.6","isMinimumFixVersionAvailable":true,"minimumFixVersion":"v1.1.7","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2017-16032","vulnerabilityDetails":"brace-expansion before 1.1.7 are vulnerable to a regular expression denial of service.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16032","cvss3Severity":"medium","cvss3Score":"5.5","cvss3Metrics":{"A":"High","AC":"High","PR":"Low","S":"Unchanged","C":"Low","UI":"Required","AV":"Local","I":"Low"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"hosted-git-info","packageVersion":"2.1.5","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;hosted-git-info:2.1.5","isMinimumFixVersionAvailable":true,"minimumFixVersion":"hosted-git-info - 2.8.9,3.0.8","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-23362","vulnerabilityDetails":"The package hosted-git-info before 3.0.8 are vulnerable to Regular Expression Denial of Service (ReDoS) via regular expression shortcutMatch in the fromUrl function in index.js. The affected regular expression exhibits polynomial worst-case time complexity.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23362","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"Low","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"is-my-json-valid","packageVersion":"2.15.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;request:2.75.0;har-validator:2.0.6;is-my-json-valid:2.15.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"is-my-json-valid - 1.4.1, 2.17.2","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-1107","vulnerabilityDetails":"It was discovered that the is-my-json-valid JavaScript library used an inefficient regular expression to validate JSON fields defined to have email format. A specially crafted JSON file could cause it to consume an excessive amount of CPU time when validated.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1107","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"Low","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"stringstream","packageVersion":"0.0.5","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;request:2.75.0;stringstream:0.0.5","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.0.6","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2018-0103","vulnerabilityDetails":"All versions of stringstream are vulnerable to out-of-bounds read as it allocates uninitialized Buffers when number is passed in input stream on Node.js 4.x and below.","vulnerabilityUrl":"https://hackerone.com/reports/321670","cvss3Severity":"medium","cvss3Score":"4.8","cvss3Metrics":{"A":"Low","AC":"High","PR":"None","S":"Unchanged","C":"Low","UI":"None","AV":"Network","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"npm","packageVersion":"3.10.10","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10","isMinimumFixVersionAvailable":true,"minimumFixVersion":"npm - 6.14.6","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-15095","vulnerabilityDetails":"Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like \"\u003cprotocol\u003e://[\u003cuser\u003e[:\u003cpassword\u003e]@]\u003chostname\u003e[:\u003cport\u003e][:][/]\u003cpath\u003e\". The password value is not redacted and is printed to stdout and also to any generated log files.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15095","cvss3Severity":"medium","cvss3Score":"4.4","cvss3Metrics":{"A":"None","AC":"High","PR":"Low","S":"Unchanged","C":"High","UI":"Required","AV":"Local","I":"None"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"chownr","packageVersion":"1.0.1","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;chownr:1.0.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.1.0","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2017-18869","vulnerabilityDetails":"A TOCTOU issue in the chownr package before 1.1.0 for Node.js 10.10 could allow a local attacker to trick it into descending into unintended directories via symlink attacks.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-18869","cvss3Severity":"low","cvss3Score":"2.5","cvss3Metrics":{"A":"None","AC":"High","PR":"Low","S":"Unchanged","C":"None","UI":"None","AV":"Local","I":"Low"},"extraData":{}}]</REMEDIATE> --> | non_defect | grunt npm install tgz vulnerabilities highest severity is vulnerable library grunt npm install tgz path to dependency file package json path to vulnerable library node modules npm node modules fstream package json found in head commit a href vulnerabilities cve severity cvss dependency type fixed in remediation available high json schema tgz transitive n a ❌ high extend tgz transitive n a ❌ high jsonpointer tgz transitive n a ❌ high is my json valid tgz transitive n a ❌ high jsonpointer tgz transitive n a ❌ high npm tgz transitive n a ❌ high tar tgz transitive n a ❌ high tar tgz transitive n a ❌ high tough cookie tgz transitive n a ❌ high npm user validate tgz transitive n a ❌ high is my json valid tgz transitive n a ❌ high qs tgz transitive n a ❌ high npm user validate tgz transitive n a ❌ high sshpk tgz transitive n a ❌ high brace expansion tgz transitive n a ❌ high is my json valid tgz transitive n a ❌ high fstream tgz transitive n a ❌ high ini tgz transitive n a ❌ medium stringstream tgz transitive n a ❌ medium bl tgz transitive n a ❌ medium npm tgz transitive n a ❌ medium npm tgz transitive n a ❌ medium minimist tgz transitive n a ❌ medium brace expansion tgz transitive n a ❌ medium hosted git info tgz transitive n a ❌ medium is my json valid tgz transitive n a ❌ medium stringstream tgz transitive n a ❌ medium npm tgz transitive n a ❌ low chownr tgz transitive n a ❌ details partial details vulnerabilities are displayed below due to a content size limitation in github to view information on the remaining vulnerabilities navigate to the whitesource application cve vulnerable library json schema tgz json schema validation and specifications library home page a href path to dependency file package json path to vulnerable library node modules json schema package json node modules npm node modules request node modules http signature node modules jsprim node modules json schema package json dependency hierarchy grunt npm install tgz root library npm tgz request tgz http signature tgz jsprim tgz x json schema tgz vulnerable library found in head commit a href found in base branch master vulnerability details json schema is vulnerable to improperly controlled modification of object prototype attributes prototype pollution 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 json schema cve vulnerable library extend tgz port of jquery extend for node js and the browser library home page a href path to dependency file package json path to vulnerable library node modules npm node modules request node modules extend package json dependency hierarchy grunt npm install tgz root library npm tgz request tgz x extend tgz vulnerable library found in head commit a href found in base branch master vulnerability details a prototype pollution vulnerability was found in module extend that allows an attacker to inject arbitrary properties onto object prototype 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 extend cve vulnerable library jsonpointer tgz simple json addressing library home page a href path to dependency file package json path to vulnerable library node modules npm node modules request node modules har validator node modules is my json valid node modules jsonpointer package json dependency hierarchy grunt npm install tgz root library npm tgz request tgz har validator tgz is my json valid tgz x jsonpointer tgz vulnerable library found in head commit a href found in base branch master vulnerability details this affects the package jsonpointer before a type confusion vulnerability can lead to a bypass of a previous prototype pollution fix when the pointer components are arrays 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 jsonpointer ws vulnerable library is my json valid tgz a jsonschema validator that uses code generation to be extremely fast library home page a href path to dependency file package json path to vulnerable library node modules npm node modules request node modules har validator node modules is my json valid package json dependency hierarchy grunt npm install tgz root library npm tgz request tgz har validator tgz x is my json valid tgz vulnerable library found in head commit a href found in base branch master vulnerability details arbitrary code execution vulnerability was found in is my json valid before via the fromatname function 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 is my json valid ws vulnerable library jsonpointer tgz simple json addressing library home page a href path to dependency file package json path to vulnerable library node modules npm node modules request node modules har validator node modules is my json valid node modules jsonpointer package json dependency hierarchy grunt npm install tgz root library npm tgz request tgz har validator tgz is my json valid tgz x jsonpointer tgz vulnerable library found in head commit a href found in base branch master vulnerability details prototype pollution vulnerability was found in jsonpointer before via the set function 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 low availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution jsonpointer cve vulnerable library npm tgz a package manager for javascript library home page a href path to dependency file package json path to vulnerable library node modules npm package json dependency hierarchy grunt npm install tgz root library x npm tgz vulnerable library found in head commit a href found in base branch master vulnerability details versions of the npm cli prior to are vulnerable to an arbitrary file write it fails to prevent access to folders outside of the intended node modules folder through the bin field a properly constructed entry in the package json bin field would allow a package publisher to modify and or gain access to arbitrary files on a user s system when the package is installed this behavior is still possible through install scripts this vulnerability bypasses a user using the ignore scripts install option publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution npm yarn cve vulnerable library tar tgz tar for node library home page a href path to dependency file package json path to vulnerable library node modules npm node modules tar package json dependency hierarchy grunt npm install tgz root library npm tgz x tar tgz vulnerable library found in head commit a href found in base branch master vulnerability details the npm package tar aka node tar before versions and has a arbitrary file creation overwrite vulnerability due to insufficient absolute path sanitization node tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the preservepaths flag is not set to true this is achieved by stripping the absolute path root from any absolute file paths contained in a tar file for example home user bashrc would turn into home user bashrc this logic was insufficient when file paths contained repeated path roots such as home user bashrc node tar would only strip a single path root from such paths when given an absolute file path with repeating path roots the resulting path e g home user bashrc would still resolve to an absolute path thus allowing arbitrary file creation and overwrite this issue was addressed in releases and users may work around this vulnerability without upgrading by creating a custom onentry method which sanitizes the entry path or a filter method which removes entries with absolute paths see referenced github advisory for details be aware of cve which fixes a similar bug in later versions of tar publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution tar cve vulnerable library tar tgz tar for node library home page a href path to dependency file package json path to vulnerable library node modules npm node modules tar package json dependency hierarchy grunt npm install tgz root library npm tgz x tar tgz vulnerable library found in head commit a href found in base branch master vulnerability details a vulnerability was found in node tar before version excluding version an arbitrary file overwrite issue exists when extracting a tarball containing a hardlink to a file that already exists on the system in conjunction with a later plain file with the same name as the hardlink this plain file content replaces the existing file content a patch has been applied to node tar 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 cve vulnerable library tough cookie tgz cookies and cookie jar for node js library home page a href path to dependency file package json path to vulnerable library node modules npm node modules request node modules tough cookie package json dependency hierarchy grunt npm install tgz root library npm tgz request tgz x tough cookie tgz vulnerable library found in head commit a href found in base branch master vulnerability details a redos regular expression denial of service flaw was found in the tough cookie module before for node js an attacker that is able to make an http request using a specially crafted cookie may cause the application to consume an excessive amount of cpu 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 ws vulnerable library npm user validate tgz user validations for npm library home page a href path to dependency file package json path to vulnerable library node modules npm node modules npm user validate package json dependency hierarchy grunt npm install tgz root library npm tgz x npm user validate tgz vulnerable library found in head commit a href found in base branch master vulnerability details the package npm user validate prior to version is vulnerable to redos the regex that validates a user s email took exponentially longer to process input strings that begin with the character publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact 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 ws vulnerable library is my json valid tgz a jsonschema validator that uses code generation to be extremely fast library home page a href path to dependency file package json path to vulnerable library node modules npm node modules request node modules har validator node modules is my json valid package json dependency hierarchy grunt npm install tgz root library npm tgz request tgz har validator tgz x is my json valid tgz vulnerable library found in head commit a href found in base branch master vulnerability details version of is my json valid before or are vulnerable to regular expression denial of service redos via the email validation function 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 istransitivedependency true dependencytree grunt npm install npm request http signature jsprim json schema isminimumfixversionavailable true minimumfixversion json schema isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails json schema is vulnerable to improperly controlled modification of object prototype attributes pollution vulnerabilityurl istransitivedependency true dependencytree grunt npm install npm request extend isminimumfixversionavailable true minimumfixversion extend isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails a prototype pollution vulnerability was found in module extend that allows an attacker to inject arbitrary properties onto object prototype vulnerabilityurl istransitivedependency true dependencytree grunt npm install npm request har validator is my json valid jsonpointer isminimumfixversionavailable true minimumfixversion jsonpointer isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails this affects the package jsonpointer before a type confusion vulnerability can lead to a bypass of a previous prototype pollution fix when the pointer components are arrays vulnerabilityurl istransitivedependency true dependencytree grunt npm install npm request har validator is my json valid isminimumfixversionavailable true minimumfixversion is my json valid isbinary false basebranches vulnerabilityidentifier ws vulnerabilitydetails arbitrary code execution vulnerability was found in is my json valid before via the fromatname function vulnerabilityurl istransitivedependency true dependencytree grunt npm install npm request har validator is my json valid jsonpointer isminimumfixversionavailable true minimumfixversion jsonpointer isbinary false basebranches vulnerabilityidentifier ws vulnerabilitydetails prototype pollution vulnerability was found in jsonpointer before via the set function vulnerabilityurl istransitivedependency true dependencytree grunt npm install npm isminimumfixversionavailable true minimumfixversion npm yarn isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails versions of the npm cli prior to are vulnerable to an arbitrary file write it fails to prevent access to folders outside of the intended node modules folder through the bin field a properly constructed entry in the package json bin field would allow a package publisher to modify and or gain access to arbitrary files on a user system when the package is installed this behavior is still possible through install scripts this vulnerability bypasses a user using the ignore scripts install option vulnerabilityurl istransitivedependency true dependencytree grunt npm install npm tar isminimumfixversionavailable true minimumfixversion tar isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails the npm package tar aka node tar before versions and has a arbitrary file creation overwrite vulnerability due to insufficient absolute path sanitization node tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the preservepaths flag is not set to true this is achieved by stripping the absolute path root from any absolute file paths contained in a tar file for example home user bashrc would turn into home user bashrc this logic was insufficient when file paths contained repeated path roots such as home user bashrc node tar would only strip a single path root from such paths when given an absolute file path with repeating path roots the resulting path e g home user bashrc would still resolve to an absolute path thus allowing arbitrary file creation and overwrite this issue was addressed in releases and users may work around this vulnerability without upgrading by creating a custom onentry method which sanitizes the entry path or a filter method which removes entries with absolute paths see referenced github advisory for details be aware of cve which fixes a similar bug in later versions of tar vulnerabilityurl istransitivedependency true dependencytree grunt npm install npm tar isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails a vulnerability was found in node tar before version excluding version an arbitrary file overwrite issue exists when extracting a tarball containing a hardlink to a file that already exists on the system in conjunction with a later plain file with the same name as the hardlink this plain file content replaces the existing file content a patch has been applied to node tar vulnerabilityurl istransitivedependency true dependencytree grunt npm install npm request tough cookie isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails a redos regular expression denial of service flaw was found in the tough cookie module before for node js an attacker that is able to make an http request using a specially crafted cookie may cause the application to consume an excessive amount of cpu vulnerabilityurl istransitivedependency true dependencytree grunt npm install npm npm user validate isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier ws vulnerabilitydetails the package npm user validate prior to version is vulnerable to redos the regex that validates a user email took exponentially longer to process input strings that begin with the character vulnerabilityurl istransitivedependency true dependencytree grunt npm install npm request har validator is my json valid isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier ws vulnerabilitydetails version of is my json valid before or are vulnerable to regular expression denial of service redos via the email validation function vulnerabilityurl istransitivedependency true dependencytree grunt npm install npm request qs isminimumfixversionavailable true minimumfixversion qs isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails the web framework using ljharb qs module older than and is vulnerable to a dos a malicious user can send a evil request to cause the web framework crash vulnerabilityurl istransitivedependency true dependencytree grunt npm install npm npm user validate isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails this affects the package npm user validate before the regex that validates user emails took exponentially longer to process long input strings beginning with characters vulnerabilityurl istransitivedependency true dependencytree grunt npm install npm request http signature sshpk isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails sshpk is vulnerable to redos when parsing crafted invalid public keys vulnerabilityurl istransitivedependency true dependencytree grunt npm install npm read package json glob minimatch brace expansion isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails index js in brace expansion before is vulnerable to regular expression denial of service redos attacks as demonstrated by an expand argument containing many comma characters vulnerabilityurl istransitivedependency true dependencytree grunt npm install npm request har validator is my json valid isminimumfixversionavailable true minimumfixversion is my json valid isbinary false basebranches vulnerabilityidentifier ws vulnerabilitydetails regular expression denial of service redos vulnerability was found in is my json valid before via the style format vulnerabilityurl istransitivedependency true dependencytree grunt npm install npm fstream isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails fstream before is vulnerable to arbitrary file overwrite extracting tarballs containing a hardlink to a file that already exists in the system and a file that matches the hardlink will overwrite the system file with the contents of the extracted file the fstream dirwriter function is vulnerable vulnerabilityurl istransitivedependency true dependencytree grunt npm install npm ini isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails this affects the package ini before if an attacker submits a malicious ini file to an application that parses it with ini parse they will pollute the prototype on the application this can be exploited further depending on the context vulnerabilityurl istransitivedependency true dependencytree grunt npm install npm request stringstream isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails versions less than of the node js stringstream module are vulnerable to an out of bounds read because of allocation of uninitialized buffers when a number is passed in the input stream when using node js x vulnerabilityurl istransitivedependency true dependencytree grunt npm install npm request bl isminimumfixversionavailable true minimumfixversion bl isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails a buffer over read vulnerability exists in bl and which could allow an attacker to supply user input even typed that if it ends up in consume argument and can become negative the bufferlist state can be corrupted tricking it into exposing uninitialized memory via regular slice calls vulnerabilityurl istransitivedependency true dependencytree grunt npm install npm isminimumfixversionavailable true minimumfixversion npm yarn isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails versions of the npm cli prior to are vulnerable to an arbitrary file write it is possible for packages to create symlinks to files outside of thenode modules folder through the bin field upon installation a properly constructed entry in the package json bin field would allow a package publisher to create a symlink pointing to arbitrary files on a user system when the package is installed this behavior is still possible through install scripts this vulnerability bypasses a user using the ignore scripts install option vulnerabilityurl istransitivedependency true dependencytree grunt npm install npm isminimumfixversionavailable true minimumfixversion npm isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails versions of the npm cli prior to are vulnerable to an arbitrary file overwrite it fails to prevent existing globally installed binaries to be overwritten by other package installations for example if a package was installed globally and created a serve binary any subsequent installs of packages that also create a serve binary would overwrite the previous serve binary this behavior is still allowed in local installations and also through install scripts this vulnerability bypasses a user using the ignore scripts install option vulnerabilityurl istransitivedependency true dependencytree grunt npm install npm mkdirp minimist isminimumfixversionavailable true minimumfixversion minimist isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails minimist before could be tricked into adding or modifying properties of object prototype using a constructor or proto payload vulnerabilityurl istransitivedependency true dependencytree grunt npm install npm read package json glob minimatch brace expansion isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails brace expansion before are vulnerable to a regular expression denial of service vulnerabilityurl istransitivedependency true dependencytree grunt npm install npm hosted git info isminimumfixversionavailable true minimumfixversion hosted git info isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails the package hosted git info before are vulnerable to regular expression denial of service redos via regular expression shortcutmatch in the fromurl function in index js the affected regular expression exhibits polynomial worst case time complexity vulnerabilityurl istransitivedependency true dependencytree grunt npm install npm request har validator is my json valid isminimumfixversionavailable true minimumfixversion is my json valid isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails it was discovered that the is my json valid javascript library used an inefficient regular expression to validate json fields defined to have email format a specially crafted json file could cause it to consume an excessive amount of cpu time when validated vulnerabilityurl istransitivedependency true dependencytree grunt npm install npm request stringstream isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier ws vulnerabilitydetails all versions of stringstream are vulnerable to out of bounds read as it allocates uninitialized buffers when number is passed in input stream on node js x and below vulnerabilityurl istransitivedependency true dependencytree grunt npm install npm isminimumfixversionavailable true minimumfixversion npm isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails versions of the npm cli prior to are vulnerable to an information exposure vulnerability through log files the cli supports urls like the password value is not redacted and is printed to stdout and also to any generated log files vulnerabilityurl istransitivedependency true dependencytree grunt npm install npm chownr isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails a toctou issue in the chownr package before for node js could allow a local attacker to trick it into descending into unintended directories via symlink attacks vulnerabilityurl | 0 |
4,409 | 2,610,093,607 | IssuesEvent | 2015-02-26 18:28:15 | chrsmith/dsdsdaadf | https://api.github.com/repos/chrsmith/dsdsdaadf | opened | 深圳孩子脸上长青春痘怎么办 | auto-migrated Priority-Medium Type-Defect | ```
深圳孩子脸上长青春痘怎么办【深圳韩方科颜全国热线400-869-
1818，24小时QQ4008691818】深圳韩方科颜专业祛痘连锁机构，机��
�以韩国秘方——韩方科颜这一国妆准字号治疗型权威，祛痘�
��品，韩方科颜专业祛痘连锁机构，采用韩国秘方配合专业“
不反弹”健康祛痘技术并结合先进“先进豪华彩光”仪，开��
�国内专业治疗粉刺、痤疮签约包治先河，成功消除了许多顾�
��脸上的痘痘。
```
-----
Original issue reported on code.google.com by `szft...@163.com` on 14 May 2014 at 8:09 | 1.0 | 深圳孩子脸上长青春痘怎么办 - ```
深圳孩子脸上长青春痘怎么办【深圳韩方科颜全国热线400-869-
1818，24小时QQ4008691818】深圳韩方科颜专业祛痘连锁机构，机��
�以韩国秘方——韩方科颜这一国妆准字号治疗型权威，祛痘�
��品，韩方科颜专业祛痘连锁机构，采用韩国秘方配合专业“
不反弹”健康祛痘技术并结合先进“先进豪华彩光”仪，开��
�国内专业治疗粉刺、痤疮签约包治先河，成功消除了许多顾�
��脸上的痘痘。
```
-----
Original issue reported on code.google.com by `szft...@163.com` on 14 May 2014 at 8:09 | defect | 深圳孩子脸上长青春痘怎么办 深圳孩子脸上长青春痘怎么办【 ， 】深圳韩方科颜专业祛痘连锁机构，机�� �以韩国秘方——韩方科颜这一国妆准字号治疗型权威，祛痘� ��品，韩方科颜专业祛痘连锁机构，采用韩国秘方配合专业“ 不反弹”健康祛痘技术并结合先进“先进豪华彩光”仪，开�� �国内专业治疗粉刺、痤疮签约包治先河，成功消除了许多顾� ��脸上的痘痘。 original issue reported on code google com by szft com on may at | 1 |
179,416 | 30,234,648,036 | IssuesEvent | 2023-07-06 09:22:55 | neondatabase/neon | https://api.github.com/repos/neondatabase/neon | opened | Consumption metrics faster after restart | t/feature c/storage/pageserver t/tech_design_rfc a/consumption_metrics | Right now we start to collect consumption metrics every N minutes, and calculate synthetic size every M minutes for all tenants in sequence (order unspecified). In default config N == M, so there is a change that on first rounds after the restart:
1. upload may have some synthetic sizes
2. upload may will have some synthetic sizes
3. upload may will have most synthetic sizes
4. upload should have most if not all synthetic sizes
However, we now need due to external requirements reporting every N instead of possibly multiples of N. There have also been ideas of setting up an SLI for how often we upload the metrics -- I think the interesting case is "how often we upload these per tenant", not "how often a POST request goes out".
On #3542 I noticed that we also leak a bit of metrics for any detached tenants, as we never clear them. The problems with the current approach of listing all tenants and iterating them is that we lack the ability to clean things up once complete, or react to for example synthetic size calculation completing.
I think we should instead organize metrics sending so that:
- task to buffer and collected metrics is spawned
- each tenant gets a process collecting the metrics on tick, including synthetic size
- per tenant caching
- synthetic size has a global rate limit already
- synthetic size could be "ongoing" while other metrics are collected, and when it completes, we would just send it like other metrics to be buffered and sent
- on tenant deactivating, we would exit the task
- the top-level consumption metrics task
- spawning up new tasks for appeared tenants
- maintaining that we should *send over* the cached metrics every K minutes by signalling all per-tenant collectors
I think this design would allow us fine grained control over metrics buffering (send everything at 1min, or at buffer size), easy to see path to use the `reqwest_retry` using retry mechanism, etc.
The per-tenant tasks would be able to measure if we are keeping up with the goal of collecting all metrics every 5min, and have no leaks. | 1.0 | Consumption metrics faster after restart - Right now we start to collect consumption metrics every N minutes, and calculate synthetic size every M minutes for all tenants in sequence (order unspecified). In default config N == M, so there is a change that on first rounds after the restart:
1. upload may have some synthetic sizes
2. upload may will have some synthetic sizes
3. upload may will have most synthetic sizes
4. upload should have most if not all synthetic sizes
However, we now need due to external requirements reporting every N instead of possibly multiples of N. There have also been ideas of setting up an SLI for how often we upload the metrics -- I think the interesting case is "how often we upload these per tenant", not "how often a POST request goes out".
On #3542 I noticed that we also leak a bit of metrics for any detached tenants, as we never clear them. The problems with the current approach of listing all tenants and iterating them is that we lack the ability to clean things up once complete, or react to for example synthetic size calculation completing.
I think we should instead organize metrics sending so that:
- task to buffer and collected metrics is spawned
- each tenant gets a process collecting the metrics on tick, including synthetic size
- per tenant caching
- synthetic size has a global rate limit already
- synthetic size could be "ongoing" while other metrics are collected, and when it completes, we would just send it like other metrics to be buffered and sent
- on tenant deactivating, we would exit the task
- the top-level consumption metrics task
- spawning up new tasks for appeared tenants
- maintaining that we should *send over* the cached metrics every K minutes by signalling all per-tenant collectors
I think this design would allow us fine grained control over metrics buffering (send everything at 1min, or at buffer size), easy to see path to use the `reqwest_retry` using retry mechanism, etc.
The per-tenant tasks would be able to measure if we are keeping up with the goal of collecting all metrics every 5min, and have no leaks. | non_defect | consumption metrics faster after restart right now we start to collect consumption metrics every n minutes and calculate synthetic size every m minutes for all tenants in sequence order unspecified in default config n m so there is a change that on first rounds after the restart upload may have some synthetic sizes upload may will have some synthetic sizes upload may will have most synthetic sizes upload should have most if not all synthetic sizes however we now need due to external requirements reporting every n instead of possibly multiples of n there have also been ideas of setting up an sli for how often we upload the metrics i think the interesting case is how often we upload these per tenant not how often a post request goes out on i noticed that we also leak a bit of metrics for any detached tenants as we never clear them the problems with the current approach of listing all tenants and iterating them is that we lack the ability to clean things up once complete or react to for example synthetic size calculation completing i think we should instead organize metrics sending so that task to buffer and collected metrics is spawned each tenant gets a process collecting the metrics on tick including synthetic size per tenant caching synthetic size has a global rate limit already synthetic size could be ongoing while other metrics are collected and when it completes we would just send it like other metrics to be buffered and sent on tenant deactivating we would exit the task the top level consumption metrics task spawning up new tasks for appeared tenants maintaining that we should send over the cached metrics every k minutes by signalling all per tenant collectors i think this design would allow us fine grained control over metrics buffering send everything at or at buffer size easy to see path to use the reqwest retry using retry mechanism etc the per tenant tasks would be able to measure if we are keeping up with the goal of collecting all metrics every and have no leaks | 0 |
180,056 | 6,642,913,861 | IssuesEvent | 2017-09-27 09:17:36 | EyeSeeTea/pictureapp | https://api.github.com/repos/EyeSeeTea/pictureapp | closed | Migrate to eReferrals the new fix to language selection issue | complexity - low (1hr) eReferrals priority - critical type - bug | English does not exist in language selection, so there's no way to select it. In a nutshell, just bring to pictureapp what was done in [this malariapp PR](https://github.com/EyeSeeTea/malariapp/pull/1599) | 1.0 | Migrate to eReferrals the new fix to language selection issue - English does not exist in language selection, so there's no way to select it. In a nutshell, just bring to pictureapp what was done in [this malariapp PR](https://github.com/EyeSeeTea/malariapp/pull/1599) | non_defect | migrate to ereferrals the new fix to language selection issue english does not exist in language selection so there s no way to select it in a nutshell just bring to pictureapp what was done in | 0 |
23,988 | 3,883,363,962 | IssuesEvent | 2016-04-13 13:39:15 | svnpenn/mp4v2 | https://api.github.com/repos/svnpenn/mp4v2 | closed | Enhancement: Python API for mp4v2 | auto-migrated Priority-Medium Type-Defect | ```
I've written a Python API using cython for the mp4v2 public API.
It's a first draft, but pretty much done. Need to finish up the unittests to
tease out any remaining
bugs and probably add some more detailed comments.
Would this be something the project would be interested in adding to their
library?
-james
```
Original issue reported on code.google.com by `kru...@gmail.com` on 24 Nov 2009 at 2:31 | 1.0 | Enhancement: Python API for mp4v2 - ```
I've written a Python API using cython for the mp4v2 public API.
It's a first draft, but pretty much done. Need to finish up the unittests to
tease out any remaining
bugs and probably add some more detailed comments.
Would this be something the project would be interested in adding to their
library?
-james
```
Original issue reported on code.google.com by `kru...@gmail.com` on 24 Nov 2009 at 2:31 | defect | enhancement python api for i ve written a python api using cython for the public api it s a first draft but pretty much done need to finish up the unittests to tease out any remaining bugs and probably add some more detailed comments would this be something the project would be interested in adding to their library james original issue reported on code google com by kru gmail com on nov at | 1 |
56,202 | 14,978,013,192 | IssuesEvent | 2021-01-28 10:15:50 | vim/vim | https://api.github.com/repos/vim/vim | closed | Patch 475 - Can't compile on a system where Xutf8SetWMProperties() - on AIX 6.1 | Priority-Medium auto-migrated defect | ```
What steps will reproduce the problem? two steps, configure and make :
1. The command:
./configure --with-features=huge --enable-gui=no
works, a few output lines :
configure: creating cache auto/config.cache
checking whether make sets $(MAKE)... yes
checking for gcc... no
checking for cc... cc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... no
checking whether cc accepts -g... yes
checking for cc option to accept ISO C89... -qlanglvl=extc89
checking how to run the C preprocessor... cc -qlanglvl=extc89 -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for library containing strerror... none required
checking for gawk... no
checking for mawk... no
checking for nawk... nawk
checking for strip... strip
checking for ANSI C header files... yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking --enable-fail-if-missing argument... no
checking for recent clang version... no
configure: checking for buggy tools...
checking for BeOS... no
...
checking whether Xutf8SetWMProperties() can be used... no
checking for _xpg4_setrunelocale in -lxpg4... no
checking how to create tags... ctags -t
checking how to run man with a section nr... man
checking --disable-nls argument... no
checking for msgfmt... no
checking for NLS... msgfmt not found - disabled
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for dlopen()... yes
checking for dlsym()... yes
checking setjmp.h usability... yes
checking setjmp.h presence... yes
checking for setjmp.h... yes
checking linker --as-needed support... no
configure: updating cache auto/config.cache
configure: creating auto/config.status
config.status: creating auto/config.mk
config.status: creating auto/config.h
2. The "make" command, it re-execute configure, compile and stop with an error,
the output:
Starting make in the src directory.
If there are problems, cd to the src directory and run make there
cd src && make first
rm -f auto/config.cache
if test "X" != "Xclean" -a "X" != "Xdistclean" -a "X" != "Xautoconf" -a "X" != "Xreconfig"; then GUI_INC_LOC="" GUI_LIB_LOC="" CC="cc -qlanglvl=extc89" CPPFLAGS="" CFLAGS="-g" LDFLAGS="" srcdir="." ./configure ; fi
configure: creating cache auto/config.cache
checking whether make sets $(MAKE)... yes
checking for gcc... cc -qlanglvl=extc89
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... no
checking whether cc -qlanglvl=extc89 accepts -g... yes
checking for cc -qlanglvl=extc89 option to accept ISO C89... none needed
checking how to run the C preprocessor... cc -qlanglvl=extc89 -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for library containing strerror... none required
checking for gawk... no
checking for mawk... no
checking for nawk... nawk
checking for strip... strip
checking for ANSI C header files... yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking --enable-fail-if-missing argument... no
checking for recent clang version... no
configure: checking for buggy tools...
checking for BeOS... no
checking for QNX... no
checking for Darwin (Mac OS X)... no
checking AvailabilityMacros.h usability... no
checking AvailabilityMacros.h presence... no
checking for AvailabilityMacros.h... no
checking --with-local-dir argument... Defaulting to /usr/local
checking --with-vim-name argument... Defaulting to vim
checking --with-ex-name argument... Defaulting to ex
checking --with-view-name argument... Defaulting to view
checking --with-global-runtime argument... no
checking --with-modified-by argument... no
checking if character set is EBCDIC... no
checking --disable-smack argument... no
checking linux/xattr.h usability... no
checking linux/xattr.h presence... no
checking for linux/xattr.h... no
checking --disable-selinux argument... no
checking for is_selinux_enabled in -lselinux... no
checking --with-features argument... Defaulting to normal
checking --with-compiledby argument... no
checking --disable-xsmp argument... no
checking --disable-xsmp-interact argument... no
checking --enable-luainterp argument... no
checking --enable-mzschemeinterp argument... no
checking --enable-perlinterp argument... no
checking --enable-pythoninterp argument... no
checking --enable-python3interp argument... no
checking --enable-tclinterp argument... no
checking --enable-rubyinterp argument... no
checking --enable-cscope argument... no
checking --enable-workshop argument... no
checking --disable-netbeans argument... no
checking for socket in -lsocket... no
checking for gethostbyname in -lnsl... yes
checking whether compiling netbeans integration is possible... yes
checking --enable-sniff argument... no
checking --enable-multibyte argument... no
checking --enable-hangulinput argument... no
checking --enable-xim argument... defaulting to auto
checking --enable-fontset argument... no
checking for xmkmf... /usr/bin/X11/xmkmf
checking for X... libraries , headers
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
checking if X11 header files can be found... yes
checking for _XdmcpAuthDoIt in -lXdmcp... no
checking for IceOpenConnection in -lICE... no
checking for XpmCreatePixmapFromData in -lXpm... yes
checking if X11 header files implicitly declare return values... no
checking size of wchar_t is 2 bytes... no
checking --enable-gui argument... yes/auto - automatic GUI support
checking whether or not to look for GTK+ 2... yes
checking whether or not to look for GNOME... no
checking whether or not to look for Motif... yes
checking whether or not to look for Athena... yes
checking whether or not to look for neXtaw... yes
checking whether or not to look for Carbon... yes
checking --disable-gtktest argument... gtk test enabled
checking for pkg-config... no
checking for location of Motif GUI includes... <not found>
checking if Athena header files can be found... yes
checking if neXtaw header files can be found... no
checking for XShapeQueryExtension in -lXext... yes
checking for wslen in -lw... no
checking for dlsym in -ldl... yes
checking for XmuCreateStippledPixmap in -lXmu... yes
checking for extra X11 defines... -DFUNCPROTO=15
checking X11/SM/SMlib.h usability... yes
checking X11/SM/SMlib.h presence... yes
checking for X11/SM/SMlib.h... yes
checking X11/xpm.h usability... yes
checking X11/xpm.h presence... yes
checking for X11/xpm.h... yes
checking X11/Sunkeysym.h usability... yes
checking X11/Sunkeysym.h presence... yes
checking for X11/Sunkeysym.h... yes
checking for XIMText in X11/Xlib.h... yes
X GUI selected; xim has been enabled
checking for X11/Xmu/Editres.h... yes
checking for CYGWIN environment... no
checking whether toupper is broken... no
checking whether __DATE__ and __TIME__ work... yes
checking whether __attribute__((unused)) is allowed... yes
checking elf.h usability... no
checking elf.h presence... no
checking for elf.h... no
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking stdarg.h usability... yes
checking stdarg.h presence... yes
checking for stdarg.h... yes
checking stdint.h usability... yes
checking stdint.h presence... yes
checking for stdint.h... yes
checking stdlib.h usability... yes
checking stdlib.h presence... yes
checking for stdlib.h... yes
checking string.h usability... yes
checking string.h presence... yes
checking for string.h... yes
checking sys/select.h usability... yes
checking sys/select.h presence... yes
checking for sys/select.h... yes
checking sys/utsname.h usability... yes
checking sys/utsname.h presence... yes
checking for sys/utsname.h... yes
checking termcap.h usability... no
checking termcap.h presence... no
checking for termcap.h... no
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking sgtty.h usability... yes
checking sgtty.h presence... yes
checking for sgtty.h... yes
checking sys/ioctl.h usability... yes
checking sys/ioctl.h presence... yes
checking for sys/ioctl.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking sys/types.h usability... yes
checking sys/types.h presence... yes
checking for sys/types.h... yes
checking termio.h usability... yes
checking termio.h presence... yes
checking for termio.h... yes
checking iconv.h usability... yes
checking iconv.h presence... yes
checking for iconv.h... yes
checking inttypes.h usability... yes
checking inttypes.h presence... yes
checking for inttypes.h... yes
checking langinfo.h usability... yes
checking langinfo.h presence... yes
checking for langinfo.h... yes
checking math.h usability... yes
checking math.h presence... yes
checking for math.h... yes
checking unistd.h usability... yes
checking unistd.h presence... yes
checking for unistd.h... yes
checking stropts.h usability... yes
checking stropts.h presence... yes
checking for stropts.h... yes
checking errno.h usability... yes
checking errno.h presence... yes
checking for errno.h... yes
checking sys/resource.h usability... yes
checking sys/resource.h presence... yes
checking for sys/resource.h... yes
checking sys/systeminfo.h usability... no
checking sys/systeminfo.h presence... no
checking for sys/systeminfo.h... no
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking sys/stream.h usability... yes
checking sys/stream.h presence... yes
checking for sys/stream.h... yes
checking termios.h usability... yes
checking termios.h presence... yes
checking for termios.h... yes
checking libc.h usability... no
checking libc.h presence... no
checking for libc.h... no
checking sys/statfs.h usability... yes
checking sys/statfs.h presence... yes
checking for sys/statfs.h... yes
checking poll.h usability... yes
checking poll.h presence... yes
checking for poll.h... yes
checking sys/poll.h usability... yes
checking sys/poll.h presence... yes
checking for sys/poll.h... yes
checking pwd.h usability... yes
checking pwd.h presence... yes
checking for pwd.h... yes
checking utime.h usability... yes
checking utime.h presence... yes
checking for utime.h... yes
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking libintl.h usability... no
checking libintl.h presence... no
checking for libintl.h... no
checking libgen.h usability... yes
checking libgen.h presence... yes
checking for libgen.h... yes
checking util/debug.h usability... no
checking util/debug.h presence... no
checking for util/debug.h... no
checking util/msg18n.h usability... no
checking util/msg18n.h presence... no
checking for util/msg18n.h... no
checking frame.h usability... no
checking frame.h presence... no
checking for frame.h... no
checking sys/acl.h usability... yes
checking sys/acl.h presence... yes
checking for sys/acl.h... yes
checking sys/access.h usability... yes
checking sys/access.h presence... yes
checking for sys/access.h... yes
checking sys/sysinfo.h usability... yes
checking sys/sysinfo.h presence... yes
checking for sys/sysinfo.h... yes
checking wchar.h usability... yes
checking wchar.h presence... yes
checking for wchar.h... yes
checking wctype.h usability... yes
checking wctype.h presence... yes
checking for wctype.h... yes
checking for sys/ptem.h... no
checking for sys/sysctl.h... no
checking for pthread_np.h... no
checking strings.h usability... yes
checking strings.h presence... yes
checking for strings.h... yes
checking if strings.h can be included after string.h... yes
checking for an ANSI C-conforming const... yes
checking for working volatile... yes
checking for mode_t... yes
checking for off_t... yes
checking for pid_t... yes
checking for size_t... yes
checking for uid_t in sys/types.h... yes
checking for uint32_t... yes
checking whether time.h and sys/time.h may both be included... yes
checking for ino_t... yes
checking for dev_t... yes
checking whether byte ordering is bigendian... yes
checking for rlim_t... yes
checking for stack_t... yes
checking whether stack_t has an ss_base field... no
checking --with-tlib argument... empty: automatic terminal library selection
checking for tgetent in -ltinfo... no
checking for tgetent in -lncurses... no
checking for tgetent in -ltermlib... no
checking for tgetent in -ltermcap... no
checking for tgetent in -lcurses... yes
checking whether we talk terminfo... yes
checking what tgetent() returns for an unknown terminal... zero
checking whether termcap.h contains ospeed... no
checking whether ospeed can be extern... yes
checking whether termcap.h contains UP, BC and PC... no
checking whether UP, BC and PC can be extern... no
checking whether tputs() uses outfuntype... no
checking whether sys/select.h and sys/time.h may both be included... yes
checking for /dev/ptc... yes
checking for SVR4 ptys... no
checking for ptyranges... p / 0123456789abcdef
checking default tty permissions/group... can't determine - assume ptys are
world accessible
world
checking return type of signal handlers... void
checking for struct sigcontext... yes
checking getcwd implementation is broken... no
checking for bcmp... yes
checking for fchdir... yes
checking for fchown... yes
checking for fsync... yes
checking for getcwd... yes
checking for getpseudotty... no
checking for getpwent... yes
checking for getpwnam... yes
checking for getpwuid... yes
checking for getrlimit... yes
checking for gettimeofday... yes
checking for getwd... yes
checking for lstat... yes
checking for memcmp... yes
checking for memset... yes
checking for mkdtemp... yes
checking for nanosleep... yes
checking for opendir... yes
checking for putenv... yes
checking for qsort... yes
checking for readlink... yes
checking for select... yes
checking for setenv... yes
checking for setpgid... yes
checking for setsid... yes
checking for sigaltstack... yes
checking for sigstack... yes
checking for sigset... yes
checking for sigsetjmp... yes
checking for sigaction... yes
checking for sigvec... yes
checking for strcasecmp... yes
checking for strerror... yes
checking for strftime... yes
checking for stricmp... no
checking for strncasecmp... yes
checking for strnicmp... no
checking for strpbrk... yes
checking for strtol... yes
checking for tgetent... yes
checking for towlower... yes
checking for towupper... yes
checking for iswupper... yes
checking for usleep... yes
checking for utime... yes
checking for utimes... yes
checking for _LARGEFILE_SOURCE value needed for large files... no
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking for st_blksize... yes
checking whether stat() ignores a trailing slash... yes
checking for iconv_open()... yes; with -liconv
checking for nl_langinfo(CODESET)... yes
checking for strtod in -lm... yes
checking for strtod() and other floating point functions... yes
checking --disable-acl argument... no
checking for acl_get_file in -lposix1e... no
checking for acl_get_file in -lacl... no
checking for POSIX ACL support... no
checking for acl_get in -lsec... no
checking for Solaris ACL support... no
checking for AIX ACL support... yes
checking --disable-gpm argument... no
checking for gpm... no
checking --disable-sysmouse argument... no
checking for sysmouse... no
checking for FD_CLOEXEC... yes
checking for rename... yes
checking for sysctl... not usable
checking for sysinfo... not usable
checking for sysinfo.mem_unit... no
checking for sysconf... yes
checking size of int... 4
checking size of long... 8
checking size of time_t... 8
checking size of off_t... 8
checking uint32_t is 32 bits... ok
checking whether memmove handles overlaps... yes
checking whether X_LOCALE needed... no
checking whether Xutf8SetWMProperties() can be used... no
checking for _xpg4_setrunelocale in -lxpg4... no
checking how to create tags... ctags -t
checking how to run man with a section nr... man
checking --disable-nls argument... no
checking for msgfmt... no
checking for NLS... msgfmt not found - disabled
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for dlopen()... yes
checking for dlsym()... yes
checking setjmp.h usability... yes
checking setjmp.h presence... yes
checking for setjmp.h... yes
checking linker --as-needed support... no
configure: updating cache auto/config.cache
configure: creating auto/config.status
config.status: creating auto/config.mk
config.status: creating auto/config.h
CC="cc -qlanglvl=extc89 -Iproto -DHAVE_CONFIG_H " srcdir=. sh ./osdef.sh
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/buffer.o buffer.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/blowfish.o blowfish.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/charset.o charset.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/crypt.o crypt.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/crypt_zip.o crypt_zip.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/diff.o diff.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/digraph.o digraph.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/edit.o edit.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/eval.o eval.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/ex_cmds.o ex_cmds.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/ex_cmds2.o ex_cmds2.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/ex_docmd.o ex_docmd.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/ex_eval.o ex_eval.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/ex_getln.o ex_getln.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/fileio.o fileio.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/fold.o fold.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/getchar.o getchar.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/hardcopy.o hardcopy.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/hashtab.o hashtab.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/if_cscope.o if_cscope.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/if_xcmdsrv.o if_xcmdsrv.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/mark.o mark.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/memline.o memline.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/menu.o menu.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/message.o message.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/misc1.o misc1.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/misc2.o misc2.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/move.o move.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/mbyte.o mbyte.c
"mbyte.c", line 5327.14: 1506-045 (S) Undeclared identifier input_style.
"mbyte.c", line 5410.9: 1506-045 (S) Undeclared identifier input_style.
"mbyte.c", line 5412.13: 1506-045 (S) Undeclared identifier xim_fg_color.
"mbyte.c", line 5412.29: 1506-045 (S) Undeclared identifier INVALCOLOR.
"mbyte.c", line 5414.28: 1506-045 (S) Undeclared identifier gui.
"mbyte.c", line 5415.13: 1506-045 (S) Undeclared identifier xim_bg_color.
"mbyte.c", line 5779.9: 1506-045 (S) Undeclared identifier input_style.
"mbyte.c", line 5794.33: 1506-045 (S) Undeclared identifier gui.
"mbyte.c", line 5870.9: 1506-045 (S) Undeclared identifier status_area_enabled.
"mbyte.c", line 5871.16: 1506-045 (S) Undeclared identifier gui.
make: The error code from the last command is 1.
Stop.
make: The error code from the last command is 2.
Stop.
3.
What is the expected output?
Compile and create the vim binary file.
What do you see instead?
The error above.
What version of the product are you using? On what operating system?
Vim 7.4.475 on Aix 6.1
C compiler version:
]xlc -qversion
IBM XL C/C++ for AIX, V11.1 (5724-X13)
Version: 11.01.0000.0006
```
Original issue reported on code.google.com by `Zulolox4...@gmail.com` on 13 Oct 2014 at 7:30
| 1.0 | Patch 475 - Can't compile on a system where Xutf8SetWMProperties() - on AIX 6.1 - ```
What steps will reproduce the problem? two steps, configure and make :
1. The command:
./configure --with-features=huge --enable-gui=no
works, a few output lines :
configure: creating cache auto/config.cache
checking whether make sets $(MAKE)... yes
checking for gcc... no
checking for cc... cc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... no
checking whether cc accepts -g... yes
checking for cc option to accept ISO C89... -qlanglvl=extc89
checking how to run the C preprocessor... cc -qlanglvl=extc89 -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for library containing strerror... none required
checking for gawk... no
checking for mawk... no
checking for nawk... nawk
checking for strip... strip
checking for ANSI C header files... yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking --enable-fail-if-missing argument... no
checking for recent clang version... no
configure: checking for buggy tools...
checking for BeOS... no
...
checking whether Xutf8SetWMProperties() can be used... no
checking for _xpg4_setrunelocale in -lxpg4... no
checking how to create tags... ctags -t
checking how to run man with a section nr... man
checking --disable-nls argument... no
checking for msgfmt... no
checking for NLS... msgfmt not found - disabled
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for dlopen()... yes
checking for dlsym()... yes
checking setjmp.h usability... yes
checking setjmp.h presence... yes
checking for setjmp.h... yes
checking linker --as-needed support... no
configure: updating cache auto/config.cache
configure: creating auto/config.status
config.status: creating auto/config.mk
config.status: creating auto/config.h
2. The "make" command, it re-execute configure, compile and stop with an error,
the output:
Starting make in the src directory.
If there are problems, cd to the src directory and run make there
cd src && make first
rm -f auto/config.cache
if test "X" != "Xclean" -a "X" != "Xdistclean" -a "X" != "Xautoconf" -a "X" != "Xreconfig"; then GUI_INC_LOC="" GUI_LIB_LOC="" CC="cc -qlanglvl=extc89" CPPFLAGS="" CFLAGS="-g" LDFLAGS="" srcdir="." ./configure ; fi
configure: creating cache auto/config.cache
checking whether make sets $(MAKE)... yes
checking for gcc... cc -qlanglvl=extc89
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... no
checking whether cc -qlanglvl=extc89 accepts -g... yes
checking for cc -qlanglvl=extc89 option to accept ISO C89... none needed
checking how to run the C preprocessor... cc -qlanglvl=extc89 -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for library containing strerror... none required
checking for gawk... no
checking for mawk... no
checking for nawk... nawk
checking for strip... strip
checking for ANSI C header files... yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking --enable-fail-if-missing argument... no
checking for recent clang version... no
configure: checking for buggy tools...
checking for BeOS... no
checking for QNX... no
checking for Darwin (Mac OS X)... no
checking AvailabilityMacros.h usability... no
checking AvailabilityMacros.h presence... no
checking for AvailabilityMacros.h... no
checking --with-local-dir argument... Defaulting to /usr/local
checking --with-vim-name argument... Defaulting to vim
checking --with-ex-name argument... Defaulting to ex
checking --with-view-name argument... Defaulting to view
checking --with-global-runtime argument... no
checking --with-modified-by argument... no
checking if character set is EBCDIC... no
checking --disable-smack argument... no
checking linux/xattr.h usability... no
checking linux/xattr.h presence... no
checking for linux/xattr.h... no
checking --disable-selinux argument... no
checking for is_selinux_enabled in -lselinux... no
checking --with-features argument... Defaulting to normal
checking --with-compiledby argument... no
checking --disable-xsmp argument... no
checking --disable-xsmp-interact argument... no
checking --enable-luainterp argument... no
checking --enable-mzschemeinterp argument... no
checking --enable-perlinterp argument... no
checking --enable-pythoninterp argument... no
checking --enable-python3interp argument... no
checking --enable-tclinterp argument... no
checking --enable-rubyinterp argument... no
checking --enable-cscope argument... no
checking --enable-workshop argument... no
checking --disable-netbeans argument... no
checking for socket in -lsocket... no
checking for gethostbyname in -lnsl... yes
checking whether compiling netbeans integration is possible... yes
checking --enable-sniff argument... no
checking --enable-multibyte argument... no
checking --enable-hangulinput argument... no
checking --enable-xim argument... defaulting to auto
checking --enable-fontset argument... no
checking for xmkmf... /usr/bin/X11/xmkmf
checking for X... libraries , headers
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
checking if X11 header files can be found... yes
checking for _XdmcpAuthDoIt in -lXdmcp... no
checking for IceOpenConnection in -lICE... no
checking for XpmCreatePixmapFromData in -lXpm... yes
checking if X11 header files implicitly declare return values... no
checking size of wchar_t is 2 bytes... no
checking --enable-gui argument... yes/auto - automatic GUI support
checking whether or not to look for GTK+ 2... yes
checking whether or not to look for GNOME... no
checking whether or not to look for Motif... yes
checking whether or not to look for Athena... yes
checking whether or not to look for neXtaw... yes
checking whether or not to look for Carbon... yes
checking --disable-gtktest argument... gtk test enabled
checking for pkg-config... no
checking for location of Motif GUI includes... <not found>
checking if Athena header files can be found... yes
checking if neXtaw header files can be found... no
checking for XShapeQueryExtension in -lXext... yes
checking for wslen in -lw... no
checking for dlsym in -ldl... yes
checking for XmuCreateStippledPixmap in -lXmu... yes
checking for extra X11 defines... -DFUNCPROTO=15
checking X11/SM/SMlib.h usability... yes
checking X11/SM/SMlib.h presence... yes
checking for X11/SM/SMlib.h... yes
checking X11/xpm.h usability... yes
checking X11/xpm.h presence... yes
checking for X11/xpm.h... yes
checking X11/Sunkeysym.h usability... yes
checking X11/Sunkeysym.h presence... yes
checking for X11/Sunkeysym.h... yes
checking for XIMText in X11/Xlib.h... yes
X GUI selected; xim has been enabled
checking for X11/Xmu/Editres.h... yes
checking for CYGWIN environment... no
checking whether toupper is broken... no
checking whether __DATE__ and __TIME__ work... yes
checking whether __attribute__((unused)) is allowed... yes
checking elf.h usability... no
checking elf.h presence... no
checking for elf.h... no
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking stdarg.h usability... yes
checking stdarg.h presence... yes
checking for stdarg.h... yes
checking stdint.h usability... yes
checking stdint.h presence... yes
checking for stdint.h... yes
checking stdlib.h usability... yes
checking stdlib.h presence... yes
checking for stdlib.h... yes
checking string.h usability... yes
checking string.h presence... yes
checking for string.h... yes
checking sys/select.h usability... yes
checking sys/select.h presence... yes
checking for sys/select.h... yes
checking sys/utsname.h usability... yes
checking sys/utsname.h presence... yes
checking for sys/utsname.h... yes
checking termcap.h usability... no
checking termcap.h presence... no
checking for termcap.h... no
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking sgtty.h usability... yes
checking sgtty.h presence... yes
checking for sgtty.h... yes
checking sys/ioctl.h usability... yes
checking sys/ioctl.h presence... yes
checking for sys/ioctl.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking sys/types.h usability... yes
checking sys/types.h presence... yes
checking for sys/types.h... yes
checking termio.h usability... yes
checking termio.h presence... yes
checking for termio.h... yes
checking iconv.h usability... yes
checking iconv.h presence... yes
checking for iconv.h... yes
checking inttypes.h usability... yes
checking inttypes.h presence... yes
checking for inttypes.h... yes
checking langinfo.h usability... yes
checking langinfo.h presence... yes
checking for langinfo.h... yes
checking math.h usability... yes
checking math.h presence... yes
checking for math.h... yes
checking unistd.h usability... yes
checking unistd.h presence... yes
checking for unistd.h... yes
checking stropts.h usability... yes
checking stropts.h presence... yes
checking for stropts.h... yes
checking errno.h usability... yes
checking errno.h presence... yes
checking for errno.h... yes
checking sys/resource.h usability... yes
checking sys/resource.h presence... yes
checking for sys/resource.h... yes
checking sys/systeminfo.h usability... no
checking sys/systeminfo.h presence... no
checking for sys/systeminfo.h... no
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking sys/stream.h usability... yes
checking sys/stream.h presence... yes
checking for sys/stream.h... yes
checking termios.h usability... yes
checking termios.h presence... yes
checking for termios.h... yes
checking libc.h usability... no
checking libc.h presence... no
checking for libc.h... no
checking sys/statfs.h usability... yes
checking sys/statfs.h presence... yes
checking for sys/statfs.h... yes
checking poll.h usability... yes
checking poll.h presence... yes
checking for poll.h... yes
checking sys/poll.h usability... yes
checking sys/poll.h presence... yes
checking for sys/poll.h... yes
checking pwd.h usability... yes
checking pwd.h presence... yes
checking for pwd.h... yes
checking utime.h usability... yes
checking utime.h presence... yes
checking for utime.h... yes
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking libintl.h usability... no
checking libintl.h presence... no
checking for libintl.h... no
checking libgen.h usability... yes
checking libgen.h presence... yes
checking for libgen.h... yes
checking util/debug.h usability... no
checking util/debug.h presence... no
checking for util/debug.h... no
checking util/msg18n.h usability... no
checking util/msg18n.h presence... no
checking for util/msg18n.h... no
checking frame.h usability... no
checking frame.h presence... no
checking for frame.h... no
checking sys/acl.h usability... yes
checking sys/acl.h presence... yes
checking for sys/acl.h... yes
checking sys/access.h usability... yes
checking sys/access.h presence... yes
checking for sys/access.h... yes
checking sys/sysinfo.h usability... yes
checking sys/sysinfo.h presence... yes
checking for sys/sysinfo.h... yes
checking wchar.h usability... yes
checking wchar.h presence... yes
checking for wchar.h... yes
checking wctype.h usability... yes
checking wctype.h presence... yes
checking for wctype.h... yes
checking for sys/ptem.h... no
checking for sys/sysctl.h... no
checking for pthread_np.h... no
checking strings.h usability... yes
checking strings.h presence... yes
checking for strings.h... yes
checking if strings.h can be included after string.h... yes
checking for an ANSI C-conforming const... yes
checking for working volatile... yes
checking for mode_t... yes
checking for off_t... yes
checking for pid_t... yes
checking for size_t... yes
checking for uid_t in sys/types.h... yes
checking for uint32_t... yes
checking whether time.h and sys/time.h may both be included... yes
checking for ino_t... yes
checking for dev_t... yes
checking whether byte ordering is bigendian... yes
checking for rlim_t... yes
checking for stack_t... yes
checking whether stack_t has an ss_base field... no
checking --with-tlib argument... empty: automatic terminal library selection
checking for tgetent in -ltinfo... no
checking for tgetent in -lncurses... no
checking for tgetent in -ltermlib... no
checking for tgetent in -ltermcap... no
checking for tgetent in -lcurses... yes
checking whether we talk terminfo... yes
checking what tgetent() returns for an unknown terminal... zero
checking whether termcap.h contains ospeed... no
checking whether ospeed can be extern... yes
checking whether termcap.h contains UP, BC and PC... no
checking whether UP, BC and PC can be extern... no
checking whether tputs() uses outfuntype... no
checking whether sys/select.h and sys/time.h may both be included... yes
checking for /dev/ptc... yes
checking for SVR4 ptys... no
checking for ptyranges... p / 0123456789abcdef
checking default tty permissions/group... can't determine - assume ptys are
world accessible
world
checking return type of signal handlers... void
checking for struct sigcontext... yes
checking getcwd implementation is broken... no
checking for bcmp... yes
checking for fchdir... yes
checking for fchown... yes
checking for fsync... yes
checking for getcwd... yes
checking for getpseudotty... no
checking for getpwent... yes
checking for getpwnam... yes
checking for getpwuid... yes
checking for getrlimit... yes
checking for gettimeofday... yes
checking for getwd... yes
checking for lstat... yes
checking for memcmp... yes
checking for memset... yes
checking for mkdtemp... yes
checking for nanosleep... yes
checking for opendir... yes
checking for putenv... yes
checking for qsort... yes
checking for readlink... yes
checking for select... yes
checking for setenv... yes
checking for setpgid... yes
checking for setsid... yes
checking for sigaltstack... yes
checking for sigstack... yes
checking for sigset... yes
checking for sigsetjmp... yes
checking for sigaction... yes
checking for sigvec... yes
checking for strcasecmp... yes
checking for strerror... yes
checking for strftime... yes
checking for stricmp... no
checking for strncasecmp... yes
checking for strnicmp... no
checking for strpbrk... yes
checking for strtol... yes
checking for tgetent... yes
checking for towlower... yes
checking for towupper... yes
checking for iswupper... yes
checking for usleep... yes
checking for utime... yes
checking for utimes... yes
checking for _LARGEFILE_SOURCE value needed for large files... no
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking for st_blksize... yes
checking whether stat() ignores a trailing slash... yes
checking for iconv_open()... yes; with -liconv
checking for nl_langinfo(CODESET)... yes
checking for strtod in -lm... yes
checking for strtod() and other floating point functions... yes
checking --disable-acl argument... no
checking for acl_get_file in -lposix1e... no
checking for acl_get_file in -lacl... no
checking for POSIX ACL support... no
checking for acl_get in -lsec... no
checking for Solaris ACL support... no
checking for AIX ACL support... yes
checking --disable-gpm argument... no
checking for gpm... no
checking --disable-sysmouse argument... no
checking for sysmouse... no
checking for FD_CLOEXEC... yes
checking for rename... yes
checking for sysctl... not usable
checking for sysinfo... not usable
checking for sysinfo.mem_unit... no
checking for sysconf... yes
checking size of int... 4
checking size of long... 8
checking size of time_t... 8
checking size of off_t... 8
checking uint32_t is 32 bits... ok
checking whether memmove handles overlaps... yes
checking whether X_LOCALE needed... no
checking whether Xutf8SetWMProperties() can be used... no
checking for _xpg4_setrunelocale in -lxpg4... no
checking how to create tags... ctags -t
checking how to run man with a section nr... man
checking --disable-nls argument... no
checking for msgfmt... no
checking for NLS... msgfmt not found - disabled
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for dlopen()... yes
checking for dlsym()... yes
checking setjmp.h usability... yes
checking setjmp.h presence... yes
checking for setjmp.h... yes
checking linker --as-needed support... no
configure: updating cache auto/config.cache
configure: creating auto/config.status
config.status: creating auto/config.mk
config.status: creating auto/config.h
CC="cc -qlanglvl=extc89 -Iproto -DHAVE_CONFIG_H " srcdir=. sh ./osdef.sh
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/buffer.o buffer.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/blowfish.o blowfish.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/charset.o charset.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/crypt.o crypt.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/crypt_zip.o crypt_zip.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/diff.o diff.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/digraph.o digraph.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/edit.o edit.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/eval.o eval.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/ex_cmds.o ex_cmds.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/ex_cmds2.o ex_cmds2.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/ex_docmd.o ex_docmd.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/ex_eval.o ex_eval.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/ex_getln.o ex_getln.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/fileio.o fileio.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/fold.o fold.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/getchar.o getchar.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/hardcopy.o hardcopy.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/hashtab.o hashtab.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/if_cscope.o if_cscope.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/if_xcmdsrv.o if_xcmdsrv.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/mark.o mark.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/memline.o memline.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/menu.o menu.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/message.o message.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/misc1.o misc1.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/misc2.o misc2.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/move.o move.c
cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g -o objects/mbyte.o mbyte.c
"mbyte.c", line 5327.14: 1506-045 (S) Undeclared identifier input_style.
"mbyte.c", line 5410.9: 1506-045 (S) Undeclared identifier input_style.
"mbyte.c", line 5412.13: 1506-045 (S) Undeclared identifier xim_fg_color.
"mbyte.c", line 5412.29: 1506-045 (S) Undeclared identifier INVALCOLOR.
"mbyte.c", line 5414.28: 1506-045 (S) Undeclared identifier gui.
"mbyte.c", line 5415.13: 1506-045 (S) Undeclared identifier xim_bg_color.
"mbyte.c", line 5779.9: 1506-045 (S) Undeclared identifier input_style.
"mbyte.c", line 5794.33: 1506-045 (S) Undeclared identifier gui.
"mbyte.c", line 5870.9: 1506-045 (S) Undeclared identifier status_area_enabled.
"mbyte.c", line 5871.16: 1506-045 (S) Undeclared identifier gui.
make: The error code from the last command is 1.
Stop.
make: The error code from the last command is 2.
Stop.
3.
What is the expected output?
Compile and create the vim binary file.
What do you see instead?
The error above.
What version of the product are you using? On what operating system?
Vim 7.4.475 on Aix 6.1
C compiler version:
]xlc -qversion
IBM XL C/C++ for AIX, V11.1 (5724-X13)
Version: 11.01.0000.0006
```
Original issue reported on code.google.com by `Zulolox4...@gmail.com` on 13 Oct 2014 at 7:30
| defect | patch can t compile on a system where on aix what steps will reproduce the problem two steps configure and make the command configure with features huge enable gui no works a few output lines configure creating cache auto config cache checking whether make sets make yes checking for gcc no checking for cc cc checking whether the c compiler works yes checking for c compiler default output file name a out checking for suffix of executables checking whether we are cross compiling no checking for suffix of object files o checking whether we are using the gnu c compiler no checking whether cc accepts g yes checking for cc option to accept iso qlanglvl checking how to run the c preprocessor cc qlanglvl e checking for grep that handles long lines and e usr bin grep checking for egrep usr bin grep e checking for fgrep usr bin grep f checking for library containing strerror none required checking for gawk no checking for mawk no checking for nawk nawk checking for strip strip checking for ansi c header files yes checking for sys wait h that is posix compatible yes checking enable fail if missing argument no checking for recent clang version no configure checking for buggy tools checking for beos no checking whether can be used no checking for setrunelocale in no checking how to create tags ctags t checking how to run man with a section nr man checking disable nls argument no checking for msgfmt no checking for nls msgfmt not found disabled checking dlfcn h usability yes checking dlfcn h presence yes checking for dlfcn h yes checking for dlopen yes checking for dlsym yes checking setjmp h usability yes checking setjmp h presence yes checking for setjmp h yes checking linker as needed support no configure updating cache auto config cache configure creating auto config status config status creating auto config mk config status creating auto config h the make command it re execute configure compile and stop with an error the output starting make in the src directory if there are problems cd to the src directory and run make there cd src make first rm f auto config cache if test x xclean a x xdistclean a x xautoconf a x xreconfig then gui inc loc gui lib loc cc cc qlanglvl cppflags cflags g ldflags srcdir configure fi configure creating cache auto config cache checking whether make sets make yes checking for gcc cc qlanglvl checking whether the c compiler works yes checking for c compiler default output file name a out checking for suffix of executables checking whether we are cross compiling no checking for suffix of object files o checking whether we are using the gnu c compiler no checking whether cc qlanglvl accepts g yes checking for cc qlanglvl option to accept iso none needed checking how to run the c preprocessor cc qlanglvl e checking for grep that handles long lines and e usr bin grep checking for egrep usr bin grep e checking for fgrep usr bin grep f checking for library containing strerror none required checking for gawk no checking for mawk no checking for nawk nawk checking for strip strip checking for ansi c header files yes checking for sys wait h that is posix compatible yes checking enable fail if missing argument no checking for recent clang version no configure checking for buggy tools checking for beos no checking for qnx no checking for darwin mac os x no checking availabilitymacros h usability no checking availabilitymacros h presence no checking for availabilitymacros h no checking with local dir argument defaulting to usr local checking with vim name argument defaulting to vim checking with ex name argument defaulting to ex checking with view name argument defaulting to view checking with global runtime argument no checking with modified by argument no checking if character set is ebcdic no checking disable smack argument no checking linux xattr h usability no checking linux xattr h presence no checking for linux xattr h no checking disable selinux argument no checking for is selinux enabled in lselinux no checking with features argument defaulting to normal checking with compiledby argument no checking disable xsmp argument no checking disable xsmp interact argument no checking enable luainterp argument no checking enable mzschemeinterp argument no checking enable perlinterp argument no checking enable pythoninterp argument no checking enable argument no checking enable tclinterp argument no checking enable rubyinterp argument no checking enable cscope argument no checking enable workshop argument no checking disable netbeans argument no checking for socket in lsocket no checking for gethostbyname in lnsl yes checking whether compiling netbeans integration is possible yes checking enable sniff argument no checking enable multibyte argument no checking enable hangulinput argument no checking enable xim argument defaulting to auto checking enable fontset argument no checking for xmkmf usr bin xmkmf checking for x libraries headers checking for gethostbyname yes checking for connect yes checking for remove yes checking for shmat yes checking for iceconnectionnumber in lice yes checking if header files can be found yes checking for xdmcpauthdoit in lxdmcp no checking for iceopenconnection in lice no checking for xpmcreatepixmapfromdata in lxpm yes checking if header files implicitly declare return values no checking size of wchar t is bytes no checking enable gui argument yes auto automatic gui support checking whether or not to look for gtk yes checking whether or not to look for gnome no checking whether or not to look for motif yes checking whether or not to look for athena yes checking whether or not to look for nextaw yes checking whether or not to look for carbon yes checking disable gtktest argument gtk test enabled checking for pkg config no checking for location of motif gui includes checking if athena header files can be found yes checking if nextaw header files can be found no checking for xshapequeryextension in lxext yes checking for wslen in lw no checking for dlsym in ldl yes checking for xmucreatestippledpixmap in lxmu yes checking for extra defines dfuncproto checking sm smlib h usability yes checking sm smlib h presence yes checking for sm smlib h yes checking xpm h usability yes checking xpm h presence yes checking for xpm h yes checking sunkeysym h usability yes checking sunkeysym h presence yes checking for sunkeysym h yes checking for ximtext in xlib h yes x gui selected xim has been enabled checking for xmu editres h yes checking for cygwin environment no checking whether toupper is broken no checking whether date and time work yes checking whether attribute unused is allowed yes checking elf h usability no checking elf h presence no checking for elf h no checking for dirent h that defines dir yes checking for library containing opendir none required checking stdarg h usability yes checking stdarg h presence yes checking for stdarg h yes checking stdint h usability yes checking stdint h presence yes checking for stdint h yes checking stdlib h usability yes checking stdlib h presence yes checking for stdlib h yes checking string h usability yes checking string h presence yes checking for string h yes checking sys select h usability yes checking sys select h presence yes checking for sys select h yes checking sys utsname h usability yes checking sys utsname h presence yes checking for sys utsname h yes checking termcap h usability no checking termcap h presence no checking for termcap h no checking fcntl h usability yes checking fcntl h presence yes checking for fcntl h yes checking sgtty h usability yes checking sgtty h presence yes checking for sgtty h yes checking sys ioctl h usability yes checking sys ioctl h presence yes checking for sys ioctl h yes checking sys time h usability yes checking sys time h presence yes checking for sys time h yes checking sys types h usability yes checking sys types h presence yes checking for sys types h yes checking termio h usability yes checking termio h presence yes checking for termio h yes checking iconv h usability yes checking iconv h presence yes checking for iconv h yes checking inttypes h usability yes checking inttypes h presence yes checking for inttypes h yes checking langinfo h usability yes checking langinfo h presence yes checking for langinfo h yes checking math h usability yes checking math h presence yes checking for math h yes checking unistd h usability yes checking unistd h presence yes checking for unistd h yes checking stropts h usability yes checking stropts h presence yes checking for stropts h yes checking errno h usability yes checking errno h presence yes checking for errno h yes checking sys resource h usability yes checking sys resource h presence yes checking for sys resource h yes checking sys systeminfo h usability no checking sys systeminfo h presence no checking for sys systeminfo h no checking locale h usability yes checking locale h presence yes checking for locale h yes checking sys stream h usability yes checking sys stream h presence yes checking for sys stream h yes checking termios h usability yes checking termios h presence yes checking for termios h yes checking libc h usability no checking libc h presence no checking for libc h no checking sys statfs h usability yes checking sys statfs h presence yes checking for sys statfs h yes checking poll h usability yes checking poll h presence yes checking for poll h yes checking sys poll h usability yes checking sys poll h presence yes checking for sys poll h yes checking pwd h usability yes checking pwd h presence yes checking for pwd h yes checking utime h usability yes checking utime h presence yes checking for utime h yes checking sys param h usability yes checking sys param h presence yes checking for sys param h yes checking libintl h usability no checking libintl h presence no checking for libintl h no checking libgen h usability yes checking libgen h presence yes checking for libgen h yes checking util debug h usability no checking util debug h presence no checking for util debug h no checking util h usability no checking util h presence no checking for util h no checking frame h usability no checking frame h presence no checking for frame h no checking sys acl h usability yes checking sys acl h presence yes checking for sys acl h yes checking sys access h usability yes checking sys access h presence yes checking for sys access h yes checking sys sysinfo h usability yes checking sys sysinfo h presence yes checking for sys sysinfo h yes checking wchar h usability yes checking wchar h presence yes checking for wchar h yes checking wctype h usability yes checking wctype h presence yes checking for wctype h yes checking for sys ptem h no checking for sys sysctl h no checking for pthread np h no checking strings h usability yes checking strings h presence yes checking for strings h yes checking if strings h can be included after string h yes checking for an ansi c conforming const yes checking for working volatile yes checking for mode t yes checking for off t yes checking for pid t yes checking for size t yes checking for uid t in sys types h yes checking for t yes checking whether time h and sys time h may both be included yes checking for ino t yes checking for dev t yes checking whether byte ordering is bigendian yes checking for rlim t yes checking for stack t yes checking whether stack t has an ss base field no checking with tlib argument empty automatic terminal library selection checking for tgetent in ltinfo no checking for tgetent in lncurses no checking for tgetent in ltermlib no checking for tgetent in ltermcap no checking for tgetent in lcurses yes checking whether we talk terminfo yes checking what tgetent returns for an unknown terminal zero checking whether termcap h contains ospeed no checking whether ospeed can be extern yes checking whether termcap h contains up bc and pc no checking whether up bc and pc can be extern no checking whether tputs uses outfuntype no checking whether sys select h and sys time h may both be included yes checking for dev ptc yes checking for ptys no checking for ptyranges p checking default tty permissions group can t determine assume ptys are world accessible world checking return type of signal handlers void checking for struct sigcontext yes checking getcwd implementation is broken no checking for bcmp yes checking for fchdir yes checking for fchown yes checking for fsync yes checking for getcwd yes checking for getpseudotty no checking for getpwent yes checking for getpwnam yes checking for getpwuid yes checking for getrlimit yes checking for gettimeofday yes checking for getwd yes checking for lstat yes checking for memcmp yes checking for memset yes checking for mkdtemp yes checking for nanosleep yes checking for opendir yes checking for putenv yes checking for qsort yes checking for readlink yes checking for select yes checking for setenv yes checking for setpgid yes checking for setsid yes checking for sigaltstack yes checking for sigstack yes checking for sigset yes checking for sigsetjmp yes checking for sigaction yes checking for sigvec yes checking for strcasecmp yes checking for strerror yes checking for strftime yes checking for stricmp no checking for strncasecmp yes checking for strnicmp no checking for strpbrk yes checking for strtol yes checking for tgetent yes checking for towlower yes checking for towupper yes checking for iswupper yes checking for usleep yes checking for utime yes checking for utimes yes checking for largefile source value needed for large files no checking for special c compiler options needed for large files no checking for file offset bits value needed for large files no checking for st blksize yes checking whether stat ignores a trailing slash yes checking for iconv open yes with liconv checking for nl langinfo codeset yes checking for strtod in lm yes checking for strtod and other floating point functions yes checking disable acl argument no checking for acl get file in no checking for acl get file in lacl no checking for posix acl support no checking for acl get in lsec no checking for solaris acl support no checking for aix acl support yes checking disable gpm argument no checking for gpm no checking disable sysmouse argument no checking for sysmouse no checking for fd cloexec yes checking for rename yes checking for sysctl not usable checking for sysinfo not usable checking for sysinfo mem unit no checking for sysconf yes checking size of int checking size of long checking size of time t checking size of off t checking t is bits ok checking whether memmove handles overlaps yes checking whether x locale needed no checking whether can be used no checking for setrunelocale in no checking how to create tags ctags t checking how to run man with a section nr man checking disable nls argument no checking for msgfmt no checking for nls msgfmt not found disabled checking dlfcn h usability yes checking dlfcn h presence yes checking for dlfcn h yes checking for dlopen yes checking for dlsym yes checking setjmp h usability yes checking setjmp h presence yes checking for setjmp h yes checking linker as needed support no configure updating cache auto config cache configure creating auto config status config status creating auto config mk config status creating auto config h cc cc qlanglvl iproto dhave config h srcdir sh osdef sh cc qlanglvl c i iproto dhave config h g o objects buffer o buffer c cc qlanglvl c i iproto dhave config h g o objects blowfish o blowfish c cc qlanglvl c i iproto dhave config h g o objects charset o charset c cc qlanglvl c i iproto dhave config h g o objects crypt o crypt c cc qlanglvl c i iproto dhave config h g o objects crypt zip o crypt zip c cc qlanglvl c i iproto dhave config h g o objects diff o diff c cc qlanglvl c i iproto dhave config h g o objects digraph o digraph c cc qlanglvl c i iproto dhave config h g o objects edit o edit c cc qlanglvl c i iproto dhave config h g o objects eval o eval c cc qlanglvl c i iproto dhave config h g o objects ex cmds o ex cmds c cc qlanglvl c i iproto dhave config h g o objects ex o ex c cc qlanglvl c i iproto dhave config h g o objects ex docmd o ex docmd c cc qlanglvl c i iproto dhave config h g o objects ex eval o ex eval c cc qlanglvl c i iproto dhave config h g o objects ex getln o ex getln c cc qlanglvl c i iproto dhave config h g o objects fileio o fileio c cc qlanglvl c i iproto dhave config h g o objects fold o fold c cc qlanglvl c i iproto dhave config h g o objects getchar o getchar c cc qlanglvl c i iproto dhave config h g o objects hardcopy o hardcopy c cc qlanglvl c i iproto dhave config h g o objects hashtab o hashtab c cc qlanglvl c i iproto dhave config h g o objects if cscope o if cscope c cc qlanglvl c i iproto dhave config h g o objects if xcmdsrv o if xcmdsrv c cc qlanglvl c i iproto dhave config h g o objects mark o mark c cc qlanglvl c i iproto dhave config h g o objects memline o memline c cc qlanglvl c i iproto dhave config h g o objects menu o menu c cc qlanglvl c i iproto dhave config h g o objects message o message c cc qlanglvl c i iproto dhave config h g o objects o c cc qlanglvl c i iproto dhave config h g o objects o c cc qlanglvl c i iproto dhave config h g o objects move o move c cc qlanglvl c i iproto dhave config h g o objects mbyte o mbyte c mbyte c line s undeclared identifier input style mbyte c line s undeclared identifier input style mbyte c line s undeclared identifier xim fg color mbyte c line s undeclared identifier invalcolor mbyte c line s undeclared identifier gui mbyte c line s undeclared identifier xim bg color mbyte c line s undeclared identifier input style mbyte c line s undeclared identifier gui mbyte c line s undeclared identifier status area enabled mbyte c line s undeclared identifier gui make the error code from the last command is stop make the error code from the last command is stop what is the expected output compile and create the vim binary file what do you see instead the error above what version of the product are you using on what operating system vim on aix c compiler version xlc qversion ibm xl c c for aix version original issue reported on code google com by gmail com on oct at | 1 |
93,162 | 8,402,343,918 | IssuesEvent | 2018-10-11 06:12:57 | tendermint/tendermint | https://api.github.com/repos/tendermint/tendermint | closed | Fail to go test rpc/lib/rpc_test.go | help wanted test waiting for response | <!--
Please fill in as much of the template below as you can.
Be ready for followup questions, and please respond in a timely
manner. We might ask you to provide additional logs and data (tendermint & app).
-->
**Tendermint version** (use `tendermint version` or `git rev-parse --verify HEAD` if installed from source):
$ git rev-parse --verify HEAD
c1f6f6479d8ed1c9e5512f5698749bb9cb85f79a
**ABCI app** (name for built-in, URL for self-written if it's publicly available):
**Environment**: 3.10.0-693.el7.x86_64
- **OS** (e.g. from /etc/os-release): CentOS Linux 7 (Core)
- **Install tools**:
- **Others**: Go version: go version go1.9.4 linux/amd64
**What happened**:
1. go get -u github.com/tendermint/tendermint/
2. dep ensure
3. cd rpc/lib/
4. go test -run TestWSClientPingPong
5. --- FAIL: TestWSClientPingPong (0.00s)
require.go:765:
Error Trace: rpc_test.go:365
Error: Expected nil, but got: &errors.errorString{s:"Moved Permanently"}
Test: TestWSClientPingPong
FAIL
exit status 1
FAIL github.com/tendermint/tendermint/rpc/lib 2.009s
**What you expected to happen**:
1. Test PASS
**Have you tried the latest version**: yes/no
1. Last Commit: c1f6f6479d8ed1c9e5512f5698749bb9cb85f79a
**How to reproduce it** (as minimally and precisely as possible):
1. go test -run TestWSClientPingPong
**Logs (paste a small part showing an error (< 10 lines) or link a pastebin, gist, etc. containing more of the log file)**:
**Config (you can paste only the changes you've made)**:
**node command runtime flags**:
**`/dump_consensus_state` output for consensus bugs**
**Anything else we need to know**:
| 1.0 | Fail to go test rpc/lib/rpc_test.go - <!--
Please fill in as much of the template below as you can.
Be ready for followup questions, and please respond in a timely
manner. We might ask you to provide additional logs and data (tendermint & app).
-->
**Tendermint version** (use `tendermint version` or `git rev-parse --verify HEAD` if installed from source):
$ git rev-parse --verify HEAD
c1f6f6479d8ed1c9e5512f5698749bb9cb85f79a
**ABCI app** (name for built-in, URL for self-written if it's publicly available):
**Environment**: 3.10.0-693.el7.x86_64
- **OS** (e.g. from /etc/os-release): CentOS Linux 7 (Core)
- **Install tools**:
- **Others**: Go version: go version go1.9.4 linux/amd64
**What happened**:
1. go get -u github.com/tendermint/tendermint/
2. dep ensure
3. cd rpc/lib/
4. go test -run TestWSClientPingPong
5. --- FAIL: TestWSClientPingPong (0.00s)
require.go:765:
Error Trace: rpc_test.go:365
Error: Expected nil, but got: &errors.errorString{s:"Moved Permanently"}
Test: TestWSClientPingPong
FAIL
exit status 1
FAIL github.com/tendermint/tendermint/rpc/lib 2.009s
**What you expected to happen**:
1. Test PASS
**Have you tried the latest version**: yes/no
1. Last Commit: c1f6f6479d8ed1c9e5512f5698749bb9cb85f79a
**How to reproduce it** (as minimally and precisely as possible):
1. go test -run TestWSClientPingPong
**Logs (paste a small part showing an error (< 10 lines) or link a pastebin, gist, etc. containing more of the log file)**:
**Config (you can paste only the changes you've made)**:
**node command runtime flags**:
**`/dump_consensus_state` output for consensus bugs**
**Anything else we need to know**:
| non_defect | fail to go test rpc lib rpc test go please fill in as much of the template below as you can be ready for followup questions and please respond in a timely manner we might ask you to provide additional logs and data tendermint app tendermint version use tendermint version or git rev parse verify head if installed from source git rev parse verify head abci app name for built in url for self written if it s publicly available environment os e g from etc os release centos linux core install tools others go version go version linux what happened go get u github com tendermint tendermint dep ensure cd rpc lib go test run testwsclientpingpong fail testwsclientpingpong require go error trace rpc test go error expected nil but got errors errorstring s moved permanently test testwsclientpingpong fail exit status fail github com tendermint tendermint rpc lib what you expected to happen test pass have you tried the latest version yes no last commit how to reproduce it as minimally and precisely as possible go test run testwsclientpingpong logs paste a small part showing an error lines or link a pastebin gist etc containing more of the log file config you can paste only the changes you ve made node command runtime flags dump consensus state output for consensus bugs anything else we need to know | 0 |
11,479 | 2,652,258,647 | IssuesEvent | 2015-03-16 16:23:48 | JoseExposito/touchegg | https://api.github.com/repos/JoseExposito/touchegg | closed | Multitouch gestures not working on VAIO SVS13AB1SX | auto-migrated Type-Defect | ```
Hi guys, thanks for the great software, I have touchegg running in two ASUS
machines with no problems. I also have a VAIO SVS13AB1SX that had multitouch
gestures under Win7, but that doesn't work under linux. I mean the two finger
scroll is working ok, but three and four fingers doesn't. When I connect an
Apple Magick Track to this computer, touchegg works flawlessly. Could you help
me walk through this issue? What should I do to discover if the pad accepts
gestures on linux?
Thank you
```
Original issue reported on code.google.com by `luis.na...@gmail.com` on 23 May 2014 at 10:40 | 1.0 | Multitouch gestures not working on VAIO SVS13AB1SX - ```
Hi guys, thanks for the great software, I have touchegg running in two ASUS
machines with no problems. I also have a VAIO SVS13AB1SX that had multitouch
gestures under Win7, but that doesn't work under linux. I mean the two finger
scroll is working ok, but three and four fingers doesn't. When I connect an
Apple Magick Track to this computer, touchegg works flawlessly. Could you help
me walk through this issue? What should I do to discover if the pad accepts
gestures on linux?
Thank you
```
Original issue reported on code.google.com by `luis.na...@gmail.com` on 23 May 2014 at 10:40 | defect | multitouch gestures not working on vaio hi guys thanks for the great software i have touchegg running in two asus machines with no problems i also have a vaio that had multitouch gestures under but that doesn t work under linux i mean the two finger scroll is working ok but three and four fingers doesn t when i connect an apple magick track to this computer touchegg works flawlessly could you help me walk through this issue what should i do to discover if the pad accepts gestures on linux thank you original issue reported on code google com by luis na gmail com on may at | 1 |
78,666 | 27,700,958,876 | IssuesEvent | 2023-03-14 07:58:35 | volution/z-scratchpad | https://api.github.com/repos/volution/z-scratchpad | closed | Update `search` command to use document titles when multiple choices are available | defect | When one uses `z-scratchpad search -W body -a edit` for example, and one chooses a line that appears in multiple documents, currently `search` prompts for the user to select a document based on its identifier.
Update that procedure to allow the user to select it based on the document's title instead.
| 1.0 | Update `search` command to use document titles when multiple choices are available - When one uses `z-scratchpad search -W body -a edit` for example, and one chooses a line that appears in multiple documents, currently `search` prompts for the user to select a document based on its identifier.
Update that procedure to allow the user to select it based on the document's title instead.
| defect | update search command to use document titles when multiple choices are available when one uses z scratchpad search w body a edit for example and one chooses a line that appears in multiple documents currently search prompts for the user to select a document based on its identifier update that procedure to allow the user to select it based on the document s title instead | 1 |
237,785 | 26,085,340,578 | IssuesEvent | 2022-12-26 01:33:51 | AlexRogalskiy/wotd | https://api.github.com/repos/AlexRogalskiy/wotd | opened | CVE-2022-46175 (High) detected in json5-2.2.0.tgz, json5-1.0.1.tgz | security vulnerability | ## CVE-2022-46175 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>json5-2.2.0.tgz</b>, <b>json5-1.0.1.tgz</b></p></summary>
<p>
<details><summary><b>json5-2.2.0.tgz</b></p></summary>
<p>JSON for humans.</p>
<p>Library home page: <a href="https://registry.npmjs.org/json5/-/json5-2.2.0.tgz">https://registry.npmjs.org/json5/-/json5-2.2.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/ts-jest/node_modules/json5/package.json,/node_modules/remark-preset-davidtheclark/node_modules/json5/package.json,/node_modules/@babel/core/node_modules/json5/package.json,/node_modules/unified-args/node_modules/json5/package.json,/node_modules/shiki/node_modules/json5/package.json</p>
<p>
Dependency Hierarchy:
- typedoc-0.21.9.tgz (Root Library)
- shiki-0.9.8.tgz
- :x: **json5-2.2.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>json5-1.0.1.tgz</b></p></summary>
<p>JSON for humans.</p>
<p>Library home page: <a href="https://registry.npmjs.org/json5/-/json5-1.0.1.tgz">https://registry.npmjs.org/json5/-/json5-1.0.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/json5/package.json,/tilt_modules/tilt_inspector/node_modules/json5/package.json</p>
<p>
Dependency Hierarchy:
- eslint-import-resolver-typescript-2.4.0.tgz (Root Library)
- tsconfig-paths-3.11.0.tgz
- :x: **json5-1.0.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/wotd/commit/28565d6f22e9c28a7f45cf805c5f731095343f0f">28565d6f22e9c28a7f45cf805c5f731095343f0f</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
JSON5 is an extension to the popular JSON file format that aims to be easier to write and maintain by hand (e.g. for config files). The `parse` method of the JSON5 library before and including version `2.2.1` does not restrict parsing of keys named `__proto__`, allowing specially crafted strings to pollute the prototype of the resulting object. This vulnerability pollutes the prototype of the object returned by `JSON5.parse` and not the global Object prototype, which is the commonly understood definition of Prototype Pollution. However, polluting the prototype of a single object can have significant security impact for an application if the object is later used in trusted operations. This vulnerability could allow an attacker to set arbitrary and unexpected keys on the object returned from `JSON5.parse`. The actual impact will depend on how applications utilize the returned object and how they filter unwanted keys, but could include denial of service, cross-site scripting, elevation of privilege, and in extreme cases, remote code execution. `JSON5.parse` should restrict parsing of `__proto__` keys when parsing JSON strings to objects. As a point of reference, the `JSON.parse` method included in JavaScript ignores `__proto__` keys. Simply changing `JSON5.parse` to `JSON.parse` in the examples above mitigates this vulnerability. This vulnerability is patched in json5 version 2.2.2 and later.
<p>Publish Date: 2022-12-24
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-46175>CVE-2022-46175</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.1</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: High
- Integrity Impact: Low
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.cve.org/CVERecord?id=CVE-2022-46175">https://www.cve.org/CVERecord?id=CVE-2022-46175</a></p>
<p>Release Date: 2022-12-24</p>
<p>Fix Resolution: json5 - 2.2.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-46175 (High) detected in json5-2.2.0.tgz, json5-1.0.1.tgz - ## CVE-2022-46175 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>json5-2.2.0.tgz</b>, <b>json5-1.0.1.tgz</b></p></summary>
<p>
<details><summary><b>json5-2.2.0.tgz</b></p></summary>
<p>JSON for humans.</p>
<p>Library home page: <a href="https://registry.npmjs.org/json5/-/json5-2.2.0.tgz">https://registry.npmjs.org/json5/-/json5-2.2.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/ts-jest/node_modules/json5/package.json,/node_modules/remark-preset-davidtheclark/node_modules/json5/package.json,/node_modules/@babel/core/node_modules/json5/package.json,/node_modules/unified-args/node_modules/json5/package.json,/node_modules/shiki/node_modules/json5/package.json</p>
<p>
Dependency Hierarchy:
- typedoc-0.21.9.tgz (Root Library)
- shiki-0.9.8.tgz
- :x: **json5-2.2.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>json5-1.0.1.tgz</b></p></summary>
<p>JSON for humans.</p>
<p>Library home page: <a href="https://registry.npmjs.org/json5/-/json5-1.0.1.tgz">https://registry.npmjs.org/json5/-/json5-1.0.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/json5/package.json,/tilt_modules/tilt_inspector/node_modules/json5/package.json</p>
<p>
Dependency Hierarchy:
- eslint-import-resolver-typescript-2.4.0.tgz (Root Library)
- tsconfig-paths-3.11.0.tgz
- :x: **json5-1.0.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/wotd/commit/28565d6f22e9c28a7f45cf805c5f731095343f0f">28565d6f22e9c28a7f45cf805c5f731095343f0f</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
JSON5 is an extension to the popular JSON file format that aims to be easier to write and maintain by hand (e.g. for config files). The `parse` method of the JSON5 library before and including version `2.2.1` does not restrict parsing of keys named `__proto__`, allowing specially crafted strings to pollute the prototype of the resulting object. This vulnerability pollutes the prototype of the object returned by `JSON5.parse` and not the global Object prototype, which is the commonly understood definition of Prototype Pollution. However, polluting the prototype of a single object can have significant security impact for an application if the object is later used in trusted operations. This vulnerability could allow an attacker to set arbitrary and unexpected keys on the object returned from `JSON5.parse`. The actual impact will depend on how applications utilize the returned object and how they filter unwanted keys, but could include denial of service, cross-site scripting, elevation of privilege, and in extreme cases, remote code execution. `JSON5.parse` should restrict parsing of `__proto__` keys when parsing JSON strings to objects. As a point of reference, the `JSON.parse` method included in JavaScript ignores `__proto__` keys. Simply changing `JSON5.parse` to `JSON.parse` in the examples above mitigates this vulnerability. This vulnerability is patched in json5 version 2.2.2 and later.
<p>Publish Date: 2022-12-24
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-46175>CVE-2022-46175</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.1</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: High
- Integrity Impact: Low
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.cve.org/CVERecord?id=CVE-2022-46175">https://www.cve.org/CVERecord?id=CVE-2022-46175</a></p>
<p>Release Date: 2022-12-24</p>
<p>Fix Resolution: json5 - 2.2.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_defect | cve high detected in tgz tgz cve high severity vulnerability vulnerable libraries tgz tgz tgz json for humans library home page a href path to dependency file package json path to vulnerable library node modules ts jest node modules package json node modules remark preset davidtheclark node modules package json node modules babel core node modules package json node modules unified args node modules package json node modules shiki node modules package json dependency hierarchy typedoc tgz root library shiki tgz x tgz vulnerable library tgz json for humans library home page a href path to dependency file package json path to vulnerable library node modules package json tilt modules tilt inspector node modules package json dependency hierarchy eslint import resolver typescript tgz root library tsconfig paths tgz x tgz vulnerable library found in head commit a href found in base branch master vulnerability details is an extension to the popular json file format that aims to be easier to write and maintain by hand e g for config files the parse method of the library before and including version does not restrict parsing of keys named proto allowing specially crafted strings to pollute the prototype of the resulting object this vulnerability pollutes the prototype of the object returned by parse and not the global object prototype which is the commonly understood definition of prototype pollution however polluting the prototype of a single object can have significant security impact for an application if the object is later used in trusted operations this vulnerability could allow an attacker to set arbitrary and unexpected keys on the object returned from parse the actual impact will depend on how applications utilize the returned object and how they filter unwanted keys but could include denial of service cross site scripting elevation of privilege and in extreme cases remote code execution parse should restrict parsing of proto keys when parsing json strings to objects as a point of reference the json parse method included in javascript ignores proto keys simply changing parse to json parse in the examples above mitigates this vulnerability this vulnerability is patched in version and later 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 high integrity impact low availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend | 0 |
670,155 | 22,677,820,345 | IssuesEvent | 2022-07-04 07:07:05 | opensquare-network/paid-qa | https://api.github.com/repos/opensquare-network/paid-qa | opened | notification item missed | bug priority:high | since we use the new format for mentioned user to display dynamic identity or address, the red bordered one missed in notification page.
<img width="758" alt="image" src="https://user-images.githubusercontent.com/19513289/177096546-fd33e135-0565-4757-86c3-ae88efd72411.png">
<img width="1091" alt="image" src="https://user-images.githubusercontent.com/19513289/177096964-38e5a155-555b-4e68-87da-110f246dbddd.png">
| 1.0 | notification item missed - since we use the new format for mentioned user to display dynamic identity or address, the red bordered one missed in notification page.
<img width="758" alt="image" src="https://user-images.githubusercontent.com/19513289/177096546-fd33e135-0565-4757-86c3-ae88efd72411.png">
<img width="1091" alt="image" src="https://user-images.githubusercontent.com/19513289/177096964-38e5a155-555b-4e68-87da-110f246dbddd.png">
| non_defect | notification item missed since we use the new format for mentioned user to display dynamic identity or address the red bordered one missed in notification page img width alt image src img width alt image src | 0 |
741,850 | 25,824,510,767 | IssuesEvent | 2022-12-12 11:59:44 | status-im/status-desktop | https://api.github.com/repos/status-im/status-desktop | opened | [Community Mint Collectibles] Create new collectible edit page | ui Communities priority F2: important S:2 | ### Description
[Epic](https://github.com/status-im/status-desktop/issues/8694)
1. Implement `Collectibles Edit` page design with **mocked data**
2. From permissions dropdown, create [navigation](https://www.figma.com/file/17fc13UBFvInrLgNUKJJg5/Kuba%E2%8E%9CDesktop?node-id=2934%3A485259&t=6E3gZk9l72B1DqRy-0)
[Collectible edit page design](https://www.figma.com/file/17fc13UBFvInrLgNUKJJg5/Kuba%E2%8E%9CDesktop?node-id=2934%3A480877&t=6E3gZk9l72B1DqRy-0)
| 1.0 | [Community Mint Collectibles] Create new collectible edit page - ### Description
[Epic](https://github.com/status-im/status-desktop/issues/8694)
1. Implement `Collectibles Edit` page design with **mocked data**
2. From permissions dropdown, create [navigation](https://www.figma.com/file/17fc13UBFvInrLgNUKJJg5/Kuba%E2%8E%9CDesktop?node-id=2934%3A485259&t=6E3gZk9l72B1DqRy-0)
[Collectible edit page design](https://www.figma.com/file/17fc13UBFvInrLgNUKJJg5/Kuba%E2%8E%9CDesktop?node-id=2934%3A480877&t=6E3gZk9l72B1DqRy-0)
| non_defect | create new collectible edit page description implement collectibles edit page design with mocked data from permissions dropdown create | 0 |
502,124 | 14,540,639,185 | IssuesEvent | 2020-12-15 13:35:27 | enso-org/enso | https://api.github.com/repos/enso-org/enso | opened | Improve Json to_text Performance | Category: Libraries Change: Non-Breaking Difficulty: Core Contributor Priority: High Type: Enhancement | ### Summary
<!--
- A summary of the task.
-->
Current `Json.to_text` implementation allocates text buffer for each json node. This is not ideal and can be improved.
### Value
`Json.to_text` is used as a default visualization expression. Rewriting it will improve the visualizations performance.
<!--
- This section should describe the value of this task.
- This value can be for users, to the team, etc.
-->
### Specification
Rewrite `Json.to_text` utilizing the events stream.
<!--
- Detailed requirements for the feature.
- The performance requirements for the feature.
-->
### Acceptance Criteria & Test Cases
`Json.to_text` uses the events stream to produce the text output.
<!--
- Any criteria that must be satisfied for the task to be accepted.
- The test plan for the feature, related to the acceptance criteria.
-->
| 1.0 | Improve Json to_text Performance - ### Summary
<!--
- A summary of the task.
-->
Current `Json.to_text` implementation allocates text buffer for each json node. This is not ideal and can be improved.
### Value
`Json.to_text` is used as a default visualization expression. Rewriting it will improve the visualizations performance.
<!--
- This section should describe the value of this task.
- This value can be for users, to the team, etc.
-->
### Specification
Rewrite `Json.to_text` utilizing the events stream.
<!--
- Detailed requirements for the feature.
- The performance requirements for the feature.
-->
### Acceptance Criteria & Test Cases
`Json.to_text` uses the events stream to produce the text output.
<!--
- Any criteria that must be satisfied for the task to be accepted.
- The test plan for the feature, related to the acceptance criteria.
-->
| non_defect | improve json to text performance summary a summary of the task current json to text implementation allocates text buffer for each json node this is not ideal and can be improved value json to text is used as a default visualization expression rewriting it will improve the visualizations performance this section should describe the value of this task this value can be for users to the team etc specification rewrite json to text utilizing the events stream detailed requirements for the feature the performance requirements for the feature acceptance criteria test cases json to text uses the events stream to produce the text output any criteria that must be satisfied for the task to be accepted the test plan for the feature related to the acceptance criteria | 0 |
25,542 | 4,381,556,367 | IssuesEvent | 2016-08-06 09:27:55 | scipy/scipy | https://api.github.com/repos/scipy/scipy | closed | expm_multiply, complex matrices not working using start,stop,ect... | defect scipy.sparse.linalg |
Hi,
There is a bug with expm_multiply. If I just use a complex matrix and vector the function returns the correct vector but when I use the linear grid feature it seems to be casting the vector to a float while iterating through the grid points:
site-packages/scipy/sparse/linalg/_expm_multiply.py:568: ComplexWarning: Casting complex values to real discards the imaginary part
X[0] = _expm_multiply_simple_core(A, B, t_0, mu, m_star, s)
site-packages/scipy/sparse/linalg/_expm_multiply.py:654: ComplexWarning: Casting complex values to real discards the imaginary part
K[p] = h * A.dot(K[p-1]) / float(p)
site-packages/scipy/sparse/linalg/_expm_multiply.py:663: ComplexWarning: Casting complex values to real discards the imaginary part
X[k + id] = np.exp(kh*mu) * F
I'm using scipy 0.17.1.
| 1.0 | expm_multiply, complex matrices not working using start,stop,ect... -
Hi,
There is a bug with expm_multiply. If I just use a complex matrix and vector the function returns the correct vector but when I use the linear grid feature it seems to be casting the vector to a float while iterating through the grid points:
site-packages/scipy/sparse/linalg/_expm_multiply.py:568: ComplexWarning: Casting complex values to real discards the imaginary part
X[0] = _expm_multiply_simple_core(A, B, t_0, mu, m_star, s)
site-packages/scipy/sparse/linalg/_expm_multiply.py:654: ComplexWarning: Casting complex values to real discards the imaginary part
K[p] = h * A.dot(K[p-1]) / float(p)
site-packages/scipy/sparse/linalg/_expm_multiply.py:663: ComplexWarning: Casting complex values to real discards the imaginary part
X[k + id] = np.exp(kh*mu) * F
I'm using scipy 0.17.1.
| defect | expm multiply complex matrices not working using start stop ect hi there is a bug with expm multiply if i just use a complex matrix and vector the function returns the correct vector but when i use the linear grid feature it seems to be casting the vector to a float while iterating through the grid points site packages scipy sparse linalg expm multiply py complexwarning casting complex values to real discards the imaginary part x expm multiply simple core a b t mu m star s site packages scipy sparse linalg expm multiply py complexwarning casting complex values to real discards the imaginary part k h a dot k float p site packages scipy sparse linalg expm multiply py complexwarning casting complex values to real discards the imaginary part x np exp kh mu f i m using scipy | 1 |
5,483 | 2,610,188,526 | IssuesEvent | 2015-02-26 18:59:43 | chrsmith/quchuseban | https://api.github.com/repos/chrsmith/quchuseban | opened | 分享脸上长色斑如何祛除 | auto-migrated Priority-Medium Type-Defect | ```
《摘要》
昔我往矣，杨柳依依，今我来思，雨雪霏霏。如若没有开始��
�是不是就不会有这一把辛酸泪；如若没有经历，是不是就不�
��有这一缕相思情。如若没有如果，我想重新洗牌，重新上演
这不是只属于一个人的独角戏。听风，划过浅浅的忧伤；听��
�，淋过丝丝的惆怅；听花开的声音，隐藏绵绵的落寞。一件�
��衣，一席长衫，一肩长发，一把天蓝伞，走进了下得正大的
雨中。这一次，我没有丢掉了伞，我喜欢天蓝色的伞遮住我��
�容颜，不被路人的眼神留连。不让他们看见我脸上的色斑！�
��上长色斑如何祛除，
《客户案例》
我今年26岁了，宝宝也两岁多了，我是在怀孕的时候长的
妊娠斑，医生说是因为孕激素分泌太多引起的色素沉淀现象��
�说是只要休息好，多增加营养，这些妊娠斑就会自己消除，�
��是等我生完宝宝，斑却越来越重了，那个时候要喂奶也没敢
用什么药品，就这样宝宝都两岁了，我脸上的妊娠斑不但没��
�减少反而越来越多了，我是实在看不下去了，到处打听祛斑�
��方法，后来我在网上查祛斑产品的时候看到「黛芙薇尔精华
液」，说是纯精华的祛斑产品，看很多人都说这个产品效果��
�错，忍不住好奇，我就去了他们的商城上,仔细看了他们的产
品介绍，我忍不住咨询了他们的客服，给他们说了我的情况��
�客服专家说，我这种斑是可以彻底去掉的，平时多注意休息�
��水果蔬菜，我就试着订购了两个周期，没想到三天就收到了
，按照专家的建议，我平时很注意睡眠，坚持用完后，我脸��
�的妊娠斑真的没有了，皮肤也白了很多，这个祛斑产品确实�
��不错的。
阅读了脸上长色斑如何祛除，再看脸上容易长斑的原因：
《色斑形成原因》
内部因素
一、压力
当人受到压力时，就会分泌肾上腺素，为对付压力而做��
�备。如果长期受到压力，人体新陈代谢的平衡就会遭到破坏�
��皮肤所需的营养供应趋于缓慢，色素母细胞就会变得很活跃
。
二、荷尔蒙分泌失调
避孕药里所含的女性荷尔蒙雌激素，会刺激麦拉宁细胞��
�分泌而形成不均匀的斑点，因避孕药而形成的斑点，虽然在�
��药中断后会停止，但仍会在皮肤上停留很长一段时间。怀孕
中因女性荷尔蒙雌激素的增加，从怀孕4—5个月开始会容易出
现斑，这时候出现的斑点在产后大部分会消失。可是，新陈��
�谢不正常、肌肤裸露在强烈的紫外线下、精神上受到压力等�
��因，都会使斑加深。有时新长出的斑，产后也不会消失，所
以需要更加注意。
三、新陈代谢缓慢
肝的新陈代谢功能不正常或卵巢功能减退时也会出现斑��
�因为新陈代谢不顺畅、或内分泌失调，使身体处于敏感状态�
��，从而加剧色素问题。我们常说的便秘会形成斑，其实就是
内分泌失调导致过敏体质而形成的。另外，身体状态不正常��
�时候，紫外线的照射也会加速斑的形成。
四、错误的使用化妆品
使用了不适合自己皮肤的化妆品，会导致皮肤过敏。在��
�疗的过程中如过量照射到紫外线，皮肤会为了抵御外界的侵�
��，在有炎症的部位聚集麦拉宁色素，这样会出现色素沉着的
问题。
外部因素
一、紫外线
照射紫外线的时候，人体为了保护皮肤，会在基底层产��
�很多麦拉宁色素。所以为了保护皮肤，会在敏感部位聚集更�
��的色素。经常裸露在强烈的阳光底下不仅促进皮肤的老化，
还会引起黑斑、雀斑等色素沉着的皮肤疾患。
二、不良的清洁习惯
因强烈的清洁习惯使皮肤变得敏感，这样会刺激皮肤。��
�皮肤敏感时，人体为了保护皮肤，黑色素细胞会分泌很多麦�
��宁色素，当色素过剩时就出现了斑、瑕疵等皮肤色素沉着的
问题。
三、遗传基因
父母中有长斑的，则本人长斑的概率就很高，这种情况��
�一定程度上就可判定是遗传基因的作用。所以家里特别是长�
��有长斑的人，要注意避免引发长斑的重要因素之一——紫外
线照射，这是预防斑必须注意的。
《有疑问帮你解决》
1,黛芙薇尔精华液真的有效果吗?真的可以把脸上的黄褐��
�去掉吗?
答：黛芙薇尔精华液DNA精华能够有效的修复周围难以触��
�的色斑，其独有的纳豆成分为皮肤的美白与靓丽，提供了必�
��可少的营养物质，可以有效的去除黄褐斑，黄褐斑，黄褐斑
，蝴蝶斑，晒斑、妊娠斑等。它它完全突破了传统的美肤时��
�，宛如在皮肤中注入了一杯兼具活化、再生、滋养等功效的�
��尾酒，同时为脸部提供大量有机维生素精华，脸部的改变显
而易见。自产品上市以来，老顾客纷纷介绍新顾客，71%的新��
�客都是通过老顾客介绍而来，口碑由此而来!
2，服用黛芙薇尔美白，会伤身体吗?有副作用吗?
答：黛芙薇尔精华液应用了精纯复合配方和领先的分类��
�斑科技，并将“DNA美肤系统”疗法应用到了该产品中，能彻�
��祛除黄褐斑，蝴蝶斑，妊娠斑，晒斑，黄褐斑，老年斑，有
效淡化黄褐斑至接近肤色。黛芙薇尔通过法国、美国、台湾��
�地的专家通力协作，超过10年的研究以全新的DNA肌肤修复技��
�，挑战传统化学护肤理念，不懈追寻发现破译大自然的美丽�
��迹，令每一位爱美的女性都能享受到科技创新所带来的自然
之美。
专为亚洲女性肤质研制，精心呵护女性美丽，多年来，为数��
�百万计的女性解除了黄褐斑困扰。深得广大女性朋友的信赖!
3，去除黄褐斑之后，会反弹吗?
答：很多曾经长了黄褐斑的人士，自从选择了黛芙薇尔��
�白，就一劳永逸。这款祛斑产品是经过数十位权威祛斑专家�
��据斑的形成原因精心研制而成用事实说话，让消费者打分。
树立权威品牌!我们的很多新客户都是老客户介绍而来，请问�
��如果效果不好，会有客户转介绍吗?
4，你们的价格有点贵，能不能便宜一点?
答：如果您使用西药最少需要2000元，煎服的药最少需要3
000元，做手术最少是5000元，而这些毫无疑问，不会对彻底去�
��你的斑点有任何帮助!一分价钱，一份价值，我们现在做的��
�是一个口碑，一个品牌，价钱并不高。如果花这点钱把你的�
��褐斑彻底去除，你还会觉得贵吗?你还会再去花那么多冤枉��
�，不但斑没去掉，还把自己的皮肤弄的越来越糟吗
5，我适合用黛芙薇尔精华液吗?
答：黛芙薇尔适用人群：
1、生理紊乱引起的黄褐斑人群
2、生育引起的妊娠斑人群
3、年纪增长引起的老年斑人群
4、化妆品色素沉积、辐射斑人群
5、长期日照引起的日晒斑人群
6、肌肤暗淡急需美白的人群
《祛斑小方法》
脸上长色斑如何祛除，同时为您分享祛斑小方法
2、30克杏仁与适量鸡蛋清混合调匀，每晚睡前搽于面部有色��
�处，次日早晨用白酒洗掉。
```
-----
Original issue reported on code.google.com by `additive...@gmail.com` on 1 Jul 2014 at 4:29 | 1.0 | 分享脸上长色斑如何祛除 - ```
《摘要》
昔我往矣，杨柳依依，今我来思，雨雪霏霏。如若没有开始��
�是不是就不会有这一把辛酸泪；如若没有经历，是不是就不�
��有这一缕相思情。如若没有如果，我想重新洗牌，重新上演
这不是只属于一个人的独角戏。听风，划过浅浅的忧伤；听��
�，淋过丝丝的惆怅；听花开的声音，隐藏绵绵的落寞。一件�
��衣，一席长衫，一肩长发，一把天蓝伞，走进了下得正大的
雨中。这一次，我没有丢掉了伞，我喜欢天蓝色的伞遮住我��
�容颜，不被路人的眼神留连。不让他们看见我脸上的色斑！�
��上长色斑如何祛除，
《客户案例》
我今年26岁了，宝宝也两岁多了，我是在怀孕的时候长的
妊娠斑，医生说是因为孕激素分泌太多引起的色素沉淀现象��
�说是只要休息好，多增加营养，这些妊娠斑就会自己消除，�
��是等我生完宝宝，斑却越来越重了，那个时候要喂奶也没敢
用什么药品，就这样宝宝都两岁了，我脸上的妊娠斑不但没��
�减少反而越来越多了，我是实在看不下去了，到处打听祛斑�
��方法，后来我在网上查祛斑产品的时候看到「黛芙薇尔精华
液」，说是纯精华的祛斑产品，看很多人都说这个产品效果��
�错，忍不住好奇，我就去了他们的商城上,仔细看了他们的产
品介绍，我忍不住咨询了他们的客服，给他们说了我的情况��
�客服专家说，我这种斑是可以彻底去掉的，平时多注意休息�
��水果蔬菜，我就试着订购了两个周期，没想到三天就收到了
，按照专家的建议，我平时很注意睡眠，坚持用完后，我脸��
�的妊娠斑真的没有了，皮肤也白了很多，这个祛斑产品确实�
��不错的。
阅读了脸上长色斑如何祛除，再看脸上容易长斑的原因：
《色斑形成原因》
内部因素
一、压力
当人受到压力时，就会分泌肾上腺素，为对付压力而做��
�备。如果长期受到压力，人体新陈代谢的平衡就会遭到破坏�
��皮肤所需的营养供应趋于缓慢，色素母细胞就会变得很活跃
。
二、荷尔蒙分泌失调
避孕药里所含的女性荷尔蒙雌激素，会刺激麦拉宁细胞��
�分泌而形成不均匀的斑点，因避孕药而形成的斑点，虽然在�
��药中断后会停止，但仍会在皮肤上停留很长一段时间。怀孕
中因女性荷尔蒙雌激素的增加，从怀孕4—5个月开始会容易出
现斑，这时候出现的斑点在产后大部分会消失。可是，新陈��
�谢不正常、肌肤裸露在强烈的紫外线下、精神上受到压力等�
��因，都会使斑加深。有时新长出的斑，产后也不会消失，所
以需要更加注意。
三、新陈代谢缓慢
肝的新陈代谢功能不正常或卵巢功能减退时也会出现斑��
�因为新陈代谢不顺畅、或内分泌失调，使身体处于敏感状态�
��，从而加剧色素问题。我们常说的便秘会形成斑，其实就是
内分泌失调导致过敏体质而形成的。另外，身体状态不正常��
�时候，紫外线的照射也会加速斑的形成。
四、错误的使用化妆品
使用了不适合自己皮肤的化妆品，会导致皮肤过敏。在��
�疗的过程中如过量照射到紫外线，皮肤会为了抵御外界的侵�
��，在有炎症的部位聚集麦拉宁色素，这样会出现色素沉着的
问题。
外部因素
一、紫外线
照射紫外线的时候，人体为了保护皮肤，会在基底层产��
�很多麦拉宁色素。所以为了保护皮肤，会在敏感部位聚集更�
��的色素。经常裸露在强烈的阳光底下不仅促进皮肤的老化，
还会引起黑斑、雀斑等色素沉着的皮肤疾患。
二、不良的清洁习惯
因强烈的清洁习惯使皮肤变得敏感，这样会刺激皮肤。��
�皮肤敏感时，人体为了保护皮肤，黑色素细胞会分泌很多麦�
��宁色素，当色素过剩时就出现了斑、瑕疵等皮肤色素沉着的
问题。
三、遗传基因
父母中有长斑的，则本人长斑的概率就很高，这种情况��
�一定程度上就可判定是遗传基因的作用。所以家里特别是长�
��有长斑的人，要注意避免引发长斑的重要因素之一——紫外
线照射，这是预防斑必须注意的。
《有疑问帮你解决》
1,黛芙薇尔精华液真的有效果吗?真的可以把脸上的黄褐��
�去掉吗?
答：黛芙薇尔精华液DNA精华能够有效的修复周围难以触��
�的色斑，其独有的纳豆成分为皮肤的美白与靓丽，提供了必�
��可少的营养物质，可以有效的去除黄褐斑，黄褐斑，黄褐斑
，蝴蝶斑，晒斑、妊娠斑等。它它完全突破了传统的美肤时��
�，宛如在皮肤中注入了一杯兼具活化、再生、滋养等功效的�
��尾酒，同时为脸部提供大量有机维生素精华，脸部的改变显
而易见。自产品上市以来，老顾客纷纷介绍新顾客，71%的新��
�客都是通过老顾客介绍而来，口碑由此而来!
2，服用黛芙薇尔美白，会伤身体吗?有副作用吗?
答：黛芙薇尔精华液应用了精纯复合配方和领先的分类��
�斑科技，并将“DNA美肤系统”疗法应用到了该产品中，能彻�
��祛除黄褐斑，蝴蝶斑，妊娠斑，晒斑，黄褐斑，老年斑，有
效淡化黄褐斑至接近肤色。黛芙薇尔通过法国、美国、台湾��
�地的专家通力协作，超过10年的研究以全新的DNA肌肤修复技��
�，挑战传统化学护肤理念，不懈追寻发现破译大自然的美丽�
��迹，令每一位爱美的女性都能享受到科技创新所带来的自然
之美。
专为亚洲女性肤质研制，精心呵护女性美丽，多年来，为数��
�百万计的女性解除了黄褐斑困扰。深得广大女性朋友的信赖!
3，去除黄褐斑之后，会反弹吗?
答：很多曾经长了黄褐斑的人士，自从选择了黛芙薇尔��
�白，就一劳永逸。这款祛斑产品是经过数十位权威祛斑专家�
��据斑的形成原因精心研制而成用事实说话，让消费者打分。
树立权威品牌!我们的很多新客户都是老客户介绍而来，请问�
��如果效果不好，会有客户转介绍吗?
4，你们的价格有点贵，能不能便宜一点?
答：如果您使用西药最少需要2000元，煎服的药最少需要3
000元，做手术最少是5000元，而这些毫无疑问，不会对彻底去�
��你的斑点有任何帮助!一分价钱，一份价值，我们现在做的��
�是一个口碑，一个品牌，价钱并不高。如果花这点钱把你的�
��褐斑彻底去除，你还会觉得贵吗?你还会再去花那么多冤枉��
�，不但斑没去掉，还把自己的皮肤弄的越来越糟吗
5，我适合用黛芙薇尔精华液吗?
答：黛芙薇尔适用人群：
1、生理紊乱引起的黄褐斑人群
2、生育引起的妊娠斑人群
3、年纪增长引起的老年斑人群
4、化妆品色素沉积、辐射斑人群
5、长期日照引起的日晒斑人群
6、肌肤暗淡急需美白的人群
《祛斑小方法》
脸上长色斑如何祛除，同时为您分享祛斑小方法
2、30克杏仁与适量鸡蛋清混合调匀，每晚睡前搽于面部有色��
�处，次日早晨用白酒洗掉。
```
-----
Original issue reported on code.google.com by `additive...@gmail.com` on 1 Jul 2014 at 4:29 | defect | 分享脸上长色斑如何祛除 《摘要》 昔我往矣，杨柳依依，今我来思，雨雪霏霏。如若没有开始�� �是不是就不会有这一把辛酸泪；如若没有经历，是不是就不� ��有这一缕相思情。如若没有如果，我想重新洗牌，重新上演 这不是只属于一个人的独角戏。听风，划过浅浅的忧伤；听�� �，淋过丝丝的惆怅；听花开的声音，隐藏绵绵的落寞。一件� ��衣，一席长衫，一肩长发，一把天蓝伞，走进了下得正大的 雨中。这一次，我没有丢掉了伞，我喜欢天蓝色的伞遮住我�� �容颜，不被路人的眼神留连。不让他们看见我脸上的色斑！� ��上长色斑如何祛除， 《客户案例》 ，宝宝也两岁多了，我是在怀孕的时候长的 妊娠斑，医生说是因为孕激素分泌太多引起的色素沉淀现象�� �说是只要休息好，多增加营养，这些妊娠斑就会自己消除，� ��是等我生完宝宝，斑却越来越重了，那个时候要喂奶也没敢 用什么药品，就这样宝宝都两岁了，我脸上的妊娠斑不但没�� �减少反而越来越多了，我是实在看不下去了，到处打听祛斑� ��方法，后来我在网上查祛斑产品的时候看到「黛芙薇尔精华 液」，说是纯精华的祛斑产品，看很多人都说这个产品效果�� �错，忍不住好奇，我就去了他们的商城上 仔细看了他们的产 品介绍，我忍不住咨询了他们的客服，给他们说了我的情况�� �客服专家说，我这种斑是可以彻底去掉的，平时多注意休息� ��水果蔬菜，我就试着订购了两个周期，没想到三天就收到了 ，按照专家的建议，我平时很注意睡眠，坚持用完后，我脸�� �的妊娠斑真的没有了，皮肤也白了很多，这个祛斑产品确实� ��不错的。 阅读了脸上长色斑如何祛除，再看脸上容易长斑的原因： 《色斑形成原因》 内部因素 一、压力 当人受到压力时，就会分泌肾上腺素，为对付压力而做�� �备。如果长期受到压力，人体新陈代谢的平衡就会遭到破坏� ��皮肤所需的营养供应趋于缓慢，色素母细胞就会变得很活跃 。 二、荷尔蒙分泌失调 避孕药里所含的女性荷尔蒙雌激素，会刺激麦拉宁细胞�� �分泌而形成不均匀的斑点，因避孕药而形成的斑点，虽然在� ��药中断后会停止，但仍会在皮肤上停留很长一段时间。怀孕 中因女性荷尔蒙雌激素的增加， — 现斑，这时候出现的斑点在产后大部分会消失。可是，新陈�� �谢不正常、肌肤裸露在强烈的紫外线下、精神上受到压力等� ��因，都会使斑加深。有时新长出的斑，产后也不会消失，所 以需要更加注意。 三、新陈代谢缓慢 肝的新陈代谢功能不正常或卵巢功能减退时也会出现斑�� �因为新陈代谢不顺畅、或内分泌失调，使身体处于敏感状态� ��，从而加剧色素问题。我们常说的便秘会形成斑，其实就是 内分泌失调导致过敏体质而形成的。另外，身体状态不正常�� �时候，紫外线的照射也会加速斑的形成。 四、错误的使用化妆品 使用了不适合自己皮肤的化妆品，会导致皮肤过敏。在�� �疗的过程中如过量照射到紫外线，皮肤会为了抵御外界的侵� ��，在有炎症的部位聚集麦拉宁色素，这样会出现色素沉着的 问题。 外部因素 一、紫外线 照射紫外线的时候，人体为了保护皮肤，会在基底层产�� �很多麦拉宁色素。所以为了保护皮肤，会在敏感部位聚集更� ��的色素。经常裸露在强烈的阳光底下不仅促进皮肤的老化， 还会引起黑斑、雀斑等色素沉着的皮肤疾患。 二、不良的清洁习惯 因强烈的清洁习惯使皮肤变得敏感，这样会刺激皮肤。�� �皮肤敏感时，人体为了保护皮肤，黑色素细胞会分泌很多麦� ��宁色素，当色素过剩时就出现了斑、瑕疵等皮肤色素沉着的 问题。 三、遗传基因 父母中有长斑的，则本人长斑的概率就很高，这种情况�� �一定程度上就可判定是遗传基因的作用。所以家里特别是长� ��有长斑的人，要注意避免引发长斑的重要因素之一——紫外 线照射，这是预防斑必须注意的。 《有疑问帮你解决》 黛芙薇尔精华液真的有效果吗 真的可以把脸上的黄褐�� �去掉吗 答：黛芙薇尔精华液dna精华能够有效的修复周围难以触�� �的色斑，其独有的纳豆成分为皮肤的美白与靓丽，提供了必� ��可少的营养物质，可以有效的去除黄褐斑，黄褐斑，黄褐斑 ，蝴蝶斑，晒斑、妊娠斑等。它它完全突破了传统的美肤时�� �，宛如在皮肤中注入了一杯兼具活化、再生、滋养等功效的� ��尾酒，同时为脸部提供大量有机维生素精华，脸部的改变显 而易见。自产品上市以来，老顾客纷纷介绍新顾客， 的新�� �客都是通过老顾客介绍而来，口碑由此而来 ，服用黛芙薇尔美白，会伤身体吗 有副作用吗 答：黛芙薇尔精华液应用了精纯复合配方和领先的分类�� �斑科技，并将“dna美肤系统”疗法应用到了该产品中，能彻� ��祛除黄褐斑，蝴蝶斑，妊娠斑，晒斑，黄褐斑，老年斑，有 效淡化黄褐斑至接近肤色。黛芙薇尔通过法国、美国、台湾�� �地的专家通力协作， �� �，挑战传统化学护肤理念，不懈追寻发现破译大自然的美丽� ��迹，令每一位爱美的女性都能享受到科技创新所带来的自然 之美。 专为亚洲女性肤质研制，精心呵护女性美丽，多年来，为数�� �百万计的女性解除了黄褐斑困扰。深得广大女性朋友的信赖 ，去除黄褐斑之后，会反弹吗 答：很多曾经长了黄褐斑的人士，自从选择了黛芙薇尔�� �白，就一劳永逸。这款祛斑产品是经过数十位权威祛斑专家� ��据斑的形成原因精心研制而成用事实说话，让消费者打分。 树立权威品牌 我们的很多新客户都是老客户介绍而来，请问� ��如果效果不好，会有客户转介绍吗 ，你们的价格有点贵，能不能便宜一点 答： ， ， ，而这些毫无疑问，不会对彻底去� ��你的斑点有任何帮助 一分价钱，一份价值，我们现在做的�� �是一个口碑，一个品牌，价钱并不高。如果花这点钱把你的� ��褐斑彻底去除，你还会觉得贵吗 你还会再去花那么多冤枉�� �，不但斑没去掉，还把自己的皮肤弄的越来越糟吗 ，我适合用黛芙薇尔精华液吗 答：黛芙薇尔适用人群： 、生理紊乱引起的黄褐斑人群 、生育引起的妊娠斑人群 、年纪增长引起的老年斑人群 、化妆品色素沉积、辐射斑人群 、长期日照引起的日晒斑人群 、肌肤暗淡急需美白的人群 《祛斑小方法》 脸上长色斑如何祛除，同时为您分享祛斑小方法 、 ，每晚睡前搽于面部有色�� �处，次日早晨用白酒洗掉。 original issue reported on code google com by additive gmail com on jul at | 1 |
46,409 | 13,055,908,922 | IssuesEvent | 2020-07-30 03:05:23 | icecube-trac/tix2 | https://api.github.com/repos/icecube-trac/tix2 | opened | [VHESelfVeto] example is broken, other details (Trac #1164) | Incomplete Migration Migrated from Trac combo reconstruction defect | Migrated from https://code.icecube.wisc.edu/ticket/1164
```json
{
"status": "closed",
"changetime": "2019-02-13T14:11:57",
"description": "I.- resources/:\n\n1.- examples/analysis.py:\n \n1.1.- if a number of frames is given (tray.Execute(100)), the result is:\n\nNOTICE (I3Tray): I3Tray finishing... (I3Tray.cxx:519 in void I3Tray::Execute(unsigned int))\n0 events total\n0 events passed the veto\n0 events were vetoed\n0 events could not find a vertex\n\nis this expected(0 events)?, if so, please write down some notes.\n\n1.2.- Without giving the number of frames, it works well:\n\nNOTICE (I3Tray): I3Tray finishing... (I3Tray.cxx:481 in void I3Tray::Execute())\nWARN (I3TableWriter): 1 SubEventStreams ['ice_top',] were seen but not booked because they were not passed as part of the 'SubEventStreams' parameter of I3TableWriter (which was configured as ['in_ice',]). To book events from these streams, add them to the 'SubEventStreams' parameter of I3TableWriter. (I3TableWriter.cxx:450 in void I3TableWriter::Finish())\n149 events total\n0 events passed the veto\n44 events were vetoed\n105 events could not find a vertex\n qtot_total: 126467 calls to physics 15.26s user 0.22s system\n\n2.- examples/runveto.py, shows a FATAL\n\nLoading VHESelfVeto.......................................ok\nFATAL (icetray): Attempt to set parameter BoundaryWidth that doesn't exist (I3ConfigurationImpl.cxx:65 in void I3ConfigurationImpl::Set(const std::string&, const boost::python::api::object&))\nTraceback (most recent call last):\n File \"resources/examples/runveto.py\", line 16, in <module>\n tray.AddModule('VHESelfVeto', 'selfveto', TimeWindow=5000, VertexThreshold=100, BoundaryWidth=50,VetoThreshold=20, Pulses=pulses)\n File \"/scratch/gmaggi/icerectrunk/build/lib/I3Tray.py\", line 140, in AddModule\n super(I3Tray, self).SetParameter(_name, k, v)\nRuntimeError: Attempt to set parameter BoundaryWidth that doesn't exist (in void I3ConfigurationImpl::Set(const std::string&, const boost::python::api::object&))\n\nBoth examples were Ran like:\npython $I3_SRC/VHESelfVeto/resources/examples/file.py here.i3 /data/exp/IceCube/2011/filtered/level2/0630/Level2_IC86.2011_data_Run00118390_0630_GCD.i3.gz /data/exp/IceCube/2011/filtered/level2/0630/Level2_IC86.2011_data_Run00118390_Part00000000.i3.bz2 \n\n3.- examples/test is missing according : http://software.icecube.wisc.edu/icerec_trunk/code_reviews.html , it would allow the user to run the module without passing arguments by command line.\n\n4.- examples/index.dox is missing. Include information please in: http://software.icecube.wisc.edu/icerec_trunk/metaproject/index.html ",
"reporter": "gmaggi",
"cc": "",
"resolution": "fixed",
"_ts": "1550067117911749",
"component": "combo reconstruction",
"summary": "[VHESelfVeto] example is broken, other details",
"priority": "critical",
"keywords": "veto VHE HomogenizedQTot",
"time": "2015-08-18T18:39:48",
"milestone": "",
"owner": "claudio.kopper",
"type": "defect"
}
```
| 1.0 | [VHESelfVeto] example is broken, other details (Trac #1164) - Migrated from https://code.icecube.wisc.edu/ticket/1164
```json
{
"status": "closed",
"changetime": "2019-02-13T14:11:57",
"description": "I.- resources/:\n\n1.- examples/analysis.py:\n \n1.1.- if a number of frames is given (tray.Execute(100)), the result is:\n\nNOTICE (I3Tray): I3Tray finishing... (I3Tray.cxx:519 in void I3Tray::Execute(unsigned int))\n0 events total\n0 events passed the veto\n0 events were vetoed\n0 events could not find a vertex\n\nis this expected(0 events)?, if so, please write down some notes.\n\n1.2.- Without giving the number of frames, it works well:\n\nNOTICE (I3Tray): I3Tray finishing... (I3Tray.cxx:481 in void I3Tray::Execute())\nWARN (I3TableWriter): 1 SubEventStreams ['ice_top',] were seen but not booked because they were not passed as part of the 'SubEventStreams' parameter of I3TableWriter (which was configured as ['in_ice',]). To book events from these streams, add them to the 'SubEventStreams' parameter of I3TableWriter. (I3TableWriter.cxx:450 in void I3TableWriter::Finish())\n149 events total\n0 events passed the veto\n44 events were vetoed\n105 events could not find a vertex\n qtot_total: 126467 calls to physics 15.26s user 0.22s system\n\n2.- examples/runveto.py, shows a FATAL\n\nLoading VHESelfVeto.......................................ok\nFATAL (icetray): Attempt to set parameter BoundaryWidth that doesn't exist (I3ConfigurationImpl.cxx:65 in void I3ConfigurationImpl::Set(const std::string&, const boost::python::api::object&))\nTraceback (most recent call last):\n File \"resources/examples/runveto.py\", line 16, in <module>\n tray.AddModule('VHESelfVeto', 'selfveto', TimeWindow=5000, VertexThreshold=100, BoundaryWidth=50,VetoThreshold=20, Pulses=pulses)\n File \"/scratch/gmaggi/icerectrunk/build/lib/I3Tray.py\", line 140, in AddModule\n super(I3Tray, self).SetParameter(_name, k, v)\nRuntimeError: Attempt to set parameter BoundaryWidth that doesn't exist (in void I3ConfigurationImpl::Set(const std::string&, const boost::python::api::object&))\n\nBoth examples were Ran like:\npython $I3_SRC/VHESelfVeto/resources/examples/file.py here.i3 /data/exp/IceCube/2011/filtered/level2/0630/Level2_IC86.2011_data_Run00118390_0630_GCD.i3.gz /data/exp/IceCube/2011/filtered/level2/0630/Level2_IC86.2011_data_Run00118390_Part00000000.i3.bz2 \n\n3.- examples/test is missing according : http://software.icecube.wisc.edu/icerec_trunk/code_reviews.html , it would allow the user to run the module without passing arguments by command line.\n\n4.- examples/index.dox is missing. Include information please in: http://software.icecube.wisc.edu/icerec_trunk/metaproject/index.html ",
"reporter": "gmaggi",
"cc": "",
"resolution": "fixed",
"_ts": "1550067117911749",
"component": "combo reconstruction",
"summary": "[VHESelfVeto] example is broken, other details",
"priority": "critical",
"keywords": "veto VHE HomogenizedQTot",
"time": "2015-08-18T18:39:48",
"milestone": "",
"owner": "claudio.kopper",
"type": "defect"
}
```
| defect | example is broken other details trac migrated from json status closed changetime description i resources n examples analysis py n if a number of frames is given tray execute the result is n nnotice finishing cxx in void execute unsigned int events total events passed the veto events were vetoed events could not find a vertex n nis this expected events if so please write down some notes n without giving the number of frames it works well n nnotice finishing cxx in void execute nwarn subeventstreams were seen but not booked because they were not passed as part of the subeventstreams parameter of which was configured as to book events from these streams add them to the subeventstreams parameter of cxx in void finish events total events passed the veto events were vetoed events could not find a vertex n qtot total calls to physics user system n examples runveto py shows a fatal n nloading vheselfveto ok nfatal icetray attempt to set parameter boundarywidth that doesn t exist cxx in void set const std string const boost python api object ntraceback most recent call last n file resources examples runveto py line in n tray addmodule vheselfveto selfveto timewindow vertexthreshold boundarywidth vetothreshold pulses pulses n file scratch gmaggi icerectrunk build lib py line in addmodule n super self setparameter name k v nruntimeerror attempt to set parameter boundarywidth that doesn t exist in void set const std string const boost python api object n nboth examples were ran like npython src vheselfveto resources examples file py here data exp icecube filtered data gcd gz data exp icecube filtered data n examples test is missing according it would allow the user to run the module without passing arguments by command line n examples index dox is missing include information please in reporter gmaggi cc resolution fixed ts component combo reconstruction summary example is broken other details priority critical keywords veto vhe homogenizedqtot time milestone owner claudio kopper type defect | 1 |
68,343 | 21,645,137,161 | IssuesEvent | 2022-05-06 00:16:06 | vector-im/element-web | https://api.github.com/repos/vector-im/element-web | closed | Emoji are small again | T-Defect X-Regression S-Minor A-Timeline A-Composer A-Emoji A11y O-Frequent | ### Steps to reproduce
Send or receive a message with an emoji, or insert one into the composer
### Outcome
#### What did you expect?
Emoji should be larger than the surrounding text
#### What happened instead?
They aren't
### Operating system
NixOS unstable
### Browser information
Firefox 99.0.1
### URL for webapp
develop.element.io
### Application version
Element version: abb31c9b01a2-react-b5ac9493dd14-js-6b5f4aa0a9c1 Olm version: 3.2.8
### Homeserver
Synapse 1.58.0
### Will you send logs?
No | 1.0 | Emoji are small again - ### Steps to reproduce
Send or receive a message with an emoji, or insert one into the composer
### Outcome
#### What did you expect?
Emoji should be larger than the surrounding text
#### What happened instead?
They aren't
### Operating system
NixOS unstable
### Browser information
Firefox 99.0.1
### URL for webapp
develop.element.io
### Application version
Element version: abb31c9b01a2-react-b5ac9493dd14-js-6b5f4aa0a9c1 Olm version: 3.2.8
### Homeserver
Synapse 1.58.0
### Will you send logs?
No | defect | emoji are small again steps to reproduce send or receive a message with an emoji or insert one into the composer outcome what did you expect emoji should be larger than the surrounding text what happened instead they aren t operating system nixos unstable browser information firefox url for webapp develop element io application version element version react js olm version homeserver synapse will you send logs no | 1 |
292,535 | 21,995,245,889 | IssuesEvent | 2022-05-26 05:17:02 | dcSpark/carp | https://api.github.com/repos/dcSpark/carp | closed | Filter to only UTXOs for TransactionOutput query | bug documentation enhancement | Although it's not clear from [the query](https://dcspark.github.io/carp/openapi/#operation/TransactionOutput), this endpoint actually just gets you all outputs and doesn't check if they are spent or not. Probably filtering based on whether or not it is spent should be added as a feature and the behavior explicitly documented. | 1.0 | Filter to only UTXOs for TransactionOutput query - Although it's not clear from [the query](https://dcspark.github.io/carp/openapi/#operation/TransactionOutput), this endpoint actually just gets you all outputs and doesn't check if they are spent or not. Probably filtering based on whether or not it is spent should be added as a feature and the behavior explicitly documented. | non_defect | filter to only utxos for transactionoutput query although it s not clear from this endpoint actually just gets you all outputs and doesn t check if they are spent or not probably filtering based on whether or not it is spent should be added as a feature and the behavior explicitly documented | 0 |
40,716 | 10,140,876,023 | IssuesEvent | 2019-08-03 08:30:57 | STEllAR-GROUP/hpx | https://api.github.com/repos/STEllAR-GROUP/hpx | closed | Install failure on OS X -- duplicate rpath entries | compiler: clang platform: Mac OSX tag: wontfix type: defect | I am using OS X Yosemite. I currently cannot build HPX from source. This used to work fine on Mavericks.
The build itself goes fine. The install then emits this error message:
```
/opt/local/bin/install_name_tool: object: /Users/eschnett/SIMFACTORY/hpx-master/install/lib/hpx/libparcel_coalescing.0.9.10.dylib malformed object (load command 39 cmdsize is zero)
```
If I use "otool -l" on this library, then I see that it is indeed broken; I see the same error message.
Using "otool -l" on the original library (the one in the build directory), I see that it is healthy. Just before load command 39 (the load commands are numbered) are the definitions for LC_RPATH, i.e. the path names provided via the -rpath command. I see that the path "/Users/eschnett/SIMFACTORY/boost-1_56_0/install/lib" appears twice.
According to my interpretation of the man page of "install_name_tool" (and Google), this should not be the case -- each path should be unique.
It appears that the commands in the file "cmake_install.cmake" should rewrite these LC_RPATH paths, changing the HPX build directory to the HPX install directory. In my build, these commands are in lines 43 to 59 of this file, and read
```
execute_process(COMMAND "/opt/local/bin/install_name_tool"
-id "libparcel_coalescing.0.dylib"
-change "/Users/eschnett/SIMFACTORY/hpx-master/build/lib/libhpx.0.dylib" "libhpx.0.dylib"
-change "/Users/eschnett/SIMFACTORY/hpx-master/build/lib/libhpx_serialization.0.dylib" "libhpx_serialization.0.dylib"
"${file}")
execute_process(COMMAND /opt/local/bin/install_name_tool
-delete_rpath "/Users/eschnett/SIMFACTORY/hpx-master/build/lib"
"${file}")
execute_process(COMMAND /opt/local/bin/install_name_tool
-delete_rpath "/Users/eschnett/SIMFACTORY/boost-1_56_0/install/lib"
"${file}")
execute_process(COMMAND /opt/local/bin/install_name_tool
-add_rpath "/Users/eschnett/SIMFACTORY/hpx-master/install/lib"
"${file}")
execute_process(COMMAND /opt/local/bin/install_name_tool
-add_rpath "/Users/eschnett/SIMFACTORY/boost-1_56_0/install/lib"
"${file}")
```
It appears that these calls to "install_name_tool" somehow break the library. I think that this is an error either in install_name_tool, or in another system tool, or in clang 3.5 that I am using to build HPX, or in cmake 3.0.
Would it be possible to manually uniquify the -rpath options that are passed to the linker, so that each path is listed only once? The file CMakeFiles/parcel_coalescing_lib.dir/link.txt contains indeed two identical -rpath options for the offending path. Unfortunately, my cmake-fu (or lack thereof) doesn't allow me to try this myself.
See also https://github.com/pandegroup/openmm/issues/295, which seems to describe exactly my situation.
| 1.0 | Install failure on OS X -- duplicate rpath entries - I am using OS X Yosemite. I currently cannot build HPX from source. This used to work fine on Mavericks.
The build itself goes fine. The install then emits this error message:
```
/opt/local/bin/install_name_tool: object: /Users/eschnett/SIMFACTORY/hpx-master/install/lib/hpx/libparcel_coalescing.0.9.10.dylib malformed object (load command 39 cmdsize is zero)
```
If I use "otool -l" on this library, then I see that it is indeed broken; I see the same error message.
Using "otool -l" on the original library (the one in the build directory), I see that it is healthy. Just before load command 39 (the load commands are numbered) are the definitions for LC_RPATH, i.e. the path names provided via the -rpath command. I see that the path "/Users/eschnett/SIMFACTORY/boost-1_56_0/install/lib" appears twice.
According to my interpretation of the man page of "install_name_tool" (and Google), this should not be the case -- each path should be unique.
It appears that the commands in the file "cmake_install.cmake" should rewrite these LC_RPATH paths, changing the HPX build directory to the HPX install directory. In my build, these commands are in lines 43 to 59 of this file, and read
```
execute_process(COMMAND "/opt/local/bin/install_name_tool"
-id "libparcel_coalescing.0.dylib"
-change "/Users/eschnett/SIMFACTORY/hpx-master/build/lib/libhpx.0.dylib" "libhpx.0.dylib"
-change "/Users/eschnett/SIMFACTORY/hpx-master/build/lib/libhpx_serialization.0.dylib" "libhpx_serialization.0.dylib"
"${file}")
execute_process(COMMAND /opt/local/bin/install_name_tool
-delete_rpath "/Users/eschnett/SIMFACTORY/hpx-master/build/lib"
"${file}")
execute_process(COMMAND /opt/local/bin/install_name_tool
-delete_rpath "/Users/eschnett/SIMFACTORY/boost-1_56_0/install/lib"
"${file}")
execute_process(COMMAND /opt/local/bin/install_name_tool
-add_rpath "/Users/eschnett/SIMFACTORY/hpx-master/install/lib"
"${file}")
execute_process(COMMAND /opt/local/bin/install_name_tool
-add_rpath "/Users/eschnett/SIMFACTORY/boost-1_56_0/install/lib"
"${file}")
```
It appears that these calls to "install_name_tool" somehow break the library. I think that this is an error either in install_name_tool, or in another system tool, or in clang 3.5 that I am using to build HPX, or in cmake 3.0.
Would it be possible to manually uniquify the -rpath options that are passed to the linker, so that each path is listed only once? The file CMakeFiles/parcel_coalescing_lib.dir/link.txt contains indeed two identical -rpath options for the offending path. Unfortunately, my cmake-fu (or lack thereof) doesn't allow me to try this myself.
See also https://github.com/pandegroup/openmm/issues/295, which seems to describe exactly my situation.
| defect | install failure on os x duplicate rpath entries i am using os x yosemite i currently cannot build hpx from source this used to work fine on mavericks the build itself goes fine the install then emits this error message opt local bin install name tool object users eschnett simfactory hpx master install lib hpx libparcel coalescing dylib malformed object load command cmdsize is zero if i use otool l on this library then i see that it is indeed broken i see the same error message using otool l on the original library the one in the build directory i see that it is healthy just before load command the load commands are numbered are the definitions for lc rpath i e the path names provided via the rpath command i see that the path users eschnett simfactory boost install lib appears twice according to my interpretation of the man page of install name tool and google this should not be the case each path should be unique it appears that the commands in the file cmake install cmake should rewrite these lc rpath paths changing the hpx build directory to the hpx install directory in my build these commands are in lines to of this file and read execute process command opt local bin install name tool id libparcel coalescing dylib change users eschnett simfactory hpx master build lib libhpx dylib libhpx dylib change users eschnett simfactory hpx master build lib libhpx serialization dylib libhpx serialization dylib file execute process command opt local bin install name tool delete rpath users eschnett simfactory hpx master build lib file execute process command opt local bin install name tool delete rpath users eschnett simfactory boost install lib file execute process command opt local bin install name tool add rpath users eschnett simfactory hpx master install lib file execute process command opt local bin install name tool add rpath users eschnett simfactory boost install lib file it appears that these calls to install name tool somehow break the library i think that this is an error either in install name tool or in another system tool or in clang that i am using to build hpx or in cmake would it be possible to manually uniquify the rpath options that are passed to the linker so that each path is listed only once the file cmakefiles parcel coalescing lib dir link txt contains indeed two identical rpath options for the offending path unfortunately my cmake fu or lack thereof doesn t allow me to try this myself see also which seems to describe exactly my situation | 1 |
44,717 | 11,494,676,361 | IssuesEvent | 2020-02-12 02:21:48 | GrangerHub/tremulous-game-logic | https://api.github.com/repos/GrangerHub/tremulous-game-logic | closed | Remove the heal reserve from the medistation, but have the healing of recently damaged humans momentarily delayed (still allow removal of poison imediately though). | accepted buildable combat enhancement game mode human team swirl | Remove the heal reserve from the medistation, but have the healing of recently damaged humans momentarily delayed (still allow removal of poison imediately though). | 1.0 | Remove the heal reserve from the medistation, but have the healing of recently damaged humans momentarily delayed (still allow removal of poison imediately though). - Remove the heal reserve from the medistation, but have the healing of recently damaged humans momentarily delayed (still allow removal of poison imediately though). | non_defect | remove the heal reserve from the medistation but have the healing of recently damaged humans momentarily delayed still allow removal of poison imediately though remove the heal reserve from the medistation but have the healing of recently damaged humans momentarily delayed still allow removal of poison imediately though | 0 |
61,357 | 17,023,673,920 | IssuesEvent | 2021-07-03 03:14:01 | tomhughes/trac-tickets | https://api.github.com/repos/tomhughes/trac-tickets | closed | Rendering of pipelines within areas with certain landuse tags | Component: osmarender Priority: minor Resolution: wontfix Type: defect | **[Submitted to the original trac issue database at 9.55pm, Tuesday, 25th January 2011]**
Osmarender has been so kind as to include pipelines in its rendering rules. Unfortunately, there seems to be an issue with pipelines running through certain landuse=* areas.
Take a look at this: http://www.openstreetmap.org/?mlat=50.80511&mlon=6.16231&zoom=17&layers=O
The heat pipeline (underground, therefore tagged layer=-1) at the tip of the marker is displayed as a reddish, dotted line. Within the farmland cutting into the commercial area, the pipeline disappears. It reappears in the commercial area again (to the west) and just before the motorway (to the northeast), only to disappear again a few hundred meters further, when it enters another landuse=farmland.
The same happens with landuse=forest and landuse=cemetery. (Well yes, the course of the pipeline may still be a bit inaccurate or incomplete, but this ticket is only about the rendering...) With landuse=commercial, landuse=military and landuse=residential, there are no problems.
By the way, I understand that Osmarender's standard layout is not a specialized "infrastructure map", so things like pipelines should not appear too prominently - but maybe the (yellow) gas pipelines could be given a slightly stronger color anyway? | 1.0 | Rendering of pipelines within areas with certain landuse tags - **[Submitted to the original trac issue database at 9.55pm, Tuesday, 25th January 2011]**
Osmarender has been so kind as to include pipelines in its rendering rules. Unfortunately, there seems to be an issue with pipelines running through certain landuse=* areas.
Take a look at this: http://www.openstreetmap.org/?mlat=50.80511&mlon=6.16231&zoom=17&layers=O
The heat pipeline (underground, therefore tagged layer=-1) at the tip of the marker is displayed as a reddish, dotted line. Within the farmland cutting into the commercial area, the pipeline disappears. It reappears in the commercial area again (to the west) and just before the motorway (to the northeast), only to disappear again a few hundred meters further, when it enters another landuse=farmland.
The same happens with landuse=forest and landuse=cemetery. (Well yes, the course of the pipeline may still be a bit inaccurate or incomplete, but this ticket is only about the rendering...) With landuse=commercial, landuse=military and landuse=residential, there are no problems.
By the way, I understand that Osmarender's standard layout is not a specialized "infrastructure map", so things like pipelines should not appear too prominently - but maybe the (yellow) gas pipelines could be given a slightly stronger color anyway? | defect | rendering of pipelines within areas with certain landuse tags osmarender has been so kind as to include pipelines in its rendering rules unfortunately there seems to be an issue with pipelines running through certain landuse areas take a look at this the heat pipeline underground therefore tagged layer at the tip of the marker is displayed as a reddish dotted line within the farmland cutting into the commercial area the pipeline disappears it reappears in the commercial area again to the west and just before the motorway to the northeast only to disappear again a few hundred meters further when it enters another landuse farmland the same happens with landuse forest and landuse cemetery well yes the course of the pipeline may still be a bit inaccurate or incomplete but this ticket is only about the rendering with landuse commercial landuse military and landuse residential there are no problems by the way i understand that osmarender s standard layout is not a specialized infrastructure map so things like pipelines should not appear too prominently but maybe the yellow gas pipelines could be given a slightly stronger color anyway | 1 |
445,474 | 12,831,446,668 | IssuesEvent | 2020-07-07 05:23:19 | qlcchain/go-qlc | https://api.github.com/repos/qlcchain/go-qlc | closed | prepare scripts for the main network upgrade | Priority: High Type: Enhancement | - update the reverse proxy configuration
- deploy new boot node
- etc... | 1.0 | prepare scripts for the main network upgrade - - update the reverse proxy configuration
- deploy new boot node
- etc... | non_defect | prepare scripts for the main network upgrade update the reverse proxy configuration deploy new boot node etc | 0 |
8,287 | 2,611,486,199 | IssuesEvent | 2015-02-27 05:27:27 | chrsmith/switchlist | https://api.github.com/repos/chrsmith/switchlist | closed | Separate checkboxes for "staging" and "offline" is confusing | auto-migrated Priority-Medium Type-Defect | ```
Towns can be in one of three states: in staging, offline, or on the layout.
The Towns panel allows staging and offline to be both set, creating a fourth:
both in staging and offline. That's incorrect, and a probably source of
confusion and bugs.
Change to a three-position pull down?
```
Original issue reported on code.google.com by `rwbowdi...@gmail.com` on 14 Apr 2012 at 4:55 | 1.0 | Separate checkboxes for "staging" and "offline" is confusing - ```
Towns can be in one of three states: in staging, offline, or on the layout.
The Towns panel allows staging and offline to be both set, creating a fourth:
both in staging and offline. That's incorrect, and a probably source of
confusion and bugs.
Change to a three-position pull down?
```
Original issue reported on code.google.com by `rwbowdi...@gmail.com` on 14 Apr 2012 at 4:55 | defect | separate checkboxes for staging and offline is confusing towns can be in one of three states in staging offline or on the layout the towns panel allows staging and offline to be both set creating a fourth both in staging and offline that s incorrect and a probably source of confusion and bugs change to a three position pull down original issue reported on code google com by rwbowdi gmail com on apr at | 1 |
3,151 | 3,811,932,255 | IssuesEvent | 2016-03-27 06:17:55 | moneyballau/statuspage | https://api.github.com/repos/moneyballau/statuspage | closed | API and Server connectivity issues | API degraded performance Website | We are currently experiencing significant connectivity issues to our cloud provider. This issue is being actively worked on and we should be back online soon.
Contest scores and settlement are not affected.
Apologies for any inconvenience. | True | API and Server connectivity issues - We are currently experiencing significant connectivity issues to our cloud provider. This issue is being actively worked on and we should be back online soon.
Contest scores and settlement are not affected.
Apologies for any inconvenience. | non_defect | api and server connectivity issues we are currently experiencing significant connectivity issues to our cloud provider this issue is being actively worked on and we should be back online soon contest scores and settlement are not affected apologies for any inconvenience | 0 |
493,516 | 14,233,966,669 | IssuesEvent | 2020-11-18 12:56:45 | StrangeLoopGames/EcoIssues | https://api.github.com/repos/StrangeLoopGames/EcoIssues | closed | Scrollable exception window | Category: UI Priority: Medium Status: Fixed | Window with exception after crashing should be fixed height with scroll | 1.0 | Scrollable exception window - Window with exception after crashing should be fixed height with scroll | non_defect | scrollable exception window window with exception after crashing should be fixed height with scroll | 0 |
48,692 | 7,451,296,737 | IssuesEvent | 2018-03-29 02:05:22 | marta-file-manager/marta-issues | https://api.github.com/repos/marta-file-manager/marta-issues | closed | Add instructions for removing Marta | documentation fixed | There should be clear instructions about how to delete Marta completely, without leaving its caches or configuration files. | 1.0 | Add instructions for removing Marta - There should be clear instructions about how to delete Marta completely, without leaving its caches or configuration files. | non_defect | add instructions for removing marta there should be clear instructions about how to delete marta completely without leaving its caches or configuration files | 0 |
79,731 | 28,536,922,121 | IssuesEvent | 2023-04-20 00:32:27 | snuailab/waffle_hub | https://api.github.com/repos/snuailab/waffle_hub | closed | Windows copatibility issue (ultralytics) | defect | ### Search before asking
- [X] I have searched the [issues](https://github.com///issues) and found no similar bug report.
### Select Component
_No response_
### Bug
- cannot load pt file from linux on windows.
issue https://github.com/ultralytics/ultralytics/issues/1900
### Environment
_No response_
### Minimal Reproducible Example
_No response_
### Additional
_No response_ | 1.0 | Windows copatibility issue (ultralytics) - ### Search before asking
- [X] I have searched the [issues](https://github.com///issues) and found no similar bug report.
### Select Component
_No response_
### Bug
- cannot load pt file from linux on windows.
issue https://github.com/ultralytics/ultralytics/issues/1900
### Environment
_No response_
### Minimal Reproducible Example
_No response_
### Additional
_No response_ | defect | windows copatibility issue ultralytics search before asking i have searched the and found no similar bug report select component no response bug cannot load pt file from linux on windows issue environment no response minimal reproducible example no response additional no response | 1 |
56,088 | 14,924,924,723 | IssuesEvent | 2021-01-24 02:56:35 | AshleyYakeley/Truth | https://api.github.com/repos/AshleyYakeley/Truth | closed | Types not being brought into scope properly | defect script handling | `let import M; datatype D = MkD T; in return ()`, with `T` exported from `M`, doesn't check. | 1.0 | Types not being brought into scope properly - `let import M; datatype D = MkD T; in return ()`, with `T` exported from `M`, doesn't check. | defect | types not being brought into scope properly let import m datatype d mkd t in return with t exported from m doesn t check | 1 |
380,175 | 26,406,927,368 | IssuesEvent | 2023-01-13 08:54:00 | gravitational/teleport | https://api.github.com/repos/gravitational/teleport | closed | Add Machine ID guide showing `gravitational/teleport-actions/auth-k8s` action | documentation machine-id | Guide should show:
- Creating role with access to a Kubernetes cluster that has already been configured with Teleport
- Creating a bot with access to the above role
- Using `gravitational/teleport-actions/setup` and `gravitational/teleport-actions/auth-k8s` to authenticate with the cluster
Some brief documentation exists at https://github.com/gravitational/teleport-actions#gravitationalteleport-actionsauth-k8s
| 1.0 | Add Machine ID guide showing `gravitational/teleport-actions/auth-k8s` action - Guide should show:
- Creating role with access to a Kubernetes cluster that has already been configured with Teleport
- Creating a bot with access to the above role
- Using `gravitational/teleport-actions/setup` and `gravitational/teleport-actions/auth-k8s` to authenticate with the cluster
Some brief documentation exists at https://github.com/gravitational/teleport-actions#gravitationalteleport-actionsauth-k8s
| non_defect | add machine id guide showing gravitational teleport actions auth action guide should show creating role with access to a kubernetes cluster that has already been configured with teleport creating a bot with access to the above role using gravitational teleport actions setup and gravitational teleport actions auth to authenticate with the cluster some brief documentation exists at | 0 |
16,420 | 2,892,782,152 | IssuesEvent | 2015-06-15 14:46:05 | zaproxy/zaproxy | https://api.github.com/repos/zaproxy/zaproxy | closed | Search regex might not be validated | Priority-Medium Type-Defect | ```
From Issue 1615.
Steps to reproduce the issue:
1. Run ZAP;
2. Select the "Search" tab;
3. Add an invalid regex, for example "*", and press Enter;
4. Note that no dialogue is shown indicating that the regex is invalid, also in the
log there's an exception:
[...]
33606 [ZAP-SearchThread] ERROR org.zaproxy.zap.ZAP$UncaughtExceptionLogger - Exception
in thread "ZAP-SearchThread"
java.util.regex.PatternSyntaxException: Dangling meta character '*' near index 0
*
^
at java.util.regex.Pattern.error(Pattern.java:1924)
at java.util.regex.Pattern.sequence(Pattern.java:2090)
at java.util.regex.Pattern.expr(Pattern.java:1964)
at java.util.regex.Pattern.compile(Pattern.java:1665)
at java.util.regex.Pattern.<init>(Pattern.java:1337)
at java.util.regex.Pattern.compile(Pattern.java:1047)
at org.zaproxy.zap.extension.search.SearchThread.search(Unknown Source)
at org.zaproxy.zap.extension.search.SearchThread.run(Unknown Source)
[...]
Remarks:
If the search is started by clicking the "Search" button the regex is validated.
ZAP Version:
Version 2.4.0 (previous versions are also affected)
```
Original issue reported on code.google.com by `THC202` on 2015-04-30 14:04:12 | 1.0 | Search regex might not be validated - ```
From Issue 1615.
Steps to reproduce the issue:
1. Run ZAP;
2. Select the "Search" tab;
3. Add an invalid regex, for example "*", and press Enter;
4. Note that no dialogue is shown indicating that the regex is invalid, also in the
log there's an exception:
[...]
33606 [ZAP-SearchThread] ERROR org.zaproxy.zap.ZAP$UncaughtExceptionLogger - Exception
in thread "ZAP-SearchThread"
java.util.regex.PatternSyntaxException: Dangling meta character '*' near index 0
*
^
at java.util.regex.Pattern.error(Pattern.java:1924)
at java.util.regex.Pattern.sequence(Pattern.java:2090)
at java.util.regex.Pattern.expr(Pattern.java:1964)
at java.util.regex.Pattern.compile(Pattern.java:1665)
at java.util.regex.Pattern.<init>(Pattern.java:1337)
at java.util.regex.Pattern.compile(Pattern.java:1047)
at org.zaproxy.zap.extension.search.SearchThread.search(Unknown Source)
at org.zaproxy.zap.extension.search.SearchThread.run(Unknown Source)
[...]
Remarks:
If the search is started by clicking the "Search" button the regex is validated.
ZAP Version:
Version 2.4.0 (previous versions are also affected)
```
Original issue reported on code.google.com by `THC202` on 2015-04-30 14:04:12 | defect | search regex might not be validated from issue steps to reproduce the issue run zap select the search tab add an invalid regex for example and press enter note that no dialogue is shown indicating that the regex is invalid also in the log there s an exception error org zaproxy zap zap uncaughtexceptionlogger exception in thread zap searchthread java util regex patternsyntaxexception dangling meta character near index at java util regex pattern error pattern java at java util regex pattern sequence pattern java at java util regex pattern expr pattern java at java util regex pattern compile pattern java at java util regex pattern pattern java at java util regex pattern compile pattern java at org zaproxy zap extension search searchthread search unknown source at org zaproxy zap extension search searchthread run unknown source remarks if the search is started by clicking the search button the regex is validated zap version version previous versions are also affected original issue reported on code google com by on | 1 |
5,867 | 2,610,216,952 | IssuesEvent | 2015-02-26 19:09:06 | chrsmith/somefinders | https://api.github.com/repos/chrsmith/somefinders | opened | практикум по бухгалтерскому учету самохвалова | auto-migrated Priority-Medium Type-Defect | ```
'''Борис Щукин'''
Привет всем не подскажите где можно найти
.практикум по бухгалтерскому учету
самохвалова. где то видел уже
'''Виолен Сергеев'''
Вот хороший сайт где можно скачать
http://bit.ly/1862RsN
'''Володар Егоров'''
Просит ввести номер мобилы!Не опасно ли это?
'''Гарибальди Дмитриев'''
Не это не влияет на баланс
'''Горазд Соколов'''
Неа все ок у меня ничего не списало
Информация о файле: практикум по
бухгалтерскому учету самохвалова
Загружен: В этом месяце
Скачан раз: 215
Рейтинг: 313
Средняя скорость скачивания: 1242
Похожих файлов: 14
```
-----
Original issue reported on code.google.com by `kondense...@gmail.com` on 16 Dec 2013 at 9:47 | 1.0 | практикум по бухгалтерскому учету самохвалова - ```
'''Борис Щукин'''
Привет всем не подскажите где можно найти
.практикум по бухгалтерскому учету
самохвалова. где то видел уже
'''Виолен Сергеев'''
Вот хороший сайт где можно скачать
http://bit.ly/1862RsN
'''Володар Егоров'''
Просит ввести номер мобилы!Не опасно ли это?
'''Гарибальди Дмитриев'''
Не это не влияет на баланс
'''Горазд Соколов'''
Неа все ок у меня ничего не списало
Информация о файле: практикум по
бухгалтерскому учету самохвалова
Загружен: В этом месяце
Скачан раз: 215
Рейтинг: 313
Средняя скорость скачивания: 1242
Похожих файлов: 14
```
-----
Original issue reported on code.google.com by `kondense...@gmail.com` on 16 Dec 2013 at 9:47 | defect | практикум по бухгалтерскому учету самохвалова борис щукин привет всем не подскажите где можно найти практикум по бухгалтерскому учету самохвалова где то видел уже виолен сергеев вот хороший сайт где можно скачать володар егоров просит ввести номер мобилы не опасно ли это гарибальди дмитриев не это не влияет на баланс горазд соколов неа все ок у меня ничего не списало информация о файле практикум по бухгалтерскому учету самохвалова загружен в этом месяце скачан раз рейтинг средняя скорость скачивания похожих файлов original issue reported on code google com by kondense gmail com on dec at | 1 |
4,412 | 2,610,093,649 | IssuesEvent | 2015-02-26 18:28:16 | chrsmith/dsdsdaadf | https://api.github.com/repos/chrsmith/dsdsdaadf | opened | 深圳韩方科颜多少钱 | auto-migrated Priority-Medium Type-Defect | ```
深圳韩方科颜多少钱【深圳韩方科颜全国热线400-869-1818，24小
时QQ4008691818】深圳韩方科颜专业祛痘连锁机构，机构以韩国��
�方——韩方科颜这一国妆准字号治疗型权威，祛痘佳品，韩�
��科颜专业祛痘连锁机构，采用韩国秘方配合专业“不反弹”
健康祛痘技术并结合先进“先进豪华彩光”仪，开创国内专��
�治疗粉刺、痤疮签约包治先河，成功消除了许多顾客脸上的�
��痘。
```
-----
Original issue reported on code.google.com by `szft...@163.com` on 14 May 2014 at 8:09 | 1.0 | 深圳韩方科颜多少钱 - ```
深圳韩方科颜多少钱【深圳韩方科颜全国热线400-869-1818，24小
时QQ4008691818】深圳韩方科颜专业祛痘连锁机构，机构以韩国��
�方——韩方科颜这一国妆准字号治疗型权威，祛痘佳品，韩�
��科颜专业祛痘连锁机构，采用韩国秘方配合专业“不反弹”
健康祛痘技术并结合先进“先进豪华彩光”仪，开创国内专��
�治疗粉刺、痤疮签约包治先河，成功消除了许多顾客脸上的�
��痘。
```
-----
Original issue reported on code.google.com by `szft...@163.com` on 14 May 2014 at 8:09 | defect | 深圳韩方科颜多少钱 深圳韩方科颜多少钱【 ， 】深圳韩方科颜专业祛痘连锁机构，机构以韩国�� �方——韩方科颜这一国妆准字号治疗型权威，祛痘佳品，韩� ��科颜专业祛痘连锁机构，采用韩国秘方配合专业“不反弹” 健康祛痘技术并结合先进“先进豪华彩光”仪，开创国内专�� �治疗粉刺、痤疮签约包治先河，成功消除了许多顾客脸上的� ��痘。 original issue reported on code google com by szft com on may at | 1 |
73,213 | 24,508,882,228 | IssuesEvent | 2022-10-10 19:11:44 | Gogo1951/Groupie | https://api.github.com/repos/Gogo1951/Groupie | closed | Remove Distorted Screenshots for Certain Instances | Priority - 3 Average Type - Defect | These don't gel with the design, let's remove these. If we don't have a badge for an instance or group, we can just use a ? badge.
I'll work on creating more badges. The squished & distorted images look awful. | 1.0 | Remove Distorted Screenshots for Certain Instances - These don't gel with the design, let's remove these. If we don't have a badge for an instance or group, we can just use a ? badge.
I'll work on creating more badges. The squished & distorted images look awful. | defect | remove distorted screenshots for certain instances these don t gel with the design let s remove these if we don t have a badge for an instance or group we can just use a badge i ll work on creating more badges the squished distorted images look awful | 1 |
10,362 | 8,026,584,477 | IssuesEvent | 2018-07-27 05:09:51 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | server: node communication issues using 3rd party certificates | A-core-security C-investigation O-community | Issue/Bug/Question
Summary:
We are using our own certificate authority to create certificates for our Cockroach cluster build. After creating the certificates, we are experiencing communication issues when attempting to start the cluster. Port communication on 26257 between the nodes does not seem to be an issues since we can telnet after starting the service. We also verified the node.crt and client.root.crt files against the ca.crt and they return valid.
Steps to reproduce:
Created node.crt and client.root.crt using a third party CA.
Started cockroach on all 3 nodes
Results Expected:
Cluster communication between nodes to be successful.
Results Occured:
Cluster will not start. Following message is returned: WARNING: The server appears to be unable to contact the other nodes in the cluster.
Logs:
Logs are attached.
[cockroach-10.log](https://github.com/cockroachdb/cockroach/files/2190368/cockroach-10.log)
[cockroach-20.log](https://github.com/cockroachdb/cockroach/files/2190369/cockroach-20.log)
[cockroach-30.log](https://github.com/cockroachdb/cockroach/files/2190370/cockroach-30.log)
Version:
Build Tag: v2.0.2
Build Time: 2018/05/21 14:55:20
Distribution: CCL
Platform: linux amd64 (x86_64-unknown-linux-gnu)
Go Version: go1.10
C Compiler: gcc 6.3.0
Build SHA-1: fa2b2bfd802ebe8150030a14b0a36c25fef90b91
Build Type: release
Certificate Validation:
openssl verify -CAfile ca.crt node.crt
node.crt: OK
openssl verify -CAfile ca.crt client.root.crt
client.root.crt: OK | True | server: node communication issues using 3rd party certificates - Issue/Bug/Question
Summary:
We are using our own certificate authority to create certificates for our Cockroach cluster build. After creating the certificates, we are experiencing communication issues when attempting to start the cluster. Port communication on 26257 between the nodes does not seem to be an issues since we can telnet after starting the service. We also verified the node.crt and client.root.crt files against the ca.crt and they return valid.
Steps to reproduce:
Created node.crt and client.root.crt using a third party CA.
Started cockroach on all 3 nodes
Results Expected:
Cluster communication between nodes to be successful.
Results Occured:
Cluster will not start. Following message is returned: WARNING: The server appears to be unable to contact the other nodes in the cluster.
Logs:
Logs are attached.
[cockroach-10.log](https://github.com/cockroachdb/cockroach/files/2190368/cockroach-10.log)
[cockroach-20.log](https://github.com/cockroachdb/cockroach/files/2190369/cockroach-20.log)
[cockroach-30.log](https://github.com/cockroachdb/cockroach/files/2190370/cockroach-30.log)
Version:
Build Tag: v2.0.2
Build Time: 2018/05/21 14:55:20
Distribution: CCL
Platform: linux amd64 (x86_64-unknown-linux-gnu)
Go Version: go1.10
C Compiler: gcc 6.3.0
Build SHA-1: fa2b2bfd802ebe8150030a14b0a36c25fef90b91
Build Type: release
Certificate Validation:
openssl verify -CAfile ca.crt node.crt
node.crt: OK
openssl verify -CAfile ca.crt client.root.crt
client.root.crt: OK | non_defect | server node communication issues using party certificates issue bug question summary we are using our own certificate authority to create certificates for our cockroach cluster build after creating the certificates we are experiencing communication issues when attempting to start the cluster port communication on between the nodes does not seem to be an issues since we can telnet after starting the service we also verified the node crt and client root crt files against the ca crt and they return valid steps to reproduce created node crt and client root crt using a third party ca started cockroach on all nodes results expected cluster communication between nodes to be successful results occured cluster will not start following message is returned warning the server appears to be unable to contact the other nodes in the cluster logs logs are attached version build tag build time distribution ccl platform linux unknown linux gnu go version c compiler gcc build sha build type release certificate validation openssl verify cafile ca crt node crt node crt ok openssl verify cafile ca crt client root crt client root crt ok | 0 |
181,880 | 6,664,993,247 | IssuesEvent | 2017-10-02 22:25:13 | classifiedz/classifiedz.github.io | https://api.github.com/repos/classifiedz/classifiedz.github.io | closed | [User Story] Post Ad Page | High Priority Post Ad Story | ## Create a post ad page
Users should should be able to create and ad post where all the details of their item can be given. The ad should appear on the main page once submitted. Users should also be able to access this option from the navbar.
- [x] Post ad page template #37
- [x] Input fields for title #38
- [x] Input fields for description #39
- [x] Category specification #40
- [x] Upload image button #41
- [x] Contact preference #42
- [x] Price input #43
- [x] Submit/Cancel buttons #44
- [ ] Have the ads posted to the front page #45
- [x] Gain access to the page through the navbar #46
- [x] Functional image upload #52 | 1.0 | [User Story] Post Ad Page - ## Create a post ad page
Users should should be able to create and ad post where all the details of their item can be given. The ad should appear on the main page once submitted. Users should also be able to access this option from the navbar.
- [x] Post ad page template #37
- [x] Input fields for title #38
- [x] Input fields for description #39
- [x] Category specification #40
- [x] Upload image button #41
- [x] Contact preference #42
- [x] Price input #43
- [x] Submit/Cancel buttons #44
- [ ] Have the ads posted to the front page #45
- [x] Gain access to the page through the navbar #46
- [x] Functional image upload #52 | non_defect | post ad page create a post ad page users should should be able to create and ad post where all the details of their item can be given the ad should appear on the main page once submitted users should also be able to access this option from the navbar post ad page template input fields for title input fields for description category specification upload image button contact preference price input submit cancel buttons have the ads posted to the front page gain access to the page through the navbar functional image upload | 0 |
38,513 | 8,870,054,705 | IssuesEvent | 2019-01-11 08:16:12 | contao/contao | https://api.github.com/repos/contao/contao | closed | Throw distinct exceptions in the opt-in service | defect | The exceptions that can be thrown should be documented with `@throws` and ideally they should be special exceptions. E.g. `TokenAlreadyConfirmedException`.
_Originally posted by @Toflar in https://github.com/contao/contao/pull/196#discussion_r243554813_ | 1.0 | Throw distinct exceptions in the opt-in service - The exceptions that can be thrown should be documented with `@throws` and ideally they should be special exceptions. E.g. `TokenAlreadyConfirmedException`.
_Originally posted by @Toflar in https://github.com/contao/contao/pull/196#discussion_r243554813_ | defect | throw distinct exceptions in the opt in service the exceptions that can be thrown should be documented with throws and ideally they should be special exceptions e g tokenalreadyconfirmedexception originally posted by toflar in | 1 |
616,456 | 19,303,136,786 | IssuesEvent | 2021-12-13 08:41:59 | MaibornWolff/codecharta | https://api.github.com/repos/MaibornWolff/codecharta | reopened | Improve custom configs | pr-visualization feature priority:urgent | # Feature request
## Description
As a user, I want custom configs to be easily understandable and easy to use so that I do not have to invest a lot of time using them.
## Acceptance criteria
- [x] Remove notification when removing entries (just remove the entry by collapsing the list)
- [ ] "AI" entries should not be kept in the local storage. They are recalculated as soon as the map is loaded anyway. Have a look here: #2435.
- [ ] Do not show non-matching entries by default! Only list matching entries for the loaded maps. All others should be in a separate category.
- [ ] Highlight matching entries for the currently loaded mode (single, multiple, diff)
- [ ] More intuitive UI in general (TBD)
- [ ] Mark custom configs as stable and remove download button (do not start before the other parts are resolved)
- [ ] Resolve https://github.com/MaibornWolff/codecharta/issues/940 as cleanup after removing the download button | 1.0 | Improve custom configs - # Feature request
## Description
As a user, I want custom configs to be easily understandable and easy to use so that I do not have to invest a lot of time using them.
## Acceptance criteria
- [x] Remove notification when removing entries (just remove the entry by collapsing the list)
- [ ] "AI" entries should not be kept in the local storage. They are recalculated as soon as the map is loaded anyway. Have a look here: #2435.
- [ ] Do not show non-matching entries by default! Only list matching entries for the loaded maps. All others should be in a separate category.
- [ ] Highlight matching entries for the currently loaded mode (single, multiple, diff)
- [ ] More intuitive UI in general (TBD)
- [ ] Mark custom configs as stable and remove download button (do not start before the other parts are resolved)
- [ ] Resolve https://github.com/MaibornWolff/codecharta/issues/940 as cleanup after removing the download button | non_defect | improve custom configs feature request description as a user i want custom configs to be easily understandable and easy to use so that i do not have to invest a lot of time using them acceptance criteria remove notification when removing entries just remove the entry by collapsing the list ai entries should not be kept in the local storage they are recalculated as soon as the map is loaded anyway have a look here do not show non matching entries by default only list matching entries for the loaded maps all others should be in a separate category highlight matching entries for the currently loaded mode single multiple diff more intuitive ui in general tbd mark custom configs as stable and remove download button do not start before the other parts are resolved resolve as cleanup after removing the download button | 0 |
23,057 | 3,755,593,135 | IssuesEvent | 2016-03-12 19:27:48 | RomanGolovanov/aMetro | https://api.github.com/repos/RomanGolovanov/aMetro | closed | [FR] Расписание / timetable | auto-migrated Priority-Medium Type-Defect | ```
было бы чудесно ещё иметь расписание
поездов в программе.
В качестве примера могу привести
https://play.google.com/store/apps/details?id=com.witharts.metro
```
Original issue reported on code.google.com by `ildar.mulyukov` on 26 Sep 2014 at 5:11 | 1.0 | [FR] Расписание / timetable - ```
было бы чудесно ещё иметь расписание
поездов в программе.
В качестве примера могу привести
https://play.google.com/store/apps/details?id=com.witharts.metro
```
Original issue reported on code.google.com by `ildar.mulyukov` on 26 Sep 2014 at 5:11 | defect | расписание timetable было бы чудесно ещё иметь расписание поездов в программе в качестве примера могу привести original issue reported on code google com by ildar mulyukov on sep at | 1 |
23,396 | 3,812,039,801 | IssuesEvent | 2016-03-27 08:38:36 | TrendBreaker/django-alchemy | https://api.github.com/repos/TrendBreaker/django-alchemy | closed | syncdb needs to support loading custom sql and fixtures | auto-migrated Component-Commands Priority-Medium Type-Defect | ```
Currently syncdb is just passing off the creation of missing tables to SA. We
need to also structure
this is such a way that custom sql can be run for those tables that were
created. This is going to be
a bit challenging since we need to find a way to get the list of tables back
out of SA.
Additionally we are not loading in any fixtures which happens with syncdb.
```
Original issue reported on code.google.com by `mtr...@gmail.com` on 26 Mar 2008 at 1:26 | 1.0 | syncdb needs to support loading custom sql and fixtures - ```
Currently syncdb is just passing off the creation of missing tables to SA. We
need to also structure
this is such a way that custom sql can be run for those tables that were
created. This is going to be
a bit challenging since we need to find a way to get the list of tables back
out of SA.
Additionally we are not loading in any fixtures which happens with syncdb.
```
Original issue reported on code.google.com by `mtr...@gmail.com` on 26 Mar 2008 at 1:26 | defect | syncdb needs to support loading custom sql and fixtures currently syncdb is just passing off the creation of missing tables to sa we need to also structure this is such a way that custom sql can be run for those tables that were created this is going to be a bit challenging since we need to find a way to get the list of tables back out of sa additionally we are not loading in any fixtures which happens with syncdb original issue reported on code google com by mtr gmail com on mar at | 1 |
52,997 | 13,781,959,899 | IssuesEvent | 2020-10-08 16:55:37 | ioana-nicolae/first | https://api.github.com/repos/ioana-nicolae/first | opened | WS-2016-0039 (High) detected in shell-quote-0.0.1.tgz | security vulnerability | ## WS-2016-0039 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>shell-quote-0.0.1.tgz</b></p></summary>
<p>quote and parse shell commands</p>
<p>Library home page: <a href="https://registry.npmjs.org/shell-quote/-/shell-quote-0.0.1.tgz">https://registry.npmjs.org/shell-quote/-/shell-quote-0.0.1.tgz</a></p>
<p>Path to dependency file: first/angular.js-master/angular.js-master/yarn.lock</p>
<p>Path to vulnerable library: first/angular.js-master/angular.js-master/yarn.lock</p>
<p>
Dependency Hierarchy:
- angular-benchpress-0.2.2.tgz (Root Library)
- browserify-7.0.3.tgz
- :x: **shell-quote-0.0.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ioana-nicolae/first/commit/6e040516f98074b37f69996b76c1c99015c1d685">6e040516f98074b37f69996b76c1c99015c1d685</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The npm module "shell-quote" cannot correctly escape "greater than" and "lower than" operator used for redirection in shell. This might be possible vulnerability for many application which depends on shell-quote.
<p>Publish Date: 2016-05-20
<p>URL: <a href=https://github.com/substack/node-shell-quote/commit/70e9eb2a854eb56a3dfa255be12610a722bbe080>WS-2016-0039</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>8.4</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nodesecurity.io/advisories/117">https://nodesecurity.io/advisories/117</a></p>
<p>Release Date: 2016-06-21</p>
<p>Fix Resolution: Upgrade to at least version 1.6.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"shell-quote","packageVersion":"0.0.1","isTransitiveDependency":true,"dependencyTree":"angular-benchpress:0.2.2;browserify:7.0.3;shell-quote:0.0.1","isMinimumFixVersionAvailable":false}],"vulnerabilityIdentifier":"WS-2016-0039","vulnerabilityDetails":"The npm module \"shell-quote\" cannot correctly escape \"greater than\" and \"lower than\" operator used for redirection in shell. This might be possible vulnerability for many application which depends on shell-quote.","vulnerabilityUrl":"https://github.com/substack/node-shell-quote/commit/70e9eb2a854eb56a3dfa255be12610a722bbe080","cvss2Severity":"high","cvss2Score":"8.4","extraData":{}}</REMEDIATE> --> | True | WS-2016-0039 (High) detected in shell-quote-0.0.1.tgz - ## WS-2016-0039 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>shell-quote-0.0.1.tgz</b></p></summary>
<p>quote and parse shell commands</p>
<p>Library home page: <a href="https://registry.npmjs.org/shell-quote/-/shell-quote-0.0.1.tgz">https://registry.npmjs.org/shell-quote/-/shell-quote-0.0.1.tgz</a></p>
<p>Path to dependency file: first/angular.js-master/angular.js-master/yarn.lock</p>
<p>Path to vulnerable library: first/angular.js-master/angular.js-master/yarn.lock</p>
<p>
Dependency Hierarchy:
- angular-benchpress-0.2.2.tgz (Root Library)
- browserify-7.0.3.tgz
- :x: **shell-quote-0.0.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ioana-nicolae/first/commit/6e040516f98074b37f69996b76c1c99015c1d685">6e040516f98074b37f69996b76c1c99015c1d685</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The npm module "shell-quote" cannot correctly escape "greater than" and "lower than" operator used for redirection in shell. This might be possible vulnerability for many application which depends on shell-quote.
<p>Publish Date: 2016-05-20
<p>URL: <a href=https://github.com/substack/node-shell-quote/commit/70e9eb2a854eb56a3dfa255be12610a722bbe080>WS-2016-0039</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>8.4</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nodesecurity.io/advisories/117">https://nodesecurity.io/advisories/117</a></p>
<p>Release Date: 2016-06-21</p>
<p>Fix Resolution: Upgrade to at least version 1.6.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"shell-quote","packageVersion":"0.0.1","isTransitiveDependency":true,"dependencyTree":"angular-benchpress:0.2.2;browserify:7.0.3;shell-quote:0.0.1","isMinimumFixVersionAvailable":false}],"vulnerabilityIdentifier":"WS-2016-0039","vulnerabilityDetails":"The npm module \"shell-quote\" cannot correctly escape \"greater than\" and \"lower than\" operator used for redirection in shell. This might be possible vulnerability for many application which depends on shell-quote.","vulnerabilityUrl":"https://github.com/substack/node-shell-quote/commit/70e9eb2a854eb56a3dfa255be12610a722bbe080","cvss2Severity":"high","cvss2Score":"8.4","extraData":{}}</REMEDIATE> --> | non_defect | ws high detected in shell quote tgz ws high severity vulnerability vulnerable library shell quote tgz quote and parse shell commands library home page a href path to dependency file first angular js master angular js master yarn lock path to vulnerable library first angular js master angular js master yarn lock dependency hierarchy angular benchpress tgz root library browserify tgz x shell quote tgz vulnerable library found in head commit a href found in base branch master vulnerability details the npm module shell quote cannot correctly escape greater than and lower than operator used for redirection in shell this might be possible vulnerability for many application which depends on shell quote publish date url a href cvss score details base score metrics not available suggested fix type upgrade version origin a href release date fix resolution upgrade to at least version isopenpronvulnerability false ispackagebased true isdefaultbranch true packages vulnerabilityidentifier ws vulnerabilitydetails the npm module shell quote cannot correctly escape greater than and lower than operator used for redirection in shell this might be possible vulnerability for many application which depends on shell quote vulnerabilityurl | 0 |
47,228 | 13,056,065,160 | IssuesEvent | 2020-07-30 03:33:02 | icecube-trac/tix2 | https://api.github.com/repos/icecube-trac/tix2 | closed | terst (Trac #165) | Migrated from Trac combo reconstruction defect | test test
Migrated from https://code.icecube.wisc.edu/ticket/165
```json
{
"status": "closed",
"changetime": "2009-06-30T13:34:54",
"description": "test test",
"reporter": "cgils",
"cc": "",
"resolution": "fixed",
"_ts": "1246368894000000",
"component": "combo reconstruction",
"summary": "terst",
"priority": "normal",
"keywords": "",
"time": "2009-06-30T13:33:04",
"milestone": "",
"owner": "kislat",
"type": "defect"
}
```
| 1.0 | terst (Trac #165) - test test
Migrated from https://code.icecube.wisc.edu/ticket/165
```json
{
"status": "closed",
"changetime": "2009-06-30T13:34:54",
"description": "test test",
"reporter": "cgils",
"cc": "",
"resolution": "fixed",
"_ts": "1246368894000000",
"component": "combo reconstruction",
"summary": "terst",
"priority": "normal",
"keywords": "",
"time": "2009-06-30T13:33:04",
"milestone": "",
"owner": "kislat",
"type": "defect"
}
```
| defect | terst trac test test migrated from json status closed changetime description test test reporter cgils cc resolution fixed ts component combo reconstruction summary terst priority normal keywords time milestone owner kislat type defect | 1 |
43,930 | 11,882,314,378 | IssuesEvent | 2020-03-27 14:12:45 | scipy/scipy | https://api.github.com/repos/scipy/scipy | closed | documentation of scipy.spatial.HalfspaceIntersection: wrong method to compute feasible point | Documentation defect scipy.spatial | I am reading the docs of:
https://docs.scipy.org/doc/scipy/reference/generated/scipy.spatial.HalfspaceIntersection.html
the example states an algorithm for computing a feasible point for the halfspace intersection algorithm by setting up a linear problem. However, the algorithm uses
res = scipy.optimize.linprog(c, A_ub=A, b_ub=b)
to solve the problem, which additionally adds an implicit constraint x>0. This works in the example as the solution indeed produces positive values only. But in the code example below, flipping the one constraint in the example around to produce negative x-values will result in the wrong solution.
The correct way is to explicitly disable all box-constraints:
res = scipy.optimize.linprog(c, A_ub=A, b_ub=b, bounds = (None,None))
#### Reproducing code example:
```
from scipy.spatial import HalfspaceIntersection
from scipy.optimize import linprog
import numpy as np
halfspaces = np.array([[1, 0., 0.], # example uses -1
[0., -1., 0.],
[2., 1., -4.],
[-0.5, 1., -2.]])
norm_vector = np.reshape(np.linalg.norm(halfspaces[:, :-1], axis=1),
(halfspaces.shape[0], 1))
c = np.zeros((halfspaces.shape[1],))
c[-1] = -1
A = np.hstack((halfspaces[:, :-1], norm_vector))
b = - halfspaces[:, -1:]
#wrong:
res = linprog(c, A_ub=A, b_ub=b)
print(res.x)
#correct
res = linprog(c, A_ub=A, b_ub=b, bounds = (None,None))
print(res.x)
```
#### Scipy/Numpy/Python version information:
1.4.1 1.17.4 sys.version_info(major=3, minor=7, micro=0, releaselevel='final', serial=0) | 1.0 | documentation of scipy.spatial.HalfspaceIntersection: wrong method to compute feasible point - I am reading the docs of:
https://docs.scipy.org/doc/scipy/reference/generated/scipy.spatial.HalfspaceIntersection.html
the example states an algorithm for computing a feasible point for the halfspace intersection algorithm by setting up a linear problem. However, the algorithm uses
res = scipy.optimize.linprog(c, A_ub=A, b_ub=b)
to solve the problem, which additionally adds an implicit constraint x>0. This works in the example as the solution indeed produces positive values only. But in the code example below, flipping the one constraint in the example around to produce negative x-values will result in the wrong solution.
The correct way is to explicitly disable all box-constraints:
res = scipy.optimize.linprog(c, A_ub=A, b_ub=b, bounds = (None,None))
#### Reproducing code example:
```
from scipy.spatial import HalfspaceIntersection
from scipy.optimize import linprog
import numpy as np
halfspaces = np.array([[1, 0., 0.], # example uses -1
[0., -1., 0.],
[2., 1., -4.],
[-0.5, 1., -2.]])
norm_vector = np.reshape(np.linalg.norm(halfspaces[:, :-1], axis=1),
(halfspaces.shape[0], 1))
c = np.zeros((halfspaces.shape[1],))
c[-1] = -1
A = np.hstack((halfspaces[:, :-1], norm_vector))
b = - halfspaces[:, -1:]
#wrong:
res = linprog(c, A_ub=A, b_ub=b)
print(res.x)
#correct
res = linprog(c, A_ub=A, b_ub=b, bounds = (None,None))
print(res.x)
```
#### Scipy/Numpy/Python version information:
1.4.1 1.17.4 sys.version_info(major=3, minor=7, micro=0, releaselevel='final', serial=0) | defect | documentation of scipy spatial halfspaceintersection wrong method to compute feasible point i am reading the docs of the example states an algorithm for computing a feasible point for the halfspace intersection algorithm by setting up a linear problem however the algorithm uses res scipy optimize linprog c a ub a b ub b to solve the problem which additionally adds an implicit constraint x this works in the example as the solution indeed produces positive values only but in the code example below flipping the one constraint in the example around to produce negative x values will result in the wrong solution the correct way is to explicitly disable all box constraints res scipy optimize linprog c a ub a b ub b bounds none none reproducing code example from scipy spatial import halfspaceintersection from scipy optimize import linprog import numpy as np halfspaces np array example uses norm vector np reshape np linalg norm halfspaces axis halfspaces shape c np zeros halfspaces shape c a np hstack halfspaces norm vector b halfspaces wrong res linprog c a ub a b ub b print res x correct res linprog c a ub a b ub b bounds none none print res x scipy numpy python version information sys version info major minor micro releaselevel final serial | 1 |
431,766 | 30,250,191,279 | IssuesEvent | 2023-07-06 19:52:39 | Xpra-org/xpra | https://api.github.com/repos/Xpra-org/xpra | closed | [Documentation / Examples / Screenshots] Could this be added as a link or something to the main README? | documentation enhancement help wanted | Hey xpra devs,
I found this project via gosu ( a C++ and ruby engine).
However, I am not entirely sure what is possible with xpra exactly.
Would it be possible to add a few partial screenshots of what people do with it? This does not
have to be all-inclusive, really just a few screenshots to see in one glance what can be done
with it. Does not have to be listed in the main README per se (although that is also possible
of course); could just be a separate page that keeps a few screenshots. While I am a ruby
guy, I am fine with python examples too and even other languages - I am mostly interested
in "what can be done with xrpa specifically". (If there was a screenshot page already as-is
I may not have seen it; in that case perhaps the section on the README could be made
longer in this regard.) Thank you for reading and potentially considering. | 1.0 | [Documentation / Examples / Screenshots] Could this be added as a link or something to the main README? - Hey xpra devs,
I found this project via gosu ( a C++ and ruby engine).
However, I am not entirely sure what is possible with xpra exactly.
Would it be possible to add a few partial screenshots of what people do with it? This does not
have to be all-inclusive, really just a few screenshots to see in one glance what can be done
with it. Does not have to be listed in the main README per se (although that is also possible
of course); could just be a separate page that keeps a few screenshots. While I am a ruby
guy, I am fine with python examples too and even other languages - I am mostly interested
in "what can be done with xrpa specifically". (If there was a screenshot page already as-is
I may not have seen it; in that case perhaps the section on the README could be made
longer in this regard.) Thank you for reading and potentially considering. | non_defect | could this be added as a link or something to the main readme hey xpra devs i found this project via gosu a c and ruby engine however i am not entirely sure what is possible with xpra exactly would it be possible to add a few partial screenshots of what people do with it this does not have to be all inclusive really just a few screenshots to see in one glance what can be done with it does not have to be listed in the main readme per se although that is also possible of course could just be a separate page that keeps a few screenshots while i am a ruby guy i am fine with python examples too and even other languages i am mostly interested in what can be done with xrpa specifically if there was a screenshot page already as is i may not have seen it in that case perhaps the section on the readme could be made longer in this regard thank you for reading and potentially considering | 0 |
189,713 | 15,193,848,498 | IssuesEvent | 2021-02-16 01:54:57 | livgust/macovidvaccines.com | https://api.github.com/repos/livgust/macovidvaccines.com | closed | Add CONTRIBUTING.md | documentation | It could be helpful, as the project matures, to include a markdown file that describes how people can contribute. I found [a nifty guide](https://opensource.guide/starting-a-project/#your-pre-launch-checklist) here. For now, it can probably be pretty simple. | 1.0 | Add CONTRIBUTING.md - It could be helpful, as the project matures, to include a markdown file that describes how people can contribute. I found [a nifty guide](https://opensource.guide/starting-a-project/#your-pre-launch-checklist) here. For now, it can probably be pretty simple. | non_defect | add contributing md it could be helpful as the project matures to include a markdown file that describes how people can contribute i found here for now it can probably be pretty simple | 0 |
179,679 | 30,284,752,973 | IssuesEvent | 2023-07-08 14:26:09 | hashgraph/hedera-json-rpc-relay | https://api.github.com/repos/hashgraph/hedera-json-rpc-relay | opened | [Design] Add monitoring and alerting rules | enhancement Epic P2 design | ### Problem
The relay publishes metrics uses prometheus, however, no rules are defined to enable relay operators to observe and support alerting.
### Solution
Explore the design and necessary implementation steps to support this and update the relay.
Create sub epic tasklist to capture the necessary work
### Alternatives
_No response_ | 1.0 | [Design] Add monitoring and alerting rules - ### Problem
The relay publishes metrics uses prometheus, however, no rules are defined to enable relay operators to observe and support alerting.
### Solution
Explore the design and necessary implementation steps to support this and update the relay.
Create sub epic tasklist to capture the necessary work
### Alternatives
_No response_ | non_defect | add monitoring and alerting rules problem the relay publishes metrics uses prometheus however no rules are defined to enable relay operators to observe and support alerting solution explore the design and necessary implementation steps to support this and update the relay create sub epic tasklist to capture the necessary work alternatives no response | 0 |
75,195 | 25,582,569,717 | IssuesEvent | 2022-12-01 06:20:27 | martinrotter/rssguard | https://api.github.com/repos/martinrotter/rssguard | closed | [BUG]: Issue with duplicate feeds | Type-Defect Status-Invalid | 
### Brief description of the issue
Experiencing duplicate feeds.
### How to reproduce the bug?
1. add filter.
`function filterMessage() {
if (msg.isAlreadyInDatabase(MessageObject.SameTitle)) {
return MessageObject.Ignore;
}
else {
return MessageObject.Accept;
}
}`
2. Add news feeds from similar sources. Ex. CTV.
### What was the expected result?
Feeds without duplicated titles.
### What actually happened?
Got duplicate feeds.
### Debug log
NA
### Operating system and version
* OS: KDE Neon
* RSS Guard version: 4.2.5
| 1.0 | [BUG]: Issue with duplicate feeds - 
### Brief description of the issue
Experiencing duplicate feeds.
### How to reproduce the bug?
1. add filter.
`function filterMessage() {
if (msg.isAlreadyInDatabase(MessageObject.SameTitle)) {
return MessageObject.Ignore;
}
else {
return MessageObject.Accept;
}
}`
2. Add news feeds from similar sources. Ex. CTV.
### What was the expected result?
Feeds without duplicated titles.
### What actually happened?
Got duplicate feeds.
### Debug log
NA
### Operating system and version
* OS: KDE Neon
* RSS Guard version: 4.2.5
| defect | issue with duplicate feeds brief description of the issue experiencing duplicate feeds how to reproduce the bug add filter function filtermessage if msg isalreadyindatabase messageobject sametitle return messageobject ignore else return messageobject accept add news feeds from similar sources ex ctv what was the expected result feeds without duplicated titles what actually happened got duplicate feeds debug log na operating system and version os kde neon rss guard version | 1 |
13,888 | 5,486,752,750 | IssuesEvent | 2017-03-14 01:12:24 | istio/manager | https://api.github.com/repos/istio/manager | closed | Use an uniform tagging system across all docker istio images (manager, mixer, proxy) | build & test infrastructure | Build system (jenkins/travis) applies:
1. "date+build#" , where date is YYYY-MM-DD-HH:SS ; required on all images
- date is a must giving Bazel build produces incorrect date
- build# - keep in mind that Mixer is on travis, manager + proxy + app (runtime) are on Jenkins
2. short SHA - required on all images
github search repo with short SHA will find the commit directly, no need to go to the build system as an extra step
3. "latest": to be used only by the build system, only if we apply it explicitly and force it with any new push, otherwise we fall in this trap http://container-solutions.com/docker-latest-confusion/
only one image per repo will have this label
4. "alpha-XX.XX"
optional, same label used for all repos, so we can select a matching set of images
can become beta etc.
5. "release-XX.XX" for when time comes :)
Private builds:
1. username + date , where date is YYYY-MM-DD-HH:SS - this will help clean up stale images
For all types of builds, additional manual labels are permitted, for instance "demo", "featureX-working". There is virtually no penalty for using multiple labels on an image.
| 1.0 | Use an uniform tagging system across all docker istio images (manager, mixer, proxy) - Build system (jenkins/travis) applies:
1. "date+build#" , where date is YYYY-MM-DD-HH:SS ; required on all images
- date is a must giving Bazel build produces incorrect date
- build# - keep in mind that Mixer is on travis, manager + proxy + app (runtime) are on Jenkins
2. short SHA - required on all images
github search repo with short SHA will find the commit directly, no need to go to the build system as an extra step
3. "latest": to be used only by the build system, only if we apply it explicitly and force it with any new push, otherwise we fall in this trap http://container-solutions.com/docker-latest-confusion/
only one image per repo will have this label
4. "alpha-XX.XX"
optional, same label used for all repos, so we can select a matching set of images
can become beta etc.
5. "release-XX.XX" for when time comes :)
Private builds:
1. username + date , where date is YYYY-MM-DD-HH:SS - this will help clean up stale images
For all types of builds, additional manual labels are permitted, for instance "demo", "featureX-working". There is virtually no penalty for using multiple labels on an image.
| non_defect | use an uniform tagging system across all docker istio images manager mixer proxy build system jenkins travis applies date build where date is yyyy mm dd hh ss required on all images date is a must giving bazel build produces incorrect date build keep in mind that mixer is on travis manager proxy app runtime are on jenkins short sha required on all images github search repo with short sha will find the commit directly no need to go to the build system as an extra step latest to be used only by the build system only if we apply it explicitly and force it with any new push otherwise we fall in this trap only one image per repo will have this label alpha xx xx optional same label used for all repos so we can select a matching set of images can become beta etc release xx xx for when time comes private builds username date where date is yyyy mm dd hh ss this will help clean up stale images for all types of builds additional manual labels are permitted for instance demo featurex working there is virtually no penalty for using multiple labels on an image | 0 |
18,166 | 3,031,263,666 | IssuesEvent | 2015-08-04 21:49:24 | dart-lang/sdk | https://api.github.com/repos/dart-lang/sdk | closed | library name when creating a new dart file doesn't respect the dart style guide | Area-Analyzer Fixed Priority-Medium Type-Defect | say i have this file in `lib/bar.dart`:
```dart
library bar;
import 'dir/foo.dart';
```
If the import `dir/foo.dart` doesn't exist. I can use alt+enter in webstorm to create the file, and it gives the file the library name: `foo` which I think is very nice, but the style guide says to give `lib/dir/foo.dart` the library name `[packagename].dir.foo`, see:
https://www.dartlang.org/articles/style-guide/
| 1.0 | library name when creating a new dart file doesn't respect the dart style guide - say i have this file in `lib/bar.dart`:
```dart
library bar;
import 'dir/foo.dart';
```
If the import `dir/foo.dart` doesn't exist. I can use alt+enter in webstorm to create the file, and it gives the file the library name: `foo` which I think is very nice, but the style guide says to give `lib/dir/foo.dart` the library name `[packagename].dir.foo`, see:
https://www.dartlang.org/articles/style-guide/
| defect | library name when creating a new dart file doesn t respect the dart style guide say i have this file in lib bar dart dart library bar import dir foo dart if the import dir foo dart doesn t exist i can use alt enter in webstorm to create the file and it gives the file the library name foo which i think is very nice but the style guide says to give lib dir foo dart the library name dir foo see | 1 |
21,271 | 3,479,427,876 | IssuesEvent | 2015-12-28 20:13:33 | innoventsolutions/birt-controls-lib | https://api.github.com/repos/innoventsolutions/birt-controls-lib | closed | How to embed the BIRT in eclip 3.2 | auto-migrated Priority-Medium Type-Defect | ```
Hi we r using the eclips 3.2 and for report we were using the jasper but now we
are planning to use the birt for graphical representation so please do need a
help for me how do i use that report in existing working eclips3.2
```
Original issue reported on code.google.com by `mavinsoo...@gmail.com` on 6 Mar 2012 at 5:18 | 1.0 | How to embed the BIRT in eclip 3.2 - ```
Hi we r using the eclips 3.2 and for report we were using the jasper but now we
are planning to use the birt for graphical representation so please do need a
help for me how do i use that report in existing working eclips3.2
```
Original issue reported on code.google.com by `mavinsoo...@gmail.com` on 6 Mar 2012 at 5:18 | defect | how to embed the birt in eclip hi we r using the eclips and for report we were using the jasper but now we are planning to use the birt for graphical representation so please do need a help for me how do i use that report in existing working original issue reported on code google com by mavinsoo gmail com on mar at | 1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.