'
return tensor;
^~~~~~
Target //mediapipe/examples/desktop/hand_tracking:hand_tracking_cpu failed to build
[Environment]
Machine: Ubuntu 18.04 (running on Amazon Lightsail), 4GB ram 2 vCPUs, 80 GB SSD
gcc Version: 7.5.0
Bazel Version: 3.7.2
OpenCV Version: 3.2.0
python Version: 2.7.17
python3 Version: 3.6.9
Note: Hello World builds and runs correctly.
",0,mediapipe build error building c command line example mediapipe hands error building mediapipe hands example c bazel build c opt define mediapipe disable gpu mediapipe examples desktop hand tracking hand tracking cpu actions running error home ubuntu mediapipe mediapipe calculators tensor build c compilation of rule mediapipe calculators tensor image to tensor converter o pencv failed exit gcc failed error executing command usr bin gcc u fortify source fstack protector wall wunused but set parameter wno free nonh eap object fno omit frame pointer d fortify source dndebug ffunction sections remaining argument s skipped use sandbox debug to see verbose messages from the sandbox gcc failed error executing command usr bin gcc u fortify source fstack protector wall wun used but set parameter wno free nonheap object fno omit frame pointer d fortify source dndebug ffunction sections remaining argumen t s skipped use sandbox debug to see verbose messages from the sandbox mediapipe calculators tensor image to tensor converter opencv cc in member function virtual absl lts statusor mediapipe an onymous opencvprocessor convert const mediapipe image const mediapipe rotatedrect const mediapipe size float float mediapipe calculators tensor image to tensor converter opencv cc error could not convert tensor from mediapipe tensor to absl lts statusor return tensor target mediapipe examples desktop hand tracking hand tracking cpu failed to build machine ubuntu running on amazon lightsail ram vcpus gb ssd gcc version bazel version opencv version python version version note hello world builds and runs correctly ,0
270999,23576654294.0,IssuesEvent,2022-08-23 01:58:16,lowRISC/opentitan,https://api.github.com/repos/lowRISC/opentitan,opened,[rom-e2e] rom_e2e_bootstrap_enabled_not_requested,Priority:P2 Type:Task SW:ROM Milestone:V2 Component:RomE2eTest,"### Test point name
[rom_e2e_bootstrap_enabled_not_requested](https://cs.opensource.google/opentitan/opentitan/+/master:sw/device/silicon_creator/rom/data/rom_testplan.hjson?q=rom_e2e_bootstrap_enabled_not_requested)
### Host side component
Unknown
### OpenTitanTool infrastructure implemented
Unknown
### Contact person
@alphan
### Checklist
Please fill out this checklist as items are completed. Link to PRs and issues as appropriate.
- [ ] Check if existing test covers most or all of this testpoint (if so, either extend said test to cover all points, or skip the next 3 checkboxes)
- [ ] Device-side (C) component developed
- [ ] Bazel build rules developed
- [ ] Host-side component developed
- [ ] HJSON test plan updated with test name (so it shows up in the dashboard)
- [ ] Test added to dvsim nightly regression (and passing at time of checking)
### Verify that ROM does not enter bootstrap when enabled in OTP but not requested.
`OWNER_SW_CFG_ROM_BOOTSTRAP_EN` OTP item must be `kHardenedBoolTrue` (`0x739`).
- Do not apply bootstrap pin strapping.
- Reset the chip.
- Verify that the chip outputs the expected `BFV`: `0142500d` over UART.
- ROM will continously reset the chip and output the same `BFV`.
- Verify that the chip does not respond to `READ_STATUS` (`0x05`).
- The data on the CIPO line must be `0xff`.
",1.0,"[rom-e2e] rom_e2e_bootstrap_enabled_not_requested - ### Test point name
[rom_e2e_bootstrap_enabled_not_requested](https://cs.opensource.google/opentitan/opentitan/+/master:sw/device/silicon_creator/rom/data/rom_testplan.hjson?q=rom_e2e_bootstrap_enabled_not_requested)
### Host side component
Unknown
### OpenTitanTool infrastructure implemented
Unknown
### Contact person
@alphan
### Checklist
Please fill out this checklist as items are completed. Link to PRs and issues as appropriate.
- [ ] Check if existing test covers most or all of this testpoint (if so, either extend said test to cover all points, or skip the next 3 checkboxes)
- [ ] Device-side (C) component developed
- [ ] Bazel build rules developed
- [ ] Host-side component developed
- [ ] HJSON test plan updated with test name (so it shows up in the dashboard)
- [ ] Test added to dvsim nightly regression (and passing at time of checking)
### Verify that ROM does not enter bootstrap when enabled in OTP but not requested.
`OWNER_SW_CFG_ROM_BOOTSTRAP_EN` OTP item must be `kHardenedBoolTrue` (`0x739`).
- Do not apply bootstrap pin strapping.
- Reset the chip.
- Verify that the chip outputs the expected `BFV`: `0142500d` over UART.
- ROM will continously reset the chip and output the same `BFV`.
- Verify that the chip does not respond to `READ_STATUS` (`0x05`).
- The data on the CIPO line must be `0xff`.
",0, rom bootstrap enabled not requested test point name host side component unknown opentitantool infrastructure implemented unknown contact person alphan checklist please fill out this checklist as items are completed link to prs and issues as appropriate check if existing test covers most or all of this testpoint if so either extend said test to cover all points or skip the next checkboxes device side c component developed bazel build rules developed host side component developed hjson test plan updated with test name so it shows up in the dashboard test added to dvsim nightly regression and passing at time of checking verify that rom does not enter bootstrap when enabled in otp but not requested owner sw cfg rom bootstrap en otp item must be khardenedbooltrue do not apply bootstrap pin strapping reset the chip verify that the chip outputs the expected bfv over uart rom will continously reset the chip and output the same bfv verify that the chip does not respond to read status the data on the cipo line must be ,0
204778,15531592090.0,IssuesEvent,2021-03-14 00:30:02,backend-br/vagas,https://api.github.com/repos/backend-br/vagas,closed,[Remoto/Campinas] Node.js developer @HDN.Digital,Alocado CI Express MongoDB NodeJS Pleno Remoto Stale Testes Unitários,"
## Nossa empresa
Somos uma consultoria de transformação digital que está no mercado há 12 anos, e estamos em franca expansão.
Temos um time especializado em entregar soluções de tecnologia que agregam valor, otimizam o tempo e trazem inovação ao seu modo de trabalho. Nossa missão é colaborar, disseminar o conhecimento e a cultura de empresas através de novas tecnologias e processos ágeis.
Há mais de 10 anos temos a experiência em desenvolvimento de softwares e soluções digitais.
Faz parte do DNA da HDN entender a dor dos nossos clientes, se colocar no lugar dele e oferecer as soluções que melhor se adequam às específicas necessidades.
Toda mudança e transformação digital requer um primeiro passo, e estamos preparados para caminhar lado a lado.
Prezamos pelo desenvolvimento do colaborador tanto a nível técnico quanto a nível pessoal, temos um ambiente leve e divertido, queremos que você tenha voz e seja ouvido, tenha participação nos processos da empresa e encontre um ambiente amigável para crescer profissionalmente e construir sua carreira conosco!
## Descrição da vaga
Você vai atuar junto ao nosso time de engenheiros back-end para arquitetar e implementar soluções para diversos clientes (nacionais e internacionais) em projetos ágeis e desruptivos, com impacto direto no negócio. Queremos um profissional comunicativo, que ame codar e tenha responsabilidade sobre suas entregas.
## Local
Remoto ou Escritório, Campinas - Nova Campinas
## Requisitos
**Obrigatórios:**
- Experiência com Node e Express
**Desejáveis:**
- Conhecimentos com MongoDB e Postgres,
- Experiência com Testes unitários com Jest
- Experiência com testes de integração
- Conhecimentos em CI/CD
- Conhecimentos em React e/ou Vue
- Experiência com microsserviços
**Diferenciais:**
- Inglês avançado
## Benefícios
- 30 dias de férias remuneradas
**Diferenciais:**
- Sala de jogos
- Acesso aos cursos internos disponibilizados pela empresa
## Contratação
Cooperativa, a combinar
## Como se candidatar
Por favor envie um email para marcelo.pinheiro@hdnit.com.br com seu CV anexado - enviar no assunto: Vaga NodeJS
## Tempo médio de feedbacks
Costumamos enviar feedbacks em até 2 dias após cada processo.
E-mail para contato em caso de não haver resposta: contato@hdnit.com.br
## Labels
#### Alocação
- Alocado
- Remoto
#### Regime
- Cooperativa
#### Nível
- Júnior
- Pleno
- Sênior
",1.0,"[Remoto/Campinas] Node.js developer @HDN.Digital -
## Nossa empresa
Somos uma consultoria de transformação digital que está no mercado há 12 anos, e estamos em franca expansão.
Temos um time especializado em entregar soluções de tecnologia que agregam valor, otimizam o tempo e trazem inovação ao seu modo de trabalho. Nossa missão é colaborar, disseminar o conhecimento e a cultura de empresas através de novas tecnologias e processos ágeis.
Há mais de 10 anos temos a experiência em desenvolvimento de softwares e soluções digitais.
Faz parte do DNA da HDN entender a dor dos nossos clientes, se colocar no lugar dele e oferecer as soluções que melhor se adequam às específicas necessidades.
Toda mudança e transformação digital requer um primeiro passo, e estamos preparados para caminhar lado a lado.
Prezamos pelo desenvolvimento do colaborador tanto a nível técnico quanto a nível pessoal, temos um ambiente leve e divertido, queremos que você tenha voz e seja ouvido, tenha participação nos processos da empresa e encontre um ambiente amigável para crescer profissionalmente e construir sua carreira conosco!
## Descrição da vaga
Você vai atuar junto ao nosso time de engenheiros back-end para arquitetar e implementar soluções para diversos clientes (nacionais e internacionais) em projetos ágeis e desruptivos, com impacto direto no negócio. Queremos um profissional comunicativo, que ame codar e tenha responsabilidade sobre suas entregas.
## Local
Remoto ou Escritório, Campinas - Nova Campinas
## Requisitos
**Obrigatórios:**
- Experiência com Node e Express
**Desejáveis:**
- Conhecimentos com MongoDB e Postgres,
- Experiência com Testes unitários com Jest
- Experiência com testes de integração
- Conhecimentos em CI/CD
- Conhecimentos em React e/ou Vue
- Experiência com microsserviços
**Diferenciais:**
- Inglês avançado
## Benefícios
- 30 dias de férias remuneradas
**Diferenciais:**
- Sala de jogos
- Acesso aos cursos internos disponibilizados pela empresa
## Contratação
Cooperativa, a combinar
## Como se candidatar
Por favor envie um email para marcelo.pinheiro@hdnit.com.br com seu CV anexado - enviar no assunto: Vaga NodeJS
## Tempo médio de feedbacks
Costumamos enviar feedbacks em até 2 dias após cada processo.
E-mail para contato em caso de não haver resposta: contato@hdnit.com.br
## Labels
#### Alocação
- Alocado
- Remoto
#### Regime
- Cooperativa
#### Nível
- Júnior
- Pleno
- Sênior
",0, node js developer hdn digital nossa empresa somos uma consultoria de transformação digital que está no mercado há anos e estamos em franca expansão temos um time especializado em entregar soluções de tecnologia que agregam valor otimizam o tempo e trazem inovação ao seu modo de trabalho nossa missão é colaborar disseminar o conhecimento e a cultura de empresas através de novas tecnologias e processos ágeis há mais de anos temos a experiência em desenvolvimento de softwares e soluções digitais faz parte do dna da hdn entender a dor dos nossos clientes se colocar no lugar dele e oferecer as soluções que melhor se adequam às específicas necessidades toda mudança e transformação digital requer um primeiro passo e estamos preparados para caminhar lado a lado prezamos pelo desenvolvimento do colaborador tanto a nível técnico quanto a nível pessoal temos um ambiente leve e divertido queremos que você tenha voz e seja ouvido tenha participação nos processos da empresa e encontre um ambiente amigável para crescer profissionalmente e construir sua carreira conosco descrição da vaga você vai atuar junto ao nosso time de engenheiros back end para arquitetar e implementar soluções para diversos clientes nacionais e internacionais em projetos ágeis e desruptivos com impacto direto no negócio queremos um profissional comunicativo que ame codar e tenha responsabilidade sobre suas entregas local remoto ou escritório campinas nova campinas requisitos obrigatórios experiência com node e express desejáveis conhecimentos com mongodb e postgres experiência com testes unitários com jest experiência com testes de integração conhecimentos em ci cd conhecimentos em react e ou vue experiência com microsserviços diferenciais inglês avançado benefícios dias de férias remuneradas diferenciais sala de jogos acesso aos cursos internos disponibilizados pela empresa contratação cooperativa a combinar como se candidatar por favor envie um email para marcelo pinheiro hdnit com br com seu cv anexado enviar no assunto vaga nodejs tempo médio de feedbacks costumamos enviar feedbacks em até dias após cada processo e mail para contato em caso de não haver resposta contato hdnit com br labels alocação alocado remoto regime cooperativa nível júnior pleno sênior ,0
1386,19985127338.0,IssuesEvent,2022-01-30 14:45:53,lkrg-org/lkrg,https://api.github.com/repos/lkrg-org/lkrg,closed,Build fails on OpenSUSE leap's Linux 5.3.18-59.37,portability,"```
/__w/lkrg/lkrg/src/modules/database/JUMP_LABEL/p_arch_jump_label_transform_apply/p_arch_jump_label_transform_apply.c: In function 'p_arch_jump_label_transform_apply_entry':
/__w/lkrg/lkrg/src/modules/database/JUMP_LABEL/p_arch_jump_label_transform_apply/p_arch_jump_label_transform_apply.c:94:19: error: 'p_text_poke_loc {aka struct text_poke_loc}' has no member named 'detour'
&& p_tmp->detour) {
^~
make[3]: *** [/usr/src/linux-5.3.18-59.37/scripts/Makefile.build:288: /__w/lkrg/lkrg/src/modules/database/JUMP_LABEL
```",True,"Build fails on OpenSUSE leap's Linux 5.3.18-59.37 - ```
/__w/lkrg/lkrg/src/modules/database/JUMP_LABEL/p_arch_jump_label_transform_apply/p_arch_jump_label_transform_apply.c: In function 'p_arch_jump_label_transform_apply_entry':
/__w/lkrg/lkrg/src/modules/database/JUMP_LABEL/p_arch_jump_label_transform_apply/p_arch_jump_label_transform_apply.c:94:19: error: 'p_text_poke_loc {aka struct text_poke_loc}' has no member named 'detour'
&& p_tmp->detour) {
^~
make[3]: *** [/usr/src/linux-5.3.18-59.37/scripts/Makefile.build:288: /__w/lkrg/lkrg/src/modules/database/JUMP_LABEL
```",1,build fails on opensuse leap s linux w lkrg lkrg src modules database jump label p arch jump label transform apply p arch jump label transform apply c in function p arch jump label transform apply entry w lkrg lkrg src modules database jump label p arch jump label transform apply p arch jump label transform apply c error p text poke loc aka struct text poke loc has no member named detour p tmp detour make usr src linux scripts makefile build w lkrg lkrg src modules database jump label ,1
1434,21655175962.0,IssuesEvent,2022-05-06 13:28:25,damccorm/test-migration-target,https://api.github.com/repos/damccorm/test-migration-target,opened,Use portable WindowIntoPayload in DataflowRunner,P3 runner-dataflow portability task,"The Java-specific blobs transmitted to Dataflow need more context, in the form of portability framework protos.
Imported from Jira [BEAM-3514](https://issues.apache.org/jira/browse/BEAM-3514). Original Jira may contain additional context.
Reported by: kenn.
This issue has child subcomponents which were not migrated over. See the original Jira for more information.",True,"Use portable WindowIntoPayload in DataflowRunner - The Java-specific blobs transmitted to Dataflow need more context, in the form of portability framework protos.
Imported from Jira [BEAM-3514](https://issues.apache.org/jira/browse/BEAM-3514). Original Jira may contain additional context.
Reported by: kenn.
This issue has child subcomponents which were not migrated over. See the original Jira for more information.",1,use portable windowintopayload in dataflowrunner the java specific blobs transmitted to dataflow need more context in the form of portability framework protos imported from jira original jira may contain additional context reported by kenn this issue has child subcomponents which were not migrated over see the original jira for more information ,1
13,2577767565.0,IssuesEvent,2015-02-12 19:00:53,magnumripper/JohnTheRipper,https://api.github.com/repos/magnumripper/JohnTheRipper,closed,Can't build on Well,portability,"Some change to formats.c between b647486..5d1a14b has introduced this:
```
gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)
gcc -DAC_BUILT -march=native -mavx -c -g -O2 -I/usr/local/include -I/opt/AMDAPP/include -I/usr/local/cuda/include -DARCH_LITTLE_ENDIAN=1 -Wall -Wdeclaration-after-statement -fomit-frame-pointer -Wno-deprecated-declarations -Wno-format-extra-args -D_GNU_SOURCE -DHAVE_CUDA -fopenmp -pthread -DHAVE_OPENCL -pthread -funroll-loops formats.c -o formats.o
/tmp/ccXscU4h.s: Assembler messages:
/tmp/ccXscU4h.s:407: Error: no such instruction: `vfmadd312sd .LC5(%rip),%xmm0,%xmm2'
make[1]: *** [formats.o] Error 1
make[1]: Leaving directory `/space/home/magnum/src/john/src'
make: *** [default] Error 2
```",True,"Can't build on Well - Some change to formats.c between b647486..5d1a14b has introduced this:
```
gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)
gcc -DAC_BUILT -march=native -mavx -c -g -O2 -I/usr/local/include -I/opt/AMDAPP/include -I/usr/local/cuda/include -DARCH_LITTLE_ENDIAN=1 -Wall -Wdeclaration-after-statement -fomit-frame-pointer -Wno-deprecated-declarations -Wno-format-extra-args -D_GNU_SOURCE -DHAVE_CUDA -fopenmp -pthread -DHAVE_OPENCL -pthread -funroll-loops formats.c -o formats.o
/tmp/ccXscU4h.s: Assembler messages:
/tmp/ccXscU4h.s:407: Error: no such instruction: `vfmadd312sd .LC5(%rip),%xmm0,%xmm2'
make[1]: *** [formats.o] Error 1
make[1]: Leaving directory `/space/home/magnum/src/john/src'
make: *** [default] Error 2
```",1,can t build on well some change to formats c between has introduced this gcc version ubuntu linaro gcc dac built march native mavx c g i usr local include i opt amdapp include i usr local cuda include darch little endian wall wdeclaration after statement fomit frame pointer wno deprecated declarations wno format extra args d gnu source dhave cuda fopenmp pthread dhave opencl pthread funroll loops formats c o formats o tmp s assembler messages tmp s error no such instruction rip make error make leaving directory space home magnum src john src make error ,1
886,11771579257.0,IssuesEvent,2020-03-16 00:37:30,microsoft/vscode,https://api.github.com/repos/microsoft/vscode,closed,Portable Mode: Support auto update on Windows,feature-request portable-mode,"Issue Type: Bug
Having the portable/zip version of vscode doesn't autoupdate, I have to manually update it by copying the zip.
I'd prefer if auto update worked because I'd imagine you could intelligently remove old files and persist my data - right now I don't know if I should delete everything and paste the new stuff (and lose my settings) or if it's OK to layer.
VS Code version: Code 1.40.0 (86405ea23e3937316009fc27c9361deee66ffbf5, 2019-11-06T17:02:13.381Z)
OS version: Windows_NT x64 10.0.18362
",True,"Portable Mode: Support auto update on Windows - Issue Type: Bug
Having the portable/zip version of vscode doesn't autoupdate, I have to manually update it by copying the zip.
I'd prefer if auto update worked because I'd imagine you could intelligently remove old files and persist my data - right now I don't know if I should delete everything and paste the new stuff (and lose my settings) or if it's OK to layer.
VS Code version: Code 1.40.0 (86405ea23e3937316009fc27c9361deee66ffbf5, 2019-11-06T17:02:13.381Z)
OS version: Windows_NT x64 10.0.18362
",1,portable mode support auto update on windows issue type bug having the portable zip version of vscode doesn t autoupdate i have to manually update it by copying the zip i d prefer if auto update worked because i d imagine you could intelligently remove old files and persist my data right now i don t know if i should delete everything and paste the new stuff and lose my settings or if it s ok to layer vs code version code os version windows nt ,1
207895,16096927998.0,IssuesEvent,2021-04-27 02:09:10,padma-g/info478-project,https://api.github.com/repos/padma-g/info478-project,closed,Identify necessary technical skills and major challenges,documentation,"What new technical skills will we need to learn in order to complete the project?
What major challenges do we anticipate?",1.0,"Identify necessary technical skills and major challenges - What new technical skills will we need to learn in order to complete the project?
What major challenges do we anticipate?",0,identify necessary technical skills and major challenges what new technical skills will we need to learn in order to complete the project what major challenges do we anticipate ,0
1767,26029031687.0,IssuesEvent,2022-12-21 19:08:14,AzureAD/microsoft-authentication-library-for-dotnet,https://api.github.com/repos/AzureAD/microsoft-authentication-library-for-dotnet,closed,[Feature Request] Add support for LogCallback in ApplicationOptions ,Supportability,"
```csharp
var options = new ConfidentialClientApplicationOptions
{
ClientId = TestConstants.ClientId,
LogLevel = LogLevel.Verbose,
EnablePiiLogging = true,
IsDefaultPlatformLoggingEnabled = true,
LogCallback = (level, msg, pii) => { log(msg); } // Not Available!
};
var cca = ConfidentialClientApplicationBuilder.CreateWithApplicationOptions(options)
.Build();
```",True,"[Feature Request] Add support for LogCallback in ApplicationOptions -
```csharp
var options = new ConfidentialClientApplicationOptions
{
ClientId = TestConstants.ClientId,
LogLevel = LogLevel.Verbose,
EnablePiiLogging = true,
IsDefaultPlatformLoggingEnabled = true,
LogCallback = (level, msg, pii) => { log(msg); } // Not Available!
};
var cca = ConfidentialClientApplicationBuilder.CreateWithApplicationOptions(options)
.Build();
```",1, add support for logcallback in applicationoptions csharp var options new confidentialclientapplicationoptions clientid testconstants clientid loglevel loglevel verbose enablepiilogging true isdefaultplatformloggingenabled true logcallback level msg pii log msg not available var cca confidentialclientapplicationbuilder createwithapplicationoptions options build ,1
181973,21664471323.0,IssuesEvent,2022-05-07 01:27:40,scottstientjes/snipe-it,https://api.github.com/repos/scottstientjes/snipe-it,closed,WS-2018-0236 (Medium) detected in mem-1.1.0.tgz - autoclosed,security vulnerability,"## WS-2018-0236 - Medium Severity Vulnerability
Vulnerable Library - mem-1.1.0.tgz
Memoize functions - An optimization used to speed up consecutive function calls by caching the result of calls with identical input
Library home page: https://registry.npmjs.org/mem/-/mem-1.1.0.tgz
Path to dependency file: /tmp/ws-scm/snipe-it/package.json
Path to vulnerable library: /tmp/ws-scm/snipe-it/node_modules/mem/package.json
Dependency Hierarchy:
- laravel-mix-2.1.11.tgz (Root Library)
- yargs-8.0.2.tgz
- os-locale-2.1.0.tgz
- :x: **mem-1.1.0.tgz** (Vulnerable Library)
Found in HEAD commit: 35f2b36393de933b01f7dd715958a7a89a2d783b
Vulnerability Details
In nodejs-mem before version 4.0.0 there is a memory leak due to old results not being removed from the cache despite reaching maxAge. Exploitation of this can lead to exhaustion of memory and subsequent denial of service.
Publish Date: 2018-08-27
URL: WS-2018-0236
CVSS 2 Score Details (5.5)
Base Score Metrics not available
Suggested Fix
Type: Upgrade version
Origin: https://bugzilla.redhat.com/show_bug.cgi?id=1623744
Release Date: 2019-05-30
Fix Resolution: 4.0.0
Vulnerable Library - mem-1.1.0.tgz
Memoize functions - An optimization used to speed up consecutive function calls by caching the result of calls with identical input
Library home page: https://registry.npmjs.org/mem/-/mem-1.1.0.tgz
Path to dependency file: /tmp/ws-scm/snipe-it/package.json
Path to vulnerable library: /tmp/ws-scm/snipe-it/node_modules/mem/package.json
Dependency Hierarchy:
- laravel-mix-2.1.11.tgz (Root Library)
- yargs-8.0.2.tgz
- os-locale-2.1.0.tgz
- :x: **mem-1.1.0.tgz** (Vulnerable Library)
Found in HEAD commit: 35f2b36393de933b01f7dd715958a7a89a2d783b
Vulnerability Details
In nodejs-mem before version 4.0.0 there is a memory leak due to old results not being removed from the cache despite reaching maxAge. Exploitation of this can lead to exhaustion of memory and subsequent denial of service.
Publish Date: 2018-08-27
URL: WS-2018-0236
CVSS 2 Score Details (5.5)
Base Score Metrics not available
Suggested Fix
Type: Upgrade version
Origin: https://bugzilla.redhat.com/show_bug.cgi?id=1623744
Release Date: 2019-05-30
Fix Resolution: 4.0.0
Vulnerable Library - jquery-1.7.2.min.js
JavaScript library for DOM operations
Library home page: https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.2/jquery.min.js
Path to dependency file: /tmp/ws-scm/serverless-mfa-api/node_modules/jmespath/index.html
Path to vulnerable library: /serverless-mfa-api/node_modules/jmespath/index.html
Dependency Hierarchy:
- :x: **jquery-1.7.2.min.js** (Vulnerable Library)
Found in HEAD commit: bc7a5cb545c98937d5fc3a8b979879b0177a757a
Vulnerability Details
jQuery before 1.9.0 is vulnerable to Cross-site Scripting (XSS) attacks. The jQuery(strInput) function does not differentiate selectors from HTML in a reliable fashion. In vulnerable versions, jQuery determined whether the input was HTML by looking for the '<' character anywhere in the string, giving attackers more flexibility when attempting to construct a malicious payload. In fixed versions, jQuery only deems the input to be HTML if it explicitly starts with the '<' character, limiting exploitability only to attackers who can control the beginning of a string, which is far less common.
Publish Date: 2018-01-18
URL: CVE-2012-6708
CVSS 3 Score Details (6.1)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://nvd.nist.gov/vuln/detail/CVE-2012-6708
Release Date: 2018-01-18
Fix Resolution: jQuery - v1.9.0
Vulnerable Library - jquery-1.7.2.min.js
JavaScript library for DOM operations
Library home page: https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.2/jquery.min.js
Path to dependency file: /tmp/ws-scm/serverless-mfa-api/node_modules/jmespath/index.html
Path to vulnerable library: /serverless-mfa-api/node_modules/jmespath/index.html
Dependency Hierarchy:
- :x: **jquery-1.7.2.min.js** (Vulnerable Library)
Found in HEAD commit: bc7a5cb545c98937d5fc3a8b979879b0177a757a
Vulnerability Details
jQuery before 1.9.0 is vulnerable to Cross-site Scripting (XSS) attacks. The jQuery(strInput) function does not differentiate selectors from HTML in a reliable fashion. In vulnerable versions, jQuery determined whether the input was HTML by looking for the '<' character anywhere in the string, giving attackers more flexibility when attempting to construct a malicious payload. In fixed versions, jQuery only deems the input to be HTML if it explicitly starts with the '<' character, limiting exploitability only to attackers who can control the beginning of a string, which is far less common.
Publish Date: 2018-01-18
URL: CVE-2012-6708
CVSS 3 Score Details (6.1)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://nvd.nist.gov/vuln/detail/CVE-2012-6708
Release Date: 2018-01-18
Fix Resolution: jQuery - v1.9.0
Vulnerable Library - parse-url-5.0.1.tgz
An advanced url parser supporting git urls too.
Library home page: https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/parse-url
Dependency Hierarchy:
- lerna-3.13.4.tgz (Root Library)
- version-3.13.4.tgz
- github-client-3.13.3.tgz
- git-url-parse-11.1.2.tgz
- git-up-4.0.1.tgz
- :x: **parse-url-5.0.1.tgz** (Vulnerable Library)
Found in HEAD commit: b9888ec61e269386b4fab790d7d16670ad49b548
Found in base branch: fix-babel-core-js
Vulnerability Details
Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository ionicabizau/parse-url prior to 7.0.0.
Publish Date: 2022-06-27
URL: CVE-2022-0722
CVSS 3 Score Details (4.8)
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: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://huntr.dev/bounties/2490ef6d-5577-4714-a4dd-9608251b4226
Release Date: 2022-06-27
Fix Resolution: parse-url - 6.0.1
Vulnerable Library - parse-url-5.0.1.tgz
An advanced url parser supporting git urls too.
Library home page: https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/parse-url
Dependency Hierarchy:
- lerna-3.13.4.tgz (Root Library)
- version-3.13.4.tgz
- github-client-3.13.3.tgz
- git-url-parse-11.1.2.tgz
- git-up-4.0.1.tgz
- :x: **parse-url-5.0.1.tgz** (Vulnerable Library)
Found in HEAD commit: b9888ec61e269386b4fab790d7d16670ad49b548
Found in base branch: fix-babel-core-js
Vulnerability Details
Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository ionicabizau/parse-url prior to 7.0.0.
Publish Date: 2022-06-27
URL: CVE-2022-0722
CVSS 3 Score Details (4.8)
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: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://huntr.dev/bounties/2490ef6d-5577-4714-a4dd-9608251b4226
Release Date: 2022-06-27
Fix Resolution: parse-url - 6.0.1
Vulnerable Libraries - jquery-1.7.2.min.js, jquery-1.3.2.min.js, jquery-1.7.1.min.js
jquery-1.7.2.min.js
JavaScript library for DOM operations
Library home page: https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.2/jquery.min.js
Path to dependency file: freeCodeCamp/api-server/node_modules/jmespath/index.html
Path to vulnerable library: freeCodeCamp/api-server/node_modules/jmespath/index.html
Dependency Hierarchy:
- :x: **jquery-1.7.2.min.js** (Vulnerable Library)
jquery-1.3.2.min.js
JavaScript library for DOM operations
Library home page: https://cdnjs.cloudflare.com/ajax/libs/jquery/1.3.2/jquery.min.js
Path to dependency file: freeCodeCamp/tools/contributor/lib/node_modules/underscore.string/test/test_underscore/temp_tests.html
Path to vulnerable library: freeCodeCamp/tools/contributor/lib/node_modules/underscore.string/test/test_underscore/vendor/jquery.js
Dependency Hierarchy:
- :x: **jquery-1.3.2.min.js** (Vulnerable Library)
jquery-1.7.1.min.js
JavaScript library for DOM operations
Library home page: https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.1/jquery.min.js
Path to dependency file: freeCodeCamp/tools/contributor/dashboard-app/client/node_modules/sockjs/examples/multiplex/index.html
Path to vulnerable library: freeCodeCamp/tools/contributor/dashboard-app/client/node_modules/sockjs/examples/multiplex/index.html,freeCodeCamp/tools/contributor/dashboard-app/client/node_modules/sockjs/examples/echo/index.html,freeCodeCamp/tools/contributor/dashboard-app/client/node_modules/sockjs/examples/express-3.x/index.html,freeCodeCamp/tools/contributor/dashboard-app/client/node_modules/sockjs/examples/hapi/html/index.html
Dependency Hierarchy:
- :x: **jquery-1.7.1.min.js** (Vulnerable Library)
Found in HEAD commit: 311e89b65c48c9468ebef29fa6a623b9e24a3093
Found in base branch: master
Vulnerability Details
jQuery before 1.9.0 is vulnerable to Cross-site Scripting (XSS) attacks. The jQuery(strInput) function does not differentiate selectors from HTML in a reliable fashion. In vulnerable versions, jQuery determined whether the input was HTML by looking for the '<' character anywhere in the string, giving attackers more flexibility when attempting to construct a malicious payload. In fixed versions, jQuery only deems the input to be HTML if it explicitly starts with the '<' character, limiting exploitability only to attackers who can control the beginning of a string, which is far less common.
Publish Date: 2018-01-18
URL: CVE-2012-6708
CVSS 3 Score Details (6.1)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://nvd.nist.gov/vuln/detail/CVE-2012-6708
Release Date: 2018-01-18
Fix Resolution: jQuery - v1.9.0
Vulnerable Libraries - jquery-1.7.2.min.js, jquery-1.3.2.min.js, jquery-1.7.1.min.js
jquery-1.7.2.min.js
JavaScript library for DOM operations
Library home page: https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.2/jquery.min.js
Path to dependency file: freeCodeCamp/api-server/node_modules/jmespath/index.html
Path to vulnerable library: freeCodeCamp/api-server/node_modules/jmespath/index.html
Dependency Hierarchy:
- :x: **jquery-1.7.2.min.js** (Vulnerable Library)
jquery-1.3.2.min.js
JavaScript library for DOM operations
Library home page: https://cdnjs.cloudflare.com/ajax/libs/jquery/1.3.2/jquery.min.js
Path to dependency file: freeCodeCamp/tools/contributor/lib/node_modules/underscore.string/test/test_underscore/temp_tests.html
Path to vulnerable library: freeCodeCamp/tools/contributor/lib/node_modules/underscore.string/test/test_underscore/vendor/jquery.js
Dependency Hierarchy:
- :x: **jquery-1.3.2.min.js** (Vulnerable Library)
jquery-1.7.1.min.js
JavaScript library for DOM operations
Library home page: https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.1/jquery.min.js
Path to dependency file: freeCodeCamp/tools/contributor/dashboard-app/client/node_modules/sockjs/examples/multiplex/index.html
Path to vulnerable library: freeCodeCamp/tools/contributor/dashboard-app/client/node_modules/sockjs/examples/multiplex/index.html,freeCodeCamp/tools/contributor/dashboard-app/client/node_modules/sockjs/examples/echo/index.html,freeCodeCamp/tools/contributor/dashboard-app/client/node_modules/sockjs/examples/express-3.x/index.html,freeCodeCamp/tools/contributor/dashboard-app/client/node_modules/sockjs/examples/hapi/html/index.html
Dependency Hierarchy:
- :x: **jquery-1.7.1.min.js** (Vulnerable Library)
Found in HEAD commit: 311e89b65c48c9468ebef29fa6a623b9e24a3093
Found in base branch: master
Vulnerability Details
jQuery before 1.9.0 is vulnerable to Cross-site Scripting (XSS) attacks. The jQuery(strInput) function does not differentiate selectors from HTML in a reliable fashion. In vulnerable versions, jQuery determined whether the input was HTML by looking for the '<' character anywhere in the string, giving attackers more flexibility when attempting to construct a malicious payload. In fixed versions, jQuery only deems the input to be HTML if it explicitly starts with the '<' character, limiting exploitability only to attackers who can control the beginning of a string, which is far less common.
Publish Date: 2018-01-18
URL: CVE-2012-6708
CVSS 3 Score Details (6.1)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://nvd.nist.gov/vuln/detail/CVE-2012-6708
Release Date: 2018-01-18
Fix Resolution: jQuery - v1.9.0
The tests should perform at least
- Component testing for the components present and their numbers
- Simulation for events like Button Press
- Props testing
The project tests are based on jest and enzyme. Tests like test1 or test2 could serve as references.
",1.0,"Tests for Weather components - WeatherDetail, WeatherList need tests
WeatherDetail.js
WeatherList.js
The tests should perform at least
- Component testing for the components present and their numbers
- Simulation for events like Button Press
- Props testing
The project tests are based on jest and enzyme. Tests like test1 or test2 could serve as references.
",0,tests for weather components weatherdetail weatherlist need tests the tests should perform at least component testing for the components present and their numbers simulation for events like button press props testing the project tests are based on jest and enzyme tests like or could serve as references ,0
312,5732077001.0,IssuesEvent,2017-04-21 14:02:40,mongoclient/mongoclient,https://api.github.com/repos/mongoclient/mongoclient,closed,Loading libssl.1.0.0 fails,portable-linux potential bug,"I'm trying to run the portable linux-x64 2.0.0 version and it gets stuck on the please wait screen.
I get the following error when running from terminal:
```
[MONGOCLIENT] [MONGOD-STDERR] /home/myuser/linux-portable-x64/resources/app/bin/mongod: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory
[MONGOCLIENT] [MONGOD-EXIT] 127
```
I'm using fedora 25 with openssl 1.0.2k installed.
I tried linking libssl.so.1.0.0 to libssl.so with no success.
## Possible Solution
Also is it possible to make mongoclient use my systems running mongod instead of running it's own mongod?
## Your Environment):
portable linux-x64 2.0.0 version electron app
Fedora Linux 25 with openssl and openssl-devel 1.0.2k",True,"Loading libssl.1.0.0 fails - I'm trying to run the portable linux-x64 2.0.0 version and it gets stuck on the please wait screen.
I get the following error when running from terminal:
```
[MONGOCLIENT] [MONGOD-STDERR] /home/myuser/linux-portable-x64/resources/app/bin/mongod: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory
[MONGOCLIENT] [MONGOD-EXIT] 127
```
I'm using fedora 25 with openssl 1.0.2k installed.
I tried linking libssl.so.1.0.0 to libssl.so with no success.
## Possible Solution
Also is it possible to make mongoclient use my systems running mongod instead of running it's own mongod?
## Your Environment):
portable linux-x64 2.0.0 version electron app
Fedora Linux 25 with openssl and openssl-devel 1.0.2k",1,loading libssl fails i m trying to run the portable linux version and it gets stuck on the please wait screen i get the following error when running from terminal home myuser linux portable resources app bin mongod error while loading shared libraries libssl so cannot open shared object file no such file or directory i m using fedora with openssl installed i tried linking libssl so to libssl so with no success possible solution also is it possible to make mongoclient use my systems running mongod instead of running it s own mongod your environment portable linux version electron app fedora linux with openssl and openssl devel ,1
809,10546870836.0,IssuesEvent,2019-10-02 22:48:27,magnumripper/JohnTheRipper,https://api.github.com/repos/magnumripper/JohnTheRipper,closed,OpenCL formats failing on macOS with Intel HD Graphics 630,notes/external issues portability,"New problems in Mojave (or since last time I checked)
See also #3235, #3434
```
Device 1: Intel(R) HD Graphics 630
Testing: ansible-opencl, Ansible Vault [PBKDF2-SHA256 HMAC-SHA256 OpenCL]... FAILED (cmp_all(49))
Testing: axcrypt-opencl [SHA1 AES OpenCL]... FAILED (get_key(6))
Testing: EncFS-opencl [PBKDF2-SHA1 AES OpenCL]... FAILED (cmp_all(1))
Testing: OpenBSD-SoftRAID-opencl [PBKDF2-SHA1 AES OpenCL]... FAILED (cmp_all(1))
Testing: telegram-opencl [PBKDF2-SHA1 AES OpenCL]... FAILED (cmp_all(2))
Testing: wpapsk-opencl, WPA/WPA2/PMF/PMKID PSK [PBKDF2-SHA1 OpenCL]... FAILED (cmp_all(10))
Testing: wpapsk-pmk-opencl, WPA/WPA2/PMF/PMKID master key [MD5/SHA-1/SHA-2 OpenCL]... FAILED (cmp_all(3))
7 out of 83 tests have FAILED
```",True,"OpenCL formats failing on macOS with Intel HD Graphics 630 - New problems in Mojave (or since last time I checked)
See also #3235, #3434
```
Device 1: Intel(R) HD Graphics 630
Testing: ansible-opencl, Ansible Vault [PBKDF2-SHA256 HMAC-SHA256 OpenCL]... FAILED (cmp_all(49))
Testing: axcrypt-opencl [SHA1 AES OpenCL]... FAILED (get_key(6))
Testing: EncFS-opencl [PBKDF2-SHA1 AES OpenCL]... FAILED (cmp_all(1))
Testing: OpenBSD-SoftRAID-opencl [PBKDF2-SHA1 AES OpenCL]... FAILED (cmp_all(1))
Testing: telegram-opencl [PBKDF2-SHA1 AES OpenCL]... FAILED (cmp_all(2))
Testing: wpapsk-opencl, WPA/WPA2/PMF/PMKID PSK [PBKDF2-SHA1 OpenCL]... FAILED (cmp_all(10))
Testing: wpapsk-pmk-opencl, WPA/WPA2/PMF/PMKID master key [MD5/SHA-1/SHA-2 OpenCL]... FAILED (cmp_all(3))
7 out of 83 tests have FAILED
```",1,opencl formats failing on macos with intel hd graphics new problems in mojave or since last time i checked see also device intel r hd graphics testing ansible opencl ansible vault failed cmp all testing axcrypt opencl failed get key testing encfs opencl failed cmp all testing openbsd softraid opencl failed cmp all testing telegram opencl failed cmp all testing wpapsk opencl wpa pmf pmkid psk failed cmp all testing wpapsk pmk opencl wpa pmf pmkid master key failed cmp all out of tests have failed ,1
1274,17018701024.0,IssuesEvent,2021-07-02 15:28:15,TYPO3-Solr/ext-solr,https://api.github.com/repos/TYPO3-Solr/ext-solr,closed,[BUG] Faked TSFE does not set applicationType in request,BACKPORTABLE,"**Describe the bug**
When initializing the TSFE a TYPO3_REQUEST is also initialized.
A request must always have a applicationType attribute.
If no applicationType is given `ApplicationType::fromRequest($GLOBALS['TYPO3_REQUEST'])`
can't bee used and throws an exception.
**To Reproduce**
Call `ApplicationType::fromRequest($GLOBALS['TYPO3_REQUEST'])` on the
`$GLOBALS['TYPO3_REQUEST']` that is initialized in
`Classes/FrontendEnvironment/Tsfe.php`
This happens for example in https://github.com/networkteam/sentry_client/blob/master/Classes/Client.php#L78
**Expected behavior**
A valid TYPO3_REQUEST should be initialized
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Used versions (please complete the following information):**
- TYPO3 Version: 10.4.16
- EXT:solr Version: 11.0.3
",True,"[BUG] Faked TSFE does not set applicationType in request - **Describe the bug**
When initializing the TSFE a TYPO3_REQUEST is also initialized.
A request must always have a applicationType attribute.
If no applicationType is given `ApplicationType::fromRequest($GLOBALS['TYPO3_REQUEST'])`
can't bee used and throws an exception.
**To Reproduce**
Call `ApplicationType::fromRequest($GLOBALS['TYPO3_REQUEST'])` on the
`$GLOBALS['TYPO3_REQUEST']` that is initialized in
`Classes/FrontendEnvironment/Tsfe.php`
This happens for example in https://github.com/networkteam/sentry_client/blob/master/Classes/Client.php#L78
**Expected behavior**
A valid TYPO3_REQUEST should be initialized
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Used versions (please complete the following information):**
- TYPO3 Version: 10.4.16
- EXT:solr Version: 11.0.3
",1, faked tsfe does not set applicationtype in request describe the bug when initializing the tsfe a request is also initialized a request must always have a applicationtype attribute if no applicationtype is given applicationtype fromrequest globals can t bee used and throws an exception to reproduce call applicationtype fromrequest globals on the globals that is initialized in classes frontendenvironment tsfe php this happens for example in expected behavior a valid request should be initialized screenshots if applicable add screenshots to help explain your problem used versions please complete the following information version ext solr version ,1
163508,13920506105.0,IssuesEvent,2020-10-21 10:32:17,dry-python/returns,https://api.github.com/repos/dry-python/returns,closed,Interfaces documentation,documentation,"This issue is to track what interface we have to document yet, and to split the PRs as well into multiples instead of one with all interfaces:
- [x] Mappable
- [x] Bindable
- [ ] Applicative
- [ ] Container",1.0,"Interfaces documentation - This issue is to track what interface we have to document yet, and to split the PRs as well into multiples instead of one with all interfaces:
- [x] Mappable
- [x] Bindable
- [ ] Applicative
- [ ] Container",0,interfaces documentation this issue is to track what interface we have to document yet and to split the prs as well into multiples instead of one with all interfaces mappable bindable applicative container,0
226,4629425776.0,IssuesEvent,2016-09-28 09:13:11,ocaml/opam-repository,https://api.github.com/repos/ocaml/opam-repository,closed,Package zarith 1.4.1 fails to install in Cygwin+MinGW,portability,"This is related to #5588 : because `gmp.h` is in `/usr/include` and not `/usr/local/include`, `zarith` also fails to find the `gmp` package.
Incidentally, the `opam` file already considers some OSes in a special manner (openbsd, freebsd and darwin), so it suffices to consider cygwin as one of these ""special"" OSes. The `CFLAGS` variable will then be set accordingly.
A second issue I had with zarith 1.4.1 was line 242 in the `configure` file:
if test ""$ocamllibdir"" = ""auto""; then ocamllibdir=`ocamlc -where`; fi
Due to Windows (and possibly a MinGW OCaml compiler) shenanigans, `ocamlc` introduces a `\r` at the end of the command, and so the `ocamllibdir` variable contains the `\r` which prevents the rest from working. I hacked a `| tr -d '\r'` after the `-where` and it worked, but it seems there is already a `echo_n()` function for that.
I didn't submit a pull request because I don't know the exact right way to fix these issues (e.g. I don't have time now to fix them the proper way), but after doing both these patches (and patching my `conf-gmp` as mentioned in #5588) I was able to install zarith on my Cygwin.
I didn't test its actual *usage* though.",True,"Package zarith 1.4.1 fails to install in Cygwin+MinGW - This is related to #5588 : because `gmp.h` is in `/usr/include` and not `/usr/local/include`, `zarith` also fails to find the `gmp` package.
Incidentally, the `opam` file already considers some OSes in a special manner (openbsd, freebsd and darwin), so it suffices to consider cygwin as one of these ""special"" OSes. The `CFLAGS` variable will then be set accordingly.
A second issue I had with zarith 1.4.1 was line 242 in the `configure` file:
if test ""$ocamllibdir"" = ""auto""; then ocamllibdir=`ocamlc -where`; fi
Due to Windows (and possibly a MinGW OCaml compiler) shenanigans, `ocamlc` introduces a `\r` at the end of the command, and so the `ocamllibdir` variable contains the `\r` which prevents the rest from working. I hacked a `| tr -d '\r'` after the `-where` and it worked, but it seems there is already a `echo_n()` function for that.
I didn't submit a pull request because I don't know the exact right way to fix these issues (e.g. I don't have time now to fix them the proper way), but after doing both these patches (and patching my `conf-gmp` as mentioned in #5588) I was able to install zarith on my Cygwin.
I didn't test its actual *usage* though.",1,package zarith fails to install in cygwin mingw this is related to because gmp h is in usr include and not usr local include zarith also fails to find the gmp package incidentally the opam file already considers some oses in a special manner openbsd freebsd and darwin so it suffices to consider cygwin as one of these special oses the cflags variable will then be set accordingly a second issue i had with zarith was line in the configure file if test ocamllibdir auto then ocamllibdir ocamlc where fi due to windows and possibly a mingw ocaml compiler shenanigans ocamlc introduces a r at the end of the command and so the ocamllibdir variable contains the r which prevents the rest from working i hacked a tr d r after the where and it worked but it seems there is already a echo n function for that i didn t submit a pull request because i don t know the exact right way to fix these issues e g i don t have time now to fix them the proper way but after doing both these patches and patching my conf gmp as mentioned in i was able to install zarith on my cygwin i didn t test its actual usage though ,1
147307,13205642297.0,IssuesEvent,2020-08-14 18:23:50,DS4PS/cpp-526-sum-2020,https://api.github.com/repos/DS4PS/cpp-526-sum-2020,opened,Chapter 1 - Arithmetic in R and Function sum(),documentation final-dashboard,"I'm having issues with function `sum()` and `NA` values.
**Expectation:** I expected to get the sum of all values in variable `x`.
",1.0,"Chapter 1 - Arithmetic in R and Function sum() - I'm having issues with function `sum()` and `NA` values.
**Expectation:** I expected to get the sum of all values in variable `x`.
",0,chapter arithmetic in r and function sum i m having issues with function sum and na values expectation i expected to get the sum of all values in variable x ,0
88487,10572714114.0,IssuesEvent,2019-10-07 10:11:46,StefanNieuwenhuis/databindr,https://api.github.com/repos/StefanNieuwenhuis/databindr,closed,Add proper readme,documentation,"As user I want to know how to use this library, so I want to be informed through an elaborate readme.",1.0,"Add proper readme - As user I want to know how to use this library, so I want to be informed through an elaborate readme.",0,add proper readme as user i want to know how to use this library so i want to be informed through an elaborate readme ,0
267085,8378961435.0,IssuesEvent,2018-10-06 19:35:33,swcarpentry/amy,https://api.github.com/repos/swcarpentry/amy,closed,open training should be an option for assigning training requests to ttt events,component: user interface (UI) priority: essential type: bug,"Related to https://github.com/swcarpentry/amy/issues/1055
When matching training requests to a ttt event from the training request page, there is no check box to mark them as open training applicants.
This functionality **does** negatively affect usability as @sheraaron's workflow involves going to the request page and assigning people to trainings in bulk.
@karenword @maneesha ",1.0,"open training should be an option for assigning training requests to ttt events - Related to https://github.com/swcarpentry/amy/issues/1055
When matching training requests to a ttt event from the training request page, there is no check box to mark them as open training applicants.
This functionality **does** negatively affect usability as @sheraaron's workflow involves going to the request page and assigning people to trainings in bulk.
@karenword @maneesha ",0,open training should be an option for assigning training requests to ttt events related to when matching training requests to a ttt event from the training request page there is no check box to mark them as open training applicants this functionality does negatively affect usability as sheraaron s workflow involves going to the request page and assigning people to trainings in bulk karenword maneesha ,0
193477,14653875159.0,IssuesEvent,2020-12-28 07:14:06,github-vet/rangeloop-pointer-findings,https://api.github.com/repos/github-vet/rangeloop-pointer-findings,closed,coreos/fleet: fleetctl/destroy_test.go; 25 LoC,fresh small test,"
Found a possible issue in [coreos/fleet](https://www.github.com/coreos/fleet) at [fleetctl/destroy_test.go](https://github.com/coreos/fleet/blob/4522498327e92ffe6fa24eaa087c73e5af4adb53/fleetctl/destroy_test.go#L67-L91)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.
> range-loop variable r used in defer or goroutine at line 76
[Click here to see the code in its original context.](https://github.com/coreos/fleet/blob/4522498327e92ffe6fa24eaa087c73e5af4adb53/fleetctl/destroy_test.go#L67-L91)
Click here to show the 25 line(s) of Go which triggered the analyzer.
```go
for _, r := range results {
var wg sync.WaitGroup
errchan := make(chan error)
cAPI = newFakeRegistryForCommands(unitPrefix, len(r.units), false)
wg.Add(2)
go func() {
defer wg.Done()
doDestroyUnits(t, r, errchan)
}()
go func() {
defer wg.Done()
doDestroyUnits(t, r, errchan)
}()
go func() {
wg.Wait()
close(errchan)
}()
for err := range errchan {
t.Errorf(""%v"", err)
}
}
```
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: 4522498327e92ffe6fa24eaa087c73e5af4adb53
",1.0,"coreos/fleet: fleetctl/destroy_test.go; 25 LoC -
Found a possible issue in [coreos/fleet](https://www.github.com/coreos/fleet) at [fleetctl/destroy_test.go](https://github.com/coreos/fleet/blob/4522498327e92ffe6fa24eaa087c73e5af4adb53/fleetctl/destroy_test.go#L67-L91)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.
> range-loop variable r used in defer or goroutine at line 76
[Click here to see the code in its original context.](https://github.com/coreos/fleet/blob/4522498327e92ffe6fa24eaa087c73e5af4adb53/fleetctl/destroy_test.go#L67-L91)
Click here to show the 25 line(s) of Go which triggered the analyzer.
```go
for _, r := range results {
var wg sync.WaitGroup
errchan := make(chan error)
cAPI = newFakeRegistryForCommands(unitPrefix, len(r.units), false)
wg.Add(2)
go func() {
defer wg.Done()
doDestroyUnits(t, r, errchan)
}()
go func() {
defer wg.Done()
doDestroyUnits(t, r, errchan)
}()
go func() {
wg.Wait()
close(errchan)
}()
for err := range errchan {
t.Errorf(""%v"", err)
}
}
```
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: 4522498327e92ffe6fa24eaa087c73e5af4adb53
",0,coreos fleet fleetctl destroy test go loc found a possible issue in at below is the message reported by the analyzer for this snippet of code beware that the analyzer only reports the first issue it finds so please do not limit your consideration to the contents of the below message range loop variable r used in defer or goroutine at line click here to show the line s of go which triggered the analyzer go for r range results var wg sync waitgroup errchan make chan error capi newfakeregistryforcommands unitprefix len r units false wg add go func defer wg done dodestroyunits t r errchan go func defer wg done dodestroyunits t r errchan go func wg wait close errchan for err range errchan t errorf v err leave a reaction on this issue to contribute to the project by classifying this instance as a bug mitigated or desirable behavior rocket see the descriptions of the classifications for more information commit id ,0
11354,2649533147.0,IssuesEvent,2015-03-15 00:50:10,Badadroid/badadroid,https://api.github.com/repos/Badadroid/badadroid,closed,insufficient memory! (move ext2system.img),auto-migrated Priority-Medium Type-Defect,"```
can you move the ext2system.img to the sd card?
I can't change theme and run samsung apps application because i haven't enoght
space!
```
Original issue reported on code.google.com by `granzier...@gmail.com` on 14 Dec 2011 at 2:47",1.0,"insufficient memory! (move ext2system.img) - ```
can you move the ext2system.img to the sd card?
I can't change theme and run samsung apps application because i haven't enoght
space!
```
Original issue reported on code.google.com by `granzier...@gmail.com` on 14 Dec 2011 at 2:47",0,insufficient memory move img can you move the img to the sd card i can t change theme and run samsung apps application because i haven t enoght space original issue reported on code google com by granzier gmail com on dec at ,0
581,7986105716.0,IssuesEvent,2018-07-19 00:02:45,rust-lang-nursery/stdsimd,https://api.github.com/repos/rust-lang-nursery/stdsimd,closed,Portable vector shuffles,A-portable,"I've just submitted a PR with an API for portable vector shuffles (https://github.com/rust-lang-nursery/stdsimd/pull/387). From the docs:
```rust
// Shuffle allows reordering the elements of a vector:
let x = i32x4::new(1, 2, 3, 4);
let r = shuffle!(x, [2, 1, 3, 0]);
assert_eq!(r, i32x4::new(3, 2, 4, 1));
// The resulting vector can be smaller than the input:
let r = shuffle!(x, [1, 3]);
assert_eq!(r, i32x2::new(2, 4));
// Equal:
let r = shuffle!(x, [1, 3, 2, 0]);
assert_eq!(r, i32x4::new(2, 4, 3, 1));
// Or larger (at most twice as large):
et r = shuffle!(x, [1, 3, 2, 2, 1, 3, 2, 2]);
assert_eq!(r, i32x8::new(2, 4, 3, 3, 2, 4, 3, 3));
// It also allows reordering elements of two vectors:
let y = i32x4::new(5, 6, 7, 8);
let r = shuffle!(x, y, [4, 0, 5, 1]);
assert_eq!(r, i32x4::new(5, 1, 6, 2));
// And this can be used to construct larger or smaller
// vectors as well.
```
It would be nice to gather feed-back on this.",True,"Portable vector shuffles - I've just submitted a PR with an API for portable vector shuffles (https://github.com/rust-lang-nursery/stdsimd/pull/387). From the docs:
```rust
// Shuffle allows reordering the elements of a vector:
let x = i32x4::new(1, 2, 3, 4);
let r = shuffle!(x, [2, 1, 3, 0]);
assert_eq!(r, i32x4::new(3, 2, 4, 1));
// The resulting vector can be smaller than the input:
let r = shuffle!(x, [1, 3]);
assert_eq!(r, i32x2::new(2, 4));
// Equal:
let r = shuffle!(x, [1, 3, 2, 0]);
assert_eq!(r, i32x4::new(2, 4, 3, 1));
// Or larger (at most twice as large):
et r = shuffle!(x, [1, 3, 2, 2, 1, 3, 2, 2]);
assert_eq!(r, i32x8::new(2, 4, 3, 3, 2, 4, 3, 3));
// It also allows reordering elements of two vectors:
let y = i32x4::new(5, 6, 7, 8);
let r = shuffle!(x, y, [4, 0, 5, 1]);
assert_eq!(r, i32x4::new(5, 1, 6, 2));
// And this can be used to construct larger or smaller
// vectors as well.
```
It would be nice to gather feed-back on this.",1,portable vector shuffles i ve just submitted a pr with an api for portable vector shuffles from the docs rust shuffle allows reordering the elements of a vector let x new let r shuffle x assert eq r new the resulting vector can be smaller than the input let r shuffle x assert eq r new equal let r shuffle x assert eq r new or larger at most twice as large et r shuffle x assert eq r new it also allows reordering elements of two vectors let y new let r shuffle x y assert eq r new and this can be used to construct larger or smaller vectors as well it would be nice to gather feed back on this ,1
439920,12690494028.0,IssuesEvent,2020-06-21 12:27:06,buddyboss/buddyboss-platform,https://api.github.com/repos/buddyboss/buddyboss-platform,opened,Audio file preview for other formats,feature: enhancement priority: medium,"**Is your feature request related to a problem? Please describe.**
Audio file preview uploaded in documents only supports MP3, WAV, and OGG
**Describe alternatives you've considered**
Audio preview should be based on the MIME type
**Support ticket links**
https://secure.helpscout.net/conversation/1198744310/78453",1.0,"Audio file preview for other formats - **Is your feature request related to a problem? Please describe.**
Audio file preview uploaded in documents only supports MP3, WAV, and OGG
**Describe alternatives you've considered**
Audio preview should be based on the MIME type
**Support ticket links**
https://secure.helpscout.net/conversation/1198744310/78453",0,audio file preview for other formats is your feature request related to a problem please describe audio file preview uploaded in documents only supports wav and ogg describe alternatives you ve considered audio preview should be based on the mime type support ticket links ,0
778507,27318748458.0,IssuesEvent,2023-02-24 17:49:18,GoogleContainerTools/skaffold,https://api.github.com/repos/GoogleContainerTools/skaffold,closed,Not able to reference secrets path to home folder,kind/bug priority/p3,"
### Expected behavior
I want to reference a secret file in `build.artifacts.docker.secret.src` in the home directory. This works well if using the realpath but not ~.
### Actual behavior
Using the realpath /home/username/.npmrc works, but using ~/.npmrc doesn't work because skaffold is appending ~/.npmrc to the actual working directory making it search to the wrong place.
I also tried to reference the home directory using $HOME env variable, but it's not a templated field, so doesn't work
### Information
- Skaffold version: skaffold 2.1.0
- Operating system: MacOS Ventura 13
- Installed via: brew
- Contents of skaffold.yaml:
```yaml
build:
local:
useBuildkit: true
artifacts:
- image: image-name
context: .
docker:
secrets:
- id: npmrc
src: ~/.npmrc
```
",1.0,"Not able to reference secrets path to home folder -
### Expected behavior
I want to reference a secret file in `build.artifacts.docker.secret.src` in the home directory. This works well if using the realpath but not ~.
### Actual behavior
Using the realpath /home/username/.npmrc works, but using ~/.npmrc doesn't work because skaffold is appending ~/.npmrc to the actual working directory making it search to the wrong place.
I also tried to reference the home directory using $HOME env variable, but it's not a templated field, so doesn't work
### Information
- Skaffold version: skaffold 2.1.0
- Operating system: MacOS Ventura 13
- Installed via: brew
- Contents of skaffold.yaml:
```yaml
build:
local:
useBuildkit: true
artifacts:
- image: image-name
context: .
docker:
secrets:
- id: npmrc
src: ~/.npmrc
```
",0,not able to reference secrets path to home folder issues without logs and details are more complicated to fix please help us by filling the template below expected behavior i want to reference a secret file in build artifacts docker secret src in the home directory this works well if using the realpath but not actual behavior using the realpath home username npmrc works but using npmrc doesn t work because skaffold is appending npmrc to the actual working directory making it search to the wrong place i also tried to reference the home directory using home env variable but it s not a templated field so doesn t work information skaffold version skaffold operating system macos ventura installed via brew contents of skaffold yaml yaml build local usebuildkit true artifacts image image name context docker secrets id npmrc src npmrc ,0
639,8578486660.0,IssuesEvent,2018-11-13 05:20:00,chapel-lang/chapel,https://api.github.com/repos/chapel-lang/chapel,opened,Heterogeneous GASNET_DOMAIN_COUNT value causes hangs,area: Third-Party type: Portability,"Under gasnet-aries we set `GASNET_DOMAIN_COUNT` to ``. We've been seeing intermittent hangs on a heterogenous system, which we've narrowed down to a single job getting different node types. As a specific example a job on a 28-core BW and 68-core KNL will hang. However, not all combinations seem to hang as a job on 10-core IV and 20-core IV seems to work.
Here's an awful patch that I've been using to reproduce. It sets `GASNET_DOMAIN_COUNT` to `SLURM_NODEID+1`
```diff
diff --git a/runtime/src/comm/gasnet/comm-gasnet.c b/runtime/src/comm/gasnet/comm-gasnet.c
index 2b1e0c6f25..76971f6014 100644
--- a/runtime/src/comm/gasnet/comm-gasnet.c
+++ b/runtime/src/comm/gasnet/comm-gasnet.c
@@ -766,12 +766,13 @@ static void set_max_segsize() {
}
}
+#include ""chpl-env.h""
static void set_num_comm_domains() {
#if defined(GASNET_CONDUIT_GEMINI) || defined(GASNET_CONDUIT_ARIES)
char num_cpus_val[22]; // big enough for an unsigned 64-bit quantity
int num_cpus;
- num_cpus = chpl_topo_getNumCPUsPhysical(true) + 1;
+ num_cpus = chpl_env_str_to_int(""SLURM_NODEID"", getenv(""SLURM_NODEID""), 0) + 1;
snprintf(num_cpus_val, sizeof(num_cpus_val), ""%d"", num_cpus);
if (setenv(""GASNET_DOMAIN_COUNT"", num_cpus_val, 0) != 0) {
```
This fails for me with 2 or more locales.",True,"Heterogeneous GASNET_DOMAIN_COUNT value causes hangs - Under gasnet-aries we set `GASNET_DOMAIN_COUNT` to ``. We've been seeing intermittent hangs on a heterogenous system, which we've narrowed down to a single job getting different node types. As a specific example a job on a 28-core BW and 68-core KNL will hang. However, not all combinations seem to hang as a job on 10-core IV and 20-core IV seems to work.
Here's an awful patch that I've been using to reproduce. It sets `GASNET_DOMAIN_COUNT` to `SLURM_NODEID+1`
```diff
diff --git a/runtime/src/comm/gasnet/comm-gasnet.c b/runtime/src/comm/gasnet/comm-gasnet.c
index 2b1e0c6f25..76971f6014 100644
--- a/runtime/src/comm/gasnet/comm-gasnet.c
+++ b/runtime/src/comm/gasnet/comm-gasnet.c
@@ -766,12 +766,13 @@ static void set_max_segsize() {
}
}
+#include ""chpl-env.h""
static void set_num_comm_domains() {
#if defined(GASNET_CONDUIT_GEMINI) || defined(GASNET_CONDUIT_ARIES)
char num_cpus_val[22]; // big enough for an unsigned 64-bit quantity
int num_cpus;
- num_cpus = chpl_topo_getNumCPUsPhysical(true) + 1;
+ num_cpus = chpl_env_str_to_int(""SLURM_NODEID"", getenv(""SLURM_NODEID""), 0) + 1;
snprintf(num_cpus_val, sizeof(num_cpus_val), ""%d"", num_cpus);
if (setenv(""GASNET_DOMAIN_COUNT"", num_cpus_val, 0) != 0) {
```
This fails for me with 2 or more locales.",1,heterogeneous gasnet domain count value causes hangs under gasnet aries we set gasnet domain count to we ve been seeing intermittent hangs on a heterogenous system which we ve narrowed down to a single job getting different node types as a specific example a job on a core bw and core knl will hang however not all combinations seem to hang as a job on core iv and core iv seems to work here s an awful patch that i ve been using to reproduce it sets gasnet domain count to slurm nodeid diff diff git a runtime src comm gasnet comm gasnet c b runtime src comm gasnet comm gasnet c index a runtime src comm gasnet comm gasnet c b runtime src comm gasnet comm gasnet c static void set max segsize include chpl env h static void set num comm domains if defined gasnet conduit gemini defined gasnet conduit aries char num cpus val big enough for an unsigned bit quantity int num cpus num cpus chpl topo getnumcpusphysical true num cpus chpl env str to int slurm nodeid getenv slurm nodeid snprintf num cpus val sizeof num cpus val d num cpus if setenv gasnet domain count num cpus val this fails for me with or more locales ,1
589399,17695950223.0,IssuesEvent,2021-08-24 15:18:18,EclipseFdn/react-eclipsefdn-members,https://api.github.com/repos/EclipseFdn/react-eclipsefdn-members,closed,Add a field to record the type of organization. ,Front End Backend top-priority,"We need to add a field to record the type of organization.
This would be a mandatory drop down list and would appear before the Member Representative section.
The options would include:
- For Profit Organization
- Non-Profit Open Source Organization / User Group
- Academic Organization
- Standards Organization
- Government Organization, Government Agency, or NGO
- Publishing/Media Organization
- Research Institute
- All others
This information would also be useful to have as part of the summary received by the Membership Coordination team.
For reference, please see the screenshot attached.
Thanks,
Zahra
",1.0,"Add a field to record the type of organization. - We need to add a field to record the type of organization.
This would be a mandatory drop down list and would appear before the Member Representative section.
The options would include:
- For Profit Organization
- Non-Profit Open Source Organization / User Group
- Academic Organization
- Standards Organization
- Government Organization, Government Agency, or NGO
- Publishing/Media Organization
- Research Institute
- All others
This information would also be useful to have as part of the summary received by the Membership Coordination team.
For reference, please see the screenshot attached.
Thanks,
Zahra
",0,add a field to record the type of organization we need to add a field to record the type of organization this would be a mandatory drop down list and would appear before the member representative section the options would include for profit organization non profit open source organization user group academic organization standards organization government organization government agency or ngo publishing media organization research institute all others this information would also be useful to have as part of the summary received by the membership coordination team for reference please see the screenshot attached thanks zahra ,0
482,6971598878.0,IssuesEvent,2017-12-11 14:33:06,edenhill/librdkafka,https://api.github.com/repos/edenhill/librdkafka,closed,segfault with latest kafkacat/librdkafka and Kafka 0.11.0,bug portability,"I have built the latest `kafkacat`/`librdkafka` using kafkacat's `bootstrap.sh`.
I got:
```
Version 1.3.1-13-ga6b599 (JSON) (librdkafka 0.11.0-RC1 builtin.features=gzip,snappy,ssl,sasl,regex,lz4,sasl_gssapi,sasl_plain,sasl_scram,plugins)
```
I am using it contact Kafka brokers using Kerberos and SSL, with the -L option.
For brokers running 0.10.2, `kafkacat` works perfectly well, all the time.
Simply changing the broker queried to one running Kafka 0.11.0, I get segfault most of the time (more than 9 times out of 10).",True,"segfault with latest kafkacat/librdkafka and Kafka 0.11.0 - I have built the latest `kafkacat`/`librdkafka` using kafkacat's `bootstrap.sh`.
I got:
```
Version 1.3.1-13-ga6b599 (JSON) (librdkafka 0.11.0-RC1 builtin.features=gzip,snappy,ssl,sasl,regex,lz4,sasl_gssapi,sasl_plain,sasl_scram,plugins)
```
I am using it contact Kafka brokers using Kerberos and SSL, with the -L option.
For brokers running 0.10.2, `kafkacat` works perfectly well, all the time.
Simply changing the broker queried to one running Kafka 0.11.0, I get segfault most of the time (more than 9 times out of 10).",1,segfault with latest kafkacat librdkafka and kafka i have built the latest kafkacat librdkafka using kafkacat s bootstrap sh i got version json librdkafka builtin features gzip snappy ssl sasl regex sasl gssapi sasl plain sasl scram plugins i am using it contact kafka brokers using kerberos and ssl with the l option for brokers running kafkacat works perfectly well all the time simply changing the broker queried to one running kafka i get segfault most of the time more than times out of ,1
27406,21698978381.0,IssuesEvent,2022-05-10 00:24:38,celeritas-project/celeritas,https://api.github.com/repos/celeritas-project/celeritas,closed,Prototype performance portability,infrastructure,Do an initial port of enough core Celeritas components to at least run some demo applications on non-CUDA hardware.,1.0,Prototype performance portability - Do an initial port of enough core Celeritas components to at least run some demo applications on non-CUDA hardware.,0,prototype performance portability do an initial port of enough core celeritas components to at least run some demo applications on non cuda hardware ,0
1534,22157283056.0,IssuesEvent,2022-06-04 01:52:53,apache/beam,https://api.github.com/repos/apache/beam,opened,Convert external transforms to use StringUtf8Coder instead of ByteArrayCoder,portability P3 improvement sdk-java-core clarified sdk-py-core io-java-kafka,"We currently encode Strings using implicit UTF8 byte arrays. Now, we could use the newly introduced StringUtf8Coder ModelCoder.
Imported from Jira [BEAM-7244](https://issues.apache.org/jira/browse/BEAM-7244). Original Jira may contain additional context.
Reported by: mxm.",True,"Convert external transforms to use StringUtf8Coder instead of ByteArrayCoder - We currently encode Strings using implicit UTF8 byte arrays. Now, we could use the newly introduced StringUtf8Coder ModelCoder.
Imported from Jira [BEAM-7244](https://issues.apache.org/jira/browse/BEAM-7244). Original Jira may contain additional context.
Reported by: mxm.",1,convert external transforms to use instead of bytearraycoder we currently encode strings using implicit byte arrays now we could use the newly introduced modelcoder imported from jira original jira may contain additional context reported by mxm ,1
1810,26775172763.0,IssuesEvent,2023-01-31 16:38:31,alcionai/corso,https://api.github.com/repos/alcionai/corso,closed,GC: Add `Beta` Servicer feature,supportability,"- To complete Backup / Restore pipelines, a beta connector is required for Pages calls.
##### Related to:
- #2169
- #2071
- #2173",True,"GC: Add `Beta` Servicer feature - - To complete Backup / Restore pipelines, a beta connector is required for Pages calls.
##### Related to:
- #2169
- #2071
- #2173",1,gc add beta servicer feature to complete backup restore pipelines a beta connector is required for pages calls related to ,1
444698,12819520343.0,IssuesEvent,2020-07-06 02:28:09,PMEAL/OpenPNM,https://api.github.com/repos/PMEAL/OpenPNM,closed,Run check_network_health as part of _sanity_check,enhancement high priority,"While creating an example for permeability benchmark, I just realized that extracted networks could have disconnected pores, which leads to solver divergence, leaving the user clueless of the cause. I think it's essential that we check for network health prior to running the algorithm. This could be part of the recently added `_sanity_check` method.",1.0,"Run check_network_health as part of _sanity_check - While creating an example for permeability benchmark, I just realized that extracted networks could have disconnected pores, which leads to solver divergence, leaving the user clueless of the cause. I think it's essential that we check for network health prior to running the algorithm. This could be part of the recently added `_sanity_check` method.",0,run check network health as part of sanity check while creating an example for permeability benchmark i just realized that extracted networks could have disconnected pores which leads to solver divergence leaving the user clueless of the cause i think it s essential that we check for network health prior to running the algorithm this could be part of the recently added sanity check method ,0
82795,7852918061.0,IssuesEvent,2018-06-20 15:49:28,eclipse/openj9,https://api.github.com/repos/eclipse/openj9,closed,functional test migration follow-up issues,comp:test,"functional tests will be moved to `functional` folder in `openj9/test/`, Issue #1679 once this movement is done. We need some follow up PR to enhance this movement.
1. move `getdependency to functional level. `
2. make build_list more flexible - it can be target to each sub level of test folder.
3. update readme file to pointing to the right position and mention functional folder. ",1.0,"functional test migration follow-up issues - functional tests will be moved to `functional` folder in `openj9/test/`, Issue #1679 once this movement is done. We need some follow up PR to enhance this movement.
1. move `getdependency to functional level. `
2. make build_list more flexible - it can be target to each sub level of test folder.
3. update readme file to pointing to the right position and mention functional folder. ",0,functional test migration follow up issues functional tests will be moved to functional folder in test issue once this movement is done we need some follow up pr to enhance this movement move getdependency to functional level make build list more flexible it can be target to each sub level of test folder update readme file to pointing to the right position and mention functional folder ,0
229948,18460366955.0,IssuesEvent,2021-10-15 23:51:39,eclipse-openj9/openj9,https://api.github.com/repos/eclipse-openj9/openj9,closed,NPE running DefaultStaticInvokeTest,comp:jit test failure blocker segfault project:MH,"Latest occurrence at https://openj9-jenkins.osuosl.org/job/Test_openjdk17_j9_sanity.openjdk_x86-64_windows_Nightly/8/consoleFull
```
21:27:44 openjdk version ""17-internal"" 2021-09-14
21:27:44 OpenJDK Runtime Environment (build 17-internal+0-adhoc.****.buildjdk17x86-64windowsnightly)
21:27:44 Eclipse OpenJ9 VM (build v0.28.0-release-18bebe9f4e3, JRE 17 Windows Server 2012 R2 amd64-64-Bit Compressed References 20210829_8 (JIT enabled, AOT enabled)
21:27:44 OpenJ9 - 18bebe9f4e3
21:27:44 OMR - 1d0a329
21:27:44 JCL - 712145ee3f5 based on jdk-17+35)
21:51:08 test DefaultStaticInvokeTest.testMethodHandleInvoke(""TestClass7"", ""TestIF7.TestClass7""): failure
21:51:08 java.lang.NullPointerException: Cannot invoke ""java.lang.invoke.MethodHandle.linkToVirtual(java.lang.Object, java.lang.Object, java.lang.invoke.MemberName)"" because """" is null
21:51:08 at java.base/java.lang.invoke.LambdaForm$DMH/0x0000000000000000.invokeVirtual(LambdaForm$DMH)
21:51:08 at java.lang.invoke.LambdaForm$MH/0x0000000095dfc060.invoke(LambdaForm$MH)
21:51:08 at java.lang.invoke.LambdaForm$MH/0x0000000095ddf6f0.invoke_MT(LambdaForm$MH)
21:51:08 at DefaultStaticInvokeTest.testMethodHandleInvoke(DefaultStaticInvokeTest.java:169)
21:51:08 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
21:51:08 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
21:51:08 at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
21:51:08 at java.base/java.lang.reflect.Method.invoke(Method.java:568)
21:51:08 at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:132)
21:51:08 at org.testng.internal.TestInvoker.invokeMethod(TestInvoker.java:599)
21:51:08 at org.testng.internal.TestInvoker.invokeTestMethod(TestInvoker.java:174)
21:51:08 at org.testng.internal.MethodRunner.runInSequence(MethodRunner.java:46)
21:51:08 at org.testng.internal.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:822)
21:51:08 at org.testng.internal.TestInvoker.invokeTestMethods(TestInvoker.java:147)
21:51:08 at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:146)
21:51:08 at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:128)
21:51:08 at org.testng.TestRunner$$Lambda$129/0x0000000096210428.accept(Unknown Source)
21:51:08 at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
21:51:08 at org.testng.TestRunner.privateRun(TestRunner.java:764)
21:51:08 at org.testng.TestRunner.run(TestRunner.java:585)
21:51:08 at org.testng.SuiteRunner.runTest(SuiteRunner.java:384)
21:51:08 at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:378)
21:51:08 at org.testng.SuiteRunner.privateRun(SuiteRunner.java:337)
21:51:08 at org.testng.SuiteRunner.run(SuiteRunner.java:286)
21:51:08 at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:53)
21:51:08 at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:96)
21:51:08 at org.testng.TestNG.runSuitesSequentially(TestNG.java:1218)
21:51:08 at org.testng.TestNG.runSuitesLocally(TestNG.java:1140)
21:51:08 at org.testng.TestNG.runSuites(TestNG.java:1069)
21:51:08 at org.testng.TestNG.run(TestNG.java:1037)
21:51:08 at com.sun.javatest.regtest.agent.TestNGRunner.main(TestNGRunner.java:94)
21:51:08 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
21:51:08 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
21:51:08 at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
21:51:08 at java.base/java.lang.reflect.Method.invoke(Method.java:568)
21:51:08 at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:312)
21:51:08 at java.base/java.lang.Thread.run(Thread.java:884)
21:51:08 ===============================================
21:51:08 java/lang/reflect/DefaultStaticTest/DefaultStaticInvokeTest.java
21:51:08 Total tests run: 276, Passes: 274, Failures: 2, Skips: 0
21:51:08 ===============================================
21:51:08
21:51:08 STDERR:
21:51:08 java.lang.Exception: failures: 2
21:51:08 at com.sun.javatest.regtest.agent.TestNGRunner.main(TestNGRunner.java:96)
21:51:08 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
21:51:08 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
21:51:08 at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
21:51:08 at java.base/java.lang.reflect.Method.invoke(Method.java:568)
21:51:08 at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:312)
21:51:08 at java.base/java.lang.Thread.run(Thread.java:884)
21:51:08
21:51:08 JavaTest Message: Test threw exception: java.lang.Exception
21:51:08 JavaTest Message: shutting down test
21:51:08
21:51:08
21:51:08 TEST RESULT: Failed. Execution failed: `main' threw exception: java.lang.Exception: failures: 2
21:51:08 --------------------------------------------------
21:54:09 Test results: passed: 766; failed: 1
21:54:10 Report written to F:\Users\jenkins\workspace\Test_openjdk17_j9_sanity.openjdk_x86-64_windows_Nightly\jvmtest\openjdk\report\html\report.html
21:54:10 Results written to F:\Users\jenkins\workspace\Test_openjdk17_j9_sanity.openjdk_x86-64_windows_Nightly\aqa-tests\TKG\output_16302870106882\jdk_lang_1\work
21:54:10 Error: Some tests failed or other problems occurred.
21:54:10
21:54:10 jdk_lang_1_FAILED
```",1.0,"NPE running DefaultStaticInvokeTest - Latest occurrence at https://openj9-jenkins.osuosl.org/job/Test_openjdk17_j9_sanity.openjdk_x86-64_windows_Nightly/8/consoleFull
```
21:27:44 openjdk version ""17-internal"" 2021-09-14
21:27:44 OpenJDK Runtime Environment (build 17-internal+0-adhoc.****.buildjdk17x86-64windowsnightly)
21:27:44 Eclipse OpenJ9 VM (build v0.28.0-release-18bebe9f4e3, JRE 17 Windows Server 2012 R2 amd64-64-Bit Compressed References 20210829_8 (JIT enabled, AOT enabled)
21:27:44 OpenJ9 - 18bebe9f4e3
21:27:44 OMR - 1d0a329
21:27:44 JCL - 712145ee3f5 based on jdk-17+35)
21:51:08 test DefaultStaticInvokeTest.testMethodHandleInvoke(""TestClass7"", ""TestIF7.TestClass7""): failure
21:51:08 java.lang.NullPointerException: Cannot invoke ""java.lang.invoke.MethodHandle.linkToVirtual(java.lang.Object, java.lang.Object, java.lang.invoke.MemberName)"" because """" is null
21:51:08 at java.base/java.lang.invoke.LambdaForm$DMH/0x0000000000000000.invokeVirtual(LambdaForm$DMH)
21:51:08 at java.lang.invoke.LambdaForm$MH/0x0000000095dfc060.invoke(LambdaForm$MH)
21:51:08 at java.lang.invoke.LambdaForm$MH/0x0000000095ddf6f0.invoke_MT(LambdaForm$MH)
21:51:08 at DefaultStaticInvokeTest.testMethodHandleInvoke(DefaultStaticInvokeTest.java:169)
21:51:08 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
21:51:08 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
21:51:08 at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
21:51:08 at java.base/java.lang.reflect.Method.invoke(Method.java:568)
21:51:08 at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:132)
21:51:08 at org.testng.internal.TestInvoker.invokeMethod(TestInvoker.java:599)
21:51:08 at org.testng.internal.TestInvoker.invokeTestMethod(TestInvoker.java:174)
21:51:08 at org.testng.internal.MethodRunner.runInSequence(MethodRunner.java:46)
21:51:08 at org.testng.internal.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:822)
21:51:08 at org.testng.internal.TestInvoker.invokeTestMethods(TestInvoker.java:147)
21:51:08 at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:146)
21:51:08 at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:128)
21:51:08 at org.testng.TestRunner$$Lambda$129/0x0000000096210428.accept(Unknown Source)
21:51:08 at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
21:51:08 at org.testng.TestRunner.privateRun(TestRunner.java:764)
21:51:08 at org.testng.TestRunner.run(TestRunner.java:585)
21:51:08 at org.testng.SuiteRunner.runTest(SuiteRunner.java:384)
21:51:08 at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:378)
21:51:08 at org.testng.SuiteRunner.privateRun(SuiteRunner.java:337)
21:51:08 at org.testng.SuiteRunner.run(SuiteRunner.java:286)
21:51:08 at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:53)
21:51:08 at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:96)
21:51:08 at org.testng.TestNG.runSuitesSequentially(TestNG.java:1218)
21:51:08 at org.testng.TestNG.runSuitesLocally(TestNG.java:1140)
21:51:08 at org.testng.TestNG.runSuites(TestNG.java:1069)
21:51:08 at org.testng.TestNG.run(TestNG.java:1037)
21:51:08 at com.sun.javatest.regtest.agent.TestNGRunner.main(TestNGRunner.java:94)
21:51:08 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
21:51:08 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
21:51:08 at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
21:51:08 at java.base/java.lang.reflect.Method.invoke(Method.java:568)
21:51:08 at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:312)
21:51:08 at java.base/java.lang.Thread.run(Thread.java:884)
21:51:08 ===============================================
21:51:08 java/lang/reflect/DefaultStaticTest/DefaultStaticInvokeTest.java
21:51:08 Total tests run: 276, Passes: 274, Failures: 2, Skips: 0
21:51:08 ===============================================
21:51:08
21:51:08 STDERR:
21:51:08 java.lang.Exception: failures: 2
21:51:08 at com.sun.javatest.regtest.agent.TestNGRunner.main(TestNGRunner.java:96)
21:51:08 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
21:51:08 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
21:51:08 at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
21:51:08 at java.base/java.lang.reflect.Method.invoke(Method.java:568)
21:51:08 at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:312)
21:51:08 at java.base/java.lang.Thread.run(Thread.java:884)
21:51:08
21:51:08 JavaTest Message: Test threw exception: java.lang.Exception
21:51:08 JavaTest Message: shutting down test
21:51:08
21:51:08
21:51:08 TEST RESULT: Failed. Execution failed: `main' threw exception: java.lang.Exception: failures: 2
21:51:08 --------------------------------------------------
21:54:09 Test results: passed: 766; failed: 1
21:54:10 Report written to F:\Users\jenkins\workspace\Test_openjdk17_j9_sanity.openjdk_x86-64_windows_Nightly\jvmtest\openjdk\report\html\report.html
21:54:10 Results written to F:\Users\jenkins\workspace\Test_openjdk17_j9_sanity.openjdk_x86-64_windows_Nightly\aqa-tests\TKG\output_16302870106882\jdk_lang_1\work
21:54:10 Error: Some tests failed or other problems occurred.
21:54:10
21:54:10 jdk_lang_1_FAILED
```",0,npe running defaultstaticinvoketest latest occurrence at openjdk version internal openjdk runtime environment build internal adhoc eclipse vm build release jre windows server bit compressed references jit enabled aot enabled omr jcl based on jdk test defaultstaticinvoketest testmethodhandleinvoke failure java lang nullpointerexception cannot invoke java lang invoke methodhandle linktovirtual java lang object java lang object java lang invoke membername because is null at java base java lang invoke lambdaform dmh invokevirtual lambdaform dmh at java lang invoke lambdaform mh invoke lambdaform mh at java lang invoke lambdaform mh invoke mt lambdaform mh at defaultstaticinvoketest testmethodhandleinvoke defaultstaticinvoketest java at java base jdk internal reflect nativemethodaccessorimpl native method at java base jdk internal reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at java base jdk internal reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java base java lang reflect method invoke method java at org testng internal methodinvocationhelper invokemethod methodinvocationhelper java at org testng internal testinvoker invokemethod testinvoker java at org testng internal testinvoker invoketestmethod testinvoker java at org testng internal methodrunner runinsequence methodrunner java at org testng internal testinvoker methodinvocationagent invoke testinvoker java at org testng internal testinvoker invoketestmethods testinvoker java at org testng internal testmethodworker invoketestmethods testmethodworker java at org testng internal testmethodworker run testmethodworker java at org testng testrunner lambda accept unknown source at java base java util arraylist foreach arraylist java at org testng testrunner privaterun testrunner java at org testng testrunner run testrunner java at org testng suiterunner runtest suiterunner java at org testng suiterunner runsequentially suiterunner java at org testng suiterunner privaterun suiterunner java at org testng suiterunner run suiterunner java at org testng suiterunnerworker runsuite suiterunnerworker java at org testng suiterunnerworker run suiterunnerworker java at org testng testng runsuitessequentially testng java at org testng testng runsuiteslocally testng java at org testng testng runsuites testng java at org testng testng run testng java at com sun javatest regtest agent testngrunner main testngrunner java at java base jdk internal reflect nativemethodaccessorimpl native method at java base jdk internal reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at java base jdk internal reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java base java lang reflect method invoke method java at com sun javatest regtest agent mainactionhelper agentvmrunnable run mainactionhelper java at java base java lang thread run thread java java lang reflect defaultstatictest defaultstaticinvoketest java total tests run passes failures skips stderr java lang exception failures at com sun javatest regtest agent testngrunner main testngrunner java at java base jdk internal reflect nativemethodaccessorimpl native method at java base jdk internal reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at java base jdk internal reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java base java lang reflect method invoke method java at com sun javatest regtest agent mainactionhelper agentvmrunnable run mainactionhelper java at java base java lang thread run thread java javatest message test threw exception java lang exception javatest message shutting down test test result failed execution failed main threw exception java lang exception failures test results passed failed report written to f users jenkins workspace test sanity openjdk windows nightly jvmtest openjdk report html report html results written to f users jenkins workspace test sanity openjdk windows nightly aqa tests tkg output jdk lang work error some tests failed or other problems occurred jdk lang failed ,0
1795,26485588137.0,IssuesEvent,2023-01-17 17:44:18,elastic/kibana,https://api.github.com/repos/elastic/kibana,closed,[Portable Dashboards][Controls] Build API Examples,Feature:Input Control Team:Presentation loe:week impact:high Project:Controls Project:Portable Dashboard,"### Why do we need examples?
Currently, the Control Group has the potential to be the unified, user friendly querying system used in many solutions pages. This is blocked by the fact that the only existing usage of the Controls API happens inside the dashboard, which uses a non-preferred creation and syncing method that makes implementing Controls look far more complicated than it is in reality. This could scare off potential implementations.
To showcase the ease of use of Controls, and their excellent DX, we should build a Control Group Examples plugin.
### Examples of examples?
This Control Group example plugin could potentially contain examples of:
- An empty control group in edit mode, where the user is capable of choosing a data view and adding controls via the editor. This may require an add control button, with a configuration object that could be passed in via the `getCreationOptions` callback. (See https://github.com/elastic/kibana/issues/145429 for more info)
- A control group with some preconfigured Controls which use the factory / builder pattern.
- A control group which is set up to listen to filters from a unified search implementation, and output its own filters. A read only JSON editor underneath could display the final, combined filters.
- A control group with its state backed up into the URL. any selections made in a control should show up in the URL
- _Optionally_ - A control group with a new type of add button configured with an array of different controls which could be added and removed by the user with one click.
These are just some ideas, any other examples are welcome! In this process, it is likely that things will need to change on the Control Group embeddable side, which is all fair game!
### Documentation
Additionally, the PR that closes this issue could write more detailed API documentation, and explanations above each example.
### Question:
With the Control Group covered nicely in the example plugin, do we need to continue maintaining the Controls storybooks?
",True,"[Portable Dashboards][Controls] Build API Examples - ### Why do we need examples?
Currently, the Control Group has the potential to be the unified, user friendly querying system used in many solutions pages. This is blocked by the fact that the only existing usage of the Controls API happens inside the dashboard, which uses a non-preferred creation and syncing method that makes implementing Controls look far more complicated than it is in reality. This could scare off potential implementations.
To showcase the ease of use of Controls, and their excellent DX, we should build a Control Group Examples plugin.
### Examples of examples?
This Control Group example plugin could potentially contain examples of:
- An empty control group in edit mode, where the user is capable of choosing a data view and adding controls via the editor. This may require an add control button, with a configuration object that could be passed in via the `getCreationOptions` callback. (See https://github.com/elastic/kibana/issues/145429 for more info)
- A control group with some preconfigured Controls which use the factory / builder pattern.
- A control group which is set up to listen to filters from a unified search implementation, and output its own filters. A read only JSON editor underneath could display the final, combined filters.
- A control group with its state backed up into the URL. any selections made in a control should show up in the URL
- _Optionally_ - A control group with a new type of add button configured with an array of different controls which could be added and removed by the user with one click.
These are just some ideas, any other examples are welcome! In this process, it is likely that things will need to change on the Control Group embeddable side, which is all fair game!
### Documentation
Additionally, the PR that closes this issue could write more detailed API documentation, and explanations above each example.
### Question:
With the Control Group covered nicely in the example plugin, do we need to continue maintaining the Controls storybooks?
",1, build api examples why do we need examples currently the control group has the potential to be the unified user friendly querying system used in many solutions pages this is blocked by the fact that the only existing usage of the controls api happens inside the dashboard which uses a non preferred creation and syncing method that makes implementing controls look far more complicated than it is in reality this could scare off potential implementations to showcase the ease of use of controls and their excellent dx we should build a control group examples plugin examples of examples this control group example plugin could potentially contain examples of an empty control group in edit mode where the user is capable of choosing a data view and adding controls via the editor this may require an add control button with a configuration object that could be passed in via the getcreationoptions callback see for more info a control group with some preconfigured controls which use the factory builder pattern a control group which is set up to listen to filters from a unified search implementation and output its own filters a read only json editor underneath could display the final combined filters a control group with its state backed up into the url any selections made in a control should show up in the url optionally a control group with a new type of add button configured with an array of different controls which could be added and removed by the user with one click these are just some ideas any other examples are welcome in this process it is likely that things will need to change on the control group embeddable side which is all fair game documentation additionally the pr that closes this issue could write more detailed api documentation and explanations above each example question with the control group covered nicely in the example plugin do we need to continue maintaining the controls storybooks ,1
1703,24737459895.0,IssuesEvent,2022-10-20 23:54:24,verilator/verilator,https://api.github.com/repos/verilator/verilator,closed,Verilated objects fails to build when using Macos Monterey,area: portability,"Thanks for taking the time to report this.
# Can you attach an example that shows the issue? (Must be openly licensed, ideally in test_regress format.)
The code is at https://github.com/tianrui-wei/verilator-reproduce
Both examples are from using verilator --timing
## when using the system bundled clang compiler
`verilator --timing --cc --exe half_adder_tb.v half_adder.v`
` make -C obj_dir -f Vhalf_adder_tb.mk CC=clang CXX='clang++ -std=c++20 -fcoroutines-ts'`
Gives me the error
```
In file included from /usr/local/share/verilator/include/verilated_timing.cpp:23:
/usr/local/share/verilator/include/verilated_timing.h:52:12: fatal error: 'coroutine' file not found
# include
^~~~~~~~~~~
1 error generated.
```
## When using the homebrew llvm version and the bundled libc++ library
`verilator --timing --cc --exe half_adder_tb.v half_adder.v`
`make -C obj_dir -f Vhalf_adder_tb.mk CC=clang CXX='clang++ -std=c++20`
Gives me the error
```
In file included from /usr/local/share/verilator/include/verilated_timing.cpp:23:
/usr/local/share/verilator/include/verilated_timing.h:98:10: error: no template named 'coroutine_handle' in namespace 'std'
std::coroutine_handle<> m_coro; // The wrapped coroutine handle
~~~~~^
/usr/local/share/verilator/include/verilated_timing.h:106:28: error: no template named 'coroutine_handle' in namespace 'std'
VlCoroutineHandle(std::coroutine_handle<> coro, VlFileLineDebug fileline)
~~~~~^
/usr/local/share/verilator/include/verilated_timing.h:183:37: error: no template named 'coroutine_handle' in namespace 'std'
void await_suspend(std::coroutine_handle<> coro) {
~~~~~^
/usr/local/share/verilator/include/verilated_timing.h:184:23: error: no matching member function for call to 'push_back'
queue.push_back({delay, VlCoroutineHandle{coro, fileline}});
~~~~~~^~~~~~~~~
/opt/homebrew/opt/llvm/bin/../include/c++/v1/vector:582:66: note: candidate function not viable: cannot convert initializer list argument to 'const std::vector::value_type' (aka 'const VlDelayScheduler::VlDelayedCoroutine')
_LIBCPP_CONSTEXPR_AFTER_CXX17 _LIBCPP_INLINE_VISIBILITY void push_back(const_reference __x);
^
/opt/homebrew/opt/llvm/bin/../include/c++/v1/vector:584:66: note: candidate function not viable: cannot convert initializer list argument to 'std::vector::value_type' (aka 'VlDelayScheduler::VlDelayedCoroutine')
_LIBCPP_CONSTEXPR_AFTER_CXX17 _LIBCPP_INLINE_VISIBILITY void push_back(value_type&& __x);
^
In file included from /usr/local/share/verilator/include/verilated_timing.cpp:23:
/usr/local/share/verilator/include/verilated_timing.h:231:37: error: no template named 'coroutine_handle' in namespace 'std'
void await_suspend(std::coroutine_handle<> coro) {
~~~~~^
/usr/local/share/verilator/include/verilated_timing.h:246:29: error: no template named 'coroutine_handle' in namespace 'std'
bool await_suspend(std::coroutine_handle<>) const { return false; } // Resume immediately
~~~~~^
/usr/local/share/verilator/include/verilated_timing.h:256:29: error: no template named 'coroutine_handle' in namespace 'std'
void await_suspend(std::coroutine_handle<> coro) const { coro.destroy(); }
~~~~~^
/usr/local/share/verilator/include/verilated_timing.h:290:37: error: no template named 'coroutine_handle' in namespace 'std'
void await_suspend(std::coroutine_handle<> coro) { join->m_susp = {coro, fileline}; }
~~~~~^
/usr/local/share/verilator/include/verilated_timing.h:305:14: error: no template named 'coroutine_handle' in namespace 'std'
std::coroutine_handle<> m_continuation; // Coroutine to resume after this one finishes
~~~~~^
/usr/local/share/verilator/include/verilated_timing.h:313:14: error: no type named 'suspend_never' in namespace 'std'
std::suspend_never initial_suspend() const { return {}; }
~~~~~^
/usr/local/share/verilator/include/verilated_timing.h:317:14: error: no type named 'suspend_never' in namespace 'std'
std::suspend_never final_suspend() noexcept;
~~~~~^
/usr/local/share/verilator/include/verilated_timing.h:350:29: error: no template named 'coroutine_handle' in namespace 'std'
void await_suspend(std::coroutine_handle<> coro) { m_promisep->m_continuation = coro; }
~~~~~^
/usr/local/share/verilator/include/verilated_timing.cpp:161:6: error: no type named 'suspend_never' in namespace 'std'
std::suspend_never VlCoroutine::VlPromise::final_suspend() noexcept {
~~~~~^
13 errors generated.
```
# What 'verilator --version' are you using? Did you try it with the git master version?
- Verilator 5.001 devel rev v4.228-148-g8dacbdec3
- This is the git master version
# What OS and distribution are you using?
M1 Pro Macbook Pro, Macos Monterey 12.6
# May we assist you in trying to fix this in Verilator yourself?
Yes that'd be great",True,"Verilated objects fails to build when using Macos Monterey - Thanks for taking the time to report this.
# Can you attach an example that shows the issue? (Must be openly licensed, ideally in test_regress format.)
The code is at https://github.com/tianrui-wei/verilator-reproduce
Both examples are from using verilator --timing
## when using the system bundled clang compiler
`verilator --timing --cc --exe half_adder_tb.v half_adder.v`
` make -C obj_dir -f Vhalf_adder_tb.mk CC=clang CXX='clang++ -std=c++20 -fcoroutines-ts'`
Gives me the error
```
In file included from /usr/local/share/verilator/include/verilated_timing.cpp:23:
/usr/local/share/verilator/include/verilated_timing.h:52:12: fatal error: 'coroutine' file not found
# include
^~~~~~~~~~~
1 error generated.
```
## When using the homebrew llvm version and the bundled libc++ library
`verilator --timing --cc --exe half_adder_tb.v half_adder.v`
`make -C obj_dir -f Vhalf_adder_tb.mk CC=clang CXX='clang++ -std=c++20`
Gives me the error
```
In file included from /usr/local/share/verilator/include/verilated_timing.cpp:23:
/usr/local/share/verilator/include/verilated_timing.h:98:10: error: no template named 'coroutine_handle' in namespace 'std'
std::coroutine_handle<> m_coro; // The wrapped coroutine handle
~~~~~^
/usr/local/share/verilator/include/verilated_timing.h:106:28: error: no template named 'coroutine_handle' in namespace 'std'
VlCoroutineHandle(std::coroutine_handle<> coro, VlFileLineDebug fileline)
~~~~~^
/usr/local/share/verilator/include/verilated_timing.h:183:37: error: no template named 'coroutine_handle' in namespace 'std'
void await_suspend(std::coroutine_handle<> coro) {
~~~~~^
/usr/local/share/verilator/include/verilated_timing.h:184:23: error: no matching member function for call to 'push_back'
queue.push_back({delay, VlCoroutineHandle{coro, fileline}});
~~~~~~^~~~~~~~~
/opt/homebrew/opt/llvm/bin/../include/c++/v1/vector:582:66: note: candidate function not viable: cannot convert initializer list argument to 'const std::vector::value_type' (aka 'const VlDelayScheduler::VlDelayedCoroutine')
_LIBCPP_CONSTEXPR_AFTER_CXX17 _LIBCPP_INLINE_VISIBILITY void push_back(const_reference __x);
^
/opt/homebrew/opt/llvm/bin/../include/c++/v1/vector:584:66: note: candidate function not viable: cannot convert initializer list argument to 'std::vector::value_type' (aka 'VlDelayScheduler::VlDelayedCoroutine')
_LIBCPP_CONSTEXPR_AFTER_CXX17 _LIBCPP_INLINE_VISIBILITY void push_back(value_type&& __x);
^
In file included from /usr/local/share/verilator/include/verilated_timing.cpp:23:
/usr/local/share/verilator/include/verilated_timing.h:231:37: error: no template named 'coroutine_handle' in namespace 'std'
void await_suspend(std::coroutine_handle<> coro) {
~~~~~^
/usr/local/share/verilator/include/verilated_timing.h:246:29: error: no template named 'coroutine_handle' in namespace 'std'
bool await_suspend(std::coroutine_handle<>) const { return false; } // Resume immediately
~~~~~^
/usr/local/share/verilator/include/verilated_timing.h:256:29: error: no template named 'coroutine_handle' in namespace 'std'
void await_suspend(std::coroutine_handle<> coro) const { coro.destroy(); }
~~~~~^
/usr/local/share/verilator/include/verilated_timing.h:290:37: error: no template named 'coroutine_handle' in namespace 'std'
void await_suspend(std::coroutine_handle<> coro) { join->m_susp = {coro, fileline}; }
~~~~~^
/usr/local/share/verilator/include/verilated_timing.h:305:14: error: no template named 'coroutine_handle' in namespace 'std'
std::coroutine_handle<> m_continuation; // Coroutine to resume after this one finishes
~~~~~^
/usr/local/share/verilator/include/verilated_timing.h:313:14: error: no type named 'suspend_never' in namespace 'std'
std::suspend_never initial_suspend() const { return {}; }
~~~~~^
/usr/local/share/verilator/include/verilated_timing.h:317:14: error: no type named 'suspend_never' in namespace 'std'
std::suspend_never final_suspend() noexcept;
~~~~~^
/usr/local/share/verilator/include/verilated_timing.h:350:29: error: no template named 'coroutine_handle' in namespace 'std'
void await_suspend(std::coroutine_handle<> coro) { m_promisep->m_continuation = coro; }
~~~~~^
/usr/local/share/verilator/include/verilated_timing.cpp:161:6: error: no type named 'suspend_never' in namespace 'std'
std::suspend_never VlCoroutine::VlPromise::final_suspend() noexcept {
~~~~~^
13 errors generated.
```
# What 'verilator --version' are you using? Did you try it with the git master version?
- Verilator 5.001 devel rev v4.228-148-g8dacbdec3
- This is the git master version
# What OS and distribution are you using?
M1 Pro Macbook Pro, Macos Monterey 12.6
# May we assist you in trying to fix this in Verilator yourself?
Yes that'd be great",1,verilated objects fails to build when using macos monterey thanks for taking the time to report this can you attach an example that shows the issue must be openly licensed ideally in test regress format the code is at both examples are from using verilator timing when using the system bundled clang compiler verilator timing cc exe half adder tb v half adder v make c obj dir f vhalf adder tb mk cc clang cxx clang std c fcoroutines ts gives me the error in file included from usr local share verilator include verilated timing cpp usr local share verilator include verilated timing h fatal error coroutine file not found include error generated when using the homebrew llvm version and the bundled libc library verilator timing cc exe half adder tb v half adder v make c obj dir f vhalf adder tb mk cc clang cxx clang std c gives me the error in file included from usr local share verilator include verilated timing cpp usr local share verilator include verilated timing h error no template named coroutine handle in namespace std std coroutine handle m coro the wrapped coroutine handle usr local share verilator include verilated timing h error no template named coroutine handle in namespace std vlcoroutinehandle std coroutine handle coro vlfilelinedebug fileline usr local share verilator include verilated timing h error no template named coroutine handle in namespace std void await suspend std coroutine handle coro usr local share verilator include verilated timing h error no matching member function for call to push back queue push back delay vlcoroutinehandle coro fileline opt homebrew opt llvm bin include c vector note candidate function not viable cannot convert initializer list argument to const std vector value type aka const vldelayscheduler vldelayedcoroutine libcpp constexpr after libcpp inline visibility void push back const reference x opt homebrew opt llvm bin include c vector note candidate function not viable cannot convert initializer list argument to std vector value type aka vldelayscheduler vldelayedcoroutine libcpp constexpr after libcpp inline visibility void push back value type x in file included from usr local share verilator include verilated timing cpp usr local share verilator include verilated timing h error no template named coroutine handle in namespace std void await suspend std coroutine handle coro usr local share verilator include verilated timing h error no template named coroutine handle in namespace std bool await suspend std coroutine handle const return false resume immediately usr local share verilator include verilated timing h error no template named coroutine handle in namespace std void await suspend std coroutine handle coro const coro destroy usr local share verilator include verilated timing h error no template named coroutine handle in namespace std void await suspend std coroutine handle coro join m susp coro fileline usr local share verilator include verilated timing h error no template named coroutine handle in namespace std std coroutine handle m continuation coroutine to resume after this one finishes usr local share verilator include verilated timing h error no type named suspend never in namespace std std suspend never initial suspend const return usr local share verilator include verilated timing h error no type named suspend never in namespace std std suspend never final suspend noexcept usr local share verilator include verilated timing h error no template named coroutine handle in namespace std void await suspend std coroutine handle coro m promisep m continuation coro usr local share verilator include verilated timing cpp error no type named suspend never in namespace std std suspend never vlcoroutine vlpromise final suspend noexcept errors generated what verilator version are you using did you try it with the git master version verilator devel rev this is the git master version what os and distribution are you using pro macbook pro macos monterey may we assist you in trying to fix this in verilator yourself yes that d be great,1
1370,19671483285.0,IssuesEvent,2022-01-11 07:52:08,internet2-org/rust-aluvm,https://api.github.com/repos/internet2-org/rust-aluvm,closed,`CoreRegs::default()` causes stack overflow,bug *portability* upstream,"## Current Behavior
```rust
#[test]
fn my_test() { let _register = CoreRegs::default(); }
```
fails with
```
thread 'isa::exec::tests::my_test' has overflowed its stack
fatal runtime error: stack overflow
```
## Cause
https://github.com/internet2-org/rust-aluvm/blob/a7e64abd4a7058bf9f06886452147810b4a5cf6d/src/reg/core_regs.rs#L99
With `Box<[LibSite; CALL_STACK_SIZE]>`, the value would be allocated to stack first, but `CALL_STACK_SIZE = 1 << 16` is too big, resuting in overflow.
## Possible Solutions
Use `Vec` instead.
## Related Issues
https://github.com/rust-lang/rust/issues/53827",True,"`CoreRegs::default()` causes stack overflow - ## Current Behavior
```rust
#[test]
fn my_test() { let _register = CoreRegs::default(); }
```
fails with
```
thread 'isa::exec::tests::my_test' has overflowed its stack
fatal runtime error: stack overflow
```
## Cause
https://github.com/internet2-org/rust-aluvm/blob/a7e64abd4a7058bf9f06886452147810b4a5cf6d/src/reg/core_regs.rs#L99
With `Box<[LibSite; CALL_STACK_SIZE]>`, the value would be allocated to stack first, but `CALL_STACK_SIZE = 1 << 16` is too big, resuting in overflow.
## Possible Solutions
Use `Vec` instead.
## Related Issues
https://github.com/rust-lang/rust/issues/53827",1, coreregs default causes stack overflow current behavior rust fn my test let register coreregs default fails with thread isa exec tests my test has overflowed its stack fatal runtime error stack overflow cause with box the value would be allocated to stack first but call stack size is too big resuting in overflow possible solutions use vec instead related issues ,1
416119,12139743413.0,IssuesEvent,2020-04-23 19:21:36,hyphacoop/organizing,https://api.github.com/repos/hyphacoop/organizing,opened,Host design jam x2 to refine internal look and feel,[priority-★★☆] look&feel wg:business-planning,"_This initial comment is collaborative and open to modification by all._
## Task Summary
🎟️ **Re-ticketed from:** #
🗣 **Loomio:** N/A
📅 **Due date:** N/A
🎯 **Success criteria:** Have developed look and feel for our internal spaces.
Building on #77 and coming out of convo in `1010-04-23 bizdev call`, we wanted to carry the visual look through handbook and chat
## To Do
- [ ] have discussion abt current icons in chat and look and feel
- [ ] jam on ideas for handbook + chat
- ...
",1.0,"Host design jam x2 to refine internal look and feel - _This initial comment is collaborative and open to modification by all._
## Task Summary
🎟️ **Re-ticketed from:** #
🗣 **Loomio:** N/A
📅 **Due date:** N/A
🎯 **Success criteria:** Have developed look and feel for our internal spaces.
Building on #77 and coming out of convo in `1010-04-23 bizdev call`, we wanted to carry the visual look through handbook and chat
## To Do
- [ ] have discussion abt current icons in chat and look and feel
- [ ] jam on ideas for handbook + chat
- ...
",0,host design jam to refine internal look and feel this initial comment is collaborative and open to modification by all task summary 🎟️ re ticketed from 🗣 loomio n a 📅 due date n a 🎯 success criteria have developed look and feel for our internal spaces building on and coming out of convo in bizdev call we wanted to carry the visual look through handbook and chat to do have discussion abt current icons in chat and look and feel jam on ideas for handbook chat ,0
6640,2816057729.0,IssuesEvent,2015-05-19 09:25:33,osakagamba/7GIQSKRNE5P3AVTZCEFXE3ON,https://api.github.com/repos/osakagamba/7GIQSKRNE5P3AVTZCEFXE3ON,closed,Ulhdu0ODZyUoazB2v+QfcYqgc5+Bmg032fATGx0Ms5Qhp9nW2ewqjCFeXL0pdDmlvboaOhnX8pSgbU0yjnFw6YwNNLGISnRzwsSTVTSbmJFzqdo3O4kuMkAoZhmTYGW9qBp/npy8ZUVRpbm6um+rZfI+t9eTV4e8dj3FsuBwquk=,design,aedPphIq7MUjcFjJ8UwpFn9IB4NtMEB7/fM4BldbSqGN0mDCMBB4GYdRmfm8jlv5KBfPgT6eVnTzb4bz3mGZlxyoVExtzmd20XT2lWxv9C67Vb14KsJpCDT0w50wniaOW2fru6oBJsJDh8wkhFOUW9Y48l+w09qDCH9IfI1ugKpXoIlfDEfwpjbvIYwXxvdFiJ6uew2IMJPKkw7CzIxM2VShxWdSr7qQEdJwji3hE7i7vurEBdqfI4E03B8hcq4XsJpmWMsJn9RmsDAgYwyYM8dT6drTKnOZq0YOVNNpN7dMD/RCk/5TCsYc+lELU6JSvbQlD3MgvnLlElDA80hJEH+fShA+cU8VW9CSc7OivKVHKGr7EUeEZy0Z2a4U9h9riaCAW+MqVrjWetKerSXLLrsz6NHOiCccYfGw/cR9FbhLXiVKOmBqybQNihkCfgnNb02D9Nt20B/HYdvi1JL5ycXfv3vQixtrZCBh3+E/ey+0Cgy2h9QzFR/16O6i1yPL0wRlbw0hw6u4u4//U/QBAtSb2865Nyob6jkOaTmPtNxmz6WzP6gu+so/XPVVTbTM5uvoiMolvo6So6x3eoFyrv8e+GtCo4DqFMwkHPcPKisrvEfP6e12HGhycgLqaZ699uq+sfBQ8fnUfrW7p8bo53PSG0Y/ypA6fAbqoH4yjKRIz2Xa+VENm8pQkVGjYr66dXCoykH9itCRtvUMbQoA99YEGI2Rh2dAiqdx8PgMMxr7NToP4O9nOwdS1jPxd8DZdfNBkwPRxd7saQAsdQWYAFp3G+77zZXOzLO79uRQ3Qugy4DUzNxWbDpS7DpDWwAQjxckflhX06hDRb4U4/1kfElTNyACw8CJVZ4kcPwcBL8w3KzFuHuS+LvnrCF+awfeh0w6RHn13wNiUQ+5CbH9M9t5LvtOs5/tGbBimm/30DMnHjq2bzonlty51DtPy5aGcg9n9zOcvMzW+iD0yZCN0WfP4HxnLR1qAIPoZ+/p3CH5OsCssbfMnwah9oGb35BbACIyi/1gSe3cI4esBN7L1ob4U0b9dndEX/QHA6RcsEfKxzb5pwPKx12cNArW8FwxgEht0ZqEeOx3ZG8oOzk0bNHgRkiGCXcWfTqNVDpNVWv70LdO6gQTowJGYWCcPZ3UDJusGnmxtxWTS/LM1k5l7rDBnOxC///Jzdi+19ASGhHy05A/RG/9lR4VNInW4/N+EO7WvicPWhTYpJn2+t7rvu25OU4qVmW29xQadIxTgPs2Q+wJtGIbyjJvfOpDrnI9SJuKaPCYRycHAEeISDcYVHngzZHMyknMZM7/z0UDDj2oU61rFKHFXFPnlo2cMQu83zal1gLcAS/u31ngQ1xbPe9I+ZNaC0Ol1jX+u6aPHW0JHJIki2iZdk8wk7p7O1t5,1.0,Ulhdu0ODZyUoazB2v+QfcYqgc5+Bmg032fATGx0Ms5Qhp9nW2ewqjCFeXL0pdDmlvboaOhnX8pSgbU0yjnFw6YwNNLGISnRzwsSTVTSbmJFzqdo3O4kuMkAoZhmTYGW9qBp/npy8ZUVRpbm6um+rZfI+t9eTV4e8dj3FsuBwquk= - aedPphIq7MUjcFjJ8UwpFn9IB4NtMEB7/fM4BldbSqGN0mDCMBB4GYdRmfm8jlv5KBfPgT6eVnTzb4bz3mGZlxyoVExtzmd20XT2lWxv9C67Vb14KsJpCDT0w50wniaOW2fru6oBJsJDh8wkhFOUW9Y48l+w09qDCH9IfI1ugKpXoIlfDEfwpjbvIYwXxvdFiJ6uew2IMJPKkw7CzIxM2VShxWdSr7qQEdJwji3hE7i7vurEBdqfI4E03B8hcq4XsJpmWMsJn9RmsDAgYwyYM8dT6drTKnOZq0YOVNNpN7dMD/RCk/5TCsYc+lELU6JSvbQlD3MgvnLlElDA80hJEH+fShA+cU8VW9CSc7OivKVHKGr7EUeEZy0Z2a4U9h9riaCAW+MqVrjWetKerSXLLrsz6NHOiCccYfGw/cR9FbhLXiVKOmBqybQNihkCfgnNb02D9Nt20B/HYdvi1JL5ycXfv3vQixtrZCBh3+E/ey+0Cgy2h9QzFR/16O6i1yPL0wRlbw0hw6u4u4//U/QBAtSb2865Nyob6jkOaTmPtNxmz6WzP6gu+so/XPVVTbTM5uvoiMolvo6So6x3eoFyrv8e+GtCo4DqFMwkHPcPKisrvEfP6e12HGhycgLqaZ699uq+sfBQ8fnUfrW7p8bo53PSG0Y/ypA6fAbqoH4yjKRIz2Xa+VENm8pQkVGjYr66dXCoykH9itCRtvUMbQoA99YEGI2Rh2dAiqdx8PgMMxr7NToP4O9nOwdS1jPxd8DZdfNBkwPRxd7saQAsdQWYAFp3G+77zZXOzLO79uRQ3Qugy4DUzNxWbDpS7DpDWwAQjxckflhX06hDRb4U4/1kfElTNyACw8CJVZ4kcPwcBL8w3KzFuHuS+LvnrCF+awfeh0w6RHn13wNiUQ+5CbH9M9t5LvtOs5/tGbBimm/30DMnHjq2bzonlty51DtPy5aGcg9n9zOcvMzW+iD0yZCN0WfP4HxnLR1qAIPoZ+/p3CH5OsCssbfMnwah9oGb35BbACIyi/1gSe3cI4esBN7L1ob4U0b9dndEX/QHA6RcsEfKxzb5pwPKx12cNArW8FwxgEht0ZqEeOx3ZG8oOzk0bNHgRkiGCXcWfTqNVDpNVWv70LdO6gQTowJGYWCcPZ3UDJusGnmxtxWTS/LM1k5l7rDBnOxC///Jzdi+19ASGhHy05A/RG/9lR4VNInW4/N+EO7WvicPWhTYpJn2+t7rvu25OU4qVmW29xQadIxTgPs2Q+wJtGIbyjJvfOpDrnI9SJuKaPCYRycHAEeISDcYVHngzZHMyknMZM7/z0UDDj2oU61rFKHFXFPnlo2cMQu83zal1gLcAS/u31ngQ1xbPe9I+ZNaC0Ol1jX+u6aPHW0JHJIki2iZdk8wk7p7O1t5,0, rzfi rck fsha e ey u so lvnrcf tgbbimm jzdi rg n ,0
273200,8527719935.0,IssuesEvent,2018-11-02 20:30:21,WallarooLabs/wallaroo,https://api.github.com/repos/WallarooLabs/wallaroo,closed,Should parallelized stateless partition router use msg uid instead of step seq ids?,investigation priority: low,"Step seq ids have the advantage of allowing pure round robin sending to the stateless computations in parallel. The disadvantage is that those are really meant for resilience tracking.
Msg uids are meant to be available in all modes, but they aren't sequential, so round robin sending will only happen on average over the course of a run.",1.0,"Should parallelized stateless partition router use msg uid instead of step seq ids? - Step seq ids have the advantage of allowing pure round robin sending to the stateless computations in parallel. The disadvantage is that those are really meant for resilience tracking.
Msg uids are meant to be available in all modes, but they aren't sequential, so round robin sending will only happen on average over the course of a run.",0,should parallelized stateless partition router use msg uid instead of step seq ids step seq ids have the advantage of allowing pure round robin sending to the stateless computations in parallel the disadvantage is that those are really meant for resilience tracking msg uids are meant to be available in all modes but they aren t sequential so round robin sending will only happen on average over the course of a run ,0
112875,9604757401.0,IssuesEvent,2019-05-10 21:01:15,elastic/kibana,https://api.github.com/repos/elastic/kibana,closed,"Failing test: UI Functional Tests.test/functional/apps/visualize/_input_control_vis·js - visualize app input control visualization chained controls ""after all"" hook",failed-test,"A test failed on a tracked branch
```
{ NoSuchSessionError: This driver instance does not have a valid session ID (did you call WebDriver.quit()?) and may no longer be used.
at promise.finally (node_modules/selenium-webdriver/lib/webdriver.js:726:38)
at Object.thenFinally [as finally] (node_modules/selenium-webdriver/lib/promise.js:124:12)
at process._tickCallback (internal/process/next_tick.js:68:7) name: 'NoSuchSessionError', remoteStacktrace: '' }
```
First failure: [Jenkins Build](https://kibana-ci.elastic.co/job/elastic+kibana+master/JOB=kibana-ciGroup10,node=immutable/70/)
",1.0,"Failing test: UI Functional Tests.test/functional/apps/visualize/_input_control_vis·js - visualize app input control visualization chained controls ""after all"" hook - A test failed on a tracked branch
```
{ NoSuchSessionError: This driver instance does not have a valid session ID (did you call WebDriver.quit()?) and may no longer be used.
at promise.finally (node_modules/selenium-webdriver/lib/webdriver.js:726:38)
at Object.thenFinally [as finally] (node_modules/selenium-webdriver/lib/promise.js:124:12)
at process._tickCallback (internal/process/next_tick.js:68:7) name: 'NoSuchSessionError', remoteStacktrace: '' }
```
First failure: [Jenkins Build](https://kibana-ci.elastic.co/job/elastic+kibana+master/JOB=kibana-ciGroup10,node=immutable/70/)
",0,failing test ui functional tests test functional apps visualize input control vis·js visualize app input control visualization chained controls after all hook a test failed on a tracked branch nosuchsessionerror this driver instance does not have a valid session id did you call webdriver quit and may no longer be used at promise finally node modules selenium webdriver lib webdriver js at object thenfinally node modules selenium webdriver lib promise js at process tickcallback internal process next tick js name nosuchsessionerror remotestacktrace first failure ,0
1154,14698612786.0,IssuesEvent,2021-01-04 06:52:32,andrewchambers/bupstash,https://api.github.com/repos/andrewchambers/bupstash,closed,Building on ARM64 fails,portability,"Using following environment:
- rustc: 1.49.0 (e1884a8e3 2020-12-29)
- os: Linux rpi4 5.4.83-1-MANJARO-ARM #1 SMP PREEMPT aarch64 GNU/Linux
- commit: b3e2ee2e3d457cd71fb78854b4a2025879779d79 (current master)
`cargo build --release` fails with the following error
```shell
Compiling libc v0.2.80
Compiling cc v1.0.65
Compiling proc-macro2 v1.0.24
Compiling autocfg v1.0.1
Compiling unicode-xid v0.2.1
Compiling syn v1.0.51
Compiling memchr v2.3.4
Compiling typenum v1.12.0
Compiling version_check v0.9.2
Compiling pkg-config v0.3.19
Compiling lazy_static v1.4.0
Compiling serde_derive v1.0.117
Compiling serde v1.0.117
Compiling bitflags v1.2.1
Compiling cfg-if v1.0.0
Compiling ryu v1.0.5
Compiling unicode-width v0.1.8
Compiling regex-syntax v0.6.21
Compiling serde_json v1.0.59
Compiling subtle v2.3.0
Compiling nix v0.17.0
Compiling anyhow v1.0.34
Compiling linked-hash-map v0.5.3
Compiling cfg-if v0.1.10
Compiling fallible-streaming-iterator v0.1.9
Compiling codemap v0.1.3
Compiling arrayvec v0.5.2
Compiling arrayref v0.3.6
Compiling void v1.0.2
Compiling constant_time_eq v0.1.5
Compiling number_prefix v0.3.0
Compiling termcolor v1.1.2
Compiling itoa v0.4.6
Compiling fallible-iterator v0.2.0
Compiling smallvec v1.5.0
Compiling shlex v0.1.1
Compiling path-clean v0.1.0
Compiling rangemap v0.1.8
Compiling glob v0.3.0
Compiling once_cell v1.5.2
Compiling humantime v2.0.1
Compiling num-traits v0.2.14
Compiling crossbeam-utils v0.8.1
Compiling num-integer v0.1.44
Compiling generic-array v0.14.4
Compiling thread_local v1.0.1
Compiling bupstash v0.6.2 (/home/el/bupstash)
Compiling lz4-sys v1.9.2
Compiling libsqlite3-sys v0.18.0
Compiling blake3 v0.3.7
Compiling getopts v0.2.21
Compiling lru-cache v0.1.2
Compiling quote v1.0.7
Compiling aho-corasick v0.7.15
Compiling time v0.1.44
Compiling terminal_size v0.1.15
Compiling atty v0.2.14
Compiling xattr v0.2.2
Compiling filetime v0.2.13
Compiling fs2 v0.4.3
Compiling regex v1.4.2
Compiling crossbeam-channel v0.5.0
Compiling codemap-diagnostic v0.1.1
Compiling tar v0.4.30
Compiling digest v0.9.0
Compiling crypto-mac v0.8.0
Compiling console v0.13.0
Compiling thiserror-impl v1.0.22
Compiling lz4 v1.23.2
Compiling indicatif v0.15.0
Compiling thiserror v1.0.22
Compiling serde_bare v0.3.0
Compiling chrono v0.4.19
Compiling rusqlite v0.23.1
error[E0308]: mismatched types
--> src/base64.rs:15:13
|
15 | out_buf.as_mut_ptr() as *mut i8,
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `u8`, found `i8`
|
= note: expected raw pointer `*mut u8`
found raw pointer `*mut i8`
error[E0308]: mismatched types
--> src/base64.rs:44:13
|
44 | data.as_ptr() as *const i8,
| ^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `u8`, found `i8`
|
= note: expected raw pointer `*const u8`
found raw pointer `*const i8`
error[E0308]: mismatched types
--> src/base64.rs:48:13
|
48 | std::ptr::null_mut::<*const i8>(),
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `u8`, found `i8`
|
= note: expected raw pointer `*mut *const u8`
found raw pointer `*mut *const i8`
error: aborting due to 3 previous errors
For more information about this error, try `rustc --explain E0308`.
error: could not compile `bupstash`
To learn more, run the command again with --verbose.
```",True,"Building on ARM64 fails - Using following environment:
- rustc: 1.49.0 (e1884a8e3 2020-12-29)
- os: Linux rpi4 5.4.83-1-MANJARO-ARM #1 SMP PREEMPT aarch64 GNU/Linux
- commit: b3e2ee2e3d457cd71fb78854b4a2025879779d79 (current master)
`cargo build --release` fails with the following error
```shell
Compiling libc v0.2.80
Compiling cc v1.0.65
Compiling proc-macro2 v1.0.24
Compiling autocfg v1.0.1
Compiling unicode-xid v0.2.1
Compiling syn v1.0.51
Compiling memchr v2.3.4
Compiling typenum v1.12.0
Compiling version_check v0.9.2
Compiling pkg-config v0.3.19
Compiling lazy_static v1.4.0
Compiling serde_derive v1.0.117
Compiling serde v1.0.117
Compiling bitflags v1.2.1
Compiling cfg-if v1.0.0
Compiling ryu v1.0.5
Compiling unicode-width v0.1.8
Compiling regex-syntax v0.6.21
Compiling serde_json v1.0.59
Compiling subtle v2.3.0
Compiling nix v0.17.0
Compiling anyhow v1.0.34
Compiling linked-hash-map v0.5.3
Compiling cfg-if v0.1.10
Compiling fallible-streaming-iterator v0.1.9
Compiling codemap v0.1.3
Compiling arrayvec v0.5.2
Compiling arrayref v0.3.6
Compiling void v1.0.2
Compiling constant_time_eq v0.1.5
Compiling number_prefix v0.3.0
Compiling termcolor v1.1.2
Compiling itoa v0.4.6
Compiling fallible-iterator v0.2.0
Compiling smallvec v1.5.0
Compiling shlex v0.1.1
Compiling path-clean v0.1.0
Compiling rangemap v0.1.8
Compiling glob v0.3.0
Compiling once_cell v1.5.2
Compiling humantime v2.0.1
Compiling num-traits v0.2.14
Compiling crossbeam-utils v0.8.1
Compiling num-integer v0.1.44
Compiling generic-array v0.14.4
Compiling thread_local v1.0.1
Compiling bupstash v0.6.2 (/home/el/bupstash)
Compiling lz4-sys v1.9.2
Compiling libsqlite3-sys v0.18.0
Compiling blake3 v0.3.7
Compiling getopts v0.2.21
Compiling lru-cache v0.1.2
Compiling quote v1.0.7
Compiling aho-corasick v0.7.15
Compiling time v0.1.44
Compiling terminal_size v0.1.15
Compiling atty v0.2.14
Compiling xattr v0.2.2
Compiling filetime v0.2.13
Compiling fs2 v0.4.3
Compiling regex v1.4.2
Compiling crossbeam-channel v0.5.0
Compiling codemap-diagnostic v0.1.1
Compiling tar v0.4.30
Compiling digest v0.9.0
Compiling crypto-mac v0.8.0
Compiling console v0.13.0
Compiling thiserror-impl v1.0.22
Compiling lz4 v1.23.2
Compiling indicatif v0.15.0
Compiling thiserror v1.0.22
Compiling serde_bare v0.3.0
Compiling chrono v0.4.19
Compiling rusqlite v0.23.1
error[E0308]: mismatched types
--> src/base64.rs:15:13
|
15 | out_buf.as_mut_ptr() as *mut i8,
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `u8`, found `i8`
|
= note: expected raw pointer `*mut u8`
found raw pointer `*mut i8`
error[E0308]: mismatched types
--> src/base64.rs:44:13
|
44 | data.as_ptr() as *const i8,
| ^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `u8`, found `i8`
|
= note: expected raw pointer `*const u8`
found raw pointer `*const i8`
error[E0308]: mismatched types
--> src/base64.rs:48:13
|
48 | std::ptr::null_mut::<*const i8>(),
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `u8`, found `i8`
|
= note: expected raw pointer `*mut *const u8`
found raw pointer `*mut *const i8`
error: aborting due to 3 previous errors
For more information about this error, try `rustc --explain E0308`.
error: could not compile `bupstash`
To learn more, run the command again with --verbose.
```",1,building on fails using following environment rustc os linux manjaro arm smp preempt gnu linux commit current master cargo build release fails with the following error shell compiling libc compiling cc compiling proc compiling autocfg compiling unicode xid compiling syn compiling memchr compiling typenum compiling version check compiling pkg config compiling lazy static compiling serde derive compiling serde compiling bitflags compiling cfg if compiling ryu compiling unicode width compiling regex syntax compiling serde json compiling subtle compiling nix compiling anyhow compiling linked hash map compiling cfg if compiling fallible streaming iterator compiling codemap compiling arrayvec compiling arrayref compiling void compiling constant time eq compiling number prefix compiling termcolor compiling itoa compiling fallible iterator compiling smallvec compiling shlex compiling path clean compiling rangemap compiling glob compiling once cell compiling humantime compiling num traits compiling crossbeam utils compiling num integer compiling generic array compiling thread local compiling bupstash home el bupstash compiling sys compiling sys compiling compiling getopts compiling lru cache compiling quote compiling aho corasick compiling time compiling terminal size compiling atty compiling xattr compiling filetime compiling compiling regex compiling crossbeam channel compiling codemap diagnostic compiling tar compiling digest compiling crypto mac compiling console compiling thiserror impl compiling compiling indicatif compiling thiserror compiling serde bare compiling chrono compiling rusqlite error mismatched types src rs out buf as mut ptr as mut expected found note expected raw pointer mut found raw pointer mut error mismatched types src rs data as ptr as const expected found note expected raw pointer const found raw pointer const error mismatched types src rs std ptr null mut expected found note expected raw pointer mut const found raw pointer mut const error aborting due to previous errors for more information about this error try rustc explain error could not compile bupstash to learn more run the command again with verbose ,1
368032,10864992349.0,IssuesEvent,2019-11-14 18:00:55,siteorigin/so-widgets-bundle,https://api.github.com/repos/siteorigin/so-widgets-bundle,opened,SO Widget Block: Features defaults aren't present,bug priority-2,"In the SO Widget Block, the SiteOrigin Features defaults aren't present.
![]()
Icon container size
Icon size
Features per row
Empty, empty and zero are incorrect defaults for those fields.",1.0,"SO Widget Block: Features defaults aren't present - In the SO Widget Block, the SiteOrigin Features defaults aren't present.
![]()
Icon container size
Icon size
Features per row
Empty, empty and zero are incorrect defaults for those fields.",0,so widget block features defaults aren t present in the so widget block the siteorigin features defaults aren t present img width alt edit page ‹ siteorigin — wordpress src icon container size icon size features per row empty empty and zero are incorrect defaults for those fields ,0
168843,13104276612.0,IssuesEvent,2020-08-04 09:59:14,web-platform-tests/wpt,https://api.github.com/repos/web-platform-tests/wpt,opened,testharness.js reuses an existing #log,cookies testharness.js,"see e.g. http://wpt.live/cookies/http-state/domain-tests.html (cookies/http-state/domain-tests.html)
looking at the testharness.js source this has always been the case, though? this does make these tests rather hard to read however…",1.0,"testharness.js reuses an existing #log - see e.g. http://wpt.live/cookies/http-state/domain-tests.html (cookies/http-state/domain-tests.html)
looking at the testharness.js source this has always been the case, though? this does make these tests rather hard to read however…",0,testharness js reuses an existing log see e g cookies http state domain tests html looking at the testharness js source this has always been the case though this does make these tests rather hard to read however…,0
28,2667158310.0,IssuesEvent,2015-03-22 09:46:12,funcoeszz/funcoeszz,https://api.github.com/repos/funcoeszz/funcoeszz,closed,zzdatafmt: identificador ANO com erro no BSD,bug portabilidade,"```
$ ./run zzdatafmt.sh
..................................................................................................................
--------------------------------------------------------------------------------------------------------------------------------------------------------------
[FAILED #114, line 144] zzdatafmt -f ANO 01/01/1000
@@ -1 +1,3 @@
+usage: date [-jnu] [-d dst] [-r seconds] [-t west] [-v[+|-]val[ymwdHMS]] ...
+ [-f fmt date | [[[mm]dd]HH]MM[[cc]yy][.ss]] [+format]
mil
--------------------------------------------------------------------------------------------------------------------------------------------------------------
.
--------------------------------------------------------------------------------------------------------------------------------------------------------------
[FAILED #115, line 145] zzdatafmt -f ANO 01/01/1900
@@ -1 +1,3 @@
+usage: date [-jnu] [-d dst] [-r seconds] [-t west] [-v[+|-]val[ymwdHMS]] ...
+ [-f fmt date | [[[mm]dd]HH]MM[[cc]yy][.ss]] [+format]
mil e novecentos
--------------------------------------------------------------------------------------------------------------------------------------------------------------
.................................................................................................................................................................................................................................................................................................................................................
FAIL: 2 of 452 tests failed
```
Curioso que o erro acontece somente com alguns anos específicos: 1000 e 1900. Os demais estão OK, como: 1990, 1999, 2000, 2001, 2010.",True,"zzdatafmt: identificador ANO com erro no BSD - ```
$ ./run zzdatafmt.sh
..................................................................................................................
--------------------------------------------------------------------------------------------------------------------------------------------------------------
[FAILED #114, line 144] zzdatafmt -f ANO 01/01/1000
@@ -1 +1,3 @@
+usage: date [-jnu] [-d dst] [-r seconds] [-t west] [-v[+|-]val[ymwdHMS]] ...
+ [-f fmt date | [[[mm]dd]HH]MM[[cc]yy][.ss]] [+format]
mil
--------------------------------------------------------------------------------------------------------------------------------------------------------------
.
--------------------------------------------------------------------------------------------------------------------------------------------------------------
[FAILED #115, line 145] zzdatafmt -f ANO 01/01/1900
@@ -1 +1,3 @@
+usage: date [-jnu] [-d dst] [-r seconds] [-t west] [-v[+|-]val[ymwdHMS]] ...
+ [-f fmt date | [[[mm]dd]HH]MM[[cc]yy][.ss]] [+format]
mil e novecentos
--------------------------------------------------------------------------------------------------------------------------------------------------------------
.................................................................................................................................................................................................................................................................................................................................................
FAIL: 2 of 452 tests failed
```
Curioso que o erro acontece somente com alguns anos específicos: 1000 e 1900. Os demais estão OK, como: 1990, 1999, 2000, 2001, 2010.",1,zzdatafmt identificador ano com erro no bsd run zzdatafmt sh zzdatafmt f ano usage date val dd hh mm yy mil zzdatafmt f ano usage date val dd hh mm yy mil e novecentos fail of tests failed curioso que o erro acontece somente com alguns anos específicos e os demais estão ok como ,1
252945,21640799313.0,IssuesEvent,2022-05-05 18:33:57,damccorm/test-migration-target,https://api.github.com/repos/damccorm/test-migration-target,opened,Document Jenkins ghprb commands,P3 testing task,"Summarize current ghprb (github pull request builder plugin) commands for people to easily find and use instead of to check each groovy file.
commands includes:
""retest this please"",
command to run specific Jenkins build (defined under .test\-infra/jenkins/job_beam_*.groovy).
Imported from Jira [BEAM-3068](https://issues.apache.org/jira/browse/BEAM-3068). Original Jira may contain additional context.
Reported by: markflyhigh.",1.0,"Document Jenkins ghprb commands - Summarize current ghprb (github pull request builder plugin) commands for people to easily find and use instead of to check each groovy file.
commands includes:
""retest this please"",
command to run specific Jenkins build (defined under .test\-infra/jenkins/job_beam_*.groovy).
Imported from Jira [BEAM-3068](https://issues.apache.org/jira/browse/BEAM-3068). Original Jira may contain additional context.
Reported by: markflyhigh.",0,document jenkins ghprb commands summarize current ghprb github pull request builder plugin commands for people to easily find and use instead of to check each groovy file commands includes retest this please command to run specific jenkins build defined under test infra jenkins job beam groovy imported from jira original jira may contain additional context reported by markflyhigh ,0
753768,26360830604.0,IssuesEvent,2023-01-11 13:16:13,Dessia-tech/dessia_common,https://api.github.com/repos/Dessia-tech/dessia_common,closed,Problem with references in case of custom eq,Priority: High Status: To be discussed,"Redefining eq of an object may create side effects in serialization.
Subobjects may not be equal strictly but can be pointed outside of the object, and won't be in the memo
solution: when an object is matched in the memo, keep exploring its subattributes in case they are used elsewhere",1.0,"Problem with references in case of custom eq - Redefining eq of an object may create side effects in serialization.
Subobjects may not be equal strictly but can be pointed outside of the object, and won't be in the memo
solution: when an object is matched in the memo, keep exploring its subattributes in case they are used elsewhere",0,problem with references in case of custom eq redefining eq of an object may create side effects in serialization subobjects may not be equal strictly but can be pointed outside of the object and won t be in the memo solution when an object is matched in the memo keep exploring its subattributes in case they are used elsewhere,0
698,9422081411.0,IssuesEvent,2019-04-11 08:33:01,magnumripper/JohnTheRipper,https://api.github.com/repos/magnumripper/JohnTheRipper,closed,Add preprocessor warnings for formats that are skipped,Fixed - pending verify portability,"Otherwise, users and developers will not notice that (and why) they do not get all the formats.
./configure of course mentions when you don't get OpenCL and CUDA formats in the ""feature summary"" output.
It also mentions pkzip format and generic crypt(3) format.
But it doesn't mention that you don't get OpenVMS format on big endian systems, or if some formats are suppressed due to missing CPU features (SSE4.1, etc).
In these cases, we should add a preprocessor warning, either for DEBUG builds or for all builds.
See comments on commit https://github.com/magnumripper/JohnTheRipper/commit/b1da77d8a235a0517782700f1cbe536e4203b0ed.
At least these formats can be skipped depending on endianness, CPU features, etc:
- [x] Stribog-256
- [x] Stribog-512
- [x] OpenVMS
So we need to add preprocessor warnings in case they are skipped.
",True,"Add preprocessor warnings for formats that are skipped - Otherwise, users and developers will not notice that (and why) they do not get all the formats.
./configure of course mentions when you don't get OpenCL and CUDA formats in the ""feature summary"" output.
It also mentions pkzip format and generic crypt(3) format.
But it doesn't mention that you don't get OpenVMS format on big endian systems, or if some formats are suppressed due to missing CPU features (SSE4.1, etc).
In these cases, we should add a preprocessor warning, either for DEBUG builds or for all builds.
See comments on commit https://github.com/magnumripper/JohnTheRipper/commit/b1da77d8a235a0517782700f1cbe536e4203b0ed.
At least these formats can be skipped depending on endianness, CPU features, etc:
- [x] Stribog-256
- [x] Stribog-512
- [x] OpenVMS
So we need to add preprocessor warnings in case they are skipped.
",1,add preprocessor warnings for formats that are skipped otherwise users and developers will not notice that and why they do not get all the formats configure of course mentions when you don t get opencl and cuda formats in the feature summary output it also mentions pkzip format and generic crypt format but it doesn t mention that you don t get openvms format on big endian systems or if some formats are suppressed due to missing cpu features etc in these cases we should add a preprocessor warning either for debug builds or for all builds see comments on commit at least these formats can be skipped depending on endianness cpu features etc stribog stribog openvms so we need to add preprocessor warnings in case they are skipped ,1
1280,17109499826.0,IssuesEvent,2021-07-10 02:22:44,verilator/verilator,https://api.github.com/repos/verilator/verilator,closed,when I make verilator@4.210 and it failed in spack,area: portability status: asked reporter,"When I make verilator@4.210 and it failed in spack:
```console
[root@centos8 ~]# spack install -y -v --keep-stage --dont-restage --no-checksum --fail-fast verilator@4.210
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/libiconv-1.16-5gvzkthgdyzwipoooaqkilcjetijwrqh
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/pkgconf-1.7.3-qnwffdxtfpwlagzm34msmtobii7iksqf
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/xz-5.2.5-5npvhv6x4hagkymz4dw2suvda5r6hpjk
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/zlib-1.2.11-ysclwr6pk6lufuzqp3tf5la4lreyq7qt
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/berkeley-db-18.1.40-vfyntuwixkzvr2rt2zjeijiqmtuu6brd
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/libsigsegv-2.12-dkxnizjmb3vgeurskkjiysmjcldaaw7x
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/diffutils-3.7-z6t4zfsla623dzpnpwebutiuoenvlt5d
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/tar-1.32-q6qjhc42v4z7prpkjfsowtbjdceh7dbb
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/ncurses-6.2-l6lhmwy4kpgkzfmgiiq2bikklnvulcyf
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/libxml2-2.9.10-cn4eee7gqv7drycs6nybr5pxxlc5uivl
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/m4-1.4.18-xjpzxna5lzr3g4gku6mjy5vz2jiyjvpi
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/bzip2-1.0.8-urctfqbstx2mii7jxupeqeypgbrul37q
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/readline-8.0-6otekrq5w5yaqh7xbi4to7hkewmnddl3
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/libtool-2.4.6-rmp7rhxalhqckvkbsxiicnq5gedv5ygy
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/gettext-0.21-pghfs6ximmdo3cyyhouf5jtwowtyngxf
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/gdbm-1.18.1-sbfql4dkw5n2cri4z34km7dmrjres4fg
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/perl-5.32.1-rs3gej7g7fp5pibnhenekowwbdfphevg
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/help2man-1.47.16-x66avrn7sgvlx7anle7bf4lekqqf232z
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/autoconf-2.69-rl7fity4bcttga7bffj7wisz673gg232
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/texinfo-6.5-jcwiw2ljyr4uauolx7kxbhrshdprlvpj
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/bison-3.7.6-krrkhqqfsuqtfhcnusuenmhz3ukilmqf
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/automake-1.16.3-ycbmiqis6f652tvuz3vkysewhl2m6jky
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/findutils-4.6.0-q3z2d45sn25fcrpvqbfo6nbqy4orlioo
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/flex-2.6.4-qsqamz4edx44n4uqjl57m7trdwqm3zyd
==> Installing verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt
==> No binary for verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt found: installing from source
==> Using cached archive: /home/spack/spack/var/spack/cache/_source-cache/archive/2a/2a821f25e5766884e7c22076790810a386725df31ee9eac58862977b347e2018.tgz
==> No patches needed for verilator
==> verilator: Executing phase: 'autoreconf'
==> verilator: Executing phase: 'configure'
==> [2021-07-09-11:03:03.627507] '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/configure' '--prefix=/home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt'
configuring for Verilator 4.210 2021-07-07
checking whether to perform partial static linking of Verilator binary... yes
checking whether to use tcmalloc... check
checking whether to use -m32... no
checking whether to build for coverage collection... no
checking whether to use hardcoded paths... yes
checking whether to show and stop on compilation warnings... no
checking whether to run long tests... no
checking for gcc... /home/spack/spack/lib/spack/env/gcc/gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether /home/spack/spack/lib/spack/env/gcc/gcc accepts -g... yes
checking for /home/spack/spack/lib/spack/env/gcc/gcc option to accept ISO C89... none needed
checking whether we are using the GNU C++ compiler... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -g... yes
checking for a BSD-compatible install... /usr/bin/install -c
compiler is /home/spack/spack/lib/spack/env/gcc/g++ --version = g++ (GCC) 8.4.1 20200928 (Red Hat 8.4.1-1)
checking that C++ compiler can compile simple program... yes
checking for ar... ar
checking for perl... /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/perl-5.32.1-rs3gej7g7fp5pibnhenekowwbdfphevg/bin/perl
checking for python3... /usr/bin/python3
checking for flex... /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/flex-2.6.4-qsqamz4edx44n4uqjl57m7trdwqm3zyd/bin/flex
/home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/flex-2.6.4-qsqamz4edx44n4uqjl57m7trdwqm3zyd/bin/flex --version = flex 2.6.4
checking for bison... /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/bison-3.7.6-krrkhqqfsuqtfhcnusuenmhz3ukilmqf/bin/bison
/home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/bison-3.7.6-krrkhqqfsuqtfhcnusuenmhz3ukilmqf/bin/bison --version = bison (GNU Bison) 3.7.6
checking for ccache... no
checking how to run the C++ preprocessor... /home/spack/spack/lib/spack/env/gcc/g++ -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for size_t... yes
checking for size_t... (cached) yes
checking for inline... inline
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -pg... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -std=gnu++14... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -std=c++03... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wextra... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wfloat-conversion... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wlogical-op... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wthread-safety... no
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Qunused-arguments... no
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -faligned-new... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wno-unused-parameter... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wno-shadow... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wno-char-subscripts... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wno-null-conversion... no
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wno-parentheses-equality... no
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wno-unused... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Og... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -ggdb... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -gz... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ linker accepts -gz... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -faligned-new... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -fbracket-depth=4096... no
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -fcf-protection=none... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -mno-cet... no
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Qunused-arguments... no
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wno-bool-operation... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wno-tautological-bitwise-compare... no
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wno-parentheses-equality... no
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wno-sign-compare... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wno-uninitialized... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wno-unused-but-set-variable... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wno-unused-parameter... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wno-unused-variable... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wno-shadow... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ linker accepts -mt... no
checking whether /home/spack/spack/lib/spack/env/gcc/g++ linker accepts -pthread... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ linker accepts -lpthread... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ linker accepts -latomic... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ linker accepts -static-libgcc... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ linker accepts -static-libstdc++... no
checking whether /home/spack/spack/lib/spack/env/gcc/g++ linker accepts -Xlinker -gc-sections... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ linker accepts -lpthread... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ linker accepts -lbcrypt... no
checking whether /home/spack/spack/lib/spack/env/gcc/g++ linker accepts -lpsapi... no
checking whether /home/spack/spack/lib/spack/env/gcc/g++ linker accepts -l:libtcmalloc_minimal.a... no
checking whether /home/spack/spack/lib/spack/env/gcc/g++ supports C++11... yes
checking for struct stat.st_mtim.tv_nsec... yes
checking whether SystemC is found (in system path)... no
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating src/Makefile_obj
config.status: creating include/verilated.mk
config.status: creating include/verilated_config.h
config.status: creating verilator.pc
config.status: creating verilator-config.cmake
config.status: creating verilator-config-version.cmake
config.status: creating src/config_build.h
config.status: src/config_build.h is unchanged
Now type 'make' (or sometimes 'gmake') to build Verilator.
==> verilator: Executing phase: 'build'
==> [2021-07-09-11:03:12.017110] 'make' '-j8'
------------------------------------------------------------
making verilator in src
make -C src
make[1]: Entering directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src'
make -C obj_dbg -j 1 TGT=../../bin/verilator_bin_dbg VL_DEBUG=1 -f ../Makefile_obj serial
make -C obj_dbg TGT=../../bin/verilator_coverage_bin_dbg VL_DEBUG=1 VL_VLCOV=1 -f ../Makefile_obj serial_vlcov
make -C obj_opt -j 1 TGT=../../bin/verilator_bin -f ../Makefile_obj serial
make[2]: Entering directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src'
make[2]: warning: -jN forced in submake: disabling jobserver mode.
make[2]: Entering directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src'
make[2]: warning: -jN forced in submake: disabling jobserver mode.
make[2]: Nothing to be done for 'serial'.
make[2]: Leaving directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src/obj_dbg'
make -C obj_dbg TGT=../../bin/verilator_bin_dbg VL_DEBUG=1 -f ../Makefile_obj
make[2]: Entering directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src/obj_dbg'
make[2]: Nothing to be done for 'serial_vlcov'.
make[2]: Leaving directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src/obj_dbg'
make -C obj_dbg TGT=../../bin/verilator_coverage_bin_dbg VL_DEBUG=1 VL_VLCOV=1 -f ../Makefile_obj
make[2]: Nothing to be done for 'serial'.
make[2]: Leaving directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src/obj_opt'
make -C obj_opt TGT=../../bin/verilator_bin -f ../Makefile_obj
make[2]: Entering directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src/obj_dbg'
make[2]: Entering directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src/obj_dbg'
make[2]: Entering directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src/obj_opt'
Compile flags: /home/spack/spack/lib/spack/env/gcc/g++ -Og -ggdb -gz -DVL_DEBUG -D_GLIBCXX_DEBUG -MMD -I. -I.. -I.. -I../../include -I../../include -MP -faligned-new -Wno-unused-parameter -Wno-shadow -DDEFENV_SYSTEMC="""" -DDEFENV_SYSTEMC_ARCH="""" -DDEFENV_SYSTEMC_INCLUDE="""" -DDEFENV_SYSTEMC_LIBDIR="""" -DDEFENV_VERILATOR_ROOT=""/home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/share/verilator""
Compile flags: /home/spack/spack/lib/spack/env/gcc/g++ -Og -ggdb -gz -DVL_DEBUG -D_GLIBCXX_DEBUG -MMD -I. -I.. -I.. -I../../include -I../../include -MP -faligned-new -Wno-unused-parameter -Wno-shadow -DDEFENV_SYSTEMC="""" -DDEFENV_SYSTEMC_ARCH="""" -DDEFENV_SYSTEMC_INCLUDE="""" -DDEFENV_SYSTEMC_LIBDIR="""" -DDEFENV_VERILATOR_ROOT=""/home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/share/verilator""
Compile flags: /home/spack/spack/lib/spack/env/gcc/g++ -O2 -MMD -I. -I.. -I.. -I../../include -I../../include -MP -faligned-new -Wno-unused-parameter -Wno-shadow -DDEFENV_SYSTEMC="""" -DDEFENV_SYSTEMC_ARCH="""" -DDEFENV_SYSTEMC_INCLUDE="""" -DDEFENV_SYSTEMC_LIBDIR="""" -DDEFENV_VERILATOR_ROOT=""/home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/share/verilator""
Linking ../../bin/verilator_coverage_bin_dbg...
/home/spack/spack/lib/spack/env/gcc/g++ -gz -static-libgcc -Xlinker -gc-sections -o ../../bin/verilator_coverage_bin_dbg VlcMain.o -lpthread -lm
make[2]: Leaving directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src/obj_opt'
Linking ../../bin/verilator_bin_dbg...
/home/spack/spack/lib/spack/env/gcc/g++ -gz -static-libgcc -Xlinker -gc-sections -o ../../bin/verilator_bin_dbg Verilator.o V3Active.o V3ActiveTop.o V3Assert.o V3AssertPre.o V3Ast.o V3AstNodes.o V3Begin.o V3Branch.o V3Broken.o V3CCtors.o V3CUse.o V3Case.o V3Cast.o V3Cdc.o V3Changed.o V3Class.o V3Clean.o V3Clock.o V3Combine.o V3Config.o V3Const__gen.o V3Coverage.o V3CoverageJoin.o V3Dead.o V3Delayed.o V3Depth.o V3DepthBlock.o V3Descope.o V3DupFinder.o V3EmitC.o V3EmitCBase.o V3EmitCConstPool.o V3EmitCFunc.o V3EmitCInlines.o V3EmitCMain.o V3EmitCMake.o V3EmitCModel.o V3EmitCSyms.o V3EmitMk.o V3EmitV.o V3EmitXml.o V3Error.o V3Expand.o V3File.o V3FileLine.o V3Gate.o V3GenClk.o V3Global.o V3Graph.o V3GraphAlg.o V3GraphAcyc.o V3GraphDfa.o V3GraphPathChecker.o V3GraphTest.o V3Hash.o V3Hasher.o V3HierBlock.o V3Inline.o V3Inst.o V3InstrCount.o V3Life.o V3LifePost.o V3LinkCells.o V3LinkDot.o V3LinkJump.o V3LinkInc.o V3LinkLValue.o V3LinkLevel.o V3LinkParse.o V3LinkResolve.o V3Localize.o V3MergeCond.o V3Name.o V3Number.o V3OptionParser.o V3Options.o V3Order.o V3Os.o V3Param.o V3Partition.o V3PreShell.o V3Premit.o V3ProtectLib.o V3Randomize.o V3Reloop.o V3Scope.o V3Scoreboard.o V3Slice.o V3Split.o V3SplitAs.o V3SplitVar.o V3Stats.o V3StatsReport.o V3String.o V3Subst.o V3Table.o V3Task.o V3Trace.o V3TraceDecl.o V3Tristate.o V3TSP.o V3Undriven.o V3Unknown.o V3Unroll.o V3Waiver.o V3Width.o V3WidthSel.o V3ParseImp.o V3ParseGrammar.o V3ParseLex.o V3PreProc.o -lpthread -lm
/usr/bin/ld: VlcMain.o: unable to initialize decompress status for section .debug_info
/usr/bin/ld: VlcMain.o: unable to initialize decompress status for section .debug_info
/usr/bin/ld: VlcMain.o: unable to initialize decompress status for section .debug_info
/usr/bin/ld: VlcMain.o: unable to initialize decompress status for section .debug_info
VlcMain.o: file not recognized: File format not recognized
collect2: error: ld returned 1 exit status
make[2]: *** [../Makefile_obj:287: ../../bin/verilator_coverage_bin_dbg] Error 1
make[2]: Leaving directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src/obj_dbg'
make[1]: *** [Makefile:70: ../bin/verilator_coverage_bin_dbg] Error 2
make[1]: *** Waiting for unfinished jobs....
/usr/bin/ld: Verilator.o: unable to initialize decompress status for section .debug_info
/usr/bin/ld: Verilator.o: unable to initialize decompress status for section .debug_info
/usr/bin/ld: Verilator.o: unable to initialize decompress status for section .debug_info
/usr/bin/ld: Verilator.o: unable to initialize decompress status for section .debug_info
Verilator.o: file not recognized: File format not recognized
collect2: error: ld returned 1 exit status
make[2]: *** [../Makefile_obj:287: ../../bin/verilator_bin_dbg] Error 1
make[2]: Leaving directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src/obj_dbg'
make[1]: *** [Makefile:66: ../bin/verilator_bin_dbg] Error 2
make[1]: Leaving directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src'
make: *** [Makefile:233: verilator_exe] Error 2
==> Error: ProcessError: Command exited with status 2:
'make' '-j8'
4 errors found in build log:
144 /home/spack/spack/lib/spack/env/gcc/g++ -gz -static-libgcc -Xlinker -gc-sections -o ../../bin/verilator_bin_dbg Verilator.o V3Active.o V3ActiveTop.o V3Assert.o V3AssertPre.o V3Ast.o V3AstNod
es.o V3Begin.o V3Branch.o V3Broken.o V3CCtors.o V3CUse.o V3Case.o V3Cast.o V3Cdc.o V3Changed.o V3Class.o V3Clean.o V3Clock.o V3Combine.o V3Config.o V3Const__gen.o V3Coverage.o V3CoverageJoin.
o V3Dead.o V3Delayed.o V3Depth.o V3DepthBlock.o V3Descope.o V3DupFinder.o V3EmitC.o V3EmitCBase.o V3EmitCConstPool.o V3EmitCFunc.o V3EmitCInlines.o V3EmitCMain.o V3EmitCMake.o V3EmitCModel.o
V3EmitCSyms.o V3EmitMk.o V3EmitV.o V3EmitXml.o V3Error.o V3Expand.o V3File.o V3FileLine.o V3Gate.o V3GenClk.o V3Global.o V3Graph.o V3GraphAlg.o V3GraphAcyc.o V3GraphDfa.o V3GraphPathChecker.o
V3GraphTest.o V3Hash.o V3Hasher.o V3HierBlock.o V3Inline.o V3Inst.o V3InstrCount.o V3Life.o V3LifePost.o V3LinkCells.o V3LinkDot.o V3LinkJump.o V3LinkInc.o V3LinkLValue.o V3LinkLevel.o V3Lin
kParse.o V3LinkResolve.o V3Localize.o V3MergeCond.o V3Name.o V3Number.o V3OptionParser.o V3Options.o V3Order.o V3Os.o V3Param.o V3Partition.o V3PreShell.o V3Premit.o V3ProtectLib.o V3Randomiz
e.o V3Reloop.o V3Scope.o V3Scoreboard.o V3Slice.o V3Split.o V3SplitAs.o V3SplitVar.o V3Stats.o V3StatsReport.o V3String.o V3Subst.o V3Table.o V3Task.o V3Trace.o V3TraceDecl.o V3Tristate.o V3T
SP.o V3Undriven.o V3Unknown.o V3Unroll.o V3Waiver.o V3Width.o V3WidthSel.o V3ParseImp.o V3ParseGrammar.o V3ParseLex.o V3PreProc.o -lpthread -lm
145 /usr/bin/ld: VlcMain.o: unable to initialize decompress status for section .debug_info
146 /usr/bin/ld: VlcMain.o: unable to initialize decompress status for section .debug_info
147 /usr/bin/ld: VlcMain.o: unable to initialize decompress status for section .debug_info
148 /usr/bin/ld: VlcMain.o: unable to initialize decompress status for section .debug_info
149 VlcMain.o: file not recognized: File format not recognized
>> 150 collect2: error: ld returned 1 exit status
>> 151 make[2]: *** [../Makefile_obj:287: ../../bin/verilator_coverage_bin_dbg] Error 1
152 make[2]: Leaving directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src/obj_dbg'
153 make[1]: *** [Makefile:70: ../bin/verilator_coverage_bin_dbg] Error 2
154 make[1]: *** Waiting for unfinished jobs....
155 /usr/bin/ld: Verilator.o: unable to initialize decompress status for section .debug_info
156 /usr/bin/ld: Verilator.o: unable to initialize decompress status for section .debug_info
157 /usr/bin/ld: Verilator.o: unable to initialize decompress status for section .debug_info
158 /usr/bin/ld: Verilator.o: unable to initialize decompress status for section .debug_info
159 Verilator.o: file not recognized: File format not recognized
>> 160 collect2: error: ld returned 1 exit status
>> 161 make[2]: *** [../Makefile_obj:287: ../../bin/verilator_bin_dbg] Error 1
162 make[2]: Leaving directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src/obj_dbg'
163 make[1]: *** [Makefile:66: ../bin/verilator_bin_dbg] Error 2
164 make[1]: Leaving directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src'
165 make: *** [Makefile:233: verilator_exe] Error 2
See build log for details:
/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-build-out.txt
==> Error: Terminating after first install failure: ProcessError: Command exited with status 2:
'make' '-j8'
```
Can you help me analyze it?
### Information on your system
[root@centos8 ~]# spack debug report
* **Spack:** 0.16.1-1624-a0b5dcca3c
* **Python:** 3.6.8
* **Platform:** linux-centos8-aarch64
* **Concretizer:** original
",True,"when I make verilator@4.210 and it failed in spack - When I make verilator@4.210 and it failed in spack:
```console
[root@centos8 ~]# spack install -y -v --keep-stage --dont-restage --no-checksum --fail-fast verilator@4.210
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/libiconv-1.16-5gvzkthgdyzwipoooaqkilcjetijwrqh
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/pkgconf-1.7.3-qnwffdxtfpwlagzm34msmtobii7iksqf
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/xz-5.2.5-5npvhv6x4hagkymz4dw2suvda5r6hpjk
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/zlib-1.2.11-ysclwr6pk6lufuzqp3tf5la4lreyq7qt
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/berkeley-db-18.1.40-vfyntuwixkzvr2rt2zjeijiqmtuu6brd
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/libsigsegv-2.12-dkxnizjmb3vgeurskkjiysmjcldaaw7x
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/diffutils-3.7-z6t4zfsla623dzpnpwebutiuoenvlt5d
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/tar-1.32-q6qjhc42v4z7prpkjfsowtbjdceh7dbb
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/ncurses-6.2-l6lhmwy4kpgkzfmgiiq2bikklnvulcyf
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/libxml2-2.9.10-cn4eee7gqv7drycs6nybr5pxxlc5uivl
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/m4-1.4.18-xjpzxna5lzr3g4gku6mjy5vz2jiyjvpi
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/bzip2-1.0.8-urctfqbstx2mii7jxupeqeypgbrul37q
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/readline-8.0-6otekrq5w5yaqh7xbi4to7hkewmnddl3
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/libtool-2.4.6-rmp7rhxalhqckvkbsxiicnq5gedv5ygy
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/gettext-0.21-pghfs6ximmdo3cyyhouf5jtwowtyngxf
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/gdbm-1.18.1-sbfql4dkw5n2cri4z34km7dmrjres4fg
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/perl-5.32.1-rs3gej7g7fp5pibnhenekowwbdfphevg
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/help2man-1.47.16-x66avrn7sgvlx7anle7bf4lekqqf232z
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/autoconf-2.69-rl7fity4bcttga7bffj7wisz673gg232
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/texinfo-6.5-jcwiw2ljyr4uauolx7kxbhrshdprlvpj
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/bison-3.7.6-krrkhqqfsuqtfhcnusuenmhz3ukilmqf
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/automake-1.16.3-ycbmiqis6f652tvuz3vkysewhl2m6jky
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/findutils-4.6.0-q3z2d45sn25fcrpvqbfo6nbqy4orlioo
[+] /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/flex-2.6.4-qsqamz4edx44n4uqjl57m7trdwqm3zyd
==> Installing verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt
==> No binary for verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt found: installing from source
==> Using cached archive: /home/spack/spack/var/spack/cache/_source-cache/archive/2a/2a821f25e5766884e7c22076790810a386725df31ee9eac58862977b347e2018.tgz
==> No patches needed for verilator
==> verilator: Executing phase: 'autoreconf'
==> verilator: Executing phase: 'configure'
==> [2021-07-09-11:03:03.627507] '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/configure' '--prefix=/home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt'
configuring for Verilator 4.210 2021-07-07
checking whether to perform partial static linking of Verilator binary... yes
checking whether to use tcmalloc... check
checking whether to use -m32... no
checking whether to build for coverage collection... no
checking whether to use hardcoded paths... yes
checking whether to show and stop on compilation warnings... no
checking whether to run long tests... no
checking for gcc... /home/spack/spack/lib/spack/env/gcc/gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether /home/spack/spack/lib/spack/env/gcc/gcc accepts -g... yes
checking for /home/spack/spack/lib/spack/env/gcc/gcc option to accept ISO C89... none needed
checking whether we are using the GNU C++ compiler... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -g... yes
checking for a BSD-compatible install... /usr/bin/install -c
compiler is /home/spack/spack/lib/spack/env/gcc/g++ --version = g++ (GCC) 8.4.1 20200928 (Red Hat 8.4.1-1)
checking that C++ compiler can compile simple program... yes
checking for ar... ar
checking for perl... /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/perl-5.32.1-rs3gej7g7fp5pibnhenekowwbdfphevg/bin/perl
checking for python3... /usr/bin/python3
checking for flex... /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/flex-2.6.4-qsqamz4edx44n4uqjl57m7trdwqm3zyd/bin/flex
/home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/flex-2.6.4-qsqamz4edx44n4uqjl57m7trdwqm3zyd/bin/flex --version = flex 2.6.4
checking for bison... /home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/bison-3.7.6-krrkhqqfsuqtfhcnusuenmhz3ukilmqf/bin/bison
/home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/bison-3.7.6-krrkhqqfsuqtfhcnusuenmhz3ukilmqf/bin/bison --version = bison (GNU Bison) 3.7.6
checking for ccache... no
checking how to run the C++ preprocessor... /home/spack/spack/lib/spack/env/gcc/g++ -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for size_t... yes
checking for size_t... (cached) yes
checking for inline... inline
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -pg... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -std=gnu++14... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -std=c++03... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wextra... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wfloat-conversion... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wlogical-op... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wthread-safety... no
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Qunused-arguments... no
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -faligned-new... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wno-unused-parameter... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wno-shadow... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wno-char-subscripts... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wno-null-conversion... no
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wno-parentheses-equality... no
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wno-unused... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Og... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -ggdb... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -gz... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ linker accepts -gz... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -faligned-new... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -fbracket-depth=4096... no
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -fcf-protection=none... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -mno-cet... no
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Qunused-arguments... no
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wno-bool-operation... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wno-tautological-bitwise-compare... no
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wno-parentheses-equality... no
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wno-sign-compare... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wno-uninitialized... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wno-unused-but-set-variable... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wno-unused-parameter... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wno-unused-variable... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ accepts -Wno-shadow... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ linker accepts -mt... no
checking whether /home/spack/spack/lib/spack/env/gcc/g++ linker accepts -pthread... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ linker accepts -lpthread... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ linker accepts -latomic... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ linker accepts -static-libgcc... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ linker accepts -static-libstdc++... no
checking whether /home/spack/spack/lib/spack/env/gcc/g++ linker accepts -Xlinker -gc-sections... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ linker accepts -lpthread... yes
checking whether /home/spack/spack/lib/spack/env/gcc/g++ linker accepts -lbcrypt... no
checking whether /home/spack/spack/lib/spack/env/gcc/g++ linker accepts -lpsapi... no
checking whether /home/spack/spack/lib/spack/env/gcc/g++ linker accepts -l:libtcmalloc_minimal.a... no
checking whether /home/spack/spack/lib/spack/env/gcc/g++ supports C++11... yes
checking for struct stat.st_mtim.tv_nsec... yes
checking whether SystemC is found (in system path)... no
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating src/Makefile_obj
config.status: creating include/verilated.mk
config.status: creating include/verilated_config.h
config.status: creating verilator.pc
config.status: creating verilator-config.cmake
config.status: creating verilator-config-version.cmake
config.status: creating src/config_build.h
config.status: src/config_build.h is unchanged
Now type 'make' (or sometimes 'gmake') to build Verilator.
==> verilator: Executing phase: 'build'
==> [2021-07-09-11:03:12.017110] 'make' '-j8'
------------------------------------------------------------
making verilator in src
make -C src
make[1]: Entering directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src'
make -C obj_dbg -j 1 TGT=../../bin/verilator_bin_dbg VL_DEBUG=1 -f ../Makefile_obj serial
make -C obj_dbg TGT=../../bin/verilator_coverage_bin_dbg VL_DEBUG=1 VL_VLCOV=1 -f ../Makefile_obj serial_vlcov
make -C obj_opt -j 1 TGT=../../bin/verilator_bin -f ../Makefile_obj serial
make[2]: Entering directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src'
make[2]: warning: -jN forced in submake: disabling jobserver mode.
make[2]: Entering directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src'
make[2]: warning: -jN forced in submake: disabling jobserver mode.
make[2]: Nothing to be done for 'serial'.
make[2]: Leaving directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src/obj_dbg'
make -C obj_dbg TGT=../../bin/verilator_bin_dbg VL_DEBUG=1 -f ../Makefile_obj
make[2]: Entering directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src/obj_dbg'
make[2]: Nothing to be done for 'serial_vlcov'.
make[2]: Leaving directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src/obj_dbg'
make -C obj_dbg TGT=../../bin/verilator_coverage_bin_dbg VL_DEBUG=1 VL_VLCOV=1 -f ../Makefile_obj
make[2]: Nothing to be done for 'serial'.
make[2]: Leaving directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src/obj_opt'
make -C obj_opt TGT=../../bin/verilator_bin -f ../Makefile_obj
make[2]: Entering directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src/obj_dbg'
make[2]: Entering directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src/obj_dbg'
make[2]: Entering directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src/obj_opt'
Compile flags: /home/spack/spack/lib/spack/env/gcc/g++ -Og -ggdb -gz -DVL_DEBUG -D_GLIBCXX_DEBUG -MMD -I. -I.. -I.. -I../../include -I../../include -MP -faligned-new -Wno-unused-parameter -Wno-shadow -DDEFENV_SYSTEMC="""" -DDEFENV_SYSTEMC_ARCH="""" -DDEFENV_SYSTEMC_INCLUDE="""" -DDEFENV_SYSTEMC_LIBDIR="""" -DDEFENV_VERILATOR_ROOT=""/home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/share/verilator""
Compile flags: /home/spack/spack/lib/spack/env/gcc/g++ -Og -ggdb -gz -DVL_DEBUG -D_GLIBCXX_DEBUG -MMD -I. -I.. -I.. -I../../include -I../../include -MP -faligned-new -Wno-unused-parameter -Wno-shadow -DDEFENV_SYSTEMC="""" -DDEFENV_SYSTEMC_ARCH="""" -DDEFENV_SYSTEMC_INCLUDE="""" -DDEFENV_SYSTEMC_LIBDIR="""" -DDEFENV_VERILATOR_ROOT=""/home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/share/verilator""
Compile flags: /home/spack/spack/lib/spack/env/gcc/g++ -O2 -MMD -I. -I.. -I.. -I../../include -I../../include -MP -faligned-new -Wno-unused-parameter -Wno-shadow -DDEFENV_SYSTEMC="""" -DDEFENV_SYSTEMC_ARCH="""" -DDEFENV_SYSTEMC_INCLUDE="""" -DDEFENV_SYSTEMC_LIBDIR="""" -DDEFENV_VERILATOR_ROOT=""/home/spack/spack/opt/spack/linux-centos8-aarch64/gcc-8.4.1/verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/share/verilator""
Linking ../../bin/verilator_coverage_bin_dbg...
/home/spack/spack/lib/spack/env/gcc/g++ -gz -static-libgcc -Xlinker -gc-sections -o ../../bin/verilator_coverage_bin_dbg VlcMain.o -lpthread -lm
make[2]: Leaving directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src/obj_opt'
Linking ../../bin/verilator_bin_dbg...
/home/spack/spack/lib/spack/env/gcc/g++ -gz -static-libgcc -Xlinker -gc-sections -o ../../bin/verilator_bin_dbg Verilator.o V3Active.o V3ActiveTop.o V3Assert.o V3AssertPre.o V3Ast.o V3AstNodes.o V3Begin.o V3Branch.o V3Broken.o V3CCtors.o V3CUse.o V3Case.o V3Cast.o V3Cdc.o V3Changed.o V3Class.o V3Clean.o V3Clock.o V3Combine.o V3Config.o V3Const__gen.o V3Coverage.o V3CoverageJoin.o V3Dead.o V3Delayed.o V3Depth.o V3DepthBlock.o V3Descope.o V3DupFinder.o V3EmitC.o V3EmitCBase.o V3EmitCConstPool.o V3EmitCFunc.o V3EmitCInlines.o V3EmitCMain.o V3EmitCMake.o V3EmitCModel.o V3EmitCSyms.o V3EmitMk.o V3EmitV.o V3EmitXml.o V3Error.o V3Expand.o V3File.o V3FileLine.o V3Gate.o V3GenClk.o V3Global.o V3Graph.o V3GraphAlg.o V3GraphAcyc.o V3GraphDfa.o V3GraphPathChecker.o V3GraphTest.o V3Hash.o V3Hasher.o V3HierBlock.o V3Inline.o V3Inst.o V3InstrCount.o V3Life.o V3LifePost.o V3LinkCells.o V3LinkDot.o V3LinkJump.o V3LinkInc.o V3LinkLValue.o V3LinkLevel.o V3LinkParse.o V3LinkResolve.o V3Localize.o V3MergeCond.o V3Name.o V3Number.o V3OptionParser.o V3Options.o V3Order.o V3Os.o V3Param.o V3Partition.o V3PreShell.o V3Premit.o V3ProtectLib.o V3Randomize.o V3Reloop.o V3Scope.o V3Scoreboard.o V3Slice.o V3Split.o V3SplitAs.o V3SplitVar.o V3Stats.o V3StatsReport.o V3String.o V3Subst.o V3Table.o V3Task.o V3Trace.o V3TraceDecl.o V3Tristate.o V3TSP.o V3Undriven.o V3Unknown.o V3Unroll.o V3Waiver.o V3Width.o V3WidthSel.o V3ParseImp.o V3ParseGrammar.o V3ParseLex.o V3PreProc.o -lpthread -lm
/usr/bin/ld: VlcMain.o: unable to initialize decompress status for section .debug_info
/usr/bin/ld: VlcMain.o: unable to initialize decompress status for section .debug_info
/usr/bin/ld: VlcMain.o: unable to initialize decompress status for section .debug_info
/usr/bin/ld: VlcMain.o: unable to initialize decompress status for section .debug_info
VlcMain.o: file not recognized: File format not recognized
collect2: error: ld returned 1 exit status
make[2]: *** [../Makefile_obj:287: ../../bin/verilator_coverage_bin_dbg] Error 1
make[2]: Leaving directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src/obj_dbg'
make[1]: *** [Makefile:70: ../bin/verilator_coverage_bin_dbg] Error 2
make[1]: *** Waiting for unfinished jobs....
/usr/bin/ld: Verilator.o: unable to initialize decompress status for section .debug_info
/usr/bin/ld: Verilator.o: unable to initialize decompress status for section .debug_info
/usr/bin/ld: Verilator.o: unable to initialize decompress status for section .debug_info
/usr/bin/ld: Verilator.o: unable to initialize decompress status for section .debug_info
Verilator.o: file not recognized: File format not recognized
collect2: error: ld returned 1 exit status
make[2]: *** [../Makefile_obj:287: ../../bin/verilator_bin_dbg] Error 1
make[2]: Leaving directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src/obj_dbg'
make[1]: *** [Makefile:66: ../bin/verilator_bin_dbg] Error 2
make[1]: Leaving directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src'
make: *** [Makefile:233: verilator_exe] Error 2
==> Error: ProcessError: Command exited with status 2:
'make' '-j8'
4 errors found in build log:
144 /home/spack/spack/lib/spack/env/gcc/g++ -gz -static-libgcc -Xlinker -gc-sections -o ../../bin/verilator_bin_dbg Verilator.o V3Active.o V3ActiveTop.o V3Assert.o V3AssertPre.o V3Ast.o V3AstNod
es.o V3Begin.o V3Branch.o V3Broken.o V3CCtors.o V3CUse.o V3Case.o V3Cast.o V3Cdc.o V3Changed.o V3Class.o V3Clean.o V3Clock.o V3Combine.o V3Config.o V3Const__gen.o V3Coverage.o V3CoverageJoin.
o V3Dead.o V3Delayed.o V3Depth.o V3DepthBlock.o V3Descope.o V3DupFinder.o V3EmitC.o V3EmitCBase.o V3EmitCConstPool.o V3EmitCFunc.o V3EmitCInlines.o V3EmitCMain.o V3EmitCMake.o V3EmitCModel.o
V3EmitCSyms.o V3EmitMk.o V3EmitV.o V3EmitXml.o V3Error.o V3Expand.o V3File.o V3FileLine.o V3Gate.o V3GenClk.o V3Global.o V3Graph.o V3GraphAlg.o V3GraphAcyc.o V3GraphDfa.o V3GraphPathChecker.o
V3GraphTest.o V3Hash.o V3Hasher.o V3HierBlock.o V3Inline.o V3Inst.o V3InstrCount.o V3Life.o V3LifePost.o V3LinkCells.o V3LinkDot.o V3LinkJump.o V3LinkInc.o V3LinkLValue.o V3LinkLevel.o V3Lin
kParse.o V3LinkResolve.o V3Localize.o V3MergeCond.o V3Name.o V3Number.o V3OptionParser.o V3Options.o V3Order.o V3Os.o V3Param.o V3Partition.o V3PreShell.o V3Premit.o V3ProtectLib.o V3Randomiz
e.o V3Reloop.o V3Scope.o V3Scoreboard.o V3Slice.o V3Split.o V3SplitAs.o V3SplitVar.o V3Stats.o V3StatsReport.o V3String.o V3Subst.o V3Table.o V3Task.o V3Trace.o V3TraceDecl.o V3Tristate.o V3T
SP.o V3Undriven.o V3Unknown.o V3Unroll.o V3Waiver.o V3Width.o V3WidthSel.o V3ParseImp.o V3ParseGrammar.o V3ParseLex.o V3PreProc.o -lpthread -lm
145 /usr/bin/ld: VlcMain.o: unable to initialize decompress status for section .debug_info
146 /usr/bin/ld: VlcMain.o: unable to initialize decompress status for section .debug_info
147 /usr/bin/ld: VlcMain.o: unable to initialize decompress status for section .debug_info
148 /usr/bin/ld: VlcMain.o: unable to initialize decompress status for section .debug_info
149 VlcMain.o: file not recognized: File format not recognized
>> 150 collect2: error: ld returned 1 exit status
>> 151 make[2]: *** [../Makefile_obj:287: ../../bin/verilator_coverage_bin_dbg] Error 1
152 make[2]: Leaving directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src/obj_dbg'
153 make[1]: *** [Makefile:70: ../bin/verilator_coverage_bin_dbg] Error 2
154 make[1]: *** Waiting for unfinished jobs....
155 /usr/bin/ld: Verilator.o: unable to initialize decompress status for section .debug_info
156 /usr/bin/ld: Verilator.o: unable to initialize decompress status for section .debug_info
157 /usr/bin/ld: Verilator.o: unable to initialize decompress status for section .debug_info
158 /usr/bin/ld: Verilator.o: unable to initialize decompress status for section .debug_info
159 Verilator.o: file not recognized: File format not recognized
>> 160 collect2: error: ld returned 1 exit status
>> 161 make[2]: *** [../Makefile_obj:287: ../../bin/verilator_bin_dbg] Error 1
162 make[2]: Leaving directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src/obj_dbg'
163 make[1]: *** [Makefile:66: ../bin/verilator_bin_dbg] Error 2
164 make[1]: Leaving directory '/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-src/src'
165 make: *** [Makefile:233: verilator_exe] Error 2
See build log for details:
/tmp/root/spack-stage/spack-stage-verilator-4.210-u6zs26mdvynhr427nts6kbalrbilqyzt/spack-build-out.txt
==> Error: Terminating after first install failure: ProcessError: Command exited with status 2:
'make' '-j8'
```
Can you help me analyze it?
### Information on your system
[root@centos8 ~]# spack debug report
* **Spack:** 0.16.1-1624-a0b5dcca3c
* **Python:** 3.6.8
* **Platform:** linux-centos8-aarch64
* **Concretizer:** original
",1,when i make verilator and it failed in spack when i make verilator and it failed in spack console spack install y v keep stage dont restage no checksum fail fast verilator home spack spack opt spack linux gcc libiconv home spack spack opt spack linux gcc pkgconf home spack spack opt spack linux gcc xz home spack spack opt spack linux gcc zlib home spack spack opt spack linux gcc berkeley db home spack spack opt spack linux gcc libsigsegv home spack spack opt spack linux gcc diffutils home spack spack opt spack linux gcc tar home spack spack opt spack linux gcc ncurses home spack spack opt spack linux gcc home spack spack opt spack linux gcc home spack spack opt spack linux gcc home spack spack opt spack linux gcc readline home spack spack opt spack linux gcc libtool home spack spack opt spack linux gcc gettext home spack spack opt spack linux gcc gdbm home spack spack opt spack linux gcc perl home spack spack opt spack linux gcc home spack spack opt spack linux gcc autoconf home spack spack opt spack linux gcc texinfo home spack spack opt spack linux gcc bison home spack spack opt spack linux gcc automake home spack spack opt spack linux gcc findutils home spack spack opt spack linux gcc flex installing verilator no binary for verilator found installing from source using cached archive home spack spack var spack cache source cache archive tgz no patches needed for verilator verilator executing phase autoreconf verilator executing phase configure tmp root spack stage spack stage verilator spack src configure prefix home spack spack opt spack linux gcc verilator configuring for verilator checking whether to perform partial static linking of verilator binary yes checking whether to use tcmalloc check checking whether to use no checking whether to build for coverage collection no checking whether to use hardcoded paths yes checking whether to show and stop on compilation warnings no checking whether to run long tests no checking for gcc home spack spack lib spack env gcc gcc checking whether the c compiler works yes checking for c compiler default output file name a out checking for suffix of executables checking whether we are cross compiling no checking for suffix of object files o checking whether we are using the gnu c compiler yes checking whether home spack spack lib spack env gcc gcc accepts g yes checking for home spack spack lib spack env gcc gcc option to accept iso none needed checking whether we are using the gnu c compiler yes checking whether home spack spack lib spack env gcc g accepts g yes checking for a bsd compatible install usr bin install c compiler is home spack spack lib spack env gcc g version g gcc red hat checking that c compiler can compile simple program yes checking for ar ar checking for perl home spack spack opt spack linux gcc perl bin perl checking for usr bin checking for flex home spack spack opt spack linux gcc flex bin flex home spack spack opt spack linux gcc flex bin flex version flex checking for bison home spack spack opt spack linux gcc bison bin bison home spack spack opt spack linux gcc bison bin bison version bison gnu bison checking for ccache no checking how to run the c preprocessor home spack spack lib spack env gcc g e checking for grep that handles long lines and e usr bin grep checking for egrep usr bin grep e checking for ansi c header files yes checking for sys types h yes checking for sys stat h yes checking for stdlib h yes checking for string h yes checking for memory h yes checking for strings h yes checking for inttypes h yes checking for stdint h yes checking for unistd h yes checking for size t yes checking for size t cached yes checking for inline inline checking whether home spack spack lib spack env gcc g accepts pg yes checking whether home spack spack lib spack env gcc g accepts std gnu yes checking whether home spack spack lib spack env gcc g accepts std c yes checking whether home spack spack lib spack env gcc g accepts wextra yes checking whether home spack spack lib spack env gcc g accepts wfloat conversion yes checking whether home spack spack lib spack env gcc g accepts wlogical op yes checking whether home spack spack lib spack env gcc g accepts wthread safety no checking whether home spack spack lib spack env gcc g accepts qunused arguments no checking whether home spack spack lib spack env gcc g accepts faligned new yes checking whether home spack spack lib spack env gcc g accepts wno unused parameter yes checking whether home spack spack lib spack env gcc g accepts wno shadow yes checking whether home spack spack lib spack env gcc g accepts wno char subscripts yes checking whether home spack spack lib spack env gcc g accepts wno null conversion no checking whether home spack spack lib spack env gcc g accepts wno parentheses equality no checking whether home spack spack lib spack env gcc g accepts wno unused yes checking whether home spack spack lib spack env gcc g accepts og yes checking whether home spack spack lib spack env gcc g accepts ggdb yes checking whether home spack spack lib spack env gcc g accepts gz yes checking whether home spack spack lib spack env gcc g linker accepts gz yes checking whether home spack spack lib spack env gcc g accepts faligned new yes checking whether home spack spack lib spack env gcc g accepts fbracket depth no checking whether home spack spack lib spack env gcc g accepts fcf protection none yes checking whether home spack spack lib spack env gcc g accepts mno cet no checking whether home spack spack lib spack env gcc g accepts qunused arguments no checking whether home spack spack lib spack env gcc g accepts wno bool operation yes checking whether home spack spack lib spack env gcc g accepts wno tautological bitwise compare no checking whether home spack spack lib spack env gcc g accepts wno parentheses equality no checking whether home spack spack lib spack env gcc g accepts wno sign compare yes checking whether home spack spack lib spack env gcc g accepts wno uninitialized yes checking whether home spack spack lib spack env gcc g accepts wno unused but set variable yes checking whether home spack spack lib spack env gcc g accepts wno unused parameter yes checking whether home spack spack lib spack env gcc g accepts wno unused variable yes checking whether home spack spack lib spack env gcc g accepts wno shadow yes checking whether home spack spack lib spack env gcc g linker accepts mt no checking whether home spack spack lib spack env gcc g linker accepts pthread yes checking whether home spack spack lib spack env gcc g linker accepts lpthread yes checking whether home spack spack lib spack env gcc g linker accepts latomic yes checking whether home spack spack lib spack env gcc g linker accepts static libgcc yes checking whether home spack spack lib spack env gcc g linker accepts static libstdc no checking whether home spack spack lib spack env gcc g linker accepts xlinker gc sections yes checking whether home spack spack lib spack env gcc g linker accepts lpthread yes checking whether home spack spack lib spack env gcc g linker accepts lbcrypt no checking whether home spack spack lib spack env gcc g linker accepts lpsapi no checking whether home spack spack lib spack env gcc g linker accepts l libtcmalloc minimal a no checking whether home spack spack lib spack env gcc g supports c yes checking for struct stat st mtim tv nsec yes checking whether systemc is found in system path no configure creating config status config status creating makefile config status creating src makefile config status creating src makefile obj config status creating include verilated mk config status creating include verilated config h config status creating verilator pc config status creating verilator config cmake config status creating verilator config version cmake config status creating src config build h config status src config build h is unchanged now type make or sometimes gmake to build verilator verilator executing phase build make making verilator in src make c src make entering directory tmp root spack stage spack stage verilator spack src src make c obj dbg j tgt bin verilator bin dbg vl debug f makefile obj serial make c obj dbg tgt bin verilator coverage bin dbg vl debug vl vlcov f makefile obj serial vlcov make c obj opt j tgt bin verilator bin f makefile obj serial make entering directory tmp root spack stage spack stage verilator spack src src make warning jn forced in submake disabling jobserver mode make entering directory tmp root spack stage spack stage verilator spack src src make warning jn forced in submake disabling jobserver mode make nothing to be done for serial make leaving directory tmp root spack stage spack stage verilator spack src src obj dbg make c obj dbg tgt bin verilator bin dbg vl debug f makefile obj make entering directory tmp root spack stage spack stage verilator spack src src obj dbg make nothing to be done for serial vlcov make leaving directory tmp root spack stage spack stage verilator spack src src obj dbg make c obj dbg tgt bin verilator coverage bin dbg vl debug vl vlcov f makefile obj make nothing to be done for serial make leaving directory tmp root spack stage spack stage verilator spack src src obj opt make c obj opt tgt bin verilator bin f makefile obj make entering directory tmp root spack stage spack stage verilator spack src src obj dbg make entering directory tmp root spack stage spack stage verilator spack src src obj dbg make entering directory tmp root spack stage spack stage verilator spack src src obj opt compile flags home spack spack lib spack env gcc g og ggdb gz dvl debug d glibcxx debug mmd i i i i include i include mp faligned new wno unused parameter wno shadow ddefenv systemc ddefenv systemc arch ddefenv systemc include ddefenv systemc libdir ddefenv verilator root home spack spack opt spack linux gcc verilator share verilator compile flags home spack spack lib spack env gcc g og ggdb gz dvl debug d glibcxx debug mmd i i i i include i include mp faligned new wno unused parameter wno shadow ddefenv systemc ddefenv systemc arch ddefenv systemc include ddefenv systemc libdir ddefenv verilator root home spack spack opt spack linux gcc verilator share verilator compile flags home spack spack lib spack env gcc g mmd i i i i include i include mp faligned new wno unused parameter wno shadow ddefenv systemc ddefenv systemc arch ddefenv systemc include ddefenv systemc libdir ddefenv verilator root home spack spack opt spack linux gcc verilator share verilator linking bin verilator coverage bin dbg home spack spack lib spack env gcc g gz static libgcc xlinker gc sections o bin verilator coverage bin dbg vlcmain o lpthread lm make leaving directory tmp root spack stage spack stage verilator spack src src obj opt linking bin verilator bin dbg home spack spack lib spack env gcc g gz static libgcc xlinker gc sections o bin verilator bin dbg verilator o o o o o o o o o o o o o o o o o o o o o gen o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o lpthread lm usr bin ld vlcmain o unable to initialize decompress status for section debug info usr bin ld vlcmain o unable to initialize decompress status for section debug info usr bin ld vlcmain o unable to initialize decompress status for section debug info usr bin ld vlcmain o unable to initialize decompress status for section debug info vlcmain o file not recognized file format not recognized error ld returned exit status make error make leaving directory tmp root spack stage spack stage verilator spack src src obj dbg make error make waiting for unfinished jobs usr bin ld verilator o unable to initialize decompress status for section debug info usr bin ld verilator o unable to initialize decompress status for section debug info usr bin ld verilator o unable to initialize decompress status for section debug info usr bin ld verilator o unable to initialize decompress status for section debug info verilator o file not recognized file format not recognized error ld returned exit status make error make leaving directory tmp root spack stage spack stage verilator spack src src obj dbg make error make leaving directory tmp root spack stage spack stage verilator spack src src make error error processerror command exited with status make errors found in build log home spack spack lib spack env gcc g gz static libgcc xlinker gc sections o bin verilator bin dbg verilator o o o o o o es o o o o o o o o o o o o o o o gen o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o kparse o o o o o o o o o o o o o o o e o o o o o o o o o o o o o o o o o sp o o o o o o o o o o o lpthread lm usr bin ld vlcmain o unable to initialize decompress status for section debug info usr bin ld vlcmain o unable to initialize decompress status for section debug info usr bin ld vlcmain o unable to initialize decompress status for section debug info usr bin ld vlcmain o unable to initialize decompress status for section debug info vlcmain o file not recognized file format not recognized error ld returned exit status make error make leaving directory tmp root spack stage spack stage verilator spack src src obj dbg make error make waiting for unfinished jobs usr bin ld verilator o unable to initialize decompress status for section debug info usr bin ld verilator o unable to initialize decompress status for section debug info usr bin ld verilator o unable to initialize decompress status for section debug info usr bin ld verilator o unable to initialize decompress status for section debug info verilator o file not recognized file format not recognized error ld returned exit status make error make leaving directory tmp root spack stage spack stage verilator spack src src obj dbg make error make leaving directory tmp root spack stage spack stage verilator spack src src make error see build log for details tmp root spack stage spack stage verilator spack build out txt error terminating after first install failure processerror command exited with status make can you help me analyze it information on your system spack debug report spack python platform linux concretizer original ,1
1862,27576668123.0,IssuesEvent,2023-03-08 13:31:32,elastic/kibana,https://api.github.com/repos/elastic/kibana,closed,[Guided onboarding] A11y improvements ,enhancement Supportability Team:Journey/Onboarding,We need to review the a11y of the guided onboarding panel and try to fix any issues. [Here](https://eui.elastic.co/pr_6247/#/utilities/portal#a-custom-flyout) is an example of an accessible custom flyout. Also see https://github.com/elastic/eui/pull/6247 ,True,[Guided onboarding] A11y improvements - We need to review the a11y of the guided onboarding panel and try to fix any issues. [Here](https://eui.elastic.co/pr_6247/#/utilities/portal#a-custom-flyout) is an example of an accessible custom flyout. Also see https://github.com/elastic/eui/pull/6247 ,1, improvements we need to review the of the guided onboarding panel and try to fix any issues is an example of an accessible custom flyout also see ,1
1354,19403352884.0,IssuesEvent,2021-12-19 15:26:53,codenjoyme/codenjoy,https://api.github.com/repos/codenjoyme/codenjoy,closed,[windows][portable] Used clients approach to build server,p-clients p-windows-portable,"Старый скрипт стоит переписать, так же как это сейчас делается для всех клиентов",True,"[windows][portable] Used clients approach to build server - Старый скрипт стоит переписать, так же как это сейчас делается для всех клиентов",1, used clients approach to build server старый скрипт стоит переписать так же как это сейчас делается для всех клиентов,1
34020,7779775834.0,IssuesEvent,2018-06-05 17:53:53,volution/vonuvoli-scheme,https://api.github.com/repos/volution/vonuvoli-scheme,opened,Parser -- enhance error reporting of parsing errors,code-parser implementation,"## Tasks
* [ ] add line-numbers in transcript output;
* [ ] highlight line in transcript output;
* [ ] show only a few lines of the source code in the transcript output;
",1.0,"Parser -- enhance error reporting of parsing errors - ## Tasks
* [ ] add line-numbers in transcript output;
* [ ] highlight line in transcript output;
* [ ] show only a few lines of the source code in the transcript output;
",0,parser enhance error reporting of parsing errors tasks add line numbers in transcript output highlight line in transcript output show only a few lines of the source code in the transcript output ,0
233257,18957552565.0,IssuesEvent,2021-11-18 22:20:01,microsoft/vscode-python,https://api.github.com/repos/microsoft/vscode-python,closed,Prompt asking if you want to install pytest/nose is displayed even though the framework is already being installed,feature-request needs PR area-testing,"We should wait for the user to click on ""Yes"" to actually install the selected framework (after running Configure, Run or Discover Tests command)
",1.0,"Prompt asking if you want to install pytest/nose is displayed even though the framework is already being installed - We should wait for the user to click on ""Yes"" to actually install the selected framework (after running Configure, Run or Discover Tests command)
",0,prompt asking if you want to install pytest nose is displayed even though the framework is already being installed we should wait for the user to click on yes to actually install the selected framework after running configure run or discover tests command ,0
49535,6032102868.0,IssuesEvent,2017-06-09 02:08:25,ampproject/amphtml,https://api.github.com/repos/ampproject/amphtml,closed,CSS Keyframe test flake,P1: High Priority Related to: Flaky Tests,"```
Chrome 59.0.3071 (Linux 0.0.0) extractKeyframes discovery should scan in media CSS FAILED
AssertionError: expected JSON to be equal.
Exp: '[{""offset"":0,""opacity"":""0""},{""offset"":1,""opacity"":""0.2""}]'
Act: '[{""offset"":0,""opacity"":""0""},{""offset"":1,""opacity"":""0.1""}]'
at /home/travis/build/ampproject/amphtml/extensions/amp-animation/0.1/test/test-keyframes-extractor.js:183:29 <- /tmp/0d247d577d808d33bae951fe28e04ea8.browserify:57424:30
at
```",1.0,"CSS Keyframe test flake - ```
Chrome 59.0.3071 (Linux 0.0.0) extractKeyframes discovery should scan in media CSS FAILED
AssertionError: expected JSON to be equal.
Exp: '[{""offset"":0,""opacity"":""0""},{""offset"":1,""opacity"":""0.2""}]'
Act: '[{""offset"":0,""opacity"":""0""},{""offset"":1,""opacity"":""0.1""}]'
at /home/travis/build/ampproject/amphtml/extensions/amp-animation/0.1/test/test-keyframes-extractor.js:183:29 <- /tmp/0d247d577d808d33bae951fe28e04ea8.browserify:57424:30
at
```",0,css keyframe test flake chrome linux extractkeyframes discovery should scan in media css failed assertionerror expected json to be equal exp act at home travis build ampproject amphtml extensions amp animation test test keyframes extractor js tmp browserify at ,0
22029,11660555649.0,IssuesEvent,2020-03-03 03:44:53,cityofaustin/atd-data-tech,https://api.github.com/repos/cityofaustin/atd-data-tech,opened,Find someone in law dept regarding legal aspects of crashes,Product: Vision Zero Crash Data System Project: Vision Zero Crash Data System Service: PM Type: Meeting Type: Research Workgroup: CTM Workgroup: VZ migrated,"what data (public or not) that might be available regarding scooter crashes.
insurance?
court filings?
- https://www.citylab.com/transportation/2019/01/scooter-crash-accidents-safety-liability-bird-lime/577687/
*Migrated from [atd-vz-data #5](https://github.com/cityofaustin/atd-vz-data/issues/5)*",1.0,"Find someone in law dept regarding legal aspects of crashes - what data (public or not) that might be available regarding scooter crashes.
insurance?
court filings?
- https://www.citylab.com/transportation/2019/01/scooter-crash-accidents-safety-liability-bird-lime/577687/
*Migrated from [atd-vz-data #5](https://github.com/cityofaustin/atd-vz-data/issues/5)*",0,find someone in law dept regarding legal aspects of crashes what data public or not that might be available regarding scooter crashes insurance court filings migrated from ,0
142250,11460227424.0,IssuesEvent,2020-02-07 09:18:25,bogdanpolak/command-delphi,https://api.github.com/repos/bogdanpolak/command-delphi,opened,PoC - Build test suite for TAsyncCommand,unit tests,"Build prototype test suite for TAsyncCommand. Problems:
- New to wait until thread will finish
- Move fThread into protected if it will be required ",1.0,"PoC - Build test suite for TAsyncCommand - Build prototype test suite for TAsyncCommand. Problems:
- New to wait until thread will finish
- Move fThread into protected if it will be required ",0,poc build test suite for tasynccommand build prototype test suite for tasynccommand problems new to wait until thread will finish move fthread into protected if it will be required ,0
1412,20986824926.0,IssuesEvent,2022-03-29 04:43:44,MicrosoftDocs/azure-docs,https://api.github.com/repos/MicrosoftDocs/azure-docs,closed,https://github.com/MicrosoftDocs/azure-docs/issues/81994 NOT IMPLEMENTED,azure-supportability/svc triaged cxp doc-enhancement Pri2,"Can you please add a feedback stating that there is no cost associated with increasing quota only cost associated with utilizing the same. I have been getting a lot of partner requests stating if there is a price associated with quota increase. A one liner should provide clarification on the same
I created a previous issue # https://github.com/MicrosoftDocs/azure-docs/issues/81994 which stated that this will be addressed but I dont see the statement. Can we please add this to the document to reduce the churn
[Enter feedback here]
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: e19f68c5-3917-c131-a379-3b9e3156593b
* Version Independent ID: 89f78479-edd5-f96c-b342-31e43ef72c92
* Content: [Increase regional vCPU quotas - Azure supportability](https://docs.microsoft.com/en-us/azure/azure-portal/supportability/regional-quota-requests#request-a-quota-increase-by-region-from-subscriptions)
* Content Source: [articles/azure-portal/supportability/regional-quota-requests.md](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-portal/supportability/regional-quota-requests.md)
* Service: **azure-supportability**
* GitHub Login: @JnHs
* Microsoft Alias: **jenhayes**",True,"https://github.com/MicrosoftDocs/azure-docs/issues/81994 NOT IMPLEMENTED - Can you please add a feedback stating that there is no cost associated with increasing quota only cost associated with utilizing the same. I have been getting a lot of partner requests stating if there is a price associated with quota increase. A one liner should provide clarification on the same
I created a previous issue # https://github.com/MicrosoftDocs/azure-docs/issues/81994 which stated that this will be addressed but I dont see the statement. Can we please add this to the document to reduce the churn
[Enter feedback here]
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: e19f68c5-3917-c131-a379-3b9e3156593b
* Version Independent ID: 89f78479-edd5-f96c-b342-31e43ef72c92
* Content: [Increase regional vCPU quotas - Azure supportability](https://docs.microsoft.com/en-us/azure/azure-portal/supportability/regional-quota-requests#request-a-quota-increase-by-region-from-subscriptions)
* Content Source: [articles/azure-portal/supportability/regional-quota-requests.md](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-portal/supportability/regional-quota-requests.md)
* Service: **azure-supportability**
* GitHub Login: @JnHs
* Microsoft Alias: **jenhayes**",1, not implemented can you please add a feedback stating that there is no cost associated with increasing quota only cost associated with utilizing the same i have been getting a lot of partner requests stating if there is a price associated with quota increase a one liner should provide clarification on the same i created a previous issue which stated that this will be addressed but i dont see the statement can we please add this to the document to reduce the churn document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source service azure supportability github login jnhs microsoft alias jenhayes ,1
131092,18214669904.0,IssuesEvent,2021-09-30 01:40:55,mgh3326/google-calendar-slackbot,https://api.github.com/repos/mgh3326/google-calendar-slackbot,opened,CVE-2021-37136 (High) detected in netty-codec-4.1.50.Final.jar,security vulnerability,"## CVE-2021-37136 - High Severity Vulnerability
Vulnerable Library - netty-codec-4.1.50.Final.jar
Netty is an asynchronous event-driven network application framework for
rapid development of maintainable high performance protocol servers and
clients.
Path to dependency file: google-calendar-slackbot/build.gradle
Path to vulnerable library: /root/.gradle/caches/modules-2/files-2.1/io.netty/netty-codec/4.1.50.Final/cbcb646c9380c6cdc3f56603ae6418a11418ce0f/netty-codec-4.1.50.Final.jar,/root/.gradle/caches/modules-2/files-2.1/io.netty/netty-codec/4.1.50.Final/cbcb646c9380c6cdc3f56603ae6418a11418ce0f/netty-codec-4.1.50.Final.jar
Dependency Hierarchy:
- spring-boot-devtools-2.3.1.RELEASE (Root Library)
- spring-boot-dependencies-2.3.1.RELEASE
- :x: **netty-codec-4.1.50.Final.jar** (Vulnerable Library)
Vulnerability Details
The Bzip2 decompression decoder function doesn't allow setting size restrictions on the decompressed output data (which affects the allocation size used during decompression).
All users of Bzip2Decoder are affected. The malicious input can trigger an OOME and so a DoS attack
Publish Date: 2021-07-21
URL: CVE-2021-37136
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://github.com/advisories/GHSA-grg4-wf29-r9vv
Release Date: 2021-07-21
Fix Resolution: io.netty:netty-codec:4.1.68.Final
Vulnerable Library - netty-codec-4.1.50.Final.jar
Netty is an asynchronous event-driven network application framework for
rapid development of maintainable high performance protocol servers and
clients.
Path to dependency file: google-calendar-slackbot/build.gradle
Path to vulnerable library: /root/.gradle/caches/modules-2/files-2.1/io.netty/netty-codec/4.1.50.Final/cbcb646c9380c6cdc3f56603ae6418a11418ce0f/netty-codec-4.1.50.Final.jar,/root/.gradle/caches/modules-2/files-2.1/io.netty/netty-codec/4.1.50.Final/cbcb646c9380c6cdc3f56603ae6418a11418ce0f/netty-codec-4.1.50.Final.jar
Dependency Hierarchy:
- spring-boot-devtools-2.3.1.RELEASE (Root Library)
- spring-boot-dependencies-2.3.1.RELEASE
- :x: **netty-codec-4.1.50.Final.jar** (Vulnerable Library)
Vulnerability Details
The Bzip2 decompression decoder function doesn't allow setting size restrictions on the decompressed output data (which affects the allocation size used during decompression).
All users of Bzip2Decoder are affected. The malicious input can trigger an OOME and so a DoS attack
Publish Date: 2021-07-21
URL: CVE-2021-37136
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://github.com/advisories/GHSA-grg4-wf29-r9vv
Release Date: 2021-07-21
Fix Resolution: io.netty:netty-codec:4.1.68.Final
Error message
>> 13388 /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: /path/to/cache/build_stage/spack-stage-esmf-8.3.0b09-jmblchtb6cpbt4ot6f22x45qwyrju334/spack-src/src/Infrastr
ucture/IO/PIO/piodarray.F90.in:162: undefined reference to `mpi_bcast_'
>> 13389 /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: /path/to/cache/build_stage/spack-stage-esmf-8.3.0b09-jmblchtb6cpbt4ot6f22x45qwyrju334/spack-src/src/Infrastr
ucture/IO/PIO/piodarray.F90.in:163: undefined reference to `mpi_bcast_'
>> 13390 /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: /path/to/cache/build_stage/spack-stage-esmf-8.3.0b09-jmblchtb6cpbt4ot6f22x45qwyrju334/spack-src/src/Infrastr
ucture/IO/PIO/piodarray.F90.in:164: undefined reference to `mpi_bcast_'
>> 13391 /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: /path/to/cache/build_stage/spack-stage-esmf-8.3.0b09-jmblchtb6cpbt4ot6f22x45qwyrju334/spack-src/src/Infrastr
ucture/IO/PIO/piodarray.F90.in:165: undefined reference to `mpi_bcast_'
Error message
>> 13388 /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: /path/to/cache/build_stage/spack-stage-esmf-8.3.0b09-jmblchtb6cpbt4ot6f22x45qwyrju334/spack-src/src/Infrastr
ucture/IO/PIO/piodarray.F90.in:162: undefined reference to `mpi_bcast_'
>> 13389 /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: /path/to/cache/build_stage/spack-stage-esmf-8.3.0b09-jmblchtb6cpbt4ot6f22x45qwyrju334/spack-src/src/Infrastr
ucture/IO/PIO/piodarray.F90.in:163: undefined reference to `mpi_bcast_'
>> 13390 /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: /path/to/cache/build_stage/spack-stage-esmf-8.3.0b09-jmblchtb6cpbt4ot6f22x45qwyrju334/spack-src/src/Infrastr
ucture/IO/PIO/piodarray.F90.in:164: undefined reference to `mpi_bcast_'
>> 13391 /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: /path/to/cache/build_stage/spack-stage-esmf-8.3.0b09-jmblchtb6cpbt4ot6f22x45qwyrju334/spack-src/src/Infrastr
ucture/IO/PIO/piodarray.F90.in:165: undefined reference to `mpi_bcast_'
Test output
2023/01/30 16:29:08 SIGINT signal received. Shutting down...
2023/01/30 16:29:08 The proxy has encountered a terminal error: unable to start: [proj.region.clust.inst] Unable to mount socket:
root_test.go:936: failed to dial endpoint: Get ""http://localhost:9191/debug/pprof/"": dial tcp [::1]:9191: connectex: No connection could be made because the target machine actively refused it.
Test output
2023/01/30 16:29:08 SIGINT signal received. Shutting down...
2023/01/30 16:29:08 The proxy has encountered a terminal error: unable to start: [proj.region.clust.inst] Unable to mount socket:
root_test.go:936: failed to dial endpoint: Get ""http://localhost:9191/debug/pprof/"": dial tcp [::1]:9191: connectex: No connection could be made because the target machine actively refused it.
Vulnerable Libraries - js-yaml-3.7.0.tgz, js-yaml-3.12.1.tgz
js-yaml-3.7.0.tgz
YAML 1.2 parser and serializer
Library home page: https://registry.npmjs.org/js-yaml/-/js-yaml-3.7.0.tgz
Path to dependency file: /tmp/ws-scm/atlsecsrv-net-a-atlsecsrv.com/package.json
Path to vulnerable library: /tmp/ws-scm/atlsecsrv-net-a-atlsecsrv.com/node_modules/js-yaml
Dependency Hierarchy:
- gulp-cssnano-2.1.3.tgz (Root Library)
- cssnano-3.10.0.tgz
- postcss-svgo-2.1.6.tgz
- svgo-0.7.2.tgz
- :x: **js-yaml-3.7.0.tgz** (Vulnerable Library)
js-yaml-3.12.1.tgz
YAML 1.2 parser and serializer
Library home page: https://registry.npmjs.org/js-yaml/-/js-yaml-3.12.1.tgz
Path to dependency file: /tmp/ws-scm/atlsecsrv-net-a-atlsecsrv.com/package.json
Path to vulnerable library: /tmp/ws-scm/atlsecsrv-net-a-atlsecsrv.com/node_modules/js-yaml
Dependency Hierarchy:
- gulp-eslint-5.0.0.tgz (Root Library)
- eslint-5.13.0.tgz
- :x: **js-yaml-3.12.1.tgz** (Vulnerable Library)
Found in HEAD commit: a1479f17f72992a58ef6c45317028a2b0f60a97a
Found in base branch: master
Vulnerability Details
Js-yaml prior to 3.13.1 are vulnerable to Code Injection. The load() function may execute arbitrary code injected through a malicious YAML file.
Publish Date: 2019-04-05
URL: WS-2019-0063
CVSS 3 Score Details (8.1)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://www.npmjs.com/advisories/813
Release Date: 2019-04-05
Fix Resolution: js-yaml - 3.13.1
Vulnerable Libraries - js-yaml-3.7.0.tgz, js-yaml-3.12.1.tgz
js-yaml-3.7.0.tgz
YAML 1.2 parser and serializer
Library home page: https://registry.npmjs.org/js-yaml/-/js-yaml-3.7.0.tgz
Path to dependency file: /tmp/ws-scm/atlsecsrv-net-a-atlsecsrv.com/package.json
Path to vulnerable library: /tmp/ws-scm/atlsecsrv-net-a-atlsecsrv.com/node_modules/js-yaml
Dependency Hierarchy:
- gulp-cssnano-2.1.3.tgz (Root Library)
- cssnano-3.10.0.tgz
- postcss-svgo-2.1.6.tgz
- svgo-0.7.2.tgz
- :x: **js-yaml-3.7.0.tgz** (Vulnerable Library)
js-yaml-3.12.1.tgz
YAML 1.2 parser and serializer
Library home page: https://registry.npmjs.org/js-yaml/-/js-yaml-3.12.1.tgz
Path to dependency file: /tmp/ws-scm/atlsecsrv-net-a-atlsecsrv.com/package.json
Path to vulnerable library: /tmp/ws-scm/atlsecsrv-net-a-atlsecsrv.com/node_modules/js-yaml
Dependency Hierarchy:
- gulp-eslint-5.0.0.tgz (Root Library)
- eslint-5.13.0.tgz
- :x: **js-yaml-3.12.1.tgz** (Vulnerable Library)
Found in HEAD commit: a1479f17f72992a58ef6c45317028a2b0f60a97a
Found in base branch: master
Vulnerability Details
Js-yaml prior to 3.13.1 are vulnerable to Code Injection. The load() function may execute arbitrary code injected through a malicious YAML file.
Publish Date: 2019-04-05
URL: WS-2019-0063
CVSS 3 Score Details (8.1)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://www.npmjs.com/advisories/813
Release Date: 2019-04-05
Fix Resolution: js-yaml - 3.13.1
Vulnerable Library - linux-stable-rtv3.8.6
Julia Cartwright's fork of linux-stable-rt.git
Library home page: https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git
Found in HEAD commit: 594a70cb9871ddd73cf61197bb1a2a1b1777a7ae
Found in base branch: master
Vulnerable Source Files (1)
/net/ipv4/udp.c
Vulnerability Details
The (1) udp_recvmsg and (2) udpv6_recvmsg functions in the Linux kernel before 4.0.6 provide inappropriate -EAGAIN return values, which allows remote attackers to cause a denial of service (EPOLLET epoll application read outage) via an incorrect checksum in a UDP packet, a different vulnerability than CVE-2015-5364.
Publish Date: 2015-08-31
URL: CVE-2015-5366
CVSS 3 Score Details (5.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: N/A
- Attack Complexity: N/A
- Privileges Required: N/A
- User Interaction: N/A
- Scope: N/A
- Impact Metrics:
- Confidentiality Impact: N/A
- Integrity Impact: N/A
- Availability Impact: N/A
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://www.linuxkernelcves.com/cves/CVE-2015-5366
Release Date: 2015-08-31
Fix Resolution: v4.1-rc7,v3.12.44,v3.14.45,v3.16.35,v3.18.17,v3.2.70
Vulnerable Library - linux-stable-rtv3.8.6
Julia Cartwright's fork of linux-stable-rt.git
Library home page: https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git
Found in HEAD commit: 594a70cb9871ddd73cf61197bb1a2a1b1777a7ae
Found in base branch: master
Vulnerable Source Files (1)
/net/ipv4/udp.c
Vulnerability Details
The (1) udp_recvmsg and (2) udpv6_recvmsg functions in the Linux kernel before 4.0.6 provide inappropriate -EAGAIN return values, which allows remote attackers to cause a denial of service (EPOLLET epoll application read outage) via an incorrect checksum in a UDP packet, a different vulnerability than CVE-2015-5364.
Publish Date: 2015-08-31
URL: CVE-2015-5366
CVSS 3 Score Details (5.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: N/A
- Attack Complexity: N/A
- Privileges Required: N/A
- User Interaction: N/A
- Scope: N/A
- Impact Metrics:
- Confidentiality Impact: N/A
- Integrity Impact: N/A
- Availability Impact: N/A
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://www.linuxkernelcves.com/cves/CVE-2015-5366
Release Date: 2015-08-31
Fix Resolution: v4.1-rc7,v3.12.44,v3.14.45,v3.16.35,v3.18.17,v3.2.70
Vulnerable Libraries - node-sass-4.13.1.tgz
node-sass-4.13.1.tgz
Wrapper around libsass
Library home page: https://registry.npmjs.org/node-sass/-/node-sass-4.13.1.tgz
Path to dependency file: /tmp/ws-scm/headless-wp-nuxt/package.json
Path to vulnerable library: /headless-wp-nuxt/node_modules/node-sass/package.json
Dependency Hierarchy:
- :x: **node-sass-4.13.1.tgz** (Vulnerable Library)
Found in HEAD commit: 748e38948b04db4c74d2e3dae8a217d0ecbc395c
Vulnerability Details
In LibSass 3.5.5, a heap-based buffer over-read exists in Sass::Prelexer::alternatives in prelexer.hpp.
Publish Date: 2019-01-14
URL: CVE-2019-6284
CVSS 3 Score Details (6.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6284
Release Date: 2019-08-06
Fix Resolution: LibSass - 3.6.0
Vulnerable Libraries - node-sass-4.13.1.tgz
node-sass-4.13.1.tgz
Wrapper around libsass
Library home page: https://registry.npmjs.org/node-sass/-/node-sass-4.13.1.tgz
Path to dependency file: /tmp/ws-scm/headless-wp-nuxt/package.json
Path to vulnerable library: /headless-wp-nuxt/node_modules/node-sass/package.json
Dependency Hierarchy:
- :x: **node-sass-4.13.1.tgz** (Vulnerable Library)
Found in HEAD commit: 748e38948b04db4c74d2e3dae8a217d0ecbc395c
Vulnerability Details
In LibSass 3.5.5, a heap-based buffer over-read exists in Sass::Prelexer::alternatives in prelexer.hpp.
Publish Date: 2019-01-14
URL: CVE-2019-6284
CVSS 3 Score Details (6.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6284
Release Date: 2019-08-06
Fix Resolution: LibSass - 3.6.0
Vulnerable Library - github.com/hashicorp/go-sockaddr-v1.0.2
IP Address/UNIX Socket convenience functions for Go
Dependency Hierarchy:
- github.com/xmidt-org/webpa-common/v2-v2.0.7-dev.1 (Root Library)
- github.com/hashicorp/consul/api-v1.13.1
- github.com/hashicorp/serf-v0.9.8
- github.com/hashicorp/memberlist-v0.3.0
- :x: **github.com/hashicorp/go-sockaddr-v1.0.2** (Vulnerable Library)
Found in HEAD commit: 5585120e6948118205d4650798b0373c28b1ec78
Found in base branch: main
Vulnerability Details
Go before 1.17.10 and 1.18.x before 1.18.2 has Incorrect Privilege Assignment. When called with a non-zero flags parameter, the Faccessat function could incorrectly report that a file is accessible.
Publish Date: 2022-06-23
URL: CVE-2022-29526
CVSS 3 Score Details (5.3)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://security-tracker.debian.org/tracker/CVE-2022-29526
Release Date: 2022-06-23
Fix Resolution: go1.17.10,go1.18.2,go1.19
Vulnerable Library - github.com/hashicorp/go-sockaddr-v1.0.2
IP Address/UNIX Socket convenience functions for Go
Dependency Hierarchy:
- github.com/xmidt-org/webpa-common/v2-v2.0.7-dev.1 (Root Library)
- github.com/hashicorp/consul/api-v1.13.1
- github.com/hashicorp/serf-v0.9.8
- github.com/hashicorp/memberlist-v0.3.0
- :x: **github.com/hashicorp/go-sockaddr-v1.0.2** (Vulnerable Library)
Found in HEAD commit: 5585120e6948118205d4650798b0373c28b1ec78
Found in base branch: main
Vulnerability Details
Go before 1.17.10 and 1.18.x before 1.18.2 has Incorrect Privilege Assignment. When called with a non-zero flags parameter, the Faccessat function could incorrectly report that a file is accessible.
Publish Date: 2022-06-23
URL: CVE-2022-29526
CVSS 3 Score Details (5.3)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://security-tracker.debian.org/tracker/CVE-2022-29526
Release Date: 2022-06-23
Fix Resolution: go1.17.10,go1.18.2,go1.19
Vulnerable Library - GitPython-2.1.5-py2.py3-none-any.whl
Python Git Library
Library home page: https://files.pythonhosted.org/packages/7e/13/2a556eb97dcf498c915e5e04bb82bf74e07bb8b7337ca2be49bfd9fb6313/GitPython-2.1.5-py2.py3-none-any.whl
Path to dependency file: /dev_requirements.txt
Path to vulnerable library: /dev_requirements.txt
Dependency Hierarchy:
- :x: **GitPython-2.1.5-py2.py3-none-any.whl** (Vulnerable Library)
Vulnerability Details
All versions of package gitpython are vulnerable to Remote Code Execution (RCE) due to improper user input validation, which makes it possible to inject a maliciously crafted remote URL into the clone command. Exploiting this vulnerability is possible because the library makes external calls to git without sufficient sanitization of input arguments.
Publish Date: 2022-12-06
URL: CVE-2022-24439
CVSS 3 Score Details (8.1)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Vulnerable Library - GitPython-2.1.5-py2.py3-none-any.whl
Python Git Library
Library home page: https://files.pythonhosted.org/packages/7e/13/2a556eb97dcf498c915e5e04bb82bf74e07bb8b7337ca2be49bfd9fb6313/GitPython-2.1.5-py2.py3-none-any.whl
Path to dependency file: /dev_requirements.txt
Path to vulnerable library: /dev_requirements.txt
Dependency Hierarchy:
- :x: **GitPython-2.1.5-py2.py3-none-any.whl** (Vulnerable Library)
Vulnerability Details
All versions of package gitpython are vulnerable to Remote Code Execution (RCE) due to improper user input validation, which makes it possible to inject a maliciously crafted remote URL into the clone command. Exploiting this vulnerability is possible because the library makes external calls to git without sufficient sanitization of input arguments.
Publish Date: 2022-12-06
URL: CVE-2022-24439
CVSS 3 Score Details (8.1)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Vulnerable Library - node-sass-4.13.0.tgz
Wrapper around libsass
Library home page: https://registry.npmjs.org/node-sass/-/node-sass-4.13.0.tgz
Path to dependency file: /tmp/ws-scm/todolist-frontend-igaku/package.json
Path to vulnerable library: /todolist-frontend-igaku/node_modules/node-sass/package.json
Dependency Hierarchy:
- :x: **node-sass-4.13.0.tgz** (Vulnerable Library)
Found in HEAD commit: b17e5f3a30530082b47eaec4f1bfc545245f9563
Vulnerability Details
In LibSass prior to 3.5.5, Sass::Eval::operator()(Sass::Binary_Expression*) inside eval.cpp allows attackers to cause a denial-of-service resulting from stack consumption via a crafted sass file, because of certain incorrect parsing of '%' as a modulo operator in parser.cpp.
Publish Date: 2018-12-04
URL: CVE-2018-19837
CVSS 3 Score Details (6.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19837
Fix Resolution: 3.5.5
Vulnerable Library - node-sass-4.13.0.tgz
Wrapper around libsass
Library home page: https://registry.npmjs.org/node-sass/-/node-sass-4.13.0.tgz
Path to dependency file: /tmp/ws-scm/todolist-frontend-igaku/package.json
Path to vulnerable library: /todolist-frontend-igaku/node_modules/node-sass/package.json
Dependency Hierarchy:
- :x: **node-sass-4.13.0.tgz** (Vulnerable Library)
Found in HEAD commit: b17e5f3a30530082b47eaec4f1bfc545245f9563
Vulnerability Details
In LibSass prior to 3.5.5, Sass::Eval::operator()(Sass::Binary_Expression*) inside eval.cpp allows attackers to cause a denial-of-service resulting from stack consumption via a crafted sass file, because of certain incorrect parsing of '%' as a modulo operator in parser.cpp.
Publish Date: 2018-12-04
URL: CVE-2018-19837
CVSS 3 Score Details (6.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19837
Fix Resolution: 3.5.5
Browser Configuration
_From [webcompat.com](https://webcompat.com/) with ❤️_",1.0,"www.amazon.fr - site is not usable -
**URL**: https://www.amazon.fr/ap/signin
**Browser / Version**: Firefox Mobile 75.0
**Operating System**: Android
**Tested Another Browser**: Yes
**Problem type**: Site is not usable
**Description**: Keeps saying incorrect password while it is correct
**Steps to Reproduce**:
Amazon shows incorrect password error, while the password is good. At the same time, I'm receiving an email with confirmation code. This is the same process as on desktop, except that on desktop I am presented with a prompt to input the confirmation code.
Browser Configuration
_From [webcompat.com](https://webcompat.com/) with ❤️_",0, site is not usable url browser version firefox mobile operating system android tested another browser yes problem type site is not usable description keeps saying incorrect password while it is correct steps to reproduce amazon shows incorrect password error while the password is good at the same time i m receiving an email with confirmation code this is the same process as on desktop except that on desktop i am presented with a prompt to input the confirmation code browser configuration none from with ❤️ ,0
785,10348824905.0,IssuesEvent,2019-09-04 20:45:11,Azure/azure-webjobs-sdk,https://api.github.com/repos/Azure/azure-webjobs-sdk,opened,Detect if the v2 ApplicationInsights Service for v2 has been replaced by customer dependency injection.,Supportability,"Customers are mistakenly overwriting the Application Insights dependency in Startup which results in missing data and dependencies not showing up in the Application Map.
This is referred to in the documentation here.
https://docs.microsoft.com/en-us/azure/azure-functions/functions-dotnet-dependency-injection#logging-services
and here
https://docs.microsoft.com/en-us/azure/azure-functions/functions-monitoring#version-2x-3
#### Repro steps
Provide the steps required to reproduce the problem
1. Create a New Functions Project
2. Add a Startup class.
3. Inject your own instance of TelemetryClient
serviceCollection.AddSingleton(sp =>
{
var configuration = TelemetryConfiguration.CreateDefault();
configuration.TelemetryProcessorChainBuilder.Use(next =>
{
var qpProcessor = new QuickPulseTelemetryProcessor(next);
qpProcessor.Initialize(configuration);
return qpProcessor;
});
#### Expected behavior
The runtime can log an error indicating that this may be missing and we can build a detector to share the above links with the customer.
#### Actual behavior
The Application Insights data and dependency tracking is affected and currently this needs a code review to detect and fix.
#### Known workarounds
No workarounds exist.
",True,"Detect if the v2 ApplicationInsights Service for v2 has been replaced by customer dependency injection. - Customers are mistakenly overwriting the Application Insights dependency in Startup which results in missing data and dependencies not showing up in the Application Map.
This is referred to in the documentation here.
https://docs.microsoft.com/en-us/azure/azure-functions/functions-dotnet-dependency-injection#logging-services
and here
https://docs.microsoft.com/en-us/azure/azure-functions/functions-monitoring#version-2x-3
#### Repro steps
Provide the steps required to reproduce the problem
1. Create a New Functions Project
2. Add a Startup class.
3. Inject your own instance of TelemetryClient
serviceCollection.AddSingleton(sp =>
{
var configuration = TelemetryConfiguration.CreateDefault();
configuration.TelemetryProcessorChainBuilder.Use(next =>
{
var qpProcessor = new QuickPulseTelemetryProcessor(next);
qpProcessor.Initialize(configuration);
return qpProcessor;
});
#### Expected behavior
The runtime can log an error indicating that this may be missing and we can build a detector to share the above links with the customer.
#### Actual behavior
The Application Insights data and dependency tracking is affected and currently this needs a code review to detect and fix.
#### Known workarounds
No workarounds exist.
",1,detect if the applicationinsights service for has been replaced by customer dependency injection customers are mistakenly overwriting the application insights dependency in startup which results in missing data and dependencies not showing up in the application map this is referred to in the documentation here and here repro steps provide the steps required to reproduce the problem create a new functions project add a startup class inject your own instance of telemetryclient servicecollection addsingleton sp var configuration telemetryconfiguration createdefault configuration telemetryprocessorchainbuilder use next var qpprocessor new quickpulsetelemetryprocessor next qpprocessor initialize configuration return qpprocessor expected behavior the runtime can log an error indicating that this may be missing and we can build a detector to share the above links with the customer actual behavior the application insights data and dependency tracking is affected and currently this needs a code review to detect and fix known workarounds no workarounds exist ,1
177645,14640675489.0,IssuesEvent,2020-12-25 03:11:14,BGround/Web-Front-End-Interview,https://api.github.com/repos/BGround/Web-Front-End-Interview,opened,ES6入门之let和const,ES6 documentation,"**let和var声明的是变量，const声明的是常量**
常量：只能取值不能赋值，就是只读不写
常量的声明：
```javascript
var es = 'ES6';
```
let和var的区别
① let不允许重复声明，var可以
```javascript
var str = 'es6';
var str = 'es2015';
console.log(str);
let es = 'es6';
let es = 'es2015';
console.log(es);
//Uncaught SyntaxError: Identifier 'es' has already been declared
```
② let不属于顶层对象window,var可以
```javascript
let str = 'es6';
console.log(window.str); //undefined
```
③ 不存在变量提升[5.JS的执行上下文](#JS的执行上下文)
```javascript
console.log(str);
let str = 'es2015';
//Uncaught ReferenceError: Cannot access 'str' before initialization
console.log(str); var str;
var str = 'es2015'; => console.log(str);
str = 'es6';
//结果是undefined，具体细节参照执行上下文分析
```
④ 暂时性死区,在代码块内，使用let命令声明变量之前，该变量都是不可用的
```javascript
if(true) {
console.log(str);
let str = 'es6';//Uncaught ReferenceError: Cannot access 'str' before initialization
}
```
因为暂时性死区, 所以要特别注意typeof的使用
【拓展】
var的创建和初始化被提升，赋值不会被提升。
let的创建被提升，初始化和赋值不会被提升。
function的创建、初始化和赋值均会被提升。
⑤ 块级作用域
```javascript
if(true) {
let str = 'es6';
}
console.log(str);
//Uncaught ReferenceError: str is not defined
```
###### let的特性const都有，不能重复声明、不存在变量提升、存在块级作用域也有暂时性死区，唯一的区别const声明常量，一旦声明无法修改。
###### 但是有一点特别注意，上面的列子中不能修改的都是基本数据类型，对于数组或者对象都是引用数据类型，引用数据类型可以修改的是存在堆内存中的数据
```javascript
const esObj = {
name: 'es6',
year: 2015
}
esObj.name = 'es2015';
console.log(esObj);
const arr = ['es6', 'es7', 'es8'];
arr[0] = 'es2015';
console.log(arr);
```
###### let定义的变量，只能在块作用域里访问，不能跨块作用域访问，也不能跨函数作用域访问,ES6新增的命令
###### var定义的变量，可以跨块作用域访问, 不能跨函数作用域访问,
###### const用来定义常量，创建时必须赋值，只能在块作用域里访问，并且不能修改引用数据类型的指向地址，但是可以修改引用数据指向地址内的数据。
",1.0,"ES6入门之let和const - **let和var声明的是变量，const声明的是常量**
常量：只能取值不能赋值，就是只读不写
常量的声明：
```javascript
var es = 'ES6';
```
let和var的区别
① let不允许重复声明，var可以
```javascript
var str = 'es6';
var str = 'es2015';
console.log(str);
let es = 'es6';
let es = 'es2015';
console.log(es);
//Uncaught SyntaxError: Identifier 'es' has already been declared
```
② let不属于顶层对象window,var可以
```javascript
let str = 'es6';
console.log(window.str); //undefined
```
③ 不存在变量提升[5.JS的执行上下文](#JS的执行上下文)
```javascript
console.log(str);
let str = 'es2015';
//Uncaught ReferenceError: Cannot access 'str' before initialization
console.log(str); var str;
var str = 'es2015'; => console.log(str);
str = 'es6';
//结果是undefined，具体细节参照执行上下文分析
```
④ 暂时性死区,在代码块内，使用let命令声明变量之前，该变量都是不可用的
```javascript
if(true) {
console.log(str);
let str = 'es6';//Uncaught ReferenceError: Cannot access 'str' before initialization
}
```
因为暂时性死区, 所以要特别注意typeof的使用
【拓展】
var的创建和初始化被提升，赋值不会被提升。
let的创建被提升，初始化和赋值不会被提升。
function的创建、初始化和赋值均会被提升。
⑤ 块级作用域
```javascript
if(true) {
let str = 'es6';
}
console.log(str);
//Uncaught ReferenceError: str is not defined
```
###### let的特性const都有，不能重复声明、不存在变量提升、存在块级作用域也有暂时性死区，唯一的区别const声明常量，一旦声明无法修改。
###### 但是有一点特别注意，上面的列子中不能修改的都是基本数据类型，对于数组或者对象都是引用数据类型，引用数据类型可以修改的是存在堆内存中的数据
```javascript
const esObj = {
name: 'es6',
year: 2015
}
esObj.name = 'es2015';
console.log(esObj);
const arr = ['es6', 'es7', 'es8'];
arr[0] = 'es2015';
console.log(arr);
```
###### let定义的变量，只能在块作用域里访问，不能跨块作用域访问，也不能跨函数作用域访问,ES6新增的命令
###### var定义的变量，可以跨块作用域访问, 不能跨函数作用域访问,
###### const用来定义常量，创建时必须赋值，只能在块作用域里访问，并且不能修改引用数据类型的指向地址，但是可以修改引用数据指向地址内的数据。
",0, let和var声明的是变量，const声明的是常量 常量：只能取值不能赋值，就是只读不写 常量的声明： javascript var es let和var的区别 ① let不允许重复声明，var可以 javascript var str var str console log str let es let es console log es uncaught syntaxerror identifier es has already been declared ② let不属于顶层对象window var可以 javascript let str console log window str undefined ③ 不存在变量提升 js的执行上下文 javascript console log str let str uncaught referenceerror cannot access str before initialization console log str var str var str console log str str 结果是undefined，具体细节参照执行上下文分析 ④ 暂时性死区 在代码块内，使用let命令声明变量之前，该变量都是不可用的 javascript if true console log str let str uncaught referenceerror cannot access str before initialization 因为暂时性死区 所以要特别注意typeof的使用 【拓展】 var的创建和初始化被提升，赋值不会被提升。 let的创建被提升，初始化和赋值不会被提升。 function的创建、初始化和赋值均会被提升。 ⑤ 块级作用域 javascript if true let str console log str uncaught referenceerror str is not defined let的特性const都有，不能重复声明、不存在变量提升、存在块级作用域也有暂时性死区，唯一的区别const声明常量，一旦声明无法修改。 但是有一点特别注意，上面的列子中不能修改的都是基本数据类型，对于数组或者对象都是引用数据类型，引用数据类型可以修改的是存在堆内存中的数据 javascript const esobj name year esobj name console log esobj const arr arr console log arr let定义的变量，只能在块作用域里访问，不能跨块作用域访问，也不能跨函数作用域访问 var定义的变量，可以跨块作用域访问 不能跨函数作用域访问 const用来定义常量，创建时必须赋值，只能在块作用域里访问，并且不能修改引用数据类型的指向地址，但是可以修改引用数据指向地址内的数据。 ,0
71208,18522995351.0,IssuesEvent,2021-10-20 16:58:42,golang/go,https://api.github.com/repos/golang/go,opened,x/build/dashboard: remove OpenBSD 6.4 builders,OS-OpenBSD Builders NeedsFix,"At this time, OpenBSD 7.0 (released 6 days ago) and 6.9 are the supported releases of OpenBSD per their support policy of maintaining the last 2 releases. OpenBSD 6.4 stopped being supported on October 17, 2019.
Go's OpenBSD support policy matches that of OpenBSD (https://golang.org/wiki/OpenBSD#longterm-support), so it's time to remove the OpenBSD 6.4 builders (for 386/amd64 archs). We'll have coverage from remaining OpenBSD 6.8 builders for same archs, plus ARM/MIPS ones, and any newer OpenBSD builders that are added.
CC @golang/release, @4a6f656c.",1.0,"x/build/dashboard: remove OpenBSD 6.4 builders - At this time, OpenBSD 7.0 (released 6 days ago) and 6.9 are the supported releases of OpenBSD per their support policy of maintaining the last 2 releases. OpenBSD 6.4 stopped being supported on October 17, 2019.
Go's OpenBSD support policy matches that of OpenBSD (https://golang.org/wiki/OpenBSD#longterm-support), so it's time to remove the OpenBSD 6.4 builders (for 386/amd64 archs). We'll have coverage from remaining OpenBSD 6.8 builders for same archs, plus ARM/MIPS ones, and any newer OpenBSD builders that are added.
CC @golang/release, @4a6f656c.",0,x build dashboard remove openbsd builders at this time openbsd released days ago and are the supported releases of openbsd per their support policy of maintaining the last releases openbsd stopped being supported on october go s openbsd support policy matches that of openbsd so it s time to remove the openbsd builders for archs we ll have coverage from remaining openbsd builders for same archs plus arm mips ones and any newer openbsd builders that are added cc golang release ,0
1767,2631744771.0,IssuesEvent,2015-03-07 11:32:56,Frege/frege,https://api.github.com/repos/Frege/frege,opened,lang-ref: chapter 5,documentation,"also not in the repo?
The long footnote: the argumentation around ""the current directory"" is a bit weak since in Java, one cannot change the current directory from within Java (only by using JNI to call into native code - but then one could also change env parameters that way.)",1.0,"lang-ref: chapter 5 - also not in the repo?
The long footnote: the argumentation around ""the current directory"" is a bit weak since in Java, one cannot change the current directory from within Java (only by using JNI to call into native code - but then one could also change env parameters that way.)",0,lang ref chapter also not in the repo the long footnote the argumentation around the current directory is a bit weak since in java one cannot change the current directory from within java only by using jni to call into native code but then one could also change env parameters that way ,0
380,6392819662.0,IssuesEvent,2017-08-04 04:38:40,UnixJunkie/parany,https://api.github.com/repos/UnixJunkie/parany,closed,Named semaphore size limit on OSX,portability,"turns out to be a bit short: [PSEMNAMLEN](https://github.com/st3fan/osx-10.9/blob/master/xnu-2422.1.72/bsd/sys/posix_sem.h#L54).
Can we `s/ocaml_//` [here](https://github.com/UnixJunkie/parany/blob/master/parany.ml#L25) ?
Or maybe (or also) change `pid` to `p` and `sem` to `s` ?",True,"Named semaphore size limit on OSX - turns out to be a bit short: [PSEMNAMLEN](https://github.com/st3fan/osx-10.9/blob/master/xnu-2422.1.72/bsd/sys/posix_sem.h#L54).
Can we `s/ocaml_//` [here](https://github.com/UnixJunkie/parany/blob/master/parany.ml#L25) ?
Or maybe (or also) change `pid` to `p` and `sem` to `s` ?",1,named semaphore size limit on osx turns out to be a bit short can we s ocaml or maybe or also change pid to p and sem to s ,1
549,7733692745.0,IssuesEvent,2018-05-26 14:57:04,systemd/systemd,https://api.github.com/repos/systemd/systemd,closed,There seems to be a memory leak in systemd-portabled,bug 🐛 has-pr ✨ portable,"I started to play with `portablectl` and came across a memory leak reported by `ASAN`. I think `attach` and `stop` should be enough to reproduce it:
```sh
-bash-4.4# /usr/lib/systemd/portablectl attach GIBBERISH
(Matching unit files with prefix 'GIBBERISH'.)
Failed to attach image: No image 'GIBBERISH' found.
-bash-4.4# systemctl stop systemd-portabled
```
Here is what I found in the journal:
```sh
systemd-portabled.service: Trying to enqueue job systemd-portabled.service/stop/replace
systemd-portabled.service: Installed new job systemd-portabled.service/stop as 335
systemd-portabled.service: Enqueued job systemd-portabled.service/stop as 335
systemd-portabled.service: Changed running -> stop-sigterm
Stopping Portable Service Manager...
systemd-portabled.service: D-Bus name org.freedesktop.portable1 no longer registered by :1.12
=================================================================
==152==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 10 byte(s) in 1 object(s) allocated from:
#0 0x7f467b823238 in __interceptor_strdup (/lib64/libasan.so.4+0x77238)
#1 0x7f467abc222d in strv_extend ../src/basic/strv.c:501
#2 0x7f467ac70403 in bus_message_read_strv_extend ../src/libsystemd/sd-bus/bus-message.c:5503
#3 0x7f467ac706ff in sd_bus_message_read_strv ../src/libsystemd/sd-bus/bus-message.c:5525
#4 0x5594d5aa88f9 in bus_image_common_attach ../src/portable/portabled-image-bus.c:235
#5 0x5594d5aa58af in redirect_method_to_image ../src/portable/portabled-bus.c:215
#6 0x5594d5aa5bf4 in method_attach_image ../src/portable/portabled-bus.c:250
#7 0x7f467ac783a9 in method_callbacks_run ../src/libsystemd/sd-bus/bus-objects.c:407
#8 0x7f467ac7fa48 in object_find_and_run ../src/libsystemd/sd-bus/bus-objects.c:1265
#9 0x7f467ac80ca9 in bus_process_object ../src/libsystemd/sd-bus/bus-objects.c:1381
#10 0x7f467acc3e82 in process_message ../src/libsystemd/sd-bus/sd-bus.c:2666
#11 0x7f467acc42f4 in process_running ../src/libsystemd/sd-bus/sd-bus.c:2708
#12 0x7f467acc64a3 in bus_process_internal ../src/libsystemd/sd-bus/sd-bus.c:2927
#13 0x7f467acc666b in sd_bus_process ../src/libsystemd/sd-bus/sd-bus.c:2954
#14 0x7f467acc922c in io_callback ../src/libsystemd/sd-bus/sd-bus.c:3299
#15 0x7f467ad61e85 in source_dispatch ../src/libsystemd/sd-event/sd-event.c:2294
#16 0x7f467ad65bd2 in sd_event_dispatch ../src/libsystemd/sd-event/sd-event.c:2652
#17 0x7f467ad66829 in sd_event_run ../src/libsystemd/sd-event/sd-event.c:2709
#18 0x7f467a9d15db in bus_event_loop_with_idle ../src/shared/bus-util.c:124
#19 0x5594d5aaf406 in manager_run ../src/portable/portabled.c:117
#20 0x5594d5aaf9d1 in main ../src/portable/portabled.c:161
#21 0x7f46791eaf29 in __libc_start_main (/lib64/libc.so.6+0x20f29)
SUMMARY: AddressSanitizer: 10 byte(s) leaked in 1 allocation(s).
systemd-portabled.service: Child 152 belongs to systemd-portabled.service.
systemd-portabled.service: Main process exited, code=exited, status=1/FAILURE
systemd-portabled.service: Failed with result 'exit-code'.
systemd-portabled.service: Changed stop-sigterm -> failed
systemd-portabled.service: Job systemd-portabled.service/stop finished, result=done
Stopped Portable Service Manager.
systemd-portabled.service: Unit entered failed state.
```",True,"There seems to be a memory leak in systemd-portabled - I started to play with `portablectl` and came across a memory leak reported by `ASAN`. I think `attach` and `stop` should be enough to reproduce it:
```sh
-bash-4.4# /usr/lib/systemd/portablectl attach GIBBERISH
(Matching unit files with prefix 'GIBBERISH'.)
Failed to attach image: No image 'GIBBERISH' found.
-bash-4.4# systemctl stop systemd-portabled
```
Here is what I found in the journal:
```sh
systemd-portabled.service: Trying to enqueue job systemd-portabled.service/stop/replace
systemd-portabled.service: Installed new job systemd-portabled.service/stop as 335
systemd-portabled.service: Enqueued job systemd-portabled.service/stop as 335
systemd-portabled.service: Changed running -> stop-sigterm
Stopping Portable Service Manager...
systemd-portabled.service: D-Bus name org.freedesktop.portable1 no longer registered by :1.12
=================================================================
==152==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 10 byte(s) in 1 object(s) allocated from:
#0 0x7f467b823238 in __interceptor_strdup (/lib64/libasan.so.4+0x77238)
#1 0x7f467abc222d in strv_extend ../src/basic/strv.c:501
#2 0x7f467ac70403 in bus_message_read_strv_extend ../src/libsystemd/sd-bus/bus-message.c:5503
#3 0x7f467ac706ff in sd_bus_message_read_strv ../src/libsystemd/sd-bus/bus-message.c:5525
#4 0x5594d5aa88f9 in bus_image_common_attach ../src/portable/portabled-image-bus.c:235
#5 0x5594d5aa58af in redirect_method_to_image ../src/portable/portabled-bus.c:215
#6 0x5594d5aa5bf4 in method_attach_image ../src/portable/portabled-bus.c:250
#7 0x7f467ac783a9 in method_callbacks_run ../src/libsystemd/sd-bus/bus-objects.c:407
#8 0x7f467ac7fa48 in object_find_and_run ../src/libsystemd/sd-bus/bus-objects.c:1265
#9 0x7f467ac80ca9 in bus_process_object ../src/libsystemd/sd-bus/bus-objects.c:1381
#10 0x7f467acc3e82 in process_message ../src/libsystemd/sd-bus/sd-bus.c:2666
#11 0x7f467acc42f4 in process_running ../src/libsystemd/sd-bus/sd-bus.c:2708
#12 0x7f467acc64a3 in bus_process_internal ../src/libsystemd/sd-bus/sd-bus.c:2927
#13 0x7f467acc666b in sd_bus_process ../src/libsystemd/sd-bus/sd-bus.c:2954
#14 0x7f467acc922c in io_callback ../src/libsystemd/sd-bus/sd-bus.c:3299
#15 0x7f467ad61e85 in source_dispatch ../src/libsystemd/sd-event/sd-event.c:2294
#16 0x7f467ad65bd2 in sd_event_dispatch ../src/libsystemd/sd-event/sd-event.c:2652
#17 0x7f467ad66829 in sd_event_run ../src/libsystemd/sd-event/sd-event.c:2709
#18 0x7f467a9d15db in bus_event_loop_with_idle ../src/shared/bus-util.c:124
#19 0x5594d5aaf406 in manager_run ../src/portable/portabled.c:117
#20 0x5594d5aaf9d1 in main ../src/portable/portabled.c:161
#21 0x7f46791eaf29 in __libc_start_main (/lib64/libc.so.6+0x20f29)
SUMMARY: AddressSanitizer: 10 byte(s) leaked in 1 allocation(s).
systemd-portabled.service: Child 152 belongs to systemd-portabled.service.
systemd-portabled.service: Main process exited, code=exited, status=1/FAILURE
systemd-portabled.service: Failed with result 'exit-code'.
systemd-portabled.service: Changed stop-sigterm -> failed
systemd-portabled.service: Job systemd-portabled.service/stop finished, result=done
Stopped Portable Service Manager.
systemd-portabled.service: Unit entered failed state.
```",1,there seems to be a memory leak in systemd portabled i started to play with portablectl and came across a memory leak reported by asan i think attach and stop should be enough to reproduce it sh bash usr lib systemd portablectl attach gibberish matching unit files with prefix gibberish failed to attach image no image gibberish found bash systemctl stop systemd portabled here is what i found in the journal sh systemd portabled service trying to enqueue job systemd portabled service stop replace systemd portabled service installed new job systemd portabled service stop as systemd portabled service enqueued job systemd portabled service stop as systemd portabled service changed running stop sigterm stopping portable service manager systemd portabled service d bus name org freedesktop no longer registered by error leaksanitizer detected memory leaks direct leak of byte s in object s allocated from in interceptor strdup libasan so in strv extend src basic strv c in bus message read strv extend src libsystemd sd bus bus message c in sd bus message read strv src libsystemd sd bus bus message c in bus image common attach src portable portabled image bus c in redirect method to image src portable portabled bus c in method attach image src portable portabled bus c in method callbacks run src libsystemd sd bus bus objects c in object find and run src libsystemd sd bus bus objects c in bus process object src libsystemd sd bus bus objects c in process message src libsystemd sd bus sd bus c in process running src libsystemd sd bus sd bus c in bus process internal src libsystemd sd bus sd bus c in sd bus process src libsystemd sd bus sd bus c in io callback src libsystemd sd bus sd bus c in source dispatch src libsystemd sd event sd event c in sd event dispatch src libsystemd sd event sd event c in sd event run src libsystemd sd event sd event c in bus event loop with idle src shared bus util c in manager run src portable portabled c in main src portable portabled c in libc start main libc so summary addresssanitizer byte s leaked in allocation s systemd portabled service child belongs to systemd portabled service systemd portabled service main process exited code exited status failure systemd portabled service failed with result exit code systemd portabled service changed stop sigterm failed systemd portabled service job systemd portabled service stop finished result done stopped portable service manager systemd portabled service unit entered failed state ,1
917,11983057598.0,IssuesEvent,2020-04-07 13:54:25,ToFuProject/tofu,https://api.github.com/repos/ToFuProject/tofu,closed,Change default separator in to_dict() from '_' to '.',Fixed in devel portability,"The default separator for flattening nested dict is currently `'_'`.
* It keeps users from defining attributes with `'_'` in the name
* A `'.'` would better render te nested structure
=> Switch from `'_'` to `'.'`
=> Ensure backward-retrocompatibility in `tf.load()` by implementing a general test",True,"Change default separator in to_dict() from '_' to '.' - The default separator for flattening nested dict is currently `'_'`.
* It keeps users from defining attributes with `'_'` in the name
* A `'.'` would better render te nested structure
=> Switch from `'_'` to `'.'`
=> Ensure backward-retrocompatibility in `tf.load()` by implementing a general test",1,change default separator in to dict from to the default separator for flattening nested dict is currently it keeps users from defining attributes with in the name a would better render te nested structure switch from to ensure backward retrocompatibility in tf load by implementing a general test,1
133,3487812984.0,IssuesEvent,2016-01-02 09:37:27,edenhill/librdkafka,https://api.github.com/repos/edenhill/librdkafka,closed,Getting errno from DLL,enhancement portability,"I'm building librdkafka as a DLL that contains static version of the run-time library (/MT).
The problem is that calling application can no longer get errno, since it's different run-time.
Is it possible to add new function to expose errno?
e.g.
`int rd_errno() { return errno; }`
Thanks.
",True,"Getting errno from DLL - I'm building librdkafka as a DLL that contains static version of the run-time library (/MT).
The problem is that calling application can no longer get errno, since it's different run-time.
Is it possible to add new function to expose errno?
e.g.
`int rd_errno() { return errno; }`
Thanks.
",1,getting errno from dll i m building librdkafka as a dll that contains static version of the run time library mt the problem is that calling application can no longer get errno since it s different run time is it possible to add new function to expose errno e g int rd errno return errno thanks ,1
141553,5437994424.0,IssuesEvent,2017-03-06 09:09:44,robotology/gazebo-yarp-plugins,https://api.github.com/repos/robotology/gazebo-yarp-plugins,closed,Test compilation against Gazebo 8 ,Complexity: Medium Priority: IFI Day Priority: Normal,"Gazebo 8 has been recently released ( http://gazebosim.org/blog/gazebo8 ) but it does not support Ubuntu 14.04 Trusty. As Travis only supports Trusty at the moment, we have no way of checking if `gazebo-yarp-plugins` compile against Gazebo 8.
By randomly searching only it seems that it should be possible to use Xenial on Travis using Docker, but I don't fully understand how this is supposed to work and which are the limitations. Perhaps @diegoferigo knows something more on this?",2.0,"Test compilation against Gazebo 8 - Gazebo 8 has been recently released ( http://gazebosim.org/blog/gazebo8 ) but it does not support Ubuntu 14.04 Trusty. As Travis only supports Trusty at the moment, we have no way of checking if `gazebo-yarp-plugins` compile against Gazebo 8.
By randomly searching only it seems that it should be possible to use Xenial on Travis using Docker, but I don't fully understand how this is supposed to work and which are the limitations. Perhaps @diegoferigo knows something more on this?",0,test compilation against gazebo gazebo has been recently released but it does not support ubuntu trusty as travis only supports trusty at the moment we have no way of checking if gazebo yarp plugins compile against gazebo by randomly searching only it seems that it should be possible to use xenial on travis using docker but i don t fully understand how this is supposed to work and which are the limitations perhaps diegoferigo knows something more on this ,0
134,3488370526.0,IssuesEvent,2016-01-02 22:11:20,svaarala/duktape,https://api.github.com/repos/svaarala/duktape,closed,Add support for using C++ exceptions instead of setjmp/longjmp to support RAII,enhancement portability,"Hello,
We have a problem with RAII and automatic destruction via stack unwinding because duktape use setjmp/longjmp.
Lua proposes to use real C++ exception instead of setjmp/longjmp if compiled in C++. Can we add this for duktape too?
The following code will never call the Object destructor from test function.
#include
#include ""duktape.h""
class Object
{
public:
Object() = default;
~Object()
{
puts(""Destroying object"");
}
};
duk_ret_t test(duk_context *ctx)
{
Object o;
duk_push_string(ctx, ""hello"");
duk_throw(ctx);
return 0;
}
int main(void)
{
auto ctx = duk_create_heap_default();
duk_push_global_object(ctx);
duk_push_c_function(ctx, test, 0);
duk_put_prop_string(ctx, -2, ""test"");
duk_peval_string(ctx, ""try { test(); } catch (ex) { print(ex); }"");
return 0;
}",True,"Add support for using C++ exceptions instead of setjmp/longjmp to support RAII - Hello,
We have a problem with RAII and automatic destruction via stack unwinding because duktape use setjmp/longjmp.
Lua proposes to use real C++ exception instead of setjmp/longjmp if compiled in C++. Can we add this for duktape too?
The following code will never call the Object destructor from test function.
#include
#include ""duktape.h""
class Object
{
public:
Object() = default;
~Object()
{
puts(""Destroying object"");
}
};
duk_ret_t test(duk_context *ctx)
{
Object o;
duk_push_string(ctx, ""hello"");
duk_throw(ctx);
return 0;
}
int main(void)
{
auto ctx = duk_create_heap_default();
duk_push_global_object(ctx);
duk_push_c_function(ctx, test, 0);
duk_put_prop_string(ctx, -2, ""test"");
duk_peval_string(ctx, ""try { test(); } catch (ex) { print(ex); }"");
return 0;
}",1,add support for using c exceptions instead of setjmp longjmp to support raii hello we have a problem with raii and automatic destruction via stack unwinding because duktape use setjmp longjmp lua proposes to use real c exception instead of setjmp longjmp if compiled in c can we add this for duktape too the following code will never call the object destructor from test function include include duktape h class object public object default object puts destroying object duk ret t test duk context ctx object o duk push string ctx hello duk throw ctx return int main void auto ctx duk create heap default duk push global object ctx duk push c function ctx test duk put prop string ctx test duk peval string ctx try test catch ex print ex return ,1
288052,31856946666.0,IssuesEvent,2023-09-15 08:10:30,nidhi7598/linux-4.19.72_CVE-2022-3564,https://api.github.com/repos/nidhi7598/linux-4.19.72_CVE-2022-3564,closed,CVE-2020-29370 (High) detected in linuxlinux-4.19.294 - autoclosed,Mend: dependency security vulnerability,"## CVE-2020-29370 - High Severity Vulnerability
Vulnerable Library - linuxlinux-4.19.294
The Linux Kernel
Library home page: https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux
Found in HEAD commit: 454c7dacf6fa9a6de86d4067f5a08f25cffa519b
Found in base branch: main
Vulnerable Source Files (2)
/mm/slub.c
/mm/slub.c
Vulnerability Details
An issue was discovered in kmem_cache_alloc_bulk in mm/slub.c in the Linux kernel before 5.5.11. The slowpath lacks the required TID increment, aka CID-fd4d9c7d0c71.
Publish Date: 2020-11-28
URL: CVE-2020-29370
CVSS 3 Score Details (7.0)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-29370
Release Date: 2020-11-28
Fix Resolution: v5.6-rc7,v5.5.11,v5.4.28
Vulnerable Library - linuxlinux-4.19.294
The Linux Kernel
Library home page: https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux
Found in HEAD commit: 454c7dacf6fa9a6de86d4067f5a08f25cffa519b
Found in base branch: main
Vulnerable Source Files (2)
/mm/slub.c
/mm/slub.c
Vulnerability Details
An issue was discovered in kmem_cache_alloc_bulk in mm/slub.c in the Linux kernel before 5.5.11. The slowpath lacks the required TID increment, aka CID-fd4d9c7d0c71.
Publish Date: 2020-11-28
URL: CVE-2020-29370
CVSS 3 Score Details (7.0)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-29370
Release Date: 2020-11-28
Fix Resolution: v5.6-rc7,v5.5.11,v5.4.28
Vulnerable Library - linuxv3.0
Linux kernel source tree
Library home page: https://github.com/verygreen/linux.git
Found in HEAD commit: 0c501f5a0fd72c7b2ac82904235363bd44fd8f9e
Found in base branch: master
Vulnerable Source Files (0)
Vulnerability Details
The keyring_search_aux function in security/keys/keyring.c in the Linux kernel through 3.14.79 allows local users to cause a denial of service (NULL pointer dereference and OOPS) via a request_key system call for the ""dead"" type.
Publish Date: 2017-03-16
URL: CVE-2017-6951
CVSS 3 Score Details (5.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-6951
Release Date: 2017-03-16
Fix Resolution: v4.11-rc8
Vulnerable Library - linuxv3.0
Linux kernel source tree
Library home page: https://github.com/verygreen/linux.git
Found in HEAD commit: 0c501f5a0fd72c7b2ac82904235363bd44fd8f9e
Found in base branch: master
Vulnerable Source Files (0)
Vulnerability Details
The keyring_search_aux function in security/keys/keyring.c in the Linux kernel through 3.14.79 allows local users to cause a denial of service (NULL pointer dereference and OOPS) via a request_key system call for the ""dead"" type.
Publish Date: 2017-03-16
URL: CVE-2017-6951
CVSS 3 Score Details (5.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-6951
Release Date: 2017-03-16
Fix Resolution: v4.11-rc8
> **Warning:** if you are exploring PureScript and a compiler release was made recently, read `Breaking Compiler Changes and Bower`
#### Solutions to Common Problems with Bower
At various times, you might encounter a problem with Bower due to its cache mechanism. When in doubt, run the following command and see if that fixes your issue:
```bash
# Deletes the 'bower_modules' and 'output' directories,
# ensuring that the next build will be completely fresh.
rm -rf bower_modules/ output/
```
# Breaking Compiler Changes and Bower
The following issue is happening less and less frequently, but still needs to be stated.
## Annoyance Defined
If a compiler release that includes breaking changes was released recently, it will take some time for libraries in the ecosystem to become compatible with that release. If you are using Bower as your dependency manager, it may try to install libraries that are and are not compatible with the new release, creating problems.
## Recommended Guidelines
In such circumstances, follow these guidelines to help find the correct version of a library:
- Go to Pursuit and look at the library's package page. Choose one of the library's versions and compare that version's publish date with the date of the compiler release. Those that occur after the compiler release are likely compatible with the new release.
- Since `purescript-prelude` is a dependency for most libraries, see which version of `purescript-prelude` the library uses. That should indicate whether it's compatible with a new compiler release or not.
- If all else fails, check the library's last few commit messages in its repository for any messages about updating to the new compiler release.
",1.0,"Include 'Solutions to Common Bower problems' in this repo - Include the work I did in purescript/documentation#237 but which wasn't included due to being 'out of the scope of project goals.'
> **Warning:** if you are exploring PureScript and a compiler release was made recently, read `Breaking Compiler Changes and Bower`
#### Solutions to Common Problems with Bower
At various times, you might encounter a problem with Bower due to its cache mechanism. When in doubt, run the following command and see if that fixes your issue:
```bash
# Deletes the 'bower_modules' and 'output' directories,
# ensuring that the next build will be completely fresh.
rm -rf bower_modules/ output/
```
# Breaking Compiler Changes and Bower
The following issue is happening less and less frequently, but still needs to be stated.
## Annoyance Defined
If a compiler release that includes breaking changes was released recently, it will take some time for libraries in the ecosystem to become compatible with that release. If you are using Bower as your dependency manager, it may try to install libraries that are and are not compatible with the new release, creating problems.
## Recommended Guidelines
In such circumstances, follow these guidelines to help find the correct version of a library:
- Go to Pursuit and look at the library's package page. Choose one of the library's versions and compare that version's publish date with the date of the compiler release. Those that occur after the compiler release are likely compatible with the new release.
- Since `purescript-prelude` is a dependency for most libraries, see which version of `purescript-prelude` the library uses. That should indicate whether it's compatible with a new compiler release or not.
- If all else fails, check the library's last few commit messages in its repository for any messages about updating to the new compiler release.
",0,include solutions to common bower problems in this repo include the work i did in purescript documentation but which wasn t included due to being out of the scope of project goals warning if you are exploring purescript and a compiler release was made recently read breaking compiler changes and bower solutions to common problems with bower at various times you might encounter a problem with bower due to its cache mechanism when in doubt run the following command and see if that fixes your issue bash deletes the bower modules and output directories ensuring that the next build will be completely fresh rm rf bower modules output breaking compiler changes and bower the following issue is happening less and less frequently but still needs to be stated annoyance defined if a compiler release that includes breaking changes was released recently it will take some time for libraries in the ecosystem to become compatible with that release if you are using bower as your dependency manager it may try to install libraries that are and are not compatible with the new release creating problems recommended guidelines in such circumstances follow these guidelines to help find the correct version of a library go to pursuit and look at the library s package page choose one of the library s versions and compare that version s publish date with the date of the compiler release those that occur after the compiler release are likely compatible with the new release since purescript prelude is a dependency for most libraries see which version of purescript prelude the library uses that should indicate whether it s compatible with a new compiler release or not if all else fails check the library s last few commit messages in its repository for any messages about updating to the new compiler release ,0
6866,6649567238.0,IssuesEvent,2017-09-28 13:40:25,commercetools/commercetools-sync-java,https://api.github.com/repos/commercetools/commercetools-sync-java,opened,JavaDoc Jar seems to not be uploaded to bintray,Infrastructure,"### Description
https://travis-ci.org/commercetools/commercetools-sync-java/builds/280844376
Seems that the JavaDoc Jar is not built still (as seen in the latest build) and hence the releases are still not making it to maven central: https://bintray.com/commercetools/maven/commercetools-sync-java#central
",1.0,"JavaDoc Jar seems to not be uploaded to bintray - ### Description
https://travis-ci.org/commercetools/commercetools-sync-java/builds/280844376
Seems that the JavaDoc Jar is not built still (as seen in the latest build) and hence the releases are still not making it to maven central: https://bintray.com/commercetools/maven/commercetools-sync-java#central
",0,javadoc jar seems to not be uploaded to bintray description seems that the javadoc jar is not built still as seen in the latest build and hence the releases are still not making it to maven central ,0
97102,10981259322.0,IssuesEvent,2019-11-30 20:22:51,adopted-ember-addons/ember-electron,https://api.github.com/repos/adopted-ember-addons/ember-electron,opened,Add testing docs,documentation,We should add some docs to let people know to write normal Ember tests and how we would recommend testing the electron parts.,1.0,Add testing docs - We should add some docs to let people know to write normal Ember tests and how we would recommend testing the electron parts.,0,add testing docs we should add some docs to let people know to write normal ember tests and how we would recommend testing the electron parts ,0
746,10083433623.0,IssuesEvent,2019-07-25 13:40:28,Azure/azure-webjobs-sdk,https://api.github.com/repos/Azure/azure-webjobs-sdk,closed,Queue Trigger Polling Instrumentation Request,3.x Supportability,"There have been a number of reports of the QueueTrigger stop polling and a restart of the Web Job is needed.
This is on QueueTrigger jobs written using Web Jobs 3.x.
E.G.
[Queue trigger stops picking up messages after connection drops and restores}(https://github.com/Azure/azure-webjobs-sdk/issues/2072)
[QueueTrigger stops triggering - how to troubleshoot?] (https://github.com/Azure/azure-webjobs-sdk/issues/2136)
This is referenced in general at [Instrument Polling Algorithms with Trace statements](https://github.com/Azure/azure-webjobs-sdk/issues/1956)
The main idea would be to show if we're still polling the Queue or if it has stopped for some reason.
Otherwise to troubleshoot this we would need more information.
1. Storage Account Logs for the Queue we are polling.
2. A Dump file of the Dotnet.exe process hosting the WebJob that is not responding.
",True,"Queue Trigger Polling Instrumentation Request - There have been a number of reports of the QueueTrigger stop polling and a restart of the Web Job is needed.
This is on QueueTrigger jobs written using Web Jobs 3.x.
E.G.
[Queue trigger stops picking up messages after connection drops and restores}(https://github.com/Azure/azure-webjobs-sdk/issues/2072)
[QueueTrigger stops triggering - how to troubleshoot?] (https://github.com/Azure/azure-webjobs-sdk/issues/2136)
This is referenced in general at [Instrument Polling Algorithms with Trace statements](https://github.com/Azure/azure-webjobs-sdk/issues/1956)
The main idea would be to show if we're still polling the Queue or if it has stopped for some reason.
Otherwise to troubleshoot this we would need more information.
1. Storage Account Logs for the Queue we are polling.
2. A Dump file of the Dotnet.exe process hosting the WebJob that is not responding.
",1,queue trigger polling instrumentation request there have been a number of reports of the queuetrigger stop polling and a restart of the web job is needed this is on queuetrigger jobs written using web jobs x e g queue trigger stops picking up messages after connection drops and restores this is referenced in general at the main idea would be to show if we re still polling the queue or if it has stopped for some reason otherwise to troubleshoot this we would need more information storage account logs for the queue we are polling a dump file of the dotnet exe process hosting the webjob that is not responding ,1
54171,29801282852.0,IssuesEvent,2023-06-16 08:18:05,JanusGraph/janusgraph,https://api.github.com/repos/JanusGraph/janusgraph,closed,Enable multiQuery optimization for valueMap step,kind/performance area/tinkerpop area/core,"We have JanusGraphPropertiesStep which extends PropertiesStep and supports multiQuery optimization, so that values() step can be optimized.
We can do something similar to PropertyMapStep so that multiQuery optimization can be applied to valueMap() step as well.
Requested by https://github.com/JanusGraph/janusgraph/discussions/2401",True,"Enable multiQuery optimization for valueMap step - We have JanusGraphPropertiesStep which extends PropertiesStep and supports multiQuery optimization, so that values() step can be optimized.
We can do something similar to PropertyMapStep so that multiQuery optimization can be applied to valueMap() step as well.
Requested by https://github.com/JanusGraph/janusgraph/discussions/2401",0,enable multiquery optimization for valuemap step we have janusgraphpropertiesstep which extends propertiesstep and supports multiquery optimization so that values step can be optimized we can do something similar to propertymapstep so that multiquery optimization can be applied to valuemap step as well requested by ,0
96099,19899770916.0,IssuesEvent,2022-01-25 06:07:51,flutter/website,https://api.github.com/repos/flutter/website,closed,"[PAGE ISSUE]: 'Write your first Flutter app, part 1'",p2-medium e0-minutes codelab,"### Page URL
https://docs.flutter.dev/get-started/codelab/
### Page source
https://github.com/flutter/website/tree/main/src/get-started/codelab.md
### Describe the problem
The page says the following:
> The main() method uses arrow (=>) notation. Use arrow notation for one-line functions or methods.
Yet the referenced code does not appear to actually use arrow notation.
### Expected fix
_No response_
### Additional context
_No response_",1.0,"[PAGE ISSUE]: 'Write your first Flutter app, part 1' - ### Page URL
https://docs.flutter.dev/get-started/codelab/
### Page source
https://github.com/flutter/website/tree/main/src/get-started/codelab.md
### Describe the problem
The page says the following:
> The main() method uses arrow (=>) notation. Use arrow notation for one-line functions or methods.
Yet the referenced code does not appear to actually use arrow notation.
### Expected fix
_No response_
### Additional context
_No response_",0, write your first flutter app part page url page source describe the problem the page says the following the main method uses arrow notation use arrow notation for one line functions or methods yet the referenced code does not appear to actually use arrow notation expected fix no response additional context no response ,0
287901,21676489913.0,IssuesEvent,2022-05-08 19:55:22,bounswe/bounswe2022group9,https://api.github.com/repos/bounswe/bounswe2022group9,closed,Combining Milestone Report,Documentation Priority: High In Progress,"TODO:
- [x] Everyone shall put their parts on the Milestone Report",1.0,"Combining Milestone Report - TODO:
- [x] Everyone shall put their parts on the Milestone Report",0,combining milestone report todo everyone shall put their parts on the milestone report,0
49624,6228788252.0,IssuesEvent,2017-07-11 00:52:02,autoboxer/MARE,https://api.github.com/repos/autoboxer/MARE,opened,redesign the All Events page,category - redesign development - css development - html development - node,This should match Anna's designs (possibly changing the 'more' arrow to fit the content pages that already exist to prevent a greater amount of rework.,1.0,redesign the All Events page - This should match Anna's designs (possibly changing the 'more' arrow to fit the content pages that already exist to prevent a greater amount of rework.,0,redesign the all events page this should match anna s designs possibly changing the more arrow to fit the content pages that already exist to prevent a greater amount of rework ,0
729805,25145678117.0,IssuesEvent,2022-11-10 05:01:30,open-telemetry/opentelemetry-collector-contrib,https://api.github.com/repos/open-telemetry/opentelemetry-collector-contrib,closed,[exporter/clickhouseexporter] Clickhouse export fail due to plog.LogRecordFlags unable to convert to UInt32,bug Stale priority:p2 exporter/clickhouse,"**Describe the bug**
A clear and concise description of what the bug is.
Clickhouse export fail because clickhouse-go is unable to convert plog.LogRecordFlags into UInt32
**Steps to reproduce**
If possible, provide a recipe for reproducing the error.
Configure clickhouse exporter with default values and send logs then the error should pop out.
**What did you expect to see?**
A clear and concise description of what you expected to see.
OpenTelemetry Collector should export to Clickhouse database.
**What did you see instead?**
A clear and concise description of what you saw instead.
```
2022-09-02T09:11:06.767Z info exporterhelper/queued_retry.go:427 Exporting failed. Will retry the request after interval. {""kind"": ""exporter"", ""data_type"": ""logs"", ""name"": ""clickhouse"", ""error"": ""ExecContext:clickhouse [AppendRow]: TraceFlags clickhouse [AppendRow]: converting plog.LogRecordFlags to UInt32 is unsupported"", ""interval"": ""21.589639508s""}
```
**What version did you use?**
Version: v0.59.0
**What config did you use?**
Config:
```yaml
extensions:
health_check:
receivers:
otlp:
grpc:
http:
processors:
batch:
timeout: 1s
exporters:
clickhouse:
dsn: clickhouse://default:password@localhost:9000/default
ttl_days: 3
timeout: 5s
logs_table_name: otel_logs
retry_on_failure:
enabled: true
initial_interval: 5s
max_interval: 30s
max_elapsed_time: 300s
logging:
logLevel: info
service:
pipelines:
logs:
receivers: [otlp]
processors: [batch]
exporters:
- clickhouse
- logging
extensions: [health_check]
```
**Environment**
Docker Image: otel/opentelemetry-collector-contrib:0.59.0
Platform: arm64
OS: Ubuntu 22.04
",1.0,"[exporter/clickhouseexporter] Clickhouse export fail due to plog.LogRecordFlags unable to convert to UInt32 - **Describe the bug**
A clear and concise description of what the bug is.
Clickhouse export fail because clickhouse-go is unable to convert plog.LogRecordFlags into UInt32
**Steps to reproduce**
If possible, provide a recipe for reproducing the error.
Configure clickhouse exporter with default values and send logs then the error should pop out.
**What did you expect to see?**
A clear and concise description of what you expected to see.
OpenTelemetry Collector should export to Clickhouse database.
**What did you see instead?**
A clear and concise description of what you saw instead.
```
2022-09-02T09:11:06.767Z info exporterhelper/queued_retry.go:427 Exporting failed. Will retry the request after interval. {""kind"": ""exporter"", ""data_type"": ""logs"", ""name"": ""clickhouse"", ""error"": ""ExecContext:clickhouse [AppendRow]: TraceFlags clickhouse [AppendRow]: converting plog.LogRecordFlags to UInt32 is unsupported"", ""interval"": ""21.589639508s""}
```
**What version did you use?**
Version: v0.59.0
**What config did you use?**
Config:
```yaml
extensions:
health_check:
receivers:
otlp:
grpc:
http:
processors:
batch:
timeout: 1s
exporters:
clickhouse:
dsn: clickhouse://default:password@localhost:9000/default
ttl_days: 3
timeout: 5s
logs_table_name: otel_logs
retry_on_failure:
enabled: true
initial_interval: 5s
max_interval: 30s
max_elapsed_time: 300s
logging:
logLevel: info
service:
pipelines:
logs:
receivers: [otlp]
processors: [batch]
exporters:
- clickhouse
- logging
extensions: [health_check]
```
**Environment**
Docker Image: otel/opentelemetry-collector-contrib:0.59.0
Platform: arm64
OS: Ubuntu 22.04
",0, clickhouse export fail due to plog logrecordflags unable to convert to describe the bug a clear and concise description of what the bug is clickhouse export fail because clickhouse go is unable to convert plog logrecordflags into steps to reproduce if possible provide a recipe for reproducing the error configure clickhouse exporter with default values and send logs then the error should pop out what did you expect to see a clear and concise description of what you expected to see opentelemetry collector should export to clickhouse database what did you see instead a clear and concise description of what you saw instead info exporterhelper queued retry go exporting failed will retry the request after interval kind exporter data type logs name clickhouse error execcontext clickhouse traceflags clickhouse converting plog logrecordflags to is unsupported interval what version did you use version what config did you use config yaml extensions health check receivers otlp grpc http processors batch timeout exporters clickhouse dsn clickhouse default password localhost default ttl days timeout logs table name otel logs retry on failure enabled true initial interval max interval max elapsed time logging loglevel info service pipelines logs receivers processors exporters clickhouse logging extensions environment docker image otel opentelemetry collector contrib platform os ubuntu ,0
52983,6668800387.0,IssuesEvent,2017-10-03 17:01:54,Esri/military-feature-toolbox,https://api.github.com/repos/Esri/military-feature-toolbox,closed,Transfer labels,4 - Done A-bug A-feature A-question B-high B-low B-moderate C-L C-M C-S C-XL C-XS E-as designed E-duplicate E-invalid E-no count E-non reproducible E-verified E-won't fix FT-Workflows G-Design G-Development G-Documentation G-Documentation Review G-Research G-Testing HP-Candidate HP-HotFix HP-Patch priority - Showstopper,"_From @lfunkhouser on October 3, 2017 16:48_
_From @lfunkhouser on October 2, 2017 15:24_
This issue is used to transfer issues to another repo
_Copied from original issue: Esri/solutions-grg-widget#119_
_Copied from original issue: Esri/solutions-geoevent-java#79_",2.0,"Transfer labels - _From @lfunkhouser on October 3, 2017 16:48_
_From @lfunkhouser on October 2, 2017 15:24_
This issue is used to transfer issues to another repo
_Copied from original issue: Esri/solutions-grg-widget#119_
_Copied from original issue: Esri/solutions-geoevent-java#79_",0,transfer labels from lfunkhouser on october from lfunkhouser on october this issue is used to transfer issues to another repo copied from original issue esri solutions grg widget copied from original issue esri solutions geoevent java ,0
1324,18285046427.0,IssuesEvent,2021-10-05 09:20:30,SAP/xsk,https://api.github.com/repos/SAP/xsk,opened,[Core] Log xssecurity processor errors using ProblemsFacade,core customer supportability,"Implement it for the **xssecurity** processor.
This will help for customer testing.
Using method `logProcessorsErrors()` in [class](https://github.com/SAP/xsk/blob/main/modules/engines/engine-commons/src/main/java/com/sap/xsk/utils/XSKCommonsUtils.java).
Related to: https://github.com/SAP/xsk/issues/465",True,"[Core] Log xssecurity processor errors using ProblemsFacade - Implement it for the **xssecurity** processor.
This will help for customer testing.
Using method `logProcessorsErrors()` in [class](https://github.com/SAP/xsk/blob/main/modules/engines/engine-commons/src/main/java/com/sap/xsk/utils/XSKCommonsUtils.java).
Related to: https://github.com/SAP/xsk/issues/465",1, log xssecurity processor errors using problemsfacade implement it for the xssecurity processor this will help for customer testing using method logprocessorserrors in related to ,1
39259,5064659089.0,IssuesEvent,2016-12-23 08:00:18,tor4kichi/Hohoema,https://api.github.com/repos/tor4kichi/Hohoema,opened,メニューを含めたベースレイアウトを修正,ui_design,"以下の画面タイプごとにレイアウトが適用されるように変更します。
* 中～大画面向け
* モバイル向け
* XInput向け
PCで操作中の場合にXInputレイアウトを使用しないオプションを利用可能にします。",1.0,"メニューを含めたベースレイアウトを修正 - 以下の画面タイプごとにレイアウトが適用されるように変更します。
* 中～大画面向け
* モバイル向け
* XInput向け
PCで操作中の場合にXInputレイアウトを使用しないオプションを利用可能にします。",0,メニューを含めたベースレイアウトを修正 以下の画面タイプごとにレイアウトが適用されるように変更します。 中～大画面向け モバイル向け xinput向け pcで操作中の場合にxinputレイアウトを使用しないオプションを利用可能にします。,0
700124,24047753356.0,IssuesEvent,2022-09-16 09:51:17,magento/magento2,https://api.github.com/repos/magento/magento2,closed,Wrong Tax calculation on Creditmemo (under certain circumstances),Issue: Cannot Reproduce Progress: PR in progress Priority: P1 Issue: ready for confirmation Issue: needs update,"
### Preconditions (*)
1. 2.4.3
2. Create Creditmemo in Backend
3. Sometimes they can not be displayed as there is an Exception in the template (see below)
### Steps to reproduce (*)
1. Hard to reproduce, anyhow: If you have mainly zero tax articles and create creditmemos they can not be displayed (Exception in the template), if the order with the same ID as the creditmemo contains articles with taxes.
### Expected result (*)
1. Creditmemos can all be displayed correctly
### Actual result (*)
1. Exception thrown in magento/module-sales/view/adminhtml/templates/order/totals/tax.phtml:62 (trying to access method on array)
---
Please provide [Severity](https://devdocs.magento.com/guides/v2.4/contributor-guide/contributing.html#backlog) assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.
- [ ] Severity: **S0** _- Affects critical data or functionality and leaves users without workaround._
- [x] Severity: **S1** _- Affects critical data or functionality and forces users to employ a workaround._
- [ ] Severity: **S2** _- Affects non-critical data or functionality and forces users to employ a workaround._
- [ ] Severity: **S3** _- Affects non-critical data or functionality and does not force users to employ a workaround._
- [ ] Severity: **S4** _- Affects aesthetics, professional look and feel, “quality” or “usability”._
",1.0,"Wrong Tax calculation on Creditmemo (under certain circumstances) -
### Preconditions (*)
1. 2.4.3
2. Create Creditmemo in Backend
3. Sometimes they can not be displayed as there is an Exception in the template (see below)
### Steps to reproduce (*)
1. Hard to reproduce, anyhow: If you have mainly zero tax articles and create creditmemos they can not be displayed (Exception in the template), if the order with the same ID as the creditmemo contains articles with taxes.
### Expected result (*)
1. Creditmemos can all be displayed correctly
### Actual result (*)
1. Exception thrown in magento/module-sales/view/adminhtml/templates/order/totals/tax.phtml:62 (trying to access method on array)
---
Please provide [Severity](https://devdocs.magento.com/guides/v2.4/contributor-guide/contributing.html#backlog) assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.
- [ ] Severity: **S0** _- Affects critical data or functionality and leaves users without workaround._
- [x] Severity: **S1** _- Affects critical data or functionality and forces users to employ a workaround._
- [ ] Severity: **S2** _- Affects non-critical data or functionality and forces users to employ a workaround._
- [ ] Severity: **S3** _- Affects non-critical data or functionality and does not force users to employ a workaround._
- [ ] Severity: **S4** _- Affects aesthetics, professional look and feel, “quality” or “usability”._
",0,wrong tax calculation on creditmemo under certain circumstances please review our guidelines before adding a new issue fields marked with are required please don t remove the template preconditions provide the exact magento version example and any important information on the environment where bug is reproducible create creditmemo in backend sometimes they can not be displayed as there is an exception in the template see below steps to reproduce important provide a set of clear steps to reproduce this bug we can not provide support without clear instructions on how to reproduce hard to reproduce anyhow if you have mainly zero tax articles and create creditmemos they can not be displayed exception in the template if the order with the same id as the creditmemo contains articles with taxes expected result creditmemos can all be displayed correctly actual result exception thrown in magento module sales view adminhtml templates order totals tax phtml trying to access method on array please provide assessment for the issue as reporter this information will help during confirmation and issue triage processes severity affects critical data or functionality and leaves users without workaround severity affects critical data or functionality and forces users to employ a workaround severity affects non critical data or functionality and forces users to employ a workaround severity affects non critical data or functionality and does not force users to employ a workaround severity affects aesthetics professional look and feel “quality” or “usability” ,0
491,7023027657.0,IssuesEvent,2017-12-22 13:36:11,magnumripper/JohnTheRipper,https://api.github.com/repos/magnumripper/JohnTheRipper,closed,JtR MinGW builds (seem to) have memory corruptions,bug portability RFC / discussion,"- It is possible to crack using a **native windows [1] build of JtR**.
- But, it is not possible to test it.
- It always fails with heap corruption or bad memory access [2].
### Steps to reproduce
- Build on Windows and run JtR using `--test` or `--test-full` options.
- Real cracking works (at least, I wasn't able to trigger an error).
### Workaround
- Build JtR with memdbg enabled (succeed even a `--test-full=0`).
### System configuration
```
Win> john --list=build-info
Version: 1.8.0-jumbo-1-5448-g17a7687
Build: mingw64 64-bit SSE2-ac
SIMD: SSE2, interleaving: MD4:3 MD5:3 SHA1:1 SHA256:1 SHA512:1
$JOHN is
Format interface version: 14
Max. number of reported tunable costs: 3
Rec file version: REC4
Charset file version: CHR3
CHARSET_MIN: 1 (0x01)
CHARSET_MAX: 255 (0xff)
CHARSET_LENGTH: 24
SALT_HASH_SIZE: 1048576
Max. Markov mode level: 400
Max. Markov mode password length: 30
gcc version: 5.3.0
Crypto library: OpenSSL
OpenSSL library version: 01000207f
OpenSSL 1.0.2g 1 Mar 2016
GMP library version: 6.1.0
File locking: NOT supported by this build - do not run concurrent sessions!
fseek(): fseeko64
ftell(): ftello64
fopen(): fopen64
memmem(): JtR internal
```
### Other information
Seems **NOT** related to:
- #2083
- #2190
****
* [1] I built JtR on someone's else HP Windows 7 notebook and I put JtR in a Windows CI service available online. I built and tested on i686 and x86_64.
* [2] 0xC0000374: STATUS_HEAP_CORRUPTION or 0xC0000005: ""memory access violation"".
****
BTW: printf definitions, e.g. ""LLu"", have problems on 32bits.",True,"JtR MinGW builds (seem to) have memory corruptions - - It is possible to crack using a **native windows [1] build of JtR**.
- But, it is not possible to test it.
- It always fails with heap corruption or bad memory access [2].
### Steps to reproduce
- Build on Windows and run JtR using `--test` or `--test-full` options.
- Real cracking works (at least, I wasn't able to trigger an error).
### Workaround
- Build JtR with memdbg enabled (succeed even a `--test-full=0`).
### System configuration
```
Win> john --list=build-info
Version: 1.8.0-jumbo-1-5448-g17a7687
Build: mingw64 64-bit SSE2-ac
SIMD: SSE2, interleaving: MD4:3 MD5:3 SHA1:1 SHA256:1 SHA512:1
$JOHN is
Format interface version: 14
Max. number of reported tunable costs: 3
Rec file version: REC4
Charset file version: CHR3
CHARSET_MIN: 1 (0x01)
CHARSET_MAX: 255 (0xff)
CHARSET_LENGTH: 24
SALT_HASH_SIZE: 1048576
Max. Markov mode level: 400
Max. Markov mode password length: 30
gcc version: 5.3.0
Crypto library: OpenSSL
OpenSSL library version: 01000207f
OpenSSL 1.0.2g 1 Mar 2016
GMP library version: 6.1.0
File locking: NOT supported by this build - do not run concurrent sessions!
fseek(): fseeko64
ftell(): ftello64
fopen(): fopen64
memmem(): JtR internal
```
### Other information
Seems **NOT** related to:
- #2083
- #2190
****
* [1] I built JtR on someone's else HP Windows 7 notebook and I put JtR in a Windows CI service available online. I built and tested on i686 and x86_64.
* [2] 0xC0000374: STATUS_HEAP_CORRUPTION or 0xC0000005: ""memory access violation"".
****
BTW: printf definitions, e.g. ""LLu"", have problems on 32bits.",1,jtr mingw builds seem to have memory corruptions it is possible to crack using a native windows build of jtr but it is not possible to test it it always fails with heap corruption or bad memory access steps to reproduce build on windows and run jtr using test or test full options real cracking works at least i wasn t able to trigger an error workaround build jtr with memdbg enabled succeed even a test full system configuration win john list build info version jumbo build bit ac simd interleaving john is format interface version max number of reported tunable costs rec file version charset file version charset min charset max charset length salt hash size max markov mode level max markov mode password length gcc version crypto library openssl openssl library version openssl mar gmp library version file locking not supported by this build do not run concurrent sessions fseek ftell fopen memmem jtr internal other information seems not related to i built jtr on someone s else hp windows notebook and i put jtr in a windows ci service available online i built and tested on and status heap corruption or memory access violation btw printf definitions e g llu have problems on ,1
523,7374251975.0,IssuesEvent,2018-03-13 19:44:53,nasa/multipath-tcp-tools,https://api.github.com/repos/nasa/multipath-tcp-tools,closed,Compilation issues,bug portability,"I had to do the following change through the project to make it compile:
```
- tcp_header_length = ((tcp_header->th_off & 0xf0 >> 4) * 4);
+ tcp_header_length = ((tcp_header->doff & 0xf0 >> 4) * 4);
```
It's probably because on your system you have ```__FAVOR_BSD``` set, because ```netinet/tcp.h``` does:
```
# ifdef __FAVOR_BSD
[...]
```
I think you could probably fix that issue by defining ```__FAVOR_BSD``` in the Makefile.",True,"Compilation issues - I had to do the following change through the project to make it compile:
```
- tcp_header_length = ((tcp_header->th_off & 0xf0 >> 4) * 4);
+ tcp_header_length = ((tcp_header->doff & 0xf0 >> 4) * 4);
```
It's probably because on your system you have ```__FAVOR_BSD``` set, because ```netinet/tcp.h``` does:
```
# ifdef __FAVOR_BSD
[...]
```
I think you could probably fix that issue by defining ```__FAVOR_BSD``` in the Makefile.",1,compilation issues i had to do the following change through the project to make it compile tcp header length tcp header th off tcp header length tcp header doff it s probably because on your system you have favor bsd set because netinet tcp h does ifdef favor bsd i think you could probably fix that issue by defining favor bsd in the makefile ,1
724445,24931089373.0,IssuesEvent,2022-10-31 11:41:10,hoffstadt/DearPyGui,https://api.github.com/repos/hoffstadt/DearPyGui,closed,"Window background color not working if ""modal=True""",priority: low state: pending type: bug,"## Version of Dear PyGui
Version: 1.40
Operating System: Win11
## My Issue/Question
If a window is set to be modal, the binded theme to set background color is not working.
## To Reproduce
Steps to reproduce the behavior:
1. Run the minimal example
2. Change modal=False
3. Run the minimal example again
## Expected behavior
Run the minimal example, the background color of About windows is not black.
Change modal to False in the windows setting.
Run again, and background color is now black.
## Standalone, minimal, complete and verifiable example
```python
import dearpygui.dearpygui as dpg
dpg.create_context()
dpg.create_viewport()
dpg.setup_dearpygui()
with dpg.theme() as themeWinBgBlack:
with dpg.theme_component(dpg.mvAll):
dpg.add_theme_color(dpg.mvThemeCol_WindowBg, [0,0,0])
with dpg.window(label=""About"", modal=True) as winMenuAbout:
dpg.add_text(""test"")
dpg.bind_item_theme(winMenuAbout, themeWinBgBlack)
dpg.show_viewport()
dpg.start_dearpygui()
dpg.destroy_context()
```
",1.0,"Window background color not working if ""modal=True"" - ## Version of Dear PyGui
Version: 1.40
Operating System: Win11
## My Issue/Question
If a window is set to be modal, the binded theme to set background color is not working.
## To Reproduce
Steps to reproduce the behavior:
1. Run the minimal example
2. Change modal=False
3. Run the minimal example again
## Expected behavior
Run the minimal example, the background color of About windows is not black.
Change modal to False in the windows setting.
Run again, and background color is now black.
## Standalone, minimal, complete and verifiable example
```python
import dearpygui.dearpygui as dpg
dpg.create_context()
dpg.create_viewport()
dpg.setup_dearpygui()
with dpg.theme() as themeWinBgBlack:
with dpg.theme_component(dpg.mvAll):
dpg.add_theme_color(dpg.mvThemeCol_WindowBg, [0,0,0])
with dpg.window(label=""About"", modal=True) as winMenuAbout:
dpg.add_text(""test"")
dpg.bind_item_theme(winMenuAbout, themeWinBgBlack)
dpg.show_viewport()
dpg.start_dearpygui()
dpg.destroy_context()
```
",0,window background color not working if modal true version of dear pygui version operating system my issue question if a window is set to be modal the binded theme to set background color is not working to reproduce steps to reproduce the behavior run the minimal example change modal false run the minimal example again expected behavior run the minimal example the background color of about windows is not black change modal to false in the windows setting run again and background color is now black standalone minimal complete and verifiable example python import dearpygui dearpygui as dpg dpg create context dpg create viewport dpg setup dearpygui with dpg theme as themewinbgblack with dpg theme component dpg mvall dpg add theme color dpg mvthemecol windowbg with dpg window label about modal true as winmenuabout dpg add text test dpg bind item theme winmenuabout themewinbgblack dpg show viewport dpg start dearpygui dpg destroy context ,0
83898,3644692607.0,IssuesEvent,2016-02-15 11:06:01,MinetestForFun/server-minetestforfun-skyblock,https://api.github.com/repos/MinetestForFun/server-minetestforfun-skyblock,closed,Protector bug,Modding ➤ BugFix Priority: High,"This only applies to the normal protector logo, not the blocks or the 3x protectors, just the normal protector logos(protector:protect2).
Logos currently **cannot** be removed. When attempting to dig them an ""Unknown Object"" texture appears next to it and the logo remains.
I copied this error from the server log right after i found this bug:
2016-02-12 21:41:41: ERROR[ServerThread]: LuaEntity name ""protector:display"" not defined
:small_orange_diamond:",1.0,"Protector bug - This only applies to the normal protector logo, not the blocks or the 3x protectors, just the normal protector logos(protector:protect2).
Logos currently **cannot** be removed. When attempting to dig them an ""Unknown Object"" texture appears next to it and the logo remains.
I copied this error from the server log right after i found this bug:
2016-02-12 21:41:41: ERROR[ServerThread]: LuaEntity name ""protector:display"" not defined
:small_orange_diamond:",0,protector bug this only applies to the normal protector logo not the blocks or the protectors just the normal protector logos protector logos currently cannot be removed when attempting to dig them an unknown object texture appears next to it and the logo remains i copied this error from the server log right after i found this bug error luaentity name protector display not defined small orange diamond ,0
232562,7661533622.0,IssuesEvent,2018-05-11 14:32:06,diwg/cf2,https://api.github.com/repos/diwg/cf2,closed,Suggestions for Types proposal,Medium Priority Types,"Daniel,
Here are my initial suggestions for the Types proposal. If you find they have merit, please craft the replacement language yourself as I am short on time this week:
1. List NC_UBYTE among the new atomic types
2. This statement
> enum types may be used, but only if they resolve to an atomic external type at the end.
needs elaboration. I think that netCDF4 library ensures that the base type of an enum must be an integer. If so, then the statement is redundant, since all integer types are valid base types. What does ""at the end"" add to the sentence? Since the base type must be an integer, there can be no recursive ENUM variables (yes?).
3. It's unclear why you narrow the proposal down to just adding ENUM, not VLEN, COMPOUND, or OPAQUE. This means the Types proposal is in effect a proposal to allow ENUM and STRING types (so should the name be changed?), because the integer types are covered by my CF1 proposal which languishes in limbo but will probably be adopted eventually (and does anyone recall another CF1 proposal to allow STRING?) . Please add rationale and/or explanation why the proposal is narrow, since adoptees will likely want to understand this proposal in the context of previous and potential future proposals related to types.",1.0,"Suggestions for Types proposal - Daniel,
Here are my initial suggestions for the Types proposal. If you find they have merit, please craft the replacement language yourself as I am short on time this week:
1. List NC_UBYTE among the new atomic types
2. This statement
> enum types may be used, but only if they resolve to an atomic external type at the end.
needs elaboration. I think that netCDF4 library ensures that the base type of an enum must be an integer. If so, then the statement is redundant, since all integer types are valid base types. What does ""at the end"" add to the sentence? Since the base type must be an integer, there can be no recursive ENUM variables (yes?).
3. It's unclear why you narrow the proposal down to just adding ENUM, not VLEN, COMPOUND, or OPAQUE. This means the Types proposal is in effect a proposal to allow ENUM and STRING types (so should the name be changed?), because the integer types are covered by my CF1 proposal which languishes in limbo but will probably be adopted eventually (and does anyone recall another CF1 proposal to allow STRING?) . Please add rationale and/or explanation why the proposal is narrow, since adoptees will likely want to understand this proposal in the context of previous and potential future proposals related to types.",0,suggestions for types proposal daniel here are my initial suggestions for the types proposal if you find they have merit please craft the replacement language yourself as i am short on time this week list nc ubyte among the new atomic types this statement enum types may be used but only if they resolve to an atomic external type at the end needs elaboration i think that library ensures that the base type of an enum must be an integer if so then the statement is redundant since all integer types are valid base types what does at the end add to the sentence since the base type must be an integer there can be no recursive enum variables yes it s unclear why you narrow the proposal down to just adding enum not vlen compound or opaque this means the types proposal is in effect a proposal to allow enum and string types so should the name be changed because the integer types are covered by my proposal which languishes in limbo but will probably be adopted eventually and does anyone recall another proposal to allow string please add rationale and or explanation why the proposal is narrow since adoptees will likely want to understand this proposal in the context of previous and potential future proposals related to types ,0
716,9634809787.0,IssuesEvent,2019-05-15 22:23:20,Azure/azure-functions-host,https://api.github.com/repos/Azure/azure-functions-host,closed,Shutdown functions host if there is no language worker,Supportability,"If starting language worker fails including retries, need to shutdown functions host. This is required to avoid invocation failures on a functions host without language worker.",True,"Shutdown functions host if there is no language worker - If starting language worker fails including retries, need to shutdown functions host. This is required to avoid invocation failures on a functions host without language worker.",1,shutdown functions host if there is no language worker if starting language worker fails including retries need to shutdown functions host this is required to avoid invocation failures on a functions host without language worker ,1
1989,32009241107.0,IssuesEvent,2023-09-21 16:47:36,thorvg/thorvg,https://api.github.com/repos/thorvg/thorvg,closed,cross compile on mcu,Ideas invalid portability,"I would like to port thorvg to my microcontroller board, which features a Cortex-M33 core and runs FreeRTOS. I've noticed that Thorvg relies on C++14, which isn't very friendly for microcontroller platforms due to its usage of certain C++ features like concurrency-related APIs. Do you happen to know if there are any plans to decouple these codes and transition to an operating system adaptation layer instead?",True,"cross compile on mcu - I would like to port thorvg to my microcontroller board, which features a Cortex-M33 core and runs FreeRTOS. I've noticed that Thorvg relies on C++14, which isn't very friendly for microcontroller platforms due to its usage of certain C++ features like concurrency-related APIs. Do you happen to know if there are any plans to decouple these codes and transition to an operating system adaptation layer instead?",1,cross compile on mcu i would like to port thorvg to my microcontroller board which features a cortex core and runs freertos i ve noticed that thorvg relies on c which isn t very friendly for microcontroller platforms due to its usage of certain c features like concurrency related apis do you happen to know if there are any plans to decouple these codes and transition to an operating system adaptation layer instead ,1
1799,26532591268.0,IssuesEvent,2023-01-19 13:35:13,microsoft/vscode,https://api.github.com/repos/microsoft/vscode,closed,Doing `code ` from integrated terminal in portable mode uses wrong user data,bug terminal portable-mode author-verification-requested,"Does this issue occur when all extensions are disabled?: No
- VS Code Version: 1.74.2
- OS Version: Arch with Linux v6.1.3
Steps to Reproduce:
1. Open VS Code in portable mode (VSCODE_PORTABLE env var set to a directory)
2. Open a file in the instance by typing `code ` in the integrated terminal.
3. VS Code opens a new window rather than opening the file as a tab, and the new window reads userdata from `~/.vscode` instead of ""$VSCODE_PORTABLE"".
Possible solution:
I investigated and noticed that the integrated terminal in VS Code reads the `VSCODE_PORTABLE` env var as unset even if it is set by the OS. As a workaround, I have added this to my config, and it works:
```
""terminal.integrated.env.linux"": { ""VSCODE_PORTABLE"": ""${env:VSCODE_PORTABLE}"" },
```
",True,"Doing `code ` from integrated terminal in portable mode uses wrong user data - Does this issue occur when all extensions are disabled?: No
- VS Code Version: 1.74.2
- OS Version: Arch with Linux v6.1.3
Steps to Reproduce:
1. Open VS Code in portable mode (VSCODE_PORTABLE env var set to a directory)
2. Open a file in the instance by typing `code ` in the integrated terminal.
3. VS Code opens a new window rather than opening the file as a tab, and the new window reads userdata from `~/.vscode` instead of ""$VSCODE_PORTABLE"".
Possible solution:
I investigated and noticed that the integrated terminal in VS Code reads the `VSCODE_PORTABLE` env var as unset even if it is set by the OS. As a workaround, I have added this to my config, and it works:
```
""terminal.integrated.env.linux"": { ""VSCODE_PORTABLE"": ""${env:VSCODE_PORTABLE}"" },
```
",1,doing code from integrated terminal in portable mode uses wrong user data does this issue occur when all extensions are disabled no report issue dialog can assist with this vs code version os version arch with linux steps to reproduce open vs code in portable mode vscode portable env var set to a directory open a file in the instance by typing code in the integrated terminal vs code opens a new window rather than opening the file as a tab and the new window reads userdata from vscode instead of vscode portable possible solution i investigated and noticed that the integrated terminal in vs code reads the vscode portable env var as unset even if it is set by the os as a workaround i have added this to my config and it works terminal integrated env linux vscode portable env vscode portable ,1
49524,12369550692.0,IssuesEvent,2020-05-18 15:25:07,tensorflow/tensorflow,https://api.github.com/repos/tensorflow/tensorflow,opened,Tensorflow containers are missing from Docker Hub,type:build/install,"Your docker pages point at
https://hub.docker.com/r/tensorflow/tensorflow
Today that returns ""404"" Oops! Page not found.",1.0,"Tensorflow containers are missing from Docker Hub - Your docker pages point at
https://hub.docker.com/r/tensorflow/tensorflow
Today that returns ""404"" Oops! Page not found.",0,tensorflow containers are missing from docker hub your docker pages point at today that returns oops page not found ,0
726074,24987140682.0,IssuesEvent,2022-11-02 15:50:31,bcgov/entity,https://api.github.com/repos/bcgov/entity,closed, Message Error when Registering a DBA / Oct 24 2022/ SP GP Business Registry,bug Priority1 ENTITY,"A product team ticket to resolved this Ops ticket - https://app.zenhub.com/workspaces/ops-60f8556e05d25b0011468870/issues/bcgov-registries/ops-support/1583
""I have had two citizens call regarding registering a DBA. They are getting a “no matches found” message when trying to put the corporation in. I’ve asked them to try the registration and business numbers as well as the name, nothing works.""",1.0," Message Error when Registering a DBA / Oct 24 2022/ SP GP Business Registry - A product team ticket to resolved this Ops ticket - https://app.zenhub.com/workspaces/ops-60f8556e05d25b0011468870/issues/bcgov-registries/ops-support/1583
""I have had two citizens call regarding registering a DBA. They are getting a “no matches found” message when trying to put the corporation in. I’ve asked them to try the registration and business numbers as well as the name, nothing works.""",0, message error when registering a dba oct sp gp business registry a product team ticket to resolved this ops ticket i have had two citizens call regarding registering a dba they are getting a “no matches found” message when trying to put the corporation in i’ve asked them to try the registration and business numbers as well as the name nothing works ,0
893,11790687605.0,IssuesEvent,2020-03-17 19:28:10,MicrosoftDocs/sql-docs,https://api.github.com/repos/MicrosoftDocs/sql-docs,closed,Sort Order on Non-Key columns in Index,Pri1 assigned-to-author doc-bug sql/prod supportability/tech,"Under ""Index Sort Order Design Guidelines"" section it was mentioned that SORT order for indexes can be created only on key columns. However, in the Adventure Works example provided, sort order was mentioned on ""RejectedQty"" which is not a key column in the table. Please check this and let me know if I am missing something.
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 20a94499-0b07-2deb-46d6-102e6f1dedac
* Version Independent ID: 324ed645-ed52-6104-9ffd-2907ff315565
* Content: [SQL Server Index Architecture and Design Guide - SQL Server](https://docs.microsoft.com/en-us/sql/relational-databases/sql-server-index-design-guide?view=sql-server-ver15#General_Design)
* Content Source: [docs/relational-databases/sql-server-index-design-guide.md](https://github.com/MicrosoftDocs/sql-docs/blob/live/docs/relational-databases/sql-server-index-design-guide.md)
* Product: **sql**
* Technology: **supportability**
* GitHub Login: @rothja
* Microsoft Alias: **jroth**",True,"Sort Order on Non-Key columns in Index - Under ""Index Sort Order Design Guidelines"" section it was mentioned that SORT order for indexes can be created only on key columns. However, in the Adventure Works example provided, sort order was mentioned on ""RejectedQty"" which is not a key column in the table. Please check this and let me know if I am missing something.
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 20a94499-0b07-2deb-46d6-102e6f1dedac
* Version Independent ID: 324ed645-ed52-6104-9ffd-2907ff315565
* Content: [SQL Server Index Architecture and Design Guide - SQL Server](https://docs.microsoft.com/en-us/sql/relational-databases/sql-server-index-design-guide?view=sql-server-ver15#General_Design)
* Content Source: [docs/relational-databases/sql-server-index-design-guide.md](https://github.com/MicrosoftDocs/sql-docs/blob/live/docs/relational-databases/sql-server-index-design-guide.md)
* Product: **sql**
* Technology: **supportability**
* GitHub Login: @rothja
* Microsoft Alias: **jroth**",1,sort order on non key columns in index under index sort order design guidelines section it was mentioned that sort order for indexes can be created only on key columns however in the adventure works example provided sort order was mentioned on rejectedqty which is not a key column in the table please check this and let me know if i am missing something document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source product sql technology supportability github login rothja microsoft alias jroth ,1
1282,17147184919.0,IssuesEvent,2021-07-13 15:47:07,ocaml/opam,https://api.github.com/repos/ocaml/opam,closed,Can't upgrade to Opam 2.0 on Windows 10/Cygwin64,AREA: PORTABILITY,"I've been trying various ways to upgrade from 1.2.2 to 2.0 following the instructions at https://opam.ocaml.org/blog/opam-2-0-0/ without success. They all seem to fail:
1. `sh <(curl -sL https://raw.githubusercontent.com/ocaml/opam/master/shell/install.sh)` says to download the Opam source, then run `make cold`, which dies after a few thousand lines of output with:
```
'/cygdrive/c/opam/opam-2.0.3/bootstrap/ocaml/bin/ocamldep.opt' -modules src/which_program/which_program.boot.ml > boot-depends.txt
'/cygdrive/c/opam/opam-2.0.3/bootstrap/ocaml/bin/ocamldep.opt' -modules src/xdg/xdg.ml > boot-depends.txt
'/cygdrive/c/opam/opam-2.0.3/bootstrap/ocaml/bin/ocamllex.opt' -q src/let-syntax/lexer.mll
'/cygdrive/c/opam/opam-2.0.3/bootstrap/ocaml/bin/ocamlc.opt' -g -w -40 -o boot.exe unix.cma boot.ml
1 [main] ocamlrun 16520 child_info_fork::abort: address space needed by 'dllunix.so' (0x400000) is already occupied
Error: fork: : Resource temporarily unavailable
```
2. Similarly `opam update; opam install opam-devel` dies while installing jbuilder:
```
#=== ERROR while installing jbuilder.1.0+beta20 ===============================#
# opam-version 1.2.2
# os cygwin
# command ./boot.exe -j 4
# path /home/Jim/.opam/4.06.1/build/jbuilder.1.0+beta20
# compiler 4.06.1
# exit-code 1
# env-file /home/Jim/.opam/4.06.1/build/jbuilder.1.0+beta20/jbuilder-5052-e0259d.env
# stdout-file /home/Jim/.opam/4.06.1/build/jbuilder.1.0+beta20/jbuilder-5052-e0259d.out
# stderr-file /home/Jim/.opam/4.06.1/build/jbuilder.1.0+beta20/jbuilder-5052-e0259d.err
### stderr ###
# 1 [main] ocamlrun 5124 child_info_fork::abort: address space needed by 'dllunix.so' (0x420000) is already occupied
# Error: fork: : Resource temporarily unavailable
```
Rebooting doesn't help.
This issue appears similar to https://github.com/ocaml/opam/issues/3503, but I'm able to compile many, many files with OCaml.
I saw this suggestion in https://github.com/ocaml/opam/issues/2276 for Cygwin32. Perhaps there an equivalent for Cygwin64?
```
rebase -b 0x7cd20000 ./.opam/4.02.3/lib/ocaml/stublibs/dllunix.so
rebase -b 0x7cdc0000 ./.opam/4.02.3/lib/ocaml/stublibs/dllthreads.so
```
Should I update to the latest cygwin? Timestamps suggest I installed in on 11/24/17.
```
$ opam config report
# OPAM config report
# opam-version 1.2.2
# self-upgrade no
# os cygwin
# external-solver no
# criteria -removed,-notuptodate,-changed
# jobs 4
# repositories 1 (http)
# pinned 0
# current-switch 4.06.1
# last-update 2019-03-16 07:58
```
",True,"Can't upgrade to Opam 2.0 on Windows 10/Cygwin64 - I've been trying various ways to upgrade from 1.2.2 to 2.0 following the instructions at https://opam.ocaml.org/blog/opam-2-0-0/ without success. They all seem to fail:
1. `sh <(curl -sL https://raw.githubusercontent.com/ocaml/opam/master/shell/install.sh)` says to download the Opam source, then run `make cold`, which dies after a few thousand lines of output with:
```
'/cygdrive/c/opam/opam-2.0.3/bootstrap/ocaml/bin/ocamldep.opt' -modules src/which_program/which_program.boot.ml > boot-depends.txt
'/cygdrive/c/opam/opam-2.0.3/bootstrap/ocaml/bin/ocamldep.opt' -modules src/xdg/xdg.ml > boot-depends.txt
'/cygdrive/c/opam/opam-2.0.3/bootstrap/ocaml/bin/ocamllex.opt' -q src/let-syntax/lexer.mll
'/cygdrive/c/opam/opam-2.0.3/bootstrap/ocaml/bin/ocamlc.opt' -g -w -40 -o boot.exe unix.cma boot.ml
1 [main] ocamlrun 16520 child_info_fork::abort: address space needed by 'dllunix.so' (0x400000) is already occupied
Error: fork: : Resource temporarily unavailable
```
2. Similarly `opam update; opam install opam-devel` dies while installing jbuilder:
```
#=== ERROR while installing jbuilder.1.0+beta20 ===============================#
# opam-version 1.2.2
# os cygwin
# command ./boot.exe -j 4
# path /home/Jim/.opam/4.06.1/build/jbuilder.1.0+beta20
# compiler 4.06.1
# exit-code 1
# env-file /home/Jim/.opam/4.06.1/build/jbuilder.1.0+beta20/jbuilder-5052-e0259d.env
# stdout-file /home/Jim/.opam/4.06.1/build/jbuilder.1.0+beta20/jbuilder-5052-e0259d.out
# stderr-file /home/Jim/.opam/4.06.1/build/jbuilder.1.0+beta20/jbuilder-5052-e0259d.err
### stderr ###
# 1 [main] ocamlrun 5124 child_info_fork::abort: address space needed by 'dllunix.so' (0x420000) is already occupied
# Error: fork: : Resource temporarily unavailable
```
Rebooting doesn't help.
This issue appears similar to https://github.com/ocaml/opam/issues/3503, but I'm able to compile many, many files with OCaml.
I saw this suggestion in https://github.com/ocaml/opam/issues/2276 for Cygwin32. Perhaps there an equivalent for Cygwin64?
```
rebase -b 0x7cd20000 ./.opam/4.02.3/lib/ocaml/stublibs/dllunix.so
rebase -b 0x7cdc0000 ./.opam/4.02.3/lib/ocaml/stublibs/dllthreads.so
```
Should I update to the latest cygwin? Timestamps suggest I installed in on 11/24/17.
```
$ opam config report
# OPAM config report
# opam-version 1.2.2
# self-upgrade no
# os cygwin
# external-solver no
# criteria -removed,-notuptodate,-changed
# jobs 4
# repositories 1 (http)
# pinned 0
# current-switch 4.06.1
# last-update 2019-03-16 07:58
```
",1,can t upgrade to opam on windows i ve been trying various ways to upgrade from to following the instructions at without success they all seem to fail sh curl sl says to download the opam source then run make cold which dies after a few thousand lines of output with cygdrive c opam opam bootstrap ocaml bin ocamldep opt modules src which program which program boot ml boot depends txt cygdrive c opam opam bootstrap ocaml bin ocamldep opt modules src xdg xdg ml boot depends txt cygdrive c opam opam bootstrap ocaml bin ocamllex opt q src let syntax lexer mll cygdrive c opam opam bootstrap ocaml bin ocamlc opt g w o boot exe unix cma boot ml ocamlrun child info fork abort address space needed by dllunix so is already occupied error fork resource temporarily unavailable similarly opam update opam install opam devel dies while installing jbuilder error while installing jbuilder opam version os cygwin command boot exe j path home jim opam build jbuilder compiler exit code env file home jim opam build jbuilder jbuilder env stdout file home jim opam build jbuilder jbuilder out stderr file home jim opam build jbuilder jbuilder err stderr ocamlrun child info fork abort address space needed by dllunix so is already occupied error fork resource temporarily unavailable rebooting doesn t help this issue appears similar to but i m able to compile many many files with ocaml i saw this suggestion in for perhaps there an equivalent for rebase b opam lib ocaml stublibs dllunix so rebase b opam lib ocaml stublibs dllthreads so should i update to the latest cygwin timestamps suggest i installed in on opam config report opam config report opam version self upgrade no os cygwin external solver no criteria removed notuptodate changed jobs repositories http pinned current switch last update ,1
1361,19512302688.0,IssuesEvent,2021-12-29 01:50:42,lkrg-org/lkrg,https://api.github.com/repos/lkrg-org/lkrg,closed,Build on RHEL7 broken,portability,"Build on RHEL7 is broken in two ways:
1. ff5ca9630057e2c1d3856a8674afac9bf6a9b1d3 apparently requires GCC 7+, and RHEL7 by default has older.
2. c6d93ae9df2519a66a6d5ec9e226f8458c51815c assumes the kernel has `READ_ONCE`, but older kernels did not. They had `ACCESS_ONCE` instead: https://lwn.net/Articles/624126/
I'm testing fixes for these.",True,"Build on RHEL7 broken - Build on RHEL7 is broken in two ways:
1. ff5ca9630057e2c1d3856a8674afac9bf6a9b1d3 apparently requires GCC 7+, and RHEL7 by default has older.
2. c6d93ae9df2519a66a6d5ec9e226f8458c51815c assumes the kernel has `READ_ONCE`, but older kernels did not. They had `ACCESS_ONCE` instead: https://lwn.net/Articles/624126/
I'm testing fixes for these.",1,build on broken build on is broken in two ways apparently requires gcc and by default has older assumes the kernel has read once but older kernels did not they had access once instead i m testing fixes for these ,1
183386,21721724193.0,IssuesEvent,2022-05-11 01:20:15,raindigi/reaction,https://api.github.com/repos/raindigi/reaction,closed,CVE-2021-29060 (Medium) detected in color-string-1.5.3.tgz - autoclosed,security vulnerability,"## CVE-2021-29060 - Medium Severity Vulnerability
Vulnerable Library - color-string-1.5.3.tgz
Parser and generator for CSS color strings
Library home page: https://registry.npmjs.org/color-string/-/color-string-1.5.3.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/color-string/package.json
Dependency Hierarchy:
- sharp-0.20.5.tgz (Root Library)
- color-3.1.0.tgz
- :x: **color-string-1.5.3.tgz** (Vulnerable Library)
Found in HEAD commit: c3f5e6b9d647cd1f977b184ae9c079f1ae297353
Vulnerability Details
A Regular Expression Denial of Service (ReDOS) vulnerability was discovered in Color-String version 1.5.5 and below which occurs when the application is provided and checks a crafted invalid HWB string.
Publish Date: 2021-06-21
URL: CVE-2021-29060
CVSS 3 Score Details (5.3)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://github.com/advisories/GHSA-257v-vj4p-3w2h
Release Date: 2021-06-21
Fix Resolution: color-string - 1.5.5
Vulnerable Library - color-string-1.5.3.tgz
Parser and generator for CSS color strings
Library home page: https://registry.npmjs.org/color-string/-/color-string-1.5.3.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/color-string/package.json
Dependency Hierarchy:
- sharp-0.20.5.tgz (Root Library)
- color-3.1.0.tgz
- :x: **color-string-1.5.3.tgz** (Vulnerable Library)
Found in HEAD commit: c3f5e6b9d647cd1f977b184ae9c079f1ae297353
Vulnerability Details
A Regular Expression Denial of Service (ReDOS) vulnerability was discovered in Color-String version 1.5.5 and below which occurs when the application is provided and checks a crafted invalid HWB string.
Publish Date: 2021-06-21
URL: CVE-2021-29060
CVSS 3 Score Details (5.3)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://github.com/advisories/GHSA-257v-vj4p-3w2h
Release Date: 2021-06-21
Fix Resolution: color-string - 1.5.5
Vulnerable Library - linux-stable-rtv4.1.33
Julia Cartwright's fork of linux-stable-rt.git
Library home page: https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git
Found in HEAD commit: 00db4e8795bcbec692fb60b19160bdd763ad42e3
Found in base branch: master
Vulnerable Source Files (1)
/drivers/staging/rtl8188eu/os_dep/ioctl_linux.c
Vulnerability Details
rtw_wx_set_scan in drivers/staging/rtl8188eu/os_dep/ioctl_linux.c in the Linux kernel through 5.11.6 allows writing beyond the end of the ->ssid[] array. NOTE: from the perspective of kernel.org releases, CVE IDs are not normally used for drivers/staging/* (unfinished work); however, system integrators may have situations in which a drivers/staging issue is relevant to their own customer base.
Publish Date: 2021-03-17
URL: CVE-2021-28660
CVSS 3 Score Details (7.8)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://www.linuxkernelcves.com/cves/CVE-2021-28660
Release Date: 2021-03-17
Fix Resolution: v4.4.262,v4.9.262,v4.14.226,v4.19.181,v5.4.106,v5.10.24,v5.11.7,v5.12-rc3
Vulnerable Library - linux-stable-rtv4.1.33
Julia Cartwright's fork of linux-stable-rt.git
Library home page: https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git
Found in HEAD commit: 00db4e8795bcbec692fb60b19160bdd763ad42e3
Found in base branch: master
Vulnerable Source Files (1)
/drivers/staging/rtl8188eu/os_dep/ioctl_linux.c
Vulnerability Details
rtw_wx_set_scan in drivers/staging/rtl8188eu/os_dep/ioctl_linux.c in the Linux kernel through 5.11.6 allows writing beyond the end of the ->ssid[] array. NOTE: from the perspective of kernel.org releases, CVE IDs are not normally used for drivers/staging/* (unfinished work); however, system integrators may have situations in which a drivers/staging issue is relevant to their own customer base.
Publish Date: 2021-03-17
URL: CVE-2021-28660
CVSS 3 Score Details (7.8)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://www.linuxkernelcves.com/cves/CVE-2021-28660
Release Date: 2021-03-17
Fix Resolution: v4.4.262,v4.9.262,v4.14.226,v4.19.181,v5.4.106,v5.10.24,v5.11.7,v5.12-rc3
More
Artifacts: [/sqlsmith/setup=seed/setting=no-ddl](https://teamcity.cockroachdb.com/viewLog.html?buildId=2143445&tab=artifacts#/sqlsmith/setup=seed/setting=no-ddl)
Related:
- #51313 roachtest: sqlsmith/setup=seed/setting=no-ddl failed [C-test-failure](https://api.github.com/repos/cockroachdb/cockroach/labels/C-test-failure) [O-roachtest](https://api.github.com/repos/cockroachdb/cockroach/labels/O-roachtest) [O-robot](https://api.github.com/repos/cockroachdb/cockroach/labels/O-robot) [branch-provisional_202007081918_v20.2.0-alpha.2](https://api.github.com/repos/cockroachdb/cockroach/labels/branch-provisional_202007081918_v20.2.0-alpha.2) [release-blocker](https://api.github.com/repos/cockroachdb/cockroach/labels/release-blocker)
- #48269 roachtest: sqlsmith/setup=seed/setting=no-ddl failed [C-test-failure](https://api.github.com/repos/cockroachdb/cockroach/labels/C-test-failure) [O-roachtest](https://api.github.com/repos/cockroachdb/cockroach/labels/O-roachtest) [O-robot](https://api.github.com/repos/cockroachdb/cockroach/labels/O-robot) [branch-master](https://api.github.com/repos/cockroachdb/cockroach/labels/branch-master) [release-blocker](https://api.github.com/repos/cockroachdb/cockroach/labels/release-blocker)
[See this test on roachdash](https://roachdash.crdb.dev/?filter=status%3Aopen+t%3A.%2Asqlsmith%2Fsetup%3Dseed%2Fsetting%3Dno-ddl.%2A&sort=title&restgroup=false&display=lastcommented+project)
powered by [pkg/cmd/internal/issues](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
More
Artifacts: [/sqlsmith/setup=seed/setting=no-ddl](https://teamcity.cockroachdb.com/viewLog.html?buildId=2143445&tab=artifacts#/sqlsmith/setup=seed/setting=no-ddl)
Related:
- #51313 roachtest: sqlsmith/setup=seed/setting=no-ddl failed [C-test-failure](https://api.github.com/repos/cockroachdb/cockroach/labels/C-test-failure) [O-roachtest](https://api.github.com/repos/cockroachdb/cockroach/labels/O-roachtest) [O-robot](https://api.github.com/repos/cockroachdb/cockroach/labels/O-robot) [branch-provisional_202007081918_v20.2.0-alpha.2](https://api.github.com/repos/cockroachdb/cockroach/labels/branch-provisional_202007081918_v20.2.0-alpha.2) [release-blocker](https://api.github.com/repos/cockroachdb/cockroach/labels/release-blocker)
- #48269 roachtest: sqlsmith/setup=seed/setting=no-ddl failed [C-test-failure](https://api.github.com/repos/cockroachdb/cockroach/labels/C-test-failure) [O-roachtest](https://api.github.com/repos/cockroachdb/cockroach/labels/O-roachtest) [O-robot](https://api.github.com/repos/cockroachdb/cockroach/labels/O-robot) [branch-master](https://api.github.com/repos/cockroachdb/cockroach/labels/branch-master) [release-blocker](https://api.github.com/repos/cockroachdb/cockroach/labels/release-blocker)
[See this test on roachdash](https://roachdash.crdb.dev/?filter=status%3Aopen+t%3A.%2Asqlsmith%2Fsetup%3Dseed%2Fsetting%3Dno-ddl.%2A&sort=title&restgroup=false&display=lastcommented+project)
powered by [pkg/cmd/internal/issues](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
![]()
**Expected result:**
![]()
",1.0,"[Категорії page] UI doesn't correspond to the mockup in the light theme - **Environment:** Windows 10 Pro, Google Chrome, version 86.0.4240.183.
**Reproducible:** always.
**Build found:** commit 79f5645
**Preconditions:**
Go to https://horondi-admin-staging.azurewebsites.net
Log into Administrator page as Administrator
**Steps to reproduce:**
Go to 'Категорії' menu item
Check the UI of the page
**Actual result:**
![]()
**Expected result:**
![]()
",0, ui doesn t correspond to the mockup in the light theme environment windows pro google chrome version reproducible always build found commit preconditions go to log into administrator page as administrator steps to reproduce go to категорії menu item check the ui of the page actual result img width alt category main page ui defects src expected result img width alt category page src ,0
621,8390559962.0,IssuesEvent,2018-10-09 12:58:37,systemd/systemd,https://api.github.com/repos/systemd/systemd,closed,"protabled: don't insist on "".raw"" suffix for raw images so strictly",bug 🐛 has-pr ✨ portable,"**systemd version the issue has been seen with**
> 239
**Used distribution**
> Arch
**Expected behaviour you didn't see**
> I have a squashfs image `image.img`. If I mount that at `/tmp/image`, then `sudo /lib/systemd/portablectl inspect /tmp/image` reports metadata fine. I expected `sudo /lib/systemd/portablectl inspect image.img` to work as well.
**Unexpected behaviour you saw**
> The command printed `Failed to inspect image metadata: Wrong medium type`. `portablectl attach` also prints the `Wrong medium type` message.
**Steps to reproduce the problem**
First build a squashfs image that reproduces the problem.
Save the following to `repro.nix`.
```nix
with (import (fetchTarball {
url = ""https://github.com/NixOS/nixpkgs/archive/56b9f6fc8e1c3a4ad10ff7c61e461d7b7e038833.tar.gz"";
sha256 = ""0v5y4wjfxbappsaibw88h7n1flcx7kpvg51mjv3h9m4aa3fn2c8q"";
}) {});
let
imageDir = stdenv.mkDerivation {
name = ""repro-filesystem"";
buildCommand = ''
mkdir -p $out/usr/lib
mkdir -p $out/usr/lib/systemd/system
echo ""PORTABLE_PRETTY_NAME=repro"" > $out/usr/lib/os-release
touch $out/usr/lib/systemd/system/repro.service
'';
};
in
stdenv.mkDerivation {
name = ""repro.img"";
nativeBuildInputs = [ squashfsTools ];
buildInputs = [ imageDir ];
buildCommand =
''
mksquashfs ${imageDir} $out \
-no-fragments \
-processors 1 \
-all-root \
-b 1048576 \
-comp xz \
-Xdict-size 100% \
'';
}
```
Run [`nix build -f repro.nix --out-link repro.img`](https://nixos.org/nix/).
Then:
```
$ file $(realpath repro.img)
/nix/store/cildzy70a6jgk5cq1d3mnbm7bg2q2wxh-repro.img: Squashfs filesystem, little endian, version 4.0, 493 bytes, 7 inodes, blocksize: 1048576 bytes, created: Thu Jan 1 00:00:01 1970
$ mkdir /tmp/repro
$ sudo mount repro.img /tmp/repro
$ sudo /usr/lib/systemd/portablectl inspect /tmp/repro
(Matching unit files with prefix 'repro'.)
Image:
/tmp/repro
Portable Service:
repro
Operating System:
n/a
Unit files:
repro.service
$ sudo /usr/lib/systemd/portablectl inspect ./repro.img
(Matching unit files with prefix 'repro.img'.)
Failed to inspect image metadata: Wrong medium type
```",True,"protabled: don't insist on "".raw"" suffix for raw images so strictly - **systemd version the issue has been seen with**
> 239
**Used distribution**
> Arch
**Expected behaviour you didn't see**
> I have a squashfs image `image.img`. If I mount that at `/tmp/image`, then `sudo /lib/systemd/portablectl inspect /tmp/image` reports metadata fine. I expected `sudo /lib/systemd/portablectl inspect image.img` to work as well.
**Unexpected behaviour you saw**
> The command printed `Failed to inspect image metadata: Wrong medium type`. `portablectl attach` also prints the `Wrong medium type` message.
**Steps to reproduce the problem**
First build a squashfs image that reproduces the problem.
Save the following to `repro.nix`.
```nix
with (import (fetchTarball {
url = ""https://github.com/NixOS/nixpkgs/archive/56b9f6fc8e1c3a4ad10ff7c61e461d7b7e038833.tar.gz"";
sha256 = ""0v5y4wjfxbappsaibw88h7n1flcx7kpvg51mjv3h9m4aa3fn2c8q"";
}) {});
let
imageDir = stdenv.mkDerivation {
name = ""repro-filesystem"";
buildCommand = ''
mkdir -p $out/usr/lib
mkdir -p $out/usr/lib/systemd/system
echo ""PORTABLE_PRETTY_NAME=repro"" > $out/usr/lib/os-release
touch $out/usr/lib/systemd/system/repro.service
'';
};
in
stdenv.mkDerivation {
name = ""repro.img"";
nativeBuildInputs = [ squashfsTools ];
buildInputs = [ imageDir ];
buildCommand =
''
mksquashfs ${imageDir} $out \
-no-fragments \
-processors 1 \
-all-root \
-b 1048576 \
-comp xz \
-Xdict-size 100% \
'';
}
```
Run [`nix build -f repro.nix --out-link repro.img`](https://nixos.org/nix/).
Then:
```
$ file $(realpath repro.img)
/nix/store/cildzy70a6jgk5cq1d3mnbm7bg2q2wxh-repro.img: Squashfs filesystem, little endian, version 4.0, 493 bytes, 7 inodes, blocksize: 1048576 bytes, created: Thu Jan 1 00:00:01 1970
$ mkdir /tmp/repro
$ sudo mount repro.img /tmp/repro
$ sudo /usr/lib/systemd/portablectl inspect /tmp/repro
(Matching unit files with prefix 'repro'.)
Image:
/tmp/repro
Portable Service:
repro
Operating System:
n/a
Unit files:
repro.service
$ sudo /usr/lib/systemd/portablectl inspect ./repro.img
(Matching unit files with prefix 'repro.img'.)
Failed to inspect image metadata: Wrong medium type
```",1,protabled don t insist on raw suffix for raw images so strictly systemd version the issue has been seen with used distribution arch expected behaviour you didn t see i have a squashfs image image img if i mount that at tmp image then sudo lib systemd portablectl inspect tmp image reports metadata fine i expected sudo lib systemd portablectl inspect image img to work as well unexpected behaviour you saw the command printed failed to inspect image metadata wrong medium type portablectl attach also prints the wrong medium type message steps to reproduce the problem first build a squashfs image that reproduces the problem save the following to repro nix nix with import fetchtarball url let imagedir stdenv mkderivation name repro filesystem buildcommand mkdir p out usr lib mkdir p out usr lib systemd system echo portable pretty name repro out usr lib os release touch out usr lib systemd system repro service in stdenv mkderivation name repro img nativebuildinputs buildinputs buildcommand mksquashfs imagedir out no fragments processors all root b comp xz xdict size run then file realpath repro img nix store repro img squashfs filesystem little endian version bytes inodes blocksize bytes created thu jan mkdir tmp repro sudo mount repro img tmp repro sudo usr lib systemd portablectl inspect tmp repro matching unit files with prefix repro image tmp repro portable service repro operating system n a unit files repro service sudo usr lib systemd portablectl inspect repro img matching unit files with prefix repro img failed to inspect image metadata wrong medium type ,1
35198,2789835026.0,IssuesEvent,2015-05-08 21:48:06,google/google-visualization-api-issues,https://api.github.com/repos/google/google-visualization-api-issues,opened,Calendar function with date pull down and select,Priority-Low Type-Enhancement,"Original [issue 242](https://code.google.com/p/google-visualization-api-issues/issues/detail?id=242) created by orwant on 2010-04-01T19:11:24.000Z:
What would you like to see us add to this API?
Google spreadsheet that has a calendar function that sits in a individual
cell allowing date pull down and user date selection. Date chosen will
then show in cell.
What component is this issue related to (PieChart, LineChart, DataTable,
Query, etc)?
*********************************************************
For developers viewing this issue: please click the 'star' icon to be
notified of future changes, and to let us know how many of you are
interested in seeing it resolved.
*********************************************************
",1.0,"Calendar function with date pull down and select - Original [issue 242](https://code.google.com/p/google-visualization-api-issues/issues/detail?id=242) created by orwant on 2010-04-01T19:11:24.000Z:
What would you like to see us add to this API?
Google spreadsheet that has a calendar function that sits in a individual
cell allowing date pull down and user date selection. Date chosen will
then show in cell.
What component is this issue related to (PieChart, LineChart, DataTable,
Query, etc)?
*********************************************************
For developers viewing this issue: please click the 'star' icon to be
notified of future changes, and to let us know how many of you are
interested in seeing it resolved.
*********************************************************
",0,calendar function with date pull down and select original created by orwant on what would you like to see us add to this api google spreadsheet that has a calendar function that sits in a individual cell allowing date pull down and user date selection date chosen will then show in cell what component is this issue related to piechart linechart datatable query etc for developers viewing this issue please click the star icon to be notified of future changes and to let us know how many of you are interested in seeing it resolved ,0
1121,14421913967.0,IssuesEvent,2020-12-05 00:43:26,AzureAD/microsoft-authentication-library-for-dotnet,https://api.github.com/repos/AzureAD/microsoft-authentication-library-for-dotnet,closed,[Bug] Throw a better exception when ROPC is attempted with MSA account,Fixed P2 Supportability bug,"**Which Version of MSAL are you using ?**
4.22
Attempt ROPC, with authority correctly set to `l.m.o/organizations`. Provide an MSA username to the API.
**Expected** an exception explaining the root cause.
Implementation suggestion:
- We could use either the ""domain_name"" from the userrealm call (need to confirm with MSA folks)
- Or the fact that the subsequent call to `GET /FederationMetadata/2007-06/FederationMetadata.xml HTTP/1.1` fails with 406 Not Acceptable.
**Actual** a bad exception which causes developers to think there is a bug in MSAL
---> System.InvalidOperationException: Sequence contains no elements
at System.Linq.ThrowHelper.ThrowNoElementsException()
at System.Linq.Enumerable.First[TSource](IEnumerable`1 source)
at Microsoft.Identity.Client.WsTrust.MexDocument.SetPolicyEndpointAddresses(XContainer mexDocument)
at Microsoft.Identity.Client.WsTrust.MexDocument..ctor(String responseBody)
at Microsoft.Identity.Client.WsTrust.WsTrustWebRequestManager.GetMexDocumentAsync(String federationMetadataUrl, RequestContext requestContext)
at Microsoft.Identity.Client.WsTrust.CommonNonInteractiveHandler.PerformWsTrustMexExchangeAsync(String federationMetadataUrl, String cloudAudienceUrn, UserAuthType userAuthType, String username, SecureString password)
at Microsoft.Identity.Client.Internal.Requests.UsernamePasswordRequest.FetchAssertionFromWsTrustAsync()
at Microsoft.Identity.Client.Internal.Requests.UsernamePasswordRequest.ExecuteAsync(CancellationToken cancellationToken)
at Microsoft.Identity.Client.Internal.Requests.RequestBase.RunAsync(CancellationToken cancellationToken)
at Microsoft.Identity.Client.ApiConfig.Executors.PublicClientExecutor.ExecuteAsync(AcquireTokenCommonParameters commonParameters, AcquireTokenByUsernamePasswordParameters usernamePasswordParameters, CancellationToken cancellationToken)
at Azure.Identity.AbstractAcquireTokenParameterBuilderExtensions.ExecuteAsync[T](AbstractAcquireTokenParameterBuilder`1 builder, Boolean async, CancellationToken cancellationToken)
at Azure.Identity.MsalPublicClient.AcquireTokenByUsernamePasswordAsync(String[] scopes, String username, SecureString password, Boolean async, CancellationToken cancellationToken)
at Azure.Identity.UsernamePasswordCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext, CancellationToken cancellationToken)
--- End of inner exception stack trace ---
",True,"[Bug] Throw a better exception when ROPC is attempted with MSA account - **Which Version of MSAL are you using ?**
4.22
Attempt ROPC, with authority correctly set to `l.m.o/organizations`. Provide an MSA username to the API.
**Expected** an exception explaining the root cause.
Implementation suggestion:
- We could use either the ""domain_name"" from the userrealm call (need to confirm with MSA folks)
- Or the fact that the subsequent call to `GET /FederationMetadata/2007-06/FederationMetadata.xml HTTP/1.1` fails with 406 Not Acceptable.
**Actual** a bad exception which causes developers to think there is a bug in MSAL
---> System.InvalidOperationException: Sequence contains no elements
at System.Linq.ThrowHelper.ThrowNoElementsException()
at System.Linq.Enumerable.First[TSource](IEnumerable`1 source)
at Microsoft.Identity.Client.WsTrust.MexDocument.SetPolicyEndpointAddresses(XContainer mexDocument)
at Microsoft.Identity.Client.WsTrust.MexDocument..ctor(String responseBody)
at Microsoft.Identity.Client.WsTrust.WsTrustWebRequestManager.GetMexDocumentAsync(String federationMetadataUrl, RequestContext requestContext)
at Microsoft.Identity.Client.WsTrust.CommonNonInteractiveHandler.PerformWsTrustMexExchangeAsync(String federationMetadataUrl, String cloudAudienceUrn, UserAuthType userAuthType, String username, SecureString password)
at Microsoft.Identity.Client.Internal.Requests.UsernamePasswordRequest.FetchAssertionFromWsTrustAsync()
at Microsoft.Identity.Client.Internal.Requests.UsernamePasswordRequest.ExecuteAsync(CancellationToken cancellationToken)
at Microsoft.Identity.Client.Internal.Requests.RequestBase.RunAsync(CancellationToken cancellationToken)
at Microsoft.Identity.Client.ApiConfig.Executors.PublicClientExecutor.ExecuteAsync(AcquireTokenCommonParameters commonParameters, AcquireTokenByUsernamePasswordParameters usernamePasswordParameters, CancellationToken cancellationToken)
at Azure.Identity.AbstractAcquireTokenParameterBuilderExtensions.ExecuteAsync[T](AbstractAcquireTokenParameterBuilder`1 builder, Boolean async, CancellationToken cancellationToken)
at Azure.Identity.MsalPublicClient.AcquireTokenByUsernamePasswordAsync(String[] scopes, String username, SecureString password, Boolean async, CancellationToken cancellationToken)
at Azure.Identity.UsernamePasswordCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext, CancellationToken cancellationToken)
--- End of inner exception stack trace ---
",1, throw a better exception when ropc is attempted with msa account which version of msal are you using attempt ropc with authority correctly set to l m o organizations provide an msa username to the api expected an exception explaining the root cause implementation suggestion we could use either the domain name from the userrealm call need to confirm with msa folks or the fact that the subsequent call to get federationmetadata federationmetadata xml http fails with not acceptable actual a bad exception which causes developers to think there is a bug in msal system invalidoperationexception sequence contains no elements at system linq throwhelper thrownoelementsexception at system linq enumerable first ienumerable source at microsoft identity client wstrust mexdocument setpolicyendpointaddresses xcontainer mexdocument at microsoft identity client wstrust mexdocument ctor string responsebody at microsoft identity client wstrust wstrustwebrequestmanager getmexdocumentasync string federationmetadataurl requestcontext requestcontext at microsoft identity client wstrust commonnoninteractivehandler performwstrustmexexchangeasync string federationmetadataurl string cloudaudienceurn userauthtype userauthtype string username securestring password at microsoft identity client internal requests usernamepasswordrequest fetchassertionfromwstrustasync at microsoft identity client internal requests usernamepasswordrequest executeasync cancellationtoken cancellationtoken at microsoft identity client internal requests requestbase runasync cancellationtoken cancellationtoken at microsoft identity client apiconfig executors publicclientexecutor executeasync acquiretokencommonparameters commonparameters acquiretokenbyusernamepasswordparameters usernamepasswordparameters cancellationtoken cancellationtoken at azure identity abstractacquiretokenparameterbuilderextensions executeasync abstractacquiretokenparameterbuilder builder boolean async cancellationtoken cancellationtoken at azure identity msalpublicclient acquiretokenbyusernamepasswordasync string scopes string username securestring password boolean async cancellationtoken cancellationtoken at azure identity usernamepasswordcredential gettokenimplasync boolean async tokenrequestcontext requestcontext cancellationtoken cancellationtoken end of inner exception stack trace ,1
1559,22782815730.0,IssuesEvent,2022-07-08 22:22:42,verilator/verilator,https://api.github.com/repos/verilator/verilator,closed,V3Lexer_pregen.yy.cpp:8665:18: error: out-of-line definition of 'LexerInput' does not match any declaration in 'V3LexerBase'out-of-line definition of 'LexerInput',area: portability resolution: answered,"I am trying to compile verilator on macOS 12.4 Dependencies are installed through macports
```
$ /opt/local/bin/flex --version
flex 2.6.4
$ /opt/local/bin/bison --version
bison (GNU Bison) 3.8.2
```
The compilation fails with the following message:
```
In file included from ../V3ParseLex.cpp:28:
V3Lexer_pregen.yy.cpp:8665:18: error: out-of-line definition of 'LexerInput' does not match any declaration in 'V3LexerBase'
int yyFlexLexer::LexerInput( char* buf, int /* max_size */ )
^~~~~~~~~~
V3Lexer_pregen.yy.cpp:8694:19: error: out-of-line definition of 'LexerOutput' does not match any declaration in 'V3LexerBase'
void yyFlexLexer::LexerOutput( const char* buf, int size )
^~~~~~~~~~~
```
I think this is a flex/bison issue but I'm not sure what went wrong. Please help.
",True,"V3Lexer_pregen.yy.cpp:8665:18: error: out-of-line definition of 'LexerInput' does not match any declaration in 'V3LexerBase'out-of-line definition of 'LexerInput' - I am trying to compile verilator on macOS 12.4 Dependencies are installed through macports
```
$ /opt/local/bin/flex --version
flex 2.6.4
$ /opt/local/bin/bison --version
bison (GNU Bison) 3.8.2
```
The compilation fails with the following message:
```
In file included from ../V3ParseLex.cpp:28:
V3Lexer_pregen.yy.cpp:8665:18: error: out-of-line definition of 'LexerInput' does not match any declaration in 'V3LexerBase'
int yyFlexLexer::LexerInput( char* buf, int /* max_size */ )
^~~~~~~~~~
V3Lexer_pregen.yy.cpp:8694:19: error: out-of-line definition of 'LexerOutput' does not match any declaration in 'V3LexerBase'
void yyFlexLexer::LexerOutput( const char* buf, int size )
^~~~~~~~~~~
```
I think this is a flex/bison issue but I'm not sure what went wrong. Please help.
",1, pregen yy cpp error out of line definition of lexerinput does not match any declaration in out of line definition of lexerinput i am trying to compile verilator on macos dependencies are installed through macports opt local bin flex version flex opt local bin bison version bison gnu bison the compilation fails with the following message in file included from cpp pregen yy cpp error out of line definition of lexerinput does not match any declaration in int yyflexlexer lexerinput char buf int max size pregen yy cpp error out of line definition of lexeroutput does not match any declaration in void yyflexlexer lexeroutput const char buf int size i think this is a flex bison issue but i m not sure what went wrong please help ,1
1036,13220706504.0,IssuesEvent,2020-08-17 12:54:11,argoproj/argo-cd,https://api.github.com/repos/argoproj/argo-cd,closed,Improve error message when excluding https:// from the URL in configmap ,enhancement good first issue type:supportability,"# Summary
URL validation for argocd-server configmap and print a error message that the URL does not contain any protocol prefix.
# Motivation
When configuring Dex config for SSO in the configmap argocd-cm is it required to provide a URL to the ArgoCD instance.
If this URL does not contain explicitly the HTTPS protocol every SSO login attempt will generate a `Failed to query provider ""argocd-server.io/api/dex"": 400 Bad Request: 400 Bad Request` message and in the argocd-server log `time=""2020-08-14T12:19:03Z"" level=info msg=""Initializing OIDC provider (issuer: argocd-server.io/api/dex)""`.
These two log entries are not good enough for debugging what is wrong when in fact it is required that the URL must be formatted like this:
Example
BAD configmap
```
---
kind: ConfigMap
apiVersion: v1
metadata:
labels:
app.kubernetes.io/name: argocd-cm
app.kubernetes.io/part-of: argocd
name: argocd-cm
namespace: argocd
data:
url: argocd-server.io
dex.config: |
logger:
level: debug
format: json
connectors:
- type: saml
name: SAML
id: saml
config:
ssoURL: https://identity-provider/idp/profile/SAML2/POST/SSO
entityIssuer: https://argocd-server.io/api/dex
ca: /opt/cert/ca.pem
usernameAttr: name
emailAttr: email
groupsAttr: groups
```
GOOD configmap
```
---
kind: ConfigMap
apiVersion: v1
metadata:
labels:
app.kubernetes.io/name: argocd-cm
app.kubernetes.io/part-of: argocd
name: argocd-cm
namespace: argocd
data:
url: https://argocd-server.io
dex.config: |
logger:
level: debug
format: json
connectors:
- type: saml
name: SAML
id: saml
config:
ssoURL: https://identity-provider/idp/profile/SAML2/POST/SSO
entityIssuer: https://argocd-server.io/api/dex
ca: /opt/cert/ca.pem
usernameAttr: name
emailAttr: email
groupsAttr: groups
```
# Proposal
When argocd-server loads the configmap `argocd-cm` do a validation of the URL (data.url) provided and check if it has a protocol prefixed or not and log accordingly. ",True,"Improve error message when excluding https:// from the URL in configmap - # Summary
URL validation for argocd-server configmap and print a error message that the URL does not contain any protocol prefix.
# Motivation
When configuring Dex config for SSO in the configmap argocd-cm is it required to provide a URL to the ArgoCD instance.
If this URL does not contain explicitly the HTTPS protocol every SSO login attempt will generate a `Failed to query provider ""argocd-server.io/api/dex"": 400 Bad Request: 400 Bad Request` message and in the argocd-server log `time=""2020-08-14T12:19:03Z"" level=info msg=""Initializing OIDC provider (issuer: argocd-server.io/api/dex)""`.
These two log entries are not good enough for debugging what is wrong when in fact it is required that the URL must be formatted like this:
Example
BAD configmap
```
---
kind: ConfigMap
apiVersion: v1
metadata:
labels:
app.kubernetes.io/name: argocd-cm
app.kubernetes.io/part-of: argocd
name: argocd-cm
namespace: argocd
data:
url: argocd-server.io
dex.config: |
logger:
level: debug
format: json
connectors:
- type: saml
name: SAML
id: saml
config:
ssoURL: https://identity-provider/idp/profile/SAML2/POST/SSO
entityIssuer: https://argocd-server.io/api/dex
ca: /opt/cert/ca.pem
usernameAttr: name
emailAttr: email
groupsAttr: groups
```
GOOD configmap
```
---
kind: ConfigMap
apiVersion: v1
metadata:
labels:
app.kubernetes.io/name: argocd-cm
app.kubernetes.io/part-of: argocd
name: argocd-cm
namespace: argocd
data:
url: https://argocd-server.io
dex.config: |
logger:
level: debug
format: json
connectors:
- type: saml
name: SAML
id: saml
config:
ssoURL: https://identity-provider/idp/profile/SAML2/POST/SSO
entityIssuer: https://argocd-server.io/api/dex
ca: /opt/cert/ca.pem
usernameAttr: name
emailAttr: email
groupsAttr: groups
```
# Proposal
When argocd-server loads the configmap `argocd-cm` do a validation of the URL (data.url) provided and check if it has a protocol prefixed or not and log accordingly. ",1,improve error message when excluding https from the url in configmap summary url validation for argocd server configmap and print a error message that the url does not contain any protocol prefix motivation when configuring dex config for sso in the configmap argocd cm is it required to provide a url to the argocd instance if this url does not contain explicitly the https protocol every sso login attempt will generate a failed to query provider argocd server io api dex bad request bad request message and in the argocd server log time level info msg initializing oidc provider issuer argocd server io api dex these two log entries are not good enough for debugging what is wrong when in fact it is required that the url must be formatted like this example bad configmap kind configmap apiversion metadata labels app kubernetes io name argocd cm app kubernetes io part of argocd name argocd cm namespace argocd data url argocd server io dex config logger level debug format json connectors type saml name saml id saml config ssourl entityissuer ca opt cert ca pem usernameattr name emailattr email groupsattr groups good configmap kind configmap apiversion metadata labels app kubernetes io name argocd cm app kubernetes io part of argocd name argocd cm namespace argocd data url dex config logger level debug format json connectors type saml name saml id saml config ssourl entityissuer ca opt cert ca pem usernameattr name emailattr email groupsattr groups proposal when argocd server loads the configmap argocd cm do a validation of the url data url provided and check if it has a protocol prefixed or not and log accordingly ,1
20450,4544456807.0,IssuesEvent,2016-09-10 18:07:20,harningt/luajson,https://api.github.com/repos/harningt/luajson,opened,Update README to remove non-present functionality,documentation,At least one function is mentioned in the readme that is non-present: isEncodable.,1.0,Update README to remove non-present functionality - At least one function is mentioned in the readme that is non-present: isEncodable.,0,update readme to remove non present functionality at least one function is mentioned in the readme that is non present isencodable ,0
58596,14292097415.0,IssuesEvent,2020-11-24 00:12:19,devtron-labs/devtron,https://api.github.com/repos/devtron-labs/devtron,opened,"CVE-2019-18658 (High) detected in k8s.io/helm/pkg/chartutil-eecf22f77df5f65c823aacd2dbd30ae6c65f186e, k8s.io/helm/pkg/sympath-eecf22f77df5f65c823aacd2dbd30ae6c65f186e",security vulnerability,"## CVE-2019-18658 - High Severity Vulnerability
Vulnerable Libraries - k8s.io/helm/pkg/chartutil-eecf22f77df5f65c823aacd2dbd30ae6c65f186e, k8s.io/helm/pkg/sympath-eecf22f77df5f65c823aacd2dbd30ae6c65f186e
k8s.io/helm/pkg/chartutil-eecf22f77df5f65c823aacd2dbd30ae6c65f186e
The Kubernetes Package Manager
Dependency Hierarchy:
- :x: **k8s.io/helm/pkg/chartutil-eecf22f77df5f65c823aacd2dbd30ae6c65f186e** (Vulnerable Library)
k8s.io/helm/pkg/sympath-eecf22f77df5f65c823aacd2dbd30ae6c65f186e
The Kubernetes Package Manager
Dependency Hierarchy:
- k8s.io/helm/pkg/chartutil-eecf22f77df5f65c823aacd2dbd30ae6c65f186e (Root Library)
- :x: **k8s.io/helm/pkg/sympath-eecf22f77df5f65c823aacd2dbd30ae6c65f186e** (Vulnerable Library)
Found in HEAD commit: f7db3d4b83b1d3b0008f56e9a649b36ed2ae830d
Found in base branch: main
Vulnerability Details
In Helm 2.x before 2.15.2, commands that deal with loading a chart as a directory or packaging a chart provide an opportunity for a maliciously designed chart to include sensitive content such as /etc/passwd, or to execute a denial of service (DoS) via a special file such as /dev/urandom, via symlinks. No version of Tiller is known to be impacted. This is a client-only issue.
Publish Date: 2019-11-12
URL: CVE-2019-18658
CVSS 3 Score Details (9.8)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-18658
Release Date: 2019-11-12
Fix Resolution: v2.15.2
Vulnerable Libraries - k8s.io/helm/pkg/chartutil-eecf22f77df5f65c823aacd2dbd30ae6c65f186e, k8s.io/helm/pkg/sympath-eecf22f77df5f65c823aacd2dbd30ae6c65f186e
k8s.io/helm/pkg/chartutil-eecf22f77df5f65c823aacd2dbd30ae6c65f186e
The Kubernetes Package Manager
Dependency Hierarchy:
- :x: **k8s.io/helm/pkg/chartutil-eecf22f77df5f65c823aacd2dbd30ae6c65f186e** (Vulnerable Library)
k8s.io/helm/pkg/sympath-eecf22f77df5f65c823aacd2dbd30ae6c65f186e
The Kubernetes Package Manager
Dependency Hierarchy:
- k8s.io/helm/pkg/chartutil-eecf22f77df5f65c823aacd2dbd30ae6c65f186e (Root Library)
- :x: **k8s.io/helm/pkg/sympath-eecf22f77df5f65c823aacd2dbd30ae6c65f186e** (Vulnerable Library)
Found in HEAD commit: f7db3d4b83b1d3b0008f56e9a649b36ed2ae830d
Found in base branch: main
Vulnerability Details
In Helm 2.x before 2.15.2, commands that deal with loading a chart as a directory or packaging a chart provide an opportunity for a maliciously designed chart to include sensitive content such as /etc/passwd, or to execute a denial of service (DoS) via a special file such as /dev/urandom, via symlinks. No version of Tiller is known to be impacted. This is a client-only issue.
Publish Date: 2019-11-12
URL: CVE-2019-18658
CVSS 3 Score Details (9.8)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-18658
Release Date: 2019-11-12
Fix Resolution: v2.15.2
Vulnerable Libraries - glob-parent-5.1.1.tgz, glob-parent-3.1.0.tgz
glob-parent-5.1.1.tgz
Extract the non-magic parent path from a glob string.
Library home page: https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.1.tgz
Path to dependency file: material-ui/node_modules/glob-parent/package.json
Path to vulnerable library: material-ui/node_modules/glob-parent/package.json
Dependency Hierarchy:
- lerna-3.22.1.tgz (Root Library)
- link-3.21.0.tgz
- command-3.21.0.tgz
- project-3.21.0.tgz
- :x: **glob-parent-5.1.1.tgz** (Vulnerable Library)
glob-parent-3.1.0.tgz
Strips glob magic from a string to provide the parent directory path
Library home page: https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz
Path to dependency file: material-ui/node_modules/glob-parent/package.json
Path to vulnerable library: material-ui/node_modules/glob-parent/package.json
Dependency Hierarchy:
- cpy-cli-3.1.1.tgz (Root Library)
- cpy-8.1.1.tgz
- globby-9.2.0.tgz
- fast-glob-2.2.7.tgz
- :x: **glob-parent-3.1.0.tgz** (Vulnerable Library)
Found in base branch: next
Vulnerability Details
Regular Expression Denial of Service (ReDoS) vulnerability was found in glob-parent before 5.1.2.
Publish Date: 2021-01-27
URL: WS-2021-0154
CVSS 3 Score Details (5.3)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://github.com/gulpjs/glob-parent/releases/tag/v5.1.2
Release Date: 2021-01-27
Fix Resolution: glob-parent - 5.1.2
Vulnerable Libraries - glob-parent-5.1.1.tgz, glob-parent-3.1.0.tgz
glob-parent-5.1.1.tgz
Extract the non-magic parent path from a glob string.
Library home page: https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.1.tgz
Path to dependency file: material-ui/node_modules/glob-parent/package.json
Path to vulnerable library: material-ui/node_modules/glob-parent/package.json
Dependency Hierarchy:
- lerna-3.22.1.tgz (Root Library)
- link-3.21.0.tgz
- command-3.21.0.tgz
- project-3.21.0.tgz
- :x: **glob-parent-5.1.1.tgz** (Vulnerable Library)
glob-parent-3.1.0.tgz
Strips glob magic from a string to provide the parent directory path
Library home page: https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz
Path to dependency file: material-ui/node_modules/glob-parent/package.json
Path to vulnerable library: material-ui/node_modules/glob-parent/package.json
Dependency Hierarchy:
- cpy-cli-3.1.1.tgz (Root Library)
- cpy-8.1.1.tgz
- globby-9.2.0.tgz
- fast-glob-2.2.7.tgz
- :x: **glob-parent-3.1.0.tgz** (Vulnerable Library)
Found in base branch: next
Vulnerability Details
Regular Expression Denial of Service (ReDoS) vulnerability was found in glob-parent before 5.1.2.
Publish Date: 2021-01-27
URL: WS-2021-0154
CVSS 3 Score Details (5.3)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://github.com/gulpjs/glob-parent/releases/tag/v5.1.2
Release Date: 2021-01-27
Fix Resolution: glob-parent - 5.1.2
$ go version
go version go1.13 linux/amd64
### What version of Badger are you using?
v1.5.5, v1.6.0, v2.0.0
### Does this issue reproduce with the latest master?
Yes (ish)
### What are the hardware specifications of the machine (RAM, OS, Disk)?
x86-64
### What did you do?
Trying to use the instructions [here](https://github.com/dgraph-io/badger/blob/master/README.md#i-see-manifest-has-unsupported-version-x-we-support-y-error) to convert a pre v2 database to v2. I get an error about the wiretype. I suspect this may be related to 4e5cbcc8574b8258c0146d4d01539b6d48212f4a as mentioned in #966.
in `badger/badger` dir:
```
$ git checkout v1.5.5
$ go build -o /tmp/badger-v1.5.5 .
$ git checkout v1.6.0
$ go build -o /tmp/badger-v1.6.0 .
$ git checkout v2.0.0-rc3
$ go build -o /tmp/badger-v2.0.0.
```
Data is in `/tmp/old/`
```
$ /tmp/badger-v1.5.5 -dir /tmp/old/ -f /tmp/backup
Listening for /debug HTTP requests at port: 8080
Port busy. Trying another one...
Listening for /debug HTTP requests at port: 8081
2019/10/04 02:19:32 Replaying from value pointer: {Fid:0 Len:44 Offset:221201341}
2019/10/04 02:19:32 Iterating file id: 0
2019/10/04 02:19:32 Iteration took: 11.493µs
$ ls -lh /tmp/backup
-rw-r--r-- 1 jmansfield 501 206M Oct 4 02:19 /tmp/backup
$ mkdir /tmp/new/
$ /tmp/badger-v2.0.0 restore --dir /tmp/new/ -f /tmp/backup
Listening for /debug HTTP requests at port: 8080
Port busy. Trying another one...
Listening for /debug HTTP requests at port: 8081
badger 2019/10/04 02:21:49 INFO: All 0 tables opened in 0s
badger 2019/10/04 02:21:49 INFO: Got compaction priority: {level:0 score:1.73 dropPrefix:[]}
Error: proto: illegal wireType 7
Usage:
badger restore [flags]
Flags:
-f, --backup-file string File to restore from (default ""badger.bak"")
-h, --help help for restore
-w, --max-pending-writes int Max number of pending writes at any time while restore (default 256)
Global Flags:
--dir string Directory where the LSM tree files are located. (required)
--vlog-dir string Directory where the value log files are located, if different from --dir
proto: illegal wireType 7
$ rm /tmp/backup
$ rm /tmp/new/*
$ /tmp/badger-v1.6.0 backup --dir /tmp/old/ -f /tmp/backup
Listening for /debug HTTP requests at port: 8080
Port busy. Trying another one...
Listening for /debug HTTP requests at port: 8081
badger 2019/10/04 02:23:41 INFO: All 1 tables opened in 116ms
badger 2019/10/04 02:23:41 INFO: Replaying file id: 0 at offset: 221201385
badger 2019/10/04 02:23:41 INFO: Replay took: 13.803µs
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.2 MB in 3.748252ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.2 MB in 2.725004ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.2 MB in 4.651587ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.3 MB in 10.003926ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.3 MB in 10.617858ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.3 MB in 9.836249ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.3 MB in 7.726215ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.3 MB in 8.288252ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.3 MB in 8.235459ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.3 MB in 6.29205ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.2 MB in 3.652964ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.2 MB in 3.849211ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.2 MB in 4.060754ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.2 MB in 4.05686ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.2 MB in 4.305175ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.2 MB in 45.192963ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 25 MB in 15.394368ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 21 MB in 12.44265ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 17 MB in 12.794977ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 13 MB in 47.555567ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 38 MB in 22.24327ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.2 MB in 3.004712ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.2 MB in 3.239008ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.2 MB in 2.023829ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.2 MB in 1.900745ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.2 MB in 43.769075ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 13 MB in 9.170276ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Sent 427900 keys
badger 2019/10/04 02:23:42 INFO: Got compaction priority: {level:0 score:1.73 dropPrefix:[]}
$ ls -lh /tmp/backup
-rw-r--r-- 1 jmansfield 501 206M Oct 4 02:23 /tmp/backup
$ /tmp/badger-v2.0.0 restore --dir /tmp/new/ -f /tmp/backup
Listening for /debug HTTP requests at port: 8080
Port busy. Trying another one...
Listening for /debug HTTP requests at port: 8081
badger 2019/10/04 02:24:16 INFO: All 0 tables opened in 0s
badger 2019/10/04 02:24:18 DEBUG: Storing value log head: {Fid:0 Len:1918 Offset:215714908}
badger 2019/10/04 02:24:18 INFO: Got compaction priority: {level:0 score:1.73 dropPrefix:[]}
badger 2019/10/04 02:24:18 INFO: Running for level: 0
badger 2019/10/04 02:24:18 DEBUG: LOG Compact. Added 427901 keys. Skipped 0 keys. Iteration took: 227.260848ms
badger 2019/10/04 02:24:18 DEBUG: Discard stats: map[]
badger 2019/10/04 02:24:18 INFO: LOG Compact 0->1, del 1 tables, add 1 tables, took 350.923977ms
badger 2019/10/04 02:24:18 INFO: Compaction for level: 0 DONE
badger 2019/10/04 02:24:18 INFO: Force compaction on level 0 done
$ ls -lh /tmp/new/
total 232M
-rw-r--r-- 1 jmansfield 501 206M Oct 4 02:24 000000.vlog
-rw-r--r-- 1 jmansfield 501 26M Oct 4 02:24 000002.sst
-rw-r--r-- 1 jmansfield 501 48 Oct 4 02:24 MANIFEST
```
### What did you expect to see?
The data get converted using 1.5.5 to v2.0.0
### What did you see instead?
An error about wireType unless the `backup` operation was performed with v1.6.0
I consider this to be an issue with documentation, not the tool. The conversion instructions in the documentation specify v1.5.5. That other doesn't work or doesn't _always_ work.",1.0,"Backup/Restore v1.5.5 -> v2.0.0 fails with - ### What version of Go are you using (`go version`)?
$ go version
go version go1.13 linux/amd64
### What version of Badger are you using?
v1.5.5, v1.6.0, v2.0.0
### Does this issue reproduce with the latest master?
Yes (ish)
### What are the hardware specifications of the machine (RAM, OS, Disk)?
x86-64
### What did you do?
Trying to use the instructions [here](https://github.com/dgraph-io/badger/blob/master/README.md#i-see-manifest-has-unsupported-version-x-we-support-y-error) to convert a pre v2 database to v2. I get an error about the wiretype. I suspect this may be related to 4e5cbcc8574b8258c0146d4d01539b6d48212f4a as mentioned in #966.
in `badger/badger` dir:
```
$ git checkout v1.5.5
$ go build -o /tmp/badger-v1.5.5 .
$ git checkout v1.6.0
$ go build -o /tmp/badger-v1.6.0 .
$ git checkout v2.0.0-rc3
$ go build -o /tmp/badger-v2.0.0.
```
Data is in `/tmp/old/`
```
$ /tmp/badger-v1.5.5 -dir /tmp/old/ -f /tmp/backup
Listening for /debug HTTP requests at port: 8080
Port busy. Trying another one...
Listening for /debug HTTP requests at port: 8081
2019/10/04 02:19:32 Replaying from value pointer: {Fid:0 Len:44 Offset:221201341}
2019/10/04 02:19:32 Iterating file id: 0
2019/10/04 02:19:32 Iteration took: 11.493µs
$ ls -lh /tmp/backup
-rw-r--r-- 1 jmansfield 501 206M Oct 4 02:19 /tmp/backup
$ mkdir /tmp/new/
$ /tmp/badger-v2.0.0 restore --dir /tmp/new/ -f /tmp/backup
Listening for /debug HTTP requests at port: 8080
Port busy. Trying another one...
Listening for /debug HTTP requests at port: 8081
badger 2019/10/04 02:21:49 INFO: All 0 tables opened in 0s
badger 2019/10/04 02:21:49 INFO: Got compaction priority: {level:0 score:1.73 dropPrefix:[]}
Error: proto: illegal wireType 7
Usage:
badger restore [flags]
Flags:
-f, --backup-file string File to restore from (default ""badger.bak"")
-h, --help help for restore
-w, --max-pending-writes int Max number of pending writes at any time while restore (default 256)
Global Flags:
--dir string Directory where the LSM tree files are located. (required)
--vlog-dir string Directory where the value log files are located, if different from --dir
proto: illegal wireType 7
$ rm /tmp/backup
$ rm /tmp/new/*
$ /tmp/badger-v1.6.0 backup --dir /tmp/old/ -f /tmp/backup
Listening for /debug HTTP requests at port: 8080
Port busy. Trying another one...
Listening for /debug HTTP requests at port: 8081
badger 2019/10/04 02:23:41 INFO: All 1 tables opened in 116ms
badger 2019/10/04 02:23:41 INFO: Replaying file id: 0 at offset: 221201385
badger 2019/10/04 02:23:41 INFO: Replay took: 13.803µs
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.2 MB in 3.748252ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.2 MB in 2.725004ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.2 MB in 4.651587ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.3 MB in 10.003926ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.3 MB in 10.617858ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.3 MB in 9.836249ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.3 MB in 7.726215ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.3 MB in 8.288252ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.3 MB in 8.235459ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.3 MB in 6.29205ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.2 MB in 3.652964ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.2 MB in 3.849211ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.2 MB in 4.060754ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.2 MB in 4.05686ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.2 MB in 4.305175ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.2 MB in 45.192963ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 25 MB in 15.394368ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 21 MB in 12.44265ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 17 MB in 12.794977ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 13 MB in 47.555567ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 38 MB in 22.24327ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.2 MB in 3.004712ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.2 MB in 3.239008ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.2 MB in 2.023829ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.2 MB in 1.900745ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 4.2 MB in 43.769075ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Created batch of size: 13 MB in 9.170276ms.
badger 2019/10/04 02:23:41 INFO: DB.Backup Sent 427900 keys
badger 2019/10/04 02:23:42 INFO: Got compaction priority: {level:0 score:1.73 dropPrefix:[]}
$ ls -lh /tmp/backup
-rw-r--r-- 1 jmansfield 501 206M Oct 4 02:23 /tmp/backup
$ /tmp/badger-v2.0.0 restore --dir /tmp/new/ -f /tmp/backup
Listening for /debug HTTP requests at port: 8080
Port busy. Trying another one...
Listening for /debug HTTP requests at port: 8081
badger 2019/10/04 02:24:16 INFO: All 0 tables opened in 0s
badger 2019/10/04 02:24:18 DEBUG: Storing value log head: {Fid:0 Len:1918 Offset:215714908}
badger 2019/10/04 02:24:18 INFO: Got compaction priority: {level:0 score:1.73 dropPrefix:[]}
badger 2019/10/04 02:24:18 INFO: Running for level: 0
badger 2019/10/04 02:24:18 DEBUG: LOG Compact. Added 427901 keys. Skipped 0 keys. Iteration took: 227.260848ms
badger 2019/10/04 02:24:18 DEBUG: Discard stats: map[]
badger 2019/10/04 02:24:18 INFO: LOG Compact 0->1, del 1 tables, add 1 tables, took 350.923977ms
badger 2019/10/04 02:24:18 INFO: Compaction for level: 0 DONE
badger 2019/10/04 02:24:18 INFO: Force compaction on level 0 done
$ ls -lh /tmp/new/
total 232M
-rw-r--r-- 1 jmansfield 501 206M Oct 4 02:24 000000.vlog
-rw-r--r-- 1 jmansfield 501 26M Oct 4 02:24 000002.sst
-rw-r--r-- 1 jmansfield 501 48 Oct 4 02:24 MANIFEST
```
### What did you expect to see?
The data get converted using 1.5.5 to v2.0.0
### What did you see instead?
An error about wireType unless the `backup` operation was performed with v1.6.0
I consider this to be an issue with documentation, not the tool. The conversion instructions in the documentation specify v1.5.5. That other doesn't work or doesn't _always_ work.",0,backup restore fails with what version of go are you using go version go version go version linux what version of badger are you using does this issue reproduce with the latest master yes ish what are the hardware specifications of the machine ram os disk what did you do trying to use the instructions to convert a pre database to i get an error about the wiretype i suspect this may be related to as mentioned in in badger badger dir git checkout go build o tmp badger git checkout go build o tmp badger git checkout go build o tmp badger data is in tmp old tmp badger dir tmp old f tmp backup listening for debug http requests at port port busy trying another one listening for debug http requests at port replaying from value pointer fid len offset iterating file id iteration took ls lh tmp backup rw r r jmansfield oct tmp backup mkdir tmp new tmp badger restore dir tmp new f tmp backup listening for debug http requests at port port busy trying another one listening for debug http requests at port badger info all tables opened in badger info got compaction priority level score dropprefix error proto illegal wiretype usage badger restore flags f backup file string file to restore from default badger bak h help help for restore w max pending writes int max number of pending writes at any time while restore default global flags dir string directory where the lsm tree files are located required vlog dir string directory where the value log files are located if different from dir proto illegal wiretype rm tmp backup rm tmp new tmp badger backup dir tmp old f tmp backup listening for debug http requests at port port busy trying another one listening for debug http requests at port badger info all tables opened in badger info replaying file id at offset badger info replay took badger info db backup created batch of size mb in badger info db backup created batch of size mb in badger info db backup created batch of size mb in badger info db backup created batch of size mb in badger info db backup created batch of size mb in badger info db backup created batch of size mb in badger info db backup created batch of size mb in badger info db backup created batch of size mb in badger info db backup created batch of size mb in badger info db backup created batch of size mb in badger info db backup created batch of size mb in badger info db backup created batch of size mb in badger info db backup created batch of size mb in badger info db backup created batch of size mb in badger info db backup created batch of size mb in badger info db backup created batch of size mb in badger info db backup created batch of size mb in badger info db backup created batch of size mb in badger info db backup created batch of size mb in badger info db backup created batch of size mb in badger info db backup created batch of size mb in badger info db backup created batch of size mb in badger info db backup created batch of size mb in badger info db backup created batch of size mb in badger info db backup created batch of size mb in badger info db backup created batch of size mb in badger info db backup created batch of size mb in badger info db backup sent keys badger info got compaction priority level score dropprefix ls lh tmp backup rw r r jmansfield oct tmp backup tmp badger restore dir tmp new f tmp backup listening for debug http requests at port port busy trying another one listening for debug http requests at port badger info all tables opened in badger debug storing value log head fid len offset badger info got compaction priority level score dropprefix badger info running for level badger debug log compact added keys skipped keys iteration took badger debug discard stats map badger info log compact del tables add tables took badger info compaction for level done badger info force compaction on level done ls lh tmp new total rw r r jmansfield oct vlog rw r r jmansfield oct sst rw r r jmansfield oct manifest what did you expect to see the data get converted using to what did you see instead an error about wiretype unless the backup operation was performed with i consider this to be an issue with documentation not the tool the conversion instructions in the documentation specify that other doesn t work or doesn t always work ,0
1766,26028786891.0,IssuesEvent,2022-12-21 18:53:44,AzureAD/microsoft-authentication-library-for-dotnet,https://api.github.com/repos/AzureAD/microsoft-authentication-library-for-dotnet,closed,[Feature Request] Improve logging,enhancement Feature Request Supportability needs-spec,"Logging at `LogLevel.Info` is too verbose and the logs are unstructured. A simple request to get a token using a client secret logs 18 events. In a service that requests many tokens, writing 18 events per token request adds a lot of noise to the service logs.
Logs are sent to the `LogCallback` delegate as an unstructured string. In a service that has structured logs, passing the date, time, OS version and library version as a single string on each request adds a lot of duplication and makes the logs hard to integrate with other service logging.
**Describe the solution you'd like**
- Change `LogLevel.Info` to log just a summary of a token request, for example one event when the request is started containing the request details and a second event when the request succeeds / fails containing the response details and the caching behavior
- Move the logs for each step of the token acquisition process to `LogLevel.Verbose`
- Pass the log details to `LogCallback` as a structure rather than a string, separating out the various parts into fields
- Give event names or event IDs to the various events to allow services to filter events
**Describe alternatives you've considered**
- Parsing the log string with a regular expression to extract the useful data
- Only writing logs at `LogLevel.Warning` and `LogLevel.Error` to service logs and logging requests by injecting a handler into the HTTP pipeline",True,"[Feature Request] Improve logging - Logging at `LogLevel.Info` is too verbose and the logs are unstructured. A simple request to get a token using a client secret logs 18 events. In a service that requests many tokens, writing 18 events per token request adds a lot of noise to the service logs.
Logs are sent to the `LogCallback` delegate as an unstructured string. In a service that has structured logs, passing the date, time, OS version and library version as a single string on each request adds a lot of duplication and makes the logs hard to integrate with other service logging.
**Describe the solution you'd like**
- Change `LogLevel.Info` to log just a summary of a token request, for example one event when the request is started containing the request details and a second event when the request succeeds / fails containing the response details and the caching behavior
- Move the logs for each step of the token acquisition process to `LogLevel.Verbose`
- Pass the log details to `LogCallback` as a structure rather than a string, separating out the various parts into fields
- Give event names or event IDs to the various events to allow services to filter events
**Describe alternatives you've considered**
- Parsing the log string with a regular expression to extract the useful data
- Only writing logs at `LogLevel.Warning` and `LogLevel.Error` to service logs and logging requests by injecting a handler into the HTTP pipeline",1, improve logging logging at loglevel info is too verbose and the logs are unstructured a simple request to get a token using a client secret logs events in a service that requests many tokens writing events per token request adds a lot of noise to the service logs logs are sent to the logcallback delegate as an unstructured string in a service that has structured logs passing the date time os version and library version as a single string on each request adds a lot of duplication and makes the logs hard to integrate with other service logging describe the solution you d like change loglevel info to log just a summary of a token request for example one event when the request is started containing the request details and a second event when the request succeeds fails containing the response details and the caching behavior move the logs for each step of the token acquisition process to loglevel verbose pass the log details to logcallback as a structure rather than a string separating out the various parts into fields give event names or event ids to the various events to allow services to filter events describe alternatives you ve considered parsing the log string with a regular expression to extract the useful data only writing logs at loglevel warning and loglevel error to service logs and logging requests by injecting a handler into the http pipeline,1
312655,9551019838.0,IssuesEvent,2019-05-02 13:35:05,bbc/simorgh,https://api.github.com/repos/bbc/simorgh,opened,Vulnerability in execa dependency,bug high priority,"**Describe the bug**
```
✗ Medium severity vulnerability found in execa
Description: Arbitrary Command Injection
Info: https://snyk.io/vuln/SNYK-JS-EXECA-174564
Introduced through: webpack-cli@3.3.0
From: webpack-cli@3.3.0 > yargs@12.0.5 > os-locale@3.1.0 > execa@1.0.0
Organisation: bbc
Package manager: npm
Target file: package-lock.json
Open source: no
Project path: simorgh
Tested 738 dependencies for known vulnerabilities, found 1 vulnerability, 1 vulnerable path.
Run `snyk wizard` to address these issues.
```
**To Reproduce**
Steps to reproduce the behavior:
1. locally run `npm run snyk`
2. See error
**Expected behavior**
No error
**Screenshots**
![]()
",1.0,"Vulnerability in execa dependency - **Describe the bug**
```
✗ Medium severity vulnerability found in execa
Description: Arbitrary Command Injection
Info: https://snyk.io/vuln/SNYK-JS-EXECA-174564
Introduced through: webpack-cli@3.3.0
From: webpack-cli@3.3.0 > yargs@12.0.5 > os-locale@3.1.0 > execa@1.0.0
Organisation: bbc
Package manager: npm
Target file: package-lock.json
Open source: no
Project path: simorgh
Tested 738 dependencies for known vulnerabilities, found 1 vulnerability, 1 vulnerable path.
Run `snyk wizard` to address these issues.
```
**To Reproduce**
Steps to reproduce the behavior:
1. locally run `npm run snyk`
2. See error
**Expected behavior**
No error
**Screenshots**
![]()
",0,vulnerability in execa dependency describe the bug ✗ medium severity vulnerability found in execa description arbitrary command injection info introduced through webpack cli from webpack cli yargs os locale execa organisation bbc package manager npm target file package lock json open source no project path simorgh tested dependencies for known vulnerabilities found vulnerability vulnerable path run snyk wizard to address these issues to reproduce steps to reproduce the behavior locally run npm run snyk see error expected behavior no error screenshots img width alt screen shot at src ,0
64485,8737558615.0,IssuesEvent,2018-12-11 23:00:35,awslabs/aws-sam-cli,https://api.github.com/repos/awslabs/aws-sam-cli,closed,Examples link in Readme broken,area/docs stage/in-review type/documentation,"In the [Examples Section](https://github.com/awslabs/aws-sam-cli#examples) of the Readme, there's a link to a `samples` folder, which is broken.
Where should we send users to instead?",1.0,"Examples link in Readme broken - In the [Examples Section](https://github.com/awslabs/aws-sam-cli#examples) of the Readme, there's a link to a `samples` folder, which is broken.
Where should we send users to instead?",0,examples link in readme broken in the of the readme there s a link to a samples folder which is broken where should we send users to instead ,0
161141,12531762274.0,IssuesEvent,2020-06-04 14:58:39,elastic/elasticsearch,https://api.github.com/repos/elastic/elasticsearch,closed,:x-pack:qa:rolling-upgrade:v6.8.10#upgradedClusterTest: IO error while waiting cluster,:Distributed/Network >test-failure Team:Distributed,"**Build scan**: https://gradle-enterprise.elastic.co/s/yvd4eyecgtota
**Repro line**: `./gradlew -p x-pack/qa/rolling-upgrade check`
**Reproduces locally?**: yes. wait. no. I'm confused.
**Applicable branches**: 7.x
**Failure history**:
I don't see it in build-stats but I'm not good at searching. I've seen it several times today.
**Failure excerpt**:
```
» Caused by: org.elasticsearch.transport.ActionNotFoundTransportException: No handler for action [indices:admin/data_stream/delete]
```
...
```
» Caused by: org.elasticsearch.ElasticsearchException: node doesn't have meta data for index [my_old_index/Vn7jbwk0TF6Bh9MubpGT0Q]
» at org.elasticsearch.indices.store.TransportNodesListShardStoreMetadata.listStoreMetadata(TransportNodesListShardStoreMetadata.java:160) ~[?:?]
```
",1.0,":x-pack:qa:rolling-upgrade:v6.8.10#upgradedClusterTest: IO error while waiting cluster - **Build scan**: https://gradle-enterprise.elastic.co/s/yvd4eyecgtota
**Repro line**: `./gradlew -p x-pack/qa/rolling-upgrade check`
**Reproduces locally?**: yes. wait. no. I'm confused.
**Applicable branches**: 7.x
**Failure history**:
I don't see it in build-stats but I'm not good at searching. I've seen it several times today.
**Failure excerpt**:
```
» Caused by: org.elasticsearch.transport.ActionNotFoundTransportException: No handler for action [indices:admin/data_stream/delete]
```
...
```
» Caused by: org.elasticsearch.ElasticsearchException: node doesn't have meta data for index [my_old_index/Vn7jbwk0TF6Bh9MubpGT0Q]
» at org.elasticsearch.indices.store.TransportNodesListShardStoreMetadata.listStoreMetadata(TransportNodesListShardStoreMetadata.java:160) ~[?:?]
```
",0, x pack qa rolling upgrade upgradedclustertest io error while waiting cluster build scan repro line gradlew p x pack qa rolling upgrade check reproduces locally yes wait no i m confused applicable branches x failure history i don t see it in build stats but i m not good at searching i ve seen it several times today failure excerpt » caused by org elasticsearch transport actionnotfoundtransportexception no handler for action » caused by org elasticsearch elasticsearchexception node doesn t have meta data for index » at org elasticsearch indices store transportnodeslistshardstoremetadata liststoremetadata transportnodeslistshardstoremetadata java ,0
536,7542437776.0,IssuesEvent,2018-04-17 13:01:04,orientechnologies/orientdb,https://api.github.com/repos/orientechnologies/orientdb,closed,SEVER Internal server error,question supportability,"## OrientDB Version, operating system, or hardware.
- v2.2,5
## Operating System
- [x] Linux
- [ ] MacOSX
- [ ] Windows
- [ ] Other Unix
- [ ] Other, name?
## Expected behavior and actual behavior
Hi,
This is the only log what we got from orientdb when tried to query the database. No other information is available.
How to gain more insight of the ""internal server error""?
I would expect a lenghty stacktrace or some other pointers, but nothing is to be seen in the log.
## Steps to reproduce the problem
",True,"SEVER Internal server error - ## OrientDB Version, operating system, or hardware.
- v2.2,5
## Operating System
- [x] Linux
- [ ] MacOSX
- [ ] Windows
- [ ] Other Unix
- [ ] Other, name?
## Expected behavior and actual behavior
Hi,
This is the only log what we got from orientdb when tried to query the database. No other information is available.
How to gain more insight of the ""internal server error""?
I would expect a lenghty stacktrace or some other pointers, but nothing is to be seen in the log.
## Steps to reproduce the problem
",1,sever internal server error orientdb version operating system or hardware operating system linux macosx windows other unix other name expected behavior and actual behavior hi this is the only log what we got from orientdb when tried to query the database no other information is available how to gain more insight of the internal server error i would expect a lenghty stacktrace or some other pointers but nothing is to be seen in the log steps to reproduce the problem ,1
118,3357814943.0,IssuesEvent,2015-11-19 04:38:55,dotnet/roslyn,https://api.github.com/repos/dotnet/roslyn,closed,Automatic referencing of mscorlib on coreclr,Area-Compilers core-clr Feature Request Portability,"Unless the [/nostdlib](https://msdn.microsoft.com/en-us/library/fa13yay7.aspx) option is passed the C# compiler will automatically add a reference to mscorlib for the compilation. The compiler assumes that mscorlib exist inside [GetCORSystemDirectory](https://msdn.microsoft.com/en-us/library/k0588yw5%28v=vs.110%29.aspx) / [RuntimeEnvironment::GetRuntimeDirectory](https://msdn.microsoft.com/en-us/library/system.runtime.interopservices.runtimeenvironment.getruntimedirectory%28v=vs.90%29.aspx). No checking is performed on this, it simply assumes the file exists in that location.
This process doesn't make sense when the compiler is run under coreclr for a couple of reasons:
- There is no mscorlib in coreclr scenarios. Instead there are a set of contract assemblies to be referenced.
- There is no SDK directory to search for. The CoreCLR deployments for the compiler will include the runtime assemblies, not the contract assemblies.
Note that relying to the desktop APIs even when running under coreclr is not really an option. They won't exist on xcopy installs or cross platform.
We need to come up with a suitable cross plat / coreclr strategy for this scenario.
",True,"Automatic referencing of mscorlib on coreclr - Unless the [/nostdlib](https://msdn.microsoft.com/en-us/library/fa13yay7.aspx) option is passed the C# compiler will automatically add a reference to mscorlib for the compilation. The compiler assumes that mscorlib exist inside [GetCORSystemDirectory](https://msdn.microsoft.com/en-us/library/k0588yw5%28v=vs.110%29.aspx) / [RuntimeEnvironment::GetRuntimeDirectory](https://msdn.microsoft.com/en-us/library/system.runtime.interopservices.runtimeenvironment.getruntimedirectory%28v=vs.90%29.aspx). No checking is performed on this, it simply assumes the file exists in that location.
This process doesn't make sense when the compiler is run under coreclr for a couple of reasons:
- There is no mscorlib in coreclr scenarios. Instead there are a set of contract assemblies to be referenced.
- There is no SDK directory to search for. The CoreCLR deployments for the compiler will include the runtime assemblies, not the contract assemblies.
Note that relying to the desktop APIs even when running under coreclr is not really an option. They won't exist on xcopy installs or cross platform.
We need to come up with a suitable cross plat / coreclr strategy for this scenario.
",1,automatic referencing of mscorlib on coreclr unless the option is passed the c compiler will automatically add a reference to mscorlib for the compilation the compiler assumes that mscorlib exist inside no checking is performed on this it simply assumes the file exists in that location this process doesn t make sense when the compiler is run under coreclr for a couple of reasons there is no mscorlib in coreclr scenarios instead there are a set of contract assemblies to be referenced there is no sdk directory to search for the coreclr deployments for the compiler will include the runtime assemblies not the contract assemblies note that relying to the desktop apis even when running under coreclr is not really an option they won t exist on xcopy installs or cross platform we need to come up with a suitable cross plat coreclr strategy for this scenario ,1
1975,30881299253.0,IssuesEvent,2023-08-03 17:49:10,tree-sitter/tree-sitter,https://api.github.com/repos/tree-sitter/tree-sitter,closed,Cannot compile tree-sitter with Clang and MinGW on Windows,bug portability,"## Issues
There are multiple issues related to the incompatibility of Tree-sitter with Clang and MinGW on Windows:
- [x] When running `tree-sitter test`, the code assumes that MSVC is used on Windows and flags, which is not a correct assumption. Flags not supported by other compilers like Clang and Mingw are used for compilation (e.g. `-fPIC`). Fixed by pull request #1835
- [x] `fdopen`, which is a non-standard POSIX function, is used on Windows. This causes compilation errors when `-Werror` is enabled with Clang on Windows because this warning is enabled by default. Fixed by pull request #1411
```cpp
warning: In file included from src\lib.c:12:
warning: src/./parser.c:1781:28: warning: 'fdopen' is deprecated: The POSIX name for this item is deprecated. Instead, use the ISO C and C++ conformant name: _fdopen. See online help for details. [-Wdeprecated-declarations]
warning: self->dot_graph_file = fdopen(fd, ""a"");
warning: ^
warning: C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\ucrt\stdio.h:2431:28: note: 'fdopen' has been explicitly marked deprecated here
warning: _Check_return_ _CRT_NONSTDC_DEPRECATE(_fdopen) _ACRTIMP FILE* __cdecl fdopen(_In_ int _FileHandle, _In_z_ char const* _Format);
warning: ^
warning: C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\ucrt\corecrt.h:414:50: note: expanded from macro '_CRT_NONSTDC_DEPRECATE'
warning: #define _CRT_NONSTDC_DEPRECATE(_NewName) _CRT_DEPRECATE_TEXT( \
warning: ^
warning: C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\VC\Tools\MSVC\14.29.30133\include\vcruntime.h:310:47: note: expanded from macro '_CRT_DEPRECATE_TEXT'
warning: #define _CRT_DEPRECATE_TEXT(_Text) __declspec(deprecated(_Text))
```
- [x] 'ts_stack__add_slice' is used in an inline function with external linkage. This is technically an error because the inline functions should not be linked statically. This causes compilation errors when `-Werror` is enabled with Clang on Windows because this warning is enabled by default. Fixed by pull request #1411
```cpp
warning: In file included from src\lib.c:14:
warning: src/./stack.c:311:9: warning: static function 'ts_stack__add_slice' is used in an inline function with external linkage [-Wstatic-in-inline]
warning: ts_stack__add_slice(
warning: ^
warning: src/./stack.c:274:1: note: use 'static' to give inline function 'stack__iter' internal linkage
warning: inline StackSliceArray stack__iter(Stack *self, StackVersion version,
warning: ^
warning: static
warning: src/./stack.c:15:16: note: expanded from macro 'inline'
warning: #define inline __forceinline
warning: ^
warning: src/./stack.c:258:13: note: 'ts_stack__add_slice' declared here
warning: static void ts_stack__add_slice(Stack *self, StackVersion original_version,
warning: ^
warning: 1 warning generated.
```
",True,"Cannot compile tree-sitter with Clang and MinGW on Windows - ## Issues
There are multiple issues related to the incompatibility of Tree-sitter with Clang and MinGW on Windows:
- [x] When running `tree-sitter test`, the code assumes that MSVC is used on Windows and flags, which is not a correct assumption. Flags not supported by other compilers like Clang and Mingw are used for compilation (e.g. `-fPIC`). Fixed by pull request #1835
- [x] `fdopen`, which is a non-standard POSIX function, is used on Windows. This causes compilation errors when `-Werror` is enabled with Clang on Windows because this warning is enabled by default. Fixed by pull request #1411
```cpp
warning: In file included from src\lib.c:12:
warning: src/./parser.c:1781:28: warning: 'fdopen' is deprecated: The POSIX name for this item is deprecated. Instead, use the ISO C and C++ conformant name: _fdopen. See online help for details. [-Wdeprecated-declarations]
warning: self->dot_graph_file = fdopen(fd, ""a"");
warning: ^
warning: C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\ucrt\stdio.h:2431:28: note: 'fdopen' has been explicitly marked deprecated here
warning: _Check_return_ _CRT_NONSTDC_DEPRECATE(_fdopen) _ACRTIMP FILE* __cdecl fdopen(_In_ int _FileHandle, _In_z_ char const* _Format);
warning: ^
warning: C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\ucrt\corecrt.h:414:50: note: expanded from macro '_CRT_NONSTDC_DEPRECATE'
warning: #define _CRT_NONSTDC_DEPRECATE(_NewName) _CRT_DEPRECATE_TEXT( \
warning: ^
warning: C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\VC\Tools\MSVC\14.29.30133\include\vcruntime.h:310:47: note: expanded from macro '_CRT_DEPRECATE_TEXT'
warning: #define _CRT_DEPRECATE_TEXT(_Text) __declspec(deprecated(_Text))
```
- [x] 'ts_stack__add_slice' is used in an inline function with external linkage. This is technically an error because the inline functions should not be linked statically. This causes compilation errors when `-Werror` is enabled with Clang on Windows because this warning is enabled by default. Fixed by pull request #1411
```cpp
warning: In file included from src\lib.c:14:
warning: src/./stack.c:311:9: warning: static function 'ts_stack__add_slice' is used in an inline function with external linkage [-Wstatic-in-inline]
warning: ts_stack__add_slice(
warning: ^
warning: src/./stack.c:274:1: note: use 'static' to give inline function 'stack__iter' internal linkage
warning: inline StackSliceArray stack__iter(Stack *self, StackVersion version,
warning: ^
warning: static
warning: src/./stack.c:15:16: note: expanded from macro 'inline'
warning: #define inline __forceinline
warning: ^
warning: src/./stack.c:258:13: note: 'ts_stack__add_slice' declared here
warning: static void ts_stack__add_slice(Stack *self, StackVersion original_version,
warning: ^
warning: 1 warning generated.
```
",1,cannot compile tree sitter with clang and mingw on windows issues there are multiple issues related to the incompatibility of tree sitter with clang and mingw on windows when running tree sitter test the code assumes that msvc is used on windows and flags which is not a correct assumption flags not supported by other compilers like clang and mingw are used for compilation e g fpic fixed by pull request fdopen which is a non standard posix function is used on windows this causes compilation errors when werror is enabled with clang on windows because this warning is enabled by default fixed by pull request cpp warning in file included from src lib c warning src parser c warning fdopen is deprecated the posix name for this item is deprecated instead use the iso c and c conformant name fdopen see online help for details warning self dot graph file fdopen fd a warning warning c program files windows kits include ucrt stdio h note fdopen has been explicitly marked deprecated here warning check return crt nonstdc deprecate fdopen acrtimp file cdecl fdopen in int filehandle in z char const format warning warning c program files windows kits include ucrt corecrt h note expanded from macro crt nonstdc deprecate warning define crt nonstdc deprecate newname crt deprecate text warning warning c program files microsoft visual studio preview vc tools msvc include vcruntime h note expanded from macro crt deprecate text warning define crt deprecate text text declspec deprecated text ts stack add slice is used in an inline function with external linkage this is technically an error because the inline functions should not be linked statically this causes compilation errors when werror is enabled with clang on windows because this warning is enabled by default fixed by pull request cpp warning in file included from src lib c warning src stack c warning static function ts stack add slice is used in an inline function with external linkage warning ts stack add slice warning warning src stack c note use static to give inline function stack iter internal linkage warning inline stackslicearray stack iter stack self stackversion version warning warning static warning src stack c note expanded from macro inline warning define inline forceinline warning warning src stack c note ts stack add slice declared here warning static void ts stack add slice stack self stackversion original version warning warning warning generated ,1
252848,21633906725.0,IssuesEvent,2022-05-05 12:36:54,gravitee-io/issues,https://api.github.com/repos/gravitee-io/issues,closed,Error when importing an API without logging on an env with `Logging audit events` activated,type: bug project: APIM Support 2 p2 loop quantum status: in test,"## :collision: Describe the bug
When trying to import an API without `logging` part on an env with `Generate API Logging audit events (API_LOGGING_ENABLED, API_LOGGING_DISABLED, API_LOGGING_UPDATED)` option activated (available under Env Settings > Gateway - API Logging menu), it throws the following error:
```java
11:48:12.387 \[gravitee-listener-671\] ERROR i.g.r.a.service.impl.ApiServiceImpl - An error occurs while auditing API logging configuration for API: 8e6c1778-9a1e-41b1-ac17-789a1e41b101
11:48:12.387 \[gravitee-listener-671\] ERROR i.g.r.a.service.impl.ApiServiceImpl - An error occurs while auditing API logging configuration for API: 8e6c1778-9a1e-41b1-ac17-789a1e41b101
java.lang.NullPointerException: null
at io.gravitee.rest.api.service.impl.ApiServiceImpl.auditApiLogging(ApiServiceImpl.java:3400)
at io.gravitee.rest.api.service.impl.ApiServiceImpl.update(ApiServiceImpl.java:1649)
at jdk.internal.reflect.GeneratedMethodAccessor1997.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
```
## :sunrise_over_mountains: To Reproduce
Steps to reproduce the behaviour:
1. Create an API, activate the logging and export it
2. Go to Env Settings > Gateway - API Logging menu and activate `Generate API Logging audit events`
3. Update the exported API to remove the `logging` section
4. Go back on the API (in the console) and try to import the updated file
4. See error
## :rainbow: Expected behaviour
Everything should be fine, the API should be updated and logging deactivated for it.
## Current behavior
Import is failing.
## :movie_camera: Useful information
Do not forget to activate
```
Generate API Logging audit events (API_LOGGING_ENABLED, API_LOGGING_DISABLED, API_LOGGING_UPDATED)
```
This NPE was spotted by SonarCloud:
## :computer: Desktop:
NA
## :warning: Potential impacts
***Which other features may be impacted by this fix. This could be populated after fix***
***What are the impacted versions?***
3.10.x +
## :link: Dependencies
Link a story or other related things...
",1.0,"Error when importing an API without logging on an env with `Logging audit events` activated - ## :collision: Describe the bug
When trying to import an API without `logging` part on an env with `Generate API Logging audit events (API_LOGGING_ENABLED, API_LOGGING_DISABLED, API_LOGGING_UPDATED)` option activated (available under Env Settings > Gateway - API Logging menu), it throws the following error:
```java
11:48:12.387 \[gravitee-listener-671\] ERROR i.g.r.a.service.impl.ApiServiceImpl - An error occurs while auditing API logging configuration for API: 8e6c1778-9a1e-41b1-ac17-789a1e41b101
11:48:12.387 \[gravitee-listener-671\] ERROR i.g.r.a.service.impl.ApiServiceImpl - An error occurs while auditing API logging configuration for API: 8e6c1778-9a1e-41b1-ac17-789a1e41b101
java.lang.NullPointerException: null
at io.gravitee.rest.api.service.impl.ApiServiceImpl.auditApiLogging(ApiServiceImpl.java:3400)
at io.gravitee.rest.api.service.impl.ApiServiceImpl.update(ApiServiceImpl.java:1649)
at jdk.internal.reflect.GeneratedMethodAccessor1997.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
```
## :sunrise_over_mountains: To Reproduce
Steps to reproduce the behaviour:
1. Create an API, activate the logging and export it
2. Go to Env Settings > Gateway - API Logging menu and activate `Generate API Logging audit events`
3. Update the exported API to remove the `logging` section
4. Go back on the API (in the console) and try to import the updated file
4. See error
## :rainbow: Expected behaviour
Everything should be fine, the API should be updated and logging deactivated for it.
## Current behavior
Import is failing.
## :movie_camera: Useful information
Do not forget to activate
```
Generate API Logging audit events (API_LOGGING_ENABLED, API_LOGGING_DISABLED, API_LOGGING_UPDATED)
```
This NPE was spotted by SonarCloud:
## :computer: Desktop:
NA
## :warning: Potential impacts
***Which other features may be impacted by this fix. This could be populated after fix***
***What are the impacted versions?***
3.10.x +
## :link: Dependencies
Link a story or other related things...
",0,error when importing an api without logging on an env with logging audit events activated collision describe the bug when trying to import an api without logging part on an env with generate api logging audit events api logging enabled api logging disabled api logging updated option activated available under env settings gateway api logging menu it throws the following error java error i g r a service impl apiserviceimpl an error occurs while auditing api logging configuration for api error i g r a service impl apiserviceimpl an error occurs while auditing api logging configuration for api java lang nullpointerexception null at io gravitee rest api service impl apiserviceimpl auditapilogging apiserviceimpl java at io gravitee rest api service impl apiserviceimpl update apiserviceimpl java at jdk internal reflect invoke unknown source at java base jdk internal reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java sunrise over mountains to reproduce steps to reproduce the behaviour create an api activate the logging and export it go to env settings gateway api logging menu and activate generate api logging audit events update the exported api to remove the logging section go back on the api in the console and try to import the updated file see error rainbow expected behaviour everything should be fine the api should be updated and logging deactivated for it current behavior import is failing movie camera useful information do not forget to activate generate api logging audit events api logging enabled api logging disabled api logging updated this npe was spotted by sonarcloud computer desktop na warning potential impacts which other features may be impacted by this fix this could be populated after fix what are the impacted versions x link dependencies link a story or other related things ,0