Unnamed: 0 int64 0 832k | id float64 2.49B 32.1B | type stringclasses 1 value | created_at stringlengths 19 19 | repo stringlengths 5 112 | repo_url stringlengths 34 141 | action stringclasses 3 values | title stringlengths 1 844 | labels stringlengths 4 721 | body stringlengths 1 261k | index stringclasses 12 values | text_combine stringlengths 96 261k | label stringclasses 2 values | text stringlengths 96 248k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
37,964 | 8,391,549,545 | IssuesEvent | 2018-10-09 15:15:18 | brian-team/brian2 | https://api.github.com/repos/brian-team/brian2 | opened | PyTorch/Tensorflow backend? | component: codegen enhancement major feature proposal | BindsNET and Nengo use PyTorch and Tensorflow (respectively) to run SNNs. I wonder if it's worth our considering this or not? Might be an easy way to get some scalability. | 1.0 | PyTorch/Tensorflow backend? - BindsNET and Nengo use PyTorch and Tensorflow (respectively) to run SNNs. I wonder if it's worth our considering this or not? Might be an easy way to get some scalability. | non_priority | pytorch tensorflow backend bindsnet and nengo use pytorch and tensorflow respectively to run snns i wonder if it s worth our considering this or not might be an easy way to get some scalability | 0 |
43,079 | 17,399,356,480 | IssuesEvent | 2021-08-02 17:19:26 | elastic/kibana | https://api.github.com/repos/elastic/kibana | opened | [Event log] Update findEventsBySavedObjectIds to resolve SO ids | Feature:EventLog Team:Alerting Services loe:hours | As part of the research done in https://github.com/elastic/kibana/issues/100666, we need to update the [`findEventsBySavedObjectIds`](https://github.com/elastic/kibana/blob/master/x-pack/plugins/event_log/server/event_log_client.ts#L83) client API method to properly resolve saved object ids. This API already makes use of the current space so it should be relatively easy to change.
One slight complication here is using the appropriate space for saved object id resolution, as the caller's space might differ from [the namespace](https://github.com/elastic/kibana/blob/master/x-pack/plugins/event_log/generated/mappings.json#L277) defined in the event log itself.
I don't expect this part of the code to need to worry about how to handle possible responses from the `.resolve()` API, but rather just use it to ensure we fetch the correct saved object. | 1.0 | [Event log] Update findEventsBySavedObjectIds to resolve SO ids - As part of the research done in https://github.com/elastic/kibana/issues/100666, we need to update the [`findEventsBySavedObjectIds`](https://github.com/elastic/kibana/blob/master/x-pack/plugins/event_log/server/event_log_client.ts#L83) client API method to properly resolve saved object ids. This API already makes use of the current space so it should be relatively easy to change.
One slight complication here is using the appropriate space for saved object id resolution, as the caller's space might differ from [the namespace](https://github.com/elastic/kibana/blob/master/x-pack/plugins/event_log/generated/mappings.json#L277) defined in the event log itself.
I don't expect this part of the code to need to worry about how to handle possible responses from the `.resolve()` API, but rather just use it to ensure we fetch the correct saved object. | non_priority | update findeventsbysavedobjectids to resolve so ids as part of the research done in we need to update the client api method to properly resolve saved object ids this api already makes use of the current space so it should be relatively easy to change one slight complication here is using the appropriate space for saved object id resolution as the caller s space might differ from defined in the event log itself i don t expect this part of the code to need to worry about how to handle possible responses from the resolve api but rather just use it to ensure we fetch the correct saved object | 0 |
182,448 | 21,664,520,804 | IssuesEvent | 2022-05-07 01:38:06 | tt9133github/ForTest2 | https://api.github.com/repos/tt9133github/ForTest2 | closed | CVE-2010-2479 (Medium) detected in moodle/moodle-v2.6.2 - autoclosed | security vulnerability | ## CVE-2010-2479 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>moodle/moodle-v2.6.2</b></p></summary>
<p>Moodle - the world's open source learning platform</p>
<p>
Dependency Hierarchy:
- :x: **moodle/moodle-v2.6.2** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/tt9133github/ForTest2/commit/27e1f740a162e55490d9ca929f243afbaa92476c">27e1f740a162e55490d9ca929f243afbaa92476c</a></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>
Cross-site scripting (XSS) vulnerability in HTML Purifier before 4.1.1, as used in Mahara and other products, when the browser is Internet Explorer, allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.
<p>Publish Date: 2010-07-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2010-2479>CVE-2010-2479</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>4.3</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-2451">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-2451</a></p>
<p>Release Date: 2010-07-06</p>
<p>Fix Resolution: 4.8.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-2010-2479 (Medium) detected in moodle/moodle-v2.6.2 - autoclosed - ## CVE-2010-2479 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>moodle/moodle-v2.6.2</b></p></summary>
<p>Moodle - the world's open source learning platform</p>
<p>
Dependency Hierarchy:
- :x: **moodle/moodle-v2.6.2** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/tt9133github/ForTest2/commit/27e1f740a162e55490d9ca929f243afbaa92476c">27e1f740a162e55490d9ca929f243afbaa92476c</a></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>
Cross-site scripting (XSS) vulnerability in HTML Purifier before 4.1.1, as used in Mahara and other products, when the browser is Internet Explorer, allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.
<p>Publish Date: 2010-07-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2010-2479>CVE-2010-2479</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>4.3</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-2451">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-2451</a></p>
<p>Release Date: 2010-07-06</p>
<p>Fix Resolution: 4.8.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_priority | cve medium detected in moodle moodle autoclosed cve medium severity vulnerability vulnerable library moodle moodle moodle the world s open source learning platform dependency hierarchy x moodle moodle vulnerable library found in head commit a href vulnerability details cross site scripting xss vulnerability in html purifier before as used in mahara and other products when the browser is internet explorer allows remote attackers to inject arbitrary web script or html via unspecified vectors publish date url a href cvss score details base score metrics not available suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
45,203 | 18,460,379,542 | IssuesEvent | 2021-10-15 23:53:58 | MicrosoftDocs/windowsserverdocs | https://api.github.com/repos/MicrosoftDocs/windowsserverdocs | closed | What about on Premise physical or VM deployments? | assigned-to-author remote-desktop-services Pri2 windows-server-threshold/prod | Why is everything here geared toward Azure? I realize that this is a big cash cow for MS, but many Enterprises own their infrastructure. This guide is next to useless for those scenarios.
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: eb4ff40d-9eb9-06ce-38cd-4b95bcbfafd8
* Version Independent ID: 4195f094-f79c-9b3e-c97f-94c093d4c696
* Content: [Remote Desktop Services roles](https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-roles)
* Content Source: [WindowsServerDocs/remote/remote-desktop-services/rds-roles.md](https://github.com/MicrosoftDocs/windowsserverdocs/blob/master/WindowsServerDocs/remote/remote-desktop-services/rds-roles.md)
* Product: **windows-server-threshold**
* GitHub Login: @Heidilohr
* Microsoft Alias: **helohr** | 1.0 | What about on Premise physical or VM deployments? - Why is everything here geared toward Azure? I realize that this is a big cash cow for MS, but many Enterprises own their infrastructure. This guide is next to useless for those scenarios.
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: eb4ff40d-9eb9-06ce-38cd-4b95bcbfafd8
* Version Independent ID: 4195f094-f79c-9b3e-c97f-94c093d4c696
* Content: [Remote Desktop Services roles](https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-roles)
* Content Source: [WindowsServerDocs/remote/remote-desktop-services/rds-roles.md](https://github.com/MicrosoftDocs/windowsserverdocs/blob/master/WindowsServerDocs/remote/remote-desktop-services/rds-roles.md)
* Product: **windows-server-threshold**
* GitHub Login: @Heidilohr
* Microsoft Alias: **helohr** | non_priority | what about on premise physical or vm deployments why is everything here geared toward azure i realize that this is a big cash cow for ms but many enterprises own their infrastructure this guide is next to useless for those scenarios 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 windows server threshold github login heidilohr microsoft alias helohr | 0 |
242,254 | 20,207,275,085 | IssuesEvent | 2022-02-11 22:01:30 | kubernetes/kubernetes | https://api.github.com/repos/kubernetes/kubernetes | closed | Refactor `audit_test.go` | area/test kind/cleanup sig/api-machinery lifecycle/rotten triage/accepted | <!-- Feature requests are unlikely to make progress as an issue.
Instead, please suggest enhancements by engaging with SIGs on slack and mailing lists.
A proposal that works through the design along with the implications of the change can be opened as a KEP:
https://git.k8s.io/enhancements/keps#kubernetes-enhancement-proposals-keps
-->
#### What would you like to be added:
The `test/integration/controlplane/audit_test.go` contains a lot of duplicated code around checking if certain audit events are there.
The `testAudit*` functions combine both actions for the tests and the assertions for the audit events. Decoupling those two things will enable us to move the "actions" code higher of the stack and unify the audit events evaluation code.
#### Why is this needed:
Unifying this test will make it shorter and will also make some of the functions more reusable. Less code = easier maintenance. | 1.0 | Refactor `audit_test.go` - <!-- Feature requests are unlikely to make progress as an issue.
Instead, please suggest enhancements by engaging with SIGs on slack and mailing lists.
A proposal that works through the design along with the implications of the change can be opened as a KEP:
https://git.k8s.io/enhancements/keps#kubernetes-enhancement-proposals-keps
-->
#### What would you like to be added:
The `test/integration/controlplane/audit_test.go` contains a lot of duplicated code around checking if certain audit events are there.
The `testAudit*` functions combine both actions for the tests and the assertions for the audit events. Decoupling those two things will enable us to move the "actions" code higher of the stack and unify the audit events evaluation code.
#### Why is this needed:
Unifying this test will make it shorter and will also make some of the functions more reusable. Less code = easier maintenance. | non_priority | refactor audit test go feature requests are unlikely to make progress as an issue instead please suggest enhancements by engaging with sigs on slack and mailing lists a proposal that works through the design along with the implications of the change can be opened as a kep what would you like to be added the test integration controlplane audit test go contains a lot of duplicated code around checking if certain audit events are there the testaudit functions combine both actions for the tests and the assertions for the audit events decoupling those two things will enable us to move the actions code higher of the stack and unify the audit events evaluation code why is this needed unifying this test will make it shorter and will also make some of the functions more reusable less code easier maintenance | 0 |
330,967 | 24,285,046,846 | IssuesEvent | 2022-09-28 21:08:57 | microsoft/onnxruntime | https://api.github.com/repos/microsoft/onnxruntime | closed | Missing depencencies for the official Python wheel (or, lacking documentation?) | documentation quantization | **Describe the bug**
Having a newly-created virtualenv with the latest version of `onnxruntime` installed in it via `pip install onnxruntime`, some imports fail because of missing dependencies:
```
>>> from onnxruntime.quantization import quantize_dynamic
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/Users/xor-xor/envs/my-test-env/lib/python3.7/site-packages/onnxruntime/quantization/__init__.py", line 1, in <module>
from .quantize import quantize, quantize_static, quantize_dynamic, quantize_qat
File "/Users/xor-xor/envs/my-test-env/lib/python3.7/site-packages/onnxruntime/quantization/quantize.py", line 7, in <module>
import onnx
ModuleNotFoundError: No module named 'onnx'
```
```
>>> from onnxruntime.transformers import optimizer
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/Users/xor-xor/envs/my-test-env/lib/python3.7/site-packages/onnxruntime/transformers/optimizer.py", line 21, in <module>
import coloredlogs
ModuleNotFoundError: No module named 'coloredlogs'
```
The latter seems to be a known one (see #7527), although the context is slightly different, as I'm not building from source here.
Installing those missing packages manually solves the problem, but if that's the recommended way of proceeding, then I think it should be mentioned [here](https://onnxruntime.ai/docs/install/#python-installs) or [here](https://onnxruntime.ai/docs/install/#requirements).
**Urgency**
None.
**System information**
- OS Platform and Distribution (e.g., Linux Ubuntu 16.04): macOS 10.15.7
- ONNX Runtime installed from (source or binary): binary
- ONNX Runtime version: 1.10.0
- Python version: 3.7.7
- Visual Studio version (if applicable): n/a
- GCC/Compiler version (if compiling from source): n/a
- CUDA/cuDNN version: n/a
- GPU model and memory: n/a
**To Reproduce**
1. `python -m venv my-test-env`
2. `source my-test-env/bin/activate`
3. `pip install pip --upgrade && pip install onnxruntime`
4. `python -c "from onnxruntime.quantization import quantize_dynamic"`
5. `python -c "from onnxruntime.transformers import optimizer"`
**Expected behavior**
Imports from steps (4) and (5) would succeed.
**Screenshots**
n/a
**Additional context**
n/a
| 1.0 | Missing depencencies for the official Python wheel (or, lacking documentation?) - **Describe the bug**
Having a newly-created virtualenv with the latest version of `onnxruntime` installed in it via `pip install onnxruntime`, some imports fail because of missing dependencies:
```
>>> from onnxruntime.quantization import quantize_dynamic
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/Users/xor-xor/envs/my-test-env/lib/python3.7/site-packages/onnxruntime/quantization/__init__.py", line 1, in <module>
from .quantize import quantize, quantize_static, quantize_dynamic, quantize_qat
File "/Users/xor-xor/envs/my-test-env/lib/python3.7/site-packages/onnxruntime/quantization/quantize.py", line 7, in <module>
import onnx
ModuleNotFoundError: No module named 'onnx'
```
```
>>> from onnxruntime.transformers import optimizer
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/Users/xor-xor/envs/my-test-env/lib/python3.7/site-packages/onnxruntime/transformers/optimizer.py", line 21, in <module>
import coloredlogs
ModuleNotFoundError: No module named 'coloredlogs'
```
The latter seems to be a known one (see #7527), although the context is slightly different, as I'm not building from source here.
Installing those missing packages manually solves the problem, but if that's the recommended way of proceeding, then I think it should be mentioned [here](https://onnxruntime.ai/docs/install/#python-installs) or [here](https://onnxruntime.ai/docs/install/#requirements).
**Urgency**
None.
**System information**
- OS Platform and Distribution (e.g., Linux Ubuntu 16.04): macOS 10.15.7
- ONNX Runtime installed from (source or binary): binary
- ONNX Runtime version: 1.10.0
- Python version: 3.7.7
- Visual Studio version (if applicable): n/a
- GCC/Compiler version (if compiling from source): n/a
- CUDA/cuDNN version: n/a
- GPU model and memory: n/a
**To Reproduce**
1. `python -m venv my-test-env`
2. `source my-test-env/bin/activate`
3. `pip install pip --upgrade && pip install onnxruntime`
4. `python -c "from onnxruntime.quantization import quantize_dynamic"`
5. `python -c "from onnxruntime.transformers import optimizer"`
**Expected behavior**
Imports from steps (4) and (5) would succeed.
**Screenshots**
n/a
**Additional context**
n/a
| non_priority | missing depencencies for the official python wheel or lacking documentation describe the bug having a newly created virtualenv with the latest version of onnxruntime installed in it via pip install onnxruntime some imports fail because of missing dependencies from onnxruntime quantization import quantize dynamic traceback most recent call last file line in file users xor xor envs my test env lib site packages onnxruntime quantization init py line in from quantize import quantize quantize static quantize dynamic quantize qat file users xor xor envs my test env lib site packages onnxruntime quantization quantize py line in import onnx modulenotfounderror no module named onnx from onnxruntime transformers import optimizer traceback most recent call last file line in file users xor xor envs my test env lib site packages onnxruntime transformers optimizer py line in import coloredlogs modulenotfounderror no module named coloredlogs the latter seems to be a known one see although the context is slightly different as i m not building from source here installing those missing packages manually solves the problem but if that s the recommended way of proceeding then i think it should be mentioned or urgency none system information os platform and distribution e g linux ubuntu macos onnx runtime installed from source or binary binary onnx runtime version python version visual studio version if applicable n a gcc compiler version if compiling from source n a cuda cudnn version n a gpu model and memory n a to reproduce python m venv my test env source my test env bin activate pip install pip upgrade pip install onnxruntime python c from onnxruntime quantization import quantize dynamic python c from onnxruntime transformers import optimizer expected behavior imports from steps and would succeed screenshots n a additional context n a | 0 |
179,520 | 13,885,307,988 | IssuesEvent | 2020-10-18 19:28:15 | Hamlib/Hamlib | https://api.github.com/repos/Hamlib/Hamlib | closed | Random set_ptt failure with RTS COM port | bug needs test | After hours of running will get an error opening COM1 as shown in WSJT-X_trace.log -- was able to duplicate on 3 computers with built-in COM port and USB cables too.
So one of a few things is happening
#1 Hamlib is not closing the device
#2 Something else is using the COM port
#3 Threading is causing a collision
[20200920 11:28:43.377 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1031 - "HamlibTransceiver::do_poll:" rig_get_ptt PTT = 0
[20200920 11:28:45.075 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:785 - Configuration::transceiver_online: Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: off; PTT: off)
[20200920 11:28:45.075 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:808 - Configuration::transceiver_frequency: 14074000 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: off; PTT: off)
[20200920 11:28:45.075 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:834 - Configuration::transceiver_ptt: true Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::UNK; SPLIT: off; PTT: off)
[20200920 11:28:45.075 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\TransceiverBase.cpp:44 - "TransceiverBase::set:" #: 288 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::UNK; SPLIT: off; PTT: off)
[20200920 11:28:45.075 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\TransceiverBase.cpp:44 - "TransceiverBase::set:" #: 289 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::UNK; SPLIT: off; PTT: on)
[20200920 11:28:45.075 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1053 - "HamlibTransceiver::do_ptt:" true Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: unknown; PTT: off) reversed = false
[20200920 11:28:45.075 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1058 - "HamlibTransceiver::do_ptt:" rig_set_ptt PTT = true
[20200920 11:28:45.119 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:2745 - Configuration::handle_transceiver_update: Transceiver State #: 288 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: unknown; PTT: off)
[20200920 11:28:45.181 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:2745 - Configuration::handle_transceiver_update: Transceiver State #: 289 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: unknown; PTT: on)
[20200920 11:28:45.181 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:785 - Configuration::transceiver_online: Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: off; PTT: on)
[20200920 11:28:45.181 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:808 - Configuration::transceiver_frequency: 14074000 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: off; PTT: on)
[20200920 11:28:45.181 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\TransceiverBase.cpp:44 - "TransceiverBase::set:" #: 290 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::UNK; SPLIT: off; PTT: on)
[20200920 11:28:45.182 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:2745 - Configuration::handle_transceiver_update: Transceiver State #: 290 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: unknown; PTT: on)
[20200920 11:28:53.313 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:934 - "HamlibTransceiver::do_poll:" VFO = VFOA
[20200920 11:28:53.334 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:974 - "HamlibTransceiver::do_poll:" rig_get_freq frequency = 1.4074e+07
[20200920 11:28:53.355 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1013 - "HamlibTransceiver::do_poll:" rig_get_mode mode = FM bw = 15000
[20200920 11:28:53.376 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1031 - "HamlibTransceiver::do_poll:" rig_get_ptt PTT = 1
[20200920 11:28:53.376 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:2745 - Configuration::handle_transceiver_update: Transceiver State #: 290 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: unknown; PTT: on)
[20200920 11:28:58.948 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:834 - Configuration::transceiver_ptt: false Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: off; PTT: on)
[20200920 11:28:58.948 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\TransceiverBase.cpp:44 - "TransceiverBase::set:" #: 291 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::UNK; SPLIT: off; PTT: off)
[20200920 11:28:58.949 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1053 - "HamlibTransceiver::do_ptt:" false Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: unknown; PTT: on) reversed = false
[20200920 11:28:58.949 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1068 - "HamlibTransceiver::do_ptt:" rig_set_ptt PTT = false
[20200920 11:28:59.061 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:712 - "HamlibTransceiver::do_frequency:" 14074000 mode: Transceiver::UNK reversed: false
[20200920 11:28:59.098 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:2745 - Configuration::handle_transceiver_update: Transceiver State #: 291 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: unknown; PTT: off)
[20200920 11:28:59.098 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:785 - Configuration::transceiver_online: Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: off; PTT: off)
[20200920 11:28:59.098 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:808 - Configuration::transceiver_frequency: 14074000 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: off; PTT: off)
[20200920 11:28:59.098 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\TransceiverBase.cpp:44 - "TransceiverBase::set:" #: 292 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::UNK; SPLIT: off; PTT: off)
[20200920 11:28:59.099 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:2745 - Configuration::handle_transceiver_update: Transceiver State #: 292 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: unknown; PTT: off)
[20200920 11:29:03.311 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:934 - "HamlibTransceiver::do_poll:" VFO = VFOA
[20200920 11:29:03.332 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:974 - "HamlibTransceiver::do_poll:" rig_get_freq frequency = 1.4074e+07
[20200920 11:29:03.352 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1013 - "HamlibTransceiver::do_poll:" rig_get_mode mode = FM bw = 15000
[20200920 11:29:03.373 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1031 - "HamlibTransceiver::do_poll:" rig_get_ptt PTT = 0
[20200920 11:29:03.373 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:2745 - Configuration::handle_transceiver_update: Transceiver State #: 292 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: unknown; PTT: off)
[20200920 11:29:13.311 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:934 - "HamlibTransceiver::do_poll:" VFO = VFOA
[20200920 11:29:13.332 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:974 - "HamlibTransceiver::do_poll:" rig_get_freq frequency = 1.4074e+07
[20200920 11:29:13.353 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1013 - "HamlibTransceiver::do_poll:" rig_get_mode mode = FM bw = 15000
[20200920 11:29:13.374 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1031 - "HamlibTransceiver::do_poll:" rig_get_ptt PTT = 0
[20200920 11:29:23.313 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:934 - "HamlibTransceiver::do_poll:" VFO = VFOA
[20200920 11:29:23.334 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:974 - "HamlibTransceiver::do_poll:" rig_get_freq frequency = 1.4074e+07
[20200920 11:29:23.355 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1013 - "HamlibTransceiver::do_poll:" rig_get_mode mode = FM bw = 15000
[20200920 11:29:23.376 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1031 - "HamlibTransceiver::do_poll:" rig_get_ptt PTT = 0
[20200920 11:29:33.314 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:934 - "HamlibTransceiver::do_poll:" VFO = VFOA
[20200920 11:29:33.335 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:974 - "HamlibTransceiver::do_poll:" rig_get_freq frequency = 1.4074e+07
[20200920 11:29:33.356 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1013 - "HamlibTransceiver::do_poll:" rig_get_mode mode = FM bw = 15000
[20200920 11:29:33.376 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1031 - "HamlibTransceiver::do_poll:" rig_get_ptt PTT = 0
[20200920 11:29:43.313 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:934 - "HamlibTransceiver::do_poll:" VFO = VFOA
[20200920 11:29:43.335 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:974 - "HamlibTransceiver::do_poll:" rig_get_freq frequency = 1.4074e+07
[20200920 11:29:43.355 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1013 - "HamlibTransceiver::do_poll:" rig_get_mode mode = FM bw = 15000
[20200920 11:29:43.376 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1031 - "HamlibTransceiver::do_poll:" rig_get_ptt PTT = 0
[20200920 11:29:45.009 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:785 - Configuration::transceiver_online: Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: off; PTT: off)
[20200920 11:29:45.009 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:808 - Configuration::transceiver_frequency: 14074000 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: off; PTT: off)
[20200920 11:29:45.009 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:834 - Configuration::transceiver_ptt: true Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::UNK; SPLIT: off; PTT: off)
[20200920 11:29:45.009 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\TransceiverBase.cpp:44 - "TransceiverBase::set:" #: 293 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::UNK; SPLIT: off; PTT: off)
[20200920 11:29:45.009 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\TransceiverBase.cpp:44 - "TransceiverBase::set:" #: 294 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::UNK; SPLIT: off; PTT: on)
[20200920 11:29:45.009 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1053 - "HamlibTransceiver::do_ptt:" true Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: unknown; PTT: off) reversed = false
[20200920 11:29:45.009 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1058 - "HamlibTransceiver::do_ptt:" rig_set_ptt PTT = true
[20200920 11:29:45.010 W. Europe Daylight Time C] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:47 - Hamlib: rig_set_ptt: cannot open PTT device "\\.\COM1"
[20200920 11:29:45.010 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:423 - "HamlibTransceiver::error_check:" error: IO error
[20200920 11:29:45.010 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1053 - "HamlibTransceiver::do_ptt:" false Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: unknown; PTT: off) reversed = false
[20200920 11:29:45.010 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1068 - "HamlibTransceiver::do_ptt:" rig_set_ptt PTT = false
[20200920 11:29:45.053 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:2745 - Configuration::handle_transceiver_update: Transceiver State #: 293 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: unknown; PTT: off)
[20200920 11:29:45.053 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:2745 - Configuration::handle_transceiver_update: Transceiver State #: 294 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: unknown; PTT: off)
[20200920 11:29:45.054 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:2795 - Configuration::handle_transceiver_failure: reason: "Hamlib error: IO error while setting PTT on"
[20200920 11:29:45.066 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:785 - Configuration::transceiver_online: Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: off; PTT: on)
[20200920 11:29:45.066 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:843 - Configuration::sync_transceiver: force signal: true enforce_mode_and_split: true Transceiver::TransceiverState(online: no Frequency {0Hz, 0Hz} Transceiver::UNK; SPLIT: unknown; PTT: off)
[20200920 11:29:45.072 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:672 - "HamlibTransceiver::do_stop:" state: Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: unknown; PTT: off) reversed = false
[20200920 11:29:45.072 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:432 - "HamlibTransceiver::do_start:" "Hamlib" "Dummy"
[20200920 11:29:45.072 W. Europe Daylight Time C] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:47 - Hamlib: rig_open: cannot open PTT device "\\.\COM1"
[20200920 11:29:45.072 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:423 - "HamlibTransceiver::error_check:" error: IO error
[20200920 11:29:45.072 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1053 - "HamlibTransceiver::do_ptt:" false Transceiver::TransceiverState(online: yes Frequency {0Hz, 0Hz} Transceiver::UNK; SPLIT: unknown; PTT: off) reversed = false
[20200920 11:29:45.072 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1068 - "HamlibTransceiver::do_ptt:" rig_set_ptt PTT = false
[20200920 11:29:45.072 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:2795 - Configuration::handle_transceiver_failure: reason: "Hamlib error: IO error while opening connection to rig"
[20200920 11:29:45.072 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:423 - "HamlibTransceiver::error_check:" error: Invalid parameter
[20200920 11:29:45.084 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:2745 - Configuration::handle_transceiver_update: Transceiver State #: 295 Transceiver::TransceiverState(online: no Frequency {0Hz, 0Hz} Transceiver::UNK; SPLIT: unknown; PTT: off)
[20200920 11:29:45.324 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:834 - Configuration::transceiver_ptt: false Transceiver::TransceiverState(online: no Frequency {0Hz, 0Hz} Transceiver::UNK; SPLIT: off; PTT: off)
[20200920 11:30:05.007 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:799 - Configuration::transceiver_offline: Transceiver::TransceiverState(online: yes Frequency {0Hz, 0Hz} Transceiver::UNK; SPLIT: off; PTT: off)
[20200920 11:30:05.007 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:785 - Configuration::transceiver_online: Transceiver::TransceiverState(online: yes Frequency {0Hz, 0Hz} Transceiver::UNK; SPLIT: off; PTT: off)
[20200920 11:30:05.007 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:808 - Configuration::transceiver_frequency: 0 Transceiver::TransceiverState(online: no Frequency {0Hz, 0Hz} Transceiver::UNK; SPLIT: unknown; PTT: off)
[20200920 11:30:05.007 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:432 - "HamlibTransceiver::do_start:" "Hamlib" "Dummy"
[20200920 11:30:05.185 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:934 - "HamlibTransceiver::do_poll:" VFO = VFOA
[20200920 11:30:05.185 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:974 - "HamlibTransceiver::do_poll:" rig_get_freq frequency = 1.4074e+07
[20200920 11:30:05.185 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1013 - "HamlibTransceiver::do_poll:" rig_get_mode mode = FM bw = 0
[20200920 11:30:05.185 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1031 - "HamlibTransceiver::do_poll:" rig_get_ptt PTT = 0
[20200920 11:30:05.185 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:651 - "HamlibTransceiver::do_start:" exit Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: unknown; PTT: off) reversed = false resolution = 0 | 1.0 | Random set_ptt failure with RTS COM port - After hours of running will get an error opening COM1 as shown in WSJT-X_trace.log -- was able to duplicate on 3 computers with built-in COM port and USB cables too.
So one of a few things is happening
#1 Hamlib is not closing the device
#2 Something else is using the COM port
#3 Threading is causing a collision
[20200920 11:28:43.377 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1031 - "HamlibTransceiver::do_poll:" rig_get_ptt PTT = 0
[20200920 11:28:45.075 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:785 - Configuration::transceiver_online: Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: off; PTT: off)
[20200920 11:28:45.075 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:808 - Configuration::transceiver_frequency: 14074000 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: off; PTT: off)
[20200920 11:28:45.075 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:834 - Configuration::transceiver_ptt: true Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::UNK; SPLIT: off; PTT: off)
[20200920 11:28:45.075 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\TransceiverBase.cpp:44 - "TransceiverBase::set:" #: 288 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::UNK; SPLIT: off; PTT: off)
[20200920 11:28:45.075 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\TransceiverBase.cpp:44 - "TransceiverBase::set:" #: 289 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::UNK; SPLIT: off; PTT: on)
[20200920 11:28:45.075 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1053 - "HamlibTransceiver::do_ptt:" true Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: unknown; PTT: off) reversed = false
[20200920 11:28:45.075 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1058 - "HamlibTransceiver::do_ptt:" rig_set_ptt PTT = true
[20200920 11:28:45.119 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:2745 - Configuration::handle_transceiver_update: Transceiver State #: 288 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: unknown; PTT: off)
[20200920 11:28:45.181 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:2745 - Configuration::handle_transceiver_update: Transceiver State #: 289 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: unknown; PTT: on)
[20200920 11:28:45.181 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:785 - Configuration::transceiver_online: Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: off; PTT: on)
[20200920 11:28:45.181 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:808 - Configuration::transceiver_frequency: 14074000 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: off; PTT: on)
[20200920 11:28:45.181 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\TransceiverBase.cpp:44 - "TransceiverBase::set:" #: 290 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::UNK; SPLIT: off; PTT: on)
[20200920 11:28:45.182 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:2745 - Configuration::handle_transceiver_update: Transceiver State #: 290 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: unknown; PTT: on)
[20200920 11:28:53.313 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:934 - "HamlibTransceiver::do_poll:" VFO = VFOA
[20200920 11:28:53.334 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:974 - "HamlibTransceiver::do_poll:" rig_get_freq frequency = 1.4074e+07
[20200920 11:28:53.355 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1013 - "HamlibTransceiver::do_poll:" rig_get_mode mode = FM bw = 15000
[20200920 11:28:53.376 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1031 - "HamlibTransceiver::do_poll:" rig_get_ptt PTT = 1
[20200920 11:28:53.376 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:2745 - Configuration::handle_transceiver_update: Transceiver State #: 290 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: unknown; PTT: on)
[20200920 11:28:58.948 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:834 - Configuration::transceiver_ptt: false Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: off; PTT: on)
[20200920 11:28:58.948 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\TransceiverBase.cpp:44 - "TransceiverBase::set:" #: 291 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::UNK; SPLIT: off; PTT: off)
[20200920 11:28:58.949 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1053 - "HamlibTransceiver::do_ptt:" false Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: unknown; PTT: on) reversed = false
[20200920 11:28:58.949 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1068 - "HamlibTransceiver::do_ptt:" rig_set_ptt PTT = false
[20200920 11:28:59.061 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:712 - "HamlibTransceiver::do_frequency:" 14074000 mode: Transceiver::UNK reversed: false
[20200920 11:28:59.098 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:2745 - Configuration::handle_transceiver_update: Transceiver State #: 291 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: unknown; PTT: off)
[20200920 11:28:59.098 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:785 - Configuration::transceiver_online: Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: off; PTT: off)
[20200920 11:28:59.098 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:808 - Configuration::transceiver_frequency: 14074000 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: off; PTT: off)
[20200920 11:28:59.098 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\TransceiverBase.cpp:44 - "TransceiverBase::set:" #: 292 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::UNK; SPLIT: off; PTT: off)
[20200920 11:28:59.099 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:2745 - Configuration::handle_transceiver_update: Transceiver State #: 292 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: unknown; PTT: off)
[20200920 11:29:03.311 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:934 - "HamlibTransceiver::do_poll:" VFO = VFOA
[20200920 11:29:03.332 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:974 - "HamlibTransceiver::do_poll:" rig_get_freq frequency = 1.4074e+07
[20200920 11:29:03.352 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1013 - "HamlibTransceiver::do_poll:" rig_get_mode mode = FM bw = 15000
[20200920 11:29:03.373 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1031 - "HamlibTransceiver::do_poll:" rig_get_ptt PTT = 0
[20200920 11:29:03.373 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:2745 - Configuration::handle_transceiver_update: Transceiver State #: 292 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: unknown; PTT: off)
[20200920 11:29:13.311 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:934 - "HamlibTransceiver::do_poll:" VFO = VFOA
[20200920 11:29:13.332 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:974 - "HamlibTransceiver::do_poll:" rig_get_freq frequency = 1.4074e+07
[20200920 11:29:13.353 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1013 - "HamlibTransceiver::do_poll:" rig_get_mode mode = FM bw = 15000
[20200920 11:29:13.374 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1031 - "HamlibTransceiver::do_poll:" rig_get_ptt PTT = 0
[20200920 11:29:23.313 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:934 - "HamlibTransceiver::do_poll:" VFO = VFOA
[20200920 11:29:23.334 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:974 - "HamlibTransceiver::do_poll:" rig_get_freq frequency = 1.4074e+07
[20200920 11:29:23.355 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1013 - "HamlibTransceiver::do_poll:" rig_get_mode mode = FM bw = 15000
[20200920 11:29:23.376 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1031 - "HamlibTransceiver::do_poll:" rig_get_ptt PTT = 0
[20200920 11:29:33.314 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:934 - "HamlibTransceiver::do_poll:" VFO = VFOA
[20200920 11:29:33.335 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:974 - "HamlibTransceiver::do_poll:" rig_get_freq frequency = 1.4074e+07
[20200920 11:29:33.356 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1013 - "HamlibTransceiver::do_poll:" rig_get_mode mode = FM bw = 15000
[20200920 11:29:33.376 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1031 - "HamlibTransceiver::do_poll:" rig_get_ptt PTT = 0
[20200920 11:29:43.313 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:934 - "HamlibTransceiver::do_poll:" VFO = VFOA
[20200920 11:29:43.335 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:974 - "HamlibTransceiver::do_poll:" rig_get_freq frequency = 1.4074e+07
[20200920 11:29:43.355 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1013 - "HamlibTransceiver::do_poll:" rig_get_mode mode = FM bw = 15000
[20200920 11:29:43.376 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1031 - "HamlibTransceiver::do_poll:" rig_get_ptt PTT = 0
[20200920 11:29:45.009 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:785 - Configuration::transceiver_online: Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: off; PTT: off)
[20200920 11:29:45.009 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:808 - Configuration::transceiver_frequency: 14074000 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: off; PTT: off)
[20200920 11:29:45.009 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:834 - Configuration::transceiver_ptt: true Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::UNK; SPLIT: off; PTT: off)
[20200920 11:29:45.009 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\TransceiverBase.cpp:44 - "TransceiverBase::set:" #: 293 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::UNK; SPLIT: off; PTT: off)
[20200920 11:29:45.009 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\TransceiverBase.cpp:44 - "TransceiverBase::set:" #: 294 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::UNK; SPLIT: off; PTT: on)
[20200920 11:29:45.009 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1053 - "HamlibTransceiver::do_ptt:" true Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: unknown; PTT: off) reversed = false
[20200920 11:29:45.009 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1058 - "HamlibTransceiver::do_ptt:" rig_set_ptt PTT = true
[20200920 11:29:45.010 W. Europe Daylight Time C] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:47 - Hamlib: rig_set_ptt: cannot open PTT device "\\.\COM1"
[20200920 11:29:45.010 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:423 - "HamlibTransceiver::error_check:" error: IO error
[20200920 11:29:45.010 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1053 - "HamlibTransceiver::do_ptt:" false Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: unknown; PTT: off) reversed = false
[20200920 11:29:45.010 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1068 - "HamlibTransceiver::do_ptt:" rig_set_ptt PTT = false
[20200920 11:29:45.053 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:2745 - Configuration::handle_transceiver_update: Transceiver State #: 293 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: unknown; PTT: off)
[20200920 11:29:45.053 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:2745 - Configuration::handle_transceiver_update: Transceiver State #: 294 Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: unknown; PTT: off)
[20200920 11:29:45.054 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:2795 - Configuration::handle_transceiver_failure: reason: "Hamlib error: IO error while setting PTT on"
[20200920 11:29:45.066 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:785 - Configuration::transceiver_online: Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: off; PTT: on)
[20200920 11:29:45.066 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:843 - Configuration::sync_transceiver: force signal: true enforce_mode_and_split: true Transceiver::TransceiverState(online: no Frequency {0Hz, 0Hz} Transceiver::UNK; SPLIT: unknown; PTT: off)
[20200920 11:29:45.072 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:672 - "HamlibTransceiver::do_stop:" state: Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: unknown; PTT: off) reversed = false
[20200920 11:29:45.072 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:432 - "HamlibTransceiver::do_start:" "Hamlib" "Dummy"
[20200920 11:29:45.072 W. Europe Daylight Time C] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:47 - Hamlib: rig_open: cannot open PTT device "\\.\COM1"
[20200920 11:29:45.072 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:423 - "HamlibTransceiver::error_check:" error: IO error
[20200920 11:29:45.072 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1053 - "HamlibTransceiver::do_ptt:" false Transceiver::TransceiverState(online: yes Frequency {0Hz, 0Hz} Transceiver::UNK; SPLIT: unknown; PTT: off) reversed = false
[20200920 11:29:45.072 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1068 - "HamlibTransceiver::do_ptt:" rig_set_ptt PTT = false
[20200920 11:29:45.072 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:2795 - Configuration::handle_transceiver_failure: reason: "Hamlib error: IO error while opening connection to rig"
[20200920 11:29:45.072 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:423 - "HamlibTransceiver::error_check:" error: Invalid parameter
[20200920 11:29:45.084 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:2745 - Configuration::handle_transceiver_update: Transceiver State #: 295 Transceiver::TransceiverState(online: no Frequency {0Hz, 0Hz} Transceiver::UNK; SPLIT: unknown; PTT: off)
[20200920 11:29:45.324 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:834 - Configuration::transceiver_ptt: false Transceiver::TransceiverState(online: no Frequency {0Hz, 0Hz} Transceiver::UNK; SPLIT: off; PTT: off)
[20200920 11:30:05.007 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:799 - Configuration::transceiver_offline: Transceiver::TransceiverState(online: yes Frequency {0Hz, 0Hz} Transceiver::UNK; SPLIT: off; PTT: off)
[20200920 11:30:05.007 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:785 - Configuration::transceiver_online: Transceiver::TransceiverState(online: yes Frequency {0Hz, 0Hz} Transceiver::UNK; SPLIT: off; PTT: off)
[20200920 11:30:05.007 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:808 - Configuration::transceiver_frequency: 0 Transceiver::TransceiverState(online: no Frequency {0Hz, 0Hz} Transceiver::UNK; SPLIT: unknown; PTT: off)
[20200920 11:30:05.007 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:432 - "HamlibTransceiver::do_start:" "Hamlib" "Dummy"
[20200920 11:30:05.185 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:934 - "HamlibTransceiver::do_poll:" VFO = VFOA
[20200920 11:30:05.185 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:974 - "HamlibTransceiver::do_poll:" rig_get_freq frequency = 1.4074e+07
[20200920 11:30:05.185 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1013 - "HamlibTransceiver::do_poll:" rig_get_mode mode = FM bw = 0
[20200920 11:30:05.185 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:1031 - "HamlibTransceiver::do_poll:" rig_get_ptt PTT = 0
[20200920 11:30:05.185 W. Europe Daylight Time D] C:\JTSDK64-Tools\tmp\wsjtx\Transceiver\HamlibTransceiver.cpp:651 - "HamlibTransceiver::do_start:" exit Transceiver::TransceiverState(online: yes Frequency {14074000Hz, 0Hz} Transceiver::FM; SPLIT: unknown; PTT: off) reversed = false resolution = 0 | non_priority | random set ptt failure with rts com port after hours of running will get an error opening as shown in wsjt x trace log was able to duplicate on computers with built in com port and usb cables too so one of a few things is happening hamlib is not closing the device something else is using the com port threading is causing a collision c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do poll rig get ptt ptt c tools tmp wsjtx configuration cpp configuration transceiver online transceiver transceiverstate online yes frequency transceiver fm split off ptt off c tools tmp wsjtx configuration cpp configuration transceiver frequency transceiver transceiverstate online yes frequency transceiver fm split off ptt off c tools tmp wsjtx configuration cpp configuration transceiver ptt true transceiver transceiverstate online yes frequency transceiver unk split off ptt off c tools tmp wsjtx transceiver transceiverbase cpp transceiverbase set transceiver transceiverstate online yes frequency transceiver unk split off ptt off c tools tmp wsjtx transceiver transceiverbase cpp transceiverbase set transceiver transceiverstate online yes frequency transceiver unk split off ptt on c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do ptt true transceiver transceiverstate online yes frequency transceiver fm split unknown ptt off reversed false c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do ptt rig set ptt ptt true c tools tmp wsjtx configuration cpp configuration handle transceiver update transceiver state transceiver transceiverstate online yes frequency transceiver fm split unknown ptt off c tools tmp wsjtx configuration cpp configuration handle transceiver update transceiver state transceiver transceiverstate online yes frequency transceiver fm split unknown ptt on c tools tmp wsjtx configuration cpp configuration transceiver online transceiver transceiverstate online yes frequency transceiver fm split off ptt on c tools tmp wsjtx configuration cpp configuration transceiver frequency transceiver transceiverstate online yes frequency transceiver fm split off ptt on c tools tmp wsjtx transceiver transceiverbase cpp transceiverbase set transceiver transceiverstate online yes frequency transceiver unk split off ptt on c tools tmp wsjtx configuration cpp configuration handle transceiver update transceiver state transceiver transceiverstate online yes frequency transceiver fm split unknown ptt on c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do poll vfo vfoa c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do poll rig get freq frequency c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do poll rig get mode mode fm bw c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do poll rig get ptt ptt c tools tmp wsjtx configuration cpp configuration handle transceiver update transceiver state transceiver transceiverstate online yes frequency transceiver fm split unknown ptt on c tools tmp wsjtx configuration cpp configuration transceiver ptt false transceiver transceiverstate online yes frequency transceiver fm split off ptt on c tools tmp wsjtx transceiver transceiverbase cpp transceiverbase set transceiver transceiverstate online yes frequency transceiver unk split off ptt off c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do ptt false transceiver transceiverstate online yes frequency transceiver fm split unknown ptt on reversed false c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do ptt rig set ptt ptt false c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do frequency mode transceiver unk reversed false c tools tmp wsjtx configuration cpp configuration handle transceiver update transceiver state transceiver transceiverstate online yes frequency transceiver fm split unknown ptt off c tools tmp wsjtx configuration cpp configuration transceiver online transceiver transceiverstate online yes frequency transceiver fm split off ptt off c tools tmp wsjtx configuration cpp configuration transceiver frequency transceiver transceiverstate online yes frequency transceiver fm split off ptt off c tools tmp wsjtx transceiver transceiverbase cpp transceiverbase set transceiver transceiverstate online yes frequency transceiver unk split off ptt off c tools tmp wsjtx configuration cpp configuration handle transceiver update transceiver state transceiver transceiverstate online yes frequency transceiver fm split unknown ptt off c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do poll vfo vfoa c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do poll rig get freq frequency c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do poll rig get mode mode fm bw c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do poll rig get ptt ptt c tools tmp wsjtx configuration cpp configuration handle transceiver update transceiver state transceiver transceiverstate online yes frequency transceiver fm split unknown ptt off c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do poll vfo vfoa c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do poll rig get freq frequency c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do poll rig get mode mode fm bw c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do poll rig get ptt ptt c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do poll vfo vfoa c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do poll rig get freq frequency c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do poll rig get mode mode fm bw c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do poll rig get ptt ptt c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do poll vfo vfoa c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do poll rig get freq frequency c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do poll rig get mode mode fm bw c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do poll rig get ptt ptt c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do poll vfo vfoa c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do poll rig get freq frequency c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do poll rig get mode mode fm bw c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do poll rig get ptt ptt c tools tmp wsjtx configuration cpp configuration transceiver online transceiver transceiverstate online yes frequency transceiver fm split off ptt off c tools tmp wsjtx configuration cpp configuration transceiver frequency transceiver transceiverstate online yes frequency transceiver fm split off ptt off c tools tmp wsjtx configuration cpp configuration transceiver ptt true transceiver transceiverstate online yes frequency transceiver unk split off ptt off c tools tmp wsjtx transceiver transceiverbase cpp transceiverbase set transceiver transceiverstate online yes frequency transceiver unk split off ptt off c tools tmp wsjtx transceiver transceiverbase cpp transceiverbase set transceiver transceiverstate online yes frequency transceiver unk split off ptt on c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do ptt true transceiver transceiverstate online yes frequency transceiver fm split unknown ptt off reversed false c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do ptt rig set ptt ptt true c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlib rig set ptt cannot open ptt device c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver error check error io error c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do ptt false transceiver transceiverstate online yes frequency transceiver fm split unknown ptt off reversed false c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do ptt rig set ptt ptt false c tools tmp wsjtx configuration cpp configuration handle transceiver update transceiver state transceiver transceiverstate online yes frequency transceiver fm split unknown ptt off c tools tmp wsjtx configuration cpp configuration handle transceiver update transceiver state transceiver transceiverstate online yes frequency transceiver fm split unknown ptt off c tools tmp wsjtx configuration cpp configuration handle transceiver failure reason hamlib error io error while setting ptt on c tools tmp wsjtx configuration cpp configuration transceiver online transceiver transceiverstate online yes frequency transceiver fm split off ptt on c tools tmp wsjtx configuration cpp configuration sync transceiver force signal true enforce mode and split true transceiver transceiverstate online no frequency transceiver unk split unknown ptt off c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do stop state transceiver transceiverstate online yes frequency transceiver fm split unknown ptt off reversed false c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do start hamlib dummy c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlib rig open cannot open ptt device c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver error check error io error c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do ptt false transceiver transceiverstate online yes frequency transceiver unk split unknown ptt off reversed false c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do ptt rig set ptt ptt false c tools tmp wsjtx configuration cpp configuration handle transceiver failure reason hamlib error io error while opening connection to rig c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver error check error invalid parameter c tools tmp wsjtx configuration cpp configuration handle transceiver update transceiver state transceiver transceiverstate online no frequency transceiver unk split unknown ptt off c tools tmp wsjtx configuration cpp configuration transceiver ptt false transceiver transceiverstate online no frequency transceiver unk split off ptt off c tools tmp wsjtx configuration cpp configuration transceiver offline transceiver transceiverstate online yes frequency transceiver unk split off ptt off c tools tmp wsjtx configuration cpp configuration transceiver online transceiver transceiverstate online yes frequency transceiver unk split off ptt off c tools tmp wsjtx configuration cpp configuration transceiver frequency transceiver transceiverstate online no frequency transceiver unk split unknown ptt off c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do start hamlib dummy c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do poll vfo vfoa c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do poll rig get freq frequency c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do poll rig get mode mode fm bw c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do poll rig get ptt ptt c tools tmp wsjtx transceiver hamlibtransceiver cpp hamlibtransceiver do start exit transceiver transceiverstate online yes frequency transceiver fm split unknown ptt off reversed false resolution | 0 |
2,560 | 12,280,206,112 | IssuesEvent | 2020-05-08 13:43:59 | ibm-cloud-architecture/cloudpak8s | https://api.github.com/repos/ibm-cloud-architecture/cloudpak8s | closed | Hide unfinished sections of CP for Automation | cp4automation | Request from Tech Sales leader. I have just commented out the unfinished parts, so they are hidden but not deleted. | 1.0 | Hide unfinished sections of CP for Automation - Request from Tech Sales leader. I have just commented out the unfinished parts, so they are hidden but not deleted. | non_priority | hide unfinished sections of cp for automation request from tech sales leader i have just commented out the unfinished parts so they are hidden but not deleted | 0 |
206,477 | 15,731,680,204 | IssuesEvent | 2021-03-29 17:22:13 | celo-org/celo-monorepo | https://api.github.com/repos/celo-org/celo-monorepo | closed | [FLAKEY TEST] protocol-test-governance-network -> protocol -> Contract: EpochRewards -> #getRewardsMultiplier() -> when the actual remaining supply is 10% less than the target remaining supply after rewards -> should return one minus 10% times the underspend adjustment | FLAKEY protocol protocol-test-governance-network | FlakeTracker closed this issue after commit fb8da80fbe7ff0444d3f8137c935154dd3677313
Discovered at commit 60d55f9d9f99230cf3a552db3374d99c625977a9
Attempt No. 1:
AssertionError: expected 0.5 and got 0.500000007.
at Object.assertEqualDpBN (/home/circleci/app/packages/protocol/lib/test-utils.ts:306:3)
at /home/circleci/app/packages/protocol/test/governance/network/epochrewards.ts:866:42
at step (/home/circleci/app/packages/protocol/test/governance/network/epochrewards.ts:33:23)
at Object.next (/home/circleci/app/packages/protocol/test/governance/network/epochrewards.ts:14:53)
at fulfilled (/home/circleci/app/packages/protocol/test/governance/network/epochrewards.ts:5:58)
at process._tickCallback (internal/process/next_tick.js:68:7)
Attempt No. 2:
Test Passed!
| 1.0 | [FLAKEY TEST] protocol-test-governance-network -> protocol -> Contract: EpochRewards -> #getRewardsMultiplier() -> when the actual remaining supply is 10% less than the target remaining supply after rewards -> should return one minus 10% times the underspend adjustment - FlakeTracker closed this issue after commit fb8da80fbe7ff0444d3f8137c935154dd3677313
Discovered at commit 60d55f9d9f99230cf3a552db3374d99c625977a9
Attempt No. 1:
AssertionError: expected 0.5 and got 0.500000007.
at Object.assertEqualDpBN (/home/circleci/app/packages/protocol/lib/test-utils.ts:306:3)
at /home/circleci/app/packages/protocol/test/governance/network/epochrewards.ts:866:42
at step (/home/circleci/app/packages/protocol/test/governance/network/epochrewards.ts:33:23)
at Object.next (/home/circleci/app/packages/protocol/test/governance/network/epochrewards.ts:14:53)
at fulfilled (/home/circleci/app/packages/protocol/test/governance/network/epochrewards.ts:5:58)
at process._tickCallback (internal/process/next_tick.js:68:7)
Attempt No. 2:
Test Passed!
| non_priority | protocol test governance network protocol contract epochrewards getrewardsmultiplier when the actual remaining supply is less than the target remaining supply after rewards should return one minus times the underspend adjustment flaketracker closed this issue after commit discovered at commit attempt no assertionerror expected and got at object assertequaldpbn home circleci app packages protocol lib test utils ts at home circleci app packages protocol test governance network epochrewards ts at step home circleci app packages protocol test governance network epochrewards ts at object next home circleci app packages protocol test governance network epochrewards ts at fulfilled home circleci app packages protocol test governance network epochrewards ts at process tickcallback internal process next tick js attempt no test passed | 0 |
106,747 | 23,277,915,935 | IssuesEvent | 2022-08-05 09:04:51 | gitpod-io/gitpod | https://api.github.com/repos/gitpod-io/gitpod | opened | Introduce dependency proxy as an instance setting for caching OpenVSX extensions | type: feature request feature: vscode-extension team: IDE | ### Problem to solve
From the relevant RFC: **[OpenVSX self-hosting POC](https://www.notion.so/gitpod/f34aabea1d3745479c87431f4a92235f)** (internal):
> We would like to prototype self hosting of OpenVSX to improve reliability on SaaS and self-hosting customers.
See also relevant discussions[[1](https://www.notion.so/gitpod/1cf6088936d04e6d9bd1b9368358f7b2#cac47154dca2469fa2a3c1455bf8cace)][[2](https://www.notion.so/gitpod/a49f456f9d144f2cbd008700337f3dde#47c9f4d6a2d6471a9b4146b83c1c7a93)] (internal).
### Proposal
Introduce dependency proxy as an instance setting for caching OpenVSX extensions.
Here's an early design on how this could look like:
<img width="717" alt="Screenshot 2022-08-05 at 11 46 59 AM" src="https://user-images.githubusercontent.com/120486/183042584-8086fabd-dbdd-4c28-91a3-835c06b57643.png">
| 1.0 | Introduce dependency proxy as an instance setting for caching OpenVSX extensions - ### Problem to solve
From the relevant RFC: **[OpenVSX self-hosting POC](https://www.notion.so/gitpod/f34aabea1d3745479c87431f4a92235f)** (internal):
> We would like to prototype self hosting of OpenVSX to improve reliability on SaaS and self-hosting customers.
See also relevant discussions[[1](https://www.notion.so/gitpod/1cf6088936d04e6d9bd1b9368358f7b2#cac47154dca2469fa2a3c1455bf8cace)][[2](https://www.notion.so/gitpod/a49f456f9d144f2cbd008700337f3dde#47c9f4d6a2d6471a9b4146b83c1c7a93)] (internal).
### Proposal
Introduce dependency proxy as an instance setting for caching OpenVSX extensions.
Here's an early design on how this could look like:
<img width="717" alt="Screenshot 2022-08-05 at 11 46 59 AM" src="https://user-images.githubusercontent.com/120486/183042584-8086fabd-dbdd-4c28-91a3-835c06b57643.png">
| non_priority | introduce dependency proxy as an instance setting for caching openvsx extensions problem to solve from the relevant rfc internal we would like to prototype self hosting of openvsx to improve reliability on saas and self hosting customers see also relevant discussions internal proposal introduce dependency proxy as an instance setting for caching openvsx extensions here s an early design on how this could look like img width alt screenshot at am src | 0 |
79,090 | 27,970,275,120 | IssuesEvent | 2023-03-25 00:58:27 | vector-im/element-web | https://api.github.com/repos/vector-im/element-web | opened | Create account link on login page incorrectly appends register to URL | T-Defect | ### Steps to reproduce
1. A synapse server with a single oidc_provider configured as only identity provider.
2. The `.well-known` options for `m.authentication` also point to the same identity provider.
3. Instead of "Continue with <IdP Name> klick on "Create account" below.
4. A redirect to the following URL happends: `https://[...]/_matrix/client/r0/login/sso/redirect/register?redirectUrl=https%3A%2F%2Fc[...]%2F`
### Outcome
#### What did you expect?
A redirect to `https://[...]/_matrix/client/r0/login/sso/redirect?redirectUrl=https%3A%2F%2Fc[...]%2F`
note the missing register in the path.
#### What happened instead?
Synapse interprets the register as the idp id and fails at this point: https://github.com/matrix-org/synapse/blob/ce00e57a2acc7c06d0e3bf4c9880dc830c6938ef/synapse/handlers/sso.py#L319
returning
```
{"errcode":"M_NOT_FOUND","error":"Unknown identity provider"}
```
### Operating system
Any
### Browser information
Any
### URL for webapp
develop.element.io (just as a test if it can be reproduced there)
### Application version
Custom deployed: version: 1.11.25 Olm version: 3.2.12
### Homeserver
Synapse 1.79.0.
### Will you send logs?
No | 1.0 | Create account link on login page incorrectly appends register to URL - ### Steps to reproduce
1. A synapse server with a single oidc_provider configured as only identity provider.
2. The `.well-known` options for `m.authentication` also point to the same identity provider.
3. Instead of "Continue with <IdP Name> klick on "Create account" below.
4. A redirect to the following URL happends: `https://[...]/_matrix/client/r0/login/sso/redirect/register?redirectUrl=https%3A%2F%2Fc[...]%2F`
### Outcome
#### What did you expect?
A redirect to `https://[...]/_matrix/client/r0/login/sso/redirect?redirectUrl=https%3A%2F%2Fc[...]%2F`
note the missing register in the path.
#### What happened instead?
Synapse interprets the register as the idp id and fails at this point: https://github.com/matrix-org/synapse/blob/ce00e57a2acc7c06d0e3bf4c9880dc830c6938ef/synapse/handlers/sso.py#L319
returning
```
{"errcode":"M_NOT_FOUND","error":"Unknown identity provider"}
```
### Operating system
Any
### Browser information
Any
### URL for webapp
develop.element.io (just as a test if it can be reproduced there)
### Application version
Custom deployed: version: 1.11.25 Olm version: 3.2.12
### Homeserver
Synapse 1.79.0.
### Will you send logs?
No | non_priority | create account link on login page incorrectly appends register to url steps to reproduce a synapse server with a single oidc provider configured as only identity provider the well known options for m authentication also point to the same identity provider instead of continue with klick on create account below a redirect to the following url happends https matrix client login sso redirect register redirecturl https outcome what did you expect a redirect to https matrix client login sso redirect redirecturl https note the missing register in the path what happened instead synapse interprets the register as the idp id and fails at this point returning errcode m not found error unknown identity provider operating system any browser information any url for webapp develop element io just as a test if it can be reproduced there application version custom deployed version olm version homeserver synapse will you send logs no | 0 |
97,627 | 20,368,142,482 | IssuesEvent | 2022-02-21 08:35:19 | loyio/blog | https://api.github.com/repos/loyio/blog | closed | Problems 10 : Regular Expression Matching | Leetcode | Given an input string `s` and a pattern `p`, implement regular expression matching with support for `'.'` and `'*'` where:
- `'.'` Matches any single character.
- `'*'` Matches zero or more of the preceding element.
The matching should cover the entire input string (not partial).
Example 1:
```
Input: s = "aa", p = "a"
Output: false
Explanation: "a" does not match the entire string "aa".
```
Example 2:
```
Input: s = "aa", p = "a*"
Output: true
Explanation: '*' means zero or more of the preceding element, 'a'. Therefore, by repeating 'a' once, it becomes "aa".
```
Example 3:
```
Input: s = "ab", p = ".*"
Output: true
Explanation: ".*" means "zero or more (*) of any character (.)".
```
Constraints:
- 1 <= s.length <= 20
- 1 <= p.length <= 30
- s contains only lowercase English letters.
- p contains only lowercase English letters, '.', and '*'.
- It is guaranteed for each appearance of the character '*', there will be a previous valid character to match. | 1.0 | Problems 10 : Regular Expression Matching - Given an input string `s` and a pattern `p`, implement regular expression matching with support for `'.'` and `'*'` where:
- `'.'` Matches any single character.
- `'*'` Matches zero or more of the preceding element.
The matching should cover the entire input string (not partial).
Example 1:
```
Input: s = "aa", p = "a"
Output: false
Explanation: "a" does not match the entire string "aa".
```
Example 2:
```
Input: s = "aa", p = "a*"
Output: true
Explanation: '*' means zero or more of the preceding element, 'a'. Therefore, by repeating 'a' once, it becomes "aa".
```
Example 3:
```
Input: s = "ab", p = ".*"
Output: true
Explanation: ".*" means "zero or more (*) of any character (.)".
```
Constraints:
- 1 <= s.length <= 20
- 1 <= p.length <= 30
- s contains only lowercase English letters.
- p contains only lowercase English letters, '.', and '*'.
- It is guaranteed for each appearance of the character '*', there will be a previous valid character to match. | non_priority | problems regular expression matching given an input string s and a pattern p implement regular expression matching with support for and where matches any single character matches zero or more of the preceding element the matching should cover the entire input string not partial example input s aa p a output false explanation a does not match the entire string aa example input s aa p a output true explanation means zero or more of the preceding element a therefore by repeating a once it becomes aa example input s ab p output true explanation means zero or more of any character constraints s length p length s contains only lowercase english letters p contains only lowercase english letters and it is guaranteed for each appearance of the character there will be a previous valid character to match | 0 |
147,688 | 13,212,420,990 | IssuesEvent | 2020-08-16 06:54:17 | terrabasedb/docs | https://api.github.com/repos/terrabasedb/docs | closed | Document the latest iteration of the protocol | documentation enhancement | With the standardization of a new _stable_ protocol, it is necessary to document the latest protocol spec. Ref: terrabasedb/terrabase#12 | 1.0 | Document the latest iteration of the protocol - With the standardization of a new _stable_ protocol, it is necessary to document the latest protocol spec. Ref: terrabasedb/terrabase#12 | non_priority | document the latest iteration of the protocol with the standardization of a new stable protocol it is necessary to document the latest protocol spec ref terrabasedb terrabase | 0 |
335,572 | 24,472,858,589 | IssuesEvent | 2022-10-07 22:21:37 | theupdateframework/go-tuf | https://api.github.com/repos/theupdateframework/go-tuf | closed | Release notes don't display breaking changes obviously | documentation good first issue hacktoberfest | https://github.com/theupdateframework/go-tuf/pull/354 is marked as breaking:
- `refactor!` with a `!` in the conventional commit
- "breaking" box ticked in the PR
- "BREAKING CHANGE" in the PR description
However, it's in the [0.4.0](https://github.com/theupdateframework/go-tuf/releases/tag/v0.4.0) release, which doesn't call it out specifically. Should it?
(Or did I do something wrong?) | 1.0 | Release notes don't display breaking changes obviously - https://github.com/theupdateframework/go-tuf/pull/354 is marked as breaking:
- `refactor!` with a `!` in the conventional commit
- "breaking" box ticked in the PR
- "BREAKING CHANGE" in the PR description
However, it's in the [0.4.0](https://github.com/theupdateframework/go-tuf/releases/tag/v0.4.0) release, which doesn't call it out specifically. Should it?
(Or did I do something wrong?) | non_priority | release notes don t display breaking changes obviously is marked as breaking refactor with a in the conventional commit breaking box ticked in the pr breaking change in the pr description however it s in the release which doesn t call it out specifically should it or did i do something wrong | 0 |
18,520 | 12,975,720,480 | IssuesEvent | 2020-07-21 17:29:23 | geneontology/noctua | https://api.github.com/repos/geneontology/noctua | opened | Fix noctua graph client to handle model-level violations | bug (B: affects usability) | The violation checks in the current client code do not handle well (crash) model-level violations.
The code should: 1) crash less and 2) display the information.
Derived from https://github.com/geneontology/minerva/issues/330
A good description of the issue there. | True | Fix noctua graph client to handle model-level violations - The violation checks in the current client code do not handle well (crash) model-level violations.
The code should: 1) crash less and 2) display the information.
Derived from https://github.com/geneontology/minerva/issues/330
A good description of the issue there. | non_priority | fix noctua graph client to handle model level violations the violation checks in the current client code do not handle well crash model level violations the code should crash less and display the information derived from a good description of the issue there | 0 |
343,475 | 24,772,188,081 | IssuesEvent | 2022-10-23 09:27:20 | evennia/evennia | https://api.github.com/repos/evennia/evennia | closed | [Documentation] Installation instructions in 1.0 dev documentation result in installation of 0.9.5 version | documentation | #### Existing page / new
https://www.evennia.com/docs/1.0-dev/Setup/Installation-Git.html
#### Documentation issue
When you follow the instructions to install evennia in the 1.0 dev documentation, you end up installing the 0.9.5 version.
#### Suggested change
Maybe tell people to switch git branch in the installation steps while 1.0 is still in a distinct branch from master ?
Right now, the needed steps are only located in the "upgrading an existing installation" page. https://www.evennia.com/docs/1.0-dev/Setup/Installation-Upgrade.html
| 1.0 | [Documentation] Installation instructions in 1.0 dev documentation result in installation of 0.9.5 version - #### Existing page / new
https://www.evennia.com/docs/1.0-dev/Setup/Installation-Git.html
#### Documentation issue
When you follow the instructions to install evennia in the 1.0 dev documentation, you end up installing the 0.9.5 version.
#### Suggested change
Maybe tell people to switch git branch in the installation steps while 1.0 is still in a distinct branch from master ?
Right now, the needed steps are only located in the "upgrading an existing installation" page. https://www.evennia.com/docs/1.0-dev/Setup/Installation-Upgrade.html
| non_priority | installation instructions in dev documentation result in installation of version existing page new documentation issue when you follow the instructions to install evennia in the dev documentation you end up installing the version suggested change maybe tell people to switch git branch in the installation steps while is still in a distinct branch from master right now the needed steps are only located in the upgrading an existing installation page | 0 |
101,551 | 21,713,250,103 | IssuesEvent | 2022-05-10 15:29:12 | liuchang0812/liuchang0812.github.io | https://api.github.com/repos/liuchang0812/liuchang0812.github.io | opened | 2266. 统计打字方案数 | Liu Chang Blog | Gitalk /posts/tech/leetcode/leetcode2266/ | https://liuchang0812.github.io/posts/tech/leetcode/leetcode2266/
爬楼梯的加强版本,分别提前生成三个字母和四个字母的 fib 数组,然后分组统计后相乘。代码如下: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 | 2.0 | 2266. 统计打字方案数 | Liu Chang Blog - https://liuchang0812.github.io/posts/tech/leetcode/leetcode2266/
爬楼梯的加强版本,分别提前生成三个字母和四个字母的 fib 数组,然后分组统计后相乘。代码如下: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 | non_priority | 统计打字方案数 liu chang blog 爬楼梯的加强版本,分别提前生成三个字母和四个字母的 fib 数组,然后分组统计后相乘。代码如下: | 0 |
18,520 | 13,047,091,845 | IssuesEvent | 2020-07-29 10:05:10 | blockframes/blockframes | https://api.github.com/repos/blockframes/blockframes | closed | Configure ImgIx source for Staging & Prod | External services Infrastructure Ops Research TODO | To configure ImgIx source we need to be logged with our c8 account, then go to google cloud console then click on "use this as default project".
This means that we will not be able to configure sources for staging & prod without breaking our own personal dev source ???
For example:
- I'm logged as PL into google cloud console
- I click on "Use blockframes-pl as my default project" to create my own dev imgix source
- Then I want to create the staging, source
- I click on "Use blockframes-staging as my default project", but did this broke my own dev source ?
So we need to investigate and find a way to have imgix source for "non-dev" envs
- See ImgIx tutorial : https://docs.imgix.com/setup/creating-sources/google-cloud-storage
- our own tutorial : https://www.notion.so/cascade8/Setup-ImgIx-c73142c04f8349b4a6e17e74a9f2209a | 1.0 | Configure ImgIx source for Staging & Prod - To configure ImgIx source we need to be logged with our c8 account, then go to google cloud console then click on "use this as default project".
This means that we will not be able to configure sources for staging & prod without breaking our own personal dev source ???
For example:
- I'm logged as PL into google cloud console
- I click on "Use blockframes-pl as my default project" to create my own dev imgix source
- Then I want to create the staging, source
- I click on "Use blockframes-staging as my default project", but did this broke my own dev source ?
So we need to investigate and find a way to have imgix source for "non-dev" envs
- See ImgIx tutorial : https://docs.imgix.com/setup/creating-sources/google-cloud-storage
- our own tutorial : https://www.notion.so/cascade8/Setup-ImgIx-c73142c04f8349b4a6e17e74a9f2209a | non_priority | configure imgix source for staging prod to configure imgix source we need to be logged with our account then go to google cloud console then click on use this as default project this means that we will not be able to configure sources for staging prod without breaking our own personal dev source for example i m logged as pl into google cloud console i click on use blockframes pl as my default project to create my own dev imgix source then i want to create the staging source i click on use blockframes staging as my default project but did this broke my own dev source so we need to investigate and find a way to have imgix source for non dev envs see imgix tutorial our own tutorial | 0 |
1,373 | 3,689,650,726 | IssuesEvent | 2016-02-25 17:08:29 | Kujawadl/CSC_341_OS_Lab | https://api.github.com/repos/Kujawadl/CSC_341_OS_Lab | closed | Semaphore must be implemented | requirement | ### The semaphore must be implemented as follows:
- A binary semaphore [global boolean value defined in os.hpp (`extern bool semaphore;`) and declared in os.cpp (`bool semaphore = false; // Default value is unlocked`)].
- When a user issues `run` at the command line, the `bool semwait()` method is immediately called, the output of which determines if a swap has occurred and thus, if execution should continue. If a swap has occurred (i.e.: the current user was moved to the blockedQueue) the scheduler should output that information to the command line and reset `switchtime = sysclock + 3` *(because the dispatcher was called in the semwait() function, and thus we now have a new currentUser. Execution must continue within the `while (sysclock < switchtime)...` loop, because if we were to break from this loop and start the scheduler from its initial loop, the dispatcher would be called a second time, skipping a user. Thus, rather than shortening the life of the loop or breaking, we extend the life of the loop such that it will repeat for three more ticks.)*
- When the user's program encounters a halt (opcode 15, i.e.: IR code 61440), the `semsignal()` method is called, then the dispatcher is immediately called to switch to the next user.
- The dispatcher must be modified to take in a parameter indicating a signal it is receiving. This signal will be used to determine whether the current user is blocked or ready so the dispatcher can decide which queue to place them in on switch.
Algorithms:
```
dispatcher(int signal)
- Save machine registers into currentUser (save user state)
- If signal is BLOCKED (arbitrarily defined as some int), push currentUser onto blockedQueue
- Else if signal is READY (arbitrarily defined as some int), push currentUser onto readyQueue
- Set currentUser to readyQueue.front; pop front of readyQueue (get next user)
- Set machine registers to currentUser.regs (load user state)
semwait()
- If semaphore is unlocked, lock it and return true, indicating that the current user is OK to
run.
- If semaphore is locked, call dispatcher with blocking signal, indicating that the dispatcher
should place the current user in the blockedQueue, rather than the default readyQueue.
The dispatcher will then load the next user from the readyQueue. Return false, indicating
that the user has been sent to the blocked queue, and the run statement should not
continue to call the interpreter.
semsignal()
- If semaphore is locked, unlock it and move all items in blockedQueue into readyQueue.
- semsignal() should not be called unless the semaphore is locked, as this method indicates
that the semaphore is ready to be unlocked and all users waiting on the semaphore should
be moved to ready status.
``` | 1.0 | Semaphore must be implemented - ### The semaphore must be implemented as follows:
- A binary semaphore [global boolean value defined in os.hpp (`extern bool semaphore;`) and declared in os.cpp (`bool semaphore = false; // Default value is unlocked`)].
- When a user issues `run` at the command line, the `bool semwait()` method is immediately called, the output of which determines if a swap has occurred and thus, if execution should continue. If a swap has occurred (i.e.: the current user was moved to the blockedQueue) the scheduler should output that information to the command line and reset `switchtime = sysclock + 3` *(because the dispatcher was called in the semwait() function, and thus we now have a new currentUser. Execution must continue within the `while (sysclock < switchtime)...` loop, because if we were to break from this loop and start the scheduler from its initial loop, the dispatcher would be called a second time, skipping a user. Thus, rather than shortening the life of the loop or breaking, we extend the life of the loop such that it will repeat for three more ticks.)*
- When the user's program encounters a halt (opcode 15, i.e.: IR code 61440), the `semsignal()` method is called, then the dispatcher is immediately called to switch to the next user.
- The dispatcher must be modified to take in a parameter indicating a signal it is receiving. This signal will be used to determine whether the current user is blocked or ready so the dispatcher can decide which queue to place them in on switch.
Algorithms:
```
dispatcher(int signal)
- Save machine registers into currentUser (save user state)
- If signal is BLOCKED (arbitrarily defined as some int), push currentUser onto blockedQueue
- Else if signal is READY (arbitrarily defined as some int), push currentUser onto readyQueue
- Set currentUser to readyQueue.front; pop front of readyQueue (get next user)
- Set machine registers to currentUser.regs (load user state)
semwait()
- If semaphore is unlocked, lock it and return true, indicating that the current user is OK to
run.
- If semaphore is locked, call dispatcher with blocking signal, indicating that the dispatcher
should place the current user in the blockedQueue, rather than the default readyQueue.
The dispatcher will then load the next user from the readyQueue. Return false, indicating
that the user has been sent to the blocked queue, and the run statement should not
continue to call the interpreter.
semsignal()
- If semaphore is locked, unlock it and move all items in blockedQueue into readyQueue.
- semsignal() should not be called unless the semaphore is locked, as this method indicates
that the semaphore is ready to be unlocked and all users waiting on the semaphore should
be moved to ready status.
``` | non_priority | semaphore must be implemented the semaphore must be implemented as follows a binary semaphore when a user issues run at the command line the bool semwait method is immediately called the output of which determines if a swap has occurred and thus if execution should continue if a swap has occurred i e the current user was moved to the blockedqueue the scheduler should output that information to the command line and reset switchtime sysclock because the dispatcher was called in the semwait function and thus we now have a new currentuser execution must continue within the while sysclock switchtime loop because if we were to break from this loop and start the scheduler from its initial loop the dispatcher would be called a second time skipping a user thus rather than shortening the life of the loop or breaking we extend the life of the loop such that it will repeat for three more ticks when the user s program encounters a halt opcode i e ir code the semsignal method is called then the dispatcher is immediately called to switch to the next user the dispatcher must be modified to take in a parameter indicating a signal it is receiving this signal will be used to determine whether the current user is blocked or ready so the dispatcher can decide which queue to place them in on switch algorithms dispatcher int signal save machine registers into currentuser save user state if signal is blocked arbitrarily defined as some int push currentuser onto blockedqueue else if signal is ready arbitrarily defined as some int push currentuser onto readyqueue set currentuser to readyqueue front pop front of readyqueue get next user set machine registers to currentuser regs load user state semwait if semaphore is unlocked lock it and return true indicating that the current user is ok to run if semaphore is locked call dispatcher with blocking signal indicating that the dispatcher should place the current user in the blockedqueue rather than the default readyqueue the dispatcher will then load the next user from the readyqueue return false indicating that the user has been sent to the blocked queue and the run statement should not continue to call the interpreter semsignal if semaphore is locked unlock it and move all items in blockedqueue into readyqueue semsignal should not be called unless the semaphore is locked as this method indicates that the semaphore is ready to be unlocked and all users waiting on the semaphore should be moved to ready status | 0 |
8,206 | 3,145,938,087 | IssuesEvent | 2015-09-14 20:24:56 | openaire/iis | https://api.github.com/repos/openaire/iis | opened | Migrate diffs in iis-3rdparty-* modules from SVN repo | a: documentation f: core | Our patched/hacked versions of 3rd party code should contain the original code along with the patch that was applied. This is how it was done in the SVN repo; however, it wasn't migrated to GitHub.
Remember to update README files in the updated Maven projects appropriately. | 1.0 | Migrate diffs in iis-3rdparty-* modules from SVN repo - Our patched/hacked versions of 3rd party code should contain the original code along with the patch that was applied. This is how it was done in the SVN repo; however, it wasn't migrated to GitHub.
Remember to update README files in the updated Maven projects appropriately. | non_priority | migrate diffs in iis modules from svn repo our patched hacked versions of party code should contain the original code along with the patch that was applied this is how it was done in the svn repo however it wasn t migrated to github remember to update readme files in the updated maven projects appropriately | 0 |
92,503 | 15,857,087,093 | IssuesEvent | 2021-04-08 03:56:08 | f00b4rb00f/test-project | https://api.github.com/repos/f00b4rb00f/test-project | opened | WS-2019-0063 (High) detected in js-yaml-3.6.1.tgz, js-yaml-3.4.6.tgz | security vulnerability | ## WS-2019-0063 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>js-yaml-3.6.1.tgz</b>, <b>js-yaml-3.4.6.tgz</b></p></summary>
<p>
<details><summary><b>js-yaml-3.6.1.tgz</b></p></summary>
<p>YAML 1.2 parser and serializer</p>
<p>Library home page: <a href="https://registry.npmjs.org/js-yaml/-/js-yaml-3.6.1.tgz">https://registry.npmjs.org/js-yaml/-/js-yaml-3.6.1.tgz</a></p>
<p>Path to dependency file: /test-project/attacker-app/package.json</p>
<p>Path to vulnerable library: test-project/attacker-app/node_modules/js-yaml/package.json,test-project/attacker-app/node_modules/js-yaml/package.json</p>
<p>
Dependency Hierarchy:
- karma-coverage-0.4.2.tgz (Root Library)
- istanbul-0.3.22.tgz
- :x: **js-yaml-3.6.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>js-yaml-3.4.6.tgz</b></p></summary>
<p>YAML 1.2 parser and serializer</p>
<p>Library home page: <a href="https://registry.npmjs.org/js-yaml/-/js-yaml-3.4.6.tgz">https://registry.npmjs.org/js-yaml/-/js-yaml-3.4.6.tgz</a></p>
<p>Path to dependency file: /test-project/attacker-app/package.json</p>
<p>Path to vulnerable library: test-project/node_modules/jscs/node_modules/js-yaml/package.json,test-project/node_modules/jscs/node_modules/js-yaml/package.json</p>
<p>
Dependency Hierarchy:
- gulp-jscs-2.0.0.tgz (Root Library)
- jscs-2.11.0.tgz
- :x: **js-yaml-3.4.6.tgz** (Vulnerable Library)
</details>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Js-yaml prior to 3.13.1 are vulnerable to Code Injection. The load() function may execute arbitrary code injected through a malicious YAML file.
<p>Publish Date: 2019-04-05
<p>URL: <a href=https://github.com/nodeca/js-yaml/pull/480>WS-2019-0063</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>8.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/813">https://www.npmjs.com/advisories/813</a></p>
<p>Release Date: 2019-04-05</p>
<p>Fix Resolution: js-yaml - 3.13.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | WS-2019-0063 (High) detected in js-yaml-3.6.1.tgz, js-yaml-3.4.6.tgz - ## WS-2019-0063 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>js-yaml-3.6.1.tgz</b>, <b>js-yaml-3.4.6.tgz</b></p></summary>
<p>
<details><summary><b>js-yaml-3.6.1.tgz</b></p></summary>
<p>YAML 1.2 parser and serializer</p>
<p>Library home page: <a href="https://registry.npmjs.org/js-yaml/-/js-yaml-3.6.1.tgz">https://registry.npmjs.org/js-yaml/-/js-yaml-3.6.1.tgz</a></p>
<p>Path to dependency file: /test-project/attacker-app/package.json</p>
<p>Path to vulnerable library: test-project/attacker-app/node_modules/js-yaml/package.json,test-project/attacker-app/node_modules/js-yaml/package.json</p>
<p>
Dependency Hierarchy:
- karma-coverage-0.4.2.tgz (Root Library)
- istanbul-0.3.22.tgz
- :x: **js-yaml-3.6.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>js-yaml-3.4.6.tgz</b></p></summary>
<p>YAML 1.2 parser and serializer</p>
<p>Library home page: <a href="https://registry.npmjs.org/js-yaml/-/js-yaml-3.4.6.tgz">https://registry.npmjs.org/js-yaml/-/js-yaml-3.4.6.tgz</a></p>
<p>Path to dependency file: /test-project/attacker-app/package.json</p>
<p>Path to vulnerable library: test-project/node_modules/jscs/node_modules/js-yaml/package.json,test-project/node_modules/jscs/node_modules/js-yaml/package.json</p>
<p>
Dependency Hierarchy:
- gulp-jscs-2.0.0.tgz (Root Library)
- jscs-2.11.0.tgz
- :x: **js-yaml-3.4.6.tgz** (Vulnerable Library)
</details>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Js-yaml prior to 3.13.1 are vulnerable to Code Injection. The load() function may execute arbitrary code injected through a malicious YAML file.
<p>Publish Date: 2019-04-05
<p>URL: <a href=https://github.com/nodeca/js-yaml/pull/480>WS-2019-0063</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>8.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/813">https://www.npmjs.com/advisories/813</a></p>
<p>Release Date: 2019-04-05</p>
<p>Fix Resolution: js-yaml - 3.13.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | ws high detected in js yaml tgz js yaml tgz ws high severity vulnerability vulnerable libraries js yaml tgz js yaml tgz js yaml tgz yaml parser and serializer library home page a href path to dependency file test project attacker app package json path to vulnerable library test project attacker app node modules js yaml package json test project attacker app node modules js yaml package json dependency hierarchy karma coverage tgz root library istanbul tgz x js yaml tgz vulnerable library js yaml tgz yaml parser and serializer library home page a href path to dependency file test project attacker app package json path to vulnerable library test project node modules jscs node modules js yaml package json test project node modules jscs node modules js yaml package json dependency hierarchy gulp jscs tgz root library jscs tgz x js yaml tgz vulnerable library vulnerability details js yaml prior to are vulnerable to code injection the load function may execute arbitrary code injected through a malicious yaml file publish date url a href cvss score details base score metrics not available suggested fix type upgrade version origin a href release date fix resolution js yaml step up your open source security game with whitesource | 0 |
198,872 | 15,007,787,575 | IssuesEvent | 2021-01-31 06:48:40 | team-nextep/facial-expression-battle | https://api.github.com/repos/team-nextep/facial-expression-battle | closed | 出せそうなコンテストを列挙する | contest | ## 背景
- せっかく作ったから、どこかのコンテストなどに出してみたい
- 去年宮岸が作った作品は、割と片っ端からコンテストに応募して、いくつか審査に残ったりもして、良かった
## 今年の出せそうなコンテストリスト(随時追加)
- [e-ZUKAスマートフォンアプリコンテスト 2020](https://compe.japandesign.ne.jp/e-zuka-appli-2020/) 締切: 2020年09月15日
- [にいがたデジコングランプリ 2020](https://compe.japandesign.ne.jp/niigata-digicon-2020/) 締切: 2020年09月18日
- [CREATIVE HACK AWARD 2020](https://compe.japandesign.ne.jp/creative-hack-award-2020/) 締切: 2020年09月25日
- [2020 アジアデジタルアート大賞展 FUKUOKA](https://compe.japandesign.ne.jp/asia-digital-art-2020/) 締切: 2020年10月11日
- [いばらきデジタルコンテンツ・ソフトウェア大賞 2020](https://compe.japandesign.ne.jp/ibaraki-digicon-2020/) 締切: 2020年10月31日
- [ヒーローズ・リーグ オンライン2020](https://heroes-league.net/) 締切: 2020年11月16日 | 1.0 | 出せそうなコンテストを列挙する - ## 背景
- せっかく作ったから、どこかのコンテストなどに出してみたい
- 去年宮岸が作った作品は、割と片っ端からコンテストに応募して、いくつか審査に残ったりもして、良かった
## 今年の出せそうなコンテストリスト(随時追加)
- [e-ZUKAスマートフォンアプリコンテスト 2020](https://compe.japandesign.ne.jp/e-zuka-appli-2020/) 締切: 2020年09月15日
- [にいがたデジコングランプリ 2020](https://compe.japandesign.ne.jp/niigata-digicon-2020/) 締切: 2020年09月18日
- [CREATIVE HACK AWARD 2020](https://compe.japandesign.ne.jp/creative-hack-award-2020/) 締切: 2020年09月25日
- [2020 アジアデジタルアート大賞展 FUKUOKA](https://compe.japandesign.ne.jp/asia-digital-art-2020/) 締切: 2020年10月11日
- [いばらきデジタルコンテンツ・ソフトウェア大賞 2020](https://compe.japandesign.ne.jp/ibaraki-digicon-2020/) 締切: 2020年10月31日
- [ヒーローズ・リーグ オンライン2020](https://heroes-league.net/) 締切: 2020年11月16日 | non_priority | 出せそうなコンテストを列挙する 背景 せっかく作ったから、どこかのコンテストなどに出してみたい 去年宮岸が作った作品は、割と片っ端からコンテストに応募して、いくつか審査に残ったりもして、良かった 今年の出せそうなコンテストリスト 随時追加 締切 締切 締切 締切 締切 締切 | 0 |
91,724 | 8,317,264,300 | IssuesEvent | 2018-09-25 11:33:02 | Wohlstand/libADLMIDI | https://api.github.com/repos/Wohlstand/libADLMIDI | closed | Add the way to change single instrument of currently-loaded bank on the fly. | Need a test enhancement | This will allow to use libADLMIDI directly how for OPL3 Bank Editor's backend to change instruments on the fly to test them, or give the ability to use libADLMIDI as VTS-plugin for the musical software.
* - [x] Stop to clean/resize the dynamical instruments data arrays. Instead, override them.
* - [x] Instread of direct access to the generated database, copy instruments of currently choosen embedded bank into dynamical array which is easy to patch.
* - [x] Make instruments store be pre-allocatable which will allow to avoid any reallocations in the real-time when sending instruments on the fly into over-GM range.
* - [x] Add the instrument structure (probably, copy-paste from wopl_file.h from the OPL3 Bank Editor the single-instrument structure) and the function to receive it's bank MSB/LSB, Patch number and type of the instrument (melodic or percussion). | 1.0 | Add the way to change single instrument of currently-loaded bank on the fly. - This will allow to use libADLMIDI directly how for OPL3 Bank Editor's backend to change instruments on the fly to test them, or give the ability to use libADLMIDI as VTS-plugin for the musical software.
* - [x] Stop to clean/resize the dynamical instruments data arrays. Instead, override them.
* - [x] Instread of direct access to the generated database, copy instruments of currently choosen embedded bank into dynamical array which is easy to patch.
* - [x] Make instruments store be pre-allocatable which will allow to avoid any reallocations in the real-time when sending instruments on the fly into over-GM range.
* - [x] Add the instrument structure (probably, copy-paste from wopl_file.h from the OPL3 Bank Editor the single-instrument structure) and the function to receive it's bank MSB/LSB, Patch number and type of the instrument (melodic or percussion). | non_priority | add the way to change single instrument of currently loaded bank on the fly this will allow to use libadlmidi directly how for bank editor s backend to change instruments on the fly to test them or give the ability to use libadlmidi as vts plugin for the musical software stop to clean resize the dynamical instruments data arrays instead override them instread of direct access to the generated database copy instruments of currently choosen embedded bank into dynamical array which is easy to patch make instruments store be pre allocatable which will allow to avoid any reallocations in the real time when sending instruments on the fly into over gm range add the instrument structure probably copy paste from wopl file h from the bank editor the single instrument structure and the function to receive it s bank msb lsb patch number and type of the instrument melodic or percussion | 0 |
40,522 | 10,028,659,613 | IssuesEvent | 2019-07-17 12:15:27 | jOOQ/jOOQ | https://api.github.com/repos/jOOQ/jOOQ | closed | Parser.parseStatements() fails to parse empty block | C: Parser E: All Editions P: Medium R: Fixed T: Defect | This doesn't parse neither using `ParserCLI` nor on https://www.jooq.org/translate
```sql
begin
null;
end;
```
The error we're getting is:
```
Variable name expected: [3:5] begin
null;
end;[*]
``` | 1.0 | Parser.parseStatements() fails to parse empty block - This doesn't parse neither using `ParserCLI` nor on https://www.jooq.org/translate
```sql
begin
null;
end;
```
The error we're getting is:
```
Variable name expected: [3:5] begin
null;
end;[*]
``` | non_priority | parser parsestatements fails to parse empty block this doesn t parse neither using parsercli nor on sql begin null end the error we re getting is variable name expected begin null end | 0 |
255,325 | 27,484,907,598 | IssuesEvent | 2023-03-04 01:33:09 | panasalap/linux-4.1.15 | https://api.github.com/repos/panasalap/linux-4.1.15 | closed | CVE-2017-14051 (Medium) detected in linuxlinux-4.1.17 - autoclosed | security vulnerability | ## CVE-2017-14051 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.1.17</b></p></summary>
<p>
<p>Apache Software Foundation (ASF)</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in 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>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/scsi/qla2xxx/qla_attr.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>
An integer overflow in the qla2x00_sysfs_write_optrom_ctl function in drivers/scsi/qla2xxx/qla_attr.c in the Linux kernel through 4.12.10 allows local users to cause a denial of service (memory corruption and system crash) by leveraging root access.
<p>Publish Date: 2017-08-31
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-14051>CVE-2017-14051</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="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-14051">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-14051</a></p>
<p>Release Date: 2017-08-31</p>
<p>Fix Resolution: v4.14-rc1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2017-14051 (Medium) detected in linuxlinux-4.1.17 - autoclosed - ## CVE-2017-14051 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.1.17</b></p></summary>
<p>
<p>Apache Software Foundation (ASF)</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in 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>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/scsi/qla2xxx/qla_attr.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>
An integer overflow in the qla2x00_sysfs_write_optrom_ctl function in drivers/scsi/qla2xxx/qla_attr.c in the Linux kernel through 4.12.10 allows local users to cause a denial of service (memory corruption and system crash) by leveraging root access.
<p>Publish Date: 2017-08-31
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-14051>CVE-2017-14051</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="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-14051">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-14051</a></p>
<p>Release Date: 2017-08-31</p>
<p>Fix Resolution: v4.14-rc1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in linuxlinux autoclosed cve medium severity vulnerability vulnerable library linuxlinux apache software foundation asf library home page a href found in head commit a href found in base branch master vulnerable source files drivers scsi qla attr c vulnerability details an integer overflow in the sysfs write optrom ctl function in drivers scsi qla attr c in the linux kernel through allows local users to cause a denial of service memory corruption and system crash by leveraging root access 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 step up your open source security game with mend | 0 |
8,781 | 23,434,733,064 | IssuesEvent | 2022-08-15 08:31:39 | facebook/react-native | https://api.github.com/repos/facebook/react-native | opened | [Android] createShadowNodeInstance function is not called | Needs: Triage :mag: Type: New Architecture | ### Description
In my library, I would like to update native parent view (probably it is called HostView), when react native child dimensions changed. I implemented it using `onLayoutChange` method but I would like to do it in synchronous manner. I just wanted to use shadow nodes for it, but for some reason it does not work, when fabric is enabled.
I checked all versions of RN from 68 and this issue occurs on all of them
### Version
> 68
### Output of `npx react-native info`
System:
OS: macOS 12.1
CPU: (10) arm64 Apple M1 Pro
Memory: 128.70 MB / 32.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.16.0 - ~/.nvm/versions/node/v16.16.0/bin/node
Yarn: 1.22.19 - ~/.nvm/versions/node/v16.16.0/bin/yarn
npm: 8.11.0 - ~/.nvm/versions/node/v16.16.0/bin/npm
Watchman: Not Found
Managers:
CocoaPods: 1.11.2 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.2, iOS 15.2, macOS 12.1, tvOS 15.2, watchOS 8.3
Android SDK:
Android NDK: 24.0.8215888
IDEs:
Android Studio: 2021.2 AI-212.5712.43.2112.8815526
Xcode: 13.2.1/13C100 - /usr/bin/xcodebuild
Languages:
Java: 11.0.15 - sdkman/candidates/java/current/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: Not Found
react-native: Not Found
react-native-macos: Not Found
npmGlobalPackages:
### Steps to reproduce
Apply below diff into RNTester
```
diff --git a/packages/rn-tester/android/app/src/main/java/com/facebook/react/uiapp/component/MyNativeViewManager.java b/packages/rn-tester/android/app/src/main/java/com/facebook/react/uiapp/component/MyNativeViewManager.java
index d8c8b731acb..d4de933f629 100644
--- a/packages/rn-tester/android/app/src/main/java/com/facebook/react/uiapp/component/MyNativeViewManager.java
+++ b/packages/rn-tester/android/app/src/main/java/com/facebook/react/uiapp/component/MyNativeViewManager.java
@@ -8,6 +8,8 @@
package com.facebook.react.uiapp.component;
import android.graphics.Color;
+import android.util.Log;
+
import androidx.annotation.NonNull;
import androidx.annotation.Nullable;
import com.facebook.react.bridge.ReadableArray;
@@ -19,6 +21,11 @@ import com.facebook.react.uimanager.ViewProps;
import com.facebook.react.uimanager.annotations.ReactProp;
import com.facebook.react.viewmanagers.RNTMyNativeViewManagerDelegate;
import com.facebook.react.viewmanagers.RNTMyNativeViewManagerInterface;
+import com.facebook.react.uimanager.LayoutShadowNode;
+import com.facebook.yoga.YogaMeasureFunction;
+import com.facebook.yoga.YogaMeasureMode;
+import com.facebook.yoga.YogaMeasureOutput;
+import com.facebook.yoga.YogaNode;
/** View manager for {@link MyNativeView} components. */
@ReactModule(name = MyNativeViewManager.REACT_CLASS)
@@ -27,6 +34,25 @@ public class MyNativeViewManager extends SimpleViewManager<MyNativeView>
public static final String REACT_CLASS = "RNTMyNativeView";
+ public static class ExampleShadowNode extends LayoutShadowNode implements
+ YogaMeasureFunction {
+
+ public ExampleShadowNode() {
+ Log.d("", "ExampleShadowNode: ");
+ }
+ @Override
+ public long measure(
+ YogaNode node,
+ float width,
+ YogaMeasureMode widthMode,
+ float height,
+ YogaMeasureMode heightMode) {
+
+ return YogaMeasureOutput.make(width, height);
+ }
+
+ }
+
private final ViewManagerDelegate<MyNativeView> mDelegate;
public MyNativeViewManager() {
@@ -51,6 +77,16 @@ public class MyNativeViewManager extends SimpleViewManager<MyNativeView>
return new MyNativeView(reactContext);
}
+ @Override
+ public LayoutShadowNode createShadowNodeInstance() {
+ return new ExampleShadowNode();
+ }
+
+ @Override
+ public Class getShadowNodeClass() {
+ return ExampleShadowNode.class;
+ }
+
@Override
public void receiveCommand(
@NonNull MyNativeView view, String commandName, @Nullable ReadableArray args) {
```
### Current State:
`ExampleShadowNode` is not called
### Current State:
`ExampleShadowNode` should have been called
### Snack, code example, screenshot, or link to a repository
https://github.com/callstack/react-native-slider/pull/410 | 1.0 | [Android] createShadowNodeInstance function is not called - ### Description
In my library, I would like to update native parent view (probably it is called HostView), when react native child dimensions changed. I implemented it using `onLayoutChange` method but I would like to do it in synchronous manner. I just wanted to use shadow nodes for it, but for some reason it does not work, when fabric is enabled.
I checked all versions of RN from 68 and this issue occurs on all of them
### Version
> 68
### Output of `npx react-native info`
System:
OS: macOS 12.1
CPU: (10) arm64 Apple M1 Pro
Memory: 128.70 MB / 32.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.16.0 - ~/.nvm/versions/node/v16.16.0/bin/node
Yarn: 1.22.19 - ~/.nvm/versions/node/v16.16.0/bin/yarn
npm: 8.11.0 - ~/.nvm/versions/node/v16.16.0/bin/npm
Watchman: Not Found
Managers:
CocoaPods: 1.11.2 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.2, iOS 15.2, macOS 12.1, tvOS 15.2, watchOS 8.3
Android SDK:
Android NDK: 24.0.8215888
IDEs:
Android Studio: 2021.2 AI-212.5712.43.2112.8815526
Xcode: 13.2.1/13C100 - /usr/bin/xcodebuild
Languages:
Java: 11.0.15 - sdkman/candidates/java/current/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: Not Found
react-native: Not Found
react-native-macos: Not Found
npmGlobalPackages:
### Steps to reproduce
Apply below diff into RNTester
```
diff --git a/packages/rn-tester/android/app/src/main/java/com/facebook/react/uiapp/component/MyNativeViewManager.java b/packages/rn-tester/android/app/src/main/java/com/facebook/react/uiapp/component/MyNativeViewManager.java
index d8c8b731acb..d4de933f629 100644
--- a/packages/rn-tester/android/app/src/main/java/com/facebook/react/uiapp/component/MyNativeViewManager.java
+++ b/packages/rn-tester/android/app/src/main/java/com/facebook/react/uiapp/component/MyNativeViewManager.java
@@ -8,6 +8,8 @@
package com.facebook.react.uiapp.component;
import android.graphics.Color;
+import android.util.Log;
+
import androidx.annotation.NonNull;
import androidx.annotation.Nullable;
import com.facebook.react.bridge.ReadableArray;
@@ -19,6 +21,11 @@ import com.facebook.react.uimanager.ViewProps;
import com.facebook.react.uimanager.annotations.ReactProp;
import com.facebook.react.viewmanagers.RNTMyNativeViewManagerDelegate;
import com.facebook.react.viewmanagers.RNTMyNativeViewManagerInterface;
+import com.facebook.react.uimanager.LayoutShadowNode;
+import com.facebook.yoga.YogaMeasureFunction;
+import com.facebook.yoga.YogaMeasureMode;
+import com.facebook.yoga.YogaMeasureOutput;
+import com.facebook.yoga.YogaNode;
/** View manager for {@link MyNativeView} components. */
@ReactModule(name = MyNativeViewManager.REACT_CLASS)
@@ -27,6 +34,25 @@ public class MyNativeViewManager extends SimpleViewManager<MyNativeView>
public static final String REACT_CLASS = "RNTMyNativeView";
+ public static class ExampleShadowNode extends LayoutShadowNode implements
+ YogaMeasureFunction {
+
+ public ExampleShadowNode() {
+ Log.d("", "ExampleShadowNode: ");
+ }
+ @Override
+ public long measure(
+ YogaNode node,
+ float width,
+ YogaMeasureMode widthMode,
+ float height,
+ YogaMeasureMode heightMode) {
+
+ return YogaMeasureOutput.make(width, height);
+ }
+
+ }
+
private final ViewManagerDelegate<MyNativeView> mDelegate;
public MyNativeViewManager() {
@@ -51,6 +77,16 @@ public class MyNativeViewManager extends SimpleViewManager<MyNativeView>
return new MyNativeView(reactContext);
}
+ @Override
+ public LayoutShadowNode createShadowNodeInstance() {
+ return new ExampleShadowNode();
+ }
+
+ @Override
+ public Class getShadowNodeClass() {
+ return ExampleShadowNode.class;
+ }
+
@Override
public void receiveCommand(
@NonNull MyNativeView view, String commandName, @Nullable ReadableArray args) {
```
### Current State:
`ExampleShadowNode` is not called
### Current State:
`ExampleShadowNode` should have been called
### Snack, code example, screenshot, or link to a repository
https://github.com/callstack/react-native-slider/pull/410 | non_priority | createshadownodeinstance function is not called description in my library i would like to update native parent view probably it is called hostview when react native child dimensions changed i implemented it using onlayoutchange method but i would like to do it in synchronous manner i just wanted to use shadow nodes for it but for some reason it does not work when fabric is enabled i checked all versions of rn from and this issue occurs on all of them version output of npx react native info system os macos cpu apple pro memory mb gb shell bin zsh binaries node nvm versions node bin node yarn nvm versions node bin yarn npm nvm versions node bin npm watchman not found managers cocoapods opt homebrew bin pod sdks ios sdk platforms driverkit ios macos tvos watchos android sdk android ndk ides android studio ai xcode usr bin xcodebuild languages java sdkman candidates java current bin javac npmpackages react native community cli not found react not found react native not found react native macos not found npmglobalpackages steps to reproduce apply below diff into rntester diff git a packages rn tester android app src main java com facebook react uiapp component mynativeviewmanager java b packages rn tester android app src main java com facebook react uiapp component mynativeviewmanager java index a packages rn tester android app src main java com facebook react uiapp component mynativeviewmanager java b packages rn tester android app src main java com facebook react uiapp component mynativeviewmanager java package com facebook react uiapp component import android graphics color import android util log import androidx annotation nonnull import androidx annotation nullable import com facebook react bridge readablearray import com facebook react uimanager viewprops import com facebook react uimanager annotations reactprop import com facebook react viewmanagers rntmynativeviewmanagerdelegate import com facebook react viewmanagers rntmynativeviewmanagerinterface import com facebook react uimanager layoutshadownode import com facebook yoga yogameasurefunction import com facebook yoga yogameasuremode import com facebook yoga yogameasureoutput import com facebook yoga yoganode view manager for link mynativeview components reactmodule name mynativeviewmanager react class public class mynativeviewmanager extends simpleviewmanager public static final string react class rntmynativeview public static class exampleshadownode extends layoutshadownode implements yogameasurefunction public exampleshadownode log d exampleshadownode override public long measure yoganode node float width yogameasuremode widthmode float height yogameasuremode heightmode return yogameasureoutput make width height private final viewmanagerdelegate mdelegate public mynativeviewmanager public class mynativeviewmanager extends simpleviewmanager return new mynativeview reactcontext override public layoutshadownode createshadownodeinstance return new exampleshadownode override public class getshadownodeclass return exampleshadownode class override public void receivecommand nonnull mynativeview view string commandname nullable readablearray args current state exampleshadownode is not called current state exampleshadownode should have been called snack code example screenshot or link to a repository | 0 |
294,741 | 22,161,933,203 | IssuesEvent | 2022-06-04 16:21:59 | timescale/docs | https://api.github.com/repos/timescale/docs | closed | [Site Bug] Typo on page: /timescaledb/latest/how-to-guides/schema-management/about-schemas/ | bug documentation |
# Describe the bug
Just a small typo
## What do the docs say now?
"In this case, you can PostgreSQL JSON and JSONB data types."
## What should the docs say?
"In this case, you can **use** PostgreSQL JSON and JSONB data types."
# Page affected
https://docs.timescale.com/timescaledb/latest/how-to-guides/schema-management/about-schemas/#table-management
# Version affected
`latest`
# Subject matter expert (SME)
N/A
# Screenshots

# Any further info
N/A
| 1.0 | [Site Bug] Typo on page: /timescaledb/latest/how-to-guides/schema-management/about-schemas/ -
# Describe the bug
Just a small typo
## What do the docs say now?
"In this case, you can PostgreSQL JSON and JSONB data types."
## What should the docs say?
"In this case, you can **use** PostgreSQL JSON and JSONB data types."
# Page affected
https://docs.timescale.com/timescaledb/latest/how-to-guides/schema-management/about-schemas/#table-management
# Version affected
`latest`
# Subject matter expert (SME)
N/A
# Screenshots

# Any further info
N/A
| non_priority | typo on page timescaledb latest how to guides schema management about schemas describe the bug just a small typo what do the docs say now in this case you can postgresql json and jsonb data types what should the docs say in this case you can use postgresql json and jsonb data types page affected version affected latest subject matter expert sme n a screenshots any further info n a | 0 |
23,925 | 11,985,479,791 | IssuesEvent | 2020-04-07 17:34:49 | Azure/azure-sdk-for-net | https://api.github.com/repos/Azure/azure-sdk-for-net | closed | [BUG] Event Grid not publishing updated package | Client Event Grid Service Attention customer-reported question | **Describe the bug**
I've installed the latest version 3.2.0 of [Microsoft.Azure.EventGrid](https://www.nuget.org/packages/Microsoft.Azure.EventGrid/3.2.0) from nuget.org. The publish date is almost a year old. Data Lake v2 has introduced new fields in the `StorageBlobCreatedEventData` model that aren't present in the package.
**Expected behavior**
Specifically, I expect `ContentOffset` to be present in the package, since it's [in the repo](https://github.com/Azure/azure-sdk-for-net/blob/c530a249ee92cee2be108162e6392aa1a4b04838/sdk/eventgrid/Microsoft.Azure.EventGrid/src/Generated/Models/StorageBlobCreatedEventData.cs#L131) but it's not there.
I would expect either a more updated package, either stable or the prerelease version referenced in the assembly.
**Actual behavior (include Exception or Stack Trace)**
The `StorageBlobCreatedEventData` class in the package doesn't have this field

**To Reproduce**
Download the package.
**Environment:**
- Name and version of the Library package used: Microsoft.Azure.EventGrid 3.2.0
- Hosting platform or OS and .NET runtime version (`dotnet --info` output for .NET Core projects): .NET Core SDK (reflecting any global.json):
Version: 3.1.101
Commit: b377529961
Runtime Environment:
OS Name: Windows
OS Version: 10.0.18363
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\3.1.101\
Host (useful for support):
Version: 3.1.1
Commit: a1388f194c
.NET Core SDKs installed:
2.1.511 [C:\Program Files\dotnet\sdk]
2.1.512 [C:\Program Files\dotnet\sdk]
2.1.801 [C:\Program Files\dotnet\sdk]
2.2.401 [C:\Program Files\dotnet\sdk]
3.1.101 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.15 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.16 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.15 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.16 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.15 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.16 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.1 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
- IDE and version : Visual Studio Enterprise Version 16.4.6 | 1.0 | [BUG] Event Grid not publishing updated package - **Describe the bug**
I've installed the latest version 3.2.0 of [Microsoft.Azure.EventGrid](https://www.nuget.org/packages/Microsoft.Azure.EventGrid/3.2.0) from nuget.org. The publish date is almost a year old. Data Lake v2 has introduced new fields in the `StorageBlobCreatedEventData` model that aren't present in the package.
**Expected behavior**
Specifically, I expect `ContentOffset` to be present in the package, since it's [in the repo](https://github.com/Azure/azure-sdk-for-net/blob/c530a249ee92cee2be108162e6392aa1a4b04838/sdk/eventgrid/Microsoft.Azure.EventGrid/src/Generated/Models/StorageBlobCreatedEventData.cs#L131) but it's not there.
I would expect either a more updated package, either stable or the prerelease version referenced in the assembly.
**Actual behavior (include Exception or Stack Trace)**
The `StorageBlobCreatedEventData` class in the package doesn't have this field

**To Reproduce**
Download the package.
**Environment:**
- Name and version of the Library package used: Microsoft.Azure.EventGrid 3.2.0
- Hosting platform or OS and .NET runtime version (`dotnet --info` output for .NET Core projects): .NET Core SDK (reflecting any global.json):
Version: 3.1.101
Commit: b377529961
Runtime Environment:
OS Name: Windows
OS Version: 10.0.18363
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\3.1.101\
Host (useful for support):
Version: 3.1.1
Commit: a1388f194c
.NET Core SDKs installed:
2.1.511 [C:\Program Files\dotnet\sdk]
2.1.512 [C:\Program Files\dotnet\sdk]
2.1.801 [C:\Program Files\dotnet\sdk]
2.2.401 [C:\Program Files\dotnet\sdk]
3.1.101 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.15 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.16 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.15 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.16 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.15 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.16 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.1 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
- IDE and version : Visual Studio Enterprise Version 16.4.6 | non_priority | event grid not publishing updated package describe the bug i ve installed the latest version of from nuget org the publish date is almost a year old data lake has introduced new fields in the storageblobcreatedeventdata model that aren t present in the package expected behavior specifically i expect contentoffset to be present in the package since it s but it s not there i would expect either a more updated package either stable or the prerelease version referenced in the assembly actual behavior include exception or stack trace the storageblobcreatedeventdata class in the package doesn t have this field to reproduce download the package environment name and version of the library package used microsoft azure eventgrid hosting platform or os and net runtime version dotnet info output for net core projects net core sdk reflecting any global json version commit runtime environment os name windows os version os platform windows rid base path c program files dotnet sdk host useful for support version commit net core sdks installed net core runtimes installed microsoft aspnetcore all microsoft aspnetcore all microsoft aspnetcore all microsoft aspnetcore all microsoft aspnetcore all microsoft aspnetcore app microsoft aspnetcore app microsoft aspnetcore app microsoft aspnetcore app microsoft aspnetcore app microsoft aspnetcore app microsoft netcore app microsoft netcore app microsoft netcore app microsoft netcore app microsoft netcore app microsoft netcore app microsoft windowsdesktop app ide and version visual studio enterprise version | 0 |
27,253 | 6,824,192,574 | IssuesEvent | 2017-11-08 04:29:34 | lmk123/blog | https://api.github.com/repos/lmk123/blog | opened | 于是我从 WebStorm 转向了 VS Code | TypeScript VS Code WebStorm | 自从大学以来,我换了不少编辑器。一开始学习 C# 的时候,用的是 [Visual Studio](https://www.visualstudio.com),这款编辑器确实非常好用,即使是用来写 JavaScript 也有很全的代码提示。
后来我决定专攻前端开发,这时候 Visual Studio 就显得太过于笨重了。在学校老师的建议下,我开始用 [Dreamweaver](http://www.adobe.com/cn/products/dreamweaver.html),老师极力推荐它的原因是它的「所见即所得」特性——不需要自己写代码,只需要拖一些控件进去,它就会自动帮你生成页面……可是它生成的代码也太差劲了,我从来没拖过控件,代码提示也不如 Visual Studio 全面,时不时的还会卡顿。
再后来,我在网友的推荐下开始用 [WebStorm](https://www.jetbrains.com/webstorm/),简直爱不释手,于是从此再也没有换过编辑器——
直到半个月前,我试了一下 [VS Code](https://code.visualstudio.com/)。
让我决定去尝试一下 VS Code 原因倒不是因为这个编辑器本身,而是因为它的一个插件——[Vetur](https://github.com/vuejs/vetur),由 Vue.js 团队开发的用来给 `*.vue` 文件提供代码提示与 TypeScript 支持。用过 Vue.js 的同学都知道,Vue.js 配置项里面的方法的 `this` 其实指向这个 Vue 实例本身,但是 WebStorm(我想其他编辑器也一样)只会把方法里的 `this` 识别成这个方法所在的对象,所以编辑器不能正确的提供 `this` 的代码提示。
在尝试了 VS Code 之后,我再一次体会到了当时发现 WebStorm 的时候的心情——爱不释手、给它折腾了一堆插件、想立刻写一些代码来体验一下这个编辑器,最后,我就停不下来了 😂
我想从我的使用角度解释一下为什么我最终从 WebStorm 转向了 VS Code,也许能给看到这篇文章的朋友们一点参考。
VS Code 最让我看中的特点就是轻量——它的轻量体现在它的**启动速度**、**内存占用**和**功能**。
注意:我是在 2015 年款 MacBook Pro (8GB 内存)上对这两款编辑器进行比较的,可能与你的感受不太一样。
### 启动速度
VS Code 启动的时候非常快——这里的非常快是相对于 WebStorm 而言的。我使用了同一个中等大小的项目(下文统一称之为测试项目)做测试,这个项目使用了 TypeScript 和 Vue.js,大概有 30 个文件。
在使用 WebStorm 的时候,一般要经过下面这些步骤:
1. 打开 WebStorm,这一阶段差不多要 7 秒。
2. 选择上面提到的测试项目并打开,需要 3 秒。
3. 打开项目之后,WebStorm 会索引代码,这段时间内它的一些功能(比如代码提示与代码着色)还没有准备好,所以我一般会等索引完成之后再开始写代码。这一阶段根据项目大小需要的时间也不固定,但对于测试项目,这一过程差不多要 10 多秒——如果你没有将 `node_modules` 文件夹 _Mark Directory as Excluded_,那么需要的时间会更长。
所以从我打开 WebStorm 到它真的可以用的这段时间,已经快有半分钟了!可是在使用 VS Code 之前,我从来没觉得这段时间很长。
那么同样的项目,VS Code 打开需要多长时间?答案是 **4 秒**。这是在我安装了 19 个扩展的情况下得出的结论,而这 19 个扩展基本涵盖了 WebStorm 中我用得到的功能。
我仔细观察了一下为什么 VS Code 相对于 WebStorm 会快很多:
1. 在 MacOS 中,直接用两个手指点击 VS Code 的图标就能展开最近打开过的项目,而 WebStorm 要先打开一个选择界面。
2. VS Code 没有那么明显的索引代码的过程。也许它根本就没有索引代码这一过程,又或者,它在后台偷偷索引但没有提示给用户知道。可是当我打开一个文件的时候,代码提示和代码着色都是已经准备好了的。注意:有一些扩展会在**第一次使用时**花费一段时间索引你的项目代码,但这一过程在下次打开项目时会非常快,所以这段时间没有计入 VS Code 的打开时间中。
### 内存占用
我经常会需要同时开启两三个项目,然后再开一些其他软件(听歌的、微信、Chrome 之类的)。如果我使用 WebStorm,时间一长,8GB 内存就会被用的只剩两三百兆,我不得不用 CleanMyMac 清理我的内存,不然电脑会变得反应迟钝。
同样的情况换成是 VS Code 就没有这个问题。我知道这一感受非常主观,所以在我写这片文章的时候,我尝试分别用这两个编辑器同时打开三个相同的项目,但它们的内存占用从数字上看是差不多的——都是 1.6GB 左右。有一点不同的是,VS Code 的进程本身占用内存很少,但它有很多个 Code Helper 进程,我每关掉一个项目,Code Helper 的数量和它们占用的内存都会相应减少。
上面的数据仅仅只是打开了三个项目的情况,如果后面多使用一段时间,WebStrom 的内存占用会越来越多——这也跟你使用了 WebStorm 中的多少功能相关。按照我这半个月来的使用体验,WebStorm 会让我觉得内存不够用,而 VS Code 就没有这个问题。
当然,这些都只是我的**主观感受**,由于没有足够的数据支持,你可以认为它们在内存占用方面打了个平手。
### 功能
一个编辑器的功能是越多越好还是越少越好?功能多当然很不错,但并不是所有人都需要一些功能,而且多余的功能会导致编辑器更加笨重。
WebStorm 和 VS Code 都提供了插件系统,但仅从核心大小来看的话,VS Code 无疑要比 WebStorm 轻量许多——这一点你从它们的设置里就可以看出来了。
WebStorm 的插件系统更像是锦上添花,因为它已经内置了很多很有用并且也很好用的功能了,一般人基本上不会去安装更多插件了,并且,Webstorm 内置的大部分插件我都不需要,我还得自己去关闭一些。
反观 VS Code,我觉得它的插件系统才是它的核心功能——VS Code 本身缺少很多功能,如果你不安装一些插件,基本上很难愉快的写代码。
从个人的角度来看,我非常喜欢 VS Code 的做法——我在写一些 JavaScript 项目的时候也是这么想的——核心应该尽可能的小,然后通过插件的方式来补充功能以适应不同的使用场景。[Koa](https://github.com/koajs/koa)和 Chrome 浏览器就是使用插件扩充功能的例子。
但是,依赖于社区开发的插件就会出现一个问题——插件的质量总是参差不齐的,插件的维护者也不一定会长时间维护下去,所以在给 VS Code 安装插件的时候我花了很长时间尝试了很多个同样功能的不同插件,不过这个痛苦的过程也只是一次性的。
对于未来,我希望 VS Code 团队能像 WebStorm 那样有一些官方维护的高质量插件,避免用户在选择插件的时候眼花缭乱。不过,目前 VS Code 肯定是没有多余的精力做这些的,所以作为用户的我们也只能自己不断的尝试了。
## 总结
本文从三个方面阐述了我个人认为 VS Code 对比 WebStorm 的优势,但实际上 WebStorm 也并不是没有比 VS Code 好的方面:
1. 就像上面提到的,WebStorm 有很多内置的官方维护的插件,能有效避免用户自行挑选第三方插件。
2. 不能否认,WebStorm 确实功能齐全,而有一些功能并不是 VS Code 的插件能取代的。让我个人感觉最强烈的一点就是 WebStorm 内置的 Git 集成要比 VS Code 好太多,即使安装了好几个 VS Code 的 Git 相关插件,也比不过 WebStorm 内置的 Git 功能。
3. ……想了想似乎就没有更多了 :joy:
我的建议是,如果你不喜欢折腾、更喜欢使用纯 GUI 方式写代码,WebStorm 无疑更适合你,使用 VS Code 的时候,你可能得学一些 Git 命令来弥补 VS Code 在 Git 集成功能方面的不足;如果你更看中 VS Code 的轻量,并且也愿意付出时间去适应、安装插件,那 VS Code 会比较合你的胃口。
最后,欢迎你留下自己的看法 ;) | 1.0 | 于是我从 WebStorm 转向了 VS Code - 自从大学以来,我换了不少编辑器。一开始学习 C# 的时候,用的是 [Visual Studio](https://www.visualstudio.com),这款编辑器确实非常好用,即使是用来写 JavaScript 也有很全的代码提示。
后来我决定专攻前端开发,这时候 Visual Studio 就显得太过于笨重了。在学校老师的建议下,我开始用 [Dreamweaver](http://www.adobe.com/cn/products/dreamweaver.html),老师极力推荐它的原因是它的「所见即所得」特性——不需要自己写代码,只需要拖一些控件进去,它就会自动帮你生成页面……可是它生成的代码也太差劲了,我从来没拖过控件,代码提示也不如 Visual Studio 全面,时不时的还会卡顿。
再后来,我在网友的推荐下开始用 [WebStorm](https://www.jetbrains.com/webstorm/),简直爱不释手,于是从此再也没有换过编辑器——
直到半个月前,我试了一下 [VS Code](https://code.visualstudio.com/)。
让我决定去尝试一下 VS Code 原因倒不是因为这个编辑器本身,而是因为它的一个插件——[Vetur](https://github.com/vuejs/vetur),由 Vue.js 团队开发的用来给 `*.vue` 文件提供代码提示与 TypeScript 支持。用过 Vue.js 的同学都知道,Vue.js 配置项里面的方法的 `this` 其实指向这个 Vue 实例本身,但是 WebStorm(我想其他编辑器也一样)只会把方法里的 `this` 识别成这个方法所在的对象,所以编辑器不能正确的提供 `this` 的代码提示。
在尝试了 VS Code 之后,我再一次体会到了当时发现 WebStorm 的时候的心情——爱不释手、给它折腾了一堆插件、想立刻写一些代码来体验一下这个编辑器,最后,我就停不下来了 😂
我想从我的使用角度解释一下为什么我最终从 WebStorm 转向了 VS Code,也许能给看到这篇文章的朋友们一点参考。
VS Code 最让我看中的特点就是轻量——它的轻量体现在它的**启动速度**、**内存占用**和**功能**。
注意:我是在 2015 年款 MacBook Pro (8GB 内存)上对这两款编辑器进行比较的,可能与你的感受不太一样。
### 启动速度
VS Code 启动的时候非常快——这里的非常快是相对于 WebStorm 而言的。我使用了同一个中等大小的项目(下文统一称之为测试项目)做测试,这个项目使用了 TypeScript 和 Vue.js,大概有 30 个文件。
在使用 WebStorm 的时候,一般要经过下面这些步骤:
1. 打开 WebStorm,这一阶段差不多要 7 秒。
2. 选择上面提到的测试项目并打开,需要 3 秒。
3. 打开项目之后,WebStorm 会索引代码,这段时间内它的一些功能(比如代码提示与代码着色)还没有准备好,所以我一般会等索引完成之后再开始写代码。这一阶段根据项目大小需要的时间也不固定,但对于测试项目,这一过程差不多要 10 多秒——如果你没有将 `node_modules` 文件夹 _Mark Directory as Excluded_,那么需要的时间会更长。
所以从我打开 WebStorm 到它真的可以用的这段时间,已经快有半分钟了!可是在使用 VS Code 之前,我从来没觉得这段时间很长。
那么同样的项目,VS Code 打开需要多长时间?答案是 **4 秒**。这是在我安装了 19 个扩展的情况下得出的结论,而这 19 个扩展基本涵盖了 WebStorm 中我用得到的功能。
我仔细观察了一下为什么 VS Code 相对于 WebStorm 会快很多:
1. 在 MacOS 中,直接用两个手指点击 VS Code 的图标就能展开最近打开过的项目,而 WebStorm 要先打开一个选择界面。
2. VS Code 没有那么明显的索引代码的过程。也许它根本就没有索引代码这一过程,又或者,它在后台偷偷索引但没有提示给用户知道。可是当我打开一个文件的时候,代码提示和代码着色都是已经准备好了的。注意:有一些扩展会在**第一次使用时**花费一段时间索引你的项目代码,但这一过程在下次打开项目时会非常快,所以这段时间没有计入 VS Code 的打开时间中。
### 内存占用
我经常会需要同时开启两三个项目,然后再开一些其他软件(听歌的、微信、Chrome 之类的)。如果我使用 WebStorm,时间一长,8GB 内存就会被用的只剩两三百兆,我不得不用 CleanMyMac 清理我的内存,不然电脑会变得反应迟钝。
同样的情况换成是 VS Code 就没有这个问题。我知道这一感受非常主观,所以在我写这片文章的时候,我尝试分别用这两个编辑器同时打开三个相同的项目,但它们的内存占用从数字上看是差不多的——都是 1.6GB 左右。有一点不同的是,VS Code 的进程本身占用内存很少,但它有很多个 Code Helper 进程,我每关掉一个项目,Code Helper 的数量和它们占用的内存都会相应减少。
上面的数据仅仅只是打开了三个项目的情况,如果后面多使用一段时间,WebStrom 的内存占用会越来越多——这也跟你使用了 WebStorm 中的多少功能相关。按照我这半个月来的使用体验,WebStorm 会让我觉得内存不够用,而 VS Code 就没有这个问题。
当然,这些都只是我的**主观感受**,由于没有足够的数据支持,你可以认为它们在内存占用方面打了个平手。
### 功能
一个编辑器的功能是越多越好还是越少越好?功能多当然很不错,但并不是所有人都需要一些功能,而且多余的功能会导致编辑器更加笨重。
WebStorm 和 VS Code 都提供了插件系统,但仅从核心大小来看的话,VS Code 无疑要比 WebStorm 轻量许多——这一点你从它们的设置里就可以看出来了。
WebStorm 的插件系统更像是锦上添花,因为它已经内置了很多很有用并且也很好用的功能了,一般人基本上不会去安装更多插件了,并且,Webstorm 内置的大部分插件我都不需要,我还得自己去关闭一些。
反观 VS Code,我觉得它的插件系统才是它的核心功能——VS Code 本身缺少很多功能,如果你不安装一些插件,基本上很难愉快的写代码。
从个人的角度来看,我非常喜欢 VS Code 的做法——我在写一些 JavaScript 项目的时候也是这么想的——核心应该尽可能的小,然后通过插件的方式来补充功能以适应不同的使用场景。[Koa](https://github.com/koajs/koa)和 Chrome 浏览器就是使用插件扩充功能的例子。
但是,依赖于社区开发的插件就会出现一个问题——插件的质量总是参差不齐的,插件的维护者也不一定会长时间维护下去,所以在给 VS Code 安装插件的时候我花了很长时间尝试了很多个同样功能的不同插件,不过这个痛苦的过程也只是一次性的。
对于未来,我希望 VS Code 团队能像 WebStorm 那样有一些官方维护的高质量插件,避免用户在选择插件的时候眼花缭乱。不过,目前 VS Code 肯定是没有多余的精力做这些的,所以作为用户的我们也只能自己不断的尝试了。
## 总结
本文从三个方面阐述了我个人认为 VS Code 对比 WebStorm 的优势,但实际上 WebStorm 也并不是没有比 VS Code 好的方面:
1. 就像上面提到的,WebStorm 有很多内置的官方维护的插件,能有效避免用户自行挑选第三方插件。
2. 不能否认,WebStorm 确实功能齐全,而有一些功能并不是 VS Code 的插件能取代的。让我个人感觉最强烈的一点就是 WebStorm 内置的 Git 集成要比 VS Code 好太多,即使安装了好几个 VS Code 的 Git 相关插件,也比不过 WebStorm 内置的 Git 功能。
3. ……想了想似乎就没有更多了 :joy:
我的建议是,如果你不喜欢折腾、更喜欢使用纯 GUI 方式写代码,WebStorm 无疑更适合你,使用 VS Code 的时候,你可能得学一些 Git 命令来弥补 VS Code 在 Git 集成功能方面的不足;如果你更看中 VS Code 的轻量,并且也愿意付出时间去适应、安装插件,那 VS Code 会比较合你的胃口。
最后,欢迎你留下自己的看法 ;) | non_priority | 于是我从 webstorm 转向了 vs code 自从大学以来,我换了不少编辑器。一开始学习 c 的时候,用的是 javascript 也有很全的代码提示。 后来我决定专攻前端开发,这时候 visual studio 就显得太过于笨重了。在学校老师的建议下,我开始用 visual studio 全面,时不时的还会卡顿。 再后来,我在网友的推荐下开始用 直到半个月前,我试了一下 让我决定去尝试一下 vs code 原因倒不是因为这个编辑器本身,而是因为它的一个插件—— vue js 团队开发的用来给 vue 文件提供代码提示与 typescript 支持。用过 vue js 的同学都知道,vue js 配置项里面的方法的 this 其实指向这个 vue 实例本身,但是 webstorm(我想其他编辑器也一样)只会把方法里的 this 识别成这个方法所在的对象,所以编辑器不能正确的提供 this 的代码提示。 在尝试了 vs code 之后,我再一次体会到了当时发现 webstorm 的时候的心情——爱不释手、给它折腾了一堆插件、想立刻写一些代码来体验一下这个编辑器,最后,我就停不下来了 😂 我想从我的使用角度解释一下为什么我最终从 webstorm 转向了 vs code,也许能给看到这篇文章的朋友们一点参考。 vs code 最让我看中的特点就是轻量——它的轻量体现在它的 启动速度 、 内存占用 和 功能 。 注意:我是在 年款 macbook pro 内存 上对这两款编辑器进行比较的,可能与你的感受不太一样。 启动速度 vs code 启动的时候非常快——这里的非常快是相对于 webstorm 而言的。我使用了同一个中等大小的项目(下文统一称之为测试项目)做测试,这个项目使用了 typescript 和 vue js,大概有 个文件。 在使用 webstorm 的时候,一般要经过下面这些步骤: 打开 webstorm,这一阶段差不多要 秒。 选择上面提到的测试项目并打开,需要 秒。 打开项目之后,webstorm 会索引代码,这段时间内它的一些功能(比如代码提示与代码着色)还没有准备好,所以我一般会等索引完成之后再开始写代码。这一阶段根据项目大小需要的时间也不固定,但对于测试项目,这一过程差不多要 多秒——如果你没有将 node modules 文件夹 mark directory as excluded ,那么需要的时间会更长。 所以从我打开 webstorm 到它真的可以用的这段时间,已经快有半分钟了!可是在使用 vs code 之前,我从来没觉得这段时间很长。 那么同样的项目,vs code 打开需要多长时间?答案是 秒 。这是在我安装了 个扩展的情况下得出的结论,而这 个扩展基本涵盖了 webstorm 中我用得到的功能。 我仔细观察了一下为什么 vs code 相对于 webstorm 会快很多: 在 macos 中,直接用两个手指点击 vs code 的图标就能展开最近打开过的项目,而 webstorm 要先打开一个选择界面。 vs code 没有那么明显的索引代码的过程。也许它根本就没有索引代码这一过程,又或者,它在后台偷偷索引但没有提示给用户知道。可是当我打开一个文件的时候,代码提示和代码着色都是已经准备好了的。注意:有一些扩展会在 第一次使用时 花费一段时间索引你的项目代码,但这一过程在下次打开项目时会非常快,所以这段时间没有计入 vs code 的打开时间中。 内存占用 我经常会需要同时开启两三个项目,然后再开一些其他软件(听歌的、微信、chrome 之类的)。如果我使用 webstorm,时间一长, 内存就会被用的只剩两三百兆,我不得不用 cleanmymac 清理我的内存,不然电脑会变得反应迟钝。 同样的情况换成是 vs code 就没有这个问题。我知道这一感受非常主观,所以在我写这片文章的时候,我尝试分别用这两个编辑器同时打开三个相同的项目,但它们的内存占用从数字上看是差不多的——都是 左右。有一点不同的是,vs code 的进程本身占用内存很少,但它有很多个 code helper 进程,我每关掉一个项目,code helper 的数量和它们占用的内存都会相应减少。 上面的数据仅仅只是打开了三个项目的情况,如果后面多使用一段时间,webstrom 的内存占用会越来越多——这也跟你使用了 webstorm 中的多少功能相关。按照我这半个月来的使用体验,webstorm 会让我觉得内存不够用,而 vs code 就没有这个问题。 当然,这些都只是我的 主观感受 ,由于没有足够的数据支持,你可以认为它们在内存占用方面打了个平手。 功能 一个编辑器的功能是越多越好还是越少越好?功能多当然很不错,但并不是所有人都需要一些功能,而且多余的功能会导致编辑器更加笨重。 webstorm 和 vs code 都提供了插件系统,但仅从核心大小来看的话,vs code 无疑要比 webstorm 轻量许多——这一点你从它们的设置里就可以看出来了。 webstorm 的插件系统更像是锦上添花,因为它已经内置了很多很有用并且也很好用的功能了,一般人基本上不会去安装更多插件了,并且,webstorm 内置的大部分插件我都不需要,我还得自己去关闭一些。 反观 vs code,我觉得它的插件系统才是它的核心功能——vs code 本身缺少很多功能,如果你不安装一些插件,基本上很难愉快的写代码。 从个人的角度来看,我非常喜欢 vs code 的做法——我在写一些 javascript 项目的时候也是这么想的——核心应该尽可能的小,然后通过插件的方式来补充功能以适应不同的使用场景。 chrome 浏览器就是使用插件扩充功能的例子。 但是,依赖于社区开发的插件就会出现一个问题——插件的质量总是参差不齐的,插件的维护者也不一定会长时间维护下去,所以在给 vs code 安装插件的时候我花了很长时间尝试了很多个同样功能的不同插件,不过这个痛苦的过程也只是一次性的。 对于未来,我希望 vs code 团队能像 webstorm 那样有一些官方维护的高质量插件,避免用户在选择插件的时候眼花缭乱。不过,目前 vs code 肯定是没有多余的精力做这些的,所以作为用户的我们也只能自己不断的尝试了。 总结 本文从三个方面阐述了我个人认为 vs code 对比 webstorm 的优势,但实际上 webstorm 也并不是没有比 vs code 好的方面: 就像上面提到的,webstorm 有很多内置的官方维护的插件,能有效避免用户自行挑选第三方插件。 不能否认,webstorm 确实功能齐全,而有一些功能并不是 vs code 的插件能取代的。让我个人感觉最强烈的一点就是 webstorm 内置的 git 集成要比 vs code 好太多,即使安装了好几个 vs code 的 git 相关插件,也比不过 webstorm 内置的 git 功能。 ……想了想似乎就没有更多了 joy 我的建议是,如果你不喜欢折腾、更喜欢使用纯 gui 方式写代码,webstorm 无疑更适合你,使用 vs code 的时候,你可能得学一些 git 命令来弥补 vs code 在 git 集成功能方面的不足;如果你更看中 vs code 的轻量,并且也愿意付出时间去适应、安装插件,那 vs code 会比较合你的胃口。 最后,欢迎你留下自己的看法 | 0 |
41,497 | 10,491,599,922 | IssuesEvent | 2019-09-25 11:31:21 | sfepy/sfepy | https://api.github.com/repos/sfepy/sfepy | opened | ls.auto_direct fails without mpi4py | defect | The `'ls.auto_direct'` solver fails when mpi4py is not installed, because `MUMPSSolver.__init__() `executes without error - then it fails in `.presolve()` on `MumpsSolver` creation. It should either work without mpi4py or fail already in `.__init__() `.
Can be reproduced by setting `use_mpi = False` in `sfepy/solvers/ls_mumps.py` and running `./run_tests.py tests/test_input_linear_elastic.py --raise`.
@vlukes could you have a look at it? Thanks! | 1.0 | ls.auto_direct fails without mpi4py - The `'ls.auto_direct'` solver fails when mpi4py is not installed, because `MUMPSSolver.__init__() `executes without error - then it fails in `.presolve()` on `MumpsSolver` creation. It should either work without mpi4py or fail already in `.__init__() `.
Can be reproduced by setting `use_mpi = False` in `sfepy/solvers/ls_mumps.py` and running `./run_tests.py tests/test_input_linear_elastic.py --raise`.
@vlukes could you have a look at it? Thanks! | non_priority | ls auto direct fails without the ls auto direct solver fails when is not installed because mumpssolver init executes without error then it fails in presolve on mumpssolver creation it should either work without or fail already in init can be reproduced by setting use mpi false in sfepy solvers ls mumps py and running run tests py tests test input linear elastic py raise vlukes could you have a look at it thanks | 0 |
31,799 | 8,752,170,221 | IssuesEvent | 2018-12-14 01:36:41 | quicklisp/quicklisp-projects | https://api.github.com/repos/quicklisp/quicklisp-projects | closed | Please add cl-punch | canbuild | https://github.com/windymelt/cl-punch
cl-punch is reader macro library for writing `lambda` expression in easy way. | 1.0 | Please add cl-punch - https://github.com/windymelt/cl-punch
cl-punch is reader macro library for writing `lambda` expression in easy way. | non_priority | please add cl punch cl punch is reader macro library for writing lambda expression in easy way | 0 |
56,697 | 23,876,318,886 | IssuesEvent | 2022-09-07 19:26:20 | MicrosoftDocs/azure-docs | https://api.github.com/repos/MicrosoftDocs/azure-docs | closed | Error: failed pre-install: timed out waiting for the condition | container-service/svc triaged cxp in-progress product-issue Pri1 | Getting an issue on helm install in the documentation. The code that i'm using is:
```
$ResourceGroup = (Get-AzContainerRegistry | Where-Object {$_.name -eq $RegistryName} ).ResourceGroupName
$ControllerRegistry = "k8s.gcr.io"
$ControllerImage = "ingress-nginx/controller"
$ControllerTag = "v1.0.4"
$PatchRegistry = "docker.io"
$PatchImage = "jettech/kube-webhook-certgen"
$PatchTag = "v1.5.1"
$DefaultBackendRegistry = "k8s.gcr.io"
$DefaultBackendImage = "defaultbackend-amd64"
$DefaultBackendTag = "1.5"
$CertManagerRegistry = "quay.io"
$CertManagerTag = "v1.3.1"
$CertManagerImageController = "jetstack/cert-manager-controller"
$CertManagerImageWebhook = "jetstack/cert-manager-webhook"
$CertManagerImageCaInjector = "jetstack/cert-manager-cainjector"
Import-AzContainerRegistryImage -ResourceGroupName $ResourceGroup -RegistryName $RegistryName -SourceRegistryUri $ControllerRegistry -SourceImage "${ControllerImage}:${ControllerTag}"
Import-AzContainerRegistryImage -ResourceGroupName $ResourceGroup -RegistryName $RegistryName -SourceRegistryUri $PatchRegistry -SourceImage "${PatchImage}:${PatchTag}"
Import-AzContainerRegistryImage -ResourceGroupName $ResourceGroup -RegistryName $RegistryName -SourceRegistryUri $DefaultBackendRegistry -SourceImage "${DefaultBackendImage}:${DefaultBackendTag}"
Import-AzContainerRegistryImage -ResourceGroupName $ResourceGroup -RegistryName $RegistryName -SourceRegistryUri $CertManagerRegistry -SourceImage "${CertManagerImageController}:${CertManagerTag}"
Import-AzContainerRegistryImage -ResourceGroupName $ResourceGroup -RegistryName $RegistryName -SourceRegistryUri $CertManagerRegistry -SourceImage "${CertManagerImageWebhook}:${CertManagerTag}"
Import-AzContainerRegistryImage -ResourceGroupName $ResourceGroup -RegistryName $RegistryName -SourceRegistryUri $CertManagerRegistry -SourceImage "${CertManagerImageCaInjector}:${CertManagerTag}"
```
and then
```
# Create a namespace for your ingress resources
kubectl create namespace ingress-basic
# Add the ingress-nginx repository
helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
# Set variable for ACR location to use for pulling images
$AcrUrl = "$RegistryName.azurecr.io"
# Get the SHA256 digest of the controller and patch images
$ControllerDigest = (Get-AzContainerRegistryTag -RegistryName $RegistryName -RepositoryName $ControllerImage -Name $ControllerTag).Attributes.digest
$PatchDigest = (Get-AzContainerRegistryTag -RegistryName $RegistryName -RepositoryName $PatchImage -Name $PatchTag).Attributes.digest
# Use Helm to deploy an NGINX ingress controller
helm install nginx-ingress ingress-nginx/ingress-nginx `
--namespace ingress-basic --create-namespace `
--set controller.replicaCount=2 `
--set controller.ingressClassResource.name="nginx-ingress" `
--set controller.nodeSelector."kubernetes\.io/os"=linux `
--set controller.image.registry=$AcrUrl `
--set controller.image.image=$ControllerImage `
--set controller.image.tag=$ControllerTag `
--set controller.image.digest="" `
--set controller.admissionWebhooks.patch.nodeSelector."kubernetes\.io/os"=linux `
--set controller.admissionWebhooks.patch.image.registry=$AcrUrl `
--set controller.admissionWebhooks.patch.image.image=$PatchImage `
--set controller.admissionWebhooks.patch.image.tag=$PatchTag `
--set controller.admissionWebhooks.patch.image.digest="" `
--set defaultBackend.nodeSelector."kubernetes\.io/os"=linux `
--set defaultBackend.image.registry=$AcrUrl `
--set defaultBackend.image.image=$DefaultBackendImage `
--set defaultBackend.image.tag=$DefaultBackendTag `
--set defaultBackend.image.digest=""
```
The second part is a little difficult though, because in your CLI instructions you have the digests equalling "", but in the powershell, you specify them above. Regardless, including them or excluding them has no effect.
I tried changing the helm version like https://github.com/MicrosoftDocs/azure-docs/issues/81694, no change (I also added the ingressClassResource.name above, and still had the timeout issue)
This issue https://github.com/MicrosoftDocs/azure-docs/issues/80321 doesn't help, because it mostly says to upgrade the controller tag to 1.0.0, but your documentation already says to use 1.0.4
This issue https://github.com/MicrosoftDocs/azure-docs/issues/81350 also doesn't help, because i've tried adding the digest and leaving it blank. No luck either spot.
Is there a better/more recent issue that fixes this problem? Thank you!
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: ada58160-dc50-b977-d3bc-65f92406e16d
* Version Independent ID: 5c596e04-fddb-effe-3b72-575f4df42d4e
* Content: [Create ingress with automatic TLS - Azure Kubernetes Service](https://docs.microsoft.com/en-us/azure/aks/ingress-tls?tabs=azure-cli)
* Content Source: [articles/aks/ingress-tls.md](https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/aks/ingress-tls.md)
* Service: **container-service**
* GitHub Login: @zr-msft
* Microsoft Alias: **zarhoads** | 1.0 | Error: failed pre-install: timed out waiting for the condition - Getting an issue on helm install in the documentation. The code that i'm using is:
```
$ResourceGroup = (Get-AzContainerRegistry | Where-Object {$_.name -eq $RegistryName} ).ResourceGroupName
$ControllerRegistry = "k8s.gcr.io"
$ControllerImage = "ingress-nginx/controller"
$ControllerTag = "v1.0.4"
$PatchRegistry = "docker.io"
$PatchImage = "jettech/kube-webhook-certgen"
$PatchTag = "v1.5.1"
$DefaultBackendRegistry = "k8s.gcr.io"
$DefaultBackendImage = "defaultbackend-amd64"
$DefaultBackendTag = "1.5"
$CertManagerRegistry = "quay.io"
$CertManagerTag = "v1.3.1"
$CertManagerImageController = "jetstack/cert-manager-controller"
$CertManagerImageWebhook = "jetstack/cert-manager-webhook"
$CertManagerImageCaInjector = "jetstack/cert-manager-cainjector"
Import-AzContainerRegistryImage -ResourceGroupName $ResourceGroup -RegistryName $RegistryName -SourceRegistryUri $ControllerRegistry -SourceImage "${ControllerImage}:${ControllerTag}"
Import-AzContainerRegistryImage -ResourceGroupName $ResourceGroup -RegistryName $RegistryName -SourceRegistryUri $PatchRegistry -SourceImage "${PatchImage}:${PatchTag}"
Import-AzContainerRegistryImage -ResourceGroupName $ResourceGroup -RegistryName $RegistryName -SourceRegistryUri $DefaultBackendRegistry -SourceImage "${DefaultBackendImage}:${DefaultBackendTag}"
Import-AzContainerRegistryImage -ResourceGroupName $ResourceGroup -RegistryName $RegistryName -SourceRegistryUri $CertManagerRegistry -SourceImage "${CertManagerImageController}:${CertManagerTag}"
Import-AzContainerRegistryImage -ResourceGroupName $ResourceGroup -RegistryName $RegistryName -SourceRegistryUri $CertManagerRegistry -SourceImage "${CertManagerImageWebhook}:${CertManagerTag}"
Import-AzContainerRegistryImage -ResourceGroupName $ResourceGroup -RegistryName $RegistryName -SourceRegistryUri $CertManagerRegistry -SourceImage "${CertManagerImageCaInjector}:${CertManagerTag}"
```
and then
```
# Create a namespace for your ingress resources
kubectl create namespace ingress-basic
# Add the ingress-nginx repository
helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
# Set variable for ACR location to use for pulling images
$AcrUrl = "$RegistryName.azurecr.io"
# Get the SHA256 digest of the controller and patch images
$ControllerDigest = (Get-AzContainerRegistryTag -RegistryName $RegistryName -RepositoryName $ControllerImage -Name $ControllerTag).Attributes.digest
$PatchDigest = (Get-AzContainerRegistryTag -RegistryName $RegistryName -RepositoryName $PatchImage -Name $PatchTag).Attributes.digest
# Use Helm to deploy an NGINX ingress controller
helm install nginx-ingress ingress-nginx/ingress-nginx `
--namespace ingress-basic --create-namespace `
--set controller.replicaCount=2 `
--set controller.ingressClassResource.name="nginx-ingress" `
--set controller.nodeSelector."kubernetes\.io/os"=linux `
--set controller.image.registry=$AcrUrl `
--set controller.image.image=$ControllerImage `
--set controller.image.tag=$ControllerTag `
--set controller.image.digest="" `
--set controller.admissionWebhooks.patch.nodeSelector."kubernetes\.io/os"=linux `
--set controller.admissionWebhooks.patch.image.registry=$AcrUrl `
--set controller.admissionWebhooks.patch.image.image=$PatchImage `
--set controller.admissionWebhooks.patch.image.tag=$PatchTag `
--set controller.admissionWebhooks.patch.image.digest="" `
--set defaultBackend.nodeSelector."kubernetes\.io/os"=linux `
--set defaultBackend.image.registry=$AcrUrl `
--set defaultBackend.image.image=$DefaultBackendImage `
--set defaultBackend.image.tag=$DefaultBackendTag `
--set defaultBackend.image.digest=""
```
The second part is a little difficult though, because in your CLI instructions you have the digests equalling "", but in the powershell, you specify them above. Regardless, including them or excluding them has no effect.
I tried changing the helm version like https://github.com/MicrosoftDocs/azure-docs/issues/81694, no change (I also added the ingressClassResource.name above, and still had the timeout issue)
This issue https://github.com/MicrosoftDocs/azure-docs/issues/80321 doesn't help, because it mostly says to upgrade the controller tag to 1.0.0, but your documentation already says to use 1.0.4
This issue https://github.com/MicrosoftDocs/azure-docs/issues/81350 also doesn't help, because i've tried adding the digest and leaving it blank. No luck either spot.
Is there a better/more recent issue that fixes this problem? Thank you!
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: ada58160-dc50-b977-d3bc-65f92406e16d
* Version Independent ID: 5c596e04-fddb-effe-3b72-575f4df42d4e
* Content: [Create ingress with automatic TLS - Azure Kubernetes Service](https://docs.microsoft.com/en-us/azure/aks/ingress-tls?tabs=azure-cli)
* Content Source: [articles/aks/ingress-tls.md](https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/aks/ingress-tls.md)
* Service: **container-service**
* GitHub Login: @zr-msft
* Microsoft Alias: **zarhoads** | non_priority | error failed pre install timed out waiting for the condition getting an issue on helm install in the documentation the code that i m using is resourcegroup get azcontainerregistry where object name eq registryname resourcegroupname controllerregistry gcr io controllerimage ingress nginx controller controllertag patchregistry docker io patchimage jettech kube webhook certgen patchtag defaultbackendregistry gcr io defaultbackendimage defaultbackend defaultbackendtag certmanagerregistry quay io certmanagertag certmanagerimagecontroller jetstack cert manager controller certmanagerimagewebhook jetstack cert manager webhook certmanagerimagecainjector jetstack cert manager cainjector import azcontainerregistryimage resourcegroupname resourcegroup registryname registryname sourceregistryuri controllerregistry sourceimage controllerimage controllertag import azcontainerregistryimage resourcegroupname resourcegroup registryname registryname sourceregistryuri patchregistry sourceimage patchimage patchtag import azcontainerregistryimage resourcegroupname resourcegroup registryname registryname sourceregistryuri defaultbackendregistry sourceimage defaultbackendimage defaultbackendtag import azcontainerregistryimage resourcegroupname resourcegroup registryname registryname sourceregistryuri certmanagerregistry sourceimage certmanagerimagecontroller certmanagertag import azcontainerregistryimage resourcegroupname resourcegroup registryname registryname sourceregistryuri certmanagerregistry sourceimage certmanagerimagewebhook certmanagertag import azcontainerregistryimage resourcegroupname resourcegroup registryname registryname sourceregistryuri certmanagerregistry sourceimage certmanagerimagecainjector certmanagertag and then create a namespace for your ingress resources kubectl create namespace ingress basic add the ingress nginx repository helm repo add ingress nginx set variable for acr location to use for pulling images acrurl registryname azurecr io get the digest of the controller and patch images controllerdigest get azcontainerregistrytag registryname registryname repositoryname controllerimage name controllertag attributes digest patchdigest get azcontainerregistrytag registryname registryname repositoryname patchimage name patchtag attributes digest use helm to deploy an nginx ingress controller helm install nginx ingress ingress nginx ingress nginx namespace ingress basic create namespace set controller replicacount set controller ingressclassresource name nginx ingress set controller nodeselector kubernetes io os linux set controller image registry acrurl set controller image image controllerimage set controller image tag controllertag set controller image digest set controller admissionwebhooks patch nodeselector kubernetes io os linux set controller admissionwebhooks patch image registry acrurl set controller admissionwebhooks patch image image patchimage set controller admissionwebhooks patch image tag patchtag set controller admissionwebhooks patch image digest set defaultbackend nodeselector kubernetes io os linux set defaultbackend image registry acrurl set defaultbackend image image defaultbackendimage set defaultbackend image tag defaultbackendtag set defaultbackend image digest the second part is a little difficult though because in your cli instructions you have the digests equalling but in the powershell you specify them above regardless including them or excluding them has no effect i tried changing the helm version like no change i also added the ingressclassresource name above and still had the timeout issue this issue doesn t help because it mostly says to upgrade the controller tag to but your documentation already says to use this issue also doesn t help because i ve tried adding the digest and leaving it blank no luck either spot is there a better more recent issue that fixes this problem thank you document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id fddb effe content content source service container service github login zr msft microsoft alias zarhoads | 0 |
162,544 | 12,680,025,487 | IssuesEvent | 2020-06-19 12:58:24 | ansible/ansible | https://api.github.com/repos/ansible/ansible | closed | Segmentation fault in mysql_user when .my.cnf is present | affects_2.3 bug collection collection:community.general database module mysql needs_info support:community support:core test | ##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
mysql_user
(probably all of the mysql_* are affected)
##### ANSIBLE VERSION
```
ansible 2.3.1.0
config file =
configured module search path = Default w/o overrides
python version = 2.7.13 (default, Feb 1 2017, 15:55:19) [GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.38)]
```
##### CONFIGURATION
All default values
##### OS / ENVIRONMENT
macOS 10.12.4
Debian 9
##### SUMMARY
mysql_user is causing a segmentation fault under the following conditions (all must be fulfilled):
- Ansible version above 1.9.6 (tested with version 2, 2.2 and 2.3)
- A .my.cnf file is present
- MariaDB from the mariadb.org repo
##### STEPS TO REPRODUCE
Install an Ansible version above 1.9.6 and provision the vagrant setup linked below
Vagrant setup:
https://gist.github.com/codeaken/ac1239904ea7f251c56b53844a0f590c
##### EXPECTED RESULTS
The following run is made with Ansible 1.9
```
ansible 1.9.6
configured module search path = None
```
and produces the expected result:
```
PLAY [all] ********************************************************************
GATHERING FACTS ***************************************************************
ok: [default]
TASK: [apt_key url=http://keyserver.ubuntu.com/pks/lookup?op=get&search=0xF1656F24C74CD1D8] ***
changed: [default]
TASK: [Add MariaDB repo] ******************************************************
changed: [default]
TASK: [Install MariaDB] *******************************************************
changed: [default]
TASK: [Enable MariaDB service] ************************************************
ok: [default]
TASK: [Install MySQL Python package] ******************************************
changed: [default]
TASK: [Set root password (localhost)] *****************************************
changed: [default]
TASK: [Saving my.cnf] *********************************************************
changed: [default]
TASK: [Set root password (%)] *************************************************
changed: [default]
PLAY RECAP ********************************************************************
default : ok=9 changed=7 unreachable=0 failed=0
```
##### ACTUAL RESULTS
This is what happens with versions of Ansible above 1.9.6
```
PLAY [all] *********************************************************************
TASK [Gathering Facts] *********************************************************
ok: [default]
TASK [apt_key] *****************************************************************
changed: [default]
TASK [Add MariaDB repo] ********************************************************
changed: [default]
TASK [Install MariaDB] *********************************************************
changed: [default]
TASK [Enable MariaDB service] **************************************************
ok: [default]
TASK [Install MySQL Python package] ********************************************
changed: [default]
TASK [Set root password (localhost)] *******************************************
changed: [default]
TASK [Saving my.cnf] ***********************************************************
changed: [default]
TASK [Set root password (%)] ***************************************************
fatal: [default]: FAILED! => {"changed": false, "failed": true, "module_stderr": "Shared connection to 127.0.0.1 closed.\r\n", "module_stdout": "", "msg": "MODULE FAILURE", "rc": 0}
```
We also get this output in /var/log/messages:
```
stretch kernel: [ 51.656582] python[4237]: segfault at 0 ip 00007fb45472250e sp 00007ffe185cc8a8 error 4 in libc-2.24.so[7fb454693000+195000]
```
Notice that the segmentation fault only occurs after we have created the .my.cnf file. | 1.0 | Segmentation fault in mysql_user when .my.cnf is present - ##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
mysql_user
(probably all of the mysql_* are affected)
##### ANSIBLE VERSION
```
ansible 2.3.1.0
config file =
configured module search path = Default w/o overrides
python version = 2.7.13 (default, Feb 1 2017, 15:55:19) [GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.38)]
```
##### CONFIGURATION
All default values
##### OS / ENVIRONMENT
macOS 10.12.4
Debian 9
##### SUMMARY
mysql_user is causing a segmentation fault under the following conditions (all must be fulfilled):
- Ansible version above 1.9.6 (tested with version 2, 2.2 and 2.3)
- A .my.cnf file is present
- MariaDB from the mariadb.org repo
##### STEPS TO REPRODUCE
Install an Ansible version above 1.9.6 and provision the vagrant setup linked below
Vagrant setup:
https://gist.github.com/codeaken/ac1239904ea7f251c56b53844a0f590c
##### EXPECTED RESULTS
The following run is made with Ansible 1.9
```
ansible 1.9.6
configured module search path = None
```
and produces the expected result:
```
PLAY [all] ********************************************************************
GATHERING FACTS ***************************************************************
ok: [default]
TASK: [apt_key url=http://keyserver.ubuntu.com/pks/lookup?op=get&search=0xF1656F24C74CD1D8] ***
changed: [default]
TASK: [Add MariaDB repo] ******************************************************
changed: [default]
TASK: [Install MariaDB] *******************************************************
changed: [default]
TASK: [Enable MariaDB service] ************************************************
ok: [default]
TASK: [Install MySQL Python package] ******************************************
changed: [default]
TASK: [Set root password (localhost)] *****************************************
changed: [default]
TASK: [Saving my.cnf] *********************************************************
changed: [default]
TASK: [Set root password (%)] *************************************************
changed: [default]
PLAY RECAP ********************************************************************
default : ok=9 changed=7 unreachable=0 failed=0
```
##### ACTUAL RESULTS
This is what happens with versions of Ansible above 1.9.6
```
PLAY [all] *********************************************************************
TASK [Gathering Facts] *********************************************************
ok: [default]
TASK [apt_key] *****************************************************************
changed: [default]
TASK [Add MariaDB repo] ********************************************************
changed: [default]
TASK [Install MariaDB] *********************************************************
changed: [default]
TASK [Enable MariaDB service] **************************************************
ok: [default]
TASK [Install MySQL Python package] ********************************************
changed: [default]
TASK [Set root password (localhost)] *******************************************
changed: [default]
TASK [Saving my.cnf] ***********************************************************
changed: [default]
TASK [Set root password (%)] ***************************************************
fatal: [default]: FAILED! => {"changed": false, "failed": true, "module_stderr": "Shared connection to 127.0.0.1 closed.\r\n", "module_stdout": "", "msg": "MODULE FAILURE", "rc": 0}
```
We also get this output in /var/log/messages:
```
stretch kernel: [ 51.656582] python[4237]: segfault at 0 ip 00007fb45472250e sp 00007ffe185cc8a8 error 4 in libc-2.24.so[7fb454693000+195000]
```
Notice that the segmentation fault only occurs after we have created the .my.cnf file. | non_priority | segmentation fault in mysql user when my cnf is present issue type bug report component name mysql user probably all of the mysql are affected ansible version ansible config file configured module search path default w o overrides python version default feb configuration all default values os environment macos debian summary mysql user is causing a segmentation fault under the following conditions all must be fulfilled ansible version above tested with version and a my cnf file is present mariadb from the mariadb org repo steps to reproduce install an ansible version above and provision the vagrant setup linked below vagrant setup expected results the following run is made with ansible ansible configured module search path none and produces the expected result play gathering facts ok task changed task changed task changed task ok task changed task changed task changed task changed play recap default ok changed unreachable failed actual results this is what happens with versions of ansible above play task ok task changed task changed task changed task ok task changed task changed task changed task fatal failed changed false failed true module stderr shared connection to closed r n module stdout msg module failure rc we also get this output in var log messages stretch kernel python segfault at ip sp error in libc so notice that the segmentation fault only occurs after we have created the my cnf file | 0 |
65,505 | 27,121,767,981 | IssuesEvent | 2023-02-15 23:45:32 | cityofaustin/atd-data-tech | https://api.github.com/repos/cityofaustin/atd-data-tech | closed | Please update the Performance Measures module in the Data Tracker application | Workgroup: Finance Type: Other Service: Apps Product: AMD Data Tracker | <!-- Email -->
<!-- melissa.burbey@austintexas.gov -->
> What application are you using?
Data Tracker
> Describe the problem.
Please update the Performance Measures module in the Data Tracker application to show information for FY23. Everything will be the same as FY22 except for these few: Please remove performance measures with ID 8060, 8584, & 9453. Please add performance measures with ID 9526 & 9527. I've included screenshots of the measures to add with their information.
> How soon do you need this?
Soon — Within a week
> Is there anything else we should know?
I need this information to be updated within a week to make sure there is adequate time to enter information as Q1 of FY23 just closed.
> Requested By
Melissa B.
[Attachment](https://api.knack.com/v1/applications/595d00ebd315cc4cb98daff4/download/asset/63bf0ae14cd4e400119791a1/pmstoaddtofy23.jpg) (44.75kb)
Request ID: DTS23-106130
| 1.0 | Please update the Performance Measures module in the Data Tracker application - <!-- Email -->
<!-- melissa.burbey@austintexas.gov -->
> What application are you using?
Data Tracker
> Describe the problem.
Please update the Performance Measures module in the Data Tracker application to show information for FY23. Everything will be the same as FY22 except for these few: Please remove performance measures with ID 8060, 8584, & 9453. Please add performance measures with ID 9526 & 9527. I've included screenshots of the measures to add with their information.
> How soon do you need this?
Soon — Within a week
> Is there anything else we should know?
I need this information to be updated within a week to make sure there is adequate time to enter information as Q1 of FY23 just closed.
> Requested By
Melissa B.
[Attachment](https://api.knack.com/v1/applications/595d00ebd315cc4cb98daff4/download/asset/63bf0ae14cd4e400119791a1/pmstoaddtofy23.jpg) (44.75kb)
Request ID: DTS23-106130
| non_priority | please update the performance measures module in the data tracker application what application are you using data tracker describe the problem please update the performance measures module in the data tracker application to show information for everything will be the same as except for these few please remove performance measures with id please add performance measures with id i ve included screenshots of the measures to add with their information how soon do you need this soon — within a week is there anything else we should know i need this information to be updated within a week to make sure there is adequate time to enter information as of just closed requested by melissa b request id | 0 |
245,555 | 26,549,276,271 | IssuesEvent | 2023-01-20 05:27:44 | nidhi7598/linux-3.0.35_CVE-2022-45934 | https://api.github.com/repos/nidhi7598/linux-3.0.35_CVE-2022-45934 | opened | CVE-2022-3623 (High) detected in linux-stable-rtv3.8.6, linuxlinux-3.0.49 | security vulnerability | ## CVE-2022-3623 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>linux-stable-rtv3.8.6</b>, <b>linuxlinux-3.0.49</b></p></summary>
<p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A vulnerability was found in Linux Kernel. It has been declared as problematic. Affected by this vulnerability is the function follow_page_pte of the file mm/gup.c of the component BPF. The manipulation leads to race condition. The attack can be launched remotely. It is recommended to apply a patch to fix this issue. The identifier VDB-211921 was assigned to this vulnerability.
<p>Publish Date: 2022-10-20
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-3623>CVE-2022-3623</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- 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://www.linuxkernelcves.com/cves/CVE-2022-3623">https://www.linuxkernelcves.com/cves/CVE-2022-3623</a></p>
<p>Release Date: 2022-10-20</p>
<p>Fix Resolution: v6.0.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-3623 (High) detected in linux-stable-rtv3.8.6, linuxlinux-3.0.49 - ## CVE-2022-3623 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>linux-stable-rtv3.8.6</b>, <b>linuxlinux-3.0.49</b></p></summary>
<p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A vulnerability was found in Linux Kernel. It has been declared as problematic. Affected by this vulnerability is the function follow_page_pte of the file mm/gup.c of the component BPF. The manipulation leads to race condition. The attack can be launched remotely. It is recommended to apply a patch to fix this issue. The identifier VDB-211921 was assigned to this vulnerability.
<p>Publish Date: 2022-10-20
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-3623>CVE-2022-3623</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- 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://www.linuxkernelcves.com/cves/CVE-2022-3623">https://www.linuxkernelcves.com/cves/CVE-2022-3623</a></p>
<p>Release Date: 2022-10-20</p>
<p>Fix Resolution: v6.0.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in linux stable linuxlinux cve high severity vulnerability vulnerable libraries linux stable linuxlinux vulnerability details a vulnerability was found in linux kernel it has been declared as problematic affected by this vulnerability is the function follow page pte of the file mm gup c of the component bpf the manipulation leads to race condition the attack can be launched remotely it is recommended to apply a patch to fix this issue the identifier vdb was assigned to this vulnerability publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact 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 |
244,219 | 18,751,067,525 | IssuesEvent | 2021-11-05 02:03:36 | AY2122S1-CS2103T-W11-4/tp | https://api.github.com/repos/AY2122S1-CS2103T-W11-4/tp | closed | [PE-D] UG \| syntax | documentation | \| syntax is not explained in the UG. Seems like it means 'or'. Maybe could add a how to use user guide at the start
<!--session: 1635494603983-8cadbd08-1068-4adb-96d6-0a93e289aa8b-->
<!--Version: Web v3.4.1-->
-------------
Labels: `severity.Low` `type.DocumentationBug`
original: hernpiblo/ped#1 | 1.0 | [PE-D] UG \| syntax - \| syntax is not explained in the UG. Seems like it means 'or'. Maybe could add a how to use user guide at the start
<!--session: 1635494603983-8cadbd08-1068-4adb-96d6-0a93e289aa8b-->
<!--Version: Web v3.4.1-->
-------------
Labels: `severity.Low` `type.DocumentationBug`
original: hernpiblo/ped#1 | non_priority | ug syntax syntax is not explained in the ug seems like it means or maybe could add a how to use user guide at the start labels severity low type documentationbug original hernpiblo ped | 0 |
47,229 | 13,056,065,873 | IssuesEvent | 2020-07-30 03:33:10 | icecube-trac/tix2 | https://api.github.com/repos/icecube-trac/tix2 | closed | Lacking a working test script for cramer-rao (Trac #168) | Migrated from Trac combo reconstruction defect | The test script in cramer-rao does not work, yet, because it depends on some command line parameters. This needs to be fixed, or a new script must be written.
Even better: write some unit tests.
Migrated from https://code.icecube.wisc.edu/ticket/168
```json
{
"status": "closed",
"changetime": "2009-10-16T13:45:16",
"description": "The test script in cramer-rao does not work, yet, because it depends on some command line parameters. This needs to be fixed, or a new script must be written.\n\nEven better: write some unit tests.",
"reporter": "kislat",
"cc": "",
"resolution": "fixed",
"_ts": "1255700716000000",
"component": "combo reconstruction",
"summary": "Lacking a working test script for cramer-rao",
"priority": "normal",
"keywords": "",
"time": "2009-10-16T13:19:00",
"milestone": "",
"owner": "lunemann",
"type": "defect"
}
```
| 1.0 | Lacking a working test script for cramer-rao (Trac #168) - The test script in cramer-rao does not work, yet, because it depends on some command line parameters. This needs to be fixed, or a new script must be written.
Even better: write some unit tests.
Migrated from https://code.icecube.wisc.edu/ticket/168
```json
{
"status": "closed",
"changetime": "2009-10-16T13:45:16",
"description": "The test script in cramer-rao does not work, yet, because it depends on some command line parameters. This needs to be fixed, or a new script must be written.\n\nEven better: write some unit tests.",
"reporter": "kislat",
"cc": "",
"resolution": "fixed",
"_ts": "1255700716000000",
"component": "combo reconstruction",
"summary": "Lacking a working test script for cramer-rao",
"priority": "normal",
"keywords": "",
"time": "2009-10-16T13:19:00",
"milestone": "",
"owner": "lunemann",
"type": "defect"
}
```
| non_priority | lacking a working test script for cramer rao trac the test script in cramer rao does not work yet because it depends on some command line parameters this needs to be fixed or a new script must be written even better write some unit tests migrated from json status closed changetime description the test script in cramer rao does not work yet because it depends on some command line parameters this needs to be fixed or a new script must be written n neven better write some unit tests reporter kislat cc resolution fixed ts component combo reconstruction summary lacking a working test script for cramer rao priority normal keywords time milestone owner lunemann type defect | 0 |
41,003 | 16,608,104,706 | IssuesEvent | 2021-06-02 07:36:49 | ErickCR12/GymTEC | https://api.github.com/repos/ErickCR12/GymTEC | closed | Tarea 4 | API Service Funcionalidad 18: Gestión de sucursales. | Crear una solicitud PUT que recibe un atributo llave y toda la información necesaria para la modificación de una sucursal existente en la base de datos SQL. | 1.0 | Tarea 4 - Crear una solicitud PUT que recibe un atributo llave y toda la información necesaria para la modificación de una sucursal existente en la base de datos SQL. | non_priority | tarea crear una solicitud put que recibe un atributo llave y toda la información necesaria para la modificación de una sucursal existente en la base de datos sql | 0 |
176,535 | 28,112,561,132 | IssuesEvent | 2023-03-31 08:21:19 | HYF-Class19/RCP-Team | https://api.github.com/repos/HYF-Class19/RCP-Team | closed | 32 - figma term of use page - v2 | design | ## Figma design
- design the term of use page
- add a screenshot to the `readme.md`
| 1.0 | 32 - figma term of use page - v2 - ## Figma design
- design the term of use page
- add a screenshot to the `readme.md`
| non_priority | figma term of use page figma design design the term of use page add a screenshot to the readme md | 0 |
20,637 | 3,830,007,791 | IssuesEvent | 2016-03-31 13:09:47 | fsr-itse/EvaP | https://api.github.com/repos/fsr-itse/EvaP | closed | Test management commands | [C] Test [P] Minor | Because in three years, run_tasks will silently fail on the production system and nobody will notice.
* [x] **run_tasks** - shouldn't be too hard and is rather important
* [x] **anonymize** - might be a bit of work to cover it properly, but should be straightforward.
* [x] **refresh_results_cache** - should be easy
* [x] **dump_testdata** - don't know how not to overwrite the file during testing, but should be possible
the other commands are already tested or rather unsuitable for testing
* [x] **merge_users** - already has a test (#703) and is shown to be pretty broken.
* [x] **run** - don't know how to test this and there isn't really anything that could break. still, somehow running it to check that it doesn't crash right away on e.g. imports would be cool
* [x] **reload_testdata** - don't know whether it's possible at all to test that, i mean it drops the whole database...
* [ ] **import_ad** - we never used it and i don't know whether it's feasible to mock ldap
use `self.stdout.write` instead of `print` and `call_command("command_name", stdout=StringIO())` to avoid console output during tests. don't know what to do about calls to `input`. | 1.0 | Test management commands - Because in three years, run_tasks will silently fail on the production system and nobody will notice.
* [x] **run_tasks** - shouldn't be too hard and is rather important
* [x] **anonymize** - might be a bit of work to cover it properly, but should be straightforward.
* [x] **refresh_results_cache** - should be easy
* [x] **dump_testdata** - don't know how not to overwrite the file during testing, but should be possible
the other commands are already tested or rather unsuitable for testing
* [x] **merge_users** - already has a test (#703) and is shown to be pretty broken.
* [x] **run** - don't know how to test this and there isn't really anything that could break. still, somehow running it to check that it doesn't crash right away on e.g. imports would be cool
* [x] **reload_testdata** - don't know whether it's possible at all to test that, i mean it drops the whole database...
* [ ] **import_ad** - we never used it and i don't know whether it's feasible to mock ldap
use `self.stdout.write` instead of `print` and `call_command("command_name", stdout=StringIO())` to avoid console output during tests. don't know what to do about calls to `input`. | non_priority | test management commands because in three years run tasks will silently fail on the production system and nobody will notice run tasks shouldn t be too hard and is rather important anonymize might be a bit of work to cover it properly but should be straightforward refresh results cache should be easy dump testdata don t know how not to overwrite the file during testing but should be possible the other commands are already tested or rather unsuitable for testing merge users already has a test and is shown to be pretty broken run don t know how to test this and there isn t really anything that could break still somehow running it to check that it doesn t crash right away on e g imports would be cool reload testdata don t know whether it s possible at all to test that i mean it drops the whole database import ad we never used it and i don t know whether it s feasible to mock ldap use self stdout write instead of print and call command command name stdout stringio to avoid console output during tests don t know what to do about calls to input | 0 |
66,882 | 27,617,092,315 | IssuesEvent | 2023-03-09 20:17:48 | hashicorp/terraform-provider-aws | https://api.github.com/repos/hashicorp/terraform-provider-aws | closed | Glue Streaming Job timeout = null not working | question service/glue | Hi, I am trying to set up an continuously running Glue streaming job by setting timeout = null. However, TF automatically assigns the default value of 2880 min to the job. What would be the best solution to this issue?
I noticed that from another issue topic: https://github.com/hashicorp/terraform-provider-aws/issues/16797
The newer release of Terraform AWS Provider removed timeout default value, would updating my TF AWS Provider version be the right/only solution? If so, I am worrying it might affect the current TF for my pipeline since we are using TF 3.x version. Is there a solution that does not require me to change the version? Thank you! | 1.0 | Glue Streaming Job timeout = null not working - Hi, I am trying to set up an continuously running Glue streaming job by setting timeout = null. However, TF automatically assigns the default value of 2880 min to the job. What would be the best solution to this issue?
I noticed that from another issue topic: https://github.com/hashicorp/terraform-provider-aws/issues/16797
The newer release of Terraform AWS Provider removed timeout default value, would updating my TF AWS Provider version be the right/only solution? If so, I am worrying it might affect the current TF for my pipeline since we are using TF 3.x version. Is there a solution that does not require me to change the version? Thank you! | non_priority | glue streaming job timeout null not working hi i am trying to set up an continuously running glue streaming job by setting timeout null however tf automatically assigns the default value of min to the job what would be the best solution to this issue i noticed that from another issue topic the newer release of terraform aws provider removed timeout default value would updating my tf aws provider version be the right only solution if so i am worrying it might affect the current tf for my pipeline since we are using tf x version is there a solution that does not require me to change the version thank you | 0 |
264,387 | 23,115,784,517 | IssuesEvent | 2022-07-27 16:32:23 | dotnet/aspnetcore | https://api.github.com/repos/dotnet/aspnetcore | closed | Quarantine ShadowCopyIgnoresItsOwnDirectoryWithRelativePathSegmentWhenCopying | test-failure area-runtime test-fixed | <!--
Note this issue template is specifically for failing tests within the dotnet/aspnetcore repo.
-->
## Failing Test(s)
<!--
Provide the fully qualified name(s) of the failing tests.
-->
- Microsoft.AspNetCore.Server.IIS.FunctionalTests.ShadowCopyTests.ShadowCopyIgnoresItsOwnDirectoryWithRelativePathSegmentWhenCopying
## Error Message
<!--
Provide the error message associated with the test failure, if applicable.
-->
```text
Assert.False() Failure
Expected: False
Actual: True
```
## Stacktrace
<details>
<!--
Provide the stack trace associated with the test failure, if applicable.
-->
```text
at Microsoft.AspNetCore.Server.IIS.FunctionalTests.ShadowCopyTests.ShadowCopyIgnoresItsOwnDirectoryWithRelativePathSegmentWhenCopying() in /_/src/Servers/IIS/IIS/test/IIS.ShadowCopy.Tests/ShadowCopyTests.cs:line 278
--- End of stack trace from previous location ---
```
</details>
## Logs
<details>
<!--
Provide the (helix) logs associated with the test failure, if applicable.
-->
```text
[0.029s] [TestLifetime] [Information] Starting test ShadowCopyIgnoresItsOwnDirectoryWithRelativePathSegmentWhenCopying at 2022-02-07T23:10:43
[0.050s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] Deploying [Variation] :: ServerType=IIS, Runtime=CoreClr, Arch=x64, BaseUrlHint=, Publish=True
[0.051s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] Microsoft Windows NT 10.0.22000.0
[0.053s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] Using prepublished application from C:\h\w\B43109B2\w\BB44097E\e\InProcessWebSite-Portable
[0.055s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Processing C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ARM64
[0.056s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying aspnetcorev2_inprocess.dll
[0.058s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Processing C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\runtimes\win\lib\net7.0
[0.058s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying System.Diagnostics.EventLog.dll
[0.059s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying System.Diagnostics.EventLog.Messages.dll
[0.060s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Processing C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\runtimes\win\lib
[0.060s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Processing C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\runtimes\win
[0.060s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Processing C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\runtimes
[0.060s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Processing C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\wwwroot
[0.060s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying static.txt
[0.061s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Processing C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\x64
[0.061s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying aspnetcorev2_inprocess.dll
[0.062s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Processing C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\x86
[0.062s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying aspnetcorev2_inprocess.dll
[0.063s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Processing C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b
[0.063s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying InProcessWebSite.deps.json
[0.064s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying InProcessWebSite.dll
[0.065s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying InProcessWebSite.exe
[0.065s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying InProcessWebSite.pdb
[0.066s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying InProcessWebSite.runtimeconfig.json
[0.066s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Authentication.Abstractions.dll
[0.067s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Authentication.Abstractions.pdb
[0.067s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Authentication.Abstractions.xml
[0.068s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Authentication.Core.dll
[0.068s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Authentication.Core.pdb
[0.069s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Authentication.Core.xml
[0.069s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Connections.Abstractions.dll
[0.070s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Connections.Abstractions.pdb
[0.071s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Connections.Abstractions.xml
[0.071s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Hosting.Abstractions.dll
[0.072s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Hosting.Abstractions.pdb
[0.072s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Hosting.Abstractions.xml
[0.073s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Hosting.dll
[0.073s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Hosting.pdb
[0.074s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Hosting.Server.Abstractions.dll
[0.074s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Hosting.Server.Abstractions.pdb
[0.075s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Hosting.Server.Abstractions.xml
[0.077s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Hosting.xml
[0.078s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Http.Abstractions.dll
[0.078s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Http.Abstractions.pdb
[0.079s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Http.Abstractions.xml
[0.079s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Http.dll
[0.080s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Http.Extensions.dll
[0.080s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Http.Extensions.pdb
[0.081s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Http.Extensions.xml
[0.081s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Http.Features.dll
[0.082s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Http.Features.pdb
[0.082s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Http.Features.xml
[0.083s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Http.pdb
[0.083s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Http.xml
[0.085s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.HttpOverrides.dll
[0.085s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.HttpOverrides.pdb
[0.086s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.HttpOverrides.xml
[0.086s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.HttpsPolicy.dll
[0.087s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.HttpsPolicy.pdb
[0.087s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.HttpsPolicy.xml
[0.088s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.ResponseCompression.dll
[0.088s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.ResponseCompression.pdb
[0.089s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.ResponseCompression.xml
[0.089s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.IIS.dll
[0.090s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.IIS.pdb
[0.091s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.IIS.xml
[0.092s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.IISIntegration.dll
[0.093s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.IISIntegration.pdb
[0.093s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.IISIntegration.xml
[0.094s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.Kestrel.Core.dll
[0.095s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.Kestrel.Core.pdb
[0.095s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.Kestrel.Core.xml
[0.096s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.Kestrel.dll
[0.096s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.Kestrel.pdb
[0.097s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.Kestrel.Transport.Quic.dll
[0.097s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.Kestrel.Transport.Quic.pdb
[0.098s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.Kestrel.Transport.Quic.xml
[0.099s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.dll
[0.099s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.pdb
[0.100s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.xml
[0.100s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.Kestrel.xml
[0.101s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.WebUtilities.dll
[0.101s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.WebUtilities.pdb
[0.102s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.WebUtilities.xml
[0.102s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Configuration.Abstractions.dll
[0.103s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Configuration.Binder.dll
[0.104s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Configuration.CommandLine.dll
[0.104s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Configuration.dll
[0.105s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Configuration.EnvironmentVariables.dll
[0.105s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Configuration.FileExtensions.dll
[0.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Configuration.Json.dll
[0.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Configuration.UserSecrets.dll
[0.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.DependencyInjection.Abstractions.dll
[0.108s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.DependencyInjection.dll
[0.108s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Features.dll
[0.109s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Features.pdb
[0.109s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Features.xml
[0.110s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.FileProviders.Abstractions.dll
[0.111s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.FileProviders.Composite.dll
[0.111s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.FileProviders.Physical.dll
[0.112s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.FileSystemGlobbing.dll
[0.113s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Hosting.Abstractions.dll
[0.113s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Hosting.dll
[0.114s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Logging.Abstractions.dll
[0.114s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Logging.Configuration.dll
[0.115s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Logging.Console.dll
[0.115s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Logging.Debug.dll
[0.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Logging.dll
[0.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Logging.EventLog.dll
[0.117s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Logging.EventSource.dll
[0.117s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.ObjectPool.dll
[0.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.ObjectPool.pdb
[0.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.ObjectPool.xml
[0.119s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Options.ConfigurationExtensions.dll
[0.119s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Options.dll
[0.120s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Primitives.dll
[0.120s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Net.Http.Headers.dll
[0.121s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Net.Http.Headers.pdb
[0.121s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Net.Http.Headers.xml
[0.122s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying System.Diagnostics.EventLog.dll
[0.123s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying System.IO.Pipelines.dll
[0.123s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying web.config
[0.124s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying xunit.assert.dll
[0.184s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] applicationhost.config path C:\h\w\B43109B2\t\d1426cac-6b91-4f2c-b67a-5aaf0e184c03
[0.260s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] W3SVC status Running
[2.183s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] Site has started.
[2.186s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] Successfully finished IIS application directory setup.
[2.250s] [HttpTestSite] [Debug] Method: GET, RequestUri: 'http://localhost:51735/Wow!', Version: 1.1, Content: <null>, Headers:
{
}
[4.603s] [HttpTestSite] [Debug] StatusCode: 200, ReasonPhrase: 'OK', Version: 1.1, Content: System.Net.Http.HttpConnectionResponseContent, Headers:
{
Transfer-Encoding: chunked
Server: Microsoft-IIS/10.0
Date: Mon, 07 Feb 2022 23:10:48 GMT
}
[4.616s] [HttpTestSite] [Debug]
[13.195s] [HttpTestSite] [Debug] Method: GET, RequestUri: 'http://localhost:51735/HelloWorld', Version: 1.1, Content: <null>, Headers:
{
}
[15.162s] [HttpTestSite] [Debug] StatusCode: 200, ReasonPhrase: 'OK', Version: 1.1, Content: System.Net.Http.HttpConnectionResponseContent, Headers:
{
Transfer-Encoding: chunked
Server: Microsoft-IIS/10.0
Date: Mon, 07 Feb 2022 23:10:59 GMT
}
[15.168s] [HttpTestSite] [Debug] Hello World
[15.494s] [Microsoft.AspNetCore.Server.IIS.FunctionalTests.ShadowCopyTests] [Error] Test threw an exception.
Xunit.Sdk.FalseException: Assert.False() Failure
Expected: False
Actual: True
at Xunit.Assert.False(Nullable`1 condition, String userMessage) in C:\Dev\xunit\xunit\src\xunit.assert\Asserts\BooleanAsserts.cs:line 52
at Xunit.Assert.False(Boolean condition) in C:\Dev\xunit\xunit\src\xunit.assert\Asserts\BooleanAsserts.cs:line 19
at Microsoft.AspNetCore.Server.IIS.FunctionalTests.ShadowCopyTests.ShadowCopyIgnoresItsOwnDirectoryWithRelativePathSegmentWhenCopying() in /_/src/Servers/IIS/IIS/test/IIS.ShadowCopy.Tests/ShadowCopyTests.cs:line 278
at Xunit.Sdk.TestInvoker`1.<>c__DisplayClass48_1.<<InvokeTestMethodAsync>b__1>d.MoveNext() in C:\Dev\xunit\xunit\src\xunit.execution\Sdk\Frameworks\Runners\TestInvoker.cs:line 264
--- End of stack trace from previous location ---
at Xunit.Sdk.ExecutionTimer.AggregateAsync(Func`1 asyncAction) in C:\Dev\xunit\xunit\src\xunit.execution\Sdk\Frameworks\ExecutionTimer.cs:line 48
at Xunit.Sdk.ExceptionAggregator.RunAsync(Func`1 code) in C:\Dev\xunit\xunit\src\xunit.core\Sdk\ExceptionAggregator.cs:line 90
[15.519s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] Stopping site, state: Stopped
[15.532s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] Stopping pool, state: Stopping
[18.900s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] Site has stopped successfully.
[19.100s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] Host process shutting down.
[19.105s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:46.520Z, PID: 6940] [aspnetcorev2.dll] Initializing logs for 'C:\h\w\B43109B2\w\BB44097E\e\ANCM\x64\aspnetcorev2.dll'. Process Id: 6940. File Version: 17.0.22038.0. Description: IIS ASP.NET Core Module V2. Commit: 58239942c25f816606ea75b482105a5c9526f1cd.
[19.105s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:46.636Z, PID: 6940] [aspnetcorev2.dll] Copying to shadow copy directory C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\0.
[19.105s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:46.743Z, PID: 6940] [aspnetcorev2.dll] Finished copying 110 files to shadow copy directory C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\.
[19.105s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:46.814Z, PID: 6940] [aspnetcorev2.dll] Resolving hostfxr parameters for application: 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe' arguments: '.\InProcessWebSite.dll' path: 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\0'
[19.105s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:46.834Z, PID: 6940] [aspnetcorev2.dll] Known dotnet.exe location: ''
[19.105s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:46.837Z, PID: 6940] [aspnetcorev2.dll] Process path 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe' is dotnet, treating application as portable
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:46.857Z, PID: 6940] [aspnetcorev2.dll] Resolving absolute path to dotnet.exe from 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:46.863Z, PID: 6940] [aspnetcorev2.dll] Found dotnet.exe at 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:46.877Z, PID: 6940] [aspnetcorev2.dll] Resolving absolute path to hostfxr.dll from 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:46.899Z, PID: 6940] [aspnetcorev2.dll] hostfxr.dll located at 'C:\h\w\B43109B2\p\dotnet-cli\host\fxr\7.0.0-preview.2.22103.2\hostfxr.dll'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:46.903Z, PID: 6940] [aspnetcorev2.dll] Converted argument '.\InProcessWebSite.dll' to 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\0\.\InProcessWebSite.dll'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:46.918Z, PID: 6940] [aspnetcorev2.dll] Parsed hostfxr options: dotnet location: 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe' hostfxr path: 'C:\h\w\B43109B2\p\dotnet-cli\host\fxr\7.0.0-preview.2.22103.2\hostfxr.dll' arguments:
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:46.971Z, PID: 6940] [aspnetcorev2.dll] Argument[0] = 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:46.982Z, PID: 6940] [aspnetcorev2.dll] Argument[1] = 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\0\.\InProcessWebSite.dll'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:46.992Z, PID: 6940] [aspnetcorev2.dll] Loading hostfxr from location C:\h\w\B43109B2\p\dotnet-cli\host\fxr\7.0.0-preview.2.22103.2\hostfxr.dll
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.683Z, PID: 6940] [aspnetcorev2.dll] Canceling standard stream pipe reader
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.712Z, PID: 6940] [aspnetcorev2.dll] Loading request handler: 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\0\x64\aspnetcorev2_inprocess.dll'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.727Z, PID: 6940] [aspnetcorev2.dll] Creating handler application
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.744Z, PID: 6940] [aspnetcorev2_inprocess.dll] Initializing logs for 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\0\x64\aspnetcorev2_inprocess.dll'. Process Id: 6940. File Version: 17.0.22038.0. Description: IIS ASP.NET Core Module V2 Request Handler. Commit: 58239942c25f816606ea75b482105a5c9526f1cd.
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.748Z, PID: 6940] [aspnetcorev2_inprocess.dll] Waiting for initialization
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.768Z, PID: 6940] [aspnetcorev2_inprocess.dll] Starting app_offline monitoring in application 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.785Z, PID: 6940] [aspnetcorev2_inprocess.dll] Starting file watcher thread
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.816Z, PID: 6940] [aspnetcorev2_inprocess.dll] Starting in-process worker thread
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.841Z, PID: 6940] [aspnetcorev2_inprocess.dll] Resolving hostfxr parameters for application: 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe' arguments: '.\InProcessWebSite.dll' path: 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\0'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.849Z, PID: 6940] [aspnetcorev2_inprocess.dll] Known dotnet.exe location: 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.855Z, PID: 6940] [aspnetcorev2_inprocess.dll] Process path 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe' is dotnet, treating application as portable
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.858Z, PID: 6940] [aspnetcorev2_inprocess.dll] Resolving absolute path to hostfxr.dll from 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.876Z, PID: 6940] [aspnetcorev2_inprocess.dll] hostfxr.dll located at 'C:\h\w\B43109B2\p\dotnet-cli\host\fxr\7.0.0-preview.2.22103.2\hostfxr.dll'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.894Z, PID: 6940] [aspnetcorev2_inprocess.dll] Converted argument '.\InProcessWebSite.dll' to 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\0\.\InProcessWebSite.dll'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.904Z, PID: 6940] [aspnetcorev2_inprocess.dll] Parsed hostfxr options: dotnet location: 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe' hostfxr path: 'C:\h\w\B43109B2\p\dotnet-cli\host\fxr\7.0.0-preview.2.22103.2\hostfxr.dll' arguments:
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.920Z, PID: 6940] [aspnetcorev2_inprocess.dll] Argument[0] = 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.923Z, PID: 6940] [aspnetcorev2_inprocess.dll] Argument[1] = 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\0\.\InProcessWebSite.dll'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.940Z, PID: 6940] [aspnetcorev2_inprocess.dll] Setting environment variable ASPNETCORE_DETAILEDERRORS=true
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.957Z, PID: 6940] [aspnetcorev2_inprocess.dll] Setting environment variable ASPNETCORE_IIS_HTTPAUTH=anonymous;
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.990Z, PID: 6940] [aspnetcorev2_inprocess.dll] Setting environment variable ASPNETCORE_IIS_PHYSICAL_PATH=C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:48.009Z, PID: 6940] [aspnetcorev2_inprocess.dll] Loading hostfxr from location C:\h\w\B43109B2\p\dotnet-cli\host\fxr\7.0.0-preview.2.22103.2\hostfxr.dll
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:48.058Z, PID: 6940] [aspnetcorev2_inprocess.dll] Initial Dll directory: '', current directory: 'c:\windows\system32\inetsrv'
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:48.089Z, PID: 6940] [aspnetcorev2_inprocess.dll] Setting dll directory to c:\windows\system32\inetsrv
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:48.094Z, PID: 6940] [aspnetcorev2_inprocess.dll] Setting current directory to C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:48.343Z, PID: 6940] [aspnetcorev2_inprocess.dll] In-process callbacks set
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:48.430Z, PID: 6940] [aspnetcorev2_inprocess.dll] Event Log: 'Application 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\' started successfully.'
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] End Event Log Message.
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:48.638Z, PID: 6940] [aspnetcorev2_inprocess.dll] Detected dll change, resetting timer callback which will eventually trigger shutdown.
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:48.677Z, PID: 6940] [aspnetcorev2.dll] ASPNET_CORE_GLOBAL_MODULE::OnGlobalConfigurationChange 'MACHINE/WEBROOT/APPHOST/DEFAULT WEB SITE'
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:48.726Z, PID: 6940] [aspnetcorev2_inprocess.dll] Received file change notification in application 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\'
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:48.738Z, PID: 6940] [aspnetcorev2.dll] Stopping application '/LM/W3SVC/1/ROOT'
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:48.835Z, PID: 6940] [aspnetcorev2_inprocess.dll] Event Log: 'Application 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\' was recycled after detecting file change in application directory.'
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] End Event Log Message.
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:48.836Z, PID: 6940] [aspnetcorev2_inprocess.dll] Stopping file watching.
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:49.425Z, PID: 6940] [aspnetcorev2_inprocess.dll] Starting copy on shutdown in filewatcher, creating directory.
[19.114s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:49.429Z, PID: 6940] [aspnetcorev2_inprocess.dll] Copying new shadow copy directory to C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\1.
[19.114s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:49.583Z, PID: 6940] [aspnetcorev2_inprocess.dll] Finished copy on shutdown to C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\1. 110 files copied.
[19.115s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:49.621Z, PID: 6940] [aspnetcorev2_inprocess.dll] Stopping CLR
[19.115s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:49.627Z, PID: 6940] [aspnetcorev2_inprocess.dll] Drained all requests, notifying managed.
[19.115s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:49.628Z, PID: 6940] [aspnetcorev2_inprocess.dll] Starting shutdown sequence 0
[19.115s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:49.652Z, PID: 6940] [aspnetcorev2_inprocess.dll] Waiting for 0 requests to drain
[19.115s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:49.702Z, PID: 6940] [aspnetcorev2_inprocess.dll] Managed application exited with code 0
[19.115s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:49.712Z, PID: 6940] [aspnetcorev2_inprocess.dll] Clr thread wait ended: clrThreadExited: 1
[19.115s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:49.739Z, PID: 6940] [aspnetcorev2_inprocess.dll] Event Log: 'Application 'MACHINE/WEBROOT/APPHOST/DEFAULT WEB SITE' has shutdown.'
[19.115s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] End Event Log Message.
[19.115s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:49.745Z, PID: 6940] [aspnetcorev2_inprocess.dll] Canceling standard stream pipe reader
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:49.750Z, PID: 6940] [aspnetcorev2_inprocess.dll] Stopping in-process worker thread
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:49.768Z, PID: 6940] [aspnetcorev2_inprocess.dll] AspNetCore InProcess Recycle Process on Demand
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:49.901Z, PID: 6940] [aspnetcorev2.dll] ASPNET_CORE_GLOBAL_MODULE::OnGlobalStopListening
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:57.107Z, PID: 608] [aspnetcorev2.dll] Initializing logs for 'C:\h\w\B43109B2\w\BB44097E\e\ANCM\x64\aspnetcorev2.dll'. Process Id: 608. File Version: 17.0.22038.0. Description: IIS ASP.NET Core Module V2. Commit: 58239942c25f816606ea75b482105a5c9526f1cd.
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:57.511Z, PID: 608] [aspnetcorev2.dll] Copying to shadow copy directory C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\1.
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:57.535Z, PID: 608] [aspnetcorev2.dll] Finished copying 0 files to shadow copy directory C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\.
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:57.538Z, PID: 608] [aspnetcorev2.dll] Resolving hostfxr parameters for application: 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe' arguments: '.\InProcessWebSite.dll' path: 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\1'
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:57.571Z, PID: 608] [aspnetcorev2.dll] Known dotnet.exe location: ''
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:57.617Z, PID: 608] [aspnetcorev2.dll] Process path 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe' is dotnet, treating application as portable
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:57.634Z, PID: 608] [aspnetcorev2.dll] Resolving absolute path to dotnet.exe from 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe'
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:57.832Z, PID: 608] [aspnetcorev2.dll] Found dotnet.exe at 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe'
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:57.875Z, PID: 608] [aspnetcorev2.dll] Resolving absolute path to hostfxr.dll from 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe'
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:57.914Z, PID: 608] [aspnetcorev2.dll] hostfxr.dll located at 'C:\h\w\B43109B2\p\dotnet-cli\host\fxr\7.0.0-preview.2.22103.2\hostfxr.dll'
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:57.953Z, PID: 608] [aspnetcorev2.dll] Converted argument '.\InProcessWebSite.dll' to 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\1\.\InProcessWebSite.dll'
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:57.983Z, PID: 608] [aspnetcorev2.dll] Parsed hostfxr options: dotnet location: 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe' hostfxr path: 'C:\h\w\B43109B2\p\dotnet-cli\host\fxr\7.0.0-preview.2.22103.2\hostfxr.dll' arguments:
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.000Z, PID: 608] [aspnetcorev2.dll] Argument[0] = 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe'
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.017Z, PID: 608] [aspnetcorev2.dll] Argument[1] = 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\1\.\InProcessWebSite.dll'
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.037Z, PID: 608] [aspnetcorev2.dll] Loading hostfxr from location C:\h\w\B43109B2\p\dotnet-cli\host\fxr\7.0.0-preview.2.22103.2\hostfxr.dll
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.108Z, PID: 608] [aspnetcorev2.dll] Canceling standard stream pipe reader
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.139Z, PID: 608] [aspnetcorev2.dll] Loading request handler: 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\1\x64\aspnetcorev2_inprocess.dll'
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.148Z, PID: 608] [aspnetcorev2.dll] Creating handler application
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.153Z, PID: 608] [aspnetcorev2_inprocess.dll] Initializing logs for 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\1\x64\aspnetcorev2_inprocess.dll'. Process Id: 608. File Version: 17.0.22038.0. Description: IIS ASP.NET Core Module V2 Request Handler. Commit: 58239942c25f816606ea75b482105a5c9526f1cd.
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.191Z, PID: 608] [aspnetcorev2_inprocess.dll] Waiting for initialization
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.198Z, PID: 608] [aspnetcorev2_inprocess.dll] Starting app_offline monitoring in application 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\'
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.204Z, PID: 608] [aspnetcorev2_inprocess.dll] Starting file watcher thread
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.236Z, PID: 608] [aspnetcorev2_inprocess.dll] Starting in-process worker thread
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.237Z, PID: 608] [aspnetcorev2_inprocess.dll] Exception 'remove_all: Access is denied.: "C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\0"' caught at D:\a\_work\1\s\src\Servers\IIS\AspNetCoreModuleV2\InProcessRequestHandler\inprocessapplication.cpp:195
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.272Z, PID: 608] [aspnetcorev2_inprocess.dll] Resolving hostfxr parameters for application: 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe' arguments: '.\InProcessWebSite.dll' path: 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\1'
[19.117s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.307Z, PID: 608] [aspnetcorev2_inprocess.dll] Known dotnet.exe location: 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe'
[19.117s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.313Z, PID: 608] [aspnetcorev2_inprocess.dll] Process path 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe' is dotnet, treating application as portable
[19.117s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.316Z, PID: 608] [aspnetcorev2_inprocess.dll] Resolving absolute path to hostfxr.dll from 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe'
[19.117s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.351Z, PID: 608] [aspnetcorev2_inprocess.dll] hostfxr.dll located at 'C:\h\w\B43109B2\p\dotnet-cli\host\fxr\7.0.0-preview.2.22103.2\hostfxr.dll'
[19.117s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.355Z, PID: 608] [aspnetcorev2_inprocess.dll] Converted argument '.\InProcessWebSite.dll' to 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\1\.\InProcessWebSite.dll'
[19.117s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.364Z, PID: 608] [aspnetcorev2_inprocess.dll] Parsed hostfxr options: dotnet location: 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe' hostfxr path: 'C:\h\w\B43109B2\p\dotnet-cli\host\fxr\7.0.0-preview.2.22103.2\hostfxr.dll' arguments:
[19.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.400Z, PID: 608] [aspnetcorev2_inprocess.dll] Argument[0] = 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe'
[19.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.421Z, PID: 608] [aspnetcorev2_inprocess.dll] Argument[1] = 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\1\.\InProcessWebSite.dll'
[19.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.442Z, PID: 608] [aspnetcorev2_inprocess.dll] Setting environment variable ASPNETCORE_DETAILEDERRORS=true
[19.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.465Z, PID: 608] [aspnetcorev2_inprocess.dll] Setting environment variable ASPNETCORE_IIS_HTTPAUTH=anonymous;
[19.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.483Z, PID: 608] [aspnetcorev2_inprocess.dll] Setting environment variable ASPNETCORE_IIS_PHYSICAL_PATH=C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\
[19.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.502Z, PID: 608] [aspnetcorev2_inprocess.dll] Loading hostfxr from location C:\h\w\B43109B2\p\dotnet-cli\host\fxr\7.0.0-preview.2.22103.2\hostfxr.dll
[19.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.534Z, PID: 608] [aspnetcorev2_inprocess.dll] Initial Dll directory: '', current directory: 'c:\windows\system32\inetsrv'
[19.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.557Z, PID: 608] [aspnetcorev2_inprocess.dll] Setting dll directory to c:\windows\system32\inetsrv
[19.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.562Z, PID: 608] [aspnetcorev2_inprocess.dll] Setting current directory to C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\
[19.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.856Z, PID: 608] [aspnetcorev2_inprocess.dll] In-process callbacks set
[19.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.906Z, PID: 608] [aspnetcorev2_inprocess.dll] Event Log: 'Application 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\' started successfully.'
[19.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] End Event Log Message.
[19.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.440Z, PID: 608] [aspnetcorev2.dll] ASPNET_CORE_GLOBAL_MODULE::OnGlobalStopListening
[19.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.448Z, PID: 608] [aspnetcorev2.dll] Stopping application '/LM/W3SVC/1/ROOT'
[19.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.452Z, PID: 608] [aspnetcorev2_inprocess.dll] Stopping file watching.
[19.119s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.457Z, PID: 608] [aspnetcorev2_inprocess.dll] Starting copy on shutdown in filewatcher, creating directory.
[19.119s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.462Z, PID: 608] [aspnetcorev2_inprocess.dll] Copying new shadow copy directory to C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\2.
[19.119s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.532Z, PID: 608] [aspnetcorev2_inprocess.dll] Finished copy on shutdown to C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\2. 110 files copied.
[19.119s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.553Z, PID: 608] [aspnetcorev2_inprocess.dll] Stopping file watcher thread
[19.119s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.553Z, PID: 608] [aspnetcorev2_inprocess.dll] Stopping CLR
[19.119s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.554Z, PID: 608] [aspnetcorev2_inprocess.dll] Received file change notification in application 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\'
[19.120s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.583Z, PID: 608] [aspnetcorev2_inprocess.dll] Starting shutdown sequence 0
[19.120s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.584Z, PID: 608] [aspnetcorev2_inprocess.dll] Drained all requests, notifying managed.
[19.120s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.589Z, PID: 608] [aspnetcorev2_inprocess.dll] Waiting for 0 requests to drain
[19.120s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.589Z, PID: 608] [aspnetcorev2_inprocess.dll] Event Log: 'Application 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\' was recycled after detecting file change in application directory.'
[19.120s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] End Event Log Message.
[19.120s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.621Z, PID: 608] [aspnetcorev2_inprocess.dll] Managed application exited with code 0
[19.120s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.626Z, PID: 608] [aspnetcorev2_inprocess.dll] Clr thread wait ended: clrThreadExited: 1
[19.120s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.634Z, PID: 608] [aspnetcorev2_inprocess.dll] Event Log: 'Application 'MACHINE/WEBROOT/APPHOST/DEFAULT WEB SITE' has shutdown.'
[19.120s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] End Event Log Message.
[19.120s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.637Z, PID: 608] [aspnetcorev2_inprocess.dll] Canceling standard stream pipe reader
[19.120s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.641Z, PID: 608] [aspnetcorev2_inprocess.dll] Stopping in-process worker thread
[19.120s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:11:00.770Z, PID: 608] [aspnetcorev2.dll] ASPNET_CORE_GLOBAL_MODULE::Terminate
[19.354s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Warning] Failed to delete directory : Access to the path 'InProcessWebSite.dll' is denied.
[19.472s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Warning] Failed to delete directory : Access to the path 'InProcessWebSite.dll' is denied.
[19.582s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Warning] Failed to delete directory : Access to the path 'InProcessWebSite.dll' is denied.
[19.687s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [Time]: Total time taken for this test variation '19.6351558' seconds
```
</details>
## Build
<!--
Provide a link to the build where the test failure occurred.
-->
https://dev.azure.com/dnceng/public/_build/results?buildId=1598027 | 2.0 | Quarantine ShadowCopyIgnoresItsOwnDirectoryWithRelativePathSegmentWhenCopying - <!--
Note this issue template is specifically for failing tests within the dotnet/aspnetcore repo.
-->
## Failing Test(s)
<!--
Provide the fully qualified name(s) of the failing tests.
-->
- Microsoft.AspNetCore.Server.IIS.FunctionalTests.ShadowCopyTests.ShadowCopyIgnoresItsOwnDirectoryWithRelativePathSegmentWhenCopying
## Error Message
<!--
Provide the error message associated with the test failure, if applicable.
-->
```text
Assert.False() Failure
Expected: False
Actual: True
```
## Stacktrace
<details>
<!--
Provide the stack trace associated with the test failure, if applicable.
-->
```text
at Microsoft.AspNetCore.Server.IIS.FunctionalTests.ShadowCopyTests.ShadowCopyIgnoresItsOwnDirectoryWithRelativePathSegmentWhenCopying() in /_/src/Servers/IIS/IIS/test/IIS.ShadowCopy.Tests/ShadowCopyTests.cs:line 278
--- End of stack trace from previous location ---
```
</details>
## Logs
<details>
<!--
Provide the (helix) logs associated with the test failure, if applicable.
-->
```text
[0.029s] [TestLifetime] [Information] Starting test ShadowCopyIgnoresItsOwnDirectoryWithRelativePathSegmentWhenCopying at 2022-02-07T23:10:43
[0.050s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] Deploying [Variation] :: ServerType=IIS, Runtime=CoreClr, Arch=x64, BaseUrlHint=, Publish=True
[0.051s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] Microsoft Windows NT 10.0.22000.0
[0.053s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] Using prepublished application from C:\h\w\B43109B2\w\BB44097E\e\InProcessWebSite-Portable
[0.055s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Processing C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ARM64
[0.056s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying aspnetcorev2_inprocess.dll
[0.058s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Processing C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\runtimes\win\lib\net7.0
[0.058s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying System.Diagnostics.EventLog.dll
[0.059s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying System.Diagnostics.EventLog.Messages.dll
[0.060s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Processing C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\runtimes\win\lib
[0.060s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Processing C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\runtimes\win
[0.060s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Processing C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\runtimes
[0.060s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Processing C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\wwwroot
[0.060s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying static.txt
[0.061s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Processing C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\x64
[0.061s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying aspnetcorev2_inprocess.dll
[0.062s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Processing C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\x86
[0.062s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying aspnetcorev2_inprocess.dll
[0.063s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Processing C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b
[0.063s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying InProcessWebSite.deps.json
[0.064s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying InProcessWebSite.dll
[0.065s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying InProcessWebSite.exe
[0.065s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying InProcessWebSite.pdb
[0.066s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying InProcessWebSite.runtimeconfig.json
[0.066s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Authentication.Abstractions.dll
[0.067s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Authentication.Abstractions.pdb
[0.067s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Authentication.Abstractions.xml
[0.068s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Authentication.Core.dll
[0.068s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Authentication.Core.pdb
[0.069s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Authentication.Core.xml
[0.069s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Connections.Abstractions.dll
[0.070s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Connections.Abstractions.pdb
[0.071s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Connections.Abstractions.xml
[0.071s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Hosting.Abstractions.dll
[0.072s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Hosting.Abstractions.pdb
[0.072s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Hosting.Abstractions.xml
[0.073s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Hosting.dll
[0.073s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Hosting.pdb
[0.074s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Hosting.Server.Abstractions.dll
[0.074s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Hosting.Server.Abstractions.pdb
[0.075s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Hosting.Server.Abstractions.xml
[0.077s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Hosting.xml
[0.078s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Http.Abstractions.dll
[0.078s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Http.Abstractions.pdb
[0.079s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Http.Abstractions.xml
[0.079s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Http.dll
[0.080s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Http.Extensions.dll
[0.080s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Http.Extensions.pdb
[0.081s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Http.Extensions.xml
[0.081s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Http.Features.dll
[0.082s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Http.Features.pdb
[0.082s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Http.Features.xml
[0.083s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Http.pdb
[0.083s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Http.xml
[0.085s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.HttpOverrides.dll
[0.085s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.HttpOverrides.pdb
[0.086s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.HttpOverrides.xml
[0.086s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.HttpsPolicy.dll
[0.087s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.HttpsPolicy.pdb
[0.087s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.HttpsPolicy.xml
[0.088s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.ResponseCompression.dll
[0.088s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.ResponseCompression.pdb
[0.089s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.ResponseCompression.xml
[0.089s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.IIS.dll
[0.090s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.IIS.pdb
[0.091s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.IIS.xml
[0.092s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.IISIntegration.dll
[0.093s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.IISIntegration.pdb
[0.093s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.IISIntegration.xml
[0.094s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.Kestrel.Core.dll
[0.095s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.Kestrel.Core.pdb
[0.095s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.Kestrel.Core.xml
[0.096s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.Kestrel.dll
[0.096s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.Kestrel.pdb
[0.097s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.Kestrel.Transport.Quic.dll
[0.097s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.Kestrel.Transport.Quic.pdb
[0.098s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.Kestrel.Transport.Quic.xml
[0.099s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.dll
[0.099s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.pdb
[0.100s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.xml
[0.100s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.Server.Kestrel.xml
[0.101s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.WebUtilities.dll
[0.101s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.WebUtilities.pdb
[0.102s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.AspNetCore.WebUtilities.xml
[0.102s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Configuration.Abstractions.dll
[0.103s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Configuration.Binder.dll
[0.104s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Configuration.CommandLine.dll
[0.104s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Configuration.dll
[0.105s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Configuration.EnvironmentVariables.dll
[0.105s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Configuration.FileExtensions.dll
[0.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Configuration.Json.dll
[0.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Configuration.UserSecrets.dll
[0.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.DependencyInjection.Abstractions.dll
[0.108s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.DependencyInjection.dll
[0.108s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Features.dll
[0.109s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Features.pdb
[0.109s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Features.xml
[0.110s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.FileProviders.Abstractions.dll
[0.111s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.FileProviders.Composite.dll
[0.111s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.FileProviders.Physical.dll
[0.112s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.FileSystemGlobbing.dll
[0.113s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Hosting.Abstractions.dll
[0.113s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Hosting.dll
[0.114s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Logging.Abstractions.dll
[0.114s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Logging.Configuration.dll
[0.115s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Logging.Console.dll
[0.115s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Logging.Debug.dll
[0.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Logging.dll
[0.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Logging.EventLog.dll
[0.117s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Logging.EventSource.dll
[0.117s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.ObjectPool.dll
[0.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.ObjectPool.pdb
[0.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.ObjectPool.xml
[0.119s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Options.ConfigurationExtensions.dll
[0.119s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Options.dll
[0.120s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Extensions.Primitives.dll
[0.120s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Net.Http.Headers.dll
[0.121s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Net.Http.Headers.pdb
[0.121s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying Microsoft.Net.Http.Headers.xml
[0.122s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying System.Diagnostics.EventLog.dll
[0.123s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying System.IO.Pipelines.dll
[0.123s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying web.config
[0.124s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Debug] Copying xunit.assert.dll
[0.184s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] applicationhost.config path C:\h\w\B43109B2\t\d1426cac-6b91-4f2c-b67a-5aaf0e184c03
[0.260s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] W3SVC status Running
[2.183s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] Site has started.
[2.186s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] Successfully finished IIS application directory setup.
[2.250s] [HttpTestSite] [Debug] Method: GET, RequestUri: 'http://localhost:51735/Wow!', Version: 1.1, Content: <null>, Headers:
{
}
[4.603s] [HttpTestSite] [Debug] StatusCode: 200, ReasonPhrase: 'OK', Version: 1.1, Content: System.Net.Http.HttpConnectionResponseContent, Headers:
{
Transfer-Encoding: chunked
Server: Microsoft-IIS/10.0
Date: Mon, 07 Feb 2022 23:10:48 GMT
}
[4.616s] [HttpTestSite] [Debug]
[13.195s] [HttpTestSite] [Debug] Method: GET, RequestUri: 'http://localhost:51735/HelloWorld', Version: 1.1, Content: <null>, Headers:
{
}
[15.162s] [HttpTestSite] [Debug] StatusCode: 200, ReasonPhrase: 'OK', Version: 1.1, Content: System.Net.Http.HttpConnectionResponseContent, Headers:
{
Transfer-Encoding: chunked
Server: Microsoft-IIS/10.0
Date: Mon, 07 Feb 2022 23:10:59 GMT
}
[15.168s] [HttpTestSite] [Debug] Hello World
[15.494s] [Microsoft.AspNetCore.Server.IIS.FunctionalTests.ShadowCopyTests] [Error] Test threw an exception.
Xunit.Sdk.FalseException: Assert.False() Failure
Expected: False
Actual: True
at Xunit.Assert.False(Nullable`1 condition, String userMessage) in C:\Dev\xunit\xunit\src\xunit.assert\Asserts\BooleanAsserts.cs:line 52
at Xunit.Assert.False(Boolean condition) in C:\Dev\xunit\xunit\src\xunit.assert\Asserts\BooleanAsserts.cs:line 19
at Microsoft.AspNetCore.Server.IIS.FunctionalTests.ShadowCopyTests.ShadowCopyIgnoresItsOwnDirectoryWithRelativePathSegmentWhenCopying() in /_/src/Servers/IIS/IIS/test/IIS.ShadowCopy.Tests/ShadowCopyTests.cs:line 278
at Xunit.Sdk.TestInvoker`1.<>c__DisplayClass48_1.<<InvokeTestMethodAsync>b__1>d.MoveNext() in C:\Dev\xunit\xunit\src\xunit.execution\Sdk\Frameworks\Runners\TestInvoker.cs:line 264
--- End of stack trace from previous location ---
at Xunit.Sdk.ExecutionTimer.AggregateAsync(Func`1 asyncAction) in C:\Dev\xunit\xunit\src\xunit.execution\Sdk\Frameworks\ExecutionTimer.cs:line 48
at Xunit.Sdk.ExceptionAggregator.RunAsync(Func`1 code) in C:\Dev\xunit\xunit\src\xunit.core\Sdk\ExceptionAggregator.cs:line 90
[15.519s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] Stopping site, state: Stopped
[15.532s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] Stopping pool, state: Stopping
[18.900s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] Site has stopped successfully.
[19.100s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] Host process shutting down.
[19.105s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:46.520Z, PID: 6940] [aspnetcorev2.dll] Initializing logs for 'C:\h\w\B43109B2\w\BB44097E\e\ANCM\x64\aspnetcorev2.dll'. Process Id: 6940. File Version: 17.0.22038.0. Description: IIS ASP.NET Core Module V2. Commit: 58239942c25f816606ea75b482105a5c9526f1cd.
[19.105s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:46.636Z, PID: 6940] [aspnetcorev2.dll] Copying to shadow copy directory C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\0.
[19.105s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:46.743Z, PID: 6940] [aspnetcorev2.dll] Finished copying 110 files to shadow copy directory C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\.
[19.105s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:46.814Z, PID: 6940] [aspnetcorev2.dll] Resolving hostfxr parameters for application: 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe' arguments: '.\InProcessWebSite.dll' path: 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\0'
[19.105s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:46.834Z, PID: 6940] [aspnetcorev2.dll] Known dotnet.exe location: ''
[19.105s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:46.837Z, PID: 6940] [aspnetcorev2.dll] Process path 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe' is dotnet, treating application as portable
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:46.857Z, PID: 6940] [aspnetcorev2.dll] Resolving absolute path to dotnet.exe from 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:46.863Z, PID: 6940] [aspnetcorev2.dll] Found dotnet.exe at 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:46.877Z, PID: 6940] [aspnetcorev2.dll] Resolving absolute path to hostfxr.dll from 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:46.899Z, PID: 6940] [aspnetcorev2.dll] hostfxr.dll located at 'C:\h\w\B43109B2\p\dotnet-cli\host\fxr\7.0.0-preview.2.22103.2\hostfxr.dll'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:46.903Z, PID: 6940] [aspnetcorev2.dll] Converted argument '.\InProcessWebSite.dll' to 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\0\.\InProcessWebSite.dll'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:46.918Z, PID: 6940] [aspnetcorev2.dll] Parsed hostfxr options: dotnet location: 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe' hostfxr path: 'C:\h\w\B43109B2\p\dotnet-cli\host\fxr\7.0.0-preview.2.22103.2\hostfxr.dll' arguments:
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:46.971Z, PID: 6940] [aspnetcorev2.dll] Argument[0] = 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:46.982Z, PID: 6940] [aspnetcorev2.dll] Argument[1] = 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\0\.\InProcessWebSite.dll'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:46.992Z, PID: 6940] [aspnetcorev2.dll] Loading hostfxr from location C:\h\w\B43109B2\p\dotnet-cli\host\fxr\7.0.0-preview.2.22103.2\hostfxr.dll
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.683Z, PID: 6940] [aspnetcorev2.dll] Canceling standard stream pipe reader
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.712Z, PID: 6940] [aspnetcorev2.dll] Loading request handler: 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\0\x64\aspnetcorev2_inprocess.dll'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.727Z, PID: 6940] [aspnetcorev2.dll] Creating handler application
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.744Z, PID: 6940] [aspnetcorev2_inprocess.dll] Initializing logs for 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\0\x64\aspnetcorev2_inprocess.dll'. Process Id: 6940. File Version: 17.0.22038.0. Description: IIS ASP.NET Core Module V2 Request Handler. Commit: 58239942c25f816606ea75b482105a5c9526f1cd.
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.748Z, PID: 6940] [aspnetcorev2_inprocess.dll] Waiting for initialization
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.768Z, PID: 6940] [aspnetcorev2_inprocess.dll] Starting app_offline monitoring in application 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.785Z, PID: 6940] [aspnetcorev2_inprocess.dll] Starting file watcher thread
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.816Z, PID: 6940] [aspnetcorev2_inprocess.dll] Starting in-process worker thread
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.841Z, PID: 6940] [aspnetcorev2_inprocess.dll] Resolving hostfxr parameters for application: 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe' arguments: '.\InProcessWebSite.dll' path: 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\0'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.849Z, PID: 6940] [aspnetcorev2_inprocess.dll] Known dotnet.exe location: 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.855Z, PID: 6940] [aspnetcorev2_inprocess.dll] Process path 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe' is dotnet, treating application as portable
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.858Z, PID: 6940] [aspnetcorev2_inprocess.dll] Resolving absolute path to hostfxr.dll from 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.876Z, PID: 6940] [aspnetcorev2_inprocess.dll] hostfxr.dll located at 'C:\h\w\B43109B2\p\dotnet-cli\host\fxr\7.0.0-preview.2.22103.2\hostfxr.dll'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.894Z, PID: 6940] [aspnetcorev2_inprocess.dll] Converted argument '.\InProcessWebSite.dll' to 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\0\.\InProcessWebSite.dll'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.904Z, PID: 6940] [aspnetcorev2_inprocess.dll] Parsed hostfxr options: dotnet location: 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe' hostfxr path: 'C:\h\w\B43109B2\p\dotnet-cli\host\fxr\7.0.0-preview.2.22103.2\hostfxr.dll' arguments:
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.920Z, PID: 6940] [aspnetcorev2_inprocess.dll] Argument[0] = 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.923Z, PID: 6940] [aspnetcorev2_inprocess.dll] Argument[1] = 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\0\.\InProcessWebSite.dll'
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.940Z, PID: 6940] [aspnetcorev2_inprocess.dll] Setting environment variable ASPNETCORE_DETAILEDERRORS=true
[19.106s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.957Z, PID: 6940] [aspnetcorev2_inprocess.dll] Setting environment variable ASPNETCORE_IIS_HTTPAUTH=anonymous;
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:47.990Z, PID: 6940] [aspnetcorev2_inprocess.dll] Setting environment variable ASPNETCORE_IIS_PHYSICAL_PATH=C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:48.009Z, PID: 6940] [aspnetcorev2_inprocess.dll] Loading hostfxr from location C:\h\w\B43109B2\p\dotnet-cli\host\fxr\7.0.0-preview.2.22103.2\hostfxr.dll
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:48.058Z, PID: 6940] [aspnetcorev2_inprocess.dll] Initial Dll directory: '', current directory: 'c:\windows\system32\inetsrv'
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:48.089Z, PID: 6940] [aspnetcorev2_inprocess.dll] Setting dll directory to c:\windows\system32\inetsrv
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:48.094Z, PID: 6940] [aspnetcorev2_inprocess.dll] Setting current directory to C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:48.343Z, PID: 6940] [aspnetcorev2_inprocess.dll] In-process callbacks set
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:48.430Z, PID: 6940] [aspnetcorev2_inprocess.dll] Event Log: 'Application 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\' started successfully.'
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] End Event Log Message.
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:48.638Z, PID: 6940] [aspnetcorev2_inprocess.dll] Detected dll change, resetting timer callback which will eventually trigger shutdown.
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:48.677Z, PID: 6940] [aspnetcorev2.dll] ASPNET_CORE_GLOBAL_MODULE::OnGlobalConfigurationChange 'MACHINE/WEBROOT/APPHOST/DEFAULT WEB SITE'
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:48.726Z, PID: 6940] [aspnetcorev2_inprocess.dll] Received file change notification in application 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\'
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:48.738Z, PID: 6940] [aspnetcorev2.dll] Stopping application '/LM/W3SVC/1/ROOT'
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:48.835Z, PID: 6940] [aspnetcorev2_inprocess.dll] Event Log: 'Application 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\' was recycled after detecting file change in application directory.'
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] End Event Log Message.
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:48.836Z, PID: 6940] [aspnetcorev2_inprocess.dll] Stopping file watching.
[19.107s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:49.425Z, PID: 6940] [aspnetcorev2_inprocess.dll] Starting copy on shutdown in filewatcher, creating directory.
[19.114s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:49.429Z, PID: 6940] [aspnetcorev2_inprocess.dll] Copying new shadow copy directory to C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\1.
[19.114s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:49.583Z, PID: 6940] [aspnetcorev2_inprocess.dll] Finished copy on shutdown to C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\1. 110 files copied.
[19.115s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:49.621Z, PID: 6940] [aspnetcorev2_inprocess.dll] Stopping CLR
[19.115s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:49.627Z, PID: 6940] [aspnetcorev2_inprocess.dll] Drained all requests, notifying managed.
[19.115s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:49.628Z, PID: 6940] [aspnetcorev2_inprocess.dll] Starting shutdown sequence 0
[19.115s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:49.652Z, PID: 6940] [aspnetcorev2_inprocess.dll] Waiting for 0 requests to drain
[19.115s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:49.702Z, PID: 6940] [aspnetcorev2_inprocess.dll] Managed application exited with code 0
[19.115s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:49.712Z, PID: 6940] [aspnetcorev2_inprocess.dll] Clr thread wait ended: clrThreadExited: 1
[19.115s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:49.739Z, PID: 6940] [aspnetcorev2_inprocess.dll] Event Log: 'Application 'MACHINE/WEBROOT/APPHOST/DEFAULT WEB SITE' has shutdown.'
[19.115s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] End Event Log Message.
[19.115s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:49.745Z, PID: 6940] [aspnetcorev2_inprocess.dll] Canceling standard stream pipe reader
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:49.750Z, PID: 6940] [aspnetcorev2_inprocess.dll] Stopping in-process worker thread
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:49.768Z, PID: 6940] [aspnetcorev2_inprocess.dll] AspNetCore InProcess Recycle Process on Demand
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:49.901Z, PID: 6940] [aspnetcorev2.dll] ASPNET_CORE_GLOBAL_MODULE::OnGlobalStopListening
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:57.107Z, PID: 608] [aspnetcorev2.dll] Initializing logs for 'C:\h\w\B43109B2\w\BB44097E\e\ANCM\x64\aspnetcorev2.dll'. Process Id: 608. File Version: 17.0.22038.0. Description: IIS ASP.NET Core Module V2. Commit: 58239942c25f816606ea75b482105a5c9526f1cd.
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:57.511Z, PID: 608] [aspnetcorev2.dll] Copying to shadow copy directory C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\1.
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:57.535Z, PID: 608] [aspnetcorev2.dll] Finished copying 0 files to shadow copy directory C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\.
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:57.538Z, PID: 608] [aspnetcorev2.dll] Resolving hostfxr parameters for application: 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe' arguments: '.\InProcessWebSite.dll' path: 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\1'
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:57.571Z, PID: 608] [aspnetcorev2.dll] Known dotnet.exe location: ''
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:57.617Z, PID: 608] [aspnetcorev2.dll] Process path 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe' is dotnet, treating application as portable
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:57.634Z, PID: 608] [aspnetcorev2.dll] Resolving absolute path to dotnet.exe from 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe'
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:57.832Z, PID: 608] [aspnetcorev2.dll] Found dotnet.exe at 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe'
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:57.875Z, PID: 608] [aspnetcorev2.dll] Resolving absolute path to hostfxr.dll from 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe'
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:57.914Z, PID: 608] [aspnetcorev2.dll] hostfxr.dll located at 'C:\h\w\B43109B2\p\dotnet-cli\host\fxr\7.0.0-preview.2.22103.2\hostfxr.dll'
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:57.953Z, PID: 608] [aspnetcorev2.dll] Converted argument '.\InProcessWebSite.dll' to 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\1\.\InProcessWebSite.dll'
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:57.983Z, PID: 608] [aspnetcorev2.dll] Parsed hostfxr options: dotnet location: 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe' hostfxr path: 'C:\h\w\B43109B2\p\dotnet-cli\host\fxr\7.0.0-preview.2.22103.2\hostfxr.dll' arguments:
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.000Z, PID: 608] [aspnetcorev2.dll] Argument[0] = 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe'
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.017Z, PID: 608] [aspnetcorev2.dll] Argument[1] = 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\1\.\InProcessWebSite.dll'
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.037Z, PID: 608] [aspnetcorev2.dll] Loading hostfxr from location C:\h\w\B43109B2\p\dotnet-cli\host\fxr\7.0.0-preview.2.22103.2\hostfxr.dll
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.108Z, PID: 608] [aspnetcorev2.dll] Canceling standard stream pipe reader
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.139Z, PID: 608] [aspnetcorev2.dll] Loading request handler: 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\1\x64\aspnetcorev2_inprocess.dll'
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.148Z, PID: 608] [aspnetcorev2.dll] Creating handler application
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.153Z, PID: 608] [aspnetcorev2_inprocess.dll] Initializing logs for 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\1\x64\aspnetcorev2_inprocess.dll'. Process Id: 608. File Version: 17.0.22038.0. Description: IIS ASP.NET Core Module V2 Request Handler. Commit: 58239942c25f816606ea75b482105a5c9526f1cd.
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.191Z, PID: 608] [aspnetcorev2_inprocess.dll] Waiting for initialization
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.198Z, PID: 608] [aspnetcorev2_inprocess.dll] Starting app_offline monitoring in application 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\'
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.204Z, PID: 608] [aspnetcorev2_inprocess.dll] Starting file watcher thread
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.236Z, PID: 608] [aspnetcorev2_inprocess.dll] Starting in-process worker thread
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.237Z, PID: 608] [aspnetcorev2_inprocess.dll] Exception 'remove_all: Access is denied.: "C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\0"' caught at D:\a\_work\1\s\src\Servers\IIS\AspNetCoreModuleV2\InProcessRequestHandler\inprocessapplication.cpp:195
[19.116s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.272Z, PID: 608] [aspnetcorev2_inprocess.dll] Resolving hostfxr parameters for application: 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe' arguments: '.\InProcessWebSite.dll' path: 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\1'
[19.117s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.307Z, PID: 608] [aspnetcorev2_inprocess.dll] Known dotnet.exe location: 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe'
[19.117s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.313Z, PID: 608] [aspnetcorev2_inprocess.dll] Process path 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe' is dotnet, treating application as portable
[19.117s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.316Z, PID: 608] [aspnetcorev2_inprocess.dll] Resolving absolute path to hostfxr.dll from 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe'
[19.117s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.351Z, PID: 608] [aspnetcorev2_inprocess.dll] hostfxr.dll located at 'C:\h\w\B43109B2\p\dotnet-cli\host\fxr\7.0.0-preview.2.22103.2\hostfxr.dll'
[19.117s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.355Z, PID: 608] [aspnetcorev2_inprocess.dll] Converted argument '.\InProcessWebSite.dll' to 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\1\.\InProcessWebSite.dll'
[19.117s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.364Z, PID: 608] [aspnetcorev2_inprocess.dll] Parsed hostfxr options: dotnet location: 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe' hostfxr path: 'C:\h\w\B43109B2\p\dotnet-cli\host\fxr\7.0.0-preview.2.22103.2\hostfxr.dll' arguments:
[19.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.400Z, PID: 608] [aspnetcorev2_inprocess.dll] Argument[0] = 'C:\h\w\B43109B2\p\dotnet-cli\dotnet.exe'
[19.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.421Z, PID: 608] [aspnetcorev2_inprocess.dll] Argument[1] = 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\1\.\InProcessWebSite.dll'
[19.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.442Z, PID: 608] [aspnetcorev2_inprocess.dll] Setting environment variable ASPNETCORE_DETAILEDERRORS=true
[19.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.465Z, PID: 608] [aspnetcorev2_inprocess.dll] Setting environment variable ASPNETCORE_IIS_HTTPAUTH=anonymous;
[19.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.483Z, PID: 608] [aspnetcorev2_inprocess.dll] Setting environment variable ASPNETCORE_IIS_PHYSICAL_PATH=C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\
[19.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.502Z, PID: 608] [aspnetcorev2_inprocess.dll] Loading hostfxr from location C:\h\w\B43109B2\p\dotnet-cli\host\fxr\7.0.0-preview.2.22103.2\hostfxr.dll
[19.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.534Z, PID: 608] [aspnetcorev2_inprocess.dll] Initial Dll directory: '', current directory: 'c:\windows\system32\inetsrv'
[19.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.557Z, PID: 608] [aspnetcorev2_inprocess.dll] Setting dll directory to c:\windows\system32\inetsrv
[19.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.562Z, PID: 608] [aspnetcorev2_inprocess.dll] Setting current directory to C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\
[19.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.856Z, PID: 608] [aspnetcorev2_inprocess.dll] In-process callbacks set
[19.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:58.906Z, PID: 608] [aspnetcorev2_inprocess.dll] Event Log: 'Application 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\' started successfully.'
[19.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] End Event Log Message.
[19.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.440Z, PID: 608] [aspnetcorev2.dll] ASPNET_CORE_GLOBAL_MODULE::OnGlobalStopListening
[19.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.448Z, PID: 608] [aspnetcorev2.dll] Stopping application '/LM/W3SVC/1/ROOT'
[19.118s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.452Z, PID: 608] [aspnetcorev2_inprocess.dll] Stopping file watching.
[19.119s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.457Z, PID: 608] [aspnetcorev2_inprocess.dll] Starting copy on shutdown in filewatcher, creating directory.
[19.119s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.462Z, PID: 608] [aspnetcorev2_inprocess.dll] Copying new shadow copy directory to C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\2.
[19.119s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.532Z, PID: 608] [aspnetcorev2_inprocess.dll] Finished copy on shutdown to C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\ShadowCopy\2. 110 files copied.
[19.119s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.553Z, PID: 608] [aspnetcorev2_inprocess.dll] Stopping file watcher thread
[19.119s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.553Z, PID: 608] [aspnetcorev2_inprocess.dll] Stopping CLR
[19.119s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.554Z, PID: 608] [aspnetcorev2_inprocess.dll] Received file change notification in application 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\'
[19.120s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.583Z, PID: 608] [aspnetcorev2_inprocess.dll] Starting shutdown sequence 0
[19.120s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.584Z, PID: 608] [aspnetcorev2_inprocess.dll] Drained all requests, notifying managed.
[19.120s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.589Z, PID: 608] [aspnetcorev2_inprocess.dll] Waiting for 0 requests to drain
[19.120s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.589Z, PID: 608] [aspnetcorev2_inprocess.dll] Event Log: 'Application 'C:\h\w\B43109B2\t\a11461820fa349049411fc439ec3ba4b\' was recycled after detecting file change in application directory.'
[19.120s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] End Event Log Message.
[19.120s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.621Z, PID: 608] [aspnetcorev2_inprocess.dll] Managed application exited with code 0
[19.120s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.626Z, PID: 608] [aspnetcorev2_inprocess.dll] Clr thread wait ended: clrThreadExited: 1
[19.120s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.634Z, PID: 608] [aspnetcorev2_inprocess.dll] Event Log: 'Application 'MACHINE/WEBROOT/APPHOST/DEFAULT WEB SITE' has shutdown.'
[19.120s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] End Event Log Message.
[19.120s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.637Z, PID: 608] [aspnetcorev2_inprocess.dll] Canceling standard stream pipe reader
[19.120s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:10:59.641Z, PID: 608] [aspnetcorev2_inprocess.dll] Stopping in-process worker thread
[19.120s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [2022-02-07T23:11:00.770Z, PID: 608] [aspnetcorev2.dll] ASPNET_CORE_GLOBAL_MODULE::Terminate
[19.354s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Warning] Failed to delete directory : Access to the path 'InProcessWebSite.dll' is denied.
[19.472s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Warning] Failed to delete directory : Access to the path 'InProcessWebSite.dll' is denied.
[19.582s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Warning] Failed to delete directory : Access to the path 'InProcessWebSite.dll' is denied.
[19.687s] [Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer] [Information] [Time]: Total time taken for this test variation '19.6351558' seconds
```
</details>
## Build
<!--
Provide a link to the build where the test failure occurred.
-->
https://dev.azure.com/dnceng/public/_build/results?buildId=1598027 | non_priority | quarantine shadowcopyignoresitsowndirectorywithrelativepathsegmentwhencopying note this issue template is specifically for failing tests within the dotnet aspnetcore repo failing test s provide the fully qualified name s of the failing tests microsoft aspnetcore server iis functionaltests shadowcopytests shadowcopyignoresitsowndirectorywithrelativepathsegmentwhencopying error message provide the error message associated with the test failure if applicable text assert false failure expected false actual true stacktrace provide the stack trace associated with the test failure if applicable text at microsoft aspnetcore server iis functionaltests shadowcopytests shadowcopyignoresitsowndirectorywithrelativepathsegmentwhencopying in src servers iis iis test iis shadowcopy tests shadowcopytests cs line end of stack trace from previous location logs provide the helix logs associated with the test failure if applicable text starting test shadowcopyignoresitsowndirectorywithrelativepathsegmentwhencopying at deploying servertype iis runtime coreclr arch baseurlhint publish true microsoft windows nt using prepublished application from c h w w e inprocesswebsite portable processing c h w t copying inprocess dll processing c h w t runtimes win lib copying system diagnostics eventlog dll copying system diagnostics eventlog messages dll processing c h w t runtimes win lib processing c h w t runtimes win processing c h w t runtimes processing c h w t wwwroot copying static txt processing c h w t copying inprocess dll processing c h w t copying inprocess dll processing c h w t copying inprocesswebsite deps json copying inprocesswebsite dll copying inprocesswebsite exe copying inprocesswebsite pdb copying inprocesswebsite runtimeconfig json copying microsoft aspnetcore authentication abstractions dll copying microsoft aspnetcore authentication abstractions pdb copying microsoft aspnetcore authentication abstractions xml copying microsoft aspnetcore authentication core dll copying microsoft aspnetcore authentication core pdb copying microsoft aspnetcore authentication core xml copying microsoft aspnetcore connections abstractions dll copying microsoft aspnetcore connections abstractions pdb copying microsoft aspnetcore connections abstractions xml copying microsoft aspnetcore hosting abstractions dll copying microsoft aspnetcore hosting abstractions pdb copying microsoft aspnetcore hosting abstractions xml copying microsoft aspnetcore hosting dll copying microsoft aspnetcore hosting pdb copying microsoft aspnetcore hosting server abstractions dll copying microsoft aspnetcore hosting server abstractions pdb copying microsoft aspnetcore hosting server abstractions xml copying microsoft aspnetcore hosting xml copying microsoft aspnetcore http abstractions dll copying microsoft aspnetcore http abstractions pdb copying microsoft aspnetcore http abstractions xml copying microsoft aspnetcore http dll copying microsoft aspnetcore http extensions dll copying microsoft aspnetcore http extensions pdb copying microsoft aspnetcore http extensions xml copying microsoft aspnetcore http features dll copying microsoft aspnetcore http features pdb copying microsoft aspnetcore http features xml copying microsoft aspnetcore http pdb copying microsoft aspnetcore http xml copying microsoft aspnetcore httpoverrides dll copying microsoft aspnetcore httpoverrides pdb copying microsoft aspnetcore httpoverrides xml copying microsoft aspnetcore httpspolicy dll copying microsoft aspnetcore httpspolicy pdb copying microsoft aspnetcore httpspolicy xml copying microsoft aspnetcore responsecompression dll copying microsoft aspnetcore responsecompression pdb copying microsoft aspnetcore responsecompression xml copying microsoft aspnetcore server iis dll copying microsoft aspnetcore server iis pdb copying microsoft aspnetcore server iis xml copying microsoft aspnetcore server iisintegration dll copying microsoft aspnetcore server iisintegration pdb copying microsoft aspnetcore server iisintegration xml copying microsoft aspnetcore server kestrel core dll copying microsoft aspnetcore server kestrel core pdb copying microsoft aspnetcore server kestrel core xml copying microsoft aspnetcore server kestrel dll copying microsoft aspnetcore server kestrel pdb copying microsoft aspnetcore server kestrel transport quic dll copying microsoft aspnetcore server kestrel transport quic pdb copying microsoft aspnetcore server kestrel transport quic xml copying microsoft aspnetcore server kestrel transport sockets dll copying microsoft aspnetcore server kestrel transport sockets pdb copying microsoft aspnetcore server kestrel transport sockets xml copying microsoft aspnetcore server kestrel xml copying microsoft aspnetcore webutilities dll copying microsoft aspnetcore webutilities pdb copying microsoft aspnetcore webutilities xml copying microsoft extensions configuration abstractions dll copying microsoft extensions configuration binder dll copying microsoft extensions configuration commandline dll copying microsoft extensions configuration dll copying microsoft extensions configuration environmentvariables dll copying microsoft extensions configuration fileextensions dll copying microsoft extensions configuration json dll copying microsoft extensions configuration usersecrets dll copying microsoft extensions dependencyinjection abstractions dll copying microsoft extensions dependencyinjection dll copying microsoft extensions features dll copying microsoft extensions features pdb copying microsoft extensions features xml copying microsoft extensions fileproviders abstractions dll copying microsoft extensions fileproviders composite dll copying microsoft extensions fileproviders physical dll copying microsoft extensions filesystemglobbing dll copying microsoft extensions hosting abstractions dll copying microsoft extensions hosting dll copying microsoft extensions logging abstractions dll copying microsoft extensions logging configuration dll copying microsoft extensions logging console dll copying microsoft extensions logging debug dll copying microsoft extensions logging dll copying microsoft extensions logging eventlog dll copying microsoft extensions logging eventsource dll copying microsoft extensions objectpool dll copying microsoft extensions objectpool pdb copying microsoft extensions objectpool xml copying microsoft extensions options configurationextensions dll copying microsoft extensions options dll copying microsoft extensions primitives dll copying microsoft net http headers dll copying microsoft net http headers pdb copying microsoft net http headers xml copying system diagnostics eventlog dll copying system io pipelines dll copying web config copying xunit assert dll applicationhost config path c h w t status running site has started successfully finished iis application directory setup method get requesturi version content headers statuscode reasonphrase ok version content system net http httpconnectionresponsecontent headers transfer encoding chunked server microsoft iis date mon feb gmt method get requesturi version content headers statuscode reasonphrase ok version content system net http httpconnectionresponsecontent headers transfer encoding chunked server microsoft iis date mon feb gmt hello world test threw an exception xunit sdk falseexception assert false failure expected false actual true at xunit assert false nullable condition string usermessage in c dev xunit xunit src xunit assert asserts booleanasserts cs line at xunit assert false boolean condition in c dev xunit xunit src xunit assert asserts booleanasserts cs line at microsoft aspnetcore server iis functionaltests shadowcopytests shadowcopyignoresitsowndirectorywithrelativepathsegmentwhencopying in src servers iis iis test iis shadowcopy tests shadowcopytests cs line at xunit sdk testinvoker c b d movenext in c dev xunit xunit src xunit execution sdk frameworks runners testinvoker cs line end of stack trace from previous location at xunit sdk executiontimer aggregateasync func asyncaction in c dev xunit xunit src xunit execution sdk frameworks executiontimer cs line at xunit sdk exceptionaggregator runasync func code in c dev xunit xunit src xunit core sdk exceptionaggregator cs line stopping site state stopped stopping pool state stopping site has stopped successfully host process shutting down initializing logs for c h w w e ancm dll process id file version description iis asp net core module commit copying to shadow copy directory c h w t shadowcopy finished copying files to shadow copy directory c h w t shadowcopy resolving hostfxr parameters for application c h w p dotnet cli dotnet exe arguments inprocesswebsite dll path c h w t shadowcopy known dotnet exe location process path c h w p dotnet cli dotnet exe is dotnet treating application as portable resolving absolute path to dotnet exe from c h w p dotnet cli dotnet exe found dotnet exe at c h w p dotnet cli dotnet exe resolving absolute path to hostfxr dll from c h w p dotnet cli dotnet exe hostfxr dll located at c h w p dotnet cli host fxr preview hostfxr dll converted argument inprocesswebsite dll to c h w t shadowcopy inprocesswebsite dll parsed hostfxr options dotnet location c h w p dotnet cli dotnet exe hostfxr path c h w p dotnet cli host fxr preview hostfxr dll arguments argument c h w p dotnet cli dotnet exe argument c h w t shadowcopy inprocesswebsite dll loading hostfxr from location c h w p dotnet cli host fxr preview hostfxr dll canceling standard stream pipe reader loading request handler c h w t shadowcopy inprocess dll creating handler application initializing logs for c h w t shadowcopy inprocess dll process id file version description iis asp net core module request handler commit waiting for initialization starting app offline monitoring in application c h w t starting file watcher thread starting in process worker thread resolving hostfxr parameters for application c h w p dotnet cli dotnet exe arguments inprocesswebsite dll path c h w t shadowcopy known dotnet exe location c h w p dotnet cli dotnet exe process path c h w p dotnet cli dotnet exe is dotnet treating application as portable resolving absolute path to hostfxr dll from c h w p dotnet cli dotnet exe hostfxr dll located at c h w p dotnet cli host fxr preview hostfxr dll converted argument inprocesswebsite dll to c h w t shadowcopy inprocesswebsite dll parsed hostfxr options dotnet location c h w p dotnet cli dotnet exe hostfxr path c h w p dotnet cli host fxr preview hostfxr dll arguments argument c h w p dotnet cli dotnet exe argument c h w t shadowcopy inprocesswebsite dll setting environment variable aspnetcore detailederrors true setting environment variable aspnetcore iis httpauth anonymous setting environment variable aspnetcore iis physical path c h w t loading hostfxr from location c h w p dotnet cli host fxr preview hostfxr dll initial dll directory current directory c windows inetsrv setting dll directory to c windows inetsrv setting current directory to c h w t in process callbacks set event log application c h w t started successfully end event log message detected dll change resetting timer callback which will eventually trigger shutdown aspnet core global module onglobalconfigurationchange machine webroot apphost default web site received file change notification in application c h w t stopping application lm root event log application c h w t was recycled after detecting file change in application directory end event log message stopping file watching starting copy on shutdown in filewatcher creating directory copying new shadow copy directory to c h w t shadowcopy finished copy on shutdown to c h w t shadowcopy files copied stopping clr drained all requests notifying managed starting shutdown sequence waiting for requests to drain managed application exited with code clr thread wait ended clrthreadexited event log application machine webroot apphost default web site has shutdown end event log message canceling standard stream pipe reader stopping in process worker thread aspnetcore inprocess recycle process on demand aspnet core global module onglobalstoplistening initializing logs for c h w w e ancm dll process id file version description iis asp net core module commit copying to shadow copy directory c h w t shadowcopy finished copying files to shadow copy directory c h w t shadowcopy resolving hostfxr parameters for application c h w p dotnet cli dotnet exe arguments inprocesswebsite dll path c h w t shadowcopy known dotnet exe location process path c h w p dotnet cli dotnet exe is dotnet treating application as portable resolving absolute path to dotnet exe from c h w p dotnet cli dotnet exe found dotnet exe at c h w p dotnet cli dotnet exe resolving absolute path to hostfxr dll from c h w p dotnet cli dotnet exe hostfxr dll located at c h w p dotnet cli host fxr preview hostfxr dll converted argument inprocesswebsite dll to c h w t shadowcopy inprocesswebsite dll parsed hostfxr options dotnet location c h w p dotnet cli dotnet exe hostfxr path c h w p dotnet cli host fxr preview hostfxr dll arguments argument c h w p dotnet cli dotnet exe argument c h w t shadowcopy inprocesswebsite dll loading hostfxr from location c h w p dotnet cli host fxr preview hostfxr dll canceling standard stream pipe reader loading request handler c h w t shadowcopy inprocess dll creating handler application initializing logs for c h w t shadowcopy inprocess dll process id file version description iis asp net core module request handler commit waiting for initialization starting app offline monitoring in application c h w t starting file watcher thread starting in process worker thread exception remove all access is denied c h w t shadowcopy caught at d a work s src servers iis inprocessrequesthandler inprocessapplication cpp resolving hostfxr parameters for application c h w p dotnet cli dotnet exe arguments inprocesswebsite dll path c h w t shadowcopy known dotnet exe location c h w p dotnet cli dotnet exe process path c h w p dotnet cli dotnet exe is dotnet treating application as portable resolving absolute path to hostfxr dll from c h w p dotnet cli dotnet exe hostfxr dll located at c h w p dotnet cli host fxr preview hostfxr dll converted argument inprocesswebsite dll to c h w t shadowcopy inprocesswebsite dll parsed hostfxr options dotnet location c h w p dotnet cli dotnet exe hostfxr path c h w p dotnet cli host fxr preview hostfxr dll arguments argument c h w p dotnet cli dotnet exe argument c h w t shadowcopy inprocesswebsite dll setting environment variable aspnetcore detailederrors true setting environment variable aspnetcore iis httpauth anonymous setting environment variable aspnetcore iis physical path c h w t loading hostfxr from location c h w p dotnet cli host fxr preview hostfxr dll initial dll directory current directory c windows inetsrv setting dll directory to c windows inetsrv setting current directory to c h w t in process callbacks set event log application c h w t started successfully end event log message aspnet core global module onglobalstoplistening stopping application lm root stopping file watching starting copy on shutdown in filewatcher creating directory copying new shadow copy directory to c h w t shadowcopy finished copy on shutdown to c h w t shadowcopy files copied stopping file watcher thread stopping clr received file change notification in application c h w t starting shutdown sequence drained all requests notifying managed waiting for requests to drain event log application c h w t was recycled after detecting file change in application directory end event log message managed application exited with code clr thread wait ended clrthreadexited event log application machine webroot apphost default web site has shutdown end event log message canceling standard stream pipe reader stopping in process worker thread aspnet core global module terminate failed to delete directory access to the path inprocesswebsite dll is denied failed to delete directory access to the path inprocesswebsite dll is denied failed to delete directory access to the path inprocesswebsite dll is denied total time taken for this test variation seconds build provide a link to the build where the test failure occurred | 0 |
26,107 | 6,748,362,020 | IssuesEvent | 2017-10-22 05:31:00 | joomla/joomla-cms | https://api.github.com/repos/joomla/joomla-cms | closed | Possible ACL for creating new menu item | No Code Attached Yet | ### Steps for the feature
Go to menu-items and create new one
There you get all possible options of menu items
If you ask a customer with no knowledge to add a menu item they get allot of options and do not know what to do.
90% of the time my customer only needs 1/2 or 3 options there.
To reduce the options i can disable a fully component and it disappears.
If i want to use the component but i do not want my customer to create menu items with lets say Tags or contacts i can't disable that option.
So new feature could be:
New ACL option to enable disable the possibility to show component in the new menu-item selection.
It would even better like to have the possibility to not show anything but just select what you want, even choosing the views. Some components have already 20 different options.
But i think this would be more difficult.
| 1.0 | Possible ACL for creating new menu item - ### Steps for the feature
Go to menu-items and create new one
There you get all possible options of menu items
If you ask a customer with no knowledge to add a menu item they get allot of options and do not know what to do.
90% of the time my customer only needs 1/2 or 3 options there.
To reduce the options i can disable a fully component and it disappears.
If i want to use the component but i do not want my customer to create menu items with lets say Tags or contacts i can't disable that option.
So new feature could be:
New ACL option to enable disable the possibility to show component in the new menu-item selection.
It would even better like to have the possibility to not show anything but just select what you want, even choosing the views. Some components have already 20 different options.
But i think this would be more difficult.
| non_priority | possible acl for creating new menu item steps for the feature go to menu items and create new one there you get all possible options of menu items if you ask a customer with no knowledge to add a menu item they get allot of options and do not know what to do of the time my customer only needs or options there to reduce the options i can disable a fully component and it disappears if i want to use the component but i do not want my customer to create menu items with lets say tags or contacts i can t disable that option so new feature could be new acl option to enable disable the possibility to show component in the new menu item selection it would even better like to have the possibility to not show anything but just select what you want even choosing the views some components have already different options but i think this would be more difficult | 0 |
2,015 | 4,837,107,782 | IssuesEvent | 2016-11-08 21:36:05 | cliffparnitzky/FormDependentMandatoryField | https://api.github.com/repos/cliffparnitzky/FormDependentMandatoryField | closed | Wrong error message for "is_empty" condition | Defect Improvement ⚙ - Processed | Hi Cliff,
many thanks for your work, saved me from braindeath ;-)
I would suggest to add another condition labeled "empty" or "is empty" to the dependent fields list. Error messages should be adapted accordingly (in German like "keine Werte in Feld xyz"). I my understanding, currently you could build it with "!=" as Condition and "*" as value which results in a wrong error message in the form.
Andreas | 1.0 | Wrong error message for "is_empty" condition - Hi Cliff,
many thanks for your work, saved me from braindeath ;-)
I would suggest to add another condition labeled "empty" or "is empty" to the dependent fields list. Error messages should be adapted accordingly (in German like "keine Werte in Feld xyz"). I my understanding, currently you could build it with "!=" as Condition and "*" as value which results in a wrong error message in the form.
Andreas | non_priority | wrong error message for is empty condition hi cliff many thanks for your work saved me from braindeath i would suggest to add another condition labeled empty or is empty to the dependent fields list error messages should be adapted accordingly in german like keine werte in feld xyz i my understanding currently you could build it with as condition and as value which results in a wrong error message in the form andreas | 0 |
300,098 | 22,641,203,747 | IssuesEvent | 2022-07-01 02:22:23 | fga-eps-mds/2022-1-PUMA-Doc | https://api.github.com/repos/fga-eps-mds/2022-1-PUMA-Doc | reopened | Levantamento Quadro de Disponibilidade | documentation good first issue organização | ### Descrição
Issue destinada ao Levantamento do Quadro de Disponibilidade dos integrantes do grupo.
### Tarefas
- [x] Todos os integrantes preencherem sua Disponibilidade para reunião/ trabalho no projeto.
### Critérios de Aceitação
- [x] Levantar o Quadro de Disponibilidade Geral;
- [x] Levantar o Quadro de Disponibilidade dos EPS;
- [x] Levantar o Quadro de Disponibilidade dos MDS. | 1.0 | Levantamento Quadro de Disponibilidade - ### Descrição
Issue destinada ao Levantamento do Quadro de Disponibilidade dos integrantes do grupo.
### Tarefas
- [x] Todos os integrantes preencherem sua Disponibilidade para reunião/ trabalho no projeto.
### Critérios de Aceitação
- [x] Levantar o Quadro de Disponibilidade Geral;
- [x] Levantar o Quadro de Disponibilidade dos EPS;
- [x] Levantar o Quadro de Disponibilidade dos MDS. | non_priority | levantamento quadro de disponibilidade descrição issue destinada ao levantamento do quadro de disponibilidade dos integrantes do grupo tarefas todos os integrantes preencherem sua disponibilidade para reunião trabalho no projeto critérios de aceitação levantar o quadro de disponibilidade geral levantar o quadro de disponibilidade dos eps levantar o quadro de disponibilidade dos mds | 0 |
48,063 | 10,199,104,946 | IssuesEvent | 2019-08-13 07:39:24 | postmanlabs/postman-app-support | https://api.github.com/repos/postmanlabs/postman-app-support | closed | Bug: Node.js native code snippet for form-data requests doesn't actually work | bug code-generator product/desktop-app | When I copy and paste a code snippet that is generated by postman for form-data requests for Node.js -> Native, I get errors when running. I would appreciate an update as I would like to test the postman requests natively as well. | 1.0 | Bug: Node.js native code snippet for form-data requests doesn't actually work - When I copy and paste a code snippet that is generated by postman for form-data requests for Node.js -> Native, I get errors when running. I would appreciate an update as I would like to test the postman requests natively as well. | non_priority | bug node js native code snippet for form data requests doesn t actually work when i copy and paste a code snippet that is generated by postman for form data requests for node js native i get errors when running i would appreciate an update as i would like to test the postman requests natively as well | 0 |
111,128 | 9,499,395,139 | IssuesEvent | 2019-04-24 06:15:49 | humera987/FXLabs-Test-Automation | https://api.github.com/repos/humera987/FXLabs-Test-Automation | opened | Vulnerability [SLA] : GET:/api/v1/runs/{jobId}/testSuite/test-suite-responses/{name} | SanityTest | Project : SanityTest
Template : ApiV1RunsJobidTestsuiteTestSuiteResponsesNameGetQueryParamPageSla
Run Id : <html><a href=https://18.144.40.113/#/app/projects/8a8080b36a49d299016a4de39a652aa2/jobs/8a8080b36a49d299016a4de39fc32bdb/runs/8a8080b36a49d299016a4dfc4d174d85>8a8080b36a49d299016a4dfc4d174d85</a></html>
Job : Default
Env : Default
Category : SLA
Tags : [SLA]
Severity : Major
Region : US_WEST_2
Result : fail
Status Code : 404
Headers : {X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Set-Cookie=[SESSION=MGExMjdkZGMtZTM4Mi00NzQ4LTk5M2EtYTFmZDczZGNmMGYy; Path=/; HttpOnly], Content-Type=[application/json;charset=UTF-8], Transfer-Encoding=[chunked], Date=[Wed, 24 Apr 2019 06:15:45 GMT]}
Endpoint : http://13.56.210.25/api/v1/api/v1/runs/Technology Administrator/testSuite/test-suite-responses/dSEdNwiy?page=1001&pageSize=1001
Request :
Response :
{
"timestamp" : "2019-04-24T06:15:45.555+0000",
"status" : 404,
"error" : "Not Found",
"message" : "No message available",
"path" : "/api/v1/api/v1/runs/Technology%20Administrator/testSuite/test-suite-responses/dSEdNwiy"
}
Logs :
com.fxlabs.fxt.bot.assertions.AssertionLogger@5b20aa98
--- FX Bot --- | 1.0 | Vulnerability [SLA] : GET:/api/v1/runs/{jobId}/testSuite/test-suite-responses/{name} - Project : SanityTest
Template : ApiV1RunsJobidTestsuiteTestSuiteResponsesNameGetQueryParamPageSla
Run Id : <html><a href=https://18.144.40.113/#/app/projects/8a8080b36a49d299016a4de39a652aa2/jobs/8a8080b36a49d299016a4de39fc32bdb/runs/8a8080b36a49d299016a4dfc4d174d85>8a8080b36a49d299016a4dfc4d174d85</a></html>
Job : Default
Env : Default
Category : SLA
Tags : [SLA]
Severity : Major
Region : US_WEST_2
Result : fail
Status Code : 404
Headers : {X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Set-Cookie=[SESSION=MGExMjdkZGMtZTM4Mi00NzQ4LTk5M2EtYTFmZDczZGNmMGYy; Path=/; HttpOnly], Content-Type=[application/json;charset=UTF-8], Transfer-Encoding=[chunked], Date=[Wed, 24 Apr 2019 06:15:45 GMT]}
Endpoint : http://13.56.210.25/api/v1/api/v1/runs/Technology Administrator/testSuite/test-suite-responses/dSEdNwiy?page=1001&pageSize=1001
Request :
Response :
{
"timestamp" : "2019-04-24T06:15:45.555+0000",
"status" : 404,
"error" : "Not Found",
"message" : "No message available",
"path" : "/api/v1/api/v1/runs/Technology%20Administrator/testSuite/test-suite-responses/dSEdNwiy"
}
Logs :
com.fxlabs.fxt.bot.assertions.AssertionLogger@5b20aa98
--- FX Bot --- | non_priority | vulnerability get api runs jobid testsuite test suite responses name project sanitytest template run id a href job default env default category sla tags severity major region us west result fail status code headers x content type options x xss protection cache control pragma expires x frame options set cookie content type transfer encoding date endpoint administrator testsuite test suite responses dsednwiy page pagesize request response timestamp status error not found message no message available path api api runs technology testsuite test suite responses dsednwiy logs com fxlabs fxt bot assertions assertionlogger fx bot | 0 |
71,310 | 18,676,707,729 | IssuesEvent | 2021-10-31 17:29:32 | quicklisp/quicklisp-projects | https://api.github.com/repos/quicklisp/quicklisp-projects | closed | Please add cl-apertium-stream-parser | canbuild | cl-apertium-stream-parser is a parser for Apertium stream, which is a format used in Apertium rule-based machine translation. The project is hosted at https://github.com/veer66/cl-apertium-stream-parser. | 1.0 | Please add cl-apertium-stream-parser - cl-apertium-stream-parser is a parser for Apertium stream, which is a format used in Apertium rule-based machine translation. The project is hosted at https://github.com/veer66/cl-apertium-stream-parser. | non_priority | please add cl apertium stream parser cl apertium stream parser is a parser for apertium stream which is a format used in apertium rule based machine translation the project is hosted at | 0 |
162,998 | 25,732,043,370 | IssuesEvent | 2022-12-07 21:07:08 | atlosdotorg/atlos | https://api.github.com/repos/atlosdotorg/atlos | closed | Convert "Temporary Connection Loss" banner into a normal notification | design change | To make it a bit less aggressive :) | 1.0 | Convert "Temporary Connection Loss" banner into a normal notification - To make it a bit less aggressive :) | non_priority | convert temporary connection loss banner into a normal notification to make it a bit less aggressive | 0 |
130,699 | 18,170,254,993 | IssuesEvent | 2021-09-27 19:06:48 | snowdensb/job-dsl-plugin | https://api.github.com/repos/snowdensb/job-dsl-plugin | opened | CVE-2020-2162 (Medium) detected in jenkins-core-2.176.jar | security vulnerability | ## CVE-2020-2162 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jenkins-core-2.176.jar</b></p></summary>
<p>Jenkins core code and view files to render HTML.</p>
<p>Library home page: <a href="https://jenkins.io/jenkins-parent/jenkins-core/">https://jenkins.io/jenkins-parent/jenkins-core/</a></p>
<p>Path to dependency file: job-dsl-plugin/job-dsl-plugin/build.gradle</p>
<p>Path to vulnerable library: caches/modules-2/files-2.1/org.jenkins-ci.main/jenkins-core/2.176/95ee06bed42207774c63dc8ead89f79f2a9daee9/jenkins-core-2.176.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jenkins-ci.main/jenkins-core/2.176/95ee06bed42207774c63dc8ead89f79f2a9daee9/jenkins-core-2.176.jar</p>
<p>
Dependency Hierarchy:
- :x: **jenkins-core-2.176.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/snowdensb/job-dsl-plugin/commit/2e8946fc25b6060b5637631b8813fe86b6da687a">2e8946fc25b6060b5637631b8813fe86b6da687a</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>
Jenkins 2.227 and earlier, LTS 2.204.5 and earlier does not set Content-Security-Policy headers for files uploaded as file parameters to a build, resulting in a stored XSS vulnerability.
<p>Publish Date: 2020-03-25
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-2162>CVE-2020-2162</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.4</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- 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://jenkins.io/security/advisory/2020-03-25/#SECURITY-1793">https://jenkins.io/security/advisory/2020-03-25/#SECURITY-1793</a></p>
<p>Release Date: 2020-03-25</p>
<p>Fix Resolution: jenkins_2.228,LTS_2.204.6</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.jenkins-ci.main","packageName":"jenkins-core","packageVersion":"2.176","packageFilePaths":["/job-dsl-plugin/build.gradle"],"isTransitiveDependency":false,"dependencyTree":"org.jenkins-ci.main:jenkins-core:2.176","isMinimumFixVersionAvailable":true,"minimumFixVersion":"jenkins_2.228,LTS_2.204.6"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-2162","vulnerabilityDetails":"Jenkins 2.227 and earlier, LTS 2.204.5 and earlier does not set Content-Security-Policy headers for files uploaded as file parameters to a build, resulting in a stored XSS vulnerability.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-2162","cvss3Severity":"medium","cvss3Score":"5.4","cvss3Metrics":{"A":"None","AC":"Low","PR":"Low","S":"Changed","C":"Low","UI":"Required","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | True | CVE-2020-2162 (Medium) detected in jenkins-core-2.176.jar - ## CVE-2020-2162 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jenkins-core-2.176.jar</b></p></summary>
<p>Jenkins core code and view files to render HTML.</p>
<p>Library home page: <a href="https://jenkins.io/jenkins-parent/jenkins-core/">https://jenkins.io/jenkins-parent/jenkins-core/</a></p>
<p>Path to dependency file: job-dsl-plugin/job-dsl-plugin/build.gradle</p>
<p>Path to vulnerable library: caches/modules-2/files-2.1/org.jenkins-ci.main/jenkins-core/2.176/95ee06bed42207774c63dc8ead89f79f2a9daee9/jenkins-core-2.176.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jenkins-ci.main/jenkins-core/2.176/95ee06bed42207774c63dc8ead89f79f2a9daee9/jenkins-core-2.176.jar</p>
<p>
Dependency Hierarchy:
- :x: **jenkins-core-2.176.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/snowdensb/job-dsl-plugin/commit/2e8946fc25b6060b5637631b8813fe86b6da687a">2e8946fc25b6060b5637631b8813fe86b6da687a</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>
Jenkins 2.227 and earlier, LTS 2.204.5 and earlier does not set Content-Security-Policy headers for files uploaded as file parameters to a build, resulting in a stored XSS vulnerability.
<p>Publish Date: 2020-03-25
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-2162>CVE-2020-2162</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.4</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- 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://jenkins.io/security/advisory/2020-03-25/#SECURITY-1793">https://jenkins.io/security/advisory/2020-03-25/#SECURITY-1793</a></p>
<p>Release Date: 2020-03-25</p>
<p>Fix Resolution: jenkins_2.228,LTS_2.204.6</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.jenkins-ci.main","packageName":"jenkins-core","packageVersion":"2.176","packageFilePaths":["/job-dsl-plugin/build.gradle"],"isTransitiveDependency":false,"dependencyTree":"org.jenkins-ci.main:jenkins-core:2.176","isMinimumFixVersionAvailable":true,"minimumFixVersion":"jenkins_2.228,LTS_2.204.6"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-2162","vulnerabilityDetails":"Jenkins 2.227 and earlier, LTS 2.204.5 and earlier does not set Content-Security-Policy headers for files uploaded as file parameters to a build, resulting in a stored XSS vulnerability.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-2162","cvss3Severity":"medium","cvss3Score":"5.4","cvss3Metrics":{"A":"None","AC":"Low","PR":"Low","S":"Changed","C":"Low","UI":"Required","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | non_priority | cve medium detected in jenkins core jar cve medium severity vulnerability vulnerable library jenkins core jar jenkins core code and view files to render html library home page a href path to dependency file job dsl plugin job dsl plugin build gradle path to vulnerable library caches modules files org jenkins ci main jenkins core jenkins core jar home wss scanner gradle caches modules files org jenkins ci main jenkins core jenkins core jar dependency hierarchy x jenkins core jar vulnerable library found in head commit a href found in base branch master vulnerability details jenkins and earlier lts and earlier does not set content security policy headers for files uploaded as file parameters to a build resulting in a stored xss vulnerability publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low 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 jenkins lts rescue worker helmet automatic remediation is available for this issue isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree org jenkins ci main jenkins core isminimumfixversionavailable true minimumfixversion jenkins lts basebranches vulnerabilityidentifier cve vulnerabilitydetails jenkins and earlier lts and earlier does not set content security policy headers for files uploaded as file parameters to a build resulting in a stored xss vulnerability vulnerabilityurl | 0 |
51,206 | 12,686,693,303 | IssuesEvent | 2020-06-20 12:29:55 | junit-pioneer/junit-pioneer | https://api.github.com/repos/junit-pioneer/junit-pioneer | closed | Update JUnit 5 to 5.5 | component: Jupiter status: in-progress theme: build type: enhancement | In order to fix #10, we need the [`InvocationInterceptor`](https://junit.org/junit5/docs/current/api/org.junit.jupiter.api/org/junit/jupiter/api/extension/InvocationInterceptor.html) extension point, which was added in 5.5.
I'll open a PR, so we can see whether there are any reasons not to update. | 1.0 | Update JUnit 5 to 5.5 - In order to fix #10, we need the [`InvocationInterceptor`](https://junit.org/junit5/docs/current/api/org.junit.jupiter.api/org/junit/jupiter/api/extension/InvocationInterceptor.html) extension point, which was added in 5.5.
I'll open a PR, so we can see whether there are any reasons not to update. | non_priority | update junit to in order to fix we need the extension point which was added in i ll open a pr so we can see whether there are any reasons not to update | 0 |
340,736 | 24,668,635,804 | IssuesEvent | 2022-10-18 12:16:52 | mantidproject/mantid | https://api.github.com/repos/mantidproject/mantid | opened | dev-docs pages not removed on site update | Documentation ISIS Team: Core | Found here: https://github.com/mantidproject/mantid/issues/34357#issuecomment-1248311915
**Describe the bug**
A dev docs file was renamed. The new page exists on the dev docs website, but so does the old.
Old https://developer.mantidproject.org/Testing/SANSGUI/SANSGUITests.html
New https://developer.mantidproject.org/Testing/SANSGUI/ISISSANSGUITests.html
**Expected behavior**
If a file is removed (or renamed) from the dev docs (or the user docs), the old page is removed from the website.
A change is needed here: https://github.com/mantidproject/mantid/blob/main/buildconfig/Jenkins/Conda/build-and-publish-devsite.sh
Possibly do not use the old clone of the website.
**Screenshots**


| 1.0 | dev-docs pages not removed on site update - Found here: https://github.com/mantidproject/mantid/issues/34357#issuecomment-1248311915
**Describe the bug**
A dev docs file was renamed. The new page exists on the dev docs website, but so does the old.
Old https://developer.mantidproject.org/Testing/SANSGUI/SANSGUITests.html
New https://developer.mantidproject.org/Testing/SANSGUI/ISISSANSGUITests.html
**Expected behavior**
If a file is removed (or renamed) from the dev docs (or the user docs), the old page is removed from the website.
A change is needed here: https://github.com/mantidproject/mantid/blob/main/buildconfig/Jenkins/Conda/build-and-publish-devsite.sh
Possibly do not use the old clone of the website.
**Screenshots**


| non_priority | dev docs pages not removed on site update found here describe the bug a dev docs file was renamed the new page exists on the dev docs website but so does the old old new expected behavior if a file is removed or renamed from the dev docs or the user docs the old page is removed from the website a change is needed here possibly do not use the old clone of the website screenshots | 0 |
388,820 | 26,783,218,188 | IssuesEvent | 2023-01-31 23:19:58 | 24seconds/orka | https://api.github.com/repos/24seconds/orka | closed | Introduce components to storybook | documentation enhancement | ## Description
Storybook seems good tool to share component behavior to coworker. It would be nice to integrate this in orka
- [x] introduce CI/CD using chromatic
- [x] write stories
- [x] #8
- [x] #10
- [x] #16
- [x] #18
- [x] PeerActivity page
| 1.0 | Introduce components to storybook - ## Description
Storybook seems good tool to share component behavior to coworker. It would be nice to integrate this in orka
- [x] introduce CI/CD using chromatic
- [x] write stories
- [x] #8
- [x] #10
- [x] #16
- [x] #18
- [x] PeerActivity page
| non_priority | introduce components to storybook description storybook seems good tool to share component behavior to coworker it would be nice to integrate this in orka introduce ci cd using chromatic write stories peeractivity page | 0 |
246,699 | 20,909,481,617 | IssuesEvent | 2022-03-24 07:50:38 | olbo98/cv-pipeline | https://api.github.com/repos/olbo98/cv-pipeline | closed | Write test for model.py | unit tests | - [x] get_circle_coords()
- [x] get_rect_coords()
- [x] add_circle_coords()
- [x] add_rect_coords()
- [x] delete_annotations()
- [x] preprocess_image() | 1.0 | Write test for model.py - - [x] get_circle_coords()
- [x] get_rect_coords()
- [x] add_circle_coords()
- [x] add_rect_coords()
- [x] delete_annotations()
- [x] preprocess_image() | non_priority | write test for model py get circle coords get rect coords add circle coords add rect coords delete annotations preprocess image | 0 |
255,466 | 21,926,733,661 | IssuesEvent | 2022-05-23 05:32:23 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | opened | roachtest: network/sanity/nodes=4 failed | C-test-failure O-robot O-roachtest release-blocker branch-release-22.1.0 | roachtest.network/sanity/nodes=4 [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=5238665&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=5238665&tab=artifacts#/network/sanity/nodes=4) on release-22.1.0 @ [3abc7eeade10df4b59b0fb24236992f95bf46d9b](https://github.com/cockroachdb/cockroach/commits/3abc7eeade10df4b59b0fb24236992f95bf46d9b):
```
The test failed on branch=release-22.1.0, cloud=gce:
test artifacts and logs in: /artifacts/network/sanity/nodes=4/run_1
network.go:101,monitor.go:105,errgroup.go:57: node 1 unexpectedly affected by latency: select 1 took 0.31s
monitor.go:127,network.go:108,network.go:517,test_runner.go:875: monitor failure: monitor task failed: t.Fatal() was called
(1) attached stack trace
-- stack trace:
| main.(*monitorImpl).WaitE
| main/pkg/cmd/roachtest/monitor.go:115
| main.(*monitorImpl).Wait
| main/pkg/cmd/roachtest/monitor.go:123
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.runNetworkSanity
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/network.go:108
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.registerNetwork.func1
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/network.go:517
| main.(*testRunner).runTest.func2
| main/pkg/cmd/roachtest/test_runner.go:875
Wraps: (2) monitor failure
Wraps: (3) attached stack trace
-- stack trace:
| main.(*monitorImpl).wait.func2
| main/pkg/cmd/roachtest/monitor.go:171
Wraps: (4) monitor task failed
Wraps: (5) attached stack trace
-- stack trace:
| main.init
| main/pkg/cmd/roachtest/monitor.go:80
| runtime.doInit
| GOROOT/src/runtime/proc.go:6498
| runtime.main
| GOROOT/src/runtime/proc.go:238
| runtime.goexit
| GOROOT/src/runtime/asm_amd64.s:1581
Wraps: (6) t.Fatal() was called
Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *withstack.withStack (4) *errutil.withPrefix (5) *withstack.withStack (6) *errutil.leafError
```
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/kv-triage
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*network/sanity/nodes=4.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| 2.0 | roachtest: network/sanity/nodes=4 failed - roachtest.network/sanity/nodes=4 [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=5238665&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=5238665&tab=artifacts#/network/sanity/nodes=4) on release-22.1.0 @ [3abc7eeade10df4b59b0fb24236992f95bf46d9b](https://github.com/cockroachdb/cockroach/commits/3abc7eeade10df4b59b0fb24236992f95bf46d9b):
```
The test failed on branch=release-22.1.0, cloud=gce:
test artifacts and logs in: /artifacts/network/sanity/nodes=4/run_1
network.go:101,monitor.go:105,errgroup.go:57: node 1 unexpectedly affected by latency: select 1 took 0.31s
monitor.go:127,network.go:108,network.go:517,test_runner.go:875: monitor failure: monitor task failed: t.Fatal() was called
(1) attached stack trace
-- stack trace:
| main.(*monitorImpl).WaitE
| main/pkg/cmd/roachtest/monitor.go:115
| main.(*monitorImpl).Wait
| main/pkg/cmd/roachtest/monitor.go:123
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.runNetworkSanity
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/network.go:108
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.registerNetwork.func1
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/network.go:517
| main.(*testRunner).runTest.func2
| main/pkg/cmd/roachtest/test_runner.go:875
Wraps: (2) monitor failure
Wraps: (3) attached stack trace
-- stack trace:
| main.(*monitorImpl).wait.func2
| main/pkg/cmd/roachtest/monitor.go:171
Wraps: (4) monitor task failed
Wraps: (5) attached stack trace
-- stack trace:
| main.init
| main/pkg/cmd/roachtest/monitor.go:80
| runtime.doInit
| GOROOT/src/runtime/proc.go:6498
| runtime.main
| GOROOT/src/runtime/proc.go:238
| runtime.goexit
| GOROOT/src/runtime/asm_amd64.s:1581
Wraps: (6) t.Fatal() was called
Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *withstack.withStack (4) *errutil.withPrefix (5) *withstack.withStack (6) *errutil.leafError
```
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/kv-triage
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*network/sanity/nodes=4.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| non_priority | roachtest network sanity nodes failed roachtest network sanity nodes with on release the test failed on branch release cloud gce test artifacts and logs in artifacts network sanity nodes run network go monitor go errgroup go node unexpectedly affected by latency select took monitor go network go network go test runner go monitor failure monitor task failed t fatal was called attached stack trace stack trace main monitorimpl waite main pkg cmd roachtest monitor go main monitorimpl wait main pkg cmd roachtest monitor go github com cockroachdb cockroach pkg cmd roachtest tests runnetworksanity github com cockroachdb cockroach pkg cmd roachtest tests network go github com cockroachdb cockroach pkg cmd roachtest tests registernetwork github com cockroachdb cockroach pkg cmd roachtest tests network go main testrunner runtest main pkg cmd roachtest test runner go wraps monitor failure wraps attached stack trace stack trace main monitorimpl wait main pkg cmd roachtest monitor go wraps monitor task failed wraps attached stack trace stack trace main init main pkg cmd roachtest monitor go runtime doinit goroot src runtime proc go runtime main goroot src runtime proc go runtime goexit goroot src runtime asm s wraps t fatal was called error types withstack withstack errutil withprefix withstack withstack errutil withprefix withstack withstack errutil leaferror help see see cc cockroachdb kv triage | 0 |
174,502 | 21,300,158,050 | IssuesEvent | 2022-04-15 01:15:15 | insited/BlogEngine | https://api.github.com/repos/insited/BlogEngine | opened | CVE-2021-43138 (High) detected in async-0.2.10.tgz, async-0.1.22.tgz | security vulnerability | ## CVE-2021-43138 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>async-0.2.10.tgz</b>, <b>async-0.1.22.tgz</b></p></summary>
<p>
<details><summary><b>async-0.2.10.tgz</b></p></summary>
<p>Higher-order functions and common patterns for asynchronous code</p>
<p>Library home page: <a href="https://registry.npmjs.org/async/-/async-0.2.10.tgz">https://registry.npmjs.org/async/-/async-0.2.10.tgz</a></p>
<p>Path to dependency file: /BlogEngine/package.json</p>
<p>Path to vulnerable library: /node_modules/async/package.json</p>
<p>
Dependency Hierarchy:
- hexo-3.8.0.tgz (Root Library)
- swig-templates-2.0.3.tgz
- uglify-js-2.6.0.tgz
- :x: **async-0.2.10.tgz** (Vulnerable Library)
</details>
<details><summary><b>async-0.1.22.tgz</b></p></summary>
<p>Higher-order functions and common patterns for asynchronous code</p>
<p>Library home page: <a href="https://registry.npmjs.org/async/-/async-0.1.22.tgz">https://registry.npmjs.org/async/-/async-0.1.22.tgz</a></p>
<p>Path to dependency file: /BlogEngine/themes/landscape/package.json</p>
<p>Path to vulnerable library: /themes/landscape/node_modules/async/package.json</p>
<p>
Dependency Hierarchy:
- grunt-0.4.5.tgz (Root Library)
- :x: **async-0.1.22.tgz** (Vulnerable Library)
</details>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A vulnerability exists in Async through 3.2.1 (fixed in 3.2.2) , which could let a malicious user obtain privileges via the mapValues() method.
<p>Publish Date: 2022-04-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-43138>CVE-2021-43138</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: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-43138">https://nvd.nist.gov/vuln/detail/CVE-2021-43138</a></p>
<p>Release Date: 2022-04-06</p>
<p>Fix Resolution (async): 3.2.2</p>
<p>Direct dependency fix Resolution (hexo): 5.0.0</p><p>Fix Resolution (async): 3.2.2</p>
<p>Direct dependency fix Resolution (grunt): 1.3.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-2021-43138 (High) detected in async-0.2.10.tgz, async-0.1.22.tgz - ## CVE-2021-43138 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>async-0.2.10.tgz</b>, <b>async-0.1.22.tgz</b></p></summary>
<p>
<details><summary><b>async-0.2.10.tgz</b></p></summary>
<p>Higher-order functions and common patterns for asynchronous code</p>
<p>Library home page: <a href="https://registry.npmjs.org/async/-/async-0.2.10.tgz">https://registry.npmjs.org/async/-/async-0.2.10.tgz</a></p>
<p>Path to dependency file: /BlogEngine/package.json</p>
<p>Path to vulnerable library: /node_modules/async/package.json</p>
<p>
Dependency Hierarchy:
- hexo-3.8.0.tgz (Root Library)
- swig-templates-2.0.3.tgz
- uglify-js-2.6.0.tgz
- :x: **async-0.2.10.tgz** (Vulnerable Library)
</details>
<details><summary><b>async-0.1.22.tgz</b></p></summary>
<p>Higher-order functions and common patterns for asynchronous code</p>
<p>Library home page: <a href="https://registry.npmjs.org/async/-/async-0.1.22.tgz">https://registry.npmjs.org/async/-/async-0.1.22.tgz</a></p>
<p>Path to dependency file: /BlogEngine/themes/landscape/package.json</p>
<p>Path to vulnerable library: /themes/landscape/node_modules/async/package.json</p>
<p>
Dependency Hierarchy:
- grunt-0.4.5.tgz (Root Library)
- :x: **async-0.1.22.tgz** (Vulnerable Library)
</details>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A vulnerability exists in Async through 3.2.1 (fixed in 3.2.2) , which could let a malicious user obtain privileges via the mapValues() method.
<p>Publish Date: 2022-04-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-43138>CVE-2021-43138</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: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-43138">https://nvd.nist.gov/vuln/detail/CVE-2021-43138</a></p>
<p>Release Date: 2022-04-06</p>
<p>Fix Resolution (async): 3.2.2</p>
<p>Direct dependency fix Resolution (hexo): 5.0.0</p><p>Fix Resolution (async): 3.2.2</p>
<p>Direct dependency fix Resolution (grunt): 1.3.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_priority | cve high detected in async tgz async tgz cve high severity vulnerability vulnerable libraries async tgz async tgz async tgz higher order functions and common patterns for asynchronous code library home page a href path to dependency file blogengine package json path to vulnerable library node modules async package json dependency hierarchy hexo tgz root library swig templates tgz uglify js tgz x async tgz vulnerable library async tgz higher order functions and common patterns for asynchronous code library home page a href path to dependency file blogengine themes landscape package json path to vulnerable library themes landscape node modules async package json dependency hierarchy grunt tgz root library x async tgz vulnerable library vulnerability details a vulnerability exists in async through fixed in which could let a malicious user obtain privileges via the mapvalues method publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution async direct dependency fix resolution hexo fix resolution async direct dependency fix resolution grunt step up your open source security game with whitesource | 0 |
26,071 | 6,743,704,993 | IssuesEvent | 2017-10-20 13:12:23 | zhmcclient/zhmccli | https://api.github.com/repos/zhmcclient/zhmccli | closed | Bad line breaks when partition has more than one NIC | area: code resolution: fixed type: bug | Copied from zhmcclient/python-zhmcclient#179 (opened by scheuran):
### Actual behavior
Show the partition details of an Partition that has at least 2 NICs attached:
> zhmc partition show <CPC> <Partition>
The zhmccli does not do any line breaks. This gets very ugly when the *uri fields (list of URIs).
As there's no line break, the terminal breaks the line - which does not look nice at all!
### Expected behavior
Ideally the zhmccli would make a line break after each uri list item.
### Execution environment
* zhmcclient version: 0.9.0
* Operating system (type+version): ubuntu14 (x86)
| 1.0 | Bad line breaks when partition has more than one NIC - Copied from zhmcclient/python-zhmcclient#179 (opened by scheuran):
### Actual behavior
Show the partition details of an Partition that has at least 2 NICs attached:
> zhmc partition show <CPC> <Partition>
The zhmccli does not do any line breaks. This gets very ugly when the *uri fields (list of URIs).
As there's no line break, the terminal breaks the line - which does not look nice at all!
### Expected behavior
Ideally the zhmccli would make a line break after each uri list item.
### Execution environment
* zhmcclient version: 0.9.0
* Operating system (type+version): ubuntu14 (x86)
| non_priority | bad line breaks when partition has more than one nic copied from zhmcclient python zhmcclient opened by scheuran actual behavior show the partition details of an partition that has at least nics attached zhmc partition show the zhmccli does not do any line breaks this gets very ugly when the uri fields list of uris as there s no line break the terminal breaks the line which does not look nice at all expected behavior ideally the zhmccli would make a line break after each uri list item execution environment zhmcclient version operating system type version | 0 |
305,557 | 26,393,132,723 | IssuesEvent | 2023-01-12 17:07:58 | dart-lang/co19 | https://api.github.com/repos/dart-lang/co19 | closed | LanguageFeatures/Patterns/variable_A02_t01 | bad-test | This test tries to match a map with 2 entries `{1: 3, 3: 4}` against the pattern `{1: var a}` which can only match maps with 1 entry:
https://github.com/dart-lang/co19/blob/780034a9476ea8e9de6d2eecf33e6e0f02a2c220/LanguageFeatures/Patterns/variable_A02_t01.dart#L212
https://github.com/dart-lang/co19/blob/780034a9476ea8e9de6d2eecf33e6e0f02a2c220/LanguageFeatures/Patterns/variable_A02_t01.dart#L106-L119 | 1.0 | LanguageFeatures/Patterns/variable_A02_t01 - This test tries to match a map with 2 entries `{1: 3, 3: 4}` against the pattern `{1: var a}` which can only match maps with 1 entry:
https://github.com/dart-lang/co19/blob/780034a9476ea8e9de6d2eecf33e6e0f02a2c220/LanguageFeatures/Patterns/variable_A02_t01.dart#L212
https://github.com/dart-lang/co19/blob/780034a9476ea8e9de6d2eecf33e6e0f02a2c220/LanguageFeatures/Patterns/variable_A02_t01.dart#L106-L119 | non_priority | languagefeatures patterns variable this test tries to match a map with entries against the pattern var a which can only match maps with entry | 0 |
27,714 | 12,694,771,400 | IssuesEvent | 2020-06-22 07:14:19 | microsoft/azure-tools-for-java | https://api.github.com/repos/microsoft/azure-tools-for-java | closed | [IntelliJ] stuck during deployment of Java web app | IntelliJ app-service need more info try-to-reproduce | Azure Toolkit for IntelliJ Version: v3.22.0-2019.1
IntelliJ version:
IDEA 2019.1.2 (Community Edition)
Build #IC-191.7141.44, built on May 7, 2019
JRE: 1.8.0_202-release-1483-b49 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
Repro steps:
- Run Azure deployment from IntelliJ

- Deployment is stuck

- By checking via FTP, the file is created with size 0 bytes

| 1.0 | [IntelliJ] stuck during deployment of Java web app - Azure Toolkit for IntelliJ Version: v3.22.0-2019.1
IntelliJ version:
IDEA 2019.1.2 (Community Edition)
Build #IC-191.7141.44, built on May 7, 2019
JRE: 1.8.0_202-release-1483-b49 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
Repro steps:
- Run Azure deployment from IntelliJ

- Deployment is stuck

- By checking via FTP, the file is created with size 0 bytes

| non_priority | stuck during deployment of java web app azure toolkit for intellij version intellij version idea community edition build ic built on may jre release jvm openjdk bit server vm by jetbrains s r o windows repro steps run azure deployment from intellij deployment is stuck by checking via ftp the file is created with size bytes | 0 |
98,441 | 8,677,263,497 | IssuesEvent | 2018-11-30 16:18:33 | mozilla-services/syncstorage-rs | https://api.github.com/repos/mozilla-services/syncstorage-rs | closed | Improper response status codes | e2e tests in progress | Several requests return a 400 instead of 415, or a 400 instead of 404, or a 200 instead of a 400. | 1.0 | Improper response status codes - Several requests return a 400 instead of 415, or a 400 instead of 404, or a 200 instead of a 400. | non_priority | improper response status codes several requests return a instead of or a instead of or a instead of a | 0 |
214,721 | 16,576,370,208 | IssuesEvent | 2021-05-31 05:43:20 | SSBMTonberry/tileson | https://api.github.com/repos/SSBMTonberry/tileson | closed | Finish up and update documentation and readme for v1.3.0 | documentation | No need for further description on this. | 1.0 | Finish up and update documentation and readme for v1.3.0 - No need for further description on this. | non_priority | finish up and update documentation and readme for no need for further description on this | 0 |
214,589 | 24,077,735,131 | IssuesEvent | 2022-09-19 01:05:42 | Baneeishaque/Raindrop-Removal-With-Light-Field-Image-Using-Image-Inpainting | https://api.github.com/repos/Baneeishaque/Raindrop-Removal-With-Light-Field-Image-Using-Image-Inpainting | closed | CVE-2021-29595 (High) detected in tensorflow-1.15.0-cp37-cp37m-manylinux2010_x86_64.whl - autoclosed | security vulnerability | ## CVE-2021-29595 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tensorflow-1.15.0-cp37-cp37m-manylinux2010_x86_64.whl</b></p></summary>
<p>TensorFlow is an open source machine learning framework for everyone.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/92/2b/e3af15221da9ff323521565fa3324b0d7c7c5b1d7a8ca66984c8d59cb0ce/tensorflow-1.15.0-cp37-cp37m-manylinux2010_x86_64.whl">https://files.pythonhosted.org/packages/92/2b/e3af15221da9ff323521565fa3324b0d7c7c5b1d7a8ca66984c8d59cb0ce/tensorflow-1.15.0-cp37-cp37m-manylinux2010_x86_64.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **tensorflow-1.15.0-cp37-cp37m-manylinux2010_x86_64.whl** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
TensorFlow is an end-to-end open source platform for machine learning. The implementation of the `DepthToSpace` TFLite operator is vulnerable to a division by zero error(https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/depth_to_space.cc#L63-L69). An attacker can craft a model such that `params->block_size` is 0. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
<p>Publish Date: 2021-05-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-29595>CVE-2021-29595</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://github.com/tensorflow/tensorflow/security/advisories/GHSA-vf94-36g5-69v8">https://github.com/tensorflow/tensorflow/security/advisories/GHSA-vf94-36g5-69v8</a></p>
<p>Release Date: 2021-05-14</p>
<p>Fix Resolution: tensorflow - 2.5.0, tensorflow-cpu - 2.5.0, tensorflow-gpu - 2.5.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-29595 (High) detected in tensorflow-1.15.0-cp37-cp37m-manylinux2010_x86_64.whl - autoclosed - ## CVE-2021-29595 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tensorflow-1.15.0-cp37-cp37m-manylinux2010_x86_64.whl</b></p></summary>
<p>TensorFlow is an open source machine learning framework for everyone.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/92/2b/e3af15221da9ff323521565fa3324b0d7c7c5b1d7a8ca66984c8d59cb0ce/tensorflow-1.15.0-cp37-cp37m-manylinux2010_x86_64.whl">https://files.pythonhosted.org/packages/92/2b/e3af15221da9ff323521565fa3324b0d7c7c5b1d7a8ca66984c8d59cb0ce/tensorflow-1.15.0-cp37-cp37m-manylinux2010_x86_64.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **tensorflow-1.15.0-cp37-cp37m-manylinux2010_x86_64.whl** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
TensorFlow is an end-to-end open source platform for machine learning. The implementation of the `DepthToSpace` TFLite operator is vulnerable to a division by zero error(https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/depth_to_space.cc#L63-L69). An attacker can craft a model such that `params->block_size` is 0. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
<p>Publish Date: 2021-05-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-29595>CVE-2021-29595</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://github.com/tensorflow/tensorflow/security/advisories/GHSA-vf94-36g5-69v8">https://github.com/tensorflow/tensorflow/security/advisories/GHSA-vf94-36g5-69v8</a></p>
<p>Release Date: 2021-05-14</p>
<p>Fix Resolution: tensorflow - 2.5.0, tensorflow-cpu - 2.5.0, tensorflow-gpu - 2.5.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in tensorflow whl autoclosed cve high severity vulnerability vulnerable library tensorflow whl tensorflow is an open source machine learning framework for everyone library home page a href path to dependency file requirements txt path to vulnerable library requirements txt dependency hierarchy x tensorflow whl vulnerable library found in base branch main vulnerability details tensorflow is an end to end open source platform for machine learning the implementation of the depthtospace tflite operator is vulnerable to a division by zero error an attacker can craft a model such that params block size is the fix will be included in tensorflow we will also cherrypick this commit on tensorflow tensorflow tensorflow and tensorflow as these are also affected and still in supported range 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 tensorflow tensorflow cpu tensorflow gpu step up your open source security game with mend | 0 |
32,166 | 7,496,785,048 | IssuesEvent | 2018-04-08 13:15:51 | vshaxe/vshaxe | https://api.github.com/repos/vshaxe/vshaxe | closed | Can't navigate to errors in haxelibs ("unable to open file") | blocked-vscode bug | When an error occurs in a haxelib, the path is absolute, breaking navigation with the problems view:

The problem matcher assumes relative paths. `"fileLocation": "absolute"` helps, but it breaks other errors with relative filepaths.
Waiting on https://github.com/Microsoft/vscode/issues/449 to be resolved.
| 1.0 | Can't navigate to errors in haxelibs ("unable to open file") - When an error occurs in a haxelib, the path is absolute, breaking navigation with the problems view:

The problem matcher assumes relative paths. `"fileLocation": "absolute"` helps, but it breaks other errors with relative filepaths.
Waiting on https://github.com/Microsoft/vscode/issues/449 to be resolved.
| non_priority | can t navigate to errors in haxelibs unable to open file when an error occurs in a haxelib the path is absolute breaking navigation with the problems view the problem matcher assumes relative paths filelocation absolute helps but it breaks other errors with relative filepaths waiting on to be resolved | 0 |
16,108 | 9,690,387,330 | IssuesEvent | 2019-05-24 08:30:54 | cuba-platform/cuba | https://api.github.com/repos/cuba-platform/cuba | closed | Update jackson-databind to 2.9.9 | state: fixed type: security ver: 6.10.10 ver: 6.8.18 ver: 6.9.10 ver: 7.0.6 ver: 7.1.0 ver: 7.2.0 | ### Environment
- Platform version: 6.10.9
### Description of the bug or enhancement
CVE-2019-12086
moderate severity
Vulnerable versions: >= 2.0.0, < 2.9.9
Patched version: 2.9.9
A Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.x before 2.9.9. When Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint, the service has the mysql-connector-java jar (8.0.14 or earlier) in the classpath, and an attacker can host a crafted MySQL server reachable by the victim, an attacker can send a crafted JSON message that allows them to read arbitrary local files on the server. This occurs because of missing com.mysql.cj.jdbc.admin.MiniAdmin validation.
#### Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.9.9 or later. | True | Update jackson-databind to 2.9.9 - ### Environment
- Platform version: 6.10.9
### Description of the bug or enhancement
CVE-2019-12086
moderate severity
Vulnerable versions: >= 2.0.0, < 2.9.9
Patched version: 2.9.9
A Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.x before 2.9.9. When Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint, the service has the mysql-connector-java jar (8.0.14 or earlier) in the classpath, and an attacker can host a crafted MySQL server reachable by the victim, an attacker can send a crafted JSON message that allows them to read arbitrary local files on the server. This occurs because of missing com.mysql.cj.jdbc.admin.MiniAdmin validation.
#### Remediation
Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.9.9 or later. | non_priority | update jackson databind to environment platform version description of the bug or enhancement cve moderate severity vulnerable versions patched version a polymorphic typing issue was discovered in fasterxml jackson databind x before when default typing is enabled either globally or for a specific property for an externally exposed json endpoint the service has the mysql connector java jar or earlier in the classpath and an attacker can host a crafted mysql server reachable by the victim an attacker can send a crafted json message that allows them to read arbitrary local files on the server this occurs because of missing com mysql cj jdbc admin miniadmin validation remediation upgrade com fasterxml jackson core jackson databind to version or later | 0 |
240,650 | 18,363,761,583 | IssuesEvent | 2021-10-09 17:41:40 | WassimBenzarti/colab-ssh | https://api.github.com/repos/WassimBenzarti/colab-ssh | closed | Make a video tutorial on how to use colab-ssh | documentation | 1. Explain what colab-ssh does
2. Demo on the function `launch_ssh_cloudflared`
3. Demo on the function `init_git_cloudflared`
4. Security tips | 1.0 | Make a video tutorial on how to use colab-ssh - 1. Explain what colab-ssh does
2. Demo on the function `launch_ssh_cloudflared`
3. Demo on the function `init_git_cloudflared`
4. Security tips | non_priority | make a video tutorial on how to use colab ssh explain what colab ssh does demo on the function launch ssh cloudflared demo on the function init git cloudflared security tips | 0 |
23,070 | 11,839,606,396 | IssuesEvent | 2020-03-23 17:25:28 | Azure/azure-powershell | https://api.github.com/repos/Azure/azure-powershell | closed | Get-AzCosmosDBCassandraTableThroughput does not emit ThroughputSettingsResult like all other API Get-AzCosmosDB*Throughput cmdlets do | Cosmos Service Attention | Get-AzCosmosDBCassandraTableThroughput does not emit PSThroughputSettingsResults, unlike all the other API Get-AzCosmosDB*Throughput cmdlets. Compare the outputs below:
PS C:\Users\paelaz\Code\plzm.github\azure-docs-powershell-samples\cosmosdb> Get-AzCosmosDBCassandraTableThroughput -ResourceGroupName myResourceGroup -AccountName pz-cdb-cass -KeyspaceName mykeyspace -Name mytable
Resource : Microsoft.Azure.Management.CosmosDB.Models.ThroughputSettingsGetPropertiesResource
Id : /subscriptions/e61e4c75-268b-4c94-ad48-237aa3231481/resourceGroups/myResourceGroup/providers/Microsoft.DocumentDB/databaseAccounts/pz-cdb-cass/cassandraKeysp
aces/mykeyspace/tables/mytable/throughputSettings/default
Name : 8v5a
Type : Microsoft.DocumentDB/databaseAccounts/cassandraKeyspaces/tables/throughputSettings
Location :
Tags :
PS C:\Users\paelaz\Code\plzm.github\azure-docs-powershell-samples\cosmosdb> Get-AzCosmosDBGremlinGraphThroughput -ResourceGroupName myResourceGroup -AccountName pz-cdb-gremlin -DatabaseName myDatabase -Name myGraph
Name : Lrkw
Id : /subscriptions/e61e4c75-268b-4c94-ad48-237aa3231481/resourceGroups/myResourceGroup/providers/Microsoft.DocumentDB/databaseAccounts/pz-cdb-gremlin/
gremlinDatabases/myDatabase/graphs/myGraph/throughputSettings/default
Throughput : 400
MinimumThroughput : 400
OfferReplacePending :
PS C:\Users\paelaz\Code\plzm.github\azure-docs-powershell-samples\cosmosdb> Get-AzCosmosDBMongoDBCollectionThroughput -ResourceGroupName myResourceGroup -AccountName pz-cdb-mongo -DatabaseName myDatabase -Name myCollection
Name : yuKT
Id : /subscriptions/e61e4c75-268b-4c94-ad48-237aa3231481/resourceGroups/myResourceGroup/providers/Microsoft.DocumentDB/databaseAccounts/pz-cdb-mongo/mo
ngodbDatabases/myDatabase/collections/myCollection/throughputSettings/default
Throughput : 400
MinimumThroughput : 400
OfferReplacePending :
PS C:\Users\paelaz\Code\plzm.github\azure-docs-powershell-samples\cosmosdb> Get-AzCosmosDBSqlContainerThroughput -ResourceGroupName myResourceGroup -AccountName pz-cdb-sql -DatabaseName myDatabase -Name myContainer
Name : nxw-
Id : /subscriptions/e61e4c75-268b-4c94-ad48-237aa3231481/resourceGroups/myResourceGroup/providers/Microsoft.DocumentDB/databaseAccounts/pz-cdb-sql/sqlD
atabases/myDatabase/containers/myContainer/throughputSettings/default
Throughput : 400
MinimumThroughput : 400
OfferReplacePending :
PS C:\Users\paelaz\Code\plzm.github\azure-docs-powershell-samples\cosmosdb> Get-AzCosmosDBTableThroughput -ResourceGroupName myResourceGroup -AccountName pz-cdb-table -Name myTable
Name : fl1K
Id : /subscriptions/e61e4c75-268b-4c94-ad48-237aa3231481/resourceGroups/myResourceGroup/providers/Microsoft.DocumentDB/databaseAccounts/pz-cdb-table/ta
bles/myTable/throughputSettings/default
Throughput : 400
MinimumThroughput : 400
OfferReplacePending :
| 1.0 | Get-AzCosmosDBCassandraTableThroughput does not emit ThroughputSettingsResult like all other API Get-AzCosmosDB*Throughput cmdlets do - Get-AzCosmosDBCassandraTableThroughput does not emit PSThroughputSettingsResults, unlike all the other API Get-AzCosmosDB*Throughput cmdlets. Compare the outputs below:
PS C:\Users\paelaz\Code\plzm.github\azure-docs-powershell-samples\cosmosdb> Get-AzCosmosDBCassandraTableThroughput -ResourceGroupName myResourceGroup -AccountName pz-cdb-cass -KeyspaceName mykeyspace -Name mytable
Resource : Microsoft.Azure.Management.CosmosDB.Models.ThroughputSettingsGetPropertiesResource
Id : /subscriptions/e61e4c75-268b-4c94-ad48-237aa3231481/resourceGroups/myResourceGroup/providers/Microsoft.DocumentDB/databaseAccounts/pz-cdb-cass/cassandraKeysp
aces/mykeyspace/tables/mytable/throughputSettings/default
Name : 8v5a
Type : Microsoft.DocumentDB/databaseAccounts/cassandraKeyspaces/tables/throughputSettings
Location :
Tags :
PS C:\Users\paelaz\Code\plzm.github\azure-docs-powershell-samples\cosmosdb> Get-AzCosmosDBGremlinGraphThroughput -ResourceGroupName myResourceGroup -AccountName pz-cdb-gremlin -DatabaseName myDatabase -Name myGraph
Name : Lrkw
Id : /subscriptions/e61e4c75-268b-4c94-ad48-237aa3231481/resourceGroups/myResourceGroup/providers/Microsoft.DocumentDB/databaseAccounts/pz-cdb-gremlin/
gremlinDatabases/myDatabase/graphs/myGraph/throughputSettings/default
Throughput : 400
MinimumThroughput : 400
OfferReplacePending :
PS C:\Users\paelaz\Code\plzm.github\azure-docs-powershell-samples\cosmosdb> Get-AzCosmosDBMongoDBCollectionThroughput -ResourceGroupName myResourceGroup -AccountName pz-cdb-mongo -DatabaseName myDatabase -Name myCollection
Name : yuKT
Id : /subscriptions/e61e4c75-268b-4c94-ad48-237aa3231481/resourceGroups/myResourceGroup/providers/Microsoft.DocumentDB/databaseAccounts/pz-cdb-mongo/mo
ngodbDatabases/myDatabase/collections/myCollection/throughputSettings/default
Throughput : 400
MinimumThroughput : 400
OfferReplacePending :
PS C:\Users\paelaz\Code\plzm.github\azure-docs-powershell-samples\cosmosdb> Get-AzCosmosDBSqlContainerThroughput -ResourceGroupName myResourceGroup -AccountName pz-cdb-sql -DatabaseName myDatabase -Name myContainer
Name : nxw-
Id : /subscriptions/e61e4c75-268b-4c94-ad48-237aa3231481/resourceGroups/myResourceGroup/providers/Microsoft.DocumentDB/databaseAccounts/pz-cdb-sql/sqlD
atabases/myDatabase/containers/myContainer/throughputSettings/default
Throughput : 400
MinimumThroughput : 400
OfferReplacePending :
PS C:\Users\paelaz\Code\plzm.github\azure-docs-powershell-samples\cosmosdb> Get-AzCosmosDBTableThroughput -ResourceGroupName myResourceGroup -AccountName pz-cdb-table -Name myTable
Name : fl1K
Id : /subscriptions/e61e4c75-268b-4c94-ad48-237aa3231481/resourceGroups/myResourceGroup/providers/Microsoft.DocumentDB/databaseAccounts/pz-cdb-table/ta
bles/myTable/throughputSettings/default
Throughput : 400
MinimumThroughput : 400
OfferReplacePending :
| non_priority | get azcosmosdbcassandratablethroughput does not emit throughputsettingsresult like all other api get azcosmosdb throughput cmdlets do get azcosmosdbcassandratablethroughput does not emit psthroughputsettingsresults unlike all the other api get azcosmosdb throughput cmdlets compare the outputs below ps c users paelaz code plzm github azure docs powershell samples cosmosdb get azcosmosdbcassandratablethroughput resourcegroupname myresourcegroup accountname pz cdb cass keyspacename mykeyspace name mytable resource microsoft azure management cosmosdb models throughputsettingsgetpropertiesresource id subscriptions resourcegroups myresourcegroup providers microsoft documentdb databaseaccounts pz cdb cass cassandrakeysp aces mykeyspace tables mytable throughputsettings default name type microsoft documentdb databaseaccounts cassandrakeyspaces tables throughputsettings location tags ps c users paelaz code plzm github azure docs powershell samples cosmosdb get azcosmosdbgremlingraphthroughput resourcegroupname myresourcegroup accountname pz cdb gremlin databasename mydatabase name mygraph name lrkw id subscriptions resourcegroups myresourcegroup providers microsoft documentdb databaseaccounts pz cdb gremlin gremlindatabases mydatabase graphs mygraph throughputsettings default throughput minimumthroughput offerreplacepending ps c users paelaz code plzm github azure docs powershell samples cosmosdb get azcosmosdbmongodbcollectionthroughput resourcegroupname myresourcegroup accountname pz cdb mongo databasename mydatabase name mycollection name yukt id subscriptions resourcegroups myresourcegroup providers microsoft documentdb databaseaccounts pz cdb mongo mo ngodbdatabases mydatabase collections mycollection throughputsettings default throughput minimumthroughput offerreplacepending ps c users paelaz code plzm github azure docs powershell samples cosmosdb get azcosmosdbsqlcontainerthroughput resourcegroupname myresourcegroup accountname pz cdb sql databasename mydatabase name mycontainer name nxw id subscriptions resourcegroups myresourcegroup providers microsoft documentdb databaseaccounts pz cdb sql sqld atabases mydatabase containers mycontainer throughputsettings default throughput minimumthroughput offerreplacepending ps c users paelaz code plzm github azure docs powershell samples cosmosdb get azcosmosdbtablethroughput resourcegroupname myresourcegroup accountname pz cdb table name mytable name id subscriptions resourcegroups myresourcegroup providers microsoft documentdb databaseaccounts pz cdb table ta bles mytable throughputsettings default throughput minimumthroughput offerreplacepending | 0 |
183,607 | 21,775,005,136 | IssuesEvent | 2022-05-13 13:01:01 | lukebroganws/secDevLabs | https://api.github.com/repos/lukebroganws/secDevLabs | opened | CVE-2022-22970 (Medium) detected in spring-beans-5.2.9.RELEASE.jar | security vulnerability | ## CVE-2022-22970 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-beans-5.2.9.RELEASE.jar</b></p></summary>
<p>Spring Beans</p>
<p>Path to dependency file: /owasp-top10-2021-apps/a3/streaming/app/backend/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-beans/5.2.9.RELEASE/spring-beans-5.2.9.RELEASE.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-jpa-2.3.4.RELEASE.jar (Root Library)
- spring-data-jpa-2.3.4.RELEASE.jar
- :x: **spring-beans-5.2.9.RELEASE.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/lukebroganws/secDevLabs/commit/c66f2ad957084d73653f76b825cbe31fa86061ba">c66f2ad957084d73653f76b825cbe31fa86061ba</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 spring framework versions prior to 5.3.20+ , 5.2.22+ and old unsupported versions, applications that handle file uploads are vulnerable to DoS attack if they rely on data binding to set a MultipartFile or javax.servlet.Part to a field in a model object.
<p>Publish Date: 2022-05-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-22970>CVE-2022-22970</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- 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://tanzu.vmware.com/security/cve-2022-22970">https://tanzu.vmware.com/security/cve-2022-22970</a></p>
<p>Release Date: 2022-05-12</p>
<p>Fix Resolution: org.springframework:spring-beans:5.2.22,5.3.20;org.springframework:spring-core:5.2.22,5.3.20</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.springframework","packageName":"spring-beans","packageVersion":"5.2.9.RELEASE","packageFilePaths":["/owasp-top10-2021-apps/a3/streaming/app/backend/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"org.springframework.boot:spring-boot-starter-data-jpa:2.3.4.RELEASE;org.springframework.data:spring-data-jpa:2.3.4.RELEASE;org.springframework:spring-beans:5.2.9.RELEASE","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.springframework:spring-beans:5.2.22,5.3.20;org.springframework:spring-core:5.2.22,5.3.20","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2022-22970","vulnerabilityDetails":"In spring framework versions prior to 5.3.20+ , 5.2.22+ and old unsupported versions, applications that handle file uploads are vulnerable to DoS attack if they rely on data binding to set a MultipartFile or javax.servlet.Part to a field in a model object.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-22970","cvss3Severity":"medium","cvss3Score":"5.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"Required","AV":"Local","I":"None"},"extraData":{}}</REMEDIATE> --> | True | CVE-2022-22970 (Medium) detected in spring-beans-5.2.9.RELEASE.jar - ## CVE-2022-22970 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-beans-5.2.9.RELEASE.jar</b></p></summary>
<p>Spring Beans</p>
<p>Path to dependency file: /owasp-top10-2021-apps/a3/streaming/app/backend/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-beans/5.2.9.RELEASE/spring-beans-5.2.9.RELEASE.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-jpa-2.3.4.RELEASE.jar (Root Library)
- spring-data-jpa-2.3.4.RELEASE.jar
- :x: **spring-beans-5.2.9.RELEASE.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/lukebroganws/secDevLabs/commit/c66f2ad957084d73653f76b825cbe31fa86061ba">c66f2ad957084d73653f76b825cbe31fa86061ba</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 spring framework versions prior to 5.3.20+ , 5.2.22+ and old unsupported versions, applications that handle file uploads are vulnerable to DoS attack if they rely on data binding to set a MultipartFile or javax.servlet.Part to a field in a model object.
<p>Publish Date: 2022-05-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-22970>CVE-2022-22970</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- 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://tanzu.vmware.com/security/cve-2022-22970">https://tanzu.vmware.com/security/cve-2022-22970</a></p>
<p>Release Date: 2022-05-12</p>
<p>Fix Resolution: org.springframework:spring-beans:5.2.22,5.3.20;org.springframework:spring-core:5.2.22,5.3.20</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.springframework","packageName":"spring-beans","packageVersion":"5.2.9.RELEASE","packageFilePaths":["/owasp-top10-2021-apps/a3/streaming/app/backend/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"org.springframework.boot:spring-boot-starter-data-jpa:2.3.4.RELEASE;org.springframework.data:spring-data-jpa:2.3.4.RELEASE;org.springframework:spring-beans:5.2.9.RELEASE","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.springframework:spring-beans:5.2.22,5.3.20;org.springframework:spring-core:5.2.22,5.3.20","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2022-22970","vulnerabilityDetails":"In spring framework versions prior to 5.3.20+ , 5.2.22+ and old unsupported versions, applications that handle file uploads are vulnerable to DoS attack if they rely on data binding to set a MultipartFile or javax.servlet.Part to a field in a model object.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-22970","cvss3Severity":"medium","cvss3Score":"5.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"Required","AV":"Local","I":"None"},"extraData":{}}</REMEDIATE> --> | non_priority | cve medium detected in spring beans release jar cve medium severity vulnerability vulnerable library spring beans release jar spring beans path to dependency file owasp apps streaming app backend pom xml path to vulnerable library home wss scanner repository org springframework spring beans release spring beans release jar dependency hierarchy spring boot starter data jpa release jar root library spring data jpa release jar x spring beans release jar vulnerable library found in head commit a href found in base branch master vulnerability details in spring framework versions prior to and old unsupported versions applications that handle file uploads are vulnerable to dos attack if they rely on data binding to set a multipartfile or javax servlet part to a field in a model object publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required 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 org springframework spring beans org springframework spring core isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree org springframework boot spring boot starter data jpa release org springframework data spring data jpa release org springframework spring beans release isminimumfixversionavailable true minimumfixversion org springframework spring beans org springframework spring core isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails in spring framework versions prior to and old unsupported versions applications that handle file uploads are vulnerable to dos attack if they rely on data binding to set a multipartfile or javax servlet part to a field in a model object vulnerabilityurl | 0 |
122,771 | 16,326,663,790 | IssuesEvent | 2021-05-12 02:15:36 | ballerina-platform/ballerina-spec | https://api.github.com/repos/ballerina-platform/ballerina-spec | closed | Type narrowing rules are unsound | design/incoherent lang | Consider:
```
import ballerina/io;
function foo([int|string] x) {
if x is [int] {
io:println("it's an [int]");
}
else {
// type of x is [int|string] - [int] which is [string]
string s = x[0];
io:println("it's an [string]");
}
}
public function main() {
[int|string] x = [1];
foo(x);
}
```
The `if` test will be false because the inherent type of x is `[int|string]`, which is not a subtype of `[int]`.
The spec says that type of `x` in the `else` is the difference of `[int|string]` and `[int]` (i.e. `[string]`) which is not correct.
The question is what is the right type to infer for `x` in the `else` branch. In other words, if x belongs to T and does not belong to S (NB *belongs to* not *looks like*), what can we say about the type that x belongs to?
| 1.0 | Type narrowing rules are unsound - Consider:
```
import ballerina/io;
function foo([int|string] x) {
if x is [int] {
io:println("it's an [int]");
}
else {
// type of x is [int|string] - [int] which is [string]
string s = x[0];
io:println("it's an [string]");
}
}
public function main() {
[int|string] x = [1];
foo(x);
}
```
The `if` test will be false because the inherent type of x is `[int|string]`, which is not a subtype of `[int]`.
The spec says that type of `x` in the `else` is the difference of `[int|string]` and `[int]` (i.e. `[string]`) which is not correct.
The question is what is the right type to infer for `x` in the `else` branch. In other words, if x belongs to T and does not belong to S (NB *belongs to* not *looks like*), what can we say about the type that x belongs to?
| non_priority | type narrowing rules are unsound consider import ballerina io function foo x if x is io println it s an else type of x is which is string s x io println it s an public function main x foo x the if test will be false because the inherent type of x is which is not a subtype of the spec says that type of x in the else is the difference of and i e which is not correct the question is what is the right type to infer for x in the else branch in other words if x belongs to t and does not belong to s nb belongs to not looks like what can we say about the type that x belongs to | 0 |
84,182 | 16,464,003,799 | IssuesEvent | 2021-05-22 03:10:06 | HazDroneCorp/combat-engineers | https://api.github.com/repos/HazDroneCorp/combat-engineers | closed | Development console | art code | Button menus for development are too annoying to implement, let's just make a dev console
- [x] Move UI assets from Frontiersmen here
- [ ] Expand upon it / tweak it to fit the current game | 1.0 | Development console - Button menus for development are too annoying to implement, let's just make a dev console
- [x] Move UI assets from Frontiersmen here
- [ ] Expand upon it / tweak it to fit the current game | non_priority | development console button menus for development are too annoying to implement let s just make a dev console move ui assets from frontiersmen here expand upon it tweak it to fit the current game | 0 |
2,849 | 3,918,800,088 | IssuesEvent | 2016-04-21 13:49:23 | dotnet/wcf | https://api.github.com/repos/dotnet/wcf | closed | Define requirements for automating OuterLoop tests cross-machine | Infrastructure | OuterLoop tests require the Bridge to be running on a Windows machine. Xplat test therefore need to involve 2 machines, one with the OS to run the test, and one with Windows to run the Bridge.
As a first step, we need to name the scenarios we want to support, including:
1. Should it support being used to test PR's automatically via GitHub?
2. Should we assume the Bridge machine can always be spun-up and created for each unique test run?
3. Should we create a long-running Bridge machine tests know about and can use without starting it?
4. Should the Bridge be capable of servicing multiple clients at a time, each with different test resource versions?
5. Which test frameworks need this? Helix? ToF? Developer's machine running Linux? | 1.0 | Define requirements for automating OuterLoop tests cross-machine - OuterLoop tests require the Bridge to be running on a Windows machine. Xplat test therefore need to involve 2 machines, one with the OS to run the test, and one with Windows to run the Bridge.
As a first step, we need to name the scenarios we want to support, including:
1. Should it support being used to test PR's automatically via GitHub?
2. Should we assume the Bridge machine can always be spun-up and created for each unique test run?
3. Should we create a long-running Bridge machine tests know about and can use without starting it?
4. Should the Bridge be capable of servicing multiple clients at a time, each with different test resource versions?
5. Which test frameworks need this? Helix? ToF? Developer's machine running Linux? | non_priority | define requirements for automating outerloop tests cross machine outerloop tests require the bridge to be running on a windows machine xplat test therefore need to involve machines one with the os to run the test and one with windows to run the bridge as a first step we need to name the scenarios we want to support including should it support being used to test pr s automatically via github should we assume the bridge machine can always be spun up and created for each unique test run should we create a long running bridge machine tests know about and can use without starting it should the bridge be capable of servicing multiple clients at a time each with different test resource versions which test frameworks need this helix tof developer s machine running linux | 0 |
247,765 | 20,988,129,469 | IssuesEvent | 2022-03-29 06:38:34 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | opened | roachtest: sqlsmith/setup=seed/setting=no-ddl failed | C-test-failure O-robot O-roachtest branch-master release-blocker | roachtest.sqlsmith/setup=seed/setting=no-ddl [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=4713654&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=4713654&tab=artifacts#/sqlsmith/setup=seed/setting=no-ddl) on master @ [29716850b181718594663889ddb5f479fef7a305](https://github.com/cockroachdb/cockroach/commits/29716850b181718594663889ddb5f479fef7a305):
```
The test failed on branch=master, cloud=gce:
test artifacts and logs in: /artifacts/sqlsmith/setup=seed/setting=no-ddl/run_1
cluster.go:1868,sqlsmith.go:101,sqlsmith.go:304,test_runner.go:875: one or more parallel execution failure
(1) attached stack trace
-- stack trace:
| github.com/cockroachdb/cockroach/pkg/roachprod/install.(*SyncedCluster).ParallelE
| github.com/cockroachdb/cockroach/pkg/roachprod/install/cluster_synced.go:2042
| github.com/cockroachdb/cockroach/pkg/roachprod/install.(*SyncedCluster).Parallel
| github.com/cockroachdb/cockroach/pkg/roachprod/install/cluster_synced.go:1923
| github.com/cockroachdb/cockroach/pkg/roachprod/install.(*SyncedCluster).Start
| github.com/cockroachdb/cockroach/pkg/roachprod/install/cockroach.go:167
| github.com/cockroachdb/cockroach/pkg/roachprod.Start
| github.com/cockroachdb/cockroach/pkg/roachprod/roachprod.go:660
| main.(*clusterImpl).StartE
| main/pkg/cmd/roachtest/cluster.go:1826
| main.(*clusterImpl).Start
| main/pkg/cmd/roachtest/cluster.go:1867
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.registerSQLSmith.func3
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/sqlsmith.go:101
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.registerSQLSmith.func4.1
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/sqlsmith.go:304
| main.(*testRunner).runTest.func2
| main/pkg/cmd/roachtest/test_runner.go:875
| runtime.goexit
| GOROOT/src/runtime/asm_amd64.s:1581
Wraps: (2) one or more parallel execution failure
Error types: (1) *withstack.withStack (2) *errutil.leafError
```
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/sql-queries
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*sqlsmith/setup=seed/setting=no-ddl.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| 2.0 | roachtest: sqlsmith/setup=seed/setting=no-ddl failed - roachtest.sqlsmith/setup=seed/setting=no-ddl [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=4713654&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=4713654&tab=artifacts#/sqlsmith/setup=seed/setting=no-ddl) on master @ [29716850b181718594663889ddb5f479fef7a305](https://github.com/cockroachdb/cockroach/commits/29716850b181718594663889ddb5f479fef7a305):
```
The test failed on branch=master, cloud=gce:
test artifacts and logs in: /artifacts/sqlsmith/setup=seed/setting=no-ddl/run_1
cluster.go:1868,sqlsmith.go:101,sqlsmith.go:304,test_runner.go:875: one or more parallel execution failure
(1) attached stack trace
-- stack trace:
| github.com/cockroachdb/cockroach/pkg/roachprod/install.(*SyncedCluster).ParallelE
| github.com/cockroachdb/cockroach/pkg/roachprod/install/cluster_synced.go:2042
| github.com/cockroachdb/cockroach/pkg/roachprod/install.(*SyncedCluster).Parallel
| github.com/cockroachdb/cockroach/pkg/roachprod/install/cluster_synced.go:1923
| github.com/cockroachdb/cockroach/pkg/roachprod/install.(*SyncedCluster).Start
| github.com/cockroachdb/cockroach/pkg/roachprod/install/cockroach.go:167
| github.com/cockroachdb/cockroach/pkg/roachprod.Start
| github.com/cockroachdb/cockroach/pkg/roachprod/roachprod.go:660
| main.(*clusterImpl).StartE
| main/pkg/cmd/roachtest/cluster.go:1826
| main.(*clusterImpl).Start
| main/pkg/cmd/roachtest/cluster.go:1867
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.registerSQLSmith.func3
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/sqlsmith.go:101
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.registerSQLSmith.func4.1
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/sqlsmith.go:304
| main.(*testRunner).runTest.func2
| main/pkg/cmd/roachtest/test_runner.go:875
| runtime.goexit
| GOROOT/src/runtime/asm_amd64.s:1581
Wraps: (2) one or more parallel execution failure
Error types: (1) *withstack.withStack (2) *errutil.leafError
```
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/sql-queries
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*sqlsmith/setup=seed/setting=no-ddl.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| non_priority | roachtest sqlsmith setup seed setting no ddl failed roachtest sqlsmith setup seed setting no ddl with on master the test failed on branch master cloud gce test artifacts and logs in artifacts sqlsmith setup seed setting no ddl run cluster go sqlsmith go sqlsmith go test runner go one or more parallel execution failure attached stack trace stack trace github com cockroachdb cockroach pkg roachprod install syncedcluster parallele github com cockroachdb cockroach pkg roachprod install cluster synced go github com cockroachdb cockroach pkg roachprod install syncedcluster parallel github com cockroachdb cockroach pkg roachprod install cluster synced go github com cockroachdb cockroach pkg roachprod install syncedcluster start github com cockroachdb cockroach pkg roachprod install cockroach go github com cockroachdb cockroach pkg roachprod start github com cockroachdb cockroach pkg roachprod roachprod go main clusterimpl starte main pkg cmd roachtest cluster go main clusterimpl start main pkg cmd roachtest cluster go github com cockroachdb cockroach pkg cmd roachtest tests registersqlsmith github com cockroachdb cockroach pkg cmd roachtest tests sqlsmith go github com cockroachdb cockroach pkg cmd roachtest tests registersqlsmith github com cockroachdb cockroach pkg cmd roachtest tests sqlsmith go main testrunner runtest main pkg cmd roachtest test runner go runtime goexit goroot src runtime asm s wraps one or more parallel execution failure error types withstack withstack errutil leaferror help see see cc cockroachdb sql queries | 0 |
276,602 | 20,991,671,866 | IssuesEvent | 2022-03-29 09:50:51 | GraphicsProgramming/learnd3d11 | https://api.github.com/repos/GraphicsProgramming/learnd3d11 | closed | MkDocs: Fix Edit link | documentation | Edit link in the docs

points to the `master` branch, which doesn't exist.
Add `edit_uri: 'edit/main/docs' to `mkdocs.yml`
| 1.0 | MkDocs: Fix Edit link - Edit link in the docs

points to the `master` branch, which doesn't exist.
Add `edit_uri: 'edit/main/docs' to `mkdocs.yml`
| non_priority | mkdocs fix edit link edit link in the docs points to the master branch which doesn t exist add edit uri edit main docs to mkdocs yml | 0 |
113,712 | 24,477,983,977 | IssuesEvent | 2022-10-08 12:31:42 | bincode-org/bincode | https://api.github.com/repos/bincode-org/bincode | closed | #[derive(Encode)] and friends break on structs with default generic arguments | not-stale bincode-2 bug(fix) | I'm testing against 2.0.0-rc.1.
The derive macros cause syntax errors when given a struct with a default generic argument, such as:
```
#[derive(Encode)]
struct Foo<Bar=Baz> {}
```
This produces the following error:
```
error: Invalid rust syntax, expected ', > or an ident, got Some(Punct { ch: '=', spacing: Alone, span: #0 bytes(104880..104881) })
--> src/xxx.rs:87:15
|
87 | struct Foo<Bar=Baz> {}
```
(I tested this in some project, so there is an unhelpful line number.) | 1.0 | #[derive(Encode)] and friends break on structs with default generic arguments - I'm testing against 2.0.0-rc.1.
The derive macros cause syntax errors when given a struct with a default generic argument, such as:
```
#[derive(Encode)]
struct Foo<Bar=Baz> {}
```
This produces the following error:
```
error: Invalid rust syntax, expected ', > or an ident, got Some(Punct { ch: '=', spacing: Alone, span: #0 bytes(104880..104881) })
--> src/xxx.rs:87:15
|
87 | struct Foo<Bar=Baz> {}
```
(I tested this in some project, so there is an unhelpful line number.) | non_priority | and friends break on structs with default generic arguments i m testing against rc the derive macros cause syntax errors when given a struct with a default generic argument such as struct foo this produces the following error error invalid rust syntax expected or an ident got some punct ch spacing alone span bytes src xxx rs struct foo i tested this in some project so there is an unhelpful line number | 0 |
208,722 | 16,135,359,849 | IssuesEvent | 2021-04-29 11:05:40 | WeblateOrg/weblate | https://api.github.com/repos/WeblateOrg/weblate | closed | Question about document linking "Checks and Fixups" | documentation | I don't know much about rst linking, but it looks like the target ids in the links are missing in the page.
https://docs.weblate.org/en/latest/user/checks.html#check-python-format
https://docs.weblate.org/en/latest/user/checks.html#check-php-format
All links are just resolved to: https://docs.weblate.org/en/latest/user/checks.html#formatted-strings
See:

Is it possible to fix it? | 1.0 | Question about document linking "Checks and Fixups" - I don't know much about rst linking, but it looks like the target ids in the links are missing in the page.
https://docs.weblate.org/en/latest/user/checks.html#check-python-format
https://docs.weblate.org/en/latest/user/checks.html#check-php-format
All links are just resolved to: https://docs.weblate.org/en/latest/user/checks.html#formatted-strings
See:

Is it possible to fix it? | non_priority | question about document linking checks and fixups i don t know much about rst linking but it looks like the target ids in the links are missing in the page all links are just resolved to see is it possible to fix it | 0 |
98,883 | 30,212,622,193 | IssuesEvent | 2023-07-05 13:43:13 | golang/go | https://api.github.com/repos/golang/go | closed | x/build/cmd/relui: pkgbuild produces an installer that installs to /usr/local/go/bin/go, no longer in PATH on os X mojave | OS-Darwin Builders WaitingForInfo NeedsInvestigation | ### What version of Go are you using (`go version`)?
go 1.11.2 darwin/amd64
### Does this issue reproduce with the latest release?
Yes
### What operating system and processor architecture are you using (`go env`)?
darwin/amd64
<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/b5/Library/Caches/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/b5/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/6p/sjn8bct92397mbgwmwwvcb4h0000gn/T/go-build195699704=/tmp/go-build -gno-record-gcc-switches -fno-common"
</pre></details>
### What did you do?
Ran the go .pkg installer downloaded from golang.org. Installer completes successfully. I then moved over to the command line & ran:
```shell
$ which go
go not found
```
### What did you expect to see?
I was _hoping_ to see `/usr/local/go/bin/go`, or for some magic created by `pkgbuild/productbuild` to symlink `/usr/local/go/bin/go` -> `/usr/local/bin/go`. but alas, nope. This problem only seems to exist on os x Mojave (as far as I can tell).
### What did you see instead?
`go not found`
My guess is the fix will land [here](https://github.com/golang/build/blob/790500f5933191797a6638a27127be424f6ae2c2/cmd/release/releaselet.go)
| 1.0 | x/build/cmd/relui: pkgbuild produces an installer that installs to /usr/local/go/bin/go, no longer in PATH on os X mojave - ### What version of Go are you using (`go version`)?
go 1.11.2 darwin/amd64
### Does this issue reproduce with the latest release?
Yes
### What operating system and processor architecture are you using (`go env`)?
darwin/amd64
<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/b5/Library/Caches/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/b5/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/6p/sjn8bct92397mbgwmwwvcb4h0000gn/T/go-build195699704=/tmp/go-build -gno-record-gcc-switches -fno-common"
</pre></details>
### What did you do?
Ran the go .pkg installer downloaded from golang.org. Installer completes successfully. I then moved over to the command line & ran:
```shell
$ which go
go not found
```
### What did you expect to see?
I was _hoping_ to see `/usr/local/go/bin/go`, or for some magic created by `pkgbuild/productbuild` to symlink `/usr/local/go/bin/go` -> `/usr/local/bin/go`. but alas, nope. This problem only seems to exist on os x Mojave (as far as I can tell).
### What did you see instead?
`go not found`
My guess is the fix will land [here](https://github.com/golang/build/blob/790500f5933191797a6638a27127be424f6ae2c2/cmd/release/releaselet.go)
| non_priority | x build cmd relui pkgbuild produces an installer that installs to usr local go bin go no longer in path on os x mojave what version of go are you using go version go darwin does this issue reproduce with the latest release yes what operating system and processor architecture are you using go env darwin go env output go env goarch gobin gocache users library caches go build goexe goflags gohostarch gohostos darwin goos darwin gopath users go goproxy gorace goroot usr local go gotmpdir gotooldir usr local go pkg tool darwin gccgo gccgo cc clang cxx clang cgo enabled gomod cgo cflags g cgo cppflags cgo cxxflags g cgo fflags g cgo ldflags g pkg config pkg config gogccflags fpic pthread fno caret diagnostics qunused arguments fmessage length fdebug prefix map var folders t go tmp go build gno record gcc switches fno common what did you do ran the go pkg installer downloaded from golang org installer completes successfully i then moved over to the command line ran shell which go go not found what did you expect to see i was hoping to see usr local go bin go or for some magic created by pkgbuild productbuild to symlink usr local go bin go usr local bin go but alas nope this problem only seems to exist on os x mojave as far as i can tell what did you see instead go not found my guess is the fix will land | 0 |
61,629 | 14,632,180,817 | IssuesEvent | 2020-12-23 21:42:07 | h2oai/wave | https://api.github.com/repos/h2oai/wave | opened | Add PAM as Option for User Authentication | feature security | #### Is your feature request related to a problem? Please describe
Not all companies use OpenID for authentication or security, some require PAM which means they are unable to use Wave today
#### Describe the solution you'd like
Wave developers to be able to use Pluggable Authentication Modules in their applications
| True | Add PAM as Option for User Authentication - #### Is your feature request related to a problem? Please describe
Not all companies use OpenID for authentication or security, some require PAM which means they are unable to use Wave today
#### Describe the solution you'd like
Wave developers to be able to use Pluggable Authentication Modules in their applications
| non_priority | add pam as option for user authentication is your feature request related to a problem please describe not all companies use openid for authentication or security some require pam which means they are unable to use wave today describe the solution you d like wave developers to be able to use pluggable authentication modules in their applications | 0 |
34,320 | 7,809,755,675 | IssuesEvent | 2018-06-12 02:35:30 | ctomkow/verify | https://api.github.com/repos/ctomkow/verify | opened | Design for code upgrade verification function | code_improvement enhancement | https://github.com/ctomkow/verify/blob/0208b64b82046bcc58b3fa69f01e03744405963c/Verify.py#L86
The basic idea behind the code_upgrade method is to pull the 'before' state of a switch, reload the switch to initiate the code upgrade, then pull the 'after' state of the switch. Coimpare the two states to ensure nothing is broken. This upgrade procedure can be scaled up by having concurrent processes.
The proposed design is outlined below. It is currently partly implemented.
_CPI stands for Cisco Prime Infrastructure_
**1. Verify switch is reachable**
- CPI is slow to report UNREACHABLE state (~5 min). Current test relies on a system `ping` call.
- Would prefer an all CPI or python solution; possibly craft ICMP echo requests directly?
**2. Device sync with CPI**
- Ensures CPI has current switch state information. This is done with a POST api call
It seems CPI only stores CDP neighbour info on device added or device sync (which is on a timer, something like once a day; too slow for our needs)
**3. Current code version**
- This is grabbed to be able to compare before and after code versions being reported. Ensure code was actually upgraded.
**4. Stack members**
- Pull all stack members part of the stack to compare before and after to ensure all switches exist
- Based on testing, if a switch is powered off, the switch is not listed, if the switch is provisioned but in an error state (e.g. OS-mismatch or V-mismatch), then the switch is shown as "Provisioned" only with certain details missing (serial number, etc).
**5. CDP neighbours**
- Pull all CDP neighbours being reported to compare before and after upgrade. This will ensure that all uplinks/downlinks come back up, as well as provide informational logging if certain devices don't come back up (e.g. VoIP phones, access points).
**6. VLANs**
- Pull all current VLANs. Ensures all VLANs still exist.
**7. Voice VLAN device IP address**
- Ping IP address (e.g. VoIP phone) to test Voice VLAN connectivity before and after. A VoIP phone is reliably pingable.
**8. Wireless VLAN device IP address**
- Ping IP address (e.g. access point) to test wireless VLAN connectivity before and after. An access point is reliably pingable.
**9. Reboot switch stack**
- This is currently implemented by a system call to `swITch.py` program, to issue the 'reload' command.
- There does not seem to be a CPI api call to reload a device. Maybe i'm missing something?
...
Perform everything again in the same order, comparing as necessary
| 1.0 | Design for code upgrade verification function - https://github.com/ctomkow/verify/blob/0208b64b82046bcc58b3fa69f01e03744405963c/Verify.py#L86
The basic idea behind the code_upgrade method is to pull the 'before' state of a switch, reload the switch to initiate the code upgrade, then pull the 'after' state of the switch. Coimpare the two states to ensure nothing is broken. This upgrade procedure can be scaled up by having concurrent processes.
The proposed design is outlined below. It is currently partly implemented.
_CPI stands for Cisco Prime Infrastructure_
**1. Verify switch is reachable**
- CPI is slow to report UNREACHABLE state (~5 min). Current test relies on a system `ping` call.
- Would prefer an all CPI or python solution; possibly craft ICMP echo requests directly?
**2. Device sync with CPI**
- Ensures CPI has current switch state information. This is done with a POST api call
It seems CPI only stores CDP neighbour info on device added or device sync (which is on a timer, something like once a day; too slow for our needs)
**3. Current code version**
- This is grabbed to be able to compare before and after code versions being reported. Ensure code was actually upgraded.
**4. Stack members**
- Pull all stack members part of the stack to compare before and after to ensure all switches exist
- Based on testing, if a switch is powered off, the switch is not listed, if the switch is provisioned but in an error state (e.g. OS-mismatch or V-mismatch), then the switch is shown as "Provisioned" only with certain details missing (serial number, etc).
**5. CDP neighbours**
- Pull all CDP neighbours being reported to compare before and after upgrade. This will ensure that all uplinks/downlinks come back up, as well as provide informational logging if certain devices don't come back up (e.g. VoIP phones, access points).
**6. VLANs**
- Pull all current VLANs. Ensures all VLANs still exist.
**7. Voice VLAN device IP address**
- Ping IP address (e.g. VoIP phone) to test Voice VLAN connectivity before and after. A VoIP phone is reliably pingable.
**8. Wireless VLAN device IP address**
- Ping IP address (e.g. access point) to test wireless VLAN connectivity before and after. An access point is reliably pingable.
**9. Reboot switch stack**
- This is currently implemented by a system call to `swITch.py` program, to issue the 'reload' command.
- There does not seem to be a CPI api call to reload a device. Maybe i'm missing something?
...
Perform everything again in the same order, comparing as necessary
| non_priority | design for code upgrade verification function the basic idea behind the code upgrade method is to pull the before state of a switch reload the switch to initiate the code upgrade then pull the after state of the switch coimpare the two states to ensure nothing is broken this upgrade procedure can be scaled up by having concurrent processes the proposed design is outlined below it is currently partly implemented cpi stands for cisco prime infrastructure verify switch is reachable cpi is slow to report unreachable state min current test relies on a system ping call would prefer an all cpi or python solution possibly craft icmp echo requests directly device sync with cpi ensures cpi has current switch state information this is done with a post api call it seems cpi only stores cdp neighbour info on device added or device sync which is on a timer something like once a day too slow for our needs current code version this is grabbed to be able to compare before and after code versions being reported ensure code was actually upgraded stack members pull all stack members part of the stack to compare before and after to ensure all switches exist based on testing if a switch is powered off the switch is not listed if the switch is provisioned but in an error state e g os mismatch or v mismatch then the switch is shown as provisioned only with certain details missing serial number etc cdp neighbours pull all cdp neighbours being reported to compare before and after upgrade this will ensure that all uplinks downlinks come back up as well as provide informational logging if certain devices don t come back up e g voip phones access points vlans pull all current vlans ensures all vlans still exist voice vlan device ip address ping ip address e g voip phone to test voice vlan connectivity before and after a voip phone is reliably pingable wireless vlan device ip address ping ip address e g access point to test wireless vlan connectivity before and after an access point is reliably pingable reboot switch stack this is currently implemented by a system call to switch py program to issue the reload command there does not seem to be a cpi api call to reload a device maybe i m missing something perform everything again in the same order comparing as necessary | 0 |
96,772 | 10,962,758,623 | IssuesEvent | 2019-11-27 17:59:43 | PixiesUPB/PixiesUPB | https://api.github.com/repos/PixiesUPB/PixiesUPB | closed | Actualización de Scrum - Sprint 1 | documentation primera-parte size:S sprint-1 | ## Historia de Usuario
Como equipo queremos actualizar el scrum con las recomendaciones del docente para poder presentar un buen proyecto.
## Criterio de aceptación
- [ ] Actualizar Scrum | 1.0 | Actualización de Scrum - Sprint 1 - ## Historia de Usuario
Como equipo queremos actualizar el scrum con las recomendaciones del docente para poder presentar un buen proyecto.
## Criterio de aceptación
- [ ] Actualizar Scrum | non_priority | actualización de scrum sprint historia de usuario como equipo queremos actualizar el scrum con las recomendaciones del docente para poder presentar un buen proyecto criterio de aceptación actualizar scrum | 0 |
49,224 | 6,159,494,507 | IssuesEvent | 2017-06-29 00:33:30 | aspnet/Razor | https://api.github.com/repos/aspnet/Razor | closed | Razor code background looks wrong with Dark Theme | by design | **Update**
Guess what, I switched back to Light theme and it looks like it does the same thing, so I assume this is by design ;) Feel free to close then if that is the case.
This is how it looks like in Dark Theme. You can notice the gray background of the font. In a standard C# editor the background of the font and the editor blend together, but not in HTML.

Looking at the color/font options we can see that the "Default" color is selected for the background for , like all other

However this Default is rgb(80,80,80) whereas all others are rgb(30, 30, 30) like the Dark Theme background. Changing to a custom color works fine though.
It looks like this setting should take the value from the theme instead.
This is what it looks like when "fixed", much better IMO

| 1.0 | Razor code background looks wrong with Dark Theme - **Update**
Guess what, I switched back to Light theme and it looks like it does the same thing, so I assume this is by design ;) Feel free to close then if that is the case.
This is how it looks like in Dark Theme. You can notice the gray background of the font. In a standard C# editor the background of the font and the editor blend together, but not in HTML.

Looking at the color/font options we can see that the "Default" color is selected for the background for , like all other

However this Default is rgb(80,80,80) whereas all others are rgb(30, 30, 30) like the Dark Theme background. Changing to a custom color works fine though.
It looks like this setting should take the value from the theme instead.
This is what it looks like when "fixed", much better IMO

| non_priority | razor code background looks wrong with dark theme update guess what i switched back to light theme and it looks like it does the same thing so i assume this is by design feel free to close then if that is the case this is how it looks like in dark theme you can notice the gray background of the font in a standard c editor the background of the font and the editor blend together but not in html looking at the color font options we can see that the default color is selected for the background for like all other however this default is rgb whereas all others are rgb like the dark theme background changing to a custom color works fine though it looks like this setting should take the value from the theme instead this is what it looks like when fixed much better imo | 0 |
67,778 | 21,154,194,372 | IssuesEvent | 2022-04-07 00:05:41 | jccastillo0007/eFacturaT | https://api.github.com/repos/jccastillo0007/eFacturaT | opened | Permitir cancelar los CFDI 3.3 | bug defect | Se require cancelar los CFDI 3.3, todavía por un buen rato.
Esto se validó en su momento y jalaba.
No se que pasó. | 1.0 | Permitir cancelar los CFDI 3.3 - Se require cancelar los CFDI 3.3, todavía por un buen rato.
Esto se validó en su momento y jalaba.
No se que pasó. | non_priority | permitir cancelar los cfdi se require cancelar los cfdi todavía por un buen rato esto se validó en su momento y jalaba no se que pasó | 0 |
94,489 | 15,962,386,757 | IssuesEvent | 2021-04-16 01:12:41 | RG4421/cbp-theme | https://api.github.com/repos/RG4421/cbp-theme | opened | CVE-2020-15366 (Medium) detected in multiple libraries | security vulnerability | ## CVE-2020-15366 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>ajv-6.12.0.tgz</b>, <b>ajv-6.10.0.tgz</b>, <b>ajv-4.11.8.tgz</b>, <b>ajv-6.11.0.tgz</b>, <b>ajv-6.5.3.tgz</b>, <b>ajv-5.5.2.tgz</b></p></summary>
<p>
<details><summary><b>ajv-6.12.0.tgz</b></p></summary>
<p>Another JSON Schema Validator</p>
<p>Library home page: <a href="https://registry.npmjs.org/ajv/-/ajv-6.12.0.tgz">https://registry.npmjs.org/ajv/-/ajv-6.12.0.tgz</a></p>
<p>Path to dependency file: cbp-theme/ds-ux-guidelines/package.json</p>
<p>Path to vulnerable library: cbp-theme/ds-ux-guidelines/node_modules/schema-utils/node_modules/ajv/package.json,cbp-theme/ds-css/node_modules/ajv/package.json</p>
<p>
Dependency Hierarchy:
- webpack-4.42.1.tgz (Root Library)
- :x: **ajv-6.12.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>ajv-6.10.0.tgz</b></p></summary>
<p>Another JSON Schema Validator</p>
<p>Library home page: <a href="https://registry.npmjs.org/ajv/-/ajv-6.10.0.tgz">https://registry.npmjs.org/ajv/-/ajv-6.10.0.tgz</a></p>
<p>Path to dependency file: cbp-theme/cbp-theme/package.json</p>
<p>Path to vulnerable library: cbp-theme/cbp-theme/node_modules/har-validator/node_modules/ajv/package.json,cbp-theme/node_modules/har-validator/node_modules/ajv/package.json</p>
<p>
Dependency Hierarchy:
- node-sass-4.11.0.tgz (Root Library)
- request-2.88.0.tgz
- har-validator-5.1.3.tgz
- :x: **ajv-6.10.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>ajv-4.11.8.tgz</b></p></summary>
<p>Another JSON Schema Validator</p>
<p>Library home page: <a href="https://registry.npmjs.org/ajv/-/ajv-4.11.8.tgz">https://registry.npmjs.org/ajv/-/ajv-4.11.8.tgz</a></p>
<p>Path to dependency file: cbp-theme/cbp-theme/package.json</p>
<p>Path to vulnerable library: cbp-theme/cbp-theme/node_modules/standard/node_modules/ajv/package.json</p>
<p>
Dependency Hierarchy:
- standard-10.0.3.tgz (Root Library)
- eslint-3.19.0.tgz
- table-3.8.3.tgz
- :x: **ajv-4.11.8.tgz** (Vulnerable Library)
</details>
<details><summary><b>ajv-6.11.0.tgz</b></p></summary>
<p>Another JSON Schema Validator</p>
<p>Library home page: <a href="https://registry.npmjs.org/ajv/-/ajv-6.11.0.tgz">https://registry.npmjs.org/ajv/-/ajv-6.11.0.tgz</a></p>
<p>Path to dependency file: cbp-theme/ds-ux-guidelines/package.json</p>
<p>Path to vulnerable library: cbp-theme/ds-ux-guidelines/node_modules/ajv/package.json</p>
<p>
Dependency Hierarchy:
- gatsby-2.20.10.tgz (Root Library)
- eslint-6.8.0.tgz
- :x: **ajv-6.11.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>ajv-6.5.3.tgz</b></p></summary>
<p>Another JSON Schema Validator</p>
<p>Library home page: <a href="https://registry.npmjs.org/ajv/-/ajv-6.5.3.tgz">https://registry.npmjs.org/ajv/-/ajv-6.5.3.tgz</a></p>
<p>Path to dependency file: cbp-theme/package.json</p>
<p>Path to vulnerable library: cbp-theme/node_modules/serve/node_modules/ajv/package.json</p>
<p>
Dependency Hierarchy:
- serve-11.2.0.tgz (Root Library)
- :x: **ajv-6.5.3.tgz** (Vulnerable Library)
</details>
<details><summary><b>ajv-5.5.2.tgz</b></p></summary>
<p>Another JSON Schema Validator</p>
<p>Library home page: <a href="https://registry.npmjs.org/ajv/-/ajv-5.5.2.tgz">https://registry.npmjs.org/ajv/-/ajv-5.5.2.tgz</a></p>
<p>Path to dependency file: cbp-theme/cbp-theme/package.json</p>
<p>Path to vulnerable library: cbp-theme/cbp-theme/node_modules/ajv/package.json</p>
<p>
Dependency Hierarchy:
- eslint-4.19.1.tgz (Root Library)
- :x: **ajv-5.5.2.tgz** (Vulnerable Library)
</details>
<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>
An issue was discovered in ajv.validate() in Ajv (aka Another JSON Schema Validator) 6.12.2. A carefully crafted JSON schema could be provided that allows execution of other code by prototype pollution. (While untrusted schemas are recommended against, the worst case of an untrusted schema should be a denial of service, not execution of code.)
<p>Publish Date: 2020-07-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15366>CVE-2020-15366</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/ajv-validator/ajv/releases/tag/v6.12.3">https://github.com/ajv-validator/ajv/releases/tag/v6.12.3</a></p>
<p>Release Date: 2020-07-15</p>
<p>Fix Resolution: ajv - 6.12.3</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"ajv","packageVersion":"6.12.0","packageFilePaths":["/ds-ux-guidelines/package.json","/ds-css/package.json"],"isTransitiveDependency":true,"dependencyTree":"webpack:4.42.1;ajv:6.12.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"ajv - 6.12.3"},{"packageType":"javascript/Node.js","packageName":"ajv","packageVersion":"6.10.0","packageFilePaths":["/cbp-theme/package.json","/package.json"],"isTransitiveDependency":true,"dependencyTree":"node-sass:4.11.0;request:2.88.0;har-validator:5.1.3;ajv:6.10.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"ajv - 6.12.3"},{"packageType":"javascript/Node.js","packageName":"ajv","packageVersion":"4.11.8","packageFilePaths":["/cbp-theme/package.json"],"isTransitiveDependency":true,"dependencyTree":"standard:10.0.3;eslint:3.19.0;table:3.8.3;ajv:4.11.8","isMinimumFixVersionAvailable":true,"minimumFixVersion":"ajv - 6.12.3"},{"packageType":"javascript/Node.js","packageName":"ajv","packageVersion":"6.11.0","packageFilePaths":["/ds-ux-guidelines/package.json"],"isTransitiveDependency":true,"dependencyTree":"gatsby:2.20.10;eslint:6.8.0;ajv:6.11.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"ajv - 6.12.3"},{"packageType":"javascript/Node.js","packageName":"ajv","packageVersion":"6.5.3","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"serve:11.2.0;ajv:6.5.3","isMinimumFixVersionAvailable":true,"minimumFixVersion":"ajv - 6.12.3"},{"packageType":"javascript/Node.js","packageName":"ajv","packageVersion":"5.5.2","packageFilePaths":["/cbp-theme/package.json"],"isTransitiveDependency":true,"dependencyTree":"eslint:4.19.1;ajv:5.5.2","isMinimumFixVersionAvailable":true,"minimumFixVersion":"ajv - 6.12.3"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-15366","vulnerabilityDetails":"An issue was discovered in ajv.validate() in Ajv (aka Another JSON Schema Validator) 6.12.2. A carefully crafted JSON schema could be provided that allows execution of other code by prototype pollution. (While untrusted schemas are recommended against, the worst case of an untrusted schema should be a denial of service, not execution of code.)","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15366","cvss3Severity":"medium","cvss3Score":"5.6","cvss3Metrics":{"A":"Low","AC":"High","PR":"None","S":"Unchanged","C":"Low","UI":"None","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | True | CVE-2020-15366 (Medium) detected in multiple libraries - ## CVE-2020-15366 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>ajv-6.12.0.tgz</b>, <b>ajv-6.10.0.tgz</b>, <b>ajv-4.11.8.tgz</b>, <b>ajv-6.11.0.tgz</b>, <b>ajv-6.5.3.tgz</b>, <b>ajv-5.5.2.tgz</b></p></summary>
<p>
<details><summary><b>ajv-6.12.0.tgz</b></p></summary>
<p>Another JSON Schema Validator</p>
<p>Library home page: <a href="https://registry.npmjs.org/ajv/-/ajv-6.12.0.tgz">https://registry.npmjs.org/ajv/-/ajv-6.12.0.tgz</a></p>
<p>Path to dependency file: cbp-theme/ds-ux-guidelines/package.json</p>
<p>Path to vulnerable library: cbp-theme/ds-ux-guidelines/node_modules/schema-utils/node_modules/ajv/package.json,cbp-theme/ds-css/node_modules/ajv/package.json</p>
<p>
Dependency Hierarchy:
- webpack-4.42.1.tgz (Root Library)
- :x: **ajv-6.12.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>ajv-6.10.0.tgz</b></p></summary>
<p>Another JSON Schema Validator</p>
<p>Library home page: <a href="https://registry.npmjs.org/ajv/-/ajv-6.10.0.tgz">https://registry.npmjs.org/ajv/-/ajv-6.10.0.tgz</a></p>
<p>Path to dependency file: cbp-theme/cbp-theme/package.json</p>
<p>Path to vulnerable library: cbp-theme/cbp-theme/node_modules/har-validator/node_modules/ajv/package.json,cbp-theme/node_modules/har-validator/node_modules/ajv/package.json</p>
<p>
Dependency Hierarchy:
- node-sass-4.11.0.tgz (Root Library)
- request-2.88.0.tgz
- har-validator-5.1.3.tgz
- :x: **ajv-6.10.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>ajv-4.11.8.tgz</b></p></summary>
<p>Another JSON Schema Validator</p>
<p>Library home page: <a href="https://registry.npmjs.org/ajv/-/ajv-4.11.8.tgz">https://registry.npmjs.org/ajv/-/ajv-4.11.8.tgz</a></p>
<p>Path to dependency file: cbp-theme/cbp-theme/package.json</p>
<p>Path to vulnerable library: cbp-theme/cbp-theme/node_modules/standard/node_modules/ajv/package.json</p>
<p>
Dependency Hierarchy:
- standard-10.0.3.tgz (Root Library)
- eslint-3.19.0.tgz
- table-3.8.3.tgz
- :x: **ajv-4.11.8.tgz** (Vulnerable Library)
</details>
<details><summary><b>ajv-6.11.0.tgz</b></p></summary>
<p>Another JSON Schema Validator</p>
<p>Library home page: <a href="https://registry.npmjs.org/ajv/-/ajv-6.11.0.tgz">https://registry.npmjs.org/ajv/-/ajv-6.11.0.tgz</a></p>
<p>Path to dependency file: cbp-theme/ds-ux-guidelines/package.json</p>
<p>Path to vulnerable library: cbp-theme/ds-ux-guidelines/node_modules/ajv/package.json</p>
<p>
Dependency Hierarchy:
- gatsby-2.20.10.tgz (Root Library)
- eslint-6.8.0.tgz
- :x: **ajv-6.11.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>ajv-6.5.3.tgz</b></p></summary>
<p>Another JSON Schema Validator</p>
<p>Library home page: <a href="https://registry.npmjs.org/ajv/-/ajv-6.5.3.tgz">https://registry.npmjs.org/ajv/-/ajv-6.5.3.tgz</a></p>
<p>Path to dependency file: cbp-theme/package.json</p>
<p>Path to vulnerable library: cbp-theme/node_modules/serve/node_modules/ajv/package.json</p>
<p>
Dependency Hierarchy:
- serve-11.2.0.tgz (Root Library)
- :x: **ajv-6.5.3.tgz** (Vulnerable Library)
</details>
<details><summary><b>ajv-5.5.2.tgz</b></p></summary>
<p>Another JSON Schema Validator</p>
<p>Library home page: <a href="https://registry.npmjs.org/ajv/-/ajv-5.5.2.tgz">https://registry.npmjs.org/ajv/-/ajv-5.5.2.tgz</a></p>
<p>Path to dependency file: cbp-theme/cbp-theme/package.json</p>
<p>Path to vulnerable library: cbp-theme/cbp-theme/node_modules/ajv/package.json</p>
<p>
Dependency Hierarchy:
- eslint-4.19.1.tgz (Root Library)
- :x: **ajv-5.5.2.tgz** (Vulnerable Library)
</details>
<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>
An issue was discovered in ajv.validate() in Ajv (aka Another JSON Schema Validator) 6.12.2. A carefully crafted JSON schema could be provided that allows execution of other code by prototype pollution. (While untrusted schemas are recommended against, the worst case of an untrusted schema should be a denial of service, not execution of code.)
<p>Publish Date: 2020-07-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15366>CVE-2020-15366</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/ajv-validator/ajv/releases/tag/v6.12.3">https://github.com/ajv-validator/ajv/releases/tag/v6.12.3</a></p>
<p>Release Date: 2020-07-15</p>
<p>Fix Resolution: ajv - 6.12.3</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"ajv","packageVersion":"6.12.0","packageFilePaths":["/ds-ux-guidelines/package.json","/ds-css/package.json"],"isTransitiveDependency":true,"dependencyTree":"webpack:4.42.1;ajv:6.12.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"ajv - 6.12.3"},{"packageType":"javascript/Node.js","packageName":"ajv","packageVersion":"6.10.0","packageFilePaths":["/cbp-theme/package.json","/package.json"],"isTransitiveDependency":true,"dependencyTree":"node-sass:4.11.0;request:2.88.0;har-validator:5.1.3;ajv:6.10.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"ajv - 6.12.3"},{"packageType":"javascript/Node.js","packageName":"ajv","packageVersion":"4.11.8","packageFilePaths":["/cbp-theme/package.json"],"isTransitiveDependency":true,"dependencyTree":"standard:10.0.3;eslint:3.19.0;table:3.8.3;ajv:4.11.8","isMinimumFixVersionAvailable":true,"minimumFixVersion":"ajv - 6.12.3"},{"packageType":"javascript/Node.js","packageName":"ajv","packageVersion":"6.11.0","packageFilePaths":["/ds-ux-guidelines/package.json"],"isTransitiveDependency":true,"dependencyTree":"gatsby:2.20.10;eslint:6.8.0;ajv:6.11.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"ajv - 6.12.3"},{"packageType":"javascript/Node.js","packageName":"ajv","packageVersion":"6.5.3","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"serve:11.2.0;ajv:6.5.3","isMinimumFixVersionAvailable":true,"minimumFixVersion":"ajv - 6.12.3"},{"packageType":"javascript/Node.js","packageName":"ajv","packageVersion":"5.5.2","packageFilePaths":["/cbp-theme/package.json"],"isTransitiveDependency":true,"dependencyTree":"eslint:4.19.1;ajv:5.5.2","isMinimumFixVersionAvailable":true,"minimumFixVersion":"ajv - 6.12.3"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-15366","vulnerabilityDetails":"An issue was discovered in ajv.validate() in Ajv (aka Another JSON Schema Validator) 6.12.2. A carefully crafted JSON schema could be provided that allows execution of other code by prototype pollution. (While untrusted schemas are recommended against, the worst case of an untrusted schema should be a denial of service, not execution of code.)","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15366","cvss3Severity":"medium","cvss3Score":"5.6","cvss3Metrics":{"A":"Low","AC":"High","PR":"None","S":"Unchanged","C":"Low","UI":"None","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | non_priority | cve medium detected in multiple libraries cve medium severity vulnerability vulnerable libraries ajv tgz ajv tgz ajv tgz ajv tgz ajv tgz ajv tgz ajv tgz another json schema validator library home page a href path to dependency file cbp theme ds ux guidelines package json path to vulnerable library cbp theme ds ux guidelines node modules schema utils node modules ajv package json cbp theme ds css node modules ajv package json dependency hierarchy webpack tgz root library x ajv tgz vulnerable library ajv tgz another json schema validator library home page a href path to dependency file cbp theme cbp theme package json path to vulnerable library cbp theme cbp theme node modules har validator node modules ajv package json cbp theme node modules har validator node modules ajv package json dependency hierarchy node sass tgz root library request tgz har validator tgz x ajv tgz vulnerable library ajv tgz another json schema validator library home page a href path to dependency file cbp theme cbp theme package json path to vulnerable library cbp theme cbp theme node modules standard node modules ajv package json dependency hierarchy standard tgz root library eslint tgz table tgz x ajv tgz vulnerable library ajv tgz another json schema validator library home page a href path to dependency file cbp theme ds ux guidelines package json path to vulnerable library cbp theme ds ux guidelines node modules ajv package json dependency hierarchy gatsby tgz root library eslint tgz x ajv tgz vulnerable library ajv tgz another json schema validator library home page a href path to dependency file cbp theme package json path to vulnerable library cbp theme node modules serve node modules ajv package json dependency hierarchy serve tgz root library x ajv tgz vulnerable library ajv tgz another json schema validator library home page a href path to dependency file cbp theme cbp theme package json path to vulnerable library cbp theme cbp theme node modules ajv package json dependency hierarchy eslint tgz root library x ajv tgz vulnerable library found in base branch master vulnerability details an issue was discovered in ajv validate in ajv aka another json schema validator a carefully crafted json schema could be provided that allows execution of other code by prototype pollution while untrusted schemas are recommended against the worst case of an untrusted schema should be a denial of service not execution of code 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 low integrity impact low availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution ajv isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree webpack ajv isminimumfixversionavailable true minimumfixversion ajv packagetype javascript node js packagename ajv packageversion packagefilepaths istransitivedependency true dependencytree node sass request har validator ajv isminimumfixversionavailable true minimumfixversion ajv packagetype javascript node js packagename ajv packageversion packagefilepaths istransitivedependency true dependencytree standard eslint table ajv isminimumfixversionavailable true minimumfixversion ajv packagetype javascript node js packagename ajv packageversion packagefilepaths istransitivedependency true dependencytree gatsby eslint ajv isminimumfixversionavailable true minimumfixversion ajv packagetype javascript node js packagename ajv packageversion packagefilepaths istransitivedependency true dependencytree serve ajv isminimumfixversionavailable true minimumfixversion ajv packagetype javascript node js packagename ajv packageversion packagefilepaths istransitivedependency true dependencytree eslint ajv isminimumfixversionavailable true minimumfixversion ajv basebranches vulnerabilityidentifier cve vulnerabilitydetails an issue was discovered in ajv validate in ajv aka another json schema validator a carefully crafted json schema could be provided that allows execution of other code by prototype pollution while untrusted schemas are recommended against the worst case of an untrusted schema should be a denial of service not execution of code vulnerabilityurl | 0 |
267,802 | 28,509,229,850 | IssuesEvent | 2023-04-19 01:46:43 | dpteam/RK3188_TABLET | https://api.github.com/repos/dpteam/RK3188_TABLET | closed | CVE-2017-7645 (High) detected in linuxv3.0, linux-yocto-4.12v3.0.66 - autoclosed | Mend: dependency security vulnerability | ## CVE-2017-7645 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>linuxv3.0</b>, <b>linux-yocto-4.12v3.0.66</b></p></summary>
<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 NFSv2/NFSv3 server in the nfsd subsystem in the Linux kernel through 4.10.11 allows remote attackers to cause a denial of service (system crash) via a long RPC reply, related to net/sunrpc/svc.c, fs/nfsd/nfs3xdr.c, and fs/nfsd/nfsxdr.c.
<p>Publish Date: 2017-04-18
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-7645>CVE-2017-7645</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-7645">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-7645</a></p>
<p>Release Date: 2017-04-18</p>
<p>Fix Resolution: v4.11</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-7645 (High) detected in linuxv3.0, linux-yocto-4.12v3.0.66 - autoclosed - ## CVE-2017-7645 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>linuxv3.0</b>, <b>linux-yocto-4.12v3.0.66</b></p></summary>
<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 NFSv2/NFSv3 server in the nfsd subsystem in the Linux kernel through 4.10.11 allows remote attackers to cause a denial of service (system crash) via a long RPC reply, related to net/sunrpc/svc.c, fs/nfsd/nfs3xdr.c, and fs/nfsd/nfsxdr.c.
<p>Publish Date: 2017-04-18
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-7645>CVE-2017-7645</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-7645">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-7645</a></p>
<p>Release Date: 2017-04-18</p>
<p>Fix Resolution: v4.11</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in linux yocto autoclosed cve high severity vulnerability vulnerable libraries linux yocto vulnerability details the server in the nfsd subsystem in the linux kernel through allows remote attackers to cause a denial of service system crash via a long rpc reply related to net sunrpc svc c fs nfsd c and fs nfsd nfsxdr c publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend | 0 |
336,316 | 30,187,298,649 | IssuesEvent | 2023-07-04 12:59:01 | Young-Child/FanFollow | https://api.github.com/repos/Young-Child/FanFollow | opened | [TEST] Default Chat Service Test 코드 작성 | test | ### Description
Chat 서비스에 대한 테스트 코드 작성
### Edge Case (추후 추가 예정)
- [ ] case1
- [ ] case2
### ToDo
- [ ] Mock 데이터 생성
- [ ] Default Chat Service에 대한 테스트 케이스 생성
- [ ] 테스트 코드 작성
| 1.0 | [TEST] Default Chat Service Test 코드 작성 - ### Description
Chat 서비스에 대한 테스트 코드 작성
### Edge Case (추후 추가 예정)
- [ ] case1
- [ ] case2
### ToDo
- [ ] Mock 데이터 생성
- [ ] Default Chat Service에 대한 테스트 케이스 생성
- [ ] 테스트 코드 작성
| non_priority | default chat service test 코드 작성 description chat 서비스에 대한 테스트 코드 작성 edge case 추후 추가 예정 todo mock 데이터 생성 default chat service에 대한 테스트 케이스 생성 테스트 코드 작성 | 0 |
75,137 | 9,819,802,821 | IssuesEvent | 2019-06-13 23:27:37 | uswds/uswds-site | https://api.github.com/repos/uswds/uswds-site | closed | Some links in developer docs redirect to the wrong url | Help wanted [Skill] Documentation [Type] Bug | ## Description
Under the "Customization, Theming, and Tokens" section in the developer docs, the links that are supposed to redirect to pages in "Design tokens" instead try to go to a nonexistent "Style tokens" section. These links end up in a 404 page.
## Steps to reproduce the issue
1. Go to the ["Customization, Theming, and Tokens" section](https://v2.designsystem.digital.gov/documentation/developers/#customization-theming-and-tokens) of the [developer docs](https://v2.designsystem.digital.gov/documentation/developers)
2. Clicking the links "Style tokens section", "color", "spacing units", and "typescale" try to go to their pages (supposed to be located at "...digital.gov/**design-tokens**/[page name]") but go to "...digital.gov/**style**/[page name]" and end up in a 404 page instead. | 1.0 | Some links in developer docs redirect to the wrong url - ## Description
Under the "Customization, Theming, and Tokens" section in the developer docs, the links that are supposed to redirect to pages in "Design tokens" instead try to go to a nonexistent "Style tokens" section. These links end up in a 404 page.
## Steps to reproduce the issue
1. Go to the ["Customization, Theming, and Tokens" section](https://v2.designsystem.digital.gov/documentation/developers/#customization-theming-and-tokens) of the [developer docs](https://v2.designsystem.digital.gov/documentation/developers)
2. Clicking the links "Style tokens section", "color", "spacing units", and "typescale" try to go to their pages (supposed to be located at "...digital.gov/**design-tokens**/[page name]") but go to "...digital.gov/**style**/[page name]" and end up in a 404 page instead. | non_priority | some links in developer docs redirect to the wrong url description under the customization theming and tokens section in the developer docs the links that are supposed to redirect to pages in design tokens instead try to go to a nonexistent style tokens section these links end up in a page steps to reproduce the issue go to the of the clicking the links style tokens section color spacing units and typescale try to go to their pages supposed to be located at digital gov design tokens but go to digital gov style and end up in a page instead | 0 |
1,634 | 17,795,510,806 | IssuesEvent | 2021-08-31 21:34:43 | hashicorp/consul | https://api.github.com/repos/hashicorp/consul | opened | Server should report when they are not fully initialized | theme/reliability | Related to #10967
When a server starts, it starts accepting connections (HTTP, DNS, RPC) before it is ready to handle them. The server must connect to other servers, and may need to receive a snapshot or logs from them. Then it has to populate the FSM from that snapshot. This can take some time when the snapshot is large.
Either servers should not accept connections until they are initialized, or they should report a specific error, so that clients know they need to communicate with a different server. | True | Server should report when they are not fully initialized - Related to #10967
When a server starts, it starts accepting connections (HTTP, DNS, RPC) before it is ready to handle them. The server must connect to other servers, and may need to receive a snapshot or logs from them. Then it has to populate the FSM from that snapshot. This can take some time when the snapshot is large.
Either servers should not accept connections until they are initialized, or they should report a specific error, so that clients know they need to communicate with a different server. | non_priority | server should report when they are not fully initialized related to when a server starts it starts accepting connections http dns rpc before it is ready to handle them the server must connect to other servers and may need to receive a snapshot or logs from them then it has to populate the fsm from that snapshot this can take some time when the snapshot is large either servers should not accept connections until they are initialized or they should report a specific error so that clients know they need to communicate with a different server | 0 |
47,406 | 19,634,886,123 | IssuesEvent | 2022-01-08 04:44:46 | Seneca-CDOT/telescope | https://api.github.com/repos/Seneca-CDOT/telescope | closed | Create a Stats microservice | type: enhancement area: back-end area: docker area: microservices | Create a microservice to deliver stats related to Telescope's users and posts.
There's already code in the repo for this task, so it only needs to be part of a microservice.
**NOTE**
This piece will have to be tested against the current backend until the `Post` microservice is ready.
| 1.0 | Create a Stats microservice - Create a microservice to deliver stats related to Telescope's users and posts.
There's already code in the repo for this task, so it only needs to be part of a microservice.
**NOTE**
This piece will have to be tested against the current backend until the `Post` microservice is ready.
| non_priority | create a stats microservice create a microservice to deliver stats related to telescope s users and posts there s already code in the repo for this task so it only needs to be part of a microservice note this piece will have to be tested against the current backend until the post microservice is ready | 0 |
250,824 | 21,337,932,604 | IssuesEvent | 2022-04-18 16:44:12 | JohnFTitor/catalog-of-stuff | https://api.github.com/repos/JohnFTitor/catalog-of-stuff | opened | [1pt] Define Schema.sql tables for Books | test create feature | ## Define Schema.sql tables for Books
- Create a schema.sql file with tables that will be analogical to the structure of the classes that you created:
- books table (add all properties and associations from the parent Item class as table columns)
- labels table
| 1.0 | [1pt] Define Schema.sql tables for Books - ## Define Schema.sql tables for Books
- Create a schema.sql file with tables that will be analogical to the structure of the classes that you created:
- books table (add all properties and associations from the parent Item class as table columns)
- labels table
| non_priority | define schema sql tables for books define schema sql tables for books create a schema sql file with tables that will be analogical to the structure of the classes that you created books table add all properties and associations from the parent item class as table columns labels table | 0 |
376,955 | 26,225,332,842 | IssuesEvent | 2023-01-04 18:08:20 | novelrt/NovelRT | https://api.github.com/repos/novelrt/NovelRT | opened | CMake Dependency needs updating due to use of VS Generator | bug cmake documentation | **Describe the issue:**
When attempting to build NovelRT on Windows 10 or 11 with Visual Studio 2022 installed, CMake versions 3.19 and 3.20 will fail using the default settings with the following error: "CMake Error: Could not create named generator Visual Studio 17 2022"
This appears to occur when using Visual Studio Code, however it can happen with other IDEs if not using Ninja or Unix Makefiles by default.
**Please provide the steps to reproduce if possible:**
1. Clone the repo
2. Open Visual Studio Code (configured with CMake Tools / C++ Support enabled)
3. Run the default configure command
4. See error
**Expected behaviour:**
The CMake version dependency should be updated to 3.21 in readme, Wiki, and the root CMakeLists.txt.
**Please tell us about your environment:**
- OS Version: Windows 11 22H2
_If building from source_:
- Compiler Version: Visual Studio 2022 v17.4.3
- IDE: Visual Studio Code, C/C++ (Microsoft) extension installed
- Git fork/branch URL: N/A, using main branch
**Additional context:**
It seems to be failing at the command level, before the CMakeLists.txt file is even processed.
| 1.0 | CMake Dependency needs updating due to use of VS Generator - **Describe the issue:**
When attempting to build NovelRT on Windows 10 or 11 with Visual Studio 2022 installed, CMake versions 3.19 and 3.20 will fail using the default settings with the following error: "CMake Error: Could not create named generator Visual Studio 17 2022"
This appears to occur when using Visual Studio Code, however it can happen with other IDEs if not using Ninja or Unix Makefiles by default.
**Please provide the steps to reproduce if possible:**
1. Clone the repo
2. Open Visual Studio Code (configured with CMake Tools / C++ Support enabled)
3. Run the default configure command
4. See error
**Expected behaviour:**
The CMake version dependency should be updated to 3.21 in readme, Wiki, and the root CMakeLists.txt.
**Please tell us about your environment:**
- OS Version: Windows 11 22H2
_If building from source_:
- Compiler Version: Visual Studio 2022 v17.4.3
- IDE: Visual Studio Code, C/C++ (Microsoft) extension installed
- Git fork/branch URL: N/A, using main branch
**Additional context:**
It seems to be failing at the command level, before the CMakeLists.txt file is even processed.
| non_priority | cmake dependency needs updating due to use of vs generator describe the issue when attempting to build novelrt on windows or with visual studio installed cmake versions and will fail using the default settings with the following error cmake error could not create named generator visual studio this appears to occur when using visual studio code however it can happen with other ides if not using ninja or unix makefiles by default please provide the steps to reproduce if possible clone the repo open visual studio code configured with cmake tools c support enabled run the default configure command see error expected behaviour the cmake version dependency should be updated to in readme wiki and the root cmakelists txt please tell us about your environment os version windows if building from source compiler version visual studio ide visual studio code c c microsoft extension installed git fork branch url n a using main branch additional context it seems to be failing at the command level before the cmakelists txt file is even processed | 0 |
114,037 | 11,835,565,136 | IssuesEvent | 2020-03-23 10:52:10 | TocappGames/game2d | https://api.github.com/repos/TocappGames/game2d | opened | add documentation | documentation | missing hello-world documentation and examples for android, wearos and watch faces | 1.0 | add documentation - missing hello-world documentation and examples for android, wearos and watch faces | non_priority | add documentation missing hello world documentation and examples for android wearos and watch faces | 0 |
59,048 | 24,639,239,215 | IssuesEvent | 2022-10-17 10:17:35 | CS3219-AY2223S1/cs3219-project-ay2223s1-g12 | https://api.github.com/repos/CS3219-AY2223S1/cs3219-project-ay2223s1-g12 | opened | Certain routes in matching-service should only be accessible by logged in users | bug matching-service user-service | Routes that require protection:
* `selectquestiondifficulty`
* `roompage` | 2.0 | Certain routes in matching-service should only be accessible by logged in users - Routes that require protection:
* `selectquestiondifficulty`
* `roompage` | non_priority | certain routes in matching service should only be accessible by logged in users routes that require protection selectquestiondifficulty roompage | 0 |
281,514 | 30,888,875,470 | IssuesEvent | 2023-08-04 01:57:10 | hshivhare67/kernel_v4.1.15_CVE-2019-10220 | https://api.github.com/repos/hshivhare67/kernel_v4.1.15_CVE-2019-10220 | reopened | CVE-2016-2069 (High) detected in linuxlinux-4.4.302 | Mend: dependency security vulnerability | ## CVE-2016-2069 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.4.302</b></p></summary>
<p>
<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in HEAD commit: <a href="https://github.com/hshivhare67/kernel_v4.1.15_CVE-2019-10220/commit/85c655ae4a38840b0edb9284bb64ec65b27331dc">85c655ae4a38840b0edb9284bb64ec65b27331dc</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>
Race condition in arch/x86/mm/tlb.c in the Linux kernel before 4.4.1 allows local users to gain privileges by triggering access to a paging structure by a different CPU.
<p>Publish Date: 2016-04-27
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-2069>CVE-2016-2069</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.4</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- 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://nvd.nist.gov/vuln/detail/CVE-2016-2069">https://nvd.nist.gov/vuln/detail/CVE-2016-2069</a></p>
<p>Release Date: 2016-04-27</p>
<p>Fix Resolution: 4.4.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2016-2069 (High) detected in linuxlinux-4.4.302 - ## CVE-2016-2069 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.4.302</b></p></summary>
<p>
<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in HEAD commit: <a href="https://github.com/hshivhare67/kernel_v4.1.15_CVE-2019-10220/commit/85c655ae4a38840b0edb9284bb64ec65b27331dc">85c655ae4a38840b0edb9284bb64ec65b27331dc</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>
Race condition in arch/x86/mm/tlb.c in the Linux kernel before 4.4.1 allows local users to gain privileges by triggering access to a paging structure by a different CPU.
<p>Publish Date: 2016-04-27
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-2069>CVE-2016-2069</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.4</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- 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://nvd.nist.gov/vuln/detail/CVE-2016-2069">https://nvd.nist.gov/vuln/detail/CVE-2016-2069</a></p>
<p>Release Date: 2016-04-27</p>
<p>Fix Resolution: 4.4.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in linuxlinux cve high severity vulnerability vulnerable library linuxlinux the linux kernel library home page a href found in head commit a href found in base branch master vulnerable source files vulnerability details race condition in arch mm tlb c in the linux kernel before allows local users to gain privileges by triggering access to a paging structure by a different cpu publish date url a href cvss score details base score metrics exploitability metrics attack vector local 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 step up your open source security game with mend | 0 |
135,463 | 18,714,875,970 | IssuesEvent | 2021-11-03 02:14:46 | ChoeMinji/react | https://api.github.com/repos/ChoeMinji/react | opened | CVE-2020-15256 (High) detected in object-path-0.11.4.tgz | security vulnerability | ## CVE-2020-15256 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>object-path-0.11.4.tgz</b></p></summary>
<p>Access deep object properties using a path</p>
<p>Library home page: <a href="https://registry.npmjs.org/object-path/-/object-path-0.11.4.tgz">https://registry.npmjs.org/object-path/-/object-path-0.11.4.tgz</a></p>
<p>Path to dependency file: react/fixtures/blocks/package.json</p>
<p>Path to vulnerable library: react/fixtures/blocks/node_modules/object-path/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-3.4.1.tgz (Root Library)
- resolve-url-loader-3.1.1.tgz
- adjust-sourcemap-loader-2.0.0.tgz
- :x: **object-path-0.11.4.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ChoeMinji/react/commit/cfdac8a3b655e30ad4724d1e0f6910d3ca3c2b5e">cfdac8a3b655e30ad4724d1e0f6910d3ca3c2b5e</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A prototype pollution vulnerability has been found in `object-path` <= 0.11.4 affecting the `set()` method. The vulnerability is limited to the `includeInheritedProps` mode (if version >= 0.11.0 is used), which has to be explicitly enabled by creating a new instance of `object-path` and setting the option `includeInheritedProps: true`, or by using the default `withInheritedProps` instance. The default operating mode is not affected by the vulnerability if version >= 0.11.0 is used. Any usage of `set()` in versions < 0.11.0 is vulnerable. The issue is fixed in object-path version 0.11.5 As a workaround, don't use the `includeInheritedProps: true` options or the `withInheritedProps` instance if using a version >= 0.11.0.
<p>Publish Date: 2020-10-19
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15256>CVE-2020-15256</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/mariocasciaro/object-path/security/advisories/GHSA-cwx2-736x-mf6w">https://github.com/mariocasciaro/object-path/security/advisories/GHSA-cwx2-736x-mf6w</a></p>
<p>Release Date: 2020-07-21</p>
<p>Fix Resolution: 0.11.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-15256 (High) detected in object-path-0.11.4.tgz - ## CVE-2020-15256 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>object-path-0.11.4.tgz</b></p></summary>
<p>Access deep object properties using a path</p>
<p>Library home page: <a href="https://registry.npmjs.org/object-path/-/object-path-0.11.4.tgz">https://registry.npmjs.org/object-path/-/object-path-0.11.4.tgz</a></p>
<p>Path to dependency file: react/fixtures/blocks/package.json</p>
<p>Path to vulnerable library: react/fixtures/blocks/node_modules/object-path/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-3.4.1.tgz (Root Library)
- resolve-url-loader-3.1.1.tgz
- adjust-sourcemap-loader-2.0.0.tgz
- :x: **object-path-0.11.4.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ChoeMinji/react/commit/cfdac8a3b655e30ad4724d1e0f6910d3ca3c2b5e">cfdac8a3b655e30ad4724d1e0f6910d3ca3c2b5e</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A prototype pollution vulnerability has been found in `object-path` <= 0.11.4 affecting the `set()` method. The vulnerability is limited to the `includeInheritedProps` mode (if version >= 0.11.0 is used), which has to be explicitly enabled by creating a new instance of `object-path` and setting the option `includeInheritedProps: true`, or by using the default `withInheritedProps` instance. The default operating mode is not affected by the vulnerability if version >= 0.11.0 is used. Any usage of `set()` in versions < 0.11.0 is vulnerable. The issue is fixed in object-path version 0.11.5 As a workaround, don't use the `includeInheritedProps: true` options or the `withInheritedProps` instance if using a version >= 0.11.0.
<p>Publish Date: 2020-10-19
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15256>CVE-2020-15256</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/mariocasciaro/object-path/security/advisories/GHSA-cwx2-736x-mf6w">https://github.com/mariocasciaro/object-path/security/advisories/GHSA-cwx2-736x-mf6w</a></p>
<p>Release Date: 2020-07-21</p>
<p>Fix Resolution: 0.11.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_priority | cve high detected in object path tgz cve high severity vulnerability vulnerable library object path tgz access deep object properties using a path library home page a href path to dependency file react fixtures blocks package json path to vulnerable library react fixtures blocks node modules object path package json dependency hierarchy react scripts tgz root library resolve url loader tgz adjust sourcemap loader tgz x object path tgz vulnerable library found in head commit a href found in base branch main vulnerability details a prototype pollution vulnerability has been found in object path is used which has to be explicitly enabled by creating a new instance of object path and setting the option includeinheritedprops true or by using the default withinheritedprops instance the default operating mode is not affected by the vulnerability if version is used any usage of set in versions publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
8,671 | 11,802,944,557 | IssuesEvent | 2020-03-18 22:48:59 | hashicorp/packer | https://api.github.com/repos/hashicorp/packer | closed | Packer drops preferred NIC types from Vagrant boxes | bug need-more-info post-processor/vagrant waiting-reply | Vagrant 2.2.2 now warns when some vulnerable NIC drivers are used, such as E1000. I am able to configure a more appropriate NIC at base box build time, with:
```json
"vboxmanage": [
["modifyvm", "{{.Name}}", "--nictype1", "82543GC"]
]
```
However, the Vagrant box produced by this Packer configuration completely forgets about this preference, resulting in the E1000 NIC being used when the box boots.
Can we fix Packer so that NIC types are better preserved in .BOX's?
Note: Vagrant also has a habit of dropping important configurations for further downstream box exports, so users will likely have to manually configure better NIC types there as well, with an `export.Vagrantfile` for use with `--vagrantfile` in `vagrant package`. But we could at least do a better job having Packer artifacts setup the right default configurations, out of the box so to speak. | 1.0 | Packer drops preferred NIC types from Vagrant boxes - Vagrant 2.2.2 now warns when some vulnerable NIC drivers are used, such as E1000. I am able to configure a more appropriate NIC at base box build time, with:
```json
"vboxmanage": [
["modifyvm", "{{.Name}}", "--nictype1", "82543GC"]
]
```
However, the Vagrant box produced by this Packer configuration completely forgets about this preference, resulting in the E1000 NIC being used when the box boots.
Can we fix Packer so that NIC types are better preserved in .BOX's?
Note: Vagrant also has a habit of dropping important configurations for further downstream box exports, so users will likely have to manually configure better NIC types there as well, with an `export.Vagrantfile` for use with `--vagrantfile` in `vagrant package`. But we could at least do a better job having Packer artifacts setup the right default configurations, out of the box so to speak. | non_priority | packer drops preferred nic types from vagrant boxes vagrant now warns when some vulnerable nic drivers are used such as i am able to configure a more appropriate nic at base box build time with json vboxmanage however the vagrant box produced by this packer configuration completely forgets about this preference resulting in the nic being used when the box boots can we fix packer so that nic types are better preserved in box s note vagrant also has a habit of dropping important configurations for further downstream box exports so users will likely have to manually configure better nic types there as well with an export vagrantfile for use with vagrantfile in vagrant package but we could at least do a better job having packer artifacts setup the right default configurations out of the box so to speak | 0 |
137,439 | 18,752,712,873 | IssuesEvent | 2021-11-05 05:53:04 | madhans23/linux-4.15 | https://api.github.com/repos/madhans23/linux-4.15 | opened | CVE-2017-16538 (Medium) detected in wip-kernelv4.15.3-wip-x12 | security vulnerability | ## CVE-2017-16538 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>wip-kernelv4.15.3-wip-x12</b></p></summary>
<p>
<p>WIP Patched Kernel Sources (Linux 4.15.15-wip-x45)</p>
<p>Library home page: <a href=git://git.code.sf.net/p/wip-kernel/code>git://git.code.sf.net/p/wip-kernel/code</a></p>
<p>Found in HEAD commit: <a href="https://github.com/madhans23/linux-4.15/commit/d96ee498864d1a0b6222cfb17d64ca8196014940">d96ee498864d1a0b6222cfb17d64ca8196014940</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/media/usb/dvb-usb-v2/lmedm04.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/media/usb/dvb-usb-v2/lmedm04.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>
drivers/media/usb/dvb-usb-v2/lmedm04.c in the Linux kernel through 4.13.11 allows local users to cause a denial of service (general protection fault and system crash) or possibly have unspecified other impact via a crafted USB device, related to a missing warm-start check and incorrect attach timing (dm04_lme2510_frontend_attach versus dm04_lme2510_tuner).
<p>Publish Date: 2017-11-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16538>CVE-2017-16538</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.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Physical
- 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-16538">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16538</a></p>
<p>Release Date: 2017-11-04</p>
<p>Fix Resolution: v4.15-rc1</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-2017-16538 (Medium) detected in wip-kernelv4.15.3-wip-x12 - ## CVE-2017-16538 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>wip-kernelv4.15.3-wip-x12</b></p></summary>
<p>
<p>WIP Patched Kernel Sources (Linux 4.15.15-wip-x45)</p>
<p>Library home page: <a href=git://git.code.sf.net/p/wip-kernel/code>git://git.code.sf.net/p/wip-kernel/code</a></p>
<p>Found in HEAD commit: <a href="https://github.com/madhans23/linux-4.15/commit/d96ee498864d1a0b6222cfb17d64ca8196014940">d96ee498864d1a0b6222cfb17d64ca8196014940</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/media/usb/dvb-usb-v2/lmedm04.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/media/usb/dvb-usb-v2/lmedm04.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>
drivers/media/usb/dvb-usb-v2/lmedm04.c in the Linux kernel through 4.13.11 allows local users to cause a denial of service (general protection fault and system crash) or possibly have unspecified other impact via a crafted USB device, related to a missing warm-start check and incorrect attach timing (dm04_lme2510_frontend_attach versus dm04_lme2510_tuner).
<p>Publish Date: 2017-11-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16538>CVE-2017-16538</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.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Physical
- 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-16538">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16538</a></p>
<p>Release Date: 2017-11-04</p>
<p>Fix Resolution: v4.15-rc1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in wip wip cve medium severity vulnerability vulnerable library wip wip wip patched kernel sources linux wip library home page git git code sf net p wip kernel code found in head commit a href found in base branch master vulnerable source files drivers media usb dvb usb c drivers media usb dvb usb c vulnerability details drivers media usb dvb usb c in the linux kernel through allows local users to cause a denial of service general protection fault and system crash or possibly have unspecified other impact via a crafted usb device related to a missing warm start check and incorrect attach timing frontend attach versus tuner publish date url a href cvss score details base score metrics exploitability metrics attack vector physical 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 whitesource | 0 |
150,012 | 19,597,949,328 | IssuesEvent | 2022-01-05 20:21:50 | shaimael/PrimeFacesAdminLTE | https://api.github.com/repos/shaimael/PrimeFacesAdminLTE | opened | CVE-2018-14042 (Medium) detected in bootstrap-3.3.4.js, bootstrap-3.3.4.min.js | security vulnerability | ## CVE-2018-14042 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>bootstrap-3.3.4.js</b>, <b>bootstrap-3.3.4.min.js</b></p></summary>
<p>
<details><summary><b>bootstrap-3.3.4.js</b></p></summary>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.4/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.4/js/bootstrap.js</a></p>
<p>Path to vulnerable library: /src/main/webapp/resources/bootstrap/js/bootstrap.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.4.js** (Vulnerable Library)
</details>
<details><summary><b>bootstrap-3.3.4.min.js</b></p></summary>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.4/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.4/js/bootstrap.min.js</a></p>
<p>Path to vulnerable library: /src/main/webapp/resources/bootstrap/js/bootstrap.min.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.4.min.js** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/shaimael/PrimeFacesAdminLTE/commit/89f33d354e9426443883e0ea242503216392aeec">89f33d354e9426443883e0ea242503216392aeec</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 Bootstrap before 4.1.2, XSS is possible in the data-container property of tooltip.
<p>Publish Date: 2018-07-13
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14042>CVE-2018-14042</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/twbs/bootstrap/pull/26630">https://github.com/twbs/bootstrap/pull/26630</a></p>
<p>Release Date: 2018-07-13</p>
<p>Fix Resolution: org.webjars.npm:bootstrap:4.1.2.org.webjars:bootstrap:3.4.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"JavaScript","packageName":"twitter-bootstrap","packageVersion":"3.3.4","packageFilePaths":[null],"isTransitiveDependency":false,"dependencyTree":"twitter-bootstrap:3.3.4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.webjars.npm:bootstrap:4.1.2.org.webjars:bootstrap:3.4.0","isBinary":false},{"packageType":"JavaScript","packageName":"twitter-bootstrap","packageVersion":"3.3.4","packageFilePaths":[null],"isTransitiveDependency":false,"dependencyTree":"twitter-bootstrap:3.3.4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.webjars.npm:bootstrap:4.1.2.org.webjars:bootstrap:3.4.0","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-14042","vulnerabilityDetails":"In Bootstrap before 4.1.2, XSS is possible in the data-container property of tooltip.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14042","cvss3Severity":"medium","cvss3Score":"6.1","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Changed","C":"Low","UI":"Required","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | True | CVE-2018-14042 (Medium) detected in bootstrap-3.3.4.js, bootstrap-3.3.4.min.js - ## CVE-2018-14042 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>bootstrap-3.3.4.js</b>, <b>bootstrap-3.3.4.min.js</b></p></summary>
<p>
<details><summary><b>bootstrap-3.3.4.js</b></p></summary>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.4/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.4/js/bootstrap.js</a></p>
<p>Path to vulnerable library: /src/main/webapp/resources/bootstrap/js/bootstrap.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.4.js** (Vulnerable Library)
</details>
<details><summary><b>bootstrap-3.3.4.min.js</b></p></summary>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.4/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.4/js/bootstrap.min.js</a></p>
<p>Path to vulnerable library: /src/main/webapp/resources/bootstrap/js/bootstrap.min.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.3.4.min.js** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/shaimael/PrimeFacesAdminLTE/commit/89f33d354e9426443883e0ea242503216392aeec">89f33d354e9426443883e0ea242503216392aeec</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 Bootstrap before 4.1.2, XSS is possible in the data-container property of tooltip.
<p>Publish Date: 2018-07-13
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14042>CVE-2018-14042</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/twbs/bootstrap/pull/26630">https://github.com/twbs/bootstrap/pull/26630</a></p>
<p>Release Date: 2018-07-13</p>
<p>Fix Resolution: org.webjars.npm:bootstrap:4.1.2.org.webjars:bootstrap:3.4.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"JavaScript","packageName":"twitter-bootstrap","packageVersion":"3.3.4","packageFilePaths":[null],"isTransitiveDependency":false,"dependencyTree":"twitter-bootstrap:3.3.4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.webjars.npm:bootstrap:4.1.2.org.webjars:bootstrap:3.4.0","isBinary":false},{"packageType":"JavaScript","packageName":"twitter-bootstrap","packageVersion":"3.3.4","packageFilePaths":[null],"isTransitiveDependency":false,"dependencyTree":"twitter-bootstrap:3.3.4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.webjars.npm:bootstrap:4.1.2.org.webjars:bootstrap:3.4.0","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-14042","vulnerabilityDetails":"In Bootstrap before 4.1.2, XSS is possible in the data-container property of tooltip.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14042","cvss3Severity":"medium","cvss3Score":"6.1","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Changed","C":"Low","UI":"Required","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | non_priority | cve medium detected in bootstrap js bootstrap min js cve medium severity vulnerability vulnerable libraries bootstrap js bootstrap min js bootstrap js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to vulnerable library src main webapp resources bootstrap js bootstrap js dependency hierarchy x bootstrap js vulnerable library bootstrap min js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to vulnerable library src main webapp resources bootstrap js bootstrap min js dependency hierarchy x bootstrap min js vulnerable library found in head commit a href found in base branch master vulnerability details in bootstrap before xss is possible in the data container property of tooltip publish date 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 org webjars npm bootstrap org webjars bootstrap isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree twitter bootstrap isminimumfixversionavailable true minimumfixversion org webjars npm bootstrap org webjars bootstrap isbinary false packagetype javascript packagename twitter bootstrap packageversion packagefilepaths istransitivedependency false dependencytree twitter bootstrap isminimumfixversionavailable true minimumfixversion org webjars npm bootstrap org webjars bootstrap isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails in bootstrap before xss is possible in the data container property of tooltip vulnerabilityurl | 0 |
3,341 | 2,678,822,727 | IssuesEvent | 2015-03-26 13:35:42 | owncloud/android | https://api.github.com/repos/owncloud/android | closed | Save scroll position | browse Design enhancement | Having a lot of files in a folder scrolling down takes some time. It would be nice if the last scrolling position for each (or only folders with many files) would be saved and restored next time I open the folder. | 1.0 | Save scroll position - Having a lot of files in a folder scrolling down takes some time. It would be nice if the last scrolling position for each (or only folders with many files) would be saved and restored next time I open the folder. | non_priority | save scroll position having a lot of files in a folder scrolling down takes some time it would be nice if the last scrolling position for each or only folders with many files would be saved and restored next time i open the folder | 0 |
70,078 | 22,841,228,178 | IssuesEvent | 2022-07-12 22:10:57 | bigbluebutton/bigbluebutton | https://api.github.com/repos/bigbluebutton/bigbluebutton | opened | Webcams: MediaStream/Track inactive events aren't being handled | type: defect status: accepted module: client component: webcam | **Describe the bug**
The 'inactive' event is fired whenever the stream gets inactive (ie it cannot be used anymore), and there are scenarios where that is unexpected behavior and must be handled accordingly.
The main example of that is when gUM permissions are revoked _by the user_ via the browser's permission management panel.
Since MediaStream/Track inactive events aren't being handled in such scenarios, what actually happens is that the camera just freezes without further indication why.
**To Reproduce**
Steps to reproduce the behavior:
1. Join a meeting
2. Share a camera
3. Revoke camera permissions
**Expected behavior**
Cameras should be correctly terminated and the cause surfaced to the user.
**Actual behavior**
Camera freezes, no error is surfaced to the user.
**Screenshots**
n/a
**Additional context**
n/a
| 1.0 | Webcams: MediaStream/Track inactive events aren't being handled - **Describe the bug**
The 'inactive' event is fired whenever the stream gets inactive (ie it cannot be used anymore), and there are scenarios where that is unexpected behavior and must be handled accordingly.
The main example of that is when gUM permissions are revoked _by the user_ via the browser's permission management panel.
Since MediaStream/Track inactive events aren't being handled in such scenarios, what actually happens is that the camera just freezes without further indication why.
**To Reproduce**
Steps to reproduce the behavior:
1. Join a meeting
2. Share a camera
3. Revoke camera permissions
**Expected behavior**
Cameras should be correctly terminated and the cause surfaced to the user.
**Actual behavior**
Camera freezes, no error is surfaced to the user.
**Screenshots**
n/a
**Additional context**
n/a
| non_priority | webcams mediastream track inactive events aren t being handled describe the bug the inactive event is fired whenever the stream gets inactive ie it cannot be used anymore and there are scenarios where that is unexpected behavior and must be handled accordingly the main example of that is when gum permissions are revoked by the user via the browser s permission management panel since mediastream track inactive events aren t being handled in such scenarios what actually happens is that the camera just freezes without further indication why to reproduce steps to reproduce the behavior join a meeting share a camera revoke camera permissions expected behavior cameras should be correctly terminated and the cause surfaced to the user actual behavior camera freezes no error is surfaced to the user screenshots n a additional context n a | 0 |
244,129 | 20,611,590,532 | IssuesEvent | 2022-03-07 09:11:33 | gameserverapp/Platform | https://api.github.com/repos/gameserverapp/Platform | closed | Custom CSS is posted being escaped | bug status: to be tested community:website | **Describe the bug**
Custom CSS is posted being escaped
**Additional context**
```
body.v3 .main-nav .navbar-nav>li .dropdown ul.dropdown-menu li a,
body.v3 .main-nav .navbar-nav>li.has_child ul.dropdown-menu li a {
color: #ccc;
}
```
Rendered CSS on the Community Website, which gets ignored:
```
body.v3 .main-nav .navbar-nav>li .dropdown ul.dropdown-menu li a,
body.v3 .main-nav .navbar-nav>li.has_child ul.dropdown-menu li a {
color: #ccc;
}
``` | 1.0 | Custom CSS is posted being escaped - **Describe the bug**
Custom CSS is posted being escaped
**Additional context**
```
body.v3 .main-nav .navbar-nav>li .dropdown ul.dropdown-menu li a,
body.v3 .main-nav .navbar-nav>li.has_child ul.dropdown-menu li a {
color: #ccc;
}
```
Rendered CSS on the Community Website, which gets ignored:
```
body.v3 .main-nav .navbar-nav>li .dropdown ul.dropdown-menu li a,
body.v3 .main-nav .navbar-nav>li.has_child ul.dropdown-menu li a {
color: #ccc;
}
``` | non_priority | custom css is posted being escaped describe the bug custom css is posted being escaped additional context body main nav navbar nav li dropdown ul dropdown menu li a body main nav navbar nav li has child ul dropdown menu li a color ccc rendered css on the community website which gets ignored body main nav navbar nav gt li dropdown ul dropdown menu li a body main nav navbar nav gt li has child ul dropdown menu li a color ccc | 0 |
208,723 | 23,642,912,629 | IssuesEvent | 2022-08-25 18:53:11 | elastic/kibana | https://api.github.com/repos/elastic/kibana | closed | Reset password link when on Cloud | Team:Security enhancement Team:Cloud loe:hours impact:low | **Describe the feature:**
When running on Cloud, Kibana should offer a "reset password" link back to Cloud (the security tab of the deployment). At worst case (if we can't link back, we should show a set of instructions on where to access the reset button).
**Describe a specific use case for the feature:**
When coming from Cloud, users are given an autogenerated set of credentials that they might not know or have missed. We should give them the ability to reset that password from Cloud.
**Challenges**
Finding the right link.
In ESS we know the base url (`cloud.elastic.co`), but also need to know the deploymentId. In https://github.com/elastic/cloud/issues/53649#issuecomment-603814633 @nachogiljaldo mentions that the `cloudId` can be decoded to have the `clusterId`. This is good enough because we have a redirect (@bevacqua to confirm). So this data is already in Kibana, just the `cloudId` needs to be decoded on the frontend, not just in Beats (which I think is where it is decoded now). See https://github.com/elastic/kibana/blob/master/x-pack/plugins/cloud/server/plugin.ts#L44 for the code that has this.
In ECE we don't know the link (https://github.com/elastic/cloud/issues/54009). This is something that we're not likely to fix anytime soon since the first we could do it would be 2.6. So we'll need to plan for a world where ECE doesn't have this link. We can probably just show a tooltip in this case? Though I don't know if there's a way for Kibana to know about if it's running in ESS vs ECE.
@joshdover @legrego @cjcenizal I'm not sure who owns the Kibana login page, but this is something that would be awesome to add asap (since it shouldn't require much coding once we have a path). Also don't know what labels to add here.
Btw this is coming out of a product review where it was made obvious that this is a very simple thing we can do to hugely improve UX (which is very true).
/cc @gjones | True | Reset password link when on Cloud - **Describe the feature:**
When running on Cloud, Kibana should offer a "reset password" link back to Cloud (the security tab of the deployment). At worst case (if we can't link back, we should show a set of instructions on where to access the reset button).
**Describe a specific use case for the feature:**
When coming from Cloud, users are given an autogenerated set of credentials that they might not know or have missed. We should give them the ability to reset that password from Cloud.
**Challenges**
Finding the right link.
In ESS we know the base url (`cloud.elastic.co`), but also need to know the deploymentId. In https://github.com/elastic/cloud/issues/53649#issuecomment-603814633 @nachogiljaldo mentions that the `cloudId` can be decoded to have the `clusterId`. This is good enough because we have a redirect (@bevacqua to confirm). So this data is already in Kibana, just the `cloudId` needs to be decoded on the frontend, not just in Beats (which I think is where it is decoded now). See https://github.com/elastic/kibana/blob/master/x-pack/plugins/cloud/server/plugin.ts#L44 for the code that has this.
In ECE we don't know the link (https://github.com/elastic/cloud/issues/54009). This is something that we're not likely to fix anytime soon since the first we could do it would be 2.6. So we'll need to plan for a world where ECE doesn't have this link. We can probably just show a tooltip in this case? Though I don't know if there's a way for Kibana to know about if it's running in ESS vs ECE.
@joshdover @legrego @cjcenizal I'm not sure who owns the Kibana login page, but this is something that would be awesome to add asap (since it shouldn't require much coding once we have a path). Also don't know what labels to add here.
Btw this is coming out of a product review where it was made obvious that this is a very simple thing we can do to hugely improve UX (which is very true).
/cc @gjones | non_priority | reset password link when on cloud describe the feature when running on cloud kibana should offer a reset password link back to cloud the security tab of the deployment at worst case if we can t link back we should show a set of instructions on where to access the reset button describe a specific use case for the feature when coming from cloud users are given an autogenerated set of credentials that they might not know or have missed we should give them the ability to reset that password from cloud challenges finding the right link in ess we know the base url cloud elastic co but also need to know the deploymentid in nachogiljaldo mentions that the cloudid can be decoded to have the clusterid this is good enough because we have a redirect bevacqua to confirm so this data is already in kibana just the cloudid needs to be decoded on the frontend not just in beats which i think is where it is decoded now see for the code that has this in ece we don t know the link this is something that we re not likely to fix anytime soon since the first we could do it would be so we ll need to plan for a world where ece doesn t have this link we can probably just show a tooltip in this case though i don t know if there s a way for kibana to know about if it s running in ess vs ece joshdover legrego cjcenizal i m not sure who owns the kibana login page but this is something that would be awesome to add asap since it shouldn t require much coding once we have a path also don t know what labels to add here btw this is coming out of a product review where it was made obvious that this is a very simple thing we can do to hugely improve ux which is very true cc gjones | 0 |
165,134 | 13,965,864,521 | IssuesEvent | 2020-10-26 00:24:31 | aws/aws-sdk-go-v2 | https://api.github.com/repos/aws/aws-sdk-go-v2 | closed | [documentation] example code is invalid (pricing.GetProductsInput) | closed-for-staleness documentation service-api | **Describe the issue with documentation**
The example code is invalid in <https://pkg.go.dev/github.com/aws/aws-sdk-go-v2@v0.24.0/service/pricing#example-Client.GetProductsRequest-Shared00>
```go
input := &pricing.GetProductsInput{
Filters: []pricing.Filter{
{
Field: aws.String("ServiceCode"),
Type: pricing.FilterTypeTermMatch,
Value: aws.String("AmazonEC2"),
},
{
Field: aws.String("volumeType"),
Type: pricing.FilterTypeTermMatch,
Value: aws.String("Provisioned IOPS"),
},
},
FormatVersion: aws.String("aws_v1"),
MaxResults: aws.Int64(1),
}
```
…should be…
```go
input := &pricing.GetProductsInput{
ServiceCode: aws.String("AmazonEC2"),
Filters: []pricing.Filter{
{
Field: aws.String("volumeType"),
Type: pricing.FilterTypeTermMatch,
Value: aws.String("Provisioned IOPS"),
},
},
FormatVersion: aws.String("aws_v1"),
MaxResults: aws.Int64(1),
}
```
----
Adding the following for the Google.
```json
{"__type":"InvalidParameterException","Message":"Input Parameters are invalid. serviceCode cannot be null or empty"}
```
```plain
Error: InvalidParameterException: Input Parameters are invalid. serviceCode cannot be null or empty
status code: 400, request id: f779863d-d7c5-4797-991c-8c3efb93d237
```
| 1.0 | [documentation] example code is invalid (pricing.GetProductsInput) - **Describe the issue with documentation**
The example code is invalid in <https://pkg.go.dev/github.com/aws/aws-sdk-go-v2@v0.24.0/service/pricing#example-Client.GetProductsRequest-Shared00>
```go
input := &pricing.GetProductsInput{
Filters: []pricing.Filter{
{
Field: aws.String("ServiceCode"),
Type: pricing.FilterTypeTermMatch,
Value: aws.String("AmazonEC2"),
},
{
Field: aws.String("volumeType"),
Type: pricing.FilterTypeTermMatch,
Value: aws.String("Provisioned IOPS"),
},
},
FormatVersion: aws.String("aws_v1"),
MaxResults: aws.Int64(1),
}
```
…should be…
```go
input := &pricing.GetProductsInput{
ServiceCode: aws.String("AmazonEC2"),
Filters: []pricing.Filter{
{
Field: aws.String("volumeType"),
Type: pricing.FilterTypeTermMatch,
Value: aws.String("Provisioned IOPS"),
},
},
FormatVersion: aws.String("aws_v1"),
MaxResults: aws.Int64(1),
}
```
----
Adding the following for the Google.
```json
{"__type":"InvalidParameterException","Message":"Input Parameters are invalid. serviceCode cannot be null or empty"}
```
```plain
Error: InvalidParameterException: Input Parameters are invalid. serviceCode cannot be null or empty
status code: 400, request id: f779863d-d7c5-4797-991c-8c3efb93d237
```
| non_priority | example code is invalid pricing getproductsinput describe the issue with documentation the example code is invalid in go input pricing getproductsinput filters pricing filter field aws string servicecode type pricing filtertypetermmatch value aws string field aws string volumetype type pricing filtertypetermmatch value aws string provisioned iops formatversion aws string aws maxresults aws …should be… go input pricing getproductsinput servicecode aws string filters pricing filter field aws string volumetype type pricing filtertypetermmatch value aws string provisioned iops formatversion aws string aws maxresults aws adding the following for the google json type invalidparameterexception message input parameters are invalid servicecode cannot be null or empty plain error invalidparameterexception input parameters are invalid servicecode cannot be null or empty status code request id | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.