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
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
2,772
| 5,705,609,564
|
IssuesEvent
|
2017-04-18 09:00:12
|
symfony/symfony
|
https://api.github.com/repos/symfony/symfony
|
closed
|
[Process] Get stuck when run `ssh` with multiplexing
|
Bug Process Status: Needs Review Unconfirmed
|
| Q | A
| ---------------- | -----
| Bug report? | yes
| Feature request? | no
| BC Break report? | no
| RFC? | no
| Symfony version | 3.2.7
It works well with code:
```
$cmd='ssh root@xxx.com echo 1;';
$p = new Symfony\Component\Process\Process($cmd);
var_dump($p->run()); // returns 0 almost immediately
var_dump($p->getOutput());
```
But it gets stuck with code:
```
$cmd='ssh -o ControlMaster=auto -o ControlPersist=60 -o ControlPath=~/.ssh/deployer_mux root@xxx.com echo 1;';
$p = new Symfony\Component\Process\Process($cmd);
var_dump($p->run()); // doesn't return anything
```
and it throws an error after 1min:
```
Symfony\Component\Process\Exception\ProcessTimedOutException with message 'The process "ssh -o ControlMaster=auto -o ControlPersist=60 -o ControlPath=~/.ssh/deployer_mux root@xxx.com echo 1;" exceeded the timeout of 60 seconds.'
```
|
1.0
|
[Process] Get stuck when run `ssh` with multiplexing - | Q | A
| ---------------- | -----
| Bug report? | yes
| Feature request? | no
| BC Break report? | no
| RFC? | no
| Symfony version | 3.2.7
It works well with code:
```
$cmd='ssh root@xxx.com echo 1;';
$p = new Symfony\Component\Process\Process($cmd);
var_dump($p->run()); // returns 0 almost immediately
var_dump($p->getOutput());
```
But it gets stuck with code:
```
$cmd='ssh -o ControlMaster=auto -o ControlPersist=60 -o ControlPath=~/.ssh/deployer_mux root@xxx.com echo 1;';
$p = new Symfony\Component\Process\Process($cmd);
var_dump($p->run()); // doesn't return anything
```
and it throws an error after 1min:
```
Symfony\Component\Process\Exception\ProcessTimedOutException with message 'The process "ssh -o ControlMaster=auto -o ControlPersist=60 -o ControlPath=~/.ssh/deployer_mux root@xxx.com echo 1;" exceeded the timeout of 60 seconds.'
```
|
process
|
get stuck when run ssh with multiplexing q a bug report yes feature request no bc break report no rfc no symfony version it works well with code cmd ssh root xxx com echo p new symfony component process process cmd var dump p run returns almost immediately var dump p getoutput but it gets stuck with code cmd ssh o controlmaster auto o controlpersist o controlpath ssh deployer mux root xxx com echo p new symfony component process process cmd var dump p run doesn t return anything and it throws an error after symfony component process exception processtimedoutexception with message the process ssh o controlmaster auto o controlpersist o controlpath ssh deployer mux root xxx com echo exceeded the timeout of seconds
| 1
|
471,856
| 13,611,671,003
|
IssuesEvent
|
2020-09-23 09:11:45
|
Automattic/abacus
|
https://api.github.com/repos/Automattic/abacus
|
closed
|
Add basic metric creation page
|
[!priority] medium [component] experimenter interface [type] enhancement
|
Aaron edited:
Consider building metric details page first (#162). We can consider making the metric creation just be an empty metric details page.
## Metric creation:
- name (snake case, lowercase)
- description
- indicator for `is_higher_better` (checkbox or slider button for on/off)
- radio box for kind of metric (revenue vs conversion)
### Revenue metric:
- refund days dropdown (1, 3, 7, 30)
- transaction types checklist (can select multiple) (new purchase, recurring, cancelation, etc). Ping @aaronyan for full list.
- product slugs dropdown (but allow additional slugs to be added/removed with a +add product button)
- all fields optional (I think)
For future iteration, make refund days and transaction types options populated by API endpoint.
### Conversion metric:
- event name (form field, with future autocomplete) - allow events to be added/removed with a +add event button
- property name and values (form field with future autocomplete) - allow properties to be added/removed with a +add property button
- properties are attached to events and events can have multiple properties
- only one event name is required
|
1.0
|
Add basic metric creation page - Aaron edited:
Consider building metric details page first (#162). We can consider making the metric creation just be an empty metric details page.
## Metric creation:
- name (snake case, lowercase)
- description
- indicator for `is_higher_better` (checkbox or slider button for on/off)
- radio box for kind of metric (revenue vs conversion)
### Revenue metric:
- refund days dropdown (1, 3, 7, 30)
- transaction types checklist (can select multiple) (new purchase, recurring, cancelation, etc). Ping @aaronyan for full list.
- product slugs dropdown (but allow additional slugs to be added/removed with a +add product button)
- all fields optional (I think)
For future iteration, make refund days and transaction types options populated by API endpoint.
### Conversion metric:
- event name (form field, with future autocomplete) - allow events to be added/removed with a +add event button
- property name and values (form field with future autocomplete) - allow properties to be added/removed with a +add property button
- properties are attached to events and events can have multiple properties
- only one event name is required
|
non_process
|
add basic metric creation page aaron edited consider building metric details page first we can consider making the metric creation just be an empty metric details page metric creation name snake case lowercase description indicator for is higher better checkbox or slider button for on off radio box for kind of metric revenue vs conversion revenue metric refund days dropdown transaction types checklist can select multiple new purchase recurring cancelation etc ping aaronyan for full list product slugs dropdown but allow additional slugs to be added removed with a add product button all fields optional i think for future iteration make refund days and transaction types options populated by api endpoint conversion metric event name form field with future autocomplete allow events to be added removed with a add event button property name and values form field with future autocomplete allow properties to be added removed with a add property button properties are attached to events and events can have multiple properties only one event name is required
| 0
|
713,709
| 24,536,506,773
|
IssuesEvent
|
2022-10-11 21:18:40
|
dwyl/learn-postgresql
|
https://api.github.com/repos/dwyl/learn-postgresql
|
closed
|
Installation process on MacOS is outdated
|
enhancement help wanted priority-2 technical chore
|
Thank you for the repo, it's mighty useful!
I'm following the readme file and I noticed the installation process in MacOS is slightly different. The wizard now only calls for server initialization and it's up and running.
Additionally, the `psql` command line doesn't come "out-of-the-box" in recent versions and some commands to add it to the $PATH variable are needed.
I can pull a quick PR to fix this 😄 .
|
1.0
|
Installation process on MacOS is outdated - Thank you for the repo, it's mighty useful!
I'm following the readme file and I noticed the installation process in MacOS is slightly different. The wizard now only calls for server initialization and it's up and running.
Additionally, the `psql` command line doesn't come "out-of-the-box" in recent versions and some commands to add it to the $PATH variable are needed.
I can pull a quick PR to fix this 😄 .
|
non_process
|
installation process on macos is outdated thank you for the repo it s mighty useful i m following the readme file and i noticed the installation process in macos is slightly different the wizard now only calls for server initialization and it s up and running additionally the psql command line doesn t come out of the box in recent versions and some commands to add it to the path variable are needed i can pull a quick pr to fix this 😄
| 0
|
213,145
| 23,966,125,637
|
IssuesEvent
|
2022-09-13 01:14:10
|
panasalap/linux-4.1.15
|
https://api.github.com/repos/panasalap/linux-4.1.15
|
closed
|
CVE-2017-1000365 (High) detected in linux-stable-rtv4.1.33 - autoclosed
|
security vulnerability
|
## CVE-2017-1000365 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>
<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/panasalap/linux-4.1.15/commit/aae4c2fa46027fd4c477372871df090c6b94f3f1">aae4c2fa46027fd4c477372871df090c6b94f3f1</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The Linux Kernel imposes a size restriction on the arguments and environmental strings passed through RLIMIT_STACK/RLIM_INFINITY (1/4 of the size), but does not take the argument and environment pointers into account, which allows attackers to bypass this limitation. This affects Linux Kernel versions 4.11.5 and earlier. It appears that this feature was introduced in the Linux Kernel version 2.6.23.
<p>Publish Date: 2017-06-19
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-1000365>CVE-2017-1000365</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.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000365">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000365</a></p>
<p>Release Date: 2017-06-19</p>
<p>Fix Resolution: v4.12-rc7</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-2017-1000365 (High) detected in linux-stable-rtv4.1.33 - autoclosed - ## CVE-2017-1000365 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>
<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/panasalap/linux-4.1.15/commit/aae4c2fa46027fd4c477372871df090c6b94f3f1">aae4c2fa46027fd4c477372871df090c6b94f3f1</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The Linux Kernel imposes a size restriction on the arguments and environmental strings passed through RLIMIT_STACK/RLIM_INFINITY (1/4 of the size), but does not take the argument and environment pointers into account, which allows attackers to bypass this limitation. This affects Linux Kernel versions 4.11.5 and earlier. It appears that this feature was introduced in the Linux Kernel version 2.6.23.
<p>Publish Date: 2017-06-19
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-1000365>CVE-2017-1000365</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.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000365">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000365</a></p>
<p>Release Date: 2017-06-19</p>
<p>Fix Resolution: v4.12-rc7</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 high detected in linux stable autoclosed cve high severity vulnerability vulnerable library linux stable julia cartwright s fork of linux stable rt git library home page a href found in head commit a href found in base branch master vulnerable source files vulnerability details the linux kernel imposes a size restriction on the arguments and environmental strings passed through rlimit stack rlim infinity of the size but does not take the argument and environment pointers into account which allows attackers to bypass this limitation this affects linux kernel versions and earlier it appears that this feature was introduced in the linux kernel version publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend
| 0
|
665,816
| 22,330,885,596
|
IssuesEvent
|
2022-06-14 14:26:18
|
mozilla/addons-linter
|
https://api.github.com/repos/mozilla/addons-linter
|
closed
|
Addon validator has a 45 char limit for the add-on name while the edit details form has a different limitation
|
state: blocked priority: p3
|
STR:
1. Log in to AMO -dev
2. Create a new add-on package and make sure that the manifest `"name"` has more than 45 characters
3. Submit your add-on through the dev hub distribution page
4. Observe the validation results
Actual result:
An error is triggered for the "name" field which exceeds the 45 character limitation
Expected result:
Since the Name field in Dev Hub is more flexible now - it allows for an add-on name to have up to 68 characters - we should make sure that there are no inconsistencies between the validation page and the edit details form
Notes:
- this can be currently reproduced only when the `content-optimization` waffle is switched on
- reproduced on AMO -dev with FF63, Win10x64
[1] validation error
[2]
Dev Hub Edit information page
|
1.0
|
Addon validator has a 45 char limit for the add-on name while the edit details form has a different limitation - STR:
1. Log in to AMO -dev
2. Create a new add-on package and make sure that the manifest `"name"` has more than 45 characters
3. Submit your add-on through the dev hub distribution page
4. Observe the validation results
Actual result:
An error is triggered for the "name" field which exceeds the 45 character limitation
Expected result:
Since the Name field in Dev Hub is more flexible now - it allows for an add-on name to have up to 68 characters - we should make sure that there are no inconsistencies between the validation page and the edit details form
Notes:
- this can be currently reproduced only when the `content-optimization` waffle is switched on
- reproduced on AMO -dev with FF63, Win10x64
[1] validation error
[2]
Dev Hub Edit information page
|
non_process
|
addon validator has a char limit for the add on name while the edit details form has a different limitation str log in to amo dev create a new add on package and make sure that the manifest name has more than characters submit your add on through the dev hub distribution page observe the validation results actual result an error is triggered for the name field which exceeds the character limitation expected result since the name field in dev hub is more flexible now it allows for an add on name to have up to characters we should make sure that there are no inconsistencies between the validation page and the edit details form notes this can be currently reproduced only when the content optimization waffle is switched on reproduced on amo dev with validation error dev hub edit information page
| 0
|
271,417
| 23,603,340,136
|
IssuesEvent
|
2022-08-24 05:41:49
|
cockroachdb/cockroach
|
https://api.github.com/repos/cockroachdb/cockroach
|
opened
|
ccl/changefeedccl: TestChangefeedPrimaryKeyChangeWorksWithMultipleTables failed
|
C-test-failure O-robot branch-master
|
ccl/changefeedccl.TestChangefeedPrimaryKeyChangeWorksWithMultipleTables [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/6213858?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/6213858?buildTab=artifacts#/) on master @ [003c0360de8b64319b5f0f127b99be91dbdca8a3](https://github.com/cockroachdb/cockroach/commits/003c0360de8b64319b5f0f127b99be91dbdca8a3):
```
=== RUN TestChangefeedPrimaryKeyChangeWorksWithMultipleTables
test_log_scope.go:162: test logs captured to: /artifacts/tmp/_tmp/a77002d7c9453d7cd2d382f907780e13/logTestChangefeedPrimaryKeyChangeWorksWithMultipleTables3076719986
test_log_scope.go:80: use -show-logs to present logs inline
=== CONT TestChangefeedPrimaryKeyChangeWorksWithMultipleTables
changefeed_test.go:5421: -- test log scope end --
--- FAIL: TestChangefeedPrimaryKeyChangeWorksWithMultipleTables (5.54s)
=== RUN TestChangefeedPrimaryKeyChangeWorksWithMultipleTables/sinkless
helpers_test.go:716: making server as system tenant
helpers_test.go:803: making sinkless feed factory
changefeed_test.go:5414:
Error Trace: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/4065/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/ccl/changefeedccl/changefeedccl_test_/changefeedccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/changefeedccl/helpers_test.go:190
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/4065/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/ccl/changefeedccl/changefeedccl_test_/changefeedccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/changefeedccl/helpers_test.go:258
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/4065/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/ccl/changefeedccl/changefeedccl_test_/changefeedccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/changefeedccl/changefeed_test.go:5414
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/4065/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/ccl/changefeedccl/changefeedccl_test_/changefeedccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/changefeedccl/helpers_test.go:839
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/4065/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/ccl/changefeedccl/changefeedccl_test_/changefeedccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/changefeedccl/helpers_test.go:867
Error: Received unexpected error:
ERROR: context canceled (SQLSTATE XXUUU)
Test: TestChangefeedPrimaryKeyChangeWorksWithMultipleTables/sinkless
--- FAIL: TestChangefeedPrimaryKeyChangeWorksWithMultipleTables/sinkless (5.39s)
```
<p>Parameters: <code>TAGS=bazel,gss,deadlock</code>
</p>
<details><summary>Help</summary>
<p>
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
</p>
</details>
/cc @cockroachdb/cdc
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestChangefeedPrimaryKeyChangeWorksWithMultipleTables.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
|
1.0
|
ccl/changefeedccl: TestChangefeedPrimaryKeyChangeWorksWithMultipleTables failed - ccl/changefeedccl.TestChangefeedPrimaryKeyChangeWorksWithMultipleTables [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/6213858?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/6213858?buildTab=artifacts#/) on master @ [003c0360de8b64319b5f0f127b99be91dbdca8a3](https://github.com/cockroachdb/cockroach/commits/003c0360de8b64319b5f0f127b99be91dbdca8a3):
```
=== RUN TestChangefeedPrimaryKeyChangeWorksWithMultipleTables
test_log_scope.go:162: test logs captured to: /artifacts/tmp/_tmp/a77002d7c9453d7cd2d382f907780e13/logTestChangefeedPrimaryKeyChangeWorksWithMultipleTables3076719986
test_log_scope.go:80: use -show-logs to present logs inline
=== CONT TestChangefeedPrimaryKeyChangeWorksWithMultipleTables
changefeed_test.go:5421: -- test log scope end --
--- FAIL: TestChangefeedPrimaryKeyChangeWorksWithMultipleTables (5.54s)
=== RUN TestChangefeedPrimaryKeyChangeWorksWithMultipleTables/sinkless
helpers_test.go:716: making server as system tenant
helpers_test.go:803: making sinkless feed factory
changefeed_test.go:5414:
Error Trace: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/4065/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/ccl/changefeedccl/changefeedccl_test_/changefeedccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/changefeedccl/helpers_test.go:190
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/4065/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/ccl/changefeedccl/changefeedccl_test_/changefeedccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/changefeedccl/helpers_test.go:258
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/4065/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/ccl/changefeedccl/changefeedccl_test_/changefeedccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/changefeedccl/changefeed_test.go:5414
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/4065/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/ccl/changefeedccl/changefeedccl_test_/changefeedccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/changefeedccl/helpers_test.go:839
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/4065/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/ccl/changefeedccl/changefeedccl_test_/changefeedccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/changefeedccl/helpers_test.go:867
Error: Received unexpected error:
ERROR: context canceled (SQLSTATE XXUUU)
Test: TestChangefeedPrimaryKeyChangeWorksWithMultipleTables/sinkless
--- FAIL: TestChangefeedPrimaryKeyChangeWorksWithMultipleTables/sinkless (5.39s)
```
<p>Parameters: <code>TAGS=bazel,gss,deadlock</code>
</p>
<details><summary>Help</summary>
<p>
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
</p>
</details>
/cc @cockroachdb/cdc
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestChangefeedPrimaryKeyChangeWorksWithMultipleTables.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
|
non_process
|
ccl changefeedccl testchangefeedprimarykeychangeworkswithmultipletables failed ccl changefeedccl testchangefeedprimarykeychangeworkswithmultipletables with on master run testchangefeedprimarykeychangeworkswithmultipletables test log scope go test logs captured to artifacts tmp tmp test log scope go use show logs to present logs inline cont testchangefeedprimarykeychangeworkswithmultipletables changefeed test go test log scope end fail testchangefeedprimarykeychangeworkswithmultipletables run testchangefeedprimarykeychangeworkswithmultipletables sinkless helpers test go making server as system tenant helpers test go making sinkless feed factory changefeed test go error trace home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg ccl changefeedccl changefeedccl test changefeedccl test runfiles com github cockroachdb cockroach pkg ccl changefeedccl helpers test go home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg ccl changefeedccl changefeedccl test changefeedccl test runfiles com github cockroachdb cockroach pkg ccl changefeedccl helpers test go home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg ccl changefeedccl changefeedccl test changefeedccl test runfiles com github cockroachdb cockroach pkg ccl changefeedccl changefeed test go home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg ccl changefeedccl changefeedccl test changefeedccl test runfiles com github cockroachdb cockroach pkg ccl changefeedccl helpers test go home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg ccl changefeedccl changefeedccl test changefeedccl test runfiles com github cockroachdb cockroach pkg ccl changefeedccl helpers test go error received unexpected error error context canceled sqlstate xxuuu test testchangefeedprimarykeychangeworkswithmultipletables sinkless fail testchangefeedprimarykeychangeworkswithmultipletables sinkless parameters tags bazel gss deadlock help see also cc cockroachdb cdc
| 0
|
21,808
| 7,085,766,405
|
IssuesEvent
|
2018-01-11 12:13:15
|
typelevel/cats
|
https://api.github.com/repos/typelevel/cats
|
closed
|
Preparations for sbt 1.0.0
|
build in progress
|
Over the last few days I started upgrading some sbt plugins as preparations for upgrading to sbt 1.0.0. This issue lists the plugins that need to be upgraded and tracks the progress of this effort:
- [x] partial-unification #1842
- [x] sbt-coursier #1825
- [x] sbt-doctest #1821
- [x] sbt-ghpages #1852
- [x] sbt-git #1849
- [x] sbt-jmh #1828
- [x] sbt-microsites #1918
- [x] sbt-mima-plugin #1824
- [x] sbt-pgp #1860
- [x] sbt-release #1829
- [x] sbt-scoverage #1861
- [x] sbt-sonatype #1859
- [x] sbt-unidoc #1843
- [x] scalastyle-sbt-plugin #1839
build.sbt changes:
- [x] curly braces for disabling tasks #1876
- [x] add val for "compile-time" configuration #1889
|
1.0
|
Preparations for sbt 1.0.0 - Over the last few days I started upgrading some sbt plugins as preparations for upgrading to sbt 1.0.0. This issue lists the plugins that need to be upgraded and tracks the progress of this effort:
- [x] partial-unification #1842
- [x] sbt-coursier #1825
- [x] sbt-doctest #1821
- [x] sbt-ghpages #1852
- [x] sbt-git #1849
- [x] sbt-jmh #1828
- [x] sbt-microsites #1918
- [x] sbt-mima-plugin #1824
- [x] sbt-pgp #1860
- [x] sbt-release #1829
- [x] sbt-scoverage #1861
- [x] sbt-sonatype #1859
- [x] sbt-unidoc #1843
- [x] scalastyle-sbt-plugin #1839
build.sbt changes:
- [x] curly braces for disabling tasks #1876
- [x] add val for "compile-time" configuration #1889
|
non_process
|
preparations for sbt over the last few days i started upgrading some sbt plugins as preparations for upgrading to sbt this issue lists the plugins that need to be upgraded and tracks the progress of this effort partial unification sbt coursier sbt doctest sbt ghpages sbt git sbt jmh sbt microsites sbt mima plugin sbt pgp sbt release sbt scoverage sbt sonatype sbt unidoc scalastyle sbt plugin build sbt changes curly braces for disabling tasks add val for compile time configuration
| 0
|
775,388
| 27,232,878,533
|
IssuesEvent
|
2023-02-21 14:26:40
|
AzerPUG/Multiple-Reputation-Tracker
|
https://api.github.com/repos/AzerPUG/Multiple-Reputation-Tracker
|
closed
|
Some reputations showing up incorrectly.
|
AzerBug Priority
|
Reputations that have a different then standard minimum rep-name (EG. Court of Night) show up as a lower rep level (friendly while exalted).
Reputations with different rep level names (EG. Venari) show up as a different name then they are supposed to have. (Friendly while 'appreciated').
Check if there is a rep level index and if we are using that incorrectly.
Check if there is a rep level name, and see if we can put that on instead.
|
1.0
|
Some reputations showing up incorrectly. - Reputations that have a different then standard minimum rep-name (EG. Court of Night) show up as a lower rep level (friendly while exalted).
Reputations with different rep level names (EG. Venari) show up as a different name then they are supposed to have. (Friendly while 'appreciated').
Check if there is a rep level index and if we are using that incorrectly.
Check if there is a rep level name, and see if we can put that on instead.
|
non_process
|
some reputations showing up incorrectly reputations that have a different then standard minimum rep name eg court of night show up as a lower rep level friendly while exalted reputations with different rep level names eg venari show up as a different name then they are supposed to have friendly while appreciated check if there is a rep level index and if we are using that incorrectly check if there is a rep level name and see if we can put that on instead
| 0
|
30,448
| 7,198,549,924
|
IssuesEvent
|
2018-02-05 13:15:02
|
mozilla-releng/services
|
https://api.github.com/repos/mozilla-releng/services
|
closed
|
shipit_code_coverage: Stop rewriting LCOV files
|
4.app: shipit_code_coverage
|
Once https://bugzilla.mozilla.org/show_bug.cgi?id=1431388 is fixed, the LCOV rewriting will happen on the test machines directly, so we won't need to perform the rewriting ourselves anymore.
|
1.0
|
shipit_code_coverage: Stop rewriting LCOV files - Once https://bugzilla.mozilla.org/show_bug.cgi?id=1431388 is fixed, the LCOV rewriting will happen on the test machines directly, so we won't need to perform the rewriting ourselves anymore.
|
non_process
|
shipit code coverage stop rewriting lcov files once is fixed the lcov rewriting will happen on the test machines directly so we won t need to perform the rewriting ourselves anymore
| 0
|
16,702
| 21,802,619,974
|
IssuesEvent
|
2022-05-16 07:21:44
|
nodejs/node
|
https://api.github.com/repos/nodejs/node
|
closed
|
Child-Process: file-descriptor auto-closes when it shouldn't without triggering close events.
|
child_process stdio
|
* **Version**: 6.11.0
* **Platform**: Windows 10.0.15063 (64bit)
* **Subsystem**: child_process (spawn component)
I have a master and a child process of which both repeatedly ping each other over fd: 3, and fd:4, however after 1 second the master stops receiving any messages from the child, and no close, end, finish, or error event is ever triggered.
Master:
```
var spawn = require('child_process').spawn;
var child = spawn(process.execPath, [__dirname+'/child.js'], {
stdio: ['pipe', 'inherit', 'inherit', 'pipe', 'pipe']
});
child.stdio[3].on('data', function(chunk){
console.log('Master Replayed to 3');
child.stdio[3].write('Reply 3');
});
child.stdio[4].on('data', function(chunk){
console.log('Master Replayed to 4');
child.stdio[4].write('Reply 4');
});
child.stdio[3].on('close', function(){
console.log('Master lost connection though fd3');
});
child.stdio[4].on('close', function(){
console.log('Master lost connection though fd4');
});
child.stdio[3].on('end', function(){
console.log('Master lost connection though fd3');
});
child.stdio[4].on('end', function(){
console.log('Master lost connection though fd4');
});
child.stdio[3].on('finish', function(){
console.log('Master lost connection though fd3');
});
child.stdio[4].on('finish', function(){
console.log('Master lost connection though fd4');
});
child.stdio[3].on('error', function(err){
console.log('Master lost connection though fd3', err);
});
child.stdio[4].on('error', function(err){
console.log('Master lost connection though fd4', err);
});
child.stdio[3].write('ready');
child.stdio[4].write('ready');
console.log('init child');
```
Child:
```
var net = require('net');
var pipe3 = new net.Socket({ fd: 3, writeable: true, readable: true});
var pipe4 = new net.Socket({ fd: 4, writeable: true, readable: true});
pipe3.on('data', function(){
console.log('Child received reply though fd3');
pipe3.write('auto');
});
pipe4.on('data', function(){
console.log('Child received reply though fd4');
pipe4.write('auto');
});
setInterval(function () {
console.log('Child says hi though fd3');
pipe3.write('Boo');
console.log('Child says hi though fd4');
pipe4.write('Boo');
}, 1000);
pipe3.on('close', function(){
console.log('Child lost connection to fd3');
});
pipe4.on('close', function(){
console.log('Child lost connection to fd4');
});
pipe3.on('end', function(){
console.log('Child lost connection to fd3');
});
pipe4.on('end', function(){
console.log('Child lost connection to fd4');
});
pipe3.on('finish', function(){
console.log('Child lost connection to fd3');
});
pipe4.on('finish', function(){
console.log('Child lost connection to fd4');
});
pipe3.on('error', function(err){
console.log('FD3:', err);
});
pipe4.on('error', function(err){
console.log('FD4:', err);
});
```
Partial log:
```
...[child and master pinging each other allot]
Child says hi though fd3
Child says hi though fd4
Child says hi though fd3
Child says hi though fd4
...
[forced close process]
```
|
1.0
|
Child-Process: file-descriptor auto-closes when it shouldn't without triggering close events. - * **Version**: 6.11.0
* **Platform**: Windows 10.0.15063 (64bit)
* **Subsystem**: child_process (spawn component)
I have a master and a child process of which both repeatedly ping each other over fd: 3, and fd:4, however after 1 second the master stops receiving any messages from the child, and no close, end, finish, or error event is ever triggered.
Master:
```
var spawn = require('child_process').spawn;
var child = spawn(process.execPath, [__dirname+'/child.js'], {
stdio: ['pipe', 'inherit', 'inherit', 'pipe', 'pipe']
});
child.stdio[3].on('data', function(chunk){
console.log('Master Replayed to 3');
child.stdio[3].write('Reply 3');
});
child.stdio[4].on('data', function(chunk){
console.log('Master Replayed to 4');
child.stdio[4].write('Reply 4');
});
child.stdio[3].on('close', function(){
console.log('Master lost connection though fd3');
});
child.stdio[4].on('close', function(){
console.log('Master lost connection though fd4');
});
child.stdio[3].on('end', function(){
console.log('Master lost connection though fd3');
});
child.stdio[4].on('end', function(){
console.log('Master lost connection though fd4');
});
child.stdio[3].on('finish', function(){
console.log('Master lost connection though fd3');
});
child.stdio[4].on('finish', function(){
console.log('Master lost connection though fd4');
});
child.stdio[3].on('error', function(err){
console.log('Master lost connection though fd3', err);
});
child.stdio[4].on('error', function(err){
console.log('Master lost connection though fd4', err);
});
child.stdio[3].write('ready');
child.stdio[4].write('ready');
console.log('init child');
```
Child:
```
var net = require('net');
var pipe3 = new net.Socket({ fd: 3, writeable: true, readable: true});
var pipe4 = new net.Socket({ fd: 4, writeable: true, readable: true});
pipe3.on('data', function(){
console.log('Child received reply though fd3');
pipe3.write('auto');
});
pipe4.on('data', function(){
console.log('Child received reply though fd4');
pipe4.write('auto');
});
setInterval(function () {
console.log('Child says hi though fd3');
pipe3.write('Boo');
console.log('Child says hi though fd4');
pipe4.write('Boo');
}, 1000);
pipe3.on('close', function(){
console.log('Child lost connection to fd3');
});
pipe4.on('close', function(){
console.log('Child lost connection to fd4');
});
pipe3.on('end', function(){
console.log('Child lost connection to fd3');
});
pipe4.on('end', function(){
console.log('Child lost connection to fd4');
});
pipe3.on('finish', function(){
console.log('Child lost connection to fd3');
});
pipe4.on('finish', function(){
console.log('Child lost connection to fd4');
});
pipe3.on('error', function(err){
console.log('FD3:', err);
});
pipe4.on('error', function(err){
console.log('FD4:', err);
});
```
Partial log:
```
...[child and master pinging each other allot]
Child says hi though fd3
Child says hi though fd4
Child says hi though fd3
Child says hi though fd4
...
[forced close process]
```
|
process
|
child process file descriptor auto closes when it shouldn t without triggering close events version platform windows subsystem child process spawn component i have a master and a child process of which both repeatedly ping each other over fd and fd however after second the master stops receiving any messages from the child and no close end finish or error event is ever triggered master var spawn require child process spawn var child spawn process execpath stdio child stdio on data function chunk console log master replayed to child stdio write reply child stdio on data function chunk console log master replayed to child stdio write reply child stdio on close function console log master lost connection though child stdio on close function console log master lost connection though child stdio on end function console log master lost connection though child stdio on end function console log master lost connection though child stdio on finish function console log master lost connection though child stdio on finish function console log master lost connection though child stdio on error function err console log master lost connection though err child stdio on error function err console log master lost connection though err child stdio write ready child stdio write ready console log init child child var net require net var new net socket fd writeable true readable true var new net socket fd writeable true readable true on data function console log child received reply though write auto on data function console log child received reply though write auto setinterval function console log child says hi though write boo console log child says hi though write boo on close function console log child lost connection to on close function console log child lost connection to on end function console log child lost connection to on end function console log child lost connection to on finish function console log child lost connection to on finish function console log child lost connection to on error function err console log err on error function err console log err partial log child says hi though child says hi though child says hi though child says hi though
| 1
|
296,468
| 9,116,260,289
|
IssuesEvent
|
2019-02-22 08:29:08
|
yavl/teeworlds-infclassR
|
https://api.github.com/repos/yavl/teeworlds-infclassR
|
opened
|
Translate /help and commands for major languages
|
low priority
|
Original InfClass was already [localized](https://github.com/yavl/teeworlds-infclassR/tree/d93a52b70588a3d13bf4af0b0b9e9924cafefa4f/data/languages) in many languages, few strings were added for /help pages and commands like /witch since then and are not going to change.
Many players from Latin America, Russian-speaking countries, some young players from France don't understand English well, so they usually don't take part in "Player is calling for Witch!" challenge, nor they form taxi or revive infected. Therefore those newly added strings should be translated to Spanish, Russian, French and some other languages.
|
1.0
|
Translate /help and commands for major languages - Original InfClass was already [localized](https://github.com/yavl/teeworlds-infclassR/tree/d93a52b70588a3d13bf4af0b0b9e9924cafefa4f/data/languages) in many languages, few strings were added for /help pages and commands like /witch since then and are not going to change.
Many players from Latin America, Russian-speaking countries, some young players from France don't understand English well, so they usually don't take part in "Player is calling for Witch!" challenge, nor they form taxi or revive infected. Therefore those newly added strings should be translated to Spanish, Russian, French and some other languages.
|
non_process
|
translate help and commands for major languages original infclass was already in many languages few strings were added for help pages and commands like witch since then and are not going to change many players from latin america russian speaking countries some young players from france don t understand english well so they usually don t take part in player is calling for witch challenge nor they form taxi or revive infected therefore those newly added strings should be translated to spanish russian french and some other languages
| 0
|
19,209
| 25,343,349,885
|
IssuesEvent
|
2022-11-19 00:54:52
|
ncbo/bioportal-project
|
https://api.github.com/repos/ncbo/bioportal-project
|
closed
|
404 error on classes page for DFO, VFB_DRIVERS ontologies
|
ontology processing problem KB Aim1 Maintenance KB1 Parsing/Ops
|
BioPortal displays a 404 error for the [classes page](https://bioportal.bioontology.org/ontologies/DFO?p=classes) for the [DFO ontology](https://bioportal.bioontology.org/ontologies/DFO). No errors in the production parsing log.
The underlying reason for the 404 is that the REST API is returning an empty set for the /roots endpoint and the UI can't construct a class tree without roots.
The [/classes endpoint](https://data.bioontology.org/ontologies/DFO/classes?display_context=false&display_links=false&include=prefLabel) returns data appropriately, i.e.:
The [/roots](https://data.bioontology.org/ontologies/DFO/classes/roots) endpoint returns an empty set:
Opening the ontology in Protege shows two root classes:
Both of the root classes are declared using an obo prefix (DFO is an OWL, not an OBO ontology):
```
<Declaration>
<Class abbreviatedIRI="obo:NCIT_C61393"/>
</Declaration>
<Declaration>
<Class abbreviatedIRI="obo:NCIT_C79273"/>
</Declaration>
```
... though it's not clear if this is preventing the REST API from locating the root classes
|
1.0
|
404 error on classes page for DFO, VFB_DRIVERS ontologies - BioPortal displays a 404 error for the [classes page](https://bioportal.bioontology.org/ontologies/DFO?p=classes) for the [DFO ontology](https://bioportal.bioontology.org/ontologies/DFO). No errors in the production parsing log.
The underlying reason for the 404 is that the REST API is returning an empty set for the /roots endpoint and the UI can't construct a class tree without roots.
The [/classes endpoint](https://data.bioontology.org/ontologies/DFO/classes?display_context=false&display_links=false&include=prefLabel) returns data appropriately, i.e.:
The [/roots](https://data.bioontology.org/ontologies/DFO/classes/roots) endpoint returns an empty set:
Opening the ontology in Protege shows two root classes:
Both of the root classes are declared using an obo prefix (DFO is an OWL, not an OBO ontology):
```
<Declaration>
<Class abbreviatedIRI="obo:NCIT_C61393"/>
</Declaration>
<Declaration>
<Class abbreviatedIRI="obo:NCIT_C79273"/>
</Declaration>
```
... though it's not clear if this is preventing the REST API from locating the root classes
|
process
|
error on classes page for dfo vfb drivers ontologies bioportal displays a error for the for the no errors in the production parsing log the underlying reason for the is that the rest api is returning an empty set for the roots endpoint and the ui can t construct a class tree without roots the returns data appropriately i e the endpoint returns an empty set opening the ontology in protege shows two root classes both of the root classes are declared using an obo prefix dfo is an owl not an obo ontology though it s not clear if this is preventing the rest api from locating the root classes
| 1
|
4,462
| 7,330,244,446
|
IssuesEvent
|
2018-03-05 09:16:28
|
UKHomeOffice/dq-aws-transition
|
https://api.github.com/repos/UKHomeOffice/dq-aws-transition
|
closed
|
Create Crontabs under SSM group on Prod Ingest Linux Server
|
DQ Data Ingest DQ Tranche 1 Production SSM processing
|
Create Crontabs under SSM group on Prod Ingest Linux Server
*/2 * * * * /ADT/scripts/sftp_oag_client_maytech.py
- [x] Crontab Created
|
1.0
|
Create Crontabs under SSM group on Prod Ingest Linux Server - Create Crontabs under SSM group on Prod Ingest Linux Server
*/2 * * * * /ADT/scripts/sftp_oag_client_maytech.py
- [x] Crontab Created
|
process
|
create crontabs under ssm group on prod ingest linux server create crontabs under ssm group on prod ingest linux server adt scripts sftp oag client maytech py crontab created
| 1
|
37,420
| 5,116,573,573
|
IssuesEvent
|
2017-01-07 05:19:59
|
extnet/Ext.NET
|
https://api.github.com/repos/extnet/Ext.NET
|
closed
|
ComboBox's list or DropDownField's component doesn't collapse on scroll in Firefox
|
3.x 4.x fixed-in-latest-extjs sencha
|
http://forums.ext.net/showthread.php?53671
**UPDATE**: still reproducible with ExtJS 5.1.1.
**Update:** Sencha issue identified and still open after 6.0.1 release.
Sencha issue: [Combobox boundlist does not collapse when in scrolling container - Firefox Only](https://www.sencha.com/forum/showthread.php?300678)
**Update:** Sencha pointed to a new issue, which has been fixed since 6.0.0: [5.1.1 Nightly: Mouse scroller on Firefox just move some millimeters the grid](https://www.sencha.com/forum/showthread.php?296278)
|
1.0
|
ComboBox's list or DropDownField's component doesn't collapse on scroll in Firefox - http://forums.ext.net/showthread.php?53671
**UPDATE**: still reproducible with ExtJS 5.1.1.
**Update:** Sencha issue identified and still open after 6.0.1 release.
Sencha issue: [Combobox boundlist does not collapse when in scrolling container - Firefox Only](https://www.sencha.com/forum/showthread.php?300678)
**Update:** Sencha pointed to a new issue, which has been fixed since 6.0.0: [5.1.1 Nightly: Mouse scroller on Firefox just move some millimeters the grid](https://www.sencha.com/forum/showthread.php?296278)
|
non_process
|
combobox s list or dropdownfield s component doesn t collapse on scroll in firefox update still reproducible with extjs update sencha issue identified and still open after release sencha issue update sencha pointed to a new issue which has been fixed since
| 0
|
10,466
| 13,244,051,960
|
IssuesEvent
|
2020-08-19 12:28:37
|
aiidateam/aiida-core
|
https://api.github.com/repos/aiidateam/aiida-core
|
reopened
|
AiiDA loses control over a process (Process is unreachable).
|
topic/processes topic/rabbitmq type/bug
|
### Describe the bug
After restarting AiiDA lab container that runs out of memory AiiDA loses connection to the running processes. Any attempt to kill them results in the error message `The process is unreachable`
### Steps to reproduce
This is the report from @cpignedoli. It involves many steps, maybe some of them are redundant:
1. Nanoribbon work chain was running.
1. For an unrelated reason, the AiiDA lab machine ran out of memory.
1. The docker container was killed “manually”, via `docker stop`.
1. Because of a bug in AiiDA lab, we manually (in config.json) switched to the default profile.
1. We started the container.
1. We switched back to the profile where the simulation was running.
1. AiiDA lost access to the calculations.
I believe the steps 4 and 6 are redundant, but I report them for the completeness of the story
### Expected behavior
AiiDA should restore access to the running processes.
### Your environment
- Operating system: Ubuntu 18.04.1
- Python version: 3.7.4
- aiida-core version: 1.2.1
- PostgreSQL: 10.12
- RabbitMQ: 3.6.10-1
|
1.0
|
AiiDA loses control over a process (Process is unreachable). - ### Describe the bug
After restarting AiiDA lab container that runs out of memory AiiDA loses connection to the running processes. Any attempt to kill them results in the error message `The process is unreachable`
### Steps to reproduce
This is the report from @cpignedoli. It involves many steps, maybe some of them are redundant:
1. Nanoribbon work chain was running.
1. For an unrelated reason, the AiiDA lab machine ran out of memory.
1. The docker container was killed “manually”, via `docker stop`.
1. Because of a bug in AiiDA lab, we manually (in config.json) switched to the default profile.
1. We started the container.
1. We switched back to the profile where the simulation was running.
1. AiiDA lost access to the calculations.
I believe the steps 4 and 6 are redundant, but I report them for the completeness of the story
### Expected behavior
AiiDA should restore access to the running processes.
### Your environment
- Operating system: Ubuntu 18.04.1
- Python version: 3.7.4
- aiida-core version: 1.2.1
- PostgreSQL: 10.12
- RabbitMQ: 3.6.10-1
|
process
|
aiida loses control over a process process is unreachable describe the bug after restarting aiida lab container that runs out of memory aiida loses connection to the running processes any attempt to kill them results in the error message the process is unreachable steps to reproduce this is the report from cpignedoli it involves many steps maybe some of them are redundant nanoribbon work chain was running for an unrelated reason the aiida lab machine ran out of memory the docker container was killed “manually” via docker stop because of a bug in aiida lab we manually in config json switched to the default profile we started the container we switched back to the profile where the simulation was running aiida lost access to the calculations i believe the steps and are redundant but i report them for the completeness of the story expected behavior aiida should restore access to the running processes your environment operating system ubuntu python version aiida core version postgresql rabbitmq
| 1
|
3,165
| 6,223,309,030
|
IssuesEvent
|
2017-07-10 11:33:00
|
zero-os/0-stor
|
https://api.github.com/repos/zero-os/0-stor
|
closed
|
0-stor: check list of consumers is properly populated
|
process_duplicate type_bug
|
- spec was not ok, it was mentioned reference counter, needs to be full list
- the counter is required to quickly decide if the data is permanent or not and how many people have referenced this data
|
1.0
|
0-stor: check list of consumers is properly populated - - spec was not ok, it was mentioned reference counter, needs to be full list
- the counter is required to quickly decide if the data is permanent or not and how many people have referenced this data
|
process
|
stor check list of consumers is properly populated spec was not ok it was mentioned reference counter needs to be full list the counter is required to quickly decide if the data is permanent or not and how many people have referenced this data
| 1
|
20,170
| 3,306,505,159
|
IssuesEvent
|
2015-11-04 12:06:00
|
dart-lang/sdk
|
https://api.github.com/repos/dart-lang/sdk
|
closed
|
Re-add dart:profiler
|
Area-Library Library-Profiler Type-Defect
|
The removal of `dart:profiler` in 1.13 has caused a lot of pain and strife for Dart users, and 1.13 isn't even released yet. The `analyzer` package, which is transitively used by almost every Dart package at least for testing, used `dart:profiler` up until its `0.26.1+8` release in October. This means that most packages for which `pub upgrade` hasn't been run recently will crash as soon as their tests are run.
The core SDK should generally avoid making breaking changes, since without incrementing its major version there's no way for packages to be future-proof against such changes. This is a case where the change is particularly painful because of how it affects `analyzer`, one of the most widely-used packages. It's also relatively easy to just avoid the breakage by retaining `dart:profiler` as a deprecated library that exports `dart:developer`.
cc @kevmoo @sethladd
|
1.0
|
Re-add dart:profiler - The removal of `dart:profiler` in 1.13 has caused a lot of pain and strife for Dart users, and 1.13 isn't even released yet. The `analyzer` package, which is transitively used by almost every Dart package at least for testing, used `dart:profiler` up until its `0.26.1+8` release in October. This means that most packages for which `pub upgrade` hasn't been run recently will crash as soon as their tests are run.
The core SDK should generally avoid making breaking changes, since without incrementing its major version there's no way for packages to be future-proof against such changes. This is a case where the change is particularly painful because of how it affects `analyzer`, one of the most widely-used packages. It's also relatively easy to just avoid the breakage by retaining `dart:profiler` as a deprecated library that exports `dart:developer`.
cc @kevmoo @sethladd
|
non_process
|
re add dart profiler the removal of dart profiler in has caused a lot of pain and strife for dart users and isn t even released yet the analyzer package which is transitively used by almost every dart package at least for testing used dart profiler up until its release in october this means that most packages for which pub upgrade hasn t been run recently will crash as soon as their tests are run the core sdk should generally avoid making breaking changes since without incrementing its major version there s no way for packages to be future proof against such changes this is a case where the change is particularly painful because of how it affects analyzer one of the most widely used packages it s also relatively easy to just avoid the breakage by retaining dart profiler as a deprecated library that exports dart developer cc kevmoo sethladd
| 0
|
12,654
| 3,634,855,314
|
IssuesEvent
|
2016-02-11 19:33:48
|
valum-framework/valum
|
https://api.github.com/repos/valum-framework/valum
|
closed
|
Support for a more structured OO API?
|
documentation
|
Hi again, I was just checking out all the new shiny stuff that's been added since I last had a peek, and I have to say I'm actually quite excited by the progress you've made. I've not had enough time with the docs to properly grok all the bits and bobs, but from my quick peruse it looks fantastic.
That said, there's a feature I'd be quite interested in. As far as I can see, currently if one so wished they could subclass the `Router` class, add their own functions and call `this.get()` etc in the `construct` block to try and move logic out of `main()` and into it's own discreet class. If this behaviour already works, could this become an official and documented way to use the framework? Perhaps further down the line some introspection magic could be added to automatically register routes based on declared functions (if that's even possible).
I don't think this would confer any technical benefit, but I feel like officially supporting this method of usage would enable applications leveraging the framework to be more Vala-esque (or at least according to my understanding of "the Vala style"). In any case, it would be an additional style in the API consumer's toolbox from which they can choose depending on taste ;)
|
1.0
|
Support for a more structured OO API? - Hi again, I was just checking out all the new shiny stuff that's been added since I last had a peek, and I have to say I'm actually quite excited by the progress you've made. I've not had enough time with the docs to properly grok all the bits and bobs, but from my quick peruse it looks fantastic.
That said, there's a feature I'd be quite interested in. As far as I can see, currently if one so wished they could subclass the `Router` class, add their own functions and call `this.get()` etc in the `construct` block to try and move logic out of `main()` and into it's own discreet class. If this behaviour already works, could this become an official and documented way to use the framework? Perhaps further down the line some introspection magic could be added to automatically register routes based on declared functions (if that's even possible).
I don't think this would confer any technical benefit, but I feel like officially supporting this method of usage would enable applications leveraging the framework to be more Vala-esque (or at least according to my understanding of "the Vala style"). In any case, it would be an additional style in the API consumer's toolbox from which they can choose depending on taste ;)
|
non_process
|
support for a more structured oo api hi again i was just checking out all the new shiny stuff that s been added since i last had a peek and i have to say i m actually quite excited by the progress you ve made i ve not had enough time with the docs to properly grok all the bits and bobs but from my quick peruse it looks fantastic that said there s a feature i d be quite interested in as far as i can see currently if one so wished they could subclass the router class add their own functions and call this get etc in the construct block to try and move logic out of main and into it s own discreet class if this behaviour already works could this become an official and documented way to use the framework perhaps further down the line some introspection magic could be added to automatically register routes based on declared functions if that s even possible i don t think this would confer any technical benefit but i feel like officially supporting this method of usage would enable applications leveraging the framework to be more vala esque or at least according to my understanding of the vala style in any case it would be an additional style in the api consumer s toolbox from which they can choose depending on taste
| 0
|
10,716
| 13,509,830,559
|
IssuesEvent
|
2020-09-14 09:47:14
|
dotnet/runtime
|
https://api.github.com/repos/dotnet/runtime
|
closed
|
System.Diagnostics.Tests.ProcessStandardConsoleTests.TestChangesInConsoleEncoding test fails on server core
|
area-System.Diagnostics.Process os-windows-server
|
I'm enabling Server Core 20H1 libraries test runs and this test failed with:
```
Assert.Equal() Failure
Expected: 65001
Actual: 437
at System.Diagnostics.Tests.ProcessStandardConsoleTests.<TestChangesInConsoleEncoding>b__1_0(Int32 expectedCodePage) in /_/src/libraries/System.Diagnostics.Process/tests/ProcessStandardConsoleTests.cs:line 26
at System.Diagnostics.Tests.ProcessStandardConsoleTests.TestChangesInConsoleEncoding() in /_/src/libraries/System.Diagnostics.Process/tests/ProcessStandardConsoleTests.cs:line 51
```
I noted that we have the following comment that for Nano we only support UTF-8 which is `65001` code page: https://github.com/dotnet/runtime/blob/efafca9bd8ba5a746634820596f8144d0d98fde1/src/libraries/System.Diagnostics.Process/tests/ProcessStandardConsoleTests.cs#L45
I went ahead and created a console app:
```cs
class Program
{
static void Main(string[] args)
{
Console.WriteLine($"CP: {GetConsoleCP()}");
Console.WriteLine($"Setting CP 437: {SetConsoleCP(437)}");
Console.WriteLine($"CP: {GetConsoleCP()}");
Console.WriteLine($"Setting CP to 65001: {SetConsoleCP(65001)}");
Console.WriteLine($"CP: {GetConsoleCP()}");
}
[DllImport("kernel32.dll")]
internal static extern int SetConsoleCP(int codePage);
[DllImport("kernel32.dll")]
internal static extern int GetConsoleCP();
}
```
Output was:
```
C:\Work\test>tmpTestCodePageServer.exe
CP: 65001
Setting CP 437: 1
CP: 437
Setting CP to 65001: 1
CP: 65001
```
I ran this on both a Nano and a Server container and got the same results:
`mcr.microsoft.com/dotnet-buildtools/prereqs:windowsservercore-2004-helix-amd64-20200904200251-272704c`
`mcr.microsoft.com/dotnet-buildtools/prereqs:nanoserver-1809-helix-amd64-08e8e40-20200107182504`
cc: @ericstj @danmosemsft @jkotas @adamsitnik @eiriktsarpalis
|
1.0
|
System.Diagnostics.Tests.ProcessStandardConsoleTests.TestChangesInConsoleEncoding test fails on server core - I'm enabling Server Core 20H1 libraries test runs and this test failed with:
```
Assert.Equal() Failure
Expected: 65001
Actual: 437
at System.Diagnostics.Tests.ProcessStandardConsoleTests.<TestChangesInConsoleEncoding>b__1_0(Int32 expectedCodePage) in /_/src/libraries/System.Diagnostics.Process/tests/ProcessStandardConsoleTests.cs:line 26
at System.Diagnostics.Tests.ProcessStandardConsoleTests.TestChangesInConsoleEncoding() in /_/src/libraries/System.Diagnostics.Process/tests/ProcessStandardConsoleTests.cs:line 51
```
I noted that we have the following comment that for Nano we only support UTF-8 which is `65001` code page: https://github.com/dotnet/runtime/blob/efafca9bd8ba5a746634820596f8144d0d98fde1/src/libraries/System.Diagnostics.Process/tests/ProcessStandardConsoleTests.cs#L45
I went ahead and created a console app:
```cs
class Program
{
static void Main(string[] args)
{
Console.WriteLine($"CP: {GetConsoleCP()}");
Console.WriteLine($"Setting CP 437: {SetConsoleCP(437)}");
Console.WriteLine($"CP: {GetConsoleCP()}");
Console.WriteLine($"Setting CP to 65001: {SetConsoleCP(65001)}");
Console.WriteLine($"CP: {GetConsoleCP()}");
}
[DllImport("kernel32.dll")]
internal static extern int SetConsoleCP(int codePage);
[DllImport("kernel32.dll")]
internal static extern int GetConsoleCP();
}
```
Output was:
```
C:\Work\test>tmpTestCodePageServer.exe
CP: 65001
Setting CP 437: 1
CP: 437
Setting CP to 65001: 1
CP: 65001
```
I ran this on both a Nano and a Server container and got the same results:
`mcr.microsoft.com/dotnet-buildtools/prereqs:windowsservercore-2004-helix-amd64-20200904200251-272704c`
`mcr.microsoft.com/dotnet-buildtools/prereqs:nanoserver-1809-helix-amd64-08e8e40-20200107182504`
cc: @ericstj @danmosemsft @jkotas @adamsitnik @eiriktsarpalis
|
process
|
system diagnostics tests processstandardconsoletests testchangesinconsoleencoding test fails on server core i m enabling server core libraries test runs and this test failed with assert equal failure expected actual at system diagnostics tests processstandardconsoletests b expectedcodepage in src libraries system diagnostics process tests processstandardconsoletests cs line at system diagnostics tests processstandardconsoletests testchangesinconsoleencoding in src libraries system diagnostics process tests processstandardconsoletests cs line i noted that we have the following comment that for nano we only support utf which is code page i went ahead and created a console app cs class program static void main string args console writeline cp getconsolecp console writeline setting cp setconsolecp console writeline cp getconsolecp console writeline setting cp to setconsolecp console writeline cp getconsolecp internal static extern int setconsolecp int codepage internal static extern int getconsolecp output was c work test tmptestcodepageserver exe cp setting cp cp setting cp to cp i ran this on both a nano and a server container and got the same results mcr microsoft com dotnet buildtools prereqs windowsservercore helix mcr microsoft com dotnet buildtools prereqs nanoserver helix cc ericstj danmosemsft jkotas adamsitnik eiriktsarpalis
| 1
|
19,954
| 26,431,905,633
|
IssuesEvent
|
2023-01-14 22:55:10
|
processing/processing4
|
https://api.github.com/repos/processing/processing4
|
closed
|
`color` in imports shows up as an error in the editor in 4.0 beta 9
|
help wanted preprocessor
|
Code still compiles and runs, but is tagged as an error while editing.
To reproduce, see what happens when importing the toxiclibs library.
Possibly related: https://github.com/processing/processing4/issues/519
|
1.0
|
`color` in imports shows up as an error in the editor in 4.0 beta 9 - Code still compiles and runs, but is tagged as an error while editing.
To reproduce, see what happens when importing the toxiclibs library.
Possibly related: https://github.com/processing/processing4/issues/519
|
process
|
color in imports shows up as an error in the editor in beta code still compiles and runs but is tagged as an error while editing to reproduce see what happens when importing the toxiclibs library possibly related
| 1
|
429,991
| 12,439,436,767
|
IssuesEvent
|
2020-05-26 10:06:07
|
frontity/frontity
|
https://api.github.com/repos/frontity/frontity
|
closed
|
publicPath option not working with absolute urls
|
bug priority: critical
|
<!-- Not following the template might result in your issue being closed -->
**_Bug report_**
- I've updated both my project and my packages to the latest Frontity versions: https://docs.frontity.org/guides/keep-frontity-updated
- I've searched for existing issues.
- I've checked the documentation: https://docs.frontity.org
- I've checked the community forum: https://community.frontity.org
**Expected behavior**
Users should be able to use absolute urls for WebPack publicPath.
**Observed behavior**
It returns and Internal Server Error.
After running `npx frontity dev --publicPath="https://externaldomain.com/static" I get the following message:
```
AssertionError [ERR_ASSERTION]: mount path must begin with "/"
at mount (webpack-internal:///./node_modules/koa-mount/index.js:14:90)
at app.use (webpack-internal:///./node_modules/@frontity/core/src/server/index.tsx:28:372)
at process._tickCallback (internal/process/next_tick.js:68:7)
```
After running the same in `build` I get this one:
```
AssertionError [ERR_ASSERTION]: mount path must begin with "/"
at e.exports (/home/mario/Desktop/Code/Frontity/frontity.org/build/server.js:47:21764)
at t.default.t.use (/home/mario/Desktop/Code/Frontity/frontity.org/build/server.js:230:15093)
at process._tickCallback (internal/process/next_tick.js:68:7)
```
**Steps involved to reproduce the problem**
* Create a new Frontity project
* Run the command ``npx frontity dev --publicPath="https://externaldomain.com/static"`
|
1.0
|
publicPath option not working with absolute urls - <!-- Not following the template might result in your issue being closed -->
**_Bug report_**
- I've updated both my project and my packages to the latest Frontity versions: https://docs.frontity.org/guides/keep-frontity-updated
- I've searched for existing issues.
- I've checked the documentation: https://docs.frontity.org
- I've checked the community forum: https://community.frontity.org
**Expected behavior**
Users should be able to use absolute urls for WebPack publicPath.
**Observed behavior**
It returns and Internal Server Error.
After running `npx frontity dev --publicPath="https://externaldomain.com/static" I get the following message:
```
AssertionError [ERR_ASSERTION]: mount path must begin with "/"
at mount (webpack-internal:///./node_modules/koa-mount/index.js:14:90)
at app.use (webpack-internal:///./node_modules/@frontity/core/src/server/index.tsx:28:372)
at process._tickCallback (internal/process/next_tick.js:68:7)
```
After running the same in `build` I get this one:
```
AssertionError [ERR_ASSERTION]: mount path must begin with "/"
at e.exports (/home/mario/Desktop/Code/Frontity/frontity.org/build/server.js:47:21764)
at t.default.t.use (/home/mario/Desktop/Code/Frontity/frontity.org/build/server.js:230:15093)
at process._tickCallback (internal/process/next_tick.js:68:7)
```
**Steps involved to reproduce the problem**
* Create a new Frontity project
* Run the command ``npx frontity dev --publicPath="https://externaldomain.com/static"`
|
non_process
|
publicpath option not working with absolute urls bug report i ve updated both my project and my packages to the latest frontity versions i ve searched for existing issues i ve checked the documentation i ve checked the community forum expected behavior users should be able to use absolute urls for webpack publicpath observed behavior it returns and internal server error after running npx frontity dev publicpath i get the following message assertionerror mount path must begin with at mount webpack internal node modules koa mount index js at app use webpack internal node modules frontity core src server index tsx at process tickcallback internal process next tick js after running the same in build i get this one assertionerror mount path must begin with at e exports home mario desktop code frontity frontity org build server js at t default t use home mario desktop code frontity frontity org build server js at process tickcallback internal process next tick js steps involved to reproduce the problem create a new frontity project run the command npx frontity dev publicpath
| 0
|
315,913
| 27,116,611,920
|
IssuesEvent
|
2023-02-15 19:06:05
|
airbytehq/airbyte
|
https://api.github.com/repos/airbytehq/airbyte
|
closed
|
Source Iterable: enable `high` test strictness level in SAT
|
type/enhancement area/connectors team/connectors-python test-strictness-level
|
## What
A `test_strictness_level` field was introduced to Source Acceptance Tests (SAT).
Iterable is a generally_available connector, we want it to have a `high` test strictness level.
**This will help**:
- maximize the SAT coverage on this connector.
- document its potential weaknesses in term of test coverage.
## How
1. Migrate the existing `acceptance-test-config.yml` file to the latest configuration format. (See instructions [here](https://github.com/airbytehq/airbyte/blob/master/airbyte-integrations/bases/source-acceptance-test/README.md#L61))
2. Enable `high` test strictness level in `acceptance-test-config.yml`. (See instructions [here](https://github.com/airbytehq/airbyte/blob/master/docs/connector-development/testing-connectors/source-acceptance-tests-reference.md#L240))
3. Commit changes on `acceptance-test-config.yml` and open a PR.
4. Run SAT with the `/test` command on the branch.
5. If tests are failing please fix the failing test or use `bypass_reason` fields to explain why a specific test can't be run.
|
1.0
|
Source Iterable: enable `high` test strictness level in SAT - ## What
A `test_strictness_level` field was introduced to Source Acceptance Tests (SAT).
Iterable is a generally_available connector, we want it to have a `high` test strictness level.
**This will help**:
- maximize the SAT coverage on this connector.
- document its potential weaknesses in term of test coverage.
## How
1. Migrate the existing `acceptance-test-config.yml` file to the latest configuration format. (See instructions [here](https://github.com/airbytehq/airbyte/blob/master/airbyte-integrations/bases/source-acceptance-test/README.md#L61))
2. Enable `high` test strictness level in `acceptance-test-config.yml`. (See instructions [here](https://github.com/airbytehq/airbyte/blob/master/docs/connector-development/testing-connectors/source-acceptance-tests-reference.md#L240))
3. Commit changes on `acceptance-test-config.yml` and open a PR.
4. Run SAT with the `/test` command on the branch.
5. If tests are failing please fix the failing test or use `bypass_reason` fields to explain why a specific test can't be run.
|
non_process
|
source iterable enable high test strictness level in sat what a test strictness level field was introduced to source acceptance tests sat iterable is a generally available connector we want it to have a high test strictness level this will help maximize the sat coverage on this connector document its potential weaknesses in term of test coverage how migrate the existing acceptance test config yml file to the latest configuration format see instructions enable high test strictness level in acceptance test config yml see instructions commit changes on acceptance test config yml and open a pr run sat with the test command on the branch if tests are failing please fix the failing test or use bypass reason fields to explain why a specific test can t be run
| 0
|
64,663
| 14,674,398,865
|
IssuesEvent
|
2020-12-30 15:14:51
|
tlubitz/pb
|
https://api.github.com/repos/tlubitz/pb
|
opened
|
CVE-2020-11023 (Medium) detected in jquery-3.4.0.min.js, jquery-1.11.3.min.js
|
security vulnerability
|
## CVE-2020-11023 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>jquery-3.4.0.min.js</b>, <b>jquery-1.11.3.min.js</b></p></summary>
<p>
<details><summary><b>jquery-3.4.0.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.4.0/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/3.4.0/jquery.min.js</a></p>
<p>Path to dependency file: pb/static/css/css_template/gettingstarted.html</p>
<p>Path to vulnerable library: pb/static/css/css_template/gettingstarted.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-3.4.0.min.js** (Vulnerable Library)
</details>
<details><summary><b>jquery-1.11.3.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.11.3/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.11.3/jquery.min.js</a></p>
<p>Path to dependency file: pb/views/layout.html</p>
<p>Path to vulnerable library: pb/views/layout.html,pb/static/css/css_template/main.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.11.3.min.js** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/tlubitz/pb/commit/927a883367986d762b2e21b97b2c4e4b54ab619c">927a883367986d762b2e21b97b2c4e4b54ab619c</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>
In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
<p>Publish Date: 2020-04-29
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-11023>CVE-2020-11023</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11023">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11023</a></p>
<p>Release Date: 2020-04-29</p>
<p>Fix Resolution: jquery - 3.5.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2020-11023 (Medium) detected in jquery-3.4.0.min.js, jquery-1.11.3.min.js - ## CVE-2020-11023 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>jquery-3.4.0.min.js</b>, <b>jquery-1.11.3.min.js</b></p></summary>
<p>
<details><summary><b>jquery-3.4.0.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.4.0/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/3.4.0/jquery.min.js</a></p>
<p>Path to dependency file: pb/static/css/css_template/gettingstarted.html</p>
<p>Path to vulnerable library: pb/static/css/css_template/gettingstarted.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-3.4.0.min.js** (Vulnerable Library)
</details>
<details><summary><b>jquery-1.11.3.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.11.3/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.11.3/jquery.min.js</a></p>
<p>Path to dependency file: pb/views/layout.html</p>
<p>Path to vulnerable library: pb/views/layout.html,pb/static/css/css_template/main.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.11.3.min.js** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/tlubitz/pb/commit/927a883367986d762b2e21b97b2c4e4b54ab619c">927a883367986d762b2e21b97b2c4e4b54ab619c</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>
In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
<p>Publish Date: 2020-04-29
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-11023>CVE-2020-11023</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11023">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11023</a></p>
<p>Release Date: 2020-04-29</p>
<p>Fix Resolution: jquery - 3.5.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 medium detected in jquery min js jquery min js cve medium severity vulnerability vulnerable libraries jquery min js jquery min js jquery min js javascript library for dom operations library home page a href path to dependency file pb static css css template gettingstarted html path to vulnerable library pb static css css template gettingstarted html dependency hierarchy x jquery min js vulnerable library jquery min js javascript library for dom operations library home page a href path to dependency file pb views layout html path to vulnerable library pb views layout html pb static css css template main html dependency hierarchy x jquery min js vulnerable library found in head commit a href found in base branch master vulnerability details in jquery versions greater than or equal to and before passing html containing elements from untrusted sources even after sanitizing it to one of jquery s dom manipulation methods i e html append and others may execute untrusted code this problem is patched in jquery 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 jquery step up your open source security game with whitesource
| 0
|
896
| 3,357,389,489
|
IssuesEvent
|
2015-11-19 01:10:32
|
beesmart-it/trend-hrm
|
https://api.github.com/repos/beesmart-it/trend-hrm
|
opened
|
Update processes list when new process is created
|
bug requirement selection process
|
Update processes list when new process is created
|
1.0
|
Update processes list when new process is created - Update processes list when new process is created
|
process
|
update processes list when new process is created update processes list when new process is created
| 1
|
240,229
| 18,296,047,414
|
IssuesEvent
|
2021-10-05 20:34:33
|
microsoft/electionguard
|
https://api.github.com/repos/microsoft/electionguard
|
opened
|
📝. Document Applications Section of 0.95.0 Specification in Markdown
|
help wanted good first issue documentation hacktoberfest
|
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Suggestion
Document **Applications** Section of 0.95.0 Specification in Markdown for easy consumption on the web. This should be as close as possible to a 1 to 1 translation.
This section is actually called Applications to end-to-end verifiability and risk limiting audits
### Possible Implementation
Using the 0.95.0 Specification (https://github.com/microsoft/electionguard/releases/download/v0.95.0/ElectionGuard_Specification_v0_95_0.pdf) provided, create a markdown documentation page for the specific section mentioned. The page should be created within the `spec/0.95.0 folder`
#### Headings
There should be only one H1 heading which will presented as the title of the page.
Any other headings should be H2 or smaller according to their section.
#### Equations
Equations should use the built-in feature.
https://squidfunk.github.io/mkdocs-material/reference/mathjax/
#### Tables
Tables should use the built-in feature.
https://squidfunk.github.io/mkdocs-material/reference/data-tables/
#### Images
We want to keep the images matching the existing style of the site. These should not be copy and pasted from the document, but created preferably. If there is no other option, screenshots from the document will be accepted.
The images may be created as svg's using https://themeisle.com/illustrations/ and/or https://undraw.co/ with the color (#80CBC4) (Preferred)
OR
By using mermaid documentation:
https://mermaid-js.github.io/mermaid/#/
https://squidfunk.github.io/mkdocs-material/reference/diagrams/
#### Green and Blue Boxes
All blue boxes should be Note admonitions.
All green boxes should be Important admonitions
https://squidfunk.github.io/mkdocs-material/reference/admonitions
#### Navigation
This is the overall navigation
```
Current or 0.95.0 <-- Overview
--- Structure <-- ElectionGuard Structure
--- Components <-- ElectionGuard Components (2nd ElectionGuard Components)
--- Baseline Parameters
--- Key Generation
--- Ballot Encryption
--- Ballot Aggregation
--- Verifiable Decryption
--- Election Record <-- The Election Record
--- Verifier Construction
------ Parameter Validation
------ Guardian Public-Key Validation
------ ...
--- Applications <-- Applications to end-end verifiability and risk limited audits
--- Acknowledgements
```
This specific page should be linked under both 0.95.0 and Current in the `mkdocs.yml`.
An example is https://www.electionguard.vote/spec/0.95.0/1_Overview/
#### Pull Request Requests
Any pull request should specifically tag @benaloh and @keithrfung as reviewers. The pull request MUST include copious screenshots.
### Anything else?
_No response_
|
1.0
|
📝. Document Applications Section of 0.95.0 Specification in Markdown - ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Suggestion
Document **Applications** Section of 0.95.0 Specification in Markdown for easy consumption on the web. This should be as close as possible to a 1 to 1 translation.
This section is actually called Applications to end-to-end verifiability and risk limiting audits
### Possible Implementation
Using the 0.95.0 Specification (https://github.com/microsoft/electionguard/releases/download/v0.95.0/ElectionGuard_Specification_v0_95_0.pdf) provided, create a markdown documentation page for the specific section mentioned. The page should be created within the `spec/0.95.0 folder`
#### Headings
There should be only one H1 heading which will presented as the title of the page.
Any other headings should be H2 or smaller according to their section.
#### Equations
Equations should use the built-in feature.
https://squidfunk.github.io/mkdocs-material/reference/mathjax/
#### Tables
Tables should use the built-in feature.
https://squidfunk.github.io/mkdocs-material/reference/data-tables/
#### Images
We want to keep the images matching the existing style of the site. These should not be copy and pasted from the document, but created preferably. If there is no other option, screenshots from the document will be accepted.
The images may be created as svg's using https://themeisle.com/illustrations/ and/or https://undraw.co/ with the color (#80CBC4) (Preferred)
OR
By using mermaid documentation:
https://mermaid-js.github.io/mermaid/#/
https://squidfunk.github.io/mkdocs-material/reference/diagrams/
#### Green and Blue Boxes
All blue boxes should be Note admonitions.
All green boxes should be Important admonitions
https://squidfunk.github.io/mkdocs-material/reference/admonitions
#### Navigation
This is the overall navigation
```
Current or 0.95.0 <-- Overview
--- Structure <-- ElectionGuard Structure
--- Components <-- ElectionGuard Components (2nd ElectionGuard Components)
--- Baseline Parameters
--- Key Generation
--- Ballot Encryption
--- Ballot Aggregation
--- Verifiable Decryption
--- Election Record <-- The Election Record
--- Verifier Construction
------ Parameter Validation
------ Guardian Public-Key Validation
------ ...
--- Applications <-- Applications to end-end verifiability and risk limited audits
--- Acknowledgements
```
This specific page should be linked under both 0.95.0 and Current in the `mkdocs.yml`.
An example is https://www.electionguard.vote/spec/0.95.0/1_Overview/
#### Pull Request Requests
Any pull request should specifically tag @benaloh and @keithrfung as reviewers. The pull request MUST include copious screenshots.
### Anything else?
_No response_
|
non_process
|
📝 document applications section of specification in markdown is there an existing issue for this i have searched the existing issues suggestion document applications section of specification in markdown for easy consumption on the web this should be as close as possible to a to translation this section is actually called applications to end to end verifiability and risk limiting audits possible implementation using the specification provided create a markdown documentation page for the specific section mentioned the page should be created within the spec folder headings there should be only one heading which will presented as the title of the page any other headings should be or smaller according to their section equations equations should use the built in feature tables tables should use the built in feature images we want to keep the images matching the existing style of the site these should not be copy and pasted from the document but created preferably if there is no other option screenshots from the document will be accepted the images may be created as svg s using and or with the color preferred or by using mermaid documentation green and blue boxes all blue boxes should be note admonitions all green boxes should be important admonitions navigation this is the overall navigation current or overview structure electionguard structure components electionguard components electionguard components baseline parameters key generation ballot encryption ballot aggregation verifiable decryption election record the election record verifier construction parameter validation guardian public key validation applications applications to end end verifiability and risk limited audits acknowledgements this specific page should be linked under both and current in the mkdocs yml an example is pull request requests any pull request should specifically tag benaloh and keithrfung as reviewers the pull request must include copious screenshots anything else no response
| 0
|
3,671
| 6,706,164,776
|
IssuesEvent
|
2017-10-12 05:24:34
|
rancher/rancher
|
https://api.github.com/repos/rancher/rancher
|
closed
|
Rancher webhooks not support Aliyun docker hub
|
area/webhooks kind/feature process/cherry-pick process/cherry-picked status/resolved status/to-test team/cn
|
Our company use Aliyun docker hub, it is auto tigger webhook and not support configuration parameter, can you support Aliyun docker hub webhook?
|
2.0
|
Rancher webhooks not support Aliyun docker hub - Our company use Aliyun docker hub, it is auto tigger webhook and not support configuration parameter, can you support Aliyun docker hub webhook?
|
process
|
rancher webhooks not support aliyun docker hub our company use aliyun docker hub it is auto tigger webhook and not support configuration parameter can you support aliyun docker hub webhook
| 1
|
759,049
| 26,578,545,410
|
IssuesEvent
|
2023-01-22 05:33:43
|
o3de/sig-testing
|
https://api.github.com/repos/o3de/sig-testing
|
opened
|
Create Roadmap View
|
needs-priority
|
Hi! SIG release is working to help the O3DE community to get visibility of the O3DE roadmap. Full context can be read here: https://github.com/o3de/sig-release/issues/79.
In order to achieve that goal, we need your help to create the roadmap for your SIG by **February 6th, 2023**, and start giving brief updates about the roadmap items at the **Joint TSC meeting on February 28th, 2023**. Instruction to create the roadmap view can be read in the RFC section "Roadmap Review in TSC monthly meeting".
Let me know if you have any concerns with the dates or any questions about the ask!
|
1.0
|
Create Roadmap View - Hi! SIG release is working to help the O3DE community to get visibility of the O3DE roadmap. Full context can be read here: https://github.com/o3de/sig-release/issues/79.
In order to achieve that goal, we need your help to create the roadmap for your SIG by **February 6th, 2023**, and start giving brief updates about the roadmap items at the **Joint TSC meeting on February 28th, 2023**. Instruction to create the roadmap view can be read in the RFC section "Roadmap Review in TSC monthly meeting".
Let me know if you have any concerns with the dates or any questions about the ask!
|
non_process
|
create roadmap view hi sig release is working to help the community to get visibility of the roadmap full context can be read here in order to achieve that goal we need your help to create the roadmap for your sig by february and start giving brief updates about the roadmap items at the joint tsc meeting on february instruction to create the roadmap view can be read in the rfc section roadmap review in tsc monthly meeting let me know if you have any concerns with the dates or any questions about the ask
| 0
|
19,989
| 26,465,240,430
|
IssuesEvent
|
2023-01-16 22:26:02
|
nion-software/nionswift
|
https://api.github.com/repos/nion-software/nionswift
|
closed
|
FFT processing should properly calibrate the intensity units of the result
|
type - bug f - processing f - filtering/masking
|
The FFT scaling in Swift is chosen so that the RMS value is the same for the source and result of the FFT.
The resulting intensity should be calibrated such that the magnitude of the complex data is the same as the original data.
[A reference discussion on stack overflow](https://stackoverflow.com/questions/1523814/units-of-a-fourier-transform-fft-when-doing-spectral-analysis-of-a-signal).
|
1.0
|
FFT processing should properly calibrate the intensity units of the result - The FFT scaling in Swift is chosen so that the RMS value is the same for the source and result of the FFT.
The resulting intensity should be calibrated such that the magnitude of the complex data is the same as the original data.
[A reference discussion on stack overflow](https://stackoverflow.com/questions/1523814/units-of-a-fourier-transform-fft-when-doing-spectral-analysis-of-a-signal).
|
process
|
fft processing should properly calibrate the intensity units of the result the fft scaling in swift is chosen so that the rms value is the same for the source and result of the fft the resulting intensity should be calibrated such that the magnitude of the complex data is the same as the original data
| 1
|
279,968
| 21,190,011,750
|
IssuesEvent
|
2022-04-08 16:18:59
|
alphonsekoh/ICT2106-P2-05
|
https://api.github.com/repos/alphonsekoh/ICT2106-P2-05
|
closed
|
Class Diagrams Revision
|
documentation
|
- [x] Prof Review Comments
- [x] Update Class Diagram
- [x] Class Diagram Revision
|
1.0
|
Class Diagrams Revision - - [x] Prof Review Comments
- [x] Update Class Diagram
- [x] Class Diagram Revision
|
non_process
|
class diagrams revision prof review comments update class diagram class diagram revision
| 0
|
21,118
| 28,086,730,768
|
IssuesEvent
|
2023-03-30 10:16:06
|
ASWE-PDA/Personal-Digital-Agent
|
https://api.github.com/repos/ASWE-PDA/Personal-Digital-Agent
|
closed
|
Text-to-speech
|
enhancement adapter speech processing
|
As a user,
I want the agent to put what it wants to say in coherent sentences
so that I can understand the agent easily.
Acceptance criteria:
- [ ] API for text-to-speech has been selected
- [ ] API can be called by an adapter module in the backend
|
1.0
|
Text-to-speech - As a user,
I want the agent to put what it wants to say in coherent sentences
so that I can understand the agent easily.
Acceptance criteria:
- [ ] API for text-to-speech has been selected
- [ ] API can be called by an adapter module in the backend
|
process
|
text to speech as a user i want the agent to put what it wants to say in coherent sentences so that i can understand the agent easily acceptance criteria api for text to speech has been selected api can be called by an adapter module in the backend
| 1
|
352,252
| 32,055,398,657
|
IssuesEvent
|
2023-09-24 02:34:25
|
apache/helix
|
https://api.github.com/repos/apache/helix
|
opened
|
[Failed CI Test] testSessionExpiredWhenResetHandlers(org.apache.helix.manager.zk.TestHandleSession)
|
FailedTestTracking
|
This issue is created for tracking unstable test: testSessionExpiredWhenResetHandlers(org.apache.helix.manager.zk.TestHandleSession)
|
1.0
|
[Failed CI Test] testSessionExpiredWhenResetHandlers(org.apache.helix.manager.zk.TestHandleSession) - This issue is created for tracking unstable test: testSessionExpiredWhenResetHandlers(org.apache.helix.manager.zk.TestHandleSession)
|
non_process
|
testsessionexpiredwhenresethandlers org apache helix manager zk testhandlesession this issue is created for tracking unstable test testsessionexpiredwhenresethandlers org apache helix manager zk testhandlesession
| 0
|
7,925
| 11,100,250,441
|
IssuesEvent
|
2019-12-16 18:46:47
|
arcus-azure/arcus.messaging
|
https://api.github.com/repos/arcus-azure/arcus.messaging
|
opened
|
Provide Azure Service Bus plugin for managing serialization information
|
area:message-processing feature
|
Provide Azure Service Bus plugin for managing serialization information by adding it to the message context and interpreting it on read.
|
1.0
|
Provide Azure Service Bus plugin for managing serialization information - Provide Azure Service Bus plugin for managing serialization information by adding it to the message context and interpreting it on read.
|
process
|
provide azure service bus plugin for managing serialization information provide azure service bus plugin for managing serialization information by adding it to the message context and interpreting it on read
| 1
|
744,045
| 25,925,763,909
|
IssuesEvent
|
2022-12-16 04:14:20
|
wso2/api-manager
|
https://api.github.com/repos/wso2/api-manager
|
closed
|
APICTL 4.2.0 pre-alpha Testing
|
Type/Task Priority/Normal Component/APICTL Missing/Component 4.2.0-alpha
|
### Description
This is to track APICTL testing 4.2.0 testing progress of @msm1992
- [x] Add and deploy APIs for the first time to a Repo
```
1. Export multiple APIs from dev using export api command
2. Extract and add them to source repository
3. Set source repository
4. Commit them (git add & git commit)
5. apictl vcs init
6. apictl vcs deploy -e prod
```
- [x] Add Applications to the above repo
```
7. Export an application from dev that is subscribed to the API
8. extract and add it to the above repository
9. Commit the application project. (git add & git commit)
10. apictl vcs deploy -e prod
```
- [x] Add an API Product to the above repo
```
11. Export an api-product from dev that is created from one of the APIs
12. extract and add it to the above repository
13. Commit the api-product project. (git add & git commit)
14. apictl vcs deploy -e prod
```
- [x] Do an errornous change and verify rollback
```
15. Do an errornous change in one of the APIs - eg: add a non existing subscription tier
16. Do a non-errornous change in one of the APIs - eg: changing the description
17. Commit both the changes. (git add & git commit)
18. apictl vcs deploy -e prod
```
- [x] Delete an API, API Product and an application (before setting --vcs-deletion-enabled=true)
```
19. Delete an API, API Product and an application in the same repo
20. Commit the changes (git add & git commit)
21. apictl vcs deploy -e prod
```
- [x] Delete an API, API Product and an application (after setting --vcs-deletion-enabled=true)
```
22. Execute apictl set --vcs-deletion-enabled=true
23. Now try, apictl vcs deploy -e prod
```
- [x] Set vcs-config-path to a new location
```
1. Start from the begining - Export multiple APIs, API Products and applications
2. Extract the and add them to a git reposidtory
3.Commit them (git add & git commit)
4. apictl vcs init
5. Set the vcs-config-path to a custom location by executing apictl set --vcs-config-path /home/foo/vcs-config.yaml
6. apictl vcs deploy -e prod
```
- [x] Add and deploy API/API Products for the first time to a Repo
```
1. Export multiple API/APIProducts s from dev using export api command
2. Extract and add them to source repository
3. Set source repository
4. Set deployment repository
5. Generate deployment dirs for some APIs and API Products in the deployment repo
6. Replace the params files inside the deployment repo with the suitable ones
7. Commit them (git add & git commit) - files in both source and deployment repos seperately as two git repos
8. apictl vcs init
9. apictl vcs deploy -e prod
```
### Affected Component
APICTL
### Version
4.2.0-alpha
### Related Issues
_No response_
### Suggested Labels
_No response_
|
1.0
|
APICTL 4.2.0 pre-alpha Testing - ### Description
This is to track APICTL testing 4.2.0 testing progress of @msm1992
- [x] Add and deploy APIs for the first time to a Repo
```
1. Export multiple APIs from dev using export api command
2. Extract and add them to source repository
3. Set source repository
4. Commit them (git add & git commit)
5. apictl vcs init
6. apictl vcs deploy -e prod
```
- [x] Add Applications to the above repo
```
7. Export an application from dev that is subscribed to the API
8. extract and add it to the above repository
9. Commit the application project. (git add & git commit)
10. apictl vcs deploy -e prod
```
- [x] Add an API Product to the above repo
```
11. Export an api-product from dev that is created from one of the APIs
12. extract and add it to the above repository
13. Commit the api-product project. (git add & git commit)
14. apictl vcs deploy -e prod
```
- [x] Do an errornous change and verify rollback
```
15. Do an errornous change in one of the APIs - eg: add a non existing subscription tier
16. Do a non-errornous change in one of the APIs - eg: changing the description
17. Commit both the changes. (git add & git commit)
18. apictl vcs deploy -e prod
```
- [x] Delete an API, API Product and an application (before setting --vcs-deletion-enabled=true)
```
19. Delete an API, API Product and an application in the same repo
20. Commit the changes (git add & git commit)
21. apictl vcs deploy -e prod
```
- [x] Delete an API, API Product and an application (after setting --vcs-deletion-enabled=true)
```
22. Execute apictl set --vcs-deletion-enabled=true
23. Now try, apictl vcs deploy -e prod
```
- [x] Set vcs-config-path to a new location
```
1. Start from the begining - Export multiple APIs, API Products and applications
2. Extract the and add them to a git reposidtory
3.Commit them (git add & git commit)
4. apictl vcs init
5. Set the vcs-config-path to a custom location by executing apictl set --vcs-config-path /home/foo/vcs-config.yaml
6. apictl vcs deploy -e prod
```
- [x] Add and deploy API/API Products for the first time to a Repo
```
1. Export multiple API/APIProducts s from dev using export api command
2. Extract and add them to source repository
3. Set source repository
4. Set deployment repository
5. Generate deployment dirs for some APIs and API Products in the deployment repo
6. Replace the params files inside the deployment repo with the suitable ones
7. Commit them (git add & git commit) - files in both source and deployment repos seperately as two git repos
8. apictl vcs init
9. apictl vcs deploy -e prod
```
### Affected Component
APICTL
### Version
4.2.0-alpha
### Related Issues
_No response_
### Suggested Labels
_No response_
|
non_process
|
apictl pre alpha testing description this is to track apictl testing testing progress of add and deploy apis for the first time to a repo export multiple apis from dev using export api command extract and add them to source repository set source repository commit them git add git commit apictl vcs init apictl vcs deploy e prod add applications to the above repo export an application from dev that is subscribed to the api extract and add it to the above repository commit the application project git add git commit apictl vcs deploy e prod add an api product to the above repo export an api product from dev that is created from one of the apis extract and add it to the above repository commit the api product project git add git commit apictl vcs deploy e prod do an errornous change and verify rollback do an errornous change in one of the apis eg add a non existing subscription tier do a non errornous change in one of the apis eg changing the description commit both the changes git add git commit apictl vcs deploy e prod delete an api api product and an application before setting vcs deletion enabled true delete an api api product and an application in the same repo commit the changes git add git commit apictl vcs deploy e prod delete an api api product and an application after setting vcs deletion enabled true execute apictl set vcs deletion enabled true now try apictl vcs deploy e prod set vcs config path to a new location start from the begining export multiple apis api products and applications extract the and add them to a git reposidtory commit them git add git commit apictl vcs init set the vcs config path to a custom location by executing apictl set vcs config path home foo vcs config yaml apictl vcs deploy e prod add and deploy api api products for the first time to a repo export multiple api apiproducts s from dev using export api command extract and add them to source repository set source repository set deployment repository generate deployment dirs for some apis and api products in the deployment repo replace the params files inside the deployment repo with the suitable ones commit them git add git commit files in both source and deployment repos seperately as two git repos apictl vcs init apictl vcs deploy e prod affected component apictl version alpha related issues no response suggested labels no response
| 0
|
8,574
| 11,742,155,106
|
IssuesEvent
|
2020-03-11 23:47:56
|
MicrosoftDocs/windows-uwp
|
https://api.github.com/repos/MicrosoftDocs/windows-uwp
|
closed
|
Error in code snipped
|
Pri2 processes-and-threading/tech uwp/prod
|
I get the following error from running the first code snipped (getting serialcommunication devices in an async task with lambda expression).
If I just include this code snipped into a freshly made Visual Studio 2019 Community Edition UWP C++ project I get the following errormessage about "this" in the lambda expression brakets:
"Error (active) E1740 lambda captured variable of type "App1::App ^*" cannot be copied to closure class field of type "App1::App ^"
If I found out correctly the error is present since a long time?
https://developercommunity.visualstudio.com/content/problem/488185/e1740-reported-in-vs2019-rc-when-capture-ccx-this.html
Sadly the accepted "solution" with:
auto _this = this;
does not work.
The code will still compile successfully even with the error.
How to solve this problem?
---
#### Dokumentdetails
⚠ *Bearbeiten Sie diesen Abschnitt nicht. Er ist für die Verknüpfung von docs.microsoft.com zum GitHub-Artikel erforderlich.*
* ID: df902334-d9ec-5bf1-c61f-f68e79787e47
* Version Independent ID: b0fe703c-5fab-d672-1260-c04018340c8b
* Content: [Asynchrone Programmierung in C++ - UWP applications](https://docs.microsoft.com/de-de/windows/uwp/threading-async/asynchronous-programming-in-cpp-universal-windows-platform-apps#feedback)
* Content Source: [windows-apps-src/threading-async/asynchronous-programming-in-cpp-universal-windows-platform-apps.md](https://github.com/MicrosoftDocs/windows-uwp.de-de/blob/live/windows-apps-src/threading-async/asynchronous-programming-in-cpp-universal-windows-platform-apps.md)
* Product: **uwp**
* Technology: **processes-and-threading**
* GitHub Login: @drewbatgit
* Microsoft Alias: **drewbat**
|
1.0
|
Error in code snipped - I get the following error from running the first code snipped (getting serialcommunication devices in an async task with lambda expression).
If I just include this code snipped into a freshly made Visual Studio 2019 Community Edition UWP C++ project I get the following errormessage about "this" in the lambda expression brakets:
"Error (active) E1740 lambda captured variable of type "App1::App ^*" cannot be copied to closure class field of type "App1::App ^"
If I found out correctly the error is present since a long time?
https://developercommunity.visualstudio.com/content/problem/488185/e1740-reported-in-vs2019-rc-when-capture-ccx-this.html
Sadly the accepted "solution" with:
auto _this = this;
does not work.
The code will still compile successfully even with the error.
How to solve this problem?
---
#### Dokumentdetails
⚠ *Bearbeiten Sie diesen Abschnitt nicht. Er ist für die Verknüpfung von docs.microsoft.com zum GitHub-Artikel erforderlich.*
* ID: df902334-d9ec-5bf1-c61f-f68e79787e47
* Version Independent ID: b0fe703c-5fab-d672-1260-c04018340c8b
* Content: [Asynchrone Programmierung in C++ - UWP applications](https://docs.microsoft.com/de-de/windows/uwp/threading-async/asynchronous-programming-in-cpp-universal-windows-platform-apps#feedback)
* Content Source: [windows-apps-src/threading-async/asynchronous-programming-in-cpp-universal-windows-platform-apps.md](https://github.com/MicrosoftDocs/windows-uwp.de-de/blob/live/windows-apps-src/threading-async/asynchronous-programming-in-cpp-universal-windows-platform-apps.md)
* Product: **uwp**
* Technology: **processes-and-threading**
* GitHub Login: @drewbatgit
* Microsoft Alias: **drewbat**
|
process
|
error in code snipped i get the following error from running the first code snipped getting serialcommunication devices in an async task with lambda expression if i just include this code snipped into a freshly made visual studio community edition uwp c project i get the following errormessage about this in the lambda expression brakets error active lambda captured variable of type app cannot be copied to closure class field of type app if i found out correctly the error is present since a long time sadly the accepted solution with auto this this does not work the code will still compile successfully even with the error how to solve this problem dokumentdetails ⚠ bearbeiten sie diesen abschnitt nicht er ist für die verknüpfung von docs microsoft com zum github artikel erforderlich id version independent id content content source product uwp technology processes and threading github login drewbatgit microsoft alias drewbat
| 1
|
130,968
| 5,140,283,676
|
IssuesEvent
|
2017-01-12 04:04:50
|
Microsoft/msbuild
|
https://api.github.com/repos/Microsoft/msbuild
|
closed
|
Upgrade Immutable Collections to 1.3.1
|
Priority 0
|
This is needed to match Roslyn version. Causing issues with ngen and perf in some VS scenarios.
|
1.0
|
Upgrade Immutable Collections to 1.3.1 - This is needed to match Roslyn version. Causing issues with ngen and perf in some VS scenarios.
|
non_process
|
upgrade immutable collections to this is needed to match roslyn version causing issues with ngen and perf in some vs scenarios
| 0
|
218,717
| 16,768,881,676
|
IssuesEvent
|
2021-06-14 12:33:47
|
NeuroTechX/moabb
|
https://api.github.com/repos/NeuroTechX/moabb
|
closed
|
Add a what's new file
|
documentation easy help wanted
|
It could be something that is displayed on github page and on documentation
See MNE, scikit-learn or https://github.com/braindecode/braindecode
|
1.0
|
Add a what's new file - It could be something that is displayed on github page and on documentation
See MNE, scikit-learn or https://github.com/braindecode/braindecode
|
non_process
|
add a what s new file it could be something that is displayed on github page and on documentation see mne scikit learn or
| 0
|
11,715
| 14,546,746,317
|
IssuesEvent
|
2020-12-15 21:44:37
|
MicrosoftDocs/azure-devops-docs
|
https://api.github.com/repos/MicrosoftDocs/azure-devops-docs
|
closed
|
Does Scheduled Trigger have 'paths' keyword like Push Trigger?
|
devops-cicd-process/tech devops/prod product-feedback
|
Hi,
It seems that the scheduled trigger does not have the `paths` keyword/property. It means that we cannot specify which directory paths we want to watch and evaluate code changes before we run scheduled pipelines. Am I correct?
If so, I suggest implementing the `paths` property for the scheduled trigger. It seems to be useful in the big repositories where we have many projects (especially, monorepos).
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 2ea2c851-bd1e-cddc-b4d0-e9f4112b8565
* Version Independent ID: 07c23fdd-14b5-985b-1c63-3f26f3a216ad
* Content: [Configure schedules to run pipelines - Azure Pipelines](https://docs.microsoft.com/en-us/azure/devops/pipelines/process/scheduled-triggers?view=azure-devops&tabs=yaml)
* Content Source: [docs/pipelines/process/scheduled-triggers.md](https://github.com/MicrosoftDocs/azure-devops-docs/blob/master/docs/pipelines/process/scheduled-triggers.md)
* Product: **devops**
* Technology: **devops-cicd-process**
* GitHub Login: @steved0x
* Microsoft Alias: **sdanie**
|
1.0
|
Does Scheduled Trigger have 'paths' keyword like Push Trigger? - Hi,
It seems that the scheduled trigger does not have the `paths` keyword/property. It means that we cannot specify which directory paths we want to watch and evaluate code changes before we run scheduled pipelines. Am I correct?
If so, I suggest implementing the `paths` property for the scheduled trigger. It seems to be useful in the big repositories where we have many projects (especially, monorepos).
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 2ea2c851-bd1e-cddc-b4d0-e9f4112b8565
* Version Independent ID: 07c23fdd-14b5-985b-1c63-3f26f3a216ad
* Content: [Configure schedules to run pipelines - Azure Pipelines](https://docs.microsoft.com/en-us/azure/devops/pipelines/process/scheduled-triggers?view=azure-devops&tabs=yaml)
* Content Source: [docs/pipelines/process/scheduled-triggers.md](https://github.com/MicrosoftDocs/azure-devops-docs/blob/master/docs/pipelines/process/scheduled-triggers.md)
* Product: **devops**
* Technology: **devops-cicd-process**
* GitHub Login: @steved0x
* Microsoft Alias: **sdanie**
|
process
|
does scheduled trigger have paths keyword like push trigger hi it seems that the scheduled trigger does not have the paths keyword property it means that we cannot specify which directory paths we want to watch and evaluate code changes before we run scheduled pipelines am i correct if so i suggest implementing the paths property for the scheduled trigger it seems to be useful in the big repositories where we have many projects especially monorepos document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id cddc version independent id content content source product devops technology devops cicd process github login microsoft alias sdanie
| 1
|
6,081
| 8,925,941,882
|
IssuesEvent
|
2019-01-22 01:36:58
|
googleapis/nodejs-datastore
|
https://api.github.com/repos/googleapis/nodejs-datastore
|
closed
|
Ship 3.0
|
type: process
|
Thanks for stopping by to let us know something could be better!
**PLEASE READ**: If you have a support contract with Google, please create an issue in the [support console](https://cloud.google.com/support/) instead of filing on GitHub. This will ensure a timely response.
Please run down the following list and make sure you've tried the usual "quick fixes":
- [x] Search the issues already opened: https://github.com/googleapis/nodejs-datastore/issues
- [x] Search the issues on our "catch-all" repository: https://github.com/googleapis/google-cloud-node
- [x] Search StackOverflow: http://stackoverflow.com/questions/tagged/google-cloud-platform+node.js
If you are still having issues, please be sure to include as much information as possible:
#### Environment details
- OS: Mac OS X
- Node.js version: 11.2.0
- npm version: 6.4.1
- `@google-cloud/datastore` version: 2.0.0
#### Steps to reproduce
Try to run the first code example in https://cloud.google.com/datastore/docs/reference/libraries
```js
// Imports the Google Cloud client library
const {Datastore} = require('@google-cloud/datastore');
// Your Google Cloud Platform project ID
const projectId = 'YOUR_PROJECT_ID';
// Creates a client
const datastore = new Datastore({
projectId: projectId,
});
```
You get the following error:
```js
TypeError: Datastore is not a constructor
```
The fix is simple - just remove the curly brackets in the require line:
```js
const Datastore = require('@google-cloud/datastore');
```
A PR fixing the examples will follow shortly...
|
1.0
|
Ship 3.0 - Thanks for stopping by to let us know something could be better!
**PLEASE READ**: If you have a support contract with Google, please create an issue in the [support console](https://cloud.google.com/support/) instead of filing on GitHub. This will ensure a timely response.
Please run down the following list and make sure you've tried the usual "quick fixes":
- [x] Search the issues already opened: https://github.com/googleapis/nodejs-datastore/issues
- [x] Search the issues on our "catch-all" repository: https://github.com/googleapis/google-cloud-node
- [x] Search StackOverflow: http://stackoverflow.com/questions/tagged/google-cloud-platform+node.js
If you are still having issues, please be sure to include as much information as possible:
#### Environment details
- OS: Mac OS X
- Node.js version: 11.2.0
- npm version: 6.4.1
- `@google-cloud/datastore` version: 2.0.0
#### Steps to reproduce
Try to run the first code example in https://cloud.google.com/datastore/docs/reference/libraries
```js
// Imports the Google Cloud client library
const {Datastore} = require('@google-cloud/datastore');
// Your Google Cloud Platform project ID
const projectId = 'YOUR_PROJECT_ID';
// Creates a client
const datastore = new Datastore({
projectId: projectId,
});
```
You get the following error:
```js
TypeError: Datastore is not a constructor
```
The fix is simple - just remove the curly brackets in the require line:
```js
const Datastore = require('@google-cloud/datastore');
```
A PR fixing the examples will follow shortly...
|
process
|
ship thanks for stopping by to let us know something could be better please read if you have a support contract with google please create an issue in the instead of filing on github this will ensure a timely response please run down the following list and make sure you ve tried the usual quick fixes search the issues already opened search the issues on our catch all repository search stackoverflow if you are still having issues please be sure to include as much information as possible environment details os mac os x node js version npm version google cloud datastore version steps to reproduce try to run the first code example in js imports the google cloud client library const datastore require google cloud datastore your google cloud platform project id const projectid your project id creates a client const datastore new datastore projectid projectid you get the following error js typeerror datastore is not a constructor the fix is simple just remove the curly brackets in the require line js const datastore require google cloud datastore a pr fixing the examples will follow shortly
| 1
|
7,218
| 10,347,676,195
|
IssuesEvent
|
2019-09-04 17:57:59
|
GetTerminus/terminus-ui
|
https://api.github.com/repos/GetTerminus/terminus-ui
|
closed
|
Backfill changelog with release information
|
Focus: community Goal: Process Improvement P4: Nice to Have Type: chore
|
Several times we've needed to look back and know when something was changed. It can be tough to look back through GitHub releases for that information. If it was all added to the existing `CHANGELOG.md` we could search within a single page.
- [ ] Backfill all release information from `v7.0.0` forward
|
1.0
|
Backfill changelog with release information - Several times we've needed to look back and know when something was changed. It can be tough to look back through GitHub releases for that information. If it was all added to the existing `CHANGELOG.md` we could search within a single page.
- [ ] Backfill all release information from `v7.0.0` forward
|
process
|
backfill changelog with release information several times we ve needed to look back and know when something was changed it can be tough to look back through github releases for that information if it was all added to the existing changelog md we could search within a single page backfill all release information from forward
| 1
|
7,644
| 10,738,030,237
|
IssuesEvent
|
2019-10-29 14:08:53
|
tueit/it_management
|
https://api.github.com/repos/tueit/it_management
|
reopened
|
add IT Management Table to Issue
|
Please check & close bug enhancement process task usability
|
please add IT Management Table to Issue. Add new Section IT Management after section Details. Content of this table should also be transfered to IT when created.
On creation of IT Ticket we need a quick entry with:
- Project (Projects)
- Customer
- Contact
- Assignee (ToDo)
- Due Date (ToDo)
Add field (Typ Link) with IT Ticket in Issue
Change Issue status to closed.
|
1.0
|
add IT Management Table to Issue - please add IT Management Table to Issue. Add new Section IT Management after section Details. Content of this table should also be transfered to IT when created.
On creation of IT Ticket we need a quick entry with:
- Project (Projects)
- Customer
- Contact
- Assignee (ToDo)
- Due Date (ToDo)
Add field (Typ Link) with IT Ticket in Issue
Change Issue status to closed.
|
process
|
add it management table to issue please add it management table to issue add new section it management after section details content of this table should also be transfered to it when created on creation of it ticket we need a quick entry with project projects customer contact assignee todo due date todo add field typ link with it ticket in issue change issue status to closed
| 1
|
202,097
| 23,055,426,131
|
IssuesEvent
|
2022-07-25 03:51:35
|
dmyers87/seeds-packets
|
https://api.github.com/repos/dmyers87/seeds-packets
|
reopened
|
CVE-2021-35065 (High) detected in multiple libraries
|
security vulnerability
|
## CVE-2021-35065 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>glob-parent-5.1.0.tgz</b>, <b>glob-parent-5.1.2.tgz</b>, <b>glob-parent-3.1.0.tgz</b></p></summary>
<p>
<details><summary><b>glob-parent-5.1.0.tgz</b></p></summary>
<p>Extract the non-magic parent path from a glob string.</p>
<p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.0.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/glob-parent</p>
<p>
Dependency Hierarchy:
- lint-staged-9.5.0.tgz (Root Library)
- del-5.1.0.tgz
- globby-10.0.2.tgz
- fast-glob-3.1.1.tgz
- :x: **glob-parent-5.1.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>glob-parent-5.1.2.tgz</b></p></summary>
<p>Extract the non-magic parent path from a glob string.</p>
<p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/glob-parent</p>
<p>
Dependency Hierarchy:
- lerna-3.22.1.tgz (Root Library)
- info-3.21.0.tgz
- command-3.21.0.tgz
- project-3.21.0.tgz
- :x: **glob-parent-5.1.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>glob-parent-3.1.0.tgz</b></p></summary>
<p>Strips glob magic from a string to provide the parent directory path</p>
<p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/glob-parent</p>
<p>
Dependency Hierarchy:
- globby-9.2.0.tgz (Root Library)
- fast-glob-2.2.6.tgz
- :x: **glob-parent-3.1.0.tgz** (Vulnerable Library)
</details>
<p>Found in base branch: <b>develop</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The package glob-parent before 6.0.1 are vulnerable to Regular Expression Denial of Service (ReDoS)
<p>Publish Date: 2021-06-22
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-35065>CVE-2021-35065</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: 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/gulpjs/glob-parent/pull/49">https://github.com/gulpjs/glob-parent/pull/49</a></p>
<p>Release Date: 2021-06-22</p>
<p>Fix Resolution: glob-parent - 6.0.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"glob-parent","packageVersion":"5.1.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"lint-staged:9.5.0;del:5.1.0;globby:10.0.2;fast-glob:3.1.1;glob-parent:5.1.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"glob-parent - 6.0.1","isBinary":false},{"packageType":"javascript/Node.js","packageName":"glob-parent","packageVersion":"5.1.2","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"lerna:3.22.1;@lerna/info:3.21.0;@lerna/command:3.21.0;@lerna/project:3.21.0;glob-parent:5.1.2","isMinimumFixVersionAvailable":true,"minimumFixVersion":"glob-parent - 6.0.1","isBinary":false},{"packageType":"javascript/Node.js","packageName":"glob-parent","packageVersion":"3.1.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"globby:9.2.0;fast-glob:2.2.6;glob-parent:3.1.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"glob-parent - 6.0.1","isBinary":false}],"baseBranches":["develop"],"vulnerabilityIdentifier":"CVE-2021-35065","vulnerabilityDetails":"The package glob-parent before 6.0.1 are vulnerable to Regular Expression Denial of Service (ReDoS) ","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-35065","cvss3Severity":"medium","cvss3Score":"5.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Changed","C":"Low","UI":"Required","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> -->
|
True
|
CVE-2021-35065 (High) detected in multiple libraries - ## CVE-2021-35065 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>glob-parent-5.1.0.tgz</b>, <b>glob-parent-5.1.2.tgz</b>, <b>glob-parent-3.1.0.tgz</b></p></summary>
<p>
<details><summary><b>glob-parent-5.1.0.tgz</b></p></summary>
<p>Extract the non-magic parent path from a glob string.</p>
<p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.0.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/glob-parent</p>
<p>
Dependency Hierarchy:
- lint-staged-9.5.0.tgz (Root Library)
- del-5.1.0.tgz
- globby-10.0.2.tgz
- fast-glob-3.1.1.tgz
- :x: **glob-parent-5.1.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>glob-parent-5.1.2.tgz</b></p></summary>
<p>Extract the non-magic parent path from a glob string.</p>
<p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/glob-parent</p>
<p>
Dependency Hierarchy:
- lerna-3.22.1.tgz (Root Library)
- info-3.21.0.tgz
- command-3.21.0.tgz
- project-3.21.0.tgz
- :x: **glob-parent-5.1.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>glob-parent-3.1.0.tgz</b></p></summary>
<p>Strips glob magic from a string to provide the parent directory path</p>
<p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/glob-parent</p>
<p>
Dependency Hierarchy:
- globby-9.2.0.tgz (Root Library)
- fast-glob-2.2.6.tgz
- :x: **glob-parent-3.1.0.tgz** (Vulnerable Library)
</details>
<p>Found in base branch: <b>develop</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The package glob-parent before 6.0.1 are vulnerable to Regular Expression Denial of Service (ReDoS)
<p>Publish Date: 2021-06-22
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-35065>CVE-2021-35065</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: 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/gulpjs/glob-parent/pull/49">https://github.com/gulpjs/glob-parent/pull/49</a></p>
<p>Release Date: 2021-06-22</p>
<p>Fix Resolution: glob-parent - 6.0.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"glob-parent","packageVersion":"5.1.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"lint-staged:9.5.0;del:5.1.0;globby:10.0.2;fast-glob:3.1.1;glob-parent:5.1.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"glob-parent - 6.0.1","isBinary":false},{"packageType":"javascript/Node.js","packageName":"glob-parent","packageVersion":"5.1.2","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"lerna:3.22.1;@lerna/info:3.21.0;@lerna/command:3.21.0;@lerna/project:3.21.0;glob-parent:5.1.2","isMinimumFixVersionAvailable":true,"minimumFixVersion":"glob-parent - 6.0.1","isBinary":false},{"packageType":"javascript/Node.js","packageName":"glob-parent","packageVersion":"3.1.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"globby:9.2.0;fast-glob:2.2.6;glob-parent:3.1.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"glob-parent - 6.0.1","isBinary":false}],"baseBranches":["develop"],"vulnerabilityIdentifier":"CVE-2021-35065","vulnerabilityDetails":"The package glob-parent before 6.0.1 are vulnerable to Regular Expression Denial of Service (ReDoS) ","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-35065","cvss3Severity":"medium","cvss3Score":"5.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Changed","C":"Low","UI":"Required","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> -->
|
non_process
|
cve high detected in multiple libraries cve medium severity vulnerability vulnerable libraries glob parent tgz glob parent tgz glob parent tgz glob parent tgz extract the non magic parent path from a glob string library home page a href path to dependency file package json path to vulnerable library node modules glob parent dependency hierarchy lint staged tgz root library del tgz globby tgz fast glob tgz x glob parent tgz vulnerable library glob parent tgz extract the non magic parent path from a glob string library home page a href path to dependency file package json path to vulnerable library node modules glob parent dependency hierarchy lerna tgz root library info tgz command tgz project tgz x glob parent tgz vulnerable library glob parent tgz strips glob magic from a string to provide the parent directory path library home page a href path to dependency file package json path to vulnerable library node modules glob parent dependency hierarchy globby tgz root library fast glob tgz x glob parent tgz vulnerable library found in base branch develop vulnerability details the package glob parent before are vulnerable to regular expression denial of service redos 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 glob parent isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree lint staged del globby fast glob glob parent isminimumfixversionavailable true minimumfixversion glob parent isbinary false packagetype javascript node js packagename glob parent packageversion packagefilepaths istransitivedependency true dependencytree lerna lerna info lerna command lerna project glob parent isminimumfixversionavailable true minimumfixversion glob parent isbinary false packagetype javascript node js packagename glob parent packageversion packagefilepaths istransitivedependency true dependencytree globby fast glob glob parent isminimumfixversionavailable true minimumfixversion glob parent isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails the package glob parent before are vulnerable to regular expression denial of service redos vulnerabilityurl
| 0
|
16,299
| 20,947,743,982
|
IssuesEvent
|
2022-03-26 05:29:19
|
PySavant/AVA
|
https://api.github.com/repos/PySavant/AVA
|
opened
|
Model Processing Speed
|
Area: Data Processing Optimization Status: In Progress
|
Currently, for development I am using a 140MB pre-trained by Acephai. [see here](https://alphacephei.com/vosk/models/vosk-model-en-us-0.22-lgraph.zip)
This model takes 1.4 seconds to load, but offers a processing speed of roughly 6 seconds for simple sentences (see image below).
The alternative model (intended for use in deployment) is a 2.9GB model also provided by Acephai [see here](https://alphacephei.com/vosk/models/vosk-model-en-us-0.22.zip)
This model takes 10.8 seconds to load, but offers a lower processing speed of 605ms for the same sentence and boasts more accuracy with increasingly complex phrases.
A note to keep in mind when developing VAD would be to make sure this model gets loaded into the thread once, and utilized for several iterations to ensure that the system is responsive.
|
1.0
|
Model Processing Speed - Currently, for development I am using a 140MB pre-trained by Acephai. [see here](https://alphacephei.com/vosk/models/vosk-model-en-us-0.22-lgraph.zip)
This model takes 1.4 seconds to load, but offers a processing speed of roughly 6 seconds for simple sentences (see image below).
The alternative model (intended for use in deployment) is a 2.9GB model also provided by Acephai [see here](https://alphacephei.com/vosk/models/vosk-model-en-us-0.22.zip)
This model takes 10.8 seconds to load, but offers a lower processing speed of 605ms for the same sentence and boasts more accuracy with increasingly complex phrases.
A note to keep in mind when developing VAD would be to make sure this model gets loaded into the thread once, and utilized for several iterations to ensure that the system is responsive.
|
process
|
model processing speed currently for development i am using a pre trained by acephai this model takes seconds to load but offers a processing speed of roughly seconds for simple sentences see image below the alternative model intended for use in deployment is a model also provided by acephai this model takes seconds to load but offers a lower processing speed of for the same sentence and boasts more accuracy with increasingly complex phrases a note to keep in mind when developing vad would be to make sure this model gets loaded into the thread once and utilized for several iterations to ensure that the system is responsive
| 1
|
9,855
| 12,854,946,002
|
IssuesEvent
|
2020-07-09 03:34:32
|
cypress-io/cypress
|
https://api.github.com/repos/cypress-io/cypress
|
closed
|
Cypress 4.2.0 10 low vulnerabilities concerning upgrade to minimist 1.2.3
|
process: dependencies stage: work in progress
|
### Current behavior:
Upgrading to cypress 4.2.1 by using `npm install --save-dev cypress@4.2.0` installs correctly but shows the following error:
```
found 10 low severity vulnerabilities
run `npm audit fix` to fix them, or `npm audit` for details
```
Running `npm audit fix` takes no action even when using the force flag. Looking at npm audit I see that there are sub dependencies for other libraries and a link to this issue: https://www.npmjs.com/advisories/1179
```
> === npm audit security report ===
┌──────────────────────────────────────────────────────────────────────────────┐
│ Manual Review │
│ Some vulnerabilities require your attention to resolve │
│ │
│ Visit https://go.npm.me/audit-guide for additional guidance │
└──────────────────────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Low │ Prototype Pollution │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=0.2.1 <1.0.0 || >=1.2.3 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ http-server │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ http-server > optimist > minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://npmjs.com/advisories/1179 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Low │ Prototype Pollution │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=0.2.1 <1.0.0 || >=1.2.3 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ http-server │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ http-server > portfinder > mkdirp > minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://npmjs.com/advisories/1179 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Low │ Prototype Pollution │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=0.2.1 <1.0.0 || >=1.2.3 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ wd │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ wd > mkdirp > minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://npmjs.com/advisories/1179 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Low │ Prototype Pollution │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=0.2.1 <1.0.0 || >=1.2.3 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ cypress [dev] │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ cypress > extract-zip > mkdirp > minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://npmjs.com/advisories/1179 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Low │ Prototype Pollution │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=0.2.1 <1.0.0 || >=1.2.3 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ mocha [dev] │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ mocha > mkdirp > minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://npmjs.com/advisories/1179 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Low │ Prototype Pollution │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=0.2.1 <1.0.0 || >=1.2.3 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ npm │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ npm > libnpx > update-notifier > latest-version > │
│ │ package-json > registry-auth-token > rc > minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://npmjs.com/advisories/1179 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Low │ Prototype Pollution │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=0.2.1 <1.0.0 || >=1.2.3 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ npm │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ npm > update-notifier > latest-version > package-json > │
│ │ registry-auth-token > rc > minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://npmjs.com/advisories/1179 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Low │ Prototype Pollution │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=0.2.1 <1.0.0 || >=1.2.3 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ npm │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ npm > libnpx > update-notifier > latest-version > │
│ │ package-json > registry-url > rc > minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://npmjs.com/advisories/1179 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Low │ Prototype Pollution │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=0.2.1 <1.0.0 || >=1.2.3 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ npm │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ npm > update-notifier > latest-version > package-json > │
│ │ registry-url > rc > minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://npmjs.com/advisories/1179 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Low │ Prototype Pollution │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=0.2.1 <1.0.0 || >=1.2.3 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ cypress [dev] │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ cypress > minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://npmjs.com/advisories/1179 │
└───────────────┴──────────────────────────────────────────────────────────────┘
found 10 low severity vulnerabilities in 12869 scanned packages
10 vulnerabilities require manual review. See the full report for details.
>
```
### Desired behavior:
The desired behavior is that npm updates to cypress@4.2.0 will not have the current vulnerabilities.
### Versions
Mac OS 10.15.3 / npm v 6.13.4 / v10.19.0
|
1.0
|
Cypress 4.2.0 10 low vulnerabilities concerning upgrade to minimist 1.2.3 - ### Current behavior:
Upgrading to cypress 4.2.1 by using `npm install --save-dev cypress@4.2.0` installs correctly but shows the following error:
```
found 10 low severity vulnerabilities
run `npm audit fix` to fix them, or `npm audit` for details
```
Running `npm audit fix` takes no action even when using the force flag. Looking at npm audit I see that there are sub dependencies for other libraries and a link to this issue: https://www.npmjs.com/advisories/1179
```
> === npm audit security report ===
┌──────────────────────────────────────────────────────────────────────────────┐
│ Manual Review │
│ Some vulnerabilities require your attention to resolve │
│ │
│ Visit https://go.npm.me/audit-guide for additional guidance │
└──────────────────────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Low │ Prototype Pollution │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=0.2.1 <1.0.0 || >=1.2.3 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ http-server │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ http-server > optimist > minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://npmjs.com/advisories/1179 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Low │ Prototype Pollution │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=0.2.1 <1.0.0 || >=1.2.3 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ http-server │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ http-server > portfinder > mkdirp > minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://npmjs.com/advisories/1179 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Low │ Prototype Pollution │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=0.2.1 <1.0.0 || >=1.2.3 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ wd │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ wd > mkdirp > minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://npmjs.com/advisories/1179 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Low │ Prototype Pollution │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=0.2.1 <1.0.0 || >=1.2.3 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ cypress [dev] │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ cypress > extract-zip > mkdirp > minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://npmjs.com/advisories/1179 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Low │ Prototype Pollution │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=0.2.1 <1.0.0 || >=1.2.3 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ mocha [dev] │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ mocha > mkdirp > minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://npmjs.com/advisories/1179 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Low │ Prototype Pollution │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=0.2.1 <1.0.0 || >=1.2.3 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ npm │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ npm > libnpx > update-notifier > latest-version > │
│ │ package-json > registry-auth-token > rc > minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://npmjs.com/advisories/1179 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Low │ Prototype Pollution │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=0.2.1 <1.0.0 || >=1.2.3 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ npm │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ npm > update-notifier > latest-version > package-json > │
│ │ registry-auth-token > rc > minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://npmjs.com/advisories/1179 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Low │ Prototype Pollution │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=0.2.1 <1.0.0 || >=1.2.3 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ npm │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ npm > libnpx > update-notifier > latest-version > │
│ │ package-json > registry-url > rc > minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://npmjs.com/advisories/1179 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Low │ Prototype Pollution │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=0.2.1 <1.0.0 || >=1.2.3 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ npm │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ npm > update-notifier > latest-version > package-json > │
│ │ registry-url > rc > minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://npmjs.com/advisories/1179 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Low │ Prototype Pollution │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=0.2.1 <1.0.0 || >=1.2.3 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ cypress [dev] │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ cypress > minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://npmjs.com/advisories/1179 │
└───────────────┴──────────────────────────────────────────────────────────────┘
found 10 low severity vulnerabilities in 12869 scanned packages
10 vulnerabilities require manual review. See the full report for details.
>
```
### Desired behavior:
The desired behavior is that npm updates to cypress@4.2.0 will not have the current vulnerabilities.
### Versions
Mac OS 10.15.3 / npm v 6.13.4 / v10.19.0
|
process
|
cypress low vulnerabilities concerning upgrade to minimist current behavior upgrading to cypress by using npm install save dev cypress installs correctly but shows the following error found low severity vulnerabilities run npm audit fix to fix them or npm audit for details running npm audit fix takes no action even when using the force flag looking at npm audit i see that there are sub dependencies for other libraries and a link to this issue npm audit security report ┌──────────────────────────────────────────────────────────────────────────────┐ │ manual review │ │ some vulnerabilities require your attention to resolve │ │ │ │ visit for additional guidance │ └──────────────────────────────────────────────────────────────────────────────┘ ┌───────────────┬──────────────────────────────────────────────────────────────┐ │ low │ prototype pollution │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ package │ minimist │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ patched in │ │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ dependency of │ http server │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ path │ http server optimist minimist │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ more info │ │ └───────────────┴──────────────────────────────────────────────────────────────┘ ┌───────────────┬──────────────────────────────────────────────────────────────┐ │ low │ prototype pollution │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ package │ minimist │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ patched in │ │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ dependency of │ http server │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ path │ http server portfinder mkdirp minimist │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ more info │ │ └───────────────┴──────────────────────────────────────────────────────────────┘ ┌───────────────┬──────────────────────────────────────────────────────────────┐ │ low │ prototype pollution │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ package │ minimist │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ patched in │ │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ dependency of │ wd │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ path │ wd mkdirp minimist │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ more info │ │ └───────────────┴──────────────────────────────────────────────────────────────┘ ┌───────────────┬──────────────────────────────────────────────────────────────┐ │ low │ prototype pollution │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ package │ minimist │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ patched in │ │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ dependency of │ cypress │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ path │ cypress extract zip mkdirp minimist │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ more info │ │ └───────────────┴──────────────────────────────────────────────────────────────┘ ┌───────────────┬──────────────────────────────────────────────────────────────┐ │ low │ prototype pollution │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ package │ minimist │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ patched in │ │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ dependency of │ mocha │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ path │ mocha mkdirp minimist │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ more info │ │ └───────────────┴──────────────────────────────────────────────────────────────┘ ┌───────────────┬──────────────────────────────────────────────────────────────┐ │ low │ prototype pollution │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ package │ minimist │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ patched in │ │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ dependency of │ npm │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ path │ npm libnpx update notifier latest version │ │ │ package json registry auth token rc minimist │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ more info │ │ └───────────────┴──────────────────────────────────────────────────────────────┘ ┌───────────────┬──────────────────────────────────────────────────────────────┐ │ low │ prototype pollution │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ package │ minimist │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ patched in │ │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ dependency of │ npm │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ path │ npm update notifier latest version package json │ │ │ registry auth token rc minimist │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ more info │ │ └───────────────┴──────────────────────────────────────────────────────────────┘ ┌───────────────┬──────────────────────────────────────────────────────────────┐ │ low │ prototype pollution │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ package │ minimist │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ patched in │ │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ dependency of │ npm │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ path │ npm libnpx update notifier latest version │ │ │ package json registry url rc minimist │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ more info │ │ └───────────────┴──────────────────────────────────────────────────────────────┘ ┌───────────────┬──────────────────────────────────────────────────────────────┐ │ low │ prototype pollution │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ package │ minimist │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ patched in │ │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ dependency of │ npm │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ path │ npm update notifier latest version package json │ │ │ registry url rc minimist │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ more info │ │ └───────────────┴──────────────────────────────────────────────────────────────┘ ┌───────────────┬──────────────────────────────────────────────────────────────┐ │ low │ prototype pollution │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ package │ minimist │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ patched in │ │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ dependency of │ cypress │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ path │ cypress minimist │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ more info │ │ └───────────────┴──────────────────────────────────────────────────────────────┘ found low severity vulnerabilities in scanned packages vulnerabilities require manual review see the full report for details desired behavior the desired behavior is that npm updates to cypress will not have the current vulnerabilities versions mac os npm v
| 1
|
49,241
| 26,046,781,256
|
IssuesEvent
|
2022-12-22 15:02:10
|
AzureAD/microsoft-authentication-library-for-dotnet
|
https://api.github.com/repos/AzureAD/microsoft-authentication-library-for-dotnet
|
closed
|
[Investigate] Investigate performance of broker authentication scenarios and Identify areas for improvment
|
bug P2 blocked scenario:Mobile-iOS scenario:Mobile-Android In Progress performance internal
|
**Which Version of MSAL are you using ?**
Latest
**Platform**
xamarin android, xamarin iOS
**What authentication flow has the issue?**
all brokered authentication flows
We need to investigate the performance of the authentication scenarios on Android and iOS to determine how long each section of the authentication flow takes. We can use this data to look for areas of opportunity to improve performance for the scenarios.
We should also compare the performance of ADAL and MSAL to get a baseline of how MSAL compares to ADAL today.
|
True
|
[Investigate] Investigate performance of broker authentication scenarios and Identify areas for improvment - **Which Version of MSAL are you using ?**
Latest
**Platform**
xamarin android, xamarin iOS
**What authentication flow has the issue?**
all brokered authentication flows
We need to investigate the performance of the authentication scenarios on Android and iOS to determine how long each section of the authentication flow takes. We can use this data to look for areas of opportunity to improve performance for the scenarios.
We should also compare the performance of ADAL and MSAL to get a baseline of how MSAL compares to ADAL today.
|
non_process
|
investigate performance of broker authentication scenarios and identify areas for improvment which version of msal are you using latest platform xamarin android xamarin ios what authentication flow has the issue all brokered authentication flows we need to investigate the performance of the authentication scenarios on android and ios to determine how long each section of the authentication flow takes we can use this data to look for areas of opportunity to improve performance for the scenarios we should also compare the performance of adal and msal to get a baseline of how msal compares to adal today
| 0
|
144,996
| 19,318,950,142
|
IssuesEvent
|
2021-12-14 01:42:50
|
txh51591/tm-repo
|
https://api.github.com/repos/txh51591/tm-repo
|
opened
|
CVE-2020-14195 (High) detected in jackson-databind-2.9.9.jar
|
security vulnerability
|
## CVE-2020-14195 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.9.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: tm-repo/pom.xml</p>
<p>Path to vulnerable library: m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.9/jackson-databind-2.9.9.jar</p>
<p>
Dependency Hierarchy:
- :x: **jackson-databind-2.9.9.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
FasterXML jackson-databind 2.x before 2.9.10.5 mishandles the interaction between serialization gadgets and typing, related to org.jsecurity.realm.jndi.JndiRealmFactory (aka org.jsecurity).
<p>Publish Date: 2020-06-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-14195>CVE-2020-14195</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14195">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14195</a></p>
<p>Release Date: 2020-06-16</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.9.10.5</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-14195 (High) detected in jackson-databind-2.9.9.jar - ## CVE-2020-14195 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.9.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: tm-repo/pom.xml</p>
<p>Path to vulnerable library: m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.9/jackson-databind-2.9.9.jar</p>
<p>
Dependency Hierarchy:
- :x: **jackson-databind-2.9.9.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
FasterXML jackson-databind 2.x before 2.9.10.5 mishandles the interaction between serialization gadgets and typing, related to org.jsecurity.realm.jndi.JndiRealmFactory (aka org.jsecurity).
<p>Publish Date: 2020-06-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-14195>CVE-2020-14195</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14195">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14195</a></p>
<p>Release Date: 2020-06-16</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.9.10.5</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 jackson databind jar cve high severity vulnerability vulnerable library jackson databind jar general data binding functionality for jackson works on core streaming api library home page a href path to dependency file tm repo pom xml path to vulnerable library repository com fasterxml jackson core jackson databind jackson databind jar dependency hierarchy x jackson databind jar vulnerable library found in base branch master vulnerability details fasterxml jackson databind x before mishandles the interaction between serialization gadgets and typing related to org jsecurity realm jndi jndirealmfactory aka org jsecurity publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution com fasterxml jackson core jackson databind step up your open source security game with whitesource
| 0
|
2,122
| 4,959,368,164
|
IssuesEvent
|
2016-12-02 13:11:11
|
qgis/QGIS-Documentation
|
https://api.github.com/repos/qgis/QGIS-Documentation
|
closed
|
Reorganize the LAStools algorithms documentation
|
Processing
|
In http://docs.qgis.org/2.14/en/docs/user_manual/processing_algs/index.html, we have
1. Is there any reason to have the last item `LAStools` being a collection of different algorithms (while the first ones are single tool)?
2. Should the tools under the `LAStools` item be moved to the same level than the others, namely under `LAStools algorithm provider`
3. Each of the first algorithms has its own page e.g, [blast2dem](http://docs.qgis.org/2.14/en/docs/user_manual/processing_algs/lidartools/blast2dem.html) while generally, afaik, algs are grouped eg, [Vector Analysis](http://docs.qgis.org/testing/en/docs/user_manual/processing_algs/qgis/vector_analysis_tools.html). Should they all be moved under the single page `LAStools algorithm provider` or sub-grouped (in which case, any idea of categories is welcome)?
Thanks
@alexbruy @volaya
|
1.0
|
Reorganize the LAStools algorithms documentation - In http://docs.qgis.org/2.14/en/docs/user_manual/processing_algs/index.html, we have
1. Is there any reason to have the last item `LAStools` being a collection of different algorithms (while the first ones are single tool)?
2. Should the tools under the `LAStools` item be moved to the same level than the others, namely under `LAStools algorithm provider`
3. Each of the first algorithms has its own page e.g, [blast2dem](http://docs.qgis.org/2.14/en/docs/user_manual/processing_algs/lidartools/blast2dem.html) while generally, afaik, algs are grouped eg, [Vector Analysis](http://docs.qgis.org/testing/en/docs/user_manual/processing_algs/qgis/vector_analysis_tools.html). Should they all be moved under the single page `LAStools algorithm provider` or sub-grouped (in which case, any idea of categories is welcome)?
Thanks
@alexbruy @volaya
|
process
|
reorganize the lastools algorithms documentation in we have is there any reason to have the last item lastools being a collection of different algorithms while the first ones are single tool should the tools under the lastools item be moved to the same level than the others namely under lastools algorithm provider each of the first algorithms has its own page e g while generally afaik algs are grouped eg should they all be moved under the single page lastools algorithm provider or sub grouped in which case any idea of categories is welcome thanks alexbruy volaya
| 1
|
215,172
| 7,292,408,593
|
IssuesEvent
|
2018-02-25 00:36:37
|
SpongePowered/Ore
|
https://api.github.com/repos/SpongePowered/Ore
|
closed
|
Delete button should not hard delete.
|
high priority
|
Project delete button should merely flip the project to the staff-only hidden state. See #413
File delete button should do the same sort of thing.
Admins (not moderators) should have a way to hard delete things as necessary for legal reasons but otherwise this shouldn't be doable.
|
1.0
|
Delete button should not hard delete. - Project delete button should merely flip the project to the staff-only hidden state. See #413
File delete button should do the same sort of thing.
Admins (not moderators) should have a way to hard delete things as necessary for legal reasons but otherwise this shouldn't be doable.
|
non_process
|
delete button should not hard delete project delete button should merely flip the project to the staff only hidden state see file delete button should do the same sort of thing admins not moderators should have a way to hard delete things as necessary for legal reasons but otherwise this shouldn t be doable
| 0
|
10,534
| 7,214,100,082
|
IssuesEvent
|
2018-02-08 00:24:52
|
tensorflow/models
|
https://api.github.com/repos/tensorflow/models
|
closed
|
Issue during debug of tensorflow
|
stat:awaiting tensorflower type:bug/performance
|
Hello,
I'm pretty new to tensorflow and python. If I try to run syntaxnet by command line it works well, but I have an issue when I try to debug it step by step with Eclipse or Spyder. I had same error: an issue on load a library (parser_ops.so). Someone should help me to understand what is the issue?
I attach here the error log (generated by Spyder)
File "<ipython-input-2-c92123615836>", line 1, in <module>
debugfile('/home/erber/models/syntaxnet/bazel-bin/syntaxnet/parser_eval.runfiles/__main__/syntaxnet/parser_eval.py', wdir='/home/erber/models/syntaxnet/bazel-bin/syntaxnet/parser_eval.runfiles/__main__/syntaxnet')
File "/usr/lib/python2.7/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py", line 719, in debugfile
debugger.run("runfile(%r, args=%r, wdir=%r)" % (filename, args, wdir))
File "/usr/lib/python2.7/bdb.py", line 400, in run
exec cmd in globals, locals
File "<string>", line 1, in <module>
File "/usr/lib/python2.7/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py", line 699, in runfile
execfile(filename, namespace)
File "/usr/lib/python2.7/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py", line 81, in execfile
builtins.execfile(filename, *where)
File "/home/erber/models/syntaxnet/bazel-bin/syntaxnet/parser_eval.runfiles/__main__/syntaxnet/parser_eval.py", line 31, in <module>
import graph_builder
File "graph_builder.py", line 22, in <module>
import load_parser_ops
File "load_parser_ops.py", line 25, in <module>
'parser_ops.so'))
File "/home/erber/.local/lib/python2.7/site-packages/tensorflow/python/framework/load_library.py", line 64, in load_op_library
None, None, error_msg, error_code)
NotFoundError: parser_ops.so: cannot open shared object file: No such file or directory
thank you very much for any help!
|
True
|
Issue during debug of tensorflow -
Hello,
I'm pretty new to tensorflow and python. If I try to run syntaxnet by command line it works well, but I have an issue when I try to debug it step by step with Eclipse or Spyder. I had same error: an issue on load a library (parser_ops.so). Someone should help me to understand what is the issue?
I attach here the error log (generated by Spyder)
File "<ipython-input-2-c92123615836>", line 1, in <module>
debugfile('/home/erber/models/syntaxnet/bazel-bin/syntaxnet/parser_eval.runfiles/__main__/syntaxnet/parser_eval.py', wdir='/home/erber/models/syntaxnet/bazel-bin/syntaxnet/parser_eval.runfiles/__main__/syntaxnet')
File "/usr/lib/python2.7/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py", line 719, in debugfile
debugger.run("runfile(%r, args=%r, wdir=%r)" % (filename, args, wdir))
File "/usr/lib/python2.7/bdb.py", line 400, in run
exec cmd in globals, locals
File "<string>", line 1, in <module>
File "/usr/lib/python2.7/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py", line 699, in runfile
execfile(filename, namespace)
File "/usr/lib/python2.7/dist-packages/spyderlib/widgets/externalshell/sitecustomize.py", line 81, in execfile
builtins.execfile(filename, *where)
File "/home/erber/models/syntaxnet/bazel-bin/syntaxnet/parser_eval.runfiles/__main__/syntaxnet/parser_eval.py", line 31, in <module>
import graph_builder
File "graph_builder.py", line 22, in <module>
import load_parser_ops
File "load_parser_ops.py", line 25, in <module>
'parser_ops.so'))
File "/home/erber/.local/lib/python2.7/site-packages/tensorflow/python/framework/load_library.py", line 64, in load_op_library
None, None, error_msg, error_code)
NotFoundError: parser_ops.so: cannot open shared object file: No such file or directory
thank you very much for any help!
|
non_process
|
issue during debug of tensorflow hello i m pretty new to tensorflow and python if i try to run syntaxnet by command line it works well but i have an issue when i try to debug it step by step with eclipse or spyder i had same error an issue on load a library parser ops so someone should help me to understand what is the issue i attach here the error log generated by spyder file line in debugfile home erber models syntaxnet bazel bin syntaxnet parser eval runfiles main syntaxnet parser eval py wdir home erber models syntaxnet bazel bin syntaxnet parser eval runfiles main syntaxnet file usr lib dist packages spyderlib widgets externalshell sitecustomize py line in debugfile debugger run runfile r args r wdir r filename args wdir file usr lib bdb py line in run exec cmd in globals locals file line in file usr lib dist packages spyderlib widgets externalshell sitecustomize py line in runfile execfile filename namespace file usr lib dist packages spyderlib widgets externalshell sitecustomize py line in execfile builtins execfile filename where file home erber models syntaxnet bazel bin syntaxnet parser eval runfiles main syntaxnet parser eval py line in import graph builder file graph builder py line in import load parser ops file load parser ops py line in parser ops so file home erber local lib site packages tensorflow python framework load library py line in load op library none none error msg error code notfounderror parser ops so cannot open shared object file no such file or directory thank you very much for any help
| 0
|
18,808
| 24,707,466,828
|
IssuesEvent
|
2022-10-19 20:24:55
|
Altinn/altinn-studio
|
https://api.github.com/repos/Altinn/altinn-studio
|
closed
|
Case: Support for OKI in Altinn 3
|
area/process Epic org/ssb org/brg
|
Create an Altinn 3 application that will replace todays OKI in Altinn 2
|
1.0
|
Case: Support for OKI in Altinn 3 - Create an Altinn 3 application that will replace todays OKI in Altinn 2
|
process
|
case support for oki in altinn create an altinn application that will replace todays oki in altinn
| 1
|
14,181
| 3,385,435,488
|
IssuesEvent
|
2015-11-27 11:29:33
|
e-government-ua/i
|
https://api.github.com/repos/e-government-ua/i
|
closed
|
На бэке реализовать авто-подмену в полях с типом markers - значение из файлов из /bpmn/markers/motion/
|
active test _activiti _wf-base
|
Пример содержимого поля(в атрибуте value):
[/bpmn/markers/motion/standart.json]
вместо него должно оказаться его содержимое.
Причем этот контент должен подставляться даже на этапе стартовой формы, чтоб уже на стартовую форму пришел замененный контент.
|
1.0
|
На бэке реализовать авто-подмену в полях с типом markers - значение из файлов из /bpmn/markers/motion/ - Пример содержимого поля(в атрибуте value):
[/bpmn/markers/motion/standart.json]
вместо него должно оказаться его содержимое.
Причем этот контент должен подставляться даже на этапе стартовой формы, чтоб уже на стартовую форму пришел замененный контент.
|
non_process
|
на бэке реализовать авто подмену в полях с типом markers значение из файлов из bpmn markers motion пример содержимого поля в атрибуте value вместо него должно оказаться его содержимое причем этот контент должен подставляться даже на этапе стартовой формы чтоб уже на стартовую форму пришел замененный контент
| 0
|
551,296
| 16,165,908,783
|
IssuesEvent
|
2021-05-01 13:43:54
|
DIT112-V21/group-16
|
https://api.github.com/repos/DIT112-V21/group-16
|
opened
|
Basic Cleaning pattern
|
Medium priority Sprint 3 User story enhancement
|
**Description**
as a Cleaning supervisor i want to be able to set the car to a cleaning pattern so that it works effectively without me having to control it
**Acceptance criteria**
1. The vehicle will move in a basic pattern turning atleast 3 times
2. The vehicle will implement obstacle avoidance while doing the cleanig pattern
|
1.0
|
Basic Cleaning pattern - **Description**
as a Cleaning supervisor i want to be able to set the car to a cleaning pattern so that it works effectively without me having to control it
**Acceptance criteria**
1. The vehicle will move in a basic pattern turning atleast 3 times
2. The vehicle will implement obstacle avoidance while doing the cleanig pattern
|
non_process
|
basic cleaning pattern description as a cleaning supervisor i want to be able to set the car to a cleaning pattern so that it works effectively without me having to control it acceptance criteria the vehicle will move in a basic pattern turning atleast times the vehicle will implement obstacle avoidance while doing the cleanig pattern
| 0
|
146,962
| 19,476,092,623
|
IssuesEvent
|
2021-12-24 12:39:03
|
sewace/PhaseShift
|
https://api.github.com/repos/sewace/PhaseShift
|
opened
|
CVE-2021-32803 (High) detected in tar-4.4.8.tgz
|
security vulnerability
|
## CVE-2021-32803 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tar-4.4.8.tgz</b></p></summary>
<p>tar for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-4.4.8.tgz">https://registry.npmjs.org/tar/-/tar-4.4.8.tgz</a></p>
<p>
Dependency Hierarchy:
- react-native-paper-2.16.0.tgz (Root Library)
- react-theme-provider-1.0.7.tgz
- flow-copy-source-1.3.0.tgz
- chokidar-2.1.6.tgz
- fsevents-1.2.9.tgz
- node-pre-gyp-0.12.0.tgz
- :x: **tar-4.4.8.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sewace/PhaseShift/commit/4fed7911a2622b8cefac707597cba1816054a701">4fed7911a2622b8cefac707597cba1816054a701</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The npm package "tar" (aka node-tar) before versions 6.1.2, 5.0.7, 4.4.15, and 3.2.3 has an arbitrary File Creation/Overwrite vulnerability via insufficient symlink protection. `node-tar` aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary `stat` calls to determine whether a given path is a directory, paths are cached when directories are created. This logic was insufficient when extracting tar files that contained both a directory and a symlink with the same name as the directory. This order of operations resulted in the directory being created and added to the `node-tar` directory cache. When a directory is present in the directory cache, subsequent calls to mkdir for that directory are skipped. However, this is also where `node-tar` checks for symlinks occur. By first creating a directory, and then replacing that directory with a symlink, it was thus possible to bypass `node-tar` symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.3, 4.4.15, 5.0.7 and 6.1.2.
<p>Publish Date: 2021-08-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-32803>CVE-2021-32803</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</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/npm/node-tar/security/advisories/GHSA-r628-mhmh-qjhw">https://github.com/npm/node-tar/security/advisories/GHSA-r628-mhmh-qjhw</a></p>
<p>Release Date: 2021-08-03</p>
<p>Fix Resolution: tar - 3.2.3, 4.4.15, 5.0.7, 6.1.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2021-32803 (High) detected in tar-4.4.8.tgz - ## CVE-2021-32803 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tar-4.4.8.tgz</b></p></summary>
<p>tar for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-4.4.8.tgz">https://registry.npmjs.org/tar/-/tar-4.4.8.tgz</a></p>
<p>
Dependency Hierarchy:
- react-native-paper-2.16.0.tgz (Root Library)
- react-theme-provider-1.0.7.tgz
- flow-copy-source-1.3.0.tgz
- chokidar-2.1.6.tgz
- fsevents-1.2.9.tgz
- node-pre-gyp-0.12.0.tgz
- :x: **tar-4.4.8.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sewace/PhaseShift/commit/4fed7911a2622b8cefac707597cba1816054a701">4fed7911a2622b8cefac707597cba1816054a701</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The npm package "tar" (aka node-tar) before versions 6.1.2, 5.0.7, 4.4.15, and 3.2.3 has an arbitrary File Creation/Overwrite vulnerability via insufficient symlink protection. `node-tar` aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary `stat` calls to determine whether a given path is a directory, paths are cached when directories are created. This logic was insufficient when extracting tar files that contained both a directory and a symlink with the same name as the directory. This order of operations resulted in the directory being created and added to the `node-tar` directory cache. When a directory is present in the directory cache, subsequent calls to mkdir for that directory are skipped. However, this is also where `node-tar` checks for symlinks occur. By first creating a directory, and then replacing that directory with a symlink, it was thus possible to bypass `node-tar` symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.3, 4.4.15, 5.0.7 and 6.1.2.
<p>Publish Date: 2021-08-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-32803>CVE-2021-32803</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</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/npm/node-tar/security/advisories/GHSA-r628-mhmh-qjhw">https://github.com/npm/node-tar/security/advisories/GHSA-r628-mhmh-qjhw</a></p>
<p>Release Date: 2021-08-03</p>
<p>Fix Resolution: tar - 3.2.3, 4.4.15, 5.0.7, 6.1.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_process
|
cve high detected in tar tgz cve high severity vulnerability vulnerable library tar tgz tar for node library home page a href dependency hierarchy react native paper tgz root library react theme provider tgz flow copy source tgz chokidar tgz fsevents tgz node pre gyp tgz x tar tgz vulnerable library found in head commit a href found in base branch master vulnerability details the npm package tar aka node tar before versions and has an arbitrary file creation overwrite vulnerability via insufficient symlink protection node tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted this is in part achieved by ensuring that extracted directories are not symlinks additionally in order to prevent unnecessary stat calls to determine whether a given path is a directory paths are cached when directories are created this logic was insufficient when extracting tar files that contained both a directory and a symlink with the same name as the directory this order of operations resulted in the directory being created and added to the node tar directory cache when a directory is present in the directory cache subsequent calls to mkdir for that directory are skipped however this is also where node tar checks for symlinks occur by first creating a directory and then replacing that directory with a symlink it was thus possible to bypass node tar symlink checks on directories essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location thus allowing arbitrary file creation and overwrite this issue was addressed in releases and publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution tar step up your open source security game with whitesource
| 0
|
21,165
| 28,139,581,398
|
IssuesEvent
|
2023-04-01 19:50:34
|
cse442-at-ub/project_s23-cinco
|
https://api.github.com/repos/cse442-at-ub/project_s23-cinco
|
opened
|
delete token client side and revoke server side upon signout
|
Processing Task Sprint 3
|
**Task Tests*
1.
-go to website url: https://www-student.cse.buffalo.edu/CSE442-542/2023-Spring/cse-442b/build/
-sign up with a new account
-log in to the newly created account
-open the developer tools
-go to application
-go to cookies
-look for session and it's token
2.
-while signed in, click the sign out button
-follow previous steps to look for sessions
-ensure the session token is now empty ""
3.
-go to myphp admin database at: https://www-student.cse.buffalo.edu/tools/db/phpmyadmin/sql.php?server=1&db=cse442_2023_spring_team_b_db&table=Sessions&pos=0
-navigate to the sessions table and ensure that same token is not within the table
|
1.0
|
delete token client side and revoke server side upon signout - **Task Tests*
1.
-go to website url: https://www-student.cse.buffalo.edu/CSE442-542/2023-Spring/cse-442b/build/
-sign up with a new account
-log in to the newly created account
-open the developer tools
-go to application
-go to cookies
-look for session and it's token
2.
-while signed in, click the sign out button
-follow previous steps to look for sessions
-ensure the session token is now empty ""
3.
-go to myphp admin database at: https://www-student.cse.buffalo.edu/tools/db/phpmyadmin/sql.php?server=1&db=cse442_2023_spring_team_b_db&table=Sessions&pos=0
-navigate to the sessions table and ensure that same token is not within the table
|
process
|
delete token client side and revoke server side upon signout task tests go to website url sign up with a new account log in to the newly created account open the developer tools go to application go to cookies look for session and it s token while signed in click the sign out button follow previous steps to look for sessions ensure the session token is now empty go to myphp admin database at navigate to the sessions table and ensure that same token is not within the table
| 1
|
21,460
| 29,498,383,616
|
IssuesEvent
|
2023-06-02 19:07:37
|
metabase/metabase
|
https://api.github.com/repos/metabase/metabase
|
closed
|
[MLv2] [Bug] Query fails when aggregating by an aggregated custom column
|
Querying/GUI .metabase-lib .Team/QueryProcessor :hammer_and_wrench:
|
Query fails with `Column "..." not found` when trying to aggregate an aggregated custom column. My guess is the field reference in MLv2 is off at the moment.
For example, let's say we have a query:
* started from the sample Products table
* having a custom column called "Half Price" (definition: `[Price] / 2`)
* aggregation: average of Half Price
* breakout: by product's "Created At" (month) column
<details>
<summary>Query JSON representation</summary>
```json
{
"source-table": 1,
"expressions": {
"Half Price": [ "field", 2, null ]
},
"aggregation": [
[ "avg", [ "expression", "Half Price" ] ]
],
"breakout": [
[ "field", 7, { "base-type": "type/DateTime", "temporal-unit": "month" } ]
]
}
```
</details>
Now if we try to add another aggregation for "Average of Half Price", MLv2 generates an aggregation clause like:
```js
[ "max", [ "field", "avg_Half Price", { "base-type": "type/Float" } ] ]
```
OTOH, MLv1 produces the following reference:
```js
[ "max", [ "field", "avg", { "base-type": "type/Float" } ] ]
```
|
1.0
|
[MLv2] [Bug] Query fails when aggregating by an aggregated custom column - Query fails with `Column "..." not found` when trying to aggregate an aggregated custom column. My guess is the field reference in MLv2 is off at the moment.
For example, let's say we have a query:
* started from the sample Products table
* having a custom column called "Half Price" (definition: `[Price] / 2`)
* aggregation: average of Half Price
* breakout: by product's "Created At" (month) column
<details>
<summary>Query JSON representation</summary>
```json
{
"source-table": 1,
"expressions": {
"Half Price": [ "field", 2, null ]
},
"aggregation": [
[ "avg", [ "expression", "Half Price" ] ]
],
"breakout": [
[ "field", 7, { "base-type": "type/DateTime", "temporal-unit": "month" } ]
]
}
```
</details>
Now if we try to add another aggregation for "Average of Half Price", MLv2 generates an aggregation clause like:
```js
[ "max", [ "field", "avg_Half Price", { "base-type": "type/Float" } ] ]
```
OTOH, MLv1 produces the following reference:
```js
[ "max", [ "field", "avg", { "base-type": "type/Float" } ] ]
```
|
process
|
query fails when aggregating by an aggregated custom column query fails with column not found when trying to aggregate an aggregated custom column my guess is the field reference in is off at the moment for example let s say we have a query started from the sample products table having a custom column called half price definition aggregation average of half price breakout by product s created at month column query json representation json source table expressions half price aggregation breakout now if we try to add another aggregation for average of half price generates an aggregation clause like js otoh produces the following reference js
| 1
|
186,478
| 6,736,521,926
|
IssuesEvent
|
2017-10-19 04:43:29
|
webcompat/web-bugs
|
https://api.github.com/repos/webcompat/web-bugs
|
closed
|
www.audible.com - video or audio doesn't play
|
browser-firefox priority-normal status-needstriage type-stylo
|
<!-- @browser: Firefox 58.0 -->
<!-- @ua_header: Mozilla/5.0 (X11; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0 -->
<!-- @reported_with: desktop-reporter -->
**URL**: http://www.audible.com/cloud-player?ref_=a_lib_cp_1&asin=B002V8MMPU
**Browser / Version**: Firefox 58.0
**Operating System**: Linux
**Tested Another Browser**: Yes
**Problem type**: Video or audio doesn't play
**Description**: audio does not play
**Steps to Reproduce**:
layout.css.servo.enabled: true
subscription
[](https://webcompat.com/uploads/2017/10/5ef93f4c-d027-4391-a6e0-55d8db671a10.jpg)
_From [webcompat.com](https://webcompat.com/) with ❤️_
|
1.0
|
www.audible.com - video or audio doesn't play - <!-- @browser: Firefox 58.0 -->
<!-- @ua_header: Mozilla/5.0 (X11; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0 -->
<!-- @reported_with: desktop-reporter -->
**URL**: http://www.audible.com/cloud-player?ref_=a_lib_cp_1&asin=B002V8MMPU
**Browser / Version**: Firefox 58.0
**Operating System**: Linux
**Tested Another Browser**: Yes
**Problem type**: Video or audio doesn't play
**Description**: audio does not play
**Steps to Reproduce**:
layout.css.servo.enabled: true
subscription
[](https://webcompat.com/uploads/2017/10/5ef93f4c-d027-4391-a6e0-55d8db671a10.jpg)
_From [webcompat.com](https://webcompat.com/) with ❤️_
|
non_process
|
video or audio doesn t play url browser version firefox operating system linux tested another browser yes problem type video or audio doesn t play description audio does not play steps to reproduce layout css servo enabled true subscription from with ❤️
| 0
|
10,721
| 3,420,420,962
|
IssuesEvent
|
2015-12-08 14:46:44
|
bmcfee/librosa
|
https://api.github.com/repos/bmcfee/librosa
|
opened
|
0.4.2 release to-dos
|
documentation management
|
- [ ] update version number
- [ ] update changelog
- see [closed PRs](https://github.com/bmcfee/librosa/pulls?utf8=%E2%9C%93&q=is%3Aclosed+is%3Apr+milestone%3A0.4.2+)
- [ ] update readme
- [ ] update examples
|
1.0
|
0.4.2 release to-dos - - [ ] update version number
- [ ] update changelog
- see [closed PRs](https://github.com/bmcfee/librosa/pulls?utf8=%E2%9C%93&q=is%3Aclosed+is%3Apr+milestone%3A0.4.2+)
- [ ] update readme
- [ ] update examples
|
non_process
|
release to dos update version number update changelog see update readme update examples
| 0
|
18,922
| 24,876,997,839
|
IssuesEvent
|
2022-10-27 20:03:22
|
BootBlock/FileSieve
|
https://api.github.com/repos/BootBlock/FileSieve
|
reopened
|
FS only process one item at a time.
|
processing stale
|
In a folder of 1500items, FS only process one item at a time (both in simulation mode and copy/move mode)
|
1.0
|
FS only process one item at a time. - In a folder of 1500items, FS only process one item at a time (both in simulation mode and copy/move mode)
|
process
|
fs only process one item at a time in a folder of fs only process one item at a time both in simulation mode and copy move mode
| 1
|
6,199
| 2,816,018,365
|
IssuesEvent
|
2015-05-19 09:11:41
|
agershun/alasql
|
https://api.github.com/repos/agershun/alasql
|
closed
|
Use in meteor
|
enhancement for discussion solved please test
|
You might want to include in your documentation something like this for Meteor users:
"Use SQL in Meteor client-side querys.
Let's face it, Mongo sucks on common data operations, so having the ability to use SQL to query data (with JOINS, GRUP BY and so on) would relief a lot of pain.With alaSQL you can do something like this in your helper:
productsSold:function(){
var customerSalesHistory=salesHistory.find({customerId:Session.get('currentCustomer')}).fetch();
var items=products.find().fetch();
return alasql("select items.name, sales.ordered as quantity from ? sales, ? items
where items.Id=sales.itemId",[customerSalesHistory,items]);
}
"
Also, you might want to create the json to make alaSql a meteor package. Meteor users can only use minimongo, so there is a real need of a reactive way to make reactive querys on teh client.
Also, minimongo is not persistent, while I see that alaSql is. So for Meteor users, alaSql is the best thing ever.
|
1.0
|
Use in meteor - You might want to include in your documentation something like this for Meteor users:
"Use SQL in Meteor client-side querys.
Let's face it, Mongo sucks on common data operations, so having the ability to use SQL to query data (with JOINS, GRUP BY and so on) would relief a lot of pain.With alaSQL you can do something like this in your helper:
productsSold:function(){
var customerSalesHistory=salesHistory.find({customerId:Session.get('currentCustomer')}).fetch();
var items=products.find().fetch();
return alasql("select items.name, sales.ordered as quantity from ? sales, ? items
where items.Id=sales.itemId",[customerSalesHistory,items]);
}
"
Also, you might want to create the json to make alaSql a meteor package. Meteor users can only use minimongo, so there is a real need of a reactive way to make reactive querys on teh client.
Also, minimongo is not persistent, while I see that alaSql is. So for Meteor users, alaSql is the best thing ever.
|
non_process
|
use in meteor you might want to include in your documentation something like this for meteor users use sql in meteor client side querys let s face it mongo sucks on common data operations so having the ability to use sql to query data with joins grup by and so on would relief a lot of pain with alasql you can do something like this in your helper productssold function var customersaleshistory saleshistory find customerid session get currentcustomer fetch var items products find fetch return alasql select items name sales ordered as quantity from sales items where items id sales itemid also you might want to create the json to make alasql a meteor package meteor users can only use minimongo so there is a real need of a reactive way to make reactive querys on teh client also minimongo is not persistent while i see that alasql is so for meteor users alasql is the best thing ever
| 0
|
2,762
| 5,695,992,442
|
IssuesEvent
|
2017-04-16 05:57:06
|
AllenFang/react-bootstrap-table
|
https://api.github.com/repos/AllenFang/react-bootstrap-table
|
closed
|
Custom the input field only instead of whole body of insert modal
|
enhancement inprocess
|
Hi Allen,
Really appreciate the work you've done here. For the Add Item Modal body, is it possible to customize one particular form field? In my case, I want to change the type of the form field from type="text" to type="password", and I can't reference the HTML element since there's no ID. Thanks in advance!
|
1.0
|
Custom the input field only instead of whole body of insert modal - Hi Allen,
Really appreciate the work you've done here. For the Add Item Modal body, is it possible to customize one particular form field? In my case, I want to change the type of the form field from type="text" to type="password", and I can't reference the HTML element since there's no ID. Thanks in advance!
|
process
|
custom the input field only instead of whole body of insert modal hi allen really appreciate the work you ve done here for the add item modal body is it possible to customize one particular form field in my case i want to change the type of the form field from type text to type password and i can t reference the html element since there s no id thanks in advance
| 1
|
36,532
| 5,068,846,924
|
IssuesEvent
|
2016-12-25 00:39:50
|
attendanceproject/djattendance
|
https://api.github.com/repos/attendanceproject/djattendance
|
closed
|
Web-access Admin view for TA's + Networks Team
|
feature testing
|
Web-access Admin view for TA's + Networks Team. To give internet to any devices via a mac-address.
@ricefield
Request from Ryan Hsu
|
1.0
|
Web-access Admin view for TA's + Networks Team - Web-access Admin view for TA's + Networks Team. To give internet to any devices via a mac-address.
@ricefield
Request from Ryan Hsu
|
non_process
|
web access admin view for ta s networks team web access admin view for ta s networks team to give internet to any devices via a mac address ricefield request from ryan hsu
| 0
|
11,150
| 13,957,693,181
|
IssuesEvent
|
2020-10-24 08:10:54
|
alexanderkotsev/geoportal
|
https://api.github.com/repos/alexanderkotsev/geoportal
|
opened
|
BE: Request about a new harvest of "Geopunt-Metadatacenter zoekdienst" Discovery Service
|
BE - Belgium Geoportal Harvesting process
|
From: ROESBEKE, Marc [marc.roesbeke@mow.vlaanderen.be]
Sent: 05 February 2019 15:06
To: JRC INSPIRE SUPPORT
Subject: [Geoportal Helpdesk]
Dear,
When will the metadata documents be collected from the officially registered Discovery Service Geopunt-Metadatacenter zoekdienst (Informatie Vlaanderen) Country BE?
The last time was Saturday, January 19, 2019 13:34:28 GMT.
Kind regards,
Marc Roesbeke
Team Vlaamse Hydrografie
Applicaton Manager
|
1.0
|
BE: Request about a new harvest of "Geopunt-Metadatacenter zoekdienst" Discovery Service - From: ROESBEKE, Marc [marc.roesbeke@mow.vlaanderen.be]
Sent: 05 February 2019 15:06
To: JRC INSPIRE SUPPORT
Subject: [Geoportal Helpdesk]
Dear,
When will the metadata documents be collected from the officially registered Discovery Service Geopunt-Metadatacenter zoekdienst (Informatie Vlaanderen) Country BE?
The last time was Saturday, January 19, 2019 13:34:28 GMT.
Kind regards,
Marc Roesbeke
Team Vlaamse Hydrografie
Applicaton Manager
|
process
|
be request about a new harvest of geopunt metadatacenter zoekdienst discovery service from roesbeke marc sent february to jrc inspire support subject dear when will the metadata documents be collected from the officially registered discovery service geopunt metadatacenter zoekdienst informatie vlaanderen country be the last time was saturday january gmt kind regards marc roesbeke team vlaamse hydrografie applicaton manager
| 1
|
10,315
| 13,157,661,097
|
IssuesEvent
|
2020-08-10 13:08:05
|
googleapis/java-cloud-bom
|
https://api.github.com/repos/googleapis/java-cloud-bom
|
reopened
|
Dependency Dashboard
|
type: process
|
This issue contains a list of Renovate updates and their statuses.
## Closed/Ignored
These updates were closed unmerged and will not be recreated unless you click a checkbox below.
- [ ] <!-- recreate-branch=renovate/com.google.googlejavaformat-google-java-format-1.x -->[deps: update dependency com.google.googlejavaformat:google-java-format to v1.8](../pull/612)
---
<details><summary>Advanced</summary>
- [ ] <!-- manual job -->Check this box to trigger a request for Renovate to run again on this repository
</details>
|
1.0
|
Dependency Dashboard - This issue contains a list of Renovate updates and their statuses.
## Closed/Ignored
These updates were closed unmerged and will not be recreated unless you click a checkbox below.
- [ ] <!-- recreate-branch=renovate/com.google.googlejavaformat-google-java-format-1.x -->[deps: update dependency com.google.googlejavaformat:google-java-format to v1.8](../pull/612)
---
<details><summary>Advanced</summary>
- [ ] <!-- manual job -->Check this box to trigger a request for Renovate to run again on this repository
</details>
|
process
|
dependency dashboard this issue contains a list of renovate updates and their statuses closed ignored these updates were closed unmerged and will not be recreated unless you click a checkbox below pull advanced check this box to trigger a request for renovate to run again on this repository
| 1
|
87,537
| 10,926,016,696
|
IssuesEvent
|
2019-11-22 13:52:35
|
Altinn/altinn-studio
|
https://api.github.com/repos/Altinn/altinn-studio
|
closed
|
Markering av fokus
|
kind/bug solution/app-frontend team/tamagotchi ux/visual-design ux/wcag
|
## Describe the bug
Ved test av skjema
1) settes ikke fokus og cursor til første element
> Vil ikke bli løst i denne bug. Skjermlesere leser ikke opp informasjon om siden hvis det autofokuseres på første element.
2) markeres ikke fokus på radioknapper og avkrysningsboker
3) fokus på datofelt, gir ramme med 2 forskjellige farger
## To Reproduce
Steps to reproduce the behavior:
1. Gå til tjenesten aarsregnskap_rr0002 til BRREG
2. Velg manuell test
3. Må selv sette fokus til det første elementet
4. Ved å tabbe nedover så ser man at ikke alle felt viser når de får fokus
## Expected behavior
Forventer at
1) ~~første åpne felt får fokus ved åpning av skjema~~ _Se kommentar øverst_
2) fokus vises for alle typer komponenter
3) hele rammen for datofelt har samme farge ved fokus
## Screenshots
Ikke fokus på første åpne felt ved åpning:
Radioknapp Ja har fokus? (tror jeg):
Jepp, for når jeg trykker, så velges den:
Datofelt har fokus:
## Additional info
Windows 10 Pro, Chrome
## Development
- [x] Develop
- [ ] Document the removal of Read-Only
### QA
- [ ] QA
|
1.0
|
Markering av fokus - ## Describe the bug
Ved test av skjema
1) settes ikke fokus og cursor til første element
> Vil ikke bli løst i denne bug. Skjermlesere leser ikke opp informasjon om siden hvis det autofokuseres på første element.
2) markeres ikke fokus på radioknapper og avkrysningsboker
3) fokus på datofelt, gir ramme med 2 forskjellige farger
## To Reproduce
Steps to reproduce the behavior:
1. Gå til tjenesten aarsregnskap_rr0002 til BRREG
2. Velg manuell test
3. Må selv sette fokus til det første elementet
4. Ved å tabbe nedover så ser man at ikke alle felt viser når de får fokus
## Expected behavior
Forventer at
1) ~~første åpne felt får fokus ved åpning av skjema~~ _Se kommentar øverst_
2) fokus vises for alle typer komponenter
3) hele rammen for datofelt har samme farge ved fokus
## Screenshots
Ikke fokus på første åpne felt ved åpning:
Radioknapp Ja har fokus? (tror jeg):
Jepp, for når jeg trykker, så velges den:
Datofelt har fokus:
## Additional info
Windows 10 Pro, Chrome
## Development
- [x] Develop
- [ ] Document the removal of Read-Only
### QA
- [ ] QA
|
non_process
|
markering av fokus describe the bug ved test av skjema settes ikke fokus og cursor til første element vil ikke bli løst i denne bug skjermlesere leser ikke opp informasjon om siden hvis det autofokuseres på første element markeres ikke fokus på radioknapper og avkrysningsboker fokus på datofelt gir ramme med forskjellige farger to reproduce steps to reproduce the behavior gå til tjenesten aarsregnskap til brreg velg manuell test må selv sette fokus til det første elementet ved å tabbe nedover så ser man at ikke alle felt viser når de får fokus expected behavior forventer at første åpne felt får fokus ved åpning av skjema se kommentar øverst fokus vises for alle typer komponenter hele rammen for datofelt har samme farge ved fokus screenshots ikke fokus på første åpne felt ved åpning radioknapp ja har fokus tror jeg jepp for når jeg trykker så velges den datofelt har fokus additional info windows pro chrome development develop document the removal of read only qa qa
| 0
|
10,906
| 13,685,598,149
|
IssuesEvent
|
2020-09-30 07:24:38
|
prisma/quaint
|
https://api.github.com/repos/prisma/quaint
|
closed
|
connection.raw_cmd() on MySQL does not return errors that occured after the first statement
|
bug/2-confirmed kind/bug process/candidate team/engines
|
Test reproduction: https://github.com/prisma/quaint/pull/186
`SELECT 1; SELECT YOLO;` will fail at the second statement, but no error will be returned to the caller. We would want this feature to run a SQL script with multiple statements and know whether it succeeded or errored.
|
1.0
|
connection.raw_cmd() on MySQL does not return errors that occured after the first statement - Test reproduction: https://github.com/prisma/quaint/pull/186
`SELECT 1; SELECT YOLO;` will fail at the second statement, but no error will be returned to the caller. We would want this feature to run a SQL script with multiple statements and know whether it succeeded or errored.
|
process
|
connection raw cmd on mysql does not return errors that occured after the first statement test reproduction select select yolo will fail at the second statement but no error will be returned to the caller we would want this feature to run a sql script with multiple statements and know whether it succeeded or errored
| 1
|
80,195
| 7,741,957,131
|
IssuesEvent
|
2018-05-29 08:01:13
|
realm/realm-core
|
https://api.github.com/repos/realm/realm-core
|
closed
|
AFL Improvements, part 2
|
T:Test
|
Continuation of #1791
- [ ] Exclude ordinary unit tests from the builds as they are not run and affects the coverage negatively
- [ ] Exercise accessors (e.g. via `TableView`) (partially done)
- [ ] Start reading values out from the Realm and check that they are equal to those originally stored (possibly requires a mirror storage of some kind)
- [ ] Consider generating coverage reports and improve from those: https://github.com/mrash/afl-cov
- [ ] Tweaks. May not be necessary as AFL _may_ already do this internally. Should be investigated before doing any work.
- [ ] "Stratify" input in order to get more edge cases
- [ ] Improve `create_string` to generate more "interesting" strings (e.g. with embedded `0` bytes)
- [ ] Consider making some things less random (e.g. table names) as fuzz testing those probably have less value / coverage compared to other paths
|
1.0
|
AFL Improvements, part 2 - Continuation of #1791
- [ ] Exclude ordinary unit tests from the builds as they are not run and affects the coverage negatively
- [ ] Exercise accessors (e.g. via `TableView`) (partially done)
- [ ] Start reading values out from the Realm and check that they are equal to those originally stored (possibly requires a mirror storage of some kind)
- [ ] Consider generating coverage reports and improve from those: https://github.com/mrash/afl-cov
- [ ] Tweaks. May not be necessary as AFL _may_ already do this internally. Should be investigated before doing any work.
- [ ] "Stratify" input in order to get more edge cases
- [ ] Improve `create_string` to generate more "interesting" strings (e.g. with embedded `0` bytes)
- [ ] Consider making some things less random (e.g. table names) as fuzz testing those probably have less value / coverage compared to other paths
|
non_process
|
afl improvements part continuation of exclude ordinary unit tests from the builds as they are not run and affects the coverage negatively exercise accessors e g via tableview partially done start reading values out from the realm and check that they are equal to those originally stored possibly requires a mirror storage of some kind consider generating coverage reports and improve from those tweaks may not be necessary as afl may already do this internally should be investigated before doing any work stratify input in order to get more edge cases improve create string to generate more interesting strings e g with embedded bytes consider making some things less random e g table names as fuzz testing those probably have less value coverage compared to other paths
| 0
|
83,802
| 16,373,024,447
|
IssuesEvent
|
2021-05-15 14:35:11
|
heclak/community-a4e-c
|
https://api.github.com/repos/heclak/community-a4e-c
|
closed
|
Input: Function selector switch in 2.0 beta 4
|
Bug Code/LUA
|
Function selector does not turn to newly added CMPTR position when keymapping Function Selector Switch - CCW and CW are used.
Also there is inconsistency in category definition in lua files. Some positions are under Weapons & Instrument Panel, some are not. (this issue might bleed to other keymappings as well)
|
1.0
|
Input: Function selector switch in 2.0 beta 4 - Function selector does not turn to newly added CMPTR position when keymapping Function Selector Switch - CCW and CW are used.
Also there is inconsistency in category definition in lua files. Some positions are under Weapons & Instrument Panel, some are not. (this issue might bleed to other keymappings as well)
|
non_process
|
input function selector switch in beta function selector does not turn to newly added cmptr position when keymapping function selector switch ccw and cw are used also there is inconsistency in category definition in lua files some positions are under weapons instrument panel some are not this issue might bleed to other keymappings as well
| 0
|
11,948
| 14,712,237,149
|
IssuesEvent
|
2021-01-05 08:39:56
|
cypress-io/cypress
|
https://api.github.com/repos/cypress-io/cypress
|
closed
|
Swap out config validation with standardized json schema validator
|
first-timers-only pkg/server process: tests stage: ready for work
|
We already created a JSON schema spec for the configuration here: https://github.com/cypress-io/cypress/blob/develop/cli/schema/cypress.schema.json
We can use this to also do the `lib/config` validation, setting defaults, etc. We're using this on all of our other projects so it just makes sense to keep it all in one area and one file.
|
1.0
|
Swap out config validation with standardized json schema validator - We already created a JSON schema spec for the configuration here: https://github.com/cypress-io/cypress/blob/develop/cli/schema/cypress.schema.json
We can use this to also do the `lib/config` validation, setting defaults, etc. We're using this on all of our other projects so it just makes sense to keep it all in one area and one file.
|
process
|
swap out config validation with standardized json schema validator we already created a json schema spec for the configuration here we can use this to also do the lib config validation setting defaults etc we re using this on all of our other projects so it just makes sense to keep it all in one area and one file
| 1
|
23,144
| 21,162,166,935
|
IssuesEvent
|
2022-04-07 10:20:37
|
ClickHouse/ClickHouse
|
https://api.github.com/repos/ClickHouse/ClickHouse
|
closed
|
DNS Resolver polluting the logs
|
usability
|
**Describe the bug**
If a hostname used is invalid, the dns resolver will keep throwing errors in each update after the server is restarted.
**Does it reproduce on recent release?**
Yes
**How to reproduce**
Run `01946_test_wrong_host_name_access` and keep an eye on the logs after. In each refresh you will see an error like this although the user was already deleted:
```
2021.07.22 17:39:03.783264 [ 694783 ] {} <Debug> DNSResolver: Updating DNS cache
2021.07.22 17:39:03.808051 [ 694783 ] {} <Error> DNSResolver: Cannot resolve host (non.existing.host.name), error 0: non.existing.host.name.
2021.07.22 17:39:03.808244 [ 694783 ] {} <Error> bool DB::DNSResolver::updateCacheImpl(UpdateF &&, ElemsT &&, const DB::String &) [UpdateF = bool (DB::DNSResolver::*)(const std::string &), ElemsT = std::unordered_set<std::string> &]: Code: 198. DB::Exception: Not found address of host: non.existing.host.name. (DNS_ERROR), Stack trace (when copying this message, always include the lines below):
0. /mnt/ch/ClickHouse/contrib/poco/Foundation/src/Exception.cpp:28: Poco::Exception::Exception(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, int) @ 0x11733a in /mnt/ch/ClickHouse/build/contrib/poco-cmake/Foundation/lib_poco_foundation.so
1. /mnt/ch/ClickHouse/src/Common/Exception.cpp:59: DB::Exception::Exception(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, int, bool) @ 0x11216e in /mnt/ch/ClickHouse/build/src/libclickhouse_common_io.so
2. /mnt/ch/ClickHouse/src/Common/DNSResolver.cpp:0: DB::resolveIPAddressImpl(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) @ 0xffe53 in /mnt/ch/ClickHouse/build/src/libclickhouse_common_io.so
3. /mnt/ch/ClickHouse/contrib/libcxx/include/__mutex_base:91: std::__1::vector<Poco::Net::IPAddress, std::__1::allocator<Poco::Net::IPAddress> > SimpleCache<std::__1::vector<Poco::Net::IPAddress, std::__1::allocator<Poco::Net::IPAddress> > (std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&), &(DB::resolveIPAddressImpl(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&))>::operator()<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&>(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) @ 0x100a54 in /mnt/ch/ClickHouse/build/src/libclickhouse_common_io.so
4. /mnt/ch/ClickHouse/contrib/libcxx/include/memory:1627: DB::DNSResolver::updateHost(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) @ 0x102779 in /mnt/ch/ClickHouse/build/src/libclickhouse_common_io.so
5. /mnt/ch/ClickHouse/src/Common/DNSResolver.cpp:262: bool DB::DNSResolver::updateCacheImpl<bool (DB::DNSResolver::*)(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&), std::__1::unordered_set<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::hash<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > >, std::__1::equal_to<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > >&>(bool (DB::DNSResolver::*&&)(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&), std::__1::unordered_set<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::hash<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > >, std::__1::equal_to<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > >&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) @ 0x102f5f in /mnt/ch/ClickHouse/build/src/libclickhouse_common_io.so
6. /mnt/ch/ClickHouse/contrib/libcxx/include/string:1444: DB::DNSResolver::updateCache() @ 0x10206b in /mnt/ch/ClickHouse/build/src/libclickhouse_common_io.so
7. /mnt/ch/ClickHouse/src/Interpreters/DNSCacheUpdater.cpp:23: DB::DNSCacheUpdater::run() @ 0x946033 in /mnt/ch/ClickHouse/build/src/libclickhouse_interpreters.so
8. /mnt/ch/ClickHouse/contrib/libcxx/include/functional:0: DB::BackgroundSchedulePoolTaskInfo::execute() @ 0xc2c88 in /mnt/ch/ClickHouse/build/src/libclickhouse_core.so
9. /mnt/ch/ClickHouse/contrib/poco/Foundation/include/Poco/AtomicCounter.h:314: DB::BackgroundSchedulePool::threadFunction() @ 0xc4695 in /mnt/ch/ClickHouse/build/src/libclickhouse_core.so
10. /mnt/ch/ClickHouse/src/Core/BackgroundSchedulePool.cpp:0: void std::__1::__function::__policy_invoker<void ()>::__call_impl<std::__1::__function::__default_alloc_func<ThreadFromGlobalPool::ThreadFromGlobalPool<DB::BackgroundSchedulePool::BackgroundSchedulePool(unsigned long, unsigned long, char const*)::$_1>(DB::BackgroundSchedulePool::BackgroundSchedulePool(unsigned long, unsigned long, char const*)::$_1&&)::'lambda'(), void ()> >(std::__1::__function::__policy_storage const*) @ 0xc4caa in /mnt/ch/ClickHouse/build/src/libclickhouse_core.so
11. /mnt/ch/ClickHouse/contrib/libcxx/include/functional:2210: ThreadPoolImpl<std::__1::thread>::worker(std::__1::__list_iterator<std::__1::thread, void*>) @ 0x16726e in /mnt/ch/ClickHouse/build/src/libclickhouse_common_io.so
12. /mnt/ch/ClickHouse/contrib/libcxx/include/memory:1655: void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void ThreadPoolImpl<std::__1::thread>::scheduleImpl<void>(std::__1::function<void ()>, int, std::__1::optional<unsigned long>)::'lambda0'()> >(void*) @ 0x1697c9 in /mnt/ch/ClickHouse/build/src/libclickhouse_common_io.so
13. start_thread @ 0x9259 in /usr/lib/libpthread-2.33.so
14. __clone @ 0xfe5e3 in /usr/lib/libc-2.33.so
(version 21.9.1.1)
2021.07.22 17:39:03.808439 [ 694783 ] {} <Debug> DNSResolver: Updated DNS cache
```
**Expected behavior**
The element should be removed from the cache on error, so it's only shown once (or when accessing it again), but not in every refresh.
|
True
|
DNS Resolver polluting the logs - **Describe the bug**
If a hostname used is invalid, the dns resolver will keep throwing errors in each update after the server is restarted.
**Does it reproduce on recent release?**
Yes
**How to reproduce**
Run `01946_test_wrong_host_name_access` and keep an eye on the logs after. In each refresh you will see an error like this although the user was already deleted:
```
2021.07.22 17:39:03.783264 [ 694783 ] {} <Debug> DNSResolver: Updating DNS cache
2021.07.22 17:39:03.808051 [ 694783 ] {} <Error> DNSResolver: Cannot resolve host (non.existing.host.name), error 0: non.existing.host.name.
2021.07.22 17:39:03.808244 [ 694783 ] {} <Error> bool DB::DNSResolver::updateCacheImpl(UpdateF &&, ElemsT &&, const DB::String &) [UpdateF = bool (DB::DNSResolver::*)(const std::string &), ElemsT = std::unordered_set<std::string> &]: Code: 198. DB::Exception: Not found address of host: non.existing.host.name. (DNS_ERROR), Stack trace (when copying this message, always include the lines below):
0. /mnt/ch/ClickHouse/contrib/poco/Foundation/src/Exception.cpp:28: Poco::Exception::Exception(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, int) @ 0x11733a in /mnt/ch/ClickHouse/build/contrib/poco-cmake/Foundation/lib_poco_foundation.so
1. /mnt/ch/ClickHouse/src/Common/Exception.cpp:59: DB::Exception::Exception(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, int, bool) @ 0x11216e in /mnt/ch/ClickHouse/build/src/libclickhouse_common_io.so
2. /mnt/ch/ClickHouse/src/Common/DNSResolver.cpp:0: DB::resolveIPAddressImpl(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) @ 0xffe53 in /mnt/ch/ClickHouse/build/src/libclickhouse_common_io.so
3. /mnt/ch/ClickHouse/contrib/libcxx/include/__mutex_base:91: std::__1::vector<Poco::Net::IPAddress, std::__1::allocator<Poco::Net::IPAddress> > SimpleCache<std::__1::vector<Poco::Net::IPAddress, std::__1::allocator<Poco::Net::IPAddress> > (std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&), &(DB::resolveIPAddressImpl(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&))>::operator()<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&>(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) @ 0x100a54 in /mnt/ch/ClickHouse/build/src/libclickhouse_common_io.so
4. /mnt/ch/ClickHouse/contrib/libcxx/include/memory:1627: DB::DNSResolver::updateHost(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) @ 0x102779 in /mnt/ch/ClickHouse/build/src/libclickhouse_common_io.so
5. /mnt/ch/ClickHouse/src/Common/DNSResolver.cpp:262: bool DB::DNSResolver::updateCacheImpl<bool (DB::DNSResolver::*)(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&), std::__1::unordered_set<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::hash<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > >, std::__1::equal_to<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > >&>(bool (DB::DNSResolver::*&&)(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&), std::__1::unordered_set<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::hash<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > >, std::__1::equal_to<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > >&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) @ 0x102f5f in /mnt/ch/ClickHouse/build/src/libclickhouse_common_io.so
6. /mnt/ch/ClickHouse/contrib/libcxx/include/string:1444: DB::DNSResolver::updateCache() @ 0x10206b in /mnt/ch/ClickHouse/build/src/libclickhouse_common_io.so
7. /mnt/ch/ClickHouse/src/Interpreters/DNSCacheUpdater.cpp:23: DB::DNSCacheUpdater::run() @ 0x946033 in /mnt/ch/ClickHouse/build/src/libclickhouse_interpreters.so
8. /mnt/ch/ClickHouse/contrib/libcxx/include/functional:0: DB::BackgroundSchedulePoolTaskInfo::execute() @ 0xc2c88 in /mnt/ch/ClickHouse/build/src/libclickhouse_core.so
9. /mnt/ch/ClickHouse/contrib/poco/Foundation/include/Poco/AtomicCounter.h:314: DB::BackgroundSchedulePool::threadFunction() @ 0xc4695 in /mnt/ch/ClickHouse/build/src/libclickhouse_core.so
10. /mnt/ch/ClickHouse/src/Core/BackgroundSchedulePool.cpp:0: void std::__1::__function::__policy_invoker<void ()>::__call_impl<std::__1::__function::__default_alloc_func<ThreadFromGlobalPool::ThreadFromGlobalPool<DB::BackgroundSchedulePool::BackgroundSchedulePool(unsigned long, unsigned long, char const*)::$_1>(DB::BackgroundSchedulePool::BackgroundSchedulePool(unsigned long, unsigned long, char const*)::$_1&&)::'lambda'(), void ()> >(std::__1::__function::__policy_storage const*) @ 0xc4caa in /mnt/ch/ClickHouse/build/src/libclickhouse_core.so
11. /mnt/ch/ClickHouse/contrib/libcxx/include/functional:2210: ThreadPoolImpl<std::__1::thread>::worker(std::__1::__list_iterator<std::__1::thread, void*>) @ 0x16726e in /mnt/ch/ClickHouse/build/src/libclickhouse_common_io.so
12. /mnt/ch/ClickHouse/contrib/libcxx/include/memory:1655: void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void ThreadPoolImpl<std::__1::thread>::scheduleImpl<void>(std::__1::function<void ()>, int, std::__1::optional<unsigned long>)::'lambda0'()> >(void*) @ 0x1697c9 in /mnt/ch/ClickHouse/build/src/libclickhouse_common_io.so
13. start_thread @ 0x9259 in /usr/lib/libpthread-2.33.so
14. __clone @ 0xfe5e3 in /usr/lib/libc-2.33.so
(version 21.9.1.1)
2021.07.22 17:39:03.808439 [ 694783 ] {} <Debug> DNSResolver: Updated DNS cache
```
**Expected behavior**
The element should be removed from the cache on error, so it's only shown once (or when accessing it again), but not in every refresh.
|
non_process
|
dns resolver polluting the logs describe the bug if a hostname used is invalid the dns resolver will keep throwing errors in each update after the server is restarted does it reproduce on recent release yes how to reproduce run test wrong host name access and keep an eye on the logs after in each refresh you will see an error like this although the user was already deleted dnsresolver updating dns cache dnsresolver cannot resolve host non existing host name error non existing host name bool db dnsresolver updatecacheimpl updatef elemst const db string code db exception not found address of host non existing host name dns error stack trace when copying this message always include the lines below mnt ch clickhouse contrib poco foundation src exception cpp poco exception exception std basic string std allocator const int in mnt ch clickhouse build contrib poco cmake foundation lib poco foundation so mnt ch clickhouse src common exception cpp db exception exception std basic string std allocator const int bool in mnt ch clickhouse build src libclickhouse common io so mnt ch clickhouse src common dnsresolver cpp db resolveipaddressimpl std basic string std allocator const in mnt ch clickhouse build src libclickhouse common io so mnt ch clickhouse contrib libcxx include mutex base std vector simplecache std basic string std allocator const db resolveipaddressimpl std basic string std allocator const operator std allocator const std basic string std allocator const in mnt ch clickhouse build src libclickhouse common io so mnt ch clickhouse contrib libcxx include memory db dnsresolver updatehost std basic string std allocator const in mnt ch clickhouse build src libclickhouse common io so mnt ch clickhouse src common dnsresolver cpp bool db dnsresolver updatecacheimpl std allocator const std unordered set std allocator std hash std allocator std equal to std allocator std allocator std allocator bool db dnsresolver std basic string std allocator const std unordered set std allocator std hash std allocator std equal to std allocator std allocator std allocator std basic string std allocator const in mnt ch clickhouse build src libclickhouse common io so mnt ch clickhouse contrib libcxx include string db dnsresolver updatecache in mnt ch clickhouse build src libclickhouse common io so mnt ch clickhouse src interpreters dnscacheupdater cpp db dnscacheupdater run in mnt ch clickhouse build src libclickhouse interpreters so mnt ch clickhouse contrib libcxx include functional db backgroundschedulepooltaskinfo execute in mnt ch clickhouse build src libclickhouse core so mnt ch clickhouse contrib poco foundation include poco atomiccounter h db backgroundschedulepool threadfunction in mnt ch clickhouse build src libclickhouse core so mnt ch clickhouse src core backgroundschedulepool cpp void std function policy invoker call impl db backgroundschedulepool backgroundschedulepool unsigned long unsigned long char const lambda void std function policy storage const in mnt ch clickhouse build src libclickhouse core so mnt ch clickhouse contrib libcxx include functional threadpoolimpl worker std list iterator in mnt ch clickhouse build src libclickhouse common io so mnt ch clickhouse contrib libcxx include memory void std thread proxy void threadpoolimpl scheduleimpl std function int std optional void in mnt ch clickhouse build src libclickhouse common io so start thread in usr lib libpthread so clone in usr lib libc so version dnsresolver updated dns cache expected behavior the element should be removed from the cache on error so it s only shown once or when accessing it again but not in every refresh
| 0
|
14,550
| 17,668,757,093
|
IssuesEvent
|
2021-08-23 00:33:43
|
lynnandtonic/nestflix.fun
|
https://api.github.com/repos/lynnandtonic/nestflix.fun
|
closed
|
Add Scratchtasia
|
suggested title in process
|
Please add as much of the following info as you can:
Title: Scratchtasia
Type (film/tv show): Film
Film or show in which it appears: The Simpsons
Is the parent film/show streaming anywhere?
yes
About when in the parent film/show does it appear?
The Itchy and Scratchy Land
Actual footage of the film/show can be seen (yes/no)?
yes
|
1.0
|
Add Scratchtasia - Please add as much of the following info as you can:
Title: Scratchtasia
Type (film/tv show): Film
Film or show in which it appears: The Simpsons
Is the parent film/show streaming anywhere?
yes
About when in the parent film/show does it appear?
The Itchy and Scratchy Land
Actual footage of the film/show can be seen (yes/no)?
yes
|
process
|
add scratchtasia please add as much of the following info as you can title scratchtasia type film tv show film film or show in which it appears the simpsons is the parent film show streaming anywhere yes about when in the parent film show does it appear the itchy and scratchy land actual footage of the film show can be seen yes no yes
| 1
|
2,463
| 5,242,667,951
|
IssuesEvent
|
2017-01-31 18:40:38
|
opentrials/opentrials
|
https://api.github.com/repos/opentrials/opentrials
|
closed
|
Extract completion_date from all our sources that have them
|
Processors
|
On #328, we started extracting `completion_date` from ClinicalTrials.gov and EUCTR. This issue is to keep track of extracting the same information from our other sources. We basically need to go on each one of them looking if they provide this information, and decide what field we should use for it (there're different types of dates of completion). See #328 for the background on why we've chosen the fields we did.
| Registry | Field |
| --- | --- |
| ClinicalTrials.gov | completion_date_actual |
| EUCTR | date_of_the_global_end_of_the_trial |
| ICTRP | N/A |
@opentrials/research This is a task that requires domain knowledge, so your help would be very useful.
|
1.0
|
Extract completion_date from all our sources that have them - On #328, we started extracting `completion_date` from ClinicalTrials.gov and EUCTR. This issue is to keep track of extracting the same information from our other sources. We basically need to go on each one of them looking if they provide this information, and decide what field we should use for it (there're different types of dates of completion). See #328 for the background on why we've chosen the fields we did.
| Registry | Field |
| --- | --- |
| ClinicalTrials.gov | completion_date_actual |
| EUCTR | date_of_the_global_end_of_the_trial |
| ICTRP | N/A |
@opentrials/research This is a task that requires domain knowledge, so your help would be very useful.
|
process
|
extract completion date from all our sources that have them on we started extracting completion date from clinicaltrials gov and euctr this issue is to keep track of extracting the same information from our other sources we basically need to go on each one of them looking if they provide this information and decide what field we should use for it there re different types of dates of completion see for the background on why we ve chosen the fields we did registry field clinicaltrials gov completion date actual euctr date of the global end of the trial ictrp n a opentrials research this is a task that requires domain knowledge so your help would be very useful
| 1
|
9,164
| 12,219,340,333
|
IssuesEvent
|
2020-05-01 21:28:21
|
jyn514/rcc
|
https://api.github.com/repos/jyn514/rcc
|
opened
|
[ICE] the lexer and the preprocessor have trouble getting along
|
ICE fuzz preprocessor
|
### Code
<!-- The code that caused the panic goes here.
This should also include the error message you got. -->
```c
#if\
2/
Message: expected `tokens_until_newline()` to reset `seen_line_token`, but `lexer.peek()` is Some(47)
Location: src/lex/cpp.rs:411
```
### Expected behavior
<!-- A description of what you expected to happen.
If you're not sure (e.g. this is invalid code),
paste the output of another compiler
(I like `clang -x c - -Wall -Wextra -pedantic`) -->
When the preprocessor calls `consume_whitespace`, it consumes _all_ the whitespace, not just the single line.
<details><summary>Backtrace</summary>
<!-- The output of `RUST_BACKTRACE=1 cargo run` goes here. -->
```
The application panicked (crashed).
Message: expected `tokens_until_newline()` to reset `seen_line_token`, but `lexer.peek()` is Some(47)
Location: src/lex/cpp.rs:411
Run with RUST_BACKTRACE=full to include source snippets.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
(5 post panic frames hidden)
5: rcc::lex::cpp::PreProcessor::tokens_until_newline::he745648b9c6da68d
at src/lex/cpp.rs:411
6: rcc::lex::cpp::PreProcessor::cpp_expr::hd2d583d5b383188b
at src/lex/cpp.rs:830
7: rcc::lex::cpp::PreProcessor::boolean_expr::hdaf7ae73e633a95f
at src/lex/cpp.rs:738
8: rcc::lex::cpp::PreProcessor::directive::hcba5a304072f52d6
at src/lex/cpp.rs:502
9: <rcc::lex::cpp::PreProcessor as core::iter::traits::iterator::Iterator>::next::hb4b76254fce30a67
at src/lex/cpp.rs:209
10: rcc::check_semantics::hd31cdd4033b22724
at src/lib.rs:170
11: rcc::compile::h7e7691f880c5ebf4
at /home/joshua/src/rust/rcc/src/lib.rs:218
12: rcc::aot_main::h8def1ca0324b8884
at src/main.rs:134
13: rcc::real_main::h192812ffe776ee2f
at src/main.rs:122
14: rcc::main::hc67a23664e8d7b5c
at src/main.rs:200
```
</details>
|
1.0
|
[ICE] the lexer and the preprocessor have trouble getting along - ### Code
<!-- The code that caused the panic goes here.
This should also include the error message you got. -->
```c
#if\
2/
Message: expected `tokens_until_newline()` to reset `seen_line_token`, but `lexer.peek()` is Some(47)
Location: src/lex/cpp.rs:411
```
### Expected behavior
<!-- A description of what you expected to happen.
If you're not sure (e.g. this is invalid code),
paste the output of another compiler
(I like `clang -x c - -Wall -Wextra -pedantic`) -->
When the preprocessor calls `consume_whitespace`, it consumes _all_ the whitespace, not just the single line.
<details><summary>Backtrace</summary>
<!-- The output of `RUST_BACKTRACE=1 cargo run` goes here. -->
```
The application panicked (crashed).
Message: expected `tokens_until_newline()` to reset `seen_line_token`, but `lexer.peek()` is Some(47)
Location: src/lex/cpp.rs:411
Run with RUST_BACKTRACE=full to include source snippets.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
(5 post panic frames hidden)
5: rcc::lex::cpp::PreProcessor::tokens_until_newline::he745648b9c6da68d
at src/lex/cpp.rs:411
6: rcc::lex::cpp::PreProcessor::cpp_expr::hd2d583d5b383188b
at src/lex/cpp.rs:830
7: rcc::lex::cpp::PreProcessor::boolean_expr::hdaf7ae73e633a95f
at src/lex/cpp.rs:738
8: rcc::lex::cpp::PreProcessor::directive::hcba5a304072f52d6
at src/lex/cpp.rs:502
9: <rcc::lex::cpp::PreProcessor as core::iter::traits::iterator::Iterator>::next::hb4b76254fce30a67
at src/lex/cpp.rs:209
10: rcc::check_semantics::hd31cdd4033b22724
at src/lib.rs:170
11: rcc::compile::h7e7691f880c5ebf4
at /home/joshua/src/rust/rcc/src/lib.rs:218
12: rcc::aot_main::h8def1ca0324b8884
at src/main.rs:134
13: rcc::real_main::h192812ffe776ee2f
at src/main.rs:122
14: rcc::main::hc67a23664e8d7b5c
at src/main.rs:200
```
</details>
|
process
|
the lexer and the preprocessor have trouble getting along code the code that caused the panic goes here this should also include the error message you got c if message expected tokens until newline to reset seen line token but lexer peek is some location src lex cpp rs expected behavior a description of what you expected to happen if you re not sure e g this is invalid code paste the output of another compiler i like clang x c wall wextra pedantic when the preprocessor calls consume whitespace it consumes all the whitespace not just the single line backtrace the application panicked crashed message expected tokens until newline to reset seen line token but lexer peek is some location src lex cpp rs run with rust backtrace full to include source snippets ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ backtrace ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ post panic frames hidden rcc lex cpp preprocessor tokens until newline at src lex cpp rs rcc lex cpp preprocessor cpp expr at src lex cpp rs rcc lex cpp preprocessor boolean expr at src lex cpp rs rcc lex cpp preprocessor directive at src lex cpp rs next at src lex cpp rs rcc check semantics at src lib rs rcc compile at home joshua src rust rcc src lib rs rcc aot main at src main rs rcc real main at src main rs rcc main at src main rs
| 1
|
194,973
| 6,901,223,784
|
IssuesEvent
|
2017-11-25 03:40:07
|
arfc/predicting-the-past
|
https://api.github.com/repos/arfc/predicting-the-past
|
opened
|
Update US simulation with PRIS information
|
Comp:Core Difficulty:2-Challenging Priority:2-Normal Status:1-New Type:Feature
|
US simulation and analysis should be updated using the PRIS reactor text file as discussed with @katyhuff .
The PRIS data file should be more up-to-date and accurate.
This will be done before #22 .
|
1.0
|
Update US simulation with PRIS information - US simulation and analysis should be updated using the PRIS reactor text file as discussed with @katyhuff .
The PRIS data file should be more up-to-date and accurate.
This will be done before #22 .
|
non_process
|
update us simulation with pris information us simulation and analysis should be updated using the pris reactor text file as discussed with katyhuff the pris data file should be more up to date and accurate this will be done before
| 0
|
254,369
| 27,375,051,440
|
IssuesEvent
|
2023-02-28 04:50:21
|
CMSgov/cms-carts-seds
|
https://api.github.com/repos/CMSgov/cms-carts-seds
|
opened
|
SHF - cms-carts-seds - main - MEDIUM - AWS Health - AWS_ACM_RENEWAL_STATE_CHANGE
|
security-hub main
|
**************************************************************
__This issue was generated from Security Hub data and is managed through automation.__
Please do not edit the title or body of this issue, or remove the security-hub tag. All other edits/comments are welcome.
Finding Id: arn:aws:health:us-east-1:519095364708:event/ACM/AWS_ACM_RENEWAL_STATE_CHANGE/AWS_ACM_RENEWAL_STATE_CHANGE-42647c49-34db-4574-a687-7e799da26fef/77efde12d3c74f2d41714ee5361fe119a6fcdbd5
**************************************************************
## Type of Issue:
- [x] Security Hub Finding
## Title:
AWS Health - AWS_ACM_RENEWAL_STATE_CHANGE
## Id:
arn:aws:health:us-east-1:519095364708:event/ACM/AWS_ACM_RENEWAL_STATE_CHANGE/AWS_ACM_RENEWAL_STATE_CHANGE-42647c49-34db-4574-a687-7e799da26fef/77efde12d3c74f2d41714ee5361fe119a6fcdbd5
(You may use this ID to lookup this finding's details in Security Hub)
## Description
This is to notify you that AWS Certificate Manager (ACM) has completed the renewal of an SSL/TLS certificate that includes the primary domain mdctcartsdev.cms.gov and a total of 1 domains.\\n\\nAWS account ID: 519095364708\\nAWS Region name: us-east-1\\nCertificate identifier: arn:aws:acm:us-east-1:519095364708:certificate/81579c1c-75cd-4bef-98b6-90d7885d6d41\\n\\nYour new certificate expires on Mar 29, 2024 at 23:59:59 UTC. \\nIf you have questions about this process, please use the Support Center at https://console.aws.amazon.com/support to contact AWS Support. If you don’t have an AWS support plan, post a new thread in the AWS Certificate Manager discussion forum at https://forums.aws.amazon.com/forum.jspa?forumID=206\\n\\nThis notification is intended solely for authorized individuals for mdctcartsdev.cms.gov. To express any concerns about this notification or if it has reached you in error, forward it along with a brief explanation of your concern to validation-questions@amazon.com.\\n
## Remediation
undefined
## AC:
- The security hub finding is resolved or suppressed, indicated by a Workflow Status of Resolved or Suppressed.
|
True
|
SHF - cms-carts-seds - main - MEDIUM - AWS Health - AWS_ACM_RENEWAL_STATE_CHANGE - **************************************************************
__This issue was generated from Security Hub data and is managed through automation.__
Please do not edit the title or body of this issue, or remove the security-hub tag. All other edits/comments are welcome.
Finding Id: arn:aws:health:us-east-1:519095364708:event/ACM/AWS_ACM_RENEWAL_STATE_CHANGE/AWS_ACM_RENEWAL_STATE_CHANGE-42647c49-34db-4574-a687-7e799da26fef/77efde12d3c74f2d41714ee5361fe119a6fcdbd5
**************************************************************
## Type of Issue:
- [x] Security Hub Finding
## Title:
AWS Health - AWS_ACM_RENEWAL_STATE_CHANGE
## Id:
arn:aws:health:us-east-1:519095364708:event/ACM/AWS_ACM_RENEWAL_STATE_CHANGE/AWS_ACM_RENEWAL_STATE_CHANGE-42647c49-34db-4574-a687-7e799da26fef/77efde12d3c74f2d41714ee5361fe119a6fcdbd5
(You may use this ID to lookup this finding's details in Security Hub)
## Description
This is to notify you that AWS Certificate Manager (ACM) has completed the renewal of an SSL/TLS certificate that includes the primary domain mdctcartsdev.cms.gov and a total of 1 domains.\\n\\nAWS account ID: 519095364708\\nAWS Region name: us-east-1\\nCertificate identifier: arn:aws:acm:us-east-1:519095364708:certificate/81579c1c-75cd-4bef-98b6-90d7885d6d41\\n\\nYour new certificate expires on Mar 29, 2024 at 23:59:59 UTC. \\nIf you have questions about this process, please use the Support Center at https://console.aws.amazon.com/support to contact AWS Support. If you don’t have an AWS support plan, post a new thread in the AWS Certificate Manager discussion forum at https://forums.aws.amazon.com/forum.jspa?forumID=206\\n\\nThis notification is intended solely for authorized individuals for mdctcartsdev.cms.gov. To express any concerns about this notification or if it has reached you in error, forward it along with a brief explanation of your concern to validation-questions@amazon.com.\\n
## Remediation
undefined
## AC:
- The security hub finding is resolved or suppressed, indicated by a Workflow Status of Resolved or Suppressed.
|
non_process
|
shf cms carts seds main medium aws health aws acm renewal state change this issue was generated from security hub data and is managed through automation please do not edit the title or body of this issue or remove the security hub tag all other edits comments are welcome finding id arn aws health us east event acm aws acm renewal state change aws acm renewal state change type of issue security hub finding title aws health aws acm renewal state change id arn aws health us east event acm aws acm renewal state change aws acm renewal state change you may use this id to lookup this finding s details in security hub description this is to notify you that aws certificate manager acm has completed the renewal of an ssl tls certificate that includes the primary domain mdctcartsdev cms gov and a total of domains n naws account id naws region name us east ncertificate identifier arn aws acm us east certificate n nyour new certificate expires on mar at utc nif you have questions about this process please use the support center at to contact aws support if you don’t have an aws support plan post a new thread in the aws certificate manager discussion forum at notification is intended solely for authorized individuals for mdctcartsdev cms gov to express any concerns about this notification or if it has reached you in error forward it along with a brief explanation of your concern to validation questions amazon com n remediation undefined ac the security hub finding is resolved or suppressed indicated by a workflow status of resolved or suppressed
| 0
|
21,233
| 28,349,462,727
|
IssuesEvent
|
2023-04-12 00:50:15
|
metabase/metabase
|
https://api.github.com/repos/metabase/metabase
|
closed
|
[MLv2] Mark source table in `display-info` method output
|
.metabase-lib .Team/QueryProcessor :hammer_and_wrench:
|
It'd be handy if table info coming from the `display-info` method could have a flag telling the client if it's a source table. Example:
```ts
const [sourceTableColumn, joinedTableColumn] = ML.orderableColumns(query);
sourceTableColumn.table.is_source_table // true
joinedTableColumn.table.is_source_table // false
```
|
1.0
|
[MLv2] Mark source table in `display-info` method output - It'd be handy if table info coming from the `display-info` method could have a flag telling the client if it's a source table. Example:
```ts
const [sourceTableColumn, joinedTableColumn] = ML.orderableColumns(query);
sourceTableColumn.table.is_source_table // true
joinedTableColumn.table.is_source_table // false
```
|
process
|
mark source table in display info method output it d be handy if table info coming from the display info method could have a flag telling the client if it s a source table example ts const ml orderablecolumns query sourcetablecolumn table is source table true joinedtablecolumn table is source table false
| 1
|
136,424
| 12,710,181,421
|
IssuesEvent
|
2020-06-23 13:31:37
|
laminas/laminas-view
|
https://api.github.com/repos/laminas/laminas-view
|
closed
|
Typo in laminas-view/helpers
|
Bug Documentation
|
### Bug Report
| Q | A
|------------ | ------
| Version(s) | 2.11.4
#### Summary
The current documentation is inconsistent with uppercase and lowercase.
Therefore the example isn't working.
#### How to reproduce
On the page:
https://docs.laminas.dev/laminas-view/helpers/advanced-usage/#writing-custom-helpers
#### Current behavior
The registration gets described with the following words:
```html
Then assume that we register it with the plugin manager by the name "specialpurpose".
```
#### Expected behavior
But should be:
```html
Then assume that we register it with the plugin manager by the name "specialPurpose".
```
Because in the next code block it gets used as:
```php
echo $this->specialPurpose();
```
|
1.0
|
Typo in laminas-view/helpers - ### Bug Report
| Q | A
|------------ | ------
| Version(s) | 2.11.4
#### Summary
The current documentation is inconsistent with uppercase and lowercase.
Therefore the example isn't working.
#### How to reproduce
On the page:
https://docs.laminas.dev/laminas-view/helpers/advanced-usage/#writing-custom-helpers
#### Current behavior
The registration gets described with the following words:
```html
Then assume that we register it with the plugin manager by the name "specialpurpose".
```
#### Expected behavior
But should be:
```html
Then assume that we register it with the plugin manager by the name "specialPurpose".
```
Because in the next code block it gets used as:
```php
echo $this->specialPurpose();
```
|
non_process
|
typo in laminas view helpers bug report q a version s summary the current documentation is inconsistent with uppercase and lowercase therefore the example isn t working how to reproduce on the page current behavior the registration gets described with the following words html then assume that we register it with the plugin manager by the name specialpurpose expected behavior but should be html then assume that we register it with the plugin manager by the name specialpurpose because in the next code block it gets used as php echo this specialpurpose
| 0
|
6,693
| 2,857,192,120
|
IssuesEvent
|
2015-06-02 18:30:53
|
vert-x3/vertx-mail-client
|
https://api.github.com/repos/vert-x3/vertx-mail-client
|
closed
|
MailEncoderTest should check decoded text
|
question test
|
when asserting the encoded parts of the mime message (e.g. utf-8 text), the unit tests currently use the encoded string, maybe it would be better to decode it again via the Wiser api and check that
|
1.0
|
MailEncoderTest should check decoded text - when asserting the encoded parts of the mime message (e.g. utf-8 text), the unit tests currently use the encoded string, maybe it would be better to decode it again via the Wiser api and check that
|
non_process
|
mailencodertest should check decoded text when asserting the encoded parts of the mime message e g utf text the unit tests currently use the encoded string maybe it would be better to decode it again via the wiser api and check that
| 0
|
22,685
| 31,987,811,763
|
IssuesEvent
|
2023-09-21 01:47:55
|
prusa3d/Prusa-Firmware
|
https://api.github.com/repos/prusa3d/Prusa-Firmware
|
closed
|
[Feature request] Non-interactive variant of Tx + Tc G-codes
|
feature request octoprint processing stale-issue
|
As far as I can tell, the `T0` - `T4` G-codes are non-interactive equivalent to `T?`, but there is no way to specify the extruder using the new default (but undocumented) `Tx` + `Tc` commands.
Suggestion : implement G-codes like `Tx0` - `Tx4` to allow specifying the extruder when using Octoprint or the like.
|
1.0
|
[Feature request] Non-interactive variant of Tx + Tc G-codes - As far as I can tell, the `T0` - `T4` G-codes are non-interactive equivalent to `T?`, but there is no way to specify the extruder using the new default (but undocumented) `Tx` + `Tc` commands.
Suggestion : implement G-codes like `Tx0` - `Tx4` to allow specifying the extruder when using Octoprint or the like.
|
process
|
non interactive variant of tx tc g codes as far as i can tell the g codes are non interactive equivalent to t but there is no way to specify the extruder using the new default but undocumented tx tc commands suggestion implement g codes like to allow specifying the extruder when using octoprint or the like
| 1
|
19,642
| 26,005,359,830
|
IssuesEvent
|
2022-12-20 18:49:13
|
hashgraph/hedera-mirror-node
|
https://api.github.com/repos/hashgraph/hedera-mirror-node
|
closed
|
pre-commit hook fails in github workflow
|
bug process
|
### Description
The new git pre-commit hook fails in github workflow release automation job `Create PR`'s `Create Pull Reques` step:
```
buildSrc/src/main/resources/hooks/pre-commit: 6: Syntax error: "(" unexpected
Error: Unexpected error: buildSrc/src/main/resources/hooks/pre-commit: 6: Syntax error: "(" unexpected
```
### Steps to reproduce
check the log above
### Additional context
_No response_
### Hedera network
other
### Version
v0.71.0-SNAPSHOT
### Operating system
None
|
1.0
|
pre-commit hook fails in github workflow - ### Description
The new git pre-commit hook fails in github workflow release automation job `Create PR`'s `Create Pull Reques` step:
```
buildSrc/src/main/resources/hooks/pre-commit: 6: Syntax error: "(" unexpected
Error: Unexpected error: buildSrc/src/main/resources/hooks/pre-commit: 6: Syntax error: "(" unexpected
```
### Steps to reproduce
check the log above
### Additional context
_No response_
### Hedera network
other
### Version
v0.71.0-SNAPSHOT
### Operating system
None
|
process
|
pre commit hook fails in github workflow description the new git pre commit hook fails in github workflow release automation job create pr s create pull reques step buildsrc src main resources hooks pre commit syntax error unexpected error unexpected error buildsrc src main resources hooks pre commit syntax error unexpected steps to reproduce check the log above additional context no response hedera network other version snapshot operating system none
| 1
|
10,929
| 13,731,409,696
|
IssuesEvent
|
2020-10-05 00:54:28
|
SethSterling/CPW215JoesWebsiteSpeakingBits
|
https://api.github.com/repos/SethSterling/CPW215JoesWebsiteSpeakingBits
|
closed
|
Set up continuous integrations with GitHub Actions
|
dev process
|
GitHub actions should be used to build the project on each commit.
|
1.0
|
Set up continuous integrations with GitHub Actions - GitHub actions should be used to build the project on each commit.
|
process
|
set up continuous integrations with github actions github actions should be used to build the project on each commit
| 1
|
817,295
| 30,635,999,796
|
IssuesEvent
|
2023-07-24 17:48:51
|
enzliguor/PokemonAO
|
https://api.github.com/repos/enzliguor/PokemonAO
|
closed
|
Implementare il recupero delle Moves dall'API Pokemon
|
high priority back-end refactor
|
Il progetto PokémonAO deve implementare la funzionalità di recuperare le moves Pokémon dall'API di pokeapi.co.
Tuttavia, dobbiamo gestire correttamente la proprietà del numero massimo di mosse conosciute, che sarà specificato in una property countMoves nel file customProperties.yaml.
Obbiettivi:
- [x] Aggiugere al file customProperties.yaml la property countMoves.
- [x] Aggiornare i metodi di elaborazione delle risposte dell'API per gestire correttamente la risposta e combinare i risultati in modo coerente.
- [x] Aggiornare il codice per recuperare le moves da pokeapi.co, limitando la richiesta in base al valore della property
countMoves e facendo in modo di avere ripartite il numero di Moves tra i vari Type (cioè per ogni type dovremo avere disponibili delle mosse) .
- [x] Salvare sul DB le moves ottenute
|
1.0
|
Implementare il recupero delle Moves dall'API Pokemon - Il progetto PokémonAO deve implementare la funzionalità di recuperare le moves Pokémon dall'API di pokeapi.co.
Tuttavia, dobbiamo gestire correttamente la proprietà del numero massimo di mosse conosciute, che sarà specificato in una property countMoves nel file customProperties.yaml.
Obbiettivi:
- [x] Aggiugere al file customProperties.yaml la property countMoves.
- [x] Aggiornare i metodi di elaborazione delle risposte dell'API per gestire correttamente la risposta e combinare i risultati in modo coerente.
- [x] Aggiornare il codice per recuperare le moves da pokeapi.co, limitando la richiesta in base al valore della property
countMoves e facendo in modo di avere ripartite il numero di Moves tra i vari Type (cioè per ogni type dovremo avere disponibili delle mosse) .
- [x] Salvare sul DB le moves ottenute
|
non_process
|
implementare il recupero delle moves dall api pokemon il progetto pokémonao deve implementare la funzionalità di recuperare le moves pokémon dall api di pokeapi co tuttavia dobbiamo gestire correttamente la proprietà del numero massimo di mosse conosciute che sarà specificato in una property countmoves nel file customproperties yaml obbiettivi aggiugere al file customproperties yaml la property countmoves aggiornare i metodi di elaborazione delle risposte dell api per gestire correttamente la risposta e combinare i risultati in modo coerente aggiornare il codice per recuperare le moves da pokeapi co limitando la richiesta in base al valore della property countmoves e facendo in modo di avere ripartite il numero di moves tra i vari type cioè per ogni type dovremo avere disponibili delle mosse salvare sul db le moves ottenute
| 0
|
20,189
| 26,756,841,850
|
IssuesEvent
|
2023-01-31 01:22:54
|
hsmusic/hsmusic-data
|
https://api.github.com/repos/hsmusic/hsmusic-data
|
closed
|
Album addition: Cool and new Volume V
|
scope: fandom type: addition type: involved process what: albums & tracks
|
https://coolandnewwebcomic.bandcamp.com/album/cool-and-new-volume-v
---
- [ ] Determine bonus content
- [ ] Locate YT uploads if any
- [ ] Cross-ref koba/canwc remix list/bandcamp for references
- [x] press E key repeatedly
|
1.0
|
Album addition: Cool and new Volume V - https://coolandnewwebcomic.bandcamp.com/album/cool-and-new-volume-v
---
- [ ] Determine bonus content
- [ ] Locate YT uploads if any
- [ ] Cross-ref koba/canwc remix list/bandcamp for references
- [x] press E key repeatedly
|
process
|
album addition cool and new volume v determine bonus content locate yt uploads if any cross ref koba canwc remix list bandcamp for references press e key repeatedly
| 1
|
256,917
| 27,561,740,371
|
IssuesEvent
|
2023-03-07 22:43:21
|
samqws-marketing/walmartlabs-concord
|
https://api.github.com/repos/samqws-marketing/walmartlabs-concord
|
closed
|
CVE-2020-15522 (Medium) detected in bcprov-jdk15on-1.64.jar, bcprov-ext-jdk15on-1.64.jar - autoclosed
|
security vulnerability
|
## CVE-2020-15522 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>bcprov-jdk15on-1.64.jar</b>, <b>bcprov-ext-jdk15on-1.64.jar</b></p></summary>
<p>
<details><summary><b>bcprov-jdk15on-1.64.jar</b></p></summary>
<p>The Bouncy Castle Crypto package is a Java implementation of cryptographic algorithms. This jar contains JCE provider and lightweight API for the Bouncy Castle Cryptography APIs for Java 5 to Java 11.</p>
<p>Library home page: <a href="https://www.bouncycastle.org/java.html">https://www.bouncycastle.org/java.html</a></p>
<p>Path to dependency file: /k8s/agent-operator/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/bouncycastle/bcprov-jdk15on/1.64/bcprov-jdk15on-1.64.jar</p>
<p>
Dependency Hierarchy:
- bcpkix-jdk15on-1.64.jar (Root Library)
- :x: **bcprov-jdk15on-1.64.jar** (Vulnerable Library)
</details>
<details><summary><b>bcprov-ext-jdk15on-1.64.jar</b></p></summary>
<p>The Bouncy Castle Crypto package is a Java implementation of cryptographic algorithms. This jar contains JCE provider and lightweight API for the Bouncy Castle Cryptography APIs for JDK 1.5 to JDK 11. Note: this package includes the NTRU encryption algorithms.</p>
<p>Library home page: <a href="https://www.bouncycastle.org/java.html">https://www.bouncycastle.org/java.html</a></p>
<p>Path to dependency file: /k8s/agent-operator/pom.xml</p>
<p>Path to vulnerable library: /y/org/bouncycastle/bcprov-ext-jdk15on/1.64/bcprov-ext-jdk15on-1.64.jar</p>
<p>
Dependency Hierarchy:
- :x: **bcprov-ext-jdk15on-1.64.jar** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/samqws-marketing/walmartlabs-concord/commit/b9420f3b9e73a9d381266ece72f7afb756f35a76">b9420f3b9e73a9d381266ece72f7afb756f35a76</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>
Bouncy Castle BC Java before 1.66, BC C# .NET before 1.8.7, BC-FJA before 1.0.1.2, 1.0.2.1, and BC-FNA before 1.0.1.1 have a timing issue within the EC math library that can expose information about the private key when an attacker is able to observe timing information for the generation of multiple deterministic ECDSA signatures.
<p>Publish Date: 2021-05-20
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-15522>CVE-2020-15522</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.9</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: 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-15522">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15522</a></p>
<p>Release Date: 2021-05-20</p>
<p>Fix Resolution (org.bouncycastle:bcprov-jdk15on): 1.66</p>
<p>Direct dependency fix Resolution (org.bouncycastle:bcpkix-jdk15on): 1.66</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
|
True
|
CVE-2020-15522 (Medium) detected in bcprov-jdk15on-1.64.jar, bcprov-ext-jdk15on-1.64.jar - autoclosed - ## CVE-2020-15522 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>bcprov-jdk15on-1.64.jar</b>, <b>bcprov-ext-jdk15on-1.64.jar</b></p></summary>
<p>
<details><summary><b>bcprov-jdk15on-1.64.jar</b></p></summary>
<p>The Bouncy Castle Crypto package is a Java implementation of cryptographic algorithms. This jar contains JCE provider and lightweight API for the Bouncy Castle Cryptography APIs for Java 5 to Java 11.</p>
<p>Library home page: <a href="https://www.bouncycastle.org/java.html">https://www.bouncycastle.org/java.html</a></p>
<p>Path to dependency file: /k8s/agent-operator/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/bouncycastle/bcprov-jdk15on/1.64/bcprov-jdk15on-1.64.jar</p>
<p>
Dependency Hierarchy:
- bcpkix-jdk15on-1.64.jar (Root Library)
- :x: **bcprov-jdk15on-1.64.jar** (Vulnerable Library)
</details>
<details><summary><b>bcprov-ext-jdk15on-1.64.jar</b></p></summary>
<p>The Bouncy Castle Crypto package is a Java implementation of cryptographic algorithms. This jar contains JCE provider and lightweight API for the Bouncy Castle Cryptography APIs for JDK 1.5 to JDK 11. Note: this package includes the NTRU encryption algorithms.</p>
<p>Library home page: <a href="https://www.bouncycastle.org/java.html">https://www.bouncycastle.org/java.html</a></p>
<p>Path to dependency file: /k8s/agent-operator/pom.xml</p>
<p>Path to vulnerable library: /y/org/bouncycastle/bcprov-ext-jdk15on/1.64/bcprov-ext-jdk15on-1.64.jar</p>
<p>
Dependency Hierarchy:
- :x: **bcprov-ext-jdk15on-1.64.jar** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/samqws-marketing/walmartlabs-concord/commit/b9420f3b9e73a9d381266ece72f7afb756f35a76">b9420f3b9e73a9d381266ece72f7afb756f35a76</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>
Bouncy Castle BC Java before 1.66, BC C# .NET before 1.8.7, BC-FJA before 1.0.1.2, 1.0.2.1, and BC-FNA before 1.0.1.1 have a timing issue within the EC math library that can expose information about the private key when an attacker is able to observe timing information for the generation of multiple deterministic ECDSA signatures.
<p>Publish Date: 2021-05-20
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-15522>CVE-2020-15522</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.9</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: 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-15522">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15522</a></p>
<p>Release Date: 2021-05-20</p>
<p>Fix Resolution (org.bouncycastle:bcprov-jdk15on): 1.66</p>
<p>Direct dependency fix Resolution (org.bouncycastle:bcpkix-jdk15on): 1.66</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
|
non_process
|
cve medium detected in bcprov jar bcprov ext jar autoclosed cve medium severity vulnerability vulnerable libraries bcprov jar bcprov ext jar bcprov jar the bouncy castle crypto package is a java implementation of cryptographic algorithms this jar contains jce provider and lightweight api for the bouncy castle cryptography apis for java to java library home page a href path to dependency file agent operator pom xml path to vulnerable library home wss scanner repository org bouncycastle bcprov bcprov jar dependency hierarchy bcpkix jar root library x bcprov jar vulnerable library bcprov ext jar the bouncy castle crypto package is a java implementation of cryptographic algorithms this jar contains jce provider and lightweight api for the bouncy castle cryptography apis for jdk to jdk note this package includes the ntru encryption algorithms library home page a href path to dependency file agent operator pom xml path to vulnerable library y org bouncycastle bcprov ext bcprov ext jar dependency hierarchy x bcprov ext jar vulnerable library found in head commit a href found in base branch master vulnerability details bouncy castle bc java before bc c net before bc fja before and bc fna before have a timing issue within the ec math library that can expose information about the private key when an attacker is able to observe timing information for the generation of multiple deterministic ecdsa signatures publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org bouncycastle bcprov direct dependency fix resolution org bouncycastle bcpkix check this box to open an automated fix pr
| 0
|
174,423
| 21,300,055,677
|
IssuesEvent
|
2022-04-15 01:01:41
|
samqws-marketing/box_mojito
|
https://api.github.com/repos/samqws-marketing/box_mojito
|
opened
|
CVE-2022-22968 (Low) detected in spring-context-5.2.9.RELEASE.jar
|
security vulnerability
|
## CVE-2022-22968 - Low Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-context-5.2.9.RELEASE.jar</b></p></summary>
<p>Spring Context</p>
<p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /test-common/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-context/5.2.9.RELEASE/spring-context-5.2.9.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-context/5.2.9.RELEASE/spring-context-5.2.9.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-context/5.2.9.RELEASE/spring-context-5.2.9.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-context/5.2.9.RELEASE/spring-context-5.2.9.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-context/5.2.9.RELEASE/spring-context-5.2.9.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-context/5.2.9.RELEASE/spring-context-5.2.9.RELEASE.jar</p>
<p>
Dependency Hierarchy:
- spring-hateoas-1.1.2.RELEASE.jar (Root Library)
- :x: **spring-context-5.2.9.RELEASE.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In Spring Framework versions 5.3.0 - 5.3.18, 5.2.0 - 5.2.20, and older unsupported versions, the patterns for disallowedFields on a DataBinder are case sensitive which means a field is not effectively protected unless it is listed with both upper and lower case for the first character of the field, including upper and lower case for the first character of all nested fields within the property path.
<p>Publish Date: 2022-04-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-22968>CVE-2022-22968</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>3.7</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- 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://tanzu.vmware.com/security/cve-2022-22968">https://tanzu.vmware.com/security/cve-2022-22968</a></p>
<p>Release Date: 2022-01-11</p>
<p>Fix Resolution: org.springframework:spring-context:5.2.21,5.3.19</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.springframework","packageName":"spring-context","packageVersion":"5.2.9.RELEASE","packageFilePaths":["/test-common/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"org.springframework.hateoas:spring-hateoas:1.1.2.RELEASE;org.springframework:spring-context:5.2.9.RELEASE","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.springframework:spring-context:5.2.21,5.3.19","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2022-22968","vulnerabilityDetails":"In Spring Framework versions 5.3.0 - 5.3.18, 5.2.0 - 5.2.20, and older unsupported versions, the patterns for disallowedFields on a DataBinder are case sensitive which means a field is not effectively protected unless it is listed with both upper and lower case for the first character of the field, including upper and lower case for the first character of all nested fields within the property path.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-22968","cvss3Severity":"low","cvss3Score":"3.7","cvss3Metrics":{"A":"None","AC":"High","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> -->
|
True
|
CVE-2022-22968 (Low) detected in spring-context-5.2.9.RELEASE.jar - ## CVE-2022-22968 - Low Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-context-5.2.9.RELEASE.jar</b></p></summary>
<p>Spring Context</p>
<p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /test-common/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-context/5.2.9.RELEASE/spring-context-5.2.9.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-context/5.2.9.RELEASE/spring-context-5.2.9.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-context/5.2.9.RELEASE/spring-context-5.2.9.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-context/5.2.9.RELEASE/spring-context-5.2.9.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-context/5.2.9.RELEASE/spring-context-5.2.9.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-context/5.2.9.RELEASE/spring-context-5.2.9.RELEASE.jar</p>
<p>
Dependency Hierarchy:
- spring-hateoas-1.1.2.RELEASE.jar (Root Library)
- :x: **spring-context-5.2.9.RELEASE.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In Spring Framework versions 5.3.0 - 5.3.18, 5.2.0 - 5.2.20, and older unsupported versions, the patterns for disallowedFields on a DataBinder are case sensitive which means a field is not effectively protected unless it is listed with both upper and lower case for the first character of the field, including upper and lower case for the first character of all nested fields within the property path.
<p>Publish Date: 2022-04-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-22968>CVE-2022-22968</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>3.7</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- 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://tanzu.vmware.com/security/cve-2022-22968">https://tanzu.vmware.com/security/cve-2022-22968</a></p>
<p>Release Date: 2022-01-11</p>
<p>Fix Resolution: org.springframework:spring-context:5.2.21,5.3.19</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.springframework","packageName":"spring-context","packageVersion":"5.2.9.RELEASE","packageFilePaths":["/test-common/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"org.springframework.hateoas:spring-hateoas:1.1.2.RELEASE;org.springframework:spring-context:5.2.9.RELEASE","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.springframework:spring-context:5.2.21,5.3.19","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2022-22968","vulnerabilityDetails":"In Spring Framework versions 5.3.0 - 5.3.18, 5.2.0 - 5.2.20, and older unsupported versions, the patterns for disallowedFields on a DataBinder are case sensitive which means a field is not effectively protected unless it is listed with both upper and lower case for the first character of the field, including upper and lower case for the first character of all nested fields within the property path.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-22968","cvss3Severity":"low","cvss3Score":"3.7","cvss3Metrics":{"A":"None","AC":"High","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> -->
|
non_process
|
cve low detected in spring context release jar cve low severity vulnerability vulnerable library spring context release jar spring context library home page a href path to dependency file test common pom xml path to vulnerable library home wss scanner repository org springframework spring context release spring context release jar home wss scanner repository org springframework spring context release spring context release jar home wss scanner repository org springframework spring context release spring context release jar home wss scanner repository org springframework spring context release spring context release jar home wss scanner repository org springframework spring context release spring context release jar home wss scanner repository org springframework spring context release spring context release jar dependency hierarchy spring hateoas release jar root library x spring context release jar vulnerable library found in base branch master vulnerability details in spring framework versions and older unsupported versions the patterns for disallowedfields on a databinder are case sensitive which means a field is not effectively protected unless it is listed with both upper and lower case for the first character of the field including upper and lower case for the first character of all nested fields within the property path publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact none 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 org springframework spring context isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree org springframework hateoas spring hateoas release org springframework spring context release isminimumfixversionavailable true minimumfixversion org springframework spring context isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails in spring framework versions and older unsupported versions the patterns for disallowedfields on a databinder are case sensitive which means a field is not effectively protected unless it is listed with both upper and lower case for the first character of the field including upper and lower case for the first character of all nested fields within the property path vulnerabilityurl
| 0
|
17,319
| 23,138,513,552
|
IssuesEvent
|
2022-07-28 16:10:00
|
ORNL-AMO/AMO-Tools-Desktop
|
https://api.github.com/repos/ORNL-AMO/AMO-Tools-Desktop
|
closed
|
Horizontal scrollbar exists when it shouldn't
|
bug Process Heating Application
|
Pages with horizontal scrollbar: Custom Materials, Settings, User Manuals, About, Feedback, Acknowledgements
The pages are ever so slightly too wide because they all have the "row" class applied to their root element.
|
1.0
|
Horizontal scrollbar exists when it shouldn't - Pages with horizontal scrollbar: Custom Materials, Settings, User Manuals, About, Feedback, Acknowledgements
The pages are ever so slightly too wide because they all have the "row" class applied to their root element.
|
process
|
horizontal scrollbar exists when it shouldn t pages with horizontal scrollbar custom materials settings user manuals about feedback acknowledgements the pages are ever so slightly too wide because they all have the row class applied to their root element
| 1
|
153,177
| 24,083,291,339
|
IssuesEvent
|
2022-09-19 08:41:09
|
baloise-incubator/design-system
|
https://api.github.com/repos/baloise-incubator/design-system
|
closed
|
Select should allow selection by typing #656 old repo
|
🐛 Bug 🧑💻 Technical Design System ⚙️ Functional Issue
|
by @Tiliavir
On bal-selects without typeahead, it should be possible to select options by typing the first letters.
Currently it is only possible to navigate through the list with arrow keys or using the mouse.
On bigger lists, this is a bit tedious.
Hi @LaurentSteiner , Hi @hirsch88
after discussing my initial suggestion with Laurent, I've updated the issue above.
Thanks for your effort
Markus
|
1.0
|
Select should allow selection by typing #656 old repo - by @Tiliavir
On bal-selects without typeahead, it should be possible to select options by typing the first letters.
Currently it is only possible to navigate through the list with arrow keys or using the mouse.
On bigger lists, this is a bit tedious.
Hi @LaurentSteiner , Hi @hirsch88
after discussing my initial suggestion with Laurent, I've updated the issue above.
Thanks for your effort
Markus
|
non_process
|
select should allow selection by typing old repo by tiliavir on bal selects without typeahead it should be possible to select options by typing the first letters currently it is only possible to navigate through the list with arrow keys or using the mouse on bigger lists this is a bit tedious hi laurentsteiner hi after discussing my initial suggestion with laurent i ve updated the issue above thanks for your effort markus
| 0
|
194,865
| 22,273,320,929
|
IssuesEvent
|
2022-06-10 14:17:29
|
RG4421/ampere-centos-kernel
|
https://api.github.com/repos/RG4421/ampere-centos-kernel
|
reopened
|
CVE-2020-15437 (Medium) detected in linuxv5.2
|
security vulnerability
|
## CVE-2020-15437 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxv5.2</b></p></summary>
<p>
<p>Linux kernel source tree</p>
<p>Library home page: <a href=https://github.com/torvalds/linux.git>https://github.com/torvalds/linux.git</a></p>
<p>Found in base branch: <b>amp-centos-8.0-kernel</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 (3)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/tty/serial/8250/8250_core.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/tty/serial/8250/8250_core.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/tty/serial/8250/8250_core.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 Linux kernel before version 5.8 is vulnerable to a NULL pointer dereference in drivers/tty/serial/8250/8250_core.c:serial8250_isa_init_ports() that allows local users to cause a denial of service by using the p->serial_in pointer which uninitialized.
WhiteSource Note: After conducting further research, WhiteSource has determined that versions v3.9-rc5 through v4.4.231, v4.5-rc1 through v4.9.231, v4.10-rc1 through v4.14.189, v4.15-rc1 through v4.19.134, v5.0-rc1 through v5.4.53, v5.5-rc1 through v5.7.10 and v5.8-rc1 through v5.8-rc6 of Linux Kernel are vulnerable to CVE-2020-15437.
<p>Publish Date: 2020-11-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15437>CVE-2020-15437</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>4.4</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: High
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.linuxkernelcves.com/cves/CVE-2020-15437">https://www.linuxkernelcves.com/cves/CVE-2020-15437</a></p>
<p>Release Date: 2020-11-23</p>
<p>Fix Resolution: v4.4.232, v4.9.232, v4.14.190, v4.19.135, v5.4.54, v5.7.11, v5.8-rc7</p>
</p>
</details>
<p></p>
|
True
|
CVE-2020-15437 (Medium) detected in linuxv5.2 - ## CVE-2020-15437 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxv5.2</b></p></summary>
<p>
<p>Linux kernel source tree</p>
<p>Library home page: <a href=https://github.com/torvalds/linux.git>https://github.com/torvalds/linux.git</a></p>
<p>Found in base branch: <b>amp-centos-8.0-kernel</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 (3)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/tty/serial/8250/8250_core.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/tty/serial/8250/8250_core.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/tty/serial/8250/8250_core.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 Linux kernel before version 5.8 is vulnerable to a NULL pointer dereference in drivers/tty/serial/8250/8250_core.c:serial8250_isa_init_ports() that allows local users to cause a denial of service by using the p->serial_in pointer which uninitialized.
WhiteSource Note: After conducting further research, WhiteSource has determined that versions v3.9-rc5 through v4.4.231, v4.5-rc1 through v4.9.231, v4.10-rc1 through v4.14.189, v4.15-rc1 through v4.19.134, v5.0-rc1 through v5.4.53, v5.5-rc1 through v5.7.10 and v5.8-rc1 through v5.8-rc6 of Linux Kernel are vulnerable to CVE-2020-15437.
<p>Publish Date: 2020-11-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15437>CVE-2020-15437</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>4.4</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: High
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.linuxkernelcves.com/cves/CVE-2020-15437">https://www.linuxkernelcves.com/cves/CVE-2020-15437</a></p>
<p>Release Date: 2020-11-23</p>
<p>Fix Resolution: v4.4.232, v4.9.232, v4.14.190, v4.19.135, v5.4.54, v5.7.11, v5.8-rc7</p>
</p>
</details>
<p></p>
|
non_process
|
cve medium detected in cve medium severity vulnerability vulnerable library linux kernel source tree library home page a href found in base branch amp centos kernel vulnerable source files drivers tty serial core c drivers tty serial core c drivers tty serial core c vulnerability details the linux kernel before version is vulnerable to a null pointer dereference in drivers tty serial core c isa init ports that allows local users to cause a denial of service by using the p serial in pointer which uninitialized whitesource note after conducting further research whitesource has determined that versions through through through through through through and through of linux kernel are vulnerable to cve publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required high 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
| 0
|
10,602
| 13,429,344,719
|
IssuesEvent
|
2020-09-07 01:32:10
|
rdoddanavar/hpr-sim
|
https://api.github.com/repos/rdoddanavar/hpr-sim
|
opened
|
Input: Error Handling
|
logging & errors pre-processing
|
Error handling against check_value() and check_path(); consider moving routines to python away from C++ member functions
|
1.0
|
Input: Error Handling - Error handling against check_value() and check_path(); consider moving routines to python away from C++ member functions
|
process
|
input error handling error handling against check value and check path consider moving routines to python away from c member functions
| 1
|
10,419
| 13,210,737,079
|
IssuesEvent
|
2020-08-15 18:33:48
|
km4ack/patmenu2
|
https://api.github.com/repos/km4ack/patmenu2
|
closed
|
add manual grid update option
|
enhancement in process
|
In addition to the GPS update in the Manage Pat section, include an option where the user could type in the grid manually.
|
1.0
|
add manual grid update option - In addition to the GPS update in the Manage Pat section, include an option where the user could type in the grid manually.
|
process
|
add manual grid update option in addition to the gps update in the manage pat section include an option where the user could type in the grid manually
| 1
|
3,177
| 6,246,138,850
|
IssuesEvent
|
2017-07-13 02:41:02
|
nodejs/node
|
https://api.github.com/repos/nodejs/node
|
closed
|
child_process.spawnSync() not return anything.
|
child_process question windows
|
* **Version**: 6.11.0 or 6.11.1
* **Platform**: Win10 Pro latest stable
* **Subsystem**:
**In my company's computer：**
`let result = childProcess.spawnSync('D:/Program Files/nodejs/node.exe', ['--version']);` work very well, can get return value.
but `let result = childProcess.spawnSync('node', ['--version']);` not work and the code behind it will not execute.
**I use myself computer：**
`let result = childProcess.spawnSync('node', ['--version']);` was work very well.
I have added 'D:\Program Files\nodejs\' to the environment variable.
This problem caused my vscode editor to not work properly. see[#45048199](https://stackoverflow.com/questions/45047450/in-the-child-process-module-in-node-js/45048199#)
|
1.0
|
child_process.spawnSync() not return anything. - * **Version**: 6.11.0 or 6.11.1
* **Platform**: Win10 Pro latest stable
* **Subsystem**:
**In my company's computer：**
`let result = childProcess.spawnSync('D:/Program Files/nodejs/node.exe', ['--version']);` work very well, can get return value.
but `let result = childProcess.spawnSync('node', ['--version']);` not work and the code behind it will not execute.
**I use myself computer：**
`let result = childProcess.spawnSync('node', ['--version']);` was work very well.
I have added 'D:\Program Files\nodejs\' to the environment variable.
This problem caused my vscode editor to not work properly. see[#45048199](https://stackoverflow.com/questions/45047450/in-the-child-process-module-in-node-js/45048199#)
|
process
|
child process spawnsync not return anything version or platform pro latest stable subsystem in my company s computer： let result childprocess spawnsync d program files nodejs node exe work very well can get return value but let result childprocess spawnsync node not work and the code behind it will not execute i use myself computer： let result childprocess spawnsync node was work very well i have added d program files nodejs to the environment variable this problem caused my vscode editor to not work properly see
| 1
|
6,250
| 9,210,542,731
|
IssuesEvent
|
2019-03-09 06:26:59
|
depthlove/depthlove.github.io
|
https://api.github.com/repos/depthlove/depthlove.github.io
|
closed
|
移动端直播应用的开发流程 | Minmin.Sun Blog
|
/2016/05/09/live-broadcast-development-process/ Gitalk
|
https://depthlove.github.io/2016/05/09/live-broadcast-development-process/
Part 1. 推流端推流，就是将采集到的音频，视频数据通过流媒体协议发送到流媒体服务器。 一、选择流媒体协议现在直播应用，采用 RTMP 协议居多，也有部分使用 HLS 协议。 采用RTMP协议，就要看下它与流媒体服务器交互的过程，RTMP协议的默认端口是1935，采用 TCP 协议。并且需要了解 FLV 的封装格式。 采用 HLS 协议，因为涉及到切片，延时会比较大，需要了解 TS 流。
|
1.0
|
移动端直播应用的开发流程 | Minmin.Sun Blog - https://depthlove.github.io/2016/05/09/live-broadcast-development-process/
Part 1. 推流端推流，就是将采集到的音频，视频数据通过流媒体协议发送到流媒体服务器。 一、选择流媒体协议现在直播应用，采用 RTMP 协议居多，也有部分使用 HLS 协议。 采用RTMP协议，就要看下它与流媒体服务器交互的过程，RTMP协议的默认端口是1935，采用 TCP 协议。并且需要了解 FLV 的封装格式。 采用 HLS 协议，因为涉及到切片，延时会比较大，需要了解 TS 流。
|
process
|
移动端直播应用的开发流程 minmin sun blog part 推流端推流，就是将采集到的音频，视频数据通过流媒体协议发送到流媒体服务器。 一、选择流媒体协议现在直播应用，采用 rtmp 协议居多，也有部分使用 hls 协议。 采用rtmp协议，就要看下它与流媒体服务器交互的过程， ，采用 tcp 协议。并且需要了解 flv 的封装格式。 采用 hls 协议，因为涉及到切片，延时会比较大，需要了解 ts 流。
| 1
|
100,815
| 11,205,262,404
|
IssuesEvent
|
2020-01-05 13:04:56
|
Shakesbeard/com.sdn.lifx-lan2
|
https://api.github.com/repos/Shakesbeard/com.sdn.lifx-lan2
|
closed
|
random color issues
|
documentation not a bug
|
I found a minor issue if I set it to give it a random color it will remain unchanged
|
1.0
|
random color issues - I found a minor issue if I set it to give it a random color it will remain unchanged
|
non_process
|
random color issues i found a minor issue if i set it to give it a random color it will remain unchanged
| 0
|
3,102
| 6,110,954,350
|
IssuesEvent
|
2017-06-21 15:58:51
|
CredentialEngine/vocabularies
|
https://api.github.com/repos/CredentialEngine/vocabularies
|
closed
|
Determine whether additional Process-related properties are needed
|
History (Term Addition) New Term Proposal Pending Process Profile Quality Assurance Related
|
This Google sheet identified the QA related properties https://docs.google.com/document/d/13td5-K4uYrfInkX2mpxeO-XpN9mFIraoe8NSciv7f58/edit?usp=sharing
These potential properties are based on quality assurance organization information. The editor has been setup to use the ceterms:ProcessProfile for each of the following. These are the properties we will explore adding. As part of a determination, feedback will be garnered from the Credential Engine Quality Assurance Advisory Group.
Create ceterms:reviewProcess
Label: Review Process
Definition: A profile of the process by which the resource being described, or aspects of it, are reviewed.
Domain: ceterms:Credential, ceterms:CredentialOrganization, ceterms:QACredentialOrganization
Range: ceterms:ProcessProfile
Create ceterms:revocationProcess
Label: Revocation Process
Definition: A profile of the process by which the resource being described, or aspects of it, are revoked.
Domain: ceterms:Credential, ceterms:CredentialOrganization, ceterms:QACredentialOrganization
Range: ceterms:ProcessProfile
Create ceterms:appealProcess
Label: Appeal Process
Definition: A profile of the process by which the resource being described, or aspects of it, are appealed.
Domain: ceterms:Credential, ceterms:CredentialOrganization, ceterms:QACredentialOrganization
Range: ceterms:ProcessProfile
Create ceterms:complaintProcess
Label: Complaint Process
Definition: A profile of the process by which complaints about the resource being described, or aspects of it, are handled.
Domains: ceterms:Credential, ceterms:CredentialOrganization, ceterms:QACredentialOrganization
Range: ceterms:ProcessProfile
|
1.0
|
Determine whether additional Process-related properties are needed - This Google sheet identified the QA related properties https://docs.google.com/document/d/13td5-K4uYrfInkX2mpxeO-XpN9mFIraoe8NSciv7f58/edit?usp=sharing
These potential properties are based on quality assurance organization information. The editor has been setup to use the ceterms:ProcessProfile for each of the following. These are the properties we will explore adding. As part of a determination, feedback will be garnered from the Credential Engine Quality Assurance Advisory Group.
Create ceterms:reviewProcess
Label: Review Process
Definition: A profile of the process by which the resource being described, or aspects of it, are reviewed.
Domain: ceterms:Credential, ceterms:CredentialOrganization, ceterms:QACredentialOrganization
Range: ceterms:ProcessProfile
Create ceterms:revocationProcess
Label: Revocation Process
Definition: A profile of the process by which the resource being described, or aspects of it, are revoked.
Domain: ceterms:Credential, ceterms:CredentialOrganization, ceterms:QACredentialOrganization
Range: ceterms:ProcessProfile
Create ceterms:appealProcess
Label: Appeal Process
Definition: A profile of the process by which the resource being described, or aspects of it, are appealed.
Domain: ceterms:Credential, ceterms:CredentialOrganization, ceterms:QACredentialOrganization
Range: ceterms:ProcessProfile
Create ceterms:complaintProcess
Label: Complaint Process
Definition: A profile of the process by which complaints about the resource being described, or aspects of it, are handled.
Domains: ceterms:Credential, ceterms:CredentialOrganization, ceterms:QACredentialOrganization
Range: ceterms:ProcessProfile
|
process
|
determine whether additional process related properties are needed this google sheet identified the qa related properties these potential properties are based on quality assurance organization information the editor has been setup to use the ceterms processprofile for each of the following these are the properties we will explore adding as part of a determination feedback will be garnered from the credential engine quality assurance advisory group create ceterms reviewprocess label review process definition a profile of the process by which the resource being described or aspects of it are reviewed domain ceterms credential ceterms credentialorganization ceterms qacredentialorganization range ceterms processprofile create ceterms revocationprocess label revocation process definition a profile of the process by which the resource being described or aspects of it are revoked domain ceterms credential ceterms credentialorganization ceterms qacredentialorganization range ceterms processprofile create ceterms appealprocess label appeal process definition a profile of the process by which the resource being described or aspects of it are appealed domain ceterms credential ceterms credentialorganization ceterms qacredentialorganization range ceterms processprofile create ceterms complaintprocess label complaint process definition a profile of the process by which complaints about the resource being described or aspects of it are handled domains ceterms credential ceterms credentialorganization ceterms qacredentialorganization range ceterms processprofile
| 1
|
20,087
| 26,595,252,146
|
IssuesEvent
|
2023-01-23 11:58:57
|
NixOS/nix
|
https://api.github.com/repos/NixOS/nix
|
opened
|
Label approved ideas to attract contributions
|
process
|
**Is your feature request related to a problem? Please describe.**
It's hard for contributors to work on things that they don't feel are completely necessary.
Hence, if I may fail to characterize contributions in a respectful way, they tend to be "obvious" things, such as fixes, or "passion projects" that people just feel like writing. These are valid contributions, but don't always lead to the project's higher level goals.
So what I'm suggesting is that there's a class of contributions that we're missing out on, because some ideas that *we* know are good, may not be obvious to contributors, even though they would be willing to help out with them.
**Describe the solution you'd like**
- Tag issues with labels such as "help wanted" or "idea approved".
- Suggest implementation strategies for such issues
**Describe alternatives you've considered**
Carry on and allow development to be bottlenecked by the Nix team.
**Additional context**
Add any other context or screenshots about the feature request here.
**Priorities**
Add :+1: to [issues you find important](https://github.com/NixOS/nix/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc).
|
1.0
|
Label approved ideas to attract contributions - **Is your feature request related to a problem? Please describe.**
It's hard for contributors to work on things that they don't feel are completely necessary.
Hence, if I may fail to characterize contributions in a respectful way, they tend to be "obvious" things, such as fixes, or "passion projects" that people just feel like writing. These are valid contributions, but don't always lead to the project's higher level goals.
So what I'm suggesting is that there's a class of contributions that we're missing out on, because some ideas that *we* know are good, may not be obvious to contributors, even though they would be willing to help out with them.
**Describe the solution you'd like**
- Tag issues with labels such as "help wanted" or "idea approved".
- Suggest implementation strategies for such issues
**Describe alternatives you've considered**
Carry on and allow development to be bottlenecked by the Nix team.
**Additional context**
Add any other context or screenshots about the feature request here.
**Priorities**
Add :+1: to [issues you find important](https://github.com/NixOS/nix/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc).
|
process
|
label approved ideas to attract contributions is your feature request related to a problem please describe it s hard for contributors to work on things that they don t feel are completely necessary hence if i may fail to characterize contributions in a respectful way they tend to be obvious things such as fixes or passion projects that people just feel like writing these are valid contributions but don t always lead to the project s higher level goals so what i m suggesting is that there s a class of contributions that we re missing out on because some ideas that we know are good may not be obvious to contributors even though they would be willing to help out with them describe the solution you d like tag issues with labels such as help wanted or idea approved suggest implementation strategies for such issues describe alternatives you ve considered carry on and allow development to be bottlenecked by the nix team additional context add any other context or screenshots about the feature request here priorities add to
| 1
|
21,817
| 30,316,641,128
|
IssuesEvent
|
2023-07-10 16:00:29
|
tdwg/dwc
|
https://api.github.com/repos/tdwg/dwc
|
closed
|
Change term - organismQuantity
|
Term - change Class - Occurrence non-normative Process - complete
|
## Term change
* Submitter: John Wieczorek (credit to Peter Desmet for noticing)
* Efficacy Justification (why is this change necessary?): Consistency (see accompanying changes in examples in #424)
* Demand Justification (if the change is semantic in nature, name at least two organizations that independently need this term): Not a semantic change
* Stability Justification (what concerns are there that this might affect existing implementations?): None
* Implications for dwciri: namespace (does this change affect a dwciri term version)?: None
Current Term definition: https://dwc.tdwg.org/terms/#dwc:organismQuantity
Proposed attributes of the new term version (Please put actual changes to be implemented in **bold** and ~strikethrough~):
* Term name (in lowerCamelCase for properties, UpperCamelCase for classes): organismQuantity
* Organized in Class (e.g., Occurrence, Event, Location, Taxon): Occurrence
* Definition of the term (normative): "A number or enumeration value for the quantity of organisms."
* Usage comments (recommendations regarding content, etc., not normative): "An organismQuantity must have a corresponding organismQuantityType."
* Examples (not normative): "`27` (organismQuantity) with `individuals` (organismQuantityType). `12.5` (organismQuantity) with `% biomass` (organismQuantityType). `r` (organismQuantity) with ~Braun Blanquet Scale~ **`Braun-Blanquet scale`** (organismQuantityType). `many` (organismQuantity) with `individuals` (organismQuantityType)."
* Refines (identifier of the broader term this term refines; normative): None
* Replaces (identifier of the existing term that would be deprecated and replaced by this term; normative): http://rs.tdwg.org/dwc/terms/version/organismQuantity-2021-07-15
* ABCD 2.06 (XPATH of the equivalent term in ABCD or EFG; not normative): "not in ABCD"
|
1.0
|
Change term - organismQuantity - ## Term change
* Submitter: John Wieczorek (credit to Peter Desmet for noticing)
* Efficacy Justification (why is this change necessary?): Consistency (see accompanying changes in examples in #424)
* Demand Justification (if the change is semantic in nature, name at least two organizations that independently need this term): Not a semantic change
* Stability Justification (what concerns are there that this might affect existing implementations?): None
* Implications for dwciri: namespace (does this change affect a dwciri term version)?: None
Current Term definition: https://dwc.tdwg.org/terms/#dwc:organismQuantity
Proposed attributes of the new term version (Please put actual changes to be implemented in **bold** and ~strikethrough~):
* Term name (in lowerCamelCase for properties, UpperCamelCase for classes): organismQuantity
* Organized in Class (e.g., Occurrence, Event, Location, Taxon): Occurrence
* Definition of the term (normative): "A number or enumeration value for the quantity of organisms."
* Usage comments (recommendations regarding content, etc., not normative): "An organismQuantity must have a corresponding organismQuantityType."
* Examples (not normative): "`27` (organismQuantity) with `individuals` (organismQuantityType). `12.5` (organismQuantity) with `% biomass` (organismQuantityType). `r` (organismQuantity) with ~Braun Blanquet Scale~ **`Braun-Blanquet scale`** (organismQuantityType). `many` (organismQuantity) with `individuals` (organismQuantityType)."
* Refines (identifier of the broader term this term refines; normative): None
* Replaces (identifier of the existing term that would be deprecated and replaced by this term; normative): http://rs.tdwg.org/dwc/terms/version/organismQuantity-2021-07-15
* ABCD 2.06 (XPATH of the equivalent term in ABCD or EFG; not normative): "not in ABCD"
|
process
|
change term organismquantity term change submitter john wieczorek credit to peter desmet for noticing efficacy justification why is this change necessary consistency see accompanying changes in examples in demand justification if the change is semantic in nature name at least two organizations that independently need this term not a semantic change stability justification what concerns are there that this might affect existing implementations none implications for dwciri namespace does this change affect a dwciri term version none current term definition proposed attributes of the new term version please put actual changes to be implemented in bold and strikethrough term name in lowercamelcase for properties uppercamelcase for classes organismquantity organized in class e g occurrence event location taxon occurrence definition of the term normative a number or enumeration value for the quantity of organisms usage comments recommendations regarding content etc not normative an organismquantity must have a corresponding organismquantitytype examples not normative organismquantity with individuals organismquantitytype organismquantity with biomass organismquantitytype r organismquantity with braun blanquet scale braun blanquet scale organismquantitytype many organismquantity with individuals organismquantitytype refines identifier of the broader term this term refines normative none replaces identifier of the existing term that would be deprecated and replaced by this term normative abcd xpath of the equivalent term in abcd or efg not normative not in abcd
| 1
|
14,751
| 18,021,660,222
|
IssuesEvent
|
2021-09-16 20:17:23
|
MicrosoftDocs/azure-devops-docs
|
https://api.github.com/repos/MicrosoftDocs/azure-devops-docs
|
closed
|
"Members of this role can use the environment when authoring yaml pipelines"?
|
doc-enhancement devops/prod devops-cicd-process/tech
|
Can you elaborate more on this sentence "Members of this role can use the environment when authoring yaml pipelines."
What does "authoring yaml pipelines" exactly mean? It means users with "User" role of the target environment can run the pipeline to the stage containing deployment job of this environment or just means users can choose what stage to run when manually triggering the pipeline?
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 77d95db6-9983-7346-d0eb-4b7443e4e252
* Version Independent ID: 0a22cccc-318d-592f-d1ab-09ec01d88087
* Content: [Create target environment - Azure Pipelines](https://docs.microsoft.com/en-us/azure/devops/pipelines/process/environments?view=azure-devops)
* Content Source: [docs/pipelines/process/environments.md](https://github.com/MicrosoftDocs/azure-devops-docs/blob/master/docs/pipelines/process/environments.md)
* Product: **devops**
* Technology: **devops-cicd-process**
* GitHub Login: @juliakm
* Microsoft Alias: **jukullam**
|
1.0
|
"Members of this role can use the environment when authoring yaml pipelines"? - Can you elaborate more on this sentence "Members of this role can use the environment when authoring yaml pipelines."
What does "authoring yaml pipelines" exactly mean? It means users with "User" role of the target environment can run the pipeline to the stage containing deployment job of this environment or just means users can choose what stage to run when manually triggering the pipeline?
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 77d95db6-9983-7346-d0eb-4b7443e4e252
* Version Independent ID: 0a22cccc-318d-592f-d1ab-09ec01d88087
* Content: [Create target environment - Azure Pipelines](https://docs.microsoft.com/en-us/azure/devops/pipelines/process/environments?view=azure-devops)
* Content Source: [docs/pipelines/process/environments.md](https://github.com/MicrosoftDocs/azure-devops-docs/blob/master/docs/pipelines/process/environments.md)
* Product: **devops**
* Technology: **devops-cicd-process**
* GitHub Login: @juliakm
* Microsoft Alias: **jukullam**
|
process
|
members of this role can use the environment when authoring yaml pipelines can you elaborate more on this sentence members of this role can use the environment when authoring yaml pipelines what does authoring yaml pipelines exactly mean it means users with user role of the target environment can run the pipeline to the stage containing deployment job of this environment or just means users can choose what stage to run when manually triggering the pipeline document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source product devops technology devops cicd process github login juliakm microsoft alias jukullam
| 1
|
304,433
| 26,276,148,255
|
IssuesEvent
|
2023-01-06 22:16:27
|
jsonschema2dataclass/js2d-gradle
|
https://api.github.com/repos/jsonschema2dataclass/js2d-gradle
|
closed
|
Can't read json schemas from classpath
|
enhancement help wanted java test dsl
|
Suppose i have a schema with definitions in jar and I want to generate classes from a schema that uses those definitions.
That doesn't seem to work with gradle plugin (this or the deprecated one), but it works fine in maven.
[test.zip](https://github.com/eirnym/js2p-gradle/files/5708267/test.zip)
|
1.0
|
Can't read json schemas from classpath - Suppose i have a schema with definitions in jar and I want to generate classes from a schema that uses those definitions.
That doesn't seem to work with gradle plugin (this or the deprecated one), but it works fine in maven.
[test.zip](https://github.com/eirnym/js2p-gradle/files/5708267/test.zip)
|
non_process
|
can t read json schemas from classpath suppose i have a schema with definitions in jar and i want to generate classes from a schema that uses those definitions that doesn t seem to work with gradle plugin this or the deprecated one but it works fine in maven
| 0
|
6,800
| 9,940,094,676
|
IssuesEvent
|
2019-07-03 08:24:13
|
aiidateam/aiida_core
|
https://api.github.com/repos/aiidateam/aiida_core
|
opened
|
Results of cached process function is not stored
|
priority/important topic/caching topic/engine topic/processes type/bug
|
Reproducible by the following:
```
#!/usr/bin/env runaiida
from aiida import orm
from aiida.engine import calcfunction
from aiida.manage.caching import enable_caching
@calcfunction
def add(x, y):
return x + y
x = orm.Int(1)
y = orm.Int(2)
result, node = add.run_get_node(x, y)
with enable_caching():
result_cached, node_cached = add.run_get_node(x, y)
assert result_cached.is_stored is True
```
|
1.0
|
Results of cached process function is not stored - Reproducible by the following:
```
#!/usr/bin/env runaiida
from aiida import orm
from aiida.engine import calcfunction
from aiida.manage.caching import enable_caching
@calcfunction
def add(x, y):
return x + y
x = orm.Int(1)
y = orm.Int(2)
result, node = add.run_get_node(x, y)
with enable_caching():
result_cached, node_cached = add.run_get_node(x, y)
assert result_cached.is_stored is True
```
|
process
|
results of cached process function is not stored reproducible by the following usr bin env runaiida from aiida import orm from aiida engine import calcfunction from aiida manage caching import enable caching calcfunction def add x y return x y x orm int y orm int result node add run get node x y with enable caching result cached node cached add run get node x y assert result cached is stored is true
| 1
|
60,673
| 8,453,885,085
|
IssuesEvent
|
2018-10-20 20:01:24
|
donmccurdy/three-pathfinding
|
https://api.github.com/repos/donmccurdy/three-pathfinding
|
closed
|
Installation documentation
|
documentation
|
#Sorry, nodejs is a mystery to me, I cannot figure it out from the docs how to run this thing. After reading external docs (sad it's not in your docs) I went this far:
```
cd three-pathfinding
npm i --save three
npm i --save three-gltf-loader
```
then I create x.js script:
```js
let mesh;
var loader = new THREE.GLTFLoader();
loader.load( 'navmesh.gltf', ({scene}) => {
scene.traverse((node) => {
if (node.isMesh) mesh = node;
});
}, undefined, (e) => {
console.error(e);
});
```
`nodejs x.js: ReferenceError: THREE is not defined`
So I try with this line first:
```js
var THREE = require('three')
```
which results in:
```
var loader = new THREE.GLTFLoader();
// TypeError: THREE.GLTFLoader is not a constructor
```
So I google around for "npm GLTFLoader()" and find things which don't work
```
import GLTF2Loader from 'three-gltf-loader'
```
Can you provide the description for the nodejs beginners like me?
|
1.0
|
Installation documentation - #Sorry, nodejs is a mystery to me, I cannot figure it out from the docs how to run this thing. After reading external docs (sad it's not in your docs) I went this far:
```
cd three-pathfinding
npm i --save three
npm i --save three-gltf-loader
```
then I create x.js script:
```js
let mesh;
var loader = new THREE.GLTFLoader();
loader.load( 'navmesh.gltf', ({scene}) => {
scene.traverse((node) => {
if (node.isMesh) mesh = node;
});
}, undefined, (e) => {
console.error(e);
});
```
`nodejs x.js: ReferenceError: THREE is not defined`
So I try with this line first:
```js
var THREE = require('three')
```
which results in:
```
var loader = new THREE.GLTFLoader();
// TypeError: THREE.GLTFLoader is not a constructor
```
So I google around for "npm GLTFLoader()" and find things which don't work
```
import GLTF2Loader from 'three-gltf-loader'
```
Can you provide the description for the nodejs beginners like me?
|
non_process
|
installation documentation sorry nodejs is a mystery to me i cannot figure it out from the docs how to run this thing after reading external docs sad it s not in your docs i went this far cd three pathfinding npm i save three npm i save three gltf loader then i create x js script js let mesh var loader new three gltfloader loader load navmesh gltf scene scene traverse node if node ismesh mesh node undefined e console error e nodejs x js referenceerror three is not defined so i try with this line first js var three require three which results in var loader new three gltfloader typeerror three gltfloader is not a constructor so i google around for npm gltfloader and find things which don t work import from three gltf loader can you provide the description for the nodejs beginners like me
| 0
|
47,144
| 5,858,449,892
|
IssuesEvent
|
2017-05-12 04:08:50
|
FireFly-WoW/FireFly-IssueTracker
|
https://api.github.com/repos/FireFly-WoW/FireFly-IssueTracker
|
closed
|
Log in & Relog issue
|
Priority: Medium Status: Needs Testing Target: Core
|
**Description:**
After you disconnect due to afk or proper log-out you get teleported from you last known position to position where your HS is set!
|
1.0
|
Log in & Relog issue - **Description:**
After you disconnect due to afk or proper log-out you get teleported from you last known position to position where your HS is set!
|
non_process
|
log in relog issue description after you disconnect due to afk or proper log out you get teleported from you last known position to position where your hs is set
| 0
|
828,964
| 31,849,160,626
|
IssuesEvent
|
2023-09-14 23:03:06
|
PardeeCenterDU/IFs-Issues-Tracking
|
https://api.github.com/repos/PardeeCenterDU/IFs-Issues-Tracking
|
closed
|
Bilateral Display Crash When Using Comparison Options
|
Blowup Display Issues New Issue / Not Under Review Priority 2 Bilateral Interaction\Influence in IFs
|
Bilateral Display Crash When Using Comparison Options
IFs 8.04+ Development
To reproduce:
1. Open bilateral display
2. Select forecast variables and scenario for display
3. Open
4. Select comparison option
5. Exit table to main display
6. Reopen, check comparison options
7. Disable comparison option
8. Crash
> The following error occurred:
>
> Exception of type 'System.Web.HttpUnhandledException' was thrown.
> System.IndexOutOfRangeException: Index was outside the bounds of the array.
> at System.Array.InternalGetReference(Void* elemRef, Int32 rank, Int32* pIndices)
> at System.Array.GetValue(Int32 index1, Int32 index2)
> at Microsoft.VisualBasic.CompilerServices.Symbols.Container.GetArrayValue(Object[] Indices)
> at Microsoft.VisualBasic.CompilerServices.NewLateBinding.InternalLateIndexGet(Object Instance, Object[] Arguments, String[] ArgumentNames, Boolean ReportErrors, ResolutionFailure& Failure, Boolean[] CopyBack)
> at Microsoft.VisualBasic.CompilerServices.NewLateBinding.ObjectLateInvokeDefault(Object Instance, Object[] Arguments, String[] ArgumentNames, Boolean ReportErrors, Boolean[] CopyBack)
> at Microsoft.VisualBasic.CompilerServices.NewLateBinding.InternalLateInvokeDefault(Object Instance, Object[] Arguments, String[] ArgumentNames, Boolean ReportErrors, Boolean[] CopyBack)
> at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateIndexGet(Object Instance, Object[] Arguments, String[] ArgumentNames)
> at IFsWeb.frm_BilateralInteractionDisplay.LoadGrid() in C:\Users\Public\IFs\IFsWeb\frm_BilateralInteractionDisplay.aspx.vb:line 752
> at IFsWeb.frm_BilateralInteractionDisplay.mnuCompReset_Click() in C:\Users\Public\IFs\IFsWeb\frm_BilateralInteractionDisplay.aspx.vb:line 1041
> at IFsWeb.frm_BilateralInteractionDisplay.ItemClickHandler(Object sender, EventArgs e) in C:\Users\Public\IFs\IFsWeb\frm_BilateralInteractionDisplay.aspx.vb:line 977
> at Coalesys.WebMenu.WebMenu.OnServerItemClick(ServerItemClickEventArgs eventArgs)
> at Coalesys.WebMenu.WebMenu.RaisePostBackEvent(String eventArgument)
> at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
> at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
> at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
|
1.0
|
Bilateral Display Crash When Using Comparison Options - Bilateral Display Crash When Using Comparison Options
IFs 8.04+ Development
To reproduce:
1. Open bilateral display
2. Select forecast variables and scenario for display
3. Open
4. Select comparison option
5. Exit table to main display
6. Reopen, check comparison options
7. Disable comparison option
8. Crash
> The following error occurred:
>
> Exception of type 'System.Web.HttpUnhandledException' was thrown.
> System.IndexOutOfRangeException: Index was outside the bounds of the array.
> at System.Array.InternalGetReference(Void* elemRef, Int32 rank, Int32* pIndices)
> at System.Array.GetValue(Int32 index1, Int32 index2)
> at Microsoft.VisualBasic.CompilerServices.Symbols.Container.GetArrayValue(Object[] Indices)
> at Microsoft.VisualBasic.CompilerServices.NewLateBinding.InternalLateIndexGet(Object Instance, Object[] Arguments, String[] ArgumentNames, Boolean ReportErrors, ResolutionFailure& Failure, Boolean[] CopyBack)
> at Microsoft.VisualBasic.CompilerServices.NewLateBinding.ObjectLateInvokeDefault(Object Instance, Object[] Arguments, String[] ArgumentNames, Boolean ReportErrors, Boolean[] CopyBack)
> at Microsoft.VisualBasic.CompilerServices.NewLateBinding.InternalLateInvokeDefault(Object Instance, Object[] Arguments, String[] ArgumentNames, Boolean ReportErrors, Boolean[] CopyBack)
> at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateIndexGet(Object Instance, Object[] Arguments, String[] ArgumentNames)
> at IFsWeb.frm_BilateralInteractionDisplay.LoadGrid() in C:\Users\Public\IFs\IFsWeb\frm_BilateralInteractionDisplay.aspx.vb:line 752
> at IFsWeb.frm_BilateralInteractionDisplay.mnuCompReset_Click() in C:\Users\Public\IFs\IFsWeb\frm_BilateralInteractionDisplay.aspx.vb:line 1041
> at IFsWeb.frm_BilateralInteractionDisplay.ItemClickHandler(Object sender, EventArgs e) in C:\Users\Public\IFs\IFsWeb\frm_BilateralInteractionDisplay.aspx.vb:line 977
> at Coalesys.WebMenu.WebMenu.OnServerItemClick(ServerItemClickEventArgs eventArgs)
> at Coalesys.WebMenu.WebMenu.RaisePostBackEvent(String eventArgument)
> at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
> at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
> at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
|
non_process
|
bilateral display crash when using comparison options bilateral display crash when using comparison options ifs development to reproduce open bilateral display select forecast variables and scenario for display open select comparison option exit table to main display reopen check comparison options disable comparison option crash the following error occurred exception of type system web httpunhandledexception was thrown system indexoutofrangeexception index was outside the bounds of the array at system array internalgetreference void elemref rank pindices at system array getvalue at microsoft visualbasic compilerservices symbols container getarrayvalue object indices at microsoft visualbasic compilerservices newlatebinding internallateindexget object instance object arguments string argumentnames boolean reporterrors resolutionfailure failure boolean copyback at microsoft visualbasic compilerservices newlatebinding objectlateinvokedefault object instance object arguments string argumentnames boolean reporterrors boolean copyback at microsoft visualbasic compilerservices newlatebinding internallateinvokedefault object instance object arguments string argumentnames boolean reporterrors boolean copyback at microsoft visualbasic compilerservices newlatebinding lateindexget object instance object arguments string argumentnames at ifsweb frm bilateralinteractiondisplay loadgrid in c users public ifs ifsweb frm bilateralinteractiondisplay aspx vb line at ifsweb frm bilateralinteractiondisplay mnucompreset click in c users public ifs ifsweb frm bilateralinteractiondisplay aspx vb line at ifsweb frm bilateralinteractiondisplay itemclickhandler object sender eventargs e in c users public ifs ifsweb frm bilateralinteractiondisplay aspx vb line at coalesys webmenu webmenu onserveritemclick serveritemclickeventargs eventargs at coalesys webmenu webmenu raisepostbackevent string eventargument at system web ui page raisepostbackevent ipostbackeventhandler sourcecontrol string eventargument at system web ui page raisepostbackevent namevaluecollection postdata at system web ui page processrequestmain boolean includestagesbeforeasyncpoint boolean includestagesafterasyncpoint
| 0
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.