Unnamed: 0 int64 0 832k | id float64 2.49B 32.1B | type stringclasses 1 value | created_at stringlengths 19 19 | repo stringlengths 5 112 | repo_url stringlengths 34 141 | action stringclasses 3 values | title stringlengths 1 855 | labels stringlengths 4 721 | body stringlengths 1 261k | index stringclasses 13 values | text_combine stringlengths 96 261k | label stringclasses 2 values | text stringlengths 96 240k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
59,519 | 7,254,140,002 | IssuesEvent | 2018-02-16 09:46:22 | syndesisio/syndesis | https://api.github.com/repos/syndesisio/syndesis | closed | UX Design: Integration Activity (Formerly Logs) | cat/design group/uxd | Designs for viewing integration level activity.
Introduced tabs within Integration summary page, one of them being Activity. From there user can:
- View details of each integration run and status of individual steps within each run.
- View full output of a specific step within a run
- Filter integration runs via a new date range tool | 1.0 | UX Design: Integration Activity (Formerly Logs) - Designs for viewing integration level activity.
Introduced tabs within Integration summary page, one of them being Activity. From there user can:
- View details of each integration run and status of individual steps within each run.
- View full output of a specific step within a run
- Filter integration runs via a new date range tool | non_priority | ux design integration activity formerly logs designs for viewing integration level activity introduced tabs within integration summary page one of them being activity from there user can view details of each integration run and status of individual steps within each run view full output of a specific step within a run filter integration runs via a new date range tool | 0 |
30,093 | 24,537,481,994 | IssuesEvent | 2022-10-11 22:25:54 | iree-org/iree | https://api.github.com/repos/iree-org/iree | opened | Extend `iree_native_test`'s `TEST_INPUT_FILES_ARG` to support `iree-run-module`'s input files | enhancement ➕ infrastructure awaiting-triage | ### Request description
`TEST_INPUT_FILE_ARG` in https://github.com/iree-org/iree/blob/main/build_tools/cmake/iree_native_test.cmake can't support `iree-run-module` properly. To extend its capability
- [ ] make it a list argument, so it can take `--flagfile`, `--module_file`, --expected_output`
- [ ] parse the argument between the file path and the flag name so it can handle android on-device test properly
### What component(s) does this issue relate to?
Other
### Additional context
An `iree-run-module` specific workaround is in https://github.com/iree-org/iree/pull/10684, but it will be nice to have it consolidate with `iree_native_test` where all the on-device manipulations are. | 1.0 | Extend `iree_native_test`'s `TEST_INPUT_FILES_ARG` to support `iree-run-module`'s input files - ### Request description
`TEST_INPUT_FILE_ARG` in https://github.com/iree-org/iree/blob/main/build_tools/cmake/iree_native_test.cmake can't support `iree-run-module` properly. To extend its capability
- [ ] make it a list argument, so it can take `--flagfile`, `--module_file`, --expected_output`
- [ ] parse the argument between the file path and the flag name so it can handle android on-device test properly
### What component(s) does this issue relate to?
Other
### Additional context
An `iree-run-module` specific workaround is in https://github.com/iree-org/iree/pull/10684, but it will be nice to have it consolidate with `iree_native_test` where all the on-device manipulations are. | non_priority | extend iree native test s test input files arg to support iree run module s input files request description test input file arg in can t support iree run module properly to extend its capability make it a list argument so it can take flagfile module file expected output parse the argument between the file path and the flag name so it can handle android on device test properly what component s does this issue relate to other additional context an iree run module specific workaround is in but it will be nice to have it consolidate with iree native test where all the on device manipulations are | 0 |
58,933 | 6,623,945,987 | IssuesEvent | 2017-09-22 09:28:08 | mantidproject/mantidimaging | https://api.github.com/repos/mantidproject/mantidimaging | closed | Setup CI on Jenkins | Quality: Unit Testing | For now a manual build of `master` with Anaconda Python 2.7 and 3.5 running nosetests. | 1.0 | Setup CI on Jenkins - For now a manual build of `master` with Anaconda Python 2.7 and 3.5 running nosetests. | non_priority | setup ci on jenkins for now a manual build of master with anaconda python and running nosetests | 0 |
27,082 | 12,512,058,503 | IssuesEvent | 2020-06-02 21:50:17 | Ryujinx/Ryujinx-Games-List | https://api.github.com/repos/Ryujinx/Ryujinx-Games-List | opened | The Jackbox Party Pack | services status-menus | ## The Jackbox Party Pack
#### Current on `master` : 1.0.4675
Game loads to title screen but does not accept any input from the controls. Any attempt to cajole it into working results in the message in the console below.
```
ServiceAm .ctor: Applet 'PlayerSelect' created.
```
#### Screenshots :
#### Log file :
[TJPP.zip](https://github.com/Ryujinx/Ryujinx-Games-List/files/4719857/TJPP.zip)
| 1.0 | The Jackbox Party Pack - ## The Jackbox Party Pack
#### Current on `master` : 1.0.4675
Game loads to title screen but does not accept any input from the controls. Any attempt to cajole it into working results in the message in the console below.
```
ServiceAm .ctor: Applet 'PlayerSelect' created.
```
#### Screenshots :
#### Log file :
[TJPP.zip](https://github.com/Ryujinx/Ryujinx-Games-List/files/4719857/TJPP.zip)
| non_priority | the jackbox party pack the jackbox party pack current on master game loads to title screen but does not accept any input from the controls any attempt to cajole it into working results in the message in the console below serviceam ctor applet playerselect created screenshots log file | 0 |
3,670 | 6,543,167,781 | IssuesEvent | 2017-09-02 18:16:51 | STEllAR-GROUP/hpx | https://api.github.com/repos/STEllAR-GROUP/hpx | closed | Unify serialization of non-default-constructible types | category: serialization type: compatibility issue | Currently, serialization of non-default-constructible types is done differently for single instances and for collections of such types. This should be unified. | True | Unify serialization of non-default-constructible types - Currently, serialization of non-default-constructible types is done differently for single instances and for collections of such types. This should be unified. | non_priority | unify serialization of non default constructible types currently serialization of non default constructible types is done differently for single instances and for collections of such types this should be unified | 0 |
9,925 | 7,035,031,056 | IssuesEvent | 2017-12-27 20:39:11 | dotnet/roslyn | https://api.github.com/repos/dotnet/roslyn | closed | UI delay during solution load from analyzer dependency checker | Area-Analyzers Area-Performance Bug | A customer reported a very large UI delay on solution load, whose underlying cause was attempting to report analyzer dependency conflict diagnostic IDE1002 on UI thread during analyzer reference initialization. This is done on the UI thread by both legacy and new project systems. The root cause is that diagnostic reporting involves checking if diagnostic was suppressed or not, which requires binding and decoding all the global assembly level attributes. We can push the analyzer dependency conflict diagnostic reporting on background thread to avoid this UI delay. | True | UI delay during solution load from analyzer dependency checker - A customer reported a very large UI delay on solution load, whose underlying cause was attempting to report analyzer dependency conflict diagnostic IDE1002 on UI thread during analyzer reference initialization. This is done on the UI thread by both legacy and new project systems. The root cause is that diagnostic reporting involves checking if diagnostic was suppressed or not, which requires binding and decoding all the global assembly level attributes. We can push the analyzer dependency conflict diagnostic reporting on background thread to avoid this UI delay. | non_priority | ui delay during solution load from analyzer dependency checker a customer reported a very large ui delay on solution load whose underlying cause was attempting to report analyzer dependency conflict diagnostic on ui thread during analyzer reference initialization this is done on the ui thread by both legacy and new project systems the root cause is that diagnostic reporting involves checking if diagnostic was suppressed or not which requires binding and decoding all the global assembly level attributes we can push the analyzer dependency conflict diagnostic reporting on background thread to avoid this ui delay | 0 |
346,738 | 24,887,195,993 | IssuesEvent | 2022-10-28 08:48:17 | vvidday/ped | https://api.github.com/repos/vvidday/ped | opened | Minor typo in section 2.2.4 of UG | type.DocumentationBug severity.VeryLow | Another extremely minor typo, I think "oncurring" is meant to be "occurring".
<!--session: 1666943934473-b5fe9332-ec22-4959-b126-97da656ed362-->
<!--Version: Web v3.4.4--> | 1.0 | Minor typo in section 2.2.4 of UG - Another extremely minor typo, I think "oncurring" is meant to be "occurring".
<!--session: 1666943934473-b5fe9332-ec22-4959-b126-97da656ed362-->
<!--Version: Web v3.4.4--> | non_priority | minor typo in section of ug another extremely minor typo i think oncurring is meant to be occurring | 0 |
177,172 | 28,366,006,234 | IssuesEvent | 2023-04-12 13:56:42 | jpmorganchase/salt-ds | https://api.github.com/repos/jpmorganchase/salt-ds | opened | Spinner sizing | role: design 🎨 | Revisit and explore spinner sizing using **size-icon** rather than size-base foundation. Things to explore and consider:
- Potential need of a new small size group
- The size-compact for spinner's thickness scaling can present constrains | 1.0 | Spinner sizing - Revisit and explore spinner sizing using **size-icon** rather than size-base foundation. Things to explore and consider:
- Potential need of a new small size group
- The size-compact for spinner's thickness scaling can present constrains | non_priority | spinner sizing revisit and explore spinner sizing using size icon rather than size base foundation things to explore and consider potential need of a new small size group the size compact for spinner s thickness scaling can present constrains | 0 |
327,686 | 28,076,974,528 | IssuesEvent | 2023-03-30 01:04:44 | haskell/cabal | https://api.github.com/repos/haskell/cabal | opened | CI: cabal-testsuite tests fail with "double directory" | type: bug continuous-integration cabal-testsuite | It was observed earlier on Windows:
- #8739
but since GHC 9.6.1 it plagues the other platforms too. [Here's one recent CI run](https://github.com/haskell/cabal/actions/runs/4443872939/jobs/7801547699?pr=8840#step:19:36).
```
PackageTests/NewBuild/CmdRun/Terminate/cabal.test.hs:4:1: error:
Error: Ambiguous module name ‘System.Directory’:
it was found in multiple packages:
directory-1.3.8.1 directory-1.3.8.1
|
4 | import System.Directory (removeFile)
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
```
Due to this error I had to disable `cabal-testsuite` altogether for 9.6.1 in #8840. | 1.0 | CI: cabal-testsuite tests fail with "double directory" - It was observed earlier on Windows:
- #8739
but since GHC 9.6.1 it plagues the other platforms too. [Here's one recent CI run](https://github.com/haskell/cabal/actions/runs/4443872939/jobs/7801547699?pr=8840#step:19:36).
```
PackageTests/NewBuild/CmdRun/Terminate/cabal.test.hs:4:1: error:
Error: Ambiguous module name ‘System.Directory’:
it was found in multiple packages:
directory-1.3.8.1 directory-1.3.8.1
|
4 | import System.Directory (removeFile)
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
```
Due to this error I had to disable `cabal-testsuite` altogether for 9.6.1 in #8840. | non_priority | ci cabal testsuite tests fail with double directory it was observed earlier on windows but since ghc it plagues the other platforms too packagetests newbuild cmdrun terminate cabal test hs error error ambiguous module name ‘system directory’ it was found in multiple packages directory directory import system directory removefile due to this error i had to disable cabal testsuite altogether for in | 0 |
161,427 | 25,339,022,251 | IssuesEvent | 2022-11-18 19:35:16 | carbon-design-system/carbon-for-ibm-dotcom | https://api.github.com/repos/carbon-design-system/carbon-for-ibm-dotcom | opened | [Lead space] design research | design design: research | ### User story
As a Carbon for IBM.com Designer I need to review the lead space and background media specs so that I can understand how the lead space is constructed and identify the gaps in documentation for adopters.
#### Tasks
- [ ] Review the Lead space, Background media design specs, and both functional specs.
- [ ] Talk with Dev team about how it's working
- [ ] Determine if we need to make changes
- [ ] Determine where to update documentation to make it more clear for adopters.
### Additional Information
- **See the epic (#?epic issue?) for the overarching descriptions of the work.**
- [Lead space Figma import]()
- [Lead space Func specs]()
- [Background media Figma import]()
- [Background media Func specs]()
#### Acceptance Criteria
- [ ] Research findings are shared with Jeannie & Olivia
- [ ] We agree on next steps for design study
| 2.0 | [Lead space] design research - ### User story
As a Carbon for IBM.com Designer I need to review the lead space and background media specs so that I can understand how the lead space is constructed and identify the gaps in documentation for adopters.
#### Tasks
- [ ] Review the Lead space, Background media design specs, and both functional specs.
- [ ] Talk with Dev team about how it's working
- [ ] Determine if we need to make changes
- [ ] Determine where to update documentation to make it more clear for adopters.
### Additional Information
- **See the epic (#?epic issue?) for the overarching descriptions of the work.**
- [Lead space Figma import]()
- [Lead space Func specs]()
- [Background media Figma import]()
- [Background media Func specs]()
#### Acceptance Criteria
- [ ] Research findings are shared with Jeannie & Olivia
- [ ] We agree on next steps for design study
| non_priority | design research user story as a carbon for ibm com designer i need to review the lead space and background media specs so that i can understand how the lead space is constructed and identify the gaps in documentation for adopters tasks review the lead space background media design specs and both functional specs talk with dev team about how it s working determine if we need to make changes determine where to update documentation to make it more clear for adopters additional information see the epic epic issue for the overarching descriptions of the work acceptance criteria research findings are shared with jeannie olivia we agree on next steps for design study | 0 |
45,146 | 5,908,095,869 | IssuesEvent | 2017-05-19 19:25:05 | participedia/frontend | https://api.github.com/repos/participedia/frontend | closed | Default profile picture needed | design | **Sender**: amberfj@gmail.com
**Comment**: Default profile picture needed
[Open #21 in Usersnap Dashboard](https://usersnap.com/a/#/participedia-dev/p/participedia-ed971123/21)
**Notes**:
- (1) We need to design a default profile pic. if picture has not been uploaded by the user.
<a href='https://usersnappublic.s3.amazonaws.com/2017-05-17/19-55/52b067b9-9b9d-4b66-a0dd-69c272492aaf.png'></a>
<a href='https://usersnappublic.s3.amazonaws.com/2017-05-17/19-55/52b067b9-9b9d-4b66-a0dd-69c272492aaf.png'>Download original image</a>
**Browser**: Chrome 58 (macOS Sierra)
**Referer**: [https://participedia.xyz/users/169032](https://participedia.xyz/users/169032)
**Screen size**: 2560 x 1440 **Browser size**: 1622 x 1295
Powered by [usersnap.com](https://usersnap.com/?utm_source=github_entry&utm_medium=web&utm_campaign=product)
| 1.0 | Default profile picture needed - **Sender**: amberfj@gmail.com
**Comment**: Default profile picture needed
[Open #21 in Usersnap Dashboard](https://usersnap.com/a/#/participedia-dev/p/participedia-ed971123/21)
**Notes**:
- (1) We need to design a default profile pic. if picture has not been uploaded by the user.
<a href='https://usersnappublic.s3.amazonaws.com/2017-05-17/19-55/52b067b9-9b9d-4b66-a0dd-69c272492aaf.png'></a>
<a href='https://usersnappublic.s3.amazonaws.com/2017-05-17/19-55/52b067b9-9b9d-4b66-a0dd-69c272492aaf.png'>Download original image</a>
**Browser**: Chrome 58 (macOS Sierra)
**Referer**: [https://participedia.xyz/users/169032](https://participedia.xyz/users/169032)
**Screen size**: 2560 x 1440 **Browser size**: 1622 x 1295
Powered by [usersnap.com](https://usersnap.com/?utm_source=github_entry&utm_medium=web&utm_campaign=product)
| non_priority | default profile picture needed sender amberfj gmail com comment default profile picture needed notes we need to design a default profile pic if picture has not been uploaded by the user a href browser chrome macos sierra referer screen size x browser size x powered by | 0 |
171,957 | 14,348,395,003 | IssuesEvent | 2020-11-29 12:17:11 | fmm1005/GESPRO_PracticaGestionTareas_2021 | https://api.github.com/repos/fmm1005/GESPRO_PracticaGestionTareas_2021 | closed | Entrega TFG | documentation | ### A entregar:
- Secretaría:
- [ ] Memoria en formato impreso.
- [ ] Cinco discos memoria, anexos, fuentes del proyecto, aplicación, otros recursos (videos, máquinas virtuales, software
open source de terceros...) .
- [ ] Un disco con la memoria y anexos con dos resúmenes del trabajo (español y inglés).
- [ ] [Impresos de solicitud.](https://www.ubu.es/escuela-politecnica-superior/estructura-del-centro/impresos-solicitudes-peticiones/trabajo-fin-de-grado)
- UbuVirtual
- [ ] Memoria y anexos en asignatura TFG.
- [ ] Memoria y anexos en comunidad TFG.
Junto con el procedimiento de entrega fijado por el tribunal de TFG en la Secretaría Académica del centro, adicionalmente hay que depositar en UBUVirtual una copia del documento(s) pdf (bien con la memoria completa, o bien desglosada en memoria y anexos).
Este procedimiento es adicional, y NO sustituye en ningún caso a la entrega en Secretaría Académica del centro.
La tarea para realizar dicha entrega la tenéis disponible en el siguiente enlace,dentro de la comunidad habilitada para tal efecto (Comunidad de Trabajo Fin de Grado en Ingeniería Informática).
El nombre del fichero debe seguir el siguiente formato (si se entrega un único fichero):
GII_apellido1_apellido2_nombre_Enero_ 2017.pdf
o bien (si se entrega en dos partes):
GII_apellido1_apellido2_nombre_Enero_2017_memoria.pdf
GII_apellido1_apellido2_nombre_Enero_2017_anexos.pdf | 1.0 | Entrega TFG - ### A entregar:
- Secretaría:
- [ ] Memoria en formato impreso.
- [ ] Cinco discos memoria, anexos, fuentes del proyecto, aplicación, otros recursos (videos, máquinas virtuales, software
open source de terceros...) .
- [ ] Un disco con la memoria y anexos con dos resúmenes del trabajo (español y inglés).
- [ ] [Impresos de solicitud.](https://www.ubu.es/escuela-politecnica-superior/estructura-del-centro/impresos-solicitudes-peticiones/trabajo-fin-de-grado)
- UbuVirtual
- [ ] Memoria y anexos en asignatura TFG.
- [ ] Memoria y anexos en comunidad TFG.
Junto con el procedimiento de entrega fijado por el tribunal de TFG en la Secretaría Académica del centro, adicionalmente hay que depositar en UBUVirtual una copia del documento(s) pdf (bien con la memoria completa, o bien desglosada en memoria y anexos).
Este procedimiento es adicional, y NO sustituye en ningún caso a la entrega en Secretaría Académica del centro.
La tarea para realizar dicha entrega la tenéis disponible en el siguiente enlace,dentro de la comunidad habilitada para tal efecto (Comunidad de Trabajo Fin de Grado en Ingeniería Informática).
El nombre del fichero debe seguir el siguiente formato (si se entrega un único fichero):
GII_apellido1_apellido2_nombre_Enero_ 2017.pdf
o bien (si se entrega en dos partes):
GII_apellido1_apellido2_nombre_Enero_2017_memoria.pdf
GII_apellido1_apellido2_nombre_Enero_2017_anexos.pdf | non_priority | entrega tfg a entregar secretaría memoria en formato impreso cinco discos memoria anexos fuentes del proyecto aplicación otros recursos videos máquinas virtuales software open source de terceros un disco con la memoria y anexos con dos resúmenes del trabajo español y inglés ubuvirtual memoria y anexos en asignatura tfg memoria y anexos en comunidad tfg junto con el procedimiento de entrega fijado por el tribunal de tfg en la secretaría académica del centro adicionalmente hay que depositar en ubuvirtual una copia del documento s pdf bien con la memoria completa o bien desglosada en memoria y anexos este procedimiento es adicional y no sustituye en ningún caso a la entrega en secretaría académica del centro la tarea para realizar dicha entrega la tenéis disponible en el siguiente enlace dentro de la comunidad habilitada para tal efecto comunidad de trabajo fin de grado en ingeniería informática el nombre del fichero debe seguir el siguiente formato si se entrega un único fichero gii nombre enero pdf o bien si se entrega en dos partes gii nombre enero memoria pdf gii nombre enero anexos pdf | 0 |
32,413 | 8,851,546,966 | IssuesEvent | 2019-01-08 16:00:35 | mtgred/netrunner | https://api.github.com/repos/mtgred/netrunner | closed | Straighten out NRDB API migration issues | deckbuilder dev | Amongst others:
- deckbuilder stores the whole card identity data along with the deck. That's a recipe for problems if the card ever gets errata'd or their fields change (as it happened now, checking validity is now via `pack_code`, not `setname`)
- card fields are currently renamed by the `fetch.coffee` script to the old, depreciated ones. To reduce confusion and debugging times, the new terminology from API 2.0 should be used.
- consider referring to cards by their IDs instead of their names, as it is way more future-proof. Also, what if FFG prints another version of the card with the same name? It may mess up a bit current alt-arts implementation, though.
| 1.0 | Straighten out NRDB API migration issues - Amongst others:
- deckbuilder stores the whole card identity data along with the deck. That's a recipe for problems if the card ever gets errata'd or their fields change (as it happened now, checking validity is now via `pack_code`, not `setname`)
- card fields are currently renamed by the `fetch.coffee` script to the old, depreciated ones. To reduce confusion and debugging times, the new terminology from API 2.0 should be used.
- consider referring to cards by their IDs instead of their names, as it is way more future-proof. Also, what if FFG prints another version of the card with the same name? It may mess up a bit current alt-arts implementation, though.
| non_priority | straighten out nrdb api migration issues amongst others deckbuilder stores the whole card identity data along with the deck that s a recipe for problems if the card ever gets errata d or their fields change as it happened now checking validity is now via pack code not setname card fields are currently renamed by the fetch coffee script to the old depreciated ones to reduce confusion and debugging times the new terminology from api should be used consider referring to cards by their ids instead of their names as it is way more future proof also what if ffg prints another version of the card with the same name it may mess up a bit current alt arts implementation though | 0 |
18,657 | 10,272,270,273 | IssuesEvent | 2019-08-23 15:59:46 | dotnet/corefx | https://api.github.com/repos/dotnet/corefx | opened | Use a custom PFX/PKCS12 loader/exporter on non-Windows platforms | area-System.Security enhancement os-linux os-mac-os-x | We have a slew of bugs related to inconsistencies between the Windows PFX loader (PFXImportCertStore), the Unix PFX loader (PKCS12_parse), and the macOS PFX loader (SecItemImport), and their paired export functions:
* #2743
* #2745
* #2746
* #11046
* #16705
* #24225
* #24226
* #26397
* #30946
* #31746
* #37599
(And probably others)
Now that we have experience with manually loading PKCS#12/PFX content (the `Pkcs12Info` class) and writing it (`Pkcs12Builder`), we should just use a custom loader and unify the experience across the platforms. | True | Use a custom PFX/PKCS12 loader/exporter on non-Windows platforms - We have a slew of bugs related to inconsistencies between the Windows PFX loader (PFXImportCertStore), the Unix PFX loader (PKCS12_parse), and the macOS PFX loader (SecItemImport), and their paired export functions:
* #2743
* #2745
* #2746
* #11046
* #16705
* #24225
* #24226
* #26397
* #30946
* #31746
* #37599
(And probably others)
Now that we have experience with manually loading PKCS#12/PFX content (the `Pkcs12Info` class) and writing it (`Pkcs12Builder`), we should just use a custom loader and unify the experience across the platforms. | non_priority | use a custom pfx loader exporter on non windows platforms we have a slew of bugs related to inconsistencies between the windows pfx loader pfximportcertstore the unix pfx loader parse and the macos pfx loader secitemimport and their paired export functions and probably others now that we have experience with manually loading pkcs pfx content the class and writing it we should just use a custom loader and unify the experience across the platforms | 0 |
187,174 | 14,427,197,674 | IssuesEvent | 2020-12-06 02:30:40 | kalexmills/github-vet-tests-dec2020 | https://api.github.com/repos/kalexmills/github-vet-tests-dec2020 | closed | Karthi96/ps1: vendor/github.com/google/certificate-transparency-go/fixchain/fixer_test.go; 27 LoC | fresh small test vendored |
Found a possible issue in [Karthi96/ps1](https://www.github.com/Karthi96/ps1) at [vendor/github.com/google/certificate-transparency-go/fixchain/fixer_test.go](https://github.com/Karthi96/ps1/blob/3edbd1a5ea423d6ccd21a4ebedf1fbd923514a46/vendor/github.com/google/certificate-transparency-go/fixchain/fixer_test.go#L70-L96)
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 i used in defer or goroutine at line 80
[Click here to see the code in its original context.](https://github.com/Karthi96/ps1/blob/3edbd1a5ea423d6ccd21a4ebedf1fbd923514a46/vendor/github.com/google/certificate-transparency-go/fixchain/fixer_test.go#L70-L96)
<details>
<summary>Click here to show the 27 line(s) of Go which triggered the analyzer.</summary>
```go
for i, fst := range fixServerTests {
chains := make(chan []*x509.Certificate)
errors := make(chan *FixError)
f.toFix = make(chan *toFix)
f.chains = chains
f.errors = errors
wg.Add(2)
go func() {
defer wg.Done()
testChains(t, i, fst.expectedChains, chains)
}()
go func() {
defer wg.Done()
testErrors(t, i, fst.expectedErrs, errors)
}()
f.wg.Add(1)
go f.fixServer()
f.QueueChain(GetTestCertificateFromPEM(t, fst.cert),
extractTestChain(t, i, fst.chain), extractTestRoots(t, i, fst.roots))
f.Wait()
close(chains)
close(errors)
wg.Wait()
}
```
</details>
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: 3edbd1a5ea423d6ccd21a4ebedf1fbd923514a46
| 1.0 | Karthi96/ps1: vendor/github.com/google/certificate-transparency-go/fixchain/fixer_test.go; 27 LoC -
Found a possible issue in [Karthi96/ps1](https://www.github.com/Karthi96/ps1) at [vendor/github.com/google/certificate-transparency-go/fixchain/fixer_test.go](https://github.com/Karthi96/ps1/blob/3edbd1a5ea423d6ccd21a4ebedf1fbd923514a46/vendor/github.com/google/certificate-transparency-go/fixchain/fixer_test.go#L70-L96)
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 i used in defer or goroutine at line 80
[Click here to see the code in its original context.](https://github.com/Karthi96/ps1/blob/3edbd1a5ea423d6ccd21a4ebedf1fbd923514a46/vendor/github.com/google/certificate-transparency-go/fixchain/fixer_test.go#L70-L96)
<details>
<summary>Click here to show the 27 line(s) of Go which triggered the analyzer.</summary>
```go
for i, fst := range fixServerTests {
chains := make(chan []*x509.Certificate)
errors := make(chan *FixError)
f.toFix = make(chan *toFix)
f.chains = chains
f.errors = errors
wg.Add(2)
go func() {
defer wg.Done()
testChains(t, i, fst.expectedChains, chains)
}()
go func() {
defer wg.Done()
testErrors(t, i, fst.expectedErrs, errors)
}()
f.wg.Add(1)
go f.fixServer()
f.QueueChain(GetTestCertificateFromPEM(t, fst.cert),
extractTestChain(t, i, fst.chain), extractTestRoots(t, i, fst.roots))
f.Wait()
close(chains)
close(errors)
wg.Wait()
}
```
</details>
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: 3edbd1a5ea423d6ccd21a4ebedf1fbd923514a46
| non_priority | vendor github com google certificate transparency go fixchain fixer 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 i used in defer or goroutine at line click here to show the line s of go which triggered the analyzer go for i fst range fixservertests chains make chan certificate errors make chan fixerror f tofix make chan tofix f chains chains f errors errors wg add go func defer wg done testchains t i fst expectedchains chains go func defer wg done testerrors t i fst expectederrs errors f wg add go f fixserver f queuechain gettestcertificatefrompem t fst cert extracttestchain t i fst chain extracttestroots t i fst roots f wait close chains close errors wg wait 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 |
166,198 | 14,021,779,624 | IssuesEvent | 2020-10-29 21:54:31 | matplotlib/matplotlib | https://api.github.com/repos/matplotlib/matplotlib | closed | Installing from source on windows, documentation | Documentation OS/Microsoft | I finally managed to install matplotlib from source in developing mode thanks to the new build documentation
https://matplotlib.org/users/installing.html
https://matplotlib.org/devdocs/users/installing.html
but it can be improved and I have some questions. I don't really know much about
`python setyp.py develop` vs `pip install -e`, wheels, `python -mpip install -ve .`, `python setup.py bdist_wheel` etc (but more now than before) and I find it quite hard to find relevant information.
I use conda and "wheel builds using conda packages" worked when I understood that the `build_alllocals.cmd ` resulted in a `.whl` file that I should install with `pip install dist/filename.whl`. The problem was that the `-e` flag didn't work so my local files where not used when I used matplotlib.
I tried to change `bdist_wheel` in the `build_alllocal.cmd` to `develop` and it worked in one step to get an develop installation.
So are there any reason why the suggested steps are
```
python setup.py bdist_wheel
pip install dist/filename.whl
```
and not just `python setup.py` or `python setup.py -e`?
A few more words in the documentation about details and difference between an installation in develop mode and a standard installation would probably make it much easier for people like me, that don't really know the details about all python setup tools, to install matplotlib from source.
| 1.0 | Installing from source on windows, documentation - I finally managed to install matplotlib from source in developing mode thanks to the new build documentation
https://matplotlib.org/users/installing.html
https://matplotlib.org/devdocs/users/installing.html
but it can be improved and I have some questions. I don't really know much about
`python setyp.py develop` vs `pip install -e`, wheels, `python -mpip install -ve .`, `python setup.py bdist_wheel` etc (but more now than before) and I find it quite hard to find relevant information.
I use conda and "wheel builds using conda packages" worked when I understood that the `build_alllocals.cmd ` resulted in a `.whl` file that I should install with `pip install dist/filename.whl`. The problem was that the `-e` flag didn't work so my local files where not used when I used matplotlib.
I tried to change `bdist_wheel` in the `build_alllocal.cmd` to `develop` and it worked in one step to get an develop installation.
So are there any reason why the suggested steps are
```
python setup.py bdist_wheel
pip install dist/filename.whl
```
and not just `python setup.py` or `python setup.py -e`?
A few more words in the documentation about details and difference between an installation in develop mode and a standard installation would probably make it much easier for people like me, that don't really know the details about all python setup tools, to install matplotlib from source.
| non_priority | installing from source on windows documentation i finally managed to install matplotlib from source in developing mode thanks to the new build documentation but it can be improved and i have some questions i don t really know much about python setyp py develop vs pip install e wheels python mpip install ve python setup py bdist wheel etc but more now than before and i find it quite hard to find relevant information i use conda and wheel builds using conda packages worked when i understood that the build alllocals cmd resulted in a whl file that i should install with pip install dist filename whl the problem was that the e flag didn t work so my local files where not used when i used matplotlib i tried to change bdist wheel in the build alllocal cmd to develop and it worked in one step to get an develop installation so are there any reason why the suggested steps are python setup py bdist wheel pip install dist filename whl and not just python setup py or python setup py e a few more words in the documentation about details and difference between an installation in develop mode and a standard installation would probably make it much easier for people like me that don t really know the details about all python setup tools to install matplotlib from source | 0 |
182,422 | 30,847,351,744 | IssuesEvent | 2023-08-02 14:30:09 | GCTC-NTGC/gc-digital-talent | https://api.github.com/repos/GCTC-NTGC/gc-digital-talent | closed | 📐 Building a better combobox (single select) | blocked: design updates in progress | # ⚙️ Summary
### [Visit the Figma file](https://www.figma.com/file/T1R64oNWog10OXiBnuiMkz/Component-library-(GC-Digital-Talent)?node-id=171%3A1557)
@esizer and I feel like we need to better address the combobox (select + keyword) element and its accessibility concerns. Our current third-party component is failing accessibility needs in multiple ways, and so we're setting out to build or find something better that meets the criteria below. Note that this focuses exclusively on a single-select combobox, as we'll expand the component to multi-select at a later time.
## 💾 Files and resources
- N/A
## ✅ Design checklist
- [ ] Component library elements have been used where appropriate
- [ ] Component library elements have been updated where changes where required
- [ ] Newly added interface elements have been added to the component library for reuse
- [ ] Newly added interface elements have been added to Github Discussions using the component issue template
- [ ] The interface is responsive or provides responsive context
- [ ] The interface provides both light and dark mode designs
- [x] Complex interactions have been prototyped in a way that showcases every step in the flow
- [x] Empty/null states have been accounted for
- [x] The design has been reviewed by at least one other team member
- [ ] The design has been presented to the design team
- [ ] The design has been approved by stakeholders
## ✅ Accessibility checklist
**Please refer to [the comprehensive list](https://www.figma.com/file/rRMvm5nq4AMet29PW7bN2p/A11y-annotations?node-id=0%3A1) for more details.**
- [x] Links have meaningful label text
- [x] Navigation matches previously established patterns
- [x] Headings are identified using annotations and follow a logical hierarchy
- [x] Layout is linear and consistent with established patterns
- [ ] New interactive elements have unique focus states that match the established pattern
- [x] Tab order has been identified using annotations
- [ ] Relevant images and icons have appropriate `alt` text
- [x] Use of color meets AA WCAG contrast requirements
- [x] States or information are not identified by color alone
- [x] New interactive elements have appropriately sized touch targets on touch devices
## 📸 Screenshot
# ✅ Requirements
- [ ] The input should provide a text-based input that triggers a select-style dropdown
- [ ] When the user types in the input, the select's options should return search results for the typed value
- [ ] The user should be able to clear the input using a fixed `x` button
- [ ] The results should accommodate both a "loading" and "no results" state
- [ ] If the user hasn't typed in the input but opens the select options, it should contain ALL available options in alphabetical order
- [ ] The results UI should be navigable using arrow keys, and the `esc` key should close the results and focus the input
- [ ] The search should indicate to assistive tech how many results are being presented, as well as both "loading" and "no results" states
- [ ] The results UI should be limited in height, with a visual affordance indicating that the list is scrollable - this is to help prevent extreme lists of results overlapping critical UI, as well as aiding in responsive navigation of long lists
- [ ] Pressing `enter` while typing in the search should focus the first result in the list
## 🛠️ Clear-able keyword value
Once a value has been typed or selected from the results list, an `x` button should appear next to the caret that when triggered, clears the keywords or selected items.
## 🛠️ Fixed, scrollable results length
The results list should show between 5-7 results and allow the user to scroll to view more. If more than 5-7 results are a part of the list, the results UI should offer a visual affordance (the shadow) indicating to the user that the list can be scrolled for more results.
## 🛠️ Loading state
To account for instances where loading results takes an extended period of time, a loading state should present itself (ideally with an animated icon) to provide immediate feedback that the application is processing the request.
## 🛠️ Alphabetical default results
If the user opens the combobox without typing in a query, they should be provided with a full list of all possible results, ordered in alphabetical order.
## 🛠️ No results found state
If the user has provided a keyword or external filter settings that results in no matching results, the results UI should notify them that no results can be found and that they should try different keywords/filters.
## 🙀 Optional requirements
### Results ordered by relevance
In an ideal world, the combobox should act like a proper search (particularly for our 140+ skills library), and this means having proper keyword relationships to help surface relevant results. For example, searching "Prototyping" shouldn't just return skills with "Prototyping" in their name, but also "Wireframing", "Interface design", etc.
# 🤔 Outstanding concerns
- Multi-select values will be handled later, though the component in Figma does present a possible approach
- There are a variety of accessibility concerns with this interface given its complexity. We should be recording decisions as we make them in reference to both testing and research.
# 📝 Related issues
**Please link all design and development sub-tasks related to this issue here for tracking purposes.**
- #5053
| 1.0 | 📐 Building a better combobox (single select) - # ⚙️ Summary
### [Visit the Figma file](https://www.figma.com/file/T1R64oNWog10OXiBnuiMkz/Component-library-(GC-Digital-Talent)?node-id=171%3A1557)
@esizer and I feel like we need to better address the combobox (select + keyword) element and its accessibility concerns. Our current third-party component is failing accessibility needs in multiple ways, and so we're setting out to build or find something better that meets the criteria below. Note that this focuses exclusively on a single-select combobox, as we'll expand the component to multi-select at a later time.
## 💾 Files and resources
- N/A
## ✅ Design checklist
- [ ] Component library elements have been used where appropriate
- [ ] Component library elements have been updated where changes where required
- [ ] Newly added interface elements have been added to the component library for reuse
- [ ] Newly added interface elements have been added to Github Discussions using the component issue template
- [ ] The interface is responsive or provides responsive context
- [ ] The interface provides both light and dark mode designs
- [x] Complex interactions have been prototyped in a way that showcases every step in the flow
- [x] Empty/null states have been accounted for
- [x] The design has been reviewed by at least one other team member
- [ ] The design has been presented to the design team
- [ ] The design has been approved by stakeholders
## ✅ Accessibility checklist
**Please refer to [the comprehensive list](https://www.figma.com/file/rRMvm5nq4AMet29PW7bN2p/A11y-annotations?node-id=0%3A1) for more details.**
- [x] Links have meaningful label text
- [x] Navigation matches previously established patterns
- [x] Headings are identified using annotations and follow a logical hierarchy
- [x] Layout is linear and consistent with established patterns
- [ ] New interactive elements have unique focus states that match the established pattern
- [x] Tab order has been identified using annotations
- [ ] Relevant images and icons have appropriate `alt` text
- [x] Use of color meets AA WCAG contrast requirements
- [x] States or information are not identified by color alone
- [x] New interactive elements have appropriately sized touch targets on touch devices
## 📸 Screenshot
# ✅ Requirements
- [ ] The input should provide a text-based input that triggers a select-style dropdown
- [ ] When the user types in the input, the select's options should return search results for the typed value
- [ ] The user should be able to clear the input using a fixed `x` button
- [ ] The results should accommodate both a "loading" and "no results" state
- [ ] If the user hasn't typed in the input but opens the select options, it should contain ALL available options in alphabetical order
- [ ] The results UI should be navigable using arrow keys, and the `esc` key should close the results and focus the input
- [ ] The search should indicate to assistive tech how many results are being presented, as well as both "loading" and "no results" states
- [ ] The results UI should be limited in height, with a visual affordance indicating that the list is scrollable - this is to help prevent extreme lists of results overlapping critical UI, as well as aiding in responsive navigation of long lists
- [ ] Pressing `enter` while typing in the search should focus the first result in the list
## 🛠️ Clear-able keyword value
Once a value has been typed or selected from the results list, an `x` button should appear next to the caret that when triggered, clears the keywords or selected items.
## 🛠️ Fixed, scrollable results length
The results list should show between 5-7 results and allow the user to scroll to view more. If more than 5-7 results are a part of the list, the results UI should offer a visual affordance (the shadow) indicating to the user that the list can be scrolled for more results.
## 🛠️ Loading state
To account for instances where loading results takes an extended period of time, a loading state should present itself (ideally with an animated icon) to provide immediate feedback that the application is processing the request.
## 🛠️ Alphabetical default results
If the user opens the combobox without typing in a query, they should be provided with a full list of all possible results, ordered in alphabetical order.
## 🛠️ No results found state
If the user has provided a keyword or external filter settings that results in no matching results, the results UI should notify them that no results can be found and that they should try different keywords/filters.
## 🙀 Optional requirements
### Results ordered by relevance
In an ideal world, the combobox should act like a proper search (particularly for our 140+ skills library), and this means having proper keyword relationships to help surface relevant results. For example, searching "Prototyping" shouldn't just return skills with "Prototyping" in their name, but also "Wireframing", "Interface design", etc.
# 🤔 Outstanding concerns
- Multi-select values will be handled later, though the component in Figma does present a possible approach
- There are a variety of accessibility concerns with this interface given its complexity. We should be recording decisions as we make them in reference to both testing and research.
# 📝 Related issues
**Please link all design and development sub-tasks related to this issue here for tracking purposes.**
- #5053
| non_priority | 📐 building a better combobox single select ⚙️ summary esizer and i feel like we need to better address the combobox select keyword element and its accessibility concerns our current third party component is failing accessibility needs in multiple ways and so we re setting out to build or find something better that meets the criteria below note that this focuses exclusively on a single select combobox as we ll expand the component to multi select at a later time 💾 files and resources n a ✅ design checklist component library elements have been used where appropriate component library elements have been updated where changes where required newly added interface elements have been added to the component library for reuse newly added interface elements have been added to github discussions using the component issue template the interface is responsive or provides responsive context the interface provides both light and dark mode designs complex interactions have been prototyped in a way that showcases every step in the flow empty null states have been accounted for the design has been reviewed by at least one other team member the design has been presented to the design team the design has been approved by stakeholders ✅ accessibility checklist please refer to for more details links have meaningful label text navigation matches previously established patterns headings are identified using annotations and follow a logical hierarchy layout is linear and consistent with established patterns new interactive elements have unique focus states that match the established pattern tab order has been identified using annotations relevant images and icons have appropriate alt text use of color meets aa wcag contrast requirements states or information are not identified by color alone new interactive elements have appropriately sized touch targets on touch devices 📸 screenshot ✅ requirements the input should provide a text based input that triggers a select style dropdown when the user types in the input the select s options should return search results for the typed value the user should be able to clear the input using a fixed x button the results should accommodate both a loading and no results state if the user hasn t typed in the input but opens the select options it should contain all available options in alphabetical order the results ui should be navigable using arrow keys and the esc key should close the results and focus the input the search should indicate to assistive tech how many results are being presented as well as both loading and no results states the results ui should be limited in height with a visual affordance indicating that the list is scrollable this is to help prevent extreme lists of results overlapping critical ui as well as aiding in responsive navigation of long lists pressing enter while typing in the search should focus the first result in the list 🛠️ clear able keyword value once a value has been typed or selected from the results list an x button should appear next to the caret that when triggered clears the keywords or selected items 🛠️ fixed scrollable results length the results list should show between results and allow the user to scroll to view more if more than results are a part of the list the results ui should offer a visual affordance the shadow indicating to the user that the list can be scrolled for more results 🛠️ loading state to account for instances where loading results takes an extended period of time a loading state should present itself ideally with an animated icon to provide immediate feedback that the application is processing the request 🛠️ alphabetical default results if the user opens the combobox without typing in a query they should be provided with a full list of all possible results ordered in alphabetical order 🛠️ no results found state if the user has provided a keyword or external filter settings that results in no matching results the results ui should notify them that no results can be found and that they should try different keywords filters 🙀 optional requirements results ordered by relevance in an ideal world the combobox should act like a proper search particularly for our skills library and this means having proper keyword relationships to help surface relevant results for example searching prototyping shouldn t just return skills with prototyping in their name but also wireframing interface design etc 🤔 outstanding concerns multi select values will be handled later though the component in figma does present a possible approach there are a variety of accessibility concerns with this interface given its complexity we should be recording decisions as we make them in reference to both testing and research 📝 related issues please link all design and development sub tasks related to this issue here for tracking purposes | 0 |
72,885 | 7,314,407,704 | IssuesEvent | 2018-03-01 07:01:00 | rancher/rancher | https://api.github.com/repos/rancher/rancher | closed | Add View in API in Pipeline menu | area/pipeline area/ui kind/bug status/resolved status/to-test team/cn version/2.0 | **Rancher versions:** 2.0 master 2/27
**Steps to Reproduce:**
1. Create a pipeline
2. Go to the menu for that pipeline
**Results:** No View in API. Please add View in API.
| 1.0 | Add View in API in Pipeline menu - **Rancher versions:** 2.0 master 2/27
**Steps to Reproduce:**
1. Create a pipeline
2. Go to the menu for that pipeline
**Results:** No View in API. Please add View in API.
| non_priority | add view in api in pipeline menu rancher versions master steps to reproduce create a pipeline go to the menu for that pipeline results no view in api please add view in api | 0 |
162,608 | 12,682,865,537 | IssuesEvent | 2020-06-19 18:21:41 | haskell-unordered-containers/unordered-containers | https://api.github.com/repos/haskell-unordered-containers/unordered-containers | opened | Test coverage | tests | I just ran `stack test --coverage` on https://github.com/haskell-unordered-containers/unordered-containers/commit/964edca40d415c7f0b70c99fda2a4d9dc0949b9f. Here's the summary of the combined coverage report for all testsuites:
Not terrible, but could be better. Maybe there's even some dead code we could get rid of? | 1.0 | Test coverage - I just ran `stack test --coverage` on https://github.com/haskell-unordered-containers/unordered-containers/commit/964edca40d415c7f0b70c99fda2a4d9dc0949b9f. Here's the summary of the combined coverage report for all testsuites:
Not terrible, but could be better. Maybe there's even some dead code we could get rid of? | non_priority | test coverage i just ran stack test coverage on here s the summary of the combined coverage report for all testsuites not terrible but could be better maybe there s even some dead code we could get rid of | 0 |
139,212 | 31,281,438,354 | IssuesEvent | 2023-08-22 09:50:12 | FerretDB/dance | https://api.github.com/repos/FerretDB/dance | opened | Split configuration loading into two package | code/chore | Currently, dance has structures and functions that load and parse YAML configuration files and transform them into a form used by other packages all in one package. Some `struct`s have two representations (`Results` and `ResultsYAML`), while others have only one used in both contexts (`Stats`). That makes it harder to introduce new features (#463) and already lead to one abandoned PR (#327).
We should this code into two packages: `internal/config` and `internal/configload`. The first one should be used by other packages and "business logic", while the second should export a single `Load` function that would return `internal/config.Config` `struct`.
Do not do other features or refactorings in this issue. | 1.0 | Split configuration loading into two package - Currently, dance has structures and functions that load and parse YAML configuration files and transform them into a form used by other packages all in one package. Some `struct`s have two representations (`Results` and `ResultsYAML`), while others have only one used in both contexts (`Stats`). That makes it harder to introduce new features (#463) and already lead to one abandoned PR (#327).
We should this code into two packages: `internal/config` and `internal/configload`. The first one should be used by other packages and "business logic", while the second should export a single `Load` function that would return `internal/config.Config` `struct`.
Do not do other features or refactorings in this issue. | non_priority | split configuration loading into two package currently dance has structures and functions that load and parse yaml configuration files and transform them into a form used by other packages all in one package some struct s have two representations results and resultsyaml while others have only one used in both contexts stats that makes it harder to introduce new features and already lead to one abandoned pr we should this code into two packages internal config and internal configload the first one should be used by other packages and business logic while the second should export a single load function that would return internal config config struct do not do other features or refactorings in this issue | 0 |
232,386 | 25,577,331,241 | IssuesEvent | 2022-11-30 23:40:51 | pactflow/example-siren | https://api.github.com/repos/pactflow/example-siren | opened | CVE-2022-42004 (High) detected in jackson-databind-2.11.2.jar | security vulnerability | ## CVE-2022-42004 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.11.2.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: /provider/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.11.2/ee08bbd8975dde844307fe8309dfcd5ec7ee129d/jackson-databind-2.11.2.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-hateoas-2.3.4.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.3.4.RELEASE.jar
- spring-boot-starter-json-2.3.4.RELEASE.jar
- :x: **jackson-databind-2.11.2.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/pactflow/example-siren/commit/abf5caaa6d058965a4210a43025377f4ad3732f6">abf5caaa6d058965a4210a43025377f4ad3732f6</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In FasterXML jackson-databind before 2.13.4, resource exhaustion can occur because of a lack of a check in BeanDeserializer._deserializeFromArray to prevent use of deeply nested arrays. An application is vulnerable only with certain customized choices for deserialization.
<p>Publish Date: 2022-10-02
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-42004>CVE-2022-42004</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2022-10-02</p>
<p>Fix Resolution (com.fasterxml.jackson.core:jackson-databind): 2.13.4</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-hateoas): 2.6.12</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
| True | CVE-2022-42004 (High) detected in jackson-databind-2.11.2.jar - ## CVE-2022-42004 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.11.2.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: /provider/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.11.2/ee08bbd8975dde844307fe8309dfcd5ec7ee129d/jackson-databind-2.11.2.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-hateoas-2.3.4.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.3.4.RELEASE.jar
- spring-boot-starter-json-2.3.4.RELEASE.jar
- :x: **jackson-databind-2.11.2.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/pactflow/example-siren/commit/abf5caaa6d058965a4210a43025377f4ad3732f6">abf5caaa6d058965a4210a43025377f4ad3732f6</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In FasterXML jackson-databind before 2.13.4, resource exhaustion can occur because of a lack of a check in BeanDeserializer._deserializeFromArray to prevent use of deeply nested arrays. An application is vulnerable only with certain customized choices for deserialization.
<p>Publish Date: 2022-10-02
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-42004>CVE-2022-42004</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2022-10-02</p>
<p>Fix Resolution (com.fasterxml.jackson.core:jackson-databind): 2.13.4</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-hateoas): 2.6.12</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
| non_priority | cve high detected in jackson databind jar cve high severity vulnerability vulnerable library jackson databind jar general data binding functionality for jackson works on core streaming api library home page a href path to dependency file provider build gradle path to vulnerable library home wss scanner gradle caches modules files com fasterxml jackson core jackson databind jackson databind jar dependency hierarchy spring boot starter hateoas release jar root library spring boot starter web release jar spring boot starter json release jar x jackson databind jar vulnerable library found in head commit a href found in base branch master vulnerability details in fasterxml jackson databind before resource exhaustion can occur because of a lack of a check in beandeserializer deserializefromarray to prevent use of deeply nested arrays an application is vulnerable only with certain customized choices for deserialization publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version release date fix resolution com fasterxml jackson core jackson databind direct dependency fix resolution org springframework boot spring boot starter hateoas check this box to open an automated fix pr | 0 |
59,738 | 14,642,924,797 | IssuesEvent | 2020-12-25 13:40:13 | cucumber/cucumber | https://api.github.com/repos/cucumber/cucumber | closed | gherkin-c does not build with MSVC | Stale language: c library: gherkin type: build | Acceptance Criteria:
- gherkin-c can build with msvc
## Summary
MSVC includes the library m.lib in the default CRT. Explicitly linking causes the build to fail.
## Expected Behavior
gerkin-c builds successfully by following the build instructions in readme.md
## Current Behavior
C:\dev\extern\cucumber\gherkin\c\out\build\x64-Debug (default)\LINK : fatal error LNK1104: cannot open file 'm.lib'
## Possible Solution
Add check for existance of m.lib and if exists, then link it in
```
include(CheckLibraryExists)
CHECK_LIBRARY_EXISTS(m log10 "" HAVE_LIB_M)
if (HAVE_LIB_M)
target_link_libraries(gherkin PRIVATE m)
endif (HAVE_LIB_M)
```
## Context & Motivation
Support all the platforms
## Your Environment
MSVC 16.8.442.31521 | 1.0 | gherkin-c does not build with MSVC - Acceptance Criteria:
- gherkin-c can build with msvc
## Summary
MSVC includes the library m.lib in the default CRT. Explicitly linking causes the build to fail.
## Expected Behavior
gerkin-c builds successfully by following the build instructions in readme.md
## Current Behavior
C:\dev\extern\cucumber\gherkin\c\out\build\x64-Debug (default)\LINK : fatal error LNK1104: cannot open file 'm.lib'
## Possible Solution
Add check for existance of m.lib and if exists, then link it in
```
include(CheckLibraryExists)
CHECK_LIBRARY_EXISTS(m log10 "" HAVE_LIB_M)
if (HAVE_LIB_M)
target_link_libraries(gherkin PRIVATE m)
endif (HAVE_LIB_M)
```
## Context & Motivation
Support all the platforms
## Your Environment
MSVC 16.8.442.31521 | non_priority | gherkin c does not build with msvc acceptance criteria gherkin c can build with msvc summary msvc includes the library m lib in the default crt explicitly linking causes the build to fail expected behavior gerkin c builds successfully by following the build instructions in readme md current behavior c dev extern cucumber gherkin c out build debug default link fatal error cannot open file m lib possible solution add check for existance of m lib and if exists then link it in include checklibraryexists check library exists m have lib m if have lib m target link libraries gherkin private m endif have lib m context motivation support all the platforms your environment msvc | 0 |
83,172 | 23,994,677,765 | IssuesEvent | 2022-09-14 06:25:07 | X-Sharp/XSharpPublic | https://api.github.com/repos/X-Sharp/XSharpPublic | closed | VS 2022 and XS 2.13.1.1 First builds not starting together with Nuget usage | MsBuild | **Describe the bug**
The first build does not start. It is necessary to try to leave VS. When the message about "build must be cancelled" appears, the build starts normally.
This happens when Nuget Package Manager options "Allow Nuget to download missing packages and automatically check for missing packages during build in Visual Studio" are enabled.
**To Reproduce**
Solution ACSLIB has been sent to Robert.
**Expected behavior**
Same as with X#-Version from June: normal starting of the build.
**Screenshots**
See attached file.
**Additional context**
Add any other context about the problem here.
[RE VS 2022 and XS 2.13.1.1 First builds not starting.zip](https://github.com/X-Sharp/XSharpPublic/files/9525263/RE.VS.2022.and.XS.2.13.1.1.First.builds.not.starting.zip)
| 1.0 | VS 2022 and XS 2.13.1.1 First builds not starting together with Nuget usage - **Describe the bug**
The first build does not start. It is necessary to try to leave VS. When the message about "build must be cancelled" appears, the build starts normally.
This happens when Nuget Package Manager options "Allow Nuget to download missing packages and automatically check for missing packages during build in Visual Studio" are enabled.
**To Reproduce**
Solution ACSLIB has been sent to Robert.
**Expected behavior**
Same as with X#-Version from June: normal starting of the build.
**Screenshots**
See attached file.
**Additional context**
Add any other context about the problem here.
[RE VS 2022 and XS 2.13.1.1 First builds not starting.zip](https://github.com/X-Sharp/XSharpPublic/files/9525263/RE.VS.2022.and.XS.2.13.1.1.First.builds.not.starting.zip)
| non_priority | vs and xs first builds not starting together with nuget usage describe the bug the first build does not start it is necessary to try to leave vs when the message about build must be cancelled appears the build starts normally this happens when nuget package manager options allow nuget to download missing packages and automatically check for missing packages during build in visual studio are enabled to reproduce solution acslib has been sent to robert expected behavior same as with x version from june normal starting of the build screenshots see attached file additional context add any other context about the problem here | 0 |
22,944 | 3,808,182,226 | IssuesEvent | 2016-03-25 13:46:08 | duckduckgo/zeroclickinfo-goodies | https://api.github.com/repos/duckduckgo/zeroclickinfo-goodies | opened | Ascii to Binary: Should have an options to separate output into sets of 4 bits | Design Maintainer Input Requested Suggestion | Suggested through DDG Feedback
This would probably require JS unless we permanently change the output format from the Perl
------
IA Page: http://duck.co/ia/view/binary
[Maintainer](http://docs.duckduckhack.com/maintaining/guidelines.html): @hunterlang | 1.0 | Ascii to Binary: Should have an options to separate output into sets of 4 bits - Suggested through DDG Feedback
This would probably require JS unless we permanently change the output format from the Perl
------
IA Page: http://duck.co/ia/view/binary
[Maintainer](http://docs.duckduckhack.com/maintaining/guidelines.html): @hunterlang | non_priority | ascii to binary should have an options to separate output into sets of bits suggested through ddg feedback this would probably require js unless we permanently change the output format from the perl ia page hunterlang | 0 |
56,984 | 13,960,927,852 | IssuesEvent | 2020-10-24 23:55:57 | rubyforgood/casa | https://api.github.com/repos/rubyforgood/casa | closed | Supervisor/admin should be able to edit case contacts from the /case_contacts page | not-ready-to-build | **What type of user is this for? volunteer/supervisor/admin/all**
supervisor/admin
**Description**
Supervisors should be able to edit case contacts from the /case_contacts page
**Screenshots of current behavior, if any**
| 1.0 | Supervisor/admin should be able to edit case contacts from the /case_contacts page - **What type of user is this for? volunteer/supervisor/admin/all**
supervisor/admin
**Description**
Supervisors should be able to edit case contacts from the /case_contacts page
**Screenshots of current behavior, if any**
| non_priority | supervisor admin should be able to edit case contacts from the case contacts page what type of user is this for volunteer supervisor admin all supervisor admin description supervisors should be able to edit case contacts from the case contacts page screenshots of current behavior if any | 0 |
65,454 | 12,578,270,161 | IssuesEvent | 2020-06-09 10:57:44 | Regalis11/Barotrauma | https://api.github.com/repos/Regalis11/Barotrauma | closed | Crashes when attempting to edit long names | Bug Code Crash | - [X] I have searched the issue tracker to check if the issue has already been reported.
**Description**
My current username on Steam is "is false when preceded by itself". It's 32 characters long - the maximum length of a Steam username. In-game it's truncated to 20 characters ("is false when preced"), but all text-boxes containing my username have the full thing as their initial value, and the game crashes when I try to highlight or edit them.
**Steps to Reproduce**
Change your name on Steam to something more than 20 characters. Then try to edit the username box in the server browser or the in-game Tab menu.
**Additional Information**
I'm no game-development expert, but I think the root cause of the crash is the mismatch between the max length of a Steam name (32 characters) and the max length of an in-game name (20 characters) - the game panics when it sees that the text-box's text is longer than it should be. Two likely fixes:
* Increase the max length of an in-game name to 32 characters.
* Add a check to the game's text boxes so that they can't be initialized with a value longer than the max length.
EDIT: Changed my name to "summary execution" (17 characters). The issue went away. | 1.0 | Crashes when attempting to edit long names - - [X] I have searched the issue tracker to check if the issue has already been reported.
**Description**
My current username on Steam is "is false when preceded by itself". It's 32 characters long - the maximum length of a Steam username. In-game it's truncated to 20 characters ("is false when preced"), but all text-boxes containing my username have the full thing as their initial value, and the game crashes when I try to highlight or edit them.
**Steps to Reproduce**
Change your name on Steam to something more than 20 characters. Then try to edit the username box in the server browser or the in-game Tab menu.
**Additional Information**
I'm no game-development expert, but I think the root cause of the crash is the mismatch between the max length of a Steam name (32 characters) and the max length of an in-game name (20 characters) - the game panics when it sees that the text-box's text is longer than it should be. Two likely fixes:
* Increase the max length of an in-game name to 32 characters.
* Add a check to the game's text boxes so that they can't be initialized with a value longer than the max length.
EDIT: Changed my name to "summary execution" (17 characters). The issue went away. | non_priority | crashes when attempting to edit long names i have searched the issue tracker to check if the issue has already been reported description my current username on steam is is false when preceded by itself it s characters long the maximum length of a steam username in game it s truncated to characters is false when preced but all text boxes containing my username have the full thing as their initial value and the game crashes when i try to highlight or edit them steps to reproduce change your name on steam to something more than characters then try to edit the username box in the server browser or the in game tab menu additional information i m no game development expert but i think the root cause of the crash is the mismatch between the max length of a steam name characters and the max length of an in game name characters the game panics when it sees that the text box s text is longer than it should be two likely fixes increase the max length of an in game name to characters add a check to the game s text boxes so that they can t be initialized with a value longer than the max length edit changed my name to summary execution characters the issue went away | 0 |
348,429 | 24,914,104,719 | IssuesEvent | 2022-10-30 07:21:41 | bohandsomn/Blog-RRST | https://api.github.com/repos/bohandsomn/Blog-RRST | opened | Release 0.0.6.1 | documentation enhancement Test | Rewrite each of the **packages** into **npm based** packages
The npm package should include the **files**:
- webpack,
- babel,
- gitignore,
- package json
- readme md
**Best practices** | 1.0 | Release 0.0.6.1 - Rewrite each of the **packages** into **npm based** packages
The npm package should include the **files**:
- webpack,
- babel,
- gitignore,
- package json
- readme md
**Best practices** | non_priority | release rewrite each of the packages into npm based packages the npm package should include the files webpack babel gitignore package json readme md best practices | 0 |
28,712 | 7,020,942,022 | IssuesEvent | 2017-12-22 00:31:06 | Microsoft/TypeScript | https://api.github.com/repos/Microsoft/TypeScript | closed | Add Error Message To EndInstallTypesEvent on Failure | Bug VS Code Tracked | Followup on #14398
Currently, the `EndInstallTypesEvent` only indicates success or failure. It does not contain any information about why the request failed.
In VSCode, when ATA fails, we would like to display a message to users informing them what went wrong so that they can possibly fix things. This would be benefit scenarios such as #14398 where ATA fails because npm is not installed | 1.0 | Add Error Message To EndInstallTypesEvent on Failure - Followup on #14398
Currently, the `EndInstallTypesEvent` only indicates success or failure. It does not contain any information about why the request failed.
In VSCode, when ATA fails, we would like to display a message to users informing them what went wrong so that they can possibly fix things. This would be benefit scenarios such as #14398 where ATA fails because npm is not installed | non_priority | add error message to endinstalltypesevent on failure followup on currently the endinstalltypesevent only indicates success or failure it does not contain any information about why the request failed in vscode when ata fails we would like to display a message to users informing them what went wrong so that they can possibly fix things this would be benefit scenarios such as where ata fails because npm is not installed | 0 |
143,771 | 22,154,280,775 | IssuesEvent | 2022-06-03 20:27:47 | department-of-veterans-affairs/va.gov-team | https://api.github.com/repos/department-of-veterans-affairs/va.gov-team | opened | [Design] No vertical lines on Veteran reviewing information pages | design ux HCE-Checkin | ## Description
There should be no vertical line decoration on all pages where Veterans are reviewing their information. E.g., contact information, emergency contact information and next of kin. Instead, there should be a horizontal divider.
Designers need to confirm whether this is correct or if this direction was specific to "edit" wireframes.
This is related to both pre-check-in and check-in.
## Tasks
- [ ] Designers need to confirm whether this is correct or if this direction was specific to "edit" wireframes.
- [ ] Create wireframes for pre-check-in and check-in, if it's determined that we need to use the horizontal line decorations
## Acceptance Criteria
- [ ] If we're changing to horizontal line decorations, wireframes available on Sketch Cloud
- [ ] If we're changing to horizontal line decorations, link to specific Sketch files
- [ ] If we're changing to horizontal line decorations, attach screenshots
- [ ] If we're changing to horizontal line decorations, talk to Lori about creating engineering ticket | 1.0 | [Design] No vertical lines on Veteran reviewing information pages - ## Description
There should be no vertical line decoration on all pages where Veterans are reviewing their information. E.g., contact information, emergency contact information and next of kin. Instead, there should be a horizontal divider.
Designers need to confirm whether this is correct or if this direction was specific to "edit" wireframes.
This is related to both pre-check-in and check-in.
## Tasks
- [ ] Designers need to confirm whether this is correct or if this direction was specific to "edit" wireframes.
- [ ] Create wireframes for pre-check-in and check-in, if it's determined that we need to use the horizontal line decorations
## Acceptance Criteria
- [ ] If we're changing to horizontal line decorations, wireframes available on Sketch Cloud
- [ ] If we're changing to horizontal line decorations, link to specific Sketch files
- [ ] If we're changing to horizontal line decorations, attach screenshots
- [ ] If we're changing to horizontal line decorations, talk to Lori about creating engineering ticket | non_priority | no vertical lines on veteran reviewing information pages description there should be no vertical line decoration on all pages where veterans are reviewing their information e g contact information emergency contact information and next of kin instead there should be a horizontal divider designers need to confirm whether this is correct or if this direction was specific to edit wireframes this is related to both pre check in and check in tasks designers need to confirm whether this is correct or if this direction was specific to edit wireframes create wireframes for pre check in and check in if it s determined that we need to use the horizontal line decorations acceptance criteria if we re changing to horizontal line decorations wireframes available on sketch cloud if we re changing to horizontal line decorations link to specific sketch files if we re changing to horizontal line decorations attach screenshots if we re changing to horizontal line decorations talk to lori about creating engineering ticket | 0 |
55,154 | 6,890,061,967 | IssuesEvent | 2017-11-22 12:42:39 | microsoftgraph/aspnetcore-connect-sample | https://api.github.com/repos/microsoftgraph/aspnetcore-connect-sample | closed | Auto "Sign In" User without Token | area: authentication by design question | In testing, every time I reload the App in Visual Studio I'm redirected back to the MSFT Sign In dialog. My account is already "Signed In" so all I'm doing is having to click my Account which redirects me back to the App.
I get that is due to not having a token in memory, however is there anyway to auto login so I don't have to "click through" ?
| 1.0 | Auto "Sign In" User without Token - In testing, every time I reload the App in Visual Studio I'm redirected back to the MSFT Sign In dialog. My account is already "Signed In" so all I'm doing is having to click my Account which redirects me back to the App.
I get that is due to not having a token in memory, however is there anyway to auto login so I don't have to "click through" ?
| non_priority | auto sign in user without token in testing every time i reload the app in visual studio i m redirected back to the msft sign in dialog my account is already signed in so all i m doing is having to click my account which redirects me back to the app i get that is due to not having a token in memory however is there anyway to auto login so i don t have to click through | 0 |
24,645 | 12,138,164,963 | IssuesEvent | 2020-04-23 16:48:11 | Azure/azure-sdk-for-net | https://api.github.com/repos/Azure/azure-sdk-for-net | closed | [Sql] DatabasesOperationsExtensions.DeleteAsync() should throw if not exists | Mgmt SQL Service Attention | DatabasesOperationsExtensions.DeleteAsync() should throw an exception when the database does not exist. Currently you can await it and if the database doesn't exist it will simply carry on. This is in contrast to say attempting to delete a Dns record set which will throw if it does not exist. | 1.0 | [Sql] DatabasesOperationsExtensions.DeleteAsync() should throw if not exists - DatabasesOperationsExtensions.DeleteAsync() should throw an exception when the database does not exist. Currently you can await it and if the database doesn't exist it will simply carry on. This is in contrast to say attempting to delete a Dns record set which will throw if it does not exist. | non_priority | databasesoperationsextensions deleteasync should throw if not exists databasesoperationsextensions deleteasync should throw an exception when the database does not exist currently you can await it and if the database doesn t exist it will simply carry on this is in contrast to say attempting to delete a dns record set which will throw if it does not exist | 0 |
6,299 | 8,665,769,502 | IssuesEvent | 2018-11-29 00:49:59 | GoogleWebComponents/model-viewer | https://api.github.com/repos/GoogleWebComponents/model-viewer | opened | Can we derive better default aria-label text? | arc: compatibility flag: question | Referencing discussion here: https://github.com/GoogleWebComponents/model-viewer/pull/242#discussion_r237312846
Right now we have a static default aria-label text on the canvas. It updates if the user configures alt text, but it's possible that we could derive better defaults based on other configurations such as the URL. This issue is for discussing potentially richer defaults. | True | Can we derive better default aria-label text? - Referencing discussion here: https://github.com/GoogleWebComponents/model-viewer/pull/242#discussion_r237312846
Right now we have a static default aria-label text on the canvas. It updates if the user configures alt text, but it's possible that we could derive better defaults based on other configurations such as the URL. This issue is for discussing potentially richer defaults. | non_priority | can we derive better default aria label text referencing discussion here right now we have a static default aria label text on the canvas it updates if the user configures alt text but it s possible that we could derive better defaults based on other configurations such as the url this issue is for discussing potentially richer defaults | 0 |
260,402 | 22,617,345,238 | IssuesEvent | 2022-06-30 00:22:58 | microsoft/vscode | https://api.github.com/repos/microsoft/vscode | reopened | Test Message are blocked by scroll bar | bug insiders-released testing | <!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No
<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
Version: 1.67.2 (user setup)
Commit: c3511e6c69bb39013c4a4b7b9566ec1ca73fc4d5
Date: 2022-05-17T18:15:52.058Z
Electron: 17.4.1
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: 9.8.177.13-electron.0
OS: Windows_NT x64 10.0.22000
Steps to Reproduce:
1. When the test messages in the peek are longer than the widget width, it will be blocked by the scroll bar (See the first line in the below video)
https://user-images.githubusercontent.com/6193897/172131221-1b0e697f-176a-44ec-8cd0-c47c9d93cec0.mp4
| 1.0 | Test Message are blocked by scroll bar - <!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No
<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
Version: 1.67.2 (user setup)
Commit: c3511e6c69bb39013c4a4b7b9566ec1ca73fc4d5
Date: 2022-05-17T18:15:52.058Z
Electron: 17.4.1
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: 9.8.177.13-electron.0
OS: Windows_NT x64 10.0.22000
Steps to Reproduce:
1. When the test messages in the peek are longer than the widget width, it will be blocked by the scroll bar (See the first line in the below video)
https://user-images.githubusercontent.com/6193897/172131221-1b0e697f-176a-44ec-8cd0-c47c9d93cec0.mp4
| non_priority | test message are blocked by scroll bar does this issue occur when all extensions are disabled yes no report issue dialog can assist with this version user setup commit date electron chromium node js electron os windows nt steps to reproduce when the test messages in the peek are longer than the widget width it will be blocked by the scroll bar see the first line in the below video | 0 |
1,822 | 3,966,768,041 | IssuesEvent | 2016-05-03 14:10:36 | IBM-Bluemix/logistics-wizard | https://api.github.com/repos/IBM-Bluemix/logistics-wizard | closed | Technical Collateral for ERP Service | content erp-service task | Plan out the content items that would be useful to developers/CIOs/etc for the ERP component. Ensure they all tie back to the value of the service and why Bluemix is being used.
Also, compile and send @jakepeyser examples you would like the digital agency to use as reference points. For example, this [Natural Language Classifier graphic video](https://www.youtube.com/watch?v=h1ZiUIvYdD8)
Story #16 | 1.0 | Technical Collateral for ERP Service - Plan out the content items that would be useful to developers/CIOs/etc for the ERP component. Ensure they all tie back to the value of the service and why Bluemix is being used.
Also, compile and send @jakepeyser examples you would like the digital agency to use as reference points. For example, this [Natural Language Classifier graphic video](https://www.youtube.com/watch?v=h1ZiUIvYdD8)
Story #16 | non_priority | technical collateral for erp service plan out the content items that would be useful to developers cios etc for the erp component ensure they all tie back to the value of the service and why bluemix is being used also compile and send jakepeyser examples you would like the digital agency to use as reference points for example this story | 0 |
23,565 | 4,956,686,687 | IssuesEvent | 2016-12-02 00:30:26 | 3DUnityScanner/SeniorDesignProject | https://api.github.com/repos/3DUnityScanner/SeniorDesignProject | opened | Camera Library Installation | documentation | How to install the library that is needed to interface with the camera | 1.0 | Camera Library Installation - How to install the library that is needed to interface with the camera | non_priority | camera library installation how to install the library that is needed to interface with the camera | 0 |
43,405 | 23,227,127,929 | IssuesEvent | 2022-08-03 02:11:13 | ECP-WarpX/impactx | https://api.github.com/repos/ECP-WarpX/impactx | opened | Activate Dynamic Load Balancing | component: core Performance optimization | Start like this:
- expose a user parameter with `N` boxes per device; currently, `N` is hard-coded to 1
- add a cost function
- add load balance interval control | True | Activate Dynamic Load Balancing - Start like this:
- expose a user parameter with `N` boxes per device; currently, `N` is hard-coded to 1
- add a cost function
- add load balance interval control | non_priority | activate dynamic load balancing start like this expose a user parameter with n boxes per device currently n is hard coded to add a cost function add load balance interval control | 0 |
158,326 | 20,024,184,215 | IssuesEvent | 2022-02-01 19:23:29 | snowdensb/job-dsl-plugin | https://api.github.com/repos/snowdensb/job-dsl-plugin | opened | CVE-2021-41184 (Medium) detected in jquery-ui-1.11.3.js, jquery-ui-1.11.3.min.js | security vulnerability | ## CVE-2021-41184 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>jquery-ui-1.11.3.js</b>, <b>jquery-ui-1.11.3.min.js</b></p></summary>
<p>
<details><summary><b>jquery-ui-1.11.3.js</b></p></summary>
<p>A curated set of user interface interactions, effects, widgets, and themes built on top of the jQuery JavaScript Library.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.11.3/jquery-ui.js">https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.11.3/jquery-ui.js</a></p>
<p>Path to vulnerable library: /job-dsl-api-viewer/build/webjars/jquery-ui/1.11.3/jquery-ui.js</p>
<p>
Dependency Hierarchy:
- :x: **jquery-ui-1.11.3.js** (Vulnerable Library)
</details>
<details><summary><b>jquery-ui-1.11.3.min.js</b></p></summary>
<p>A curated set of user interface interactions, effects, widgets, and themes built on top of the jQuery JavaScript Library.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.11.3/jquery-ui.min.js">https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.11.3/jquery-ui.min.js</a></p>
<p>Path to vulnerable library: /job-dsl-api-viewer/build/webjars/jquery-ui/1.11.3/jquery-ui.min.js</p>
<p>
Dependency Hierarchy:
- :x: **jquery-ui-1.11.3.min.js** (Vulnerable Library)
</details>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of the `of` option of the `.position()` util from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. Any string value passed to the `of` option is now treated as a CSS selector. A workaround is to not accept the value of the `of` option from untrusted sources.
<p>Publish Date: 2021-10-26
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-41184>CVE-2021-41184</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41184">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41184</a></p>
<p>Release Date: 2021-10-26</p>
<p>Fix Resolution: jquery-ui - 1.13.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"JavaScript","packageName":"jqueryui","packageVersion":"1.11.3","packageFilePaths":[null],"isTransitiveDependency":false,"dependencyTree":"jqueryui:1.11.3","isMinimumFixVersionAvailable":true,"minimumFixVersion":"jquery-ui - 1.13.0","isBinary":false},{"packageType":"JavaScript","packageName":"jqueryui","packageVersion":"1.11.3","packageFilePaths":[null],"isTransitiveDependency":false,"dependencyTree":"jqueryui:1.11.3","isMinimumFixVersionAvailable":true,"minimumFixVersion":"jquery-ui - 1.13.0","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-41184","vulnerabilityDetails":"jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of the `of` option of the `.position()` util from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. Any string value passed to the `of` option is now treated as a CSS selector. A workaround is to not accept the value of the `of` option from untrusted sources.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-41184","cvss3Severity":"medium","cvss3Score":"6.1","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Changed","C":"Low","UI":"Required","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | True | CVE-2021-41184 (Medium) detected in jquery-ui-1.11.3.js, jquery-ui-1.11.3.min.js - ## CVE-2021-41184 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>jquery-ui-1.11.3.js</b>, <b>jquery-ui-1.11.3.min.js</b></p></summary>
<p>
<details><summary><b>jquery-ui-1.11.3.js</b></p></summary>
<p>A curated set of user interface interactions, effects, widgets, and themes built on top of the jQuery JavaScript Library.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.11.3/jquery-ui.js">https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.11.3/jquery-ui.js</a></p>
<p>Path to vulnerable library: /job-dsl-api-viewer/build/webjars/jquery-ui/1.11.3/jquery-ui.js</p>
<p>
Dependency Hierarchy:
- :x: **jquery-ui-1.11.3.js** (Vulnerable Library)
</details>
<details><summary><b>jquery-ui-1.11.3.min.js</b></p></summary>
<p>A curated set of user interface interactions, effects, widgets, and themes built on top of the jQuery JavaScript Library.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.11.3/jquery-ui.min.js">https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.11.3/jquery-ui.min.js</a></p>
<p>Path to vulnerable library: /job-dsl-api-viewer/build/webjars/jquery-ui/1.11.3/jquery-ui.min.js</p>
<p>
Dependency Hierarchy:
- :x: **jquery-ui-1.11.3.min.js** (Vulnerable Library)
</details>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of the `of` option of the `.position()` util from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. Any string value passed to the `of` option is now treated as a CSS selector. A workaround is to not accept the value of the `of` option from untrusted sources.
<p>Publish Date: 2021-10-26
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-41184>CVE-2021-41184</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41184">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41184</a></p>
<p>Release Date: 2021-10-26</p>
<p>Fix Resolution: jquery-ui - 1.13.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"JavaScript","packageName":"jqueryui","packageVersion":"1.11.3","packageFilePaths":[null],"isTransitiveDependency":false,"dependencyTree":"jqueryui:1.11.3","isMinimumFixVersionAvailable":true,"minimumFixVersion":"jquery-ui - 1.13.0","isBinary":false},{"packageType":"JavaScript","packageName":"jqueryui","packageVersion":"1.11.3","packageFilePaths":[null],"isTransitiveDependency":false,"dependencyTree":"jqueryui:1.11.3","isMinimumFixVersionAvailable":true,"minimumFixVersion":"jquery-ui - 1.13.0","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-41184","vulnerabilityDetails":"jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of the `of` option of the `.position()` util from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. Any string value passed to the `of` option is now treated as a CSS selector. A workaround is to not accept the value of the `of` option from untrusted sources.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-41184","cvss3Severity":"medium","cvss3Score":"6.1","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Changed","C":"Low","UI":"Required","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | non_priority | cve medium detected in jquery ui js jquery ui min js cve medium severity vulnerability vulnerable libraries jquery ui js jquery ui min js jquery ui js a curated set of user interface interactions effects widgets and themes built on top of the jquery javascript library library home page a href path to vulnerable library job dsl api viewer build webjars jquery ui jquery ui js dependency hierarchy x jquery ui js vulnerable library jquery ui min js a curated set of user interface interactions effects widgets and themes built on top of the jquery javascript library library home page a href path to vulnerable library job dsl api viewer build webjars jquery ui jquery ui min js dependency hierarchy x jquery ui min js vulnerable library found in base branch master vulnerability details jquery ui is the official jquery user interface library prior to version accepting the value of the of option of the position util from untrusted sources may execute untrusted code the issue is fixed in jquery ui any string value passed to the of option is now treated as a css selector a workaround is to not accept the value of the of option from untrusted sources publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution jquery ui isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree jqueryui isminimumfixversionavailable true minimumfixversion jquery ui isbinary false packagetype javascript packagename jqueryui packageversion packagefilepaths istransitivedependency false dependencytree jqueryui isminimumfixversionavailable true minimumfixversion jquery ui isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails jquery ui is the official jquery user interface library prior to version accepting the value of the of option of the position util from untrusted sources may execute untrusted code the issue is fixed in jquery ui any string value passed to the of option is now treated as a css selector a workaround is to not accept the value of the of option from untrusted sources vulnerabilityurl | 0 |
32,320 | 4,762,299,971 | IssuesEvent | 2016-10-25 11:02:12 | ansible/ansible | https://api.github.com/repos/ansible/ansible | opened | validate-modules: Error on * imports for new modules | test | ##### ISSUE TYPE
- Feature Idea
##### COMPONENT NAME
validate-modules
##### ANSIBLE VERSION
```
ansible 2.3.0 (devel 5502da3cf8) last updated 2016/10/25 11:22:53 (GMT +100)
lib/ansible/modules/core: (devel 4c020102a9) last updated 2016/10/25 11:22:57 (GMT +100)
lib/ansible/modules/extras: (devel 8f77a0e72a) last updated 2016/10/25 11:22:59 (GMT +100)
config file =
```
##### CONFIGURATION
##### OS / ENVIRONMENT
##### SUMMARY
New modules should import what they need, no longer importing `*` from module_utils.
We may want to make a judgement call about fixing existing modules
Also this need adding to the list of checks in `test/sanity/validate-modules/README.rst`
##### STEPS TO REPRODUCE
##### EXPECTED RESULTS
##### ACTUAL RESULTS
| 1.0 | validate-modules: Error on * imports for new modules - ##### ISSUE TYPE
- Feature Idea
##### COMPONENT NAME
validate-modules
##### ANSIBLE VERSION
```
ansible 2.3.0 (devel 5502da3cf8) last updated 2016/10/25 11:22:53 (GMT +100)
lib/ansible/modules/core: (devel 4c020102a9) last updated 2016/10/25 11:22:57 (GMT +100)
lib/ansible/modules/extras: (devel 8f77a0e72a) last updated 2016/10/25 11:22:59 (GMT +100)
config file =
```
##### CONFIGURATION
##### OS / ENVIRONMENT
##### SUMMARY
New modules should import what they need, no longer importing `*` from module_utils.
We may want to make a judgement call about fixing existing modules
Also this need adding to the list of checks in `test/sanity/validate-modules/README.rst`
##### STEPS TO REPRODUCE
##### EXPECTED RESULTS
##### ACTUAL RESULTS
| non_priority | validate modules error on imports for new modules issue type feature idea component name validate modules ansible version ansible devel last updated gmt lib ansible modules core devel last updated gmt lib ansible modules extras devel last updated gmt config file configuration os environment summary new modules should import what they need no longer importing from module utils we may want to make a judgement call about fixing existing modules also this need adding to the list of checks in test sanity validate modules readme rst steps to reproduce expected results actual results | 0 |
92,747 | 18,945,899,753 | IssuesEvent | 2021-11-18 10:07:54 | jOOQ/jOOQ | https://api.github.com/repos/jOOQ/jOOQ | closed | PostgreSQL CockroachDB CodeGen Error - unknown function: information_schema._pg_char_max_length() | T: Defect C: Code Generation P: Medium T: Support request R: Feedback Pending E: Professional Edition E: Enterprise Edition C: DB: CockroachDB | ### Expected behavior
Code generation should succeed and create model classes.
### Actual behavior
Error thrown during generation.
`Caused by: org.jooq.exception.DataAccessException: SQL [with recursive domains(domain_id, base_id, typbasetype, src) as (select d.oid, d.oid, d.typbasetype, case when c.oid is not null then array[pg_get_constraintdef(c.oid)] end from pg_catalog.pg_type as d join pg_catalog.pg_namespace as n on n.oid = d.typnamespace left outer join pg_catalog.pg_constraint as c on d.oid = c.contypid where (d.typtype = ? and n.nspname in (?, ?, ?, ?, ?)) union all select domains.domain_id, d.oid, d.typbasetype, case when c.conbin is null then domains.src else array_append(domains.src, pg_get_constraintdef(c.oid)) end from domains join pg_catalog.pg_type as d on domains.typbasetype = d.oid left outer join pg_catalog.pg_constraint as c on d.oid = c.contypid) select n.nspname, d.typname, d.typnotnull, d.typdefault, b.typname, information_schema._pg_char_max_length(d.typbasetype, d.typtypmod) as character_maximum_length, information_schema._pg_numeric_precision(d.typbasetype, d.typtypmod) as numeric_precision, information_schema._pg_numeric_scale(d.typbasetype, d.typtypmod) as numeric_scale, domains.src from pg_catalog.pg_type as d join domains on (domains.typbasetype = ? and domains.domain_id = d.oid) join pg_catalog.pg_type as b on domains.base_id = b.oid join pg_catalog.pg_namespace as n on n.oid = d.typnamespace where (d.typtype = ? and n.nspname in (?, ?, ?, ?, ?)) order by n.nspname, d.typname]; ERROR: unknown function: information_schema._pg_char_max_length()`
### Steps to reproduce the problem
- If the problem relates to code generation, please post your code generation configuration
```
<configuration xmlns="http://www.jooq.org/xsd/jooq-codegen-3.15.0.xsd">
<jdbc>
<driver>org.postgresql.Driver</driver>
<url>jdbc:postgresql://localhost:26257/payment?sslmode=disable</url>
<user>sam</user>
<password>pw</password>
</jdbc>
<generator>
<database>
<name>org.jooq.meta.postgres.PostgresDatabase</name>
<includes>.*</includes>
<inputSchema>public</inputSchema>
</database>
<generate/>
<target>
<packageName>com.example.cockroachpoc.model</packageName>
<directory>/path/to/your/dir</directory>
</target>
</generator>
</configuration>
```
- If the problem relates to upgrades, please check if your RDBMS version is still supported by jOOQ: https://www.jooq.org/download/support-matrix
- A complete set of DDL statements can help re-create the setup you're having
- An MCVE can be helpful to provide a complete reproduction case: https://github.com/jOOQ/jOOQ-mcve
### Versions
- jOOQ: 3.14.15
- Java: 11.0.5
- Database (include vendor): CockroachDB
- OS: WIndows
- JDBC Driver (include name if inofficial driver): Postgres
| 1.0 | PostgreSQL CockroachDB CodeGen Error - unknown function: information_schema._pg_char_max_length() - ### Expected behavior
Code generation should succeed and create model classes.
### Actual behavior
Error thrown during generation.
`Caused by: org.jooq.exception.DataAccessException: SQL [with recursive domains(domain_id, base_id, typbasetype, src) as (select d.oid, d.oid, d.typbasetype, case when c.oid is not null then array[pg_get_constraintdef(c.oid)] end from pg_catalog.pg_type as d join pg_catalog.pg_namespace as n on n.oid = d.typnamespace left outer join pg_catalog.pg_constraint as c on d.oid = c.contypid where (d.typtype = ? and n.nspname in (?, ?, ?, ?, ?)) union all select domains.domain_id, d.oid, d.typbasetype, case when c.conbin is null then domains.src else array_append(domains.src, pg_get_constraintdef(c.oid)) end from domains join pg_catalog.pg_type as d on domains.typbasetype = d.oid left outer join pg_catalog.pg_constraint as c on d.oid = c.contypid) select n.nspname, d.typname, d.typnotnull, d.typdefault, b.typname, information_schema._pg_char_max_length(d.typbasetype, d.typtypmod) as character_maximum_length, information_schema._pg_numeric_precision(d.typbasetype, d.typtypmod) as numeric_precision, information_schema._pg_numeric_scale(d.typbasetype, d.typtypmod) as numeric_scale, domains.src from pg_catalog.pg_type as d join domains on (domains.typbasetype = ? and domains.domain_id = d.oid) join pg_catalog.pg_type as b on domains.base_id = b.oid join pg_catalog.pg_namespace as n on n.oid = d.typnamespace where (d.typtype = ? and n.nspname in (?, ?, ?, ?, ?)) order by n.nspname, d.typname]; ERROR: unknown function: information_schema._pg_char_max_length()`
### Steps to reproduce the problem
- If the problem relates to code generation, please post your code generation configuration
```
<configuration xmlns="http://www.jooq.org/xsd/jooq-codegen-3.15.0.xsd">
<jdbc>
<driver>org.postgresql.Driver</driver>
<url>jdbc:postgresql://localhost:26257/payment?sslmode=disable</url>
<user>sam</user>
<password>pw</password>
</jdbc>
<generator>
<database>
<name>org.jooq.meta.postgres.PostgresDatabase</name>
<includes>.*</includes>
<inputSchema>public</inputSchema>
</database>
<generate/>
<target>
<packageName>com.example.cockroachpoc.model</packageName>
<directory>/path/to/your/dir</directory>
</target>
</generator>
</configuration>
```
- If the problem relates to upgrades, please check if your RDBMS version is still supported by jOOQ: https://www.jooq.org/download/support-matrix
- A complete set of DDL statements can help re-create the setup you're having
- An MCVE can be helpful to provide a complete reproduction case: https://github.com/jOOQ/jOOQ-mcve
### Versions
- jOOQ: 3.14.15
- Java: 11.0.5
- Database (include vendor): CockroachDB
- OS: WIndows
- JDBC Driver (include name if inofficial driver): Postgres
| non_priority | postgresql cockroachdb codegen error unknown function information schema pg char max length expected behavior code generation should succeed and create model classes actual behavior error thrown during generation caused by org jooq exception dataaccessexception sql end from pg catalog pg type as d join pg catalog pg namespace as n on n oid d typnamespace left outer join pg catalog pg constraint as c on d oid c contypid where d typtype and n nspname in union all select domains domain id d oid d typbasetype case when c conbin is null then domains src else array append domains src pg get constraintdef c oid end from domains join pg catalog pg type as d on domains typbasetype d oid left outer join pg catalog pg constraint as c on d oid c contypid select n nspname d typname d typnotnull d typdefault b typname information schema pg char max length d typbasetype d typtypmod as character maximum length information schema pg numeric precision d typbasetype d typtypmod as numeric precision information schema pg numeric scale d typbasetype d typtypmod as numeric scale domains src from pg catalog pg type as d join domains on domains typbasetype and domains domain id d oid join pg catalog pg type as b on domains base id b oid join pg catalog pg namespace as n on n oid d typnamespace where d typtype and n nspname in order by n nspname d typname error unknown function information schema pg char max length steps to reproduce the problem if the problem relates to code generation please post your code generation configuration configuration xmlns org postgresql driver jdbc postgresql localhost payment sslmode disable sam pw org jooq meta postgres postgresdatabase public com example cockroachpoc model path to your dir if the problem relates to upgrades please check if your rdbms version is still supported by jooq a complete set of ddl statements can help re create the setup you re having an mcve can be helpful to provide a complete reproduction case versions jooq java database include vendor cockroachdb os windows jdbc driver include name if inofficial driver postgres | 0 |
25,345 | 11,169,742,880 | IssuesEvent | 2019-12-28 08:13:00 | n-psk/libpack-scripts | https://api.github.com/repos/n-psk/libpack-scripts | opened | WS-2019-0307 (Medium) detected in mem-1.1.0.tgz | security vulnerability | ## WS-2019-0307 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>mem-1.1.0.tgz</b></p></summary>
<p>Memoize functions - An optimization used to speed up consecutive function calls by caching the result of calls with identical input</p>
<p>Library home page: <a href="https://registry.npmjs.org/mem/-/mem-1.1.0.tgz">https://registry.npmjs.org/mem/-/mem-1.1.0.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/libpack-scripts/packages/package-name/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/libpack-scripts/packages/package-name/node_modules/mem/package.json,/tmp/ws-scm/libpack-scripts/packages/package-name/node_modules/mem/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-1.1.5.tgz (Root Library)
- webpack-3.8.1.tgz
- yargs-8.0.2.tgz
- os-locale-2.1.0.tgz
- :x: **mem-1.1.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/n-psk/libpack-scripts/commit/274cfb7f3db8d74a0a35e44eeac2d312ce785ef0">274cfb7f3db8d74a0a35e44eeac2d312ce785ef0</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Denial of Service (DoS) vulnerability found in mem before 4.0.0. There is a failure in removal of old values from the cache. As a result, attacker may exhaust the system's memory.
<p>Publish Date: 2019-12-01
<p>URL: <a href=https://github.com/sindresorhus/mem/commit/da4e4398cb27b602de3bd55f746efa9b4a31702b>WS-2019-0307</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/1084">https://www.npmjs.com/advisories/1084</a></p>
<p>Release Date: 2019-12-01</p>
<p>Fix Resolution: mem - 4.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | WS-2019-0307 (Medium) detected in mem-1.1.0.tgz - ## WS-2019-0307 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>mem-1.1.0.tgz</b></p></summary>
<p>Memoize functions - An optimization used to speed up consecutive function calls by caching the result of calls with identical input</p>
<p>Library home page: <a href="https://registry.npmjs.org/mem/-/mem-1.1.0.tgz">https://registry.npmjs.org/mem/-/mem-1.1.0.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/libpack-scripts/packages/package-name/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/libpack-scripts/packages/package-name/node_modules/mem/package.json,/tmp/ws-scm/libpack-scripts/packages/package-name/node_modules/mem/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-1.1.5.tgz (Root Library)
- webpack-3.8.1.tgz
- yargs-8.0.2.tgz
- os-locale-2.1.0.tgz
- :x: **mem-1.1.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/n-psk/libpack-scripts/commit/274cfb7f3db8d74a0a35e44eeac2d312ce785ef0">274cfb7f3db8d74a0a35e44eeac2d312ce785ef0</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Denial of Service (DoS) vulnerability found in mem before 4.0.0. There is a failure in removal of old values from the cache. As a result, attacker may exhaust the system's memory.
<p>Publish Date: 2019-12-01
<p>URL: <a href=https://github.com/sindresorhus/mem/commit/da4e4398cb27b602de3bd55f746efa9b4a31702b>WS-2019-0307</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/1084">https://www.npmjs.com/advisories/1084</a></p>
<p>Release Date: 2019-12-01</p>
<p>Fix Resolution: mem - 4.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | ws medium detected in mem tgz ws medium severity vulnerability vulnerable library mem tgz memoize functions an optimization used to speed up consecutive function calls by caching the result of calls with identical input library home page a href path to dependency file tmp ws scm libpack scripts packages package name package json path to vulnerable library tmp ws scm libpack scripts packages package name node modules mem package json tmp ws scm libpack scripts packages package name node modules mem package json dependency hierarchy react scripts tgz root library webpack tgz yargs tgz os locale tgz x mem tgz vulnerable library found in head commit a href vulnerability details denial of service dos vulnerability found in mem before there is a failure in removal of old values from the cache as a result attacker may exhaust the system s memory publish date url a href cvss score details base score metrics not available suggested fix type upgrade version origin a href release date fix resolution mem step up your open source security game with whitesource | 0 |
76,372 | 26,395,712,239 | IssuesEvent | 2023-01-12 19:12:46 | jccastillo0007/eFacturaT | https://api.github.com/repos/jccastillo0007/eFacturaT | closed | Lo que faltó para hacer el Carta Porte mas gaver de México - Validación en la pantalla de captura | resolved defect | Estoy identificando que se me pasó solicitar la validación de datos obligatorios en la pantalla de captura (addenda).
Validar lo siguiente:
Origen(es): seleccionar origen y fecha de salida.
Destino(s): seleccionar destino, distancia recorrida y fecha probable de entrega
Mercancía(s): seleccionar mercancía, cantidad y peso. (el peso se pone en automático, si se capturó en el catálogo)
Transporte: transporte (haber seleccionado un transporte)
Operador: operador (al menos 1).
No permitir guardar, si no supera la validación.
| 1.0 | Lo que faltó para hacer el Carta Porte mas gaver de México - Validación en la pantalla de captura - Estoy identificando que se me pasó solicitar la validación de datos obligatorios en la pantalla de captura (addenda).
Validar lo siguiente:
Origen(es): seleccionar origen y fecha de salida.
Destino(s): seleccionar destino, distancia recorrida y fecha probable de entrega
Mercancía(s): seleccionar mercancía, cantidad y peso. (el peso se pone en automático, si se capturó en el catálogo)
Transporte: transporte (haber seleccionado un transporte)
Operador: operador (al menos 1).
No permitir guardar, si no supera la validación.
| non_priority | lo que faltó para hacer el carta porte mas gaver de méxico validación en la pantalla de captura estoy identificando que se me pasó solicitar la validación de datos obligatorios en la pantalla de captura addenda validar lo siguiente origen es seleccionar origen y fecha de salida destino s seleccionar destino distancia recorrida y fecha probable de entrega mercancía s seleccionar mercancía cantidad y peso el peso se pone en automático si se capturó en el catálogo transporte transporte haber seleccionado un transporte operador operador al menos no permitir guardar si no supera la validación | 0 |
390,528 | 26,865,271,923 | IssuesEvent | 2023-02-03 22:45:25 | Max1mus7/cider-app | https://api.github.com/repos/Max1mus7/cider-app | opened | Add issue template | documentation enhancement good first issue | Create an effective issue template (or set of issue templates) to use to create issues within this repo
| 1.0 | Add issue template - Create an effective issue template (or set of issue templates) to use to create issues within this repo
| non_priority | add issue template create an effective issue template or set of issue templates to use to create issues within this repo | 0 |
184,792 | 14,990,310,908 | IssuesEvent | 2021-01-29 06:06:12 | Ethereal-Developers-Inc/OpenScan | https://api.github.com/repos/Ethereal-Developers-Inc/OpenScan | closed | Custom cropper screen | documentation question | How can I remove 'Original' 'Magic Color' and other buttons from cropping screen?
I've downloaded the Flutter scanner plugin and tried to modify -> scanner_core -> scanlibrary -> src -> main -> res -> layout -> result_layout.xml
but the buttons are still there. | 1.0 | Custom cropper screen - How can I remove 'Original' 'Magic Color' and other buttons from cropping screen?
I've downloaded the Flutter scanner plugin and tried to modify -> scanner_core -> scanlibrary -> src -> main -> res -> layout -> result_layout.xml
but the buttons are still there. | non_priority | custom cropper screen how can i remove original magic color and other buttons from cropping screen i ve downloaded the flutter scanner plugin and tried to modify scanner core scanlibrary src main res layout result layout xml but the buttons are still there | 0 |
78,701 | 10,082,010,383 | IssuesEvent | 2019-07-25 10:07:05 | line/armeria | https://api.github.com/repos/line/armeria | opened | Add an example for enabling binary content preview for non-200 Thrift calls. | documentation | We recently received a question how a user can check what Thrift calls were made in a timed-out request. When a request gets timed out with an automatic `503 Service Unavailable` response, its `RequestLog` will enter `COMPLETE` availability, preventing `THttpService` from setting `RequestLog.requestContent()`.
In this case, a user may want to enable content previews for non-200 Thrift calls, so that he or she can at least get the needed information by deserializing the hex dump content preview.
Because it is a fairly common scenario, we should provide an example in our documentation: https://line.github.io/armeria/advanced-structured-logging.html#enabling-content-previews
| 1.0 | Add an example for enabling binary content preview for non-200 Thrift calls. - We recently received a question how a user can check what Thrift calls were made in a timed-out request. When a request gets timed out with an automatic `503 Service Unavailable` response, its `RequestLog` will enter `COMPLETE` availability, preventing `THttpService` from setting `RequestLog.requestContent()`.
In this case, a user may want to enable content previews for non-200 Thrift calls, so that he or she can at least get the needed information by deserializing the hex dump content preview.
Because it is a fairly common scenario, we should provide an example in our documentation: https://line.github.io/armeria/advanced-structured-logging.html#enabling-content-previews
| non_priority | add an example for enabling binary content preview for non thrift calls we recently received a question how a user can check what thrift calls were made in a timed out request when a request gets timed out with an automatic service unavailable response its requestlog will enter complete availability preventing thttpservice from setting requestlog requestcontent in this case a user may want to enable content previews for non thrift calls so that he or she can at least get the needed information by deserializing the hex dump content preview because it is a fairly common scenario we should provide an example in our documentation | 0 |
239,539 | 26,231,849,020 | IssuesEvent | 2023-01-05 01:23:48 | vipinsun/blockchain-carbon-accounting | https://api.github.com/repos/vipinsun/blockchain-carbon-accounting | opened | CVE-2022-24999 (High) detected in qs-6.10.1.tgz | security vulnerability | ## CVE-2022-24999 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>qs-6.10.1.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-6.10.1.tgz">https://registry.npmjs.org/qs/-/qs-6.10.1.tgz</a></p>
<p>Path to dependency file: /utility-emissions-channel/typescript_app/package.json</p>
<p>Path to vulnerable library: /utility-emissions-channel/typescript_app/node_modules/@hyperledger/cactus-plugin-ledger-connector-fabric/node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- cactus-plugin-ledger-connector-fabric-0.9.0.tgz (Root Library)
- fabric-network-2.3.0-snapshot.49.tgz
- nano-9.0.5.tgz
- :x: **qs-6.10.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/vipinsun/blockchain-carbon-accounting/commit/d388e16464e00b9ce84df0d247029f534a429b90">d388e16464e00b9ce84df0d247029f534a429b90</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used. In many typical Express use cases, an unauthenticated remote attacker can place the attack payload in the query string of the URL that is used to visit the application, such as a[__proto__]=b&a[__proto__]&a[length]=100000000. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4 (and therefore Express 4.17.3, which has "deps: qs@6.9.7" in its release description, is not vulnerable).
<p>Publish Date: 2022-11-26
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-24999>CVE-2022-24999</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.cve.org/CVERecord?id=CVE-2022-24999">https://www.cve.org/CVERecord?id=CVE-2022-24999</a></p>
<p>Release Date: 2022-11-26</p>
<p>Fix Resolution: qs - 6.2.4,6.3.3,6.4.1,6.5.3,6.6.1,6.7.3,6.8.3,6.9.7,6.10.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-24999 (High) detected in qs-6.10.1.tgz - ## CVE-2022-24999 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>qs-6.10.1.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-6.10.1.tgz">https://registry.npmjs.org/qs/-/qs-6.10.1.tgz</a></p>
<p>Path to dependency file: /utility-emissions-channel/typescript_app/package.json</p>
<p>Path to vulnerable library: /utility-emissions-channel/typescript_app/node_modules/@hyperledger/cactus-plugin-ledger-connector-fabric/node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- cactus-plugin-ledger-connector-fabric-0.9.0.tgz (Root Library)
- fabric-network-2.3.0-snapshot.49.tgz
- nano-9.0.5.tgz
- :x: **qs-6.10.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/vipinsun/blockchain-carbon-accounting/commit/d388e16464e00b9ce84df0d247029f534a429b90">d388e16464e00b9ce84df0d247029f534a429b90</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used. In many typical Express use cases, an unauthenticated remote attacker can place the attack payload in the query string of the URL that is used to visit the application, such as a[__proto__]=b&a[__proto__]&a[length]=100000000. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4 (and therefore Express 4.17.3, which has "deps: qs@6.9.7" in its release description, is not vulnerable).
<p>Publish Date: 2022-11-26
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-24999>CVE-2022-24999</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.cve.org/CVERecord?id=CVE-2022-24999">https://www.cve.org/CVERecord?id=CVE-2022-24999</a></p>
<p>Release Date: 2022-11-26</p>
<p>Fix Resolution: qs - 6.2.4,6.3.3,6.4.1,6.5.3,6.6.1,6.7.3,6.8.3,6.9.7,6.10.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in qs tgz cve high severity vulnerability vulnerable library qs tgz a querystring parser that supports nesting and arrays with a depth limit library home page a href path to dependency file utility emissions channel typescript app package json path to vulnerable library utility emissions channel typescript app node modules hyperledger cactus plugin ledger connector fabric node modules qs package json dependency hierarchy cactus plugin ledger connector fabric tgz root library fabric network snapshot tgz nano tgz x qs tgz vulnerable library found in head commit a href found in base branch main vulnerability details qs before as used in express before and other products allows attackers to cause a node process hang for an express application because an proto key can be used in many typical express use cases an unauthenticated remote attacker can place the attack payload in the query string of the url that is used to visit the application such as a b a a the fix was backported to qs and and therefore express which has deps qs in its release description is not vulnerable publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution qs step up your open source security game with mend | 0 |
333,540 | 29,736,661,670 | IssuesEvent | 2023-06-14 01:54:07 | microsoft/AzureStorageExplorer | https://api.github.com/repos/microsoft/AzureStorageExplorer | closed | Miss the action 'Clone...' for one ADLS Gen2/regular blob container | :heavy_check_mark: merged 🧪 testing :beetle: regression | **Storage Explorer Version**: 1.30.0
**Build Number**: 20230613.2
**Branch**: main
**Platform/OS**: Windows 10/Linux Ubuntu 20.04/MacOS Ventura 13.4 (Apple M1 Pro)
**Architecture**: x64
**How Found**: From running test cases
**Regression From**: Previous release (1.30.0)
## Steps to Reproduce ##
1. Expand one storage account -> Blob Containers.
2. Right click one blob container -> Observe the context menu.
3. Check whether there is an action 'Clone...'.
## Expected Experience ##
There is an action 'Clone...'.
## Actual Experience ##
There is no action 'Clone...'.
| 1.0 | Miss the action 'Clone...' for one ADLS Gen2/regular blob container - **Storage Explorer Version**: 1.30.0
**Build Number**: 20230613.2
**Branch**: main
**Platform/OS**: Windows 10/Linux Ubuntu 20.04/MacOS Ventura 13.4 (Apple M1 Pro)
**Architecture**: x64
**How Found**: From running test cases
**Regression From**: Previous release (1.30.0)
## Steps to Reproduce ##
1. Expand one storage account -> Blob Containers.
2. Right click one blob container -> Observe the context menu.
3. Check whether there is an action 'Clone...'.
## Expected Experience ##
There is an action 'Clone...'.
## Actual Experience ##
There is no action 'Clone...'.
| non_priority | miss the action clone for one adls regular blob container storage explorer version build number branch main platform os windows linux ubuntu macos ventura apple pro architecture how found from running test cases regression from previous release steps to reproduce expand one storage account blob containers right click one blob container observe the context menu check whether there is an action clone expected experience there is an action clone actual experience there is no action clone | 0 |
149,180 | 11,884,971,660 | IssuesEvent | 2020-03-27 18:39:58 | roc-project/roc | https://api.github.com/repos/roc-project/roc | closed | Parser memory leak | report tests | Hey! It seems that in some cases, our Ragel parsers create a memory leak.
To reproduce, if we add for example " test" to the string being parsed ("rtsp://host:123/path?query test"):
https://github.com/roc-project/roc/blob/bc364daf9f77c83706354c19c139b111414a1a0d/src/tests/roc_address/test_endpoint_uri.cpp#L89-L102
The following error appears:
```
src/tests/roc_address/test_endpoint_uri.cpp:99: error: Failure in TEST(endpoint_uri, fields)
expected <query>
but was <query test>
difference starts at position 5 at: < query test >
^
src/modules/roc_core/heap_allocator.cpp:26: error: roc_panic()
ERROR: roc_core: heap allocator: detected leak(s): 2 objects was not freed
Backtrace:
#1: 0x44b57a roc::core::print_backtrace()+0x5a
#2: 0x44ac8a roc::core::crash(char const*)+0x3a
#3: 0x44ac4e roc::core::panic(char const*, char const*, int, char const*, ...)+0x25e
#4: 0x449855 roc::core::HeapAllocator::~HeapAllocator()+0x85
#5: 0x433951 roc::address::TEST_GROUP_CppUTestGroupendpoint_uri::~TEST_GROUP_CppUTestGroupendpoint_uri()+0x31
#6: 0x433515 roc::address::TEST_endpoint_uri_fields_Test::~TEST_endpoint_uri_fields_Test()+0x15
#7: 0x433539 roc::address::TEST_endpoint_uri_fields_Test::~TEST_endpoint_uri_fields_Test()+0x19
#8: 0x45b32e UtestShell::runOneTestInCurrentProcess(TestPlugin*, TestResult&)+0x7e
#9: 0x45b972 PlatformSpecificSetJmpImplementation+0x42
#10: 0x458ea7 UtestShell::runOneTest(TestPlugin*, TestResult&)+0x57
#11: 0x458457 TestRegistry::runAllTests(TestResult&)+0xa7
#12: 0x44d6a9 CommandLineTestRunner::runAllTests()+0xe9
#13: 0x44d799 CommandLineTestRunner::runAllTestsMain()+0x79
#14: 0x44d8fd CommandLineTestRunner::RunAllTests(int, char const**)+0xad
#15: 0x444893 main+0xd3
#16: 0x7f7292b5bb97 __libc_start_main+0xe7
#17: 0x42890a _start+0x2a
Aborted (core dumped)
``` | 1.0 | Parser memory leak - Hey! It seems that in some cases, our Ragel parsers create a memory leak.
To reproduce, if we add for example " test" to the string being parsed ("rtsp://host:123/path?query test"):
https://github.com/roc-project/roc/blob/bc364daf9f77c83706354c19c139b111414a1a0d/src/tests/roc_address/test_endpoint_uri.cpp#L89-L102
The following error appears:
```
src/tests/roc_address/test_endpoint_uri.cpp:99: error: Failure in TEST(endpoint_uri, fields)
expected <query>
but was <query test>
difference starts at position 5 at: < query test >
^
src/modules/roc_core/heap_allocator.cpp:26: error: roc_panic()
ERROR: roc_core: heap allocator: detected leak(s): 2 objects was not freed
Backtrace:
#1: 0x44b57a roc::core::print_backtrace()+0x5a
#2: 0x44ac8a roc::core::crash(char const*)+0x3a
#3: 0x44ac4e roc::core::panic(char const*, char const*, int, char const*, ...)+0x25e
#4: 0x449855 roc::core::HeapAllocator::~HeapAllocator()+0x85
#5: 0x433951 roc::address::TEST_GROUP_CppUTestGroupendpoint_uri::~TEST_GROUP_CppUTestGroupendpoint_uri()+0x31
#6: 0x433515 roc::address::TEST_endpoint_uri_fields_Test::~TEST_endpoint_uri_fields_Test()+0x15
#7: 0x433539 roc::address::TEST_endpoint_uri_fields_Test::~TEST_endpoint_uri_fields_Test()+0x19
#8: 0x45b32e UtestShell::runOneTestInCurrentProcess(TestPlugin*, TestResult&)+0x7e
#9: 0x45b972 PlatformSpecificSetJmpImplementation+0x42
#10: 0x458ea7 UtestShell::runOneTest(TestPlugin*, TestResult&)+0x57
#11: 0x458457 TestRegistry::runAllTests(TestResult&)+0xa7
#12: 0x44d6a9 CommandLineTestRunner::runAllTests()+0xe9
#13: 0x44d799 CommandLineTestRunner::runAllTestsMain()+0x79
#14: 0x44d8fd CommandLineTestRunner::RunAllTests(int, char const**)+0xad
#15: 0x444893 main+0xd3
#16: 0x7f7292b5bb97 __libc_start_main+0xe7
#17: 0x42890a _start+0x2a
Aborted (core dumped)
``` | non_priority | parser memory leak hey it seems that in some cases our ragel parsers create a memory leak to reproduce if we add for example test to the string being parsed rtsp host path query test the following error appears src tests roc address test endpoint uri cpp error failure in test endpoint uri fields expected but was difference starts at position at src modules roc core heap allocator cpp error roc panic error roc core heap allocator detected leak s objects was not freed backtrace roc core print backtrace roc core crash char const roc core panic char const char const int char const roc core heapallocator heapallocator roc address test group cpputestgroupendpoint uri test group cpputestgroupendpoint uri roc address test endpoint uri fields test test endpoint uri fields test roc address test endpoint uri fields test test endpoint uri fields test utestshell runonetestincurrentprocess testplugin testresult platformspecificsetjmpimplementation utestshell runonetest testplugin testresult testregistry runalltests testresult commandlinetestrunner runalltests commandlinetestrunner runalltestsmain commandlinetestrunner runalltests int char const main libc start main start aborted core dumped | 0 |
313,400 | 26,926,848,173 | IssuesEvent | 2023-02-07 14:21:05 | sympy/sympy | https://api.github.com/repos/sympy/sympy | closed | simplified Piecewise is missing conditions | simplify functions.elementary.piecewise Add test to close | I have been trying to write a model for the size of symbolic powers.
I define the Piecewise expression as follows for power `b**e` with
the expressions of the Piecewise giving a value that is representative
of the region in which the size of the power is found (e.g. 1/2 if the
value of the power is between 0 and 1):
```python
var('b e')
A=Piecewise((1, Eq(b, 1) | Eq(e, 0) | (Eq(b, -1) & Eq(Mod(e, 2), 0))),
(0, Eq(b, 0) & (e > 0)), (-1, Eq(b, -1) & Eq(Mod(e, 2), 1)),
(Piecewise((2, ((b > 1) & (e > 0)) | ((b > 0) & (b < 1) & (e < 0)) |
((e >= 2) & (b < -1) & Eq(Mod(e, 2), 0)) | ((e <= -2) & (b > -1) & (b
< 0) & Eq(Mod(e, 2), 0))), (S.Half, ((b > 1) & (e < 0)) | ((b > 0) & (e >
0) & (b < 1)) | ((e <= -2) & (b < -1) & Eq(Mod(e, 2), 0)) | ((e >= 2)
& (b > -1) & (b < 0) & Eq(Mod(e, 2), 0))), (-S.Half, Eq(Mod(e, 2), 1) &
(((e <= -1) & (b < -1)) | ((e >= 1) & (b > -1) & (b < 0)))), (-2, ((e
>= 1) & (b < -1) & Eq(Mod(e, 2), 1)) | ((e <= -1) & (b > -1) & (b < 0)
& Eq(Mod(e, 2), 1)))), Eq(im(b), 0) & Eq(im(e), 0)))
```
As a test of folding and simplification I create the following alternative forms for A
```python
B=piecewise_fold(A)
sa=A.simplify()
sb=B.simplify()
```
I then test the forms over a range of `b` and `e` values:
```python
v = Tuple(-2, -1, -0.5, 0, 0.5, 1, 2)
for i in v:
for j in v:
r = {b:i,e:j}
ok=[k.xreplace(r) for k in (A,B,sa,sb)]
if len(set(ok))!=1:print('ab %s %s'%(r,ok))
```
Although `A` and `B` agree, the simplified forms of each do not and I get these results
```python
s {b: -2, e: -1} [-1/2, -1/2, -1/2, nan]
s {b: -2, e: 1} [-2, -2, -2, nan]
s {b: -1/2, e: 1} [-1/2, -1/2, -1/2, nan]
```
The `nan` indicates that the conditions for the values of `b` and `e` that were passed are not found in the Piecewise expression so a default `nan` is returned. I confirmed that the value returned by `sa` agrees with the value from `A`. I have not yet tracked down the source of the discrepancy from `sb` in which are missing the cases for -2 and -1/2:
```python
Piecewise(
(1, Eq(b, 1) | Eq(e, 0) | (Eq(b, -1) & Eq(Mod(e, 2), 0))),
(0, Eq(b, 0) & (e > 0)),
(-1, Eq(b, -1) & Eq(Mod(e, 2), 1)),
(2, Eq(im(b), 0) & Eq(im(e), 0) & ((b > 0) | (b > 1)) & ((b > 0) | (e > 0)) & ((b > 1) | (b < 1)) & ((b > 1) | (e < 0)) & ((e > 0) | (b < 1)) & ((e > 0) | (e < 0))),
(1/2, Eq(im(b), 0) & Eq(im(e), 0) & ((b > 0) | (b > 1)) & ((b > 0) | (e < 0)) & ((b > 1) | (e > 0)) & ((b > 1) | (b < 1)) & ((e > 0) | (e < 0)) & ((b < 1) | (e <0))))
``` | 1.0 | simplified Piecewise is missing conditions - I have been trying to write a model for the size of symbolic powers.
I define the Piecewise expression as follows for power `b**e` with
the expressions of the Piecewise giving a value that is representative
of the region in which the size of the power is found (e.g. 1/2 if the
value of the power is between 0 and 1):
```python
var('b e')
A=Piecewise((1, Eq(b, 1) | Eq(e, 0) | (Eq(b, -1) & Eq(Mod(e, 2), 0))),
(0, Eq(b, 0) & (e > 0)), (-1, Eq(b, -1) & Eq(Mod(e, 2), 1)),
(Piecewise((2, ((b > 1) & (e > 0)) | ((b > 0) & (b < 1) & (e < 0)) |
((e >= 2) & (b < -1) & Eq(Mod(e, 2), 0)) | ((e <= -2) & (b > -1) & (b
< 0) & Eq(Mod(e, 2), 0))), (S.Half, ((b > 1) & (e < 0)) | ((b > 0) & (e >
0) & (b < 1)) | ((e <= -2) & (b < -1) & Eq(Mod(e, 2), 0)) | ((e >= 2)
& (b > -1) & (b < 0) & Eq(Mod(e, 2), 0))), (-S.Half, Eq(Mod(e, 2), 1) &
(((e <= -1) & (b < -1)) | ((e >= 1) & (b > -1) & (b < 0)))), (-2, ((e
>= 1) & (b < -1) & Eq(Mod(e, 2), 1)) | ((e <= -1) & (b > -1) & (b < 0)
& Eq(Mod(e, 2), 1)))), Eq(im(b), 0) & Eq(im(e), 0)))
```
As a test of folding and simplification I create the following alternative forms for A
```python
B=piecewise_fold(A)
sa=A.simplify()
sb=B.simplify()
```
I then test the forms over a range of `b` and `e` values:
```python
v = Tuple(-2, -1, -0.5, 0, 0.5, 1, 2)
for i in v:
for j in v:
r = {b:i,e:j}
ok=[k.xreplace(r) for k in (A,B,sa,sb)]
if len(set(ok))!=1:print('ab %s %s'%(r,ok))
```
Although `A` and `B` agree, the simplified forms of each do not and I get these results
```python
s {b: -2, e: -1} [-1/2, -1/2, -1/2, nan]
s {b: -2, e: 1} [-2, -2, -2, nan]
s {b: -1/2, e: 1} [-1/2, -1/2, -1/2, nan]
```
The `nan` indicates that the conditions for the values of `b` and `e` that were passed are not found in the Piecewise expression so a default `nan` is returned. I confirmed that the value returned by `sa` agrees with the value from `A`. I have not yet tracked down the source of the discrepancy from `sb` in which are missing the cases for -2 and -1/2:
```python
Piecewise(
(1, Eq(b, 1) | Eq(e, 0) | (Eq(b, -1) & Eq(Mod(e, 2), 0))),
(0, Eq(b, 0) & (e > 0)),
(-1, Eq(b, -1) & Eq(Mod(e, 2), 1)),
(2, Eq(im(b), 0) & Eq(im(e), 0) & ((b > 0) | (b > 1)) & ((b > 0) | (e > 0)) & ((b > 1) | (b < 1)) & ((b > 1) | (e < 0)) & ((e > 0) | (b < 1)) & ((e > 0) | (e < 0))),
(1/2, Eq(im(b), 0) & Eq(im(e), 0) & ((b > 0) | (b > 1)) & ((b > 0) | (e < 0)) & ((b > 1) | (e > 0)) & ((b > 1) | (b < 1)) & ((e > 0) | (e < 0)) & ((b < 1) | (e <0))))
``` | non_priority | simplified piecewise is missing conditions i have been trying to write a model for the size of symbolic powers i define the piecewise expression as follows for power b e with the expressions of the piecewise giving a value that is representative of the region in which the size of the power is found e g if the value of the power is between and python var b e a piecewise eq b eq e eq b eq mod e eq b e eq b eq mod e piecewise b e b b e e b b e e b b b eq mod e s half eq mod e e b b e b b eq mod e eq im b eq im e as a test of folding and simplification i create the following alternative forms for a python b piecewise fold a sa a simplify sb b simplify i then test the forms over a range of b and e values python v tuple for i in v for j in v r b i e j ok if len set ok print ab s s r ok although a and b agree the simplified forms of each do not and i get these results python s b e s b e s b e the nan indicates that the conditions for the values of b and e that were passed are not found in the piecewise expression so a default nan is returned i confirmed that the value returned by sa agrees with the value from a i have not yet tracked down the source of the discrepancy from sb in which are missing the cases for and python piecewise eq b eq e eq b eq mod e eq b e eq b eq mod e eq im b eq im e b b b e b b e b e eq im b eq im e b b b e e b b e b e | 0 |
88,481 | 15,801,792,883 | IssuesEvent | 2021-04-03 06:36:01 | atlslscsrv-app/upgraded-waddle | https://api.github.com/repos/atlslscsrv-app/upgraded-waddle | opened | WS-2019-0027 (Medium) detected in marked-0.3.6.js | security vulnerability | ## WS-2019-0027 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>marked-0.3.6.js</b></p></summary>
<p>A markdown parser built for speed</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/marked/0.3.6/marked.js">https://cdnjs.cloudflare.com/ajax/libs/marked/0.3.6/marked.js</a></p>
<p>Path to vulnerable library: upgraded-waddle/dist/resources/app/node_modules/marked/lib/marked.js</p>
<p>
Dependency Hierarchy:
- :x: **marked-0.3.6.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/atlslscsrv-app/upgraded-waddle/commit/1276c3f8dfa20d6b9e11c763abc35bb6e59a82a7">1276c3f8dfa20d6b9e11c763abc35bb6e59a82a7</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Versions 0.3.17 and earlier of marked has Four regexes were vulnerable to catastrophic backtracking. This leaves markdown servers open to a potential REDOS attack.
<p>Publish Date: 2018-02-26
<p>URL: <a href=https://github.com/markedjs/marked/commit/b15e42b67cec9ded8505e9d68bb8741ad7a9590d>WS-2019-0027</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/markedjs/marked/commit/b15e42b67cec9ded8505e9d68bb8741ad7a9590d">https://github.com/markedjs/marked/commit/b15e42b67cec9ded8505e9d68bb8741ad7a9590d</a></p>
<p>Release Date: 2019-03-17</p>
<p>Fix Resolution: 0.3.18</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | WS-2019-0027 (Medium) detected in marked-0.3.6.js - ## WS-2019-0027 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>marked-0.3.6.js</b></p></summary>
<p>A markdown parser built for speed</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/marked/0.3.6/marked.js">https://cdnjs.cloudflare.com/ajax/libs/marked/0.3.6/marked.js</a></p>
<p>Path to vulnerable library: upgraded-waddle/dist/resources/app/node_modules/marked/lib/marked.js</p>
<p>
Dependency Hierarchy:
- :x: **marked-0.3.6.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/atlslscsrv-app/upgraded-waddle/commit/1276c3f8dfa20d6b9e11c763abc35bb6e59a82a7">1276c3f8dfa20d6b9e11c763abc35bb6e59a82a7</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Versions 0.3.17 and earlier of marked has Four regexes were vulnerable to catastrophic backtracking. This leaves markdown servers open to a potential REDOS attack.
<p>Publish Date: 2018-02-26
<p>URL: <a href=https://github.com/markedjs/marked/commit/b15e42b67cec9ded8505e9d68bb8741ad7a9590d>WS-2019-0027</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/markedjs/marked/commit/b15e42b67cec9ded8505e9d68bb8741ad7a9590d">https://github.com/markedjs/marked/commit/b15e42b67cec9ded8505e9d68bb8741ad7a9590d</a></p>
<p>Release Date: 2019-03-17</p>
<p>Fix Resolution: 0.3.18</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | ws medium detected in marked js ws medium severity vulnerability vulnerable library marked js a markdown parser built for speed library home page a href path to vulnerable library upgraded waddle dist resources app node modules marked lib marked js dependency hierarchy x marked js vulnerable library found in head commit a href found in base branch master vulnerability details versions and earlier of marked has four regexes were vulnerable to catastrophic backtracking this leaves markdown servers open to a potential redos attack publish date url a href cvss score details base score metrics not available suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
232,374 | 25,576,228,026 | IssuesEvent | 2022-11-30 22:24:25 | golang/go | https://api.github.com/repos/golang/go | closed | x/net/http2/h2c: ineffective mitigation for unsafe io.ReadAll [1.18 backport] | Security CherryPickApproved | @neild requested issue #56352 to be considered for backport to the next 1.18 minor release.
> @gopherbot please open backport issues, this is a potential request smuggling vector
| True | x/net/http2/h2c: ineffective mitigation for unsafe io.ReadAll [1.18 backport] - @neild requested issue #56352 to be considered for backport to the next 1.18 minor release.
> @gopherbot please open backport issues, this is a potential request smuggling vector
| non_priority | x net ineffective mitigation for unsafe io readall neild requested issue to be considered for backport to the next minor release gopherbot please open backport issues this is a potential request smuggling vector | 0 |
67,312 | 9,023,740,954 | IssuesEvent | 2019-02-07 08:28:57 | zendframework/zend-i18n | https://api.github.com/repos/zendframework/zend-i18n | closed | Missing documentation for Zend\I18n\Validator\PostCode | EasyFix bug documentation | The validator "PostCode" needs some explanations and code examples.
https://github.com/zendframework/zend-i18n/blob/master/src/Validator/PostCode.php | 1.0 | Missing documentation for Zend\I18n\Validator\PostCode - The validator "PostCode" needs some explanations and code examples.
https://github.com/zendframework/zend-i18n/blob/master/src/Validator/PostCode.php | non_priority | missing documentation for zend validator postcode the validator postcode needs some explanations and code examples | 0 |
346,068 | 30,864,338,909 | IssuesEvent | 2023-08-03 06:54:34 | microsoft/vscode | https://api.github.com/repos/microsoft/vscode | opened | Unit test failure: extension is installed and enabled when installed by server cli | unit-test-failure | https://dev.azure.com/monacotools/Monaco/_build/results?buildId=226386&view=logs&j=a5d99aad-4929-5289-bf4a-26b78032353d&t=63d40075-f8bd-5843-b20c-bf914eb0111d&l=657
```
271 passing (2m)
16 pending
1 failing
1) vscode server cli
extension is installed and enabled when installed by server cli:
AssertionError [ERR_ASSERTION] [ERR_ASSERTION]: The expression evaluated to a falsy value:
assert.ok(vscode.extensions.getExtension(extension))
at Context.<anonymous> (/Users/runner/work/1/s/extensions/vscode-api-tests/src/singlefolder-tests/extensions.test.ts:23:10)
at processImmediate (node:internal/timers:466:21)
``` | 1.0 | Unit test failure: extension is installed and enabled when installed by server cli - https://dev.azure.com/monacotools/Monaco/_build/results?buildId=226386&view=logs&j=a5d99aad-4929-5289-bf4a-26b78032353d&t=63d40075-f8bd-5843-b20c-bf914eb0111d&l=657
```
271 passing (2m)
16 pending
1 failing
1) vscode server cli
extension is installed and enabled when installed by server cli:
AssertionError [ERR_ASSERTION] [ERR_ASSERTION]: The expression evaluated to a falsy value:
assert.ok(vscode.extensions.getExtension(extension))
at Context.<anonymous> (/Users/runner/work/1/s/extensions/vscode-api-tests/src/singlefolder-tests/extensions.test.ts:23:10)
at processImmediate (node:internal/timers:466:21)
``` | non_priority | unit test failure extension is installed and enabled when installed by server cli passing pending failing vscode server cli extension is installed and enabled when installed by server cli assertionerror the expression evaluated to a falsy value assert ok vscode extensions getextension extension at context users runner work s extensions vscode api tests src singlefolder tests extensions test ts at processimmediate node internal timers | 0 |
68,352 | 8,263,314,430 | IssuesEvent | 2018-09-14 01:37:14 | dotnet/roslyn | https://api.github.com/repos/dotnet/roslyn | closed | C# comment <summary> showing in collapsed mode | Area-IDE Developer Community Need Design Review Resolution-By Design | Using c# comments
/// <summary>
/// Import
/// </summary>
/// <param name="fileStream"></param>
/// <returns></returns>
Task<long> Import(Stream fileStream);
In collpased mode it shows
/// <summary> Import
The <summary> portion shouldn't be seen
_This issue has been moved from https://developercommunity.visualstudio.com/content/problem/276820/c-comment-showing-in-collapsed-mode.html
VSTS ticketId: 635931_
_These are the original issue comments:_
DotnetShadow on 6/19/2018, 04:13 PM (5 days ago): This issue seems to affect c# Interface onl
_These are the original issue solutions:_
(no solutions) | 2.0 | C# comment <summary> showing in collapsed mode - Using c# comments
/// <summary>
/// Import
/// </summary>
/// <param name="fileStream"></param>
/// <returns></returns>
Task<long> Import(Stream fileStream);
In collpased mode it shows
/// <summary> Import
The <summary> portion shouldn't be seen
_This issue has been moved from https://developercommunity.visualstudio.com/content/problem/276820/c-comment-showing-in-collapsed-mode.html
VSTS ticketId: 635931_
_These are the original issue comments:_
DotnetShadow on 6/19/2018, 04:13 PM (5 days ago): This issue seems to affect c# Interface onl
_These are the original issue solutions:_
(no solutions) | non_priority | c comment showing in collapsed mode using c comments lt summary gt import lt summary gt lt param name quot filestream quot gt lt param gt lt returns gt lt returns gt task lt long gt import stream filestream in collpased mode it shows lt summary gt import the lt summary gt portion shouldn t be seen this issue has been moved from vsts ticketid these are the original issue comments dotnetshadow on pm days ago this issue seems to affect c interface onl these are the original issue solutions no solutions | 0 |
47,460 | 10,097,467,485 | IssuesEvent | 2019-07-28 06:10:53 | WarEmu/WarBugs | https://api.github.com/repos/WarEmu/WarBugs | closed | WL Pet keeps flames of rhuin even when BW leaves party | Ability Sourcecode | Expected behavior and actual behavior: Flames of rhuin vanishes from pet when BW leaves party. Pet is keeping the enchantment.
Steps to reproduce the problem: Have a BW in party use Flames of Rhuin near pet, kick BW from party and pet should still have FoR while you have lost it.
Ye is the name of the pet
Screenshots/Videos or archive.org evidences:
| 1.0 | WL Pet keeps flames of rhuin even when BW leaves party - Expected behavior and actual behavior: Flames of rhuin vanishes from pet when BW leaves party. Pet is keeping the enchantment.
Steps to reproduce the problem: Have a BW in party use Flames of Rhuin near pet, kick BW from party and pet should still have FoR while you have lost it.
Ye is the name of the pet
Screenshots/Videos or archive.org evidences:
| non_priority | wl pet keeps flames of rhuin even when bw leaves party expected behavior and actual behavior flames of rhuin vanishes from pet when bw leaves party pet is keeping the enchantment steps to reproduce the problem have a bw in party use flames of rhuin near pet kick bw from party and pet should still have for while you have lost it ye is the name of the pet screenshots videos or archive org evidences | 0 |
17,159 | 3,595,197,285 | IssuesEvent | 2016-02-02 04:34:14 | kumulsoft/Fixed-Assets | https://api.github.com/repos/kumulsoft/Fixed-Assets | reopened | Capture Release version on home page screen | enhancement Fixed Ready for testing | Refer image below where the location it should appear.
| 1.0 | Capture Release version on home page screen - Refer image below where the location it should appear.
| non_priority | capture release version on home page screen refer image below where the location it should appear | 0 |
26,168 | 26,510,263,322 | IssuesEvent | 2023-01-18 16:34:56 | godotengine/godot | https://api.github.com/repos/godotengine/godot | closed | Editing complex TileMap results in significant editor freeze | bug topic:editor usability topic:2d performance | ### Godot version
ed300d7
### System information
W10
### Issue description
I have a complex TileSet with over 20 atlas sources and scenes with hundreds of tiles. Whenever I click TileMap to edit it, the editor will freeze for a couple of seconds (5 in release_debug build) before the Tile editor will open.
Opening or switching to scenes that contain TileMap also results in a freeze.
### Steps to reproduce
1. Open the attached project
2. Open LagExample scene
3. Click TileMap
### Minimal reproduction project
[TileMapLag.zip](https://github.com/godotengine/godot/files/7532993/TileMapLag.zip)
| True | Editing complex TileMap results in significant editor freeze - ### Godot version
ed300d7
### System information
W10
### Issue description
I have a complex TileSet with over 20 atlas sources and scenes with hundreds of tiles. Whenever I click TileMap to edit it, the editor will freeze for a couple of seconds (5 in release_debug build) before the Tile editor will open.
Opening or switching to scenes that contain TileMap also results in a freeze.
### Steps to reproduce
1. Open the attached project
2. Open LagExample scene
3. Click TileMap
### Minimal reproduction project
[TileMapLag.zip](https://github.com/godotengine/godot/files/7532993/TileMapLag.zip)
| non_priority | editing complex tilemap results in significant editor freeze godot version system information issue description i have a complex tileset with over atlas sources and scenes with hundreds of tiles whenever i click tilemap to edit it the editor will freeze for a couple of seconds in release debug build before the tile editor will open opening or switching to scenes that contain tilemap also results in a freeze steps to reproduce open the attached project open lagexample scene click tilemap minimal reproduction project | 0 |
219,393 | 17,089,506,529 | IssuesEvent | 2021-07-08 15:37:18 | HackingPolitics/hp-frontend | https://api.github.com/repos/HackingPolitics/hp-frontend | closed | Handlungsauftrag fehlt | betatest | Im Screen Problem und Handlungsauftrag fehlt der Handlungsauftrag:
Aktuell kann der User nicht sagen, was die Verwaltung eigentlich tun soll:
https://testing.hacking-politics.de/antraege/79/problem | 1.0 | Handlungsauftrag fehlt - Im Screen Problem und Handlungsauftrag fehlt der Handlungsauftrag:
Aktuell kann der User nicht sagen, was die Verwaltung eigentlich tun soll:
https://testing.hacking-politics.de/antraege/79/problem | non_priority | handlungsauftrag fehlt im screen problem und handlungsauftrag fehlt der handlungsauftrag aktuell kann der user nicht sagen was die verwaltung eigentlich tun soll | 0 |
11,631 | 3,510,358,900 | IssuesEvent | 2016-01-09 12:02:31 | PaulStoffregen/Audio | https://api.github.com/repos/PaulStoffregen/Audio | closed | Need AudioSynthWaveformSineModulated "sine_fm" example | Documentation Needed | Maybe someone really experienced with synthesis could create a nice example using this object and perhaps the envelope or other waveforms at low frequency to control it? Ideally, something rhythmic or musical sounding, rather than "random noises", would be perfect. | 1.0 | Need AudioSynthWaveformSineModulated "sine_fm" example - Maybe someone really experienced with synthesis could create a nice example using this object and perhaps the envelope or other waveforms at low frequency to control it? Ideally, something rhythmic or musical sounding, rather than "random noises", would be perfect. | non_priority | need audiosynthwaveformsinemodulated sine fm example maybe someone really experienced with synthesis could create a nice example using this object and perhaps the envelope or other waveforms at low frequency to control it ideally something rhythmic or musical sounding rather than random noises would be perfect | 0 |
35,917 | 14,896,585,508 | IssuesEvent | 2021-01-21 10:35:26 | terraform-providers/terraform-provider-azurerm | https://api.github.com/repos/terraform-providers/terraform-provider-azurerm | closed | Support for Log Analytics auditing on azurerm_mssql_server/database | enhancement sdk/requires-upgrade service/mssql upstream-microsoft | <!--- Please keep this note for the community --->
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
<!--- Thank you for keeping this note for the community --->
### Description
Please can we get some support for adding the Log Analytics destination on auditing. At present only the storage option is supported in the extended_auditing_policy block.
### New or Affected Resource(s)
azurerm_sql_server
azurerm_mssql_server
### Potential Terraform Configuration
resource "azurerm_mssql_server" "example" {
name = "mssqlserver"
resource_group_name = azurerm_resource_group.example.name
location = azurerm_resource_group.example.location
version = "12.0"
administrator_login = "missadministrator"
administrator_login_password = "thisIsKat11"
extended_auditing_policy {
azuremonitor_target_enabled = true
log_analytics_workspace_id = data.azurerm_log_analytics_workspace.oms.id
}
The arm template when setting is configured looks like this:
{
"type": "Microsoft.Sql/servers/auditingSettings",
"apiVersion": "2017-03-01-preview",
"name": "[concat(parameters('servers_xxxxxxxxxxxxxxx_name'), '/Default')]",
"dependsOn": [
"[resourceId('Microsoft.Sql/servers', parameters('servers_xxxxxxxxxxxxxxx_name'))]"
],
"properties": {
"state": "Enabled",
"retentionDays": 0,
"auditActionsAndGroups": [
"SUCCESSFUL_DATABASE_AUTHENTICATION_GROUP",
"FAILED_DATABASE_AUTHENTICATION_GROUP",
"BATCH_COMPLETED_GROUP"
],
"storageAccountSubscriptionId": "00000000-0000-0000-0000-000000000000",
"isStorageSecondaryKeyInUse": false,
**"isAzureMonitorTargetEnabled": true**
}
}
```hcl
# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.
```
### References
<!---
Information about referencing Github Issues: https://help.github.com/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests
Are there any other GitHub issues (open or closed) or pull requests that should be linked here? Vendor blog posts or documentation? For example:
* https://azure.microsoft.com/en-us/roadmap/virtual-network-service-endpoint-for-azure-cosmos-db/
--->
* #0000
| 1.0 | Support for Log Analytics auditing on azurerm_mssql_server/database - <!--- Please keep this note for the community --->
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
<!--- Thank you for keeping this note for the community --->
### Description
Please can we get some support for adding the Log Analytics destination on auditing. At present only the storage option is supported in the extended_auditing_policy block.
### New or Affected Resource(s)
azurerm_sql_server
azurerm_mssql_server
### Potential Terraform Configuration
resource "azurerm_mssql_server" "example" {
name = "mssqlserver"
resource_group_name = azurerm_resource_group.example.name
location = azurerm_resource_group.example.location
version = "12.0"
administrator_login = "missadministrator"
administrator_login_password = "thisIsKat11"
extended_auditing_policy {
azuremonitor_target_enabled = true
log_analytics_workspace_id = data.azurerm_log_analytics_workspace.oms.id
}
The arm template when setting is configured looks like this:
{
"type": "Microsoft.Sql/servers/auditingSettings",
"apiVersion": "2017-03-01-preview",
"name": "[concat(parameters('servers_xxxxxxxxxxxxxxx_name'), '/Default')]",
"dependsOn": [
"[resourceId('Microsoft.Sql/servers', parameters('servers_xxxxxxxxxxxxxxx_name'))]"
],
"properties": {
"state": "Enabled",
"retentionDays": 0,
"auditActionsAndGroups": [
"SUCCESSFUL_DATABASE_AUTHENTICATION_GROUP",
"FAILED_DATABASE_AUTHENTICATION_GROUP",
"BATCH_COMPLETED_GROUP"
],
"storageAccountSubscriptionId": "00000000-0000-0000-0000-000000000000",
"isStorageSecondaryKeyInUse": false,
**"isAzureMonitorTargetEnabled": true**
}
}
```hcl
# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.
```
### References
<!---
Information about referencing Github Issues: https://help.github.com/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests
Are there any other GitHub issues (open or closed) or pull requests that should be linked here? Vendor blog posts or documentation? For example:
* https://azure.microsoft.com/en-us/roadmap/virtual-network-service-endpoint-for-azure-cosmos-db/
--->
* #0000
| non_priority | support for log analytics auditing on azurerm mssql server database community note please vote on this issue by adding a 👍 to the original issue to help the community and maintainers prioritize this request please do not leave or me too comments they generate extra noise for issue followers and do not help prioritize the request if you are interested in working on this issue or have submitted a pull request please leave a comment description please can we get some support for adding the log analytics destination on auditing at present only the storage option is supported in the extended auditing policy block new or affected resource s azurerm sql server azurerm mssql server potential terraform configuration resource azurerm mssql server example name mssqlserver resource group name azurerm resource group example name location azurerm resource group example location version administrator login missadministrator administrator login password extended auditing policy azuremonitor target enabled true log analytics workspace id data azurerm log analytics workspace oms id the arm template when setting is configured looks like this type microsoft sql servers auditingsettings apiversion preview name dependson properties state enabled retentiondays auditactionsandgroups successful database authentication group failed database authentication group batch completed group storageaccountsubscriptionid isstoragesecondarykeyinuse false isazuremonitortargetenabled true hcl copy paste your terraform configurations here for large terraform configs please use a service like dropbox and share a link to the zip file for security you can also encrypt the files using our gpg public key references information about referencing github issues are there any other github issues open or closed or pull requests that should be linked here vendor blog posts or documentation for example | 0 |
120,570 | 12,091,511,670 | IssuesEvent | 2020-04-19 11:58:00 | borgbackup/borg | https://api.github.com/repos/borgbackup/borg | closed | recreate deletes all files using --patterns-from parameter | documentation | <!--
Thank you for reporting an issue.
*IMPORTANT* - *before* creating a new issue please look around:
- Borgbackup documentation: http://borgbackup.readthedocs.io/en/stable/index.html
- FAQ: https://borgbackup.readthedocs.io/en/stable/faq.html
and
- open issues in Github tracker: https://github.com/borgbackup/borg/issues
If you cannot find a similar problem, then create a new issue.
Please fill in as much of the template as possible.
-->
## Have you checked borgbackup docs, FAQ, and open Github issues?
Yes
## Is this a BUG / ISSUE report or a QUESTION?
Bug
## System information. For client/server mode post info for both machines.
Dell Laptop
#### Your borg version (borg -V).
borg 1.1.7
#### Operating system (distribution) and version.
Linux Solus v3.99999
#### Hardware / network configuration, and filesystems used.
ext4
#### How much data is handled by borg?
2.3M (test case)
#### Full borg commandline that lead to the problem (leave away excludes and passwords)
borg create --stat --verbose --list .::full ~/R_script
borg create --stat --verbose --list --patterns-from test.lst .::patterns
borg recreate --stat --verbose --list --patterns-from test.lst --target full.recreated .::full
CONTENTS: R_Script
R_Script/test.R
R_Script/.Rproj.user/7038483/pcs/files-pane.pper (and many other files under .Rproj.user)
R_Script/Jags-Ydich-XnomSsubj-MbernBeta-Diagtheta[1].eps
R_Script/Jags-Ydich-XnomSsubj-MbernBeta-Diagtheta[2].eps
R_Script/Jags-Ydich-XnomSsubj-MbernBeta-Diagtheta[3].eps
R_Script/Jags-Ydich-XnomSsubj-MbernBeta-Diagtheta[4].eps
R_Script/R_Script/Jags-Ydich-XnomSsubj-MbernBeta-Post.eps
CONTENT:S test.lst
```
P re
R /home/user/R_script
+ .*Jags.*(1).*
- .*\.eps.*
- .*\.Rproj.*
```
## Describe the problem you're observing.
I run the full backup under with the full archive. The files look like they're all backed up under borg list .::full. Then, I create a new backup with --from-patterns test.lst. The backup seems to work as expected backing up everything but the *.eps and *.Rproj* files but keeps the R_Script/test.R and R_Script/Jags-Ydich-XnomSsubj-MbernBeta-Diagtheta[1].eps file as specified by the 1st "+" line of test.lst. Finally, I run recreate on the full archive. I expected the results to be effectively same as the patterns backup in my full.recreated archive . However, it deletes everything but the R_Script/Jags-Ydich-XnomSsubj-MbernBeta-Diagtheta[1].eps file. Even if I run the recreate command without --target and overwrite the full archive, R_Script/Jags-Ydich-XnomSsubj-MbernBeta-Diagtheta[1].eps is still the only file in the full archive after recreate.
#### Can you reproduce the problem? If so, describe how. If not, describe troubleshooting steps you took before opening the issue.
Yes - please see steps above. I used a very small test directory.
#### Include any warning/errors/backtraces from the system logs
No warnings or errors.
<!--
If this complaint relates to borg performance, please include CRUD benchmark
results and any steps you took to troubleshoot.
How to run benchmark: http://borgbackup.readthedocs.io/en/stable/usage/benchmark.html
*IMPORTANT* - Please mark logs and text output from terminal commands
or else Github will not display them correctly.
An example is provided below.
Example:
```
this is an example how log text should be marked (wrap it with ```)
```
-->
| 1.0 | recreate deletes all files using --patterns-from parameter - <!--
Thank you for reporting an issue.
*IMPORTANT* - *before* creating a new issue please look around:
- Borgbackup documentation: http://borgbackup.readthedocs.io/en/stable/index.html
- FAQ: https://borgbackup.readthedocs.io/en/stable/faq.html
and
- open issues in Github tracker: https://github.com/borgbackup/borg/issues
If you cannot find a similar problem, then create a new issue.
Please fill in as much of the template as possible.
-->
## Have you checked borgbackup docs, FAQ, and open Github issues?
Yes
## Is this a BUG / ISSUE report or a QUESTION?
Bug
## System information. For client/server mode post info for both machines.
Dell Laptop
#### Your borg version (borg -V).
borg 1.1.7
#### Operating system (distribution) and version.
Linux Solus v3.99999
#### Hardware / network configuration, and filesystems used.
ext4
#### How much data is handled by borg?
2.3M (test case)
#### Full borg commandline that lead to the problem (leave away excludes and passwords)
borg create --stat --verbose --list .::full ~/R_script
borg create --stat --verbose --list --patterns-from test.lst .::patterns
borg recreate --stat --verbose --list --patterns-from test.lst --target full.recreated .::full
CONTENTS: R_Script
R_Script/test.R
R_Script/.Rproj.user/7038483/pcs/files-pane.pper (and many other files under .Rproj.user)
R_Script/Jags-Ydich-XnomSsubj-MbernBeta-Diagtheta[1].eps
R_Script/Jags-Ydich-XnomSsubj-MbernBeta-Diagtheta[2].eps
R_Script/Jags-Ydich-XnomSsubj-MbernBeta-Diagtheta[3].eps
R_Script/Jags-Ydich-XnomSsubj-MbernBeta-Diagtheta[4].eps
R_Script/R_Script/Jags-Ydich-XnomSsubj-MbernBeta-Post.eps
CONTENT:S test.lst
```
P re
R /home/user/R_script
+ .*Jags.*(1).*
- .*\.eps.*
- .*\.Rproj.*
```
## Describe the problem you're observing.
I run the full backup under with the full archive. The files look like they're all backed up under borg list .::full. Then, I create a new backup with --from-patterns test.lst. The backup seems to work as expected backing up everything but the *.eps and *.Rproj* files but keeps the R_Script/test.R and R_Script/Jags-Ydich-XnomSsubj-MbernBeta-Diagtheta[1].eps file as specified by the 1st "+" line of test.lst. Finally, I run recreate on the full archive. I expected the results to be effectively same as the patterns backup in my full.recreated archive . However, it deletes everything but the R_Script/Jags-Ydich-XnomSsubj-MbernBeta-Diagtheta[1].eps file. Even if I run the recreate command without --target and overwrite the full archive, R_Script/Jags-Ydich-XnomSsubj-MbernBeta-Diagtheta[1].eps is still the only file in the full archive after recreate.
#### Can you reproduce the problem? If so, describe how. If not, describe troubleshooting steps you took before opening the issue.
Yes - please see steps above. I used a very small test directory.
#### Include any warning/errors/backtraces from the system logs
No warnings or errors.
<!--
If this complaint relates to borg performance, please include CRUD benchmark
results and any steps you took to troubleshoot.
How to run benchmark: http://borgbackup.readthedocs.io/en/stable/usage/benchmark.html
*IMPORTANT* - Please mark logs and text output from terminal commands
or else Github will not display them correctly.
An example is provided below.
Example:
```
this is an example how log text should be marked (wrap it with ```)
```
-->
| non_priority | recreate deletes all files using patterns from parameter thank you for reporting an issue important before creating a new issue please look around borgbackup documentation faq and open issues in github tracker if you cannot find a similar problem then create a new issue please fill in as much of the template as possible have you checked borgbackup docs faq and open github issues yes is this a bug issue report or a question bug system information for client server mode post info for both machines dell laptop your borg version borg v borg operating system distribution and version linux solus hardware network configuration and filesystems used how much data is handled by borg test case full borg commandline that lead to the problem leave away excludes and passwords borg create stat verbose list full r script borg create stat verbose list patterns from test lst patterns borg recreate stat verbose list patterns from test lst target full recreated full contents r script r script test r r script rproj user pcs files pane pper and many other files under rproj user r script jags ydich xnomssubj mbernbeta diagtheta eps r script jags ydich xnomssubj mbernbeta diagtheta eps r script jags ydich xnomssubj mbernbeta diagtheta eps r script jags ydich xnomssubj mbernbeta diagtheta eps r script r script jags ydich xnomssubj mbernbeta post eps content s test lst p re r home user r script jags eps rproj describe the problem you re observing i run the full backup under with the full archive the files look like they re all backed up under borg list full then i create a new backup with from patterns test lst the backup seems to work as expected backing up everything but the eps and rproj files but keeps the r script test r and r script jags ydich xnomssubj mbernbeta diagtheta eps file as specified by the line of test lst finally i run recreate on the full archive i expected the results to be effectively same as the patterns backup in my full recreated archive however it deletes everything but the r script jags ydich xnomssubj mbernbeta diagtheta eps file even if i run the recreate command without target and overwrite the full archive r script jags ydich xnomssubj mbernbeta diagtheta eps is still the only file in the full archive after recreate can you reproduce the problem if so describe how if not describe troubleshooting steps you took before opening the issue yes please see steps above i used a very small test directory include any warning errors backtraces from the system logs no warnings or errors if this complaint relates to borg performance please include crud benchmark results and any steps you took to troubleshoot how to run benchmark important please mark logs and text output from terminal commands or else github will not display them correctly an example is provided below example this is an example how log text should be marked wrap it with | 0 |
177,157 | 14,617,510,890 | IssuesEvent | 2020-12-22 14:53:32 | MetOffice/XBTs_classification | https://api.github.com/repos/MetOffice/XBTs_classification | opened | Preparation for SPICE production | documentation production | Some tidying up of the data and trained algorithms on the SPICE platform ahead of the use of the XBT code for production of Ocean Dataset products. These tasks include:
- [] Write readme files about the `xbt-data` and `xbt-results` directories
- [] create symlinks to identify which data directories, experiment configurations and trained algorithms are the current ones that should be used for production
- [] ensure experiment configuration mentions which version of the code it should be used with | 1.0 | Preparation for SPICE production - Some tidying up of the data and trained algorithms on the SPICE platform ahead of the use of the XBT code for production of Ocean Dataset products. These tasks include:
- [] Write readme files about the `xbt-data` and `xbt-results` directories
- [] create symlinks to identify which data directories, experiment configurations and trained algorithms are the current ones that should be used for production
- [] ensure experiment configuration mentions which version of the code it should be used with | non_priority | preparation for spice production some tidying up of the data and trained algorithms on the spice platform ahead of the use of the xbt code for production of ocean dataset products these tasks include write readme files about the xbt data and xbt results directories create symlinks to identify which data directories experiment configurations and trained algorithms are the current ones that should be used for production ensure experiment configuration mentions which version of the code it should be used with | 0 |
178,693 | 29,975,255,666 | IssuesEvent | 2023-06-24 00:42:54 | flutter/flutter | https://api.github.com/repos/flutter/flutter | closed | test design doc issue | design doc | ### Document Link
flutter.dev/go/link
### What problem are you solving?
bla bla bla
this is the description | 1.0 | test design doc issue - ### Document Link
flutter.dev/go/link
### What problem are you solving?
bla bla bla
this is the description | non_priority | test design doc issue document link flutter dev go link what problem are you solving bla bla bla this is the description | 0 |
2,794 | 2,637,299,355 | IssuesEvent | 2015-03-10 12:17:58 | RequestPolicyContinued/requestpolicy | https://api.github.com/repos/RequestPolicyContinued/requestpolicy | opened | test restartlessness | unit test | actions like disabling, enabling, uninstalling, installing and upgrading (all of them without a restart) need to be tested. After each of those actions, the unit test should rerun.
I'm currently working on this. | 1.0 | test restartlessness - actions like disabling, enabling, uninstalling, installing and upgrading (all of them without a restart) need to be tested. After each of those actions, the unit test should rerun.
I'm currently working on this. | non_priority | test restartlessness actions like disabling enabling uninstalling installing and upgrading all of them without a restart need to be tested after each of those actions the unit test should rerun i m currently working on this | 0 |
26,707 | 4,240,329,753 | IssuesEvent | 2016-07-06 13:05:01 | hioa-cs/IncludeOS | https://api.github.com/repos/hioa-cs/IncludeOS | closed | test: exceptions incomplete | C++ standard library Refactoring Test | - Missing new test system (test.py)
- Missing SUCCESS
- Needs to be updated with either macro or lest test framework (preferred) | 1.0 | test: exceptions incomplete - - Missing new test system (test.py)
- Missing SUCCESS
- Needs to be updated with either macro or lest test framework (preferred) | non_priority | test exceptions incomplete missing new test system test py missing success needs to be updated with either macro or lest test framework preferred | 0 |
53,824 | 7,858,722,289 | IssuesEvent | 2018-06-21 14:39:11 | CartoDB/carto-vl | https://api.github.com/repos/CartoDB/carto-vl | opened | Fix docs generation | documentation | There are some consistency issues when the generation of the documentation and in the docs.
1. In [CartoDB/developers](https://github.com/CartoDB/developers) the tag should be used to generate the documentation instead of `master`. @csubira
2. We should replace the [guide](https://github.com/CartoDB/carto-vl/blob/master/docs/guides/01-getting-started.md) to use a dynamic variable for the version instead of a fixed value, like in [carto.js's guide](https://github.com/CartoDB/carto.js/blob/master/docs/guides/01-quickstart.md) with `%VERSION%`.
After all these changes we should release the next `0.5.0` to follow the convention of using minor for new features in `0.x`.
| 1.0 | Fix docs generation - There are some consistency issues when the generation of the documentation and in the docs.
1. In [CartoDB/developers](https://github.com/CartoDB/developers) the tag should be used to generate the documentation instead of `master`. @csubira
2. We should replace the [guide](https://github.com/CartoDB/carto-vl/blob/master/docs/guides/01-getting-started.md) to use a dynamic variable for the version instead of a fixed value, like in [carto.js's guide](https://github.com/CartoDB/carto.js/blob/master/docs/guides/01-quickstart.md) with `%VERSION%`.
After all these changes we should release the next `0.5.0` to follow the convention of using minor for new features in `0.x`.
| non_priority | fix docs generation there are some consistency issues when the generation of the documentation and in the docs in the tag should be used to generate the documentation instead of master csubira we should replace the to use a dynamic variable for the version instead of a fixed value like in with version after all these changes we should release the next to follow the convention of using minor for new features in x | 0 |
8,136 | 2,963,981,265 | IssuesEvent | 2015-07-10 14:15:36 | PropelVentures/GenericPlatform | https://api.github.com/repos/PropelVentures/GenericPlatform | closed | Check List options appear on non-checklists | Fix Applied - Test Not Working to Spec | When I toggle from Checklist to box or xlist ... the checklist options (select-all and deleteBut) still appear on screen...
these should only appear when the checklist is active (checkmarks on side) | 1.0 | Check List options appear on non-checklists - When I toggle from Checklist to box or xlist ... the checklist options (select-all and deleteBut) still appear on screen...
these should only appear when the checklist is active (checkmarks on side) | non_priority | check list options appear on non checklists when i toggle from checklist to box or xlist the checklist options select all and deletebut still appear on screen these should only appear when the checklist is active checkmarks on side | 0 |
181,484 | 14,040,226,803 | IssuesEvent | 2020-11-01 01:07:34 | nrwl/nx | https://api.github.com/repos/nrwl/nx | closed | `ng generate jest-project` adding duplicate "libs/animations/tsconfig.spec.json" to lint | community scope: testing tools status: stale type: enhancement |
`ng generate jest-project --project animations` adding duplicate "libs/animations/tsconfig.spec.json" to lint section
Note:
> deleted `karma.conf.js`, `test.ts`, and `tsconfig.spec.json` and remove the `test` target for this module from `angular.json` before running about command.
**Before**
```json
"test": {
"builder": "@angular-devkit/build-angular:karma",
"options": {
"main": "libs/animations/src/test.ts",
"tsConfig": "libs/animations/tsconfig.spec.json",
"karmaConfig": "libs/animations/karma.conf.js"
}
},
"lint": {
"builder": "@angular-devkit/build-angular:tslint",
"options": {
"tsConfig": [
"libs/animations/tsconfig.lib.json",
"libs/animations/tsconfig.spec.json"
],
"exclude": [
"**/node_modules/**"
]
}
},
```
**After**
```json
"lint": {
"builder": "@angular-devkit/build-angular:tslint",
"options": {
"tsConfig": [
"libs/animations/tsconfig.lib.json",
"libs/animations/tsconfig.spec.json",
"libs/animations/tsconfig.spec.json"
],
"exclude": [
"**/node_modules/**"
]
}
},
"test": {
"builder": "@nrwl/builders:jest",
"options": {
"jestConfig": "libs/animations/jest.config.js",
"tsConfig": "libs/animations/tsconfig.spec.json",
"setupFile": "libs/animations/src/test-setup.ts"
}
}
``` | 1.0 | `ng generate jest-project` adding duplicate "libs/animations/tsconfig.spec.json" to lint -
`ng generate jest-project --project animations` adding duplicate "libs/animations/tsconfig.spec.json" to lint section
Note:
> deleted `karma.conf.js`, `test.ts`, and `tsconfig.spec.json` and remove the `test` target for this module from `angular.json` before running about command.
**Before**
```json
"test": {
"builder": "@angular-devkit/build-angular:karma",
"options": {
"main": "libs/animations/src/test.ts",
"tsConfig": "libs/animations/tsconfig.spec.json",
"karmaConfig": "libs/animations/karma.conf.js"
}
},
"lint": {
"builder": "@angular-devkit/build-angular:tslint",
"options": {
"tsConfig": [
"libs/animations/tsconfig.lib.json",
"libs/animations/tsconfig.spec.json"
],
"exclude": [
"**/node_modules/**"
]
}
},
```
**After**
```json
"lint": {
"builder": "@angular-devkit/build-angular:tslint",
"options": {
"tsConfig": [
"libs/animations/tsconfig.lib.json",
"libs/animations/tsconfig.spec.json",
"libs/animations/tsconfig.spec.json"
],
"exclude": [
"**/node_modules/**"
]
}
},
"test": {
"builder": "@nrwl/builders:jest",
"options": {
"jestConfig": "libs/animations/jest.config.js",
"tsConfig": "libs/animations/tsconfig.spec.json",
"setupFile": "libs/animations/src/test-setup.ts"
}
}
``` | non_priority | ng generate jest project adding duplicate libs animations tsconfig spec json to lint ng generate jest project project animations adding duplicate libs animations tsconfig spec json to lint section note deleted karma conf js test ts and tsconfig spec json and remove the test target for this module from angular json before running about command before json test builder angular devkit build angular karma options main libs animations src test ts tsconfig libs animations tsconfig spec json karmaconfig libs animations karma conf js lint builder angular devkit build angular tslint options tsconfig libs animations tsconfig lib json libs animations tsconfig spec json exclude node modules after json lint builder angular devkit build angular tslint options tsconfig libs animations tsconfig lib json libs animations tsconfig spec json libs animations tsconfig spec json exclude node modules test builder nrwl builders jest options jestconfig libs animations jest config js tsconfig libs animations tsconfig spec json setupfile libs animations src test setup ts | 0 |
358,043 | 25,176,655,606 | IssuesEvent | 2022-11-11 09:51:55 | joshuan98/pe | https://api.github.com/repos/joshuan98/pe | opened | Maven link | type.DocumentationBug severity.VeryLow | Instead of simply having a link called `maven`, the group can consider writing:
"Jackson Databind 2.14.0-rc1: Link to Maven"
where clicking "Link to Maven" would bring them to the respective page instead
<!--session: 1668153141432-36232c33-860e-4bee-912b-b662843a3c54-->
<!--Version: Web v3.4.4--> | 1.0 | Maven link - Instead of simply having a link called `maven`, the group can consider writing:
"Jackson Databind 2.14.0-rc1: Link to Maven"
where clicking "Link to Maven" would bring them to the respective page instead
<!--session: 1668153141432-36232c33-860e-4bee-912b-b662843a3c54-->
<!--Version: Web v3.4.4--> | non_priority | maven link instead of simply having a link called maven the group can consider writing jackson databind link to maven where clicking link to maven would bring them to the respective page instead | 0 |
311,787 | 23,404,923,778 | IssuesEvent | 2022-08-12 11:52:04 | raycast/extensions | https://api.github.com/repos/raycast/extensions | opened | Buggy jumps when scrolling on the docs | documentation | It's only happening when scrolling slowly.
At least happening in https://developers.raycast.com/api-reference/user-interface/list
gif of the bug:
| 1.0 | Buggy jumps when scrolling on the docs - It's only happening when scrolling slowly.
At least happening in https://developers.raycast.com/api-reference/user-interface/list
gif of the bug:
| non_priority | buggy jumps when scrolling on the docs it s only happening when scrolling slowly at least happening in gif of the bug | 0 |
88,230 | 17,499,834,795 | IssuesEvent | 2021-08-10 08:03:43 | Regalis11/Barotrauma | https://api.github.com/repos/Regalis11/Barotrauma | closed | LevelResource item component deattaches much sooner than the DeattachDuration field suggests. | Bug Code | - [x] I have searched the issue tracker to check if the issue has already been reported.
**Description**
LevelResources deattach faster than expected by the DeattachDuration field.
**Steps To Reproduce**
Just time it. Mod test item included in *Additional information* field.
**Version**
Windows 0.14.6.0.
**Additional information**
Test item (just place it in the sub editor):
```
<Item name="TEST levelresource" identifier="test_levelresource" category="Material" Tags="smallitem,ore" canbepicked="true" description="" scale="0.5">
<ContainedSprite texture="Content/Items/Materials/MineralEnvironment.png" usewhenattached="true" decorativespritebehavior="HideWhenNotVisible" depth="0.55" sourcerect="512,0,86,147" origin="0.5,0.5" />
<Sprite texture="Content/Items/Materials/Minerals.png" depth="0.3" sourcerect="258,4,126,121" origin="0.5,0.5" />
<Body radius="40" width="20" density="50" />
<Holdable slots="Any,RightHand,LeftHand" msg="ItemMsgUsePlasmaCutter" handle1="0,0" pickingtime="5.0" attachable="true" reattachable="false" attachedbydefault="true" />
<LevelResource deattachduration="60" randomoffsetfromwall="0">
<Commonness commonness="0" />
<RequiredItem items="cuttingequipment" type="Equipped" />
</LevelResource>
</Item>
``` | 1.0 | LevelResource item component deattaches much sooner than the DeattachDuration field suggests. - - [x] I have searched the issue tracker to check if the issue has already been reported.
**Description**
LevelResources deattach faster than expected by the DeattachDuration field.
**Steps To Reproduce**
Just time it. Mod test item included in *Additional information* field.
**Version**
Windows 0.14.6.0.
**Additional information**
Test item (just place it in the sub editor):
```
<Item name="TEST levelresource" identifier="test_levelresource" category="Material" Tags="smallitem,ore" canbepicked="true" description="" scale="0.5">
<ContainedSprite texture="Content/Items/Materials/MineralEnvironment.png" usewhenattached="true" decorativespritebehavior="HideWhenNotVisible" depth="0.55" sourcerect="512,0,86,147" origin="0.5,0.5" />
<Sprite texture="Content/Items/Materials/Minerals.png" depth="0.3" sourcerect="258,4,126,121" origin="0.5,0.5" />
<Body radius="40" width="20" density="50" />
<Holdable slots="Any,RightHand,LeftHand" msg="ItemMsgUsePlasmaCutter" handle1="0,0" pickingtime="5.0" attachable="true" reattachable="false" attachedbydefault="true" />
<LevelResource deattachduration="60" randomoffsetfromwall="0">
<Commonness commonness="0" />
<RequiredItem items="cuttingequipment" type="Equipped" />
</LevelResource>
</Item>
``` | non_priority | levelresource item component deattaches much sooner than the deattachduration field suggests i have searched the issue tracker to check if the issue has already been reported description levelresources deattach faster than expected by the deattachduration field steps to reproduce just time it mod test item included in additional information field version windows additional information test item just place it in the sub editor | 0 |
53,822 | 13,262,355,714 | IssuesEvent | 2020-08-20 21:36:58 | icecube-trac/tix4 | https://api.github.com/repos/icecube-trac/tix4 | closed | icetray-start does not detect download failures (Trac #2144) | Migrated from Trac cvmfs defect | There are several reasons icetray start can fail to download a user-specified tarball, such as networking issues or the current host OS not matching any tarball which currently exists for the specified meta-project. Currently, this leads to a rather confusing and uninformative error:
icetray-start: line 164: /env-shell.sh: No such file or directory
(This happens because the attempt to extract the build directory name from the tarball has silently failed, leaving that variable empty.) I think that some actual error handling, such as
```text
145a146,149
> if [ ! -e `basename $TARBALL` ]; then
> echo "Failed to download $TARBALL" 1>&2
> exit 1
> fi
```
would help greatly, as the user will then see (for example):
Failed to download http://icecube:skua@convey.icecube.wisc.edu/data/user/tcarver/icerec/V05-02-00_rc0/build/icerec.candidates.V05-02-00_rc0.r159939.RHEL_7_x86_64.tar.gz
which makes it clear that either the network or the target URL should be investigated. (In this example the tarball only has a RHEL_6 version, and now the user has the information to see the OS mismatch.)
<details>
<summary><em>Migrated from <a href="https://code.icecube.wisc.edu/projects/icecube/ticket/2144">https://code.icecube.wisc.edu/projects/icecube/ticket/2144</a>, reported by cweaverand owned by david.schultz</em></summary>
<p>
```json
{
"status": "closed",
"changetime": "2019-02-13T14:15:23",
"_ts": "1550067323910946",
"description": "There are several reasons icetray start can fail to download a user-specified tarball, such as networking issues or the current host OS not matching any tarball which currently exists for the specified meta-project. Currently, this leads to a rather confusing and uninformative error:\n\n\ticetray-start: line 164: /env-shell.sh: No such file or directory\n\n(This happens because the attempt to extract the build directory name from the tarball has silently failed, leaving that variable empty.) I think that some actual error handling, such as \n\n{{{\n145a146,149\n> \t\tif [ ! -e `basename $TARBALL` ]; then\n> \t\t\techo \"Failed to download $TARBALL\" 1>&2\n> \t\t\texit 1\n> \t\tfi\n}}}\n\nwould help greatly, as the user will then see (for example):\n\n\tFailed to download http://icecube:skua@convey.icecube.wisc.edu/data/user/tcarver/icerec/V05-02-00_rc0/build/icerec.candidates.V05-02-00_rc0.r159939.RHEL_7_x86_64.tar.gz\n\nwhich makes it clear that either the network or the target URL should be investigated. (In this example the tarball only has a RHEL_6 version, and now the user has the information to see the OS mismatch.)",
"reporter": "cweaver",
"cc": "",
"resolution": "fixed",
"time": "2018-04-11T19:45:56",
"component": "cvmfs",
"summary": "icetray-start does not detect download failures",
"priority": "normal",
"keywords": "",
"milestone": "",
"owner": "david.schultz",
"type": "defect"
}
```
</p>
</details>
| 1.0 | icetray-start does not detect download failures (Trac #2144) - There are several reasons icetray start can fail to download a user-specified tarball, such as networking issues or the current host OS not matching any tarball which currently exists for the specified meta-project. Currently, this leads to a rather confusing and uninformative error:
icetray-start: line 164: /env-shell.sh: No such file or directory
(This happens because the attempt to extract the build directory name from the tarball has silently failed, leaving that variable empty.) I think that some actual error handling, such as
```text
145a146,149
> if [ ! -e `basename $TARBALL` ]; then
> echo "Failed to download $TARBALL" 1>&2
> exit 1
> fi
```
would help greatly, as the user will then see (for example):
Failed to download http://icecube:skua@convey.icecube.wisc.edu/data/user/tcarver/icerec/V05-02-00_rc0/build/icerec.candidates.V05-02-00_rc0.r159939.RHEL_7_x86_64.tar.gz
which makes it clear that either the network or the target URL should be investigated. (In this example the tarball only has a RHEL_6 version, and now the user has the information to see the OS mismatch.)
<details>
<summary><em>Migrated from <a href="https://code.icecube.wisc.edu/projects/icecube/ticket/2144">https://code.icecube.wisc.edu/projects/icecube/ticket/2144</a>, reported by cweaverand owned by david.schultz</em></summary>
<p>
```json
{
"status": "closed",
"changetime": "2019-02-13T14:15:23",
"_ts": "1550067323910946",
"description": "There are several reasons icetray start can fail to download a user-specified tarball, such as networking issues or the current host OS not matching any tarball which currently exists for the specified meta-project. Currently, this leads to a rather confusing and uninformative error:\n\n\ticetray-start: line 164: /env-shell.sh: No such file or directory\n\n(This happens because the attempt to extract the build directory name from the tarball has silently failed, leaving that variable empty.) I think that some actual error handling, such as \n\n{{{\n145a146,149\n> \t\tif [ ! -e `basename $TARBALL` ]; then\n> \t\t\techo \"Failed to download $TARBALL\" 1>&2\n> \t\t\texit 1\n> \t\tfi\n}}}\n\nwould help greatly, as the user will then see (for example):\n\n\tFailed to download http://icecube:skua@convey.icecube.wisc.edu/data/user/tcarver/icerec/V05-02-00_rc0/build/icerec.candidates.V05-02-00_rc0.r159939.RHEL_7_x86_64.tar.gz\n\nwhich makes it clear that either the network or the target URL should be investigated. (In this example the tarball only has a RHEL_6 version, and now the user has the information to see the OS mismatch.)",
"reporter": "cweaver",
"cc": "",
"resolution": "fixed",
"time": "2018-04-11T19:45:56",
"component": "cvmfs",
"summary": "icetray-start does not detect download failures",
"priority": "normal",
"keywords": "",
"milestone": "",
"owner": "david.schultz",
"type": "defect"
}
```
</p>
</details>
| non_priority | icetray start does not detect download failures trac there are several reasons icetray start can fail to download a user specified tarball such as networking issues or the current host os not matching any tarball which currently exists for the specified meta project currently this leads to a rather confusing and uninformative error icetray start line env shell sh no such file or directory this happens because the attempt to extract the build directory name from the tarball has silently failed leaving that variable empty i think that some actual error handling such as text if then echo failed to download tarball exit fi would help greatly as the user will then see for example failed to download which makes it clear that either the network or the target url should be investigated in this example the tarball only has a rhel version and now the user has the information to see the os mismatch migrated from json status closed changetime ts description there are several reasons icetray start can fail to download a user specified tarball such as networking issues or the current host os not matching any tarball which currently exists for the specified meta project currently this leads to a rather confusing and uninformative error n n ticetray start line env shell sh no such file or directory n n this happens because the attempt to extract the build directory name from the tarball has silently failed leaving that variable empty i think that some actual error handling such as n n n t tif then n t t techo failed to download tarball n t t texit n t tfi n n nwould help greatly as the user will then see for example n n tfailed to download makes it clear that either the network or the target url should be investigated in this example the tarball only has a rhel version and now the user has the information to see the os mismatch reporter cweaver cc resolution fixed time component cvmfs summary icetray start does not detect download failures priority normal keywords milestone owner david schultz type defect | 0 |
40,137 | 5,278,219,859 | IssuesEvent | 2017-02-07 07:14:35 | dotnet/cli | https://api.github.com/repos/dotnet/cli | closed | dotnet test shows exception if project.json file is wrong | bug dotnet-test fit-n-finish | ## Steps to reproduce
1. Use a project.json file that has an error in the structure (i.e. a missing comma)
2. dotnet test
## Expected behavior
When running the other dotnet commands they all show the following error message:
`After parsing a value an unexpected character was encountered: ". Path 'frameworks', line 19, position 2.`
`dotnet test` should show the same message.
## Actual behavior
dotnet-test Error: 0 : C:\Users\mariari\bugbash\src\project.json(19,2): Error: Microsoft.DotNet.ProjectModel.FileFormatException: After parsing a value an unexpected character was encountered: ". Path 'frameworks', line 19, position 2. ---> Newtonsoft.Json.JsonReaderException: After parsing a value an unexpected character was encountered: ". Path 'frameworks', line 19, position 2.
at Newtonsoft.Json.JsonTextReader.ParsePostValue()
at Newtonsoft.Json.JsonTextReader.Read()
at Newtonsoft.Json.Linq.JContainer.ReadContentFrom(JsonReader r, JsonLoadSettings settings)
at Newtonsoft.Json.Linq.JContainer.ReadTokenFrom(JsonReader reader, JsonLoadSettings options)
at Newtonsoft.Json.Linq.JObject.Load(JsonReader reader, JsonLoadSettings settings)
at Newtonsoft.Json.Linq.JObject.Load(JsonReader reader)
at Microsoft.DotNet.ProjectModel.ProjectReader.ReadProject(Stream stream, String projectName, String projectPath, ProjectReaderSettings settings)
at Microsoft.DotNet.ProjectModel.ProjectReader.TryGetProject(String path, Project& project, ProjectReaderSettings settings)
--- End of inner exception stack trace ---
at Microsoft.DotNet.ProjectModel.ProjectReader.TryGetProject(String path, Project& project, ProjectReaderSettings settings)
at Microsoft.DotNet.ProjectModel.Workspace.AddProjectEntry(String projectDirectory, FileModelEntry`1 currentEntry)
at Microsoft.DotNet.ProjectModel.Workspace.<GetProjectCore>b__11_0(String key)
at System.Collections.Concurrent.ConcurrentDictionary`2.AddOrUpdate(TKey key, Func`2 addValueFactory, Func`3 updateValueFactory)
at Microsoft.DotNet.ProjectModel.Workspace.GetProjectCore(String projectDirectory)
at Microsoft.DotNet.ProjectModel.Workspace.AddProjectContextEntry(String projectDirectory, ProjectContextCollection currentEntry)
at Microsoft.DotNet.ProjectModel.Workspace.<GetProjectContextCollection>b__8_0(String key)
at System.Collections.Concurrent.ConcurrentDictionary`2.AddOrUpdate(TKey key, Func`2 addValueFactory, Func`3 updateValueFactory)
at Microsoft.DotNet.ProjectModel.Workspace.GetProjectContextCollection(String projectPath)
at Microsoft.DotNet.Tools.Test.TestCommand.DoRun(String[] args)
## Environment data
`dotnet --info` output:
.NET Command Line Tools (1.0.0-preview2-003024)
Product Information:
Version: 1.0.0-preview2-003024
Commit SHA-1 hash: ef4a8e85ef
Runtime Environment:
OS Name: Windows
OS Version: 10.0.10586
OS Platform: Windows
RID: win10-x64
| 1.0 | dotnet test shows exception if project.json file is wrong - ## Steps to reproduce
1. Use a project.json file that has an error in the structure (i.e. a missing comma)
2. dotnet test
## Expected behavior
When running the other dotnet commands they all show the following error message:
`After parsing a value an unexpected character was encountered: ". Path 'frameworks', line 19, position 2.`
`dotnet test` should show the same message.
## Actual behavior
dotnet-test Error: 0 : C:\Users\mariari\bugbash\src\project.json(19,2): Error: Microsoft.DotNet.ProjectModel.FileFormatException: After parsing a value an unexpected character was encountered: ". Path 'frameworks', line 19, position 2. ---> Newtonsoft.Json.JsonReaderException: After parsing a value an unexpected character was encountered: ". Path 'frameworks', line 19, position 2.
at Newtonsoft.Json.JsonTextReader.ParsePostValue()
at Newtonsoft.Json.JsonTextReader.Read()
at Newtonsoft.Json.Linq.JContainer.ReadContentFrom(JsonReader r, JsonLoadSettings settings)
at Newtonsoft.Json.Linq.JContainer.ReadTokenFrom(JsonReader reader, JsonLoadSettings options)
at Newtonsoft.Json.Linq.JObject.Load(JsonReader reader, JsonLoadSettings settings)
at Newtonsoft.Json.Linq.JObject.Load(JsonReader reader)
at Microsoft.DotNet.ProjectModel.ProjectReader.ReadProject(Stream stream, String projectName, String projectPath, ProjectReaderSettings settings)
at Microsoft.DotNet.ProjectModel.ProjectReader.TryGetProject(String path, Project& project, ProjectReaderSettings settings)
--- End of inner exception stack trace ---
at Microsoft.DotNet.ProjectModel.ProjectReader.TryGetProject(String path, Project& project, ProjectReaderSettings settings)
at Microsoft.DotNet.ProjectModel.Workspace.AddProjectEntry(String projectDirectory, FileModelEntry`1 currentEntry)
at Microsoft.DotNet.ProjectModel.Workspace.<GetProjectCore>b__11_0(String key)
at System.Collections.Concurrent.ConcurrentDictionary`2.AddOrUpdate(TKey key, Func`2 addValueFactory, Func`3 updateValueFactory)
at Microsoft.DotNet.ProjectModel.Workspace.GetProjectCore(String projectDirectory)
at Microsoft.DotNet.ProjectModel.Workspace.AddProjectContextEntry(String projectDirectory, ProjectContextCollection currentEntry)
at Microsoft.DotNet.ProjectModel.Workspace.<GetProjectContextCollection>b__8_0(String key)
at System.Collections.Concurrent.ConcurrentDictionary`2.AddOrUpdate(TKey key, Func`2 addValueFactory, Func`3 updateValueFactory)
at Microsoft.DotNet.ProjectModel.Workspace.GetProjectContextCollection(String projectPath)
at Microsoft.DotNet.Tools.Test.TestCommand.DoRun(String[] args)
## Environment data
`dotnet --info` output:
.NET Command Line Tools (1.0.0-preview2-003024)
Product Information:
Version: 1.0.0-preview2-003024
Commit SHA-1 hash: ef4a8e85ef
Runtime Environment:
OS Name: Windows
OS Version: 10.0.10586
OS Platform: Windows
RID: win10-x64
| non_priority | dotnet test shows exception if project json file is wrong steps to reproduce use a project json file that has an error in the structure i e a missing comma dotnet test expected behavior when running the other dotnet commands they all show the following error message after parsing a value an unexpected character was encountered path frameworks line position dotnet test should show the same message actual behavior dotnet test error c users mariari bugbash src project json error microsoft dotnet projectmodel fileformatexception after parsing a value an unexpected character was encountered path frameworks line position newtonsoft json jsonreaderexception after parsing a value an unexpected character was encountered path frameworks line position at newtonsoft json jsontextreader parsepostvalue at newtonsoft json jsontextreader read at newtonsoft json linq jcontainer readcontentfrom jsonreader r jsonloadsettings settings at newtonsoft json linq jcontainer readtokenfrom jsonreader reader jsonloadsettings options at newtonsoft json linq jobject load jsonreader reader jsonloadsettings settings at newtonsoft json linq jobject load jsonreader reader at microsoft dotnet projectmodel projectreader readproject stream stream string projectname string projectpath projectreadersettings settings at microsoft dotnet projectmodel projectreader trygetproject string path project project projectreadersettings settings end of inner exception stack trace at microsoft dotnet projectmodel projectreader trygetproject string path project project projectreadersettings settings at microsoft dotnet projectmodel workspace addprojectentry string projectdirectory filemodelentry currententry at microsoft dotnet projectmodel workspace b string key at system collections concurrent concurrentdictionary addorupdate tkey key func addvaluefactory func updatevaluefactory at microsoft dotnet projectmodel workspace getprojectcore string projectdirectory at microsoft dotnet projectmodel workspace addprojectcontextentry string projectdirectory projectcontextcollection currententry at microsoft dotnet projectmodel workspace b string key at system collections concurrent concurrentdictionary addorupdate tkey key func addvaluefactory func updatevaluefactory at microsoft dotnet projectmodel workspace getprojectcontextcollection string projectpath at microsoft dotnet tools test testcommand dorun string args environment data dotnet info output net command line tools product information version commit sha hash runtime environment os name windows os version os platform windows rid | 0 |
204 | 2,729,396,866 | IssuesEvent | 2015-04-16 08:16:01 | folklabs/hernehill.org.uk | https://api.github.com/repos/folklabs/hernehill.org.uk | closed | Tag filters on services listing - not alphabetical | f-services | The tags for the filters on the servcies listings are a bit juimbled, no idea how you would find what you wanted.
If we get more tags is there a merit of having a text search or predictive dropdown? | 1.0 | Tag filters on services listing - not alphabetical - The tags for the filters on the servcies listings are a bit juimbled, no idea how you would find what you wanted.
If we get more tags is there a merit of having a text search or predictive dropdown? | non_priority | tag filters on services listing not alphabetical the tags for the filters on the servcies listings are a bit juimbled no idea how you would find what you wanted if we get more tags is there a merit of having a text search or predictive dropdown | 0 |
13,243 | 22,353,191,950 | IssuesEvent | 2022-06-15 13:43:26 | naomikorem/MarketSystem | https://api.github.com/repos/naomikorem/MarketSystem | closed | Encrypt passwords that the client send to the server | implement requirement client_relates | The passwords that sent to the server should be encrypted. | 1.0 | Encrypt passwords that the client send to the server - The passwords that sent to the server should be encrypted. | non_priority | encrypt passwords that the client send to the server the passwords that sent to the server should be encrypted | 0 |
33,076 | 12,168,526,115 | IssuesEvent | 2020-04-27 12:49:57 | elikkatzgit/20.2.1 | https://api.github.com/repos/elikkatzgit/20.2.1 | opened | WS-2019-0332 (Medium) detected in handlebars-4.5.1.tgz | security vulnerability | ## WS-2019-0332 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>handlebars-4.5.1.tgz</b></p></summary>
<p>Handlebars provides the power necessary to let you build semantic templates effectively with no frustration</p>
<p>Library home page: <a href="https://registry.npmjs.org/handlebars/-/handlebars-4.5.1.tgz">https://registry.npmjs.org/handlebars/-/handlebars-4.5.1.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/20.2.1/package.json</p>
<p>Path to vulnerable library: /20.2.1/node_modules/handlebars/package.json,/20.2.1/node_modules/handlebars/package.json</p>
<p>
Dependency Hierarchy:
- :x: **handlebars-4.5.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/elikkatzgit/20.2.1/commit/d938556f9ce6bddab541a23d889df6d1bb1fe8a9">d938556f9ce6bddab541a23d889df6d1bb1fe8a9</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Arbitrary Code Execution vulnerability found in handlebars before 4.5.3. Lookup helper fails to validate templates. Attack may submit templates that execute arbitrary JavaScript in the system.It is due to an incomplete fix for a WS-2019-0331.
<p>Publish Date: 2019-12-05
<p>URL: <a href=https://github.com/wycats/handlebars.js/commit/198887808780bbef9dba67a8af68ece091d5baa7>WS-2019-0332</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/1324">https://www.npmjs.com/advisories/1324</a></p>
<p>Release Date: 2019-12-05</p>
<p>Fix Resolution: handlebars - 4.5.3</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"handlebars","packageVersion":"4.5.1","isTransitiveDependency":false,"dependencyTree":"handlebars:4.5.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"handlebars - 4.5.3"}],"vulnerabilityIdentifier":"WS-2019-0332","vulnerabilityDetails":"Arbitrary Code Execution vulnerability found in handlebars before 4.5.3. Lookup helper fails to validate templates. Attack may submit templates that execute arbitrary JavaScript in the system.It is due to an incomplete fix for a WS-2019-0331.","vulnerabilityUrl":"https://github.com/wycats/handlebars.js/commit/198887808780bbef9dba67a8af68ece091d5baa7","cvss2Severity":"medium","cvss2Score":"5.0","extraData":{}}</REMEDIATE> --> | True | WS-2019-0332 (Medium) detected in handlebars-4.5.1.tgz - ## WS-2019-0332 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>handlebars-4.5.1.tgz</b></p></summary>
<p>Handlebars provides the power necessary to let you build semantic templates effectively with no frustration</p>
<p>Library home page: <a href="https://registry.npmjs.org/handlebars/-/handlebars-4.5.1.tgz">https://registry.npmjs.org/handlebars/-/handlebars-4.5.1.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/20.2.1/package.json</p>
<p>Path to vulnerable library: /20.2.1/node_modules/handlebars/package.json,/20.2.1/node_modules/handlebars/package.json</p>
<p>
Dependency Hierarchy:
- :x: **handlebars-4.5.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/elikkatzgit/20.2.1/commit/d938556f9ce6bddab541a23d889df6d1bb1fe8a9">d938556f9ce6bddab541a23d889df6d1bb1fe8a9</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Arbitrary Code Execution vulnerability found in handlebars before 4.5.3. Lookup helper fails to validate templates. Attack may submit templates that execute arbitrary JavaScript in the system.It is due to an incomplete fix for a WS-2019-0331.
<p>Publish Date: 2019-12-05
<p>URL: <a href=https://github.com/wycats/handlebars.js/commit/198887808780bbef9dba67a8af68ece091d5baa7>WS-2019-0332</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/1324">https://www.npmjs.com/advisories/1324</a></p>
<p>Release Date: 2019-12-05</p>
<p>Fix Resolution: handlebars - 4.5.3</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"handlebars","packageVersion":"4.5.1","isTransitiveDependency":false,"dependencyTree":"handlebars:4.5.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"handlebars - 4.5.3"}],"vulnerabilityIdentifier":"WS-2019-0332","vulnerabilityDetails":"Arbitrary Code Execution vulnerability found in handlebars before 4.5.3. Lookup helper fails to validate templates. Attack may submit templates that execute arbitrary JavaScript in the system.It is due to an incomplete fix for a WS-2019-0331.","vulnerabilityUrl":"https://github.com/wycats/handlebars.js/commit/198887808780bbef9dba67a8af68ece091d5baa7","cvss2Severity":"medium","cvss2Score":"5.0","extraData":{}}</REMEDIATE> --> | non_priority | ws medium detected in handlebars tgz ws medium severity vulnerability vulnerable library handlebars tgz handlebars provides the power necessary to let you build semantic templates effectively with no frustration library home page a href path to dependency file tmp ws scm package json path to vulnerable library node modules handlebars package json node modules handlebars package json dependency hierarchy x handlebars tgz vulnerable library found in head commit a href vulnerability details arbitrary code execution vulnerability found in handlebars before lookup helper fails to validate templates attack may submit templates that execute arbitrary javascript in the system it is due to an incomplete fix for a ws publish date url a href cvss score details base score metrics not available suggested fix type upgrade version origin a href release date fix resolution handlebars check this box to open an automated fix pr isopenpronvulnerability false ispackagebased true isdefaultbranch true packages vulnerabilityidentifier ws vulnerabilitydetails arbitrary code execution vulnerability found in handlebars before lookup helper fails to validate templates attack may submit templates that execute arbitrary javascript in the system it is due to an incomplete fix for a ws vulnerabilityurl | 0 |
236,461 | 18,098,297,089 | IssuesEvent | 2021-09-22 11:36:32 | protocolbuffers/protobuf | https://api.github.com/repos/protocolbuffers/protobuf | closed | The behavior of default proto_path will use include directory, Can I use? | question documentation | I find protoc default add the path of protoc's localtion `include` directory which contains `/google/protobuf/descriptor.proto` file when compiling the proto file, I get the source code as follow, but I can not find any description this feature in document, Can I use this feature as formal, Would it remove in future version without notify?
```c++
https://github.com/protocolbuffers/protobuf/blob/master/src/google/protobuf/compiler/command_line_interface.cc
void AddDefaultProtoPaths(
std::vector<std::pair<std::string, std::string> >* paths) {
// TODO(xiaofeng): The code currently only checks relative paths of where
// the protoc binary is installed. We probably should make it handle more
// cases than that.
std::string path;
if (!GetProtocAbsolutePath(&path)) {
return;
}
// Strip the binary name.
size_t pos = path.find_last_of("/\\");
if (pos == std::string::npos || pos == 0) {
return;
}
path = path.substr(0, pos);
// Check the binary's directory.
if (IsInstalledProtoPath(path)) {
paths->push_back(std::pair<std::string, std::string>("", path));
return;
}
// Check if there is an include subdirectory.
if (IsInstalledProtoPath(path + "/include")) {
paths->push_back(
std::pair<std::string, std::string>("", path + "/include"));
return;
}
// Check if the upper level directory has an "include" subdirectory.
pos = path.find_last_of("/\\");
if (pos == std::string::npos || pos == 0) {
return;
}
path = path.substr(0, pos);
if (IsInstalledProtoPath(path + "/include")) {
paths->push_back(
std::pair<std::string, std::string>("", path + "/include"));
return;
}
}
```
| 1.0 | The behavior of default proto_path will use include directory, Can I use? - I find protoc default add the path of protoc's localtion `include` directory which contains `/google/protobuf/descriptor.proto` file when compiling the proto file, I get the source code as follow, but I can not find any description this feature in document, Can I use this feature as formal, Would it remove in future version without notify?
```c++
https://github.com/protocolbuffers/protobuf/blob/master/src/google/protobuf/compiler/command_line_interface.cc
void AddDefaultProtoPaths(
std::vector<std::pair<std::string, std::string> >* paths) {
// TODO(xiaofeng): The code currently only checks relative paths of where
// the protoc binary is installed. We probably should make it handle more
// cases than that.
std::string path;
if (!GetProtocAbsolutePath(&path)) {
return;
}
// Strip the binary name.
size_t pos = path.find_last_of("/\\");
if (pos == std::string::npos || pos == 0) {
return;
}
path = path.substr(0, pos);
// Check the binary's directory.
if (IsInstalledProtoPath(path)) {
paths->push_back(std::pair<std::string, std::string>("", path));
return;
}
// Check if there is an include subdirectory.
if (IsInstalledProtoPath(path + "/include")) {
paths->push_back(
std::pair<std::string, std::string>("", path + "/include"));
return;
}
// Check if the upper level directory has an "include" subdirectory.
pos = path.find_last_of("/\\");
if (pos == std::string::npos || pos == 0) {
return;
}
path = path.substr(0, pos);
if (IsInstalledProtoPath(path + "/include")) {
paths->push_back(
std::pair<std::string, std::string>("", path + "/include"));
return;
}
}
```
| non_priority | the behavior of default proto path will use include directory can i use i find protoc default add the path of protoc s localtion include directory which contains google protobuf descriptor proto file when compiling the proto file i get the source code as follow but i can not find any description this feature in document can i use this feature as formal would it remove in future version without notify c void adddefaultprotopaths std vector paths todo xiaofeng the code currently only checks relative paths of where the protoc binary is installed we probably should make it handle more cases than that std string path if getprotocabsolutepath path return strip the binary name size t pos path find last of if pos std string npos pos return path path substr pos check the binary s directory if isinstalledprotopath path paths push back std pair path return check if there is an include subdirectory if isinstalledprotopath path include paths push back std pair path include return check if the upper level directory has an include subdirectory pos path find last of if pos std string npos pos return path path substr pos if isinstalledprotopath path include paths push back std pair path include return | 0 |
399,037 | 27,222,619,279 | IssuesEvent | 2023-02-21 07:10:06 | asdf-vm/asdf | https://api.github.com/repos/asdf-vm/asdf | closed | How do I remove ASDF | documentation | ### How can we improve the documentation?
Just as bad as the pyenv docs: `ASDF` worms its way into pretty much everything, where is the documentation to remove it?
Or should I just nuke my OS now? | 1.0 | How do I remove ASDF - ### How can we improve the documentation?
Just as bad as the pyenv docs: `ASDF` worms its way into pretty much everything, where is the documentation to remove it?
Or should I just nuke my OS now? | non_priority | how do i remove asdf how can we improve the documentation just as bad as the pyenv docs asdf worms its way into pretty much everything where is the documentation to remove it or should i just nuke my os now | 0 |
18,781 | 11,048,613,826 | IssuesEvent | 2019-12-09 21:32:45 | terraform-providers/terraform-provider-aws | https://api.github.com/repos/terraform-providers/terraform-provider-aws | closed | IAM instance roles not available for cloud-init | needs-triage service/ec2 service/iam | ### Terraform Version
<!--- Please run `terraform -v` to show the Terraform core version and provider version(s). If you are not running the latest version of Terraform or the provider, please upgrade because your issue may have already been fixed. [Terraform documentation on provider versioning](https://www.terraform.io/docs/configuration/providers.html#provider-versions). --->
$ terraform -v
Terraform v0.11.11
+ provider.aws v2.1.0 (or 2.2.0)
+ provider.template v1.0.0
+ provider.tls v1.2.0
### Affected Resource(s)
<!--- Please list the affected resources and data sources. --->
* aws_instance
* aws_iam_role
### Terraform Configuration Files
<!--- Information about code formatting: https://help.github.com/articles/basic-writing-and-formatting-syntax/#quoting-code --->
https://registry.terraform.io/modules/trajano/swarm-aws/docker/2.3.2
Just changed from AWS 2.1 to AWS 2.2 in the samples and the instance credentials do not appear to be present during cloud init but works when you run the same script inside and `curl`ing the meta data shows the instance ID. So it appears to be a timing issue because it works with a `t3.micro` but not a `t3.small` which is a slightly faster machine.
```hcl
# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key: https://keybase.io/hashicorp
```
### Debug Output
<!---
Please provide a link to a GitHub Gist containing the complete debug output. Please do NOT paste the debug output in the issue; just paste a link to the Gist.
To obtain the debug output, see the [Terraform documentation on debugging](https://www.terraform.io/docs/internals/debugging.html).
--->
### Panic Output
<!--- If Terraform produced a panic, please provide a link to a GitHub Gist containing the output of the `crash.log`. --->
### Expected Behavior
Everything should be provisioned correctly.
### Actual Behavior
I get an error saying missing credentials when invoking boto3 in cloud-init
### Steps to Reproduce
<!--- Please list the steps required to reproduce the issue. --->
1. `terraform apply`
### Important Factoids
<!--- Are there anything atypical about your accounts that we should know? For example: Running in EC2 Classic? --->
### References
<!---
Information about referencing Github Issues: https://help.github.com/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests
Are there any other GitHub issues (open or closed) or pull requests that should be linked here? Vendor documentation? For example:
--->
* #0000
| 2.0 | IAM instance roles not available for cloud-init - ### Terraform Version
<!--- Please run `terraform -v` to show the Terraform core version and provider version(s). If you are not running the latest version of Terraform or the provider, please upgrade because your issue may have already been fixed. [Terraform documentation on provider versioning](https://www.terraform.io/docs/configuration/providers.html#provider-versions). --->
$ terraform -v
Terraform v0.11.11
+ provider.aws v2.1.0 (or 2.2.0)
+ provider.template v1.0.0
+ provider.tls v1.2.0
### Affected Resource(s)
<!--- Please list the affected resources and data sources. --->
* aws_instance
* aws_iam_role
### Terraform Configuration Files
<!--- Information about code formatting: https://help.github.com/articles/basic-writing-and-formatting-syntax/#quoting-code --->
https://registry.terraform.io/modules/trajano/swarm-aws/docker/2.3.2
Just changed from AWS 2.1 to AWS 2.2 in the samples and the instance credentials do not appear to be present during cloud init but works when you run the same script inside and `curl`ing the meta data shows the instance ID. So it appears to be a timing issue because it works with a `t3.micro` but not a `t3.small` which is a slightly faster machine.
```hcl
# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key: https://keybase.io/hashicorp
```
### Debug Output
<!---
Please provide a link to a GitHub Gist containing the complete debug output. Please do NOT paste the debug output in the issue; just paste a link to the Gist.
To obtain the debug output, see the [Terraform documentation on debugging](https://www.terraform.io/docs/internals/debugging.html).
--->
### Panic Output
<!--- If Terraform produced a panic, please provide a link to a GitHub Gist containing the output of the `crash.log`. --->
### Expected Behavior
Everything should be provisioned correctly.
### Actual Behavior
I get an error saying missing credentials when invoking boto3 in cloud-init
### Steps to Reproduce
<!--- Please list the steps required to reproduce the issue. --->
1. `terraform apply`
### Important Factoids
<!--- Are there anything atypical about your accounts that we should know? For example: Running in EC2 Classic? --->
### References
<!---
Information about referencing Github Issues: https://help.github.com/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests
Are there any other GitHub issues (open or closed) or pull requests that should be linked here? Vendor documentation? For example:
--->
* #0000
| non_priority | iam instance roles not available for cloud init terraform version terraform v terraform provider aws or provider template provider tls affected resource s aws instance aws iam role terraform configuration files just changed from aws to aws in the samples and the instance credentials do not appear to be present during cloud init but works when you run the same script inside and curl ing the meta data shows the instance id so it appears to be a timing issue because it works with a micro but not a small which is a slightly faster machine hcl copy paste your terraform configurations here for large terraform configs please use a service like dropbox and share a link to the zip file for security you can also encrypt the files using our gpg public key debug output please provide a link to a github gist containing the complete debug output please do not paste the debug output in the issue just paste a link to the gist to obtain the debug output see the panic output expected behavior everything should be provisioned correctly actual behavior i get an error saying missing credentials when invoking in cloud init steps to reproduce terraform apply important factoids references information about referencing github issues are there any other github issues open or closed or pull requests that should be linked here vendor documentation for example | 0 |
181,769 | 14,888,197,137 | IssuesEvent | 2021-01-20 19:28:56 | hashicorp/terraform-provider-aws | https://api.github.com/repos/hashicorp/terraform-provider-aws | closed | Documentation : block-devices link is broken on aws_instance resource page | bug documentation service/ec2 | <!---
Please note the following potential times when an issue might be in Terraform core:
* [Configuration Language](https://www.terraform.io/docs/configuration/index.html) or resource ordering issues
* [State](https://www.terraform.io/docs/state/index.html) and [State Backend](https://www.terraform.io/docs/backends/index.html) issues
* [Provisioner](https://www.terraform.io/docs/provisioners/index.html) issues
* [Registry](https://registry.terraform.io/) issues
* Spans resources across multiple providers
If you are running into one of these scenarios, we recommend opening an issue in the [Terraform core repository](https://github.com/hashicorp/terraform/) instead.
--->
<!--- Please keep this note for the community --->
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
<!--- Thank you for keeping this note for the community --->
The internal markdown link referencing block-devices is broken on the [aws_instance page](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/instance)
For eg:
> * `ephemeral_block_device` - (Optional) Customize Ephemeral (also known as "Instance Store") volumes on the instance. See [Block Devices](#block-devices) below for details.
### Affected Resource(s)
<!--- Please list the affected resources and data sources. --->
* aws_instance
### References
<!---
Information about referencing Github Issues: https://help.github.com/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests
Are there any other GitHub issues (open or closed) or pull requests that should be linked here? Vendor documentation? For example:
--->
* NA
| 1.0 | Documentation : block-devices link is broken on aws_instance resource page - <!---
Please note the following potential times when an issue might be in Terraform core:
* [Configuration Language](https://www.terraform.io/docs/configuration/index.html) or resource ordering issues
* [State](https://www.terraform.io/docs/state/index.html) and [State Backend](https://www.terraform.io/docs/backends/index.html) issues
* [Provisioner](https://www.terraform.io/docs/provisioners/index.html) issues
* [Registry](https://registry.terraform.io/) issues
* Spans resources across multiple providers
If you are running into one of these scenarios, we recommend opening an issue in the [Terraform core repository](https://github.com/hashicorp/terraform/) instead.
--->
<!--- Please keep this note for the community --->
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
<!--- Thank you for keeping this note for the community --->
The internal markdown link referencing block-devices is broken on the [aws_instance page](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/instance)
For eg:
> * `ephemeral_block_device` - (Optional) Customize Ephemeral (also known as "Instance Store") volumes on the instance. See [Block Devices](#block-devices) below for details.
### Affected Resource(s)
<!--- Please list the affected resources and data sources. --->
* aws_instance
### References
<!---
Information about referencing Github Issues: https://help.github.com/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests
Are there any other GitHub issues (open or closed) or pull requests that should be linked here? Vendor documentation? For example:
--->
* NA
| non_priority | documentation block devices link is broken on aws instance resource page please note the following potential times when an issue might be in terraform core or resource ordering issues and issues issues issues spans resources across multiple providers if you are running into one of these scenarios we recommend opening an issue in the instead community note please vote on this issue by adding a 👍 to the original issue to help the community and maintainers prioritize this request please do not leave or other comments that do not add relevant new information or questions they generate extra noise for issue followers and do not help prioritize the request if you are interested in working on this issue or have submitted a pull request please leave a comment the internal markdown link referencing block devices is broken on the for eg ephemeral block device optional customize ephemeral also known as instance store volumes on the instance see block devices below for details affected resource s aws instance references information about referencing github issues are there any other github issues open or closed or pull requests that should be linked here vendor documentation for example na | 0 |
271,451 | 29,502,813,690 | IssuesEvent | 2023-06-03 01:08:45 | jgeraigery/venice | https://api.github.com/repos/jgeraigery/venice | opened | github-pages-219.gem: 5 vulnerabilities (highest severity is: 8.8) | Mend: dependency security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>github-pages-219.gem</b></p></summary>
<p></p>
<p>Path to dependency file: /docs/Gemfile.lock</p>
<p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/commonmarker-0.17.13.gem</p>
<p>
</details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (github-pages version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [WS-2022-0093](https://github.com/gjtorikian/commonmarker/commit/ab4504fd17460627a6ab255bc3c63e8e5fc6aed3) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.8 | commonmarker-0.17.13.gem | Transitive | N/A* | ❌ |
| [WS-2022-0320](https://github.com/gjtorikian/commonmarker/commit/a8f8d76fbc8c92ddb2e539a06bd93c5f8326705e) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | commonmarker-0.17.13.gem | Transitive | N/A* | ❌ |
| [CVE-2023-26485](https://www.mend.io/vulnerability-database/CVE-2023-26485) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | commonmarker-0.17.13.gem | Transitive | N/A* | ❌ |
| [CVE-2023-24824](https://www.mend.io/vulnerability-database/CVE-2023-24824) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | commonmarker-0.17.13.gem | Transitive | N/A* | ❌ |
| [WS-2023-0095](https://github.com/gjtorikian/commonmarker/commit/42cfc90251353f9fceda91b884d0ded8d3da0bcf) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | commonmarker-0.17.13.gem | Transitive | N/A* | ❌ |
<p>*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.</p>
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> WS-2022-0093</summary>
### Vulnerable Library - <b>commonmarker-0.17.13.gem</b></p>
<p>A fast, safe, extensible parser for CommonMark. This wraps the official libcmark library.</p>
<p>Library home page: <a href="https://rubygems.org/gems/commonmarker-0.17.13.gem">https://rubygems.org/gems/commonmarker-0.17.13.gem</a></p>
<p>Path to dependency file: /docs/Gemfile.lock</p>
<p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/commonmarker-0.17.13.gem</p>
<p>
Dependency Hierarchy:
- github-pages-219.gem (Root Library)
- jekyll-commonmark-ghpages-0.1.6.gem
- :x: **commonmarker-0.17.13.gem** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
commonmarker versions prior to 0.23.4 are vulnerable to heap memory corruption when parsing tables whose marker rows contain more than UINT16_MAX columns.
The impact of this heap corruption ranges from Information Leak to Arbitrary Code Execution.
<p>Publish Date: 2022-02-03
<p>URL: <a href=https://github.com/gjtorikian/commonmarker/commit/ab4504fd17460627a6ab255bc3c63e8e5fc6aed3>WS-2022-0093</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-fmx4-26r3-wxpf">https://github.com/advisories/GHSA-fmx4-26r3-wxpf</a></p>
<p>Release Date: 2022-02-03</p>
<p>Fix Resolution: commonmarker - 0.23.4</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> WS-2022-0320</summary>
### Vulnerable Library - <b>commonmarker-0.17.13.gem</b></p>
<p>A fast, safe, extensible parser for CommonMark. This wraps the official libcmark library.</p>
<p>Library home page: <a href="https://rubygems.org/gems/commonmarker-0.17.13.gem">https://rubygems.org/gems/commonmarker-0.17.13.gem</a></p>
<p>Path to dependency file: /docs/Gemfile.lock</p>
<p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/commonmarker-0.17.13.gem</p>
<p>
Dependency Hierarchy:
- github-pages-219.gem (Root Library)
- jekyll-commonmark-ghpages-0.1.6.gem
- :x: **commonmarker-0.17.13.gem** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Unbounded resource exhaustion in cmark-gfm autolink extension may lead to denial of service
<p>Publish Date: 2022-09-21
<p>URL: <a href=https://github.com/gjtorikian/commonmarker/commit/a8f8d76fbc8c92ddb2e539a06bd93c5f8326705e>WS-2022-0320</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-4qw4-jpp4-8gvp">https://github.com/advisories/GHSA-4qw4-jpp4-8gvp</a></p>
<p>Release Date: 2022-09-21</p>
<p>Fix Resolution: commonmarker - 0.23.6</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2023-26485</summary>
### Vulnerable Library - <b>commonmarker-0.17.13.gem</b></p>
<p>A fast, safe, extensible parser for CommonMark. This wraps the official libcmark library.</p>
<p>Library home page: <a href="https://rubygems.org/gems/commonmarker-0.17.13.gem">https://rubygems.org/gems/commonmarker-0.17.13.gem</a></p>
<p>Path to dependency file: /docs/Gemfile.lock</p>
<p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/commonmarker-0.17.13.gem</p>
<p>
Dependency Hierarchy:
- github-pages-219.gem (Root Library)
- jekyll-commonmark-ghpages-0.1.6.gem
- :x: **commonmarker-0.17.13.gem** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
cmark-gfm is GitHub's fork of cmark, a CommonMark parsing and rendering library and program in C. A polynomial time complexity issue in cmark-gfm may lead to unbounded resource exhaustion and subsequent denial of service. This CVE covers quadratic complexity issues when parsing text which leads with either large numbers of `_` characters. This issue has been addressed in version 0.29.0.gfm.10. Users are advised to upgrade. Users unable to upgrade should validate that their input comes from trusted sources. ### Impact A polynomial time complexity issue in cmark-gfm may lead to unbounded resource exhaustion and subsequent denial of service. ### Proof of concept ``` $ ~/cmark-gfm$ python3 -c 'pad = "_" * 100000; print(pad + "." + pad, end="")' | time ./build/src/cmark-gfm --to plaintext ``` Increasing the number 10000 in the above commands causes the running time to increase quadratically. ### Patches This vulnerability have been patched in 0.29.0.gfm.10. ### Note on cmark and cmark-gfm XXX: TBD [cmark-gfm](https://github.com/github/cmark-gfm) is a fork of [cmark](https://github.com/commonmark/cmark) that adds the GitHub Flavored Markdown extensions. The two codebases have diverged over time, but share a common core. These bugs affect both `cmark` and `cmark-gfm`. ### Credit We would like to thank @gravypod for reporting this vulnerability. ### References https://en.wikipedia.org/wiki/Time_complexity ### For more information If you have any questions or comments about this advisory: * Open an issue in [github/cmark-gfm](https://github.com/github/cmark-gfm)
<p>Publish Date: 2023-03-31
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-26485>CVE-2023-26485</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-48wp-p9qv-4j64">https://github.com/advisories/GHSA-48wp-p9qv-4j64</a></p>
<p>Release Date: 2023-03-31</p>
<p>Fix Resolution: commonmarker - 0.23.9</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2023-24824</summary>
### Vulnerable Library - <b>commonmarker-0.17.13.gem</b></p>
<p>A fast, safe, extensible parser for CommonMark. This wraps the official libcmark library.</p>
<p>Library home page: <a href="https://rubygems.org/gems/commonmarker-0.17.13.gem">https://rubygems.org/gems/commonmarker-0.17.13.gem</a></p>
<p>Path to dependency file: /docs/Gemfile.lock</p>
<p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/commonmarker-0.17.13.gem</p>
<p>
Dependency Hierarchy:
- github-pages-219.gem (Root Library)
- jekyll-commonmark-ghpages-0.1.6.gem
- :x: **commonmarker-0.17.13.gem** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
cmark-gfm is GitHub's fork of cmark, a CommonMark parsing and rendering library and program in C. A polynomial time complexity issue in cmark-gfm may lead to unbounded resource exhaustion and subsequent denial of service. This CVE covers quadratic complexity issues when parsing text which leads with either large numbers of `>` or `-` characters. This issue has been addressed in version 0.29.0.gfm.10. Users are advised to upgrade. Users unable to upgrade should validate that their input comes from trusted sources.
<p>Publish Date: 2023-03-31
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-24824>CVE-2023-24824</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-48wp-p9qv-4j64">https://github.com/advisories/GHSA-48wp-p9qv-4j64</a></p>
<p>Release Date: 2023-03-31</p>
<p>Fix Resolution: commonmarker - 0.23.9</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> WS-2023-0095</summary>
### Vulnerable Library - <b>commonmarker-0.17.13.gem</b></p>
<p>A fast, safe, extensible parser for CommonMark. This wraps the official libcmark library.</p>
<p>Library home page: <a href="https://rubygems.org/gems/commonmarker-0.17.13.gem">https://rubygems.org/gems/commonmarker-0.17.13.gem</a></p>
<p>Path to dependency file: /docs/Gemfile.lock</p>
<p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/commonmarker-0.17.13.gem</p>
<p>
Dependency Hierarchy:
- github-pages-219.gem (Root Library)
- jekyll-commonmark-ghpages-0.1.6.gem
- :x: **commonmarker-0.17.13.gem** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Commonmarker vulnerable to to several quadratic complexity bugs that may lead to denial of service
<p>Publish Date: 2023-04-12
<p>URL: <a href=https://github.com/gjtorikian/commonmarker/commit/42cfc90251353f9fceda91b884d0ded8d3da0bcf>WS-2023-0095</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-48wp-p9qv-4j64">https://github.com/advisories/GHSA-48wp-p9qv-4j64</a></p>
<p>Release Date: 2023-04-12</p>
<p>Fix Resolution: commonmarker - 0.23.9</p>
</p>
<p></p>
</details> | True | github-pages-219.gem: 5 vulnerabilities (highest severity is: 8.8) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>github-pages-219.gem</b></p></summary>
<p></p>
<p>Path to dependency file: /docs/Gemfile.lock</p>
<p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/commonmarker-0.17.13.gem</p>
<p>
</details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (github-pages version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [WS-2022-0093](https://github.com/gjtorikian/commonmarker/commit/ab4504fd17460627a6ab255bc3c63e8e5fc6aed3) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.8 | commonmarker-0.17.13.gem | Transitive | N/A* | ❌ |
| [WS-2022-0320](https://github.com/gjtorikian/commonmarker/commit/a8f8d76fbc8c92ddb2e539a06bd93c5f8326705e) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | commonmarker-0.17.13.gem | Transitive | N/A* | ❌ |
| [CVE-2023-26485](https://www.mend.io/vulnerability-database/CVE-2023-26485) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | commonmarker-0.17.13.gem | Transitive | N/A* | ❌ |
| [CVE-2023-24824](https://www.mend.io/vulnerability-database/CVE-2023-24824) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | commonmarker-0.17.13.gem | Transitive | N/A* | ❌ |
| [WS-2023-0095](https://github.com/gjtorikian/commonmarker/commit/42cfc90251353f9fceda91b884d0ded8d3da0bcf) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | commonmarker-0.17.13.gem | Transitive | N/A* | ❌ |
<p>*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.</p>
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> WS-2022-0093</summary>
### Vulnerable Library - <b>commonmarker-0.17.13.gem</b></p>
<p>A fast, safe, extensible parser for CommonMark. This wraps the official libcmark library.</p>
<p>Library home page: <a href="https://rubygems.org/gems/commonmarker-0.17.13.gem">https://rubygems.org/gems/commonmarker-0.17.13.gem</a></p>
<p>Path to dependency file: /docs/Gemfile.lock</p>
<p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/commonmarker-0.17.13.gem</p>
<p>
Dependency Hierarchy:
- github-pages-219.gem (Root Library)
- jekyll-commonmark-ghpages-0.1.6.gem
- :x: **commonmarker-0.17.13.gem** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
commonmarker versions prior to 0.23.4 are vulnerable to heap memory corruption when parsing tables whose marker rows contain more than UINT16_MAX columns.
The impact of this heap corruption ranges from Information Leak to Arbitrary Code Execution.
<p>Publish Date: 2022-02-03
<p>URL: <a href=https://github.com/gjtorikian/commonmarker/commit/ab4504fd17460627a6ab255bc3c63e8e5fc6aed3>WS-2022-0093</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-fmx4-26r3-wxpf">https://github.com/advisories/GHSA-fmx4-26r3-wxpf</a></p>
<p>Release Date: 2022-02-03</p>
<p>Fix Resolution: commonmarker - 0.23.4</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> WS-2022-0320</summary>
### Vulnerable Library - <b>commonmarker-0.17.13.gem</b></p>
<p>A fast, safe, extensible parser for CommonMark. This wraps the official libcmark library.</p>
<p>Library home page: <a href="https://rubygems.org/gems/commonmarker-0.17.13.gem">https://rubygems.org/gems/commonmarker-0.17.13.gem</a></p>
<p>Path to dependency file: /docs/Gemfile.lock</p>
<p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/commonmarker-0.17.13.gem</p>
<p>
Dependency Hierarchy:
- github-pages-219.gem (Root Library)
- jekyll-commonmark-ghpages-0.1.6.gem
- :x: **commonmarker-0.17.13.gem** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Unbounded resource exhaustion in cmark-gfm autolink extension may lead to denial of service
<p>Publish Date: 2022-09-21
<p>URL: <a href=https://github.com/gjtorikian/commonmarker/commit/a8f8d76fbc8c92ddb2e539a06bd93c5f8326705e>WS-2022-0320</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-4qw4-jpp4-8gvp">https://github.com/advisories/GHSA-4qw4-jpp4-8gvp</a></p>
<p>Release Date: 2022-09-21</p>
<p>Fix Resolution: commonmarker - 0.23.6</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2023-26485</summary>
### Vulnerable Library - <b>commonmarker-0.17.13.gem</b></p>
<p>A fast, safe, extensible parser for CommonMark. This wraps the official libcmark library.</p>
<p>Library home page: <a href="https://rubygems.org/gems/commonmarker-0.17.13.gem">https://rubygems.org/gems/commonmarker-0.17.13.gem</a></p>
<p>Path to dependency file: /docs/Gemfile.lock</p>
<p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/commonmarker-0.17.13.gem</p>
<p>
Dependency Hierarchy:
- github-pages-219.gem (Root Library)
- jekyll-commonmark-ghpages-0.1.6.gem
- :x: **commonmarker-0.17.13.gem** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
cmark-gfm is GitHub's fork of cmark, a CommonMark parsing and rendering library and program in C. A polynomial time complexity issue in cmark-gfm may lead to unbounded resource exhaustion and subsequent denial of service. This CVE covers quadratic complexity issues when parsing text which leads with either large numbers of `_` characters. This issue has been addressed in version 0.29.0.gfm.10. Users are advised to upgrade. Users unable to upgrade should validate that their input comes from trusted sources. ### Impact A polynomial time complexity issue in cmark-gfm may lead to unbounded resource exhaustion and subsequent denial of service. ### Proof of concept ``` $ ~/cmark-gfm$ python3 -c 'pad = "_" * 100000; print(pad + "." + pad, end="")' | time ./build/src/cmark-gfm --to plaintext ``` Increasing the number 10000 in the above commands causes the running time to increase quadratically. ### Patches This vulnerability have been patched in 0.29.0.gfm.10. ### Note on cmark and cmark-gfm XXX: TBD [cmark-gfm](https://github.com/github/cmark-gfm) is a fork of [cmark](https://github.com/commonmark/cmark) that adds the GitHub Flavored Markdown extensions. The two codebases have diverged over time, but share a common core. These bugs affect both `cmark` and `cmark-gfm`. ### Credit We would like to thank @gravypod for reporting this vulnerability. ### References https://en.wikipedia.org/wiki/Time_complexity ### For more information If you have any questions or comments about this advisory: * Open an issue in [github/cmark-gfm](https://github.com/github/cmark-gfm)
<p>Publish Date: 2023-03-31
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-26485>CVE-2023-26485</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-48wp-p9qv-4j64">https://github.com/advisories/GHSA-48wp-p9qv-4j64</a></p>
<p>Release Date: 2023-03-31</p>
<p>Fix Resolution: commonmarker - 0.23.9</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2023-24824</summary>
### Vulnerable Library - <b>commonmarker-0.17.13.gem</b></p>
<p>A fast, safe, extensible parser for CommonMark. This wraps the official libcmark library.</p>
<p>Library home page: <a href="https://rubygems.org/gems/commonmarker-0.17.13.gem">https://rubygems.org/gems/commonmarker-0.17.13.gem</a></p>
<p>Path to dependency file: /docs/Gemfile.lock</p>
<p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/commonmarker-0.17.13.gem</p>
<p>
Dependency Hierarchy:
- github-pages-219.gem (Root Library)
- jekyll-commonmark-ghpages-0.1.6.gem
- :x: **commonmarker-0.17.13.gem** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
cmark-gfm is GitHub's fork of cmark, a CommonMark parsing and rendering library and program in C. A polynomial time complexity issue in cmark-gfm may lead to unbounded resource exhaustion and subsequent denial of service. This CVE covers quadratic complexity issues when parsing text which leads with either large numbers of `>` or `-` characters. This issue has been addressed in version 0.29.0.gfm.10. Users are advised to upgrade. Users unable to upgrade should validate that their input comes from trusted sources.
<p>Publish Date: 2023-03-31
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-24824>CVE-2023-24824</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-48wp-p9qv-4j64">https://github.com/advisories/GHSA-48wp-p9qv-4j64</a></p>
<p>Release Date: 2023-03-31</p>
<p>Fix Resolution: commonmarker - 0.23.9</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> WS-2023-0095</summary>
### Vulnerable Library - <b>commonmarker-0.17.13.gem</b></p>
<p>A fast, safe, extensible parser for CommonMark. This wraps the official libcmark library.</p>
<p>Library home page: <a href="https://rubygems.org/gems/commonmarker-0.17.13.gem">https://rubygems.org/gems/commonmarker-0.17.13.gem</a></p>
<p>Path to dependency file: /docs/Gemfile.lock</p>
<p>Path to vulnerable library: /home/wss-scanner/.gem/ruby/2.7.0/cache/commonmarker-0.17.13.gem</p>
<p>
Dependency Hierarchy:
- github-pages-219.gem (Root Library)
- jekyll-commonmark-ghpages-0.1.6.gem
- :x: **commonmarker-0.17.13.gem** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Commonmarker vulnerable to to several quadratic complexity bugs that may lead to denial of service
<p>Publish Date: 2023-04-12
<p>URL: <a href=https://github.com/gjtorikian/commonmarker/commit/42cfc90251353f9fceda91b884d0ded8d3da0bcf>WS-2023-0095</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-48wp-p9qv-4j64">https://github.com/advisories/GHSA-48wp-p9qv-4j64</a></p>
<p>Release Date: 2023-04-12</p>
<p>Fix Resolution: commonmarker - 0.23.9</p>
</p>
<p></p>
</details> | non_priority | github pages gem vulnerabilities highest severity is vulnerable library github pages gem path to dependency file docs gemfile lock path to vulnerable library home wss scanner gem ruby cache commonmarker gem vulnerabilities cve severity cvss dependency type fixed in github pages version remediation available high commonmarker gem transitive n a high commonmarker gem transitive n a high commonmarker gem transitive n a high commonmarker gem transitive n a high commonmarker gem transitive n a for some transitive vulnerabilities there is no version of direct dependency with a fix check the details section below to see if there is a version of transitive dependency where vulnerability is fixed details ws vulnerable library commonmarker gem a fast safe extensible parser for commonmark this wraps the official libcmark library library home page a href path to dependency file docs gemfile lock path to vulnerable library home wss scanner gem ruby cache commonmarker gem dependency hierarchy github pages gem root library jekyll commonmark ghpages gem x commonmarker gem vulnerable library found in base branch main vulnerability details commonmarker versions prior to are vulnerable to heap memory corruption when parsing tables whose marker rows contain more than max columns the impact of this heap corruption ranges from information leak to arbitrary code execution publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution commonmarker ws vulnerable library commonmarker gem a fast safe extensible parser for commonmark this wraps the official libcmark library library home page a href path to dependency file docs gemfile lock path to vulnerable library home wss scanner gem ruby cache commonmarker gem dependency hierarchy github pages gem root library jekyll commonmark ghpages gem x commonmarker gem vulnerable library found in base branch main vulnerability details unbounded resource exhaustion in cmark gfm autolink extension may lead to denial of service publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution commonmarker cve vulnerable library commonmarker gem a fast safe extensible parser for commonmark this wraps the official libcmark library library home page a href path to dependency file docs gemfile lock path to vulnerable library home wss scanner gem ruby cache commonmarker gem dependency hierarchy github pages gem root library jekyll commonmark ghpages gem x commonmarker gem vulnerable library found in base branch main vulnerability details cmark gfm is github s fork of cmark a commonmark parsing and rendering library and program in c a polynomial time complexity issue in cmark gfm may lead to unbounded resource exhaustion and subsequent denial of service this cve covers quadratic complexity issues when parsing text which leads with either large numbers of characters this issue has been addressed in version gfm users are advised to upgrade users unable to upgrade should validate that their input comes from trusted sources impact a polynomial time complexity issue in cmark gfm may lead to unbounded resource exhaustion and subsequent denial of service proof of concept cmark gfm c pad print pad pad end time build src cmark gfm to plaintext increasing the number in the above commands causes the running time to increase quadratically patches this vulnerability have been patched in gfm note on cmark and cmark gfm xxx tbd is a fork of that adds the github flavored markdown extensions the two codebases have diverged over time but share a common core these bugs affect both cmark and cmark gfm credit we would like to thank gravypod for reporting this vulnerability references for more information if you have any questions or comments about this advisory open an issue in publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution commonmarker cve vulnerable library commonmarker gem a fast safe extensible parser for commonmark this wraps the official libcmark library library home page a href path to dependency file docs gemfile lock path to vulnerable library home wss scanner gem ruby cache commonmarker gem dependency hierarchy github pages gem root library jekyll commonmark ghpages gem x commonmarker gem vulnerable library found in base branch main vulnerability details cmark gfm is github s fork of cmark a commonmark parsing and rendering library and program in c a polynomial time complexity issue in cmark gfm may lead to unbounded resource exhaustion and subsequent denial of service this cve covers quadratic complexity issues when parsing text which leads with either large numbers of or characters this issue has been addressed in version gfm users are advised to upgrade users unable to upgrade should validate that their input comes from trusted sources publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution commonmarker ws vulnerable library commonmarker gem a fast safe extensible parser for commonmark this wraps the official libcmark library library home page a href path to dependency file docs gemfile lock path to vulnerable library home wss scanner gem ruby cache commonmarker gem dependency hierarchy github pages gem root library jekyll commonmark ghpages gem x commonmarker gem vulnerable library found in base branch main vulnerability details commonmarker vulnerable to to several quadratic complexity bugs that may lead to denial of service publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution commonmarker | 0 |
49,015 | 7,469,596,128 | IssuesEvent | 2018-04-02 23:44:41 | raxod502/straight.el | https://api.github.com/repos/raxod502/straight.el | closed | Clarifications on recipe handling | documentation question | Hello,
I'm a user of emacs but not a programmer. I make a heavily use of org-mode for professional reasons. Your project straight.el is very interesting (as my linux of choice is nixos).
The documentation of straight.el is very comprehensive. However some things that should be clarified IMHO :
- is (straight-use-package '(some-package...)...) strictly equivalent to (use-package some-package :straight ...) ?
- does (use-package some-package :straight (some-package :host git ....) makes absolutely sure that some-package is downloaded from git ?
Thanks, and sorry if this is not properly an issue, I could ask the question on another channel if you prefer ...
| 1.0 | Clarifications on recipe handling - Hello,
I'm a user of emacs but not a programmer. I make a heavily use of org-mode for professional reasons. Your project straight.el is very interesting (as my linux of choice is nixos).
The documentation of straight.el is very comprehensive. However some things that should be clarified IMHO :
- is (straight-use-package '(some-package...)...) strictly equivalent to (use-package some-package :straight ...) ?
- does (use-package some-package :straight (some-package :host git ....) makes absolutely sure that some-package is downloaded from git ?
Thanks, and sorry if this is not properly an issue, I could ask the question on another channel if you prefer ...
| non_priority | clarifications on recipe handling hello i m a user of emacs but not a programmer i make a heavily use of org mode for professional reasons your project straight el is very interesting as my linux of choice is nixos the documentation of straight el is very comprehensive however some things that should be clarified imho is straight use package some package strictly equivalent to use package some package straight does use package some package straight some package host git makes absolutely sure that some package is downloaded from git thanks and sorry if this is not properly an issue i could ask the question on another channel if you prefer | 0 |
59,379 | 14,380,112,241 | IssuesEvent | 2020-12-02 02:00:47 | dotnet/aspnetcore | https://api.github.com/repos/dotnet/aspnetcore | closed | Document how to create custom external provider authentication | area-security | How can a custom external authentication provider (for example called **MyCustomAuth**) be implemented (from start to finish) like:
* [Your existing providers (Facebook/Google/Microsoft/etc..)](https://docs.microsoft.com/en-us/aspnet/core/security/authentication/social/?view=aspnetcore-3.1&tabs=visual-studio)
* [3rd-party providers (GitHub/LinkedIn/Yahoo/etc..)](https://docs.microsoft.com/en-us/aspnet/core/security/authentication/social/other-logins?view=aspnetcore-3.1)
I am able to setup the WebApp side & get an external login button, but cannot get the external provider side working with how the endpoints (**authorize**, **token** & **user information**) work and interact back to the WebApp.
I have attempted using an OAuthHandler, but if this is overkill and and a RemoteAuthenticationHandler or AuthenticationHandler could be used instead, please let me know.
Is there a basic example project to show how both sides work together OR in one that particularly demonstrates how the endpoints work with the authentication middleware and gets from:
* page **/Identity/Account/Login**, where a user then clicks on **MyCustomAuth** button under "**Use another service to log in**"
* to page **/Identity/Account/ExternalLogin**, where user enters their email and clicks **Register** under "**Associate your account**".
I think this documentation & example project would be very helpful.
Thanks in advance. | True | Document how to create custom external provider authentication - How can a custom external authentication provider (for example called **MyCustomAuth**) be implemented (from start to finish) like:
* [Your existing providers (Facebook/Google/Microsoft/etc..)](https://docs.microsoft.com/en-us/aspnet/core/security/authentication/social/?view=aspnetcore-3.1&tabs=visual-studio)
* [3rd-party providers (GitHub/LinkedIn/Yahoo/etc..)](https://docs.microsoft.com/en-us/aspnet/core/security/authentication/social/other-logins?view=aspnetcore-3.1)
I am able to setup the WebApp side & get an external login button, but cannot get the external provider side working with how the endpoints (**authorize**, **token** & **user information**) work and interact back to the WebApp.
I have attempted using an OAuthHandler, but if this is overkill and and a RemoteAuthenticationHandler or AuthenticationHandler could be used instead, please let me know.
Is there a basic example project to show how both sides work together OR in one that particularly demonstrates how the endpoints work with the authentication middleware and gets from:
* page **/Identity/Account/Login**, where a user then clicks on **MyCustomAuth** button under "**Use another service to log in**"
* to page **/Identity/Account/ExternalLogin**, where user enters their email and clicks **Register** under "**Associate your account**".
I think this documentation & example project would be very helpful.
Thanks in advance. | non_priority | document how to create custom external provider authentication how can a custom external authentication provider for example called mycustomauth be implemented from start to finish like i am able to setup the webapp side get an external login button but cannot get the external provider side working with how the endpoints authorize token user information work and interact back to the webapp i have attempted using an oauthhandler but if this is overkill and and a remoteauthenticationhandler or authenticationhandler could be used instead please let me know is there a basic example project to show how both sides work together or in one that particularly demonstrates how the endpoints work with the authentication middleware and gets from page identity account login where a user then clicks on mycustomauth button under use another service to log in to page identity account externallogin where user enters their email and clicks register under associate your account i think this documentation example project would be very helpful thanks in advance | 0 |
28,135 | 11,592,045,773 | IssuesEvent | 2020-02-24 10:39:38 | Altinn/altinn-studio | https://api.github.com/repos/Altinn/altinn-studio | reopened | Access to Register from Receipt | area/api-expose area/authorization area/receipt area/register kind/security kind/user-story solution/api-mgmt solution/platform | ## Description
Current implementation of Receipt is mostly in the browser client react app logic. A part of that is a request to retrieve the party object from Register. The issue with this is that Register requires a SubscriptionKey to get the request through API Management.
This change seeks to give Receipt a proxy function for Register. The react app logic should request Party through the Receipt API instead of directly against Register. The Receipt API logic can then add a subscription key to the request before forwarding it to Register.
## Considerations
It is important that Receipt doesn't create an open door to Register. The proxy function cannot take any input to determine what Party to retrieve. The Party returned must be based on the party cookie and access to the party must go through authorization. The party must match the owner of the Instance.
## Acceptance criteria
- [ ] Platform Receipt gets a new endpoint that can return the party of current instance owner (reportee)
- [ ] It must be impossible to request the party of "random" instance owners (partyid) by changing the cookie value.
## Specification tasks
- [ ] Development tasks are defined
- [ ] Test design / decide test need
## Development tasks
> Add tasks here
## Definition of done
- [ ] Documentation is updated (if relevant)
- [ ] Technical documentation (docs.altinn.studio)
- [ ] User documentation (altinn.github.io/docs)
- [ ] QA
- [ ] Manual test is complete (if relevant)
- [ ] Automated test is implemented (if relevant)
- [ ] All tasks in this userstory are closed (i.e. remaining tasks are moved to other user stories or marked obsolete)
| True | Access to Register from Receipt - ## Description
Current implementation of Receipt is mostly in the browser client react app logic. A part of that is a request to retrieve the party object from Register. The issue with this is that Register requires a SubscriptionKey to get the request through API Management.
This change seeks to give Receipt a proxy function for Register. The react app logic should request Party through the Receipt API instead of directly against Register. The Receipt API logic can then add a subscription key to the request before forwarding it to Register.
## Considerations
It is important that Receipt doesn't create an open door to Register. The proxy function cannot take any input to determine what Party to retrieve. The Party returned must be based on the party cookie and access to the party must go through authorization. The party must match the owner of the Instance.
## Acceptance criteria
- [ ] Platform Receipt gets a new endpoint that can return the party of current instance owner (reportee)
- [ ] It must be impossible to request the party of "random" instance owners (partyid) by changing the cookie value.
## Specification tasks
- [ ] Development tasks are defined
- [ ] Test design / decide test need
## Development tasks
> Add tasks here
## Definition of done
- [ ] Documentation is updated (if relevant)
- [ ] Technical documentation (docs.altinn.studio)
- [ ] User documentation (altinn.github.io/docs)
- [ ] QA
- [ ] Manual test is complete (if relevant)
- [ ] Automated test is implemented (if relevant)
- [ ] All tasks in this userstory are closed (i.e. remaining tasks are moved to other user stories or marked obsolete)
| non_priority | access to register from receipt description current implementation of receipt is mostly in the browser client react app logic a part of that is a request to retrieve the party object from register the issue with this is that register requires a subscriptionkey to get the request through api management this change seeks to give receipt a proxy function for register the react app logic should request party through the receipt api instead of directly against register the receipt api logic can then add a subscription key to the request before forwarding it to register considerations it is important that receipt doesn t create an open door to register the proxy function cannot take any input to determine what party to retrieve the party returned must be based on the party cookie and access to the party must go through authorization the party must match the owner of the instance acceptance criteria platform receipt gets a new endpoint that can return the party of current instance owner reportee it must be impossible to request the party of random instance owners partyid by changing the cookie value specification tasks development tasks are defined test design decide test need development tasks add tasks here definition of done documentation is updated if relevant technical documentation docs altinn studio user documentation altinn github io docs qa manual test is complete if relevant automated test is implemented if relevant all tasks in this userstory are closed i e remaining tasks are moved to other user stories or marked obsolete | 0 |
167,390 | 20,726,037,764 | IssuesEvent | 2022-03-14 02:05:12 | peterwkc85/Java_Jackson | https://api.github.com/repos/peterwkc85/Java_Jackson | opened | CVE-2020-10673 (High) detected in jackson-databind-2.2.3.jar | security vulnerability | ## CVE-2020-10673 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.2.3.jar</b></p></summary>
<p>A high-performance JSON processor (parser, generator).</p>
<p>Path to dependency file: /json-patch-master/json-patch-master/build.gradle</p>
<p>Path to vulnerable library: /json-patch-master/json-patch-master/build.gradle</p>
<p>
Dependency Hierarchy:
- jackson-coreutils-1.6.jar (Root Library)
- :x: **jackson-databind-2.2.3.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to com.caucho.config.types.ResourceRef (aka caucho-quercus).
<p>Publish Date: 2020-03-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-10673>CVE-2020-10673</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/FasterXML/jackson-databind/issues/2660">https://github.com/FasterXML/jackson-databind/issues/2660</a></p>
<p>Release Date: 2020-03-18</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.9.10.4</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-10673 (High) detected in jackson-databind-2.2.3.jar - ## CVE-2020-10673 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.2.3.jar</b></p></summary>
<p>A high-performance JSON processor (parser, generator).</p>
<p>Path to dependency file: /json-patch-master/json-patch-master/build.gradle</p>
<p>Path to vulnerable library: /json-patch-master/json-patch-master/build.gradle</p>
<p>
Dependency Hierarchy:
- jackson-coreutils-1.6.jar (Root Library)
- :x: **jackson-databind-2.2.3.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to com.caucho.config.types.ResourceRef (aka caucho-quercus).
<p>Publish Date: 2020-03-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-10673>CVE-2020-10673</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/FasterXML/jackson-databind/issues/2660">https://github.com/FasterXML/jackson-databind/issues/2660</a></p>
<p>Release Date: 2020-03-18</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.9.10.4</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in jackson databind jar cve high severity vulnerability vulnerable library jackson databind jar a high performance json processor parser generator path to dependency file json patch master json patch master build gradle path to vulnerable library json patch master json patch master build gradle dependency hierarchy jackson coreutils jar root library x jackson databind jar vulnerable library vulnerability details fasterxml jackson databind x before mishandles the interaction between serialization gadgets and typing related to com caucho config types resourceref aka caucho quercus publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution com fasterxml jackson core jackson databind step up your open source security game with whitesource | 0 |
63,247 | 26,321,559,845 | IssuesEvent | 2023-01-10 00:28:12 | hashicorp/terraform-provider-azurerm | https://api.github.com/repos/hashicorp/terraform-provider-azurerm | closed | Support for priority setting in azurerm_web_pubsub_hub event_handler | bug service/web-pub-sub | ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Community Note
<!--- Please keep this note for the community --->
* Please vote on this issue by adding a :thumbsup: [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
<!--- Thank you for keeping this note for the community --->
### Description
Hi,
I noticed that event handlers in Azure Web PubSub are ordered by priority. It is important because incoming events might be caught by the wrong handler before reaching the expected one if the correct priority is not set.
I haven't found a way to set the priority in the current module. Adding it in the future would be a good thing to fully support Azure Web PubSub.
Best regards.
### New or Affected Resource(s)/Data Source(s)
azurerm_web_pubsub_hub
### Potential Terraform Configuration
```hcl
resource "azurerm_web_pubsub_hub" "mediaplayer" {
name = "mediaplayer"
web_pubsub_id = azurerm_web_pubsub.webpubsub.id
anonymous_connections_enabled = true
event_handler {
url_template = var.connect_event_handler_url
system_events = ["connect"]
priority = 1
auth {
managed_identity_id = azurerm_web_pubsub.webpubsub.identity.0.principal_id
}
}
event_handler {
url_template = var.disconnect_event_handler_url
system_events = ["disconnect"]
priority = 5
auth {
managed_identity_id = azurerm_web_pubsub.webpubsub.identity.0.principal_id
}
}
}
```
### References
_No response_ | 1.0 | Support for priority setting in azurerm_web_pubsub_hub event_handler - ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Community Note
<!--- Please keep this note for the community --->
* Please vote on this issue by adding a :thumbsup: [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
<!--- Thank you for keeping this note for the community --->
### Description
Hi,
I noticed that event handlers in Azure Web PubSub are ordered by priority. It is important because incoming events might be caught by the wrong handler before reaching the expected one if the correct priority is not set.
I haven't found a way to set the priority in the current module. Adding it in the future would be a good thing to fully support Azure Web PubSub.
Best regards.
### New or Affected Resource(s)/Data Source(s)
azurerm_web_pubsub_hub
### Potential Terraform Configuration
```hcl
resource "azurerm_web_pubsub_hub" "mediaplayer" {
name = "mediaplayer"
web_pubsub_id = azurerm_web_pubsub.webpubsub.id
anonymous_connections_enabled = true
event_handler {
url_template = var.connect_event_handler_url
system_events = ["connect"]
priority = 1
auth {
managed_identity_id = azurerm_web_pubsub.webpubsub.identity.0.principal_id
}
}
event_handler {
url_template = var.disconnect_event_handler_url
system_events = ["disconnect"]
priority = 5
auth {
managed_identity_id = azurerm_web_pubsub.webpubsub.identity.0.principal_id
}
}
}
```
### References
_No response_ | non_priority | support for priority setting in azurerm web pubsub hub event handler is there an existing issue for this i have searched the existing issues community note please vote on this issue by adding a thumbsup to the original issue to help the community and maintainers prioritize this request please do not leave or me too comments they generate extra noise for issue followers and do not help prioritize the request if you are interested in working on this issue or have submitted a pull request please leave a comment description hi i noticed that event handlers in azure web pubsub are ordered by priority it is important because incoming events might be caught by the wrong handler before reaching the expected one if the correct priority is not set i haven t found a way to set the priority in the current module adding it in the future would be a good thing to fully support azure web pubsub best regards new or affected resource s data source s azurerm web pubsub hub potential terraform configuration hcl resource azurerm web pubsub hub mediaplayer name mediaplayer web pubsub id azurerm web pubsub webpubsub id anonymous connections enabled true event handler url template var connect event handler url system events priority auth managed identity id azurerm web pubsub webpubsub identity principal id event handler url template var disconnect event handler url system events priority auth managed identity id azurerm web pubsub webpubsub identity principal id references no response | 0 |
132,743 | 28,313,414,646 | IssuesEvent | 2023-04-10 17:24:42 | rust-lang/rust | https://api.github.com/repos/rust-lang/rust | closed | `./x.py test src/test/codegen` fails | A-testsuite A-codegen C-bug A-contributor-roadblock | Codegen tests currently fail in stage 1:
```
---- [codegen] src/test/codegen/mem-replace-direct-memcpy.rs stdout ----
error: verification with 'FileCheck' failed
status: exit status: 1
command: "/home/r/src/rust/rustc.3/build/x86_64-unknown-linux-gnu/ci-llvm/bin/FileCheck" "--input-file" "/home/r/src/rust/rustc.3/build/x86_64-unknown-linux-gnu/test/codegen/mem-replace-direct-memcpy/mem-replace-direct-memcpy.ll" "/home/r/src/rust/rustc.3/src/test/codegen/mem-replace-direct-memcpy.rs" "--allow-unused-prefixes" "--check-prefixes" "CHECK,NONMSVC"
stdout: none
--- stderr -------------------------------
/home/r/src/rust/rustc.3/src/test/codegen/mem-replace-direct-memcpy.rs:20:11: error: CHECK: expected string not found in input
// CHECK: call void @llvm.memcpy.{{.+}}({{i8\*|ptr}} align 1 %{{.*}}, {{i8\*|ptr}} align 1 %dest, i{{.*}} 1, i1 false)
^
/home/r/src/rust/rustc.3/build/x86_64-unknown-linux-gnu/test/codegen/mem-replace-direct-memcpy/mem-replace-direct-memcpy.ll:52:21: note: scanning from here
; core::mem::replace
^
/home/r/src/rust/rustc.3/build/x86_64-unknown-linux-gnu/test/codegen/mem-replace-direct-memcpy/mem-replace-direct-memcpy.ll:138:2: note: possible intended match here
call void @llvm.memcpy.p0i8.p0i8.i64(i8* align 1 %_4, i8* align 1 %src, i64 1, i1 false)
^
```
I think this started with https://github.com/rust-lang/rust/pull/91743. | 1.0 | `./x.py test src/test/codegen` fails - Codegen tests currently fail in stage 1:
```
---- [codegen] src/test/codegen/mem-replace-direct-memcpy.rs stdout ----
error: verification with 'FileCheck' failed
status: exit status: 1
command: "/home/r/src/rust/rustc.3/build/x86_64-unknown-linux-gnu/ci-llvm/bin/FileCheck" "--input-file" "/home/r/src/rust/rustc.3/build/x86_64-unknown-linux-gnu/test/codegen/mem-replace-direct-memcpy/mem-replace-direct-memcpy.ll" "/home/r/src/rust/rustc.3/src/test/codegen/mem-replace-direct-memcpy.rs" "--allow-unused-prefixes" "--check-prefixes" "CHECK,NONMSVC"
stdout: none
--- stderr -------------------------------
/home/r/src/rust/rustc.3/src/test/codegen/mem-replace-direct-memcpy.rs:20:11: error: CHECK: expected string not found in input
// CHECK: call void @llvm.memcpy.{{.+}}({{i8\*|ptr}} align 1 %{{.*}}, {{i8\*|ptr}} align 1 %dest, i{{.*}} 1, i1 false)
^
/home/r/src/rust/rustc.3/build/x86_64-unknown-linux-gnu/test/codegen/mem-replace-direct-memcpy/mem-replace-direct-memcpy.ll:52:21: note: scanning from here
; core::mem::replace
^
/home/r/src/rust/rustc.3/build/x86_64-unknown-linux-gnu/test/codegen/mem-replace-direct-memcpy/mem-replace-direct-memcpy.ll:138:2: note: possible intended match here
call void @llvm.memcpy.p0i8.p0i8.i64(i8* align 1 %_4, i8* align 1 %src, i64 1, i1 false)
^
```
I think this started with https://github.com/rust-lang/rust/pull/91743. | non_priority | x py test src test codegen fails codegen tests currently fail in stage src test codegen mem replace direct memcpy rs stdout error verification with filecheck failed status exit status command home r src rust rustc build unknown linux gnu ci llvm bin filecheck input file home r src rust rustc build unknown linux gnu test codegen mem replace direct memcpy mem replace direct memcpy ll home r src rust rustc src test codegen mem replace direct memcpy rs allow unused prefixes check prefixes check nonmsvc stdout none stderr home r src rust rustc src test codegen mem replace direct memcpy rs error check expected string not found in input check call void llvm memcpy ptr align ptr align dest i false home r src rust rustc build unknown linux gnu test codegen mem replace direct memcpy mem replace direct memcpy ll note scanning from here core mem replace home r src rust rustc build unknown linux gnu test codegen mem replace direct memcpy mem replace direct memcpy ll note possible intended match here call void llvm memcpy align align src false i think this started with | 0 |
34,464 | 7,836,503,159 | IssuesEvent | 2018-06-17 20:18:25 | SSYGEN/blog | https://api.github.com/repos/SSYGEN/blog | closed | The Value of Copypasting | code organization | `2016-02-05 13:46`
Yesterday I read a blog post, [this one](http://benmccormick.org/2016/01/08/reusable-code-patterns/), about code reuse patterns. I think it's mostly correct in its assessments but IMO it doesn't do justice to the **Copy and Paste** technique. So in this post I'll explain why I think copypasting your own code instead of properly making it reusable is a good idea more often than you'd think, especially if you're an indie developer working on an indie game. Also, if you're surprised like [this guy](https://www.reddit.com/r/gamedev/comments/445dr1/state_of_game_code/) at how "bad" game code can be, hopefully this article will shed some light into why that's often true.
<br>
## Reuse
My main argument is that the costs of copypasting are often lower than the ongoing costs of properly making things reusable. So first let's try an example showing the process of making reusable code. This example will use functions but the same thought process applies to classes, mixins, components, inheritance and what have you that you decide to use to reuse code.
So assume we want to add functionality `X` to the codebase and it's made up of three logical parts, `A`, `B` and `C`. I'd do that like this:
``` lua
-- A, explains what A does
block 1
block 2
block 3
-- B, explains what B does
block 4
block 5
-- C, explains what C does
block 6
block 7
block 8
```
If I'm only using `X` in one place I'd probably write it like I wrote it up there, with simple comments (-- are comments) dividing the different logical sections and explaining what each section does when necessary. If I'm calling `X` from multiple places then I'd wrap the above code in a function named `X`.
This is all good and simple so far. But now suppose we want to add functionality `Y`. And this new functionality is really similar to `X`, in that it uses `A`, `B` and `C`, except `A` has to be a bit different, maybe `block 2` has to be changed for `block 9`, and after `block 3` there should be an additional `block 10`.
So now first what we can do is take `B` and `C` out into their own functions, since they're going to be reused by `X` and `Y`:
``` lua
function B()
block 4
block 5
end
function C()
block 6
block 7
block 8
end
```
And then what we can do is either create a new function `D`, which will be the modified `A`, or modify `A` such that it takes into account the possibilities that functionality `Y` needs. The first solution would look like this:
``` lua
...
function A()
block 1
block 2
block 3
end
function D()
block 1
block 9
block 3
block 10
end
function X()
A()
B()
C()
end
function Y()
D()
B()
C()
end
```
The problem with this solution is that now `block 1` and `block 3` are repeated on `A` and `D` and since we want to minimize code repetition this won't work.
The second solution avoids code duplication by doing this:
``` lua
...
function A(y_flag)
block 1
if d_flag
block 9
else
block 2
block 3
if d_flag
block 10
end
function X()
A()
B()
C()
end
function Y()
A(y_flag = true)
B()
C()
end
```
This solution is better from a code duplication perspective because it gets rid of it, but it also has its own problems in that as the needs of `A` grow with more and more functionalities, it will become a confusing land of random conditionals and settings that is going to be really hard to logically follow.
Anyway, either solution chosen, suppose now that we want to add functionality `Z`, which, again, is really similar to both `X` and `Y` but slightly different. Now `A` is also a little different where `block 3` needs to be `block 12`. And again, we can go through the same exercise of either choosing to create a new function `E` that will be exactly what `Z` needs:
``` lua
function A()
block 1
block 2
block 3
end
function D()
block 1
block 9
block 3
block 10
end
function E()
block 1
block 2
block 12
end
function X()
A()
B()
C()
end
function Y()
D()
B()
C()
end
function Z()
E()
B()
C()
end
```
Or changing `A` to suit `Z`'s needs:
``` lua
...
function A(y_flag, z_flag)
block 1
if y_flag
block 9
else
block 2
if z_flag
block 12
else
block 3
if y_flag
block 10
end
function X()
A()
B()
C()
end
function Y()
A(y_flag = true)
B()
C()
end
function Z()
A(z_flag = true)
B()
C()
end
```
Either way we choose, we lose. This is because this exercise will keep going on and on forever as we add new functionality to our codebase, and as the codebase grows, whatever we did to minimize code duplication will make it fundamentally more complex. The solution where you add a new function adds a new node to your code, and with a new node now you have more dependencies to think about and worry about. The solution where you add flags and settings adds logical complexity to the flow of the affected function, which makes the code a lot harder to reason about. Any other solution out of this problem will do either of those things and complexity will grow.
The point here is not that code reuse is bad, but that there are ongoing costs to making things reusable. The cost here is that at each point you have to add a new functionality, you'll have to think about which solution to choose to minimize duplication and which previous components/functions that exist in the codebase that you should look at to change and/or use. The process of building reusable code is one where you have to think about how to integrate new functionality against existing code instead of just adding new functionality. This is a huge mental resource drain that most people forget to take into account.
<br>
## Copypasting
Now let's look at the same example through a copypasting lens. We add functionality `X`:
``` lua
function X()
-- A
block 1
block 2
block 3
-- B
block 4
block 5
-- C
block 6
block 7
block 8
end
```
Now we want to add functionality `Y`, which is a bit different from `X` in the ways described earlier. Instead of worrying about what can and can't be reused, we'll just copy paste `X` and change what needs to be changed:
``` lua
function Y()
-- A
block 1
block 9
block 3
block 10
-- B
block 4
block 5
-- C
block 6
block 7
block 8
end
```
Now we want to add functionality `Z`, which is similar to `X` and `Y`. Again, instead of worrying about what can and can't be reused, we'll just copy paste `X` again and change what needs to be changed:
``` lua
function Z()
-- A
block 1
block 2
block 11
-- B
block 4
block 5
-- C
block 6
block 7
block 8
end
```
Isn't this process much much simpler? This takes no mental effort at all. You literally just copypaste and change what needs to be changed. Yes, there are very obvious problems with copypasting. If we want to change how `B` works for instance now we have 3 places where we have to make that change. And that's a bad thing! But my point is that people should know when the costs of doing this are higher than the ongoing costs of making things reusable and when they aren't.
The upfront costs of copypasting are usually a lot lower than the upfront costs of making things reusable. This is a fact. The long term costs of copypasting are usually a lot higher than the long term costs of making things reusable. This is another fact. But people often forget about the first fact and that they can use both of them to make reasonable and responsible trades in their codebase. The lower upfront costs of copypasting can be extremely useful in a huge number of situations, but a lot of people default to reuse always, and that's a huge waste of mental resources and a huge unnecessary increase in complexity.
<br>
## Frequency of Change
One of the ways you can use to figure out when using copypasting actually makes sense is looking at the frequency of change of some part of your codebase. If in the example above we know (through experience or instinct) that `C` is a piece of code that has a very low frequency of change, then it makes a lot of sense to not care about it from a code duplication perspective, because most of the time it won't be changed.
For instance, suppose that for every 20 functionalities we add that are similar enough to `X`, only once does `C` change. In this case it makes sense to put `C` away as a function, call it from `X` and then just copypaste `X` each time for each new functionality. When `C` changes (which doesn't happen often), we'll either have to change the function itself or add a new function similar enough to `C`, which is exactly what we did for `A` in the example above. The difference here is that instead of defaulting to reuse, we default to copypaste and use reuse where it actually makes sense to use it. And we do this because the situation called for it, not because we just decided that this was going to be a rule that we always follow.
<br>
## Example
So now for a real example. This is an attack in one of the games I'm working on:
<p align="center">
<img src="https://github.com/adonaac/blog/raw/master/images/punch.gif"/>
</p>
It's a 3 part melee attack, light -> medium -> heavy punches as the player presses the same key over and over. All that's happening to make this happen is: player presses key, character plays some animation, a hitbox is created to see if the attack hit anyone, then if it hit someone a series of events happen, like the enemy gets pushed back and loses some HP, and the camera shakes, and some particles fly around and so on. To get this attack going I need 3 main files.
The first file is an attack object. This gets attached to the player and then input is directed to the current attack attached to the key pressed. The attack object has state and logic needed to make the player side of this attack work, which is logic needed for which animation to play (if the sequence is in light, medium or heavy punch stage), cooldowns, pushing the player forward or backwards a bit and so on. This is also where the melee hitbox gets created.
The second file is the melee hitbox. This is just a normal hitbox that collides with relevant enemies to see if the attack hit them or not. If it collides, this calls the appropriate function for this attack and passes as arguments to it the hitbox, the player, the enemy hit and some other additional necessary data.
The third file is the function that gets called by the melee hitbox. I call these functions events. Basically they're functions that will receive all interested parties of this attack and do things to them, like deal damage to enemies, give HP back to the player if it has some life leech passive, shake the screen, add some effects, create particles and so on.
Out of these files, the first and third ones are the ones I'm constantly copy pasting. If I want to add another 3 stage attack for instance, but with kick animations instead of punches, I'll just copy paste the 3 stage punch and change what's needed to change. The same goes for the third file. If some event is similar enough to the event of another attack I'll just copy paste it. And this is the optimal course of action for attacks. Because I'm constantly adding attacks to the game and very rarely changing how attacks in general work. The times where I need to change something for all attacks happen, but they're really rare compared to the times where I have to add a new attack. So it makes the most sense to minimize costs of adding new attacks by levering the low upfront costs of copypasting.
---
The general rule here is that a lot of the times it's better to optimize for _process simplification_ than it is to optimize for code reuse. And this is especially true with indie game development. Simple processes for doing things to your game require less mental effort, which means you can work for longer and you're less likely to get demotivated by high complexity.
At the same time, when you do need to do something dumb like changing the general case in 20 places because you didn't abstract things properly, this is dumb work that is also very easy to do and that you don't need to think about, which also minimizes mental effort spent. And on top of this, since gameplay code is often changing in unexpected ways, it's usually better to start from dumb code and generalize from there than it is to start from generalized code and working your way backwards.
<br>
## END
Hopefully we've all learned something from this. One thing I noticed is that often times I see indie developers with amazing games, but by all normal standards if you were to look at their code they would be considered bad coders who just don't know any good practices.
I think intuitively people realize that doing things like what I outlined in this article is a good idea, and so you get lots of "dumb" code that works. It's important to understand that if you're able to analyze these tradeoffs properly you can make informed decisions about how to engage in those dumb activities while decreasing the overall costs of making whatever you want to make.
Also don't let other people bully you into "proper" code and tell you your code is dumb. Tell them they're dumb instead and that their code is even dumber and that they should be ashamed of trying to shame you. And tell them Undertale has dumb code so it's okay to have dumb code too. Look:
<p align="center">
<img src="http://i.imgur.com/yfXIjC7.png"/>
</p>
| 1.0 | The Value of Copypasting - `2016-02-05 13:46`
Yesterday I read a blog post, [this one](http://benmccormick.org/2016/01/08/reusable-code-patterns/), about code reuse patterns. I think it's mostly correct in its assessments but IMO it doesn't do justice to the **Copy and Paste** technique. So in this post I'll explain why I think copypasting your own code instead of properly making it reusable is a good idea more often than you'd think, especially if you're an indie developer working on an indie game. Also, if you're surprised like [this guy](https://www.reddit.com/r/gamedev/comments/445dr1/state_of_game_code/) at how "bad" game code can be, hopefully this article will shed some light into why that's often true.
<br>
## Reuse
My main argument is that the costs of copypasting are often lower than the ongoing costs of properly making things reusable. So first let's try an example showing the process of making reusable code. This example will use functions but the same thought process applies to classes, mixins, components, inheritance and what have you that you decide to use to reuse code.
So assume we want to add functionality `X` to the codebase and it's made up of three logical parts, `A`, `B` and `C`. I'd do that like this:
``` lua
-- A, explains what A does
block 1
block 2
block 3
-- B, explains what B does
block 4
block 5
-- C, explains what C does
block 6
block 7
block 8
```
If I'm only using `X` in one place I'd probably write it like I wrote it up there, with simple comments (-- are comments) dividing the different logical sections and explaining what each section does when necessary. If I'm calling `X` from multiple places then I'd wrap the above code in a function named `X`.
This is all good and simple so far. But now suppose we want to add functionality `Y`. And this new functionality is really similar to `X`, in that it uses `A`, `B` and `C`, except `A` has to be a bit different, maybe `block 2` has to be changed for `block 9`, and after `block 3` there should be an additional `block 10`.
So now first what we can do is take `B` and `C` out into their own functions, since they're going to be reused by `X` and `Y`:
``` lua
function B()
block 4
block 5
end
function C()
block 6
block 7
block 8
end
```
And then what we can do is either create a new function `D`, which will be the modified `A`, or modify `A` such that it takes into account the possibilities that functionality `Y` needs. The first solution would look like this:
``` lua
...
function A()
block 1
block 2
block 3
end
function D()
block 1
block 9
block 3
block 10
end
function X()
A()
B()
C()
end
function Y()
D()
B()
C()
end
```
The problem with this solution is that now `block 1` and `block 3` are repeated on `A` and `D` and since we want to minimize code repetition this won't work.
The second solution avoids code duplication by doing this:
``` lua
...
function A(y_flag)
block 1
if d_flag
block 9
else
block 2
block 3
if d_flag
block 10
end
function X()
A()
B()
C()
end
function Y()
A(y_flag = true)
B()
C()
end
```
This solution is better from a code duplication perspective because it gets rid of it, but it also has its own problems in that as the needs of `A` grow with more and more functionalities, it will become a confusing land of random conditionals and settings that is going to be really hard to logically follow.
Anyway, either solution chosen, suppose now that we want to add functionality `Z`, which, again, is really similar to both `X` and `Y` but slightly different. Now `A` is also a little different where `block 3` needs to be `block 12`. And again, we can go through the same exercise of either choosing to create a new function `E` that will be exactly what `Z` needs:
``` lua
function A()
block 1
block 2
block 3
end
function D()
block 1
block 9
block 3
block 10
end
function E()
block 1
block 2
block 12
end
function X()
A()
B()
C()
end
function Y()
D()
B()
C()
end
function Z()
E()
B()
C()
end
```
Or changing `A` to suit `Z`'s needs:
``` lua
...
function A(y_flag, z_flag)
block 1
if y_flag
block 9
else
block 2
if z_flag
block 12
else
block 3
if y_flag
block 10
end
function X()
A()
B()
C()
end
function Y()
A(y_flag = true)
B()
C()
end
function Z()
A(z_flag = true)
B()
C()
end
```
Either way we choose, we lose. This is because this exercise will keep going on and on forever as we add new functionality to our codebase, and as the codebase grows, whatever we did to minimize code duplication will make it fundamentally more complex. The solution where you add a new function adds a new node to your code, and with a new node now you have more dependencies to think about and worry about. The solution where you add flags and settings adds logical complexity to the flow of the affected function, which makes the code a lot harder to reason about. Any other solution out of this problem will do either of those things and complexity will grow.
The point here is not that code reuse is bad, but that there are ongoing costs to making things reusable. The cost here is that at each point you have to add a new functionality, you'll have to think about which solution to choose to minimize duplication and which previous components/functions that exist in the codebase that you should look at to change and/or use. The process of building reusable code is one where you have to think about how to integrate new functionality against existing code instead of just adding new functionality. This is a huge mental resource drain that most people forget to take into account.
<br>
## Copypasting
Now let's look at the same example through a copypasting lens. We add functionality `X`:
``` lua
function X()
-- A
block 1
block 2
block 3
-- B
block 4
block 5
-- C
block 6
block 7
block 8
end
```
Now we want to add functionality `Y`, which is a bit different from `X` in the ways described earlier. Instead of worrying about what can and can't be reused, we'll just copy paste `X` and change what needs to be changed:
``` lua
function Y()
-- A
block 1
block 9
block 3
block 10
-- B
block 4
block 5
-- C
block 6
block 7
block 8
end
```
Now we want to add functionality `Z`, which is similar to `X` and `Y`. Again, instead of worrying about what can and can't be reused, we'll just copy paste `X` again and change what needs to be changed:
``` lua
function Z()
-- A
block 1
block 2
block 11
-- B
block 4
block 5
-- C
block 6
block 7
block 8
end
```
Isn't this process much much simpler? This takes no mental effort at all. You literally just copypaste and change what needs to be changed. Yes, there are very obvious problems with copypasting. If we want to change how `B` works for instance now we have 3 places where we have to make that change. And that's a bad thing! But my point is that people should know when the costs of doing this are higher than the ongoing costs of making things reusable and when they aren't.
The upfront costs of copypasting are usually a lot lower than the upfront costs of making things reusable. This is a fact. The long term costs of copypasting are usually a lot higher than the long term costs of making things reusable. This is another fact. But people often forget about the first fact and that they can use both of them to make reasonable and responsible trades in their codebase. The lower upfront costs of copypasting can be extremely useful in a huge number of situations, but a lot of people default to reuse always, and that's a huge waste of mental resources and a huge unnecessary increase in complexity.
<br>
## Frequency of Change
One of the ways you can use to figure out when using copypasting actually makes sense is looking at the frequency of change of some part of your codebase. If in the example above we know (through experience or instinct) that `C` is a piece of code that has a very low frequency of change, then it makes a lot of sense to not care about it from a code duplication perspective, because most of the time it won't be changed.
For instance, suppose that for every 20 functionalities we add that are similar enough to `X`, only once does `C` change. In this case it makes sense to put `C` away as a function, call it from `X` and then just copypaste `X` each time for each new functionality. When `C` changes (which doesn't happen often), we'll either have to change the function itself or add a new function similar enough to `C`, which is exactly what we did for `A` in the example above. The difference here is that instead of defaulting to reuse, we default to copypaste and use reuse where it actually makes sense to use it. And we do this because the situation called for it, not because we just decided that this was going to be a rule that we always follow.
<br>
## Example
So now for a real example. This is an attack in one of the games I'm working on:
<p align="center">
<img src="https://github.com/adonaac/blog/raw/master/images/punch.gif"/>
</p>
It's a 3 part melee attack, light -> medium -> heavy punches as the player presses the same key over and over. All that's happening to make this happen is: player presses key, character plays some animation, a hitbox is created to see if the attack hit anyone, then if it hit someone a series of events happen, like the enemy gets pushed back and loses some HP, and the camera shakes, and some particles fly around and so on. To get this attack going I need 3 main files.
The first file is an attack object. This gets attached to the player and then input is directed to the current attack attached to the key pressed. The attack object has state and logic needed to make the player side of this attack work, which is logic needed for which animation to play (if the sequence is in light, medium or heavy punch stage), cooldowns, pushing the player forward or backwards a bit and so on. This is also where the melee hitbox gets created.
The second file is the melee hitbox. This is just a normal hitbox that collides with relevant enemies to see if the attack hit them or not. If it collides, this calls the appropriate function for this attack and passes as arguments to it the hitbox, the player, the enemy hit and some other additional necessary data.
The third file is the function that gets called by the melee hitbox. I call these functions events. Basically they're functions that will receive all interested parties of this attack and do things to them, like deal damage to enemies, give HP back to the player if it has some life leech passive, shake the screen, add some effects, create particles and so on.
Out of these files, the first and third ones are the ones I'm constantly copy pasting. If I want to add another 3 stage attack for instance, but with kick animations instead of punches, I'll just copy paste the 3 stage punch and change what's needed to change. The same goes for the third file. If some event is similar enough to the event of another attack I'll just copy paste it. And this is the optimal course of action for attacks. Because I'm constantly adding attacks to the game and very rarely changing how attacks in general work. The times where I need to change something for all attacks happen, but they're really rare compared to the times where I have to add a new attack. So it makes the most sense to minimize costs of adding new attacks by levering the low upfront costs of copypasting.
---
The general rule here is that a lot of the times it's better to optimize for _process simplification_ than it is to optimize for code reuse. And this is especially true with indie game development. Simple processes for doing things to your game require less mental effort, which means you can work for longer and you're less likely to get demotivated by high complexity.
At the same time, when you do need to do something dumb like changing the general case in 20 places because you didn't abstract things properly, this is dumb work that is also very easy to do and that you don't need to think about, which also minimizes mental effort spent. And on top of this, since gameplay code is often changing in unexpected ways, it's usually better to start from dumb code and generalize from there than it is to start from generalized code and working your way backwards.
<br>
## END
Hopefully we've all learned something from this. One thing I noticed is that often times I see indie developers with amazing games, but by all normal standards if you were to look at their code they would be considered bad coders who just don't know any good practices.
I think intuitively people realize that doing things like what I outlined in this article is a good idea, and so you get lots of "dumb" code that works. It's important to understand that if you're able to analyze these tradeoffs properly you can make informed decisions about how to engage in those dumb activities while decreasing the overall costs of making whatever you want to make.
Also don't let other people bully you into "proper" code and tell you your code is dumb. Tell them they're dumb instead and that their code is even dumber and that they should be ashamed of trying to shame you. And tell them Undertale has dumb code so it's okay to have dumb code too. Look:
<p align="center">
<img src="http://i.imgur.com/yfXIjC7.png"/>
</p>
| non_priority | the value of copypasting yesterday i read a blog post about code reuse patterns i think it s mostly correct in its assessments but imo it doesn t do justice to the copy and paste technique so in this post i ll explain why i think copypasting your own code instead of properly making it reusable is a good idea more often than you d think especially if you re an indie developer working on an indie game also if you re surprised like at how bad game code can be hopefully this article will shed some light into why that s often true reuse my main argument is that the costs of copypasting are often lower than the ongoing costs of properly making things reusable so first let s try an example showing the process of making reusable code this example will use functions but the same thought process applies to classes mixins components inheritance and what have you that you decide to use to reuse code so assume we want to add functionality x to the codebase and it s made up of three logical parts a b and c i d do that like this lua a explains what a does block block block b explains what b does block block c explains what c does block block block if i m only using x in one place i d probably write it like i wrote it up there with simple comments are comments dividing the different logical sections and explaining what each section does when necessary if i m calling x from multiple places then i d wrap the above code in a function named x this is all good and simple so far but now suppose we want to add functionality y and this new functionality is really similar to x in that it uses a b and c except a has to be a bit different maybe block has to be changed for block and after block there should be an additional block so now first what we can do is take b and c out into their own functions since they re going to be reused by x and y lua function b block block end function c block block block end and then what we can do is either create a new function d which will be the modified a or modify a such that it takes into account the possibilities that functionality y needs the first solution would look like this lua function a block block block end function d block block block block end function x a b c end function y d b c end the problem with this solution is that now block and block are repeated on a and d and since we want to minimize code repetition this won t work the second solution avoids code duplication by doing this lua function a y flag block if d flag block else block block if d flag block end function x a b c end function y a y flag true b c end this solution is better from a code duplication perspective because it gets rid of it but it also has its own problems in that as the needs of a grow with more and more functionalities it will become a confusing land of random conditionals and settings that is going to be really hard to logically follow anyway either solution chosen suppose now that we want to add functionality z which again is really similar to both x and y but slightly different now a is also a little different where block needs to be block and again we can go through the same exercise of either choosing to create a new function e that will be exactly what z needs lua function a block block block end function d block block block block end function e block block block end function x a b c end function y d b c end function z e b c end or changing a to suit z s needs lua function a y flag z flag block if y flag block else block if z flag block else block if y flag block end function x a b c end function y a y flag true b c end function z a z flag true b c end either way we choose we lose this is because this exercise will keep going on and on forever as we add new functionality to our codebase and as the codebase grows whatever we did to minimize code duplication will make it fundamentally more complex the solution where you add a new function adds a new node to your code and with a new node now you have more dependencies to think about and worry about the solution where you add flags and settings adds logical complexity to the flow of the affected function which makes the code a lot harder to reason about any other solution out of this problem will do either of those things and complexity will grow the point here is not that code reuse is bad but that there are ongoing costs to making things reusable the cost here is that at each point you have to add a new functionality you ll have to think about which solution to choose to minimize duplication and which previous components functions that exist in the codebase that you should look at to change and or use the process of building reusable code is one where you have to think about how to integrate new functionality against existing code instead of just adding new functionality this is a huge mental resource drain that most people forget to take into account copypasting now let s look at the same example through a copypasting lens we add functionality x lua function x a block block block b block block c block block block end now we want to add functionality y which is a bit different from x in the ways described earlier instead of worrying about what can and can t be reused we ll just copy paste x and change what needs to be changed lua function y a block block block block b block block c block block block end now we want to add functionality z which is similar to x and y again instead of worrying about what can and can t be reused we ll just copy paste x again and change what needs to be changed lua function z a block block block b block block c block block block end isn t this process much much simpler this takes no mental effort at all you literally just copypaste and change what needs to be changed yes there are very obvious problems with copypasting if we want to change how b works for instance now we have places where we have to make that change and that s a bad thing but my point is that people should know when the costs of doing this are higher than the ongoing costs of making things reusable and when they aren t the upfront costs of copypasting are usually a lot lower than the upfront costs of making things reusable this is a fact the long term costs of copypasting are usually a lot higher than the long term costs of making things reusable this is another fact but people often forget about the first fact and that they can use both of them to make reasonable and responsible trades in their codebase the lower upfront costs of copypasting can be extremely useful in a huge number of situations but a lot of people default to reuse always and that s a huge waste of mental resources and a huge unnecessary increase in complexity frequency of change one of the ways you can use to figure out when using copypasting actually makes sense is looking at the frequency of change of some part of your codebase if in the example above we know through experience or instinct that c is a piece of code that has a very low frequency of change then it makes a lot of sense to not care about it from a code duplication perspective because most of the time it won t be changed for instance suppose that for every functionalities we add that are similar enough to x only once does c change in this case it makes sense to put c away as a function call it from x and then just copypaste x each time for each new functionality when c changes which doesn t happen often we ll either have to change the function itself or add a new function similar enough to c which is exactly what we did for a in the example above the difference here is that instead of defaulting to reuse we default to copypaste and use reuse where it actually makes sense to use it and we do this because the situation called for it not because we just decided that this was going to be a rule that we always follow example so now for a real example this is an attack in one of the games i m working on img src it s a part melee attack light medium heavy punches as the player presses the same key over and over all that s happening to make this happen is player presses key character plays some animation a hitbox is created to see if the attack hit anyone then if it hit someone a series of events happen like the enemy gets pushed back and loses some hp and the camera shakes and some particles fly around and so on to get this attack going i need main files the first file is an attack object this gets attached to the player and then input is directed to the current attack attached to the key pressed the attack object has state and logic needed to make the player side of this attack work which is logic needed for which animation to play if the sequence is in light medium or heavy punch stage cooldowns pushing the player forward or backwards a bit and so on this is also where the melee hitbox gets created the second file is the melee hitbox this is just a normal hitbox that collides with relevant enemies to see if the attack hit them or not if it collides this calls the appropriate function for this attack and passes as arguments to it the hitbox the player the enemy hit and some other additional necessary data the third file is the function that gets called by the melee hitbox i call these functions events basically they re functions that will receive all interested parties of this attack and do things to them like deal damage to enemies give hp back to the player if it has some life leech passive shake the screen add some effects create particles and so on out of these files the first and third ones are the ones i m constantly copy pasting if i want to add another stage attack for instance but with kick animations instead of punches i ll just copy paste the stage punch and change what s needed to change the same goes for the third file if some event is similar enough to the event of another attack i ll just copy paste it and this is the optimal course of action for attacks because i m constantly adding attacks to the game and very rarely changing how attacks in general work the times where i need to change something for all attacks happen but they re really rare compared to the times where i have to add a new attack so it makes the most sense to minimize costs of adding new attacks by levering the low upfront costs of copypasting the general rule here is that a lot of the times it s better to optimize for process simplification than it is to optimize for code reuse and this is especially true with indie game development simple processes for doing things to your game require less mental effort which means you can work for longer and you re less likely to get demotivated by high complexity at the same time when you do need to do something dumb like changing the general case in places because you didn t abstract things properly this is dumb work that is also very easy to do and that you don t need to think about which also minimizes mental effort spent and on top of this since gameplay code is often changing in unexpected ways it s usually better to start from dumb code and generalize from there than it is to start from generalized code and working your way backwards end hopefully we ve all learned something from this one thing i noticed is that often times i see indie developers with amazing games but by all normal standards if you were to look at their code they would be considered bad coders who just don t know any good practices i think intuitively people realize that doing things like what i outlined in this article is a good idea and so you get lots of dumb code that works it s important to understand that if you re able to analyze these tradeoffs properly you can make informed decisions about how to engage in those dumb activities while decreasing the overall costs of making whatever you want to make also don t let other people bully you into proper code and tell you your code is dumb tell them they re dumb instead and that their code is even dumber and that they should be ashamed of trying to shame you and tell them undertale has dumb code so it s okay to have dumb code too look img src | 0 |
65,017 | 14,708,415,850 | IssuesEvent | 2021-01-04 23:39:01 | SmartBear/readyapi-testengine-maven-plugin | https://api.github.com/repos/SmartBear/readyapi-testengine-maven-plugin | opened | CVE-2019-14540 (High) detected in jackson-databind-2.9.10.jar | security vulnerability | ## CVE-2019-14540 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.10.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: readyapi-testengine-maven-plugin/pom.xml</p>
<p>Path to vulnerable library: canner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.10/jackson-databind-2.9.10.jar</p>
<p>
Dependency Hierarchy:
- :x: **jackson-databind-2.9.10.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/SmartBear/readyapi-testengine-maven-plugin/commit/d0981d735a777d1527cbd9a85bc57b01302d04f7">d0981d735a777d1527cbd9a85bc57b01302d04f7</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10. It is related to com.zaxxer.hikari.HikariConfig.
<p>Publish Date: 2019-09-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-14540>CVE-2019-14540</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14540">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14540</a></p>
<p>Release Date: 2019-09-15</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.8.11.5,2.9.10,2.10.0.pr3,2.11.0.rc1</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"com.fasterxml.jackson.core","packageName":"jackson-databind","packageVersion":"2.9.10","isTransitiveDependency":false,"dependencyTree":"com.fasterxml.jackson.core:jackson-databind:2.9.10","isMinimumFixVersionAvailable":true,"minimumFixVersion":"com.fasterxml.jackson.core:jackson-databind:2.8.11.5,2.9.10,2.10.0.pr3,2.11.0.rc1"}],"vulnerabilityIdentifier":"CVE-2019-14540","vulnerabilityDetails":"A Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10. It is related to com.zaxxer.hikari.HikariConfig.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-14540","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2019-14540 (High) detected in jackson-databind-2.9.10.jar - ## CVE-2019-14540 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.10.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: readyapi-testengine-maven-plugin/pom.xml</p>
<p>Path to vulnerable library: canner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.10/jackson-databind-2.9.10.jar</p>
<p>
Dependency Hierarchy:
- :x: **jackson-databind-2.9.10.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/SmartBear/readyapi-testengine-maven-plugin/commit/d0981d735a777d1527cbd9a85bc57b01302d04f7">d0981d735a777d1527cbd9a85bc57b01302d04f7</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10. It is related to com.zaxxer.hikari.HikariConfig.
<p>Publish Date: 2019-09-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-14540>CVE-2019-14540</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14540">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14540</a></p>
<p>Release Date: 2019-09-15</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.8.11.5,2.9.10,2.10.0.pr3,2.11.0.rc1</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"com.fasterxml.jackson.core","packageName":"jackson-databind","packageVersion":"2.9.10","isTransitiveDependency":false,"dependencyTree":"com.fasterxml.jackson.core:jackson-databind:2.9.10","isMinimumFixVersionAvailable":true,"minimumFixVersion":"com.fasterxml.jackson.core:jackson-databind:2.8.11.5,2.9.10,2.10.0.pr3,2.11.0.rc1"}],"vulnerabilityIdentifier":"CVE-2019-14540","vulnerabilityDetails":"A Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10. It is related to com.zaxxer.hikari.HikariConfig.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-14540","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | non_priority | cve high detected in jackson databind jar cve high severity vulnerability vulnerable library jackson databind jar general data binding functionality for jackson works on core streaming api library home page a href path to dependency file readyapi testengine maven plugin pom xml path to vulnerable library canner repository com fasterxml jackson core jackson databind jackson databind jar dependency hierarchy x jackson databind jar vulnerable library found in head commit a href found in base branch master vulnerability details a polymorphic typing issue was discovered in fasterxml jackson databind before it is related to com zaxxer hikari hikariconfig publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution com fasterxml jackson core jackson databind check this box to open an automated fix pr isopenpronvulnerability false ispackagebased true isdefaultbranch true packages vulnerabilityidentifier cve vulnerabilitydetails a polymorphic typing issue was discovered in fasterxml jackson databind before it is related to com zaxxer hikari hikariconfig vulnerabilityurl | 0 |
43,856 | 11,868,217,940 | IssuesEvent | 2020-03-26 08:46:26 | phingofficial/phing | https://api.github.com/repos/phingofficial/phing | closed | Optional tasks depend on obsolete software | PHP compat defect dependencies ext tasks feedback | Phing 3.0.0-alpha3
PHP 7.3.12
Many optional tasks depend (see "3.1.2 Software Dependencies" in documentation) on PEAR which is obsolete now. It makes some troubles. For example, if I use "FtpDeployTask" and install somehow Net_FTP package then I've got errors:
```
[PHP Error] Methods with the same name as their class will not be constructors in a future version of PHP; Net_FTP has a deprecated constructor [line 556 of D:\somepath\Lib\Net\FTP.php]
[PHP Error] define(): Declaration of case-insensitive constants is deprecated [line 34 of D:\somepath\Lib\Net\FTP.php]
[PHP Error] define(): Declaration of case-insensitive constants is deprecated [line 43 of D:\somepath\Lib\Net\FTP.php]
[PHP Error] define(): Declaration of case-insensitive constants is deprecated [line 52 of D:\somepath\Lib\Net\FTP.php]
[PHP Error] define(): Declaration of case-insensitive constants is deprecated [line 61 of D:\somepath\Lib\Net\FTP.php]
[PHP Error] define(): Declaration of case-insensitive constants is deprecated [line 71 of D:\somepath\Lib\Net\FTP.php]
[PHP Error] define(): Declaration of case-insensitive constants is deprecated [line 83 of D:\somepath\Lib\Net\FTP.php]
```
So actually it does not work. Is there any way to really use tasks depending on PEAR? If not then trouble must be at least documented. | 1.0 | Optional tasks depend on obsolete software - Phing 3.0.0-alpha3
PHP 7.3.12
Many optional tasks depend (see "3.1.2 Software Dependencies" in documentation) on PEAR which is obsolete now. It makes some troubles. For example, if I use "FtpDeployTask" and install somehow Net_FTP package then I've got errors:
```
[PHP Error] Methods with the same name as their class will not be constructors in a future version of PHP; Net_FTP has a deprecated constructor [line 556 of D:\somepath\Lib\Net\FTP.php]
[PHP Error] define(): Declaration of case-insensitive constants is deprecated [line 34 of D:\somepath\Lib\Net\FTP.php]
[PHP Error] define(): Declaration of case-insensitive constants is deprecated [line 43 of D:\somepath\Lib\Net\FTP.php]
[PHP Error] define(): Declaration of case-insensitive constants is deprecated [line 52 of D:\somepath\Lib\Net\FTP.php]
[PHP Error] define(): Declaration of case-insensitive constants is deprecated [line 61 of D:\somepath\Lib\Net\FTP.php]
[PHP Error] define(): Declaration of case-insensitive constants is deprecated [line 71 of D:\somepath\Lib\Net\FTP.php]
[PHP Error] define(): Declaration of case-insensitive constants is deprecated [line 83 of D:\somepath\Lib\Net\FTP.php]
```
So actually it does not work. Is there any way to really use tasks depending on PEAR? If not then trouble must be at least documented. | non_priority | optional tasks depend on obsolete software phing php many optional tasks depend see software dependencies in documentation on pear which is obsolete now it makes some troubles for example if i use ftpdeploytask and install somehow net ftp package then i ve got errors methods with the same name as their class will not be constructors in a future version of php net ftp has a deprecated constructor define declaration of case insensitive constants is deprecated define declaration of case insensitive constants is deprecated define declaration of case insensitive constants is deprecated define declaration of case insensitive constants is deprecated define declaration of case insensitive constants is deprecated define declaration of case insensitive constants is deprecated so actually it does not work is there any way to really use tasks depending on pear if not then trouble must be at least documented | 0 |
6,136 | 8,787,612,811 | IssuesEvent | 2018-12-20 19:15:47 | renovatebot/renovate | https://api.github.com/repos/renovatebot/renovate | opened | Add java versioning | #java feat needs-requirements pri3-normal | Based on the existing lib/versioning/loose implementation, we want a java-specific one for Gradle and Maven. Particularly, it needs to answer correctly for stable vs unstable, so that versions like 1.2.3.Release are not classified as unstable.
Let's gather requirements here first.
Cc @JamieMagee @corecanarias | 1.0 | Add java versioning - Based on the existing lib/versioning/loose implementation, we want a java-specific one for Gradle and Maven. Particularly, it needs to answer correctly for stable vs unstable, so that versions like 1.2.3.Release are not classified as unstable.
Let's gather requirements here first.
Cc @JamieMagee @corecanarias | non_priority | add java versioning based on the existing lib versioning loose implementation we want a java specific one for gradle and maven particularly it needs to answer correctly for stable vs unstable so that versions like release are not classified as unstable let s gather requirements here first cc jamiemagee corecanarias | 0 |
14,754 | 9,478,246,342 | IssuesEvent | 2019-04-19 21:52:02 | openstreetmap/iD | https://api.github.com/repos/openstreetmap/iD | closed | Add a hotkey to toggle the OSM data layer | usability | Even in wireframe mode the OSM data can obscure too much of the background imagery:
<img width="772" alt="Screen Shot 2019-03-25 at 5 46 41 PM" src="https://user-images.githubusercontent.com/2046746/54957591-89765d80-4f29-11e9-8b79-945738fa928a.png">
While the user can open the Map Data pane to turn off the layer, it'd be easier if there were a shortcut to quickly toggle the data. I recommend a two-key combination such as Cmd+W to reduce users accidentally turning off all data and no knowing what to do. | True | Add a hotkey to toggle the OSM data layer - Even in wireframe mode the OSM data can obscure too much of the background imagery:
<img width="772" alt="Screen Shot 2019-03-25 at 5 46 41 PM" src="https://user-images.githubusercontent.com/2046746/54957591-89765d80-4f29-11e9-8b79-945738fa928a.png">
While the user can open the Map Data pane to turn off the layer, it'd be easier if there were a shortcut to quickly toggle the data. I recommend a two-key combination such as Cmd+W to reduce users accidentally turning off all data and no knowing what to do. | non_priority | add a hotkey to toggle the osm data layer even in wireframe mode the osm data can obscure too much of the background imagery img width alt screen shot at pm src while the user can open the map data pane to turn off the layer it d be easier if there were a shortcut to quickly toggle the data i recommend a two key combination such as cmd w to reduce users accidentally turning off all data and no knowing what to do | 0 |
81,700 | 31,390,914,141 | IssuesEvent | 2023-08-26 10:25:51 | nats-io/nats-server | https://api.github.com/repos/nats-io/nats-server | opened | HTTP headers are not set for the monitoring server when the status is not 200 OK | defect | ### What version were you using?
nats-server: v2.9.21
### What environment was the server running in?
Linux amd64
### Is this defect reproducible?
All the monitoring server endpoints return `http.StatusOK` except the `/healthz` endpoint when the health check fails.
Requests made to the `/healthz` endpoint when the health check fails will receive responses with the default HTTP headers, for example the `Content-Type` header will be set to the value `text/plain; charset=utf-8` instead of `application/json` and `application/javascript` for JSONP.
This is happening because setting the headers on an `http.ResponseWriter` has no effect after setting the status code with `ResponseWriter.WriteHeader`.
The function [`ResponseHandler()`](https://github.com/mdawar/nats-server/blob/5b18e80d424926eca48091c6eb2e2a56fdffdc5d/server/monitor.go#L2305) sets the headers, but when the health check fails, the function [`HandleHealthz()`](https://github.com/mdawar/nats-server/blob/5b18e80d424926eca48091c6eb2e2a56fdffdc5d/server/monitor.go#L3080) calls `WriteHeader()` before calling `ResponseHandler()` which causes this issue.
I will add tests that reproduce this issue in a pull request.
### Given the capability you are leveraging, describe your expectation?
The HTTP headers for the `/healthz` endpoint should be set properly when the health check fails.
### Given the expectation, what is the defect you are observing?
Setting the headers has no effect after calling `ResponseWriter.WriteHeader()`. | 1.0 | HTTP headers are not set for the monitoring server when the status is not 200 OK - ### What version were you using?
nats-server: v2.9.21
### What environment was the server running in?
Linux amd64
### Is this defect reproducible?
All the monitoring server endpoints return `http.StatusOK` except the `/healthz` endpoint when the health check fails.
Requests made to the `/healthz` endpoint when the health check fails will receive responses with the default HTTP headers, for example the `Content-Type` header will be set to the value `text/plain; charset=utf-8` instead of `application/json` and `application/javascript` for JSONP.
This is happening because setting the headers on an `http.ResponseWriter` has no effect after setting the status code with `ResponseWriter.WriteHeader`.
The function [`ResponseHandler()`](https://github.com/mdawar/nats-server/blob/5b18e80d424926eca48091c6eb2e2a56fdffdc5d/server/monitor.go#L2305) sets the headers, but when the health check fails, the function [`HandleHealthz()`](https://github.com/mdawar/nats-server/blob/5b18e80d424926eca48091c6eb2e2a56fdffdc5d/server/monitor.go#L3080) calls `WriteHeader()` before calling `ResponseHandler()` which causes this issue.
I will add tests that reproduce this issue in a pull request.
### Given the capability you are leveraging, describe your expectation?
The HTTP headers for the `/healthz` endpoint should be set properly when the health check fails.
### Given the expectation, what is the defect you are observing?
Setting the headers has no effect after calling `ResponseWriter.WriteHeader()`. | non_priority | http headers are not set for the monitoring server when the status is not ok what version were you using nats server what environment was the server running in linux is this defect reproducible all the monitoring server endpoints return http statusok except the healthz endpoint when the health check fails requests made to the healthz endpoint when the health check fails will receive responses with the default http headers for example the content type header will be set to the value text plain charset utf instead of application json and application javascript for jsonp this is happening because setting the headers on an http responsewriter has no effect after setting the status code with responsewriter writeheader the function sets the headers but when the health check fails the function calls writeheader before calling responsehandler which causes this issue i will add tests that reproduce this issue in a pull request given the capability you are leveraging describe your expectation the http headers for the healthz endpoint should be set properly when the health check fails given the expectation what is the defect you are observing setting the headers has no effect after calling responsewriter writeheader | 0 |
80,388 | 15,398,292,804 | IssuesEvent | 2021-03-03 23:43:46 | mozilla/fxa | https://api.github.com/repos/mozilla/fxa | closed | Refactor authentication states | code_quality fxa-auth-server needs:discussion | In the past couple of weeks we have seen a couple instances where our `unverified` and `verified` session states have cause some confusion with our users, ref https://github.com/mozilla/fxa-content-server/issues/6767.
With the introduction of TOTP, we started to manually performed checks on our [routes](https://github.com/mozilla/fxa-auth-server/blob/ba011c7e537c5a91062ac8fe3240a6b9c6c70254/lib/routes/account.js#L1234) to see if the current session was verified with TOTP and then decided to let the user proceed.
ISTM that we should have levels of verification similar to the AAL levels and then have the routes define the level it needs. We currently keep track of the supported authentication methods [here](https://github.com/mozilla/fxa-auth-server/blob/ba27d4101ddc93722458abea37f3eae4b1b7ea21/lib/authMethods.js#L39).
Some improvement/refactoring that could be done:
* Add/Update auth strategy,
* `unverifiedSessionToken` - Route does not require session to be verified
* `sessionToken` - Requires the maximum verification level that the account supports
* https://github.com/mozilla/fxa-auth-server/blob/ba27d4101ddc93722458abea37f3eae4b1b7ea21/lib/server.js#L194
* Store supported account authentication state in session token
* https://github.com/mozilla/fxa-auth-server/blob/ba27d4101ddc93722458abea37f3eae4b1b7ea21/lib/tokens/session_token.js#L50
* Update required routes to use new strategy
* Update our `unverified` error messaging to say something along the lines that session does not have correct security permissions to complete request and to re-login.
┆Issue is synchronized with this [Jira Task](https://jira.mozilla.com/browse/FXA-656)
┆Issue Number: FXA-656
| 1.0 | Refactor authentication states - In the past couple of weeks we have seen a couple instances where our `unverified` and `verified` session states have cause some confusion with our users, ref https://github.com/mozilla/fxa-content-server/issues/6767.
With the introduction of TOTP, we started to manually performed checks on our [routes](https://github.com/mozilla/fxa-auth-server/blob/ba011c7e537c5a91062ac8fe3240a6b9c6c70254/lib/routes/account.js#L1234) to see if the current session was verified with TOTP and then decided to let the user proceed.
ISTM that we should have levels of verification similar to the AAL levels and then have the routes define the level it needs. We currently keep track of the supported authentication methods [here](https://github.com/mozilla/fxa-auth-server/blob/ba27d4101ddc93722458abea37f3eae4b1b7ea21/lib/authMethods.js#L39).
Some improvement/refactoring that could be done:
* Add/Update auth strategy,
* `unverifiedSessionToken` - Route does not require session to be verified
* `sessionToken` - Requires the maximum verification level that the account supports
* https://github.com/mozilla/fxa-auth-server/blob/ba27d4101ddc93722458abea37f3eae4b1b7ea21/lib/server.js#L194
* Store supported account authentication state in session token
* https://github.com/mozilla/fxa-auth-server/blob/ba27d4101ddc93722458abea37f3eae4b1b7ea21/lib/tokens/session_token.js#L50
* Update required routes to use new strategy
* Update our `unverified` error messaging to say something along the lines that session does not have correct security permissions to complete request and to re-login.
┆Issue is synchronized with this [Jira Task](https://jira.mozilla.com/browse/FXA-656)
┆Issue Number: FXA-656
| non_priority | refactor authentication states in the past couple of weeks we have seen a couple instances where our unverified and verified session states have cause some confusion with our users ref with the introduction of totp we started to manually performed checks on our to see if the current session was verified with totp and then decided to let the user proceed istm that we should have levels of verification similar to the aal levels and then have the routes define the level it needs we currently keep track of the supported authentication methods some improvement refactoring that could be done add update auth strategy unverifiedsessiontoken route does not require session to be verified sessiontoken requires the maximum verification level that the account supports store supported account authentication state in session token update required routes to use new strategy update our unverified error messaging to say something along the lines that session does not have correct security permissions to complete request and to re login ┆issue is synchronized with this ┆issue number fxa | 0 |
331,864 | 29,145,134,545 | IssuesEvent | 2023-05-18 01:43:58 | jyao1/rust-spdm | https://api.github.com/repos/jyao1/rust-spdm | closed | enable cargo fuzz (libfuzzer) for fuzzing | test | Once this is enabled, we can change afl -> libfuzzer in CI. | 1.0 | enable cargo fuzz (libfuzzer) for fuzzing - Once this is enabled, we can change afl -> libfuzzer in CI. | non_priority | enable cargo fuzz libfuzzer for fuzzing once this is enabled we can change afl libfuzzer in ci | 0 |
94,919 | 27,329,101,698 | IssuesEvent | 2023-02-25 11:45:59 | projectnessie/nessie | https://api.github.com/repos/projectnessie/nessie | closed | Failed to generate Jacoco reports: EOFException at `ExecutionDataReader.readExecutionData` | build | Running `./gradlew test`:
```
> Task :nessie-quarkus-cli:test
Failed to generate Jacoco reports
java.io.EOFException
at java.base/java.io.DataInputStream.readUnsignedShort(DataInputStream.java:345)
at java.base/java.io.DataInputStream.readUTF(DataInputStream.java:594)
at java.base/java.io.DataInputStream.readUTF(DataInputStream.java:569)
at org.jacoco.core.data.ExecutionDataReader.readExecutionData(ExecutionDataReader.java:149)
at org.jacoco.core.data.ExecutionDataReader.readBlock(ExecutionDataReader.java:116)
at org.jacoco.core.data.ExecutionDataReader.read(ExecutionDataReader.java:93)
at org.jacoco.core.tools.ExecFileLoader.load(ExecFileLoader.java:60)
at org.jacoco.core.tools.ExecFileLoader.load(ExecFileLoader.java:74)
at io.quarkus.jacoco.runtime.ReportCreator.run(ReportCreator.java:72)
at java.base/java.lang.Thread.run(Thread.java:829)
Failed to generate Jacoco reports
java.io.EOFException
at java.base/java.io.DataInputStream.readByte(DataInputStream.java:272)
at org.jacoco.core.internal.data.CompactDataInput.readBooleanArray(CompactDataInput.java:64)
at org.jacoco.core.data.ExecutionDataReader.readExecutionData(ExecutionDataReader.java:150)
at org.jacoco.core.data.ExecutionDataReader.readBlock(ExecutionDataReader.java:116)
at org.jacoco.core.data.ExecutionDataReader.read(ExecutionDataReader.java:93)
at org.jacoco.core.tools.ExecFileLoader.load(ExecFileLoader.java:60)
at org.jacoco.core.tools.ExecFileLoader.load(ExecFileLoader.java:74)
at io.quarkus.jacoco.runtime.ReportCreator.run(ReportCreator.java:72)
at java.base/java.lang.Thread.run(Thread.java:829)
``` | 1.0 | Failed to generate Jacoco reports: EOFException at `ExecutionDataReader.readExecutionData` - Running `./gradlew test`:
```
> Task :nessie-quarkus-cli:test
Failed to generate Jacoco reports
java.io.EOFException
at java.base/java.io.DataInputStream.readUnsignedShort(DataInputStream.java:345)
at java.base/java.io.DataInputStream.readUTF(DataInputStream.java:594)
at java.base/java.io.DataInputStream.readUTF(DataInputStream.java:569)
at org.jacoco.core.data.ExecutionDataReader.readExecutionData(ExecutionDataReader.java:149)
at org.jacoco.core.data.ExecutionDataReader.readBlock(ExecutionDataReader.java:116)
at org.jacoco.core.data.ExecutionDataReader.read(ExecutionDataReader.java:93)
at org.jacoco.core.tools.ExecFileLoader.load(ExecFileLoader.java:60)
at org.jacoco.core.tools.ExecFileLoader.load(ExecFileLoader.java:74)
at io.quarkus.jacoco.runtime.ReportCreator.run(ReportCreator.java:72)
at java.base/java.lang.Thread.run(Thread.java:829)
Failed to generate Jacoco reports
java.io.EOFException
at java.base/java.io.DataInputStream.readByte(DataInputStream.java:272)
at org.jacoco.core.internal.data.CompactDataInput.readBooleanArray(CompactDataInput.java:64)
at org.jacoco.core.data.ExecutionDataReader.readExecutionData(ExecutionDataReader.java:150)
at org.jacoco.core.data.ExecutionDataReader.readBlock(ExecutionDataReader.java:116)
at org.jacoco.core.data.ExecutionDataReader.read(ExecutionDataReader.java:93)
at org.jacoco.core.tools.ExecFileLoader.load(ExecFileLoader.java:60)
at org.jacoco.core.tools.ExecFileLoader.load(ExecFileLoader.java:74)
at io.quarkus.jacoco.runtime.ReportCreator.run(ReportCreator.java:72)
at java.base/java.lang.Thread.run(Thread.java:829)
``` | non_priority | failed to generate jacoco reports eofexception at executiondatareader readexecutiondata running gradlew test task nessie quarkus cli test failed to generate jacoco reports java io eofexception at java base java io datainputstream readunsignedshort datainputstream java at java base java io datainputstream readutf datainputstream java at java base java io datainputstream readutf datainputstream java at org jacoco core data executiondatareader readexecutiondata executiondatareader java at org jacoco core data executiondatareader readblock executiondatareader java at org jacoco core data executiondatareader read executiondatareader java at org jacoco core tools execfileloader load execfileloader java at org jacoco core tools execfileloader load execfileloader java at io quarkus jacoco runtime reportcreator run reportcreator java at java base java lang thread run thread java failed to generate jacoco reports java io eofexception at java base java io datainputstream readbyte datainputstream java at org jacoco core internal data compactdatainput readbooleanarray compactdatainput java at org jacoco core data executiondatareader readexecutiondata executiondatareader java at org jacoco core data executiondatareader readblock executiondatareader java at org jacoco core data executiondatareader read executiondatareader java at org jacoco core tools execfileloader load execfileloader java at org jacoco core tools execfileloader load execfileloader java at io quarkus jacoco runtime reportcreator run reportcreator java at java base java lang thread run thread java | 0 |
15,661 | 20,203,538,128 | IssuesEvent | 2022-02-11 17:36:09 | safing/portmaster | https://api.github.com/repos/safing/portmaster | reopened | Compatibility with Cisco Secure Endpoint (Cisco AMP) | in/compatibility backlog docs ✓ waiting for resources | **Pre-Submit Checklist**:
- Check applicable sources for existing issues:
- (N/A) [Linux Compatibility](https://docs.safing.io/portmaster/install/linux#compatibility)
- (N/A) [VPN Compatibility](https://docs.safing.io/portmaster/install/status/vpn-compatibility)
- [x] [Github Issues](https://github.com/safing/portmaster/issues?q=is%3Aissue+label%3Ain%2Fcompatibility)
**What worked?**
The portmaster UI and Core service launch. The portmaster also correctly identifies the network traffic by DNS name. As far as i can tell all connections displayed are accurate.
**What did not work?**
Blocked domains are not successfully blocked, furthermore DNS resolution takes an exponentially longer time then without the portmaster installed. Possibly timing out before resorting back to the Cisco Secure endpoint. After an restart of the Core Service no network traffic is allowed anymore, and after shutting down the portmaster everything starts working again. When trying to start the portmaster back up again the core service won't start. unless killing it completely and starting it back up again.
Rebooting doesn't work, killing the Cisco processes seems to work but it forces itself back up again, thus killing the network connection.
The following three errors are shown:
* Detected System DNS Client Bypass Attempt;
* Something is interfering with the Portmaster;
* Limited network connectivity.
I feel like for now it is best to consider Cisco Secure Endpoint as incompatible. At least on windows.
**Debug Information**:
<details>
<summary>Version 0.7.12</summary>
```
Portmaster
version 0.7.12
commit tags/v0.7.12-0-g466210b6134216054111af2f2bc0740a07e783b6
built with go1.15.8 (gc) windows/amd64
using options main.go
by user@docker
on 16.12.2021
Licensed under the AGPLv3 license.
The source code is available here: https://github.com/safing/portmaster
```
</details>
<details>
<summary>Platform: Microsoft Windows 10 Enterprise 10.0.19044 Build 19044</summary>
```
System: Microsoft Windows 10 Enterprise windows (Standalone Workstation) 10.0.19044 Build 19044
Kernel: 10.0.19044 Build 19044 x86_64
```
</details>
<details>
<summary>Status: Trusted</summary>
```
ActiveSecurityLevel: Trusted
SelectedSecurityLevel: Off
ThreatMitigationLevel: Trusted
CaptivePortal:
OnlineStatus: Limited
```
</details>
<details>
<summary>Resolvers: 1/1</summary>
```
Cloudflare
dot://1.1.1.2:853#config
Failing: false
```
</details>
<details>
<summary>Compat Module Error</summary>
```
Message: self-check #2: dns integration check failed: did not receive test query after 3s
Timestamp: 2021-12-22 22:10:59.8241517 +0100 CET m=+117.862369101
ModuleName: compat
TaskName: selfcheck
TaskType:
Severity: error
PanicValue: %!s(<nil>)
StackTrace:
goroutine 3097 [running]:
runtime/debug.Stack(0xc000010730, 0xc0007f7a90, 0x50)
/usr/local/go/src/runtime/debug/stack.go:24 +0xa5
github.com/safing/portbase/modules.(*Module).NewErrorMessage(0xc0001bb040, 0x144fd05, 0x9, 0x1550860, 0xc000010730, 0x58)
/home/user/git/safing/portbase/modules/error.go:48 +0x58
github.com/safing/portmaster/compat.(*systemIssue).notify(0x19da6c0, 0x1550860, 0xc000010730)
/home/user/git/safing/portmaster/compat/notify.go:89 +0x1ac
github.com/safing/portmaster/compat.selfcheckTaskFunc(0x1562a60, 0xc00065ddc0, 0xc0007a07e0, 0x0, 0x0)
/home/user/git/safing/portmaster/compat/module.go:85 +0x16b
github.com/safing/portbase/modules.(*Task).executeWithLocking(0xc0007a07e0)
/home/user/git/safing/portbase/modules/tasks.go:369 +0x94
created by github.com/safing/portbase/modules.(*Task).runWithLocking
/home/user/git/safing/portbase/modules/tasks.go:318 +0x285
```
</details>
<details>
<summary>Unexpected Logs</summary>
```
211222 22:09:34.587 ine-status:509 > WARN 108 netenv: dns check query failed: lookup one.one.one.one.: no such host
211222 22:09:34.587 ine-status:523 > WARN 110 netenv: dns fallback check query failed: lookup dns-check.safing.io.: no such host
211222 22:09:51.691 ine-status:509 > WARN 129 netenv: dns check query failed: lookup one.one.one.one.: no such host
211222 22:10:02.768 ine-status:523 > WARN 141 netenv: dns fallback check query failed: lookup dns-check.safing.io.: no such host
211222 22:10:15.815 ine-status:509 > WARN 183 netenv: dns check query failed: lookup one.one.one.one.: no such host
211222 22:10:26.973 pat/module:083 > ERRO 199 compat: self-check #2: dns integration check failed: did not receive test query after 3s
211222 22:10:27.860 ine-status:523 > WARN 201 netenv: dns fallback check query failed: lookup dns-check.safing.io.: no such host
211222 22:10:40.926 ine-status:509 > WARN 212 netenv: dns check query failed: lookup one.one.one.one.: no such host
211222 22:10:52.982 ine-status:523 > WARN 228 netenv: dns fallback check query failed: lookup dns-check.safing.io.: no such host
211222 22:10:57.543 pat/module:083 > ERRO 233 compat: self-check #2: dns integration check failed: did not receive test query after 3s
211222 22:10:59.824 CURRENT TIME
```
</details>
<details>
<summary>Goroutine Stack</summary>
```
goroutine profile: total 2259
1630 @ 0xb9de1a 0xbae7f7 0xbae7e2 0xbcabc9 0xbde9eb 0x11bf235 0x12b08d5 0x12b05ea 0x12b8b8e 0xf1adc7 0xf1a4de 0xf1cbc5 0xbcfba1
# 0xbcabc8 sync.runtime_Semacquire+0x48 /usr/local/go/src/runtime/sema.go:56
# 0xbde9ea sync.(*WaitGroup).Wait+0x6a /usr/local/go/src/sync/waitgroup.go:130
# 0x11bf234 golang.org/x/sync/singleflight.(*Group).Do+0x1f4 /home/user/go/pkg/mod/golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c/singleflight/singleflight.go:94
# 0x12b08d4 github.com/safing/portmaster/firewall.getConnection+0xd4 /home/user/git/safing/portmaster/firewall/interception.go:130
# 0x12b05e9 github.com/safing/portmaster/firewall.handlePacket+0x1c9 /home/user/git/safing/portmaster/firewall/interception.go:113
# 0x12b8b8d github.com/safing/portmaster/firewall.packetHandler.func1+0x4d /home/user/git/safing/portmaster/firewall/interception.go:527
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf1cbc4 github.com/safing/portbase/modules.(*Module).StartWorker.func1+0x64 /home/user/git/safing/portbase/modules/worker.go:27
502 @ 0xb9de1a 0xbae7f7 0xbae7e2 0xbcacee 0x11b8c93 0x11b8c45 0x11c3259 0x11c2b8b 0x11c0bea 0x1273377 0x12b8ae5 0x11bf889 0x11bf425 0x11bf194 0x12b08d5 0x12b05ea 0x12b8b8e 0xf1adc7 0xf1a4de 0xf1cbc5 0xbcfba1
# 0xbcaced sync.runtime_SemacquireMutex+0x4d /usr/local/go/src/runtime/sema.go:71
# 0x11b8c92 sync.(*RWMutex).RLock+0xb2 /usr/local/go/src/sync/rwmutex.go:50
# 0x11b8c44 github.com/safing/portmaster/profile.(*LayeredProfile).LocalProfile+0x64 /home/user/git/safing/portmaster/profile/profile-layered.go:162
# 0x11c3258 github.com/safing/portmaster/process.(*Process).UpdateProfileMetadata+0x58 /home/user/git/safing/portmaster/process/profile.go:102
# 0x11c2b8a github.com/safing/portmaster/process.(*Process).GetProfile+0x12a /home/user/git/safing/portmaster/process/profile.go:28
# 0x11c0be9 github.com/safing/portmaster/process.GetProcessByConnection+0x3a9 /home/user/git/safing/portmaster/process/find.go:40
# 0x1273376 github.com/safing/portmaster/network.NewConnectionFromFirstPacket+0xb6 /home/user/git/safing/portmaster/network/connection.go:320
# 0x12b8ae4 github.com/safing/portmaster/firewall.getConnection.func1+0xa4 /home/user/git/safing/portmaster/firewall/interception.go:138
# 0x11bf888 golang.org/x/sync/singleflight.(*Group).doCall.func2+0x68 /home/user/go/pkg/mod/golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c/singleflight/singleflight.go:193
# 0x11bf424 golang.org/x/sync/singleflight.(*Group).doCall+0xc4 /home/user/go/pkg/mod/golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c/singleflight/singleflight.go:195
# 0x11bf193 golang.org/x/sync/singleflight.(*Group).Do+0x153 /home/user/go/pkg/mod/golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c/singleflight/singleflight.go:108
# 0x12b08d4 github.com/safing/portmaster/firewall.getConnection+0xd4 /home/user/git/safing/portmaster/firewall/interception.go:130
# 0x12b05e9 github.com/safing/portmaster/firewall.handlePacket+0x1c9 /home/user/git/safing/portmaster/firewall/interception.go:113
# 0x12b8b8d github.com/safing/portmaster/firewall.packetHandler.func1+0x4d /home/user/git/safing/portmaster/firewall/interception.go:527
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf1cbc4 github.com/safing/portbase/modules.(*Module).StartWorker.func1+0x64 /home/user/git/safing/portbase/modules/worker.go:27
51 @ 0xb9de1a 0xbae7f7 0xbae7e2 0xbcacee 0xbdce2f 0x11c31b2 0x11c2ae6 0x11c0bea 0x1273377 0x12b8ae5 0x11bf889 0x11bf425 0x11bf194 0x12b08d5 0x12b05ea 0x12b8b8e 0xf1adc7 0xf1a4de 0xf1cbc5 0xbcfba1
# 0xbcaced sync.runtime_SemacquireMutex+0x4d /usr/local/go/src/runtime/sema.go:71
# 0xbdce2e sync.(*Mutex).lockSlow+0x10e /usr/local/go/src/sync/mutex.go:138
# 0x11c31b1 sync.(*Mutex).Lock+0x751 /usr/local/go/src/sync/mutex.go:81
# 0x11c2ae5 github.com/safing/portmaster/process.(*Process).GetProfile+0x85 /home/user/git/safing/portmaster/process/profile.go:22
# 0x11c0be9 github.com/safing/portmaster/process.GetProcessByConnection+0x3a9 /home/user/git/safing/portmaster/process/find.go:40
# 0x1273376 github.com/safing/portmaster/network.NewConnectionFromFirstPacket+0xb6 /home/user/git/safing/portmaster/network/connection.go:320
# 0x12b8ae4 github.com/safing/portmaster/firewall.getConnection.func1+0xa4 /home/user/git/safing/portmaster/firewall/interception.go:138
# 0x11bf888 golang.org/x/sync/singleflight.(*Group).doCall.func2+0x68 /home/user/go/pkg/mod/golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c/singleflight/singleflight.go:193
# 0x11bf424 golang.org/x/sync/singleflight.(*Group).doCall+0xc4 /home/user/go/pkg/mod/golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c/singleflight/singleflight.go:195
# 0x11bf193 golang.org/x/sync/singleflight.(*Group).Do+0x153 /home/user/go/pkg/mod/golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c/singleflight/singleflight.go:108
# 0x12b08d4 github.com/safing/portmaster/firewall.getConnection+0xd4 /home/user/git/safing/portmaster/firewall/interception.go:130
# 0x12b05e9 github.com/safing/portmaster/firewall.handlePacket+0x1c9 /home/user/git/safing/portmaster/firewall/interception.go:113
# 0x12b8b8d github.com/safing/portmaster/firewall.packetHandler.func1+0x4d /home/user/git/safing/portmaster/firewall/interception.go:527
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf1cbc4 github.com/safing/portbase/modules.(*Module).StartWorker.func1+0x64 /home/user/git/safing/portbase/modules/worker.go:27
11 @ 0xb9de1a 0xbade2f 0xf59b65 0xf5a1d7 0xbcfba1
# 0xf59b64 github.com/safing/portbase/api.(*DatabaseAPI).processSub+0x224 /home/user/git/safing/portbase/api/database.go:415
# 0xf5a1d6 github.com/safing/portbase/api.(*DatabaseAPI).handleQsub+0x136 /home/user/git/safing/portbase/api/database.go:478
8 @ 0xb9de1a 0xbade2f 0x124bc6a 0xbcfba1
# 0x124bc69 github.com/xtaci/kcp-go/v5.(*TimedSched).sched+0x2c9 /home/user/go/pkg/mod/github.com/xtaci/kcp-go/v5@v5.6.1/timedsched.go:67
4 @ 0xb9de1a 0xbae7f7 0xbae7e2 0xbcacee 0xbdce2f 0xbde5b5 0xbde549 0x11bb897 0x11c2d25 0x11c0bea 0x1273377 0x12b8ae5 0x11bf889 0x11bf425 0x11bf194 0x12b08d5 0x12b05ea 0x12b8b8e 0xf1adc7 0xf1a4de 0xf1cbc5 0xbcfba1
# 0xbcaced sync.runtime_SemacquireMutex+0x4d /usr/local/go/src/runtime/sema.go:71
# 0xbdce2e sync.(*Mutex).lockSlow+0x10e /usr/local/go/src/sync/mutex.go:138
# 0xbde5b4 sync.(*Mutex).Lock+0x94 /usr/local/go/src/sync/mutex.go:81
# 0xbde548 sync.(*RWMutex).Lock+0x28 /usr/local/go/src/sync/rwmutex.go:98
# 0x11bb896 github.com/safing/portmaster/profile.(*Profile).LayeredProfile+0x56 /home/user/git/safing/portmaster/profile/profile.go:406
# 0x11c2d24 github.com/safing/portmaster/process.(*Process).GetProfile+0x2c4 /home/user/git/safing/portmaster/process/profile.go:93
# 0x11c0be9 github.com/safing/portmaster/process.GetProcessByConnection+0x3a9 /home/user/git/safing/portmaster/process/find.go:40
# 0x1273376 github.com/safing/portmaster/network.NewConnectionFromFirstPacket+0xb6 /home/user/git/safing/portmaster/network/connection.go:320
# 0x12b8ae4 github.com/safing/portmaster/firewall.getConnection.func1+0xa4 /home/user/git/safing/portmaster/firewall/interception.go:138
# 0x11bf888 golang.org/x/sync/singleflight.(*Group).doCall.func2+0x68 /home/user/go/pkg/mod/golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c/singleflight/singleflight.go:193
# 0x11bf424 golang.org/x/sync/singleflight.(*Group).doCall+0xc4 /home/user/go/pkg/mod/golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c/singleflight/singleflight.go:195
# 0x11bf193 golang.org/x/sync/singleflight.(*Group).Do+0x153 /home/user/go/pkg/mod/golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c/singleflight/singleflight.go:108
# 0x12b08d4 github.com/safing/portmaster/firewall.getConnection+0xd4 /home/user/git/safing/portmaster/firewall/interception.go:130
# 0x12b05e9 github.com/safing/portmaster/firewall.handlePacket+0x1c9 /home/user/git/safing/portmaster/firewall/interception.go:113
# 0x12b8b8d github.com/safing/portmaster/firewall.packetHandler.func1+0x4d /home/user/git/safing/portmaster/firewall/interception.go:527
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf1cbc4 github.com/safing/portbase/modules.(*Module).StartWorker.func1+0x64 /home/user/git/safing/portbase/modules/worker.go:27
2 @ 0xb64875 0xbcc492 0xbef9a5 0xd1f519 0xd1fdd2 0xbcfba1
# 0xbcc491 syscall.Syscall6+0xf1 /usr/local/go/src/runtime/syscall_windows.go:201
# 0xbef9a4 syscall.GetAddrInfoW+0xe4 /usr/local/go/src/syscall/zsyscall_windows.go:1718
# 0xd1f518 net.(*Resolver).lookupIP.func1+0x258 /usr/local/go/src/net/lookup_windows.go:109
# 0xd1fdd1 net.(*Resolver).lookupIP.func2+0x31 /usr/local/go/src/net/lookup_windows.go:146
2 @ 0xb9de1a 0xb93e65 0xbc9365 0xc0c30c 0xc0d645 0xc0e81f 0xd01dd6 0xd10e35 0xd9ba8a 0xd9bc16 0xf342e7 0xf3686b 0xf3793b 0xf380f6 0xf575aa 0xf1adc7 0xf1a4de 0xf1cbc5 0xbcfba1
# 0xbc9364 internal/poll.runtime_pollWait+0x64 /usr/local/go/src/runtime/netpoll.go:222
# 0xc0c30b internal/poll.(*pollDesc).wait+0x4b /usr/local/go/src/internal/poll/fd_poll_runtime.go:87
# 0xc0d644 internal/poll.execIO+0x104 /usr/local/go/src/internal/poll/fd_windows.go:175
# 0xc0e81e internal/poll.(*FD).Read+0x2fe /usr/local/go/src/internal/poll/fd_windows.go:441
# 0xd01dd5 net.(*netFD).Read+0x55 /usr/local/go/src/net/fd_posix.go:55
# 0xd10e34 net.(*conn).Read+0x94 /usr/local/go/src/net/net.go:182
# 0xd9ba89 bufio.(*Reader).fill+0x109 /usr/local/go/src/bufio/bufio.go:101
# 0xd9bc15 bufio.(*Reader).Peek+0x55 /usr/local/go/src/bufio/bufio.go:139
# 0xf342e6 github.com/gorilla/websocket.(*Conn).read+0x46 /home/user/go/pkg/mod/github.com/gorilla/websocket@v1.4.2/conn.go:370
# 0xf3686a github.com/gorilla/websocket.(*Conn).advanceFrame+0x6a /home/user/go/pkg/mod/github.com/gorilla/websocket@v1.4.2/conn.go:798
# 0xf3793a github.com/gorilla/websocket.(*Conn).NextReader+0x9a /home/user/go/pkg/mod/github.com/gorilla/websocket@v1.4.2/conn.go:980
# 0xf380f5 github.com/gorilla/websocket.(*Conn).ReadMessage+0x35 /home/user/go/pkg/mod/github.com/gorilla/websocket@v1.4.2/conn.go:1064
# 0xf575a9 github.com/safing/portbase/api.(*DatabaseAPI).handler+0x49 /home/user/git/safing/portbase/api/database.go:150
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf1cbc4 github.com/safing/portbase/modules.(*Module).StartWorker.func1+0x64 /home/user/git/safing/portbase/modules/worker.go:27
2 @ 0xb9de1a 0xbade2f 0xd0ff59 0xd1e4d9 0xd1efc2 0xcfc7b5 0xbcfba1
# 0xd0ff58 net.(*Resolver).lookupIP+0x1b8 /usr/local/go/src/net/lookup_windows.go:151
# 0xd1e4d8 net.glob..func1+0x78 /usr/local/go/src/net/hook.go:23
# 0xd1efc1 net.(*Resolver).lookupIPAddr.func1+0xc1 /usr/local/go/src/net/lookup.go:293
# 0xcfc7b4 internal/singleflight.(*Group).doCall+0x34 /usr/local/go/src/internal/singleflight/singleflight.go:95
2 @ 0xb9de1a 0xbade2f 0xf0cf78 0xf1adc7 0xf1a811 0xbcfba1
# 0xf0cf77 github.com/safing/portbase/database.(*Interface).DelayedCacheWriter+0x1d7 /home/user/git/safing/portbase/database/interface_cache.go:34
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
2 @ 0xb9de1a 0xbade2f 0xf24965 0xf1adc7 0xf1a811 0xbcfba1
# 0xf24964 github.com/safing/portbase/rng.(*Feeder).run+0x2e4 /home/user/git/safing/portbase/rng/entropy.go:119
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
2 @ 0xb9de1a 0xbade2f 0xf58085 0xf1adc7 0xf1a4de 0xf1cbc5 0xbcfba1
# 0xf58084 github.com/safing/portbase/api.(*DatabaseAPI).writer+0x124 /home/user/git/safing/portbase/api/database.go:217
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf1cbc4 github.com/safing/portbase/modules.(*Module).StartWorker.func1+0x64 /home/user/git/safing/portbase/modules/worker.go:27
2 @ 0xb9de1a 0xbade2f 0xf59b65 0xf59772 0xbcfba1
# 0xf59b64 github.com/safing/portbase/api.(*DatabaseAPI).processSub+0x224 /home/user/git/safing/portbase/api/database.go:415
# 0xf59771 github.com/safing/portbase/api.(*DatabaseAPI).handleSub+0xd1 /home/user/git/safing/portbase/api/database.go:387
2 @ 0xb9de1a 0xbae7f7 0xbae7e2 0xbcacee 0xbdce2f 0x1274d56 0x1274c96 0x12b0728 0x12b8b8e 0xf1adc7 0xf1a4de 0xf1cbc5 0xbcfba1
# 0xbcaced sync.runtime_SemacquireMutex+0x4d /usr/local/go/src/runtime/sema.go:71
# 0xbdce2e sync.(*Mutex).lockSlow+0x10e /usr/local/go/src/sync/mutex.go:138
# 0x1274d55 sync.(*Mutex).Lock+0xf5 /usr/local/go/src/sync/mutex.go:81
# 0x1274c95 github.com/safing/portmaster/network.(*Connection).HandlePacket+0x35 /home/user/git/safing/portmaster/network/connection.go:602
# 0x12b0727 github.com/safing/portmaster/firewall.handlePacket+0x307 /home/user/git/safing/portmaster/firewall/interception.go:121
# 0x12b8b8d github.com/safing/portmaster/firewall.packetHandler.func1+0x4d /home/user/git/safing/portmaster/firewall/interception.go:527
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf1cbc4 github.com/safing/portbase/modules.(*Module).StartWorker.func1+0x64 /home/user/git/safing/portbase/modules/worker.go:27
1 @ 0xb64875 0xbcc349 0xec4e1a 0x12a4f0f 0x12a3b31 0xbcfba1
# 0xbcc348 syscall.Syscall+0xe8 /usr/local/go/src/runtime/syscall_windows.go:188
# 0xec4e19 golang.org/x/sys/windows.(*Proc).Call+0x139 /home/user/go/pkg/mod/golang.org/x/sys@v0.0.0-20211124211545-fe61309f8881/windows/dll_windows.go:170
# 0x12a4f0e github.com/safing/portmaster/firewall/interception/windowskext.RecvVerdictRequest+0x16e /home/user/git/safing/portmaster/firewall/interception/windowskext/kext.go:167
# 0x12a3b30 github.com/safing/portmaster/firewall/interception/windowskext.Handler+0xb0 /home/user/git/safing/portmaster/firewall/interception/windowskext/handler.go:59
1 @ 0xb64875 0xbcc492 0xbe8b65 0xbe65ef 0xc0e751 0xc163fe 0xc163d1 0xd9dd8b 0xf7080c 0xbcfba1
# 0xbcc491 syscall.Syscall6+0xf1 /usr/local/go/src/runtime/syscall_windows.go:201
# 0xbe8b64 syscall.ReadFile+0x104 /usr/local/go/src/syscall/zsyscall_windows.go:313
# 0xbe65ee syscall.Read+0x6e /usr/local/go/src/syscall/syscall_windows.go:369
# 0xc0e750 internal/poll.(*FD).Read+0x230 /usr/local/go/src/internal/poll/fd_windows.go:427
# 0xc163fd os.(*File).read+0x7d /usr/local/go/src/os/file_posix.go:31
# 0xc163d0 os.(*File).Read+0x50 /usr/local/go/src/os/file.go:116
# 0xd9dd8a bufio.(*Scanner).Scan+0xaa /usr/local/go/src/bufio/scan.go:214
# 0xf7080b github.com/safing/portbase/run.inputSignals+0x8b /home/user/git/safing/portbase/run/main.go:116
1 @ 0xb6d053 0xbcb429 0xf6ff89 0xbcfba1
# 0xbcb428 os/signal.signal_recv+0xa8 /usr/local/go/src/runtime/sigqueue.go:147
# 0xf6ff88 os/signal.loop+0x28 /usr/local/go/src/os/signal/signal_unix.go:23
1 @ 0xb9de1a 0xb66ada 0xb6670b 0x114e4cc 0xf1adc7 0xf1a811 0xbcfba1
# 0x114e4cb github.com/safing/portmaster/resolver.listenToMDNS+0x54b /home/user/git/safing/portmaster/resolver/resolver-mdns.go:130
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xb93e65 0xbc9365 0xc0c30c 0xc0d645 0xc0e81f 0xd01dd6 0xd10e35 0x1150793 0x115ceb1 0xf1adc7 0xf1a811 0xbcfba1
# 0xbc9364 internal/poll.runtime_pollWait+0x64 /usr/local/go/src/runtime/netpoll.go:222
# 0xc0c30b internal/poll.(*pollDesc).wait+0x4b /usr/local/go/src/internal/poll/fd_poll_runtime.go:87
# 0xc0d644 internal/poll.execIO+0x104 /usr/local/go/src/internal/poll/fd_windows.go:175
# 0xc0e81e internal/poll.(*FD).Read+0x2fe /usr/local/go/src/internal/poll/fd_windows.go:441
# 0xd01dd5 net.(*netFD).Read+0x55 /usr/local/go/src/net/fd_posix.go:55
# 0xd10e34 net.(*conn).Read+0x94 /usr/local/go/src/net/net.go:182
# 0x1150792 github.com/safing/portmaster/resolver.listenForDNSPackets+0x92 /home/user/git/safing/portmaster/resolver/resolver-mdns.go:328
# 0x115ceb0 github.com/safing/portmaster/resolver.listenToMDNS.func1+0x50 /home/user/git/safing/portmaster/resolver/resolver-mdns.go:86
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xb93e65 0xbc9365 0xc0c30c 0xc0d645 0xc0e81f 0xd01dd6 0xd10e35 0x1150793 0x115cfb1 0xf1adc7 0xf1a811 0xbcfba1
# 0xbc9364 internal/poll.runtime_pollWait+0x64 /usr/local/go/src/runtime/netpoll.go:222
# 0xc0c30b internal/poll.(*pollDesc).wait+0x4b /usr/local/go/src/internal/poll/fd_poll_runtime.go:87
# 0xc0d644 internal/poll.execIO+0x104 /usr/local/go/src/internal/poll/fd_windows.go:175
# 0xc0e81e internal/poll.(*FD).Read+0x2fe /usr/local/go/src/internal/poll/fd_windows.go:441
# 0xd01dd5 net.(*netFD).Read+0x55 /usr/local/go/src/net/fd_posix.go:55
# 0xd10e34 net.(*conn).Read+0x94 /usr/local/go/src/net/net.go:182
# 0x1150792 github.com/safing/portmaster/resolver.listenForDNSPackets+0x92 /home/user/git/safing/portmaster/resolver/resolver-mdns.go:328
# 0x115cfb0 github.com/safing/portmaster/resolver.listenToMDNS.func3+0x50 /home/user/git/safing/portmaster/resolver/resolver-mdns.go:108
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xb93e65 0xbc9365 0xc0c30c 0xc0d645 0xc0e81f 0xd01dd6 0xd10e35 0x1150793 0x115d031 0xf1adc7 0xf1a811 0xbcfba1
# 0xbc9364 internal/poll.runtime_pollWait+0x64 /usr/local/go/src/runtime/netpoll.go:222
# 0xc0c30b internal/poll.(*pollDesc).wait+0x4b /usr/local/go/src/internal/poll/fd_poll_runtime.go:87
# 0xc0d644 internal/poll.execIO+0x104 /usr/local/go/src/internal/poll/fd_windows.go:175
# 0xc0e81e internal/poll.(*FD).Read+0x2fe /usr/local/go/src/internal/poll/fd_windows.go:441
# 0xd01dd5 net.(*netFD).Read+0x55 /usr/local/go/src/net/fd_posix.go:55
# 0xd10e34 net.(*conn).Read+0x94 /usr/local/go/src/net/net.go:182
# 0x1150792 github.com/safing/portmaster/resolver.listenForDNSPackets+0x92 /home/user/git/safing/portmaster/resolver/resolver-mdns.go:328
# 0x115d030 github.com/safing/portmaster/resolver.listenToMDNS.func4+0x50 /home/user/git/safing/portmaster/resolver/resolver-mdns.go:119
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xb93e65 0xbc9365 0xc0c30c 0xc0d645 0xc0e81f 0xd01dd6 0xd10e35 0xe094df 0xbcfba1
# 0xbc9364 internal/poll.runtime_pollWait+0x64 /usr/local/go/src/runtime/netpoll.go:222
# 0xc0c30b internal/poll.(*pollDesc).wait+0x4b /usr/local/go/src/internal/poll/fd_poll_runtime.go:87
# 0xc0d644 internal/poll.execIO+0x104 /usr/local/go/src/internal/poll/fd_windows.go:175
# 0xc0e81e internal/poll.(*FD).Read+0x2fe /usr/local/go/src/internal/poll/fd_windows.go:441
# 0xd01dd5 net.(*netFD).Read+0x55 /usr/local/go/src/net/fd_posix.go:55
# 0xd10e34 net.(*conn).Read+0x94 /usr/local/go/src/net/net.go:182
# 0xe094de net/http.(*connReader).backgroundRead+0x5e /usr/local/go/src/net/http/server.go:690
1 @ 0xb9de1a 0xb93e65 0xbc9365 0xc0c30c 0xc0d645 0xc0f359 0xd01f05 0xd1b425 0xd19b85 0xfbdae5 0xfa89b9 0xfa5d6a 0xfa754f 0xfa65ba 0x12c0765 0xf1adc7 0xf1a811 0xbcfba1
# 0xbc9364 internal/poll.runtime_pollWait+0x64 /usr/local/go/src/runtime/netpoll.go:222
# 0xc0c30b internal/poll.(*pollDesc).wait+0x4b /usr/local/go/src/internal/poll/fd_poll_runtime.go:87
# 0xc0d644 internal/poll.execIO+0x104 /usr/local/go/src/internal/poll/fd_windows.go:175
# 0xc0f358 internal/poll.(*FD).ReadFrom+0x118 /usr/local/go/src/internal/poll/fd_windows.go:581
# 0xd01f04 net.(*netFD).readFrom+0x64 /usr/local/go/src/net/fd_posix.go:61
# 0xd1b424 net.(*UDPConn).readFrom+0x64 /usr/local/go/src/net/udpsock_posix.go:47
# 0xd19b84 net.(*UDPConn).ReadFrom+0x64 /usr/local/go/src/net/udpsock.go:118
# 0xfbdae4 github.com/miekg/dns.ReadFromSessionUDP+0x64 /home/user/go/pkg/mod/github.com/miekg/dns@v1.1.43/udp_windows.go:19
# 0xfa89b8 github.com/miekg/dns.(*Server).readUDP+0xd8 /home/user/go/pkg/mod/github.com/miekg/dns@v1.1.43/server.go:687
# 0xfa5d69 github.com/miekg/dns.defaultReader.ReadUDP+0x49 /home/user/go/pkg/mod/github.com/miekg/dns@v1.1.43/server.go:174
# 0xfa754e github.com/miekg/dns.(*Server).serveUDP+0x20e /home/user/go/pkg/mod/github.com/miekg/dns@v1.1.43/server.go:501
# 0xfa65b9 github.com/miekg/dns.(*Server).ListenAndServe+0x339 /home/user/go/pkg/mod/github.com/miekg/dns@v1.1.43/server.go:330
# 0x12c0764 github.com/safing/portmaster/nameserver.startListener.func1+0x44 /home/user/git/safing/portmaster/nameserver/module.go:114
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xb93e65 0xbc9365 0xc0c30c 0xc0d645 0xc10c59 0xc10f0a 0xd03565 0xd18e59 0xd1796b 0xe13c8e 0xe139be 0xf62f54 0xf1adc7 0xf1a4de 0xf60b76 0xbcfba1
# 0xbc9364 internal/poll.runtime_pollWait+0x64 /usr/local/go/src/runtime/netpoll.go:222
# 0xc0c30b internal/poll.(*pollDesc).wait+0x4b /usr/local/go/src/internal/poll/fd_poll_runtime.go:87
# 0xc0d644 internal/poll.execIO+0x104 /usr/local/go/src/internal/poll/fd_windows.go:175
# 0xc10c58 internal/poll.(*FD).acceptOne+0x98 /usr/local/go/src/internal/poll/fd_windows.go:810
# 0xc10f09 internal/poll.(*FD).Accept+0x169 /usr/local/go/src/internal/poll/fd_windows.go:844
# 0xd03564 net.(*netFD).accept+0x84 /usr/local/go/src/net/fd_windows.go:139
# 0xd18e58 net.(*TCPListener).accept+0x38 /usr/local/go/src/net/tcpsock_posix.go:139
# 0xd1796a net.(*TCPListener).Accept+0x6a /usr/local/go/src/net/tcpsock.go:261
# 0xe13c8d net/http.(*Server).Serve+0x26d /usr/local/go/src/net/http/server.go:2937
# 0xe139bd net/http.(*Server).ListenAndServe+0xbd /usr/local/go/src/net/http/server.go:2866
# 0xf62f53 github.com/safing/portbase/api.Serve.func1+0x33 /home/user/git/safing/portbase/api/router.go:63
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf60b75 github.com/safing/portbase/api.Serve+0x1d5 /home/user/git/safing/portbase/api/router.go:62
1 @ 0xb9de1a 0xbade2f 0x10cee15 0xf1adc7 0xf1a811 0xbcfba1
# 0x10cee14 github.com/safing/portbase/notifications.cleaner+0x114 /home/user/git/safing/portbase/notifications/cleaner.go:13
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xbade2f 0x10f3cf8 0xf1adc7 0xf1a811 0xbcfba1
# 0x10f3cf7 github.com/safing/portmaster/intel/geoip.(*updateWorker).run+0x117 /home/user/git/safing/portmaster/intel/geoip/database.go:173
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xbade2f 0x10fa5c5 0xf1adc7 0xf1a811 0xbcfba1
# 0x10fa5c4 github.com/safing/portmaster/netenv.monitorNetworkChanges+0x164 /home/user/git/safing/portmaster/netenv/network-change.go:48
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xbade2f 0x110dcfc 0xf1adc7 0xf1a4de 0xf1cbc5 0xbcfba1
# 0x110dcfb github.com/safing/portmaster/status.autoPilot+0xdb /home/user/git/safing/portmaster/status/autopilot.go:16
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf1cbc4 github.com/safing/portbase/modules.(*Module).StartWorker.func1+0x64 /home/user/git/safing/portbase/modules/worker.go:27
1 @ 0xb9de1a 0xbade2f 0x114e9c5 0x115d0a5 0xf1adc7 0xf1a811 0xbcfba1
# 0x114e9c4 github.com/safing/portmaster/resolver.handleMDNSMessages+0x104 /home/user/git/safing/portmaster/resolver/resolver-mdns.go:137
# 0x115d0a4 github.com/safing/portmaster/resolver.listenToMDNS.func5+0x44 /home/user/git/safing/portmaster/resolver/resolver-mdns.go:126
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xbade2f 0x11b1248 0xf1adc7 0xf1a811 0xbcfba1
# 0x11b1247 github.com/safing/portmaster/profile.cleanActiveProfiles+0x187 /home/user/git/safing/portmaster/profile/active.go:84
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xbade2f 0x124c1a5 0xbcfba1
# 0x124c1a4 github.com/xtaci/kcp-go/v5.(*TimedSched).prepend+0x284 /home/user/go/pkg/mod/github.com/xtaci/kcp-go/v5@v5.6.1/timedsched.go:103
1 @ 0xb9de1a 0xbade2f 0x127733a 0xf1adc7 0xf1a811 0xbcfba1
# 0x1277339 github.com/safing/portmaster/network.openDNSRequestWriter+0x119 /home/user/git/safing/portmaster/network/dns.go:91
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xbade2f 0x12b2aac 0xf1adc7 0xf1a4de 0xf1cbc5 0xbcfba1
# 0x12b2aab github.com/safing/portmaster/firewall.packetHandler+0x10b /home/user/git/safing/portmaster/firewall/interception.go:522
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf1cbc4 github.com/safing/portbase/modules.(*Module).StartWorker.func1+0x64 /home/user/git/safing/portbase/modules/worker.go:27
1 @ 0xb9de1a 0xbade2f 0x12b2da9 0xf1adc7 0xf1a4de 0xf1cbc5 0xbcfba1
# 0x12b2da8 github.com/safing/portmaster/firewall.statLogger+0x248 /home/user/git/safing/portmaster/firewall/interception.go:536
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf1cbc4 github.com/safing/portbase/modules.(*Module).StartWorker.func1+0x64 /home/user/git/safing/portbase/modules/worker.go:27
1 @ 0xb9de1a 0xbade2f 0xd0edc5 0xd0e4ed 0xd0e497 0x10fc1a5 0x10fb9fb 0xf1adc7 0xf1a811 0xbcfba1
# 0xd0edc4 net.(*Resolver).lookupIPAddr+0x684 /usr/local/go/src/net/lookup.go:299
# 0xd0e4ec net.(*Resolver).LookupIPAddr+0x8c /usr/local/go/src/net/lookup.go:204
# 0xd0e496 net.LookupIP+0x36 /usr/local/go/src/net/lookup.go:190
# 0x10fc1a4 github.com/safing/portmaster/netenv.checkOnlineStatus+0x504 /home/user/git/safing/portmaster/netenv/online-status.go:507
# 0x10fb9fa github.com/safing/portmaster/netenv.monitorOnlineStatus+0x5a /home/user/git/safing/portmaster/netenv/online-status.go:369
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xbade2f 0xd0edc5 0xd0e4ed 0xd0e497 0x11c6cb1 0xf1adc7 0xf1a4de 0xf1cbc5 0xbcfba1
# 0xd0edc4 net.(*Resolver).lookupIPAddr+0x684 /usr/local/go/src/net/lookup.go:299
# 0xd0e4ec net.(*Resolver).LookupIPAddr+0x8c /usr/local/go/src/net/lookup.go:204
# 0xd0e496 net.LookupIP+0x36 /usr/local/go/src/net/lookup.go:190
# 0x11c6cb0 github.com/safing/portmaster/compat.selfcheck.func2+0xb0 /home/user/git/safing/portmaster/compat/selfcheck.go:123
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf1cbc4 github.com/safing/portbase/modules.(*Module).StartWorker.func1+0x64 /home/user/git/safing/portbase/modules/worker.go:27
1 @ 0xb9de1a 0xbade2f 0xeeaeb4 0xeeaa98 0xbcfba1
# 0xeeaeb3 github.com/safing/portbase/log.writer+0x3b3 /home/user/git/safing/portbase/log/output.go:156
# 0xeeaa97 github.com/safing/portbase/log.writerManager+0x97 /home/user/git/safing/portbase/log/output.go:113
1 @ 0xb9de1a 0xbade2f 0xf13cd8 0xbcfba1
# 0xf13cd7 github.com/safing/portbase/modules.microTaskScheduler+0x1b7 /home/user/git/safing/portbase/modules/microtasks.go:184
1 @ 0xb9de1a 0xbade2f 0xf19f25 0xbcfba1
# 0xf19f24 github.com/safing/portbase/modules.taskQueueHandler+0x1c4 /home/user/git/safing/portbase/modules/tasks.go:447
1 @ 0xb9de1a 0xbade2f 0xf1a1fe 0xbcfba1
# 0xf1a1fd github.com/safing/portbase/modules.taskScheduleHandler+0xfd /home/user/git/safing/portbase/modules/tasks.go:497
1 @ 0xb9de1a 0xbade2f 0xf24c9d 0xf1adc7 0xf1a811 0xbcfba1
# 0xf24c9c github.com/safing/portbase/rng.fullFeeder+0x15c /home/user/git/safing/portbase/rng/fullfeed.go:25
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xbade2f 0xf25725 0xf1adc7 0xf1a811 0xbcfba1
# 0xf25724 github.com/safing/portbase/rng.osFeeder+0x1e4 /home/user/git/safing/portbase/rng/osfeeder.go:27
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xbade2f 0xf26054 0xf1adc7 0xf1a811 0xbcfba1
# 0xf26053 github.com/safing/portbase/rng.tickFeeder+0x253 /home/user/git/safing/portbase/rng/tickfeeder.go:60
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xbade2f 0xf70518 0x12c1290 0xb9da49 0xbcfba1
# 0xf70517 github.com/safing/portbase/run.Run+0x237 /home/user/git/safing/portbase/run/main.go:66
# 0x12c128f main.main+0xcf /home/user/git/safing/portmaster/cmds/portmaster-core/main.go:31
# 0xb9da48 runtime.main+0x208 /usr/local/go/src/runtime/proc.go:204
1 @ 0xb9de1a 0xbae7f7 0xbae7e2 0xbcacee 0x11b8c93 0x11b8c45 0x11c4959 0x12ac4f1 0x12ac4cf 0x12b4793 0x12b342d 0x12b30c5 0x12b227e 0x1274e6c 0x1279611 0xf1adc7 0xf1a4de 0xf1cbc5 0xbcfba1
# 0xbcaced sync.runtime_SemacquireMutex+0x4d /usr/local/go/src/runtime/sema.go:71
# 0x11b8c92 sync.(*RWMutex).RLock+0xb2 /usr/local/go/src/sync/rwmutex.go:50
# 0x11b8c44 github.com/safing/portmaster/profile.(*LayeredProfile).LocalProfile+0x64 /home/user/git/safing/portmaster/profile/profile-layered.go:162
# 0x11c4958 github.com/safing/portmaster/compat.(*appIssue).notify+0x58 /home/user/git/safing/portmaster/compat/notify.go:104
# 0x12ac4f0 github.com/safing/portmaster/compat.ReportSecureDNSBypassIssue+0xf0 /home/user/git/safing/portmaster/compat/callbacks.go:31
# 0x12ac4ce github.com/safing/portmaster/firewall.PreventBypassing+0xce /home/user/git/safing/portmaster/firewall/bypassing.go:35
# 0x12b4792 github.com/safing/portmaster/firewall.checkBypassPrevention+0x72 /home/user/git/safing/portmaster/firewall/master.go:359
# 0x12b342c github.com/safing/portmaster/firewall.runDeciders+0xec /home/user/git/safing/portmaster/firewall/master.go:126
# 0x12b30c4 github.com/safing/portmaster/firewall.DecideOnConnection+0x2c4 /home/user/git/safing/portmaster/firewall/master.go:96
# 0x12b227d github.com/safing/portmaster/firewall.initialHandler+0x83d /home/user/git/safing/portmaster/firewall/interception.go:367
# 0x1274e6b github.com/safing/portmaster/network.(*Connection).packetHandler+0xeb /home/user/git/safing/portmaster/network/connection.go:625
# 0x1279610 github.com/safing/portmaster/network.(*Connection).SetFirewallHandler.func1+0x30 /home/user/git/safing/portmaster/network/connection.go:587
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf1cbc4 github.com/safing/portbase/modules.(*Module).StartWorker.func1+0x64 /home/user/git/safing/portbase/modules/worker.go:27
1 @ 0xb9de1a 0xbae7f7 0xbae7e2 0xbcacee 0xbdce2f 0x1279345 0x127905d 0xf13aa2 0xf13877 0x1272576 0x12723ba 0xf1adc7 0xf1a811 0xbcfba1
# 0xbcaced sync.runtime_SemacquireMutex+0x4d /usr/local/go/src/runtime/sema.go:71
# 0xbdce2e sync.(*Mutex).lockSlow+0x10e /usr/local/go/src/sync/mutex.go:138
# 0x1279344 sync.(*Mutex).Lock+0x504 /usr/local/go/src/sync/mutex.go:81
# 0x127905c github.com/safing/portmaster/network.cleanConnections.func1+0x21c /home/user/git/safing/portmaster/network/clean.go:51
# 0xf13aa1 github.com/safing/portbase/modules.(*Module).runMicroTask+0xa1 /home/user/git/safing/portbase/modules/microtasks.go:158
# 0xf13876 github.com/safing/portbase/modules.(*Module).RunMediumPriorityMicroTask+0x96 /home/user/git/safing/portbase/modules/microtasks.go:106
# 0x1272575 github.com/safing/portmaster/network.cleanConnections+0x95 /home/user/git/safing/portmaster/network/clean.go:43
# 0x12723b9 github.com/safing/portmaster/network.connectionCleaner+0x59 /home/user/git/safing/portmaster/network/clean.go:30
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xbae7f7 0xbae7e2 0xbcacee 0xbdce2f 0xbdcd0e 0xf5b1bf 0xf59bb6 0xf5a1d7 0xbcfba1
# 0xbcaced sync.runtime_SemacquireMutex+0x4d /usr/local/go/src/runtime/sema.go:71
# 0xbdce2e sync.(*Mutex).lockSlow+0x10e /usr/local/go/src/sync/mutex.go:138
# 0xbdcd0d sync.(*Mutex).Lock+0x4d /usr/local/go/src/sync/mutex.go:81
# 0xf5b1be github.com/safing/portbase/api.marshalRecord+0x7e /home/user/git/safing/portbase/api/database.go:631
# 0xf59bb5 github.com/safing/portbase/api.(*DatabaseAPI).processSub+0x275 /home/user/git/safing/portbase/api/database.go:424
# 0xf5a1d6 github.com/safing/portbase/api.(*DatabaseAPI).handleQsub+0x136 /home/user/git/safing/portbase/api/database.go:478
1 @ 0xb9de1a 0xbae7f7 0xbae7e2 0xbcacee 0xbdce2f 0xbde5b5 0xbde549 0x11c6825 0x11c6abf 0xf1adc7 0xf1a4de 0xf1cbc5 0xbcfba1
# 0xbcaced sync.runtime_SemacquireMutex+0x4d /usr/local/go/src/runtime/sema.go:71
# 0xbdce2e sync.(*Mutex).lockSlow+0x10e /usr/local/go/src/sync/mutex.go:138
# 0xbde5b4 sync.(*Mutex).Lock+0x94 /usr/local/go/src/sync/mutex.go:81
# 0xbde548 sync.(*RWMutex).Lock+0x28 /usr/local/go/src/sync/rwmutex.go:98
# 0x11c6824 github.com/safing/portmaster/compat.(*appIssue).notify.func1.1+0x64 /home/user/git/safing/portmaster/compat/notify.go:153
# 0x11c6abe github.com/safing/portmaster/compat.(*appIssue).notify.func1+0x3e /home/user/git/safing/portmaster/compat/notify.go:162
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf1cbc4 github.com/safing/portbase/modules.(*Module).StartWorker.func1+0x64 /home/user/git/safing/portbase/modules/worker.go:27
1 @ 0xb9de1a 0xbae7f7 0xbae7e2 0xbcacee 0xbde5aa 0x11b8dea 0x11bdaa5 0xf1adc7 0xf1a811 0xbcfba1
# 0xbcaced sync.runtime_SemacquireMutex+0x4d /usr/local/go/src/runtime/sema.go:71
# 0xbde5a9 sync.(*RWMutex).Lock+0x89 /usr/local/go/src/sync/rwmutex.go:103
# 0x11b8de9 github.com/safing/portmaster/profile.(*LayeredProfile).increaseRevisionCounter+0x109 /home/user/git/safing/portmaster/profile/profile-layered.go:176
# 0x11bdaa4 github.com/safing/portmaster/profile.startProfileUpdateChecker.func1+0x364 /home/user/git/safing/portmaster/profile/database.go:95
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xbae7f7 0xbae7e2 0xbcacee 0xbde5aa 0x11c6825 0x11c6abf 0xf1adc7 0xf1a4de 0xf1cbc5 0xbcfba1
# 0xbcaced sync.runtime_SemacquireMutex+0x4d /usr/local/go/src/runtime/sema.go:71
# 0xbde5a9 sync.(*RWMutex).Lock+0x89 /usr/local/go/src/sync/rwmutex.go:103
# 0x11c6824 github.com/safing/portmaster/compat.(*appIssue).notify.func1.1+0x64 /home/user/git/safing/portmaster/compat/notify.go:153
# 0x11c6abe github.com/safing/portmaster/compat.(*appIssue).notify.func1+0x3e /home/user/git/safing/portmaster/compat/notify.go:162
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf1cbc4 github.com/safing/portbase/modules.(*Module).StartWorker.func1+0x64 /home/user/git/safing/portbase/modules/worker.go:27
1 @ 0xbc8fa5 0xf4910a 0xf48ea7 0xf45978 0xf52016 0x11a9213 0xf5d424 0xf5c9d6 0xf6188f 0xf62fcc 0xf1adc7 0xf1a4de 0xf60cc5 0xe138ca 0xe0f86d 0xbcfba1
# 0xbc8fa4 runtime/pprof.runtime_goroutineProfileWithLabels+0x64 /usr/local/go/src/runtime/mprof.go:716
# 0xf49109 runtime/pprof.writeRuntimeProfile+0xe9 /usr/local/go/src/runtime/pprof/pprof.go:724
# 0xf48ea6 runtime/pprof.writeGoroutine+0xa6 /usr/local/go/src/runtime/pprof/pprof.go:684
# 0xf45977 runtime/pprof.(*Profile).WriteTo+0x3f7 /usr/local/go/src/runtime/pprof/pprof.go:331
# 0xf52015 github.com/safing/portbase/utils/debug.(*Info).AddGoroutineStack+0x95 /home/user/git/safing/portbase/utils/debug/debug.go:132
# 0x11a9212 github.com/safing/portmaster/core.debugInfo+0x112 /home/user/git/safing/portmaster/core/api.go:91
# 0xf5d423 github.com/safing/portbase/api.(*Endpoint).ServeHTTP+0xa23 /home/user/git/safing/portbase/api/endpoints.go:438
# 0xf5c9d5 github.com/safing/portbase/api.(*endpointHandler).ServeHTTP+0xb5 /home/user/git/safing/portbase/api/endpoints.go:357
# 0xf6188e github.com/safing/portbase/api.(*mainHandler).handle+0xbae /home/user/git/safing/portbase/api/router.go:197
# 0xf62fcb github.com/safing/portbase/api.(*mainHandler).ServeHTTP.func1+0x4b /home/user/git/safing/portbase/api/router.go:81
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf60cc4 github.com/safing/portbase/api.(*mainHandler).ServeHTTP+0xa4 /home/user/git/safing/portbase/api/router.go:80
# 0xe138c9 net/http.serverHandler.ServeHTTP+0xa9 /usr/local/go/src/net/http/server.go:2843
# 0xe0f86c net/http.(*conn).serve+0x8ac /usr/local/go/src/net/http/server.go:1925
```
</details>
[logs.zip](https://github.com/safing/portmaster/files/7765280/logs.zip)
| True | Compatibility with Cisco Secure Endpoint (Cisco AMP) - **Pre-Submit Checklist**:
- Check applicable sources for existing issues:
- (N/A) [Linux Compatibility](https://docs.safing.io/portmaster/install/linux#compatibility)
- (N/A) [VPN Compatibility](https://docs.safing.io/portmaster/install/status/vpn-compatibility)
- [x] [Github Issues](https://github.com/safing/portmaster/issues?q=is%3Aissue+label%3Ain%2Fcompatibility)
**What worked?**
The portmaster UI and Core service launch. The portmaster also correctly identifies the network traffic by DNS name. As far as i can tell all connections displayed are accurate.
**What did not work?**
Blocked domains are not successfully blocked, furthermore DNS resolution takes an exponentially longer time then without the portmaster installed. Possibly timing out before resorting back to the Cisco Secure endpoint. After an restart of the Core Service no network traffic is allowed anymore, and after shutting down the portmaster everything starts working again. When trying to start the portmaster back up again the core service won't start. unless killing it completely and starting it back up again.
Rebooting doesn't work, killing the Cisco processes seems to work but it forces itself back up again, thus killing the network connection.
The following three errors are shown:
* Detected System DNS Client Bypass Attempt;
* Something is interfering with the Portmaster;
* Limited network connectivity.
I feel like for now it is best to consider Cisco Secure Endpoint as incompatible. At least on windows.
**Debug Information**:
<details>
<summary>Version 0.7.12</summary>
```
Portmaster
version 0.7.12
commit tags/v0.7.12-0-g466210b6134216054111af2f2bc0740a07e783b6
built with go1.15.8 (gc) windows/amd64
using options main.go
by user@docker
on 16.12.2021
Licensed under the AGPLv3 license.
The source code is available here: https://github.com/safing/portmaster
```
</details>
<details>
<summary>Platform: Microsoft Windows 10 Enterprise 10.0.19044 Build 19044</summary>
```
System: Microsoft Windows 10 Enterprise windows (Standalone Workstation) 10.0.19044 Build 19044
Kernel: 10.0.19044 Build 19044 x86_64
```
</details>
<details>
<summary>Status: Trusted</summary>
```
ActiveSecurityLevel: Trusted
SelectedSecurityLevel: Off
ThreatMitigationLevel: Trusted
CaptivePortal:
OnlineStatus: Limited
```
</details>
<details>
<summary>Resolvers: 1/1</summary>
```
Cloudflare
dot://1.1.1.2:853#config
Failing: false
```
</details>
<details>
<summary>Compat Module Error</summary>
```
Message: self-check #2: dns integration check failed: did not receive test query after 3s
Timestamp: 2021-12-22 22:10:59.8241517 +0100 CET m=+117.862369101
ModuleName: compat
TaskName: selfcheck
TaskType:
Severity: error
PanicValue: %!s(<nil>)
StackTrace:
goroutine 3097 [running]:
runtime/debug.Stack(0xc000010730, 0xc0007f7a90, 0x50)
/usr/local/go/src/runtime/debug/stack.go:24 +0xa5
github.com/safing/portbase/modules.(*Module).NewErrorMessage(0xc0001bb040, 0x144fd05, 0x9, 0x1550860, 0xc000010730, 0x58)
/home/user/git/safing/portbase/modules/error.go:48 +0x58
github.com/safing/portmaster/compat.(*systemIssue).notify(0x19da6c0, 0x1550860, 0xc000010730)
/home/user/git/safing/portmaster/compat/notify.go:89 +0x1ac
github.com/safing/portmaster/compat.selfcheckTaskFunc(0x1562a60, 0xc00065ddc0, 0xc0007a07e0, 0x0, 0x0)
/home/user/git/safing/portmaster/compat/module.go:85 +0x16b
github.com/safing/portbase/modules.(*Task).executeWithLocking(0xc0007a07e0)
/home/user/git/safing/portbase/modules/tasks.go:369 +0x94
created by github.com/safing/portbase/modules.(*Task).runWithLocking
/home/user/git/safing/portbase/modules/tasks.go:318 +0x285
```
</details>
<details>
<summary>Unexpected Logs</summary>
```
211222 22:09:34.587 ine-status:509 > WARN 108 netenv: dns check query failed: lookup one.one.one.one.: no such host
211222 22:09:34.587 ine-status:523 > WARN 110 netenv: dns fallback check query failed: lookup dns-check.safing.io.: no such host
211222 22:09:51.691 ine-status:509 > WARN 129 netenv: dns check query failed: lookup one.one.one.one.: no such host
211222 22:10:02.768 ine-status:523 > WARN 141 netenv: dns fallback check query failed: lookup dns-check.safing.io.: no such host
211222 22:10:15.815 ine-status:509 > WARN 183 netenv: dns check query failed: lookup one.one.one.one.: no such host
211222 22:10:26.973 pat/module:083 > ERRO 199 compat: self-check #2: dns integration check failed: did not receive test query after 3s
211222 22:10:27.860 ine-status:523 > WARN 201 netenv: dns fallback check query failed: lookup dns-check.safing.io.: no such host
211222 22:10:40.926 ine-status:509 > WARN 212 netenv: dns check query failed: lookup one.one.one.one.: no such host
211222 22:10:52.982 ine-status:523 > WARN 228 netenv: dns fallback check query failed: lookup dns-check.safing.io.: no such host
211222 22:10:57.543 pat/module:083 > ERRO 233 compat: self-check #2: dns integration check failed: did not receive test query after 3s
211222 22:10:59.824 CURRENT TIME
```
</details>
<details>
<summary>Goroutine Stack</summary>
```
goroutine profile: total 2259
1630 @ 0xb9de1a 0xbae7f7 0xbae7e2 0xbcabc9 0xbde9eb 0x11bf235 0x12b08d5 0x12b05ea 0x12b8b8e 0xf1adc7 0xf1a4de 0xf1cbc5 0xbcfba1
# 0xbcabc8 sync.runtime_Semacquire+0x48 /usr/local/go/src/runtime/sema.go:56
# 0xbde9ea sync.(*WaitGroup).Wait+0x6a /usr/local/go/src/sync/waitgroup.go:130
# 0x11bf234 golang.org/x/sync/singleflight.(*Group).Do+0x1f4 /home/user/go/pkg/mod/golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c/singleflight/singleflight.go:94
# 0x12b08d4 github.com/safing/portmaster/firewall.getConnection+0xd4 /home/user/git/safing/portmaster/firewall/interception.go:130
# 0x12b05e9 github.com/safing/portmaster/firewall.handlePacket+0x1c9 /home/user/git/safing/portmaster/firewall/interception.go:113
# 0x12b8b8d github.com/safing/portmaster/firewall.packetHandler.func1+0x4d /home/user/git/safing/portmaster/firewall/interception.go:527
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf1cbc4 github.com/safing/portbase/modules.(*Module).StartWorker.func1+0x64 /home/user/git/safing/portbase/modules/worker.go:27
502 @ 0xb9de1a 0xbae7f7 0xbae7e2 0xbcacee 0x11b8c93 0x11b8c45 0x11c3259 0x11c2b8b 0x11c0bea 0x1273377 0x12b8ae5 0x11bf889 0x11bf425 0x11bf194 0x12b08d5 0x12b05ea 0x12b8b8e 0xf1adc7 0xf1a4de 0xf1cbc5 0xbcfba1
# 0xbcaced sync.runtime_SemacquireMutex+0x4d /usr/local/go/src/runtime/sema.go:71
# 0x11b8c92 sync.(*RWMutex).RLock+0xb2 /usr/local/go/src/sync/rwmutex.go:50
# 0x11b8c44 github.com/safing/portmaster/profile.(*LayeredProfile).LocalProfile+0x64 /home/user/git/safing/portmaster/profile/profile-layered.go:162
# 0x11c3258 github.com/safing/portmaster/process.(*Process).UpdateProfileMetadata+0x58 /home/user/git/safing/portmaster/process/profile.go:102
# 0x11c2b8a github.com/safing/portmaster/process.(*Process).GetProfile+0x12a /home/user/git/safing/portmaster/process/profile.go:28
# 0x11c0be9 github.com/safing/portmaster/process.GetProcessByConnection+0x3a9 /home/user/git/safing/portmaster/process/find.go:40
# 0x1273376 github.com/safing/portmaster/network.NewConnectionFromFirstPacket+0xb6 /home/user/git/safing/portmaster/network/connection.go:320
# 0x12b8ae4 github.com/safing/portmaster/firewall.getConnection.func1+0xa4 /home/user/git/safing/portmaster/firewall/interception.go:138
# 0x11bf888 golang.org/x/sync/singleflight.(*Group).doCall.func2+0x68 /home/user/go/pkg/mod/golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c/singleflight/singleflight.go:193
# 0x11bf424 golang.org/x/sync/singleflight.(*Group).doCall+0xc4 /home/user/go/pkg/mod/golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c/singleflight/singleflight.go:195
# 0x11bf193 golang.org/x/sync/singleflight.(*Group).Do+0x153 /home/user/go/pkg/mod/golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c/singleflight/singleflight.go:108
# 0x12b08d4 github.com/safing/portmaster/firewall.getConnection+0xd4 /home/user/git/safing/portmaster/firewall/interception.go:130
# 0x12b05e9 github.com/safing/portmaster/firewall.handlePacket+0x1c9 /home/user/git/safing/portmaster/firewall/interception.go:113
# 0x12b8b8d github.com/safing/portmaster/firewall.packetHandler.func1+0x4d /home/user/git/safing/portmaster/firewall/interception.go:527
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf1cbc4 github.com/safing/portbase/modules.(*Module).StartWorker.func1+0x64 /home/user/git/safing/portbase/modules/worker.go:27
51 @ 0xb9de1a 0xbae7f7 0xbae7e2 0xbcacee 0xbdce2f 0x11c31b2 0x11c2ae6 0x11c0bea 0x1273377 0x12b8ae5 0x11bf889 0x11bf425 0x11bf194 0x12b08d5 0x12b05ea 0x12b8b8e 0xf1adc7 0xf1a4de 0xf1cbc5 0xbcfba1
# 0xbcaced sync.runtime_SemacquireMutex+0x4d /usr/local/go/src/runtime/sema.go:71
# 0xbdce2e sync.(*Mutex).lockSlow+0x10e /usr/local/go/src/sync/mutex.go:138
# 0x11c31b1 sync.(*Mutex).Lock+0x751 /usr/local/go/src/sync/mutex.go:81
# 0x11c2ae5 github.com/safing/portmaster/process.(*Process).GetProfile+0x85 /home/user/git/safing/portmaster/process/profile.go:22
# 0x11c0be9 github.com/safing/portmaster/process.GetProcessByConnection+0x3a9 /home/user/git/safing/portmaster/process/find.go:40
# 0x1273376 github.com/safing/portmaster/network.NewConnectionFromFirstPacket+0xb6 /home/user/git/safing/portmaster/network/connection.go:320
# 0x12b8ae4 github.com/safing/portmaster/firewall.getConnection.func1+0xa4 /home/user/git/safing/portmaster/firewall/interception.go:138
# 0x11bf888 golang.org/x/sync/singleflight.(*Group).doCall.func2+0x68 /home/user/go/pkg/mod/golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c/singleflight/singleflight.go:193
# 0x11bf424 golang.org/x/sync/singleflight.(*Group).doCall+0xc4 /home/user/go/pkg/mod/golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c/singleflight/singleflight.go:195
# 0x11bf193 golang.org/x/sync/singleflight.(*Group).Do+0x153 /home/user/go/pkg/mod/golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c/singleflight/singleflight.go:108
# 0x12b08d4 github.com/safing/portmaster/firewall.getConnection+0xd4 /home/user/git/safing/portmaster/firewall/interception.go:130
# 0x12b05e9 github.com/safing/portmaster/firewall.handlePacket+0x1c9 /home/user/git/safing/portmaster/firewall/interception.go:113
# 0x12b8b8d github.com/safing/portmaster/firewall.packetHandler.func1+0x4d /home/user/git/safing/portmaster/firewall/interception.go:527
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf1cbc4 github.com/safing/portbase/modules.(*Module).StartWorker.func1+0x64 /home/user/git/safing/portbase/modules/worker.go:27
11 @ 0xb9de1a 0xbade2f 0xf59b65 0xf5a1d7 0xbcfba1
# 0xf59b64 github.com/safing/portbase/api.(*DatabaseAPI).processSub+0x224 /home/user/git/safing/portbase/api/database.go:415
# 0xf5a1d6 github.com/safing/portbase/api.(*DatabaseAPI).handleQsub+0x136 /home/user/git/safing/portbase/api/database.go:478
8 @ 0xb9de1a 0xbade2f 0x124bc6a 0xbcfba1
# 0x124bc69 github.com/xtaci/kcp-go/v5.(*TimedSched).sched+0x2c9 /home/user/go/pkg/mod/github.com/xtaci/kcp-go/v5@v5.6.1/timedsched.go:67
4 @ 0xb9de1a 0xbae7f7 0xbae7e2 0xbcacee 0xbdce2f 0xbde5b5 0xbde549 0x11bb897 0x11c2d25 0x11c0bea 0x1273377 0x12b8ae5 0x11bf889 0x11bf425 0x11bf194 0x12b08d5 0x12b05ea 0x12b8b8e 0xf1adc7 0xf1a4de 0xf1cbc5 0xbcfba1
# 0xbcaced sync.runtime_SemacquireMutex+0x4d /usr/local/go/src/runtime/sema.go:71
# 0xbdce2e sync.(*Mutex).lockSlow+0x10e /usr/local/go/src/sync/mutex.go:138
# 0xbde5b4 sync.(*Mutex).Lock+0x94 /usr/local/go/src/sync/mutex.go:81
# 0xbde548 sync.(*RWMutex).Lock+0x28 /usr/local/go/src/sync/rwmutex.go:98
# 0x11bb896 github.com/safing/portmaster/profile.(*Profile).LayeredProfile+0x56 /home/user/git/safing/portmaster/profile/profile.go:406
# 0x11c2d24 github.com/safing/portmaster/process.(*Process).GetProfile+0x2c4 /home/user/git/safing/portmaster/process/profile.go:93
# 0x11c0be9 github.com/safing/portmaster/process.GetProcessByConnection+0x3a9 /home/user/git/safing/portmaster/process/find.go:40
# 0x1273376 github.com/safing/portmaster/network.NewConnectionFromFirstPacket+0xb6 /home/user/git/safing/portmaster/network/connection.go:320
# 0x12b8ae4 github.com/safing/portmaster/firewall.getConnection.func1+0xa4 /home/user/git/safing/portmaster/firewall/interception.go:138
# 0x11bf888 golang.org/x/sync/singleflight.(*Group).doCall.func2+0x68 /home/user/go/pkg/mod/golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c/singleflight/singleflight.go:193
# 0x11bf424 golang.org/x/sync/singleflight.(*Group).doCall+0xc4 /home/user/go/pkg/mod/golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c/singleflight/singleflight.go:195
# 0x11bf193 golang.org/x/sync/singleflight.(*Group).Do+0x153 /home/user/go/pkg/mod/golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c/singleflight/singleflight.go:108
# 0x12b08d4 github.com/safing/portmaster/firewall.getConnection+0xd4 /home/user/git/safing/portmaster/firewall/interception.go:130
# 0x12b05e9 github.com/safing/portmaster/firewall.handlePacket+0x1c9 /home/user/git/safing/portmaster/firewall/interception.go:113
# 0x12b8b8d github.com/safing/portmaster/firewall.packetHandler.func1+0x4d /home/user/git/safing/portmaster/firewall/interception.go:527
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf1cbc4 github.com/safing/portbase/modules.(*Module).StartWorker.func1+0x64 /home/user/git/safing/portbase/modules/worker.go:27
2 @ 0xb64875 0xbcc492 0xbef9a5 0xd1f519 0xd1fdd2 0xbcfba1
# 0xbcc491 syscall.Syscall6+0xf1 /usr/local/go/src/runtime/syscall_windows.go:201
# 0xbef9a4 syscall.GetAddrInfoW+0xe4 /usr/local/go/src/syscall/zsyscall_windows.go:1718
# 0xd1f518 net.(*Resolver).lookupIP.func1+0x258 /usr/local/go/src/net/lookup_windows.go:109
# 0xd1fdd1 net.(*Resolver).lookupIP.func2+0x31 /usr/local/go/src/net/lookup_windows.go:146
2 @ 0xb9de1a 0xb93e65 0xbc9365 0xc0c30c 0xc0d645 0xc0e81f 0xd01dd6 0xd10e35 0xd9ba8a 0xd9bc16 0xf342e7 0xf3686b 0xf3793b 0xf380f6 0xf575aa 0xf1adc7 0xf1a4de 0xf1cbc5 0xbcfba1
# 0xbc9364 internal/poll.runtime_pollWait+0x64 /usr/local/go/src/runtime/netpoll.go:222
# 0xc0c30b internal/poll.(*pollDesc).wait+0x4b /usr/local/go/src/internal/poll/fd_poll_runtime.go:87
# 0xc0d644 internal/poll.execIO+0x104 /usr/local/go/src/internal/poll/fd_windows.go:175
# 0xc0e81e internal/poll.(*FD).Read+0x2fe /usr/local/go/src/internal/poll/fd_windows.go:441
# 0xd01dd5 net.(*netFD).Read+0x55 /usr/local/go/src/net/fd_posix.go:55
# 0xd10e34 net.(*conn).Read+0x94 /usr/local/go/src/net/net.go:182
# 0xd9ba89 bufio.(*Reader).fill+0x109 /usr/local/go/src/bufio/bufio.go:101
# 0xd9bc15 bufio.(*Reader).Peek+0x55 /usr/local/go/src/bufio/bufio.go:139
# 0xf342e6 github.com/gorilla/websocket.(*Conn).read+0x46 /home/user/go/pkg/mod/github.com/gorilla/websocket@v1.4.2/conn.go:370
# 0xf3686a github.com/gorilla/websocket.(*Conn).advanceFrame+0x6a /home/user/go/pkg/mod/github.com/gorilla/websocket@v1.4.2/conn.go:798
# 0xf3793a github.com/gorilla/websocket.(*Conn).NextReader+0x9a /home/user/go/pkg/mod/github.com/gorilla/websocket@v1.4.2/conn.go:980
# 0xf380f5 github.com/gorilla/websocket.(*Conn).ReadMessage+0x35 /home/user/go/pkg/mod/github.com/gorilla/websocket@v1.4.2/conn.go:1064
# 0xf575a9 github.com/safing/portbase/api.(*DatabaseAPI).handler+0x49 /home/user/git/safing/portbase/api/database.go:150
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf1cbc4 github.com/safing/portbase/modules.(*Module).StartWorker.func1+0x64 /home/user/git/safing/portbase/modules/worker.go:27
2 @ 0xb9de1a 0xbade2f 0xd0ff59 0xd1e4d9 0xd1efc2 0xcfc7b5 0xbcfba1
# 0xd0ff58 net.(*Resolver).lookupIP+0x1b8 /usr/local/go/src/net/lookup_windows.go:151
# 0xd1e4d8 net.glob..func1+0x78 /usr/local/go/src/net/hook.go:23
# 0xd1efc1 net.(*Resolver).lookupIPAddr.func1+0xc1 /usr/local/go/src/net/lookup.go:293
# 0xcfc7b4 internal/singleflight.(*Group).doCall+0x34 /usr/local/go/src/internal/singleflight/singleflight.go:95
2 @ 0xb9de1a 0xbade2f 0xf0cf78 0xf1adc7 0xf1a811 0xbcfba1
# 0xf0cf77 github.com/safing/portbase/database.(*Interface).DelayedCacheWriter+0x1d7 /home/user/git/safing/portbase/database/interface_cache.go:34
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
2 @ 0xb9de1a 0xbade2f 0xf24965 0xf1adc7 0xf1a811 0xbcfba1
# 0xf24964 github.com/safing/portbase/rng.(*Feeder).run+0x2e4 /home/user/git/safing/portbase/rng/entropy.go:119
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
2 @ 0xb9de1a 0xbade2f 0xf58085 0xf1adc7 0xf1a4de 0xf1cbc5 0xbcfba1
# 0xf58084 github.com/safing/portbase/api.(*DatabaseAPI).writer+0x124 /home/user/git/safing/portbase/api/database.go:217
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf1cbc4 github.com/safing/portbase/modules.(*Module).StartWorker.func1+0x64 /home/user/git/safing/portbase/modules/worker.go:27
2 @ 0xb9de1a 0xbade2f 0xf59b65 0xf59772 0xbcfba1
# 0xf59b64 github.com/safing/portbase/api.(*DatabaseAPI).processSub+0x224 /home/user/git/safing/portbase/api/database.go:415
# 0xf59771 github.com/safing/portbase/api.(*DatabaseAPI).handleSub+0xd1 /home/user/git/safing/portbase/api/database.go:387
2 @ 0xb9de1a 0xbae7f7 0xbae7e2 0xbcacee 0xbdce2f 0x1274d56 0x1274c96 0x12b0728 0x12b8b8e 0xf1adc7 0xf1a4de 0xf1cbc5 0xbcfba1
# 0xbcaced sync.runtime_SemacquireMutex+0x4d /usr/local/go/src/runtime/sema.go:71
# 0xbdce2e sync.(*Mutex).lockSlow+0x10e /usr/local/go/src/sync/mutex.go:138
# 0x1274d55 sync.(*Mutex).Lock+0xf5 /usr/local/go/src/sync/mutex.go:81
# 0x1274c95 github.com/safing/portmaster/network.(*Connection).HandlePacket+0x35 /home/user/git/safing/portmaster/network/connection.go:602
# 0x12b0727 github.com/safing/portmaster/firewall.handlePacket+0x307 /home/user/git/safing/portmaster/firewall/interception.go:121
# 0x12b8b8d github.com/safing/portmaster/firewall.packetHandler.func1+0x4d /home/user/git/safing/portmaster/firewall/interception.go:527
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf1cbc4 github.com/safing/portbase/modules.(*Module).StartWorker.func1+0x64 /home/user/git/safing/portbase/modules/worker.go:27
1 @ 0xb64875 0xbcc349 0xec4e1a 0x12a4f0f 0x12a3b31 0xbcfba1
# 0xbcc348 syscall.Syscall+0xe8 /usr/local/go/src/runtime/syscall_windows.go:188
# 0xec4e19 golang.org/x/sys/windows.(*Proc).Call+0x139 /home/user/go/pkg/mod/golang.org/x/sys@v0.0.0-20211124211545-fe61309f8881/windows/dll_windows.go:170
# 0x12a4f0e github.com/safing/portmaster/firewall/interception/windowskext.RecvVerdictRequest+0x16e /home/user/git/safing/portmaster/firewall/interception/windowskext/kext.go:167
# 0x12a3b30 github.com/safing/portmaster/firewall/interception/windowskext.Handler+0xb0 /home/user/git/safing/portmaster/firewall/interception/windowskext/handler.go:59
1 @ 0xb64875 0xbcc492 0xbe8b65 0xbe65ef 0xc0e751 0xc163fe 0xc163d1 0xd9dd8b 0xf7080c 0xbcfba1
# 0xbcc491 syscall.Syscall6+0xf1 /usr/local/go/src/runtime/syscall_windows.go:201
# 0xbe8b64 syscall.ReadFile+0x104 /usr/local/go/src/syscall/zsyscall_windows.go:313
# 0xbe65ee syscall.Read+0x6e /usr/local/go/src/syscall/syscall_windows.go:369
# 0xc0e750 internal/poll.(*FD).Read+0x230 /usr/local/go/src/internal/poll/fd_windows.go:427
# 0xc163fd os.(*File).read+0x7d /usr/local/go/src/os/file_posix.go:31
# 0xc163d0 os.(*File).Read+0x50 /usr/local/go/src/os/file.go:116
# 0xd9dd8a bufio.(*Scanner).Scan+0xaa /usr/local/go/src/bufio/scan.go:214
# 0xf7080b github.com/safing/portbase/run.inputSignals+0x8b /home/user/git/safing/portbase/run/main.go:116
1 @ 0xb6d053 0xbcb429 0xf6ff89 0xbcfba1
# 0xbcb428 os/signal.signal_recv+0xa8 /usr/local/go/src/runtime/sigqueue.go:147
# 0xf6ff88 os/signal.loop+0x28 /usr/local/go/src/os/signal/signal_unix.go:23
1 @ 0xb9de1a 0xb66ada 0xb6670b 0x114e4cc 0xf1adc7 0xf1a811 0xbcfba1
# 0x114e4cb github.com/safing/portmaster/resolver.listenToMDNS+0x54b /home/user/git/safing/portmaster/resolver/resolver-mdns.go:130
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xb93e65 0xbc9365 0xc0c30c 0xc0d645 0xc0e81f 0xd01dd6 0xd10e35 0x1150793 0x115ceb1 0xf1adc7 0xf1a811 0xbcfba1
# 0xbc9364 internal/poll.runtime_pollWait+0x64 /usr/local/go/src/runtime/netpoll.go:222
# 0xc0c30b internal/poll.(*pollDesc).wait+0x4b /usr/local/go/src/internal/poll/fd_poll_runtime.go:87
# 0xc0d644 internal/poll.execIO+0x104 /usr/local/go/src/internal/poll/fd_windows.go:175
# 0xc0e81e internal/poll.(*FD).Read+0x2fe /usr/local/go/src/internal/poll/fd_windows.go:441
# 0xd01dd5 net.(*netFD).Read+0x55 /usr/local/go/src/net/fd_posix.go:55
# 0xd10e34 net.(*conn).Read+0x94 /usr/local/go/src/net/net.go:182
# 0x1150792 github.com/safing/portmaster/resolver.listenForDNSPackets+0x92 /home/user/git/safing/portmaster/resolver/resolver-mdns.go:328
# 0x115ceb0 github.com/safing/portmaster/resolver.listenToMDNS.func1+0x50 /home/user/git/safing/portmaster/resolver/resolver-mdns.go:86
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xb93e65 0xbc9365 0xc0c30c 0xc0d645 0xc0e81f 0xd01dd6 0xd10e35 0x1150793 0x115cfb1 0xf1adc7 0xf1a811 0xbcfba1
# 0xbc9364 internal/poll.runtime_pollWait+0x64 /usr/local/go/src/runtime/netpoll.go:222
# 0xc0c30b internal/poll.(*pollDesc).wait+0x4b /usr/local/go/src/internal/poll/fd_poll_runtime.go:87
# 0xc0d644 internal/poll.execIO+0x104 /usr/local/go/src/internal/poll/fd_windows.go:175
# 0xc0e81e internal/poll.(*FD).Read+0x2fe /usr/local/go/src/internal/poll/fd_windows.go:441
# 0xd01dd5 net.(*netFD).Read+0x55 /usr/local/go/src/net/fd_posix.go:55
# 0xd10e34 net.(*conn).Read+0x94 /usr/local/go/src/net/net.go:182
# 0x1150792 github.com/safing/portmaster/resolver.listenForDNSPackets+0x92 /home/user/git/safing/portmaster/resolver/resolver-mdns.go:328
# 0x115cfb0 github.com/safing/portmaster/resolver.listenToMDNS.func3+0x50 /home/user/git/safing/portmaster/resolver/resolver-mdns.go:108
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xb93e65 0xbc9365 0xc0c30c 0xc0d645 0xc0e81f 0xd01dd6 0xd10e35 0x1150793 0x115d031 0xf1adc7 0xf1a811 0xbcfba1
# 0xbc9364 internal/poll.runtime_pollWait+0x64 /usr/local/go/src/runtime/netpoll.go:222
# 0xc0c30b internal/poll.(*pollDesc).wait+0x4b /usr/local/go/src/internal/poll/fd_poll_runtime.go:87
# 0xc0d644 internal/poll.execIO+0x104 /usr/local/go/src/internal/poll/fd_windows.go:175
# 0xc0e81e internal/poll.(*FD).Read+0x2fe /usr/local/go/src/internal/poll/fd_windows.go:441
# 0xd01dd5 net.(*netFD).Read+0x55 /usr/local/go/src/net/fd_posix.go:55
# 0xd10e34 net.(*conn).Read+0x94 /usr/local/go/src/net/net.go:182
# 0x1150792 github.com/safing/portmaster/resolver.listenForDNSPackets+0x92 /home/user/git/safing/portmaster/resolver/resolver-mdns.go:328
# 0x115d030 github.com/safing/portmaster/resolver.listenToMDNS.func4+0x50 /home/user/git/safing/portmaster/resolver/resolver-mdns.go:119
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xb93e65 0xbc9365 0xc0c30c 0xc0d645 0xc0e81f 0xd01dd6 0xd10e35 0xe094df 0xbcfba1
# 0xbc9364 internal/poll.runtime_pollWait+0x64 /usr/local/go/src/runtime/netpoll.go:222
# 0xc0c30b internal/poll.(*pollDesc).wait+0x4b /usr/local/go/src/internal/poll/fd_poll_runtime.go:87
# 0xc0d644 internal/poll.execIO+0x104 /usr/local/go/src/internal/poll/fd_windows.go:175
# 0xc0e81e internal/poll.(*FD).Read+0x2fe /usr/local/go/src/internal/poll/fd_windows.go:441
# 0xd01dd5 net.(*netFD).Read+0x55 /usr/local/go/src/net/fd_posix.go:55
# 0xd10e34 net.(*conn).Read+0x94 /usr/local/go/src/net/net.go:182
# 0xe094de net/http.(*connReader).backgroundRead+0x5e /usr/local/go/src/net/http/server.go:690
1 @ 0xb9de1a 0xb93e65 0xbc9365 0xc0c30c 0xc0d645 0xc0f359 0xd01f05 0xd1b425 0xd19b85 0xfbdae5 0xfa89b9 0xfa5d6a 0xfa754f 0xfa65ba 0x12c0765 0xf1adc7 0xf1a811 0xbcfba1
# 0xbc9364 internal/poll.runtime_pollWait+0x64 /usr/local/go/src/runtime/netpoll.go:222
# 0xc0c30b internal/poll.(*pollDesc).wait+0x4b /usr/local/go/src/internal/poll/fd_poll_runtime.go:87
# 0xc0d644 internal/poll.execIO+0x104 /usr/local/go/src/internal/poll/fd_windows.go:175
# 0xc0f358 internal/poll.(*FD).ReadFrom+0x118 /usr/local/go/src/internal/poll/fd_windows.go:581
# 0xd01f04 net.(*netFD).readFrom+0x64 /usr/local/go/src/net/fd_posix.go:61
# 0xd1b424 net.(*UDPConn).readFrom+0x64 /usr/local/go/src/net/udpsock_posix.go:47
# 0xd19b84 net.(*UDPConn).ReadFrom+0x64 /usr/local/go/src/net/udpsock.go:118
# 0xfbdae4 github.com/miekg/dns.ReadFromSessionUDP+0x64 /home/user/go/pkg/mod/github.com/miekg/dns@v1.1.43/udp_windows.go:19
# 0xfa89b8 github.com/miekg/dns.(*Server).readUDP+0xd8 /home/user/go/pkg/mod/github.com/miekg/dns@v1.1.43/server.go:687
# 0xfa5d69 github.com/miekg/dns.defaultReader.ReadUDP+0x49 /home/user/go/pkg/mod/github.com/miekg/dns@v1.1.43/server.go:174
# 0xfa754e github.com/miekg/dns.(*Server).serveUDP+0x20e /home/user/go/pkg/mod/github.com/miekg/dns@v1.1.43/server.go:501
# 0xfa65b9 github.com/miekg/dns.(*Server).ListenAndServe+0x339 /home/user/go/pkg/mod/github.com/miekg/dns@v1.1.43/server.go:330
# 0x12c0764 github.com/safing/portmaster/nameserver.startListener.func1+0x44 /home/user/git/safing/portmaster/nameserver/module.go:114
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xb93e65 0xbc9365 0xc0c30c 0xc0d645 0xc10c59 0xc10f0a 0xd03565 0xd18e59 0xd1796b 0xe13c8e 0xe139be 0xf62f54 0xf1adc7 0xf1a4de 0xf60b76 0xbcfba1
# 0xbc9364 internal/poll.runtime_pollWait+0x64 /usr/local/go/src/runtime/netpoll.go:222
# 0xc0c30b internal/poll.(*pollDesc).wait+0x4b /usr/local/go/src/internal/poll/fd_poll_runtime.go:87
# 0xc0d644 internal/poll.execIO+0x104 /usr/local/go/src/internal/poll/fd_windows.go:175
# 0xc10c58 internal/poll.(*FD).acceptOne+0x98 /usr/local/go/src/internal/poll/fd_windows.go:810
# 0xc10f09 internal/poll.(*FD).Accept+0x169 /usr/local/go/src/internal/poll/fd_windows.go:844
# 0xd03564 net.(*netFD).accept+0x84 /usr/local/go/src/net/fd_windows.go:139
# 0xd18e58 net.(*TCPListener).accept+0x38 /usr/local/go/src/net/tcpsock_posix.go:139
# 0xd1796a net.(*TCPListener).Accept+0x6a /usr/local/go/src/net/tcpsock.go:261
# 0xe13c8d net/http.(*Server).Serve+0x26d /usr/local/go/src/net/http/server.go:2937
# 0xe139bd net/http.(*Server).ListenAndServe+0xbd /usr/local/go/src/net/http/server.go:2866
# 0xf62f53 github.com/safing/portbase/api.Serve.func1+0x33 /home/user/git/safing/portbase/api/router.go:63
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf60b75 github.com/safing/portbase/api.Serve+0x1d5 /home/user/git/safing/portbase/api/router.go:62
1 @ 0xb9de1a 0xbade2f 0x10cee15 0xf1adc7 0xf1a811 0xbcfba1
# 0x10cee14 github.com/safing/portbase/notifications.cleaner+0x114 /home/user/git/safing/portbase/notifications/cleaner.go:13
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xbade2f 0x10f3cf8 0xf1adc7 0xf1a811 0xbcfba1
# 0x10f3cf7 github.com/safing/portmaster/intel/geoip.(*updateWorker).run+0x117 /home/user/git/safing/portmaster/intel/geoip/database.go:173
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xbade2f 0x10fa5c5 0xf1adc7 0xf1a811 0xbcfba1
# 0x10fa5c4 github.com/safing/portmaster/netenv.monitorNetworkChanges+0x164 /home/user/git/safing/portmaster/netenv/network-change.go:48
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xbade2f 0x110dcfc 0xf1adc7 0xf1a4de 0xf1cbc5 0xbcfba1
# 0x110dcfb github.com/safing/portmaster/status.autoPilot+0xdb /home/user/git/safing/portmaster/status/autopilot.go:16
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf1cbc4 github.com/safing/portbase/modules.(*Module).StartWorker.func1+0x64 /home/user/git/safing/portbase/modules/worker.go:27
1 @ 0xb9de1a 0xbade2f 0x114e9c5 0x115d0a5 0xf1adc7 0xf1a811 0xbcfba1
# 0x114e9c4 github.com/safing/portmaster/resolver.handleMDNSMessages+0x104 /home/user/git/safing/portmaster/resolver/resolver-mdns.go:137
# 0x115d0a4 github.com/safing/portmaster/resolver.listenToMDNS.func5+0x44 /home/user/git/safing/portmaster/resolver/resolver-mdns.go:126
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xbade2f 0x11b1248 0xf1adc7 0xf1a811 0xbcfba1
# 0x11b1247 github.com/safing/portmaster/profile.cleanActiveProfiles+0x187 /home/user/git/safing/portmaster/profile/active.go:84
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xbade2f 0x124c1a5 0xbcfba1
# 0x124c1a4 github.com/xtaci/kcp-go/v5.(*TimedSched).prepend+0x284 /home/user/go/pkg/mod/github.com/xtaci/kcp-go/v5@v5.6.1/timedsched.go:103
1 @ 0xb9de1a 0xbade2f 0x127733a 0xf1adc7 0xf1a811 0xbcfba1
# 0x1277339 github.com/safing/portmaster/network.openDNSRequestWriter+0x119 /home/user/git/safing/portmaster/network/dns.go:91
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xbade2f 0x12b2aac 0xf1adc7 0xf1a4de 0xf1cbc5 0xbcfba1
# 0x12b2aab github.com/safing/portmaster/firewall.packetHandler+0x10b /home/user/git/safing/portmaster/firewall/interception.go:522
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf1cbc4 github.com/safing/portbase/modules.(*Module).StartWorker.func1+0x64 /home/user/git/safing/portbase/modules/worker.go:27
1 @ 0xb9de1a 0xbade2f 0x12b2da9 0xf1adc7 0xf1a4de 0xf1cbc5 0xbcfba1
# 0x12b2da8 github.com/safing/portmaster/firewall.statLogger+0x248 /home/user/git/safing/portmaster/firewall/interception.go:536
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf1cbc4 github.com/safing/portbase/modules.(*Module).StartWorker.func1+0x64 /home/user/git/safing/portbase/modules/worker.go:27
1 @ 0xb9de1a 0xbade2f 0xd0edc5 0xd0e4ed 0xd0e497 0x10fc1a5 0x10fb9fb 0xf1adc7 0xf1a811 0xbcfba1
# 0xd0edc4 net.(*Resolver).lookupIPAddr+0x684 /usr/local/go/src/net/lookup.go:299
# 0xd0e4ec net.(*Resolver).LookupIPAddr+0x8c /usr/local/go/src/net/lookup.go:204
# 0xd0e496 net.LookupIP+0x36 /usr/local/go/src/net/lookup.go:190
# 0x10fc1a4 github.com/safing/portmaster/netenv.checkOnlineStatus+0x504 /home/user/git/safing/portmaster/netenv/online-status.go:507
# 0x10fb9fa github.com/safing/portmaster/netenv.monitorOnlineStatus+0x5a /home/user/git/safing/portmaster/netenv/online-status.go:369
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xbade2f 0xd0edc5 0xd0e4ed 0xd0e497 0x11c6cb1 0xf1adc7 0xf1a4de 0xf1cbc5 0xbcfba1
# 0xd0edc4 net.(*Resolver).lookupIPAddr+0x684 /usr/local/go/src/net/lookup.go:299
# 0xd0e4ec net.(*Resolver).LookupIPAddr+0x8c /usr/local/go/src/net/lookup.go:204
# 0xd0e496 net.LookupIP+0x36 /usr/local/go/src/net/lookup.go:190
# 0x11c6cb0 github.com/safing/portmaster/compat.selfcheck.func2+0xb0 /home/user/git/safing/portmaster/compat/selfcheck.go:123
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf1cbc4 github.com/safing/portbase/modules.(*Module).StartWorker.func1+0x64 /home/user/git/safing/portbase/modules/worker.go:27
1 @ 0xb9de1a 0xbade2f 0xeeaeb4 0xeeaa98 0xbcfba1
# 0xeeaeb3 github.com/safing/portbase/log.writer+0x3b3 /home/user/git/safing/portbase/log/output.go:156
# 0xeeaa97 github.com/safing/portbase/log.writerManager+0x97 /home/user/git/safing/portbase/log/output.go:113
1 @ 0xb9de1a 0xbade2f 0xf13cd8 0xbcfba1
# 0xf13cd7 github.com/safing/portbase/modules.microTaskScheduler+0x1b7 /home/user/git/safing/portbase/modules/microtasks.go:184
1 @ 0xb9de1a 0xbade2f 0xf19f25 0xbcfba1
# 0xf19f24 github.com/safing/portbase/modules.taskQueueHandler+0x1c4 /home/user/git/safing/portbase/modules/tasks.go:447
1 @ 0xb9de1a 0xbade2f 0xf1a1fe 0xbcfba1
# 0xf1a1fd github.com/safing/portbase/modules.taskScheduleHandler+0xfd /home/user/git/safing/portbase/modules/tasks.go:497
1 @ 0xb9de1a 0xbade2f 0xf24c9d 0xf1adc7 0xf1a811 0xbcfba1
# 0xf24c9c github.com/safing/portbase/rng.fullFeeder+0x15c /home/user/git/safing/portbase/rng/fullfeed.go:25
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xbade2f 0xf25725 0xf1adc7 0xf1a811 0xbcfba1
# 0xf25724 github.com/safing/portbase/rng.osFeeder+0x1e4 /home/user/git/safing/portbase/rng/osfeeder.go:27
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xbade2f 0xf26054 0xf1adc7 0xf1a811 0xbcfba1
# 0xf26053 github.com/safing/portbase/rng.tickFeeder+0x253 /home/user/git/safing/portbase/rng/tickfeeder.go:60
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xbade2f 0xf70518 0x12c1290 0xb9da49 0xbcfba1
# 0xf70517 github.com/safing/portbase/run.Run+0x237 /home/user/git/safing/portbase/run/main.go:66
# 0x12c128f main.main+0xcf /home/user/git/safing/portmaster/cmds/portmaster-core/main.go:31
# 0xb9da48 runtime.main+0x208 /usr/local/go/src/runtime/proc.go:204
1 @ 0xb9de1a 0xbae7f7 0xbae7e2 0xbcacee 0x11b8c93 0x11b8c45 0x11c4959 0x12ac4f1 0x12ac4cf 0x12b4793 0x12b342d 0x12b30c5 0x12b227e 0x1274e6c 0x1279611 0xf1adc7 0xf1a4de 0xf1cbc5 0xbcfba1
# 0xbcaced sync.runtime_SemacquireMutex+0x4d /usr/local/go/src/runtime/sema.go:71
# 0x11b8c92 sync.(*RWMutex).RLock+0xb2 /usr/local/go/src/sync/rwmutex.go:50
# 0x11b8c44 github.com/safing/portmaster/profile.(*LayeredProfile).LocalProfile+0x64 /home/user/git/safing/portmaster/profile/profile-layered.go:162
# 0x11c4958 github.com/safing/portmaster/compat.(*appIssue).notify+0x58 /home/user/git/safing/portmaster/compat/notify.go:104
# 0x12ac4f0 github.com/safing/portmaster/compat.ReportSecureDNSBypassIssue+0xf0 /home/user/git/safing/portmaster/compat/callbacks.go:31
# 0x12ac4ce github.com/safing/portmaster/firewall.PreventBypassing+0xce /home/user/git/safing/portmaster/firewall/bypassing.go:35
# 0x12b4792 github.com/safing/portmaster/firewall.checkBypassPrevention+0x72 /home/user/git/safing/portmaster/firewall/master.go:359
# 0x12b342c github.com/safing/portmaster/firewall.runDeciders+0xec /home/user/git/safing/portmaster/firewall/master.go:126
# 0x12b30c4 github.com/safing/portmaster/firewall.DecideOnConnection+0x2c4 /home/user/git/safing/portmaster/firewall/master.go:96
# 0x12b227d github.com/safing/portmaster/firewall.initialHandler+0x83d /home/user/git/safing/portmaster/firewall/interception.go:367
# 0x1274e6b github.com/safing/portmaster/network.(*Connection).packetHandler+0xeb /home/user/git/safing/portmaster/network/connection.go:625
# 0x1279610 github.com/safing/portmaster/network.(*Connection).SetFirewallHandler.func1+0x30 /home/user/git/safing/portmaster/network/connection.go:587
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf1cbc4 github.com/safing/portbase/modules.(*Module).StartWorker.func1+0x64 /home/user/git/safing/portbase/modules/worker.go:27
1 @ 0xb9de1a 0xbae7f7 0xbae7e2 0xbcacee 0xbdce2f 0x1279345 0x127905d 0xf13aa2 0xf13877 0x1272576 0x12723ba 0xf1adc7 0xf1a811 0xbcfba1
# 0xbcaced sync.runtime_SemacquireMutex+0x4d /usr/local/go/src/runtime/sema.go:71
# 0xbdce2e sync.(*Mutex).lockSlow+0x10e /usr/local/go/src/sync/mutex.go:138
# 0x1279344 sync.(*Mutex).Lock+0x504 /usr/local/go/src/sync/mutex.go:81
# 0x127905c github.com/safing/portmaster/network.cleanConnections.func1+0x21c /home/user/git/safing/portmaster/network/clean.go:51
# 0xf13aa1 github.com/safing/portbase/modules.(*Module).runMicroTask+0xa1 /home/user/git/safing/portbase/modules/microtasks.go:158
# 0xf13876 github.com/safing/portbase/modules.(*Module).RunMediumPriorityMicroTask+0x96 /home/user/git/safing/portbase/modules/microtasks.go:106
# 0x1272575 github.com/safing/portmaster/network.cleanConnections+0x95 /home/user/git/safing/portmaster/network/clean.go:43
# 0x12723b9 github.com/safing/portmaster/network.connectionCleaner+0x59 /home/user/git/safing/portmaster/network/clean.go:30
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xbae7f7 0xbae7e2 0xbcacee 0xbdce2f 0xbdcd0e 0xf5b1bf 0xf59bb6 0xf5a1d7 0xbcfba1
# 0xbcaced sync.runtime_SemacquireMutex+0x4d /usr/local/go/src/runtime/sema.go:71
# 0xbdce2e sync.(*Mutex).lockSlow+0x10e /usr/local/go/src/sync/mutex.go:138
# 0xbdcd0d sync.(*Mutex).Lock+0x4d /usr/local/go/src/sync/mutex.go:81
# 0xf5b1be github.com/safing/portbase/api.marshalRecord+0x7e /home/user/git/safing/portbase/api/database.go:631
# 0xf59bb5 github.com/safing/portbase/api.(*DatabaseAPI).processSub+0x275 /home/user/git/safing/portbase/api/database.go:424
# 0xf5a1d6 github.com/safing/portbase/api.(*DatabaseAPI).handleQsub+0x136 /home/user/git/safing/portbase/api/database.go:478
1 @ 0xb9de1a 0xbae7f7 0xbae7e2 0xbcacee 0xbdce2f 0xbde5b5 0xbde549 0x11c6825 0x11c6abf 0xf1adc7 0xf1a4de 0xf1cbc5 0xbcfba1
# 0xbcaced sync.runtime_SemacquireMutex+0x4d /usr/local/go/src/runtime/sema.go:71
# 0xbdce2e sync.(*Mutex).lockSlow+0x10e /usr/local/go/src/sync/mutex.go:138
# 0xbde5b4 sync.(*Mutex).Lock+0x94 /usr/local/go/src/sync/mutex.go:81
# 0xbde548 sync.(*RWMutex).Lock+0x28 /usr/local/go/src/sync/rwmutex.go:98
# 0x11c6824 github.com/safing/portmaster/compat.(*appIssue).notify.func1.1+0x64 /home/user/git/safing/portmaster/compat/notify.go:153
# 0x11c6abe github.com/safing/portmaster/compat.(*appIssue).notify.func1+0x3e /home/user/git/safing/portmaster/compat/notify.go:162
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf1cbc4 github.com/safing/portbase/modules.(*Module).StartWorker.func1+0x64 /home/user/git/safing/portbase/modules/worker.go:27
1 @ 0xb9de1a 0xbae7f7 0xbae7e2 0xbcacee 0xbde5aa 0x11b8dea 0x11bdaa5 0xf1adc7 0xf1a811 0xbcfba1
# 0xbcaced sync.runtime_SemacquireMutex+0x4d /usr/local/go/src/runtime/sema.go:71
# 0xbde5a9 sync.(*RWMutex).Lock+0x89 /usr/local/go/src/sync/rwmutex.go:103
# 0x11b8de9 github.com/safing/portmaster/profile.(*LayeredProfile).increaseRevisionCounter+0x109 /home/user/git/safing/portmaster/profile/profile-layered.go:176
# 0x11bdaa4 github.com/safing/portmaster/profile.startProfileUpdateChecker.func1+0x364 /home/user/git/safing/portmaster/profile/database.go:95
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a810 github.com/safing/portbase/modules.(*Module).runServiceWorker+0x130 /home/user/git/safing/portbase/modules/worker.go:78
1 @ 0xb9de1a 0xbae7f7 0xbae7e2 0xbcacee 0xbde5aa 0x11c6825 0x11c6abf 0xf1adc7 0xf1a4de 0xf1cbc5 0xbcfba1
# 0xbcaced sync.runtime_SemacquireMutex+0x4d /usr/local/go/src/runtime/sema.go:71
# 0xbde5a9 sync.(*RWMutex).Lock+0x89 /usr/local/go/src/sync/rwmutex.go:103
# 0x11c6824 github.com/safing/portmaster/compat.(*appIssue).notify.func1.1+0x64 /home/user/git/safing/portmaster/compat/notify.go:153
# 0x11c6abe github.com/safing/portmaster/compat.(*appIssue).notify.func1+0x3e /home/user/git/safing/portmaster/compat/notify.go:162
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf1cbc4 github.com/safing/portbase/modules.(*Module).StartWorker.func1+0x64 /home/user/git/safing/portbase/modules/worker.go:27
1 @ 0xbc8fa5 0xf4910a 0xf48ea7 0xf45978 0xf52016 0x11a9213 0xf5d424 0xf5c9d6 0xf6188f 0xf62fcc 0xf1adc7 0xf1a4de 0xf60cc5 0xe138ca 0xe0f86d 0xbcfba1
# 0xbc8fa4 runtime/pprof.runtime_goroutineProfileWithLabels+0x64 /usr/local/go/src/runtime/mprof.go:716
# 0xf49109 runtime/pprof.writeRuntimeProfile+0xe9 /usr/local/go/src/runtime/pprof/pprof.go:724
# 0xf48ea6 runtime/pprof.writeGoroutine+0xa6 /usr/local/go/src/runtime/pprof/pprof.go:684
# 0xf45977 runtime/pprof.(*Profile).WriteTo+0x3f7 /usr/local/go/src/runtime/pprof/pprof.go:331
# 0xf52015 github.com/safing/portbase/utils/debug.(*Info).AddGoroutineStack+0x95 /home/user/git/safing/portbase/utils/debug/debug.go:132
# 0x11a9212 github.com/safing/portmaster/core.debugInfo+0x112 /home/user/git/safing/portmaster/core/api.go:91
# 0xf5d423 github.com/safing/portbase/api.(*Endpoint).ServeHTTP+0xa23 /home/user/git/safing/portbase/api/endpoints.go:438
# 0xf5c9d5 github.com/safing/portbase/api.(*endpointHandler).ServeHTTP+0xb5 /home/user/git/safing/portbase/api/endpoints.go:357
# 0xf6188e github.com/safing/portbase/api.(*mainHandler).handle+0xbae /home/user/git/safing/portbase/api/router.go:197
# 0xf62fcb github.com/safing/portbase/api.(*mainHandler).ServeHTTP.func1+0x4b /home/user/git/safing/portbase/api/router.go:81
# 0xf1adc6 github.com/safing/portbase/modules.(*Module).runWorker+0xa6 /home/user/git/safing/portbase/modules/worker.go:119
# 0xf1a4dd github.com/safing/portbase/modules.(*Module).RunWorker+0x9d /home/user/git/safing/portbase/modules/worker.go:47
# 0xf60cc4 github.com/safing/portbase/api.(*mainHandler).ServeHTTP+0xa4 /home/user/git/safing/portbase/api/router.go:80
# 0xe138c9 net/http.serverHandler.ServeHTTP+0xa9 /usr/local/go/src/net/http/server.go:2843
# 0xe0f86c net/http.(*conn).serve+0x8ac /usr/local/go/src/net/http/server.go:1925
```
</details>
[logs.zip](https://github.com/safing/portmaster/files/7765280/logs.zip)
| non_priority | compatibility with cisco secure endpoint cisco amp pre submit checklist check applicable sources for existing issues n a n a what worked the portmaster ui and core service launch the portmaster also correctly identifies the network traffic by dns name as far as i can tell all connections displayed are accurate what did not work blocked domains are not successfully blocked furthermore dns resolution takes an exponentially longer time then without the portmaster installed possibly timing out before resorting back to the cisco secure endpoint after an restart of the core service no network traffic is allowed anymore and after shutting down the portmaster everything starts working again when trying to start the portmaster back up again the core service won t start unless killing it completely and starting it back up again rebooting doesn t work killing the cisco processes seems to work but it forces itself back up again thus killing the network connection the following three errors are shown detected system dns client bypass attempt something is interfering with the portmaster limited network connectivity i feel like for now it is best to consider cisco secure endpoint as incompatible at least on windows debug information version portmaster version commit tags built with gc windows using options main go by user docker on licensed under the license the source code is available here platform microsoft windows enterprise build system microsoft windows enterprise windows standalone workstation build kernel build status trusted activesecuritylevel trusted selectedsecuritylevel off threatmitigationlevel trusted captiveportal onlinestatus limited resolvers cloudflare dot config failing false compat module error message self check dns integration check failed did not receive test query after timestamp cet m modulename compat taskname selfcheck tasktype severity error panicvalue s stacktrace goroutine runtime debug stack usr local go src runtime debug stack go github com safing portbase modules module newerrormessage home user git safing portbase modules error go github com safing portmaster compat systemissue notify home user git safing portmaster compat notify go github com safing portmaster compat selfchecktaskfunc home user git safing portmaster compat module go github com safing portbase modules task executewithlocking home user git safing portbase modules tasks go created by github com safing portbase modules task runwithlocking home user git safing portbase modules tasks go unexpected logs ine status warn netenv dns check query failed lookup one one one one no such host ine status warn netenv dns fallback check query failed lookup dns check safing io no such host ine status warn netenv dns check query failed lookup one one one one no such host ine status warn netenv dns fallback check query failed lookup dns check safing io no such host ine status warn netenv dns check query failed lookup one one one one no such host pat module erro compat self check dns integration check failed did not receive test query after ine status warn netenv dns fallback check query failed lookup dns check safing io no such host ine status warn netenv dns check query failed lookup one one one one no such host ine status warn netenv dns fallback check query failed lookup dns check safing io no such host pat module erro compat self check dns integration check failed did not receive test query after current time goroutine stack goroutine profile total sync runtime semacquire usr local go src runtime sema go sync waitgroup wait usr local go src sync waitgroup go golang org x sync singleflight group do home user go pkg mod golang org x sync singleflight singleflight go github com safing portmaster firewall getconnection home user git safing portmaster firewall interception go github com safing portmaster firewall handlepacket home user git safing portmaster firewall interception go github com safing portmaster firewall packethandler home user git safing portmaster firewall interception go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module startworker home user git safing portbase modules worker go sync runtime semacquiremutex usr local go src runtime sema go sync rwmutex rlock usr local go src sync rwmutex go github com safing portmaster profile layeredprofile localprofile home user git safing portmaster profile profile layered go github com safing portmaster process process updateprofilemetadata home user git safing portmaster process profile go github com safing portmaster process process getprofile home user git safing portmaster process profile go github com safing portmaster process getprocessbyconnection home user git safing portmaster process find go github com safing portmaster network newconnectionfromfirstpacket home user git safing portmaster network connection go github com safing portmaster firewall getconnection home user git safing portmaster firewall interception go golang org x sync singleflight group docall home user go pkg mod golang org x sync singleflight singleflight go golang org x sync singleflight group docall home user go pkg mod golang org x sync singleflight singleflight go golang org x sync singleflight group do home user go pkg mod golang org x sync singleflight singleflight go github com safing portmaster firewall getconnection home user git safing portmaster firewall interception go github com safing portmaster firewall handlepacket home user git safing portmaster firewall interception go github com safing portmaster firewall packethandler home user git safing portmaster firewall interception go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module startworker home user git safing portbase modules worker go sync runtime semacquiremutex usr local go src runtime sema go sync mutex lockslow usr local go src sync mutex go sync mutex lock usr local go src sync mutex go github com safing portmaster process process getprofile home user git safing portmaster process profile go github com safing portmaster process getprocessbyconnection home user git safing portmaster process find go github com safing portmaster network newconnectionfromfirstpacket home user git safing portmaster network connection go github com safing portmaster firewall getconnection home user git safing portmaster firewall interception go golang org x sync singleflight group docall home user go pkg mod golang org x sync singleflight singleflight go golang org x sync singleflight group docall home user go pkg mod golang org x sync singleflight singleflight go golang org x sync singleflight group do home user go pkg mod golang org x sync singleflight singleflight go github com safing portmaster firewall getconnection home user git safing portmaster firewall interception go github com safing portmaster firewall handlepacket home user git safing portmaster firewall interception go github com safing portmaster firewall packethandler home user git safing portmaster firewall interception go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module startworker home user git safing portbase modules worker go github com safing portbase api databaseapi processsub home user git safing portbase api database go github com safing portbase api databaseapi handleqsub home user git safing portbase api database go github com xtaci kcp go timedsched sched home user go pkg mod github com xtaci kcp go timedsched go sync runtime semacquiremutex usr local go src runtime sema go sync mutex lockslow usr local go src sync mutex go sync mutex lock usr local go src sync mutex go sync rwmutex lock usr local go src sync rwmutex go github com safing portmaster profile profile layeredprofile home user git safing portmaster profile profile go github com safing portmaster process process getprofile home user git safing portmaster process profile go github com safing portmaster process getprocessbyconnection home user git safing portmaster process find go github com safing portmaster network newconnectionfromfirstpacket home user git safing portmaster network connection go github com safing portmaster firewall getconnection home user git safing portmaster firewall interception go golang org x sync singleflight group docall home user go pkg mod golang org x sync singleflight singleflight go golang org x sync singleflight group docall home user go pkg mod golang org x sync singleflight singleflight go golang org x sync singleflight group do home user go pkg mod golang org x sync singleflight singleflight go github com safing portmaster firewall getconnection home user git safing portmaster firewall interception go github com safing portmaster firewall handlepacket home user git safing portmaster firewall interception go github com safing portmaster firewall packethandler home user git safing portmaster firewall interception go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module startworker home user git safing portbase modules worker go syscall usr local go src runtime syscall windows go syscall getaddrinfow usr local go src syscall zsyscall windows go net resolver lookupip usr local go src net lookup windows go net resolver lookupip usr local go src net lookup windows go internal poll runtime pollwait usr local go src runtime netpoll go internal poll polldesc wait usr local go src internal poll fd poll runtime go internal poll execio usr local go src internal poll fd windows go internal poll fd read usr local go src internal poll fd windows go net netfd read usr local go src net fd posix go net conn read usr local go src net net go bufio reader fill usr local go src bufio bufio go bufio reader peek usr local go src bufio bufio go github com gorilla websocket conn read home user go pkg mod github com gorilla websocket conn go github com gorilla websocket conn advanceframe home user go pkg mod github com gorilla websocket conn go github com gorilla websocket conn nextreader home user go pkg mod github com gorilla websocket conn go github com gorilla websocket conn readmessage home user go pkg mod github com gorilla websocket conn go github com safing portbase api databaseapi handler home user git safing portbase api database go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module startworker home user git safing portbase modules worker go net resolver lookupip usr local go src net lookup windows go net glob usr local go src net hook go net resolver lookupipaddr usr local go src net lookup go internal singleflight group docall usr local go src internal singleflight singleflight go github com safing portbase database interface delayedcachewriter home user git safing portbase database interface cache go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runserviceworker home user git safing portbase modules worker go github com safing portbase rng feeder run home user git safing portbase rng entropy go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runserviceworker home user git safing portbase modules worker go github com safing portbase api databaseapi writer home user git safing portbase api database go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module startworker home user git safing portbase modules worker go github com safing portbase api databaseapi processsub home user git safing portbase api database go github com safing portbase api databaseapi handlesub home user git safing portbase api database go sync runtime semacquiremutex usr local go src runtime sema go sync mutex lockslow usr local go src sync mutex go sync mutex lock usr local go src sync mutex go github com safing portmaster network connection handlepacket home user git safing portmaster network connection go github com safing portmaster firewall handlepacket home user git safing portmaster firewall interception go github com safing portmaster firewall packethandler home user git safing portmaster firewall interception go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module startworker home user git safing portbase modules worker go syscall syscall usr local go src runtime syscall windows go golang org x sys windows proc call home user go pkg mod golang org x sys windows dll windows go github com safing portmaster firewall interception windowskext recvverdictrequest home user git safing portmaster firewall interception windowskext kext go github com safing portmaster firewall interception windowskext handler home user git safing portmaster firewall interception windowskext handler go syscall usr local go src runtime syscall windows go syscall readfile usr local go src syscall zsyscall windows go syscall read usr local go src syscall syscall windows go internal poll fd read usr local go src internal poll fd windows go os file read usr local go src os file posix go os file read usr local go src os file go bufio scanner scan usr local go src bufio scan go github com safing portbase run inputsignals home user git safing portbase run main go os signal signal recv usr local go src runtime sigqueue go os signal loop usr local go src os signal signal unix go github com safing portmaster resolver listentomdns home user git safing portmaster resolver resolver mdns go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runserviceworker home user git safing portbase modules worker go internal poll runtime pollwait usr local go src runtime netpoll go internal poll polldesc wait usr local go src internal poll fd poll runtime go internal poll execio usr local go src internal poll fd windows go internal poll fd read usr local go src internal poll fd windows go net netfd read usr local go src net fd posix go net conn read usr local go src net net go github com safing portmaster resolver listenfordnspackets home user git safing portmaster resolver resolver mdns go github com safing portmaster resolver listentomdns home user git safing portmaster resolver resolver mdns go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runserviceworker home user git safing portbase modules worker go internal poll runtime pollwait usr local go src runtime netpoll go internal poll polldesc wait usr local go src internal poll fd poll runtime go internal poll execio usr local go src internal poll fd windows go internal poll fd read usr local go src internal poll fd windows go net netfd read usr local go src net fd posix go net conn read usr local go src net net go github com safing portmaster resolver listenfordnspackets home user git safing portmaster resolver resolver mdns go github com safing portmaster resolver listentomdns home user git safing portmaster resolver resolver mdns go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runserviceworker home user git safing portbase modules worker go internal poll runtime pollwait usr local go src runtime netpoll go internal poll polldesc wait usr local go src internal poll fd poll runtime go internal poll execio usr local go src internal poll fd windows go internal poll fd read usr local go src internal poll fd windows go net netfd read usr local go src net fd posix go net conn read usr local go src net net go github com safing portmaster resolver listenfordnspackets home user git safing portmaster resolver resolver mdns go github com safing portmaster resolver listentomdns home user git safing portmaster resolver resolver mdns go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runserviceworker home user git safing portbase modules worker go internal poll runtime pollwait usr local go src runtime netpoll go internal poll polldesc wait usr local go src internal poll fd poll runtime go internal poll execio usr local go src internal poll fd windows go internal poll fd read usr local go src internal poll fd windows go net netfd read usr local go src net fd posix go net conn read usr local go src net net go net http connreader backgroundread usr local go src net http server go internal poll runtime pollwait usr local go src runtime netpoll go internal poll polldesc wait usr local go src internal poll fd poll runtime go internal poll execio usr local go src internal poll fd windows go internal poll fd readfrom usr local go src internal poll fd windows go net netfd readfrom usr local go src net fd posix go net udpconn readfrom usr local go src net udpsock posix go net udpconn readfrom usr local go src net udpsock go github com miekg dns readfromsessionudp home user go pkg mod github com miekg dns udp windows go github com miekg dns server readudp home user go pkg mod github com miekg dns server go github com miekg dns defaultreader readudp home user go pkg mod github com miekg dns server go github com miekg dns server serveudp home user go pkg mod github com miekg dns server go github com miekg dns server listenandserve home user go pkg mod github com miekg dns server go github com safing portmaster nameserver startlistener home user git safing portmaster nameserver module go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runserviceworker home user git safing portbase modules worker go internal poll runtime pollwait usr local go src runtime netpoll go internal poll polldesc wait usr local go src internal poll fd poll runtime go internal poll execio usr local go src internal poll fd windows go internal poll fd acceptone usr local go src internal poll fd windows go internal poll fd accept usr local go src internal poll fd windows go net netfd accept usr local go src net fd windows go net tcplistener accept usr local go src net tcpsock posix go net tcplistener accept usr local go src net tcpsock go net http server serve usr local go src net http server go net http server listenandserve usr local go src net http server go github com safing portbase api serve home user git safing portbase api router go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase api serve home user git safing portbase api router go github com safing portbase notifications cleaner home user git safing portbase notifications cleaner go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runserviceworker home user git safing portbase modules worker go github com safing portmaster intel geoip updateworker run home user git safing portmaster intel geoip database go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runserviceworker home user git safing portbase modules worker go github com safing portmaster netenv monitornetworkchanges home user git safing portmaster netenv network change go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runserviceworker home user git safing portbase modules worker go github com safing portmaster status autopilot home user git safing portmaster status autopilot go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module startworker home user git safing portbase modules worker go github com safing portmaster resolver handlemdnsmessages home user git safing portmaster resolver resolver mdns go github com safing portmaster resolver listentomdns home user git safing portmaster resolver resolver mdns go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runserviceworker home user git safing portbase modules worker go github com safing portmaster profile cleanactiveprofiles home user git safing portmaster profile active go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runserviceworker home user git safing portbase modules worker go github com xtaci kcp go timedsched prepend home user go pkg mod github com xtaci kcp go timedsched go github com safing portmaster network opendnsrequestwriter home user git safing portmaster network dns go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runserviceworker home user git safing portbase modules worker go github com safing portmaster firewall packethandler home user git safing portmaster firewall interception go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module startworker home user git safing portbase modules worker go github com safing portmaster firewall statlogger home user git safing portmaster firewall interception go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module startworker home user git safing portbase modules worker go net resolver lookupipaddr usr local go src net lookup go net resolver lookupipaddr usr local go src net lookup go net lookupip usr local go src net lookup go github com safing portmaster netenv checkonlinestatus home user git safing portmaster netenv online status go github com safing portmaster netenv monitoronlinestatus home user git safing portmaster netenv online status go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runserviceworker home user git safing portbase modules worker go net resolver lookupipaddr usr local go src net lookup go net resolver lookupipaddr usr local go src net lookup go net lookupip usr local go src net lookup go github com safing portmaster compat selfcheck home user git safing portmaster compat selfcheck go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module startworker home user git safing portbase modules worker go github com safing portbase log writer home user git safing portbase log output go github com safing portbase log writermanager home user git safing portbase log output go github com safing portbase modules microtaskscheduler home user git safing portbase modules microtasks go github com safing portbase modules taskqueuehandler home user git safing portbase modules tasks go github com safing portbase modules taskschedulehandler home user git safing portbase modules tasks go github com safing portbase rng fullfeeder home user git safing portbase rng fullfeed go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runserviceworker home user git safing portbase modules worker go github com safing portbase rng osfeeder home user git safing portbase rng osfeeder go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runserviceworker home user git safing portbase modules worker go github com safing portbase rng tickfeeder home user git safing portbase rng tickfeeder go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runserviceworker home user git safing portbase modules worker go github com safing portbase run run home user git safing portbase run main go main main home user git safing portmaster cmds portmaster core main go runtime main usr local go src runtime proc go sync runtime semacquiremutex usr local go src runtime sema go sync rwmutex rlock usr local go src sync rwmutex go github com safing portmaster profile layeredprofile localprofile home user git safing portmaster profile profile layered go github com safing portmaster compat appissue notify home user git safing portmaster compat notify go github com safing portmaster compat reportsecurednsbypassissue home user git safing portmaster compat callbacks go github com safing portmaster firewall preventbypassing home user git safing portmaster firewall bypassing go github com safing portmaster firewall checkbypassprevention home user git safing portmaster firewall master go github com safing portmaster firewall rundeciders home user git safing portmaster firewall master go github com safing portmaster firewall decideonconnection home user git safing portmaster firewall master go github com safing portmaster firewall initialhandler home user git safing portmaster firewall interception go github com safing portmaster network connection packethandler home user git safing portmaster network connection go github com safing portmaster network connection setfirewallhandler home user git safing portmaster network connection go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module startworker home user git safing portbase modules worker go sync runtime semacquiremutex usr local go src runtime sema go sync mutex lockslow usr local go src sync mutex go sync mutex lock usr local go src sync mutex go github com safing portmaster network cleanconnections home user git safing portmaster network clean go github com safing portbase modules module runmicrotask home user git safing portbase modules microtasks go github com safing portbase modules module runmediumprioritymicrotask home user git safing portbase modules microtasks go github com safing portmaster network cleanconnections home user git safing portmaster network clean go github com safing portmaster network connectioncleaner home user git safing portmaster network clean go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runserviceworker home user git safing portbase modules worker go sync runtime semacquiremutex usr local go src runtime sema go sync mutex lockslow usr local go src sync mutex go sync mutex lock usr local go src sync mutex go github com safing portbase api marshalrecord home user git safing portbase api database go github com safing portbase api databaseapi processsub home user git safing portbase api database go github com safing portbase api databaseapi handleqsub home user git safing portbase api database go sync runtime semacquiremutex usr local go src runtime sema go sync mutex lockslow usr local go src sync mutex go sync mutex lock usr local go src sync mutex go sync rwmutex lock usr local go src sync rwmutex go github com safing portmaster compat appissue notify home user git safing portmaster compat notify go github com safing portmaster compat appissue notify home user git safing portmaster compat notify go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module startworker home user git safing portbase modules worker go sync runtime semacquiremutex usr local go src runtime sema go sync rwmutex lock usr local go src sync rwmutex go github com safing portmaster profile layeredprofile increaserevisioncounter home user git safing portmaster profile profile layered go github com safing portmaster profile startprofileupdatechecker home user git safing portmaster profile database go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runserviceworker home user git safing portbase modules worker go sync runtime semacquiremutex usr local go src runtime sema go sync rwmutex lock usr local go src sync rwmutex go github com safing portmaster compat appissue notify home user git safing portmaster compat notify go github com safing portmaster compat appissue notify home user git safing portmaster compat notify go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module startworker home user git safing portbase modules worker go runtime pprof runtime goroutineprofilewithlabels usr local go src runtime mprof go runtime pprof writeruntimeprofile usr local go src runtime pprof pprof go runtime pprof writegoroutine usr local go src runtime pprof pprof go runtime pprof profile writeto usr local go src runtime pprof pprof go github com safing portbase utils debug info addgoroutinestack home user git safing portbase utils debug debug go github com safing portmaster core debuginfo home user git safing portmaster core api go github com safing portbase api endpoint servehttp home user git safing portbase api endpoints go github com safing portbase api endpointhandler servehttp home user git safing portbase api endpoints go github com safing portbase api mainhandler handle home user git safing portbase api router go github com safing portbase api mainhandler servehttp home user git safing portbase api router go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase modules module runworker home user git safing portbase modules worker go github com safing portbase api mainhandler servehttp home user git safing portbase api router go net http serverhandler servehttp usr local go src net http server go net http conn serve usr local go src net http server go | 0 |
105,568 | 23,072,473,189 | IssuesEvent | 2022-07-25 19:29:56 | octomation/maintainer | https://api.github.com/repos/octomation/maintainer | closed | pkg: file: register encoders for specific formats | kind: improvement difficulty: medium kind: feature scope: code scope: test | **Motivation:** it allows to simplify code like this
```go
var data HeatMap
format := strings.ToLower(filepath.Ext(file.Name()))
switch format {
case ".json":
err := json.NewDecoder(file).Decode(&data)
src.data = data
return data, err
case ".yml", ".yaml":
err := yaml.NewDecoder(file).Decode(&data)
src.data = data
return data, err
default:
return nil, fmt.Errorf("unsupported format: %s", format)
}
```
```go
func pack(file afero.File, data any) error {
format := strings.ToLower(filepath.Ext(file.Name()))
switch format {
case ".json":
return json.NewEncoder(file).Encode(data)
case ".yml", ".yaml":
return yaml.NewEncoder(file).Encode(data)
default:
return fmt.Errorf("unsupported format: %s", format)
}
}
func unpack(file afero.File, ptr any) error {
format := strings.ToLower(filepath.Ext(file.Name()))
switch format {
case ".json":
return json.NewDecoder(file).Decode(ptr)
case ".yml", ".yaml":
return yaml.NewDecoder(file).Decode(ptr)
default:
return fmt.Errorf("unsupported format: %s", format)
}
}
``` | 1.0 | pkg: file: register encoders for specific formats - **Motivation:** it allows to simplify code like this
```go
var data HeatMap
format := strings.ToLower(filepath.Ext(file.Name()))
switch format {
case ".json":
err := json.NewDecoder(file).Decode(&data)
src.data = data
return data, err
case ".yml", ".yaml":
err := yaml.NewDecoder(file).Decode(&data)
src.data = data
return data, err
default:
return nil, fmt.Errorf("unsupported format: %s", format)
}
```
```go
func pack(file afero.File, data any) error {
format := strings.ToLower(filepath.Ext(file.Name()))
switch format {
case ".json":
return json.NewEncoder(file).Encode(data)
case ".yml", ".yaml":
return yaml.NewEncoder(file).Encode(data)
default:
return fmt.Errorf("unsupported format: %s", format)
}
}
func unpack(file afero.File, ptr any) error {
format := strings.ToLower(filepath.Ext(file.Name()))
switch format {
case ".json":
return json.NewDecoder(file).Decode(ptr)
case ".yml", ".yaml":
return yaml.NewDecoder(file).Decode(ptr)
default:
return fmt.Errorf("unsupported format: %s", format)
}
}
``` | non_priority | pkg file register encoders for specific formats motivation it allows to simplify code like this go var data heatmap format strings tolower filepath ext file name switch format case json err json newdecoder file decode data src data data return data err case yml yaml err yaml newdecoder file decode data src data data return data err default return nil fmt errorf unsupported format s format go func pack file afero file data any error format strings tolower filepath ext file name switch format case json return json newencoder file encode data case yml yaml return yaml newencoder file encode data default return fmt errorf unsupported format s format func unpack file afero file ptr any error format strings tolower filepath ext file name switch format case json return json newdecoder file decode ptr case yml yaml return yaml newdecoder file decode ptr default return fmt errorf unsupported format s format | 0 |
57,882 | 6,559,726,117 | IssuesEvent | 2017-09-07 06:06:49 | Kademi/kademi-dev | https://api.github.com/repos/Kademi/kademi-dev | closed | KCRM: Closing a lead causes white error page | bug Project KCRM Ready to Test QA | Close this lead to see what i see. This happens with all leads I close.
http://kcrm.kademi.us/leads/11377186/ | 1.0 | KCRM: Closing a lead causes white error page - Close this lead to see what i see. This happens with all leads I close.
http://kcrm.kademi.us/leads/11377186/ | non_priority | kcrm closing a lead causes white error page close this lead to see what i see this happens with all leads i close | 0 |
40,272 | 10,482,079,993 | IssuesEvent | 2019-09-24 11:07:21 | ClickHouse/ClickHouse | https://api.github.com/repos/ClickHouse/ClickHouse | closed | HTTP ClickHouse exception code 1002 | alternative build obsolete version | Unable to connect using HTTP on ClickHouse 19.4.0.49
**How to reproduce**
* Use Manjaro (or probably any Arch Linux)
* Use poco-1.9.0-2
* Install clickhouse from AUR with an AUR helper (ex. `yay -S clickhouse`)
* Migrate from an older ClickHouse version (previous recent release)
* Store all logs and data directory on its own partition (if relevant).
* Connect to the new server using DBeaver 6.0.0
**Expected behavior**
```
Unexpected driver error occurred while connecting to database
ru.yandex.clickhouse.except.ClickHouseUnknownException: ClickHouse exception, code: 1002, host: localhost, port: 8123; ClickHouse response without column names
ru.yandex.clickhouse.except.ClickHouseUnknownException: ClickHouse exception, code: 1002, host: localhost, port: 8123; ClickHouse response without column names
ClickHouse exception, code: 1002, host: localhost, port: 8123; ClickHouse response without column names
ClickHouse exception, code: 1002, host: localhost, port: 8123; ClickHouse response without column names
ClickHouse response without column names
ClickHouse response without column names
```
Tailing the `clickhouse-server.log` reveals the following error:
```
2019.03.14 11:19:53.241061 [ 24 ] {73864537-9514-47c5-aa50-177250470e41} <Error> virtual DB::WriteBufferFromHTTPServerResponse::~WriteBufferFromHTTPServerResponse(): Poco::Exception. Code: 1000, e.code() = 0, e.displayText() = Assertion violation: !_pStream in file "/build/poco/src/poco-1.9.0-all/Net/src/HTTPServerResponseImpl.cpp", line 69
```
Same thing in `clickhouse-server.err.log`
---
Is anyone else experiencing this? | 1.0 | HTTP ClickHouse exception code 1002 - Unable to connect using HTTP on ClickHouse 19.4.0.49
**How to reproduce**
* Use Manjaro (or probably any Arch Linux)
* Use poco-1.9.0-2
* Install clickhouse from AUR with an AUR helper (ex. `yay -S clickhouse`)
* Migrate from an older ClickHouse version (previous recent release)
* Store all logs and data directory on its own partition (if relevant).
* Connect to the new server using DBeaver 6.0.0
**Expected behavior**
```
Unexpected driver error occurred while connecting to database
ru.yandex.clickhouse.except.ClickHouseUnknownException: ClickHouse exception, code: 1002, host: localhost, port: 8123; ClickHouse response without column names
ru.yandex.clickhouse.except.ClickHouseUnknownException: ClickHouse exception, code: 1002, host: localhost, port: 8123; ClickHouse response without column names
ClickHouse exception, code: 1002, host: localhost, port: 8123; ClickHouse response without column names
ClickHouse exception, code: 1002, host: localhost, port: 8123; ClickHouse response without column names
ClickHouse response without column names
ClickHouse response without column names
```
Tailing the `clickhouse-server.log` reveals the following error:
```
2019.03.14 11:19:53.241061 [ 24 ] {73864537-9514-47c5-aa50-177250470e41} <Error> virtual DB::WriteBufferFromHTTPServerResponse::~WriteBufferFromHTTPServerResponse(): Poco::Exception. Code: 1000, e.code() = 0, e.displayText() = Assertion violation: !_pStream in file "/build/poco/src/poco-1.9.0-all/Net/src/HTTPServerResponseImpl.cpp", line 69
```
Same thing in `clickhouse-server.err.log`
---
Is anyone else experiencing this? | non_priority | http clickhouse exception code unable to connect using http on clickhouse how to reproduce use manjaro or probably any arch linux use poco install clickhouse from aur with an aur helper ex yay s clickhouse migrate from an older clickhouse version previous recent release store all logs and data directory on its own partition if relevant connect to the new server using dbeaver expected behavior unexpected driver error occurred while connecting to database ru yandex clickhouse except clickhouseunknownexception clickhouse exception code host localhost port clickhouse response without column names ru yandex clickhouse except clickhouseunknownexception clickhouse exception code host localhost port clickhouse response without column names clickhouse exception code host localhost port clickhouse response without column names clickhouse exception code host localhost port clickhouse response without column names clickhouse response without column names clickhouse response without column names tailing the clickhouse server log reveals the following error virtual db writebufferfromhttpserverresponse writebufferfromhttpserverresponse poco exception code e code e displaytext assertion violation pstream in file build poco src poco all net src httpserverresponseimpl cpp line same thing in clickhouse server err log is anyone else experiencing this | 0 |
240,553 | 20,036,369,020 | IssuesEvent | 2022-02-02 12:21:14 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | opened | roachtest: tlp failed | C-test-failure O-robot O-roachtest release-blocker branch-release-21.2 | roachtest.tlp [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=4275952&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=4275952&tab=artifacts#/tlp) on release-21.2 @ [5afb632f77eee9f09f2adfa2943e1979ec4ebedf](https://github.com/cockroachdb/cockroach/commits/5afb632f77eee9f09f2adfa2943e1979ec4ebedf):
```
The test failed on branch=release-21.2, cloud=gce:
test artifacts and logs in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/tlp/run_1
tlp.go:128,test_runner.go:777: expected unpartitioned count 8 to equal partitioned count 11
(1) attached stack trace
-- stack trace:
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.runTLPQuery.func2
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/tlp.go:191
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.runWithTimeout.func1
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/tlp.go:203
| runtime.goexit
| /usr/local/go/src/runtime/asm_amd64.s:1581
Wraps: (2) expected unpartitioned count 8 to equal partitioned count 11
| sql: SELECT count(*) FROM defaultdb.public.table3 AS tab_18624
| SELECT count(*) FROM (SELECT * FROM defaultdb.public.table3 AS tab_18624 WHERE (NOT ('21:17:16.418508'::TIME NOT IN (tab_18624.col3_3,))) UNION ALL SELECT * FROM defaultdb.public.table3 AS tab_18624 WHERE NOT ((NOT ('21:17:16.418508'::TIME NOT IN (tab_18624.col3_3,)))) UNION ALL SELECT * FROM defaultdb.public.table3 AS tab_18624 WHERE ((NOT ('21:17:16.418508'::TIME NOT IN (tab_18624.col3_3,)))) IS NULL)
Error types: (1) *withstack.withStack (2) *errutil.leafError
```
<details><summary>Reproduce</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
</p>
</details>
<details><summary>Same failure on other branches</summary>
<p>
- #74675 roachtest: tlp failed [C-test-failure O-roachtest O-robot T-sql-queries branch-master release-blocker]
</p>
</details>
/cc @cockroachdb/sql-queries
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*tlp.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| 2.0 | roachtest: tlp failed - roachtest.tlp [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=4275952&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=4275952&tab=artifacts#/tlp) on release-21.2 @ [5afb632f77eee9f09f2adfa2943e1979ec4ebedf](https://github.com/cockroachdb/cockroach/commits/5afb632f77eee9f09f2adfa2943e1979ec4ebedf):
```
The test failed on branch=release-21.2, cloud=gce:
test artifacts and logs in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/tlp/run_1
tlp.go:128,test_runner.go:777: expected unpartitioned count 8 to equal partitioned count 11
(1) attached stack trace
-- stack trace:
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.runTLPQuery.func2
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/tlp.go:191
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.runWithTimeout.func1
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/tlp.go:203
| runtime.goexit
| /usr/local/go/src/runtime/asm_amd64.s:1581
Wraps: (2) expected unpartitioned count 8 to equal partitioned count 11
| sql: SELECT count(*) FROM defaultdb.public.table3 AS tab_18624
| SELECT count(*) FROM (SELECT * FROM defaultdb.public.table3 AS tab_18624 WHERE (NOT ('21:17:16.418508'::TIME NOT IN (tab_18624.col3_3,))) UNION ALL SELECT * FROM defaultdb.public.table3 AS tab_18624 WHERE NOT ((NOT ('21:17:16.418508'::TIME NOT IN (tab_18624.col3_3,)))) UNION ALL SELECT * FROM defaultdb.public.table3 AS tab_18624 WHERE ((NOT ('21:17:16.418508'::TIME NOT IN (tab_18624.col3_3,)))) IS NULL)
Error types: (1) *withstack.withStack (2) *errutil.leafError
```
<details><summary>Reproduce</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
</p>
</details>
<details><summary>Same failure on other branches</summary>
<p>
- #74675 roachtest: tlp failed [C-test-failure O-roachtest O-robot T-sql-queries branch-master release-blocker]
</p>
</details>
/cc @cockroachdb/sql-queries
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*tlp.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| non_priority | roachtest tlp failed roachtest tlp with on release the test failed on branch release cloud gce test artifacts and logs in home agent work go src github com cockroachdb cockroach artifacts tlp run tlp go test runner go expected unpartitioned count to equal partitioned count attached stack trace stack trace github com cockroachdb cockroach pkg cmd roachtest tests runtlpquery home agent work go src github com cockroachdb cockroach pkg cmd roachtest tests tlp go github com cockroachdb cockroach pkg cmd roachtest tests runwithtimeout home agent work go src github com cockroachdb cockroach pkg cmd roachtest tests tlp go runtime goexit usr local go src runtime asm s wraps expected unpartitioned count to equal partitioned count sql select count from defaultdb public as tab select count from select from defaultdb public as tab where not time not in tab union all select from defaultdb public as tab where not not time not in tab union all select from defaultdb public as tab where not time not in tab is null error types withstack withstack errutil leaferror reproduce see same failure on other branches roachtest tlp failed cc cockroachdb sql queries | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.