Unnamed: 0 int64 3 832k | id float64 2.49B 32.1B | type stringclasses 1 value | created_at stringlengths 19 19 | repo stringlengths 7 112 | repo_url stringlengths 36 141 | action stringclasses 3 values | title stringlengths 2 742 | labels stringlengths 4 431 | body stringlengths 5 239k | index stringclasses 10 values | text_combine stringlengths 96 240k | label stringclasses 2 values | text stringlengths 96 200k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
165,160 | 26,112,036,186 | IssuesEvent | 2022-12-27 21:40:46 | CDCgov/prime-reportstream | https://api.github.com/repos/CDCgov/prime-reportstream | opened | Public Validation Page design finalization | design experience | ## Problem statement
Need a location, page layout, and instructions for the new public validation feature on the RS website.
## What you need to know
Much work has been done to design the validation tool, now we need to determine where it goes and what it will look like to an unauthenticated user (public).
## Acceptance criteria
- [ ] Determine new page location and update site map (notify @lizzieamanning )
- [ ] On page, include instructions for proper usage of the feature and next steps after success
- [ ] Place relevant design details and instructions into # yyyy for engineering work to be completed
## To Do
- [ ] Work with O+O onboarding team to determine verbiage for on-page instructions as it should likely match what is used in their future emails to prospective senders | 1.0 | Public Validation Page design finalization - ## Problem statement
Need a location, page layout, and instructions for the new public validation feature on the RS website.
## What you need to know
Much work has been done to design the validation tool, now we need to determine where it goes and what it will look like to an unauthenticated user (public).
## Acceptance criteria
- [ ] Determine new page location and update site map (notify @lizzieamanning )
- [ ] On page, include instructions for proper usage of the feature and next steps after success
- [ ] Place relevant design details and instructions into # yyyy for engineering work to be completed
## To Do
- [ ] Work with O+O onboarding team to determine verbiage for on-page instructions as it should likely match what is used in their future emails to prospective senders | non_usab | public validation page design finalization problem statement need a location page layout and instructions for the new public validation feature on the rs website what you need to know much work has been done to design the validation tool now we need to determine where it goes and what it will look like to an unauthenticated user public acceptance criteria determine new page location and update site map notify lizzieamanning on page include instructions for proper usage of the feature and next steps after success place relevant design details and instructions into yyyy for engineering work to be completed to do work with o o onboarding team to determine verbiage for on page instructions as it should likely match what is used in their future emails to prospective senders | 0 |
19,724 | 14,491,553,487 | IssuesEvent | 2020-12-11 04:56:09 | kubernetes/kubernetes | https://api.github.com/repos/kubernetes/kubernetes | closed | kubectl completion is too slow | area/usability kind/feature lifecycle/rotten sig/cli | **What happened**:
Kubectl shell completion might be depressingly slow.
Main problem that completion uses constructions like:
```
kubectl get -o template '--template={{ range .items }}{{ .metadata.name }} {{ end }}' configmap
```
to get resource names. But in large installations they can be extremely slow.
**What you expected to happen**:
I expecting that completion will not download tens of megabytes for each `<TAB>` pressing and will work much faster, actually same speed which is need for getting all resources list.
**How to reproduce it (as minimally and precisely as possible)**:
For example if you use single helm tiller per cluster. And install ~200 releases. You can face with the next situation:
```bash
time kubectl get -n=kube-system -o template '--template={{ range .items }}{{ .metadata.name }} {{ end }}' configmap > /dev/null
real 0m14.563s
user 0m9.625s
sys 0m1.257s
```
This is happening because of using template option will download all the resources body and then try parse it, but this is too a lot of information:
```bash
# kubectl get -n=kube-system -o json configmaps > /tmp/configmaps.yaml
# du -hs /tmp/configmaps.yaml
59M /tmp/configmaps.yaml
```
You will face with the same problem if you have many pods:
```bash
# kubectl get pod -n kube-system | wc -l
1759
# kubectl get pod -n kube-system -o yaml > /tmp/pod.yaml
# du -hs /tmp/pod.yaml
7.8M /tmp/pod.yaml
# time kubectl get -n=kube-system -o template '--template={{ range .items }}{{ .metadata.name }} {{ end }}' pod > /dev/null
real 0m4.018s
user 0m4.060s
sys 0m0.173s
```
**Anything else we need to know?**:
Simple solution for this issue is not using `-o template` for getting resource names.
**Environment**:
- Kubernetes version (use `kubectl version`):
```
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.0", GitCommit:"2bd9643cee5b3b3a5ecbd3af49d09018f0773c77", GitTreeState:"clean", BuildDate:"2019-09-18T14:36:53Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.1", GitCommit:"4485c6f18cee9a5d3c3b4e523bd27972b1b53892", GitTreeState:"clean", BuildDate:"2019-07-18T09:09:21Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}
```
- Cloud provider or hardware configuration: basremetal
- OS (e.g: `cat /etc/os-release`):
```
NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="0;36"
HOME_URL="https://www.archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://bugs.archlinux.org/"
LOGO=archlinux
```
- Kernel (e.g. `uname -a`):
```
Linux kvaps-laptop 5.2.9-arch1-1-ARCH #1 SMP PREEMPT Fri Aug 16 11:29:43 UTC 2019 x86_64 GNU/Linux
```
- Install tools: kubeadm
- Network plugin and version (if this is a network-related bug): bridget
- Others:
| True | kubectl completion is too slow - **What happened**:
Kubectl shell completion might be depressingly slow.
Main problem that completion uses constructions like:
```
kubectl get -o template '--template={{ range .items }}{{ .metadata.name }} {{ end }}' configmap
```
to get resource names. But in large installations they can be extremely slow.
**What you expected to happen**:
I expecting that completion will not download tens of megabytes for each `<TAB>` pressing and will work much faster, actually same speed which is need for getting all resources list.
**How to reproduce it (as minimally and precisely as possible)**:
For example if you use single helm tiller per cluster. And install ~200 releases. You can face with the next situation:
```bash
time kubectl get -n=kube-system -o template '--template={{ range .items }}{{ .metadata.name }} {{ end }}' configmap > /dev/null
real 0m14.563s
user 0m9.625s
sys 0m1.257s
```
This is happening because of using template option will download all the resources body and then try parse it, but this is too a lot of information:
```bash
# kubectl get -n=kube-system -o json configmaps > /tmp/configmaps.yaml
# du -hs /tmp/configmaps.yaml
59M /tmp/configmaps.yaml
```
You will face with the same problem if you have many pods:
```bash
# kubectl get pod -n kube-system | wc -l
1759
# kubectl get pod -n kube-system -o yaml > /tmp/pod.yaml
# du -hs /tmp/pod.yaml
7.8M /tmp/pod.yaml
# time kubectl get -n=kube-system -o template '--template={{ range .items }}{{ .metadata.name }} {{ end }}' pod > /dev/null
real 0m4.018s
user 0m4.060s
sys 0m0.173s
```
**Anything else we need to know?**:
Simple solution for this issue is not using `-o template` for getting resource names.
**Environment**:
- Kubernetes version (use `kubectl version`):
```
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.0", GitCommit:"2bd9643cee5b3b3a5ecbd3af49d09018f0773c77", GitTreeState:"clean", BuildDate:"2019-09-18T14:36:53Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.1", GitCommit:"4485c6f18cee9a5d3c3b4e523bd27972b1b53892", GitTreeState:"clean", BuildDate:"2019-07-18T09:09:21Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}
```
- Cloud provider or hardware configuration: basremetal
- OS (e.g: `cat /etc/os-release`):
```
NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="0;36"
HOME_URL="https://www.archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://bugs.archlinux.org/"
LOGO=archlinux
```
- Kernel (e.g. `uname -a`):
```
Linux kvaps-laptop 5.2.9-arch1-1-ARCH #1 SMP PREEMPT Fri Aug 16 11:29:43 UTC 2019 x86_64 GNU/Linux
```
- Install tools: kubeadm
- Network plugin and version (if this is a network-related bug): bridget
- Others:
| usab | kubectl completion is too slow what happened kubectl shell completion might be depressingly slow main problem that completion uses constructions like kubectl get o template template range items metadata name end configmap to get resource names but in large installations they can be extremely slow what you expected to happen i expecting that completion will not download tens of megabytes for each pressing and will work much faster actually same speed which is need for getting all resources list how to reproduce it as minimally and precisely as possible for example if you use single helm tiller per cluster and install releases you can face with the next situation bash time kubectl get n kube system o template template range items metadata name end configmap dev null real user sys this is happening because of using template option will download all the resources body and then try parse it but this is too a lot of information bash kubectl get n kube system o json configmaps tmp configmaps yaml du hs tmp configmaps yaml tmp configmaps yaml you will face with the same problem if you have many pods bash kubectl get pod n kube system wc l kubectl get pod n kube system o yaml tmp pod yaml du hs tmp pod yaml tmp pod yaml time kubectl get n kube system o template template range items metadata name end pod dev null real user sys anything else we need to know simple solution for this issue is not using o template for getting resource names environment kubernetes version use kubectl version client version version info major minor gitversion gitcommit gittreestate clean builddate goversion compiler gc platform linux server version version info major minor gitversion gitcommit gittreestate clean builddate goversion compiler gc platform linux cloud provider or hardware configuration basremetal os e g cat etc os release name arch linux pretty name arch linux id arch build id rolling ansi color home url documentation url support url bug report url logo archlinux kernel e g uname a linux kvaps laptop arch smp preempt fri aug utc gnu linux install tools kubeadm network plugin and version if this is a network related bug bridget others | 1 |
3,867 | 3,591,975,079 | IssuesEvent | 2016-02-01 14:23:19 | Yakindu/statecharts | https://api.github.com/repos/Yakindu/statecharts | opened | Add default to code area of a statechart | Comp-Graphical Editor Usability Issue | The "code area" of a statechart is empty when a new statechart model is created. Therefore, add default input (e.g.)
interface:
// Define statechart events and variables here
... | True | Add default to code area of a statechart - The "code area" of a statechart is empty when a new statechart model is created. Therefore, add default input (e.g.)
interface:
// Define statechart events and variables here
... | usab | add default to code area of a statechart the code area of a statechart is empty when a new statechart model is created therefore add default input e g interface define statechart events and variables here | 1 |
19,869 | 14,672,760,348 | IssuesEvent | 2020-12-30 11:24:15 | WordPress/gutenberg | https://api.github.com/repos/WordPress/gutenberg | closed | Reusable Blocks: Incorrect label appears in block breadcrumb component | Needs Dev [Feature] Reusable Blocks [Type] Bug | When I hover over a reusable block before I click on it shows the label in the top right corner to be "Reusable Block" as expected. When I'm editing the reusable block and hover over a block inside the reusable block the label in the top right corner shows "Reusable Template" as the parent when I would expect "Reusable Block". I'm a site developer working to understand exactly how Gutenberg is put together and works. When using Gutenberg I've started to use the hover labels in the top right to tell me where I am and is incredibly helpful when working with block nesting (inner blocks). If this is intentional and part of how reusable blocks work could you link me to the documentation? If this is only a labeling mistake, would you mind mending it? It would help with clarity for me during this change of editor.
Thanks for your work!
## To Reproduce
1. Create a post using Gutenberg.
2. Insert a reusable block.
3. Hover over the reusable block and observe the label in the top right corner.
4. Click on the reusable block.
5. Click on the "edit" button in the top right.
6. Hover over one of the blocks inside the reusable block and observe the label in the top right corner.
## Expected behavior
I was expecting the labels to both use "Reusable Block".
## Screenshots
## Desktop
- Gutenberg: v4.4.0
- OS: macOS v10.13.5
- Browser: Firefox
- Version: 63.0.3 | True | Reusable Blocks: Incorrect label appears in block breadcrumb component - When I hover over a reusable block before I click on it shows the label in the top right corner to be "Reusable Block" as expected. When I'm editing the reusable block and hover over a block inside the reusable block the label in the top right corner shows "Reusable Template" as the parent when I would expect "Reusable Block". I'm a site developer working to understand exactly how Gutenberg is put together and works. When using Gutenberg I've started to use the hover labels in the top right to tell me where I am and is incredibly helpful when working with block nesting (inner blocks). If this is intentional and part of how reusable blocks work could you link me to the documentation? If this is only a labeling mistake, would you mind mending it? It would help with clarity for me during this change of editor.
Thanks for your work!
## To Reproduce
1. Create a post using Gutenberg.
2. Insert a reusable block.
3. Hover over the reusable block and observe the label in the top right corner.
4. Click on the reusable block.
5. Click on the "edit" button in the top right.
6. Hover over one of the blocks inside the reusable block and observe the label in the top right corner.
## Expected behavior
I was expecting the labels to both use "Reusable Block".
## Screenshots
## Desktop
- Gutenberg: v4.4.0
- OS: macOS v10.13.5
- Browser: Firefox
- Version: 63.0.3 | usab | reusable blocks incorrect label appears in block breadcrumb component when i hover over a reusable block before i click on it shows the label in the top right corner to be reusable block as expected when i m editing the reusable block and hover over a block inside the reusable block the label in the top right corner shows reusable template as the parent when i would expect reusable block i m a site developer working to understand exactly how gutenberg is put together and works when using gutenberg i ve started to use the hover labels in the top right to tell me where i am and is incredibly helpful when working with block nesting inner blocks if this is intentional and part of how reusable blocks work could you link me to the documentation if this is only a labeling mistake would you mind mending it it would help with clarity for me during this change of editor thanks for your work to reproduce create a post using gutenberg insert a reusable block hover over the reusable block and observe the label in the top right corner click on the reusable block click on the edit button in the top right hover over one of the blocks inside the reusable block and observe the label in the top right corner expected behavior i was expecting the labels to both use reusable block screenshots desktop gutenberg os macos browser firefox version | 1 |
14,969 | 18,761,125,469 | IssuesEvent | 2021-11-05 16:34:25 | Roave/BetterReflection | https://api.github.com/repos/Roave/BetterReflection | closed | Implement adapters for `ReflectionAttribute`, `ReflectionEnumPureCase`, `ReflectionEnumBackedCase` and `ReflectionEnumUnitcase` when supported by PHP | enhancement reflection compatibility | Ref: https://bugs.php.net/bug.php?id=81474 | True | Implement adapters for `ReflectionAttribute`, `ReflectionEnumPureCase`, `ReflectionEnumBackedCase` and `ReflectionEnumUnitcase` when supported by PHP - Ref: https://bugs.php.net/bug.php?id=81474 | non_usab | implement adapters for reflectionattribute reflectionenumpurecase reflectionenumbackedcase and reflectionenumunitcase when supported by php ref | 0 |
814,431 | 30,507,540,191 | IssuesEvent | 2023-07-18 18:04:31 | GoogleCloudPlatform/professional-services-data-validator | https://api.github.com/repos/GoogleCloudPlatform/professional-services-data-validator | closed | schema validation: BigQuery BIGNUMERIC | priority: p1 | BigQuery BIGNUMERIC columns are being read by schema validation as `decimal(38, 9)`. Possibly this is because BIGNUMERIC precision and scale exceeds that supported by Ibis but I thought it should be logged anyway.
Example BigQuery column:
```
, col_dec_38 BIGNUMERIC(38)
```
Shows in DVT schema validation as `decimal(38, 9)`.
@nehanene15 , do you think this would be resolved by the Ibis upgrade?
If we change the input type then the following integrations tests will need to be updated (search for "issue-839" in the files):
- test_hive.py
- test_oracle.py
- test_sql_server.py
- test_teradata.py | 1.0 | schema validation: BigQuery BIGNUMERIC - BigQuery BIGNUMERIC columns are being read by schema validation as `decimal(38, 9)`. Possibly this is because BIGNUMERIC precision and scale exceeds that supported by Ibis but I thought it should be logged anyway.
Example BigQuery column:
```
, col_dec_38 BIGNUMERIC(38)
```
Shows in DVT schema validation as `decimal(38, 9)`.
@nehanene15 , do you think this would be resolved by the Ibis upgrade?
If we change the input type then the following integrations tests will need to be updated (search for "issue-839" in the files):
- test_hive.py
- test_oracle.py
- test_sql_server.py
- test_teradata.py | non_usab | schema validation bigquery bignumeric bigquery bignumeric columns are being read by schema validation as decimal possibly this is because bignumeric precision and scale exceeds that supported by ibis but i thought it should be logged anyway example bigquery column col dec bignumeric shows in dvt schema validation as decimal do you think this would be resolved by the ibis upgrade if we change the input type then the following integrations tests will need to be updated search for issue in the files test hive py test oracle py test sql server py test teradata py | 0 |
9,396 | 6,277,988,319 | IssuesEvent | 2017-07-18 13:31:18 | giantswarm/cli | https://api.github.com/repos/giantswarm/cli | closed | swarm open should open an app in the browser | 1 - status/later area/goldenpath area/usability kind/feature | As recommended by _a user_ in our alpha channel it would be handy to have a `swarm open` command that opens up the url of the app in the browser. Similar to `heroku open`.
See: https://devcenter.heroku.com/articles/getting-started-with-rails3#visit-your-application
Original Author: @teemow
Created at 10-11-2014 16:20:21
Gitlab: [giantswarm/cli!106](https://git.giantswarm.io/giantswarm/cli/issues/106)
<!---
@huboard:{"order":145.5,"milestone_order":55,"custom_state":""}
-->
| True | swarm open should open an app in the browser - As recommended by _a user_ in our alpha channel it would be handy to have a `swarm open` command that opens up the url of the app in the browser. Similar to `heroku open`.
See: https://devcenter.heroku.com/articles/getting-started-with-rails3#visit-your-application
Original Author: @teemow
Created at 10-11-2014 16:20:21
Gitlab: [giantswarm/cli!106](https://git.giantswarm.io/giantswarm/cli/issues/106)
<!---
@huboard:{"order":145.5,"milestone_order":55,"custom_state":""}
-->
| usab | swarm open should open an app in the browser as recommended by a user in our alpha channel it would be handy to have a swarm open command that opens up the url of the app in the browser similar to heroku open see original author teemow created at gitlab huboard order milestone order custom state | 1 |
27,803 | 30,440,710,113 | IssuesEvent | 2023-07-15 03:05:28 | mekanism/Mekanism | https://api.github.com/repos/mekanism/Mekanism | closed | Thermodynamic Conductor will keep getting heat from fusion reactor even when disabled | bug confirmed Fixed in dev Usability 1.19 | ### Issue description
I want to use a fusion reactor to start another fusion reactor, so I am using thermodynamic conductor to connect them.
I want the conductor can be detach from the reactor, so it will be more efficient.
The issue is when I use redstone to disable them, or use the configure to set the side to None, it will keep getting heat from the reactor really fast (about 10Mk/t), faster than when it's connected.
### Steps to reproduce
1. place a fusion reactor
2. give it enough fuel, and start it
3. connect it to a thermodynamic conductor (any kind)
4. right click the conductor use configure, allow redstone to control it.
5. give it a redstone signal
6. You will see the reactor's heat is jumping down, and the conductor's heat will be rising up.
### Minecraft version
1.19.2 (Latest)
### Forge version
43.2.6
### Mekanism version
10.3.8 (Latest)
### Other relevant versions
_No response_
### If a (crash)log is relevant for this issue, link it here: (It's almost always relevant)
_No response_ | True | Thermodynamic Conductor will keep getting heat from fusion reactor even when disabled - ### Issue description
I want to use a fusion reactor to start another fusion reactor, so I am using thermodynamic conductor to connect them.
I want the conductor can be detach from the reactor, so it will be more efficient.
The issue is when I use redstone to disable them, or use the configure to set the side to None, it will keep getting heat from the reactor really fast (about 10Mk/t), faster than when it's connected.
### Steps to reproduce
1. place a fusion reactor
2. give it enough fuel, and start it
3. connect it to a thermodynamic conductor (any kind)
4. right click the conductor use configure, allow redstone to control it.
5. give it a redstone signal
6. You will see the reactor's heat is jumping down, and the conductor's heat will be rising up.
### Minecraft version
1.19.2 (Latest)
### Forge version
43.2.6
### Mekanism version
10.3.8 (Latest)
### Other relevant versions
_No response_
### If a (crash)log is relevant for this issue, link it here: (It's almost always relevant)
_No response_ | usab | thermodynamic conductor will keep getting heat from fusion reactor even when disabled issue description i want to use a fusion reactor to start another fusion reactor so i am using thermodynamic conductor to connect them i want the conductor can be detach from the reactor so it will be more efficient the issue is when i use redstone to disable them or use the configure to set the side to none it will keep getting heat from the reactor really fast about t faster than when it s connected steps to reproduce place a fusion reactor give it enough fuel and start it connect it to a thermodynamic conductor any kind right click the conductor use configure allow redstone to control it give it a redstone signal you will see the reactor s heat is jumping down and the conductor s heat will be rising up minecraft version latest forge version mekanism version latest other relevant versions no response if a crash log is relevant for this issue link it here it s almost always relevant no response | 1 |
1,632 | 2,563,710,596 | IssuesEvent | 2015-02-06 15:06:52 | hydroshare/hydroshare | https://api.github.com/repos/hydroshare/hydroshare | closed | Wrong file gets deleted from a resource | bug Fix pushed to github ready for testing | When a resource has multiple files listed and one tries to delete any file other than the first one from the list, it deletes the first one. | 1.0 | Wrong file gets deleted from a resource - When a resource has multiple files listed and one tries to delete any file other than the first one from the list, it deletes the first one. | non_usab | wrong file gets deleted from a resource when a resource has multiple files listed and one tries to delete any file other than the first one from the list it deletes the first one | 0 |
10,371 | 6,689,312,033 | IssuesEvent | 2017-10-09 00:43:31 | uqbar-project/wollok | https://api.github.com/repos/uqbar-project/wollok | closed | REPL continues to run after program has been modified | component: repl in progress usability | If you have a program running in the REPL and you modify it, the REPL continues running the old program.
I would like to give a try to update the program in execution, maybe it is easier than it appears at first sight. But still, if that is not possible, we should take some action when the running program is modified. Otherwise, programmers tend to get confused because they can't see any behavior change after program modifications.
Two simple actions, we should either
a. Stop de REPL, or
b. If we allow to continue running, at least add some kind of visual clue about running an obsolete program: change a color or icon, display a warning, etc. | True | REPL continues to run after program has been modified - If you have a program running in the REPL and you modify it, the REPL continues running the old program.
I would like to give a try to update the program in execution, maybe it is easier than it appears at first sight. But still, if that is not possible, we should take some action when the running program is modified. Otherwise, programmers tend to get confused because they can't see any behavior change after program modifications.
Two simple actions, we should either
a. Stop de REPL, or
b. If we allow to continue running, at least add some kind of visual clue about running an obsolete program: change a color or icon, display a warning, etc. | usab | repl continues to run after program has been modified if you have a program running in the repl and you modify it the repl continues running the old program i would like to give a try to update the program in execution maybe it is easier than it appears at first sight but still if that is not possible we should take some action when the running program is modified otherwise programmers tend to get confused because they can t see any behavior change after program modifications two simple actions we should either a stop de repl or b if we allow to continue running at least add some kind of visual clue about running an obsolete program change a color or icon display a warning etc | 1 |
8,678 | 5,914,731,366 | IssuesEvent | 2017-05-22 04:39:51 | broesamle/clip_8 | https://api.github.com/repos/broesamle/clip_8 | closed | larger location indicators for error feedback | high-prio usability | The square around critical locations should always appear in an appropriate size.
Currently it is fixed pixel counts but it could be derived in proportion to of the `viewBox` width. | True | larger location indicators for error feedback - The square around critical locations should always appear in an appropriate size.
Currently it is fixed pixel counts but it could be derived in proportion to of the `viewBox` width. | usab | larger location indicators for error feedback the square around critical locations should always appear in an appropriate size currently it is fixed pixel counts but it could be derived in proportion to of the viewbox width | 1 |
24,254 | 23,540,437,691 | IssuesEvent | 2022-08-20 09:55:35 | the-tale/the-tale | https://api.github.com/repos/the-tale/the-tale | closed | На странице рынка не грузится картинка печеньки | type_bug cont_usability est_simple comp_market good first issue | Скорее всего неправильный (старый) путь к статике прописан | True | На странице рынка не грузится картинка печеньки - Скорее всего неправильный (старый) путь к статике прописан | usab | на странице рынка не грузится картинка печеньки скорее всего неправильный старый путь к статике прописан | 1 |
11,342 | 16,995,798,914 | IssuesEvent | 2021-07-01 06:13:19 | renovatebot/renovate | https://api.github.com/repos/renovatebot/renovate | closed | These updates encountered an error and will be retried. Click a checkbox below to force a retry now. | priority-5-triage status:requirements type:bug | <!--
PLEASE DO NOT REPORT ANY SECURITY CONCERNS THIS WAY
Email renovate-disclosure@whitesourcesoftware.com instead.
-->
**How are you running Renovate?**
- [ ] WhiteSource Renovate hosted app on github.com
- [x] Self hosted
If using the hosted app, please skip to the next section.
Otherwise, if self-hosted, please complete the following:
Please select which platform you are using:
- [ ] Azure DevOps (dev.azure.com)
- [ ] Azure DevOps Server
- [ ] Bitbucket Cloud (bitbucket.org)
- [ ] Bitbucket Server
- [ ] Gitea
- [ ] github.com
- [ ] GitHub Enterprise Server
- [ ] gitlab.com
- [x] GitLab self-hosted
Renovate version: 25.49
**Describe the bug**
Dashboard says: `These updates encountered an error and will be retried. Click a checkbox below to force a retry now.`
This issue contains a list of Renovate updates and their statuses.
## Awaiting Schedule
These updates are awaiting their schedule. Click on a checkbox to get an update now.
- [ ] <!-- unschedule-branch=renovate/nuxtjs-tailwindcss-3.x -->chore(deps): update dependency @nuxtjs/tailwindcss to v3.4.3
- [ ] <!-- unschedule-branch=renovate/husky-4.x -->chore(deps): update dependency husky to v4.3.8
- [ ] <!-- unschedule-branch=renovate/lint-staged-10.x -->chore(deps): update dependency lint-staged to v10.5.4
- [ ] <!-- unschedule-branch=renovate/nuxtjs-pwa-3.x -->fix(deps): update dependency @nuxtjs/pwa to v3.3.5
- [ ] <!-- unschedule-branch=renovate/babel-monorepo -->chore(deps): update dependency @babel/runtime-corejs3 to v7.14.7
- [ ] <!-- unschedule-branch=renovate/eslint-7.x -->chore(deps): update dependency eslint to v7.29.0
- [ ] <!-- unschedule-branch=renovate/eslint-config-prettier-7.x -->chore(deps): update dependency eslint-config-prettier to v7.2.0
- [ ] <!-- unschedule-branch=renovate/eslint-plugin-prettier-3.x -->chore(deps): update dependency eslint-plugin-prettier to v3.4.0
- [ ] <!-- unschedule-branch=renovate/fs-extra-9.x -->chore(deps): update dependency fs-extra to v9.1.0
- [ ] <!-- unschedule-branch=renovate/prettier-2.x -->chore(deps): update dependency prettier to v2.3.2
- [ ] <!-- unschedule-branch=renovate/sass-1.x -->chore(deps): update dependency sass to v1.35.1
- [ ] <!-- unschedule-branch=renovate/sass-loader-10.x -->chore(deps): update dependency sass-loader to v10.2.0
- [ ] <!-- unschedule-branch=renovate/stylelint-13.x -->chore(deps): update dependency stylelint to v13.13.1
- [ ] <!-- unschedule-branch=renovate/stylelint-scss-3.x -->chore(deps): update dependency stylelint-scss to v3.19.0
- [ ] <!-- unschedule-branch=renovate/nuxtjs-monorepo -->chore(deps): update nuxtjs monorepo to v2.15.7 (`@nuxt/types`, `nuxt`)
- [ ] <!-- unschedule-branch=renovate/vue-monorepo -->chore(deps): update vue monorepo (`@vue/test-utils`, `vue-jest`)
- [ ] <!-- unschedule-branch=renovate/nuxt-content-theme-docs-0.x -->fix(deps): update dependency @nuxt/content-theme-docs to v0.10.2
- [ ] <!-- unschedule-branch=renovate/nuxtjs-axios-5.x -->fix(deps): update dependency @nuxtjs/axios to v5.13.6
- [ ] <!-- unschedule-branch=renovate/core-js-3.x -->fix(deps): update dependency core-js to v3.15.2
- [ ] <!-- unschedule-branch=renovate/d3-6.x -->fix(deps): update dependency d3 to v6.7.0
- [ ] <!-- unschedule-branch=renovate/date-fns-2.x -->fix(deps): update dependency date-fns to v2.22.1
- [ ] <!-- unschedule-branch=renovate/vue2-leaflet-2.x -->fix(deps): update dependency vue2-leaflet to v2.7.1
- [ ] <!-- unschedule-branch=renovate/major-commitlint-monorepo -->chore(deps): update commitlint monorepo to v12 (major) (`@commitlint/cli`, `@commitlint/config-conventional`)
- [ ] <!-- unschedule-branch=renovate/nuxtjs-eslint-config-6.x -->chore(deps): update dependency @nuxtjs/eslint-config to v6
- [ ] <!-- unschedule-branch=renovate/eslint-config-prettier-8.x -->chore(deps): update dependency eslint-config-prettier to v8
- [ ] <!-- unschedule-branch=renovate/fs-extra-10.x -->chore(deps): update dependency fs-extra to v10
- [ ] <!-- unschedule-branch=renovate/lint-staged-11.x -->chore(deps): update dependency lint-staged to v11
- [ ] <!-- unschedule-branch=renovate/sass-loader-12.x -->chore(deps): update dependency sass-loader to v12
- [ ] <!-- unschedule-branch=renovate/stylelint-config-standard-22.x -->chore(deps): update dependency stylelint-config-standard to v22
- [ ] <!-- unschedule-branch=renovate/major-jest-monorepo -->chore(deps): update jest monorepo to v27 (major) (`babel-jest`, `jest`)
- [ ] <!-- unschedule-branch=renovate/nuxtjs-sentry-5.x -->fix(deps): update dependency @nuxtjs/sentry to v5
- [ ] <!-- unschedule-branch=renovate/d3-7.x -->fix(deps): update dependency d3 to v7
- [ ] <!-- unschedule-branch=renovate/vue-matomo-4.x -->fix(deps): update dependency vue-matomo to v4
## Errored
These updates encountered an error and will be retried. Click a checkbox below to force a retry now.
- [ ] <!-- retry-branch=renovate/pin-dependencies -->chore(deps): pin dependencies (`@babel/runtime-corejs3`, `@commitlint/cli`, `@commitlint/config-conventional`, `@nuxt/content-theme-docs`, `@nuxt/types`, `@nuxtjs/axios`, `@nuxtjs/eslint-config`, `@nuxtjs/eslint-module`, `@nuxtjs/pwa`, `@nuxtjs/sentry`, `@nuxtjs/stylelint-module`, `@nuxtjs/tailwindcss`, `@vue/test-utils`, `babel-eslint`, `babel-jest`, `cloudflare`, `core-js`, `d3`, `date-fns`, `eslint`, `eslint-config-prettier`, `eslint-plugin-nuxt`, `eslint-plugin-prettier`, `fibers`, `fs-extra`, `hashicorp/terraform`, `hcloud`, `husky`, `jest`, `leaflet`, `lint-staged`, `nuxt`, `postcss-focus-within`, `prettier`, `sass`, `sass-loader`, `stylelint`, `stylelint-config-prettier`, `stylelint-config-standard`, `stylelint-order`, `stylelint-scss`, `topojson`, `vue-jest`, `vue-matomo`, `vue2-leaflet`, `workerize-loader`)
However, retry does not work.
MR creation does not work for the project for `company/map project`, it works however for other projects such as `company/wpc `or `company/nuxt`.
Runner logs do not print any error.
**Relevant debug logs**
<!--
Try not to raise a bug report unless you've looked at the logs first.
If you're running self-hosted, run with `LOG_LEVEL=debug` in your environment variables and search for whatever dependency/branch/PR that is causing the problem. If you are using the Renovate App, log into https://app.renovatebot.com/dashboard and locate the correct job log for when the problem occurred (e.g. when the PR was created).
Paste the *relevant* logs here, not the entire thing and not just a link to the dashboard (others do not have permissions to view them).
-->
<details><summary>Click me to see logs</summary>
```
Running with gitlab-runner 14.0.1 (c1edb478)
on infra1 renovate maeesMZL
Resolving secrets
00:00
Preparing the "docker" executor
Using Docker executor with image renovate/renovate:25.49@sha256:56def454410e3a44d20081244401330e58c1ce417dff3237f34dd3a20d4a218b ...
Starting service docker:20.10.7-dind ...
Pulling docker image docker:20.10.7-dind@sha256:4e1e22f471afc7ed5e024127396f56db392c1b6fc81fc0c05c0e072fb51909fe ...
Using docker image sha256:b0a9f712488ae3b3ddf576e14e56186f709e4735fe042b01f76521878929d535 for docker:20.10.7-dind@sha256:4e1e22f471afc7ed5e024127396f56db392c1b6fc81fc0c05c0e072fb51909fe with digest docker@sha256:4e1e22f471afc7ed5e024127396f56db392c1b6fc81fc0c05c0e072fb51909fe ...
Waiting for services to be up and running...
Pulling docker image renovate/renovate:25.49@sha256:56def454410e3a44d20081244401330e58c1ce417dff3237f34dd3a20d4a218b ...
Using docker image sha256:bdaf1372959bb42cc79628cf092ee3600e15387562120c140cb7508807e84e58 for renovate/renovate:25.49@sha256:56def454410e3a44d20081244401330e58c1ce417dff3237f34dd3a20d4a218b with digest renovate/renovate@sha256:56def454410e3a44d20081244401330e58c1ce417dff3237f34dd3a20d4a218b ...
Preparing environment
00:01
Running on runner-maeesmzl-project-199-concurrent-0 via infra1.company.com...
Getting source from Git repository
Fetching changes with git depth set to 50...
Reinitialized existing Git repository in /builds/company/renovate-runner/.git/
Checking out af70d19d as main...
Removing node_modules/
Removing renovate-log.ndjson
Removing renovate/
Skipping Git submodules setup
Restoring cache
Checking cache for main-renovate...
No URL provided, cache will not be downloaded from shared cache server. Instead a local version of cache will be extracted.
Successfully extracted cache
Executing "step_script" stage of the job script
Using docker image sha256:bdaf1372959bb42cc79628cf092ee3600e15387562120c140cb7508807e84e58 for renovate/renovate:25.49@sha256:56def454410e3a44d20081244401330e58c1ce417dff3237f34dd3a20d4a218b with digest renovate/renovate@sha256:56def454410e3a44d20081244401330e58c1ce417dff3237f34dd3a20d4a218b ...
$ renovate $RENOVATE_EXTRA_FLAGS
INFO: Repository started (repository=company/company-nuxt)
"renovateVersion": "25.49.0"
INFO: Dependency extraction complete (repository=company/company-nuxt)
"baseBranch": "master",
"stats": {
"managers": {"npm": {"fileCount": 1, "depCount": 44}},
"total": {"fileCount": 1, "depCount": 44}
}
INFO: Repository finished (repository=company/company-nuxt)
"durationMs": 14115
INFO: Repository started (repository=company/wpc)
"renovateVersion": "25.49.0"
INFO: Dependency extraction complete (repository=company/wpc)
"baseBranch": "master",
"stats": {
"managers": {"npm": {"fileCount": 1, "depCount": 24}},
"total": {"fileCount": 1, "depCount": 24}
}
INFO: Repository finished (repository=company/wpc)
"durationMs": 3869
INFO: Repository started (repository=company/map)
"renovateVersion": "25.49.0"
INFO: Dependency extraction complete (repository=company/map)
"baseBranch": "master",
"stats": {
"managers": {
"npm": {"fileCount": 2, "depCount": 45},
"terraform": {"fileCount": 5, "depCount": 13}
},
"total": {"fileCount": 7, "depCount": 58}
}
INFO: Repository finished (repository=company/map)
"durationMs": 50599
Saving cache for successful job
Creating cache main-renovate...
/builds/company/renovate-runner/renovate: found 68462 matching files and directories
No URL provided, cache will be not uploaded to shared cache server. Cache will be stored only locally.
Created cache
Uploading artifacts for successful job
00:01
Uploading artifacts...
renovate-log.ndjson: found 1 matching files and directories
Uploading artifacts as "archive" to coordinator... ok id=89639 responseStatus=201 Created token=xY6K-gCg
Cleaning up file based variables
00:01
Job succeeded
```
</details>
**Have you created a minimal reproduction repository?**
Please read the [minimal reproductions documentation](https://github.com/renovatebot/renovate/blob/main/docs/development/minimal-reproductions.md) to learn how to make a good minimal reproduction repository.
- [ ] I have provided a minimal reproduction repository
- [ ] I don't have time for that, but it happens in a public repository I have linked to
- [x] I don't have time for that, and cannot share my private repository
- [ ] The nature of this bug means it's impossible to reproduce publicly
**Additional context**
<!-- Add any other context about the problem here, including your own debugging or ideas on what went wrong. -->
My configs:
```
// renovate-config-base
{
"extends": [
"config:base",
":timezone(Europe/Vienna)",
":label(Renovate)",
":assignee(gitlab)"
],
"packageRules": [
{
"matchUpdateTypes": ["major"],
"addLabels": ["SemVer::major"]
},
{
"matchUpdateTypes": ["minor"],
"addLabels": ["SemVer::minor"]
},
{
"matchUpdateTypes": ["patch"],
"addLabels": ["SemVer::patch"]
}
]
}
```
```
// renovate-config-javascript
{
"extends": [
"local>company/renovate-config-base",
":pinAllExceptPeerDependencies",
":onlyNpm"
],
"packageRules": [
{
"matchDatasources": ["npm"],
"stabilityDays": 3
},
{
"matchDepTypes": ["dependencies"],
"addLabels": ["Dependency::runtime"]
},
{
"matchDepTypes": ["devDependencies"],
"addLabels": ["Dependency::development"]
},
{
"matchDepTypes": ["peerDependencies"],
"addLabels": ["Dependency::peer"]
},
{
"matchDepTypes": ["optionalDependencies"],
"addLabels": ["Dependency::optional"]
},
{
"matchDepTypes": ["bundledDependencies"],
"addLabels": ["Dependency::bundled"]
}
]
}
```
```
// company/map/renovate.json
{
"extends": [
"local>company/renovate-config-javascript",
":disableRateLimiting",
"schedule:weekly",
":dependencyDashboard"
],
"packageRules": [
{
"matchPackageNames": ["@nuxtjs/tailwindcss"],
"allowedVersions": "<4"
},
{
"matchPackageNames": ["husky"],
"allowedVersions": "<5"
},
{
"matchPackageNames": ["core-js"],
"allowedVersions": "<4"
},
{
"matchPackageNames": ["postcss-focus-within"],
"allowedVersions": "<5"
}
],
"dependencyDashboardAutoclose": true
}
```
```
// company/map/package.json
{
"name": "map",
"version": "1.0.0",
"private": true,
"scripts": {
"dev": "nuxt",
"build": "nuxt build",
"start": "nuxt start",
"generate": "nuxt generate",
"lint:js": "eslint --ext .js,.vue --ignore-path .gitignore .",
"lint:style": "stylelint **/*.{vue,css} --ignore-path .gitignore",
"lint": "yarn lint:js && yarn lint:style",
"lint:fix": "yarn lint:js --fix && yarn lint:style --fix",
"test": "jest"
},
"lint-staged": {
"*.{js,vue}": "eslint",
"*.{css,vue}": "stylelint"
},
"husky": {
"hooks": {
"commit-msg": "commitlint -E HUSKY_GIT_PARAMS",
"pre-commit": "lint-staged"
}
},
"dependencies": {
"@nuxtjs/axios": "^5.12.4",
"@nuxtjs/pwa": "^3.3.3",
"@nuxtjs/sentry": "^4.5.0",
"core-js": "3",
"d3": "^6.3.1",
"date-fns": "^2.16.1",
"leaflet": "^1.7.1",
"nuxt": "^2.14.12",
"topojson": "^3.0.2",
"vue-matomo": "^3.14.0-0",
"vue2-leaflet": "^2.6.0"
},
"devDependencies": {
"@babel/runtime-corejs3": "^7.12.5",
"@commitlint/cli": "^11.0.0",
"@commitlint/config-conventional": "^11.0.0",
"@nuxt/types": "~2.14.0",
"@nuxtjs/eslint-config": "^5.0.0",
"@nuxtjs/eslint-module": "^3.0.2",
"@nuxtjs/stylelint-module": "^4.0.0",
"@nuxtjs/tailwindcss": "^3.4.1",
"@vue/test-utils": "^1.1.2",
"babel-core": "7.0.0-bridge.0",
"babel-eslint": "^10.1.0",
"babel-jest": "^26.6.3",
"eslint": "^7.16.0",
"eslint-config-prettier": "^7.1.0",
"eslint-plugin-nuxt": "^2.0.0",
"eslint-plugin-prettier": "^3.3.0",
"fibers": "^5.0.0",
"fs-extra": "^9.0.1",
"husky": "^4.3.6",
"jest": "^26.6.3",
"lint-staged": "^10.5.3",
"prettier": "^2.2.1",
"sass": "^1.30.0",
"sass-loader": "^10.1.0",
"stylelint": "^13.8.0",
"stylelint-config-prettier": "^8.0.2",
"stylelint-config-standard": "^20.0.0",
"stylelint-order": "^4.1.0",
"stylelint-scss": "^3.18.0",
"vue-jest": "^4.0.0-rc.1",
"workerize-loader": "^1.3.0"
},
"browserslist": [
"last 2 versions",
"> 0.15%",
"not IE 9",
"chrome >70",
"android >4",
"ios_saf >9"
],
"resolutions": {
"postcss-focus-within": "^4.0.0"
}
}
```
...
| 1.0 | These updates encountered an error and will be retried. Click a checkbox below to force a retry now. - <!--
PLEASE DO NOT REPORT ANY SECURITY CONCERNS THIS WAY
Email renovate-disclosure@whitesourcesoftware.com instead.
-->
**How are you running Renovate?**
- [ ] WhiteSource Renovate hosted app on github.com
- [x] Self hosted
If using the hosted app, please skip to the next section.
Otherwise, if self-hosted, please complete the following:
Please select which platform you are using:
- [ ] Azure DevOps (dev.azure.com)
- [ ] Azure DevOps Server
- [ ] Bitbucket Cloud (bitbucket.org)
- [ ] Bitbucket Server
- [ ] Gitea
- [ ] github.com
- [ ] GitHub Enterprise Server
- [ ] gitlab.com
- [x] GitLab self-hosted
Renovate version: 25.49
**Describe the bug**
Dashboard says: `These updates encountered an error and will be retried. Click a checkbox below to force a retry now.`
This issue contains a list of Renovate updates and their statuses.
## Awaiting Schedule
These updates are awaiting their schedule. Click on a checkbox to get an update now.
- [ ] <!-- unschedule-branch=renovate/nuxtjs-tailwindcss-3.x -->chore(deps): update dependency @nuxtjs/tailwindcss to v3.4.3
- [ ] <!-- unschedule-branch=renovate/husky-4.x -->chore(deps): update dependency husky to v4.3.8
- [ ] <!-- unschedule-branch=renovate/lint-staged-10.x -->chore(deps): update dependency lint-staged to v10.5.4
- [ ] <!-- unschedule-branch=renovate/nuxtjs-pwa-3.x -->fix(deps): update dependency @nuxtjs/pwa to v3.3.5
- [ ] <!-- unschedule-branch=renovate/babel-monorepo -->chore(deps): update dependency @babel/runtime-corejs3 to v7.14.7
- [ ] <!-- unschedule-branch=renovate/eslint-7.x -->chore(deps): update dependency eslint to v7.29.0
- [ ] <!-- unschedule-branch=renovate/eslint-config-prettier-7.x -->chore(deps): update dependency eslint-config-prettier to v7.2.0
- [ ] <!-- unschedule-branch=renovate/eslint-plugin-prettier-3.x -->chore(deps): update dependency eslint-plugin-prettier to v3.4.0
- [ ] <!-- unschedule-branch=renovate/fs-extra-9.x -->chore(deps): update dependency fs-extra to v9.1.0
- [ ] <!-- unschedule-branch=renovate/prettier-2.x -->chore(deps): update dependency prettier to v2.3.2
- [ ] <!-- unschedule-branch=renovate/sass-1.x -->chore(deps): update dependency sass to v1.35.1
- [ ] <!-- unschedule-branch=renovate/sass-loader-10.x -->chore(deps): update dependency sass-loader to v10.2.0
- [ ] <!-- unschedule-branch=renovate/stylelint-13.x -->chore(deps): update dependency stylelint to v13.13.1
- [ ] <!-- unschedule-branch=renovate/stylelint-scss-3.x -->chore(deps): update dependency stylelint-scss to v3.19.0
- [ ] <!-- unschedule-branch=renovate/nuxtjs-monorepo -->chore(deps): update nuxtjs monorepo to v2.15.7 (`@nuxt/types`, `nuxt`)
- [ ] <!-- unschedule-branch=renovate/vue-monorepo -->chore(deps): update vue monorepo (`@vue/test-utils`, `vue-jest`)
- [ ] <!-- unschedule-branch=renovate/nuxt-content-theme-docs-0.x -->fix(deps): update dependency @nuxt/content-theme-docs to v0.10.2
- [ ] <!-- unschedule-branch=renovate/nuxtjs-axios-5.x -->fix(deps): update dependency @nuxtjs/axios to v5.13.6
- [ ] <!-- unschedule-branch=renovate/core-js-3.x -->fix(deps): update dependency core-js to v3.15.2
- [ ] <!-- unschedule-branch=renovate/d3-6.x -->fix(deps): update dependency d3 to v6.7.0
- [ ] <!-- unschedule-branch=renovate/date-fns-2.x -->fix(deps): update dependency date-fns to v2.22.1
- [ ] <!-- unschedule-branch=renovate/vue2-leaflet-2.x -->fix(deps): update dependency vue2-leaflet to v2.7.1
- [ ] <!-- unschedule-branch=renovate/major-commitlint-monorepo -->chore(deps): update commitlint monorepo to v12 (major) (`@commitlint/cli`, `@commitlint/config-conventional`)
- [ ] <!-- unschedule-branch=renovate/nuxtjs-eslint-config-6.x -->chore(deps): update dependency @nuxtjs/eslint-config to v6
- [ ] <!-- unschedule-branch=renovate/eslint-config-prettier-8.x -->chore(deps): update dependency eslint-config-prettier to v8
- [ ] <!-- unschedule-branch=renovate/fs-extra-10.x -->chore(deps): update dependency fs-extra to v10
- [ ] <!-- unschedule-branch=renovate/lint-staged-11.x -->chore(deps): update dependency lint-staged to v11
- [ ] <!-- unschedule-branch=renovate/sass-loader-12.x -->chore(deps): update dependency sass-loader to v12
- [ ] <!-- unschedule-branch=renovate/stylelint-config-standard-22.x -->chore(deps): update dependency stylelint-config-standard to v22
- [ ] <!-- unschedule-branch=renovate/major-jest-monorepo -->chore(deps): update jest monorepo to v27 (major) (`babel-jest`, `jest`)
- [ ] <!-- unschedule-branch=renovate/nuxtjs-sentry-5.x -->fix(deps): update dependency @nuxtjs/sentry to v5
- [ ] <!-- unschedule-branch=renovate/d3-7.x -->fix(deps): update dependency d3 to v7
- [ ] <!-- unschedule-branch=renovate/vue-matomo-4.x -->fix(deps): update dependency vue-matomo to v4
## Errored
These updates encountered an error and will be retried. Click a checkbox below to force a retry now.
- [ ] <!-- retry-branch=renovate/pin-dependencies -->chore(deps): pin dependencies (`@babel/runtime-corejs3`, `@commitlint/cli`, `@commitlint/config-conventional`, `@nuxt/content-theme-docs`, `@nuxt/types`, `@nuxtjs/axios`, `@nuxtjs/eslint-config`, `@nuxtjs/eslint-module`, `@nuxtjs/pwa`, `@nuxtjs/sentry`, `@nuxtjs/stylelint-module`, `@nuxtjs/tailwindcss`, `@vue/test-utils`, `babel-eslint`, `babel-jest`, `cloudflare`, `core-js`, `d3`, `date-fns`, `eslint`, `eslint-config-prettier`, `eslint-plugin-nuxt`, `eslint-plugin-prettier`, `fibers`, `fs-extra`, `hashicorp/terraform`, `hcloud`, `husky`, `jest`, `leaflet`, `lint-staged`, `nuxt`, `postcss-focus-within`, `prettier`, `sass`, `sass-loader`, `stylelint`, `stylelint-config-prettier`, `stylelint-config-standard`, `stylelint-order`, `stylelint-scss`, `topojson`, `vue-jest`, `vue-matomo`, `vue2-leaflet`, `workerize-loader`)
However, retry does not work.
MR creation does not work for the project for `company/map project`, it works however for other projects such as `company/wpc `or `company/nuxt`.
Runner logs do not print any error.
**Relevant debug logs**
<!--
Try not to raise a bug report unless you've looked at the logs first.
If you're running self-hosted, run with `LOG_LEVEL=debug` in your environment variables and search for whatever dependency/branch/PR that is causing the problem. If you are using the Renovate App, log into https://app.renovatebot.com/dashboard and locate the correct job log for when the problem occurred (e.g. when the PR was created).
Paste the *relevant* logs here, not the entire thing and not just a link to the dashboard (others do not have permissions to view them).
-->
<details><summary>Click me to see logs</summary>
```
Running with gitlab-runner 14.0.1 (c1edb478)
on infra1 renovate maeesMZL
Resolving secrets
00:00
Preparing the "docker" executor
Using Docker executor with image renovate/renovate:25.49@sha256:56def454410e3a44d20081244401330e58c1ce417dff3237f34dd3a20d4a218b ...
Starting service docker:20.10.7-dind ...
Pulling docker image docker:20.10.7-dind@sha256:4e1e22f471afc7ed5e024127396f56db392c1b6fc81fc0c05c0e072fb51909fe ...
Using docker image sha256:b0a9f712488ae3b3ddf576e14e56186f709e4735fe042b01f76521878929d535 for docker:20.10.7-dind@sha256:4e1e22f471afc7ed5e024127396f56db392c1b6fc81fc0c05c0e072fb51909fe with digest docker@sha256:4e1e22f471afc7ed5e024127396f56db392c1b6fc81fc0c05c0e072fb51909fe ...
Waiting for services to be up and running...
Pulling docker image renovate/renovate:25.49@sha256:56def454410e3a44d20081244401330e58c1ce417dff3237f34dd3a20d4a218b ...
Using docker image sha256:bdaf1372959bb42cc79628cf092ee3600e15387562120c140cb7508807e84e58 for renovate/renovate:25.49@sha256:56def454410e3a44d20081244401330e58c1ce417dff3237f34dd3a20d4a218b with digest renovate/renovate@sha256:56def454410e3a44d20081244401330e58c1ce417dff3237f34dd3a20d4a218b ...
Preparing environment
00:01
Running on runner-maeesmzl-project-199-concurrent-0 via infra1.company.com...
Getting source from Git repository
Fetching changes with git depth set to 50...
Reinitialized existing Git repository in /builds/company/renovate-runner/.git/
Checking out af70d19d as main...
Removing node_modules/
Removing renovate-log.ndjson
Removing renovate/
Skipping Git submodules setup
Restoring cache
Checking cache for main-renovate...
No URL provided, cache will not be downloaded from shared cache server. Instead a local version of cache will be extracted.
Successfully extracted cache
Executing "step_script" stage of the job script
Using docker image sha256:bdaf1372959bb42cc79628cf092ee3600e15387562120c140cb7508807e84e58 for renovate/renovate:25.49@sha256:56def454410e3a44d20081244401330e58c1ce417dff3237f34dd3a20d4a218b with digest renovate/renovate@sha256:56def454410e3a44d20081244401330e58c1ce417dff3237f34dd3a20d4a218b ...
$ renovate $RENOVATE_EXTRA_FLAGS
INFO: Repository started (repository=company/company-nuxt)
"renovateVersion": "25.49.0"
INFO: Dependency extraction complete (repository=company/company-nuxt)
"baseBranch": "master",
"stats": {
"managers": {"npm": {"fileCount": 1, "depCount": 44}},
"total": {"fileCount": 1, "depCount": 44}
}
INFO: Repository finished (repository=company/company-nuxt)
"durationMs": 14115
INFO: Repository started (repository=company/wpc)
"renovateVersion": "25.49.0"
INFO: Dependency extraction complete (repository=company/wpc)
"baseBranch": "master",
"stats": {
"managers": {"npm": {"fileCount": 1, "depCount": 24}},
"total": {"fileCount": 1, "depCount": 24}
}
INFO: Repository finished (repository=company/wpc)
"durationMs": 3869
INFO: Repository started (repository=company/map)
"renovateVersion": "25.49.0"
INFO: Dependency extraction complete (repository=company/map)
"baseBranch": "master",
"stats": {
"managers": {
"npm": {"fileCount": 2, "depCount": 45},
"terraform": {"fileCount": 5, "depCount": 13}
},
"total": {"fileCount": 7, "depCount": 58}
}
INFO: Repository finished (repository=company/map)
"durationMs": 50599
Saving cache for successful job
Creating cache main-renovate...
/builds/company/renovate-runner/renovate: found 68462 matching files and directories
No URL provided, cache will be not uploaded to shared cache server. Cache will be stored only locally.
Created cache
Uploading artifacts for successful job
00:01
Uploading artifacts...
renovate-log.ndjson: found 1 matching files and directories
Uploading artifacts as "archive" to coordinator... ok id=89639 responseStatus=201 Created token=xY6K-gCg
Cleaning up file based variables
00:01
Job succeeded
```
</details>
**Have you created a minimal reproduction repository?**
Please read the [minimal reproductions documentation](https://github.com/renovatebot/renovate/blob/main/docs/development/minimal-reproductions.md) to learn how to make a good minimal reproduction repository.
- [ ] I have provided a minimal reproduction repository
- [ ] I don't have time for that, but it happens in a public repository I have linked to
- [x] I don't have time for that, and cannot share my private repository
- [ ] The nature of this bug means it's impossible to reproduce publicly
**Additional context**
<!-- Add any other context about the problem here, including your own debugging or ideas on what went wrong. -->
My configs:
```
// renovate-config-base
{
"extends": [
"config:base",
":timezone(Europe/Vienna)",
":label(Renovate)",
":assignee(gitlab)"
],
"packageRules": [
{
"matchUpdateTypes": ["major"],
"addLabels": ["SemVer::major"]
},
{
"matchUpdateTypes": ["minor"],
"addLabels": ["SemVer::minor"]
},
{
"matchUpdateTypes": ["patch"],
"addLabels": ["SemVer::patch"]
}
]
}
```
```
// renovate-config-javascript
{
"extends": [
"local>company/renovate-config-base",
":pinAllExceptPeerDependencies",
":onlyNpm"
],
"packageRules": [
{
"matchDatasources": ["npm"],
"stabilityDays": 3
},
{
"matchDepTypes": ["dependencies"],
"addLabels": ["Dependency::runtime"]
},
{
"matchDepTypes": ["devDependencies"],
"addLabels": ["Dependency::development"]
},
{
"matchDepTypes": ["peerDependencies"],
"addLabels": ["Dependency::peer"]
},
{
"matchDepTypes": ["optionalDependencies"],
"addLabels": ["Dependency::optional"]
},
{
"matchDepTypes": ["bundledDependencies"],
"addLabels": ["Dependency::bundled"]
}
]
}
```
```
// company/map/renovate.json
{
"extends": [
"local>company/renovate-config-javascript",
":disableRateLimiting",
"schedule:weekly",
":dependencyDashboard"
],
"packageRules": [
{
"matchPackageNames": ["@nuxtjs/tailwindcss"],
"allowedVersions": "<4"
},
{
"matchPackageNames": ["husky"],
"allowedVersions": "<5"
},
{
"matchPackageNames": ["core-js"],
"allowedVersions": "<4"
},
{
"matchPackageNames": ["postcss-focus-within"],
"allowedVersions": "<5"
}
],
"dependencyDashboardAutoclose": true
}
```
```
// company/map/package.json
{
"name": "map",
"version": "1.0.0",
"private": true,
"scripts": {
"dev": "nuxt",
"build": "nuxt build",
"start": "nuxt start",
"generate": "nuxt generate",
"lint:js": "eslint --ext .js,.vue --ignore-path .gitignore .",
"lint:style": "stylelint **/*.{vue,css} --ignore-path .gitignore",
"lint": "yarn lint:js && yarn lint:style",
"lint:fix": "yarn lint:js --fix && yarn lint:style --fix",
"test": "jest"
},
"lint-staged": {
"*.{js,vue}": "eslint",
"*.{css,vue}": "stylelint"
},
"husky": {
"hooks": {
"commit-msg": "commitlint -E HUSKY_GIT_PARAMS",
"pre-commit": "lint-staged"
}
},
"dependencies": {
"@nuxtjs/axios": "^5.12.4",
"@nuxtjs/pwa": "^3.3.3",
"@nuxtjs/sentry": "^4.5.0",
"core-js": "3",
"d3": "^6.3.1",
"date-fns": "^2.16.1",
"leaflet": "^1.7.1",
"nuxt": "^2.14.12",
"topojson": "^3.0.2",
"vue-matomo": "^3.14.0-0",
"vue2-leaflet": "^2.6.0"
},
"devDependencies": {
"@babel/runtime-corejs3": "^7.12.5",
"@commitlint/cli": "^11.0.0",
"@commitlint/config-conventional": "^11.0.0",
"@nuxt/types": "~2.14.0",
"@nuxtjs/eslint-config": "^5.0.0",
"@nuxtjs/eslint-module": "^3.0.2",
"@nuxtjs/stylelint-module": "^4.0.0",
"@nuxtjs/tailwindcss": "^3.4.1",
"@vue/test-utils": "^1.1.2",
"babel-core": "7.0.0-bridge.0",
"babel-eslint": "^10.1.0",
"babel-jest": "^26.6.3",
"eslint": "^7.16.0",
"eslint-config-prettier": "^7.1.0",
"eslint-plugin-nuxt": "^2.0.0",
"eslint-plugin-prettier": "^3.3.0",
"fibers": "^5.0.0",
"fs-extra": "^9.0.1",
"husky": "^4.3.6",
"jest": "^26.6.3",
"lint-staged": "^10.5.3",
"prettier": "^2.2.1",
"sass": "^1.30.0",
"sass-loader": "^10.1.0",
"stylelint": "^13.8.0",
"stylelint-config-prettier": "^8.0.2",
"stylelint-config-standard": "^20.0.0",
"stylelint-order": "^4.1.0",
"stylelint-scss": "^3.18.0",
"vue-jest": "^4.0.0-rc.1",
"workerize-loader": "^1.3.0"
},
"browserslist": [
"last 2 versions",
"> 0.15%",
"not IE 9",
"chrome >70",
"android >4",
"ios_saf >9"
],
"resolutions": {
"postcss-focus-within": "^4.0.0"
}
}
```
...
| non_usab | these updates encountered an error and will be retried click a checkbox below to force a retry now please do not report any security concerns this way email renovate disclosure whitesourcesoftware com instead how are you running renovate whitesource renovate hosted app on github com self hosted if using the hosted app please skip to the next section otherwise if self hosted please complete the following please select which platform you are using azure devops dev azure com azure devops server bitbucket cloud bitbucket org bitbucket server gitea github com github enterprise server gitlab com gitlab self hosted renovate version describe the bug dashboard says these updates encountered an error and will be retried click a checkbox below to force a retry now this issue contains a list of renovate updates and their statuses awaiting schedule these updates are awaiting their schedule click on a checkbox to get an update now chore deps update dependency nuxtjs tailwindcss to chore deps update dependency husky to chore deps update dependency lint staged to fix deps update dependency nuxtjs pwa to chore deps update dependency babel runtime to chore deps update dependency eslint to chore deps update dependency eslint config prettier to chore deps update dependency eslint plugin prettier to chore deps update dependency fs extra to chore deps update dependency prettier to chore deps update dependency sass to chore deps update dependency sass loader to chore deps update dependency stylelint to chore deps update dependency stylelint scss to chore deps update nuxtjs monorepo to nuxt types nuxt chore deps update vue monorepo vue test utils vue jest fix deps update dependency nuxt content theme docs to fix deps update dependency nuxtjs axios to fix deps update dependency core js to fix deps update dependency to fix deps update dependency date fns to fix deps update dependency leaflet to chore deps update commitlint monorepo to major commitlint cli commitlint config conventional chore deps update dependency nuxtjs eslint config to chore deps update dependency eslint config prettier to chore deps update dependency fs extra to chore deps update dependency lint staged to chore deps update dependency sass loader to chore deps update dependency stylelint config standard to chore deps update jest monorepo to major babel jest jest fix deps update dependency nuxtjs sentry to fix deps update dependency to fix deps update dependency vue matomo to errored these updates encountered an error and will be retried click a checkbox below to force a retry now chore deps pin dependencies babel runtime commitlint cli commitlint config conventional nuxt content theme docs nuxt types nuxtjs axios nuxtjs eslint config nuxtjs eslint module nuxtjs pwa nuxtjs sentry nuxtjs stylelint module nuxtjs tailwindcss vue test utils babel eslint babel jest cloudflare core js date fns eslint eslint config prettier eslint plugin nuxt eslint plugin prettier fibers fs extra hashicorp terraform hcloud husky jest leaflet lint staged nuxt postcss focus within prettier sass sass loader stylelint stylelint config prettier stylelint config standard stylelint order stylelint scss topojson vue jest vue matomo leaflet workerize loader however retry does not work mr creation does not work for the project for company map project it works however for other projects such as company wpc or company nuxt runner logs do not print any error relevant debug logs try not to raise a bug report unless you ve looked at the logs first if you re running self hosted run with log level debug in your environment variables and search for whatever dependency branch pr that is causing the problem if you are using the renovate app log into and locate the correct job log for when the problem occurred e g when the pr was created paste the relevant logs here not the entire thing and not just a link to the dashboard others do not have permissions to view them click me to see logs running with gitlab runner on renovate maeesmzl resolving secrets preparing the docker executor using docker executor with image renovate renovate starting service docker dind pulling docker image docker dind using docker image for docker dind with digest docker waiting for services to be up and running pulling docker image renovate renovate using docker image for renovate renovate with digest renovate renovate preparing environment running on runner maeesmzl project concurrent via company com getting source from git repository fetching changes with git depth set to reinitialized existing git repository in builds company renovate runner git checking out as main removing node modules removing renovate log ndjson removing renovate skipping git submodules setup restoring cache checking cache for main renovate no url provided cache will not be downloaded from shared cache server instead a local version of cache will be extracted successfully extracted cache executing step script stage of the job script using docker image for renovate renovate with digest renovate renovate renovate renovate extra flags info repository started repository company company nuxt renovateversion info dependency extraction complete repository company company nuxt basebranch master stats managers npm filecount depcount total filecount depcount info repository finished repository company company nuxt durationms info repository started repository company wpc renovateversion info dependency extraction complete repository company wpc basebranch master stats managers npm filecount depcount total filecount depcount info repository finished repository company wpc durationms info repository started repository company map renovateversion info dependency extraction complete repository company map basebranch master stats managers npm filecount depcount terraform filecount depcount total filecount depcount info repository finished repository company map durationms saving cache for successful job creating cache main renovate builds company renovate runner renovate found matching files and directories no url provided cache will be not uploaded to shared cache server cache will be stored only locally created cache uploading artifacts for successful job uploading artifacts renovate log ndjson found matching files and directories uploading artifacts as archive to coordinator ok id responsestatus created token gcg cleaning up file based variables job succeeded have you created a minimal reproduction repository please read the to learn how to make a good minimal reproduction repository i have provided a minimal reproduction repository i don t have time for that but it happens in a public repository i have linked to i don t have time for that and cannot share my private repository the nature of this bug means it s impossible to reproduce publicly additional context my configs renovate config base extends config base timezone europe vienna label renovate assignee gitlab packagerules matchupdatetypes addlabels matchupdatetypes addlabels matchupdatetypes addlabels renovate config javascript extends local company renovate config base pinallexceptpeerdependencies onlynpm packagerules matchdatasources stabilitydays matchdeptypes addlabels matchdeptypes addlabels matchdeptypes addlabels matchdeptypes addlabels matchdeptypes addlabels company map renovate json extends local company renovate config javascript disableratelimiting schedule weekly dependencydashboard packagerules matchpackagenames allowedversions matchpackagenames allowedversions matchpackagenames allowedversions matchpackagenames allowedversions dependencydashboardautoclose true company map package json name map version private true scripts dev nuxt build nuxt build start nuxt start generate nuxt generate lint js eslint ext js vue ignore path gitignore lint style stylelint vue css ignore path gitignore lint yarn lint js yarn lint style lint fix yarn lint js fix yarn lint style fix test jest lint staged js vue eslint css vue stylelint husky hooks commit msg commitlint e husky git params pre commit lint staged dependencies nuxtjs axios nuxtjs pwa nuxtjs sentry core js date fns leaflet nuxt topojson vue matomo leaflet devdependencies babel runtime commitlint cli commitlint config conventional nuxt types nuxtjs eslint config nuxtjs eslint module nuxtjs stylelint module nuxtjs tailwindcss vue test utils babel core bridge babel eslint babel jest eslint eslint config prettier eslint plugin nuxt eslint plugin prettier fibers fs extra husky jest lint staged prettier sass sass loader stylelint stylelint config prettier stylelint config standard stylelint order stylelint scss vue jest rc workerize loader browserslist last versions not ie chrome android ios saf resolutions postcss focus within | 0 |
296,595 | 9,122,408,488 | IssuesEvent | 2019-02-23 07:39:25 | ChrisCScott/forecaster | https://api.github.com/repos/ChrisCScott/forecaster | closed | Align timing of income and living expenses transactions | IncomeForecast WithdrawalForecast medium priority | Currently we assume that income is received whenever dictated by `Person.payment_frequency` (and we assume it's received in the middle of each period), whereas living expenses are incurred monthly at the start of each month. These don't line up, which leads to odd behaviour.
Ideally, living expenses would be recorded as being incurred at the same time that employment income is received. Consider adding living expenses at the timings dictated by each person's `payment_frequency`, proportionately to each person's `net_income`. | 1.0 | Align timing of income and living expenses transactions - Currently we assume that income is received whenever dictated by `Person.payment_frequency` (and we assume it's received in the middle of each period), whereas living expenses are incurred monthly at the start of each month. These don't line up, which leads to odd behaviour.
Ideally, living expenses would be recorded as being incurred at the same time that employment income is received. Consider adding living expenses at the timings dictated by each person's `payment_frequency`, proportionately to each person's `net_income`. | non_usab | align timing of income and living expenses transactions currently we assume that income is received whenever dictated by person payment frequency and we assume it s received in the middle of each period whereas living expenses are incurred monthly at the start of each month these don t line up which leads to odd behaviour ideally living expenses would be recorded as being incurred at the same time that employment income is received consider adding living expenses at the timings dictated by each person s payment frequency proportionately to each person s net income | 0 |
102,244 | 21,936,926,813 | IssuesEvent | 2022-05-23 14:30:42 | betagouv/mon-service-securise | https://api.github.com/repos/betagouv/mon-service-securise | opened | Ne pas passer `identifiantsMesures` au constructeur de la classe `Mesures` | code | Pour faire suite à la PR #251
Il n'y a pas lieu de passer les identifiants des mesures du référentiel au constructeur de la classe `Mesures`. On doit pouvoir faire le test sur le nombre de mesures complétées dans `MesuresGenerales#statutSaisie`. | 1.0 | Ne pas passer `identifiantsMesures` au constructeur de la classe `Mesures` - Pour faire suite à la PR #251
Il n'y a pas lieu de passer les identifiants des mesures du référentiel au constructeur de la classe `Mesures`. On doit pouvoir faire le test sur le nombre de mesures complétées dans `MesuresGenerales#statutSaisie`. | non_usab | ne pas passer identifiantsmesures au constructeur de la classe mesures pour faire suite à la pr il n y a pas lieu de passer les identifiants des mesures du référentiel au constructeur de la classe mesures on doit pouvoir faire le test sur le nombre de mesures complétées dans mesuresgenerales statutsaisie | 0 |
15,224 | 9,880,198,154 | IssuesEvent | 2019-06-24 12:02:14 | ebmdatalab/openprescribing | https://api.github.com/repos/ebmdatalab/openprescribing | closed | Put practice address on measure breakdown pages | trivial usability-ux | Example page https://openprescribing.net/measure/libre/practice/H81073/
Apart from looking at the URL which tells you the code, it isn't clear which practice is shown. As CCGs get bigger there will be more and more practices with same name in same CCG so this could be problematic. | True | Put practice address on measure breakdown pages - Example page https://openprescribing.net/measure/libre/practice/H81073/
Apart from looking at the URL which tells you the code, it isn't clear which practice is shown. As CCGs get bigger there will be more and more practices with same name in same CCG so this could be problematic. | usab | put practice address on measure breakdown pages example page apart from looking at the url which tells you the code it isn t clear which practice is shown as ccgs get bigger there will be more and more practices with same name in same ccg so this could be problematic | 1 |
177,669 | 21,485,941,993 | IssuesEvent | 2022-04-26 23:25:28 | RG4421/multi-juicer | https://api.github.com/repos/RG4421/multi-juicer | opened | CVE-2022-29078 (High) detected in ejs-2.7.4.tgz, ejs-3.1.6.tgz | security vulnerability | ## CVE-2022-29078 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>ejs-2.7.4.tgz</b>, <b>ejs-3.1.6.tgz</b></p></summary>
<p>
<details><summary><b>ejs-2.7.4.tgz</b></p></summary>
<p>Embedded JavaScript templates</p>
<p>Library home page: <a href="https://registry.npmjs.org/ejs/-/ejs-2.7.4.tgz">https://registry.npmjs.org/ejs/-/ejs-2.7.4.tgz</a></p>
<p>Path to dependency file: /juice-balancer/ui/package.json</p>
<p>Path to vulnerable library: /juice-balancer/ui/node_modules/ejs/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-4.0.3.tgz (Root Library)
- workbox-webpack-plugin-5.1.4.tgz
- workbox-build-5.1.4.tgz
- rollup-plugin-off-main-thread-1.4.2.tgz
- :x: **ejs-2.7.4.tgz** (Vulnerable Library)
</details>
<details><summary><b>ejs-3.1.6.tgz</b></p></summary>
<p>Embedded JavaScript templates</p>
<p>Library home page: <a href="https://registry.npmjs.org/ejs/-/ejs-3.1.6.tgz">https://registry.npmjs.org/ejs/-/ejs-3.1.6.tgz</a></p>
<p>Path to dependency file: /juice-balancer/ui/package.json</p>
<p>Path to vulnerable library: /juice-balancer/ui/node_modules/source-map-explorer/node_modules/ejs/package.json</p>
<p>
Dependency Hierarchy:
- source-map-explorer-2.5.2.tgz (Root Library)
- :x: **ejs-3.1.6.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/RG4421/multi-juicer/commit/8576a853ef65531c776b5ea4aac618580e1b0354">8576a853ef65531c776b5ea4aac618580e1b0354</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 ejs (aka Embedded JavaScript templates) package 3.1.6 for Node.js allows server-side template injection in settings[view options][outputFunctionName]. This is parsed as an internal option, and overwrites the outputFunctionName option with an arbitrary OS command (which is executed upon template compilation).
<p>Publish Date: 2022-04-25
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-29078>CVE-2022-29078</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29078~">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29078~</a></p>
<p>Release Date: 2022-04-25</p>
<p>Fix Resolution: ejs - v3.1.7</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"ejs","packageVersion":"2.7.4","packageFilePaths":["/juice-balancer/ui/package.json"],"isTransitiveDependency":true,"dependencyTree":"react-scripts:4.0.3;workbox-webpack-plugin:5.1.4;workbox-build:5.1.4;@surma/rollup-plugin-off-main-thread:1.4.2;ejs:2.7.4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"ejs - v3.1.7","isBinary":false},{"packageType":"javascript/Node.js","packageName":"ejs","packageVersion":"3.1.6","packageFilePaths":["/juice-balancer/ui/package.json"],"isTransitiveDependency":true,"dependencyTree":"source-map-explorer:2.5.2;ejs:3.1.6","isMinimumFixVersionAvailable":true,"minimumFixVersion":"ejs - v3.1.7","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2022-29078","vulnerabilityDetails":"The ejs (aka Embedded JavaScript templates) package 3.1.6 for Node.js allows server-side template injection in settings[view options][outputFunctionName]. This is parsed as an internal option, and overwrites the outputFunctionName option with an arbitrary OS command (which is executed upon template compilation).","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-29078","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2022-29078 (High) detected in ejs-2.7.4.tgz, ejs-3.1.6.tgz - ## CVE-2022-29078 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>ejs-2.7.4.tgz</b>, <b>ejs-3.1.6.tgz</b></p></summary>
<p>
<details><summary><b>ejs-2.7.4.tgz</b></p></summary>
<p>Embedded JavaScript templates</p>
<p>Library home page: <a href="https://registry.npmjs.org/ejs/-/ejs-2.7.4.tgz">https://registry.npmjs.org/ejs/-/ejs-2.7.4.tgz</a></p>
<p>Path to dependency file: /juice-balancer/ui/package.json</p>
<p>Path to vulnerable library: /juice-balancer/ui/node_modules/ejs/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-4.0.3.tgz (Root Library)
- workbox-webpack-plugin-5.1.4.tgz
- workbox-build-5.1.4.tgz
- rollup-plugin-off-main-thread-1.4.2.tgz
- :x: **ejs-2.7.4.tgz** (Vulnerable Library)
</details>
<details><summary><b>ejs-3.1.6.tgz</b></p></summary>
<p>Embedded JavaScript templates</p>
<p>Library home page: <a href="https://registry.npmjs.org/ejs/-/ejs-3.1.6.tgz">https://registry.npmjs.org/ejs/-/ejs-3.1.6.tgz</a></p>
<p>Path to dependency file: /juice-balancer/ui/package.json</p>
<p>Path to vulnerable library: /juice-balancer/ui/node_modules/source-map-explorer/node_modules/ejs/package.json</p>
<p>
Dependency Hierarchy:
- source-map-explorer-2.5.2.tgz (Root Library)
- :x: **ejs-3.1.6.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/RG4421/multi-juicer/commit/8576a853ef65531c776b5ea4aac618580e1b0354">8576a853ef65531c776b5ea4aac618580e1b0354</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 ejs (aka Embedded JavaScript templates) package 3.1.6 for Node.js allows server-side template injection in settings[view options][outputFunctionName]. This is parsed as an internal option, and overwrites the outputFunctionName option with an arbitrary OS command (which is executed upon template compilation).
<p>Publish Date: 2022-04-25
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-29078>CVE-2022-29078</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29078~">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29078~</a></p>
<p>Release Date: 2022-04-25</p>
<p>Fix Resolution: ejs - v3.1.7</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"ejs","packageVersion":"2.7.4","packageFilePaths":["/juice-balancer/ui/package.json"],"isTransitiveDependency":true,"dependencyTree":"react-scripts:4.0.3;workbox-webpack-plugin:5.1.4;workbox-build:5.1.4;@surma/rollup-plugin-off-main-thread:1.4.2;ejs:2.7.4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"ejs - v3.1.7","isBinary":false},{"packageType":"javascript/Node.js","packageName":"ejs","packageVersion":"3.1.6","packageFilePaths":["/juice-balancer/ui/package.json"],"isTransitiveDependency":true,"dependencyTree":"source-map-explorer:2.5.2;ejs:3.1.6","isMinimumFixVersionAvailable":true,"minimumFixVersion":"ejs - v3.1.7","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2022-29078","vulnerabilityDetails":"The ejs (aka Embedded JavaScript templates) package 3.1.6 for Node.js allows server-side template injection in settings[view options][outputFunctionName]. This is parsed as an internal option, and overwrites the outputFunctionName option with an arbitrary OS command (which is executed upon template compilation).","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-29078","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | non_usab | cve high detected in ejs tgz ejs tgz cve high severity vulnerability vulnerable libraries ejs tgz ejs tgz ejs tgz embedded javascript templates library home page a href path to dependency file juice balancer ui package json path to vulnerable library juice balancer ui node modules ejs package json dependency hierarchy react scripts tgz root library workbox webpack plugin tgz workbox build tgz rollup plugin off main thread tgz x ejs tgz vulnerable library ejs tgz embedded javascript templates library home page a href path to dependency file juice balancer ui package json path to vulnerable library juice balancer ui node modules source map explorer node modules ejs package json dependency hierarchy source map explorer tgz root library x ejs tgz vulnerable library found in head commit a href found in base branch master vulnerability details the ejs aka embedded javascript templates package for node js allows server side template injection in settings this is parsed as an internal option and overwrites the outputfunctionname option with an arbitrary os command which is executed upon template compilation 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 ejs isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree react scripts workbox webpack plugin workbox build surma rollup plugin off main thread ejs isminimumfixversionavailable true minimumfixversion ejs isbinary false packagetype javascript node js packagename ejs packageversion packagefilepaths istransitivedependency true dependencytree source map explorer ejs isminimumfixversionavailable true minimumfixversion ejs isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails the ejs aka embedded javascript templates package for node js allows server side template injection in settings this is parsed as an internal option and overwrites the outputfunctionname option with an arbitrary os command which is executed upon template compilation vulnerabilityurl | 0 |
218,652 | 24,385,399,256 | IssuesEvent | 2022-10-04 11:19:12 | elastic/integrations | https://api.github.com/repos/elastic/integrations | closed | Azure WAF | Team:Security-External Integrations Category: SWG/WAF New Integration | ### Description
Azure Web Application Firewall (WAF) provides centralized protection of your web applications from common exploits and vulnerabilities. Web applications are increasingly targeted by malicious attacks that exploit commonly known vulnerabilities. SQL injection and cross-site scripting are among the most common attacks.
### Architecture
Event Hubs are the most common way of integrating Azure WAF with SIEMs. Relevant documentation [here](https://docs.microsoft.com/en-us/azure/web-application-firewall/ag/web-application-firewall-logs).
# Integration release checklist
This checklist is intended for integrations maintainers to ensure consistency
when creating or updating a Package, Module or Dataset for an Integration.
### All changes
- [ ] Change follows the [contributing guidelines](https://github.com/elastic/integrations/blob/master/CONTRIBUTING.md)
- [ ] Supported versions of the monitoring target are documented
- [ ] Supported operating systems are documented (if applicable)
- [ ] Integration or [System tests](https://github.com/elastic/elastic-package/blob/master/docs/howto/system_testing.md) exist
- [ ] Documentation exists
- [ ] Fields follow [ECS](https://github.com/elastic/ecs) and [naming conventions](https://www.elastic.co/guide/en/beats/devguide/master/event-conventions.html)
- [ ] At least a manual test with ES / Kibana / Agent has been performed.
- [ ] Required Kibana version set to:
### New Package
- [ ] Screenshot of the "Add Integration" page on Fleet added
### Dashboards changes
- [ ] Dashboards exists
- [ ] Screenshots added or updated
- [ ] Datastream filters added to visualizations
### Log dataset changes
- [ ] [Pipeline tests](https://github.com/elastic/elastic-package/blob/master/docs/howto/pipeline_testing.md) exist (if applicable)
- [ ] Generated output for at least 1 log file exists
- [ ] Sample event (`sample_event.json`) exists | True | Azure WAF - ### Description
Azure Web Application Firewall (WAF) provides centralized protection of your web applications from common exploits and vulnerabilities. Web applications are increasingly targeted by malicious attacks that exploit commonly known vulnerabilities. SQL injection and cross-site scripting are among the most common attacks.
### Architecture
Event Hubs are the most common way of integrating Azure WAF with SIEMs. Relevant documentation [here](https://docs.microsoft.com/en-us/azure/web-application-firewall/ag/web-application-firewall-logs).
# Integration release checklist
This checklist is intended for integrations maintainers to ensure consistency
when creating or updating a Package, Module or Dataset for an Integration.
### All changes
- [ ] Change follows the [contributing guidelines](https://github.com/elastic/integrations/blob/master/CONTRIBUTING.md)
- [ ] Supported versions of the monitoring target are documented
- [ ] Supported operating systems are documented (if applicable)
- [ ] Integration or [System tests](https://github.com/elastic/elastic-package/blob/master/docs/howto/system_testing.md) exist
- [ ] Documentation exists
- [ ] Fields follow [ECS](https://github.com/elastic/ecs) and [naming conventions](https://www.elastic.co/guide/en/beats/devguide/master/event-conventions.html)
- [ ] At least a manual test with ES / Kibana / Agent has been performed.
- [ ] Required Kibana version set to:
### New Package
- [ ] Screenshot of the "Add Integration" page on Fleet added
### Dashboards changes
- [ ] Dashboards exists
- [ ] Screenshots added or updated
- [ ] Datastream filters added to visualizations
### Log dataset changes
- [ ] [Pipeline tests](https://github.com/elastic/elastic-package/blob/master/docs/howto/pipeline_testing.md) exist (if applicable)
- [ ] Generated output for at least 1 log file exists
- [ ] Sample event (`sample_event.json`) exists | non_usab | azure waf description azure web application firewall waf provides centralized protection of your web applications from common exploits and vulnerabilities web applications are increasingly targeted by malicious attacks that exploit commonly known vulnerabilities sql injection and cross site scripting are among the most common attacks architecture event hubs are the most common way of integrating azure waf with siems relevant documentation integration release checklist this checklist is intended for integrations maintainers to ensure consistency when creating or updating a package module or dataset for an integration all changes change follows the supported versions of the monitoring target are documented supported operating systems are documented if applicable integration or exist documentation exists fields follow and at least a manual test with es kibana agent has been performed required kibana version set to new package screenshot of the add integration page on fleet added dashboards changes dashboards exists screenshots added or updated datastream filters added to visualizations log dataset changes exist if applicable generated output for at least log file exists sample event sample event json exists | 0 |
15,101 | 9,764,430,982 | IssuesEvent | 2019-06-05 15:45:22 | downshiftorg/prophoto7-issues | https://api.github.com/repos/downshiftorg/prophoto7-issues | closed | Deleting font style should warn if being used | usability | <a href="https://github.com/meatwad5675"><img src="https://avatars3.githubusercontent.com/u/11544705?v=4" align="left" width="96" height="96" hspace="10"></img></a> **Issue by [meatwad5675](https://github.com/meatwad5675)**
_Friday Apr 27, 2018 at 19:55 GMT_
_Originally opened as https://github.com/downshiftorg/prophoto/issues/3213_
----
Keep selected font styles in state
| True | Deleting font style should warn if being used - <a href="https://github.com/meatwad5675"><img src="https://avatars3.githubusercontent.com/u/11544705?v=4" align="left" width="96" height="96" hspace="10"></img></a> **Issue by [meatwad5675](https://github.com/meatwad5675)**
_Friday Apr 27, 2018 at 19:55 GMT_
_Originally opened as https://github.com/downshiftorg/prophoto/issues/3213_
----
Keep selected font styles in state
| usab | deleting font style should warn if being used issue by friday apr at gmt originally opened as keep selected font styles in state | 1 |
134,958 | 18,518,915,981 | IssuesEvent | 2021-10-20 13:15:13 | vipinsun/fabric-sdk-go | https://api.github.com/repos/vipinsun/fabric-sdk-go | opened | CVE-2020-7238 (High) detected in netty-codec-http-4.1.38.Final.jar | security vulnerability | ## CVE-2020-7238 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>netty-codec-http-4.1.38.Final.jar</b></p></summary>
<p>Netty is an asynchronous event-driven network application framework for
rapid development of maintainable high performance protocol servers and
clients.</p>
<p>Path to dependency file: fabric-sdk-go/test/fixtures/testdata/java/example_cc/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/io.netty/netty-codec-http/4.1.38.Final/4d55b3cdb74cd140d262de96987ebd369125a64c/netty-codec-http-4.1.38.Final.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/io.netty/netty-codec-http/4.1.38.Final/4d55b3cdb74cd140d262de96987ebd369125a64c/netty-codec-http-4.1.38.Final.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/io.netty/netty-codec-http/4.1.38.Final/4d55b3cdb74cd140d262de96987ebd369125a64c/netty-codec-http-4.1.38.Final.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/io.netty/netty-codec-http/4.1.38.Final/4d55b3cdb74cd140d262de96987ebd369125a64c/netty-codec-http-4.1.38.Final.jar</p>
<p>
Dependency Hierarchy:
- fabric-chaincode-shim-1.4.8.jar (Root Library)
- fabric-chaincode-protos-1.4.8.jar
- grpc-netty-1.23.0.jar
- netty-codec-http2-4.1.38.Final.jar
- :x: **netty-codec-http-4.1.38.Final.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/vipinsun/fabric-sdk-go/commit/432a85aa9d4094d52823bdb4be9cf19758df85e1">432a85aa9d4094d52823bdb4be9cf19758df85e1</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Netty 4.1.43.Final allows HTTP Request Smuggling because it mishandles Transfer-Encoding whitespace (such as a [space]Transfer-Encoding:chunked line) and a later Content-Length header. This issue exists because of an incomplete fix for CVE-2019-16869.
<p>Publish Date: 2020-01-27
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7238>CVE-2020-7238</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/netty/netty/issues/9861">https://github.com/netty/netty/issues/9861</a></p>
<p>Release Date: 2020-01-27</p>
<p>Fix Resolution: io.netty:netty-all:4.1.44.Final;io.netty:netty-codec-http:4.1.44.Final</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-7238 (High) detected in netty-codec-http-4.1.38.Final.jar - ## CVE-2020-7238 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>netty-codec-http-4.1.38.Final.jar</b></p></summary>
<p>Netty is an asynchronous event-driven network application framework for
rapid development of maintainable high performance protocol servers and
clients.</p>
<p>Path to dependency file: fabric-sdk-go/test/fixtures/testdata/java/example_cc/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/io.netty/netty-codec-http/4.1.38.Final/4d55b3cdb74cd140d262de96987ebd369125a64c/netty-codec-http-4.1.38.Final.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/io.netty/netty-codec-http/4.1.38.Final/4d55b3cdb74cd140d262de96987ebd369125a64c/netty-codec-http-4.1.38.Final.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/io.netty/netty-codec-http/4.1.38.Final/4d55b3cdb74cd140d262de96987ebd369125a64c/netty-codec-http-4.1.38.Final.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/io.netty/netty-codec-http/4.1.38.Final/4d55b3cdb74cd140d262de96987ebd369125a64c/netty-codec-http-4.1.38.Final.jar</p>
<p>
Dependency Hierarchy:
- fabric-chaincode-shim-1.4.8.jar (Root Library)
- fabric-chaincode-protos-1.4.8.jar
- grpc-netty-1.23.0.jar
- netty-codec-http2-4.1.38.Final.jar
- :x: **netty-codec-http-4.1.38.Final.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/vipinsun/fabric-sdk-go/commit/432a85aa9d4094d52823bdb4be9cf19758df85e1">432a85aa9d4094d52823bdb4be9cf19758df85e1</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Netty 4.1.43.Final allows HTTP Request Smuggling because it mishandles Transfer-Encoding whitespace (such as a [space]Transfer-Encoding:chunked line) and a later Content-Length header. This issue exists because of an incomplete fix for CVE-2019-16869.
<p>Publish Date: 2020-01-27
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7238>CVE-2020-7238</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/netty/netty/issues/9861">https://github.com/netty/netty/issues/9861</a></p>
<p>Release Date: 2020-01-27</p>
<p>Fix Resolution: io.netty:netty-all:4.1.44.Final;io.netty:netty-codec-http:4.1.44.Final</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_usab | cve high detected in netty codec http final jar cve high severity vulnerability vulnerable library netty codec http final jar netty is an asynchronous event driven network application framework for rapid development of maintainable high performance protocol servers and clients path to dependency file fabric sdk go test fixtures testdata java example cc build gradle path to vulnerable library home wss scanner gradle caches modules files io netty netty codec http final netty codec http final jar home wss scanner gradle caches modules files io netty netty codec http final netty codec http final jar home wss scanner gradle caches modules files io netty netty codec http final netty codec http final jar home wss scanner gradle caches modules files io netty netty codec http final netty codec http final jar dependency hierarchy fabric chaincode shim jar root library fabric chaincode protos jar grpc netty jar netty codec final jar x netty codec http final jar vulnerable library found in head commit a href found in base branch main vulnerability details netty final allows http request smuggling because it mishandles transfer encoding whitespace such as a transfer encoding chunked line and a later content length header this issue exists because of an incomplete fix for cve 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 io netty netty all final io netty netty codec http final step up your open source security game with whitesource | 0 |
50,283 | 13,506,487,379 | IssuesEvent | 2020-09-14 03:09:33 | OpenLiberty/open-liberty | https://api.github.com/repos/OpenLiberty/open-liberty | opened | Swap acmeCA tracegroup to ACMECA | team:Core Security team:Wendigo East | Change the tracegroup for the acmeCA feature from ACME to ACMECA | True | Swap acmeCA tracegroup to ACMECA - Change the tracegroup for the acmeCA feature from ACME to ACMECA | non_usab | swap acmeca tracegroup to acmeca change the tracegroup for the acmeca feature from acme to acmeca | 0 |
31,568 | 7,395,629,622 | IssuesEvent | 2018-03-18 00:35:00 | GiantsLoveDeathMetal/foolscap | https://api.github.com/repos/GiantsLoveDeathMetal/foolscap | closed | Move `os` out of note_content and into handle_note_io | Clean Code | This: https://github.com/GiantsLoveDeathMetal/foolscap/blob/master/foolscap/note_content.py#L1
The functions in `handle_note_io` should do the lifting of `os` | 1.0 | Move `os` out of note_content and into handle_note_io - This: https://github.com/GiantsLoveDeathMetal/foolscap/blob/master/foolscap/note_content.py#L1
The functions in `handle_note_io` should do the lifting of `os` | non_usab | move os out of note content and into handle note io this the functions in handle note io should do the lifting of os | 0 |
19,728 | 14,497,095,402 | IssuesEvent | 2020-12-11 13:46:17 | zaproxy/zaproxy | https://api.github.com/repos/zaproxy/zaproxy | closed | No Way to Specify Custom 404 | Usability enhancement tracker | ```
What steps will reproduce the problem?
1. Scan something that returns custom a 302 to a custom 404 error message.
What is the expected output? What do you see instead?
Lots of False positives, especially when it comes to default files.
What version of the product are you using? On what operating system?
1.0.0. OS doesn't matter.
Please provide any additional information below.
```
> Original issue reported on code.google.com by `logicalgambit` on 2010-10-06 16:13:56
---
Part 1
======
- [x] Initial implementation - https://github.com/zaproxy/zaproxy/pull/3638
- [x] Analyzer fallback - https://github.com/zaproxy/zaproxy/pull/6194
- [x] UnitTests - https://github.com/zaproxy/zaproxy/pull/6232, https://github.com/zaproxy/zaproxy/pull/6245, https://github.com/zaproxy/zaproxy/pull/6310
- [x] Update User Guide / zap-core-help - https://github.com/zaproxy/zap-core-help/pull/335
Part 2
======
- [x] pscan rules adapted (When targeting 2.10.0) - https://github.com/zaproxy/zap-extensions/pull/2616, https://github.com/zaproxy/zap-extensions/pull/2627 https://github.com/zaproxy/zap-extensions/pull/2630
- [x] ascan rules adapted (When targeting 2.10.0) - https://github.com/zaproxy/zap-extensions/pull/2639 https://github.com/zaproxy/zap-extensions/pull/2642
| True | No Way to Specify Custom 404 - ```
What steps will reproduce the problem?
1. Scan something that returns custom a 302 to a custom 404 error message.
What is the expected output? What do you see instead?
Lots of False positives, especially when it comes to default files.
What version of the product are you using? On what operating system?
1.0.0. OS doesn't matter.
Please provide any additional information below.
```
> Original issue reported on code.google.com by `logicalgambit` on 2010-10-06 16:13:56
---
Part 1
======
- [x] Initial implementation - https://github.com/zaproxy/zaproxy/pull/3638
- [x] Analyzer fallback - https://github.com/zaproxy/zaproxy/pull/6194
- [x] UnitTests - https://github.com/zaproxy/zaproxy/pull/6232, https://github.com/zaproxy/zaproxy/pull/6245, https://github.com/zaproxy/zaproxy/pull/6310
- [x] Update User Guide / zap-core-help - https://github.com/zaproxy/zap-core-help/pull/335
Part 2
======
- [x] pscan rules adapted (When targeting 2.10.0) - https://github.com/zaproxy/zap-extensions/pull/2616, https://github.com/zaproxy/zap-extensions/pull/2627 https://github.com/zaproxy/zap-extensions/pull/2630
- [x] ascan rules adapted (When targeting 2.10.0) - https://github.com/zaproxy/zap-extensions/pull/2639 https://github.com/zaproxy/zap-extensions/pull/2642
| usab | no way to specify custom what steps will reproduce the problem scan something that returns custom a to a custom error message what is the expected output what do you see instead lots of false positives especially when it comes to default files what version of the product are you using on what operating system os doesn t matter please provide any additional information below original issue reported on code google com by logicalgambit on part initial implementation analyzer fallback unittests update user guide zap core help part pscan rules adapted when targeting ascan rules adapted when targeting | 1 |
6,222 | 4,186,266,303 | IssuesEvent | 2016-06-23 14:02:00 | lionheart/openradar-mirror | https://api.github.com/repos/lionheart/openradar-mirror | opened | 26839946: Xcode 8 doesn't provide enough extension hook to provide vim keybindings. | classification:ui/usability reproducible:always status:open | #### Description
Summary:
Many developers (read: me and few similarly weird people I know) relied on undocumented Xcode plugins feature. This allowed us to use a fairly popular plugin, XVim (https://github.com/XVimProject/XVim/) that provided vim-like keybindigs for Xcode.
Since Xcode 8, this is no longer possible — SIP disallows injecting your own key mapping and the extension API isn't powerful enough to enable plugins similar to this.
Steps to Reproduce:
1. Open Xcode 8
2. Try to use Xvim
Expected Results:
You can use vim-like bindings and be more productive (or at least think you are).
Actual Results:
You're sad because you can't use vim-like bindings.
Version:
Xcode 8 beta 1.
Notes:
Configuration:
Attachments:
-
Product Version: 8
Created: 2016-06-16T16:49:44.900020
Originated: 2016-06-16T00:00:00
Open Radar Link: http://www.openradar.me/26839946 | True | 26839946: Xcode 8 doesn't provide enough extension hook to provide vim keybindings. - #### Description
Summary:
Many developers (read: me and few similarly weird people I know) relied on undocumented Xcode plugins feature. This allowed us to use a fairly popular plugin, XVim (https://github.com/XVimProject/XVim/) that provided vim-like keybindigs for Xcode.
Since Xcode 8, this is no longer possible — SIP disallows injecting your own key mapping and the extension API isn't powerful enough to enable plugins similar to this.
Steps to Reproduce:
1. Open Xcode 8
2. Try to use Xvim
Expected Results:
You can use vim-like bindings and be more productive (or at least think you are).
Actual Results:
You're sad because you can't use vim-like bindings.
Version:
Xcode 8 beta 1.
Notes:
Configuration:
Attachments:
-
Product Version: 8
Created: 2016-06-16T16:49:44.900020
Originated: 2016-06-16T00:00:00
Open Radar Link: http://www.openradar.me/26839946 | usab | xcode doesn t provide enough extension hook to provide vim keybindings description summary many developers read me and few similarly weird people i know relied on undocumented xcode plugins feature this allowed us to use a fairly popular plugin xvim that provided vim like keybindigs for xcode since xcode this is no longer possible — sip disallows injecting your own key mapping and the extension api isn t powerful enough to enable plugins similar to this steps to reproduce open xcode try to use xvim expected results you can use vim like bindings and be more productive or at least think you are actual results you re sad because you can t use vim like bindings version xcode beta notes configuration attachments product version created originated open radar link | 1 |
23,711 | 22,621,098,740 | IssuesEvent | 2022-06-30 06:25:42 | bevyengine/bevy | https://api.github.com/repos/bevyengine/bevy | closed | [wasm] Attempting to get an EventWriter for an unregistered event type panics with an unhelpful message | D-Good-First-Issue A-ECS C-Usability S-Ready-For-Implementation | ## Bevy version
0.5.0
## Operating system & version
wasm
## What you did
Create a system like so:
```
struct Event;
fn system(mut events: EventWriter<Event>) {}
```
Set up the app, but do not register the event
```
App::build()
.with_system(system.system())
.run();
```
## What you expected to happen
The application is misconfigured so I expect this to panic, and ideally the message for the panic would explain that a system attempted to fetch an `EventWriter` for an unregistered event type.
## What actually happened
The application panics with the following:
```
panicked at 'assertion failed: `(left == right)`
left: `true`,
right: `false`: cannot recursively acquire mutex',
```
and upon further examination of the stack trace it turns out to be the failure described by #1924
| True | [wasm] Attempting to get an EventWriter for an unregistered event type panics with an unhelpful message - ## Bevy version
0.5.0
## Operating system & version
wasm
## What you did
Create a system like so:
```
struct Event;
fn system(mut events: EventWriter<Event>) {}
```
Set up the app, but do not register the event
```
App::build()
.with_system(system.system())
.run();
```
## What you expected to happen
The application is misconfigured so I expect this to panic, and ideally the message for the panic would explain that a system attempted to fetch an `EventWriter` for an unregistered event type.
## What actually happened
The application panics with the following:
```
panicked at 'assertion failed: `(left == right)`
left: `true`,
right: `false`: cannot recursively acquire mutex',
```
and upon further examination of the stack trace it turns out to be the failure described by #1924
| usab | attempting to get an eventwriter for an unregistered event type panics with an unhelpful message bevy version operating system version wasm what you did create a system like so struct event fn system mut events eventwriter set up the app but do not register the event app build with system system system run what you expected to happen the application is misconfigured so i expect this to panic and ideally the message for the panic would explain that a system attempted to fetch an eventwriter for an unregistered event type what actually happened the application panics with the following panicked at assertion failed left right left true right false cannot recursively acquire mutex and upon further examination of the stack trace it turns out to be the failure described by | 1 |
45,648 | 24,150,439,203 | IssuesEvent | 2022-09-21 23:43:26 | dolthub/dolt | https://api.github.com/repos/dolthub/dolt | closed | `dolt fetch upstream main` fails on VPS with 1GB RAM | performance cli | ## Reproduce Instructions
These work on a computer with sufficient resources, but fail on a computer with very little RAM (like a VPS).
The following is a dump of the `history` command for my ease.
```bash
1079 dolt clone nacho53/us-housing-prices-v2
1080 dolt remote add upstream dolthub/us-housing-prices-v2
1081 ls
1082 cd us-housing-prices-v2/
1083 ls
1084 dolt remote add upstream dolthub/us-housing-prices-v2
1085 dolt fetch upstream
1086 df -h
1087 free -h
1088 dolt fetch upstream
1094 echo dolt sucks on low memory - open ticket later
```
## Result
```
~/us-housing-prices-v2$ dolt fetch upstream
Downloaded 19,955 chunks, 70 MB @ 1.18 MB/s.
Killed
```
## Comments
I know this is an edge case, running dolt on such a low resource system, but it has sufficient swap space available, so I don't feel as though it should be killed in such a case.
## System
* Ubuntu 20.04.05 LTS
* RAM: 1 GiB
* Swap: 4 GiB
* Cores: 1
* Dolt Version: 0.41.4
| True | `dolt fetch upstream main` fails on VPS with 1GB RAM - ## Reproduce Instructions
These work on a computer with sufficient resources, but fail on a computer with very little RAM (like a VPS).
The following is a dump of the `history` command for my ease.
```bash
1079 dolt clone nacho53/us-housing-prices-v2
1080 dolt remote add upstream dolthub/us-housing-prices-v2
1081 ls
1082 cd us-housing-prices-v2/
1083 ls
1084 dolt remote add upstream dolthub/us-housing-prices-v2
1085 dolt fetch upstream
1086 df -h
1087 free -h
1088 dolt fetch upstream
1094 echo dolt sucks on low memory - open ticket later
```
## Result
```
~/us-housing-prices-v2$ dolt fetch upstream
Downloaded 19,955 chunks, 70 MB @ 1.18 MB/s.
Killed
```
## Comments
I know this is an edge case, running dolt on such a low resource system, but it has sufficient swap space available, so I don't feel as though it should be killed in such a case.
## System
* Ubuntu 20.04.05 LTS
* RAM: 1 GiB
* Swap: 4 GiB
* Cores: 1
* Dolt Version: 0.41.4
| non_usab | dolt fetch upstream main fails on vps with ram reproduce instructions these work on a computer with sufficient resources but fail on a computer with very little ram like a vps the following is a dump of the history command for my ease bash dolt clone us housing prices dolt remote add upstream dolthub us housing prices ls cd us housing prices ls dolt remote add upstream dolthub us housing prices dolt fetch upstream df h free h dolt fetch upstream echo dolt sucks on low memory open ticket later result us housing prices dolt fetch upstream downloaded chunks mb mb s killed comments i know this is an edge case running dolt on such a low resource system but it has sufficient swap space available so i don t feel as though it should be killed in such a case system ubuntu lts ram gib swap gib cores dolt version | 0 |
264,185 | 20,009,189,777 | IssuesEvent | 2022-02-01 02:46:39 | EdwarCastellanos5120/proyectos-mates | https://api.github.com/repos/EdwarCastellanos5120/proyectos-mates | closed | Problema con el README | bug documentation | # Comentario 1
El README ES MUY CORTO
# Comentario 2
El archivo de Matemáticas es modificable | 1.0 | Problema con el README - # Comentario 1
El README ES MUY CORTO
# Comentario 2
El archivo de Matemáticas es modificable | non_usab | problema con el readme comentario el readme es muy corto comentario el archivo de matemáticas es modificable | 0 |
781,371 | 27,435,308,886 | IssuesEvent | 2023-03-02 06:47:58 | brave/brave-browser | https://api.github.com/repos/brave/brave-browser | closed | Open bookmark section when the bottom navigation button is pressed for long time | feature/bookmarks priority/P3 feature-request OS/Android | ## Description
I frequently need to bookmark sites from my mobile in different folders and subfolders, but every time when I need to change the bookmark folder or subfolder I need to press the edit bookmark button and then select the folder.
So I would like to have a long-press feature on the bottom navigation bookmark button that would open a bookmark section where I can change and select folders, I have an image attached of the **" bottom navigation bookmark button"**
The expected result should look like the following
https://user-images.githubusercontent.com/70164257/114224878-a4b13b80-993f-11eb-92c5-28704483062f.mp4
## Device details
- Device type: Samsung S20 FE
- Android version: 11
## Brave version
-Brave:1.22.71
-Chromium: 89.0.4389.114
| 1.0 | Open bookmark section when the bottom navigation button is pressed for long time - ## Description
I frequently need to bookmark sites from my mobile in different folders and subfolders, but every time when I need to change the bookmark folder or subfolder I need to press the edit bookmark button and then select the folder.
So I would like to have a long-press feature on the bottom navigation bookmark button that would open a bookmark section where I can change and select folders, I have an image attached of the **" bottom navigation bookmark button"**
The expected result should look like the following
https://user-images.githubusercontent.com/70164257/114224878-a4b13b80-993f-11eb-92c5-28704483062f.mp4
## Device details
- Device type: Samsung S20 FE
- Android version: 11
## Brave version
-Brave:1.22.71
-Chromium: 89.0.4389.114
| non_usab | open bookmark section when the bottom navigation button is pressed for long time description i frequently need to bookmark sites from my mobile in different folders and subfolders but every time when i need to change the bookmark folder or subfolder i need to press the edit bookmark button and then select the folder so i would like to have a long press feature on the bottom navigation bookmark button that would open a bookmark section where i can change and select folders i have an image attached of the bottom navigation bookmark button the expected result should look like the following device details device type samsung fe android version brave version brave chromium | 0 |
94,003 | 8,461,739,954 | IssuesEvent | 2018-10-22 22:59:13 | red/red | https://api.github.com/repos/red/red | closed | DRAW re-orders BOX coordinates | status.built status.tested type.bug | **Describe the bug**
`DRAW` re-orders of BOX coordinates and modifies its block argument.
**To Reproduce**
```
>> view [base 100x100 draw x: [box 10x0 20x10 box 20x0 10x10]]
>> x
== [box 10x0 20x10 box 10x0 20x10]
>> view [base 100x100 green draw x: [box 20x20 10x10 box 15x5 0x10]]
>> x
== [box 10x10 20x20 box 0x5 15x10]
```
**Expected behavior**
Draw block should not be modified
**Platform version:**
```
RED: [ branch: "master" tag: #v0.6.3 ahead: 1068 date: 7-Oct-2018/2:40:37 commit: #b4e7fff72801c9e7f563c11d6d722685ad8e88d9 ]
PLATFORM: [ name: "Windows 10" OS: 'Windows arch: 'x86-64 version: 10.0.0 build: 17134 ]
``` | 1.0 | DRAW re-orders BOX coordinates - **Describe the bug**
`DRAW` re-orders of BOX coordinates and modifies its block argument.
**To Reproduce**
```
>> view [base 100x100 draw x: [box 10x0 20x10 box 20x0 10x10]]
>> x
== [box 10x0 20x10 box 10x0 20x10]
>> view [base 100x100 green draw x: [box 20x20 10x10 box 15x5 0x10]]
>> x
== [box 10x10 20x20 box 0x5 15x10]
```
**Expected behavior**
Draw block should not be modified
**Platform version:**
```
RED: [ branch: "master" tag: #v0.6.3 ahead: 1068 date: 7-Oct-2018/2:40:37 commit: #b4e7fff72801c9e7f563c11d6d722685ad8e88d9 ]
PLATFORM: [ name: "Windows 10" OS: 'Windows arch: 'x86-64 version: 10.0.0 build: 17134 ]
``` | non_usab | draw re orders box coordinates describe the bug draw re orders of box coordinates and modifies its block argument to reproduce view x view x expected behavior draw block should not be modified platform version red platform | 0 |
184,625 | 14,985,853,831 | IssuesEvent | 2021-01-28 20:29:07 | corrados/jamulus | https://api.github.com/repos/corrados/jamulus | closed | Status of Jamulus integration in Linux distributions | documentation | This issue is basically just a list of URLs which relate to possible integrations of Jamulus in Linux distributions.
Several years ago, there was an attempt to include Jamulus in Redhat:
https://bugzilla.redhat.com/show_bug.cgi?id=1118963
The CONFIG options "noupcasename" and "opus_shared_lib" were a result of it.
More recently, mirabilos did some work for including Jamulus in Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958146
We also have Jamulus Issues related to that, e.g., https://github.com/corrados/jamulus/issues/100
It seems that there is a Jamulus package in OpenSuse available:
https://software.opensuse.org/package/Jamulus
If you know of other Linux distributions or have updated informations, please post them here.
<a href="https://repology.org/project/jamulus/versions">
<img src="https://repology.org/badge/vertical-allrepos/jamulus.svg" alt="Packaging status">
</a> | 1.0 | Status of Jamulus integration in Linux distributions - This issue is basically just a list of URLs which relate to possible integrations of Jamulus in Linux distributions.
Several years ago, there was an attempt to include Jamulus in Redhat:
https://bugzilla.redhat.com/show_bug.cgi?id=1118963
The CONFIG options "noupcasename" and "opus_shared_lib" were a result of it.
More recently, mirabilos did some work for including Jamulus in Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958146
We also have Jamulus Issues related to that, e.g., https://github.com/corrados/jamulus/issues/100
It seems that there is a Jamulus package in OpenSuse available:
https://software.opensuse.org/package/Jamulus
If you know of other Linux distributions or have updated informations, please post them here.
<a href="https://repology.org/project/jamulus/versions">
<img src="https://repology.org/badge/vertical-allrepos/jamulus.svg" alt="Packaging status">
</a> | non_usab | status of jamulus integration in linux distributions this issue is basically just a list of urls which relate to possible integrations of jamulus in linux distributions several years ago there was an attempt to include jamulus in redhat the config options noupcasename and opus shared lib were a result of it more recently mirabilos did some work for including jamulus in debian we also have jamulus issues related to that e g it seems that there is a jamulus package in opensuse available if you know of other linux distributions or have updated informations please post them here a href | 0 |
576,673 | 17,091,867,642 | IssuesEvent | 2021-07-08 18:37:40 | buddyboss/buddyboss-platform | https://api.github.com/repos/buddyboss/buddyboss-platform | opened | Zoom notice show when update the group from backend. | bug priority: high | **Describe the bug**
When we update the group details on the backend and refresh the group on the frontend that time shows the "Group Zoom settings were successfully updated." Notice.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to any group
2. edit the group details and save the group.
3. reload the group page on the front end.
4. See error about the showing the notice.
**Expected behavior**
Zoom Notice should not show on the front end without update any details.
**Screenshots**
https://www.loom.com/share/5988a37bfa304dbeab1884638dbacfcf
**Environment**
dev site: https://dev-meet.flywheelsites.com/
| 1.0 | Zoom notice show when update the group from backend. - **Describe the bug**
When we update the group details on the backend and refresh the group on the frontend that time shows the "Group Zoom settings were successfully updated." Notice.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to any group
2. edit the group details and save the group.
3. reload the group page on the front end.
4. See error about the showing the notice.
**Expected behavior**
Zoom Notice should not show on the front end without update any details.
**Screenshots**
https://www.loom.com/share/5988a37bfa304dbeab1884638dbacfcf
**Environment**
dev site: https://dev-meet.flywheelsites.com/
| non_usab | zoom notice show when update the group from backend describe the bug when we update the group details on the backend and refresh the group on the frontend that time shows the group zoom settings were successfully updated notice to reproduce steps to reproduce the behavior go to any group edit the group details and save the group reload the group page on the front end see error about the showing the notice expected behavior zoom notice should not show on the front end without update any details screenshots environment dev site | 0 |
18,652 | 13,134,562,914 | IssuesEvent | 2020-08-06 23:52:40 | microsoft/vscode-azurearmtools | https://api.github.com/repos/microsoft/vscode-azurearmtools | reopened | STORY: Refactorings | P1 story spec story: usability | # Parameters/variables (P1)
- [ ] Extract to variable #515
- [ ] Extract to parameter #515
- [ ] Parameter -> variable
- [ ] Variable -> parameter
# Resources (P2)
Related: STORY: Show dependencies between resources #833
- [ ] Drag resources up/down in the tree, or move up/down in the template editor
- [ ] Sort by dependencies
- [ ] Extract child resource from nested under parent to top level and vice versa
- [ ] Update api versions for all resources of a particular type, or maybe find/replace all resources with the same type and apiversion. e.g. Change all storage accounts to this api version.
# resourceId
- [ ] convert to/from full resourceId vs short references
# Nested/linked templates (P3)
- [ ] Nested template <-> linked template
- [ ] Inner-scoped template <-> outer-scoped template
- [ ] Extract resources to nested/linked template (requires picking up referenced vars/params)
- [ ] Inline nested/linked template into the template
# User functions (P4)
- [ ] Extract to user function
# apiVersions
- [ ] Auto-fix: (change to newer api version that we support, or newest, or first newer version that we support)
- [ ] Auto-fix for all apiversions?
# Blue Sky thinking
- [ ] "COPY-ize" a resource(s), etc. - convert single instance resource(s) into multiple instances
- [ ] Can we do anything to help with resource dependencies? | True | STORY: Refactorings - # Parameters/variables (P1)
- [ ] Extract to variable #515
- [ ] Extract to parameter #515
- [ ] Parameter -> variable
- [ ] Variable -> parameter
# Resources (P2)
Related: STORY: Show dependencies between resources #833
- [ ] Drag resources up/down in the tree, or move up/down in the template editor
- [ ] Sort by dependencies
- [ ] Extract child resource from nested under parent to top level and vice versa
- [ ] Update api versions for all resources of a particular type, or maybe find/replace all resources with the same type and apiversion. e.g. Change all storage accounts to this api version.
# resourceId
- [ ] convert to/from full resourceId vs short references
# Nested/linked templates (P3)
- [ ] Nested template <-> linked template
- [ ] Inner-scoped template <-> outer-scoped template
- [ ] Extract resources to nested/linked template (requires picking up referenced vars/params)
- [ ] Inline nested/linked template into the template
# User functions (P4)
- [ ] Extract to user function
# apiVersions
- [ ] Auto-fix: (change to newer api version that we support, or newest, or first newer version that we support)
- [ ] Auto-fix for all apiversions?
# Blue Sky thinking
- [ ] "COPY-ize" a resource(s), etc. - convert single instance resource(s) into multiple instances
- [ ] Can we do anything to help with resource dependencies? | usab | story refactorings parameters variables extract to variable extract to parameter parameter variable variable parameter resources related story show dependencies between resources drag resources up down in the tree or move up down in the template editor sort by dependencies extract child resource from nested under parent to top level and vice versa update api versions for all resources of a particular type or maybe find replace all resources with the same type and apiversion e g change all storage accounts to this api version resourceid convert to from full resourceid vs short references nested linked templates nested template linked template inner scoped template outer scoped template extract resources to nested linked template requires picking up referenced vars params inline nested linked template into the template user functions extract to user function apiversions auto fix change to newer api version that we support or newest or first newer version that we support auto fix for all apiversions blue sky thinking copy ize a resource s etc convert single instance resource s into multiple instances can we do anything to help with resource dependencies | 1 |
8,328 | 5,624,405,285 | IssuesEvent | 2017-04-04 16:58:07 | zaproxy/zaproxy | https://api.github.com/repos/zaproxy/zaproxy | opened | Enhancement: Additional Global Exclude default patterns | enhancement Usability | Food for thought ... re: <sub>https://github.com/zaproxy/zaproxy/blob/efce236ddf6f89516de6cd0592e22372149e0e05/src/org/zaproxy/zap/extension/globalexcludeurl/GlobalExcludeURLParam.java#L63</sub>
`^https?://detectportal\.firefox\.com.*$` Firefox mechanism for detecting captive portals.
`^https?://www\.google-analytics\.com.*$` Google analytics....nuff said.
`^https?://ciscobinary\.openh264\.org.*$` Firefox codec download (https://support.mozilla.org/t5/Firefox/Where-is-a-check-that-http-ciscobinary-openh264-org-openh264-is/m-p/1316497#M1005892)
`^https?://fonts.*$` This might be too generic, I built it broadly after seeing fonts.googleapis.com and fonts.gstatic.com used...
| True | Enhancement: Additional Global Exclude default patterns - Food for thought ... re: <sub>https://github.com/zaproxy/zaproxy/blob/efce236ddf6f89516de6cd0592e22372149e0e05/src/org/zaproxy/zap/extension/globalexcludeurl/GlobalExcludeURLParam.java#L63</sub>
`^https?://detectportal\.firefox\.com.*$` Firefox mechanism for detecting captive portals.
`^https?://www\.google-analytics\.com.*$` Google analytics....nuff said.
`^https?://ciscobinary\.openh264\.org.*$` Firefox codec download (https://support.mozilla.org/t5/Firefox/Where-is-a-check-that-http-ciscobinary-openh264-org-openh264-is/m-p/1316497#M1005892)
`^https?://fonts.*$` This might be too generic, I built it broadly after seeing fonts.googleapis.com and fonts.gstatic.com used...
| usab | enhancement additional global exclude default patterns food for thought re https detectportal firefox com firefox mechanism for detecting captive portals https www google analytics com google analytics nuff said https ciscobinary org firefox codec download https fonts this might be too generic i built it broadly after seeing fonts googleapis com and fonts gstatic com used | 1 |
18,155 | 12,603,604,841 | IssuesEvent | 2020-06-11 13:44:50 | kubernetes/kubernetes | https://api.github.com/repos/kubernetes/kubernetes | closed | high priority pods be evicted when diskPressure in k8s 1.15 | kind/bug lifecycle/rotten sig/apps sig/cluster-lifecycle sig/node sig/usability | My k8s version is 1.15.6.
I want my high priority pods won't be evicted when diskPressure.
I found that PR: https://github.com/kubernetes/kubernetes/pull/87144 , high priority pods should not be evicted when diskPressure.
I won't update to 1.17 temporarily.
so can patch this PR to k8s 1.15?
**What happened**:
high priority pods won't be evicted when diskPressure
**What you expected to happen**:
**How to reproduce it (as minimally and precisely as possible)**:
**Anything else we need to know?**:
**Environment**:
- Kubernetes version (use `kubectl version`): My k8s version is 1.15.6.
- Cloud provider or hardware configuration:
- OS (e.g: `cat /etc/os-release`):
- Kernel (e.g. `uname -a`):
- Install tools:
- Network plugin and version (if this is a network-related bug):
- Others:
| True | high priority pods be evicted when diskPressure in k8s 1.15 - My k8s version is 1.15.6.
I want my high priority pods won't be evicted when diskPressure.
I found that PR: https://github.com/kubernetes/kubernetes/pull/87144 , high priority pods should not be evicted when diskPressure.
I won't update to 1.17 temporarily.
so can patch this PR to k8s 1.15?
**What happened**:
high priority pods won't be evicted when diskPressure
**What you expected to happen**:
**How to reproduce it (as minimally and precisely as possible)**:
**Anything else we need to know?**:
**Environment**:
- Kubernetes version (use `kubectl version`): My k8s version is 1.15.6.
- Cloud provider or hardware configuration:
- OS (e.g: `cat /etc/os-release`):
- Kernel (e.g. `uname -a`):
- Install tools:
- Network plugin and version (if this is a network-related bug):
- Others:
| usab | high priority pods be evicted when diskpressure in my version is i want my high priority pods won t be evicted when diskpressure i found that pr high priority pods should not be evicted when diskpressure i won t update to temporarily so can patch this pr to what happened high priority pods won t be evicted when diskpressure what you expected to happen how to reproduce it as minimally and precisely as possible anything else we need to know environment kubernetes version use kubectl version my version is cloud provider or hardware configuration os e g cat etc os release kernel e g uname a install tools network plugin and version if this is a network related bug others | 1 |
53,080 | 3,035,197,716 | IssuesEvent | 2015-08-06 00:43:43 | INN/Largo | https://api.github.com/repos/INN/Largo | closed | Create filter for LMP arguments | good for beginners in progress priority: normal type: improvement | Chicago Catalyst redefines the `largo_load_more_posts` function [in order to limit the returned posts to a specific prominence term](https://bitbucket.org/projectlargo/theme-chicago-catalyst/src/963dfd5b2648743a48b80cf0f413a79043e0db92/functions.php?at=master#functions.php-203).
We should probably make [`$args`](https://github.com/INN/Largo/blob/master/inc/ajax-functions.php#L88-L93) filterable before the query is run. | 1.0 | Create filter for LMP arguments - Chicago Catalyst redefines the `largo_load_more_posts` function [in order to limit the returned posts to a specific prominence term](https://bitbucket.org/projectlargo/theme-chicago-catalyst/src/963dfd5b2648743a48b80cf0f413a79043e0db92/functions.php?at=master#functions.php-203).
We should probably make [`$args`](https://github.com/INN/Largo/blob/master/inc/ajax-functions.php#L88-L93) filterable before the query is run. | non_usab | create filter for lmp arguments chicago catalyst redefines the largo load more posts function we should probably make filterable before the query is run | 0 |
152,077 | 5,832,515,051 | IssuesEvent | 2017-05-08 22:02:00 | openshift/origin | https://api.github.com/repos/openshift/origin | closed | Centos PaaS RPM packages for openshift origin v1.5.0 | component/install kind/enhancement priority/P2 | Would it be possible to build RPM packages for Openshift Origin v1.5.0 and release them on the Centos PaaS repository?
In the experimental repository at https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin/ I can see the following packages:
- origin-1.5.0-0.4.el7.x86_64.rpm 2017-02-08 18:08 35M
- origin-1.5.0-0.7.rc1.x86_64.rpm 2017-04-12 18:14 35M
But I suspect that the `origin-1.5.0-0.4.el7.x86_64.rpm` is not the stable release because the package was released on "2017-02-08 18:08" (according to the directory listing) while the [official release](https://github.com/openshift/origin/releases/tag/v1.5.0) is dated April 21st.
I can install packages from the testing repository at buildlogs.centos.org before official release.
Thank you in advance @tdawson | 1.0 | Centos PaaS RPM packages for openshift origin v1.5.0 - Would it be possible to build RPM packages for Openshift Origin v1.5.0 and release them on the Centos PaaS repository?
In the experimental repository at https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin/ I can see the following packages:
- origin-1.5.0-0.4.el7.x86_64.rpm 2017-02-08 18:08 35M
- origin-1.5.0-0.7.rc1.x86_64.rpm 2017-04-12 18:14 35M
But I suspect that the `origin-1.5.0-0.4.el7.x86_64.rpm` is not the stable release because the package was released on "2017-02-08 18:08" (according to the directory listing) while the [official release](https://github.com/openshift/origin/releases/tag/v1.5.0) is dated April 21st.
I can install packages from the testing repository at buildlogs.centos.org before official release.
Thank you in advance @tdawson | non_usab | centos paas rpm packages for openshift origin would it be possible to build rpm packages for openshift origin and release them on the centos paas repository in the experimental repository at i can see the following packages origin rpm origin rpm but i suspect that the origin rpm is not the stable release because the package was released on according to the directory listing while the is dated april i can install packages from the testing repository at buildlogs centos org before official release thank you in advance tdawson | 0 |
332,439 | 24,343,102,511 | IssuesEvent | 2022-10-02 00:19:54 | jeffreycharters/station | https://api.github.com/repos/jeffreycharters/station | closed | Update contributing.md file | documentation enhancement hacktoberfest | I know that the contributing.md file already does a great job listing this project's essence. I thought we could update it with steps on how to help new contributors do stuff like fork, clone, commit their changes, and push back to this repo.
Should in case this issue is approved, I would like to be assigned to it. | 1.0 | Update contributing.md file - I know that the contributing.md file already does a great job listing this project's essence. I thought we could update it with steps on how to help new contributors do stuff like fork, clone, commit their changes, and push back to this repo.
Should in case this issue is approved, I would like to be assigned to it. | non_usab | update contributing md file i know that the contributing md file already does a great job listing this project s essence i thought we could update it with steps on how to help new contributors do stuff like fork clone commit their changes and push back to this repo should in case this issue is approved i would like to be assigned to it | 0 |
91,361 | 26,369,093,084 | IssuesEvent | 2023-01-11 19:02:27 | tarantool/tarantool | https://api.github.com/repos/tarantool/tarantool | closed | clang-15: build fails with 'Unable to get thread stack' | build 1.10 | The build works with clang 14:
```sh
CC=clang-14 CXX=clang++-14 cmake . \
-DCMAKE_BUILD_TYPE=RelWithDebInfo \
-DENABLE_BACKTRACE=ON \
-DENABLE_DIST=ON \
-DENABLE_FEEDBACK_DAEMON=OFF \
-DENABLE_BUNDLED_LIBCURL=OFF && \
make -j
```
With clang 14 it shows the following cmake check results around pthread:
```
-- Looking for pthread_np.h
-- Looking for pthread_np.h - not found
-- Performing Test HAVE_PTHREAD_SETNAME_NP
-- Performing Test HAVE_PTHREAD_SETNAME_NP - Success
-- Performing Test HAVE_PTHREAD_SETNAME_NP_1
-- Performing Test HAVE_PTHREAD_SETNAME_NP_1 - Failed
-- Performing Test HAVE_PTHREAD_SET_NAME_NP
-- Performing Test HAVE_PTHREAD_SET_NAME_NP - Failed
-- Performing Test HAVE_PTHREAD_GETATTR_NP
-- Performing Test HAVE_PTHREAD_GETATTR_NP - Success
-- Performing Test HAVE_PTHREAD_STACKSEG_NP
-- Performing Test HAVE_PTHREAD_STACKSEG_NP - Failed
-- Performing Test HAVE_PTHREAD_ATTR_GET_NP
-- Performing Test HAVE_PTHREAD_ATTR_GET_NP - Failed
-- Performing Test HAVE_PTHREAD_GET_STACKSIZE_NP
-- Performing Test HAVE_PTHREAD_GET_STACKSIZE_NP - Failed
-- Performing Test HAVE_PTHREAD_GET_STACKADDR_NP
-- Performing Test HAVE_PTHREAD_GET_STACKADDR_NP - Failed
```
However the same on clang 15:
```sh
CC=clang-15 CXX=clang++-15 cmake . \
-DCMAKE_BUILD_TYPE=RelWithDebInfo \
-DENABLE_BACKTRACE=ON \
-DENABLE_DIST=ON \
-DENABLE_FEEDBACK_DAEMON=OFF \
-DENABLE_BUNDLED_LIBCURL=OFF && \
make -j
```
Gives 'all failed' for the pthread related checks.
```
-- Looking for pthread_np.h
-- Looking for pthread_np.h - not found
-- Performing Test HAVE_PTHREAD_SETNAME_NP
-- Performing Test HAVE_PTHREAD_SETNAME_NP - Failed
-- Performing Test HAVE_PTHREAD_SETNAME_NP_1
-- Performing Test HAVE_PTHREAD_SETNAME_NP_1 - Failed
-- Performing Test HAVE_PTHREAD_SET_NAME_NP
-- Performing Test HAVE_PTHREAD_SET_NAME_NP - Failed
-- Performing Test HAVE_PTHREAD_GETATTR_NP
-- Performing Test HAVE_PTHREAD_GETATTR_NP - Failed
-- Performing Test HAVE_PTHREAD_STACKSEG_NP
-- Performing Test HAVE_PTHREAD_STACKSEG_NP - Failed
-- Performing Test HAVE_PTHREAD_ATTR_GET_NP
-- Performing Test HAVE_PTHREAD_ATTR_GET_NP - Failed
-- Performing Test HAVE_PTHREAD_GET_STACKSIZE_NP
-- Performing Test HAVE_PTHREAD_GET_STACKSIZE_NP - Failed
-- Performing Test HAVE_PTHREAD_GET_STACKADDR_NP
-- Performing Test HAVE_PTHREAD_GET_STACKADDR_NP - Failed
```
And the build fails later.
```c
[ 9%] Building C object src/lib/core/CMakeFiles/core.dir/diag.c.o
In file included from /home/alex/p/tarantool-meta/r/t-5/src/lib/core/diag.c:32:
In file included from /home/alex/p/tarantool-meta/r/t-5/src/lib/core/fiber.h:37:
/home/alex/p/tarantool-meta/r/t-5/src/tt_pthread.h:377:2: error: Unable to get thread stack
#error Unable to get thread stack
^
/home/alex/p/tarantool-meta/r/t-5/src/tt_pthread.h:340:36: warning: unused parameter 'thread' [-Wunused-parameter]
tt_pthread_attr_getstack(pthread_t thread, void **stackaddr, size_t *stacksize)
^
/home/alex/p/tarantool-meta/r/t-5/src/tt_pthread.h:340:51: warning: unused parameter 'stackaddr' [-Wunused-parameter]
tt_pthread_attr_getstack(pthread_t thread, void **stackaddr, size_t *stacksize)
^
/home/alex/p/tarantool-meta/r/t-5/src/tt_pthread.h:340:70: warning: unused parameter 'stacksize' [-Wunused-parameter]
tt_pthread_attr_getstack(pthread_t thread, void **stackaddr, size_t *stacksize)
^
3 warnings and 1 error generated.
```
The reason is inaccurate CMake checks code. From `CMakeFiles/CMakeError.log`:
```c
/usr/lib/llvm/15/bin/clang-15 -DHAVE_PTHREAD_SETNAME_NP -D_DARWIN_C_SOURCE -D_GNU_SOURCE -fexceptions -funwind-tables -fasynchronous-unwind-tables -fno-common -fopenmp -msse2 -pedantic-errors -MD -MT CMakeFiles/cmTC_6822f.dir/src.c.o -MF CMakeFiles/cmTC_6822f.dir/src.c.o.d -o CMakeFiles/cmTC_6822f.dir/src.c.o -c /home/alex/p/tarantool-meta/r/t-5/CMakeFiles/CMakeScratch/TryCompile-78KaOK/src.c
/home/alex/p/tarantool-meta/r/t-5/CMakeFiles/CMakeScratch/TryCompile-78KaOK/src.c:4:17: error: a function declaration without a prototype is deprecated in all versions of C [-Werror,-Wstrict-prototypes]
int main() { pthread_setname_np(pthread_self(), ""); }
^
void
1 error generated.
``` | 1.0 | clang-15: build fails with 'Unable to get thread stack' - The build works with clang 14:
```sh
CC=clang-14 CXX=clang++-14 cmake . \
-DCMAKE_BUILD_TYPE=RelWithDebInfo \
-DENABLE_BACKTRACE=ON \
-DENABLE_DIST=ON \
-DENABLE_FEEDBACK_DAEMON=OFF \
-DENABLE_BUNDLED_LIBCURL=OFF && \
make -j
```
With clang 14 it shows the following cmake check results around pthread:
```
-- Looking for pthread_np.h
-- Looking for pthread_np.h - not found
-- Performing Test HAVE_PTHREAD_SETNAME_NP
-- Performing Test HAVE_PTHREAD_SETNAME_NP - Success
-- Performing Test HAVE_PTHREAD_SETNAME_NP_1
-- Performing Test HAVE_PTHREAD_SETNAME_NP_1 - Failed
-- Performing Test HAVE_PTHREAD_SET_NAME_NP
-- Performing Test HAVE_PTHREAD_SET_NAME_NP - Failed
-- Performing Test HAVE_PTHREAD_GETATTR_NP
-- Performing Test HAVE_PTHREAD_GETATTR_NP - Success
-- Performing Test HAVE_PTHREAD_STACKSEG_NP
-- Performing Test HAVE_PTHREAD_STACKSEG_NP - Failed
-- Performing Test HAVE_PTHREAD_ATTR_GET_NP
-- Performing Test HAVE_PTHREAD_ATTR_GET_NP - Failed
-- Performing Test HAVE_PTHREAD_GET_STACKSIZE_NP
-- Performing Test HAVE_PTHREAD_GET_STACKSIZE_NP - Failed
-- Performing Test HAVE_PTHREAD_GET_STACKADDR_NP
-- Performing Test HAVE_PTHREAD_GET_STACKADDR_NP - Failed
```
However the same on clang 15:
```sh
CC=clang-15 CXX=clang++-15 cmake . \
-DCMAKE_BUILD_TYPE=RelWithDebInfo \
-DENABLE_BACKTRACE=ON \
-DENABLE_DIST=ON \
-DENABLE_FEEDBACK_DAEMON=OFF \
-DENABLE_BUNDLED_LIBCURL=OFF && \
make -j
```
Gives 'all failed' for the pthread related checks.
```
-- Looking for pthread_np.h
-- Looking for pthread_np.h - not found
-- Performing Test HAVE_PTHREAD_SETNAME_NP
-- Performing Test HAVE_PTHREAD_SETNAME_NP - Failed
-- Performing Test HAVE_PTHREAD_SETNAME_NP_1
-- Performing Test HAVE_PTHREAD_SETNAME_NP_1 - Failed
-- Performing Test HAVE_PTHREAD_SET_NAME_NP
-- Performing Test HAVE_PTHREAD_SET_NAME_NP - Failed
-- Performing Test HAVE_PTHREAD_GETATTR_NP
-- Performing Test HAVE_PTHREAD_GETATTR_NP - Failed
-- Performing Test HAVE_PTHREAD_STACKSEG_NP
-- Performing Test HAVE_PTHREAD_STACKSEG_NP - Failed
-- Performing Test HAVE_PTHREAD_ATTR_GET_NP
-- Performing Test HAVE_PTHREAD_ATTR_GET_NP - Failed
-- Performing Test HAVE_PTHREAD_GET_STACKSIZE_NP
-- Performing Test HAVE_PTHREAD_GET_STACKSIZE_NP - Failed
-- Performing Test HAVE_PTHREAD_GET_STACKADDR_NP
-- Performing Test HAVE_PTHREAD_GET_STACKADDR_NP - Failed
```
And the build fails later.
```c
[ 9%] Building C object src/lib/core/CMakeFiles/core.dir/diag.c.o
In file included from /home/alex/p/tarantool-meta/r/t-5/src/lib/core/diag.c:32:
In file included from /home/alex/p/tarantool-meta/r/t-5/src/lib/core/fiber.h:37:
/home/alex/p/tarantool-meta/r/t-5/src/tt_pthread.h:377:2: error: Unable to get thread stack
#error Unable to get thread stack
^
/home/alex/p/tarantool-meta/r/t-5/src/tt_pthread.h:340:36: warning: unused parameter 'thread' [-Wunused-parameter]
tt_pthread_attr_getstack(pthread_t thread, void **stackaddr, size_t *stacksize)
^
/home/alex/p/tarantool-meta/r/t-5/src/tt_pthread.h:340:51: warning: unused parameter 'stackaddr' [-Wunused-parameter]
tt_pthread_attr_getstack(pthread_t thread, void **stackaddr, size_t *stacksize)
^
/home/alex/p/tarantool-meta/r/t-5/src/tt_pthread.h:340:70: warning: unused parameter 'stacksize' [-Wunused-parameter]
tt_pthread_attr_getstack(pthread_t thread, void **stackaddr, size_t *stacksize)
^
3 warnings and 1 error generated.
```
The reason is inaccurate CMake checks code. From `CMakeFiles/CMakeError.log`:
```c
/usr/lib/llvm/15/bin/clang-15 -DHAVE_PTHREAD_SETNAME_NP -D_DARWIN_C_SOURCE -D_GNU_SOURCE -fexceptions -funwind-tables -fasynchronous-unwind-tables -fno-common -fopenmp -msse2 -pedantic-errors -MD -MT CMakeFiles/cmTC_6822f.dir/src.c.o -MF CMakeFiles/cmTC_6822f.dir/src.c.o.d -o CMakeFiles/cmTC_6822f.dir/src.c.o -c /home/alex/p/tarantool-meta/r/t-5/CMakeFiles/CMakeScratch/TryCompile-78KaOK/src.c
/home/alex/p/tarantool-meta/r/t-5/CMakeFiles/CMakeScratch/TryCompile-78KaOK/src.c:4:17: error: a function declaration without a prototype is deprecated in all versions of C [-Werror,-Wstrict-prototypes]
int main() { pthread_setname_np(pthread_self(), ""); }
^
void
1 error generated.
``` | non_usab | clang build fails with unable to get thread stack the build works with clang sh cc clang cxx clang cmake dcmake build type relwithdebinfo denable backtrace on denable dist on denable feedback daemon off denable bundled libcurl off make j with clang it shows the following cmake check results around pthread looking for pthread np h looking for pthread np h not found performing test have pthread setname np performing test have pthread setname np success performing test have pthread setname np performing test have pthread setname np failed performing test have pthread set name np performing test have pthread set name np failed performing test have pthread getattr np performing test have pthread getattr np success performing test have pthread stackseg np performing test have pthread stackseg np failed performing test have pthread attr get np performing test have pthread attr get np failed performing test have pthread get stacksize np performing test have pthread get stacksize np failed performing test have pthread get stackaddr np performing test have pthread get stackaddr np failed however the same on clang sh cc clang cxx clang cmake dcmake build type relwithdebinfo denable backtrace on denable dist on denable feedback daemon off denable bundled libcurl off make j gives all failed for the pthread related checks looking for pthread np h looking for pthread np h not found performing test have pthread setname np performing test have pthread setname np failed performing test have pthread setname np performing test have pthread setname np failed performing test have pthread set name np performing test have pthread set name np failed performing test have pthread getattr np performing test have pthread getattr np failed performing test have pthread stackseg np performing test have pthread stackseg np failed performing test have pthread attr get np performing test have pthread attr get np failed performing test have pthread get stacksize np performing test have pthread get stacksize np failed performing test have pthread get stackaddr np performing test have pthread get stackaddr np failed and the build fails later c building c object src lib core cmakefiles core dir diag c o in file included from home alex p tarantool meta r t src lib core diag c in file included from home alex p tarantool meta r t src lib core fiber h home alex p tarantool meta r t src tt pthread h error unable to get thread stack error unable to get thread stack home alex p tarantool meta r t src tt pthread h warning unused parameter thread tt pthread attr getstack pthread t thread void stackaddr size t stacksize home alex p tarantool meta r t src tt pthread h warning unused parameter stackaddr tt pthread attr getstack pthread t thread void stackaddr size t stacksize home alex p tarantool meta r t src tt pthread h warning unused parameter stacksize tt pthread attr getstack pthread t thread void stackaddr size t stacksize warnings and error generated the reason is inaccurate cmake checks code from cmakefiles cmakeerror log c usr lib llvm bin clang dhave pthread setname np d darwin c source d gnu source fexceptions funwind tables fasynchronous unwind tables fno common fopenmp pedantic errors md mt cmakefiles cmtc dir src c o mf cmakefiles cmtc dir src c o d o cmakefiles cmtc dir src c o c home alex p tarantool meta r t cmakefiles cmakescratch trycompile src c home alex p tarantool meta r t cmakefiles cmakescratch trycompile src c error a function declaration without a prototype is deprecated in all versions of c int main pthread setname np pthread self void error generated | 0 |
134,788 | 12,627,069,754 | IssuesEvent | 2020-06-14 19:37:25 | cdnjs/cdnjs | https://api.github.com/repos/cdnjs/cdnjs | closed | Improve CDNJS documentation | in progress 📒 Documentation | # The importance of documentation
I've been actively contributing to CDNJS for the past couple of weeks and it has been a truly delightful experience working with CDNJS maintainers and fellow contributors. They've been highly supportive.
In the process of contributing, I've come to realize how important CDNJSs mission is for developers. However, **with great power comes great responsibility**.
Open source projects are usually self-promoted by their easy to read, organized, and exhaustive documentation. Great examples include Backbone.js, Can.js, jQuery++, Underscore.js, jQuery, HTML5 Boilerplate, Require.js, Twitter Bootstrap, and many more. Just as writing good code and great tests are important, excellent documentation helps others use and extend a project.
# The current state of CDNJS documentation
The current CDNJS documentation is good. It's pretty good when compared to majority of the open source projects hosted on GitHub. However, it can be **better**.
Currently, the following places loosely host the documentation for CDNJS:
* [README.md](https://github.com/cdnjs/cdnjs/blob/master/README.md): This is the landing page for anyone visiting the CDNJS repository on GitHub.
* [documents directory](https://github.com/cdnjs/cdnjs/tree/master/documents): This directory contains a few readme files for the [API](https://github.com/cdnjs/cdnjs/blob/master/documents/api.md), the [auto update](https://github.com/cdnjs/cdnjs/blob/master/documents/autoupdate.md) functionality and [sparse checkout](https://github.com/cdnjs/cdnjs/blob/master/documents/sparseCheckout.md) feature for those working on the project locally.
* [CONTRIBUTING.md](https://github.com/cdnjs/cdnjs/blob/master/CONTRIBUTING.md): This is the main guide for people looking to contribute to the CDNJS project.
* [CDNJS wiki](https://github.com/cdnjs/cdnjs/wiki): The wiki currently consists of only one page titled [Extensions, Plugins, Resources](https://github.com/cdnjs/cdnjs/wiki/Extensions%2C-Plugins%2C-Resources).
In my opinion, these are few of the problems with the current documentation:
* **MAJOR**: The documentation is scattered across several places making it difficult for new contributors and even seasoned ones to look something up.
* **MAJOR**: Several important guidelines are missing from the documentation. Few which are at the top of my mind include commit message styles, instructions for debugging problems with pull requests with CDNJS tools and more.
* **MINOR**: Most of the documentation is laced with grammatical errors. _I understand that English is not the first language of maintainers and I'd be more than happy to help._
# Why GitHub wiki pages?
[GitHub Wikis](https://help.github.com/articles/about-github-wikis/) are a place in your repository where you can share long-form content about your project, such as how to use it, how it's been designed, manifestos on its core principles, and so on. Whereas a README is intended to quickly orient readers as to what your project can do, wikis can be used to provide additional documentation.
Wikis can be edited directly on GitHub, or you can work with a text editor offline and simply push your changes. Wikis are also collaborative by design.
# What next?
If the maintainers of CDNJS are comfortable with it, I'd like to work on revamping the documentation using wiki pages. Right now, we can start with a roadmap of issues that need to be solved and work on them one-by-one.
cc @PeterDaveHello
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/44690726-improve-cdnjs-documentation?utm_campaign=plugin&utm_content=tracker%2F32893&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F32893&utm_medium=issues&utm_source=github).
</bountysource-plugin> | 1.0 | Improve CDNJS documentation - # The importance of documentation
I've been actively contributing to CDNJS for the past couple of weeks and it has been a truly delightful experience working with CDNJS maintainers and fellow contributors. They've been highly supportive.
In the process of contributing, I've come to realize how important CDNJSs mission is for developers. However, **with great power comes great responsibility**.
Open source projects are usually self-promoted by their easy to read, organized, and exhaustive documentation. Great examples include Backbone.js, Can.js, jQuery++, Underscore.js, jQuery, HTML5 Boilerplate, Require.js, Twitter Bootstrap, and many more. Just as writing good code and great tests are important, excellent documentation helps others use and extend a project.
# The current state of CDNJS documentation
The current CDNJS documentation is good. It's pretty good when compared to majority of the open source projects hosted on GitHub. However, it can be **better**.
Currently, the following places loosely host the documentation for CDNJS:
* [README.md](https://github.com/cdnjs/cdnjs/blob/master/README.md): This is the landing page for anyone visiting the CDNJS repository on GitHub.
* [documents directory](https://github.com/cdnjs/cdnjs/tree/master/documents): This directory contains a few readme files for the [API](https://github.com/cdnjs/cdnjs/blob/master/documents/api.md), the [auto update](https://github.com/cdnjs/cdnjs/blob/master/documents/autoupdate.md) functionality and [sparse checkout](https://github.com/cdnjs/cdnjs/blob/master/documents/sparseCheckout.md) feature for those working on the project locally.
* [CONTRIBUTING.md](https://github.com/cdnjs/cdnjs/blob/master/CONTRIBUTING.md): This is the main guide for people looking to contribute to the CDNJS project.
* [CDNJS wiki](https://github.com/cdnjs/cdnjs/wiki): The wiki currently consists of only one page titled [Extensions, Plugins, Resources](https://github.com/cdnjs/cdnjs/wiki/Extensions%2C-Plugins%2C-Resources).
In my opinion, these are few of the problems with the current documentation:
* **MAJOR**: The documentation is scattered across several places making it difficult for new contributors and even seasoned ones to look something up.
* **MAJOR**: Several important guidelines are missing from the documentation. Few which are at the top of my mind include commit message styles, instructions for debugging problems with pull requests with CDNJS tools and more.
* **MINOR**: Most of the documentation is laced with grammatical errors. _I understand that English is not the first language of maintainers and I'd be more than happy to help._
# Why GitHub wiki pages?
[GitHub Wikis](https://help.github.com/articles/about-github-wikis/) are a place in your repository where you can share long-form content about your project, such as how to use it, how it's been designed, manifestos on its core principles, and so on. Whereas a README is intended to quickly orient readers as to what your project can do, wikis can be used to provide additional documentation.
Wikis can be edited directly on GitHub, or you can work with a text editor offline and simply push your changes. Wikis are also collaborative by design.
# What next?
If the maintainers of CDNJS are comfortable with it, I'd like to work on revamping the documentation using wiki pages. Right now, we can start with a roadmap of issues that need to be solved and work on them one-by-one.
cc @PeterDaveHello
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/44690726-improve-cdnjs-documentation?utm_campaign=plugin&utm_content=tracker%2F32893&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F32893&utm_medium=issues&utm_source=github).
</bountysource-plugin> | non_usab | improve cdnjs documentation the importance of documentation i ve been actively contributing to cdnjs for the past couple of weeks and it has been a truly delightful experience working with cdnjs maintainers and fellow contributors they ve been highly supportive in the process of contributing i ve come to realize how important cdnjss mission is for developers however with great power comes great responsibility open source projects are usually self promoted by their easy to read organized and exhaustive documentation great examples include backbone js can js jquery underscore js jquery boilerplate require js twitter bootstrap and many more just as writing good code and great tests are important excellent documentation helps others use and extend a project the current state of cdnjs documentation the current cdnjs documentation is good it s pretty good when compared to majority of the open source projects hosted on github however it can be better currently the following places loosely host the documentation for cdnjs this is the landing page for anyone visiting the cdnjs repository on github this directory contains a few readme files for the the functionality and feature for those working on the project locally this is the main guide for people looking to contribute to the cdnjs project the wiki currently consists of only one page titled in my opinion these are few of the problems with the current documentation major the documentation is scattered across several places making it difficult for new contributors and even seasoned ones to look something up major several important guidelines are missing from the documentation few which are at the top of my mind include commit message styles instructions for debugging problems with pull requests with cdnjs tools and more minor most of the documentation is laced with grammatical errors i understand that english is not the first language of maintainers and i d be more than happy to help why github wiki pages are a place in your repository where you can share long form content about your project such as how to use it how it s been designed manifestos on its core principles and so on whereas a readme is intended to quickly orient readers as to what your project can do wikis can be used to provide additional documentation wikis can be edited directly on github or you can work with a text editor offline and simply push your changes wikis are also collaborative by design what next if the maintainers of cdnjs are comfortable with it i d like to work on revamping the documentation using wiki pages right now we can start with a roadmap of issues that need to be solved and work on them one by one cc peterdavehello want to back this issue we accept bounties via | 0 |
96,277 | 27,801,978,950 | IssuesEvent | 2023-03-17 16:30:36 | dotnet/source-build | https://api.github.com/repos/dotnet/source-build | closed | Offline CI legs are failing to find package runtime.linux-x64.Microsoft.DotNet.ILCompiler | area-build | Failing Microsoft internal CI - https://dev.azure.com/dnceng/internal/_build/results?buildId=2134798
Sample failure
```
/vmr/src/runtime/artifacts/source-build/self/src/src/coreclr/tools/aot/ILCompiler/ILCompiler.csproj : error NU1101: Unable to find package runtime.linux-x64.Microsoft.DotNet.ILCompiler. No packages exist with this id in source(s): prebuilt, previously-source-built, reference-packages, source-built [/vmr/src/runtime/artifacts/source-build/self/src/Build.proj]
/vmr/src/runtime/artifacts/source-build/self/src/src/coreclr/tools/aot/ILCompiler/ILCompiler.csproj : error NU1101: Unable to find package runtime.linux-x64.Microsoft.DotNet.ILCompiler. No packages exist with this id in source(s): prebuilt, previously-source-built, reference-packages, source-built [/vmr/src/runtime/artifacts/source-build/self/src/Build.proj]
```
The failure seems to be caused by a new dependency on the IlCompiler in the runtime build. The portable ILCompiler is not something the [prep's bootstrap logic](https://github.com/dotnet/installer/blob/main/src/SourceBuild/content/eng/bootstrap/buildBootstrapPreviouslySB.csproj#L30) restores for x64. | 1.0 | Offline CI legs are failing to find package runtime.linux-x64.Microsoft.DotNet.ILCompiler - Failing Microsoft internal CI - https://dev.azure.com/dnceng/internal/_build/results?buildId=2134798
Sample failure
```
/vmr/src/runtime/artifacts/source-build/self/src/src/coreclr/tools/aot/ILCompiler/ILCompiler.csproj : error NU1101: Unable to find package runtime.linux-x64.Microsoft.DotNet.ILCompiler. No packages exist with this id in source(s): prebuilt, previously-source-built, reference-packages, source-built [/vmr/src/runtime/artifacts/source-build/self/src/Build.proj]
/vmr/src/runtime/artifacts/source-build/self/src/src/coreclr/tools/aot/ILCompiler/ILCompiler.csproj : error NU1101: Unable to find package runtime.linux-x64.Microsoft.DotNet.ILCompiler. No packages exist with this id in source(s): prebuilt, previously-source-built, reference-packages, source-built [/vmr/src/runtime/artifacts/source-build/self/src/Build.proj]
```
The failure seems to be caused by a new dependency on the IlCompiler in the runtime build. The portable ILCompiler is not something the [prep's bootstrap logic](https://github.com/dotnet/installer/blob/main/src/SourceBuild/content/eng/bootstrap/buildBootstrapPreviouslySB.csproj#L30) restores for x64. | non_usab | offline ci legs are failing to find package runtime linux microsoft dotnet ilcompiler failing microsoft internal ci sample failure vmr src runtime artifacts source build self src src coreclr tools aot ilcompiler ilcompiler csproj error unable to find package runtime linux microsoft dotnet ilcompiler no packages exist with this id in source s prebuilt previously source built reference packages source built vmr src runtime artifacts source build self src src coreclr tools aot ilcompiler ilcompiler csproj error unable to find package runtime linux microsoft dotnet ilcompiler no packages exist with this id in source s prebuilt previously source built reference packages source built the failure seems to be caused by a new dependency on the ilcompiler in the runtime build the portable ilcompiler is not something the restores for | 0 |
9,096 | 6,145,663,466 | IssuesEvent | 2017-06-27 12:08:36 | Virtual-Labs/structural-dynamics-iiith | https://api.github.com/repos/Virtual-Labs/structural-dynamics-iiith | closed | QA_Concept of Response Spectrum_Procedure_Content-needs-to-be-updated | Category: Usability Developed by: VLEAD Open-Edx Resolved Severity :S1 Status: Open | Defect Description :
In the Procedure page of Concept of Response Spectrum experiment, the content says "The section will be updated soon". Need to either include the content or remove the section.
Actual Result :
In the Procedure page of Concept of Response Spectrum experiment, the content says "The section will be updated soon".
Environment :
OS: Windows 7, Ubuntu-16.04,Centos-6
Browsers: Firefox-42.0,Chrome-47.0,chromium-45.0
Bandwidth : 100Mbps
Hardware Configuration:8GBRAM
Processor:i5
Attachment
| True | QA_Concept of Response Spectrum_Procedure_Content-needs-to-be-updated - Defect Description :
In the Procedure page of Concept of Response Spectrum experiment, the content says "The section will be updated soon". Need to either include the content or remove the section.
Actual Result :
In the Procedure page of Concept of Response Spectrum experiment, the content says "The section will be updated soon".
Environment :
OS: Windows 7, Ubuntu-16.04,Centos-6
Browsers: Firefox-42.0,Chrome-47.0,chromium-45.0
Bandwidth : 100Mbps
Hardware Configuration:8GBRAM
Processor:i5
Attachment
| usab | qa concept of response spectrum procedure content needs to be updated defect description in the procedure page of concept of response spectrum experiment the content says the section will be updated soon need to either include the content or remove the section actual result in the procedure page of concept of response spectrum experiment the content says the section will be updated soon environment os windows ubuntu centos browsers firefox chrome chromium bandwidth hardware configuration processor attachment | 1 |
68,200 | 14,914,575,549 | IssuesEvent | 2021-01-22 15:35:47 | AlexRogalskiy/object-mappers-playground | https://api.github.com/repos/AlexRogalskiy/object-mappers-playground | opened | CVE-2020-26217 (High) detected in xstream-1.4.9.jar, xstream-1.4.7.jar | security vulnerability | ## CVE-2020-26217 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>xstream-1.4.9.jar</b>, <b>xstream-1.4.7.jar</b></p></summary>
<p>
<details><summary><b>xstream-1.4.9.jar</b></p></summary>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Library home page: <a href="http://x-stream.github.io">http://x-stream.github.io</a></p>
<p>Path to dependency file: object-mappers-playground/modules/objectmappers-all/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.9/xstream-1.4.9.jar,/home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.9/xstream-1.4.9.jar</p>
<p>
Dependency Hierarchy:
- jmapper-core-1.6.1.CR2.jar (Root Library)
- :x: **xstream-1.4.9.jar** (Vulnerable Library)
</details>
<details><summary><b>xstream-1.4.7.jar</b></p></summary>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: object-mappers-playground/modules/objectmappers-smooks/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.7/xstream-1.4.7.jar</p>
<p>
Dependency Hierarchy:
- milyn-smooks-all-1.7.1.jar (Root Library)
- :x: **xstream-1.4.7.jar** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/object-mappers-playground/commit/ccc3fe199db8575ce11d67be41855d33c5e718ab">ccc3fe199db8575ce11d67be41855d33c5e718ab</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
XStream before version 1.4.14 is vulnerable to Remote Code Execution.The vulnerability may allow a remote attacker to run arbitrary shell commands only by manipulating the processed input stream. Only users who rely on blocklists are affected. Anyone using XStream's Security Framework allowlist is not affected. The linked advisory provides code workarounds for users who cannot upgrade. The issue is fixed in version 1.4.14.
<p>Publish Date: 2020-11-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-26217>CVE-2020-26217</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: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-mw36-7c6c-q4q2">https://github.com/x-stream/xstream/security/advisories/GHSA-mw36-7c6c-q4q2</a></p>
<p>Release Date: 2020-11-16</p>
<p>Fix Resolution: com.thoughtworks.xstream:xstream:1.4.14</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-26217 (High) detected in xstream-1.4.9.jar, xstream-1.4.7.jar - ## CVE-2020-26217 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>xstream-1.4.9.jar</b>, <b>xstream-1.4.7.jar</b></p></summary>
<p>
<details><summary><b>xstream-1.4.9.jar</b></p></summary>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Library home page: <a href="http://x-stream.github.io">http://x-stream.github.io</a></p>
<p>Path to dependency file: object-mappers-playground/modules/objectmappers-all/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.9/xstream-1.4.9.jar,/home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.9/xstream-1.4.9.jar</p>
<p>
Dependency Hierarchy:
- jmapper-core-1.6.1.CR2.jar (Root Library)
- :x: **xstream-1.4.9.jar** (Vulnerable Library)
</details>
<details><summary><b>xstream-1.4.7.jar</b></p></summary>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: object-mappers-playground/modules/objectmappers-smooks/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.7/xstream-1.4.7.jar</p>
<p>
Dependency Hierarchy:
- milyn-smooks-all-1.7.1.jar (Root Library)
- :x: **xstream-1.4.7.jar** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/object-mappers-playground/commit/ccc3fe199db8575ce11d67be41855d33c5e718ab">ccc3fe199db8575ce11d67be41855d33c5e718ab</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
XStream before version 1.4.14 is vulnerable to Remote Code Execution.The vulnerability may allow a remote attacker to run arbitrary shell commands only by manipulating the processed input stream. Only users who rely on blocklists are affected. Anyone using XStream's Security Framework allowlist is not affected. The linked advisory provides code workarounds for users who cannot upgrade. The issue is fixed in version 1.4.14.
<p>Publish Date: 2020-11-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-26217>CVE-2020-26217</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: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-mw36-7c6c-q4q2">https://github.com/x-stream/xstream/security/advisories/GHSA-mw36-7c6c-q4q2</a></p>
<p>Release Date: 2020-11-16</p>
<p>Fix Resolution: com.thoughtworks.xstream:xstream:1.4.14</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_usab | cve high detected in xstream jar xstream jar cve high severity vulnerability vulnerable libraries xstream jar xstream jar xstream jar xstream is a serialization library from java objects to xml and back library home page a href path to dependency file object mappers playground modules objectmappers all pom xml path to vulnerable library home wss scanner repository com thoughtworks xstream xstream xstream jar home wss scanner repository com thoughtworks xstream xstream xstream jar dependency hierarchy jmapper core jar root library x xstream jar vulnerable library xstream jar xstream is a serialization library from java objects to xml and back path to dependency file object mappers playground modules objectmappers smooks pom xml path to vulnerable library home wss scanner repository com thoughtworks xstream xstream xstream jar dependency hierarchy milyn smooks all jar root library x xstream jar vulnerable library found in head commit a href vulnerability details xstream before version is vulnerable to remote code execution the vulnerability may allow a remote attacker to run arbitrary shell commands only by manipulating the processed input stream only users who rely on blocklists are affected anyone using xstream s security framework allowlist is not affected the linked advisory provides code workarounds for users who cannot upgrade the issue is fixed in version 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 high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution com thoughtworks xstream xstream step up your open source security game with whitesource | 0 |
276,286 | 30,444,242,614 | IssuesEvent | 2023-07-15 13:06:22 | dgee2/menu-ui | https://api.github.com/repos/dgee2/menu-ui | closed | CVE-2022-37599 (High) detected in loader-utils-2.0.0.tgz | security vulnerability | ## CVE-2022-37599 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>loader-utils-2.0.0.tgz</b></p></summary>
<p>utils for webpack loaders</p>
<p>Library home page: <a href="https://registry.npmjs.org/loader-utils/-/loader-utils-2.0.0.tgz">https://registry.npmjs.org/loader-utils/-/loader-utils-2.0.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/loader-utils/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-4.0.2.tgz (Root Library)
- webpack-5.5.0.tgz
- :x: **loader-utils-2.0.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/dgee2/menu-ui/commit/9ef518df7cad4d3e15264ea477a603819eba668c">9ef518df7cad4d3e15264ea477a603819eba668c</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>
A Regular expression denial of service (ReDoS) flaw was found in Function interpolateName in interpolateName.js in webpack loader-utils 2.0.0 via the resourcePath variable in interpolateName.js.
<p>Publish Date: 2022-10-11
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-37599>CVE-2022-37599</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-hhq3-ff78-jv3g">https://github.com/advisories/GHSA-hhq3-ff78-jv3g</a></p>
<p>Release Date: 2022-10-11</p>
<p>Fix Resolution (loader-utils): 2.0.3</p>
<p>Direct dependency fix Resolution (react-scripts): 5.0.1</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-37599 (High) detected in loader-utils-2.0.0.tgz - ## CVE-2022-37599 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>loader-utils-2.0.0.tgz</b></p></summary>
<p>utils for webpack loaders</p>
<p>Library home page: <a href="https://registry.npmjs.org/loader-utils/-/loader-utils-2.0.0.tgz">https://registry.npmjs.org/loader-utils/-/loader-utils-2.0.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/loader-utils/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-4.0.2.tgz (Root Library)
- webpack-5.5.0.tgz
- :x: **loader-utils-2.0.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/dgee2/menu-ui/commit/9ef518df7cad4d3e15264ea477a603819eba668c">9ef518df7cad4d3e15264ea477a603819eba668c</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>
A Regular expression denial of service (ReDoS) flaw was found in Function interpolateName in interpolateName.js in webpack loader-utils 2.0.0 via the resourcePath variable in interpolateName.js.
<p>Publish Date: 2022-10-11
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-37599>CVE-2022-37599</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-hhq3-ff78-jv3g">https://github.com/advisories/GHSA-hhq3-ff78-jv3g</a></p>
<p>Release Date: 2022-10-11</p>
<p>Fix Resolution (loader-utils): 2.0.3</p>
<p>Direct dependency fix Resolution (react-scripts): 5.0.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_usab | cve high detected in loader utils tgz cve high severity vulnerability vulnerable library loader utils tgz utils for webpack loaders library home page a href path to dependency file package json path to vulnerable library node modules loader utils package json dependency hierarchy react scripts tgz root library webpack tgz x loader utils tgz vulnerable library found in head commit a href found in base branch master vulnerability details a regular expression denial of service redos flaw was found in function interpolatename in interpolatename js in webpack loader utils via the resourcepath variable in interpolatename js 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 loader utils direct dependency fix resolution react scripts step up your open source security game with mend | 0 |
114,225 | 24,568,837,507 | IssuesEvent | 2022-10-13 06:55:21 | ballerina-platform/ballerina-lang | https://api.github.com/repos/ballerina-platform/ballerina-lang | closed | [Bug]: ClassCastException in ExtractToFunctionCodeAction | Type/Bug Team/LanguageServer Points/1 Area/CodeAction Reason/EngineeringMistake userCategory/Editor | ### Description
Placing the cursor at the following cursor position gives a ClassCastException,
<img width="1198" alt="Screenshot 2022-10-03 at 13 02 16" src="https://user-images.githubusercontent.com/61020198/193523423-b495998e-5ad4-4a13-9a77-40ecdfa8e044.png">
```
[Error - 1:00:51 PM] CodeAction 'ExtractToFunctionCodeAction' failed! {, error: 'class io.ballerina.compiler.syntax.tree.BasicLiteralNode cannot be cast to class io.ballerina.compiler.syntax.tree.FieldAccessExpressionNode (io.ballerina.compiler.syntax.tree.BasicLiteralNode and io.ballerina.compiler.syntax.tree.FieldAccessExpressionNode are in unnamed module of loader 'app')'}
java.lang.ClassCastException: class io.ballerina.compiler.syntax.tree.BasicLiteralNode cannot be cast to class io.ballerina.compiler.syntax.tree.FieldAccessExpressionNode (io.ballerina.compiler.syntax.tree.BasicLiteralNode and io.ballerina.compiler.syntax.tree.FieldAccessExpressionNode are in unnamed module of loader 'app')
at org.ballerinalang.langserver.codeaction.providers.ExtractToFunctionCodeAction.isExpressionExtractable(ExtractToFunctionCodeAction.java:549)
at org.ballerinalang.langserver.codeaction.providers.ExtractToFunctionCodeAction.validate(ExtractToFunctionCodeAction.java:86)
at org.ballerinalang.langserver.codeaction.CodeActionRouter.lambda$getAvailableCodeActions$1(CodeActionRouter.java:94)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1540)
at org.ballerinalang.langserver.codeaction.CodeActionRouter.getAvailableCodeActions(CodeActionRouter.java:88)
at org.ballerinalang.langserver.codeaction.BallerinaCodeActionExtension.execute(BallerinaCodeActionExtension.java:49)
at org.ballerinalang.langserver.codeaction.BallerinaCodeActionExtension.execute(BallerinaCodeActionExtension.java:37)
at org.ballerinalang.langserver.LangExtensionDelegator.codeActions(LangExtensionDelegator.java:169)
at org.ballerinalang.langserver.BallerinaTextDocumentService.lambda$codeAction$8(BallerinaTextDocumentService.java:334)
at java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:642)
at java.base/java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:479)
at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290)
at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020)
at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656)
at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1594)
at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:177)
```
### Steps to Reproduce
```
type Student record {
string fname;
string lname;
int age;
};
public function main() {
Student st = {fname: "<cursor>",};
}
```
### Affected Version(s)
2201.2.x
### Related area
-> Editor | 1.0 | [Bug]: ClassCastException in ExtractToFunctionCodeAction - ### Description
Placing the cursor at the following cursor position gives a ClassCastException,
<img width="1198" alt="Screenshot 2022-10-03 at 13 02 16" src="https://user-images.githubusercontent.com/61020198/193523423-b495998e-5ad4-4a13-9a77-40ecdfa8e044.png">
```
[Error - 1:00:51 PM] CodeAction 'ExtractToFunctionCodeAction' failed! {, error: 'class io.ballerina.compiler.syntax.tree.BasicLiteralNode cannot be cast to class io.ballerina.compiler.syntax.tree.FieldAccessExpressionNode (io.ballerina.compiler.syntax.tree.BasicLiteralNode and io.ballerina.compiler.syntax.tree.FieldAccessExpressionNode are in unnamed module of loader 'app')'}
java.lang.ClassCastException: class io.ballerina.compiler.syntax.tree.BasicLiteralNode cannot be cast to class io.ballerina.compiler.syntax.tree.FieldAccessExpressionNode (io.ballerina.compiler.syntax.tree.BasicLiteralNode and io.ballerina.compiler.syntax.tree.FieldAccessExpressionNode are in unnamed module of loader 'app')
at org.ballerinalang.langserver.codeaction.providers.ExtractToFunctionCodeAction.isExpressionExtractable(ExtractToFunctionCodeAction.java:549)
at org.ballerinalang.langserver.codeaction.providers.ExtractToFunctionCodeAction.validate(ExtractToFunctionCodeAction.java:86)
at org.ballerinalang.langserver.codeaction.CodeActionRouter.lambda$getAvailableCodeActions$1(CodeActionRouter.java:94)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1540)
at org.ballerinalang.langserver.codeaction.CodeActionRouter.getAvailableCodeActions(CodeActionRouter.java:88)
at org.ballerinalang.langserver.codeaction.BallerinaCodeActionExtension.execute(BallerinaCodeActionExtension.java:49)
at org.ballerinalang.langserver.codeaction.BallerinaCodeActionExtension.execute(BallerinaCodeActionExtension.java:37)
at org.ballerinalang.langserver.LangExtensionDelegator.codeActions(LangExtensionDelegator.java:169)
at org.ballerinalang.langserver.BallerinaTextDocumentService.lambda$codeAction$8(BallerinaTextDocumentService.java:334)
at java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:642)
at java.base/java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:479)
at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290)
at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020)
at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656)
at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1594)
at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:177)
```
### Steps to Reproduce
```
type Student record {
string fname;
string lname;
int age;
};
public function main() {
Student st = {fname: "<cursor>",};
}
```
### Affected Version(s)
2201.2.x
### Related area
-> Editor | non_usab | classcastexception in extracttofunctioncodeaction description placing the cursor at the following cursor position gives a classcastexception img width alt screenshot at src codeaction extracttofunctioncodeaction failed error class io ballerina compiler syntax tree basicliteralnode cannot be cast to class io ballerina compiler syntax tree fieldaccessexpressionnode io ballerina compiler syntax tree basicliteralnode and io ballerina compiler syntax tree fieldaccessexpressionnode are in unnamed module of loader app java lang classcastexception class io ballerina compiler syntax tree basicliteralnode cannot be cast to class io ballerina compiler syntax tree fieldaccessexpressionnode io ballerina compiler syntax tree basicliteralnode and io ballerina compiler syntax tree fieldaccessexpressionnode are in unnamed module of loader app at org ballerinalang langserver codeaction providers extracttofunctioncodeaction isexpressionextractable extracttofunctioncodeaction java at org ballerinalang langserver codeaction providers extracttofunctioncodeaction validate extracttofunctioncodeaction java at org ballerinalang langserver codeaction codeactionrouter lambda getavailablecodeactions codeactionrouter java at java base java util arraylist foreach arraylist java at org ballerinalang langserver codeaction codeactionrouter getavailablecodeactions codeactionrouter java at org ballerinalang langserver codeaction ballerinacodeactionextension execute ballerinacodeactionextension java at org ballerinalang langserver codeaction ballerinacodeactionextension execute ballerinacodeactionextension java at org ballerinalang langserver langextensiondelegator codeactions langextensiondelegator java at org ballerinalang langserver ballerinatextdocumentservice lambda codeaction ballerinatextdocumentservice java at java base java util concurrent completablefuture uniapply tryfire completablefuture java at java base java util concurrent completablefuture completion exec completablefuture java at java base java util concurrent forkjointask doexec forkjointask java at java base java util concurrent forkjoinpool workqueue toplevelexec forkjoinpool java at java base java util concurrent forkjoinpool scan forkjoinpool java at java base java util concurrent forkjoinpool runworker forkjoinpool java at java base java util concurrent forkjoinworkerthread run forkjoinworkerthread java steps to reproduce type student record string fname string lname int age public function main student st fname affected version s x related area editor | 0 |
3,042 | 3,297,175,125 | IssuesEvent | 2015-11-02 06:43:23 | OpenCollar/opencollar | https://api.github.com/repos/OpenCollar/opencollar | closed | changed commands to "prefix action command" | change completed enhancement usability | We want to get rid of ugly, hard to read and weird to type commands like:
prefixactioncommand
but use:
prefix action command
old examples:
prefixsetpublic - prefixunsetpublic
new:
prefix enable public - prefix disable public
Also make menus available throughout the collar with commands:
pr menu something
| True | changed commands to "prefix action command" - We want to get rid of ugly, hard to read and weird to type commands like:
prefixactioncommand
but use:
prefix action command
old examples:
prefixsetpublic - prefixunsetpublic
new:
prefix enable public - prefix disable public
Also make menus available throughout the collar with commands:
pr menu something
| usab | changed commands to prefix action command we want to get rid of ugly hard to read and weird to type commands like prefixactioncommand but use prefix action command old examples prefixsetpublic prefixunsetpublic new prefix enable public prefix disable public also make menus available throughout the collar with commands pr menu something | 1 |
1,313 | 2,791,479,241 | IssuesEvent | 2015-05-10 05:38:47 | mathnet/mathnet-numerics | https://api.github.com/repos/mathnet/mathnet-numerics | opened | Matrix/Vector builder with generic functions instead of type to allow type inference | X-Usability | The current Matrix and Vector builders are generic in type, meaning that the desired type needs to be specified explicitly even though it often could have been inferred from the arguments if it were generic in the methods instead of the type.
Unfortunately we cannot modify the original builders, but we could provide a new alternative one in addition. | True | Matrix/Vector builder with generic functions instead of type to allow type inference - The current Matrix and Vector builders are generic in type, meaning that the desired type needs to be specified explicitly even though it often could have been inferred from the arguments if it were generic in the methods instead of the type.
Unfortunately we cannot modify the original builders, but we could provide a new alternative one in addition. | usab | matrix vector builder with generic functions instead of type to allow type inference the current matrix and vector builders are generic in type meaning that the desired type needs to be specified explicitly even though it often could have been inferred from the arguments if it were generic in the methods instead of the type unfortunately we cannot modify the original builders but we could provide a new alternative one in addition | 1 |
17,524 | 6,469,324,577 | IssuesEvent | 2017-08-17 05:23:02 | nodejs/node | https://api.github.com/repos/nodejs/node | closed | --enable-static fails due to multiple definition | build tracing v7.x v8.x | * **Version**: v7.10.0, v8.0.0
* **Platform**: Linux x64 (Ubuntu 17.04)
* **Subsystem**: Build?
```
./configure --enable-static
make
```
ends up
```
/tmp/out/Release/obj.target/node/src/tracing/node_trace_writer.o: In function `node::tracing::NodeTraceWriter::FlushPrivate()':
node_trace_writer.cc:(.text+0x16e0): multiple definition of `node::tracing::NodeTraceWriter::FlushPrivate()'
/tmp/out/Release/obj.target/node/src/tracing/node_trace_writer.o:node_trace_writer.cc:(.text+0x16e0): first defined here
/tmp/out/Release/obj.target/node/src/tracing/trace_event.o: In function `node::tracing::TraceEventHelper::SetCurrentPlatform(v8::Platform*)':
trace_event.cc:(.text+0x0): multiple definition of `node::tracing::TraceEventHelper::SetCurrentPlatform(v8::Platform*)'
/tmp/out/Release/obj.target/node/src/tracing/trace_event.o:trace_event.cc:(.text+0x0): first defined here
/tmp/out/Release/obj.target/node/src/tracing/trace_event.o:(.bss+0x0): multiple definition of `node::tracing::platform_'
/tmp/out/Release/obj.target/node/src/tracing/trace_event.o:(.bss+0x0): first defined here
/tmp/out/Release/obj.target/node/src/tracing/trace_event.o: In function `node::tracing::TraceEventHelper::GetCurrentPlatform()':
trace_event.cc:(.text+0x10): multiple definition of `node::tracing::TraceEventHelper::GetCurrentPlatform()'
/tmp/out/Release/obj.target/node/src/tracing/trace_event.o:trace_event.cc:(.text+0x10): first defined here
collect2: error: ld returned 1 exit status
cctest.target.mk:218: recipe for target '/tmp/out/Release/cctest' failed
make[1]: *** [/tmp/out/Release/cctest] Error 1
rm 8cc54113df3f034cebe6283bb3a0080714e3f522.intermediate
Makefile:76: recipe for target 'node' failed
make: *** [node] Error 2
```
for me.
With v7.4.0, things are working. | 1.0 | --enable-static fails due to multiple definition - * **Version**: v7.10.0, v8.0.0
* **Platform**: Linux x64 (Ubuntu 17.04)
* **Subsystem**: Build?
```
./configure --enable-static
make
```
ends up
```
/tmp/out/Release/obj.target/node/src/tracing/node_trace_writer.o: In function `node::tracing::NodeTraceWriter::FlushPrivate()':
node_trace_writer.cc:(.text+0x16e0): multiple definition of `node::tracing::NodeTraceWriter::FlushPrivate()'
/tmp/out/Release/obj.target/node/src/tracing/node_trace_writer.o:node_trace_writer.cc:(.text+0x16e0): first defined here
/tmp/out/Release/obj.target/node/src/tracing/trace_event.o: In function `node::tracing::TraceEventHelper::SetCurrentPlatform(v8::Platform*)':
trace_event.cc:(.text+0x0): multiple definition of `node::tracing::TraceEventHelper::SetCurrentPlatform(v8::Platform*)'
/tmp/out/Release/obj.target/node/src/tracing/trace_event.o:trace_event.cc:(.text+0x0): first defined here
/tmp/out/Release/obj.target/node/src/tracing/trace_event.o:(.bss+0x0): multiple definition of `node::tracing::platform_'
/tmp/out/Release/obj.target/node/src/tracing/trace_event.o:(.bss+0x0): first defined here
/tmp/out/Release/obj.target/node/src/tracing/trace_event.o: In function `node::tracing::TraceEventHelper::GetCurrentPlatform()':
trace_event.cc:(.text+0x10): multiple definition of `node::tracing::TraceEventHelper::GetCurrentPlatform()'
/tmp/out/Release/obj.target/node/src/tracing/trace_event.o:trace_event.cc:(.text+0x10): first defined here
collect2: error: ld returned 1 exit status
cctest.target.mk:218: recipe for target '/tmp/out/Release/cctest' failed
make[1]: *** [/tmp/out/Release/cctest] Error 1
rm 8cc54113df3f034cebe6283bb3a0080714e3f522.intermediate
Makefile:76: recipe for target 'node' failed
make: *** [node] Error 2
```
for me.
With v7.4.0, things are working. | non_usab | enable static fails due to multiple definition version platform linux ubuntu subsystem build configure enable static make ends up tmp out release obj target node src tracing node trace writer o in function node tracing nodetracewriter flushprivate node trace writer cc text multiple definition of node tracing nodetracewriter flushprivate tmp out release obj target node src tracing node trace writer o node trace writer cc text first defined here tmp out release obj target node src tracing trace event o in function node tracing traceeventhelper setcurrentplatform platform trace event cc text multiple definition of node tracing traceeventhelper setcurrentplatform platform tmp out release obj target node src tracing trace event o trace event cc text first defined here tmp out release obj target node src tracing trace event o bss multiple definition of node tracing platform tmp out release obj target node src tracing trace event o bss first defined here tmp out release obj target node src tracing trace event o in function node tracing traceeventhelper getcurrentplatform trace event cc text multiple definition of node tracing traceeventhelper getcurrentplatform tmp out release obj target node src tracing trace event o trace event cc text first defined here error ld returned exit status cctest target mk recipe for target tmp out release cctest failed make error rm intermediate makefile recipe for target node failed make error for me with things are working | 0 |
9,781 | 6,412,576,326 | IssuesEvent | 2017-08-08 03:57:18 | FReBOmusic/FReBO | https://api.github.com/repos/FReBOmusic/FReBO | opened | List Entries | Usability | In the event that the user navigates to the Categories Screen List View, on the Categories Screen.
**Expected Response**: The Equipment Categories should be displayed in alphabetical order on the Categories List View of the Categories Screen. | True | List Entries - In the event that the user navigates to the Categories Screen List View, on the Categories Screen.
**Expected Response**: The Equipment Categories should be displayed in alphabetical order on the Categories List View of the Categories Screen. | usab | list entries in the event that the user navigates to the categories screen list view on the categories screen expected response the equipment categories should be displayed in alphabetical order on the categories list view of the categories screen | 1 |
27,279 | 28,000,059,284 | IssuesEvent | 2023-03-27 11:06:48 | ClickHouse/ClickHouse | https://api.github.com/repos/ClickHouse/ClickHouse | opened | remove log_comment value from Settings column in query_log table | usability | **Describe the issue**
Users can (and will put in log_comment setting some context of that particular query, which is useful for debugging)
But currently it's being doubled in `log_comment` column AND in Settings column (because user define log_comment as setting)
IE double disk usage
**Expected behavior**
No duplication of data.
| True | remove log_comment value from Settings column in query_log table - **Describe the issue**
Users can (and will put in log_comment setting some context of that particular query, which is useful for debugging)
But currently it's being doubled in `log_comment` column AND in Settings column (because user define log_comment as setting)
IE double disk usage
**Expected behavior**
No duplication of data.
| usab | remove log comment value from settings column in query log table describe the issue users can and will put in log comment setting some context of that particular query which is useful for debugging but currently it s being doubled in log comment column and in settings column because user define log comment as setting ie double disk usage expected behavior no duplication of data | 1 |
19,788 | 14,546,984,347 | IssuesEvent | 2020-12-15 22:08:37 | zaproxy/zaproxy | https://api.github.com/repos/zaproxy/zaproxy | closed | SOAP Extension - Various Issues | Usability add-on tracker | The SOAP extensions and it's scanner rules/plugins are impacted by various issues.
Per: https://github.com/zaproxy/zap-extensions/pull/1725#issuecomment-407016036
> I noticed other problem (although it might not be the only issue that prevents the scanners from scanning the messages), the message added to `ImportWSDL.requestsList` and put into `ImportWSDL.configurationsList` is later modified (in `WSDLCustomParser.persistMessage`) which means that the scanners are not able to get a `SOAPMsgConfig` nor the actions.
Per https://github.com/zaproxy/zap-extensions/pull/1725#issuecomment-406383321:
> Other things I noticed while tackling this. At https://github.com/zaproxy/zap-extensions/blob/master/addOns/soap/src/main/java/org/zaproxy/zap/extension/soap/ImportWSDL.java#L103 `requestsList` only has entries if the import was just done; if you've opened a saved session or install the addon after the endpoints are already in the Sites Tree then it is empty.
**Software versions**
- ZAP: 2.7.0 and Dev
- Add-on: SOAP v3
**Additional context**
https://github.com/zaproxy/zaproxy/issues/4832
https://github.com/zaproxy/zap-extensions/pull/1725
<sub>Testing info: https://github.com/zaproxy/zap-extensions/pull/1725#issuecomment-406381922 </sub>
| True | SOAP Extension - Various Issues - The SOAP extensions and it's scanner rules/plugins are impacted by various issues.
Per: https://github.com/zaproxy/zap-extensions/pull/1725#issuecomment-407016036
> I noticed other problem (although it might not be the only issue that prevents the scanners from scanning the messages), the message added to `ImportWSDL.requestsList` and put into `ImportWSDL.configurationsList` is later modified (in `WSDLCustomParser.persistMessage`) which means that the scanners are not able to get a `SOAPMsgConfig` nor the actions.
Per https://github.com/zaproxy/zap-extensions/pull/1725#issuecomment-406383321:
> Other things I noticed while tackling this. At https://github.com/zaproxy/zap-extensions/blob/master/addOns/soap/src/main/java/org/zaproxy/zap/extension/soap/ImportWSDL.java#L103 `requestsList` only has entries if the import was just done; if you've opened a saved session or install the addon after the endpoints are already in the Sites Tree then it is empty.
**Software versions**
- ZAP: 2.7.0 and Dev
- Add-on: SOAP v3
**Additional context**
https://github.com/zaproxy/zaproxy/issues/4832
https://github.com/zaproxy/zap-extensions/pull/1725
<sub>Testing info: https://github.com/zaproxy/zap-extensions/pull/1725#issuecomment-406381922 </sub>
| usab | soap extension various issues the soap extensions and it s scanner rules plugins are impacted by various issues per i noticed other problem although it might not be the only issue that prevents the scanners from scanning the messages the message added to importwsdl requestslist and put into importwsdl configurationslist is later modified in wsdlcustomparser persistmessage which means that the scanners are not able to get a soapmsgconfig nor the actions per other things i noticed while tackling this at requestslist only has entries if the import was just done if you ve opened a saved session or install the addon after the endpoints are already in the sites tree then it is empty software versions zap and dev add on soap additional context testing info | 1 |
22,610 | 19,714,019,276 | IssuesEvent | 2022-01-13 09:13:28 | lablup/backend.ai | https://api.github.com/repos/lablup/backend.ai | closed | Change the name of a running compute session | feature usability manager client console | There is a request from users that they want to change the name of the `RUNNING` compute session. This is not a major issue, but I think it would be good to have this feature.
- [x] Create a manager API endpoint to accept the request to change a session name.
* Should not change the name of a compute session when it is not `RUNNING`.
- [x] Add a CLI command to change a session's name.
- [ ] Add a feature to update a session's name in Web-UI, perhaps by clicking the session name text.
<img width="205" alt="image" src="https://user-images.githubusercontent.com/7539358/136492854-c9000d1e-c04c-4162-aa83-9aa2a9aca18f.png">
| True | Change the name of a running compute session - There is a request from users that they want to change the name of the `RUNNING` compute session. This is not a major issue, but I think it would be good to have this feature.
- [x] Create a manager API endpoint to accept the request to change a session name.
* Should not change the name of a compute session when it is not `RUNNING`.
- [x] Add a CLI command to change a session's name.
- [ ] Add a feature to update a session's name in Web-UI, perhaps by clicking the session name text.
<img width="205" alt="image" src="https://user-images.githubusercontent.com/7539358/136492854-c9000d1e-c04c-4162-aa83-9aa2a9aca18f.png">
| usab | change the name of a running compute session there is a request from users that they want to change the name of the running compute session this is not a major issue but i think it would be good to have this feature create a manager api endpoint to accept the request to change a session name should not change the name of a compute session when it is not running add a cli command to change a session s name add a feature to update a session s name in web ui perhaps by clicking the session name text img width alt image src | 1 |
10,361 | 6,678,419,749 | IssuesEvent | 2017-10-05 14:11:48 | coala/coala-bears | https://api.github.com/repos/coala/coala-bears | opened | CheckstyleBear: Unreadable traceback for user when checkstyle.jar download fails | area/usability difficulty/medium | For example a timeout causes this --> https://github.com/coala/coala-bears/issues/2065
Would be better to have a simple error message printed. | True | CheckstyleBear: Unreadable traceback for user when checkstyle.jar download fails - For example a timeout causes this --> https://github.com/coala/coala-bears/issues/2065
Would be better to have a simple error message printed. | usab | checkstylebear unreadable traceback for user when checkstyle jar download fails for example a timeout causes this would be better to have a simple error message printed | 1 |
6,744 | 4,533,450,760 | IssuesEvent | 2016-09-08 11:39:31 | Starcounter/Starcounter | https://api.github.com/repos/Starcounter/Starcounter | opened | UriMapping.OntologyMap throws nondescript exception when handler is missing | usability | Calling `UriMapping.OntologyMap` with a handler that isn't registered results in a `NullReferenceException`. You have to look at the code to figure out what's wrong. | True | UriMapping.OntologyMap throws nondescript exception when handler is missing - Calling `UriMapping.OntologyMap` with a handler that isn't registered results in a `NullReferenceException`. You have to look at the code to figure out what's wrong. | usab | urimapping ontologymap throws nondescript exception when handler is missing calling urimapping ontologymap with a handler that isn t registered results in a nullreferenceexception you have to look at the code to figure out what s wrong | 1 |
45,009 | 13,100,504,419 | IssuesEvent | 2020-08-04 00:45:24 | AOSC-Dev/aosc-os-abbs | https://api.github.com/repos/AOSC-Dev/aosc-os-abbs | opened | mbedtls: security update to 2.16.7 | security to-stable upgrade | <!-- Please remove items do not apply. -->
**CVE IDs:** CVE-2020-10932
**Other security advisory IDs:** ASA-202007-5
**Description:**
A side channel attack has been found on the ECDSA implementation of
Mbed TLS before 2.22.0, 2.16.6 and 2.7.15, allowing a local attacker
with access to precise enough timing and memory access information
(typically an untrusted operating system attacking a secure enclave
such as SGX or the TrustZone secure world) to fully recover an ECDSA
private key after observing a number of signature operations.
---
https://tls.mbed.org/tech-updates/security-advisories/mbedtls-security-advisory-2020-04
https://tls.mbed.org/tech-updates/security-advisories/mbedtls-security-advisory-2020-07
**Architectural progress (Mainline):**
<!-- Please remove any architecture to which the security vulnerabilities do not apply. -->
- [ ] AMD64 `amd64`
- [ ] 32-bit Optional Environment `optenv32`
- [ ] AArch64 `arm64`
**Architectural progress (Retro):**
<!-- Please remove any architecture to which the security vulnerabilities do not apply. -->
- [ ] ARMv5t+ `armel`
- [ ] ARMv7 `armhf`
- [ ] i486 `i486`
<!-- If the specified package is `noarch`, please use the stub below. -->
<!-- - [ ] Architecture-independent `noarch` -->
| True | mbedtls: security update to 2.16.7 - <!-- Please remove items do not apply. -->
**CVE IDs:** CVE-2020-10932
**Other security advisory IDs:** ASA-202007-5
**Description:**
A side channel attack has been found on the ECDSA implementation of
Mbed TLS before 2.22.0, 2.16.6 and 2.7.15, allowing a local attacker
with access to precise enough timing and memory access information
(typically an untrusted operating system attacking a secure enclave
such as SGX or the TrustZone secure world) to fully recover an ECDSA
private key after observing a number of signature operations.
---
https://tls.mbed.org/tech-updates/security-advisories/mbedtls-security-advisory-2020-04
https://tls.mbed.org/tech-updates/security-advisories/mbedtls-security-advisory-2020-07
**Architectural progress (Mainline):**
<!-- Please remove any architecture to which the security vulnerabilities do not apply. -->
- [ ] AMD64 `amd64`
- [ ] 32-bit Optional Environment `optenv32`
- [ ] AArch64 `arm64`
**Architectural progress (Retro):**
<!-- Please remove any architecture to which the security vulnerabilities do not apply. -->
- [ ] ARMv5t+ `armel`
- [ ] ARMv7 `armhf`
- [ ] i486 `i486`
<!-- If the specified package is `noarch`, please use the stub below. -->
<!-- - [ ] Architecture-independent `noarch` -->
| non_usab | mbedtls security update to cve ids cve other security advisory ids asa description a side channel attack has been found on the ecdsa implementation of mbed tls before and allowing a local attacker with access to precise enough timing and memory access information typically an untrusted operating system attacking a secure enclave such as sgx or the trustzone secure world to fully recover an ecdsa private key after observing a number of signature operations architectural progress mainline bit optional environment architectural progress retro armel armhf | 0 |
67,636 | 17,024,410,878 | IssuesEvent | 2021-07-03 07:06:40 | apache/shardingsphere | https://api.github.com/repos/apache/shardingsphere | closed | Calcite always can not download when mvn install in windows env | status: volunteer wanted type: build | Calcite lib always can not download when mvn install in windows env, please investigate the reason.
error log:
```
Error: Failed to execute goal on project shardingsphere-infra-optimize: Could not resolve dependencies for project org.apache.shardingsphere:shardingsphere-infra-optimize:jar:5.0.0-RC1-SNAPSHOT: Failed to collect dependencies at org.apache.calcite:calcite-core:jar:1.26.0: Failed to read artifact descriptor for org.apache.calcite:calcite-core:jar:1.26.0: Could not transfer artifact org.apache.calcite:calcite-core:pom:1.26.0 from/to central (https://repo.maven.apache.org/maven2): Transfer failed for https://repo.maven.apache.org/maven2/org/apache/calcite/calcite-core/1.26.0/calcite-core-1.26.0.pom: Connection reset -> [Help 1]
Error:
Error: To see the full stack trace of the errors, re-run Maven with the -e switch.
Error: Re-run Maven using the -X switch to enable full debug logging.
Error:
Error: For more information about the errors and possible solutions, please read the following articles:
Error: [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
Error:
Error: After correcting the problems, you can resume the build with the command
Error: mvn <args> -rf :shardingsphere-infra-optimize
Error: Process completed with exit code 1.
``` | 1.0 | Calcite always can not download when mvn install in windows env - Calcite lib always can not download when mvn install in windows env, please investigate the reason.
error log:
```
Error: Failed to execute goal on project shardingsphere-infra-optimize: Could not resolve dependencies for project org.apache.shardingsphere:shardingsphere-infra-optimize:jar:5.0.0-RC1-SNAPSHOT: Failed to collect dependencies at org.apache.calcite:calcite-core:jar:1.26.0: Failed to read artifact descriptor for org.apache.calcite:calcite-core:jar:1.26.0: Could not transfer artifact org.apache.calcite:calcite-core:pom:1.26.0 from/to central (https://repo.maven.apache.org/maven2): Transfer failed for https://repo.maven.apache.org/maven2/org/apache/calcite/calcite-core/1.26.0/calcite-core-1.26.0.pom: Connection reset -> [Help 1]
Error:
Error: To see the full stack trace of the errors, re-run Maven with the -e switch.
Error: Re-run Maven using the -X switch to enable full debug logging.
Error:
Error: For more information about the errors and possible solutions, please read the following articles:
Error: [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
Error:
Error: After correcting the problems, you can resume the build with the command
Error: mvn <args> -rf :shardingsphere-infra-optimize
Error: Process completed with exit code 1.
``` | non_usab | calcite always can not download when mvn install in windows env calcite lib always can not download when mvn install in windows env please investigate the reason error log error failed to execute goal on project shardingsphere infra optimize could not resolve dependencies for project org apache shardingsphere shardingsphere infra optimize jar snapshot failed to collect dependencies at org apache calcite calcite core jar failed to read artifact descriptor for org apache calcite calcite core jar could not transfer artifact org apache calcite calcite core pom from to central transfer failed for connection reset error error to see the full stack trace of the errors re run maven with the e switch error re run maven using the x switch to enable full debug logging error error for more information about the errors and possible solutions please read the following articles error error error after correcting the problems you can resume the build with the command error mvn rf shardingsphere infra optimize error process completed with exit code | 0 |
5,959 | 8,389,198,137 | IssuesEvent | 2018-10-09 08:56:40 | AdguardTeam/CoreLibs | https://api.github.com/repos/AdguardTeam/CoreLibs | closed | Check that QUIC v44 is blocked properly | P2: High compatibility | @ameshkov commented on [Sat Sep 15 2018](https://github.com/AdguardTeam/AdguardForWindows/issues/2335)
I've got a report that QUIC in Chrome 71 is not blocked properly.
Something has changed in QUIC v44, we should check what exactly.
| True | Check that QUIC v44 is blocked properly - @ameshkov commented on [Sat Sep 15 2018](https://github.com/AdguardTeam/AdguardForWindows/issues/2335)
I've got a report that QUIC in Chrome 71 is not blocked properly.
Something has changed in QUIC v44, we should check what exactly.
| non_usab | check that quic is blocked properly ameshkov commented on i ve got a report that quic in chrome is not blocked properly something has changed in quic we should check what exactly | 0 |
127,420 | 17,269,141,812 | IssuesEvent | 2021-07-22 17:19:00 | fecgov/fec-cms | https://api.github.com/repos/fecgov/fec-cms | opened | Begin A/B experiment for data landing page | Pairing opportunity Work: Front-end Work: UX/Design | **What we're after:**
Using [these designs](https://github.com/fecgov/fec-cms/issues/4790), we will begin an experiment on the data landing page to see how that affects user navigation to the [compare candidates/election search page](https://www.fec.gov/data/elections/?state=&cycle=2022&election_full=true).
**Completion criteria:**
- [ ] Experiment has begun
- [ ] Follow-up meeting ticket is created to schedule and conduct a review of the results | 1.0 | Begin A/B experiment for data landing page - **What we're after:**
Using [these designs](https://github.com/fecgov/fec-cms/issues/4790), we will begin an experiment on the data landing page to see how that affects user navigation to the [compare candidates/election search page](https://www.fec.gov/data/elections/?state=&cycle=2022&election_full=true).
**Completion criteria:**
- [ ] Experiment has begun
- [ ] Follow-up meeting ticket is created to schedule and conduct a review of the results | non_usab | begin a b experiment for data landing page what we re after using we will begin an experiment on the data landing page to see how that affects user navigation to the completion criteria experiment has begun follow up meeting ticket is created to schedule and conduct a review of the results | 0 |
105,568 | 23,072,473,189 | IssuesEvent | 2022-07-25 19:29:56 | octomation/maintainer | https://api.github.com/repos/octomation/maintainer | closed | pkg: file: register encoders for specific formats | kind: improvement difficulty: medium kind: feature scope: code scope: test | **Motivation:** it allows to simplify code like this
```go
var data HeatMap
format := strings.ToLower(filepath.Ext(file.Name()))
switch format {
case ".json":
err := json.NewDecoder(file).Decode(&data)
src.data = data
return data, err
case ".yml", ".yaml":
err := yaml.NewDecoder(file).Decode(&data)
src.data = data
return data, err
default:
return nil, fmt.Errorf("unsupported format: %s", format)
}
```
```go
func pack(file afero.File, data any) error {
format := strings.ToLower(filepath.Ext(file.Name()))
switch format {
case ".json":
return json.NewEncoder(file).Encode(data)
case ".yml", ".yaml":
return yaml.NewEncoder(file).Encode(data)
default:
return fmt.Errorf("unsupported format: %s", format)
}
}
func unpack(file afero.File, ptr any) error {
format := strings.ToLower(filepath.Ext(file.Name()))
switch format {
case ".json":
return json.NewDecoder(file).Decode(ptr)
case ".yml", ".yaml":
return yaml.NewDecoder(file).Decode(ptr)
default:
return fmt.Errorf("unsupported format: %s", format)
}
}
``` | 1.0 | pkg: file: register encoders for specific formats - **Motivation:** it allows to simplify code like this
```go
var data HeatMap
format := strings.ToLower(filepath.Ext(file.Name()))
switch format {
case ".json":
err := json.NewDecoder(file).Decode(&data)
src.data = data
return data, err
case ".yml", ".yaml":
err := yaml.NewDecoder(file).Decode(&data)
src.data = data
return data, err
default:
return nil, fmt.Errorf("unsupported format: %s", format)
}
```
```go
func pack(file afero.File, data any) error {
format := strings.ToLower(filepath.Ext(file.Name()))
switch format {
case ".json":
return json.NewEncoder(file).Encode(data)
case ".yml", ".yaml":
return yaml.NewEncoder(file).Encode(data)
default:
return fmt.Errorf("unsupported format: %s", format)
}
}
func unpack(file afero.File, ptr any) error {
format := strings.ToLower(filepath.Ext(file.Name()))
switch format {
case ".json":
return json.NewDecoder(file).Decode(ptr)
case ".yml", ".yaml":
return yaml.NewDecoder(file).Decode(ptr)
default:
return fmt.Errorf("unsupported format: %s", format)
}
}
``` | non_usab | pkg file register encoders for specific formats motivation it allows to simplify code like this go var data heatmap format strings tolower filepath ext file name switch format case json err json newdecoder file decode data src data data return data err case yml yaml err yaml newdecoder file decode data src data data return data err default return nil fmt errorf unsupported format s format go func pack file afero file data any error format strings tolower filepath ext file name switch format case json return json newencoder file encode data case yml yaml return yaml newencoder file encode data default return fmt errorf unsupported format s format func unpack file afero file ptr any error format strings tolower filepath ext file name switch format case json return json newdecoder file decode ptr case yml yaml return yaml newdecoder file decode ptr default return fmt errorf unsupported format s format | 0 |
19,306 | 13,796,929,657 | IssuesEvent | 2020-10-09 20:45:29 | joyent/conch-ui | https://api.github.com/repos/joyent/conch-ui | opened | create build -> add racks dialog is confusing | question usability | When adding racks to a new build --
does it make sense to list validated racks specifically (and I'm not sure what criteria you are using for determining this -- as "validated" is not a field on the rack table), as normally one would be creating a new build to add racks and devices to, where these items have not yet been preflighted.
@perigrin what do you think?
| True | create build -> add racks dialog is confusing - When adding racks to a new build --
does it make sense to list validated racks specifically (and I'm not sure what criteria you are using for determining this -- as "validated" is not a field on the rack table), as normally one would be creating a new build to add racks and devices to, where these items have not yet been preflighted.
@perigrin what do you think?
| usab | create build add racks dialog is confusing when adding racks to a new build does it make sense to list validated racks specifically and i m not sure what criteria you are using for determining this as validated is not a field on the rack table as normally one would be creating a new build to add racks and devices to where these items have not yet been preflighted perigrin what do you think | 1 |
19,092 | 13,536,133,892 | IssuesEvent | 2020-09-16 08:36:43 | topcoder-platform/qa-fun | https://api.github.com/repos/topcoder-platform/qa-fun | closed | Account logo not visible properly | UX/Usability | **Steps to Reproduce:**
1. Go to the link https://www.topcoder.com/settings/account
2. Observe some account logo not visible
**Expected Result:** Logo should visible and proper
**Actual Result:** Account logo image not proper and visible
**Screenshots or screencast:**
**Device/OS/Browser Information:**
Lenovo Thinkpad, Windows 10, Firefox 75.0
| True | Account logo not visible properly - **Steps to Reproduce:**
1. Go to the link https://www.topcoder.com/settings/account
2. Observe some account logo not visible
**Expected Result:** Logo should visible and proper
**Actual Result:** Account logo image not proper and visible
**Screenshots or screencast:**
**Device/OS/Browser Information:**
Lenovo Thinkpad, Windows 10, Firefox 75.0
| usab | account logo not visible properly steps to reproduce go to the link observe some account logo not visible expected result logo should visible and proper actual result account logo image not proper and visible screenshots or screencast device os browser information lenovo thinkpad windows firefox | 1 |
13,463 | 8,485,064,287 | IssuesEvent | 2018-10-26 06:18:52 | OctopusDeploy/Issues | https://api.github.com/repos/OctopusDeploy/Issues | opened | UI improve the lifecycles list for lifecycles that contain large numbers of environments/phases | area/usability kind/enhancement | # Prerequisites
- [x] I have searched [open](https://github.com/OctopusDeploy/Issues/issues) and [closed](https://github.com/OctopusDeploy/Issues/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aclosed) issues to make sure it isn't already requested
- [x] I have written a descriptive issue title
- [x] I have linked the original source of this feature request
- [x] I have tagged the issue appropriately (area/*, kind/enhancement)
# The problem
The lifecycles list screen does not scale well when you have lifecycles with many environments and/or phases. You end up with list items that are higher than the screen itself which makes the list pretty useless in terms of being able to scan it quickly for your lifecycle.
E.g. The problem:
<img width="1902" alt="screen shot 2018-10-26 at 4 11 51 pm" src="https://user-images.githubusercontent.com/819605/47547830-58720c80-d93a-11e8-8406-b6af7750b35c.png">
# The proposed solution
We plan to add a toggle similar to the one on the process sidebar for long lifecycles. When this kicks in, you'll simple see a Show/Hide button to allow you to expand/contract the actually lifecycle map. This will let you quickly scan the list of lifecycle names and, more importantly, **get to where you want to, faster**.
E.g. When fully collapsed:
<img width="1920" alt="screen shot 2018-10-26 at 4 12 08 pm" src="https://user-images.githubusercontent.com/819605/47547846-632ca180-d93a-11e8-8e80-1cc1ec5fc3a7.png">
E.g. When one is toggled:
<img width="1919" alt="screen shot 2018-10-26 at 4 12 47 pm" src="https://user-images.githubusercontent.com/819605/47547854-69228280-d93a-11e8-9799-97e553c22d36.png">
## Workarounds
There are no workarounds to this issue at present, other than using the filtering, which doesn't really help when the rows still take up so much height.
## Links
This was raised by a customer and feedback given internally:
> The lifecycle list page really sucked for them (#usability). They had some large lifecycles and the list on this page was impossible to scan because it was filled with a list of environments in each lifecycle. | True | UI improve the lifecycles list for lifecycles that contain large numbers of environments/phases - # Prerequisites
- [x] I have searched [open](https://github.com/OctopusDeploy/Issues/issues) and [closed](https://github.com/OctopusDeploy/Issues/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aclosed) issues to make sure it isn't already requested
- [x] I have written a descriptive issue title
- [x] I have linked the original source of this feature request
- [x] I have tagged the issue appropriately (area/*, kind/enhancement)
# The problem
The lifecycles list screen does not scale well when you have lifecycles with many environments and/or phases. You end up with list items that are higher than the screen itself which makes the list pretty useless in terms of being able to scan it quickly for your lifecycle.
E.g. The problem:
<img width="1902" alt="screen shot 2018-10-26 at 4 11 51 pm" src="https://user-images.githubusercontent.com/819605/47547830-58720c80-d93a-11e8-8406-b6af7750b35c.png">
# The proposed solution
We plan to add a toggle similar to the one on the process sidebar for long lifecycles. When this kicks in, you'll simple see a Show/Hide button to allow you to expand/contract the actually lifecycle map. This will let you quickly scan the list of lifecycle names and, more importantly, **get to where you want to, faster**.
E.g. When fully collapsed:
<img width="1920" alt="screen shot 2018-10-26 at 4 12 08 pm" src="https://user-images.githubusercontent.com/819605/47547846-632ca180-d93a-11e8-8e80-1cc1ec5fc3a7.png">
E.g. When one is toggled:
<img width="1919" alt="screen shot 2018-10-26 at 4 12 47 pm" src="https://user-images.githubusercontent.com/819605/47547854-69228280-d93a-11e8-9799-97e553c22d36.png">
## Workarounds
There are no workarounds to this issue at present, other than using the filtering, which doesn't really help when the rows still take up so much height.
## Links
This was raised by a customer and feedback given internally:
> The lifecycle list page really sucked for them (#usability). They had some large lifecycles and the list on this page was impossible to scan because it was filled with a list of environments in each lifecycle. | usab | ui improve the lifecycles list for lifecycles that contain large numbers of environments phases prerequisites i have searched and issues to make sure it isn t already requested i have written a descriptive issue title i have linked the original source of this feature request i have tagged the issue appropriately area kind enhancement the problem the lifecycles list screen does not scale well when you have lifecycles with many environments and or phases you end up with list items that are higher than the screen itself which makes the list pretty useless in terms of being able to scan it quickly for your lifecycle e g the problem img width alt screen shot at pm src the proposed solution we plan to add a toggle similar to the one on the process sidebar for long lifecycles when this kicks in you ll simple see a show hide button to allow you to expand contract the actually lifecycle map this will let you quickly scan the list of lifecycle names and more importantly get to where you want to faster e g when fully collapsed img width alt screen shot at pm src e g when one is toggled img width alt screen shot at pm src workarounds there are no workarounds to this issue at present other than using the filtering which doesn t really help when the rows still take up so much height links this was raised by a customer and feedback given internally the lifecycle list page really sucked for them usability they had some large lifecycles and the list on this page was impossible to scan because it was filled with a list of environments in each lifecycle | 1 |
284,550 | 24,607,786,809 | IssuesEvent | 2022-10-14 17:59:31 | rizinorg/rizin | https://api.github.com/repos/rizinorg/rizin | closed | Support MachO chained fixups (binaries compiled with XCode >= 13) | test-required Mach-O | > All programs and dylibs built with a deployment target of macOS 12 or iOS 15 or later now use the chained fixups format. This uses different load commands and LINKEDIT data, and won’t run or load on older OS versions. (49851380)
https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes | 1.0 | Support MachO chained fixups (binaries compiled with XCode >= 13) - > All programs and dylibs built with a deployment target of macOS 12 or iOS 15 or later now use the chained fixups format. This uses different load commands and LINKEDIT data, and won’t run or load on older OS versions. (49851380)
https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes | non_usab | support macho chained fixups binaries compiled with xcode all programs and dylibs built with a deployment target of macos or ios or later now use the chained fixups format this uses different load commands and linkedit data and won’t run or load on older os versions | 0 |
4,527 | 3,870,845,364 | IssuesEvent | 2016-04-11 07:02:59 | lionheart/openradar-mirror | https://api.github.com/repos/lionheart/openradar-mirror | opened | 22838491: Renaming .csr files does not recognize extension, is inconsistens and sets text selection incorrectly | classification:ui/usability reproducible:always status:open | #### Description
Summary:
Renaming .csr files does not recognize extension, is inconsistens and sets text selection incorrectly
Steps to Reproduce:
Cretate two files.
foo.pem and foo.csr (they could be a certificate a certificate signing request) It doesn't matter if there is actually any real content in the files.
Select one of the files and hit Enter to get into file renaming in the Finder.
Expected Results:
The .csr and .pem files should have the filename selected for renaming, but the extension (.csr or .pem) should not be selected to be
Actual Results:
With the .pem file, the extension is recognized and the selection spans the filename but leaves out the .pem extension.
.csr is not recognized as an extension. The complete filename is selected.
Regression:
I haven't seen this behaviour in older OS X versions. I haven't tested this in El Capitan 10.11. betas.
Notes:
n/a
-
Product Version: Finder 10.10.5
Created: 2015-09-24T15:11:58.350820
Originated: 2015-09-24T17:11:00
Open Radar Link: http://www.openradar.me/22838491 | True | 22838491: Renaming .csr files does not recognize extension, is inconsistens and sets text selection incorrectly - #### Description
Summary:
Renaming .csr files does not recognize extension, is inconsistens and sets text selection incorrectly
Steps to Reproduce:
Cretate two files.
foo.pem and foo.csr (they could be a certificate a certificate signing request) It doesn't matter if there is actually any real content in the files.
Select one of the files and hit Enter to get into file renaming in the Finder.
Expected Results:
The .csr and .pem files should have the filename selected for renaming, but the extension (.csr or .pem) should not be selected to be
Actual Results:
With the .pem file, the extension is recognized and the selection spans the filename but leaves out the .pem extension.
.csr is not recognized as an extension. The complete filename is selected.
Regression:
I haven't seen this behaviour in older OS X versions. I haven't tested this in El Capitan 10.11. betas.
Notes:
n/a
-
Product Version: Finder 10.10.5
Created: 2015-09-24T15:11:58.350820
Originated: 2015-09-24T17:11:00
Open Radar Link: http://www.openradar.me/22838491 | usab | renaming csr files does not recognize extension is inconsistens and sets text selection incorrectly description summary renaming csr files does not recognize extension is inconsistens and sets text selection incorrectly steps to reproduce cretate two files foo pem and foo csr they could be a certificate a certificate signing request it doesn t matter if there is actually any real content in the files select one of the files and hit enter to get into file renaming in the finder expected results the csr and pem files should have the filename selected for renaming but the extension csr or pem should not be selected to be actual results with the pem file the extension is recognized and the selection spans the filename but leaves out the pem extension csr is not recognized as an extension the complete filename is selected regression i haven t seen this behaviour in older os x versions i haven t tested this in el capitan betas notes n a product version finder created originated open radar link | 1 |
61,786 | 8,557,147,033 | IssuesEvent | 2018-11-08 15:02:56 | spacetelescope/jwql | https://api.github.com/repos/spacetelescope/jwql | opened | Add naming conventions to the Style Guide | Documentation Low Priority enhancement | We should have a dedicated section to our style guide that describes how certain things should be named within our project, e.g. instrument names (`NIRCam` vs `Nircam` vs `NIRCAM`), program IDs (string vs int) etc.
Credit @Johannes-Sahlmann for the idea | 1.0 | Add naming conventions to the Style Guide - We should have a dedicated section to our style guide that describes how certain things should be named within our project, e.g. instrument names (`NIRCam` vs `Nircam` vs `NIRCAM`), program IDs (string vs int) etc.
Credit @Johannes-Sahlmann for the idea | non_usab | add naming conventions to the style guide we should have a dedicated section to our style guide that describes how certain things should be named within our project e g instrument names nircam vs nircam vs nircam program ids string vs int etc credit johannes sahlmann for the idea | 0 |
4,206 | 3,769,963,935 | IssuesEvent | 2016-03-16 12:58:20 | zaproxy/zaproxy | https://api.github.com/repos/zaproxy/zaproxy | opened | Context Alert Filters - No Filter for Default Context on First Use | add-on bug Usability | If you have ZAP running and install it then open the properties of your Default Context (or any pre-existing context) it doesn't show the Alert Filter category. However, if you create a new context after adding the Alert Filter Addon you'll see it. OR, if you restart ZAP it shows for the Default Context.
| True | Context Alert Filters - No Filter for Default Context on First Use - If you have ZAP running and install it then open the properties of your Default Context (or any pre-existing context) it doesn't show the Alert Filter category. However, if you create a new context after adding the Alert Filter Addon you'll see it. OR, if you restart ZAP it shows for the Default Context.
| usab | context alert filters no filter for default context on first use if you have zap running and install it then open the properties of your default context or any pre existing context it doesn t show the alert filter category however if you create a new context after adding the alert filter addon you ll see it or if you restart zap it shows for the default context | 1 |
20,598 | 3,828,492,478 | IssuesEvent | 2016-03-31 06:08:16 | AeroScripts/QuestieDev | https://api.github.com/repos/AeroScripts/QuestieDev | closed | Questie Error in Desolace | test again | Picking up the below errors when I gathered the quests at Nijel's Point in Desolace.
_interface\addons\questie\QuestieQuest.lu
a:157: attempt to call global
‘QuestCompat_GetQuestLogTitle’ (a nil value)
interface\addons\questie\QuestieQuest.lu
a:294: attempt to call global
‘QuestCompat_GetQuestLogTitle’ (a nil value)
_
The errors won't disappear, and whilst present the map does not update to show questie drops / kills. | 1.0 | Questie Error in Desolace - Picking up the below errors when I gathered the quests at Nijel's Point in Desolace.
_interface\addons\questie\QuestieQuest.lu
a:157: attempt to call global
‘QuestCompat_GetQuestLogTitle’ (a nil value)
interface\addons\questie\QuestieQuest.lu
a:294: attempt to call global
‘QuestCompat_GetQuestLogTitle’ (a nil value)
_
The errors won't disappear, and whilst present the map does not update to show questie drops / kills. | non_usab | questie error in desolace picking up the below errors when i gathered the quests at nijel s point in desolace interface addons questie questiequest lu a attempt to call global ‘questcompat getquestlogtitle’ a nil value interface addons questie questiequest lu a attempt to call global ‘questcompat getquestlogtitle’ a nil value the errors won t disappear and whilst present the map does not update to show questie drops kills | 0 |
394,265 | 27,025,265,519 | IssuesEvent | 2023-02-11 14:19:25 | glass-dev/glass | https://api.github.com/repos/glass-dev/glass | opened | Add splash figure to documentation home | documentation | Add Fig. 2 from arXiv:2302-01942 as first image to the start page of the documentation.
It needs a transparent background and grey zoom-in lines that are visible both on light and dark backgrounds. | 1.0 | Add splash figure to documentation home - Add Fig. 2 from arXiv:2302-01942 as first image to the start page of the documentation.
It needs a transparent background and grey zoom-in lines that are visible both on light and dark backgrounds. | non_usab | add splash figure to documentation home add fig from arxiv as first image to the start page of the documentation it needs a transparent background and grey zoom in lines that are visible both on light and dark backgrounds | 0 |
285,796 | 31,155,600,730 | IssuesEvent | 2023-08-16 12:57:16 | nidhi7598/linux-4.1.15_CVE-2018-5873 | https://api.github.com/repos/nidhi7598/linux-4.1.15_CVE-2018-5873 | opened | CVE-2018-1000028 (High) detected in linuxlinux-4.1.52 | Mend: dependency security vulnerability | ## CVE-2018-1000028 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.1.52</b></p></summary>
<p>
<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
Linux kernel version after commit bdcf0a423ea1 - 4.15-rc4+, 4.14.8+, 4.9.76+, 4.4.111+ contains a Incorrect Access Control vulnerability in NFS server (nfsd) that can result in remote users reading or writing files they should not be able to via NFS. This attack appear to be exploitable via NFS server must export a filesystem with the "rootsquash" options enabled. This vulnerability appears to have been fixed in after commit 1995266727fa.
<p>Publish Date: 2018-02-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-1000028>CVE-2018-1000028</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.4</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-1000028">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-1000028</a></p>
<p>Release Date: 2018-02-09</p>
<p>Fix Resolution: v4.15</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2018-1000028 (High) detected in linuxlinux-4.1.52 - ## CVE-2018-1000028 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.1.52</b></p></summary>
<p>
<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
Linux kernel version after commit bdcf0a423ea1 - 4.15-rc4+, 4.14.8+, 4.9.76+, 4.4.111+ contains a Incorrect Access Control vulnerability in NFS server (nfsd) that can result in remote users reading or writing files they should not be able to via NFS. This attack appear to be exploitable via NFS server must export a filesystem with the "rootsquash" options enabled. This vulnerability appears to have been fixed in after commit 1995266727fa.
<p>Publish Date: 2018-02-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-1000028>CVE-2018-1000028</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.4</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-1000028">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-1000028</a></p>
<p>Release Date: 2018-02-09</p>
<p>Fix Resolution: v4.15</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_usab | cve high detected in linuxlinux cve high severity vulnerability vulnerable library linuxlinux the linux kernel library home page a href found in base branch master vulnerable source files vulnerability details linux kernel version after commit contains a incorrect access control vulnerability in nfs server nfsd that can result in remote users reading or writing files they should not be able to via nfs this attack appear to be exploitable via nfs server must export a filesystem with the rootsquash options enabled this vulnerability appears to have been fixed in after commit publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend | 0 |
48,707 | 2,999,486,923 | IssuesEvent | 2015-07-23 19:16:56 | jayway/powermock | https://api.github.com/repos/jayway/powermock | opened | Verify if the mockStatic may cause ClassNotFoundException | imported Milestone-Release1.6 Priority-Low Type-Task | _From [johan.ha...@gmail.com](https://code.google.com/u/105676376875942041029/) on November 26, 2009 08:06:15_
User report:
StaticClass.java:
package com.anoop.test;
public class StaticClass {
public static String getName(){
return "Anoop";
}
public static void setName(String name){
System.out.println(name);
}
}
AnoopClass.java:
package com.anoop.test;
public class AnoopClass {
private String name;
public void doSomething(){
name = StaticClass.getName();
name = name + " does something";
}
public String getName(){
return name;
}
}
The Junit class:
package com.anoop.test;
import static org.junit.Assert.*;
import org.junit.Before;
import org.junit.Test;
import org.junit.runner.RunWith;
import org.powermock.core.classloader.annotations.PrepareForTest;
import org.powermock.modules.junit4.PowerMockRunner;
import static org.powermock.api.easymock.PowerMock.*;
import static org.easymock. EasyMock .expect;
import static org.easymock. EasyMock .isA;
import static org.easymock. EasyMock .isNull;
@RunWith(PowerMockRunner.class)
@PrepareForTest({StaticClass.class})
public class AnoopClassTest {
private AnoopClass anoopClass;
@Before
public void setUp() throws Exception {
anoopClass = new AnoopClass();
}
@Test
public void testDoSomething() {
mockStatic(StaticClass.class);
expect(StaticClass.getName()).andReturn("Deepa");
replay(StaticClass.class);
anoopClass.doSomething();
System.out.println(anoopClass.getName());
verify(StaticClass.class);
}
}
Error trace:
java.lang.NoClassDefFoundError: com.anoop.test.StaticClass$
$EnhancerByCGLIB$$3caf6adf
at sun.reflect.GeneratedSerializationConstructorAccessor6.newInstance
(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Constructor.java:521)
at
org.easymock.classextension.internal.objenesis.instantiator.sun.SunReflectionFactoryInstantiator.newInstance
(SunReflectionFactoryInstantiator.java:40)
at
org.easymock.classextension.internal.objenesis.ObjenesisBase.newInstance
(ObjenesisBase.java:58)
at
org.easymock.classextension.internal.objenesis.ObjenesisHelper.newInstance
(ObjenesisHelper.java:28)
at
org.easymock.classextension.internal.ObjenesisClassInstantiator.newInstance
(ObjenesisClassInstantiator.java:12)
at
org.powermock.api.easymock.internal.signedsupport.SignedSupportingClassProxyFactory.createProxy
(SignedSupportingClassProxyFactory.java:201)
at org.easymock.internal.MocksControl.createMock(MocksControl.java:
40)
at org.powermock.api.easymock.PowerMock.doCreateMock(PowerMock.java:
2155)
at org.powermock.api.easymock.PowerMock.doMock(PowerMock.java:2110)
at org.powermock.api.easymock.PowerMock.mockStatic(PowerMock.java:
290)
at com.anoop.test.AnoopClassTest.testDoSomething(AnoopClassTest.java:
28)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at org.junit.internal.runners.TestMethod.invoke(TestMethod.java:66)
at
org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl
$PowerMockJUnit44MethodRunner.runTestMethod
(PowerMockJUnit44RunnerDelegateImpl.java:322)
at org.junit.internal.runners.MethodRoadie$2.run(MethodRoadie.java:
86)
at
org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters
(MethodRoadie.java:94)
at
org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl
$PowerMockJUnit44MethodRunner.executeTest
(PowerMockJUnit44RunnerDelegateImpl.java:309)
at
org.powermock.modules.junit4.internal.impl.PowerMockJUnit47RunnerDelegateImpl
$PowerMockJUnit47MethodRunner.executeTestInSuper
(PowerMockJUnit47RunnerDelegateImpl.java:73)
at
org.powermock.modules.junit4.internal.impl.PowerMockJUnit47RunnerDelegateImpl
$PowerMockJUnit47MethodRunner.executeTest
(PowerMockJUnit47RunnerDelegateImpl.java:53)
at
org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl
$PowerMockJUnit44MethodRunner.runBeforesThenTestThenAfters
(PowerMockJUnit44RunnerDelegateImpl.java:297)
at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:
84)
at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:49)
at
org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.invokeTestMethod
(PowerMockJUnit44RunnerDelegateImpl.java:222)
at
org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.runMethods
(PowerMockJUnit44RunnerDelegateImpl.java:161)
at
org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl
$1.run(PowerMockJUnit44RunnerDelegateImpl.java:135)
at org.junit.internal.runners.ClassRoadie.runUnprotected
(ClassRoadie.java:34)
at org.junit.internal.runners.ClassRoadie.runProtected
(ClassRoadie.java:44)
at
org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.run
(PowerMockJUnit44RunnerDelegateImpl.java:133)
at
org.powermock.modules.junit4.common.internal.impl.JUnit4TestSuiteChunkerImpl.run
(JUnit4TestSuiteChunkerImpl.java:112)
at
org.powermock.modules.junit4.common.internal.impl.AbstractCommonPowerMockRunner.run
(AbstractCommonPowerMockRunner.java:44)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run
(JUnit4TestReference.java:38)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run
(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests
(RemoteTestRunner.java:460)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests
(RemoteTestRunner.java:673)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run
(RemoteTestRunner.java:386)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main
(RemoteTestRunner.java:196)
_Original issue: http://code.google.com/p/powermock/issues/detail?id=208_ | 1.0 | Verify if the mockStatic may cause ClassNotFoundException - _From [johan.ha...@gmail.com](https://code.google.com/u/105676376875942041029/) on November 26, 2009 08:06:15_
User report:
StaticClass.java:
package com.anoop.test;
public class StaticClass {
public static String getName(){
return "Anoop";
}
public static void setName(String name){
System.out.println(name);
}
}
AnoopClass.java:
package com.anoop.test;
public class AnoopClass {
private String name;
public void doSomething(){
name = StaticClass.getName();
name = name + " does something";
}
public String getName(){
return name;
}
}
The Junit class:
package com.anoop.test;
import static org.junit.Assert.*;
import org.junit.Before;
import org.junit.Test;
import org.junit.runner.RunWith;
import org.powermock.core.classloader.annotations.PrepareForTest;
import org.powermock.modules.junit4.PowerMockRunner;
import static org.powermock.api.easymock.PowerMock.*;
import static org.easymock. EasyMock .expect;
import static org.easymock. EasyMock .isA;
import static org.easymock. EasyMock .isNull;
@RunWith(PowerMockRunner.class)
@PrepareForTest({StaticClass.class})
public class AnoopClassTest {
private AnoopClass anoopClass;
@Before
public void setUp() throws Exception {
anoopClass = new AnoopClass();
}
@Test
public void testDoSomething() {
mockStatic(StaticClass.class);
expect(StaticClass.getName()).andReturn("Deepa");
replay(StaticClass.class);
anoopClass.doSomething();
System.out.println(anoopClass.getName());
verify(StaticClass.class);
}
}
Error trace:
java.lang.NoClassDefFoundError: com.anoop.test.StaticClass$
$EnhancerByCGLIB$$3caf6adf
at sun.reflect.GeneratedSerializationConstructorAccessor6.newInstance
(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Constructor.java:521)
at
org.easymock.classextension.internal.objenesis.instantiator.sun.SunReflectionFactoryInstantiator.newInstance
(SunReflectionFactoryInstantiator.java:40)
at
org.easymock.classextension.internal.objenesis.ObjenesisBase.newInstance
(ObjenesisBase.java:58)
at
org.easymock.classextension.internal.objenesis.ObjenesisHelper.newInstance
(ObjenesisHelper.java:28)
at
org.easymock.classextension.internal.ObjenesisClassInstantiator.newInstance
(ObjenesisClassInstantiator.java:12)
at
org.powermock.api.easymock.internal.signedsupport.SignedSupportingClassProxyFactory.createProxy
(SignedSupportingClassProxyFactory.java:201)
at org.easymock.internal.MocksControl.createMock(MocksControl.java:
40)
at org.powermock.api.easymock.PowerMock.doCreateMock(PowerMock.java:
2155)
at org.powermock.api.easymock.PowerMock.doMock(PowerMock.java:2110)
at org.powermock.api.easymock.PowerMock.mockStatic(PowerMock.java:
290)
at com.anoop.test.AnoopClassTest.testDoSomething(AnoopClassTest.java:
28)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at org.junit.internal.runners.TestMethod.invoke(TestMethod.java:66)
at
org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl
$PowerMockJUnit44MethodRunner.runTestMethod
(PowerMockJUnit44RunnerDelegateImpl.java:322)
at org.junit.internal.runners.MethodRoadie$2.run(MethodRoadie.java:
86)
at
org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters
(MethodRoadie.java:94)
at
org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl
$PowerMockJUnit44MethodRunner.executeTest
(PowerMockJUnit44RunnerDelegateImpl.java:309)
at
org.powermock.modules.junit4.internal.impl.PowerMockJUnit47RunnerDelegateImpl
$PowerMockJUnit47MethodRunner.executeTestInSuper
(PowerMockJUnit47RunnerDelegateImpl.java:73)
at
org.powermock.modules.junit4.internal.impl.PowerMockJUnit47RunnerDelegateImpl
$PowerMockJUnit47MethodRunner.executeTest
(PowerMockJUnit47RunnerDelegateImpl.java:53)
at
org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl
$PowerMockJUnit44MethodRunner.runBeforesThenTestThenAfters
(PowerMockJUnit44RunnerDelegateImpl.java:297)
at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:
84)
at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:49)
at
org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.invokeTestMethod
(PowerMockJUnit44RunnerDelegateImpl.java:222)
at
org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.runMethods
(PowerMockJUnit44RunnerDelegateImpl.java:161)
at
org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl
$1.run(PowerMockJUnit44RunnerDelegateImpl.java:135)
at org.junit.internal.runners.ClassRoadie.runUnprotected
(ClassRoadie.java:34)
at org.junit.internal.runners.ClassRoadie.runProtected
(ClassRoadie.java:44)
at
org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.run
(PowerMockJUnit44RunnerDelegateImpl.java:133)
at
org.powermock.modules.junit4.common.internal.impl.JUnit4TestSuiteChunkerImpl.run
(JUnit4TestSuiteChunkerImpl.java:112)
at
org.powermock.modules.junit4.common.internal.impl.AbstractCommonPowerMockRunner.run
(AbstractCommonPowerMockRunner.java:44)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run
(JUnit4TestReference.java:38)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run
(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests
(RemoteTestRunner.java:460)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests
(RemoteTestRunner.java:673)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run
(RemoteTestRunner.java:386)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main
(RemoteTestRunner.java:196)
_Original issue: http://code.google.com/p/powermock/issues/detail?id=208_ | non_usab | verify if the mockstatic may cause classnotfoundexception from on november user report staticclass java package com anoop test public class staticclass public static string getname return anoop public static void setname string name system out println name anoopclass java package com anoop test public class anoopclass private string name public void dosomething name staticclass getname name name does something public string getname return name the junit class package com anoop test import static org junit assert import org junit before import org junit test import org junit runner runwith import org powermock core classloader annotations preparefortest import org powermock modules powermockrunner import static org powermock api easymock powermock import static org easymock easymock expect import static org easymock easymock isa import static org easymock easymock isnull runwith powermockrunner class preparefortest staticclass class public class anoopclasstest private anoopclass anoopclass before public void setup throws exception anoopclass new anoopclass test public void testdosomething mockstatic staticclass class expect staticclass getname andreturn deepa replay staticclass class anoopclass dosomething system out println anoopclass getname verify staticclass class error trace java lang noclassdeffounderror com anoop test staticclass enhancerbycglib at sun reflect newinstance unknown source at java lang reflect constructor newinstance constructor java at org easymock classextension internal objenesis instantiator sun sunreflectionfactoryinstantiator newinstance sunreflectionfactoryinstantiator java at org easymock classextension internal objenesis objenesisbase newinstance objenesisbase java at org easymock classextension internal objenesis objenesishelper newinstance objenesishelper java at org easymock classextension internal objenesisclassinstantiator newinstance objenesisclassinstantiator java at org powermock api easymock internal signedsupport signedsupportingclassproxyfactory createproxy signedsupportingclassproxyfactory java at org easymock internal mockscontrol createmock mockscontrol java at org powermock api easymock powermock docreatemock powermock java at org powermock api easymock powermock domock powermock java at org powermock api easymock powermock mockstatic powermock java at com anoop test anoopclasstest testdosomething anoopclasstest java at sun reflect nativemethodaccessorimpl native method at sun reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java lang reflect method invoke method java at org junit internal runners testmethod invoke testmethod java at org powermock modules internal impl runtestmethod java at org junit internal runners methodroadie run methodroadie java at org junit internal runners methodroadie runbeforesthentestthenafters methodroadie java at org powermock modules internal impl executetest java at org powermock modules internal impl executetestinsuper java at org powermock modules internal impl executetest java at org powermock modules internal impl runbeforesthentestthenafters java at org junit internal runners methodroadie runtest methodroadie java at org junit internal runners methodroadie run methodroadie java at org powermock modules internal impl invoketestmethod java at org powermock modules internal impl runmethods java at org powermock modules internal impl run java at org junit internal runners classroadie rununprotected classroadie java at org junit internal runners classroadie runprotected classroadie java at org powermock modules internal impl run java at org powermock modules common internal impl run java at org powermock modules common internal impl abstractcommonpowermockrunner run abstractcommonpowermockrunner java at org eclipse jdt internal runner run java at org eclipse jdt internal junit runner testexecution run testexecution java at org eclipse jdt internal junit runner remotetestrunner runtests remotetestrunner java at org eclipse jdt internal junit runner remotetestrunner runtests remotetestrunner java at org eclipse jdt internal junit runner remotetestrunner run remotetestrunner java at org eclipse jdt internal junit runner remotetestrunner main remotetestrunner java original issue | 0 |
255,835 | 21,959,449,003 | IssuesEvent | 2022-05-24 14:41:16 | xcat2/xcat-core | https://api.github.com/repos/xcat2/xcat-core | closed | xcattest check:output== does not execute | component:test | @gurevichmark recently discovered the following issue:
When running an xcattest testcase and checking for an exact string match in the output, the check does not execute:
```
# cat cases0
start:xcattest_checkoutput_exactmatch
description:check:output== match an exact string
label:mn_only,ci_test
cmd:echo "Test"
check:output==Test
end
# xcattest -t xcattest_checkoutput_exactmatch
...
------START::xcattest_checkoutput_exactmatch::Time:Wed Feb 16 13:55:01 2022------
RUN:echo "Test" [Wed Feb 16 13:55:01 2022]
ElapsedTime:0 sec
RETURN rc = 0
OUTPUT:
Test
------END::xcattest_checkoutput_exactmatch::Passed::Time:Wed Feb 16 13:55:01 2022 ::Duration::0 sec------
------Total: 1 , Failed: 0------
...
```
The expected result should either pass like this:
```
------START::xcattest_checkoutput_exactmatch::Time:Wed Feb 16 13:58:59 2022------
RUN:echo "Test" [Wed Feb 16 13:58:59 2022]
ElapsedTime:0 sec
RETURN rc = 0
OUTPUT:
Test
CHECK:output == Test [Pass]
------END::xcattest_checkoutput_exactmatch::Passed::Time:Wed Feb 16 13:58:59 2022 ::Duration::0 sec------
------Total: 1 , Failed: 0------
```
or fail like this:
```
------START::xcattest_checkoutput_exactmatch::Time:Wed Feb 16 14:02:17 2022------
RUN:echo "Test" [Wed Feb 16 14:02:17 2022]
ElapsedTime:0 sec
RETURN rc = 0
OUTPUT:
Test
CHECK:output == Test2 [Failed]
------END::xcattest_checkoutput_exactmatch::Failed::Time:Wed Feb 16 14:02:17 2022 ::Duration::0 sec------
------Total: 1 , Failed: 1------
```
| 1.0 | xcattest check:output== does not execute - @gurevichmark recently discovered the following issue:
When running an xcattest testcase and checking for an exact string match in the output, the check does not execute:
```
# cat cases0
start:xcattest_checkoutput_exactmatch
description:check:output== match an exact string
label:mn_only,ci_test
cmd:echo "Test"
check:output==Test
end
# xcattest -t xcattest_checkoutput_exactmatch
...
------START::xcattest_checkoutput_exactmatch::Time:Wed Feb 16 13:55:01 2022------
RUN:echo "Test" [Wed Feb 16 13:55:01 2022]
ElapsedTime:0 sec
RETURN rc = 0
OUTPUT:
Test
------END::xcattest_checkoutput_exactmatch::Passed::Time:Wed Feb 16 13:55:01 2022 ::Duration::0 sec------
------Total: 1 , Failed: 0------
...
```
The expected result should either pass like this:
```
------START::xcattest_checkoutput_exactmatch::Time:Wed Feb 16 13:58:59 2022------
RUN:echo "Test" [Wed Feb 16 13:58:59 2022]
ElapsedTime:0 sec
RETURN rc = 0
OUTPUT:
Test
CHECK:output == Test [Pass]
------END::xcattest_checkoutput_exactmatch::Passed::Time:Wed Feb 16 13:58:59 2022 ::Duration::0 sec------
------Total: 1 , Failed: 0------
```
or fail like this:
```
------START::xcattest_checkoutput_exactmatch::Time:Wed Feb 16 14:02:17 2022------
RUN:echo "Test" [Wed Feb 16 14:02:17 2022]
ElapsedTime:0 sec
RETURN rc = 0
OUTPUT:
Test
CHECK:output == Test2 [Failed]
------END::xcattest_checkoutput_exactmatch::Failed::Time:Wed Feb 16 14:02:17 2022 ::Duration::0 sec------
------Total: 1 , Failed: 1------
```
| non_usab | xcattest check output does not execute gurevichmark recently discovered the following issue when running an xcattest testcase and checking for an exact string match in the output the check does not execute cat start xcattest checkoutput exactmatch description check output match an exact string label mn only ci test cmd echo test check output test end xcattest t xcattest checkoutput exactmatch start xcattest checkoutput exactmatch time wed feb run echo test elapsedtime sec return rc output test end xcattest checkoutput exactmatch passed time wed feb duration sec total failed the expected result should either pass like this start xcattest checkoutput exactmatch time wed feb run echo test elapsedtime sec return rc output test check output test end xcattest checkoutput exactmatch passed time wed feb duration sec total failed or fail like this start xcattest checkoutput exactmatch time wed feb run echo test elapsedtime sec return rc output test check output end xcattest checkoutput exactmatch failed time wed feb duration sec total failed | 0 |
11,551 | 7,292,726,112 | IssuesEvent | 2018-02-25 05:13:39 | phan/phan | https://api.github.com/repos/phan/phan | closed | Dependency cycles can cause class hydration to fail | bug usability | With the following code, the method `C::e` does not get imported into the definition of class `A`.
``` php
<?php
class B extends C {
public function d() : A {
return new A;
}
}
class C {
public $p = A::class;
public static function e() {}
}
class A extends B {
private function f() {
self::e();
}
}
```
The issue is that the order of hydration goes `B -> C -> A`. Since `C` depends on `A`, it needs to be hydrated before `C` can be hydrated. When we go to hydrate `A`, it will attempt to import properties, methods and constants from `B`, but since it is mid-process with hydration, it will refuse to do it again (cycle prevention) and nothing from `B` will make it into `A`.
| True | Dependency cycles can cause class hydration to fail - With the following code, the method `C::e` does not get imported into the definition of class `A`.
``` php
<?php
class B extends C {
public function d() : A {
return new A;
}
}
class C {
public $p = A::class;
public static function e() {}
}
class A extends B {
private function f() {
self::e();
}
}
```
The issue is that the order of hydration goes `B -> C -> A`. Since `C` depends on `A`, it needs to be hydrated before `C` can be hydrated. When we go to hydrate `A`, it will attempt to import properties, methods and constants from `B`, but since it is mid-process with hydration, it will refuse to do it again (cycle prevention) and nothing from `B` will make it into `A`.
| usab | dependency cycles can cause class hydration to fail with the following code the method c e does not get imported into the definition of class a php php class b extends c public function d a return new a class c public p a class public static function e class a extends b private function f self e the issue is that the order of hydration goes b c a since c depends on a it needs to be hydrated before c can be hydrated when we go to hydrate a it will attempt to import properties methods and constants from b but since it is mid process with hydration it will refuse to do it again cycle prevention and nothing from b will make it into a | 1 |
10,541 | 6,794,173,740 | IssuesEvent | 2017-11-01 10:57:38 | ElektraInitiative/libelektra | https://api.github.com/repos/ElektraInitiative/libelektra | opened | INI: Elektra Removes Metadata | bug usability | # Description
It looks like Elektra removes metadata if we use **INI as default storage** plugin and store data using a **cascading key**.
# Steps to Reproduce the Problem
1. Configure Elektra with INI as default storage:
```sh
mkdir build
cd build
cmake .. -GNinja -DPLUGINS='ALL' -DKDB_DB_FILE='default.ini' -DKDB_DB_INIT='elektra.ini' -DKDB_DEFAULT_STORAGE=ini
```
2. Build Elektra:
```sh
ninja
```
3. Run the following commands:
```sh
# Mount yamlcpp plugin to cascading namespace `/examples/yamlcpp`
kdb mount config.yaml /examples/yamlcpp yamlcpp
# Add a new key and add some metadata to the new key
kdb set /examples/yamlcpp/brand new
kdb setmeta /examples/yamlcpp/brand comment "The Devil And God Are Raging Inside Me"
kdb setmeta /examples/yamlcpp/brand rationale "Because I Love It"
# Retrieve metadata
kdb lsmeta /examples/yamlcpp/brand
```
# Expected Result
```sh
#> comment
#> rationale
```
# Actual Result
```sh
#> rationale
```
# Additional Information
Everything works fine if we do not use cascading keys:
```sh
# Mount yamlcpp plugin to cascading namespace `/examples/yamlcpp`
kdb mount config.yaml user/examples/yamlcpp yamlcpp
# Add a new key and add some metadata to the new key
kdb set user/examples/yamlcpp/brand new
kdb setmeta user/examples/yamlcpp/brand comment "The Devil And God Are Raging Inside Me"
kdb setmeta user/examples/yamlcpp/brand rationale "Because I Love It"
# Retrieve metadata
kdb lsmeta user/examples/yamlcpp/brand
#> comment
#> rationale
```
# System Information
- Elektra Version: master
| True | INI: Elektra Removes Metadata - # Description
It looks like Elektra removes metadata if we use **INI as default storage** plugin and store data using a **cascading key**.
# Steps to Reproduce the Problem
1. Configure Elektra with INI as default storage:
```sh
mkdir build
cd build
cmake .. -GNinja -DPLUGINS='ALL' -DKDB_DB_FILE='default.ini' -DKDB_DB_INIT='elektra.ini' -DKDB_DEFAULT_STORAGE=ini
```
2. Build Elektra:
```sh
ninja
```
3. Run the following commands:
```sh
# Mount yamlcpp plugin to cascading namespace `/examples/yamlcpp`
kdb mount config.yaml /examples/yamlcpp yamlcpp
# Add a new key and add some metadata to the new key
kdb set /examples/yamlcpp/brand new
kdb setmeta /examples/yamlcpp/brand comment "The Devil And God Are Raging Inside Me"
kdb setmeta /examples/yamlcpp/brand rationale "Because I Love It"
# Retrieve metadata
kdb lsmeta /examples/yamlcpp/brand
```
# Expected Result
```sh
#> comment
#> rationale
```
# Actual Result
```sh
#> rationale
```
# Additional Information
Everything works fine if we do not use cascading keys:
```sh
# Mount yamlcpp plugin to cascading namespace `/examples/yamlcpp`
kdb mount config.yaml user/examples/yamlcpp yamlcpp
# Add a new key and add some metadata to the new key
kdb set user/examples/yamlcpp/brand new
kdb setmeta user/examples/yamlcpp/brand comment "The Devil And God Are Raging Inside Me"
kdb setmeta user/examples/yamlcpp/brand rationale "Because I Love It"
# Retrieve metadata
kdb lsmeta user/examples/yamlcpp/brand
#> comment
#> rationale
```
# System Information
- Elektra Version: master
| usab | ini elektra removes metadata description it looks like elektra removes metadata if we use ini as default storage plugin and store data using a cascading key steps to reproduce the problem configure elektra with ini as default storage sh mkdir build cd build cmake gninja dplugins all dkdb db file default ini dkdb db init elektra ini dkdb default storage ini build elektra sh ninja run the following commands sh mount yamlcpp plugin to cascading namespace examples yamlcpp kdb mount config yaml examples yamlcpp yamlcpp add a new key and add some metadata to the new key kdb set examples yamlcpp brand new kdb setmeta examples yamlcpp brand comment the devil and god are raging inside me kdb setmeta examples yamlcpp brand rationale because i love it retrieve metadata kdb lsmeta examples yamlcpp brand expected result sh comment rationale actual result sh rationale additional information everything works fine if we do not use cascading keys sh mount yamlcpp plugin to cascading namespace examples yamlcpp kdb mount config yaml user examples yamlcpp yamlcpp add a new key and add some metadata to the new key kdb set user examples yamlcpp brand new kdb setmeta user examples yamlcpp brand comment the devil and god are raging inside me kdb setmeta user examples yamlcpp brand rationale because i love it retrieve metadata kdb lsmeta user examples yamlcpp brand comment rationale system information elektra version master | 1 |
27,654 | 30,023,888,928 | IssuesEvent | 2023-06-27 03:26:40 | ZcashFoundation/zebra | https://api.github.com/repos/ZcashFoundation/zebra | opened | Make the Zebra logo fit in a standard 80 character terminal width | C-bug S-needs-triage P-Low :snowflake: I-usability A-diagnostics | ### What happened?
I expected to see this happen:
Like `zcashd`, Zebra's default config should fit in a standard 80x24 character terminal.
Instead, this happened:
<img width="878" alt="Screenshot 2023-06-27 at 13 23 58" src="https://github.com/ZcashFoundation/zebra/assets/8951843/5b5ab9da-75b7-4f62-8ab4-aa91dfa5fa8e">
### What were you doing when the issue happened?
Ran command `zebrad` on PR #6945, which is going to merge to `main` soon.
### Zebra logs
Thank you for running a mainnet zebrad 1.0.0 node!
You're helping to strengthen the network and contributing to a social good :)
2023-06-27T03:21:05.970176Z INFO zebrad::components::tracing::component: started tracing component filter="info" TRACING_STATIC_MAX_LEVEL=LevelFilter::INFO LOG_STATIC_MAX_LEVEL=Info
2023-06-27T03:21:05.970255Z INFO zebrad::application: Diagnostic Metadata:
version: 1.0.0
Zcash network: Mainnet
state version: 25
features: default,release_max_level_info
branch: main
git commit: 3a96056
commit timestamp: 2023-06-26T23:11:57.000000000Z
target triple: aarch64-apple-darwin
rust compiler: 1.70.0
rust release date: 2023-05-31
optimization level: 3
debug checks: false
2023-06-27T03:21:05.970265Z INFO zebrad::application: loaded zebrad config config_path=None config=ZebradConfig { consensus: Config { checkpoint_sync: true, debug_skip_parameter_preload: false }, metrics: Config { endpoint_addr: None }, network: Config { listen_addr: 0.0.0.0:8233, network: Mainnet, initial_mainnet_peers: {"dnsseed.z.cash:8233", "dnsseed.str4d.xyz:8233", "mainnet.seeder.zfnd.org:8233", "mainnet.is.yolo.money:8233"}, initial_testnet_peers: {"dnsseed.testnet.z.cash:18233", "testnet.seeder.zfnd.org:18233", "testnet.is.yolo.money:18233"}, cache_dir: IsEnabled(true), peerset_initial_target_size: 25, crawl_new_peer_interval: 61s, max_connections_per_ip: 1 }, state: Config { cache_dir: "/Users/hyper/Library/Caches/zebra", ephemeral: false, debug_stop_at_height: None, delete_old_database: true }, tracing: Config { use_color: true, force_use_color: false, filter: None, buffer_limit: 128000, endpoint_addr: None, flamegraph: None, log_file: None, use_journald: false }, sync: Config { download_concurrency_limit: 50, checkpoint_verify_concurrency_limit: 1000, full_verify_concurrency_limit: 20, parallel_cpu_threads: 0 }, mempool: Config { tx_cost_limit: 80000000, eviction_memory_time: 3600s, debug_enable_at_height: None }, rpc: Config { listen_addr: None, parallel_cpu_threads: 1, debug_force_finished_sync: false } }
### Zebra Version
Commit 3a96056 (1.0.0 + PR #6945)
### Which operating systems does the issue happen on?
- [X] Linux
- [X] macOS
- [ ] Windows
- [ ] Other OS
### OS details
Darwin machine-name 22.3.0 Darwin Kernel Version 22.3.0: Thu Jan 5 20:48:54 PST 2023; root:xnu-8792.81.2~2/RELEASE_ARM64_T6000 arm64
### Additional information
We just need to make the terminal images a little smaller. | True | Make the Zebra logo fit in a standard 80 character terminal width - ### What happened?
I expected to see this happen:
Like `zcashd`, Zebra's default config should fit in a standard 80x24 character terminal.
Instead, this happened:
<img width="878" alt="Screenshot 2023-06-27 at 13 23 58" src="https://github.com/ZcashFoundation/zebra/assets/8951843/5b5ab9da-75b7-4f62-8ab4-aa91dfa5fa8e">
### What were you doing when the issue happened?
Ran command `zebrad` on PR #6945, which is going to merge to `main` soon.
### Zebra logs
Thank you for running a mainnet zebrad 1.0.0 node!
You're helping to strengthen the network and contributing to a social good :)
2023-06-27T03:21:05.970176Z INFO zebrad::components::tracing::component: started tracing component filter="info" TRACING_STATIC_MAX_LEVEL=LevelFilter::INFO LOG_STATIC_MAX_LEVEL=Info
2023-06-27T03:21:05.970255Z INFO zebrad::application: Diagnostic Metadata:
version: 1.0.0
Zcash network: Mainnet
state version: 25
features: default,release_max_level_info
branch: main
git commit: 3a96056
commit timestamp: 2023-06-26T23:11:57.000000000Z
target triple: aarch64-apple-darwin
rust compiler: 1.70.0
rust release date: 2023-05-31
optimization level: 3
debug checks: false
2023-06-27T03:21:05.970265Z INFO zebrad::application: loaded zebrad config config_path=None config=ZebradConfig { consensus: Config { checkpoint_sync: true, debug_skip_parameter_preload: false }, metrics: Config { endpoint_addr: None }, network: Config { listen_addr: 0.0.0.0:8233, network: Mainnet, initial_mainnet_peers: {"dnsseed.z.cash:8233", "dnsseed.str4d.xyz:8233", "mainnet.seeder.zfnd.org:8233", "mainnet.is.yolo.money:8233"}, initial_testnet_peers: {"dnsseed.testnet.z.cash:18233", "testnet.seeder.zfnd.org:18233", "testnet.is.yolo.money:18233"}, cache_dir: IsEnabled(true), peerset_initial_target_size: 25, crawl_new_peer_interval: 61s, max_connections_per_ip: 1 }, state: Config { cache_dir: "/Users/hyper/Library/Caches/zebra", ephemeral: false, debug_stop_at_height: None, delete_old_database: true }, tracing: Config { use_color: true, force_use_color: false, filter: None, buffer_limit: 128000, endpoint_addr: None, flamegraph: None, log_file: None, use_journald: false }, sync: Config { download_concurrency_limit: 50, checkpoint_verify_concurrency_limit: 1000, full_verify_concurrency_limit: 20, parallel_cpu_threads: 0 }, mempool: Config { tx_cost_limit: 80000000, eviction_memory_time: 3600s, debug_enable_at_height: None }, rpc: Config { listen_addr: None, parallel_cpu_threads: 1, debug_force_finished_sync: false } }
### Zebra Version
Commit 3a96056 (1.0.0 + PR #6945)
### Which operating systems does the issue happen on?
- [X] Linux
- [X] macOS
- [ ] Windows
- [ ] Other OS
### OS details
Darwin machine-name 22.3.0 Darwin Kernel Version 22.3.0: Thu Jan 5 20:48:54 PST 2023; root:xnu-8792.81.2~2/RELEASE_ARM64_T6000 arm64
### Additional information
We just need to make the terminal images a little smaller. | usab | make the zebra logo fit in a standard character terminal width what happened i expected to see this happen like zcashd zebra s default config should fit in a standard character terminal instead this happened img width alt screenshot at src what were you doing when the issue happened ran command zebrad on pr which is going to merge to main soon zebra logs thank you for running a mainnet zebrad node you re helping to strengthen the network and contributing to a social good info zebrad components tracing component started tracing component filter info tracing static max level levelfilter info log static max level info info zebrad application diagnostic metadata version zcash network mainnet state version features default release max level info branch main git commit commit timestamp target triple apple darwin rust compiler rust release date optimization level debug checks false info zebrad application loaded zebrad config config path none config zebradconfig consensus config checkpoint sync true debug skip parameter preload false metrics config endpoint addr none network config listen addr network mainnet initial mainnet peers dnsseed z cash dnsseed xyz mainnet seeder zfnd org mainnet is yolo money initial testnet peers dnsseed testnet z cash testnet seeder zfnd org testnet is yolo money cache dir isenabled true peerset initial target size crawl new peer interval max connections per ip state config cache dir users hyper library caches zebra ephemeral false debug stop at height none delete old database true tracing config use color true force use color false filter none buffer limit endpoint addr none flamegraph none log file none use journald false sync config download concurrency limit checkpoint verify concurrency limit full verify concurrency limit parallel cpu threads mempool config tx cost limit eviction memory time debug enable at height none rpc config listen addr none parallel cpu threads debug force finished sync false zebra version commit pr which operating systems does the issue happen on linux macos windows other os os details darwin machine name darwin kernel version thu jan pst root xnu release additional information we just need to make the terminal images a little smaller | 1 |
6,346 | 4,232,322,699 | IssuesEvent | 2016-07-04 22:01:27 | lionheart/openradar-mirror | https://api.github.com/repos/lionheart/openradar-mirror | opened | 27163184: Xcode8 - building after a purge-build-folder yields bizarre errors | classification:ui/usability reproducible:sometimes status:open | #### Description
Summary:
I often clean my build folder (option-click on the menu item) to get Xcode's head back in to a good place.
Every now and then I get bizarre errors.
video showing the problem is attached
The project in question is attached. This follows close on the heels of rdar://27163150 , trying to figure out ways of getting it to work.
also attached is a screen shot of the errors from the log.
Steps to Reproduce:
1. purge build folder
2. rebuild with new clean slate
Expected Results:
3. build happens normally
Actual Results:
3. bizarre errors.
Version:
Version 8.0 beta (8S128d)
10.11.4 (15E65)
Notes:
It's really not that big a deal - just ignore new build errors and try rebuilding again , but
when it happens day-in, day-out, it's just another heavy-sigh
death-of-a-thousand-cuts that makes using Xcode unpleasant.
Configuration:
Attachments:
'ObjCInterop.zip', 'Screen Shot 2016-07-04 at 5.53.01 PM.png' and 'bizarro-world.mp4' were successfully uploaded.
-
Product Version: Version 8.0 beta (8S128d)
Created: 2016-07-04T21:57:40.278800
Originated: 2016-07-04T00:00:00
Open Radar Link: http://www.openradar.me/27163184 | True | 27163184: Xcode8 - building after a purge-build-folder yields bizarre errors - #### Description
Summary:
I often clean my build folder (option-click on the menu item) to get Xcode's head back in to a good place.
Every now and then I get bizarre errors.
video showing the problem is attached
The project in question is attached. This follows close on the heels of rdar://27163150 , trying to figure out ways of getting it to work.
also attached is a screen shot of the errors from the log.
Steps to Reproduce:
1. purge build folder
2. rebuild with new clean slate
Expected Results:
3. build happens normally
Actual Results:
3. bizarre errors.
Version:
Version 8.0 beta (8S128d)
10.11.4 (15E65)
Notes:
It's really not that big a deal - just ignore new build errors and try rebuilding again , but
when it happens day-in, day-out, it's just another heavy-sigh
death-of-a-thousand-cuts that makes using Xcode unpleasant.
Configuration:
Attachments:
'ObjCInterop.zip', 'Screen Shot 2016-07-04 at 5.53.01 PM.png' and 'bizarro-world.mp4' were successfully uploaded.
-
Product Version: Version 8.0 beta (8S128d)
Created: 2016-07-04T21:57:40.278800
Originated: 2016-07-04T00:00:00
Open Radar Link: http://www.openradar.me/27163184 | usab | building after a purge build folder yields bizarre errors description summary i often clean my build folder option click on the menu item to get xcode s head back in to a good place every now and then i get bizarre errors video showing the problem is attached the project in question is attached this follows close on the heels of rdar trying to figure out ways of getting it to work also attached is a screen shot of the errors from the log steps to reproduce purge build folder rebuild with new clean slate expected results build happens normally actual results bizarre errors version version beta notes it s really not that big a deal just ignore new build errors and try rebuilding again but when it happens day in day out it s just another heavy sigh death of a thousand cuts that makes using xcode unpleasant configuration attachments objcinterop zip screen shot at pm png and bizarro world were successfully uploaded product version version beta created originated open radar link | 1 |
27,713 | 30,250,033,989 | IssuesEvent | 2023-07-06 19:44:30 | bisq-network/bisq | https://api.github.com/repos/bisq-network/bisq | closed | Use OS native notifications | re:usability good first issue on:Windows on:Linux on:macOS | We use simulated notifiactions as JavaFX does not support native OS notifiactions. Find solutions to use native notifacitions.
See: http://mail.openjdk.java.net/pipermail/openjfx-dev/2014-September/015827.html
<!---
@huboard:{"order":321.6875010132817,"milestone_order":157,"custom_state":""}
-->
| True | Use OS native notifications - We use simulated notifiactions as JavaFX does not support native OS notifiactions. Find solutions to use native notifacitions.
See: http://mail.openjdk.java.net/pipermail/openjfx-dev/2014-September/015827.html
<!---
@huboard:{"order":321.6875010132817,"milestone_order":157,"custom_state":""}
-->
| usab | use os native notifications we use simulated notifiactions as javafx does not support native os notifiactions find solutions to use native notifacitions see huboard order milestone order custom state | 1 |
89,055 | 8,188,700,428 | IssuesEvent | 2018-08-30 03:30:02 | dotnet/project-system | https://api.github.com/repos/dotnet/project-system | opened | Integration tests are failing indeterminately with MEF composition issue | Test | ```
20:10:46 Debug Trace:
20:10:46 Error loading dependency assembly 'Microsoft.Test.Apex.TeamFoundation, PublicKeyToken=b03f5f7f11d50a3a' of 'Microsoft.Test.Apex.SourceControlIntegration.dll' for operations composition container. Dependencies from this assembly will be missing in the composition. Could not load file or assembly 'Microsoft.Test.Apex.TeamFoundation, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG))
20:10:46 Populating Assembly Catalog: ApexAssemblyCatalog (attributed with [ProvidesOperationsExtensionAttribute])
20:10:46 Failed to load assembly Microsoft.VisualStudio.TestTools.UnitTesting.AssertInconclusiveException while looking for exports. Exception: System.TypeLoadException: Cannot find type System.Exception in module System.Runtime.dll.
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyModule.ResolveTypeRef(ITypeReference typeReference)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyTypeReference.GetResolvedTypeWorker()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetResolvedType()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetCustomAttributesData()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.HasAttributes(Type targetType, Boolean validateInheritedAttributes, Type[] attributeTypes)
20:10:46 at Microsoft.Test.Apex.ApexTypeUniverse.<GetExportedTypes>d__11.MoveNext()
20:10:46 Failed to load assembly Microsoft.VisualStudio.TestTools.UnitTesting.InternalTestFailureException while looking for exports. Exception: System.TypeLoadException: Cannot find type System.Exception in module System.Runtime.dll.
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyModule.ResolveTypeRef(ITypeReference typeReference)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyTypeReference.GetResolvedTypeWorker()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetResolvedType()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetCustomAttributesData()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.HasAttributes(Type targetType, Boolean validateInheritedAttributes, Type[] attributeTypes)
20:10:46 at Microsoft.Test.Apex.ApexTypeUniverse.<GetExportedTypes>d__11.MoveNext()
20:10:46 Failed to load assembly Microsoft.VisualStudio.TestTools.UnitTesting.ExpectedExceptionAttribute while looking for exports. Exception: System.TypeLoadException: Cannot find type System.Attribute in module System.Runtime.dll.
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyModule.ResolveTypeRef(ITypeReference typeReference)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyTypeReference.GetResolvedTypeWorker()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetResolvedType()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetCustomAttributesData()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.HasAttributes(Type targetType, Boolean validateInheritedAttributes, Type[] attributeTypes)
20:10:46 at Microsoft.Test.Apex.ApexTypeUniverse.<GetExportedTypes>d__11.MoveNext()
20:10:46 Failed to load assembly Microsoft.VisualStudio.TestTools.UnitTesting.TestCategoryAttribute while looking for exports. Exception: System.TypeLoadException: Cannot find type System.Attribute in module System.Runtime.dll.
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyModule.ResolveTypeRef(ITypeReference typeReference)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyTypeReference.GetResolvedTypeWorker()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetResolvedType()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetCustomAttributesData()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.HasAttributes(Type targetType, Boolean validateInheritedAttributes, Type[] attributeTypes)
20:10:46 at Microsoft.Test.Apex.ApexTypeUniverse.<GetExportedTypes>d__11.MoveNext()
20:10:46 Failed to load assembly Microsoft.VisualStudio.TestTools.UnitTesting.AssertFailedException while looking for exports. Exception: System.TypeLoadException: Cannot find type System.Exception in module System.Runtime.dll.
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyModule.ResolveTypeRef(ITypeReference typeReference)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyTypeReference.GetResolvedTypeWorker()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetResolvedType()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetCustomAttributesData()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.HasAttributes(Type targetType, Boolean validateInheritedAttributes, Type[] attributeTypes)
20:10:46 at Microsoft.Test.Apex.ApexTypeUniverse.<GetExportedTypes>d__11.MoveNext()
20:10:46 Failed to load assembly Microsoft.VisualStudio.TestTools.UnitTesting.DataTestMethodAttribute while looking for exports. Exception: System.TypeLoadException: Cannot find type System.Attribute in module System.Runtime.dll.
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyModule.ResolveTypeRef(ITypeReference typeReference)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyTypeReference.GetResolvedTypeWorker()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetResolvedType()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetCustomAttributesData()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.HasAttributes(Type targetType, Boolean validateInheritedAttributes, Type[] attributeTypes)
20:10:46 at Microsoft.Test.Apex.ApexTypeUniverse.<GetExportedTypes>d__11.MoveNext()
20:10:46 Failed to load assembly Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute while looking for exports. Exception: System.TypeLoadException: Cannot find type System.Attribute in module System.Runtime.dll.
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyModule.ResolveTypeRef(ITypeReference typeReference)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyTypeReference.GetResolvedTypeWorker()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetResolvedType()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetCustomAttributesData()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.HasAttributes(Type targetType, Boolean validateInheritedAttributes, Type[] attributeTypes)
20:10:46 at Microsoft.Test.Apex.ApexTypeUniverse.<GetExportedTypes>d__11.MoveNext()
20:10:46 Failed to load assembly Microsoft.VisualStudio.TestTools.UnitTesting.CssProjectStructureAttribute while looking for exports. Exception: System.TypeLoadException: Cannot find type System.Attribute in module System.Runtime.dll.
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyModule.ResolveTypeRef(ITypeReference typeReference)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyTypeReference.GetResolvedTypeWorker()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetResolvedType()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetCustomAttributesData()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.HasAttributes(Type targetType, Boolean validateInheritedAttributes, Type[] attributeTypes)
20:10:46 at Microsoft.Test.Apex.ApexTypeUniverse.<GetExportedTypes>d__11.MoveNext()
20:10:46 Failed to load assembly Microsoft.VisualStudio.TestTools.UnitTesting.CssIterationAttribute while looking for exports. Exception: System.TypeLoadException: Cannot find type System.Attribute in module System.Runtime.dll.
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyModule.ResolveTypeRef(ITypeReference typeReference)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyTypeReference.GetResolvedTypeWorker()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetResolvedType()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetCustomAttributesData()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.HasAttributes(Type targetType, Boolean validateInheritedAttributes, Type[] attributeTypes)
20:10:46 at Microsoft.Test.Apex.ApexTypeUniverse.<GetExportedTypes>d__11.MoveNext()
20:10:46 Failed to load assembly Microsoft.VisualStudio.TestTools.UnitTesting.WorkItemAttribute while looking for exports. Exception: System.TypeLoadException: Cannot find type System.Attribute in module System.Runtime.dll.
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyModule.ResolveTypeRef(ITypeReference typeReference)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyTypeReference.GetResolvedTypeWorker()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetResolvedType()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetCustomAttributesData()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.HasAttributes(Type targetType, Boolean validateInheritedAttributes, Type[] attributeTypes)
20:10:46 at Microsoft.Test.Apex.ApexTypeUniverse.<GetExportedTypes>d__11.MoveNext()
20:10:46 Found 78 exported, and 0 unexportable types from assemblies 'Microsoft.Test.Apex.Framework.dll, Microsoft.Test.Apex.VSTestIntegration.dll, Microsoft.VisualStudio.ProjectSystem.IntegrationTests.dll, Microsoft.VisualStudio.TestPlatform.TestFramework.dll, Microsoft.VisualStudio.TestPlatform.TestFramework.Extensions.dll, Microsoft.Test.Apex.VisualStudio.dll, Microsoft.Test.Apex.VisualStudio.Hosting.dll, Microsoft.Test.Apex.OsIntegration.dll, Microsoft.Test.Apex.SourceControlIntegration.dll'
20:10:46
20:10:46 Failed to load Omni log dll: System.IO.FileNotFoundException: Could not load file or assembly 'Omni.Logging.Extended' or one of its dependencies. The system cannot find the file specified.
20:10:46 File name: 'Omni.Logging.Extended'
20:10:46 at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
20:10:46 at System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
20:10:46 at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
20:10:46 at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection)
20:10:46 at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
20:10:46 at System.Reflection.Assembly.Load(String assemblyString)
20:10:46 at Microsoft.Test.Apex.Services.Logging.TestLoggerSinks.OmniLog.OmniLogSink..ctor()
``` | 1.0 | Integration tests are failing indeterminately with MEF composition issue - ```
20:10:46 Debug Trace:
20:10:46 Error loading dependency assembly 'Microsoft.Test.Apex.TeamFoundation, PublicKeyToken=b03f5f7f11d50a3a' of 'Microsoft.Test.Apex.SourceControlIntegration.dll' for operations composition container. Dependencies from this assembly will be missing in the composition. Could not load file or assembly 'Microsoft.Test.Apex.TeamFoundation, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG))
20:10:46 Populating Assembly Catalog: ApexAssemblyCatalog (attributed with [ProvidesOperationsExtensionAttribute])
20:10:46 Failed to load assembly Microsoft.VisualStudio.TestTools.UnitTesting.AssertInconclusiveException while looking for exports. Exception: System.TypeLoadException: Cannot find type System.Exception in module System.Runtime.dll.
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyModule.ResolveTypeRef(ITypeReference typeReference)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyTypeReference.GetResolvedTypeWorker()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetResolvedType()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetCustomAttributesData()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.HasAttributes(Type targetType, Boolean validateInheritedAttributes, Type[] attributeTypes)
20:10:46 at Microsoft.Test.Apex.ApexTypeUniverse.<GetExportedTypes>d__11.MoveNext()
20:10:46 Failed to load assembly Microsoft.VisualStudio.TestTools.UnitTesting.InternalTestFailureException while looking for exports. Exception: System.TypeLoadException: Cannot find type System.Exception in module System.Runtime.dll.
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyModule.ResolveTypeRef(ITypeReference typeReference)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyTypeReference.GetResolvedTypeWorker()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetResolvedType()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetCustomAttributesData()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.HasAttributes(Type targetType, Boolean validateInheritedAttributes, Type[] attributeTypes)
20:10:46 at Microsoft.Test.Apex.ApexTypeUniverse.<GetExportedTypes>d__11.MoveNext()
20:10:46 Failed to load assembly Microsoft.VisualStudio.TestTools.UnitTesting.ExpectedExceptionAttribute while looking for exports. Exception: System.TypeLoadException: Cannot find type System.Attribute in module System.Runtime.dll.
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyModule.ResolveTypeRef(ITypeReference typeReference)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyTypeReference.GetResolvedTypeWorker()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetResolvedType()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetCustomAttributesData()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.HasAttributes(Type targetType, Boolean validateInheritedAttributes, Type[] attributeTypes)
20:10:46 at Microsoft.Test.Apex.ApexTypeUniverse.<GetExportedTypes>d__11.MoveNext()
20:10:46 Failed to load assembly Microsoft.VisualStudio.TestTools.UnitTesting.TestCategoryAttribute while looking for exports. Exception: System.TypeLoadException: Cannot find type System.Attribute in module System.Runtime.dll.
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyModule.ResolveTypeRef(ITypeReference typeReference)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyTypeReference.GetResolvedTypeWorker()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetResolvedType()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetCustomAttributesData()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.HasAttributes(Type targetType, Boolean validateInheritedAttributes, Type[] attributeTypes)
20:10:46 at Microsoft.Test.Apex.ApexTypeUniverse.<GetExportedTypes>d__11.MoveNext()
20:10:46 Failed to load assembly Microsoft.VisualStudio.TestTools.UnitTesting.AssertFailedException while looking for exports. Exception: System.TypeLoadException: Cannot find type System.Exception in module System.Runtime.dll.
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyModule.ResolveTypeRef(ITypeReference typeReference)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyTypeReference.GetResolvedTypeWorker()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetResolvedType()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetCustomAttributesData()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.HasAttributes(Type targetType, Boolean validateInheritedAttributes, Type[] attributeTypes)
20:10:46 at Microsoft.Test.Apex.ApexTypeUniverse.<GetExportedTypes>d__11.MoveNext()
20:10:46 Failed to load assembly Microsoft.VisualStudio.TestTools.UnitTesting.DataTestMethodAttribute while looking for exports. Exception: System.TypeLoadException: Cannot find type System.Attribute in module System.Runtime.dll.
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyModule.ResolveTypeRef(ITypeReference typeReference)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyTypeReference.GetResolvedTypeWorker()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetResolvedType()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetCustomAttributesData()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.HasAttributes(Type targetType, Boolean validateInheritedAttributes, Type[] attributeTypes)
20:10:46 at Microsoft.Test.Apex.ApexTypeUniverse.<GetExportedTypes>d__11.MoveNext()
20:10:46 Failed to load assembly Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute while looking for exports. Exception: System.TypeLoadException: Cannot find type System.Attribute in module System.Runtime.dll.
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyModule.ResolveTypeRef(ITypeReference typeReference)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyTypeReference.GetResolvedTypeWorker()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetResolvedType()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetCustomAttributesData()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.HasAttributes(Type targetType, Boolean validateInheritedAttributes, Type[] attributeTypes)
20:10:46 at Microsoft.Test.Apex.ApexTypeUniverse.<GetExportedTypes>d__11.MoveNext()
20:10:46 Failed to load assembly Microsoft.VisualStudio.TestTools.UnitTesting.CssProjectStructureAttribute while looking for exports. Exception: System.TypeLoadException: Cannot find type System.Attribute in module System.Runtime.dll.
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyModule.ResolveTypeRef(ITypeReference typeReference)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyTypeReference.GetResolvedTypeWorker()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetResolvedType()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetCustomAttributesData()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.HasAttributes(Type targetType, Boolean validateInheritedAttributes, Type[] attributeTypes)
20:10:46 at Microsoft.Test.Apex.ApexTypeUniverse.<GetExportedTypes>d__11.MoveNext()
20:10:46 Failed to load assembly Microsoft.VisualStudio.TestTools.UnitTesting.CssIterationAttribute while looking for exports. Exception: System.TypeLoadException: Cannot find type System.Attribute in module System.Runtime.dll.
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyModule.ResolveTypeRef(ITypeReference typeReference)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyTypeReference.GetResolvedTypeWorker()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetResolvedType()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetCustomAttributesData()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.HasAttributes(Type targetType, Boolean validateInheritedAttributes, Type[] attributeTypes)
20:10:46 at Microsoft.Test.Apex.ApexTypeUniverse.<GetExportedTypes>d__11.MoveNext()
20:10:46 Failed to load assembly Microsoft.VisualStudio.TestTools.UnitTesting.WorkItemAttribute while looking for exports. Exception: System.TypeLoadException: Cannot find type System.Attribute in module System.Runtime.dll.
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyAssembly.GetType(String name, Boolean throwOnError)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyModule.ResolveTypeRef(ITypeReference typeReference)
20:10:46 at Microsoft.MetadataReader.MetadataOnlyTypeReference.GetResolvedTypeWorker()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetResolvedType()
20:10:46 at Microsoft.MetadataReader.TypeProxy.GetCustomAttributesData()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.<GetAllAttributes>d__3.MoveNext()
20:10:46 at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)
20:10:46 at Microsoft.Test.Apex.ReflectionHelpers.HasAttributes(Type targetType, Boolean validateInheritedAttributes, Type[] attributeTypes)
20:10:46 at Microsoft.Test.Apex.ApexTypeUniverse.<GetExportedTypes>d__11.MoveNext()
20:10:46 Found 78 exported, and 0 unexportable types from assemblies 'Microsoft.Test.Apex.Framework.dll, Microsoft.Test.Apex.VSTestIntegration.dll, Microsoft.VisualStudio.ProjectSystem.IntegrationTests.dll, Microsoft.VisualStudio.TestPlatform.TestFramework.dll, Microsoft.VisualStudio.TestPlatform.TestFramework.Extensions.dll, Microsoft.Test.Apex.VisualStudio.dll, Microsoft.Test.Apex.VisualStudio.Hosting.dll, Microsoft.Test.Apex.OsIntegration.dll, Microsoft.Test.Apex.SourceControlIntegration.dll'
20:10:46
20:10:46 Failed to load Omni log dll: System.IO.FileNotFoundException: Could not load file or assembly 'Omni.Logging.Extended' or one of its dependencies. The system cannot find the file specified.
20:10:46 File name: 'Omni.Logging.Extended'
20:10:46 at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
20:10:46 at System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
20:10:46 at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
20:10:46 at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection)
20:10:46 at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
20:10:46 at System.Reflection.Assembly.Load(String assemblyString)
20:10:46 at Microsoft.Test.Apex.Services.Logging.TestLoggerSinks.OmniLog.OmniLogSink..ctor()
``` | non_usab | integration tests are failing indeterminately with mef composition issue debug trace error loading dependency assembly microsoft test apex teamfoundation publickeytoken of microsoft test apex sourcecontrolintegration dll for operations composition container dependencies from this assembly will be missing in the composition could not load file or assembly microsoft test apex teamfoundation publickeytoken or one of its dependencies the parameter is incorrect exception from hresult e invalidarg populating assembly catalog apexassemblycatalog attributed with failed to load assembly microsoft visualstudio testtools unittesting assertinconclusiveexception while looking for exports exception system typeloadexception cannot find type system exception in module system runtime dll at microsoft metadatareader metadataonlyassembly gettype string name boolean throwonerror boolean ignorecase at microsoft metadatareader metadataonlyassembly gettype string name boolean throwonerror at microsoft metadatareader metadataonlymodule resolvetyperef itypereference typereference at microsoft metadatareader metadataonlytypereference getresolvedtypeworker at microsoft metadatareader typeproxy getresolvedtype at microsoft metadatareader typeproxy getcustomattributesdata at microsoft test apex reflectionhelpers d movenext at microsoft test apex reflectionhelpers d movenext at microsoft test apex reflectionhelpers d movenext at system linq enumerable any ienumerable source func predicate at microsoft test apex reflectionhelpers hasattributes type targettype boolean validateinheritedattributes type attributetypes at microsoft test apex apextypeuniverse d movenext failed to load assembly microsoft visualstudio testtools unittesting internaltestfailureexception while looking for exports exception system typeloadexception cannot find type system exception in module system runtime dll at microsoft metadatareader metadataonlyassembly gettype string name boolean throwonerror boolean ignorecase at microsoft metadatareader metadataonlyassembly gettype string name boolean throwonerror at microsoft metadatareader metadataonlymodule resolvetyperef itypereference typereference at microsoft metadatareader metadataonlytypereference getresolvedtypeworker at microsoft metadatareader typeproxy getresolvedtype at microsoft metadatareader typeproxy getcustomattributesdata at microsoft test apex reflectionhelpers d movenext at microsoft test apex reflectionhelpers d movenext at microsoft test apex reflectionhelpers d movenext at system linq enumerable any ienumerable source func predicate at microsoft test apex reflectionhelpers hasattributes type targettype boolean validateinheritedattributes type attributetypes at microsoft test apex apextypeuniverse d movenext failed to load assembly microsoft visualstudio testtools unittesting expectedexceptionattribute while looking for exports exception system typeloadexception cannot find type system attribute in module system runtime dll at microsoft metadatareader metadataonlyassembly gettype string name boolean throwonerror boolean ignorecase at microsoft metadatareader metadataonlyassembly gettype string name boolean throwonerror at microsoft metadatareader metadataonlymodule resolvetyperef itypereference typereference at microsoft metadatareader metadataonlytypereference getresolvedtypeworker at microsoft metadatareader typeproxy getresolvedtype at microsoft metadatareader typeproxy getcustomattributesdata at microsoft test apex reflectionhelpers d movenext at microsoft test apex reflectionhelpers d movenext at microsoft test apex reflectionhelpers d movenext at system linq enumerable any ienumerable source func predicate at microsoft test apex reflectionhelpers hasattributes type targettype boolean validateinheritedattributes type attributetypes at microsoft test apex apextypeuniverse d movenext failed to load assembly microsoft visualstudio testtools unittesting testcategoryattribute while looking for exports exception system typeloadexception cannot find type system attribute in module system runtime dll at microsoft metadatareader metadataonlyassembly gettype string name boolean throwonerror boolean ignorecase at microsoft metadatareader metadataonlyassembly gettype string name boolean throwonerror at microsoft metadatareader metadataonlymodule resolvetyperef itypereference typereference at microsoft metadatareader metadataonlytypereference getresolvedtypeworker at microsoft metadatareader typeproxy getresolvedtype at microsoft metadatareader typeproxy getcustomattributesdata at microsoft test apex reflectionhelpers d movenext at microsoft test apex reflectionhelpers d movenext at microsoft test apex reflectionhelpers d movenext at system linq enumerable any ienumerable source func predicate at microsoft test apex reflectionhelpers hasattributes type targettype boolean validateinheritedattributes type attributetypes at microsoft test apex apextypeuniverse d movenext failed to load assembly microsoft visualstudio testtools unittesting assertfailedexception while looking for exports exception system typeloadexception cannot find type system exception in module system runtime dll at microsoft metadatareader metadataonlyassembly gettype string name boolean throwonerror boolean ignorecase at microsoft metadatareader metadataonlyassembly gettype string name boolean throwonerror at microsoft metadatareader metadataonlymodule resolvetyperef itypereference typereference at microsoft metadatareader metadataonlytypereference getresolvedtypeworker at microsoft metadatareader typeproxy getresolvedtype at microsoft metadatareader typeproxy getcustomattributesdata at microsoft test apex reflectionhelpers d movenext at microsoft test apex reflectionhelpers d movenext at microsoft test apex reflectionhelpers d movenext at system linq enumerable any ienumerable source func predicate at microsoft test apex reflectionhelpers hasattributes type targettype boolean validateinheritedattributes type attributetypes at microsoft test apex apextypeuniverse d movenext failed to load assembly microsoft visualstudio testtools unittesting datatestmethodattribute while looking for exports exception system typeloadexception cannot find type system attribute in module system runtime dll at microsoft metadatareader metadataonlyassembly gettype string name boolean throwonerror boolean ignorecase at microsoft metadatareader metadataonlyassembly gettype string name boolean throwonerror at microsoft metadatareader metadataonlymodule resolvetyperef itypereference typereference at microsoft metadatareader metadataonlytypereference getresolvedtypeworker at microsoft metadatareader typeproxy getresolvedtype at microsoft metadatareader typeproxy getcustomattributesdata at microsoft test apex reflectionhelpers d movenext at microsoft test apex reflectionhelpers d movenext at microsoft test apex reflectionhelpers d movenext at system linq enumerable any ienumerable source func predicate at microsoft test apex reflectionhelpers hasattributes type targettype boolean validateinheritedattributes type attributetypes at microsoft test apex apextypeuniverse d movenext failed to load assembly microsoft visualstudio testtools unittesting descriptionattribute while looking for exports exception system typeloadexception cannot find type system attribute in module system runtime dll at microsoft metadatareader metadataonlyassembly gettype string name boolean throwonerror boolean ignorecase at microsoft metadatareader metadataonlyassembly gettype string name boolean throwonerror at microsoft metadatareader metadataonlymodule resolvetyperef itypereference typereference at microsoft metadatareader metadataonlytypereference getresolvedtypeworker at microsoft metadatareader typeproxy getresolvedtype at microsoft metadatareader typeproxy getcustomattributesdata at microsoft test apex reflectionhelpers d movenext at microsoft test apex reflectionhelpers d movenext at microsoft test apex reflectionhelpers d movenext at system linq enumerable any ienumerable source func predicate at microsoft test apex reflectionhelpers hasattributes type targettype boolean validateinheritedattributes type attributetypes at microsoft test apex apextypeuniverse d movenext failed to load assembly microsoft visualstudio testtools unittesting cssprojectstructureattribute while looking for exports exception system typeloadexception cannot find type system attribute in module system runtime dll at microsoft metadatareader metadataonlyassembly gettype string name boolean throwonerror boolean ignorecase at microsoft metadatareader metadataonlyassembly gettype string name boolean throwonerror at microsoft metadatareader metadataonlymodule resolvetyperef itypereference typereference at microsoft metadatareader metadataonlytypereference getresolvedtypeworker at microsoft metadatareader typeproxy getresolvedtype at microsoft metadatareader typeproxy getcustomattributesdata at microsoft test apex reflectionhelpers d movenext at microsoft test apex reflectionhelpers d movenext at microsoft test apex reflectionhelpers d movenext at system linq enumerable any ienumerable source func predicate at microsoft test apex reflectionhelpers hasattributes type targettype boolean validateinheritedattributes type attributetypes at microsoft test apex apextypeuniverse d movenext failed to load assembly microsoft visualstudio testtools unittesting cssiterationattribute while looking for exports exception system typeloadexception cannot find type system attribute in module system runtime dll at microsoft metadatareader metadataonlyassembly gettype string name boolean throwonerror boolean ignorecase at microsoft metadatareader metadataonlyassembly gettype string name boolean throwonerror at microsoft metadatareader metadataonlymodule resolvetyperef itypereference typereference at microsoft metadatareader metadataonlytypereference getresolvedtypeworker at microsoft metadatareader typeproxy getresolvedtype at microsoft metadatareader typeproxy getcustomattributesdata at microsoft test apex reflectionhelpers d movenext at microsoft test apex reflectionhelpers d movenext at microsoft test apex reflectionhelpers d movenext at system linq enumerable any ienumerable source func predicate at microsoft test apex reflectionhelpers hasattributes type targettype boolean validateinheritedattributes type attributetypes at microsoft test apex apextypeuniverse d movenext failed to load assembly microsoft visualstudio testtools unittesting workitemattribute while looking for exports exception system typeloadexception cannot find type system attribute in module system runtime dll at microsoft metadatareader metadataonlyassembly gettype string name boolean throwonerror boolean ignorecase at microsoft metadatareader metadataonlyassembly gettype string name boolean throwonerror at microsoft metadatareader metadataonlymodule resolvetyperef itypereference typereference at microsoft metadatareader metadataonlytypereference getresolvedtypeworker at microsoft metadatareader typeproxy getresolvedtype at microsoft metadatareader typeproxy getcustomattributesdata at microsoft test apex reflectionhelpers d movenext at microsoft test apex reflectionhelpers d movenext at microsoft test apex reflectionhelpers d movenext at system linq enumerable any ienumerable source func predicate at microsoft test apex reflectionhelpers hasattributes type targettype boolean validateinheritedattributes type attributetypes at microsoft test apex apextypeuniverse d movenext found exported and unexportable types from assemblies microsoft test apex framework dll microsoft test apex vstestintegration dll microsoft visualstudio projectsystem integrationtests dll microsoft visualstudio testplatform testframework dll microsoft visualstudio testplatform testframework extensions dll microsoft test apex visualstudio dll microsoft test apex visualstudio hosting dll microsoft test apex osintegration dll microsoft test apex sourcecontrolintegration dll failed to load omni log dll system io filenotfoundexception could not load file or assembly omni logging extended or one of its dependencies the system cannot find the file specified file name omni logging extended at system reflection runtimeassembly nload assemblyname filename string codebase evidence assemblysecurity runtimeassembly locationhint stackcrawlmark stackmark intptr pprivhostbinder boolean throwonfilenotfound boolean forintrospection boolean suppresssecuritychecks at system reflection runtimeassembly nload assemblyname filename string codebase evidence assemblysecurity runtimeassembly locationhint stackcrawlmark stackmark intptr pprivhostbinder boolean throwonfilenotfound boolean forintrospection boolean suppresssecuritychecks at system reflection runtimeassembly internalloadassemblyname assemblyname assemblyref evidence assemblysecurity runtimeassembly reqassembly stackcrawlmark stackmark intptr pprivhostbinder boolean throwonfilenotfound boolean forintrospection boolean suppresssecuritychecks at system reflection runtimeassembly internalload string assemblystring evidence assemblysecurity stackcrawlmark stackmark intptr pprivhostbinder boolean forintrospection at system reflection runtimeassembly internalload string assemblystring evidence assemblysecurity stackcrawlmark stackmark boolean forintrospection at system reflection assembly load string assemblystring at microsoft test apex services logging testloggersinks omnilog omnilogsink ctor | 0 |
806,160 | 29,803,436,979 | IssuesEvent | 2023-06-16 09:49:23 | frequenz-floss/frequenz-sdk-python | https://api.github.com/repos/frequenz-floss/frequenz-sdk-python | opened | Error reporting when microgrid API is misconfigured | priority:❓ type:bug part:core part:microgrid | ### What happened?
We wanted to run some FCR prequalification tests on a set of batteries. These batteries had been moved to a separate instance of the microgrid API. When running the actor, we were unable to start, because we got the error "Component tree is not a graph!". It appears to be thrown from here: https://github.com/frequenz-floss/frequenz-sdk-python/blob/3565d731d4b64581ff95e91a40a5bc57e7ad2905/src/frequenz/sdk/microgrid/_graph.py#L705
Initially, we could not find anything wrong with the component graph itself, since we verified it using the connections endpoint of the microgrid API. It was then pointed out to us that there existed a component, which was not connected to any other components. After removing this component, the error went away.
### What did you expect instead?
Ideally, the error reporting here should be more detailed, to avoid debugging sessions that lead to false conclusions. Something like `component ID #X has no connections and is a dangling component` would have saved us a lot of effort here.
### Affected version(s)
v0.20.0
### Affected part(s)
Core components (data structures, etc.) (part:core), Microgrid (API, component graph, etc.) (part:microgrid)
### Extra information
_No response_ | 1.0 | Error reporting when microgrid API is misconfigured - ### What happened?
We wanted to run some FCR prequalification tests on a set of batteries. These batteries had been moved to a separate instance of the microgrid API. When running the actor, we were unable to start, because we got the error "Component tree is not a graph!". It appears to be thrown from here: https://github.com/frequenz-floss/frequenz-sdk-python/blob/3565d731d4b64581ff95e91a40a5bc57e7ad2905/src/frequenz/sdk/microgrid/_graph.py#L705
Initially, we could not find anything wrong with the component graph itself, since we verified it using the connections endpoint of the microgrid API. It was then pointed out to us that there existed a component, which was not connected to any other components. After removing this component, the error went away.
### What did you expect instead?
Ideally, the error reporting here should be more detailed, to avoid debugging sessions that lead to false conclusions. Something like `component ID #X has no connections and is a dangling component` would have saved us a lot of effort here.
### Affected version(s)
v0.20.0
### Affected part(s)
Core components (data structures, etc.) (part:core), Microgrid (API, component graph, etc.) (part:microgrid)
### Extra information
_No response_ | non_usab | error reporting when microgrid api is misconfigured what happened we wanted to run some fcr prequalification tests on a set of batteries these batteries had been moved to a separate instance of the microgrid api when running the actor we were unable to start because we got the error component tree is not a graph it appears to be thrown from here initially we could not find anything wrong with the component graph itself since we verified it using the connections endpoint of the microgrid api it was then pointed out to us that there existed a component which was not connected to any other components after removing this component the error went away what did you expect instead ideally the error reporting here should be more detailed to avoid debugging sessions that lead to false conclusions something like component id x has no connections and is a dangling component would have saved us a lot of effort here affected version s affected part s core components data structures etc part core microgrid api component graph etc part microgrid extra information no response | 0 |
18,828 | 13,262,358,288 | IssuesEvent | 2020-08-20 21:37:21 | Electron-Cash/Electron-Cash | https://api.github.com/repos/Electron-Cash/Electron-Cash | closed | Cashfusion: Suppress Tor prompt or offer plugin disable when Fusion is disabled | Cash Fusion UX and usability | Currently Cashfusion triggers a "Tor is missing" prompt every time the program starts, as long as it cannot find a Tor port anywhere (whether integrated or systemwide), as long as the Fusion plugin is on (default). This is non-ideal for users who do not wish to run a Tor client nor Fusion, but nevertheless is uninformed about the option to turn Cashfusion plugin off in menus.
One way to address it is to move the check for Tor availability to only trigger when Fusion is either manually enabled, or at start only when Fusion was enabled in the previous session.
Another (easier?) way is that in the same prompt, in addition to starting Tor or Cancel, add an additional option to disable the Cashfusion plugin altogether. Perhaps add a line "If you disable Cashfusion plugin now and wish to enable it later, find it at Tools -> Optional Features -> Cashfusion".
A third way may be to remove the prompt altogether, and always enable integrated Tor as long as no system Tor is detected to be running. However that might be undesirable for people who do not want a Tor client of any kind to run on their machine. | True | Cashfusion: Suppress Tor prompt or offer plugin disable when Fusion is disabled - Currently Cashfusion triggers a "Tor is missing" prompt every time the program starts, as long as it cannot find a Tor port anywhere (whether integrated or systemwide), as long as the Fusion plugin is on (default). This is non-ideal for users who do not wish to run a Tor client nor Fusion, but nevertheless is uninformed about the option to turn Cashfusion plugin off in menus.
One way to address it is to move the check for Tor availability to only trigger when Fusion is either manually enabled, or at start only when Fusion was enabled in the previous session.
Another (easier?) way is that in the same prompt, in addition to starting Tor or Cancel, add an additional option to disable the Cashfusion plugin altogether. Perhaps add a line "If you disable Cashfusion plugin now and wish to enable it later, find it at Tools -> Optional Features -> Cashfusion".
A third way may be to remove the prompt altogether, and always enable integrated Tor as long as no system Tor is detected to be running. However that might be undesirable for people who do not want a Tor client of any kind to run on their machine. | usab | cashfusion suppress tor prompt or offer plugin disable when fusion is disabled currently cashfusion triggers a tor is missing prompt every time the program starts as long as it cannot find a tor port anywhere whether integrated or systemwide as long as the fusion plugin is on default this is non ideal for users who do not wish to run a tor client nor fusion but nevertheless is uninformed about the option to turn cashfusion plugin off in menus one way to address it is to move the check for tor availability to only trigger when fusion is either manually enabled or at start only when fusion was enabled in the previous session another easier way is that in the same prompt in addition to starting tor or cancel add an additional option to disable the cashfusion plugin altogether perhaps add a line if you disable cashfusion plugin now and wish to enable it later find it at tools optional features cashfusion a third way may be to remove the prompt altogether and always enable integrated tor as long as no system tor is detected to be running however that might be undesirable for people who do not want a tor client of any kind to run on their machine | 1 |
523,323 | 15,178,239,032 | IssuesEvent | 2021-02-14 14:40:10 | nlpsandbox/nlpsandbox-client | https://api.github.com/repos/nlpsandbox/nlpsandbox-client | closed | Update client to match new schema and data node | Priority: High | ### Is your proposal related to a problem?
The data node was updated to support non-random note, annotation, and patient Ids.
### Describe the solution you'd like
Support the new data node. | 1.0 | Update client to match new schema and data node - ### Is your proposal related to a problem?
The data node was updated to support non-random note, annotation, and patient Ids.
### Describe the solution you'd like
Support the new data node. | non_usab | update client to match new schema and data node is your proposal related to a problem the data node was updated to support non random note annotation and patient ids describe the solution you d like support the new data node | 0 |
610,864 | 18,926,990,939 | IssuesEvent | 2021-11-17 10:34:45 | wso2/product-apim | https://api.github.com/repos/wso2/product-apim | closed | [APIM 2.6.0] Unnecessary SOAP Action element in generated sequence template for SOAP 1.1 | Type/Bug Priority/Normal | ### Description:
<!-- Describe the issue -->
Invalid xml element `<web:operationID>` is added as the root element of the generated sequence template when creating an API using SOAP 1.1
### Steps to reproduce:
1. Create and publish a SOAP API using either a file or a url.
2. Enable wirelogs and invoke the API.
3. Invalid sequence template will be shown in the gateway logs.
### Affected Product Version:
<!-- Members can use Affected/*** labels -->
APIM-2.6.0
--- | 1.0 | [APIM 2.6.0] Unnecessary SOAP Action element in generated sequence template for SOAP 1.1 - ### Description:
<!-- Describe the issue -->
Invalid xml element `<web:operationID>` is added as the root element of the generated sequence template when creating an API using SOAP 1.1
### Steps to reproduce:
1. Create and publish a SOAP API using either a file or a url.
2. Enable wirelogs and invoke the API.
3. Invalid sequence template will be shown in the gateway logs.
### Affected Product Version:
<!-- Members can use Affected/*** labels -->
APIM-2.6.0
--- | non_usab | unnecessary soap action element in generated sequence template for soap description invalid xml element is added as the root element of the generated sequence template when creating an api using soap steps to reproduce create and publish a soap api using either a file or a url enable wirelogs and invoke the api invalid sequence template will be shown in the gateway logs affected product version apim | 0 |
150,358 | 5,765,261,625 | IssuesEvent | 2017-04-27 01:35:51 | CovertJaguar/Railcraft | https://api.github.com/repos/CovertJaguar/Railcraft | closed | Creative Mode crash with certain blocks disabled | bug implemented priority-medium | Railcraft will crash using the Creative Search tab (not the Railcraft tab) with certain blocks disabled. From the testing I did, these blocks were the ones at fault:
B:ore_dark_diamond=false
B:ore_dark_emerald=false
B:ore_dark_lapis=false
B:ore_saltpeter=false
B:ore_sulfur=false
Other ores can still be disabled safely.
May be related to #1162.
edit: Ah, almost forgot a crash log: https://pastebin.com/su0dktz2 | 1.0 | Creative Mode crash with certain blocks disabled - Railcraft will crash using the Creative Search tab (not the Railcraft tab) with certain blocks disabled. From the testing I did, these blocks were the ones at fault:
B:ore_dark_diamond=false
B:ore_dark_emerald=false
B:ore_dark_lapis=false
B:ore_saltpeter=false
B:ore_sulfur=false
Other ores can still be disabled safely.
May be related to #1162.
edit: Ah, almost forgot a crash log: https://pastebin.com/su0dktz2 | non_usab | creative mode crash with certain blocks disabled railcraft will crash using the creative search tab not the railcraft tab with certain blocks disabled from the testing i did these blocks were the ones at fault b ore dark diamond false b ore dark emerald false b ore dark lapis false b ore saltpeter false b ore sulfur false other ores can still be disabled safely may be related to edit ah almost forgot a crash log | 0 |
98,736 | 4,030,801,392 | IssuesEvent | 2016-05-18 15:15:52 | navacohen90/Click-a-Table | https://api.github.com/repos/navacohen90/Click-a-Table | closed | Courses View for specific course type | 3 - Done points: 10 priority1 - HIGH | UI -
Server
DB
<!---
@huboard:{"milestone_order":0.001953125,"order":11.5078125,"custom_state":""}
-->
| 1.0 | Courses View for specific course type - UI -
Server
DB
<!---
@huboard:{"milestone_order":0.001953125,"order":11.5078125,"custom_state":""}
-->
| non_usab | courses view for specific course type ui server db huboard milestone order order custom state | 0 |
157,907 | 19,988,527,825 | IssuesEvent | 2022-01-31 01:06:22 | RG4421/grafana | https://api.github.com/repos/RG4421/grafana | opened | WS-2021-0461 (Medium) detected in swagger-ui-bundle-3.19.5.js | security vulnerability | ## WS-2021-0461 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>swagger-ui-bundle-3.19.5.js</b></p></summary>
<p>Swagger UI is a dependency-free collection of HTML, JavaScript, and CSS assets that dynamically generate beautiful documentation from a Swagger-compliant API</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/swagger-ui/3.19.5/swagger-ui-bundle.js">https://cdnjs.cloudflare.com/ajax/libs/swagger-ui/3.19.5/swagger-ui-bundle.js</a></p>
<p>Path to dependency file: /pkg/services/ngalert/api/tooling/index.html</p>
<p>Path to vulnerable library: /grafana/pkg/services/ngalert/api/tooling/index.html</p>
<p>
Dependency Hierarchy:
- :x: **swagger-ui-bundle-3.19.5.js** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
SwaggerUI supports displaying remote OpenAPI definitions through the ?url parameter. This enables robust demonstration capabilities on sites like petstore.swagger.io, editor.swagger.io, and similar sites, where users often want to see what their OpenAPI definitions would look like rendered.
However, this functionality may pose a risk for users who host their own SwaggerUI instances. In particular, including remote OpenAPI definitions opens a vector for phishing attacks by abusing the trusted names/domains of self-hosted instances.
Resolution:
We've made the decision to disable query parameters (#4872) by default starting with SwaggerUI version 4.1.3. Please update to this version when it becomes available (ETA: 2021 December). Users will still be able to be re-enable the options at their discretion. We'll continue to enable query parameters on the Swagger demo sites.
<p>Publish Date: 2021-12-09
<p>URL: <a href=https://github.com/swagger-api/swagger-ui/commit/01a3e55960f864a0acf6a8d06e5ddaf6776a7f76>WS-2021-0461</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-qrmm-w75w-3wpx">https://github.com/advisories/GHSA-qrmm-w75w-3wpx</a></p>
<p>Release Date: 2021-12-09</p>
<p>Fix Resolution: swagger-ui - 4.1.3;swagger-ui-dist - 4.1.3</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"JavaScript","packageName":"swagger-ui","packageVersion":"3.19.5","packageFilePaths":["/pkg/services/ngalert/api/tooling/index.html"],"isTransitiveDependency":false,"dependencyTree":"swagger-ui:3.19.5","isMinimumFixVersionAvailable":true,"minimumFixVersion":"swagger-ui - 4.1.3;swagger-ui-dist - 4.1.3","isBinary":false}],"baseBranches":["main"],"vulnerabilityIdentifier":"WS-2021-0461","vulnerabilityDetails":"SwaggerUI supports displaying remote OpenAPI definitions through the ?url parameter. This enables robust demonstration capabilities on sites like petstore.swagger.io, editor.swagger.io, and similar sites, where users often want to see what their OpenAPI definitions would look like rendered.\n\nHowever, this functionality may pose a risk for users who host their own SwaggerUI instances. In particular, including remote OpenAPI definitions opens a vector for phishing attacks by abusing the trusted names/domains of self-hosted instances.\n\nResolution:\nWe\u0027ve made the decision to disable query parameters (#4872) by default starting with SwaggerUI version 4.1.3. Please update to this version when it becomes available (ETA: 2021 December). Users will still be able to be re-enable the options at their discretion. We\u0027ll continue to enable query parameters on the Swagger demo sites.","vulnerabilityUrl":"https://github.com/swagger-api/swagger-ui/commit/01a3e55960f864a0acf6a8d06e5ddaf6776a7f76","cvss3Severity":"medium","cvss3Score":"6.1","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Changed","C":"Low","UI":"Required","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | True | WS-2021-0461 (Medium) detected in swagger-ui-bundle-3.19.5.js - ## WS-2021-0461 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>swagger-ui-bundle-3.19.5.js</b></p></summary>
<p>Swagger UI is a dependency-free collection of HTML, JavaScript, and CSS assets that dynamically generate beautiful documentation from a Swagger-compliant API</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/swagger-ui/3.19.5/swagger-ui-bundle.js">https://cdnjs.cloudflare.com/ajax/libs/swagger-ui/3.19.5/swagger-ui-bundle.js</a></p>
<p>Path to dependency file: /pkg/services/ngalert/api/tooling/index.html</p>
<p>Path to vulnerable library: /grafana/pkg/services/ngalert/api/tooling/index.html</p>
<p>
Dependency Hierarchy:
- :x: **swagger-ui-bundle-3.19.5.js** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
SwaggerUI supports displaying remote OpenAPI definitions through the ?url parameter. This enables robust demonstration capabilities on sites like petstore.swagger.io, editor.swagger.io, and similar sites, where users often want to see what their OpenAPI definitions would look like rendered.
However, this functionality may pose a risk for users who host their own SwaggerUI instances. In particular, including remote OpenAPI definitions opens a vector for phishing attacks by abusing the trusted names/domains of self-hosted instances.
Resolution:
We've made the decision to disable query parameters (#4872) by default starting with SwaggerUI version 4.1.3. Please update to this version when it becomes available (ETA: 2021 December). Users will still be able to be re-enable the options at their discretion. We'll continue to enable query parameters on the Swagger demo sites.
<p>Publish Date: 2021-12-09
<p>URL: <a href=https://github.com/swagger-api/swagger-ui/commit/01a3e55960f864a0acf6a8d06e5ddaf6776a7f76>WS-2021-0461</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-qrmm-w75w-3wpx">https://github.com/advisories/GHSA-qrmm-w75w-3wpx</a></p>
<p>Release Date: 2021-12-09</p>
<p>Fix Resolution: swagger-ui - 4.1.3;swagger-ui-dist - 4.1.3</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"JavaScript","packageName":"swagger-ui","packageVersion":"3.19.5","packageFilePaths":["/pkg/services/ngalert/api/tooling/index.html"],"isTransitiveDependency":false,"dependencyTree":"swagger-ui:3.19.5","isMinimumFixVersionAvailable":true,"minimumFixVersion":"swagger-ui - 4.1.3;swagger-ui-dist - 4.1.3","isBinary":false}],"baseBranches":["main"],"vulnerabilityIdentifier":"WS-2021-0461","vulnerabilityDetails":"SwaggerUI supports displaying remote OpenAPI definitions through the ?url parameter. This enables robust demonstration capabilities on sites like petstore.swagger.io, editor.swagger.io, and similar sites, where users often want to see what their OpenAPI definitions would look like rendered.\n\nHowever, this functionality may pose a risk for users who host their own SwaggerUI instances. In particular, including remote OpenAPI definitions opens a vector for phishing attacks by abusing the trusted names/domains of self-hosted instances.\n\nResolution:\nWe\u0027ve made the decision to disable query parameters (#4872) by default starting with SwaggerUI version 4.1.3. Please update to this version when it becomes available (ETA: 2021 December). Users will still be able to be re-enable the options at their discretion. We\u0027ll continue to enable query parameters on the Swagger demo sites.","vulnerabilityUrl":"https://github.com/swagger-api/swagger-ui/commit/01a3e55960f864a0acf6a8d06e5ddaf6776a7f76","cvss3Severity":"medium","cvss3Score":"6.1","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Changed","C":"Low","UI":"Required","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | non_usab | ws medium detected in swagger ui bundle js ws medium severity vulnerability vulnerable library swagger ui bundle js swagger ui is a dependency free collection of html javascript and css assets that dynamically generate beautiful documentation from a swagger compliant api library home page a href path to dependency file pkg services ngalert api tooling index html path to vulnerable library grafana pkg services ngalert api tooling index html dependency hierarchy x swagger ui bundle js vulnerable library found in base branch main vulnerability details swaggerui supports displaying remote openapi definitions through the url parameter this enables robust demonstration capabilities on sites like petstore swagger io editor swagger io and similar sites where users often want to see what their openapi definitions would look like rendered however this functionality may pose a risk for users who host their own swaggerui instances in particular including remote openapi definitions opens a vector for phishing attacks by abusing the trusted names domains of self hosted instances resolution we ve made the decision to disable query parameters by default starting with swaggerui version please update to this version when it becomes available eta december users will still be able to be re enable the options at their discretion we ll continue to enable query parameters on the swagger demo sites publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution swagger ui swagger ui dist isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree swagger ui isminimumfixversionavailable true minimumfixversion swagger ui swagger ui dist isbinary false basebranches vulnerabilityidentifier ws vulnerabilitydetails swaggerui supports displaying remote openapi definitions through the url parameter this enables robust demonstration capabilities on sites like petstore swagger io editor swagger io and similar sites where users often want to see what their openapi definitions would look like rendered n nhowever this functionality may pose a risk for users who host their own swaggerui instances in particular including remote openapi definitions opens a vector for phishing attacks by abusing the trusted names domains of self hosted instances n nresolution nwe made the decision to disable query parameters by default starting with swaggerui version please update to this version when it becomes available eta december users will still be able to be re enable the options at their discretion we continue to enable query parameters on the swagger demo sites vulnerabilityurl | 0 |
36,463 | 2,799,600,787 | IssuesEvent | 2015-05-13 02:28:38 | ceylon/ceylon-js | https://api.github.com/repos/ceylon/ceylon-js | closed | Errors constructing generic class using named argument list | bug high priority | It seems that type arguments are not available when using named argument lists to invoke a constructor:
```ceylon
interface I<T> {}
class C<T> satisfies I<T> {
shared new New() { print("x"); }
}
class D<T> {
shared new New() { print(`T`); }
}
shared void tryCrash() {
C<String>.New {};
// TypeError: Cannot read property 'T$C' of undefined
D<String>.New {};
// Error: Missing type argument 'Type' [object Object]
// at Object.typeLiteral$meta
}
``` | 1.0 | Errors constructing generic class using named argument list - It seems that type arguments are not available when using named argument lists to invoke a constructor:
```ceylon
interface I<T> {}
class C<T> satisfies I<T> {
shared new New() { print("x"); }
}
class D<T> {
shared new New() { print(`T`); }
}
shared void tryCrash() {
C<String>.New {};
// TypeError: Cannot read property 'T$C' of undefined
D<String>.New {};
// Error: Missing type argument 'Type' [object Object]
// at Object.typeLiteral$meta
}
``` | non_usab | errors constructing generic class using named argument list it seems that type arguments are not available when using named argument lists to invoke a constructor ceylon interface i class c satisfies i shared new new print x class d shared new new print t shared void trycrash c new typeerror cannot read property t c of undefined d new error missing type argument type at object typeliteral meta | 0 |
165,362 | 12,838,854,841 | IssuesEvent | 2020-07-07 18:13:55 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | roachtest: schemachange/random-load failed | C-test-failure O-roachtest O-robot branch-provisional_202006230815_v19.1.10 release-blocker | [(roachtest).schemachange/random-load failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=2032556&tab=buildLog) on [provisional_202006230815_v19.1.10@7101af9b438f1ae4a4b4557922ab73f95eef137e](https://github.com/cockroachdb/cockroach/commits/7101af9b438f1ae4a4b4557922ab73f95eef137e):
```
| 35965.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 opOk
| 35965.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnCmtErr
| 35965.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnOk
| 35966.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 opOk
| 35966.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnCmtErr
| 35966.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnOk
| 35967.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 opOk
| 35967.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnCmtErr
| _elapsed___errors__ops/sec(inst)___ops/sec(cum)__p50(ms)__p95(ms)__p99(ms)_pMax(ms)
| 35967.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnOk
| 35968.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 opOk
| 35968.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnCmtErr
| 35968.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnOk
| 35969.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 opOk
| 35969.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnCmtErr
| 35969.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnOk
| 35970.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 opOk
| 35970.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnCmtErr
| 35970.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnOk
| 35971.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 opOk
| 35971.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnCmtErr
| 35971.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnOk
| 35972.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 opOk
| 35972.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnCmtErr
| 35972.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnOk
| 35973.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 opOk
| 35973.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnCmtErr
| 35973.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnOk
| 35974.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 opOk
| _elapsed___errors__ops/sec(inst)___ops/sec(cum)__p50(ms)__p95(ms)__p99(ms)_pMax(ms)
| 35974.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnCmtErr
| 35974.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnOk
| 35975.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 opOk
| 35975.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnCmtErr
| 35975.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnOk
| 35976.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 opOk
| 35976.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnCmtErr
| 35976.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnOk
| 35977.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 opOk
| 35977.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnCmtErr
| 35977.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnOk
| 35978.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 opOk
| 35978.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnCmtErr
| 35978.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnOk
Wraps: (5) secondary error attachment
| signal: killed
| (1) signal: killed
| Error types: (1) *exec.ExitError
Wraps: (6) context canceled
Error types: (1) *withstack.withStack (2) *safedetails.withSafeDetails (3) *errutil.withMessage (4) *main.withCommandDetails (5) *secondary.withSecondaryError (6) *errors.errorString
```
<details><summary>More</summary><p>
Artifacts: [/schemachange/random-load](https://teamcity.cockroachdb.com/viewLog.html?buildId=2032556&tab=artifacts#/schemachange/random-load)
Related:
- #50557 roachtest: schemachange/random-load failed [C-test-failure](https://api.github.com/repos/cockroachdb/cockroach/labels/C-test-failure) [O-roachtest](https://api.github.com/repos/cockroachdb/cockroach/labels/O-roachtest) [O-robot](https://api.github.com/repos/cockroachdb/cockroach/labels/O-robot) [branch-release-19.1](https://api.github.com/repos/cockroachdb/cockroach/labels/branch-release-19.1) [release-blocker](https://api.github.com/repos/cockroachdb/cockroach/labels/release-blocker)
[See this test on roachdash](https://roachdash.crdb.dev/?filter=status%3Aopen+t%3A.%2Aschemachange%2Frandom-load.%2A&sort=title&restgroup=false&display=lastcommented+project)
<sub>powered by [pkg/cmd/internal/issues](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)</sub></p></details>
| 2.0 | roachtest: schemachange/random-load failed - [(roachtest).schemachange/random-load failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=2032556&tab=buildLog) on [provisional_202006230815_v19.1.10@7101af9b438f1ae4a4b4557922ab73f95eef137e](https://github.com/cockroachdb/cockroach/commits/7101af9b438f1ae4a4b4557922ab73f95eef137e):
```
| 35965.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 opOk
| 35965.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnCmtErr
| 35965.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnOk
| 35966.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 opOk
| 35966.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnCmtErr
| 35966.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnOk
| 35967.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 opOk
| 35967.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnCmtErr
| _elapsed___errors__ops/sec(inst)___ops/sec(cum)__p50(ms)__p95(ms)__p99(ms)_pMax(ms)
| 35967.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnOk
| 35968.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 opOk
| 35968.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnCmtErr
| 35968.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnOk
| 35969.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 opOk
| 35969.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnCmtErr
| 35969.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnOk
| 35970.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 opOk
| 35970.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnCmtErr
| 35970.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnOk
| 35971.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 opOk
| 35971.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnCmtErr
| 35971.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnOk
| 35972.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 opOk
| 35972.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnCmtErr
| 35972.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnOk
| 35973.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 opOk
| 35973.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnCmtErr
| 35973.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnOk
| 35974.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 opOk
| _elapsed___errors__ops/sec(inst)___ops/sec(cum)__p50(ms)__p95(ms)__p99(ms)_pMax(ms)
| 35974.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnCmtErr
| 35974.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnOk
| 35975.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 opOk
| 35975.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnCmtErr
| 35975.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnOk
| 35976.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 opOk
| 35976.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnCmtErr
| 35976.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnOk
| 35977.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 opOk
| 35977.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnCmtErr
| 35977.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnOk
| 35978.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 opOk
| 35978.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnCmtErr
| 35978.0s 49 0.0 0.0 0.0 0.0 0.0 0.0 txnOk
Wraps: (5) secondary error attachment
| signal: killed
| (1) signal: killed
| Error types: (1) *exec.ExitError
Wraps: (6) context canceled
Error types: (1) *withstack.withStack (2) *safedetails.withSafeDetails (3) *errutil.withMessage (4) *main.withCommandDetails (5) *secondary.withSecondaryError (6) *errors.errorString
```
<details><summary>More</summary><p>
Artifacts: [/schemachange/random-load](https://teamcity.cockroachdb.com/viewLog.html?buildId=2032556&tab=artifacts#/schemachange/random-load)
Related:
- #50557 roachtest: schemachange/random-load failed [C-test-failure](https://api.github.com/repos/cockroachdb/cockroach/labels/C-test-failure) [O-roachtest](https://api.github.com/repos/cockroachdb/cockroach/labels/O-roachtest) [O-robot](https://api.github.com/repos/cockroachdb/cockroach/labels/O-robot) [branch-release-19.1](https://api.github.com/repos/cockroachdb/cockroach/labels/branch-release-19.1) [release-blocker](https://api.github.com/repos/cockroachdb/cockroach/labels/release-blocker)
[See this test on roachdash](https://roachdash.crdb.dev/?filter=status%3Aopen+t%3A.%2Aschemachange%2Frandom-load.%2A&sort=title&restgroup=false&display=lastcommented+project)
<sub>powered by [pkg/cmd/internal/issues](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)</sub></p></details>
| non_usab | roachtest schemachange random load failed on opok txncmterr txnok opok txncmterr txnok opok txncmterr elapsed errors ops sec inst ops sec cum ms ms ms pmax ms txnok opok txncmterr txnok opok txncmterr txnok opok txncmterr txnok opok txncmterr txnok opok txncmterr txnok opok txncmterr txnok opok elapsed errors ops sec inst ops sec cum ms ms ms pmax ms txncmterr txnok opok txncmterr txnok opok txncmterr txnok opok txncmterr txnok opok txncmterr txnok wraps secondary error attachment signal killed signal killed error types exec exiterror wraps context canceled error types withstack withstack safedetails withsafedetails errutil withmessage main withcommanddetails secondary withsecondaryerror errors errorstring more artifacts related roachtest schemachange random load failed powered by | 0 |
342,507 | 24,745,781,982 | IssuesEvent | 2022-10-21 09:33:57 | tinkoff-ai/etna | https://api.github.com/repos/tinkoff-ai/etna | opened | Improve the Readme | documentation | ### 🚀 Feature Request
It seems we have not appropriate readme structure, it should be slightly improved
### Proposal
TODO
### Test cases
_No response_
### Additional context
_No response_ | 1.0 | Improve the Readme - ### 🚀 Feature Request
It seems we have not appropriate readme structure, it should be slightly improved
### Proposal
TODO
### Test cases
_No response_
### Additional context
_No response_ | non_usab | improve the readme 🚀 feature request it seems we have not appropriate readme structure it should be slightly improved proposal todo test cases no response additional context no response | 0 |
22,328 | 19,074,106,022 | IssuesEvent | 2021-11-27 12:53:29 | imchillin/Anamnesis | https://api.github.com/repos/imchillin/Anamnesis | closed | Application slowdown when posing over extended durations | Bug Posing Investigate Usability DevOps | It would appear that loading .cmp files causes the tool to slow down considerably. We still have yet to find the actual link to prove this theory, despite it being the one thing in common amongst reports. Can only investigate and get additional log files to find a pattern. <s>thank christ this is still in beta</s> | True | Application slowdown when posing over extended durations - It would appear that loading .cmp files causes the tool to slow down considerably. We still have yet to find the actual link to prove this theory, despite it being the one thing in common amongst reports. Can only investigate and get additional log files to find a pattern. <s>thank christ this is still in beta</s> | usab | application slowdown when posing over extended durations it would appear that loading cmp files causes the tool to slow down considerably we still have yet to find the actual link to prove this theory despite it being the one thing in common amongst reports can only investigate and get additional log files to find a pattern thank christ this is still in beta | 1 |
4,500 | 3,870,267,658 | IssuesEvent | 2016-04-11 02:01:48 | lionheart/openradar-mirror | https://api.github.com/repos/lionheart/openradar-mirror | opened | 22983352: 10.11 Disk Utility App Useless in El Capitan | classification:ui/usability reproducible:always status:open | #### Description
Summary:
The Disk Utility App in El Capitan is practically useless. It is less user friendly and less functional. It is a major step back from previous versions of Disk Utility in OS X.
Steps to Reproduce:
Example:
1. Attach a disk with an encrypted JHFS+ filesystem
* Close the auto-prompt for password if asked
2. Open Disk Utility and try to mount the encrypted volume
Expected Results:
I expect it to be easy to mount this volume. The "unlock" function should be in the toolbar by default when applicable. I expect there to be a right-click context menu to allow the appropriate actions when I right-click on a drive or volume.
Actual Results:
The application is pure useless. I might as well throw OS X UI away and do everything from the command line from the start.
Version:
10.11 (15A284)
Notes:
Configuration:
Attachments:
'Screen Shot 2015-10-05 at 6.18.29 PM.png' was successfully uploaded.
-
Product Version: 10.11 (15A284)
Created: 2015-10-06T00:24:15.611070
Originated: 2015-10-05T18:23:00
Open Radar Link: http://www.openradar.me/22983352 | True | 22983352: 10.11 Disk Utility App Useless in El Capitan - #### Description
Summary:
The Disk Utility App in El Capitan is practically useless. It is less user friendly and less functional. It is a major step back from previous versions of Disk Utility in OS X.
Steps to Reproduce:
Example:
1. Attach a disk with an encrypted JHFS+ filesystem
* Close the auto-prompt for password if asked
2. Open Disk Utility and try to mount the encrypted volume
Expected Results:
I expect it to be easy to mount this volume. The "unlock" function should be in the toolbar by default when applicable. I expect there to be a right-click context menu to allow the appropriate actions when I right-click on a drive or volume.
Actual Results:
The application is pure useless. I might as well throw OS X UI away and do everything from the command line from the start.
Version:
10.11 (15A284)
Notes:
Configuration:
Attachments:
'Screen Shot 2015-10-05 at 6.18.29 PM.png' was successfully uploaded.
-
Product Version: 10.11 (15A284)
Created: 2015-10-06T00:24:15.611070
Originated: 2015-10-05T18:23:00
Open Radar Link: http://www.openradar.me/22983352 | usab | disk utility app useless in el capitan description summary the disk utility app in el capitan is practically useless it is less user friendly and less functional it is a major step back from previous versions of disk utility in os x steps to reproduce example attach a disk with an encrypted jhfs filesystem close the auto prompt for password if asked open disk utility and try to mount the encrypted volume expected results i expect it to be easy to mount this volume the unlock function should be in the toolbar by default when applicable i expect there to be a right click context menu to allow the appropriate actions when i right click on a drive or volume actual results the application is pure useless i might as well throw os x ui away and do everything from the command line from the start version notes configuration attachments screen shot at pm png was successfully uploaded product version created originated open radar link | 1 |
23,434 | 21,897,018,945 | IssuesEvent | 2022-05-20 09:36:31 | opentap/opentap | https://api.github.com/repos/opentap/opentap | closed | API for expanding/collapsing test steps heirachies | Usability Feature | Based on user request. It would be helpful to be able to control the expand/collapse state from an API, and also save the state as a part of the test plan.
| True | API for expanding/collapsing test steps heirachies - Based on user request. It would be helpful to be able to control the expand/collapse state from an API, and also save the state as a part of the test plan.
| usab | api for expanding collapsing test steps heirachies based on user request it would be helpful to be able to control the expand collapse state from an api and also save the state as a part of the test plan | 1 |
97,755 | 11,031,642,900 | IssuesEvent | 2019-12-06 18:14:02 | humanmade/hm-juicer | https://api.github.com/repos/humanmade/hm-juicer | closed | Add constants documentation to plugin README.md | documentation good first issue | #6 adds a number of new constants. Currently only one is documented in the main README.md file. We should document the others as well. | 1.0 | Add constants documentation to plugin README.md - #6 adds a number of new constants. Currently only one is documented in the main README.md file. We should document the others as well. | non_usab | add constants documentation to plugin readme md adds a number of new constants currently only one is documented in the main readme md file we should document the others as well | 0 |
301,342 | 26,037,764,246 | IssuesEvent | 2022-12-22 07:29:15 | commercialhaskell/stackage | https://api.github.com/repos/commercialhaskell/stackage | closed | aws-sns-verify test failure | failure: test-suite | ```
Test suite failure for package aws-sns-verify-0.0.0.2
aws-sns-verify-test: exited with: ExitFailure 1
Full log available at /var/stackage/work/unpack-dir/.stack-work/logs/aws-sns-verify-0.0.0.2-test.log
Amazon.SNS.Verify
verifySNSMessage
successfully validates an SNS notification [✘]
successfully confirms a subscription [✘]
Amazon.SNS.Verify.Validate
validateSnsMessage
successfully validates an SNS notification [✘]
fails to validate a currupt SNS notification [✘]
fails to validate a bad PEM [✘]
fails to validate an unexpected url [✔]
successfully validates an SNS subscription [✘]
successfully validates an SNS unsubscribe [✘]
...
Failures:
tests/Amazon/SNS/VerifySpec.hs:15:5:
1) Amazon.SNS.Verify.verifySNSMessage successfully validates an SNS notification
uncaught exception: SNSNotificationValidationError
BadUri "http://localhost:3000"
To rerun use: --match "/Amazon.SNS.Verify/verifySNSMessage/successfully validates an SNS notification/"
tests/Amazon/SNS/VerifySpec.hs:51:9:
2) Amazon.SNS.Verify.verifySNSMessage successfully confirms a subscription
predicate failed on expected exception: SNSNotificationValidationError (BadUri "http://localhost:3000")
To rerun use: --match "/Amazon.SNS.Verify/verifySNSMessage/successfully confirms a subscription/"
tests/Amazon/SNS/Verify/ValidateSpec.hs:32:9:
3) Amazon.SNS.Verify.Validate.validateSnsMessage successfully validates an SNS notification expected: Right (SNSMessage "Some message")
but got: Left (BadUri "http://localhost:3000")
To rerun use: --match "/Amazon.SNS.Verify.Validate/validateSnsMessage/successfully validates an SNS notification/"
tests/Amazon/SNS/Verify/ValidateSpec.hs:52:10:
4) Amazon.SNS.Verify.Validate.validateSnsMessage fails to validate a currupt SNS notification
expected: Left (InvalidPayload SignatureInvalid)
but got: Left (BadUri "http://localhost:3000")
To rerun use: --match "/Amazon.SNS.Verify.Validate/validateSnsMessage/fails to validate a currupt SNS notification/"
...
```
Will disable the test for now. CC @pbrisbin @mjgpy3 @StevenXL | 1.0 | aws-sns-verify test failure - ```
Test suite failure for package aws-sns-verify-0.0.0.2
aws-sns-verify-test: exited with: ExitFailure 1
Full log available at /var/stackage/work/unpack-dir/.stack-work/logs/aws-sns-verify-0.0.0.2-test.log
Amazon.SNS.Verify
verifySNSMessage
successfully validates an SNS notification [✘]
successfully confirms a subscription [✘]
Amazon.SNS.Verify.Validate
validateSnsMessage
successfully validates an SNS notification [✘]
fails to validate a currupt SNS notification [✘]
fails to validate a bad PEM [✘]
fails to validate an unexpected url [✔]
successfully validates an SNS subscription [✘]
successfully validates an SNS unsubscribe [✘]
...
Failures:
tests/Amazon/SNS/VerifySpec.hs:15:5:
1) Amazon.SNS.Verify.verifySNSMessage successfully validates an SNS notification
uncaught exception: SNSNotificationValidationError
BadUri "http://localhost:3000"
To rerun use: --match "/Amazon.SNS.Verify/verifySNSMessage/successfully validates an SNS notification/"
tests/Amazon/SNS/VerifySpec.hs:51:9:
2) Amazon.SNS.Verify.verifySNSMessage successfully confirms a subscription
predicate failed on expected exception: SNSNotificationValidationError (BadUri "http://localhost:3000")
To rerun use: --match "/Amazon.SNS.Verify/verifySNSMessage/successfully confirms a subscription/"
tests/Amazon/SNS/Verify/ValidateSpec.hs:32:9:
3) Amazon.SNS.Verify.Validate.validateSnsMessage successfully validates an SNS notification expected: Right (SNSMessage "Some message")
but got: Left (BadUri "http://localhost:3000")
To rerun use: --match "/Amazon.SNS.Verify.Validate/validateSnsMessage/successfully validates an SNS notification/"
tests/Amazon/SNS/Verify/ValidateSpec.hs:52:10:
4) Amazon.SNS.Verify.Validate.validateSnsMessage fails to validate a currupt SNS notification
expected: Left (InvalidPayload SignatureInvalid)
but got: Left (BadUri "http://localhost:3000")
To rerun use: --match "/Amazon.SNS.Verify.Validate/validateSnsMessage/fails to validate a currupt SNS notification/"
...
```
Will disable the test for now. CC @pbrisbin @mjgpy3 @StevenXL | non_usab | aws sns verify test failure test suite failure for package aws sns verify aws sns verify test exited with exitfailure full log available at var stackage work unpack dir stack work logs aws sns verify test log amazon sns verify verifysnsmessage successfully validates an sns notification successfully confirms a subscription amazon sns verify validate validatesnsmessage successfully validates an sns notification fails to validate a currupt sns notification fails to validate a bad pem fails to validate an unexpected url successfully validates an sns subscription successfully validates an sns unsubscribe failures tests amazon sns verifyspec hs amazon sns verify verifysnsmessage successfully validates an sns notification uncaught exception snsnotificationvalidationerror baduri to rerun use match amazon sns verify verifysnsmessage successfully validates an sns notification tests amazon sns verifyspec hs amazon sns verify verifysnsmessage successfully confirms a subscription predicate failed on expected exception snsnotificationvalidationerror baduri to rerun use match amazon sns verify verifysnsmessage successfully confirms a subscription tests amazon sns verify validatespec hs amazon sns verify validate validatesnsmessage successfully validates an sns notification expected right snsmessage some message but got left baduri to rerun use match amazon sns verify validate validatesnsmessage successfully validates an sns notification tests amazon sns verify validatespec hs amazon sns verify validate validatesnsmessage fails to validate a currupt sns notification expected left invalidpayload signatureinvalid but got left baduri to rerun use match amazon sns verify validate validatesnsmessage fails to validate a currupt sns notification will disable the test for now cc pbrisbin stevenxl | 0 |
63,294 | 26,341,577,618 | IssuesEvent | 2023-01-10 18:07:15 | Azure/azure-cli-extensions | https://api.github.com/repos/Azure/azure-cli-extensions | closed | not able to do az login | question customer-reported Machine Learning Service Attention Auto-Assign Azure CLI Team | <!--- 🛑 Please check existing issues first before continuing: https://github.com/Azure/azure-cli/issues --->
### **This is autogenerated. Please review and update as needed.**
## Describe the bug
**Command Name**
`az login
Extension Name: azure-ml-admin-cli. Version: 0.0.1.`
**Errors:**
```
The command failed with an unexpected error. Here is the traceback:
login() got an unexpected keyword argument 'msi'
Traceback (most recent call last):
File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 233, in invoke
File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 663, in execute
File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 697, in _run_job
File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 333, in __call__
File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 121, in handler
File "C:\Users\saidu\.azure\cliextensions\azure-ml-admin-cli\azext_admin\custom.py", line 82, in mls_login
return login(username=username,
TypeError: login() got an unexpected keyword argument 'msi'
```
## To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
- _Put any pre-requisite steps here..._
- `az login`
## Expected Behavior
## Environment Summary
```
Windows-10-10.0.22621-SP0
Python 3.10.8
Installer: MSI
azure-cli 2.43.0
Extensions:
azure-ml-admin-cli 0.0.1
Dependencies:
msal 1.20.0
azure-mgmt-resource 21.1.0b1
```
## Additional Context
<!--Please don't remove this:-->
<!--auto-generated-->
| 1.0 | not able to do az login - <!--- 🛑 Please check existing issues first before continuing: https://github.com/Azure/azure-cli/issues --->
### **This is autogenerated. Please review and update as needed.**
## Describe the bug
**Command Name**
`az login
Extension Name: azure-ml-admin-cli. Version: 0.0.1.`
**Errors:**
```
The command failed with an unexpected error. Here is the traceback:
login() got an unexpected keyword argument 'msi'
Traceback (most recent call last):
File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 233, in invoke
File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 663, in execute
File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 697, in _run_job
File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 333, in __call__
File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 121, in handler
File "C:\Users\saidu\.azure\cliextensions\azure-ml-admin-cli\azext_admin\custom.py", line 82, in mls_login
return login(username=username,
TypeError: login() got an unexpected keyword argument 'msi'
```
## To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
- _Put any pre-requisite steps here..._
- `az login`
## Expected Behavior
## Environment Summary
```
Windows-10-10.0.22621-SP0
Python 3.10.8
Installer: MSI
azure-cli 2.43.0
Extensions:
azure-ml-admin-cli 0.0.1
Dependencies:
msal 1.20.0
azure-mgmt-resource 21.1.0b1
```
## Additional Context
<!--Please don't remove this:-->
<!--auto-generated-->
| non_usab | not able to do az login this is autogenerated please review and update as needed describe the bug command name az login extension name azure ml admin cli version errors the command failed with an unexpected error here is the traceback login got an unexpected keyword argument msi traceback most recent call last file d a work s build scripts windows artifacts cli lib site packages knack cli py line in invoke file d a work s build scripts windows artifacts cli lib site packages azure cli core commands init py line in execute file d a work s build scripts windows artifacts cli lib site packages azure cli core commands init py line in run jobs serially file d a work s build scripts windows artifacts cli lib site packages azure cli core commands init py line in run job file d a work s build scripts windows artifacts cli lib site packages azure cli core commands init py line in call file d a work s build scripts windows artifacts cli lib site packages azure cli core commands command operation py line in handler file c users saidu azure cliextensions azure ml admin cli azext admin custom py line in mls login return login username username typeerror login got an unexpected keyword argument msi to reproduce steps to reproduce the behavior note that argument values have been redacted as they may contain sensitive information put any pre requisite steps here az login expected behavior environment summary windows python installer msi azure cli extensions azure ml admin cli dependencies msal azure mgmt resource additional context | 0 |
131,238 | 10,686,053,030 | IssuesEvent | 2019-10-22 13:47:46 | dbrownukk/EFD_v2 | https://api.github.com/repos/dbrownukk/EFD_v2 | closed | Household does not validate, but no error shown | For Testing bug | Instance: EFD_HM
App: OIHM
Module: Household
Study: M1 End2End Test
HH: 7
Status is Fully Parsed.
All Resources are status 'valid'.
But they all have 0 units produced or worked (apart from Inputs)
this is as in the spreadsheet attached.
In detail view click Validate
> no response.
HHH 3 has similar data, but 1 invalid resource - Validate runs, but correctly fails for that HH
| 1.0 | Household does not validate, but no error shown - Instance: EFD_HM
App: OIHM
Module: Household
Study: M1 End2End Test
HH: 7
Status is Fully Parsed.
All Resources are status 'valid'.
But they all have 0 units produced or worked (apart from Inputs)
this is as in the spreadsheet attached.
In detail view click Validate
> no response.
HHH 3 has similar data, but 1 invalid resource - Validate runs, but correctly fails for that HH
| non_usab | household does not validate but no error shown instance efd hm app oihm module household study test hh status is fully parsed all resources are status valid but they all have units produced or worked apart from inputs this is as in the spreadsheet attached in detail view click validate no response hhh has similar data but invalid resource validate runs but correctly fails for that hh | 0 |
21,321 | 16,829,047,018 | IssuesEvent | 2021-06-17 23:46:27 | tailscale/tailscale | https://api.github.com/repos/tailscale/tailscale | opened | Windows Server 2019 RDS admin panel does not work when Tailscale is running | L2 Few OS-windows P5 Halts deployment T5 Usability | A customer reported that on Windows Server 2019, the Remote Desktop Services admin panel does not load when Tailscale is installed. I have reproduced the issue but not yet found the cause.
| True | Windows Server 2019 RDS admin panel does not work when Tailscale is running - A customer reported that on Windows Server 2019, the Remote Desktop Services admin panel does not load when Tailscale is installed. I have reproduced the issue but not yet found the cause.
| usab | windows server rds admin panel does not work when tailscale is running a customer reported that on windows server the remote desktop services admin panel does not load when tailscale is installed i have reproduced the issue but not yet found the cause | 1 |
68,714 | 13,171,945,565 | IssuesEvent | 2020-08-11 17:33:25 | atilacamurca/glossario-friends | https://api.github.com/repos/atilacamurca/glossario-friends | closed | Adicionar múltiplas referências na página inicial | code | Fazer com que a página inicial use outras referências, dando um caráter dinâmico a página
Ver se é possível criar uma graphql query para obter as referências, livrando assim de precisar duplicar conteúdo.
Outra ideia seria criar links rápidos para itens interessantes ou não muito conhecidos, talvez com a imagem do episódio um título e um link rápido (ao invés de renderizar o trecho do markdown).
### Referências
- <https://github.com/gs-shop/vue-slick-carousel> - support a SSR nativo
- <https://ssense.github.io/vue-carousel/> usar vue-carousel para colocar várias referências
- <https://github.com/naver/egjs-flicking/blob/master/packages/vue-flicking/README.md> | 1.0 | Adicionar múltiplas referências na página inicial - Fazer com que a página inicial use outras referências, dando um caráter dinâmico a página
Ver se é possível criar uma graphql query para obter as referências, livrando assim de precisar duplicar conteúdo.
Outra ideia seria criar links rápidos para itens interessantes ou não muito conhecidos, talvez com a imagem do episódio um título e um link rápido (ao invés de renderizar o trecho do markdown).
### Referências
- <https://github.com/gs-shop/vue-slick-carousel> - support a SSR nativo
- <https://ssense.github.io/vue-carousel/> usar vue-carousel para colocar várias referências
- <https://github.com/naver/egjs-flicking/blob/master/packages/vue-flicking/README.md> | non_usab | adicionar múltiplas referências na página inicial fazer com que a página inicial use outras referências dando um caráter dinâmico a página ver se é possível criar uma graphql query para obter as referências livrando assim de precisar duplicar conteúdo outra ideia seria criar links rápidos para itens interessantes ou não muito conhecidos talvez com a imagem do episódio um título e um link rápido ao invés de renderizar o trecho do markdown referências support a ssr nativo usar vue carousel para colocar várias referências | 0 |
17,302 | 11,873,582,901 | IssuesEvent | 2020-03-26 17:32:06 | certtools/intelmq | https://api.github.com/repos/certtools/intelmq | closed | Shadowserver parser: Bad error message if report name is unknown | bug component: bots usability | If the report has not file name then this exception occurs:
```
Bot has found a problem.
Traceback (most recent call last):
File "/usr/local/lib/python3.6/dist-packages/intelmq/lib/bot.py", line 267, in start
self.process()
File "/usr/local/lib/python3.6/dist-packages/intelmq/lib/bot.py", line 942, in process
for line in self.parse(report):
File "/usr/local/lib/python3.6/dist-packages/intelmq/bots/parsers/shadowserver/parser.py", line 65, in parse
filename_search = self.__is_filename_regex.search(self.report_name)
TypeError: expected string or bytes-like object
```
Should be a human readable error message. | True | Shadowserver parser: Bad error message if report name is unknown - If the report has not file name then this exception occurs:
```
Bot has found a problem.
Traceback (most recent call last):
File "/usr/local/lib/python3.6/dist-packages/intelmq/lib/bot.py", line 267, in start
self.process()
File "/usr/local/lib/python3.6/dist-packages/intelmq/lib/bot.py", line 942, in process
for line in self.parse(report):
File "/usr/local/lib/python3.6/dist-packages/intelmq/bots/parsers/shadowserver/parser.py", line 65, in parse
filename_search = self.__is_filename_regex.search(self.report_name)
TypeError: expected string or bytes-like object
```
Should be a human readable error message. | usab | shadowserver parser bad error message if report name is unknown if the report has not file name then this exception occurs bot has found a problem traceback most recent call last file usr local lib dist packages intelmq lib bot py line in start self process file usr local lib dist packages intelmq lib bot py line in process for line in self parse report file usr local lib dist packages intelmq bots parsers shadowserver parser py line in parse filename search self is filename regex search self report name typeerror expected string or bytes like object should be a human readable error message | 1 |
5,365 | 3,918,153,563 | IssuesEvent | 2016-04-21 11:15:07 | kolliSuman/issues | https://api.github.com/repos/kolliSuman/issues | closed | QA_Vibration of M.D.O.F System_Manual_p1 | Category: Usability Developed By: VLEAD Release Number: Production Severity: S2 Status: Open | Defect Description :
In the Manual page of "Vibration of M.D.O.F System" experiment,when we click on the manual link,it is taking much time to open the manual video instead the redirecting to a new tab with the selected link
Actual Result :
In the Manual page of "Vibration of M.D.O.F System" experiment,when we click on the manual link,it is taking much time to open the manual video
Environment :
OS: Windows 7, Ubuntu-16.04,Centos-6
Browsers: Firefox-42.0,Chrome-47.0,chromium-45.0
Bandwidth : 100Mbps
Hardware Configuration:8GBRAM
Processor:i5
Test Step Link:
https://github.com/Virtual-Labs/Structural Dynami/blob/master/test-cases/integration_test-cases/Vibration%20of%20M.D.O.F%20System/Vibration%20of%20M.D.O.F%20System_08_Manual_p1.org | True | QA_Vibration of M.D.O.F System_Manual_p1 - Defect Description :
In the Manual page of "Vibration of M.D.O.F System" experiment,when we click on the manual link,it is taking much time to open the manual video instead the redirecting to a new tab with the selected link
Actual Result :
In the Manual page of "Vibration of M.D.O.F System" experiment,when we click on the manual link,it is taking much time to open the manual video
Environment :
OS: Windows 7, Ubuntu-16.04,Centos-6
Browsers: Firefox-42.0,Chrome-47.0,chromium-45.0
Bandwidth : 100Mbps
Hardware Configuration:8GBRAM
Processor:i5
Test Step Link:
https://github.com/Virtual-Labs/Structural Dynami/blob/master/test-cases/integration_test-cases/Vibration%20of%20M.D.O.F%20System/Vibration%20of%20M.D.O.F%20System_08_Manual_p1.org | usab | qa vibration of m d o f system manual defect description in the manual page of vibration of m d o f system experiment when we click on the manual link it is taking much time to open the manual video instead the redirecting to a new tab with the selected link actual result in the manual page of vibration of m d o f system experiment when we click on the manual link it is taking much time to open the manual video environment os windows ubuntu centos browsers firefox chrome chromium bandwidth hardware configuration processor test step link dynami blob master test cases integration test cases vibration d o f vibration d o f manual org | 1 |
669,988 | 22,648,853,999 | IssuesEvent | 2022-07-01 11:28:05 | Enabel/flysystem-sharepoint | https://api.github.com/repos/Enabel/flysystem-sharepoint | opened | Create file when directory already exist | Priority: Must have (vital) [Critical] Type: Bug | If the directory "/foo" already exist trying to add a file in "/foo/bar" doen't work
```php
$flysytem->write("/foo/bar/baz.txt", "content");
```
=> Call this method "->requestDirectoryMetadata("bar")". Because "/bar" doesn't exist on the root directory, it would then try to create "/foo/bar" and throw an exception because "/foo/bar" already exists. | 1.0 | Create file when directory already exist - If the directory "/foo" already exist trying to add a file in "/foo/bar" doen't work
```php
$flysytem->write("/foo/bar/baz.txt", "content");
```
=> Call this method "->requestDirectoryMetadata("bar")". Because "/bar" doesn't exist on the root directory, it would then try to create "/foo/bar" and throw an exception because "/foo/bar" already exists. | non_usab | create file when directory already exist if the directory foo already exist trying to add a file in foo bar doen t work php flysytem write foo bar baz txt content call this method requestdirectorymetadata bar because bar doesn t exist on the root directory it would then try to create foo bar and throw an exception because foo bar already exists | 0 |
715,575 | 24,604,660,830 | IssuesEvent | 2022-10-14 15:10:44 | open-telemetry/opentelemetry-js | https://api.github.com/repos/open-telemetry/opentelemetry-js | closed | bug(EnvDetector): does not support otel resource attribute values containing spaces | bug priority:p2 | ### What happened?
## Steps to Reproduce
set any otel resource attribute to a value containing a space
```
export OTEL_RESOURCE_ATTRIBUTES='service.name="foo bar"'
```
## Expected Result
I would expect the events sent to otel collector to would have the same attributes set in `OTEL_RESOURCE_ATTRIBUTES`.
## Actual Result
`EnvDetector` throws the following error
```
EnvDetector failed: Attribute value should be a ASCII string with a length not exceed 255 characters.
```
and the otel resource attributes are not present on the events sent to the otel collector.
## Additional Details
### OpenTelemetry Setup Code
```JavaScript
import { diag, DiagConsoleLogger, DiagLogLevel } from '@opentelemetry/api'
import { getNodeAutoInstrumentations } from '@opentelemetry/auto-instrumentations-node'
import { OTLPTraceExporter } from '@opentelemetry/exporter-trace-otlp-http'
import * as opentelemetry from '@opentelemetry/sdk-node'
diag.setLogger(new DiagConsoleLogger(), DiagLogLevel.DEBUG)
const opentelemetrySDK = new opentelemetry.NodeSDK({
instrumentations: [
getNodeAutoInstrumentations({
'@opentelemetry/instrumentation-express': {
ignoreLayers: [/.*/],
},
'@opentelemetry/instrumentation-http': {
ignoreIncomingRequestHook: (request) => {
const ignoreIncomingRequestUrls = ['/ignore']
return ignoreIncomingRequestUrls.includes(request.url)
},
},
}),
],
traceExporter: new OTLPTraceExporter(),
})
opentelemetrySDK.start()
process.on('SIGTERM', () => {
opentelemetrySDK.shutdown().finally(() => process.exit(0))
})
```
### package.json
```JSON
{
"dependencies": {
"@opentelemetry/api": "1.2.0",
"@opentelemetry/auto-instrumentations-node": "0.31.2",
"@opentelemetry/exporter-trace-otlp-http": "0.28.0",
"@opentelemetry/sdk-node": "0.31.0"
}
}
```
### Relevant log output
```shell
EnvDetector failed: Attribute value should be a ASCII string with a length not exceed 255 characters.
```
| 1.0 | bug(EnvDetector): does not support otel resource attribute values containing spaces - ### What happened?
## Steps to Reproduce
set any otel resource attribute to a value containing a space
```
export OTEL_RESOURCE_ATTRIBUTES='service.name="foo bar"'
```
## Expected Result
I would expect the events sent to otel collector to would have the same attributes set in `OTEL_RESOURCE_ATTRIBUTES`.
## Actual Result
`EnvDetector` throws the following error
```
EnvDetector failed: Attribute value should be a ASCII string with a length not exceed 255 characters.
```
and the otel resource attributes are not present on the events sent to the otel collector.
## Additional Details
### OpenTelemetry Setup Code
```JavaScript
import { diag, DiagConsoleLogger, DiagLogLevel } from '@opentelemetry/api'
import { getNodeAutoInstrumentations } from '@opentelemetry/auto-instrumentations-node'
import { OTLPTraceExporter } from '@opentelemetry/exporter-trace-otlp-http'
import * as opentelemetry from '@opentelemetry/sdk-node'
diag.setLogger(new DiagConsoleLogger(), DiagLogLevel.DEBUG)
const opentelemetrySDK = new opentelemetry.NodeSDK({
instrumentations: [
getNodeAutoInstrumentations({
'@opentelemetry/instrumentation-express': {
ignoreLayers: [/.*/],
},
'@opentelemetry/instrumentation-http': {
ignoreIncomingRequestHook: (request) => {
const ignoreIncomingRequestUrls = ['/ignore']
return ignoreIncomingRequestUrls.includes(request.url)
},
},
}),
],
traceExporter: new OTLPTraceExporter(),
})
opentelemetrySDK.start()
process.on('SIGTERM', () => {
opentelemetrySDK.shutdown().finally(() => process.exit(0))
})
```
### package.json
```JSON
{
"dependencies": {
"@opentelemetry/api": "1.2.0",
"@opentelemetry/auto-instrumentations-node": "0.31.2",
"@opentelemetry/exporter-trace-otlp-http": "0.28.0",
"@opentelemetry/sdk-node": "0.31.0"
}
}
```
### Relevant log output
```shell
EnvDetector failed: Attribute value should be a ASCII string with a length not exceed 255 characters.
```
| non_usab | bug envdetector does not support otel resource attribute values containing spaces what happened steps to reproduce set any otel resource attribute to a value containing a space export otel resource attributes service name foo bar expected result i would expect the events sent to otel collector to would have the same attributes set in otel resource attributes actual result envdetector throws the following error envdetector failed attribute value should be a ascii string with a length not exceed characters and the otel resource attributes are not present on the events sent to the otel collector additional details opentelemetry setup code javascript import diag diagconsolelogger diagloglevel from opentelemetry api import getnodeautoinstrumentations from opentelemetry auto instrumentations node import otlptraceexporter from opentelemetry exporter trace otlp http import as opentelemetry from opentelemetry sdk node diag setlogger new diagconsolelogger diagloglevel debug const opentelemetrysdk new opentelemetry nodesdk instrumentations getnodeautoinstrumentations opentelemetry instrumentation express ignorelayers opentelemetry instrumentation http ignoreincomingrequesthook request const ignoreincomingrequesturls return ignoreincomingrequesturls includes request url traceexporter new otlptraceexporter opentelemetrysdk start process on sigterm opentelemetrysdk shutdown finally process exit package json json dependencies opentelemetry api opentelemetry auto instrumentations node opentelemetry exporter trace otlp http opentelemetry sdk node relevant log output shell envdetector failed attribute value should be a ascii string with a length not exceed characters | 0 |
25,344 | 6,653,683,696 | IssuesEvent | 2017-09-29 09:25:30 | openbmc/openbmc-test-automation | https://api.github.com/repos/openbmc/openbmc-test-automation | closed | Code update: Remaining upload image of BMC/ PNOR test cases | Epic Func:CodeUpdate Test | - [ ] BMC/PNOR: Upload image with incorrect MANIFEST
- [ ] BMC/PNOR: Upload image with incorrect Image | 1.0 | Code update: Remaining upload image of BMC/ PNOR test cases - - [ ] BMC/PNOR: Upload image with incorrect MANIFEST
- [ ] BMC/PNOR: Upload image with incorrect Image | non_usab | code update remaining upload image of bmc pnor test cases bmc pnor upload image with incorrect manifest bmc pnor upload image with incorrect image | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.