Unnamed: 0
int64 0
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 1
744
| labels
stringlengths 4
574
| body
stringlengths 9
211k
| index
stringclasses 10
values | text_combine
stringlengths 96
211k
| label
stringclasses 2
values | text
stringlengths 96
188k
| binary_label
int64 0
1
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
21,913
| 30,443,451,774
|
IssuesEvent
|
2023-07-15 11:09:11
|
h4sh5/pypi-auto-scanner
|
https://api.github.com/repos/h4sh5/pypi-auto-scanner
|
opened
|
skypilot-nightly 1.0.0.dev20230715 has 2 GuardDog issues
|
guarddog exec-base64 silent-process-execution
|
https://pypi.org/project/skypilot-nightly
https://inspector.pypi.io/project/skypilot-nightly
```{
"dependency": "skypilot-nightly",
"version": "1.0.0.dev20230715",
"result": {
"issues": 2,
"errors": {},
"results": {
"exec-base64": [
{
"location": "skypilot-nightly-1.0.0.dev20230715/sky/cloud_stores.py:110",
"code": " p = subprocess.run(command,\n stdout=subprocess.PIPE,\n shell=True,\n check=True,\n executable='/bin/bash')",
"message": "This package contains a call to the `eval` function with a `base64` encoded string as argument.\nThis is a common method used to hide a malicious payload in a module as static analysis will not decode the\nstring.\n"
}
],
"silent-process-execution": [
{
"location": "skypilot-nightly-1.0.0.dev20230715/sky/skylet/log_lib.py:219",
"code": " subprocess.Popen(\n daemon_cmd,\n start_new_session=True,\n # Suppress output\n stdout=subprocess.DEVNULL,\n stderr=subprocess.DEVNULL,\n # Disa... )",
"message": "This package is silently executing an external binary, redirecting stdout, stderr and stdin to /dev/null"
}
]
},
"path": "/tmp/tmpt1rm056_/skypilot-nightly"
}
}```
|
1.0
|
skypilot-nightly 1.0.0.dev20230715 has 2 GuardDog issues - https://pypi.org/project/skypilot-nightly
https://inspector.pypi.io/project/skypilot-nightly
```{
"dependency": "skypilot-nightly",
"version": "1.0.0.dev20230715",
"result": {
"issues": 2,
"errors": {},
"results": {
"exec-base64": [
{
"location": "skypilot-nightly-1.0.0.dev20230715/sky/cloud_stores.py:110",
"code": " p = subprocess.run(command,\n stdout=subprocess.PIPE,\n shell=True,\n check=True,\n executable='/bin/bash')",
"message": "This package contains a call to the `eval` function with a `base64` encoded string as argument.\nThis is a common method used to hide a malicious payload in a module as static analysis will not decode the\nstring.\n"
}
],
"silent-process-execution": [
{
"location": "skypilot-nightly-1.0.0.dev20230715/sky/skylet/log_lib.py:219",
"code": " subprocess.Popen(\n daemon_cmd,\n start_new_session=True,\n # Suppress output\n stdout=subprocess.DEVNULL,\n stderr=subprocess.DEVNULL,\n # Disa... )",
"message": "This package is silently executing an external binary, redirecting stdout, stderr and stdin to /dev/null"
}
]
},
"path": "/tmp/tmpt1rm056_/skypilot-nightly"
}
}```
|
process
|
skypilot nightly has guarddog issues dependency skypilot nightly version result issues errors results exec location skypilot nightly sky cloud stores py code p subprocess run command n stdout subprocess pipe n shell true n check true n executable bin bash message this package contains a call to the eval function with a encoded string as argument nthis is a common method used to hide a malicious payload in a module as static analysis will not decode the nstring n silent process execution location skypilot nightly sky skylet log lib py code subprocess popen n daemon cmd n start new session true n suppress output n stdout subprocess devnull n stderr subprocess devnull n disa message this package is silently executing an external binary redirecting stdout stderr and stdin to dev null path tmp skypilot nightly
| 1
|
10,070
| 13,044,161,863
|
IssuesEvent
|
2020-07-29 03:47:27
|
tikv/tikv
|
https://api.github.com/repos/tikv/tikv
|
closed
|
UCP: Migrate scalar function `UTCTimeWithoutArg` from TiDB
|
challenge-program-2 component/coprocessor difficulty/easy sig/coprocessor
|
## Description
Port the scalar function `UTCTimeWithoutArg` from TiDB to coprocessor.
## Score
* 50
## Mentor(s)
* @andylokandy
## Recommended Skills
* Rust programming
## Learning Materials
Already implemented expressions ported from TiDB
- https://github.com/tikv/tikv/tree/master/components/tidb_query/src/rpn_expr)
- https://github.com/tikv/tikv/tree/master/components/tidb_query/src/expr)
|
2.0
|
UCP: Migrate scalar function `UTCTimeWithoutArg` from TiDB -
## Description
Port the scalar function `UTCTimeWithoutArg` from TiDB to coprocessor.
## Score
* 50
## Mentor(s)
* @andylokandy
## Recommended Skills
* Rust programming
## Learning Materials
Already implemented expressions ported from TiDB
- https://github.com/tikv/tikv/tree/master/components/tidb_query/src/rpn_expr)
- https://github.com/tikv/tikv/tree/master/components/tidb_query/src/expr)
|
process
|
ucp migrate scalar function utctimewithoutarg from tidb description port the scalar function utctimewithoutarg from tidb to coprocessor score mentor s andylokandy recommended skills rust programming learning materials already implemented expressions ported from tidb
| 1
|
6,616
| 9,696,314,917
|
IssuesEvent
|
2019-05-25 06:15:01
|
AmpersandTarski/Ampersand
|
https://api.github.com/repos/AmpersandTarski/Ampersand
|
closed
|
Compilation fails to reproduce on Travis
|
software process
|
<!-- Thanks for contributing to Ampersand! Please pick a clear title and proceed. -->
<!-- Please note: If your issue is about RAP3, please report it over there:
https://github.com/AmpersandTarski/RAP/issues
-->
#### Version of ampersand that was used
Ampersand-v3.17.0 [tryPullReq:e40e14a97*], build time: 25-May-19 06:18:49 CEST
#### What I expected
I expected that Travis will compile without errors any Ampersand that is compiled without errors on my laptop.
#### What happened instead
Travis failed to compile Ampersand, whereas this Ampersand compiles without errors on my laptop.
#### Steps to reproduce
1. check out branch ["tryPullReq" from GitHub](https://github.com/AmpersandTarski/Ampersand/tree/tryPullReq)
2. verify on your laptop that Ampersand can be compiled.
3. inspect the [result on Travis](https://travis-ci.org/AmpersandTarski/Ampersand/jobs/537066631) to see that Travis failed.
#### Screenshot / Video
<img width="1192" alt="Screenshot 2019-05-25 at 06 26 34" src="https://user-images.githubusercontent.com/275768/58364556-a215dc00-7eb6-11e9-86a4-75f54b87c3db.png">
#### Context / Source of ampersand script
<!-- Optional: share your script if possible. It helps us reproduce the problem. Please try to keep the scripts tiny
We'd also love to know how you found the bug: #dogfooding, #manual-testing, #automated-testing, or #user-report if applicable.
If requesting a new feature, explain why you'd like to see it added.
-->
|
1.0
|
Compilation fails to reproduce on Travis - <!-- Thanks for contributing to Ampersand! Please pick a clear title and proceed. -->
<!-- Please note: If your issue is about RAP3, please report it over there:
https://github.com/AmpersandTarski/RAP/issues
-->
#### Version of ampersand that was used
Ampersand-v3.17.0 [tryPullReq:e40e14a97*], build time: 25-May-19 06:18:49 CEST
#### What I expected
I expected that Travis will compile without errors any Ampersand that is compiled without errors on my laptop.
#### What happened instead
Travis failed to compile Ampersand, whereas this Ampersand compiles without errors on my laptop.
#### Steps to reproduce
1. check out branch ["tryPullReq" from GitHub](https://github.com/AmpersandTarski/Ampersand/tree/tryPullReq)
2. verify on your laptop that Ampersand can be compiled.
3. inspect the [result on Travis](https://travis-ci.org/AmpersandTarski/Ampersand/jobs/537066631) to see that Travis failed.
#### Screenshot / Video
<img width="1192" alt="Screenshot 2019-05-25 at 06 26 34" src="https://user-images.githubusercontent.com/275768/58364556-a215dc00-7eb6-11e9-86a4-75f54b87c3db.png">
#### Context / Source of ampersand script
<!-- Optional: share your script if possible. It helps us reproduce the problem. Please try to keep the scripts tiny
We'd also love to know how you found the bug: #dogfooding, #manual-testing, #automated-testing, or #user-report if applicable.
If requesting a new feature, explain why you'd like to see it added.
-->
|
process
|
compilation fails to reproduce on travis please note if your issue is about please report it over there version of ampersand that was used ampersand build time may cest what i expected i expected that travis will compile without errors any ampersand that is compiled without errors on my laptop what happened instead travis failed to compile ampersand whereas this ampersand compiles without errors on my laptop steps to reproduce check out branch verify on your laptop that ampersand can be compiled inspect the to see that travis failed screenshot video img width alt screenshot at src context source of ampersand script optional share your script if possible it helps us reproduce the problem please try to keep the scripts tiny we d also love to know how you found the bug dogfooding manual testing automated testing or user report if applicable if requesting a new feature explain why you d like to see it added
| 1
|
13,132
| 15,531,284,174
|
IssuesEvent
|
2021-03-13 22:50:25
|
Ultimate-Hosts-Blacklist/whitelist
|
https://api.github.com/repos/Ultimate-Hosts-Blacklist/whitelist
|
closed
|
[FALSE-POSITIVE?] Windows Weather application no connection to service
|
whitelisting process
|
When I use your domain block list filter I'm unable to use the Weather application in Windows 10. It just says there is no connection probably because a domain is blocked. Is this communication considered as spy or telemetry or it's just wrong addition to the list.
|
1.0
|
[FALSE-POSITIVE?] Windows Weather application no connection to service - When I use your domain block list filter I'm unable to use the Weather application in Windows 10. It just says there is no connection probably because a domain is blocked. Is this communication considered as spy or telemetry or it's just wrong addition to the list.
|
process
|
windows weather application no connection to service when i use your domain block list filter i m unable to use the weather application in windows it just says there is no connection probably because a domain is blocked is this communication considered as spy or telemetry or it s just wrong addition to the list
| 1
|
27,426
| 13,247,638,305
|
IssuesEvent
|
2020-08-19 17:35:28
|
spinnaker/keel
|
https://api.github.com/repos/spinnaker/keel
|
closed
|
We have a lot of artifacts, maybe we should clean them up at some point
|
enhancement performance stale to-be-closed
|
The number of artifacts is growing every day since everyone keeps making artifacts. At some point, we should clean them up so they don't overwhelm us.
|
True
|
We have a lot of artifacts, maybe we should clean them up at some point - The number of artifacts is growing every day since everyone keeps making artifacts. At some point, we should clean them up so they don't overwhelm us.
|
non_process
|
we have a lot of artifacts maybe we should clean them up at some point the number of artifacts is growing every day since everyone keeps making artifacts at some point we should clean them up so they don t overwhelm us
| 0
|
701,679
| 24,103,479,184
|
IssuesEvent
|
2022-09-20 04:37:38
|
canonical/jaas-dashboard
|
https://api.github.com/repos/canonical/jaas-dashboard
|
closed
|
Controllers count shows 1 when there are 2
|
Priority: Medium
|
On the controllers view the count in the header only shows 1 when there are more controllers in the list.
|
1.0
|
Controllers count shows 1 when there are 2 - On the controllers view the count in the header only shows 1 when there are more controllers in the list.
|
non_process
|
controllers count shows when there are on the controllers view the count in the header only shows when there are more controllers in the list
| 0
|
20,016
| 26,488,237,621
|
IssuesEvent
|
2023-01-17 20:00:33
|
esmero/ami
|
https://api.github.com/repos/esmero/ami
|
closed
|
CSV Column/Header Sort
|
enhancement LoD Reconciliation CSV Processing
|
What?
---------------------------
Alphabetical sorting of CSV column headers (fields) listed within the Reconcile LoD tab. Future sorting of CSV column headers (fields) for future data harvests.
Example:
Why?
----------------------------
Aids in pinpointing specific fields, and those with and without URI pairings.
|
1.0
|
CSV Column/Header Sort - What?
---------------------------
Alphabetical sorting of CSV column headers (fields) listed within the Reconcile LoD tab. Future sorting of CSV column headers (fields) for future data harvests.
Example:
Why?
----------------------------
Aids in pinpointing specific fields, and those with and without URI pairings.
|
process
|
csv column header sort what alphabetical sorting of csv column headers fields listed within the reconcile lod tab future sorting of csv column headers fields for future data harvests example why aids in pinpointing specific fields and those with and without uri pairings
| 1
|
63,884
| 26,541,921,527
|
IssuesEvent
|
2023-01-19 20:01:15
|
hashicorp/nomad
|
https://api.github.com/repos/hashicorp/nomad
|
closed
|
Nomad marks deployments as successful, before Consul checks are passed.
|
type/bug theme/deployments theme/service-discovery
|
### Nomad version and environment details
Nomad 1.1.2 -> 1.4.2
Consul 1.9.5
Ubuntu 20.04
### Environment configuration:
Servers: 3 nomad servers, consul servers (services register here) + consul servers with ACL.
Clients: we've installed nomad client and consul agent.
### Issue
After upgrading Nomad from 1.1.2 to 1.4.2 some deployments are marked as successful, despite that service has not yet been registered with Consul. This problem is reproduced when running several deployments at the same time.
### Reproduction steps
1. Make docker image of the service, which runs 3 seconds after starting and then fails.
2. Run several deployments via script - [nomad-reproducer.go.txt](https://github.com/hashicorp/nomad/files/10217111/nomad-reproducer.go.txt)
### Expected Behaviour
All deployments fail.
### Actual Behaviour
Few deployments are successful.
### Logs for one allocation for successful deployment
Nomad start to process deployment:
```
nomad[2668973]: 2022-12-09T13:34:35.361+0300 [DEBUG] client.alloc_runner.task_runner: lifecycle start condition has been met, proceeding: alloc_id=384708cc-5ca5-1e14-ca6b-7017045ee3c7 task=shiva-ci-TestNomad-Run-Fail-test-25-2704-task
nomad[2668973]: 2022-12-09T13:34:35.422+0300 [WARN] client.alloc_runner.task_runner.task_hook.logmon: plugin configured with a nil SecureConfig: alloc_id=384708cc-5ca5-1e14-ca6b-7017045ee3c7 task=shiva-ci-TestNomad-Run-Fail-test-25-2704-task
nomad[2668973]: 2022-12-09T13:34:35.422+0300 [DEBUG] client.alloc_runner.task_runner.task_hook.logmon: starting plugin: alloc_id=384708cc-5ca5-1e14-ca6b-7017045ee3c7 task=shiva-ci-TestNomad-Run-Fail-test-25-2704-task path=/usr/bin/nomad args=["/usr/bin/nomad", "logmon"]
nomad[2668973]: 2022-12-09T13:34:35.422+0300 [DEBUG] client.alloc_runner.task_runner.task_hook.logmon: plugin started: alloc_id=384708cc-5ca5-1e14-ca6b-7017045ee3c7 task=shiva-ci-TestNomad-Run-Fail-test-25-2704-task path=/usr/bin/nomad pid=1424417
nomad[2668973]: 2022-12-09T13:34:35.422+0300 [DEBUG] client.alloc_runner.task_runner.task_hook.logmon: waiting for RPC address: alloc_id=384708cc-5ca5-1e14-ca6b-7017045ee3c7 task=shiva-ci-TestNomad-Run-Fail-test-25-2704-task path=/usr/bin/nomad
nomad[2668973]: 2022-12-09T13:34:35.435+0300 [DEBUG] client.alloc_runner.task_runner.task_hook.logmon.nomad: plugin address: alloc_id=384708cc-5ca5-1e14-ca6b-7017045ee3c7 task=shiva-ci-TestNomad-Run-Fail-test-25-2704-task @module=logmon address=/tmp/plugin1614056546 network=unix timestamp="2022-12-09T13:34:35.435+0300"
nomad[2668973]: 2022-12-09T13:34:35.435+0300 [DEBUG] client.alloc_runner.task_runner.task_hook.logmon: using plugin: alloc_id=384708cc-5ca5-1e14-ca6b-7017045ee3c7 task=shiva-ci-TestNomad-Run-Fail-test-25-2704-task version=2
nomad[2668973]: 2022-12-09T13:34:35.442+0300 [INFO] client.alloc_runner.task_runner.task_hook.logmon.nomad: opening fifo: alloc_id=384708cc-5ca5-1e14-ca6b-7017045ee3c7 task=shiva-ci-TestNomad-Run-Fail-test-25-2704-task @module=logmon path=/var/lib/nomad/alloc/384708cc-5ca5-1e14-ca6b-7017045ee3c7/alloc/logs/.shiva-ci-TestNomad-Run-Fail-test-25-2704-task.stdout.fifo timestamp="2022-12-09T13:34:35.442+0300"
nomad[2668973]: 2022-12-09T13:34:35.443+0300 [INFO] client.alloc_runner.task_runner.task_hook.logmon.nomad: opening fifo: alloc_id=384708cc-5ca5-1e14-ca6b-7017045ee3c7 task=shiva-ci-TestNomad-Run-Fail-test-25-2704-task @module=logmon path=/var/lib/nomad/alloc/384708cc-5ca5-1e14-ca6b-7017045ee3c7/alloc/logs/.shiva-ci-TestNomad-Run-Fail-test-25-2704-task.stderr.fifo timestamp="2022-12-09T13:34:35.443+0300"
nomad[2668973]: 2022-12-09T13:34:35.534+0300 [DEBUG] client.driver_mgr.docker: binding directories: driver=docker task_name=shiva-ci-TestNomad-Run-Fail-test-25-2704-task binds="[]string{\"/var/lib/nomad/alloc/384708cc-5ca5-1e14-ca6b-7017045ee3c7/alloc:/alloc\", \"/var/lib/nomad/alloc/384708cc-5ca5-1e14-ca6b-7017045ee3c7/shiva-ci-TestNomad-Run-Fail-test-25-2704-task/local:/local\", \"/var/lib/nomad/alloc/384708cc-5ca5-1e14-ca6b-7017045ee3c7/shiva-ci-TestNomad-Run-Fail-test-25-2704-task/secrets:/secrets\", \"/etc/docker/resolv.conf:/etc/resolv.conf:ro\"}"
nomad[2668973]: 2022-12-09T13:34:35.535+0300 [DEBUG] client.driver_mgr.docker: applied labels on the container: driver=docker task_name=shiva-ci-TestNomad-Run-Fail-test-25-2704-task labels=map[com.hashicorp.nomad.alloc_id:384708cc-5ca5-1e14-ca6b-7017045ee3c7]
nomad[2668973]: 2022-12-09T13:34:35.535+0300 [DEBUG] client.driver_mgr.docker: setting container name: driver=docker task_name=shiva-ci-TestNomad-Run-Fail-test-25-2704-task container_name=shiva-ci-TestNomad-Run-Fail-test-25-2704-task-384708cc-5ca5-1e14-ca6b-7017045ee3c7
```
Dockerd start container:
```
dockerd[60232]: 2022-12-09T13:34:35.535621200+03:00 level=debug msg="Calling POST /containers/create?name=shiva-ci-TestNomad-Run-Fail-test-25-2704-task-384708cc-5ca5-1e14-ca6b-7017045ee3c7"
dockerd[60232]: 2022-12-09T13:34:51.808265565+03:00 level=debug msg="Assigning addresses for endpoint shiva-ci-TestNomad-Run-Fail-test-25-2704-task-384708cc-5ca5-1e14-ca6b-7017045ee3c7's interface on network vertis"
```
Container fail:
```
dockerd[60232]: 2022-12-09T13:34:57.848499016+03:00 level=debug msg="Revoking external connectivity on endpoint shiva-ci-TestNomad-Run-Fail-test-25-2704-task-384708cc-5ca5-1e14-ca6b-7017045ee3c7 (0469b6ae1bb562a08331195c330fb5fb05e231499861b4f5927ddc25020ef9cc)"
dockerd[60232]: 2022-12-09T13:35:03.354392690+03:00 level=debug msg="Releasing addresses for endpoint shiva-ci-TestNomad-Run-Fail-test-25-2704-task-384708cc-5ca5-1e14-ca6b-7017045ee3c7's interface on network vertis"
```
Nomad marks deployment as successful:
```
2022-12-09 13:35:06.120 Deployment Update for ID "cae9bf7e-d534-eab4-a963-7e68893d8474": Status "successful"; Description "Deployment completed successfully"
_PID=241887 _SYSTEMD_UNIT=nomad.service
```
Container restart due to restart policy:
```
nomad[2668973]: 2022-12-09T13:35:06.778+0300 [INFO] client.alloc_runner.task_runner: restarting task: alloc_id=384708cc-5ca5-1e14-ca6b-7017045ee3c7 task=shiva-ci-TestNomad-Run-Fail-test-25-2704-task reason="Restart within policy" delay=1.155116655s
nomad[2668973]: 2022-12-09T13:35:07.938+0300 [DEBUG] client.alloc_runner.task_runner: lifecycle start condition has been met, proceeding: alloc_id=384708cc-5ca5-1e14-ca6b-7017045ee3c7 task=shiva-ci-TestNomad-Run-Fail-test-25-2704-task
nomad[2668973]: 2022-12-09T13:35:07.940+0300 [INFO] client.alloc_runner.task_runner.task_hook.logmon.nomad: opening fifo: alloc_id=384708cc-5ca5-1e14-ca6b-7017045ee3c7 task=shiva-ci-TestNomad-Run-Fail-test-25-2704-task @module=logmon path=/var/lib/nomad/alloc/384708cc-5ca5-1e14-ca6b-7017045ee3c7/alloc/logs/.shiva-ci-TestNomad-Run-Fail-test-25-2704-task.stdout.fifo timestamp="2022-12-09T13:35:07.940+0300"
nomad[2668973]: 2022-12-09T13:35:07.940+0300 [INFO] client.alloc_runner.task_runner.task_hook.logmon.nomad: opening fifo: alloc_id=384708cc-5ca5-1e14-ca6b-7017045ee3c7 task=shiva-ci-TestNomad-Run-Fail-test-25-2704-task path=/var/lib/nomad/alloc/384708cc-5ca5-1e14-ca6b-7017045ee3c7/alloc/logs/.shiva-ci-TestNomad-Run-Fail-test-25-2704-task.stderr.fifo @module=logmon timestamp="2022-12-09T13:35:07.940+0300"
nomad[2668973]: 2022-12-09T13:35:07.946+0300 [DEBUG] client.driver_mgr.docker: binding directories: driver=docker task_name=shiva-ci-TestNomad-Run-Fail-test-25-2704-task binds="[]string{\"/var/lib/nomad/alloc/384708cc-5ca5-1e14-ca6b-7017045ee3c7/alloc:/alloc\", \"/var/lib/nomad/alloc/384708cc-5ca5-1e14-ca6b-7017045ee3c7/shiva-ci-TestNomad-Run-Fail-test-25-2704-task/local:/local\", \"/var/lib/nomad/alloc/384708cc-5ca5-1e14-ca6b-7017045ee3c7/shiva-ci-TestNomad-Run-Fail-test-25-2704-task/secrets:/secrets\", \"/etc/docker/resolv.conf:/etc/resolv.conf:ro\"}"
nomad[2668973]: 2022-12-09T13:35:07.946+0300 [DEBUG] client.driver_mgr.docker: applied labels on the container: driver=docker task_name=shiva-ci-TestNomad-Run-Fail-test-25-2704-task labels=map[com.hashicorp.nomad.alloc_id:384708cc-5ca5-1e14-ca6b-7017045ee3c7]
nomad[2668973]: 2022-12-09T13:35:07.946+0300 [DEBUG] client.driver_mgr.docker: setting container name: driver=docker task_name=shiva-ci-TestNomad-Run-Fail-test-25-2704-task container_name=shiva-ci-TestNomad-Run-Fail-test-25-2704-task-384708cc-5ca5-1e14-ca6b-7017045ee3c7
```
First Consul check logs for alloc_id=384708cc-5ca5-1e14-ca6b-7017045ee3c7:
```
consul[48541]: 2022-12-09T13:36:17.347+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.599+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.636+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.684+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.685+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.717+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.732+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.772+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.817+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.818+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.855+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.858+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.877+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.879+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.880+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.898+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.981+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.996+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:18.120+0300 [WARN] agent: Check is now critical: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
```
|
1.0
|
Nomad marks deployments as successful, before Consul checks are passed. - ### Nomad version and environment details
Nomad 1.1.2 -> 1.4.2
Consul 1.9.5
Ubuntu 20.04
### Environment configuration:
Servers: 3 nomad servers, consul servers (services register here) + consul servers with ACL.
Clients: we've installed nomad client and consul agent.
### Issue
After upgrading Nomad from 1.1.2 to 1.4.2 some deployments are marked as successful, despite that service has not yet been registered with Consul. This problem is reproduced when running several deployments at the same time.
### Reproduction steps
1. Make docker image of the service, which runs 3 seconds after starting and then fails.
2. Run several deployments via script - [nomad-reproducer.go.txt](https://github.com/hashicorp/nomad/files/10217111/nomad-reproducer.go.txt)
### Expected Behaviour
All deployments fail.
### Actual Behaviour
Few deployments are successful.
### Logs for one allocation for successful deployment
Nomad start to process deployment:
```
nomad[2668973]: 2022-12-09T13:34:35.361+0300 [DEBUG] client.alloc_runner.task_runner: lifecycle start condition has been met, proceeding: alloc_id=384708cc-5ca5-1e14-ca6b-7017045ee3c7 task=shiva-ci-TestNomad-Run-Fail-test-25-2704-task
nomad[2668973]: 2022-12-09T13:34:35.422+0300 [WARN] client.alloc_runner.task_runner.task_hook.logmon: plugin configured with a nil SecureConfig: alloc_id=384708cc-5ca5-1e14-ca6b-7017045ee3c7 task=shiva-ci-TestNomad-Run-Fail-test-25-2704-task
nomad[2668973]: 2022-12-09T13:34:35.422+0300 [DEBUG] client.alloc_runner.task_runner.task_hook.logmon: starting plugin: alloc_id=384708cc-5ca5-1e14-ca6b-7017045ee3c7 task=shiva-ci-TestNomad-Run-Fail-test-25-2704-task path=/usr/bin/nomad args=["/usr/bin/nomad", "logmon"]
nomad[2668973]: 2022-12-09T13:34:35.422+0300 [DEBUG] client.alloc_runner.task_runner.task_hook.logmon: plugin started: alloc_id=384708cc-5ca5-1e14-ca6b-7017045ee3c7 task=shiva-ci-TestNomad-Run-Fail-test-25-2704-task path=/usr/bin/nomad pid=1424417
nomad[2668973]: 2022-12-09T13:34:35.422+0300 [DEBUG] client.alloc_runner.task_runner.task_hook.logmon: waiting for RPC address: alloc_id=384708cc-5ca5-1e14-ca6b-7017045ee3c7 task=shiva-ci-TestNomad-Run-Fail-test-25-2704-task path=/usr/bin/nomad
nomad[2668973]: 2022-12-09T13:34:35.435+0300 [DEBUG] client.alloc_runner.task_runner.task_hook.logmon.nomad: plugin address: alloc_id=384708cc-5ca5-1e14-ca6b-7017045ee3c7 task=shiva-ci-TestNomad-Run-Fail-test-25-2704-task @module=logmon address=/tmp/plugin1614056546 network=unix timestamp="2022-12-09T13:34:35.435+0300"
nomad[2668973]: 2022-12-09T13:34:35.435+0300 [DEBUG] client.alloc_runner.task_runner.task_hook.logmon: using plugin: alloc_id=384708cc-5ca5-1e14-ca6b-7017045ee3c7 task=shiva-ci-TestNomad-Run-Fail-test-25-2704-task version=2
nomad[2668973]: 2022-12-09T13:34:35.442+0300 [INFO] client.alloc_runner.task_runner.task_hook.logmon.nomad: opening fifo: alloc_id=384708cc-5ca5-1e14-ca6b-7017045ee3c7 task=shiva-ci-TestNomad-Run-Fail-test-25-2704-task @module=logmon path=/var/lib/nomad/alloc/384708cc-5ca5-1e14-ca6b-7017045ee3c7/alloc/logs/.shiva-ci-TestNomad-Run-Fail-test-25-2704-task.stdout.fifo timestamp="2022-12-09T13:34:35.442+0300"
nomad[2668973]: 2022-12-09T13:34:35.443+0300 [INFO] client.alloc_runner.task_runner.task_hook.logmon.nomad: opening fifo: alloc_id=384708cc-5ca5-1e14-ca6b-7017045ee3c7 task=shiva-ci-TestNomad-Run-Fail-test-25-2704-task @module=logmon path=/var/lib/nomad/alloc/384708cc-5ca5-1e14-ca6b-7017045ee3c7/alloc/logs/.shiva-ci-TestNomad-Run-Fail-test-25-2704-task.stderr.fifo timestamp="2022-12-09T13:34:35.443+0300"
nomad[2668973]: 2022-12-09T13:34:35.534+0300 [DEBUG] client.driver_mgr.docker: binding directories: driver=docker task_name=shiva-ci-TestNomad-Run-Fail-test-25-2704-task binds="[]string{\"/var/lib/nomad/alloc/384708cc-5ca5-1e14-ca6b-7017045ee3c7/alloc:/alloc\", \"/var/lib/nomad/alloc/384708cc-5ca5-1e14-ca6b-7017045ee3c7/shiva-ci-TestNomad-Run-Fail-test-25-2704-task/local:/local\", \"/var/lib/nomad/alloc/384708cc-5ca5-1e14-ca6b-7017045ee3c7/shiva-ci-TestNomad-Run-Fail-test-25-2704-task/secrets:/secrets\", \"/etc/docker/resolv.conf:/etc/resolv.conf:ro\"}"
nomad[2668973]: 2022-12-09T13:34:35.535+0300 [DEBUG] client.driver_mgr.docker: applied labels on the container: driver=docker task_name=shiva-ci-TestNomad-Run-Fail-test-25-2704-task labels=map[com.hashicorp.nomad.alloc_id:384708cc-5ca5-1e14-ca6b-7017045ee3c7]
nomad[2668973]: 2022-12-09T13:34:35.535+0300 [DEBUG] client.driver_mgr.docker: setting container name: driver=docker task_name=shiva-ci-TestNomad-Run-Fail-test-25-2704-task container_name=shiva-ci-TestNomad-Run-Fail-test-25-2704-task-384708cc-5ca5-1e14-ca6b-7017045ee3c7
```
Dockerd start container:
```
dockerd[60232]: 2022-12-09T13:34:35.535621200+03:00 level=debug msg="Calling POST /containers/create?name=shiva-ci-TestNomad-Run-Fail-test-25-2704-task-384708cc-5ca5-1e14-ca6b-7017045ee3c7"
dockerd[60232]: 2022-12-09T13:34:51.808265565+03:00 level=debug msg="Assigning addresses for endpoint shiva-ci-TestNomad-Run-Fail-test-25-2704-task-384708cc-5ca5-1e14-ca6b-7017045ee3c7's interface on network vertis"
```
Container fail:
```
dockerd[60232]: 2022-12-09T13:34:57.848499016+03:00 level=debug msg="Revoking external connectivity on endpoint shiva-ci-TestNomad-Run-Fail-test-25-2704-task-384708cc-5ca5-1e14-ca6b-7017045ee3c7 (0469b6ae1bb562a08331195c330fb5fb05e231499861b4f5927ddc25020ef9cc)"
dockerd[60232]: 2022-12-09T13:35:03.354392690+03:00 level=debug msg="Releasing addresses for endpoint shiva-ci-TestNomad-Run-Fail-test-25-2704-task-384708cc-5ca5-1e14-ca6b-7017045ee3c7's interface on network vertis"
```
Nomad marks deployment as successful:
```
2022-12-09 13:35:06.120 Deployment Update for ID "cae9bf7e-d534-eab4-a963-7e68893d8474": Status "successful"; Description "Deployment completed successfully"
_PID=241887 _SYSTEMD_UNIT=nomad.service
```
Container restart due to restart policy:
```
nomad[2668973]: 2022-12-09T13:35:06.778+0300 [INFO] client.alloc_runner.task_runner: restarting task: alloc_id=384708cc-5ca5-1e14-ca6b-7017045ee3c7 task=shiva-ci-TestNomad-Run-Fail-test-25-2704-task reason="Restart within policy" delay=1.155116655s
nomad[2668973]: 2022-12-09T13:35:07.938+0300 [DEBUG] client.alloc_runner.task_runner: lifecycle start condition has been met, proceeding: alloc_id=384708cc-5ca5-1e14-ca6b-7017045ee3c7 task=shiva-ci-TestNomad-Run-Fail-test-25-2704-task
nomad[2668973]: 2022-12-09T13:35:07.940+0300 [INFO] client.alloc_runner.task_runner.task_hook.logmon.nomad: opening fifo: alloc_id=384708cc-5ca5-1e14-ca6b-7017045ee3c7 task=shiva-ci-TestNomad-Run-Fail-test-25-2704-task @module=logmon path=/var/lib/nomad/alloc/384708cc-5ca5-1e14-ca6b-7017045ee3c7/alloc/logs/.shiva-ci-TestNomad-Run-Fail-test-25-2704-task.stdout.fifo timestamp="2022-12-09T13:35:07.940+0300"
nomad[2668973]: 2022-12-09T13:35:07.940+0300 [INFO] client.alloc_runner.task_runner.task_hook.logmon.nomad: opening fifo: alloc_id=384708cc-5ca5-1e14-ca6b-7017045ee3c7 task=shiva-ci-TestNomad-Run-Fail-test-25-2704-task path=/var/lib/nomad/alloc/384708cc-5ca5-1e14-ca6b-7017045ee3c7/alloc/logs/.shiva-ci-TestNomad-Run-Fail-test-25-2704-task.stderr.fifo @module=logmon timestamp="2022-12-09T13:35:07.940+0300"
nomad[2668973]: 2022-12-09T13:35:07.946+0300 [DEBUG] client.driver_mgr.docker: binding directories: driver=docker task_name=shiva-ci-TestNomad-Run-Fail-test-25-2704-task binds="[]string{\"/var/lib/nomad/alloc/384708cc-5ca5-1e14-ca6b-7017045ee3c7/alloc:/alloc\", \"/var/lib/nomad/alloc/384708cc-5ca5-1e14-ca6b-7017045ee3c7/shiva-ci-TestNomad-Run-Fail-test-25-2704-task/local:/local\", \"/var/lib/nomad/alloc/384708cc-5ca5-1e14-ca6b-7017045ee3c7/shiva-ci-TestNomad-Run-Fail-test-25-2704-task/secrets:/secrets\", \"/etc/docker/resolv.conf:/etc/resolv.conf:ro\"}"
nomad[2668973]: 2022-12-09T13:35:07.946+0300 [DEBUG] client.driver_mgr.docker: applied labels on the container: driver=docker task_name=shiva-ci-TestNomad-Run-Fail-test-25-2704-task labels=map[com.hashicorp.nomad.alloc_id:384708cc-5ca5-1e14-ca6b-7017045ee3c7]
nomad[2668973]: 2022-12-09T13:35:07.946+0300 [DEBUG] client.driver_mgr.docker: setting container name: driver=docker task_name=shiva-ci-TestNomad-Run-Fail-test-25-2704-task container_name=shiva-ci-TestNomad-Run-Fail-test-25-2704-task-384708cc-5ca5-1e14-ca6b-7017045ee3c7
```
First Consul check logs for alloc_id=384708cc-5ca5-1e14-ca6b-7017045ee3c7:
```
consul[48541]: 2022-12-09T13:36:17.347+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.599+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.636+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.684+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.685+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.717+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.732+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.772+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.817+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.818+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.855+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.858+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.877+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.879+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.880+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.898+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.981+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:17.996+0300 [DEBUG] agent: Check in sync: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
consul[48541]: 2022-12-09T13:36:18.120+0300 [WARN] agent: Check is now critical: check=_nomad-check-a73262881d59e860d85f2ba206bc9adbd8c3d3eb
```
|
non_process
|
nomad marks deployments as successful before consul checks are passed nomad version and environment details nomad consul ubuntu environment configuration servers nomad servers consul servers services register here consul servers with acl clients we ve installed nomad client and consul agent issue after upgrading nomad from to some deployments are marked as successful despite that service has not yet been registered with consul this problem is reproduced when running several deployments at the same time reproduction steps make docker image of the service which runs seconds after starting and then fails run several deployments via script expected behaviour all deployments fail actual behaviour few deployments are successful logs for one allocation for successful deployment nomad start to process deployment nomad client alloc runner task runner lifecycle start condition has been met proceeding alloc id task shiva ci testnomad run fail test task nomad client alloc runner task runner task hook logmon plugin configured with a nil secureconfig alloc id task shiva ci testnomad run fail test task nomad client alloc runner task runner task hook logmon starting plugin alloc id task shiva ci testnomad run fail test task path usr bin nomad args nomad client alloc runner task runner task hook logmon plugin started alloc id task shiva ci testnomad run fail test task path usr bin nomad pid nomad client alloc runner task runner task hook logmon waiting for rpc address alloc id task shiva ci testnomad run fail test task path usr bin nomad nomad client alloc runner task runner task hook logmon nomad plugin address alloc id task shiva ci testnomad run fail test task module logmon address tmp network unix timestamp nomad client alloc runner task runner task hook logmon using plugin alloc id task shiva ci testnomad run fail test task version nomad client alloc runner task runner task hook logmon nomad opening fifo alloc id task shiva ci testnomad run fail test task module logmon path var lib nomad alloc alloc logs shiva ci testnomad run fail test task stdout fifo timestamp nomad client alloc runner task runner task hook logmon nomad opening fifo alloc id task shiva ci testnomad run fail test task module logmon path var lib nomad alloc alloc logs shiva ci testnomad run fail test task stderr fifo timestamp nomad client driver mgr docker binding directories driver docker task name shiva ci testnomad run fail test task binds string var lib nomad alloc alloc alloc var lib nomad alloc shiva ci testnomad run fail test task local local var lib nomad alloc shiva ci testnomad run fail test task secrets secrets etc docker resolv conf etc resolv conf ro nomad client driver mgr docker applied labels on the container driver docker task name shiva ci testnomad run fail test task labels map nomad client driver mgr docker setting container name driver docker task name shiva ci testnomad run fail test task container name shiva ci testnomad run fail test task dockerd start container dockerd level debug msg calling post containers create name shiva ci testnomad run fail test task dockerd level debug msg assigning addresses for endpoint shiva ci testnomad run fail test task s interface on network vertis container fail dockerd level debug msg revoking external connectivity on endpoint shiva ci testnomad run fail test task dockerd level debug msg releasing addresses for endpoint shiva ci testnomad run fail test task s interface on network vertis nomad marks deployment as successful deployment update for id status successful description deployment completed successfully pid systemd unit nomad service container restart due to restart policy nomad client alloc runner task runner restarting task alloc id task shiva ci testnomad run fail test task reason restart within policy delay nomad client alloc runner task runner lifecycle start condition has been met proceeding alloc id task shiva ci testnomad run fail test task nomad client alloc runner task runner task hook logmon nomad opening fifo alloc id task shiva ci testnomad run fail test task module logmon path var lib nomad alloc alloc logs shiva ci testnomad run fail test task stdout fifo timestamp nomad client alloc runner task runner task hook logmon nomad opening fifo alloc id task shiva ci testnomad run fail test task path var lib nomad alloc alloc logs shiva ci testnomad run fail test task stderr fifo module logmon timestamp nomad client driver mgr docker binding directories driver docker task name shiva ci testnomad run fail test task binds string var lib nomad alloc alloc alloc var lib nomad alloc shiva ci testnomad run fail test task local local var lib nomad alloc shiva ci testnomad run fail test task secrets secrets etc docker resolv conf etc resolv conf ro nomad client driver mgr docker applied labels on the container driver docker task name shiva ci testnomad run fail test task labels map nomad client driver mgr docker setting container name driver docker task name shiva ci testnomad run fail test task container name shiva ci testnomad run fail test task first consul check logs for alloc id consul agent check in sync check nomad check consul agent check in sync check nomad check consul agent check in sync check nomad check consul agent check in sync check nomad check consul agent check in sync check nomad check consul agent check in sync check nomad check consul agent check in sync check nomad check consul agent check in sync check nomad check consul agent check in sync check nomad check consul agent check in sync check nomad check consul agent check in sync check nomad check consul agent check in sync check nomad check consul agent check in sync check nomad check consul agent check in sync check nomad check consul agent check in sync check nomad check consul agent check in sync check nomad check consul agent check in sync check nomad check consul agent check in sync check nomad check consul agent check is now critical check nomad check
| 0
|
335,754
| 30,084,793,300
|
IssuesEvent
|
2023-06-29 07:49:00
|
proarc/proarc-client
|
https://api.github.com/repos/proarc/proarc-client
|
closed
|
Exporty v klientovi - timeout
|
1 chyba 7 návrh na zavření 6 lokální test
|
@SykoraLukas Navazuji na náš rozhovor a raději zakládám issue - prosíme o radu. Děkuji.
Při exportu objektu pro Krameria s volbou instance "local" dochází někdy (zřejmě u větších souborů) k chybě (viz obrázek), export je ale dokončen a ve správě procesů chyba není v logu. Log operace stažený ze serveru v příloze. @PetrKotynek
[chyba_exportu_8_3_400dev.txt](https://github.com/proarc/proarc-client/files/10921008/chyba_exportu_8_3_400dev.txt)
|
1.0
|
Exporty v klientovi - timeout - @SykoraLukas Navazuji na náš rozhovor a raději zakládám issue - prosíme o radu. Děkuji.
Při exportu objektu pro Krameria s volbou instance "local" dochází někdy (zřejmě u větších souborů) k chybě (viz obrázek), export je ale dokončen a ve správě procesů chyba není v logu. Log operace stažený ze serveru v příloze. @PetrKotynek
[chyba_exportu_8_3_400dev.txt](https://github.com/proarc/proarc-client/files/10921008/chyba_exportu_8_3_400dev.txt)
|
non_process
|
exporty v klientovi timeout sykoralukas navazuji na náš rozhovor a raději zakládám issue prosíme o radu děkuji při exportu objektu pro krameria s volbou instance local dochází někdy zřejmě u větších souborů k chybě viz obrázek export je ale dokončen a ve správě procesů chyba není v logu log operace stažený ze serveru v příloze petrkotynek
| 0
|
286,676
| 31,719,618,105
|
IssuesEvent
|
2023-09-10 08:54:46
|
Mend-developer-platform-load/Stacey-Hamilton
|
https://api.github.com/repos/Mend-developer-platform-load/Stacey-Hamilton
|
closed
|
mime-1.3.4.tgz: 1 vulnerabilities (highest severity is: 7.5) - autoclosed
|
Mend: dependency security vulnerability
|
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>mime-1.3.4.tgz</b></p></summary>
<p>A comprehensive library for mime-type mapping</p>
<p>Library home page: <a href="https://registry.npmjs.org/mime/-/mime-1.3.4.tgz">https://registry.npmjs.org/mime/-/mime-1.3.4.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/mime/package.json</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/Stacey-Hamilton/commit/dad25d8c95047fda9182846fe4143606b5601dee">dad25d8c95047fda9182846fe4143606b5601dee</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (mime version) | Remediation Possible** |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2017-16138](https://www.mend.io/vulnerability-database/CVE-2017-16138) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | mime-1.3.4.tgz | Direct | 1.4.1 | ✅ |
<p>**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation</p>
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2017-16138</summary>
### Vulnerable Library - <b>mime-1.3.4.tgz</b></p>
<p>A comprehensive library for mime-type mapping</p>
<p>Library home page: <a href="https://registry.npmjs.org/mime/-/mime-1.3.4.tgz">https://registry.npmjs.org/mime/-/mime-1.3.4.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/mime/package.json</p>
<p>
Dependency Hierarchy:
- :x: **mime-1.3.4.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/Stacey-Hamilton/commit/dad25d8c95047fda9182846fe4143606b5601dee">dad25d8c95047fda9182846fe4143606b5601dee</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The mime module < 1.4.1, 2.0.1, 2.0.2 is vulnerable to regular expression denial of service when a mime lookup is performed on untrusted user input.
Mend Note: Converted from WS-2017-0330, on 2022-11-08.
<p>Publish Date: 2018-06-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-16138>CVE-2017-16138</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16138">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16138</a></p>
<p>Release Date: 2018-06-07</p>
<p>Fix Resolution: 1.4.1</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
</details>
***
<p>:rescue_worker_helmet:Automatic Remediation will be attempted for this issue.</p>
|
True
|
mime-1.3.4.tgz: 1 vulnerabilities (highest severity is: 7.5) - autoclosed - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>mime-1.3.4.tgz</b></p></summary>
<p>A comprehensive library for mime-type mapping</p>
<p>Library home page: <a href="https://registry.npmjs.org/mime/-/mime-1.3.4.tgz">https://registry.npmjs.org/mime/-/mime-1.3.4.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/mime/package.json</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/Stacey-Hamilton/commit/dad25d8c95047fda9182846fe4143606b5601dee">dad25d8c95047fda9182846fe4143606b5601dee</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (mime version) | Remediation Possible** |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2017-16138](https://www.mend.io/vulnerability-database/CVE-2017-16138) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | mime-1.3.4.tgz | Direct | 1.4.1 | ✅ |
<p>**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation</p>
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2017-16138</summary>
### Vulnerable Library - <b>mime-1.3.4.tgz</b></p>
<p>A comprehensive library for mime-type mapping</p>
<p>Library home page: <a href="https://registry.npmjs.org/mime/-/mime-1.3.4.tgz">https://registry.npmjs.org/mime/-/mime-1.3.4.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/mime/package.json</p>
<p>
Dependency Hierarchy:
- :x: **mime-1.3.4.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/Stacey-Hamilton/commit/dad25d8c95047fda9182846fe4143606b5601dee">dad25d8c95047fda9182846fe4143606b5601dee</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The mime module < 1.4.1, 2.0.1, 2.0.2 is vulnerable to regular expression denial of service when a mime lookup is performed on untrusted user input.
Mend Note: Converted from WS-2017-0330, on 2022-11-08.
<p>Publish Date: 2018-06-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-16138>CVE-2017-16138</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16138">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16138</a></p>
<p>Release Date: 2018-06-07</p>
<p>Fix Resolution: 1.4.1</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
</details>
***
<p>:rescue_worker_helmet:Automatic Remediation will be attempted for this issue.</p>
|
non_process
|
mime tgz vulnerabilities highest severity is autoclosed vulnerable library mime tgz a comprehensive library for mime type mapping library home page a href path to dependency file package json path to vulnerable library node modules mime package json found in head commit a href vulnerabilities cve severity cvss dependency type fixed in mime version remediation possible high mime tgz direct in some cases remediation pr cannot be created automatically for a vulnerability despite the availability of remediation details cve vulnerable library mime tgz a comprehensive library for mime type mapping library home page a href path to dependency file package json path to vulnerable library node modules mime package json dependency hierarchy x mime tgz vulnerable library found in head commit a href found in base branch main vulnerability details the mime module is vulnerable to regular expression denial of service when a mime lookup is performed on untrusted user input mend note converted from ws on 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 rescue worker helmet automatic remediation will be attempted for this issue rescue worker helmet automatic remediation will be attempted for this issue
| 0
|
1,035
| 3,491,895,220
|
IssuesEvent
|
2016-01-04 17:43:11
|
kerubistan/kerub
|
https://api.github.com/repos/kerubistan/kerub
|
opened
|
advanced operational risk analysis
|
component:data processing enhancement priority: normal
|
the "what if"'s
With milestone 0.1 the planner considers risks created by the operational state of the system.
The planner should consider the possible events. E.g.
* if the host X goes down
* if the storage fails
* if power failure hits
what expectation will be broken and for how long
|
1.0
|
advanced operational risk analysis - the "what if"'s
With milestone 0.1 the planner considers risks created by the operational state of the system.
The planner should consider the possible events. E.g.
* if the host X goes down
* if the storage fails
* if power failure hits
what expectation will be broken and for how long
|
process
|
advanced operational risk analysis the what if s with milestone the planner considers risks created by the operational state of the system the planner should consider the possible events e g if the host x goes down if the storage fails if power failure hits what expectation will be broken and for how long
| 1
|
105,002
| 16,623,613,355
|
IssuesEvent
|
2021-06-03 06:44:26
|
Thanraj/OpenSSL_1.0.1
|
https://api.github.com/repos/Thanraj/OpenSSL_1.0.1
|
opened
|
CVE-2015-0286 (Medium) detected in opensslOpenSSL_1_0_1
|
security vulnerability
|
## CVE-2015-0286 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>opensslOpenSSL_1_0_1</b></p></summary>
<p>
<p>Akamai fork of openssl master.</p>
<p>Library home page: <a href=https://github.com/akamai/openssl.git>https://github.com/akamai/openssl.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Thanraj/OpenSSL_1.0.1/commit/f1fe40536a9d3c961cc1415e9dd6d4fd002b61dc">f1fe40536a9d3c961cc1415e9dd6d4fd002b61dc</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 (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>OpenSSL_1.0.1/crypto/asn1/a_type.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>OpenSSL_1.0.1/crypto/asn1/a_type.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The ASN1_TYPE_cmp function in crypto/asn1/a_type.c in OpenSSL before 0.9.8zf, 1.0.0 before 1.0.0r, 1.0.1 before 1.0.1m, and 1.0.2 before 1.0.2a does not properly perform boolean-type comparisons, which allows remote attackers to cause a denial of service (invalid read operation and application crash) via a crafted X.509 certificate to an endpoint that uses the certificate-verification feature.
<p>Publish Date: 2015-03-19
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-0286>CVE-2015-0286</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2015-0286">https://nvd.nist.gov/vuln/detail/CVE-2015-0286</a></p>
<p>Release Date: 2015-03-19</p>
<p>Fix Resolution: 0.9.8zf,1.0.0r,1.0.1m,1.0.2a</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-2015-0286 (Medium) detected in opensslOpenSSL_1_0_1 - ## CVE-2015-0286 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>opensslOpenSSL_1_0_1</b></p></summary>
<p>
<p>Akamai fork of openssl master.</p>
<p>Library home page: <a href=https://github.com/akamai/openssl.git>https://github.com/akamai/openssl.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Thanraj/OpenSSL_1.0.1/commit/f1fe40536a9d3c961cc1415e9dd6d4fd002b61dc">f1fe40536a9d3c961cc1415e9dd6d4fd002b61dc</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 (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>OpenSSL_1.0.1/crypto/asn1/a_type.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>OpenSSL_1.0.1/crypto/asn1/a_type.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The ASN1_TYPE_cmp function in crypto/asn1/a_type.c in OpenSSL before 0.9.8zf, 1.0.0 before 1.0.0r, 1.0.1 before 1.0.1m, and 1.0.2 before 1.0.2a does not properly perform boolean-type comparisons, which allows remote attackers to cause a denial of service (invalid read operation and application crash) via a crafted X.509 certificate to an endpoint that uses the certificate-verification feature.
<p>Publish Date: 2015-03-19
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-0286>CVE-2015-0286</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2015-0286">https://nvd.nist.gov/vuln/detail/CVE-2015-0286</a></p>
<p>Release Date: 2015-03-19</p>
<p>Fix Resolution: 0.9.8zf,1.0.0r,1.0.1m,1.0.2a</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_process
|
cve medium detected in opensslopenssl cve medium severity vulnerability vulnerable library opensslopenssl akamai fork of openssl master library home page a href found in head commit a href found in base branch master vulnerable source files openssl crypto a type c openssl crypto a type c vulnerability details the type cmp function in crypto a type c in openssl before before before and before does not properly perform boolean type comparisons which allows remote attackers to cause a denial of service invalid read operation and application crash via a crafted x certificate to an endpoint that uses the certificate verification feature publish date url a href cvss score details base score metrics not available suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource
| 0
|
1,950
| 4,773,483,941
|
IssuesEvent
|
2016-10-27 00:52:55
|
yhtgrace/echo
|
https://api.github.com/repos/yhtgrace/echo
|
opened
|
Build echo features table
|
preprocessing
|
For each patient, features of interest for filtering and stratification/modeling:
* Inpatient/outpatient echo features
* ICU echo features
* Time relative to ICU admission
* ICU sepsis at time of echo
* Which drugs (pressors/inotropes) was the patient given
* Amount of fluids patient was given
* Age at time of echo
* Comorbidities: obesity, alchohol abuse
* On mechanical ventilation during echo, what type
* Labs: creatinine, troponin, lactate, etc. (see labs of interest) [time of echo, at 24, 48, ... hours]
* Renal function, on dialysis, etc.
|
1.0
|
Build echo features table - For each patient, features of interest for filtering and stratification/modeling:
* Inpatient/outpatient echo features
* ICU echo features
* Time relative to ICU admission
* ICU sepsis at time of echo
* Which drugs (pressors/inotropes) was the patient given
* Amount of fluids patient was given
* Age at time of echo
* Comorbidities: obesity, alchohol abuse
* On mechanical ventilation during echo, what type
* Labs: creatinine, troponin, lactate, etc. (see labs of interest) [time of echo, at 24, 48, ... hours]
* Renal function, on dialysis, etc.
|
process
|
build echo features table for each patient features of interest for filtering and stratification modeling inpatient outpatient echo features icu echo features time relative to icu admission icu sepsis at time of echo which drugs pressors inotropes was the patient given amount of fluids patient was given age at time of echo comorbidities obesity alchohol abuse on mechanical ventilation during echo what type labs creatinine troponin lactate etc see labs of interest renal function on dialysis etc
| 1
|
818,001
| 30,666,909,995
|
IssuesEvent
|
2023-07-25 19:01:13
|
cytoscape/enrichment-map-webapp
|
https://api.github.com/repos/cytoscape/enrichment-map-webapp
|
closed
|
Tooltip for intersection icon should be on the entire line
|
medium priority
|
**Description of new feature**
- The tooltip target for the intersection icon should be on the entire line, rather than just the icon.
- It's currently only on the icon itself, so it's hard to find.
**Motivation for new feature**
- People try to hover over the word 'genes' and get nothing.
- #164
|
1.0
|
Tooltip for intersection icon should be on the entire line - **Description of new feature**
- The tooltip target for the intersection icon should be on the entire line, rather than just the icon.
- It's currently only on the icon itself, so it's hard to find.
**Motivation for new feature**
- People try to hover over the word 'genes' and get nothing.
- #164
|
non_process
|
tooltip for intersection icon should be on the entire line description of new feature the tooltip target for the intersection icon should be on the entire line rather than just the icon it s currently only on the icon itself so it s hard to find motivation for new feature people try to hover over the word genes and get nothing
| 0
|
20,572
| 27,232,433,477
|
IssuesEvent
|
2023-02-21 14:11:22
|
oyvindln/vhs-decode
|
https://api.github.com/repos/oyvindln/vhs-decode
|
opened
|
HiFi Decode Development & Improvements
|
in-process Audio
|
Currently, HiFi decode is fully working but needs improvements that have already been discussed since it is now merged I'll create this issue here for reference.
## Documentation
- [x] CX Card & DdD Usage
- [ ] RTLSDR Usage
## Input RF Support
- [x] CXADC Modes
- [x] 16-bit Signed (DdD)
- [ ] 10-bit Packed (DdD)
- [ ] IQ files (RTLSDR)
## Output Codec
- [x] FLAC
- [ ] PCM
## Output Sample Rate
- [x] 192khz
- [ ] 96khz
- [ ] 48khz
## Output Bit Depth
- [x] 24-bit (Interger)
- [ ] 16-bit (Interger)
- [ ] 32-bit (Interger)
- [ ] 32-bit (float)
## Utility Modes
- [x] Live Output
- [x] GNU Radio Passthrough
- [ ] Demodulation Live Graph
## Format Support
- [x] (S)VHS
- [ ] BetaMax
- [x] Sony 8mm (Video8/High8)
- [ ] PCM Tapes
|
1.0
|
HiFi Decode Development & Improvements - Currently, HiFi decode is fully working but needs improvements that have already been discussed since it is now merged I'll create this issue here for reference.
## Documentation
- [x] CX Card & DdD Usage
- [ ] RTLSDR Usage
## Input RF Support
- [x] CXADC Modes
- [x] 16-bit Signed (DdD)
- [ ] 10-bit Packed (DdD)
- [ ] IQ files (RTLSDR)
## Output Codec
- [x] FLAC
- [ ] PCM
## Output Sample Rate
- [x] 192khz
- [ ] 96khz
- [ ] 48khz
## Output Bit Depth
- [x] 24-bit (Interger)
- [ ] 16-bit (Interger)
- [ ] 32-bit (Interger)
- [ ] 32-bit (float)
## Utility Modes
- [x] Live Output
- [x] GNU Radio Passthrough
- [ ] Demodulation Live Graph
## Format Support
- [x] (S)VHS
- [ ] BetaMax
- [x] Sony 8mm (Video8/High8)
- [ ] PCM Tapes
|
process
|
hifi decode development improvements currently hifi decode is fully working but needs improvements that have already been discussed since it is now merged i ll create this issue here for reference documentation cx card ddd usage rtlsdr usage input rf support cxadc modes bit signed ddd bit packed ddd iq files rtlsdr output codec flac pcm output sample rate output bit depth bit interger bit interger bit interger bit float utility modes live output gnu radio passthrough demodulation live graph format support s vhs betamax sony pcm tapes
| 1
|
13,087
| 15,435,310,818
|
IssuesEvent
|
2021-03-07 08:15:37
|
shirou/gopsutil
|
https://api.github.com/repos/shirou/gopsutil
|
closed
|
OpenProcess fails with PROCESS_QUERY_LIMITED_INFORMATION on Windows XP
|
os:windows package:process
|
Creating this issue to reference this behavior on Windows XP, quoting myself from https://github.com/shirou/gopsutil/pull/713#issue-295118285
> Regarding WinXP, this is failing because of PROCESS_QUERY_LIMITED_INFORMATION being introduced in Vista. Calling `windows.OpenProcess` with `windows.PROCESS_QUERY_INFORMATION` works properly on WinXP (hinting that every calls to OpenProcess with PROCESS_QUERY_LIMITED_INFORMATION in gopsutil fail on WinXP). Handling this (opening process with right parameter according to Windows version) would complicate a little bit the code in process_window.go (while being prudent not too slow down gopsutil functions), I'm not sure if we should bother so much about WinXP now that it's deprecated for quite a few years.
I think it would be nice to keep compatibility with WinXP, but with a low priority (we didn't even have report from users that these calls to OpenProcess are broken on XP), I will probably implement something in the future if nobody else does.
|
1.0
|
OpenProcess fails with PROCESS_QUERY_LIMITED_INFORMATION on Windows XP - Creating this issue to reference this behavior on Windows XP, quoting myself from https://github.com/shirou/gopsutil/pull/713#issue-295118285
> Regarding WinXP, this is failing because of PROCESS_QUERY_LIMITED_INFORMATION being introduced in Vista. Calling `windows.OpenProcess` with `windows.PROCESS_QUERY_INFORMATION` works properly on WinXP (hinting that every calls to OpenProcess with PROCESS_QUERY_LIMITED_INFORMATION in gopsutil fail on WinXP). Handling this (opening process with right parameter according to Windows version) would complicate a little bit the code in process_window.go (while being prudent not too slow down gopsutil functions), I'm not sure if we should bother so much about WinXP now that it's deprecated for quite a few years.
I think it would be nice to keep compatibility with WinXP, but with a low priority (we didn't even have report from users that these calls to OpenProcess are broken on XP), I will probably implement something in the future if nobody else does.
|
process
|
openprocess fails with process query limited information on windows xp creating this issue to reference this behavior on windows xp quoting myself from regarding winxp this is failing because of process query limited information being introduced in vista calling windows openprocess with windows process query information works properly on winxp hinting that every calls to openprocess with process query limited information in gopsutil fail on winxp handling this opening process with right parameter according to windows version would complicate a little bit the code in process window go while being prudent not too slow down gopsutil functions i m not sure if we should bother so much about winxp now that it s deprecated for quite a few years i think it would be nice to keep compatibility with winxp but with a low priority we didn t even have report from users that these calls to openprocess are broken on xp i will probably implement something in the future if nobody else does
| 1
|
3,571
| 6,613,208,809
|
IssuesEvent
|
2017-09-20 08:23:38
|
inasafe/inasafe-realtime
|
https://api.github.com/repos/inasafe/inasafe-realtime
|
closed
|
Share InaSAFE realtime earthquake impact map with BMKG
|
earthquake feature request ready realtime processor
|
BMKG has requested that InaSAFE realtime also return the impact map to them
Proposed solution
make it happen
See original ticket at https://github.com/inasafe/inasafe/issues/2986 for further discussion.
|
1.0
|
Share InaSAFE realtime earthquake impact map with BMKG - BMKG has requested that InaSAFE realtime also return the impact map to them
Proposed solution
make it happen
See original ticket at https://github.com/inasafe/inasafe/issues/2986 for further discussion.
|
process
|
share inasafe realtime earthquake impact map with bmkg bmkg has requested that inasafe realtime also return the impact map to them proposed solution make it happen see original ticket at for further discussion
| 1
|
7,038
| 10,197,178,414
|
IssuesEvent
|
2019-08-12 23:11:36
|
metabase/metabase
|
https://api.github.com/repos/metabase/metabase
|
closed
|
Grouping by "year" results in numeric years instead of timestamps
|
Query Processor Timezones/Calendars
|
All other date grouping granularities return a timestamp (e.x. `2016-02-23T00:00:27.126Z`) except for "year" which returns a number (e.x. `2016`). For consistency we should always return a timestamp.
This is currently manifesting itself in the `multiseries_charts_v1` branch as all "year" grouped times being parsed as date within a couple seconds of the unix epoch...
|
1.0
|
Grouping by "year" results in numeric years instead of timestamps - All other date grouping granularities return a timestamp (e.x. `2016-02-23T00:00:27.126Z`) except for "year" which returns a number (e.x. `2016`). For consistency we should always return a timestamp.
This is currently manifesting itself in the `multiseries_charts_v1` branch as all "year" grouped times being parsed as date within a couple seconds of the unix epoch...
|
process
|
grouping by year results in numeric years instead of timestamps all other date grouping granularities return a timestamp e x except for year which returns a number e x for consistency we should always return a timestamp this is currently manifesting itself in the multiseries charts branch as all year grouped times being parsed as date within a couple seconds of the unix epoch
| 1
|
82,584
| 15,648,359,139
|
IssuesEvent
|
2021-03-23 05:33:40
|
YJSoft/namuhub
|
https://api.github.com/repos/YJSoft/namuhub
|
closed
|
CVE-2019-16792 (High) detected in waitress-0.8.9.tar.gz - autoclosed
|
security vulnerability
|
## CVE-2019-16792 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>waitress-0.8.9.tar.gz</b></p></summary>
<p>Waitress WSGI server</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/ee/65/fc9dee74a909a1187ca51e4f15ad9c4d35476e4ab5813f73421505c48053/waitress-0.8.9.tar.gz">https://files.pythonhosted.org/packages/ee/65/fc9dee74a909a1187ca51e4f15ad9c4d35476e4ab5813f73421505c48053/waitress-0.8.9.tar.gz</a></p>
<p>Path to dependency file: namuhub/requirements.txt</p>
<p>Path to vulnerable library: namuhub/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **waitress-0.8.9.tar.gz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/YJSoft/namuhub/commit/3e2e58c112b34d9d89ec2ec01b44226ffaaf7d87">3e2e58c112b34d9d89ec2ec01b44226ffaaf7d87</a></p>
<p>Found in base branch: <b>develop</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>
Waitress through version 1.3.1 allows request smuggling by sending the Content-Length header twice. Waitress would header fold a double Content-Length header and due to being unable to cast the now comma separated value to an integer would set the Content-Length to 0 internally. If two Content-Length headers are sent in a single request, Waitress would treat the request as having no body, thereby treating the body of the request as a new request in HTTP pipelining. This issue is fixed in Waitress 1.4.0.
<p>Publish Date: 2020-01-22
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-16792>CVE-2019-16792</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16792">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16792</a></p>
<p>Release Date: 2020-01-22</p>
<p>Fix Resolution: 1.4.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2019-16792 (High) detected in waitress-0.8.9.tar.gz - autoclosed - ## CVE-2019-16792 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>waitress-0.8.9.tar.gz</b></p></summary>
<p>Waitress WSGI server</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/ee/65/fc9dee74a909a1187ca51e4f15ad9c4d35476e4ab5813f73421505c48053/waitress-0.8.9.tar.gz">https://files.pythonhosted.org/packages/ee/65/fc9dee74a909a1187ca51e4f15ad9c4d35476e4ab5813f73421505c48053/waitress-0.8.9.tar.gz</a></p>
<p>Path to dependency file: namuhub/requirements.txt</p>
<p>Path to vulnerable library: namuhub/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **waitress-0.8.9.tar.gz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/YJSoft/namuhub/commit/3e2e58c112b34d9d89ec2ec01b44226ffaaf7d87">3e2e58c112b34d9d89ec2ec01b44226ffaaf7d87</a></p>
<p>Found in base branch: <b>develop</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>
Waitress through version 1.3.1 allows request smuggling by sending the Content-Length header twice. Waitress would header fold a double Content-Length header and due to being unable to cast the now comma separated value to an integer would set the Content-Length to 0 internally. If two Content-Length headers are sent in a single request, Waitress would treat the request as having no body, thereby treating the body of the request as a new request in HTTP pipelining. This issue is fixed in Waitress 1.4.0.
<p>Publish Date: 2020-01-22
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-16792>CVE-2019-16792</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16792">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16792</a></p>
<p>Release Date: 2020-01-22</p>
<p>Fix Resolution: 1.4.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_process
|
cve high detected in waitress tar gz autoclosed cve high severity vulnerability vulnerable library waitress tar gz waitress wsgi server library home page a href path to dependency file namuhub requirements txt path to vulnerable library namuhub requirements txt dependency hierarchy x waitress tar gz vulnerable library found in head commit a href found in base branch develop vulnerability details waitress through version allows request smuggling by sending the content length header twice waitress would header fold a double content length header and due to being unable to cast the now comma separated value to an integer would set the content length to internally if two content length headers are sent in a single request waitress would treat the request as having no body thereby treating the body of the request as a new request in http pipelining this issue is fixed in waitress publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource
| 0
|
21,340
| 29,086,236,450
|
IssuesEvent
|
2023-05-16 00:16:38
|
darktable-org/darktable
|
https://api.github.com/repos/darktable-org/darktable
|
closed
|
Multi-resolution export
|
feature: enhancement scope: image processing no-issue-activity
|
When you need the same image at different resolutions, as of now, you need to manually re-export the image at each resolution, meaning recomputing a full pipeline for each resolution.
It would me more efficient to compute only the max resolution or full resolution pipeline (depending on settings), then downsample for each of the smaller resolutions from the same high-res image buffer.
|
1.0
|
Multi-resolution export - When you need the same image at different resolutions, as of now, you need to manually re-export the image at each resolution, meaning recomputing a full pipeline for each resolution.
It would me more efficient to compute only the max resolution or full resolution pipeline (depending on settings), then downsample for each of the smaller resolutions from the same high-res image buffer.
|
process
|
multi resolution export when you need the same image at different resolutions as of now you need to manually re export the image at each resolution meaning recomputing a full pipeline for each resolution it would me more efficient to compute only the max resolution or full resolution pipeline depending on settings then downsample for each of the smaller resolutions from the same high res image buffer
| 1
|
625,649
| 19,759,902,417
|
IssuesEvent
|
2022-01-16 08:23:12
|
dahaeng/dahaeng-android
|
https://api.github.com/repos/dahaeng/dahaeng-android
|
closed
|
스플래시 화면
|
bug enhancement high-priority
|
- 안드로이드12 대응해서 만들어야 함
- 커뮤니티 포스트들 미리 로드 해야 함
---
### 알려진 문제
- 에뮬레이터에서는 작동하지 않음
- 실기기에서는 잘 작동하는거 확인
|
1.0
|
스플래시 화면 - - 안드로이드12 대응해서 만들어야 함
- 커뮤니티 포스트들 미리 로드 해야 함
---
### 알려진 문제
- 에뮬레이터에서는 작동하지 않음
- 실기기에서는 잘 작동하는거 확인
|
non_process
|
스플래시 화면 대응해서 만들어야 함 커뮤니티 포스트들 미리 로드 해야 함 알려진 문제 에뮬레이터에서는 작동하지 않음 실기기에서는 잘 작동하는거 확인
| 0
|
244,823
| 18,767,525,517
|
IssuesEvent
|
2021-11-06 07:14:52
|
ProjectSOTAS/documents
|
https://api.github.com/repos/ProjectSOTAS/documents
|
opened
|
Update how we score each other method
|
documentation
|
Update how we score each other method to make it more detailed and understandable.
|
1.0
|
Update how we score each other method - Update how we score each other method to make it more detailed and understandable.
|
non_process
|
update how we score each other method update how we score each other method to make it more detailed and understandable
| 0
|
345,160
| 10,354,098,045
|
IssuesEvent
|
2019-09-05 13:05:49
|
AbsaOSS/enceladus
|
https://api.github.com/repos/AbsaOSS/enceladus
|
closed
|
Change status code from 500 to 400 for schema upload failure
|
Menas feature priority: medium
|
## Background
Currently, when uploading schema fails 500 (Internal server error) is sent to the client. This is confusing since it does not distinguish between schema syntax errors and actual server issues.
## Feature
* Change the status code of a malformed schema from 500 to 400 (Bad request).
* Change the UI to handle 400 and 500 codes differently.
|
1.0
|
Change status code from 500 to 400 for schema upload failure - ## Background
Currently, when uploading schema fails 500 (Internal server error) is sent to the client. This is confusing since it does not distinguish between schema syntax errors and actual server issues.
## Feature
* Change the status code of a malformed schema from 500 to 400 (Bad request).
* Change the UI to handle 400 and 500 codes differently.
|
non_process
|
change status code from to for schema upload failure background currently when uploading schema fails internal server error is sent to the client this is confusing since it does not distinguish between schema syntax errors and actual server issues feature change the status code of a malformed schema from to bad request change the ui to handle and codes differently
| 0
|
177,521
| 21,478,275,767
|
IssuesEvent
|
2022-04-26 15:20:32
|
elastic/elasticsearch
|
https://api.github.com/repos/elastic/elasticsearch
|
closed
|
7.9 documentation for Configuring elasticsearch for SAML references the deprecated sp.acs endpoint.
|
>docs :Security/Authentication Team:Docs Team:Security
|
**Details:**
The documentation found at https://www.elastic.co/guide/en/elasticsearch/reference/current/saml-guide-authentication.html states that the sp.acs value should be "https://kibana.example.com/api/security/v1/saml"
However, this endpoint was deprecated in 7.6 in favor of "https://kibana.example.com/api/security/saml/callback".
See: https://github.com/elastic/elasticsearch/blob/master/x-pack/docs/en/security/authentication/saml-guide.asciidoc#create-a-saml-realm
This causes confusion as to what the setting should be defined as. When using the saml-elasticsearch-metadata script, the generated metadata binds to the location using the ../saml/callback. When these don't match because the realm settings are configured with the deprecated endpoint, it results in an authentication warning similar to:
```
Authentication to realm <realm_name> failed - Provided SAML response is not valid for realm <realm_name> (Caused by ElasticsearchSecurityException[SAML response <string> is for destination <KIBANA_URL>/api/security/v1/saml but this realm uses <KIBANA_URL>/api/security/saml/callback])
```
|
True
|
7.9 documentation for Configuring elasticsearch for SAML references the deprecated sp.acs endpoint. - **Details:**
The documentation found at https://www.elastic.co/guide/en/elasticsearch/reference/current/saml-guide-authentication.html states that the sp.acs value should be "https://kibana.example.com/api/security/v1/saml"
However, this endpoint was deprecated in 7.6 in favor of "https://kibana.example.com/api/security/saml/callback".
See: https://github.com/elastic/elasticsearch/blob/master/x-pack/docs/en/security/authentication/saml-guide.asciidoc#create-a-saml-realm
This causes confusion as to what the setting should be defined as. When using the saml-elasticsearch-metadata script, the generated metadata binds to the location using the ../saml/callback. When these don't match because the realm settings are configured with the deprecated endpoint, it results in an authentication warning similar to:
```
Authentication to realm <realm_name> failed - Provided SAML response is not valid for realm <realm_name> (Caused by ElasticsearchSecurityException[SAML response <string> is for destination <KIBANA_URL>/api/security/v1/saml but this realm uses <KIBANA_URL>/api/security/saml/callback])
```
|
non_process
|
documentation for configuring elasticsearch for saml references the deprecated sp acs endpoint details the documentation found at states that the sp acs value should be however this endpoint was deprecated in in favor of see this causes confusion as to what the setting should be defined as when using the saml elasticsearch metadata script the generated metadata binds to the location using the saml callback when these don t match because the realm settings are configured with the deprecated endpoint it results in an authentication warning similar to authentication to realm failed provided saml response is not valid for realm caused by elasticsearchsecurityexception
| 0
|
100,630
| 21,465,786,257
|
IssuesEvent
|
2022-04-26 03:27:10
|
paulevsGitch/BetterEnd
|
https://api.github.com/repos/paulevsGitch/BetterEnd
|
closed
|
Armored elytra gains no benefit from Unbreaking enchantment.
|
bug in dev code
|
I had unbreaking X on an armored elytra and noted it was wearing down fast. I made another one without enchants and found they both took damage at the same rate.
|
1.0
|
Armored elytra gains no benefit from Unbreaking enchantment. - I had unbreaking X on an armored elytra and noted it was wearing down fast. I made another one without enchants and found they both took damage at the same rate.
|
non_process
|
armored elytra gains no benefit from unbreaking enchantment i had unbreaking x on an armored elytra and noted it was wearing down fast i made another one without enchants and found they both took damage at the same rate
| 0
|
3,980
| 6,553,900,463
|
IssuesEvent
|
2017-09-06 01:49:21
|
OKFNat/offenewahlen-nrw17
|
https://api.github.com/repos/OKFNat/offenewahlen-nrw17
|
opened
|
Frontend für Suchmaschinen optimieren
|
Requirement
|
* Sitemap: soll sich selbstständig aktualisieren, bei Launch generieren
* Google Webmaster Tools
|
1.0
|
Frontend für Suchmaschinen optimieren -
* Sitemap: soll sich selbstständig aktualisieren, bei Launch generieren
* Google Webmaster Tools
|
non_process
|
frontend für suchmaschinen optimieren sitemap soll sich selbstständig aktualisieren bei launch generieren google webmaster tools
| 0
|
15,664
| 19,847,110,206
|
IssuesEvent
|
2022-01-21 08:04:42
|
ooi-data/RS01SUM1-LJ01B-09-PRESTB102-streamed-prest_real_time
|
https://api.github.com/repos/ooi-data/RS01SUM1-LJ01B-09-PRESTB102-streamed-prest_real_time
|
opened
|
🛑 Processing failed: ValueError
|
process
|
## Overview
`ValueError` found in `processing_task` task during run ended on 2022-01-21T08:04:42.154565.
## Details
Flow name: `RS01SUM1-LJ01B-09-PRESTB102-streamed-prest_real_time`
Task name: `processing_task`
Error type: `ValueError`
Error message: not enough values to unpack (expected 3, got 0)
<details>
<summary>Traceback</summary>
```
Traceback (most recent call last):
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/ooi_harvester/processor/pipeline.py", line 165, in processing
final_path = finalize_data_stream(
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/ooi_harvester/processor/__init__.py", line 84, in finalize_data_stream
append_to_zarr(mod_ds, final_store, enc, logger=logger)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/ooi_harvester/processor/__init__.py", line 357, in append_to_zarr
_append_zarr(store, mod_ds)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/ooi_harvester/processor/utils.py", line 187, in _append_zarr
existing_arr.append(var_data.values)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/variable.py", line 519, in values
return _as_array_or_item(self._data)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/variable.py", line 259, in _as_array_or_item
data = np.asarray(data)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/array/core.py", line 1541, in __array__
x = self.compute()
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/base.py", line 288, in compute
(result,) = compute(self, traverse=False, **kwargs)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/base.py", line 571, in compute
results = schedule(dsk, keys, **kwargs)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/threaded.py", line 79, in get
results = get_async(
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/local.py", line 507, in get_async
raise_exception(exc, tb)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/local.py", line 315, in reraise
raise exc
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/local.py", line 220, in execute_task
result = _execute_task(task, data)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/core.py", line 119, in _execute_task
return func(*(_execute_task(a, cache) for a in args))
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/array/core.py", line 116, in getter
c = np.asarray(c)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/indexing.py", line 357, in __array__
return np.asarray(self.array, dtype=dtype)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/indexing.py", line 551, in __array__
self._ensure_cached()
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/indexing.py", line 548, in _ensure_cached
self.array = NumpyIndexingAdapter(np.asarray(self.array))
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/indexing.py", line 521, in __array__
return np.asarray(self.array, dtype=dtype)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/indexing.py", line 422, in __array__
return np.asarray(array[self.key], dtype=None)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/coding/variables.py", line 70, in __array__
return self.func(self.array)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/coding/variables.py", line 137, in _apply_mask
data = np.asarray(data, dtype=dtype)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/indexing.py", line 422, in __array__
return np.asarray(array[self.key], dtype=None)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/backends/zarr.py", line 73, in __getitem__
return array[key.tuple]
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/zarr/core.py", line 673, in __getitem__
return self.get_basic_selection(selection, fields=fields)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/zarr/core.py", line 798, in get_basic_selection
return self._get_basic_selection_nd(selection=selection, out=out,
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/zarr/core.py", line 841, in _get_basic_selection_nd
return self._get_selection(indexer=indexer, out=out, fields=fields)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/zarr/core.py", line 1135, in _get_selection
lchunk_coords, lchunk_selection, lout_selection = zip(*indexer)
ValueError: not enough values to unpack (expected 3, got 0)
```
</details>
|
1.0
|
🛑 Processing failed: ValueError - ## Overview
`ValueError` found in `processing_task` task during run ended on 2022-01-21T08:04:42.154565.
## Details
Flow name: `RS01SUM1-LJ01B-09-PRESTB102-streamed-prest_real_time`
Task name: `processing_task`
Error type: `ValueError`
Error message: not enough values to unpack (expected 3, got 0)
<details>
<summary>Traceback</summary>
```
Traceback (most recent call last):
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/ooi_harvester/processor/pipeline.py", line 165, in processing
final_path = finalize_data_stream(
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/ooi_harvester/processor/__init__.py", line 84, in finalize_data_stream
append_to_zarr(mod_ds, final_store, enc, logger=logger)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/ooi_harvester/processor/__init__.py", line 357, in append_to_zarr
_append_zarr(store, mod_ds)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/ooi_harvester/processor/utils.py", line 187, in _append_zarr
existing_arr.append(var_data.values)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/variable.py", line 519, in values
return _as_array_or_item(self._data)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/variable.py", line 259, in _as_array_or_item
data = np.asarray(data)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/array/core.py", line 1541, in __array__
x = self.compute()
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/base.py", line 288, in compute
(result,) = compute(self, traverse=False, **kwargs)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/base.py", line 571, in compute
results = schedule(dsk, keys, **kwargs)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/threaded.py", line 79, in get
results = get_async(
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/local.py", line 507, in get_async
raise_exception(exc, tb)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/local.py", line 315, in reraise
raise exc
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/local.py", line 220, in execute_task
result = _execute_task(task, data)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/core.py", line 119, in _execute_task
return func(*(_execute_task(a, cache) for a in args))
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/array/core.py", line 116, in getter
c = np.asarray(c)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/indexing.py", line 357, in __array__
return np.asarray(self.array, dtype=dtype)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/indexing.py", line 551, in __array__
self._ensure_cached()
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/indexing.py", line 548, in _ensure_cached
self.array = NumpyIndexingAdapter(np.asarray(self.array))
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/indexing.py", line 521, in __array__
return np.asarray(self.array, dtype=dtype)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/indexing.py", line 422, in __array__
return np.asarray(array[self.key], dtype=None)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/coding/variables.py", line 70, in __array__
return self.func(self.array)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/coding/variables.py", line 137, in _apply_mask
data = np.asarray(data, dtype=dtype)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/indexing.py", line 422, in __array__
return np.asarray(array[self.key], dtype=None)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/backends/zarr.py", line 73, in __getitem__
return array[key.tuple]
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/zarr/core.py", line 673, in __getitem__
return self.get_basic_selection(selection, fields=fields)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/zarr/core.py", line 798, in get_basic_selection
return self._get_basic_selection_nd(selection=selection, out=out,
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/zarr/core.py", line 841, in _get_basic_selection_nd
return self._get_selection(indexer=indexer, out=out, fields=fields)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/zarr/core.py", line 1135, in _get_selection
lchunk_coords, lchunk_selection, lout_selection = zip(*indexer)
ValueError: not enough values to unpack (expected 3, got 0)
```
</details>
|
process
|
🛑 processing failed valueerror overview valueerror found in processing task task during run ended on details flow name streamed prest real time task name processing task error type valueerror error message not enough values to unpack expected got traceback traceback most recent call last file srv conda envs notebook lib site packages ooi harvester processor pipeline py line in processing final path finalize data stream file srv conda envs notebook lib site packages ooi harvester processor init py line in finalize data stream append to zarr mod ds final store enc logger logger file srv conda envs notebook lib site packages ooi harvester processor init py line in append to zarr append zarr store mod ds file srv conda envs notebook lib site packages ooi harvester processor utils py line in append zarr existing arr append var data values file srv conda envs notebook lib site packages xarray core variable py line in values return as array or item self data file srv conda envs notebook lib site packages xarray core variable py line in as array or item data np asarray data file srv conda envs notebook lib site packages dask array core py line in array x self compute file srv conda envs notebook lib site packages dask base py line in compute result compute self traverse false kwargs file srv conda envs notebook lib site packages dask base py line in compute results schedule dsk keys kwargs file srv conda envs notebook lib site packages dask threaded py line in get results get async file srv conda envs notebook lib site packages dask local py line in get async raise exception exc tb file srv conda envs notebook lib site packages dask local py line in reraise raise exc file srv conda envs notebook lib site packages dask local py line in execute task result execute task task data file srv conda envs notebook lib site packages dask core py line in execute task return func execute task a cache for a in args file srv conda envs notebook lib site packages dask array core py line in getter c np asarray c file srv conda envs notebook lib site packages xarray core indexing py line in array return np asarray self array dtype dtype file srv conda envs notebook lib site packages xarray core indexing py line in array self ensure cached file srv conda envs notebook lib site packages xarray core indexing py line in ensure cached self array numpyindexingadapter np asarray self array file srv conda envs notebook lib site packages xarray core indexing py line in array return np asarray self array dtype dtype file srv conda envs notebook lib site packages xarray core indexing py line in array return np asarray array dtype none file srv conda envs notebook lib site packages xarray coding variables py line in array return self func self array file srv conda envs notebook lib site packages xarray coding variables py line in apply mask data np asarray data dtype dtype file srv conda envs notebook lib site packages xarray core indexing py line in array return np asarray array dtype none file srv conda envs notebook lib site packages xarray backends zarr py line in getitem return array file srv conda envs notebook lib site packages zarr core py line in getitem return self get basic selection selection fields fields file srv conda envs notebook lib site packages zarr core py line in get basic selection return self get basic selection nd selection selection out out file srv conda envs notebook lib site packages zarr core py line in get basic selection nd return self get selection indexer indexer out out fields fields file srv conda envs notebook lib site packages zarr core py line in get selection lchunk coords lchunk selection lout selection zip indexer valueerror not enough values to unpack expected got
| 1
|
7,766
| 10,888,590,100
|
IssuesEvent
|
2019-11-18 16:31:55
|
codeuniversity/smag-mvp
|
https://api.github.com/repos/codeuniversity/smag-mvp
|
closed
|
Create face encoding postgres inserter
|
Image Processing
|
- read encoding, post_id, boundries (internal_picture_url?) from kafka topic
- insert into postgres (new table)
|
1.0
|
Create face encoding postgres inserter - - read encoding, post_id, boundries (internal_picture_url?) from kafka topic
- insert into postgres (new table)
|
process
|
create face encoding postgres inserter read encoding post id boundries internal picture url from kafka topic insert into postgres new table
| 1
|
7,156
| 7,861,104,188
|
IssuesEvent
|
2018-06-21 22:30:52
|
terraform-providers/terraform-provider-aws
|
https://api.github.com/repos/terraform-providers/terraform-provider-aws
|
closed
|
TargetTrackingScaling support
|
enhancement service/ec2
|
_This issue was originally opened by @meyerbro as hashicorp/terraform#15823. It was migrated here as a result of the [provider split](https://www.hashicorp.com/blog/upcoming-provider-changes-in-terraform-0-10/). The original body of the issue is below._
<hr>
Hello, when are you planning to support TargetTrackingScaling?
I really want to use Terraform for that and it's about one month already that AWS launched that but no Terraform support it seems.
Thanks,
Felipe
|
1.0
|
TargetTrackingScaling support - _This issue was originally opened by @meyerbro as hashicorp/terraform#15823. It was migrated here as a result of the [provider split](https://www.hashicorp.com/blog/upcoming-provider-changes-in-terraform-0-10/). The original body of the issue is below._
<hr>
Hello, when are you planning to support TargetTrackingScaling?
I really want to use Terraform for that and it's about one month already that AWS launched that but no Terraform support it seems.
Thanks,
Felipe
|
non_process
|
targettrackingscaling support this issue was originally opened by meyerbro as hashicorp terraform it was migrated here as a result of the the original body of the issue is below hello when are you planning to support targettrackingscaling i really want to use terraform for that and it s about one month already that aws launched that but no terraform support it seems thanks felipe
| 0
|
14,961
| 18,446,889,061
|
IssuesEvent
|
2021-10-15 04:06:33
|
cypress-io/cypress
|
https://api.github.com/repos/cypress-io/cypress
|
reopened
|
Fix `error_ui` system test
|
process: tests stage: waiting
|
System test "e2e error ui handles sourcemaps in webpack for project: webpack-preprocessor-awesome-typescript-loader" began failing after the changes in #18172 merged into the changes in #16354.
It is currently skipped in that PR but should be fixed.
https://app.circleci.com/pipelines/github/cypress-io/cypress/24949/workflows/9a3333e5-0255-4bf2-962c-9a9c7ce8d755/jobs/931986/tests#failed-test-0
Error output from `yarn workspace @tooling/system-tests test error_ui`:
```
====================================================================================================
(Run Starting)
┌────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Cypress: 8.6.0 │
│ Browser: Electron 93 (headless) │
│ Specs: 1 found (failing_spec.ts) │
│ Searched: cypress/integration/failing_spec.* │
└────────────────────────────────────────────────────────────────────────────────────────────────┘
────────────────────────────────────────────────────────────────────────────────────────────────────
Running: failing_spec.ts (1 of 1)
(node:437526) electron: The default of nativeWindowOpen is deprecated and will be changing from false to true in Electron 15. See https://github.com/electron/electron/issues/28511 for more information.
ℹ ｢atl｣: Using typescript@4.2.4 from typescript
ℹ ｢atl｣: Using tsconfig.json from /home/flotwig/src/cypress/cypress/system-tests/.projects/webpack-preprocessor-awesome-typescript-loader/cypress/tsconfig.json
ℹ ｢atl｣: Checking started in a separate process...
✖ ｢atl｣: Checking finished with 253 errors
Oops...we found an error preparing this test file:
cypress/integration/failing_spec.ts
The error was:
Error: Webpack Compilation Error
[at-loader] ./cypress/integration/failing_spec.ts:21:1
TS2304: Cannot find name 'context'.
[at-loader] ./cypress/integration/failing_spec.ts:22:3
TS2304: Cannot find name 'beforeEach'.
[at-loader] ./cypress/integration/failing_spec.ts:4:22
TS6053: File '/home/flotwig/src/cypress/cli/types/mocha/index.d.ts' not found.
[at-loader] ./cypress/integration/failing_spec.ts:5:22
TS6053: File '/home/flotwig/src/cypress/cli/types/jquery/index.d.ts' not found.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:10:19
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:11:16
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:12:16
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:18:15
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:24:16
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:25:15
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:26:13
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:27:12
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:31:12
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:32:11
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:35:9
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:57:12
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:64:14
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:65:19
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:66:12
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:67:15
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:101:56
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:101:113
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:101:134
TS2315: Type 'JQuery' is not generic.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:140:56
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:140:113
TS2315: Type 'JQuery' is not generic.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:152:35
TS2315: Type 'JQuery' is not generic.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:170:66
TS2315: Type 'JQuery' is not generic.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:177:20
TS2315: Type 'JQuery' is not generic.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:177:32
TS2315: Type 'JQuery' is not generic.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:197:86
TS2315: Type 'JQuery' is not generic.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:204:16
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:204:48
TS2315: Type 'JQuery' is not generic.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:211:33
TS2315: Type 'JQuery' is not generic.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:220:34
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:220:56
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:287:21
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:287:43
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:296:38
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:296:76
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:296:104
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:303:38
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:303:76
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:303:104
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:319:24
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:319:46
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:328:38
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:328:76
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:328:104
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:328:121
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:333:62
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:419:111
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:432:49
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:480:49
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:674:30
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:674:48
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1539:15
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1540:18
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1541:29
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1560:18
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1561:28
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1595:23
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1595:51
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1595:81
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1613:33
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1613:58
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1623:19
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1624:22
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1624:50
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1695:28
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1695:56
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1695:86
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1770:25
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1770:73
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1777:24
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1777:49
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1905:52
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1932:25
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1932:45
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:2301:102
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:2326:108
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:2514:24
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:2523:90
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:2573:79
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:2649:16
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:2650:19
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:2651:30
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:2662:19
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:2663:29
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:2745:24
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:2745:52
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:2745:82
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:2763:34
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:2763:59
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13106:73
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13106:92
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13106:119
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13166:55
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13175:61
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13175:131
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13187:61
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13188:106
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13200:80
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13200:127
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13200:160
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13388:24
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13388:51
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13389:24
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13389:51
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13390:24
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13390:51
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13391:8
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13418:24
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13418:51
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13419:24
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13419:51
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13420:8
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13447:24
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13448:24
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13449:8
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13474:36
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13474:63
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13474:92
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13497:56
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13497:83
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13497:113
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13520:32
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/index.d.ts:34:10
TS2304: Cannot find name 'jQuery'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:47:20
TS2304: Cannot find name 'JQueryAjaxSettings'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:47:41
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:54:34
TS2304: Cannot find name 'JQueryAjaxSettings'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:54:55
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:62:73
TS2304: Cannot find name 'JQueryAjaxSettings'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:62:100
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:68:54
TS2304: Cannot find name 'JQueryAjaxSettings'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:68:81
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:70:19
TS2304: Cannot find name 'JQueryAjaxSettings'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:77:24
TS2304: Cannot find name 'JQueryAjaxSettings'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:86:71
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:86:110
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:95:93
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:95:132
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:102:75
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:102:95
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:110:97
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:110:117
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:117:82
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:117:102
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:122:12
TS2304: Cannot find name 'JQueryParam'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:131:72
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:131:111
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:140:94
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:140:133
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:147:32
TS2304: Cannot find name 'JQueryCallback'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:226:35
TS2304: Cannot find name 'JQueryPromise'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:226:81
TS2304: Cannot find name 'JQueryPromise'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:308:42
TS2304: Cannot find name 'JQueryDeferred'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:308:70
TS2304: Cannot find name 'JQueryDeferred'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:345:12
TS2304: Cannot find name 'JQueryEventConstructor'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:360:14
TS2304: Cannot find name 'JQuerySupport'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:581:35
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:587:32
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:587:58
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:587:83
TS2304: Cannot find name 'JQueryAjaxSettings'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:593:31
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:593:57
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:593:81
TS2304: Cannot find name 'JQueryAjaxSettings'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:611:34
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:611:98
TS2304: Cannot find name 'JQueryAjaxSettings'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:629:23
TS2304: Cannot find name 'JQuerySerializeArrayElement'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:869:15
TS2304: Cannot find name 'JQueryCoordinates'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:875:25
TS2304: Cannot find name 'JQueryCoordinates'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:881:42
TS2304: Cannot find name 'JQueryCoordinates'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:881:64
TS2304: Cannot find name 'JQueryCoordinates'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:914:17
TS2304: Cannot find name 'JQueryCoordinates'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1012:46
TS2304: Cannot find name 'JQueryPromise'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1037:42
TS2304: Cannot find name 'JQueryAnimationOptions'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1067:21
TS2304: Cannot find name 'JQueryAnimationOptions'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1089:22
TS2304: Cannot find name 'JQueryAnimationOptions'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1129:25
TS2304: Cannot find name 'JQueryAnimationOptions'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1158:19
TS2304: Cannot find name 'JQueryAnimationOptions'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1180:19
TS2304: Cannot find name 'JQueryAnimationOptions'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1202:24
TS2304: Cannot find name 'JQueryAnimationOptions'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1224:26
TS2304: Cannot find name 'JQueryAnimationOptions'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1246:22
TS2304: Cannot find name 'JQueryAnimationOptions'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1284:21
TS2304: Cannot find name 'JQueryAnimationOptions'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1299:68
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1306:52
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1338:33
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1345:51
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1356:35
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1363:53
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1374:34
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1381:52
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1392:37
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1399:55
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1401:71
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1402:87
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1413:34
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1420:52
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1427:36
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1434:55
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1441:37
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1448:56
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1456:36
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1456:89
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1462:39
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1473:36
TS2304: Cannot find name 'JQueryKeyEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1480:54
TS2304: Cannot find name 'JQueryKeyEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1491:37
TS2304: Cannot find name 'JQueryKeyEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1498:55
TS2304: Cannot find name 'JQueryKeyEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1509:34
TS2304: Cannot find name 'JQueryKeyEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1516:52
TS2304: Cannot find name 'JQueryKeyEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1523:33
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1530:51
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1541:38
TS2304: Cannot find name 'JQueryMouseEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1548:57
TS2304: Cannot find name 'JQueryMouseEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1559:39
TS2304: Cannot find name 'JQueryMouseEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1566:58
TS2304: Cannot find name 'JQueryMouseEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1577:39
TS2304: Cannot find name 'JQueryMouseEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1584:58
TS2304: Cannot find name 'JQueryMouseEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1595:38
TS2304: Cannot find name 'JQueryMouseEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1602:57
TS2304: Cannot find name 'JQueryMouseEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1613:37
TS2304: Cannot find name 'JQueryMouseEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1620:56
TS2304: Cannot find name 'JQueryMouseEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1631:38
TS2304: Cannot find name 'JQueryMouseEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1638:57
TS2304: Cannot find name 'JQueryMouseEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1649:36
TS2304: Cannot find name 'JQueryMouseEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1656:55
TS2304: Cannot find name 'JQueryMouseEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1669:68
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1676:48
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1691:47
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1699:58
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1707:65
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1716:76
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1739:48
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1747:62
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1756:66
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1765:77
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1801:35
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1808:54
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1819:35
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1826:54
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1837:35
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1844:54
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1855:35
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1862:53
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1877:20
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1893:56
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1919:77
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1939:35
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1946:53
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1960:34
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1967:50
TS2304: Cannot find name 'JQueryEventObject'.
at handle (/home/flotwig/src/cypress/cypress/npm/webpack-preprocessor/dist/index.js:180:23)
at finalCallback (/home/flotwig/src/cypress/cypress/npm/webpack-preprocessor/node_modules/webpack/lib/Compiler.js:257:39)
at /home/flotwig/src/cypress/cypress/npm/webpack-preprocessor/node_modules/webpack/lib/Compiler.js:306:14
at AsyncSeriesHook.eval [as callAsync] (eval at create (/home/flotwig/src/cypress/cypress/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
at AsyncSeriesHook.lazyCompileHook (/home/flotwig/src/cypress/cypress/node_modules/tapable/lib/Hook.js:154:20)
at /home/flotwig/src/cypress/cypress/npm/webpack-preprocessor/node_modules/webpack/lib/Compiler.js:304:22
at Compiler.emitRecords (/home/flotwig/src/cypress/cypress/npm/webpack-preprocessor/node_modules/webpack/lib/Compiler.js:499:39)
at /home/flotwig/src/cypress/cypress/npm/webpack-preprocessor/node_modules/webpack/lib/Compiler.js:298:10
at /home/flotwig/src/cypress/cypress/npm/webpack-preprocessor/node_modules/webpack/lib/Compiler.js:485:14
at AsyncSeriesHook.eval [as callAsync] (eval at create (/home/flotwig/src/cypress/cypress/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
at AsyncSeriesHook.lazyCompileHook (/home/flotwig/src/cypress/cypress/node_modules/tapable/lib/Hook.js:154:20)
at /home/flotwig/src/cypress/cypress/npm/webpack-preprocessor/node_modules/webpack/lib/Compiler.js:482:27
at /home/flotwig/src/cypress/cypress/node_modules/neo-async/async.js:2818:7
at done (/home/flotwig/src/cypress/cypress/node_modules/neo-async/async.js:3522:9)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/home/flotwig/src/cypress/cypress/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
at AsyncSeriesHook.lazyCompileHook (/home/flotwig/src/cypress/cypress/node_modules/tapable/lib/Hook.js:154:20)
at /home/flotwig/src/cypress/cypress/npm/webpack-preprocessor/node_modules/webpack/lib/Compiler.js:464:33
at /home/flotwig/src/cypress/cypress/packages/server/node_modules/graceful-fs/graceful-fs.js:111:16
at /home/flotwig/src/cypress/cypress/node_modules/graceful-fs/graceful-fs.js:61:14
at /home/flotwig/src/cypress/cypress/packages/server/node_modules/graceful-fs/graceful-fs.js:45:10
at FSReqCallback.oncomplete (fs.js:180:23)
This occurred while Cypress was compiling and bundling your test code. This is usually caused by:
- A missing file or dependency
- A syntax error in the file or one of its dependencies
Fix the error in your code and re-run your tests.
(Results)
┌────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Tests: 0 │
│ Passing: 0 │
│ Failing: 1 │
│ Pending: 0 │
│ Skipped: 0 │
│ Screenshots: 0 │
│ Video: true │
│ Duration: 0 seconds │
│ Spec Ran: failing_spec.ts │
└────────────────────────────────────────────────────────────────────────────────────────────────┘
(Video)
- Started processing: Compressing to 32 CRF
- Finished processing: /XXX/XXX/XXX/cypress/videos/failing_spec.ts.mp4 (2 seconds)
====================================================================================================
(Run Finished)
Spec Tests Passing Failing Pending Skipped
┌────────────────────────────────────────────────────────────────────────────────────────────────┐
│ ✖ failing_spec.ts 0ms - - 1 - - │
└────────────────────────────────────────────────────────────────────────────────────────────────┘
✖ 1 of 1 failed (100%) 0ms - - 1 - -
```
|
1.0
|
Fix `error_ui` system test - System test "e2e error ui handles sourcemaps in webpack for project: webpack-preprocessor-awesome-typescript-loader" began failing after the changes in #18172 merged into the changes in #16354.
It is currently skipped in that PR but should be fixed.
https://app.circleci.com/pipelines/github/cypress-io/cypress/24949/workflows/9a3333e5-0255-4bf2-962c-9a9c7ce8d755/jobs/931986/tests#failed-test-0
Error output from `yarn workspace @tooling/system-tests test error_ui`:
```
====================================================================================================
(Run Starting)
┌────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Cypress: 8.6.0 │
│ Browser: Electron 93 (headless) │
│ Specs: 1 found (failing_spec.ts) │
│ Searched: cypress/integration/failing_spec.* │
└────────────────────────────────────────────────────────────────────────────────────────────────┘
────────────────────────────────────────────────────────────────────────────────────────────────────
Running: failing_spec.ts (1 of 1)
(node:437526) electron: The default of nativeWindowOpen is deprecated and will be changing from false to true in Electron 15. See https://github.com/electron/electron/issues/28511 for more information.
ℹ ｢atl｣: Using typescript@4.2.4 from typescript
ℹ ｢atl｣: Using tsconfig.json from /home/flotwig/src/cypress/cypress/system-tests/.projects/webpack-preprocessor-awesome-typescript-loader/cypress/tsconfig.json
ℹ ｢atl｣: Checking started in a separate process...
✖ ｢atl｣: Checking finished with 253 errors
Oops...we found an error preparing this test file:
cypress/integration/failing_spec.ts
The error was:
Error: Webpack Compilation Error
[at-loader] ./cypress/integration/failing_spec.ts:21:1
TS2304: Cannot find name 'context'.
[at-loader] ./cypress/integration/failing_spec.ts:22:3
TS2304: Cannot find name 'beforeEach'.
[at-loader] ./cypress/integration/failing_spec.ts:4:22
TS6053: File '/home/flotwig/src/cypress/cli/types/mocha/index.d.ts' not found.
[at-loader] ./cypress/integration/failing_spec.ts:5:22
TS6053: File '/home/flotwig/src/cypress/cli/types/jquery/index.d.ts' not found.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:10:19
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:11:16
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:12:16
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:18:15
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:24:16
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:25:15
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:26:13
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:27:12
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:31:12
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:32:11
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:35:9
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:57:12
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:64:14
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:65:19
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:66:12
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:67:15
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:101:56
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:101:113
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:101:134
TS2315: Type 'JQuery' is not generic.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:140:56
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:140:113
TS2315: Type 'JQuery' is not generic.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:152:35
TS2315: Type 'JQuery' is not generic.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:170:66
TS2315: Type 'JQuery' is not generic.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:177:20
TS2315: Type 'JQuery' is not generic.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:177:32
TS2315: Type 'JQuery' is not generic.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:197:86
TS2315: Type 'JQuery' is not generic.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:204:16
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:204:48
TS2315: Type 'JQuery' is not generic.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:211:33
TS2315: Type 'JQuery' is not generic.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:220:34
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:220:56
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:287:21
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:287:43
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:296:38
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:296:76
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:296:104
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:303:38
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:303:76
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:303:104
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:319:24
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:319:46
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:328:38
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:328:76
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:328:104
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:328:121
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:333:62
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:419:111
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:432:49
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:480:49
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:674:30
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:674:48
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1539:15
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1540:18
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1541:29
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1560:18
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1561:28
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1595:23
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1595:51
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1595:81
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1613:33
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1613:58
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1623:19
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1624:22
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1624:50
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1695:28
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1695:56
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1695:86
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1770:25
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1770:73
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1777:24
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1777:49
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1905:52
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1932:25
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:1932:45
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:2301:102
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:2326:108
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:2514:24
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:2523:90
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:2573:79
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:2649:16
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:2650:19
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:2651:30
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:2662:19
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:2663:29
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:2745:24
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:2745:52
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:2745:82
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:2763:34
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:2763:59
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13106:73
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13106:92
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13106:119
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13166:55
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13175:61
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13175:131
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13187:61
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13188:106
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13200:80
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13200:127
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13200:160
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13388:24
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13388:51
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13389:24
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13389:51
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13390:24
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13390:51
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13391:8
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13418:24
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13418:51
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13419:24
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13419:51
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13420:8
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13447:24
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13448:24
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13449:8
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13474:36
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13474:63
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13474:92
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13497:56
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13497:83
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13497:113
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/JQueryStatic.d.ts:13520:32
TS2702: 'JQuery' only refers to a type, but is being used as a namespace here.
[at-loader] ../../../node_modules/@types/jquery/index.d.ts:34:10
TS2304: Cannot find name 'jQuery'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:47:20
TS2304: Cannot find name 'JQueryAjaxSettings'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:47:41
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:54:34
TS2304: Cannot find name 'JQueryAjaxSettings'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:54:55
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:62:73
TS2304: Cannot find name 'JQueryAjaxSettings'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:62:100
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:68:54
TS2304: Cannot find name 'JQueryAjaxSettings'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:68:81
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:70:19
TS2304: Cannot find name 'JQueryAjaxSettings'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:77:24
TS2304: Cannot find name 'JQueryAjaxSettings'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:86:71
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:86:110
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:95:93
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:95:132
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:102:75
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:102:95
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:110:97
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:110:117
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:117:82
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:117:102
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:122:12
TS2304: Cannot find name 'JQueryParam'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:131:72
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:131:111
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:140:94
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:140:133
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:147:32
TS2304: Cannot find name 'JQueryCallback'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:226:35
TS2304: Cannot find name 'JQueryPromise'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:226:81
TS2304: Cannot find name 'JQueryPromise'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:308:42
TS2304: Cannot find name 'JQueryDeferred'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:308:70
TS2304: Cannot find name 'JQueryDeferred'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:345:12
TS2304: Cannot find name 'JQueryEventConstructor'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:360:14
TS2304: Cannot find name 'JQuerySupport'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:581:35
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:587:32
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:587:58
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:587:83
TS2304: Cannot find name 'JQueryAjaxSettings'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:593:31
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:593:57
TS2304: Cannot find name 'JQueryXHR'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:593:81
TS2304: Cannot find name 'JQueryAjaxSettings'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:611:34
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:611:98
TS2304: Cannot find name 'JQueryAjaxSettings'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:629:23
TS2304: Cannot find name 'JQuerySerializeArrayElement'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:869:15
TS2304: Cannot find name 'JQueryCoordinates'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:875:25
TS2304: Cannot find name 'JQueryCoordinates'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:881:42
TS2304: Cannot find name 'JQueryCoordinates'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:881:64
TS2304: Cannot find name 'JQueryCoordinates'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:914:17
TS2304: Cannot find name 'JQueryCoordinates'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1012:46
TS2304: Cannot find name 'JQueryPromise'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1037:42
TS2304: Cannot find name 'JQueryAnimationOptions'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1067:21
TS2304: Cannot find name 'JQueryAnimationOptions'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1089:22
TS2304: Cannot find name 'JQueryAnimationOptions'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1129:25
TS2304: Cannot find name 'JQueryAnimationOptions'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1158:19
TS2304: Cannot find name 'JQueryAnimationOptions'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1180:19
TS2304: Cannot find name 'JQueryAnimationOptions'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1202:24
TS2304: Cannot find name 'JQueryAnimationOptions'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1224:26
TS2304: Cannot find name 'JQueryAnimationOptions'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1246:22
TS2304: Cannot find name 'JQueryAnimationOptions'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1284:21
TS2304: Cannot find name 'JQueryAnimationOptions'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1299:68
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1306:52
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1338:33
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1345:51
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1356:35
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1363:53
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1374:34
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1381:52
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1392:37
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1399:55
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1401:71
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1402:87
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1413:34
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1420:52
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1427:36
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1434:55
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1441:37
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1448:56
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1456:36
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1456:89
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1462:39
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1473:36
TS2304: Cannot find name 'JQueryKeyEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1480:54
TS2304: Cannot find name 'JQueryKeyEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1491:37
TS2304: Cannot find name 'JQueryKeyEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1498:55
TS2304: Cannot find name 'JQueryKeyEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1509:34
TS2304: Cannot find name 'JQueryKeyEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1516:52
TS2304: Cannot find name 'JQueryKeyEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1523:33
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1530:51
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1541:38
TS2304: Cannot find name 'JQueryMouseEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1548:57
TS2304: Cannot find name 'JQueryMouseEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1559:39
TS2304: Cannot find name 'JQueryMouseEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1566:58
TS2304: Cannot find name 'JQueryMouseEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1577:39
TS2304: Cannot find name 'JQueryMouseEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1584:58
TS2304: Cannot find name 'JQueryMouseEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1595:38
TS2304: Cannot find name 'JQueryMouseEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1602:57
TS2304: Cannot find name 'JQueryMouseEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1613:37
TS2304: Cannot find name 'JQueryMouseEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1620:56
TS2304: Cannot find name 'JQueryMouseEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1631:38
TS2304: Cannot find name 'JQueryMouseEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1638:57
TS2304: Cannot find name 'JQueryMouseEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1649:36
TS2304: Cannot find name 'JQueryMouseEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1656:55
TS2304: Cannot find name 'JQueryMouseEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1669:68
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1676:48
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1691:47
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1699:58
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1707:65
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1716:76
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1739:48
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1747:62
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1756:66
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1765:77
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1801:35
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1808:54
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1819:35
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1826:54
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1837:35
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1844:54
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1855:35
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1862:53
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1877:20
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1893:56
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1919:77
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1939:35
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1946:53
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1960:34
TS2304: Cannot find name 'JQueryEventObject'.
[at-loader] ../../../node_modules/@types/chai-jquery/index.d.ts:1967:50
TS2304: Cannot find name 'JQueryEventObject'.
at handle (/home/flotwig/src/cypress/cypress/npm/webpack-preprocessor/dist/index.js:180:23)
at finalCallback (/home/flotwig/src/cypress/cypress/npm/webpack-preprocessor/node_modules/webpack/lib/Compiler.js:257:39)
at /home/flotwig/src/cypress/cypress/npm/webpack-preprocessor/node_modules/webpack/lib/Compiler.js:306:14
at AsyncSeriesHook.eval [as callAsync] (eval at create (/home/flotwig/src/cypress/cypress/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
at AsyncSeriesHook.lazyCompileHook (/home/flotwig/src/cypress/cypress/node_modules/tapable/lib/Hook.js:154:20)
at /home/flotwig/src/cypress/cypress/npm/webpack-preprocessor/node_modules/webpack/lib/Compiler.js:304:22
at Compiler.emitRecords (/home/flotwig/src/cypress/cypress/npm/webpack-preprocessor/node_modules/webpack/lib/Compiler.js:499:39)
at /home/flotwig/src/cypress/cypress/npm/webpack-preprocessor/node_modules/webpack/lib/Compiler.js:298:10
at /home/flotwig/src/cypress/cypress/npm/webpack-preprocessor/node_modules/webpack/lib/Compiler.js:485:14
at AsyncSeriesHook.eval [as callAsync] (eval at create (/home/flotwig/src/cypress/cypress/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
at AsyncSeriesHook.lazyCompileHook (/home/flotwig/src/cypress/cypress/node_modules/tapable/lib/Hook.js:154:20)
at /home/flotwig/src/cypress/cypress/npm/webpack-preprocessor/node_modules/webpack/lib/Compiler.js:482:27
at /home/flotwig/src/cypress/cypress/node_modules/neo-async/async.js:2818:7
at done (/home/flotwig/src/cypress/cypress/node_modules/neo-async/async.js:3522:9)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/home/flotwig/src/cypress/cypress/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
at AsyncSeriesHook.lazyCompileHook (/home/flotwig/src/cypress/cypress/node_modules/tapable/lib/Hook.js:154:20)
at /home/flotwig/src/cypress/cypress/npm/webpack-preprocessor/node_modules/webpack/lib/Compiler.js:464:33
at /home/flotwig/src/cypress/cypress/packages/server/node_modules/graceful-fs/graceful-fs.js:111:16
at /home/flotwig/src/cypress/cypress/node_modules/graceful-fs/graceful-fs.js:61:14
at /home/flotwig/src/cypress/cypress/packages/server/node_modules/graceful-fs/graceful-fs.js:45:10
at FSReqCallback.oncomplete (fs.js:180:23)
This occurred while Cypress was compiling and bundling your test code. This is usually caused by:
- A missing file or dependency
- A syntax error in the file or one of its dependencies
Fix the error in your code and re-run your tests.
(Results)
┌────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Tests: 0 │
│ Passing: 0 │
│ Failing: 1 │
│ Pending: 0 │
│ Skipped: 0 │
│ Screenshots: 0 │
│ Video: true │
│ Duration: 0 seconds │
│ Spec Ran: failing_spec.ts │
└────────────────────────────────────────────────────────────────────────────────────────────────┘
(Video)
- Started processing: Compressing to 32 CRF
- Finished processing: /XXX/XXX/XXX/cypress/videos/failing_spec.ts.mp4 (2 seconds)
====================================================================================================
(Run Finished)
Spec Tests Passing Failing Pending Skipped
┌────────────────────────────────────────────────────────────────────────────────────────────────┐
│ ✖ failing_spec.ts 0ms - - 1 - - │
└────────────────────────────────────────────────────────────────────────────────────────────────┘
✖ 1 of 1 failed (100%) 0ms - - 1 - -
```
|
process
|
fix error ui system test system test error ui handles sourcemaps in webpack for project webpack preprocessor awesome typescript loader began failing after the changes in merged into the changes in it is currently skipped in that pr but should be fixed error output from yarn workspace tooling system tests test error ui run starting ┌────────────────────────────────────────────────────────────────────────────────────────────────┐ │ cypress │ │ browser electron headless │ │ specs found failing spec ts │ │ searched cypress integration failing spec │ └────────────────────────────────────────────────────────────────────────────────────────────────┘ ──────────────────────────────────────────────────────────────────────────────────────────────────── running failing spec ts of node electron the default of nativewindowopen is deprecated and will be changing from false to true in electron see for more information ℹ ｢atl｣ using typescript from typescript ℹ ｢atl｣ using tsconfig json from home flotwig src cypress cypress system tests projects webpack preprocessor awesome typescript loader cypress tsconfig json ℹ ｢atl｣ checking started in a separate process ✖ ｢atl｣ checking finished with errors oops we found an error preparing this test file cypress integration failing spec ts the error was error webpack compilation error cypress integration failing spec ts cannot find name context cypress integration failing spec ts cannot find name beforeeach cypress integration failing spec ts file home flotwig src cypress cli types mocha index d ts not found cypress integration failing spec ts file home flotwig src cypress cli types jquery index d ts not found node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts type jquery is not generic node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts type jquery is not generic node modules types jquery jquerystatic d ts type jquery is not generic node modules types jquery jquerystatic d ts type jquery is not generic node modules types jquery jquerystatic d ts type jquery is not generic node modules types jquery jquerystatic d ts type jquery is not generic node modules types jquery jquerystatic d ts type jquery is not generic node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts type jquery is not generic node modules types jquery jquerystatic d ts type jquery is not generic node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery jquerystatic d ts jquery only refers to a type but is being used as a namespace here node modules types jquery index d ts cannot find name jquery node modules types chai jquery index d ts cannot find name jqueryajaxsettings node modules types chai jquery index d ts cannot find name jqueryxhr node modules types chai jquery index d ts cannot find name jqueryajaxsettings node modules types chai jquery index d ts cannot find name jqueryxhr node modules types chai jquery index d ts cannot find name jqueryajaxsettings node modules types chai jquery index d ts cannot find name jqueryxhr node modules types chai jquery index d ts cannot find name jqueryajaxsettings node modules types chai jquery index d ts cannot find name jqueryxhr node modules types chai jquery index d ts cannot find name jqueryajaxsettings node modules types chai jquery index d ts cannot find name jqueryajaxsettings node modules types chai jquery index d ts cannot find name jqueryxhr node modules types chai jquery index d ts cannot find name jqueryxhr node modules types chai jquery index d ts cannot find name jqueryxhr node modules types chai jquery index d ts cannot find name jqueryxhr node modules types chai jquery index d ts cannot find name jqueryxhr node modules types chai jquery index d ts cannot find name jqueryxhr node modules types chai jquery index d ts cannot find name jqueryxhr node modules types chai jquery index d ts cannot find name jqueryxhr node modules types chai jquery index d ts cannot find name jqueryxhr node modules types chai jquery index d ts cannot find name jqueryxhr node modules types chai jquery index d ts cannot find name jqueryparam node modules types chai jquery index d ts cannot find name jqueryxhr node modules types chai jquery index d ts cannot find name jqueryxhr node modules types chai jquery index d ts cannot find name jqueryxhr node modules types chai jquery index d ts cannot find name jqueryxhr node modules types chai jquery index d ts cannot find name jquerycallback node modules types chai jquery index d ts cannot find name jquerypromise node modules types chai jquery index d ts cannot find name jquerypromise node modules types chai jquery index d ts cannot find name jquerydeferred node modules types chai jquery index d ts cannot find name jquerydeferred node modules types chai jquery index d ts cannot find name jqueryeventconstructor node modules types chai jquery index d ts cannot find name jquerysupport node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryxhr node modules types chai jquery index d ts cannot find name jqueryajaxsettings node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryxhr node modules types chai jquery index d ts cannot find name jqueryajaxsettings node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryajaxsettings node modules types chai jquery index d ts cannot find name jqueryserializearrayelement node modules types chai jquery index d ts cannot find name jquerycoordinates node modules types chai jquery index d ts cannot find name jquerycoordinates node modules types chai jquery index d ts cannot find name jquerycoordinates node modules types chai jquery index d ts cannot find name jquerycoordinates node modules types chai jquery index d ts cannot find name jquerycoordinates node modules types chai jquery index d ts cannot find name jquerypromise node modules types chai jquery index d ts cannot find name jqueryanimationoptions node modules types chai jquery index d ts cannot find name jqueryanimationoptions node modules types chai jquery index d ts cannot find name jqueryanimationoptions node modules types chai jquery index d ts cannot find name jqueryanimationoptions node modules types chai jquery index d ts cannot find name jqueryanimationoptions node modules types chai jquery index d ts cannot find name jqueryanimationoptions node modules types chai jquery index d ts cannot find name jqueryanimationoptions node modules types chai jquery index d ts cannot find name jqueryanimationoptions node modules types chai jquery index d ts cannot find name jqueryanimationoptions node modules types chai jquery index d ts cannot find name jqueryanimationoptions node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jquerykeyeventobject node modules types chai jquery index d ts cannot find name jquerykeyeventobject node modules types chai jquery index d ts cannot find name jquerykeyeventobject node modules types chai jquery index d ts cannot find name jquerykeyeventobject node modules types chai jquery index d ts cannot find name jquerykeyeventobject node modules types chai jquery index d ts cannot find name jquerykeyeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jquerymouseeventobject node modules types chai jquery index d ts cannot find name jquerymouseeventobject node modules types chai jquery index d ts cannot find name jquerymouseeventobject node modules types chai jquery index d ts cannot find name jquerymouseeventobject node modules types chai jquery index d ts cannot find name jquerymouseeventobject node modules types chai jquery index d ts cannot find name jquerymouseeventobject node modules types chai jquery index d ts cannot find name jquerymouseeventobject node modules types chai jquery index d ts cannot find name jquerymouseeventobject node modules types chai jquery index d ts cannot find name jquerymouseeventobject node modules types chai jquery index d ts cannot find name jquerymouseeventobject node modules types chai jquery index d ts cannot find name jquerymouseeventobject node modules types chai jquery index d ts cannot find name jquerymouseeventobject node modules types chai jquery index d ts cannot find name jquerymouseeventobject node modules types chai jquery index d ts cannot find name jquerymouseeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject node modules types chai jquery index d ts cannot find name jqueryeventobject at handle home flotwig src cypress cypress npm webpack preprocessor dist index js at finalcallback home flotwig src cypress cypress npm webpack preprocessor node modules webpack lib compiler js at home flotwig src cypress cypress npm webpack preprocessor node modules webpack lib compiler js at asyncserieshook eval eval at create home flotwig src cypress cypress node modules tapable lib hookcodefactory js at asyncserieshook lazycompilehook home flotwig src cypress cypress node modules tapable lib hook js at home flotwig src cypress cypress npm webpack preprocessor node modules webpack lib compiler js at compiler emitrecords home flotwig src cypress cypress npm webpack preprocessor node modules webpack lib compiler js at home flotwig src cypress cypress npm webpack preprocessor node modules webpack lib compiler js at home flotwig src cypress cypress npm webpack preprocessor node modules webpack lib compiler js at asyncserieshook eval eval at create home flotwig src cypress cypress node modules tapable lib hookcodefactory js at asyncserieshook lazycompilehook home flotwig src cypress cypress node modules tapable lib hook js at home flotwig src cypress cypress npm webpack preprocessor node modules webpack lib compiler js at home flotwig src cypress cypress node modules neo async async js at done home flotwig src cypress cypress node modules neo async async js at asyncserieshook eval eval at create home flotwig src cypress cypress node modules tapable lib hookcodefactory js at asyncserieshook lazycompilehook home flotwig src cypress cypress node modules tapable lib hook js at home flotwig src cypress cypress npm webpack preprocessor node modules webpack lib compiler js at home flotwig src cypress cypress packages server node modules graceful fs graceful fs js at home flotwig src cypress cypress node modules graceful fs graceful fs js at home flotwig src cypress cypress packages server node modules graceful fs graceful fs js at fsreqcallback oncomplete fs js this occurred while cypress was compiling and bundling your test code this is usually caused by a missing file or dependency a syntax error in the file or one of its dependencies fix the error in your code and re run your tests results ┌────────────────────────────────────────────────────────────────────────────────────────────────┐ │ tests │ │ passing │ │ failing │ │ pending │ │ skipped │ │ screenshots │ │ video true │ │ duration seconds │ │ spec ran failing spec ts │ └────────────────────────────────────────────────────────────────────────────────────────────────┘ video started processing compressing to crf finished processing xxx xxx xxx cypress videos failing spec ts seconds run finished spec tests passing failing pending skipped ┌────────────────────────────────────────────────────────────────────────────────────────────────┐ │ ✖ failing spec ts │ └────────────────────────────────────────────────────────────────────────────────────────────────┘ ✖ of failed
| 1
|
17,899
| 23,873,280,345
|
IssuesEvent
|
2022-09-07 16:32:12
|
DSpace/dspace-angular
|
https://api.github.com/repos/DSpace/dspace-angular
|
closed
|
Addition of button to delete a single process
|
bug high priority e/16 tools:processes
|
Buttons on the UI side should be added to cancel single completed or failed processes.
We are interested in this functionality and could implement it ourselves.
|
1.0
|
Addition of button to delete a single process - Buttons on the UI side should be added to cancel single completed or failed processes.
We are interested in this functionality and could implement it ourselves.
|
process
|
addition of button to delete a single process buttons on the ui side should be added to cancel single completed or failed processes we are interested in this functionality and could implement it ourselves
| 1
|
134,717
| 18,499,133,117
|
IssuesEvent
|
2021-10-19 12:02:11
|
elastic/kibana
|
https://api.github.com/repos/elastic/kibana
|
opened
|
[Security Solution] Horizontal lines are not getting upto the whole data shown in table.
|
bug triage_needed Team: SecuritySolution
|
**Describe the bug**
Horizontal lines are not getting upto the whole data shown in table.
**Build Details:**
```
Version:7.16.0 SNAPSHOT
Build: 45316
COMMIT: f002f58fd6cd35f8ecf97f5e64d1f836d96c51e5
```
**Browser Details:**
N/A
**Preconditions**
1. Kibana should be running.
2. Agent should be installed
3. Alerts should be created
**Steps to Reproduce**
1. Navigate to Alert tab.
2. Click on view details of any alert present.
3. Click on the table tab.
4. Scroll the horizontal bar.
5. Observe that Horizontal lines are not getting upto the whole data shown in table
**Notes**
"can you confirm are we going to add the horizontal scroll bar on table view as earlier in 7.15.1 we dont have it "
**Actual Result**
The Horizontal lines under the data present on table are not present upto the whole data.
**Expected Result**
The Horizontal lines should be their for the whole data visible on table
**Screen-Shots**
Build: 7.16.0
Build: 7.15.1
|
True
|
[Security Solution] Horizontal lines are not getting upto the whole data shown in table. - **Describe the bug**
Horizontal lines are not getting upto the whole data shown in table.
**Build Details:**
```
Version:7.16.0 SNAPSHOT
Build: 45316
COMMIT: f002f58fd6cd35f8ecf97f5e64d1f836d96c51e5
```
**Browser Details:**
N/A
**Preconditions**
1. Kibana should be running.
2. Agent should be installed
3. Alerts should be created
**Steps to Reproduce**
1. Navigate to Alert tab.
2. Click on view details of any alert present.
3. Click on the table tab.
4. Scroll the horizontal bar.
5. Observe that Horizontal lines are not getting upto the whole data shown in table
**Notes**
"can you confirm are we going to add the horizontal scroll bar on table view as earlier in 7.15.1 we dont have it "
**Actual Result**
The Horizontal lines under the data present on table are not present upto the whole data.
**Expected Result**
The Horizontal lines should be their for the whole data visible on table
**Screen-Shots**
Build: 7.16.0
Build: 7.15.1
|
non_process
|
horizontal lines are not getting upto the whole data shown in table describe the bug horizontal lines are not getting upto the whole data shown in table build details version snapshot build commit browser details n a preconditions kibana should be running agent should be installed alerts should be created steps to reproduce navigate to alert tab click on view details of any alert present click on the table tab scroll the horizontal bar observe that horizontal lines are not getting upto the whole data shown in table notes can you confirm are we going to add the horizontal scroll bar on table view as earlier in we dont have it actual result the horizontal lines under the data present on table are not present upto the whole data expected result the horizontal lines should be their for the whole data visible on table screen shots build build
| 0
|
398,839
| 11,742,414,091
|
IssuesEvent
|
2020-03-12 00:42:09
|
thaliawww/concrexit
|
https://api.github.com/repos/thaliawww/concrexit
|
closed
|
Add filter to committee membership admin for active memberships
|
easy and fun feature priority: low
|
In GitLab by @se-bastiaan on May 24, 2018, 10:29
### One-sentence description
Add filter to committee membership admin for active memberships
### Desired behaviour
Have the ability to filter between active, non-active and all committee memberships. (Active = no end date)
|
1.0
|
Add filter to committee membership admin for active memberships - In GitLab by @se-bastiaan on May 24, 2018, 10:29
### One-sentence description
Add filter to committee membership admin for active memberships
### Desired behaviour
Have the ability to filter between active, non-active and all committee memberships. (Active = no end date)
|
non_process
|
add filter to committee membership admin for active memberships in gitlab by se bastiaan on may one sentence description add filter to committee membership admin for active memberships desired behaviour have the ability to filter between active non active and all committee memberships active no end date
| 0
|
78,553
| 22,303,385,093
|
IssuesEvent
|
2022-06-13 10:47:01
|
cgeo/cgeo
|
https://api.github.com/repos/cgeo/cgeo
|
closed
|
CI needs active JDK11 for compileSdkVersion 31
|
Bug CI server / Build tools
|
### Describe your problem!
log on CI:
~~~
11:03:16 > Task :main:compileBasicNightlyJavaWithJavac
11:03:16 An exception has occurred in the compiler (1.8.0_101). Please file a bug against the Java compiler via the Java bug reporting page (http://bugreport.java.com/) after checking the Bug Database (http://bugs.java.com/) for duplicates. Include your program and the following diagnostic in your report. Thank you.
11:03:16 java.lang.AssertionError: annotationType(): unrecognized Attribute name MODULE (class com.sun.tools.javac.util.UnsharedNameTable$NameImpl)
~~~
This is a result of switching to `compileSdkVersion 31` in #13136 .
Seee e.g. https://stackoverflow.com/questions/68344424/unrecognized-attribute-name-module-class-com-sun-tools-javac-util-sharednametab .
We have to switch to JDK11 also for the Build.
### How to reproduce?
see https://ci.cgeo.org/job/cgeo%20nightly/2694/consoleFull#-109812861545fc375f-a63e-468b-8450-76255356fdf9
### Actual result after these steps?
_No response_
### Expected result after these steps?
_No response_
### Reproducible
Yes
### c:geo Version
2022.06.13-NB2
### System information
_No response_
### Additional Information
_No response_
|
1.0
|
CI needs active JDK11 for compileSdkVersion 31 - ### Describe your problem!
log on CI:
~~~
11:03:16 > Task :main:compileBasicNightlyJavaWithJavac
11:03:16 An exception has occurred in the compiler (1.8.0_101). Please file a bug against the Java compiler via the Java bug reporting page (http://bugreport.java.com/) after checking the Bug Database (http://bugs.java.com/) for duplicates. Include your program and the following diagnostic in your report. Thank you.
11:03:16 java.lang.AssertionError: annotationType(): unrecognized Attribute name MODULE (class com.sun.tools.javac.util.UnsharedNameTable$NameImpl)
~~~
This is a result of switching to `compileSdkVersion 31` in #13136 .
Seee e.g. https://stackoverflow.com/questions/68344424/unrecognized-attribute-name-module-class-com-sun-tools-javac-util-sharednametab .
We have to switch to JDK11 also for the Build.
### How to reproduce?
see https://ci.cgeo.org/job/cgeo%20nightly/2694/consoleFull#-109812861545fc375f-a63e-468b-8450-76255356fdf9
### Actual result after these steps?
_No response_
### Expected result after these steps?
_No response_
### Reproducible
Yes
### c:geo Version
2022.06.13-NB2
### System information
_No response_
### Additional Information
_No response_
|
non_process
|
ci needs active for compilesdkversion describe your problem log on ci task main compilebasicnightlyjavawithjavac an exception has occurred in the compiler please file a bug against the java compiler via the java bug reporting page after checking the bug database for duplicates include your program and the following diagnostic in your report thank you java lang assertionerror annotationtype unrecognized attribute name module class com sun tools javac util unsharednametable nameimpl this is a result of switching to compilesdkversion in seee e g we have to switch to also for the build how to reproduce see actual result after these steps no response expected result after these steps no response reproducible yes c geo version system information no response additional information no response
| 0
|
22,618
| 31,842,882,691
|
IssuesEvent
|
2023-09-14 17:36:53
|
USGS-WiM/StreamStats
|
https://api.github.com/repos/USGS-WiM/StreamStats
|
reopened
|
Disable BP on TestWeb
|
Batch Processor
|
We are not going to allow batch processing on test. If the host url is test.streamstats we should disable the BP button.
|
1.0
|
Disable BP on TestWeb - We are not going to allow batch processing on test. If the host url is test.streamstats we should disable the BP button.
|
process
|
disable bp on testweb we are not going to allow batch processing on test if the host url is test streamstats we should disable the bp button
| 1
|
2,798
| 5,729,132,195
|
IssuesEvent
|
2017-04-21 04:34:04
|
nodejs/node
|
https://api.github.com/repos/nodejs/node
|
opened
|
investigate flaky sequential/test-benchmark-child-process on Windows
|
benchmark child_process test windows
|
* **Version**: v8.0.0-pre
* **Platform**: win2008r2
* **Subsystem**: test
<!-- Enter your issue details below this comment. -->
`sequential/test-benchmark-child-process ` is still failing sometimes flaky on Windows in CI. I'll open a PR to mark it as flaky. This issue is for trying to locate the problem and a solution.
When the test succeeds, it seems to take just a few seconds.
https://ci.nodejs.org/job/node-test-binary-windows/RUN_SUBSET=3,VS_VERSION=vs2015,label=win2008r2/7865/console
```console
ok 356 sequential/test-benchmark-child-process
---
duration_ms: 1.764
```
When it fails, it's a timeout.
https://ci.nodejs.org/job/node-test-binary-windows/7867/RUN_SUBSET=3,VS_VERSION=vs2015,label=win2008r2/console
```console
not ok 356 sequential/test-benchmark-child-process
---
duration_ms: 60.70
severity: fail
stack: |-
timeout
```
This would suggest a race condition or something else causing a child process to hang or something. And that might be the cause. But...
Interestingly, a stress test where the five benchmarks that this test calls were all split out into individual tests, succeeded but each test took around 30 seconds to run. Wha??!! I know! (Only other change in those tests is the `dur` option for the benchmarks was increased from 0 to 0.1.)
https://ci.nodejs.org/job/node-stress-single-test/1161/nodes=win2016/console:
```console
ok 1 sequential/test-benchmark-child-process-exec-stdout
---
duration_ms: 3.158
...
ok 2 sequential/test-benchmark-child-process-params
---
duration_ms: 36.735
...
ok 3 sequential/test-benchmark-child-process-read-ipc
---
duration_ms: 30.116
...
ok 4 sequential/test-benchmark-child-process-read
---
duration_ms: 31.844
...
ok 5 sequential/test-benchmark-child-process-spawn-echo
---
duration_ms: 31.661
```
So I'm not sure what's going on here. Maybe it can be worked out by someone more comfortable testing and debugging on Windows or someone more deeply familiar with child_process and/or our benchmarking code. @nodejs/platform-windows @nodejs/benchmarking @mscdex @cjihrig @bnoordhuis @nodejs/testing
|
1.0
|
investigate flaky sequential/test-benchmark-child-process on Windows - * **Version**: v8.0.0-pre
* **Platform**: win2008r2
* **Subsystem**: test
<!-- Enter your issue details below this comment. -->
`sequential/test-benchmark-child-process ` is still failing sometimes flaky on Windows in CI. I'll open a PR to mark it as flaky. This issue is for trying to locate the problem and a solution.
When the test succeeds, it seems to take just a few seconds.
https://ci.nodejs.org/job/node-test-binary-windows/RUN_SUBSET=3,VS_VERSION=vs2015,label=win2008r2/7865/console
```console
ok 356 sequential/test-benchmark-child-process
---
duration_ms: 1.764
```
When it fails, it's a timeout.
https://ci.nodejs.org/job/node-test-binary-windows/7867/RUN_SUBSET=3,VS_VERSION=vs2015,label=win2008r2/console
```console
not ok 356 sequential/test-benchmark-child-process
---
duration_ms: 60.70
severity: fail
stack: |-
timeout
```
This would suggest a race condition or something else causing a child process to hang or something. And that might be the cause. But...
Interestingly, a stress test where the five benchmarks that this test calls were all split out into individual tests, succeeded but each test took around 30 seconds to run. Wha??!! I know! (Only other change in those tests is the `dur` option for the benchmarks was increased from 0 to 0.1.)
https://ci.nodejs.org/job/node-stress-single-test/1161/nodes=win2016/console:
```console
ok 1 sequential/test-benchmark-child-process-exec-stdout
---
duration_ms: 3.158
...
ok 2 sequential/test-benchmark-child-process-params
---
duration_ms: 36.735
...
ok 3 sequential/test-benchmark-child-process-read-ipc
---
duration_ms: 30.116
...
ok 4 sequential/test-benchmark-child-process-read
---
duration_ms: 31.844
...
ok 5 sequential/test-benchmark-child-process-spawn-echo
---
duration_ms: 31.661
```
So I'm not sure what's going on here. Maybe it can be worked out by someone more comfortable testing and debugging on Windows or someone more deeply familiar with child_process and/or our benchmarking code. @nodejs/platform-windows @nodejs/benchmarking @mscdex @cjihrig @bnoordhuis @nodejs/testing
|
process
|
investigate flaky sequential test benchmark child process on windows version pre platform subsystem test sequential test benchmark child process is still failing sometimes flaky on windows in ci i ll open a pr to mark it as flaky this issue is for trying to locate the problem and a solution when the test succeeds it seems to take just a few seconds console ok sequential test benchmark child process duration ms when it fails it s a timeout console not ok sequential test benchmark child process duration ms severity fail stack timeout this would suggest a race condition or something else causing a child process to hang or something and that might be the cause but interestingly a stress test where the five benchmarks that this test calls were all split out into individual tests succeeded but each test took around seconds to run wha i know only other change in those tests is the dur option for the benchmarks was increased from to console ok sequential test benchmark child process exec stdout duration ms ok sequential test benchmark child process params duration ms ok sequential test benchmark child process read ipc duration ms ok sequential test benchmark child process read duration ms ok sequential test benchmark child process spawn echo duration ms so i m not sure what s going on here maybe it can be worked out by someone more comfortable testing and debugging on windows or someone more deeply familiar with child process and or our benchmarking code nodejs platform windows nodejs benchmarking mscdex cjihrig bnoordhuis nodejs testing
| 1
|
20,645
| 27,322,999,767
|
IssuesEvent
|
2023-02-24 21:52:15
|
googleapis/google-api-java-client
|
https://api.github.com/repos/googleapis/google-api-java-client
|
opened
|
Remove maven version workaround in CI/Windows check
|
priority: p2 type: process
|
This is to follow-up on the workaround added in https://github.com/googleapis/google-api-java-client/pull/2269, which is for a regression specific in Maven 3.9.0. This workaround can be reverted once a newer version of maven is released with fix.
|
1.0
|
Remove maven version workaround in CI/Windows check - This is to follow-up on the workaround added in https://github.com/googleapis/google-api-java-client/pull/2269, which is for a regression specific in Maven 3.9.0. This workaround can be reverted once a newer version of maven is released with fix.
|
process
|
remove maven version workaround in ci windows check this is to follow up on the workaround added in which is for a regression specific in maven this workaround can be reverted once a newer version of maven is released with fix
| 1
|
88,310
| 25,371,150,939
|
IssuesEvent
|
2022-11-21 10:39:04
|
godotengine/godot-cpp
|
https://api.github.com/repos/godotengine/godot-cpp
|
closed
|
Release builds are linking with debug libraries
|
bug platform:windows buildsystem
|
Since updating for Godot 4 beta 4 support, users have been reporting an issue where my builds produced using `template_release` are linked with debug runtime libraries: https://github.com/codecat/godot-tbloader/issues/36
This might be related to #867, but I don't really know enough about SCons to properly debug this. I believe my SCons file is properly configured though, so this might be a bug in godot-cpp?
|
1.0
|
Release builds are linking with debug libraries - Since updating for Godot 4 beta 4 support, users have been reporting an issue where my builds produced using `template_release` are linked with debug runtime libraries: https://github.com/codecat/godot-tbloader/issues/36
This might be related to #867, but I don't really know enough about SCons to properly debug this. I believe my SCons file is properly configured though, so this might be a bug in godot-cpp?
|
non_process
|
release builds are linking with debug libraries since updating for godot beta support users have been reporting an issue where my builds produced using template release are linked with debug runtime libraries this might be related to but i don t really know enough about scons to properly debug this i believe my scons file is properly configured though so this might be a bug in godot cpp
| 0
|
128,007
| 5,042,447,826
|
IssuesEvent
|
2016-12-19 14:01:38
|
Signbank/NGT-signbank
|
https://api.github.com/repos/Signbank/NGT-signbank
|
closed
|
URGENT: do not show all signs to non-logged in users
|
enhancement top priority
|
* Non-logged in users have a menu item Signs > Show all signs, but this should only show signs with "In dictionary = true"!! Now it shows all signs
* The search function for public users is already correctly restricting itself to the dictionary signs
|
1.0
|
URGENT: do not show all signs to non-logged in users - * Non-logged in users have a menu item Signs > Show all signs, but this should only show signs with "In dictionary = true"!! Now it shows all signs
* The search function for public users is already correctly restricting itself to the dictionary signs
|
non_process
|
urgent do not show all signs to non logged in users non logged in users have a menu item signs show all signs but this should only show signs with in dictionary true now it shows all signs the search function for public users is already correctly restricting itself to the dictionary signs
| 0
|
11,466
| 14,289,679,759
|
IssuesEvent
|
2020-11-23 19:38:51
|
googleapis/nodejs-phishing-protection
|
https://api.github.com/repos/googleapis/nodejs-phishing-protection
|
opened
|
wrong test configuration
|
type: process
|
We seem to be applying the wrong test configuration [here](https://github.com/googleapis/nodejs-phishing-protection/blob/master/.github/sync-repo-settings.yaml#L8).
I think we just need to remove ` (pull_request)` (_we should be able to just copy over the config from repo-automation-bots?_).
|
1.0
|
wrong test configuration - We seem to be applying the wrong test configuration [here](https://github.com/googleapis/nodejs-phishing-protection/blob/master/.github/sync-repo-settings.yaml#L8).
I think we just need to remove ` (pull_request)` (_we should be able to just copy over the config from repo-automation-bots?_).
|
process
|
wrong test configuration we seem to be applying the wrong test configuration i think we just need to remove pull request we should be able to just copy over the config from repo automation bots
| 1
|
12,996
| 15,359,379,847
|
IssuesEvent
|
2021-03-01 15:47:38
|
edwardsmarc/CASFRI
|
https://api.github.com/repos/edwardsmarc/CASFRI
|
opened
|
Automate validation of historical database
|
enhancement high post-translation process
|
- Create some constraints ensuring that generated polygon never overlap in time (sum of all the valid years for a polygon should = 2030 - 1930 + 1)
- There should not be any spatial overlaps in selected years
|
1.0
|
Automate validation of historical database - - Create some constraints ensuring that generated polygon never overlap in time (sum of all the valid years for a polygon should = 2030 - 1930 + 1)
- There should not be any spatial overlaps in selected years
|
process
|
automate validation of historical database create some constraints ensuring that generated polygon never overlap in time sum of all the valid years for a polygon should there should not be any spatial overlaps in selected years
| 1
|
41,430
| 2,869,005,162
|
IssuesEvent
|
2015-06-05 22:31:25
|
dart-lang/sdk
|
https://api.github.com/repos/dart-lang/sdk
|
closed
|
Support SASS style mixins for cross browser styling.
|
Area-Pkg Pkg-Csslib Priority-Unassigned Triaged Type-Enhancement
|
Example define mixin border-radius:
@mixin border-radius($radius) {
-moz-border-radius: $radius;
-webkit-border-radius: $radius;
-ms-border-radius: $radius;
border-radius: $radius;
}
Usage of mixin:
.round-button {
background: black;
color: white;
padding: 20px;
@include border-radius(5px);
}
CSS generated:
.round-button {
background: black;
color: white;
padding: 20px;
-moz-border-radius: 5px;
-webkit-border-radius: 5px;
-ms-border-radius: 5px;
-o-border-radius: 5px;
-khtml-border-radius: 5px;
border-radius: 5px;
}
|
1.0
|
Support SASS style mixins for cross browser styling. - Example define mixin border-radius:
@mixin border-radius($radius) {
-moz-border-radius: $radius;
-webkit-border-radius: $radius;
-ms-border-radius: $radius;
border-radius: $radius;
}
Usage of mixin:
.round-button {
background: black;
color: white;
padding: 20px;
@include border-radius(5px);
}
CSS generated:
.round-button {
background: black;
color: white;
padding: 20px;
-moz-border-radius: 5px;
-webkit-border-radius: 5px;
-ms-border-radius: 5px;
-o-border-radius: 5px;
-khtml-border-radius: 5px;
border-radius: 5px;
}
|
non_process
|
support sass style mixins for cross browser styling example define mixin border radius mixin border radius radius moz border radius radius webkit border radius radius ms border radius radius border radius radius usage of mixin round button background black color white padding include border radius css generated round button background black color white padding moz border radius webkit border radius ms border radius o border radius khtml border radius border radius
| 0
|
2,939
| 8,584,028,313
|
IssuesEvent
|
2018-11-13 21:29:08
|
poanetwork/blockscout
|
https://api.github.com/repos/poanetwork/blockscout
|
closed
|
Fix Parity Internal Transactions
|
bug :bug: client: parity in progress priority: high severity: 3 team: architecture
|
The `input` value is not currently being imported by the internal transactions fetcher. We should also check for other fields that may not be validated on import.
### Environment
* Client: Parity
* Fetcher: Internal Transactions
|
1.0
|
Fix Parity Internal Transactions - The `input` value is not currently being imported by the internal transactions fetcher. We should also check for other fields that may not be validated on import.
### Environment
* Client: Parity
* Fetcher: Internal Transactions
|
non_process
|
fix parity internal transactions the input value is not currently being imported by the internal transactions fetcher we should also check for other fields that may not be validated on import environment client parity fetcher internal transactions
| 0
|
52,805
| 6,278,709,165
|
IssuesEvent
|
2017-07-18 14:52:27
|
dwyl/best-evidence
|
https://api.github.com/repos/dwyl/best-evidence
|
closed
|
Transfer Heroku App
|
please-test priority-2 T1h technical
|
We have at the moment an heroku app that I have created during my spike "voice recognition" #2 #3
This application is currently hosted on my dwyl account so we need to transfer it to the new heroku account so that any users with the credentials can access the application configuration
|
1.0
|
Transfer Heroku App - We have at the moment an heroku app that I have created during my spike "voice recognition" #2 #3
This application is currently hosted on my dwyl account so we need to transfer it to the new heroku account so that any users with the credentials can access the application configuration
|
non_process
|
transfer heroku app we have at the moment an heroku app that i have created during my spike voice recognition this application is currently hosted on my dwyl account so we need to transfer it to the new heroku account so that any users with the credentials can access the application configuration
| 0
|
17,110
| 22,634,596,912
|
IssuesEvent
|
2022-06-30 17:37:48
|
hashgraph/hedera-json-rpc-relay
|
https://api.github.com/repos/hashgraph/hedera-json-rpc-relay
|
closed
|
Update the acceptance test for eth_gasPrice
|
enhancement limechain P3 process
|
### Problem
The current released version of mirror-node(`0.57.2`) does not include the endpoint for retrieving gas fees `/network/fees`, so the acceptance test is temporary disabled.
### Solution
Enable the acceptance test for `eth_gasPrice` once a new version of mirror-node is released and the endpoint `/network/fees` exists.
### Alternatives
_No response_
|
1.0
|
Update the acceptance test for eth_gasPrice - ### Problem
The current released version of mirror-node(`0.57.2`) does not include the endpoint for retrieving gas fees `/network/fees`, so the acceptance test is temporary disabled.
### Solution
Enable the acceptance test for `eth_gasPrice` once a new version of mirror-node is released and the endpoint `/network/fees` exists.
### Alternatives
_No response_
|
process
|
update the acceptance test for eth gasprice problem the current released version of mirror node does not include the endpoint for retrieving gas fees network fees so the acceptance test is temporary disabled solution enable the acceptance test for eth gasprice once a new version of mirror node is released and the endpoint network fees exists alternatives no response
| 1
|
19,273
| 25,463,967,391
|
IssuesEvent
|
2022-11-25 00:37:29
|
devssa/onde-codar-em-salvador
|
https://api.github.com/repos/devssa/onde-codar-em-salvador
|
closed
|
Analista de Requisitos na [WEX]
|
SALVADOR EFETIVO(CLT) DESENVOLVIMENTO DE SOFTWARE SCRUM AGILE REQUISITOS PROCESSOS Stale
|
<!--
==================================================
POR FAVOR, SÓ POSTE SE A VAGA FOR PARA SALVADOR E CIDADES VIZINHAS!
Use: "Desenvolvedor Front-end" ao invés de
"Front-End Developer" \o/
Exemplo: `[JAVASCRIPT] [MYSQL] [NODE.JS] Desenvolvedor Front-End na [NOME DA EMPRESA]`
==================================================
-->
## Analista de requisitos
A WEX líder global em soluções de pagamentos corporativos busca Analista de Requisitos para atuação na área da Tecnologia (GDC) em Salvador.
#### Descrição das principais atividades:
- Gerenciar os Backlogs de produtos priorizados;
- Analisar e documentar necessidades de usuários (Internos e externos);
- Resolver problemas dos demandantes, implementando técnicas e esclarecimento de dúvidas;
- Garantir a qualidade dos códigos testes para a àrea de Qualidade;
- Utilizar metodologias agéis afim de garantir consistência e prazo de entrega.
## Local
Salvador - Bahia
## Requisitos
**Obrigatórios:**
- Ensino superior completo em Análise e Desenvolvimento de Sistemas, Ciências da Computação, Sistemas de Informação, Negócios ou áreas correlatas;
- No mínimo cinco anos de experiência na função de Analista de Requisitos;
- Inglês avançado/fluente - MANDATÓRIO;
- Conhecimento em metodologias ágeis - SCRUM e Waterfall SDLC;
- Experiência em trabalhar com diferentes interlocutores, seja em áreas internas ou externas.
#### Perfil comportamental esperado:
- Pensamento analítico;
- Prezar pela qualidade dos produtos.
- Autonomia com responsabilidade;
- Senso de urgência e importância;
- Boa comunicação;
- Colaboração.
## Contratação
CLT(Efetivo)
## WEX
Líder global em soluções para meios de pagamento corporativo, atendemos mundialmente mais de 350 mil empresas, com movimentação anual superior a US$ 40 bilhões nos segmentos de Benefícios, Frete, Viagem e Saúde. Com mais de 30 anos de experiência, temos as ferramentas que ajudam milhares de empresas a ter mais controle de seus negócios, redução de custos, mais eficiência, agilidade operacional e satisfação para você e seus colaboradores. Além da facilidade de oferecer cartões com a bandeira MasterCard, aceito em mais de 1.8 milhão de estabelecimentos credenciados, nossos produtos também auxiliam seus colaboradores a terem mais controle sobre seus gastos no dia a dia, por meio de serviços de pagamento de contas, recarga de celular, saque emergencial entre outros. Nosso crescimento se dá por nossa paixão pela inovação contínua e por estarmos sempre em busca de um nível de serviços incomparável em nosso segmento. E claro, por termos parceiros como você.
## Como se candidatar
https://www.linkedin.com/jobs/view/1308568542/?eBP=NotAvailableFromVoyagerAPI&recommendedFlavor=SCHOOL_RECRUIT&refId=7cccdde8-07b8-4dd3-b9ff-a60449d27674&trk=d_flagship3_search_srp_jobs
|
1.0
|
Analista de Requisitos na [WEX] - <!--
==================================================
POR FAVOR, SÓ POSTE SE A VAGA FOR PARA SALVADOR E CIDADES VIZINHAS!
Use: "Desenvolvedor Front-end" ao invés de
"Front-End Developer" \o/
Exemplo: `[JAVASCRIPT] [MYSQL] [NODE.JS] Desenvolvedor Front-End na [NOME DA EMPRESA]`
==================================================
-->
## Analista de requisitos
A WEX líder global em soluções de pagamentos corporativos busca Analista de Requisitos para atuação na área da Tecnologia (GDC) em Salvador.
#### Descrição das principais atividades:
- Gerenciar os Backlogs de produtos priorizados;
- Analisar e documentar necessidades de usuários (Internos e externos);
- Resolver problemas dos demandantes, implementando técnicas e esclarecimento de dúvidas;
- Garantir a qualidade dos códigos testes para a àrea de Qualidade;
- Utilizar metodologias agéis afim de garantir consistência e prazo de entrega.
## Local
Salvador - Bahia
## Requisitos
**Obrigatórios:**
- Ensino superior completo em Análise e Desenvolvimento de Sistemas, Ciências da Computação, Sistemas de Informação, Negócios ou áreas correlatas;
- No mínimo cinco anos de experiência na função de Analista de Requisitos;
- Inglês avançado/fluente - MANDATÓRIO;
- Conhecimento em metodologias ágeis - SCRUM e Waterfall SDLC;
- Experiência em trabalhar com diferentes interlocutores, seja em áreas internas ou externas.
#### Perfil comportamental esperado:
- Pensamento analítico;
- Prezar pela qualidade dos produtos.
- Autonomia com responsabilidade;
- Senso de urgência e importância;
- Boa comunicação;
- Colaboração.
## Contratação
CLT(Efetivo)
## WEX
Líder global em soluções para meios de pagamento corporativo, atendemos mundialmente mais de 350 mil empresas, com movimentação anual superior a US$ 40 bilhões nos segmentos de Benefícios, Frete, Viagem e Saúde. Com mais de 30 anos de experiência, temos as ferramentas que ajudam milhares de empresas a ter mais controle de seus negócios, redução de custos, mais eficiência, agilidade operacional e satisfação para você e seus colaboradores. Além da facilidade de oferecer cartões com a bandeira MasterCard, aceito em mais de 1.8 milhão de estabelecimentos credenciados, nossos produtos também auxiliam seus colaboradores a terem mais controle sobre seus gastos no dia a dia, por meio de serviços de pagamento de contas, recarga de celular, saque emergencial entre outros. Nosso crescimento se dá por nossa paixão pela inovação contínua e por estarmos sempre em busca de um nível de serviços incomparável em nosso segmento. E claro, por termos parceiros como você.
## Como se candidatar
https://www.linkedin.com/jobs/view/1308568542/?eBP=NotAvailableFromVoyagerAPI&recommendedFlavor=SCHOOL_RECRUIT&refId=7cccdde8-07b8-4dd3-b9ff-a60449d27674&trk=d_flagship3_search_srp_jobs
|
process
|
analista de requisitos na por favor só poste se a vaga for para salvador e cidades vizinhas use desenvolvedor front end ao invés de front end developer o exemplo desenvolvedor front end na analista de requisitos a wex líder global em soluções de pagamentos corporativos busca analista de requisitos para atuação na área da tecnologia gdc em salvador descrição das principais atividades gerenciar os backlogs de produtos priorizados analisar e documentar necessidades de usuários internos e externos resolver problemas dos demandantes implementando técnicas e esclarecimento de dúvidas garantir a qualidade dos códigos testes para a àrea de qualidade utilizar metodologias agéis afim de garantir consistência e prazo de entrega local salvador bahia requisitos obrigatórios ensino superior completo em análise e desenvolvimento de sistemas ciências da computação sistemas de informação negócios ou áreas correlatas no mínimo cinco anos de experiência na função de analista de requisitos inglês avançado fluente mandatório conhecimento em metodologias ágeis scrum e waterfall sdlc experiência em trabalhar com diferentes interlocutores seja em áreas internas ou externas perfil comportamental esperado pensamento analítico prezar pela qualidade dos produtos autonomia com responsabilidade senso de urgência e importância boa comunicação colaboração contratação clt efetivo wex líder global em soluções para meios de pagamento corporativo atendemos mundialmente mais de mil empresas com movimentação anual superior a us bilhões nos segmentos de benefícios frete viagem e saúde com mais de anos de experiência temos as ferramentas que ajudam milhares de empresas a ter mais controle de seus negócios redução de custos mais eficiência agilidade operacional e satisfação para você e seus colaboradores além da facilidade de oferecer cartões com a bandeira mastercard aceito em mais de milhão de estabelecimentos credenciados nossos produtos também auxiliam seus colaboradores a terem mais controle sobre seus gastos no dia a dia por meio de serviços de pagamento de contas recarga de celular saque emergencial entre outros nosso crescimento se dá por nossa paixão pela inovação contínua e por estarmos sempre em busca de um nível de serviços incomparável em nosso segmento e claro por termos parceiros como você como se candidatar
| 1
|
12,539
| 14,973,124,737
|
IssuesEvent
|
2021-01-28 00:20:40
|
googleapis/python-pubsub
|
https://api.github.com/repos/googleapis/python-pubsub
|
closed
|
Auto generated code get_distribution method through `DistributionNotFound` error
|
api: pubsub type: process
|
Try statement never executed because of `get_distribution(google-pubsub)`, it should be get_distribution("google-cloud-pubsub",)
https://github.com/googleapis/python-pubsub/blob/6b9eec81ccee81ab93646eaf7652139fc218ed36/google/pubsub_v1/services/publisher/transports/base.py#L34-L37
also found same thing at various places:
https://github.com/googleapis/python-pubsub/blob/6b9eec81ccee81ab93646eaf7652139fc218ed36/google/pubsub_v1/services/subscriber/transports/base.py#L36
https://github.com/googleapis/python-pubsub/blob/6b9eec81ccee81ab93646eaf7652139fc218ed36/google/pubsub_v1/services/publisher/async_client.py#L1093
https://github.com/googleapis/python-pubsub/blob/6b9eec81ccee81ab93646eaf7652139fc218ed36/google/pubsub_v1/services/publisher/client.py#L1199
https://github.com/googleapis/python-pubsub/blob/6b9eec81ccee81ab93646eaf7652139fc218ed36/google/pubsub_v1/services/subscriber/client.py#L1904
|
1.0
|
Auto generated code get_distribution method through `DistributionNotFound` error - Try statement never executed because of `get_distribution(google-pubsub)`, it should be get_distribution("google-cloud-pubsub",)
https://github.com/googleapis/python-pubsub/blob/6b9eec81ccee81ab93646eaf7652139fc218ed36/google/pubsub_v1/services/publisher/transports/base.py#L34-L37
also found same thing at various places:
https://github.com/googleapis/python-pubsub/blob/6b9eec81ccee81ab93646eaf7652139fc218ed36/google/pubsub_v1/services/subscriber/transports/base.py#L36
https://github.com/googleapis/python-pubsub/blob/6b9eec81ccee81ab93646eaf7652139fc218ed36/google/pubsub_v1/services/publisher/async_client.py#L1093
https://github.com/googleapis/python-pubsub/blob/6b9eec81ccee81ab93646eaf7652139fc218ed36/google/pubsub_v1/services/publisher/client.py#L1199
https://github.com/googleapis/python-pubsub/blob/6b9eec81ccee81ab93646eaf7652139fc218ed36/google/pubsub_v1/services/subscriber/client.py#L1904
|
process
|
auto generated code get distribution method through distributionnotfound error try statement never executed because of get distribution google pubsub it should be get distribution google cloud pubsub also found same thing at various places
| 1
|
216,524
| 7,309,047,087
|
IssuesEvent
|
2018-02-28 10:25:35
|
fxi/map-x-mgl
|
https://api.github.com/repos/fxi/map-x-mgl
|
closed
|
Filter values is not populated
|
Fixed Priority 1 bug
|
For views with categorical values, the _"Filter values"_ tool is not populated. This issue makes the filter unusable.
|
1.0
|
Filter values is not populated - For views with categorical values, the _"Filter values"_ tool is not populated. This issue makes the filter unusable.
|
non_process
|
filter values is not populated for views with categorical values the filter values tool is not populated this issue makes the filter unusable
| 0
|
9,219
| 12,255,513,278
|
IssuesEvent
|
2020-05-06 10:19:37
|
qgis/QGIS
|
https://api.github.com/repos/qgis/QGIS
|
closed
|
Cannot use aggregate function in graphical modeller
|
Bug Processing
|
Trying to use the "sum" aggregate function in graphical modeller. Keep getting the error - Cannot use aggregate function in this context. Function runs fine in field calculator outside of model. Using Q3.10 but have tried in other versions and still get same issue.
|
1.0
|
Cannot use aggregate function in graphical modeller - Trying to use the "sum" aggregate function in graphical modeller. Keep getting the error - Cannot use aggregate function in this context. Function runs fine in field calculator outside of model. Using Q3.10 but have tried in other versions and still get same issue.
|
process
|
cannot use aggregate function in graphical modeller trying to use the sum aggregate function in graphical modeller keep getting the error cannot use aggregate function in this context function runs fine in field calculator outside of model using but have tried in other versions and still get same issue
| 1
|
33,930
| 7,302,373,148
|
IssuesEvent
|
2018-02-27 09:30:18
|
auvipy/django-sqlalchemy
|
https://api.github.com/repos/auvipy/django-sqlalchemy
|
closed
|
Adjacency list relationships do not work
|
Priority-Medium Type-Defect auto-migrated
|
```
The setup for adjacency list relationships (self-referential) is different on
SA than for normal Many
to One. The current declarative parts do not handle this properly.
[http://www.sqlalchemy.org/docs/04/mappers.html#advdatamapping_relation_selfrefe
rential_quer]
y
```
Original issue reported on code.google.com by `mtr...@gmail.com` on 10 Apr 2008 at 1:30
|
1.0
|
Adjacency list relationships do not work - ```
The setup for adjacency list relationships (self-referential) is different on
SA than for normal Many
to One. The current declarative parts do not handle this properly.
[http://www.sqlalchemy.org/docs/04/mappers.html#advdatamapping_relation_selfrefe
rential_quer]
y
```
Original issue reported on code.google.com by `mtr...@gmail.com` on 10 Apr 2008 at 1:30
|
non_process
|
adjacency list relationships do not work the setup for adjacency list relationships self referential is different on sa than for normal many to one the current declarative parts do not handle this properly rential quer y original issue reported on code google com by mtr gmail com on apr at
| 0
|
6,027
| 8,837,186,458
|
IssuesEvent
|
2019-01-05 01:40:51
|
nion-software/nionswift
|
https://api.github.com/repos/nion-software/nionswift
|
closed
|
Processing operations should keep float32 if possible.
|
f - processing level - easy priority - critical type - bug
|
Several operations promote data to float64 unnecessarily. Includes external scripts such as AlignZLP or Thickness.
|
1.0
|
Processing operations should keep float32 if possible. - Several operations promote data to float64 unnecessarily. Includes external scripts such as AlignZLP or Thickness.
|
process
|
processing operations should keep if possible several operations promote data to unnecessarily includes external scripts such as alignzlp or thickness
| 1
|
24,326
| 7,477,619,971
|
IssuesEvent
|
2018-04-04 08:54:29
|
zeromq/cppzmq
|
https://api.github.com/repos/zeromq/cppzmq
|
closed
|
build problems
|
Area (build/compilation)
|
I have been able to build libzmq using the libzmq.sln file found in the msvc/vs2017 folder in the directory with visual studio 2017. Now, I'm following the instructions on how to build libzmq as mentioned here since I need cppzmq to use zmq with c++. However, the compilation always return an error every time I run the command "make -j4 install". It shows this error
It also shows an error whenever I try to build cppzmq first. It shows this error
|
1.0
|
build problems - I have been able to build libzmq using the libzmq.sln file found in the msvc/vs2017 folder in the directory with visual studio 2017. Now, I'm following the instructions on how to build libzmq as mentioned here since I need cppzmq to use zmq with c++. However, the compilation always return an error every time I run the command "make -j4 install". It shows this error
It also shows an error whenever I try to build cppzmq first. It shows this error
|
non_process
|
build problems i have been able to build libzmq using the libzmq sln file found in the msvc folder in the directory with visual studio now i m following the instructions on how to build libzmq as mentioned here since i need cppzmq to use zmq with c however the compilation always return an error every time i run the command make install it shows this error it also shows an error whenever i try to build cppzmq first it shows this error
| 0
|
21,236
| 28,355,525,085
|
IssuesEvent
|
2023-04-12 07:01:22
|
metabase/metabase
|
https://api.github.com/repos/metabase/metabase
|
closed
|
[MLv2] Add convenience `changeDirection(query, orderBy)` function
|
.metabase-lib .Team/QueryProcessor :hammer_and_wrench:
|
to flip a given order by from `:asc` to `:desc` , this will be much less work than asking the FE to construct a new order by and call `replace()` or something just to power the behavior when you click the arrow in the UI to change direction.
|
1.0
|
[MLv2] Add convenience `changeDirection(query, orderBy)` function - to flip a given order by from `:asc` to `:desc` , this will be much less work than asking the FE to construct a new order by and call `replace()` or something just to power the behavior when you click the arrow in the UI to change direction.
|
process
|
add convenience changedirection query orderby function to flip a given order by from asc to desc this will be much less work than asking the fe to construct a new order by and call replace or something just to power the behavior when you click the arrow in the ui to change direction
| 1
|
11,538
| 14,427,172,598
|
IssuesEvent
|
2020-12-06 02:21:13
|
cggos/cggos.github.io
|
https://api.github.com/repos/cggos/cggos.github.io
|
opened
|
图像分析之ORB特征 - Gavin Gao's Blog
|
Gitalk image-process-feature-orb
|
https://cggos.github.io/image-process-feature-orb.html
[TOC]Overview Oriented FAST + Rotated BRIEF Feature/Corner Detector FAST方法 – 定位特征点坐标 矩方法 – 特征点方向 非极大值抑制 – 特征点响应值（分数） 图像金字塔 – 特征点具有 尺度不变性Descriptor B...
|
1.0
|
图像分析之ORB特征 - Gavin Gao's Blog - https://cggos.github.io/image-process-feature-orb.html
[TOC]Overview Oriented FAST + Rotated BRIEF Feature/Corner Detector FAST方法 – 定位特征点坐标 矩方法 – 特征点方向 非极大值抑制 – 特征点响应值（分数） 图像金字塔 – 特征点具有 尺度不变性Descriptor B...
|
process
|
图像分析之orb特征 gavin gao s blog overview oriented fast rotated brief feature corner detector fast方法 – 定位特征点坐标 矩方法 – 特征点方向 非极大值抑制 – 特征点响应值（分数） 图像金字塔 – 特征点具有 尺度不变性descriptor b
| 1
|
5,179
| 7,962,111,981
|
IssuesEvent
|
2018-07-13 13:18:43
|
gluster/glusterd2
|
https://api.github.com/repos/gluster/glusterd2
|
opened
|
Consider running tests such as misspell for all PRs
|
easyfix priority: low process-improvement tests
|
There have been multiple PRs over time to fix issues reported by [Go report card](https://goreportcard.com/report/github.com/gluster/glusterd2#golint) service which runs multiple tests such as [ineffassign](https://github.com/gordonklaus/ineffassign) and [misspell](https://github.com/client9/misspell). Instead of merging PRs and fixing these (minor) issues later, it'll be good to have these tests in CI and fail early.
|
1.0
|
Consider running tests such as misspell for all PRs - There have been multiple PRs over time to fix issues reported by [Go report card](https://goreportcard.com/report/github.com/gluster/glusterd2#golint) service which runs multiple tests such as [ineffassign](https://github.com/gordonklaus/ineffassign) and [misspell](https://github.com/client9/misspell). Instead of merging PRs and fixing these (minor) issues later, it'll be good to have these tests in CI and fail early.
|
process
|
consider running tests such as misspell for all prs there have been multiple prs over time to fix issues reported by service which runs multiple tests such as and instead of merging prs and fixing these minor issues later it ll be good to have these tests in ci and fail early
| 1
|
14,565
| 17,689,916,365
|
IssuesEvent
|
2021-08-24 08:41:21
|
ankidroid/Anki-Android
|
https://api.github.com/repos/ankidroid/Anki-Android
|
closed
|
[Bug] Flaky unit tests (including test SchedV2Test:regression_test_preview)
|
Bug Dev Test process
|
```
com.ichi2.libanki.sched.SchedV2Test > regression_test_preview FAILED
java.lang.Exception: Main looper has queued unexecuted runnables. This might be the cause of the test failure. You might need a shadowOf(getMainLooper()).idle() call.
at org.robolectric.android.internal.AndroidTestEnvironment.checkStateAfterTestFailure(AndroidTestEnvironment.java:502)
at org.robolectric.RobolectricTestRunner$HelperTestRunner$1.evaluate(RobolectricTestRunner.java:581)
at org.robolectric.internal.SandboxTestRunner$2.lambda$evaluate$0(SandboxTestRunner.java:263)
at org.robolectric.internal.bytecode.Sandbox.lambda$runOnMainThread$0(Sandbox.java:89)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by:
java.util.NoSuchElementException
at java.util.LinkedList.getFirst(LinkedList.java:244)
at com.ichi2.libanki.sched.LrnCardQueue.getFirstDue(LrnCardQueue.java:25)
at com.ichi2.libanki.sched.SchedV2._getLrnCard(SchedV2.java:1108)
at com.ichi2.libanki.sched.SchedV2._getCard(SchedV2.java:674)
at com.ichi2.libanki.sched.SchedV2.getCard(SchedV2.java:172)
at com.ichi2.libanki.sched.SchedV2Test.regression_test_preview(SchedV2Test.java:1719)
```
|
1.0
|
[Bug] Flaky unit tests (including test SchedV2Test:regression_test_preview) - ```
com.ichi2.libanki.sched.SchedV2Test > regression_test_preview FAILED
java.lang.Exception: Main looper has queued unexecuted runnables. This might be the cause of the test failure. You might need a shadowOf(getMainLooper()).idle() call.
at org.robolectric.android.internal.AndroidTestEnvironment.checkStateAfterTestFailure(AndroidTestEnvironment.java:502)
at org.robolectric.RobolectricTestRunner$HelperTestRunner$1.evaluate(RobolectricTestRunner.java:581)
at org.robolectric.internal.SandboxTestRunner$2.lambda$evaluate$0(SandboxTestRunner.java:263)
at org.robolectric.internal.bytecode.Sandbox.lambda$runOnMainThread$0(Sandbox.java:89)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by:
java.util.NoSuchElementException
at java.util.LinkedList.getFirst(LinkedList.java:244)
at com.ichi2.libanki.sched.LrnCardQueue.getFirstDue(LrnCardQueue.java:25)
at com.ichi2.libanki.sched.SchedV2._getLrnCard(SchedV2.java:1108)
at com.ichi2.libanki.sched.SchedV2._getCard(SchedV2.java:674)
at com.ichi2.libanki.sched.SchedV2.getCard(SchedV2.java:172)
at com.ichi2.libanki.sched.SchedV2Test.regression_test_preview(SchedV2Test.java:1719)
```
|
process
|
flaky unit tests including test regression test preview com libanki sched regression test preview failed java lang exception main looper has queued unexecuted runnables this might be the cause of the test failure you might need a shadowof getmainlooper idle call at org robolectric android internal androidtestenvironment checkstateaftertestfailure androidtestenvironment java at org robolectric robolectrictestrunner helpertestrunner evaluate robolectrictestrunner java at org robolectric internal sandboxtestrunner lambda evaluate sandboxtestrunner java at org robolectric internal bytecode sandbox lambda runonmainthread sandbox java at java util concurrent futuretask run futuretask java at java util concurrent threadpoolexecutor runworker threadpoolexecutor java at java util concurrent threadpoolexecutor worker run threadpoolexecutor java at java lang thread run thread java caused by java util nosuchelementexception at java util linkedlist getfirst linkedlist java at com libanki sched lrncardqueue getfirstdue lrncardqueue java at com libanki sched getlrncard java at com libanki sched getcard java at com libanki sched getcard java at com libanki sched regression test preview java
| 1
|
184,080
| 14,968,368,194
|
IssuesEvent
|
2021-01-27 16:45:39
|
JohnnyRS/PandaCrazy-Max
|
https://api.github.com/repos/JohnnyRS/PandaCrazy-Max
|
closed
|
Extension is now on the final testing stage.
|
documentation extra attention
|
Everything I wanted to add to the extension is now finished. It should do everything that the old script did including the panda crazy helper and queue helper. The helper options are in the popup when clicking on the extension icon when a mturk page is opened. This week I will be testing all the options, buttons and stats to make sure they work and does what they should do. If there is any problems feel free to add a bug issue here or use the discussions tab here.
Hoping if there isn't any big problems I'll start the process of adding the extension to the chrome store next week. Due to this being my first extension I'll be testing to see how this works. Not sure how long the verification process will take from chrome so expect the extension in the store after the new year.
I also will be finishing up the documentation this week with screenshots and updated information. Leave a message here or in the discussions if there is anything that is confusing.
I will also be adding an example theme somewhere here. I am working on an example external script to control the extension also so other developers can create their own interfaces.
|
1.0
|
Extension is now on the final testing stage. - Everything I wanted to add to the extension is now finished. It should do everything that the old script did including the panda crazy helper and queue helper. The helper options are in the popup when clicking on the extension icon when a mturk page is opened. This week I will be testing all the options, buttons and stats to make sure they work and does what they should do. If there is any problems feel free to add a bug issue here or use the discussions tab here.
Hoping if there isn't any big problems I'll start the process of adding the extension to the chrome store next week. Due to this being my first extension I'll be testing to see how this works. Not sure how long the verification process will take from chrome so expect the extension in the store after the new year.
I also will be finishing up the documentation this week with screenshots and updated information. Leave a message here or in the discussions if there is anything that is confusing.
I will also be adding an example theme somewhere here. I am working on an example external script to control the extension also so other developers can create their own interfaces.
|
non_process
|
extension is now on the final testing stage everything i wanted to add to the extension is now finished it should do everything that the old script did including the panda crazy helper and queue helper the helper options are in the popup when clicking on the extension icon when a mturk page is opened this week i will be testing all the options buttons and stats to make sure they work and does what they should do if there is any problems feel free to add a bug issue here or use the discussions tab here hoping if there isn t any big problems i ll start the process of adding the extension to the chrome store next week due to this being my first extension i ll be testing to see how this works not sure how long the verification process will take from chrome so expect the extension in the store after the new year i also will be finishing up the documentation this week with screenshots and updated information leave a message here or in the discussions if there is anything that is confusing i will also be adding an example theme somewhere here i am working on an example external script to control the extension also so other developers can create their own interfaces
| 0
|
18,472
| 24,550,665,060
|
IssuesEvent
|
2022-10-12 12:22:05
|
GoogleCloudPlatform/fda-mystudies
|
https://api.github.com/repos/GoogleCloudPlatform/fda-mystudies
|
closed
|
[iOS] iOS 15.4 > HTML breakage in Rich text editor in instruction step for iOS 15.4 version
|
Bug P1 iOS Process: Fixed Process: Tested dev
|
**Steps:**
1. Upgrade iOS version to 15.4
2. Install the app
3. Login and enroll into study (eg. StudyID - AMobileStudy in Dev Instance)
4. Open instruction step and observe HTML is not rendered sometimes
5. Discard results and re-open again
6. Observe HTML is not rendered consistently
**Actual:** HTML breakage in Rich text editor in instruction step
**Expected:** Text should render properly
**Note:**
1. Issue not observed in other iOS versions like 15.1/15.2
2. Issue not observed in other RTE pages eg. consent, overview, Resources, Data sharing but need to verified from code level so it doesn't break for different combinations in the 15.4 version
**Refer video:**
https://user-images.githubusercontent.com/60386291/160422449-39bb8dde-b26b-4ea7-baea-df8434506c5b.MOV
|
2.0
|
[iOS] iOS 15.4 > HTML breakage in Rich text editor in instruction step for iOS 15.4 version - **Steps:**
1. Upgrade iOS version to 15.4
2. Install the app
3. Login and enroll into study (eg. StudyID - AMobileStudy in Dev Instance)
4. Open instruction step and observe HTML is not rendered sometimes
5. Discard results and re-open again
6. Observe HTML is not rendered consistently
**Actual:** HTML breakage in Rich text editor in instruction step
**Expected:** Text should render properly
**Note:**
1. Issue not observed in other iOS versions like 15.1/15.2
2. Issue not observed in other RTE pages eg. consent, overview, Resources, Data sharing but need to verified from code level so it doesn't break for different combinations in the 15.4 version
**Refer video:**
https://user-images.githubusercontent.com/60386291/160422449-39bb8dde-b26b-4ea7-baea-df8434506c5b.MOV
|
process
|
ios html breakage in rich text editor in instruction step for ios version steps upgrade ios version to install the app login and enroll into study eg studyid amobilestudy in dev instance open instruction step and observe html is not rendered sometimes discard results and re open again observe html is not rendered consistently actual html breakage in rich text editor in instruction step expected text should render properly note issue not observed in other ios versions like issue not observed in other rte pages eg consent overview resources data sharing but need to verified from code level so it doesn t break for different combinations in the version refer video
| 1
|
569,594
| 17,015,455,488
|
IssuesEvent
|
2021-07-02 11:20:52
|
tomhughes/trac-tickets
|
https://api.github.com/repos/tomhughes/trac-tickets
|
opened
|
P2 mini-icon
|
Component: potlatch2 Priority: trivial Type: enhancement
|
**[Submitted to the original trac issue database at 3.15pm, Saturday, 2nd April 2011]**
A famfamfam-style 16px-by-16px icon would be nice to ship with the SVN distribution of P2 :)
|
1.0
|
P2 mini-icon - **[Submitted to the original trac issue database at 3.15pm, Saturday, 2nd April 2011]**
A famfamfam-style 16px-by-16px icon would be nice to ship with the SVN distribution of P2 :)
|
non_process
|
mini icon a famfamfam style by icon would be nice to ship with the svn distribution of
| 0
|
454,065
| 13,094,267,072
|
IssuesEvent
|
2020-08-03 12:04:49
|
SkriptLang/Skript
|
https://api.github.com/repos/SkriptLang/Skript
|
closed
|
Suggest some additional features for Skript
|
enhancement priority: low
|
# Conditions
- [ ] plugin %string% is loaded
- [x] %chunk/world% is loaded
# Events
- [x] Locale change event (PlayerLocaleChangeEvent)
- [ ] Broadcast event (BroadcastMessageEvent) and recipient support for it (maybe? look at javadoc for recipient method)
- [x] Server ping event (ServerListPingEvent) with MOTD support
- [ ] Tab completion (TabCompleteEvent)
- [ ] Inventory drag event (InventoryDragEvent)
- [ ] Brew event (BrewEvent)
- [ ] Anvil prepare event (PrepareAnvilEvent)
- [ ] Horse jump event (HorseJumpEvent)
- [ ] Leash event (PlayerLeashEntityEvent)
- [ ] Unleash event (EntityUnleashEvent)
# Effects
- [ ] Load/unload plugins, worlds and chunks
- [x] Force player to chat
- [x] Show/hide player support
- [ ] Update inventory (maybe not, method is deprecated but has been forever so...?)
- [x] Send block change
# Expressions
- [x] hidden players of %players% (Player.Spigot#getHiddenPlayers)
- [x] locale of %players% (Player.Spigot#getLocale)
- [ ] New line
# Features
- [ ] Scoreboard support
- [ ] Bossbar support
- [ ] Firework support (firework types, launch effect, etc.)
- [ ] Inventory serialization
It would be great to have the basic features of Bukkit available without addon. 😃
|
1.0
|
Suggest some additional features for Skript - # Conditions
- [ ] plugin %string% is loaded
- [x] %chunk/world% is loaded
# Events
- [x] Locale change event (PlayerLocaleChangeEvent)
- [ ] Broadcast event (BroadcastMessageEvent) and recipient support for it (maybe? look at javadoc for recipient method)
- [x] Server ping event (ServerListPingEvent) with MOTD support
- [ ] Tab completion (TabCompleteEvent)
- [ ] Inventory drag event (InventoryDragEvent)
- [ ] Brew event (BrewEvent)
- [ ] Anvil prepare event (PrepareAnvilEvent)
- [ ] Horse jump event (HorseJumpEvent)
- [ ] Leash event (PlayerLeashEntityEvent)
- [ ] Unleash event (EntityUnleashEvent)
# Effects
- [ ] Load/unload plugins, worlds and chunks
- [x] Force player to chat
- [x] Show/hide player support
- [ ] Update inventory (maybe not, method is deprecated but has been forever so...?)
- [x] Send block change
# Expressions
- [x] hidden players of %players% (Player.Spigot#getHiddenPlayers)
- [x] locale of %players% (Player.Spigot#getLocale)
- [ ] New line
# Features
- [ ] Scoreboard support
- [ ] Bossbar support
- [ ] Firework support (firework types, launch effect, etc.)
- [ ] Inventory serialization
It would be great to have the basic features of Bukkit available without addon. 😃
|
non_process
|
suggest some additional features for skript conditions plugin string is loaded chunk world is loaded events locale change event playerlocalechangeevent broadcast event broadcastmessageevent and recipient support for it maybe look at javadoc for recipient method server ping event serverlistpingevent with motd support tab completion tabcompleteevent inventory drag event inventorydragevent brew event brewevent anvil prepare event prepareanvilevent horse jump event horsejumpevent leash event playerleashentityevent unleash event entityunleashevent effects load unload plugins worlds and chunks force player to chat show hide player support update inventory maybe not method is deprecated but has been forever so send block change expressions hidden players of players player spigot gethiddenplayers locale of players player spigot getlocale new line features scoreboard support bossbar support firework support firework types launch effect etc inventory serialization it would be great to have the basic features of bukkit available without addon 😃
| 0
|
131,070
| 5,142,471,798
|
IssuesEvent
|
2017-01-12 13:25:32
|
hpi-swt2/workshop-portal
|
https://api.github.com/repos/hpi-swt2/workshop-portal
|
closed
|
US_1.22: Anfragen Overview page
|
High Priority needs review team-helene
|
**As**
organizer/coach
**I want to**
have an overview page where I see all existing requests for workshops with the topic wish, the name of the person that made the request, the date wish and the and amount of people that would participate. I also want to see a status that shows if the request is open or accepted. I want a details button!
**in order to**
have better overview
** 🍪**
- [ ]
|
1.0
|
US_1.22: Anfragen Overview page - **As**
organizer/coach
**I want to**
have an overview page where I see all existing requests for workshops with the topic wish, the name of the person that made the request, the date wish and the and amount of people that would participate. I also want to see a status that shows if the request is open or accepted. I want a details button!
**in order to**
have better overview
** 🍪**
- [ ]
|
non_process
|
us anfragen overview page as organizer coach i want to have an overview page where i see all existing requests for workshops with the topic wish the name of the person that made the request the date wish and the and amount of people that would participate i also want to see a status that shows if the request is open or accepted i want a details button in order to have better overview 🍪
| 0
|
5,517
| 8,380,770,181
|
IssuesEvent
|
2018-10-07 18:01:07
|
bitshares/bitshares-community-ui
|
https://api.github.com/repos/bitshares/bitshares-community-ui
|
closed
|
Login/signup desktop pop-up window
|
Login mockup process
|
Problem: currently most of the bitshares users are confused which account type / security method to choose
Goal: create a user-friendly UI to make it easy to utilize all signup/login methods available at bitshares:
- cloud account with password
- wallet account with backup phrase
- wallet account with key file
|
1.0
|
Login/signup desktop pop-up window - Problem: currently most of the bitshares users are confused which account type / security method to choose
Goal: create a user-friendly UI to make it easy to utilize all signup/login methods available at bitshares:
- cloud account with password
- wallet account with backup phrase
- wallet account with key file
|
process
|
login signup desktop pop up window problem currently most of the bitshares users are confused which account type security method to choose goal create a user friendly ui to make it easy to utilize all signup login methods available at bitshares cloud account with password wallet account with backup phrase wallet account with key file
| 1
|
28,927
| 4,446,304,008
|
IssuesEvent
|
2016-08-20 15:54:10
|
cockroachdb/cockroach
|
https://api.github.com/repos/cockroachdb/cockroach
|
closed
|
stress: failed test in cockroach/gossip/gossip.test: TestGossipStorageCleanup
|
Robot test-failure
|
Binary: cockroach/static-tests.tar.gz sha: https://github.com/cockroachdb/cockroach/commits/dae179f8d4881dea0a891e23e4e06106315bee3a
Stress build found a failed test:
```
=== RUN TestGossipStorageCleanup
I160820 05:17:53.886360 gossip/simulation/network.go:68 simulating gossip network with 3 nodes
W160820 05:17:53.886513 gossip/gossip.go:1039 not connected to cluster; use --join to specify a connected node
W160820 05:17:53.886685 gossip/gossip.go:1039 not connected to cluster; use --join to specify a connected node
W160820 05:17:53.886828 gossip/gossip.go:1039 not connected to cluster; use --join to specify a connected node
W160820 05:17:53.891243 gossip/gossip.go:835 invalid bootstrap address: &{typ:tcp addr:10.0.0.1000:3333333}, invalid port 3333333
W160820 05:17:53.891421 gossip/gossip.go:835 invalid bootstrap address: &{typ:tcp addr:10.0.0.1000:3333333}, invalid port 3333333
W160820 05:17:53.891711 gossip/gossip.go:835 invalid bootstrap address: &{typ:tcp addr:10.0.0.1000:3333333}, invalid port 3333333
I160820 05:17:53.892496 gossip/client.go:111 node 1: started gossip client to 127.0.0.1:36397
I160820 05:17:53.892523 gossip/client.go:111 node 2: started gossip client to 127.0.0.1:33953
I160820 05:17:53.896227 gossip/client.go:111 node 3: started gossip client to 127.0.0.1:44049
I160820 05:17:53.900376 gossip/client.go:111 node 1: started gossip client to 127.0.0.1:43837
I160820 05:17:53.900387 gossip/client.go:111 node 3: started gossip client to 127.0.0.1:43837
I160820 05:17:53.900433 gossip/client.go:111 node 2: started gossip client to 127.0.0.1:43837
I160820 05:17:53.900487 gossip/gossip.go:1007 node has connected to cluster via gossip
I160820 05:17:53.901695 gossip/simulation/network.go:193 gossip network simulation: total infos sent=54, received=0
I160820 05:17:53.901807 gossip/gossip.go:1007 node has connected to cluster via gossip
I160820 05:17:53.902049 gossip/gossip.go:1007 node has connected to cluster via gossip
I160820 05:17:53.914643 http2_client.go:1024 transport: http2Client.notifyError got notified that the client transport was broken EOF.
I160820 05:17:53.915156 http2_client.go:1024 transport: http2Client.notifyError got notified that the client transport was broken read tcp 127.0.0.1:46128->127.0.0.1:43837: read: connection reset by peer.
I160820 05:17:53.915308 /go/src/google.golang.org/grpc/clientconn.go:651 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 127.0.0.1:43837: getsockopt: connection refused"; Reconnecting to {"127.0.0.1:43837" <nil>}
I160820 05:17:54.915488 /go/src/google.golang.org/grpc/clientconn.go:651 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 127.0.0.1:43837: getsockopt: connection refused"; Reconnecting to {"127.0.0.1:43837" <nil>}
I160820 05:17:56.520014 /go/src/google.golang.org/grpc/clientconn.go:651 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 127.0.0.1:43837: getsockopt: connection refused"; Reconnecting to {"127.0.0.1:43837" <nil>}
I160820 05:17:58.741592 /go/src/google.golang.org/grpc/clientconn.go:651 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 127.0.0.1:43837: getsockopt: connection refused"; Reconnecting to {"127.0.0.1:43837" <nil>}
I160820 05:18:02.561599 /go/src/google.golang.org/grpc/clientconn.go:651 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 127.0.0.1:43837: getsockopt: connection refused"; Reconnecting to {"127.0.0.1:43837" <nil>}
I160820 05:18:09.974949 /go/src/google.golang.org/grpc/clientconn.go:651 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 127.0.0.1:43837: getsockopt: connection refused"; Reconnecting to {"127.0.0.1:43837" <nil>}
I160820 05:18:21.300859 /go/src/google.golang.org/grpc/clientconn.go:651 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 127.0.0.1:43837: getsockopt: connection refused"; Reconnecting to {"127.0.0.1:43837" <nil>}
I160820 05:18:35.111526 /go/src/google.golang.org/grpc/clientconn.go:651 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 127.0.0.1:43837: getsockopt: connection refused"; Reconnecting to {"127.0.0.1:43837" <nil>}
I160820 05:18:38.987509 /go/src/google.golang.org/grpc/clientconn.go:751 grpc: addrConn.transportMonitor exits due to: context canceled
I160820 05:18:38.987549 http2_server.go:276 transport: http2Server.HandleStreams failed to read frame: read tcp 127.0.0.1:44049->127.0.0.1:43804: use of closed network connection
I160820 05:18:38.987559 http2_server.go:276 transport: http2Server.HandleStreams failed to read frame: read tcp 127.0.0.1:36397->127.0.0.1:33314: use of closed network connection
I160820 05:18:38.987583 http2_server.go:276 transport: http2Server.HandleStreams failed to read frame: read tcp 127.0.0.1:33953->127.0.0.1:39555: use of closed network connection
W160820 05:18:38.987611 gossip/infostore.go:291 node unavailable; try another peer
W160820 05:18:38.987634 gossip/infostore.go:291 node unavailable; try another peer
W160820 05:18:38.987684 gossip/infostore.go:291 node unavailable; try another peer
W160820 05:18:38.987916 gossip/infostore.go:291 node unavailable; try another peer
W160820 05:18:38.987936 gossip/infostore.go:291 node unavailable; try another peer
W160820 05:18:38.987955 gossip/infostore.go:291 node unavailable; try another peer
W160820 05:18:38.987971 gossip/infostore.go:291 node unavailable; try another peer
--- FAIL: TestGossipStorageCleanup (45.10s)
testing.go:117: gossip/storage_test.go:271, condition failed to evaluate within 45s: expected 2, got 4 (info: []util.UnresolvedAddr{util.UnresolvedAddr{NetworkField:"tcp", AddressField:"127.0.0.1:36397"}, util.UnresolvedAddr{NetworkField:"tcp", AddressField:"127.0.0.1:33953"}, util.UnresolvedAddr{NetworkField:"tcp", AddressField:"127.0.0.1:35176"}, util.UnresolvedAddr{NetworkField:"tcp", AddressField:"127.0.0.1:43837"}})
FAIL
ERROR: exit status 1
```
Run Details:
```
98 runs so far, 0 failures, over 5s
202 runs so far, 0 failures, over 10s
307 runs so far, 0 failures, over 15s
415 runs so far, 0 failures, over 20s
519 runs so far, 0 failures, over 25s
623 runs so far, 0 failures, over 30s
727 runs so far, 0 failures, over 35s
830 runs so far, 0 failures, over 40s
928 runs so far, 0 failures, over 45s
1016 runs so far, 0 failures, over 50s
1081 runs so far, 0 failures, over 55s
1150 runs so far, 0 failures, over 1m0s
1218 runs so far, 0 failures, over 1m5s
1289 runs so far, 0 failures, over 1m10s
1362 runs so far, 0 failures, over 1m15s
1433 runs so far, 0 failures, over 1m20s
1500 runs so far, 0 failures, over 1m25s
1539 runs completed, 1 failures, over 1m28s
FAIL
```
Please assign, take a look and update the issue accordingly.
|
1.0
|
stress: failed test in cockroach/gossip/gossip.test: TestGossipStorageCleanup - Binary: cockroach/static-tests.tar.gz sha: https://github.com/cockroachdb/cockroach/commits/dae179f8d4881dea0a891e23e4e06106315bee3a
Stress build found a failed test:
```
=== RUN TestGossipStorageCleanup
I160820 05:17:53.886360 gossip/simulation/network.go:68 simulating gossip network with 3 nodes
W160820 05:17:53.886513 gossip/gossip.go:1039 not connected to cluster; use --join to specify a connected node
W160820 05:17:53.886685 gossip/gossip.go:1039 not connected to cluster; use --join to specify a connected node
W160820 05:17:53.886828 gossip/gossip.go:1039 not connected to cluster; use --join to specify a connected node
W160820 05:17:53.891243 gossip/gossip.go:835 invalid bootstrap address: &{typ:tcp addr:10.0.0.1000:3333333}, invalid port 3333333
W160820 05:17:53.891421 gossip/gossip.go:835 invalid bootstrap address: &{typ:tcp addr:10.0.0.1000:3333333}, invalid port 3333333
W160820 05:17:53.891711 gossip/gossip.go:835 invalid bootstrap address: &{typ:tcp addr:10.0.0.1000:3333333}, invalid port 3333333
I160820 05:17:53.892496 gossip/client.go:111 node 1: started gossip client to 127.0.0.1:36397
I160820 05:17:53.892523 gossip/client.go:111 node 2: started gossip client to 127.0.0.1:33953
I160820 05:17:53.896227 gossip/client.go:111 node 3: started gossip client to 127.0.0.1:44049
I160820 05:17:53.900376 gossip/client.go:111 node 1: started gossip client to 127.0.0.1:43837
I160820 05:17:53.900387 gossip/client.go:111 node 3: started gossip client to 127.0.0.1:43837
I160820 05:17:53.900433 gossip/client.go:111 node 2: started gossip client to 127.0.0.1:43837
I160820 05:17:53.900487 gossip/gossip.go:1007 node has connected to cluster via gossip
I160820 05:17:53.901695 gossip/simulation/network.go:193 gossip network simulation: total infos sent=54, received=0
I160820 05:17:53.901807 gossip/gossip.go:1007 node has connected to cluster via gossip
I160820 05:17:53.902049 gossip/gossip.go:1007 node has connected to cluster via gossip
I160820 05:17:53.914643 http2_client.go:1024 transport: http2Client.notifyError got notified that the client transport was broken EOF.
I160820 05:17:53.915156 http2_client.go:1024 transport: http2Client.notifyError got notified that the client transport was broken read tcp 127.0.0.1:46128->127.0.0.1:43837: read: connection reset by peer.
I160820 05:17:53.915308 /go/src/google.golang.org/grpc/clientconn.go:651 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 127.0.0.1:43837: getsockopt: connection refused"; Reconnecting to {"127.0.0.1:43837" <nil>}
I160820 05:17:54.915488 /go/src/google.golang.org/grpc/clientconn.go:651 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 127.0.0.1:43837: getsockopt: connection refused"; Reconnecting to {"127.0.0.1:43837" <nil>}
I160820 05:17:56.520014 /go/src/google.golang.org/grpc/clientconn.go:651 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 127.0.0.1:43837: getsockopt: connection refused"; Reconnecting to {"127.0.0.1:43837" <nil>}
I160820 05:17:58.741592 /go/src/google.golang.org/grpc/clientconn.go:651 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 127.0.0.1:43837: getsockopt: connection refused"; Reconnecting to {"127.0.0.1:43837" <nil>}
I160820 05:18:02.561599 /go/src/google.golang.org/grpc/clientconn.go:651 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 127.0.0.1:43837: getsockopt: connection refused"; Reconnecting to {"127.0.0.1:43837" <nil>}
I160820 05:18:09.974949 /go/src/google.golang.org/grpc/clientconn.go:651 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 127.0.0.1:43837: getsockopt: connection refused"; Reconnecting to {"127.0.0.1:43837" <nil>}
I160820 05:18:21.300859 /go/src/google.golang.org/grpc/clientconn.go:651 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 127.0.0.1:43837: getsockopt: connection refused"; Reconnecting to {"127.0.0.1:43837" <nil>}
I160820 05:18:35.111526 /go/src/google.golang.org/grpc/clientconn.go:651 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 127.0.0.1:43837: getsockopt: connection refused"; Reconnecting to {"127.0.0.1:43837" <nil>}
I160820 05:18:38.987509 /go/src/google.golang.org/grpc/clientconn.go:751 grpc: addrConn.transportMonitor exits due to: context canceled
I160820 05:18:38.987549 http2_server.go:276 transport: http2Server.HandleStreams failed to read frame: read tcp 127.0.0.1:44049->127.0.0.1:43804: use of closed network connection
I160820 05:18:38.987559 http2_server.go:276 transport: http2Server.HandleStreams failed to read frame: read tcp 127.0.0.1:36397->127.0.0.1:33314: use of closed network connection
I160820 05:18:38.987583 http2_server.go:276 transport: http2Server.HandleStreams failed to read frame: read tcp 127.0.0.1:33953->127.0.0.1:39555: use of closed network connection
W160820 05:18:38.987611 gossip/infostore.go:291 node unavailable; try another peer
W160820 05:18:38.987634 gossip/infostore.go:291 node unavailable; try another peer
W160820 05:18:38.987684 gossip/infostore.go:291 node unavailable; try another peer
W160820 05:18:38.987916 gossip/infostore.go:291 node unavailable; try another peer
W160820 05:18:38.987936 gossip/infostore.go:291 node unavailable; try another peer
W160820 05:18:38.987955 gossip/infostore.go:291 node unavailable; try another peer
W160820 05:18:38.987971 gossip/infostore.go:291 node unavailable; try another peer
--- FAIL: TestGossipStorageCleanup (45.10s)
testing.go:117: gossip/storage_test.go:271, condition failed to evaluate within 45s: expected 2, got 4 (info: []util.UnresolvedAddr{util.UnresolvedAddr{NetworkField:"tcp", AddressField:"127.0.0.1:36397"}, util.UnresolvedAddr{NetworkField:"tcp", AddressField:"127.0.0.1:33953"}, util.UnresolvedAddr{NetworkField:"tcp", AddressField:"127.0.0.1:35176"}, util.UnresolvedAddr{NetworkField:"tcp", AddressField:"127.0.0.1:43837"}})
FAIL
ERROR: exit status 1
```
Run Details:
```
98 runs so far, 0 failures, over 5s
202 runs so far, 0 failures, over 10s
307 runs so far, 0 failures, over 15s
415 runs so far, 0 failures, over 20s
519 runs so far, 0 failures, over 25s
623 runs so far, 0 failures, over 30s
727 runs so far, 0 failures, over 35s
830 runs so far, 0 failures, over 40s
928 runs so far, 0 failures, over 45s
1016 runs so far, 0 failures, over 50s
1081 runs so far, 0 failures, over 55s
1150 runs so far, 0 failures, over 1m0s
1218 runs so far, 0 failures, over 1m5s
1289 runs so far, 0 failures, over 1m10s
1362 runs so far, 0 failures, over 1m15s
1433 runs so far, 0 failures, over 1m20s
1500 runs so far, 0 failures, over 1m25s
1539 runs completed, 1 failures, over 1m28s
FAIL
```
Please assign, take a look and update the issue accordingly.
|
non_process
|
stress failed test in cockroach gossip gossip test testgossipstoragecleanup binary cockroach static tests tar gz sha stress build found a failed test run testgossipstoragecleanup gossip simulation network go simulating gossip network with nodes gossip gossip go not connected to cluster use join to specify a connected node gossip gossip go not connected to cluster use join to specify a connected node gossip gossip go not connected to cluster use join to specify a connected node gossip gossip go invalid bootstrap address typ tcp addr invalid port gossip gossip go invalid bootstrap address typ tcp addr invalid port gossip gossip go invalid bootstrap address typ tcp addr invalid port gossip client go node started gossip client to gossip client go node started gossip client to gossip client go node started gossip client to gossip client go node started gossip client to gossip client go node started gossip client to gossip client go node started gossip client to gossip gossip go node has connected to cluster via gossip gossip simulation network go gossip network simulation total infos sent received gossip gossip go node has connected to cluster via gossip gossip gossip go node has connected to cluster via gossip client go transport notifyerror got notified that the client transport was broken eof client go transport notifyerror got notified that the client transport was broken read tcp read connection reset by peer go src google golang org grpc clientconn go grpc addrconn resettransport failed to create client transport connection error desc transport dial tcp getsockopt connection refused reconnecting to go src google golang org grpc clientconn go grpc addrconn resettransport failed to create client transport connection error desc transport dial tcp getsockopt connection refused reconnecting to go src google golang org grpc clientconn go grpc addrconn resettransport failed to create client transport connection error desc transport dial tcp getsockopt connection refused reconnecting to go src google golang org grpc clientconn go grpc addrconn resettransport failed to create client transport connection error desc transport dial tcp getsockopt connection refused reconnecting to go src google golang org grpc clientconn go grpc addrconn resettransport failed to create client transport connection error desc transport dial tcp getsockopt connection refused reconnecting to go src google golang org grpc clientconn go grpc addrconn resettransport failed to create client transport connection error desc transport dial tcp getsockopt connection refused reconnecting to go src google golang org grpc clientconn go grpc addrconn resettransport failed to create client transport connection error desc transport dial tcp getsockopt connection refused reconnecting to go src google golang org grpc clientconn go grpc addrconn resettransport failed to create client transport connection error desc transport dial tcp getsockopt connection refused reconnecting to go src google golang org grpc clientconn go grpc addrconn transportmonitor exits due to context canceled server go transport handlestreams failed to read frame read tcp use of closed network connection server go transport handlestreams failed to read frame read tcp use of closed network connection server go transport handlestreams failed to read frame read tcp use of closed network connection gossip infostore go node unavailable try another peer gossip infostore go node unavailable try another peer gossip infostore go node unavailable try another peer gossip infostore go node unavailable try another peer gossip infostore go node unavailable try another peer gossip infostore go node unavailable try another peer gossip infostore go node unavailable try another peer fail testgossipstoragecleanup testing go gossip storage test go condition failed to evaluate within expected got info util unresolvedaddr util unresolvedaddr networkfield tcp addressfield util unresolvedaddr networkfield tcp addressfield util unresolvedaddr networkfield tcp addressfield util unresolvedaddr networkfield tcp addressfield fail error exit status run details runs so far failures over runs so far failures over runs so far failures over runs so far failures over runs so far failures over runs so far failures over runs so far failures over runs so far failures over runs so far failures over runs so far failures over runs so far failures over runs so far failures over runs so far failures over runs so far failures over runs so far failures over runs so far failures over runs so far failures over runs completed failures over fail please assign take a look and update the issue accordingly
| 0
|
127,949
| 5,040,883,393
|
IssuesEvent
|
2016-12-19 08:09:46
|
Signbank/NGT-signbank
|
https://api.github.com/repos/Signbank/NGT-signbank
|
closed
|
Make all Signbank data available in ELAN by making it downloadable in packages
|
ASL enhancement top priority
|
(translated from an email sent earlier)
The connection between Signbank and ELAN will be made by putting all Signbank data into a package (e.g. zipped) that can be downloaded by ELAN through a webservice API. The package contains all glosses and of each gloss
1. all data fields
2. all media (images, videos etc.) in small format (how small? how to shrink? (with ffmpeg/avconv))
ELAN uses this package as a kind of ECV+, so when showing, creating/editing of annotations, in the lexicon tab or showing the gloss video in several places.
A package has a certain timestamp and the API makes it possible to download only the changes between 2 timestamps (normally the timestamp of the last downloaded package and now). ELAN will ask for a new package at strategic times, strategic for the ELAN user that is.
The reason to have all Signbank data saved locally is that CNGT computers are already fit for large amount of data. It also helps to show the gloss videos if they are stored locally.
Tasks/questions for the Signbank team:
- How does the API work? How to sign in?
- What does a package look like?
Tasks/questions for the ELAN team:
- How to store the Signbank data?
- How to use the Signbank data in ELAN?
- How does the link back to Signbank work? Through a web link in the default browser.
|
1.0
|
Make all Signbank data available in ELAN by making it downloadable in packages - (translated from an email sent earlier)
The connection between Signbank and ELAN will be made by putting all Signbank data into a package (e.g. zipped) that can be downloaded by ELAN through a webservice API. The package contains all glosses and of each gloss
1. all data fields
2. all media (images, videos etc.) in small format (how small? how to shrink? (with ffmpeg/avconv))
ELAN uses this package as a kind of ECV+, so when showing, creating/editing of annotations, in the lexicon tab or showing the gloss video in several places.
A package has a certain timestamp and the API makes it possible to download only the changes between 2 timestamps (normally the timestamp of the last downloaded package and now). ELAN will ask for a new package at strategic times, strategic for the ELAN user that is.
The reason to have all Signbank data saved locally is that CNGT computers are already fit for large amount of data. It also helps to show the gloss videos if they are stored locally.
Tasks/questions for the Signbank team:
- How does the API work? How to sign in?
- What does a package look like?
Tasks/questions for the ELAN team:
- How to store the Signbank data?
- How to use the Signbank data in ELAN?
- How does the link back to Signbank work? Through a web link in the default browser.
|
non_process
|
make all signbank data available in elan by making it downloadable in packages translated from an email sent earlier the connection between signbank and elan will be made by putting all signbank data into a package e g zipped that can be downloaded by elan through a webservice api the package contains all glosses and of each gloss all data fields all media images videos etc in small format how small how to shrink with ffmpeg avconv elan uses this package as a kind of ecv so when showing creating editing of annotations in the lexicon tab or showing the gloss video in several places a package has a certain timestamp and the api makes it possible to download only the changes between timestamps normally the timestamp of the last downloaded package and now elan will ask for a new package at strategic times strategic for the elan user that is the reason to have all signbank data saved locally is that cngt computers are already fit for large amount of data it also helps to show the gloss videos if they are stored locally tasks questions for the signbank team how does the api work how to sign in what does a package look like tasks questions for the elan team how to store the signbank data how to use the signbank data in elan how does the link back to signbank work through a web link in the default browser
| 0
|
17,266
| 23,048,315,091
|
IssuesEvent
|
2022-07-24 08:35:11
|
python/cpython
|
https://api.github.com/repos/python/cpython
|
closed
|
Uninformative error message when working with semaphores
|
type-feature stdlib pending 3.12 expert-multiprocessing
|
<!--
If you're new to Python and you're not sure whether what you're experiencing is a bug, the CPython issue tracker is not
the right place to seek help. Consider the following options instead:
- reading the Python tutorial: https://docs.python.org/3/tutorial/
- posting in the "Users" category on discuss.python.org: https://discuss.python.org/c/users/7
- emailing the Python-list mailing list: https://mail.python.org/mailman/listinfo/python-list
- searching our issue tracker (https://github.com/python/cpython/issues) to see if
your problem has already been reported
-->
**Bug report**
Uninformative error message `OSError: [Errno 28] No space left on device` when working with semaphores
in "python3.8/multiprocessing/synchronize.py", line 57"
steps to reproduce:
```bash
docker run --shm-size="1m" -it python:3.8 python -c 'from multiprocessing import Array; myarr = [Array("b", 100) for _ in range(1000)]'
```
current behavior:
```
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "<string>", line 1, in <listcomp>
File "/usr/local/lib/python3.8/multiprocessing/context.py", line 141, in Array
return Array(typecode_or_type, size_or_initializer, lock=lock,
File "/usr/local/lib/python3.8/multiprocessing/sharedctypes.py", line 93, in Array
lock = ctx.RLock()
File "/usr/local/lib/python3.8/multiprocessing/context.py", line 73, in RLock
return RLock(ctx=self.get_context())
File "/usr/local/lib/python3.8/multiprocessing/synchronize.py", line 187, in __init__
SemLock.__init__(self, RECURSIVE_MUTEX, 1, 1, ctx=ctx)
File "/usr/local/lib/python3.8/multiprocessing/synchronize.py", line 57, in __init__
sl = self._semlock = _multiprocessing.SemLock(
OSError: [Errno 28] No space left on device
```
**Your environment**
<!-- Include as many relevant details as possible about the environment you experienced the bug in -->
- CPython versions tested on: `3.8 3.9 3.10`
- Operating system and architecture: `Linux r2d2 5.13.0-35-generic #40~20.04.1-Ubuntu SMP Mon Mar 7 09:18:32 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux`
- docker: `docker-ce 5:20.10.13~3-0~ubuntu-focal`
How to fix:
Add a clearer message: `There is not enough space in the file system to create a semaphore`
<!--
You can freely edit this text. Remove any lines you believe are unnecessary.
-->
|
1.0
|
Uninformative error message when working with semaphores - <!--
If you're new to Python and you're not sure whether what you're experiencing is a bug, the CPython issue tracker is not
the right place to seek help. Consider the following options instead:
- reading the Python tutorial: https://docs.python.org/3/tutorial/
- posting in the "Users" category on discuss.python.org: https://discuss.python.org/c/users/7
- emailing the Python-list mailing list: https://mail.python.org/mailman/listinfo/python-list
- searching our issue tracker (https://github.com/python/cpython/issues) to see if
your problem has already been reported
-->
**Bug report**
Uninformative error message `OSError: [Errno 28] No space left on device` when working with semaphores
in "python3.8/multiprocessing/synchronize.py", line 57"
steps to reproduce:
```bash
docker run --shm-size="1m" -it python:3.8 python -c 'from multiprocessing import Array; myarr = [Array("b", 100) for _ in range(1000)]'
```
current behavior:
```
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "<string>", line 1, in <listcomp>
File "/usr/local/lib/python3.8/multiprocessing/context.py", line 141, in Array
return Array(typecode_or_type, size_or_initializer, lock=lock,
File "/usr/local/lib/python3.8/multiprocessing/sharedctypes.py", line 93, in Array
lock = ctx.RLock()
File "/usr/local/lib/python3.8/multiprocessing/context.py", line 73, in RLock
return RLock(ctx=self.get_context())
File "/usr/local/lib/python3.8/multiprocessing/synchronize.py", line 187, in __init__
SemLock.__init__(self, RECURSIVE_MUTEX, 1, 1, ctx=ctx)
File "/usr/local/lib/python3.8/multiprocessing/synchronize.py", line 57, in __init__
sl = self._semlock = _multiprocessing.SemLock(
OSError: [Errno 28] No space left on device
```
**Your environment**
<!-- Include as many relevant details as possible about the environment you experienced the bug in -->
- CPython versions tested on: `3.8 3.9 3.10`
- Operating system and architecture: `Linux r2d2 5.13.0-35-generic #40~20.04.1-Ubuntu SMP Mon Mar 7 09:18:32 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux`
- docker: `docker-ce 5:20.10.13~3-0~ubuntu-focal`
How to fix:
Add a clearer message: `There is not enough space in the file system to create a semaphore`
<!--
You can freely edit this text. Remove any lines you believe are unnecessary.
-->
|
process
|
uninformative error message when working with semaphores if you re new to python and you re not sure whether what you re experiencing is a bug the cpython issue tracker is not the right place to seek help consider the following options instead reading the python tutorial posting in the users category on discuss python org emailing the python list mailing list searching our issue tracker to see if your problem has already been reported bug report uninformative error message oserror no space left on device when working with semaphores in multiprocessing synchronize py line steps to reproduce bash docker run shm size it python python c from multiprocessing import array myarr current behavior traceback most recent call last file line in file line in file usr local lib multiprocessing context py line in array return array typecode or type size or initializer lock lock file usr local lib multiprocessing sharedctypes py line in array lock ctx rlock file usr local lib multiprocessing context py line in rlock return rlock ctx self get context file usr local lib multiprocessing synchronize py line in init semlock init self recursive mutex ctx ctx file usr local lib multiprocessing synchronize py line in init sl self semlock multiprocessing semlock oserror no space left on device your environment cpython versions tested on operating system and architecture linux generic ubuntu smp mon mar utc gnu linux docker docker ce ubuntu focal how to fix add a clearer message there is not enough space in the file system to create a semaphore you can freely edit this text remove any lines you believe are unnecessary
| 1
|
641,442
| 20,826,717,787
|
IssuesEvent
|
2022-03-18 22:06:26
|
MaracatronicsRobotics/Armorial-Suassuna
|
https://api.github.com/repos/MaracatronicsRobotics/Armorial-Suassuna
|
closed
|
WorldMap
|
suassuna priority
|
The WorldMap class will be, as its name suggests, the class that will store all field objects and field information. It must instantiate the Coach's gRPC client, which will make constant requests via the network to obtain the most up-to-date data from the Armorial-Carrero module, fill in and make it possible through methods to request this data.
- [x] Create the WorldMap base class which will inherit from Entity class
- [x] Create an #77 (similar to [this](https://github.com/MaracatronicsRobotics/Suassuna-SSL/blob/main/src/utils/types/object/object.h)) class that can receive both Ball and Robot class data (from protobuf) and parse all of its information providing also getters **[CANCELLED]**
- [x] Allocate an instance from the Coach gRPC client
- [x] In the loop() method make the requests using the gRPC client and update the **Object** and field vars (remember to use [QReadWriteLock ](https://doc.qt.io/qt-5/qreadwritelock.html) for better performances)
- [x] Make get methods to request objects and field data (for the Field-related requests an class #78 can be created just like [here](https://github.com/MaracatronicsRobotics/Armorial-Suassuna/blob/master/entity/locations.h)
|
1.0
|
WorldMap - The WorldMap class will be, as its name suggests, the class that will store all field objects and field information. It must instantiate the Coach's gRPC client, which will make constant requests via the network to obtain the most up-to-date data from the Armorial-Carrero module, fill in and make it possible through methods to request this data.
- [x] Create the WorldMap base class which will inherit from Entity class
- [x] Create an #77 (similar to [this](https://github.com/MaracatronicsRobotics/Suassuna-SSL/blob/main/src/utils/types/object/object.h)) class that can receive both Ball and Robot class data (from protobuf) and parse all of its information providing also getters **[CANCELLED]**
- [x] Allocate an instance from the Coach gRPC client
- [x] In the loop() method make the requests using the gRPC client and update the **Object** and field vars (remember to use [QReadWriteLock ](https://doc.qt.io/qt-5/qreadwritelock.html) for better performances)
- [x] Make get methods to request objects and field data (for the Field-related requests an class #78 can be created just like [here](https://github.com/MaracatronicsRobotics/Armorial-Suassuna/blob/master/entity/locations.h)
|
non_process
|
worldmap the worldmap class will be as its name suggests the class that will store all field objects and field information it must instantiate the coach s grpc client which will make constant requests via the network to obtain the most up to date data from the armorial carrero module fill in and make it possible through methods to request this data create the worldmap base class which will inherit from entity class create an similar to class that can receive both ball and robot class data from protobuf and parse all of its information providing also getters allocate an instance from the coach grpc client in the loop method make the requests using the grpc client and update the object and field vars remember to use for better performances make get methods to request objects and field data for the field related requests an class can be created just like
| 0
|
274,611
| 20,843,611,244
|
IssuesEvent
|
2022-03-21 05:29:59
|
fluid-cloudnative/fluid
|
https://api.github.com/repos/fluid-cloudnative/fluid
|
opened
|
[DOC]Insert licence for pkg/ddc/alluxio/load_data.go
|
documentation
|
**Provide a link to that doc page:**
**What is the defect and your suggestions on improvement:**
Insert licence for pkg/ddc/alluxio/load_data.go
|
1.0
|
[DOC]Insert licence for pkg/ddc/alluxio/load_data.go - **Provide a link to that doc page:**
**What is the defect and your suggestions on improvement:**
Insert licence for pkg/ddc/alluxio/load_data.go
|
non_process
|
insert licence for pkg ddc alluxio load data go provide a link to that doc page what is the defect and your suggestions on improvement insert licence for pkg ddc alluxio load data go
| 0
|
2,783
| 5,717,541,843
|
IssuesEvent
|
2017-04-19 17:28:46
|
nodejs/node
|
https://api.github.com/repos/nodejs/node
|
closed
|
process:Why http_parser version do not display?
|
confirmed-bug http_parser process
|
* **Version**:8.0.0-pre
* **Platform**:Darwin Kernel Version 16.5.0: Fri Mar 3 16:52:33 PST 2017; root:xnu-3789.51.2~3/RELEASE_X86_64 x86_64
* **Subsystem**:http_parser
When I type `node -p process.versions.http_parser` in Terminal,it display below:
`HTTP_PARSER_VERSION_MAJOR.HTTP_PARSER_VERSION_MINOR.HTTP_PARSER_VERSION_PATCH`
It is never happen in previous version,just nearest master branch.Windows and macOS be affected,and I do not test in Linux.
|
1.0
|
process:Why http_parser version do not display? - * **Version**:8.0.0-pre
* **Platform**:Darwin Kernel Version 16.5.0: Fri Mar 3 16:52:33 PST 2017; root:xnu-3789.51.2~3/RELEASE_X86_64 x86_64
* **Subsystem**:http_parser
When I type `node -p process.versions.http_parser` in Terminal,it display below:
`HTTP_PARSER_VERSION_MAJOR.HTTP_PARSER_VERSION_MINOR.HTTP_PARSER_VERSION_PATCH`
It is never happen in previous version,just nearest master branch.Windows and macOS be affected,and I do not test in Linux.
|
process
|
process why http parser version do not display version pre platform darwin kernel version fri mar pst root xnu release subsystem http parser when i type node p process versions http parser in terminal it display below http parser version major http parser version minor http parser version patch it is never happen in previous version just nearest master branch windows and macos be affected and i do not test in linux
| 1
|
704,700
| 24,206,570,659
|
IssuesEvent
|
2022-09-25 10:08:49
|
space-wizards/space-station-14
|
https://api.github.com/repos/space-wizards/space-station-14
|
opened
|
Botany scaling should be removed
|
Issue: Bug Priority: 2-Before Release Difficulty: 1-Easy
|
The first time I saw the sprites being scaled I thought it was a bug because the sprites looked so out of place. After talking about mob sprite scaling on discord it's probably better that this gets reverted.
|
1.0
|
Botany scaling should be removed - The first time I saw the sprites being scaled I thought it was a bug because the sprites looked so out of place. After talking about mob sprite scaling on discord it's probably better that this gets reverted.
|
non_process
|
botany scaling should be removed the first time i saw the sprites being scaled i thought it was a bug because the sprites looked so out of place after talking about mob sprite scaling on discord it s probably better that this gets reverted
| 0
|
711,890
| 24,478,863,716
|
IssuesEvent
|
2022-10-08 14:49:01
|
AY2223S1-CS2103T-W17-1/tp
|
https://api.github.com/repos/AY2223S1-CS2103T-W17-1/tp
|
closed
|
Event Implementations
|
type.Task priority.High
|
Refactor Tags to Events, and implement the relevant methods and UI changes.
|
1.0
|
Event Implementations - Refactor Tags to Events, and implement the relevant methods and UI changes.
|
non_process
|
event implementations refactor tags to events and implement the relevant methods and ui changes
| 0
|
193,733
| 14,661,004,466
|
IssuesEvent
|
2020-12-29 01:59:30
|
github-vet/rangeloop-pointer-findings
|
https://api.github.com/repos/github-vet/rangeloop-pointer-findings
|
closed
|
firebase/firebase-admin-go: firebase_test.go; 18 LoC
|
fresh small test
|
Found a possible issue in [firebase/firebase-admin-go](https://www.github.com/firebase/firebase-admin-go) at [firebase_test.go](https://github.com/firebase/firebase-admin-go/blob/77177c78411cff9a6c2de612c52d903776582e6b/firebase_test.go#L246-L263)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.
> reference to tc was used in a composite literal at line 249
[Click here to see the code in its original context.](https://github.com/firebase/firebase-admin-go/blob/77177c78411cff9a6c2de612c52d903776582e6b/firebase_test.go#L246-L263)
<details>
<summary>Click here to show the 18 line(s) of Go which triggered the analyzer.</summary>
```go
for _, tc := range cases {
ctx := context.Background()
conf := &Config{
AuthOverride: &tc,
DatabaseURL: "https://mock-db.firebaseio.com",
}
app, err := NewApp(ctx, conf, option.WithCredentialsFile("testdata/service_account.json"))
if err != nil {
t.Fatal(err)
}
if !reflect.DeepEqual(app.authOverride, tc) {
t.Errorf("AuthOverrides = %v; want = %v", app.authOverride, tc)
}
if c, err := app.Database(ctx); c == nil || err != nil {
t.Errorf("Database() = (%v, %v); want (db, nil)", c, err)
}
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: 77177c78411cff9a6c2de612c52d903776582e6b
|
1.0
|
firebase/firebase-admin-go: firebase_test.go; 18 LoC -
Found a possible issue in [firebase/firebase-admin-go](https://www.github.com/firebase/firebase-admin-go) at [firebase_test.go](https://github.com/firebase/firebase-admin-go/blob/77177c78411cff9a6c2de612c52d903776582e6b/firebase_test.go#L246-L263)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.
> reference to tc was used in a composite literal at line 249
[Click here to see the code in its original context.](https://github.com/firebase/firebase-admin-go/blob/77177c78411cff9a6c2de612c52d903776582e6b/firebase_test.go#L246-L263)
<details>
<summary>Click here to show the 18 line(s) of Go which triggered the analyzer.</summary>
```go
for _, tc := range cases {
ctx := context.Background()
conf := &Config{
AuthOverride: &tc,
DatabaseURL: "https://mock-db.firebaseio.com",
}
app, err := NewApp(ctx, conf, option.WithCredentialsFile("testdata/service_account.json"))
if err != nil {
t.Fatal(err)
}
if !reflect.DeepEqual(app.authOverride, tc) {
t.Errorf("AuthOverrides = %v; want = %v", app.authOverride, tc)
}
if c, err := app.Database(ctx); c == nil || err != nil {
t.Errorf("Database() = (%v, %v); want (db, nil)", c, err)
}
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: 77177c78411cff9a6c2de612c52d903776582e6b
|
non_process
|
firebase firebase admin go firebase test go loc found a possible issue in at below is the message reported by the analyzer for this snippet of code beware that the analyzer only reports the first issue it finds so please do not limit your consideration to the contents of the below message reference to tc was used in a composite literal at line click here to show the line s of go which triggered the analyzer go for tc range cases ctx context background conf config authoverride tc databaseurl app err newapp ctx conf option withcredentialsfile testdata service account json if err nil t fatal err if reflect deepequal app authoverride tc t errorf authoverrides v want v app authoverride tc if c err app database ctx c nil err nil t errorf database v v want db nil c err leave a reaction on this issue to contribute to the project by classifying this instance as a bug mitigated or desirable behavior rocket see the descriptions of the classifications for more information commit id
| 0
|
434,673
| 12,521,606,416
|
IssuesEvent
|
2020-06-03 17:40:57
|
cds-snc/report-a-cybercrime
|
https://api.github.com/repos/cds-snc/report-a-cybercrime
|
closed
|
High Priority: If a user's referrer isn't from CAFC, redirect them to CAFC.
|
Good learning issue HOTFIX 🔥 bug high priority
|
Right now our app accepts a new visitor once an hour. When it is time for a new visitor, we accept them regardless of their referrer. Once we've had a new visitor, we do not let anyone in for an hour.
Our app gets a lot of traffic without a valid referrer (bots, webcrawlers, etc..).
To prevent this traffic from blocking valid traffic, code was added in #1672 to only increment availableData.numberOfRequests and availableData.lastRequested if the user had a valid referrer. However we still allow this invalid traffic to access the app, but this traffic is not counted towards the 1 per hour user limit.
However these bots, webcrawlers, etc.. are messing with our google analytics analysis.
This code needs to be changed:
1. redirect anyone who does not have a valid referrer back to cafc
2. add a environment variable to we can disable this behaviour on our local, dev and staging for testing.
FYI: PR #1672 also includes testing procedures to forge your referrer for local testing this code.
|
1.0
|
High Priority: If a user's referrer isn't from CAFC, redirect them to CAFC. - Right now our app accepts a new visitor once an hour. When it is time for a new visitor, we accept them regardless of their referrer. Once we've had a new visitor, we do not let anyone in for an hour.
Our app gets a lot of traffic without a valid referrer (bots, webcrawlers, etc..).
To prevent this traffic from blocking valid traffic, code was added in #1672 to only increment availableData.numberOfRequests and availableData.lastRequested if the user had a valid referrer. However we still allow this invalid traffic to access the app, but this traffic is not counted towards the 1 per hour user limit.
However these bots, webcrawlers, etc.. are messing with our google analytics analysis.
This code needs to be changed:
1. redirect anyone who does not have a valid referrer back to cafc
2. add a environment variable to we can disable this behaviour on our local, dev and staging for testing.
FYI: PR #1672 also includes testing procedures to forge your referrer for local testing this code.
|
non_process
|
high priority if a user s referrer isn t from cafc redirect them to cafc right now our app accepts a new visitor once an hour when it is time for a new visitor we accept them regardless of their referrer once we ve had a new visitor we do not let anyone in for an hour our app gets a lot of traffic without a valid referrer bots webcrawlers etc to prevent this traffic from blocking valid traffic code was added in to only increment availabledata numberofrequests and availabledata lastrequested if the user had a valid referrer however we still allow this invalid traffic to access the app but this traffic is not counted towards the per hour user limit however these bots webcrawlers etc are messing with our google analytics analysis this code needs to be changed redirect anyone who does not have a valid referrer back to cafc add a environment variable to we can disable this behaviour on our local dev and staging for testing fyi pr also includes testing procedures to forge your referrer for local testing this code
| 0
|
160,449
| 12,512,096,318
|
IssuesEvent
|
2020-06-02 21:55:28
|
certbot/certbot
|
https://api.github.com/repos/certbot/certbot
|
opened
|
Build, test, and deploy Certbot DNS plugin snaps in CI
|
area: pkging area: snaps area: testing
|
Blocked #7672 which tracks creating these plugin snaps.
I think we probably also want to block deploying the DNS plugin snaps on https://github.com/certbot/certbot/issues/7935 which tracks creating a EFF/Certbot snapcraft account.
|
1.0
|
Build, test, and deploy Certbot DNS plugin snaps in CI - Blocked #7672 which tracks creating these plugin snaps.
I think we probably also want to block deploying the DNS plugin snaps on https://github.com/certbot/certbot/issues/7935 which tracks creating a EFF/Certbot snapcraft account.
|
non_process
|
build test and deploy certbot dns plugin snaps in ci blocked which tracks creating these plugin snaps i think we probably also want to block deploying the dns plugin snaps on which tracks creating a eff certbot snapcraft account
| 0
|
90
| 2,534,772,475
|
IssuesEvent
|
2015-01-25 09:48:25
|
rhattersley/docbook2asciidoc
|
https://api.github.com/repos/rhattersley/docbook2asciidoc
|
opened
|
Preface: Revision history
|
pre-process
|
This section doesn't make sense with the proposed workflow. (And is incompatible with the removal of highlighting.)
|
1.0
|
Preface: Revision history - This section doesn't make sense with the proposed workflow. (And is incompatible with the removal of highlighting.)
|
process
|
preface revision history this section doesn t make sense with the proposed workflow and is incompatible with the removal of highlighting
| 1
|
899
| 3,358,003,616
|
IssuesEvent
|
2015-11-19 06:27:08
|
kerubistan/kerub
|
https://api.github.com/repos/kerubistan/kerub
|
closed
|
create kotlin utility for qemu-img
|
component:data processing component:scheduling enhancement priority: normal
|
Only basic operations
* info
* resize
* create
* convert
* snapshot create, list, delete
* check
|
1.0
|
create kotlin utility for qemu-img - Only basic operations
* info
* resize
* create
* convert
* snapshot create, list, delete
* check
|
process
|
create kotlin utility for qemu img only basic operations info resize create convert snapshot create list delete check
| 1
|
783,350
| 27,526,906,306
|
IssuesEvent
|
2023-03-06 18:46:34
|
intel/cve-bin-tool
|
https://api.github.com/repos/intel/cve-bin-tool
|
opened
|
fix: discrepancy between results on windows vs linux for test_SBOM
|
bug CI higher priority
|
* related: #2747
In the course of creating #2747 @metabiswadeep figured out that our SBOM tests were failing because windows and linux were reporting different numbers of cves:
> 91 CVEs are detected for glibc in windows, whereas 90 CVEs are detected in Linux. So I suppose some CVEs are not detected by Linux?
**There should not be any cases where the number of CVEs changes depending on which platform is used for scanning at this time, so this is a bug.**
(It is possible to have a CVE that impacts only one platform, but we explicitly avoid assuming that the platform used for scanning is the same platform that will run the code, so we should not be taking such data into account in the current version.)
To fix this bug:
- figure out why we're getting different results on different platforms. It may be related to the different line feeds in windows vs linux (`\r\n` vs `\n`) as that can change detection, but it could also be something completely different.
- if you don't have access to windows and linux on your own systems, you can use github actions **on your own fork** to experiment. Although you're welcome to open a draft PR while you experiment, you don't need to open a PR to run the tests -- you should be able to run them directly on your branch.
- fix it so they both give the correct result, whatever that may be.
- fix the test updated in #2747 so that it behaves correctly. Right now it has bad logic that makes that portion of the test basically non-functional: it will pass no matter how many CVEs the code finds as it is currently written. It will either need to be reverted to something closer to its previous state or replaced with something better that actually works correctly.
A note for new contributors: I don't expect this to be an easy bug. I don't have any answers about how to fix it or any insights that I haven't included here. If you can't figure out how to get started in investigating on your own, please move on to another bug.
|
1.0
|
fix: discrepancy between results on windows vs linux for test_SBOM - * related: #2747
In the course of creating #2747 @metabiswadeep figured out that our SBOM tests were failing because windows and linux were reporting different numbers of cves:
> 91 CVEs are detected for glibc in windows, whereas 90 CVEs are detected in Linux. So I suppose some CVEs are not detected by Linux?
**There should not be any cases where the number of CVEs changes depending on which platform is used for scanning at this time, so this is a bug.**
(It is possible to have a CVE that impacts only one platform, but we explicitly avoid assuming that the platform used for scanning is the same platform that will run the code, so we should not be taking such data into account in the current version.)
To fix this bug:
- figure out why we're getting different results on different platforms. It may be related to the different line feeds in windows vs linux (`\r\n` vs `\n`) as that can change detection, but it could also be something completely different.
- if you don't have access to windows and linux on your own systems, you can use github actions **on your own fork** to experiment. Although you're welcome to open a draft PR while you experiment, you don't need to open a PR to run the tests -- you should be able to run them directly on your branch.
- fix it so they both give the correct result, whatever that may be.
- fix the test updated in #2747 so that it behaves correctly. Right now it has bad logic that makes that portion of the test basically non-functional: it will pass no matter how many CVEs the code finds as it is currently written. It will either need to be reverted to something closer to its previous state or replaced with something better that actually works correctly.
A note for new contributors: I don't expect this to be an easy bug. I don't have any answers about how to fix it or any insights that I haven't included here. If you can't figure out how to get started in investigating on your own, please move on to another bug.
|
non_process
|
fix discrepancy between results on windows vs linux for test sbom related in the course of creating metabiswadeep figured out that our sbom tests were failing because windows and linux were reporting different numbers of cves cves are detected for glibc in windows whereas cves are detected in linux so i suppose some cves are not detected by linux there should not be any cases where the number of cves changes depending on which platform is used for scanning at this time so this is a bug it is possible to have a cve that impacts only one platform but we explicitly avoid assuming that the platform used for scanning is the same platform that will run the code so we should not be taking such data into account in the current version to fix this bug figure out why we re getting different results on different platforms it may be related to the different line feeds in windows vs linux r n vs n as that can change detection but it could also be something completely different if you don t have access to windows and linux on your own systems you can use github actions on your own fork to experiment although you re welcome to open a draft pr while you experiment you don t need to open a pr to run the tests you should be able to run them directly on your branch fix it so they both give the correct result whatever that may be fix the test updated in so that it behaves correctly right now it has bad logic that makes that portion of the test basically non functional it will pass no matter how many cves the code finds as it is currently written it will either need to be reverted to something closer to its previous state or replaced with something better that actually works correctly a note for new contributors i don t expect this to be an easy bug i don t have any answers about how to fix it or any insights that i haven t included here if you can t figure out how to get started in investigating on your own please move on to another bug
| 0
|
235,720
| 25,962,050,021
|
IssuesEvent
|
2022-12-19 01:01:05
|
rvvergara/passionate-navigation
|
https://api.github.com/repos/rvvergara/passionate-navigation
|
opened
|
CVE-2022-23518 (Medium) detected in rails-html-sanitizer-1.3.0.gem
|
security vulnerability
|
## CVE-2022-23518 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>rails-html-sanitizer-1.3.0.gem</b></p></summary>
<p>HTML sanitization for Rails applications</p>
<p>Library home page: <a href="https://rubygems.org/gems/rails-html-sanitizer-1.3.0.gem">https://rubygems.org/gems/rails-html-sanitizer-1.3.0.gem</a></p>
<p>
Dependency Hierarchy:
- rspec-rails-3.9.0.gem (Root Library)
- actionpack-5.2.4.1.gem
- :x: **rails-html-sanitizer-1.3.0.gem** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/rvvergara/passionate-navigation/commit/29c41a363897f31c9626ab59a2c81019db726dbf">29c41a363897f31c9626ab59a2c81019db726dbf</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
rails-html-sanitizer is responsible for sanitizing HTML fragments in Rails applications. Versions >= 1.0.3, < 1.4.4 are vulnerable to cross-site scripting via data URIs when used in combination with Loofah >= 2.1.0. This issue is patched in version 1.4.4.
<p>Publish Date: 2022-12-14
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-23518>CVE-2022-23518</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/rails/rails-html-sanitizer/security/advisories/GHSA-mcvf-2q2m-x72m">https://github.com/rails/rails-html-sanitizer/security/advisories/GHSA-mcvf-2q2m-x72m</a></p>
<p>Release Date: 2022-12-14</p>
<p>Fix Resolution: rails-html-sanitizer - 1.4.4</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2022-23518 (Medium) detected in rails-html-sanitizer-1.3.0.gem - ## CVE-2022-23518 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>rails-html-sanitizer-1.3.0.gem</b></p></summary>
<p>HTML sanitization for Rails applications</p>
<p>Library home page: <a href="https://rubygems.org/gems/rails-html-sanitizer-1.3.0.gem">https://rubygems.org/gems/rails-html-sanitizer-1.3.0.gem</a></p>
<p>
Dependency Hierarchy:
- rspec-rails-3.9.0.gem (Root Library)
- actionpack-5.2.4.1.gem
- :x: **rails-html-sanitizer-1.3.0.gem** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/rvvergara/passionate-navigation/commit/29c41a363897f31c9626ab59a2c81019db726dbf">29c41a363897f31c9626ab59a2c81019db726dbf</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
rails-html-sanitizer is responsible for sanitizing HTML fragments in Rails applications. Versions >= 1.0.3, < 1.4.4 are vulnerable to cross-site scripting via data URIs when used in combination with Loofah >= 2.1.0. This issue is patched in version 1.4.4.
<p>Publish Date: 2022-12-14
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-23518>CVE-2022-23518</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/rails/rails-html-sanitizer/security/advisories/GHSA-mcvf-2q2m-x72m">https://github.com/rails/rails-html-sanitizer/security/advisories/GHSA-mcvf-2q2m-x72m</a></p>
<p>Release Date: 2022-12-14</p>
<p>Fix Resolution: rails-html-sanitizer - 1.4.4</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_process
|
cve medium detected in rails html sanitizer gem cve medium severity vulnerability vulnerable library rails html sanitizer gem html sanitization for rails applications library home page a href dependency hierarchy rspec rails gem root library actionpack gem x rails html sanitizer gem vulnerable library found in head commit a href found in base branch master vulnerability details rails html sanitizer is responsible for sanitizing html fragments in rails applications versions this issue is patched in version 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 rails html sanitizer step up your open source security game with mend
| 0
|
5,269
| 8,058,894,384
|
IssuesEvent
|
2018-08-02 20:01:42
|
AlexsLemonade/refinebio
|
https://api.github.com/repos/AlexsLemonade/refinebio
|
opened
|
Remove Non-Expression Column from Illumina NO_OP
|
illumina beadchip processor smasher
|
### Context
During the Jackiecrunch, it was discovered that samples such as `GSM1089291-tbl-1.txt` contain a column field, likely a p-value:
```
ILMN_1885639 10.0000 0.7931
ILMN_2209417 10.0000 0.2029
ILMN_1765401 152.0873 0.0000
```
That apparently survive the gene conversion step:
```
ENSEMBL 10.0000 0.7931
ENSG00000105675 10 0.2029
ENSG00000085721 152.0873 0
```
We don't want these value as they will muck up the smasher.
### Problem or idea
How do we determine which is the correct column to keep? At what step should the extra data be chucked away?
### Solution or next step
Determine above then implement.
### New Issue Checklist
- [ ] The title is short and descriptive.
- [ ] You have explained the context that led you to write this issue.
- [ ] You have reported a problem or idea.
- [ ] You have proposed a solution or next step.
|
1.0
|
Remove Non-Expression Column from Illumina NO_OP - ### Context
During the Jackiecrunch, it was discovered that samples such as `GSM1089291-tbl-1.txt` contain a column field, likely a p-value:
```
ILMN_1885639 10.0000 0.7931
ILMN_2209417 10.0000 0.2029
ILMN_1765401 152.0873 0.0000
```
That apparently survive the gene conversion step:
```
ENSEMBL 10.0000 0.7931
ENSG00000105675 10 0.2029
ENSG00000085721 152.0873 0
```
We don't want these value as they will muck up the smasher.
### Problem or idea
How do we determine which is the correct column to keep? At what step should the extra data be chucked away?
### Solution or next step
Determine above then implement.
### New Issue Checklist
- [ ] The title is short and descriptive.
- [ ] You have explained the context that led you to write this issue.
- [ ] You have reported a problem or idea.
- [ ] You have proposed a solution or next step.
|
process
|
remove non expression column from illumina no op context during the jackiecrunch it was discovered that samples such as tbl txt contain a column field likely a p value ilmn ilmn ilmn that apparently survive the gene conversion step ensembl we don t want these value as they will muck up the smasher problem or idea how do we determine which is the correct column to keep at what step should the extra data be chucked away solution or next step determine above then implement new issue checklist the title is short and descriptive you have explained the context that led you to write this issue you have reported a problem or idea you have proposed a solution or next step
| 1
|
89,518
| 17,946,844,135
|
IssuesEvent
|
2021-09-12 00:33:15
|
sourcegraph/sourcegraph
|
https://api.github.com/repos/sourcegraph/sourcegraph
|
closed
|
Code intel: loading spinner (sometimes) doesn't appear when visiting a deep link
|
bug code-nav team/frontend-platform
|
- Sideload an extension that takes more than 1.2s to return a hover and definition (e.g. add `delay(2000)` to basic-code-intel's `definition()` function)
- Visit https://sourcegraph.com/github.com/gorilla/mux@c5c6c98bc25355028a63748a498942a6398ccd22/-/blob/mux.go#L24:19
- Notice that the loading spinner doesn't appear after 1.2s
I believe this happens because no providers are registered when the page first loads, resulting in a `null` definition immediately, which cancels the loading spinner.
|
1.0
|
Code intel: loading spinner (sometimes) doesn't appear when visiting a deep link - - Sideload an extension that takes more than 1.2s to return a hover and definition (e.g. add `delay(2000)` to basic-code-intel's `definition()` function)
- Visit https://sourcegraph.com/github.com/gorilla/mux@c5c6c98bc25355028a63748a498942a6398ccd22/-/blob/mux.go#L24:19
- Notice that the loading spinner doesn't appear after 1.2s
I believe this happens because no providers are registered when the page first loads, resulting in a `null` definition immediately, which cancels the loading spinner.
|
non_process
|
code intel loading spinner sometimes doesn t appear when visiting a deep link sideload an extension that takes more than to return a hover and definition e g add delay to basic code intel s definition function visit notice that the loading spinner doesn t appear after i believe this happens because no providers are registered when the page first loads resulting in a null definition immediately which cancels the loading spinner
| 0
|
16,098
| 20,269,692,055
|
IssuesEvent
|
2022-02-15 15:11:59
|
decidim/decidim
|
https://api.github.com/repos/decidim/decidim
|
closed
|
Fix characters not encoded in highlighted participatory processes groups title
|
type: bug module: participatory processes
|
**Describe the bug**
Highlighted participatory processes groups who's title contain chars that are html escaped, render the chars double escaped thus producing D' diacritics.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to 'https://try.decidim.org/processes?locale=es'
2. See error on "Dolores quo'd commodi." PP group title.
**Expected behavior**
Add .html_safe to card title
**Screenshots**
<img width="607" alt="Capture d’écran 2022-02-11 à 16 11 36" src="https://user-images.githubusercontent.com/52420208/153617009-955e1ad2-e166-4ee0-ab69-b4163beaf5d9.png">
**Extra data (please complete the following information):**
- Decidim Version: [ Decidim 0.26.0.rc2]
- Decidim installation: [[try.decidim.org](https://try.decidim.org)]
**Additional context**
It was fixed for highlighted processes in https://github.com/decidim/decidim/pull/6798
|
1.0
|
Fix characters not encoded in highlighted participatory processes groups title - **Describe the bug**
Highlighted participatory processes groups who's title contain chars that are html escaped, render the chars double escaped thus producing D' diacritics.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to 'https://try.decidim.org/processes?locale=es'
2. See error on "Dolores quo'd commodi." PP group title.
**Expected behavior**
Add .html_safe to card title
**Screenshots**
<img width="607" alt="Capture d’écran 2022-02-11 à 16 11 36" src="https://user-images.githubusercontent.com/52420208/153617009-955e1ad2-e166-4ee0-ab69-b4163beaf5d9.png">
**Extra data (please complete the following information):**
- Decidim Version: [ Decidim 0.26.0.rc2]
- Decidim installation: [[try.decidim.org](https://try.decidim.org)]
**Additional context**
It was fixed for highlighted processes in https://github.com/decidim/decidim/pull/6798
|
process
|
fix characters not encoded in highlighted participatory processes groups title describe the bug highlighted participatory processes groups who s title contain chars that are html escaped render the chars double escaped thus producing d diacritics to reproduce steps to reproduce the behavior go to see error on dolores quo d commodi pp group title expected behavior add html safe to card title screenshots img width alt capture d’écran à src extra data please complete the following information decidim version decidim installation additional context it was fixed for highlighted processes in
| 1
|
22,502
| 15,225,692,208
|
IssuesEvent
|
2021-02-18 07:45:53
|
wazuh/wazuh-documentation
|
https://api.github.com/repos/wazuh/wazuh-documentation
|
closed
|
Create release notes for Wazuh v4.1.0
|
priority: highest type: infrastructure
|
Hello team!
The aim of this issue is to create the release notes for Wazuh v4.1.0
Regards,
David
|
1.0
|
Create release notes for Wazuh v4.1.0 - Hello team!
The aim of this issue is to create the release notes for Wazuh v4.1.0
Regards,
David
|
non_process
|
create release notes for wazuh hello team the aim of this issue is to create the release notes for wazuh regards david
| 0
|
17,906
| 23,887,837,259
|
IssuesEvent
|
2022-09-08 09:05:55
|
apache/arrow-rs
|
https://api.github.com/repos/apache/arrow-rs
|
closed
|
Intermittent S3 emulator test failure `message: "Missing information for upload part 2"`
|
bug development-process object-store
|
**Describe the bug**
Intermittently, the `object_store` Emulator Tests test fails like this
```
thread 'aws::tests::s3_test' panicked at 'called `Result::unwrap()` on an `Err` value: Custom { kind: Other, error: HttpDispatch(HttpDispatchError { message: "Missing information for upload part 2" }) }', object_store/src/aws.rs:1277:59
```
Here is an example failure: https://github.com/apache/arrow-rs/runs/7639063643?check_suite_focus=true that then passed on the subsequent run: https://github.com/apache/arrow-rs/runs/7639161157?check_suite_focus=true
**To Reproduce**
Not sure
**Expected behavior**
Test should pass or fail consistently
**Additional context**
<!--
Add any other context about the problem here.
-->
|
1.0
|
Intermittent S3 emulator test failure `message: "Missing information for upload part 2"` - **Describe the bug**
Intermittently, the `object_store` Emulator Tests test fails like this
```
thread 'aws::tests::s3_test' panicked at 'called `Result::unwrap()` on an `Err` value: Custom { kind: Other, error: HttpDispatch(HttpDispatchError { message: "Missing information for upload part 2" }) }', object_store/src/aws.rs:1277:59
```
Here is an example failure: https://github.com/apache/arrow-rs/runs/7639063643?check_suite_focus=true that then passed on the subsequent run: https://github.com/apache/arrow-rs/runs/7639161157?check_suite_focus=true
**To Reproduce**
Not sure
**Expected behavior**
Test should pass or fail consistently
**Additional context**
<!--
Add any other context about the problem here.
-->
|
process
|
intermittent emulator test failure message missing information for upload part describe the bug intermittently the object store emulator tests test fails like this thread aws tests test panicked at called result unwrap on an err value custom kind other error httpdispatch httpdispatcherror message missing information for upload part object store src aws rs here is an example failure that then passed on the subsequent run to reproduce not sure expected behavior test should pass or fail consistently additional context add any other context about the problem here
| 1
|
5,175
| 7,959,870,459
|
IssuesEvent
|
2018-07-13 03:42:30
|
GoogleCloudPlatform/google-cloud-python
|
https://api.github.com/repos/GoogleCloudPlatform/google-cloud-python
|
closed
|
Bigtable: new system test failure
|
api: bigtable testing type: process
|
#5513 caused a new (non-flaky, AFAICT) [system test failure](https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/7142):
```python
def test_create_table_with_split_keys(self):
temp_table_id = 'foo-bar-baz-split-table'
initial_split_keys = [b'split_key_1', b'split_key_10',
b'split_key_20', b'']
temp_table = Config.INSTANCE.table(temp_table_id)
temp_table.create(initial_split_keys=initial_split_keys)
self.tables_to_delete.append(temp_table)
# Read Sample Row Keys for created splits
sample_row_keys = temp_table.sample_row_keys()
self.assertEqual(set([srk.row_key for srk in sample_row_keys]),
> set(initial_split_keys))
E AssertionError: Items in the second set but not the first:
E 'split_key_1'
E 'split_key_10'
E 'split_key_20'
```
|
1.0
|
Bigtable: new system test failure - #5513 caused a new (non-flaky, AFAICT) [system test failure](https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/7142):
```python
def test_create_table_with_split_keys(self):
temp_table_id = 'foo-bar-baz-split-table'
initial_split_keys = [b'split_key_1', b'split_key_10',
b'split_key_20', b'']
temp_table = Config.INSTANCE.table(temp_table_id)
temp_table.create(initial_split_keys=initial_split_keys)
self.tables_to_delete.append(temp_table)
# Read Sample Row Keys for created splits
sample_row_keys = temp_table.sample_row_keys()
self.assertEqual(set([srk.row_key for srk in sample_row_keys]),
> set(initial_split_keys))
E AssertionError: Items in the second set but not the first:
E 'split_key_1'
E 'split_key_10'
E 'split_key_20'
```
|
process
|
bigtable new system test failure caused a new non flaky afaict python def test create table with split keys self temp table id foo bar baz split table initial split keys b split key b split key b split key b temp table config instance table temp table id temp table create initial split keys initial split keys self tables to delete append temp table read sample row keys for created splits sample row keys temp table sample row keys self assertequal set set initial split keys e assertionerror items in the second set but not the first e split key e split key e split key
| 1
|
17,998
| 24,016,405,732
|
IssuesEvent
|
2022-09-15 01:26:49
|
openxla/stablehlo
|
https://api.github.com/repos/openxla/stablehlo
|
opened
|
Decide what to do with build warnings
|
Process
|
MLIR-HLO has a problem with build warning spew (https://github.com/tensorflow/mlir-hlo/issues/43), and we're starting to have an issue with this as well. One possibility to address this would be to compile with `-Werror`.
|
1.0
|
Decide what to do with build warnings - MLIR-HLO has a problem with build warning spew (https://github.com/tensorflow/mlir-hlo/issues/43), and we're starting to have an issue with this as well. One possibility to address this would be to compile with `-Werror`.
|
process
|
decide what to do with build warnings mlir hlo has a problem with build warning spew and we re starting to have an issue with this as well one possibility to address this would be to compile with werror
| 1
|
284,700
| 30,913,670,668
|
IssuesEvent
|
2023-08-05 02:33:51
|
Nivaskumark/kernel_v4.19.72_old
|
https://api.github.com/repos/Nivaskumark/kernel_v4.19.72_old
|
reopened
|
CVE-2020-0404 (Medium) detected in linux-yoctov5.4.51
|
Mend: dependency security vulnerability
|
## CVE-2020-0404 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-yoctov5.4.51</b></p></summary>
<p>
<p>Yocto Linux Embedded kernel</p>
<p>Library home page: <a href=https://git.yoctoproject.org/git/linux-yocto>https://git.yoctoproject.org/git/linux-yocto</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Nivaskumark/kernel_v4.19.72/commit/ce49083a1c14be2d13cb5e878257d293e6c748bc">ce49083a1c14be2d13cb5e878257d293e6c748bc</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/media/usb/uvc/uvc_driver.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
In uvc_scan_chain_forward of uvc_driver.c, there is a possible linked list corruption due to an unusual root cause. This could lead to local escalation of privilege in the kernel with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-111893654References: Upstream kernel
<p>Publish Date: 2020-09-17
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-0404>CVE-2020-0404</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2020-09-17</p>
<p>Fix Resolution: v4.4.214,v4.9.214,v4.14.171,v4.19.103,v5.4.19,v5.5.3,v5.6-rc1</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-2020-0404 (Medium) detected in linux-yoctov5.4.51 - ## CVE-2020-0404 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-yoctov5.4.51</b></p></summary>
<p>
<p>Yocto Linux Embedded kernel</p>
<p>Library home page: <a href=https://git.yoctoproject.org/git/linux-yocto>https://git.yoctoproject.org/git/linux-yocto</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Nivaskumark/kernel_v4.19.72/commit/ce49083a1c14be2d13cb5e878257d293e6c748bc">ce49083a1c14be2d13cb5e878257d293e6c748bc</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/media/usb/uvc/uvc_driver.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
In uvc_scan_chain_forward of uvc_driver.c, there is a possible linked list corruption due to an unusual root cause. This could lead to local escalation of privilege in the kernel with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-111893654References: Upstream kernel
<p>Publish Date: 2020-09-17
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-0404>CVE-2020-0404</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2020-09-17</p>
<p>Fix Resolution: v4.4.214,v4.9.214,v4.14.171,v4.19.103,v5.4.19,v5.5.3,v5.6-rc1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_process
|
cve medium detected in linux cve medium severity vulnerability vulnerable library linux yocto linux embedded kernel library home page a href found in head commit a href found in base branch master vulnerable source files drivers media usb uvc uvc driver c vulnerability details in uvc scan chain forward of uvc driver c there is a possible linked list corruption due to an unusual root cause this could lead to local escalation of privilege in the kernel with no additional execution privileges needed user interaction is not needed for exploitation product androidversions android kernelandroid id a upstream kernel publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version release date fix resolution step up your open source security game with mend
| 0
|
2,265
| 2,602,207,614
|
IssuesEvent
|
2015-02-24 06:02:32
|
INCF/nineml
|
https://api.github.com/repos/INCF/nineml
|
reopened
|
Do we need a separate “AnalogOut” element to match “EventOut” instead of just using Alias/StateVariable’?
|
design choice specification
|
This is mainly a stylistic/readability issue, which in most cases will mean just replacing one of the Alias tags with AnalogOut (except when the AnalogPort is connected directly to a state variable when you will need to create an extra tag). However, it would perhaps be useful when it comes to simulator implementation to know which values need to be returned and it should at least help the AnalogOuts visually stand out from the Alias’, of which there could be many.
|
1.0
|
Do we need a separate “AnalogOut” element to match “EventOut” instead of just using Alias/StateVariable’? - This is mainly a stylistic/readability issue, which in most cases will mean just replacing one of the Alias tags with AnalogOut (except when the AnalogPort is connected directly to a state variable when you will need to create an extra tag). However, it would perhaps be useful when it comes to simulator implementation to know which values need to be returned and it should at least help the AnalogOuts visually stand out from the Alias’, of which there could be many.
|
non_process
|
do we need a separate “analogout” element to match “eventout” instead of just using alias statevariable’ this is mainly a stylistic readability issue which in most cases will mean just replacing one of the alias tags with analogout except when the analogport is connected directly to a state variable when you will need to create an extra tag however it would perhaps be useful when it comes to simulator implementation to know which values need to be returned and it should at least help the analogouts visually stand out from the alias’ of which there could be many
| 0
|
438,935
| 30,669,981,519
|
IssuesEvent
|
2023-07-25 21:28:37
|
rancher/ecm-distro-tools
|
https://api.github.com/repos/rancher/ecm-distro-tools
|
closed
|
Document go updates resulting from k3s patch releases
|
documentation
|
The k3s release documentation should include steps to update the go version used in k3s.
|
1.0
|
Document go updates resulting from k3s patch releases - The k3s release documentation should include steps to update the go version used in k3s.
|
non_process
|
document go updates resulting from patch releases the release documentation should include steps to update the go version used in
| 0
|
18,998
| 24,993,784,754
|
IssuesEvent
|
2022-11-02 21:22:10
|
aiidateam/aiida-core
|
https://api.github.com/repos/aiidateam/aiida-core
|
closed
|
Why `get_function_source_code` return source file of the function not the source function itself?
|
priority/nice-to-have topic/processes
|
https://github.com/aiidateam/aiida-core/blob/06063e7c38b6e40d3d2fbafe84e4e7f6adc8782a/aiida/orm/utils/mixins.py#L108-L113
Would this more make sense if the source code of function rather than the source of the file is returned?
Besides, if I understand it correctly, every process function will be stored along with a source file in the repository. Is that too redundant to store the same files every time when the `ProcessNode` call and store?
|
1.0
|
Why `get_function_source_code` return source file of the function not the source function itself? - https://github.com/aiidateam/aiida-core/blob/06063e7c38b6e40d3d2fbafe84e4e7f6adc8782a/aiida/orm/utils/mixins.py#L108-L113
Would this more make sense if the source code of function rather than the source of the file is returned?
Besides, if I understand it correctly, every process function will be stored along with a source file in the repository. Is that too redundant to store the same files every time when the `ProcessNode` call and store?
|
process
|
why get function source code return source file of the function not the source function itself would this more make sense if the source code of function rather than the source of the file is returned besides if i understand it correctly every process function will be stored along with a source file in the repository is that too redundant to store the same files every time when the processnode call and store
| 1
|
80,924
| 7,761,168,766
|
IssuesEvent
|
2018-06-01 08:59:33
|
Nineclown/The-Convenient-ATM
|
https://api.github.com/repos/Nineclown/The-Convenient-ATM
|
closed
|
현재 지폐 보유량을 변경하는 기능
|
Failed Test pass
|
nonfunctional requirement에 따르면
잘못된 값을 입력하면 유저가 즉각적으로 알 수 있어야 하지만
지폐 보유량에 문자열을 입력하면 경고창이 실행되지 않는다.
T235: 현재 지폐 보유량을 변경하는 기능
https://jaehyun379.testrail.io/index.php?/tests/view/235
|
1.0
|
현재 지폐 보유량을 변경하는 기능 - nonfunctional requirement에 따르면
잘못된 값을 입력하면 유저가 즉각적으로 알 수 있어야 하지만
지폐 보유량에 문자열을 입력하면 경고창이 실행되지 않는다.
T235: 현재 지폐 보유량을 변경하는 기능
https://jaehyun379.testrail.io/index.php?/tests/view/235
|
non_process
|
현재 지폐 보유량을 변경하는 기능 nonfunctional requirement에 따르면 잘못된 값을 입력하면 유저가 즉각적으로 알 수 있어야 하지만 지폐 보유량에 문자열을 입력하면 경고창이 실행되지 않는다 현재 지폐 보유량을 변경하는 기능
| 0
|
3,261
| 6,339,974,882
|
IssuesEvent
|
2017-07-27 09:40:44
|
w3c/html
|
https://api.github.com/repos/w3c/html
|
closed
|
CfC: HTML 5.2 to Candidate Recommendation
|
process
|
This is a Call for Consensus to move the [18 July 2017 HTML 5.2 Working Draft](https://www.w3.org/TR/2017/WD-html52-20170718/) to Candidate Recommendation.
Please note the following features will be listed as "at-risk", and may be removed by the end of the CR period, if testing shows there is not likely interoperability of implementation:
* The `inputmode` attribute for `input` elements
*The `menu` and `menuitem` elements
* The `allow-presentation` sandboxing flag for the `sandbox` attribute of an `iframe`
* The `dialog` element
* The `datetime` state for the `input` element
* The plugin API
If you believe other items should be marked "at risk" please note them in issue #893
Approval can be marked with a thumbs up - if you vote against, please explain why in a comment.
Replies will be taken into consideration until the end of 26 July.
|
1.0
|
CfC: HTML 5.2 to Candidate Recommendation - This is a Call for Consensus to move the [18 July 2017 HTML 5.2 Working Draft](https://www.w3.org/TR/2017/WD-html52-20170718/) to Candidate Recommendation.
Please note the following features will be listed as "at-risk", and may be removed by the end of the CR period, if testing shows there is not likely interoperability of implementation:
* The `inputmode` attribute for `input` elements
*The `menu` and `menuitem` elements
* The `allow-presentation` sandboxing flag for the `sandbox` attribute of an `iframe`
* The `dialog` element
* The `datetime` state for the `input` element
* The plugin API
If you believe other items should be marked "at risk" please note them in issue #893
Approval can be marked with a thumbs up - if you vote against, please explain why in a comment.
Replies will be taken into consideration until the end of 26 July.
|
process
|
cfc html to candidate recommendation this is a call for consensus to move the to candidate recommendation please note the following features will be listed as at risk and may be removed by the end of the cr period if testing shows there is not likely interoperability of implementation the inputmode attribute for input elements the menu and menuitem elements the allow presentation sandboxing flag for the sandbox attribute of an iframe the dialog element the datetime state for the input element the plugin api if you believe other items should be marked at risk please note them in issue approval can be marked with a thumbs up if you vote against please explain why in a comment replies will be taken into consideration until the end of july
| 1
|
9,236
| 12,264,767,117
|
IssuesEvent
|
2020-05-07 05:25:54
|
cypress-io/cypress
|
https://api.github.com/repos/cypress-io/cypress
|
opened
|
Internal e2e test failing - async plugins error
|
process: tests type: chore
|
### Current behavior:
Seen this failure a couple of times now in our `server/test/e2e/3_plugins_spec.js`
https://circleci.com/gh/cypress-io/cypress/316940
<img width="810" alt="Screen Shot 2020-05-07 at 11 52 34 AM" src="https://user-images.githubusercontent.com/1271364/81257465-59b8e500-9059-11ea-9ba0-40007e1a0e93.png">
### Versions
4.6.0-prerelease - `develop` branch
|
1.0
|
Internal e2e test failing - async plugins error - ### Current behavior:
Seen this failure a couple of times now in our `server/test/e2e/3_plugins_spec.js`
https://circleci.com/gh/cypress-io/cypress/316940
<img width="810" alt="Screen Shot 2020-05-07 at 11 52 34 AM" src="https://user-images.githubusercontent.com/1271364/81257465-59b8e500-9059-11ea-9ba0-40007e1a0e93.png">
### Versions
4.6.0-prerelease - `develop` branch
|
process
|
internal test failing async plugins error current behavior seen this failure a couple of times now in our server test plugins spec js img width alt screen shot at am src versions prerelease develop branch
| 1
|
11,462
| 14,286,715,027
|
IssuesEvent
|
2020-11-23 15:29:02
|
AlexsLemonade/refinebio-examples
|
https://api.github.com/repos/AlexsLemonade/refinebio-examples
|
opened
|
Create a template Rmd specifically for advanced topics/usage examples
|
advanced topics process
|
### Background
Context is #357 - please read the initial comment for that issue in detail!
### Problem
The advanced topics notebooks have a different audience and it stands to reason that those users will have a bit more experience with things like file paths and the different platforms. We can't assume that those users have gone through our other examples (e.g., we should still treat them as independent). We should try to strike a balance between making sure folks can get up and running with refine.bio data but give more information so they can understand whether an analysis is appropriate for their question.
### What potential "gotchas" do we know of?
I expect most gotchas will become apparent while we work our way through #357. Because we want to give users an idea about whether or not an advanced approach is right for them, I'm imagining a mostly blank section in the template that's about _why_ to use an analysis.
### What are the recommended next steps?
1. Add introductory material to our first advanced topic example, which is WGCNA (#357).
2. Create a template Rmd specifically for our advanced topics examples.
3. Update CONTRIBUTING.md to reflect that there will be two templates to choose from.
|
1.0
|
Create a template Rmd specifically for advanced topics/usage examples - ### Background
Context is #357 - please read the initial comment for that issue in detail!
### Problem
The advanced topics notebooks have a different audience and it stands to reason that those users will have a bit more experience with things like file paths and the different platforms. We can't assume that those users have gone through our other examples (e.g., we should still treat them as independent). We should try to strike a balance between making sure folks can get up and running with refine.bio data but give more information so they can understand whether an analysis is appropriate for their question.
### What potential "gotchas" do we know of?
I expect most gotchas will become apparent while we work our way through #357. Because we want to give users an idea about whether or not an advanced approach is right for them, I'm imagining a mostly blank section in the template that's about _why_ to use an analysis.
### What are the recommended next steps?
1. Add introductory material to our first advanced topic example, which is WGCNA (#357).
2. Create a template Rmd specifically for our advanced topics examples.
3. Update CONTRIBUTING.md to reflect that there will be two templates to choose from.
|
process
|
create a template rmd specifically for advanced topics usage examples background context is please read the initial comment for that issue in detail problem the advanced topics notebooks have a different audience and it stands to reason that those users will have a bit more experience with things like file paths and the different platforms we can t assume that those users have gone through our other examples e g we should still treat them as independent we should try to strike a balance between making sure folks can get up and running with refine bio data but give more information so they can understand whether an analysis is appropriate for their question what potential gotchas do we know of i expect most gotchas will become apparent while we work our way through because we want to give users an idea about whether or not an advanced approach is right for them i m imagining a mostly blank section in the template that s about why to use an analysis what are the recommended next steps add introductory material to our first advanced topic example which is wgcna create a template rmd specifically for our advanced topics examples update contributing md to reflect that there will be two templates to choose from
| 1
|
64,684
| 14,677,157,098
|
IssuesEvent
|
2020-12-30 22:20:34
|
kadirselcuk/test-infra
|
https://api.github.com/repos/kadirselcuk/test-infra
|
opened
|
CVE-2020-8911 (Medium) detected in github.com/aws/aws-sdk-go/service/s3-82ad808f2307df0776c038bfd7ea85440a35c02e
|
security vulnerability
|
## CVE-2020-8911 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>github.com/aws/aws-sdk-go/service/s3-82ad808f2307df0776c038bfd7ea85440a35c02e</b></p></summary>
<p>AWS SDK for the Go programming language.</p>
<p>
Dependency Hierarchy:
- :x: **github.com/aws/aws-sdk-go/service/s3-82ad808f2307df0776c038bfd7ea85440a35c02e** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kadirselcuk/test-infra/commit/53a75214732f7d3d2f74e3738703a9d0ef54db9f">53a75214732f7d3d2f74e3738703a9d0ef54db9f</a></p>
<p>Found in base branch: <b>autoupdate</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>
A padding oracle vulnerability exists in the AWS S3 Crypto SDK for GoLang versions prior to V2. The SDK allows users to encrypt files with AES-CBC without computing a Message Authentication Code (MAC), which then allows an attacker who has write access to the target's S3 bucket and can observe whether or not an endpoint with access to the key can decrypt a file, they can reconstruct the plaintext with (on average) 128*length (plaintext) queries to the endpoint, by exploiting CBC's ability to manipulate the bytes of the next block and PKCS5 padding errors. It is recommended to update your SDK to V2 or later, and re-encrypt your files.
<p>Publish Date: 2020-08-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8911>CVE-2020-8911</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8911">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8911</a></p>
<p>Release Date: 2020-07-21</p>
<p>Fix Resolution: v1.34.1</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-8911 (Medium) detected in github.com/aws/aws-sdk-go/service/s3-82ad808f2307df0776c038bfd7ea85440a35c02e - ## CVE-2020-8911 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>github.com/aws/aws-sdk-go/service/s3-82ad808f2307df0776c038bfd7ea85440a35c02e</b></p></summary>
<p>AWS SDK for the Go programming language.</p>
<p>
Dependency Hierarchy:
- :x: **github.com/aws/aws-sdk-go/service/s3-82ad808f2307df0776c038bfd7ea85440a35c02e** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kadirselcuk/test-infra/commit/53a75214732f7d3d2f74e3738703a9d0ef54db9f">53a75214732f7d3d2f74e3738703a9d0ef54db9f</a></p>
<p>Found in base branch: <b>autoupdate</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>
A padding oracle vulnerability exists in the AWS S3 Crypto SDK for GoLang versions prior to V2. The SDK allows users to encrypt files with AES-CBC without computing a Message Authentication Code (MAC), which then allows an attacker who has write access to the target's S3 bucket and can observe whether or not an endpoint with access to the key can decrypt a file, they can reconstruct the plaintext with (on average) 128*length (plaintext) queries to the endpoint, by exploiting CBC's ability to manipulate the bytes of the next block and PKCS5 padding errors. It is recommended to update your SDK to V2 or later, and re-encrypt your files.
<p>Publish Date: 2020-08-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8911>CVE-2020-8911</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8911">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8911</a></p>
<p>Release Date: 2020-07-21</p>
<p>Fix Resolution: v1.34.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_process
|
cve medium detected in github com aws aws sdk go service cve medium severity vulnerability vulnerable library github com aws aws sdk go service aws sdk for the go programming language dependency hierarchy x github com aws aws sdk go service vulnerable library found in head commit a href found in base branch autoupdate vulnerability details a padding oracle vulnerability exists in the aws crypto sdk for golang versions prior to the sdk allows users to encrypt files with aes cbc without computing a message authentication code mac which then allows an attacker who has write access to the target s bucket and can observe whether or not an endpoint with access to the key can decrypt a file they can reconstruct the plaintext with on average length plaintext queries to the endpoint by exploiting cbc s ability to manipulate the bytes of the next block and padding errors it is recommended to update your sdk to or later and re encrypt your files publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity high privileges required low user interaction none scope changed impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource
| 0
|
5,503
| 8,375,005,810
|
IssuesEvent
|
2018-10-05 15:11:16
|
allinurl/goaccess
|
https://api.github.com/repos/allinurl/goaccess
|
closed
|
Question regarding log-format
|
log-processing question
|
First of, I would like to thank you for building this awesome and free app. I just want to inquire how virtual hostname or IP works?
For example I have logs like:
**66.249.71.43** - - [01/Oct/2018:07:14:57 +0000] "GET / HTTP/1.1" 401 4230 "-" "Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.96 Mobile Safari/537.36 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"
**hostname-66.domain.com** - - [01/Oct/2018:07:14:57 +0000] "GET / HTTP/1.1" 401 4230 "-" "Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.96 Mobile Safari/537.36 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"
%h tag the second sample log as invalid requests and %v won't work. Is there something like %h|%v or something like that?
Thanks.
|
1.0
|
Question regarding log-format - First of, I would like to thank you for building this awesome and free app. I just want to inquire how virtual hostname or IP works?
For example I have logs like:
**66.249.71.43** - - [01/Oct/2018:07:14:57 +0000] "GET / HTTP/1.1" 401 4230 "-" "Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.96 Mobile Safari/537.36 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"
**hostname-66.domain.com** - - [01/Oct/2018:07:14:57 +0000] "GET / HTTP/1.1" 401 4230 "-" "Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.96 Mobile Safari/537.36 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"
%h tag the second sample log as invalid requests and %v won't work. Is there something like %h|%v or something like that?
Thanks.
|
process
|
question regarding log format first of i would like to thank you for building this awesome and free app i just want to inquire how virtual hostname or ip works for example i have logs like get http mozilla linux android nexus build applewebkit khtml like gecko chrome mobile safari compatible googlebot hostname domain com get http mozilla linux android nexus build applewebkit khtml like gecko chrome mobile safari compatible googlebot h tag the second sample log as invalid requests and v won t work is there something like h v or something like that thanks
| 1
|
5,337
| 8,160,311,876
|
IssuesEvent
|
2018-08-24 00:37:09
|
material-components/material-components-ios
|
https://api.github.com/repos/material-components/material-components-ios
|
reopened
|
Perform a heavy-duty instrumentation pass on the catalog and demo apps
|
app:Catalog app:Pesto app:Shrine good first issue type:Process
|
### Context
We want our components to consume as few cycles as is reasonably possible so that applications have more compute time per screen refresh.
### Potential work ahead
For each of our applications:
- Deploy the app to a device and run the CPU profiling instrument.
- Navigate through the entire application.
- Check the profiling results and identify any surprising metrics.
- File bugs identifying the performance problem.
|
1.0
|
Perform a heavy-duty instrumentation pass on the catalog and demo apps - ### Context
We want our components to consume as few cycles as is reasonably possible so that applications have more compute time per screen refresh.
### Potential work ahead
For each of our applications:
- Deploy the app to a device and run the CPU profiling instrument.
- Navigate through the entire application.
- Check the profiling results and identify any surprising metrics.
- File bugs identifying the performance problem.
|
process
|
perform a heavy duty instrumentation pass on the catalog and demo apps context we want our components to consume as few cycles as is reasonably possible so that applications have more compute time per screen refresh potential work ahead for each of our applications deploy the app to a device and run the cpu profiling instrument navigate through the entire application check the profiling results and identify any surprising metrics file bugs identifying the performance problem
| 1
|
98,752
| 8,685,007,078
|
IssuesEvent
|
2018-12-03 05:44:11
|
muqeed11/FXTesting
|
https://api.github.com/repos/muqeed11/FXTesting
|
opened
|
FX UAT TEST : ApiV1EventsRegisterGetNoParams
|
FX UAT TEST
|
Project : FX UAT TEST
Job : UAT
Env : UAT
Region : US_WEST
Result : fail
Status Code : 500
Headers : {}
Endpoint : http://13.56.210.25/api/v1/events/register
Request :
Response :
Error while extracting response for type [class java.lang.String] and content type [text/event-stream;charset=UTF-8]; nested exception is java.net.SocketTimeoutException: Read timed out
Logs :
Assertion [@StatusCode == 200] resolved-to [500 == 200] result [Failed]
--- FX Bot ---
|
1.0
|
FX UAT TEST : ApiV1EventsRegisterGetNoParams - Project : FX UAT TEST
Job : UAT
Env : UAT
Region : US_WEST
Result : fail
Status Code : 500
Headers : {}
Endpoint : http://13.56.210.25/api/v1/events/register
Request :
Response :
Error while extracting response for type [class java.lang.String] and content type [text/event-stream;charset=UTF-8]; nested exception is java.net.SocketTimeoutException: Read timed out
Logs :
Assertion [@StatusCode == 200] resolved-to [500 == 200] result [Failed]
--- FX Bot ---
|
non_process
|
fx uat test project fx uat test job uat env uat region us west result fail status code headers endpoint request response error while extracting response for type and content type nested exception is java net sockettimeoutexception read timed out logs assertion resolved to result fx bot
| 0
|
7,700
| 18,894,930,616
|
IssuesEvent
|
2021-11-15 16:50:19
|
MicrosoftDocs/architecture-center
|
https://api.github.com/repos/MicrosoftDocs/architecture-center
|
closed
|
Terraform code example for baseline AKS architecture
|
assigned-to-author triaged product-question architecture-center/svc reference-architecture/subsvc Pri3
|
For https://docs.microsoft.com/en-us/azure/architecture/reference-architectures/containers/aks/secure-baseline-aks#network-topology, is there a Terraform code reference for the implementation that would create all needed resources? What’s the list of subscriptions required for this implementation?
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 46723a24-75ac-f6e2-c172-d3827ca0b7d6
* Version Independent ID: c975744e-e594-5667-14b3-c38824bbe24c
* Content: [Baseline architecture for an AKS cluster - Azure Architecture Center](https://docs.microsoft.com/en-us/azure/architecture/reference-architectures/containers/aks/secure-baseline-aks#network-topology)
* Content Source: [docs/reference-architectures/containers/aks/secure-baseline-aks.yml](https://github.com/microsoftdocs/architecture-center/blob/master/docs/reference-architectures/containers/aks/secure-baseline-aks.yml)
* Service: **architecture-center**
* Sub-service: **reference-architecture**
* GitHub Login: @PageWriter-MSFT
* Microsoft Alias: **pnp**
|
2.0
|
Terraform code example for baseline AKS architecture - For https://docs.microsoft.com/en-us/azure/architecture/reference-architectures/containers/aks/secure-baseline-aks#network-topology, is there a Terraform code reference for the implementation that would create all needed resources? What’s the list of subscriptions required for this implementation?
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 46723a24-75ac-f6e2-c172-d3827ca0b7d6
* Version Independent ID: c975744e-e594-5667-14b3-c38824bbe24c
* Content: [Baseline architecture for an AKS cluster - Azure Architecture Center](https://docs.microsoft.com/en-us/azure/architecture/reference-architectures/containers/aks/secure-baseline-aks#network-topology)
* Content Source: [docs/reference-architectures/containers/aks/secure-baseline-aks.yml](https://github.com/microsoftdocs/architecture-center/blob/master/docs/reference-architectures/containers/aks/secure-baseline-aks.yml)
* Service: **architecture-center**
* Sub-service: **reference-architecture**
* GitHub Login: @PageWriter-MSFT
* Microsoft Alias: **pnp**
|
non_process
|
terraform code example for baseline aks architecture for is there a terraform code reference for the implementation that would create all needed resources what’s the list of subscriptions required for this implementation document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source service architecture center sub service reference architecture github login pagewriter msft microsoft alias pnp
| 0
|
816,589
| 30,603,657,880
|
IssuesEvent
|
2023-07-22 18:12:21
|
sef-global/scholarx-frontend
|
https://api.github.com/repos/sef-global/scholarx-frontend
|
opened
|
Implement the admin dashboard - edit email view
|
frontend priority: low admin
|
### Description
As part of this issue, we need to create the admin dashboard -edit email view, which should closely match the provided mockup. This will provide the admins with a way to view all the edit emails.
### Tasks
1. Set up the basic React components as required.
1. Implement the layout and design of the admin dashboard - edit email view, following the provided mockup.
1. Integrate the necessary components and assets to achieve the desired functionality and visual appearance.
1. Ensure responsiveness and compatibility across different devices and screen sizes.
Mockup: https://www.figma.com/file/nehm2ff8aR7NkPerg39fK9/ScholarX-V2-%7C-Wireframes?type=design&node-id=523%3A6&mode=design&t=MusZHQ3y31nKxoli-1
### Acceptance Criteria
- The user interface closely resembles the provided mockup.
- All required sections, elements, and content are present and displayed correctly.
- The interface is responsive and works well on various devices and screen sizes.
- The implementation follows best practices and coding standards.
- Unit tests are written.
|
1.0
|
Implement the admin dashboard - edit email view - ### Description
As part of this issue, we need to create the admin dashboard -edit email view, which should closely match the provided mockup. This will provide the admins with a way to view all the edit emails.
### Tasks
1. Set up the basic React components as required.
1. Implement the layout and design of the admin dashboard - edit email view, following the provided mockup.
1. Integrate the necessary components and assets to achieve the desired functionality and visual appearance.
1. Ensure responsiveness and compatibility across different devices and screen sizes.
Mockup: https://www.figma.com/file/nehm2ff8aR7NkPerg39fK9/ScholarX-V2-%7C-Wireframes?type=design&node-id=523%3A6&mode=design&t=MusZHQ3y31nKxoli-1
### Acceptance Criteria
- The user interface closely resembles the provided mockup.
- All required sections, elements, and content are present and displayed correctly.
- The interface is responsive and works well on various devices and screen sizes.
- The implementation follows best practices and coding standards.
- Unit tests are written.
|
non_process
|
implement the admin dashboard edit email view description as part of this issue we need to create the admin dashboard edit email view which should closely match the provided mockup this will provide the admins with a way to view all the edit emails tasks set up the basic react components as required implement the layout and design of the admin dashboard edit email view following the provided mockup integrate the necessary components and assets to achieve the desired functionality and visual appearance ensure responsiveness and compatibility across different devices and screen sizes mockup acceptance criteria the user interface closely resembles the provided mockup all required sections elements and content are present and displayed correctly the interface is responsive and works well on various devices and screen sizes the implementation follows best practices and coding standards unit tests are written
| 0
|
28,821
| 4,128,624,699
|
IssuesEvent
|
2016-06-10 07:29:34
|
ppy/osu-web
|
https://api.github.com/repos/ppy/osu-web
|
closed
|
Let's show more difficulty icons.
|
design
|
This looks plain silly and doesn't allow users to get the details they want. We should show how many we can fit and then use the "+n" for any more that can't fit.
|
1.0
|
Let's show more difficulty icons. - 
This looks plain silly and doesn't allow users to get the details they want. We should show how many we can fit and then use the "+n" for any more that can't fit.
|
non_process
|
let s show more difficulty icons this looks plain silly and doesn t allow users to get the details they want we should show how many we can fit and then use the n for any more that can t fit
| 0
|
16,180
| 20,625,900,430
|
IssuesEvent
|
2022-03-07 22:30:20
|
zotero/zotero
|
https://api.github.com/repos/zotero/zotero
|
opened
|
Search on parent item title/creator/year in Add Note window
|
Word Processor Integration
|
I haven't actually checked to make sure we're not doing this already, but if not, it seems like it would make it easier to find things.
(Thinking about this in relation to https://github.com/zotero/zotero/issues/2387.)
|
1.0
|
Search on parent item title/creator/year in Add Note window - I haven't actually checked to make sure we're not doing this already, but if not, it seems like it would make it easier to find things.
(Thinking about this in relation to https://github.com/zotero/zotero/issues/2387.)
|
process
|
search on parent item title creator year in add note window i haven t actually checked to make sure we re not doing this already but if not it seems like it would make it easier to find things thinking about this in relation to
| 1
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.