Unnamed: 0
int64 1
832k
| id
float64 2.49B
32.1B
| type
stringclasses 1
value | created_at
stringlengths 19
19
| repo
stringlengths 7
112
| repo_url
stringlengths 36
141
| action
stringclasses 3
values | title
stringlengths 3
438
| labels
stringlengths 4
308
| body
stringlengths 7
254k
| index
stringclasses 7
values | text_combine
stringlengths 96
254k
| label
stringclasses 2
values | text
stringlengths 96
246k
| binary_label
int64 0
1
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
369,774
| 10,917,562,210
|
IssuesEvent
|
2019-11-21 15:22:47
|
NorwegianClimateCentre/noresm2cmor
|
https://api.github.com/repos/NorwegianClimateCentre/noresm2cmor
|
reopened
|
[CMIP6 CMOR-ization & ESGF-publication] NorESM2-LM - piClim-anthro
|
ESGF publish Priority High
|
### Mandatory information:
**Full path to the case(s) of the experiment on NIRD**
/projects/NS9560K/noresm/cases/NF1850norbc_anthro2014_f19_20190811
**experiment_id**
<strike>e.g., RFMIP</strike>
- piClim-anthro
**model_id**
e.g.,
NorESM2-LM
**CASENAME(s) and years to be CMORized**
e.g.,
<strike>NF1850norbc_anthro2014_f19_20190811</strike>
NF1850norbc_anthro2014_f19_20190811, 1-30
### Optional information
(additional information, if the experiment is branched/hybrid restart from previous parent experiment; you may find more information relevant to the experiment_id here: https://github.com/NorwegianClimateCentre/noresm2cmor/blob/master/tables/CMIP6_CV.json)
<strike>
**parent_experiment_id**
e.g.,
piControl
**parent_experiment_rip**
e.g., r1i1p1
'no parent'
**parent_time_units**
e.g.,
'days since 0421-01-01'
**branch_method**
e.g.,
'Hybrid-restart from year 1751-01-01 of piControl',
</strike>
**other information**
(provide other information that might be useful)
e.g., realisation, initialisation, etc...
and the cases name and path to the parent experiment, etc
This is requested as input to a RFMIP paper by the end of October, so please give it a high prioity.
|
1.0
|
[CMIP6 CMOR-ization & ESGF-publication] NorESM2-LM - piClim-anthro - ### Mandatory information:
**Full path to the case(s) of the experiment on NIRD**
/projects/NS9560K/noresm/cases/NF1850norbc_anthro2014_f19_20190811
**experiment_id**
<strike>e.g., RFMIP</strike>
- piClim-anthro
**model_id**
e.g.,
NorESM2-LM
**CASENAME(s) and years to be CMORized**
e.g.,
<strike>NF1850norbc_anthro2014_f19_20190811</strike>
NF1850norbc_anthro2014_f19_20190811, 1-30
### Optional information
(additional information, if the experiment is branched/hybrid restart from previous parent experiment; you may find more information relevant to the experiment_id here: https://github.com/NorwegianClimateCentre/noresm2cmor/blob/master/tables/CMIP6_CV.json)
<strike>
**parent_experiment_id**
e.g.,
piControl
**parent_experiment_rip**
e.g., r1i1p1
'no parent'
**parent_time_units**
e.g.,
'days since 0421-01-01'
**branch_method**
e.g.,
'Hybrid-restart from year 1751-01-01 of piControl',
</strike>
**other information**
(provide other information that might be useful)
e.g., realisation, initialisation, etc...
and the cases name and path to the parent experiment, etc
This is requested as input to a RFMIP paper by the end of October, so please give it a high prioity.
|
non_main
|
lm piclim anthro mandatory information full path to the case s of the experiment on nird projects noresm cases experiment id e g rfmip piclim anthro model id e g lm casename s and years to be cmorized e g optional information additional information if the experiment is branched hybrid restart from previous parent experiment you may find more information relevant to the experiment id here parent experiment id e g picontrol parent experiment rip e g no parent parent time units e g days since branch method e g hybrid restart from year of picontrol other information provide other information that might be useful e g realisation initialisation etc and the cases name and path to the parent experiment etc this is requested as input to a rfmip paper by the end of october so please give it a high prioity
| 0
|
5,202
| 26,449,757,177
|
IssuesEvent
|
2023-01-16 10:17:38
|
Pandora-IsoMemo/bmsc-app
|
https://api.github.com/repos/Pandora-IsoMemo/bmsc-app
|
closed
|
Create wiki with installation instruction
|
Support: IT maintainance
|
Move and update installation instructions from
- https://github.com/Pandora-IsoMemo/drat/issues/8
to a new created wiki of this app
|
True
|
Create wiki with installation instruction - Move and update installation instructions from
- https://github.com/Pandora-IsoMemo/drat/issues/8
to a new created wiki of this app
|
main
|
create wiki with installation instruction move and update installation instructions from to a new created wiki of this app
| 1
|
209,492
| 7,176,544,491
|
IssuesEvent
|
2018-01-31 10:23:26
|
NCEAS/metacat
|
https://api.github.com/repos/NCEAS/metacat
|
closed
|
Download DTDs/Schemas for client
|
Category: metacat Component: Bugzilla-Id Priority: Normal Status: Resolved Tracker: Bug
|
---
Author Name: **Dan Higgins** (Dan Higgins)
Original Redmine Issue: 29, https://projects.ecoinformatics.org/ecoinfo/issues/29
Original Date: 2000-06-21
Original Assignee: Jivka Bojilova
---
The client needs to be able to get a list of doctypes from the server in order
to show the list of possible search types to the user. The client may also need
to download DTDs/Schemas.
|
1.0
|
Download DTDs/Schemas for client - ---
Author Name: **Dan Higgins** (Dan Higgins)
Original Redmine Issue: 29, https://projects.ecoinformatics.org/ecoinfo/issues/29
Original Date: 2000-06-21
Original Assignee: Jivka Bojilova
---
The client needs to be able to get a list of doctypes from the server in order
to show the list of possible search types to the user. The client may also need
to download DTDs/Schemas.
|
non_main
|
download dtds schemas for client author name dan higgins dan higgins original redmine issue original date original assignee jivka bojilova the client needs to be able to get a list of doctypes from the server in order to show the list of possible search types to the user the client may also need to download dtds schemas
| 0
|
1,996
| 6,710,907,380
|
IssuesEvent
|
2017-10-13 00:08:42
|
cannawen/metric_units_reddit_bot
|
https://api.github.com/repos/cannawen/metric_units_reddit_bot
|
closed
|
Refactor network module to avoid use of deasync
|
chore in progress maintainer approved
|
[metric_units](https://www.reddit.com/user/metric_units) is a sassy reddit bot that finds imperial units, and replies with a metric conversion.
**Enhancement request:**
`deasync` is used to create functions that act like they are synchronous, but, this is very non-idiomatic (i.e. "things aren't typically done this way in javascript-land"), unnecessary (i.e. it is possible to implement in other ways), and affects performance.
Potential patterns to refactor with: callbacks, promises or await.
`deasync` should be removed from:
- `src/bot.js`
- require (unused in this module anyway)
- `src/network.js`
- require
- `networkRequest()`
- `refreshToken()`
- `package.json`
Note: changes will also need to be made to functions that make use of `networkRequest()` and `refreshToken()` and so on...
**Recommended reading:**
[CONTRIBUTING.md](./CONTRIBUTING.md) (sections "Etiquette", "Work on an issue" and "Make a PR" are most important)
**Recommended skills:**
Javascript
**Estimated effort:**
1-2 hours
|
True
|
Refactor network module to avoid use of deasync - [metric_units](https://www.reddit.com/user/metric_units) is a sassy reddit bot that finds imperial units, and replies with a metric conversion.
**Enhancement request:**
`deasync` is used to create functions that act like they are synchronous, but, this is very non-idiomatic (i.e. "things aren't typically done this way in javascript-land"), unnecessary (i.e. it is possible to implement in other ways), and affects performance.
Potential patterns to refactor with: callbacks, promises or await.
`deasync` should be removed from:
- `src/bot.js`
- require (unused in this module anyway)
- `src/network.js`
- require
- `networkRequest()`
- `refreshToken()`
- `package.json`
Note: changes will also need to be made to functions that make use of `networkRequest()` and `refreshToken()` and so on...
**Recommended reading:**
[CONTRIBUTING.md](./CONTRIBUTING.md) (sections "Etiquette", "Work on an issue" and "Make a PR" are most important)
**Recommended skills:**
Javascript
**Estimated effort:**
1-2 hours
|
main
|
refactor network module to avoid use of deasync is a sassy reddit bot that finds imperial units and replies with a metric conversion enhancement request deasync is used to create functions that act like they are synchronous but this is very non idiomatic i e things aren t typically done this way in javascript land unnecessary i e it is possible to implement in other ways and affects performance potential patterns to refactor with callbacks promises or await deasync should be removed from src bot js require unused in this module anyway src network js require networkrequest refreshtoken package json note changes will also need to be made to functions that make use of networkrequest and refreshtoken and so on recommended reading contributing md sections etiquette work on an issue and make a pr are most important recommended skills javascript estimated effort hours
| 1
|
81,334
| 23,442,762,119
|
IssuesEvent
|
2022-08-15 16:26:31
|
dotnet/runtime
|
https://api.github.com/repos/dotnet/runtime
|
closed
|
Source-build fails to build w/CS0208: Cannot take the address of, get the size of, or declare a pointer to a managed type
|
blocking-release source-build area-Infrastructure
|
The latest dependency flow into installer's broke source-build w/the following errors:
```
/tarball/src/runtime/artifacts/source-build/self/src/src/coreclr/System.Private.CoreLib/src/System/Reflection/RuntimeMethodInfo.CoreCLR.cs(319,50): error CS0208: Cannot take the address of, get the size of, or declare a pointer to a managed type ('MethodBase.StackAllocatedByRefs') [/tarball/src/runtime/artifacts/source-build/self/src/src/coreclr/System.Private.CoreLib/System.Private.CoreLib.csproj]
/tarball/src/runtime/artifacts/source-build/self/src/src/libraries/System.Private.CoreLib/src/System/Reflection/MethodBase.cs(249,23): error CS0208: Cannot take the address of, get the size of, or declare a pointer to a managed type ('ByReference') [/tarball/src/runtime/artifacts/source-build/self/src/src/coreclr/System.Private.CoreLib/System.Private.CoreLib.csproj]
/tarball/src/runtime/artifacts/source-build/self/src/src/libraries/System.Private.CoreLib/src/System/Reflection/MethodBase.cs(254,23): error CS0208: Cannot take the address of, get the size of, or declare a pointer to a managed type ('ByReference') [/tarball/src/runtime/artifacts/source-build/self/src/src/coreclr/System.Private.CoreLib/System.Private.CoreLib.csproj]
/tarball/src/runtime/artifacts/source-build/self/src/src/libraries/System.Private.CoreLib/src/System/Reflection/RuntimeConstructorInfo.cs(149,54): error CS0208: Cannot take the address of, get the size of, or declare a pointer to a managed type ('MethodBase.StackAllocatedByRefs') [/tarball/src/runtime/artifacts/source-build/self/src/src/coreclr/System.Private.CoreLib/System.Private.CoreLib.csproj]
/tarball/src/runtime/artifacts/source-build/self/src/src/libraries/System.Private.CoreLib/src/System/Reflection/RuntimeMethodInfo.cs(146,54): error CS0208: Cannot take the address of, get the size of, or declare a pointer to a managed type ('MethodBase.StackAllocatedByRefs') [/tarball/src/runtime/artifacts/source-build/self/src/src/coreclr/System.Private.CoreLib/System.Private.CoreLib.csproj]
/tarball/src/runtime/artifacts/source-build/self/src/src/libraries/System.Private.CoreLib/src/System/Reflection/RuntimeConstructorInfo.cs(302,54): error CS0208: Cannot take the address of, get the size of, or declare a pointer to a managed type ('MethodBase.StackAllocatedByRefs') [/tarball/src/runtime/artifacts/source-build/self/src/src/coreclr/System.Private.CoreLib/System.Private.CoreLib.csproj]
/tarball/src/runtime/artifacts/source-build/self/src/src/coreclr/System.Private.CoreLib/src/System/Reflection/Emit/DynamicMethod.cs(507,54): error CS0208: Cannot take the address of, get the size of, or declare a pointer to a managed type ('MethodBase.StackAllocatedByRefs') [/tarball/src/runtime/artifacts/source-build/self/src/src/coreclr/System.Private.CoreLib/System.Private.CoreLib.csproj]
```
[CI Build Failure](https://dev.azure.com/dnceng/internal/_build/results?buildId=1939153&view=logs&j=87a4ea9e-995f-5db7-cd08-b96ecbe4e25a&t=f8cf185b-29d6-52a5-84b1-6edc34dd9fec) (internal Microsoft link)
Source-build does build with the latest compiler version and toolset which is likely a contributing factor here.
|
1.0
|
Source-build fails to build w/CS0208: Cannot take the address of, get the size of, or declare a pointer to a managed type - The latest dependency flow into installer's broke source-build w/the following errors:
```
/tarball/src/runtime/artifacts/source-build/self/src/src/coreclr/System.Private.CoreLib/src/System/Reflection/RuntimeMethodInfo.CoreCLR.cs(319,50): error CS0208: Cannot take the address of, get the size of, or declare a pointer to a managed type ('MethodBase.StackAllocatedByRefs') [/tarball/src/runtime/artifacts/source-build/self/src/src/coreclr/System.Private.CoreLib/System.Private.CoreLib.csproj]
/tarball/src/runtime/artifacts/source-build/self/src/src/libraries/System.Private.CoreLib/src/System/Reflection/MethodBase.cs(249,23): error CS0208: Cannot take the address of, get the size of, or declare a pointer to a managed type ('ByReference') [/tarball/src/runtime/artifacts/source-build/self/src/src/coreclr/System.Private.CoreLib/System.Private.CoreLib.csproj]
/tarball/src/runtime/artifacts/source-build/self/src/src/libraries/System.Private.CoreLib/src/System/Reflection/MethodBase.cs(254,23): error CS0208: Cannot take the address of, get the size of, or declare a pointer to a managed type ('ByReference') [/tarball/src/runtime/artifacts/source-build/self/src/src/coreclr/System.Private.CoreLib/System.Private.CoreLib.csproj]
/tarball/src/runtime/artifacts/source-build/self/src/src/libraries/System.Private.CoreLib/src/System/Reflection/RuntimeConstructorInfo.cs(149,54): error CS0208: Cannot take the address of, get the size of, or declare a pointer to a managed type ('MethodBase.StackAllocatedByRefs') [/tarball/src/runtime/artifacts/source-build/self/src/src/coreclr/System.Private.CoreLib/System.Private.CoreLib.csproj]
/tarball/src/runtime/artifacts/source-build/self/src/src/libraries/System.Private.CoreLib/src/System/Reflection/RuntimeMethodInfo.cs(146,54): error CS0208: Cannot take the address of, get the size of, or declare a pointer to a managed type ('MethodBase.StackAllocatedByRefs') [/tarball/src/runtime/artifacts/source-build/self/src/src/coreclr/System.Private.CoreLib/System.Private.CoreLib.csproj]
/tarball/src/runtime/artifacts/source-build/self/src/src/libraries/System.Private.CoreLib/src/System/Reflection/RuntimeConstructorInfo.cs(302,54): error CS0208: Cannot take the address of, get the size of, or declare a pointer to a managed type ('MethodBase.StackAllocatedByRefs') [/tarball/src/runtime/artifacts/source-build/self/src/src/coreclr/System.Private.CoreLib/System.Private.CoreLib.csproj]
/tarball/src/runtime/artifacts/source-build/self/src/src/coreclr/System.Private.CoreLib/src/System/Reflection/Emit/DynamicMethod.cs(507,54): error CS0208: Cannot take the address of, get the size of, or declare a pointer to a managed type ('MethodBase.StackAllocatedByRefs') [/tarball/src/runtime/artifacts/source-build/self/src/src/coreclr/System.Private.CoreLib/System.Private.CoreLib.csproj]
```
[CI Build Failure](https://dev.azure.com/dnceng/internal/_build/results?buildId=1939153&view=logs&j=87a4ea9e-995f-5db7-cd08-b96ecbe4e25a&t=f8cf185b-29d6-52a5-84b1-6edc34dd9fec) (internal Microsoft link)
Source-build does build with the latest compiler version and toolset which is likely a contributing factor here.
|
non_main
|
source build fails to build w cannot take the address of get the size of or declare a pointer to a managed type the latest dependency flow into installer s broke source build w the following errors tarball src runtime artifacts source build self src src coreclr system private corelib src system reflection runtimemethodinfo coreclr cs error cannot take the address of get the size of or declare a pointer to a managed type methodbase stackallocatedbyrefs tarball src runtime artifacts source build self src src libraries system private corelib src system reflection methodbase cs error cannot take the address of get the size of or declare a pointer to a managed type byreference tarball src runtime artifacts source build self src src libraries system private corelib src system reflection methodbase cs error cannot take the address of get the size of or declare a pointer to a managed type byreference tarball src runtime artifacts source build self src src libraries system private corelib src system reflection runtimeconstructorinfo cs error cannot take the address of get the size of or declare a pointer to a managed type methodbase stackallocatedbyrefs tarball src runtime artifacts source build self src src libraries system private corelib src system reflection runtimemethodinfo cs error cannot take the address of get the size of or declare a pointer to a managed type methodbase stackallocatedbyrefs tarball src runtime artifacts source build self src src libraries system private corelib src system reflection runtimeconstructorinfo cs error cannot take the address of get the size of or declare a pointer to a managed type methodbase stackallocatedbyrefs tarball src runtime artifacts source build self src src coreclr system private corelib src system reflection emit dynamicmethod cs error cannot take the address of get the size of or declare a pointer to a managed type methodbase stackallocatedbyrefs internal microsoft link source build does build with the latest compiler version and toolset which is likely a contributing factor here
| 0
|
1,046
| 4,859,904,450
|
IssuesEvent
|
2016-11-13 21:42:49
|
ansible/ansible-modules-core
|
https://api.github.com/repos/ansible/ansible-modules-core
|
closed
|
stat: readable and writeable are missing
|
affects_2.1 docs_report waiting_on_maintainer
|
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
stat
##### ANSIBLE VERSION
```
ansible 2.1.2.0
config file = xxx/ansible.cfg
configured module search path = Default w/o overrides
```
##### OS / ENVIRONMENT
Debian 8
##### SUMMARY
In the stat dict the keys "readable" and "writeable" are missing. These keys are mentioned in the documentation [http://docs.ansible.com/ansible/stat_module.html](url).
##### STEPS TO REPRODUCE
```
- stat: path=/etc
name: check /etc
register: path
- fail: msg="/etc is not there"
when: not path.stat.exists
- fail: msg="/etc is not readable"
when: not path.stat.readable
```
##### EXPECTED RESULTS
correct evaluation of path.stat.readable
##### ACTUAL RESULTS
```
fatal: [xxx]: FAILED! => {"failed": true, "msg": "The conditional check 'not path.stat.readable' failed. The error was: error while evaluating conditional (not path.stat.readable): 'dict object' has no attribute 'readable'\n\nThe error appears to have been in 'xxx/playbook.yml': line x, column x, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n when: not path.stat.exists\n - fail: msg=\"/etc is not readable\"\n ^ here\n"}
```
|
True
|
stat: readable and writeable are missing - ##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
stat
##### ANSIBLE VERSION
```
ansible 2.1.2.0
config file = xxx/ansible.cfg
configured module search path = Default w/o overrides
```
##### OS / ENVIRONMENT
Debian 8
##### SUMMARY
In the stat dict the keys "readable" and "writeable" are missing. These keys are mentioned in the documentation [http://docs.ansible.com/ansible/stat_module.html](url).
##### STEPS TO REPRODUCE
```
- stat: path=/etc
name: check /etc
register: path
- fail: msg="/etc is not there"
when: not path.stat.exists
- fail: msg="/etc is not readable"
when: not path.stat.readable
```
##### EXPECTED RESULTS
correct evaluation of path.stat.readable
##### ACTUAL RESULTS
```
fatal: [xxx]: FAILED! => {"failed": true, "msg": "The conditional check 'not path.stat.readable' failed. The error was: error while evaluating conditional (not path.stat.readable): 'dict object' has no attribute 'readable'\n\nThe error appears to have been in 'xxx/playbook.yml': line x, column x, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n when: not path.stat.exists\n - fail: msg=\"/etc is not readable\"\n ^ here\n"}
```
|
main
|
stat readable and writeable are missing issue type bug report component name stat ansible version ansible config file xxx ansible cfg configured module search path default w o overrides os environment debian summary in the stat dict the keys readable and writeable are missing these keys are mentioned in the documentation url steps to reproduce stat path etc name check etc register path fail msg etc is not there when not path stat exists fail msg etc is not readable when not path stat readable expected results correct evaluation of path stat readable actual results fatal failed failed true msg the conditional check not path stat readable failed the error was error while evaluating conditional not path stat readable dict object has no attribute readable n nthe error appears to have been in xxx playbook yml line x column x but may nbe elsewhere in the file depending on the exact syntax problem n nthe offending line appears to be n n when not path stat exists n fail msg etc is not readable n here n
| 1
|
3,615
| 14,617,968,179
|
IssuesEvent
|
2020-12-22 15:32:37
|
OpenLightingProject/ola
|
https://api.github.com/repos/OpenLightingProject/ola
|
closed
|
make check fails with compile error - -Wstringop-truncation
|
Language-C++ Maintainability OpSys-Linux bug
|
It seems that `make check` is failing to build the tests, below I have added the compile line from my build log.
```
g++ -DHAVE_CONFIG_H -I. -I/opt/saleae/SaleaeDeviceSdk-1.1.9/include -I./include -I./include -Wall -Wformat -W -fvisibility-inlines-hidden -pthread -DTEST_SRC_DIR=\".\" -DTEST_BUILD_DIR=\".\" -Werror -Wno-error=deprecated-declarations -g -O2 -std=gnu++11 -pthread -MT plugins/dummy/plugins_dummy_DummyPluginTester-DummyPortTest.o -MD -MP -MF plugins/dummy/.deps/plugins_dummy_DummyPluginTester-DummyPortTest.Tpo -c -o plugins/dummy/plugins_dummy_DummyPluginTester-DummyPortTest.o `test -f 'plugins/dummy/DummyPortTest.cpp' || echo './'`plugins/dummy/DummyPortTest.cpp
plugins/dummy/DummyPortTest.cpp: In member function ‘void ola::plugin::dummy::DummyPortTest::testParamDescription()’:
plugins/dummy/DummyPortTest.cpp:678:32: error: unknown option after ‘#pragma GCC diagnostic’ kind [-Werror=pragmas]
#pragma GCC diagnostic ignored "-Wstringop-truncation"
^
cc1plus: all warnings being treated as errors
make[3]: *** [plugins/dummy/plugins_dummy_DummyPluginTester-DummyPortTest.o] Error 1
make[3]: Leaving directory `/home/jenkins/jobs/Open_Lighting_Architecture_-_Linux/workspace'
make[2]: *** [check-am] Error 2
make[2]: Leaving directory `/home/jenkins/jobs/Open_Lighting_Architecture_-_Linux/workspace'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/home/jenkins/jobs/Open_Lighting_Architecture_-_Linux/workspace'
make: *** [check] Error 2
+ echo 'Testing failed 2'
```
My compiler version is below and I am building using Mint Linux 20
```
$ g++ --version
g++ (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
```
I can provide more information if needed, as this was from my internal Jenkins CI.
Rod
|
True
|
make check fails with compile error - -Wstringop-truncation - It seems that `make check` is failing to build the tests, below I have added the compile line from my build log.
```
g++ -DHAVE_CONFIG_H -I. -I/opt/saleae/SaleaeDeviceSdk-1.1.9/include -I./include -I./include -Wall -Wformat -W -fvisibility-inlines-hidden -pthread -DTEST_SRC_DIR=\".\" -DTEST_BUILD_DIR=\".\" -Werror -Wno-error=deprecated-declarations -g -O2 -std=gnu++11 -pthread -MT plugins/dummy/plugins_dummy_DummyPluginTester-DummyPortTest.o -MD -MP -MF plugins/dummy/.deps/plugins_dummy_DummyPluginTester-DummyPortTest.Tpo -c -o plugins/dummy/plugins_dummy_DummyPluginTester-DummyPortTest.o `test -f 'plugins/dummy/DummyPortTest.cpp' || echo './'`plugins/dummy/DummyPortTest.cpp
plugins/dummy/DummyPortTest.cpp: In member function ‘void ola::plugin::dummy::DummyPortTest::testParamDescription()’:
plugins/dummy/DummyPortTest.cpp:678:32: error: unknown option after ‘#pragma GCC diagnostic’ kind [-Werror=pragmas]
#pragma GCC diagnostic ignored "-Wstringop-truncation"
^
cc1plus: all warnings being treated as errors
make[3]: *** [plugins/dummy/plugins_dummy_DummyPluginTester-DummyPortTest.o] Error 1
make[3]: Leaving directory `/home/jenkins/jobs/Open_Lighting_Architecture_-_Linux/workspace'
make[2]: *** [check-am] Error 2
make[2]: Leaving directory `/home/jenkins/jobs/Open_Lighting_Architecture_-_Linux/workspace'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/home/jenkins/jobs/Open_Lighting_Architecture_-_Linux/workspace'
make: *** [check] Error 2
+ echo 'Testing failed 2'
```
My compiler version is below and I am building using Mint Linux 20
```
$ g++ --version
g++ (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
```
I can provide more information if needed, as this was from my internal Jenkins CI.
Rod
|
main
|
make check fails with compile error wstringop truncation it seems that make check is failing to build the tests below i have added the compile line from my build log g dhave config h i i opt saleae saleaedevicesdk include i include i include wall wformat w fvisibility inlines hidden pthread dtest src dir dtest build dir werror wno error deprecated declarations g std gnu pthread mt plugins dummy plugins dummy dummyplugintester dummyporttest o md mp mf plugins dummy deps plugins dummy dummyplugintester dummyporttest tpo c o plugins dummy plugins dummy dummyplugintester dummyporttest o test f plugins dummy dummyporttest cpp echo plugins dummy dummyporttest cpp plugins dummy dummyporttest cpp in member function ‘void ola plugin dummy dummyporttest testparamdescription ’ plugins dummy dummyporttest cpp error unknown option after ‘ pragma gcc diagnostic’ kind pragma gcc diagnostic ignored wstringop truncation all warnings being treated as errors make error make leaving directory home jenkins jobs open lighting architecture linux workspace make error make leaving directory home jenkins jobs open lighting architecture linux workspace make error make leaving directory home jenkins jobs open lighting architecture linux workspace make error echo testing failed my compiler version is below and i am building using mint linux g version g ubuntu copyright c free software foundation inc this is free software see the source for copying conditions there is no warranty not even for merchantability or fitness for a particular purpose i can provide more information if needed as this was from my internal jenkins ci rod
| 1
|
2,728
| 9,639,708,987
|
IssuesEvent
|
2019-05-16 14:05:13
|
ansible/ansible
|
https://api.github.com/repos/ansible/ansible
|
closed
|
Move AWS module dev docs to docsite
|
affects_2.8 aws cloud deprecated docs huawei module needs_maintainer oracle support:certified support:community support:core
|
<!--- Verify first that your improvement is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
Move the AWS module development content from its [current markdown file](https://github.com/ansible/ansible/blob/devel/lib/ansible/modules/cloud/amazon/GUIDELINES.md) into an rST file so it will be indexed and become more findable.
<!--- Explain the problem briefly below, add suggestions to wording or structure -->
<!--- HINT: Did you know the documentation has an "Edit on GitHub" link on every page ? -->
##### ISSUE TYPE
- Documentation Report
##### COMPONENT NAME
lib/ansible/modules/cloud/amazon/GUIDELINES.md
docs.ansible.com
##### ANSIBLE VERSION
2.8
##### CONFIGURATION
N/A
##### OS / ENVIRONMENT
N/A
|
True
|
Move AWS module dev docs to docsite - <!--- Verify first that your improvement is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
Move the AWS module development content from its [current markdown file](https://github.com/ansible/ansible/blob/devel/lib/ansible/modules/cloud/amazon/GUIDELINES.md) into an rST file so it will be indexed and become more findable.
<!--- Explain the problem briefly below, add suggestions to wording or structure -->
<!--- HINT: Did you know the documentation has an "Edit on GitHub" link on every page ? -->
##### ISSUE TYPE
- Documentation Report
##### COMPONENT NAME
lib/ansible/modules/cloud/amazon/GUIDELINES.md
docs.ansible.com
##### ANSIBLE VERSION
2.8
##### CONFIGURATION
N/A
##### OS / ENVIRONMENT
N/A
|
main
|
move aws module dev docs to docsite summary move the aws module development content from its into an rst file so it will be indexed and become more findable issue type documentation report component name lib ansible modules cloud amazon guidelines md docs ansible com ansible version configuration n a os environment n a
| 1
|
25,809
| 11,220,005,082
|
IssuesEvent
|
2020-01-07 15:00:43
|
paritytech/substrate-light-ui
|
https://api.github.com/repos/paritytech/substrate-light-ui
|
closed
|
CSP Note: If ever we use a webview,
|
@electron-app F1-security P9-somedaymaybe
|
```
app.on('web-contents-created', (event, contents) => {
contents.on('will-attach-webview', (event, webPreferences, params) => {
event.preventDefault();
});
});
```
|
True
|
CSP Note: If ever we use a webview, -
```
app.on('web-contents-created', (event, contents) => {
contents.on('will-attach-webview', (event, webPreferences, params) => {
event.preventDefault();
});
});
```
|
non_main
|
csp note if ever we use a webview app on web contents created event contents contents on will attach webview event webpreferences params event preventdefault
| 0
|
88,295
| 10,568,419,960
|
IssuesEvent
|
2019-10-06 12:55:11
|
AlexxNB/svelte-chota
|
https://api.github.com/repos/AlexxNB/svelte-chota
|
opened
|
Correct documentation text
|
documentation help wanted
|
My english is poor, so the docs text isn't pretty. Necessary to edit the text by somebody who is english native speaker.
|
1.0
|
Correct documentation text - My english is poor, so the docs text isn't pretty. Necessary to edit the text by somebody who is english native speaker.
|
non_main
|
correct documentation text my english is poor so the docs text isn t pretty necessary to edit the text by somebody who is english native speaker
| 0
|
2,364
| 8,440,431,454
|
IssuesEvent
|
2018-10-18 07:15:00
|
Kristinita/Erics-Green-Room
|
https://api.github.com/repos/Kristinita/Erics-Green-Room
|
opened
|
feat(enhancement): шаблоны
|
need-maintainer packages
|
### 1. Запрос
Неплохо было бы, если б в пакетах комнат Эрика можно было бы использовать шаблоны: то есть, когда один текст заменялся бы другим.
### 2. Аргументация
#### 2.1. Основное предназначение
Собственно, нужны для того же, для чего применяются шаблоны в программировании.
1. Вместо того, чтобы постоянно писать один и тот же длинный текст, легче применить шаблон.
1. Повторы обычно считаются [**признаком code smell**](https://www.artima.com/intv/dry.html) в программировании и «[**свидетельствуют о стилистической беспомощности автора»**](http://www.textologia.ru/russkiy/stilistika/lexsicheskaya/povtorenie-slov/948/?q=463&n=948)» для художественных, публицистических и научных статей. Почему они должны существовать в наших пакетах?
1. Шаблоны сокращают размеры пакетов.
1. При наличии шаблонов, если что-то захотим изменить, то достаточно будет изменить шаблон, а не производить замены везде.
#### 2.2. Скрытие названий сайтов
Больше вероятность, что от проблем будет убережён Альфа-хаб в том числе.
### 3. Пример технической реализации
Пользователь выбирает пакет для отыгрыша → какой-нибудь модуль, к примеру, [**replace-in-file**](https://www.npmjs.com/package/replace-in-file) производит замены в выбранном файле → пользователь играет пакет, где проведены замены.
### 4. Глобальные шаблоны
Которые будут применяться для всех пакетов.
#### 4.1. Темы
По состоянию на 17 октября 2018 38 пакетов комнат Эрика нуждаются в переписывании по причине [**реализации отыгрыша по темам**](https://github.com/Kristinita/Erics-Green-Room/issues/56). В 31 из них темы будут в следующем формате:
```
Назовите A по B
```
или:
```
Назовите A по B и С
```
+ Примеры замен:
+ `{по2|автора|художественному произведению}` → `Назовите автора по художественному произведению`,
+ `{по3|место катастрофы|году|типу}` → `Назовите место катастрофы по году и типу`.
#### 4.2. Метаданные шапки
Примеры:
+ `{сни}` → `Ссылка(и) на источник(и)`,
+ `{авт}` → `Автор(ы), редакторы и рецензенты (если есть) материалов источника(ов)`.
#### 4.3. Имена сайтов
Производятся прямые замены:
+ `{tw}` → `twitter`,
+ `{fl}` → `facebook`.
И так далее.
### 5. Локальные
Которые будут применяться только в пределах пакета.
Пример — если в шапке пакета содержится следующий текст:
```text
Локальные шаблоны:
{нмнк} — на момент написания книги
```
Это значит, что все вхождения `нмнк` в данном пакете перед отыгрышем будут заменены на `на момент написания книги`.
Спасибо.
|
True
|
feat(enhancement): шаблоны - ### 1. Запрос
Неплохо было бы, если б в пакетах комнат Эрика можно было бы использовать шаблоны: то есть, когда один текст заменялся бы другим.
### 2. Аргументация
#### 2.1. Основное предназначение
Собственно, нужны для того же, для чего применяются шаблоны в программировании.
1. Вместо того, чтобы постоянно писать один и тот же длинный текст, легче применить шаблон.
1. Повторы обычно считаются [**признаком code smell**](https://www.artima.com/intv/dry.html) в программировании и «[**свидетельствуют о стилистической беспомощности автора»**](http://www.textologia.ru/russkiy/stilistika/lexsicheskaya/povtorenie-slov/948/?q=463&n=948)» для художественных, публицистических и научных статей. Почему они должны существовать в наших пакетах?
1. Шаблоны сокращают размеры пакетов.
1. При наличии шаблонов, если что-то захотим изменить, то достаточно будет изменить шаблон, а не производить замены везде.
#### 2.2. Скрытие названий сайтов
Больше вероятность, что от проблем будет убережён Альфа-хаб в том числе.
### 3. Пример технической реализации
Пользователь выбирает пакет для отыгрыша → какой-нибудь модуль, к примеру, [**replace-in-file**](https://www.npmjs.com/package/replace-in-file) производит замены в выбранном файле → пользователь играет пакет, где проведены замены.
### 4. Глобальные шаблоны
Которые будут применяться для всех пакетов.
#### 4.1. Темы
По состоянию на 17 октября 2018 38 пакетов комнат Эрика нуждаются в переписывании по причине [**реализации отыгрыша по темам**](https://github.com/Kristinita/Erics-Green-Room/issues/56). В 31 из них темы будут в следующем формате:
```
Назовите A по B
```
или:
```
Назовите A по B и С
```
+ Примеры замен:
+ `{по2|автора|художественному произведению}` → `Назовите автора по художественному произведению`,
+ `{по3|место катастрофы|году|типу}` → `Назовите место катастрофы по году и типу`.
#### 4.2. Метаданные шапки
Примеры:
+ `{сни}` → `Ссылка(и) на источник(и)`,
+ `{авт}` → `Автор(ы), редакторы и рецензенты (если есть) материалов источника(ов)`.
#### 4.3. Имена сайтов
Производятся прямые замены:
+ `{tw}` → `twitter`,
+ `{fl}` → `facebook`.
И так далее.
### 5. Локальные
Которые будут применяться только в пределах пакета.
Пример — если в шапке пакета содержится следующий текст:
```text
Локальные шаблоны:
{нмнк} — на момент написания книги
```
Это значит, что все вхождения `нмнк` в данном пакете перед отыгрышем будут заменены на `на момент написания книги`.
Спасибо.
|
main
|
feat enhancement шаблоны запрос неплохо было бы если б в пакетах комнат эрика можно было бы использовать шаблоны то есть когда один текст заменялся бы другим аргументация основное предназначение собственно нужны для того же для чего применяются шаблоны в программировании вместо того чтобы постоянно писать один и тот же длинный текст легче применить шаблон повторы обычно считаются в программировании и « для художественных публицистических и научных статей почему они должны существовать в наших пакетах шаблоны сокращают размеры пакетов при наличии шаблонов если что то захотим изменить то достаточно будет изменить шаблон а не производить замены везде скрытие названий сайтов больше вероятность что от проблем будет убережён альфа хаб в том числе пример технической реализации пользователь выбирает пакет для отыгрыша → какой нибудь модуль к примеру производит замены в выбранном файле → пользователь играет пакет где проведены замены глобальные шаблоны которые будут применяться для всех пакетов темы по состоянию на октября пакетов комнат эрика нуждаются в переписывании по причине в из них темы будут в следующем формате назовите a по b или назовите a по b и с примеры замен автора художественному произведению → назовите автора по художественному произведению место катастрофы году типу → назовите место катастрофы по году и типу метаданные шапки примеры сни → ссылка и на источник и авт → автор ы редакторы и рецензенты если есть материалов источника ов имена сайтов производятся прямые замены tw → twitter fl → facebook и так далее локальные которые будут применяться только в пределах пакета пример — если в шапке пакета содержится следующий текст text локальные шаблоны нмнк — на момент написания книги это значит что все вхождения нмнк в данном пакете перед отыгрышем будут заменены на на момент написания книги спасибо
| 1
|
1,083
| 4,931,796,273
|
IssuesEvent
|
2016-11-28 11:24:27
|
ansible/ansible-modules-core
|
https://api.github.com/repos/ansible/ansible-modules-core
|
closed
|
junos_config: obj, end = self.raw_decode(s, idx=_w(s, 0).end()) -> TypeError: expected string or buffer
|
affects_2.3 bug_report networking waiting_on_maintainer
|
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
junos_config
##### ANSIBLE VERSION
```
```
##### CONFIGURATION
##### OS / ENVIRONMENT
##### SUMMARY
##### STEPS TO REPRODUCE
```
Run Junos test cases, or manually:
- name: configure device with config
junos_config:
src: basic/config.j2
provider: "{{ netconf }}"
register: result
templates/basic/config.j2
interfaces {
lo0 {
unit 0 {
family inet {
address 1.1.1.1/32;
}
}
}
}
```
##### EXPECTED RESULTS
##### ACTUAL RESULTS
```yaml
TASK [junos_config : configure device with config] *****************************
task path: /tmp/run-network-test/junos/devel/ansible/test/integration/targets/junos_config/tests/netconf/src_basic.yaml:11
Using module file /usr/local/lib/python2.7/dist-packages/ansible/modules/core/network/junos/junos_config.py
<vsrx01> ESTABLISH LOCAL CONNECTION FOR USER: johnb
<vsrx01> EXEC /bin/sh -c '( umask 77 && mkdir -p "` echo $HOME/.ansible/tmp/ansible-tmp-1479324113.09-83039427345774 `" && echo ansible-tmp-1479324113.09-83039427345774="` echo $HOME/.ansible/tmp/ansible-tmp-1479324113.09-83039427345774 `" ) && sleep 0'
<vsrx01> PUT /tmp/tmpj7mocy TO /home/johnb/.ansible/tmp/ansible-tmp-1479324113.09-83039427345774/junos_config.py
<vsrx01> EXEC /bin/sh -c 'chmod u+x /home/johnb/.ansible/tmp/ansible-tmp-1479324113.09-83039427345774/ /home/johnb/.ansible/tmp/ansible-tmp-1479324113.09-83039427345774/junos_config.py && sleep 0'
<vsrx01> EXEC /bin/sh -c 'python /home/johnb/.ansible/tmp/ansible-tmp-1479324113.09-83039427345774/junos_config.py; rm -rf "/home/johnb/.ansible/tmp/ansible-tmp-1479324113.09-83039427345774/" > /dev/null 2>&1 && sleep 0'
An exception occurred during task execution. The full traceback is:
Traceback (most recent call last):
File "/tmp/ansible_5AgCUV/ansible_module_junos_config.py", line 343, in <module>
main()
File "/tmp/ansible_5AgCUV/ansible_module_junos_config.py", line 334, in main
run(module, result)
File "/tmp/ansible_5AgCUV/ansible_module_junos_config.py", line 292, in run
return load_config(module, result)
File "/tmp/ansible_5AgCUV/ansible_module_junos_config.py", line 245, in load_config
config_format = module.params['src_format'] or guess_format(candidate)
File "/tmp/ansible_5AgCUV/ansible_module_junos_config.py", line 176, in guess_format
json.loads(config)
File "/usr/lib/python2.7/json/__init__.py", line 339, in loads
return _default_decoder.decode(s)
File "/usr/lib/python2.7/json/decoder.py", line 364, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
TypeError: expected string or buffer
fatal: [vsrx01]: FAILED! => {
"changed": false,
"failed": true,
"invocation": {
"module_args": {
"provider": {
"host": "vsrx01",
"password": "Ansible",
"transport": "netconf",
"username": "ansible"
},
"src": "interfaces {\n lo0 {\n unit 0 {\n family inet {\n address 1.1.1.1/32;\n }\n }\n }\n}\n\n"
},
"module_name": "junos_config"
},
"module_stderr": "Traceback (most recent call last):\n File \"/tmp/ansible_5AgCUV/ansible_module_junos_config.py\", line 343, in <module>\n main()\n File \"/tmp/ansible_5AgCUV/ansible_module_junos_config.py\", line 334, in main\n run(module, result)\n File \"/tmp/ansible_5AgCUV/ansible_module_junos_config.py\", line 292, in run\n return load_config(module, result)\n File \"/tmp/ansible_5AgCUV/ansible_module_junos_config.py\", line 245, in load_config\n config_format = module.params['src_format'] or guess_format(candidate)\n File \"/tmp/ansible_5AgCUV/ansible_module_junos_config.py\", line 176, in guess_format\n json.loads(config)\n File \"/usr/lib/python2.7/json/__init__.py\", line 339, in loads\n return _default_decoder.decode(s)\n File \"/usr/lib/python2.7/json/decoder.py\", line 364, in decode\n obj, end = self.raw_decode(s, idx=_w(s, 0).end())\nTypeError: expected string or buffer\n",
"module_stdout": "",
"msg": "MODULE FAILURE"
```
|
True
|
junos_config: obj, end = self.raw_decode(s, idx=_w(s, 0).end()) -> TypeError: expected string or buffer - ##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
junos_config
##### ANSIBLE VERSION
```
```
##### CONFIGURATION
##### OS / ENVIRONMENT
##### SUMMARY
##### STEPS TO REPRODUCE
```
Run Junos test cases, or manually:
- name: configure device with config
junos_config:
src: basic/config.j2
provider: "{{ netconf }}"
register: result
templates/basic/config.j2
interfaces {
lo0 {
unit 0 {
family inet {
address 1.1.1.1/32;
}
}
}
}
```
##### EXPECTED RESULTS
##### ACTUAL RESULTS
```yaml
TASK [junos_config : configure device with config] *****************************
task path: /tmp/run-network-test/junos/devel/ansible/test/integration/targets/junos_config/tests/netconf/src_basic.yaml:11
Using module file /usr/local/lib/python2.7/dist-packages/ansible/modules/core/network/junos/junos_config.py
<vsrx01> ESTABLISH LOCAL CONNECTION FOR USER: johnb
<vsrx01> EXEC /bin/sh -c '( umask 77 && mkdir -p "` echo $HOME/.ansible/tmp/ansible-tmp-1479324113.09-83039427345774 `" && echo ansible-tmp-1479324113.09-83039427345774="` echo $HOME/.ansible/tmp/ansible-tmp-1479324113.09-83039427345774 `" ) && sleep 0'
<vsrx01> PUT /tmp/tmpj7mocy TO /home/johnb/.ansible/tmp/ansible-tmp-1479324113.09-83039427345774/junos_config.py
<vsrx01> EXEC /bin/sh -c 'chmod u+x /home/johnb/.ansible/tmp/ansible-tmp-1479324113.09-83039427345774/ /home/johnb/.ansible/tmp/ansible-tmp-1479324113.09-83039427345774/junos_config.py && sleep 0'
<vsrx01> EXEC /bin/sh -c 'python /home/johnb/.ansible/tmp/ansible-tmp-1479324113.09-83039427345774/junos_config.py; rm -rf "/home/johnb/.ansible/tmp/ansible-tmp-1479324113.09-83039427345774/" > /dev/null 2>&1 && sleep 0'
An exception occurred during task execution. The full traceback is:
Traceback (most recent call last):
File "/tmp/ansible_5AgCUV/ansible_module_junos_config.py", line 343, in <module>
main()
File "/tmp/ansible_5AgCUV/ansible_module_junos_config.py", line 334, in main
run(module, result)
File "/tmp/ansible_5AgCUV/ansible_module_junos_config.py", line 292, in run
return load_config(module, result)
File "/tmp/ansible_5AgCUV/ansible_module_junos_config.py", line 245, in load_config
config_format = module.params['src_format'] or guess_format(candidate)
File "/tmp/ansible_5AgCUV/ansible_module_junos_config.py", line 176, in guess_format
json.loads(config)
File "/usr/lib/python2.7/json/__init__.py", line 339, in loads
return _default_decoder.decode(s)
File "/usr/lib/python2.7/json/decoder.py", line 364, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
TypeError: expected string or buffer
fatal: [vsrx01]: FAILED! => {
"changed": false,
"failed": true,
"invocation": {
"module_args": {
"provider": {
"host": "vsrx01",
"password": "Ansible",
"transport": "netconf",
"username": "ansible"
},
"src": "interfaces {\n lo0 {\n unit 0 {\n family inet {\n address 1.1.1.1/32;\n }\n }\n }\n}\n\n"
},
"module_name": "junos_config"
},
"module_stderr": "Traceback (most recent call last):\n File \"/tmp/ansible_5AgCUV/ansible_module_junos_config.py\", line 343, in <module>\n main()\n File \"/tmp/ansible_5AgCUV/ansible_module_junos_config.py\", line 334, in main\n run(module, result)\n File \"/tmp/ansible_5AgCUV/ansible_module_junos_config.py\", line 292, in run\n return load_config(module, result)\n File \"/tmp/ansible_5AgCUV/ansible_module_junos_config.py\", line 245, in load_config\n config_format = module.params['src_format'] or guess_format(candidate)\n File \"/tmp/ansible_5AgCUV/ansible_module_junos_config.py\", line 176, in guess_format\n json.loads(config)\n File \"/usr/lib/python2.7/json/__init__.py\", line 339, in loads\n return _default_decoder.decode(s)\n File \"/usr/lib/python2.7/json/decoder.py\", line 364, in decode\n obj, end = self.raw_decode(s, idx=_w(s, 0).end())\nTypeError: expected string or buffer\n",
"module_stdout": "",
"msg": "MODULE FAILURE"
```
|
main
|
junos config obj end self raw decode s idx w s end typeerror expected string or buffer issue type bug report component name junos config ansible version configuration os environment summary steps to reproduce run junos test cases or manually name configure device with config junos config src basic config provider netconf register result templates basic config interfaces unit family inet address expected results actual results yaml task task path tmp run network test junos devel ansible test integration targets junos config tests netconf src basic yaml using module file usr local lib dist packages ansible modules core network junos junos config py establish local connection for user johnb exec bin sh c umask mkdir p echo home ansible tmp ansible tmp echo ansible tmp echo home ansible tmp ansible tmp sleep put tmp to home johnb ansible tmp ansible tmp junos config py exec bin sh c chmod u x home johnb ansible tmp ansible tmp home johnb ansible tmp ansible tmp junos config py sleep exec bin sh c python home johnb ansible tmp ansible tmp junos config py rm rf home johnb ansible tmp ansible tmp dev null sleep an exception occurred during task execution the full traceback is traceback most recent call last file tmp ansible ansible module junos config py line in main file tmp ansible ansible module junos config py line in main run module result file tmp ansible ansible module junos config py line in run return load config module result file tmp ansible ansible module junos config py line in load config config format module params or guess format candidate file tmp ansible ansible module junos config py line in guess format json loads config file usr lib json init py line in loads return default decoder decode s file usr lib json decoder py line in decode obj end self raw decode s idx w s end typeerror expected string or buffer fatal failed changed false failed true invocation module args provider host password ansible transport netconf username ansible src interfaces n n unit n family inet n address n n n n n n module name junos config module stderr traceback most recent call last n file tmp ansible ansible module junos config py line in n main n file tmp ansible ansible module junos config py line in main n run module result n file tmp ansible ansible module junos config py line in run n return load config module result n file tmp ansible ansible module junos config py line in load config n config format module params or guess format candidate n file tmp ansible ansible module junos config py line in guess format n json loads config n file usr lib json init py line in loads n return default decoder decode s n file usr lib json decoder py line in decode n obj end self raw decode s idx w s end ntypeerror expected string or buffer n module stdout msg module failure
| 1
|
54,570
| 13,771,533,231
|
IssuesEvent
|
2020-10-07 22:13:17
|
STEllAR-GROUP/hpx
|
https://api.github.com/repos/STEllAR-GROUP/hpx
|
opened
|
hpx::lcos::barrier() results in deadlock
|
category: LCOs category: parcel transport compiler: gcc platform: Linux project: Phylanx type: defect
|
## Expected Behavior
According to the documentation, using `hpx::lcos::barrier("barrier_name")` without specifying the number of localities or the rank should assume all the localities, and the current locality as the rank.
## Actual Behavior
Deadlock.
A similar problem is true for gather_here() and broadcast_to() - it requires at least the locality count to compile/work correctly.
## Steps to Reproduce the Problem
The Phylanx project is using HPX, and in a distributed run, APEX is using HPX collectives to do event unification at the end of execution.
1. Configure HPX with MPI support and APEX enabled
1. Configure Phylanx
1. Run a Phylanx distributed example with the environment variable `APEX_OTF2=1` set. It won't deadlock with the current code, but if these lines are changed to use default argument values, it will deadlock:
https://github.com/khuck/xpress-apex/blob/f666086dc469f48c220997d1b6b121e01d3c3afc/src/apex/otf2_listener.cpp#L1453
https://github.com/khuck/xpress-apex/blob/f666086dc469f48c220997d1b6b121e01d3c3afc/src/apex/otf2_listener.cpp#L1588
## Specifications
... Please describe your environment
- HPX Version: current master
- Platform (compiler, OS): linux GCC 7
h/t @stevenrbrandt
|
1.0
|
hpx::lcos::barrier() results in deadlock - ## Expected Behavior
According to the documentation, using `hpx::lcos::barrier("barrier_name")` without specifying the number of localities or the rank should assume all the localities, and the current locality as the rank.
## Actual Behavior
Deadlock.
A similar problem is true for gather_here() and broadcast_to() - it requires at least the locality count to compile/work correctly.
## Steps to Reproduce the Problem
The Phylanx project is using HPX, and in a distributed run, APEX is using HPX collectives to do event unification at the end of execution.
1. Configure HPX with MPI support and APEX enabled
1. Configure Phylanx
1. Run a Phylanx distributed example with the environment variable `APEX_OTF2=1` set. It won't deadlock with the current code, but if these lines are changed to use default argument values, it will deadlock:
https://github.com/khuck/xpress-apex/blob/f666086dc469f48c220997d1b6b121e01d3c3afc/src/apex/otf2_listener.cpp#L1453
https://github.com/khuck/xpress-apex/blob/f666086dc469f48c220997d1b6b121e01d3c3afc/src/apex/otf2_listener.cpp#L1588
## Specifications
... Please describe your environment
- HPX Version: current master
- Platform (compiler, OS): linux GCC 7
h/t @stevenrbrandt
|
non_main
|
hpx lcos barrier results in deadlock expected behavior according to the documentation using hpx lcos barrier barrier name without specifying the number of localities or the rank should assume all the localities and the current locality as the rank actual behavior deadlock a similar problem is true for gather here and broadcast to it requires at least the locality count to compile work correctly steps to reproduce the problem the phylanx project is using hpx and in a distributed run apex is using hpx collectives to do event unification at the end of execution configure hpx with mpi support and apex enabled configure phylanx run a phylanx distributed example with the environment variable apex set it won t deadlock with the current code but if these lines are changed to use default argument values it will deadlock specifications please describe your environment hpx version current master platform compiler os linux gcc h t stevenrbrandt
| 0
|
319,623
| 23,782,055,802
|
IssuesEvent
|
2022-09-02 06:24:49
|
SenseNet/sensenet
|
https://api.github.com/repos/SenseNet/sensenet
|
closed
|
Docs site technology, build and architecture know-how
|
documentation
|
Get familiar with the technology and the possibilities, e.g. how the menu works, how do we change the structure.
|
1.0
|
Docs site technology, build and architecture know-how - Get familiar with the technology and the possibilities, e.g. how the menu works, how do we change the structure.
|
non_main
|
docs site technology build and architecture know how get familiar with the technology and the possibilities e g how the menu works how do we change the structure
| 0
|
2,289
| 8,142,269,607
|
IssuesEvent
|
2018-08-21 06:57:56
|
TabbycatDebate/tabbycat
|
https://api.github.com/repos/TabbycatDebate/tabbycat
|
closed
|
Rankings generator crashes when only one metric in precedence
|
awaiting maintainer bugs
|
BACKEND-VR: https://sentry.io/tabbycat-ig/backend/issues/645557194/
I think it crashes because when trying to generate a subrank, it looks for `metrics[1:]`, which is an empty list whenever the team standings precedence has only one element in it.
```
TypeError: itemgetter expected 1 arguments, got 0
(9 additional frame(s) were not displayed)
...
File "draw/manager.py", line 191, in get_teams
generator = TeamStandingsGenerator(metrics, ('rank', 'subrank'), tiebreak="random")
File "standings/base.py", line 294, in __init__
self._interpret_rankings(rankings)
File "standings/base.py", line 393, in _interpret_rankings
annotator = klass(self.precedence)
File "standings/ranking.py", line 97, in __init__
self.rank_key = metricgetter(*metrics[1:])
File "standings/metrics.py", line 23, in metricgetter
metricitemgetter = itemgetter(*items)
TypeError: itemgetter expected 1 arguments, got 0
```
|
True
|
Rankings generator crashes when only one metric in precedence - BACKEND-VR: https://sentry.io/tabbycat-ig/backend/issues/645557194/
I think it crashes because when trying to generate a subrank, it looks for `metrics[1:]`, which is an empty list whenever the team standings precedence has only one element in it.
```
TypeError: itemgetter expected 1 arguments, got 0
(9 additional frame(s) were not displayed)
...
File "draw/manager.py", line 191, in get_teams
generator = TeamStandingsGenerator(metrics, ('rank', 'subrank'), tiebreak="random")
File "standings/base.py", line 294, in __init__
self._interpret_rankings(rankings)
File "standings/base.py", line 393, in _interpret_rankings
annotator = klass(self.precedence)
File "standings/ranking.py", line 97, in __init__
self.rank_key = metricgetter(*metrics[1:])
File "standings/metrics.py", line 23, in metricgetter
metricitemgetter = itemgetter(*items)
TypeError: itemgetter expected 1 arguments, got 0
```
|
main
|
rankings generator crashes when only one metric in precedence backend vr i think it crashes because when trying to generate a subrank it looks for metrics which is an empty list whenever the team standings precedence has only one element in it typeerror itemgetter expected arguments got additional frame s were not displayed file draw manager py line in get teams generator teamstandingsgenerator metrics rank subrank tiebreak random file standings base py line in init self interpret rankings rankings file standings base py line in interpret rankings annotator klass self precedence file standings ranking py line in init self rank key metricgetter metrics file standings metrics py line in metricgetter metricitemgetter itemgetter items typeerror itemgetter expected arguments got
| 1
|
246,470
| 20,866,896,963
|
IssuesEvent
|
2022-03-22 08:15:11
|
trinodb/trino
|
https://api.github.com/repos/trinodb/trino
|
opened
|
Flaky TestingSqlServer initialization due to log message wait strategy
|
bug test
|
The expected message "The default collation was successfully changed." was logged, but `LogMessageWaitStrategy` seems failing:
```
2022-03-22T07:57:36.5495854Z org.testcontainers.containers.ContainerLaunchException: Timed out waiting for log output matching '.*The default collation was successfully changed.*'
2022-03-22T07:57:36.5497129Z at org.testcontainers.containers.wait.strategy.LogMessageWaitStrategy.waitUntilReady(LogMessageWaitStrategy.java:49)
2022-03-22T07:57:36.5498130Z at org.testcontainers.containers.wait.strategy.AbstractWaitStrategy.waitUntilReady(AbstractWaitStrategy.java:51)
2022-03-22T07:57:36.5499151Z at io.trino.plugin.sqlserver.TestingSqlServer$1TestingMSSQLServerContainer.waitUntilContainerStarted(TestingSqlServer.java:120)
2022-03-22T07:57:36.5500204Z at org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:468)
2022-03-22T07:57:36.5503025Z at org.testcontainers.containers.GenericContainer.lambda$doStart$0(GenericContainer.java:331)
2022-03-22T07:57:36.5503817Z at org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:81)
2022-03-22T07:57:36.5505293Z at org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:329)
2022-03-22T07:57:36.5505993Z at org.testcontainers.containers.GenericContainer.start(GenericContainer.java:317)
2022-03-22T07:57:36.5506739Z at io.trino.testing.containers.TestContainers.startOrReuse(TestContainers.java:42)
2022-03-22T07:57:36.5507443Z at io.trino.plugin.sqlserver.TestingSqlServer.createContainer(TestingSqlServer.java:142)
2022-03-22T07:57:36.5508103Z at io.trino.plugin.sqlserver.TestingSqlServer.lambda$new$3(TestingSqlServer.java:90)
2022-03-22T07:57:36.5508682Z at net.jodah.failsafe.Functions.lambda$get$0(Functions.java:48)
2022-03-22T07:57:36.5555607Z at net.jodah.failsafe.TimeoutExecutor.lambda$supply$2(TimeoutExecutor.java:91)
2022-03-22T07:57:36.5643602Z at net.jodah.failsafe.RetryPolicyExecutor.lambda$supply$0(RetryPolicyExecutor.java:62)
2022-03-22T07:57:36.5644138Z at net.jodah.failsafe.Execution.executeSync(Execution.java:129)
2022-03-22T07:57:36.5644600Z at net.jodah.failsafe.FailsafeExecutor.call(FailsafeExecutor.java:376)
2022-03-22T07:57:36.5646940Z at net.jodah.failsafe.FailsafeExecutor.get(FailsafeExecutor.java:67)
2022-03-22T07:57:36.5647426Z at io.trino.plugin.sqlserver.TestingSqlServer.<init>(TestingSqlServer.java:90)
2022-03-22T07:57:36.5647998Z at io.trino.plugin.sqlserver.TestingSqlServer.<init>(TestingSqlServer.java:84)
2022-03-22T07:57:36.5653802Z at io.trino.plugin.sqlserver.BaseSqlServerTransactionIsolationTest.createQueryRunner(BaseSqlServerTransactionIsolationTest.java:37)
2022-03-22T07:57:36.5654811Z at io.trino.testing.AbstractTestQueryFramework.init(AbstractTestQueryFramework.java:94)
2022-03-22T07:57:36.5655373Z at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2022-03-22T07:57:36.5655969Z at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
2022-03-22T07:57:36.5656991Z at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
2022-03-22T07:57:36.5657525Z at java.base/java.lang.reflect.Method.invoke(Method.java:566)
2022-03-22T07:57:36.5658035Z at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:104)
2022-03-22T07:57:36.5658694Z at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:515)
2022-03-22T07:57:36.5659195Z at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:217)
2022-03-22T07:57:36.5659672Z at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:144)
2022-03-22T07:57:36.5660226Z at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:169)
2022-03-22T07:57:36.5660877Z at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108)
2022-03-22T07:57:36.5661502Z at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
2022-03-22T07:57:36.5662179Z at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
2022-03-22T07:57:36.5662600Z at java.base/java.lang.Thread.run(Thread.java:829)
2022-03-22T07:57:36.5662791Z
2022-03-22T07:57:36.5662799Z
2022-03-22T07:57:36.5664006Z 2022-03-22T01:57:36.500-0600 INFO dispatcher-query-80 io.trino.event.QueryMonitor TIMELINE: Query 20220322_075736_00846_vjzbw :: Transaction:[ae138008-3e50-4f1d-9d47-621245fcbed0] :: elapsed 242ms :: planning 43ms :: waiting 93ms :: scheduling 108ms :: running 74ms :: finishing 17ms :: begin 2022-03-22T01:57:36.243-06:00 :: end 2022-03-22T01:57:36.485-06:00
```
<details><summary>open</summary>
<p>
```
2022-03-22T07:57:36.5665015Z 2022-03-22T01:57:36.518-0600 ERROR pool-4-thread-2 🐳 [mcr.microsoft.com/mssql/server:2017-CU13] Log output from the failed container:
2022-03-22T07:57:36.5665793Z 2022-03-22 07:53:32.13 Server Setup step is copying system data file 'C:\templatedata\master.mdf' to '/var/opt/mssql/data/master.mdf'.
2022-03-22T07:57:36.5666079Z
2022-03-22T07:57:36.5666958Z 2022-03-22 07:53:32.22 Server Did not find an existing master data file /var/opt/mssql/data/master.mdf, copying the missing default master and other system database files. If you have moved the database location, but not moved the database files, startup may fail. To repair: shutdown SQL Server, move the master database to configured location, and restart.
2022-03-22T07:57:36.5667573Z
2022-03-22T07:57:36.5667997Z 2022-03-22 07:53:32.22 Server Setup step is copying system data file 'C:\templatedata\mastlog.ldf' to '/var/opt/mssql/data/mastlog.ldf'.
2022-03-22T07:57:36.5668276Z
2022-03-22T07:57:36.5668663Z 2022-03-22 07:53:32.23 Server Setup step is copying system data file 'C:\templatedata\model.mdf' to '/var/opt/mssql/data/model.mdf'.
2022-03-22T07:57:36.5669022Z
2022-03-22T07:57:36.5669453Z 2022-03-22 07:53:32.24 Server Setup step is copying system data file 'C:\templatedata\modellog.ldf' to '/var/opt/mssql/data/modellog.ldf'.
2022-03-22T07:57:36.5669733Z
2022-03-22T07:57:36.5670145Z 2022-03-22 07:53:32.26 Server Setup step is copying system data file 'C:\templatedata\msdbdata.mdf' to '/var/opt/mssql/data/msdbdata.mdf'.
2022-03-22T07:57:36.5670511Z
2022-03-22T07:57:36.5670930Z 2022-03-22 07:53:32.28 Server Setup step is copying system data file 'C:\templatedata\msdblog.ldf' to '/var/opt/mssql/data/msdblog.ldf'.
2022-03-22T07:57:36.5671202Z
2022-03-22T07:57:36.5671614Z 2022-03-22 07:53:32.38 Server Microsoft SQL Server 2017 (RTM-CU13) (KB4466404) - 14.0.3048.4 (X64)
2022-03-22T07:57:36.5671831Z
2022-03-22T07:57:36.5671930Z Nov 30 2018 12:57:58
2022-03-22T07:57:36.5672062Z
2022-03-22T07:57:36.5672202Z Copyright (C) 2017 Microsoft Corporation
2022-03-22T07:57:36.5672372Z
2022-03-22T07:57:36.5672613Z Developer Edition (64-bit) on Linux (Ubuntu 16.04.5 LTS)
2022-03-22T07:57:36.5672796Z
2022-03-22T07:57:36.5673106Z 2022-03-22 07:53:32.39 Server UTC adjustment: 0:00
2022-03-22T07:57:36.5673370Z
2022-03-22T07:57:36.5673614Z 2022-03-22 07:53:32.39 Server (c) Microsoft Corporation.
2022-03-22T07:57:36.5673790Z
2022-03-22T07:57:36.5674010Z 2022-03-22 07:53:32.39 Server All rights reserved.
2022-03-22T07:57:36.5674166Z
2022-03-22T07:57:36.5674399Z 2022-03-22 07:53:32.39 Server Server process ID is 4124.
2022-03-22T07:57:36.5674571Z
2022-03-22T07:57:36.5674989Z 2022-03-22 07:53:32.40 Server Logging SQL Server messages in file '/var/opt/mssql/log/errorlog'.
2022-03-22T07:57:36.5675216Z
2022-03-22T07:57:36.5675464Z 2022-03-22 07:53:32.40 Server Registry startup parameters:
2022-03-22T07:57:36.5675648Z
2022-03-22T07:57:36.5675839Z -d /var/opt/mssql/data/master.mdf
2022-03-22T07:57:36.5815627Z
2022-03-22T07:57:36.5816092Z -l /var/opt/mssql/data/mastlog.ldf
2022-03-22T07:57:36.5816289Z
2022-03-22T07:57:36.5816470Z -e /var/opt/mssql/log/errorlog
2022-03-22T07:57:36.5816628Z
2022-03-22T07:57:36.5817607Z 2022-03-22 07:53:32.40 Server SQL Server detected 1 sockets with 2 cores per socket and 2 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2022-03-22T07:57:36.5818056Z
2022-03-22T07:57:36.5818508Z 2022-03-22 07:53:32.41 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2022-03-22T07:57:36.5818788Z
2022-03-22T07:57:36.5853614Z 2022-03-22 07:53:32.41 Server Detected 5558 MB of RAM. This is an informational message; no user action is required.
2022-03-22T07:57:36.5855204Z
2022-03-22T07:57:36.5855564Z 2022-03-22 07:53:32.42 Server Using conventional memory in the memory manager.
2022-03-22T07:57:36.5855786Z
2022-03-22T07:57:36.5856365Z 2022-03-22 07:53:32.44 Server Machine supports memory error recovery. SQL memory protection is enabled to recover from memory corruption.
2022-03-22T07:57:36.5856660Z
2022-03-22T07:57:36.5856993Z 2022-03-22 07:53:32.66 Server Buffer pool extension is already disabled. No action is necessary.
2022-03-22T07:57:36.5857232Z
2022-03-22T07:57:36.5857617Z 2022-03-22 07:53:32.83 Server InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
2022-03-22T07:57:36.5857884Z
2022-03-22T07:57:36.5860478Z 2022-03-22 07:53:32.84 Server Implied authentication manager initialization failed. Implied authentication will be disabled.
2022-03-22T07:57:36.5860755Z
2022-03-22T07:57:36.5862695Z 2022-03-22 07:53:32.84 Server Successfully initialized the TLS configuration. Allowed TLS protocol versions are ['1.0 1.1 1.2']. Allowed TLS ciphers are ['ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:!DHE-RSA-AES256-GCM-SHA384:!DHE-RSA-AES128-GCM-SHA256:!DHE-RSA-AES256-SHA:!DHE-RSA-AES128-SHA'].
2022-03-22T07:57:36.5865359Z
2022-03-22T07:57:36.5865749Z 2022-03-22 07:53:32.90 Server The maximum number of dedicated administrator connections for this instance is '1'
2022-03-22T07:57:36.5866235Z
2022-03-22T07:57:36.5866955Z 2022-03-22 07:53:32.90 Server Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2022-03-22T07:57:36.5867372Z
2022-03-22T07:57:36.5868129Z 2022-03-22 07:53:32.92 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2022-03-22T07:57:36.5868480Z
2022-03-22T07:57:36.5868762Z 2022-03-22 07:53:32.95 Server In-Memory OLTP initialized on lowend machine.
2022-03-22T07:57:36.5868979Z
2022-03-22T07:57:36.5871513Z 2022-03-22 07:53:33.06 Server Database Instant File Initialization: enabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
2022-03-22T07:57:36.5871965Z
2022-03-22T07:57:36.5872113Z ForceFlush is enabled for this instance.
2022-03-22T07:57:36.5872523Z
2022-03-22T07:57:36.5872876Z 2022-03-22 07:53:33.07 Server Query Store settings initialized with enabled = 1,
2022-03-22T07:57:36.5873091Z
2022-03-22T07:57:36.5873615Z 2022-03-22 07:53:33.09 Server Software Usage Metrics is disabled.
2022-03-22T07:57:36.5874546Z
2022-03-22T07:57:36.5874829Z 2022-03-22 07:53:33.10 spid6s Starting up database 'master'.
2022-03-22T07:57:36.5875016Z
2022-03-22T07:57:36.5875208Z ForceFlush feature is enabled for log durability.
2022-03-22T07:57:36.5875393Z
2022-03-22T07:57:36.5876355Z 2022-03-22 07:53:33.56 spid6s The tail of the log for database master is being rewritten to match the new sector size of 4096 bytes. 3072 bytes at offset 418816 in file /var/opt/mssql/data/mastlog.ldf will be written.
2022-03-22T07:57:36.5876995Z
2022-03-22T07:57:36.5877359Z 2022-03-22 07:53:33.90 spid6s Converting database 'master' from version 862 to the current version 869.
2022-03-22T07:57:36.5877590Z
2022-03-22T07:57:36.5877941Z 2022-03-22 07:53:33.91 spid6s Database 'master' running the upgrade step from version 862 to version 863.
2022-03-22T07:57:36.5878173Z
2022-03-22T07:57:36.5878508Z 2022-03-22 07:53:33.92 spid6s Database 'master' running the upgrade step from version 863 to version 864.
2022-03-22T07:57:36.5878735Z
2022-03-22T07:57:36.5879305Z 2022-03-22 07:53:33.94 spid6s Database 'master' running the upgrade step from version 864 to version 865.
2022-03-22T07:57:36.5879538Z
2022-03-22T07:57:36.5879867Z 2022-03-22 07:53:33.95 spid6s Database 'master' running the upgrade step from version 865 to version 866.
2022-03-22T07:57:36.5880094Z
2022-03-22T07:57:36.5880430Z 2022-03-22 07:53:33.96 spid6s Database 'master' running the upgrade step from version 866 to version 867.
2022-03-22T07:57:36.5880660Z
2022-03-22T07:57:36.5880994Z 2022-03-22 07:53:33.97 spid6s Database 'master' running the upgrade step from version 867 to version 868.
2022-03-22T07:57:36.5881225Z
2022-03-22T07:57:36.5881761Z 2022-03-22 07:53:33.99 spid6s Database 'master' running the upgrade step from version 868 to version 869.
2022-03-22T07:57:36.5881992Z
2022-03-22T07:57:36.5882282Z 2022-03-22 07:53:34.38 spid6s Resource governor reconfiguration succeeded.
2022-03-22T07:57:36.5882490Z
2022-03-22T07:57:36.5883201Z 2022-03-22 07:53:34.38 spid6s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2022-03-22T07:57:36.5883811Z
2022-03-22T07:57:36.5885174Z 2022-03-22 07:53:34.39 spid6s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2022-03-22T07:57:36.5885450Z
2022-03-22T07:57:36.5885734Z 2022-03-22 07:53:34.47 spid6s SQL Trace ID 1 was started by login "sa".
2022-03-22T07:57:36.5885929Z
2022-03-22T07:57:36.5886630Z 2022-03-22 07:53:34.50 spid6s Server name is '4fd4a1f8c943'. This is an informational message only. No user action is required.
2022-03-22T07:57:36.5887266Z
2022-03-22T07:57:36.5887561Z 2022-03-22 07:53:34.50 spid19s Password policy update was successful.
2022-03-22T07:57:36.5887763Z
2022-03-22T07:57:36.5888004Z 2022-03-22 07:53:34.54 spid6s Starting up database 'msdb'.
2022-03-22T07:57:36.5888181Z
2022-03-22T07:57:36.5888881Z 2022-03-22 07:53:34.54 spid22s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
2022-03-22T07:57:36.5889181Z
2022-03-22T07:57:36.5889464Z 2022-03-22 07:53:34.55 spid9s Starting up database 'mssqlsystemresource'.
2022-03-22T07:57:36.5889671Z
2022-03-22T07:57:36.5890848Z 2022-03-22 07:53:34.55 spid22s Always On: The availability replica manager is waiting for the instance of SQL Server to allow client connections. This is an informational message only. No user action is required.
2022-03-22T07:57:36.5891379Z
2022-03-22T07:57:36.5891842Z 2022-03-22 07:53:34.57 spid9s The resource database build version is 14.00.3048. This is an informational message only. No user action is required.
2022-03-22T07:57:36.5892109Z
2022-03-22T07:57:36.5892349Z 2022-03-22 07:53:34.64 spid9s Starting up database 'model'.
2022-03-22T07:57:36.5892531Z
2022-03-22T07:57:36.5892870Z 2022-03-22 07:53:35.22 spid19s A self-generated certificate was successfully loaded for encryption.
2022-03-22T07:57:36.5893141Z
2022-03-22T07:57:36.5893642Z 2022-03-22 07:53:35.24 spid19s Server is listening on [ 'any' <ipv4> 1433].
2022-03-22T07:57:36.5893843Z
2022-03-22T07:57:36.5894129Z 2022-03-22 07:53:35.25 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2022-03-22T07:57:36.5894405Z
2022-03-22T07:57:36.5894986Z 2022-03-22 07:53:35.25 spid9s The tail of the log for database model is being rewritten to match the new sector size of 4096 bytes. 2048 bytes at offset 75776 in file /var/opt/mssql/data/modellog.ldf will be written.
2022-03-22T07:57:36.5895325Z
2022-03-22T07:57:36.5895995Z 2022-03-22 07:53:35.25 Server Dedicated admin connection support was established for listening locally on port 1434.
2022-03-22T07:57:36.5896253Z
2022-03-22T07:57:36.5896824Z 2022-03-22 07:53:35.25 spid6s The tail of the log for database msdb is being rewritten to match the new sector size of 4096 bytes. 512 bytes at offset 306688 in file /var/opt/mssql/data/MSDBLog.ldf will be written.
2022-03-22T07:57:36.5897152Z
2022-03-22T07:57:36.5897491Z 2022-03-22 07:53:35.28 spid9s Converting database 'model' from version 862 to the current version 869.
2022-03-22T07:57:36.5897717Z
2022-03-22T07:57:36.5898060Z 2022-03-22 07:53:35.28 spid9s Database 'model' running the upgrade step from version 862 to version 863.
2022-03-22T07:57:36.5898293Z
2022-03-22T07:57:36.5899033Z 2022-03-22 07:53:35.28 spid6s Converting database 'msdb' from version 862 to the current version 869.
2022-03-22T07:57:36.5899262Z
2022-03-22T07:57:36.5899601Z 2022-03-22 07:53:35.29 spid6s Database 'msdb' running the upgrade step from version 862 to version 863.
2022-03-22T07:57:36.5899832Z
2022-03-22T07:57:36.5900169Z 2022-03-22 07:53:35.30 spid9s Database 'model' running the upgrade step from version 863 to version 864.
2022-03-22T07:57:36.5900393Z
2022-03-22T07:57:36.5900796Z 2022-03-22 07:53:35.32 spid19s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2022-03-22T07:57:36.5901271Z
2022-03-22T07:57:36.5901619Z 2022-03-22 07:53:35.33 spid6s Database 'msdb' running the upgrade step from version 863 to version 864.
2022-03-22T07:57:36.5901847Z
2022-03-22T07:57:36.5902389Z 2022-03-22 07:53:35.33 spid9s Database 'model' running the upgrade step from version 864 to version 865.
2022-03-22T07:57:36.5902630Z
2022-03-22T07:57:36.5902976Z 2022-03-22 07:53:35.34 spid9s Database 'model' running the upgrade step from version 865 to version 866.
2022-03-22T07:57:36.5903200Z
2022-03-22T07:57:36.5903528Z 2022-03-22 07:53:35.34 spid9s Database 'model' running the upgrade step from version 866 to version 867.
2022-03-22T07:57:36.5903946Z
2022-03-22T07:57:36.5904290Z 2022-03-22 07:53:35.34 spid6s Database 'msdb' running the upgrade step from version 864 to version 865.
2022-03-22T07:57:36.5904516Z
2022-03-22T07:57:36.5904851Z 2022-03-22 07:53:35.34 spid9s Database 'model' running the upgrade step from version 867 to version 868.
2022-03-22T07:57:36.5905074Z
2022-03-22T07:57:36.5905621Z 2022-03-22 07:53:35.35 spid6s Database 'msdb' running the upgrade step from version 865 to version 866.
2022-03-22T07:57:36.5905843Z
2022-03-22T07:57:36.5906181Z 2022-03-22 07:53:35.35 spid6s Database 'msdb' running the upgrade step from version 866 to version 867.
2022-03-22T07:57:36.5906547Z
2022-03-22T07:57:36.5906882Z 2022-03-22 07:53:35.36 spid9s Database 'model' running the upgrade step from version 868 to version 869.
2022-03-22T07:57:36.5907303Z
2022-03-22T07:57:36.5907642Z 2022-03-22 07:53:35.36 spid6s Database 'msdb' running the upgrade step from version 867 to version 868.
2022-03-22T07:57:36.5907862Z
2022-03-22T07:57:36.5908192Z 2022-03-22 07:53:35.37 spid6s Database 'msdb' running the upgrade step from version 868 to version 869.
2022-03-22T07:57:36.5908421Z
2022-03-22T07:57:36.5908642Z 2022-03-22 07:53:35.47 spid9s Polybase feature disabled.
2022-03-22T07:57:36.5908820Z
2022-03-22T07:57:36.5909283Z 2022-03-22 07:53:35.48 spid9s Clearing tempdb database.
2022-03-22T07:57:36.5909462Z
2022-03-22T07:57:36.5909711Z 2022-03-22 07:53:36.09 spid9s Starting up database 'tempdb'.
2022-03-22T07:57:36.5909892Z
2022-03-22T07:57:36.5910233Z 2022-03-22 07:53:36.35 spid9s The tempdb database has 1 data file(s).
2022-03-22T07:57:36.5910431Z
2022-03-22T07:57:36.5911069Z 2022-03-22 07:53:36.35 spid24s The Service Broker endpoint is in disabled or stopped state.
2022-03-22T07:57:36.5911300Z
2022-03-22T07:57:36.5911632Z 2022-03-22 07:53:36.35 spid24s The Database Mirroring endpoint is in disabled or stopped state.
2022-03-22T07:57:36.5911851Z
2022-03-22T07:57:36.5912102Z 2022-03-22 07:53:36.37 spid24s Service Broker manager has started.
2022-03-22T07:57:36.5912287Z
2022-03-22T07:57:36.5912887Z 2022-03-22 07:53:36.45 spid6s Recovery is complete. This is an informational message only. No user action is required.
2022-03-22T07:57:36.5913140Z
2022-03-22T07:57:36.5913493Z 2022-03-22 07:53:36.49 spid22s The default language (LCID 0) has been set for engine and full-text services.
2022-03-22T07:57:36.5913722Z
2022-03-22T07:57:36.5913944Z 2022-03-22 07:53:36.51 spid22s Warning ******************
2022-03-22T07:57:36.5914111Z
2022-03-22T07:57:36.5914419Z 2022-03-22 07:53:36.51 spid22s Attempting to change default collation to Latin1_General_CS_AS.
2022-03-22T07:57:36.5914852Z
2022-03-22T07:57:36.5915139Z 2022-03-22 07:53:36.58 spid22s index restored for master.syspriorities.
2022-03-22T07:57:36.5915341Z
2022-03-22T07:57:36.5915605Z 2022-03-22 07:53:38.10 spid22s index restored for master.sysbrickfiles.
2022-03-22T07:57:36.5915806Z
2022-03-22T07:57:36.5916634Z 2022-03-22 07:53:38.10 spid22s index restored for master.sysowners.
2022-03-22T07:57:36.5916853Z
2022-03-22T07:57:36.5917148Z 2022-03-22 07:53:38.10 spid22s index restored for master.sysdbreg.
2022-03-22T07:57:36.5917333Z
2022-03-22T07:57:36.5917596Z 2022-03-22 07:53:38.11 spid22s index restored for master.sysschobjs.
2022-03-22T07:57:36.5918014Z
2022-03-22T07:57:36.5918303Z 2022-03-22 07:53:38.11 spid22s index restored for master.sysextsources.
2022-03-22T07:57:36.5918504Z
2022-03-22T07:57:36.5918799Z 2022-03-22 07:53:38.12 spid22s index restored for master.sysextfileformats.
2022-03-22T07:57:36.5919006Z
2022-03-22T07:57:36.5919466Z 2022-03-22 07:53:38.12 spid22s index restored for master.syscolpars.
2022-03-22T07:57:36.5919662Z
2022-03-22T07:57:36.5919923Z 2022-03-22 07:53:38.12 spid22s index restored for master.sysxlgns.
2022-03-22T07:57:36.5920100Z
2022-03-22T07:57:36.5920356Z 2022-03-22 07:53:38.12 spid22s index restored for master.sysxsrvs.
2022-03-22T07:57:36.5920750Z
2022-03-22T07:57:36.5921017Z 2022-03-22 07:53:38.13 spid22s index restored for master.sysnsobjs.
2022-03-22T07:57:36.5921210Z
2022-03-22T07:57:36.5921463Z 2022-03-22 07:53:38.13 spid22s index restored for master.syscerts.
2022-03-22T07:57:36.5921648Z
2022-03-22T07:57:36.5921902Z 2022-03-22 07:53:38.13 spid22s index restored for master.sysrmtlgns.
2022-03-22T07:57:36.5922091Z
2022-03-22T07:57:36.5922349Z 2022-03-22 07:53:38.13 spid22s index restored for master.sysxprops.
2022-03-22T07:57:36.5922537Z
2022-03-22T07:57:36.5923183Z 2022-03-22 07:53:38.13 spid22s index restored for master.sysscalartypes.
2022-03-22T07:57:36.5923815Z
2022-03-22T07:57:36.5924111Z 2022-03-22 07:53:38.13 spid22s index restored for master.sysidxstats.
2022-03-22T07:57:36.5924308Z
2022-03-22T07:57:36.5924914Z 2022-03-22 07:53:38.13 spid22s index restored for master.sysendpts.
2022-03-22T07:57:36.5925110Z
2022-03-22T07:57:36.5925381Z 2022-03-22 07:53:38.13 spid22s index restored for master.sysclsobjs.
2022-03-22T07:57:36.5925561Z
2022-03-22T07:57:36.5925837Z 2022-03-22 07:53:38.14 spid22s index restored for master.sysremsvcbinds.
2022-03-22T07:57:36.5926037Z
2022-03-22T07:57:36.5926336Z 2022-03-22 07:53:38.14 spid22s index restored for master.sysrts.
2022-03-22T07:57:36.5926769Z
2022-03-22T07:57:36.5927045Z 2022-03-22 07:53:38.14 spid22s index restored for master.sysasymkeys.
2022-03-22T07:57:36.5927242Z
2022-03-22T07:57:36.5927510Z 2022-03-22 07:53:38.14 spid22s index restored for master.syssqlguides.
2022-03-22T07:57:36.5927705Z
2022-03-22T07:57:36.5928075Z 2022-03-22 07:53:38.14 spid22s index restored for master.syssoftobjrefs.
2022-03-22T07:57:36.5928504Z
2022-03-22T07:57:36.5928811Z 2022-03-22 07:53:38.15 spid22s index restored for master.MSreplication_options.
2022-03-22T07:57:36.5929027Z
2022-03-22T07:57:36.5929306Z 2022-03-22 07:53:38.19 spid22s index restored for tempdb.syspriorities.
2022-03-22T07:57:36.5929503Z
2022-03-22T07:57:36.5929757Z 2022-03-22 07:53:38.19 spid22s index restored for tempdb.sysowners.
2022-03-22T07:57:36.5930638Z
2022-03-22T07:57:36.5930914Z 2022-03-22 07:53:38.19 spid22s index restored for tempdb.sysdbreg.
2022-03-22T07:57:36.5931104Z
2022-03-22T07:57:36.5931350Z 2022-03-22 07:53:38.20 spid22s index restored for tempdb.sysschobjs.
2022-03-22T07:57:36.5931546Z
2022-03-22T07:57:36.5931823Z 2022-03-22 07:53:38.21 spid22s index restored for tempdb.sysextsources.
2022-03-22T07:57:36.5932397Z
2022-03-22T07:57:36.5932699Z 2022-03-22 07:53:38.21 spid22s index restored for tempdb.sysextfileformats.
2022-03-22T07:57:36.5932908Z
2022-03-22T07:57:36.5933168Z 2022-03-22 07:53:38.22 spid22s index restored for tempdb.syscolpars.
2022-03-22T07:57:36.5933359Z
2022-03-22T07:57:36.5933612Z 2022-03-22 07:53:38.22 spid22s index restored for tempdb.sysxlgns.
2022-03-22T07:57:36.5933800Z
2022-03-22T07:57:36.5934052Z 2022-03-22 07:53:38.22 spid22s index restored for tempdb.sysxsrvs.
2022-03-22T07:57:36.5934459Z
2022-03-22T07:57:36.5934729Z 2022-03-22 07:53:38.22 spid22s index restored for tempdb.sysnsobjs.
2022-03-22T07:57:36.5935207Z
2022-03-22T07:57:36.5935485Z 2022-03-22 07:53:38.22 spid22s index restored for tempdb.syscerts.
2022-03-22T07:57:36.5935668Z
2022-03-22T07:57:36.5935928Z 2022-03-22 07:53:38.23 spid22s index restored for tempdb.sysrmtlgns.
2022-03-22T07:57:36.5936122Z
2022-03-22T07:57:36.5936972Z 2022-03-22 07:53:38.23 spid22s index restored for tempdb.sysxprops.
2022-03-22T07:57:36.5937179Z
2022-03-22T07:57:36.5937479Z 2022-03-22 07:53:38.24 spid22s index restored for tempdb.sysscalartypes.
2022-03-22T07:57:36.5937687Z
2022-03-22T07:57:36.5937951Z 2022-03-22 07:53:38.24 spid22s index restored for tempdb.sysidxstats.
2022-03-22T07:57:36.5938142Z
2022-03-22T07:57:36.5938398Z 2022-03-22 07:53:38.24 spid22s index restored for tempdb.sysendpts.
2022-03-22T07:57:36.5938590Z
2022-03-22T07:57:36.5939057Z 2022-03-22 07:53:38.24 spid22s index restored for tempdb.sysclsobjs.
2022-03-22T07:57:36.5939258Z
2022-03-22T07:57:36.5939537Z 2022-03-22 07:53:38.25 spid22s index restored for tempdb.sysremsvcbinds.
2022-03-22T07:57:36.5939739Z
2022-03-22T07:57:36.5939998Z 2022-03-22 07:53:38.25 spid22s index restored for tempdb.sysrts.
2022-03-22T07:57:36.5940182Z
2022-03-22T07:57:36.5940902Z 2022-03-22 07:53:38.25 spid22s index restored for tempdb.sysasymkeys.
2022-03-22T07:57:36.5941099Z
2022-03-22T07:57:36.5941364Z 2022-03-22 07:53:38.25 spid22s index restored for tempdb.syssqlguides.
2022-03-22T07:57:36.5941562Z
2022-03-22T07:57:36.5941834Z 2022-03-22 07:53:38.25 spid22s index restored for tempdb.syssoftobjrefs.
2022-03-22T07:57:36.5942493Z
2022-03-22T07:57:36.5942776Z 2022-03-22 07:53:38.30 spid22s index restored for model.syspriorities.
2022-03-22T07:57:36.5942974Z
2022-03-22T07:57:36.5943230Z 2022-03-22 07:53:38.30 spid22s index restored for model.sysowners.
2022-03-22T07:57:36.5943416Z
2022-03-22T07:57:36.5943666Z 2022-03-22 07:53:38.31 spid22s index restored for model.sysdbreg.
2022-03-22T07:57:36.5944049Z
2022-03-22T07:57:36.5944319Z 2022-03-22 07:53:38.32 spid22s index restored for model.sysschobjs.
2022-03-22T07:57:36.5944513Z
2022-03-22T07:57:36.5944777Z 2022-03-22 07:53:38.32 spid22s index restored for model.sysextsources.
2022-03-22T07:57:36.5944982Z
2022-03-22T07:57:36.5945460Z 2022-03-22 07:53:38.32 spid22s index restored for model.sysextfileformats.
2022-03-22T07:57:36.5945668Z
2022-03-22T07:57:36.5946028Z 2022-03-22 07:53:38.32 spid22s index restored for model.syscolpars.
2022-03-22T07:57:36.5946229Z
2022-03-22T07:57:36.5946489Z 2022-03-22 07:53:38.33 spid22s index restored for model.sysxlgns.
2022-03-22T07:57:36.5946676Z
2022-03-22T07:57:36.5947132Z 2022-03-22 07:53:38.33 spid22s index restored for model.sysxsrvs.
2022-03-22T07:57:36.5947319Z
2022-03-22T07:57:36.5947568Z 2022-03-22 07:53:38.33 spid22s index restored for model.sysnsobjs.
2022-03-22T07:57:36.5947758Z
2022-03-22T07:57:36.5948012Z 2022-03-22 07:53:38.33 spid22s index restored for model.syscerts.
2022-03-22T07:57:36.5948198Z
2022-03-22T07:57:36.5948647Z 2022-03-22 07:53:38.34 spid22s index restored for model.sysrmtlgns.
2022-03-22T07:57:36.5948843Z
2022-03-22T07:57:36.5949108Z 2022-03-22 07:53:38.34 spid22s index restored for model.sysxprops.
2022-03-22T07:57:36.5949294Z
2022-03-22T07:57:36.5949564Z 2022-03-22 07:53:38.34 spid22s index restored for model.sysscalartypes.
2022-03-22T07:57:36.5949766Z
2022-03-22T07:57:36.5950242Z 2022-03-22 07:53:38.34 spid22s index restored for model.sysidxstats.
2022-03-22T07:57:36.5950450Z
2022-03-22T07:57:36.5950715Z 2022-03-22 07:53:38.34 spid22s index restored for model.sysendpts.
2022-03-22T07:57:36.5950905Z
2022-03-22T07:57:36.5951159Z 2022-03-22 07:53:38.35 spid22s index restored for model.sysclsobjs.
2022-03-22T07:57:36.5951347Z
2022-03-22T07:57:36.5951816Z 2022-03-22 07:53:38.35 spid22s index restored for model.sysremsvcbinds.
2022-03-22T07:57:36.5952023Z
2022-03-22T07:57:36.5952263Z 2022-03-22 07:53:38.35 spid22s index restored for model.sysrts.
2022-03-22T07:57:36.5952447Z
2022-03-22T07:57:36.5952707Z 2022-03-22 07:53:38.35 spid22s index restored for model.sysasymkeys.
2022-03-22T07:57:36.5952900Z
2022-03-22T07:57:36.5953163Z 2022-03-22 07:53:38.35 spid22s index restored for model.syssqlguides.
2022-03-22T07:57:36.5953354Z
2022-03-22T07:57:36.5956543Z 2022-03-22 07:53:38.35 spid22s index restored for model.syssoftobjrefs.
2022-03-22T07:57:36.5956873Z
2022-03-22T07:57:36.5957212Z 2022-03-22 07:53:38.57 spid22s index restored for msdb.syspriorities.
2022-03-22T07:57:36.5957411Z
2022-03-22T07:57:36.5957665Z 2022-03-22 07:53:38.59 spid22s index restored for msdb.sysowners.
2022-03-22T07:57:36.5958134Z
2022-03-22T07:57:36.5958397Z 2022-03-22 07:53:38.59 spid22s index restored for msdb.sysdbreg.
2022-03-22T07:57:36.5958582Z
2022-03-22T07:57:36.5958838Z 2022-03-22 07:53:38.62 spid22s index restored for msdb.sysschobjs.
2022-03-22T07:57:36.5959026Z
2022-03-22T07:57:36.5959289Z 2022-03-22 07:53:38.62 spid22s index restored for msdb.sysextsources.
2022-03-22T07:57:36.5959483Z
2022-03-22T07:57:36.5959746Z 2022-03-22 07:53:38.63 spid22s index restored for msdb.sysextfileformats.
2022-03-22T07:57:36.5960243Z
2022-03-22T07:57:36.6006611Z 2022-03-22 07:53:38.65 spid22s index restored for msdb.syscolpars.
2022-03-22T07:57:36.6006838Z
2022-03-22T07:57:36.6007117Z 2022-03-22 07:53:38.65 spid22s index restored for msdb.sysxlgns.
2022-03-22T07:57:36.6007314Z
2022-03-22T07:57:36.6007569Z 2022-03-22 07:53:38.65 spid22s index restored for msdb.sysxsrvs.
2022-03-22T07:57:36.6007938Z
2022-03-22T07:57:36.6008205Z 2022-03-22 07:53:38.66 spid22s index restored for msdb.sysnsobjs.
2022-03-22T07:57:36.6008394Z
2022-03-22T07:57:36.6009130Z 2022-03-22 07:53:38.66 spid22s index restored for msdb.syscerts.
2022-03-22T07:57:36.6009330Z
2022-03-22T07:57:36.6009616Z 2022-03-22 07:53:38.66 spid22s index restored for msdb.sysrmtlgns.
2022-03-22T07:57:36.6009807Z
2022-03-22T07:57:36.6010062Z 2022-03-22 07:53:38.66 spid22s index restored for msdb.sysxprops.
2022-03-22T07:57:36.6010251Z
2022-03-22T07:57:36.6010530Z 2022-03-22 07:53:38.66 spid22s index restored for msdb.sysscalartypes.
2022-03-22T07:57:36.6011206Z
2022-03-22T07:57:36.6011465Z 2022-03-22 07:53:38.67 spid22s index restored for msdb.sysidxstats.
2022-03-22T07:57:36.6011660Z
2022-03-22T07:57:36.6012019Z 2022-03-22 07:53:38.67 spid22s index restored for msdb.sysendpts.
2022-03-22T07:57:36.6012211Z
2022-03-22T07:57:36.6012475Z 2022-03-22 07:53:38.67 spid22s index restored for msdb.sysclsobjs.
2022-03-22T07:57:36.6012903Z
2022-03-22T07:57:36.6013255Z 2022-03-22 07:53:38.67 spid22s index restored for msdb.sysremsvcbinds.
2022-03-22T07:57:36.6013452Z
2022-03-22T07:57:36.6013703Z 2022-03-22 07:53:38.67 spid22s index restored for msdb.sysrts.
2022-03-22T07:57:36.6013885Z
2022-03-22T07:57:36.6014590Z 2022-03-22 07:53:38.68 spid22s index restored for msdb.sysasymkeys.
2022-03-22T07:57:36.6014790Z
2022-03-22T07:57:36.6015061Z 2022-03-22 07:53:38.68 spid22s index restored for msdb.syssqlguides.
2022-03-22T07:57:36.6015252Z
2022-03-22T07:57:36.6015518Z 2022-03-22 07:53:38.69 spid22s index restored for msdb.syssoftobjrefs.
2022-03-22T07:57:36.6015716Z
2022-03-22T07:57:36.6016003Z 2022-03-22 07:53:38.69 spid22s index restored for msdb.syscachedcredentials.
2022-03-22T07:57:36.6016216Z
2022-03-22T07:57:36.6016519Z 2022-03-22 07:53:38.69 spid22s index restored for msdb.syscollector_blobs_internal.
2022-03-22T07:57:36.6016723Z
2022-03-22T07:57:36.6017874Z 2022-03-22 07:53:38.70 spid22s index restored for msdb.syspolicy_system_health_state_internal.
2022-03-22T07:57:36.6018115Z
2022-03-22T07:57:36.6018475Z 2022-03-22 07:53:38.71 spid22s index restored for msdb.sysmanagement_shared_server_groups_internal.
2022-03-22T07:57:36.6018707Z
2022-03-22T07:57:36.6018977Z 2022-03-22 07:53:38.71 spid22s index restored for msdb.sysssispackages.
2022-03-22T07:57:36.6019178Z
2022-03-22T07:57:36.6019954Z 2022-03-22 07:53:38.72 spid22s index restored for msdb.sysmanagement_shared_registered_servers_internal.
2022-03-22T07:57:36.6020201Z
2022-03-22T07:57:36.6020509Z 2022-03-22 07:53:38.72 spid22s index restored for msdb.sysssispackagefolders.
2022-03-22T07:57:36.6020720Z
2022-03-22T07:57:36.6021132Z 2022-03-22 07:53:38.73 spid22s index restored for msdb.sysutility_mi_smo_properties_to_collect_internal.
2022-03-22T07:57:36.6021722Z
2022-03-22T07:57:36.6022057Z 2022-03-22 07:53:38.73 spid22s index restored for msdb.syspolicy_configuration_internal.
2022-03-22T07:57:36.6022281Z
2022-03-22T07:57:36.6022586Z 2022-03-22 07:53:38.74 spid22s index restored for msdb.log_shipping_primary_databases.
2022-03-22T07:57:36.6022802Z
2022-03-22T07:57:36.6023096Z 2022-03-22 07:53:38.75 spid22s index restored for msdb.syspolicy_management_facets.
2022-03-22T07:57:36.6023306Z
2022-03-22T07:57:36.6023589Z 2022-03-22 07:53:38.76 spid22s index restored for msdb.syspolicy_facet_events.
2022-03-22T07:57:36.6023791Z
2022-03-22T07:57:36.6024086Z 2022-03-22 07:53:38.77 spid22s index restored for msdb.syscollector_config_store_internal.
2022-03-22T07:57:36.6024756Z
2022-03-22T07:57:36.6025081Z 2022-03-22 07:53:38.77 spid22s index restored for msdb.sysutility_ucp_dac_health_internal.
2022-03-22T07:57:36.6025300Z
2022-03-22T07:57:36.6025568Z 2022-03-22 07:53:38.77 spid22s index restored for msdb.sysmail_profile.
2022-03-22T07:57:36.6025767Z
2022-03-22T07:57:36.6026013Z 2022-03-22 07:53:38.77 spid22s index restored for msdb.MSdbms.
2022-03-22T07:57:36.6026615Z
2022-03-22T07:57:36.6027160Z 2022-03-22 07:53:38.78 spid22s index restored for msdb.log_shipping_primary_secondaries.
2022-03-22T07:57:36.6027374Z
2022-03-22T07:57:36.6027681Z 2022-03-22 07:53:38.79 spid22s index restored for msdb.syspolicy_conditions_internal.
2022-03-22T07:57:36.6027895Z
2022-03-22T07:57:36.6028160Z 2022-03-22 07:53:38.80 spid22s index restored for msdb.MSdbms_datatype.
2022-03-22T07:57:36.6028355Z
2022-03-22T07:57:36.6029045Z 2022-03-22 07:53:38.80 spid22s index restored for msdb.log_shipping_monitor_primary.
2022-03-22T07:57:36.6029258Z
2022-03-22T07:57:36.6029589Z 2022-03-22 07:53:38.80 spid22s index restored for msdb.log_shipping_monitor_history_detail.
2022-03-22T07:57:36.6029804Z
2022-03-22T07:57:36.6030304Z 2022-03-22 07:53:38.81 spid22s index restored for msdb.log_shipping_monitor_error_detail.
2022-03-22T07:57:36.6030888Z
2022-03-22T07:57:36.6031198Z 2022-03-22 07:53:38.81 spid22s index restored for msdb.log_shipping_secondary.
2022-03-22T07:57:36.6031393Z
2022-03-22T07:57:36.6031949Z 2022-03-22 07:53:38.81 spid22s index restored for msdb.log_shipping_secondary_databases.
2022-03-22T07:57:36.6032911Z
2022-03-22T07:57:36.6033794Z 2022-03-22 07:53:38.81 spid22s index restored for msdb.sysutility_ucp_managed_instances_internal.
2022-03-22T07:57:36.6034028Z
2022-03-22T07:57:36.6034560Z 2022-03-22 07:53:38.82 spid22s index restored for msdb.log_shipping_monitor_secondary.
2022-03-22T07:57:36.6034771Z
2022-03-22T07:57:36.6035041Z 2022-03-22 07:53:38.82 spid22s index restored for msdb.sysmail_account.
2022-03-22T07:57:36.6035915Z
2022-03-22T07:57:36.6036442Z 2022-03-22 07:53:38.83 spid22s index restored for msdb.sysutility_ucp_mi_health_internal.
2022-03-22T07:57:36.6036659Z
2022-03-22T07:57:36.6037355Z 2022-03-22 07:53:38.83 spid22s index restored for msdb.sysdac_instances_internal.
2022-03-22T07:57:36.6037563Z
2022-03-22T07:57:36.6037885Z 2022-03-22 07:53:38.84 spid22s index restored for msdb.syscollector_collection_sets_internal.
2022-03-22T07:57:36.6038103Z
2022-03-22T07:57:36.6039320Z 2022-03-22 07:53:38.84 spid22s index restored for msdb.syspolicy_policy_categories_internal.
2022-03-22T07:57:36.6039554Z
2022-03-22T07:57:36.6039863Z 2022-03-22 07:53:38.84 spid22s index restored for msdb.sysdac_history_internal.
2022-03-22T07:57:36.6040075Z
2022-03-22T07:57:36.6040349Z 2022-03-22 07:53:38.85 spid22s index restored for msdb.sysmail_servertype.
2022-03-22T07:57:36.6040775Z
2022-03-22T07:57:36.6041278Z 2022-03-22 07:53:38.85 spid22s index restored for msdb.syspolicy_object_sets_internal.
2022-03-22T07:57:36.6067599Z
2022-03-22T07:57:36.6068702Z 2022-03-22 07:53:38.86 spid22s index restored for msdb.sysutility_ucp_health_policies_internal.
2022-03-22T07:57:36.6068959Z
2022-03-22T07:57:36.6069243Z 2022-03-22 07:53:38.86 spid22s index restored for msdb.sysmail_server.
2022-03-22T07:57:36.6069449Z
2022-03-22T07:57:36.6069827Z 2022-03-22 07:53:38.86 spid22s index restored for msdb.sysutility_ucp_filegroups_with_policy_violations_internal.
2022-03-22T07:57:36.6070081Z
2022-03-22T07:57:36.6071211Z 2022-03-22 07:53:38.87 spid22s index restored for msdb.sysutility_ucp_policy_check_conditions_internal.
2022-03-22T07:57:36.6071455Z
2022-03-22T07:57:36.6071791Z 2022-03-22 07:53:38.87 spid22s index restored for msdb.syscollector_collector_types_internal.
2022-03-22T07:57:36.6072020Z
2022-03-22T07:57:36.6072318Z 2022-03-22 07:53:38.88 spid22s index restored for msdb.syspolicy_policies_internal.
2022-03-22T07:57:36.6072531Z
2022-03-22T07:57:36.6073448Z 2022-03-22 07:53:38.89 spid22s index restored for msdb.sysutility_ucp_policy_target_conditions_internal.
2022-03-22T07:57:36.6073697Z
2022-03-22T07:57:36.6074008Z 2022-03-22 07:53:38.89 spid22s index restored for msdb.sysmail_configuration.
2022-03-22T07:57:36.6074222Z
2022-03-22T07:57:36.6074523Z 2022-03-22 07:53:38.89 spid22s index restored for msdb.external_libraries_installed.
2022-03-22T07:57:36.6075329Z
2022-03-22T07:57:36.6075654Z 2022-03-22 07:53:38.90 spid22s index restored for msdb.sysdbmaintplan_databases.
2022-03-22T07:57:36.6075864Z
2022-03-22T07:57:36.6076708Z 2022-03-22 07:53:38.90 spid22s index restored for msdb.sysutility_ucp_configuration_internal.
2022-03-22T07:57:36.6076945Z
2022-03-22T07:57:36.6077698Z 2022-03-22 07:53:38.90 spid22s index restored for msdb.sysproxies.
2022-03-22T07:57:36.6077890Z
2022-03-22T07:57:36.6078165Z 2022-03-22 07:53:38.91 spid22s index restored for msdb.syssubsystems.
2022-03-22T07:57:36.6078814Z
2022-03-22T07:57:36.6079153Z 2022-03-22 07:53:38.91 spid22s index restored for msdb.syscollector_collection_items_internal.
2022-03-22T07:57:36.6079366Z
2022-03-22T07:57:36.6079641Z 2022-03-22 07:53:38.92 spid22s index restored for msdb.sysdownloadlist.
2022-03-22T07:57:36.6079844Z
2022-03-22T07:57:36.6081277Z 2022-03-22 07:53:38.92 spid22s index restored for msdb.sysoriginatingservers.
2022-03-22T07:57:36.6081790Z
2022-03-22T07:57:36.6082125Z 2022-03-22 07:53:38.93 spid22s index restored for msdb.autoadmin_managed_databases.
2022-03-22T07:57:36.6082337Z
2022-03-22T07:57:36.6082952Z 2022-03-22 07:53:38.93 spid22s index restored for msdb.sysjobs.
2022-03-22T07:57:36.6083146Z
2022-03-22T07:57:36.6084021Z 2022-03-22 07:53:38.93 spid22s index restored for msdb.smart_backup_files.
2022-03-22T07:57:36.6084418Z
2022-03-22T07:57:36.6084701Z 2022-03-22 07:53:38.94 spid22s index restored for msdb.backupset.
2022-03-22T07:57:36.6084891Z
2022-03-22T07:57:36.6085151Z 2022-03-22 07:53:38.94 spid22s index restored for msdb.sysjobsteps.
2022-03-22T07:57:36.6085342Z
2022-03-22T07:57:36.6087110Z 2022-03-22 07:53:38.94 spid22s index restored for msdb.syscollector_execution_stats_internal.
2022-03-22T07:57:36.6087361Z
2022-03-22T07:57:36.6087739Z 2022-03-22 07:53:38.95 spid22s index restored for msdb.sysutility_ucp_mi_file_space_health_internal.
2022-03-22T07:57:36.6087976Z
2022-03-22T07:57:36.6088666Z 2022-03-22 07:53:38.95 spid22s index restored for msdb.syspolicy_target_sets_internal.
2022-03-22T07:57:36.6088879Z
2022-03-22T07:57:36.6089153Z 2022-03-22 07:53:38.96 spid22s index restored for msdb.sysschedules.
2022-03-22T07:57:36.6089350Z
2022-03-22T07:57:36.6089680Z 2022-03-22 07:53:38.96 spid22s index restored for msdb.sysutility_ucp_mi_database_health_internal.
2022-03-22T07:57:36.6089904Z
2022-03-22T07:57:36.6090172Z 2022-03-22 07:53:38.96 spid22s index restored for msdb.logmarkhistory.
2022-03-22T07:57:36.6090569Z
2022-03-22T07:57:36.6091330Z 2022-03-22 07:53:38.97 spid22s index restored for msdb.sysutility_ucp_dac_file_space_health_internal.
2022-03-22T07:57:36.6092152Z
2022-03-22T07:57:36.6092443Z 2022-03-22 07:53:38.98 spid22s index restored for msdb.syscategories.
2022-03-22T07:57:36.6092639Z
2022-03-22T07:57:36.6093193Z 2022-03-22 07:53:38.98 spid22s index restored for msdb.systargetservers.
2022-03-22T07:57:36.6093698Z
2022-03-22T07:57:36.6094061Z 2022-03-22 07:53:38.99 spid22s index restored for msdb.sysutility_ucp_mi_volume_space_health_internal.
2022-03-22T07:57:36.6094526Z
2022-03-22T07:57:36.6094879Z 2022-03-22 07:53:38.99 spid22s index restored for msdb.sysutility_mi_dac_execution_statistics_internal.
2022-03-22T07:57:36.6095115Z
2022-03-22T07:57:36.6095409Z 2022-03-22 07:53:38.99 spid22s index restored for msdb.systargetservergroups.
2022-03-22T07:57:36.6095625Z
2022-03-22T07:57:36.6096552Z 2022-03-22 07:53:38.99 spid22s index restored for msdb.syspolicy_policy_category_subscriptions_internal.
2022-03-22T07:57:36.6096797Z
2022-03-22T07:57:36.6097048Z 2022-03-22 07:53:39.00 spid22s index restored for msdb.sysalerts.
2022-03-22T07:57:36.6097241Z
2022-03-22T07:57:36.6097574Z 2022-03-22 07:53:39.00 spid22s index restored for msdb.sysutility_ucp_computer_cpu_health_internal.
2022-03-22T07:57:36.6097808Z
2022-03-22T07:57:36.6098133Z 2022-03-22 07:53:39.00 spid22s index restored for msdb.sysutility_mi_session_statistics_internal.
2022-03-22T07:57:36.6098506Z
2022-03-22T07:57:36.6098771Z 2022-03-22 07:53:39.01 spid22s index restored for msdb.sysoperators.
2022-03-22T07:57:36.6098966Z
2022-03-22T07:57:36.6099712Z 2022-03-22 07:53:39.03 spid22s The default collation was successfully changed.
```
</p>
</details>
https://github.com/trinodb/trino/runs/5640191532?check_suite_focus=true
|
1.0
|
Flaky TestingSqlServer initialization due to log message wait strategy - The expected message "The default collation was successfully changed." was logged, but `LogMessageWaitStrategy` seems failing:
```
2022-03-22T07:57:36.5495854Z org.testcontainers.containers.ContainerLaunchException: Timed out waiting for log output matching '.*The default collation was successfully changed.*'
2022-03-22T07:57:36.5497129Z at org.testcontainers.containers.wait.strategy.LogMessageWaitStrategy.waitUntilReady(LogMessageWaitStrategy.java:49)
2022-03-22T07:57:36.5498130Z at org.testcontainers.containers.wait.strategy.AbstractWaitStrategy.waitUntilReady(AbstractWaitStrategy.java:51)
2022-03-22T07:57:36.5499151Z at io.trino.plugin.sqlserver.TestingSqlServer$1TestingMSSQLServerContainer.waitUntilContainerStarted(TestingSqlServer.java:120)
2022-03-22T07:57:36.5500204Z at org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:468)
2022-03-22T07:57:36.5503025Z at org.testcontainers.containers.GenericContainer.lambda$doStart$0(GenericContainer.java:331)
2022-03-22T07:57:36.5503817Z at org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:81)
2022-03-22T07:57:36.5505293Z at org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:329)
2022-03-22T07:57:36.5505993Z at org.testcontainers.containers.GenericContainer.start(GenericContainer.java:317)
2022-03-22T07:57:36.5506739Z at io.trino.testing.containers.TestContainers.startOrReuse(TestContainers.java:42)
2022-03-22T07:57:36.5507443Z at io.trino.plugin.sqlserver.TestingSqlServer.createContainer(TestingSqlServer.java:142)
2022-03-22T07:57:36.5508103Z at io.trino.plugin.sqlserver.TestingSqlServer.lambda$new$3(TestingSqlServer.java:90)
2022-03-22T07:57:36.5508682Z at net.jodah.failsafe.Functions.lambda$get$0(Functions.java:48)
2022-03-22T07:57:36.5555607Z at net.jodah.failsafe.TimeoutExecutor.lambda$supply$2(TimeoutExecutor.java:91)
2022-03-22T07:57:36.5643602Z at net.jodah.failsafe.RetryPolicyExecutor.lambda$supply$0(RetryPolicyExecutor.java:62)
2022-03-22T07:57:36.5644138Z at net.jodah.failsafe.Execution.executeSync(Execution.java:129)
2022-03-22T07:57:36.5644600Z at net.jodah.failsafe.FailsafeExecutor.call(FailsafeExecutor.java:376)
2022-03-22T07:57:36.5646940Z at net.jodah.failsafe.FailsafeExecutor.get(FailsafeExecutor.java:67)
2022-03-22T07:57:36.5647426Z at io.trino.plugin.sqlserver.TestingSqlServer.<init>(TestingSqlServer.java:90)
2022-03-22T07:57:36.5647998Z at io.trino.plugin.sqlserver.TestingSqlServer.<init>(TestingSqlServer.java:84)
2022-03-22T07:57:36.5653802Z at io.trino.plugin.sqlserver.BaseSqlServerTransactionIsolationTest.createQueryRunner(BaseSqlServerTransactionIsolationTest.java:37)
2022-03-22T07:57:36.5654811Z at io.trino.testing.AbstractTestQueryFramework.init(AbstractTestQueryFramework.java:94)
2022-03-22T07:57:36.5655373Z at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2022-03-22T07:57:36.5655969Z at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
2022-03-22T07:57:36.5656991Z at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
2022-03-22T07:57:36.5657525Z at java.base/java.lang.reflect.Method.invoke(Method.java:566)
2022-03-22T07:57:36.5658035Z at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:104)
2022-03-22T07:57:36.5658694Z at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:515)
2022-03-22T07:57:36.5659195Z at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:217)
2022-03-22T07:57:36.5659672Z at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:144)
2022-03-22T07:57:36.5660226Z at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:169)
2022-03-22T07:57:36.5660877Z at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108)
2022-03-22T07:57:36.5661502Z at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
2022-03-22T07:57:36.5662179Z at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
2022-03-22T07:57:36.5662600Z at java.base/java.lang.Thread.run(Thread.java:829)
2022-03-22T07:57:36.5662791Z
2022-03-22T07:57:36.5662799Z
2022-03-22T07:57:36.5664006Z 2022-03-22T01:57:36.500-0600 INFO dispatcher-query-80 io.trino.event.QueryMonitor TIMELINE: Query 20220322_075736_00846_vjzbw :: Transaction:[ae138008-3e50-4f1d-9d47-621245fcbed0] :: elapsed 242ms :: planning 43ms :: waiting 93ms :: scheduling 108ms :: running 74ms :: finishing 17ms :: begin 2022-03-22T01:57:36.243-06:00 :: end 2022-03-22T01:57:36.485-06:00
```
<details><summary>open</summary>
<p>
```
2022-03-22T07:57:36.5665015Z 2022-03-22T01:57:36.518-0600 ERROR pool-4-thread-2 🐳 [mcr.microsoft.com/mssql/server:2017-CU13] Log output from the failed container:
2022-03-22T07:57:36.5665793Z 2022-03-22 07:53:32.13 Server Setup step is copying system data file 'C:\templatedata\master.mdf' to '/var/opt/mssql/data/master.mdf'.
2022-03-22T07:57:36.5666079Z
2022-03-22T07:57:36.5666958Z 2022-03-22 07:53:32.22 Server Did not find an existing master data file /var/opt/mssql/data/master.mdf, copying the missing default master and other system database files. If you have moved the database location, but not moved the database files, startup may fail. To repair: shutdown SQL Server, move the master database to configured location, and restart.
2022-03-22T07:57:36.5667573Z
2022-03-22T07:57:36.5667997Z 2022-03-22 07:53:32.22 Server Setup step is copying system data file 'C:\templatedata\mastlog.ldf' to '/var/opt/mssql/data/mastlog.ldf'.
2022-03-22T07:57:36.5668276Z
2022-03-22T07:57:36.5668663Z 2022-03-22 07:53:32.23 Server Setup step is copying system data file 'C:\templatedata\model.mdf' to '/var/opt/mssql/data/model.mdf'.
2022-03-22T07:57:36.5669022Z
2022-03-22T07:57:36.5669453Z 2022-03-22 07:53:32.24 Server Setup step is copying system data file 'C:\templatedata\modellog.ldf' to '/var/opt/mssql/data/modellog.ldf'.
2022-03-22T07:57:36.5669733Z
2022-03-22T07:57:36.5670145Z 2022-03-22 07:53:32.26 Server Setup step is copying system data file 'C:\templatedata\msdbdata.mdf' to '/var/opt/mssql/data/msdbdata.mdf'.
2022-03-22T07:57:36.5670511Z
2022-03-22T07:57:36.5670930Z 2022-03-22 07:53:32.28 Server Setup step is copying system data file 'C:\templatedata\msdblog.ldf' to '/var/opt/mssql/data/msdblog.ldf'.
2022-03-22T07:57:36.5671202Z
2022-03-22T07:57:36.5671614Z 2022-03-22 07:53:32.38 Server Microsoft SQL Server 2017 (RTM-CU13) (KB4466404) - 14.0.3048.4 (X64)
2022-03-22T07:57:36.5671831Z
2022-03-22T07:57:36.5671930Z Nov 30 2018 12:57:58
2022-03-22T07:57:36.5672062Z
2022-03-22T07:57:36.5672202Z Copyright (C) 2017 Microsoft Corporation
2022-03-22T07:57:36.5672372Z
2022-03-22T07:57:36.5672613Z Developer Edition (64-bit) on Linux (Ubuntu 16.04.5 LTS)
2022-03-22T07:57:36.5672796Z
2022-03-22T07:57:36.5673106Z 2022-03-22 07:53:32.39 Server UTC adjustment: 0:00
2022-03-22T07:57:36.5673370Z
2022-03-22T07:57:36.5673614Z 2022-03-22 07:53:32.39 Server (c) Microsoft Corporation.
2022-03-22T07:57:36.5673790Z
2022-03-22T07:57:36.5674010Z 2022-03-22 07:53:32.39 Server All rights reserved.
2022-03-22T07:57:36.5674166Z
2022-03-22T07:57:36.5674399Z 2022-03-22 07:53:32.39 Server Server process ID is 4124.
2022-03-22T07:57:36.5674571Z
2022-03-22T07:57:36.5674989Z 2022-03-22 07:53:32.40 Server Logging SQL Server messages in file '/var/opt/mssql/log/errorlog'.
2022-03-22T07:57:36.5675216Z
2022-03-22T07:57:36.5675464Z 2022-03-22 07:53:32.40 Server Registry startup parameters:
2022-03-22T07:57:36.5675648Z
2022-03-22T07:57:36.5675839Z -d /var/opt/mssql/data/master.mdf
2022-03-22T07:57:36.5815627Z
2022-03-22T07:57:36.5816092Z -l /var/opt/mssql/data/mastlog.ldf
2022-03-22T07:57:36.5816289Z
2022-03-22T07:57:36.5816470Z -e /var/opt/mssql/log/errorlog
2022-03-22T07:57:36.5816628Z
2022-03-22T07:57:36.5817607Z 2022-03-22 07:53:32.40 Server SQL Server detected 1 sockets with 2 cores per socket and 2 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2022-03-22T07:57:36.5818056Z
2022-03-22T07:57:36.5818508Z 2022-03-22 07:53:32.41 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2022-03-22T07:57:36.5818788Z
2022-03-22T07:57:36.5853614Z 2022-03-22 07:53:32.41 Server Detected 5558 MB of RAM. This is an informational message; no user action is required.
2022-03-22T07:57:36.5855204Z
2022-03-22T07:57:36.5855564Z 2022-03-22 07:53:32.42 Server Using conventional memory in the memory manager.
2022-03-22T07:57:36.5855786Z
2022-03-22T07:57:36.5856365Z 2022-03-22 07:53:32.44 Server Machine supports memory error recovery. SQL memory protection is enabled to recover from memory corruption.
2022-03-22T07:57:36.5856660Z
2022-03-22T07:57:36.5856993Z 2022-03-22 07:53:32.66 Server Buffer pool extension is already disabled. No action is necessary.
2022-03-22T07:57:36.5857232Z
2022-03-22T07:57:36.5857617Z 2022-03-22 07:53:32.83 Server InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
2022-03-22T07:57:36.5857884Z
2022-03-22T07:57:36.5860478Z 2022-03-22 07:53:32.84 Server Implied authentication manager initialization failed. Implied authentication will be disabled.
2022-03-22T07:57:36.5860755Z
2022-03-22T07:57:36.5862695Z 2022-03-22 07:53:32.84 Server Successfully initialized the TLS configuration. Allowed TLS protocol versions are ['1.0 1.1 1.2']. Allowed TLS ciphers are ['ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:!DHE-RSA-AES256-GCM-SHA384:!DHE-RSA-AES128-GCM-SHA256:!DHE-RSA-AES256-SHA:!DHE-RSA-AES128-SHA'].
2022-03-22T07:57:36.5865359Z
2022-03-22T07:57:36.5865749Z 2022-03-22 07:53:32.90 Server The maximum number of dedicated administrator connections for this instance is '1'
2022-03-22T07:57:36.5866235Z
2022-03-22T07:57:36.5866955Z 2022-03-22 07:53:32.90 Server Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2022-03-22T07:57:36.5867372Z
2022-03-22T07:57:36.5868129Z 2022-03-22 07:53:32.92 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2022-03-22T07:57:36.5868480Z
2022-03-22T07:57:36.5868762Z 2022-03-22 07:53:32.95 Server In-Memory OLTP initialized on lowend machine.
2022-03-22T07:57:36.5868979Z
2022-03-22T07:57:36.5871513Z 2022-03-22 07:53:33.06 Server Database Instant File Initialization: enabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
2022-03-22T07:57:36.5871965Z
2022-03-22T07:57:36.5872113Z ForceFlush is enabled for this instance.
2022-03-22T07:57:36.5872523Z
2022-03-22T07:57:36.5872876Z 2022-03-22 07:53:33.07 Server Query Store settings initialized with enabled = 1,
2022-03-22T07:57:36.5873091Z
2022-03-22T07:57:36.5873615Z 2022-03-22 07:53:33.09 Server Software Usage Metrics is disabled.
2022-03-22T07:57:36.5874546Z
2022-03-22T07:57:36.5874829Z 2022-03-22 07:53:33.10 spid6s Starting up database 'master'.
2022-03-22T07:57:36.5875016Z
2022-03-22T07:57:36.5875208Z ForceFlush feature is enabled for log durability.
2022-03-22T07:57:36.5875393Z
2022-03-22T07:57:36.5876355Z 2022-03-22 07:53:33.56 spid6s The tail of the log for database master is being rewritten to match the new sector size of 4096 bytes. 3072 bytes at offset 418816 in file /var/opt/mssql/data/mastlog.ldf will be written.
2022-03-22T07:57:36.5876995Z
2022-03-22T07:57:36.5877359Z 2022-03-22 07:53:33.90 spid6s Converting database 'master' from version 862 to the current version 869.
2022-03-22T07:57:36.5877590Z
2022-03-22T07:57:36.5877941Z 2022-03-22 07:53:33.91 spid6s Database 'master' running the upgrade step from version 862 to version 863.
2022-03-22T07:57:36.5878173Z
2022-03-22T07:57:36.5878508Z 2022-03-22 07:53:33.92 spid6s Database 'master' running the upgrade step from version 863 to version 864.
2022-03-22T07:57:36.5878735Z
2022-03-22T07:57:36.5879305Z 2022-03-22 07:53:33.94 spid6s Database 'master' running the upgrade step from version 864 to version 865.
2022-03-22T07:57:36.5879538Z
2022-03-22T07:57:36.5879867Z 2022-03-22 07:53:33.95 spid6s Database 'master' running the upgrade step from version 865 to version 866.
2022-03-22T07:57:36.5880094Z
2022-03-22T07:57:36.5880430Z 2022-03-22 07:53:33.96 spid6s Database 'master' running the upgrade step from version 866 to version 867.
2022-03-22T07:57:36.5880660Z
2022-03-22T07:57:36.5880994Z 2022-03-22 07:53:33.97 spid6s Database 'master' running the upgrade step from version 867 to version 868.
2022-03-22T07:57:36.5881225Z
2022-03-22T07:57:36.5881761Z 2022-03-22 07:53:33.99 spid6s Database 'master' running the upgrade step from version 868 to version 869.
2022-03-22T07:57:36.5881992Z
2022-03-22T07:57:36.5882282Z 2022-03-22 07:53:34.38 spid6s Resource governor reconfiguration succeeded.
2022-03-22T07:57:36.5882490Z
2022-03-22T07:57:36.5883201Z 2022-03-22 07:53:34.38 spid6s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2022-03-22T07:57:36.5883811Z
2022-03-22T07:57:36.5885174Z 2022-03-22 07:53:34.39 spid6s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2022-03-22T07:57:36.5885450Z
2022-03-22T07:57:36.5885734Z 2022-03-22 07:53:34.47 spid6s SQL Trace ID 1 was started by login "sa".
2022-03-22T07:57:36.5885929Z
2022-03-22T07:57:36.5886630Z 2022-03-22 07:53:34.50 spid6s Server name is '4fd4a1f8c943'. This is an informational message only. No user action is required.
2022-03-22T07:57:36.5887266Z
2022-03-22T07:57:36.5887561Z 2022-03-22 07:53:34.50 spid19s Password policy update was successful.
2022-03-22T07:57:36.5887763Z
2022-03-22T07:57:36.5888004Z 2022-03-22 07:53:34.54 spid6s Starting up database 'msdb'.
2022-03-22T07:57:36.5888181Z
2022-03-22T07:57:36.5888881Z 2022-03-22 07:53:34.54 spid22s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
2022-03-22T07:57:36.5889181Z
2022-03-22T07:57:36.5889464Z 2022-03-22 07:53:34.55 spid9s Starting up database 'mssqlsystemresource'.
2022-03-22T07:57:36.5889671Z
2022-03-22T07:57:36.5890848Z 2022-03-22 07:53:34.55 spid22s Always On: The availability replica manager is waiting for the instance of SQL Server to allow client connections. This is an informational message only. No user action is required.
2022-03-22T07:57:36.5891379Z
2022-03-22T07:57:36.5891842Z 2022-03-22 07:53:34.57 spid9s The resource database build version is 14.00.3048. This is an informational message only. No user action is required.
2022-03-22T07:57:36.5892109Z
2022-03-22T07:57:36.5892349Z 2022-03-22 07:53:34.64 spid9s Starting up database 'model'.
2022-03-22T07:57:36.5892531Z
2022-03-22T07:57:36.5892870Z 2022-03-22 07:53:35.22 spid19s A self-generated certificate was successfully loaded for encryption.
2022-03-22T07:57:36.5893141Z
2022-03-22T07:57:36.5893642Z 2022-03-22 07:53:35.24 spid19s Server is listening on [ 'any' <ipv4> 1433].
2022-03-22T07:57:36.5893843Z
2022-03-22T07:57:36.5894129Z 2022-03-22 07:53:35.25 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2022-03-22T07:57:36.5894405Z
2022-03-22T07:57:36.5894986Z 2022-03-22 07:53:35.25 spid9s The tail of the log for database model is being rewritten to match the new sector size of 4096 bytes. 2048 bytes at offset 75776 in file /var/opt/mssql/data/modellog.ldf will be written.
2022-03-22T07:57:36.5895325Z
2022-03-22T07:57:36.5895995Z 2022-03-22 07:53:35.25 Server Dedicated admin connection support was established for listening locally on port 1434.
2022-03-22T07:57:36.5896253Z
2022-03-22T07:57:36.5896824Z 2022-03-22 07:53:35.25 spid6s The tail of the log for database msdb is being rewritten to match the new sector size of 4096 bytes. 512 bytes at offset 306688 in file /var/opt/mssql/data/MSDBLog.ldf will be written.
2022-03-22T07:57:36.5897152Z
2022-03-22T07:57:36.5897491Z 2022-03-22 07:53:35.28 spid9s Converting database 'model' from version 862 to the current version 869.
2022-03-22T07:57:36.5897717Z
2022-03-22T07:57:36.5898060Z 2022-03-22 07:53:35.28 spid9s Database 'model' running the upgrade step from version 862 to version 863.
2022-03-22T07:57:36.5898293Z
2022-03-22T07:57:36.5899033Z 2022-03-22 07:53:35.28 spid6s Converting database 'msdb' from version 862 to the current version 869.
2022-03-22T07:57:36.5899262Z
2022-03-22T07:57:36.5899601Z 2022-03-22 07:53:35.29 spid6s Database 'msdb' running the upgrade step from version 862 to version 863.
2022-03-22T07:57:36.5899832Z
2022-03-22T07:57:36.5900169Z 2022-03-22 07:53:35.30 spid9s Database 'model' running the upgrade step from version 863 to version 864.
2022-03-22T07:57:36.5900393Z
2022-03-22T07:57:36.5900796Z 2022-03-22 07:53:35.32 spid19s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2022-03-22T07:57:36.5901271Z
2022-03-22T07:57:36.5901619Z 2022-03-22 07:53:35.33 spid6s Database 'msdb' running the upgrade step from version 863 to version 864.
2022-03-22T07:57:36.5901847Z
2022-03-22T07:57:36.5902389Z 2022-03-22 07:53:35.33 spid9s Database 'model' running the upgrade step from version 864 to version 865.
2022-03-22T07:57:36.5902630Z
2022-03-22T07:57:36.5902976Z 2022-03-22 07:53:35.34 spid9s Database 'model' running the upgrade step from version 865 to version 866.
2022-03-22T07:57:36.5903200Z
2022-03-22T07:57:36.5903528Z 2022-03-22 07:53:35.34 spid9s Database 'model' running the upgrade step from version 866 to version 867.
2022-03-22T07:57:36.5903946Z
2022-03-22T07:57:36.5904290Z 2022-03-22 07:53:35.34 spid6s Database 'msdb' running the upgrade step from version 864 to version 865.
2022-03-22T07:57:36.5904516Z
2022-03-22T07:57:36.5904851Z 2022-03-22 07:53:35.34 spid9s Database 'model' running the upgrade step from version 867 to version 868.
2022-03-22T07:57:36.5905074Z
2022-03-22T07:57:36.5905621Z 2022-03-22 07:53:35.35 spid6s Database 'msdb' running the upgrade step from version 865 to version 866.
2022-03-22T07:57:36.5905843Z
2022-03-22T07:57:36.5906181Z 2022-03-22 07:53:35.35 spid6s Database 'msdb' running the upgrade step from version 866 to version 867.
2022-03-22T07:57:36.5906547Z
2022-03-22T07:57:36.5906882Z 2022-03-22 07:53:35.36 spid9s Database 'model' running the upgrade step from version 868 to version 869.
2022-03-22T07:57:36.5907303Z
2022-03-22T07:57:36.5907642Z 2022-03-22 07:53:35.36 spid6s Database 'msdb' running the upgrade step from version 867 to version 868.
2022-03-22T07:57:36.5907862Z
2022-03-22T07:57:36.5908192Z 2022-03-22 07:53:35.37 spid6s Database 'msdb' running the upgrade step from version 868 to version 869.
2022-03-22T07:57:36.5908421Z
2022-03-22T07:57:36.5908642Z 2022-03-22 07:53:35.47 spid9s Polybase feature disabled.
2022-03-22T07:57:36.5908820Z
2022-03-22T07:57:36.5909283Z 2022-03-22 07:53:35.48 spid9s Clearing tempdb database.
2022-03-22T07:57:36.5909462Z
2022-03-22T07:57:36.5909711Z 2022-03-22 07:53:36.09 spid9s Starting up database 'tempdb'.
2022-03-22T07:57:36.5909892Z
2022-03-22T07:57:36.5910233Z 2022-03-22 07:53:36.35 spid9s The tempdb database has 1 data file(s).
2022-03-22T07:57:36.5910431Z
2022-03-22T07:57:36.5911069Z 2022-03-22 07:53:36.35 spid24s The Service Broker endpoint is in disabled or stopped state.
2022-03-22T07:57:36.5911300Z
2022-03-22T07:57:36.5911632Z 2022-03-22 07:53:36.35 spid24s The Database Mirroring endpoint is in disabled or stopped state.
2022-03-22T07:57:36.5911851Z
2022-03-22T07:57:36.5912102Z 2022-03-22 07:53:36.37 spid24s Service Broker manager has started.
2022-03-22T07:57:36.5912287Z
2022-03-22T07:57:36.5912887Z 2022-03-22 07:53:36.45 spid6s Recovery is complete. This is an informational message only. No user action is required.
2022-03-22T07:57:36.5913140Z
2022-03-22T07:57:36.5913493Z 2022-03-22 07:53:36.49 spid22s The default language (LCID 0) has been set for engine and full-text services.
2022-03-22T07:57:36.5913722Z
2022-03-22T07:57:36.5913944Z 2022-03-22 07:53:36.51 spid22s Warning ******************
2022-03-22T07:57:36.5914111Z
2022-03-22T07:57:36.5914419Z 2022-03-22 07:53:36.51 spid22s Attempting to change default collation to Latin1_General_CS_AS.
2022-03-22T07:57:36.5914852Z
2022-03-22T07:57:36.5915139Z 2022-03-22 07:53:36.58 spid22s index restored for master.syspriorities.
2022-03-22T07:57:36.5915341Z
2022-03-22T07:57:36.5915605Z 2022-03-22 07:53:38.10 spid22s index restored for master.sysbrickfiles.
2022-03-22T07:57:36.5915806Z
2022-03-22T07:57:36.5916634Z 2022-03-22 07:53:38.10 spid22s index restored for master.sysowners.
2022-03-22T07:57:36.5916853Z
2022-03-22T07:57:36.5917148Z 2022-03-22 07:53:38.10 spid22s index restored for master.sysdbreg.
2022-03-22T07:57:36.5917333Z
2022-03-22T07:57:36.5917596Z 2022-03-22 07:53:38.11 spid22s index restored for master.sysschobjs.
2022-03-22T07:57:36.5918014Z
2022-03-22T07:57:36.5918303Z 2022-03-22 07:53:38.11 spid22s index restored for master.sysextsources.
2022-03-22T07:57:36.5918504Z
2022-03-22T07:57:36.5918799Z 2022-03-22 07:53:38.12 spid22s index restored for master.sysextfileformats.
2022-03-22T07:57:36.5919006Z
2022-03-22T07:57:36.5919466Z 2022-03-22 07:53:38.12 spid22s index restored for master.syscolpars.
2022-03-22T07:57:36.5919662Z
2022-03-22T07:57:36.5919923Z 2022-03-22 07:53:38.12 spid22s index restored for master.sysxlgns.
2022-03-22T07:57:36.5920100Z
2022-03-22T07:57:36.5920356Z 2022-03-22 07:53:38.12 spid22s index restored for master.sysxsrvs.
2022-03-22T07:57:36.5920750Z
2022-03-22T07:57:36.5921017Z 2022-03-22 07:53:38.13 spid22s index restored for master.sysnsobjs.
2022-03-22T07:57:36.5921210Z
2022-03-22T07:57:36.5921463Z 2022-03-22 07:53:38.13 spid22s index restored for master.syscerts.
2022-03-22T07:57:36.5921648Z
2022-03-22T07:57:36.5921902Z 2022-03-22 07:53:38.13 spid22s index restored for master.sysrmtlgns.
2022-03-22T07:57:36.5922091Z
2022-03-22T07:57:36.5922349Z 2022-03-22 07:53:38.13 spid22s index restored for master.sysxprops.
2022-03-22T07:57:36.5922537Z
2022-03-22T07:57:36.5923183Z 2022-03-22 07:53:38.13 spid22s index restored for master.sysscalartypes.
2022-03-22T07:57:36.5923815Z
2022-03-22T07:57:36.5924111Z 2022-03-22 07:53:38.13 spid22s index restored for master.sysidxstats.
2022-03-22T07:57:36.5924308Z
2022-03-22T07:57:36.5924914Z 2022-03-22 07:53:38.13 spid22s index restored for master.sysendpts.
2022-03-22T07:57:36.5925110Z
2022-03-22T07:57:36.5925381Z 2022-03-22 07:53:38.13 spid22s index restored for master.sysclsobjs.
2022-03-22T07:57:36.5925561Z
2022-03-22T07:57:36.5925837Z 2022-03-22 07:53:38.14 spid22s index restored for master.sysremsvcbinds.
2022-03-22T07:57:36.5926037Z
2022-03-22T07:57:36.5926336Z 2022-03-22 07:53:38.14 spid22s index restored for master.sysrts.
2022-03-22T07:57:36.5926769Z
2022-03-22T07:57:36.5927045Z 2022-03-22 07:53:38.14 spid22s index restored for master.sysasymkeys.
2022-03-22T07:57:36.5927242Z
2022-03-22T07:57:36.5927510Z 2022-03-22 07:53:38.14 spid22s index restored for master.syssqlguides.
2022-03-22T07:57:36.5927705Z
2022-03-22T07:57:36.5928075Z 2022-03-22 07:53:38.14 spid22s index restored for master.syssoftobjrefs.
2022-03-22T07:57:36.5928504Z
2022-03-22T07:57:36.5928811Z 2022-03-22 07:53:38.15 spid22s index restored for master.MSreplication_options.
2022-03-22T07:57:36.5929027Z
2022-03-22T07:57:36.5929306Z 2022-03-22 07:53:38.19 spid22s index restored for tempdb.syspriorities.
2022-03-22T07:57:36.5929503Z
2022-03-22T07:57:36.5929757Z 2022-03-22 07:53:38.19 spid22s index restored for tempdb.sysowners.
2022-03-22T07:57:36.5930638Z
2022-03-22T07:57:36.5930914Z 2022-03-22 07:53:38.19 spid22s index restored for tempdb.sysdbreg.
2022-03-22T07:57:36.5931104Z
2022-03-22T07:57:36.5931350Z 2022-03-22 07:53:38.20 spid22s index restored for tempdb.sysschobjs.
2022-03-22T07:57:36.5931546Z
2022-03-22T07:57:36.5931823Z 2022-03-22 07:53:38.21 spid22s index restored for tempdb.sysextsources.
2022-03-22T07:57:36.5932397Z
2022-03-22T07:57:36.5932699Z 2022-03-22 07:53:38.21 spid22s index restored for tempdb.sysextfileformats.
2022-03-22T07:57:36.5932908Z
2022-03-22T07:57:36.5933168Z 2022-03-22 07:53:38.22 spid22s index restored for tempdb.syscolpars.
2022-03-22T07:57:36.5933359Z
2022-03-22T07:57:36.5933612Z 2022-03-22 07:53:38.22 spid22s index restored for tempdb.sysxlgns.
2022-03-22T07:57:36.5933800Z
2022-03-22T07:57:36.5934052Z 2022-03-22 07:53:38.22 spid22s index restored for tempdb.sysxsrvs.
2022-03-22T07:57:36.5934459Z
2022-03-22T07:57:36.5934729Z 2022-03-22 07:53:38.22 spid22s index restored for tempdb.sysnsobjs.
2022-03-22T07:57:36.5935207Z
2022-03-22T07:57:36.5935485Z 2022-03-22 07:53:38.22 spid22s index restored for tempdb.syscerts.
2022-03-22T07:57:36.5935668Z
2022-03-22T07:57:36.5935928Z 2022-03-22 07:53:38.23 spid22s index restored for tempdb.sysrmtlgns.
2022-03-22T07:57:36.5936122Z
2022-03-22T07:57:36.5936972Z 2022-03-22 07:53:38.23 spid22s index restored for tempdb.sysxprops.
2022-03-22T07:57:36.5937179Z
2022-03-22T07:57:36.5937479Z 2022-03-22 07:53:38.24 spid22s index restored for tempdb.sysscalartypes.
2022-03-22T07:57:36.5937687Z
2022-03-22T07:57:36.5937951Z 2022-03-22 07:53:38.24 spid22s index restored for tempdb.sysidxstats.
2022-03-22T07:57:36.5938142Z
2022-03-22T07:57:36.5938398Z 2022-03-22 07:53:38.24 spid22s index restored for tempdb.sysendpts.
2022-03-22T07:57:36.5938590Z
2022-03-22T07:57:36.5939057Z 2022-03-22 07:53:38.24 spid22s index restored for tempdb.sysclsobjs.
2022-03-22T07:57:36.5939258Z
2022-03-22T07:57:36.5939537Z 2022-03-22 07:53:38.25 spid22s index restored for tempdb.sysremsvcbinds.
2022-03-22T07:57:36.5939739Z
2022-03-22T07:57:36.5939998Z 2022-03-22 07:53:38.25 spid22s index restored for tempdb.sysrts.
2022-03-22T07:57:36.5940182Z
2022-03-22T07:57:36.5940902Z 2022-03-22 07:53:38.25 spid22s index restored for tempdb.sysasymkeys.
2022-03-22T07:57:36.5941099Z
2022-03-22T07:57:36.5941364Z 2022-03-22 07:53:38.25 spid22s index restored for tempdb.syssqlguides.
2022-03-22T07:57:36.5941562Z
2022-03-22T07:57:36.5941834Z 2022-03-22 07:53:38.25 spid22s index restored for tempdb.syssoftobjrefs.
2022-03-22T07:57:36.5942493Z
2022-03-22T07:57:36.5942776Z 2022-03-22 07:53:38.30 spid22s index restored for model.syspriorities.
2022-03-22T07:57:36.5942974Z
2022-03-22T07:57:36.5943230Z 2022-03-22 07:53:38.30 spid22s index restored for model.sysowners.
2022-03-22T07:57:36.5943416Z
2022-03-22T07:57:36.5943666Z 2022-03-22 07:53:38.31 spid22s index restored for model.sysdbreg.
2022-03-22T07:57:36.5944049Z
2022-03-22T07:57:36.5944319Z 2022-03-22 07:53:38.32 spid22s index restored for model.sysschobjs.
2022-03-22T07:57:36.5944513Z
2022-03-22T07:57:36.5944777Z 2022-03-22 07:53:38.32 spid22s index restored for model.sysextsources.
2022-03-22T07:57:36.5944982Z
2022-03-22T07:57:36.5945460Z 2022-03-22 07:53:38.32 spid22s index restored for model.sysextfileformats.
2022-03-22T07:57:36.5945668Z
2022-03-22T07:57:36.5946028Z 2022-03-22 07:53:38.32 spid22s index restored for model.syscolpars.
2022-03-22T07:57:36.5946229Z
2022-03-22T07:57:36.5946489Z 2022-03-22 07:53:38.33 spid22s index restored for model.sysxlgns.
2022-03-22T07:57:36.5946676Z
2022-03-22T07:57:36.5947132Z 2022-03-22 07:53:38.33 spid22s index restored for model.sysxsrvs.
2022-03-22T07:57:36.5947319Z
2022-03-22T07:57:36.5947568Z 2022-03-22 07:53:38.33 spid22s index restored for model.sysnsobjs.
2022-03-22T07:57:36.5947758Z
2022-03-22T07:57:36.5948012Z 2022-03-22 07:53:38.33 spid22s index restored for model.syscerts.
2022-03-22T07:57:36.5948198Z
2022-03-22T07:57:36.5948647Z 2022-03-22 07:53:38.34 spid22s index restored for model.sysrmtlgns.
2022-03-22T07:57:36.5948843Z
2022-03-22T07:57:36.5949108Z 2022-03-22 07:53:38.34 spid22s index restored for model.sysxprops.
2022-03-22T07:57:36.5949294Z
2022-03-22T07:57:36.5949564Z 2022-03-22 07:53:38.34 spid22s index restored for model.sysscalartypes.
2022-03-22T07:57:36.5949766Z
2022-03-22T07:57:36.5950242Z 2022-03-22 07:53:38.34 spid22s index restored for model.sysidxstats.
2022-03-22T07:57:36.5950450Z
2022-03-22T07:57:36.5950715Z 2022-03-22 07:53:38.34 spid22s index restored for model.sysendpts.
2022-03-22T07:57:36.5950905Z
2022-03-22T07:57:36.5951159Z 2022-03-22 07:53:38.35 spid22s index restored for model.sysclsobjs.
2022-03-22T07:57:36.5951347Z
2022-03-22T07:57:36.5951816Z 2022-03-22 07:53:38.35 spid22s index restored for model.sysremsvcbinds.
2022-03-22T07:57:36.5952023Z
2022-03-22T07:57:36.5952263Z 2022-03-22 07:53:38.35 spid22s index restored for model.sysrts.
2022-03-22T07:57:36.5952447Z
2022-03-22T07:57:36.5952707Z 2022-03-22 07:53:38.35 spid22s index restored for model.sysasymkeys.
2022-03-22T07:57:36.5952900Z
2022-03-22T07:57:36.5953163Z 2022-03-22 07:53:38.35 spid22s index restored for model.syssqlguides.
2022-03-22T07:57:36.5953354Z
2022-03-22T07:57:36.5956543Z 2022-03-22 07:53:38.35 spid22s index restored for model.syssoftobjrefs.
2022-03-22T07:57:36.5956873Z
2022-03-22T07:57:36.5957212Z 2022-03-22 07:53:38.57 spid22s index restored for msdb.syspriorities.
2022-03-22T07:57:36.5957411Z
2022-03-22T07:57:36.5957665Z 2022-03-22 07:53:38.59 spid22s index restored for msdb.sysowners.
2022-03-22T07:57:36.5958134Z
2022-03-22T07:57:36.5958397Z 2022-03-22 07:53:38.59 spid22s index restored for msdb.sysdbreg.
2022-03-22T07:57:36.5958582Z
2022-03-22T07:57:36.5958838Z 2022-03-22 07:53:38.62 spid22s index restored for msdb.sysschobjs.
2022-03-22T07:57:36.5959026Z
2022-03-22T07:57:36.5959289Z 2022-03-22 07:53:38.62 spid22s index restored for msdb.sysextsources.
2022-03-22T07:57:36.5959483Z
2022-03-22T07:57:36.5959746Z 2022-03-22 07:53:38.63 spid22s index restored for msdb.sysextfileformats.
2022-03-22T07:57:36.5960243Z
2022-03-22T07:57:36.6006611Z 2022-03-22 07:53:38.65 spid22s index restored for msdb.syscolpars.
2022-03-22T07:57:36.6006838Z
2022-03-22T07:57:36.6007117Z 2022-03-22 07:53:38.65 spid22s index restored for msdb.sysxlgns.
2022-03-22T07:57:36.6007314Z
2022-03-22T07:57:36.6007569Z 2022-03-22 07:53:38.65 spid22s index restored for msdb.sysxsrvs.
2022-03-22T07:57:36.6007938Z
2022-03-22T07:57:36.6008205Z 2022-03-22 07:53:38.66 spid22s index restored for msdb.sysnsobjs.
2022-03-22T07:57:36.6008394Z
2022-03-22T07:57:36.6009130Z 2022-03-22 07:53:38.66 spid22s index restored for msdb.syscerts.
2022-03-22T07:57:36.6009330Z
2022-03-22T07:57:36.6009616Z 2022-03-22 07:53:38.66 spid22s index restored for msdb.sysrmtlgns.
2022-03-22T07:57:36.6009807Z
2022-03-22T07:57:36.6010062Z 2022-03-22 07:53:38.66 spid22s index restored for msdb.sysxprops.
2022-03-22T07:57:36.6010251Z
2022-03-22T07:57:36.6010530Z 2022-03-22 07:53:38.66 spid22s index restored for msdb.sysscalartypes.
2022-03-22T07:57:36.6011206Z
2022-03-22T07:57:36.6011465Z 2022-03-22 07:53:38.67 spid22s index restored for msdb.sysidxstats.
2022-03-22T07:57:36.6011660Z
2022-03-22T07:57:36.6012019Z 2022-03-22 07:53:38.67 spid22s index restored for msdb.sysendpts.
2022-03-22T07:57:36.6012211Z
2022-03-22T07:57:36.6012475Z 2022-03-22 07:53:38.67 spid22s index restored for msdb.sysclsobjs.
2022-03-22T07:57:36.6012903Z
2022-03-22T07:57:36.6013255Z 2022-03-22 07:53:38.67 spid22s index restored for msdb.sysremsvcbinds.
2022-03-22T07:57:36.6013452Z
2022-03-22T07:57:36.6013703Z 2022-03-22 07:53:38.67 spid22s index restored for msdb.sysrts.
2022-03-22T07:57:36.6013885Z
2022-03-22T07:57:36.6014590Z 2022-03-22 07:53:38.68 spid22s index restored for msdb.sysasymkeys.
2022-03-22T07:57:36.6014790Z
2022-03-22T07:57:36.6015061Z 2022-03-22 07:53:38.68 spid22s index restored for msdb.syssqlguides.
2022-03-22T07:57:36.6015252Z
2022-03-22T07:57:36.6015518Z 2022-03-22 07:53:38.69 spid22s index restored for msdb.syssoftobjrefs.
2022-03-22T07:57:36.6015716Z
2022-03-22T07:57:36.6016003Z 2022-03-22 07:53:38.69 spid22s index restored for msdb.syscachedcredentials.
2022-03-22T07:57:36.6016216Z
2022-03-22T07:57:36.6016519Z 2022-03-22 07:53:38.69 spid22s index restored for msdb.syscollector_blobs_internal.
2022-03-22T07:57:36.6016723Z
2022-03-22T07:57:36.6017874Z 2022-03-22 07:53:38.70 spid22s index restored for msdb.syspolicy_system_health_state_internal.
2022-03-22T07:57:36.6018115Z
2022-03-22T07:57:36.6018475Z 2022-03-22 07:53:38.71 spid22s index restored for msdb.sysmanagement_shared_server_groups_internal.
2022-03-22T07:57:36.6018707Z
2022-03-22T07:57:36.6018977Z 2022-03-22 07:53:38.71 spid22s index restored for msdb.sysssispackages.
2022-03-22T07:57:36.6019178Z
2022-03-22T07:57:36.6019954Z 2022-03-22 07:53:38.72 spid22s index restored for msdb.sysmanagement_shared_registered_servers_internal.
2022-03-22T07:57:36.6020201Z
2022-03-22T07:57:36.6020509Z 2022-03-22 07:53:38.72 spid22s index restored for msdb.sysssispackagefolders.
2022-03-22T07:57:36.6020720Z
2022-03-22T07:57:36.6021132Z 2022-03-22 07:53:38.73 spid22s index restored for msdb.sysutility_mi_smo_properties_to_collect_internal.
2022-03-22T07:57:36.6021722Z
2022-03-22T07:57:36.6022057Z 2022-03-22 07:53:38.73 spid22s index restored for msdb.syspolicy_configuration_internal.
2022-03-22T07:57:36.6022281Z
2022-03-22T07:57:36.6022586Z 2022-03-22 07:53:38.74 spid22s index restored for msdb.log_shipping_primary_databases.
2022-03-22T07:57:36.6022802Z
2022-03-22T07:57:36.6023096Z 2022-03-22 07:53:38.75 spid22s index restored for msdb.syspolicy_management_facets.
2022-03-22T07:57:36.6023306Z
2022-03-22T07:57:36.6023589Z 2022-03-22 07:53:38.76 spid22s index restored for msdb.syspolicy_facet_events.
2022-03-22T07:57:36.6023791Z
2022-03-22T07:57:36.6024086Z 2022-03-22 07:53:38.77 spid22s index restored for msdb.syscollector_config_store_internal.
2022-03-22T07:57:36.6024756Z
2022-03-22T07:57:36.6025081Z 2022-03-22 07:53:38.77 spid22s index restored for msdb.sysutility_ucp_dac_health_internal.
2022-03-22T07:57:36.6025300Z
2022-03-22T07:57:36.6025568Z 2022-03-22 07:53:38.77 spid22s index restored for msdb.sysmail_profile.
2022-03-22T07:57:36.6025767Z
2022-03-22T07:57:36.6026013Z 2022-03-22 07:53:38.77 spid22s index restored for msdb.MSdbms.
2022-03-22T07:57:36.6026615Z
2022-03-22T07:57:36.6027160Z 2022-03-22 07:53:38.78 spid22s index restored for msdb.log_shipping_primary_secondaries.
2022-03-22T07:57:36.6027374Z
2022-03-22T07:57:36.6027681Z 2022-03-22 07:53:38.79 spid22s index restored for msdb.syspolicy_conditions_internal.
2022-03-22T07:57:36.6027895Z
2022-03-22T07:57:36.6028160Z 2022-03-22 07:53:38.80 spid22s index restored for msdb.MSdbms_datatype.
2022-03-22T07:57:36.6028355Z
2022-03-22T07:57:36.6029045Z 2022-03-22 07:53:38.80 spid22s index restored for msdb.log_shipping_monitor_primary.
2022-03-22T07:57:36.6029258Z
2022-03-22T07:57:36.6029589Z 2022-03-22 07:53:38.80 spid22s index restored for msdb.log_shipping_monitor_history_detail.
2022-03-22T07:57:36.6029804Z
2022-03-22T07:57:36.6030304Z 2022-03-22 07:53:38.81 spid22s index restored for msdb.log_shipping_monitor_error_detail.
2022-03-22T07:57:36.6030888Z
2022-03-22T07:57:36.6031198Z 2022-03-22 07:53:38.81 spid22s index restored for msdb.log_shipping_secondary.
2022-03-22T07:57:36.6031393Z
2022-03-22T07:57:36.6031949Z 2022-03-22 07:53:38.81 spid22s index restored for msdb.log_shipping_secondary_databases.
2022-03-22T07:57:36.6032911Z
2022-03-22T07:57:36.6033794Z 2022-03-22 07:53:38.81 spid22s index restored for msdb.sysutility_ucp_managed_instances_internal.
2022-03-22T07:57:36.6034028Z
2022-03-22T07:57:36.6034560Z 2022-03-22 07:53:38.82 spid22s index restored for msdb.log_shipping_monitor_secondary.
2022-03-22T07:57:36.6034771Z
2022-03-22T07:57:36.6035041Z 2022-03-22 07:53:38.82 spid22s index restored for msdb.sysmail_account.
2022-03-22T07:57:36.6035915Z
2022-03-22T07:57:36.6036442Z 2022-03-22 07:53:38.83 spid22s index restored for msdb.sysutility_ucp_mi_health_internal.
2022-03-22T07:57:36.6036659Z
2022-03-22T07:57:36.6037355Z 2022-03-22 07:53:38.83 spid22s index restored for msdb.sysdac_instances_internal.
2022-03-22T07:57:36.6037563Z
2022-03-22T07:57:36.6037885Z 2022-03-22 07:53:38.84 spid22s index restored for msdb.syscollector_collection_sets_internal.
2022-03-22T07:57:36.6038103Z
2022-03-22T07:57:36.6039320Z 2022-03-22 07:53:38.84 spid22s index restored for msdb.syspolicy_policy_categories_internal.
2022-03-22T07:57:36.6039554Z
2022-03-22T07:57:36.6039863Z 2022-03-22 07:53:38.84 spid22s index restored for msdb.sysdac_history_internal.
2022-03-22T07:57:36.6040075Z
2022-03-22T07:57:36.6040349Z 2022-03-22 07:53:38.85 spid22s index restored for msdb.sysmail_servertype.
2022-03-22T07:57:36.6040775Z
2022-03-22T07:57:36.6041278Z 2022-03-22 07:53:38.85 spid22s index restored for msdb.syspolicy_object_sets_internal.
2022-03-22T07:57:36.6067599Z
2022-03-22T07:57:36.6068702Z 2022-03-22 07:53:38.86 spid22s index restored for msdb.sysutility_ucp_health_policies_internal.
2022-03-22T07:57:36.6068959Z
2022-03-22T07:57:36.6069243Z 2022-03-22 07:53:38.86 spid22s index restored for msdb.sysmail_server.
2022-03-22T07:57:36.6069449Z
2022-03-22T07:57:36.6069827Z 2022-03-22 07:53:38.86 spid22s index restored for msdb.sysutility_ucp_filegroups_with_policy_violations_internal.
2022-03-22T07:57:36.6070081Z
2022-03-22T07:57:36.6071211Z 2022-03-22 07:53:38.87 spid22s index restored for msdb.sysutility_ucp_policy_check_conditions_internal.
2022-03-22T07:57:36.6071455Z
2022-03-22T07:57:36.6071791Z 2022-03-22 07:53:38.87 spid22s index restored for msdb.syscollector_collector_types_internal.
2022-03-22T07:57:36.6072020Z
2022-03-22T07:57:36.6072318Z 2022-03-22 07:53:38.88 spid22s index restored for msdb.syspolicy_policies_internal.
2022-03-22T07:57:36.6072531Z
2022-03-22T07:57:36.6073448Z 2022-03-22 07:53:38.89 spid22s index restored for msdb.sysutility_ucp_policy_target_conditions_internal.
2022-03-22T07:57:36.6073697Z
2022-03-22T07:57:36.6074008Z 2022-03-22 07:53:38.89 spid22s index restored for msdb.sysmail_configuration.
2022-03-22T07:57:36.6074222Z
2022-03-22T07:57:36.6074523Z 2022-03-22 07:53:38.89 spid22s index restored for msdb.external_libraries_installed.
2022-03-22T07:57:36.6075329Z
2022-03-22T07:57:36.6075654Z 2022-03-22 07:53:38.90 spid22s index restored for msdb.sysdbmaintplan_databases.
2022-03-22T07:57:36.6075864Z
2022-03-22T07:57:36.6076708Z 2022-03-22 07:53:38.90 spid22s index restored for msdb.sysutility_ucp_configuration_internal.
2022-03-22T07:57:36.6076945Z
2022-03-22T07:57:36.6077698Z 2022-03-22 07:53:38.90 spid22s index restored for msdb.sysproxies.
2022-03-22T07:57:36.6077890Z
2022-03-22T07:57:36.6078165Z 2022-03-22 07:53:38.91 spid22s index restored for msdb.syssubsystems.
2022-03-22T07:57:36.6078814Z
2022-03-22T07:57:36.6079153Z 2022-03-22 07:53:38.91 spid22s index restored for msdb.syscollector_collection_items_internal.
2022-03-22T07:57:36.6079366Z
2022-03-22T07:57:36.6079641Z 2022-03-22 07:53:38.92 spid22s index restored for msdb.sysdownloadlist.
2022-03-22T07:57:36.6079844Z
2022-03-22T07:57:36.6081277Z 2022-03-22 07:53:38.92 spid22s index restored for msdb.sysoriginatingservers.
2022-03-22T07:57:36.6081790Z
2022-03-22T07:57:36.6082125Z 2022-03-22 07:53:38.93 spid22s index restored for msdb.autoadmin_managed_databases.
2022-03-22T07:57:36.6082337Z
2022-03-22T07:57:36.6082952Z 2022-03-22 07:53:38.93 spid22s index restored for msdb.sysjobs.
2022-03-22T07:57:36.6083146Z
2022-03-22T07:57:36.6084021Z 2022-03-22 07:53:38.93 spid22s index restored for msdb.smart_backup_files.
2022-03-22T07:57:36.6084418Z
2022-03-22T07:57:36.6084701Z 2022-03-22 07:53:38.94 spid22s index restored for msdb.backupset.
2022-03-22T07:57:36.6084891Z
2022-03-22T07:57:36.6085151Z 2022-03-22 07:53:38.94 spid22s index restored for msdb.sysjobsteps.
2022-03-22T07:57:36.6085342Z
2022-03-22T07:57:36.6087110Z 2022-03-22 07:53:38.94 spid22s index restored for msdb.syscollector_execution_stats_internal.
2022-03-22T07:57:36.6087361Z
2022-03-22T07:57:36.6087739Z 2022-03-22 07:53:38.95 spid22s index restored for msdb.sysutility_ucp_mi_file_space_health_internal.
2022-03-22T07:57:36.6087976Z
2022-03-22T07:57:36.6088666Z 2022-03-22 07:53:38.95 spid22s index restored for msdb.syspolicy_target_sets_internal.
2022-03-22T07:57:36.6088879Z
2022-03-22T07:57:36.6089153Z 2022-03-22 07:53:38.96 spid22s index restored for msdb.sysschedules.
2022-03-22T07:57:36.6089350Z
2022-03-22T07:57:36.6089680Z 2022-03-22 07:53:38.96 spid22s index restored for msdb.sysutility_ucp_mi_database_health_internal.
2022-03-22T07:57:36.6089904Z
2022-03-22T07:57:36.6090172Z 2022-03-22 07:53:38.96 spid22s index restored for msdb.logmarkhistory.
2022-03-22T07:57:36.6090569Z
2022-03-22T07:57:36.6091330Z 2022-03-22 07:53:38.97 spid22s index restored for msdb.sysutility_ucp_dac_file_space_health_internal.
2022-03-22T07:57:36.6092152Z
2022-03-22T07:57:36.6092443Z 2022-03-22 07:53:38.98 spid22s index restored for msdb.syscategories.
2022-03-22T07:57:36.6092639Z
2022-03-22T07:57:36.6093193Z 2022-03-22 07:53:38.98 spid22s index restored for msdb.systargetservers.
2022-03-22T07:57:36.6093698Z
2022-03-22T07:57:36.6094061Z 2022-03-22 07:53:38.99 spid22s index restored for msdb.sysutility_ucp_mi_volume_space_health_internal.
2022-03-22T07:57:36.6094526Z
2022-03-22T07:57:36.6094879Z 2022-03-22 07:53:38.99 spid22s index restored for msdb.sysutility_mi_dac_execution_statistics_internal.
2022-03-22T07:57:36.6095115Z
2022-03-22T07:57:36.6095409Z 2022-03-22 07:53:38.99 spid22s index restored for msdb.systargetservergroups.
2022-03-22T07:57:36.6095625Z
2022-03-22T07:57:36.6096552Z 2022-03-22 07:53:38.99 spid22s index restored for msdb.syspolicy_policy_category_subscriptions_internal.
2022-03-22T07:57:36.6096797Z
2022-03-22T07:57:36.6097048Z 2022-03-22 07:53:39.00 spid22s index restored for msdb.sysalerts.
2022-03-22T07:57:36.6097241Z
2022-03-22T07:57:36.6097574Z 2022-03-22 07:53:39.00 spid22s index restored for msdb.sysutility_ucp_computer_cpu_health_internal.
2022-03-22T07:57:36.6097808Z
2022-03-22T07:57:36.6098133Z 2022-03-22 07:53:39.00 spid22s index restored for msdb.sysutility_mi_session_statistics_internal.
2022-03-22T07:57:36.6098506Z
2022-03-22T07:57:36.6098771Z 2022-03-22 07:53:39.01 spid22s index restored for msdb.sysoperators.
2022-03-22T07:57:36.6098966Z
2022-03-22T07:57:36.6099712Z 2022-03-22 07:53:39.03 spid22s The default collation was successfully changed.
```
</p>
</details>
https://github.com/trinodb/trino/runs/5640191532?check_suite_focus=true
|
non_main
|
flaky testingsqlserver initialization due to log message wait strategy the expected message the default collation was successfully changed was logged but logmessagewaitstrategy seems failing org testcontainers containers containerlaunchexception timed out waiting for log output matching the default collation was successfully changed at org testcontainers containers wait strategy logmessagewaitstrategy waituntilready logmessagewaitstrategy java at org testcontainers containers wait strategy abstractwaitstrategy waituntilready abstractwaitstrategy java at io trino plugin sqlserver testingsqlserver waituntilcontainerstarted testingsqlserver java at org testcontainers containers genericcontainer trystart genericcontainer java at org testcontainers containers genericcontainer lambda dostart genericcontainer java at org rnorth ducttape unreliables unreliables retryuntilsuccess unreliables java at org testcontainers containers genericcontainer dostart genericcontainer java at org testcontainers containers genericcontainer start genericcontainer java at io trino testing containers testcontainers startorreuse testcontainers java at io trino plugin sqlserver testingsqlserver createcontainer testingsqlserver java at io trino plugin sqlserver testingsqlserver lambda new testingsqlserver java at net jodah failsafe functions lambda get functions java at net jodah failsafe timeoutexecutor lambda supply timeoutexecutor java at net jodah failsafe retrypolicyexecutor lambda supply retrypolicyexecutor java at net jodah failsafe execution executesync execution java at net jodah failsafe failsafeexecutor call failsafeexecutor java at net jodah failsafe failsafeexecutor get failsafeexecutor java at io trino plugin sqlserver testingsqlserver testingsqlserver java at io trino plugin sqlserver testingsqlserver testingsqlserver java at io trino plugin sqlserver basesqlservertransactionisolationtest createqueryrunner basesqlservertransactionisolationtest java at io trino testing abstracttestqueryframework init abstracttestqueryframework java at java base jdk internal reflect nativemethodaccessorimpl native method at java base jdk internal reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at java base jdk internal reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java base java lang reflect method invoke method java at org testng internal methodinvocationhelper invokemethod methodinvocationhelper java at org testng internal invoker invokeconfigurationmethod invoker java at org testng internal invoker invokeconfigurations invoker java at org testng internal invoker invokeconfigurations invoker java at org testng internal testmethodworker invokebeforeclassmethods testmethodworker java at org testng internal testmethodworker run testmethodworker java at java base java util concurrent threadpoolexecutor runworker threadpoolexecutor java at java base java util concurrent threadpoolexecutor worker run threadpoolexecutor java at java base java lang thread run thread java info dispatcher query io trino event querymonitor timeline query vjzbw transaction elapsed planning waiting scheduling running finishing begin end open error pool thread 🐳 log output from the failed container server setup step is copying system data file c templatedata master mdf to var opt mssql data master mdf server did not find an existing master data file var opt mssql data master mdf copying the missing default master and other system database files if you have moved the database location but not moved the database files startup may fail to repair shutdown sql server move the master database to configured location and restart server setup step is copying system data file c templatedata mastlog ldf to var opt mssql data mastlog ldf server setup step is copying system data file c templatedata model mdf to var opt mssql data model mdf server setup step is copying system data file c templatedata modellog ldf to var opt mssql data modellog ldf server setup step is copying system data file c templatedata msdbdata mdf to var opt mssql data msdbdata mdf server setup step is copying system data file c templatedata msdblog ldf to var opt mssql data msdblog ldf server microsoft sql server rtm nov copyright c microsoft corporation developer edition bit on linux ubuntu lts server utc adjustment server c microsoft corporation server all rights reserved server server process id is server logging sql server messages in file var opt mssql log errorlog server registry startup parameters d var opt mssql data master mdf l var opt mssql data mastlog ldf e var opt mssql log errorlog server sql server detected sockets with cores per socket and logical processors per socket total logical processors using logical processors based on sql server licensing this is an informational message no user action is required server sql server is starting at normal priority base this is an informational message only no user action is required server detected mb of ram this is an informational message no user action is required server using conventional memory in the memory manager server machine supports memory error recovery sql memory protection is enabled to recover from memory corruption server buffer pool extension is already disabled no action is necessary server initializeexternalusergroupsid failed implied authentication will be disabled server implied authentication manager initialization failed implied authentication will be disabled server successfully initialized the tls configuration allowed tls protocol versions are allowed tls ciphers are server the maximum number of dedicated administrator connections for this instance is server node configuration node cpu mask active cpu mask this message provides a description of the numa configuration for this computer this is an informational message only no user action is required server using dynamic lock allocation initial allocation of lock blocks and lock owner blocks per node this is an informational message only no user action is required server in memory oltp initialized on lowend machine server database instant file initialization enabled for security and performance considerations see the topic database instant file initialization in sql server books online this is an informational message only no user action is required forceflush is enabled for this instance server query store settings initialized with enabled server software usage metrics is disabled starting up database master forceflush feature is enabled for log durability the tail of the log for database master is being rewritten to match the new sector size of bytes bytes at offset in file var opt mssql data mastlog ldf will be written converting database master from version to the current version database master running the upgrade step from version to version database master running the upgrade step from version to version database master running the upgrade step from version to version database master running the upgrade step from version to version database master running the upgrade step from version to version database master running the upgrade step from version to version database master running the upgrade step from version to version resource governor reconfiguration succeeded sql server audit is starting the audits this is an informational message no user action is required sql server audit has started the audits this is an informational message no user action is required sql trace id was started by login sa server name is this is an informational message only no user action is required password policy update was successful starting up database msdb always on the availability replica manager is starting this is an informational message only no user action is required starting up database mssqlsystemresource always on the availability replica manager is waiting for the instance of sql server to allow client connections this is an informational message only no user action is required the resource database build version is this is an informational message only no user action is required starting up database model a self generated certificate was successfully loaded for encryption server is listening on server server is listening on the tail of the log for database model is being rewritten to match the new sector size of bytes bytes at offset in file var opt mssql data modellog ldf will be written server dedicated admin connection support was established for listening locally on port the tail of the log for database msdb is being rewritten to match the new sector size of bytes bytes at offset in file var opt mssql data msdblog ldf will be written converting database model from version to the current version database model running the upgrade step from version to version converting database msdb from version to the current version database msdb running the upgrade step from version to version database model running the upgrade step from version to version sql server is now ready for client connections this is an informational message no user action is required database msdb running the upgrade step from version to version database model running the upgrade step from version to version database model running the upgrade step from version to version database model running the upgrade step from version to version database msdb running the upgrade step from version to version database model running the upgrade step from version to version database msdb running the upgrade step from version to version database msdb running the upgrade step from version to version database model running the upgrade step from version to version database msdb running the upgrade step from version to version database msdb running the upgrade step from version to version polybase feature disabled clearing tempdb database starting up database tempdb the tempdb database has data file s the service broker endpoint is in disabled or stopped state the database mirroring endpoint is in disabled or stopped state service broker manager has started recovery is complete this is an informational message only no user action is required the default language lcid has been set for engine and full text services warning attempting to change default collation to general cs as index restored for master syspriorities index restored for master sysbrickfiles index restored for master sysowners index restored for master sysdbreg index restored for master sysschobjs index restored for master sysextsources index restored for master sysextfileformats index restored for master syscolpars index restored for master sysxlgns index restored for master sysxsrvs index restored for master sysnsobjs index restored for master syscerts index restored for master sysrmtlgns index restored for master sysxprops index restored for master sysscalartypes index restored for master sysidxstats index restored for master sysendpts index restored for master sysclsobjs index restored for master sysremsvcbinds index restored for master sysrts index restored for master sysasymkeys index restored for master syssqlguides index restored for master syssoftobjrefs index restored for master msreplication options index restored for tempdb syspriorities index restored for tempdb sysowners index restored for tempdb sysdbreg index restored for tempdb sysschobjs index restored for tempdb sysextsources index restored for tempdb sysextfileformats index restored for tempdb syscolpars index restored for tempdb sysxlgns index restored for tempdb sysxsrvs index restored for tempdb sysnsobjs index restored for tempdb syscerts index restored for tempdb sysrmtlgns index restored for tempdb sysxprops index restored for tempdb sysscalartypes index restored for tempdb sysidxstats index restored for tempdb sysendpts index restored for tempdb sysclsobjs index restored for tempdb sysremsvcbinds index restored for tempdb sysrts index restored for tempdb sysasymkeys index restored for tempdb syssqlguides index restored for tempdb syssoftobjrefs index restored for model syspriorities index restored for model sysowners index restored for model sysdbreg index restored for model sysschobjs index restored for model sysextsources index restored for model sysextfileformats index restored for model syscolpars index restored for model sysxlgns index restored for model sysxsrvs index restored for model sysnsobjs index restored for model syscerts index restored for model sysrmtlgns index restored for model sysxprops index restored for model sysscalartypes index restored for model sysidxstats index restored for model sysendpts index restored for model sysclsobjs index restored for model sysremsvcbinds index restored for model sysrts index restored for model sysasymkeys index restored for model syssqlguides index restored for model syssoftobjrefs index restored for msdb syspriorities index restored for msdb sysowners index restored for msdb sysdbreg index restored for msdb sysschobjs index restored for msdb sysextsources index restored for msdb sysextfileformats index restored for msdb syscolpars index restored for msdb sysxlgns index restored for msdb sysxsrvs index restored for msdb sysnsobjs index restored for msdb syscerts index restored for msdb sysrmtlgns index restored for msdb sysxprops index restored for msdb sysscalartypes index restored for msdb sysidxstats index restored for msdb sysendpts index restored for msdb sysclsobjs index restored for msdb sysremsvcbinds index restored for msdb sysrts index restored for msdb sysasymkeys index restored for msdb syssqlguides index restored for msdb syssoftobjrefs index restored for msdb syscachedcredentials index restored for msdb syscollector blobs internal index restored for msdb syspolicy system health state internal index restored for msdb sysmanagement shared server groups internal index restored for msdb sysssispackages index restored for msdb sysmanagement shared registered servers internal index restored for msdb sysssispackagefolders index restored for msdb sysutility mi smo properties to collect internal index restored for msdb syspolicy configuration internal index restored for msdb log shipping primary databases index restored for msdb syspolicy management facets index restored for msdb syspolicy facet events index restored for msdb syscollector config store internal index restored for msdb sysutility ucp dac health internal index restored for msdb sysmail profile index restored for msdb msdbms index restored for msdb log shipping primary secondaries index restored for msdb syspolicy conditions internal index restored for msdb msdbms datatype index restored for msdb log shipping monitor primary index restored for msdb log shipping monitor history detail index restored for msdb log shipping monitor error detail index restored for msdb log shipping secondary index restored for msdb log shipping secondary databases index restored for msdb sysutility ucp managed instances internal index restored for msdb log shipping monitor secondary index restored for msdb sysmail account index restored for msdb sysutility ucp mi health internal index restored for msdb sysdac instances internal index restored for msdb syscollector collection sets internal index restored for msdb syspolicy policy categories internal index restored for msdb sysdac history internal index restored for msdb sysmail servertype index restored for msdb syspolicy object sets internal index restored for msdb sysutility ucp health policies internal index restored for msdb sysmail server index restored for msdb sysutility ucp filegroups with policy violations internal index restored for msdb sysutility ucp policy check conditions internal index restored for msdb syscollector collector types internal index restored for msdb syspolicy policies internal index restored for msdb sysutility ucp policy target conditions internal index restored for msdb sysmail configuration index restored for msdb external libraries installed index restored for msdb sysdbmaintplan databases index restored for msdb sysutility ucp configuration internal index restored for msdb sysproxies index restored for msdb syssubsystems index restored for msdb syscollector collection items internal index restored for msdb sysdownloadlist index restored for msdb sysoriginatingservers index restored for msdb autoadmin managed databases index restored for msdb sysjobs index restored for msdb smart backup files index restored for msdb backupset index restored for msdb sysjobsteps index restored for msdb syscollector execution stats internal index restored for msdb sysutility ucp mi file space health internal index restored for msdb syspolicy target sets internal index restored for msdb sysschedules index restored for msdb sysutility ucp mi database health internal index restored for msdb logmarkhistory index restored for msdb sysutility ucp dac file space health internal index restored for msdb syscategories index restored for msdb systargetservers index restored for msdb sysutility ucp mi volume space health internal index restored for msdb sysutility mi dac execution statistics internal index restored for msdb systargetservergroups index restored for msdb syspolicy policy category subscriptions internal index restored for msdb sysalerts index restored for msdb sysutility ucp computer cpu health internal index restored for msdb sysutility mi session statistics internal index restored for msdb sysoperators the default collation was successfully changed
| 0
|
4,514
| 23,465,785,455
|
IssuesEvent
|
2022-08-16 16:37:51
|
aws/aws-sam-cli
|
https://api.github.com/repos/aws/aws-sam-cli
|
closed
|
Accept concurrent requests when using --warm-containers
|
type/feature area/local/invoke maintainer/need-followup
|
### Describe your idea/feature/enhancement
When developing serving an API locally you may run into concurrent requests done by a browser, and in macOS specifically without the `--warm-containers` option enabled it's very hard to test an endpoint that renders HTML, for example ([as each lambda invocation is going to take ~3s](https://github.com/aws/aws-sam-cli/issues/2858)).
So, with that in mind, I'd love to see concurrent requests being supported when using one of the `--warm-containers` options.
By looking at the repository code it seems that `lambda_runner.invoke` is not expecting concurrent requests while reading the stdout stream which causes the concurrent requests to fail as the stdout is `b''` and not a valid JSON response.
I came across [this](https://github.com/aws/aws-sam-cli/issues/2502#issuecomment-750475792) while searching about concurrency so, feel free to close this one if the team understands that this is cause more problems than a solution.
### Proposal
I'd like to propose a way to accept concurrent requests in similar (couldn't find a better word but, it's far from similar) how NGINX and API Gateway deals with requests by accepting N of them but, since we have Docker as a limiting factor, processing it one at a time (similar to having a rate of 1 request/s but with 100 requests as a burst, for example).
I came up with this patch for it:
```diff
diff --git a/samcli/local/apigw/local_apigw_service.py b/samcli/local/apigw/local_apigw_service.py
index cc2684c2..93964c22 100644
--- a/samcli/local/apigw/local_apigw_service.py
+++ b/samcli/local/apigw/local_apigw_service.py
@@ -3,6 +3,7 @@ import io
import json
import logging
import base64
+import threading
from typing import List, Optional
from flask import Flask, request
@@ -137,6 +138,7 @@ class LocalApigwService(BaseLocalService):
self.static_dir = static_dir
self._dict_of_routes = {}
self.stderr = stderr
+ self._lock = threading.BoundedSemaphore()
def create(self):
"""
@@ -155,6 +157,10 @@ class LocalApigwService(BaseLocalService):
# Prevent the dev server from emitting headers that will make the browser cache response by default
self._app.config["SEND_FILE_MAX_AGE_DEFAULT"] = 0
+ self._app.before_request(self._block_concurrent_requests)
+ self._app.teardown_request(self._release_request_lock)
+
+
# This will normalize all endpoints and strip any trailing '/'
self._app.url_map.strict_slashes = False
default_route = None
@@ -256,6 +262,7 @@ class LocalApigwService(BaseLocalService):
self._app.register_error_handler(405, ServiceErrorResponses.route_not_found)
# Something went wrong
self._app.register_error_handler(500, ServiceErrorResponses.lambda_failure_response)
+ self._app.register_error_handler(504, ServiceErrorResponses.gateway_timeout)
def _request_handler(self, **kwargs):
"""
@@ -838,3 +845,16 @@ class LocalApigwService(BaseLocalService):
"""
return request_mimetype in binary_types or "*/*" in binary_types
+
+ def _block_concurrent_requests(self):
+ # Use the hard timeout of APIG for integrations for each request.
+ acquired = self._lock.acquire(timeout=29)
+
+ if not acquired:
+ return ServiceErrorResponses.gateway_timeout()
+
+ def _release_request_lock(self, error=None):
+ try:
+ self._lock.release()
+ except ValueError:
+ LOG.debug("Tried to release more than it should.")
diff --git a/samcli/local/apigw/service_error_responses.py b/samcli/local/apigw/service_error_responses.py
index e2214dad..41231b9b 100644
--- a/samcli/local/apigw/service_error_responses.py
+++ b/samcli/local/apigw/service_error_responses.py
@@ -8,9 +8,11 @@ class ServiceErrorResponses:
_NO_LAMBDA_INTEGRATION = {"message": "No function defined for resource method"}
_MISSING_AUTHENTICATION = {"message": "Missing Authentication Token"}
_LAMBDA_FAILURE = {"message": "Internal server error"}
+ _GATEWAY_TIMEOUT = {"message": "Gateway Timeout"}
HTTP_STATUS_CODE_502 = 502
HTTP_STATUS_CODE_403 = 403
+ HTTP_STATUS_CODE_504 = 504
@staticmethod
def lambda_failure_response(*args):
@@ -42,3 +44,8 @@ class ServiceErrorResponses:
"""
response_data = jsonify(ServiceErrorResponses._MISSING_AUTHENTICATION)
return make_response(response_data, ServiceErrorResponses.HTTP_STATUS_CODE_403)
+
+ @staticmethod
+ def gateway_timeout(*args):
+ response_data = jsonify(ServiceErrorResponses._GATEWAY_TIMEOUT)
+ return make_response(response_data, ServiceErrorResponses.HTTP_STATUS_CODE_504)
```
The code above uses a mutex to make the Flask threads wait until the previous one finishes by using Flask's [before_request](https://flask.palletsprojects.com/en/2.0.x/api/#flask.Flask.before_request) and [teardown_request](https://flask.palletsprojects.com/en/2.0.x/api/#flask.Flask.teardown_request). The first one tries to acquire the lock within a 29s timeout (which is the same used in APIG) while the second one releases it. If a thread can't acquire the lock within the 29s interval it raises a `504 Bad gateway`.
There's a drawback to it, of course, if for some reason the lambda function times out the container doesn't flush some of the requests (I didn't look into it deeply but, it was what I could observe from my tests). It seems that _maybe_ the `invoke` hangs? Or Docker hangs? Well, and this is the part where it may not be feasible or some guidance is needed to move forward.
Thanks for reading thru this!
|
True
|
Accept concurrent requests when using --warm-containers - ### Describe your idea/feature/enhancement
When developing serving an API locally you may run into concurrent requests done by a browser, and in macOS specifically without the `--warm-containers` option enabled it's very hard to test an endpoint that renders HTML, for example ([as each lambda invocation is going to take ~3s](https://github.com/aws/aws-sam-cli/issues/2858)).
So, with that in mind, I'd love to see concurrent requests being supported when using one of the `--warm-containers` options.
By looking at the repository code it seems that `lambda_runner.invoke` is not expecting concurrent requests while reading the stdout stream which causes the concurrent requests to fail as the stdout is `b''` and not a valid JSON response.
I came across [this](https://github.com/aws/aws-sam-cli/issues/2502#issuecomment-750475792) while searching about concurrency so, feel free to close this one if the team understands that this is cause more problems than a solution.
### Proposal
I'd like to propose a way to accept concurrent requests in similar (couldn't find a better word but, it's far from similar) how NGINX and API Gateway deals with requests by accepting N of them but, since we have Docker as a limiting factor, processing it one at a time (similar to having a rate of 1 request/s but with 100 requests as a burst, for example).
I came up with this patch for it:
```diff
diff --git a/samcli/local/apigw/local_apigw_service.py b/samcli/local/apigw/local_apigw_service.py
index cc2684c2..93964c22 100644
--- a/samcli/local/apigw/local_apigw_service.py
+++ b/samcli/local/apigw/local_apigw_service.py
@@ -3,6 +3,7 @@ import io
import json
import logging
import base64
+import threading
from typing import List, Optional
from flask import Flask, request
@@ -137,6 +138,7 @@ class LocalApigwService(BaseLocalService):
self.static_dir = static_dir
self._dict_of_routes = {}
self.stderr = stderr
+ self._lock = threading.BoundedSemaphore()
def create(self):
"""
@@ -155,6 +157,10 @@ class LocalApigwService(BaseLocalService):
# Prevent the dev server from emitting headers that will make the browser cache response by default
self._app.config["SEND_FILE_MAX_AGE_DEFAULT"] = 0
+ self._app.before_request(self._block_concurrent_requests)
+ self._app.teardown_request(self._release_request_lock)
+
+
# This will normalize all endpoints and strip any trailing '/'
self._app.url_map.strict_slashes = False
default_route = None
@@ -256,6 +262,7 @@ class LocalApigwService(BaseLocalService):
self._app.register_error_handler(405, ServiceErrorResponses.route_not_found)
# Something went wrong
self._app.register_error_handler(500, ServiceErrorResponses.lambda_failure_response)
+ self._app.register_error_handler(504, ServiceErrorResponses.gateway_timeout)
def _request_handler(self, **kwargs):
"""
@@ -838,3 +845,16 @@ class LocalApigwService(BaseLocalService):
"""
return request_mimetype in binary_types or "*/*" in binary_types
+
+ def _block_concurrent_requests(self):
+ # Use the hard timeout of APIG for integrations for each request.
+ acquired = self._lock.acquire(timeout=29)
+
+ if not acquired:
+ return ServiceErrorResponses.gateway_timeout()
+
+ def _release_request_lock(self, error=None):
+ try:
+ self._lock.release()
+ except ValueError:
+ LOG.debug("Tried to release more than it should.")
diff --git a/samcli/local/apigw/service_error_responses.py b/samcli/local/apigw/service_error_responses.py
index e2214dad..41231b9b 100644
--- a/samcli/local/apigw/service_error_responses.py
+++ b/samcli/local/apigw/service_error_responses.py
@@ -8,9 +8,11 @@ class ServiceErrorResponses:
_NO_LAMBDA_INTEGRATION = {"message": "No function defined for resource method"}
_MISSING_AUTHENTICATION = {"message": "Missing Authentication Token"}
_LAMBDA_FAILURE = {"message": "Internal server error"}
+ _GATEWAY_TIMEOUT = {"message": "Gateway Timeout"}
HTTP_STATUS_CODE_502 = 502
HTTP_STATUS_CODE_403 = 403
+ HTTP_STATUS_CODE_504 = 504
@staticmethod
def lambda_failure_response(*args):
@@ -42,3 +44,8 @@ class ServiceErrorResponses:
"""
response_data = jsonify(ServiceErrorResponses._MISSING_AUTHENTICATION)
return make_response(response_data, ServiceErrorResponses.HTTP_STATUS_CODE_403)
+
+ @staticmethod
+ def gateway_timeout(*args):
+ response_data = jsonify(ServiceErrorResponses._GATEWAY_TIMEOUT)
+ return make_response(response_data, ServiceErrorResponses.HTTP_STATUS_CODE_504)
```
The code above uses a mutex to make the Flask threads wait until the previous one finishes by using Flask's [before_request](https://flask.palletsprojects.com/en/2.0.x/api/#flask.Flask.before_request) and [teardown_request](https://flask.palletsprojects.com/en/2.0.x/api/#flask.Flask.teardown_request). The first one tries to acquire the lock within a 29s timeout (which is the same used in APIG) while the second one releases it. If a thread can't acquire the lock within the 29s interval it raises a `504 Bad gateway`.
There's a drawback to it, of course, if for some reason the lambda function times out the container doesn't flush some of the requests (I didn't look into it deeply but, it was what I could observe from my tests). It seems that _maybe_ the `invoke` hangs? Or Docker hangs? Well, and this is the part where it may not be feasible or some guidance is needed to move forward.
Thanks for reading thru this!
|
main
|
accept concurrent requests when using warm containers describe your idea feature enhancement when developing serving an api locally you may run into concurrent requests done by a browser and in macos specifically without the warm containers option enabled it s very hard to test an endpoint that renders html for example so with that in mind i d love to see concurrent requests being supported when using one of the warm containers options by looking at the repository code it seems that lambda runner invoke is not expecting concurrent requests while reading the stdout stream which causes the concurrent requests to fail as the stdout is b and not a valid json response i came across while searching about concurrency so feel free to close this one if the team understands that this is cause more problems than a solution proposal i d like to propose a way to accept concurrent requests in similar couldn t find a better word but it s far from similar how nginx and api gateway deals with requests by accepting n of them but since we have docker as a limiting factor processing it one at a time similar to having a rate of request s but with requests as a burst for example i came up with this patch for it diff diff git a samcli local apigw local apigw service py b samcli local apigw local apigw service py index a samcli local apigw local apigw service py b samcli local apigw local apigw service py import io import json import logging import import threading from typing import list optional from flask import flask request class localapigwservice baselocalservice self static dir static dir self dict of routes self stderr stderr self lock threading boundedsemaphore def create self class localapigwservice baselocalservice prevent the dev server from emitting headers that will make the browser cache response by default self app config self app before request self block concurrent requests self app teardown request self release request lock this will normalize all endpoints and strip any trailing self app url map strict slashes false default route none class localapigwservice baselocalservice self app register error handler serviceerrorresponses route not found something went wrong self app register error handler serviceerrorresponses lambda failure response self app register error handler serviceerrorresponses gateway timeout def request handler self kwargs class localapigwservice baselocalservice return request mimetype in binary types or in binary types def block concurrent requests self use the hard timeout of apig for integrations for each request acquired self lock acquire timeout if not acquired return serviceerrorresponses gateway timeout def release request lock self error none try self lock release except valueerror log debug tried to release more than it should diff git a samcli local apigw service error responses py b samcli local apigw service error responses py index a samcli local apigw service error responses py b samcli local apigw service error responses py class serviceerrorresponses no lambda integration message no function defined for resource method missing authentication message missing authentication token lambda failure message internal server error gateway timeout message gateway timeout http status code http status code http status code staticmethod def lambda failure response args class serviceerrorresponses response data jsonify serviceerrorresponses missing authentication return make response response data serviceerrorresponses http status code staticmethod def gateway timeout args response data jsonify serviceerrorresponses gateway timeout return make response response data serviceerrorresponses http status code the code above uses a mutex to make the flask threads wait until the previous one finishes by using flask s and the first one tries to acquire the lock within a timeout which is the same used in apig while the second one releases it if a thread can t acquire the lock within the interval it raises a bad gateway there s a drawback to it of course if for some reason the lambda function times out the container doesn t flush some of the requests i didn t look into it deeply but it was what i could observe from my tests it seems that maybe the invoke hangs or docker hangs well and this is the part where it may not be feasible or some guidance is needed to move forward thanks for reading thru this
| 1
|
209,691
| 23,730,762,667
|
IssuesEvent
|
2022-08-31 01:20:30
|
Gal-Doron/renovate-test
|
https://api.github.com/repos/Gal-Doron/renovate-test
|
closed
|
CVE-2021-44832 (Medium) detected in log4j-core-2.14.0.jar - autoclosed
|
security vulnerability
|
## CVE-2021-44832 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>log4j-core-2.14.0.jar</b></p></summary>
<p>The Apache Log4j Implementation</p>
<p>Library home page: <a href="https://logging.apache.org/log4j/2.x/">https://logging.apache.org/log4j/2.x/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /ository/org/apache/logging/log4j/log4j-core/2.14.0/log4j-core-2.14.0.jar</p>
<p>
Dependency Hierarchy:
- :x: **log4j-core-2.14.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Gal-Doron/renovate-test/commit/18ace59282ac46d518b94191200613dd4490868e">18ace59282ac46d518b94191200613dd4490868e</a></p>
<p>Found in base branch: <b>main</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>
Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to a remote code execution (RCE) attack when a configuration uses a JDBC Appender with a JNDI LDAP data source URI when an attacker has control of the target LDAP server. This issue is fixed by limiting JNDI data source names to the java protocol in Log4j2 versions 2.17.1, 2.12.4, and 2.3.2.
<p>Publish Date: 2021-12-28
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-44832>CVE-2021-44832</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: High
- 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://logging.apache.org/log4j/2.x/security.html">https://logging.apache.org/log4j/2.x/security.html</a></p>
<p>Release Date: 2021-12-28</p>
<p>Fix Resolution: 2.17.1</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
|
True
|
CVE-2021-44832 (Medium) detected in log4j-core-2.14.0.jar - autoclosed - ## CVE-2021-44832 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>log4j-core-2.14.0.jar</b></p></summary>
<p>The Apache Log4j Implementation</p>
<p>Library home page: <a href="https://logging.apache.org/log4j/2.x/">https://logging.apache.org/log4j/2.x/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /ository/org/apache/logging/log4j/log4j-core/2.14.0/log4j-core-2.14.0.jar</p>
<p>
Dependency Hierarchy:
- :x: **log4j-core-2.14.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Gal-Doron/renovate-test/commit/18ace59282ac46d518b94191200613dd4490868e">18ace59282ac46d518b94191200613dd4490868e</a></p>
<p>Found in base branch: <b>main</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>
Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to a remote code execution (RCE) attack when a configuration uses a JDBC Appender with a JNDI LDAP data source URI when an attacker has control of the target LDAP server. This issue is fixed by limiting JNDI data source names to the java protocol in Log4j2 versions 2.17.1, 2.12.4, and 2.3.2.
<p>Publish Date: 2021-12-28
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-44832>CVE-2021-44832</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: High
- 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://logging.apache.org/log4j/2.x/security.html">https://logging.apache.org/log4j/2.x/security.html</a></p>
<p>Release Date: 2021-12-28</p>
<p>Fix Resolution: 2.17.1</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
|
non_main
|
cve medium detected in core jar autoclosed cve medium severity vulnerability vulnerable library core jar the apache implementation library home page a href path to dependency file pom xml path to vulnerable library ository org apache logging core core jar dependency hierarchy x core jar vulnerable library found in head commit a href found in base branch main vulnerability details apache versions through excluding security fix releases and are vulnerable to a remote code execution rce attack when a configuration uses a jdbc appender with a jndi ldap data source uri when an attacker has control of the target ldap server this issue is fixed by limiting jndi data source names to the java protocol in versions and publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required high 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 rescue worker helmet automatic remediation is available for this issue
| 0
|
4,370
| 22,162,505,008
|
IssuesEvent
|
2022-06-04 18:09:57
|
Lissy93/dashy
|
https://api.github.com/repos/Lissy93/dashy
|
closed
|
[FEATURE_REQUEST] Extending visibility / permissions on items
|
🦄 Feature Request 👤 Awaiting Maintainer Response
|
### Is your feature request related to a problem? If so, please describe.
Currently, you can only use the `showForUsers` or `hideForUsers` option in the `displayData` section to hide / show specific sections to specific user. However, it could be helpful to also be able to hide specific `items`. E.g.: I want my users to see the login page for our VMWare vCenter, but i don't want them to see each ESXI Host on it's own (i sometimes have to get access to them, so they are stored with the vCenter in one big "VMWare" Section). 😊
### Describe the solution you'd like
I'd like to have a `hideForUsers`, `showForUsers` and `hideForGuests` option for each item i have in my Dashy Dashboard, so i can manage item visibility individually per item. 😊
### Priority
Medium (Would be very useful)
### Is this something you would be keen to implement
Maybe
|
True
|
[FEATURE_REQUEST] Extending visibility / permissions on items - ### Is your feature request related to a problem? If so, please describe.
Currently, you can only use the `showForUsers` or `hideForUsers` option in the `displayData` section to hide / show specific sections to specific user. However, it could be helpful to also be able to hide specific `items`. E.g.: I want my users to see the login page for our VMWare vCenter, but i don't want them to see each ESXI Host on it's own (i sometimes have to get access to them, so they are stored with the vCenter in one big "VMWare" Section). 😊
### Describe the solution you'd like
I'd like to have a `hideForUsers`, `showForUsers` and `hideForGuests` option for each item i have in my Dashy Dashboard, so i can manage item visibility individually per item. 😊
### Priority
Medium (Would be very useful)
### Is this something you would be keen to implement
Maybe
|
main
|
extending visibility permissions on items is your feature request related to a problem if so please describe currently you can only use the showforusers or hideforusers option in the displaydata section to hide show specific sections to specific user however it could be helpful to also be able to hide specific items e g i want my users to see the login page for our vmware vcenter but i don t want them to see each esxi host on it s own i sometimes have to get access to them so they are stored with the vcenter in one big vmware section 😊 describe the solution you d like i d like to have a hideforusers showforusers and hideforguests option for each item i have in my dashy dashboard so i can manage item visibility individually per item 😊 priority medium would be very useful is this something you would be keen to implement maybe
| 1
|
68,595
| 14,937,895,545
|
IssuesEvent
|
2021-01-25 15:09:31
|
minio/console
|
https://api.github.com/repos/minio/console
|
closed
|
How does authentication work after #535?
|
security
|
I just updated and noticed that in #535 the console user environment was removed and now I can no longer sign in to the Console — it comes back as 401 Unauthorized. I looked at the new README and tried adding a user called `console` with policy `consoleAdmin` as described but I still cannot sign in as any user or the newly added console. I can still sign in through the MinIO Browser and command-line client.
```
console version 0.5.0 - e7f220b
minio version RELEASE.2021-01-16T02-19-44Z
```
For some reason it seems like the `latest` tag for console on Docker Hub is still on 0.5.0 rather than the latest 0.5.1.
|
True
|
How does authentication work after #535? - I just updated and noticed that in #535 the console user environment was removed and now I can no longer sign in to the Console — it comes back as 401 Unauthorized. I looked at the new README and tried adding a user called `console` with policy `consoleAdmin` as described but I still cannot sign in as any user or the newly added console. I can still sign in through the MinIO Browser and command-line client.
```
console version 0.5.0 - e7f220b
minio version RELEASE.2021-01-16T02-19-44Z
```
For some reason it seems like the `latest` tag for console on Docker Hub is still on 0.5.0 rather than the latest 0.5.1.
|
non_main
|
how does authentication work after i just updated and noticed that in the console user environment was removed and now i can no longer sign in to the console — it comes back as unauthorized i looked at the new readme and tried adding a user called console with policy consoleadmin as described but i still cannot sign in as any user or the newly added console i can still sign in through the minio browser and command line client console version minio version release for some reason it seems like the latest tag for console on docker hub is still on rather than the latest
| 0
|
99,406
| 12,422,228,998
|
IssuesEvent
|
2020-05-23 20:57:02
|
Charcoal-SE/SmokeDetector
|
https://api.github.com/repos/Charcoal-SE/SmokeDetector
|
reopened
|
Reporting reasons are no longer being added as comments on MS
|
status: by design status: norepro
|
Recently, #2398 was implemented, which automatically adds reporting reasons (i.e. `!!/report [post link] "reporting reason"`) as a comment on the relevant metasmoke record for the post.
However, this seems to have broken at some point in the last month or two.
Can this please be fixed?
|
1.0
|
Reporting reasons are no longer being added as comments on MS - Recently, #2398 was implemented, which automatically adds reporting reasons (i.e. `!!/report [post link] "reporting reason"`) as a comment on the relevant metasmoke record for the post.
However, this seems to have broken at some point in the last month or two.
Can this please be fixed?
|
non_main
|
reporting reasons are no longer being added as comments on ms recently was implemented which automatically adds reporting reasons i e report reporting reason as a comment on the relevant metasmoke record for the post however this seems to have broken at some point in the last month or two can this please be fixed
| 0
|
352,382
| 25,064,733,336
|
IssuesEvent
|
2022-11-07 07:08:36
|
AY2223S1-CS2103-W14-2/tp
|
https://api.github.com/repos/AY2223S1-CS2103-W14-2/tp
|
closed
|
Improve DG
|
documentation
|
Improve DG grammar
Check for serious mistakes
Check American English spelling
|
1.0
|
Improve DG - Improve DG grammar
Check for serious mistakes
Check American English spelling
|
non_main
|
improve dg improve dg grammar check for serious mistakes check american english spelling
| 0
|
727,956
| 25,061,195,153
|
IssuesEvent
|
2022-11-07 01:57:34
|
FiniteLoop-NMAMIT/flc-website
|
https://api.github.com/repos/FiniteLoop-NMAMIT/flc-website
|
opened
|
tasks admin dashboard
|
enhancement help wanted low-priority
|
- create a new page /assign (protected route, only allowed to users with role === 'core')
- add a 'score' field to 'task' table (each task must have a score assigned)
- render a form (task description, assigning to a team etc) which will update the 'task' table on db
- use cases: to assign competitive coding questions, hackathon problem statements etc for scoring points
[As this can be alternatively done on prisma studio, we will consider this as a low-priority issue until other high-priority ones get solved]
|
1.0
|
tasks admin dashboard - - create a new page /assign (protected route, only allowed to users with role === 'core')
- add a 'score' field to 'task' table (each task must have a score assigned)
- render a form (task description, assigning to a team etc) which will update the 'task' table on db
- use cases: to assign competitive coding questions, hackathon problem statements etc for scoring points
[As this can be alternatively done on prisma studio, we will consider this as a low-priority issue until other high-priority ones get solved]
|
non_main
|
tasks admin dashboard create a new page assign protected route only allowed to users with role core add a score field to task table each task must have a score assigned render a form task description assigning to a team etc which will update the task table on db use cases to assign competitive coding questions hackathon problem statements etc for scoring points
| 0
|
682,598
| 23,349,397,790
|
IssuesEvent
|
2022-08-09 21:29:39
|
ucb-rit/coldfront
|
https://api.github.com/repos/ucb-rit/coldfront
|
closed
|
Write tests for cluster access request generation
|
mid priority
|
After #130, cluster access requests can be generated in a few ways:
1. A user requests to join a project and is manually approved,
2. A manager adds a user to a project,
3. A new project request is approved, and the requester is automatically added to the project, or
4. A PI requests access from the Project Detail view.
Write tests to ensure that these requests get generated in all of these cases, and that emails get sent to the right parties.
- In particular, test that a previously-removed user can re-join a project and regain cluster access.
|
1.0
|
Write tests for cluster access request generation - After #130, cluster access requests can be generated in a few ways:
1. A user requests to join a project and is manually approved,
2. A manager adds a user to a project,
3. A new project request is approved, and the requester is automatically added to the project, or
4. A PI requests access from the Project Detail view.
Write tests to ensure that these requests get generated in all of these cases, and that emails get sent to the right parties.
- In particular, test that a previously-removed user can re-join a project and regain cluster access.
|
non_main
|
write tests for cluster access request generation after cluster access requests can be generated in a few ways a user requests to join a project and is manually approved a manager adds a user to a project a new project request is approved and the requester is automatically added to the project or a pi requests access from the project detail view write tests to ensure that these requests get generated in all of these cases and that emails get sent to the right parties in particular test that a previously removed user can re join a project and regain cluster access
| 0
|
767,473
| 26,926,749,252
|
IssuesEvent
|
2023-02-07 14:18:01
|
epicmaxco/vuestic-ui
|
https://api.github.com/repos/epicmaxco/vuestic-ui
|
closed
|
Docs refresh
|
docs LOW PRIORITY
|
Updating docs is a bit problematic. As you can have update happen when user has page loaded.
If they try to navigate to some page - they might have an issue, as module might be not available anymore.
So we want to introduce some solution to make user interaction seamless.
Couple of ideas:
* keep multiple versions of bundle on server (let's say up to 24h), each in its own folder.
* sometimes send a request (to some json, where version is defined?) and if anything is changed (flags or version) - present user with update dialog similarly to what other docs use. This is not ideal as it requires action from user.
|
1.0
|
Docs refresh - Updating docs is a bit problematic. As you can have update happen when user has page loaded.
If they try to navigate to some page - they might have an issue, as module might be not available anymore.
So we want to introduce some solution to make user interaction seamless.
Couple of ideas:
* keep multiple versions of bundle on server (let's say up to 24h), each in its own folder.
* sometimes send a request (to some json, where version is defined?) and if anything is changed (flags or version) - present user with update dialog similarly to what other docs use. This is not ideal as it requires action from user.
|
non_main
|
docs refresh updating docs is a bit problematic as you can have update happen when user has page loaded if they try to navigate to some page they might have an issue as module might be not available anymore so we want to introduce some solution to make user interaction seamless couple of ideas keep multiple versions of bundle on server let s say up to each in its own folder sometimes send a request to some json where version is defined and if anything is changed flags or version present user with update dialog similarly to what other docs use this is not ideal as it requires action from user
| 0
|
184,645
| 14,986,345,196
|
IssuesEvent
|
2021-01-28 21:07:14
|
rdsaliba/notorious-eng
|
https://api.github.com/repos/rdsaliba/notorious-eng
|
closed
|
Doc R2 - Defect Tracking report
|
documentation
|
Acceptance Criteria:
- [x] Release 2 documentation for the Bug section
The release 2 document, as well as the release 2 template, are in the team's drive.
Feedback from release 1:
Only 1 bug report. This was a bug reported by SonarQube.
|
1.0
|
Doc R2 - Defect Tracking report - Acceptance Criteria:
- [x] Release 2 documentation for the Bug section
The release 2 document, as well as the release 2 template, are in the team's drive.
Feedback from release 1:
Only 1 bug report. This was a bug reported by SonarQube.
|
non_main
|
doc defect tracking report acceptance criteria release documentation for the bug section the release document as well as the release template are in the team s drive feedback from release only bug report this was a bug reported by sonarqube
| 0
|
156,257
| 24,589,277,614
|
IssuesEvent
|
2022-10-13 23:29:08
|
wwcodecolorado/scrollodex
|
https://api.github.com/repos/wwcodecolorado/scrollodex
|
opened
|
Address skipped heading level
|
Hacktoberfest design a11y
|
#### Description
The project currently skips from H1 to and H3. This does not meet WCAG and could causing a confusing navigation for screenreader users.
#### How to visualize page structure with Wave
1. install wave web accessibility evaluation tool browser extension
2. run tool (on Mac `cmd + shift + u`)
3. within summary sidebar, select structure tab
4. Note the Orange alert concerning skipped heading level
#### Screenshot(s)
#### Tasks
- [ ] Address the skipped heading level
- [ ] Ensure fix does not change styling
#### Resources
[Deque Heading Order](https://dequeuniversity.com/rules/axe/4.4/heading-order)
|
1.0
|
Address skipped heading level - #### Description
The project currently skips from H1 to and H3. This does not meet WCAG and could causing a confusing navigation for screenreader users.
#### How to visualize page structure with Wave
1. install wave web accessibility evaluation tool browser extension
2. run tool (on Mac `cmd + shift + u`)
3. within summary sidebar, select structure tab
4. Note the Orange alert concerning skipped heading level
#### Screenshot(s)
#### Tasks
- [ ] Address the skipped heading level
- [ ] Ensure fix does not change styling
#### Resources
[Deque Heading Order](https://dequeuniversity.com/rules/axe/4.4/heading-order)
|
non_main
|
address skipped heading level description the project currently skips from to and this does not meet wcag and could causing a confusing navigation for screenreader users how to visualize page structure with wave install wave web accessibility evaluation tool browser extension run tool on mac cmd shift u within summary sidebar select structure tab note the orange alert concerning skipped heading level screenshot s tasks address the skipped heading level ensure fix does not change styling resources
| 0
|
64,231
| 15,828,262,142
|
IssuesEvent
|
2021-04-06 09:40:10
|
spack/spack
|
https://api.github.com/repos/spack/spack
|
opened
|
Install and compile fastjson@1.2.73: package com.alibaba.json.bvtVO.???????? does not exist
|
build-error
|
see:
```console
localhost:~ # spack install --keep-stage -v fastjson
[+] /home/spack/opt/spack/linux-sles15-aarch64/gcc-7.4.0/openjdk-1.8.0_191-b12-efygw4r7e2ocitlwttcp2yn6beizzz5c
[+] /home/spack/opt/spack/linux-sles15-aarch64/gcc-7.4.0/maven-3.6.3-nlllqprafuwb2ob66z6e2edp6nlsbvnx
==> Installing fastjson-1.2.76-z7mzhzejy3apulb24jqt6oqixpvlqkwv
==> No binary for fastjson-1.2.76-z7mzhzejy3apulb24jqt6oqixpvlqkwv found: installing from source
==> Using cached archive: /home/spack/var/spack/cache/_source-cache/archive/c7/c707eb3d3c809c30051583e46a38e9dc06c8941219161bd1bb7a9d6bb6ad1fbf.tar.gz
==> fastjson: Executing phase: 'build'
==> [2021-04-06-17:37:57.253972] '/home/spack/opt/spack/linux-sles15-aarch64/gcc-7.4.0/maven-3.6.3-nlllqprafuwb2ob66z6e2edp6nlsbvnx/bin/mvn' 'package' '-DskipTests'
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------< com.alibaba:fastjson >------------------------
[INFO] Building fastjson 1.2.76
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ fastjson ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 6 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @ fastjson ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 190 source files to /home/stage/root/spack-stage-fastjson-1.2.76-z7mzhzejy3apulb24jqt6oqixpvlqkwv/spack-src/target/classes
[INFO] /home/stage/root/spack-stage-fastjson-1.2.76-z7mzhzejy3apulb24jqt6oqixpvlqkwv/spack-src/src/main/java/com/alibaba/fastjson/util/TypeUtils.java: Some input files use or override a deprecated API.
[INFO] /home/stage/root/spack-stage-fastjson-1.2.76-z7mzhzejy3apulb24jqt6oqixpvlqkwv/spack-src/src/main/java/com/alibaba/fastjson/util/TypeUtils.java: Recompile with -Xlint:deprecation for details.
[INFO] /home/stage/root/spack-stage-fastjson-1.2.76-z7mzhzejy3apulb24jqt6oqixpvlqkwv/spack-src/src/main/java/com/alibaba/fastjson/parser/DefaultJSONParser.java: Some input files use unchecked or unsafe operations.
[INFO] /home/stage/root/spack-stage-fastjson-1.2.76-z7mzhzejy3apulb24jqt6oqixpvlqkwv/spack-src/src/main/java/com/alibaba/fastjson/parser/DefaultJSONParser.java: Recompile with -Xlint:unchecked for details.
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ fastjson ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 98 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.0:testCompile (default-testCompile) @ fastjson ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 2806 source files to /home/stage/root/spack-stage-fastjson-1.2.76-z7mzhzejy3apulb24jqt6oqixpvlqkwv/spack-src/target/test-classes
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /home/stage/root/spack-stage-fastjson-1.2.76-z7mzhzejy3apulb24jqt6oqixpvlqkwv/spack-src/src/test/java/com/alibaba/json/bvt/issue_3100/Issue3132.java:[4,39] package com.alibaba.json.bvtVO.???????? does not exist
[INFO] 1 error
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 17.871 s
[INFO] Finished at: 2021-04-06T17:38:16+08:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:testCompile (default-testCompile) on project fastjson: Compilation failure
[ERROR] /home/stage/root/spack-stage-fastjson-1.2.76-z7mzhzejy3apulb24jqt6oqixpvlqkwv/spack-src/src/test/java/com/alibaba/json/bvt/issue_3100/Issue3132.java:[4,39] package com.alibaba.json.bvtVO.???????? does not exist
[ERROR]
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
==> Error: ProcessError: Command exited with status 1:
'/home/spack/opt/spack/linux-sles15-aarch64/gcc-7.4.0/maven-3.6.3-nlllqprafuwb2ob66z6e2edp6nlsbvnx/bin/mvn' 'package' '-DskipTests'
12 errors found in build log:
23 [INFO] Copying 98 resources
24 [INFO]
25 [INFO] --- maven-compiler-plugin:3.8.0:testCompile (default-testCompile) @ fastjson ---
26 [INFO] Changes detected - recompiling the module!
27 [INFO] Compiling 2806 source files to /home/stage/root/spack-stage-fastjson-1.2.76-z7mzhzejy3apulb24jqt6oqixpvlqkwv/spack-src/target/test-classes
28 [INFO] -------------------------------------------------------------
>> 29 [ERROR] COMPILATION ERROR :
30 [INFO] -------------------------------------------------------------
>> 31 [ERROR] /home/stage/root/spack-stage-fastjson-1.2.76-z7mzhzejy3apulb24jqt6oqixpvlqkwv/spack-src/src/test/java/com/alibaba/json/bvt/issue_3100/Issue3132.java:[4,39] package com.alibab
a.json.bvtVO.???????? does not exist
32 [INFO] 1 error
33 [INFO] -------------------------------------------------------------
34 [INFO] ------------------------------------------------------------------------
35 [INFO] BUILD FAILURE
36 [INFO] ------------------------------------------------------------------------
37 [INFO] Total time: 17.871 s
38 [INFO] Finished at: 2021-04-06T17:38:16+08:00
39 [INFO] ------------------------------------------------------------------------
>> 40 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:testCompile (default-testCompile) on project fastjson: Compilation failure
>> 41 [ERROR] /home/stage/root/spack-stage-fastjson-1.2.76-z7mzhzejy3apulb24jqt6oqixpvlqkwv/spack-src/src/test/java/com/alibaba/json/bvt/issue_3100/Issue3132.java:[4,39] package com.alibab
a.json.bvtVO.???????? does not exist
>> 42 [ERROR]
>> 43 [ERROR] -> [Help 1]
>> 44 [ERROR]
>> 45 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
>> 46 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> 47 [ERROR]
>> 48 [ERROR] For more information about the errors and possible solutions, please read the following articles:
>> 49 [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
See build log for details:
/home/stage/root/spack-stage-fastjson-1.2.76-z7mzhzejy3apulb24jqt6oqixpvlqkwv/spack-build-out.txt
```
When I install and compile fastjson@1.2.73 in the sppack, an error occurs: package com.alibaba.json.bvtVO.???????? does not exist. What can I do?
### Information on your system
localhost:~ # spack debug report
* **Spack:** 0.16.0-77-98460b6f4
* **Python:** 3.6.5
* **Platform:** linux-sles15-aarch64
* **Concretizer:** original
<!-- Please include the output of `spack debug report` -->
<!-- If you have any relevant configuration detail (custom `packages.yaml` or `modules.yaml`, etc.) you can add that here as well. -->
|
1.0
|
Install and compile fastjson@1.2.73: package com.alibaba.json.bvtVO.???????? does not exist - see:
```console
localhost:~ # spack install --keep-stage -v fastjson
[+] /home/spack/opt/spack/linux-sles15-aarch64/gcc-7.4.0/openjdk-1.8.0_191-b12-efygw4r7e2ocitlwttcp2yn6beizzz5c
[+] /home/spack/opt/spack/linux-sles15-aarch64/gcc-7.4.0/maven-3.6.3-nlllqprafuwb2ob66z6e2edp6nlsbvnx
==> Installing fastjson-1.2.76-z7mzhzejy3apulb24jqt6oqixpvlqkwv
==> No binary for fastjson-1.2.76-z7mzhzejy3apulb24jqt6oqixpvlqkwv found: installing from source
==> Using cached archive: /home/spack/var/spack/cache/_source-cache/archive/c7/c707eb3d3c809c30051583e46a38e9dc06c8941219161bd1bb7a9d6bb6ad1fbf.tar.gz
==> fastjson: Executing phase: 'build'
==> [2021-04-06-17:37:57.253972] '/home/spack/opt/spack/linux-sles15-aarch64/gcc-7.4.0/maven-3.6.3-nlllqprafuwb2ob66z6e2edp6nlsbvnx/bin/mvn' 'package' '-DskipTests'
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------< com.alibaba:fastjson >------------------------
[INFO] Building fastjson 1.2.76
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ fastjson ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 6 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @ fastjson ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 190 source files to /home/stage/root/spack-stage-fastjson-1.2.76-z7mzhzejy3apulb24jqt6oqixpvlqkwv/spack-src/target/classes
[INFO] /home/stage/root/spack-stage-fastjson-1.2.76-z7mzhzejy3apulb24jqt6oqixpvlqkwv/spack-src/src/main/java/com/alibaba/fastjson/util/TypeUtils.java: Some input files use or override a deprecated API.
[INFO] /home/stage/root/spack-stage-fastjson-1.2.76-z7mzhzejy3apulb24jqt6oqixpvlqkwv/spack-src/src/main/java/com/alibaba/fastjson/util/TypeUtils.java: Recompile with -Xlint:deprecation for details.
[INFO] /home/stage/root/spack-stage-fastjson-1.2.76-z7mzhzejy3apulb24jqt6oqixpvlqkwv/spack-src/src/main/java/com/alibaba/fastjson/parser/DefaultJSONParser.java: Some input files use unchecked or unsafe operations.
[INFO] /home/stage/root/spack-stage-fastjson-1.2.76-z7mzhzejy3apulb24jqt6oqixpvlqkwv/spack-src/src/main/java/com/alibaba/fastjson/parser/DefaultJSONParser.java: Recompile with -Xlint:unchecked for details.
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ fastjson ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 98 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.0:testCompile (default-testCompile) @ fastjson ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 2806 source files to /home/stage/root/spack-stage-fastjson-1.2.76-z7mzhzejy3apulb24jqt6oqixpvlqkwv/spack-src/target/test-classes
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /home/stage/root/spack-stage-fastjson-1.2.76-z7mzhzejy3apulb24jqt6oqixpvlqkwv/spack-src/src/test/java/com/alibaba/json/bvt/issue_3100/Issue3132.java:[4,39] package com.alibaba.json.bvtVO.???????? does not exist
[INFO] 1 error
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 17.871 s
[INFO] Finished at: 2021-04-06T17:38:16+08:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:testCompile (default-testCompile) on project fastjson: Compilation failure
[ERROR] /home/stage/root/spack-stage-fastjson-1.2.76-z7mzhzejy3apulb24jqt6oqixpvlqkwv/spack-src/src/test/java/com/alibaba/json/bvt/issue_3100/Issue3132.java:[4,39] package com.alibaba.json.bvtVO.???????? does not exist
[ERROR]
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
==> Error: ProcessError: Command exited with status 1:
'/home/spack/opt/spack/linux-sles15-aarch64/gcc-7.4.0/maven-3.6.3-nlllqprafuwb2ob66z6e2edp6nlsbvnx/bin/mvn' 'package' '-DskipTests'
12 errors found in build log:
23 [INFO] Copying 98 resources
24 [INFO]
25 [INFO] --- maven-compiler-plugin:3.8.0:testCompile (default-testCompile) @ fastjson ---
26 [INFO] Changes detected - recompiling the module!
27 [INFO] Compiling 2806 source files to /home/stage/root/spack-stage-fastjson-1.2.76-z7mzhzejy3apulb24jqt6oqixpvlqkwv/spack-src/target/test-classes
28 [INFO] -------------------------------------------------------------
>> 29 [ERROR] COMPILATION ERROR :
30 [INFO] -------------------------------------------------------------
>> 31 [ERROR] /home/stage/root/spack-stage-fastjson-1.2.76-z7mzhzejy3apulb24jqt6oqixpvlqkwv/spack-src/src/test/java/com/alibaba/json/bvt/issue_3100/Issue3132.java:[4,39] package com.alibab
a.json.bvtVO.???????? does not exist
32 [INFO] 1 error
33 [INFO] -------------------------------------------------------------
34 [INFO] ------------------------------------------------------------------------
35 [INFO] BUILD FAILURE
36 [INFO] ------------------------------------------------------------------------
37 [INFO] Total time: 17.871 s
38 [INFO] Finished at: 2021-04-06T17:38:16+08:00
39 [INFO] ------------------------------------------------------------------------
>> 40 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:testCompile (default-testCompile) on project fastjson: Compilation failure
>> 41 [ERROR] /home/stage/root/spack-stage-fastjson-1.2.76-z7mzhzejy3apulb24jqt6oqixpvlqkwv/spack-src/src/test/java/com/alibaba/json/bvt/issue_3100/Issue3132.java:[4,39] package com.alibab
a.json.bvtVO.???????? does not exist
>> 42 [ERROR]
>> 43 [ERROR] -> [Help 1]
>> 44 [ERROR]
>> 45 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
>> 46 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> 47 [ERROR]
>> 48 [ERROR] For more information about the errors and possible solutions, please read the following articles:
>> 49 [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
See build log for details:
/home/stage/root/spack-stage-fastjson-1.2.76-z7mzhzejy3apulb24jqt6oqixpvlqkwv/spack-build-out.txt
```
When I install and compile fastjson@1.2.73 in the sppack, an error occurs: package com.alibaba.json.bvtVO.???????? does not exist. What can I do?
### Information on your system
localhost:~ # spack debug report
* **Spack:** 0.16.0-77-98460b6f4
* **Python:** 3.6.5
* **Platform:** linux-sles15-aarch64
* **Concretizer:** original
<!-- Please include the output of `spack debug report` -->
<!-- If you have any relevant configuration detail (custom `packages.yaml` or `modules.yaml`, etc.) you can add that here as well. -->
|
non_main
|
install and compile fastjson package com alibaba json bvtvo does not exist see console localhost spack install keep stage v fastjson home spack opt spack linux gcc openjdk home spack opt spack linux gcc maven installing fastjson no binary for fastjson found installing from source using cached archive home spack var spack cache source cache archive tar gz fastjson executing phase build home spack opt spack linux gcc maven bin mvn package dskiptests scanning for projects building fastjson maven resources plugin resources default resources fastjson using utf encoding to copy filtered resources copying resources maven compiler plugin compile default compile fastjson changes detected recompiling the module compiling source files to home stage root spack stage fastjson spack src target classes home stage root spack stage fastjson spack src src main java com alibaba fastjson util typeutils java some input files use or override a deprecated api home stage root spack stage fastjson spack src src main java com alibaba fastjson util typeutils java recompile with xlint deprecation for details home stage root spack stage fastjson spack src src main java com alibaba fastjson parser defaultjsonparser java some input files use unchecked or unsafe operations home stage root spack stage fastjson spack src src main java com alibaba fastjson parser defaultjsonparser java recompile with xlint unchecked for details maven resources plugin testresources default testresources fastjson using utf encoding to copy filtered resources copying resources maven compiler plugin testcompile default testcompile fastjson changes detected recompiling the module compiling source files to home stage root spack stage fastjson spack src target test classes compilation error home stage root spack stage fastjson spack src src test java com alibaba json bvt issue java package com alibaba json bvtvo does not exist error build failure total time s finished at failed to execute goal org apache maven plugins maven compiler plugin testcompile default testcompile on project fastjson compilation failure home stage root spack stage fastjson spack src src test java com alibaba json bvt issue java package com alibaba json bvtvo does not exist to see the full stack trace of the errors re run maven with the e switch re run maven using the x switch to enable full debug logging for more information about the errors and possible solutions please read the following articles error processerror command exited with status home spack opt spack linux gcc maven bin mvn package dskiptests errors found in build log copying resources maven compiler plugin testcompile default testcompile fastjson changes detected recompiling the module compiling source files to home stage root spack stage fastjson spack src target test classes compilation error home stage root spack stage fastjson spack src src test java com alibaba json bvt issue java package com alibab a json bvtvo does not exist error build failure total time s finished at failed to execute goal org apache maven plugins maven compiler plugin testcompile default testcompile on project fastjson compilation failure home stage root spack stage fastjson spack src src test java com alibaba json bvt issue java package com alibab a json bvtvo does not exist to see the full stack trace of the errors re run maven with the e switch re run maven using the x switch to enable full debug logging for more information about the errors and possible solutions please read the following articles see build log for details home stage root spack stage fastjson spack build out txt when i install and compile fastjson in the sppack an error occurs package com alibaba json bvtvo does not exist what can i do information on your system localhost spack debug report spack python platform linux concretizer original
| 0
|
5,016
| 25,765,690,564
|
IssuesEvent
|
2022-12-09 01:30:24
|
aws/serverless-application-model
|
https://api.github.com/repos/aws/serverless-application-model
|
closed
|
Run cfn-lint on test outputs without causing circular dependency
|
type/feature maintainer/need-response
|
**Description:**
Adding in cfn-lint as a test dependency caused dependency issues as noted in #1008. We are removing cfn-lint as a dependency in #1034, but it can be a valuable testing tool.
I'm opening this issue to track adding it back in such a way that it does not cause circular dependency issues and allows us to use it as part of our testing suite.
|
True
|
Run cfn-lint on test outputs without causing circular dependency - **Description:**
Adding in cfn-lint as a test dependency caused dependency issues as noted in #1008. We are removing cfn-lint as a dependency in #1034, but it can be a valuable testing tool.
I'm opening this issue to track adding it back in such a way that it does not cause circular dependency issues and allows us to use it as part of our testing suite.
|
main
|
run cfn lint on test outputs without causing circular dependency description adding in cfn lint as a test dependency caused dependency issues as noted in we are removing cfn lint as a dependency in but it can be a valuable testing tool i m opening this issue to track adding it back in such a way that it does not cause circular dependency issues and allows us to use it as part of our testing suite
| 1
|
2,927
| 3,252,939,668
|
IssuesEvent
|
2015-10-19 16:53:45
|
tgstation/-tg-station
|
https://api.github.com/repos/tgstation/-tg-station
|
closed
|
Slime processor annoying mass clicking
|
Feature Request Not a bug Usability
|
When you're grinding slimes, if you have steroided them, and upgraded the processor you have a million slime cores you need to manually click into the fridge, and its really annoying since you go through a lot of slimes in xenobio. There should be a way to like set the processor to autofeed to an adjacent fridge so you don't need to click
|
True
|
Slime processor annoying mass clicking - When you're grinding slimes, if you have steroided them, and upgraded the processor you have a million slime cores you need to manually click into the fridge, and its really annoying since you go through a lot of slimes in xenobio. There should be a way to like set the processor to autofeed to an adjacent fridge so you don't need to click
|
non_main
|
slime processor annoying mass clicking when you re grinding slimes if you have steroided them and upgraded the processor you have a million slime cores you need to manually click into the fridge and its really annoying since you go through a lot of slimes in xenobio there should be a way to like set the processor to autofeed to an adjacent fridge so you don t need to click
| 0
|
1,283
| 5,429,649,809
|
IssuesEvent
|
2017-03-03 19:00:57
|
duckduckgo/zeroclickinfo-goodies
|
https://api.github.com/repos/duckduckgo/zeroclickinfo-goodies
|
closed
|
USPS: Triggering on iOS error code: 18446744073709550611
|
Maintainer Input Requested
|
https://duckduckgo.com/?q=18446744073709550611&t=ffab&ia=answer
## Shows USPS tracking IA which takes you to an invalid tracking number page. The number is an NSURLErrorDomain code for iOS.
IA Page: http://duck.co/ia/view/usps
[Maintainer](http://docs.duckduckhack.com/maintaining/guidelines.html): @jagtalon
|
True
|
USPS: Triggering on iOS error code: 18446744073709550611 - https://duckduckgo.com/?q=18446744073709550611&t=ffab&ia=answer
## Shows USPS tracking IA which takes you to an invalid tracking number page. The number is an NSURLErrorDomain code for iOS.
IA Page: http://duck.co/ia/view/usps
[Maintainer](http://docs.duckduckhack.com/maintaining/guidelines.html): @jagtalon
|
main
|
usps triggering on ios error code shows usps tracking ia which takes you to an invalid tracking number page the number is an nsurlerrordomain code for ios ia page jagtalon
| 1
|
130,833
| 5,134,054,025
|
IssuesEvent
|
2017-01-11 07:20:49
|
ObjectiveSubject/cgu
|
https://api.github.com/repos/ObjectiveSubject/cgu
|
closed
|
Gap between modules.
|
2 hrs enhancement Low Priority
|
@kpettinga Had a look in WP as I thought there might have been a content issue. But there's a gap between two modules in Chrome. See screenshot.
http://cgu.wpengine.com/school/drucker-school-of-management/research/
http://cgu.wpengine.com/school/institute-of-mathematical-sciences/
http://cgu.wpengine.com/school/school-of-community-and-global-health/
|
1.0
|
Gap between modules. - @kpettinga Had a look in WP as I thought there might have been a content issue. But there's a gap between two modules in Chrome. See screenshot.
http://cgu.wpengine.com/school/drucker-school-of-management/research/
http://cgu.wpengine.com/school/institute-of-mathematical-sciences/
http://cgu.wpengine.com/school/school-of-community-and-global-health/
|
non_main
|
gap between modules kpettinga had a look in wp as i thought there might have been a content issue but there s a gap between two modules in chrome see screenshot
| 0
|
15,730
| 3,481,443,235
|
IssuesEvent
|
2015-12-29 16:11:06
|
slivne/try_git
|
https://api.github.com/repos/slivne/try_git
|
opened
|
repair : repair_fixes_updates_to_cells_test
|
dtest repair
|
Check that repair fixes a few update to cells contents 1. Create a cluster of 2 nodes with rf=2, disable read_repair, hinttef_handoff 2. Insert data 3. Shutdown node 2 4. Update some cells 5. Start node 2 6. Run repair on node 2 7. Shutdown node 1 - check that all data exists on node 2
|
1.0
|
repair : repair_fixes_updates_to_cells_test - Check that repair fixes a few update to cells contents 1. Create a cluster of 2 nodes with rf=2, disable read_repair, hinttef_handoff 2. Insert data 3. Shutdown node 2 4. Update some cells 5. Start node 2 6. Run repair on node 2 7. Shutdown node 1 - check that all data exists on node 2
|
non_main
|
repair repair fixes updates to cells test check that repair fixes a few update to cells contents create a cluster of nodes with rf disable read repair hinttef handoff insert data shutdown node update some cells start node run repair on node shutdown node check that all data exists on node
| 0
|
2,366
| 8,459,848,645
|
IssuesEvent
|
2018-10-22 17:06:14
|
invertase/react-native-firebase
|
https://api.github.com/repos/invertase/react-native-firebase
|
closed
|
W/FirebaseMessaging: Error while parsing timestamp in GCM event
|
await-maintainer-feedback firebase-issue notifications
|
When the app is on foreground no notification is shown...
The logcat shows me this:
```
W/FirebaseMessaging: Error while parsing timestamp in GCM event
java.lang.NumberFormatException: s == null
at java.lang.Integer.parseInt(Integer.java:570)
at java.lang.Integer.parseInt(Integer.java:643)
at com.google.firebase.messaging.zzb.zzc(Unknown Source:81)
at com.google.firebase.messaging.zzb.zze(Unknown Source:2)
at com.google.firebase.messaging.FirebaseMessagingService.zzd(Unknown Source:280)
at com.google.firebase.iid.zzc.run(Unknown Source:4)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at com.google.android.gms.common.util.concurrent.zza.run(Unknown Source:7)
at java.lang.Thread.run(Thread.java:764)
```
On background works well...
This is and example of the notification send:
```json
{
"to":"token",
"notification" : {
"title":"Su requerimiento numero WSXQWE/2018 esta siento atendido",
"body" : "Nuestras areas operativas estan trabajando en su requerimiento"
},
"data":{
"accion":"detalle_requerimiento",
"data":17
},
"priority": "high"
}
```
|
True
|
W/FirebaseMessaging: Error while parsing timestamp in GCM event - When the app is on foreground no notification is shown...
The logcat shows me this:
```
W/FirebaseMessaging: Error while parsing timestamp in GCM event
java.lang.NumberFormatException: s == null
at java.lang.Integer.parseInt(Integer.java:570)
at java.lang.Integer.parseInt(Integer.java:643)
at com.google.firebase.messaging.zzb.zzc(Unknown Source:81)
at com.google.firebase.messaging.zzb.zze(Unknown Source:2)
at com.google.firebase.messaging.FirebaseMessagingService.zzd(Unknown Source:280)
at com.google.firebase.iid.zzc.run(Unknown Source:4)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at com.google.android.gms.common.util.concurrent.zza.run(Unknown Source:7)
at java.lang.Thread.run(Thread.java:764)
```
On background works well...
This is and example of the notification send:
```json
{
"to":"token",
"notification" : {
"title":"Su requerimiento numero WSXQWE/2018 esta siento atendido",
"body" : "Nuestras areas operativas estan trabajando en su requerimiento"
},
"data":{
"accion":"detalle_requerimiento",
"data":17
},
"priority": "high"
}
```
|
main
|
w firebasemessaging error while parsing timestamp in gcm event when the app is on foreground no notification is shown the logcat shows me this w firebasemessaging error while parsing timestamp in gcm event java lang numberformatexception s null at java lang integer parseint integer java at java lang integer parseint integer java at com google firebase messaging zzb zzc unknown source at com google firebase messaging zzb zze unknown source at com google firebase messaging firebasemessagingservice zzd unknown source at com google firebase iid zzc run unknown source at java util concurrent threadpoolexecutor runworker threadpoolexecutor java at java util concurrent threadpoolexecutor worker run threadpoolexecutor java at com google android gms common util concurrent zza run unknown source at java lang thread run thread java on background works well this is and example of the notification send json to token notification title su requerimiento numero wsxqwe esta siento atendido body nuestras areas operativas estan trabajando en su requerimiento data accion detalle requerimiento data priority high
| 1
|
150,744
| 19,618,706,164
|
IssuesEvent
|
2022-01-07 01:36:52
|
ibm-cio-vulnerability-scanning/insomnia
|
https://api.github.com/repos/ibm-cio-vulnerability-scanning/insomnia
|
opened
|
CVE-2021-35065 (High) detected in multiple libraries
|
security vulnerability
|
## CVE-2021-35065 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>glob-parent-5.1.2.tgz</b>, <b>glob-parent-2.0.0.tgz</b>, <b>glob-parent-5.1.1.tgz</b>, <b>glob-parent-3.1.0.tgz</b></p></summary>
<p>
<details><summary><b>glob-parent-5.1.2.tgz</b></p></summary>
<p>Extract the non-magic parent path from a glob string.</p>
<p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/markdownlint-cli2/node_modules/glob-parent/package.json,/packages/insomnia-components/node_modules/fast-glob/node_modules/glob-parent/package.json,/packages/insomnia-components/node_modules/@storybook/core-common/node_modules/glob-parent/package.json,/node_modules/@typescript-eslint/typescript-estree/node_modules/glob-parent/package.json,/node_modules/eslint/node_modules/glob-parent/package.json</p>
<p>
Dependency Hierarchy:
- react-6.2.9.tgz (Root Library)
- react-dev-utils-11.0.4.tgz
- globby-11.0.1.tgz
- fast-glob-3.2.5.tgz
- :x: **glob-parent-5.1.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>glob-parent-2.0.0.tgz</b></p></summary>
<p>Strips glob magic from a string to provide the parent path</p>
<p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-2.0.0.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-2.0.0.tgz</a></p>
<p>Path to dependency file: /packages/insomnia-components/package.json</p>
<p>Path to vulnerable library: /packages/insomnia-components/node_modules/glob-base/node_modules/glob-parent/package.json</p>
<p>
Dependency Hierarchy:
- react-6.2.9.tgz (Root Library)
- core-common-6.2.9.tgz
- glob-base-0.3.0.tgz
- :x: **glob-parent-2.0.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>glob-parent-5.1.1.tgz</b></p></summary>
<p>Extract the non-magic parent path from a glob string.</p>
<p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.1.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/@lerna/project/node_modules/glob-parent/package.json,/packages/insomnia-components/node_modules/watchpack/node_modules/glob-parent/package.json,/packages/insomnia-inso/node_modules/glob-parent/package.json,/packages/insomnia-testing/node_modules/glob-parent/package.json</p>
<p>
Dependency Hierarchy:
- lerna-3.22.1.tgz (Root Library)
- link-3.21.0.tgz
- command-3.21.0.tgz
- project-3.21.0.tgz
- :x: **glob-parent-5.1.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>glob-parent-3.1.0.tgz</b></p></summary>
<p>Strips glob magic from a string to provide the parent directory path</p>
<p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz</a></p>
<p>
Dependency Hierarchy:
- webpack-4.43.0.tgz (Root Library)
- watchpack-1.7.2.tgz
- watchpack-chokidar2-2.0.0.tgz
- chokidar-2.1.8.tgz
- :x: **glob-parent-3.1.0.tgz** (Vulnerable Library)
</details>
<p>Found in base branch: <b>develop</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>
The package glob-parent before 6.0.1 are vulnerable to Regular Expression Denial of Service (ReDoS)
<p>Publish Date: 2021-06-22
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-35065>CVE-2021-35065</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://github.com/gulpjs/glob-parent/pull/49">https://github.com/gulpjs/glob-parent/pull/49</a></p>
<p>Release Date: 2021-06-22</p>
<p>Fix Resolution: glob-parent - 6.0.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2021-35065 (High) detected in multiple libraries - ## CVE-2021-35065 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>glob-parent-5.1.2.tgz</b>, <b>glob-parent-2.0.0.tgz</b>, <b>glob-parent-5.1.1.tgz</b>, <b>glob-parent-3.1.0.tgz</b></p></summary>
<p>
<details><summary><b>glob-parent-5.1.2.tgz</b></p></summary>
<p>Extract the non-magic parent path from a glob string.</p>
<p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/markdownlint-cli2/node_modules/glob-parent/package.json,/packages/insomnia-components/node_modules/fast-glob/node_modules/glob-parent/package.json,/packages/insomnia-components/node_modules/@storybook/core-common/node_modules/glob-parent/package.json,/node_modules/@typescript-eslint/typescript-estree/node_modules/glob-parent/package.json,/node_modules/eslint/node_modules/glob-parent/package.json</p>
<p>
Dependency Hierarchy:
- react-6.2.9.tgz (Root Library)
- react-dev-utils-11.0.4.tgz
- globby-11.0.1.tgz
- fast-glob-3.2.5.tgz
- :x: **glob-parent-5.1.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>glob-parent-2.0.0.tgz</b></p></summary>
<p>Strips glob magic from a string to provide the parent path</p>
<p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-2.0.0.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-2.0.0.tgz</a></p>
<p>Path to dependency file: /packages/insomnia-components/package.json</p>
<p>Path to vulnerable library: /packages/insomnia-components/node_modules/glob-base/node_modules/glob-parent/package.json</p>
<p>
Dependency Hierarchy:
- react-6.2.9.tgz (Root Library)
- core-common-6.2.9.tgz
- glob-base-0.3.0.tgz
- :x: **glob-parent-2.0.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>glob-parent-5.1.1.tgz</b></p></summary>
<p>Extract the non-magic parent path from a glob string.</p>
<p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.1.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/@lerna/project/node_modules/glob-parent/package.json,/packages/insomnia-components/node_modules/watchpack/node_modules/glob-parent/package.json,/packages/insomnia-inso/node_modules/glob-parent/package.json,/packages/insomnia-testing/node_modules/glob-parent/package.json</p>
<p>
Dependency Hierarchy:
- lerna-3.22.1.tgz (Root Library)
- link-3.21.0.tgz
- command-3.21.0.tgz
- project-3.21.0.tgz
- :x: **glob-parent-5.1.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>glob-parent-3.1.0.tgz</b></p></summary>
<p>Strips glob magic from a string to provide the parent directory path</p>
<p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz</a></p>
<p>
Dependency Hierarchy:
- webpack-4.43.0.tgz (Root Library)
- watchpack-1.7.2.tgz
- watchpack-chokidar2-2.0.0.tgz
- chokidar-2.1.8.tgz
- :x: **glob-parent-3.1.0.tgz** (Vulnerable Library)
</details>
<p>Found in base branch: <b>develop</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>
The package glob-parent before 6.0.1 are vulnerable to Regular Expression Denial of Service (ReDoS)
<p>Publish Date: 2021-06-22
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-35065>CVE-2021-35065</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://github.com/gulpjs/glob-parent/pull/49">https://github.com/gulpjs/glob-parent/pull/49</a></p>
<p>Release Date: 2021-06-22</p>
<p>Fix Resolution: glob-parent - 6.0.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_main
|
cve high detected in multiple libraries cve high severity vulnerability vulnerable libraries glob parent tgz glob parent tgz glob parent tgz glob parent tgz glob parent tgz extract the non magic parent path from a glob string library home page a href path to dependency file package json path to vulnerable library node modules markdownlint node modules glob parent package json packages insomnia components node modules fast glob node modules glob parent package json packages insomnia components node modules storybook core common node modules glob parent package json node modules typescript eslint typescript estree node modules glob parent package json node modules eslint node modules glob parent package json dependency hierarchy react tgz root library react dev utils tgz globby tgz fast glob tgz x glob parent tgz vulnerable library glob parent tgz strips glob magic from a string to provide the parent path library home page a href path to dependency file packages insomnia components package json path to vulnerable library packages insomnia components node modules glob base node modules glob parent package json dependency hierarchy react tgz root library core common tgz glob base tgz x glob parent tgz vulnerable library glob parent tgz extract the non magic parent path from a glob string library home page a href path to dependency file package json path to vulnerable library node modules lerna project node modules glob parent package json packages insomnia components node modules watchpack node modules glob parent package json packages insomnia inso node modules glob parent package json packages insomnia testing node modules glob parent package json dependency hierarchy lerna tgz root library link tgz command tgz project tgz x glob parent tgz vulnerable library glob parent tgz strips glob magic from a string to provide the parent directory path library home page a href dependency hierarchy webpack tgz root library watchpack tgz watchpack tgz chokidar tgz x glob parent tgz vulnerable library found in base branch develop vulnerability details the package glob parent before are vulnerable to regular expression denial of service redos 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 glob parent step up your open source security game with whitesource
| 0
|
629,098
| 20,023,315,080
|
IssuesEvent
|
2022-02-01 18:28:46
|
Datawheel/canon
|
https://api.github.com/repos/Datawheel/canon
|
closed
|
[reports] Style inline generators
|
type: feature priority: 3 - medium effort: 3 - standard
|
In cms-1.0-develop, one can click a generator in VariablesList, and the entire modal will replace its contents with the generator the user clicked. They can edit this, then click "Save & Return" at which point the modal returns to the statlike.
Dave, can you style this such that:
- [x] The hover is conditional over only generators
- [x] The hover is somehow meaningful for clicking (use a tooltip to explain?)
- [x] The transition of going from the normal editor to the `setInlineId` editors has some kind of visually helpful slide/transition
- [x] Any other design elements that would help the user understand "where we are"
|
1.0
|
[reports] Style inline generators - In cms-1.0-develop, one can click a generator in VariablesList, and the entire modal will replace its contents with the generator the user clicked. They can edit this, then click "Save & Return" at which point the modal returns to the statlike.
Dave, can you style this such that:
- [x] The hover is conditional over only generators
- [x] The hover is somehow meaningful for clicking (use a tooltip to explain?)
- [x] The transition of going from the normal editor to the `setInlineId` editors has some kind of visually helpful slide/transition
- [x] Any other design elements that would help the user understand "where we are"
|
non_main
|
style inline generators in cms develop one can click a generator in variableslist and the entire modal will replace its contents with the generator the user clicked they can edit this then click save return at which point the modal returns to the statlike dave can you style this such that the hover is conditional over only generators the hover is somehow meaningful for clicking use a tooltip to explain the transition of going from the normal editor to the setinlineid editors has some kind of visually helpful slide transition any other design elements that would help the user understand where we are
| 0
|
332,802
| 24,350,175,508
|
IssuesEvent
|
2022-10-02 21:02:06
|
ovejerojose/Full_Stack
|
https://api.github.com/repos/ovejerojose/Full_Stack
|
reopened
|
#US09
|
documentation
|
- Como: Personal administrativo
Quiero: Que en la confirmación de la reserva tanto al cliente como al personal administrativo se le brinde un número identificador o ID
|
1.0
|
#US09 - - Como: Personal administrativo
Quiero: Que en la confirmación de la reserva tanto al cliente como al personal administrativo se le brinde un número identificador o ID
|
non_main
|
como personal administrativo quiero que en la confirmación de la reserva tanto al cliente como al personal administrativo se le brinde un número identificador o id
| 0
|
1,609
| 6,572,623,808
|
IssuesEvent
|
2017-09-11 03:50:57
|
ansible/ansible-modules-core
|
https://api.github.com/repos/ansible/ansible-modules-core
|
closed
|
Upload binary file possibility in URI module
|
affects_1.9 feature_idea waiting_on_maintainer
|
##### Issue Type:
- Feature Idea
##### Plugin Name:
uri
##### Ansible Version:
1.9.2
##### Environment:
N/A
##### Summary:
It would be nice to have option to upload binary file to HTTP endpoint using HTTP PUT. Expecting behaviour similar to following curl command:
```
curl -k -X PUT -u user:password --upload-file test.jar "https://IP:PORT/endpoint/"
```
and example of possible URI usage:
```
- name: Push jar to nexus
uri:
url: "https://{{ inventory_hostname }}:{{ port }}/{{ endpoint }}"
src: /tmp/{{ file }}.jar
user: "{{ user }}"
password: "{{ password }}"
method: PUT
```
|
True
|
Upload binary file possibility in URI module - ##### Issue Type:
- Feature Idea
##### Plugin Name:
uri
##### Ansible Version:
1.9.2
##### Environment:
N/A
##### Summary:
It would be nice to have option to upload binary file to HTTP endpoint using HTTP PUT. Expecting behaviour similar to following curl command:
```
curl -k -X PUT -u user:password --upload-file test.jar "https://IP:PORT/endpoint/"
```
and example of possible URI usage:
```
- name: Push jar to nexus
uri:
url: "https://{{ inventory_hostname }}:{{ port }}/{{ endpoint }}"
src: /tmp/{{ file }}.jar
user: "{{ user }}"
password: "{{ password }}"
method: PUT
```
|
main
|
upload binary file possibility in uri module issue type feature idea plugin name uri ansible version environment n a summary it would be nice to have option to upload binary file to http endpoint using http put expecting behaviour similar to following curl command curl k x put u user password upload file test jar and example of possible uri usage name push jar to nexus uri url inventory hostname port endpoint src tmp file jar user user password password method put
| 1
|
17,138
| 3,594,577,039
|
IssuesEvent
|
2016-02-02 00:24:29
|
googlefonts/fontbakery
|
https://api.github.com/repos/googlefonts/fontbakery
|
closed
|
Upstream test: Check glyphs names comply with PostScript conventions
|
quick testing
|
As per https://github.com/behdad/fonttools/issues/120 then glyph names should be checked for compliance with the PostScript glyph naming requirements, described at http://www.adobe.com/devnet-archive/opentype/archives/glyphnamelimits.html#4
|
1.0
|
Upstream test: Check glyphs names comply with PostScript conventions - As per https://github.com/behdad/fonttools/issues/120 then glyph names should be checked for compliance with the PostScript glyph naming requirements, described at http://www.adobe.com/devnet-archive/opentype/archives/glyphnamelimits.html#4
|
non_main
|
upstream test check glyphs names comply with postscript conventions as per then glyph names should be checked for compliance with the postscript glyph naming requirements described at
| 0
|
238,685
| 26,144,490,779
|
IssuesEvent
|
2022-12-30 01:04:39
|
artkamote/examples
|
https://api.github.com/repos/artkamote/examples
|
opened
|
CVE-2022-3064 (High) detected in github.com/go-yaml/yaml-v2.2.2
|
security vulnerability
|
## CVE-2022-3064 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>github.com/go-yaml/yaml-v2.2.2</b></p></summary>
<p>YAML support for the Go language.</p>
<p>
Dependency Hierarchy:
- github.com/AWS/aws-lambda-go-v1.6.0 (Root Library)
- github.com/STRETCHR/testify-v1.5.1
- :x: **github.com/go-yaml/yaml-v2.2.2** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/artkamote/examples/commit/dcbe4aefe4b3685f4b15493a01db0f19b118a0c4">dcbe4aefe4b3685f4b15493a01db0f19b118a0c4</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>
Parsing malicious or large YAML documents can consume excessive amounts of CPU or memory.
<p>Publish Date: 2022-12-27
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-3064>CVE-2022-3064</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://pkg.go.dev/vuln/GO-2022-0956">https://pkg.go.dev/vuln/GO-2022-0956</a></p>
<p>Release Date: 2022-12-27</p>
<p>Fix Resolution: v2.2.4</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-3064 (High) detected in github.com/go-yaml/yaml-v2.2.2 - ## CVE-2022-3064 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>github.com/go-yaml/yaml-v2.2.2</b></p></summary>
<p>YAML support for the Go language.</p>
<p>
Dependency Hierarchy:
- github.com/AWS/aws-lambda-go-v1.6.0 (Root Library)
- github.com/STRETCHR/testify-v1.5.1
- :x: **github.com/go-yaml/yaml-v2.2.2** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/artkamote/examples/commit/dcbe4aefe4b3685f4b15493a01db0f19b118a0c4">dcbe4aefe4b3685f4b15493a01db0f19b118a0c4</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>
Parsing malicious or large YAML documents can consume excessive amounts of CPU or memory.
<p>Publish Date: 2022-12-27
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-3064>CVE-2022-3064</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://pkg.go.dev/vuln/GO-2022-0956">https://pkg.go.dev/vuln/GO-2022-0956</a></p>
<p>Release Date: 2022-12-27</p>
<p>Fix Resolution: v2.2.4</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_main
|
cve high detected in github com go yaml yaml cve high severity vulnerability vulnerable library github com go yaml yaml yaml support for the go language dependency hierarchy github com aws aws lambda go root library github com stretchr testify x github com go yaml yaml vulnerable library found in head commit a href found in base branch master vulnerability details parsing malicious or large yaml documents can consume excessive amounts of cpu or memory publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend
| 0
|
1,956
| 6,676,916,631
|
IssuesEvent
|
2017-10-05 08:22:20
|
opencaching/opencaching-pl
|
https://api.github.com/repos/opencaching/opencaching-pl
|
opened
|
Refactoring attribute IDs
|
Component_Cache Component_Configs Component_DataBase Component_Export (GPX etc.) Component_OKAPI_usage Maintainability Type_Enhancement Usability
|
I propose a more radical overhaul, that will bring consistency across OCPL and OCDE and greatly simplify exports and OKAPI and exchanging data.
It requires a bit of cooperation between OCPL and OCDE developers and each node admin because there will be changes in the data.
Here is my proposal _(for a complete overhaul)_:
- all OC attributes that have equivalent meaning to a GC attribute to use the same numeric ID
_(while the meaning is equivalent, the exact wording of it's name need not be the same. examples are "bring your children / suitable for children / kids friendly / etc")_
- all OC attributes that have equivalent meaning to a negated GC attribute to use the same numeric ID with 99X prefix, where X is the hundreds digit from the GC attribute ID, currently 0, but allowing to be expanded. _(for example: "available 24/7" is ID 13. "NOT available 24/7" to be ID 99013.)_
- all OC attributes that have equivalent meaning on both PL and DE branches to have numeric IDs in the range 1000 - 1999
- all OC attributes that are PL branch specific to have numeric IDs in the range 2000 - 2999
- all OC attributes that are DE branch specific to have numeric IDs in the range 3000 - 3999
- all OC attributes that have the meaning of a negated OC attribute to use the same numeric ID on the least significant 3 digits, the fourth digit be the branch designator (according to applicability) and the fifth (most significant digit) be 9.
(hypothetical generic example: "available during high tide" ID 2141 - PL branch (UK), "NOT available during high tide" ID 91141 - all branches)
The only special processing to handle OC/GC differences might be regarding the negated GC attribute to set GC specific negation with non-prefixed ID in GPX file. The introduction of <oc:attribute> in GPX export is very helpful in this regard too.
All IDs documented properly at https://wiki.opencaching.eu/index.php/Cache_attributes
-----------------------------
What does this acomplish:
1. a consistent export of data with non-overlapping numerical identificators regardless of the source site
2. a consistent and well documented set of data for third party application builders to rely upon
2. a consistent export of data compatible with GC aware apps
===================================
Roadmap to acomplish this:
1. collect all existing information from all nodes about attributes
2. decide and inform all nodes and developers to put on hold any future changes to attributes until this is fully implemented and deployed
3. renumber all attributes (and create well documented correspondency tables); document new scheme at https://wiki.opencaching.eu/index.php/Cache_attributes along with deployment schedule.
4. implement the code changes
5. create SQL files to alter the database definition tables and cache<=>attrib mapping tables
_to avoid overlaps, simply add 10000 to all existing IDs, then individually remap each._
6. test
7. make simulated deployment
8. coordinate with all node admins for production deployment
8a. OC node stops syncing to repository (at least PL branch based nodes)
8b. OC node goes into maintenance mode
8c. database changes are applied
8d. OC node updates to code changes
8e. OC node resumes syncing to repository (where applicable)
8f. OC node resumes normal operations
9. make documentation updates (including publishing the remapping table, if needed by third party)
10. point third party developers to https://wiki.opencaching.eu/index.php/Cache_attributes
|
True
|
Refactoring attribute IDs - I propose a more radical overhaul, that will bring consistency across OCPL and OCDE and greatly simplify exports and OKAPI and exchanging data.
It requires a bit of cooperation between OCPL and OCDE developers and each node admin because there will be changes in the data.
Here is my proposal _(for a complete overhaul)_:
- all OC attributes that have equivalent meaning to a GC attribute to use the same numeric ID
_(while the meaning is equivalent, the exact wording of it's name need not be the same. examples are "bring your children / suitable for children / kids friendly / etc")_
- all OC attributes that have equivalent meaning to a negated GC attribute to use the same numeric ID with 99X prefix, where X is the hundreds digit from the GC attribute ID, currently 0, but allowing to be expanded. _(for example: "available 24/7" is ID 13. "NOT available 24/7" to be ID 99013.)_
- all OC attributes that have equivalent meaning on both PL and DE branches to have numeric IDs in the range 1000 - 1999
- all OC attributes that are PL branch specific to have numeric IDs in the range 2000 - 2999
- all OC attributes that are DE branch specific to have numeric IDs in the range 3000 - 3999
- all OC attributes that have the meaning of a negated OC attribute to use the same numeric ID on the least significant 3 digits, the fourth digit be the branch designator (according to applicability) and the fifth (most significant digit) be 9.
(hypothetical generic example: "available during high tide" ID 2141 - PL branch (UK), "NOT available during high tide" ID 91141 - all branches)
The only special processing to handle OC/GC differences might be regarding the negated GC attribute to set GC specific negation with non-prefixed ID in GPX file. The introduction of <oc:attribute> in GPX export is very helpful in this regard too.
All IDs documented properly at https://wiki.opencaching.eu/index.php/Cache_attributes
-----------------------------
What does this acomplish:
1. a consistent export of data with non-overlapping numerical identificators regardless of the source site
2. a consistent and well documented set of data for third party application builders to rely upon
2. a consistent export of data compatible with GC aware apps
===================================
Roadmap to acomplish this:
1. collect all existing information from all nodes about attributes
2. decide and inform all nodes and developers to put on hold any future changes to attributes until this is fully implemented and deployed
3. renumber all attributes (and create well documented correspondency tables); document new scheme at https://wiki.opencaching.eu/index.php/Cache_attributes along with deployment schedule.
4. implement the code changes
5. create SQL files to alter the database definition tables and cache<=>attrib mapping tables
_to avoid overlaps, simply add 10000 to all existing IDs, then individually remap each._
6. test
7. make simulated deployment
8. coordinate with all node admins for production deployment
8a. OC node stops syncing to repository (at least PL branch based nodes)
8b. OC node goes into maintenance mode
8c. database changes are applied
8d. OC node updates to code changes
8e. OC node resumes syncing to repository (where applicable)
8f. OC node resumes normal operations
9. make documentation updates (including publishing the remapping table, if needed by third party)
10. point third party developers to https://wiki.opencaching.eu/index.php/Cache_attributes
|
main
|
refactoring attribute ids i propose a more radical overhaul that will bring consistency across ocpl and ocde and greatly simplify exports and okapi and exchanging data it requires a bit of cooperation between ocpl and ocde developers and each node admin because there will be changes in the data here is my proposal for a complete overhaul all oc attributes that have equivalent meaning to a gc attribute to use the same numeric id while the meaning is equivalent the exact wording of it s name need not be the same examples are bring your children suitable for children kids friendly etc all oc attributes that have equivalent meaning to a negated gc attribute to use the same numeric id with prefix where x is the hundreds digit from the gc attribute id currently but allowing to be expanded for example available is id not available to be id all oc attributes that have equivalent meaning on both pl and de branches to have numeric ids in the range all oc attributes that are pl branch specific to have numeric ids in the range all oc attributes that are de branch specific to have numeric ids in the range all oc attributes that have the meaning of a negated oc attribute to use the same numeric id on the least significant digits the fourth digit be the branch designator according to applicability and the fifth most significant digit be hypothetical generic example available during high tide id pl branch uk not available during high tide id all branches the only special processing to handle oc gc differences might be regarding the negated gc attribute to set gc specific negation with non prefixed id in gpx file the introduction of in gpx export is very helpful in this regard too all ids documented properly at what does this acomplish a consistent export of data with non overlapping numerical identificators regardless of the source site a consistent and well documented set of data for third party application builders to rely upon a consistent export of data compatible with gc aware apps roadmap to acomplish this collect all existing information from all nodes about attributes decide and inform all nodes and developers to put on hold any future changes to attributes until this is fully implemented and deployed renumber all attributes and create well documented correspondency tables document new scheme at along with deployment schedule implement the code changes create sql files to alter the database definition tables and cache attrib mapping tables to avoid overlaps simply add to all existing ids then individually remap each test make simulated deployment coordinate with all node admins for production deployment oc node stops syncing to repository at least pl branch based nodes oc node goes into maintenance mode database changes are applied oc node updates to code changes oc node resumes syncing to repository where applicable oc node resumes normal operations make documentation updates including publishing the remapping table if needed by third party point third party developers to
| 1
|
695
| 4,257,760,046
|
IssuesEvent
|
2016-07-11 01:05:56
|
Particular/ServiceInsight
|
https://api.github.com/repos/Particular/ServiceInsight
|
closed
|
Look for a valid license on multiple locations (HKCU and HKLM)
|
Size: S State: In Progress - Maintainer Prio Tag: Maintainer Prio Type: Refactoring
|
The new licensing package would look for a license in both HKCU and HKLM. If you have an expired or trial license at one location, the licensing module will still look for a valid license in the other location.
|
True
|
Look for a valid license on multiple locations (HKCU and HKLM) - The new licensing package would look for a license in both HKCU and HKLM. If you have an expired or trial license at one location, the licensing module will still look for a valid license in the other location.
|
main
|
look for a valid license on multiple locations hkcu and hklm the new licensing package would look for a license in both hkcu and hklm if you have an expired or trial license at one location the licensing module will still look for a valid license in the other location
| 1
|
44,915
| 2,918,434,241
|
IssuesEvent
|
2015-06-24 08:06:33
|
UnifiedViews/Plugins
|
https://api.github.com/repos/UnifiedViews/Plugins
|
closed
|
Create new DPU: e-DistributionMetadata
|
priority: Normal resolution: fixed severity: enhancement status: resolved
|
Take this dpu https://github.com/mff-uk/DPUs/tree/master/dpu/e-distributionMetadata
move it here, rewrite it completely and make it work.
|
1.0
|
Create new DPU: e-DistributionMetadata - Take this dpu https://github.com/mff-uk/DPUs/tree/master/dpu/e-distributionMetadata
move it here, rewrite it completely and make it work.
|
non_main
|
create new dpu e distributionmetadata take this dpu move it here rewrite it completely and make it work
| 0
|
5,272
| 8,059,815,157
|
IssuesEvent
|
2018-08-02 23:57:26
|
uccser/verto
|
https://api.github.com/repos/uccser/verto
|
opened
|
Extract image file path parsing code into separate function
|
processor implementation restructuring
|
The same code is used in `ImageTagBlockProcessor`, `ImageContainerBlockProcessor` and `ImageInline` pattern. This is redundant and could lead to mistakes when updating these processors, so should moved to another function which each of the processors can call.
|
1.0
|
Extract image file path parsing code into separate function - The same code is used in `ImageTagBlockProcessor`, `ImageContainerBlockProcessor` and `ImageInline` pattern. This is redundant and could lead to mistakes when updating these processors, so should moved to another function which each of the processors can call.
|
non_main
|
extract image file path parsing code into separate function the same code is used in imagetagblockprocessor imagecontainerblockprocessor and imageinline pattern this is redundant and could lead to mistakes when updating these processors so should moved to another function which each of the processors can call
| 0
|
218,500
| 16,994,044,477
|
IssuesEvent
|
2021-07-01 02:29:33
|
quarkusio/quarkus
|
https://api.github.com/repos/quarkusio/quarkus
|
closed
|
Continuous Testing onComplete called when no tests has been run
|
area/continuous-testing kind/bug
|
## Describe the bug
This is maybe an edge case, but it happened in this specific situation:
project: https://github.com/ia3andy/rock-rock-rock/tree/no-test-run
1. Run in dev mode and start continuous testing "r"
2. Hit "b" to activate broken mode
3. Change the content of the @Disabled `mayWeHaveANewBand` test
In the output it's a local branch where I added a specific message for that case as a fallback:
```
2021-05-19 12:06:42,364 INFO [io.quarkus] (Quarkus Main Thread) Profile dev activated. Live Coding activated.
2021-05-19 12:06:42,364 INFO [io.quarkus] (Quarkus Main Thread) Installed features: [agroal, cdi, hibernate-orm, hibernate-orm-panache, hibernate-validator, jdbc-postgresql, nar
2021-05-19 12:06:52,025 INFO [io.qua.test] (Test runner thread) ==================== TEST REPORT #1 ====================
2021-05-19 12:06:52,026 INFO [io.qua.test] (Test runner thread) >>>>>>>>>>>>>>>>>>>> 3 TESTS PASSED <<<<<<<<<<<<<<<<<<<<
2021-05-19 12:06:52,773 INFO [io.qua.dep.dev.tes.TestSupport] (Aesh InputStream Reader) Broken only mode enabled
2021-05-19 12:06:59,010 INFO [io.qua.dep.dev.RuntimeUpdatesProcessor] (Test Compile Timer) Changed source files detected, recompiling RockBandResourceTest.java
2021-05-19 12:07:00,119 INFO [io.qua.test] (Test runner thread) ==================== TEST REPORT #2 ====================
2021-05-19 12:07:00,120 WARN [io.qua.test] (Test runner thread) >>>>>>>>>>>>>>>>>>>> NO TEST WAS RUN <<<<<<<<<<<<<<<<<<<<
2021-05-19 14:54:27,786 INFO [io.quarkus] (Shutdown thread) rock-rock-rock stopped in 0.021s
```
|
1.0
|
Continuous Testing onComplete called when no tests has been run - ## Describe the bug
This is maybe an edge case, but it happened in this specific situation:
project: https://github.com/ia3andy/rock-rock-rock/tree/no-test-run
1. Run in dev mode and start continuous testing "r"
2. Hit "b" to activate broken mode
3. Change the content of the @Disabled `mayWeHaveANewBand` test
In the output it's a local branch where I added a specific message for that case as a fallback:
```
2021-05-19 12:06:42,364 INFO [io.quarkus] (Quarkus Main Thread) Profile dev activated. Live Coding activated.
2021-05-19 12:06:42,364 INFO [io.quarkus] (Quarkus Main Thread) Installed features: [agroal, cdi, hibernate-orm, hibernate-orm-panache, hibernate-validator, jdbc-postgresql, nar
2021-05-19 12:06:52,025 INFO [io.qua.test] (Test runner thread) ==================== TEST REPORT #1 ====================
2021-05-19 12:06:52,026 INFO [io.qua.test] (Test runner thread) >>>>>>>>>>>>>>>>>>>> 3 TESTS PASSED <<<<<<<<<<<<<<<<<<<<
2021-05-19 12:06:52,773 INFO [io.qua.dep.dev.tes.TestSupport] (Aesh InputStream Reader) Broken only mode enabled
2021-05-19 12:06:59,010 INFO [io.qua.dep.dev.RuntimeUpdatesProcessor] (Test Compile Timer) Changed source files detected, recompiling RockBandResourceTest.java
2021-05-19 12:07:00,119 INFO [io.qua.test] (Test runner thread) ==================== TEST REPORT #2 ====================
2021-05-19 12:07:00,120 WARN [io.qua.test] (Test runner thread) >>>>>>>>>>>>>>>>>>>> NO TEST WAS RUN <<<<<<<<<<<<<<<<<<<<
2021-05-19 14:54:27,786 INFO [io.quarkus] (Shutdown thread) rock-rock-rock stopped in 0.021s
```
|
non_main
|
continuous testing oncomplete called when no tests has been run describe the bug this is maybe an edge case but it happened in this specific situation project run in dev mode and start continuous testing r hit b to activate broken mode change the content of the disabled maywehaveanewband test in the output it s a local branch where i added a specific message for that case as a fallback info quarkus main thread profile dev activated live coding activated info quarkus main thread installed features agroal cdi hibernate orm hibernate orm panache hibernate validator jdbc postgresql nar info test runner thread test report info test runner thread tests passed info aesh inputstream reader broken only mode enabled info test compile timer changed source files detected recompiling rockbandresourcetest java info test runner thread test report warn test runner thread no test was run info shutdown thread rock rock rock stopped in
| 0
|
2,305
| 8,235,658,515
|
IssuesEvent
|
2018-09-09 07:38:21
|
arcticicestudio/igloo
|
https://api.github.com/repos/arcticicestudio/igloo
|
closed
|
Update and remove obsolete application desktop files
|
scope-maintainability snowblock-plank snowblock-xdg type-improvement
|
Some XDG application `.desktop` files are not required anymore because the latest upstream versions have been adapted and improved to match the custom configurations:
<p align="center"><img src="https://upload.wikimedia.org/wikipedia/commons/d/d5/IntelliJ_IDEA_Logo.svg?sanitize=true" width="20%" /> <img src="https://upload.wikimedia.org/wikipedia/commons/a/a1/PyCharm_Logo.svg?sanitize=true" width="20%" /> <img src="https://confluence.jetbrains.com/download/thumbnails/51964300/WebStorm_400x400_Twitter_logo_white.png" width="22%" /></p>
* [JetBrains IntelliJ IDEA Ultimate Edition][jb-idea-u] binary `/opt/intellij-idea-ultimate-edition/bin/idea.sh` is now linked to `/usr/bin/idea` and `/usr/bin/intellij-idea-ultimate-edition`. The desktop file is now named uniform `/usr/share/applications/jetbrains-idea.desktop`.
* [JetBrains IntelliJ IDEA Community Edition][jb-idea-ce] binary `/opt/intellij-idea-community-edition/bin/idea.sh` is now linked to `/usr/bin/idea`. The desktop file is now named uniform `/usr/share/applications/jetbrains-idea.desktop`.
* [JetBrains Webstorm][jb-ws] binary `/opt/webstorm/bin/webstorm.sh` is now linked to `/usr/bin/webstorm` and the desktop file is now named uniform `/usr/share/applications/jetbrains-webstorm.desktop`.
* [JetBrains Pycharm Community Edition][jb-py-ce] binary `/opt/pycharm-community-edition/bin/pycharm.sh` is now linked to `/usr/bin/pycharm`, bu the desktop file is still named `/usr/share/applications/pycharm.desktop`.
<p align="center"><img src="https://github-atom-io-herokuapp-com.global.ssl.fastly.net/assets/index-logo-9fb707770c2c8a018b7a2933906c3436.svg" width="20%" /></p>
* [Atom 1.28][a] included an upgrade to Electron 2.0 and now ships with an standalone launcher(`/usr/lib/atom/atom`) instead of using the Electron binary (`electron <BINARY_PATH>`).
[jb-idea-u]: https://aur.archlinux.org/cgit/aur.git/tree/jetbrains-idea.desktop?h=intellij-idea-ultimate-edition
[jb-idea-ce]: https://git.archlinux.org/svntogit/community.git/tree/trunk/idea.desktop?h=packages/intellij-idea-community-edition
[jb-ws]: https://aur.archlinux.org/cgit/aur.git/tree/jetbrains-webstorm.desktop?h=webstorm
[jb-py-ce]: https://git.archlinux.org/svntogit/community.git/tree/trunk/pycharm.desktop?h=packages/pycharm-community-edition
[a]: http://blog.atom.io/2018/06/21/atom-1-28.html#electron-upgrade
|
True
|
Update and remove obsolete application desktop files - Some XDG application `.desktop` files are not required anymore because the latest upstream versions have been adapted and improved to match the custom configurations:
<p align="center"><img src="https://upload.wikimedia.org/wikipedia/commons/d/d5/IntelliJ_IDEA_Logo.svg?sanitize=true" width="20%" /> <img src="https://upload.wikimedia.org/wikipedia/commons/a/a1/PyCharm_Logo.svg?sanitize=true" width="20%" /> <img src="https://confluence.jetbrains.com/download/thumbnails/51964300/WebStorm_400x400_Twitter_logo_white.png" width="22%" /></p>
* [JetBrains IntelliJ IDEA Ultimate Edition][jb-idea-u] binary `/opt/intellij-idea-ultimate-edition/bin/idea.sh` is now linked to `/usr/bin/idea` and `/usr/bin/intellij-idea-ultimate-edition`. The desktop file is now named uniform `/usr/share/applications/jetbrains-idea.desktop`.
* [JetBrains IntelliJ IDEA Community Edition][jb-idea-ce] binary `/opt/intellij-idea-community-edition/bin/idea.sh` is now linked to `/usr/bin/idea`. The desktop file is now named uniform `/usr/share/applications/jetbrains-idea.desktop`.
* [JetBrains Webstorm][jb-ws] binary `/opt/webstorm/bin/webstorm.sh` is now linked to `/usr/bin/webstorm` and the desktop file is now named uniform `/usr/share/applications/jetbrains-webstorm.desktop`.
* [JetBrains Pycharm Community Edition][jb-py-ce] binary `/opt/pycharm-community-edition/bin/pycharm.sh` is now linked to `/usr/bin/pycharm`, bu the desktop file is still named `/usr/share/applications/pycharm.desktop`.
<p align="center"><img src="https://github-atom-io-herokuapp-com.global.ssl.fastly.net/assets/index-logo-9fb707770c2c8a018b7a2933906c3436.svg" width="20%" /></p>
* [Atom 1.28][a] included an upgrade to Electron 2.0 and now ships with an standalone launcher(`/usr/lib/atom/atom`) instead of using the Electron binary (`electron <BINARY_PATH>`).
[jb-idea-u]: https://aur.archlinux.org/cgit/aur.git/tree/jetbrains-idea.desktop?h=intellij-idea-ultimate-edition
[jb-idea-ce]: https://git.archlinux.org/svntogit/community.git/tree/trunk/idea.desktop?h=packages/intellij-idea-community-edition
[jb-ws]: https://aur.archlinux.org/cgit/aur.git/tree/jetbrains-webstorm.desktop?h=webstorm
[jb-py-ce]: https://git.archlinux.org/svntogit/community.git/tree/trunk/pycharm.desktop?h=packages/pycharm-community-edition
[a]: http://blog.atom.io/2018/06/21/atom-1-28.html#electron-upgrade
|
main
|
update and remove obsolete application desktop files some xdg application desktop files are not required anymore because the latest upstream versions have been adapted and improved to match the custom configurations binary opt intellij idea ultimate edition bin idea sh is now linked to usr bin idea and usr bin intellij idea ultimate edition the desktop file is now named uniform usr share applications jetbrains idea desktop binary opt intellij idea community edition bin idea sh is now linked to usr bin idea the desktop file is now named uniform usr share applications jetbrains idea desktop binary opt webstorm bin webstorm sh is now linked to usr bin webstorm and the desktop file is now named uniform usr share applications jetbrains webstorm desktop binary opt pycharm community edition bin pycharm sh is now linked to usr bin pycharm bu the desktop file is still named usr share applications pycharm desktop included an upgrade to electron and now ships with an standalone launcher usr lib atom atom instead of using the electron binary electron
| 1
|
149
| 2,669,188,541
|
IssuesEvent
|
2015-03-23 14:15:59
|
TheRosettaFoundation/SOLAS-Match
|
https://api.github.com/repos/TheRosettaFoundation/SOLAS-Match
|
closed
|
Creating separate html files for FAQ
|
feature-idea Localisation maintainability
|
As it stands, it is very difficult to update the FAQ because of the distributed nature of FAQ's content within the strings files. To facilitate easy updating of FAQ content (as well as easy localisation), the content can be stored in plain html format (excluding header and footer info) for each language within the localisation folder (ui/localisation/) (e.g. FAQ_en.html, FAQ_es.html, FAQ_it.html). Then depending on user's preferred UI language, the relevant FAQ can be displayed with the header and footer information.
This will also have following benefits:
1) isolates FAQ content from stings.xml and strings.xml can mainly be used for non-static content.
2) screenshots/localised images can be used within the FAQ
3) in place localisation of html files - for localisers
@spaceindaver, @TheIceMageX50 What are your views on this idea?
|
True
|
Creating separate html files for FAQ - As it stands, it is very difficult to update the FAQ because of the distributed nature of FAQ's content within the strings files. To facilitate easy updating of FAQ content (as well as easy localisation), the content can be stored in plain html format (excluding header and footer info) for each language within the localisation folder (ui/localisation/) (e.g. FAQ_en.html, FAQ_es.html, FAQ_it.html). Then depending on user's preferred UI language, the relevant FAQ can be displayed with the header and footer information.
This will also have following benefits:
1) isolates FAQ content from stings.xml and strings.xml can mainly be used for non-static content.
2) screenshots/localised images can be used within the FAQ
3) in place localisation of html files - for localisers
@spaceindaver, @TheIceMageX50 What are your views on this idea?
|
main
|
creating separate html files for faq as it stands it is very difficult to update the faq because of the distributed nature of faq s content within the strings files to facilitate easy updating of faq content as well as easy localisation the content can be stored in plain html format excluding header and footer info for each language within the localisation folder ui localisation e g faq en html faq es html faq it html then depending on user s preferred ui language the relevant faq can be displayed with the header and footer information this will also have following benefits isolates faq content from stings xml and strings xml can mainly be used for non static content screenshots localised images can be used within the faq in place localisation of html files for localisers spaceindaver what are your views on this idea
| 1
|
276,678
| 30,514,528,030
|
IssuesEvent
|
2023-07-19 01:01:48
|
amaybaum-dev/log4shell-demo2
|
https://api.github.com/repos/amaybaum-dev/log4shell-demo2
|
opened
|
spring-boot-starter-web-2.6.1.jar: 13 vulnerabilities (highest severity is: 9.8) reachable
|
Mend: dependency security vulnerability
|
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-boot-starter-web-2.6.1.jar</b></p></summary>
<p></p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-core/5.3.13/d2a6c3372dd337e08144f9f49f386b8ec7a8080d/spring-core-5.3.13.jar</p>
<p>
</details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (spring-boot-starter-web version) | Remediation Available | Reachability |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- | --- |
| [CVE-2022-22965](https://www.mend.io/vulnerability-database/CVE-2022-22965) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.8 | spring-beans-5.3.13.jar | Transitive | 2.6.6 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2022-1471](https://www.mend.io/vulnerability-database/CVE-2022-1471) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.8 | snakeyaml-1.29.jar | Transitive | N/A* | ❌|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20>](## 'The vulnerability is non-reachable.')</a></p> |
| [CVE-2022-42004](https://www.mend.io/vulnerability-database/CVE-2022-42004) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | jackson-databind-2.13.0.jar | Transitive | 2.6.12 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2022-42003](https://www.mend.io/vulnerability-database/CVE-2022-42003) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | jackson-databind-2.13.0.jar | Transitive | 2.6.15 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2020-36518](https://www.mend.io/vulnerability-database/CVE-2020-36518) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | jackson-databind-2.13.0.jar | Transitive | 2.6.8 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2023-24998](https://www.mend.io/vulnerability-database/CVE-2023-24998) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | tomcat-embed-core-9.0.55.jar | Transitive | 2.6.15 | ✅ |
| [CVE-2021-46877](https://www.mend.io/vulnerability-database/CVE-2021-46877) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | jackson-databind-2.13.0.jar | Transitive | 2.6.2 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2022-22950](https://www.mend.io/vulnerability-database/CVE-2022-22950) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.5 | spring-expression-5.3.13.jar | Transitive | 2.6.5 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2023-20861](https://www.mend.io/vulnerability-database/CVE-2023-20861) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.5 | spring-expression-5.3.13.jar | Transitive | 2.6.15 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2023-20863](https://www.mend.io/vulnerability-database/CVE-2023-20863) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.5 | spring-expression-5.3.13.jar | Transitive | 2.6.15 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2022-22968](https://www.mend.io/vulnerability-database/CVE-2022-22968) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.3 | spring-context-5.3.13.jar | Transitive | 2.6.7 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2022-22970](https://www.mend.io/vulnerability-database/CVE-2022-22970) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.3 | detected in multiple dependencies | Transitive | 2.6.8 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-22060](https://www.mend.io/vulnerability-database/CVE-2021-22060) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 4.3 | detected in multiple dependencies | Transitive | 2.6.2 | ✅ |
<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/critical_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2022-22965</summary>
### Vulnerable Library - <b>spring-beans-5.3.13.jar</b></p>
<p>Spring Beans</p>
<p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-beans/5.3.13/1d90c96b287253ec371260c35fbbea719c24bad6/spring-beans-5.3.13.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.6.1.jar (Root Library)
- spring-webmvc-5.3.13.jar
- :x: **spring-beans-5.3.13.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
fr.christophetd.log4shell.vulnerableapp.VulnerableAppApplication (Application)
-> org.springframework.boot.SpringApplication (Extension)
-> ❌ org.springframework.beans.CachedIntrospectionResults (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
A Spring MVC or Spring WebFlux application running on JDK 9+ may be vulnerable to remote code execution (RCE) via data binding. The specific exploit requires the application to run on Tomcat as a WAR deployment. If the application is deployed as a Spring Boot executable jar, i.e. the default, it is not vulnerable to the exploit. However, the nature of the vulnerability is more general, and there may be other ways to exploit it.
Mend Note: Converted from WS-2022-0107, on 2022-11-07.
<p>Publish Date: 2022-04-01
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-22965>CVE-2022-22965</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</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: 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://spring.io/blog/2022/03/31/spring-framework-rce-early-announcement">https://spring.io/blog/2022/03/31/spring-framework-rce-early-announcement</a></p>
<p>Release Date: 2022-04-01</p>
<p>Fix Resolution (org.springframework:spring-beans): 5.3.18</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.6.6</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20> CVE-2022-1471</summary>
### Vulnerable Library - <b>snakeyaml-1.29.jar</b></p>
<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href="http://www.snakeyaml.org">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.29/6d0cdafb2010f1297e574656551d7145240f6e25/snakeyaml-1.29.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.6.1.jar (Root Library)
- spring-boot-starter-2.6.1.jar
- :x: **snakeyaml-1.29.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
<p>The vulnerable code is not reachable.</p>
</p>
<p></p>
### Vulnerability Details
<p>
SnakeYaml's Constructor() class does not restrict types which can be instantiated during deserialization. Deserializing yaml content provided by an attacker can lead to remote code execution. We recommend using SnakeYaml's SafeConsturctor when parsing untrusted content to restrict deserialization. We recommend upgrading to version 2.0 and beyond.
<p>Publish Date: 2022-12-01
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-1471>CVE-2022-1471</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</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: 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://bitbucket.org/snakeyaml/snakeyaml/issues/561/cve-2022-1471-vulnerability-in#comment-64634374">https://bitbucket.org/snakeyaml/snakeyaml/issues/561/cve-2022-1471-vulnerability-in#comment-64634374</a></p>
<p>Release Date: 2022-12-01</p>
<p>Fix Resolution: org.yaml:snakeyaml:2.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2022-42004</summary>
### Vulnerable Library - <b>jackson-databind-2.13.0.jar</b></p>
<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: /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.13.0/889672a1721d6d85b2834fcd29d3fda92c8c8891/jackson-databind-2.13.0.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.6.1.jar (Root Library)
- spring-boot-starter-json-2.6.1.jar
- :x: **jackson-databind-2.13.0.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
fr.christophetd.log4shell.vulnerableapp.MainController (Application)
-> org.apache.logging.log4j.LogManager (Extension)
-> org.apache.logging.log4j.core.LoggerContext (Extension)
-> org.apache.logging.log4j.core.config.json.JsonConfiguration (Extension)
-> com.fasterxml.jackson.databind.ObjectMapper (Extension)
-> com.fasterxml.jackson.databind.deser.BeanDeserializerFactory (Extension)
-> ❌ com.fasterxml.jackson.databind.deser.BeanDeserializer (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<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>
<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>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-web): 2.6.12</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2022-42003</summary>
### Vulnerable Library - <b>jackson-databind-2.13.0.jar</b></p>
<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: /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.13.0/889672a1721d6d85b2834fcd29d3fda92c8c8891/jackson-databind-2.13.0.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.6.1.jar (Root Library)
- spring-boot-starter-json-2.6.1.jar
- :x: **jackson-databind-2.13.0.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
fr.christophetd.log4shell.vulnerableapp.MainController (Application)
-> org.apache.logging.log4j.LogManager (Extension)
-> org.apache.logging.log4j.core.async.AsyncLoggerContext (Extension)
-> org.apache.logging.log4j.core.config.Configuration (Extension)
-> org.apache.logging.log4j.core.jackson.LogEventWithContextListMixIn (Extension)
-> org.apache.logging.log4j.core.jackson.ContextDataAsEntryListDeserializer (Extension)
-> ❌ com.fasterxml.jackson.databind.deser.std.StdDeserializer (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
In FasterXML jackson-databind before 2.14.0-rc1, resource exhaustion can occur because of a lack of a check in primitive value deserializers to avoid deep wrapper array nesting, when the UNWRAP_SINGLE_VALUE_ARRAYS feature is enabled. Additional fix version in 2.13.4.1 and 2.12.17.1
<p>Publish Date: 2022-10-02
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-42003>CVE-2022-42003</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>Release Date: 2022-10-02</p>
<p>Fix Resolution (com.fasterxml.jackson.core:jackson-databind): 2.13.4.1</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.6.15</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2020-36518</summary>
### Vulnerable Library - <b>jackson-databind-2.13.0.jar</b></p>
<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: /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.13.0/889672a1721d6d85b2834fcd29d3fda92c8c8891/jackson-databind-2.13.0.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.6.1.jar (Root Library)
- spring-boot-starter-json-2.6.1.jar
- :x: **jackson-databind-2.13.0.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
fr.christophetd.log4shell.vulnerableapp.MainController (Application)
-> org.apache.logging.log4j.LogManager (Extension)
-> org.apache.logging.log4j.core.LoggerContext (Extension)
-> com.fasterxml.jackson.databind.ObjectMapper (Extension)
...
-> com.fasterxml.jackson.databind.deser.BasicDeserializerFactory (Extension)
-> com.fasterxml.jackson.databind.deser.std.UntypedObjectDeserializer (Extension)
-> ❌ com.fasterxml.jackson.databind.deser.std.UntypedObjectDeserializer$Vanilla (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
jackson-databind before 2.13.0 allows a Java StackOverflow exception and denial of service via a large depth of nested objects.
Mend Note: After conducting further research, Mend has determined that all versions of com.fasterxml.jackson.core:jackson-databind up to version 2.13.2 are vulnerable to CVE-2020-36518.
<p>Publish Date: 2022-03-11
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-36518>CVE-2020-36518</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>Release Date: 2022-03-11</p>
<p>Fix Resolution (com.fasterxml.jackson.core:jackson-databind): 2.13.2.1</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.6.8</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2023-24998</summary>
### Vulnerable Library - <b>tomcat-embed-core-9.0.55.jar</b></p>
<p>Core Tomcat implementation</p>
<p>Library home page: <a href="https://tomcat.apache.org/">https://tomcat.apache.org/</a></p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.tomcat.embed/tomcat-embed-core/9.0.55/6ab68425d34f35e93cf97e1950c2c710161d8ce1/tomcat-embed-core-9.0.55.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.6.1.jar (Root Library)
- spring-boot-starter-tomcat-2.6.1.jar
- :x: **tomcat-embed-core-9.0.55.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Apache Commons FileUpload before 1.5 does not limit the number of request parts to be processed resulting in the possibility of an attacker triggering a DoS with a malicious upload or series of uploads.
Note that, like all of the file upload limits, the
new configuration option (FileUploadBase#setFileCountMax) is not
enabled by default and must be explicitly configured.
<p>Publish Date: 2023-02-20
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-24998>CVE-2023-24998</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://tomcat.apache.org/security-10.html">https://tomcat.apache.org/security-10.html</a></p>
<p>Release Date: 2023-02-20</p>
<p>Fix Resolution (org.apache.tomcat.embed:tomcat-embed-core): 9.0.71</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.6.15</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2021-46877</summary>
### Vulnerable Library - <b>jackson-databind-2.13.0.jar</b></p>
<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: /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.13.0/889672a1721d6d85b2834fcd29d3fda92c8c8891/jackson-databind-2.13.0.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.6.1.jar (Root Library)
- spring-boot-starter-json-2.6.1.jar
- :x: **jackson-databind-2.13.0.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
fr.christophetd.log4shell.vulnerableapp.MainController (Application)
-> org.apache.logging.log4j.Logger (Extension)
-> org.apache.logging.log4j.Level (Extension)
-> com.fasterxml.jackson.databind.DeserializationContext (Extension)
...
-> com.fasterxml.jackson.databind.node.ValueNode (Extension)
-> com.fasterxml.jackson.databind.node.BaseJsonNode (Extension)
-> ❌ com.fasterxml.jackson.databind.node.NodeSerialization (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
jackson-databind 2.10.x through 2.12.x before 2.12.6 and 2.13.x before 2.13.1 allows attackers to cause a denial of service (2 GB transient heap usage per read) in uncommon situations involving JsonNode JDK serialization.
<p>Publish Date: 2023-03-18
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-46877>CVE-2021-46877</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://www.cve.org/CVERecord?id=CVE-2021-46877">https://www.cve.org/CVERecord?id=CVE-2021-46877</a></p>
<p>Release Date: 2023-03-18</p>
<p>Fix Resolution (com.fasterxml.jackson.core:jackson-databind): 2.13.1</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.6.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2022-22950</summary>
### Vulnerable Library - <b>spring-expression-5.3.13.jar</b></p>
<p>Spring Expression Language (SpEL)</p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-expression/5.3.13/8f7448f4fb296a92855fd0afea3375ce41061e84/spring-expression-5.3.13.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.6.1.jar (Root Library)
- spring-webmvc-5.3.13.jar
- :x: **spring-expression-5.3.13.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
fr.christophetd.log4shell.vulnerableapp.VulnerableAppApplication (Application)
-> org.springframework.boot.SpringApplication (Extension)
-> org.springframework.context.annotation.AnnotationConfigUtils (Extension)
-> org.springframework.context.event.EventExpressionEvaluator (Extension)
...
-> org.springframework.expression.spel.support.StandardEvaluationContext (Extension)
-> org.springframework.expression.spel.support.StandardTypeComparator (Extension)
-> ❌ org.springframework.expression.spel.SpelMessage (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
n Spring Framework versions 5.3.0 - 5.3.16 and older unsupported versions, it is possible for a user to provide a specially crafted SpEL expression that may cause a denial of service condition.
<p>Publish Date: 2022-04-01
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-22950>CVE-2022-22950</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.5</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: 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://tanzu.vmware.com/security/cve-2022-22950">https://tanzu.vmware.com/security/cve-2022-22950</a></p>
<p>Release Date: 2022-04-01</p>
<p>Fix Resolution (org.springframework:spring-expression): 5.3.17</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.6.5</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2023-20861</summary>
### Vulnerable Library - <b>spring-expression-5.3.13.jar</b></p>
<p>Spring Expression Language (SpEL)</p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-expression/5.3.13/8f7448f4fb296a92855fd0afea3375ce41061e84/spring-expression-5.3.13.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.6.1.jar (Root Library)
- spring-webmvc-5.3.13.jar
- :x: **spring-expression-5.3.13.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
fr.christophetd.log4shell.vulnerableapp.VulnerableAppApplication (Application)
-> org.springframework.boot.autoconfigure.SpringBootApplication (Extension)
-> org.springframework.boot.autoconfigure.AutoConfigurationImportSelector (Extension)
-> org.springframework.context.event.ApplicationListenerMethodAdapter (Extension)
...
-> org.springframework.expression.spel.standard.SpelExpressionParser (Extension)
-> org.springframework.expression.spel.standard.InternalSpelExpressionParser (Extension)
-> ❌ org.springframework.expression.spel.ast.OperatorMatches (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
In Spring Framework versions 6.0.0 - 6.0.6, 5.3.0 - 5.3.25, 5.2.0.RELEASE - 5.2.22.RELEASE, and older unsupported versions, it is possible for a user to provide a specially crafted SpEL expression that may cause a denial-of-service (DoS) condition.
<p>Publish Date: 2023-03-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-20861>CVE-2023-20861</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.5</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: 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://spring.io/security/cve-2023-20861">https://spring.io/security/cve-2023-20861</a></p>
<p>Release Date: 2023-03-23</p>
<p>Fix Resolution (org.springframework:spring-expression): 5.3.26</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.6.15</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2023-20863</summary>
### Vulnerable Library - <b>spring-expression-5.3.13.jar</b></p>
<p>Spring Expression Language (SpEL)</p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-expression/5.3.13/8f7448f4fb296a92855fd0afea3375ce41061e84/spring-expression-5.3.13.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.6.1.jar (Root Library)
- spring-webmvc-5.3.13.jar
- :x: **spring-expression-5.3.13.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
fr.christophetd.log4shell.vulnerableapp.VulnerableAppApplication (Application)
-> org.springframework.boot.SpringApplication (Extension)
-> org.springframework.context.annotation.AnnotationConfigUtils (Extension)
-> org.springframework.context.event.EventExpressionEvaluator (Extension)
...
-> org.springframework.expression.spel.support.StandardEvaluationContext (Extension)
-> org.springframework.expression.spel.support.StandardTypeComparator (Extension)
-> ❌ org.springframework.expression.spel.SpelMessage (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
In spring framework versions prior to 5.2.24 release+ ,5.3.27+ and 6.0.8+ , it is possible for a user to provide a specially crafted SpEL expression that may cause a denial-of-service (DoS) condition.
<p>Publish Date: 2023-04-13
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-20863>CVE-2023-20863</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.5</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: 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://spring.io/security/cve-2023-20863">https://spring.io/security/cve-2023-20863</a></p>
<p>Release Date: 2023-04-13</p>
<p>Fix Resolution (org.springframework:spring-expression): 5.3.27</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.6.15</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2022-22968</summary>
### Vulnerable Library - <b>spring-context-5.3.13.jar</b></p>
<p>Spring Context</p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-context/5.3.13/e328db1c30ffe1c58328e4ab42cd3855a5307469/spring-context-5.3.13.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.6.1.jar (Root Library)
- spring-webmvc-5.3.13.jar
- :x: **spring-context-5.3.13.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
fr.christophetd.log4shell.vulnerableapp.VulnerableAppApplication (Application)
-> org.springframework.boot.SpringApplication (Extension)
-> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory (Extension)
-> org.springframework.web.servlet.mvc.method.annotation.MvcUriComponentsBuilder (Extension)
...
-> org.springframework.web.method.annotation.AbstractNamedValueMethodArgumentResolver (Extension)
-> org.springframework.web.bind.WebDataBinder (Extension)
-> ❌ org.springframework.validation.DataBinder (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
In Spring Framework versions 5.3.0 - 5.3.18, 5.2.0 - 5.2.20, and older unsupported versions, the patterns for disallowedFields on a DataBinder are case sensitive which means a field is not effectively protected unless it is listed with both upper and lower case for the first character of the field, including upper and lower case for the first character of all nested fields within the property path.
<p>Publish Date: 2022-04-14
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-22968>CVE-2022-22968</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.3</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: 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://tanzu.vmware.com/security/cve-2022-22968">https://tanzu.vmware.com/security/cve-2022-22968</a></p>
<p>Release Date: 2022-04-14</p>
<p>Fix Resolution (org.springframework:spring-context): 5.3.19</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.6.7</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2022-22970</summary>
### Vulnerable Libraries - <b>spring-beans-5.3.13.jar</b>, <b>spring-core-5.3.13.jar</b></p>
<p>
### <b>spring-beans-5.3.13.jar</b></p>
<p>Spring Beans</p>
<p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-beans/5.3.13/1d90c96b287253ec371260c35fbbea719c24bad6/spring-beans-5.3.13.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.6.1.jar (Root Library)
- spring-webmvc-5.3.13.jar
- :x: **spring-beans-5.3.13.jar** (Vulnerable Library)
### <b>spring-core-5.3.13.jar</b></p>
<p>Spring Core</p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-core/5.3.13/d2a6c3372dd337e08144f9f49f386b8ec7a8080d/spring-core-5.3.13.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.6.1.jar (Root Library)
- spring-webmvc-5.3.13.jar
- :x: **spring-core-5.3.13.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
fr.christophetd.log4shell.vulnerableapp.VulnerableAppApplication (Application)
-> org.springframework.boot.SpringApplication (Extension)
-> ❌ org.springframework.beans.CachedIntrospectionResults (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
In spring framework versions prior to 5.3.20+ , 5.2.22+ and old unsupported versions, applications that handle file uploads are vulnerable to DoS attack if they rely on data binding to set a MultipartFile or javax.servlet.Part to a field in a model object.
<p>Publish Date: 2022-05-12
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-22970>CVE-2022-22970</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.3</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- 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://tanzu.vmware.com/security/cve-2022-22970">https://tanzu.vmware.com/security/cve-2022-22970</a></p>
<p>Release Date: 2022-05-12</p>
<p>Fix Resolution (org.springframework:spring-beans): 5.3.20</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.6.8</p><p>Fix Resolution (org.springframework:spring-core): 5.3.20</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.6.8</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2021-22060</summary>
### Vulnerable Libraries - <b>spring-core-5.3.13.jar</b>, <b>spring-web-5.3.13.jar</b></p>
<p>
### <b>spring-core-5.3.13.jar</b></p>
<p>Spring Core</p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-core/5.3.13/d2a6c3372dd337e08144f9f49f386b8ec7a8080d/spring-core-5.3.13.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.6.1.jar (Root Library)
- spring-webmvc-5.3.13.jar
- :x: **spring-core-5.3.13.jar** (Vulnerable Library)
### <b>spring-web-5.3.13.jar</b></p>
<p>Spring Web</p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-web/5.3.13/66d95a5d2d436961b4cae036723f4c7a764fc14c/spring-web-5.3.13.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.6.1.jar (Root Library)
- :x: **spring-web-5.3.13.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Spring Framework versions 5.3.0 - 5.3.13, 5.2.0 - 5.2.18, and older unsupported versions, it is possible for a user to provide malicious input to cause the insertion of additional log entries. This is a follow-up to CVE-2021-22096 that protects against additional types of input and in more places of the Spring Framework codebase.
<p>Publish Date: 2022-01-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-22060>CVE-2021-22060</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>4.3</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: None
- 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://spring.io/security/cve-2021-22060">https://spring.io/security/cve-2021-22060</a></p>
<p>Release Date: 2022-01-10</p>
<p>Fix Resolution (org.springframework:spring-core): 5.3.14</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.6.2</p><p>Fix Resolution (org.springframework:spring-web): 5.3.14</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.6.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p>
|
True
|
spring-boot-starter-web-2.6.1.jar: 13 vulnerabilities (highest severity is: 9.8) reachable - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-boot-starter-web-2.6.1.jar</b></p></summary>
<p></p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-core/5.3.13/d2a6c3372dd337e08144f9f49f386b8ec7a8080d/spring-core-5.3.13.jar</p>
<p>
</details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (spring-boot-starter-web version) | Remediation Available | Reachability |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- | --- |
| [CVE-2022-22965](https://www.mend.io/vulnerability-database/CVE-2022-22965) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.8 | spring-beans-5.3.13.jar | Transitive | 2.6.6 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2022-1471](https://www.mend.io/vulnerability-database/CVE-2022-1471) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.8 | snakeyaml-1.29.jar | Transitive | N/A* | ❌|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20>](## 'The vulnerability is non-reachable.')</a></p> |
| [CVE-2022-42004](https://www.mend.io/vulnerability-database/CVE-2022-42004) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | jackson-databind-2.13.0.jar | Transitive | 2.6.12 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2022-42003](https://www.mend.io/vulnerability-database/CVE-2022-42003) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | jackson-databind-2.13.0.jar | Transitive | 2.6.15 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2020-36518](https://www.mend.io/vulnerability-database/CVE-2020-36518) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | jackson-databind-2.13.0.jar | Transitive | 2.6.8 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2023-24998](https://www.mend.io/vulnerability-database/CVE-2023-24998) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | tomcat-embed-core-9.0.55.jar | Transitive | 2.6.15 | ✅ |
| [CVE-2021-46877](https://www.mend.io/vulnerability-database/CVE-2021-46877) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | jackson-databind-2.13.0.jar | Transitive | 2.6.2 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2022-22950](https://www.mend.io/vulnerability-database/CVE-2022-22950) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.5 | spring-expression-5.3.13.jar | Transitive | 2.6.5 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2023-20861](https://www.mend.io/vulnerability-database/CVE-2023-20861) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.5 | spring-expression-5.3.13.jar | Transitive | 2.6.15 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2023-20863](https://www.mend.io/vulnerability-database/CVE-2023-20863) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.5 | spring-expression-5.3.13.jar | Transitive | 2.6.15 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2022-22968](https://www.mend.io/vulnerability-database/CVE-2022-22968) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.3 | spring-context-5.3.13.jar | Transitive | 2.6.7 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2022-22970](https://www.mend.io/vulnerability-database/CVE-2022-22970) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.3 | detected in multiple dependencies | Transitive | 2.6.8 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-22060](https://www.mend.io/vulnerability-database/CVE-2021-22060) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 4.3 | detected in multiple dependencies | Transitive | 2.6.2 | ✅ |
<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/critical_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2022-22965</summary>
### Vulnerable Library - <b>spring-beans-5.3.13.jar</b></p>
<p>Spring Beans</p>
<p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-beans/5.3.13/1d90c96b287253ec371260c35fbbea719c24bad6/spring-beans-5.3.13.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.6.1.jar (Root Library)
- spring-webmvc-5.3.13.jar
- :x: **spring-beans-5.3.13.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
fr.christophetd.log4shell.vulnerableapp.VulnerableAppApplication (Application)
-> org.springframework.boot.SpringApplication (Extension)
-> ❌ org.springframework.beans.CachedIntrospectionResults (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
A Spring MVC or Spring WebFlux application running on JDK 9+ may be vulnerable to remote code execution (RCE) via data binding. The specific exploit requires the application to run on Tomcat as a WAR deployment. If the application is deployed as a Spring Boot executable jar, i.e. the default, it is not vulnerable to the exploit. However, the nature of the vulnerability is more general, and there may be other ways to exploit it.
Mend Note: Converted from WS-2022-0107, on 2022-11-07.
<p>Publish Date: 2022-04-01
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-22965>CVE-2022-22965</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</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: 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://spring.io/blog/2022/03/31/spring-framework-rce-early-announcement">https://spring.io/blog/2022/03/31/spring-framework-rce-early-announcement</a></p>
<p>Release Date: 2022-04-01</p>
<p>Fix Resolution (org.springframework:spring-beans): 5.3.18</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.6.6</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20> CVE-2022-1471</summary>
### Vulnerable Library - <b>snakeyaml-1.29.jar</b></p>
<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href="http://www.snakeyaml.org">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.yaml/snakeyaml/1.29/6d0cdafb2010f1297e574656551d7145240f6e25/snakeyaml-1.29.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.6.1.jar (Root Library)
- spring-boot-starter-2.6.1.jar
- :x: **snakeyaml-1.29.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
<p>The vulnerable code is not reachable.</p>
</p>
<p></p>
### Vulnerability Details
<p>
SnakeYaml's Constructor() class does not restrict types which can be instantiated during deserialization. Deserializing yaml content provided by an attacker can lead to remote code execution. We recommend using SnakeYaml's SafeConsturctor when parsing untrusted content to restrict deserialization. We recommend upgrading to version 2.0 and beyond.
<p>Publish Date: 2022-12-01
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-1471>CVE-2022-1471</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</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: 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://bitbucket.org/snakeyaml/snakeyaml/issues/561/cve-2022-1471-vulnerability-in#comment-64634374">https://bitbucket.org/snakeyaml/snakeyaml/issues/561/cve-2022-1471-vulnerability-in#comment-64634374</a></p>
<p>Release Date: 2022-12-01</p>
<p>Fix Resolution: org.yaml:snakeyaml:2.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2022-42004</summary>
### Vulnerable Library - <b>jackson-databind-2.13.0.jar</b></p>
<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: /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.13.0/889672a1721d6d85b2834fcd29d3fda92c8c8891/jackson-databind-2.13.0.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.6.1.jar (Root Library)
- spring-boot-starter-json-2.6.1.jar
- :x: **jackson-databind-2.13.0.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
fr.christophetd.log4shell.vulnerableapp.MainController (Application)
-> org.apache.logging.log4j.LogManager (Extension)
-> org.apache.logging.log4j.core.LoggerContext (Extension)
-> org.apache.logging.log4j.core.config.json.JsonConfiguration (Extension)
-> com.fasterxml.jackson.databind.ObjectMapper (Extension)
-> com.fasterxml.jackson.databind.deser.BeanDeserializerFactory (Extension)
-> ❌ com.fasterxml.jackson.databind.deser.BeanDeserializer (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<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>
<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>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-web): 2.6.12</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2022-42003</summary>
### Vulnerable Library - <b>jackson-databind-2.13.0.jar</b></p>
<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: /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.13.0/889672a1721d6d85b2834fcd29d3fda92c8c8891/jackson-databind-2.13.0.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.6.1.jar (Root Library)
- spring-boot-starter-json-2.6.1.jar
- :x: **jackson-databind-2.13.0.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
fr.christophetd.log4shell.vulnerableapp.MainController (Application)
-> org.apache.logging.log4j.LogManager (Extension)
-> org.apache.logging.log4j.core.async.AsyncLoggerContext (Extension)
-> org.apache.logging.log4j.core.config.Configuration (Extension)
-> org.apache.logging.log4j.core.jackson.LogEventWithContextListMixIn (Extension)
-> org.apache.logging.log4j.core.jackson.ContextDataAsEntryListDeserializer (Extension)
-> ❌ com.fasterxml.jackson.databind.deser.std.StdDeserializer (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
In FasterXML jackson-databind before 2.14.0-rc1, resource exhaustion can occur because of a lack of a check in primitive value deserializers to avoid deep wrapper array nesting, when the UNWRAP_SINGLE_VALUE_ARRAYS feature is enabled. Additional fix version in 2.13.4.1 and 2.12.17.1
<p>Publish Date: 2022-10-02
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-42003>CVE-2022-42003</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>Release Date: 2022-10-02</p>
<p>Fix Resolution (com.fasterxml.jackson.core:jackson-databind): 2.13.4.1</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.6.15</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2020-36518</summary>
### Vulnerable Library - <b>jackson-databind-2.13.0.jar</b></p>
<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: /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.13.0/889672a1721d6d85b2834fcd29d3fda92c8c8891/jackson-databind-2.13.0.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.6.1.jar (Root Library)
- spring-boot-starter-json-2.6.1.jar
- :x: **jackson-databind-2.13.0.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
fr.christophetd.log4shell.vulnerableapp.MainController (Application)
-> org.apache.logging.log4j.LogManager (Extension)
-> org.apache.logging.log4j.core.LoggerContext (Extension)
-> com.fasterxml.jackson.databind.ObjectMapper (Extension)
...
-> com.fasterxml.jackson.databind.deser.BasicDeserializerFactory (Extension)
-> com.fasterxml.jackson.databind.deser.std.UntypedObjectDeserializer (Extension)
-> ❌ com.fasterxml.jackson.databind.deser.std.UntypedObjectDeserializer$Vanilla (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
jackson-databind before 2.13.0 allows a Java StackOverflow exception and denial of service via a large depth of nested objects.
Mend Note: After conducting further research, Mend has determined that all versions of com.fasterxml.jackson.core:jackson-databind up to version 2.13.2 are vulnerable to CVE-2020-36518.
<p>Publish Date: 2022-03-11
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-36518>CVE-2020-36518</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>Release Date: 2022-03-11</p>
<p>Fix Resolution (com.fasterxml.jackson.core:jackson-databind): 2.13.2.1</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.6.8</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2023-24998</summary>
### Vulnerable Library - <b>tomcat-embed-core-9.0.55.jar</b></p>
<p>Core Tomcat implementation</p>
<p>Library home page: <a href="https://tomcat.apache.org/">https://tomcat.apache.org/</a></p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.tomcat.embed/tomcat-embed-core/9.0.55/6ab68425d34f35e93cf97e1950c2c710161d8ce1/tomcat-embed-core-9.0.55.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.6.1.jar (Root Library)
- spring-boot-starter-tomcat-2.6.1.jar
- :x: **tomcat-embed-core-9.0.55.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Apache Commons FileUpload before 1.5 does not limit the number of request parts to be processed resulting in the possibility of an attacker triggering a DoS with a malicious upload or series of uploads.
Note that, like all of the file upload limits, the
new configuration option (FileUploadBase#setFileCountMax) is not
enabled by default and must be explicitly configured.
<p>Publish Date: 2023-02-20
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-24998>CVE-2023-24998</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://tomcat.apache.org/security-10.html">https://tomcat.apache.org/security-10.html</a></p>
<p>Release Date: 2023-02-20</p>
<p>Fix Resolution (org.apache.tomcat.embed:tomcat-embed-core): 9.0.71</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.6.15</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2021-46877</summary>
### Vulnerable Library - <b>jackson-databind-2.13.0.jar</b></p>
<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: /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.13.0/889672a1721d6d85b2834fcd29d3fda92c8c8891/jackson-databind-2.13.0.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.6.1.jar (Root Library)
- spring-boot-starter-json-2.6.1.jar
- :x: **jackson-databind-2.13.0.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
fr.christophetd.log4shell.vulnerableapp.MainController (Application)
-> org.apache.logging.log4j.Logger (Extension)
-> org.apache.logging.log4j.Level (Extension)
-> com.fasterxml.jackson.databind.DeserializationContext (Extension)
...
-> com.fasterxml.jackson.databind.node.ValueNode (Extension)
-> com.fasterxml.jackson.databind.node.BaseJsonNode (Extension)
-> ❌ com.fasterxml.jackson.databind.node.NodeSerialization (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
jackson-databind 2.10.x through 2.12.x before 2.12.6 and 2.13.x before 2.13.1 allows attackers to cause a denial of service (2 GB transient heap usage per read) in uncommon situations involving JsonNode JDK serialization.
<p>Publish Date: 2023-03-18
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-46877>CVE-2021-46877</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://www.cve.org/CVERecord?id=CVE-2021-46877">https://www.cve.org/CVERecord?id=CVE-2021-46877</a></p>
<p>Release Date: 2023-03-18</p>
<p>Fix Resolution (com.fasterxml.jackson.core:jackson-databind): 2.13.1</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.6.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2022-22950</summary>
### Vulnerable Library - <b>spring-expression-5.3.13.jar</b></p>
<p>Spring Expression Language (SpEL)</p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-expression/5.3.13/8f7448f4fb296a92855fd0afea3375ce41061e84/spring-expression-5.3.13.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.6.1.jar (Root Library)
- spring-webmvc-5.3.13.jar
- :x: **spring-expression-5.3.13.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
fr.christophetd.log4shell.vulnerableapp.VulnerableAppApplication (Application)
-> org.springframework.boot.SpringApplication (Extension)
-> org.springframework.context.annotation.AnnotationConfigUtils (Extension)
-> org.springframework.context.event.EventExpressionEvaluator (Extension)
...
-> org.springframework.expression.spel.support.StandardEvaluationContext (Extension)
-> org.springframework.expression.spel.support.StandardTypeComparator (Extension)
-> ❌ org.springframework.expression.spel.SpelMessage (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
n Spring Framework versions 5.3.0 - 5.3.16 and older unsupported versions, it is possible for a user to provide a specially crafted SpEL expression that may cause a denial of service condition.
<p>Publish Date: 2022-04-01
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-22950>CVE-2022-22950</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.5</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: 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://tanzu.vmware.com/security/cve-2022-22950">https://tanzu.vmware.com/security/cve-2022-22950</a></p>
<p>Release Date: 2022-04-01</p>
<p>Fix Resolution (org.springframework:spring-expression): 5.3.17</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.6.5</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2023-20861</summary>
### Vulnerable Library - <b>spring-expression-5.3.13.jar</b></p>
<p>Spring Expression Language (SpEL)</p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-expression/5.3.13/8f7448f4fb296a92855fd0afea3375ce41061e84/spring-expression-5.3.13.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.6.1.jar (Root Library)
- spring-webmvc-5.3.13.jar
- :x: **spring-expression-5.3.13.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
fr.christophetd.log4shell.vulnerableapp.VulnerableAppApplication (Application)
-> org.springframework.boot.autoconfigure.SpringBootApplication (Extension)
-> org.springframework.boot.autoconfigure.AutoConfigurationImportSelector (Extension)
-> org.springframework.context.event.ApplicationListenerMethodAdapter (Extension)
...
-> org.springframework.expression.spel.standard.SpelExpressionParser (Extension)
-> org.springframework.expression.spel.standard.InternalSpelExpressionParser (Extension)
-> ❌ org.springframework.expression.spel.ast.OperatorMatches (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
In Spring Framework versions 6.0.0 - 6.0.6, 5.3.0 - 5.3.25, 5.2.0.RELEASE - 5.2.22.RELEASE, and older unsupported versions, it is possible for a user to provide a specially crafted SpEL expression that may cause a denial-of-service (DoS) condition.
<p>Publish Date: 2023-03-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-20861>CVE-2023-20861</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.5</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: 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://spring.io/security/cve-2023-20861">https://spring.io/security/cve-2023-20861</a></p>
<p>Release Date: 2023-03-23</p>
<p>Fix Resolution (org.springframework:spring-expression): 5.3.26</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.6.15</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2023-20863</summary>
### Vulnerable Library - <b>spring-expression-5.3.13.jar</b></p>
<p>Spring Expression Language (SpEL)</p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-expression/5.3.13/8f7448f4fb296a92855fd0afea3375ce41061e84/spring-expression-5.3.13.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.6.1.jar (Root Library)
- spring-webmvc-5.3.13.jar
- :x: **spring-expression-5.3.13.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
fr.christophetd.log4shell.vulnerableapp.VulnerableAppApplication (Application)
-> org.springframework.boot.SpringApplication (Extension)
-> org.springframework.context.annotation.AnnotationConfigUtils (Extension)
-> org.springframework.context.event.EventExpressionEvaluator (Extension)
...
-> org.springframework.expression.spel.support.StandardEvaluationContext (Extension)
-> org.springframework.expression.spel.support.StandardTypeComparator (Extension)
-> ❌ org.springframework.expression.spel.SpelMessage (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
In spring framework versions prior to 5.2.24 release+ ,5.3.27+ and 6.0.8+ , it is possible for a user to provide a specially crafted SpEL expression that may cause a denial-of-service (DoS) condition.
<p>Publish Date: 2023-04-13
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-20863>CVE-2023-20863</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.5</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: 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://spring.io/security/cve-2023-20863">https://spring.io/security/cve-2023-20863</a></p>
<p>Release Date: 2023-04-13</p>
<p>Fix Resolution (org.springframework:spring-expression): 5.3.27</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.6.15</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2022-22968</summary>
### Vulnerable Library - <b>spring-context-5.3.13.jar</b></p>
<p>Spring Context</p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-context/5.3.13/e328db1c30ffe1c58328e4ab42cd3855a5307469/spring-context-5.3.13.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.6.1.jar (Root Library)
- spring-webmvc-5.3.13.jar
- :x: **spring-context-5.3.13.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
fr.christophetd.log4shell.vulnerableapp.VulnerableAppApplication (Application)
-> org.springframework.boot.SpringApplication (Extension)
-> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory (Extension)
-> org.springframework.web.servlet.mvc.method.annotation.MvcUriComponentsBuilder (Extension)
...
-> org.springframework.web.method.annotation.AbstractNamedValueMethodArgumentResolver (Extension)
-> org.springframework.web.bind.WebDataBinder (Extension)
-> ❌ org.springframework.validation.DataBinder (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
In Spring Framework versions 5.3.0 - 5.3.18, 5.2.0 - 5.2.20, and older unsupported versions, the patterns for disallowedFields on a DataBinder are case sensitive which means a field is not effectively protected unless it is listed with both upper and lower case for the first character of the field, including upper and lower case for the first character of all nested fields within the property path.
<p>Publish Date: 2022-04-14
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-22968>CVE-2022-22968</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.3</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: 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://tanzu.vmware.com/security/cve-2022-22968">https://tanzu.vmware.com/security/cve-2022-22968</a></p>
<p>Release Date: 2022-04-14</p>
<p>Fix Resolution (org.springframework:spring-context): 5.3.19</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.6.7</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2022-22970</summary>
### Vulnerable Libraries - <b>spring-beans-5.3.13.jar</b>, <b>spring-core-5.3.13.jar</b></p>
<p>
### <b>spring-beans-5.3.13.jar</b></p>
<p>Spring Beans</p>
<p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-beans/5.3.13/1d90c96b287253ec371260c35fbbea719c24bad6/spring-beans-5.3.13.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.6.1.jar (Root Library)
- spring-webmvc-5.3.13.jar
- :x: **spring-beans-5.3.13.jar** (Vulnerable Library)
### <b>spring-core-5.3.13.jar</b></p>
<p>Spring Core</p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-core/5.3.13/d2a6c3372dd337e08144f9f49f386b8ec7a8080d/spring-core-5.3.13.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.6.1.jar (Root Library)
- spring-webmvc-5.3.13.jar
- :x: **spring-core-5.3.13.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
fr.christophetd.log4shell.vulnerableapp.VulnerableAppApplication (Application)
-> org.springframework.boot.SpringApplication (Extension)
-> ❌ org.springframework.beans.CachedIntrospectionResults (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
In spring framework versions prior to 5.3.20+ , 5.2.22+ and old unsupported versions, applications that handle file uploads are vulnerable to DoS attack if they rely on data binding to set a MultipartFile or javax.servlet.Part to a field in a model object.
<p>Publish Date: 2022-05-12
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-22970>CVE-2022-22970</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.3</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- 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://tanzu.vmware.com/security/cve-2022-22970">https://tanzu.vmware.com/security/cve-2022-22970</a></p>
<p>Release Date: 2022-05-12</p>
<p>Fix Resolution (org.springframework:spring-beans): 5.3.20</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.6.8</p><p>Fix Resolution (org.springframework:spring-core): 5.3.20</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.6.8</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2021-22060</summary>
### Vulnerable Libraries - <b>spring-core-5.3.13.jar</b>, <b>spring-web-5.3.13.jar</b></p>
<p>
### <b>spring-core-5.3.13.jar</b></p>
<p>Spring Core</p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-core/5.3.13/d2a6c3372dd337e08144f9f49f386b8ec7a8080d/spring-core-5.3.13.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.6.1.jar (Root Library)
- spring-webmvc-5.3.13.jar
- :x: **spring-core-5.3.13.jar** (Vulnerable Library)
### <b>spring-web-5.3.13.jar</b></p>
<p>Spring Web</p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-web/5.3.13/66d95a5d2d436961b4cae036723f4c7a764fc14c/spring-web-5.3.13.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.6.1.jar (Root Library)
- :x: **spring-web-5.3.13.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Spring Framework versions 5.3.0 - 5.3.13, 5.2.0 - 5.2.18, and older unsupported versions, it is possible for a user to provide malicious input to cause the insertion of additional log entries. This is a follow-up to CVE-2021-22096 that protects against additional types of input and in more places of the Spring Framework codebase.
<p>Publish Date: 2022-01-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-22060>CVE-2021-22060</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>4.3</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: None
- 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://spring.io/security/cve-2021-22060">https://spring.io/security/cve-2021-22060</a></p>
<p>Release Date: 2022-01-10</p>
<p>Fix Resolution (org.springframework:spring-core): 5.3.14</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.6.2</p><p>Fix Resolution (org.springframework:spring-web): 5.3.14</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.6.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p>
|
non_main
|
spring boot starter web jar vulnerabilities highest severity is reachable vulnerable library spring boot starter web jar path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org springframework spring core spring core jar vulnerabilities cve severity cvss dependency type fixed in spring boot starter web version remediation available reachability critical spring beans jar transitive the vulnerability is likely to be reachable critical snakeyaml jar transitive n a the vulnerability is non reachable high jackson databind jar transitive the vulnerability is likely to be reachable high jackson databind jar transitive the vulnerability is likely to be reachable high jackson databind jar transitive the vulnerability is likely to be reachable high tomcat embed core jar transitive high jackson databind jar transitive the vulnerability is likely to be reachable medium spring expression jar transitive the vulnerability is likely to be reachable medium spring expression jar transitive the vulnerability is likely to be reachable medium spring expression jar transitive the vulnerability is likely to be reachable medium spring context jar transitive the vulnerability is likely to be reachable medium detected in multiple dependencies transitive the vulnerability is likely to be reachable medium detected in multiple dependencies transitive 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 cve vulnerable library spring beans jar spring beans library home page a href path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org springframework spring beans spring beans jar dependency hierarchy spring boot starter web jar root library spring webmvc jar x spring beans jar vulnerable library found in base branch main reachability analysis this vulnerability is potentially used fr christophetd vulnerableapp vulnerableappapplication application org springframework boot springapplication extension ❌ org springframework beans cachedintrospectionresults vulnerable component vulnerability details a spring mvc or spring webflux application running on jdk may be vulnerable to remote code execution rce via data binding the specific exploit requires the application to run on tomcat as a war deployment if the application is deployed as a spring boot executable jar i e the default it is not vulnerable to the exploit however the nature of the vulnerability is more general and there may be other ways to exploit it mend note converted from ws on 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 org springframework spring beans direct dependency fix resolution org springframework boot spring boot starter web rescue worker helmet automatic remediation is available for this issue cve vulnerable library snakeyaml jar yaml parser and emitter for java library home page a href path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org yaml snakeyaml snakeyaml jar dependency hierarchy spring boot starter web jar root library spring boot starter jar x snakeyaml jar vulnerable library found in base branch main reachability analysis the vulnerable code is not reachable vulnerability details snakeyaml s constructor class does not restrict types which can be instantiated during deserialization deserializing yaml content provided by an attacker can lead to remote code execution we recommend using snakeyaml s safeconsturctor when parsing untrusted content to restrict deserialization we recommend upgrading to version and beyond 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 org yaml snakeyaml cve 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 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 web jar root library spring boot starter json jar x jackson databind jar vulnerable library found in base branch main reachability analysis this vulnerability is potentially used fr christophetd vulnerableapp maincontroller application org apache logging logmanager extension org apache logging core loggercontext extension org apache logging core config json jsonconfiguration extension com fasterxml jackson databind objectmapper extension com fasterxml jackson databind deser beandeserializerfactory extension ❌ com fasterxml jackson databind deser beandeserializer vulnerable component 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 web rescue worker helmet automatic remediation is available for this issue cve 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 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 web jar root library spring boot starter json jar x jackson databind jar vulnerable library found in base branch main reachability analysis this vulnerability is potentially used fr christophetd vulnerableapp maincontroller application org apache logging logmanager extension org apache logging core async asyncloggercontext extension org apache logging core config configuration extension org apache logging core jackson logeventwithcontextlistmixin extension org apache logging core jackson contextdataasentrylistdeserializer extension ❌ com fasterxml jackson databind deser std stddeserializer vulnerable component vulnerability details in fasterxml jackson databind before resource exhaustion can occur because of a lack of a check in primitive value deserializers to avoid deep wrapper array nesting when the unwrap single value arrays feature is enabled additional fix version in and 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 web rescue worker helmet automatic remediation is available for this issue cve 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 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 web jar root library spring boot starter json jar x jackson databind jar vulnerable library found in base branch main reachability analysis this vulnerability is potentially used fr christophetd vulnerableapp maincontroller application org apache logging logmanager extension org apache logging core loggercontext extension com fasterxml jackson databind objectmapper extension com fasterxml jackson databind deser basicdeserializerfactory extension com fasterxml jackson databind deser std untypedobjectdeserializer extension ❌ com fasterxml jackson databind deser std untypedobjectdeserializer vanilla vulnerable component vulnerability details jackson databind before allows a java stackoverflow exception and denial of service via a large depth of nested objects mend note after conducting further research mend has determined that all versions of com fasterxml jackson core jackson databind up to version are vulnerable to cve 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 web rescue worker helmet automatic remediation is available for this issue cve vulnerable library tomcat embed core jar core tomcat implementation library home page a href path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org apache tomcat embed tomcat embed core tomcat embed core jar dependency hierarchy spring boot starter web jar root library spring boot starter tomcat jar x tomcat embed core jar vulnerable library found in base branch main vulnerability details apache commons fileupload before does not limit the number of request parts to be processed resulting in the possibility of an attacker triggering a dos with a malicious upload or series of uploads note that like all of the file upload limits the new configuration option fileuploadbase setfilecountmax is not enabled by default and must be explicitly configured 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 org apache tomcat embed tomcat embed core direct dependency fix resolution org springframework boot spring boot starter web rescue worker helmet automatic remediation is available for this issue cve 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 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 web jar root library spring boot starter json jar x jackson databind jar vulnerable library found in base branch main reachability analysis this vulnerability is potentially used fr christophetd vulnerableapp maincontroller application org apache logging logger extension org apache logging level extension com fasterxml jackson databind deserializationcontext extension com fasterxml jackson databind node valuenode extension com fasterxml jackson databind node basejsonnode extension ❌ com fasterxml jackson databind node nodeserialization vulnerable component vulnerability details jackson databind x through x before and x before allows attackers to cause a denial of service gb transient heap usage per read in uncommon situations involving jsonnode jdk serialization 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 com fasterxml jackson core jackson databind direct dependency fix resolution org springframework boot spring boot starter web rescue worker helmet automatic remediation is available for this issue cve vulnerable library spring expression jar spring expression language spel path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org springframework spring expression spring expression jar dependency hierarchy spring boot starter web jar root library spring webmvc jar x spring expression jar vulnerable library found in base branch main reachability analysis this vulnerability is potentially used fr christophetd vulnerableapp vulnerableappapplication application org springframework boot springapplication extension org springframework context annotation annotationconfigutils extension org springframework context event eventexpressionevaluator extension org springframework expression spel support standardevaluationcontext extension org springframework expression spel support standardtypecomparator extension ❌ org springframework expression spel spelmessage vulnerable component vulnerability details n spring framework versions and older unsupported versions it is possible for a user to provide a specially crafted spel expression that may cause a denial of service condition 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 none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org springframework spring expression direct dependency fix resolution org springframework boot spring boot starter web rescue worker helmet automatic remediation is available for this issue cve vulnerable library spring expression jar spring expression language spel path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org springframework spring expression spring expression jar dependency hierarchy spring boot starter web jar root library spring webmvc jar x spring expression jar vulnerable library found in base branch main reachability analysis this vulnerability is potentially used fr christophetd vulnerableapp vulnerableappapplication application org springframework boot autoconfigure springbootapplication extension org springframework boot autoconfigure autoconfigurationimportselector extension org springframework context event applicationlistenermethodadapter extension org springframework expression spel standard spelexpressionparser extension org springframework expression spel standard internalspelexpressionparser extension ❌ org springframework expression spel ast operatormatches vulnerable component vulnerability details in spring framework versions release release and older unsupported versions it is possible for a user to provide a specially crafted spel expression that may cause a denial of service dos condition 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 none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org springframework spring expression direct dependency fix resolution org springframework boot spring boot starter web rescue worker helmet automatic remediation is available for this issue cve vulnerable library spring expression jar spring expression language spel path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org springframework spring expression spring expression jar dependency hierarchy spring boot starter web jar root library spring webmvc jar x spring expression jar vulnerable library found in base branch main reachability analysis this vulnerability is potentially used fr christophetd vulnerableapp vulnerableappapplication application org springframework boot springapplication extension org springframework context annotation annotationconfigutils extension org springframework context event eventexpressionevaluator extension org springframework expression spel support standardevaluationcontext extension org springframework expression spel support standardtypecomparator extension ❌ org springframework expression spel spelmessage vulnerable component vulnerability details in spring framework versions prior to release and it is possible for a user to provide a specially crafted spel expression that may cause a denial of service dos condition 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 none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org springframework spring expression direct dependency fix resolution org springframework boot spring boot starter web rescue worker helmet automatic remediation is available for this issue cve vulnerable library spring context jar spring context path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org springframework spring context spring context jar dependency hierarchy spring boot starter web jar root library spring webmvc jar x spring context jar vulnerable library found in base branch main reachability analysis this vulnerability is potentially used fr christophetd vulnerableapp vulnerableappapplication application org springframework boot springapplication extension org springframework beans factory support abstractautowirecapablebeanfactory extension org springframework web servlet mvc method annotation mvcuricomponentsbuilder extension org springframework web method annotation abstractnamedvaluemethodargumentresolver extension org springframework web bind webdatabinder extension ❌ org springframework validation databinder vulnerable component vulnerability details in spring framework versions and older unsupported versions the patterns for disallowedfields on a databinder are case sensitive which means a field is not effectively protected unless it is listed with both upper and lower case for the first character of the field including upper and lower case for the first character of all nested fields within the property path publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org springframework spring context direct dependency fix resolution org springframework boot spring boot starter web rescue worker helmet automatic remediation is available for this issue cve vulnerable libraries spring beans jar spring core jar spring beans jar spring beans library home page a href path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org springframework spring beans spring beans jar dependency hierarchy spring boot starter web jar root library spring webmvc jar x spring beans jar vulnerable library spring core jar spring core path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org springframework spring core spring core jar dependency hierarchy spring boot starter web jar root library spring webmvc jar x spring core jar vulnerable library found in base branch main reachability analysis this vulnerability is potentially used fr christophetd vulnerableapp vulnerableappapplication application org springframework boot springapplication extension ❌ org springframework beans cachedintrospectionresults vulnerable component vulnerability details in spring framework versions prior to and old unsupported versions applications that handle file uploads are vulnerable to dos attack if they rely on data binding to set a multipartfile or javax servlet part to a field in a model object publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required low 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 org springframework spring beans direct dependency fix resolution org springframework boot spring boot starter web fix resolution org springframework spring core direct dependency fix resolution org springframework boot spring boot starter web rescue worker helmet automatic remediation is available for this issue cve vulnerable libraries spring core jar spring web jar spring core jar spring core path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org springframework spring core spring core jar dependency hierarchy spring boot starter web jar root library spring webmvc jar x spring core jar vulnerable library spring web jar spring web path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org springframework spring web spring web jar dependency hierarchy spring boot starter web jar root library x spring web jar vulnerable library found in base branch main vulnerability details in spring framework versions and older unsupported versions it is possible for a user to provide malicious input to cause the insertion of additional log entries this is a follow up to cve that protects against additional types of input and in more places of the spring framework codebase 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 none integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org springframework spring core direct dependency fix resolution org springframework boot spring boot starter web fix resolution org springframework spring web direct dependency fix resolution org springframework boot spring boot starter web rescue worker helmet automatic remediation is available for this issue rescue worker helmet automatic remediation is available for this issue
| 0
|
31
| 2,550,391,538
|
IssuesEvent
|
2015-02-01 14:10:55
|
pychess/pychess
|
https://api.github.com/repos/pychess/pychess
|
closed
|
Log Viewer should nower be locked
|
bug Maintainability UI
|
Original [issue 147](https://code.google.com/p/pychess/issues/detail?id=147) created by @thomasahle:
**What steps will reproduce the problem?**
1. Open Pychess
2. Try to open the log viewer
**What is the expected output? What do you see instead?**
Log viewer is locked as a part of the view menu
**Please use labels and text to provide additional information.**
Instead of locking the entire view menu, we should only lock the nessesery
entries (all besides lock viewer) or perhaps we should move it to another
menu, but I can't imagine any one more obvious.
|
True
|
Log Viewer should nower be locked - Original [issue 147](https://code.google.com/p/pychess/issues/detail?id=147) created by @thomasahle:
**What steps will reproduce the problem?**
1. Open Pychess
2. Try to open the log viewer
**What is the expected output? What do you see instead?**
Log viewer is locked as a part of the view menu
**Please use labels and text to provide additional information.**
Instead of locking the entire view menu, we should only lock the nessesery
entries (all besides lock viewer) or perhaps we should move it to another
menu, but I can't imagine any one more obvious.
|
main
|
log viewer should nower be locked original created by thomasahle what steps will reproduce the problem open pychess try to open the log viewer what is the expected output what do you see instead log viewer is locked as a part of the view menu please use labels and text to provide additional information instead of locking the entire view menu we should only lock the nessesery entries all besides lock viewer or perhaps we should move it to another menu but i can t imagine any one more obvious
| 1
|
1,135
| 4,998,638,906
|
IssuesEvent
|
2016-12-09 20:31:05
|
ansible/ansible-modules-core
|
https://api.github.com/repos/ansible/ansible-modules-core
|
closed
|
ec2 module: profile option ignored
|
affects_1.9 aws bug_report cloud waiting_on_maintainer
|
**Issue Type**: Bug Report
**Ansible Version**: 1.9
**Ansible Configuration**: default
**Environment**: OSX 10.9.5
**Summary**: The "profile" option in the ec2 module is ignored
**Steps To Reproduce**:
Create a playbook like so and run it. The account in which `subnet-0000000` exists must not be in your default aws profile (defined in `~/.aws/{credentials,config}`:
```
- name: Make an instance
hosts: all
connection: local
gather_facts: False
tasks:
- name: Manage instances
ec2:
profile: myprofile
region: us-east-1
wait: yes
group_id: sg-000000
key_name: mykey
vpc_subnet_id: subnet-0000000
instance_type: m3.medium
instance_tags:
Name: my-test
image: ami-0000000
volumes:
- device_name: /dev/sdb
ephemeral: ephemeral0
```
**Expected Results**: An instance is created as specified
**Actual Results**:
The following error occurs:
```
failed: [localhost] => {"failed": true, "parsed": false}
Traceback (most recent call last):
File "/Users/me/.ansible/tmp/ansible-tmp-1436472344.45-200995340429191/ec2", line 3054, in <module>
main()
File "/Users/me/.ansible/tmp/ansible-tmp-1436472344.45-200995340429191/ec2", line 1246, in main
(instance_dict_array, new_instance_ids, changed) = create_instances(module, ec2, vpc)
File "/Users/me/.ansible/tmp/ansible-tmp-1436472344.45-200995340429191/ec2", line 789, in create_instances
vpc_id = vpc.get_all_subnets(subnet_ids=[vpc_subnet_id])[0].vpc_id
File "/Library/Python/2.7/site-packages/boto/vpc/__init__.py", line 1153, in get_all_subnets
return self.get_list('DescribeSubnets', params, [('item', Subnet)])
File "/Library/Python/2.7/site-packages/boto/connection.py", line 1185, in get_list
raise self.ResponseError(response.status, response.reason, body)
boto.exception.EC2ResponseError: EC2ResponseError: 400 Bad Request
<?xml version="1.0" encoding="UTF-8"?>
<Response><Errors><Error><Code>InvalidSubnetID.NotFound</Code><Message>The subnet ID 'subnet-000000' does not exist</Message></Error></Errors><RequestID>xxxxxxxxxxxxxxxxxx</RequestID></Response>
```
Changing the profile in which that subnet exists to the default profile allows the playbook to run as expected.
|
True
|
ec2 module: profile option ignored - **Issue Type**: Bug Report
**Ansible Version**: 1.9
**Ansible Configuration**: default
**Environment**: OSX 10.9.5
**Summary**: The "profile" option in the ec2 module is ignored
**Steps To Reproduce**:
Create a playbook like so and run it. The account in which `subnet-0000000` exists must not be in your default aws profile (defined in `~/.aws/{credentials,config}`:
```
- name: Make an instance
hosts: all
connection: local
gather_facts: False
tasks:
- name: Manage instances
ec2:
profile: myprofile
region: us-east-1
wait: yes
group_id: sg-000000
key_name: mykey
vpc_subnet_id: subnet-0000000
instance_type: m3.medium
instance_tags:
Name: my-test
image: ami-0000000
volumes:
- device_name: /dev/sdb
ephemeral: ephemeral0
```
**Expected Results**: An instance is created as specified
**Actual Results**:
The following error occurs:
```
failed: [localhost] => {"failed": true, "parsed": false}
Traceback (most recent call last):
File "/Users/me/.ansible/tmp/ansible-tmp-1436472344.45-200995340429191/ec2", line 3054, in <module>
main()
File "/Users/me/.ansible/tmp/ansible-tmp-1436472344.45-200995340429191/ec2", line 1246, in main
(instance_dict_array, new_instance_ids, changed) = create_instances(module, ec2, vpc)
File "/Users/me/.ansible/tmp/ansible-tmp-1436472344.45-200995340429191/ec2", line 789, in create_instances
vpc_id = vpc.get_all_subnets(subnet_ids=[vpc_subnet_id])[0].vpc_id
File "/Library/Python/2.7/site-packages/boto/vpc/__init__.py", line 1153, in get_all_subnets
return self.get_list('DescribeSubnets', params, [('item', Subnet)])
File "/Library/Python/2.7/site-packages/boto/connection.py", line 1185, in get_list
raise self.ResponseError(response.status, response.reason, body)
boto.exception.EC2ResponseError: EC2ResponseError: 400 Bad Request
<?xml version="1.0" encoding="UTF-8"?>
<Response><Errors><Error><Code>InvalidSubnetID.NotFound</Code><Message>The subnet ID 'subnet-000000' does not exist</Message></Error></Errors><RequestID>xxxxxxxxxxxxxxxxxx</RequestID></Response>
```
Changing the profile in which that subnet exists to the default profile allows the playbook to run as expected.
|
main
|
module profile option ignored issue type bug report ansible version ansible configuration default environment osx summary the profile option in the module is ignored steps to reproduce create a playbook like so and run it the account in which subnet exists must not be in your default aws profile defined in aws credentials config name make an instance hosts all connection local gather facts false tasks name manage instances profile myprofile region us east wait yes group id sg key name mykey vpc subnet id subnet instance type medium instance tags name my test image ami volumes device name dev sdb ephemeral expected results an instance is created as specified actual results the following error occurs failed failed true parsed false traceback most recent call last file users me ansible tmp ansible tmp line in main file users me ansible tmp ansible tmp line in main instance dict array new instance ids changed create instances module vpc file users me ansible tmp ansible tmp line in create instances vpc id vpc get all subnets subnet ids vpc id file library python site packages boto vpc init py line in get all subnets return self get list describesubnets params file library python site packages boto connection py line in get list raise self responseerror response status response reason body boto exception bad request invalidsubnetid notfound the subnet id subnet does not exist xxxxxxxxxxxxxxxxxx changing the profile in which that subnet exists to the default profile allows the playbook to run as expected
| 1
|
2,807
| 10,054,045,877
|
IssuesEvent
|
2019-07-21 22:04:28
|
tgstation/tgstation
|
https://api.github.com/repos/tgstation/tgstation
|
closed
|
The obj construction/deconstruction system needs a refactor
|
Maintainability/Hinders improvements
|
attackby -> istype -> do_after copypasta needs to STOP!
|
True
|
The obj construction/deconstruction system needs a refactor - attackby -> istype -> do_after copypasta needs to STOP!
|
main
|
the obj construction deconstruction system needs a refactor attackby istype do after copypasta needs to stop
| 1
|
681
| 4,229,675,602
|
IssuesEvent
|
2016-07-04 08:51:04
|
duckduckgo/zeroclickinfo-goodies
|
https://api.github.com/repos/duckduckgo/zeroclickinfo-goodies
|
closed
|
Belarusian Cheat Sheet: Should show pronunciation
|
Maintainer Input Requested PR Received Suggestion
|
For language cheat sheets we have a `trn` property (as well as `key` and `val`) for transliteration/pronunciation. The Belarusian cheat sheet should be updated to include them. See the Chinese cheat sheet for a live example: https://github.com/duckduckgo/zeroclickinfo-goodies/blob/master/share/goodie/cheat_sheets/json/language/chinese.json
[Suggested on Twitter](https://twitter.com/NiklasNisbeth/status/743435020803653632)
------
IA Page: http://duck.co/ia/view/belarusian_cheat_sheet
[Maintainer](http://docs.duckduckhack.com/maintaining/guidelines.html): @qqq3
|
True
|
Belarusian Cheat Sheet: Should show pronunciation - For language cheat sheets we have a `trn` property (as well as `key` and `val`) for transliteration/pronunciation. The Belarusian cheat sheet should be updated to include them. See the Chinese cheat sheet for a live example: https://github.com/duckduckgo/zeroclickinfo-goodies/blob/master/share/goodie/cheat_sheets/json/language/chinese.json
[Suggested on Twitter](https://twitter.com/NiklasNisbeth/status/743435020803653632)
------
IA Page: http://duck.co/ia/view/belarusian_cheat_sheet
[Maintainer](http://docs.duckduckhack.com/maintaining/guidelines.html): @qqq3
|
main
|
belarusian cheat sheet should show pronunciation for language cheat sheets we have a trn property as well as key and val for transliteration pronunciation the belarusian cheat sheet should be updated to include them see the chinese cheat sheet for a live example ia page
| 1
|
1,470
| 6,370,652,380
|
IssuesEvent
|
2017-08-01 14:35:42
|
OpenRefine/OpenRefine
|
https://api.github.com/repos/OpenRefine/OpenRefine
|
closed
|
Travis: oraclejdk7 is not available anymore
|
maintainability
|
Some Travis builds fail when they are executed on Ubuntu Trusty, because oraclejdk7 is not available there anymore:
https://github.com/travis-ci/travis-ci/issues/7884#issuecomment-308451879
We have two options:
- either set "dist: precise" to force using Precise (this image will stop being updated at some point)
- or we just drop oraclejdk7 support.
|
True
|
Travis: oraclejdk7 is not available anymore - Some Travis builds fail when they are executed on Ubuntu Trusty, because oraclejdk7 is not available there anymore:
https://github.com/travis-ci/travis-ci/issues/7884#issuecomment-308451879
We have two options:
- either set "dist: precise" to force using Precise (this image will stop being updated at some point)
- or we just drop oraclejdk7 support.
|
main
|
travis is not available anymore some travis builds fail when they are executed on ubuntu trusty because is not available there anymore we have two options either set dist precise to force using precise this image will stop being updated at some point or we just drop support
| 1
|
3,072
| 11,632,948,736
|
IssuesEvent
|
2020-02-28 06:54:39
|
chocolatey-community/chocolatey-package-requests
|
https://api.github.com/repos/chocolatey-community/chocolatey-package-requests
|
closed
|
RFM - Screenpresso
|
Status: Available For Maintainer(s)
|
## Current Maintainer
- [X] I am the maintainer of the package and wish to pass it to someone else;
## I DON'T Want To Become The Maintainer
- [ ] I have followed the Package Triage Process and I do NOT want to become maintainer of the package;
- [X] There is no existing open maintainer request for this package;
## Checklist
- [X] Issue title starts with 'RFM - '
## Existing Package Details
Package URL: https://chocolatey.org/packages/screenpresso
Package source URL: https://github.com/brutaldev/chocolatey-packages/tree/master/Screenpresso
|
True
|
RFM - Screenpresso - ## Current Maintainer
- [X] I am the maintainer of the package and wish to pass it to someone else;
## I DON'T Want To Become The Maintainer
- [ ] I have followed the Package Triage Process and I do NOT want to become maintainer of the package;
- [X] There is no existing open maintainer request for this package;
## Checklist
- [X] Issue title starts with 'RFM - '
## Existing Package Details
Package URL: https://chocolatey.org/packages/screenpresso
Package source URL: https://github.com/brutaldev/chocolatey-packages/tree/master/Screenpresso
|
main
|
rfm screenpresso current maintainer i am the maintainer of the package and wish to pass it to someone else i don t want to become the maintainer i have followed the package triage process and i do not want to become maintainer of the package there is no existing open maintainer request for this package checklist issue title starts with rfm existing package details package url package source url
| 1
|
492,314
| 14,200,166,640
|
IssuesEvent
|
2020-11-16 04:38:22
|
numbersprotocol/capture-lite
|
https://api.github.com/repos/numbersprotocol/capture-lite
|
opened
|
從 Gplay Store 下載安裝後，App icon 下的名稱還是叫做 Capture Lite
|
bug priority:critical
|
## Description
App 名稱須修正為 capture
## Steps to Reproduce
1. Go to '...'
1. Click on '....'
1. Scroll down to '....'
1. See error
## Expected Behavior
* Expected: A clear and concise description of what you expected to happen.
* Actual: A clear and concise description of what actually happened.
## Logs
If applicable, add logs or screenshots to help explain your problem.
## Environment
* Version: _e.g. 1.3.0, beta2, etc._
* OS: _e.g. Ubuntu 20.04, Android 10, iOS 13, etc._
* Device: _e.g. HTC Exodus 1_
|
1.0
|
從 Gplay Store 下載安裝後，App icon 下的名稱還是叫做 Capture Lite - ## Description
App 名稱須修正為 capture
## Steps to Reproduce
1. Go to '...'
1. Click on '....'
1. Scroll down to '....'
1. See error
## Expected Behavior
* Expected: A clear and concise description of what you expected to happen.
* Actual: A clear and concise description of what actually happened.
## Logs
If applicable, add logs or screenshots to help explain your problem.
## Environment
* Version: _e.g. 1.3.0, beta2, etc._
* OS: _e.g. Ubuntu 20.04, Android 10, iOS 13, etc._
* Device: _e.g. HTC Exodus 1_
|
non_main
|
從 gplay store 下載安裝後，app icon 下的名稱還是叫做 capture lite description app 名稱須修正為 capture steps to reproduce go to click on scroll down to see error expected behavior expected a clear and concise description of what you expected to happen actual a clear and concise description of what actually happened logs if applicable add logs or screenshots to help explain your problem environment version e g etc os e g ubuntu android ios etc device e g htc exodus
| 0
|
11,599
| 17,535,774,895
|
IssuesEvent
|
2021-08-12 06:11:02
|
renovatebot/renovate
|
https://api.github.com/repos/renovatebot/renovate
|
opened
|
Renovate Application-level Proxy
|
type:feature priority-2-important status:requirements
|
### What would you like Renovate to be able to do?
Support the concept of a Renovate-specific proxy, inspired by Go's proxy. It should support both datasource lookups as well as changelogs.
### If you have any ideas on how this should be implemented, please tell us here.
This would probably mean a new repository which depends on Renovate code, but also require some features in Renovate too, such as:
- Configuring the proxy address
- "No proxy" capability
- Configurable retry codes (e.g. defaults to 429, 5xx but could add any 4xx)
### Is this a feature you are interested in implementing yourself?
Yes
|
1.0
|
Renovate Application-level Proxy - ### What would you like Renovate to be able to do?
Support the concept of a Renovate-specific proxy, inspired by Go's proxy. It should support both datasource lookups as well as changelogs.
### If you have any ideas on how this should be implemented, please tell us here.
This would probably mean a new repository which depends on Renovate code, but also require some features in Renovate too, such as:
- Configuring the proxy address
- "No proxy" capability
- Configurable retry codes (e.g. defaults to 429, 5xx but could add any 4xx)
### Is this a feature you are interested in implementing yourself?
Yes
|
non_main
|
renovate application level proxy what would you like renovate to be able to do support the concept of a renovate specific proxy inspired by go s proxy it should support both datasource lookups as well as changelogs if you have any ideas on how this should be implemented please tell us here this would probably mean a new repository which depends on renovate code but also require some features in renovate too such as configuring the proxy address no proxy capability configurable retry codes e g defaults to but could add any is this a feature you are interested in implementing yourself yes
| 0
|
1,036
| 4,832,750,417
|
IssuesEvent
|
2016-11-08 08:40:16
|
ansible/ansible-modules-extras
|
https://api.github.com/repos/ansible/ansible-modules-extras
|
closed
|
consul: Delete service by name (probably) can't work
|
affects_2.3 bug_report P3 waiting_on_maintainer
|
The modules takes either 'id' or 'service_name':
```
service_id = module.params.get('service_id') or module.params.get('service_name')
...
remove_service(module, service_id)
```
In remove_service:
```
service = get_service_by_id(consul_api, service_id)
```
In get_service_by_id:
```
for name, service in consul_api.agent.services().iteritems():
if service['ID'] == service_id:
return ConsulService(loaded=service)
```
Seems that if statement should be:
```
if service['ID'] == service_id or service['Service'] == service_id:
```
|
True
|
consul: Delete service by name (probably) can't work - The modules takes either 'id' or 'service_name':
```
service_id = module.params.get('service_id') or module.params.get('service_name')
...
remove_service(module, service_id)
```
In remove_service:
```
service = get_service_by_id(consul_api, service_id)
```
In get_service_by_id:
```
for name, service in consul_api.agent.services().iteritems():
if service['ID'] == service_id:
return ConsulService(loaded=service)
```
Seems that if statement should be:
```
if service['ID'] == service_id or service['Service'] == service_id:
```
|
main
|
consul delete service by name probably can t work the modules takes either id or service name service id module params get service id or module params get service name remove service module service id in remove service service get service by id consul api service id in get service by id for name service in consul api agent services iteritems if service service id return consulservice loaded service seems that if statement should be if service service id or service service id
| 1
|
1,171
| 5,089,235,390
|
IssuesEvent
|
2017-01-01 13:12:54
|
tgstation/tgstation
|
https://api.github.com/repos/tgstation/tgstation
|
closed
|
Alert time out should use addtimer instead of spawn
|
Maintainability/Hinders improvements Not a bug
|
neersighted: hey someone
neersighted: KorPhaeron: open an issue for me
neersighted; alert timeout should use addtimer
KorPhaeron; why am I opening it
neersighted; because I'm neck deep in code hell
neersighted; I'm touching 4 instances of life() and species code
@neersighted
|
True
|
Alert time out should use addtimer instead of spawn - neersighted: hey someone
neersighted: KorPhaeron: open an issue for me
neersighted; alert timeout should use addtimer
KorPhaeron; why am I opening it
neersighted; because I'm neck deep in code hell
neersighted; I'm touching 4 instances of life() and species code
@neersighted
|
main
|
alert time out should use addtimer instead of spawn neersighted hey someone neersighted korphaeron open an issue for me neersighted alert timeout should use addtimer korphaeron why am i opening it neersighted because i m neck deep in code hell neersighted i m touching instances of life and species code neersighted
| 1
|
830,092
| 31,988,472,058
|
IssuesEvent
|
2023-09-21 02:37:01
|
hoteljuliet/SPEL
|
https://api.github.com/repos/hoteljuliet/SPEL
|
closed
|
Finalize object model
|
high priority
|
The goal here is to make the addition of new steps easy, with minimal boiler plate. Base classes should have all the "infra" code.
|
1.0
|
Finalize object model - The goal here is to make the addition of new steps easy, with minimal boiler plate. Base classes should have all the "infra" code.
|
non_main
|
finalize object model the goal here is to make the addition of new steps easy with minimal boiler plate base classes should have all the infra code
| 0
|
1,132
| 4,998,447,713
|
IssuesEvent
|
2016-12-09 19:53:06
|
ansible/ansible-modules-core
|
https://api.github.com/repos/ansible/ansible-modules-core
|
closed
|
--diff doesn't show all differences with Template module
|
affects_2.2 bug_report waiting_on_maintainer
|
<!--- Verify first that your issue/request is not already reported in GitHub -->
##### ISSUE TYPE
<!--- Pick one below and delete the rest: -->
- Bug Report
##### COMPONENT NAME
Template
##### ANSIBLE VERSION
<!--- Paste verbatim output from “ansible --version” between quotes below -->
```
ansible 2.2.0 (devel 3bac945147)
```
##### CONFIGURATION
<!---
Mention any settings you have changed/added/removed in ansible.cfg
(or using the ANSIBLE_* environment variables).
-->
##### OS / ENVIRONMENT
<!---
Mention the OS you are running Ansible from, and the OS you are
managing, or say “N/A” for anything that is not platform-specific.
-->
N/A
##### SUMMARY
<!--- Explain the problem briefly -->
Using `--diff` when running template module doesn't show all the changes when both the template file and mode has changed.
##### STEPS TO REPRODUCE
<!---
For bugs, show exactly how to reproduce the problem.
For new features, show how the feature would be used.
-->
<!--- Paste example playbooks or commands between quotes below -->
Task:
```
- name: ensures /abc/myconf.conf exists
template:
src: "my_template"
dest: "/abc/myconf.conf"
mode: 0755
become: yes
become_method: sudo
```
myconf.conf
```
{
"obj": {
"type": "foo",
"pol": {
"a": "{{ ansible_processor_vcpus }}|a_pol",
"b": "b_pol,
"c": "c_pol",
"d": "d_pol"
}
}
}
```
Changed task w/ updated `mode` and updated `myconf.conf`
```
- name: ensures /abc/myconf.conf exists
template:
src: "my_template"
dest: "/abc/myconf.conf"
mode: 0775
become: yes
become_method: sudo
```
```
{
"obj": {
"type": "foo1",
"pol": {
"a": "{{ ansible_processor_vcpus }}|a_pol",
"b": "b_pol,
"c": "c_pol",
"d": "d_pol"
}
}
}
```
<!--- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- What did you expect to happen when running the steps above? -->
```
changed: [xx.xx.xx.xxx] => {"changed": true, "diff": {"after": {"mode": "0775", "path": "/abc/myconf.conf"}, "before": {"mode": "0755", "path": "/abc/myconf.conf"},{"after": "{\n \"obj\": {\n \"type\": \"foo1\",\n \"pol\": {\n \"a\": \"2|a_pol\",\n \"b\": \"b_pol,\n \"c\": \"c_pol\",\n \"d\": \"d_pol\"\n }\n }\n}\n\n", "after_header": "dynamically generated", "before": "{\n \"obj\": {\n \"type\": \"foo\",\n \"pol\": {\n \"a\": \"2|a_pol\",\n \"b\": \"b_pol,\n \"c\": \"c_pol\",\n \"d\": \"d_pol\"\n }\n}, "gid": 0, "group": "root", "invocation": {"module_args": {"backup": null, "content": null, "delimiter": null, "dest": "/abc/myconf.conf", "diff_peek": null, "directory_mode": null, "follow": true, "force": false, "group": null, "mode": 509, "original_basename": "myconf.conf.j2", "owner": null, "path": "/abc/myconf.conf", "recurse": false, "regexp": null, "remote_src": null, "selevel": null, "serole": null, "setype": null, "seuser": null, "src": null, "state": null, "validate": null}}, "mode": "0755", "owner": "root", "path": "/abc/myconf.conf", "size": 138, "state": "file", "uid": 0}
--- before: /abc/myconf.conf
+++ after: dynamically generated
@@ -1,6 +1,6 @@
{
"obj": {
- "type": "foo",
+ "type": "foo1",
"pol": {
"a": "2|a_pol",
"b": "b_pol,
--- before
+++ after
@@ -1,4 +1,4 @@
{
- "mode": "0755",
+ "mode": "0775",
"path": "/abc/myconf.conf"
}
```
##### ACTUAL RESULTS
<!--- What actually happened? If possible run with extra verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes below -->
Ansible playbook was run with `--diff` and `--check` flags. The behavior is the same whether `--check` flag was used or not.
```
changed: [xx.xx.xx.xxx] => {"changed": true, "diff": {"after": "{\n \"obj\": {\n \"type\": \"foo1\",\n \"pol\": {\n \"a\": \"2|a_pol\",\n \"b\": \"b_pol,\n \"c\": \"c_pol\",\n \"d\": \"d_pol\"\n }\n }\n}\n\n", "after_header": "dynamically generated", "before": "{\n \"obj\": {\n \"type\": \"foo\",\n \"pol\": {\n \"a\": \"2|a_pol\",\n \"b\": \"b_pol,\n \"c\": \"c_pol\",\n \"d\": \"d_pol\"\n }\n }\n}\n\n", "before_header": "/abc/myconf.conf"}, "invocation": {"module_args": {"dest": "/abc/myconf.conf", "mode": 509, "src": "myconf.conf.j2"}, "module_name": "template"}}
--- before: /abc/myconf.conf
+++ after: dynamically generated
@@ -1,6 +1,6 @@
{
"obj": {
- "type": "foo",
+ "type": "foo1",
"pol": {
"a": "2|a_pol",
"b": "b_pol,
```
NOTE: When only `mode` was updated with no changes to the `myconf.conf` file, the output is as expected as follows:
```
--- before
+++ after
@@ -1,4 +1,4 @@
{
- "mode": "0755",
+ "mode": "0775",
"path": "/abc/myconf.conf"
}
```
|
True
|
--diff doesn't show all differences with Template module - <!--- Verify first that your issue/request is not already reported in GitHub -->
##### ISSUE TYPE
<!--- Pick one below and delete the rest: -->
- Bug Report
##### COMPONENT NAME
Template
##### ANSIBLE VERSION
<!--- Paste verbatim output from “ansible --version” between quotes below -->
```
ansible 2.2.0 (devel 3bac945147)
```
##### CONFIGURATION
<!---
Mention any settings you have changed/added/removed in ansible.cfg
(or using the ANSIBLE_* environment variables).
-->
##### OS / ENVIRONMENT
<!---
Mention the OS you are running Ansible from, and the OS you are
managing, or say “N/A” for anything that is not platform-specific.
-->
N/A
##### SUMMARY
<!--- Explain the problem briefly -->
Using `--diff` when running template module doesn't show all the changes when both the template file and mode has changed.
##### STEPS TO REPRODUCE
<!---
For bugs, show exactly how to reproduce the problem.
For new features, show how the feature would be used.
-->
<!--- Paste example playbooks or commands between quotes below -->
Task:
```
- name: ensures /abc/myconf.conf exists
template:
src: "my_template"
dest: "/abc/myconf.conf"
mode: 0755
become: yes
become_method: sudo
```
myconf.conf
```
{
"obj": {
"type": "foo",
"pol": {
"a": "{{ ansible_processor_vcpus }}|a_pol",
"b": "b_pol,
"c": "c_pol",
"d": "d_pol"
}
}
}
```
Changed task w/ updated `mode` and updated `myconf.conf`
```
- name: ensures /abc/myconf.conf exists
template:
src: "my_template"
dest: "/abc/myconf.conf"
mode: 0775
become: yes
become_method: sudo
```
```
{
"obj": {
"type": "foo1",
"pol": {
"a": "{{ ansible_processor_vcpus }}|a_pol",
"b": "b_pol,
"c": "c_pol",
"d": "d_pol"
}
}
}
```
<!--- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- What did you expect to happen when running the steps above? -->
```
changed: [xx.xx.xx.xxx] => {"changed": true, "diff": {"after": {"mode": "0775", "path": "/abc/myconf.conf"}, "before": {"mode": "0755", "path": "/abc/myconf.conf"},{"after": "{\n \"obj\": {\n \"type\": \"foo1\",\n \"pol\": {\n \"a\": \"2|a_pol\",\n \"b\": \"b_pol,\n \"c\": \"c_pol\",\n \"d\": \"d_pol\"\n }\n }\n}\n\n", "after_header": "dynamically generated", "before": "{\n \"obj\": {\n \"type\": \"foo\",\n \"pol\": {\n \"a\": \"2|a_pol\",\n \"b\": \"b_pol,\n \"c\": \"c_pol\",\n \"d\": \"d_pol\"\n }\n}, "gid": 0, "group": "root", "invocation": {"module_args": {"backup": null, "content": null, "delimiter": null, "dest": "/abc/myconf.conf", "diff_peek": null, "directory_mode": null, "follow": true, "force": false, "group": null, "mode": 509, "original_basename": "myconf.conf.j2", "owner": null, "path": "/abc/myconf.conf", "recurse": false, "regexp": null, "remote_src": null, "selevel": null, "serole": null, "setype": null, "seuser": null, "src": null, "state": null, "validate": null}}, "mode": "0755", "owner": "root", "path": "/abc/myconf.conf", "size": 138, "state": "file", "uid": 0}
--- before: /abc/myconf.conf
+++ after: dynamically generated
@@ -1,6 +1,6 @@
{
"obj": {
- "type": "foo",
+ "type": "foo1",
"pol": {
"a": "2|a_pol",
"b": "b_pol,
--- before
+++ after
@@ -1,4 +1,4 @@
{
- "mode": "0755",
+ "mode": "0775",
"path": "/abc/myconf.conf"
}
```
##### ACTUAL RESULTS
<!--- What actually happened? If possible run with extra verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes below -->
Ansible playbook was run with `--diff` and `--check` flags. The behavior is the same whether `--check` flag was used or not.
```
changed: [xx.xx.xx.xxx] => {"changed": true, "diff": {"after": "{\n \"obj\": {\n \"type\": \"foo1\",\n \"pol\": {\n \"a\": \"2|a_pol\",\n \"b\": \"b_pol,\n \"c\": \"c_pol\",\n \"d\": \"d_pol\"\n }\n }\n}\n\n", "after_header": "dynamically generated", "before": "{\n \"obj\": {\n \"type\": \"foo\",\n \"pol\": {\n \"a\": \"2|a_pol\",\n \"b\": \"b_pol,\n \"c\": \"c_pol\",\n \"d\": \"d_pol\"\n }\n }\n}\n\n", "before_header": "/abc/myconf.conf"}, "invocation": {"module_args": {"dest": "/abc/myconf.conf", "mode": 509, "src": "myconf.conf.j2"}, "module_name": "template"}}
--- before: /abc/myconf.conf
+++ after: dynamically generated
@@ -1,6 +1,6 @@
{
"obj": {
- "type": "foo",
+ "type": "foo1",
"pol": {
"a": "2|a_pol",
"b": "b_pol,
```
NOTE: When only `mode` was updated with no changes to the `myconf.conf` file, the output is as expected as follows:
```
--- before
+++ after
@@ -1,4 +1,4 @@
{
- "mode": "0755",
+ "mode": "0775",
"path": "/abc/myconf.conf"
}
```
|
main
|
diff doesn t show all differences with template module issue type bug report component name template ansible version ansible devel configuration mention any settings you have changed added removed in ansible cfg or using the ansible environment variables os environment mention the os you are running ansible from and the os you are managing or say “n a” for anything that is not platform specific n a summary using diff when running template module doesn t show all the changes when both the template file and mode has changed steps to reproduce for bugs show exactly how to reproduce the problem for new features show how the feature would be used task name ensures abc myconf conf exists template src my template dest abc myconf conf mode become yes become method sudo myconf conf obj type foo pol a ansible processor vcpus a pol b b pol c c pol d d pol changed task w updated mode and updated myconf conf name ensures abc myconf conf exists template src my template dest abc myconf conf mode become yes become method sudo obj type pol a ansible processor vcpus a pol b b pol c c pol d d pol expected results changed changed true diff after mode path abc myconf conf before mode path abc myconf conf after n obj n type n pol n a a pol n b b pol n c c pol n d d pol n n n n n after header dynamically generated before n obj n type foo n pol n a a pol n b b pol n c c pol n d d pol n n gid group root invocation module args backup null content null delimiter null dest abc myconf conf diff peek null directory mode null follow true force false group null mode original basename myconf conf owner null path abc myconf conf recurse false regexp null remote src null selevel null serole null setype null seuser null src null state null validate null mode owner root path abc myconf conf size state file uid before abc myconf conf after dynamically generated obj type foo type pol a a pol b b pol before after mode mode path abc myconf conf actual results ansible playbook was run with diff and check flags the behavior is the same whether check flag was used or not changed changed true diff after n obj n type n pol n a a pol n b b pol n c c pol n d d pol n n n n n after header dynamically generated before n obj n type foo n pol n a a pol n b b pol n c c pol n d d pol n n n n n before header abc myconf conf invocation module args dest abc myconf conf mode src myconf conf module name template before abc myconf conf after dynamically generated obj type foo type pol a a pol b b pol note when only mode was updated with no changes to the myconf conf file the output is as expected as follows before after mode mode path abc myconf conf
| 1
|
1,357
| 5,849,545,657
|
IssuesEvent
|
2017-05-11 00:21:35
|
Microsoft/DirectXTK
|
https://api.github.com/repos/Microsoft/DirectXTK
|
closed
|
Raise minimum supported Feature Level to 9.3
|
maintainence
|
The DirectX Tool Kit has supported all feature levels 9.1 and up, primarily to support Surface RT and Surface RT 2 devices. Since these devices will not be getting upgraded to Windows 10, and given the fact that the vast majority of PCs have 10.0 or better hardware, we will be retiring support for FL 9.1. There are almost no 9.2 devices of relevance today, but Windows phone 8.1 support requires FL 9.3.
|
True
|
Raise minimum supported Feature Level to 9.3 - The DirectX Tool Kit has supported all feature levels 9.1 and up, primarily to support Surface RT and Surface RT 2 devices. Since these devices will not be getting upgraded to Windows 10, and given the fact that the vast majority of PCs have 10.0 or better hardware, we will be retiring support for FL 9.1. There are almost no 9.2 devices of relevance today, but Windows phone 8.1 support requires FL 9.3.
|
main
|
raise minimum supported feature level to the directx tool kit has supported all feature levels and up primarily to support surface rt and surface rt devices since these devices will not be getting upgraded to windows and given the fact that the vast majority of pcs have or better hardware we will be retiring support for fl there are almost no devices of relevance today but windows phone support requires fl
| 1
|
1,495
| 6,476,924,639
|
IssuesEvent
|
2017-08-18 00:50:08
|
ansible/ansible-modules-extras
|
https://api.github.com/repos/ansible/ansible-modules-extras
|
closed
|
minor broken html/quoting on efs_module.html
|
affects_2.3 aws cloud docs_report waiting_on_maintainer
|
<!--- Verify first that your issue/request is not already reported in GitHub -->
searched for efs in open issues, none found
##### ISSUE TYPE
- Documentation Report
##### COMPONENT NAME
documentation of efs_module
##### ANSIBLE VERSION
n/a
##### CONFIGURATION
n/a
##### OS / ENVIRONMENT
n/a
##### SUMMARY
https://docs.ansible.com/ansible/efs_module.html shows on my chrome broken html after parameter tags
##### EXPECTED RESULTS
readable documentation on the website
|
True
|
minor broken html/quoting on efs_module.html - <!--- Verify first that your issue/request is not already reported in GitHub -->
searched for efs in open issues, none found
##### ISSUE TYPE
- Documentation Report
##### COMPONENT NAME
documentation of efs_module
##### ANSIBLE VERSION
n/a
##### CONFIGURATION
n/a
##### OS / ENVIRONMENT
n/a
##### SUMMARY
https://docs.ansible.com/ansible/efs_module.html shows on my chrome broken html after parameter tags
##### EXPECTED RESULTS
readable documentation on the website
|
main
|
minor broken html quoting on efs module html searched for efs in open issues none found issue type documentation report component name documentation of efs module ansible version n a configuration n a os environment n a summary shows on my chrome broken html after parameter tags expected results readable documentation on the website
| 1
|
201,318
| 15,802,199,842
|
IssuesEvent
|
2021-04-03 08:33:37
|
Chihui8199/ped
|
https://api.github.com/repos/Chihui8199/ped
|
opened
|
Unclear documentation on items update
|
severity.Low type.DocumentationBug
|
Initially I thought u were suppose to type items update p in one line and realised is not that.
Instead perhaps it better to show in full how the code is suppose to work i.e the whole chunk on what you are suppose to type
<!--session: 1617437377808-99f84f2d-a099-496e-83df-64f775c41f5f-->
|
1.0
|
Unclear documentation on items update - 
Initially I thought u were suppose to type items update p in one line and realised is not that.
Instead perhaps it better to show in full how the code is suppose to work i.e the whole chunk on what you are suppose to type
<!--session: 1617437377808-99f84f2d-a099-496e-83df-64f775c41f5f-->
|
non_main
|
unclear documentation on items update initially i thought u were suppose to type items update p in one line and realised is not that instead perhaps it better to show in full how the code is suppose to work i e the whole chunk on what you are suppose to type
| 0
|
184,304
| 14,286,633,327
|
IssuesEvent
|
2020-11-23 15:23:03
|
hikari-py/hikari
|
https://api.github.com/repos/hikari-py/hikari
|
closed
|
Add an `old_x` attribute to update events
|
enhancement good first issue medium testing
|
### Summary
<!-- Small summary of the feature -->
There should be an attribute in update related events that point to the latest "old" version of said entity in cache, None otherwise.
### Problem
<!-- What problem will this feature solve (if any)? -->
Currently it's quite impracticable to know what changed with `XUpdateEvent` events, since the cache is updated before the event is dispatched to the listeners/subscribers. To achieve the desired effect, one would have to change the whole cache implementation so that the cache is updated after the events are dispatched, which is quite cumbersome.
Having the "possible" older version of the updated entity is quite useful because you're able to know what part of it changed and so correctly trigger whatever logic you want. Without this, it becomes much harder to execute some routine whenever, let's say, a member is muted, or a guild has its logo changed.
### Ideal implementation
<!-- How should this feature be implemented? -->
I believe it would probably be best to simply add a field/attribute to those event classes that contain the cached entity before it is updated, possibly named `old_x` (`old_channel`, `old_role`, etc).
One issue I see with this is an extra hit on cache, which can possibly be more precious than this, but I also believe if someone is needing that level of optimisation, they probably know their way around quite well and have written their own implementation of stuff.
### Checklist
<!-- Make sure to tick all the following boxes by putting an `x` in between (like this `[x]`) -->
- [x] I have searched the issue tracker and have made sure it's not a duplicate.
|
1.0
|
Add an `old_x` attribute to update events - ### Summary
<!-- Small summary of the feature -->
There should be an attribute in update related events that point to the latest "old" version of said entity in cache, None otherwise.
### Problem
<!-- What problem will this feature solve (if any)? -->
Currently it's quite impracticable to know what changed with `XUpdateEvent` events, since the cache is updated before the event is dispatched to the listeners/subscribers. To achieve the desired effect, one would have to change the whole cache implementation so that the cache is updated after the events are dispatched, which is quite cumbersome.
Having the "possible" older version of the updated entity is quite useful because you're able to know what part of it changed and so correctly trigger whatever logic you want. Without this, it becomes much harder to execute some routine whenever, let's say, a member is muted, or a guild has its logo changed.
### Ideal implementation
<!-- How should this feature be implemented? -->
I believe it would probably be best to simply add a field/attribute to those event classes that contain the cached entity before it is updated, possibly named `old_x` (`old_channel`, `old_role`, etc).
One issue I see with this is an extra hit on cache, which can possibly be more precious than this, but I also believe if someone is needing that level of optimisation, they probably know their way around quite well and have written their own implementation of stuff.
### Checklist
<!-- Make sure to tick all the following boxes by putting an `x` in between (like this `[x]`) -->
- [x] I have searched the issue tracker and have made sure it's not a duplicate.
|
non_main
|
add an old x attribute to update events summary there should be an attribute in update related events that point to the latest old version of said entity in cache none otherwise problem currently it s quite impracticable to know what changed with xupdateevent events since the cache is updated before the event is dispatched to the listeners subscribers to achieve the desired effect one would have to change the whole cache implementation so that the cache is updated after the events are dispatched which is quite cumbersome having the possible older version of the updated entity is quite useful because you re able to know what part of it changed and so correctly trigger whatever logic you want without this it becomes much harder to execute some routine whenever let s say a member is muted or a guild has its logo changed ideal implementation i believe it would probably be best to simply add a field attribute to those event classes that contain the cached entity before it is updated possibly named old x old channel old role etc one issue i see with this is an extra hit on cache which can possibly be more precious than this but i also believe if someone is needing that level of optimisation they probably know their way around quite well and have written their own implementation of stuff checklist i have searched the issue tracker and have made sure it s not a duplicate
| 0
|
270,520
| 8,461,352,422
|
IssuesEvent
|
2018-10-22 21:33:01
|
webcompat/web-bugs
|
https://api.github.com/repos/webcompat/web-bugs
|
closed
|
preev.com - site is not usable
|
browser-firefox priority-normal
|
<!-- @browser: Firefox 64.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:64.0) Gecko/20100101 Firefox/64.0 -->
<!-- @reported_with: desktop-reporter -->
**URL**: http://preev.com/
**Browser / Version**: Firefox 64.0
**Operating System**: Windows 10
**Tested Another Browser**: Yes
**Problem type**: Site is not usable
**Description**: Website is not usable in mobile browser. Try to click on input field and it will not work.
**Steps to Reproduce**:
[](https://webcompat.com/uploads/2018/10/e4325466-4761-47ea-b249-51628cb07b3f.jpeg)
<details>
<summary>Browser Configuration</summary>
<ul>
{u'mixed active content blocked': False, u'buildID': u'20181015220336', u'hasTouchScreen': False, u'tracking content blocked': u'false', u'consoleLog': [u'[JavaScript Warning: "The resource at http://www.google-analytics.com/ga.js was blocked because content blocking is enabled." {file: "http://preev.com/" line: 0}]', u'[JavaScript Warning: "Loading failed for the <script> with source http://www.google-analytics.com/ga.js." {file: "http://preev.com/" line: 1}]'], u'gfx.webrender.blob-images': True, u'gfx.webrender.all': False, u'mixed passive content blocked': False, u'gfx.webrender.enabled': False, u'image.mem.shared': True, u'channel': u'aurora'}
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_
|
1.0
|
preev.com - site is not usable - <!-- @browser: Firefox 64.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:64.0) Gecko/20100101 Firefox/64.0 -->
<!-- @reported_with: desktop-reporter -->
**URL**: http://preev.com/
**Browser / Version**: Firefox 64.0
**Operating System**: Windows 10
**Tested Another Browser**: Yes
**Problem type**: Site is not usable
**Description**: Website is not usable in mobile browser. Try to click on input field and it will not work.
**Steps to Reproduce**:
[](https://webcompat.com/uploads/2018/10/e4325466-4761-47ea-b249-51628cb07b3f.jpeg)
<details>
<summary>Browser Configuration</summary>
<ul>
{u'mixed active content blocked': False, u'buildID': u'20181015220336', u'hasTouchScreen': False, u'tracking content blocked': u'false', u'consoleLog': [u'[JavaScript Warning: "The resource at http://www.google-analytics.com/ga.js was blocked because content blocking is enabled." {file: "http://preev.com/" line: 0}]', u'[JavaScript Warning: "Loading failed for the <script> with source http://www.google-analytics.com/ga.js." {file: "http://preev.com/" line: 1}]'], u'gfx.webrender.blob-images': True, u'gfx.webrender.all': False, u'mixed passive content blocked': False, u'gfx.webrender.enabled': False, u'image.mem.shared': True, u'channel': u'aurora'}
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_
|
non_main
|
preev com site is not usable url browser version firefox operating system windows tested another browser yes problem type site is not usable description website is not usable in mobile browser try to click on input field and it will not work steps to reproduce browser configuration u mixed active content blocked false u buildid u u hastouchscreen false u tracking content blocked u false u consolelog u u gfx webrender blob images true u gfx webrender all false u mixed passive content blocked false u gfx webrender enabled false u image mem shared true u channel u aurora from with ❤️
| 0
|
1,666
| 6,574,070,638
|
IssuesEvent
|
2017-09-11 11:21:06
|
ansible/ansible-modules-core
|
https://api.github.com/repos/ansible/ansible-modules-core
|
closed
|
Extend script module to ingest JSON output on stdout
|
affects_2.2 feature_idea waiting_on_maintainer
|
Detail | Information
--------|--------
Issue Type | Feature Idea
Component Name | script
Ansible Version | <=2.2
OS / Environment | N/A
# Feature Explanation
I'd like to see the script module extended (don't forget Windows users here either) so that if a script outputs JSON that Ansible understands, the JSON blob is ingested into Ansible just like it would be if it was returned from a module. I'd suggest the following for a new parameter.
Attribute | Detail
--------|--------
Name | json
Type | boolean
Default | false
Description | Script outputs valid JSON on stdout and the JSON blob is in a format that Ansible understands.
Using this parameter I could for instance write a short script to perform a task, but still correctly return if there was a change or a failure.
|
True
|
Extend script module to ingest JSON output on stdout - Detail | Information
--------|--------
Issue Type | Feature Idea
Component Name | script
Ansible Version | <=2.2
OS / Environment | N/A
# Feature Explanation
I'd like to see the script module extended (don't forget Windows users here either) so that if a script outputs JSON that Ansible understands, the JSON blob is ingested into Ansible just like it would be if it was returned from a module. I'd suggest the following for a new parameter.
Attribute | Detail
--------|--------
Name | json
Type | boolean
Default | false
Description | Script outputs valid JSON on stdout and the JSON blob is in a format that Ansible understands.
Using this parameter I could for instance write a short script to perform a task, but still correctly return if there was a change or a failure.
|
main
|
extend script module to ingest json output on stdout detail information issue type feature idea component name script ansible version os environment n a feature explanation i d like to see the script module extended don t forget windows users here either so that if a script outputs json that ansible understands the json blob is ingested into ansible just like it would be if it was returned from a module i d suggest the following for a new parameter attribute detail name json type boolean default false description script outputs valid json on stdout and the json blob is in a format that ansible understands using this parameter i could for instance write a short script to perform a task but still correctly return if there was a change or a failure
| 1
|
185,732
| 6,727,211,318
|
IssuesEvent
|
2017-10-17 12:51:36
|
metasfresh/metasfresh
|
https://api.github.com/repos/metasfresh/metasfresh
|
closed
|
Forecast in Material Disposition
|
branch:master branch:release priority:high type:enhancement
|
### Is this a bug or feature request?
Feature Request
Belongs to https://github.com/metasfresh/metasfresh/issues/1339
### What is the current behavior?
Currently, Forecast is not respected in Material Disposition.
#### Which are the steps to reproduce?
Open, check and see.
### What is the expected or desired behavior?
Handle Forecast Data in Material Disposition.
|
1.0
|
Forecast in Material Disposition - ### Is this a bug or feature request?
Feature Request
Belongs to https://github.com/metasfresh/metasfresh/issues/1339
### What is the current behavior?
Currently, Forecast is not respected in Material Disposition.
#### Which are the steps to reproduce?
Open, check and see.
### What is the expected or desired behavior?
Handle Forecast Data in Material Disposition.
|
non_main
|
forecast in material disposition is this a bug or feature request feature request belongs to what is the current behavior currently forecast is not respected in material disposition which are the steps to reproduce open check and see what is the expected or desired behavior handle forecast data in material disposition
| 0
|
674
| 4,216,276,797
|
IssuesEvent
|
2016-06-30 08:42:07
|
Particular/NServiceBus
|
https://api.github.com/repos/Particular/NServiceBus
|
closed
|
Confusing obsoletes for Storage
|
Project: V6 Launch Size: S State: In Progress - Maintainer Prio Tag: Maintainer Prio Type: Bug
|
In v6 if using the old syntax to specify a specific storage eg:
`c.UsePersistence<FakeTmStorage>().For(Storage.Timeouts);`
will give 2 compiler errors
```
'Storage' is obsolete: Please use `NServiceBus.Persistence.StorageType` instead
```
and
```
PersistenceExtentions<FakeTmStorage>.For(params Storage[])' is obsolete:
Please use `UsePersistence<T, S>()` instead
```
Following the first will lead no where since changing to `StorageType` give other compile errors since `Storage` is a enum but `StorageType` is a class.
Following the second error is the way to go.
|
True
|
Confusing obsoletes for Storage - In v6 if using the old syntax to specify a specific storage eg:
`c.UsePersistence<FakeTmStorage>().For(Storage.Timeouts);`
will give 2 compiler errors
```
'Storage' is obsolete: Please use `NServiceBus.Persistence.StorageType` instead
```
and
```
PersistenceExtentions<FakeTmStorage>.For(params Storage[])' is obsolete:
Please use `UsePersistence<T, S>()` instead
```
Following the first will lead no where since changing to `StorageType` give other compile errors since `Storage` is a enum but `StorageType` is a class.
Following the second error is the way to go.
|
main
|
confusing obsoletes for storage in if using the old syntax to specify a specific storage eg c usepersistence for storage timeouts will give compiler errors storage is obsolete please use nservicebus persistence storagetype instead and persistenceextentions for params storage is obsolete please use usepersistence instead following the first will lead no where since changing to storagetype give other compile errors since storage is a enum but storagetype is a class following the second error is the way to go
| 1
|
48,963
| 25,920,444,109
|
IssuesEvent
|
2022-12-15 21:23:50
|
CondeNast/atjson
|
https://api.github.com/repos/CondeNast/atjson
|
closed
|
Add cumulative performance time to performance profile summary
|
⏱ Performance
|
Currently we don't have this readily available for our performance profiles, which makes it a bit difficult in cases like https://github.com/CondeNast/atjson/pull/394, where function names were changed with the change. The cumulative summary with the confidence interval would help in this case so we're more aware of the affect of the changes.
|
True
|
Add cumulative performance time to performance profile summary - Currently we don't have this readily available for our performance profiles, which makes it a bit difficult in cases like https://github.com/CondeNast/atjson/pull/394, where function names were changed with the change. The cumulative summary with the confidence interval would help in this case so we're more aware of the affect of the changes.
|
non_main
|
add cumulative performance time to performance profile summary currently we don t have this readily available for our performance profiles which makes it a bit difficult in cases like where function names were changed with the change the cumulative summary with the confidence interval would help in this case so we re more aware of the affect of the changes
| 0
|
2,588
| 8,808,863,224
|
IssuesEvent
|
2018-12-27 16:38:19
|
RDIL/area4
|
https://api.github.com/repos/RDIL/area4
|
closed
|
Python 2 support
|
enhancement not-stale subject: maintaining-project
|
## Idea
Create a dev build that supports python2
## Context
Some code features are not compatible.
## Helpfulness
Allowes us to expand community.
## Anything Else
I already created a branch for this.
|
True
|
Python 2 support - ## Idea
Create a dev build that supports python2
## Context
Some code features are not compatible.
## Helpfulness
Allowes us to expand community.
## Anything Else
I already created a branch for this.
|
main
|
python support idea create a dev build that supports context some code features are not compatible helpfulness allowes us to expand community anything else i already created a branch for this
| 1
|
4,897
| 25,139,035,265
|
IssuesEvent
|
2022-11-09 21:16:51
|
centerofci/mathesar
|
https://api.github.com/repos/centerofci/mathesar
|
closed
|
Opening the table inspector should not clear the cell selection
|
type: bug work: frontend status: ready restricted: maintainers
|
## Steps to reproduce
1. Open a table page.
1. Close the table inspector.
1. Select one cell.
1. Open the table inspector.
1. Expect the cell to remain selected once the table inspector is opened.
1. Instead, observe that opening the table inspector has cleared the cell selection.
CC: @rajatvijay
|
True
|
Opening the table inspector should not clear the cell selection - ## Steps to reproduce
1. Open a table page.
1. Close the table inspector.
1. Select one cell.
1. Open the table inspector.
1. Expect the cell to remain selected once the table inspector is opened.
1. Instead, observe that opening the table inspector has cleared the cell selection.
CC: @rajatvijay
|
main
|
opening the table inspector should not clear the cell selection steps to reproduce open a table page close the table inspector select one cell open the table inspector expect the cell to remain selected once the table inspector is opened instead observe that opening the table inspector has cleared the cell selection cc rajatvijay
| 1
|
677
| 4,221,006,718
|
IssuesEvent
|
2016-07-01 02:09:30
|
NodeOS/NodeOS
|
https://api.github.com/repos/NodeOS/NodeOS
|
closed
|
Maintain npkg.org
|
needs-maintainer
|
I put up a few packages on http://npgk.org for keeping track of useful node-os modules on npm.
If anyone would like to help maintain that site, please let me know.
|
True
|
Maintain npkg.org - I put up a few packages on http://npgk.org for keeping track of useful node-os modules on npm.
If anyone would like to help maintain that site, please let me know.
|
main
|
maintain npkg org i put up a few packages on for keeping track of useful node os modules on npm if anyone would like to help maintain that site please let me know
| 1
|
442,186
| 12,741,337,576
|
IssuesEvent
|
2020-06-26 05:47:12
|
StrangeLoopGames/EcoIssues
|
https://api.github.com/repos/StrangeLoopGames/EcoIssues
|
closed
|
[0.9.0 staging-1625] Can't create second law by one session
|
Category: UI Priority: Critical Priority: High Status: Fixed
|
Step to reproduce:
- connect to server. open court press "Draft law" and create some law:
- press propose law. afret that press "Draft law" in second cell:
- I have this window and can't click anything here:
- i can only close it.
- so I need to restart client to propose another law
|
2.0
|
[0.9.0 staging-1625] Can't create second law by one session - Step to reproduce:
- connect to server. open court press "Draft law" and create some law:
- press propose law. afret that press "Draft law" in second cell:
- I have this window and can't click anything here:
- i can only close it.
- so I need to restart client to propose another law
|
non_main
|
can t create second law by one session step to reproduce connect to server open court press draft law and create some law press propose law afret that press draft law in second cell i have this window and can t click anything here i can only close it so i need to restart client to propose another law
| 0
|
3,652
| 14,916,980,012
|
IssuesEvent
|
2021-01-22 19:05:25
|
tgstation/tgstation-server
|
https://api.github.com/repos/tgstation/tgstation-server
|
closed
|
The public facing DMAPI needs to be versioned separately from the Interop (Bridge/Topic) version
|
Area: DMAPI Maintainability Issue Work In Progress
|
They are not the same things.
We really want to bump the former to 6 but keep the latter at 5.
This semver deal is getting worse all the time.
|
True
|
The public facing DMAPI needs to be versioned separately from the Interop (Bridge/Topic) version - They are not the same things.
We really want to bump the former to 6 but keep the latter at 5.
This semver deal is getting worse all the time.
|
main
|
the public facing dmapi needs to be versioned separately from the interop bridge topic version they are not the same things we really want to bump the former to but keep the latter at this semver deal is getting worse all the time
| 1
|
4,153
| 19,808,731,253
|
IssuesEvent
|
2022-01-19 09:54:03
|
RalfKoban/MiKo-Analyzers
|
https://api.github.com/repos/RalfKoban/MiKo-Analyzers
|
opened
|
MiKo_3075 for private classes should be aware of private classes inheriting
|
bug Area: analyzer Area: maintainability
|
If a class is private and the containing class contains other private classes, inspect them for inheriting from a private class. Report a violation only in case there is no other private class that's inheriting from the class.
|
True
|
MiKo_3075 for private classes should be aware of private classes inheriting - If a class is private and the containing class contains other private classes, inspect them for inheriting from a private class. Report a violation only in case there is no other private class that's inheriting from the class.
|
main
|
miko for private classes should be aware of private classes inheriting if a class is private and the containing class contains other private classes inspect them for inheriting from a private class report a violation only in case there is no other private class that s inheriting from the class
| 1
|
437,199
| 30,591,579,781
|
IssuesEvent
|
2023-07-21 17:32:10
|
MrXcitement/devc-fortran
|
https://api.github.com/repos/MrXcitement/devc-fortran
|
opened
|
Readme should explain how to use the generated devcontainer image
|
documentation
|
The Readme was written before I had implemented the github action that built and pushed the devcontainer image.
There needs to be a usage section for how to use the devcontainer image to develop fortran programs.
|
1.0
|
Readme should explain how to use the generated devcontainer image - The Readme was written before I had implemented the github action that built and pushed the devcontainer image.
There needs to be a usage section for how to use the devcontainer image to develop fortran programs.
|
non_main
|
readme should explain how to use the generated devcontainer image the readme was written before i had implemented the github action that built and pushed the devcontainer image there needs to be a usage section for how to use the devcontainer image to develop fortran programs
| 0
|
5,501
| 27,457,964,921
|
IssuesEvent
|
2023-03-02 23:17:34
|
ipfs/ipfs-docs
|
https://api.github.com/repos/ipfs/ipfs-docs
|
closed
|
Consolidate "Basic Concepts" into 1-2 page overview
|
dif/hard P2 need/analysis need/maintainers-input effort/days
|
Currently, we have 8 pages under _Concepts_ > _Basic Concepts_. These pages existed before the recent content reorganization, and were just reshuffled. There has been discussion about how we might combine some of these pages into a similar, more concise _Basic Concepts_ section. The purpose of this issue is to discuss and settle on a refactor.
Assignee: @ElPaisano
Epic: https://github.com/ipfs/ipfs-docs/issues/1432
Proposed Task:
- [ ] Read pages currently under _Basic Concepts_ and note the following:
- Duplicate content
- Outdated content
- Incorrect content
- Missing content
- Confusing / misleading content
- Broken links / links that should probably go somewhere else
- Anything else that can be improved
- [ ] Create PR to rewrite basic concepts into 1-2 pages
|
True
|
Consolidate "Basic Concepts" into 1-2 page overview - Currently, we have 8 pages under _Concepts_ > _Basic Concepts_. These pages existed before the recent content reorganization, and were just reshuffled. There has been discussion about how we might combine some of these pages into a similar, more concise _Basic Concepts_ section. The purpose of this issue is to discuss and settle on a refactor.
Assignee: @ElPaisano
Epic: https://github.com/ipfs/ipfs-docs/issues/1432
Proposed Task:
- [ ] Read pages currently under _Basic Concepts_ and note the following:
- Duplicate content
- Outdated content
- Incorrect content
- Missing content
- Confusing / misleading content
- Broken links / links that should probably go somewhere else
- Anything else that can be improved
- [ ] Create PR to rewrite basic concepts into 1-2 pages
|
main
|
consolidate basic concepts into page overview currently we have pages under concepts basic concepts these pages existed before the recent content reorganization and were just reshuffled there has been discussion about how we might combine some of these pages into a similar more concise basic concepts section the purpose of this issue is to discuss and settle on a refactor assignee elpaisano epic proposed task read pages currently under basic concepts and note the following duplicate content outdated content incorrect content missing content confusing misleading content broken links links that should probably go somewhere else anything else that can be improved create pr to rewrite basic concepts into pages
| 1
|
328,183
| 24,173,416,553
|
IssuesEvent
|
2022-09-22 21:37:20
|
microsoftgraph/microsoft-graph-docs
|
https://api.github.com/repos/microsoftgraph/microsoft-graph-docs
|
closed
|
The shortlink for the overview video is broken
|
area: teams bug: documentation MSTeams-Developer-Support
|
The shortlink for the Microsoft Teams API overview video `https://aka.ms/teamsgraph/v1/video` is broken. After some fiddling with the link it looks like it should point to `https://aka.ms/teamsgraph` instead – although I'm not really sure about that, as it's actually a link to this very page (that does have a video at the very beginning, though...).
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: ba4f5720-3eb2-fe1d-472e-497d1449f97b
* Version Independent ID: eaa22434-4691-77e2-8905-bf6d7e9e0bef
* Content: [Microsoft Teams API overview - Microsoft Graph](https://docs.microsoft.com/en-us/graph/teams-concept-overview)
* Content Source: [concepts/teams-concept-overview.md](https://github.com/microsoftgraph/microsoft-graph-docs/blob/main/concepts/teams-concept-overview.md)
* Product: **microsoft-teams**
* Technology: **microsoft-graph**
* GitHub Login: @nkramer
* Microsoft Alias: **MSGraphDocsVteam**
|
1.0
|
The shortlink for the overview video is broken - The shortlink for the Microsoft Teams API overview video `https://aka.ms/teamsgraph/v1/video` is broken. After some fiddling with the link it looks like it should point to `https://aka.ms/teamsgraph` instead – although I'm not really sure about that, as it's actually a link to this very page (that does have a video at the very beginning, though...).
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: ba4f5720-3eb2-fe1d-472e-497d1449f97b
* Version Independent ID: eaa22434-4691-77e2-8905-bf6d7e9e0bef
* Content: [Microsoft Teams API overview - Microsoft Graph](https://docs.microsoft.com/en-us/graph/teams-concept-overview)
* Content Source: [concepts/teams-concept-overview.md](https://github.com/microsoftgraph/microsoft-graph-docs/blob/main/concepts/teams-concept-overview.md)
* Product: **microsoft-teams**
* Technology: **microsoft-graph**
* GitHub Login: @nkramer
* Microsoft Alias: **MSGraphDocsVteam**
|
non_main
|
the shortlink for the overview video is broken the shortlink for the microsoft teams api overview video is broken after some fiddling with the link it looks like it should point to instead – although i m not really sure about that as it s actually a link to this very page that does have a video at the very beginning though document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source product microsoft teams technology microsoft graph github login nkramer microsoft alias msgraphdocsvteam
| 0
|
4,075
| 19,249,926,101
|
IssuesEvent
|
2021-12-09 03:07:39
|
aws/aws-sam-cli
|
https://api.github.com/repos/aws/aws-sam-cli
|
closed
|
sam local invoke executes with AWS CLI profile instead of provided IAM role
|
type/feature blocked/more-info-needed maintainer/need-followup
|
### Description:
A developer on our sam project attempted to build and locally invoke a Function resource. The (Python 3.8) function in question calls [list_users](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/cognito-idp.html#CognitoIdentityProvider.Client.list_users). Her IAM user role does not have the appropriate permissions; however, the ARN of a role that _does_ was provided in the function's Role in the project's template.yaml. This role has been used in other functions and seems to be correctly associated with them on deployment.
Her local invocation failed, however, with the following error:
`An error occurred (AccessDeniedException) when calling the ListUsers operation: User: [her IAM user ARN] is not authorized to perform: cognito-idp:ListUsers on resource: [the user pool ARN]`
### Steps to reproduce:
Using the IAM console, create an IAM role with the appropriate permissions for a Lambda function to assume it and to call list_users on a user pool. Create an IAM user without those permissions.
Sign into the AWS CLI as the IAM user without list_users.
Add a function to a sam project and pass the ARN of the list_users role as its Role parameter.
`sam build` and `sam local invoke` that function.
### Observed result:
AccessDeniedException
### Expected result:
The function should execute with the provided role
### Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
1. OS: OS X Big Sur version 11.1
2. `sam --version`: 1.23.0
3. AWS region: us-east-1
I am aware that it's not the _best_ practice to grant developers the ability to assume permissions through Lambda functions that they wouldn't be granted normally. In this case, I am not concerned with the scope of access but concerned that a more-permissive IAM user role might let a function with a restrictive IAM role work locally but hit AccessDeniedException on deployment.
|
True
|
sam local invoke executes with AWS CLI profile instead of provided IAM role - ### Description:
A developer on our sam project attempted to build and locally invoke a Function resource. The (Python 3.8) function in question calls [list_users](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/cognito-idp.html#CognitoIdentityProvider.Client.list_users). Her IAM user role does not have the appropriate permissions; however, the ARN of a role that _does_ was provided in the function's Role in the project's template.yaml. This role has been used in other functions and seems to be correctly associated with them on deployment.
Her local invocation failed, however, with the following error:
`An error occurred (AccessDeniedException) when calling the ListUsers operation: User: [her IAM user ARN] is not authorized to perform: cognito-idp:ListUsers on resource: [the user pool ARN]`
### Steps to reproduce:
Using the IAM console, create an IAM role with the appropriate permissions for a Lambda function to assume it and to call list_users on a user pool. Create an IAM user without those permissions.
Sign into the AWS CLI as the IAM user without list_users.
Add a function to a sam project and pass the ARN of the list_users role as its Role parameter.
`sam build` and `sam local invoke` that function.
### Observed result:
AccessDeniedException
### Expected result:
The function should execute with the provided role
### Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
1. OS: OS X Big Sur version 11.1
2. `sam --version`: 1.23.0
3. AWS region: us-east-1
I am aware that it's not the _best_ practice to grant developers the ability to assume permissions through Lambda functions that they wouldn't be granted normally. In this case, I am not concerned with the scope of access but concerned that a more-permissive IAM user role might let a function with a restrictive IAM role work locally but hit AccessDeniedException on deployment.
|
main
|
sam local invoke executes with aws cli profile instead of provided iam role description a developer on our sam project attempted to build and locally invoke a function resource the python function in question calls her iam user role does not have the appropriate permissions however the arn of a role that does was provided in the function s role in the project s template yaml this role has been used in other functions and seems to be correctly associated with them on deployment her local invocation failed however with the following error an error occurred accessdeniedexception when calling the listusers operation user is not authorized to perform cognito idp listusers on resource steps to reproduce using the iam console create an iam role with the appropriate permissions for a lambda function to assume it and to call list users on a user pool create an iam user without those permissions sign into the aws cli as the iam user without list users add a function to a sam project and pass the arn of the list users role as its role parameter sam build and sam local invoke that function observed result accessdeniedexception expected result the function should execute with the provided role additional environment details ex windows mac amazon linux etc os os x big sur version sam version aws region us east i am aware that it s not the best practice to grant developers the ability to assume permissions through lambda functions that they wouldn t be granted normally in this case i am not concerned with the scope of access but concerned that a more permissive iam user role might let a function with a restrictive iam role work locally but hit accessdeniedexception on deployment
| 1
|
96,415
| 8,614,218,643
|
IssuesEvent
|
2018-11-19 16:54:04
|
SME-Issues/issues
|
https://api.github.com/repos/SME-Issues/issues
|
closed
|
Query Invoice Tests Comprehension Partial - 19/11/2018 - 5004
|
NLP Api pulse_tests
|
**Query Invoice Tests Comprehension Partial**
- Total: 21
- Passed: 7
- **Full Pass: 6 (30%)**
- Not Understood: 1
- Failed but Understood: 14 (70%)
|
1.0
|
Query Invoice Tests Comprehension Partial - 19/11/2018 - 5004 - **Query Invoice Tests Comprehension Partial**
- Total: 21
- Passed: 7
- **Full Pass: 6 (30%)**
- Not Understood: 1
- Failed but Understood: 14 (70%)
|
non_main
|
query invoice tests comprehension partial query invoice tests comprehension partial total passed full pass not understood failed but understood
| 0
|
60,783
| 25,258,157,528
|
IssuesEvent
|
2022-11-15 20:03:15
|
cityofaustin/atd-data-tech
|
https://api.github.com/repos/cityofaustin/atd-data-tech
|
closed
|
Update iMOPED models
|
Workgroup: ATSD Service: Geo
|
The models that help update the iMOPED data are running very slowly because the databases they need to write and read from are really big.
I created new databases, pointed the models to it, and the process is much faster and without crashing now.
|
1.0
|
Update iMOPED models - The models that help update the iMOPED data are running very slowly because the databases they need to write and read from are really big.
I created new databases, pointed the models to it, and the process is much faster and without crashing now.
|
non_main
|
update imoped models the models that help update the imoped data are running very slowly because the databases they need to write and read from are really big i created new databases pointed the models to it and the process is much faster and without crashing now
| 0
|
4,671
| 24,157,004,732
|
IssuesEvent
|
2022-09-22 08:32:42
|
cncf/glossary
|
https://api.github.com/repos/cncf/glossary
|
closed
|
Issues on labeler workflow
|
maintainers
|
Hi, I would like to share my observation on the labeler workflow issues. (PTAL @seokho-son)
#### 1. Failing on labeling
Several days ago, the labeler workflow was updated and re-enabled on the upstream. But, the workflow (i.e.,.github/workflows/labeler.yml) hasn't been applied yet on every `dev-**` branch. Thus, I expected this issue would be resolved naturally. Until then, please ignore the error.
#### 2. Awaiting approval from a maintainer
I should have expected such an inconvenient operation... When the first-time contributors create a PR, the labeler workflow will ask the approval from a maintainer. An alternative to this is to run the workflow as a cron job. In this case, I'm concerned about the request limit on GitHub Actions.
Comments, advice, concerns, and contributions are always welcome =)
|
True
|
Issues on labeler workflow - Hi, I would like to share my observation on the labeler workflow issues. (PTAL @seokho-son)
#### 1. Failing on labeling
Several days ago, the labeler workflow was updated and re-enabled on the upstream. But, the workflow (i.e.,.github/workflows/labeler.yml) hasn't been applied yet on every `dev-**` branch. Thus, I expected this issue would be resolved naturally. Until then, please ignore the error.
#### 2. Awaiting approval from a maintainer
I should have expected such an inconvenient operation... When the first-time contributors create a PR, the labeler workflow will ask the approval from a maintainer. An alternative to this is to run the workflow as a cron job. In this case, I'm concerned about the request limit on GitHub Actions.
Comments, advice, concerns, and contributions are always welcome =)
|
main
|
issues on labeler workflow hi i would like to share my observation on the labeler workflow issues ptal seokho son failing on labeling several days ago the labeler workflow was updated and re enabled on the upstream but the workflow i e github workflows labeler yml hasn t been applied yet on every dev branch thus i expected this issue would be resolved naturally until then please ignore the error awaiting approval from a maintainer i should have expected such an inconvenient operation when the first time contributors create a pr the labeler workflow will ask the approval from a maintainer an alternative to this is to run the workflow as a cron job in this case i m concerned about the request limit on github actions comments advice concerns and contributions are always welcome
| 1
|
202,992
| 15,326,516,271
|
IssuesEvent
|
2021-02-26 03:48:11
|
kubernetes/kubernetes
|
https://api.github.com/repos/kubernetes/kubernetes
|
opened
|
[Failing Test] ServiceAccounts ServiceAccountIssuerDiscovery should support OIDC discovery of service account issuer [Conformance]
|
kind/failing-test
|
<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
#### Which jobs are failing:
`ci-kubernetes-gce-conformance-latest-kubetest2`
#### Which test(s) are failing:
`Kubernetes e2e suite.[sig-auth] ServiceAccounts ServiceAccountIssuerDiscovery should support OIDC discovery of service account issuer [Conformance] `
#### Since when has it been failing:
Fairly new job, but it's the only Conformance test which is failing consistently.
#### Testgrid link:
https://testgrid.k8s.io/conformance-all#Conformance%20-%20GCE%20-%20master%20-%20kubetest2
#### Reason for failure:
e.g. https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-gce-conformance-latest-kubetest2/1365061586389045248
```
Feb 25 23:28:50.753: INFO: Pod logs:
2021/02/25 23:28:19 OK: Got token
2021/02/25 23:28:19 OK: got issuer https://kubernetes.io/kubetest2
2021/02/25 23:28:19 Full, not-validated claims:
openidmetadata.claims{Claims:jwt.Claims{Issuer:"https://kubernetes.io/kubetest2", Subject:"system:serviceaccount:svcaccounts-5085:default", Audience:jwt.Audience{"oidc-discovery-test"}, Expiry:1614296299, NotBefore:1614295699, IssuedAt:1614295699, ID:""}, Kubernetes:openidmetadata.kubeClaims{Namespace:"svcaccounts-5085", ServiceAccount:openidmetadata.kubeName{Name:"default", UID:"de16732d-7e39-46b8-8d7d-44bde84f9a91"}}}
2021/02/25 23:28:19 Get "https://kubernetes.io/kubetest2/.well-known/openid-configuration": x509: certificate signed by unknown authority
```
#### Anything else we need to know:
This is a new job as part of migration to kubetest2 effort: https://github.com/kubernetes/enhancements/issues/2464
Comparing it to: https://testgrid.k8s.io/conformance-all#conformance,%20master%20(dev)
e.g
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-kind-conformance/1365089519384137728
```
Feb 26 00:43:27.144: INFO: Pod logs:
2021/02/26 00:42:55 OK: Got token
2021/02/26 00:42:55 OK: got issuer https://kubernetes.default.svc.cluster.local
2021/02/26 00:42:55 Full, not-validated claims:
openidmetadata.claims{Claims:jwt.Claims{Issuer:"https://kubernetes.default.svc.cluster.local", Subject:"system:serviceaccount:svcaccounts-5425:default", Audience:jwt.Audience{"oidc-discovery-test"}, Expiry:1614300775, NotBefore:1614300175, IssuedAt:1614300175, ID:""}, Kubernetes:openidmetadata.kubeClaims{Namespace:"svcaccounts-5425", ServiceAccount:openidmetadata.kubeName{Name:"default", UID:"2591919d-84ec-42a0-9976-80803df8dedd"}}}
2021/02/26 00:42:55 OK: Constructed OIDC provider for issuer https://kubernetes.default.svc.cluster.local
2021/02/26 00:42:55 OK: Validated signature on JWT
2021/02/26 00:42:55 OK: Got valid claims from token!
2021/02/26 00:42:55 Full, validated claims:
&openidmetadata.claims{Claims:jwt.Claims{Issuer:"https://kubernetes.default.svc.cluster.local", Subject:"system:serviceaccount:svcaccounts-5425:default", Audience:jwt.Audience{"oidc-discovery-test"}, Expiry:1614300775, NotBefore:1614300175, IssuedAt:1614300175, ID:""}, Kubernetes:openidmetadata.kubeClaims{Namespace:"svcaccounts-5425", ServiceAccount:openidmetadata.kubeName{Name:"default", UID:"2591919d-84ec-42a0-9976-80803df8dedd"}}}
```
The issuer seems to differ `https://kubernetes.io/kubetest2` vs `https://kubernetes.default.svc.cluster.local`
would be good to know why/where it's coming from, especially to know if there's a discrepancy/inherent assumptions in how the cluster needs to be created.
This doesn't seem to be related to another issue regarding the same test: https://github.com/kubernetes/kubernetes/issues/99470
/cc @BenTheElder @spiffxp
@kubernetes/sig-auth-bugs
|
1.0
|
[Failing Test] ServiceAccounts ServiceAccountIssuerDiscovery should support OIDC discovery of service account issuer [Conformance] - <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->
#### Which jobs are failing:
`ci-kubernetes-gce-conformance-latest-kubetest2`
#### Which test(s) are failing:
`Kubernetes e2e suite.[sig-auth] ServiceAccounts ServiceAccountIssuerDiscovery should support OIDC discovery of service account issuer [Conformance] `
#### Since when has it been failing:
Fairly new job, but it's the only Conformance test which is failing consistently.
#### Testgrid link:
https://testgrid.k8s.io/conformance-all#Conformance%20-%20GCE%20-%20master%20-%20kubetest2
#### Reason for failure:
e.g. https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-gce-conformance-latest-kubetest2/1365061586389045248
```
Feb 25 23:28:50.753: INFO: Pod logs:
2021/02/25 23:28:19 OK: Got token
2021/02/25 23:28:19 OK: got issuer https://kubernetes.io/kubetest2
2021/02/25 23:28:19 Full, not-validated claims:
openidmetadata.claims{Claims:jwt.Claims{Issuer:"https://kubernetes.io/kubetest2", Subject:"system:serviceaccount:svcaccounts-5085:default", Audience:jwt.Audience{"oidc-discovery-test"}, Expiry:1614296299, NotBefore:1614295699, IssuedAt:1614295699, ID:""}, Kubernetes:openidmetadata.kubeClaims{Namespace:"svcaccounts-5085", ServiceAccount:openidmetadata.kubeName{Name:"default", UID:"de16732d-7e39-46b8-8d7d-44bde84f9a91"}}}
2021/02/25 23:28:19 Get "https://kubernetes.io/kubetest2/.well-known/openid-configuration": x509: certificate signed by unknown authority
```
#### Anything else we need to know:
This is a new job as part of migration to kubetest2 effort: https://github.com/kubernetes/enhancements/issues/2464
Comparing it to: https://testgrid.k8s.io/conformance-all#conformance,%20master%20(dev)
e.g
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-kind-conformance/1365089519384137728
```
Feb 26 00:43:27.144: INFO: Pod logs:
2021/02/26 00:42:55 OK: Got token
2021/02/26 00:42:55 OK: got issuer https://kubernetes.default.svc.cluster.local
2021/02/26 00:42:55 Full, not-validated claims:
openidmetadata.claims{Claims:jwt.Claims{Issuer:"https://kubernetes.default.svc.cluster.local", Subject:"system:serviceaccount:svcaccounts-5425:default", Audience:jwt.Audience{"oidc-discovery-test"}, Expiry:1614300775, NotBefore:1614300175, IssuedAt:1614300175, ID:""}, Kubernetes:openidmetadata.kubeClaims{Namespace:"svcaccounts-5425", ServiceAccount:openidmetadata.kubeName{Name:"default", UID:"2591919d-84ec-42a0-9976-80803df8dedd"}}}
2021/02/26 00:42:55 OK: Constructed OIDC provider for issuer https://kubernetes.default.svc.cluster.local
2021/02/26 00:42:55 OK: Validated signature on JWT
2021/02/26 00:42:55 OK: Got valid claims from token!
2021/02/26 00:42:55 Full, validated claims:
&openidmetadata.claims{Claims:jwt.Claims{Issuer:"https://kubernetes.default.svc.cluster.local", Subject:"system:serviceaccount:svcaccounts-5425:default", Audience:jwt.Audience{"oidc-discovery-test"}, Expiry:1614300775, NotBefore:1614300175, IssuedAt:1614300175, ID:""}, Kubernetes:openidmetadata.kubeClaims{Namespace:"svcaccounts-5425", ServiceAccount:openidmetadata.kubeName{Name:"default", UID:"2591919d-84ec-42a0-9976-80803df8dedd"}}}
```
The issuer seems to differ `https://kubernetes.io/kubetest2` vs `https://kubernetes.default.svc.cluster.local`
would be good to know why/where it's coming from, especially to know if there's a discrepancy/inherent assumptions in how the cluster needs to be created.
This doesn't seem to be related to another issue regarding the same test: https://github.com/kubernetes/kubernetes/issues/99470
/cc @BenTheElder @spiffxp
@kubernetes/sig-auth-bugs
|
non_main
|
serviceaccounts serviceaccountissuerdiscovery should support oidc discovery of service account issuer which jobs are failing ci kubernetes gce conformance latest which test s are failing kubernetes suite serviceaccounts serviceaccountissuerdiscovery should support oidc discovery of service account issuer since when has it been failing fairly new job but it s the only conformance test which is failing consistently testgrid link reason for failure e g feb info pod logs ok got token ok got issuer full not validated claims openidmetadata claims claims jwt claims issuer subject system serviceaccount svcaccounts default audience jwt audience oidc discovery test expiry notbefore issuedat id kubernetes openidmetadata kubeclaims namespace svcaccounts serviceaccount openidmetadata kubename name default uid get certificate signed by unknown authority anything else we need to know this is a new job as part of migration to effort comparing it to e g feb info pod logs ok got token ok got issuer full not validated claims openidmetadata claims claims jwt claims issuer subject system serviceaccount svcaccounts default audience jwt audience oidc discovery test expiry notbefore issuedat id kubernetes openidmetadata kubeclaims namespace svcaccounts serviceaccount openidmetadata kubename name default uid ok constructed oidc provider for issuer ok validated signature on jwt ok got valid claims from token full validated claims openidmetadata claims claims jwt claims issuer subject system serviceaccount svcaccounts default audience jwt audience oidc discovery test expiry notbefore issuedat id kubernetes openidmetadata kubeclaims namespace svcaccounts serviceaccount openidmetadata kubename name default uid the issuer seems to differ vs would be good to know why where it s coming from especially to know if there s a discrepancy inherent assumptions in how the cluster needs to be created this doesn t seem to be related to another issue regarding the same test cc bentheelder spiffxp kubernetes sig auth bugs
| 0
|
3,588
| 14,480,162,114
|
IssuesEvent
|
2020-12-10 10:47:12
|
RalfKoban/MiKo-Analyzers
|
https://api.github.com/repos/RalfKoban/MiKo-Analyzers
|
opened
|
Disposable types should throw ObjectDisposedException on each property/method
|
Area: analyzer Area: maintainability feature
|
A type that implements `IDisposable` should throw a `ObjectDisposedException` on each of its public/protected/internal methods (except for the `Dispose` method) to indicate a programming error.
This could be done either directly or indirectly via another method (e.g. a private one)
|
True
|
Disposable types should throw ObjectDisposedException on each property/method - A type that implements `IDisposable` should throw a `ObjectDisposedException` on each of its public/protected/internal methods (except for the `Dispose` method) to indicate a programming error.
This could be done either directly or indirectly via another method (e.g. a private one)
|
main
|
disposable types should throw objectdisposedexception on each property method a type that implements idisposable should throw a objectdisposedexception on each of its public protected internal methods except for the dispose method to indicate a programming error this could be done either directly or indirectly via another method e g a private one
| 1
|
307,316
| 9,415,423,244
|
IssuesEvent
|
2019-04-10 12:37:28
|
WoWManiaUK/Blackwing-Lair
|
https://api.github.com/repos/WoWManiaUK/Blackwing-Lair
|
closed
|
[NPC/Vendor-21145] Little Azimi - Bloodmyst Isle-
|
Fixed Confirmed Fixed in Dev Priority zone 1-20
|
**Links:**
[Little Azimi ](https://www.wowhead.com/npc=21145/little-azimi)
**What is happening:**
Vendor does not sell item
**What should happen:**
Vendor need to sell item
|
1.0
|
[NPC/Vendor-21145] Little Azimi - Bloodmyst Isle- - **Links:**
[Little Azimi ](https://www.wowhead.com/npc=21145/little-azimi)
**What is happening:**
Vendor does not sell item
**What should happen:**
Vendor need to sell item
|
non_main
|
little azimi bloodmyst isle links what is happening vendor does not sell item what should happen vendor need to sell item
| 0
|
12,995
| 3,297,787,829
|
IssuesEvent
|
2015-11-02 10:55:22
|
binidini/tytymyty-ios
|
https://api.github.com/repos/binidini/tytymyty-ios
|
closed
|
настройки уведомления для отправителя
|
test
|
сейчас вижу настройки только для курьера - нужны и для отправителя
также нужно указать что настройки смс и email можно изменить на сайте --- либо реализовать в приложении
тоже для андройд
|
1.0
|
настройки уведомления для отправителя - сейчас вижу настройки только для курьера - нужны и для отправителя
также нужно указать что настройки смс и email можно изменить на сайте --- либо реализовать в приложении
тоже для андройд
|
non_main
|
настройки уведомления для отправителя сейчас вижу настройки только для курьера нужны и для отправителя также нужно указать что настройки смс и email можно изменить на сайте либо реализовать в приложении тоже для андройд
| 0
|
5,880
| 32,004,100,940
|
IssuesEvent
|
2023-09-21 13:55:21
|
MozillaFoundation/foundation.mozilla.org
|
https://api.github.com/repos/MozillaFoundation/foundation.mozilla.org
|
closed
|
Fix exception type and `org` in `review_app_admin.py`, replace `GITHUB_TOKEN`
|
bug engineering maintain
|
### Describe the bug
Whether through some sort of deprecation or some other nonsense, the review apps haven't been able to create an admin user and the app crashes when it can't. It's because the `GITHUB_TOKEN` environment variable for the review apps on Heroku is expired, so this needs replaced. Also, the `org` variable in `review_app_admin.py` is set to our old org of `mozilla` and not `MozillaFoundation` and needs to be changed before this 301 disappears. We're also trying to catch `ObjectDoesNotExist`, so let's maybe get more specific with `User.DoesNotExist` to handle the case of no admin user existing.
Example:
```
Creating Donate Site record in Wagtail
[32;1mDone![0m
Setting up DNS records and Sites for review app
Traceback (most recent call last):
File "/app/network-api/networkapi/management/commands/review_app_admin.py", line 20, in handle
User.objects.get(username="admin")
File "/app/.heroku/python/lib/python3.9/site-packages/django/db/models/manager.py", line 85, in manager_method
return getattr(self.get_queryset(), name)(*args, **kwargs)
File "/app/.heroku/python/lib/python3.9/site-packages/django/db/models/query.py", line 435, in get
raise self.model.DoesNotExist(
django.contrib.auth.models.User.DoesNotExist: User matching query does not exist.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/app/network-api/manage.py", line 35, in <module>
execute_from_command_line(sys.argv)
File "/app/.heroku/python/lib/python3.9/site-packages/django/core/management/__init__.py", line 419, in execute_from_command_line
utility.execute()
File "/app/.heroku/python/lib/python3.9/site-packages/django/core/management/__init__.py", line 413, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/app/.heroku/python/lib/python3.9/site-packages/django/core/management/base.py", line 354, in run_from_argv
self.execute(*args, **cmd_options)
File "/app/.heroku/python/lib/python3.9/site-packages/django/core/management/base.py", line 398, in execute
output = self.handle(*args, **options)
File "/app/network-api/networkapi/management/commands/review_app_admin.py", line 47, in handle
r.raise_for_status()
File "/app/.heroku/python/lib/python3.9/site-packages/requests/models.py", line 1021, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 401 Client Error: Unauthorized for url: https://api.github.com/repos/mozilla/foundation.mozilla.org/pulls/11139
```
### To Reproduce
Steps to reproduce the behavior:
1. Create a review app from a branch or PR on Heroku
2. Watch it crash and burn
### Expected behavior
Admin account is created, sent to our Slack channel, app finishes deploy on Heroku
|
True
|
Fix exception type and `org` in `review_app_admin.py`, replace `GITHUB_TOKEN` - ### Describe the bug
Whether through some sort of deprecation or some other nonsense, the review apps haven't been able to create an admin user and the app crashes when it can't. It's because the `GITHUB_TOKEN` environment variable for the review apps on Heroku is expired, so this needs replaced. Also, the `org` variable in `review_app_admin.py` is set to our old org of `mozilla` and not `MozillaFoundation` and needs to be changed before this 301 disappears. We're also trying to catch `ObjectDoesNotExist`, so let's maybe get more specific with `User.DoesNotExist` to handle the case of no admin user existing.
Example:
```
Creating Donate Site record in Wagtail
[32;1mDone![0m
Setting up DNS records and Sites for review app
Traceback (most recent call last):
File "/app/network-api/networkapi/management/commands/review_app_admin.py", line 20, in handle
User.objects.get(username="admin")
File "/app/.heroku/python/lib/python3.9/site-packages/django/db/models/manager.py", line 85, in manager_method
return getattr(self.get_queryset(), name)(*args, **kwargs)
File "/app/.heroku/python/lib/python3.9/site-packages/django/db/models/query.py", line 435, in get
raise self.model.DoesNotExist(
django.contrib.auth.models.User.DoesNotExist: User matching query does not exist.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/app/network-api/manage.py", line 35, in <module>
execute_from_command_line(sys.argv)
File "/app/.heroku/python/lib/python3.9/site-packages/django/core/management/__init__.py", line 419, in execute_from_command_line
utility.execute()
File "/app/.heroku/python/lib/python3.9/site-packages/django/core/management/__init__.py", line 413, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/app/.heroku/python/lib/python3.9/site-packages/django/core/management/base.py", line 354, in run_from_argv
self.execute(*args, **cmd_options)
File "/app/.heroku/python/lib/python3.9/site-packages/django/core/management/base.py", line 398, in execute
output = self.handle(*args, **options)
File "/app/network-api/networkapi/management/commands/review_app_admin.py", line 47, in handle
r.raise_for_status()
File "/app/.heroku/python/lib/python3.9/site-packages/requests/models.py", line 1021, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 401 Client Error: Unauthorized for url: https://api.github.com/repos/mozilla/foundation.mozilla.org/pulls/11139
```
### To Reproduce
Steps to reproduce the behavior:
1. Create a review app from a branch or PR on Heroku
2. Watch it crash and burn
### Expected behavior
Admin account is created, sent to our Slack channel, app finishes deploy on Heroku
|
main
|
fix exception type and org in review app admin py replace github token describe the bug whether through some sort of deprecation or some other nonsense the review apps haven t been able to create an admin user and the app crashes when it can t it s because the github token environment variable for the review apps on heroku is expired so this needs replaced also the org variable in review app admin py is set to our old org of mozilla and not mozillafoundation and needs to be changed before this disappears we re also trying to catch objectdoesnotexist so let s maybe get more specific with user doesnotexist to handle the case of no admin user existing example creating donate site record in wagtail setting up dns records and sites for review app traceback most recent call last file app network api networkapi management commands review app admin py line in handle user objects get username admin file app heroku python lib site packages django db models manager py line in manager method return getattr self get queryset name args kwargs file app heroku python lib site packages django db models query py line in get raise self model doesnotexist django contrib auth models user doesnotexist user matching query does not exist during handling of the above exception another exception occurred traceback most recent call last file app network api manage py line in execute from command line sys argv file app heroku python lib site packages django core management init py line in execute from command line utility execute file app heroku python lib site packages django core management init py line in execute self fetch command subcommand run from argv self argv file app heroku python lib site packages django core management base py line in run from argv self execute args cmd options file app heroku python lib site packages django core management base py line in execute output self handle args options file app network api networkapi management commands review app admin py line in handle r raise for status file app heroku python lib site packages requests models py line in raise for status raise httperror http error msg response self requests exceptions httperror client error unauthorized for url to reproduce steps to reproduce the behavior create a review app from a branch or pr on heroku watch it crash and burn expected behavior admin account is created sent to our slack channel app finishes deploy on heroku
| 1
|
1,650
| 6,572,678,788
|
IssuesEvent
|
2017-09-11 04:20:38
|
ansible/ansible-modules-extras
|
https://api.github.com/repos/ansible/ansible-modules-extras
|
closed
|
blockinfile marker is null while replace the last line
|
affects_2.2 bug_report waiting_on_maintainer
|
<!--- Verify first that your issue/request is not already reported in GitHub -->
##### ISSUE TYPE
<!--- Pick one below and delete the rest: -->
- Bug Report
##### COMPONENT NAME
<!--- Name of the plugin/module/task -->
- blockinfile
##### ANSIBLE VERSION
<!--- Paste verbatim output from “ansible --version” between quotes below -->
```
ansible 2.2.0.0
```
##### CONFIGURATION
<!---
Mention any settings you have changed/added/removed in ansible.cfg
(or using the ANSIBLE_* environment variables).
-->
the default setting
##### OS / ENVIRONMENT
<!---
Mention the OS you are running Ansible from, and the OS you are
managing, or say “N/A” for anything that is not platform-specific.
-->
ubuntu 14.04 3.16.0-37-generic
##### SUMMARY
<!--- Explain the problem briefly -->
- I don't want inser any marker info,but when I set
+ `no` , it will inser `False` befor and after the content
+ `null`,it will inser `None` befor and after the content
+ `""`, it will inser space line befor and after the content
- when set it to "",it will replace the last line
##### STEPS TO REPRODUCE
<!---
For bugs, show exactly how to reproduce the problem.
For new features, show how the feature would be used.
-->
<!--- Paste example playbooks or commands between quotes below -->
```
- name: update nrpe config in /etc/nagios
blockinfile:
backup: yes
marker: ""
dest: /path/to/nrpe_local.cfg
block: command[check_tomcat_curl]=/usr/local/control/nrpe_check/check_tomcat.sh
```
<!--- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- What did you expect to happen when running the steps above? -->
I just don't inser any marker info
##### ACTUAL RESULTS
<!--- What actually happened? If possible run with extra verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes below -->
befor running playbook the file is
```
123456
123456
```
after running playbook the file is
```
123456
command[check_tomcat_curl]=/usr/local/control/nrpe_check/check_tomcat.sh
```
|
True
|
blockinfile marker is null while replace the last line - <!--- Verify first that your issue/request is not already reported in GitHub -->
##### ISSUE TYPE
<!--- Pick one below and delete the rest: -->
- Bug Report
##### COMPONENT NAME
<!--- Name of the plugin/module/task -->
- blockinfile
##### ANSIBLE VERSION
<!--- Paste verbatim output from “ansible --version” between quotes below -->
```
ansible 2.2.0.0
```
##### CONFIGURATION
<!---
Mention any settings you have changed/added/removed in ansible.cfg
(or using the ANSIBLE_* environment variables).
-->
the default setting
##### OS / ENVIRONMENT
<!---
Mention the OS you are running Ansible from, and the OS you are
managing, or say “N/A” for anything that is not platform-specific.
-->
ubuntu 14.04 3.16.0-37-generic
##### SUMMARY
<!--- Explain the problem briefly -->
- I don't want inser any marker info,but when I set
+ `no` , it will inser `False` befor and after the content
+ `null`,it will inser `None` befor and after the content
+ `""`, it will inser space line befor and after the content
- when set it to "",it will replace the last line
##### STEPS TO REPRODUCE
<!---
For bugs, show exactly how to reproduce the problem.
For new features, show how the feature would be used.
-->
<!--- Paste example playbooks or commands between quotes below -->
```
- name: update nrpe config in /etc/nagios
blockinfile:
backup: yes
marker: ""
dest: /path/to/nrpe_local.cfg
block: command[check_tomcat_curl]=/usr/local/control/nrpe_check/check_tomcat.sh
```
<!--- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- What did you expect to happen when running the steps above? -->
I just don't inser any marker info
##### ACTUAL RESULTS
<!--- What actually happened? If possible run with extra verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes below -->
befor running playbook the file is
```
123456
123456
```
after running playbook the file is
```
123456
command[check_tomcat_curl]=/usr/local/control/nrpe_check/check_tomcat.sh
```
|
main
|
blockinfile marker is null while replace the last line issue type bug report component name blockinfile ansible version ansible configuration mention any settings you have changed added removed in ansible cfg or using the ansible environment variables the default setting os environment mention the os you are running ansible from and the os you are managing or say “n a” for anything that is not platform specific ubuntu generic summary i don t want inser any marker info but when i set no it will inser false befor and after the content null it will inser none befor and after the content it will inser space line befor and after the content when set it to it will replace the last line steps to reproduce for bugs show exactly how to reproduce the problem for new features show how the feature would be used name update nrpe config in etc nagios blockinfile backup yes marker dest path to nrpe local cfg block command usr local control nrpe check check tomcat sh expected results i just don t inser any marker info actual results befor running playbook the file is after running playbook the file is command usr local control nrpe check check tomcat sh
| 1
|
2,053
| 6,966,126,448
|
IssuesEvent
|
2017-12-09 15:10:46
|
chocolatey/chocolatey-package-requests
|
https://api.github.com/repos/chocolatey/chocolatey-package-requests
|
closed
|
RFM - Sandboxie
|
Status: Available For Maintainer(s)
|
The sandboxie package is out of date by quite a few versions.
I have contacted the maintainer see:
github.com/dtgm/chocolatey-packages/issues/331
|
True
|
RFM - Sandboxie - The sandboxie package is out of date by quite a few versions.
I have contacted the maintainer see:
github.com/dtgm/chocolatey-packages/issues/331
|
main
|
rfm sandboxie the sandboxie package is out of date by quite a few versions i have contacted the maintainer see github com dtgm chocolatey packages issues
| 1
|
236,291
| 7,748,349,644
|
IssuesEvent
|
2018-05-30 08:02:48
|
Gloirin/m2gTest
|
https://api.github.com/repos/Gloirin/m2gTest
|
closed
|
0002308:
add printing for calendar
|
Calendar Feature Request high priority
|
**Reported by pschuele on 18 Feb 2010 10:38**
add printing for calendar
|
1.0
|
0002308:
add printing for calendar - **Reported by pschuele on 18 Feb 2010 10:38**
add printing for calendar
|
non_main
|
add printing for calendar reported by pschuele on feb add printing for calendar
| 0
|
176,758
| 13,652,082,707
|
IssuesEvent
|
2020-09-27 05:22:43
|
IBM/ibm-spectrum-scale-cloud-install
|
https://api.github.com/repos/IBM/ibm-spectrum-scale-cloud-install
|
closed
|
ecs cluster not deleted after stack deletion
|
Customer Impact: Localized low impact Customer Probability: Medium Environment: AWS Severity: 3 Type: Needs Test
|
We created stack using custom ami and after scale verification, we started deletion. Before deletion, we ran `mmcloudworkflows teardown --stack_name nil-custom`. After successful mmcloudworkflows command, I started stack deletion from UI through cloudformation. But stack deletion failed as its failed to delete bucket and ecscluster.
We know bucket can't be deleted unless its empty but ecs cluster should be deleted.
|
1.0
|
ecs cluster not deleted after stack deletion - We created stack using custom ami and after scale verification, we started deletion. Before deletion, we ran `mmcloudworkflows teardown --stack_name nil-custom`. After successful mmcloudworkflows command, I started stack deletion from UI through cloudformation. But stack deletion failed as its failed to delete bucket and ecscluster.
We know bucket can't be deleted unless its empty but ecs cluster should be deleted.
|
non_main
|
ecs cluster not deleted after stack deletion we created stack using custom ami and after scale verification we started deletion before deletion we ran mmcloudworkflows teardown stack name nil custom after successful mmcloudworkflows command i started stack deletion from ui through cloudformation but stack deletion failed as its failed to delete bucket and ecscluster we know bucket can t be deleted unless its empty but ecs cluster should be deleted
| 0
|
244,284
| 26,375,066,496
|
IssuesEvent
|
2023-01-12 01:15:21
|
Watemlifts/NextSimpleStarter
|
https://api.github.com/repos/Watemlifts/NextSimpleStarter
|
opened
|
WS-2023-0004 (Medium) detected in jszip-3.7.1.tgz, jszip-3.4.0.tgz
|
security vulnerability
|
## WS-2023-0004 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>jszip-3.7.1.tgz</b>, <b>jszip-3.4.0.tgz</b></p></summary>
<p>
<details><summary><b>jszip-3.7.1.tgz</b></p></summary>
<p>Create, read and edit .zip files with JavaScript http://stuartk.com/jszip</p>
<p>Library home page: <a href="https://registry.npmjs.org/jszip/-/jszip-3.7.1.tgz">https://registry.npmjs.org/jszip/-/jszip-3.7.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/jszip/package.json</p>
<p>
Dependency Hierarchy:
- snyk-1.518.0.tgz (Root Library)
- snyk-mvn-plugin-2.25.3.tgz
- java-call-graph-builder-1.19.1.tgz
- :x: **jszip-3.7.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>jszip-3.4.0.tgz</b></p></summary>
<p>Create, read and edit .zip files with JavaScript http://stuartk.com/jszip</p>
<p>Library home page: <a href="https://registry.npmjs.org/jszip/-/jszip-3.4.0.tgz">https://registry.npmjs.org/jszip/-/jszip-3.4.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/snyk-nuget-plugin/node_modules/jszip/package.json</p>
<p>
Dependency Hierarchy:
- snyk-1.518.0.tgz (Root Library)
- snyk-nuget-plugin-1.21.0.tgz
- :x: **jszip-3.4.0.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/Watemlifts/NextSimpleStarter/commit/ac0fa999b44119e16e88460b115294c73ce1f351">ac0fa999b44119e16e88460b115294c73ce1f351</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>
jszip before 3.8.0 does not sanitize filenames when files are loaded with `loadAsync`, which makes the library vunerable to zip-slip attack.
<p>Publish Date: 2023-01-04
<p>URL: <a href=https://github.com/Stuk/jszip/commit/2edab366119c9ee948357c02f1206c28566cdf15>WS-2023-0004</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2023-01-04</p>
<p>Fix Resolution (jszip): 3.8.0</p>
<p>Direct dependency fix Resolution (snyk): 1.519.0</p><p>Fix Resolution (jszip): 3.6.0</p>
<p>Direct dependency fix Resolution (snyk): 1.667.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
WS-2023-0004 (Medium) detected in jszip-3.7.1.tgz, jszip-3.4.0.tgz - ## WS-2023-0004 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>jszip-3.7.1.tgz</b>, <b>jszip-3.4.0.tgz</b></p></summary>
<p>
<details><summary><b>jszip-3.7.1.tgz</b></p></summary>
<p>Create, read and edit .zip files with JavaScript http://stuartk.com/jszip</p>
<p>Library home page: <a href="https://registry.npmjs.org/jszip/-/jszip-3.7.1.tgz">https://registry.npmjs.org/jszip/-/jszip-3.7.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/jszip/package.json</p>
<p>
Dependency Hierarchy:
- snyk-1.518.0.tgz (Root Library)
- snyk-mvn-plugin-2.25.3.tgz
- java-call-graph-builder-1.19.1.tgz
- :x: **jszip-3.7.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>jszip-3.4.0.tgz</b></p></summary>
<p>Create, read and edit .zip files with JavaScript http://stuartk.com/jszip</p>
<p>Library home page: <a href="https://registry.npmjs.org/jszip/-/jszip-3.4.0.tgz">https://registry.npmjs.org/jszip/-/jszip-3.4.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/snyk-nuget-plugin/node_modules/jszip/package.json</p>
<p>
Dependency Hierarchy:
- snyk-1.518.0.tgz (Root Library)
- snyk-nuget-plugin-1.21.0.tgz
- :x: **jszip-3.4.0.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/Watemlifts/NextSimpleStarter/commit/ac0fa999b44119e16e88460b115294c73ce1f351">ac0fa999b44119e16e88460b115294c73ce1f351</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>
jszip before 3.8.0 does not sanitize filenames when files are loaded with `loadAsync`, which makes the library vunerable to zip-slip attack.
<p>Publish Date: 2023-01-04
<p>URL: <a href=https://github.com/Stuk/jszip/commit/2edab366119c9ee948357c02f1206c28566cdf15>WS-2023-0004</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2023-01-04</p>
<p>Fix Resolution (jszip): 3.8.0</p>
<p>Direct dependency fix Resolution (snyk): 1.519.0</p><p>Fix Resolution (jszip): 3.6.0</p>
<p>Direct dependency fix Resolution (snyk): 1.667.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_main
|
ws medium detected in jszip tgz jszip tgz ws medium severity vulnerability vulnerable libraries jszip tgz jszip tgz jszip tgz create read and edit zip files with javascript library home page a href path to dependency file package json path to vulnerable library node modules jszip package json dependency hierarchy snyk tgz root library snyk mvn plugin tgz java call graph builder tgz x jszip tgz vulnerable library jszip tgz create read and edit zip files with javascript library home page a href path to dependency file package json path to vulnerable library node modules snyk nuget plugin node modules jszip package json dependency hierarchy snyk tgz root library snyk nuget plugin tgz x jszip tgz vulnerable library found in head commit a href found in base branch master vulnerability details jszip before does not sanitize filenames when files are loaded with loadasync which makes the library vunerable to zip slip attack publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version release date fix resolution jszip direct dependency fix resolution snyk fix resolution jszip direct dependency fix resolution snyk step up your open source security game with mend
| 0
|
355,915
| 25,176,061,897
|
IssuesEvent
|
2022-11-11 09:22:08
|
shawnkai/pe
|
https://api.github.com/repos/shawnkai/pe
|
opened
|
Lack of disclaimer when editing data file
|
severity.Low type.DocumentationBug
|
When editing data file, users might unintentionally wipe out all data if they edit data to an illegal format. This disclaimer is not mentioned in the UG and might cause serious implications if the user unknowingly does it.
<!--session: 1668149524827-954a4db7-55ce-4f7d-9957-87f255f39ffc-->
<!--Version: Web v3.4.4-->
|
1.0
|
Lack of disclaimer when editing data file - When editing data file, users might unintentionally wipe out all data if they edit data to an illegal format. This disclaimer is not mentioned in the UG and might cause serious implications if the user unknowingly does it.
<!--session: 1668149524827-954a4db7-55ce-4f7d-9957-87f255f39ffc-->
<!--Version: Web v3.4.4-->
|
non_main
|
lack of disclaimer when editing data file when editing data file users might unintentionally wipe out all data if they edit data to an illegal format this disclaimer is not mentioned in the ug and might cause serious implications if the user unknowingly does it
| 0
|
297,226
| 9,162,076,450
|
IssuesEvent
|
2019-03-01 12:21:49
|
webcompat/web-bugs
|
https://api.github.com/repos/webcompat/web-bugs
|
closed
|
innovate.go2cloud.org - see bug description
|
browser-firefox-mobile priority-normal
|
<!-- @browser: Firefox Mobile 66.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 8.0.0; Mobile; rv:66.0) Gecko/66.0 Firefox/66.0 -->
<!-- @reported_with: mobile-reporter -->
**URL**: http://innovate.go2cloud.org/aff_c?offer_id=2194&aff_id=714&aff_sub=MO4_102a0dac7a1adaf71539d7ee054e39&WebViewUserAgent=&device_id=fbfec417-e473-4b70-8c49-c27f575387bd&device_type=android&device_model=&app_id=35cf9d73877c7b3c2643bfd29acedcb4d5aa8d1811ed22e347b49864e85cec2cbf64f2f56e4b2c5e1ba6596abe6e444ec991aa2a3645919109dfd247de0caeac84bef7186d2fa8d36f908486d5894ca321018d75e07e776289411ecf13b6fb89
**Browser / Version**: Firefox Mobile 66.0
**Operating System**: Android 8.0.0
**Tested Another Browser**: No
**Problem type**: Something else
**Description**: no response
**Steps to Reproduce**:
Refreshed keep getting blank screen
<details>
<summary>Browser Configuration</summary>
<ul>
<li>mixed active content blocked: false</li><li>image.mem.shared: true</li><li>buildID: 20190211185957</li><li>tracking content blocked: false</li><li>gfx.webrender.blob-images: true</li><li>hasTouchScreen: true</li><li>mixed passive content blocked: false</li><li>gfx.webrender.enabled: false</li><li>gfx.webrender.all: false</li><li>channel: beta</li>
</ul>
<p>Console Messages:</p>
<pre>
[u'[JavaScript Error: "The character encoding of the plain text document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the file needs to be declared in the transfer protocol or file needs to use a byte order mark as an encoding signature." {file: "http://innovate.go2cloud.org/aff_c?offer_id=2194&aff_id=714&aff_sub=MO4_102a0dac7a1adaf71539d7ee054e39&WebViewUserAgent=&device_id=fbfec417-e473-4b70-8c49-c27f575387bd&device_type=android&device_model=&app_id=35cf9d73877c7b3c2643bfd29acedcb4d5aa8d1811ed22e347b49864e85cec2cbf64f2f56e4b2c5e1ba6596abe6e444ec991aa2a3645919109dfd247de0caeac84bef7186d2fa8d36f908486d5894ca321018d75e07e776289411ecf13b6fb89" line: 0}]']
</pre>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_
|
1.0
|
innovate.go2cloud.org - see bug description - <!-- @browser: Firefox Mobile 66.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 8.0.0; Mobile; rv:66.0) Gecko/66.0 Firefox/66.0 -->
<!-- @reported_with: mobile-reporter -->
**URL**: http://innovate.go2cloud.org/aff_c?offer_id=2194&aff_id=714&aff_sub=MO4_102a0dac7a1adaf71539d7ee054e39&WebViewUserAgent=&device_id=fbfec417-e473-4b70-8c49-c27f575387bd&device_type=android&device_model=&app_id=35cf9d73877c7b3c2643bfd29acedcb4d5aa8d1811ed22e347b49864e85cec2cbf64f2f56e4b2c5e1ba6596abe6e444ec991aa2a3645919109dfd247de0caeac84bef7186d2fa8d36f908486d5894ca321018d75e07e776289411ecf13b6fb89
**Browser / Version**: Firefox Mobile 66.0
**Operating System**: Android 8.0.0
**Tested Another Browser**: No
**Problem type**: Something else
**Description**: no response
**Steps to Reproduce**:
Refreshed keep getting blank screen
<details>
<summary>Browser Configuration</summary>
<ul>
<li>mixed active content blocked: false</li><li>image.mem.shared: true</li><li>buildID: 20190211185957</li><li>tracking content blocked: false</li><li>gfx.webrender.blob-images: true</li><li>hasTouchScreen: true</li><li>mixed passive content blocked: false</li><li>gfx.webrender.enabled: false</li><li>gfx.webrender.all: false</li><li>channel: beta</li>
</ul>
<p>Console Messages:</p>
<pre>
[u'[JavaScript Error: "The character encoding of the plain text document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the file needs to be declared in the transfer protocol or file needs to use a byte order mark as an encoding signature." {file: "http://innovate.go2cloud.org/aff_c?offer_id=2194&aff_id=714&aff_sub=MO4_102a0dac7a1adaf71539d7ee054e39&WebViewUserAgent=&device_id=fbfec417-e473-4b70-8c49-c27f575387bd&device_type=android&device_model=&app_id=35cf9d73877c7b3c2643bfd29acedcb4d5aa8d1811ed22e347b49864e85cec2cbf64f2f56e4b2c5e1ba6596abe6e444ec991aa2a3645919109dfd247de0caeac84bef7186d2fa8d36f908486d5894ca321018d75e07e776289411ecf13b6fb89" line: 0}]']
</pre>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_
|
non_main
|
innovate org see bug description url browser version firefox mobile operating system android tested another browser no problem type something else description no response steps to reproduce refreshed keep getting blank screen browser configuration mixed active content blocked false image mem shared true buildid tracking content blocked false gfx webrender blob images true hastouchscreen true mixed passive content blocked false gfx webrender enabled false gfx webrender all false channel beta console messages from with ❤️
| 0
|
17,355
| 9,740,168,084
|
IssuesEvent
|
2019-06-01 17:52:28
|
github/semantic
|
https://api.github.com/repos/github/semantic
|
opened
|
RWS’ constant-time approximation of edit distance is not actually constant-time
|
bug diffing performance
|
`editDistanceUpTo` is not actually a constant-time approximation of the tree edit distance, because it relies on `cutoff`, which models a bound on recursion depth, but not on traversal count.
The paper refers to their use of “an iterative deepending [sic] top-down matching that stops after a fixed number of compared nodes and is thus in O(1).” It seems likely that this was a typo of [iterative deepening](https://en.wikipedia.org/wiki/Iterative_deepening_depth-first_search). This is the traversal we’d want to place a constant bound on.
|
True
|
RWS’ constant-time approximation of edit distance is not actually constant-time - `editDistanceUpTo` is not actually a constant-time approximation of the tree edit distance, because it relies on `cutoff`, which models a bound on recursion depth, but not on traversal count.
The paper refers to their use of “an iterative deepending [sic] top-down matching that stops after a fixed number of compared nodes and is thus in O(1).” It seems likely that this was a typo of [iterative deepening](https://en.wikipedia.org/wiki/Iterative_deepening_depth-first_search). This is the traversal we’d want to place a constant bound on.
|
non_main
|
rws’ constant time approximation of edit distance is not actually constant time editdistanceupto is not actually a constant time approximation of the tree edit distance because it relies on cutoff which models a bound on recursion depth but not on traversal count the paper refers to their use of “an iterative deepending top down matching that stops after a fixed number of compared nodes and is thus in o ” it seems likely that this was a typo of this is the traversal we’d want to place a constant bound on
| 0
|
218,518
| 24,375,711,156
|
IssuesEvent
|
2022-10-04 00:33:24
|
valtech-ch/microservice-kubernetes-cluster
|
https://api.github.com/repos/valtech-ch/microservice-kubernetes-cluster
|
closed
|
CVE-2022-42003 (Medium) detected in jackson-databind-2.9.8.jar, jackson-databind-2.13.4.jar - autoclosed
|
security vulnerability
|
## CVE-2022-42003 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>jackson-databind-2.9.8.jar</b>, <b>jackson-databind-2.13.4.jar</b></p></summary>
<p>
<details><summary><b>jackson-databind-2.9.8.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: /functions/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.9.8/11283f21cc480aa86c4df7a0a3243ec508372ed2/jackson-databind-2.9.8.jar</p>
<p>
Dependency Hierarchy:
- spring-cloud-function-adapter-azure-3.2.7.jar (Root Library)
- spring-cloud-function-context-3.2.7.jar
- :x: **jackson-databind-2.9.8.jar** (Vulnerable Library)
</details>
<details><summary><b>jackson-databind-2.13.4.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: /persistence/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.13.4/98b0edfa8e4084078f10b7b356c300ded4a71491/jackson-databind-2.13.4.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.13.4/98b0edfa8e4084078f10b7b356c300ded4a71491/jackson-databind-2.13.4.jar,/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.13.4/98b0edfa8e4084078f10b7b356c300ded4a71491/jackson-databind-2.13.4.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.13.4/98b0edfa8e4084078f10b7b356c300ded4a71491/jackson-databind-2.13.4.jar</p>
<p>
Dependency Hierarchy:
- :x: **jackson-databind-2.13.4.jar** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/valtech-ch/microservice-kubernetes-cluster/commit/335a4047c89f52dfe860e93daefb32dc86a521a2">335a4047c89f52dfe860e93daefb32dc86a521a2</a></p>
<p>Found in base branch: <b>develop</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In FasterXML jackson-databind before 2.14.0-rc1, resource exhaustion can occur because of a lack of a check in primitive value deserializers to avoid deep wrapper array nesting, when the UNWRAP_SINGLE_VALUE_ARRAYS feature is enabled.
<p>Publish Date: 2022-10-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-42003>CVE-2022-42003</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2022-42003 (Medium) detected in jackson-databind-2.9.8.jar, jackson-databind-2.13.4.jar - autoclosed - ## CVE-2022-42003 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>jackson-databind-2.9.8.jar</b>, <b>jackson-databind-2.13.4.jar</b></p></summary>
<p>
<details><summary><b>jackson-databind-2.9.8.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: /functions/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.9.8/11283f21cc480aa86c4df7a0a3243ec508372ed2/jackson-databind-2.9.8.jar</p>
<p>
Dependency Hierarchy:
- spring-cloud-function-adapter-azure-3.2.7.jar (Root Library)
- spring-cloud-function-context-3.2.7.jar
- :x: **jackson-databind-2.9.8.jar** (Vulnerable Library)
</details>
<details><summary><b>jackson-databind-2.13.4.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: /persistence/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.13.4/98b0edfa8e4084078f10b7b356c300ded4a71491/jackson-databind-2.13.4.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.13.4/98b0edfa8e4084078f10b7b356c300ded4a71491/jackson-databind-2.13.4.jar,/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.13.4/98b0edfa8e4084078f10b7b356c300ded4a71491/jackson-databind-2.13.4.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.13.4/98b0edfa8e4084078f10b7b356c300ded4a71491/jackson-databind-2.13.4.jar</p>
<p>
Dependency Hierarchy:
- :x: **jackson-databind-2.13.4.jar** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/valtech-ch/microservice-kubernetes-cluster/commit/335a4047c89f52dfe860e93daefb32dc86a521a2">335a4047c89f52dfe860e93daefb32dc86a521a2</a></p>
<p>Found in base branch: <b>develop</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In FasterXML jackson-databind before 2.14.0-rc1, resource exhaustion can occur because of a lack of a check in primitive value deserializers to avoid deep wrapper array nesting, when the UNWRAP_SINGLE_VALUE_ARRAYS feature is enabled.
<p>Publish Date: 2022-10-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-42003>CVE-2022-42003</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_main
|
cve medium detected in jackson databind jar jackson databind jar autoclosed cve medium severity vulnerability vulnerable libraries jackson databind jar jackson databind jar jackson databind jar general data binding functionality for jackson works on core streaming api library home page a href path to dependency file functions 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 cloud function adapter azure jar root library spring cloud function context jar x jackson databind jar 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 persistence build gradle path to vulnerable library home wss scanner gradle caches modules files com fasterxml jackson core jackson databind jackson databind jar home wss scanner gradle caches modules files com fasterxml jackson core jackson databind jackson databind jar files com fasterxml jackson core jackson databind jackson databind jar home wss scanner gradle caches modules files 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 develop vulnerability details in fasterxml jackson databind before resource exhaustion can occur because of a lack of a check in primitive value deserializers to avoid deep wrapper array nesting when the unwrap single value arrays feature is enabled publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href step up your open source security game with mend
| 0
|
5,050
| 25,874,266,099
|
IssuesEvent
|
2022-12-14 06:26:11
|
microsoft/DirectXTex
|
https://api.github.com/repos/microsoft/DirectXTex
|
closed
|
Add Spectre mitigation support to NuGet and vcpkg
|
maintainence
|
For **NuGet**, add an alternative library built with `/p:SpectreMitigation=Spectre` for Desktop (not supported by UWP).
For **vcpkg**, add a ``spectre`` feature that sets a CMake build option ``ENABLE_SPECTRE_MITIGATION=ON``.
|
True
|
Add Spectre mitigation support to NuGet and vcpkg - For **NuGet**, add an alternative library built with `/p:SpectreMitigation=Spectre` for Desktop (not supported by UWP).
For **vcpkg**, add a ``spectre`` feature that sets a CMake build option ``ENABLE_SPECTRE_MITIGATION=ON``.
|
main
|
add spectre mitigation support to nuget and vcpkg for nuget add an alternative library built with p spectremitigation spectre for desktop not supported by uwp for vcpkg add a spectre feature that sets a cmake build option enable spectre mitigation on
| 1
|
10,308
| 7,988,107,691
|
IssuesEvent
|
2018-07-19 09:55:34
|
tine20/tine20
|
https://api.github.com/repos/tine20/tine20
|
closed
|
0013500:
MYSQL-DB PASSWORD LEAKED AFTER UPGRADE !!!
|
Bug Info in Forum Mantis Security Setup
|
**Reported by estradis on 29 Sep 2017 09:46**
We tried to upgrade ubuntu from trusty to xenial, but tine was not working after. Instead of showing the logon screen, the settings were dumped in json format, INCLUDING THE LOGON CREDENTIALS FOR THE MYSQL DATABASE. I've investigated access during this time and fortunatly there were none, except upgrade team.
Since tine is usually accessible from the internet, THIS ISSUE IS A MAJOR SECURITY RISK AND BE SHOULD FIXED IMMEDIATELY!
|
True
|
0013500:
MYSQL-DB PASSWORD LEAKED AFTER UPGRADE !!! - **Reported by estradis on 29 Sep 2017 09:46**
We tried to upgrade ubuntu from trusty to xenial, but tine was not working after. Instead of showing the logon screen, the settings were dumped in json format, INCLUDING THE LOGON CREDENTIALS FOR THE MYSQL DATABASE. I've investigated access during this time and fortunatly there were none, except upgrade team.
Since tine is usually accessible from the internet, THIS ISSUE IS A MAJOR SECURITY RISK AND BE SHOULD FIXED IMMEDIATELY!
|
non_main
|
mysql db password leaked after upgrade reported by estradis on sep we tried to upgrade ubuntu from trusty to xenial but tine was not working after instead of showing the logon screen the settings were dumped in json format including the logon credentials for the mysql database i ve investigated access during this time and fortunatly there were none except upgrade team since tine is usually accessible from the internet this issue is a major security risk and be should fixed immediately
| 0
|
25,745
| 25,813,637,527
|
IssuesEvent
|
2022-12-12 02:02:47
|
doki-theme/doki-theme-vscode
|
https://api.github.com/repos/doki-theme/doki-theme-vscode
|
closed
|
Setting custom assets paths to a directory causes asset install issues.
|
usability
|
<!--
NOTE: Did you check the FAQs (https://one-dark.gitbook.io/jetbrains/help/faqs)
to see if your problem already has a work around?
-->
**Describe the bug**
<!-- A clear and concise description of what the bug is. -->
in the asset help sectioin you say that running as administrator in wondows will fix the issue unable to install Zero Two Dark Obsidian, please see active tab for more information. but even i run it as administrator in doesn't solve I keep trying to add my own background and sticker but it keeps showing the same thing please help
**To Reproduce**
<!-- Steps to reproduce the behavior -->
1.
**Expected Behavior**
<!-- A clear and concise description of what you expected to happen. -->
**Environment**
<!-- Please go to *Help: About* and copy the infos
to the clipboard and paste it here.
It should contain:
* OS (Windows, Linux, Mac)
* Product + version
Please also include the Doki-Theme version
-->
**Screenshots**
<!-- If applicable, add screenshots to help explain your problem. -->
|
True
|
Setting custom assets paths to a directory causes asset install issues. - <!--
NOTE: Did you check the FAQs (https://one-dark.gitbook.io/jetbrains/help/faqs)
to see if your problem already has a work around?
-->
**Describe the bug**
<!-- A clear and concise description of what the bug is. -->
in the asset help sectioin you say that running as administrator in wondows will fix the issue unable to install Zero Two Dark Obsidian, please see active tab for more information. but even i run it as administrator in doesn't solve I keep trying to add my own background and sticker but it keeps showing the same thing please help
**To Reproduce**
<!-- Steps to reproduce the behavior -->
1.
**Expected Behavior**
<!-- A clear and concise description of what you expected to happen. -->
**Environment**
<!-- Please go to *Help: About* and copy the infos
to the clipboard and paste it here.
It should contain:
* OS (Windows, Linux, Mac)
* Product + version
Please also include the Doki-Theme version
-->
**Screenshots**
<!-- If applicable, add screenshots to help explain your problem. -->
|
non_main
|
setting custom assets paths to a directory causes asset install issues note did you check the faqs to see if your problem already has a work around describe the bug in the asset help sectioin you say that running as administrator in wondows will fix the issue unable to install zero two dark obsidian please see active tab for more information but even i run it as administrator in doesn t solve i keep trying to add my own background and sticker but it keeps showing the same thing please help to reproduce expected behavior environment please go to help about and copy the infos to the clipboard and paste it here it should contain os windows linux mac product version please also include the doki theme version screenshots
| 0
|
3,078
| 11,646,100,858
|
IssuesEvent
|
2020-03-01 06:43:00
|
microsoft/DirectXMath
|
https://api.github.com/repos/microsoft/DirectXMath
|
closed
|
C++ enhancements (noexcept, more constexpr, operator[] for some types)
|
maintainence
|
- It would be nice to have an `operator[]` member method for `XMFLOAT2`, `XMFLOAT3`, `XMFLOAT4`, etc. instead of taking the address of the `x` member variable for instance.
- All the methods of non-SIMD structs such as `XMFLOAT2`, `XMFLOAT3`, `XMFLOAT4`, etc. could be made `noexcept` and `constexpr`.
|
True
|
C++ enhancements (noexcept, more constexpr, operator[] for some types) - - It would be nice to have an `operator[]` member method for `XMFLOAT2`, `XMFLOAT3`, `XMFLOAT4`, etc. instead of taking the address of the `x` member variable for instance.
- All the methods of non-SIMD structs such as `XMFLOAT2`, `XMFLOAT3`, `XMFLOAT4`, etc. could be made `noexcept` and `constexpr`.
|
main
|
c enhancements noexcept more constexpr operator for some types it would be nice to have an operator member method for etc instead of taking the address of the x member variable for instance all the methods of non simd structs such as etc could be made noexcept and constexpr
| 1
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.