Unnamed: 0
int64 0
832k
| id
float64 2.49B
32.1B
| type
stringclasses 1
value | created_at
stringlengths 19
19
| repo
stringlengths 7
112
| repo_url
stringlengths 36
141
| action
stringclasses 3
values | title
stringlengths 1
853
| labels
stringlengths 4
898
| body
stringlengths 2
262k
| index
stringclasses 13
values | text_combine
stringlengths 96
262k
| label
stringclasses 2
values | text
stringlengths 96
250k
| binary_label
int64 0
1
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
146,163
| 22,973,043,737
|
IssuesEvent
|
2022-07-20 06:10:15
|
nextcloud/text
|
https://api.github.com/repos/nextcloud/text
|
closed
|
✨📱 Text app review: Mobile focus
|
enhancement design 2. developing
|
(Notes from first review on 2020-10-06 in issue at https://github.com/nextcloud/text/issues/1075 )
## Header bar https://github.com/nextcloud/text/issues/2440 https://github.com/nextcloud/text/pull/2441
* [x] Make backgound solid var(--color-main-background)
* [x] Add small blue flavor bar on the top like in Nextcloud Office
* [x] Bold the filename / title
## Toolbar
* [x] The 3-dot menu wraps into the next line, but all toolbar entries should always be on the same row (with "Saved" indicator" and people menu) https://github.com/nextcloud/text/issues/1186 https://github.com/nextcloud/text/pull/2294
* [ ] #2606 https://github.com/nextcloud/text/pull/2611
* In the long run, we could group the items into few menus: Formatting, headings, etc – however we might not have enough space
* Possibly think about moving the formatting bar to the bottom on mobile
* [x] #2607 https://github.com/nextcloud/text/pull/2627
* [x] use primary for active icons, primary-light for the background
* [x] raise opacity for all buttons by default
* [x] current opacity for the disabled buttons
* [x] Remove blue circle below active icon
## Collaborators https://github.com/nextcloud/text/issues/2449 https://github.com/nextcloud/text/pull/2450
* [x] "Saved" text is too wide
* [x] Could be combined with participants, showing a circle indicator on unsaved changes, and in the participants menu we can show extra text for "Last saved x minutes ago" on top of the participant list → **let’s do this one**
* [x] Adjust behavior on desktop, but keep "Saved" text as additional info
* Could collapse into a checkmark icon on mobile, could even be actionable to save
* Could show asterisk next to filename, but filename is not present on mobile
* Could be in a subline below the title, but filename is not present on mobile
* [x] People avatars could be a bit smaller → from 44px to e.g. 36px
* [x] Avatars should move a bit closer together to save space
* [x] Author color borders could be var(--color-main-background) when author colors are not enabled so there is separation, and when author colors are not enabled the colors don’t make sense yet anyway.
* [x] Always show all participants in dropdown (including yourself so you know your own color)
## Content
* [ ] If possible, cursor of other collaborators could show (there is a tiptap component) #90
|
1.0
|
✨📱 Text app review: Mobile focus - (Notes from first review on 2020-10-06 in issue at https://github.com/nextcloud/text/issues/1075 )
## Header bar https://github.com/nextcloud/text/issues/2440 https://github.com/nextcloud/text/pull/2441
* [x] Make backgound solid var(--color-main-background)
* [x] Add small blue flavor bar on the top like in Nextcloud Office
* [x] Bold the filename / title
## Toolbar
* [x] The 3-dot menu wraps into the next line, but all toolbar entries should always be on the same row (with "Saved" indicator" and people menu) https://github.com/nextcloud/text/issues/1186 https://github.com/nextcloud/text/pull/2294
* [ ] #2606 https://github.com/nextcloud/text/pull/2611
* In the long run, we could group the items into few menus: Formatting, headings, etc – however we might not have enough space
* Possibly think about moving the formatting bar to the bottom on mobile
* [x] #2607 https://github.com/nextcloud/text/pull/2627
* [x] use primary for active icons, primary-light for the background
* [x] raise opacity for all buttons by default
* [x] current opacity for the disabled buttons
* [x] Remove blue circle below active icon
## Collaborators https://github.com/nextcloud/text/issues/2449 https://github.com/nextcloud/text/pull/2450
* [x] "Saved" text is too wide
* [x] Could be combined with participants, showing a circle indicator on unsaved changes, and in the participants menu we can show extra text for "Last saved x minutes ago" on top of the participant list → **let’s do this one**
* [x] Adjust behavior on desktop, but keep "Saved" text as additional info
* Could collapse into a checkmark icon on mobile, could even be actionable to save
* Could show asterisk next to filename, but filename is not present on mobile
* Could be in a subline below the title, but filename is not present on mobile
* [x] People avatars could be a bit smaller → from 44px to e.g. 36px
* [x] Avatars should move a bit closer together to save space
* [x] Author color borders could be var(--color-main-background) when author colors are not enabled so there is separation, and when author colors are not enabled the colors don’t make sense yet anyway.
* [x] Always show all participants in dropdown (including yourself so you know your own color)
## Content
* [ ] If possible, cursor of other collaborators could show (there is a tiptap component) #90
|
non_build
|
✨📱 text app review mobile focus notes from first review on in issue at header bar make backgound solid var color main background add small blue flavor bar on the top like in nextcloud office bold the filename title toolbar the dot menu wraps into the next line but all toolbar entries should always be on the same row with saved indicator and people menu in the long run we could group the items into few menus formatting headings etc – however we might not have enough space possibly think about moving the formatting bar to the bottom on mobile use primary for active icons primary light for the background raise opacity for all buttons by default current opacity for the disabled buttons remove blue circle below active icon collaborators saved text is too wide could be combined with participants showing a circle indicator on unsaved changes and in the participants menu we can show extra text for last saved x minutes ago on top of the participant list → let’s do this one adjust behavior on desktop but keep saved text as additional info could collapse into a checkmark icon on mobile could even be actionable to save could show asterisk next to filename but filename is not present on mobile could be in a subline below the title but filename is not present on mobile people avatars could be a bit smaller → from to e g avatars should move a bit closer together to save space author color borders could be var color main background when author colors are not enabled so there is separation and when author colors are not enabled the colors don’t make sense yet anyway always show all participants in dropdown including yourself so you know your own color content if possible cursor of other collaborators could show there is a tiptap component
| 0
|
39,874
| 6,778,091,773
|
IssuesEvent
|
2017-10-28 05:34:12
|
devinmatte/wasp
|
https://api.github.com/repos/devinmatte/wasp
|
closed
|
Create a man page
|
documentation enhancement research
|
Almost all good command line tools provide a man page for easy documentation.
Write up some documentation, that coincides with a man page so that a new user could easily pick up the tool
|
1.0
|
Create a man page - Almost all good command line tools provide a man page for easy documentation.
Write up some documentation, that coincides with a man page so that a new user could easily pick up the tool
|
non_build
|
create a man page almost all good command line tools provide a man page for easy documentation write up some documentation that coincides with a man page so that a new user could easily pick up the tool
| 0
|
207,475
| 15,818,820,160
|
IssuesEvent
|
2021-04-05 16:34:59
|
FlowCrypt/flowcrypt-android
|
https://api.github.com/repos/FlowCrypt/flowcrypt-android
|
closed
|
Semaphore fails: NDK at /home/semaphore/Android/Sdk/ndk/22.0.7026061 did not have a source.properties file
|
android_testing
|
For example, in the #1125
https://flowcrypt.semaphoreci.com/jobs/e9151626-290e-4052-a51d-c59240d332a1
Also here: #1126 and I think in some others
|
1.0
|
Semaphore fails: NDK at /home/semaphore/Android/Sdk/ndk/22.0.7026061 did not have a source.properties file - For example, in the #1125
https://flowcrypt.semaphoreci.com/jobs/e9151626-290e-4052-a51d-c59240d332a1
Also here: #1126 and I think in some others
|
non_build
|
semaphore fails ndk at home semaphore android sdk ndk did not have a source properties file for example in the also here and i think in some others
| 0
|
11,579
| 5,039,421,913
|
IssuesEvent
|
2016-12-18 20:15:19
|
opencv/opencv
|
https://api.github.com/repos/opencv/opencv
|
closed
|
Compile error with OpenCV 3.1.0, GCC 5.4
|
bug category: build/install
|
Hi,
While I was trying to compile the source code, I have confronted with following error. Can anyone hint me how to fix?
Thank you very much!
_____________________________________________________________________________
[ 22%] Generating test_precomp.hpp
[ 22%] Generating precomp.hpp.gch/opencv_freetype_RELEASE.gch
[ 22%] Generating precomp.hpp
[ 22%] Generating test_precomp.hpp
[ 22%] Generating test_precomp.hpp.gch/opencv_test_fuzzy_RELEASE.gch
[ 22%] Generating precomp.hpp.gch/opencv_fuzzy_RELEASE.gch
[ 22%] Generating test_precomp.hpp.gch/opencv_test_imgcodecs_RELEASE.gch
/home/gusto/src/opencv/build/modules/freetype/precomp.hpp:61:22: fatal error: ft2build.h: No such file or directory
compilation terminated.
modules/freetype/CMakeFiles/pch_Generate_opencv_freetype.dir/build.make:62: recipe for target 'modules/freetype/precomp.hpp.gch/opencv_freetype_RELEASE.gch' failed
make[2]: *** [modules/freetype/precomp.hpp.gch/opencv_freetype_RELEASE.gch] Error 1
CMakeFiles/Makefile2:6186: recipe for target 'modules/freetype/CMakeFiles/pch_Generate_opencv_freetype.dir/all' failed
make[1]: *** [modules/freetype/CMakeFiles/pch_Generate_opencv_freetype.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 22%] Built target pch_Generate_opencv_test_fuzzy
[ 22%] Built target pch_Generate_opencv_fuzzy
[ 22%] Built target pch_Generate_opencv_test_imgcodecs
Makefile:160: recipe for target 'all' failed
make: *** [all] Error 2
|
1.0
|
Compile error with OpenCV 3.1.0, GCC 5.4 - Hi,
While I was trying to compile the source code, I have confronted with following error. Can anyone hint me how to fix?
Thank you very much!
_____________________________________________________________________________
[ 22%] Generating test_precomp.hpp
[ 22%] Generating precomp.hpp.gch/opencv_freetype_RELEASE.gch
[ 22%] Generating precomp.hpp
[ 22%] Generating test_precomp.hpp
[ 22%] Generating test_precomp.hpp.gch/opencv_test_fuzzy_RELEASE.gch
[ 22%] Generating precomp.hpp.gch/opencv_fuzzy_RELEASE.gch
[ 22%] Generating test_precomp.hpp.gch/opencv_test_imgcodecs_RELEASE.gch
/home/gusto/src/opencv/build/modules/freetype/precomp.hpp:61:22: fatal error: ft2build.h: No such file or directory
compilation terminated.
modules/freetype/CMakeFiles/pch_Generate_opencv_freetype.dir/build.make:62: recipe for target 'modules/freetype/precomp.hpp.gch/opencv_freetype_RELEASE.gch' failed
make[2]: *** [modules/freetype/precomp.hpp.gch/opencv_freetype_RELEASE.gch] Error 1
CMakeFiles/Makefile2:6186: recipe for target 'modules/freetype/CMakeFiles/pch_Generate_opencv_freetype.dir/all' failed
make[1]: *** [modules/freetype/CMakeFiles/pch_Generate_opencv_freetype.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 22%] Built target pch_Generate_opencv_test_fuzzy
[ 22%] Built target pch_Generate_opencv_fuzzy
[ 22%] Built target pch_Generate_opencv_test_imgcodecs
Makefile:160: recipe for target 'all' failed
make: *** [all] Error 2
|
build
|
compile error with opencv gcc hi while i was trying to compile the source code i have confronted with following error can anyone hint me how to fix thank you very much generating test precomp hpp generating precomp hpp gch opencv freetype release gch generating precomp hpp generating test precomp hpp generating test precomp hpp gch opencv test fuzzy release gch generating precomp hpp gch opencv fuzzy release gch generating test precomp hpp gch opencv test imgcodecs release gch home gusto src opencv build modules freetype precomp hpp fatal error h no such file or directory compilation terminated modules freetype cmakefiles pch generate opencv freetype dir build make recipe for target modules freetype precomp hpp gch opencv freetype release gch failed make error cmakefiles recipe for target modules freetype cmakefiles pch generate opencv freetype dir all failed make error make waiting for unfinished jobs built target pch generate opencv test fuzzy built target pch generate opencv fuzzy built target pch generate opencv test imgcodecs makefile recipe for target all failed make error
| 1
|
786,470
| 27,656,800,316
|
IssuesEvent
|
2023-03-12 02:58:18
|
lyeskara/SOEN390
|
https://api.github.com/repos/lyeskara/SOEN390
|
closed
|
DMing only works one way
|
bug high priority
|
## Describe the bug
- [x] #19
The messaging feature only works one way.
One person sends a message to a connection.
If the connection sends a message back, the application crashes.
## To Reproduce
- Log into an account
- Go into "Messages"
- Send a message to a connection
- Log into the account corresponding to that connection
- Send a message replying back to the first message sent
## Expected behavior
Messaging feature should work both ways.
The connection you are messaging should be able to message you back without crashing the application.
## Priority
P1, high priority for this sprint. Needs to be fixed as soon as possible.
## Possible Solution
Rewrite the source code to incorporate this feature of connections being able to message each other freely
## Desktop
- Browser [chrome]
- Resolution [2560 X 1289]
- Device: [PC]
- OS: [Windows11]
- Screen size: [27"]
## Additional context
- [x] #19
|
1.0
|
DMing only works one way - ## Describe the bug
- [x] #19
The messaging feature only works one way.
One person sends a message to a connection.
If the connection sends a message back, the application crashes.
## To Reproduce
- Log into an account
- Go into "Messages"
- Send a message to a connection
- Log into the account corresponding to that connection
- Send a message replying back to the first message sent
## Expected behavior
Messaging feature should work both ways.
The connection you are messaging should be able to message you back without crashing the application.
## Priority
P1, high priority for this sprint. Needs to be fixed as soon as possible.
## Possible Solution
Rewrite the source code to incorporate this feature of connections being able to message each other freely
## Desktop
- Browser [chrome]
- Resolution [2560 X 1289]
- Device: [PC]
- OS: [Windows11]
- Screen size: [27"]
## Additional context
- [x] #19
|
non_build
|
dming only works one way describe the bug the messaging feature only works one way one person sends a message to a connection if the connection sends a message back the application crashes to reproduce log into an account go into messages send a message to a connection log into the account corresponding to that connection send a message replying back to the first message sent expected behavior messaging feature should work both ways the connection you are messaging should be able to message you back without crashing the application priority high priority for this sprint needs to be fixed as soon as possible possible solution rewrite the source code to incorporate this feature of connections being able to message each other freely desktop browser resolution device os screen size additional context
| 0
|
33,725
| 9,201,773,272
|
IssuesEvent
|
2019-03-07 20:32:44
|
broadinstitute/gatk
|
https://api.github.com/repos/broadinstitute/gatk
|
closed
|
Fix failing gatk-nightly builds
|
BuildSystem Docker
|
Apparently there have been some issues lately with the gatk-nighly builds failing to upload. This appears to have been the case for the past month as the dockerhub repo doesn't show any images newer than 3 months ago.
|
1.0
|
Fix failing gatk-nightly builds - Apparently there have been some issues lately with the gatk-nighly builds failing to upload. This appears to have been the case for the past month as the dockerhub repo doesn't show any images newer than 3 months ago.
|
build
|
fix failing gatk nightly builds apparently there have been some issues lately with the gatk nighly builds failing to upload this appears to have been the case for the past month as the dockerhub repo doesn t show any images newer than months ago
| 1
|
54,781
| 13,925,977,237
|
IssuesEvent
|
2020-10-21 17:37:03
|
polatengin/B05277
|
https://api.github.com/repos/polatengin/B05277
|
opened
|
CVE-2020-8203 (High) detected in multiple libraries
|
security vulnerability
|
## CVE-2020-8203 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>lodash-1.0.2.tgz</b>, <b>lodash-3.10.1.tgz</b>, <b>lodash-4.3.0.tgz</b></p></summary>
<p>
<details><summary><b>lodash-1.0.2.tgz</b></p></summary>
<p>A utility library delivering consistency, customization, performance, and extras.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-1.0.2.tgz">https://registry.npmjs.org/lodash/-/lodash-1.0.2.tgz</a></p>
<p>Path to dependency file: B05277/Chapter03/3-BundlingAndMinifyingJavaScriptFilesWithGulp/package.json</p>
<p>Path to vulnerable library: B05277/Chapter03/3-BundlingAndMinifyingJavaScriptFilesWithGulp/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- gulp-3.9.1.tgz (Root Library)
- vinyl-fs-0.3.14.tgz
- glob-watcher-0.0.6.tgz
- gaze-0.5.2.tgz
- globule-0.1.0.tgz
- :x: **lodash-1.0.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>lodash-3.10.1.tgz</b></p></summary>
<p>The modern build of lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz">https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz</a></p>
<p>Path to dependency file: B05277/Chapter03/2-CompilingLessFilesToCSSFilesWithGrunt/package.json</p>
<p>Path to vulnerable library: B05277/Chapter03/2-CompilingLessFilesToCSSFilesWithGrunt/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- grunt-contrib-watch-1.0.0.tgz (Root Library)
- :x: **lodash-3.10.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>lodash-4.3.0.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.3.0.tgz">https://registry.npmjs.org/lodash/-/lodash-4.3.0.tgz</a></p>
<p>Path to dependency file: B05277/Chapter03/2-CompilingLessFilesToCSSFilesWithGrunt/package.json</p>
<p>Path to vulnerable library: B05277/Chapter03/2-CompilingLessFilesToCSSFilesWithGrunt/node_modules/grunt-legacy-util/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- grunt-1.0.2.tgz (Root Library)
- grunt-legacy-util-1.0.0.tgz
- :x: **lodash-4.3.0.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/polatengin/B05277/commit/17c9aaaa23bce244f17eb788d2e53f21061314da">17c9aaaa23bce244f17eb788d2e53f21061314da</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Prototype pollution attack when using _.zipObjectDeep in lodash <= 4.17.15.
<p>Publish Date: 2020-07-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8203>CVE-2020-8203</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.4</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/1523">https://www.npmjs.com/advisories/1523</a></p>
<p>Release Date: 2020-07-23</p>
<p>Fix Resolution: lodash - 4.17.19</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-8203 (High) detected in multiple libraries - ## CVE-2020-8203 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>lodash-1.0.2.tgz</b>, <b>lodash-3.10.1.tgz</b>, <b>lodash-4.3.0.tgz</b></p></summary>
<p>
<details><summary><b>lodash-1.0.2.tgz</b></p></summary>
<p>A utility library delivering consistency, customization, performance, and extras.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-1.0.2.tgz">https://registry.npmjs.org/lodash/-/lodash-1.0.2.tgz</a></p>
<p>Path to dependency file: B05277/Chapter03/3-BundlingAndMinifyingJavaScriptFilesWithGulp/package.json</p>
<p>Path to vulnerable library: B05277/Chapter03/3-BundlingAndMinifyingJavaScriptFilesWithGulp/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- gulp-3.9.1.tgz (Root Library)
- vinyl-fs-0.3.14.tgz
- glob-watcher-0.0.6.tgz
- gaze-0.5.2.tgz
- globule-0.1.0.tgz
- :x: **lodash-1.0.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>lodash-3.10.1.tgz</b></p></summary>
<p>The modern build of lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz">https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz</a></p>
<p>Path to dependency file: B05277/Chapter03/2-CompilingLessFilesToCSSFilesWithGrunt/package.json</p>
<p>Path to vulnerable library: B05277/Chapter03/2-CompilingLessFilesToCSSFilesWithGrunt/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- grunt-contrib-watch-1.0.0.tgz (Root Library)
- :x: **lodash-3.10.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>lodash-4.3.0.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.3.0.tgz">https://registry.npmjs.org/lodash/-/lodash-4.3.0.tgz</a></p>
<p>Path to dependency file: B05277/Chapter03/2-CompilingLessFilesToCSSFilesWithGrunt/package.json</p>
<p>Path to vulnerable library: B05277/Chapter03/2-CompilingLessFilesToCSSFilesWithGrunt/node_modules/grunt-legacy-util/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- grunt-1.0.2.tgz (Root Library)
- grunt-legacy-util-1.0.0.tgz
- :x: **lodash-4.3.0.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/polatengin/B05277/commit/17c9aaaa23bce244f17eb788d2e53f21061314da">17c9aaaa23bce244f17eb788d2e53f21061314da</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Prototype pollution attack when using _.zipObjectDeep in lodash <= 4.17.15.
<p>Publish Date: 2020-07-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8203>CVE-2020-8203</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.4</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/1523">https://www.npmjs.com/advisories/1523</a></p>
<p>Release Date: 2020-07-23</p>
<p>Fix Resolution: lodash - 4.17.19</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_build
|
cve high detected in multiple libraries cve high severity vulnerability vulnerable libraries lodash tgz lodash tgz lodash tgz lodash tgz a utility library delivering consistency customization performance and extras library home page a href path to dependency file bundlingandminifyingjavascriptfileswithgulp package json path to vulnerable library bundlingandminifyingjavascriptfileswithgulp node modules lodash package json dependency hierarchy gulp tgz root library vinyl fs tgz glob watcher tgz gaze tgz globule tgz x lodash tgz vulnerable library lodash tgz the modern build of lodash modular utilities library home page a href path to dependency file compilinglessfilestocssfileswithgrunt package json path to vulnerable library compilinglessfilestocssfileswithgrunt node modules lodash package json dependency hierarchy grunt contrib watch tgz root library x lodash tgz vulnerable library lodash tgz lodash modular utilities library home page a href path to dependency file compilinglessfilestocssfileswithgrunt package json path to vulnerable library compilinglessfilestocssfileswithgrunt node modules grunt legacy util node modules lodash package json dependency hierarchy grunt tgz root library grunt legacy util tgz x lodash tgz vulnerable library found in head commit a href found in base branch master vulnerability details prototype pollution attack when using zipobjectdeep in lodash publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution lodash step up your open source security game with whitesource
| 0
|
4,707
| 3,436,424,850
|
IssuesEvent
|
2015-12-12 11:12:41
|
WPN-XM/WPN-XM
|
https://api.github.com/repos/WPN-XM/WPN-XM
|
closed
|
code sign the setup executables
|
build tools feature installation wizard security
|
The goal is to code-sign the installer executables in order to avoid the nasty popup and to make the installers safe against modification.
- [x] Buy Code sign cert or acquire a free one
- [x] acquire a free code-signing cert (for open source projects)
- http://certum.eu/certum/cert,offer_en_open_source_cs.xml
- [ ] add "code-signing" code to the install wizards
- [ ] Research: How to protect/encrypt the certificate on public build infrastructure, like Travis-CI?
- [ ] trigger "code-signing" during build process / installer compilation on Travis-CI
Resources:
- http://www.jrsoftware.org/ishelp/index.php?topic=setup_signtool
- by using kSign: http://certhelp.ksoftware.net/support/solutions/articles/17169-how-do-i-automate-code-signing-with-innosetup-and-ksign-
- https://www.pierschel.com/de/software-blog/18-code-signing-tutorial-de
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/6821617-code-sign-the-setup-executables?utm_campaign=plugin&utm_content=tracker%2F164029&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F164029&utm_medium=issues&utm_source=github).
</bountysource-plugin>
|
1.0
|
code sign the setup executables - The goal is to code-sign the installer executables in order to avoid the nasty popup and to make the installers safe against modification.
- [x] Buy Code sign cert or acquire a free one
- [x] acquire a free code-signing cert (for open source projects)
- http://certum.eu/certum/cert,offer_en_open_source_cs.xml
- [ ] add "code-signing" code to the install wizards
- [ ] Research: How to protect/encrypt the certificate on public build infrastructure, like Travis-CI?
- [ ] trigger "code-signing" during build process / installer compilation on Travis-CI
Resources:
- http://www.jrsoftware.org/ishelp/index.php?topic=setup_signtool
- by using kSign: http://certhelp.ksoftware.net/support/solutions/articles/17169-how-do-i-automate-code-signing-with-innosetup-and-ksign-
- https://www.pierschel.com/de/software-blog/18-code-signing-tutorial-de
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/6821617-code-sign-the-setup-executables?utm_campaign=plugin&utm_content=tracker%2F164029&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F164029&utm_medium=issues&utm_source=github).
</bountysource-plugin>
|
build
|
code sign the setup executables the goal is to code sign the installer executables in order to avoid the nasty popup and to make the installers safe against modification buy code sign cert or acquire a free one acquire a free code signing cert for open source projects add code signing code to the install wizards research how to protect encrypt the certificate on public build infrastructure like travis ci trigger code signing during build process installer compilation on travis ci resources by using ksign want to back this issue we accept bounties via
| 1
|
35,692
| 9,645,533,883
|
IssuesEvent
|
2019-05-17 08:54:50
|
yandex/ClickHouse
|
https://api.github.com/repos/yandex/ClickHouse
|
opened
|
build failed, by clang 8.0.0
|
build
|
hi, Thank you for your work.
I compiled in stable version (19.5.3.8 stable) wrong.
first, Download the code from LLVM and copy the code from the driver directory to compiler_8.0.0 and compiler_8.0.0svn.
second, The build code.
failed message:
CMake Error at dbms/programs/clang/Compiler-8.0.0svn/CMakeLists.txt:32 (add_clang_tool):
Unknown CMake command "add_clang_tool".
|
1.0
|
build failed, by clang 8.0.0 - hi, Thank you for your work.
I compiled in stable version (19.5.3.8 stable) wrong.
first, Download the code from LLVM and copy the code from the driver directory to compiler_8.0.0 and compiler_8.0.0svn.
second, The build code.
failed message:
CMake Error at dbms/programs/clang/Compiler-8.0.0svn/CMakeLists.txt:32 (add_clang_tool):
Unknown CMake command "add_clang_tool".
|
build
|
build failed by clang hi thank you for your work i compiled in stable version stable wrong first download the code from llvm and copy the code from the driver directory to compiler and compiler second the build code failed message cmake error at dbms programs clang compiler cmakelists txt add clang tool unknown cmake command add clang tool
| 1
|
16,406
| 31,778,423,673
|
IssuesEvent
|
2023-09-12 15:44:07
|
cancervariants/fusor
|
https://api.github.com/repos/cancervariants/fusor
|
closed
|
relax requirements of minimum information model components
|
priority:medium requirement
|
see https://github.com/cancervariants/fusion-curation/issues/261
relax requirements of minimum information model components
(do not require assay metadata, causative event, protein domains, reading frame)
|
1.0
|
relax requirements of minimum information model components - see https://github.com/cancervariants/fusion-curation/issues/261
relax requirements of minimum information model components
(do not require assay metadata, causative event, protein domains, reading frame)
|
non_build
|
relax requirements of minimum information model components see relax requirements of minimum information model components do not require assay metadata causative event protein domains reading frame
| 0
|
333,065
| 24,361,829,668
|
IssuesEvent
|
2022-10-03 12:22:23
|
eclipse-dataspaceconnector/DataSpaceConnector
|
https://api.github.com/repos/eclipse-dataspaceconnector/DataSpaceConnector
|
closed
|
Update Documentation on event filtering and add missing javadoc to Event Classes
|
documentation stale
|
# Feature Request
The documentation about how to filter Events needs to be adapted. Also the events type Assets and TransferProcess needs to get javadoc.
## Which Areas Would Be Affected?
Event Framework
## Why Is the Feature Desired?
Documentation needs always to be up to date.
## Solution Proposal
Adding and adapt documentation
## Type of Issue
Improvement
## Checklist
- [x] assigned appropriate label?
- [x] **Do NOT select a milestone or an assignee!**
|
1.0
|
Update Documentation on event filtering and add missing javadoc to Event Classes - # Feature Request
The documentation about how to filter Events needs to be adapted. Also the events type Assets and TransferProcess needs to get javadoc.
## Which Areas Would Be Affected?
Event Framework
## Why Is the Feature Desired?
Documentation needs always to be up to date.
## Solution Proposal
Adding and adapt documentation
## Type of Issue
Improvement
## Checklist
- [x] assigned appropriate label?
- [x] **Do NOT select a milestone or an assignee!**
|
non_build
|
update documentation on event filtering and add missing javadoc to event classes feature request the documentation about how to filter events needs to be adapted also the events type assets and transferprocess needs to get javadoc which areas would be affected event framework why is the feature desired documentation needs always to be up to date solution proposal adding and adapt documentation type of issue improvement checklist assigned appropriate label do not select a milestone or an assignee
| 0
|
10,133
| 4,712,540,686
|
IssuesEvent
|
2016-10-14 17:05:59
|
openshift/origin
|
https://api.github.com/repos/openshift/origin
|
closed
|
Git Flow Workflow
|
component/build kind/enhancement kind/question priority/P2
|
Hi there,
Reading through the docs, I was unsure whether or not a git flow workflow is currently supported by OpenShift. It seems that when you create a new app and associate a git repository with it, you can only specify a single branch to utilize for deployments, etc. This seems geared more towards a fork-and-pull model of using git. In my org, contributors to a repository simply create feature branches and then make pull requests against the master branch.
What would be ideal to augment this workflow is to be able to create a new app (or "sub-app") per branch in a repository. I think this could be done manually at the moment simply by prepending the branch name to the app name and then specifying the git branch for builds during app creation. That said, this seems kind of hacky and could probably become unmanageable quite quickly. Do you have any suggestions on how to go about this or if there are any planned enhancements to the platform to support this workflow?
Thanks!
|
1.0
|
Git Flow Workflow - Hi there,
Reading through the docs, I was unsure whether or not a git flow workflow is currently supported by OpenShift. It seems that when you create a new app and associate a git repository with it, you can only specify a single branch to utilize for deployments, etc. This seems geared more towards a fork-and-pull model of using git. In my org, contributors to a repository simply create feature branches and then make pull requests against the master branch.
What would be ideal to augment this workflow is to be able to create a new app (or "sub-app") per branch in a repository. I think this could be done manually at the moment simply by prepending the branch name to the app name and then specifying the git branch for builds during app creation. That said, this seems kind of hacky and could probably become unmanageable quite quickly. Do you have any suggestions on how to go about this or if there are any planned enhancements to the platform to support this workflow?
Thanks!
|
build
|
git flow workflow hi there reading through the docs i was unsure whether or not a git flow workflow is currently supported by openshift it seems that when you create a new app and associate a git repository with it you can only specify a single branch to utilize for deployments etc this seems geared more towards a fork and pull model of using git in my org contributors to a repository simply create feature branches and then make pull requests against the master branch what would be ideal to augment this workflow is to be able to create a new app or sub app per branch in a repository i think this could be done manually at the moment simply by prepending the branch name to the app name and then specifying the git branch for builds during app creation that said this seems kind of hacky and could probably become unmanageable quite quickly do you have any suggestions on how to go about this or if there are any planned enhancements to the platform to support this workflow thanks
| 1
|
57,175
| 14,016,597,613
|
IssuesEvent
|
2020-10-29 14:42:20
|
NCEAS/metacatui
|
https://api.github.com/repos/NCEAS/metacatui
|
closed
|
Organize Rule files into subfolders
|
query builder task
|
Let's create folders in the 'models' 'views' and 'templates' directories of the Metacatui repo and put all the new Query builder files in those folders, even if it's only one. I've been starting to organize things more this away and it's helped me during development find the file I need faster.
|
1.0
|
Organize Rule files into subfolders - Let's create folders in the 'models' 'views' and 'templates' directories of the Metacatui repo and put all the new Query builder files in those folders, even if it's only one. I've been starting to organize things more this away and it's helped me during development find the file I need faster.
|
build
|
organize rule files into subfolders let s create folders in the models views and templates directories of the metacatui repo and put all the new query builder files in those folders even if it s only one i ve been starting to organize things more this away and it s helped me during development find the file i need faster
| 1
|
17,124
| 11,705,814,081
|
IssuesEvent
|
2020-03-07 18:09:01
|
kubernetes/kubernetes
|
https://api.github.com/repos/kubernetes/kubernetes
|
closed
|
certificatesigningrequest.certificates.k8s.io wrong output upon certificate deny
|
kind/bug sig/auth sig/cli sig/usability
|
<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
Denied a CSR using `kubectl certificate deny`. Got the wrong/misleading output
**What you expected to happen**:
Expected api to return correct output.
**How to reproduce it (as minimally and precisely as possible)**:
1. Create `CertificateSigningRequest` object.
```
cat <<EOF | kubectl apply -f -
> apiVersion: certificates.k8s.io/v1beta1
> kind: CertificateSigningRequest
> metadata:
> name: test
> spec:
> request: $(cat test.csr | base64 | tr -d '\n')
> usages:
> - digital signature
> - key encipherment
> - server auth
> EOF
```
2. Deny the request
```
kubectl certificate deny test
```
You will get following output
```
certificatesigningrequest.certificates.k8s.io/test approved
```
**Anything else we need to know?**:
**Environment**: Test
- Kubernetes version (use `kubectl version`):
```
kubectl version --short
Client Version: v1.16.0
Server Version: v1.16.0
```
- Cloud provider or hardware configuration:
- OS (e.g: `cat /etc/os-release`):
- Kernel (e.g. `uname -a`):
- Install tools:
- Network plugin and version (if this is a network-related bug):
- Others:
|
True
|
certificatesigningrequest.certificates.k8s.io wrong output upon certificate deny - <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
Denied a CSR using `kubectl certificate deny`. Got the wrong/misleading output
**What you expected to happen**:
Expected api to return correct output.
**How to reproduce it (as minimally and precisely as possible)**:
1. Create `CertificateSigningRequest` object.
```
cat <<EOF | kubectl apply -f -
> apiVersion: certificates.k8s.io/v1beta1
> kind: CertificateSigningRequest
> metadata:
> name: test
> spec:
> request: $(cat test.csr | base64 | tr -d '\n')
> usages:
> - digital signature
> - key encipherment
> - server auth
> EOF
```
2. Deny the request
```
kubectl certificate deny test
```
You will get following output
```
certificatesigningrequest.certificates.k8s.io/test approved
```
**Anything else we need to know?**:
**Environment**: Test
- Kubernetes version (use `kubectl version`):
```
kubectl version --short
Client Version: v1.16.0
Server Version: v1.16.0
```
- Cloud provider or hardware configuration:
- OS (e.g: `cat /etc/os-release`):
- Kernel (e.g. `uname -a`):
- Install tools:
- Network plugin and version (if this is a network-related bug):
- Others:
|
non_build
|
certificatesigningrequest certificates io wrong output upon certificate deny please use this template while reporting a bug and provide as much info as possible not doing so may result in your bug not being addressed in a timely manner thanks if the matter is security related please disclose it privately via what happened denied a csr using kubectl certificate deny got the wrong misleading output what you expected to happen expected api to return correct output how to reproduce it as minimally and precisely as possible create certificatesigningrequest object cat eof kubectl apply f apiversion certificates io kind certificatesigningrequest metadata name test spec request cat test csr tr d n usages digital signature key encipherment server auth eof deny the request kubectl certificate deny test you will get following output certificatesigningrequest certificates io test approved anything else we need to know environment test kubernetes version use kubectl version kubectl version short client version server version cloud provider or hardware configuration os e g cat etc os release kernel e g uname a install tools network plugin and version if this is a network related bug others
| 0
|
36,351
| 9,795,563,348
|
IssuesEvent
|
2019-06-11 04:20:34
|
tensorflow/tensorflow
|
https://api.github.com/repos/tensorflow/tensorflow
|
closed
|
Updated Eigen breaks builds
|
2.0 stat:awaiting response subtype: ubuntu/linux type:build/install
|
**System information**
- OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Fedora 30
- Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
- TensorFlow installed from (source or binary): source
- TensorFlow version: 2.0
- Python version: 3.7
- Installed using virtualenv? pip? conda?: source in virtualenv
- Bazel version (if compiling from source): 0.25.2-1
- GCC/Compiler version (if compiling from source): 9.1.1-1
- CUDA/cuDNN version: 10.1
**Describe the problem**
master branch earlier today could compile fine, now it no longer can with the following error in many files:
```
external/eigen_archive/unsupported/Eigen/CXX11/../../../Eigen/src/Core/arch/GPU/Half.h(717): error: no suitable constructor exists to convert from "float" to "Eigen::half"
```
It seems commit cf5687d4b3f66fecbab4ac35f89be0b9edac17eb may have caused this since it updated the Eigen version.
**Provide the exact sequence of commands / steps that you executed before running into the problem**
```
virtualenv tensorflow
cd tensorflow
. bin/activate
pip install --upgrade --force-reinstall pip setuptools
pip install wheel numpy scipy keras
git clone https://github.com/tensorflow/tensorflow.git --single-branch --branch master
cd tensorflow
./configure
# Use default values except:
# CUDA support: Y and TensorRT support: Y
# Only support compute capability 7.0 and not 6.1
export TMP=/tmp
bazel build --jobs 15 -c opt --config=opt --config=v2 --config=mkl --config=numa \
--copt=-march=native --cxxopt=-march=native --copt=-O3 --cxxopt=-O3 \
//tensorflow/tools/pip_package:build_pip_package --verbose_failures
```
|
1.0
|
Updated Eigen breaks builds - **System information**
- OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Fedora 30
- Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
- TensorFlow installed from (source or binary): source
- TensorFlow version: 2.0
- Python version: 3.7
- Installed using virtualenv? pip? conda?: source in virtualenv
- Bazel version (if compiling from source): 0.25.2-1
- GCC/Compiler version (if compiling from source): 9.1.1-1
- CUDA/cuDNN version: 10.1
**Describe the problem**
master branch earlier today could compile fine, now it no longer can with the following error in many files:
```
external/eigen_archive/unsupported/Eigen/CXX11/../../../Eigen/src/Core/arch/GPU/Half.h(717): error: no suitable constructor exists to convert from "float" to "Eigen::half"
```
It seems commit cf5687d4b3f66fecbab4ac35f89be0b9edac17eb may have caused this since it updated the Eigen version.
**Provide the exact sequence of commands / steps that you executed before running into the problem**
```
virtualenv tensorflow
cd tensorflow
. bin/activate
pip install --upgrade --force-reinstall pip setuptools
pip install wheel numpy scipy keras
git clone https://github.com/tensorflow/tensorflow.git --single-branch --branch master
cd tensorflow
./configure
# Use default values except:
# CUDA support: Y and TensorRT support: Y
# Only support compute capability 7.0 and not 6.1
export TMP=/tmp
bazel build --jobs 15 -c opt --config=opt --config=v2 --config=mkl --config=numa \
--copt=-march=native --cxxopt=-march=native --copt=-O3 --cxxopt=-O3 \
//tensorflow/tools/pip_package:build_pip_package --verbose_failures
```
|
build
|
updated eigen breaks builds system information os platform and distribution e g linux ubuntu fedora mobile device e g iphone pixel samsung galaxy if the issue happens on mobile device tensorflow installed from source or binary source tensorflow version python version installed using virtualenv pip conda source in virtualenv bazel version if compiling from source gcc compiler version if compiling from source cuda cudnn version describe the problem master branch earlier today could compile fine now it no longer can with the following error in many files external eigen archive unsupported eigen eigen src core arch gpu half h error no suitable constructor exists to convert from float to eigen half it seems commit may have caused this since it updated the eigen version provide the exact sequence of commands steps that you executed before running into the problem virtualenv tensorflow cd tensorflow bin activate pip install upgrade force reinstall pip setuptools pip install wheel numpy scipy keras git clone single branch branch master cd tensorflow configure use default values except cuda support y and tensorrt support y only support compute capability and not export tmp tmp bazel build jobs c opt config opt config config mkl config numa copt march native cxxopt march native copt cxxopt tensorflow tools pip package build pip package verbose failures
| 1
|
132,166
| 28,110,302,735
|
IssuesEvent
|
2023-03-31 06:32:35
|
cosmos/ibc-go
|
https://api.github.com/repos/cosmos/ibc-go
|
closed
|
Use state in enums in channel handshake logs
|
good first issue code hygiene
|
<!-- < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < ☺
v ✰ Thanks for opening an issue! ✰
v Before smashing the submit button please review the template.
v Word of caution: poorly thought-out proposals may be rejected
v without deliberation
☺ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -->
## Summary
Update hardcoded strings used within the ibc channel handshake code to use enum `String()` methods.
At the end of each handshake handler the previous state and current state is logged. Currently, the states are hardcoded.
Update them to use the correct enum `String()` methods.
See 04-channel/keeper/handshake.go. E.g. https://github.com/cosmos/ibc-go/blob/main/modules/core/04-channel/keeper/handshake.go#L96
____
#### For Admin Use
- [ ] Not duplicate issue
- [ ] Appropriate labels applied
- [ ] Appropriate contributors tagged/assigned
|
1.0
|
Use state in enums in channel handshake logs - <!-- < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < ☺
v ✰ Thanks for opening an issue! ✰
v Before smashing the submit button please review the template.
v Word of caution: poorly thought-out proposals may be rejected
v without deliberation
☺ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -->
## Summary
Update hardcoded strings used within the ibc channel handshake code to use enum `String()` methods.
At the end of each handshake handler the previous state and current state is logged. Currently, the states are hardcoded.
Update them to use the correct enum `String()` methods.
See 04-channel/keeper/handshake.go. E.g. https://github.com/cosmos/ibc-go/blob/main/modules/core/04-channel/keeper/handshake.go#L96
____
#### For Admin Use
- [ ] Not duplicate issue
- [ ] Appropriate labels applied
- [ ] Appropriate contributors tagged/assigned
|
non_build
|
use state in enums in channel handshake logs ☺ v ✰ thanks for opening an issue ✰ v before smashing the submit button please review the template v word of caution poorly thought out proposals may be rejected v without deliberation ☺ summary update hardcoded strings used within the ibc channel handshake code to use enum string methods at the end of each handshake handler the previous state and current state is logged currently the states are hardcoded update them to use the correct enum string methods see channel keeper handshake go e g for admin use not duplicate issue appropriate labels applied appropriate contributors tagged assigned
| 0
|
54,619
| 3,070,359,688
|
IssuesEvent
|
2015-08-19 03:23:19
|
SiliconValleyInsight/activity_tracker
|
https://api.github.com/repos/SiliconValleyInsight/activity_tracker
|
closed
|
On Choose Activities screen, hide activity icons that can't be tracked by the app
|
1st priority resolved
|
Hide other activities from the choose activities screen that can't be tracked by the app anyway.
Here are activities for hiding (sorry couldn't upload screencaps):
1. van icon (3rd from left, 1st row)
2. running icon (2nd from left, 2nd row)
3. swimming icon (3rd from left, 2nd row)
4. ball icon (3rd row)
5. train icon (3rd row)
|
1.0
|
On Choose Activities screen, hide activity icons that can't be tracked by the app - Hide other activities from the choose activities screen that can't be tracked by the app anyway.
Here are activities for hiding (sorry couldn't upload screencaps):
1. van icon (3rd from left, 1st row)
2. running icon (2nd from left, 2nd row)
3. swimming icon (3rd from left, 2nd row)
4. ball icon (3rd row)
5. train icon (3rd row)
|
non_build
|
on choose activities screen hide activity icons that can t be tracked by the app hide other activities from the choose activities screen that can t be tracked by the app anyway here are activities for hiding sorry couldn t upload screencaps van icon from left row running icon from left row swimming icon from left row ball icon row train icon row
| 0
|
84,539
| 10,544,983,200
|
IssuesEvent
|
2019-10-02 18:07:54
|
aragon/aragon-apps
|
https://api.github.com/repos/aragon/aragon-apps
|
closed
|
Determine what notifications we want
|
app: finance app: token manager app: vault app: voting component: frontend design: request enhancement
|
For the notifications feature to be implemented, we should decide on what notifications we want from each app.
Furthermore, there are technically two types of notifications: "global" and "direct", where global notifications are for all users of a DAO and direct notification is for a specific user or a specific set of users.
We should think about signal/noise ratio when deciding.
|
1.0
|
Determine what notifications we want - For the notifications feature to be implemented, we should decide on what notifications we want from each app.
Furthermore, there are technically two types of notifications: "global" and "direct", where global notifications are for all users of a DAO and direct notification is for a specific user or a specific set of users.
We should think about signal/noise ratio when deciding.
|
non_build
|
determine what notifications we want for the notifications feature to be implemented we should decide on what notifications we want from each app furthermore there are technically two types of notifications global and direct where global notifications are for all users of a dao and direct notification is for a specific user or a specific set of users we should think about signal noise ratio when deciding
| 0
|
64,486
| 15,891,616,829
|
IssuesEvent
|
2021-04-10 20:00:00
|
minetest/minetest
|
https://api.github.com/repos/minetest/minetest
|
closed
|
Building attempts to write into the bin directory in the source code.
|
@ Build Request / Suggestion
|
stable-5
commit 07903949ec329c4856e15a020bb3c48f851405d8
(Presently current)
Building attempts to write into the bin directory in the source code rather than in the build or object directory. The source code can be kept clean of build files. Some procedures can require it. The directory may be read-only.
|
1.0
|
Building attempts to write into the bin directory in the source code. - stable-5
commit 07903949ec329c4856e15a020bb3c48f851405d8
(Presently current)
Building attempts to write into the bin directory in the source code rather than in the build or object directory. The source code can be kept clean of build files. Some procedures can require it. The directory may be read-only.
|
build
|
building attempts to write into the bin directory in the source code stable commit presently current building attempts to write into the bin directory in the source code rather than in the build or object directory the source code can be kept clean of build files some procedures can require it the directory may be read only
| 1
|
29,110
| 8,289,433,288
|
IssuesEvent
|
2018-09-19 14:40:47
|
athrane/pineapple
|
https://api.github.com/repos/athrane/pineapple
|
closed
|
mvn jetty:run fails with RuntimeException: Error scanning entry META-INF/versions/9/...
|
Java9 bug maven build pineapple-web-application-war
|
Stacktrace:
```
[INFO] jetty-9.2.3.v20140905
[WARNING] Failed startup of context o.e.j.m.p.JettyWebAppContext@4a23350{/,file:/C:/Users/Thrane/git/pineapple/applications/pineapple-web-application/pineapple-web-application-war/src/main/webapp/,STARTING}{file:/C:/Users/Thrane/git/pineapple/applications/pineapple-web-application/pineapple-web-application-war/src/main/webapp/}
MultiException[java.lang.RuntimeException: Error scanning entry META-INF/versions/9/javax/xml/bind/ModuleUtil.class from jar file:/C:/.m2/repository/javax/xml/bind/jaxb-api/2.3.0/jaxb-api-2.3.0.jar, java.lang.RuntimeException: Error scanning entry module-info.class from jar file:/C:/.m2/repository/javax/xml/bind/jaxb-api/2.3.0/jaxb-api-2.3.0.jar]
at org.eclipse.jetty.annotations.AnnotationConfiguration.scanForAnnotations(AnnotationConfiguration.java:535)
at org.eclipse.jetty.annotations.AnnotationConfiguration.configure(AnnotationConfiguration.java:446)
at org.eclipse.jetty.webapp.WebAppContext.configure(WebAppContext.java:471)
at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1329)
at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:497)
at org.eclipse.jetty.maven.plugin.JettyWebAppContext.doStart(JettyWebAppContext.java:365)
```
|
1.0
|
mvn jetty:run fails with RuntimeException: Error scanning entry META-INF/versions/9/... - Stacktrace:
```
[INFO] jetty-9.2.3.v20140905
[WARNING] Failed startup of context o.e.j.m.p.JettyWebAppContext@4a23350{/,file:/C:/Users/Thrane/git/pineapple/applications/pineapple-web-application/pineapple-web-application-war/src/main/webapp/,STARTING}{file:/C:/Users/Thrane/git/pineapple/applications/pineapple-web-application/pineapple-web-application-war/src/main/webapp/}
MultiException[java.lang.RuntimeException: Error scanning entry META-INF/versions/9/javax/xml/bind/ModuleUtil.class from jar file:/C:/.m2/repository/javax/xml/bind/jaxb-api/2.3.0/jaxb-api-2.3.0.jar, java.lang.RuntimeException: Error scanning entry module-info.class from jar file:/C:/.m2/repository/javax/xml/bind/jaxb-api/2.3.0/jaxb-api-2.3.0.jar]
at org.eclipse.jetty.annotations.AnnotationConfiguration.scanForAnnotations(AnnotationConfiguration.java:535)
at org.eclipse.jetty.annotations.AnnotationConfiguration.configure(AnnotationConfiguration.java:446)
at org.eclipse.jetty.webapp.WebAppContext.configure(WebAppContext.java:471)
at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1329)
at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:497)
at org.eclipse.jetty.maven.plugin.JettyWebAppContext.doStart(JettyWebAppContext.java:365)
```
|
build
|
mvn jetty run fails with runtimeexception error scanning entry meta inf versions stacktrace jetty failed startup of context o e j m p jettywebappcontext file c users thrane git pineapple applications pineapple web application pineapple web application war src main webapp starting file c users thrane git pineapple applications pineapple web application pineapple web application war src main webapp multiexception at org eclipse jetty annotations annotationconfiguration scanforannotations annotationconfiguration java at org eclipse jetty annotations annotationconfiguration configure annotationconfiguration java at org eclipse jetty webapp webappcontext configure webappcontext java at org eclipse jetty webapp webappcontext startcontext webappcontext java at org eclipse jetty server handler contexthandler dostart contexthandler java at org eclipse jetty webapp webappcontext dostart webappcontext java at org eclipse jetty maven plugin jettywebappcontext dostart jettywebappcontext java
| 1
|
78,613
| 22,324,752,706
|
IssuesEvent
|
2022-06-14 09:37:44
|
elastic/elasticsearch
|
https://api.github.com/repos/elastic/elasticsearch
|
closed
|
[CI] bwcTestSnapshots,windows-2012-r2 fails with missing depedencies
|
:Delivery/Build >test-failure needs:triage Team:Delivery
|
### CI Link
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+7.17+multijob+platform-support-windows/GRADLE_TASK=bwcTestSnapshots,os=windows-2012-r2/360/
### Repro line
None
### Does it reproduce?
Didn't try
### Applicable branches
7.17
### Failure history
_No response_
### Failure excerpt
Looks like flaky network at first glance but wanted to confirm:
```
10:47:27 Starting a Gradle Daemon (subsequent builds will be faster)
10:49:29
10:49:29 FAILURE: Build failed with an exception.
10:49:29
10:49:29 * What went wrong:
10:49:29 A problem occurred configuring project ':build-tools'.
10:49:29 > Could not determine the dependencies of null.
10:49:29 > Could not resolve all task dependencies for configuration ':build-tools:classpath'.
10:49:29 > Could not resolve org.apache.rat:apache-rat:0.11.
10:49:29 Required by:
10:49:29 project :build-tools > project :build-conventions
10:49:29 > Could not resolve org.apache.rat:apache-rat:0.11.
10:49:29 > Could not get resource 'https://plugins.gradle.org/m2/org/apache/rat/apache-rat/0.11/apache-rat-0.11.pom'.
10:49:29 > Premature end of Content-Length delimited message body (expected: 7,502; received: 6,128)
```
|
1.0
|
[CI] bwcTestSnapshots,windows-2012-r2 fails with missing depedencies - ### CI Link
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+7.17+multijob+platform-support-windows/GRADLE_TASK=bwcTestSnapshots,os=windows-2012-r2/360/
### Repro line
None
### Does it reproduce?
Didn't try
### Applicable branches
7.17
### Failure history
_No response_
### Failure excerpt
Looks like flaky network at first glance but wanted to confirm:
```
10:47:27 Starting a Gradle Daemon (subsequent builds will be faster)
10:49:29
10:49:29 FAILURE: Build failed with an exception.
10:49:29
10:49:29 * What went wrong:
10:49:29 A problem occurred configuring project ':build-tools'.
10:49:29 > Could not determine the dependencies of null.
10:49:29 > Could not resolve all task dependencies for configuration ':build-tools:classpath'.
10:49:29 > Could not resolve org.apache.rat:apache-rat:0.11.
10:49:29 Required by:
10:49:29 project :build-tools > project :build-conventions
10:49:29 > Could not resolve org.apache.rat:apache-rat:0.11.
10:49:29 > Could not get resource 'https://plugins.gradle.org/m2/org/apache/rat/apache-rat/0.11/apache-rat-0.11.pom'.
10:49:29 > Premature end of Content-Length delimited message body (expected: 7,502; received: 6,128)
```
|
build
|
bwctestsnapshots windows fails with missing depedencies ci link repro line none does it reproduce didn t try applicable branches failure history no response failure excerpt looks like flaky network at first glance but wanted to confirm starting a gradle daemon subsequent builds will be faster failure build failed with an exception what went wrong a problem occurred configuring project build tools could not determine the dependencies of null could not resolve all task dependencies for configuration build tools classpath could not resolve org apache rat apache rat required by project build tools project build conventions could not resolve org apache rat apache rat could not get resource premature end of content length delimited message body expected received
| 1
|
423,052
| 12,289,922,371
|
IssuesEvent
|
2020-05-10 00:21:35
|
eclipse-ee4j/glassfish
|
https://api.github.com/repos/eclipse-ee4j/glassfish
|
closed
|
missing resource-ref in domain.xml breaks connection pooling
|
Component: jdbc ERR: Assignee Priority: Major Stale Type: Bug
|
Related to #18166, but different failure mode
If you are missing resource-ref in domain.xml, then you can still get connections from JNDI but they won't be pooled, and the "Monitor" tab in the admin console won't work - returns all zeros.
Silent failure is bad.
#### Affected Versions
[3.1.1, 3.1.2]
|
1.0
|
missing resource-ref in domain.xml breaks connection pooling - Related to #18166, but different failure mode
If you are missing resource-ref in domain.xml, then you can still get connections from JNDI but they won't be pooled, and the "Monitor" tab in the admin console won't work - returns all zeros.
Silent failure is bad.
#### Affected Versions
[3.1.1, 3.1.2]
|
non_build
|
missing resource ref in domain xml breaks connection pooling related to but different failure mode if you are missing resource ref in domain xml then you can still get connections from jndi but they won t be pooled and the monitor tab in the admin console won t work returns all zeros silent failure is bad affected versions
| 0
|
51,865
| 12,821,104,912
|
IssuesEvent
|
2020-07-06 07:25:26
|
kubevirt/kubevirt
|
https://api.github.com/repos/kubevirt/kubevirt
|
closed
|
[rfe_id:588] ContainerDisk Starting from custom image location with disk at /custom-disk/downloaded [test_id:1466]should boot normally
|
kind/bug triage/build-officer
|
<!-- This form is for bug reports and feature requests ONLY!
Also make sure that you visit our User Guide at https://kubevirt.io/user-guide/
-->
**Is this a BUG REPORT or FEATURE REQUEST?**:
> Uncomment only one, leave it on its own line:
>
/kind bug
/label build-officer
> /kind enhancement
**What happened**:
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/3544/pull-kubevirt-e2e-kind-k8s-1.17.0-ipv6/1274612562545086464
**What you expected to happen**:
test should pass.
**How to reproduce it (as minimally and precisely as possible)**:
**Anything else we need to know?**:
**Environment**:
- KubeVirt version (use `virtctl version`):
- Kubernetes version (use `kubectl version`):
- VM or VMI specifications:
- Cloud provider or hardware configuration:
- OS (e.g. from /etc/os-release):
- Kernel (e.g. `uname -a`):
- Install tools:
- Others:
|
1.0
|
[rfe_id:588] ContainerDisk Starting from custom image location with disk at /custom-disk/downloaded [test_id:1466]should boot normally - <!-- This form is for bug reports and feature requests ONLY!
Also make sure that you visit our User Guide at https://kubevirt.io/user-guide/
-->
**Is this a BUG REPORT or FEATURE REQUEST?**:
> Uncomment only one, leave it on its own line:
>
/kind bug
/label build-officer
> /kind enhancement
**What happened**:
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/3544/pull-kubevirt-e2e-kind-k8s-1.17.0-ipv6/1274612562545086464
**What you expected to happen**:
test should pass.
**How to reproduce it (as minimally and precisely as possible)**:
**Anything else we need to know?**:
**Environment**:
- KubeVirt version (use `virtctl version`):
- Kubernetes version (use `kubectl version`):
- VM or VMI specifications:
- Cloud provider or hardware configuration:
- OS (e.g. from /etc/os-release):
- Kernel (e.g. `uname -a`):
- Install tools:
- Others:
|
build
|
containerdisk starting from custom image location with disk at custom disk downloaded should boot normally this form is for bug reports and feature requests only also make sure that you visit our user guide at is this a bug report or feature request uncomment only one leave it on its own line kind bug label build officer kind enhancement what happened what you expected to happen test should pass how to reproduce it as minimally and precisely as possible anything else we need to know environment kubevirt version use virtctl version kubernetes version use kubectl version vm or vmi specifications cloud provider or hardware configuration os e g from etc os release kernel e g uname a install tools others
| 1
|
44,628
| 11,472,979,750
|
IssuesEvent
|
2020-02-09 20:26:40
|
spack/spack
|
https://api.github.com/repos/spack/spack
|
closed
|
incorrect intel-tbb sha256sums from #14783
|
build-error
|
I think yesterday's commit #14783 broke the checksums for the recent
intel-tbb versions.
The commit added:
```
version('2020.1', sha256='48d51c63b16787af54e1ee4aaf30042087f20564b4eecf9a032d5568bc2f0bf8')
version('2020.0', sha256='8eed2377ac62e6ac10af5a8303ce861e4525ffe491a061b48e8fe094fc741ce9')
version('2019.9', sha256='15652f5328cf00c576f065e5cd3eaf3317422fe82afb67a9bcec0dc065bd2abe')
```
But when I wget the tar files directly, I get a different sha256sum.
```
72cffaeac3b50b117c4e2279f9162308d35873b3e744aff5a088beff6f65c9af 2020_U1.tar.gz
db80f4f7abb95c2d08fe64abdc0a9250903e4c725f1c667ac517450de426023a 2020.tar.gz
15652f5328cf00c576f065e5cd3eaf3317422fe82afb67a9bcec0dc065bd2abe 2019_U9.tar.gz
```
So, 2019_U9 is correct, but the 2020 and 2020_U1 are not.
Also, the name of the 2020 tar file is `2020.tar.gz`, not
`2020_U0.tar.gz`.
I would just submit a PR to fix this, but this was part of a larger
commit that "updated" the versions of several intel packages. I don't
use the other ones (just tbb), so I don't know if those sha hashes
need fixing or not.
```
M var/spack/repos/builtin/packages/intel-daal/package.py
M var/spack/repos/builtin/packages/intel-ipp/package.py
M var/spack/repos/builtin/packages/intel-mkl-dnn/package.py
M var/spack/repos/builtin/packages/intel-mkl/package.py
M var/spack/repos/builtin/packages/intel-mpi/package.py
M var/spack/repos/builtin/packages/intel-parallel-studio/package.py
M var/spack/repos/builtin/packages/intel-pin/package.py
M var/spack/repos/builtin/packages/intel-tbb/package.py
```
Could someone check this and see who has the right sha256sum?
And check the other packages.
Thanks.
@robert-mijakovic
|
1.0
|
incorrect intel-tbb sha256sums from #14783 -
I think yesterday's commit #14783 broke the checksums for the recent
intel-tbb versions.
The commit added:
```
version('2020.1', sha256='48d51c63b16787af54e1ee4aaf30042087f20564b4eecf9a032d5568bc2f0bf8')
version('2020.0', sha256='8eed2377ac62e6ac10af5a8303ce861e4525ffe491a061b48e8fe094fc741ce9')
version('2019.9', sha256='15652f5328cf00c576f065e5cd3eaf3317422fe82afb67a9bcec0dc065bd2abe')
```
But when I wget the tar files directly, I get a different sha256sum.
```
72cffaeac3b50b117c4e2279f9162308d35873b3e744aff5a088beff6f65c9af 2020_U1.tar.gz
db80f4f7abb95c2d08fe64abdc0a9250903e4c725f1c667ac517450de426023a 2020.tar.gz
15652f5328cf00c576f065e5cd3eaf3317422fe82afb67a9bcec0dc065bd2abe 2019_U9.tar.gz
```
So, 2019_U9 is correct, but the 2020 and 2020_U1 are not.
Also, the name of the 2020 tar file is `2020.tar.gz`, not
`2020_U0.tar.gz`.
I would just submit a PR to fix this, but this was part of a larger
commit that "updated" the versions of several intel packages. I don't
use the other ones (just tbb), so I don't know if those sha hashes
need fixing or not.
```
M var/spack/repos/builtin/packages/intel-daal/package.py
M var/spack/repos/builtin/packages/intel-ipp/package.py
M var/spack/repos/builtin/packages/intel-mkl-dnn/package.py
M var/spack/repos/builtin/packages/intel-mkl/package.py
M var/spack/repos/builtin/packages/intel-mpi/package.py
M var/spack/repos/builtin/packages/intel-parallel-studio/package.py
M var/spack/repos/builtin/packages/intel-pin/package.py
M var/spack/repos/builtin/packages/intel-tbb/package.py
```
Could someone check this and see who has the right sha256sum?
And check the other packages.
Thanks.
@robert-mijakovic
|
build
|
incorrect intel tbb from i think yesterday s commit broke the checksums for the recent intel tbb versions the commit added version version version but when i wget the tar files directly i get a different tar gz tar gz tar gz so is correct but the and are not also the name of the tar file is tar gz not tar gz i would just submit a pr to fix this but this was part of a larger commit that updated the versions of several intel packages i don t use the other ones just tbb so i don t know if those sha hashes need fixing or not m var spack repos builtin packages intel daal package py m var spack repos builtin packages intel ipp package py m var spack repos builtin packages intel mkl dnn package py m var spack repos builtin packages intel mkl package py m var spack repos builtin packages intel mpi package py m var spack repos builtin packages intel parallel studio package py m var spack repos builtin packages intel pin package py m var spack repos builtin packages intel tbb package py could someone check this and see who has the right and check the other packages thanks robert mijakovic
| 1
|
138,520
| 5,342,921,070
|
IssuesEvent
|
2017-02-17 09:46:54
|
Pliohub/Plio
|
https://api.github.com/repos/Pliohub/Plio
|
closed
|
Add an Email address field to Org settings
|
resolved todo top priority
|
It should be disabled. It should contain current org owner's email.
|
1.0
|
Add an Email address field to Org settings - 
It should be disabled. It should contain current org owner's email.
|
non_build
|
add an email address field to org settings it should be disabled it should contain current org owner s email
| 0
|
112,509
| 17,089,883,494
|
IssuesEvent
|
2021-07-08 16:02:21
|
MohamedElashri/Zotero-Docker
|
https://api.github.com/repos/MohamedElashri/Zotero-Docker
|
closed
|
WS-2021-0090 (High) detected in findhit-util-0.2.9.tgz
|
security vulnerability
|
## WS-2021-0090 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>findhit-util-0.2.9.tgz</b></p></summary>
<p>general propose utils for javascript</p>
<p>Library home page: <a href="https://registry.npmjs.org/findhit-util/-/findhit-util-0.2.9.tgz">https://registry.npmjs.org/findhit-util/-/findhit-util-0.2.9.tgz</a></p>
<p>Path to dependency file: Zotero-Docker/stream-server/package.json</p>
<p>Path to vulnerable library: Zotero-Docker/stream-server/node_modules/findhit-util/package.json</p>
<p>
Dependency Hierarchy:
- findhit-proxywrap-0.3.12.tgz (Root Library)
- :x: **findhit-util-0.2.9.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/MohamedElashri/Zotero-Docker/commit/d9b3b08f65f152a5478ffe8bd588c83a3a7d0758">d9b3b08f65f152a5478ffe8bd588c83a3a7d0758</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>
Prototype pollution vulnerability in `findhit-util` versions 0.0.1 through 0.2.9 allows an attacker to cause a denial of service and may lead to remote code execution.
<p>Publish Date: 2021-05-09
<p>URL: <a href=https://github.com/findhit/util/blob/f51f7329be0c3fbe3d4379bc109e4c6ea3a83242/lib/core.js#L93>WS-2021-0090</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.2</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: Low
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
WS-2021-0090 (High) detected in findhit-util-0.2.9.tgz - ## WS-2021-0090 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>findhit-util-0.2.9.tgz</b></p></summary>
<p>general propose utils for javascript</p>
<p>Library home page: <a href="https://registry.npmjs.org/findhit-util/-/findhit-util-0.2.9.tgz">https://registry.npmjs.org/findhit-util/-/findhit-util-0.2.9.tgz</a></p>
<p>Path to dependency file: Zotero-Docker/stream-server/package.json</p>
<p>Path to vulnerable library: Zotero-Docker/stream-server/node_modules/findhit-util/package.json</p>
<p>
Dependency Hierarchy:
- findhit-proxywrap-0.3.12.tgz (Root Library)
- :x: **findhit-util-0.2.9.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/MohamedElashri/Zotero-Docker/commit/d9b3b08f65f152a5478ffe8bd588c83a3a7d0758">d9b3b08f65f152a5478ffe8bd588c83a3a7d0758</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>
Prototype pollution vulnerability in `findhit-util` versions 0.0.1 through 0.2.9 allows an attacker to cause a denial of service and may lead to remote code execution.
<p>Publish Date: 2021-05-09
<p>URL: <a href=https://github.com/findhit/util/blob/f51f7329be0c3fbe3d4379bc109e4c6ea3a83242/lib/core.js#L93>WS-2021-0090</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.2</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: Low
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_build
|
ws high detected in findhit util tgz ws high severity vulnerability vulnerable library findhit util tgz general propose utils for javascript library home page a href path to dependency file zotero docker stream server package json path to vulnerable library zotero docker stream server node modules findhit util package json dependency hierarchy findhit proxywrap tgz root library x findhit util tgz vulnerable library found in head commit a href found in base branch main vulnerability details prototype pollution vulnerability in findhit util versions through allows an attacker to cause a denial of service and may lead to remote code execution publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact low availability impact high for more information on scores click a href step up your open source security game with whitesource
| 0
|
4,070
| 2,964,542,366
|
IssuesEvent
|
2015-07-10 17:15:11
|
dart-lang/dev_compiler
|
https://api.github.com/repos/dart-lang/dev_compiler
|
closed
|
merge analyzer errors with static info
|
analyzer code health
|
The idea is that we use the same mechanism to report all errors. Currently analyzer errors don't hold a reference to the AstNode, so the integration is not trivial.
One option is to move away from storing static info per node (just store it by offset & length like the analyzer does). This might be OK since the codegen doesn't need all the static info, just some bits here and there.
|
1.0
|
merge analyzer errors with static info - The idea is that we use the same mechanism to report all errors. Currently analyzer errors don't hold a reference to the AstNode, so the integration is not trivial.
One option is to move away from storing static info per node (just store it by offset & length like the analyzer does). This might be OK since the codegen doesn't need all the static info, just some bits here and there.
|
non_build
|
merge analyzer errors with static info the idea is that we use the same mechanism to report all errors currently analyzer errors don t hold a reference to the astnode so the integration is not trivial one option is to move away from storing static info per node just store it by offset length like the analyzer does this might be ok since the codegen doesn t need all the static info just some bits here and there
| 0
|
358,512
| 25,194,919,192
|
IssuesEvent
|
2022-11-12 11:36:51
|
riccardoperra/codeimage
|
https://api.github.com/repos/riccardoperra/codeimage
|
closed
|
[INT] Task for 1.0 Deploy
|
documentation P1 next
|
### Which @codeimage/* package(s) are relevant/releated to the feature request?
codeimage, config, locale, highlight, ui
### Description
- [x] Big review of everything
- [x] Improve packages build speed
- [X] Improve and fix typings
- [X] Update README for contributions
- [x] Update packages documentation
- [x] Improve release/preview CI/CD workflow with Github Action
- [x] Improve feature stability
- [x] Add backend documentation
- [X] Fix CodeSandbox project run
|
1.0
|
[INT] Task for 1.0 Deploy - ### Which @codeimage/* package(s) are relevant/releated to the feature request?
codeimage, config, locale, highlight, ui
### Description
- [x] Big review of everything
- [x] Improve packages build speed
- [X] Improve and fix typings
- [X] Update README for contributions
- [x] Update packages documentation
- [x] Improve release/preview CI/CD workflow with Github Action
- [x] Improve feature stability
- [x] Add backend documentation
- [X] Fix CodeSandbox project run
|
non_build
|
task for deploy which codeimage package s are relevant releated to the feature request codeimage config locale highlight ui description big review of everything improve packages build speed improve and fix typings update readme for contributions update packages documentation improve release preview ci cd workflow with github action improve feature stability add backend documentation fix codesandbox project run
| 0
|
1,441
| 2,757,219,802
|
IssuesEvent
|
2015-04-27 13:48:33
|
travis-ci/travis-ci
|
https://api.github.com/repos/travis-ci/travis-ci
|
closed
|
travis-build: preserving the status in $?
|
travis-build
|
Whether make succeeds or fails $? is always 1.
<pre>
script:
- make -j 4
- COMPILE_RESULT=$?
- echo COMPILE_RESULT=${COMPILE_RESULT}
</pre>
output:
<pre>
..
The command "make -j 4" exited with 0.
$ COMPILE_RESULT=$?
The command "COMPILE_RESULT=$?" exited with 0.
$ echo COMPILE_RESULT=${COMPILE_RESULT}
COMPILE_RESULT=1
</pre>
|
1.0
|
travis-build: preserving the status in $? - Whether make succeeds or fails $? is always 1.
<pre>
script:
- make -j 4
- COMPILE_RESULT=$?
- echo COMPILE_RESULT=${COMPILE_RESULT}
</pre>
output:
<pre>
..
The command "make -j 4" exited with 0.
$ COMPILE_RESULT=$?
The command "COMPILE_RESULT=$?" exited with 0.
$ echo COMPILE_RESULT=${COMPILE_RESULT}
COMPILE_RESULT=1
</pre>
|
build
|
travis build preserving the status in whether make succeeds or fails is always script make j compile result echo compile result compile result output the command make j exited with compile result the command compile result exited with echo compile result compile result compile result
| 1
|
54,243
| 13,284,379,758
|
IssuesEvent
|
2020-08-24 06:09:46
|
tensorflow/tensorflow
|
https://api.github.com/repos/tensorflow/tensorflow
|
opened
|
I've got a build error for "Build a handwritten digit classifier app with TensorFlow Lite"
|
type:build/install
|
**System information**
- OS Platform: WIndows10
- Mobile device: AVD (Android 10.0(Google Play) API:29)
- TensorFlow installed from (source or binary): Google Colabo
- TensorFlow version: 2.3.0
- Python version: 3.7
- Installed using virtualenv? pip? conda?: Preinstalled in Google Colabo
- Bazel version (if compiling from source):
> Android Studio 4.0
> Build #AI-193.6911.18.40.6514223, built on May 21, 2020
> Runtime version: 1.8.0_242-release-1644-b01 amd64
> VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
> Windows 10 10.0
> GC: ParNew, ConcurrentMarkSweep
> Memory: 1237M
> Cores: 8
> Registry: ide.new.welcome.screen.force=true
> Non-Bundled Plugins: org.jetbrains.kotlin
**Describe the problem**
I followed TF lite trial site and at step 5(https://codelabs.developers.google.com/codelabs/digit-classifier-tflite/#5),
after pressing a "Run 'app'" button on Android Studio, I got the following error in Android Studio.
Only safe (?.) or non-null asserted (!!.) calls are allowed on a nullable receiver of type interpreter?
Following **interpreter** is highlighted.
private fun initializeInterpreter() {
// TODO: Read the model input shape from model file.
// Read input shape from model file
val inputShape = **interpreter**.getInputTensor(0).shape()
inputImageWidth = inputShape[1]
inputImageHeight = inputShape[2]
I'm a newbie of Android Studio, thus I have not been able to find any wrong configuration in it.
Could you give me any clue?
Thank you.
**Any other info / logs**
At the very first try, when I press the "Run 'app'" button, Android Studio attempted to install something version 28.0.3(maybe SDK?). However, it was not able to fetch the version.
I have never seen the same message, even if I delete all "example_master" folder and change the location and try again.
One more info.
Although I don't know the difference b/w 'start' project and 'finish' project, I tried 'finish' project w/ same "mnist.tflite" too.
Then, Android studio spitted "Compatible side by side NDK version was not found. Default is 21.0.6113669." error.
My build.gradle is below by the way.
> apply plugin: 'com.android.application'
> apply plugin: 'kotlin-android'
> apply plugin: 'kotlin-android-extensions'
>
> android {
> compileSdkVersion 29
> defaultConfig {
> applicationId "org.tensorflow.lite.codelabs.digitclassifier"
> minSdkVersion 21
> targetSdkVersion 29
> versionCode 1
> versionName "1.0"
> testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
> }
>
> // TODO: Add an option to avoid compressing TF Lite model file
> aaptOptions {
> noCompress "tflite"
> }
>
> buildTypes {
> release {
> minifyEnabled false
> proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
> }
> }
> }
>
> // Sanity check if you have trained and downloaded TF Lite model.
> preBuild.doFirst {
> assert file("./src/main/assets/mnist.tflite").exists() :
> "mnist.tflite not found. Make sure you have trained and " +
> "downloaded your TensorFlow Lite model to assets/ folder"
> }
>
> dependencies {
> implementation fileTree(dir: 'libs', include: ['*.jar'])
> implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
>
> // Support Libraries
> implementation 'androidx.appcompat:appcompat:1.1.0'
> implementation 'androidx.core:core-ktx:1.1.0'
> implementation 'androidx.constraintlayout:constraintlayout:1.1.3'
>
> // AndroidDraw Library
> implementation 'com.github.divyanshub024:AndroidDraw:v0.1'
>
> // Task API
> implementation "com.google.android.gms:play-services-tasks:17.0.0"
>
> //TODO: Add TF Lite
> implementation 'org.tensorflow:tensorflow-lite:2.0.0'
>
> testImplementation 'junit:junit:4.12'
> androidTestImplementation 'androidx.test:runner:1.2.0'
> androidTestImplementation 'androidx.test.espresso:espresso-core:3.2.0'
> }
I changed TF version, but each of them ended up w/ same error.
implementation 'org.tensorflow:tensorflow-lite:2.3.0'
implementation 'org.tensorflow:tensorflow-lite:2.2.0'
|
1.0
|
I've got a build error for "Build a handwritten digit classifier app with TensorFlow Lite" - **System information**
- OS Platform: WIndows10
- Mobile device: AVD (Android 10.0(Google Play) API:29)
- TensorFlow installed from (source or binary): Google Colabo
- TensorFlow version: 2.3.0
- Python version: 3.7
- Installed using virtualenv? pip? conda?: Preinstalled in Google Colabo
- Bazel version (if compiling from source):
> Android Studio 4.0
> Build #AI-193.6911.18.40.6514223, built on May 21, 2020
> Runtime version: 1.8.0_242-release-1644-b01 amd64
> VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
> Windows 10 10.0
> GC: ParNew, ConcurrentMarkSweep
> Memory: 1237M
> Cores: 8
> Registry: ide.new.welcome.screen.force=true
> Non-Bundled Plugins: org.jetbrains.kotlin
**Describe the problem**
I followed TF lite trial site and at step 5(https://codelabs.developers.google.com/codelabs/digit-classifier-tflite/#5),
after pressing a "Run 'app'" button on Android Studio, I got the following error in Android Studio.
Only safe (?.) or non-null asserted (!!.) calls are allowed on a nullable receiver of type interpreter?
Following **interpreter** is highlighted.
private fun initializeInterpreter() {
// TODO: Read the model input shape from model file.
// Read input shape from model file
val inputShape = **interpreter**.getInputTensor(0).shape()
inputImageWidth = inputShape[1]
inputImageHeight = inputShape[2]
I'm a newbie of Android Studio, thus I have not been able to find any wrong configuration in it.
Could you give me any clue?
Thank you.
**Any other info / logs**
At the very first try, when I press the "Run 'app'" button, Android Studio attempted to install something version 28.0.3(maybe SDK?). However, it was not able to fetch the version.
I have never seen the same message, even if I delete all "example_master" folder and change the location and try again.
One more info.
Although I don't know the difference b/w 'start' project and 'finish' project, I tried 'finish' project w/ same "mnist.tflite" too.
Then, Android studio spitted "Compatible side by side NDK version was not found. Default is 21.0.6113669." error.
My build.gradle is below by the way.
> apply plugin: 'com.android.application'
> apply plugin: 'kotlin-android'
> apply plugin: 'kotlin-android-extensions'
>
> android {
> compileSdkVersion 29
> defaultConfig {
> applicationId "org.tensorflow.lite.codelabs.digitclassifier"
> minSdkVersion 21
> targetSdkVersion 29
> versionCode 1
> versionName "1.0"
> testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
> }
>
> // TODO: Add an option to avoid compressing TF Lite model file
> aaptOptions {
> noCompress "tflite"
> }
>
> buildTypes {
> release {
> minifyEnabled false
> proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
> }
> }
> }
>
> // Sanity check if you have trained and downloaded TF Lite model.
> preBuild.doFirst {
> assert file("./src/main/assets/mnist.tflite").exists() :
> "mnist.tflite not found. Make sure you have trained and " +
> "downloaded your TensorFlow Lite model to assets/ folder"
> }
>
> dependencies {
> implementation fileTree(dir: 'libs', include: ['*.jar'])
> implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
>
> // Support Libraries
> implementation 'androidx.appcompat:appcompat:1.1.0'
> implementation 'androidx.core:core-ktx:1.1.0'
> implementation 'androidx.constraintlayout:constraintlayout:1.1.3'
>
> // AndroidDraw Library
> implementation 'com.github.divyanshub024:AndroidDraw:v0.1'
>
> // Task API
> implementation "com.google.android.gms:play-services-tasks:17.0.0"
>
> //TODO: Add TF Lite
> implementation 'org.tensorflow:tensorflow-lite:2.0.0'
>
> testImplementation 'junit:junit:4.12'
> androidTestImplementation 'androidx.test:runner:1.2.0'
> androidTestImplementation 'androidx.test.espresso:espresso-core:3.2.0'
> }
I changed TF version, but each of them ended up w/ same error.
implementation 'org.tensorflow:tensorflow-lite:2.3.0'
implementation 'org.tensorflow:tensorflow-lite:2.2.0'
|
build
|
i ve got a build error for build a handwritten digit classifier app with tensorflow lite system information os platform mobile device avd android google play api tensorflow installed from source or binary google colabo tensorflow version python version installed using virtualenv pip conda preinstalled in google colabo bazel version if compiling from source android studio build ai built on may runtime version release vm openjdk bit server vm by jetbrains s r o windows gc parnew concurrentmarksweep memory cores registry ide new welcome screen force true non bundled plugins org jetbrains kotlin describe the problem i followed tf lite trial site and at step after pressing a run app button on android studio i got the following error in android studio only safe or non null asserted calls are allowed on a nullable receiver of type interpreter following interpreter is highlighted private fun initializeinterpreter todo read the model input shape from model file read input shape from model file val inputshape interpreter getinputtensor shape inputimagewidth inputshape inputimageheight inputshape i m a newbie of android studio thus i have not been able to find any wrong configuration in it could you give me any clue thank you any other info logs at the very first try when i press the run app button android studio attempted to install something version maybe sdk however it was not able to fetch the version i have never seen the same message even if i delete all example master folder and change the location and try again one more info although i don t know the difference b w start project and finish project i tried finish project w same mnist tflite too then android studio spitted compatible side by side ndk version was not found default is error my build gradle is below by the way apply plugin com android application apply plugin kotlin android apply plugin kotlin android extensions android compilesdkversion defaultconfig applicationid org tensorflow lite codelabs digitclassifier minsdkversion targetsdkversion versioncode versionname testinstrumentationrunner androidx test runner androidjunitrunner todo add an option to avoid compressing tf lite model file aaptoptions nocompress tflite buildtypes release minifyenabled false proguardfiles getdefaultproguardfile proguard android optimize txt proguard rules pro sanity check if you have trained and downloaded tf lite model prebuild dofirst assert file src main assets mnist tflite exists mnist tflite not found make sure you have trained and downloaded your tensorflow lite model to assets folder dependencies implementation filetree dir libs include implementation org jetbrains kotlin kotlin stdlib kotlin version support libraries implementation androidx appcompat appcompat implementation androidx core core ktx implementation androidx constraintlayout constraintlayout androiddraw library implementation com github androiddraw task api implementation com google android gms play services tasks todo add tf lite implementation org tensorflow tensorflow lite testimplementation junit junit androidtestimplementation androidx test runner androidtestimplementation androidx test espresso espresso core i changed tf version but each of them ended up w same error implementation org tensorflow tensorflow lite implementation org tensorflow tensorflow lite
| 1
|
203,260
| 15,359,331,535
|
IssuesEvent
|
2021-03-01 15:44:32
|
open-telemetry/opentelemetry-java-instrumentation
|
https://api.github.com/repos/open-telemetry/opentelemetry-java-instrumentation
|
closed
|
Write integration tests for kubernetes-client
|
area:tests priority:p3 release:required-for-ga
|
Currently it only has unit tests.
Wondering if we can write tests for it similar to the `aws-sdk` tests by standing up a fake endpoint and having `aws-sdk` talk to it.
Also, it looks like `kubernetes-client` uses `okhttp3`, so this would allow us to test with `:instrumentation:okhttp:okhttp-3.0` and verify that we aren't getting duplicate `CLIENT` spans.
|
1.0
|
Write integration tests for kubernetes-client - Currently it only has unit tests.
Wondering if we can write tests for it similar to the `aws-sdk` tests by standing up a fake endpoint and having `aws-sdk` talk to it.
Also, it looks like `kubernetes-client` uses `okhttp3`, so this would allow us to test with `:instrumentation:okhttp:okhttp-3.0` and verify that we aren't getting duplicate `CLIENT` spans.
|
non_build
|
write integration tests for kubernetes client currently it only has unit tests wondering if we can write tests for it similar to the aws sdk tests by standing up a fake endpoint and having aws sdk talk to it also it looks like kubernetes client uses so this would allow us to test with instrumentation okhttp okhttp and verify that we aren t getting duplicate client spans
| 0
|
74,169
| 20,047,689,772
|
IssuesEvent
|
2022-02-03 00:01:58
|
camunda-community-hub/camunda-bpm-camel
|
https://api.github.com/repos/camunda-community-hub/camunda-bpm-camel
|
closed
|
update to camunda 7.16
|
build
|
to be able to use the latest supported spring boot version (see #78 ) we should bring the extension to camunda 7.16.
|
1.0
|
update to camunda 7.16 - to be able to use the latest supported spring boot version (see #78 ) we should bring the extension to camunda 7.16.
|
build
|
update to camunda to be able to use the latest supported spring boot version see we should bring the extension to camunda
| 1
|
24,471
| 17,291,979,151
|
IssuesEvent
|
2021-07-25 00:13:04
|
rust-ml/linfa
|
https://api.github.com/repos/rust-ml/linfa
|
closed
|
Fix the CI
|
infrastructure
|
Right now the CI is broken for two reasons I know of. Firstly, the newest version of `thiserror`(1.0.26) breaks Clippy on older versions. This can be sidestepped by locking `thiserror` to an older version, but I don't see the value of running Clippy on older versions of Rust in the first place. We should only run code quality for stable Rust and maybe beta.
We are also pinning our version of nightly in CI. This was done because using the latest nightly caused occasional breakages in the past. Unfortunately our current nightly version is too old for some of our dependencies. We may be able to fix this by reverting back to using latest nightly, but I don't see the point in running nightly in CI since Linfa is used in stable Rust.
|
1.0
|
Fix the CI - Right now the CI is broken for two reasons I know of. Firstly, the newest version of `thiserror`(1.0.26) breaks Clippy on older versions. This can be sidestepped by locking `thiserror` to an older version, but I don't see the value of running Clippy on older versions of Rust in the first place. We should only run code quality for stable Rust and maybe beta.
We are also pinning our version of nightly in CI. This was done because using the latest nightly caused occasional breakages in the past. Unfortunately our current nightly version is too old for some of our dependencies. We may be able to fix this by reverting back to using latest nightly, but I don't see the point in running nightly in CI since Linfa is used in stable Rust.
|
non_build
|
fix the ci right now the ci is broken for two reasons i know of firstly the newest version of thiserror breaks clippy on older versions this can be sidestepped by locking thiserror to an older version but i don t see the value of running clippy on older versions of rust in the first place we should only run code quality for stable rust and maybe beta we are also pinning our version of nightly in ci this was done because using the latest nightly caused occasional breakages in the past unfortunately our current nightly version is too old for some of our dependencies we may be able to fix this by reverting back to using latest nightly but i don t see the point in running nightly in ci since linfa is used in stable rust
| 0
|
87,103
| 25,034,099,626
|
IssuesEvent
|
2022-11-04 14:41:19
|
dotnet/arcade
|
https://api.github.com/repos/dotnet/arcade
|
closed
|
Build failed: arcade-services-internal-ci/main #20221104.1
|
Build Failed
|
Build [#20221104.1](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_build/results?buildId=2037187) failed
## :x: : internal / arcade-services-internal-ci failed
### Summary
**Finished** - Fri, 04 Nov 2022 14:22:27 GMT
**Duration** - 222 minutes
**Requested for** - DotNet Bot
**Reason** - batchedCI
### Details
#### Validate deployment
- :x: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/302) - The job running on agent NetCore1ESPool-Internal 4 ran longer than the maximum time of 90 minutes. For more information, see https://go.microsoft.com/fwlink/?linkid=2077134
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/279) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/279) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/279) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/280) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/280) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/280) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/281) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/281) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/281) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/282) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/282) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/282) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :x: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/299) - The operation was canceled.
#### Validate Build Assets
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/97) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/97) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/97) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/98) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/98) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/98) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/99) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/99) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/99) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/100) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/100) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/100) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/101) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/101) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/101) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/102) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/102) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/102) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/103) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/103) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/103) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/104) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/104) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/104) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/105) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/105) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/105) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/106) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/106) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/106) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/110) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/110) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/110) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/113) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/113) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/113) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/114) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/114) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/114) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/115) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/115) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/115) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/116) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/116) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/116) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/118) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/118) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/118) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/119) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/119) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/119) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/120) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/120) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/120) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/121) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/121) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/121) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/122) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/122) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/122) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/123) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/123) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/123) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/124) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/124) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/124) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
#### Deploy
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/212) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/212) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/212) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/213) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/213) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/213) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/230) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/230) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/230) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/231) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/231) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/231) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/191) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/191) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/191) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/192) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/192) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/192) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/185) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/185) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/185) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/186) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/186) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/186) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/244) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/244) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/244) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/245) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/245) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/245) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
#### Post-Deployment
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/267) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/267) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/267) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/268) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/268) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/268) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/269) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/269) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/269) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/270) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/270) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/270) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/271) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/271) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/271) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/272) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/272) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/272) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
#### Build
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/5) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/5) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/5) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/6) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/6) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/6) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/7) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/7) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/7) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/8) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/8) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/8) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/9) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/9) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/9) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/10) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/10) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/10) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/11) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/11) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/11) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/12) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/12) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/12) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/29) - Component Governance detected 2 security related alerts at or above 'High' severity. Microsoft’s Open Source policy requires that all high and critical security vulnerabilities found by this task be addressed by upgrading vulnerable components. Vulnerabilities in indirect dependencies should be addressed by upgrading the root dependency.
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/29) - Component Governance detected 2 security alert(s) at or above 'High' severity that need to be resolved. On their Due date these alerts will break the build.
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/29) - The Component Detection tool partially succeeded. See the logs for more information.
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/61) - Component Governance detected 2 security related alerts at or above 'High' severity. Microsoft’s Open Source policy requires that all high and critical security vulnerabilities found by this task be addressed by upgrading vulnerable components. Vulnerabilities in indirect dependencies should be addressed by upgrading the root dependency.
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/61) - Component Governance detected 2 security alert(s) at or above 'High' severity that need to be resolved. On their Due date these alerts will break the build.
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/61) - The Component Detection tool partially succeeded. See the logs for more information.
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/72) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/72) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/72) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/73) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/73) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/73) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/74) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/74) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/74) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/75) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/75) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/75) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
#### Publish using Darc
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/169) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/169) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/169) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/170) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/170) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/170) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/171) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/171) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/171) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/172) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/172) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/172) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/173) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/173) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/173) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/174) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/174) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/174) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/175) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/175) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/175) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/176) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/176) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/176) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/177) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/177) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/177) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/178) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/178) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/178) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
### Changes
- [0de63510](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/0de63510204195ad9806cffd7e37b215a98942b9) - Přemek Vysoký - Keep `tarball/content` and VMR's root synchronized always (#2086)
- [624325c7](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/624325c776856052bb708da6b255448e714b15e3) - Chad Nedzlek - Expose Console.In for some command line apps
- [d2e30ce1](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/d2e30ce1f0e158b0ae2de179b9307eb0b8fb8f42) - Chad Nedzlek - Expose Console.In for some command line apps
- [785cfc67](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/785cfc67c1c01cc6d465e4824ebf3a64fd75e2b3) - Kyaw Thant - Use --config-env to pass in user and pat (#2081)
- [51918ca4](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/51918ca4d38bbd917ef47d610e95c4cb038e3e76) - dotnet-maestro[bot] - Update dependencies from https://github.com/dotnet/arcade build 20221031.5 (#2084)
- [cc8a2aea](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/cc8a2aea1dc604f3572d32e464f17fbae3a0bcd6) - Přemek Vysoký - Generate a list of components for VMR's main README (#2083)
- [8f3e0e5f](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/8f3e0e5ff5625245c5c092f53d110f3b302aebe6) - Chad Nedzlek - Add aliases to commands
- [65928566](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/659285662336369ae6caee3f77a3680884914dfe) - Chad Nedzlek - -p to --project because of warnings
- [36aa6bcd](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/36aa6bcd00a0acb3ad24ab08f26089d651242c9e) - Chad Nedzlek - -p to --project because of warnings
- [274a18c0](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/274a18c07ce5b0ff425c8a225b4a5db6f510c0a6) - Chad Nedzlek - Wrong helper overload
|
1.0
|
Build failed: arcade-services-internal-ci/main #20221104.1 - Build [#20221104.1](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_build/results?buildId=2037187) failed
## :x: : internal / arcade-services-internal-ci failed
### Summary
**Finished** - Fri, 04 Nov 2022 14:22:27 GMT
**Duration** - 222 minutes
**Requested for** - DotNet Bot
**Reason** - batchedCI
### Details
#### Validate deployment
- :x: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/302) - The job running on agent NetCore1ESPool-Internal 4 ran longer than the maximum time of 90 minutes. For more information, see https://go.microsoft.com/fwlink/?linkid=2077134
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/279) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/279) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/279) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/280) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/280) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/280) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/281) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/281) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/281) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/282) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/282) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/282) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :x: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/299) - The operation was canceled.
#### Validate Build Assets
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/97) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/97) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/97) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/98) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/98) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/98) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/99) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/99) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/99) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/100) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/100) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/100) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/101) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/101) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/101) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/102) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/102) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/102) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/103) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/103) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/103) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/104) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/104) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/104) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/105) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/105) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/105) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/106) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/106) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/106) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/110) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/110) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/110) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/113) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/113) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/113) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/114) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/114) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/114) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/115) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/115) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/115) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/116) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/116) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/116) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/118) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/118) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/118) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/119) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/119) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/119) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/120) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/120) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/120) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/121) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/121) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/121) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/122) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/122) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/122) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/123) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/123) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/123) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/124) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/124) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/124) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
#### Deploy
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/212) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/212) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/212) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/213) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/213) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/213) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/230) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/230) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/230) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/231) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/231) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/231) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/191) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/191) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/191) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/192) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/192) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/192) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/185) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/185) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/185) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/186) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/186) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/186) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/244) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/244) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/244) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/245) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/245) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/245) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
#### Post-Deployment
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/267) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/267) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/267) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/268) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/268) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/268) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/269) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/269) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/269) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/270) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/270) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/270) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/271) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/271) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/271) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/272) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/272) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/272) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
#### Build
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/5) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/5) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/5) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/6) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/6) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/6) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/7) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/7) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/7) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/8) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/8) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/8) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/9) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/9) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/9) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/10) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/10) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/10) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/11) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/11) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/11) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/12) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/12) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/12) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/29) - Component Governance detected 2 security related alerts at or above 'High' severity. Microsoft’s Open Source policy requires that all high and critical security vulnerabilities found by this task be addressed by upgrading vulnerable components. Vulnerabilities in indirect dependencies should be addressed by upgrading the root dependency.
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/29) - Component Governance detected 2 security alert(s) at or above 'High' severity that need to be resolved. On their Due date these alerts will break the build.
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/29) - The Component Detection tool partially succeeded. See the logs for more information.
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/61) - Component Governance detected 2 security related alerts at or above 'High' severity. Microsoft’s Open Source policy requires that all high and critical security vulnerabilities found by this task be addressed by upgrading vulnerable components. Vulnerabilities in indirect dependencies should be addressed by upgrading the root dependency.
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/61) - Component Governance detected 2 security alert(s) at or above 'High' severity that need to be resolved. On their Due date these alerts will break the build.
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/61) - The Component Detection tool partially succeeded. See the logs for more information.
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/72) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/72) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/72) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/73) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/73) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/73) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/74) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/74) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/74) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/75) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/75) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/75) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
#### Publish using Darc
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/169) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/169) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/169) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/170) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/170) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/170) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/171) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/171) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/171) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/172) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/172) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/172) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/173) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/173) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/173) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/174) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/174) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/174) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/175) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/175) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/175) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/176) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/176) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/176) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/177) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/177) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/177) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/178) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/178) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2037187/logs/178) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
### Changes
- [0de63510](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/0de63510204195ad9806cffd7e37b215a98942b9) - Přemek Vysoký - Keep `tarball/content` and VMR's root synchronized always (#2086)
- [624325c7](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/624325c776856052bb708da6b255448e714b15e3) - Chad Nedzlek - Expose Console.In for some command line apps
- [d2e30ce1](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/d2e30ce1f0e158b0ae2de179b9307eb0b8fb8f42) - Chad Nedzlek - Expose Console.In for some command line apps
- [785cfc67](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/785cfc67c1c01cc6d465e4824ebf3a64fd75e2b3) - Kyaw Thant - Use --config-env to pass in user and pat (#2081)
- [51918ca4](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/51918ca4d38bbd917ef47d610e95c4cb038e3e76) - dotnet-maestro[bot] - Update dependencies from https://github.com/dotnet/arcade build 20221031.5 (#2084)
- [cc8a2aea](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/cc8a2aea1dc604f3572d32e464f17fbae3a0bcd6) - Přemek Vysoký - Generate a list of components for VMR's main README (#2083)
- [8f3e0e5f](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/8f3e0e5ff5625245c5c092f53d110f3b302aebe6) - Chad Nedzlek - Add aliases to commands
- [65928566](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/659285662336369ae6caee3f77a3680884914dfe) - Chad Nedzlek - -p to --project because of warnings
- [36aa6bcd](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/36aa6bcd00a0acb3ad24ab08f26089d651242c9e) - Chad Nedzlek - -p to --project because of warnings
- [274a18c0](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/274a18c07ce5b0ff425c8a225b4a5db6f510c0a6) - Chad Nedzlek - Wrong helper overload
|
build
|
build failed arcade services internal ci main build failed x internal arcade services internal ci failed summary finished fri nov gmt duration minutes requested for dotnet bot reason batchedci details validate deployment x the job running on agent internal ran longer than the maximum time of minutes for more information see warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json x the operation was canceled validate build assets warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json deploy warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json post deployment warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json build warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning component governance detected security related alerts at or above high severity microsoft’s open source policy requires that all high and critical security vulnerabilities found by this task be addressed by upgrading vulnerable components vulnerabilities in indirect dependencies should be addressed by upgrading the root dependency warning component governance detected security alert s at or above high severity that need to be resolved on their due date these alerts will break the build warning the component detection tool partially succeeded see the logs for more information warning component governance detected security related alerts at or above high severity microsoft’s open source policy requires that all high and critical security vulnerabilities found by this task be addressed by upgrading vulnerable components vulnerabilities in indirect dependencies should be addressed by upgrading the root dependency warning component governance detected security alert s at or above high severity that need to be resolved on their due date these alerts will break the build warning the component detection tool partially succeeded see the logs for more information warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json publish using darc warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json warning resource file has already set to d a work tasks azurekeyvault node modules azure pipelines tasks azure arm rest module json changes přemek vysoký keep tarball content and vmr s root synchronized always chad nedzlek expose console in for some command line apps chad nedzlek expose console in for some command line apps kyaw thant use config env to pass in user and pat dotnet maestro update dependencies from build přemek vysoký generate a list of components for vmr s main readme chad nedzlek add aliases to commands chad nedzlek p to project because of warnings chad nedzlek p to project because of warnings chad nedzlek wrong helper overload
| 1
|
276,158
| 20,971,510,187
|
IssuesEvent
|
2022-03-28 11:50:44
|
rsource-open-source/rsource.community
|
https://api.github.com/repos/rsource-open-source/rsource.community
|
opened
|
Dockerize for Local Development
|
documentation enhancement
|
- [ ] Create sh/psh file in replacement of git clone
- [ ] Dockerfile
- [ ] Document setup process
|
1.0
|
Dockerize for Local Development - - [ ] Create sh/psh file in replacement of git clone
- [ ] Dockerfile
- [ ] Document setup process
|
non_build
|
dockerize for local development create sh psh file in replacement of git clone dockerfile document setup process
| 0
|
41,651
| 10,758,465,152
|
IssuesEvent
|
2019-10-31 15:01:37
|
atc0005/elbow
|
https://api.github.com/repos/atc0005/elbow
|
opened
|
Update GitHub Actions Workflow to use Makefile for installing linting tools
|
CI builds linting
|
This would allow the same steps to be used locally as well as remotely by CI.
|
1.0
|
Update GitHub Actions Workflow to use Makefile for installing linting tools - This would allow the same steps to be used locally as well as remotely by CI.
|
build
|
update github actions workflow to use makefile for installing linting tools this would allow the same steps to be used locally as well as remotely by ci
| 1
|
283,641
| 21,321,252,772
|
IssuesEvent
|
2022-04-17 05:24:44
|
ru2saig/xfce4-kind-plugin
|
https://api.github.com/repos/ru2saig/xfce4-kind-plugin
|
closed
|
Add a section in the README with resources and links
|
documentation
|
See NOTES in the local repo, as well as bookmarks
|
1.0
|
Add a section in the README with resources and links - See NOTES in the local repo, as well as bookmarks
|
non_build
|
add a section in the readme with resources and links see notes in the local repo as well as bookmarks
| 0
|
67,109
| 27,725,512,809
|
IssuesEvent
|
2023-03-15 01:39:44
|
kenkit/neon_service
|
https://api.github.com/repos/kenkit/neon_service
|
closed
|
[121625] neon_service.exe: ExecuteHandler2@20, ExecuteHandler@20, UtilitiesPlugin::notify_que, std::for_each<std::_Vector_ite...
|
neon_service_crash wait_for_updates
|
<table>
<tr>
<td><img src='https://backtrace.io/images/icon.png' width=30 height=30 /></td>
<td><b><a href="https://neon.sp.backtrace.io/dashboard/neon/project/neon/group/121625e046f076b6e9099d7e4795d426d4deb7c7eaf4835d8cfc566b33853b1e">New error: [neon]</a></b><br /><b>1</b> occurrence since (Fri Nov 15 2019 11:27:39)<br /></td>
</tr>
</table><table>
<tr><td><strong>Application</strong></td><td>neon_service.exe</td></tr>
<tr>
<td><strong>Attributes</strong></td>
<td>
<strong>error.message</strong> — 1
<ul>
<li><code>STATUS_FATAL_APP_EXIT: {Fatal Application Exit} %hs</code> — 1</li></ul><br>
<strong>version</strong> — 1
<ul>
<li><code>1.0.446</code> — 1</li></ul><br>
<strong>product_name</strong> — 1
<ul>
<li><code>*</code> — 1</li></ul><br></td>
</tr>
<tr>
<td><strong>Classifiers</strong></td>
<td>
<strong>exception</strong><br></td>
</tr>
<tr>
<td><strong>Frames</strong></td>
<td>
<code>
ExecuteHandler2@20
ExecuteHandler@20
UtilitiesPlugin::notify_que
std::for_each<std::_Vector_iterator<std::_Vector_val<std::_Simple_types<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > > >,<lambda_f8b23e02614aa163451097531188488b> >
WssPlugin::handle_response
std::_Invoker_ret<void>::_Call<<lambda_736d349d46f21b39c5f20d0988717bdb> &,std::shared_ptr<SimpleWeb::SocketServerBase<boost::asio::basic_stream_socket<boost::asio::ip::tcp,boost::asio::any_io_executor> >::Connection>,std::shared_ptr<SimpleWeb::SocketServerBase<boost::asio::basic_stream_socket<boost::asio::ip::tcp,boost::asio::any_io_executor> >::InMessage> >
std::_Func_impl_no_alloc<<lambda_736d349d46f21b39c5f20d0988717bdb>,void,std::shared_ptr<SimpleWeb::SocketServerBase<boost::asio::basic_stream_socket<boost::asio::ip::tcp,boost::asio::any_io_executor> >::Connection>,std::shared_ptr<SimpleWeb::SocketServerBase<boost::asio::basic_stream_socket<boost::asio::ip::tcp,boost::asio::any_io_executor> >::InMessage> >::_Do_call
boost::asio::asio_handler_invoke<boost::asio::detail::binder2<boost::asio::detail::read_dynbuf_v1_op<boost::asio::basic_stream_socket<boost::asio::ip::tcp,boost::asio::any_io_executor>,boost::asio::basic_streambuf_ref<std::allocator<char> >,boost::asio::detail::transfer_exactly_t,<lambda_2cbb75cc50a33860b82dd4f8d9553f44> >,boost::system::error_code,unsigned int> >
boost_asio_handler_invoke_helpers::invoke<boost::asio::detail::binder2<boost::asio::detail::read_dynbuf_v1_op<boost::asio::basic_stream_socket<boost::asio::ip::tcp,boost::asio::any_io_executor>,boost::asio::basic_streambuf_ref<std::allocator<char> >,boost::asio::detail::transfer_exactly_t,<lambda_2cbb75cc50a33860b82dd4f8d9553f44> >,boost::system::error_code,unsigned int>,<lambda_2cbb75cc50a33860b82dd4f8d9553f44> >
boost::asio::detail::asio_handler_invoke<boost::asio::detail::binder2<boost::asio::detail::read_dynbuf_v1_op<boost::asio::basic_stream_socket<boost::asio::ip::tcp,boost::asio::any_io_executor>,boost::asio::basic_streambuf_ref<std::allocator<char> >,boost::asio::detail::transfer_exactly_t,<lambda_2cbb75cc50a33860b82dd4f8d9553f44> >,boost::system::error_code,unsigned int>,boost::asio::basic_stream_socket<boost::asio::ip::tcp,boost::asio::any_io_executor>,boost::asio::basic_streambuf_ref<std::allocator<char> >,boost::asio::detail::transfer_exactly_t,<lambda_2cbb75cc50a33860b82dd4f8d9553f44> >
boost_asio_handler_invoke_helpers::invoke<boost::asio::detail::binder2<boost::asio::detail::read_dynbuf_v1_op<boost::asio::basic_stream_socket<boost::asio::ip::tcp,boost::asio::any_io_executor>,boost::asio::basic_streambuf_ref<std::allocator<char> >,boost::asio::detail::transfer_exactly_t,<lambda_2cbb75cc50a33860b82dd4f8d9553f44> >,boost::system::error_code,unsigned int>,boost::asio::detail::read_dynbuf_v1_op<boost::asio::basic_stream_socket<boost::asio::ip::tcp,boost::asio::any_io_executor>,boost::asio::basic_streambuf_ref<std::allocator<char> >,boost::asio::detail::transfer_exactly_t,<lambda_2cbb75cc50a33860b82dd4f8d9553f44> > >
boost::asio::detail::handler_work<boost::asio::detail::read_dynbuf_v1_op<boost::asio::basic_stream_socket<boost::asio::ip::tcp,boost::asio::any_io_executor>,boost::asio::basic_streambuf_ref<std::allocator<char> >,boost::asio::detail::transfer_exactly_t,<lambda_2cbb75cc50a33860b82dd4f8d9553f44> >,boost::asio::any_io_executor,void>::complete<boost::asio::detail::binder2<boost::asio::detail::read_dynbuf_v1_op<boost::asio::basic_stream_socket<boost::asio::ip::tcp,boost::asio::any_io_executor>,boost::asio::basic_streambuf_ref<std::allocator<char> >,boost::asio::detail::transfer_exactly_t,<lambda_2cbb75cc50a33860b82dd4f8d9553f44> >,boost::system::error_code,unsigned int> >
boost::asio::detail::win_iocp_operation::complete
boost::asio::detail::win_iocp_io_context::do_one
boost::asio::detail::win_iocp_io_context::run
boost::asio::io_context::run
SimpleWeb::SocketServerBase<boost::asio::basic_stream_socket<boost::asio::ip::tcp,boost::asio::any_io_executor> >::start(std::function<void __cdecl
std::thread::_Invoke<std::tuple<<lambda_cee478e0dbf0b7545e51d6e19366f0a7> >,0></code>
</td>
</tr></table>
|
1.0
|
[121625] neon_service.exe: ExecuteHandler2@20, ExecuteHandler@20, UtilitiesPlugin::notify_que, std::for_each<std::_Vector_ite... - <table>
<tr>
<td><img src='https://backtrace.io/images/icon.png' width=30 height=30 /></td>
<td><b><a href="https://neon.sp.backtrace.io/dashboard/neon/project/neon/group/121625e046f076b6e9099d7e4795d426d4deb7c7eaf4835d8cfc566b33853b1e">New error: [neon]</a></b><br /><b>1</b> occurrence since (Fri Nov 15 2019 11:27:39)<br /></td>
</tr>
</table><table>
<tr><td><strong>Application</strong></td><td>neon_service.exe</td></tr>
<tr>
<td><strong>Attributes</strong></td>
<td>
<strong>error.message</strong> — 1
<ul>
<li><code>STATUS_FATAL_APP_EXIT: {Fatal Application Exit} %hs</code> — 1</li></ul><br>
<strong>version</strong> — 1
<ul>
<li><code>1.0.446</code> — 1</li></ul><br>
<strong>product_name</strong> — 1
<ul>
<li><code>*</code> — 1</li></ul><br></td>
</tr>
<tr>
<td><strong>Classifiers</strong></td>
<td>
<strong>exception</strong><br></td>
</tr>
<tr>
<td><strong>Frames</strong></td>
<td>
<code>
ExecuteHandler2@20
ExecuteHandler@20
UtilitiesPlugin::notify_que
std::for_each<std::_Vector_iterator<std::_Vector_val<std::_Simple_types<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > > >,<lambda_f8b23e02614aa163451097531188488b> >
WssPlugin::handle_response
std::_Invoker_ret<void>::_Call<<lambda_736d349d46f21b39c5f20d0988717bdb> &,std::shared_ptr<SimpleWeb::SocketServerBase<boost::asio::basic_stream_socket<boost::asio::ip::tcp,boost::asio::any_io_executor> >::Connection>,std::shared_ptr<SimpleWeb::SocketServerBase<boost::asio::basic_stream_socket<boost::asio::ip::tcp,boost::asio::any_io_executor> >::InMessage> >
std::_Func_impl_no_alloc<<lambda_736d349d46f21b39c5f20d0988717bdb>,void,std::shared_ptr<SimpleWeb::SocketServerBase<boost::asio::basic_stream_socket<boost::asio::ip::tcp,boost::asio::any_io_executor> >::Connection>,std::shared_ptr<SimpleWeb::SocketServerBase<boost::asio::basic_stream_socket<boost::asio::ip::tcp,boost::asio::any_io_executor> >::InMessage> >::_Do_call
boost::asio::asio_handler_invoke<boost::asio::detail::binder2<boost::asio::detail::read_dynbuf_v1_op<boost::asio::basic_stream_socket<boost::asio::ip::tcp,boost::asio::any_io_executor>,boost::asio::basic_streambuf_ref<std::allocator<char> >,boost::asio::detail::transfer_exactly_t,<lambda_2cbb75cc50a33860b82dd4f8d9553f44> >,boost::system::error_code,unsigned int> >
boost_asio_handler_invoke_helpers::invoke<boost::asio::detail::binder2<boost::asio::detail::read_dynbuf_v1_op<boost::asio::basic_stream_socket<boost::asio::ip::tcp,boost::asio::any_io_executor>,boost::asio::basic_streambuf_ref<std::allocator<char> >,boost::asio::detail::transfer_exactly_t,<lambda_2cbb75cc50a33860b82dd4f8d9553f44> >,boost::system::error_code,unsigned int>,<lambda_2cbb75cc50a33860b82dd4f8d9553f44> >
boost::asio::detail::asio_handler_invoke<boost::asio::detail::binder2<boost::asio::detail::read_dynbuf_v1_op<boost::asio::basic_stream_socket<boost::asio::ip::tcp,boost::asio::any_io_executor>,boost::asio::basic_streambuf_ref<std::allocator<char> >,boost::asio::detail::transfer_exactly_t,<lambda_2cbb75cc50a33860b82dd4f8d9553f44> >,boost::system::error_code,unsigned int>,boost::asio::basic_stream_socket<boost::asio::ip::tcp,boost::asio::any_io_executor>,boost::asio::basic_streambuf_ref<std::allocator<char> >,boost::asio::detail::transfer_exactly_t,<lambda_2cbb75cc50a33860b82dd4f8d9553f44> >
boost_asio_handler_invoke_helpers::invoke<boost::asio::detail::binder2<boost::asio::detail::read_dynbuf_v1_op<boost::asio::basic_stream_socket<boost::asio::ip::tcp,boost::asio::any_io_executor>,boost::asio::basic_streambuf_ref<std::allocator<char> >,boost::asio::detail::transfer_exactly_t,<lambda_2cbb75cc50a33860b82dd4f8d9553f44> >,boost::system::error_code,unsigned int>,boost::asio::detail::read_dynbuf_v1_op<boost::asio::basic_stream_socket<boost::asio::ip::tcp,boost::asio::any_io_executor>,boost::asio::basic_streambuf_ref<std::allocator<char> >,boost::asio::detail::transfer_exactly_t,<lambda_2cbb75cc50a33860b82dd4f8d9553f44> > >
boost::asio::detail::handler_work<boost::asio::detail::read_dynbuf_v1_op<boost::asio::basic_stream_socket<boost::asio::ip::tcp,boost::asio::any_io_executor>,boost::asio::basic_streambuf_ref<std::allocator<char> >,boost::asio::detail::transfer_exactly_t,<lambda_2cbb75cc50a33860b82dd4f8d9553f44> >,boost::asio::any_io_executor,void>::complete<boost::asio::detail::binder2<boost::asio::detail::read_dynbuf_v1_op<boost::asio::basic_stream_socket<boost::asio::ip::tcp,boost::asio::any_io_executor>,boost::asio::basic_streambuf_ref<std::allocator<char> >,boost::asio::detail::transfer_exactly_t,<lambda_2cbb75cc50a33860b82dd4f8d9553f44> >,boost::system::error_code,unsigned int> >
boost::asio::detail::win_iocp_operation::complete
boost::asio::detail::win_iocp_io_context::do_one
boost::asio::detail::win_iocp_io_context::run
boost::asio::io_context::run
SimpleWeb::SocketServerBase<boost::asio::basic_stream_socket<boost::asio::ip::tcp,boost::asio::any_io_executor> >::start(std::function<void __cdecl
std::thread::_Invoke<std::tuple<<lambda_cee478e0dbf0b7545e51d6e19366f0a7> >,0></code>
</td>
</tr></table>
|
non_build
|
neon service exe executehandler utilitiesplugin notify que std for each occurrence since fri nov application neon service exe attributes error message mdash status fatal app exit fatal application exit hs mdash version mdash mdash product name mdash mdash classifiers exception frames executehandler utilitiesplugin notify que std for each lt std vector iterator lt std vector val lt std simple types lt std basic string lt char std char traits lt char gt std allocator lt char gt gt gt gt gt lt lambda gt gt wssplugin handle response std invoker ret lt void gt call lt lt lambda gt amp std shared ptr lt simpleweb socketserverbase lt boost asio basic stream socket lt boost asio ip tcp boost asio any io executor gt gt connection gt std shared ptr lt simpleweb socketserverbase lt boost asio basic stream socket lt boost asio ip tcp boost asio any io executor gt gt inmessage gt gt std func impl no alloc lt lt lambda gt void std shared ptr lt simpleweb socketserverbase lt boost asio basic stream socket lt boost asio ip tcp boost asio any io executor gt gt connection gt std shared ptr lt simpleweb socketserverbase lt boost asio basic stream socket lt boost asio ip tcp boost asio any io executor gt gt inmessage gt gt do call boost asio asio handler invoke lt boost asio detail lt boost asio detail read dynbuf op lt boost asio basic stream socket lt boost asio ip tcp boost asio any io executor gt boost asio basic streambuf ref lt std allocator lt char gt gt boost asio detail transfer exactly t lt lambda gt gt boost system error code unsigned int gt gt boost asio handler invoke helpers invoke lt boost asio detail lt boost asio detail read dynbuf op lt boost asio basic stream socket lt boost asio ip tcp boost asio any io executor gt boost asio basic streambuf ref lt std allocator lt char gt gt boost asio detail transfer exactly t lt lambda gt gt boost system error code unsigned int gt lt lambda gt gt boost asio detail asio handler invoke lt boost asio detail lt boost asio detail read dynbuf op lt boost asio basic stream socket lt boost asio ip tcp boost asio any io executor gt boost asio basic streambuf ref lt std allocator lt char gt gt boost asio detail transfer exactly t lt lambda gt gt boost system error code unsigned int gt boost asio basic stream socket lt boost asio ip tcp boost asio any io executor gt boost asio basic streambuf ref lt std allocator lt char gt gt boost asio detail transfer exactly t lt lambda gt gt boost asio handler invoke helpers invoke lt boost asio detail lt boost asio detail read dynbuf op lt boost asio basic stream socket lt boost asio ip tcp boost asio any io executor gt boost asio basic streambuf ref lt std allocator lt char gt gt boost asio detail transfer exactly t lt lambda gt gt boost system error code unsigned int gt boost asio detail read dynbuf op lt boost asio basic stream socket lt boost asio ip tcp boost asio any io executor gt boost asio basic streambuf ref lt std allocator lt char gt gt boost asio detail transfer exactly t lt lambda gt gt gt boost asio detail handler work lt boost asio detail read dynbuf op lt boost asio basic stream socket lt boost asio ip tcp boost asio any io executor gt boost asio basic streambuf ref lt std allocator lt char gt gt boost asio detail transfer exactly t lt lambda gt gt boost asio any io executor void gt complete lt boost asio detail lt boost asio detail read dynbuf op lt boost asio basic stream socket lt boost asio ip tcp boost asio any io executor gt boost asio basic streambuf ref lt std allocator lt char gt gt boost asio detail transfer exactly t lt lambda gt gt boost system error code unsigned int gt gt boost asio detail win iocp operation complete boost asio detail win iocp io context do one boost asio detail win iocp io context run boost asio io context run simpleweb socketserverbase lt boost asio basic stream socket lt boost asio ip tcp boost asio any io executor gt gt start std function lt void cdecl std thread invoke lt std tuple lt lt lambda gt gt gt
| 0
|
68,308
| 17,213,656,946
|
IssuesEvent
|
2021-07-19 08:44:36
|
grafana/grafana
|
https://api.github.com/repos/grafana/grafana
|
closed
|
Grafana 8.0.5 - build RPM package -> Unknown command "pkg-rpm"
|
type/build-packaging
|
this always worked, but with 8.0.5 it throws an error.
````
root@lpgaixmgmtlx01:/scratch/go/dev/src/github.com/grafana/grafana>go run build.go build pkg-rpm
Version: 8.0.5, Linux Version: 8.0.5, Package Iteration: 1626352577
rm -r ./bin/linux-ppc64le/grafana-server
rm -r ./bin/linux-ppc64le/grafana-server.md5
go version
go version go1.16.6 linux/ppc64le
Targeting linux/ppc64le
go build -ldflags -w -X main.version=8.0.5 -X main.commit=cbb2aa5 -X main.buildstamp=1625740244 -X main.buildBranch=HEAD -o ./bin/linux-ppc64le/grafana-server ./pkg/cmd/grafana-server
rm -r ./bin/linux-ppc64le/grafana-cli
rm -r ./bin/linux-ppc64le/grafana-cli.md5
go version
go version go1.16.6 linux/ppc64le
Targeting linux/ppc64le
go build -ldflags -w -X main.version=8.0.5 -X main.commit=cbb2aa5 -X main.buildstamp=1625740244 -X main.buildBranch=HEAD -o ./bin/linux-ppc64le/grafana-cli ./pkg/cmd/grafana-cli
Unknown command "pkg-rpm"
exit status 1
````
so what is the newest sorcery to build an rpm package? i forced to build my as i am runnig on ppc64le.
go run build.go build creates the binaries as expected, but i need to package the whole thing (front / backedn) into an rpm.
root@lpgaixmgmtlx01:/scratch/go/dev/src/github.com/grafana/grafana>bin/linux-ppc64le/grafana-cli --version
Grafana CLI version 8.0.5
|
1.0
|
Grafana 8.0.5 - build RPM package -> Unknown command "pkg-rpm" - this always worked, but with 8.0.5 it throws an error.
````
root@lpgaixmgmtlx01:/scratch/go/dev/src/github.com/grafana/grafana>go run build.go build pkg-rpm
Version: 8.0.5, Linux Version: 8.0.5, Package Iteration: 1626352577
rm -r ./bin/linux-ppc64le/grafana-server
rm -r ./bin/linux-ppc64le/grafana-server.md5
go version
go version go1.16.6 linux/ppc64le
Targeting linux/ppc64le
go build -ldflags -w -X main.version=8.0.5 -X main.commit=cbb2aa5 -X main.buildstamp=1625740244 -X main.buildBranch=HEAD -o ./bin/linux-ppc64le/grafana-server ./pkg/cmd/grafana-server
rm -r ./bin/linux-ppc64le/grafana-cli
rm -r ./bin/linux-ppc64le/grafana-cli.md5
go version
go version go1.16.6 linux/ppc64le
Targeting linux/ppc64le
go build -ldflags -w -X main.version=8.0.5 -X main.commit=cbb2aa5 -X main.buildstamp=1625740244 -X main.buildBranch=HEAD -o ./bin/linux-ppc64le/grafana-cli ./pkg/cmd/grafana-cli
Unknown command "pkg-rpm"
exit status 1
````
so what is the newest sorcery to build an rpm package? i forced to build my as i am runnig on ppc64le.
go run build.go build creates the binaries as expected, but i need to package the whole thing (front / backedn) into an rpm.
root@lpgaixmgmtlx01:/scratch/go/dev/src/github.com/grafana/grafana>bin/linux-ppc64le/grafana-cli --version
Grafana CLI version 8.0.5
|
build
|
grafana build rpm package unknown command pkg rpm this always worked but with it throws an error root scratch go dev src github com grafana grafana go run build go build pkg rpm version linux version package iteration rm r bin linux grafana server rm r bin linux grafana server go version go version linux targeting linux go build ldflags w x main version x main commit x main buildstamp x main buildbranch head o bin linux grafana server pkg cmd grafana server rm r bin linux grafana cli rm r bin linux grafana cli go version go version linux targeting linux go build ldflags w x main version x main commit x main buildstamp x main buildbranch head o bin linux grafana cli pkg cmd grafana cli unknown command pkg rpm exit status so what is the newest sorcery to build an rpm package i forced to build my as i am runnig on go run build go build creates the binaries as expected but i need to package the whole thing front backedn into an rpm root scratch go dev src github com grafana grafana bin linux grafana cli version grafana cli version
| 1
|
380,326
| 26,413,672,249
|
IssuesEvent
|
2023-01-13 14:19:23
|
yugabyte/yugabyte-db
|
https://api.github.com/repos/yugabyte/yugabyte-db
|
opened
|
[Docs] CDC docs have two main pages and importation limitations are missing from one
|
area/documentation
|
### Description
Docs for CDC have different levels of detail between EXPLORE and DEVELOPER/ARCHITECTURE Topics:
* https://docs.yugabyte.com/preview/explore/change-data-capture/
* https://docs.yugabyte.com/preview/architecture/docdb-replication/change-data-capture/
With important limitations and issues in the EXPLORE version not mention nor linked from the other. The 2nd document should link to the first for further information so the important limitations and such are noted. Otherwise reading just that one you might not become aware of the other details.
|
1.0
|
[Docs] CDC docs have two main pages and importation limitations are missing from one - ### Description
Docs for CDC have different levels of detail between EXPLORE and DEVELOPER/ARCHITECTURE Topics:
* https://docs.yugabyte.com/preview/explore/change-data-capture/
* https://docs.yugabyte.com/preview/architecture/docdb-replication/change-data-capture/
With important limitations and issues in the EXPLORE version not mention nor linked from the other. The 2nd document should link to the first for further information so the important limitations and such are noted. Otherwise reading just that one you might not become aware of the other details.
|
non_build
|
cdc docs have two main pages and importation limitations are missing from one description docs for cdc have different levels of detail between explore and developer architecture topics with important limitations and issues in the explore version not mention nor linked from the other the document should link to the first for further information so the important limitations and such are noted otherwise reading just that one you might not become aware of the other details
| 0
|
76,248
| 21,314,844,277
|
IssuesEvent
|
2022-04-16 05:06:05
|
fusion44/blitz_api
|
https://api.github.com/repos/fusion44/blitz_api
|
opened
|
Remove gRPC as a hard dependency
|
v0.5.0-beta build
|
Currently gRPC is always installed, even if the user only runs Core Lightning.
The dependencies for the lightning backend must be installed by `pip` manually upon install:
* **LND**: `pip install grpcio grpcio-tools googleapis-common-protos protobuf`
* **CLN**: `pip install pyln-client`
|
1.0
|
Remove gRPC as a hard dependency - Currently gRPC is always installed, even if the user only runs Core Lightning.
The dependencies for the lightning backend must be installed by `pip` manually upon install:
* **LND**: `pip install grpcio grpcio-tools googleapis-common-protos protobuf`
* **CLN**: `pip install pyln-client`
|
build
|
remove grpc as a hard dependency currently grpc is always installed even if the user only runs core lightning the dependencies for the lightning backend must be installed by pip manually upon install lnd pip install grpcio grpcio tools googleapis common protos protobuf cln pip install pyln client
| 1
|
13,429
| 3,715,441,501
|
IssuesEvent
|
2016-03-03 01:45:07
|
boto/boto3
|
https://api.github.com/repos/boto/boto3
|
closed
|
listing the top level contents of a s3 bucket with Prefix and Delimiter
|
documentation enhancement
|
Apologies for what sounds like a very basic question. In [this example](http://docs.aws.amazon.com/AmazonS3/latest/dev/ListingKeysHierarchy.html) from the s3 docs is there a way to list the continents? I was hoping this might work, but it doesn't seem to:
```python
import boto3
s3 = boto3.resource('s3')
bucket = s3.Bucket('edsu-test-bucket')
for o in bucket.objects.filter(Delimiter='/'):
print(o.key)
```
However, the equivalent code using boto2 does seem to work the way I expect:
```python
import boto
s3 = boto.connect_s3()
bucket = s3.get_bucket('edsu-test-bucket')
for o in bucket.list(delimiter='/'):
print(o.name)
```
|
1.0
|
listing the top level contents of a s3 bucket with Prefix and Delimiter - Apologies for what sounds like a very basic question. In [this example](http://docs.aws.amazon.com/AmazonS3/latest/dev/ListingKeysHierarchy.html) from the s3 docs is there a way to list the continents? I was hoping this might work, but it doesn't seem to:
```python
import boto3
s3 = boto3.resource('s3')
bucket = s3.Bucket('edsu-test-bucket')
for o in bucket.objects.filter(Delimiter='/'):
print(o.key)
```
However, the equivalent code using boto2 does seem to work the way I expect:
```python
import boto
s3 = boto.connect_s3()
bucket = s3.get_bucket('edsu-test-bucket')
for o in bucket.list(delimiter='/'):
print(o.name)
```
|
non_build
|
listing the top level contents of a bucket with prefix and delimiter apologies for what sounds like a very basic question in from the docs is there a way to list the continents i was hoping this might work but it doesn t seem to python import resource bucket bucket edsu test bucket for o in bucket objects filter delimiter print o key however the equivalent code using does seem to work the way i expect python import boto boto connect bucket get bucket edsu test bucket for o in bucket list delimiter print o name
| 0
|
99,897
| 30,574,147,318
|
IssuesEvent
|
2023-07-21 02:47:00
|
apache/shardingsphere
|
https://api.github.com/repos/apache/shardingsphere
|
opened
|
refactor the github action to make workflows execute faster
|
type: refactor type: build
|
Sort out the following operations to make workflows faster:
- [ ] comile the nightly-build-artifact.yml and nightly-build-example.yml as nightly-build.yml
|
1.0
|
refactor the github action to make workflows execute faster - Sort out the following operations to make workflows faster:
- [ ] comile the nightly-build-artifact.yml and nightly-build-example.yml as nightly-build.yml
|
build
|
refactor the github action to make workflows execute faster sort out the following operations to make workflows faster comile the nightly build artifact yml and nightly build example yml as nightly build yml
| 1
|
4,134
| 3,296,519,835
|
IssuesEvent
|
2015-11-01 22:20:53
|
quicklisp/quicklisp-projects
|
https://api.github.com/repos/quicklisp/quicklisp-projects
|
closed
|
Please add fast-websocket
|
canbuild
|
fast-websocket is an optimized low-level WebSocket protocol parser/composer.
https://github.com/fukamachi/fast-websocket
|
1.0
|
Please add fast-websocket - fast-websocket is an optimized low-level WebSocket protocol parser/composer.
https://github.com/fukamachi/fast-websocket
|
build
|
please add fast websocket fast websocket is an optimized low level websocket protocol parser composer
| 1
|
50,055
| 12,466,360,987
|
IssuesEvent
|
2020-05-28 15:21:54
|
googleapis/nodejs-spanner
|
https://api.github.com/repos/googleapis/nodejs-spanner
|
opened
|
Mocha Tests: "before all" hook for "should throw an error for non-existant tables" failed
|
buildcop: issue priority: p1 type: bug
|
Note: #953 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
----
commit: 87c7edcb2c3ba729b1e278bb191b695b0cd376cb
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/d809bccb-e6c2-4aa2-9733-62067612193b), [Sponge](http://sponge2/d809bccb-e6c2-4aa2-9733-62067612193b)
status: failed
<details><summary>Test output</summary><br><pre>Timeout of 1600000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/tmpfs/src/github/nodejs-spanner/build/system-test/spanner.js)
Error: Timeout of 1600000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/tmpfs/src/github/nodejs-spanner/build/system-test/spanner.js)</pre></details>
|
1.0
|
Mocha Tests: "before all" hook for "should throw an error for non-existant tables" failed - Note: #953 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
----
commit: 87c7edcb2c3ba729b1e278bb191b695b0cd376cb
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/d809bccb-e6c2-4aa2-9733-62067612193b), [Sponge](http://sponge2/d809bccb-e6c2-4aa2-9733-62067612193b)
status: failed
<details><summary>Test output</summary><br><pre>Timeout of 1600000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/tmpfs/src/github/nodejs-spanner/build/system-test/spanner.js)
Error: Timeout of 1600000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/tmpfs/src/github/nodejs-spanner/build/system-test/spanner.js)</pre></details>
|
build
|
mocha tests before all hook for should throw an error for non existant tables failed note was also for this test but it was closed more than days ago so i didn t mark it flaky commit buildurl status failed test output timeout of exceeded for async tests and hooks ensure done is called if returning a promise ensure it resolves tmpfs src github nodejs spanner build system test spanner js error timeout of exceeded for async tests and hooks ensure done is called if returning a promise ensure it resolves tmpfs src github nodejs spanner build system test spanner js
| 1
|
285,601
| 21,526,266,232
|
IssuesEvent
|
2022-04-28 18:46:53
|
marcosjunior184/Wellmii
|
https://api.github.com/repos/marcosjunior184/Wellmii
|
opened
|
User case: 30 - 45
|
documentation
|
Documentation should contain:
- Age specifics ranging from 15 to 30.
- Consider scenarios such as using the app a home, at the gym, etc.
- Consider emotions such as anxiety, anger, depression, etc.
|
1.0
|
User case: 30 - 45 - Documentation should contain:
- Age specifics ranging from 15 to 30.
- Consider scenarios such as using the app a home, at the gym, etc.
- Consider emotions such as anxiety, anger, depression, etc.
|
non_build
|
user case documentation should contain age specifics ranging from to consider scenarios such as using the app a home at the gym etc consider emotions such as anxiety anger depression etc
| 0
|
50,241
| 12,486,437,763
|
IssuesEvent
|
2020-05-31 02:08:19
|
spack/spack
|
https://api.github.com/repos/spack/spack
|
closed
|
Installation issue: ssht should install headers into `include/ssht` subdir
|
build-error
|
The `ssht` package seems to install its header into the wrong location.
The `ssht` package uses `cp` to copy header files into the `include` directory of the install location. However, there is also an (unused) `install` target in the `CMakeFile`, which would install the header files into `include/ssht`.
How should this be resolved? I assume the long-term goal is to rely on the package's built-in mechanism as much as possible. However, this would be a breaking change. Are there guidelines or mechanisms for handling this?
|
1.0
|
Installation issue: ssht should install headers into `include/ssht` subdir - The `ssht` package seems to install its header into the wrong location.
The `ssht` package uses `cp` to copy header files into the `include` directory of the install location. However, there is also an (unused) `install` target in the `CMakeFile`, which would install the header files into `include/ssht`.
How should this be resolved? I assume the long-term goal is to rely on the package's built-in mechanism as much as possible. However, this would be a breaking change. Are there guidelines or mechanisms for handling this?
|
build
|
installation issue ssht should install headers into include ssht subdir the ssht package seems to install its header into the wrong location the ssht package uses cp to copy header files into the include directory of the install location however there is also an unused install target in the cmakefile which would install the header files into include ssht how should this be resolved i assume the long term goal is to rely on the package s built in mechanism as much as possible however this would be a breaking change are there guidelines or mechanisms for handling this
| 1
|
60,781
| 14,915,785,812
|
IssuesEvent
|
2021-01-22 17:12:55
|
tensorflow/tensorflow
|
https://api.github.com/repos/tensorflow/tensorflow
|
closed
|
Jupyter kernel restarts/crashes when importing Tensorflow, 'ModuleNotFoundError: No module named 'tensorflow' in Python CLI
|
TF 2.4 stat:awaiting response subtype:macOS type:build/install
|
**System information**
Using an M1 MacBook
I cannot use environment capture because the package is not being detected. I have tried the following: restarting computer, reinstalling Conda, reinstalling individual packages, installing using different package managers, setting up new environments, using different versions of python in different environments. It was working before and then suddenly stopped. I have seen reports of it being a memory issue, but it never occurred before, and I have 16GB of RAM, it should be more than enough.
**Describe the current behavior**
Jupyter kernel restarts/crashes when importing Tensorflow, 'ModuleNotFoundError: No module named 'tensorflow' in Python CLI
**Describe the expected behavior**
For it to import normally
Below is a video of the behaviour.
https://drive.google.com/file/d/11hCwbneKVdx0srZN9YxCyyIwDE8BKKQN/view?usp=sharing
<img width="724" alt="Screen Shot 2021-01-21 at 10 02 34 AM" src="https://user-images.githubusercontent.com/51058259/105384701-c9630600-5bcf-11eb-9f2c-53cb693ddf88.png">
<img width="723" alt="Screen Shot 2021-01-21 at 10 02 57 AM" src="https://user-images.githubusercontent.com/51058259/105384741-d7b12200-5bcf-11eb-850a-9a47cfb3c8ea.png">
|
1.0
|
Jupyter kernel restarts/crashes when importing Tensorflow, 'ModuleNotFoundError: No module named 'tensorflow' in Python CLI - **System information**
Using an M1 MacBook
I cannot use environment capture because the package is not being detected. I have tried the following: restarting computer, reinstalling Conda, reinstalling individual packages, installing using different package managers, setting up new environments, using different versions of python in different environments. It was working before and then suddenly stopped. I have seen reports of it being a memory issue, but it never occurred before, and I have 16GB of RAM, it should be more than enough.
**Describe the current behavior**
Jupyter kernel restarts/crashes when importing Tensorflow, 'ModuleNotFoundError: No module named 'tensorflow' in Python CLI
**Describe the expected behavior**
For it to import normally
Below is a video of the behaviour.
https://drive.google.com/file/d/11hCwbneKVdx0srZN9YxCyyIwDE8BKKQN/view?usp=sharing
<img width="724" alt="Screen Shot 2021-01-21 at 10 02 34 AM" src="https://user-images.githubusercontent.com/51058259/105384701-c9630600-5bcf-11eb-9f2c-53cb693ddf88.png">
<img width="723" alt="Screen Shot 2021-01-21 at 10 02 57 AM" src="https://user-images.githubusercontent.com/51058259/105384741-d7b12200-5bcf-11eb-850a-9a47cfb3c8ea.png">
|
build
|
jupyter kernel restarts crashes when importing tensorflow modulenotfounderror no module named tensorflow in python cli system information using an macbook i cannot use environment capture because the package is not being detected i have tried the following restarting computer reinstalling conda reinstalling individual packages installing using different package managers setting up new environments using different versions of python in different environments it was working before and then suddenly stopped i have seen reports of it being a memory issue but it never occurred before and i have of ram it should be more than enough describe the current behavior jupyter kernel restarts crashes when importing tensorflow modulenotfounderror no module named tensorflow in python cli describe the expected behavior for it to import normally below is a video of the behaviour img width alt screen shot at am src img width alt screen shot at am src
| 1
|
71,670
| 18,842,001,801
|
IssuesEvent
|
2021-11-11 10:39:22
|
appsmithorg/appsmith
|
https://api.github.com/repos/appsmithorg/appsmith
|
closed
|
[Bug]: Disabling the icon column type does not disable the icon
|
Bug Table Widget App Viewers Pod Low Production UI Building Pod Papercut
|
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Current Behavior
It is observed that by enabling the disable toggle of icon column type - User is still able to access the icon button column
https://loom.com/share/be8a17efc55847bbbe03625aa6a57481
### Steps To Reproduce
```markdown
1.Launch appsmith app in release or prod environment
2.Drag and drop table widget
3.Change any of the column type to icon
4.Disable the icon column type and observe
```
### Environment
Release
### Version
Cloud
|
1.0
|
[Bug]: Disabling the icon column type does not disable the icon - ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Current Behavior
It is observed that by enabling the disable toggle of icon column type - User is still able to access the icon button column
https://loom.com/share/be8a17efc55847bbbe03625aa6a57481
### Steps To Reproduce
```markdown
1.Launch appsmith app in release or prod environment
2.Drag and drop table widget
3.Change any of the column type to icon
4.Disable the icon column type and observe
```
### Environment
Release
### Version
Cloud
|
build
|
disabling the icon column type does not disable the icon is there an existing issue for this i have searched the existing issues current behavior it is observed that by enabling the disable toggle of icon column type user is still able to access the icon button column steps to reproduce markdown launch appsmith app in release or prod environment drag and drop table widget change any of the column type to icon disable the icon column type and observe environment release version cloud
| 1
|
113,840
| 17,156,284,912
|
IssuesEvent
|
2021-07-14 07:20:07
|
MOONGIFT/moongift.dev
|
https://api.github.com/repos/MOONGIFT/moongift.dev
|
opened
|
heartbeatsjp/check-tls-cert: Check-tls-cert is a TLS certificate checker.
|
Golang OSS Security
|
https://github.com/heartbeatsjp/check-tls-cert
Check-tls-cert is a TLS certificate checker. Contribute to heartbeatsjp/check-tls-cert development by creating an account on GitHub.
TLS証明書の有効性と証明書チェインの検証を行う。
|
True
|
heartbeatsjp/check-tls-cert: Check-tls-cert is a TLS certificate checker. - https://github.com/heartbeatsjp/check-tls-cert
Check-tls-cert is a TLS certificate checker. Contribute to heartbeatsjp/check-tls-cert development by creating an account on GitHub.
TLS証明書の有効性と証明書チェインの検証を行う。
|
non_build
|
heartbeatsjp check tls cert check tls cert is a tls certificate checker check tls cert is a tls certificate checker contribute to heartbeatsjp check tls cert development by creating an account on github tls証明書の有効性と証明書チェインの検証を行う。
| 0
|
164,545
| 25,984,923,986
|
IssuesEvent
|
2022-12-19 22:44:27
|
dotnet/project-system-tools
|
https://api.github.com/repos/dotnet/project-system-tools
|
closed
|
Design process for project-system-tools extension to support VS 15.9 and above
|
design
|
Older VS versions, like 15.9 cannot support Codespaces package dependencies.
Currently, there is a feature/codespaces branch on this repo that supports 16.8 and above, and the main branch supports 15.9 to 16.8.
Find a solution where 15.9 and above can be supported:
- Use only one extension that is able to switch between non Codespaces and Codespace environments (System.Reflection?)
- Maintain two extensions for each use case
- something else?
|
1.0
|
Design process for project-system-tools extension to support VS 15.9 and above - Older VS versions, like 15.9 cannot support Codespaces package dependencies.
Currently, there is a feature/codespaces branch on this repo that supports 16.8 and above, and the main branch supports 15.9 to 16.8.
Find a solution where 15.9 and above can be supported:
- Use only one extension that is able to switch between non Codespaces and Codespace environments (System.Reflection?)
- Maintain two extensions for each use case
- something else?
|
non_build
|
design process for project system tools extension to support vs and above older vs versions like cannot support codespaces package dependencies currently there is a feature codespaces branch on this repo that supports and above and the main branch supports to find a solution where and above can be supported use only one extension that is able to switch between non codespaces and codespace environments system reflection maintain two extensions for each use case something else
| 0
|
4,742
| 3,440,179,087
|
IssuesEvent
|
2015-12-14 13:27:47
|
Itseez/opencv
|
https://api.github.com/repos/Itseez/opencv
|
closed
|
Unable to build with OpenNI+Kinect support
|
affected: master auto-transferred bug category: build/install priority: normal
|
Transferred from http://code.opencv.org/issues/3572
```
|| Arun JVS on 2014-02-25 13:59
|| Priority: Normal
|| Affected: branch 'master' (3.0-dev)
|| Category: build/install
|| Tracker: Bug
|| Difficulty:
|| PR:
|| Platform: x64 / Linux
```
Unable to build with OpenNI+Kinect support
-----------
```
I'm trying to build OpenCV with OpenNI+avin2 Kinect Driver support
(as suggested by http://docs.opencv.org/doc/user_guide/ug_highgui.html):
<pre>
$ cmake\
-D CMAKE_BUILD_TYPE=RELEASE\
-D CMAKE_INSTALL_PREFIX=/home/arun/opencv/opencv-install\
-D BUILD_DOCS=ON\
-D BUILD_EXAMPLES=ON\
-D BUILD_TESTS=ON\
-D BUILD_PERF_TESTS=ON\
-D BUILD_opencv_python=ON\
-D WITH_OPENGL=ON\
-D WITH_OPENNI=ON\
-D OPENNI_LIB_DIR=/home/arun/opencv/openni/lib\
-D OPENNI_INCLUDE_DIR=/home/arun/opencv/openni/include\
-D OPENNI_PRIME_SENSOR_MODULE_BIN_DIR=/home/arun/opencv/openni/bin\
/home/arun/opencv/opencv
</pre>
However cmake is unable to find them:
<pre>
....
....
WARNING, OpenNI library directory (set by OPENNI_LIB_DIR variable) is not found or does not have OpenNI libraries.
WARNING, OpenNI include directory (set by OPENNI_INCLUDE_DIR variable) is not found or does not have OpenNI include files.
WARNING, PrimeSensor Module binaries directory (set by OPENNI_PRIME_SENSOR_MODULE_BIN_DIR variable) is not found or does not have PrimeSensor Module binaries.
-- Looking for libavformat/avformat.h
-- Looking for libavformat/avformat.h - found
....
....
-- Video I/O:
-- DC1394 1.x: NO
-- DC1394 2.x: YES (ver 2.2.0)
-- FFMPEG: YES
-- codec: YES (ver 53.35.0)
-- format: YES (ver 53.21.1)
-- util: YES (ver 51.22.2)
-- swscale: YES (ver 2.1.0)
-- gentoo-style: YES
-- GStreamer: NO
-- OpenNI: NO
-- OpenNI PrimeSensor Modules: NO
....
....
</pre>
I have correctly extracted the contents from OpenNI-Linux-x64-2.2.0.33.tar.zip and SensorKinect093-Bin-Linux-x64-v5.1.2.1.tar.bz2 though:
@$ tree /home/arun/opencv/openni/@
<pre>
.
├── bin
│ └── XnSensorServer
├── include
│ ├── Android-Arm
│ │ └── OniPlatformAndroid-Arm.h
│ ├── Driver
│ │ ├── OniDriverAPI.h
│ │ └── OniDriverTypes.h
│ ├── Linux-Arm
│ │ └── OniPlatformLinux-Arm.h
│ ├── Linux-x86
│ │ └── OniPlatformLinux-x86.h
│ ├── MacOSX
│ │ └── OniPlatformMacOSX.h
│ ├── OniCAPI.h
│ ├── OniCEnums.h
│ ├── OniCProperties.h
│ ├── OniCTypes.h
│ ├── OniEnums.h
│ ├── OniPlatform.h
│ ├── OniProperties.h
│ ├── OniVersion.h
│ ├── OpenNI.h
│ ├── PrimeSense.h
│ ├── PS1080.h
│ ├── PSLink.h
│ └── Win32
│ └── OniPlatformWin32.h
└── lib
├── libOpenNI2.jni.so
├── libOpenNI2.so
├── libXnCore.so
├── libXnDDK.so
├── libXnDeviceFile.so
├── libXnDeviceSensorV2KM.so
├── libXnFormats.so
├── OpenNI2
│ └── Drivers
│ ├── libOniFile.so
│ ├── libPS1080.so
│ ├── libPSLink.so
│ ├── PS1080.ini
│ └── PSLink.ini
├── OpenNI.ini
└── org.openni.jar
11 directories, 34 files
</pre>
Someone also faced this problem:
http://answers.opencv.org/question/17666/opencv-2461-openni-22-missing/
Does OpenCV maintain support for OpenNI at all?
I can't find any mention of 'libOpenNI2.so' anywhere is the course.
```
History
-------
##### Roman Donchenko on 2014-02-25 14:00
```
OpenNI 2 is not supported. Use 1, or help us implement it. :-)
```
##### Arun JVS on 2014-02-25 14:13
```
I would like to look into it. But http://www.openni.org says that the site closes on April 23rd.
Any clues on that?
Maybe it is more worth to use OpenKinect.org's libfreenect (https://github.com/OpenKinect/libfreenect) ?
It definitely seems lighter and neatly written.
```
##### Dinar Ahmatnurov on 2014-03-04 10:47
```
- Assignee set to Roman Donchenko
- Status changed from New to Open
- Category set to build/install
```
|
1.0
|
Unable to build with OpenNI+Kinect support - Transferred from http://code.opencv.org/issues/3572
```
|| Arun JVS on 2014-02-25 13:59
|| Priority: Normal
|| Affected: branch 'master' (3.0-dev)
|| Category: build/install
|| Tracker: Bug
|| Difficulty:
|| PR:
|| Platform: x64 / Linux
```
Unable to build with OpenNI+Kinect support
-----------
```
I'm trying to build OpenCV with OpenNI+avin2 Kinect Driver support
(as suggested by http://docs.opencv.org/doc/user_guide/ug_highgui.html):
<pre>
$ cmake\
-D CMAKE_BUILD_TYPE=RELEASE\
-D CMAKE_INSTALL_PREFIX=/home/arun/opencv/opencv-install\
-D BUILD_DOCS=ON\
-D BUILD_EXAMPLES=ON\
-D BUILD_TESTS=ON\
-D BUILD_PERF_TESTS=ON\
-D BUILD_opencv_python=ON\
-D WITH_OPENGL=ON\
-D WITH_OPENNI=ON\
-D OPENNI_LIB_DIR=/home/arun/opencv/openni/lib\
-D OPENNI_INCLUDE_DIR=/home/arun/opencv/openni/include\
-D OPENNI_PRIME_SENSOR_MODULE_BIN_DIR=/home/arun/opencv/openni/bin\
/home/arun/opencv/opencv
</pre>
However cmake is unable to find them:
<pre>
....
....
WARNING, OpenNI library directory (set by OPENNI_LIB_DIR variable) is not found or does not have OpenNI libraries.
WARNING, OpenNI include directory (set by OPENNI_INCLUDE_DIR variable) is not found or does not have OpenNI include files.
WARNING, PrimeSensor Module binaries directory (set by OPENNI_PRIME_SENSOR_MODULE_BIN_DIR variable) is not found or does not have PrimeSensor Module binaries.
-- Looking for libavformat/avformat.h
-- Looking for libavformat/avformat.h - found
....
....
-- Video I/O:
-- DC1394 1.x: NO
-- DC1394 2.x: YES (ver 2.2.0)
-- FFMPEG: YES
-- codec: YES (ver 53.35.0)
-- format: YES (ver 53.21.1)
-- util: YES (ver 51.22.2)
-- swscale: YES (ver 2.1.0)
-- gentoo-style: YES
-- GStreamer: NO
-- OpenNI: NO
-- OpenNI PrimeSensor Modules: NO
....
....
</pre>
I have correctly extracted the contents from OpenNI-Linux-x64-2.2.0.33.tar.zip and SensorKinect093-Bin-Linux-x64-v5.1.2.1.tar.bz2 though:
@$ tree /home/arun/opencv/openni/@
<pre>
.
├── bin
│ └── XnSensorServer
├── include
│ ├── Android-Arm
│ │ └── OniPlatformAndroid-Arm.h
│ ├── Driver
│ │ ├── OniDriverAPI.h
│ │ └── OniDriverTypes.h
│ ├── Linux-Arm
│ │ └── OniPlatformLinux-Arm.h
│ ├── Linux-x86
│ │ └── OniPlatformLinux-x86.h
│ ├── MacOSX
│ │ └── OniPlatformMacOSX.h
│ ├── OniCAPI.h
│ ├── OniCEnums.h
│ ├── OniCProperties.h
│ ├── OniCTypes.h
│ ├── OniEnums.h
│ ├── OniPlatform.h
│ ├── OniProperties.h
│ ├── OniVersion.h
│ ├── OpenNI.h
│ ├── PrimeSense.h
│ ├── PS1080.h
│ ├── PSLink.h
│ └── Win32
│ └── OniPlatformWin32.h
└── lib
├── libOpenNI2.jni.so
├── libOpenNI2.so
├── libXnCore.so
├── libXnDDK.so
├── libXnDeviceFile.so
├── libXnDeviceSensorV2KM.so
├── libXnFormats.so
├── OpenNI2
│ └── Drivers
│ ├── libOniFile.so
│ ├── libPS1080.so
│ ├── libPSLink.so
│ ├── PS1080.ini
│ └── PSLink.ini
├── OpenNI.ini
└── org.openni.jar
11 directories, 34 files
</pre>
Someone also faced this problem:
http://answers.opencv.org/question/17666/opencv-2461-openni-22-missing/
Does OpenCV maintain support for OpenNI at all?
I can't find any mention of 'libOpenNI2.so' anywhere is the course.
```
History
-------
##### Roman Donchenko on 2014-02-25 14:00
```
OpenNI 2 is not supported. Use 1, or help us implement it. :-)
```
##### Arun JVS on 2014-02-25 14:13
```
I would like to look into it. But http://www.openni.org says that the site closes on April 23rd.
Any clues on that?
Maybe it is more worth to use OpenKinect.org's libfreenect (https://github.com/OpenKinect/libfreenect) ?
It definitely seems lighter and neatly written.
```
##### Dinar Ahmatnurov on 2014-03-04 10:47
```
- Assignee set to Roman Donchenko
- Status changed from New to Open
- Category set to build/install
```
|
build
|
unable to build with openni kinect support transferred from arun jvs on priority normal affected branch master dev category build install tracker bug difficulty pr platform linux unable to build with openni kinect support i m trying to build opencv with openni kinect driver support as suggested by cmake d cmake build type release d cmake install prefix home arun opencv opencv install d build docs on d build examples on d build tests on d build perf tests on d build opencv python on d with opengl on d with openni on d openni lib dir home arun opencv openni lib d openni include dir home arun opencv openni include d openni prime sensor module bin dir home arun opencv openni bin home arun opencv opencv however cmake is unable to find them warning openni library directory set by openni lib dir variable is not found or does not have openni libraries warning openni include directory set by openni include dir variable is not found or does not have openni include files warning primesensor module binaries directory set by openni prime sensor module bin dir variable is not found or does not have primesensor module binaries looking for libavformat avformat h looking for libavformat avformat h found video i o x no x yes ver ffmpeg yes codec yes ver format yes ver util yes ver swscale yes ver gentoo style yes gstreamer no openni no openni primesensor modules no i have correctly extracted the contents from openni linux tar zip and bin linux tar though tree home arun opencv openni ├── bin │ └── xnsensorserver ├── include │ ├── android arm │ │ └── oniplatformandroid arm h │ ├── driver │ │ ├── onidriverapi h │ │ └── onidrivertypes h │ ├── linux arm │ │ └── oniplatformlinux arm h │ ├── linux │ │ └── oniplatformlinux h │ ├── macosx │ │ └── oniplatformmacosx h │ ├── onicapi h │ ├── onicenums h │ ├── onicproperties h │ ├── onictypes h │ ├── onienums h │ ├── oniplatform h │ ├── oniproperties h │ ├── oniversion h │ ├── openni h │ ├── primesense h │ ├── h │ ├── pslink h │ └── │ └── h └── lib ├── jni so ├── so ├── libxncore so ├── libxnddk so ├── libxndevicefile so ├── so ├── libxnformats so ├── │ └── drivers │ ├── libonifile so │ ├── so │ ├── libpslink so │ ├── ini │ └── pslink ini ├── openni ini └── org openni jar directories files someone also faced this problem does opencv maintain support for openni at all i can t find any mention of so anywhere is the course history roman donchenko on openni is not supported use or help us implement it arun jvs on i would like to look into it but says that the site closes on april any clues on that maybe it is more worth to use openkinect org s libfreenect it definitely seems lighter and neatly written dinar ahmatnurov on assignee set to roman donchenko status changed from new to open category set to build install
| 1
|
7,889
| 4,097,763,695
|
IssuesEvent
|
2016-06-03 03:58:36
|
JuliaLang/julia
|
https://api.github.com/repos/JuliaLang/julia
|
closed
|
Compilation failed on ppc64
|
build Power
|
Hi All, I am trying to compile Julia 0.4.5 on Power8, Redhat 7.2/64-bit. My "Make.user" file:
prefix=${SOFT}/julia
[julia.ppc64.log.zip](https://github.com/JuliaLang/julia/files/234398/julia.ppc64.log.zip)
# <-- custom destination folder, SOFT is defined in .bashrc
include $(JULIAHOME)/Make.powerpc
The failure happens while "inference.jl" is compiled (the complete output file is attached):
```
inference.jl
julia: /home/albert/tmp/julia-0.4.5/deps/llvm-3.6.0/lib/CodeGen/MachineLICM.cpp:960: bool {anonymous}::MachineLICM::IsLoopInvariantInst(llvm::MachineInstr&): Assertion `MRI->getVRegDef(Reg) && "Machine instr not mapped for this vreg?!"' failed.
signal (6): Aborted
/bin/sh: line 1: 102713 Aborted (core dumped) /home/albert/tmp/julia-0.4.5/usr/bin/julia -C native --output-ji /home/albert/tmp/julia-0.4.5/usr/lib/julia/inference0.ji -f coreimg.jl
make[1]: *** [/home/albert/tmp/julia-0.4.5/usr/lib/julia/inference0.ji] Error 134
make: *** [julia-inference] Error 2
```
|
1.0
|
Compilation failed on ppc64 - Hi All, I am trying to compile Julia 0.4.5 on Power8, Redhat 7.2/64-bit. My "Make.user" file:
prefix=${SOFT}/julia
[julia.ppc64.log.zip](https://github.com/JuliaLang/julia/files/234398/julia.ppc64.log.zip)
# <-- custom destination folder, SOFT is defined in .bashrc
include $(JULIAHOME)/Make.powerpc
The failure happens while "inference.jl" is compiled (the complete output file is attached):
```
inference.jl
julia: /home/albert/tmp/julia-0.4.5/deps/llvm-3.6.0/lib/CodeGen/MachineLICM.cpp:960: bool {anonymous}::MachineLICM::IsLoopInvariantInst(llvm::MachineInstr&): Assertion `MRI->getVRegDef(Reg) && "Machine instr not mapped for this vreg?!"' failed.
signal (6): Aborted
/bin/sh: line 1: 102713 Aborted (core dumped) /home/albert/tmp/julia-0.4.5/usr/bin/julia -C native --output-ji /home/albert/tmp/julia-0.4.5/usr/lib/julia/inference0.ji -f coreimg.jl
make[1]: *** [/home/albert/tmp/julia-0.4.5/usr/lib/julia/inference0.ji] Error 134
make: *** [julia-inference] Error 2
```
|
build
|
compilation failed on hi all i am trying to compile julia on redhat bit my make user file prefix soft julia custom destination folder soft is defined in bashrc include juliahome make powerpc the failure happens while inference jl is compiled the complete output file is attached inference jl julia home albert tmp julia deps llvm lib codegen machinelicm cpp bool anonymous machinelicm isloopinvariantinst llvm machineinstr assertion mri getvregdef reg machine instr not mapped for this vreg failed signal aborted bin sh line aborted core dumped home albert tmp julia usr bin julia c native output ji home albert tmp julia usr lib julia ji f coreimg jl make error make error
| 1
|
61,002
| 14,939,103,964
|
IssuesEvent
|
2021-01-25 16:32:51
|
EIDSS/EIDSS7
|
https://api.github.com/repos/EIDSS/EIDSS7
|
closed
|
ADM04 - Modify existing Org.
|
Build 98.0 Known issue bug
|
**Summary**
ADM04 - User is expected to update the organization information. I am able to update everything besides postal code. The postal code should be a data entry field but it is actually a drop down option in the system.
**To Reproduce**
Steps to reproduce the behavior:
1. Log in as admanders
2. Go to Organization List
3. Click on the edit button for a organization
4. Update the postal code to "45209" - This is the point of failure, unable to update the postal code which is a required field.
**Expected behavior**
User should be able to update the postal code field
**Screenshots**
**Additional details:**
- Build:
- Script title (enter ad hoc if not script-based):
**Issue severity (Optional)**
Severity (critical, major, minor, low):
**Additional context**
Add any other context about the problem here.
|
1.0
|
ADM04 - Modify existing Org. - **Summary**
ADM04 - User is expected to update the organization information. I am able to update everything besides postal code. The postal code should be a data entry field but it is actually a drop down option in the system.
**To Reproduce**
Steps to reproduce the behavior:
1. Log in as admanders
2. Go to Organization List
3. Click on the edit button for a organization
4. Update the postal code to "45209" - This is the point of failure, unable to update the postal code which is a required field.
**Expected behavior**
User should be able to update the postal code field
**Screenshots**
**Additional details:**
- Build:
- Script title (enter ad hoc if not script-based):
**Issue severity (Optional)**
Severity (critical, major, minor, low):
**Additional context**
Add any other context about the problem here.
|
build
|
modify existing org summary user is expected to update the organization information i am able to update everything besides postal code the postal code should be a data entry field but it is actually a drop down option in the system to reproduce steps to reproduce the behavior log in as admanders go to organization list click on the edit button for a organization update the postal code to this is the point of failure unable to update the postal code which is a required field expected behavior user should be able to update the postal code field screenshots additional details build script title enter ad hoc if not script based issue severity optional severity critical major minor low additional context add any other context about the problem here
| 1
|
23,428
| 7,329,141,756
|
IssuesEvent
|
2018-03-05 02:53:08
|
judah/pier
|
https://api.github.com/repos/judah/pier
|
closed
|
TemplateHaskell can't find extra-source-files
|
Build All The Packages
|
Example:
```
* Command: yesod-bin-1.5.3: building executable yesod
_pier/artifact/B39n5SYis8Ej30xcWm36rpWJXCFGTNEu53-wVDji59M/package/raw/yesod-bin-1.5.3/Devel.hs:130:38: error:
* Exception when trying to run compile-time code:
refreshing.html: openBinaryFile: does not exist (No such file or directory)
Code: embedFile "refreshing.html"
* In the untyped splice: $(embedFile "refreshing.html")
|
130 | let refreshHtml = LB.fromChunks [$(embedFile "refreshing.html")]
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
```
It's probably because the files are actually located under `_pier/archive/...`. Not sure what a good fix is in general. Manually symlinking the extra-source-files to the root might work, but feels like a large hammer, and might overlap in purpose with other code such as that around C input files.
|
1.0
|
TemplateHaskell can't find extra-source-files - Example:
```
* Command: yesod-bin-1.5.3: building executable yesod
_pier/artifact/B39n5SYis8Ej30xcWm36rpWJXCFGTNEu53-wVDji59M/package/raw/yesod-bin-1.5.3/Devel.hs:130:38: error:
* Exception when trying to run compile-time code:
refreshing.html: openBinaryFile: does not exist (No such file or directory)
Code: embedFile "refreshing.html"
* In the untyped splice: $(embedFile "refreshing.html")
|
130 | let refreshHtml = LB.fromChunks [$(embedFile "refreshing.html")]
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
```
It's probably because the files are actually located under `_pier/archive/...`. Not sure what a good fix is in general. Manually symlinking the extra-source-files to the root might work, but feels like a large hammer, and might overlap in purpose with other code such as that around C input files.
|
build
|
templatehaskell can t find extra source files example command yesod bin building executable yesod pier artifact package raw yesod bin devel hs error exception when trying to run compile time code refreshing html openbinaryfile does not exist no such file or directory code embedfile refreshing html in the untyped splice embedfile refreshing html let refreshhtml lb fromchunks it s probably because the files are actually located under pier archive not sure what a good fix is in general manually symlinking the extra source files to the root might work but feels like a large hammer and might overlap in purpose with other code such as that around c input files
| 1
|
72,700
| 19,425,056,859
|
IssuesEvent
|
2021-12-21 03:35:23
|
xenial-io/Xenial.Framework
|
https://api.github.com/repos/xenial-io/Xenial.Framework
|
opened
|
SourceGenerators - Partial methods for ColumnBuilderAttributes
|
enhancement FeatureRequest SourceGenerators Core ColumnBuilder
|
similar to #63 we should expand that concept to `ListViewColumnsBuilderAttribute` and `LookupListViewColumnsBuilderAttribute` correspondingly to their naming convention
|
1.0
|
SourceGenerators - Partial methods for ColumnBuilderAttributes - similar to #63 we should expand that concept to `ListViewColumnsBuilderAttribute` and `LookupListViewColumnsBuilderAttribute` correspondingly to their naming convention
|
build
|
sourcegenerators partial methods for columnbuilderattributes similar to we should expand that concept to listviewcolumnsbuilderattribute and lookuplistviewcolumnsbuilderattribute correspondingly to their naming convention
| 1
|
340,937
| 10,280,417,868
|
IssuesEvent
|
2019-08-26 05:13:39
|
ballerina-platform/ballerina-lang
|
https://api.github.com/repos/ballerina-platform/ballerina-lang
|
opened
|
Implement the `__detach()` method for std lib listeners
|
Area/StandardLibs Priority/High Type/Task
|
**Description:**
$title, the std lib listeners (other than HTTP) currently have empty implementations for the same.
**Related Issues (optional):**
https://github.com/ballerina-platform/ballerina-lang/issues/17680
|
1.0
|
Implement the `__detach()` method for std lib listeners - **Description:**
$title, the std lib listeners (other than HTTP) currently have empty implementations for the same.
**Related Issues (optional):**
https://github.com/ballerina-platform/ballerina-lang/issues/17680
|
non_build
|
implement the detach method for std lib listeners description title the std lib listeners other than http currently have empty implementations for the same related issues optional
| 0
|
48,298
| 12,192,341,815
|
IssuesEvent
|
2020-04-29 12:47:45
|
alan-turing-institute/ptype-dmkd
|
https://api.github.com/repos/alan-turing-institute/ptype-dmkd
|
closed
|
Publish package to PyPI
|
type:feature what:build
|
Automate publishing to PyPI using `develop` and `master` pattern.
- [x] test upload to TestPyPI
- [x] `publish.sh` script that takes PyPI password as argument
- [x] add`pypi-password` secret to repo
- [x] GitHub job to run `publish.sh` using `pypi-password`
- [x] new `release` branch; Publish job should only run on `release`
- [x] new `develop` branch as default
- <s>add `upload-artifact` step to store `dist` folder as artifact</s>
- <s>add `download-artifact` step to publish job</s>
- <s>missing project description</s>
- `HTTPError: 400 Client Error: File already exists`
- [x] bump version number in `setup.py` (probably using [bump2version](https://pypi.org/project/bump2version/))
- `HTTPError: 400 Client Error: Only one sdist may be uploaded per release`
- [x] clean `dist` directory otherwise will end up with multiple source distributions
- [x] `git tag` with version number
- [x] `git push` to push changes to version number in `setup.py` and `.bumpversion.cfg`
- <s>only publish if [latest commit is tagged](https://packaging.python.org/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/)</s>
- switch from TestPyPI to PyPI
- [x] PyPI secret in repo
- [x] parameterise `publish.sh` on `pypi` or `testpypi`
- [x] `build-test-publish.yml` to use `pypi` by default
- [x] top-level Bash script to emulate GitHub workflow (with appropriate password)
- [x] extract common Python `virtualenv` gubbins
|
1.0
|
Publish package to PyPI - Automate publishing to PyPI using `develop` and `master` pattern.
- [x] test upload to TestPyPI
- [x] `publish.sh` script that takes PyPI password as argument
- [x] add`pypi-password` secret to repo
- [x] GitHub job to run `publish.sh` using `pypi-password`
- [x] new `release` branch; Publish job should only run on `release`
- [x] new `develop` branch as default
- <s>add `upload-artifact` step to store `dist` folder as artifact</s>
- <s>add `download-artifact` step to publish job</s>
- <s>missing project description</s>
- `HTTPError: 400 Client Error: File already exists`
- [x] bump version number in `setup.py` (probably using [bump2version](https://pypi.org/project/bump2version/))
- `HTTPError: 400 Client Error: Only one sdist may be uploaded per release`
- [x] clean `dist` directory otherwise will end up with multiple source distributions
- [x] `git tag` with version number
- [x] `git push` to push changes to version number in `setup.py` and `.bumpversion.cfg`
- <s>only publish if [latest commit is tagged](https://packaging.python.org/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/)</s>
- switch from TestPyPI to PyPI
- [x] PyPI secret in repo
- [x] parameterise `publish.sh` on `pypi` or `testpypi`
- [x] `build-test-publish.yml` to use `pypi` by default
- [x] top-level Bash script to emulate GitHub workflow (with appropriate password)
- [x] extract common Python `virtualenv` gubbins
|
build
|
publish package to pypi automate publishing to pypi using develop and master pattern test upload to testpypi publish sh script that takes pypi password as argument add pypi password secret to repo github job to run publish sh using pypi password new release branch publish job should only run on release new develop branch as default add upload artifact step to store dist folder as artifact add download artifact step to publish job missing project description httperror client error file already exists bump version number in setup py probably using httperror client error only one sdist may be uploaded per release clean dist directory otherwise will end up with multiple source distributions git tag with version number git push to push changes to version number in setup py and bumpversion cfg only publish if switch from testpypi to pypi pypi secret in repo parameterise publish sh on pypi or testpypi build test publish yml to use pypi by default top level bash script to emulate github workflow with appropriate password extract common python virtualenv gubbins
| 1
|
37,721
| 10,062,507,595
|
IssuesEvent
|
2019-07-23 01:28:41
|
eventespresso/event-espresso-core
|
https://api.github.com/repos/eventespresso/event-espresso-core
|
closed
|
Test if React.createElement is being used instead of wp.element.createElement in our built files.
|
category:assets requires:WP 5.0 🧩 type:bug 🐞 type:build-process 🔨
|
<!--
BEFORE POSTING YOUR ISSUE:
- These comments won't show up when you submit the issue.
- Please ensure that what you are reporting is specific to this project.
- Try to add as much detail as possible. Be specific!
- Make sure you read the README.md for the project regarding posting issues.
- Search this repository for issues and pull requests and whether it has been fixed or reported already.
- Ensure you are using the latest code before reporting bugs (unless you are reporting an issue disovered in a branch).
- Disable all plugins and switch to a default theme to ensure its not a plugin/theme conflict issue.
- To report a security issue, please visit this page: https://eventespresso.com/report-a-security-vulnerability/
-->
**Describe the bug**
<!-- A clear and concise description of what the bug is. -->
I don't know for sure if this is a bug or not, but this is something I want to look into to verify. I just realized today that I have the webpack config setup to use the `ProvidePlugin` for exposing the react import automatically in built files. Effectively this removes the need to import react wherever we're using jsx. However, I'm concerned that this means the built files for things used in the wp5.0+ environment are using `React.createElement` instead of `wp.element.createElement` (which is currently a thin wrapper around `React.createElement`). Some _potential_ side effects of this would be:
- unnecessary increase in bundle size.
- increased dependence on react when WP intentionally exposed this wrapper so react could be swapped out for something else down the road.
Currently, a downside to fixing this (if I found it was doing what I thought it might) is that the we'd only be able to use our built files in WP 5.0+ (because of the `wp.element` dependency). I don't think it'd be worth the extensive work required to make things back-compat with earlier WP versions (meaning we'd have to manually import the `@wordpress/element` package and build two versions of built files for use in different environments).
With the WP version requirement in mind, I'm just filing this issue and putting it in the
icebox until we bump our minimum WP version requirement.
**To Verify**
* Verification involves looking at built files for any of our components that use jsx and make sure the components are using `wp.element.createElement` rather than `react.createElement`.
|
1.0
|
Test if React.createElement is being used instead of wp.element.createElement in our built files. - <!--
BEFORE POSTING YOUR ISSUE:
- These comments won't show up when you submit the issue.
- Please ensure that what you are reporting is specific to this project.
- Try to add as much detail as possible. Be specific!
- Make sure you read the README.md for the project regarding posting issues.
- Search this repository for issues and pull requests and whether it has been fixed or reported already.
- Ensure you are using the latest code before reporting bugs (unless you are reporting an issue disovered in a branch).
- Disable all plugins and switch to a default theme to ensure its not a plugin/theme conflict issue.
- To report a security issue, please visit this page: https://eventespresso.com/report-a-security-vulnerability/
-->
**Describe the bug**
<!-- A clear and concise description of what the bug is. -->
I don't know for sure if this is a bug or not, but this is something I want to look into to verify. I just realized today that I have the webpack config setup to use the `ProvidePlugin` for exposing the react import automatically in built files. Effectively this removes the need to import react wherever we're using jsx. However, I'm concerned that this means the built files for things used in the wp5.0+ environment are using `React.createElement` instead of `wp.element.createElement` (which is currently a thin wrapper around `React.createElement`). Some _potential_ side effects of this would be:
- unnecessary increase in bundle size.
- increased dependence on react when WP intentionally exposed this wrapper so react could be swapped out for something else down the road.
Currently, a downside to fixing this (if I found it was doing what I thought it might) is that the we'd only be able to use our built files in WP 5.0+ (because of the `wp.element` dependency). I don't think it'd be worth the extensive work required to make things back-compat with earlier WP versions (meaning we'd have to manually import the `@wordpress/element` package and build two versions of built files for use in different environments).
With the WP version requirement in mind, I'm just filing this issue and putting it in the
icebox until we bump our minimum WP version requirement.
**To Verify**
* Verification involves looking at built files for any of our components that use jsx and make sure the components are using `wp.element.createElement` rather than `react.createElement`.
|
build
|
test if react createelement is being used instead of wp element createelement in our built files before posting your issue these comments won t show up when you submit the issue please ensure that what you are reporting is specific to this project try to add as much detail as possible be specific make sure you read the readme md for the project regarding posting issues search this repository for issues and pull requests and whether it has been fixed or reported already ensure you are using the latest code before reporting bugs unless you are reporting an issue disovered in a branch disable all plugins and switch to a default theme to ensure its not a plugin theme conflict issue to report a security issue please visit this page describe the bug i don t know for sure if this is a bug or not but this is something i want to look into to verify i just realized today that i have the webpack config setup to use the provideplugin for exposing the react import automatically in built files effectively this removes the need to import react wherever we re using jsx however i m concerned that this means the built files for things used in the environment are using react createelement instead of wp element createelement which is currently a thin wrapper around react createelement some potential side effects of this would be unnecessary increase in bundle size increased dependence on react when wp intentionally exposed this wrapper so react could be swapped out for something else down the road currently a downside to fixing this if i found it was doing what i thought it might is that the we d only be able to use our built files in wp because of the wp element dependency i don t think it d be worth the extensive work required to make things back compat with earlier wp versions meaning we d have to manually import the wordpress element package and build two versions of built files for use in different environments with the wp version requirement in mind i m just filing this issue and putting it in the icebox until we bump our minimum wp version requirement to verify verification involves looking at built files for any of our components that use jsx and make sure the components are using wp element createelement rather than react createelement
| 1
|
27,550
| 7,979,256,508
|
IssuesEvent
|
2018-07-17 21:03:42
|
RA20-TickIt/API
|
https://api.github.com/repos/RA20-TickIt/API
|
closed
|
feat/staff/scan-ticket
|
scope: build state: merge type: feature
|
1. Vendor App scans ticket
2. Sends info to API
3. Check if ticket has been used
4. If yes, change ticket details on DB and return a success message to vendor
5. If no, return error messages
|
1.0
|
feat/staff/scan-ticket - 1. Vendor App scans ticket
2. Sends info to API
3. Check if ticket has been used
4. If yes, change ticket details on DB and return a success message to vendor
5. If no, return error messages
|
build
|
feat staff scan ticket vendor app scans ticket sends info to api check if ticket has been used if yes change ticket details on db and return a success message to vendor if no return error messages
| 1
|
50,774
| 12,553,539,143
|
IssuesEvent
|
2020-06-06 22:25:53
|
final-hill/decorator-contracts
|
https://api.github.com/repos/final-hill/decorator-contracts
|
closed
|
Release not working
|
bug feature/build
|
https://github.com/final-hill/decorator-contracts/actions/runs/125767144
Due to a limitation in GitHub actions, packages can not be referenced between workflows
|
1.0
|
Release not working - https://github.com/final-hill/decorator-contracts/actions/runs/125767144
Due to a limitation in GitHub actions, packages can not be referenced between workflows
|
build
|
release not working due to a limitation in github actions packages can not be referenced between workflows
| 1
|
338,612
| 24,592,682,282
|
IssuesEvent
|
2022-10-14 04:49:55
|
iacopy/cleanpython
|
https://api.github.com/repos/iacopy/cleanpython
|
opened
|
Add documentation
|
documentation
|
Best practices: [Structuring Your Project]( https://docs.python-guide.org/writing/structure/)
## Testing:
- https://plainenglish.io/blog/unit-testing-in-python-structure-57acd51da923
- https://docs.python-guide.org/writing/tests/
- https://realpython.com/python-testing/
### Patching, mocking
- https://levelup.gitconnected.com/unit-testing-in-python-mocking-patching-and-dependency-injection-301280db2fed
|
1.0
|
Add documentation - Best practices: [Structuring Your Project]( https://docs.python-guide.org/writing/structure/)
## Testing:
- https://plainenglish.io/blog/unit-testing-in-python-structure-57acd51da923
- https://docs.python-guide.org/writing/tests/
- https://realpython.com/python-testing/
### Patching, mocking
- https://levelup.gitconnected.com/unit-testing-in-python-mocking-patching-and-dependency-injection-301280db2fed
|
non_build
|
add documentation best practices testing patching mocking
| 0
|
120,853
| 25,884,818,045
|
IssuesEvent
|
2022-12-14 13:51:58
|
Clueless-Community/seamless-ui
|
https://api.github.com/repos/Clueless-Community/seamless-ui
|
closed
|
Improve footer-blue-10
|
codepeak 22 issue:3
|
Need to improve this component: footer-blue-10
## Improvements required :
Make it responsive
## Any reference image?
|
1.0
|
Improve footer-blue-10 - Need to improve this component: footer-blue-10
## Improvements required :
Make it responsive
## Any reference image?
|
non_build
|
improve footer blue need to improve this component footer blue improvements required make it responsive any reference image
| 0
|
687,930
| 23,543,190,728
|
IssuesEvent
|
2022-08-20 18:22:04
|
KendallDoesCoding/mogul-christmas
|
https://api.github.com/repos/KendallDoesCoding/mogul-christmas
|
closed
|
Update ludsocials directory
|
bug good first issue css on-hold 🟩 priority: low EddieHub:good-first-issue 🏁 status: ready for dev 🔢 points: 5
|
Currently, the div class is "songs" instead of "socials" in the HTML for the Lud-Socials directory, I updated the class and added the same css to it, but there's still a bug... The branch which I am working on this is linked in the "Development" if anyone can help debug the issue.
cc: @TechStudent11
|
1.0
|
Update ludsocials directory - Currently, the div class is "songs" instead of "socials" in the HTML for the Lud-Socials directory, I updated the class and added the same css to it, but there's still a bug... The branch which I am working on this is linked in the "Development" if anyone can help debug the issue.
cc: @TechStudent11
|
non_build
|
update ludsocials directory currently the div class is songs instead of socials in the html for the lud socials directory i updated the class and added the same css to it but there s still a bug the branch which i am working on this is linked in the development if anyone can help debug the issue cc
| 0
|
18,256
| 10,053,578,058
|
IssuesEvent
|
2019-07-21 17:57:14
|
raoulvdberge/refinedstorage
|
https://api.github.com/repos/raoulvdberge/refinedstorage
|
closed
|
Server hard lock on Refined storage- net.minecraft.util.math.Vec3i.equals
|
Performance
|
#### Issue description:
My FTB Sky Adventures server locked hard, warmroast and sampler stall reports show refined storage.
#### Version (make sure you are on the latest version before reporting):
- Minecraft: 1.12.2
- Forge: 2770
- Refined Storage: refinedstorage-1.6.5.jar
Does this issue occur on a server? YES
#### If a (crash)log is relevant for this issue, link it here:
Warmroast image
Stall report from sampler-
https://gist.github.com/ProsperCraft/9ab04dd6c73fd45f45d1b1733d8b9ae5
Latest logs-
https://gist.github.com/ProsperCraft/e59055322620d89b175890bb005a702b
Debug log, and more stall logs-
[refinedstorage.zip](https://github.com/raoulvdberge/refinedstorage/files/2535193/refinedstorage.zip)
|
True
|
Server hard lock on Refined storage- net.minecraft.util.math.Vec3i.equals - #### Issue description:
My FTB Sky Adventures server locked hard, warmroast and sampler stall reports show refined storage.
#### Version (make sure you are on the latest version before reporting):
- Minecraft: 1.12.2
- Forge: 2770
- Refined Storage: refinedstorage-1.6.5.jar
Does this issue occur on a server? YES
#### If a (crash)log is relevant for this issue, link it here:
Warmroast image
Stall report from sampler-
https://gist.github.com/ProsperCraft/9ab04dd6c73fd45f45d1b1733d8b9ae5
Latest logs-
https://gist.github.com/ProsperCraft/e59055322620d89b175890bb005a702b
Debug log, and more stall logs-
[refinedstorage.zip](https://github.com/raoulvdberge/refinedstorage/files/2535193/refinedstorage.zip)
|
non_build
|
server hard lock on refined storage net minecraft util math equals issue description my ftb sky adventures server locked hard warmroast and sampler stall reports show refined storage version make sure you are on the latest version before reporting minecraft forge refined storage refinedstorage jar does this issue occur on a server yes if a crash log is relevant for this issue link it here warmroast image stall report from sampler latest logs debug log and more stall logs
| 0
|
45,245
| 11,615,317,389
|
IssuesEvent
|
2020-02-26 14:02:37
|
tensorflow/tensorflow
|
https://api.github.com/repos/tensorflow/tensorflow
|
opened
|
I have to install TF 1.8!
|
type:build/install
|
<em>Please make sure that this is a build/installation issue. As per our [GitHub Policy](https://github.com/tensorflow/tensorflow/blob/master/ISSUES.md), we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template</em>
**System information**
- OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows (10 or 8.1)
- Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
- TensorFlow installed from (source or binary):
- TensorFlow version:1.8
- Python version:3.6
- Installed using virtualenv? pip? conda?:both
- Bazel version (if compiling from source):
- GCC/Compiler version (if compiling from source):
- CUDA/cuDNN version:9.1
- GPU model and memory:NVIDIA GeForce GTX 760
**Describe the problem**
Hello, the computing capabilities of my GPU is 3.0 and TF doesn't work in this case. I've read that it's possible to run the 1.8 version here https://medium.com/@naarkie/using-tensorflow-gpu-on-a-compute-3-0-graphics-card-in-windows-4184f4228fe9
But impossible to find the good package.
I need it to use the Visions of Chaos software (fractal art).
May somebody help me?
Thanks for all.
Best regards,
François
**Provide the exact sequence of commands / steps that you executed before running into the problem**
**Any other info / logs**
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.
|
1.0
|
I have to install TF 1.8! - <em>Please make sure that this is a build/installation issue. As per our [GitHub Policy](https://github.com/tensorflow/tensorflow/blob/master/ISSUES.md), we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template</em>
**System information**
- OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows (10 or 8.1)
- Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
- TensorFlow installed from (source or binary):
- TensorFlow version:1.8
- Python version:3.6
- Installed using virtualenv? pip? conda?:both
- Bazel version (if compiling from source):
- GCC/Compiler version (if compiling from source):
- CUDA/cuDNN version:9.1
- GPU model and memory:NVIDIA GeForce GTX 760
**Describe the problem**
Hello, the computing capabilities of my GPU is 3.0 and TF doesn't work in this case. I've read that it's possible to run the 1.8 version here https://medium.com/@naarkie/using-tensorflow-gpu-on-a-compute-3-0-graphics-card-in-windows-4184f4228fe9
But impossible to find the good package.
I need it to use the Visions of Chaos software (fractal art).
May somebody help me?
Thanks for all.
Best regards,
François
**Provide the exact sequence of commands / steps that you executed before running into the problem**
**Any other info / logs**
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.
|
build
|
i have to install tf please make sure that this is a build installation issue as per our we only address code doc bugs performance issues feature requests and build installation issues on github tag build template system information os platform and distribution e g linux ubuntu windows or mobile device e g iphone pixel samsung galaxy if the issue happens on mobile device tensorflow installed from source or binary tensorflow version python version installed using virtualenv pip conda both bazel version if compiling from source gcc compiler version if compiling from source cuda cudnn version gpu model and memory nvidia geforce gtx describe the problem hello the computing capabilities of my gpu is and tf doesn t work in this case i ve read that it s possible to run the version here but impossible to find the good package i need it to use the visions of chaos software fractal art may somebody help me thanks for all best regards françois provide the exact sequence of commands steps that you executed before running into the problem any other info logs include any logs or source code that would be helpful to diagnose the problem if including tracebacks please include the full traceback large logs and files should be attached
| 1
|
23,329
| 7,314,075,251
|
IssuesEvent
|
2018-03-01 05:00:11
|
Microsoft/ChakraCore
|
https://api.github.com/repos/Microsoft/ChakraCore
|
closed
|
[Legacy config] cl : Command line warning D9002: ignoring unknown option '-Zc:implicitNoexcept-'
|
Build Bug Codebase Quality
|
Seems this option was added after Dev12 (compiler toolchain used by the legacy configuration).
`cl : Command line warning D9002: ignoring unknown option '-Zc:implicitNoexcept-'`
See: https://ci2.dot.net/job/Microsoft_ChakraCore/job/release_1.6/job/daily_dev12_x86_debug/36
|
1.0
|
[Legacy config] cl : Command line warning D9002: ignoring unknown option '-Zc:implicitNoexcept-' - Seems this option was added after Dev12 (compiler toolchain used by the legacy configuration).
`cl : Command line warning D9002: ignoring unknown option '-Zc:implicitNoexcept-'`
See: https://ci2.dot.net/job/Microsoft_ChakraCore/job/release_1.6/job/daily_dev12_x86_debug/36
|
build
|
cl command line warning ignoring unknown option zc implicitnoexcept seems this option was added after compiler toolchain used by the legacy configuration cl command line warning ignoring unknown option zc implicitnoexcept see
| 1
|
137,396
| 11,136,151,193
|
IssuesEvent
|
2019-12-20 15:57:05
|
brave/browser-android-tabs
|
https://api.github.com/repos/brave/browser-android-tabs
|
closed
|
Manual test run on Android x86 for 1.6.1
|
QA/Yes release-notes/exclude tests x86
|
## Per release specialty tests
- [x] Clear data button needs to have primary button colour. ([#2086](https://github.com/brave/browser-android-tabs/issues/2086))
- [x] Upgrade to Chromium 79.0.3945.79. ([#2362](https://github.com/brave/browser-android-tabs/issues/2362))
## Installer
- [x] Check that installer is close to the size of the last release
- [x] Check the Brave version in About and make sure it is EXACTLY as expected
## Visual look
- [x] Make sure thereafter every merge
- [x] No Chrome/Chromium words appear on normal or private tabs
- [x] No Chrome/Chromium icons are shown in normal or private tabs
## Data
Pre-Requisite: Put previous build shortcut on the home screen. Also, have several sites 'Added to home screen' (from 3 dots menu) and then upgrade to new build
- [x] Verify that data from the previous build appears in the updated build as expected (bookmarks, etc)
- [x] Verify that the cookies from the previous build are preserved after upgrade
- [x] Verify shortcut is still available on the home screen after upgrade
- [x] Verify sites added to home screen are still visible and able to be used after upgrade
- [x] Verify sync chain created in the previous version is still retained on upgrade
- [x] Verify settings changes done in the previous version are still retained on upgrade
## Bookmarks
- [x] Verify that creating a bookmark works
- [x] Verify that clicking a bookmark loads the bookmark
- [x] Verify that deleting a bookmark works
- [x] Verify that creating a bookmark folder works
## Custom tabs
- [x] Make sure Brave handles links from Gmail, Slack
- [x] Make sure Brave works as custom tabs provide with Chrome browser
- [x] Ensure custom tabs work even with sync enabled/disabled
## Context menus
- [x] Make sure context menu items in the URL bar work
- [x] Make sure context menu items on content work with no selected text
- [x] Make sure context menu items on content work with selected text
- [x] Make sure context menu items on content work inside an editable control (input, textarea, or contenteditable)
## Developer Tools
- [x] Verify you can inspect sublinks via dev tools
## Find in page
- [x] Ensure search box is shown when selected via the hamburger menu
- [x] Verify that you can successfully find a word on the page
- [x] Verify that the forward and backward navigation icons under find are working
- [x] Verify failed to find shows 0 results
## Site hacks
- [x] Verify https://www.twitch.tv/adobe sub-page loads a video and you can play it
## Settings and Bottom bar
- [x] Verify changing default settings are retained and don't cause the browser to crash
- [x] Verify bottom bar buttons (Home/Bookmark/Search/Tabs) work as expected
## Downloads
- [x] Verify downloading a file works and that all actions on the download item work.
- [x] Verify that PDF is downloaded over HTTPS at https://basicattentiontoken.org/BasicAttentionTokenWhitePaper-4.pdf
- [x] Verify that PDF is downloaded over HTTP at http://www.pdf995.com/samples/pdf.pdf
## Fullscreen
- [x] Verify that entering HTML5 fullscreen works and pressing restore to go back exits full screen. (youtube.com)
## Autofill Tests
- [x] Verify that autofill works on https://srirambv.github.io/formfiller.html
## Zoom
- [x] Verify zoom in / out gestures work
- [x] Verify that navigating to a different origin resets the zoom
## Bravery settings
- [x] Check that HTTPS Everywhere works by loading http://https-everywhere.badssl.com/
- [x] Turning HTTPS Everywhere off and shields off both disable the redirect to https://https-everywhere.badssl.com/
- [x] Check that toggling to blocking and allow ads works as expected
- [x] Verify that clicking through a cert error in https://badssl.com/ works
- [x] Visit https://brianbondy.com/ and then turn on script blocking, nothing should load. Allow it from the script blocking UI in the URL bar and it should work.
- [x] Verify that default Bravery settings take effect on pages with no site settings
- [x] Verify that 3rd party storage results are blank at https://jsfiddle.net/7ke9r14a/7/ when 3rd party cookies are blocked
### Fingerprint Tests
- [x] Visit https://browserleaks.com/webrtc, ensure 2 blocked items are listed in shields
- [x] Verify that https://diafygi.github.io/webrtc-ips/ doesn't leak IP address when `Block all fingerprinting protection` is on
## Content Tests
- [x] Go to https://brianbondy.com/ and click on the twitter icon on the top right. Verify that context menus work in the new twitter tab
- [x] Go to https://trac.torproject.org/projects/tor/login and make sure that the password can be saved. Make sure the saved password is auto-populated when you visit the site again
- [x] Open a GitHub issue and type some misspellings, make sure they aren't autocorrected
- [x] Open an email on http://mail.google.com/ or inbox.google.com and click on a link. Make sure it works
- [x] Verify that https://mixed-script.badssl.com/ shows up as grey not red (no mixed content scripts are run)
## Sync
- [x] Verify you are able to join sync chain by scanning the QR code
- [x] Verify you are able to join sync chain using code words
- [x] Verify you are able to create a sync chain on the device and add other devices to the chain via QR code/Code words
- [x] Verify that bookmarks from other devices on the chain show up on the mobile device after sync completes
- [x] Verify newly created bookmarks gets sync'd to all devices on the sync chain
- [x] Verify existing bookmarks before joining sync chain also gets sync'd to all devices on the sync chain
- [x] Verify sync works on an upgrade profile and new bookmarks added post-upgrade sync's across devices on the chain
- [x] Verify adding a bookmark on custom tab gets synced across all devices in the chain
- [x] Verify you are able to create a standalone sync chain with one device
## Top sites view
- [x] Long-press on top sites to get to deletion mode, and delete a top site (note this will stop that site from showing up again on top sites, so you may not want to do this a site you want to keep there)
## Background
- [x] Start loading a page, background the app, wait > 5 sec, then bring to front, ensure splash screen is not shown
## Session storage
- [x] Verify that tabs restore when closed, including active tab
## Yet to be implemented
- Check that ad replacement works on http://slashdot.org
- Verify that Safe Browsing works (https://www.raisegame.com/)
- Turning Safe Browsing off and shields off both disable safe browsing for https://www.raisegame.com/
- Verify that turning on fingerprinting protection in `Privacy` shows 3 fingerprints blocked at https://jsfiddle.net/bkf50r8v/13/. Verify that turning it off in the Bravery menu shows 0 fingerprints blocked
- Verify that audio fingerprint is blocked at https://audiofingerprint.openwpm.com/ when fingerprinting protection is on
|
1.0
|
Manual test run on Android x86 for 1.6.1 - ## Per release specialty tests
- [x] Clear data button needs to have primary button colour. ([#2086](https://github.com/brave/browser-android-tabs/issues/2086))
- [x] Upgrade to Chromium 79.0.3945.79. ([#2362](https://github.com/brave/browser-android-tabs/issues/2362))
## Installer
- [x] Check that installer is close to the size of the last release
- [x] Check the Brave version in About and make sure it is EXACTLY as expected
## Visual look
- [x] Make sure thereafter every merge
- [x] No Chrome/Chromium words appear on normal or private tabs
- [x] No Chrome/Chromium icons are shown in normal or private tabs
## Data
Pre-Requisite: Put previous build shortcut on the home screen. Also, have several sites 'Added to home screen' (from 3 dots menu) and then upgrade to new build
- [x] Verify that data from the previous build appears in the updated build as expected (bookmarks, etc)
- [x] Verify that the cookies from the previous build are preserved after upgrade
- [x] Verify shortcut is still available on the home screen after upgrade
- [x] Verify sites added to home screen are still visible and able to be used after upgrade
- [x] Verify sync chain created in the previous version is still retained on upgrade
- [x] Verify settings changes done in the previous version are still retained on upgrade
## Bookmarks
- [x] Verify that creating a bookmark works
- [x] Verify that clicking a bookmark loads the bookmark
- [x] Verify that deleting a bookmark works
- [x] Verify that creating a bookmark folder works
## Custom tabs
- [x] Make sure Brave handles links from Gmail, Slack
- [x] Make sure Brave works as custom tabs provide with Chrome browser
- [x] Ensure custom tabs work even with sync enabled/disabled
## Context menus
- [x] Make sure context menu items in the URL bar work
- [x] Make sure context menu items on content work with no selected text
- [x] Make sure context menu items on content work with selected text
- [x] Make sure context menu items on content work inside an editable control (input, textarea, or contenteditable)
## Developer Tools
- [x] Verify you can inspect sublinks via dev tools
## Find in page
- [x] Ensure search box is shown when selected via the hamburger menu
- [x] Verify that you can successfully find a word on the page
- [x] Verify that the forward and backward navigation icons under find are working
- [x] Verify failed to find shows 0 results
## Site hacks
- [x] Verify https://www.twitch.tv/adobe sub-page loads a video and you can play it
## Settings and Bottom bar
- [x] Verify changing default settings are retained and don't cause the browser to crash
- [x] Verify bottom bar buttons (Home/Bookmark/Search/Tabs) work as expected
## Downloads
- [x] Verify downloading a file works and that all actions on the download item work.
- [x] Verify that PDF is downloaded over HTTPS at https://basicattentiontoken.org/BasicAttentionTokenWhitePaper-4.pdf
- [x] Verify that PDF is downloaded over HTTP at http://www.pdf995.com/samples/pdf.pdf
## Fullscreen
- [x] Verify that entering HTML5 fullscreen works and pressing restore to go back exits full screen. (youtube.com)
## Autofill Tests
- [x] Verify that autofill works on https://srirambv.github.io/formfiller.html
## Zoom
- [x] Verify zoom in / out gestures work
- [x] Verify that navigating to a different origin resets the zoom
## Bravery settings
- [x] Check that HTTPS Everywhere works by loading http://https-everywhere.badssl.com/
- [x] Turning HTTPS Everywhere off and shields off both disable the redirect to https://https-everywhere.badssl.com/
- [x] Check that toggling to blocking and allow ads works as expected
- [x] Verify that clicking through a cert error in https://badssl.com/ works
- [x] Visit https://brianbondy.com/ and then turn on script blocking, nothing should load. Allow it from the script blocking UI in the URL bar and it should work.
- [x] Verify that default Bravery settings take effect on pages with no site settings
- [x] Verify that 3rd party storage results are blank at https://jsfiddle.net/7ke9r14a/7/ when 3rd party cookies are blocked
### Fingerprint Tests
- [x] Visit https://browserleaks.com/webrtc, ensure 2 blocked items are listed in shields
- [x] Verify that https://diafygi.github.io/webrtc-ips/ doesn't leak IP address when `Block all fingerprinting protection` is on
## Content Tests
- [x] Go to https://brianbondy.com/ and click on the twitter icon on the top right. Verify that context menus work in the new twitter tab
- [x] Go to https://trac.torproject.org/projects/tor/login and make sure that the password can be saved. Make sure the saved password is auto-populated when you visit the site again
- [x] Open a GitHub issue and type some misspellings, make sure they aren't autocorrected
- [x] Open an email on http://mail.google.com/ or inbox.google.com and click on a link. Make sure it works
- [x] Verify that https://mixed-script.badssl.com/ shows up as grey not red (no mixed content scripts are run)
## Sync
- [x] Verify you are able to join sync chain by scanning the QR code
- [x] Verify you are able to join sync chain using code words
- [x] Verify you are able to create a sync chain on the device and add other devices to the chain via QR code/Code words
- [x] Verify that bookmarks from other devices on the chain show up on the mobile device after sync completes
- [x] Verify newly created bookmarks gets sync'd to all devices on the sync chain
- [x] Verify existing bookmarks before joining sync chain also gets sync'd to all devices on the sync chain
- [x] Verify sync works on an upgrade profile and new bookmarks added post-upgrade sync's across devices on the chain
- [x] Verify adding a bookmark on custom tab gets synced across all devices in the chain
- [x] Verify you are able to create a standalone sync chain with one device
## Top sites view
- [x] Long-press on top sites to get to deletion mode, and delete a top site (note this will stop that site from showing up again on top sites, so you may not want to do this a site you want to keep there)
## Background
- [x] Start loading a page, background the app, wait > 5 sec, then bring to front, ensure splash screen is not shown
## Session storage
- [x] Verify that tabs restore when closed, including active tab
## Yet to be implemented
- Check that ad replacement works on http://slashdot.org
- Verify that Safe Browsing works (https://www.raisegame.com/)
- Turning Safe Browsing off and shields off both disable safe browsing for https://www.raisegame.com/
- Verify that turning on fingerprinting protection in `Privacy` shows 3 fingerprints blocked at https://jsfiddle.net/bkf50r8v/13/. Verify that turning it off in the Bravery menu shows 0 fingerprints blocked
- Verify that audio fingerprint is blocked at https://audiofingerprint.openwpm.com/ when fingerprinting protection is on
|
non_build
|
manual test run on android for per release specialty tests clear data button needs to have primary button colour upgrade to chromium installer check that installer is close to the size of the last release check the brave version in about and make sure it is exactly as expected visual look make sure thereafter every merge no chrome chromium words appear on normal or private tabs no chrome chromium icons are shown in normal or private tabs data pre requisite put previous build shortcut on the home screen also have several sites added to home screen from dots menu and then upgrade to new build verify that data from the previous build appears in the updated build as expected bookmarks etc verify that the cookies from the previous build are preserved after upgrade verify shortcut is still available on the home screen after upgrade verify sites added to home screen are still visible and able to be used after upgrade verify sync chain created in the previous version is still retained on upgrade verify settings changes done in the previous version are still retained on upgrade bookmarks verify that creating a bookmark works verify that clicking a bookmark loads the bookmark verify that deleting a bookmark works verify that creating a bookmark folder works custom tabs make sure brave handles links from gmail slack make sure brave works as custom tabs provide with chrome browser ensure custom tabs work even with sync enabled disabled context menus make sure context menu items in the url bar work make sure context menu items on content work with no selected text make sure context menu items on content work with selected text make sure context menu items on content work inside an editable control input textarea or contenteditable developer tools verify you can inspect sublinks via dev tools find in page ensure search box is shown when selected via the hamburger menu verify that you can successfully find a word on the page verify that the forward and backward navigation icons under find are working verify failed to find shows results site hacks verify sub page loads a video and you can play it settings and bottom bar verify changing default settings are retained and don t cause the browser to crash verify bottom bar buttons home bookmark search tabs work as expected downloads verify downloading a file works and that all actions on the download item work verify that pdf is downloaded over https at verify that pdf is downloaded over http at fullscreen verify that entering fullscreen works and pressing restore to go back exits full screen youtube com autofill tests verify that autofill works on zoom verify zoom in out gestures work verify that navigating to a different origin resets the zoom bravery settings check that https everywhere works by loading turning https everywhere off and shields off both disable the redirect to check that toggling to blocking and allow ads works as expected verify that clicking through a cert error in works visit and then turn on script blocking nothing should load allow it from the script blocking ui in the url bar and it should work verify that default bravery settings take effect on pages with no site settings verify that party storage results are blank at when party cookies are blocked fingerprint tests visit ensure blocked items are listed in shields verify that doesn t leak ip address when block all fingerprinting protection is on content tests go to and click on the twitter icon on the top right verify that context menus work in the new twitter tab go to and make sure that the password can be saved make sure the saved password is auto populated when you visit the site again open a github issue and type some misspellings make sure they aren t autocorrected open an email on or inbox google com and click on a link make sure it works verify that shows up as grey not red no mixed content scripts are run sync verify you are able to join sync chain by scanning the qr code verify you are able to join sync chain using code words verify you are able to create a sync chain on the device and add other devices to the chain via qr code code words verify that bookmarks from other devices on the chain show up on the mobile device after sync completes verify newly created bookmarks gets sync d to all devices on the sync chain verify existing bookmarks before joining sync chain also gets sync d to all devices on the sync chain verify sync works on an upgrade profile and new bookmarks added post upgrade sync s across devices on the chain verify adding a bookmark on custom tab gets synced across all devices in the chain verify you are able to create a standalone sync chain with one device top sites view long press on top sites to get to deletion mode and delete a top site note this will stop that site from showing up again on top sites so you may not want to do this a site you want to keep there background start loading a page background the app wait sec then bring to front ensure splash screen is not shown session storage verify that tabs restore when closed including active tab yet to be implemented check that ad replacement works on verify that safe browsing works turning safe browsing off and shields off both disable safe browsing for verify that turning on fingerprinting protection in privacy shows fingerprints blocked at verify that turning it off in the bravery menu shows fingerprints blocked verify that audio fingerprint is blocked at when fingerprinting protection is on
| 0
|
63,972
| 14,656,818,830
|
IssuesEvent
|
2020-12-28 14:16:06
|
fu1771695yongxie/odoo
|
https://api.github.com/repos/fu1771695yongxie/odoo
|
opened
|
CVE-2015-9251 (Medium) detected in jquery-1.6.2.js, jquery-2.1.3.min.js
|
security vulnerability
|
## CVE-2015-9251 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>jquery-1.6.2.js</b>, <b>jquery-2.1.3.min.js</b></p></summary>
<p>
<details><summary><b>jquery-1.6.2.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.6.2/jquery.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.6.2/jquery.js</a></p>
<p>Path to dependency file: odoo/addons/web/node_modules/qs/test/browser/index.html</p>
<p>Path to vulnerable library: odoo/addons/web/node_modules/qs/test/browser/jquery.js</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.6.2.js** (Vulnerable Library)
</details>
<details><summary><b>jquery-2.1.3.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/2.1.3/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/2.1.3/jquery.min.js</a></p>
<p>Path to vulnerable library: odoo/doc/_extensions/odoo_ext/static/jquery.min.js</p>
<p>
Dependency Hierarchy:
- :x: **jquery-2.1.3.min.js** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/fu1771695yongxie/odoo/commit/d2f4766e5250a653951e7d3f6813f6da8973da84">d2f4766e5250a653951e7d3f6813f6da8973da84</a></p>
<p>Found in base branch: <b>14.0</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>
jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS) attacks when a cross-domain Ajax request is performed without the dataType option, causing text/javascript responses to be executed.
<p>Publish Date: 2018-01-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-9251>CVE-2015-9251</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://nvd.nist.gov/vuln/detail/CVE-2015-9251">https://nvd.nist.gov/vuln/detail/CVE-2015-9251</a></p>
<p>Release Date: 2018-01-18</p>
<p>Fix Resolution: jQuery - v3.0.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-2015-9251 (Medium) detected in jquery-1.6.2.js, jquery-2.1.3.min.js - ## CVE-2015-9251 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>jquery-1.6.2.js</b>, <b>jquery-2.1.3.min.js</b></p></summary>
<p>
<details><summary><b>jquery-1.6.2.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.6.2/jquery.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.6.2/jquery.js</a></p>
<p>Path to dependency file: odoo/addons/web/node_modules/qs/test/browser/index.html</p>
<p>Path to vulnerable library: odoo/addons/web/node_modules/qs/test/browser/jquery.js</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.6.2.js** (Vulnerable Library)
</details>
<details><summary><b>jquery-2.1.3.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/2.1.3/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/2.1.3/jquery.min.js</a></p>
<p>Path to vulnerable library: odoo/doc/_extensions/odoo_ext/static/jquery.min.js</p>
<p>
Dependency Hierarchy:
- :x: **jquery-2.1.3.min.js** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/fu1771695yongxie/odoo/commit/d2f4766e5250a653951e7d3f6813f6da8973da84">d2f4766e5250a653951e7d3f6813f6da8973da84</a></p>
<p>Found in base branch: <b>14.0</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>
jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS) attacks when a cross-domain Ajax request is performed without the dataType option, causing text/javascript responses to be executed.
<p>Publish Date: 2018-01-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-9251>CVE-2015-9251</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://nvd.nist.gov/vuln/detail/CVE-2015-9251">https://nvd.nist.gov/vuln/detail/CVE-2015-9251</a></p>
<p>Release Date: 2018-01-18</p>
<p>Fix Resolution: jQuery - v3.0.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_build
|
cve medium detected in jquery js jquery min js cve medium severity vulnerability vulnerable libraries jquery js jquery min js jquery js javascript library for dom operations library home page a href path to dependency file odoo addons web node modules qs test browser index html path to vulnerable library odoo addons web node modules qs test browser jquery js dependency hierarchy x jquery js vulnerable library jquery min js javascript library for dom operations library home page a href path to vulnerable library odoo doc extensions odoo ext static jquery min js dependency hierarchy x jquery min js vulnerable library found in head commit a href found in base branch vulnerability details jquery before is vulnerable to cross site scripting xss attacks when a cross domain ajax request is performed without the datatype option causing text javascript responses to be executed publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution jquery step up your open source security game with whitesource
| 0
|
120,238
| 10,110,957,638
|
IssuesEvent
|
2019-07-30 11:35:28
|
imixs/imixs-workflow
|
https://api.github.com/repos/imixs/imixs-workflow
|
closed
|
AccessAdapter and OwnerPlugin
|
critical feature testing
|
Computing the ownerhship of a workitem must still be part of a plugin. This can not be handled by the ParticipantAdapter introduced in version 5.0.1
For that reason we split again the implementation into a new Adatper Class 'AccessAdapter' and plug-in 'OwnerPlugin'.
With this setup the ownership can be computed early in the processing life cycle depending on the Plugin definition of a BPMN model.
The Access Controll List (ACL) is computed by the new AccessAdapter at the end of the processing life cycle.
|
1.0
|
AccessAdapter and OwnerPlugin - Computing the ownerhship of a workitem must still be part of a plugin. This can not be handled by the ParticipantAdapter introduced in version 5.0.1
For that reason we split again the implementation into a new Adatper Class 'AccessAdapter' and plug-in 'OwnerPlugin'.
With this setup the ownership can be computed early in the processing life cycle depending on the Plugin definition of a BPMN model.
The Access Controll List (ACL) is computed by the new AccessAdapter at the end of the processing life cycle.
|
non_build
|
accessadapter and ownerplugin computing the ownerhship of a workitem must still be part of a plugin this can not be handled by the participantadapter introduced in version for that reason we split again the implementation into a new adatper class accessadapter and plug in ownerplugin with this setup the ownership can be computed early in the processing life cycle depending on the plugin definition of a bpmn model the access controll list acl is computed by the new accessadapter at the end of the processing life cycle
| 0
|
33,472
| 4,488,795,960
|
IssuesEvent
|
2016-08-30 08:44:22
|
initiatived21/d21
|
https://api.github.com/repos/initiatived21/d21
|
opened
|
favicon
|
Design enhancement
|
Zumindet bis zum tatsächlichen Launch sollten wir ein favicon für unsere Seite einbauen. Aus unserem eckigen Ubuntu-Logo lässt sich das ja auch ganz gut anstellen
|
1.0
|
favicon - Zumindet bis zum tatsächlichen Launch sollten wir ein favicon für unsere Seite einbauen. Aus unserem eckigen Ubuntu-Logo lässt sich das ja auch ganz gut anstellen
|
non_build
|
favicon zumindet bis zum tatsächlichen launch sollten wir ein favicon für unsere seite einbauen aus unserem eckigen ubuntu logo lässt sich das ja auch ganz gut anstellen
| 0
|
369,657
| 10,916,005,028
|
IssuesEvent
|
2019-11-21 12:26:21
|
ONEARMY/community-platform
|
https://api.github.com/repos/ONEARMY/community-platform
|
closed
|
[bug] email link in user profile is broken
|
Priority: High❕ Type:Bug🐛
|
**Describe the bug**
if you click on "email" it opens a page with a broken URL
**To Reproduce**
https://community.preciousplastic.com/u/Atelier%20Lamoureux
click on "email"
see broken page
**Expected behaviour**
I think we want to open a composing email window? using "mailto:"
|
1.0
|
[bug] email link in user profile is broken - **Describe the bug**
if you click on "email" it opens a page with a broken URL
**To Reproduce**
https://community.preciousplastic.com/u/Atelier%20Lamoureux
click on "email"
see broken page
**Expected behaviour**
I think we want to open a composing email window? using "mailto:"
|
non_build
|
email link in user profile is broken describe the bug if you click on email it opens a page with a broken url to reproduce click on email see broken page expected behaviour i think we want to open a composing email window using mailto
| 0
|
27,236
| 12,533,254,575
|
IssuesEvent
|
2020-06-04 17:16:48
|
microsoft/BotBuilder-Samples
|
https://api.github.com/repos/microsoft/BotBuilder-Samples
|
closed
|
Application hosted media calling bot which proactively messages aswell.
|
Bot Services customer-replied-to customer-reported
|
Trying to develop an application hosted media calling bot which when it joins an online meeting it can type a welcome message in the call chat.
The purpose of the bot is to record calls so I shall be use the updaterecordingstatus api and I want it to type a warning in the call/meeting chat window.
Finding not many good samples on the Microsoftgraphcomms repo...
|
1.0
|
Application hosted media calling bot which proactively messages aswell. - Trying to develop an application hosted media calling bot which when it joins an online meeting it can type a welcome message in the call chat.
The purpose of the bot is to record calls so I shall be use the updaterecordingstatus api and I want it to type a warning in the call/meeting chat window.
Finding not many good samples on the Microsoftgraphcomms repo...
|
non_build
|
application hosted media calling bot which proactively messages aswell trying to develop an application hosted media calling bot which when it joins an online meeting it can type a welcome message in the call chat the purpose of the bot is to record calls so i shall be use the updaterecordingstatus api and i want it to type a warning in the call meeting chat window finding not many good samples on the microsoftgraphcomms repo
| 0
|
667,156
| 22,420,010,174
|
IssuesEvent
|
2022-06-20 01:15:45
|
pixiebrix/pixiebrix-extension
|
https://api.github.com/repos/pixiebrix/pixiebrix-extension
|
closed
|
Add support for atomic operations
|
low priority runtime
|
Context
- Each brick is executed an async
- If multiple extensions are running at the same time, there's no guaranteed order
- Therefore, using a sequence like 1) get shared page state, 2) jq, 3) set shared page state could result in the mutations being performed on stale data
Implementation Sketch
- Introduce a "global interpreter lock" to the runtime
- Add a "atomic" control flow brick that grabs the lock for the extension+runId
- Have other extension wait for the lock to be released to run (where do they pause at?)
|
1.0
|
Add support for atomic operations - Context
- Each brick is executed an async
- If multiple extensions are running at the same time, there's no guaranteed order
- Therefore, using a sequence like 1) get shared page state, 2) jq, 3) set shared page state could result in the mutations being performed on stale data
Implementation Sketch
- Introduce a "global interpreter lock" to the runtime
- Add a "atomic" control flow brick that grabs the lock for the extension+runId
- Have other extension wait for the lock to be released to run (where do they pause at?)
|
non_build
|
add support for atomic operations context each brick is executed an async if multiple extensions are running at the same time there s no guaranteed order therefore using a sequence like get shared page state jq set shared page state could result in the mutations being performed on stale data implementation sketch introduce a global interpreter lock to the runtime add a atomic control flow brick that grabs the lock for the extension runid have other extension wait for the lock to be released to run where do they pause at
| 0
|
65,462
| 19,528,091,983
|
IssuesEvent
|
2021-12-30 11:43:05
|
primefaces/primefaces
|
https://api.github.com/repos/primefaces/primefaces
|
opened
|
Panel: bottom border radius of content is incorrect with footer
|
defect
|
Screenshots are taken from https://www.primefaces.org/showcase/ui/panel/panel.xhtml (Saga, but also happens with Vela and Arya).
<img width="272" alt="Screenshot 2021-12-30 at 12 36 08" src="https://user-images.githubusercontent.com/7500178/147748592-f3ebce40-177f-4f11-ac67-ab9c19685ec9.png">
<img width="254" alt="Screenshot 2021-12-30 at 12 36 17" src="https://user-images.githubusercontent.com/7500178/147748596-94bfb33f-b38d-47fe-8e3f-82f8387b6486.png">
|
1.0
|
Panel: bottom border radius of content is incorrect with footer - Screenshots are taken from https://www.primefaces.org/showcase/ui/panel/panel.xhtml (Saga, but also happens with Vela and Arya).
<img width="272" alt="Screenshot 2021-12-30 at 12 36 08" src="https://user-images.githubusercontent.com/7500178/147748592-f3ebce40-177f-4f11-ac67-ab9c19685ec9.png">
<img width="254" alt="Screenshot 2021-12-30 at 12 36 17" src="https://user-images.githubusercontent.com/7500178/147748596-94bfb33f-b38d-47fe-8e3f-82f8387b6486.png">
|
non_build
|
panel bottom border radius of content is incorrect with footer screenshots are taken from saga but also happens with vela and arya img width alt screenshot at src img width alt screenshot at src
| 0
|
38,429
| 10,195,255,697
|
IssuesEvent
|
2019-08-12 17:40:35
|
hashicorp/packer
|
https://api.github.com/repos/hashicorp/packer
|
closed
|
Packer 1.4.1 stucks on "Waiting for AMI to become ready..."
|
builder/amazon regression waiting-reply
|
- Packer version from `packer version 1.4.1`
- Host platform RHEL 6
- Debug log output from `PACKER_LOG=1 packer build template.json`.
Please 2019/06/06 13:10:26 ui: CENTOS7: Stopping instance
2019/06/06 13:10:27 ui: ==> CENTOS7: Waiting for the instance to stop...
2019/06/06 13:10:57 ui: ==> CENTOS7: Enabling Enhanced Networking (ENA)...
2019/06/06 13:10:57 ui: ==> CENTOS7: Creating AMI XXXXX-CENT7.6HVM-XX from instance i-05XXXXXXXXXXXXXXX
2019/06/06 13:10:58 ui: CENTOS7: AMI: ami-XXXXXXXXXXXX
2019/06/06 13:10:58 ui: ==> CENTOS7: Waiting for AMI to become ready...
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 ui error: Cancelling build after receiving interrupt
2019/06/06 13:26:12 Cancelling builder after context cancellation context canceled
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Error waiting for AMI: RequestCanceled: waiter context canceled
2019/06/06 13:26:12 packer: caused by: context canceled
2019/06/06 13:26:13 packer: 2019/06/06 13:26:13 Unable to determine reason waiting for AMI failed: RequestExpired: Request has expired.
2019/06/06 13:26:13 packer: status code: 400, request id: c97c4f36-401c-44d3-bfa8-147a89a7149b
2019/06/06 13:26:13 ui error: ==> CENTOS7: Unknown error waiting for AMI.
2019/06/06 13:26:13 ui: ==> CENTOS7: Terminating the source AWS instance...
With packer version 1.2.0, I am able to pack the AMIs without any issue.
|
1.0
|
Packer 1.4.1 stucks on "Waiting for AMI to become ready..." - - Packer version from `packer version 1.4.1`
- Host platform RHEL 6
- Debug log output from `PACKER_LOG=1 packer build template.json`.
Please 2019/06/06 13:10:26 ui: CENTOS7: Stopping instance
2019/06/06 13:10:27 ui: ==> CENTOS7: Waiting for the instance to stop...
2019/06/06 13:10:57 ui: ==> CENTOS7: Enabling Enhanced Networking (ENA)...
2019/06/06 13:10:57 ui: ==> CENTOS7: Creating AMI XXXXX-CENT7.6HVM-XX from instance i-05XXXXXXXXXXXXXXX
2019/06/06 13:10:58 ui: CENTOS7: AMI: ami-XXXXXXXXXXXX
2019/06/06 13:10:58 ui: ==> CENTOS7: Waiting for AMI to become ready...
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 ui error: Cancelling build after receiving interrupt
2019/06/06 13:26:12 Cancelling builder after context cancellation context canceled
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Received interrupt signal (count: 1). Ignoring.
2019/06/06 13:26:12 packer: 2019/06/06 13:26:12 Error waiting for AMI: RequestCanceled: waiter context canceled
2019/06/06 13:26:12 packer: caused by: context canceled
2019/06/06 13:26:13 packer: 2019/06/06 13:26:13 Unable to determine reason waiting for AMI failed: RequestExpired: Request has expired.
2019/06/06 13:26:13 packer: status code: 400, request id: c97c4f36-401c-44d3-bfa8-147a89a7149b
2019/06/06 13:26:13 ui error: ==> CENTOS7: Unknown error waiting for AMI.
2019/06/06 13:26:13 ui: ==> CENTOS7: Terminating the source AWS instance...
With packer version 1.2.0, I am able to pack the AMIs without any issue.
|
build
|
packer stucks on waiting for ami to become ready packer version from packer version host platform rhel debug log output from packer log packer build template json please ui stopping instance ui waiting for the instance to stop ui enabling enhanced networking ena ui creating ami xxxxx xx from instance i ui ami ami xxxxxxxxxxxx ui waiting for ami to become ready packer received interrupt signal count ignoring packer received interrupt signal count ignoring packer received interrupt signal count ignoring packer received interrupt signal count ignoring packer received interrupt signal count ignoring packer received interrupt signal count ignoring packer received interrupt signal count ignoring packer received interrupt signal count ignoring packer received interrupt signal count ignoring packer received interrupt signal count ignoring packer received interrupt signal count ignoring packer received interrupt signal count ignoring packer received interrupt signal count ignoring packer received interrupt signal count ignoring ui error cancelling build after receiving interrupt cancelling builder after context cancellation context canceled packer received interrupt signal count ignoring packer received interrupt signal count ignoring packer received interrupt signal count ignoring packer received interrupt signal count ignoring packer received interrupt signal count ignoring packer error waiting for ami requestcanceled waiter context canceled packer caused by context canceled packer unable to determine reason waiting for ami failed requestexpired request has expired packer status code request id ui error unknown error waiting for ami ui terminating the source aws instance with packer version i am able to pack the amis without any issue
| 1
|
236,942
| 19,587,364,076
|
IssuesEvent
|
2022-01-05 08:51:12
|
rapidsai/cuml
|
https://api.github.com/repos/rapidsai/cuml
|
closed
|
[BUG] Numerical warnings in `test_preprocessing.py::test_scale` pytest
|
bug tests inactive-30d
|
**Describe the bug**
When running the pytests in `cuml/test/test_preprocessing.py::test_scale` the following warnings happen that could be relevant to the correctness of the test:
```python
cuml/test/test_preprocessing.py: 20 warnings
/home/galahad/RAPIDS/21.10/cuml/enh-sklearn-024/python/cuml/_thirdparty/sklearn/preprocessing/_data.py:179: UserWarning: Numerical issues were encountered when centering the data and might not be solved. Dataset may contain too large values. You may need to prescale your features.
warnings.warn("Numerical issues were encountered "
cuml/test/test_preprocessing.py: 10 warnings
/home/galahad/RAPIDS/21.10/cuml/enh-sklearn-024/python/cuml/_thirdparty/sklearn/preprocessing/_data.py:196: UserWarning: Numerical issues were encountered when scaling the data and might not be solved. The standard deviation of the data is probably very close to 0.
warnings.warn("Numerical issues were encountered "
cuml/test/test_preprocessing.py: 20 warnings
/home/galahad/miniconda3/envs/ns0909/lib/python3.8/site-packages/sklearn/preprocessing/_data.py:194: UserWarning: Numerical issues were encountered when centering the data and might not be solved. Dataset may contain too large values. You may need to prescale your features.
warnings.warn("Numerical issues were encountered "
cuml/test/test_preprocessing.py: 10 warnings
/home/galahad/miniconda3/envs/ns0909/lib/python3.8/site-packages/sklearn/preprocessing/_data.py:211: UserWarning: Numerical issues were encountered when scaling the data and might not be solved. The standard deviation of the data is probably very close to 0.
warnings.warn("Numerical issues were encountered "
```
The warnings will be ignored by pytest to improve CI logs, but they still need to be dealt with.
|
1.0
|
[BUG] Numerical warnings in `test_preprocessing.py::test_scale` pytest - **Describe the bug**
When running the pytests in `cuml/test/test_preprocessing.py::test_scale` the following warnings happen that could be relevant to the correctness of the test:
```python
cuml/test/test_preprocessing.py: 20 warnings
/home/galahad/RAPIDS/21.10/cuml/enh-sklearn-024/python/cuml/_thirdparty/sklearn/preprocessing/_data.py:179: UserWarning: Numerical issues were encountered when centering the data and might not be solved. Dataset may contain too large values. You may need to prescale your features.
warnings.warn("Numerical issues were encountered "
cuml/test/test_preprocessing.py: 10 warnings
/home/galahad/RAPIDS/21.10/cuml/enh-sklearn-024/python/cuml/_thirdparty/sklearn/preprocessing/_data.py:196: UserWarning: Numerical issues were encountered when scaling the data and might not be solved. The standard deviation of the data is probably very close to 0.
warnings.warn("Numerical issues were encountered "
cuml/test/test_preprocessing.py: 20 warnings
/home/galahad/miniconda3/envs/ns0909/lib/python3.8/site-packages/sklearn/preprocessing/_data.py:194: UserWarning: Numerical issues were encountered when centering the data and might not be solved. Dataset may contain too large values. You may need to prescale your features.
warnings.warn("Numerical issues were encountered "
cuml/test/test_preprocessing.py: 10 warnings
/home/galahad/miniconda3/envs/ns0909/lib/python3.8/site-packages/sklearn/preprocessing/_data.py:211: UserWarning: Numerical issues were encountered when scaling the data and might not be solved. The standard deviation of the data is probably very close to 0.
warnings.warn("Numerical issues were encountered "
```
The warnings will be ignored by pytest to improve CI logs, but they still need to be dealt with.
|
non_build
|
numerical warnings in test preprocessing py test scale pytest describe the bug when running the pytests in cuml test test preprocessing py test scale the following warnings happen that could be relevant to the correctness of the test python cuml test test preprocessing py warnings home galahad rapids cuml enh sklearn python cuml thirdparty sklearn preprocessing data py userwarning numerical issues were encountered when centering the data and might not be solved dataset may contain too large values you may need to prescale your features warnings warn numerical issues were encountered cuml test test preprocessing py warnings home galahad rapids cuml enh sklearn python cuml thirdparty sklearn preprocessing data py userwarning numerical issues were encountered when scaling the data and might not be solved the standard deviation of the data is probably very close to warnings warn numerical issues were encountered cuml test test preprocessing py warnings home galahad envs lib site packages sklearn preprocessing data py userwarning numerical issues were encountered when centering the data and might not be solved dataset may contain too large values you may need to prescale your features warnings warn numerical issues were encountered cuml test test preprocessing py warnings home galahad envs lib site packages sklearn preprocessing data py userwarning numerical issues were encountered when scaling the data and might not be solved the standard deviation of the data is probably very close to warnings warn numerical issues were encountered the warnings will be ignored by pytest to improve ci logs but they still need to be dealt with
| 0
|
33,286
| 9,087,125,960
|
IssuesEvent
|
2019-02-18 12:55:32
|
ethereum/aleth
|
https://api.github.com/repos/ethereum/aleth
|
closed
|
Roll cpp-ethereum ARM binaries into PPA so they are available via apt-get
|
build enhancement
|
_From @phonikg on February 16, 2016 23:0_
I understand it may be a lower priority item, but I believe this is possible, especially by automating the x-compile work that doublethink.co has done.
_Copied from original issue: ethereum/webthree-umbrella#228_
|
1.0
|
Roll cpp-ethereum ARM binaries into PPA so they are available via apt-get - _From @phonikg on February 16, 2016 23:0_
I understand it may be a lower priority item, but I believe this is possible, especially by automating the x-compile work that doublethink.co has done.
_Copied from original issue: ethereum/webthree-umbrella#228_
|
build
|
roll cpp ethereum arm binaries into ppa so they are available via apt get from phonikg on february i understand it may be a lower priority item but i believe this is possible especially by automating the x compile work that doublethink co has done copied from original issue ethereum webthree umbrella
| 1
|
165,481
| 26,179,586,678
|
IssuesEvent
|
2023-01-02 14:00:20
|
coq/coq
|
https://api.github.com/repos/coq/coq
|
closed
|
coqdoc generated index.html too verbose ?
|
kind: documentation part: coqdoc kind: design discussion
|
<!-- Thank you for reporting a bug to Coq! -->
Hi,
The file index.html generated by coqtop contains a lot of links associated with bound variables.
For instance, the following lemma
~~~coq
Lemma eq_b_iff (alpha beta : T1) :
eq_b alpha beta = true ↔ alpha = beta.
~~~
generates the entry
~~~
alpha:130 [binder, in hydras.Epsilon0.T1]
~~~
The same problem occurs even in the case of an explicitely quantified variable.
Thus, I get at least one thousand entries for the variable alpha !
Is it possible to tell coqdoc not to insert binders in the index ?
Pierre
(on Coq 8.12.0 (July 2020))
<!-- If you can, it's helpful to provide self-contained example of some code
that reproduces the bug. If not, a link to a larger example is also helpful.
You can generate a shorter version of your program by following these
instructions: https://github.com/coq/coq/wiki/Coqbot-minimize-feature. -->
#### Coq Version
<!-- You can get this information by running `coqtop -v`. If relevant, please
also include your operating system. -->
|
1.0
|
coqdoc generated index.html too verbose ? - <!-- Thank you for reporting a bug to Coq! -->
Hi,
The file index.html generated by coqtop contains a lot of links associated with bound variables.
For instance, the following lemma
~~~coq
Lemma eq_b_iff (alpha beta : T1) :
eq_b alpha beta = true ↔ alpha = beta.
~~~
generates the entry
~~~
alpha:130 [binder, in hydras.Epsilon0.T1]
~~~
The same problem occurs even in the case of an explicitely quantified variable.
Thus, I get at least one thousand entries for the variable alpha !
Is it possible to tell coqdoc not to insert binders in the index ?
Pierre
(on Coq 8.12.0 (July 2020))
<!-- If you can, it's helpful to provide self-contained example of some code
that reproduces the bug. If not, a link to a larger example is also helpful.
You can generate a shorter version of your program by following these
instructions: https://github.com/coq/coq/wiki/Coqbot-minimize-feature. -->
#### Coq Version
<!-- You can get this information by running `coqtop -v`. If relevant, please
also include your operating system. -->
|
non_build
|
coqdoc generated index html too verbose hi the file index html generated by coqtop contains a lot of links associated with bound variables for instance the following lemma coq lemma eq b iff alpha beta eq b alpha beta true ↔ alpha beta generates the entry alpha the same problem occurs even in the case of an explicitely quantified variable thus i get at least one thousand entries for the variable alpha is it possible to tell coqdoc not to insert binders in the index pierre on coq july if you can it s helpful to provide self contained example of some code that reproduces the bug if not a link to a larger example is also helpful you can generate a shorter version of your program by following these instructions coq version you can get this information by running coqtop v if relevant please also include your operating system
| 0
|
77,954
| 22,051,942,075
|
IssuesEvent
|
2022-05-30 09:25:34
|
fraunhoferhhi/vvenc
|
https://api.github.com/repos/fraunhoferhhi/vvenc
|
closed
|
Build error when using Visual Studio 17 2022
|
build
|
Hello,
I got this error when build a vvenc:
My command: cmake -B build -DCMAKE_BUILD_TYPE=Release
cmake -S . -B build/release-shared -DCMAKE_INSTALL_PREFIX=/usr/local -DCMAKE_BUILD_TYPE=Release -DBUILD_SHARED_LIBS=1
Can i have a solution for this ?
Thanks!
|
1.0
|
Build error when using Visual Studio 17 2022 - Hello,
I got this error when build a vvenc:
My command: cmake -B build -DCMAKE_BUILD_TYPE=Release
cmake -S . -B build/release-shared -DCMAKE_INSTALL_PREFIX=/usr/local -DCMAKE_BUILD_TYPE=Release -DBUILD_SHARED_LIBS=1
Can i have a solution for this ?
Thanks!
|
build
|
build error when using visual studio hello i got this error when build a vvenc my command cmake b build dcmake build type release cmake s b build release shared dcmake install prefix usr local dcmake build type release dbuild shared libs can i have a solution for this thanks
| 1
|
100,785
| 30,774,907,236
|
IssuesEvent
|
2023-07-31 05:20:47
|
SoftFever/OrcaSlicer
|
https://api.github.com/repos/SoftFever/OrcaSlicer
|
closed
|
[BUG] Process settings disappear if you save and load the project.
|
bug nightly build
|
If I change any settings like number of walls, speed, number of bottom layers, top and any others, then save the project and load it, then all settings will be lost and the ones saved by default in the process profile will be used.
**3mf File for This Bug**
no model needed to reproduce or any
**To Reproduce**
1. Run the program
2. Change any parameters in the process - the number of walls, bottom layers, top, speed. Any
3. Save the project
4. Open this project (do not save changes to the process profile)
5. Switch tabs - Quality, Strength, Speed
You will see that your changes are gone and the settings saved in the process profile are being used.
**Printer model**
Bambu Lab X1C
**Desktop (please complete the following information):**
- OS: Windows 10
- Version last from Actions https://github.com/SoftFever/OrcaSlicer/actions/runs/5704604879
- The version I'm using without this error https://github.com/SoftFever/OrcaSlicer/actions/runs/5578530790
UPD. It seems to me that the error appeared starting with this build - https://github.com/SoftFever/OrcaSlicer/actions/runs/5657699530
|
1.0
|
[BUG] Process settings disappear if you save and load the project. - If I change any settings like number of walls, speed, number of bottom layers, top and any others, then save the project and load it, then all settings will be lost and the ones saved by default in the process profile will be used.
**3mf File for This Bug**
no model needed to reproduce or any
**To Reproduce**
1. Run the program
2. Change any parameters in the process - the number of walls, bottom layers, top, speed. Any
3. Save the project
4. Open this project (do not save changes to the process profile)
5. Switch tabs - Quality, Strength, Speed
You will see that your changes are gone and the settings saved in the process profile are being used.
**Printer model**
Bambu Lab X1C
**Desktop (please complete the following information):**
- OS: Windows 10
- Version last from Actions https://github.com/SoftFever/OrcaSlicer/actions/runs/5704604879
- The version I'm using without this error https://github.com/SoftFever/OrcaSlicer/actions/runs/5578530790
UPD. It seems to me that the error appeared starting with this build - https://github.com/SoftFever/OrcaSlicer/actions/runs/5657699530
|
build
|
process settings disappear if you save and load the project if i change any settings like number of walls speed number of bottom layers top and any others then save the project and load it then all settings will be lost and the ones saved by default in the process profile will be used file for this bug no model needed to reproduce or any to reproduce run the program change any parameters in the process the number of walls bottom layers top speed any save the project open this project do not save changes to the process profile switch tabs quality strength speed you will see that your changes are gone and the settings saved in the process profile are being used printer model bambu lab desktop please complete the following information os windows version last from actions the version i m using without this error upd it seems to me that the error appeared starting with this build
| 1
|
134,563
| 19,271,894,237
|
IssuesEvent
|
2021-12-10 07:00:41
|
dotnet/aspnetcore
|
https://api.github.com/repos/dotnet/aspnetcore
|
closed
|
Add possibility to customize `Server` response header in `KestrelServerOptions`
|
:heavy_check_mark: Resolution: By Design area-runtime Status: Resolved
|
Hi we have option to disable response header `Server=Kestrel` however in our case we would like to use a generic `CodeName` instead `Kestrel`. We want to preserve header itself as it allows us to distinguish which layer has responded (microservice, load-balancer or cdn and etc) but for security reasons we do not want to expose which concrete implementation we are relaying on.
I know we could disable adding server header by Kestrel itself and adding it manually in middleware, however I believe we would risk on rare occasions responses without this header if request would be terminated before reaching our middleware.
|
1.0
|
Add possibility to customize `Server` response header in `KestrelServerOptions` - Hi we have option to disable response header `Server=Kestrel` however in our case we would like to use a generic `CodeName` instead `Kestrel`. We want to preserve header itself as it allows us to distinguish which layer has responded (microservice, load-balancer or cdn and etc) but for security reasons we do not want to expose which concrete implementation we are relaying on.
I know we could disable adding server header by Kestrel itself and adding it manually in middleware, however I believe we would risk on rare occasions responses without this header if request would be terminated before reaching our middleware.
|
non_build
|
add possibility to customize server response header in kestrelserveroptions hi we have option to disable response header server kestrel however in our case we would like to use a generic codename instead kestrel we want to preserve header itself as it allows us to distinguish which layer has responded microservice load balancer or cdn and etc but for security reasons we do not want to expose which concrete implementation we are relaying on i know we could disable adding server header by kestrel itself and adding it manually in middleware however i believe we would risk on rare occasions responses without this header if request would be terminated before reaching our middleware
| 0
|
36,055
| 9,733,779,045
|
IssuesEvent
|
2019-05-31 10:34:42
|
angular/angular-cli
|
https://api.github.com/repos/angular/angular-cli
|
opened
|
ES2015 class with decorators are not being treeshaken away
|
comp: devkit/build-optimizer freq2: medium severity3: broken type: bug/fix
|
<!--🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅
Oh hi there! 😄
To expedite issue processing please search open and closed issues before submitting a new one.
Existing issues often contain information about workarounds, resolution, or progress updates.
🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅-->
# 🐞 Bug report
### Command (mark with an `x`)
<!-- Can you pin-point the command or commands that are effected by this bug? -->
<!-- ✍️edit: -->
```
- [ ] new
- [x] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc
```
### Description
When not using tsickle, TypeScript emits the following code for classes which have property or method decorators
```ts
export class foo {
bar() {
}
}
__decorate([
decorator()
], foo.prototype, "bar", null);
```
The problematic as terser is unable to drop the above code if the Class is unused.
## 🌍 Your Environment
<pre><code>
Angular CLI: 8.0.0
Node: 11.0.0
OS: win32 x64
Angular: 8.0.0
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router
Package Version
-----------------------------------------------------------
@angular-devkit/architect 0.800.0
@angular-devkit/build-angular 0.800.0
@angular-devkit/build-optimizer 0.800.0
@angular-devkit/build-webpack 0.800.0
@angular-devkit/core 8.0.0
@angular-devkit/schematics 8.0.0
@ngtools/webpack 8.0.0
@schematics/angular 8.0.0
@schematics/update 0.800.0
rxjs 6.4.0
typescript 3.4.5
webpack 4.30.0
</code></pre>
**Anything else relevant?**
<!-- ✍️Is this a browser specific issue? If so, please specify the browser and version. -->
<!-- ✍️Do any of these matter: operating system, IDE, package manager, HTTP server, ...? If so, please mention it below. -->
Related to #14577
|
1.0
|
ES2015 class with decorators are not being treeshaken away - <!--🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅
Oh hi there! 😄
To expedite issue processing please search open and closed issues before submitting a new one.
Existing issues often contain information about workarounds, resolution, or progress updates.
🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅-->
# 🐞 Bug report
### Command (mark with an `x`)
<!-- Can you pin-point the command or commands that are effected by this bug? -->
<!-- ✍️edit: -->
```
- [ ] new
- [x] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc
```
### Description
When not using tsickle, TypeScript emits the following code for classes which have property or method decorators
```ts
export class foo {
bar() {
}
}
__decorate([
decorator()
], foo.prototype, "bar", null);
```
The problematic as terser is unable to drop the above code if the Class is unused.
## 🌍 Your Environment
<pre><code>
Angular CLI: 8.0.0
Node: 11.0.0
OS: win32 x64
Angular: 8.0.0
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router
Package Version
-----------------------------------------------------------
@angular-devkit/architect 0.800.0
@angular-devkit/build-angular 0.800.0
@angular-devkit/build-optimizer 0.800.0
@angular-devkit/build-webpack 0.800.0
@angular-devkit/core 8.0.0
@angular-devkit/schematics 8.0.0
@ngtools/webpack 8.0.0
@schematics/angular 8.0.0
@schematics/update 0.800.0
rxjs 6.4.0
typescript 3.4.5
webpack 4.30.0
</code></pre>
**Anything else relevant?**
<!-- ✍️Is this a browser specific issue? If so, please specify the browser and version. -->
<!-- ✍️Do any of these matter: operating system, IDE, package manager, HTTP server, ...? If so, please mention it below. -->
Related to #14577
|
build
|
class with decorators are not being treeshaken away 🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅 oh hi there 😄 to expedite issue processing please search open and closed issues before submitting a new one existing issues often contain information about workarounds resolution or progress updates 🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅 🐞 bug report command mark with an x new build serve test generate add update lint run config help version doc description when not using tsickle typescript emits the following code for classes which have property or method decorators ts export class foo bar decorate decorator foo prototype bar null the problematic as terser is unable to drop the above code if the class is unused 🌍 your environment angular cli node os angular animations cli common compiler compiler cli core forms language service platform browser platform browser dynamic router package version angular devkit architect angular devkit build angular angular devkit build optimizer angular devkit build webpack angular devkit core angular devkit schematics ngtools webpack schematics angular schematics update rxjs typescript webpack anything else relevant related to
| 1
|
10,318
| 4,751,462,919
|
IssuesEvent
|
2016-10-22 22:12:04
|
chilblane/chilblane.github.io
|
https://api.github.com/repos/chilblane/chilblane.github.io
|
closed
|
Switch to a build system
|
build & deploy
|
Research and implement a build system that can work with GitHub Pages.
Enables:
- HTML templating
- CSS preprocessing
- Environment variables
|
1.0
|
Switch to a build system - Research and implement a build system that can work with GitHub Pages.
Enables:
- HTML templating
- CSS preprocessing
- Environment variables
|
build
|
switch to a build system research and implement a build system that can work with github pages enables html templating css preprocessing environment variables
| 1
|
180,603
| 21,625,798,760
|
IssuesEvent
|
2022-05-05 01:51:01
|
mgh3326/studyolle
|
https://api.github.com/repos/mgh3326/studyolle
|
closed
|
WS-2018-0084 (High) detected in nodev4.6.1 - autoclosed
|
security vulnerability
|
## WS-2018-0084 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>nodev4.6.1</b></p></summary>
<p>
<p>Node.js JavaScript runtime :sparkles::turtle::rocket::sparkles:</p>
<p>Library home page: <a href=https://github.com/nodejs/node.git>https://github.com/nodejs/node.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/mgh3326/studyolle/commit/57ad34c02d62ce3b8eb4cb40f157e3d1b073d92e">57ad34c02d62ce3b8eb4cb40f157e3d1b073d92e</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>studyolle/target/classes/static/node/node_modules/npm/node_modules/request/node_modules/http-signature/node_modules/sshpk/lib/formats/ssh.js</b>
</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>
Versions of sshpk before 1.14.1 are vulnerable to regular expression denial of service when parsing crafted invalid public keys.
<p>Publish Date: 2018-04-25
<p>URL: <a href=https://github.com/joyent/node-sshpk/blob/v1.13.1/lib/formats/ssh.js#L17>WS-2018-0084</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://nodesecurity.io/advisories/606">https://nodesecurity.io/advisories/606</a></p>
<p>Release Date: 2018-01-27</p>
<p>Fix Resolution: 1.14.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-2018-0084 (High) detected in nodev4.6.1 - autoclosed - ## WS-2018-0084 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>nodev4.6.1</b></p></summary>
<p>
<p>Node.js JavaScript runtime :sparkles::turtle::rocket::sparkles:</p>
<p>Library home page: <a href=https://github.com/nodejs/node.git>https://github.com/nodejs/node.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/mgh3326/studyolle/commit/57ad34c02d62ce3b8eb4cb40f157e3d1b073d92e">57ad34c02d62ce3b8eb4cb40f157e3d1b073d92e</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>studyolle/target/classes/static/node/node_modules/npm/node_modules/request/node_modules/http-signature/node_modules/sshpk/lib/formats/ssh.js</b>
</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>
Versions of sshpk before 1.14.1 are vulnerable to regular expression denial of service when parsing crafted invalid public keys.
<p>Publish Date: 2018-04-25
<p>URL: <a href=https://github.com/joyent/node-sshpk/blob/v1.13.1/lib/formats/ssh.js#L17>WS-2018-0084</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://nodesecurity.io/advisories/606">https://nodesecurity.io/advisories/606</a></p>
<p>Release Date: 2018-01-27</p>
<p>Fix Resolution: 1.14.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_build
|
ws high detected in autoclosed ws high severity vulnerability vulnerable library node js javascript runtime sparkles turtle rocket sparkles library home page a href found in head commit a href found in base branch master vulnerable source files studyolle target classes static node node modules npm node modules request node modules http signature node modules sshpk lib formats ssh js vulnerability details versions of sshpk before are vulnerable to regular expression denial of service when parsing crafted invalid public keys 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
|
260,805
| 27,784,757,317
|
IssuesEvent
|
2023-03-17 01:34:50
|
utopikkad/vue-modal
|
https://api.github.com/repos/utopikkad/vue-modal
|
opened
|
CVE-2020-8116 (High) detected in dot-prop-4.2.0.tgz
|
Mend: dependency security vulnerability
|
## CVE-2020-8116 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>dot-prop-4.2.0.tgz</b></p></summary>
<p>Get, set, or delete a property from a nested object using a dot path</p>
<p>Library home page: <a href="https://registry.npmjs.org/dot-prop/-/dot-prop-4.2.0.tgz">https://registry.npmjs.org/dot-prop/-/dot-prop-4.2.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/dot-prop/package.json</p>
<p>
Dependency Hierarchy:
- cli-service-3.12.1.tgz (Root Library)
- optimize-cssnano-plugin-1.0.6.tgz
- cssnano-preset-default-4.0.7.tgz
- postcss-merge-rules-4.0.3.tgz
- postcss-selector-parser-3.1.1.tgz
- :x: **dot-prop-4.2.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Prototype pollution vulnerability in dot-prop npm package versions before 4.2.1 and versions 5.x before 5.1.1 allows an attacker to add arbitrary properties to JavaScript language constructs such as objects.
<p>Publish Date: 2020-02-04
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-8116>CVE-2020-8116</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.3</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: 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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8116">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8116</a></p>
<p>Release Date: 2020-02-04</p>
<p>Fix Resolution (dot-prop): 4.2.1</p>
<p>Direct dependency fix Resolution (@vue/cli-service): 4.0.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-2020-8116 (High) detected in dot-prop-4.2.0.tgz - ## CVE-2020-8116 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>dot-prop-4.2.0.tgz</b></p></summary>
<p>Get, set, or delete a property from a nested object using a dot path</p>
<p>Library home page: <a href="https://registry.npmjs.org/dot-prop/-/dot-prop-4.2.0.tgz">https://registry.npmjs.org/dot-prop/-/dot-prop-4.2.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/dot-prop/package.json</p>
<p>
Dependency Hierarchy:
- cli-service-3.12.1.tgz (Root Library)
- optimize-cssnano-plugin-1.0.6.tgz
- cssnano-preset-default-4.0.7.tgz
- postcss-merge-rules-4.0.3.tgz
- postcss-selector-parser-3.1.1.tgz
- :x: **dot-prop-4.2.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Prototype pollution vulnerability in dot-prop npm package versions before 4.2.1 and versions 5.x before 5.1.1 allows an attacker to add arbitrary properties to JavaScript language constructs such as objects.
<p>Publish Date: 2020-02-04
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-8116>CVE-2020-8116</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.3</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: 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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8116">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8116</a></p>
<p>Release Date: 2020-02-04</p>
<p>Fix Resolution (dot-prop): 4.2.1</p>
<p>Direct dependency fix Resolution (@vue/cli-service): 4.0.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_build
|
cve high detected in dot prop tgz cve high severity vulnerability vulnerable library dot prop tgz get set or delete a property from a nested object using a dot path library home page a href path to dependency file package json path to vulnerable library node modules dot prop package json dependency hierarchy cli service tgz root library optimize cssnano plugin tgz cssnano preset default tgz postcss merge rules tgz postcss selector parser tgz x dot prop tgz vulnerable library found in base branch master vulnerability details prototype pollution vulnerability in dot prop npm package versions before and versions x before allows an attacker to add arbitrary properties to javascript language constructs such as objects 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 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 dot prop direct dependency fix resolution vue cli service step up your open source security game with mend
| 0
|
3,790
| 2,917,961,187
|
IssuesEvent
|
2015-06-24 03:17:54
|
openframeworks/openFrameworks
|
https://api.github.com/repos/openframeworks/openFrameworks
|
opened
|
iOS arm64 - ld: 128-bit / 64-bit LDR/STR not 16-byte / 8-byte aligned
|
iOS xcode
|
#### The following Errors reported in linking process for iOS arm64.
```
ld: 128-bit LDR/STR not 16-byte aligned: from pcrestudy (0x1001B2E74) to l013@0x00004334 (0x1006DC85C) in 'pcrestudy' from ../../../libs/poco/lib/ios/PocoFoundation.a(pcre_study.o) for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
```
http://forum.openframeworks.cc/t/poco-linking-error-for-ios-64-bit/19831
```
ld: 64-bit LDR/STR not 8-byte aligned: from ZN2cv7compareERKNS_11_InputArrayES2_RKNS_12_OutputArrayEi (0x100661428) to l173@0x0001E3D8 (0x100D3625C) in 'ZN2cv7compareERKNS_11_InputArrayES2_RKNS_12_OutputArrayEi' from addons/ofxOpenCv/libs/opencv/lib/ios/opencv_core.a(arithm.cpp.o) for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
```
http://forum.openframeworks.cc/t/solved-linker-errors-with-opencv-64bits/19572/5?u=danoli3
```
ld: 64-bit LDR/STR not 8-byte aligned: from __ZN2cv7compareERKNS_11_InputArrayES2_RKNS_12_OutputArrayEi (0x100661428) to l173@0x0001E3D8 (0x100D3625C) in '__ZN2cv7compareERKNS_11_InputArrayES2_RKNS_12_OutputArrayEi' from addons/ofxOpenCv/libs/opencv/lib/ios/opencv_core.a(arithm.cpp.o) for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
```
https://github.com/openframeworks/openFrameworks/issues/3039#issuecomment-102740590
```
cause this error
ld: 128-bit LDR/STR not 16-byte aligned: from __ZN13CResizeEngine16horizontalFilterEP8FIBITMAPjjjjPK10tagRGBQUADS1_j (0x1006FFF20) to l005@0x00000850 (0x100B825D8) in '__ZN13CResizeEngine16horizontalFilterEP8FIBITMAPjjjjPK10tagRGBQUADS1_j' from /Users/mahmoudnasr/Desktop/-------/-----/AR/QCAR/REVU_IOS/FreeImage/lib/ios/freeimage.a(Resize.o-arm64) for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
```
https://github.com/openframeworks/openFrameworks/commit/dcc7debab977dfb136ceb205890a04617c68b621#commitcomment-11791432
# Problem:
- This is caused by a LLVM alignment compatibility issue with older Xcode Versions / LLVM compiler.
## Solution:
- Update Xcode to 6.3.1 or greater
- This is mandatory for iOS AppStore submissions anyway
|
1.0
|
iOS arm64 - ld: 128-bit / 64-bit LDR/STR not 16-byte / 8-byte aligned - #### The following Errors reported in linking process for iOS arm64.
```
ld: 128-bit LDR/STR not 16-byte aligned: from pcrestudy (0x1001B2E74) to l013@0x00004334 (0x1006DC85C) in 'pcrestudy' from ../../../libs/poco/lib/ios/PocoFoundation.a(pcre_study.o) for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
```
http://forum.openframeworks.cc/t/poco-linking-error-for-ios-64-bit/19831
```
ld: 64-bit LDR/STR not 8-byte aligned: from ZN2cv7compareERKNS_11_InputArrayES2_RKNS_12_OutputArrayEi (0x100661428) to l173@0x0001E3D8 (0x100D3625C) in 'ZN2cv7compareERKNS_11_InputArrayES2_RKNS_12_OutputArrayEi' from addons/ofxOpenCv/libs/opencv/lib/ios/opencv_core.a(arithm.cpp.o) for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
```
http://forum.openframeworks.cc/t/solved-linker-errors-with-opencv-64bits/19572/5?u=danoli3
```
ld: 64-bit LDR/STR not 8-byte aligned: from __ZN2cv7compareERKNS_11_InputArrayES2_RKNS_12_OutputArrayEi (0x100661428) to l173@0x0001E3D8 (0x100D3625C) in '__ZN2cv7compareERKNS_11_InputArrayES2_RKNS_12_OutputArrayEi' from addons/ofxOpenCv/libs/opencv/lib/ios/opencv_core.a(arithm.cpp.o) for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
```
https://github.com/openframeworks/openFrameworks/issues/3039#issuecomment-102740590
```
cause this error
ld: 128-bit LDR/STR not 16-byte aligned: from __ZN13CResizeEngine16horizontalFilterEP8FIBITMAPjjjjPK10tagRGBQUADS1_j (0x1006FFF20) to l005@0x00000850 (0x100B825D8) in '__ZN13CResizeEngine16horizontalFilterEP8FIBITMAPjjjjPK10tagRGBQUADS1_j' from /Users/mahmoudnasr/Desktop/-------/-----/AR/QCAR/REVU_IOS/FreeImage/lib/ios/freeimage.a(Resize.o-arm64) for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
```
https://github.com/openframeworks/openFrameworks/commit/dcc7debab977dfb136ceb205890a04617c68b621#commitcomment-11791432
# Problem:
- This is caused by a LLVM alignment compatibility issue with older Xcode Versions / LLVM compiler.
## Solution:
- Update Xcode to 6.3.1 or greater
- This is mandatory for iOS AppStore submissions anyway
|
non_build
|
ios ld bit bit ldr str not byte byte aligned the following errors reported in linking process for ios ld bit ldr str not byte aligned from pcrestudy to in pcrestudy from libs poco lib ios pocofoundation a pcre study o for architecture clang error linker command failed with exit code use v to see invocation ld bit ldr str not byte aligned from rkns outputarrayei to in rkns outputarrayei from addons ofxopencv libs opencv lib ios opencv core a arithm cpp o for architecture clang error linker command failed with exit code use v to see invocation ld bit ldr str not byte aligned from rkns outputarrayei to in rkns outputarrayei from addons ofxopencv libs opencv lib ios opencv core a arithm cpp o for architecture clang error linker command failed with exit code use v to see invocation cause this error ld bit ldr str not byte aligned from j to in j from users mahmoudnasr desktop ar qcar revu ios freeimage lib ios freeimage a resize o for architecture clang error linker command failed with exit code use v to see invocation problem this is caused by a llvm alignment compatibility issue with older xcode versions llvm compiler solution update xcode to or greater this is mandatory for ios appstore submissions anyway
| 0
|
93,452
| 26,958,482,124
|
IssuesEvent
|
2023-02-08 16:26:28
|
adoptium/temurin-build
|
https://api.github.com/repos/adoptium/temurin-build
|
opened
|
Add Reproducible Build Comparisons to Jenkins Pipelines
|
enhancement reproducible-build
|
Add the ability in the ci-jenkins-pipelines to support dual build with integrated reproducible build comparison.
Only supported for certain versions and platforms.
Initially jdk(head) platforms:
1. Win64
2. x64Linux
3. MacOS
4.
|
1.0
|
Add Reproducible Build Comparisons to Jenkins Pipelines - Add the ability in the ci-jenkins-pipelines to support dual build with integrated reproducible build comparison.
Only supported for certain versions and platforms.
Initially jdk(head) platforms:
1. Win64
2. x64Linux
3. MacOS
4.
|
build
|
add reproducible build comparisons to jenkins pipelines add the ability in the ci jenkins pipelines to support dual build with integrated reproducible build comparison only supported for certain versions and platforms initially jdk head platforms macos
| 1
|
60,085
| 14,703,098,842
|
IssuesEvent
|
2021-01-04 14:34:54
|
wazuh/wazuh-packages
|
https://api.github.com/repos/wazuh/wazuh-packages
|
closed
|
Fix HP-UX checksum parameter
|
bug build-tools hp-ux
|
Hi team,
The `generate_wazuh_packages.sh` script for HP-UX generates the checksum files with this format:
```
SHA512(wazuh-agent-4.1.0-1-hpux-11v3-ia64.tar)= a1365db32e104a2bec71fb92801476a45dcebbea05de4c85a3f4fcc52ea61df87ec05314d4614aba34965ea0ed81f61fad6a8054fd97e2d32b9f4a5c93130981 wazuh-agent-4.1.0-1-hpux-11v3-ia64.tar
```
meanwhile, the format must be this one:
```
a1365db32e104a2bec71fb92801476a45dcebbea05de4c85a3f4fcc52ea61df87ec05314d4614aba34965ea0ed81f61fad6a8054fd97e2d32b9f4a5c93130981 wazuh-agent-4.1.0-1-hpux-11v3-ia64.tar
|
1.0
|
Fix HP-UX checksum parameter - Hi team,
The `generate_wazuh_packages.sh` script for HP-UX generates the checksum files with this format:
```
SHA512(wazuh-agent-4.1.0-1-hpux-11v3-ia64.tar)= a1365db32e104a2bec71fb92801476a45dcebbea05de4c85a3f4fcc52ea61df87ec05314d4614aba34965ea0ed81f61fad6a8054fd97e2d32b9f4a5c93130981 wazuh-agent-4.1.0-1-hpux-11v3-ia64.tar
```
meanwhile, the format must be this one:
```
a1365db32e104a2bec71fb92801476a45dcebbea05de4c85a3f4fcc52ea61df87ec05314d4614aba34965ea0ed81f61fad6a8054fd97e2d32b9f4a5c93130981 wazuh-agent-4.1.0-1-hpux-11v3-ia64.tar
|
build
|
fix hp ux checksum parameter hi team the generate wazuh packages sh script for hp ux generates the checksum files with this format wazuh agent hpux tar wazuh agent hpux tar meanwhile the format must be this one wazuh agent hpux tar
| 1
|
303,435
| 9,307,084,573
|
IssuesEvent
|
2019-03-25 11:19:50
|
IBM/watson-assistant-workbench
|
https://api.github.com/repos/IBM/watson-assistant-workbench
|
opened
|
Add support for API keys into functions_deploy
|
Priority: medium enhancement
|
Currently, user needs to specify username and password, but he can find only API key on the cloud functions web page (the API key is in fact only the combination of username and password, but someone can be confused).
|
1.0
|
Add support for API keys into functions_deploy - Currently, user needs to specify username and password, but he can find only API key on the cloud functions web page (the API key is in fact only the combination of username and password, but someone can be confused).
|
non_build
|
add support for api keys into functions deploy currently user needs to specify username and password but he can find only api key on the cloud functions web page the api key is in fact only the combination of username and password but someone can be confused
| 0
|
667,222
| 22,422,635,008
|
IssuesEvent
|
2022-06-20 05:57:53
|
itsbasil23/Github-issue-templates
|
https://api.github.com/repos/itsbasil23/Github-issue-templates
|
opened
|
Mobile friendly test
|
Priority 2
|
**Is your feature request related to a problem? Please describe.**
Yes it has to do with the texts of the webpage
**Describe the solution you'd like**
Make the texts a bigger so they can be mobile friendly
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.
|
1.0
|
Mobile friendly test - **Is your feature request related to a problem? Please describe.**
Yes it has to do with the texts of the webpage
**Describe the solution you'd like**
Make the texts a bigger so they can be mobile friendly
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.
|
non_build
|
mobile friendly test is your feature request related to a problem please describe yes it has to do with the texts of the webpage describe the solution you d like make the texts a bigger so they can be mobile friendly describe alternatives you ve considered a clear and concise description of any alternative solutions or features you ve considered additional context add any other context or screenshots about the feature request here
| 0
|
269,561
| 20,387,138,004
|
IssuesEvent
|
2022-02-22 08:19:45
|
aitos-io/BoAT-X-Framework
|
https://api.github.com/repos/aitos-io/BoAT-X-Framework
|
closed
|
BoAT-X Framework for Fibocom L610 Integration Guideline- Broken sentence
|
documentation Severity/minor Priority/P4
|
**Describe the bug**
This guide describes how to integrate BoAT-X Framework source code into L610 OpenCPU SDK, compile BoAT-X Framework static library and build the demo program under Linux environment.
Kindly change expression if applicable:
This article describes how to integrate BoAT-X Framework source code into L610 OpenCPU SDK, compile BoAT-X Framework static library and build the demo program in Linux.
|
1.0
|
BoAT-X Framework for Fibocom L610 Integration Guideline- Broken sentence - **Describe the bug**
This guide describes how to integrate BoAT-X Framework source code into L610 OpenCPU SDK, compile BoAT-X Framework static library and build the demo program under Linux environment.
Kindly change expression if applicable:
This article describes how to integrate BoAT-X Framework source code into L610 OpenCPU SDK, compile BoAT-X Framework static library and build the demo program in Linux.
|
non_build
|
boat x framework for fibocom integration guideline broken sentence describe the bug this guide describes how to integrate boat x framework source code into opencpu sdk compile boat x framework static library and build the demo program under linux environment kindly change expression if applicable this article describes how to integrate boat x framework source code into opencpu sdk compile boat x framework static library and build the demo program in linux
| 0
|
71,624
| 18,798,613,220
|
IssuesEvent
|
2021-11-09 03:01:31
|
doctrine/dbal
|
https://api.github.com/repos/doctrine/dbal
|
closed
|
Delete SQL statement is wrong when using alias MySQL
|
Bug QueryBuilder Stale
|
### Bug Report
Invalid forming delete query when I use alias for table. Query produces a syntax error.
My `MySQL` version is `5.7.25`.
| Q | A
|------------ | ------
| BC Break | no
| Version | 2.12.x
#### Summary
I'm using the delete like described in example `https://github.com/doctrine/dbal/blob/79cba0bc0e653005fc9ab5a23624828a803f41fb/lib/Doctrine/DBAL/Query/QueryBuilder.php#L545`
$qb = $conn->createQueryBuilder()
->delete('users_groups', 'ug')
->where('ug.groupId = :groupId')
->setParameter(':groupId', 1);
This creates a query like this: `DELETE FROM users_groups ug WHERE ug.groupId = 1` that produces an MySQL error
`ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ug WHERE ug.groupId = 1' at line 1`
I do not know if this is a specific MySQL issue or for some MySQL versions, my current MySQL version is 5.7.25.
I've searched MySQL error related answers and i found this https://stackoverflow.com/a/26935749/2624626
delete <alias> from <table> <alias> where <alias>.<field>...
For me `DELETE ug FROM users_groups ug WHERE ug.groupId = 1` worked as expected and without errors.
#### Current behaviour
DELETE FROM <table_name> <alias> WHERE <alias>.<field> ...
#### How to reproduce
`CREATE TABLE test_delete (userId int, groupId int);`
`INSERT INTO test_delete (userId, groupId) VALUES (1,1), (1,2), (1,3), (2,1), (2,3);`
`DELETE FROM test_delete td WHERE td.groupId = 1;`
https://www.db-fiddle.com/f/uPFmoWKGyQngD97AVMBV8Y/1
`DELETE td FROM test_delete td WHERE td.groupId = 1;`
$qb = $conn->createQueryBuilder()
->delete('test_delete', 'td')
->where('td.groupId = :groupId')
->setParameter(':groupId', 1);
$qb->execute();
#### Expected behaviour
DELETE <alias> FROM <table_name> <alias> WHERE <alias>.<field> ...
|
1.0
|
Delete SQL statement is wrong when using alias MySQL - ### Bug Report
Invalid forming delete query when I use alias for table. Query produces a syntax error.
My `MySQL` version is `5.7.25`.
| Q | A
|------------ | ------
| BC Break | no
| Version | 2.12.x
#### Summary
I'm using the delete like described in example `https://github.com/doctrine/dbal/blob/79cba0bc0e653005fc9ab5a23624828a803f41fb/lib/Doctrine/DBAL/Query/QueryBuilder.php#L545`
$qb = $conn->createQueryBuilder()
->delete('users_groups', 'ug')
->where('ug.groupId = :groupId')
->setParameter(':groupId', 1);
This creates a query like this: `DELETE FROM users_groups ug WHERE ug.groupId = 1` that produces an MySQL error
`ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ug WHERE ug.groupId = 1' at line 1`
I do not know if this is a specific MySQL issue or for some MySQL versions, my current MySQL version is 5.7.25.
I've searched MySQL error related answers and i found this https://stackoverflow.com/a/26935749/2624626
delete <alias> from <table> <alias> where <alias>.<field>...
For me `DELETE ug FROM users_groups ug WHERE ug.groupId = 1` worked as expected and without errors.
#### Current behaviour
DELETE FROM <table_name> <alias> WHERE <alias>.<field> ...
#### How to reproduce
`CREATE TABLE test_delete (userId int, groupId int);`
`INSERT INTO test_delete (userId, groupId) VALUES (1,1), (1,2), (1,3), (2,1), (2,3);`
`DELETE FROM test_delete td WHERE td.groupId = 1;`
https://www.db-fiddle.com/f/uPFmoWKGyQngD97AVMBV8Y/1
`DELETE td FROM test_delete td WHERE td.groupId = 1;`
$qb = $conn->createQueryBuilder()
->delete('test_delete', 'td')
->where('td.groupId = :groupId')
->setParameter(':groupId', 1);
$qb->execute();
#### Expected behaviour
DELETE <alias> FROM <table_name> <alias> WHERE <alias>.<field> ...
|
build
|
delete sql statement is wrong when using alias mysql bug report invalid forming delete query when i use alias for table query produces a syntax error my mysql version is q a bc break no version x summary i m using the delete like described in example qb conn createquerybuilder delete users groups ug where ug groupid groupid setparameter groupid this creates a query like this delete from users groups ug where ug groupid that produces an mysql error error you have an error in your sql syntax check the manual that corresponds to your mysql server version for the right syntax to use near ug where ug groupid at line i do not know if this is a specific mysql issue or for some mysql versions my current mysql version is i ve searched mysql error related answers and i found this delete from where for me delete ug from users groups ug where ug groupid worked as expected and without errors current behaviour delete from where how to reproduce create table test delete userid int groupid int insert into test delete userid groupid values delete from test delete td where td groupid delete td from test delete td where td groupid qb conn createquerybuilder delete test delete td where td groupid groupid setparameter groupid qb execute expected behaviour delete from where
| 1
|
51,790
| 12,808,550,456
|
IssuesEvent
|
2020-07-03 13:50:03
|
finos/alloy
|
https://api.github.com/repos/finos/alloy
|
closed
|
Build support for all test permutations
|
Build Readiness
|
Tasks
- [x] @gs-bracej shares test permutations (only environment variables)
- [x] @maoo calculates minutes consumption (see below)
- @maoo applies permutations as build matrix - https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstrategy (will be done when code is contributed)
- [x] @maoo reaches out to LF to understand how they manage GitHub Actions workloads
- [x] @maoo reaches out to github to understand build load and GitHub Actions pricing (we expect a lot of minutes needed to run all permutations /cc @brooklynrob )
## Minutes estimated consumption
The build of Alloy is quite articulated and - based on some estimates extracted from their current infrastructure - the amount of monthly builds sums up to roughly 23.000 minutes (12 hours / day), since there are several build permutations that must be checked at all times.
Following the [GitHub Actions pricing](https://help.github.com/en/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions), we'd end up with a monthly bill of 160$/month , given that 3000 minutes are already included in our free GitHub Org tier.
|
1.0
|
Build support for all test permutations - Tasks
- [x] @gs-bracej shares test permutations (only environment variables)
- [x] @maoo calculates minutes consumption (see below)
- @maoo applies permutations as build matrix - https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstrategy (will be done when code is contributed)
- [x] @maoo reaches out to LF to understand how they manage GitHub Actions workloads
- [x] @maoo reaches out to github to understand build load and GitHub Actions pricing (we expect a lot of minutes needed to run all permutations /cc @brooklynrob )
## Minutes estimated consumption
The build of Alloy is quite articulated and - based on some estimates extracted from their current infrastructure - the amount of monthly builds sums up to roughly 23.000 minutes (12 hours / day), since there are several build permutations that must be checked at all times.
Following the [GitHub Actions pricing](https://help.github.com/en/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions), we'd end up with a monthly bill of 160$/month , given that 3000 minutes are already included in our free GitHub Org tier.
|
build
|
build support for all test permutations tasks gs bracej shares test permutations only environment variables maoo calculates minutes consumption see below maoo applies permutations as build matrix will be done when code is contributed maoo reaches out to lf to understand how they manage github actions workloads maoo reaches out to github to understand build load and github actions pricing we expect a lot of minutes needed to run all permutations cc brooklynrob minutes estimated consumption the build of alloy is quite articulated and based on some estimates extracted from their current infrastructure the amount of monthly builds sums up to roughly minutes hours day since there are several build permutations that must be checked at all times following the we d end up with a monthly bill of month given that minutes are already included in our free github org tier
| 1
|
26,067
| 6,743,345,223
|
IssuesEvent
|
2017-10-20 11:40:27
|
numbbo/coco
|
https://api.github.com/repos/numbbo/coco
|
closed
|
Expose reference worst f-values-of-interest to the solver
|
bbob-biobj Code-Experiments Priority-High Usability
|
in the bi- or multi-objective case (as suggested by @TGlas and others). The candidate would be the Nadir point, also because it defines the switch (from distance to hypervolume) when computing the currently used quality indicator.
Rationales:
- In practical applications it is quite likely to be available and highly useful.
- It might be "unfair" and result in an unwarranted bias to leave the solver completely in the dark about this information.
|
1.0
|
Expose reference worst f-values-of-interest to the solver - in the bi- or multi-objective case (as suggested by @TGlas and others). The candidate would be the Nadir point, also because it defines the switch (from distance to hypervolume) when computing the currently used quality indicator.
Rationales:
- In practical applications it is quite likely to be available and highly useful.
- It might be "unfair" and result in an unwarranted bias to leave the solver completely in the dark about this information.
|
non_build
|
expose reference worst f values of interest to the solver in the bi or multi objective case as suggested by tglas and others the candidate would be the nadir point also because it defines the switch from distance to hypervolume when computing the currently used quality indicator rationales in practical applications it is quite likely to be available and highly useful it might be unfair and result in an unwarranted bias to leave the solver completely in the dark about this information
| 0
|
20,205
| 6,827,503,833
|
IssuesEvent
|
2017-11-08 17:13:43
|
zooniverse/Panoptes-Front-End
|
https://api.github.com/repos/zooniverse/Panoptes-Front-End
|
closed
|
Ability to scale images for site content (not subjects) by percentages
|
feature request project builder
|
I find the scaling utility by pixel hard because you have to exactly know how big the image is. I've had to rescale images by hand in Adobe Illustrator because I can adjust by 50% or 10% and then upload it and see what it looks like on the site and then repeat the process until I get a size I like. I think most project builders will have this issue when making figures for the help and the research pages.
Be able to tell the service you use for thumbnails to do a percentage would help. Currently all that's in the markdown help and what I was told was the pixel scale version where you have to give both dimensions.
|
1.0
|
Ability to scale images for site content (not subjects) by percentages - I find the scaling utility by pixel hard because you have to exactly know how big the image is. I've had to rescale images by hand in Adobe Illustrator because I can adjust by 50% or 10% and then upload it and see what it looks like on the site and then repeat the process until I get a size I like. I think most project builders will have this issue when making figures for the help and the research pages.
Be able to tell the service you use for thumbnails to do a percentage would help. Currently all that's in the markdown help and what I was told was the pixel scale version where you have to give both dimensions.
|
build
|
ability to scale images for site content not subjects by percentages i find the scaling utility by pixel hard because you have to exactly know how big the image is i ve had to rescale images by hand in adobe illustrator because i can adjust by or and then upload it and see what it looks like on the site and then repeat the process until i get a size i like i think most project builders will have this issue when making figures for the help and the research pages be able to tell the service you use for thumbnails to do a percentage would help currently all that s in the markdown help and what i was told was the pixel scale version where you have to give both dimensions
| 1
|
24,968
| 5,114,873,049
|
IssuesEvent
|
2017-01-06 19:55:44
|
atom/notifications
|
https://api.github.com/repos/atom/notifications
|
closed
|
`clear` is not documented
|
documentation
|
I've recently started using the build in notifications in Atom in [my build package](https://atom.io/packages/build). I have some specs which trigger the error message I use. Problem is that they persist between specs. I see that you call `atom.notifications.clear()`. Maybe this should be documented so I can use it safely and find it easily.
|
1.0
|
`clear` is not documented - I've recently started using the build in notifications in Atom in [my build package](https://atom.io/packages/build). I have some specs which trigger the error message I use. Problem is that they persist between specs. I see that you call `atom.notifications.clear()`. Maybe this should be documented so I can use it safely and find it easily.
|
non_build
|
clear is not documented i ve recently started using the build in notifications in atom in i have some specs which trigger the error message i use problem is that they persist between specs i see that you call atom notifications clear maybe this should be documented so i can use it safely and find it easily
| 0
|
44,290
| 2,903,154,237
|
IssuesEvent
|
2015-06-18 11:47:03
|
SteamDatabase/steamSummerMinigame
|
https://api.github.com/repos/SteamDatabase/steamSummerMinigame
|
closed
|
Investigate Critical Damage + Elementals Stack
|
2 - Medium Priority Help Wanted Question
|
A bunch of us in Reddit #2 have seen that increasing elemental damage does not affect critical click damage. If so, elementals are somewhat pointless?
|
1.0
|
Investigate Critical Damage + Elementals Stack - A bunch of us in Reddit #2 have seen that increasing elemental damage does not affect critical click damage. If so, elementals are somewhat pointless?
|
non_build
|
investigate critical damage elementals stack a bunch of us in reddit have seen that increasing elemental damage does not affect critical click damage if so elementals are somewhat pointless
| 0
|
267,690
| 8,391,758,866
|
IssuesEvent
|
2018-10-09 15:44:59
|
colomoto/colomoto-docker-base
|
https://api.github.com/repos/colomoto/colomoto-docker-base
|
closed
|
Spurious dependencies pulled by matplotlib
|
enhancement low priority
|
The matplotlib conda package pulls useless dependencies, namely:
* pyqt (dragging qt)
* tk
* tornado
The pyqt dependency can be responsible for quite some extra weight.
How can we fix this? Create fake packages and put them in the colomoto channel with a specific label (e.g. fake), or in a dedicated channel (e.g., colomoto-shadow)?
|
1.0
|
Spurious dependencies pulled by matplotlib - The matplotlib conda package pulls useless dependencies, namely:
* pyqt (dragging qt)
* tk
* tornado
The pyqt dependency can be responsible for quite some extra weight.
How can we fix this? Create fake packages and put them in the colomoto channel with a specific label (e.g. fake), or in a dedicated channel (e.g., colomoto-shadow)?
|
non_build
|
spurious dependencies pulled by matplotlib the matplotlib conda package pulls useless dependencies namely pyqt dragging qt tk tornado the pyqt dependency can be responsible for quite some extra weight how can we fix this create fake packages and put them in the colomoto channel with a specific label e g fake or in a dedicated channel e g colomoto shadow
| 0
|
74,367
| 20,146,670,267
|
IssuesEvent
|
2022-02-09 08:19:21
|
nanvon/blog-comments
|
https://api.github.com/repos/nanvon/blog-comments
|
opened
|
如何在GitHub上搭建个人网站（github.io） — 南枫的寻宝之旅 · 寻宝之旅，即刻就启程
|
gitment /2021/12/22/how-to-build-github-pages/
|
https://blog.nanvon.cn/2021/12/22/how-to-build-github-pages/
目前，想要搭建自己的博客、个人主页、在线简历、项目演示，大部分同学选择购买云服务器+域名，我也在阿里云购买了云服务器+域名，不过也有同学想要免费的服务，就可以使用 GitHub 提供的免费 Pages服务：github.io。
|
1.0
|
如何在GitHub上搭建个人网站（github.io） — 南枫的寻宝之旅 · 寻宝之旅，即刻就启程 - https://blog.nanvon.cn/2021/12/22/how-to-build-github-pages/
目前，想要搭建自己的博客、个人主页、在线简历、项目演示，大部分同学选择购买云服务器+域名，我也在阿里云购买了云服务器+域名，不过也有同学想要免费的服务，就可以使用 GitHub 提供的免费 Pages服务：github.io。
|
build
|
如何在github上搭建个人网站（github io） — 南枫的寻宝之旅 · 寻宝之旅，即刻就启程 目前，想要搭建自己的博客、个人主页、在线简历、项目演示，大部分同学选择购买云服务器 域名，我也在阿里云购买了云服务器 域名，不过也有同学想要免费的服务，就可以使用 github 提供的免费 pages服务：github io。
| 1
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.