Unnamed: 0
int64 0
832k
| id
float64 2.49B
32.1B
| type
stringclasses 1
value | created_at
stringlengths 19
19
| repo
stringlengths 7
112
| repo_url
stringlengths 36
141
| action
stringclasses 3
values | title
stringlengths 1
744
| labels
stringlengths 4
574
| body
stringlengths 9
211k
| index
stringclasses 10
values | text_combine
stringlengths 96
211k
| label
stringclasses 2
values | text
stringlengths 96
188k
| binary_label
int64 0
1
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
403,508
| 27,421,412,994
|
IssuesEvent
|
2023-03-01 16:58:25
|
ladukwek/ESDP-AP7-ATTRACTOR
|
https://api.github.com/repos/ladukwek/ESDP-AP7-ATTRACTOR
|
closed
|
Инструкция по запуску проекта для заказчика
|
documentation task
|
### Конечный результат:
Описение действий для запуска проекта локально для заказчиков.
### Мотивация:
Инструкция к запуску проекта необходима для того, что бы заказчик мог у себя на компьютере локально запустить проект для просмотра страниц и функционала.
### План решения:
Описать как установить нужные библиотеки, установить виртуальное окружение, сделать миграции, загрузить фикстуры и запустить проект на локальном порту 8000
### Критерии приёма:
- Инструкиция должна быть на русском языке
- Описение должно быть последовательным
- Заказчику должно быть понятно как читать инструцию
### Планируемое время: **2 часов**
|
1.0
|
Инструкция по запуску проекта для заказчика - ### Конечный результат:
Описение действий для запуска проекта локально для заказчиков.
### Мотивация:
Инструкция к запуску проекта необходима для того, что бы заказчик мог у себя на компьютере локально запустить проект для просмотра страниц и функционала.
### План решения:
Описать как установить нужные библиотеки, установить виртуальное окружение, сделать миграции, загрузить фикстуры и запустить проект на локальном порту 8000
### Критерии приёма:
- Инструкиция должна быть на русском языке
- Описение должно быть последовательным
- Заказчику должно быть понятно как читать инструцию
### Планируемое время: **2 часов**
|
non_process
|
инструкция по запуску проекта для заказчика конечный результат описение действий для запуска проекта локально для заказчиков мотивация инструкция к запуску проекта необходима для того что бы заказчик мог у себя на компьютере локально запустить проект для просмотра страниц и функционала план решения описать как установить нужные библиотеки установить виртуальное окружение сделать миграции загрузить фикстуры и запустить проект на локальном порту критерии приёма инструкиция должна быть на русском языке описение должно быть последовательным заказчику должно быть понятно как читать инструцию планируемое время часов
| 0
|
14,245
| 17,173,104,138
|
IssuesEvent
|
2021-07-15 08:03:53
|
qgis/QGIS
|
https://api.github.com/repos/qgis/QGIS
|
closed
|
Temporary raster isn't calculated in Raster calculator
|
Bug Feedback Processing
|
Procedure:
- use of the model graphic builder
- use rasterize algoritm to rasterize a vector line (it's work well)
- gdal raster calculator use the rasterize vector how calculation element, but the result is a NODATA output (it'nt work)
- if use a save rasterize vector line ingdal raster calculator it's work well!
WELL the issue, for me, is that gdal raster calculator doesn't recognized the temporary raster because have a too long filename in temp folder. I GIVE THIS IDEA
I need to use the model graphic builder in may raster model work
I'm sorry if i mistake where post the issue
[prova.txt](https://github.com/qgis/QGIS/files/3743415/prova.txt)
|
1.0
|
Temporary raster isn't calculated in Raster calculator - Procedure:
- use of the model graphic builder
- use rasterize algoritm to rasterize a vector line (it's work well)
- gdal raster calculator use the rasterize vector how calculation element, but the result is a NODATA output (it'nt work)
- if use a save rasterize vector line ingdal raster calculator it's work well!
WELL the issue, for me, is that gdal raster calculator doesn't recognized the temporary raster because have a too long filename in temp folder. I GIVE THIS IDEA
I need to use the model graphic builder in may raster model work
I'm sorry if i mistake where post the issue
[prova.txt](https://github.com/qgis/QGIS/files/3743415/prova.txt)
|
process
|
temporary raster isn t calculated in raster calculator procedure use of the model graphic builder use rasterize algoritm to rasterize a vector line it s work well gdal raster calculator use the rasterize vector how calculation element but the result is a nodata output it nt work if use a save rasterize vector line ingdal raster calculator it s work well well the issue for me is that gdal raster calculator doesn t recognized the temporary raster because have a too long filename in temp folder i give this idea i need to use the model graphic builder in may raster model work i m sorry if i mistake where post the issue
| 1
|
18,724
| 4,308,082,502
|
IssuesEvent
|
2016-07-21 11:35:20
|
mbeddr/mbeddr.core
|
https://api.github.com/repos/mbeddr/mbeddr.core
|
closed
|
rm.exe not part of minGW anymore
|
theme.documentation
|
The minGW installation does not come with rm.exe anymore, which is required by our generated make files. It seems like they shipped the required binary in previous versions, but removed it now.
|
1.0
|
rm.exe not part of minGW anymore - The minGW installation does not come with rm.exe anymore, which is required by our generated make files. It seems like they shipped the required binary in previous versions, but removed it now.
|
non_process
|
rm exe not part of mingw anymore the mingw installation does not come with rm exe anymore which is required by our generated make files it seems like they shipped the required binary in previous versions but removed it now
| 0
|
18,032
| 24,041,175,815
|
IssuesEvent
|
2022-09-16 02:03:50
|
NoHornDragon/NoHornDragon_GameDev
|
https://api.github.com/repos/NoHornDragon/NoHornDragon_GameDev
|
opened
|
[Process] 코딩 컨벤션 정하자!
|
Process
|
내가 생각했을 때 분리해야 하는 건...
네이밍규칙, 괄호 들여쓰기 정도면 될 것 같음
# Common 규칙
* 불필요한 using은 전부 삭제
* 조건문이나 반복문 짧다고 바로 붙여쓰지 말기
* 예시)
```C#
if (true) Console.log("true!");
// Fuck
if (true)
Console.log("true!");
// Good
```
* 사실 한 줄짜리여도 괄호로 분리해야 가독성이 좋다라는 말이 있긴 한데 투머치지 않을까 싶음
* 수식과 수학 연산자(+, -, *, / 등...)은 모두 띄어쓰기
* 행바꿈 두 줄 이상 하지 않기
# 네임스페이스
* namespace NHD.[directory path]
이건 저번 회의때 정했으니까 알것이구
# 네이밍
* 클래스 : 파스칼 표기법(첫 글자는 대문자, 이후는 카멜표기법과 같음)
* 메서드 : 파스칼 표기법
* 클래스 프로퍼티 변수 : 카멜 표기법(첫 글자가 소문자)
* 현재 우리 프로젝트는 프로퍼티 변수와 메서드 변수를 딱히 구분짓는 네이밍을 하지 않는데 회사에서는 언더바를 앞에 붙여서 구분했음. 이거 싹다 바꾸려면 코스트 클텐데 그냥 냅둘까? 고민 중
* 메서드 변수 : 카멜 표기법
* 상수 : 대문자 스네이크 표기법(언더바로 구분하는거)
* 외부 데이터(JSON으로 불러오는 값처럼) : 소문자 스네이크 표기법
읽어보고 수정하고 싶거나 이거 현실적으로 힘들 것 같다! 싶으면 댓글 달아주셈
|
1.0
|
[Process] 코딩 컨벤션 정하자! - 내가 생각했을 때 분리해야 하는 건...
네이밍규칙, 괄호 들여쓰기 정도면 될 것 같음
# Common 규칙
* 불필요한 using은 전부 삭제
* 조건문이나 반복문 짧다고 바로 붙여쓰지 말기
* 예시)
```C#
if (true) Console.log("true!");
// Fuck
if (true)
Console.log("true!");
// Good
```
* 사실 한 줄짜리여도 괄호로 분리해야 가독성이 좋다라는 말이 있긴 한데 투머치지 않을까 싶음
* 수식과 수학 연산자(+, -, *, / 등...)은 모두 띄어쓰기
* 행바꿈 두 줄 이상 하지 않기
# 네임스페이스
* namespace NHD.[directory path]
이건 저번 회의때 정했으니까 알것이구
# 네이밍
* 클래스 : 파스칼 표기법(첫 글자는 대문자, 이후는 카멜표기법과 같음)
* 메서드 : 파스칼 표기법
* 클래스 프로퍼티 변수 : 카멜 표기법(첫 글자가 소문자)
* 현재 우리 프로젝트는 프로퍼티 변수와 메서드 변수를 딱히 구분짓는 네이밍을 하지 않는데 회사에서는 언더바를 앞에 붙여서 구분했음. 이거 싹다 바꾸려면 코스트 클텐데 그냥 냅둘까? 고민 중
* 메서드 변수 : 카멜 표기법
* 상수 : 대문자 스네이크 표기법(언더바로 구분하는거)
* 외부 데이터(JSON으로 불러오는 값처럼) : 소문자 스네이크 표기법
읽어보고 수정하고 싶거나 이거 현실적으로 힘들 것 같다! 싶으면 댓글 달아주셈
|
process
|
코딩 컨벤션 정하자 내가 생각했을 때 분리해야 하는 건 네이밍규칙 괄호 들여쓰기 정도면 될 것 같음 common 규칙 불필요한 using은 전부 삭제 조건문이나 반복문 짧다고 바로 붙여쓰지 말기 예시 c if true console log true fuck if true console log true good 사실 한 줄짜리여도 괄호로 분리해야 가독성이 좋다라는 말이 있긴 한데 투머치지 않을까 싶음 수식과 수학 연산자 등 은 모두 띄어쓰기 행바꿈 두 줄 이상 하지 않기 네임스페이스 namespace nhd 이건 저번 회의때 정했으니까 알것이구 네이밍 클래스 파스칼 표기법 첫 글자는 대문자 이후는 카멜표기법과 같음 메서드 파스칼 표기법 클래스 프로퍼티 변수 카멜 표기법 첫 글자가 소문자 현재 우리 프로젝트는 프로퍼티 변수와 메서드 변수를 딱히 구분짓는 네이밍을 하지 않는데 회사에서는 언더바를 앞에 붙여서 구분했음 이거 싹다 바꾸려면 코스트 클텐데 그냥 냅둘까 고민 중 메서드 변수 카멜 표기법 상수 대문자 스네이크 표기법 언더바로 구분하는거 외부 데이터 json으로 불러오는 값처럼 소문자 스네이크 표기법 읽어보고 수정하고 싶거나 이거 현실적으로 힘들 것 같다 싶으면 댓글 달아주셈
| 1
|
11,052
| 13,888,390,236
|
IssuesEvent
|
2020-10-19 06:12:52
|
didi/mpx
|
https://api.github.com/repos/didi/mpx
|
closed
|
[Bug report] theme.json 无法被正确处理
|
processing
|
**问题描述**
根据微信官方文档，theme.json 用来适配 dark mode，我在开发过程中发现的问题如下：
1. src/theme.json 不会被正确输出到 dist/theme.json
2. theme.json 中的键值对： "iconPath1": "static/icon1.png" 不会被正确替换成 "iconPath1": "img/icon1[hash].png"
**环境信息描述**
1. macOS 10.15.6
2. "@mpxjs/core": "^2.5.11", "@mpxjs/webpack-plugin": "2.5.33", "@mpxjs/api-proxy": "^2.5.10"
**最简复现demo**
如需 demo 请回复
|
1.0
|
[Bug report] theme.json 无法被正确处理 - **问题描述**
根据微信官方文档，theme.json 用来适配 dark mode，我在开发过程中发现的问题如下：
1. src/theme.json 不会被正确输出到 dist/theme.json
2. theme.json 中的键值对： "iconPath1": "static/icon1.png" 不会被正确替换成 "iconPath1": "img/icon1[hash].png"
**环境信息描述**
1. macOS 10.15.6
2. "@mpxjs/core": "^2.5.11", "@mpxjs/webpack-plugin": "2.5.33", "@mpxjs/api-proxy": "^2.5.10"
**最简复现demo**
如需 demo 请回复
|
process
|
theme json 无法被正确处理 问题描述 根据微信官方文档，theme json 用来适配 dark mode，我在开发过程中发现的问题如下： src theme json 不会被正确输出到 dist theme json theme json 中的键值对： static png 不会被正确替换成 img png 环境信息描述 macos mpxjs core mpxjs webpack plugin mpxjs api proxy 最简复现demo 如需 demo 请回复
| 1
|
2,149
| 4,998,287,472
|
IssuesEvent
|
2016-12-09 19:22:50
|
davidfestal/ceylon-gwt
|
https://api.github.com/repos/davidfestal/ceylon-gwt
|
opened
|
Transform let expressions
|
enhancement m_processor m_runtime
|
The `LetExpr` of the Javac AST has not equivalent source code. We should produce equivalent but valid Java source code.
The idea is to use an anonymous class that implements a specific interface provided by the `ceylon.interop.gwt.runtime` module.
|
1.0
|
Transform let expressions - The `LetExpr` of the Javac AST has not equivalent source code. We should produce equivalent but valid Java source code.
The idea is to use an anonymous class that implements a specific interface provided by the `ceylon.interop.gwt.runtime` module.
|
process
|
transform let expressions the letexpr of the javac ast has not equivalent source code we should produce equivalent but valid java source code the idea is to use an anonymous class that implements a specific interface provided by the ceylon interop gwt runtime module
| 1
|
98,797
| 4,031,383,126
|
IssuesEvent
|
2016-05-18 16:59:15
|
siteorigin/vantage
|
https://api.github.com/repos/siteorigin/vantage
|
opened
|
Posts page: Post titles aren't outputting
|
bug priority-1
|
The blog page isn't displaying post titles. Post titles are however displaying in category archive pages. The blog page issue applies both "Front page displays: Your latest posts" and to a defined posts page.
|
1.0
|
Posts page: Post titles aren't outputting - The blog page isn't displaying post titles. Post titles are however displaying in category archive pages. The blog page issue applies both "Front page displays: Your latest posts" and to a defined posts page.
|
non_process
|
posts page post titles aren t outputting the blog page isn t displaying post titles post titles are however displaying in category archive pages the blog page issue applies both front page displays your latest posts and to a defined posts page
| 0
|
275,910
| 20,961,108,280
|
IssuesEvent
|
2022-03-27 20:15:30
|
wolve265/BluetoothCar
|
https://api.github.com/repos/wolve265/BluetoothCar
|
closed
|
Przygotować prosty test modułu L298N
|
documentation enhancement
|
Należy przygotować prosty test modułu L298N aby:
- zaznajomić się z jego bibliotekami
- sprawdzić działanie modułu
- dowiedzieć się jak podłączyć moduł do płytki Arduino Uno
Zadania:
- [x] utworzyć katalog **src/L298N** @wolve265
- [x] znaleźć odpowiednią bibliotekę i dowiedzieć się jak jej używać lub napisać własną @wolve265
- [x] dodać bibliotekę do projektu @wolve265
- [x] napisać test **TestOfL298N** i umieścić go w katalogu **tests** @wolve265
- [x] przeprowadzić test na sprzęcie @wolve265
|
1.0
|
Przygotować prosty test modułu L298N - Należy przygotować prosty test modułu L298N aby:
- zaznajomić się z jego bibliotekami
- sprawdzić działanie modułu
- dowiedzieć się jak podłączyć moduł do płytki Arduino Uno
Zadania:
- [x] utworzyć katalog **src/L298N** @wolve265
- [x] znaleźć odpowiednią bibliotekę i dowiedzieć się jak jej używać lub napisać własną @wolve265
- [x] dodać bibliotekę do projektu @wolve265
- [x] napisać test **TestOfL298N** i umieścić go w katalogu **tests** @wolve265
- [x] przeprowadzić test na sprzęcie @wolve265
|
non_process
|
przygotować prosty test modułu należy przygotować prosty test modułu aby zaznajomić się z jego bibliotekami sprawdzić działanie modułu dowiedzieć się jak podłączyć moduł do płytki arduino uno zadania utworzyć katalog src znaleźć odpowiednią bibliotekę i dowiedzieć się jak jej używać lub napisać własną dodać bibliotekę do projektu napisać test i umieścić go w katalogu tests przeprowadzić test na sprzęcie
| 0
|
2,022
| 4,846,796,734
|
IssuesEvent
|
2016-11-10 13:03:31
|
Alfresco/alfresco-ng2-components
|
https://api.github.com/repos/Alfresco/alfresco-ng2-components
|
opened
|
'Running' filter is not refreshed with newly created process
|
browser: all bug comp: activiti-processList
|
1. Create a new process (using start process option)
2. Notice 'Running' filter is not updated with newly created process
3. Navigate away and back to same page and process is displayed
|
1.0
|
'Running' filter is not refreshed with newly created process - 1. Create a new process (using start process option)
2. Notice 'Running' filter is not updated with newly created process
3. Navigate away and back to same page and process is displayed
|
process
|
running filter is not refreshed with newly created process create a new process using start process option notice running filter is not updated with newly created process navigate away and back to same page and process is displayed
| 1
|
87,483
| 25,133,234,898
|
IssuesEvent
|
2022-11-09 16:34:38
|
dotnet/arcade
|
https://api.github.com/repos/dotnet/arcade
|
closed
|
Build failed: arcade-services-internal-ci/main #20221107.4
|
Build Failed
|
Build [#20221107.4](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_build/results?buildId=2039486) failed
## :x: : internal / arcade-services-internal-ci failed
### Summary
**Finished** - Tue, 08 Nov 2022 06:28:42 GMT
**Duration** - 220 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/2039486/logs/302) - The job running on agent NetCore1ESPool-Internal 58 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/2039486/logs/276) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/276) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/276) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/277) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/277) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/277) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/278) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/278) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/278) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/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/2039486/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/2039486/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
- :x: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/299) - The operation was canceled.
#### Validate Build Assets
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/logs/117) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/117) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/117) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/logs/125) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/125) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/125) - Resource file has already set to: 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/2039486/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/2039486/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/2039486/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/2039486/logs/187) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/187) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/187) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/215) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/215) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/215) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/217) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/217) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/217) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/210) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/210) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/210) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/211) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/211) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/211) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/195) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/195) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/195) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/196) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/196) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/196) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/239) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/239) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/239) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/240) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/240) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/240) - Resource file has already set to: 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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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
#### Publish using Darc
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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
#### Build
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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
### Changes
- [df782231](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/df782231ec2f67c07a356cff361bc9225e306de1) - Matt Galbraith - Fix Autoscale out alert (#2095)
- [2cf06cce](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/2cf06ccedbcb3b01d914df4d83d5224f24c9e150) - Chad Nedzlek - Share OTP code, since it's used in 2 places in helix (#2096)
- [09c0d1e4](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/09c0d1e48621eb3b85257ec0c3af9814c33665a1) - Přemek Vysoký - Create a dedicated branch for VMR initialization commits (#2094)
- [5331e8e9](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/5331e8e9fb5308aa0e555533ff9eea1334bc65b8) - Přemek Vysoký - Fix recursive detection of dependencies in VMR synchronization (#2093)
- [aa6e835e](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/aa6e835ea5e8ef70a95a8fa6075fdf4c73de8bd8) - Jon Fortescue - Ignore AzDO workitems, add better logging (#2092)
- [486c964b](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/486c964bde71e663d00f5509517cbf5447d789d3) - Jon Fortescue - Add linked issue/release notes check (#2087)
- [6c22515c](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/6c22515c07422dbbc81d8c0f380c5585203597fb) - Milena Hristova - Fix VMR synchronization when pulling empty commits (#2090)
- [7a093e86](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/7a093e86507405b990f0e6aa5c634c9a5585319f) - Přemek Vysoký - Initialize VMR even without `README`/`THIRD-PARTY-NOTICES` files (#2089)
- [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
|
1.0
|
Build failed: arcade-services-internal-ci/main #20221107.4 - Build [#20221107.4](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_build/results?buildId=2039486) failed
## :x: : internal / arcade-services-internal-ci failed
### Summary
**Finished** - Tue, 08 Nov 2022 06:28:42 GMT
**Duration** - 220 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/2039486/logs/302) - The job running on agent NetCore1ESPool-Internal 58 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/2039486/logs/276) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/276) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/276) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/277) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/277) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/277) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/278) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/278) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/278) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/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/2039486/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/2039486/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
- :x: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/299) - The operation was canceled.
#### Validate Build Assets
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/logs/117) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/117) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/117) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/logs/125) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/125) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/125) - Resource file has already set to: 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/2039486/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/2039486/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/2039486/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/2039486/logs/187) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/187) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/187) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/215) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/215) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/215) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/217) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/217) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/217) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/210) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/210) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/210) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/211) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/211) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/211) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/195) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/195) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/195) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/196) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/196) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/196) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/239) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/239) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/239) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/240) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/240) - Resource file has already set to: D:\a\_work\_tasks\AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e\1.212.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/logs/240) - Resource file has already set to: 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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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
#### Publish using Darc
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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
#### Build
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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/2039486/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
### Changes
- [df782231](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/df782231ec2f67c07a356cff361bc9225e306de1) - Matt Galbraith - Fix Autoscale out alert (#2095)
- [2cf06cce](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/2cf06ccedbcb3b01d914df4d83d5224f24c9e150) - Chad Nedzlek - Share OTP code, since it's used in 2 places in helix (#2096)
- [09c0d1e4](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/09c0d1e48621eb3b85257ec0c3af9814c33665a1) - Přemek Vysoký - Create a dedicated branch for VMR initialization commits (#2094)
- [5331e8e9](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/5331e8e9fb5308aa0e555533ff9eea1334bc65b8) - Přemek Vysoký - Fix recursive detection of dependencies in VMR synchronization (#2093)
- [aa6e835e](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/aa6e835ea5e8ef70a95a8fa6075fdf4c73de8bd8) - Jon Fortescue - Ignore AzDO workitems, add better logging (#2092)
- [486c964b](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/486c964bde71e663d00f5509517cbf5447d789d3) - Jon Fortescue - Add linked issue/release notes check (#2087)
- [6c22515c](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/6c22515c07422dbbc81d8c0f380c5585203597fb) - Milena Hristova - Fix VMR synchronization when pulling empty commits (#2090)
- [7a093e86](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_git/ec29e881-6ad7-4427-832d-ce639ccba518/commit/7a093e86507405b990f0e6aa5c634c9a5585319f) - Přemek Vysoký - Initialize VMR even without `README`/`THIRD-PARTY-NOTICES` files (#2089)
- [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
|
non_process
|
build failed arcade services internal ci main build failed x internal arcade services internal ci failed summary finished tue 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 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 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 changes matt galbraith fix autoscale out alert chad nedzlek share otp code since it s used in places in helix přemek vysoký create a dedicated branch for vmr initialization commits přemek vysoký fix recursive detection of dependencies in vmr synchronization jon fortescue ignore azdo workitems add better logging jon fortescue add linked issue release notes check milena hristova fix vmr synchronization when pulling empty commits přemek vysoký initialize vmr even without readme third party notices files přemek vysoký keep tarball content and vmr s root synchronized always chad nedzlek expose console in for some command line apps
| 0
|
191,635
| 6,835,704,782
|
IssuesEvent
|
2017-11-10 02:46:22
|
phetsims/energy-skate-park-basics
|
https://api.github.com/repos/phetsims/energy-skate-park-basics
|
closed
|
Cannot reshape tracks
|
priority:2-high
|
Detected during https://github.com/phetsims/phet-io/issues/1239 it is no longer possible to reshape tracks. Dragging by the control point just translates the entire track. Not sure when this problem was introduced.
|
1.0
|
Cannot reshape tracks - Detected during https://github.com/phetsims/phet-io/issues/1239 it is no longer possible to reshape tracks. Dragging by the control point just translates the entire track. Not sure when this problem was introduced.
|
non_process
|
cannot reshape tracks detected during it is no longer possible to reshape tracks dragging by the control point just translates the entire track not sure when this problem was introduced
| 0
|
13,929
| 16,685,412,741
|
IssuesEvent
|
2021-06-08 07:31:24
|
bisq-network/bisq
|
https://api.github.com/repos/bisq-network/bisq
|
closed
|
BSQ trading fee calculated incorrectly
|
in:dao in:trade-process
|
Some offers pay an incorrect BSQ fee.
Here is an example of the discrepancies from today's offer book. Some have underpaid, others have overpaid.
The fee rate is chosen based on the block height at the time the offer is created. For example, an offer created at block height 673810 would use the fee rate of 7.53 BSQ per bitcoin.
A small but significant subset of offers have not chosen the correct fee rate. How can this happen?
Looking at the highlighted onion addresses, it seems that when a node chooses an incorrect rate, it is consistent in choosing the same incorrect fee rate for subsequent offers.
Attn: @chimp1984 @ripcurlx
[feeDiscrepancies_20210318.xlsx](https://github.com/bisq-network/bisq/files/6166243/feeDiscrepancies_20210318.xlsx) [TxFeeRawData_20210318.txt](https://github.com/bisq-network/bisq/files/6166278/TxFeeRawData_20210318.txt)
|
1.0
|
BSQ trading fee calculated incorrectly - Some offers pay an incorrect BSQ fee.
Here is an example of the discrepancies from today's offer book. Some have underpaid, others have overpaid.
The fee rate is chosen based on the block height at the time the offer is created. For example, an offer created at block height 673810 would use the fee rate of 7.53 BSQ per bitcoin.
A small but significant subset of offers have not chosen the correct fee rate. How can this happen?
Looking at the highlighted onion addresses, it seems that when a node chooses an incorrect rate, it is consistent in choosing the same incorrect fee rate for subsequent offers.
Attn: @chimp1984 @ripcurlx
[feeDiscrepancies_20210318.xlsx](https://github.com/bisq-network/bisq/files/6166243/feeDiscrepancies_20210318.xlsx) [TxFeeRawData_20210318.txt](https://github.com/bisq-network/bisq/files/6166278/TxFeeRawData_20210318.txt)
|
process
|
bsq trading fee calculated incorrectly some offers pay an incorrect bsq fee here is an example of the discrepancies from today s offer book some have underpaid others have overpaid the fee rate is chosen based on the block height at the time the offer is created for example an offer created at block height would use the fee rate of bsq per bitcoin a small but significant subset of offers have not chosen the correct fee rate how can this happen looking at the highlighted onion addresses it seems that when a node chooses an incorrect rate it is consistent in choosing the same incorrect fee rate for subsequent offers attn ripcurlx
| 1
|
7,826
| 11,007,411,253
|
IssuesEvent
|
2019-12-04 08:26:08
|
geneontology/go-ontology
|
https://api.github.com/repos/geneontology/go-ontology
|
closed
|
rename remaining "evasion or tolerence terms"
|
Other term-related request multi-species process quick fix
|
GO:0030682 evasion or tolerance of host defenses
GO:0020012 evasion or tolerance of host immune response
-> mitigation of blah
|
1.0
|
rename remaining "evasion or tolerence terms" -
GO:0030682 evasion or tolerance of host defenses
GO:0020012 evasion or tolerance of host immune response
-> mitigation of blah
|
process
|
rename remaining evasion or tolerence terms go evasion or tolerance of host defenses go evasion or tolerance of host immune response mitigation of blah
| 1
|
317,235
| 27,221,291,307
|
IssuesEvent
|
2023-02-21 05:41:54
|
meckleunn/unnamed
|
https://api.github.com/repos/meckleunn/unnamed
|
closed
|
add forums for divisions into one category for SC
|
Test :100: Awaiting Approval :sos:
|
- Star Citizen Divisions
- > Division 1
- > 2 etc
|
1.0
|
add forums for divisions into one category for SC - - Star Citizen Divisions
- > Division 1
- > 2 etc
|
non_process
|
add forums for divisions into one category for sc star citizen divisions division etc
| 0
|
718,149
| 24,705,814,187
|
IssuesEvent
|
2022-10-19 18:58:06
|
kubernetes/kubernetes
|
https://api.github.com/repos/kubernetes/kubernetes
|
closed
|
E2eNode Suite: [sig-node] MirrorPod ... test is flaking on deletion of mirror pod
|
priority/important-soon sig/node kind/flake lifecycle/rotten triage/accepted
|
### Which jobs are flaking?
prowjob_name: ci-kubernetes-node-kubelet-kubetest2-1-23
prowjob_config_url: https://git.k8s.io/test-infra/config/jobs/kubernetes/sig-release/release-branch-jobs/1.23.yaml
The test failure is related to static-pods, and the deletion of the associated mirror-pod when the static pod is removed.
### Which tests are flaking?
E2eNode Suite: [sig-node] MirrorPod when create a mirror pod without changes should successfully recreate when file is removed and recreated [NodeConformance]
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-node-kubelet-kubetest2-1-23/1525946672201338880
### Since when has it been flaking?
flaking since:
5/12/2022:
first failure:
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-node-kubelet-kubetest2-1-23/1524676333974589440
job history listing:
https://prow.k8s.io/job-history/gs/kubernetes-jenkins/logs/ci-kubernetes-node-kubelet-kubetest2-1-23?buildId=1525039116524195840
### Testgrid link
https://testgrid.k8s.io/sig-release-job-config-errors#node-kubelet-1.23-kubetest2
### Reason for failure (if possible)
The test failure is related to static-pods, and the **deletion of the associated mirror-pod when the static pod is removed.**
#### preliminary analysis:
- **success case** [clearly shows a DELETE call](https://storage.googleapis.com/kubernetes-jenkins/logs/ci-kubernetes-node-kubelet-kubetest2-1-23/1525069315961786368/artifacts/60aead4b-d2ac-11ec-b40b-862e9d6d5e5e/test-cos-89-16108-659-8/services.log):
```
I0513 11:20:17.108284 2009 httplog.go:129] "HTTP" verb="DELETE" URI="/api/v1/namespaces/mirror-pod-225/pods/static-pod-e5a41e8d-ed47-4fac-b2bf-824f0fcb4972-test-cos-89-16108-659-8" latency="3.91334ms" userAgent="kubelet/v1.23.7 (linux/amd64) kubernetes/21cde7d" audit-ID="31a5a235-55d3-41ec-a675-9fb03b0b6976" srcIP="127.0.0.1:50180" apf_pl="exempt" apf_fs="exempt" resp=200
```
- **fail case** def no DELETE call in [apiserver logs](https://storage.googleapis.com/kubernetes-jenkins/logs/ci-kubernetes-node-kubelet-kubetest2-1-23/1525946672201338880/artifacts/68802832-d493-11ec-b161-3e13eb6fa348/test-cos-89-16108-659-8/services.log)
### Anything else we need to know?
_No response_
### Relevant SIG(s)
/sig-release
|
1.0
|
E2eNode Suite: [sig-node] MirrorPod ... test is flaking on deletion of mirror pod - ### Which jobs are flaking?
prowjob_name: ci-kubernetes-node-kubelet-kubetest2-1-23
prowjob_config_url: https://git.k8s.io/test-infra/config/jobs/kubernetes/sig-release/release-branch-jobs/1.23.yaml
The test failure is related to static-pods, and the deletion of the associated mirror-pod when the static pod is removed.
### Which tests are flaking?
E2eNode Suite: [sig-node] MirrorPod when create a mirror pod without changes should successfully recreate when file is removed and recreated [NodeConformance]
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-node-kubelet-kubetest2-1-23/1525946672201338880
### Since when has it been flaking?
flaking since:
5/12/2022:
first failure:
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-node-kubelet-kubetest2-1-23/1524676333974589440
job history listing:
https://prow.k8s.io/job-history/gs/kubernetes-jenkins/logs/ci-kubernetes-node-kubelet-kubetest2-1-23?buildId=1525039116524195840
### Testgrid link
https://testgrid.k8s.io/sig-release-job-config-errors#node-kubelet-1.23-kubetest2
### Reason for failure (if possible)
The test failure is related to static-pods, and the **deletion of the associated mirror-pod when the static pod is removed.**
#### preliminary analysis:
- **success case** [clearly shows a DELETE call](https://storage.googleapis.com/kubernetes-jenkins/logs/ci-kubernetes-node-kubelet-kubetest2-1-23/1525069315961786368/artifacts/60aead4b-d2ac-11ec-b40b-862e9d6d5e5e/test-cos-89-16108-659-8/services.log):
```
I0513 11:20:17.108284 2009 httplog.go:129] "HTTP" verb="DELETE" URI="/api/v1/namespaces/mirror-pod-225/pods/static-pod-e5a41e8d-ed47-4fac-b2bf-824f0fcb4972-test-cos-89-16108-659-8" latency="3.91334ms" userAgent="kubelet/v1.23.7 (linux/amd64) kubernetes/21cde7d" audit-ID="31a5a235-55d3-41ec-a675-9fb03b0b6976" srcIP="127.0.0.1:50180" apf_pl="exempt" apf_fs="exempt" resp=200
```
- **fail case** def no DELETE call in [apiserver logs](https://storage.googleapis.com/kubernetes-jenkins/logs/ci-kubernetes-node-kubelet-kubetest2-1-23/1525946672201338880/artifacts/68802832-d493-11ec-b161-3e13eb6fa348/test-cos-89-16108-659-8/services.log)
### Anything else we need to know?
_No response_
### Relevant SIG(s)
/sig-release
|
non_process
|
suite mirrorpod test is flaking on deletion of mirror pod which jobs are flaking prowjob name ci kubernetes node kubelet prowjob config url the test failure is related to static pods and the deletion of the associated mirror pod when the static pod is removed which tests are flaking suite mirrorpod when create a mirror pod without changes should successfully recreate when file is removed and recreated since when has it been flaking flaking since first failure job history listing testgrid link reason for failure if possible the test failure is related to static pods and the deletion of the associated mirror pod when the static pod is removed preliminary analysis success case httplog go http verb delete uri api namespaces mirror pod pods static pod test cos latency useragent kubelet linux kubernetes audit id srcip apf pl exempt apf fs exempt resp fail case def no delete call in anything else we need to know no response relevant sig s sig release
| 0
|
11,868
| 14,667,898,931
|
IssuesEvent
|
2020-12-29 19:49:24
|
modi-w/AutoVersionsDB
|
https://api.github.com/repos/modi-w/AutoVersionsDB
|
opened
|
The progress percentage show above 100% when restore step executed
|
area-Core area-UI good first issue process-ready-for-implementation type-bug up-for-grab
|
**Describe the bug**
When we run sync and we had an error during the process, the restore step should be executed.
Sometimes, in the above situation, the progress percentage show above 100%.
**To Reproduce**
Steps to reproduce the behavior:
1. Create a script error in one of the last script file.
2. Run "Sync" or "Recreate"
3. After the process completed, open the log process window and look at the last notifications.
|
1.0
|
The progress percentage show above 100% when restore step executed - **Describe the bug**
When we run sync and we had an error during the process, the restore step should be executed.
Sometimes, in the above situation, the progress percentage show above 100%.
**To Reproduce**
Steps to reproduce the behavior:
1. Create a script error in one of the last script file.
2. Run "Sync" or "Recreate"
3. After the process completed, open the log process window and look at the last notifications.
|
process
|
the progress percentage show above when restore step executed describe the bug when we run sync and we had an error during the process the restore step should be executed sometimes in the above situation the progress percentage show above to reproduce steps to reproduce the behavior create a script error in one of the last script file run sync or recreate after the process completed open the log process window and look at the last notifications
| 1
|
57,773
| 8,206,139,381
|
IssuesEvent
|
2018-09-03 12:33:37
|
ReactiveX/RxJava
|
https://api.github.com/repos/ReactiveX/RxJava
|
closed
|
Add an "Error handling" JavaDocs section to fromCallable & co
|
2.x Documentation PR welcome good first issue
|
The operators of `fromCallable`, `fromAction` and `fromRunnable` in the reactive classes could use an `<dt><b>Error handling:</b></dt>` section in the JavaDocs describing the regular and canceled/disposed behavior.
> If the `{@link Callable/Action/Runnable}` throws an exception/exception/unchecked exception, the respective `{@link Throwable}` is delivered to the downstream via `{@link Subscriber/Observer/.../#onError()}`, except when the downstream has canceled/disposed this `{@code Flowable/Observable/Single/Maybe/Completable}` source. In this latter case, the Throwable is delivered to the global error handler via `{@link RxJavaPlugins#onError(Throwable)}` as `{@link io.reactivex.exceptions.UndeliverableException UndeliverableException}`.
|
1.0
|
Add an "Error handling" JavaDocs section to fromCallable & co - The operators of `fromCallable`, `fromAction` and `fromRunnable` in the reactive classes could use an `<dt><b>Error handling:</b></dt>` section in the JavaDocs describing the regular and canceled/disposed behavior.
> If the `{@link Callable/Action/Runnable}` throws an exception/exception/unchecked exception, the respective `{@link Throwable}` is delivered to the downstream via `{@link Subscriber/Observer/.../#onError()}`, except when the downstream has canceled/disposed this `{@code Flowable/Observable/Single/Maybe/Completable}` source. In this latter case, the Throwable is delivered to the global error handler via `{@link RxJavaPlugins#onError(Throwable)}` as `{@link io.reactivex.exceptions.UndeliverableException UndeliverableException}`.
|
non_process
|
add an error handling javadocs section to fromcallable co the operators of fromcallable fromaction and fromrunnable in the reactive classes could use an error handling section in the javadocs describing the regular and canceled disposed behavior if the link callable action runnable throws an exception exception unchecked exception the respective link throwable is delivered to the downstream via link subscriber observer onerror except when the downstream has canceled disposed this code flowable observable single maybe completable source in this latter case the throwable is delivered to the global error handler via link rxjavaplugins onerror throwable as link io reactivex exceptions undeliverableexception undeliverableexception
| 0
|
75,740
| 15,443,676,431
|
IssuesEvent
|
2021-03-08 09:26:14
|
AlexRogalskiy/code-formats
|
https://api.github.com/repos/AlexRogalskiy/code-formats
|
opened
|
CVE-2020-7598 (Medium) detected in minimist-0.0.8.tgz
|
security vulnerability
|
## CVE-2020-7598 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>minimist-0.0.8.tgz</b></p></summary>
<p>parse argument options</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz">https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz</a></p>
<p>Path to dependency file: code-formats/package.json</p>
<p>Path to vulnerable library: code-formats/node_modules/lambdafs/node_modules/minimist/package.json</p>
<p>
Dependency Hierarchy:
- chrome-aws-lambda-3.1.1.tgz (Root Library)
- lambdafs-1.3.0.tgz
- tar-fs-2.0.0.tgz
- mkdirp-0.5.1.tgz
- :x: **minimist-0.0.8.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/code-formats/commit/7eca41b801772a2cc094668bbb3aa09b72455180">7eca41b801772a2cc094668bbb3aa09b72455180</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
minimist before 1.2.2 could be tricked into adding or modifying properties of Object.prototype using a "constructor" or "__proto__" payload.
<p>Publish Date: 2020-03-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7598>CVE-2020-7598</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/substack/minimist/commit/63e7ed05aa4b1889ec2f3b196426db4500cbda94">https://github.com/substack/minimist/commit/63e7ed05aa4b1889ec2f3b196426db4500cbda94</a></p>
<p>Release Date: 2020-03-11</p>
<p>Fix Resolution: minimist - 0.2.1,1.2.3</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-7598 (Medium) detected in minimist-0.0.8.tgz - ## CVE-2020-7598 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>minimist-0.0.8.tgz</b></p></summary>
<p>parse argument options</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz">https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz</a></p>
<p>Path to dependency file: code-formats/package.json</p>
<p>Path to vulnerable library: code-formats/node_modules/lambdafs/node_modules/minimist/package.json</p>
<p>
Dependency Hierarchy:
- chrome-aws-lambda-3.1.1.tgz (Root Library)
- lambdafs-1.3.0.tgz
- tar-fs-2.0.0.tgz
- mkdirp-0.5.1.tgz
- :x: **minimist-0.0.8.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/code-formats/commit/7eca41b801772a2cc094668bbb3aa09b72455180">7eca41b801772a2cc094668bbb3aa09b72455180</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
minimist before 1.2.2 could be tricked into adding or modifying properties of Object.prototype using a "constructor" or "__proto__" payload.
<p>Publish Date: 2020-03-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7598>CVE-2020-7598</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/substack/minimist/commit/63e7ed05aa4b1889ec2f3b196426db4500cbda94">https://github.com/substack/minimist/commit/63e7ed05aa4b1889ec2f3b196426db4500cbda94</a></p>
<p>Release Date: 2020-03-11</p>
<p>Fix Resolution: minimist - 0.2.1,1.2.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_process
|
cve medium detected in minimist tgz cve medium severity vulnerability vulnerable library minimist tgz parse argument options library home page a href path to dependency file code formats package json path to vulnerable library code formats node modules lambdafs node modules minimist package json dependency hierarchy chrome aws lambda tgz root library lambdafs tgz tar fs tgz mkdirp tgz x minimist tgz vulnerable library found in head commit a href vulnerability details minimist before could be tricked into adding or modifying properties of object prototype using a constructor or proto payload publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact low availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution minimist step up your open source security game with whitesource
| 0
|
428,118
| 29,928,648,269
|
IssuesEvent
|
2023-06-22 07:54:28
|
Azure/Industrial-IoT
|
https://api.github.com/repos/Azure/Industrial-IoT
|
closed
|
We need better documentation for --strict mode in OPC Publisher, we need better documentation for all other message profiles.
|
documentation OPC Publisher
|
> "Type": "ByteString",
I will address the docs. There will be a --strict version of the docs, and backcompat version (this one).
---
In reply to: [1385126686](https://github.com/Azure/Industrial-IoT/pull/1928#issuecomment-1385126686) [](http://example.com/codeflow?ancestors=1385126686,1385126686)
---
Refers to: docs/modules/telemetry-events-format.md:229 in ed3aaf4. [](commit_id = ed3aaf4f3ea5f4d34249bd35d2a1240a862183d4, deletion_comment = False)
_Originally posted by @marcschier in https://github.com/Azure/Industrial-IoT/issues/1928#issuecomment-1385277949_
|
1.0
|
We need better documentation for --strict mode in OPC Publisher, we need better documentation for all other message profiles. - > "Type": "ByteString",
I will address the docs. There will be a --strict version of the docs, and backcompat version (this one).
---
In reply to: [1385126686](https://github.com/Azure/Industrial-IoT/pull/1928#issuecomment-1385126686) [](http://example.com/codeflow?ancestors=1385126686,1385126686)
---
Refers to: docs/modules/telemetry-events-format.md:229 in ed3aaf4. [](commit_id = ed3aaf4f3ea5f4d34249bd35d2a1240a862183d4, deletion_comment = False)
_Originally posted by @marcschier in https://github.com/Azure/Industrial-IoT/issues/1928#issuecomment-1385277949_
|
non_process
|
we need better documentation for strict mode in opc publisher we need better documentation for all other message profiles type bytestring i will address the docs there will be a strict version of the docs and backcompat version this one in reply to refers to docs modules telemetry events format md in commit id deletion comment false originally posted by marcschier in
| 0
|
212,416
| 23,894,347,860
|
IssuesEvent
|
2022-09-08 13:47:58
|
samq-ghdemo/ori-kit
|
https://api.github.com/repos/samq-ghdemo/ori-kit
|
opened
|
CVE-2022-36067 (High) detected in vm2-3.9.3.tgz
|
security vulnerability
|
## CVE-2022-36067 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>vm2-3.9.3.tgz</b></p></summary>
<p>vm2 is a sandbox that can run untrusted code with whitelisted Node's built-in modules. Securely!</p>
<p>Library home page: <a href="https://registry.npmjs.org/vm2/-/vm2-3.9.3.tgz">https://registry.npmjs.org/vm2/-/vm2-3.9.3.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/vm2/package.json</p>
<p>
Dependency Hierarchy:
- juicy-chat-bot-0.6.4.tgz (Root Library)
- :x: **vm2-3.9.3.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/ori-kit/commit/ba236fd18ec3e6450d68d675bce1609d2e5d3230">ba236fd18ec3e6450d68d675bce1609d2e5d3230</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>
vm2 is a sandbox that can run untrusted code with whitelisted Node's built-in modules. In versions prior to version 3.9.11, a threat actor can bypass the sandbox protections to gain remote code execution rights on the host running the sandbox. This vulnerability was patched in the release of version 3.9.11 of vm2. There are no known workarounds.
<p>Publish Date: 2022-09-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-36067>CVE-2022-36067</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>10.0</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/patriksimek/vm2/security/advisories/GHSA-mrgp-mrhc-5jrq">https://github.com/patriksimek/vm2/security/advisories/GHSA-mrgp-mrhc-5jrq</a></p>
<p>Release Date: 2022-09-06</p>
<p>Fix Resolution: vm2 - 3.9.11</p>
</p>
</details>
<p></p>
|
True
|
CVE-2022-36067 (High) detected in vm2-3.9.3.tgz - ## CVE-2022-36067 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>vm2-3.9.3.tgz</b></p></summary>
<p>vm2 is a sandbox that can run untrusted code with whitelisted Node's built-in modules. Securely!</p>
<p>Library home page: <a href="https://registry.npmjs.org/vm2/-/vm2-3.9.3.tgz">https://registry.npmjs.org/vm2/-/vm2-3.9.3.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/vm2/package.json</p>
<p>
Dependency Hierarchy:
- juicy-chat-bot-0.6.4.tgz (Root Library)
- :x: **vm2-3.9.3.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/ori-kit/commit/ba236fd18ec3e6450d68d675bce1609d2e5d3230">ba236fd18ec3e6450d68d675bce1609d2e5d3230</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>
vm2 is a sandbox that can run untrusted code with whitelisted Node's built-in modules. In versions prior to version 3.9.11, a threat actor can bypass the sandbox protections to gain remote code execution rights on the host running the sandbox. This vulnerability was patched in the release of version 3.9.11 of vm2. There are no known workarounds.
<p>Publish Date: 2022-09-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-36067>CVE-2022-36067</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>10.0</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/patriksimek/vm2/security/advisories/GHSA-mrgp-mrhc-5jrq">https://github.com/patriksimek/vm2/security/advisories/GHSA-mrgp-mrhc-5jrq</a></p>
<p>Release Date: 2022-09-06</p>
<p>Fix Resolution: vm2 - 3.9.11</p>
</p>
</details>
<p></p>
|
non_process
|
cve high detected in tgz cve high severity vulnerability vulnerable library tgz is a sandbox that can run untrusted code with whitelisted node s built in modules securely library home page a href path to dependency file package json path to vulnerable library node modules package json dependency hierarchy juicy chat bot tgz root library x tgz vulnerable library found in head commit a href found in base branch main vulnerability details is a sandbox that can run untrusted code with whitelisted node s built in modules in versions prior to version a threat actor can bypass the sandbox protections to gain remote code execution rights on the host running the sandbox this vulnerability was patched in the release of version of there are no known workarounds 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 changed impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution
| 0
|
670,200
| 22,679,818,791
|
IssuesEvent
|
2022-07-04 08:53:39
|
HyphaApp/hypha
|
https://api.github.com/repos/HyphaApp/hypha
|
opened
|
Update to Python 3.10.5 (from 3.9.x)
|
Type: Maintenance Priority: Low
|
This is needed to update the Heroku buildpack to "heroku-22".
|
1.0
|
Update to Python 3.10.5 (from 3.9.x) - This is needed to update the Heroku buildpack to "heroku-22".
|
non_process
|
update to python from x this is needed to update the heroku buildpack to heroku
| 0
|
17,491
| 23,305,155,253
|
IssuesEvent
|
2022-08-07 22:39:09
|
sparc4-dev/astropop
|
https://api.github.com/repos/sparc4-dev/astropop
|
closed
|
Registration: need native byte order issue
|
bug image-processing
|
Both `cross-correlation` and `asterism-matching` need native byte order. Perform sep fixing on registering too.
```
2022-07-06 09:19:07,346 astropop - INFO - reading file 0 from 5: reduced/gd108/FB2022041720184978_C1.fits [file_collection]
/home/wagner/anaconda3/envs/astropop/lib/python3.9/site-packages/astropop/_db.py:93: FutureWarning: elementwise comparison failed; returning scalar instead, but in the future will perform elementwise comparison
if k in self.keywords or add_columns:
/home/wagner/anaconda3/envs/astropop/lib/python3.9/site-packages/astropop/_db.py:52: FutureWarning: elementwise comparison failed; returning scalar instead, but in the future will perform elementwise comparison
if item not in self.keywords:
/home/wagner/anaconda3/envs/astropop/lib/python3.9/site-packages/astropop/_db.py:33: FutureWarning: elementwise comparison failed; returning scalar instead, but in the future will perform elementwise comparison
if name in self.keywords:
/home/wagner/anaconda3/envs/astropop/lib/python3.9/site-packages/astropop/_db.py:38: FutureWarning: elementwise comparison failed; returning scalar instead, but in the future will perform elementwise comparison
while col in self.keywords:
2022-07-06 09:19:07,421 astropop - INFO - reading file 1 from 5: reduced/gd108/FB2022041720205104_C1.fits [file_collection]
2022-07-06 09:19:07,436 astropop - INFO - reading file 2 from 5: reduced/gd108/FB2022041720225229_C1.fits [file_collection]
2022-07-06 09:19:07,473 astropop - INFO - reading file 3 from 5: reduced/gd108/FB2022041720245353_C1.fits [file_collection]
2022-07-06 09:19:07,516 astropop - INFO - reading file 4 from 5: reduced/gd108/FB2022041720265478_C1.fits [file_collection]
Total files: 5
Star files (GD 108 - V): 5
['reduced/gd108/FB2022041720184978_C1.fits', 'reduced/gd108/FB2022041720205104_C1.fits', 'reduced/gd108/FB2022041720225229_C1.fits', 'reduced/gd108/FB2022041720245353_C1.fits', 'reduced/gd108/FB2022041720265478_C1.fits']
2022-07-06 09:19:18,244 astropop - INFO - Registering image 1 from 5 [register]
2022-07-06 09:19:18,274 astropop - INFO - Images are equal, skipping registering. [register]
---------------------------------------------------------------------------
ValueError Traceback (most recent call last)
Input In [2], in <cell line: 27>()
12 gd108_V2_frames = list(gd108_V2_fg.framedata(unit='adu', use_memmap_backend=True))
14 #gd108_V2_frames[0] = gd108_V2_frames[0].astype(np.float32)
15 #gd108_V2_frames[1] = gd108_V2_frames[1].astype(np.float32)
16 #gd108_V2_frames[2] = gd108_V2_frames[2].astype(np.float32)
(...)
24
25 #print(*gd108_V2_frames)
---> 27 registered_frames = register_framedata_list(gd108_V2_frames, algorithm='asterism-matching', inplace=True)
28 #registered_frames = register_framedata_list(gd108_V2_frames)
30 imagem_combinada = imcombine(registered_frames, method='sum')
File ~/anaconda3/envs/astropop/lib/python3.9/site-packages/astropop/image/register.py:425, in register_framedata_list(frame_list, algorithm, ref_image, clip_output, cval, inplace, **kwargs)
423 for i in range(n):
424 logger.info('Registering image %i from %i', i+1, n)
--> 425 reg_list[i] = reg.register_framedata(frame_list[ref_image],
426 frame_list[i],
427 cval=cval, inplace=inplace)
429 if clip_output:
430 shifts = [(i.meta['astropop registration_shift_x'],
431 i.meta['astropop registration_shift_y']) for i in reg_list]
File ~/anaconda3/envs/astropop/lib/python3.9/site-packages/astropop/image/register.py:184, in _BaseRegister.register_framedata(self, frame1, frame2, cval, inplace)
182 if not frame2.uncertainty.empty:
183 unct = frame2.get_uncertainty(return_none=False)
--> 184 unct = self._apply_transform_image(unct,
185 tform, cval=np.nan)
186 reg_frame.uncertainty = unct
188 sx, sy = tform.translation
File ~/anaconda3/envs/astropop/lib/python3.9/site-packages/astropop/image/register.py:62, in _BaseRegister._apply_transform_image(image, tform, cval)
59 @staticmethod
60 def _apply_transform_image(image, tform, cval=0):
61 """Apply the transform to an image."""
---> 62 return transform.warp(image, tform, mode='constant', cval=cval,
63 preserve_range=True)
File ~/anaconda3/envs/astropop/lib/python3.9/site-packages/skimage/transform/_warps.py:944, in warp(image, inverse_map, map_args, output_shape, order, mode, cval, clip, preserve_range)
942 ctype = 'float32_t' if image.dtype == np.float32 else 'float64_t'
943 if image.ndim == 2:
--> 944 warped = _warp_fast[ctype](image, matrix,
945 output_shape=output_shape,
946 order=order, mode=mode, cval=cval)
947 elif image.ndim == 3:
948 dims = []
File ~/anaconda3/envs/astropop/lib/python3.9/site-packages/skimage/transform/_warps_cy.pyx:71, in skimage.transform._warps_cy._warp_fast()
ValueError: Big-endian buffer not supported on little-endian compiler
```
|
1.0
|
Registration: need native byte order issue - Both `cross-correlation` and `asterism-matching` need native byte order. Perform sep fixing on registering too.
```
2022-07-06 09:19:07,346 astropop - INFO - reading file 0 from 5: reduced/gd108/FB2022041720184978_C1.fits [file_collection]
/home/wagner/anaconda3/envs/astropop/lib/python3.9/site-packages/astropop/_db.py:93: FutureWarning: elementwise comparison failed; returning scalar instead, but in the future will perform elementwise comparison
if k in self.keywords or add_columns:
/home/wagner/anaconda3/envs/astropop/lib/python3.9/site-packages/astropop/_db.py:52: FutureWarning: elementwise comparison failed; returning scalar instead, but in the future will perform elementwise comparison
if item not in self.keywords:
/home/wagner/anaconda3/envs/astropop/lib/python3.9/site-packages/astropop/_db.py:33: FutureWarning: elementwise comparison failed; returning scalar instead, but in the future will perform elementwise comparison
if name in self.keywords:
/home/wagner/anaconda3/envs/astropop/lib/python3.9/site-packages/astropop/_db.py:38: FutureWarning: elementwise comparison failed; returning scalar instead, but in the future will perform elementwise comparison
while col in self.keywords:
2022-07-06 09:19:07,421 astropop - INFO - reading file 1 from 5: reduced/gd108/FB2022041720205104_C1.fits [file_collection]
2022-07-06 09:19:07,436 astropop - INFO - reading file 2 from 5: reduced/gd108/FB2022041720225229_C1.fits [file_collection]
2022-07-06 09:19:07,473 astropop - INFO - reading file 3 from 5: reduced/gd108/FB2022041720245353_C1.fits [file_collection]
2022-07-06 09:19:07,516 astropop - INFO - reading file 4 from 5: reduced/gd108/FB2022041720265478_C1.fits [file_collection]
Total files: 5
Star files (GD 108 - V): 5
['reduced/gd108/FB2022041720184978_C1.fits', 'reduced/gd108/FB2022041720205104_C1.fits', 'reduced/gd108/FB2022041720225229_C1.fits', 'reduced/gd108/FB2022041720245353_C1.fits', 'reduced/gd108/FB2022041720265478_C1.fits']
2022-07-06 09:19:18,244 astropop - INFO - Registering image 1 from 5 [register]
2022-07-06 09:19:18,274 astropop - INFO - Images are equal, skipping registering. [register]
---------------------------------------------------------------------------
ValueError Traceback (most recent call last)
Input In [2], in <cell line: 27>()
12 gd108_V2_frames = list(gd108_V2_fg.framedata(unit='adu', use_memmap_backend=True))
14 #gd108_V2_frames[0] = gd108_V2_frames[0].astype(np.float32)
15 #gd108_V2_frames[1] = gd108_V2_frames[1].astype(np.float32)
16 #gd108_V2_frames[2] = gd108_V2_frames[2].astype(np.float32)
(...)
24
25 #print(*gd108_V2_frames)
---> 27 registered_frames = register_framedata_list(gd108_V2_frames, algorithm='asterism-matching', inplace=True)
28 #registered_frames = register_framedata_list(gd108_V2_frames)
30 imagem_combinada = imcombine(registered_frames, method='sum')
File ~/anaconda3/envs/astropop/lib/python3.9/site-packages/astropop/image/register.py:425, in register_framedata_list(frame_list, algorithm, ref_image, clip_output, cval, inplace, **kwargs)
423 for i in range(n):
424 logger.info('Registering image %i from %i', i+1, n)
--> 425 reg_list[i] = reg.register_framedata(frame_list[ref_image],
426 frame_list[i],
427 cval=cval, inplace=inplace)
429 if clip_output:
430 shifts = [(i.meta['astropop registration_shift_x'],
431 i.meta['astropop registration_shift_y']) for i in reg_list]
File ~/anaconda3/envs/astropop/lib/python3.9/site-packages/astropop/image/register.py:184, in _BaseRegister.register_framedata(self, frame1, frame2, cval, inplace)
182 if not frame2.uncertainty.empty:
183 unct = frame2.get_uncertainty(return_none=False)
--> 184 unct = self._apply_transform_image(unct,
185 tform, cval=np.nan)
186 reg_frame.uncertainty = unct
188 sx, sy = tform.translation
File ~/anaconda3/envs/astropop/lib/python3.9/site-packages/astropop/image/register.py:62, in _BaseRegister._apply_transform_image(image, tform, cval)
59 @staticmethod
60 def _apply_transform_image(image, tform, cval=0):
61 """Apply the transform to an image."""
---> 62 return transform.warp(image, tform, mode='constant', cval=cval,
63 preserve_range=True)
File ~/anaconda3/envs/astropop/lib/python3.9/site-packages/skimage/transform/_warps.py:944, in warp(image, inverse_map, map_args, output_shape, order, mode, cval, clip, preserve_range)
942 ctype = 'float32_t' if image.dtype == np.float32 else 'float64_t'
943 if image.ndim == 2:
--> 944 warped = _warp_fast[ctype](image, matrix,
945 output_shape=output_shape,
946 order=order, mode=mode, cval=cval)
947 elif image.ndim == 3:
948 dims = []
File ~/anaconda3/envs/astropop/lib/python3.9/site-packages/skimage/transform/_warps_cy.pyx:71, in skimage.transform._warps_cy._warp_fast()
ValueError: Big-endian buffer not supported on little-endian compiler
```
|
process
|
registration need native byte order issue both cross correlation and asterism matching need native byte order perform sep fixing on registering too astropop info reading file from reduced fits home wagner envs astropop lib site packages astropop db py futurewarning elementwise comparison failed returning scalar instead but in the future will perform elementwise comparison if k in self keywords or add columns home wagner envs astropop lib site packages astropop db py futurewarning elementwise comparison failed returning scalar instead but in the future will perform elementwise comparison if item not in self keywords home wagner envs astropop lib site packages astropop db py futurewarning elementwise comparison failed returning scalar instead but in the future will perform elementwise comparison if name in self keywords home wagner envs astropop lib site packages astropop db py futurewarning elementwise comparison failed returning scalar instead but in the future will perform elementwise comparison while col in self keywords astropop info reading file from reduced fits astropop info reading file from reduced fits astropop info reading file from reduced fits astropop info reading file from reduced fits total files star files gd v astropop info registering image from astropop info images are equal skipping registering valueerror traceback most recent call last input in in frames list fg framedata unit adu use memmap backend true frames frames astype np frames frames astype np frames frames astype np print frames registered frames register framedata list frames algorithm asterism matching inplace true registered frames register framedata list frames imagem combinada imcombine registered frames method sum file envs astropop lib site packages astropop image register py in register framedata list frame list algorithm ref image clip output cval inplace kwargs for i in range n logger info registering image i from i i n reg list reg register framedata frame list frame list cval cval inplace inplace if clip output shifts i meta for i in reg list file envs astropop lib site packages astropop image register py in baseregister register framedata self cval inplace if not uncertainty empty unct get uncertainty return none false unct self apply transform image unct tform cval np nan reg frame uncertainty unct sx sy tform translation file envs astropop lib site packages astropop image register py in baseregister apply transform image image tform cval staticmethod def apply transform image image tform cval apply the transform to an image return transform warp image tform mode constant cval cval preserve range true file envs astropop lib site packages skimage transform warps py in warp image inverse map map args output shape order mode cval clip preserve range ctype t if image dtype np else t if image ndim warped warp fast image matrix output shape output shape order order mode mode cval cval elif image ndim dims file envs astropop lib site packages skimage transform warps cy pyx in skimage transform warps cy warp fast valueerror big endian buffer not supported on little endian compiler
| 1
|
291,472
| 21,926,235,960
|
IssuesEvent
|
2022-05-23 04:41:38
|
rokath/trice
|
https://api.github.com/repos/rokath/trice
|
reopened
|
Create automatic tests for all taget mode variants
|
documentation enhancement quality
|
| Interface | Timestamp | Encryption | Buffer mode | result |
| - | - | - | - | - |
| RTT | yes | yes | double | no output |
| RTT | yes | yes | direct | ok |
| RTT | no | yes | double | ? |
| RTT | no | yes | direct | ? |
| RTT | x | no | x | ok |
| UART | x | x | x | ok |
|
1.0
|
Create automatic tests for all taget mode variants - | Interface | Timestamp | Encryption | Buffer mode | result |
| - | - | - | - | - |
| RTT | yes | yes | double | no output |
| RTT | yes | yes | direct | ok |
| RTT | no | yes | double | ? |
| RTT | no | yes | direct | ? |
| RTT | x | no | x | ok |
| UART | x | x | x | ok |
|
non_process
|
create automatic tests for all taget mode variants interface timestamp encryption buffer mode result rtt yes yes double no output rtt yes yes direct ok rtt no yes double rtt no yes direct rtt x no x ok uart x x x ok
| 0
|
275,536
| 8,576,781,095
|
IssuesEvent
|
2018-11-12 21:30:04
|
swe-ms-boun/2018fall-swe574-g1
|
https://api.github.com/repos/swe-ms-boun/2018fall-swe574-g1
|
closed
|
User registration
|
priority.low tier.api tier.db type.feature
|
* Implementing the user registration functionalities. Associated requirements are as follows:
* Users shall be able to create their account in the system with a simple process. Simple process means creating the user accounts by requiring them to provide the least information such as only email address and password.
|
1.0
|
User registration - * Implementing the user registration functionalities. Associated requirements are as follows:
* Users shall be able to create their account in the system with a simple process. Simple process means creating the user accounts by requiring them to provide the least information such as only email address and password.
|
non_process
|
user registration implementing the user registration functionalities associated requirements are as follows users shall be able to create their account in the system with a simple process simple process means creating the user accounts by requiring them to provide the least information such as only email address and password
| 0
|
7,982
| 11,170,752,514
|
IssuesEvent
|
2019-12-28 15:11:20
|
bisq-network/bisq
|
https://api.github.com/repos/bisq-network/bisq
|
closed
|
F2F trade stuck in some weird state
|
High an:investigation in:trade-process was:dropped
|
As I shared on [reddit](https://www.reddit.com/r/bisq/comments/cwj1ru/selling_f2f_but_not_sure_what_to_do/):
I see on Portfolio -> open trades a green item/line where I'm "BTC seller as maker" and I assume it's green because it's selected but the bullet points "Wait for blockchain confirmation" etc. are all greyed out.
In the information I see the taker fee transaction and the maker fee transaction and they have 20 and 2800 confirmations respectively but the taker fee transaction doesn't have the tick with the tooltip next to it as the maker fee transaction does.
I restarted bisq. I updated it to the latest version but nothing helps. My full node is not stuck, as the confirmations on the maker tx match what the block explorer says.
The taker is also available to provide his side I think. Just had a call with him and will meet him tomorrow.
|
1.0
|
F2F trade stuck in some weird state - As I shared on [reddit](https://www.reddit.com/r/bisq/comments/cwj1ru/selling_f2f_but_not_sure_what_to_do/):
I see on Portfolio -> open trades a green item/line where I'm "BTC seller as maker" and I assume it's green because it's selected but the bullet points "Wait for blockchain confirmation" etc. are all greyed out.
In the information I see the taker fee transaction and the maker fee transaction and they have 20 and 2800 confirmations respectively but the taker fee transaction doesn't have the tick with the tooltip next to it as the maker fee transaction does.
I restarted bisq. I updated it to the latest version but nothing helps. My full node is not stuck, as the confirmations on the maker tx match what the block explorer says.
The taker is also available to provide his side I think. Just had a call with him and will meet him tomorrow.
|
process
|
trade stuck in some weird state as i shared on i see on portfolio open trades a green item line where i m btc seller as maker and i assume it s green because it s selected but the bullet points wait for blockchain confirmation etc are all greyed out in the information i see the taker fee transaction and the maker fee transaction and they have and confirmations respectively but the taker fee transaction doesn t have the tick with the tooltip next to it as the maker fee transaction does i restarted bisq i updated it to the latest version but nothing helps my full node is not stuck as the confirmations on the maker tx match what the block explorer says the taker is also available to provide his side i think just had a call with him and will meet him tomorrow
| 1
|
15,172
| 26,602,137,169
|
IssuesEvent
|
2023-01-23 16:28:47
|
renovatebot/renovate
|
https://api.github.com/repos/renovatebot/renovate
|
opened
|
Istio packages failed
|
type:bug status:requirements priority-5-triage
|
### How are you running Renovate?
Mend Renovate hosted app on github.com
### If you're self-hosting Renovate, tell us what version of Renovate you run.
_No response_
### If you're self-hosting Renovate, select which platform you are using.
GitHub Enterprise Server
### If you're self-hosting Renovate, tell us what version of the platform you run.
_No response_
### Was this something which used to work for you, and then stopped?
It used to work, and then stopped
### Describe the bug
Istio in my go modules returns ` Failed to look up go dependency` after installing renovate
### Relevant debug logs
<details><summary>Logs</summary>
```
`DEBUG: Datasource connection error (repository=secret)
"datasource": "go",
"packageName": "istio.io/istio",
"url": undefined,
"errCode": "EPROTO"
DEBUG: Failed to look up go dependency istio.io/istio (repository=secret, packageFile=istio-init/go.mod, dependency=istio.io/istio)`
```
</details>
### Have you created a minimal reproduction repository?
No reproduction repository
|
1.0
|
Istio packages failed - ### How are you running Renovate?
Mend Renovate hosted app on github.com
### If you're self-hosting Renovate, tell us what version of Renovate you run.
_No response_
### If you're self-hosting Renovate, select which platform you are using.
GitHub Enterprise Server
### If you're self-hosting Renovate, tell us what version of the platform you run.
_No response_
### Was this something which used to work for you, and then stopped?
It used to work, and then stopped
### Describe the bug
Istio in my go modules returns ` Failed to look up go dependency` after installing renovate
### Relevant debug logs
<details><summary>Logs</summary>
```
`DEBUG: Datasource connection error (repository=secret)
"datasource": "go",
"packageName": "istio.io/istio",
"url": undefined,
"errCode": "EPROTO"
DEBUG: Failed to look up go dependency istio.io/istio (repository=secret, packageFile=istio-init/go.mod, dependency=istio.io/istio)`
```
</details>
### Have you created a minimal reproduction repository?
No reproduction repository
|
non_process
|
istio packages failed how are you running renovate mend renovate hosted app on github com if you re self hosting renovate tell us what version of renovate you run no response if you re self hosting renovate select which platform you are using github enterprise server if you re self hosting renovate tell us what version of the platform you run no response was this something which used to work for you and then stopped it used to work and then stopped describe the bug istio in my go modules returns failed to look up go dependency after installing renovate relevant debug logs logs debug datasource connection error repository secret datasource go packagename istio io istio url undefined errcode eproto debug failed to look up go dependency istio io istio repository secret packagefile istio init go mod dependency istio io istio have you created a minimal reproduction repository no reproduction repository
| 0
|
8,539
| 11,713,955,514
|
IssuesEvent
|
2020-03-09 11:20:06
|
kazuwjnlab/cvpaper
|
https://api.github.com/repos/kazuwjnlab/cvpaper
|
opened
|
[cvpaper] CVPR2019 #117 A Variational Auto-Encoder Model for Stochastic Point Processes
|
ActionPrediction PointProcess VAE 動画
|
## \#117 [A Variational Auto-Encoder Model for Stochastic Point Processes](http://openaccess.thecvf.com/content_CVPR_2019/papers/Mehrasa_A_Variational_Auto-Encoder_Model_for_Stochastic_Point_Processes_CVPR_2019_paper.pdf)
Nazanin Mehrasa, Akash Abdu Jyothi, Thibaut Durand, Jiawei He, Leonid Sigal, Greg Mori
### どんな論文か？
動画中のある時点までの動作とタイミングからその後の動作と継続時間を予測するタスク（point process?）をVAEベースの確率モデルで行う手法を提案．一般的なVAEが固定の潜在分布を仮定するのに対し，各時点での潜在分布と次の動作の潜在分布のパラメータを推定するposterirとpriorをエンコーダに導入し，動作の関係性を考慮できるようにした．
### 新規性
動画のシーンに動作が結びつけられているデータ（Point Process，例として調理過程など）の確率的モデル化をVAEベースの手法で行なった．時系列データのために，次時点の潜在分布のパラメータを予測するpriorをエンコーダに導入した．
### 結果
LSTMベースの手法と，提案手法からpriorを取り除いたもの（潜在分布を固定）を比較手法として実験を行なった．データセットにはMultiTHUMOS DatasetとBreakfast Datasetを用いた．対数尤度と動作の予測精度，時間の予測誤差MAEを指標とし評価を行なったところ，提案手法が既存手法に大きく勝った．
### その他（なぜ通ったか？等）
VAE, PointProcess, ActionPrediction, 動画,
|
1.0
|
[cvpaper] CVPR2019 #117 A Variational Auto-Encoder Model for Stochastic Point Processes - ## \#117 [A Variational Auto-Encoder Model for Stochastic Point Processes](http://openaccess.thecvf.com/content_CVPR_2019/papers/Mehrasa_A_Variational_Auto-Encoder_Model_for_Stochastic_Point_Processes_CVPR_2019_paper.pdf)
Nazanin Mehrasa, Akash Abdu Jyothi, Thibaut Durand, Jiawei He, Leonid Sigal, Greg Mori
### どんな論文か？
動画中のある時点までの動作とタイミングからその後の動作と継続時間を予測するタスク（point process?）をVAEベースの確率モデルで行う手法を提案．一般的なVAEが固定の潜在分布を仮定するのに対し，各時点での潜在分布と次の動作の潜在分布のパラメータを推定するposterirとpriorをエンコーダに導入し，動作の関係性を考慮できるようにした．
### 新規性
動画のシーンに動作が結びつけられているデータ（Point Process，例として調理過程など）の確率的モデル化をVAEベースの手法で行なった．時系列データのために，次時点の潜在分布のパラメータを予測するpriorをエンコーダに導入した．
### 結果
LSTMベースの手法と，提案手法からpriorを取り除いたもの（潜在分布を固定）を比較手法として実験を行なった．データセットにはMultiTHUMOS DatasetとBreakfast Datasetを用いた．対数尤度と動作の予測精度，時間の予測誤差MAEを指標とし評価を行なったところ，提案手法が既存手法に大きく勝った．
### その他（なぜ通ったか？等）
VAE, PointProcess, ActionPrediction, 動画,
|
process
|
a variational auto encoder model for stochastic point processes nazanin mehrasa akash abdu jyothi thibaut durand jiawei he leonid sigal greg mori どんな論文か？ 動画中のある時点までの動作とタイミングからその後の動作と継続時間を予測するタスク（point process ）をvaeベースの確率モデルで行う手法を提案．一般的なvaeが固定の潜在分布を仮定するのに対し，各時点での潜在分布と次の動作の潜在分布のパラメータを推定するposterirとpriorをエンコーダに導入し，動作の関係性を考慮できるようにした． 新規性 動画のシーンに動作が結びつけられているデータ（point process，例として調理過程など）の確率的モデル化をvaeベースの手法で行なった．時系列データのために，次時点の潜在分布のパラメータを予測するpriorをエンコーダに導入した． 結果 lstmベースの手法と，提案手法からpriorを取り除いたもの（潜在分布を固定）を比較手法として実験を行なった．データセットにはmultithumos datasetとbreakfast datasetを用いた．対数尤度と動作の予測精度，時間の予測誤差maeを指標とし評価を行なったところ，提案手法が既存手法に大きく勝った． その他（なぜ通ったか？等） vae pointprocess actionprediction 動画
| 1
|
53,223
| 7,812,322,408
|
IssuesEvent
|
2018-06-12 13:04:40
|
WordPress/gutenberg
|
https://api.github.com/repos/WordPress/gutenberg
|
opened
|
Data Modue: Improve Selectors/Actions docs
|
Documentation Good First Issue
|
Related #7264
Now, that we generate markdown docs for Selectors and Actions, we need to make sure the wording used there is accurate and not redundant.
For instance: Actions shouldn't state that they return action objects.
Instead of `Returns an action object used in signalling that block types have been added.`, write `Signal that a block type, or types, have been added.`
More details here https://github.com/WordPress/gutenberg/pull/7264#pullrequestreview-127916268
|
1.0
|
Data Modue: Improve Selectors/Actions docs - Related #7264
Now, that we generate markdown docs for Selectors and Actions, we need to make sure the wording used there is accurate and not redundant.
For instance: Actions shouldn't state that they return action objects.
Instead of `Returns an action object used in signalling that block types have been added.`, write `Signal that a block type, or types, have been added.`
More details here https://github.com/WordPress/gutenberg/pull/7264#pullrequestreview-127916268
|
non_process
|
data modue improve selectors actions docs related now that we generate markdown docs for selectors and actions we need to make sure the wording used there is accurate and not redundant for instance actions shouldn t state that they return action objects instead of returns an action object used in signalling that block types have been added write signal that a block type or types have been added more details here
| 0
|
10,796
| 13,609,206,531
|
IssuesEvent
|
2020-09-23 04:35:50
|
googleapis/java-dns
|
https://api.github.com/repos/googleapis/java-dns
|
closed
|
Dependency Dashboard
|
api: dns type: process
|
This issue contains a list of Renovate updates and their statuses.
## Open
These updates have all been created already. Click a checkbox below to force a retry/rebase of any.
- [ ] <!-- rebase-branch=renovate/com.google.cloud-google-cloud-dns-1.x -->chore(deps): update dependency com.google.cloud:google-cloud-dns to v1.0.1
- [ ] <!-- rebase-branch=renovate/org.easymock-easymock-4.x -->deps: update dependency org.easymock:easymock to v4
---
- [ ] <!-- manual job -->Check this box to trigger a request for Renovate to run again on this repository
|
1.0
|
Dependency Dashboard - This issue contains a list of Renovate updates and their statuses.
## Open
These updates have all been created already. Click a checkbox below to force a retry/rebase of any.
- [ ] <!-- rebase-branch=renovate/com.google.cloud-google-cloud-dns-1.x -->chore(deps): update dependency com.google.cloud:google-cloud-dns to v1.0.1
- [ ] <!-- rebase-branch=renovate/org.easymock-easymock-4.x -->deps: update dependency org.easymock:easymock to v4
---
- [ ] <!-- manual job -->Check this box to trigger a request for Renovate to run again on this repository
|
process
|
dependency dashboard this issue contains a list of renovate updates and their statuses open these updates have all been created already click a checkbox below to force a retry rebase of any chore deps update dependency com google cloud google cloud dns to deps update dependency org easymock easymock to check this box to trigger a request for renovate to run again on this repository
| 1
|
12,639
| 15,016,634,661
|
IssuesEvent
|
2021-02-01 09:50:21
|
threefoldtech/js-sdk
|
https://api.github.com/repos/threefoldtech/js-sdk
|
closed
|
Adding a worker node to an existing cluster in a VDC takes forever
|
process_wontfix
|
VDC name: jetserthing
I launched a numbetr of marketsplace solutions (2) and wen I tried to launch the 3rd one, I got a message that told me that there were no more resources.
Wanted to add a worker node to see of that would lead to more capacity being available in the cluster that would allow me to launch this peertube container. The progress screen was slow to progress and got stuck at this forever:
I pressed "Reload page" a couple of times but always got back to the same rotating page.
CLI shows a new worker node
```
john@RescuedMac:~/.kube$ kubectl get nodes
NAME STATUS ROLES AGE VERSION
k3os-21973 Ready <none> 8m59s v1.19.4+k3s1
k3os-31241 Ready <none> 22h v1.19.4+k3s1
k3os-4283 Ready master 22h v1.19.4+k3s1
```
|
1.0
|
Adding a worker node to an existing cluster in a VDC takes forever - VDC name: jetserthing
I launched a numbetr of marketsplace solutions (2) and wen I tried to launch the 3rd one, I got a message that told me that there were no more resources.
Wanted to add a worker node to see of that would lead to more capacity being available in the cluster that would allow me to launch this peertube container. The progress screen was slow to progress and got stuck at this forever:
I pressed "Reload page" a couple of times but always got back to the same rotating page.
CLI shows a new worker node
```
john@RescuedMac:~/.kube$ kubectl get nodes
NAME STATUS ROLES AGE VERSION
k3os-21973 Ready <none> 8m59s v1.19.4+k3s1
k3os-31241 Ready <none> 22h v1.19.4+k3s1
k3os-4283 Ready master 22h v1.19.4+k3s1
```
|
process
|
adding a worker node to an existing cluster in a vdc takes forever vdc name jetserthing i launched a numbetr of marketsplace solutions and wen i tried to launch the one i got a message that told me that there were no more resources wanted to add a worker node to see of that would lead to more capacity being available in the cluster that would allow me to launch this peertube container the progress screen was slow to progress and got stuck at this forever i pressed reload page a couple of times but always got back to the same rotating page cli shows a new worker node john rescuedmac kube kubectl get nodes name status roles age version ready ready ready master
| 1
|
8,457
| 11,631,060,176
|
IssuesEvent
|
2020-02-28 00:08:58
|
pytorch/pytorch
|
https://api.github.com/repos/pytorch/pytorch
|
closed
|
test_backwards_fork flaky test (plus deadlock after)
|
better-engineering module: multiprocessing topic: flaky-tests triaged
|
Here's what a failure looks like:
```
07:50:54 ======================================================================
07:50:54 FAIL: test_backwards_fork (__main__.TestMultiprocessing)
07:50:54 backwards() should succeed when called before and after a fork
07:50:54 ----------------------------------------------------------------------
07:50:54 Traceback (most recent call last):
07:50:54 File "test_multiprocessing.py", line 436, in test_backwards_fork
07:50:54 self.assertFalse(p.is_alive())
07:50:54 AssertionError: True is not false
07:50:54
07:50:54 ----------------------------------------------------------------------
07:50:54 Ran 19 tests in 23.804s
07:50:54
07:50:54 FAILED (failures=1, skipped=3)
08:03:07 Build timed out (after 20 minutes). Marking the build as failed.
08:03:07 Build was aborted
```
First `test_backward_fork` fails (not good), and then the exit from Python hangs, so that the build is only terminated when timeout happens.
CC @colesbury who originally added the test in b79d74aa812cf5a3370ab09e20704453b070cb0e
Known failure occurrences:
On master:
* https://ci.pytorch.org/jenkins/job/pytorch-builds/job/pytorch-win-ws2016-cuda9-cudnn7-py3-test/2927//console (on master; tests before and after pass)
PRs:
* https://ci.pytorch.org/jenkins/job/pytorch-builds/job/pytorch-linux-xenial-cuda9-cudnn7-py2-test/4624//console
* https://ci.pytorch.org/jenkins/job/pytorch-builds/job/pytorch-linux-xenial-cuda9-cudnn7-py2-test/4623//console
* https://ci.pytorch.org/jenkins/job/pytorch-builds/job/pytorch-linux-xenial-cuda8-cudnn6-py3-test/4685//console
|
1.0
|
test_backwards_fork flaky test (plus deadlock after) - Here's what a failure looks like:
```
07:50:54 ======================================================================
07:50:54 FAIL: test_backwards_fork (__main__.TestMultiprocessing)
07:50:54 backwards() should succeed when called before and after a fork
07:50:54 ----------------------------------------------------------------------
07:50:54 Traceback (most recent call last):
07:50:54 File "test_multiprocessing.py", line 436, in test_backwards_fork
07:50:54 self.assertFalse(p.is_alive())
07:50:54 AssertionError: True is not false
07:50:54
07:50:54 ----------------------------------------------------------------------
07:50:54 Ran 19 tests in 23.804s
07:50:54
07:50:54 FAILED (failures=1, skipped=3)
08:03:07 Build timed out (after 20 minutes). Marking the build as failed.
08:03:07 Build was aborted
```
First `test_backward_fork` fails (not good), and then the exit from Python hangs, so that the build is only terminated when timeout happens.
CC @colesbury who originally added the test in b79d74aa812cf5a3370ab09e20704453b070cb0e
Known failure occurrences:
On master:
* https://ci.pytorch.org/jenkins/job/pytorch-builds/job/pytorch-win-ws2016-cuda9-cudnn7-py3-test/2927//console (on master; tests before and after pass)
PRs:
* https://ci.pytorch.org/jenkins/job/pytorch-builds/job/pytorch-linux-xenial-cuda9-cudnn7-py2-test/4624//console
* https://ci.pytorch.org/jenkins/job/pytorch-builds/job/pytorch-linux-xenial-cuda9-cudnn7-py2-test/4623//console
* https://ci.pytorch.org/jenkins/job/pytorch-builds/job/pytorch-linux-xenial-cuda8-cudnn6-py3-test/4685//console
|
process
|
test backwards fork flaky test plus deadlock after here s what a failure looks like fail test backwards fork main testmultiprocessing backwards should succeed when called before and after a fork traceback most recent call last file test multiprocessing py line in test backwards fork self assertfalse p is alive assertionerror true is not false ran tests in failed failures skipped build timed out after minutes marking the build as failed build was aborted first test backward fork fails not good and then the exit from python hangs so that the build is only terminated when timeout happens cc colesbury who originally added the test in known failure occurrences on master on master tests before and after pass prs
| 1
|
36,166
| 8,056,848,647
|
IssuesEvent
|
2018-08-02 13:54:02
|
usnistgov/ACVP
|
https://api.github.com/repos/usnistgov/ACVP
|
closed
|
CTR DRBG: test vectors without PR seem wrong
|
Numerical code bug Spec error
|
I get the following vectors for predictionresistance == false:
```
"testType" : "AFT",
"mode" : "AES-128",
"derFunc" : true,
"predResistance" : false,
"entropyInputLen" : 128,
"reSeed" : true,
"nonceLen" : 64,
"persoStringLen" : 0,
"additionalInputLen" : 0,
"returnedBitsLen" : 512,
"tests" : [ {
"tcId" : 1,
"entropyInput" : "CAED3A22E6CEF0801CB84C393CAD1B10",
"nonce" : "214AC39FACDA5E84",
"persoString" : "",
"otherInput" : [ {
"additionalInput" : "",
"entropyInput" : "5DBF858FCF24267F3C1CBFD2B3CAF805"
}, {
"additionalInput" : "",
"entropyInput" : ""
}, {
"additionalInput" : "",
"entropyInput" : ""
} ]
}, {
```
The providing of otherInput seems wrong as we do not have prediction resistance. Besides, there are 3 entries in otherInput.
|
1.0
|
CTR DRBG: test vectors without PR seem wrong - I get the following vectors for predictionresistance == false:
```
"testType" : "AFT",
"mode" : "AES-128",
"derFunc" : true,
"predResistance" : false,
"entropyInputLen" : 128,
"reSeed" : true,
"nonceLen" : 64,
"persoStringLen" : 0,
"additionalInputLen" : 0,
"returnedBitsLen" : 512,
"tests" : [ {
"tcId" : 1,
"entropyInput" : "CAED3A22E6CEF0801CB84C393CAD1B10",
"nonce" : "214AC39FACDA5E84",
"persoString" : "",
"otherInput" : [ {
"additionalInput" : "",
"entropyInput" : "5DBF858FCF24267F3C1CBFD2B3CAF805"
}, {
"additionalInput" : "",
"entropyInput" : ""
}, {
"additionalInput" : "",
"entropyInput" : ""
} ]
}, {
```
The providing of otherInput seems wrong as we do not have prediction resistance. Besides, there are 3 entries in otherInput.
|
non_process
|
ctr drbg test vectors without pr seem wrong i get the following vectors for predictionresistance false testtype aft mode aes derfunc true predresistance false entropyinputlen reseed true noncelen persostringlen additionalinputlen returnedbitslen tests tcid entropyinput nonce persostring otherinput additionalinput entropyinput additionalinput entropyinput additionalinput entropyinput the providing of otherinput seems wrong as we do not have prediction resistance besides there are entries in otherinput
| 0
|
64,708
| 8,755,470,081
|
IssuesEvent
|
2018-12-14 14:57:56
|
flyve-mdm/web-mdm-dashboard
|
https://api.github.com/repos/flyve-mdm/web-mdm-dashboard
|
opened
|
Test reports
|
ci documentation
|
<!-- File a GitHub issue only for bugs or feature requests related to the code **in this repository**. For other topics you can get more information in the README file. -->
### Observed Results:
Missing test report information
<!-- This could be a description, error output, steps to reproduce, a feature missed, etc. -->
### Expected behavior:
Display the test report in the development section
<!-- What did you expect to happen? -->
|
1.0
|
Test reports - <!-- File a GitHub issue only for bugs or feature requests related to the code **in this repository**. For other topics you can get more information in the README file. -->
### Observed Results:
Missing test report information
<!-- This could be a description, error output, steps to reproduce, a feature missed, etc. -->
### Expected behavior:
Display the test report in the development section
<!-- What did you expect to happen? -->
|
non_process
|
test reports observed results missing test report information expected behavior display the test report in the development section
| 0
|
104,731
| 4,218,091,739
|
IssuesEvent
|
2016-06-30 15:00:28
|
RhoInc/safety-results-over-time
|
https://api.github.com/repos/RhoInc/safety-results-over-time
|
closed
|
Add Filter by Site Feature
|
high priority
|
Add feature to filter by site, so they can see AEs (and vitals, labs, etc.) from one site at a time
|
1.0
|
Add Filter by Site Feature - Add feature to filter by site, so they can see AEs (and vitals, labs, etc.) from one site at a time
|
non_process
|
add filter by site feature add feature to filter by site so they can see aes and vitals labs etc from one site at a time
| 0
|
5,734
| 8,576,878,999
|
IssuesEvent
|
2018-11-12 21:49:34
|
IIIF/website
|
https://api.github.com/repos/IIIF/website
|
opened
|
Move editorial committee membership from /api/ to /community/, update re TRC
|
TRC in progress process
|
As part of https://github.com/IIIF/api/issues/1637 there should be:
* `/community/editors/` -- editorial committee membership and role
* `/community/policy/editorial/` -- editorial committee process
and then we remove the existing https://iiif.io/api/annex/notes/editors/ and fix links in /api/
|
1.0
|
Move editorial committee membership from /api/ to /community/, update re TRC - As part of https://github.com/IIIF/api/issues/1637 there should be:
* `/community/editors/` -- editorial committee membership and role
* `/community/policy/editorial/` -- editorial committee process
and then we remove the existing https://iiif.io/api/annex/notes/editors/ and fix links in /api/
|
process
|
move editorial committee membership from api to community update re trc as part of there should be community editors editorial committee membership and role community policy editorial editorial committee process and then we remove the existing and fix links in api
| 1
|
17,107
| 22,628,041,065
|
IssuesEvent
|
2022-06-30 12:29:40
|
zotero/zotero-google-docs-integration
|
https://api.github.com/repos/zotero/zotero-google-docs-integration
|
closed
|
Google Docs v2 400 error: Invalid requests[20].deleteNamedRange: ID or name for named range must be set
|
bug Word Processor Integration
|
https://forums.zotero.org/discussion/98006/google-docs-updating-error
Resulting in "{Updating}"
|
1.0
|
Google Docs v2 400 error: Invalid requests[20].deleteNamedRange: ID or name for named range must be set - https://forums.zotero.org/discussion/98006/google-docs-updating-error
Resulting in "{Updating}"
|
process
|
google docs error invalid requests deletenamedrange id or name for named range must be set resulting in updating
| 1
|
172,752
| 6,515,941,006
|
IssuesEvent
|
2017-08-26 23:08:11
|
josephroque/campus-guide
|
https://api.github.com/repos/josephroque/campus-guide
|
opened
|
Searching causes warning message about slow JS
|
bug priority-low
|
Error message is here:
```
Error setting property 'text' of RCTTextField with tag #405: Native TextInput(<some text>) is 5 events ahead of JS - try to make your JS faster.
```
where <some text> is some previous search terms.
Most likely has to do with typing causing `actions.search` in `AppHeader` to be called, which sets search term props and propagates throughout app to update filters, and by the time it propagates back to `AppHeader` to re-render with the new term and set `TextInput` value, the user has already typed more text.
|
1.0
|
Searching causes warning message about slow JS - Error message is here:
```
Error setting property 'text' of RCTTextField with tag #405: Native TextInput(<some text>) is 5 events ahead of JS - try to make your JS faster.
```
where <some text> is some previous search terms.
Most likely has to do with typing causing `actions.search` in `AppHeader` to be called, which sets search term props and propagates throughout app to update filters, and by the time it propagates back to `AppHeader` to re-render with the new term and set `TextInput` value, the user has already typed more text.
|
non_process
|
searching causes warning message about slow js error message is here error setting property text of rcttextfield with tag native textinput is events ahead of js try to make your js faster where is some previous search terms most likely has to do with typing causing actions search in appheader to be called which sets search term props and propagates throughout app to update filters and by the time it propagates back to appheader to re render with the new term and set textinput value the user has already typed more text
| 0
|
21,759
| 30,277,403,438
|
IssuesEvent
|
2023-07-07 21:09:30
|
hashgraph/hedera-json-rpc-relay
|
https://api.github.com/repos/hashgraph/hedera-json-rpc-relay
|
closed
|
Missing `pnpm` dependency
|
bug enhancement P2 process
|
### Description
When I try to run the project following the steps in read me, I always get the following error.
```
> build
> npx lerna run build
lerna notice cli v6.4.1
lerna info versioning independent
✖ @hashgraph/json-rpc-relay:build
> @hashgraph/json-rpc-relay@0.27.0-SNAPSHOT build
> pnpm run clean && pnpm run compile
sh: 1: pnpm: not found
npm ERR! Lifecycle script `build` failed with error:
npm ERR! Error: command failed
npm ERR! in workspace: @hashgraph/json-rpc-relay@0.27.0-SNAPSHOT
npm ERR! at location: /home/ubuntu/hedera/hedera-json-rpc-relay/packages/relay
```
This is not a big deal but we should include `pnpm` in the dependency list as we needs it for building the project.
### Steps to reproduce
Clone the project and then run the following steps
```
From the root of the project workspace:
Run npm install. This will create and populate node_modules.
Run npm run setup. This will link the node_modules to the packages, and the packages together.
Run npm run build. This will clean and compile the relay library and the server.
Run npm run start. This will start the server on port 7546.
```
### Additional context
_No response_
### Hedera network
mainnet, testnet, previewnet, other
### Version
lastest
### Operating system
None
|
1.0
|
Missing `pnpm` dependency - ### Description
When I try to run the project following the steps in read me, I always get the following error.
```
> build
> npx lerna run build
lerna notice cli v6.4.1
lerna info versioning independent
✖ @hashgraph/json-rpc-relay:build
> @hashgraph/json-rpc-relay@0.27.0-SNAPSHOT build
> pnpm run clean && pnpm run compile
sh: 1: pnpm: not found
npm ERR! Lifecycle script `build` failed with error:
npm ERR! Error: command failed
npm ERR! in workspace: @hashgraph/json-rpc-relay@0.27.0-SNAPSHOT
npm ERR! at location: /home/ubuntu/hedera/hedera-json-rpc-relay/packages/relay
```
This is not a big deal but we should include `pnpm` in the dependency list as we needs it for building the project.
### Steps to reproduce
Clone the project and then run the following steps
```
From the root of the project workspace:
Run npm install. This will create and populate node_modules.
Run npm run setup. This will link the node_modules to the packages, and the packages together.
Run npm run build. This will clean and compile the relay library and the server.
Run npm run start. This will start the server on port 7546.
```
### Additional context
_No response_
### Hedera network
mainnet, testnet, previewnet, other
### Version
lastest
### Operating system
None
|
process
|
missing pnpm dependency description when i try to run the project following the steps in read me i always get the following error build npx lerna run build lerna notice cli lerna info versioning independent ✖ hashgraph json rpc relay build hashgraph json rpc relay snapshot build pnpm run clean pnpm run compile sh pnpm not found npm err lifecycle script build failed with error npm err error command failed npm err in workspace hashgraph json rpc relay snapshot npm err at location home ubuntu hedera hedera json rpc relay packages relay this is not a big deal but we should include pnpm in the dependency list as we needs it for building the project steps to reproduce clone the project and then run the following steps from the root of the project workspace run npm install this will create and populate node modules run npm run setup this will link the node modules to the packages and the packages together run npm run build this will clean and compile the relay library and the server run npm run start this will start the server on port additional context no response hedera network mainnet testnet previewnet other version lastest operating system none
| 1
|
5,614
| 8,469,487,706
|
IssuesEvent
|
2018-10-23 23:13:05
|
googleapis/google-api-java-client-services
|
https://api.github.com/repos/googleapis/google-api-java-client-services
|
closed
|
Setup CI
|
type: process
|
If we want to enable automerging generated libraries, we need to ensure the projects build.
|
1.0
|
Setup CI - If we want to enable automerging generated libraries, we need to ensure the projects build.
|
process
|
setup ci if we want to enable automerging generated libraries we need to ensure the projects build
| 1
|
325,778
| 24,061,182,002
|
IssuesEvent
|
2022-09-16 23:02:20
|
vala-lang/vala-www
|
https://api.github.com/repos/vala-lang/vala-www
|
closed
|
Add all information about translating website content in the repository
|
documentation
|
Currently, the README gives a summary of the steps needed to translate website content.
This should be expanded on so everything translators need to know about adding translations to the website is in the repository.
|
1.0
|
Add all information about translating website content in the repository - Currently, the README gives a summary of the steps needed to translate website content.
This should be expanded on so everything translators need to know about adding translations to the website is in the repository.
|
non_process
|
add all information about translating website content in the repository currently the readme gives a summary of the steps needed to translate website content this should be expanded on so everything translators need to know about adding translations to the website is in the repository
| 0
|
380,051
| 11,253,619,374
|
IssuesEvent
|
2020-01-11 17:30:47
|
Atlantiss/NetherwingBugtracker
|
https://api.github.com/repos/Atlantiss/NetherwingBugtracker
|
closed
|
Multiple spells going off in a single global
|
- Core Mechanic Exploit/Abuse - Priority
|
**Description**:
Currently, you're able to cast multiple instant casted spells in the same global. In this example, I'll use the life tap as an example. You're casting Drain Life - at the end of the cast (between last tick and the 2nd to last tick) you tap life tap - you get more than 1 cast off.
This is the only example I could find, but I can surely imagine that there's exploit potential for someone brighter than myself.
Server revision: 2605
|
1.0
|
Multiple spells going off in a single global - **Description**:
Currently, you're able to cast multiple instant casted spells in the same global. In this example, I'll use the life tap as an example. You're casting Drain Life - at the end of the cast (between last tick and the 2nd to last tick) you tap life tap - you get more than 1 cast off.
This is the only example I could find, but I can surely imagine that there's exploit potential for someone brighter than myself.
Server revision: 2605
|
non_process
|
multiple spells going off in a single global description currently you re able to cast multiple instant casted spells in the same global in this example i ll use the life tap as an example you re casting drain life at the end of the cast between last tick and the to last tick you tap life tap you get more than cast off this is the only example i could find but i can surely imagine that there s exploit potential for someone brighter than myself server revision
| 0
|
964
| 3,422,103,187
|
IssuesEvent
|
2015-12-08 21:34:43
|
darnir/wget
|
https://api.github.com/repos/darnir/wget
|
closed
|
./gettext.h:262:6: '__STRICT_ANSI__' is not defined, evaluates to 0
|
Lexical or Preprocessor Issue Wundef
|
./gettext.h:262:6: warning: '__STRICT_ANSI__' is not defined, evaluates to 0 [-Wundef,Lexical or Preprocessor Issue]
|
1.0
|
./gettext.h:262:6: '__STRICT_ANSI__' is not defined, evaluates to 0 - ./gettext.h:262:6: warning: '__STRICT_ANSI__' is not defined, evaluates to 0 [-Wundef,Lexical or Preprocessor Issue]
|
process
|
gettext h strict ansi is not defined evaluates to gettext h warning strict ansi is not defined evaluates to
| 1
|
495,486
| 14,282,788,974
|
IssuesEvent
|
2020-11-23 10:05:24
|
VolmitSoftware/Iris
|
https://api.github.com/repos/VolmitSoftware/Iris
|
closed
|
Aggro biome shuffle not very aggro.
|
Enhancement Low Priority Plugin
|
I made three worlds with three seeds.
the biomes look like they got gently stirred rather than completely shuffled.
World1: https://cdn.discordapp.com/attachments/666290834878234647/767347644883664896/unknown.png
World2: https://cdn.discordapp.com/attachments/666290834878234647/767347727725363240/unknown.png
World3: https://cdn.discordapp.com/attachments/666290834878234647/767347892386005002/unknown.png
|
1.0
|
Aggro biome shuffle not very aggro. - I made three worlds with three seeds.
the biomes look like they got gently stirred rather than completely shuffled.
World1: https://cdn.discordapp.com/attachments/666290834878234647/767347644883664896/unknown.png
World2: https://cdn.discordapp.com/attachments/666290834878234647/767347727725363240/unknown.png
World3: https://cdn.discordapp.com/attachments/666290834878234647/767347892386005002/unknown.png
|
non_process
|
aggro biome shuffle not very aggro i made three worlds with three seeds the biomes look like they got gently stirred rather than completely shuffled
| 0
|
173,793
| 6,530,920,949
|
IssuesEvent
|
2017-08-30 16:43:48
|
nadineproject/nadine
|
https://api.github.com/repos/nadineproject/nadine
|
closed
|
CC to staff@ gets lost in the aether
|
High Priority
|
I am not getting emails that are To: someone, and are CC: to staff.
|
1.0
|
CC to staff@ gets lost in the aether - I am not getting emails that are To: someone, and are CC: to staff.
|
non_process
|
cc to staff gets lost in the aether i am not getting emails that are to someone and are cc to staff
| 0
|
19,556
| 25,878,525,010
|
IssuesEvent
|
2022-12-14 09:39:44
|
mehta-lab/microDL
|
https://api.github.com/repos/mehta-lab/microDL
|
closed
|
Masking in gunpowder pipeline
|
preprocessing
|
Current zarr reader pr should cover reading functionality for mask creation. Computation is already implemented.
Need to write masks to additional channel in zarr array. If we create a copy with flatfield correction, both copies need to have the same amount of channels. Plan for this is:
- Compute masks for 'raw' data, and store as additional channel in 'raw' data array
- Compute flat-field corrected data.
- Compute mask for flat-field corrected data and store as additional channel in ff corrected data array.
*check if masks channel already exists before computing*
Note: metadata for mask creation should be saved in `torch_config.yml` file. When written, create copy in zarr store to 'tag' the masks to record how they were generated
|
1.0
|
Masking in gunpowder pipeline - Current zarr reader pr should cover reading functionality for mask creation. Computation is already implemented.
Need to write masks to additional channel in zarr array. If we create a copy with flatfield correction, both copies need to have the same amount of channels. Plan for this is:
- Compute masks for 'raw' data, and store as additional channel in 'raw' data array
- Compute flat-field corrected data.
- Compute mask for flat-field corrected data and store as additional channel in ff corrected data array.
*check if masks channel already exists before computing*
Note: metadata for mask creation should be saved in `torch_config.yml` file. When written, create copy in zarr store to 'tag' the masks to record how they were generated
|
process
|
masking in gunpowder pipeline current zarr reader pr should cover reading functionality for mask creation computation is already implemented need to write masks to additional channel in zarr array if we create a copy with flatfield correction both copies need to have the same amount of channels plan for this is compute masks for raw data and store as additional channel in raw data array compute flat field corrected data compute mask for flat field corrected data and store as additional channel in ff corrected data array check if masks channel already exists before computing note metadata for mask creation should be saved in torch config yml file when written create copy in zarr store to tag the masks to record how they were generated
| 1
|
17,451
| 23,269,905,533
|
IssuesEvent
|
2022-08-04 21:32:14
|
vectordotdev/vector
|
https://api.github.com/repos/vectordotdev/vector
|
closed
|
Schema metadata RFC
|
type: task domain: processing
|
As a first step towards supporting various schemas, we want to shift the event metadata into a Vector specific namespace. This will solve a number of awkward siutations where Vector's metadata clashes with the user's schema.
## Examples
### Transitioning from Logstash
Let's look at a simple example where a user is replacing Logstash with Vector. Vector would receive data from upstream beats over TCP in the following format:
```json
{
"message": "127.0.0.1 - - [11/Dec/2013:00:01:45 -0800] \"GET /xampp/status.php HTTP/1.1\" 200 3891 \"http://cadenza/xampp/navi.php\" \"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:25.0) Gecko/20100101 Firefox/25.0\"",
"@timestamp": "2013-12-11T08:01:45.000Z",
"@version": "1",
"host": "cadenza",
"clientip": "127.0.0.1",
"ident": "-",
"auth": "-",
"timestamp": "11/Dec/2013:00:01:45 -0800",
"verb": "GET",
"request": "/xampp/status.php",
"httpversion": "1.1",
"response": "200",
"bytes": "3891",
"referrer": "\"http://cadenza/xampp/navi.php\"",
"agent": "\"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:25.0) Gecko/20100101 Firefox/25.0\""
}
```
Here we can see that the event is already enriched with metadata. When the event leaves the Vector `socket` source it'll be formatted as such:
```json
{
"timestamp": "...",
"host": "...",
"message": "{\n\"message\": \"127.0.0.1 - - [11/Dec/2013:00:01:45 -0800] \"GET /xampp/status.php HTTP/1.1\" 200 3891 \"http://cadenza/xampp/navi.php\" \"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:25.0) Gecko/20100101 Firefox/25.0\"\",\n\"@timestamp\": \"2013-12-11T08:01:45.000Z\",\n\"@version\": \"1\",\n\"host\": \"cadenza\",\n\"clientip\": \"127.0.0.1\",\n\"ident\": \"-\",\n\"auth\": \"-\",\n\"timestamp\": \"11/Dec/2013:00:01:45 -0800\",\n\"verb\": \"GET\",\n\"request\": \"/xampp/status.php\",\n\"httpversion\": \"1.1\",\n\"response\": \"200\",\n\"bytes\": \"3891\",\n\"referrer\": \"\"http://cadenza/xampp/navi.php\"\",\n\"agent\": \"\"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:25.0) Gecko/20100101 Firefox/25.0\"\"\n}\n"
}
```
Right off the bat this is awkward since we've constructed an event that does not resemble what they are expecting. To solve this the user must run the event through the `json_parser` which would result in:
```json
{
"timestamp": "...",
"message": "127.0.0.1 - - [11/Dec/2013:00:01:45 -0800] \"GET /xampp/status.php HTTP/1.1\" 200 3891 \"http://cadenza/xampp/navi.php\" \"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:25.0) Gecko/20100101 Firefox/25.0\"",
"@timestamp": "2013-12-11T08:01:45.000Z",
"@version": "1",
"host": "cadenza",
"clientip": "127.0.0.1",
"ident": "-",
"auth": "-",
"timestamp": "11/Dec/2013:00:01:45 -0800",
"verb": "GET",
"request": "/xampp/status.php",
"httpversion": "1.1",
"response": "200",
"bytes": "3891",
"referrer": "\"http://cadenza/xampp/navi.php\"",
"agent": "\"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:25.0) Gecko/20100101 Firefox/25.0\""
}
```
This is looking better, but notice we have a `timestamp` and `@timestamp` field with different values. When this event is encoded within a sink, we'll use the wrong timestamp.
This should be enough to demonstrate the awkwardness of this approach.
## Proposals
Below are a couple of proposals that have been discussed. As part of the RFC you'll need to choose the best approach and propose it.
### Vector metadata namespace
Instead of pulluting the user's namespace with Vector specific fields, `timestamp` and `message` in our example above, we could shove them in a Vector specific namespace:
```json
{
"_vector": {
"timestamp": "...",
"host": "..."
},
"message": "..."
}
```
This solves the key clashing issues in that we are no longer polluting the user's namespace.
### `raw` metadata key
In addition the the above, we could also move raw data into a specific `raw` key:
```json
{
"_vector": {
"timestamp": "...",
"host": "...",
"raw": "..."
}
}
```
This strikes me as cleaner and much more flexible:
1. We retain the raw data which I'm sure is useful in some use cases.
2. We know if the event is explicitly structured or not. In the `tcp` -> `tcp` pipeline we can cleanly pass this data through.
## Alternatives & Prior Art
It is worth exploring Splunk forwarder's approach to this problem. From my understanding, they use a root-level `_raw` key that gets removed once the data is parsed. You can see this in their docs:
> If events do not have a `_raw` field, they'll be serialized to JSON prior to being sent.
## Outstanding questions
1. Even though we solved the problem of polluting the user's namespace, how would Vector know which `timestamp` key to use within each sink? Could the user tell us this through configuration? Hint: we'll need some sort of schema knowledge that tells us where to look for fields.
2. How do we prevent the `_vector` metadata key from being encoded? Ex: we could default the sink-level `encoding.except_fields` to `["_vector"]`, or we could hard code ignoring this when we encode events.
3. What should we do with all of the `*_key` options across our sources and sinks?
4. How do we preserve backward compatibility?
|
1.0
|
Schema metadata RFC - As a first step towards supporting various schemas, we want to shift the event metadata into a Vector specific namespace. This will solve a number of awkward siutations where Vector's metadata clashes with the user's schema.
## Examples
### Transitioning from Logstash
Let's look at a simple example where a user is replacing Logstash with Vector. Vector would receive data from upstream beats over TCP in the following format:
```json
{
"message": "127.0.0.1 - - [11/Dec/2013:00:01:45 -0800] \"GET /xampp/status.php HTTP/1.1\" 200 3891 \"http://cadenza/xampp/navi.php\" \"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:25.0) Gecko/20100101 Firefox/25.0\"",
"@timestamp": "2013-12-11T08:01:45.000Z",
"@version": "1",
"host": "cadenza",
"clientip": "127.0.0.1",
"ident": "-",
"auth": "-",
"timestamp": "11/Dec/2013:00:01:45 -0800",
"verb": "GET",
"request": "/xampp/status.php",
"httpversion": "1.1",
"response": "200",
"bytes": "3891",
"referrer": "\"http://cadenza/xampp/navi.php\"",
"agent": "\"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:25.0) Gecko/20100101 Firefox/25.0\""
}
```
Here we can see that the event is already enriched with metadata. When the event leaves the Vector `socket` source it'll be formatted as such:
```json
{
"timestamp": "...",
"host": "...",
"message": "{\n\"message\": \"127.0.0.1 - - [11/Dec/2013:00:01:45 -0800] \"GET /xampp/status.php HTTP/1.1\" 200 3891 \"http://cadenza/xampp/navi.php\" \"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:25.0) Gecko/20100101 Firefox/25.0\"\",\n\"@timestamp\": \"2013-12-11T08:01:45.000Z\",\n\"@version\": \"1\",\n\"host\": \"cadenza\",\n\"clientip\": \"127.0.0.1\",\n\"ident\": \"-\",\n\"auth\": \"-\",\n\"timestamp\": \"11/Dec/2013:00:01:45 -0800\",\n\"verb\": \"GET\",\n\"request\": \"/xampp/status.php\",\n\"httpversion\": \"1.1\",\n\"response\": \"200\",\n\"bytes\": \"3891\",\n\"referrer\": \"\"http://cadenza/xampp/navi.php\"\",\n\"agent\": \"\"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:25.0) Gecko/20100101 Firefox/25.0\"\"\n}\n"
}
```
Right off the bat this is awkward since we've constructed an event that does not resemble what they are expecting. To solve this the user must run the event through the `json_parser` which would result in:
```json
{
"timestamp": "...",
"message": "127.0.0.1 - - [11/Dec/2013:00:01:45 -0800] \"GET /xampp/status.php HTTP/1.1\" 200 3891 \"http://cadenza/xampp/navi.php\" \"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:25.0) Gecko/20100101 Firefox/25.0\"",
"@timestamp": "2013-12-11T08:01:45.000Z",
"@version": "1",
"host": "cadenza",
"clientip": "127.0.0.1",
"ident": "-",
"auth": "-",
"timestamp": "11/Dec/2013:00:01:45 -0800",
"verb": "GET",
"request": "/xampp/status.php",
"httpversion": "1.1",
"response": "200",
"bytes": "3891",
"referrer": "\"http://cadenza/xampp/navi.php\"",
"agent": "\"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:25.0) Gecko/20100101 Firefox/25.0\""
}
```
This is looking better, but notice we have a `timestamp` and `@timestamp` field with different values. When this event is encoded within a sink, we'll use the wrong timestamp.
This should be enough to demonstrate the awkwardness of this approach.
## Proposals
Below are a couple of proposals that have been discussed. As part of the RFC you'll need to choose the best approach and propose it.
### Vector metadata namespace
Instead of pulluting the user's namespace with Vector specific fields, `timestamp` and `message` in our example above, we could shove them in a Vector specific namespace:
```json
{
"_vector": {
"timestamp": "...",
"host": "..."
},
"message": "..."
}
```
This solves the key clashing issues in that we are no longer polluting the user's namespace.
### `raw` metadata key
In addition the the above, we could also move raw data into a specific `raw` key:
```json
{
"_vector": {
"timestamp": "...",
"host": "...",
"raw": "..."
}
}
```
This strikes me as cleaner and much more flexible:
1. We retain the raw data which I'm sure is useful in some use cases.
2. We know if the event is explicitly structured or not. In the `tcp` -> `tcp` pipeline we can cleanly pass this data through.
## Alternatives & Prior Art
It is worth exploring Splunk forwarder's approach to this problem. From my understanding, they use a root-level `_raw` key that gets removed once the data is parsed. You can see this in their docs:
> If events do not have a `_raw` field, they'll be serialized to JSON prior to being sent.
## Outstanding questions
1. Even though we solved the problem of polluting the user's namespace, how would Vector know which `timestamp` key to use within each sink? Could the user tell us this through configuration? Hint: we'll need some sort of schema knowledge that tells us where to look for fields.
2. How do we prevent the `_vector` metadata key from being encoded? Ex: we could default the sink-level `encoding.except_fields` to `["_vector"]`, or we could hard code ignoring this when we encode events.
3. What should we do with all of the `*_key` options across our sources and sinks?
4. How do we preserve backward compatibility?
|
process
|
schema metadata rfc as a first step towards supporting various schemas we want to shift the event metadata into a vector specific namespace this will solve a number of awkward siutations where vector s metadata clashes with the user s schema examples transitioning from logstash let s look at a simple example where a user is replacing logstash with vector vector would receive data from upstream beats over tcp in the following format json message get xampp status php http mozilla macintosh intel mac os x rv gecko firefox timestamp version host cadenza clientip ident auth timestamp dec verb get request xampp status php httpversion response bytes referrer agent mozilla macintosh intel mac os x rv gecko firefox here we can see that the event is already enriched with metadata when the event leaves the vector socket source it ll be formatted as such json timestamp host message n message get xampp status php http mozilla macintosh intel mac os x rv gecko firefox n timestamp n version n host cadenza n clientip n ident n auth n timestamp dec n verb get n request xampp status php n httpversion n response n bytes n referrer mozilla macintosh intel mac os x rv gecko firefox n n right off the bat this is awkward since we ve constructed an event that does not resemble what they are expecting to solve this the user must run the event through the json parser which would result in json timestamp message get xampp status php http mozilla macintosh intel mac os x rv gecko firefox timestamp version host cadenza clientip ident auth timestamp dec verb get request xampp status php httpversion response bytes referrer agent mozilla macintosh intel mac os x rv gecko firefox this is looking better but notice we have a timestamp and timestamp field with different values when this event is encoded within a sink we ll use the wrong timestamp this should be enough to demonstrate the awkwardness of this approach proposals below are a couple of proposals that have been discussed as part of the rfc you ll need to choose the best approach and propose it vector metadata namespace instead of pulluting the user s namespace with vector specific fields timestamp and message in our example above we could shove them in a vector specific namespace json vector timestamp host message this solves the key clashing issues in that we are no longer polluting the user s namespace raw metadata key in addition the the above we could also move raw data into a specific raw key json vector timestamp host raw this strikes me as cleaner and much more flexible we retain the raw data which i m sure is useful in some use cases we know if the event is explicitly structured or not in the tcp tcp pipeline we can cleanly pass this data through alternatives prior art it is worth exploring splunk forwarder s approach to this problem from my understanding they use a root level raw key that gets removed once the data is parsed you can see this in their docs if events do not have a raw field they ll be serialized to json prior to being sent outstanding questions even though we solved the problem of polluting the user s namespace how would vector know which timestamp key to use within each sink could the user tell us this through configuration hint we ll need some sort of schema knowledge that tells us where to look for fields how do we prevent the vector metadata key from being encoded ex we could default the sink level encoding except fields to or we could hard code ignoring this when we encode events what should we do with all of the key options across our sources and sinks how do we preserve backward compatibility
| 1
|
1,576
| 4,167,480,332
|
IssuesEvent
|
2016-06-20 09:40:59
|
e-government-ua/iBP
|
https://api.github.com/repos/e-government-ua/iBP
|
closed
|
Ірпінь - Видача архівних копій рішень
|
In process of testing in work test
|
контактна особа:
Карєв Костянтин - управляющий делами мерии iispolcom@gmail.com +38 066 519 36 12 Белоконь Виктор cigetsoftware@gmail.com +380 (66) 156-89-17
|
1.0
|
Ірпінь - Видача архівних копій рішень - контактна особа:
Карєв Костянтин - управляющий делами мерии iispolcom@gmail.com +38 066 519 36 12 Белоконь Виктор cigetsoftware@gmail.com +380 (66) 156-89-17
|
process
|
ірпінь видача архівних копій рішень контактна особа карєв костянтин управляющий делами мерии iispolcom gmail com белоконь виктор cigetsoftware gmail com
| 1
|
11,311
| 14,114,969,215
|
IssuesEvent
|
2020-11-07 18:29:42
|
allinurl/goaccess
|
https://api.github.com/repos/allinurl/goaccess
|
closed
|
Duplicated request entries on "Requested Files" panel
|
log-processing question
|
Hello! I'm currently trying to automate the report generation for a project which contains several deployed nodes, these nodes write to different logs, and I'm generating the report for those logs. Each of these logs relates to a day of accesses and they are rotated daily around 3AM.
```bash
# Concatenate log files into a single file
zcat -f $LOGS | sort -k $SORT > $PARSED_LOG
# Process log variations
bash $BASEDIR/process-log-variations.sh $PARSED_LOG
# Import log data into BTREE databases
goaccess --process-and-exit -p $conf $PARSED_LOG
# Generate HTML from BTREE databases
goaccess -p $conf -o $REPDIR/report.html
```
My script receives several log files and concatenates them together, sorts them by the date field, and then using SED removes variation fields, such as IDs, Hashes, and others from the requests URL replacing them with the word "$var". A single log file is generated from this process which I then feed to GoAcess, first persisting the data and then updating the report HTML with data from the last log file.
The problem is that, after loading 4/5 days of logs, in the "Requested Files" panel, the behavior in the following image happens:
As you can see, there are several "GET /api/auth/token" when only one should be appearing. Does anyone know why this happen? Is it a bug or am I doing something wrong?
|
1.0
|
Duplicated request entries on "Requested Files" panel - Hello! I'm currently trying to automate the report generation for a project which contains several deployed nodes, these nodes write to different logs, and I'm generating the report for those logs. Each of these logs relates to a day of accesses and they are rotated daily around 3AM.
```bash
# Concatenate log files into a single file
zcat -f $LOGS | sort -k $SORT > $PARSED_LOG
# Process log variations
bash $BASEDIR/process-log-variations.sh $PARSED_LOG
# Import log data into BTREE databases
goaccess --process-and-exit -p $conf $PARSED_LOG
# Generate HTML from BTREE databases
goaccess -p $conf -o $REPDIR/report.html
```
My script receives several log files and concatenates them together, sorts them by the date field, and then using SED removes variation fields, such as IDs, Hashes, and others from the requests URL replacing them with the word "$var". A single log file is generated from this process which I then feed to GoAcess, first persisting the data and then updating the report HTML with data from the last log file.
The problem is that, after loading 4/5 days of logs, in the "Requested Files" panel, the behavior in the following image happens:
As you can see, there are several "GET /api/auth/token" when only one should be appearing. Does anyone know why this happen? Is it a bug or am I doing something wrong?
|
process
|
duplicated request entries on requested files panel hello i m currently trying to automate the report generation for a project which contains several deployed nodes these nodes write to different logs and i m generating the report for those logs each of these logs relates to a day of accesses and they are rotated daily around bash concatenate log files into a single file zcat f logs sort k sort parsed log process log variations bash basedir process log variations sh parsed log import log data into btree databases goaccess process and exit p conf parsed log generate html from btree databases goaccess p conf o repdir report html my script receives several log files and concatenates them together sorts them by the date field and then using sed removes variation fields such as ids hashes and others from the requests url replacing them with the word var a single log file is generated from this process which i then feed to goacess first persisting the data and then updating the report html with data from the last log file the problem is that after loading days of logs in the requested files panel the behavior in the following image happens as you can see there are several get api auth token when only one should be appearing does anyone know why this happen is it a bug or am i doing something wrong
| 1
|
368,264
| 10,869,006,330
|
IssuesEvent
|
2019-11-15 06:08:07
|
StrangeLoopGames/EcoIssues
|
https://api.github.com/repos/StrangeLoopGames/EcoIssues
|
closed
|
[0.9.0 staging-1234] Bank account selection in a bank glitch
|
Medium Priority
|
in 8.3 it was like that (just click on the name for switching)
But now you will get history window with that.
It should just switch accounts,
|
1.0
|
[0.9.0 staging-1234] Bank account selection in a bank glitch - in 8.3 it was like that (just click on the name for switching)
But now you will get history window with that.
It should just switch accounts,
|
non_process
|
bank account selection in a bank glitch in it was like that just click on the name for switching but now you will get history window with that it should just switch accounts
| 0
|
14,568
| 17,691,937,947
|
IssuesEvent
|
2021-08-24 11:05:06
|
qgis/QGIS
|
https://api.github.com/repos/qgis/QGIS
|
closed
|
Polygonize algorithm outputs only NULL values in attribute table
|
Feedback Processing Bug
|
### What is the bug or the crash?
When running the Polygonize algorithm on a line layer with the option Keep Fields, the fields are added to the result but the table only contains NULL values. Tested on 3.21, 3.20 and 3.16 and confirmed by someone else.
### Steps to reproduce the issue
1. Open line layer
2. Processing > Polygonize (the QGIS algorithm)
3. Choose line layer
4. Check "Keep fields"
5. Run
6. Open attribute table of the result
### Versions
3.16, 3.20, 3.21
### Additional context
Algorithm log:
QGIS version: 3.21.0-Master
QGIS code revision: d16d76155e
Qt version: 5.12.8
Python version: 3.8.10
GDAL version: 3.0.4
GEOS version: 3.8.0-CAPI-1.13.1
PROJ version: Rel. 6.3.1, February 10th, 2020
Processing algorithm…
Algorithm 'Polygonize' starting…
Input parameters:
{ 'INPUT' : '/home/raymond/tmp/range_lines.gpkg|layername=range_lines', 'KEEP_FIELDS' : True, 'OUTPUT' : 'ogr:dbname=\'/home/raymond/tmp/range_polys.gpkg\' table=\"output\" (geom)' }
Collecting lines…
Noding lines…
Polygonizing…
Execution completed in 0.09 seconds
Results:
{'NUM_POLYGONS': 5,
'OUTPUT': '/home/raymond/tmp/range_polys.gpkg|layername=output'}
Loading resulting layers
Algorithm 'Polygonize' finished
|
1.0
|
Polygonize algorithm outputs only NULL values in attribute table - ### What is the bug or the crash?
When running the Polygonize algorithm on a line layer with the option Keep Fields, the fields are added to the result but the table only contains NULL values. Tested on 3.21, 3.20 and 3.16 and confirmed by someone else.
### Steps to reproduce the issue
1. Open line layer
2. Processing > Polygonize (the QGIS algorithm)
3. Choose line layer
4. Check "Keep fields"
5. Run
6. Open attribute table of the result
### Versions
3.16, 3.20, 3.21
### Additional context
Algorithm log:
QGIS version: 3.21.0-Master
QGIS code revision: d16d76155e
Qt version: 5.12.8
Python version: 3.8.10
GDAL version: 3.0.4
GEOS version: 3.8.0-CAPI-1.13.1
PROJ version: Rel. 6.3.1, February 10th, 2020
Processing algorithm…
Algorithm 'Polygonize' starting…
Input parameters:
{ 'INPUT' : '/home/raymond/tmp/range_lines.gpkg|layername=range_lines', 'KEEP_FIELDS' : True, 'OUTPUT' : 'ogr:dbname=\'/home/raymond/tmp/range_polys.gpkg\' table=\"output\" (geom)' }
Collecting lines…
Noding lines…
Polygonizing…
Execution completed in 0.09 seconds
Results:
{'NUM_POLYGONS': 5,
'OUTPUT': '/home/raymond/tmp/range_polys.gpkg|layername=output'}
Loading resulting layers
Algorithm 'Polygonize' finished
|
process
|
polygonize algorithm outputs only null values in attribute table what is the bug or the crash when running the polygonize algorithm on a line layer with the option keep fields the fields are added to the result but the table only contains null values tested on and and confirmed by someone else steps to reproduce the issue open line layer processing polygonize the qgis algorithm choose line layer check keep fields run open attribute table of the result versions additional context algorithm log qgis version master qgis code revision qt version python version gdal version geos version capi proj version rel february processing algorithm… algorithm polygonize starting… input parameters input home raymond tmp range lines gpkg layername range lines keep fields true output ogr dbname home raymond tmp range polys gpkg table output geom collecting lines… noding lines… polygonizing… execution completed in seconds results num polygons output home raymond tmp range polys gpkg layername output loading resulting layers algorithm polygonize finished
| 1
|
819,997
| 30,757,359,867
|
IssuesEvent
|
2023-07-29 08:15:28
|
brain-link/scanhub-ui
|
https://api.github.com/repos/brain-link/scanhub-ui
|
closed
|
Full screen sequence view
|
priority: high type: feature request
|
Decouple the sequence viewer from the exam-tree view. Plot can be accessed through a job, if a sequence was uploaded/selected and sequence is valid (can be compiled).
Connected to the following issue: https://github.com/brain-link/scanhub-ui/issues/5
|
1.0
|
Full screen sequence view - Decouple the sequence viewer from the exam-tree view. Plot can be accessed through a job, if a sequence was uploaded/selected and sequence is valid (can be compiled).
Connected to the following issue: https://github.com/brain-link/scanhub-ui/issues/5
|
non_process
|
full screen sequence view decouple the sequence viewer from the exam tree view plot can be accessed through a job if a sequence was uploaded selected and sequence is valid can be compiled connected to the following issue
| 0
|
8,236
| 11,417,545,891
|
IssuesEvent
|
2020-02-03 00:03:03
|
parcel-bundler/parcel
|
https://api.github.com/repos/parcel-bundler/parcel
|
closed
|
How to resolve Sass url()?
|
:grey_question: Question CSS Preprocessing Stale
|
<!---
Thanks for filing an issue 😄 ! Before you submit, please read the following:
Search open/closed issues before submitting since someone might have asked the same thing before!
-->
# ❔ Question
<!--- Provide your question here -->
I'm using parcel-bundler in a Node package to bundle a group of SCSS files. Using version 1.9.7, I had no issues resolving `url()` calls. Upon upgrading, however, I receive an error: `Error: ENOENT: no such file or directory`.
I noticed that in [1.10.0](https://github.com/parcel-bundler/parcel/pull/1909), URL resolving was moved to postcss.
How can I resolve calls to `url()` using the current versions of parcel-bundler?
## 🔦 Context
<!--- How has this issue affected you? What are you trying to accomplish? -->
I was trying to bundle a group of SCSS files for output to a separate repository. The error comes in when I `@import` a stylesheet from a different package. This wasn't an issue before.
<!--- Providing context helps us come up with a solution that is most useful in the real world -->
## 💻 Code Sample
<!-- If you are seeing an error, please provide a code repository, gist or sample files to reproduce the issue -->
```scss
background: url(#{$pswp__assets-path}default-skin.png) 0 0 no-repeat;
```
`$pswp__assets-path` is set currently to an empty string, so this should resolve to url(default-skin.png).
## 🌍 Your Environment
<!--- Include as many relevant details about the environment you are using -->
| Software | Version(s) |
| ---------------- | ---------- |
| Parcel |
| Node |
| npm/Yarn |
| Operating System |
<!-- Love parcel? Please consider supporting our collective:
👉 https://opencollective.com/parcel/donate -->
|
1.0
|
How to resolve Sass url()? - <!---
Thanks for filing an issue 😄 ! Before you submit, please read the following:
Search open/closed issues before submitting since someone might have asked the same thing before!
-->
# ❔ Question
<!--- Provide your question here -->
I'm using parcel-bundler in a Node package to bundle a group of SCSS files. Using version 1.9.7, I had no issues resolving `url()` calls. Upon upgrading, however, I receive an error: `Error: ENOENT: no such file or directory`.
I noticed that in [1.10.0](https://github.com/parcel-bundler/parcel/pull/1909), URL resolving was moved to postcss.
How can I resolve calls to `url()` using the current versions of parcel-bundler?
## 🔦 Context
<!--- How has this issue affected you? What are you trying to accomplish? -->
I was trying to bundle a group of SCSS files for output to a separate repository. The error comes in when I `@import` a stylesheet from a different package. This wasn't an issue before.
<!--- Providing context helps us come up with a solution that is most useful in the real world -->
## 💻 Code Sample
<!-- If you are seeing an error, please provide a code repository, gist or sample files to reproduce the issue -->
```scss
background: url(#{$pswp__assets-path}default-skin.png) 0 0 no-repeat;
```
`$pswp__assets-path` is set currently to an empty string, so this should resolve to url(default-skin.png).
## 🌍 Your Environment
<!--- Include as many relevant details about the environment you are using -->
| Software | Version(s) |
| ---------------- | ---------- |
| Parcel |
| Node |
| npm/Yarn |
| Operating System |
<!-- Love parcel? Please consider supporting our collective:
👉 https://opencollective.com/parcel/donate -->
|
process
|
how to resolve sass url thanks for filing an issue 😄 before you submit please read the following search open closed issues before submitting since someone might have asked the same thing before ❔ question i m using parcel bundler in a node package to bundle a group of scss files using version i had no issues resolving url calls upon upgrading however i receive an error error enoent no such file or directory i noticed that in url resolving was moved to postcss how can i resolve calls to url using the current versions of parcel bundler 🔦 context i was trying to bundle a group of scss files for output to a separate repository the error comes in when i import a stylesheet from a different package this wasn t an issue before 💻 code sample scss background url pswp assets path default skin png no repeat pswp assets path is set currently to an empty string so this should resolve to url default skin png 🌍 your environment software version s parcel node npm yarn operating system love parcel please consider supporting our collective 👉
| 1
|
20,764
| 27,495,141,569
|
IssuesEvent
|
2023-03-05 03:19:24
|
open-telemetry/opentelemetry-collector
|
https://api.github.com/repos/open-telemetry/opentelemetry-collector
|
closed
|
Authentication processor - tech debt from the review
|
enhancement Stale priority:p3 release:after-ga area:processor
|
During the review for the authentication processor PRs, the following items came up:
1. We should consider renaming `attribute` to something else, possibly `header`, although future receivers might not be HTTP-based at all. Context: https://github.com/open-telemetry/opentelemetry-collector/pull/1807#discussion_r492377673
1. Move `internal/auth` to `config/configauth/internal`. Context: https://github.com/open-telemetry/opentelemetry-collector/pull/1808#discussion_r491188522
|
1.0
|
Authentication processor - tech debt from the review - During the review for the authentication processor PRs, the following items came up:
1. We should consider renaming `attribute` to something else, possibly `header`, although future receivers might not be HTTP-based at all. Context: https://github.com/open-telemetry/opentelemetry-collector/pull/1807#discussion_r492377673
1. Move `internal/auth` to `config/configauth/internal`. Context: https://github.com/open-telemetry/opentelemetry-collector/pull/1808#discussion_r491188522
|
process
|
authentication processor tech debt from the review during the review for the authentication processor prs the following items came up we should consider renaming attribute to something else possibly header although future receivers might not be http based at all context move internal auth to config configauth internal context
| 1
|
13,147
| 15,570,494,787
|
IssuesEvent
|
2021-03-17 02:42:07
|
fluent/fluent-bit
|
https://api.github.com/repos/fluent/fluent-bit
|
closed
|
SUSE has '/usr/lib/systemd/system' but not '/lib/systemd/system'
|
Stale bug fixed waiting-for-user work-in-process
|
https://github.com/fluent/fluent-bit/blob/42f97274a0a896f1e5e20a9ced18bebc90294788/src/CMakeLists.txt#L383
This will not install fluent-bit.service. As in SUSE it doesn't have '/lib/systemd/system'
|
1.0
|
SUSE has '/usr/lib/systemd/system' but not '/lib/systemd/system' - https://github.com/fluent/fluent-bit/blob/42f97274a0a896f1e5e20a9ced18bebc90294788/src/CMakeLists.txt#L383
This will not install fluent-bit.service. As in SUSE it doesn't have '/lib/systemd/system'
|
process
|
suse has usr lib systemd system but not lib systemd system this will not install fluent bit service as in suse it doesn t have lib systemd system
| 1
|
3,473
| 6,552,146,605
|
IssuesEvent
|
2017-09-05 17:09:28
|
brucemiller/LaTeXML
|
https://api.github.com/repos/brucemiller/LaTeXML
|
closed
|
LaTeXML positions equation numbers using absolute positioning
|
postprocessing question
|
Simple latex example from the web
http://www.electronics.oulu.fi/latex/examples/example_1/
and ePub generated under macOS 10.12.4 with calibre 2.82.0 using
latexml --dest=example1.xml example1.tex
latexmlpost -dest=example1.html example1.xml
/Applications/calibre.app/Contents/MacOS/ebook-convert example1.html example1.epub --language en --no-default-epub-cover
In the html, the (1) for the equation is in the correct place
but in the ePub when viewed in iBooks version 1.9,
the (1) ends up on the following page.
### Submitted the above as a bug to calibre but this was their response: ###
I doubt very much this has anything to do with conversion. Most likely,
latexml positions equation numbers using absolute positioning, that kind
of thing will break in multipage displays like on iBooks. In general, I
highly doubt that the output of latexml is actually reflowable, you
might have better results with using mathjax instead, for example,
https://manual.calibre-ebook.com/typesetting_math.html
While this currently works only in the calibre ebook viewer, in calibre
3.0 calibre will also have an in browser viewer so it will work in any
(modern) browser.
There also may be options you can feed to latexml to make its output
more reflowable -- but as I dont use it, I can't help you with that.
|
1.0
|
LaTeXML positions equation numbers using absolute positioning - Simple latex example from the web
http://www.electronics.oulu.fi/latex/examples/example_1/
and ePub generated under macOS 10.12.4 with calibre 2.82.0 using
latexml --dest=example1.xml example1.tex
latexmlpost -dest=example1.html example1.xml
/Applications/calibre.app/Contents/MacOS/ebook-convert example1.html example1.epub --language en --no-default-epub-cover
In the html, the (1) for the equation is in the correct place
but in the ePub when viewed in iBooks version 1.9,
the (1) ends up on the following page.
### Submitted the above as a bug to calibre but this was their response: ###
I doubt very much this has anything to do with conversion. Most likely,
latexml positions equation numbers using absolute positioning, that kind
of thing will break in multipage displays like on iBooks. In general, I
highly doubt that the output of latexml is actually reflowable, you
might have better results with using mathjax instead, for example,
https://manual.calibre-ebook.com/typesetting_math.html
While this currently works only in the calibre ebook viewer, in calibre
3.0 calibre will also have an in browser viewer so it will work in any
(modern) browser.
There also may be options you can feed to latexml to make its output
more reflowable -- but as I dont use it, I can't help you with that.
|
process
|
latexml positions equation numbers using absolute positioning simple latex example from the web and epub generated under macos with calibre using latexml dest xml tex latexmlpost dest html xml applications calibre app contents macos ebook convert html epub language en no default epub cover in the html the for the equation is in the correct place but in the epub when viewed in ibooks version the ends up on the following page submitted the above as a bug to calibre but this was their response i doubt very much this has anything to do with conversion most likely latexml positions equation numbers using absolute positioning that kind of thing will break in multipage displays like on ibooks in general i highly doubt that the output of latexml is actually reflowable you might have better results with using mathjax instead for example while this currently works only in the calibre ebook viewer in calibre calibre will also have an in browser viewer so it will work in any modern browser there also may be options you can feed to latexml to make its output more reflowable but as i dont use it i can t help you with that
| 1
|
15,666
| 19,847,151,844
|
IssuesEvent
|
2022-01-21 08:07:47
|
ooi-data/CE01ISSM-RID16-07-NUTNRB000-telemetered-nutnr_b_dcl_full_instrument
|
https://api.github.com/repos/ooi-data/CE01ISSM-RID16-07-NUTNRB000-telemetered-nutnr_b_dcl_full_instrument
|
opened
|
🛑 Processing failed: ValueError
|
process
|
## Overview
`ValueError` found in `processing_task` task during run ended on 2022-01-21T08:07:46.485863.
## Details
Flow name: `CE01ISSM-RID16-07-NUTNRB000-telemetered-nutnr_b_dcl_full_instrument`
Task name: `processing_task`
Error type: `ValueError`
Error message: not enough values to unpack (expected 3, got 0)
<details>
<summary>Traceback</summary>
```
Traceback (most recent call last):
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/ooi_harvester/processor/pipeline.py", line 165, in processing
final_path = finalize_data_stream(
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/ooi_harvester/processor/__init__.py", line 84, in finalize_data_stream
append_to_zarr(mod_ds, final_store, enc, logger=logger)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/ooi_harvester/processor/__init__.py", line 357, in append_to_zarr
_append_zarr(store, mod_ds)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/ooi_harvester/processor/utils.py", line 187, in _append_zarr
existing_arr.append(var_data.values)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/variable.py", line 519, in values
return _as_array_or_item(self._data)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/variable.py", line 259, in _as_array_or_item
data = np.asarray(data)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/array/core.py", line 1541, in __array__
x = self.compute()
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/base.py", line 288, in compute
(result,) = compute(self, traverse=False, **kwargs)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/base.py", line 571, in compute
results = schedule(dsk, keys, **kwargs)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/threaded.py", line 79, in get
results = get_async(
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/local.py", line 507, in get_async
raise_exception(exc, tb)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/local.py", line 315, in reraise
raise exc
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/local.py", line 220, in execute_task
result = _execute_task(task, data)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/core.py", line 119, in _execute_task
return func(*(_execute_task(a, cache) for a in args))
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/array/core.py", line 116, in getter
c = np.asarray(c)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/indexing.py", line 357, in __array__
return np.asarray(self.array, dtype=dtype)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/indexing.py", line 551, in __array__
self._ensure_cached()
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/indexing.py", line 548, in _ensure_cached
self.array = NumpyIndexingAdapter(np.asarray(self.array))
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/indexing.py", line 521, in __array__
return np.asarray(self.array, dtype=dtype)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/indexing.py", line 422, in __array__
return np.asarray(array[self.key], dtype=None)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/coding/variables.py", line 70, in __array__
return self.func(self.array)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/coding/variables.py", line 137, in _apply_mask
data = np.asarray(data, dtype=dtype)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/indexing.py", line 422, in __array__
return np.asarray(array[self.key], dtype=None)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/backends/zarr.py", line 73, in __getitem__
return array[key.tuple]
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/zarr/core.py", line 673, in __getitem__
return self.get_basic_selection(selection, fields=fields)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/zarr/core.py", line 798, in get_basic_selection
return self._get_basic_selection_nd(selection=selection, out=out,
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/zarr/core.py", line 841, in _get_basic_selection_nd
return self._get_selection(indexer=indexer, out=out, fields=fields)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/zarr/core.py", line 1135, in _get_selection
lchunk_coords, lchunk_selection, lout_selection = zip(*indexer)
ValueError: not enough values to unpack (expected 3, got 0)
```
</details>
|
1.0
|
🛑 Processing failed: ValueError - ## Overview
`ValueError` found in `processing_task` task during run ended on 2022-01-21T08:07:46.485863.
## Details
Flow name: `CE01ISSM-RID16-07-NUTNRB000-telemetered-nutnr_b_dcl_full_instrument`
Task name: `processing_task`
Error type: `ValueError`
Error message: not enough values to unpack (expected 3, got 0)
<details>
<summary>Traceback</summary>
```
Traceback (most recent call last):
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/ooi_harvester/processor/pipeline.py", line 165, in processing
final_path = finalize_data_stream(
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/ooi_harvester/processor/__init__.py", line 84, in finalize_data_stream
append_to_zarr(mod_ds, final_store, enc, logger=logger)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/ooi_harvester/processor/__init__.py", line 357, in append_to_zarr
_append_zarr(store, mod_ds)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/ooi_harvester/processor/utils.py", line 187, in _append_zarr
existing_arr.append(var_data.values)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/variable.py", line 519, in values
return _as_array_or_item(self._data)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/variable.py", line 259, in _as_array_or_item
data = np.asarray(data)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/array/core.py", line 1541, in __array__
x = self.compute()
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/base.py", line 288, in compute
(result,) = compute(self, traverse=False, **kwargs)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/base.py", line 571, in compute
results = schedule(dsk, keys, **kwargs)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/threaded.py", line 79, in get
results = get_async(
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/local.py", line 507, in get_async
raise_exception(exc, tb)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/local.py", line 315, in reraise
raise exc
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/local.py", line 220, in execute_task
result = _execute_task(task, data)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/core.py", line 119, in _execute_task
return func(*(_execute_task(a, cache) for a in args))
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/dask/array/core.py", line 116, in getter
c = np.asarray(c)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/indexing.py", line 357, in __array__
return np.asarray(self.array, dtype=dtype)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/indexing.py", line 551, in __array__
self._ensure_cached()
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/indexing.py", line 548, in _ensure_cached
self.array = NumpyIndexingAdapter(np.asarray(self.array))
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/indexing.py", line 521, in __array__
return np.asarray(self.array, dtype=dtype)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/indexing.py", line 422, in __array__
return np.asarray(array[self.key], dtype=None)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/coding/variables.py", line 70, in __array__
return self.func(self.array)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/coding/variables.py", line 137, in _apply_mask
data = np.asarray(data, dtype=dtype)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/indexing.py", line 422, in __array__
return np.asarray(array[self.key], dtype=None)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/backends/zarr.py", line 73, in __getitem__
return array[key.tuple]
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/zarr/core.py", line 673, in __getitem__
return self.get_basic_selection(selection, fields=fields)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/zarr/core.py", line 798, in get_basic_selection
return self._get_basic_selection_nd(selection=selection, out=out,
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/zarr/core.py", line 841, in _get_basic_selection_nd
return self._get_selection(indexer=indexer, out=out, fields=fields)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/zarr/core.py", line 1135, in _get_selection
lchunk_coords, lchunk_selection, lout_selection = zip(*indexer)
ValueError: not enough values to unpack (expected 3, got 0)
```
</details>
|
process
|
🛑 processing failed valueerror overview valueerror found in processing task task during run ended on details flow name telemetered nutnr b dcl full instrument task name processing task error type valueerror error message not enough values to unpack expected got traceback traceback most recent call last file srv conda envs notebook lib site packages ooi harvester processor pipeline py line in processing final path finalize data stream file srv conda envs notebook lib site packages ooi harvester processor init py line in finalize data stream append to zarr mod ds final store enc logger logger file srv conda envs notebook lib site packages ooi harvester processor init py line in append to zarr append zarr store mod ds file srv conda envs notebook lib site packages ooi harvester processor utils py line in append zarr existing arr append var data values file srv conda envs notebook lib site packages xarray core variable py line in values return as array or item self data file srv conda envs notebook lib site packages xarray core variable py line in as array or item data np asarray data file srv conda envs notebook lib site packages dask array core py line in array x self compute file srv conda envs notebook lib site packages dask base py line in compute result compute self traverse false kwargs file srv conda envs notebook lib site packages dask base py line in compute results schedule dsk keys kwargs file srv conda envs notebook lib site packages dask threaded py line in get results get async file srv conda envs notebook lib site packages dask local py line in get async raise exception exc tb file srv conda envs notebook lib site packages dask local py line in reraise raise exc file srv conda envs notebook lib site packages dask local py line in execute task result execute task task data file srv conda envs notebook lib site packages dask core py line in execute task return func execute task a cache for a in args file srv conda envs notebook lib site packages dask array core py line in getter c np asarray c file srv conda envs notebook lib site packages xarray core indexing py line in array return np asarray self array dtype dtype file srv conda envs notebook lib site packages xarray core indexing py line in array self ensure cached file srv conda envs notebook lib site packages xarray core indexing py line in ensure cached self array numpyindexingadapter np asarray self array file srv conda envs notebook lib site packages xarray core indexing py line in array return np asarray self array dtype dtype file srv conda envs notebook lib site packages xarray core indexing py line in array return np asarray array dtype none file srv conda envs notebook lib site packages xarray coding variables py line in array return self func self array file srv conda envs notebook lib site packages xarray coding variables py line in apply mask data np asarray data dtype dtype file srv conda envs notebook lib site packages xarray core indexing py line in array return np asarray array dtype none file srv conda envs notebook lib site packages xarray backends zarr py line in getitem return array file srv conda envs notebook lib site packages zarr core py line in getitem return self get basic selection selection fields fields file srv conda envs notebook lib site packages zarr core py line in get basic selection return self get basic selection nd selection selection out out file srv conda envs notebook lib site packages zarr core py line in get basic selection nd return self get selection indexer indexer out out fields fields file srv conda envs notebook lib site packages zarr core py line in get selection lchunk coords lchunk selection lout selection zip indexer valueerror not enough values to unpack expected got
| 1
|
94,942
| 27,334,826,823
|
IssuesEvent
|
2023-02-26 03:45:07
|
AVSLab/basilisk
|
https://api.github.com/repos/AVSLab/basilisk
|
closed
|
Fix Linux builds with `--opNav True`
|
bug build
|
Linux builds of Basilisk appear to be broken when the `opNav` flag is used due to a case sensitivity issue. A detailed log of the error is included below.
```
~/basilisk$ python3 conanfile.py --opNav True --vizInterface True --clean
python -m pip install --upgrade pip
Requirement already satisfied: pip in ./.venv/lib/python3.7/site-packages (23.0)
Configuring: use libstdc++11 by default
Checking conan configuration: Done
Auto-Generating Draft Modules... Done
Running this conan command:
python -m conans.conan install . --build=missing -s build_type=Release -if dist3/conan -o opNav=True -o vizInterface=True -o buildProject=True -o clean=True
Configuration:
[settings]
arch=x86_64
arch_build=x86_64
build_type=Release
compiler=gcc
compiler.libcxx=libstdc++11
compiler.version=7
os=Linux
os_build=Linux
[options]
buildProject=True
clean=True
opNav=True
vizInterface=True
[build_requires]
[env]
[conf]
tools.system.package_manager:mode=install
[...]
Installing (downloading, building) binaries...
[...]
opencv/4.1.2: Already installed!
[...]
CMake Error at cmake/usingOpenCV.cmake:1 (find_package):
By not providing "Findopencv.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "opencv", but
CMake did not find one.
Could not find a package configuration file provided by "opencv" with any
of the following names:
opencvConfig.cmake
opencv-config.cmake
Add the installation prefix of "opencv" to CMAKE_PREFIX_PATH or set
"opencv_DIR" to a directory containing one of the above files. If "opencv"
provides a separate development package or SDK, be sure it has been
installed.
Call Stack (most recent call first):
simulation/sensors/camera/Custom.cmake:1 (include)
CMakeLists.txt:336 (include)
CMakeLists.txt:565 (generate_package_targets)
-- Configuring incomplete, errors occurred!
See also "/home/andrew/basilisk/dist3/CMakeFiles/CMakeOutput.log".
ERROR: conanfile.py (Basilisk/2.1.7b0): Error in build() method, line 265
cmake.configure()
ConanException: Error 1 while executing cd '/home/andrew/basilisk/dist3' && cmake -G "Unix Makefiles" -DCMAKE_BUILD_TYPE="Release" -DCONAN_IN_LOCAL_CACHE="OFF" -DCONAN_COMPILER="gcc" -DCONAN_COMPILER_VERSION="7" -DCONAN_CXX_FLAGS="-m64" -DCONAN_SHARED_LINKER_FLAGS="-m64" -DCONAN_C_FLAGS="-m64" -DCMAKE_CXX_FLAGS="-m64" -DCMAKE_SHARED_LINKER_FLAGS="-m64" -DCMAKE_C_FLAGS="-m64" -DCONAN_LIBCXX="libstdc++11" -DCMAKE_INSTALL_PREFIX="/home/andrew/basilisk/package" -DCMAKE_INSTALL_BINDIR="bin" -DCMAKE_INSTALL_SBINDIR="bin" -DCMAKE_INSTALL_LIBEXECDIR="bin" -DCMAKE_INSTALL_LIBDIR="lib" -DCMAKE_INSTALL_INCLUDEDIR="include" -DCMAKE_INSTALL_OLDINCLUDEDIR="include" -DCMAKE_INSTALL_DATAROOTDIR="share" -DCMAKE_PREFIX_PATH="/home/andrew/basilisk/dist3/conan" -DCMAKE_MODULE_PATH="/home/andrew/basilisk/dist3/conan" -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY="ON" -DCONAN_EXPORTED="1" -DBUILD_OPNAV="True" -DBUILD_VIZINTERFACE="True" -DEXTERNAL_MODULES_PATH="" -DPYTHON_VERSION="3.7" -Wno-dev '/home/andrew/basilisk/src'
```
**To reproduce**
Steps to reproduce the behavior:
1. Follow documentation for a conventional Linux build
2. Run `python3 conanfile.py --opNav True --vizInterface True --clean`
3. See error.
**Expected behavior**
Basilisk builds as normal with the `camera` and other `opNav`-related modules
**Desktop (please complete the following information):**
- OS: Ubuntu
- Version 18.04
- Python version 3.7.15
Additional config info, such as my `conan` profile, is provided above.
**Additional context**
Per #184, this can be fixed with a change to the `src/cmake/usingOpenCV.cmake` file to reference `OpenCV` instead of `opencv`.
|
1.0
|
Fix Linux builds with `--opNav True` - Linux builds of Basilisk appear to be broken when the `opNav` flag is used due to a case sensitivity issue. A detailed log of the error is included below.
```
~/basilisk$ python3 conanfile.py --opNav True --vizInterface True --clean
python -m pip install --upgrade pip
Requirement already satisfied: pip in ./.venv/lib/python3.7/site-packages (23.0)
Configuring: use libstdc++11 by default
Checking conan configuration: Done
Auto-Generating Draft Modules... Done
Running this conan command:
python -m conans.conan install . --build=missing -s build_type=Release -if dist3/conan -o opNav=True -o vizInterface=True -o buildProject=True -o clean=True
Configuration:
[settings]
arch=x86_64
arch_build=x86_64
build_type=Release
compiler=gcc
compiler.libcxx=libstdc++11
compiler.version=7
os=Linux
os_build=Linux
[options]
buildProject=True
clean=True
opNav=True
vizInterface=True
[build_requires]
[env]
[conf]
tools.system.package_manager:mode=install
[...]
Installing (downloading, building) binaries...
[...]
opencv/4.1.2: Already installed!
[...]
CMake Error at cmake/usingOpenCV.cmake:1 (find_package):
By not providing "Findopencv.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "opencv", but
CMake did not find one.
Could not find a package configuration file provided by "opencv" with any
of the following names:
opencvConfig.cmake
opencv-config.cmake
Add the installation prefix of "opencv" to CMAKE_PREFIX_PATH or set
"opencv_DIR" to a directory containing one of the above files. If "opencv"
provides a separate development package or SDK, be sure it has been
installed.
Call Stack (most recent call first):
simulation/sensors/camera/Custom.cmake:1 (include)
CMakeLists.txt:336 (include)
CMakeLists.txt:565 (generate_package_targets)
-- Configuring incomplete, errors occurred!
See also "/home/andrew/basilisk/dist3/CMakeFiles/CMakeOutput.log".
ERROR: conanfile.py (Basilisk/2.1.7b0): Error in build() method, line 265
cmake.configure()
ConanException: Error 1 while executing cd '/home/andrew/basilisk/dist3' && cmake -G "Unix Makefiles" -DCMAKE_BUILD_TYPE="Release" -DCONAN_IN_LOCAL_CACHE="OFF" -DCONAN_COMPILER="gcc" -DCONAN_COMPILER_VERSION="7" -DCONAN_CXX_FLAGS="-m64" -DCONAN_SHARED_LINKER_FLAGS="-m64" -DCONAN_C_FLAGS="-m64" -DCMAKE_CXX_FLAGS="-m64" -DCMAKE_SHARED_LINKER_FLAGS="-m64" -DCMAKE_C_FLAGS="-m64" -DCONAN_LIBCXX="libstdc++11" -DCMAKE_INSTALL_PREFIX="/home/andrew/basilisk/package" -DCMAKE_INSTALL_BINDIR="bin" -DCMAKE_INSTALL_SBINDIR="bin" -DCMAKE_INSTALL_LIBEXECDIR="bin" -DCMAKE_INSTALL_LIBDIR="lib" -DCMAKE_INSTALL_INCLUDEDIR="include" -DCMAKE_INSTALL_OLDINCLUDEDIR="include" -DCMAKE_INSTALL_DATAROOTDIR="share" -DCMAKE_PREFIX_PATH="/home/andrew/basilisk/dist3/conan" -DCMAKE_MODULE_PATH="/home/andrew/basilisk/dist3/conan" -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY="ON" -DCONAN_EXPORTED="1" -DBUILD_OPNAV="True" -DBUILD_VIZINTERFACE="True" -DEXTERNAL_MODULES_PATH="" -DPYTHON_VERSION="3.7" -Wno-dev '/home/andrew/basilisk/src'
```
**To reproduce**
Steps to reproduce the behavior:
1. Follow documentation for a conventional Linux build
2. Run `python3 conanfile.py --opNav True --vizInterface True --clean`
3. See error.
**Expected behavior**
Basilisk builds as normal with the `camera` and other `opNav`-related modules
**Desktop (please complete the following information):**
- OS: Ubuntu
- Version 18.04
- Python version 3.7.15
Additional config info, such as my `conan` profile, is provided above.
**Additional context**
Per #184, this can be fixed with a change to the `src/cmake/usingOpenCV.cmake` file to reference `OpenCV` instead of `opencv`.
|
non_process
|
fix linux builds with opnav true linux builds of basilisk appear to be broken when the opnav flag is used due to a case sensitivity issue a detailed log of the error is included below basilisk conanfile py opnav true vizinterface true clean python m pip install upgrade pip requirement already satisfied pip in venv lib site packages configuring use libstdc by default checking conan configuration done auto generating draft modules done running this conan command python m conans conan install build missing s build type release if conan o opnav true o vizinterface true o buildproject true o clean true configuration arch arch build build type release compiler gcc compiler libcxx libstdc compiler version os linux os build linux buildproject true clean true opnav true vizinterface true tools system package manager mode install installing downloading building binaries opencv already installed cmake error at cmake usingopencv cmake find package by not providing findopencv cmake in cmake module path this project has asked cmake to find a package configuration file provided by opencv but cmake did not find one could not find a package configuration file provided by opencv with any of the following names opencvconfig cmake opencv config cmake add the installation prefix of opencv to cmake prefix path or set opencv dir to a directory containing one of the above files if opencv provides a separate development package or sdk be sure it has been installed call stack most recent call first simulation sensors camera custom cmake include cmakelists txt include cmakelists txt generate package targets configuring incomplete errors occurred see also home andrew basilisk cmakefiles cmakeoutput log error conanfile py basilisk error in build method line cmake configure conanexception error while executing cd home andrew basilisk cmake g unix makefiles dcmake build type release dconan in local cache off dconan compiler gcc dconan compiler version dconan cxx flags dconan shared linker flags dconan c flags dcmake cxx flags dcmake shared linker flags dcmake c flags dconan libcxx libstdc dcmake install prefix home andrew basilisk package dcmake install bindir bin dcmake install sbindir bin dcmake install libexecdir bin dcmake install libdir lib dcmake install includedir include dcmake install oldincludedir include dcmake install datarootdir share dcmake prefix path home andrew basilisk conan dcmake module path home andrew basilisk conan dcmake export no package registry on dconan exported dbuild opnav true dbuild vizinterface true dexternal modules path dpython version wno dev home andrew basilisk src to reproduce steps to reproduce the behavior follow documentation for a conventional linux build run conanfile py opnav true vizinterface true clean see error expected behavior basilisk builds as normal with the camera and other opnav related modules desktop please complete the following information os ubuntu version python version additional config info such as my conan profile is provided above additional context per this can be fixed with a change to the src cmake usingopencv cmake file to reference opencv instead of opencv
| 0
|
2,571
| 5,325,661,606
|
IssuesEvent
|
2017-02-15 00:32:36
|
jlm2017/jlm-video-subtitles
|
https://api.github.com/repos/jlm2017/jlm-video-subtitles
|
opened
|
[subtitles] [german] Il faut rompre avec ce monde pourri
|
Process: [0] Awaiting subtitles
|
# Video title
Il faut rompre avec ce monde pourri
# URL
https://www.youtube.com/watch?v=HMNwmW1BHRY&t=7s
# Youtube subtitles language
German
# Duration
17:20
# Subtitles URL
https://www.youtube.com/timedtext_editor?ui=hd&action_mde_edit_form=1&bl=vmp&v=HMNwmW1BHRY&tab=captions&lang=de&ref=player
|
1.0
|
[subtitles] [german] Il faut rompre avec ce monde pourri - # Video title
Il faut rompre avec ce monde pourri
# URL
https://www.youtube.com/watch?v=HMNwmW1BHRY&t=7s
# Youtube subtitles language
German
# Duration
17:20
# Subtitles URL
https://www.youtube.com/timedtext_editor?ui=hd&action_mde_edit_form=1&bl=vmp&v=HMNwmW1BHRY&tab=captions&lang=de&ref=player
|
process
|
il faut rompre avec ce monde pourri video title il faut rompre avec ce monde pourri url youtube subtitles language german duration subtitles url
| 1
|
19,315
| 25,467,776,634
|
IssuesEvent
|
2022-11-25 07:06:54
|
GoogleCloudPlatform/fda-mystudies
|
https://api.github.com/repos/GoogleCloudPlatform/fda-mystudies
|
closed
|
[Android] Getting 'You are offline' popup message when tried to signup in the mobile app
|
Bug P2 Android Process: Fixed Process: Tested QA Process: Tested dev
|
**Steps:**
1. Install the build
2. Open the app
3. Sign up for the app
4. Complete the sign up process and Verify, after navigating to study list screen
**AR:** Getting 'You are offline' popup message when tried to signup in the mobile app
**ER:** Study list should be loaded without any error's
**Note:**
1. Issue is observed intermittently
2. Issue is observed only in sign up flow
|
3.0
|
[Android] Getting 'You are offline' popup message when tried to signup in the mobile app - **Steps:**
1. Install the build
2. Open the app
3. Sign up for the app
4. Complete the sign up process and Verify, after navigating to study list screen
**AR:** Getting 'You are offline' popup message when tried to signup in the mobile app
**ER:** Study list should be loaded without any error's
**Note:**
1. Issue is observed intermittently
2. Issue is observed only in sign up flow
|
process
|
getting you are offline popup message when tried to signup in the mobile app steps install the build open the app sign up for the app complete the sign up process and verify after navigating to study list screen ar getting you are offline popup message when tried to signup in the mobile app er study list should be loaded without any error s note issue is observed intermittently issue is observed only in sign up flow
| 1
|
20,334
| 26,987,593,683
|
IssuesEvent
|
2023-02-09 17:13:54
|
metabase/metabase
|
https://api.github.com/repos/metabase/metabase
|
closed
|
[MongoDB] Timezone issue when using relative time filters
|
Type:Bug Priority:P2 Database/Mongo Querying/Processor .Correctness Misc/Timezones Difficulty:Medium .Backend
|
I am using data source as MongoDB, where I have `createdAt` in each document, it's of date type and is always in UTC (GMT +0) Timezone, I have configured Metabase accordingly to show me these values on IST, it's working as expected. Now the difference is when I set a filter on a specific date the count of rows is different from the one when I set relative date.
### _Note: In this example scenario current date is 31st Dec 2020 (Indian Standard Time)_
## Using on the specific date filter
I have set a data filter (On Specific Date) to 30th Dec 2020, then the count of rows is 45.
#### What went weird?
Everything seems fine, Data looks perfect as it should be.
## Using on a relative date filter
Now when I change the filter to Previous 1 Day (Do not include today), then the count of rows is 43.
#### What went weird?
1. I can see 2 records of 31st Dec as well. (I didn't select include today, also today has more data).
Those 2 extra records are: December 31, 2020, 2:22 AM, December 31, 2020, 1:44 AM
2. 4 records went missing, and those are:
i. December 30, 2020, 12:37 AM
ii. December 30, 2020, 12:58 AM
iii. December 30, 2020, 1:38 AM
iv. December 30, 2020, 1:45 AM
**Assumptions**
I think when using the relative time filter the query is not using the local timezone, the data has a difference of +05:30
### Severity
Low or Medium
### Metabase Diagnostic Info
```json
{
"browser-info": {
"language": "en-US",
"platform": "MacIntel",
"userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 11_1_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.88 Safari/537.36",
"vendor": "Google Inc."
},
"system-info": {
"file.encoding": "UTF-8",
"java.runtime.name": "OpenJDK Runtime Environment",
"java.runtime.version": "11.0.7+10",
"java.vendor": "AdoptOpenJDK",
"java.vendor.url": "https://adoptopenjdk.net/",
"java.version": "11.0.7",
"java.vm.name": "OpenJDK 64-Bit Server VM",
"java.vm.version": "11.0.7+10",
"os.name": "Linux",
"os.version": "4.19.0-0.bpo.11-amd64",
"user.language": "en",
"user.timezone": "Asia/Calcutta"
},
"metabase-info": {
"databases": [
"mongo",
"googleanalytics"
],
"hosting-env": "unknown",
"application-database": "postgres",
"application-database-details": {
"database": {
"name": "PostgreSQL",
"version": "13.1 (Debian 13.1-1.pgdg100+1)"
},
"jdbc-driver": {
"name": "PostgreSQL JDBC Driver",
"version": "42.2.8"
}
},
"run-mode": "prod",
"version": {
"date": "2020-12-17",
"tag": "v0.37.4",
"branch": "release-x.37.x",
"hash": "e0d5287"
},
"settings": {
"report-timezone": "UTC"
}
}
}
```
|
1.0
|
[MongoDB] Timezone issue when using relative time filters - I am using data source as MongoDB, where I have `createdAt` in each document, it's of date type and is always in UTC (GMT +0) Timezone, I have configured Metabase accordingly to show me these values on IST, it's working as expected. Now the difference is when I set a filter on a specific date the count of rows is different from the one when I set relative date.
### _Note: In this example scenario current date is 31st Dec 2020 (Indian Standard Time)_
## Using on the specific date filter
I have set a data filter (On Specific Date) to 30th Dec 2020, then the count of rows is 45.
#### What went weird?
Everything seems fine, Data looks perfect as it should be.
## Using on a relative date filter
Now when I change the filter to Previous 1 Day (Do not include today), then the count of rows is 43.
#### What went weird?
1. I can see 2 records of 31st Dec as well. (I didn't select include today, also today has more data).
Those 2 extra records are: December 31, 2020, 2:22 AM, December 31, 2020, 1:44 AM
2. 4 records went missing, and those are:
i. December 30, 2020, 12:37 AM
ii. December 30, 2020, 12:58 AM
iii. December 30, 2020, 1:38 AM
iv. December 30, 2020, 1:45 AM
**Assumptions**
I think when using the relative time filter the query is not using the local timezone, the data has a difference of +05:30
### Severity
Low or Medium
### Metabase Diagnostic Info
```json
{
"browser-info": {
"language": "en-US",
"platform": "MacIntel",
"userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 11_1_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.88 Safari/537.36",
"vendor": "Google Inc."
},
"system-info": {
"file.encoding": "UTF-8",
"java.runtime.name": "OpenJDK Runtime Environment",
"java.runtime.version": "11.0.7+10",
"java.vendor": "AdoptOpenJDK",
"java.vendor.url": "https://adoptopenjdk.net/",
"java.version": "11.0.7",
"java.vm.name": "OpenJDK 64-Bit Server VM",
"java.vm.version": "11.0.7+10",
"os.name": "Linux",
"os.version": "4.19.0-0.bpo.11-amd64",
"user.language": "en",
"user.timezone": "Asia/Calcutta"
},
"metabase-info": {
"databases": [
"mongo",
"googleanalytics"
],
"hosting-env": "unknown",
"application-database": "postgres",
"application-database-details": {
"database": {
"name": "PostgreSQL",
"version": "13.1 (Debian 13.1-1.pgdg100+1)"
},
"jdbc-driver": {
"name": "PostgreSQL JDBC Driver",
"version": "42.2.8"
}
},
"run-mode": "prod",
"version": {
"date": "2020-12-17",
"tag": "v0.37.4",
"branch": "release-x.37.x",
"hash": "e0d5287"
},
"settings": {
"report-timezone": "UTC"
}
}
}
```
|
process
|
timezone issue when using relative time filters i am using data source as mongodb where i have createdat in each document it s of date type and is always in utc gmt timezone i have configured metabase accordingly to show me these values on ist it s working as expected now the difference is when i set a filter on a specific date the count of rows is different from the one when i set relative date note in this example scenario current date is dec indian standard time using on the specific date filter i have set a data filter on specific date to dec then the count of rows is what went weird everything seems fine data looks perfect as it should be using on a relative date filter now when i change the filter to previous day do not include today then the count of rows is what went weird i can see records of dec as well i didn t select include today also today has more data those extra records are december am december am records went missing and those are i december am ii december am iii december am iv december am assumptions i think when using the relative time filter the query is not using the local timezone the data has a difference of severity low or medium metabase diagnostic info json browser info language en us platform macintel useragent mozilla macintosh intel mac os x applewebkit khtml like gecko chrome safari vendor google inc system info file encoding utf java runtime name openjdk runtime environment java runtime version java vendor adoptopenjdk java vendor url java version java vm name openjdk bit server vm java vm version os name linux os version bpo user language en user timezone asia calcutta metabase info databases mongo googleanalytics hosting env unknown application database postgres application database details database name postgresql version debian jdbc driver name postgresql jdbc driver version run mode prod version date tag branch release x x hash settings report timezone utc
| 1
|
1,247
| 3,784,773,482
|
IssuesEvent
|
2016-03-20 02:06:16
|
ViDA-NYU/genotet
|
https://api.github.com/repos/ViDA-NYU/genotet
|
opened
|
use one data path
|
data processing
|
Right now we have this in config
```
networkPath = .../genotet_data/network/
bindingPath = .../genotet_data/binding/
expressionPath = .../genotet_data/expression/
bigWigToWigPath = .../genotet_data/bigWigToWig
uploadPath = .../genotet_data/upload/
bedPath = .../genotet_data/bed/
mappingPath = .../genotet_data/mapping/
```
But it seems to me that this is getting over complicated. I suggest we just do
```
dataPath = .../genotet_data/
```
and then we control all the stuffs under this folder, put them in respective folders.
|
1.0
|
use one data path - Right now we have this in config
```
networkPath = .../genotet_data/network/
bindingPath = .../genotet_data/binding/
expressionPath = .../genotet_data/expression/
bigWigToWigPath = .../genotet_data/bigWigToWig
uploadPath = .../genotet_data/upload/
bedPath = .../genotet_data/bed/
mappingPath = .../genotet_data/mapping/
```
But it seems to me that this is getting over complicated. I suggest we just do
```
dataPath = .../genotet_data/
```
and then we control all the stuffs under this folder, put them in respective folders.
|
process
|
use one data path right now we have this in config networkpath genotet data network bindingpath genotet data binding expressionpath genotet data expression bigwigtowigpath genotet data bigwigtowig uploadpath genotet data upload bedpath genotet data bed mappingpath genotet data mapping but it seems to me that this is getting over complicated i suggest we just do datapath genotet data and then we control all the stuffs under this folder put them in respective folders
| 1
|
14,250
| 17,187,593,465
|
IssuesEvent
|
2021-07-16 06:00:50
|
qgis/QGIS
|
https://api.github.com/repos/qgis/QGIS
|
closed
|
Expression widget does not list fields when Selected features only is checked
|
Bug Processing
|
<!--
Bug fixing and feature development is a community responsibility, and not the responsibility of the QGIS project alone.
If this bug report or feature request is high-priority for you, we suggest engaging a QGIS developer or support organisation and financially sponsoring a fix
Checklist before submitting
- [ ] Search through existing issue reports and gis.stackexchange.com to check whether the issue already exists
- [ ] Test with a [clean new user profile](https://docs.qgis.org/testing/en/docs/user_manual/introduction/qgis_configuration.html?highlight=profile#working-with-user-profiles).
- [ ] Create a light and self-contained sample dataset and project file which demonstrates the issue
-->
**Describe the bug**
<!-- A clear and concise description of what the bug is. -->
In processing algorithms that use a `QgsProcessingParameterExpression`, the widget has a combobox populated with the available fields. If the *Selected features only* checkbox is checked, then the expression widget no longer shows the fields in the combobox.
**How to Reproduce**
- Load a vector layer with some features
- Run an algorithm that uses a `QgsProcessingParameterExpression`, for example *Order by expression*
- Click on the expression widget combobox button: the layer's fields are listed
- Go to the map canvas and select some features
- Back to the algorithm dialog, check *Selected features only*
- Click on the expression widget combobox button: the layer's fields are **not** listed
**QGIS and OS versions**
69faea8 on Debian testing
<!-- In the QGIS Help menu -> About, click in the table, Ctrl+A and then Ctrl+C. Finally paste here -->
<!-- Add any other context about the problem here. -->
|
1.0
|
Expression widget does not list fields when Selected features only is checked - <!--
Bug fixing and feature development is a community responsibility, and not the responsibility of the QGIS project alone.
If this bug report or feature request is high-priority for you, we suggest engaging a QGIS developer or support organisation and financially sponsoring a fix
Checklist before submitting
- [ ] Search through existing issue reports and gis.stackexchange.com to check whether the issue already exists
- [ ] Test with a [clean new user profile](https://docs.qgis.org/testing/en/docs/user_manual/introduction/qgis_configuration.html?highlight=profile#working-with-user-profiles).
- [ ] Create a light and self-contained sample dataset and project file which demonstrates the issue
-->
**Describe the bug**
<!-- A clear and concise description of what the bug is. -->
In processing algorithms that use a `QgsProcessingParameterExpression`, the widget has a combobox populated with the available fields. If the *Selected features only* checkbox is checked, then the expression widget no longer shows the fields in the combobox.
**How to Reproduce**
- Load a vector layer with some features
- Run an algorithm that uses a `QgsProcessingParameterExpression`, for example *Order by expression*
- Click on the expression widget combobox button: the layer's fields are listed
- Go to the map canvas and select some features
- Back to the algorithm dialog, check *Selected features only*
- Click on the expression widget combobox button: the layer's fields are **not** listed
**QGIS and OS versions**
69faea8 on Debian testing
<!-- In the QGIS Help menu -> About, click in the table, Ctrl+A and then Ctrl+C. Finally paste here -->
<!-- Add any other context about the problem here. -->
|
process
|
expression widget does not list fields when selected features only is checked bug fixing and feature development is a community responsibility and not the responsibility of the qgis project alone if this bug report or feature request is high priority for you we suggest engaging a qgis developer or support organisation and financially sponsoring a fix checklist before submitting search through existing issue reports and gis stackexchange com to check whether the issue already exists test with a create a light and self contained sample dataset and project file which demonstrates the issue describe the bug in processing algorithms that use a qgsprocessingparameterexpression the widget has a combobox populated with the available fields if the selected features only checkbox is checked then the expression widget no longer shows the fields in the combobox how to reproduce load a vector layer with some features run an algorithm that uses a qgsprocessingparameterexpression for example order by expression click on the expression widget combobox button the layer s fields are listed go to the map canvas and select some features back to the algorithm dialog check selected features only click on the expression widget combobox button the layer s fields are not listed qgis and os versions on debian testing about click in the table ctrl a and then ctrl c finally paste here
| 1
|
19,400
| 25,541,452,142
|
IssuesEvent
|
2022-11-29 15:35:05
|
aiidateam/plumpy
|
https://api.github.com/repos/aiidateam/plumpy
|
closed
|
`Process.raw_inputs` are modified in `on_create`
|
type/bug priority/important topic/processes
|
The inputs that are passed when instantiating a new `Process` instance are stored in the `_raw_inputs` attribute. They are supposed to remain unchanged, however, they are mutated by the `on_create` call by passing it into the `spec().inputs.pre_process` call.
|
1.0
|
`Process.raw_inputs` are modified in `on_create` - The inputs that are passed when instantiating a new `Process` instance are stored in the `_raw_inputs` attribute. They are supposed to remain unchanged, however, they are mutated by the `on_create` call by passing it into the `spec().inputs.pre_process` call.
|
process
|
process raw inputs are modified in on create the inputs that are passed when instantiating a new process instance are stored in the raw inputs attribute they are supposed to remain unchanged however they are mutated by the on create call by passing it into the spec inputs pre process call
| 1
|
375,910
| 26,181,708,313
|
IssuesEvent
|
2023-01-02 16:28:13
|
aidotse/PASEOS
|
https://api.github.com/repos/aidotse/PASEOS
|
opened
|
Put first version on pip
|
documentation user-facing
|
# Feature
## Desired Behavior / Functionality
It might be nice, if we get on pip soon! :partying_face:
Could use these scripts for convenience:
https://github.com/esa/torchquad/blob/main/.github/workflows/deploy_to_test_pypi.yml
https://github.com/esa/torchquad/blob/main/.github/workflows/deploy_to_pypi.yml
This "what needs to be done" in release process could inspire us, maybe we create this type of issue workflow too?
## What Needs to Be Done
- [ ] Set up release issue workflow
- [ ] Follow it
## How Can It Be Tested
Install from pip if it's successful :upside_down_face:
|
1.0
|
Put first version on pip - # Feature
## Desired Behavior / Functionality
It might be nice, if we get on pip soon! :partying_face:
Could use these scripts for convenience:
https://github.com/esa/torchquad/blob/main/.github/workflows/deploy_to_test_pypi.yml
https://github.com/esa/torchquad/blob/main/.github/workflows/deploy_to_pypi.yml
This "what needs to be done" in release process could inspire us, maybe we create this type of issue workflow too?
## What Needs to Be Done
- [ ] Set up release issue workflow
- [ ] Follow it
## How Can It Be Tested
Install from pip if it's successful :upside_down_face:
|
non_process
|
put first version on pip feature desired behavior functionality it might be nice if we get on pip soon partying face could use these scripts for convenience this what needs to be done in release process could inspire us maybe we create this type of issue workflow too what needs to be done set up release issue workflow follow it how can it be tested install from pip if it s successful upside down face
| 0
|
18,934
| 24,890,513,852
|
IssuesEvent
|
2022-10-28 11:35:21
|
TUM-Dev/NavigaTUM
|
https://api.github.com/repos/TUM-Dev/NavigaTUM
|
closed
|
[Entry] [4220.01.119]: Koordinate bearbeiten
|
entry webform delete-after-processing
|
Hallo, ich möchte diese Koordinate zum Roomfinder hinzufügen:
```
"4220.01.119": {coords: {lat: 48.39883751173505, lon: 11.72308191140641}}
```
|
1.0
|
[Entry] [4220.01.119]: Koordinate bearbeiten - Hallo, ich möchte diese Koordinate zum Roomfinder hinzufügen:
```
"4220.01.119": {coords: {lat: 48.39883751173505, lon: 11.72308191140641}}
```
|
process
|
koordinate bearbeiten hallo ich möchte diese koordinate zum roomfinder hinzufügen coords lat lon
| 1
|
111,897
| 14,170,279,073
|
IssuesEvent
|
2020-11-12 14:20:48
|
ajency/Dhanda-App
|
https://api.github.com/repos/ajency/Dhanda-App
|
closed
|
no marking of half day with yellow colour found
|
Assigned to QA UI/ design Yet to Push
|
In the case of present where a green tick mark is placed a mark with yellow colour must be marked to indicated that the employee is half day.
|
1.0
|
no marking of half day with yellow colour found - In the case of present where a green tick mark is placed a mark with yellow colour must be marked to indicated that the employee is half day.
|
non_process
|
no marking of half day with yellow colour found in the case of present where a green tick mark is placed a mark with yellow colour must be marked to indicated that the employee is half day
| 0
|
8,828
| 27,172,303,820
|
IssuesEvent
|
2023-02-17 20:39:17
|
OneDrive/onedrive-api-docs
|
https://api.github.com/repos/OneDrive/onedrive-api-docs
|
closed
|
Create Delta Token using datetime
|
type:enhancement Needs: Triage :mag: area:Delta automation:Closed
|
#### Category
- [ ] **Question**
- [ ] Documentation issue
- [ ] Bug
Is there any way to create a delta token using some datetime? because token=latest would create token using current time and we may need to have one that could be created using some old time
Thank you.
[ ]: http://aka.ms/onedrive-api-issues
[x]: http://aka.ms/onedrive-api-issues
|
1.0
|
Create Delta Token using datetime -
#### Category
- [ ] **Question**
- [ ] Documentation issue
- [ ] Bug
Is there any way to create a delta token using some datetime? because token=latest would create token using current time and we may need to have one that could be created using some old time
Thank you.
[ ]: http://aka.ms/onedrive-api-issues
[x]: http://aka.ms/onedrive-api-issues
|
non_process
|
create delta token using datetime category question documentation issue bug is there any way to create a delta token using some datetime because token latest would create token using current time and we may need to have one that could be created using some old time thank you
| 0
|
330,716
| 24,274,237,204
|
IssuesEvent
|
2022-09-28 12:46:35
|
microsoft/torchgeo
|
https://api.github.com/repos/microsoft/torchgeo
|
opened
|
Resnet50 pretrained model documentation
|
documentation
|
### Issue
- The documentation suggests that the `sensor` flag can take on several sources, but one has to go into the source code to find out which values are possible
- The documentation states that the `bands` flag can accept 'all' or 'rgb', however, currently only 'all' is supported and specifying 'rgb' throws an error
- I am wondering why the number of input channels for pretrained on Sentinel2 imagery is 10 and not all the available 13 bands
I can open an PR if there are suggestions to the above issues and change the documentation accordingly.
### Fix
Be more clear about which values are currently supported and an explanation about how the pretrained weights came about.
|
1.0
|
Resnet50 pretrained model documentation - ### Issue
- The documentation suggests that the `sensor` flag can take on several sources, but one has to go into the source code to find out which values are possible
- The documentation states that the `bands` flag can accept 'all' or 'rgb', however, currently only 'all' is supported and specifying 'rgb' throws an error
- I am wondering why the number of input channels for pretrained on Sentinel2 imagery is 10 and not all the available 13 bands
I can open an PR if there are suggestions to the above issues and change the documentation accordingly.
### Fix
Be more clear about which values are currently supported and an explanation about how the pretrained weights came about.
|
non_process
|
pretrained model documentation issue the documentation suggests that the sensor flag can take on several sources but one has to go into the source code to find out which values are possible the documentation states that the bands flag can accept all or rgb however currently only all is supported and specifying rgb throws an error i am wondering why the number of input channels for pretrained on imagery is and not all the available bands i can open an pr if there are suggestions to the above issues and change the documentation accordingly fix be more clear about which values are currently supported and an explanation about how the pretrained weights came about
| 0
|
12,566
| 14,983,179,758
|
IssuesEvent
|
2021-01-28 16:53:05
|
scikit-learn/scikit-learn
|
https://api.github.com/repos/scikit-learn/scikit-learn
|
closed
|
New strategies for KBinsDiscretizer
|
New Feature module:preprocessing
|
New non-parametric strategies could be added to KBD. Like geometric, winsorized, combined (Uniform+Quantiles, Geometric+Uniform, Geometric+Quantiles).
Winsorized binning uses interpercentile range (in my examples I used p95-p05) instead of peak-to-peak (max - min) like in Uniform. It allows algorithm to ignore outliers and save the form of distribution of the most of the mass of data.
Geometric binning uses incremental binning. This technique allows to "deskew" the distribution (or skew it if it was symmetric). It is used in some GIS packages and could be beneficial for regression models.
Uniquant is Uniform+Quantiles (CatBoost also has this one). It is just an average between Uniform and Quantile bins. Same thing for Geouni and Geoquant. I did not plot Quantile strategy, since it will be always uniform distribution. I used n_bins=31 with N=10_000.
[More info about winsorized binning could be found here](https://www.r-bloggers.com/2019/03/binning-data-with-rbin/). It will require additional parameter and the effect of this binning technique could be achieved by different strategies without additional hyperparameters, so this one is debatable.
[More info about geometric binning (and other interesting techniques) could be found here](https://www.slideshare.net/johnjreiser/classification-systems)
Results for LogisticRegression, RandomForestClassifier, Ridge and RandomForestRegressor. Datasets generated with `make_classification` and `make_regression` with `n_samples=1000` and `n_bins=10` (default value). Combined here is Uniform+Quantile. I did not test other combos mentioned above.
All these new algorithms are easy to implement (just add another elif and two lines of code for each one) and are fast to compute, since no fitting is necessary.
|
1.0
|
New strategies for KBinsDiscretizer - New non-parametric strategies could be added to KBD. Like geometric, winsorized, combined (Uniform+Quantiles, Geometric+Uniform, Geometric+Quantiles).
Winsorized binning uses interpercentile range (in my examples I used p95-p05) instead of peak-to-peak (max - min) like in Uniform. It allows algorithm to ignore outliers and save the form of distribution of the most of the mass of data.
Geometric binning uses incremental binning. This technique allows to "deskew" the distribution (or skew it if it was symmetric). It is used in some GIS packages and could be beneficial for regression models.
Uniquant is Uniform+Quantiles (CatBoost also has this one). It is just an average between Uniform and Quantile bins. Same thing for Geouni and Geoquant. I did not plot Quantile strategy, since it will be always uniform distribution. I used n_bins=31 with N=10_000.
[More info about winsorized binning could be found here](https://www.r-bloggers.com/2019/03/binning-data-with-rbin/). It will require additional parameter and the effect of this binning technique could be achieved by different strategies without additional hyperparameters, so this one is debatable.
[More info about geometric binning (and other interesting techniques) could be found here](https://www.slideshare.net/johnjreiser/classification-systems)
Results for LogisticRegression, RandomForestClassifier, Ridge and RandomForestRegressor. Datasets generated with `make_classification` and `make_regression` with `n_samples=1000` and `n_bins=10` (default value). Combined here is Uniform+Quantile. I did not test other combos mentioned above.
All these new algorithms are easy to implement (just add another elif and two lines of code for each one) and are fast to compute, since no fitting is necessary.
|
process
|
new strategies for kbinsdiscretizer new non parametric strategies could be added to kbd like geometric winsorized combined uniform quantiles geometric uniform geometric quantiles winsorized binning uses interpercentile range in my examples i used instead of peak to peak max min like in uniform it allows algorithm to ignore outliers and save the form of distribution of the most of the mass of data geometric binning uses incremental binning this technique allows to deskew the distribution or skew it if it was symmetric it is used in some gis packages and could be beneficial for regression models uniquant is uniform quantiles catboost also has this one it is just an average between uniform and quantile bins same thing for geouni and geoquant i did not plot quantile strategy since it will be always uniform distribution i used n bins with n it will require additional parameter and the effect of this binning technique could be achieved by different strategies without additional hyperparameters so this one is debatable results for logisticregression randomforestclassifier ridge and randomforestregressor datasets generated with make classification and make regression with n samples and n bins default value combined here is uniform quantile i did not test other combos mentioned above all these new algorithms are easy to implement just add another elif and two lines of code for each one and are fast to compute since no fitting is necessary
| 1
|
17,618
| 23,433,970,071
|
IssuesEvent
|
2022-08-15 07:38:19
|
Tencent/tdesign-miniprogram
|
https://api.github.com/repos/Tencent/tdesign-miniprogram
|
closed
|
[Upload] 无论 requestMethod 是否成功，都会返回 success
|
bug in process
|
### tdesign-miniprogram 版本
latest
### 重现链接
_No response_
### 重现步骤
配置一个 requestMethod 方法，并给一个错误的上传地址
### 期望结果
不会触发 success 事件，而是触发 fail 事件
### 实际结果
先触发了 success 事件，然后再开始执行上传，并发现上传错误
<img width="996" alt="image" src="https://user-images.githubusercontent.com/8725110/183850000-75bd5852-067a-4fa4-861e-d7cae1ba3948.png">
### 框架版本
小程序
### 浏览器版本
_No response_
### 系统版本
_No response_
### Node版本
_No response_
### 补充说明
_No response_
|
1.0
|
[Upload] 无论 requestMethod 是否成功，都会返回 success - ### tdesign-miniprogram 版本
latest
### 重现链接
_No response_
### 重现步骤
配置一个 requestMethod 方法，并给一个错误的上传地址
### 期望结果
不会触发 success 事件，而是触发 fail 事件
### 实际结果
先触发了 success 事件，然后再开始执行上传，并发现上传错误
<img width="996" alt="image" src="https://user-images.githubusercontent.com/8725110/183850000-75bd5852-067a-4fa4-861e-d7cae1ba3948.png">
### 框架版本
小程序
### 浏览器版本
_No response_
### 系统版本
_No response_
### Node版本
_No response_
### 补充说明
_No response_
|
process
|
无论 requestmethod 是否成功，都会返回 success tdesign miniprogram 版本 latest 重现链接 no response 重现步骤 配置一个 requestmethod 方法，并给一个错误的上传地址 期望结果 不会触发 success 事件，而是触发 fail 事件 实际结果 先触发了 success 事件，然后再开始执行上传，并发现上传错误 img width alt image src 框架版本 小程序 浏览器版本 no response 系统版本 no response node版本 no response 补充说明 no response
| 1
|
19,480
| 25,790,427,676
|
IssuesEvent
|
2022-12-10 03:20:09
|
ffrostflame/BridgeNet2
|
https://api.github.com/repos/ffrostflame/BridgeNet2
|
opened
|
Truly dynamic bridges/identifiers
|
where: api where: internal process type: feature status: deciding
|
The problem with truly dynamic identifiers/bridges is that you end up needing to manage old identifier references, it needs to be done in a way that does not impact speed, and it needs to be replicated.
There is no way to do this without metatable trickery- I'm going to postpone this until after release, because it is mainly a secondary feature, however it is an incredibly powerful feature.
|
1.0
|
Truly dynamic bridges/identifiers - The problem with truly dynamic identifiers/bridges is that you end up needing to manage old identifier references, it needs to be done in a way that does not impact speed, and it needs to be replicated.
There is no way to do this without metatable trickery- I'm going to postpone this until after release, because it is mainly a secondary feature, however it is an incredibly powerful feature.
|
process
|
truly dynamic bridges identifiers the problem with truly dynamic identifiers bridges is that you end up needing to manage old identifier references it needs to be done in a way that does not impact speed and it needs to be replicated there is no way to do this without metatable trickery i m going to postpone this until after release because it is mainly a secondary feature however it is an incredibly powerful feature
| 1
|
12,559
| 14,979,504,506
|
IssuesEvent
|
2021-01-28 12:21:29
|
parcel-bundler/parcel
|
https://api.github.com/repos/parcel-bundler/parcel
|
closed
|
@parcel/optimizer-cssnano - Missed semicolon
|
:bug: Bug CSS Preprocessing ✨ Parcel 2
|
<!---
Thanks for filing an issue 😄 ! Before you submit, please read the following:
Search open/closed issues before submitting since someone might have asked the same thing before!
-->
# 🐛 bug report
Whenever I try to run `parcel build index.html --no-source-maps --no-scope-hoist` I get the following error
```
🚨 Build failed.
@parcel/optimizer-cssnano: <css input>:1567:14: Missed semicolon
CssSyntaxError: <css input>:1567:14: Missed semicolon
at Input.error (/var/www/html/ampache.hego.co/client/node_modules/@parcel/optimizer-cssnano/node_modules/postcss/lib/input.js:130:16)
at Parser.checkMissedSemicolon (/var/www/html/ampache.hego.co/client/node_modules/@parcel/optimizer-cssnano/node_modules/postcss/lib/parser.js:603:22)
at Parser.decl (/var/www/html/ampache.hego.co/client/node_modules/@parcel/optimizer-cssnano/node_modules/postcss/lib/parser.js:286:46)
at Parser.other (/var/www/html/ampache.hego.co/client/node_modules/@parcel/optimizer-cssnano/node_modules/postcss/lib/parser.js:133:18)
at Parser.parse (/var/www/html/ampache.hego.co/client/node_modules/@parcel/optimizer-cssnano/node_modules/postcss/lib/parser.js:77:16)
at parse (/var/www/html/ampache.hego.co/client/node_modules/@parcel/optimizer-cssnano/node_modules/postcss/lib/parse.js:17:12)
at new LazyResult (/var/www/html/ampache.hego.co/client/node_modules/@parcel/optimizer-cssnano/node_modules/postcss/lib/lazy-result.js:60:16)
at Processor.<anonymous> (/var/www/html/ampache.hego.co/client/node_modules/@parcel/optimizer-cssnano/node_modules/postcss/lib/processor.js:138:12)
at Processor.process (/var/www/html/ampache.hego.co/client/node_modules/@parcel/optimizer-cssnano/node_modules/postcss/lib/processor.js:117:23)
at Object.optimize (/var/www/html/ampache.hego.co/client/node_modules/@parcel/optimizer-cssnano/lib/CSSNanoOptimizer.js:38:68)
FATAL ERROR: v8::FromJust Maybe value is Nothing.
1: 0xa68bf0 node::Abort() [/usr/bin/node]
2: 0x99bc4d node::FatalError(char const*, char const*) [/usr/bin/node]
3: 0xc41f9a v8::Utils::ReportApiFailure(char const*, char const*) [/usr/bin/node]
4: 0x9c139d node::UVException(v8::Isolate*, int, char const*, char const*, char const*, char const*) [/usr/bin/node]
5: 0xa6f048 node::fs::FSReqAfterScope::Reject(uv_fs_s*) [/usr/bin/node]
6: 0xa70319 node::fs::AfterStat(uv_fs_s*) [/usr/bin/node]
7: 0x14479ed [/usr/bin/node]
8: 0x144bfe6 [/usr/bin/node]
9: 0x145eac5 [/usr/bin/node]
10: 0x144c918 uv_run [/usr/bin/node]
11: 0x9bc025 node::SpinEventLoop(node::Environment*) [/usr/bin/node]
12: 0xb2d359 node::worker::Worker::Run() [/usr/bin/node]
13: 0xb2db68 [/usr/bin/node]
14: 0x7f283b113609 [/lib/x86_64-linux-gnu/libpthread.so.0]
15: 0x7f283b03a293 clone [/lib/x86_64-linux-gnu/libc.so.6]
Aborted (core dumped)
error Command failed with exit code 134.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Process finished with exit code 134 (interrupted by signal 6: SIGABRT)
```
🎛 Configuration (.babelrc, package.json, cli command)
<!--- If describing a bug, tell us what your babel configuration looks like -->
.postcssrc
```{
"modules": true,
"plugins": {
"postcss-modules": {
"generateScopedName": "_[name]__[local]"
}
}
}
```
.parcelrc
```
{
"extends": "@parcel/config-default",
"transformers": {
"*.png": ["@parcel/transformer-raw"],
"*.svg": ["@parcel/transformer-raw"]
}
}
```
.babelrc
```
{
"presets": [
"@babel/preset-typescript",
"@babel/preset-env",
"@babel/preset-react"
],
"plugins": [
"@babel/plugin-transform-runtime",
"@babel/plugin-proposal-class-properties"
]
}
```
## 🔦 Context
Running `parcel index.html` works fine.
Commenting this bit of Stylus code seems to resolve the issue
```
@keyframes fadeInFromNone
0%
display none
opacity 0
1%
display block
opacity 0
100%
display block
opacity 1
&:hover
& > img
filter invert(56%) sepia(96%) saturate(1211%) hue-rotate(0deg) brightness(103%) contrast(104%) //make orange
& > .options
display block
opacity 1
animation fadeInFromNone 0.15s easeOut
```
## 💻 Code Sample
https://github.com/ampache/ampache/tree/react-client
This is the entire project
## 🌍 Your Environment
<!--- Include as many relevant details about the environment you experienced the bug in -->
| Software | Version(s) |
| ---------------- | ---------- |
| Parcel | 2.0.0-beta.1
| Node | 15.5.0
| Yarn | 1.19.1
| Operating System | Ubuntu 20.04.1 LTS x86_64
<!-- Love parcel? Please consider supporting our collective:
👉 https://opencollective.com/parcel/donate -->
|
1.0
|
@parcel/optimizer-cssnano - Missed semicolon - <!---
Thanks for filing an issue 😄 ! Before you submit, please read the following:
Search open/closed issues before submitting since someone might have asked the same thing before!
-->
# 🐛 bug report
Whenever I try to run `parcel build index.html --no-source-maps --no-scope-hoist` I get the following error
```
🚨 Build failed.
@parcel/optimizer-cssnano: <css input>:1567:14: Missed semicolon
CssSyntaxError: <css input>:1567:14: Missed semicolon
at Input.error (/var/www/html/ampache.hego.co/client/node_modules/@parcel/optimizer-cssnano/node_modules/postcss/lib/input.js:130:16)
at Parser.checkMissedSemicolon (/var/www/html/ampache.hego.co/client/node_modules/@parcel/optimizer-cssnano/node_modules/postcss/lib/parser.js:603:22)
at Parser.decl (/var/www/html/ampache.hego.co/client/node_modules/@parcel/optimizer-cssnano/node_modules/postcss/lib/parser.js:286:46)
at Parser.other (/var/www/html/ampache.hego.co/client/node_modules/@parcel/optimizer-cssnano/node_modules/postcss/lib/parser.js:133:18)
at Parser.parse (/var/www/html/ampache.hego.co/client/node_modules/@parcel/optimizer-cssnano/node_modules/postcss/lib/parser.js:77:16)
at parse (/var/www/html/ampache.hego.co/client/node_modules/@parcel/optimizer-cssnano/node_modules/postcss/lib/parse.js:17:12)
at new LazyResult (/var/www/html/ampache.hego.co/client/node_modules/@parcel/optimizer-cssnano/node_modules/postcss/lib/lazy-result.js:60:16)
at Processor.<anonymous> (/var/www/html/ampache.hego.co/client/node_modules/@parcel/optimizer-cssnano/node_modules/postcss/lib/processor.js:138:12)
at Processor.process (/var/www/html/ampache.hego.co/client/node_modules/@parcel/optimizer-cssnano/node_modules/postcss/lib/processor.js:117:23)
at Object.optimize (/var/www/html/ampache.hego.co/client/node_modules/@parcel/optimizer-cssnano/lib/CSSNanoOptimizer.js:38:68)
FATAL ERROR: v8::FromJust Maybe value is Nothing.
1: 0xa68bf0 node::Abort() [/usr/bin/node]
2: 0x99bc4d node::FatalError(char const*, char const*) [/usr/bin/node]
3: 0xc41f9a v8::Utils::ReportApiFailure(char const*, char const*) [/usr/bin/node]
4: 0x9c139d node::UVException(v8::Isolate*, int, char const*, char const*, char const*, char const*) [/usr/bin/node]
5: 0xa6f048 node::fs::FSReqAfterScope::Reject(uv_fs_s*) [/usr/bin/node]
6: 0xa70319 node::fs::AfterStat(uv_fs_s*) [/usr/bin/node]
7: 0x14479ed [/usr/bin/node]
8: 0x144bfe6 [/usr/bin/node]
9: 0x145eac5 [/usr/bin/node]
10: 0x144c918 uv_run [/usr/bin/node]
11: 0x9bc025 node::SpinEventLoop(node::Environment*) [/usr/bin/node]
12: 0xb2d359 node::worker::Worker::Run() [/usr/bin/node]
13: 0xb2db68 [/usr/bin/node]
14: 0x7f283b113609 [/lib/x86_64-linux-gnu/libpthread.so.0]
15: 0x7f283b03a293 clone [/lib/x86_64-linux-gnu/libc.so.6]
Aborted (core dumped)
error Command failed with exit code 134.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Process finished with exit code 134 (interrupted by signal 6: SIGABRT)
```
🎛 Configuration (.babelrc, package.json, cli command)
<!--- If describing a bug, tell us what your babel configuration looks like -->
.postcssrc
```{
"modules": true,
"plugins": {
"postcss-modules": {
"generateScopedName": "_[name]__[local]"
}
}
}
```
.parcelrc
```
{
"extends": "@parcel/config-default",
"transformers": {
"*.png": ["@parcel/transformer-raw"],
"*.svg": ["@parcel/transformer-raw"]
}
}
```
.babelrc
```
{
"presets": [
"@babel/preset-typescript",
"@babel/preset-env",
"@babel/preset-react"
],
"plugins": [
"@babel/plugin-transform-runtime",
"@babel/plugin-proposal-class-properties"
]
}
```
## 🔦 Context
Running `parcel index.html` works fine.
Commenting this bit of Stylus code seems to resolve the issue
```
@keyframes fadeInFromNone
0%
display none
opacity 0
1%
display block
opacity 0
100%
display block
opacity 1
&:hover
& > img
filter invert(56%) sepia(96%) saturate(1211%) hue-rotate(0deg) brightness(103%) contrast(104%) //make orange
& > .options
display block
opacity 1
animation fadeInFromNone 0.15s easeOut
```
## 💻 Code Sample
https://github.com/ampache/ampache/tree/react-client
This is the entire project
## 🌍 Your Environment
<!--- Include as many relevant details about the environment you experienced the bug in -->
| Software | Version(s) |
| ---------------- | ---------- |
| Parcel | 2.0.0-beta.1
| Node | 15.5.0
| Yarn | 1.19.1
| Operating System | Ubuntu 20.04.1 LTS x86_64
<!-- Love parcel? Please consider supporting our collective:
👉 https://opencollective.com/parcel/donate -->
|
process
|
parcel optimizer cssnano missed semicolon thanks for filing an issue 😄 before you submit please read the following search open closed issues before submitting since someone might have asked the same thing before 🐛 bug report whenever i try to run parcel build index html no source maps no scope hoist i get the following error 🚨 build failed parcel optimizer cssnano missed semicolon csssyntaxerror missed semicolon at input error var www html ampache hego co client node modules parcel optimizer cssnano node modules postcss lib input js at parser checkmissedsemicolon var www html ampache hego co client node modules parcel optimizer cssnano node modules postcss lib parser js at parser decl var www html ampache hego co client node modules parcel optimizer cssnano node modules postcss lib parser js at parser other var www html ampache hego co client node modules parcel optimizer cssnano node modules postcss lib parser js at parser parse var www html ampache hego co client node modules parcel optimizer cssnano node modules postcss lib parser js at parse var www html ampache hego co client node modules parcel optimizer cssnano node modules postcss lib parse js at new lazyresult var www html ampache hego co client node modules parcel optimizer cssnano node modules postcss lib lazy result js at processor var www html ampache hego co client node modules parcel optimizer cssnano node modules postcss lib processor js at processor process var www html ampache hego co client node modules parcel optimizer cssnano node modules postcss lib processor js at object optimize var www html ampache hego co client node modules parcel optimizer cssnano lib cssnanooptimizer js fatal error fromjust maybe value is nothing node abort node fatalerror char const char const utils reportapifailure char const char const node uvexception isolate int char const char const char const char const node fs fsreqafterscope reject uv fs s node fs afterstat uv fs s uv run node spineventloop node environment node worker worker run clone aborted core dumped error command failed with exit code info visit for documentation about this command process finished with exit code interrupted by signal sigabrt 🎛 configuration babelrc package json cli command postcssrc modules true plugins postcss modules generatescopedname parcelrc extends parcel config default transformers png svg babelrc presets babel preset typescript babel preset env babel preset react plugins babel plugin transform runtime babel plugin proposal class properties 🔦 context running parcel index html works fine commenting this bit of stylus code seems to resolve the issue keyframes fadeinfromnone display none opacity display block opacity display block opacity hover img filter invert sepia saturate hue rotate brightness contrast make orange options display block opacity animation fadeinfromnone easeout 💻 code sample this is the entire project 🌍 your environment software version s parcel beta node yarn operating system ubuntu lts love parcel please consider supporting our collective 👉
| 1
|
243,592
| 18,718,473,609
|
IssuesEvent
|
2021-11-03 09:02:14
|
WICG/conversion-measurement-api
|
https://api.github.com/repos/WICG/conversion-measurement-api
|
opened
|
Add links to blogposts in explainers to easen onboarding
|
documentation
|
Explainers in this repo may be the first touchpoint for folks looking to experiment with Attribution Reporting.
However, explainers are not always the most approachable guidance for newcomers⏤sometimes, high-level intro blogposts are available.
Would it make sense to link these at the top of each explainer? By adding something along these lines at the beginning of each explainer:
******
This is a technical explainer. If you're looking for a high-level intro to {e.g. Attribution Reporting with event-level reports}, head over to {link to blogpost}.
For a list of all resources on Attribution Reporting, head over to [Attribution Reporting](https://developer.chrome.com/docs/privacy-sandbox/attribution-reporting/).
******
Note: [external documentation](https://github.com/WICG/conversion-measurement-api#external-documentation) is listed in the README but this could also be better, I'll open a separate issue for that).
|
1.0
|
Add links to blogposts in explainers to easen onboarding - Explainers in this repo may be the first touchpoint for folks looking to experiment with Attribution Reporting.
However, explainers are not always the most approachable guidance for newcomers⏤sometimes, high-level intro blogposts are available.
Would it make sense to link these at the top of each explainer? By adding something along these lines at the beginning of each explainer:
******
This is a technical explainer. If you're looking for a high-level intro to {e.g. Attribution Reporting with event-level reports}, head over to {link to blogpost}.
For a list of all resources on Attribution Reporting, head over to [Attribution Reporting](https://developer.chrome.com/docs/privacy-sandbox/attribution-reporting/).
******
Note: [external documentation](https://github.com/WICG/conversion-measurement-api#external-documentation) is listed in the README but this could also be better, I'll open a separate issue for that).
|
non_process
|
add links to blogposts in explainers to easen onboarding explainers in this repo may be the first touchpoint for folks looking to experiment with attribution reporting however explainers are not always the most approachable guidance for newcomers⏤sometimes high level intro blogposts are available would it make sense to link these at the top of each explainer by adding something along these lines at the beginning of each explainer this is a technical explainer if you re looking for a high level intro to e g attribution reporting with event level reports head over to link to blogpost for a list of all resources on attribution reporting head over to note is listed in the readme but this could also be better i ll open a separate issue for that
| 0
|
3,287
| 6,383,419,560
|
IssuesEvent
|
2017-08-03 00:12:12
|
nodejs/node
|
https://api.github.com/repos/nodejs/node
|
closed
|
child_process, *nix, stdio undefined when kernel nofile limit hit
|
child_process
|
<!--
Thank you for reporting an issue.
This issue tracker is for bugs and issues found within Node.js core.
If you require more general support please file an issue on our help
repo. https://github.com/nodejs/help
Please fill in as much of the template below as you're able.
Version: output of `node -v`
Platform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows)
Subsystem: if known, please specify affected core module name
If possible, please provide code that demonstrates the problem, keeping it as
simple and free of external dependencies as you are able.
-->
* **Version**: v8.2.0-rc.1
* **Platform**: 16.5.0 Darwin Kernel Version 16.5.0: Fri Mar 3 16:52:33 PST 2017; root:xnu-3789.51.2~3/RELEASE_X86_64 x86_64
* **Subsystem**: child_process
<!-- Enter your issue details below this comment. -->
When we hit the NOFILE limit under either Linux or OS X, the `stdio` property of a `child_process` instance is sometimes `undefined`. This is either undocumented behavior (docs say `stdio` should always be an Array on an instance of `child_process`) or a bug.
To reproduce:
1. ensure you can hit the limit of open files at any given time
2. loop this code until you hit the limit:
```js
const childProcess = require('child_process');
const worker = childProcess.spawn('/path/to/some/executable/expecting/pipes', [], {stdio: ['ignore', 1, 2, 'pipe', 'pipe']});
```
3. `worker.stdio` will be `undefined`, rather than an `Array` once the open file limit is hit
Also see https://github.com/webpack-contrib/thread-loader/issues/2 where I first observed this.
|
1.0
|
child_process, *nix, stdio undefined when kernel nofile limit hit - <!--
Thank you for reporting an issue.
This issue tracker is for bugs and issues found within Node.js core.
If you require more general support please file an issue on our help
repo. https://github.com/nodejs/help
Please fill in as much of the template below as you're able.
Version: output of `node -v`
Platform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows)
Subsystem: if known, please specify affected core module name
If possible, please provide code that demonstrates the problem, keeping it as
simple and free of external dependencies as you are able.
-->
* **Version**: v8.2.0-rc.1
* **Platform**: 16.5.0 Darwin Kernel Version 16.5.0: Fri Mar 3 16:52:33 PST 2017; root:xnu-3789.51.2~3/RELEASE_X86_64 x86_64
* **Subsystem**: child_process
<!-- Enter your issue details below this comment. -->
When we hit the NOFILE limit under either Linux or OS X, the `stdio` property of a `child_process` instance is sometimes `undefined`. This is either undocumented behavior (docs say `stdio` should always be an Array on an instance of `child_process`) or a bug.
To reproduce:
1. ensure you can hit the limit of open files at any given time
2. loop this code until you hit the limit:
```js
const childProcess = require('child_process');
const worker = childProcess.spawn('/path/to/some/executable/expecting/pipes', [], {stdio: ['ignore', 1, 2, 'pipe', 'pipe']});
```
3. `worker.stdio` will be `undefined`, rather than an `Array` once the open file limit is hit
Also see https://github.com/webpack-contrib/thread-loader/issues/2 where I first observed this.
|
process
|
child process nix stdio undefined when kernel nofile limit hit thank you for reporting an issue this issue tracker is for bugs and issues found within node js core if you require more general support please file an issue on our help repo please fill in as much of the template below as you re able version output of node v platform output of uname a unix or version and or bit windows subsystem if known please specify affected core module name if possible please provide code that demonstrates the problem keeping it as simple and free of external dependencies as you are able version rc platform darwin kernel version fri mar pst root xnu release subsystem child process when we hit the nofile limit under either linux or os x the stdio property of a child process instance is sometimes undefined this is either undocumented behavior docs say stdio should always be an array on an instance of child process or a bug to reproduce ensure you can hit the limit of open files at any given time loop this code until you hit the limit js const childprocess require child process const worker childprocess spawn path to some executable expecting pipes stdio worker stdio will be undefined rather than an array once the open file limit is hit also see where i first observed this
| 1
|
3,142
| 6,195,508,806
|
IssuesEvent
|
2017-07-05 12:48:51
|
higankanshi/Meta.Vlc
|
https://api.github.com/repos/higankanshi/Meta.Vlc
|
closed
|
SnapshotContext , switch path extension missing dot
|
bug processing
|
as far as I know, the method **Path.GetExtensions** return value have a dot prefix, just like ".jpg". but the switch in the method lost the litter dot.
> public SnapshotContext(String path, int quality)
{
Path = System.IO.Path.GetDirectoryName(path).FormatPath();
Name = System.IO.Path.GetFileName(path);
switch (System.IO.Path.GetExtension(path).ToLower())
{
case "bmp":
Format = SnapshotFormat.BMP;
break;
case "png":
Format = SnapshotFormat.PNG;
break;
case "jpg":
case "jpeg":
Format = SnapshotFormat.JPG;
break;
default:
throw new ArgumentOutOfRangeException("path", @"Screenshot format must be 'bmp', 'jpg' or 'png'.");
}
Quality = quality;
}
When I post a file path like "c:\\abc.jpg", it will always throw exception say not right extension, I think, they should may be case ".bmp", ".png" and ".jpg"?
|
1.0
|
SnapshotContext , switch path extension missing dot - as far as I know, the method **Path.GetExtensions** return value have a dot prefix, just like ".jpg". but the switch in the method lost the litter dot.
> public SnapshotContext(String path, int quality)
{
Path = System.IO.Path.GetDirectoryName(path).FormatPath();
Name = System.IO.Path.GetFileName(path);
switch (System.IO.Path.GetExtension(path).ToLower())
{
case "bmp":
Format = SnapshotFormat.BMP;
break;
case "png":
Format = SnapshotFormat.PNG;
break;
case "jpg":
case "jpeg":
Format = SnapshotFormat.JPG;
break;
default:
throw new ArgumentOutOfRangeException("path", @"Screenshot format must be 'bmp', 'jpg' or 'png'.");
}
Quality = quality;
}
When I post a file path like "c:\\abc.jpg", it will always throw exception say not right extension, I think, they should may be case ".bmp", ".png" and ".jpg"?
|
process
|
snapshotcontext switch path extension missing dot as far as i know the method path getextensions return value have a dot prefix just like jpg but the switch in the method lost the litter dot public snapshotcontext string path int quality path system io path getdirectoryname path formatpath name system io path getfilename path switch system io path getextension path tolower case bmp format snapshotformat bmp break case png format snapshotformat png break case jpg case jpeg format snapshotformat jpg break default throw new argumentoutofrangeexception path screenshot format must be bmp jpg or png quality quality when i post a file path like c abc jpg it will always throw exception say not right extension i think they should may be case bmp png and jpg
| 1
|
2,660
| 5,435,256,691
|
IssuesEvent
|
2017-03-05 15:31:18
|
alexrj/Slic3r
|
https://api.github.com/repos/alexrj/Slic3r
|
closed
|
output_filename_format template variables are not replaced when background processing is disabled
|
Background Processing UI: Misc Verified bug
|
### Version
1.2.9-364-g3700950
### Operating system type + version
Debian testing/unstable, Perl 5.22.2, Slic3r from git.
### Behavior
As described in [https://github.com/alexrj/Slic3r/wiki/FAQ#how-can-i-specify-a-custom-filename-format-for-output-g-code-files], when using the GUI, the `output_filename_format` setting can include the print preset, filament preset, and printer preset. However, these are only replaced if background processing is enabled, otherwise the filename will contain the literal variables, like `myobject.[print_preset]_[filament_preset]_[printer_preset].gcode`.
Steps to reproduce:
1. Go to "Print Settings" → "Output options", and set "Output filename format" to `[input_filename_base].[print_preset]_[filament_preset]_[printer_preset].[scale].gcode`. Save the preset.
2. Have background processing enabled, or enable it via "File" → "Preferences", and restart Slic3r.
3. Load any STL, e.g. `GEB.stl`, click "Export G-Code".
4. The pre-defined filename in the save dialog looks like `GEB.Lulzbot fine_Lulzbot PLA DAS FILAMENT_Lulzbot.100%.gcode` (which includes the names of my presets). Close the dialog without saving.
5. Disable background processing via "File" → "Preferences", and restart Slic3r.
6. Load an STL, export G-Code.
7. The pre-defined filename in the save dialog now looks like `GEB.[print_preset]_[filament_preset]_[printer_preset].100%.gcode`, but it should look like before in step 4.
This happens with any STL that I tried (about ~6 different), and also after cleaning my Slic3r settings and doing the Configuration Assistant again to get a fresh preset.
|
1.0
|
output_filename_format template variables are not replaced when background processing is disabled - ### Version
1.2.9-364-g3700950
### Operating system type + version
Debian testing/unstable, Perl 5.22.2, Slic3r from git.
### Behavior
As described in [https://github.com/alexrj/Slic3r/wiki/FAQ#how-can-i-specify-a-custom-filename-format-for-output-g-code-files], when using the GUI, the `output_filename_format` setting can include the print preset, filament preset, and printer preset. However, these are only replaced if background processing is enabled, otherwise the filename will contain the literal variables, like `myobject.[print_preset]_[filament_preset]_[printer_preset].gcode`.
Steps to reproduce:
1. Go to "Print Settings" → "Output options", and set "Output filename format" to `[input_filename_base].[print_preset]_[filament_preset]_[printer_preset].[scale].gcode`. Save the preset.
2. Have background processing enabled, or enable it via "File" → "Preferences", and restart Slic3r.
3. Load any STL, e.g. `GEB.stl`, click "Export G-Code".
4. The pre-defined filename in the save dialog looks like `GEB.Lulzbot fine_Lulzbot PLA DAS FILAMENT_Lulzbot.100%.gcode` (which includes the names of my presets). Close the dialog without saving.
5. Disable background processing via "File" → "Preferences", and restart Slic3r.
6. Load an STL, export G-Code.
7. The pre-defined filename in the save dialog now looks like `GEB.[print_preset]_[filament_preset]_[printer_preset].100%.gcode`, but it should look like before in step 4.
This happens with any STL that I tried (about ~6 different), and also after cleaning my Slic3r settings and doing the Configuration Assistant again to get a fresh preset.
|
process
|
output filename format template variables are not replaced when background processing is disabled version operating system type version debian testing unstable perl from git behavior as described in when using the gui the output filename format setting can include the print preset filament preset and printer preset however these are only replaced if background processing is enabled otherwise the filename will contain the literal variables like myobject gcode steps to reproduce go to print settings → output options and set output filename format to gcode save the preset have background processing enabled or enable it via file → preferences and restart load any stl e g geb stl click export g code the pre defined filename in the save dialog looks like geb lulzbot fine lulzbot pla das filament lulzbot gcode which includes the names of my presets close the dialog without saving disable background processing via file → preferences and restart load an stl export g code the pre defined filename in the save dialog now looks like geb gcode but it should look like before in step this happens with any stl that i tried about different and also after cleaning my settings and doing the configuration assistant again to get a fresh preset
| 1
|
794
| 10,550,587,885
|
IssuesEvent
|
2019-10-03 11:26:12
|
Cha-OS/colabo
|
https://api.github.com/repos/Cha-OS/colabo
|
opened
|
Net or Server accessing errors
|
IMPORTANT UX.UsrOnBoard+AvoidUsrErr backend moderation performance reliability
|
- if the server is unavailable, inform the user, e.g. after several retries or HTTP request FAIL response
- let him TRY again.
- NOTIFICATIONS or TOOLBAR Status
- you're offline (re-introduce it from the old code)
- you're net is weak
|
True
|
Net or Server accessing errors - - if the server is unavailable, inform the user, e.g. after several retries or HTTP request FAIL response
- let him TRY again.
- NOTIFICATIONS or TOOLBAR Status
- you're offline (re-introduce it from the old code)
- you're net is weak
|
non_process
|
net or server accessing errors if the server is unavailable inform the user e g after several retries or http request fail response let him try again notifications or toolbar status you re offline re introduce it from the old code you re net is weak
| 0
|
15,324
| 19,433,139,074
|
IssuesEvent
|
2021-12-21 14:15:59
|
threefoldtech/tfchain
|
https://api.github.com/repos/threefoldtech/tfchain
|
closed
|
Testnet migration
|
process_wontfix
|
We are looking into setting up a new testnet based on NPOS validaton. Since it is really hard to migrate from aura to babe/staking, we will set up a new testnet. At least the balances from old testnet will need to be restored on the new testnet.
There is an "exportstate" subcommand in the tfchain binary, which might provide the required functionality so we can just start the new chain with a genesis config created with that command.
|
1.0
|
Testnet migration - We are looking into setting up a new testnet based on NPOS validaton. Since it is really hard to migrate from aura to babe/staking, we will set up a new testnet. At least the balances from old testnet will need to be restored on the new testnet.
There is an "exportstate" subcommand in the tfchain binary, which might provide the required functionality so we can just start the new chain with a genesis config created with that command.
|
process
|
testnet migration we are looking into setting up a new testnet based on npos validaton since it is really hard to migrate from aura to babe staking we will set up a new testnet at least the balances from old testnet will need to be restored on the new testnet there is an exportstate subcommand in the tfchain binary which might provide the required functionality so we can just start the new chain with a genesis config created with that command
| 1
|
225,375
| 7,481,214,069
|
IssuesEvent
|
2018-04-04 19:55:08
|
RITlug/TigerOS
|
https://api.github.com/repos/RITlug/TigerOS
|
opened
|
Fix Design Documentation to accomidate new directory structure
|
bug easyfix priority:med
|
# Summary
* This issue is a…
* [x] Bug report
* [ ] Feature request
* [ ] Other issue
* [ ] Question
* **Describe the issue / feature in 1-2 sentences**:
New directory structure has messed up some of the links in the wiki.
# Background
### Bug report
404 page in Design docs on certain links. Needs to be fixed. Should be easy the places exist just in different places than before.
|
1.0
|
Fix Design Documentation to accomidate new directory structure - # Summary
* This issue is a…
* [x] Bug report
* [ ] Feature request
* [ ] Other issue
* [ ] Question
* **Describe the issue / feature in 1-2 sentences**:
New directory structure has messed up some of the links in the wiki.
# Background
### Bug report
404 page in Design docs on certain links. Needs to be fixed. Should be easy the places exist just in different places than before.
|
non_process
|
fix design documentation to accomidate new directory structure summary this issue is a… bug report feature request other issue question describe the issue feature in sentences new directory structure has messed up some of the links in the wiki background bug report page in design docs on certain links needs to be fixed should be easy the places exist just in different places than before
| 0
|
151,090
| 23,761,084,084
|
IssuesEvent
|
2022-09-01 08:56:12
|
Regalis11/Barotrauma
|
https://api.github.com/repos/Regalis11/Barotrauma
|
closed
|
small pumps are not visible on the typhoon 1 preview in the lobby
|
Bug Need more info Design Low prio
|
### Disclaimers
- [X] I have searched the issue tracker to check if the issue has already been reported.
- [X] My issue happened while using mods.
### What happened?
I should have been able to see the small pumps in expanded preview for the typhoon in the game lobby
### Reproduction steps
1. load up a lobby
2. select the typhon
3. open the expanded preview
4. check for the small pumps
### Bug prevalence
Happens every time I play
### Version
0.18.15.0
### -
_No response_
### Which operating system did you encounter this bug on?
Windows
### Relevant error messages and crash reports
_No response_
|
1.0
|
small pumps are not visible on the typhoon 1 preview in the lobby - ### Disclaimers
- [X] I have searched the issue tracker to check if the issue has already been reported.
- [X] My issue happened while using mods.
### What happened?
I should have been able to see the small pumps in expanded preview for the typhoon in the game lobby
### Reproduction steps
1. load up a lobby
2. select the typhon
3. open the expanded preview
4. check for the small pumps
### Bug prevalence
Happens every time I play
### Version
0.18.15.0
### -
_No response_
### Which operating system did you encounter this bug on?
Windows
### Relevant error messages and crash reports
_No response_
|
non_process
|
small pumps are not visible on the typhoon preview in the lobby disclaimers i have searched the issue tracker to check if the issue has already been reported my issue happened while using mods what happened i should have been able to see the small pumps in expanded preview for the typhoon in the game lobby reproduction steps load up a lobby select the typhon open the expanded preview check for the small pumps bug prevalence happens every time i play version no response which operating system did you encounter this bug on windows relevant error messages and crash reports no response
| 0
|
367,640
| 25,754,964,142
|
IssuesEvent
|
2022-12-08 15:46:09
|
Pradumnasaraf/open-source-with-pradumna
|
https://api.github.com/repos/Pradumnasaraf/open-source-with-pradumna
|
closed
|
[FEATURE] Add process and documentation about GitHub code spaces
|
documentation how-to feature
|
### Description
As GitHub came up with a new feature of code spaces, i would like to add it in the repo and let beginners know about it more clearly.
### Screenshots
|
1.0
|
[FEATURE] Add process and documentation about GitHub code spaces - ### Description
As GitHub came up with a new feature of code spaces, i would like to add it in the repo and let beginners know about it more clearly.
### Screenshots
|
non_process
|
add process and documentation about github code spaces description as github came up with a new feature of code spaces i would like to add it in the repo and let beginners know about it more clearly screenshots
| 0
|
5,834
| 8,666,087,010
|
IssuesEvent
|
2018-11-29 02:18:53
|
w3c/w3process
|
https://api.github.com/repos/w3c/w3process
|
closed
|
"Implementation experience" description should clearly identify likelihood of broad acceptance
|
ABInputSought ABProcess2019Candidate
|
Transferred from https://www.w3.org/community/w3process/track/issues/180
State: Raised
|
1.0
|
"Implementation experience" description should clearly identify likelihood of broad acceptance - Transferred from https://www.w3.org/community/w3process/track/issues/180
State: Raised
|
process
|
implementation experience description should clearly identify likelihood of broad acceptance transferred from state raised
| 1
|
306,401
| 26,465,026,563
|
IssuesEvent
|
2023-01-16 22:09:12
|
Exiled-Team/Common-Utils
|
https://api.github.com/repos/Exiled-Team/Common-Utils
|
opened
|
[BUG] Plugin not loading
|
needs testing
|
**Describe the bug**
A clear and concise description of what the bug is.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
**Expected behavior**
Plugin loading correctly
**Server logs**
```[2023-01-16 22:06:20.516 +00:00] [ERROR] [Exiled.Loader] Plugin "Common Utilities" threw an exception while enabling: System.TypeLoadException: Could not resolve type with token 01000064 (from typeref, class/assembly Exiled.Events.EventArgs.Player.ThrownItemEventArgs, Exiled.Events, Version=6.0.0.0, Culture=neutral> at Exiled.Loader.Loader.EnablePlugins () [0x000a8] in <45764f9e3028450f9a5d618968896851>:0
```
**Copy of current CU config section**
CommonUtilities:
# Whether or not debug messages should be shown.
debug: false
# The SCP Roles able to use V to talk to humans.
scp_speech:
- Scp049
# Whether or not MTF/CI can 'escape' while disarmed to switch teams.
disarm_switch_teams: true
# Whether or not disarmed people will be prevented from interacting with >
restrictive_disarming: true
# The text displayed at the timed interval specified below.
timed_broadcast: <color=lime>This server is running </color><color=red>EX>
# The time each timed broadcast will be displayed.
timed_broadcast_duration: 5
# The delay between each timed broadcast. To disable timed broadcasts, se>
timed_broadcast_delay: 300
# The message displayed to the player when they first join the server. Se>
join_message: <color=lime>Welcome %player%! Please read our rules!</color>
# The amount of time (in seconds) the join message is displayed.
join_message_duration: 5
# The amount of time (in seconds) after the round starts, before the faci>
autonuke_time: 1500
# Wether or not the nuke should be unable to be disabled during the auto->
autonuke_lock: true
# The message given to all players when the auto-nuke is triggered. A dur>
autonuke_broadcast:
# The broadcast content
content: The auto nuke has been activated.
# The broadcast duration
duration: 10
# The broadcast type
type: Normal
# Indicates whether the broadcast should be shown or not
show: true
# Whether or not to show player's health under their name when you look a>
player_health_info: true
# Whether or not friendly fire should automatically turn on when a round >
friendly_fire_on_round_end: true
# The multiplier applied to radio battery usage. Set to 0 to disable radi>
# The multiplier applied to radio battery usage. Set to 0 to disable radi>
radio_battery_drain_multiplier: 1
# The color to use for lights while the warhead is active.
warhead_color:
r: 1
g: 0.2
b: 0.2
a: 1
# The maximum time, in seconds, that a player can be AFK before being kic>
afk_limit: 120
# The roles that are ignored by the AFK system.
afk_ignored_roles:
- Scp079
- Spectator
- Tutorial
# The list of starting items for roles. ItemName is the item to give them>
starting_inventories:
ClassD:
slot1:
- item_name: KeycardJanitor
chance: 10
group: none
- item_name: Coin
chance: 100
group: none
slot2:
- item_name: Flashlight
chance: 100
group: none
slot3: []
slot4: []
slot5: []
slot6: []
slot7: []
slot8: []
ammo:
- type: Ammo556x45
amount: 200
group: none
# The list of custom 914 recipies. Original is the item being upgraded, N>
scp914_item_changes:
Rough:
- original: KeycardO5
new: MicroHID
chance: 50
# The list of custom 914 recipies for roles. Original is the role to be c>
scp914_class_changes:
Rough:
- original: ClassD
new: Spectator
chance: 100
keep_inventory: true
# The list of 914 teleport settings. Note that if you set "zone" to anyth>
scp914_teleport_chances:
Rough:
- zone: Unspecified
room: LczClassDSpawn
offset:
x: 0
y: 0
z: 0
chance: 100
damage: 250
# A dictionary of random effects to apply to players when going through 9>
scp914_effect_chances:
Rough:
- effect: AmnesiaVision
chance: 100
duration: 0
# Determines if 914 effects are exclusive, meaning only one can be applie>
scp914_effects_exclusivity: false
# Whether or not SCPs are immune to effects gained from 914.
scps_immune_to914_effects: false
# The frequency (in seconds) between ragdoll cleanups. Set to 0 to disabl>
ragdoll_cleanup_delay: 0
# If ragdoll cleanup should only happen in the Pocket Dimension or not.
ragdoll_cleanup_only_pocket: false
# The frequency (in seconds) between item cleanups. Set to 0 to disable.
item_cleanup_delay: 0
# If item cleanup should only happen in the Pocket Dimension or not.
item_cleanup_only_pocket: false
# A list of all roles and their damage modifiers. The number here is a mu>
role_damage_multipliers:
Scp173: 1
# A list of all Weapons and their damage modifiers. The number here is a >
damage_multipliers:
E11Sr: 1
# A list of roles and how much health they should be given when they kill>
health_on_kill:
Scp173: 0
Scp939: 10
# A list of roles and what their default starting health should be.
health_values:
Scp173: 3200
NtfCaptain: 120
# If the plugin is enabled or not.
is_enabled: true
**EXILED Version:**6.0.0-beta.22
**Plugin Version:**7.0.2
**Results of `show plugins` command in console:**
- Required Exiled Version: 6.0.0.0
- Prefix: exiled_updater
- Priority: Medium
Exiled.Permissions:
- Author: Exiled Team
- Version: 6.0.0.0
- Required Exiled Version: 6.0.0.0
- Prefix: exiled_permissions
- Priority: Medium
Exiled.CreditTags:
- Author: Babyboucher20 & iRebbok & Exiled Team
- Version: 6.0.0.0
- Required Exiled Version: 6.0.0.0
- Prefix: exiled_credits
- Priority: Medium
Exiled.CustomItems:
- Author: Exiled Team
- Version: 6.0.0.0
- Required Exiled Version: 6.0.0.0
- Prefix: exiled_custom_items
- Priority: Medium
**Additional context**
Add any other context about the problem here.
|
1.0
|
[BUG] Plugin not loading - **Describe the bug**
A clear and concise description of what the bug is.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
**Expected behavior**
Plugin loading correctly
**Server logs**
```[2023-01-16 22:06:20.516 +00:00] [ERROR] [Exiled.Loader] Plugin "Common Utilities" threw an exception while enabling: System.TypeLoadException: Could not resolve type with token 01000064 (from typeref, class/assembly Exiled.Events.EventArgs.Player.ThrownItemEventArgs, Exiled.Events, Version=6.0.0.0, Culture=neutral> at Exiled.Loader.Loader.EnablePlugins () [0x000a8] in <45764f9e3028450f9a5d618968896851>:0
```
**Copy of current CU config section**
CommonUtilities:
# Whether or not debug messages should be shown.
debug: false
# The SCP Roles able to use V to talk to humans.
scp_speech:
- Scp049
# Whether or not MTF/CI can 'escape' while disarmed to switch teams.
disarm_switch_teams: true
# Whether or not disarmed people will be prevented from interacting with >
restrictive_disarming: true
# The text displayed at the timed interval specified below.
timed_broadcast: <color=lime>This server is running </color><color=red>EX>
# The time each timed broadcast will be displayed.
timed_broadcast_duration: 5
# The delay between each timed broadcast. To disable timed broadcasts, se>
timed_broadcast_delay: 300
# The message displayed to the player when they first join the server. Se>
join_message: <color=lime>Welcome %player%! Please read our rules!</color>
# The amount of time (in seconds) the join message is displayed.
join_message_duration: 5
# The amount of time (in seconds) after the round starts, before the faci>
autonuke_time: 1500
# Wether or not the nuke should be unable to be disabled during the auto->
autonuke_lock: true
# The message given to all players when the auto-nuke is triggered. A dur>
autonuke_broadcast:
# The broadcast content
content: The auto nuke has been activated.
# The broadcast duration
duration: 10
# The broadcast type
type: Normal
# Indicates whether the broadcast should be shown or not
show: true
# Whether or not to show player's health under their name when you look a>
player_health_info: true
# Whether or not friendly fire should automatically turn on when a round >
friendly_fire_on_round_end: true
# The multiplier applied to radio battery usage. Set to 0 to disable radi>
# The multiplier applied to radio battery usage. Set to 0 to disable radi>
radio_battery_drain_multiplier: 1
# The color to use for lights while the warhead is active.
warhead_color:
r: 1
g: 0.2
b: 0.2
a: 1
# The maximum time, in seconds, that a player can be AFK before being kic>
afk_limit: 120
# The roles that are ignored by the AFK system.
afk_ignored_roles:
- Scp079
- Spectator
- Tutorial
# The list of starting items for roles. ItemName is the item to give them>
starting_inventories:
ClassD:
slot1:
- item_name: KeycardJanitor
chance: 10
group: none
- item_name: Coin
chance: 100
group: none
slot2:
- item_name: Flashlight
chance: 100
group: none
slot3: []
slot4: []
slot5: []
slot6: []
slot7: []
slot8: []
ammo:
- type: Ammo556x45
amount: 200
group: none
# The list of custom 914 recipies. Original is the item being upgraded, N>
scp914_item_changes:
Rough:
- original: KeycardO5
new: MicroHID
chance: 50
# The list of custom 914 recipies for roles. Original is the role to be c>
scp914_class_changes:
Rough:
- original: ClassD
new: Spectator
chance: 100
keep_inventory: true
# The list of 914 teleport settings. Note that if you set "zone" to anyth>
scp914_teleport_chances:
Rough:
- zone: Unspecified
room: LczClassDSpawn
offset:
x: 0
y: 0
z: 0
chance: 100
damage: 250
# A dictionary of random effects to apply to players when going through 9>
scp914_effect_chances:
Rough:
- effect: AmnesiaVision
chance: 100
duration: 0
# Determines if 914 effects are exclusive, meaning only one can be applie>
scp914_effects_exclusivity: false
# Whether or not SCPs are immune to effects gained from 914.
scps_immune_to914_effects: false
# The frequency (in seconds) between ragdoll cleanups. Set to 0 to disabl>
ragdoll_cleanup_delay: 0
# If ragdoll cleanup should only happen in the Pocket Dimension or not.
ragdoll_cleanup_only_pocket: false
# The frequency (in seconds) between item cleanups. Set to 0 to disable.
item_cleanup_delay: 0
# If item cleanup should only happen in the Pocket Dimension or not.
item_cleanup_only_pocket: false
# A list of all roles and their damage modifiers. The number here is a mu>
role_damage_multipliers:
Scp173: 1
# A list of all Weapons and their damage modifiers. The number here is a >
damage_multipliers:
E11Sr: 1
# A list of roles and how much health they should be given when they kill>
health_on_kill:
Scp173: 0
Scp939: 10
# A list of roles and what their default starting health should be.
health_values:
Scp173: 3200
NtfCaptain: 120
# If the plugin is enabled or not.
is_enabled: true
**EXILED Version:**6.0.0-beta.22
**Plugin Version:**7.0.2
**Results of `show plugins` command in console:**
- Required Exiled Version: 6.0.0.0
- Prefix: exiled_updater
- Priority: Medium
Exiled.Permissions:
- Author: Exiled Team
- Version: 6.0.0.0
- Required Exiled Version: 6.0.0.0
- Prefix: exiled_permissions
- Priority: Medium
Exiled.CreditTags:
- Author: Babyboucher20 & iRebbok & Exiled Team
- Version: 6.0.0.0
- Required Exiled Version: 6.0.0.0
- Prefix: exiled_credits
- Priority: Medium
Exiled.CustomItems:
- Author: Exiled Team
- Version: 6.0.0.0
- Required Exiled Version: 6.0.0.0
- Prefix: exiled_custom_items
- Priority: Medium
**Additional context**
Add any other context about the problem here.
|
non_process
|
plugin not loading describe the bug a clear and concise description of what the bug is to reproduce steps to reproduce the behavior go to click on scroll down to see error expected behavior plugin loading correctly server logs plugin common utilities threw an exception while enabling system typeloadexception could not resolve type with token from typeref class assembly exiled events eventargs player thrownitemeventargs exiled events version culture neutral at exiled loader loader enableplugins in copy of current cu config section commonutilities whether or not debug messages should be shown debug false the scp roles able to use v to talk to humans scp speech whether or not mtf ci can escape while disarmed to switch teams disarm switch teams true whether or not disarmed people will be prevented from interacting with restrictive disarming true the text displayed at the timed interval specified below timed broadcast this server is running ex the time each timed broadcast will be displayed timed broadcast duration the delay between each timed broadcast to disable timed broadcasts se timed broadcast delay the message displayed to the player when they first join the server se join message welcome player please read our rules the amount of time in seconds the join message is displayed join message duration the amount of time in seconds after the round starts before the faci autonuke time wether or not the nuke should be unable to be disabled during the auto autonuke lock true the message given to all players when the auto nuke is triggered a dur autonuke broadcast the broadcast content content the auto nuke has been activated the broadcast duration duration the broadcast type type normal indicates whether the broadcast should be shown or not show true whether or not to show player s health under their name when you look a player health info true whether or not friendly fire should automatically turn on when a round friendly fire on round end true the multiplier applied to radio battery usage set to to disable radi the multiplier applied to radio battery usage set to to disable radi radio battery drain multiplier the color to use for lights while the warhead is active warhead color r g b a the maximum time in seconds that a player can be afk before being kic afk limit the roles that are ignored by the afk system afk ignored roles spectator tutorial the list of starting items for roles itemname is the item to give them starting inventories classd item name keycardjanitor chance group none item name coin chance group none item name flashlight chance group none ammo type amount group none the list of custom recipies original is the item being upgraded n item changes rough original new microhid chance the list of custom recipies for roles original is the role to be c class changes rough original classd new spectator chance keep inventory true the list of teleport settings note that if you set zone to anyth teleport chances rough zone unspecified room lczclassdspawn offset x y z chance damage a dictionary of random effects to apply to players when going through effect chances rough effect amnesiavision chance duration determines if effects are exclusive meaning only one can be applie effects exclusivity false whether or not scps are immune to effects gained from scps immune effects false the frequency in seconds between ragdoll cleanups set to to disabl ragdoll cleanup delay if ragdoll cleanup should only happen in the pocket dimension or not ragdoll cleanup only pocket false the frequency in seconds between item cleanups set to to disable item cleanup delay if item cleanup should only happen in the pocket dimension or not item cleanup only pocket false a list of all roles and their damage modifiers the number here is a mu role damage multipliers a list of all weapons and their damage modifiers the number here is a damage multipliers a list of roles and how much health they should be given when they kill health on kill a list of roles and what their default starting health should be health values ntfcaptain if the plugin is enabled or not is enabled true exiled version beta plugin version results of show plugins command in console required exiled version prefix exiled updater priority medium exiled permissions author exiled team version required exiled version prefix exiled permissions priority medium exiled credittags author irebbok exiled team version required exiled version prefix exiled credits priority medium exiled customitems author exiled team version required exiled version prefix exiled custom items priority medium additional context add any other context about the problem here
| 0
|
13,998
| 16,772,057,026
|
IssuesEvent
|
2021-06-14 15:52:42
|
prisma/prisma
|
https://api.github.com/repos/prisma/prisma
|
opened
|
Internal: client fixtures fail to generate
|
kind/bug process/candidate team/client topic: internal topic: tests
|
### Bug description
I followed the instructions from https://github.com/prisma/prisma/blob/master/CONTRIBUTING.md
But the generate fixtures doesn't work anymore, it fails with this on my machine (macOS)
```
npx ts-node fixtures/generate.ts ./fixtures/blog/ --skip-transpile
[Error: ENOENT: no such file or directory, copyfile 'fixtures/blog/prisma/schema.prisma' -> 'fixtures/blog/@prisma/client/schema.prisma'] {
errno: -2,
code: 'ENOENT',
syscall: 'copyfile',
path: 'fixtures/blog/prisma/schema.prisma',
dest: 'fixtures/blog/@prisma/client/schema.prisma'
}
```
I’m ok to use something else but would be great to have it set up in the repo, I don’t want to create a custom dir and do manual stuff when I need it, basically, I would want to just run generate and be good to go.
### How to reproduce
<!--
1. Go to '...'
2. Change '....'
3. Run '....'
4. See error
-->
### Expected behavior
_No response_
### Prisma information
<!-- Do not include your database credentials when sharing your Prisma schema! -->
### Environment & setup
- OS: <!--[e.g. Mac OS, Windows, Debian, CentOS, ...]-->
- Database: <!--[PostgreSQL, MySQL, MariaDB or SQLite]-->
- Node.js version: <!--[Run `node -v` to see your Node.js version]-->
### Prisma Version
```
```
|
1.0
|
Internal: client fixtures fail to generate - ### Bug description
I followed the instructions from https://github.com/prisma/prisma/blob/master/CONTRIBUTING.md
But the generate fixtures doesn't work anymore, it fails with this on my machine (macOS)
```
npx ts-node fixtures/generate.ts ./fixtures/blog/ --skip-transpile
[Error: ENOENT: no such file or directory, copyfile 'fixtures/blog/prisma/schema.prisma' -> 'fixtures/blog/@prisma/client/schema.prisma'] {
errno: -2,
code: 'ENOENT',
syscall: 'copyfile',
path: 'fixtures/blog/prisma/schema.prisma',
dest: 'fixtures/blog/@prisma/client/schema.prisma'
}
```
I’m ok to use something else but would be great to have it set up in the repo, I don’t want to create a custom dir and do manual stuff when I need it, basically, I would want to just run generate and be good to go.
### How to reproduce
<!--
1. Go to '...'
2. Change '....'
3. Run '....'
4. See error
-->
### Expected behavior
_No response_
### Prisma information
<!-- Do not include your database credentials when sharing your Prisma schema! -->
### Environment & setup
- OS: <!--[e.g. Mac OS, Windows, Debian, CentOS, ...]-->
- Database: <!--[PostgreSQL, MySQL, MariaDB or SQLite]-->
- Node.js version: <!--[Run `node -v` to see your Node.js version]-->
### Prisma Version
```
```
|
process
|
internal client fixtures fail to generate bug description i followed the instructions from but the generate fixtures doesn t work anymore it fails with this on my machine macos npx ts node fixtures generate ts fixtures blog skip transpile errno code enoent syscall copyfile path fixtures blog prisma schema prisma dest fixtures blog prisma client schema prisma i’m ok to use something else but would be great to have it set up in the repo i don’t want to create a custom dir and do manual stuff when i need it basically i would want to just run generate and be good to go how to reproduce go to change run see error expected behavior no response prisma information environment setup os database node js version prisma version
| 1
|
116,596
| 9,856,940,140
|
IssuesEvent
|
2019-06-20 00:18:08
|
medic/medic
|
https://api.github.com/repos/medic/medic
|
closed
|
e2e tests fail at 0000 GMT on travis
|
Priority: 2 - Medium Testing Type: Technical issue
|
I've noticed this a few times. Restarting the build fixes it.
```
registration transition
submits new sms messages
✗ shows content (10 secs)
- Expected 'LMP Alh, Jan 2, 2020' to be 'LMP Jtan, Jan 1, 2020'.
at checkAutoResponse (/home/travis/build/medic/medic/tests/e2e/registration-by-sms.js:268:95)
at UserContext.it (/home/travis/build/medic/medic/tests/e2e/registration-by-sms.js:291:7)
at /home/travis/build/medic/medic/node_modules/jasminewd2/index.js:112:25
at new ManagedPromise (/home/travis/build/medic/medic/node_modules/selenium-webdriver/lib/promise.js:1077:7)
at ControlFlow.promise (/home/travis/build/medic/medic/node_modules/selenium-webdriver/lib/promise.js:2505:12)
at schedulerExecute (/home/travis/build/medic/medic/node_modules/jasminewd2/index.js:95:18)
at TaskQueue.execute_ (/home/travis/build/medic/medic/node_modules/selenium-webdriver/lib/promise.js:3084:14)
at TaskQueue.executeNext_ (/home/travis/build/medic/medic/node_modules/selenium-webdriver/lib/promise.js:3067:27)
at asyncRun (/home/travis/build/medic/medic/node_modules/selenium-webdriver/lib/promise.js:2974:25)
at /home/travis/build/medic/medic/node_modules/selenium-webdriver/lib/promise.js:668:7
- Expected 'LMP Alh, Jan 2, 2020' to be 'LMP Jtan, Jan 1, 2020'.
at checkScheduledTask (/home/travis/build/medic/medic/tests/e2e/registration-by-sms.js:276:80)
at UserContext.it (/home/travis/build/medic/medic/tests/e2e/registration-by-sms.js:294:7)
at /home/travis/build/medic/medic/node_modules/jasminewd2/index.js:112:25
at new ManagedPromise (/home/travis/build/medic/medic/node_modules/selenium-webdriver/lib/promise.js:1077:7)
at ControlFlow.promise (/home/travis/build/medic/medic/node_modules/selenium-webdriver/lib/promise.js:2505:12)
at schedulerExecute (/home/travis/build/medic/medic/node_modules/jasminewd2/index.js:95:18)
at TaskQueue.execute_ (/home/travis/build/medic/medic/node_modules/selenium-webdriver/lib/promise.js:3084:14)
at TaskQueue.executeNext_ (/home/travis/build/medic/medic/node_modules/selenium-webdriver/lib/promise.js:3067:27)
at asyncRun (/home/travis/build/medic/medic/node_modules/selenium-webdriver/lib/promise.js:2974:25)
at /home/travis/build/medic/medic/node_modules/selenium-webdriver/lib/promise.js:668:7
```
|
1.0
|
e2e tests fail at 0000 GMT on travis - I've noticed this a few times. Restarting the build fixes it.
```
registration transition
submits new sms messages
✗ shows content (10 secs)
- Expected 'LMP Alh, Jan 2, 2020' to be 'LMP Jtan, Jan 1, 2020'.
at checkAutoResponse (/home/travis/build/medic/medic/tests/e2e/registration-by-sms.js:268:95)
at UserContext.it (/home/travis/build/medic/medic/tests/e2e/registration-by-sms.js:291:7)
at /home/travis/build/medic/medic/node_modules/jasminewd2/index.js:112:25
at new ManagedPromise (/home/travis/build/medic/medic/node_modules/selenium-webdriver/lib/promise.js:1077:7)
at ControlFlow.promise (/home/travis/build/medic/medic/node_modules/selenium-webdriver/lib/promise.js:2505:12)
at schedulerExecute (/home/travis/build/medic/medic/node_modules/jasminewd2/index.js:95:18)
at TaskQueue.execute_ (/home/travis/build/medic/medic/node_modules/selenium-webdriver/lib/promise.js:3084:14)
at TaskQueue.executeNext_ (/home/travis/build/medic/medic/node_modules/selenium-webdriver/lib/promise.js:3067:27)
at asyncRun (/home/travis/build/medic/medic/node_modules/selenium-webdriver/lib/promise.js:2974:25)
at /home/travis/build/medic/medic/node_modules/selenium-webdriver/lib/promise.js:668:7
- Expected 'LMP Alh, Jan 2, 2020' to be 'LMP Jtan, Jan 1, 2020'.
at checkScheduledTask (/home/travis/build/medic/medic/tests/e2e/registration-by-sms.js:276:80)
at UserContext.it (/home/travis/build/medic/medic/tests/e2e/registration-by-sms.js:294:7)
at /home/travis/build/medic/medic/node_modules/jasminewd2/index.js:112:25
at new ManagedPromise (/home/travis/build/medic/medic/node_modules/selenium-webdriver/lib/promise.js:1077:7)
at ControlFlow.promise (/home/travis/build/medic/medic/node_modules/selenium-webdriver/lib/promise.js:2505:12)
at schedulerExecute (/home/travis/build/medic/medic/node_modules/jasminewd2/index.js:95:18)
at TaskQueue.execute_ (/home/travis/build/medic/medic/node_modules/selenium-webdriver/lib/promise.js:3084:14)
at TaskQueue.executeNext_ (/home/travis/build/medic/medic/node_modules/selenium-webdriver/lib/promise.js:3067:27)
at asyncRun (/home/travis/build/medic/medic/node_modules/selenium-webdriver/lib/promise.js:2974:25)
at /home/travis/build/medic/medic/node_modules/selenium-webdriver/lib/promise.js:668:7
```
|
non_process
|
tests fail at gmt on travis i ve noticed this a few times restarting the build fixes it registration transition submits new sms messages ✗ shows content secs expected lmp alh jan to be lmp jtan jan at checkautoresponse home travis build medic medic tests registration by sms js at usercontext it home travis build medic medic tests registration by sms js at home travis build medic medic node modules index js at new managedpromise home travis build medic medic node modules selenium webdriver lib promise js at controlflow promise home travis build medic medic node modules selenium webdriver lib promise js at schedulerexecute home travis build medic medic node modules index js at taskqueue execute home travis build medic medic node modules selenium webdriver lib promise js at taskqueue executenext home travis build medic medic node modules selenium webdriver lib promise js at asyncrun home travis build medic medic node modules selenium webdriver lib promise js at home travis build medic medic node modules selenium webdriver lib promise js expected lmp alh jan to be lmp jtan jan at checkscheduledtask home travis build medic medic tests registration by sms js at usercontext it home travis build medic medic tests registration by sms js at home travis build medic medic node modules index js at new managedpromise home travis build medic medic node modules selenium webdriver lib promise js at controlflow promise home travis build medic medic node modules selenium webdriver lib promise js at schedulerexecute home travis build medic medic node modules index js at taskqueue execute home travis build medic medic node modules selenium webdriver lib promise js at taskqueue executenext home travis build medic medic node modules selenium webdriver lib promise js at asyncrun home travis build medic medic node modules selenium webdriver lib promise js at home travis build medic medic node modules selenium webdriver lib promise js
| 0
|
430,726
| 30,196,651,939
|
IssuesEvent
|
2023-07-04 22:17:46
|
javalent/dice-roller
|
https://api.github.com/repos/javalent/dice-roller
|
closed
|
[Basic Usage]: Table Roller doesn't work/is confusing to use
|
bug documentation
|
### Check for existing bug reports before submitting.
- [X] I searched for existing [Bug Reports](https://github.com/javalent/dice-roller/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-descc) and found no similar reports.
### Expected Behavior
I've copy-pasted multiple examples from the documentation directly into my markdown, yet it doesn't render.
The [documentation](https://plugins.javalent.com/dice/rollers/table) or [documentation for lists](https://plugins.javalent.com/dice/rollers/list), both says to simply make a table/list and reference it in a codeblock. Like so:
```
| Header |
| A |
| B |
```
Or
```
- a
- b
- c
- d
```
And then reference it in another note like so:
`dice: [[Note^block-id]]`
### Current behaviour
A simple roll like so:
`dice: 1d4`
...works as intended.
But any kind of reference simply loads the entire file, and the dice graphic does nothing when clicked.
[Image](https://i.imgur.com/otf99Hg.png)
I've now tried simply copy pasting the _exact_ examples in the documentation, but [it doesn't render anything from the note at all](https://i.imgur.com/S6VJkEj.png).
### Reproduction
Copy and paste the [documentation](https://plugins.javalent.com/dice/rollers/list) [examples](https://plugins.javalent.com/dice/rollers/table), and notice that they fail or doesn't work as intended.
### Which Operating Systems are you using?
- [ ] Android
- [ ] iPhone/iPad
- [ ] Linux
- [ ] macOS
- [X] Windows
### Obsidian Version Check
1.3.5
### Plugin Version
8.17.0
### Confirmation
- [X] I have disabled all other plugins and the issue still persists.
### Possible solution
_No response_
|
1.0
|
[Basic Usage]: Table Roller doesn't work/is confusing to use - ### Check for existing bug reports before submitting.
- [X] I searched for existing [Bug Reports](https://github.com/javalent/dice-roller/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-descc) and found no similar reports.
### Expected Behavior
I've copy-pasted multiple examples from the documentation directly into my markdown, yet it doesn't render.
The [documentation](https://plugins.javalent.com/dice/rollers/table) or [documentation for lists](https://plugins.javalent.com/dice/rollers/list), both says to simply make a table/list and reference it in a codeblock. Like so:
```
| Header |
| A |
| B |
```
Or
```
- a
- b
- c
- d
```
And then reference it in another note like so:
`dice: [[Note^block-id]]`
### Current behaviour
A simple roll like so:
`dice: 1d4`
...works as intended.
But any kind of reference simply loads the entire file, and the dice graphic does nothing when clicked.
[Image](https://i.imgur.com/otf99Hg.png)
I've now tried simply copy pasting the _exact_ examples in the documentation, but [it doesn't render anything from the note at all](https://i.imgur.com/S6VJkEj.png).
### Reproduction
Copy and paste the [documentation](https://plugins.javalent.com/dice/rollers/list) [examples](https://plugins.javalent.com/dice/rollers/table), and notice that they fail or doesn't work as intended.
### Which Operating Systems are you using?
- [ ] Android
- [ ] iPhone/iPad
- [ ] Linux
- [ ] macOS
- [X] Windows
### Obsidian Version Check
1.3.5
### Plugin Version
8.17.0
### Confirmation
- [X] I have disabled all other plugins and the issue still persists.
### Possible solution
_No response_
|
non_process
|
table roller doesn t work is confusing to use check for existing bug reports before submitting i searched for existing and found no similar reports expected behavior i ve copy pasted multiple examples from the documentation directly into my markdown yet it doesn t render the or both says to simply make a table list and reference it in a codeblock like so header a b or a b c d and then reference it in another note like so dice current behaviour a simple roll like so dice works as intended but any kind of reference simply loads the entire file and the dice graphic does nothing when clicked i ve now tried simply copy pasting the exact examples in the documentation but reproduction copy and paste the and notice that they fail or doesn t work as intended which operating systems are you using android iphone ipad linux macos windows obsidian version check plugin version confirmation i have disabled all other plugins and the issue still persists possible solution no response
| 0
|
1,424
| 3,989,431,961
|
IssuesEvent
|
2016-05-09 14:01:00
|
mitchellh/packer
|
https://api.github.com/repos/mitchellh/packer
|
closed
|
`amazon-import` - Importing to Multiple Regions?
|
post-processor/amazon-import question
|
What's the best method for using amazon-import with multiple regions? I currently have the following:
```
"post-processors": [
[{
"type": "amazon-import",
"access_key": "{{user `aws_access_key`}}",
"secret_key": "{{user `aws_secret_key`}}",
"region": "us-east-1",
"s3_bucket_name": "{{user `s3_bucket_name`}}",
"s3_key_name": "{{user `s3_key_name`}}"
},
{
"type": "amazon-import",
"access_key": "{{user `aws_access_key`}}",
"secret_key": "{{user `aws_secret_key`}}",
"region": "us-west-1",
"s3_bucket_name": "{{user `s3_bucket_name`}}",
"s3_key_name": "{{user `s3_key_name`}}"
}]
],
```
However, I then get the following error on the second import: `* Post-processor failed: No OVA file found in artifact from builder`.
Is there a better way to do this?
|
1.0
|
`amazon-import` - Importing to Multiple Regions? - What's the best method for using amazon-import with multiple regions? I currently have the following:
```
"post-processors": [
[{
"type": "amazon-import",
"access_key": "{{user `aws_access_key`}}",
"secret_key": "{{user `aws_secret_key`}}",
"region": "us-east-1",
"s3_bucket_name": "{{user `s3_bucket_name`}}",
"s3_key_name": "{{user `s3_key_name`}}"
},
{
"type": "amazon-import",
"access_key": "{{user `aws_access_key`}}",
"secret_key": "{{user `aws_secret_key`}}",
"region": "us-west-1",
"s3_bucket_name": "{{user `s3_bucket_name`}}",
"s3_key_name": "{{user `s3_key_name`}}"
}]
],
```
However, I then get the following error on the second import: `* Post-processor failed: No OVA file found in artifact from builder`.
Is there a better way to do this?
|
process
|
amazon import importing to multiple regions what s the best method for using amazon import with multiple regions i currently have the following post processors type amazon import access key user aws access key secret key user aws secret key region us east bucket name user bucket name key name user key name type amazon import access key user aws access key secret key user aws secret key region us west bucket name user bucket name key name user key name however i then get the following error on the second import post processor failed no ova file found in artifact from builder is there a better way to do this
| 1
|
78,677
| 22,345,917,609
|
IssuesEvent
|
2022-06-15 07:47:52
|
cocos/cocos-engine
|
https://api.github.com/repos/cocos/cocos-engine
|
closed
|
Should not export atlas plist raw file when building project
|
Bug P2 Module: 2D Editor Module: Build
|
### Cocos Creator version
3.5.0
### System information
WeChat Mini Game & Android
### Issue description
This file is useless, since we already import plist as SpriteAtlas object.
Re: https://forum.cocos.org/t/topic/135525/14?u=jare
### Relevant error log output
_No response_
### Steps to reproduce
nope
### Minimal reproduction project
_No response_
|
1.0
|
Should not export atlas plist raw file when building project - ### Cocos Creator version
3.5.0
### System information
WeChat Mini Game & Android
### Issue description
This file is useless, since we already import plist as SpriteAtlas object.
Re: https://forum.cocos.org/t/topic/135525/14?u=jare
### Relevant error log output
_No response_
### Steps to reproduce
nope
### Minimal reproduction project
_No response_
|
non_process
|
should not export atlas plist raw file when building project cocos creator version system information wechat mini game android issue description this file is useless since we already import plist as spriteatlas object re relevant error log output no response steps to reproduce nope minimal reproduction project no response
| 0
|
17,362
| 23,186,047,728
|
IssuesEvent
|
2022-08-01 08:28:35
|
streamnative/flink
|
https://api.github.com/repos/streamnative/flink
|
closed
|
[SQL Connector] when documentation is reviewed, merge back the SN hub documentation to the flink repo and replace the README.md
|
compute/data-processing
|
Also investigate the auto documentation publish pipeline
|
1.0
|
[SQL Connector] when documentation is reviewed, merge back the SN hub documentation to the flink repo and replace the README.md - Also investigate the auto documentation publish pipeline
|
process
|
when documentation is reviewed merge back the sn hub documentation to the flink repo and replace the readme md also investigate the auto documentation publish pipeline
| 1
|
21,850
| 14,898,562,110
|
IssuesEvent
|
2021-01-21 13:17:36
|
spring-projects/spring-batch
|
https://api.github.com/repos/spring-projects/spring-batch
|
closed
|
Provide a way to specify the class loader to be used by a ClassPathXmlApplicationContextFactory [BATCH-2182]
|
in: infrastructure status: waiting-for-triage type: enhancement
|
**[Mauro Molinari](https://jira.spring.io/secure/ViewProfile.jspa?name=mauromol)** opened **[BATCH-2182](https://jira.spring.io/browse/BATCH-2182?redirect=false)** and commented
A `ClassPathXmlApplicationContextFactory` creates `ClassPathXmlApplicationContext` instances. The latter, by extending `DefaultResourceLoader` would allow to specify the class loader to use to locate resources. It would be very useful if the factory and the corresponding `ClasspathXmlApplicationContextsFactoryBean` (which, IMHO, should better be called `ClassPathXmlApplicationContextFactoryFactoryBean`, since it's a `FactoryBean` that creates factories and also would need an upper case "P" in "ClassPath") allowed to specify the class loader to use. This would allow to create an `AutomaticJobRegistrar` which registers jobs defined in child contexts loaded through a suitable class loader (which may in turn load classes at runtime from hot-deployed JARs, for instance).
Being able to specify just one class loader on the FactoryBean for all created factories would be better than nothing.
Right now I have to write my own FactoryBean and factory to achieve this, but I think that supporting this out-of-the-box should be quite simple and valuable.
By the way, I see that with 3.0.0.M2 `ClassPathXmlApplicationContextFactory` has been deprecated in favour of `GenericApplicationContextFactory`, which creates generic `ConfigurableApplicationContexts`. This enhancement might give a reason to revert the deprecation on `ClassPathXmlApplicationContextFactory` and add some additional value to it...
---
**Affects:** 2.1.9
|
1.0
|
Provide a way to specify the class loader to be used by a ClassPathXmlApplicationContextFactory [BATCH-2182] - **[Mauro Molinari](https://jira.spring.io/secure/ViewProfile.jspa?name=mauromol)** opened **[BATCH-2182](https://jira.spring.io/browse/BATCH-2182?redirect=false)** and commented
A `ClassPathXmlApplicationContextFactory` creates `ClassPathXmlApplicationContext` instances. The latter, by extending `DefaultResourceLoader` would allow to specify the class loader to use to locate resources. It would be very useful if the factory and the corresponding `ClasspathXmlApplicationContextsFactoryBean` (which, IMHO, should better be called `ClassPathXmlApplicationContextFactoryFactoryBean`, since it's a `FactoryBean` that creates factories and also would need an upper case "P" in "ClassPath") allowed to specify the class loader to use. This would allow to create an `AutomaticJobRegistrar` which registers jobs defined in child contexts loaded through a suitable class loader (which may in turn load classes at runtime from hot-deployed JARs, for instance).
Being able to specify just one class loader on the FactoryBean for all created factories would be better than nothing.
Right now I have to write my own FactoryBean and factory to achieve this, but I think that supporting this out-of-the-box should be quite simple and valuable.
By the way, I see that with 3.0.0.M2 `ClassPathXmlApplicationContextFactory` has been deprecated in favour of `GenericApplicationContextFactory`, which creates generic `ConfigurableApplicationContexts`. This enhancement might give a reason to revert the deprecation on `ClassPathXmlApplicationContextFactory` and add some additional value to it...
---
**Affects:** 2.1.9
|
non_process
|
provide a way to specify the class loader to be used by a classpathxmlapplicationcontextfactory opened and commented a classpathxmlapplicationcontextfactory creates classpathxmlapplicationcontext instances the latter by extending defaultresourceloader would allow to specify the class loader to use to locate resources it would be very useful if the factory and the corresponding classpathxmlapplicationcontextsfactorybean which imho should better be called classpathxmlapplicationcontextfactoryfactorybean since it s a factorybean that creates factories and also would need an upper case p in classpath allowed to specify the class loader to use this would allow to create an automaticjobregistrar which registers jobs defined in child contexts loaded through a suitable class loader which may in turn load classes at runtime from hot deployed jars for instance being able to specify just one class loader on the factorybean for all created factories would be better than nothing right now i have to write my own factorybean and factory to achieve this but i think that supporting this out of the box should be quite simple and valuable by the way i see that with classpathxmlapplicationcontextfactory has been deprecated in favour of genericapplicationcontextfactory which creates generic configurableapplicationcontexts this enhancement might give a reason to revert the deprecation on classpathxmlapplicationcontextfactory and add some additional value to it affects
| 0
|
25,676
| 11,207,764,298
|
IssuesEvent
|
2020-01-06 05:15:48
|
emilwareus/NodeGoat
|
https://api.github.com/repos/emilwareus/NodeGoat
|
opened
|
CVE-2019-20149 (Medium) detected in multiple libraries
|
security vulnerability
|
## CVE-2019-20149 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>kind-of-3.2.2.tgz</b>, <b>kind-of-4.0.0.tgz</b>, <b>kind-of-6.0.2.tgz</b>, <b>kind-of-3.0.3.tgz</b>, <b>kind-of-5.1.0.tgz</b></p></summary>
<p>
<details><summary><b>kind-of-3.2.2.tgz</b></p></summary>
<p>Get the native type of a value.</p>
<p>Library home page: <a href="https://registry.npmjs.org/kind-of/-/kind-of-3.2.2.tgz">https://registry.npmjs.org/kind-of/-/kind-of-3.2.2.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/NodeGoat/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/NodeGoat/node_modules/readdirp/node_modules/is-number/node_modules/kind-of/package.json</p>
<p>
Dependency Hierarchy:
- grunt-cli-1.3.2.tgz (Root Library)
- liftoff-2.5.0.tgz
- findup-sync-2.0.0.tgz
- micromatch-3.1.10.tgz
- extglob-2.0.4.tgz
- expand-brackets-2.1.4.tgz
- define-property-0.2.5.tgz
- is-descriptor-0.1.6.tgz
- is-accessor-descriptor-0.1.6.tgz
- :x: **kind-of-3.2.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>kind-of-4.0.0.tgz</b></p></summary>
<p>Get the native type of a value.</p>
<p>Library home page: <a href="https://registry.npmjs.org/kind-of/-/kind-of-4.0.0.tgz">https://registry.npmjs.org/kind-of/-/kind-of-4.0.0.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/NodeGoat/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/NodeGoat/node_modules/has-values/node_modules/kind-of/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- braces-2.3.2.tgz
- snapdragon-0.8.2.tgz
- base-0.11.2.tgz
- cache-base-1.0.1.tgz
- has-value-1.0.0.tgz
- has-values-1.0.0.tgz
- :x: **kind-of-4.0.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>kind-of-6.0.2.tgz</b></p></summary>
<p>Get the native type of a value.</p>
<p>Library home page: <a href="https://registry.npmjs.org/kind-of/-/kind-of-6.0.2.tgz">https://registry.npmjs.org/kind-of/-/kind-of-6.0.2.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/NodeGoat/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/NodeGoat/node_modules/nodemon/node_modules/kind-of/package.json</p>
<p>
Dependency Hierarchy:
- grunt-cli-1.3.2.tgz (Root Library)
- liftoff-2.5.0.tgz
- findup-sync-2.0.0.tgz
- micromatch-3.1.10.tgz
- :x: **kind-of-6.0.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>kind-of-3.0.3.tgz</b></p></summary>
<p>Get the native type of a value.</p>
<p>Library home page: <a href="https://registry.npmjs.org/kind-of/-/kind-of-3.0.3.tgz">https://registry.npmjs.org/kind-of/-/kind-of-3.0.3.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/NodeGoat/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/NodeGoat/node_modules/nyc/node_modules/kind-of/package.json</p>
<p>
Dependency Hierarchy:
- grunt-if-0.2.0.tgz (Root Library)
- grunt-contrib-nodeunit-1.0.0.tgz
- nodeunit-0.9.5.tgz
- tap-7.1.2.tgz
- nyc-7.1.0.tgz
- micromatch-2.3.11.tgz
- :x: **kind-of-3.0.3.tgz** (Vulnerable Library)
</details>
<details><summary><b>kind-of-5.1.0.tgz</b></p></summary>
<p>Get the native type of a value.</p>
<p>Library home page: <a href="https://registry.npmjs.org/kind-of/-/kind-of-5.1.0.tgz">https://registry.npmjs.org/kind-of/-/kind-of-5.1.0.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/NodeGoat/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/NodeGoat/node_modules/nodemon/node_modules/expand-brackets/node_modules/kind-of/package.json</p>
<p>
Dependency Hierarchy:
- grunt-cli-1.3.2.tgz (Root Library)
- liftoff-2.5.0.tgz
- findup-sync-2.0.0.tgz
- micromatch-3.1.10.tgz
- extglob-2.0.4.tgz
- expand-brackets-2.1.4.tgz
- define-property-0.2.5.tgz
- is-descriptor-0.1.6.tgz
- :x: **kind-of-5.1.0.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/emilwareus/NodeGoat/commit/dfbd2d5093f62bf89420a345e69ef391c38d45e4">dfbd2d5093f62bf89420a345e69ef391c38d45e4</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
ctorName in index.js in kind-of v6.0.2 allows external user input to overwrite certain internal attributes via a conflicting name, as demonstrated by 'constructor': {'name':'Symbol'}. Hence, a crafted payload can overwrite this builtin attribute to manipulate the type detection result.
<p>Publish Date: 2019-12-30
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-20149>CVE-2019-20149</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2019-20149 (Medium) detected in multiple libraries - ## CVE-2019-20149 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>kind-of-3.2.2.tgz</b>, <b>kind-of-4.0.0.tgz</b>, <b>kind-of-6.0.2.tgz</b>, <b>kind-of-3.0.3.tgz</b>, <b>kind-of-5.1.0.tgz</b></p></summary>
<p>
<details><summary><b>kind-of-3.2.2.tgz</b></p></summary>
<p>Get the native type of a value.</p>
<p>Library home page: <a href="https://registry.npmjs.org/kind-of/-/kind-of-3.2.2.tgz">https://registry.npmjs.org/kind-of/-/kind-of-3.2.2.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/NodeGoat/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/NodeGoat/node_modules/readdirp/node_modules/is-number/node_modules/kind-of/package.json</p>
<p>
Dependency Hierarchy:
- grunt-cli-1.3.2.tgz (Root Library)
- liftoff-2.5.0.tgz
- findup-sync-2.0.0.tgz
- micromatch-3.1.10.tgz
- extglob-2.0.4.tgz
- expand-brackets-2.1.4.tgz
- define-property-0.2.5.tgz
- is-descriptor-0.1.6.tgz
- is-accessor-descriptor-0.1.6.tgz
- :x: **kind-of-3.2.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>kind-of-4.0.0.tgz</b></p></summary>
<p>Get the native type of a value.</p>
<p>Library home page: <a href="https://registry.npmjs.org/kind-of/-/kind-of-4.0.0.tgz">https://registry.npmjs.org/kind-of/-/kind-of-4.0.0.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/NodeGoat/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/NodeGoat/node_modules/has-values/node_modules/kind-of/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- braces-2.3.2.tgz
- snapdragon-0.8.2.tgz
- base-0.11.2.tgz
- cache-base-1.0.1.tgz
- has-value-1.0.0.tgz
- has-values-1.0.0.tgz
- :x: **kind-of-4.0.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>kind-of-6.0.2.tgz</b></p></summary>
<p>Get the native type of a value.</p>
<p>Library home page: <a href="https://registry.npmjs.org/kind-of/-/kind-of-6.0.2.tgz">https://registry.npmjs.org/kind-of/-/kind-of-6.0.2.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/NodeGoat/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/NodeGoat/node_modules/nodemon/node_modules/kind-of/package.json</p>
<p>
Dependency Hierarchy:
- grunt-cli-1.3.2.tgz (Root Library)
- liftoff-2.5.0.tgz
- findup-sync-2.0.0.tgz
- micromatch-3.1.10.tgz
- :x: **kind-of-6.0.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>kind-of-3.0.3.tgz</b></p></summary>
<p>Get the native type of a value.</p>
<p>Library home page: <a href="https://registry.npmjs.org/kind-of/-/kind-of-3.0.3.tgz">https://registry.npmjs.org/kind-of/-/kind-of-3.0.3.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/NodeGoat/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/NodeGoat/node_modules/nyc/node_modules/kind-of/package.json</p>
<p>
Dependency Hierarchy:
- grunt-if-0.2.0.tgz (Root Library)
- grunt-contrib-nodeunit-1.0.0.tgz
- nodeunit-0.9.5.tgz
- tap-7.1.2.tgz
- nyc-7.1.0.tgz
- micromatch-2.3.11.tgz
- :x: **kind-of-3.0.3.tgz** (Vulnerable Library)
</details>
<details><summary><b>kind-of-5.1.0.tgz</b></p></summary>
<p>Get the native type of a value.</p>
<p>Library home page: <a href="https://registry.npmjs.org/kind-of/-/kind-of-5.1.0.tgz">https://registry.npmjs.org/kind-of/-/kind-of-5.1.0.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/NodeGoat/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/NodeGoat/node_modules/nodemon/node_modules/expand-brackets/node_modules/kind-of/package.json</p>
<p>
Dependency Hierarchy:
- grunt-cli-1.3.2.tgz (Root Library)
- liftoff-2.5.0.tgz
- findup-sync-2.0.0.tgz
- micromatch-3.1.10.tgz
- extglob-2.0.4.tgz
- expand-brackets-2.1.4.tgz
- define-property-0.2.5.tgz
- is-descriptor-0.1.6.tgz
- :x: **kind-of-5.1.0.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/emilwareus/NodeGoat/commit/dfbd2d5093f62bf89420a345e69ef391c38d45e4">dfbd2d5093f62bf89420a345e69ef391c38d45e4</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
ctorName in index.js in kind-of v6.0.2 allows external user input to overwrite certain internal attributes via a conflicting name, as demonstrated by 'constructor': {'name':'Symbol'}. Hence, a crafted payload can overwrite this builtin attribute to manipulate the type detection result.
<p>Publish Date: 2019-12-30
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-20149>CVE-2019-20149</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_process
|
cve medium detected in multiple libraries cve medium severity vulnerability vulnerable libraries kind of tgz kind of tgz kind of tgz kind of tgz kind of tgz kind of tgz get the native type of a value library home page a href path to dependency file tmp ws scm nodegoat package json path to vulnerable library tmp ws scm nodegoat node modules readdirp node modules is number node modules kind of package json dependency hierarchy grunt cli tgz root library liftoff tgz findup sync tgz micromatch tgz extglob tgz expand brackets tgz define property tgz is descriptor tgz is accessor descriptor tgz x kind of tgz vulnerable library kind of tgz get the native type of a value library home page a href path to dependency file tmp ws scm nodegoat package json path to vulnerable library tmp ws scm nodegoat node modules has values node modules kind of package json dependency hierarchy forever tgz root library forever monitor tgz chokidar tgz braces tgz snapdragon tgz base tgz cache base tgz has value tgz has values tgz x kind of tgz vulnerable library kind of tgz get the native type of a value library home page a href path to dependency file tmp ws scm nodegoat package json path to vulnerable library tmp ws scm nodegoat node modules nodemon node modules kind of package json dependency hierarchy grunt cli tgz root library liftoff tgz findup sync tgz micromatch tgz x kind of tgz vulnerable library kind of tgz get the native type of a value library home page a href path to dependency file tmp ws scm nodegoat package json path to vulnerable library tmp ws scm nodegoat node modules nyc node modules kind of package json dependency hierarchy grunt if tgz root library grunt contrib nodeunit tgz nodeunit tgz tap tgz nyc tgz micromatch tgz x kind of tgz vulnerable library kind of tgz get the native type of a value library home page a href path to dependency file tmp ws scm nodegoat package json path to vulnerable library tmp ws scm nodegoat node modules nodemon node modules expand brackets node modules kind of package json dependency hierarchy grunt cli tgz root library liftoff tgz findup sync tgz micromatch tgz extglob tgz expand brackets tgz define property tgz is descriptor tgz x kind of tgz vulnerable library found in head commit a href vulnerability details ctorname in index js in kind of allows external user input to overwrite certain internal attributes via a conflicting name as demonstrated by constructor name symbol hence a crafted payload can overwrite this builtin attribute to manipulate the type detection result publish date url a href cvss score details base score metrics not available step up your open source security game with whitesource
| 0
|
329,807
| 10,024,689,342
|
IssuesEvent
|
2019-07-16 22:48:05
|
crafted/crafted
|
https://api.github.com/repos/crafted/crafted
|
closed
|
Deep-link across issues
|
feature pkg: github-dashboard priority: low
|
GitHub will deep-link issues when written like `#10`, e.g. #10
Should be able to do the same in the app and clicking should bring up the item detail (probably as a popup)
|
1.0
|
Deep-link across issues - GitHub will deep-link issues when written like `#10`, e.g. #10
Should be able to do the same in the app and clicking should bring up the item detail (probably as a popup)
|
non_process
|
deep link across issues github will deep link issues when written like e g should be able to do the same in the app and clicking should bring up the item detail probably as a popup
| 0
|
207,284
| 7,126,935,176
|
IssuesEvent
|
2018-01-20 16:12:04
|
gw2efficiency/issues
|
https://api.github.com/repos/gw2efficiency/issues
|
closed
|
Show rarity for account unlocks (achievements, outfits, skins, titles, etc.)
|
Feature Priority A Ready for Release
|
Someone on [reddit](https://www.reddit.com/r/gw2efficiency/comments/4t1ffm/suggestion_achievements_ideas/) suggested something that would be awesome:
- Similar to xbox true achievements, generate a 'trueachievements' score based on what the population has achieved. (e.g. `((Total Players)/(Players with Achievement))^0.5`)
- Instead of 'find me a random achievement' or the in-game 'almost completed' achievements, let people search (by section, if they avoid pvp for instance) on what is the 'easiest' achievement they could do.
|
1.0
|
Show rarity for account unlocks (achievements, outfits, skins, titles, etc.) - Someone on [reddit](https://www.reddit.com/r/gw2efficiency/comments/4t1ffm/suggestion_achievements_ideas/) suggested something that would be awesome:
- Similar to xbox true achievements, generate a 'trueachievements' score based on what the population has achieved. (e.g. `((Total Players)/(Players with Achievement))^0.5`)
- Instead of 'find me a random achievement' or the in-game 'almost completed' achievements, let people search (by section, if they avoid pvp for instance) on what is the 'easiest' achievement they could do.
|
non_process
|
show rarity for account unlocks achievements outfits skins titles etc someone on suggested something that would be awesome similar to xbox true achievements generate a trueachievements score based on what the population has achieved e g total players players with achievement instead of find me a random achievement or the in game almost completed achievements let people search by section if they avoid pvp for instance on what is the easiest achievement they could do
| 0
|
6,918
| 10,076,688,691
|
IssuesEvent
|
2019-07-24 16:50:38
|
googleapis/google-cloud-python
|
https://api.github.com/repos/googleapis/google-cloud-python
|
opened
|
Asset: 'test_export_assets' flakes
|
api: cloudasset flaky testing type: process
|
/cc @gaogaogiraffe (test added in PR #8613, configuration updated in #8627)
From [this Kokoro failure today](https://source.cloud.google.com/results/invocations/0ddf2264-a3dd-4e44-956b-594c87bb1add/targets/cloud-devrel%2Fclient-libraries%2Fgoogle-cloud-python%2Fpresubmit%2Fasset/log):
```python
___________________ TestVPCServiceControl.test_export_assets ___________________
self = <test_vpcsc.TestVPCServiceControl object at 0x7fe8f53fa9d0>
@pytest.mark.skipif(
PROJECT_INSIDE is None, reason="Missing environment variable: PROJECT_ID"
)
@pytest.mark.skipif(
PROJECT_OUTSIDE is None,
reason="Missing environment variable: GOOGLE_CLOUD_TESTS_VPCSC_OUTSIDE_PERIMETER_PROJECT",
)
def test_export_assets(self):
client = asset_v1.AssetServiceClient()
output_config = {}
parent_inside = "projects/" + PROJECT_INSIDE
delayed_inside = lambda: client.export_assets(parent_inside, output_config)
parent_outside = "projects/" + PROJECT_OUTSIDE
delayed_outside = lambda: client.export_assets(parent_outside, output_config)
> TestVPCServiceControl._do_test(delayed_inside, delayed_outside)
tests/system/test_vpcsc.py:67:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
delayed_inside = <function <lambda> at 0x7fe8f5348b90>
delayed_outside = <function <lambda> at 0x7fe8f5348c08>
@staticmethod
def _do_test(delayed_inside, delayed_outside):
if IS_INSIDE_VPCSC.lower() == "true":
> assert TestVPCServiceControl._is_rejected(delayed_outside)
E assert False
E + where False = <function _is_rejected at 0x7fe8f3031de8>(<function <lambda> at 0x7fe8f5348c08>)
E + where <function _is_rejected at 0x7fe8f3031de8> = TestVPCServiceControl._is_rejected
tests/system/test_vpcsc.py:47: AssertionError
```
|
1.0
|
Asset: 'test_export_assets' flakes - /cc @gaogaogiraffe (test added in PR #8613, configuration updated in #8627)
From [this Kokoro failure today](https://source.cloud.google.com/results/invocations/0ddf2264-a3dd-4e44-956b-594c87bb1add/targets/cloud-devrel%2Fclient-libraries%2Fgoogle-cloud-python%2Fpresubmit%2Fasset/log):
```python
___________________ TestVPCServiceControl.test_export_assets ___________________
self = <test_vpcsc.TestVPCServiceControl object at 0x7fe8f53fa9d0>
@pytest.mark.skipif(
PROJECT_INSIDE is None, reason="Missing environment variable: PROJECT_ID"
)
@pytest.mark.skipif(
PROJECT_OUTSIDE is None,
reason="Missing environment variable: GOOGLE_CLOUD_TESTS_VPCSC_OUTSIDE_PERIMETER_PROJECT",
)
def test_export_assets(self):
client = asset_v1.AssetServiceClient()
output_config = {}
parent_inside = "projects/" + PROJECT_INSIDE
delayed_inside = lambda: client.export_assets(parent_inside, output_config)
parent_outside = "projects/" + PROJECT_OUTSIDE
delayed_outside = lambda: client.export_assets(parent_outside, output_config)
> TestVPCServiceControl._do_test(delayed_inside, delayed_outside)
tests/system/test_vpcsc.py:67:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
delayed_inside = <function <lambda> at 0x7fe8f5348b90>
delayed_outside = <function <lambda> at 0x7fe8f5348c08>
@staticmethod
def _do_test(delayed_inside, delayed_outside):
if IS_INSIDE_VPCSC.lower() == "true":
> assert TestVPCServiceControl._is_rejected(delayed_outside)
E assert False
E + where False = <function _is_rejected at 0x7fe8f3031de8>(<function <lambda> at 0x7fe8f5348c08>)
E + where <function _is_rejected at 0x7fe8f3031de8> = TestVPCServiceControl._is_rejected
tests/system/test_vpcsc.py:47: AssertionError
```
|
process
|
asset test export assets flakes cc gaogaogiraffe test added in pr configuration updated in from python testvpcservicecontrol test export assets self pytest mark skipif project inside is none reason missing environment variable project id pytest mark skipif project outside is none reason missing environment variable google cloud tests vpcsc outside perimeter project def test export assets self client asset assetserviceclient output config parent inside projects project inside delayed inside lambda client export assets parent inside output config parent outside projects project outside delayed outside lambda client export assets parent outside output config testvpcservicecontrol do test delayed inside delayed outside tests system test vpcsc py delayed inside at delayed outside at staticmethod def do test delayed inside delayed outside if is inside vpcsc lower true assert testvpcservicecontrol is rejected delayed outside e assert false e where false at e where testvpcservicecontrol is rejected tests system test vpcsc py assertionerror
| 1
|
22,631
| 19,804,580,923
|
IssuesEvent
|
2022-01-19 04:16:30
|
Curtis-VL/OVRToolkit-Issues
|
https://api.github.com/repos/Curtis-VL/OVRToolkit-Issues
|
opened
|
Add a prompt message when a user tries to edit look hiding angle but the overlay isn't attached to a device
|
usability
|
Add a prompt message when a user tries to edit look hiding angle but the overlay isn't attached to a device.
|
True
|
Add a prompt message when a user tries to edit look hiding angle but the overlay isn't attached to a device - Add a prompt message when a user tries to edit look hiding angle but the overlay isn't attached to a device.
|
non_process
|
add a prompt message when a user tries to edit look hiding angle but the overlay isn t attached to a device add a prompt message when a user tries to edit look hiding angle but the overlay isn t attached to a device
| 0
|
8,566
| 11,737,836,618
|
IssuesEvent
|
2020-03-11 15:12:15
|
cypress-io/cypress
|
https://api.github.com/repos/cypress-io/cypress
|
closed
|
Replace deprecated request library dependency
|
process: dependencies stage: needs review type: chore
|
### Current behavior:
Request library is deprecated. Getting this message on installing packages in logs.
### Desired behavior:
Replace request with maintained alternative like node-fetch
### Test code to reproduce
just run `yarn add request`
|
1.0
|
Replace deprecated request library dependency - ### Current behavior:
Request library is deprecated. Getting this message on installing packages in logs.
### Desired behavior:
Replace request with maintained alternative like node-fetch
### Test code to reproduce
just run `yarn add request`
|
process
|
replace deprecated request library dependency current behavior request library is deprecated getting this message on installing packages in logs desired behavior replace request with maintained alternative like node fetch test code to reproduce just run yarn add request
| 1
|
21,498
| 3,900,354,521
|
IssuesEvent
|
2016-04-18 05:19:22
|
NishantUpadhyay-BTC/BLISS-Issue-Tracking
|
https://api.github.com/repos/NishantUpadhyay-BTC/BLISS-Issue-Tracking
|
reopened
|
Guest UI: general design note
|
Change Request Deployed to Test Done
|
Adjust bottom of page so we don't ever see the bottoms of the rocks - perhaps cut off the bottom 1/4 or so
|
1.0
|
Guest UI: general design note - Adjust bottom of page so we don't ever see the bottoms of the rocks - perhaps cut off the bottom 1/4 or so
|
non_process
|
guest ui general design note adjust bottom of page so we don t ever see the bottoms of the rocks perhaps cut off the bottom or so
| 0
|
16,808
| 22,058,285,482
|
IssuesEvent
|
2022-05-30 14:48:07
|
KratosMultiphysics/Kratos
|
https://api.github.com/repos/KratosMultiphysics/Kratos
|
closed
|
[Core] PointOutputProcess is not an output process (no IsOutputStep nor PrintOutput)
|
Post Process
|
**Description**
An update of the visualization_variables of elements, which are cut, of the visualization_model_part does not seem to happen every time step. E.g. if a PointOutputProcess (or one of the derived classes) creates output every time step for a cut element, the values in the output file of the PointOutputProcess won't change for a certain number of time steps (often until a GiD or VTK Output of the visualization model part happens). The output of works for the standard FluidModelPart.fluid_computational_model_part.
**Scope**
- EmbeddedSkinVisualizationProcess
**To Reproduce**
- Use `embedded_symbolic_navier_stokes_discontinuous` as element_type
- Add `ApplyEmbeddedSkinVisualizationProcess` in your ProjectParameters to have a visualization_model_part,( e.g. "visualization_variables": ["VELOCITY","PRESSURE"])
- Add a `PointOutputProcess` using the visualization_model_part for a point in an element, which is cut (e.g. "output_variables": [ "PRESSURE"])
- Add a `GiDOutputProcess`, which output_interval is bigger than 1 (e.g. "nodal_results" : ["VELOCITY","PRESSURE"])
- Run a couple of time steps (more that output_interval of your GiDOutputProcess)
example see [visOutput.zip](https://github.com/KratosMultiphysics/Kratos/files/5599021/visOutput.zip) --> first output point of the LineOutputProcess is a cut element, the remaining points not
**Expected behavior**
The files created by a PointOutputProcess writes updated results for every time step, including elements, which are cut.
**Environment**
- OS: Ubuntu 20.04.1
- Branch: master
- Python 3.7.4
|
1.0
|
[Core] PointOutputProcess is not an output process (no IsOutputStep nor PrintOutput) - **Description**
An update of the visualization_variables of elements, which are cut, of the visualization_model_part does not seem to happen every time step. E.g. if a PointOutputProcess (or one of the derived classes) creates output every time step for a cut element, the values in the output file of the PointOutputProcess won't change for a certain number of time steps (often until a GiD or VTK Output of the visualization model part happens). The output of works for the standard FluidModelPart.fluid_computational_model_part.
**Scope**
- EmbeddedSkinVisualizationProcess
**To Reproduce**
- Use `embedded_symbolic_navier_stokes_discontinuous` as element_type
- Add `ApplyEmbeddedSkinVisualizationProcess` in your ProjectParameters to have a visualization_model_part,( e.g. "visualization_variables": ["VELOCITY","PRESSURE"])
- Add a `PointOutputProcess` using the visualization_model_part for a point in an element, which is cut (e.g. "output_variables": [ "PRESSURE"])
- Add a `GiDOutputProcess`, which output_interval is bigger than 1 (e.g. "nodal_results" : ["VELOCITY","PRESSURE"])
- Run a couple of time steps (more that output_interval of your GiDOutputProcess)
example see [visOutput.zip](https://github.com/KratosMultiphysics/Kratos/files/5599021/visOutput.zip) --> first output point of the LineOutputProcess is a cut element, the remaining points not
**Expected behavior**
The files created by a PointOutputProcess writes updated results for every time step, including elements, which are cut.
**Environment**
- OS: Ubuntu 20.04.1
- Branch: master
- Python 3.7.4
|
process
|
pointoutputprocess is not an output process no isoutputstep nor printoutput description an update of the visualization variables of elements which are cut of the visualization model part does not seem to happen every time step e g if a pointoutputprocess or one of the derived classes creates output every time step for a cut element the values in the output file of the pointoutputprocess won t change for a certain number of time steps often until a gid or vtk output of the visualization model part happens the output of works for the standard fluidmodelpart fluid computational model part scope embeddedskinvisualizationprocess to reproduce use embedded symbolic navier stokes discontinuous as element type add applyembeddedskinvisualizationprocess in your projectparameters to have a visualization model part e g visualization variables add a pointoutputprocess using the visualization model part for a point in an element which is cut e g output variables add a gidoutputprocess which output interval is bigger than e g nodal results run a couple of time steps more that output interval of your gidoutputprocess example see first output point of the lineoutputprocess is a cut element the remaining points not expected behavior the files created by a pointoutputprocess writes updated results for every time step including elements which are cut environment os ubuntu branch master python
| 1
|
11,218
| 13,998,914,218
|
IssuesEvent
|
2020-10-28 10:06:06
|
bisq-network/proposals
|
https://api.github.com/repos/bisq-network/proposals
|
closed
|
BSQ trading fee update for Cycle 15
|
re:compensation re:processes was:approved
|
This proposal keeps a record of the [process](https://bisq.wiki/Updating_BSQ_trading_fees) to keep the BSQ trading fee at 50% discount to BTC trading fee. It will remain open until we need to update BSQ trading fees again.
Link to last issue: #202
## Cycle 15
**Parameters**
* USD/BTC price: 9380USD
* USD/BSQ price: 0.61USD
* Current BSQ discount: 57.2%
There's a need to **update BSQ trading fee for Cycle 15.** The 15% cap for BSQ trading fee increase has been used.
<!--
If it's under 45%, use: "There's a need to **update BSQ trading fee for Cycle .**"
If it's over 55% you might need to add "The 15% cap for BSQ trading fee increase has be reached."
-->
### New BSQ trading fees
A change parameter request for BSQ trading fees will be submitted to DAO voting:
New BSQ maker fee: `7.6 BSQ`
New BSQ taker fee: `53.23BSQ`
|
1.0
|
BSQ trading fee update for Cycle 15 - This proposal keeps a record of the [process](https://bisq.wiki/Updating_BSQ_trading_fees) to keep the BSQ trading fee at 50% discount to BTC trading fee. It will remain open until we need to update BSQ trading fees again.
Link to last issue: #202
## Cycle 15
**Parameters**
* USD/BTC price: 9380USD
* USD/BSQ price: 0.61USD
* Current BSQ discount: 57.2%
There's a need to **update BSQ trading fee for Cycle 15.** The 15% cap for BSQ trading fee increase has been used.
<!--
If it's under 45%, use: "There's a need to **update BSQ trading fee for Cycle .**"
If it's over 55% you might need to add "The 15% cap for BSQ trading fee increase has be reached."
-->
### New BSQ trading fees
A change parameter request for BSQ trading fees will be submitted to DAO voting:
New BSQ maker fee: `7.6 BSQ`
New BSQ taker fee: `53.23BSQ`
|
process
|
bsq trading fee update for cycle this proposal keeps a record of the to keep the bsq trading fee at discount to btc trading fee it will remain open until we need to update bsq trading fees again link to last issue cycle parameters usd btc price usd bsq price current bsq discount there s a need to update bsq trading fee for cycle the cap for bsq trading fee increase has been used if it s under use there s a need to update bsq trading fee for cycle if it s over you might need to add the cap for bsq trading fee increase has be reached new bsq trading fees a change parameter request for bsq trading fees will be submitted to dao voting new bsq maker fee bsq new bsq taker fee
| 1
|
4,212
| 3,773,271,085
|
IssuesEvent
|
2016-03-17 01:03:24
|
lionheart/openradar-mirror
|
https://api.github.com/repos/lionheart/openradar-mirror
|
opened
|
25207304: Unexpected popup when opening gmail from Safari
|
classification:ui/usability reproducible:sometimes status:open
|
#### Description
Summary:
I get a weird popup when opening gmail from Safari that's very user-unfriendly.
Steps to Reproduce:
1. Open Safari
2. Open mail.google.com
3. Get a weird popup:
http://f.cl.ly/items/1W020S0p2B2j2J011v42/IMG_0293.PNG
Expected Results:
4. Popup language responds the following questions:
How's showing me this? Is it Google or Apple?
What's a database?
Why didn't I see this on other sites?
What happens if I don't?
What happens if I do and want to revert it?
Can I get more help?
Actual Results:
4. Pop up uses technical and incomplete language.
Version:
iOS 9.2.1
Notes:
I can't make a full picture of what this means with a background of 15 years of coding, of which 7 were on iOS. I can't imagine a regular user understanding the reach of these options.
Configuration:
iPad mini 3.
Attachments:
-
Product Version: 9.2.1
Created: 2016-03-17T00:46:42.054800
Originated: 2016-03-16T00:00:00
Open Radar Link: http://www.openradar.me/25207304
|
True
|
25207304: Unexpected popup when opening gmail from Safari - #### Description
Summary:
I get a weird popup when opening gmail from Safari that's very user-unfriendly.
Steps to Reproduce:
1. Open Safari
2. Open mail.google.com
3. Get a weird popup:
http://f.cl.ly/items/1W020S0p2B2j2J011v42/IMG_0293.PNG
Expected Results:
4. Popup language responds the following questions:
How's showing me this? Is it Google or Apple?
What's a database?
Why didn't I see this on other sites?
What happens if I don't?
What happens if I do and want to revert it?
Can I get more help?
Actual Results:
4. Pop up uses technical and incomplete language.
Version:
iOS 9.2.1
Notes:
I can't make a full picture of what this means with a background of 15 years of coding, of which 7 were on iOS. I can't imagine a regular user understanding the reach of these options.
Configuration:
iPad mini 3.
Attachments:
-
Product Version: 9.2.1
Created: 2016-03-17T00:46:42.054800
Originated: 2016-03-16T00:00:00
Open Radar Link: http://www.openradar.me/25207304
|
non_process
|
unexpected popup when opening gmail from safari description summary i get a weird popup when opening gmail from safari that s very user unfriendly steps to reproduce open safari open mail google com get a weird popup expected results popup language responds the following questions how s showing me this is it google or apple what s a database why didn t i see this on other sites what happens if i don t what happens if i do and want to revert it can i get more help actual results pop up uses technical and incomplete language version ios notes i can t make a full picture of what this means with a background of years of coding of which were on ios i can t imagine a regular user understanding the reach of these options configuration ipad mini attachments product version created originated open radar link
| 0
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.