Unnamed: 0
int64 0
832k
| id
float64 2.49B
32.1B
| type
stringclasses 1
value | created_at
stringlengths 19
19
| repo
stringlengths 5
112
| repo_url
stringlengths 34
141
| action
stringclasses 3
values | title
stringlengths 1
757
| labels
stringlengths 4
664
| body
stringlengths 3
261k
| index
stringclasses 10
values | text_combine
stringlengths 96
261k
| label
stringclasses 2
values | text
stringlengths 96
232k
| binary_label
int64 0
1
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
13,758
| 2,782,443,820
|
IssuesEvent
|
2015-05-06 18:10:35
|
cultibox/cultibox
|
https://api.github.com/repos/cultibox/cultibox
|
closed
|
[cultipi] probleme de lancement
|
Priority-Low Type-Defect
|
```
je n'arrive pas à joindre mon cultipi sous:
http://cultipi.local/cultibox/
ca m'indique :erreur de chargement de la page
par contre, pas de souci avec :
http://192.168.0.11/cultibox/
ca se charge correctment
une fois lancé depuis l'adresse qui marche je peux recliquer sur mon lien
http://cultipi.local/cultibox/ et la ca marche...
```
Original issue reported on code.google.com by `elchaf...@gmail.com` on 17 Mar 2015 at 4:57
|
1.0
|
[cultipi] probleme de lancement - ```
je n'arrive pas à joindre mon cultipi sous:
http://cultipi.local/cultibox/
ca m'indique :erreur de chargement de la page
par contre, pas de souci avec :
http://192.168.0.11/cultibox/
ca se charge correctment
une fois lancé depuis l'adresse qui marche je peux recliquer sur mon lien
http://cultipi.local/cultibox/ et la ca marche...
```
Original issue reported on code.google.com by `elchaf...@gmail.com` on 17 Mar 2015 at 4:57
|
defect
|
probleme de lancement je n arrive pas à joindre mon cultipi sous ca m indique erreur de chargement de la page par contre pas de souci avec ca se charge correctment une fois lancé depuis l adresse qui marche je peux recliquer sur mon lien et la ca marche original issue reported on code google com by elchaf gmail com on mar at
| 1
|
127,309
| 12,312,058,984
|
IssuesEvent
|
2020-05-12 13:24:09
|
epam/fonda
|
https://api.github.com/repos/epam/fonda
|
opened
|
Add overall information on the issue/pr management approach
|
documentation enhancement
|
@kamyshova please add the following information on the overall contribution to the repo and how the issues are tracked:
* Entrypoint:
* `Issue`: if there is only an idea for some feature and fix and it shall be discussed first
* `PR`: if there is already an implementation for some feature or a bug-fix
* What information shall be provided to the Issue/PR description (we need to add Issue/PR templates further), which branch shall be used as a merge destination
* If the issue is created first - how it gets implemented (discussion -> decision)
* If a PR is created first (or a PR is created as a result of work on an issue) - how to request to approval, how it gets discussed, approved, merged
* Any other valuable information of your choice
|
1.0
|
Add overall information on the issue/pr management approach - @kamyshova please add the following information on the overall contribution to the repo and how the issues are tracked:
* Entrypoint:
* `Issue`: if there is only an idea for some feature and fix and it shall be discussed first
* `PR`: if there is already an implementation for some feature or a bug-fix
* What information shall be provided to the Issue/PR description (we need to add Issue/PR templates further), which branch shall be used as a merge destination
* If the issue is created first - how it gets implemented (discussion -> decision)
* If a PR is created first (or a PR is created as a result of work on an issue) - how to request to approval, how it gets discussed, approved, merged
* Any other valuable information of your choice
|
non_defect
|
add overall information on the issue pr management approach kamyshova please add the following information on the overall contribution to the repo and how the issues are tracked entrypoint issue if there is only an idea for some feature and fix and it shall be discussed first pr if there is already an implementation for some feature or a bug fix what information shall be provided to the issue pr description we need to add issue pr templates further which branch shall be used as a merge destination if the issue is created first how it gets implemented discussion decision if a pr is created first or a pr is created as a result of work on an issue how to request to approval how it gets discussed approved merged any other valuable information of your choice
| 0
|
21,072
| 6,975,527,015
|
IssuesEvent
|
2017-12-12 07:31:37
|
etalab/geo.data.gouv.fr
|
https://api.github.com/repos/etalab/geo.data.gouv.fr
|
closed
|
Héberger la police Lato en local
|
build-process enhancement
|
https://www.fontsquirrel.com/fonts/lato
Pour :
* plus de dépendance à Google
* davantage de latitude sur la stratégie de chargement (perfs)
* une dépendance à semanticui de moins
Contre :
* plus lent si on s'y prend mal :)
|
1.0
|
Héberger la police Lato en local - https://www.fontsquirrel.com/fonts/lato
Pour :
* plus de dépendance à Google
* davantage de latitude sur la stratégie de chargement (perfs)
* une dépendance à semanticui de moins
Contre :
* plus lent si on s'y prend mal :)
|
non_defect
|
héberger la police lato en local pour plus de dépendance à google davantage de latitude sur la stratégie de chargement perfs une dépendance à semanticui de moins contre plus lent si on s y prend mal
| 0
|
299,985
| 25,941,199,819
|
IssuesEvent
|
2022-12-16 18:34:45
|
apache/beam
|
https://api.github.com/repos/apache/beam
|
closed
|
ExternalPythonTransformTest.trivialPythonTransform flaky
|
java P1 bug cross-language failing test flake beam-fixit
|
Example run: https://ci-beam.apache.org/job/beam_PreCommit_Java_Phrase/4806/testReport/junit/org.apache.beam.sdk.extensions.python/ExternalPythonTransformTest/trivialPythonTransform/
```
java.lang.RuntimeException: java.util.concurrent.TimeoutException: Timeout waiting for Python service
startup after 16616 seconds.
at org.apache.beam.sdk.extensions.python.ExternalPythonTransform.expand(ExternalPythonTransform.java:107)
at
org.apache.beam.sdk.Pipeline.applyInternal(Pipeline.java:548)
at org.apache.beam.sdk.Pipeline.applyTransform(Pipeline.java:482)
at
org.apache.beam.sdk.values.PCollection.apply(PCollection.java:363)
at org.apache.beam.sdk.extensions.python.ExternalPythonTransformTest.trivialPythonTransform(ExternalPythonTransformTest.java:41)
at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
at
org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
```
Imported from Jira [BEAM-14148](https://issues.apache.org/jira/browse/BEAM-14148). Original Jira may contain additional context.
Reported by: lcwik.
|
1.0
|
ExternalPythonTransformTest.trivialPythonTransform flaky - Example run: https://ci-beam.apache.org/job/beam_PreCommit_Java_Phrase/4806/testReport/junit/org.apache.beam.sdk.extensions.python/ExternalPythonTransformTest/trivialPythonTransform/
```
java.lang.RuntimeException: java.util.concurrent.TimeoutException: Timeout waiting for Python service
startup after 16616 seconds.
at org.apache.beam.sdk.extensions.python.ExternalPythonTransform.expand(ExternalPythonTransform.java:107)
at
org.apache.beam.sdk.Pipeline.applyInternal(Pipeline.java:548)
at org.apache.beam.sdk.Pipeline.applyTransform(Pipeline.java:482)
at
org.apache.beam.sdk.values.PCollection.apply(PCollection.java:363)
at org.apache.beam.sdk.extensions.python.ExternalPythonTransformTest.trivialPythonTransform(ExternalPythonTransformTest.java:41)
at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
at
org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
```
Imported from Jira [BEAM-14148](https://issues.apache.org/jira/browse/BEAM-14148). Original Jira may contain additional context.
Reported by: lcwik.
|
non_defect
|
externalpythontransformtest trivialpythontransform flaky example run java lang runtimeexception java util concurrent timeoutexception timeout waiting for python service startup after seconds at org apache beam sdk extensions python externalpythontransform expand externalpythontransform java at org apache beam sdk pipeline applyinternal pipeline java at org apache beam sdk pipeline applytransform pipeline java at org apache beam sdk values pcollection apply pcollection java at org apache beam sdk extensions python externalpythontransformtest trivialpythontransform externalpythontransformtest java at sun reflect nativemethodaccessorimpl native method at sun reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java lang reflect method invoke method java at org junit runners model frameworkmethod runreflectivecall frameworkmethod java at org junit internal runners model reflectivecallable run reflectivecallable java at org junit runners model frameworkmethod invokeexplosively frameworkmethod java at org junit internal runners statements invokemethod evaluate invokemethod java at org junit runners parentrunner evaluate parentrunner java at org junit runners evaluate java at org junit runners parentrunner runleaf parentrunner java at org junit runners runchild java at org junit runners runchild java at org junit runners parentrunner run parentrunner java imported from jira original jira may contain additional context reported by lcwik
| 0
|
30,152
| 6,033,387,688
|
IssuesEvent
|
2017-06-09 08:10:16
|
moosetechnology/Moose
|
https://api.github.com/repos/moosetechnology/Moose
|
closed
|
Non-interactive visualisations
|
Priority-Medium Type-Defect
|
Originally reported on Google Code with ID 1075
```
Several visualisations are not interactive and they don't provide fly-by-help. E.g.,
name cloud, distribution map, dependency (cycles)
```
Reported by `damien.cassou` on 2014-06-26 14:46:51
|
1.0
|
Non-interactive visualisations - Originally reported on Google Code with ID 1075
```
Several visualisations are not interactive and they don't provide fly-by-help. E.g.,
name cloud, distribution map, dependency (cycles)
```
Reported by `damien.cassou` on 2014-06-26 14:46:51
|
defect
|
non interactive visualisations originally reported on google code with id several visualisations are not interactive and they don t provide fly by help e g name cloud distribution map dependency cycles reported by damien cassou on
| 1
|
18,859
| 3,089,699,327
|
IssuesEvent
|
2015-08-25 23:06:17
|
google/googlemock
|
https://api.github.com/repos/google/googlemock
|
closed
|
Visual Studio 10 release link fails
|
auto-migrated Priority-Medium Type-Defect
|
```
I used svn to get the current release, opened the solution file and selected
batch build of everything.
The release build then fails while linking with this error:
gmock.lib(gtest-all.obj) : error LNK2038: mismatch detected for
'_ITERATOR_DEBUG_LEVEL': value '2' doesn't match value '0' in gmock_all_test.obj
gmock.lib(gmock-all.obj) : error LNK2038: mismatch detected for
'_ITERATOR_DEBUG_LEVEL': value '2' doesn't match value '0' in gmock_all_test.obj
libcpmtd.lib(stdthrow.obj) : error LNK2038: mismatch detected for
'_ITERATOR_DEBUG_LEVEL': value '2' doesn't match value '0' in gmock_all_test.obj
libcpmtd.lib(xdebug.obj) : error LNK2038: mismatch detected for
'_ITERATOR_DEBUG_LEVEL': value '2' doesn't match value '0' in gmock_all_test.obj
LIBCMTD.lib(dbgheap.obj) : error LNK2005: __heap_alloc already defined in
LIBCMT.lib(malloc.obj)
LIBCMTD.lib(dbgheap.obj) : error LNK2005: __recalloc already defined in
LIBCMT.lib(recalloc.obj)
LIBCMTD.lib(dbgheap.obj) : error LNK2005: __msize already defined in
LIBCMT.lib(msize.obj)
LIBCMTD.lib(dbghook.obj) : error LNK2005: __crt_debugger_hook already defined
in LIBCMT.lib(dbghook.obj)
LIBCMTD.lib(isctype.obj) : error LNK2005: __isctype_l already defined in
LIBCMT.lib(isctype.obj)
LIBCMTD.lib(isctype.obj) : error LNK2005: __isctype already defined in
LIBCMT.lib(isctype.obj)
LINK : warning LNK4098: defaultlib 'LIBCMT' conflicts with use of other libs;
use /NODEFAULTLIB:library
LINK : warning LNK4098: defaultlib 'LIBCMTD' conflicts with use of other libs;
use /NODEFAULTLIB:library
D:\dev\3rdparty\googlemock\msvc\2010\Release\gmock_test.exe : fatal error
LNK1169: one or more multiply defined symbols found
Build FAILED.
```
Original issue reported on code.google.com by `l...@schouw.me` on 2 Mar 2013 at 8:29
|
1.0
|
Visual Studio 10 release link fails - ```
I used svn to get the current release, opened the solution file and selected
batch build of everything.
The release build then fails while linking with this error:
gmock.lib(gtest-all.obj) : error LNK2038: mismatch detected for
'_ITERATOR_DEBUG_LEVEL': value '2' doesn't match value '0' in gmock_all_test.obj
gmock.lib(gmock-all.obj) : error LNK2038: mismatch detected for
'_ITERATOR_DEBUG_LEVEL': value '2' doesn't match value '0' in gmock_all_test.obj
libcpmtd.lib(stdthrow.obj) : error LNK2038: mismatch detected for
'_ITERATOR_DEBUG_LEVEL': value '2' doesn't match value '0' in gmock_all_test.obj
libcpmtd.lib(xdebug.obj) : error LNK2038: mismatch detected for
'_ITERATOR_DEBUG_LEVEL': value '2' doesn't match value '0' in gmock_all_test.obj
LIBCMTD.lib(dbgheap.obj) : error LNK2005: __heap_alloc already defined in
LIBCMT.lib(malloc.obj)
LIBCMTD.lib(dbgheap.obj) : error LNK2005: __recalloc already defined in
LIBCMT.lib(recalloc.obj)
LIBCMTD.lib(dbgheap.obj) : error LNK2005: __msize already defined in
LIBCMT.lib(msize.obj)
LIBCMTD.lib(dbghook.obj) : error LNK2005: __crt_debugger_hook already defined
in LIBCMT.lib(dbghook.obj)
LIBCMTD.lib(isctype.obj) : error LNK2005: __isctype_l already defined in
LIBCMT.lib(isctype.obj)
LIBCMTD.lib(isctype.obj) : error LNK2005: __isctype already defined in
LIBCMT.lib(isctype.obj)
LINK : warning LNK4098: defaultlib 'LIBCMT' conflicts with use of other libs;
use /NODEFAULTLIB:library
LINK : warning LNK4098: defaultlib 'LIBCMTD' conflicts with use of other libs;
use /NODEFAULTLIB:library
D:\dev\3rdparty\googlemock\msvc\2010\Release\gmock_test.exe : fatal error
LNK1169: one or more multiply defined symbols found
Build FAILED.
```
Original issue reported on code.google.com by `l...@schouw.me` on 2 Mar 2013 at 8:29
|
defect
|
visual studio release link fails i used svn to get the current release opened the solution file and selected batch build of everything the release build then fails while linking with this error gmock lib gtest all obj error mismatch detected for iterator debug level value doesn t match value in gmock all test obj gmock lib gmock all obj error mismatch detected for iterator debug level value doesn t match value in gmock all test obj libcpmtd lib stdthrow obj error mismatch detected for iterator debug level value doesn t match value in gmock all test obj libcpmtd lib xdebug obj error mismatch detected for iterator debug level value doesn t match value in gmock all test obj libcmtd lib dbgheap obj error heap alloc already defined in libcmt lib malloc obj libcmtd lib dbgheap obj error recalloc already defined in libcmt lib recalloc obj libcmtd lib dbgheap obj error msize already defined in libcmt lib msize obj libcmtd lib dbghook obj error crt debugger hook already defined in libcmt lib dbghook obj libcmtd lib isctype obj error isctype l already defined in libcmt lib isctype obj libcmtd lib isctype obj error isctype already defined in libcmt lib isctype obj link warning defaultlib libcmt conflicts with use of other libs use nodefaultlib library link warning defaultlib libcmtd conflicts with use of other libs use nodefaultlib library d dev googlemock msvc release gmock test exe fatal error one or more multiply defined symbols found build failed original issue reported on code google com by l schouw me on mar at
| 1
|
6,914
| 2,610,306,008
|
IssuesEvent
|
2015-02-26 19:38:24
|
chrsmith/hedgewars
|
https://api.github.com/repos/chrsmith/hedgewars
|
closed
|
The 0.9.16 source tarball is missing files
|
auto-migrated Priority-Critical Type-Defect
|
```
The Hedgewars 0.9.16 source tarball, available at
http://download.gna.org/hedgewars/hedgewars-src-0.9.16.tar.bz2 , is missing at
least one directory — `misc/liblua` — when compared to the main source
repository. This results in a CMake error when trying to build Hedgewars from
the source tarball:
CMake Error at CMakeLists.txt:192 (add_subdirectory):
add_subdirectory given source "misc/liblua" which is not an existing
directory.
```
-----
Original issue reported on code.google.com by `andrey.vihrov` on 17 Sep 2011 at 5:29
|
1.0
|
The 0.9.16 source tarball is missing files - ```
The Hedgewars 0.9.16 source tarball, available at
http://download.gna.org/hedgewars/hedgewars-src-0.9.16.tar.bz2 , is missing at
least one directory — `misc/liblua` — when compared to the main source
repository. This results in a CMake error when trying to build Hedgewars from
the source tarball:
CMake Error at CMakeLists.txt:192 (add_subdirectory):
add_subdirectory given source "misc/liblua" which is not an existing
directory.
```
-----
Original issue reported on code.google.com by `andrey.vihrov` on 17 Sep 2011 at 5:29
|
defect
|
the source tarball is missing files the hedgewars source tarball available at is missing at least one directory — misc liblua — when compared to the main source repository this results in a cmake error when trying to build hedgewars from the source tarball cmake error at cmakelists txt add subdirectory add subdirectory given source misc liblua which is not an existing directory original issue reported on code google com by andrey vihrov on sep at
| 1
|
28,554
| 5,289,364,412
|
IssuesEvent
|
2017-02-08 17:12:06
|
gwaldron/osgearth
|
https://api.github.com/repos/gwaldron/osgearth
|
opened
|
master/2.8: WFS always appends "?SERVICE=..." to URL
|
defect HP
|
It needs to check and see whether there is already a "?" in the base URL, and if so use an ampersand instead.
|
1.0
|
master/2.8: WFS always appends "?SERVICE=..." to URL - It needs to check and see whether there is already a "?" in the base URL, and if so use an ampersand instead.
|
defect
|
master wfs always appends service to url it needs to check and see whether there is already a in the base url and if so use an ampersand instead
| 1
|
350,642
| 10,499,787,469
|
IssuesEvent
|
2019-09-26 09:07:45
|
modxcms/revolution
|
https://api.github.com/repos/modxcms/revolution
|
closed
|
Error in core\model\phpthumb\phpthumb.class.php 990
|
area-core bug priority-2-high state/accepting-pull-request
|
## Bug report
### Summary
Notice: Use of undefined constant IMG_WEBP - assumed 'IMG_WEBP' in \core\model\phpthumb\phpthumb.class.php on line 990
### Step to reproduce
Rename "core" and "manager" directories/
Create TV named "image". Media sources: default and custom, same problem.
don't show images thumbnails in /manager/
### Observed behavior
If i comment or delete code from line 990
```
if ($imagetypes & IMG_WEBP) {
$this->thumbnailFormat = 'webp';
$AvailableImageOutputFormats[] = 'webp';
}
```
everythig is ok.
screenshots
[error in code](http://перекраска-дома.рф/phpthumb_modx.png)
[no thumbnail](http://перекраска-дома.рф/modx_manager.png)
### Environment
MODX 2.7.1, php 7.0.8 , mysql 5.5, Fitefox 65.0.2. Using openserver 5.2.2
|
1.0
|
Error in core\model\phpthumb\phpthumb.class.php 990 - ## Bug report
### Summary
Notice: Use of undefined constant IMG_WEBP - assumed 'IMG_WEBP' in \core\model\phpthumb\phpthumb.class.php on line 990
### Step to reproduce
Rename "core" and "manager" directories/
Create TV named "image". Media sources: default and custom, same problem.
don't show images thumbnails in /manager/
### Observed behavior
If i comment or delete code from line 990
```
if ($imagetypes & IMG_WEBP) {
$this->thumbnailFormat = 'webp';
$AvailableImageOutputFormats[] = 'webp';
}
```
everythig is ok.
screenshots
[error in code](http://перекраска-дома.рф/phpthumb_modx.png)
[no thumbnail](http://перекраска-дома.рф/modx_manager.png)
### Environment
MODX 2.7.1, php 7.0.8 , mysql 5.5, Fitefox 65.0.2. Using openserver 5.2.2
|
non_defect
|
error in core model phpthumb phpthumb class php bug report summary notice use of undefined constant img webp assumed img webp in core model phpthumb phpthumb class php on line step to reproduce rename core and manager directories create tv named image media sources default and custom same problem don t show images thumbnails in manager observed behavior if i comment or delete code from line if imagetypes img webp this thumbnailformat webp availableimageoutputformats webp everythig is ok screenshots environment modx php mysql fitefox using openserver
| 0
|
833
| 2,594,148,987
|
IssuesEvent
|
2015-02-20 00:11:06
|
BALL-Project/ball
|
https://api.github.com/repos/BALL-Project/ball
|
closed
|
Test suite failing
|
C: BALL Core P: major R: fixed T: defect
|
**Reported by Thomas Pr tzlich on 7 Apr 38777282 17:46 UTC**
The following subtests failed:
- RMSDMinimizer_test
|
1.0
|
Test suite failing - **Reported by Thomas Pr tzlich on 7 Apr 38777282 17:46 UTC**
The following subtests failed:
- RMSDMinimizer_test
|
defect
|
test suite failing reported by thomas pr tzlich on apr utc the following subtests failed rmsdminimizer test
| 1
|
204,981
| 7,093,344,076
|
IssuesEvent
|
2018-01-12 20:05:40
|
StrangeLoopGames/EcoIssues
|
https://api.github.com/repos/StrangeLoopGames/EcoIssues
|
closed
|
rubble dropping from the sky, sometimes just sits there ##cc778b68
|
Medium Priority
|
When loading in game it is taking longer and longer (possibly still due to loading in uncollected rubble and debris?), and we can seerubble dropping from the sky, but as you can see by last snap shot it sometimes still is hanging there




|
1.0
|
rubble dropping from the sky, sometimes just sits there ##cc778b68 - When loading in game it is taking longer and longer (possibly still due to loading in uncollected rubble and debris?), and we can seerubble dropping from the sky, but as you can see by last snap shot it sometimes still is hanging there




|
non_defect
|
rubble dropping from the sky sometimes just sits there when loading in game it is taking longer and longer possibly still due to loading in uncollected rubble and debris and we can seerubble dropping from the sky but as you can see by last snap shot it sometimes still is hanging there
| 0
|
18,487
| 3,067,708,183
|
IssuesEvent
|
2015-08-18 12:11:49
|
openivef/ivef-sdk
|
https://api.github.com/repos/openivef/ivef-sdk
|
closed
|
Restrictions are not yet implemented
|
auto-migrated Priority-Medium Type-Defect
|
```
The restrictions maxLength and minLength are not taken into account by the
code generator. This can result in XML which is not valid according to the
xsd.
minLength and maxLength should be taken into account to produce XML which
validates according to the XSD.
```
Original issue reported on code.google.com by `Danny.Smit.0@gmail.com` on 27 Apr 2010 at 9:21
|
1.0
|
Restrictions are not yet implemented - ```
The restrictions maxLength and minLength are not taken into account by the
code generator. This can result in XML which is not valid according to the
xsd.
minLength and maxLength should be taken into account to produce XML which
validates according to the XSD.
```
Original issue reported on code.google.com by `Danny.Smit.0@gmail.com` on 27 Apr 2010 at 9:21
|
defect
|
restrictions are not yet implemented the restrictions maxlength and minlength are not taken into account by the code generator this can result in xml which is not valid according to the xsd minlength and maxlength should be taken into account to produce xml which validates according to the xsd original issue reported on code google com by danny smit gmail com on apr at
| 1
|
424,507
| 12,312,119,165
|
IssuesEvent
|
2020-05-12 13:29:19
|
ScottishCovidResponse/SCRCIssueTracking
|
https://api.github.com/repos/ScottishCovidResponse/SCRCIssueTracking
|
closed
|
Check .gitignore is OK (e.g. ignore .pyc files, source data, output .pdfs?)
|
Simple Network Sim Top Priority
|
Produce a `.gitignore` to be agreed by team.
|
1.0
|
Check .gitignore is OK (e.g. ignore .pyc files, source data, output .pdfs?) - Produce a `.gitignore` to be agreed by team.
|
non_defect
|
check gitignore is ok e g ignore pyc files source data output pdfs produce a gitignore to be agreed by team
| 0
|
87,162
| 10,880,689,481
|
IssuesEvent
|
2019-11-17 12:59:17
|
Xeverous/filter_spirit
|
https://api.github.com/repos/Xeverous/filter_spirit
|
closed
|
optional bounds for price queries
|
design documentation enhancement grammar
|
There should be a way to specify only lower or upper price bound of the query. Currently if you want 100c+ divination cards you can write `$divination | price(100, 999999)` however such workaround:
- is not very appealing, unintuitive to use
- has a hidden limit defined by the implementation (max integer value)
- may cause hidden problems (when eg a card giving mirror is worth some huge number in chaos)
Current idea: `_` keyword, indicating "no value". That is, `$divination | price(100, _)`. One might propose `price(100,)` but it might look weird and I would like to avoid optional tokens in the grammar.
Any thoughts?
|
1.0
|
optional bounds for price queries - There should be a way to specify only lower or upper price bound of the query. Currently if you want 100c+ divination cards you can write `$divination | price(100, 999999)` however such workaround:
- is not very appealing, unintuitive to use
- has a hidden limit defined by the implementation (max integer value)
- may cause hidden problems (when eg a card giving mirror is worth some huge number in chaos)
Current idea: `_` keyword, indicating "no value". That is, `$divination | price(100, _)`. One might propose `price(100,)` but it might look weird and I would like to avoid optional tokens in the grammar.
Any thoughts?
|
non_defect
|
optional bounds for price queries there should be a way to specify only lower or upper price bound of the query currently if you want divination cards you can write divination price however such workaround is not very appealing unintuitive to use has a hidden limit defined by the implementation max integer value may cause hidden problems when eg a card giving mirror is worth some huge number in chaos current idea keyword indicating no value that is divination price one might propose price but it might look weird and i would like to avoid optional tokens in the grammar any thoughts
| 0
|
483,493
| 13,925,682,831
|
IssuesEvent
|
2020-10-21 17:11:08
|
CDH-Studio/I-Talent
|
https://api.github.com/repos/CDH-Studio/I-Talent
|
closed
|
Add a "privacy" pop up message upon logging into the application
|
client request enhancement frontend medium priority
|
**Is your feature request related to a problem? Please describe.**
In I-Talent, employees will be providing information that is considered "personal" such as education. It's important that they confirm they understand the legistlation that applies and how the information will be used.
**The solution**
Everytime a user logs in to I-Talent they should be prompted with a Message (with a privacy notice statement)
They will be required to confirm by clicking on an "ok" button.
Text for the statement in both languages to follow.

|
1.0
|
Add a "privacy" pop up message upon logging into the application - **Is your feature request related to a problem? Please describe.**
In I-Talent, employees will be providing information that is considered "personal" such as education. It's important that they confirm they understand the legistlation that applies and how the information will be used.
**The solution**
Everytime a user logs in to I-Talent they should be prompted with a Message (with a privacy notice statement)
They will be required to confirm by clicking on an "ok" button.
Text for the statement in both languages to follow.

|
non_defect
|
add a privacy pop up message upon logging into the application is your feature request related to a problem please describe in i talent employees will be providing information that is considered personal such as education it s important that they confirm they understand the legistlation that applies and how the information will be used the solution everytime a user logs in to i talent they should be prompted with a message with a privacy notice statement they will be required to confirm by clicking on an ok button text for the statement in both languages to follow
| 0
|
5,865
| 2,610,216,924
|
IssuesEvent
|
2015-02-26 19:09:06
|
chrsmith/somefinders
|
https://api.github.com/repos/chrsmith/somefinders
|
opened
|
petousb exe
|
auto-migrated Priority-Medium Type-Defect
|
```
'''Ахмат Беляев'''
День добрый никак не могу найти .petousb exe. как
то выкладывали уже
'''Алексей Пестов'''
Качай тут http://bit.ly/1dYMFRv
'''Вольмир Суханов'''
Спасибо вроде то но просит телефон вводить
'''Венедикт Захаров'''
Неа все ок у меня ничего не списало
'''Аксён Воробьёв'''
Не это не влияет на баланс
Информация о файле: petousb exe
Загружен: В этом месяце
Скачан раз: 762
Рейтинг: 1108
Средняя скорость скачивания: 384
Похожих файлов: 33
```
-----
Original issue reported on code.google.com by `kondense...@gmail.com` on 16 Dec 2013 at 9:46
|
1.0
|
petousb exe - ```
'''Ахмат Беляев'''
День добрый никак не могу найти .petousb exe. как
то выкладывали уже
'''Алексей Пестов'''
Качай тут http://bit.ly/1dYMFRv
'''Вольмир Суханов'''
Спасибо вроде то но просит телефон вводить
'''Венедикт Захаров'''
Неа все ок у меня ничего не списало
'''Аксён Воробьёв'''
Не это не влияет на баланс
Информация о файле: petousb exe
Загружен: В этом месяце
Скачан раз: 762
Рейтинг: 1108
Средняя скорость скачивания: 384
Похожих файлов: 33
```
-----
Original issue reported on code.google.com by `kondense...@gmail.com` on 16 Dec 2013 at 9:46
|
defect
|
petousb exe ахмат беляев день добрый никак не могу найти petousb exe как то выкладывали уже алексей пестов качай тут вольмир суханов спасибо вроде то но просит телефон вводить венедикт захаров неа все ок у меня ничего не списало аксён воробьёв не это не влияет на баланс информация о файле petousb exe загружен в этом месяце скачан раз рейтинг средняя скорость скачивания похожих файлов original issue reported on code google com by kondense gmail com on dec at
| 1
|
426,597
| 12,374,881,554
|
IssuesEvent
|
2020-05-19 02:55:55
|
buddyboss/buddyboss-platform
|
https://api.github.com/repos/buddyboss/buddyboss-platform
|
opened
|
Messages and Notifications to SMS
|
feature: enhancement priority: medium
|
I would like to see the ability to provide notification to users via SMS messaging.
For younger community members (say under 25 years old) email correspondence is "not a thing". Their email inbox is the last place they go for communication. In contrast, email is still relied on by many other personas.
While the REST API should greatly assist in the development of mobile applications, adding SMS functionality to the platform would go a long way in the mobile realm.
Here are my start on requirements for text communication between members:
As a member, I would like to receive a text message alert via my cell phone number when I receive a new message in BuddyBoss. It should include the following information in the text message as a minimum:
- Site name
- Sender name
- URL link to recipient's message page in BuddyBoss
https://www.sitename.com/members/username/messages/
As a member, I would like to receive a text message alert via my cell phone number when I receive a new notification in BuddyBoss. It should include the following information as minimum:
- Notification type
- Sender or group name
- Notification text if applicable
- Link to recipient's notification page
https://www.sitename.com/members/username/notifications/
As a member, I would like the ability to control whether I receive text alerts when I receive a message in BuddyBoss (on or off) in the Email settings (rename to Email & Text Settings)
As a member, I would like the ability to control whether I receive text alerts of a BuddyBoss notification. (on or off) in the Email settings.
As a system administrator, I would like to be able to send text messages without asking the user to specify the carrier (AT&T, Verizon etc.)
As a system administrator, I would like to send text messages using existing SMS sending services. I would specifically like to integrate with Amazon's SNS service.
As a system administrator, I would like to be able to turn on or off the use of SMS alerts for either messages or notifications or both.
As an administrator, I would like to avoid installing a plugin for this functionality.
|
1.0
|
Messages and Notifications to SMS - I would like to see the ability to provide notification to users via SMS messaging.
For younger community members (say under 25 years old) email correspondence is "not a thing". Their email inbox is the last place they go for communication. In contrast, email is still relied on by many other personas.
While the REST API should greatly assist in the development of mobile applications, adding SMS functionality to the platform would go a long way in the mobile realm.
Here are my start on requirements for text communication between members:
As a member, I would like to receive a text message alert via my cell phone number when I receive a new message in BuddyBoss. It should include the following information in the text message as a minimum:
- Site name
- Sender name
- URL link to recipient's message page in BuddyBoss
https://www.sitename.com/members/username/messages/
As a member, I would like to receive a text message alert via my cell phone number when I receive a new notification in BuddyBoss. It should include the following information as minimum:
- Notification type
- Sender or group name
- Notification text if applicable
- Link to recipient's notification page
https://www.sitename.com/members/username/notifications/
As a member, I would like the ability to control whether I receive text alerts when I receive a message in BuddyBoss (on or off) in the Email settings (rename to Email & Text Settings)
As a member, I would like the ability to control whether I receive text alerts of a BuddyBoss notification. (on or off) in the Email settings.
As a system administrator, I would like to be able to send text messages without asking the user to specify the carrier (AT&T, Verizon etc.)
As a system administrator, I would like to send text messages using existing SMS sending services. I would specifically like to integrate with Amazon's SNS service.
As a system administrator, I would like to be able to turn on or off the use of SMS alerts for either messages or notifications or both.
As an administrator, I would like to avoid installing a plugin for this functionality.
|
non_defect
|
messages and notifications to sms i would like to see the ability to provide notification to users via sms messaging for younger community members say under years old email correspondence is not a thing their email inbox is the last place they go for communication in contrast email is still relied on by many other personas while the rest api should greatly assist in the development of mobile applications adding sms functionality to the platform would go a long way in the mobile realm here are my start on requirements for text communication between members as a member i would like to receive a text message alert via my cell phone number when i receive a new message in buddyboss it should include the following information in the text message as a minimum site name sender name url link to recipient s message page in buddyboss as a member i would like to receive a text message alert via my cell phone number when i receive a new notification in buddyboss it should include the following information as minimum notification type sender or group name notification text if applicable link to recipient s notification page as a member i would like the ability to control whether i receive text alerts when i receive a message in buddyboss on or off in the email settings rename to email text settings as a member i would like the ability to control whether i receive text alerts of a buddyboss notification on or off in the email settings as a system administrator i would like to be able to send text messages without asking the user to specify the carrier at t verizon etc as a system administrator i would like to send text messages using existing sms sending services i would specifically like to integrate with amazon s sns service as a system administrator i would like to be able to turn on or off the use of sms alerts for either messages or notifications or both as an administrator i would like to avoid installing a plugin for this functionality
| 0
|
9,390
| 2,615,147,352
|
IssuesEvent
|
2015-03-01 06:23:36
|
chrsmith/html5rocks
|
https://api.github.com/repos/chrsmith/html5rocks
|
closed
|
html5rocks.com front page needs to include a list of features
|
auto-migrated features Milestone-3 Priority-Medium Type-Defect
|
```
What steps will reproduce the problem?
1.
2.
3.
What is the expected output? What do you see instead?
Please use labels and text to provide additional information.
```
Original issue reported on code.google.com by `v...@google.com` on 24 Sep 2010 at 5:30
|
1.0
|
html5rocks.com front page needs to include a list of features - ```
What steps will reproduce the problem?
1.
2.
3.
What is the expected output? What do you see instead?
Please use labels and text to provide additional information.
```
Original issue reported on code.google.com by `v...@google.com` on 24 Sep 2010 at 5:30
|
defect
|
com front page needs to include a list of features what steps will reproduce the problem what is the expected output what do you see instead please use labels and text to provide additional information original issue reported on code google com by v google com on sep at
| 1
|
67,456
| 20,961,613,565
|
IssuesEvent
|
2022-03-27 21:49:41
|
abedmaatalla/sipdroid
|
https://api.github.com/repos/abedmaatalla/sipdroid
|
closed
|
Other part can not hear me
|
Priority-Medium Type-Defect auto-migrated
|
```
When calling to an iphone with acrobits softphone the other end can not hear me.
I'm on a samsung galaxy s2
Last beta of sipdroid.
```
Original issue reported on code.google.com by `eliosfed...@gmail.com` on 29 Nov 2011 at 7:34
- Merged into: #2
|
1.0
|
Other part can not hear me - ```
When calling to an iphone with acrobits softphone the other end can not hear me.
I'm on a samsung galaxy s2
Last beta of sipdroid.
```
Original issue reported on code.google.com by `eliosfed...@gmail.com` on 29 Nov 2011 at 7:34
- Merged into: #2
|
defect
|
other part can not hear me when calling to an iphone with acrobits softphone the other end can not hear me i m on a samsung galaxy last beta of sipdroid original issue reported on code google com by eliosfed gmail com on nov at merged into
| 1
|
9,165
| 3,024,947,740
|
IssuesEvent
|
2015-08-03 02:50:29
|
stan-dev/math
|
https://api.github.com/repos/stan-dev/math
|
closed
|
Travis yml broken
|
testing
|
## Bug Report
__Version__
2.7.0
__Description__
Travis yml tries to clone stan and use its libraries. These have moved to the Math library.
__Steps__
See travis output.
|
1.0
|
Travis yml broken - ## Bug Report
__Version__
2.7.0
__Description__
Travis yml tries to clone stan and use its libraries. These have moved to the Math library.
__Steps__
See travis output.
|
non_defect
|
travis yml broken bug report version description travis yml tries to clone stan and use its libraries these have moved to the math library steps see travis output
| 0
|
19,085
| 3,137,198,491
|
IssuesEvent
|
2015-09-11 00:16:00
|
ArctosDB/arctos
|
https://api.github.com/repos/ArctosDB/arctos
|
closed
|
image loader is broken
|
Type-Defect Usability
|
```
What steps will reproduce the problem?
1. upload ZIP file
2. get the media bulkloader template
3. it won't load
rebuild template-builder
```
Original issue reported on code.google.com by `dust...@gmail.com` on 11 Dec 2014 at 2:15
|
1.0
|
image loader is broken - ```
What steps will reproduce the problem?
1. upload ZIP file
2. get the media bulkloader template
3. it won't load
rebuild template-builder
```
Original issue reported on code.google.com by `dust...@gmail.com` on 11 Dec 2014 at 2:15
|
defect
|
image loader is broken what steps will reproduce the problem upload zip file get the media bulkloader template it won t load rebuild template builder original issue reported on code google com by dust gmail com on dec at
| 1
|
67,464
| 20,961,613,785
|
IssuesEvent
|
2022-03-27 21:49:44
|
abedmaatalla/sipdroid
|
https://api.github.com/repos/abedmaatalla/sipdroid
|
closed
|
unable to use bluetooth earpiece/handset with sipdroid and tablet.
|
Priority-Medium Type-Defect auto-migrated
|
```
Tablet:pocket edge
Handset: thinkgeek bluetooth handset.
I have used sipdroid with my bluetooth headphones flawlessly.
The only problem is that its microphone is lacking.
So I purchased a bluetooth handset from thinkdroid.
But sipdroid on the pocket edge seems to only send audio through the media
audio out(the speakers).
My handset is connected via "edge audio" only.
My headphones connects via "edge audio and media audio"
Can you guys build in a sound out switcher into sipdroid?
I have tried a couple of bluetooth sound routing programs but none worked.
I think the only way to fix this is give sipdroid users the ability to choose
the audio out and audio in(together or separately).
I am also looking into a paid account to get that better audio codec.
```
Original issue reported on code.google.com by `manofli...@gmail.com` on 13 Jan 2012 at 12:20
- Merged into: #561
|
1.0
|
unable to use bluetooth earpiece/handset with sipdroid and tablet. - ```
Tablet:pocket edge
Handset: thinkgeek bluetooth handset.
I have used sipdroid with my bluetooth headphones flawlessly.
The only problem is that its microphone is lacking.
So I purchased a bluetooth handset from thinkdroid.
But sipdroid on the pocket edge seems to only send audio through the media
audio out(the speakers).
My handset is connected via "edge audio" only.
My headphones connects via "edge audio and media audio"
Can you guys build in a sound out switcher into sipdroid?
I have tried a couple of bluetooth sound routing programs but none worked.
I think the only way to fix this is give sipdroid users the ability to choose
the audio out and audio in(together or separately).
I am also looking into a paid account to get that better audio codec.
```
Original issue reported on code.google.com by `manofli...@gmail.com` on 13 Jan 2012 at 12:20
- Merged into: #561
|
defect
|
unable to use bluetooth earpiece handset with sipdroid and tablet tablet pocket edge handset thinkgeek bluetooth handset i have used sipdroid with my bluetooth headphones flawlessly the only problem is that its microphone is lacking so i purchased a bluetooth handset from thinkdroid but sipdroid on the pocket edge seems to only send audio through the media audio out the speakers my handset is connected via edge audio only my headphones connects via edge audio and media audio can you guys build in a sound out switcher into sipdroid i have tried a couple of bluetooth sound routing programs but none worked i think the only way to fix this is give sipdroid users the ability to choose the audio out and audio in together or separately i am also looking into a paid account to get that better audio codec original issue reported on code google com by manofli gmail com on jan at merged into
| 1
|
40,182
| 9,885,854,632
|
IssuesEvent
|
2019-06-25 04:25:39
|
PList-Net/PList-Net
|
https://api.github.com/repos/PList-Net/PList-Net
|
closed
|
Unicode detection does not work.
|
Priority-Medium Type-Defect auto-migrated
|
```
What steps will reproduce the problem?
1. Create a PListString with non-ASCII characters. For instance "Mikkel Løkke"
2. Note that although this string can be (and more importantly *is*) written as
UTF-8 it is still wrapped in <ustring> tags.
3. This will cause iOS to determine that a profile is invalid.
What is the expected output? What do you see instead?
An utf-8 string wrapped in <string> tags. An utf-8 string wrapped in <ustring>
tags.
What version of the product are you using?
Latest version from nuGet on .net 4.0
```
Original issue reported on code.google.com by `m.loe...@m2p.dk` on 10 Jan 2013 at 1:47
|
1.0
|
Unicode detection does not work. - ```
What steps will reproduce the problem?
1. Create a PListString with non-ASCII characters. For instance "Mikkel Løkke"
2. Note that although this string can be (and more importantly *is*) written as
UTF-8 it is still wrapped in <ustring> tags.
3. This will cause iOS to determine that a profile is invalid.
What is the expected output? What do you see instead?
An utf-8 string wrapped in <string> tags. An utf-8 string wrapped in <ustring>
tags.
What version of the product are you using?
Latest version from nuGet on .net 4.0
```
Original issue reported on code.google.com by `m.loe...@m2p.dk` on 10 Jan 2013 at 1:47
|
defect
|
unicode detection does not work what steps will reproduce the problem create a pliststring with non ascii characters for instance mikkel løkke note that although this string can be and more importantly is written as utf it is still wrapped in tags this will cause ios to determine that a profile is invalid what is the expected output what do you see instead an utf string wrapped in tags an utf string wrapped in tags what version of the product are you using latest version from nuget on net original issue reported on code google com by m loe dk on jan at
| 1
|
10,914
| 2,622,847,854
|
IssuesEvent
|
2015-03-04 08:03:33
|
max99x/pagemon-chrome-ext
|
https://api.github.com/repos/max99x/pagemon-chrome-ext
|
closed
|
Monitored Pages Do Not Show
|
auto-migrated Priority-Medium Type-Defect
|
```
What steps will reproduce the problem?
When I check specific pages, those will appear blank.
What is the expected output? What do you see instead?
I expect to see changes but I see a blank page.
What version of the Chrome are you using? On what operating system?
8.0.552.224
Please provide any additional information below.
Some pages appearing blank while others work fine and show changes.
```
Original issue reported on code.google.com by `junom...@gmail.com` on 21 Dec 2010 at 10:26
|
1.0
|
Monitored Pages Do Not Show - ```
What steps will reproduce the problem?
When I check specific pages, those will appear blank.
What is the expected output? What do you see instead?
I expect to see changes but I see a blank page.
What version of the Chrome are you using? On what operating system?
8.0.552.224
Please provide any additional information below.
Some pages appearing blank while others work fine and show changes.
```
Original issue reported on code.google.com by `junom...@gmail.com` on 21 Dec 2010 at 10:26
|
defect
|
monitored pages do not show what steps will reproduce the problem when i check specific pages those will appear blank what is the expected output what do you see instead i expect to see changes but i see a blank page what version of the chrome are you using on what operating system please provide any additional information below some pages appearing blank while others work fine and show changes original issue reported on code google com by junom gmail com on dec at
| 1
|
240,355
| 18,345,498,295
|
IssuesEvent
|
2021-10-08 05:26:03
|
GDSC-RCCIIT/General-Purpose-Scripts
|
https://api.github.com/repos/GDSC-RCCIIT/General-Purpose-Scripts
|
closed
|
Links in readme are broken.
|
bug documentation hacktoberfest
|
## Create a report to help us improve our scripts
### Mention the script affected by the bug
The main readme file of our repository.
### Describe the bug
A lot of the links in the available scripts section of our main readme file are either broken or are pointing to something entirely off-topic.
### Expected behavior
Ideally all the links should work and point to the directory of the target script.
## Do you want to work on this?
- [ ] yes
- [x] no
## Additional Context
You have to check all the links and fix the broken ones.
|
1.0
|
Links in readme are broken. - ## Create a report to help us improve our scripts
### Mention the script affected by the bug
The main readme file of our repository.
### Describe the bug
A lot of the links in the available scripts section of our main readme file are either broken or are pointing to something entirely off-topic.
### Expected behavior
Ideally all the links should work and point to the directory of the target script.
## Do you want to work on this?
- [ ] yes
- [x] no
## Additional Context
You have to check all the links and fix the broken ones.
|
non_defect
|
links in readme are broken create a report to help us improve our scripts mention the script affected by the bug the main readme file of our repository describe the bug a lot of the links in the available scripts section of our main readme file are either broken or are pointing to something entirely off topic expected behavior ideally all the links should work and point to the directory of the target script do you want to work on this yes no additional context you have to check all the links and fix the broken ones
| 0
|
70,958
| 23,390,475,572
|
IssuesEvent
|
2022-08-11 17:19:31
|
scipy/scipy
|
https://api.github.com/repos/scipy/scipy
|
opened
|
BUG: Sparse matrix multiplication output outright wrong
|
defect
|
### Describe your issue.
For same two matrices, matrix multiplication output generated by `numpy` and `scipy.sparse` does not match
### Reproducing Code Example
```python
import numpy as np
from scipy.sparse import csr_matrix, csc_matrix
DA = np.array([[0.82, 0.0, 0.0], [0.0, 0.84, 0.0], [0.0, 0.0, 0.0]])
DB = np.array([[0.0, 0.0, 0.41], [0.90, 0.0, 0.0], [0.0, 0.0, 0.0]])
print(np.matmul(DA, DB))
SA = csr_matrix(DA)
SB = csr_matrix(DB)
print(SA.multiply(SB).toarray())
```
### Error message
```shell
numpy output:
[[0. 0. 0.3362]
[0.756 0. 0. ]
[0. 0. 0. ]]
scipy output:
[[0. 0. 0.]
[0. 0. 0.]
[0. 0. 0.]]
```
### SciPy/NumPy/Python version information
1.8.1 1.22.3 sys.version_info(major=3, minor=8, micro=5, releaselevel='final', serial=0)
|
1.0
|
BUG: Sparse matrix multiplication output outright wrong - ### Describe your issue.
For same two matrices, matrix multiplication output generated by `numpy` and `scipy.sparse` does not match
### Reproducing Code Example
```python
import numpy as np
from scipy.sparse import csr_matrix, csc_matrix
DA = np.array([[0.82, 0.0, 0.0], [0.0, 0.84, 0.0], [0.0, 0.0, 0.0]])
DB = np.array([[0.0, 0.0, 0.41], [0.90, 0.0, 0.0], [0.0, 0.0, 0.0]])
print(np.matmul(DA, DB))
SA = csr_matrix(DA)
SB = csr_matrix(DB)
print(SA.multiply(SB).toarray())
```
### Error message
```shell
numpy output:
[[0. 0. 0.3362]
[0.756 0. 0. ]
[0. 0. 0. ]]
scipy output:
[[0. 0. 0.]
[0. 0. 0.]
[0. 0. 0.]]
```
### SciPy/NumPy/Python version information
1.8.1 1.22.3 sys.version_info(major=3, minor=8, micro=5, releaselevel='final', serial=0)
|
defect
|
bug sparse matrix multiplication output outright wrong describe your issue for same two matrices matrix multiplication output generated by numpy and scipy sparse does not match reproducing code example python import numpy as np from scipy sparse import csr matrix csc matrix da np array db np array print np matmul da db sa csr matrix da sb csr matrix db print sa multiply sb toarray error message shell numpy output scipy output scipy numpy python version information sys version info major minor micro releaselevel final serial
| 1
|
361,185
| 10,705,401,045
|
IssuesEvent
|
2019-10-24 13:39:16
|
mozilla/addons-server
|
https://api.github.com/repos/mozilla/addons-server
|
closed
|
Add `matched_rules` to `ScannerResult`
|
component: scanners priority: p3 state: pull request ready
|
In order to work on #12688, we need to associate `ScannerRule` and `ScannerResult` entries when we can. This issue is about doing this.
|
1.0
|
Add `matched_rules` to `ScannerResult` - In order to work on #12688, we need to associate `ScannerRule` and `ScannerResult` entries when we can. This issue is about doing this.
|
non_defect
|
add matched rules to scannerresult in order to work on we need to associate scannerrule and scannerresult entries when we can this issue is about doing this
| 0
|
51,758
| 13,211,302,006
|
IssuesEvent
|
2020-08-15 22:09:37
|
icecube-trac/tix4
|
https://api.github.com/repos/icecube-trac/tix4
|
opened
|
photospline - look at potential clang false positive (Trac #987)
|
Incomplete Migration Migrated from Trac combo core defect
|
<details>
<summary><em>Migrated from <a href="https://code.icecube.wisc.edu/projects/icecube/ticket/987">https://code.icecube.wisc.edu/projects/icecube/ticket/987</a>, reported by negaand owned by nega</em></summary>
<p>
```json
{
"status": "closed",
"changetime": "2016-03-18T21:14:09",
"_ts": "1458335649133028",
"description": "with clang-3.7\n{{{\n[ 12%] Building C object photospline/CMakeFiles/photospline.dir/private/lib/bspline_multi.c.o\nclang: warning: optimization flag '-fno-signaling-nans' is not supported\nclang: warning: optimization flag '-fno-signaling-nans' is not supported\n../../src/photospline/private/lib/bspline_multi.c:78:23: warning: variable 'sp' is uninitialized when used here [-Wuninitialized]\n if (__builtin_expect(sp & 15UL, 0))\n ^~\n../../src/photospline/private/lib/bspline_multi.c:77:36: note: initialize the variable 'sp' to silence this warning\n volatile register unsigned long sp __asm(\"esp\");\n ^\n = 0\n1 warning generated.\n}}}\n\nclang is possible getting confused by `__asm()`",
"reporter": "nega",
"cc": "jvansanten",
"resolution": "fixed",
"time": "2015-05-14T15:27:27",
"component": "combo core",
"summary": "photospline - look at potential clang false positive",
"priority": "trivial",
"keywords": "",
"milestone": "",
"owner": "nega",
"type": "defect"
}
```
</p>
</details>
|
1.0
|
photospline - look at potential clang false positive (Trac #987) - <details>
<summary><em>Migrated from <a href="https://code.icecube.wisc.edu/projects/icecube/ticket/987">https://code.icecube.wisc.edu/projects/icecube/ticket/987</a>, reported by negaand owned by nega</em></summary>
<p>
```json
{
"status": "closed",
"changetime": "2016-03-18T21:14:09",
"_ts": "1458335649133028",
"description": "with clang-3.7\n{{{\n[ 12%] Building C object photospline/CMakeFiles/photospline.dir/private/lib/bspline_multi.c.o\nclang: warning: optimization flag '-fno-signaling-nans' is not supported\nclang: warning: optimization flag '-fno-signaling-nans' is not supported\n../../src/photospline/private/lib/bspline_multi.c:78:23: warning: variable 'sp' is uninitialized when used here [-Wuninitialized]\n if (__builtin_expect(sp & 15UL, 0))\n ^~\n../../src/photospline/private/lib/bspline_multi.c:77:36: note: initialize the variable 'sp' to silence this warning\n volatile register unsigned long sp __asm(\"esp\");\n ^\n = 0\n1 warning generated.\n}}}\n\nclang is possible getting confused by `__asm()`",
"reporter": "nega",
"cc": "jvansanten",
"resolution": "fixed",
"time": "2015-05-14T15:27:27",
"component": "combo core",
"summary": "photospline - look at potential clang false positive",
"priority": "trivial",
"keywords": "",
"milestone": "",
"owner": "nega",
"type": "defect"
}
```
</p>
</details>
|
defect
|
photospline look at potential clang false positive trac migrated from json status closed changetime ts description with clang n n building c object photospline cmakefiles photospline dir private lib bspline multi c o nclang warning optimization flag fno signaling nans is not supported nclang warning optimization flag fno signaling nans is not supported n src photospline private lib bspline multi c warning variable sp is uninitialized when used here n if builtin expect sp n n src photospline private lib bspline multi c note initialize the variable sp to silence this warning n volatile register unsigned long sp asm esp n n warning generated n n nclang is possible getting confused by asm reporter nega cc jvansanten resolution fixed time component combo core summary photospline look at potential clang false positive priority trivial keywords milestone owner nega type defect
| 1
|
74,013
| 24,904,012,233
|
IssuesEvent
|
2022-10-29 02:53:06
|
openzfs/zfs
|
https://api.github.com/repos/openzfs/zfs
|
closed
|
`zpool events` does not list DEGRADED state change for pool
|
Type: Defect Status: Stale
|
### System information
<!-- add version after "|" character -->
Type | Version/Name
--- | ---
Distribution Name | NixOS
Distribution Version | 21.05
Kernel Version | 5.10.70
Architecture | x86_64
OpenZFS Version | 2.0.6-1
### Describe the problem you're observing
When a pool goes into DEGRADED due to a missing drive, the corresponding statechange event is not generated.
### Describe how to reproduce the problem
My pool looks like this:
```
pool: zroot
state: ONLINE
scan: resilvered 5.49M in 00:00:01 with 0 errors on Sun Oct 10 10:43:34 2021
config:
NAME STATE READ WRITE CKSUM
zroot ONLINE 0 0 0
raidz1-0 ONLINE 0 0 0
ata-ST10000NM0568-2H5110_ZHZ54D5K-part3 ONLINE 0 0 0
ata-ST10000NM0568-2H5110_ZHZ54D1C-part3 ONLINE 0 0 0
ata-ST10000NM0568-2H5110_ZHZ54DBW-part1 ONLINE 0 0 0
ata-ST10000NM0568-2H5110_ZHZ54D2A-part1 ONLINE 0 0 0
errors: No known data errors
```
I wanted to verify that ZED sends emails correctly when the pool is degraded. To do that, I kill one of the drives like so:
```
sudo sh -c 'echo 0 > /sys/block/sdc/device/delete'
```
And the status changes to degraded as expected:
```
pool: zroot
state: DEGRADED
status: One or more devices could not be used because the label is missing or
invalid. Sufficient replicas exist for the pool to continue
functioning in a degraded state.
action: Replace the device using 'zpool replace'.
see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-4J
scan: resilvered 15.0M in 00:00:01 with 0 errors on Sun Oct 10 10:15:55 2021
config:
NAME STATE READ WRITE CKSUM
zroot DEGRADED 0 0 0
raidz1-0 DEGRADED 0 0 0
ata-ST10000NM0568-2H5110_ZHZ54D5K-part3 ONLINE 0 0 0
ata-ST10000NM0568-2H5110_ZHZ54D1C-part3 ONLINE 0 0 0
ata-ST10000NM0568-2H5110_ZHZ54DBW-part1 UNAVAIL 3 69 0
ata-ST10000NM0568-2H5110_ZHZ54D2A-part1 ONLINE 0 0 0
errors: No known data errors
```
However, `zpool events -v` does _not_ include a statechange event to DEGRADED for the pool. It _does_ include an UNAVAIL statechange event for the drive itself. However, the default zedlet `statechange-notify.sh` only catches `'DEGRADED', 'FAULTED' or 'REMOVED'`.
There is an argument to be made that `statechange-notify.sh` should also catch `UNAVAIL`, but I still think that the statechange event for the pool going to DEGRADED should be generated.
Here is the list of relevant events:
```
Oct 10 2021 10:39:51.709234009 ereport.fs.zfs.io
class = "ereport.fs.zfs.io"
ena = 0x150e03af8dd01001
detector = (embedded nvlist)
version = 0x0
scheme = "zfs"
pool = 0xe244c57cc81be54b
vdev = 0x7e580703404ed3ff
(end detector)
pool = "zroot"
pool_guid = 0xe244c57cc81be54b
pool_state = 0x0
pool_context = 0x0
pool_failmode = "wait"
vdev_guid = 0x7e580703404ed3ff
vdev_type = "disk"
vdev_path = "/dev/disk/by-id/ata-ST10000NM0568-2H5110_ZHZ54DBW-part1"
vdev_ashift = 0x9
vdev_complete_ts = 0x150e03b1fe3
vdev_delta_ts = 0x3cdb
vdev_read_errors = 0x0
vdev_write_errors = 0x0
vdev_cksum_errors = 0x0
vdev_delays = 0x0
parent_guid = 0x581f35675e2a34d0
parent_type = "raidz"
vdev_spare_paths =
vdev_spare_guids =
zio_err = 0x5
zio_flags = 0xb08c1
zio_stage = 0x1000000
zio_pipeline = 0x1080000
zio_delay = 0x60b2
zio_timestamp = 0x150e03a5d84
zio_delta = 0x74d2
zio_priority = 0x0
zio_offset = 0x42000
zio_size = 0x2000
time = 0x6162c2f7 0x2a460d59
eid = 0x10
Oct 10 2021 10:39:51.709234009 ereport.fs.zfs.io
class = "ereport.fs.zfs.io"
ena = 0x150e03c1a6d01001
detector = (embedded nvlist)
version = 0x0
scheme = "zfs"
pool = 0xe244c57cc81be54b
vdev = 0x7e580703404ed3ff
(end detector)
pool = "zroot"
pool_guid = 0xe244c57cc81be54b
pool_state = 0x0
pool_context = 0x0
pool_failmode = "wait"
vdev_guid = 0x7e580703404ed3ff
vdev_type = "disk"
vdev_path = "/dev/disk/by-id/ata-ST10000NM0568-2H5110_ZHZ54DBW-part1"
vdev_ashift = 0x9
vdev_complete_ts = 0x150e03c03c6
vdev_delta_ts = 0x13cdc
vdev_read_errors = 0x1
vdev_write_errors = 0x0
vdev_cksum_errors = 0x0
vdev_delays = 0x0
parent_guid = 0x581f35675e2a34d0
parent_type = "raidz"
vdev_spare_paths =
vdev_spare_guids =
zio_err = 0x5
zio_flags = 0xb08c1
zio_stage = 0x1000000
zio_pipeline = 0x1080000
zio_delay = 0x130b9
zio_timestamp = 0x150e03ac6ea
zio_delta = 0x13c83
zio_priority = 0x0
zio_offset = 0x91808b82000
zio_size = 0x2000
time = 0x6162c2f7 0x2a460d59
eid = 0x11
Oct 10 2021 10:39:51.709234009 ereport.fs.zfs.io
class = "ereport.fs.zfs.io"
ena = 0x150e03d5c5d01001
detector = (embedded nvlist)
version = 0x0
scheme = "zfs"
pool = 0xe244c57cc81be54b
vdev = 0x7e580703404ed3ff
(end detector)
pool = "zroot"
pool_guid = 0xe244c57cc81be54b
pool_state = 0x0
pool_context = 0x0
pool_failmode = "wait"
vdev_guid = 0x7e580703404ed3ff
vdev_type = "disk"
vdev_path = "/dev/disk/by-id/ata-ST10000NM0568-2H5110_ZHZ54DBW-part1"
vdev_ashift = 0x9
vdev_complete_ts = 0x150e03d4b23
vdev_delta_ts = 0x25387
vdev_read_errors = 0x2
vdev_write_errors = 0x0
vdev_cksum_errors = 0x0
vdev_delays = 0x0
parent_guid = 0x581f35675e2a34d0
parent_type = "raidz"
vdev_spare_paths =
vdev_spare_guids =
zio_err = 0x5
zio_flags = 0xb08c1
zio_stage = 0x1000000
zio_pipeline = 0x1080000
zio_delay = 0x24b23
zio_timestamp = 0x150e03af79c
zio_delta = 0x25331
zio_priority = 0x0
zio_offset = 0x91808bc2000
zio_size = 0x2000
time = 0x6162c2f7 0x2a460d59
eid = 0x12
Oct 10 2021 10:39:51.709234009 ereport.fs.zfs.probe_failure
class = "ereport.fs.zfs.probe_failure"
ena = 0x150e03e351d01001
detector = (embedded nvlist)
version = 0x0
scheme = "zfs"
pool = 0xe244c57cc81be54b
vdev = 0x7e580703404ed3ff
(end detector)
pool = "zroot"
pool_guid = 0xe244c57cc81be54b
pool_state = 0x0
pool_context = 0x0
pool_failmode = "wait"
vdev_guid = 0x7e580703404ed3ff
vdev_type = "disk"
vdev_path = "/dev/disk/by-id/ata-ST10000NM0568-2H5110_ZHZ54DBW-part1"
vdev_ashift = 0x9
vdev_complete_ts = 0x150e03d4b23
vdev_delta_ts = 0x25387
vdev_read_errors = 0x3
vdev_write_errors = 0x0
vdev_cksum_errors = 0x0
vdev_delays = 0x0
parent_guid = 0x581f35675e2a34d0
parent_type = "raidz"
vdev_spare_paths =
vdev_spare_guids =
prev_state = 0x0
time = 0x6162c2f7 0x2a460d59
eid = 0x13
Oct 10 2021 10:39:52.820242319 ereport.fs.zfs.vdev.unknown
class = "ereport.fs.zfs.vdev.unknown"
ena = 0x1512276b31e00001
detector = (embedded nvlist)
version = 0x0
scheme = "zfs"
pool = 0xe244c57cc81be54b
vdev = 0x7e580703404ed3ff
(end detector)
pool = "zroot"
pool_guid = 0xe244c57cc81be54b
pool_state = 0x0
pool_context = 0x0
pool_failmode = "wait"
vdev_guid = 0x7e580703404ed3ff
vdev_type = "disk"
vdev_path = "/dev/disk/by-id/ata-ST10000NM0568-2H5110_ZHZ54DBW-part1"
vdev_ashift = 0x9
vdev_complete_ts = 0x150e09f79f7
vdev_delta_ts = 0x3ee8
vdev_read_errors = 0x3
vdev_write_errors = 0x45
vdev_cksum_errors = 0x0
vdev_delays = 0x0
parent_guid = 0x581f35675e2a34d0
parent_type = "raidz"
vdev_spare_paths =
vdev_spare_guids =
prev_state = 0x1
time = 0x6162c2f8 0x30e3e78f
eid = 0x14
Oct 10 2021 10:39:52.820242319 resource.fs.zfs.statechange
version = 0x0
class = "resource.fs.zfs.statechange"
pool = "zroot"
pool_guid = 0xe244c57cc81be54b
pool_state = 0x0
pool_context = 0x0
vdev_guid = 0x7e580703404ed3ff
vdev_state = "UNAVAIL" (0x4)
vdev_path = "/dev/disk/by-id/ata-ST10000NM0568-2H5110_ZHZ54DBW-part1"
vdev_laststate = "ONLINE" (0x7)
time = 0x6162c2f8 0x30e3e78f
eid = 0x15
```
|
1.0
|
`zpool events` does not list DEGRADED state change for pool - ### System information
<!-- add version after "|" character -->
Type | Version/Name
--- | ---
Distribution Name | NixOS
Distribution Version | 21.05
Kernel Version | 5.10.70
Architecture | x86_64
OpenZFS Version | 2.0.6-1
### Describe the problem you're observing
When a pool goes into DEGRADED due to a missing drive, the corresponding statechange event is not generated.
### Describe how to reproduce the problem
My pool looks like this:
```
pool: zroot
state: ONLINE
scan: resilvered 5.49M in 00:00:01 with 0 errors on Sun Oct 10 10:43:34 2021
config:
NAME STATE READ WRITE CKSUM
zroot ONLINE 0 0 0
raidz1-0 ONLINE 0 0 0
ata-ST10000NM0568-2H5110_ZHZ54D5K-part3 ONLINE 0 0 0
ata-ST10000NM0568-2H5110_ZHZ54D1C-part3 ONLINE 0 0 0
ata-ST10000NM0568-2H5110_ZHZ54DBW-part1 ONLINE 0 0 0
ata-ST10000NM0568-2H5110_ZHZ54D2A-part1 ONLINE 0 0 0
errors: No known data errors
```
I wanted to verify that ZED sends emails correctly when the pool is degraded. To do that, I kill one of the drives like so:
```
sudo sh -c 'echo 0 > /sys/block/sdc/device/delete'
```
And the status changes to degraded as expected:
```
pool: zroot
state: DEGRADED
status: One or more devices could not be used because the label is missing or
invalid. Sufficient replicas exist for the pool to continue
functioning in a degraded state.
action: Replace the device using 'zpool replace'.
see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-4J
scan: resilvered 15.0M in 00:00:01 with 0 errors on Sun Oct 10 10:15:55 2021
config:
NAME STATE READ WRITE CKSUM
zroot DEGRADED 0 0 0
raidz1-0 DEGRADED 0 0 0
ata-ST10000NM0568-2H5110_ZHZ54D5K-part3 ONLINE 0 0 0
ata-ST10000NM0568-2H5110_ZHZ54D1C-part3 ONLINE 0 0 0
ata-ST10000NM0568-2H5110_ZHZ54DBW-part1 UNAVAIL 3 69 0
ata-ST10000NM0568-2H5110_ZHZ54D2A-part1 ONLINE 0 0 0
errors: No known data errors
```
However, `zpool events -v` does _not_ include a statechange event to DEGRADED for the pool. It _does_ include an UNAVAIL statechange event for the drive itself. However, the default zedlet `statechange-notify.sh` only catches `'DEGRADED', 'FAULTED' or 'REMOVED'`.
There is an argument to be made that `statechange-notify.sh` should also catch `UNAVAIL`, but I still think that the statechange event for the pool going to DEGRADED should be generated.
Here is the list of relevant events:
```
Oct 10 2021 10:39:51.709234009 ereport.fs.zfs.io
class = "ereport.fs.zfs.io"
ena = 0x150e03af8dd01001
detector = (embedded nvlist)
version = 0x0
scheme = "zfs"
pool = 0xe244c57cc81be54b
vdev = 0x7e580703404ed3ff
(end detector)
pool = "zroot"
pool_guid = 0xe244c57cc81be54b
pool_state = 0x0
pool_context = 0x0
pool_failmode = "wait"
vdev_guid = 0x7e580703404ed3ff
vdev_type = "disk"
vdev_path = "/dev/disk/by-id/ata-ST10000NM0568-2H5110_ZHZ54DBW-part1"
vdev_ashift = 0x9
vdev_complete_ts = 0x150e03b1fe3
vdev_delta_ts = 0x3cdb
vdev_read_errors = 0x0
vdev_write_errors = 0x0
vdev_cksum_errors = 0x0
vdev_delays = 0x0
parent_guid = 0x581f35675e2a34d0
parent_type = "raidz"
vdev_spare_paths =
vdev_spare_guids =
zio_err = 0x5
zio_flags = 0xb08c1
zio_stage = 0x1000000
zio_pipeline = 0x1080000
zio_delay = 0x60b2
zio_timestamp = 0x150e03a5d84
zio_delta = 0x74d2
zio_priority = 0x0
zio_offset = 0x42000
zio_size = 0x2000
time = 0x6162c2f7 0x2a460d59
eid = 0x10
Oct 10 2021 10:39:51.709234009 ereport.fs.zfs.io
class = "ereport.fs.zfs.io"
ena = 0x150e03c1a6d01001
detector = (embedded nvlist)
version = 0x0
scheme = "zfs"
pool = 0xe244c57cc81be54b
vdev = 0x7e580703404ed3ff
(end detector)
pool = "zroot"
pool_guid = 0xe244c57cc81be54b
pool_state = 0x0
pool_context = 0x0
pool_failmode = "wait"
vdev_guid = 0x7e580703404ed3ff
vdev_type = "disk"
vdev_path = "/dev/disk/by-id/ata-ST10000NM0568-2H5110_ZHZ54DBW-part1"
vdev_ashift = 0x9
vdev_complete_ts = 0x150e03c03c6
vdev_delta_ts = 0x13cdc
vdev_read_errors = 0x1
vdev_write_errors = 0x0
vdev_cksum_errors = 0x0
vdev_delays = 0x0
parent_guid = 0x581f35675e2a34d0
parent_type = "raidz"
vdev_spare_paths =
vdev_spare_guids =
zio_err = 0x5
zio_flags = 0xb08c1
zio_stage = 0x1000000
zio_pipeline = 0x1080000
zio_delay = 0x130b9
zio_timestamp = 0x150e03ac6ea
zio_delta = 0x13c83
zio_priority = 0x0
zio_offset = 0x91808b82000
zio_size = 0x2000
time = 0x6162c2f7 0x2a460d59
eid = 0x11
Oct 10 2021 10:39:51.709234009 ereport.fs.zfs.io
class = "ereport.fs.zfs.io"
ena = 0x150e03d5c5d01001
detector = (embedded nvlist)
version = 0x0
scheme = "zfs"
pool = 0xe244c57cc81be54b
vdev = 0x7e580703404ed3ff
(end detector)
pool = "zroot"
pool_guid = 0xe244c57cc81be54b
pool_state = 0x0
pool_context = 0x0
pool_failmode = "wait"
vdev_guid = 0x7e580703404ed3ff
vdev_type = "disk"
vdev_path = "/dev/disk/by-id/ata-ST10000NM0568-2H5110_ZHZ54DBW-part1"
vdev_ashift = 0x9
vdev_complete_ts = 0x150e03d4b23
vdev_delta_ts = 0x25387
vdev_read_errors = 0x2
vdev_write_errors = 0x0
vdev_cksum_errors = 0x0
vdev_delays = 0x0
parent_guid = 0x581f35675e2a34d0
parent_type = "raidz"
vdev_spare_paths =
vdev_spare_guids =
zio_err = 0x5
zio_flags = 0xb08c1
zio_stage = 0x1000000
zio_pipeline = 0x1080000
zio_delay = 0x24b23
zio_timestamp = 0x150e03af79c
zio_delta = 0x25331
zio_priority = 0x0
zio_offset = 0x91808bc2000
zio_size = 0x2000
time = 0x6162c2f7 0x2a460d59
eid = 0x12
Oct 10 2021 10:39:51.709234009 ereport.fs.zfs.probe_failure
class = "ereport.fs.zfs.probe_failure"
ena = 0x150e03e351d01001
detector = (embedded nvlist)
version = 0x0
scheme = "zfs"
pool = 0xe244c57cc81be54b
vdev = 0x7e580703404ed3ff
(end detector)
pool = "zroot"
pool_guid = 0xe244c57cc81be54b
pool_state = 0x0
pool_context = 0x0
pool_failmode = "wait"
vdev_guid = 0x7e580703404ed3ff
vdev_type = "disk"
vdev_path = "/dev/disk/by-id/ata-ST10000NM0568-2H5110_ZHZ54DBW-part1"
vdev_ashift = 0x9
vdev_complete_ts = 0x150e03d4b23
vdev_delta_ts = 0x25387
vdev_read_errors = 0x3
vdev_write_errors = 0x0
vdev_cksum_errors = 0x0
vdev_delays = 0x0
parent_guid = 0x581f35675e2a34d0
parent_type = "raidz"
vdev_spare_paths =
vdev_spare_guids =
prev_state = 0x0
time = 0x6162c2f7 0x2a460d59
eid = 0x13
Oct 10 2021 10:39:52.820242319 ereport.fs.zfs.vdev.unknown
class = "ereport.fs.zfs.vdev.unknown"
ena = 0x1512276b31e00001
detector = (embedded nvlist)
version = 0x0
scheme = "zfs"
pool = 0xe244c57cc81be54b
vdev = 0x7e580703404ed3ff
(end detector)
pool = "zroot"
pool_guid = 0xe244c57cc81be54b
pool_state = 0x0
pool_context = 0x0
pool_failmode = "wait"
vdev_guid = 0x7e580703404ed3ff
vdev_type = "disk"
vdev_path = "/dev/disk/by-id/ata-ST10000NM0568-2H5110_ZHZ54DBW-part1"
vdev_ashift = 0x9
vdev_complete_ts = 0x150e09f79f7
vdev_delta_ts = 0x3ee8
vdev_read_errors = 0x3
vdev_write_errors = 0x45
vdev_cksum_errors = 0x0
vdev_delays = 0x0
parent_guid = 0x581f35675e2a34d0
parent_type = "raidz"
vdev_spare_paths =
vdev_spare_guids =
prev_state = 0x1
time = 0x6162c2f8 0x30e3e78f
eid = 0x14
Oct 10 2021 10:39:52.820242319 resource.fs.zfs.statechange
version = 0x0
class = "resource.fs.zfs.statechange"
pool = "zroot"
pool_guid = 0xe244c57cc81be54b
pool_state = 0x0
pool_context = 0x0
vdev_guid = 0x7e580703404ed3ff
vdev_state = "UNAVAIL" (0x4)
vdev_path = "/dev/disk/by-id/ata-ST10000NM0568-2H5110_ZHZ54DBW-part1"
vdev_laststate = "ONLINE" (0x7)
time = 0x6162c2f8 0x30e3e78f
eid = 0x15
```
|
defect
|
zpool events does not list degraded state change for pool system information type version name distribution name nixos distribution version kernel version architecture openzfs version describe the problem you re observing when a pool goes into degraded due to a missing drive the corresponding statechange event is not generated describe how to reproduce the problem my pool looks like this pool zroot state online scan resilvered in with errors on sun oct config name state read write cksum zroot online online ata online ata online ata online ata online errors no known data errors i wanted to verify that zed sends emails correctly when the pool is degraded to do that i kill one of the drives like so sudo sh c echo sys block sdc device delete and the status changes to degraded as expected pool zroot state degraded status one or more devices could not be used because the label is missing or invalid sufficient replicas exist for the pool to continue functioning in a degraded state action replace the device using zpool replace see scan resilvered in with errors on sun oct config name state read write cksum zroot degraded degraded ata online ata online ata unavail ata online errors no known data errors however zpool events v does not include a statechange event to degraded for the pool it does include an unavail statechange event for the drive itself however the default zedlet statechange notify sh only catches degraded faulted or removed there is an argument to be made that statechange notify sh should also catch unavail but i still think that the statechange event for the pool going to degraded should be generated here is the list of relevant events oct ereport fs zfs io class ereport fs zfs io ena detector embedded nvlist version scheme zfs pool vdev end detector pool zroot pool guid pool state pool context pool failmode wait vdev guid vdev type disk vdev path dev disk by id ata vdev ashift vdev complete ts vdev delta ts vdev read errors vdev write errors vdev cksum errors vdev delays parent guid parent type raidz vdev spare paths vdev spare guids zio err zio flags zio stage zio pipeline zio delay zio timestamp zio delta zio priority zio offset zio size time eid oct ereport fs zfs io class ereport fs zfs io ena detector embedded nvlist version scheme zfs pool vdev end detector pool zroot pool guid pool state pool context pool failmode wait vdev guid vdev type disk vdev path dev disk by id ata vdev ashift vdev complete ts vdev delta ts vdev read errors vdev write errors vdev cksum errors vdev delays parent guid parent type raidz vdev spare paths vdev spare guids zio err zio flags zio stage zio pipeline zio delay zio timestamp zio delta zio priority zio offset zio size time eid oct ereport fs zfs io class ereport fs zfs io ena detector embedded nvlist version scheme zfs pool vdev end detector pool zroot pool guid pool state pool context pool failmode wait vdev guid vdev type disk vdev path dev disk by id ata vdev ashift vdev complete ts vdev delta ts vdev read errors vdev write errors vdev cksum errors vdev delays parent guid parent type raidz vdev spare paths vdev spare guids zio err zio flags zio stage zio pipeline zio delay zio timestamp zio delta zio priority zio offset zio size time eid oct ereport fs zfs probe failure class ereport fs zfs probe failure ena detector embedded nvlist version scheme zfs pool vdev end detector pool zroot pool guid pool state pool context pool failmode wait vdev guid vdev type disk vdev path dev disk by id ata vdev ashift vdev complete ts vdev delta ts vdev read errors vdev write errors vdev cksum errors vdev delays parent guid parent type raidz vdev spare paths vdev spare guids prev state time eid oct ereport fs zfs vdev unknown class ereport fs zfs vdev unknown ena detector embedded nvlist version scheme zfs pool vdev end detector pool zroot pool guid pool state pool context pool failmode wait vdev guid vdev type disk vdev path dev disk by id ata vdev ashift vdev complete ts vdev delta ts vdev read errors vdev write errors vdev cksum errors vdev delays parent guid parent type raidz vdev spare paths vdev spare guids prev state time eid oct resource fs zfs statechange version class resource fs zfs statechange pool zroot pool guid pool state pool context vdev guid vdev state unavail vdev path dev disk by id ata vdev laststate online time eid
| 1
|
31,897
| 6,657,859,662
|
IssuesEvent
|
2017-09-30 11:43:40
|
primefaces/primefaces
|
https://api.github.com/repos/primefaces/primefaces
|
closed
|
Wrong selection in Mobile DataList with facet header
|
defect mobile
|
when i tap on the row of my dataList (in mobile environment), the wrong Object value is passed to the ajax listener (it's the next value in the dataList).
It happens only if i put a <f:facet name=header> in the list.
Using PF 5.0.1
``` xml
<p:dataList id="list" var="seg" value="#{segnBean.segnalazioni}"
emptyMessage="#{l.emptyTable}" pt:data-inset="true">
<f:facet name="header">
#{l.elencoSegnalazioni}
</f:facet>
<p:ajax event="tap" listener="#{segnBean.selectSegnalazione}" oncomplete="PrimeFaces.Mobile.navigate('#second', {reverse: true|false,transition: 'flip'});" />
<h:outputLink value="#">
<h2>#{seg.segId}
</h:outputLink>
</p:dataList>
----------------------------
public void selectSegnalazione(SelectEvent event) {
Segnalazioni seg = (Segnalazioni) event.getObject();
System.out.println(seg.getSegId());
...
}
```
|
1.0
|
Wrong selection in Mobile DataList with facet header - when i tap on the row of my dataList (in mobile environment), the wrong Object value is passed to the ajax listener (it's the next value in the dataList).
It happens only if i put a <f:facet name=header> in the list.
Using PF 5.0.1
``` xml
<p:dataList id="list" var="seg" value="#{segnBean.segnalazioni}"
emptyMessage="#{l.emptyTable}" pt:data-inset="true">
<f:facet name="header">
#{l.elencoSegnalazioni}
</f:facet>
<p:ajax event="tap" listener="#{segnBean.selectSegnalazione}" oncomplete="PrimeFaces.Mobile.navigate('#second', {reverse: true|false,transition: 'flip'});" />
<h:outputLink value="#">
<h2>#{seg.segId}
</h:outputLink>
</p:dataList>
----------------------------
public void selectSegnalazione(SelectEvent event) {
Segnalazioni seg = (Segnalazioni) event.getObject();
System.out.println(seg.getSegId());
...
}
```
|
defect
|
wrong selection in mobile datalist with facet header when i tap on the row of my datalist in mobile environment the wrong object value is passed to the ajax listener it s the next value in the datalist it happens only if i put a in the list using pf xml p datalist id list var seg value segnbean segnalazioni emptymessage l emptytable pt data inset true l elencosegnalazioni seg segid public void selectsegnalazione selectevent event segnalazioni seg segnalazioni event getobject system out println seg getsegid
| 1
|
78,007
| 27,275,075,368
|
IssuesEvent
|
2023-02-23 03:55:56
|
apache/jmeter
|
https://api.github.com/repos/apache/jmeter
|
opened
|
Is this a bug?
|
defect to-triage
|
### Expected behavior
Run jmeter in the background to output the correct result
### Actual behavior



jmeter.log
`2023-02-23 11:16:03,974 INFO o.a.j.u.JMeterUtils: Setting Locale to en_EN
2023-02-23 11:16:03,994 INFO o.a.j.JMeter: Loading user properties from: /opt/apache-jmeter-5.5/bin/user.properties
2023-02-23 11:16:03,994 INFO o.a.j.JMeter: Loading system properties from: /opt/apache-jmeter-5.5/bin/system.properties
2023-02-23 11:16:04,000 INFO o.a.j.JMeter: Copyright (c) 1998-2022 The Apache Software Foundation
2023-02-23 11:16:04,000 INFO o.a.j.JMeter: Version 5.5
2023-02-23 11:16:04,000 INFO o.a.j.JMeter: java.version=17.0.4.1
2023-02-23 11:16:04,000 INFO o.a.j.JMeter: java.vm.name=OpenJDK 64-Bit Server VM
2023-02-23 11:16:04,000 INFO o.a.j.JMeter: os.name=Linux
2023-02-23 11:16:04,000 INFO o.a.j.JMeter: os.arch=amd64
2023-02-23 11:16:04,000 INFO o.a.j.JMeter: os.version=5.10.0-10-amd64
2023-02-23 11:16:04,000 INFO o.a.j.JMeter: file.encoding=UTF-8
2023-02-23 11:16:04,000 INFO o.a.j.JMeter: java.awt.headless=true
2023-02-23 11:16:04,000 INFO o.a.j.JMeter: Max memory =1073741824
2023-02-23 11:16:04,000 INFO o.a.j.JMeter: Available Processors =48
2023-02-23 11:16:04,010 INFO o.a.j.JMeter: Default Locale=English (EN)
2023-02-23 11:16:04,010 INFO o.a.j.JMeter: JMeter Locale=English (EN)
2023-02-23 11:16:04,010 INFO o.a.j.JMeter: JMeterHome=/opt/apache-jmeter-5.5
2023-02-23 11:16:04,010 INFO o.a.j.JMeter: user.dir =/root/.jenkins/workspace/csm
2023-02-23 11:16:04,010 INFO o.a.j.JMeter: PWD =/root/.jenkins/workspace/csm
2023-02-23 11:16:04,011 INFO o.a.j.JMeter: IP: 127.0.1.1 Name: performance FullName: performance
2023-02-23 11:16:04,019 INFO o.a.j.s.FileServer: Default base='/root/.jenkins/workspace/csm'
2023-02-23 11:16:04,020 INFO o.a.j.s.FileServer: Set new base='/root/.jenkins/workspace/csm/csm'
2023-02-23 11:16:04,161 INFO o.a.j.s.SaveService: Testplan (JMX) version: 2.2. Testlog (JTL) version: 2.2
2023-02-23 11:16:04,184 INFO o.a.j.s.SaveService: Using SaveService properties version 5.0
2023-02-23 11:16:04,187 INFO o.a.j.s.SaveService: Using SaveService properties file encoding UTF-8
2023-02-23 11:16:04,190 INFO o.a.j.s.SaveService: Loading file: csm/sm3.jmx
2023-02-23 11:16:04,249 INFO o.a.j.p.h.s.HTTPSamplerBase: Parser for text/html is org.apache.jmeter.protocol.http.parser.LagartoBasedHtmlParser
2023-02-23 11:16:04,249 INFO o.a.j.p.h.s.HTTPSamplerBase: Parser for application/xhtml+xml is org.apache.jmeter.protocol.http.parser.LagartoBasedHtmlParser
2023-02-23 11:16:04,249 INFO o.a.j.p.h.s.HTTPSamplerBase: Parser for application/xml is org.apache.jmeter.protocol.http.parser.LagartoBasedHtmlParser
2023-02-23 11:16:04,249 INFO o.a.j.p.h.s.HTTPSamplerBase: Parser for text/xml is org.apache.jmeter.protocol.http.parser.LagartoBasedHtmlParser
2023-02-23 11:16:04,250 INFO o.a.j.p.h.s.HTTPSamplerBase: Parser for text/vnd.wap.wml is org.apache.jmeter.protocol.http.parser.RegexpHTMLParser
2023-02-23 11:16:04,250 INFO o.a.j.p.h.s.HTTPSamplerBase: Parser for text/css is org.apache.jmeter.protocol.http.parser.CssParser
2023-02-23 11:16:04,273 INFO o.a.j.JMeter: Creating summariser <summary>
2023-02-23 11:16:04,284 INFO o.a.j.e.StandardJMeterEngine: Running the test!
2023-02-23 11:16:04,285 INFO o.a.j.s.SampleEvent: List of sample_variables: []
2023-02-23 11:16:04,286 INFO o.a.j.s.SampleEvent: List of sample_variables: []
2023-02-23 11:16:04,291 INFO o.a.j.e.u.CompoundVariable: Note: Function class names must contain the string: '.functions.'
2023-02-23 11:16:04,291 INFO o.a.j.e.u.CompoundVariable: Note: Function class names must not contain the string: '.gui.'
2023-02-23 11:16:04,344 INFO o.a.j.JMeter: Running test (1677122164344)
2023-02-23 11:16:04,366 INFO o.a.j.e.StandardJMeterEngine: Starting ThreadGroup: 1 : Thread Group
2023-02-23 11:16:04,366 INFO o.a.j.e.StandardJMeterEngine: Starting 100 threads for group Thread Group.
2023-02-23 11:16:04,367 INFO o.a.j.e.StandardJMeterEngine: Thread will continue on error
2023-02-23 11:16:04,367 INFO o.a.j.t.ThreadGroup: Starting thread group... number=1 threads=100 ramp-up=1 delayedStart=false
2023-02-23 11:16:04,374 INFO o.a.j.s.SampleResult: Note: Sample TimeStamps are START times
2023-02-23 11:16:04,375 INFO o.a.j.s.SampleResult: sampleresult.default.encoding is set to ISO-8859-1
2023-02-23 11:16:04,375 INFO o.a.j.s.SampleResult: sampleresult.useNanoTime=true
2023-02-23 11:16:04,375 INFO o.a.j.s.SampleResult: sampleresult.nanoThreadSleep=5000
2023-02-23 11:16:04,376 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-1
2023-02-23 11:16:04,382 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-2
2023-02-23 11:16:04,391 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-3
2023-02-23 11:16:04,395 INFO o.a.j.p.h.s.HTTPHCAbstractImpl: Local host = performance
2023-02-23 11:16:04,400 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-4
2023-02-23 11:16:04,402 INFO o.a.j.p.h.s.HTTPHC4Impl: HTTP request retry count = 0
2023-02-23 11:16:04,409 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-5
2023-02-23 11:16:04,419 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-6
2023-02-23 11:16:04,429 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-7
2023-02-23 11:16:04,432 INFO o.a.j.t.ThreadGroup: Started thread group number 1
2023-02-23 11:16:04,432 INFO o.a.j.e.StandardJMeterEngine: All thread groups have been started
2023-02-23 11:16:04,439 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-8
2023-02-23 11:16:04,448 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-9
2023-02-23 11:16:04,458 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-10
2023-02-23 11:16:04,468 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-11
2023-02-23 11:16:04,478 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-12
2023-02-23 11:16:04,488 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-13
2023-02-23 11:16:04,499 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-14
2023-02-23 11:16:04,508 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-15
2023-02-23 11:16:04,518 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-16
2023-02-23 11:16:04,528 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-17
2023-02-23 11:16:04,538 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-18
2023-02-23 11:16:04,548 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-19
2023-02-23 11:16:04,557 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-20
2023-02-23 11:16:04,568 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-21
2023-02-23 11:16:04,578 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-22
2023-02-23 11:16:04,588 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-23
2023-02-23 11:16:04,598 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-24
2023-02-23 11:16:04,607 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-25
2023-02-23 11:16:04,618 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-26
2023-02-23 11:16:04,628 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-27
2023-02-23 11:16:04,637 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-28
2023-02-23 11:16:04,648 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-29
2023-02-23 11:16:04,658 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-30
2023-02-23 11:16:04,678 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-31
2023-02-23 11:16:04,679 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-32
2023-02-23 11:16:04,688 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-33
2023-02-23 11:16:04,698 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-34
2023-02-23 11:16:04,709 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-35
2023-02-23 11:16:04,718 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-36
2023-02-23 11:16:04,728 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-37
2023-02-23 11:16:04,739 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-38
2023-02-23 11:16:04,748 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-39
2023-02-23 11:16:04,758 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-40
2023-02-23 11:16:04,768 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-41
2023-02-23 11:16:04,778 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-42
2023-02-23 11:16:04,788 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-43
2023-02-23 11:16:04,798 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-44
2023-02-23 11:16:04,808 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-45
2023-02-23 11:16:04,818 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-46
2023-02-23 11:16:04,829 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-47
2023-02-23 11:16:04,838 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-48
2023-02-23 11:16:04,848 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-49
2023-02-23 11:16:04,859 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-50
2023-02-23 11:16:04,868 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-51
2023-02-23 11:16:04,878 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-52
2023-02-23 11:16:04,888 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-53
2023-02-23 11:16:04,904 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-54
2023-02-23 11:16:04,908 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-55
2023-02-23 11:16:04,918 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-56
2023-02-23 11:16:04,928 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-57
2023-02-23 11:16:04,938 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-58
2023-02-23 11:16:04,949 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-59
2023-02-23 11:16:04,958 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-60
2023-02-23 11:16:04,968 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-61
2023-02-23 11:16:04,979 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-62
2023-02-23 11:16:04,988 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-63
2023-02-23 11:16:04,998 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-64
2023-02-23 11:16:05,008 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-65
2023-02-23 11:16:05,018 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-66
2023-02-23 11:16:05,028 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-67
2023-02-23 11:16:05,038 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-68
2023-02-23 11:16:05,048 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-69
2023-02-23 11:16:05,058 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-70
2023-02-23 11:16:05,068 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-71
2023-02-23 11:16:05,078 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-72
2023-02-23 11:16:05,088 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-73
2023-02-23 11:16:05,098 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-74
2023-02-23 11:16:05,108 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-75
2023-02-23 11:16:05,118 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-76
2023-02-23 11:16:05,128 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-77
2023-02-23 11:16:05,138 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-78
2023-02-23 11:16:05,148 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-79
2023-02-23 11:16:05,158 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-80
2023-02-23 11:16:05,169 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-81
2023-02-23 11:16:05,179 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-82
2023-02-23 11:16:05,188 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-83
2023-02-23 11:16:05,198 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-84
2023-02-23 11:16:05,212 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-85
2023-02-23 11:16:05,218 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-86
2023-02-23 11:16:05,228 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-87
2023-02-23 11:16:05,238 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-88
2023-02-23 11:16:05,248 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-89
2023-02-23 11:16:05,258 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-90
2023-02-23 11:16:05,268 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-91
2023-02-23 11:16:05,278 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-92
2023-02-23 11:16:05,288 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-93
2023-02-23 11:16:05,298 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-94
2023-02-23 11:16:05,308 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-95
2023-02-23 11:16:05,318 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-96
2023-02-23 11:16:05,328 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-97
2023-02-23 11:16:05,338 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-98
2023-02-23 11:16:05,348 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-99
2023-02-23 11:16:05,358 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-100
2023-02-23 11:17:04,372 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-2
2023-02-23 11:17:04,370 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-1
2023-02-23 11:17:04,374 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-5
2023-02-23 11:17:04,376 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-5
2023-02-23 11:17:04,376 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-1
2023-02-23 11:17:04,379 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-3
2023-02-23 11:17:04,379 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-3
2023-02-23 11:17:04,380 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-12
2023-02-23 11:17:04,380 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-6
2023-02-23 11:17:04,380 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-12
2023-02-23 11:17:04,380 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-6
2023-02-23 11:17:04,384 INFO o.a.j.r.Summariser: summary + 1 in 00:01:00 = 0.0/s Avg: 11 Min: 11 Max: 11 Err: 0 (0.00%) Active: 100 Started: 100 Finished: 0
2023-02-23 11:17:04,384 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-16
2023-02-23 11:17:04,384 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-7
2023-02-23 11:17:04,384 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-16
2023-02-23 11:17:04,385 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-7
2023-02-23 11:17:04,385 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-2
2023-02-23 11:17:04,386 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-20
2023-02-23 11:17:04,386 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-20
2023-02-23 11:17:04,387 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-13
2023-02-23 11:17:04,387 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-4
2023-02-23 11:17:04,387 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-13
2023-02-23 11:17:04,387 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-15
2023-02-23 11:17:04,387 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-24
2023-02-23 11:17:04,387 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-4
2023-02-23 11:17:04,387 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-24
2023-02-23 11:17:04,387 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-15
2023-02-23 11:17:04,387 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-22
2023-02-23 11:17:04,388 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-26
2023-02-23 11:17:04,388 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-9
2023-02-23 11:17:04,388 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-9
2023-02-23 11:17:04,388 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-26
2023-02-23 11:17:04,388 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-25
2023-02-23 11:17:04,388 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-17
2023-02-23 11:17:04,388 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-21
2023-02-23 11:17:04,388 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-17
2023-02-23 11:17:04,388 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-25
2023-02-23 11:17:04,388 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-22
2023-02-23 11:17:04,388 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-14
2023-02-23 11:17:04,388 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-21
2023-02-23 11:17:04,388 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-8
2023-02-23 11:17:04,389 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-14
2023-02-23 11:17:04,389 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-8
2023-02-23 11:17:04,390 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-10
2023-02-23 11:17:04,390 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-32
2023-02-23 11:17:04,390 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-10
2023-02-23 11:17:04,390 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-11
2023-02-23 11:17:04,390 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-32
2023-02-23 11:17:04,390 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-33
2023-02-23 11:17:04,390 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-11
2023-02-23 11:17:04,390 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-33
2023-02-23 11:17:04,392 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-27
2023-02-23 11:17:04,392 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-27
2023-02-23 11:17:04,394 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-36
2023-02-23 11:17:04,394 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-31
2023-02-23 11:17:04,394 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-28
2023-02-23 11:17:04,394 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-36
2023-02-23 11:17:04,394 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-31
2023-02-23 11:17:04,394 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-28
2023-02-23 11:17:04,395 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-19
2023-02-23 11:17:04,395 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-19
2023-02-23 11:17:04,396 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-23
2023-02-23 11:17:04,396 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-29
2023-02-23 11:17:04,396 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-23
2023-02-23 11:17:04,396 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-29
2023-02-23 11:17:04,397 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-34
2023-02-23 11:17:04,397 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-38
2023-02-23 11:17:04,397 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-34
2023-02-23 11:17:04,397 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-38
2023-02-23 11:17:04,398 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-44
2023-02-23 11:17:04,398 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-18
2023-02-23 11:17:04,398 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-42
2023-02-23 11:17:04,398 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-44
2023-02-23 11:17:04,398 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-18
2023-02-23 11:17:04,398 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-42
2023-02-23 11:17:04,399 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-41
2023-02-23 11:17:04,399 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-41
2023-02-23 11:17:04,400 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-37
2023-02-23 11:17:04,400 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-37
2023-02-23 11:17:04,400 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-40
2023-02-23 11:17:04,401 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-40
2023-02-23 11:17:04,401 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-45
2023-02-23 11:17:04,401 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-49
2023-02-23 11:17:04,401 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-45
2023-02-23 11:17:04,401 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-48
2023-02-23 11:17:04,401 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-49
2023-02-23 11:17:04,401 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-48
2023-02-23 11:17:04,402 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-35
2023-02-23 11:17:04,402 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-30
2023-02-23 11:17:04,402 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-46
2023-02-23 11:17:04,402 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-35
2023-02-23 11:17:04,402 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-30
2023-02-23 11:17:04,402 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-46
2023-02-23 11:17:04,402 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-51
2023-02-23 11:17:04,403 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-43
2023-02-23 11:17:04,403 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-39
2023-02-23 11:17:04,403 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-47
2023-02-23 11:17:04,403 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-51
2023-02-23 11:17:04,403 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-43
2023-02-23 11:17:04,403 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-39
2023-02-23 11:17:04,403 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-47
2023-02-23 11:17:04,405 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-56
2023-02-23 11:17:04,405 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-56
2023-02-23 11:17:04,407 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-53
2023-02-23 11:17:04,407 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-52
2023-02-23 11:17:04,407 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-53
2023-02-23 11:17:04,408 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-52
2023-02-23 11:17:04,408 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-60
2023-02-23 11:17:04,408 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-50
2023-02-23 11:17:04,408 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-58
2023-02-23 11:17:04,408 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-60
2023-02-23 11:17:04,408 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-50
2023-02-23 11:17:04,409 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-58
2023-02-23 11:17:04,409 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-59
2023-02-23 11:17:04,409 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-55
2023-02-23 11:17:04,409 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-59
2023-02-23 11:17:04,409 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-55
2023-02-23 11:17:04,409 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-61
2023-02-23 11:17:04,409 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-61
2023-02-23 11:17:04,410 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-54
2023-02-23 11:17:04,410 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-54
2023-02-23 11:17:04,411 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-57
2023-02-23 11:17:04,411 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-57
2023-02-23 11:17:04,412 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-65
2023-02-23 11:17:04,412 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-65
2023-02-23 11:17:04,414 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-64
2023-02-23 11:17:04,414 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-64
2023-02-23 11:17:04,414 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-68
2023-02-23 11:17:04,414 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-67
2023-02-23 11:17:04,414 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-68
2023-02-23 11:17:04,415 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-66
2023-02-23 11:17:04,415 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-67
2023-02-23 11:17:04,415 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-62
2023-02-23 11:17:04,415 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-66
2023-02-23 11:17:04,415 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-62
2023-02-23 11:17:04,415 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-63
2023-02-23 11:17:04,416 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-63
2023-02-23 11:17:04,416 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-70
2023-02-23 11:17:04,416 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-70
2023-02-23 11:17:04,416 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-69
2023-02-23 11:17:04,416 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-69
2023-02-23 11:17:04,417 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-72
2023-02-23 11:17:04,418 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-72
2023-02-23 11:17:04,418 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-73
2023-02-23 11:17:04,418 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-73
2023-02-23 11:17:04,418 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-74
2023-02-23 11:17:04,419 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-74
2023-02-23 11:17:04,419 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-75
2023-02-23 11:17:04,419 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-75
2023-02-23 11:17:04,419 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-77
2023-02-23 11:17:04,420 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-77
2023-02-23 11:17:04,421 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-76
2023-02-23 11:17:04,421 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-76
2023-02-23 11:17:04,422 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-82
2023-02-23 11:17:04,422 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-82
2023-02-23 11:17:04,422 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-81
2023-02-23 11:17:04,422 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-80
2023-02-23 11:17:04,422 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-81
2023-02-23 11:17:04,422 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-80
2023-02-23 11:17:04,423 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-71
2023-02-23 11:17:04,423 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-71
2023-02-23 11:17:04,423 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-78
2023-02-23 11:17:04,423 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-79
2023-02-23 11:17:04,423 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-83
2023-02-23 11:17:04,423 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-78
2023-02-23 11:17:04,423 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-79
2023-02-23 11:17:04,423 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-83
2023-02-23 11:17:04,424 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-87
2023-02-23 11:17:04,424 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-84
2023-02-23 11:17:04,424 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-85
2023-02-23 11:17:04,424 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-87
2023-02-23 11:17:04,425 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-84
2023-02-23 11:17:04,425 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-85
2023-02-23 11:17:04,425 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-88
2023-02-23 11:17:04,425 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-88
2023-02-23 11:17:04,426 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-91
2023-02-23 11:17:04,426 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-91
2023-02-23 11:17:04,426 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-86
2023-02-23 11:17:04,426 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-89
2023-02-23 11:17:04,426 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-90
2023-02-23 11:17:04,427 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-86
2023-02-23 11:17:04,427 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-89
2023-02-23 11:17:04,427 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-90
2023-02-23 11:17:04,427 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-93
2023-02-23 11:17:04,427 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-93
2023-02-23 11:17:04,428 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-95
2023-02-23 11:17:04,428 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-92
2023-02-23 11:17:04,428 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-95
2023-02-23 11:17:04,428 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-92
2023-02-23 11:17:04,429 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-94
2023-02-23 11:17:04,429 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-94
2023-02-23 11:17:04,429 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-97
2023-02-23 11:17:04,429 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-97
2023-02-23 11:17:04,429 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-96
2023-02-23 11:17:04,429 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-96
2023-02-23 11:17:04,430 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-99
2023-02-23 11:17:04,430 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-98
2023-02-23 11:17:04,430 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-99
2023-02-23 11:17:04,430 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-98
2023-02-23 11:17:04,431 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-100
2023-02-23 11:17:04,432 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-100
2023-02-23 11:17:04,432 INFO o.a.j.e.StandardJMeterEngine: Notifying test listeners of end of test
2023-02-23 11:17:04,433 INFO o.a.j.r.Summariser: summary + 99 in 00:00:00 = 1736.8/s Avg: 18 Min: 1 Max: 58 Err: 0 (0.00%) Active: 0 Started: 100 Finished: 100
2023-02-23 11:17:04,434 INFO o.a.j.r.Summariser: summary = 100 in 00:01:00 = 1.7/s Avg: 18 Min: 1 Max: 58 Err: 0 (0.00%)
`
### Steps to reproduce the problem
The transaction controller checked the Generate parent sample option and ran jmeter in the background and the output was abnormal. May I ask whether this situation was caused by a bug?
### JMeter Version
5.5
### Java Version
openjdk version "11.0.12" 2021-07-20 OpenJDK Runtime Environment (build 11.0.12+7-post-Debian-2) OpenJDK 64-Bit Server VM (build 11.0.12+7-post-Debian-2, mixed mode, sharing)
### OS Version
windows10;Debian 5.10.84-1
|
1.0
|
Is this a bug? - ### Expected behavior
Run jmeter in the background to output the correct result
### Actual behavior



jmeter.log
`2023-02-23 11:16:03,974 INFO o.a.j.u.JMeterUtils: Setting Locale to en_EN
2023-02-23 11:16:03,994 INFO o.a.j.JMeter: Loading user properties from: /opt/apache-jmeter-5.5/bin/user.properties
2023-02-23 11:16:03,994 INFO o.a.j.JMeter: Loading system properties from: /opt/apache-jmeter-5.5/bin/system.properties
2023-02-23 11:16:04,000 INFO o.a.j.JMeter: Copyright (c) 1998-2022 The Apache Software Foundation
2023-02-23 11:16:04,000 INFO o.a.j.JMeter: Version 5.5
2023-02-23 11:16:04,000 INFO o.a.j.JMeter: java.version=17.0.4.1
2023-02-23 11:16:04,000 INFO o.a.j.JMeter: java.vm.name=OpenJDK 64-Bit Server VM
2023-02-23 11:16:04,000 INFO o.a.j.JMeter: os.name=Linux
2023-02-23 11:16:04,000 INFO o.a.j.JMeter: os.arch=amd64
2023-02-23 11:16:04,000 INFO o.a.j.JMeter: os.version=5.10.0-10-amd64
2023-02-23 11:16:04,000 INFO o.a.j.JMeter: file.encoding=UTF-8
2023-02-23 11:16:04,000 INFO o.a.j.JMeter: java.awt.headless=true
2023-02-23 11:16:04,000 INFO o.a.j.JMeter: Max memory =1073741824
2023-02-23 11:16:04,000 INFO o.a.j.JMeter: Available Processors =48
2023-02-23 11:16:04,010 INFO o.a.j.JMeter: Default Locale=English (EN)
2023-02-23 11:16:04,010 INFO o.a.j.JMeter: JMeter Locale=English (EN)
2023-02-23 11:16:04,010 INFO o.a.j.JMeter: JMeterHome=/opt/apache-jmeter-5.5
2023-02-23 11:16:04,010 INFO o.a.j.JMeter: user.dir =/root/.jenkins/workspace/csm
2023-02-23 11:16:04,010 INFO o.a.j.JMeter: PWD =/root/.jenkins/workspace/csm
2023-02-23 11:16:04,011 INFO o.a.j.JMeter: IP: 127.0.1.1 Name: performance FullName: performance
2023-02-23 11:16:04,019 INFO o.a.j.s.FileServer: Default base='/root/.jenkins/workspace/csm'
2023-02-23 11:16:04,020 INFO o.a.j.s.FileServer: Set new base='/root/.jenkins/workspace/csm/csm'
2023-02-23 11:16:04,161 INFO o.a.j.s.SaveService: Testplan (JMX) version: 2.2. Testlog (JTL) version: 2.2
2023-02-23 11:16:04,184 INFO o.a.j.s.SaveService: Using SaveService properties version 5.0
2023-02-23 11:16:04,187 INFO o.a.j.s.SaveService: Using SaveService properties file encoding UTF-8
2023-02-23 11:16:04,190 INFO o.a.j.s.SaveService: Loading file: csm/sm3.jmx
2023-02-23 11:16:04,249 INFO o.a.j.p.h.s.HTTPSamplerBase: Parser for text/html is org.apache.jmeter.protocol.http.parser.LagartoBasedHtmlParser
2023-02-23 11:16:04,249 INFO o.a.j.p.h.s.HTTPSamplerBase: Parser for application/xhtml+xml is org.apache.jmeter.protocol.http.parser.LagartoBasedHtmlParser
2023-02-23 11:16:04,249 INFO o.a.j.p.h.s.HTTPSamplerBase: Parser for application/xml is org.apache.jmeter.protocol.http.parser.LagartoBasedHtmlParser
2023-02-23 11:16:04,249 INFO o.a.j.p.h.s.HTTPSamplerBase: Parser for text/xml is org.apache.jmeter.protocol.http.parser.LagartoBasedHtmlParser
2023-02-23 11:16:04,250 INFO o.a.j.p.h.s.HTTPSamplerBase: Parser for text/vnd.wap.wml is org.apache.jmeter.protocol.http.parser.RegexpHTMLParser
2023-02-23 11:16:04,250 INFO o.a.j.p.h.s.HTTPSamplerBase: Parser for text/css is org.apache.jmeter.protocol.http.parser.CssParser
2023-02-23 11:16:04,273 INFO o.a.j.JMeter: Creating summariser <summary>
2023-02-23 11:16:04,284 INFO o.a.j.e.StandardJMeterEngine: Running the test!
2023-02-23 11:16:04,285 INFO o.a.j.s.SampleEvent: List of sample_variables: []
2023-02-23 11:16:04,286 INFO o.a.j.s.SampleEvent: List of sample_variables: []
2023-02-23 11:16:04,291 INFO o.a.j.e.u.CompoundVariable: Note: Function class names must contain the string: '.functions.'
2023-02-23 11:16:04,291 INFO o.a.j.e.u.CompoundVariable: Note: Function class names must not contain the string: '.gui.'
2023-02-23 11:16:04,344 INFO o.a.j.JMeter: Running test (1677122164344)
2023-02-23 11:16:04,366 INFO o.a.j.e.StandardJMeterEngine: Starting ThreadGroup: 1 : Thread Group
2023-02-23 11:16:04,366 INFO o.a.j.e.StandardJMeterEngine: Starting 100 threads for group Thread Group.
2023-02-23 11:16:04,367 INFO o.a.j.e.StandardJMeterEngine: Thread will continue on error
2023-02-23 11:16:04,367 INFO o.a.j.t.ThreadGroup: Starting thread group... number=1 threads=100 ramp-up=1 delayedStart=false
2023-02-23 11:16:04,374 INFO o.a.j.s.SampleResult: Note: Sample TimeStamps are START times
2023-02-23 11:16:04,375 INFO o.a.j.s.SampleResult: sampleresult.default.encoding is set to ISO-8859-1
2023-02-23 11:16:04,375 INFO o.a.j.s.SampleResult: sampleresult.useNanoTime=true
2023-02-23 11:16:04,375 INFO o.a.j.s.SampleResult: sampleresult.nanoThreadSleep=5000
2023-02-23 11:16:04,376 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-1
2023-02-23 11:16:04,382 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-2
2023-02-23 11:16:04,391 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-3
2023-02-23 11:16:04,395 INFO o.a.j.p.h.s.HTTPHCAbstractImpl: Local host = performance
2023-02-23 11:16:04,400 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-4
2023-02-23 11:16:04,402 INFO o.a.j.p.h.s.HTTPHC4Impl: HTTP request retry count = 0
2023-02-23 11:16:04,409 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-5
2023-02-23 11:16:04,419 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-6
2023-02-23 11:16:04,429 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-7
2023-02-23 11:16:04,432 INFO o.a.j.t.ThreadGroup: Started thread group number 1
2023-02-23 11:16:04,432 INFO o.a.j.e.StandardJMeterEngine: All thread groups have been started
2023-02-23 11:16:04,439 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-8
2023-02-23 11:16:04,448 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-9
2023-02-23 11:16:04,458 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-10
2023-02-23 11:16:04,468 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-11
2023-02-23 11:16:04,478 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-12
2023-02-23 11:16:04,488 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-13
2023-02-23 11:16:04,499 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-14
2023-02-23 11:16:04,508 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-15
2023-02-23 11:16:04,518 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-16
2023-02-23 11:16:04,528 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-17
2023-02-23 11:16:04,538 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-18
2023-02-23 11:16:04,548 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-19
2023-02-23 11:16:04,557 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-20
2023-02-23 11:16:04,568 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-21
2023-02-23 11:16:04,578 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-22
2023-02-23 11:16:04,588 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-23
2023-02-23 11:16:04,598 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-24
2023-02-23 11:16:04,607 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-25
2023-02-23 11:16:04,618 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-26
2023-02-23 11:16:04,628 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-27
2023-02-23 11:16:04,637 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-28
2023-02-23 11:16:04,648 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-29
2023-02-23 11:16:04,658 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-30
2023-02-23 11:16:04,678 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-31
2023-02-23 11:16:04,679 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-32
2023-02-23 11:16:04,688 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-33
2023-02-23 11:16:04,698 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-34
2023-02-23 11:16:04,709 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-35
2023-02-23 11:16:04,718 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-36
2023-02-23 11:16:04,728 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-37
2023-02-23 11:16:04,739 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-38
2023-02-23 11:16:04,748 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-39
2023-02-23 11:16:04,758 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-40
2023-02-23 11:16:04,768 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-41
2023-02-23 11:16:04,778 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-42
2023-02-23 11:16:04,788 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-43
2023-02-23 11:16:04,798 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-44
2023-02-23 11:16:04,808 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-45
2023-02-23 11:16:04,818 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-46
2023-02-23 11:16:04,829 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-47
2023-02-23 11:16:04,838 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-48
2023-02-23 11:16:04,848 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-49
2023-02-23 11:16:04,859 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-50
2023-02-23 11:16:04,868 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-51
2023-02-23 11:16:04,878 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-52
2023-02-23 11:16:04,888 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-53
2023-02-23 11:16:04,904 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-54
2023-02-23 11:16:04,908 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-55
2023-02-23 11:16:04,918 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-56
2023-02-23 11:16:04,928 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-57
2023-02-23 11:16:04,938 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-58
2023-02-23 11:16:04,949 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-59
2023-02-23 11:16:04,958 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-60
2023-02-23 11:16:04,968 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-61
2023-02-23 11:16:04,979 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-62
2023-02-23 11:16:04,988 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-63
2023-02-23 11:16:04,998 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-64
2023-02-23 11:16:05,008 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-65
2023-02-23 11:16:05,018 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-66
2023-02-23 11:16:05,028 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-67
2023-02-23 11:16:05,038 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-68
2023-02-23 11:16:05,048 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-69
2023-02-23 11:16:05,058 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-70
2023-02-23 11:16:05,068 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-71
2023-02-23 11:16:05,078 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-72
2023-02-23 11:16:05,088 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-73
2023-02-23 11:16:05,098 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-74
2023-02-23 11:16:05,108 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-75
2023-02-23 11:16:05,118 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-76
2023-02-23 11:16:05,128 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-77
2023-02-23 11:16:05,138 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-78
2023-02-23 11:16:05,148 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-79
2023-02-23 11:16:05,158 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-80
2023-02-23 11:16:05,169 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-81
2023-02-23 11:16:05,179 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-82
2023-02-23 11:16:05,188 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-83
2023-02-23 11:16:05,198 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-84
2023-02-23 11:16:05,212 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-85
2023-02-23 11:16:05,218 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-86
2023-02-23 11:16:05,228 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-87
2023-02-23 11:16:05,238 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-88
2023-02-23 11:16:05,248 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-89
2023-02-23 11:16:05,258 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-90
2023-02-23 11:16:05,268 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-91
2023-02-23 11:16:05,278 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-92
2023-02-23 11:16:05,288 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-93
2023-02-23 11:16:05,298 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-94
2023-02-23 11:16:05,308 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-95
2023-02-23 11:16:05,318 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-96
2023-02-23 11:16:05,328 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-97
2023-02-23 11:16:05,338 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-98
2023-02-23 11:16:05,348 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-99
2023-02-23 11:16:05,358 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-100
2023-02-23 11:17:04,372 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-2
2023-02-23 11:17:04,370 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-1
2023-02-23 11:17:04,374 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-5
2023-02-23 11:17:04,376 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-5
2023-02-23 11:17:04,376 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-1
2023-02-23 11:17:04,379 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-3
2023-02-23 11:17:04,379 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-3
2023-02-23 11:17:04,380 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-12
2023-02-23 11:17:04,380 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-6
2023-02-23 11:17:04,380 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-12
2023-02-23 11:17:04,380 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-6
2023-02-23 11:17:04,384 INFO o.a.j.r.Summariser: summary + 1 in 00:01:00 = 0.0/s Avg: 11 Min: 11 Max: 11 Err: 0 (0.00%) Active: 100 Started: 100 Finished: 0
2023-02-23 11:17:04,384 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-16
2023-02-23 11:17:04,384 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-7
2023-02-23 11:17:04,384 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-16
2023-02-23 11:17:04,385 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-7
2023-02-23 11:17:04,385 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-2
2023-02-23 11:17:04,386 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-20
2023-02-23 11:17:04,386 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-20
2023-02-23 11:17:04,387 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-13
2023-02-23 11:17:04,387 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-4
2023-02-23 11:17:04,387 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-13
2023-02-23 11:17:04,387 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-15
2023-02-23 11:17:04,387 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-24
2023-02-23 11:17:04,387 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-4
2023-02-23 11:17:04,387 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-24
2023-02-23 11:17:04,387 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-15
2023-02-23 11:17:04,387 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-22
2023-02-23 11:17:04,388 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-26
2023-02-23 11:17:04,388 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-9
2023-02-23 11:17:04,388 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-9
2023-02-23 11:17:04,388 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-26
2023-02-23 11:17:04,388 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-25
2023-02-23 11:17:04,388 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-17
2023-02-23 11:17:04,388 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-21
2023-02-23 11:17:04,388 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-17
2023-02-23 11:17:04,388 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-25
2023-02-23 11:17:04,388 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-22
2023-02-23 11:17:04,388 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-14
2023-02-23 11:17:04,388 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-21
2023-02-23 11:17:04,388 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-8
2023-02-23 11:17:04,389 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-14
2023-02-23 11:17:04,389 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-8
2023-02-23 11:17:04,390 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-10
2023-02-23 11:17:04,390 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-32
2023-02-23 11:17:04,390 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-10
2023-02-23 11:17:04,390 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-11
2023-02-23 11:17:04,390 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-32
2023-02-23 11:17:04,390 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-33
2023-02-23 11:17:04,390 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-11
2023-02-23 11:17:04,390 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-33
2023-02-23 11:17:04,392 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-27
2023-02-23 11:17:04,392 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-27
2023-02-23 11:17:04,394 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-36
2023-02-23 11:17:04,394 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-31
2023-02-23 11:17:04,394 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-28
2023-02-23 11:17:04,394 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-36
2023-02-23 11:17:04,394 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-31
2023-02-23 11:17:04,394 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-28
2023-02-23 11:17:04,395 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-19
2023-02-23 11:17:04,395 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-19
2023-02-23 11:17:04,396 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-23
2023-02-23 11:17:04,396 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-29
2023-02-23 11:17:04,396 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-23
2023-02-23 11:17:04,396 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-29
2023-02-23 11:17:04,397 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-34
2023-02-23 11:17:04,397 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-38
2023-02-23 11:17:04,397 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-34
2023-02-23 11:17:04,397 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-38
2023-02-23 11:17:04,398 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-44
2023-02-23 11:17:04,398 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-18
2023-02-23 11:17:04,398 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-42
2023-02-23 11:17:04,398 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-44
2023-02-23 11:17:04,398 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-18
2023-02-23 11:17:04,398 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-42
2023-02-23 11:17:04,399 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-41
2023-02-23 11:17:04,399 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-41
2023-02-23 11:17:04,400 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-37
2023-02-23 11:17:04,400 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-37
2023-02-23 11:17:04,400 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-40
2023-02-23 11:17:04,401 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-40
2023-02-23 11:17:04,401 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-45
2023-02-23 11:17:04,401 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-49
2023-02-23 11:17:04,401 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-45
2023-02-23 11:17:04,401 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-48
2023-02-23 11:17:04,401 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-49
2023-02-23 11:17:04,401 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-48
2023-02-23 11:17:04,402 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-35
2023-02-23 11:17:04,402 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-30
2023-02-23 11:17:04,402 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-46
2023-02-23 11:17:04,402 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-35
2023-02-23 11:17:04,402 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-30
2023-02-23 11:17:04,402 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-46
2023-02-23 11:17:04,402 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-51
2023-02-23 11:17:04,403 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-43
2023-02-23 11:17:04,403 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-39
2023-02-23 11:17:04,403 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-47
2023-02-23 11:17:04,403 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-51
2023-02-23 11:17:04,403 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-43
2023-02-23 11:17:04,403 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-39
2023-02-23 11:17:04,403 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-47
2023-02-23 11:17:04,405 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-56
2023-02-23 11:17:04,405 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-56
2023-02-23 11:17:04,407 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-53
2023-02-23 11:17:04,407 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-52
2023-02-23 11:17:04,407 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-53
2023-02-23 11:17:04,408 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-52
2023-02-23 11:17:04,408 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-60
2023-02-23 11:17:04,408 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-50
2023-02-23 11:17:04,408 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-58
2023-02-23 11:17:04,408 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-60
2023-02-23 11:17:04,408 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-50
2023-02-23 11:17:04,409 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-58
2023-02-23 11:17:04,409 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-59
2023-02-23 11:17:04,409 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-55
2023-02-23 11:17:04,409 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-59
2023-02-23 11:17:04,409 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-55
2023-02-23 11:17:04,409 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-61
2023-02-23 11:17:04,409 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-61
2023-02-23 11:17:04,410 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-54
2023-02-23 11:17:04,410 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-54
2023-02-23 11:17:04,411 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-57
2023-02-23 11:17:04,411 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-57
2023-02-23 11:17:04,412 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-65
2023-02-23 11:17:04,412 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-65
2023-02-23 11:17:04,414 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-64
2023-02-23 11:17:04,414 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-64
2023-02-23 11:17:04,414 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-68
2023-02-23 11:17:04,414 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-67
2023-02-23 11:17:04,414 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-68
2023-02-23 11:17:04,415 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-66
2023-02-23 11:17:04,415 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-67
2023-02-23 11:17:04,415 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-62
2023-02-23 11:17:04,415 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-66
2023-02-23 11:17:04,415 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-62
2023-02-23 11:17:04,415 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-63
2023-02-23 11:17:04,416 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-63
2023-02-23 11:17:04,416 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-70
2023-02-23 11:17:04,416 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-70
2023-02-23 11:17:04,416 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-69
2023-02-23 11:17:04,416 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-69
2023-02-23 11:17:04,417 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-72
2023-02-23 11:17:04,418 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-72
2023-02-23 11:17:04,418 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-73
2023-02-23 11:17:04,418 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-73
2023-02-23 11:17:04,418 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-74
2023-02-23 11:17:04,419 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-74
2023-02-23 11:17:04,419 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-75
2023-02-23 11:17:04,419 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-75
2023-02-23 11:17:04,419 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-77
2023-02-23 11:17:04,420 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-77
2023-02-23 11:17:04,421 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-76
2023-02-23 11:17:04,421 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-76
2023-02-23 11:17:04,422 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-82
2023-02-23 11:17:04,422 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-82
2023-02-23 11:17:04,422 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-81
2023-02-23 11:17:04,422 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-80
2023-02-23 11:17:04,422 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-81
2023-02-23 11:17:04,422 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-80
2023-02-23 11:17:04,423 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-71
2023-02-23 11:17:04,423 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-71
2023-02-23 11:17:04,423 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-78
2023-02-23 11:17:04,423 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-79
2023-02-23 11:17:04,423 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-83
2023-02-23 11:17:04,423 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-78
2023-02-23 11:17:04,423 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-79
2023-02-23 11:17:04,423 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-83
2023-02-23 11:17:04,424 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-87
2023-02-23 11:17:04,424 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-84
2023-02-23 11:17:04,424 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-85
2023-02-23 11:17:04,424 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-87
2023-02-23 11:17:04,425 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-84
2023-02-23 11:17:04,425 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-85
2023-02-23 11:17:04,425 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-88
2023-02-23 11:17:04,425 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-88
2023-02-23 11:17:04,426 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-91
2023-02-23 11:17:04,426 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-91
2023-02-23 11:17:04,426 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-86
2023-02-23 11:17:04,426 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-89
2023-02-23 11:17:04,426 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-90
2023-02-23 11:17:04,427 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-86
2023-02-23 11:17:04,427 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-89
2023-02-23 11:17:04,427 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-90
2023-02-23 11:17:04,427 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-93
2023-02-23 11:17:04,427 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-93
2023-02-23 11:17:04,428 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-95
2023-02-23 11:17:04,428 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-92
2023-02-23 11:17:04,428 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-95
2023-02-23 11:17:04,428 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-92
2023-02-23 11:17:04,429 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-94
2023-02-23 11:17:04,429 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-94
2023-02-23 11:17:04,429 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-97
2023-02-23 11:17:04,429 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-97
2023-02-23 11:17:04,429 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-96
2023-02-23 11:17:04,429 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-96
2023-02-23 11:17:04,430 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-99
2023-02-23 11:17:04,430 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-98
2023-02-23 11:17:04,430 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-99
2023-02-23 11:17:04,430 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-98
2023-02-23 11:17:04,431 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group 1-100
2023-02-23 11:17:04,432 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-100
2023-02-23 11:17:04,432 INFO o.a.j.e.StandardJMeterEngine: Notifying test listeners of end of test
2023-02-23 11:17:04,433 INFO o.a.j.r.Summariser: summary + 99 in 00:00:00 = 1736.8/s Avg: 18 Min: 1 Max: 58 Err: 0 (0.00%) Active: 0 Started: 100 Finished: 100
2023-02-23 11:17:04,434 INFO o.a.j.r.Summariser: summary = 100 in 00:01:00 = 1.7/s Avg: 18 Min: 1 Max: 58 Err: 0 (0.00%)
`
### Steps to reproduce the problem
The transaction controller checked the Generate parent sample option and ran jmeter in the background and the output was abnormal. May I ask whether this situation was caused by a bug?
### JMeter Version
5.5
### Java Version
openjdk version "11.0.12" 2021-07-20 OpenJDK Runtime Environment (build 11.0.12+7-post-Debian-2) OpenJDK 64-Bit Server VM (build 11.0.12+7-post-Debian-2, mixed mode, sharing)
### OS Version
windows10;Debian 5.10.84-1
|
defect
|
is this a bug expected behavior run jmeter in the background to output the correct result actual behavior jmeter log info o a j u jmeterutils setting locale to en en info o a j jmeter loading user properties from opt apache jmeter bin user properties info o a j jmeter loading system properties from opt apache jmeter bin system properties info o a j jmeter copyright c the apache software foundation info o a j jmeter version info o a j jmeter java version info o a j jmeter java vm name openjdk bit server vm info o a j jmeter os name linux info o a j jmeter os arch info o a j jmeter os version info o a j jmeter file encoding utf info o a j jmeter java awt headless true info o a j jmeter max memory info o a j jmeter available processors info o a j jmeter default locale english en info o a j jmeter jmeter locale english en info o a j jmeter jmeterhome opt apache jmeter info o a j jmeter user dir root jenkins workspace csm info o a j jmeter pwd root jenkins workspace csm info o a j jmeter ip name performance fullname performance info o a j s fileserver default base root jenkins workspace csm info o a j s fileserver set new base root jenkins workspace csm csm info o a j s saveservice testplan jmx version testlog jtl version info o a j s saveservice using saveservice properties version info o a j s saveservice using saveservice properties file encoding utf info o a j s saveservice loading file csm jmx info o a j p h s httpsamplerbase parser for text html is org apache jmeter protocol http parser lagartobasedhtmlparser info o a j p h s httpsamplerbase parser for application xhtml xml is org apache jmeter protocol http parser lagartobasedhtmlparser info o a j p h s httpsamplerbase parser for application xml is org apache jmeter protocol http parser lagartobasedhtmlparser info o a j p h s httpsamplerbase parser for text xml is org apache jmeter protocol http parser lagartobasedhtmlparser info o a j p h s httpsamplerbase parser for text vnd wap wml is org apache jmeter protocol http parser regexphtmlparser info o a j p h s httpsamplerbase parser for text css is org apache jmeter protocol http parser cssparser info o a j jmeter creating summariser info o a j e standardjmeterengine running the test info o a j s sampleevent list of sample variables info o a j s sampleevent list of sample variables info o a j e u compoundvariable note function class names must contain the string functions info o a j e u compoundvariable note function class names must not contain the string gui info o a j jmeter running test info o a j e standardjmeterengine starting threadgroup thread group info o a j e standardjmeterengine starting threads for group thread group info o a j e standardjmeterengine thread will continue on error info o a j t threadgroup starting thread group number threads ramp up delayedstart false info o a j s sampleresult note sample timestamps are start times info o a j s sampleresult sampleresult default encoding is set to iso info o a j s sampleresult sampleresult usenanotime true info o a j s sampleresult sampleresult nanothreadsleep info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j p h s httphcabstractimpl local host performance info o a j t jmeterthread thread started thread group info o a j p h s http request retry count info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t threadgroup started thread group number info o a j e standardjmeterengine all thread groups have been started info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread thread started thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j r summariser summary in s avg min max err active started finished info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread thread finished thread group info o a j t jmeterthread stopping because end time detected by thread thread group info o a j t jmeterthread thread finished thread group info o a j e standardjmeterengine notifying test listeners of end of test info o a j r summariser summary in s avg min max err active started finished info o a j r summariser summary in s avg min max err steps to reproduce the problem the transaction controller checked the generate parent sample option and ran jmeter in the background and the output was abnormal may i ask whether this situation was caused by a bug jmeter version java version openjdk version openjdk runtime environment build post debian openjdk bit server vm build post debian mixed mode sharing os version debian
| 1
|
91,161
| 26,285,182,028
|
IssuesEvent
|
2023-01-07 19:00:54
|
FreeCAD/FreeCAD
|
https://api.github.com/repos/FreeCAD/FreeCAD
|
closed
|
[Issue] Addon Manager - Connection Failed / Unable to read data from GitHub...
|
packaging/building Addon Manager OS: Windows
|
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Forums discussion
https://forum.freecad.org/viewtopic.php?f=3&t=74990&p=651243&hilit=connection+failed&sid=f7710cc5821c918e569a396711991997#p651243
### Version
0.20 (Release)
### Full version info
```shell
0.20.2
29177 +426 (Git)
2022/12/07 02:35:37
```
### Subproject(s) affected?
Addon Manager
### Issue description
Addon Manager fails to start with error:

Connection failed: Unable to read data from GitHub: check your internet connection and proxy settings and try again.
### Anything else?
_No response_
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct
|
1.0
|
[Issue] Addon Manager - Connection Failed / Unable to read data from GitHub... - ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Forums discussion
https://forum.freecad.org/viewtopic.php?f=3&t=74990&p=651243&hilit=connection+failed&sid=f7710cc5821c918e569a396711991997#p651243
### Version
0.20 (Release)
### Full version info
```shell
0.20.2
29177 +426 (Git)
2022/12/07 02:35:37
```
### Subproject(s) affected?
Addon Manager
### Issue description
Addon Manager fails to start with error:

Connection failed: Unable to read data from GitHub: check your internet connection and proxy settings and try again.
### Anything else?
_No response_
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct
|
non_defect
|
addon manager connection failed unable to read data from github is there an existing issue for this i have searched the existing issues forums discussion version release full version info shell git subproject s affected addon manager issue description addon manager fails to start with error connection failed unable to read data from github check your internet connection and proxy settings and try again anything else no response code of conduct i agree to follow this project s code of conduct
| 0
|
73,058
| 24,433,325,860
|
IssuesEvent
|
2022-10-06 09:40:36
|
matrix-org/matrix-js-sdk
|
https://api.github.com/repos/matrix-org/matrix-js-sdk
|
opened
|
Room name needs to be re-calculated on new Function Members state events
|
T-Defect
|
MSC-like description of the `io.element.functional_members` state event:
https://github.com/vector-im/element-meta/blob/develop/spec/functional_members.md
## Steps to reproduce
1. Invite a bot to a DM room.
2. Note that the bot's name gets added to the dynamic room name.
3. Set a `io.element.functional_members` state event to exclude the bot name from the room name.
## Expected
An update to that room state updates the dynamic room name.
## Actual
The room name is only calculated when the room members change or you restart the client.
## What?? `io.element.` state events? Where is the Matrix standard?
[MSC2199: Canonical DMs](https://github.com/matrix-org/matrix-doc/blob/travis/msc/immutable-dms/proposals/2199-canonical-dms.md) defines `unimportant` users, which are likely going to accomplish the same.
However, we have an EMS product which needs this feature and it's still uncertain where MSC2199 is going.
Once the Spec supports hiding user names from dynamic room names, this custom state event will likely be deprecated.
|
1.0
|
Room name needs to be re-calculated on new Function Members state events - MSC-like description of the `io.element.functional_members` state event:
https://github.com/vector-im/element-meta/blob/develop/spec/functional_members.md
## Steps to reproduce
1. Invite a bot to a DM room.
2. Note that the bot's name gets added to the dynamic room name.
3. Set a `io.element.functional_members` state event to exclude the bot name from the room name.
## Expected
An update to that room state updates the dynamic room name.
## Actual
The room name is only calculated when the room members change or you restart the client.
## What?? `io.element.` state events? Where is the Matrix standard?
[MSC2199: Canonical DMs](https://github.com/matrix-org/matrix-doc/blob/travis/msc/immutable-dms/proposals/2199-canonical-dms.md) defines `unimportant` users, which are likely going to accomplish the same.
However, we have an EMS product which needs this feature and it's still uncertain where MSC2199 is going.
Once the Spec supports hiding user names from dynamic room names, this custom state event will likely be deprecated.
|
defect
|
room name needs to be re calculated on new function members state events msc like description of the io element functional members state event steps to reproduce invite a bot to a dm room note that the bot s name gets added to the dynamic room name set a io element functional members state event to exclude the bot name from the room name expected an update to that room state updates the dynamic room name actual the room name is only calculated when the room members change or you restart the client what io element state events where is the matrix standard defines unimportant users which are likely going to accomplish the same however we have an ems product which needs this feature and it s still uncertain where is going once the spec supports hiding user names from dynamic room names this custom state event will likely be deprecated
| 1
|
279,923
| 8,675,871,100
|
IssuesEvent
|
2018-11-30 12:19:54
|
Proliner/omoda
|
https://api.github.com/repos/Proliner/omoda
|
closed
|
klantonderzoek of image tracking een goed idee is
|
Priority: Low
|
Onderdeel voor Design Thinking
- vraag een klanten of image tracking een goed idee is
- vragen of ze een ander idee hebben
|
1.0
|
klantonderzoek of image tracking een goed idee is - Onderdeel voor Design Thinking
- vraag een klanten of image tracking een goed idee is
- vragen of ze een ander idee hebben
|
non_defect
|
klantonderzoek of image tracking een goed idee is onderdeel voor design thinking vraag een klanten of image tracking een goed idee is vragen of ze een ander idee hebben
| 0
|
439,428
| 12,682,620,841
|
IssuesEvent
|
2020-06-19 17:48:10
|
ankidroid/Anki-Android
|
https://api.github.com/repos/ankidroid/Anki-Android
|
closed
|
Decks name are not stripped
|
Priority-High
|
Current alpha of anki strips the deck names. We don't. This leads to the following bug, that I can create using both Anki and Ankidroid but not with only one of both:
https://forums.ankiweb.net/t/decks-with-trailing-spaces/89/4?u=arthurmilchior
It is not clear to me either whether we should just strip deck name (that's a really easy change to do), because I fear that in this case, a similar bug may occur if we sync with older version of anki (I have not yet tested. I'll do if no one has a better idea)
|
1.0
|
Decks name are not stripped - Current alpha of anki strips the deck names. We don't. This leads to the following bug, that I can create using both Anki and Ankidroid but not with only one of both:
https://forums.ankiweb.net/t/decks-with-trailing-spaces/89/4?u=arthurmilchior
It is not clear to me either whether we should just strip deck name (that's a really easy change to do), because I fear that in this case, a similar bug may occur if we sync with older version of anki (I have not yet tested. I'll do if no one has a better idea)
|
non_defect
|
decks name are not stripped current alpha of anki strips the deck names we don t this leads to the following bug that i can create using both anki and ankidroid but not with only one of both it is not clear to me either whether we should just strip deck name that s a really easy change to do because i fear that in this case a similar bug may occur if we sync with older version of anki i have not yet tested i ll do if no one has a better idea
| 0
|
7,995
| 8,129,910,749
|
IssuesEvent
|
2018-08-17 16:33:53
|
MicrosoftDocs/azure-docs
|
https://api.github.com/repos/MicrosoftDocs/azure-docs
|
closed
|
Error when creating PVC
|
assigned-to-author container-service/svc doc-enhancement in-progress triaged
|
Hello,
I'm getting two different errors when following the documentation. They might be related.
I've created the SC + PVC as such:
```
cat azure-file-sc.yaml
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
name: azurefile
provisioner: kubernetes.io/azure-file
mountOptions:
- dir_mode=0777
- file_mode=0777
- uid=1000
- gid=1000
parameters:
storageAccount: aks110storage
cat azure-file-pvc.yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: azurefile
spec:
accessModes:
- ReadWriteMany
storageClassName: azurefile
resources:
requests:
storage: 5Gi
```
But when I look at the PVC, I get the following errors: (1 RBAC error, 1 "Share already exists" error):
```
Warning ProvisioningFailed 33s persistentvolume-controller Failed to provision volume with StorageClass "azurefile": Couldn't create secret secrets is forbidden: User "system:serviceaccount:kube-system:persistent-volume-binder" cannot create secrets in the namespace "default"
Warning ProvisioningFailed 19s persistentvolume-controller Failed to provision volume with StorageClass "azurefile": failed to create share kubernetes-dynamic-pvc-f4732704-998a-11e8-a166-0a58ac1f1264 in account aks110storage: failed to create file share, err: storage: service returned error: StatusCode=409, ErrorCode=ShareAlreadyExists, ErrorMessage=The specified share already exists.
RequestId:b890a34a-701a-0013-5897-2da84a000000
Time:2018-08-06T15:11:26.0105288Z, RequestInitiated=Mon, 06 Aug 2018 15:11:25 GMT, RequestId=b890a34a-701a-0013-5897-2da84a000000, API Version=2016-05-31, QueryParameterName=, QueryParameterValue=
Warning ProvisioningFailed 4s persistentvolume-controller Failed to provision volume with StorageClass "azurefile": failed to create share kubernetes-dynamic-pvc-f4732704-998a-11e8-a166-0a58ac1f1264 in account aks110storage: failed to create file share, err: storage: service returned error: StatusCode=409, ErrorCode=ShareAlreadyExists, ErrorMessage=The specified share already exists.
```
Here is my K8S version info:
```
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.2", GitCommit:"81753b10df112992bf51bbc2c2f85208aad78335", GitTreeState:"clean", BuildDate:"2018-04-27T09:22:21Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.5", GitCommit:"32ac1c9073b132b8ba18aa830f46b77dcceb0723", GitTreeState:"clean", BuildDate:"2018-06-21T11:34:22Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
```
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: a57e48b4-dc33-0b9d-b773-42ce7d2bffd0
* Version Independent ID: e912ac2d-cf6a-0b54-4697-1940b1270874
* Content: [Use Azure File with AKS](https://docs.microsoft.com/en-us/azure/aks/azure-files-dynamic-pv)
* Content Source: [articles/aks/azure-files-dynamic-pv.md](https://github.com/Microsoft/azure-docs/blob/master/articles/aks/azure-files-dynamic-pv.md)
* Service: **container-service**
* GitHub Login: @iainfoulds
* Microsoft Alias: **iainfou**
|
1.0
|
Error when creating PVC - Hello,
I'm getting two different errors when following the documentation. They might be related.
I've created the SC + PVC as such:
```
cat azure-file-sc.yaml
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
name: azurefile
provisioner: kubernetes.io/azure-file
mountOptions:
- dir_mode=0777
- file_mode=0777
- uid=1000
- gid=1000
parameters:
storageAccount: aks110storage
cat azure-file-pvc.yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: azurefile
spec:
accessModes:
- ReadWriteMany
storageClassName: azurefile
resources:
requests:
storage: 5Gi
```
But when I look at the PVC, I get the following errors: (1 RBAC error, 1 "Share already exists" error):
```
Warning ProvisioningFailed 33s persistentvolume-controller Failed to provision volume with StorageClass "azurefile": Couldn't create secret secrets is forbidden: User "system:serviceaccount:kube-system:persistent-volume-binder" cannot create secrets in the namespace "default"
Warning ProvisioningFailed 19s persistentvolume-controller Failed to provision volume with StorageClass "azurefile": failed to create share kubernetes-dynamic-pvc-f4732704-998a-11e8-a166-0a58ac1f1264 in account aks110storage: failed to create file share, err: storage: service returned error: StatusCode=409, ErrorCode=ShareAlreadyExists, ErrorMessage=The specified share already exists.
RequestId:b890a34a-701a-0013-5897-2da84a000000
Time:2018-08-06T15:11:26.0105288Z, RequestInitiated=Mon, 06 Aug 2018 15:11:25 GMT, RequestId=b890a34a-701a-0013-5897-2da84a000000, API Version=2016-05-31, QueryParameterName=, QueryParameterValue=
Warning ProvisioningFailed 4s persistentvolume-controller Failed to provision volume with StorageClass "azurefile": failed to create share kubernetes-dynamic-pvc-f4732704-998a-11e8-a166-0a58ac1f1264 in account aks110storage: failed to create file share, err: storage: service returned error: StatusCode=409, ErrorCode=ShareAlreadyExists, ErrorMessage=The specified share already exists.
```
Here is my K8S version info:
```
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.2", GitCommit:"81753b10df112992bf51bbc2c2f85208aad78335", GitTreeState:"clean", BuildDate:"2018-04-27T09:22:21Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.5", GitCommit:"32ac1c9073b132b8ba18aa830f46b77dcceb0723", GitTreeState:"clean", BuildDate:"2018-06-21T11:34:22Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
```
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: a57e48b4-dc33-0b9d-b773-42ce7d2bffd0
* Version Independent ID: e912ac2d-cf6a-0b54-4697-1940b1270874
* Content: [Use Azure File with AKS](https://docs.microsoft.com/en-us/azure/aks/azure-files-dynamic-pv)
* Content Source: [articles/aks/azure-files-dynamic-pv.md](https://github.com/Microsoft/azure-docs/blob/master/articles/aks/azure-files-dynamic-pv.md)
* Service: **container-service**
* GitHub Login: @iainfoulds
* Microsoft Alias: **iainfou**
|
non_defect
|
error when creating pvc hello i m getting two different errors when following the documentation they might be related i ve created the sc pvc as such cat azure file sc yaml kind storageclass apiversion storage io metadata name azurefile provisioner kubernetes io azure file mountoptions dir mode file mode uid gid parameters storageaccount cat azure file pvc yaml apiversion kind persistentvolumeclaim metadata name azurefile spec accessmodes readwritemany storageclassname azurefile resources requests storage but when i look at the pvc i get the following errors rbac error share already exists error warning provisioningfailed persistentvolume controller failed to provision volume with storageclass azurefile couldn t create secret secrets is forbidden user system serviceaccount kube system persistent volume binder cannot create secrets in the namespace default warning provisioningfailed persistentvolume controller failed to provision volume with storageclass azurefile failed to create share kubernetes dynamic pvc in account failed to create file share err storage service returned error statuscode errorcode sharealreadyexists errormessage the specified share already exists requestid time requestinitiated mon aug gmt requestid api version queryparametername queryparametervalue warning provisioningfailed persistentvolume controller failed to provision volume with storageclass azurefile failed to create share kubernetes dynamic pvc in account failed to create file share err storage service returned error statuscode errorcode sharealreadyexists errormessage the specified share already exists here is my version info client version version info major minor gitversion gitcommit gittreestate clean builddate goversion compiler gc platform darwin server version version info major minor gitversion gitcommit gittreestate clean builddate goversion compiler gc platform linux document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source service container service github login iainfoulds microsoft alias iainfou
| 0
|
69,284
| 22,318,921,333
|
IssuesEvent
|
2022-06-14 03:04:52
|
scipy/scipy
|
https://api.github.com/repos/scipy/scipy
|
closed
|
BUG: Memory leak in function `Py_FindObjects` due to new reference is not decreased (static analyzer report)
|
defect scipy.ndimage
|
1. A new reference is returned and assigned to `tuple`.
https://github.com/scipy/scipy/blob/8627df31ab07d66b438c7e5d5880e3f4d435f248/scipy/ndimage/src/nd_image.c#L888
2. Assume `tuple` is not NULL.
https://github.com/scipy/scipy/blob/8627df31ab07d66b438c7e5d5880e3f4d435f248/scipy/ndimage/src/nd_image.c#L889
3. Assume taking the true branch.
https://github.com/scipy/scipy/blob/8627df31ab07d66b438c7e5d5880e3f4d435f248/scipy/ndimage/src/nd_image.c#L897
4. Goto `exit`. `tuple` goes out-of-scope without decreasing the refcnt.
https://github.com/scipy/scipy/blob/8627df31ab07d66b438c7e5d5880e3f4d435f248/scipy/ndimage/src/nd_image.c#L899
Internal Report ID: c5db6d
---
NOTE: the local variable `tuple` declared here is never used apart from line 925.
https://github.com/scipy/scipy/blob/8627df31ab07d66b438c7e5d5880e3f4d435f248/scipy/ndimage/src/nd_image.c#L850
|
1.0
|
BUG: Memory leak in function `Py_FindObjects` due to new reference is not decreased (static analyzer report) - 1. A new reference is returned and assigned to `tuple`.
https://github.com/scipy/scipy/blob/8627df31ab07d66b438c7e5d5880e3f4d435f248/scipy/ndimage/src/nd_image.c#L888
2. Assume `tuple` is not NULL.
https://github.com/scipy/scipy/blob/8627df31ab07d66b438c7e5d5880e3f4d435f248/scipy/ndimage/src/nd_image.c#L889
3. Assume taking the true branch.
https://github.com/scipy/scipy/blob/8627df31ab07d66b438c7e5d5880e3f4d435f248/scipy/ndimage/src/nd_image.c#L897
4. Goto `exit`. `tuple` goes out-of-scope without decreasing the refcnt.
https://github.com/scipy/scipy/blob/8627df31ab07d66b438c7e5d5880e3f4d435f248/scipy/ndimage/src/nd_image.c#L899
Internal Report ID: c5db6d
---
NOTE: the local variable `tuple` declared here is never used apart from line 925.
https://github.com/scipy/scipy/blob/8627df31ab07d66b438c7e5d5880e3f4d435f248/scipy/ndimage/src/nd_image.c#L850
|
defect
|
bug memory leak in function py findobjects due to new reference is not decreased static analyzer report a new reference is returned and assigned to tuple assume tuple is not null assume taking the true branch goto exit tuple goes out of scope without decreasing the refcnt internal report id note the local variable tuple declared here is never used apart from line
| 1
|
17,482
| 9,791,463,025
|
IssuesEvent
|
2019-06-10 15:05:41
|
JuliaRobotics/DistributedFactorGraphs.jl
|
https://api.github.com/repos/JuliaRobotics/DistributedFactorGraphs.jl
|
closed
|
Make DFG type stable
|
performance types
|
Maybe target DFG v0.2.x to not have dynamic types such as `Union` or `Any`, for example here:
https://github.com/JuliaRobotics/DistributedFactorGraphs.jl/blob/aa7ac5df8cec93d134cd43c453949aecd663461e/src/services/GraphsDFG.jl#L54
See here:
https://docs.julialang.org/en/v1/manual/performance-tips/#Avoid-containers-with-abstract-type-parameters-1
|
True
|
Make DFG type stable - Maybe target DFG v0.2.x to not have dynamic types such as `Union` or `Any`, for example here:
https://github.com/JuliaRobotics/DistributedFactorGraphs.jl/blob/aa7ac5df8cec93d134cd43c453949aecd663461e/src/services/GraphsDFG.jl#L54
See here:
https://docs.julialang.org/en/v1/manual/performance-tips/#Avoid-containers-with-abstract-type-parameters-1
|
non_defect
|
make dfg type stable maybe target dfg x to not have dynamic types such as union or any for example here see here
| 0
|
72,423
| 24,110,616,926
|
IssuesEvent
|
2022-09-20 11:01:51
|
primefaces/primeng
|
https://api.github.com/repos/primefaces/primeng
|
opened
|
primeng 14 tree select filter not retaining the checkbox selection
|
defect
|
### Describe the bug

### Environment
All
### Reproducer
_No response_
### Angular version
14.2.1
### PrimeNG version
14.1.0
### Build / Runtime
Angular CLI App
### Language
ALL
### Node version (for AoT issues node --version)
16.13.0
### Browser(s)
All
### Steps to reproduce the behavior
_No response_
### Expected behavior
_No response_
|
1.0
|
primeng 14 tree select filter not retaining the checkbox selection - ### Describe the bug

### Environment
All
### Reproducer
_No response_
### Angular version
14.2.1
### PrimeNG version
14.1.0
### Build / Runtime
Angular CLI App
### Language
ALL
### Node version (for AoT issues node --version)
16.13.0
### Browser(s)
All
### Steps to reproduce the behavior
_No response_
### Expected behavior
_No response_
|
defect
|
primeng tree select filter not retaining the checkbox selection describe the bug environment all reproducer no response angular version primeng version build runtime angular cli app language all node version for aot issues node version browser s all steps to reproduce the behavior no response expected behavior no response
| 1
|
63,243
| 7,708,990,187
|
IssuesEvent
|
2018-05-22 07:44:35
|
WordPress/gutenberg
|
https://api.github.com/repos/WordPress/gutenberg
|
opened
|
Selecting the Document tab should deselect blocks.
|
Needs Design Feedback [Type] Bug
|
**Describe the bug**
When you select a block and the Settings sidebar is open, the Block tab is automatically selected.
When you deselect a block, the Document tab is then opened.
If you select a block, then click the Document tab, logically this should also deselect the block.
**To Reproduce**
Steps to reproduce the behavior:
- Click a block, observe the Block tab is opened
- Click the Documents tab, observe the block is not deselected
**Expected behavior**
Way back, in version 0.6 I think, we used something a similar feature to autoselect the block inspector when a block had focus. We used a "breadcrumb" style instead of tabs for the sidebar, the idea being that the sidebar was always contextual, and when you had no block selected you were at the document scope, when a block selected you dug into the block scope.
This behavior is now reinstated, although with tabs. But because deselecting a block automatically selects the Document tab, it feels like selecting the Document tab when a block is selected should logically also deselect the block.
**Screenshots**

|
1.0
|
Selecting the Document tab should deselect blocks. - **Describe the bug**
When you select a block and the Settings sidebar is open, the Block tab is automatically selected.
When you deselect a block, the Document tab is then opened.
If you select a block, then click the Document tab, logically this should also deselect the block.
**To Reproduce**
Steps to reproduce the behavior:
- Click a block, observe the Block tab is opened
- Click the Documents tab, observe the block is not deselected
**Expected behavior**
Way back, in version 0.6 I think, we used something a similar feature to autoselect the block inspector when a block had focus. We used a "breadcrumb" style instead of tabs for the sidebar, the idea being that the sidebar was always contextual, and when you had no block selected you were at the document scope, when a block selected you dug into the block scope.
This behavior is now reinstated, although with tabs. But because deselecting a block automatically selects the Document tab, it feels like selecting the Document tab when a block is selected should logically also deselect the block.
**Screenshots**

|
non_defect
|
selecting the document tab should deselect blocks describe the bug when you select a block and the settings sidebar is open the block tab is automatically selected when you deselect a block the document tab is then opened if you select a block then click the document tab logically this should also deselect the block to reproduce steps to reproduce the behavior click a block observe the block tab is opened click the documents tab observe the block is not deselected expected behavior way back in version i think we used something a similar feature to autoselect the block inspector when a block had focus we used a breadcrumb style instead of tabs for the sidebar the idea being that the sidebar was always contextual and when you had no block selected you were at the document scope when a block selected you dug into the block scope this behavior is now reinstated although with tabs but because deselecting a block automatically selects the document tab it feels like selecting the document tab when a block is selected should logically also deselect the block screenshots
| 0
|
14,564
| 2,826,528,494
|
IssuesEvent
|
2015-05-22 03:34:19
|
canadainc/quran10
|
https://api.github.com/repos/canadainc/quran10
|
closed
|
Cannot enable Join Disconnected Letters because app keeps saying there is 1bytes left on device
|
Component-Logic Fixed OpSys-10.3.0 Priority-Critical Type-Defect Verified
|
On R072, 10.3.0.1434
Finished downloading tafsir. Now trying to enable Join Disconnected Letters, but when you do, it checks for metadata, then the Yes button in the confirm dialog is not enabled because not enough space.
This happens iff the download directory was never created.
|
1.0
|
Cannot enable Join Disconnected Letters because app keeps saying there is 1bytes left on device - On R072, 10.3.0.1434
Finished downloading tafsir. Now trying to enable Join Disconnected Letters, but when you do, it checks for metadata, then the Yes button in the confirm dialog is not enabled because not enough space.
This happens iff the download directory was never created.
|
defect
|
cannot enable join disconnected letters because app keeps saying there is left on device on finished downloading tafsir now trying to enable join disconnected letters but when you do it checks for metadata then the yes button in the confirm dialog is not enabled because not enough space this happens iff the download directory was never created
| 1
|
381,892
| 26,475,819,142
|
IssuesEvent
|
2023-01-17 11:02:03
|
Scirra/Construct-3-bugs
|
https://api.github.com/repos/Scirra/Construct-3-bugs
|
closed
|
wrong expression in gamepad manual entry
|
duplicate documentation
|
related to #6398 and r320
>Gamepad: replace LastButton expression with ButtonIndex, as due to an oversight LastButton never used its parameter
The gamepad manual entry refers to lastbutton despite it being replaced:
https://www.construct.net/en/make-games/manuals/construct-3/plugin-reference/gamepad
|
1.0
|
wrong expression in gamepad manual entry - related to #6398 and r320
>Gamepad: replace LastButton expression with ButtonIndex, as due to an oversight LastButton never used its parameter
The gamepad manual entry refers to lastbutton despite it being replaced:
https://www.construct.net/en/make-games/manuals/construct-3/plugin-reference/gamepad
|
non_defect
|
wrong expression in gamepad manual entry related to and gamepad replace lastbutton expression with buttonindex as due to an oversight lastbutton never used its parameter the gamepad manual entry refers to lastbutton despite it being replaced
| 0
|
300,610
| 25,980,402,972
|
IssuesEvent
|
2022-12-19 18:15:52
|
dotnet/fsharp
|
https://api.github.com/repos/dotnet/fsharp
|
closed
|
TypeProvider tests are disabled on .NET 5/6 testing
|
Area-Testing Continuous Improvement Needs-Triage
|
Too many type provider tests are disabled on .NET Core:
```
#if !NETCOREAPP
// All tests which do a manual invoke of the F# compiler are disabled
```
We should re-enable these.
|
1.0
|
TypeProvider tests are disabled on .NET 5/6 testing - Too many type provider tests are disabled on .NET Core:
```
#if !NETCOREAPP
// All tests which do a manual invoke of the F# compiler are disabled
```
We should re-enable these.
|
non_defect
|
typeprovider tests are disabled on net testing too many type provider tests are disabled on net core if netcoreapp all tests which do a manual invoke of the f compiler are disabled we should re enable these
| 0
|
13,308
| 2,752,094,582
|
IssuesEvent
|
2015-04-24 13:45:30
|
riverloopsec/killerbee
|
https://api.github.com/repos/riverloopsec/killerbee
|
closed
|
KB FW Source
|
auto-migrated Priority-Medium Type-Defect
|
```
Greetings,
Where can I DL the KB FW source?
Thanks,
Komp
```
Original issue reported on code.google.com by `komp...@gmail.com` on 20 Nov 2012 at 6:12
|
1.0
|
KB FW Source - ```
Greetings,
Where can I DL the KB FW source?
Thanks,
Komp
```
Original issue reported on code.google.com by `komp...@gmail.com` on 20 Nov 2012 at 6:12
|
defect
|
kb fw source greetings where can i dl the kb fw source thanks komp original issue reported on code google com by komp gmail com on nov at
| 1
|
72,955
| 24,383,582,061
|
IssuesEvent
|
2022-10-04 09:50:40
|
vector-im/element-web
|
https://api.github.com/repos/vector-im/element-web
|
closed
|
Surprise sunglasses (inappropriate plain-text emoji replacement)
|
T-Defect
|
### Steps to reproduce
1. Enable _Automatically replace plain text emoji_
2. Copy+paste this into the composer:
```
- [link](https://example.com/12345678)
-
```
3. Then type some more characters after the second bullet
4. 😎
### Outcome
#### What did you expect?
Not 😎
#### What happened instead?
😎
### Operating system
Windows 10
### Application version
Element Nightly version: 0.0.1-nightly.2022093001 Olm version: 3.2.12
### How did you install the app?
web then auto udpated
### Homeserver
lant.uk
### Will you send logs?
No
|
1.0
|
Surprise sunglasses (inappropriate plain-text emoji replacement) - ### Steps to reproduce
1. Enable _Automatically replace plain text emoji_
2. Copy+paste this into the composer:
```
- [link](https://example.com/12345678)
-
```
3. Then type some more characters after the second bullet
4. 😎
### Outcome
#### What did you expect?
Not 😎
#### What happened instead?
😎
### Operating system
Windows 10
### Application version
Element Nightly version: 0.0.1-nightly.2022093001 Olm version: 3.2.12
### How did you install the app?
web then auto udpated
### Homeserver
lant.uk
### Will you send logs?
No
|
defect
|
surprise sunglasses inappropriate plain text emoji replacement steps to reproduce enable automatically replace plain text emoji copy paste this into the composer then type some more characters after the second bullet 😎 outcome what did you expect not 😎 what happened instead 😎 operating system windows application version element nightly version nightly olm version how did you install the app web then auto udpated homeserver lant uk will you send logs no
| 1
|
53,654
| 13,262,058,427
|
IssuesEvent
|
2020-08-20 21:01:38
|
icecube-trac/tix4
|
https://api.github.com/repos/icecube-trac/tix4
|
closed
|
icetray - tests fail to build under C++11 w/ boost 1.48 (Trac #1823)
|
Migrated from Trac combo core defect
|
I'm guessing the root cause is the older boost version.
This is on morax.private.pa.umd.edu.
```text
[ 72%] Building CXX object icetray/CMakeFiles/icetray-test.dir/private/test/I3TrayTest.cxx.o
In file included from /usr/include/boost148/boost/iterator/transform_iterator.hpp:23:0,
from ../../source/icetray/public/icetray/I3Frame.h:29,
from ../../source/icetray/public/icetray/I3Module.h:32,
from ../../source/icetray/public/icetray/I3Tray.h:36,
from ../../source/icetray/private/test/I3TrayTest.cxx:3:
/usr/include/boost148/boost/utility/result_of.hpp: In instantiation of ‘struct boost::detail::result_of_nested_result<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>, local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>’:
/usr/include/boost148/boost/utility/result_of.hpp:83:8: required from ‘struct boost::detail::tr1_result_of_impl<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>, local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>), false>’
/usr/include/boost148/boost/utility/detail/result_of_iterate.hpp:23:8: required from ‘struct boost::tr1_result_of<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>’
/usr/include/boost148/boost/utility/detail/result_of_iterate.hpp:80:8: required from ‘struct boost::result_of<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>’
../../source/icetray/public/icetray/I3Tray.h:331:77: required from ‘typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type I3Tray::AddModule(Type, std::string) [with Type = local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>; typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type = I3Tray::param_setter; std::string = std::basic_string<char>]’
../../source/icetray/private/test/I3TrayTest.cxx:269:50: required from here
/usr/include/boost148/boost/utility/result_of.hpp:79:8: error: no class template named ‘result’ in ‘struct local_test_routine_functions_as_modules()::<lambda(class boost::shared_ptr<I3Frame>)>’
struct result_of_nested_result : F::template result<FArgs>
^
In file included from ../../source/icetray/private/test/I3TrayTest.cxx:3:0:
../../source/icetray/public/icetray/I3Tray.h: In instantiation of ‘typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type I3Tray::AddModule(Type, std::string) [with Type = local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>; typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type = I3Tray::param_setter; std::string = std::basic_string<char>]’:
../../source/icetray/private/test/I3TrayTest.cxx:269:50: required from here
../../source/icetray/public/icetray/I3Tray.h:331:77: error: no type named ‘type’ in ‘struct boost::result_of<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>’
typedef typename boost::result_of<Type(boost::shared_ptr<I3Frame>)>::type ResultType;
^
../../source/icetray/public/icetray/I3Tray.h:332:64: error: no matching function for call to ‘I3Tray::AddFunctionModule(local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>&, std::string&)’
return this->AddFunctionModule<ResultType>(func, instancename);
^
../../source/icetray/public/icetray/I3Tray.h:285:3: note: candidate: template<class RetType> I3Tray::param_setter I3Tray::AddFunctionModule(boost::function<RetType(boost::shared_ptr<I3Frame>)>, const string&)
AddFunctionModule(boost::function<RetType(boost::shared_ptr<I3Frame>)>,
^
../../source/icetray/public/icetray/I3Tray.h:285:3: note: template argument deduction/substitution failed:
In file included from /usr/include/boost148/boost/iterator/transform_iterator.hpp:23:0,
from ../../source/icetray/public/icetray/I3Frame.h:29,
from ../../source/icetray/public/icetray/I3Module.h:32,
from ../../source/icetray/public/icetray/I3Tray.h:36,
from ../../source/icetray/private/test/I3TrayTest.cxx:3:
/usr/include/boost148/boost/utility/result_of.hpp: In instantiation of ‘struct boost::detail::result_of_nested_result<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>, local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>’:
/usr/include/boost148/boost/utility/result_of.hpp:83:8: required from ‘struct boost::detail::tr1_result_of_impl<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>, local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>), false>’
/usr/include/boost148/boost/utility/detail/result_of_iterate.hpp:23:8: required from ‘struct boost::tr1_result_of<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>’
/usr/include/boost148/boost/utility/detail/result_of_iterate.hpp:80:8: required from ‘struct boost::result_of<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>’
../../source/icetray/public/icetray/I3Tray.h:331:77: required from ‘typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type I3Tray::AddModule(Type, std::string) [with Type = local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>; typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type = I3Tray::param_setter; std::string = std::basic_string<char>]’
../../source/icetray/private/test/I3TrayTest.cxx:270:65: required from here
/usr/include/boost148/boost/utility/result_of.hpp:79:8: error: no class template named ‘result’ in ‘struct local_test_routine_functions_as_modules()::<lambda(class boost::shared_ptr<I3Frame>)>’
struct result_of_nested_result : F::template result<FArgs>
^
In file included from ../../source/icetray/private/test/I3TrayTest.cxx:3:0:
../../source/icetray/public/icetray/I3Tray.h: In instantiation of ‘typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type I3Tray::AddModule(Type, std::string) [with Type = local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>; typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type = I3Tray::param_setter; std::string = std::basic_string<char>]’:
../../source/icetray/private/test/I3TrayTest.cxx:270:65: required from here
../../source/icetray/public/icetray/I3Tray.h:331:77: error: no type named ‘type’ in ‘struct boost::result_of<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>’
typedef typename boost::result_of<Type(boost::shared_ptr<I3Frame>)>::type ResultType;
^
../../source/icetray/public/icetray/I3Tray.h:332:64: error: no matching function for call to ‘I3Tray::AddFunctionModule(local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>&, std::string&)’
return this->AddFunctionModule<ResultType>(func, instancename);
^
../../source/icetray/public/icetray/I3Tray.h:285:3: note: candidate: template<class RetType> I3Tray::param_setter I3Tray::AddFunctionModule(boost::function<RetType(boost::shared_ptr<I3Frame>)>, const string&)
AddFunctionModule(boost::function<RetType(boost::shared_ptr<I3Frame>)>,
^
../../source/icetray/public/icetray/I3Tray.h:285:3: note: template argument deduction/substitution failed:
make[3]: *** [icetray/CMakeFiles/icetray-test.dir/private/test/I3TrayTest.cxx.o] Error 1
make[2]: *** [icetray/CMakeFiles/icetray-test.dir/all] Error 2
make[1]: *** [CMakeFiles/test-bins.dir/rule] Error 2
make: *** [test-bins] Error 2
[buildslave@morax build]$
```
<details>
<summary><em>Migrated from <a href="https://code.icecube.wisc.edu/projects/icecube/ticket/1823">https://code.icecube.wisc.edu/projects/icecube/ticket/1823</a>, reported by negaand owned by olivas</em></summary>
<p>
```json
{
"status": "closed",
"changetime": "2019-02-13T14:12:38",
"_ts": "1550067158057333",
"description": "I'm guessing the root cause is the older boost version.\n\nThis is on morax.private.pa.umd.edu.\n\n{{{\n[ 72%] Building CXX object icetray/CMakeFiles/icetray-test.dir/private/test/I3TrayTest.cxx.o\nIn file included from /usr/include/boost148/boost/iterator/transform_iterator.hpp:23:0,\n from ../../source/icetray/public/icetray/I3Frame.h:29,\n from ../../source/icetray/public/icetray/I3Module.h:32,\n from ../../source/icetray/public/icetray/I3Tray.h:36,\n from ../../source/icetray/private/test/I3TrayTest.cxx:3:\n/usr/include/boost148/boost/utility/result_of.hpp: In instantiation of \u2018struct boost::detail::result_of_nested_result<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>, local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>\u2019:\n/usr/include/boost148/boost/utility/result_of.hpp:83:8: required from \u2018struct boost::detail::tr1_result_of_impl<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>, local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>), false>\u2019\n/usr/include/boost148/boost/utility/detail/result_of_iterate.hpp:23:8: required from \u2018struct boost::tr1_result_of<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>\u2019\n/usr/include/boost148/boost/utility/detail/result_of_iterate.hpp:80:8: required from \u2018struct boost::result_of<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>\u2019\n../../source/icetray/public/icetray/I3Tray.h:331:77: required from \u2018typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type I3Tray::AddModule(Type, std::string) [with Type = local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>; typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type = I3Tray::param_setter; std::string = std::basic_string<char>]\u2019\n../../source/icetray/private/test/I3TrayTest.cxx:269:50: required from here\n/usr/include/boost148/boost/utility/result_of.hpp:79:8: error: no class template named \u2018result\u2019 in \u2018struct local_test_routine_functions_as_modules()::<lambda(class boost::shared_ptr<I3Frame>)>\u2019\n struct result_of_nested_result : F::template result<FArgs>\n ^\nIn file included from ../../source/icetray/private/test/I3TrayTest.cxx:3:0:\n../../source/icetray/public/icetray/I3Tray.h: In instantiation of \u2018typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type I3Tray::AddModule(Type, std::string) [with Type = local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>; typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type = I3Tray::param_setter; std::string = std::basic_string<char>]\u2019:\n../../source/icetray/private/test/I3TrayTest.cxx:269:50: required from here\n../../source/icetray/public/icetray/I3Tray.h:331:77: error: no type named \u2018type\u2019 in \u2018struct boost::result_of<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>\u2019\n typedef typename boost::result_of<Type(boost::shared_ptr<I3Frame>)>::type ResultType;\n ^\n../../source/icetray/public/icetray/I3Tray.h:332:64: error: no matching function for call to \u2018I3Tray::AddFunctionModule(local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>&, std::string&)\u2019\n return this->AddFunctionModule<ResultType>(func, instancename);\n ^\n../../source/icetray/public/icetray/I3Tray.h:285:3: note: candidate: template<class RetType> I3Tray::param_setter I3Tray::AddFunctionModule(boost::function<RetType(boost::shared_ptr<I3Frame>)>, const string&)\n AddFunctionModule(boost::function<RetType(boost::shared_ptr<I3Frame>)>,\n ^\n../../source/icetray/public/icetray/I3Tray.h:285:3: note: template argument deduction/substitution failed:\nIn file included from /usr/include/boost148/boost/iterator/transform_iterator.hpp:23:0,\n from ../../source/icetray/public/icetray/I3Frame.h:29,\n from ../../source/icetray/public/icetray/I3Module.h:32,\n from ../../source/icetray/public/icetray/I3Tray.h:36,\n from ../../source/icetray/private/test/I3TrayTest.cxx:3:\n/usr/include/boost148/boost/utility/result_of.hpp: In instantiation of \u2018struct boost::detail::result_of_nested_result<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>, local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>\u2019:\n/usr/include/boost148/boost/utility/result_of.hpp:83:8: required from \u2018struct boost::detail::tr1_result_of_impl<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>, local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>), false>\u2019\n/usr/include/boost148/boost/utility/detail/result_of_iterate.hpp:23:8: required from \u2018struct boost::tr1_result_of<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>\u2019\n/usr/include/boost148/boost/utility/detail/result_of_iterate.hpp:80:8: required from \u2018struct boost::result_of<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>\u2019\n../../source/icetray/public/icetray/I3Tray.h:331:77: required from \u2018typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type I3Tray::AddModule(Type, std::string) [with Type = local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>; typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type = I3Tray::param_setter; std::string = std::basic_string<char>]\u2019\n../../source/icetray/private/test/I3TrayTest.cxx:270:65: required from here\n/usr/include/boost148/boost/utility/result_of.hpp:79:8: error: no class template named \u2018result\u2019 in \u2018struct local_test_routine_functions_as_modules()::<lambda(class boost::shared_ptr<I3Frame>)>\u2019\n struct result_of_nested_result : F::template result<FArgs>\n ^\nIn file included from ../../source/icetray/private/test/I3TrayTest.cxx:3:0:\n../../source/icetray/public/icetray/I3Tray.h: In instantiation of \u2018typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type I3Tray::AddModule(Type, std::string) [with Type = local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>; typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type = I3Tray::param_setter; std::string = std::basic_string<char>]\u2019:\n../../source/icetray/private/test/I3TrayTest.cxx:270:65: required from here\n../../source/icetray/public/icetray/I3Tray.h:331:77: error: no type named \u2018type\u2019 in \u2018struct boost::result_of<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>\u2019\n typedef typename boost::result_of<Type(boost::shared_ptr<I3Frame>)>::type ResultType;\n ^\n../../source/icetray/public/icetray/I3Tray.h:332:64: error: no matching function for call to \u2018I3Tray::AddFunctionModule(local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>&, std::string&)\u2019\n return this->AddFunctionModule<ResultType>(func, instancename);\n ^\n../../source/icetray/public/icetray/I3Tray.h:285:3: note: candidate: template<class RetType> I3Tray::param_setter I3Tray::AddFunctionModule(boost::function<RetType(boost::shared_ptr<I3Frame>)>, const string&)\n AddFunctionModule(boost::function<RetType(boost::shared_ptr<I3Frame>)>,\n ^\n../../source/icetray/public/icetray/I3Tray.h:285:3: note: template argument deduction/substitution failed:\nmake[3]: *** [icetray/CMakeFiles/icetray-test.dir/private/test/I3TrayTest.cxx.o] Error 1\nmake[2]: *** [icetray/CMakeFiles/icetray-test.dir/all] Error 2\nmake[1]: *** [CMakeFiles/test-bins.dir/rule] Error 2\nmake: *** [test-bins] Error 2\n[buildslave@morax build]$ \n}}}",
"reporter": "nega",
"cc": "",
"resolution": "fixed",
"time": "2016-08-16T22:08:12",
"component": "combo core",
"summary": "icetray - tests fail to build under C++11 w/ boost 1.48",
"priority": "critical",
"keywords": "boost c++11",
"milestone": "",
"owner": "olivas",
"type": "defect"
}
```
</p>
</details>
|
1.0
|
icetray - tests fail to build under C++11 w/ boost 1.48 (Trac #1823) - I'm guessing the root cause is the older boost version.
This is on morax.private.pa.umd.edu.
```text
[ 72%] Building CXX object icetray/CMakeFiles/icetray-test.dir/private/test/I3TrayTest.cxx.o
In file included from /usr/include/boost148/boost/iterator/transform_iterator.hpp:23:0,
from ../../source/icetray/public/icetray/I3Frame.h:29,
from ../../source/icetray/public/icetray/I3Module.h:32,
from ../../source/icetray/public/icetray/I3Tray.h:36,
from ../../source/icetray/private/test/I3TrayTest.cxx:3:
/usr/include/boost148/boost/utility/result_of.hpp: In instantiation of ‘struct boost::detail::result_of_nested_result<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>, local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>’:
/usr/include/boost148/boost/utility/result_of.hpp:83:8: required from ‘struct boost::detail::tr1_result_of_impl<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>, local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>), false>’
/usr/include/boost148/boost/utility/detail/result_of_iterate.hpp:23:8: required from ‘struct boost::tr1_result_of<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>’
/usr/include/boost148/boost/utility/detail/result_of_iterate.hpp:80:8: required from ‘struct boost::result_of<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>’
../../source/icetray/public/icetray/I3Tray.h:331:77: required from ‘typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type I3Tray::AddModule(Type, std::string) [with Type = local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>; typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type = I3Tray::param_setter; std::string = std::basic_string<char>]’
../../source/icetray/private/test/I3TrayTest.cxx:269:50: required from here
/usr/include/boost148/boost/utility/result_of.hpp:79:8: error: no class template named ‘result’ in ‘struct local_test_routine_functions_as_modules()::<lambda(class boost::shared_ptr<I3Frame>)>’
struct result_of_nested_result : F::template result<FArgs>
^
In file included from ../../source/icetray/private/test/I3TrayTest.cxx:3:0:
../../source/icetray/public/icetray/I3Tray.h: In instantiation of ‘typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type I3Tray::AddModule(Type, std::string) [with Type = local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>; typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type = I3Tray::param_setter; std::string = std::basic_string<char>]’:
../../source/icetray/private/test/I3TrayTest.cxx:269:50: required from here
../../source/icetray/public/icetray/I3Tray.h:331:77: error: no type named ‘type’ in ‘struct boost::result_of<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>’
typedef typename boost::result_of<Type(boost::shared_ptr<I3Frame>)>::type ResultType;
^
../../source/icetray/public/icetray/I3Tray.h:332:64: error: no matching function for call to ‘I3Tray::AddFunctionModule(local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>&, std::string&)’
return this->AddFunctionModule<ResultType>(func, instancename);
^
../../source/icetray/public/icetray/I3Tray.h:285:3: note: candidate: template<class RetType> I3Tray::param_setter I3Tray::AddFunctionModule(boost::function<RetType(boost::shared_ptr<I3Frame>)>, const string&)
AddFunctionModule(boost::function<RetType(boost::shared_ptr<I3Frame>)>,
^
../../source/icetray/public/icetray/I3Tray.h:285:3: note: template argument deduction/substitution failed:
In file included from /usr/include/boost148/boost/iterator/transform_iterator.hpp:23:0,
from ../../source/icetray/public/icetray/I3Frame.h:29,
from ../../source/icetray/public/icetray/I3Module.h:32,
from ../../source/icetray/public/icetray/I3Tray.h:36,
from ../../source/icetray/private/test/I3TrayTest.cxx:3:
/usr/include/boost148/boost/utility/result_of.hpp: In instantiation of ‘struct boost::detail::result_of_nested_result<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>, local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>’:
/usr/include/boost148/boost/utility/result_of.hpp:83:8: required from ‘struct boost::detail::tr1_result_of_impl<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>, local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>), false>’
/usr/include/boost148/boost/utility/detail/result_of_iterate.hpp:23:8: required from ‘struct boost::tr1_result_of<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>’
/usr/include/boost148/boost/utility/detail/result_of_iterate.hpp:80:8: required from ‘struct boost::result_of<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>’
../../source/icetray/public/icetray/I3Tray.h:331:77: required from ‘typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type I3Tray::AddModule(Type, std::string) [with Type = local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>; typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type = I3Tray::param_setter; std::string = std::basic_string<char>]’
../../source/icetray/private/test/I3TrayTest.cxx:270:65: required from here
/usr/include/boost148/boost/utility/result_of.hpp:79:8: error: no class template named ‘result’ in ‘struct local_test_routine_functions_as_modules()::<lambda(class boost::shared_ptr<I3Frame>)>’
struct result_of_nested_result : F::template result<FArgs>
^
In file included from ../../source/icetray/private/test/I3TrayTest.cxx:3:0:
../../source/icetray/public/icetray/I3Tray.h: In instantiation of ‘typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type I3Tray::AddModule(Type, std::string) [with Type = local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>; typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type = I3Tray::param_setter; std::string = std::basic_string<char>]’:
../../source/icetray/private/test/I3TrayTest.cxx:270:65: required from here
../../source/icetray/public/icetray/I3Tray.h:331:77: error: no type named ‘type’ in ‘struct boost::result_of<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>’
typedef typename boost::result_of<Type(boost::shared_ptr<I3Frame>)>::type ResultType;
^
../../source/icetray/public/icetray/I3Tray.h:332:64: error: no matching function for call to ‘I3Tray::AddFunctionModule(local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>&, std::string&)’
return this->AddFunctionModule<ResultType>(func, instancename);
^
../../source/icetray/public/icetray/I3Tray.h:285:3: note: candidate: template<class RetType> I3Tray::param_setter I3Tray::AddFunctionModule(boost::function<RetType(boost::shared_ptr<I3Frame>)>, const string&)
AddFunctionModule(boost::function<RetType(boost::shared_ptr<I3Frame>)>,
^
../../source/icetray/public/icetray/I3Tray.h:285:3: note: template argument deduction/substitution failed:
make[3]: *** [icetray/CMakeFiles/icetray-test.dir/private/test/I3TrayTest.cxx.o] Error 1
make[2]: *** [icetray/CMakeFiles/icetray-test.dir/all] Error 2
make[1]: *** [CMakeFiles/test-bins.dir/rule] Error 2
make: *** [test-bins] Error 2
[buildslave@morax build]$
```
<details>
<summary><em>Migrated from <a href="https://code.icecube.wisc.edu/projects/icecube/ticket/1823">https://code.icecube.wisc.edu/projects/icecube/ticket/1823</a>, reported by negaand owned by olivas</em></summary>
<p>
```json
{
"status": "closed",
"changetime": "2019-02-13T14:12:38",
"_ts": "1550067158057333",
"description": "I'm guessing the root cause is the older boost version.\n\nThis is on morax.private.pa.umd.edu.\n\n{{{\n[ 72%] Building CXX object icetray/CMakeFiles/icetray-test.dir/private/test/I3TrayTest.cxx.o\nIn file included from /usr/include/boost148/boost/iterator/transform_iterator.hpp:23:0,\n from ../../source/icetray/public/icetray/I3Frame.h:29,\n from ../../source/icetray/public/icetray/I3Module.h:32,\n from ../../source/icetray/public/icetray/I3Tray.h:36,\n from ../../source/icetray/private/test/I3TrayTest.cxx:3:\n/usr/include/boost148/boost/utility/result_of.hpp: In instantiation of \u2018struct boost::detail::result_of_nested_result<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>, local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>\u2019:\n/usr/include/boost148/boost/utility/result_of.hpp:83:8: required from \u2018struct boost::detail::tr1_result_of_impl<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>, local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>), false>\u2019\n/usr/include/boost148/boost/utility/detail/result_of_iterate.hpp:23:8: required from \u2018struct boost::tr1_result_of<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>\u2019\n/usr/include/boost148/boost/utility/detail/result_of_iterate.hpp:80:8: required from \u2018struct boost::result_of<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>\u2019\n../../source/icetray/public/icetray/I3Tray.h:331:77: required from \u2018typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type I3Tray::AddModule(Type, std::string) [with Type = local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>; typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type = I3Tray::param_setter; std::string = std::basic_string<char>]\u2019\n../../source/icetray/private/test/I3TrayTest.cxx:269:50: required from here\n/usr/include/boost148/boost/utility/result_of.hpp:79:8: error: no class template named \u2018result\u2019 in \u2018struct local_test_routine_functions_as_modules()::<lambda(class boost::shared_ptr<I3Frame>)>\u2019\n struct result_of_nested_result : F::template result<FArgs>\n ^\nIn file included from ../../source/icetray/private/test/I3TrayTest.cxx:3:0:\n../../source/icetray/public/icetray/I3Tray.h: In instantiation of \u2018typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type I3Tray::AddModule(Type, std::string) [with Type = local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>; typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type = I3Tray::param_setter; std::string = std::basic_string<char>]\u2019:\n../../source/icetray/private/test/I3TrayTest.cxx:269:50: required from here\n../../source/icetray/public/icetray/I3Tray.h:331:77: error: no type named \u2018type\u2019 in \u2018struct boost::result_of<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>\u2019\n typedef typename boost::result_of<Type(boost::shared_ptr<I3Frame>)>::type ResultType;\n ^\n../../source/icetray/public/icetray/I3Tray.h:332:64: error: no matching function for call to \u2018I3Tray::AddFunctionModule(local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>&, std::string&)\u2019\n return this->AddFunctionModule<ResultType>(func, instancename);\n ^\n../../source/icetray/public/icetray/I3Tray.h:285:3: note: candidate: template<class RetType> I3Tray::param_setter I3Tray::AddFunctionModule(boost::function<RetType(boost::shared_ptr<I3Frame>)>, const string&)\n AddFunctionModule(boost::function<RetType(boost::shared_ptr<I3Frame>)>,\n ^\n../../source/icetray/public/icetray/I3Tray.h:285:3: note: template argument deduction/substitution failed:\nIn file included from /usr/include/boost148/boost/iterator/transform_iterator.hpp:23:0,\n from ../../source/icetray/public/icetray/I3Frame.h:29,\n from ../../source/icetray/public/icetray/I3Module.h:32,\n from ../../source/icetray/public/icetray/I3Tray.h:36,\n from ../../source/icetray/private/test/I3TrayTest.cxx:3:\n/usr/include/boost148/boost/utility/result_of.hpp: In instantiation of \u2018struct boost::detail::result_of_nested_result<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>, local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>\u2019:\n/usr/include/boost148/boost/utility/result_of.hpp:83:8: required from \u2018struct boost::detail::tr1_result_of_impl<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>, local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>), false>\u2019\n/usr/include/boost148/boost/utility/detail/result_of_iterate.hpp:23:8: required from \u2018struct boost::tr1_result_of<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>\u2019\n/usr/include/boost148/boost/utility/detail/result_of_iterate.hpp:80:8: required from \u2018struct boost::result_of<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>\u2019\n../../source/icetray/public/icetray/I3Tray.h:331:77: required from \u2018typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type I3Tray::AddModule(Type, std::string) [with Type = local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>; typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type = I3Tray::param_setter; std::string = std::basic_string<char>]\u2019\n../../source/icetray/private/test/I3TrayTest.cxx:270:65: required from here\n/usr/include/boost148/boost/utility/result_of.hpp:79:8: error: no class template named \u2018result\u2019 in \u2018struct local_test_routine_functions_as_modules()::<lambda(class boost::shared_ptr<I3Frame>)>\u2019\n struct result_of_nested_result : F::template result<FArgs>\n ^\nIn file included from ../../source/icetray/private/test/I3TrayTest.cxx:3:0:\n../../source/icetray/public/icetray/I3Tray.h: In instantiation of \u2018typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type I3Tray::AddModule(Type, std::string) [with Type = local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>; typename boost::disable_if<boost::mpl::or_<boost::is_base_of<I3Module, Type>, boost::is_same<boost::python::api::object, Type>, boost::is_convertible<Type, std::basic_string<char> >, is_shared_ptr<T> >, I3Tray::param_setter>::type = I3Tray::param_setter; std::string = std::basic_string<char>]\u2019:\n../../source/icetray/private/test/I3TrayTest.cxx:270:65: required from here\n../../source/icetray/public/icetray/I3Tray.h:331:77: error: no type named \u2018type\u2019 in \u2018struct boost::result_of<local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>(boost::shared_ptr<I3Frame>)>\u2019\n typedef typename boost::result_of<Type(boost::shared_ptr<I3Frame>)>::type ResultType;\n ^\n../../source/icetray/public/icetray/I3Tray.h:332:64: error: no matching function for call to \u2018I3Tray::AddFunctionModule(local_test_routine_functions_as_modules()::<lambda(boost::shared_ptr<I3Frame>)>&, std::string&)\u2019\n return this->AddFunctionModule<ResultType>(func, instancename);\n ^\n../../source/icetray/public/icetray/I3Tray.h:285:3: note: candidate: template<class RetType> I3Tray::param_setter I3Tray::AddFunctionModule(boost::function<RetType(boost::shared_ptr<I3Frame>)>, const string&)\n AddFunctionModule(boost::function<RetType(boost::shared_ptr<I3Frame>)>,\n ^\n../../source/icetray/public/icetray/I3Tray.h:285:3: note: template argument deduction/substitution failed:\nmake[3]: *** [icetray/CMakeFiles/icetray-test.dir/private/test/I3TrayTest.cxx.o] Error 1\nmake[2]: *** [icetray/CMakeFiles/icetray-test.dir/all] Error 2\nmake[1]: *** [CMakeFiles/test-bins.dir/rule] Error 2\nmake: *** [test-bins] Error 2\n[buildslave@morax build]$ \n}}}",
"reporter": "nega",
"cc": "",
"resolution": "fixed",
"time": "2016-08-16T22:08:12",
"component": "combo core",
"summary": "icetray - tests fail to build under C++11 w/ boost 1.48",
"priority": "critical",
"keywords": "boost c++11",
"milestone": "",
"owner": "olivas",
"type": "defect"
}
```
</p>
</details>
|
defect
|
icetray tests fail to build under c w boost trac i m guessing the root cause is the older boost version this is on morax private pa umd edu text building cxx object icetray cmakefiles icetray test dir private test cxx o in file included from usr include boost iterator transform iterator hpp from source icetray public icetray h from source icetray public icetray h from source icetray public icetray h from source icetray private test cxx usr include boost utility result of hpp in instantiation of ‘struct boost detail result of nested result local test routine functions as modules boost shared ptr ’ usr include boost utility result of hpp required from ‘struct boost detail result of impl local test routine functions as modules boost shared ptr false ’ usr include boost utility detail result of iterate hpp required from ‘struct boost result of boost shared ptr ’ usr include boost utility detail result of iterate hpp required from ‘struct boost result of boost shared ptr ’ source icetray public icetray h required from ‘typename boost disable if boost is same boost is convertible is shared ptr param setter type addmodule type std string ’ source icetray private test cxx required from here usr include boost utility result of hpp error no class template named ‘result’ in ‘struct local test routine functions as modules ’ struct result of nested result f template result in file included from source icetray private test cxx source icetray public icetray h in instantiation of ‘typename boost disable if boost is same boost is convertible is shared ptr param setter type addmodule type std string ’ source icetray private test cxx required from here source icetray public icetray h error no type named ‘type’ in ‘struct boost result of boost shared ptr ’ typedef typename boost result of type resulttype source icetray public icetray h error no matching function for call to ‘ addfunctionmodule local test routine functions as modules std string ’ return this addfunctionmodule func instancename source icetray public icetray h note candidate template param setter addfunctionmodule boost function const string addfunctionmodule boost function source icetray public icetray h note template argument deduction substitution failed in file included from usr include boost iterator transform iterator hpp from source icetray public icetray h from source icetray public icetray h from source icetray public icetray h from source icetray private test cxx usr include boost utility result of hpp in instantiation of ‘struct boost detail result of nested result local test routine functions as modules boost shared ptr ’ usr include boost utility result of hpp required from ‘struct boost detail result of impl local test routine functions as modules boost shared ptr false ’ usr include boost utility detail result of iterate hpp required from ‘struct boost result of boost shared ptr ’ usr include boost utility detail result of iterate hpp required from ‘struct boost result of boost shared ptr ’ source icetray public icetray h required from ‘typename boost disable if boost is same boost is convertible is shared ptr param setter type addmodule type std string ’ source icetray private test cxx required from here usr include boost utility result of hpp error no class template named ‘result’ in ‘struct local test routine functions as modules ’ struct result of nested result f template result in file included from source icetray private test cxx source icetray public icetray h in instantiation of ‘typename boost disable if boost is same boost is convertible is shared ptr param setter type addmodule type std string ’ source icetray private test cxx required from here source icetray public icetray h error no type named ‘type’ in ‘struct boost result of boost shared ptr ’ typedef typename boost result of type resulttype source icetray public icetray h error no matching function for call to ‘ addfunctionmodule local test routine functions as modules std string ’ return this addfunctionmodule func instancename source icetray public icetray h note candidate template param setter addfunctionmodule boost function const string addfunctionmodule boost function source icetray public icetray h note template argument deduction substitution failed make error make error make error make error migrated from json status closed changetime ts description i m guessing the root cause is the older boost version n nthis is on morax private pa umd edu n n n building cxx object icetray cmakefiles icetray test dir private test cxx o nin file included from usr include boost iterator transform iterator hpp n from source icetray public icetray h n from source icetray public icetray h n from source icetray public icetray h n from source icetray private test cxx n usr include boost utility result of hpp in instantiation of boost detail result of nested result local test routine functions as modules boost shared ptr n usr include boost utility result of hpp required from boost detail result of impl local test routine functions as modules boost shared ptr false n usr include boost utility detail result of iterate hpp required from boost result of boost shared ptr n usr include boost utility detail result of iterate hpp required from boost result of boost shared ptr n source icetray public icetray h required from boost disable if boost is same boost is convertible is shared ptr param setter type addmodule type std string n source icetray private test cxx required from here n usr include boost utility result of hpp error no class template named in local test routine functions as modules n struct result of nested result f template result n nin file included from source icetray private test cxx n source icetray public icetray h in instantiation of boost disable if boost is same boost is convertible is shared ptr param setter type addmodule type std string n source icetray private test cxx required from here n source icetray public icetray h error no type named in boost result of boost shared ptr n typedef typename boost result of type resulttype n n source icetray public icetray h error no matching function for call to addfunctionmodule local test routine functions as modules std string n return this addfunctionmodule func instancename n n source icetray public icetray h note candidate template param setter addfunctionmodule boost function const string n addfunctionmodule boost function n n source icetray public icetray h note template argument deduction substitution failed nin file included from usr include boost iterator transform iterator hpp n from source icetray public icetray h n from source icetray public icetray h n from source icetray public icetray h n from source icetray private test cxx n usr include boost utility result of hpp in instantiation of boost detail result of nested result local test routine functions as modules boost shared ptr n usr include boost utility result of hpp required from boost detail result of impl local test routine functions as modules boost shared ptr false n usr include boost utility detail result of iterate hpp required from boost result of boost shared ptr n usr include boost utility detail result of iterate hpp required from boost result of boost shared ptr n source icetray public icetray h required from boost disable if boost is same boost is convertible is shared ptr param setter type addmodule type std string n source icetray private test cxx required from here n usr include boost utility result of hpp error no class template named in local test routine functions as modules n struct result of nested result f template result n nin file included from source icetray private test cxx n source icetray public icetray h in instantiation of boost disable if boost is same boost is convertible is shared ptr param setter type addmodule type std string n source icetray private test cxx required from here n source icetray public icetray h error no type named in boost result of boost shared ptr n typedef typename boost result of type resulttype n n source icetray public icetray h error no matching function for call to addfunctionmodule local test routine functions as modules std string n return this addfunctionmodule func instancename n n source icetray public icetray h note candidate template param setter addfunctionmodule boost function const string n addfunctionmodule boost function n n source icetray public icetray h note template argument deduction substitution failed nmake error nmake error nmake error nmake error n n reporter nega cc resolution fixed time component combo core summary icetray tests fail to build under c w boost priority critical keywords boost c milestone owner olivas type defect
| 1
|
98,129
| 11,045,930,695
|
IssuesEvent
|
2019-12-09 15:57:59
|
CentOS-PaaS-SIG/linchpin
|
https://api.github.com/repos/CentOS-PaaS-SIG/linchpin
|
opened
|
Readme.rst under config folder is outdated
|
documentation improvement
|
The readme.rst which explains the CI workflow is outdated, it needs to be updated.
|
1.0
|
Readme.rst under config folder is outdated - The readme.rst which explains the CI workflow is outdated, it needs to be updated.
|
non_defect
|
readme rst under config folder is outdated the readme rst which explains the ci workflow is outdated it needs to be updated
| 0
|
48,199
| 13,067,516,995
|
IssuesEvent
|
2020-07-31 00:42:57
|
icecube-trac/tix2
|
https://api.github.com/repos/icecube-trac/tix2
|
closed
|
[filterscripts] Exception if no best Fit was found (Trac #1950)
|
Migrated from Trac combo reconstruction defect
|
Hello,
I am encountering this:
```text
ERROR (PythonFunction): Error running python function as module: (PythonFunction.cxx:173 in virtual void PythonFunction::Process())
ERROR (I3Module): OnlineL2_findBestSucceededFit: Exception thrown (I3Module.cxx:116 in void I3Module::Do(void (I3Module::*)()))
Traceback (most recent call last):
File "/data/user/flauber/scripts/executables/SimulationFiltering.py", line 412, in <module>
main(opts)
File "/data/user/flauber/scripts/executables/SimulationFiltering.py", line 371, in main
tray.Execute()
File "/mnt/lfs3/user/flauber/software/icerec_V05-00-05/build/lib/I3Tray.py", line 234, in Execute
super(I3Tray, self).Execute()
File "/mnt/lfs3/user/flauber/software/icerec_V05-00-05/build/lib/icecube/filterscripts/onlinel2filter.py", line 570, in findBestSucceededFit
frame.Put(name+"_BestFitName", "None")
Boost.Python.ArgumentError: Python argument types in
I3Frame.Put(I3Frame, str, str)
did not match C++ signature:
Put(I3Frame {lvalue}, std::string, boost::shared_ptr<I3FrameObject const>, I3Frame::Stream)
Put(I3Frame {lvalue}, std::string, boost::shared_ptr<I3FrameObject const>)
```
while running SimulationFiltering.py from filterscripts/resources/scripts
I guess, the "None" needs to be wrapped to become an dataclasses.I3String or similar.
Migrated from https://code.icecube.wisc.edu/ticket/1950
```json
{
"status": "closed",
"changetime": "2017-02-20T09:08:11",
"description": "Hello,\n\nI am encountering this:\n{{{\nERROR (PythonFunction): Error running python function as module: (PythonFunction.cxx:173 in virtual void PythonFunction::Process())\nERROR (I3Module): OnlineL2_findBestSucceededFit: Exception thrown (I3Module.cxx:116 in void I3Module::Do(void (I3Module::*)()))\nTraceback (most recent call last):\n File \"/data/user/flauber/scripts/executables/SimulationFiltering.py\", line 412, in <module>\n main(opts)\n File \"/data/user/flauber/scripts/executables/SimulationFiltering.py\", line 371, in main\n tray.Execute()\n File \"/mnt/lfs3/user/flauber/software/icerec_V05-00-05/build/lib/I3Tray.py\", line 234, in Execute\n super(I3Tray, self).Execute()\n File \"/mnt/lfs3/user/flauber/software/icerec_V05-00-05/build/lib/icecube/filterscripts/onlinel2filter.py\", line 570, in findBestSucceededFit\n frame.Put(name+\"_BestFitName\", \"None\")\nBoost.Python.ArgumentError: Python argument types in\n I3Frame.Put(I3Frame, str, str)\ndid not match C++ signature:\n Put(I3Frame {lvalue}, std::string, boost::shared_ptr<I3FrameObject const>, I3Frame::Stream)\n Put(I3Frame {lvalue}, std::string, boost::shared_ptr<I3FrameObject const>)\n}}}\n\nwhile running SimulationFiltering.py from filterscripts/resources/scripts\n\nI guess, the \"None\" needs to be wrapped to become an dataclasses.I3String or similar.\n",
"reporter": "flauber",
"cc": "",
"resolution": "fixed",
"_ts": "1487581691387840",
"component": "combo reconstruction",
"summary": "[filterscripts] Exception if no best Fit was found",
"priority": "normal",
"keywords": "filterscripts",
"time": "2017-02-20T08:51:22",
"milestone": "",
"owner": "thomas.kintscher",
"type": "defect"
}
```
|
1.0
|
[filterscripts] Exception if no best Fit was found (Trac #1950) - Hello,
I am encountering this:
```text
ERROR (PythonFunction): Error running python function as module: (PythonFunction.cxx:173 in virtual void PythonFunction::Process())
ERROR (I3Module): OnlineL2_findBestSucceededFit: Exception thrown (I3Module.cxx:116 in void I3Module::Do(void (I3Module::*)()))
Traceback (most recent call last):
File "/data/user/flauber/scripts/executables/SimulationFiltering.py", line 412, in <module>
main(opts)
File "/data/user/flauber/scripts/executables/SimulationFiltering.py", line 371, in main
tray.Execute()
File "/mnt/lfs3/user/flauber/software/icerec_V05-00-05/build/lib/I3Tray.py", line 234, in Execute
super(I3Tray, self).Execute()
File "/mnt/lfs3/user/flauber/software/icerec_V05-00-05/build/lib/icecube/filterscripts/onlinel2filter.py", line 570, in findBestSucceededFit
frame.Put(name+"_BestFitName", "None")
Boost.Python.ArgumentError: Python argument types in
I3Frame.Put(I3Frame, str, str)
did not match C++ signature:
Put(I3Frame {lvalue}, std::string, boost::shared_ptr<I3FrameObject const>, I3Frame::Stream)
Put(I3Frame {lvalue}, std::string, boost::shared_ptr<I3FrameObject const>)
```
while running SimulationFiltering.py from filterscripts/resources/scripts
I guess, the "None" needs to be wrapped to become an dataclasses.I3String or similar.
Migrated from https://code.icecube.wisc.edu/ticket/1950
```json
{
"status": "closed",
"changetime": "2017-02-20T09:08:11",
"description": "Hello,\n\nI am encountering this:\n{{{\nERROR (PythonFunction): Error running python function as module: (PythonFunction.cxx:173 in virtual void PythonFunction::Process())\nERROR (I3Module): OnlineL2_findBestSucceededFit: Exception thrown (I3Module.cxx:116 in void I3Module::Do(void (I3Module::*)()))\nTraceback (most recent call last):\n File \"/data/user/flauber/scripts/executables/SimulationFiltering.py\", line 412, in <module>\n main(opts)\n File \"/data/user/flauber/scripts/executables/SimulationFiltering.py\", line 371, in main\n tray.Execute()\n File \"/mnt/lfs3/user/flauber/software/icerec_V05-00-05/build/lib/I3Tray.py\", line 234, in Execute\n super(I3Tray, self).Execute()\n File \"/mnt/lfs3/user/flauber/software/icerec_V05-00-05/build/lib/icecube/filterscripts/onlinel2filter.py\", line 570, in findBestSucceededFit\n frame.Put(name+\"_BestFitName\", \"None\")\nBoost.Python.ArgumentError: Python argument types in\n I3Frame.Put(I3Frame, str, str)\ndid not match C++ signature:\n Put(I3Frame {lvalue}, std::string, boost::shared_ptr<I3FrameObject const>, I3Frame::Stream)\n Put(I3Frame {lvalue}, std::string, boost::shared_ptr<I3FrameObject const>)\n}}}\n\nwhile running SimulationFiltering.py from filterscripts/resources/scripts\n\nI guess, the \"None\" needs to be wrapped to become an dataclasses.I3String or similar.\n",
"reporter": "flauber",
"cc": "",
"resolution": "fixed",
"_ts": "1487581691387840",
"component": "combo reconstruction",
"summary": "[filterscripts] Exception if no best Fit was found",
"priority": "normal",
"keywords": "filterscripts",
"time": "2017-02-20T08:51:22",
"milestone": "",
"owner": "thomas.kintscher",
"type": "defect"
}
```
|
defect
|
exception if no best fit was found trac hello i am encountering this text error pythonfunction error running python function as module pythonfunction cxx in virtual void pythonfunction process error findbestsucceededfit exception thrown cxx in void do void traceback most recent call last file data user flauber scripts executables simulationfiltering py line in main opts file data user flauber scripts executables simulationfiltering py line in main tray execute file mnt user flauber software icerec build lib py line in execute super self execute file mnt user flauber software icerec build lib icecube filterscripts py line in findbestsucceededfit frame put name bestfitname none boost python argumenterror python argument types in put str str did not match c signature put lvalue std string boost shared ptr stream put lvalue std string boost shared ptr while running simulationfiltering py from filterscripts resources scripts i guess the none needs to be wrapped to become an dataclasses or similar migrated from json status closed changetime description hello n ni am encountering this n nerror pythonfunction error running python function as module pythonfunction cxx in virtual void pythonfunction process nerror findbestsucceededfit exception thrown cxx in void do void ntraceback most recent call last n file data user flauber scripts executables simulationfiltering py line in n main opts n file data user flauber scripts executables simulationfiltering py line in main n tray execute n file mnt user flauber software icerec build lib py line in execute n super self execute n file mnt user flauber software icerec build lib icecube filterscripts py line in findbestsucceededfit n frame put name bestfitname none nboost python argumenterror python argument types in n put str str ndid not match c signature n put lvalue std string boost shared ptr stream n put lvalue std string boost shared ptr n n nwhile running simulationfiltering py from filterscripts resources scripts n ni guess the none needs to be wrapped to become an dataclasses or similar n reporter flauber cc resolution fixed ts component combo reconstruction summary exception if no best fit was found priority normal keywords filterscripts time milestone owner thomas kintscher type defect
| 1
|
47,596
| 13,057,527,803
|
IssuesEvent
|
2020-07-30 07:30:20
|
LiskHQ/lisk-desktop
|
https://api.github.com/repos/LiskHQ/lisk-desktop
|
opened
|
Refactor unit tests to use shallow rendering in top level components
|
type: bug type: defect type: refactoring type: test
|
### Expected behavior
All top level components identified in #2967 should use shallow rendering.
### Actual behavior
Top level components render the entire component structure.
### Action Points
- All top level components should be refactored to use shallow rendering instead.
|
1.0
|
Refactor unit tests to use shallow rendering in top level components - ### Expected behavior
All top level components identified in #2967 should use shallow rendering.
### Actual behavior
Top level components render the entire component structure.
### Action Points
- All top level components should be refactored to use shallow rendering instead.
|
defect
|
refactor unit tests to use shallow rendering in top level components expected behavior all top level components identified in should use shallow rendering actual behavior top level components render the entire component structure action points all top level components should be refactored to use shallow rendering instead
| 1
|
58,960
| 16,978,832,703
|
IssuesEvent
|
2021-06-30 05:48:31
|
openzfs/zfs
|
https://api.github.com/repos/openzfs/zfs
|
opened
|
open() on a zvol dev node may fail with errno=ERESTARTSYS in userspace (observed with udev)
|
Status: Triage Needed Type: Defect
|
### System information
Type | Version/Name
--- | ---
Distribution Name | Arch Linux
Distribution Version | rolling release / 2021 Jun 28
Linux Kernel | 5.13
Architecture | x86_64
ZFS Version | 2.0.5-1
SPL Version | 2.0.5-1
(One thing I haven't actually done, is build zfs from the current git master and test with that. I'll try that ASAP. I don't think it'll necessarily change anything, but it did hit me as one of those "oh yeah I probably should do that" things.)
### The problem
At system startup right after pool import, or at any other time when a large number of zvol dev nodes pop into existence (e.g. when setting `snapdev=visible` on a volume dataset with many snapshots), a small random smattering of the `/dev/zvol/*` symlinks that are expected to be created, are missing. This is just the immediately user-noticeable symptom, though.
Adding the following udev rule to heighten the log level for zvol devices helps diagnose what's going on. You can throw this in as `/etc/udev/rules.d/00-debug.rules` and load it up at runtime via `udevadm control -R` if desired.
```
SUBSYSTEM=="block", KERNEL=="zd*", OPTIONS="log_level=debug"
```
The rule in `/usr/lib/udev/rules.d/60-zvol.rules` for creating the `/dev/zvol/*` symlinks includes a `PROGRAM` token which causes udev (systemd-udevd) to spawn an instance of `/usr/lib/udev/zvol_id` per `/dev/zd*` dev node. Many of these are run in parallel at once.
The debug logging rule shown above reveals that what's happening is that, occasionally and somewhat randomly, one of these `zvol_id` processes will not be able to successfully perform the `open("/dev/zdN", O_RDONLY)` syscall to open the dev node it was asked to identify. The syscall fails, and the value in `errno` after the failure is 512.
So... 512 isn't a valid userspace error value *at all*. I was fortunate to find that 512 corresponds to `ERESTARTSYS` in Linux kernel land. As far as I know, this is a Thing That Should Never Leak To Userspace. Yet, it has, for whatever reason. (Maybe something about the signal configuration in udev processes is unusual and allows for this? No idea.)
Anyway. My naive understanding is that if a syscall handler (such as `zvol_open`) returns `-ERESTARTSYS`, then the Linux kernel is supposed to automatically make things "just work" such that the thread doesn't exit back to userspace but instead makes a U-turn and auto-retries the syscall again. (Which, in this case, would serve the purpose of effecting a retry on some heavily contended locks.) And so in principle, glibc shouldn't have to do any magic; and the program itself shouldn't have to do some sort of `EINTR` loop. And, at least if things work as intended, no `ERESTARTSYS` 512 values should be seen on the userspace side. (Yet, here we are.)
It should also be noted that other udev-spawned programs (e.g. `udisks-part-id`) also occasionally encountered the exact same syscall error with the same `ERESTARTSYS` error; often well-correlated with the failure in `zvol_id`, presumably due to both programs running at nearly the same time and both facing similar lock contention.
I did hack around with the `zvol_id` program, and experimented with putting the `open` syscall into a loop that would retry on failure `if (errno == 512)`. I put number-of-tries printouts to stderr in that loop, and I found that the `open` call would eventually succeed; but generally after something on the order of 20-400 retries. (Probably would fare better with some kind of sleep call in between, but ehhh.)
I do half-wonder if the reorganization that happened in 5df7e9d85ced424292e8312a7848b6092a29c930 has anything to do with this issue: prior to that commit, `zvol_first_open` would directly `return (-SET_ERROR(ERESTARTSYS));`, whereas after the commit, `zvol_first_open` (in one file) does `return (SET_ERROR(EINTR));` while `zvol_open` (in a different file) does some `-EINTR` to `-ERESTARTSYS` stuff. Doesn't seem like the whole story by any means, but possibly a complicating factor.
I also wonder if there was some internal change to how the Linux kernel does its `ERESTARTSYS` magic, perhaps in 5.12. I haven't been able to actually track down where that logic is located, at the moment; I think it used to be in one particular file, but has since been moved to some other file; and my on-the-fly kretprobes knowledge apparently isn't good enough to figure out how to just print out a damn stack trace whenever `zvol_first_open` returns `-EINTR`.
### Other issues and PRs of similarity or relevance
- #612: Ancient issue concerning deadlocks when using zvols as vdevs (for whatever pathological reason someone would want to do such a thing); resolved by 65d56083b4617a4cade0cff68cbbaf68114169d6 which originally introduced the `-ERESTARTSYS` mechanism to `zvol_first_open`
- #1220: PR a month after the above, tweaking the code a bit
- #6283: Issue concerning deadlocks on 1-CPU systems due to endless `-ERESTARTSYS` retries without any possibility for task switching to take place and resolve the lock situation
- #6312: PR fixing the above issue by adding the explicit `schedule()` call in the `-ERESTARTSYS` case
- #7773: Issue concerning lock contention and `-ERESTARTSYS` in `zvol_open` (never resolved, closed as stale)
### Information that might kinda help reproduce the problem maybe perhaps
I don't know if I have any specific reliable way to reproduce the problem.
The best I can say is that my pool has a lot of zvols (dozens to hundreds, particularly when `snapdev=visible`), and that I see this pretty consistently whenever a bunch of `/dev/zd*` nodes come into existence at the same time and make systemd-udevd spin up a crapton of workers that all attempt to access some large number of those dev nodes at the same time (undoubtedly running into some degree of lock contention).
I don't do any exotic things like attempting to build nested zfs contraptions involving using zvols as vdevs. (I generally regard myself as a sane person.)
I use a custom kernel that has, among other things, `CONFIG_PREEMPT=y` and `CONFIG_HZ=1000`. The involuntary preemption thing could be relevant; not entirely sure, to be honest.
This has been happening on an SMP system with multiple cores (AMD FX-8350).
If it's of any interest, I'm currently running systemd/udev version 249rc2. I believe this was happening on 248.3 as well, and possibly prior to that. I'm 95% sure I was also seeing this behavior back on kernel 5.12.2 (at which time I was using zfs 2babd2004).
Oh yeah and I guess that little udev rule file I posted earlier that enables debug log_level for `/dev/zd*` dev nodes is probably a handy thing to have around if you're trying to reproduce this.
### Logs of interest
Nothing of particular note shows up in `/proc/spl/kstat/zfs/dbgmsg` (with `zfs_flags=1`).
What I've posted below, however, is some interesting udev `log_level=debug` output from the journal, isolated out for one particular zvol device that had difficulty when I switched `snapdev=hidden` to `snapdev=visible` on a particular volume.
In this case I was using an unmodified `zvol_id` binary that didn't have any printouts added to indicate e.g. what `errno` was; but you can see it from the `udisks-part-id` invocation that also failed on the `open` syscall.
```
systemd-udevd[3765278]: zd736: The log level is changed to 'debug' while processing device (SEQNUM=8400, ACTION=add)
systemd-udevd[3765278]: zd736: /usr/lib/udev/rules.d/50-udev-default.rules:69 GROUP 6
systemd-udevd[3765278]: zd736: /usr/lib/udev/rules.d/60-zvol.rules:6 Running PROGRAM '/usr/lib/udev/zvol_id /dev/zd736'
systemd-udevd[3765278]: zd736: Starting '/usr/lib/udev/zvol_id /dev/zd736'
systemd-udevd[3765278]: Successfully forked off '(spawn)' as PID 3765289.
systemd-udevd[3765278]: zd736: '/usr/lib/udev/zvol_id /dev/zd736'(out) 'Unable to open device file: /dev/zd736'
systemd-udevd[3765278]: zd736: Process '/usr/lib/udev/zvol_id /dev/zd736' succeeded.
systemd-udevd[3765278]: zd736: /usr/lib/udev/rules.d/60-zvol.rules:6 LINK 'zvol/Unable'
systemd-udevd[3765278]: zd736: /usr/lib/udev/rules.d/60-zvol.rules:6 LINK 'to'
systemd-udevd[3765278]: zd736: /usr/lib/udev/rules.d/60-zvol.rules:6 LINK 'open'
systemd-udevd[3765278]: zd736: /usr/lib/udev/rules.d/60-zvol.rules:6 LINK 'device'
systemd-udevd[3765278]: zd736: /usr/lib/udev/rules.d/60-zvol.rules:6 LINK 'file:'
systemd-udevd[3765278]: zd736: /usr/lib/udev/rules.d/60-zvol.rules:6 LINK '/dev/zd736'
systemd-udevd[3765278]: zd736: /usr/lib/udev/rules.d/80-udisks.rules:84 Importing properties from results of 'udisks-part-id /dev/zd736'
systemd-udevd[3765278]: zd736: Starting 'udisks-part-id /dev/zd736'
systemd-udevd[3765278]: Successfully forked off '(spawn)' as PID 3765294.
systemd-udevd[3765278]: zd736: 'udisks-part-id /dev/zd736'(err) 'using device_file=/dev/zd736 syspath=/sys/devices/virtual/block/zd736, offset=0 ao=0 and number=0 for /dev/zd736'
systemd-udevd[3765278]: zd736: 'udisks-part-id /dev/zd736'(err) 'Error opening /dev/zd736: Unknown error 512'
systemd-udevd[3765278]: zd736: Process 'udisks-part-id /dev/zd736' succeeded.
systemd-udevd[3765278]: zd736: Handling device node '/dev/zd736', devnum=b230:736
systemd-udevd[3765278]: zd736: Setting permissions /dev/zd736, uid=0, gid=6, mode=0660
systemd-udevd[3765278]: zd736: Found 'b230:736' claiming '/run/udev/links/file:'
systemd-udevd[3765278]: zd736: Creating symlink '/dev/file:' to 'zd736'
systemd-udevd[3765278]: zd736: Found 'b230:736' claiming '/run/udev/links/open'
systemd-udevd[3765278]: zd736: Creating symlink '/dev/open' to 'zd736'
systemd-udevd[3765278]: zd736: Found 'b230:736' claiming '/run/udev/links/zvol\x2fUnable'
systemd-udevd[3765278]: zd736: Creating symlink '/dev/zvol/Unable' to '../zd736'
systemd-udevd[3765278]: zd736: Found 'b230:736' claiming '/run/udev/links/to'
systemd-udevd[3765278]: zd736: Creating symlink '/dev/to' to 'zd736'
systemd-udevd[3765278]: zd736: Found 'b230:736' claiming '/run/udev/links/dev\x2fzd736'
systemd-udevd[3765278]: zd736: Creating symlink '/dev/dev/zd736' to '../zd736'
systemd-udevd[3765278]: zd736: Found 'b230:736' claiming '/run/udev/links/device'
systemd-udevd[3765278]: zd736: Creating symlink '/dev/device' to 'zd736'
systemd-udevd[3765278]: zd736: Creating symlink '/dev/block/230:736' to '../zd736'
systemd-udevd[3765278]: zd736: sd-device: Created db file '/run/udev/data/b230:736' for '/devices/virtual/block/zd736'
systemd-udevd[3765278]: zd736: Handling device node '/dev/zd736', devnum=b230:736
systemd-udevd[3765278]: zd736: Preserve permissions of /dev/zd736, uid=0, gid=6, mode=0660
systemd-udevd[3765278]: zd736: Found 'b230:736' claiming '/run/udev/links/file:'
systemd-udevd[3765278]: zd736: Preserve already existing symlink '/dev/file:' to 'zd736'
systemd-udevd[3765278]: zd736: Found 'b230:736' claiming '/run/udev/links/open'
systemd-udevd[3765278]: zd736: Preserve already existing symlink '/dev/open' to 'zd736'
systemd-udevd[3765278]: zd736: Found 'b230:736' claiming '/run/udev/links/zvol\x2fUnable'
systemd-udevd[3765278]: zd736: Preserve already existing symlink '/dev/zvol/Unable' to '../zd736'
systemd-udevd[3765278]: zd736: Found 'b230:736' claiming '/run/udev/links/to'
systemd-udevd[3765278]: zd736: Preserve already existing symlink '/dev/to' to 'zd736'
systemd-udevd[3765278]: zd736: Found 'b230:736' claiming '/run/udev/links/dev\x2fzd736'
systemd-udevd[3765278]: zd736: Preserve already existing symlink '/dev/dev/zd736' to '../zd736'
systemd-udevd[3765278]: zd736: Found 'b230:736' claiming '/run/udev/links/device'
systemd-udevd[3765278]: zd736: Preserve already existing symlink '/dev/device' to 'zd736'
systemd-udevd[3765278]: zd736: Preserve already existing symlink '/dev/block/230:736' to '../zd736'
systemd-udevd[3765278]: zd736: Adding watch on '/dev/zd736'
systemd-udevd[3765278]: zd736: Device processed (SEQNUM=8400, ACTION=add)
systemd-udevd[3765278]: zd736: sd-device-monitor: Passed 757 byte to netlink monitor
```
### In case you read the log above and are now thinking "wtf are those symlinks?!"
In the log sequence posted above, it's hard not to notice that another idiotic thing is going on. Because there's some goofs in the udev rules file and in `zvol_id`, the nonzero exit status of 512 from `zvol_id` is modulo'd into 0, which of course is then treated as a "success", meaning that the contents of `stdout` are not ignored, but are consumed normally (as if they were the name of the `/dev/zvol/*` symlink to create). And then `zvol_id`, for reasons I don't particularly understand, only ever prints stuff (including its error messages) to stdout; combine that with the wonders of space-separated list syntax, and you wind up with udev deciding that the rules are requesting that the following symlinks be created:
```
/dev/zvol/Unable -> /dev/zd736
/dev/to -> /dev/zd736
/dev/open -> /dev/zd736
/dev/device -> /dev/zd736
/dev/file: -> /dev/zd736
/dev//dev/zd736 -> /dev/zd736
```
(I plan to address this in a separate PR that I have pretty much all lined up and ready to go already. The `60-zvol.rules` file is extremely ancient; like, it's literally a decade old. And it uses a fairly impressive number of deprecated syntax quirks for a mere one-liner file. Most of the code for `zvol_id` is about a decade old as well, and does dumb stuff like printing error messages to stdout. So yeah, I'll be taking care of all of this particular dumbness myself shortly. That PR will fix the bizarre symlinks symptom that's been going on; but it doesn't do anything to address the core mystery of "why the hell are these `zvol_open` calls failing, and in such a way that `errno=ERESTARTSYS` is getting to userspace?")
### Stuff I can do to help
If this issue turns out to be a giant pain to reproduce, I'm happy to do stuff like flipping on `zfs_flags` bits, dumping various logs, adding extra debug printouts in particular places, creating/building/running custom one-off builds of the zfs module that I use on my personal system with my actual data with reckless abandon; basically whatever helps track this down. 😄
|
1.0
|
open() on a zvol dev node may fail with errno=ERESTARTSYS in userspace (observed with udev) - ### System information
Type | Version/Name
--- | ---
Distribution Name | Arch Linux
Distribution Version | rolling release / 2021 Jun 28
Linux Kernel | 5.13
Architecture | x86_64
ZFS Version | 2.0.5-1
SPL Version | 2.0.5-1
(One thing I haven't actually done, is build zfs from the current git master and test with that. I'll try that ASAP. I don't think it'll necessarily change anything, but it did hit me as one of those "oh yeah I probably should do that" things.)
### The problem
At system startup right after pool import, or at any other time when a large number of zvol dev nodes pop into existence (e.g. when setting `snapdev=visible` on a volume dataset with many snapshots), a small random smattering of the `/dev/zvol/*` symlinks that are expected to be created, are missing. This is just the immediately user-noticeable symptom, though.
Adding the following udev rule to heighten the log level for zvol devices helps diagnose what's going on. You can throw this in as `/etc/udev/rules.d/00-debug.rules` and load it up at runtime via `udevadm control -R` if desired.
```
SUBSYSTEM=="block", KERNEL=="zd*", OPTIONS="log_level=debug"
```
The rule in `/usr/lib/udev/rules.d/60-zvol.rules` for creating the `/dev/zvol/*` symlinks includes a `PROGRAM` token which causes udev (systemd-udevd) to spawn an instance of `/usr/lib/udev/zvol_id` per `/dev/zd*` dev node. Many of these are run in parallel at once.
The debug logging rule shown above reveals that what's happening is that, occasionally and somewhat randomly, one of these `zvol_id` processes will not be able to successfully perform the `open("/dev/zdN", O_RDONLY)` syscall to open the dev node it was asked to identify. The syscall fails, and the value in `errno` after the failure is 512.
So... 512 isn't a valid userspace error value *at all*. I was fortunate to find that 512 corresponds to `ERESTARTSYS` in Linux kernel land. As far as I know, this is a Thing That Should Never Leak To Userspace. Yet, it has, for whatever reason. (Maybe something about the signal configuration in udev processes is unusual and allows for this? No idea.)
Anyway. My naive understanding is that if a syscall handler (such as `zvol_open`) returns `-ERESTARTSYS`, then the Linux kernel is supposed to automatically make things "just work" such that the thread doesn't exit back to userspace but instead makes a U-turn and auto-retries the syscall again. (Which, in this case, would serve the purpose of effecting a retry on some heavily contended locks.) And so in principle, glibc shouldn't have to do any magic; and the program itself shouldn't have to do some sort of `EINTR` loop. And, at least if things work as intended, no `ERESTARTSYS` 512 values should be seen on the userspace side. (Yet, here we are.)
It should also be noted that other udev-spawned programs (e.g. `udisks-part-id`) also occasionally encountered the exact same syscall error with the same `ERESTARTSYS` error; often well-correlated with the failure in `zvol_id`, presumably due to both programs running at nearly the same time and both facing similar lock contention.
I did hack around with the `zvol_id` program, and experimented with putting the `open` syscall into a loop that would retry on failure `if (errno == 512)`. I put number-of-tries printouts to stderr in that loop, and I found that the `open` call would eventually succeed; but generally after something on the order of 20-400 retries. (Probably would fare better with some kind of sleep call in between, but ehhh.)
I do half-wonder if the reorganization that happened in 5df7e9d85ced424292e8312a7848b6092a29c930 has anything to do with this issue: prior to that commit, `zvol_first_open` would directly `return (-SET_ERROR(ERESTARTSYS));`, whereas after the commit, `zvol_first_open` (in one file) does `return (SET_ERROR(EINTR));` while `zvol_open` (in a different file) does some `-EINTR` to `-ERESTARTSYS` stuff. Doesn't seem like the whole story by any means, but possibly a complicating factor.
I also wonder if there was some internal change to how the Linux kernel does its `ERESTARTSYS` magic, perhaps in 5.12. I haven't been able to actually track down where that logic is located, at the moment; I think it used to be in one particular file, but has since been moved to some other file; and my on-the-fly kretprobes knowledge apparently isn't good enough to figure out how to just print out a damn stack trace whenever `zvol_first_open` returns `-EINTR`.
### Other issues and PRs of similarity or relevance
- #612: Ancient issue concerning deadlocks when using zvols as vdevs (for whatever pathological reason someone would want to do such a thing); resolved by 65d56083b4617a4cade0cff68cbbaf68114169d6 which originally introduced the `-ERESTARTSYS` mechanism to `zvol_first_open`
- #1220: PR a month after the above, tweaking the code a bit
- #6283: Issue concerning deadlocks on 1-CPU systems due to endless `-ERESTARTSYS` retries without any possibility for task switching to take place and resolve the lock situation
- #6312: PR fixing the above issue by adding the explicit `schedule()` call in the `-ERESTARTSYS` case
- #7773: Issue concerning lock contention and `-ERESTARTSYS` in `zvol_open` (never resolved, closed as stale)
### Information that might kinda help reproduce the problem maybe perhaps
I don't know if I have any specific reliable way to reproduce the problem.
The best I can say is that my pool has a lot of zvols (dozens to hundreds, particularly when `snapdev=visible`), and that I see this pretty consistently whenever a bunch of `/dev/zd*` nodes come into existence at the same time and make systemd-udevd spin up a crapton of workers that all attempt to access some large number of those dev nodes at the same time (undoubtedly running into some degree of lock contention).
I don't do any exotic things like attempting to build nested zfs contraptions involving using zvols as vdevs. (I generally regard myself as a sane person.)
I use a custom kernel that has, among other things, `CONFIG_PREEMPT=y` and `CONFIG_HZ=1000`. The involuntary preemption thing could be relevant; not entirely sure, to be honest.
This has been happening on an SMP system with multiple cores (AMD FX-8350).
If it's of any interest, I'm currently running systemd/udev version 249rc2. I believe this was happening on 248.3 as well, and possibly prior to that. I'm 95% sure I was also seeing this behavior back on kernel 5.12.2 (at which time I was using zfs 2babd2004).
Oh yeah and I guess that little udev rule file I posted earlier that enables debug log_level for `/dev/zd*` dev nodes is probably a handy thing to have around if you're trying to reproduce this.
### Logs of interest
Nothing of particular note shows up in `/proc/spl/kstat/zfs/dbgmsg` (with `zfs_flags=1`).
What I've posted below, however, is some interesting udev `log_level=debug` output from the journal, isolated out for one particular zvol device that had difficulty when I switched `snapdev=hidden` to `snapdev=visible` on a particular volume.
In this case I was using an unmodified `zvol_id` binary that didn't have any printouts added to indicate e.g. what `errno` was; but you can see it from the `udisks-part-id` invocation that also failed on the `open` syscall.
```
systemd-udevd[3765278]: zd736: The log level is changed to 'debug' while processing device (SEQNUM=8400, ACTION=add)
systemd-udevd[3765278]: zd736: /usr/lib/udev/rules.d/50-udev-default.rules:69 GROUP 6
systemd-udevd[3765278]: zd736: /usr/lib/udev/rules.d/60-zvol.rules:6 Running PROGRAM '/usr/lib/udev/zvol_id /dev/zd736'
systemd-udevd[3765278]: zd736: Starting '/usr/lib/udev/zvol_id /dev/zd736'
systemd-udevd[3765278]: Successfully forked off '(spawn)' as PID 3765289.
systemd-udevd[3765278]: zd736: '/usr/lib/udev/zvol_id /dev/zd736'(out) 'Unable to open device file: /dev/zd736'
systemd-udevd[3765278]: zd736: Process '/usr/lib/udev/zvol_id /dev/zd736' succeeded.
systemd-udevd[3765278]: zd736: /usr/lib/udev/rules.d/60-zvol.rules:6 LINK 'zvol/Unable'
systemd-udevd[3765278]: zd736: /usr/lib/udev/rules.d/60-zvol.rules:6 LINK 'to'
systemd-udevd[3765278]: zd736: /usr/lib/udev/rules.d/60-zvol.rules:6 LINK 'open'
systemd-udevd[3765278]: zd736: /usr/lib/udev/rules.d/60-zvol.rules:6 LINK 'device'
systemd-udevd[3765278]: zd736: /usr/lib/udev/rules.d/60-zvol.rules:6 LINK 'file:'
systemd-udevd[3765278]: zd736: /usr/lib/udev/rules.d/60-zvol.rules:6 LINK '/dev/zd736'
systemd-udevd[3765278]: zd736: /usr/lib/udev/rules.d/80-udisks.rules:84 Importing properties from results of 'udisks-part-id /dev/zd736'
systemd-udevd[3765278]: zd736: Starting 'udisks-part-id /dev/zd736'
systemd-udevd[3765278]: Successfully forked off '(spawn)' as PID 3765294.
systemd-udevd[3765278]: zd736: 'udisks-part-id /dev/zd736'(err) 'using device_file=/dev/zd736 syspath=/sys/devices/virtual/block/zd736, offset=0 ao=0 and number=0 for /dev/zd736'
systemd-udevd[3765278]: zd736: 'udisks-part-id /dev/zd736'(err) 'Error opening /dev/zd736: Unknown error 512'
systemd-udevd[3765278]: zd736: Process 'udisks-part-id /dev/zd736' succeeded.
systemd-udevd[3765278]: zd736: Handling device node '/dev/zd736', devnum=b230:736
systemd-udevd[3765278]: zd736: Setting permissions /dev/zd736, uid=0, gid=6, mode=0660
systemd-udevd[3765278]: zd736: Found 'b230:736' claiming '/run/udev/links/file:'
systemd-udevd[3765278]: zd736: Creating symlink '/dev/file:' to 'zd736'
systemd-udevd[3765278]: zd736: Found 'b230:736' claiming '/run/udev/links/open'
systemd-udevd[3765278]: zd736: Creating symlink '/dev/open' to 'zd736'
systemd-udevd[3765278]: zd736: Found 'b230:736' claiming '/run/udev/links/zvol\x2fUnable'
systemd-udevd[3765278]: zd736: Creating symlink '/dev/zvol/Unable' to '../zd736'
systemd-udevd[3765278]: zd736: Found 'b230:736' claiming '/run/udev/links/to'
systemd-udevd[3765278]: zd736: Creating symlink '/dev/to' to 'zd736'
systemd-udevd[3765278]: zd736: Found 'b230:736' claiming '/run/udev/links/dev\x2fzd736'
systemd-udevd[3765278]: zd736: Creating symlink '/dev/dev/zd736' to '../zd736'
systemd-udevd[3765278]: zd736: Found 'b230:736' claiming '/run/udev/links/device'
systemd-udevd[3765278]: zd736: Creating symlink '/dev/device' to 'zd736'
systemd-udevd[3765278]: zd736: Creating symlink '/dev/block/230:736' to '../zd736'
systemd-udevd[3765278]: zd736: sd-device: Created db file '/run/udev/data/b230:736' for '/devices/virtual/block/zd736'
systemd-udevd[3765278]: zd736: Handling device node '/dev/zd736', devnum=b230:736
systemd-udevd[3765278]: zd736: Preserve permissions of /dev/zd736, uid=0, gid=6, mode=0660
systemd-udevd[3765278]: zd736: Found 'b230:736' claiming '/run/udev/links/file:'
systemd-udevd[3765278]: zd736: Preserve already existing symlink '/dev/file:' to 'zd736'
systemd-udevd[3765278]: zd736: Found 'b230:736' claiming '/run/udev/links/open'
systemd-udevd[3765278]: zd736: Preserve already existing symlink '/dev/open' to 'zd736'
systemd-udevd[3765278]: zd736: Found 'b230:736' claiming '/run/udev/links/zvol\x2fUnable'
systemd-udevd[3765278]: zd736: Preserve already existing symlink '/dev/zvol/Unable' to '../zd736'
systemd-udevd[3765278]: zd736: Found 'b230:736' claiming '/run/udev/links/to'
systemd-udevd[3765278]: zd736: Preserve already existing symlink '/dev/to' to 'zd736'
systemd-udevd[3765278]: zd736: Found 'b230:736' claiming '/run/udev/links/dev\x2fzd736'
systemd-udevd[3765278]: zd736: Preserve already existing symlink '/dev/dev/zd736' to '../zd736'
systemd-udevd[3765278]: zd736: Found 'b230:736' claiming '/run/udev/links/device'
systemd-udevd[3765278]: zd736: Preserve already existing symlink '/dev/device' to 'zd736'
systemd-udevd[3765278]: zd736: Preserve already existing symlink '/dev/block/230:736' to '../zd736'
systemd-udevd[3765278]: zd736: Adding watch on '/dev/zd736'
systemd-udevd[3765278]: zd736: Device processed (SEQNUM=8400, ACTION=add)
systemd-udevd[3765278]: zd736: sd-device-monitor: Passed 757 byte to netlink monitor
```
### In case you read the log above and are now thinking "wtf are those symlinks?!"
In the log sequence posted above, it's hard not to notice that another idiotic thing is going on. Because there's some goofs in the udev rules file and in `zvol_id`, the nonzero exit status of 512 from `zvol_id` is modulo'd into 0, which of course is then treated as a "success", meaning that the contents of `stdout` are not ignored, but are consumed normally (as if they were the name of the `/dev/zvol/*` symlink to create). And then `zvol_id`, for reasons I don't particularly understand, only ever prints stuff (including its error messages) to stdout; combine that with the wonders of space-separated list syntax, and you wind up with udev deciding that the rules are requesting that the following symlinks be created:
```
/dev/zvol/Unable -> /dev/zd736
/dev/to -> /dev/zd736
/dev/open -> /dev/zd736
/dev/device -> /dev/zd736
/dev/file: -> /dev/zd736
/dev//dev/zd736 -> /dev/zd736
```
(I plan to address this in a separate PR that I have pretty much all lined up and ready to go already. The `60-zvol.rules` file is extremely ancient; like, it's literally a decade old. And it uses a fairly impressive number of deprecated syntax quirks for a mere one-liner file. Most of the code for `zvol_id` is about a decade old as well, and does dumb stuff like printing error messages to stdout. So yeah, I'll be taking care of all of this particular dumbness myself shortly. That PR will fix the bizarre symlinks symptom that's been going on; but it doesn't do anything to address the core mystery of "why the hell are these `zvol_open` calls failing, and in such a way that `errno=ERESTARTSYS` is getting to userspace?")
### Stuff I can do to help
If this issue turns out to be a giant pain to reproduce, I'm happy to do stuff like flipping on `zfs_flags` bits, dumping various logs, adding extra debug printouts in particular places, creating/building/running custom one-off builds of the zfs module that I use on my personal system with my actual data with reckless abandon; basically whatever helps track this down. 😄
|
defect
|
open on a zvol dev node may fail with errno erestartsys in userspace observed with udev system information type version name distribution name arch linux distribution version rolling release jun linux kernel architecture zfs version spl version one thing i haven t actually done is build zfs from the current git master and test with that i ll try that asap i don t think it ll necessarily change anything but it did hit me as one of those oh yeah i probably should do that things the problem at system startup right after pool import or at any other time when a large number of zvol dev nodes pop into existence e g when setting snapdev visible on a volume dataset with many snapshots a small random smattering of the dev zvol symlinks that are expected to be created are missing this is just the immediately user noticeable symptom though adding the following udev rule to heighten the log level for zvol devices helps diagnose what s going on you can throw this in as etc udev rules d debug rules and load it up at runtime via udevadm control r if desired subsystem block kernel zd options log level debug the rule in usr lib udev rules d zvol rules for creating the dev zvol symlinks includes a program token which causes udev systemd udevd to spawn an instance of usr lib udev zvol id per dev zd dev node many of these are run in parallel at once the debug logging rule shown above reveals that what s happening is that occasionally and somewhat randomly one of these zvol id processes will not be able to successfully perform the open dev zdn o rdonly syscall to open the dev node it was asked to identify the syscall fails and the value in errno after the failure is so isn t a valid userspace error value at all i was fortunate to find that corresponds to erestartsys in linux kernel land as far as i know this is a thing that should never leak to userspace yet it has for whatever reason maybe something about the signal configuration in udev processes is unusual and allows for this no idea anyway my naive understanding is that if a syscall handler such as zvol open returns erestartsys then the linux kernel is supposed to automatically make things just work such that the thread doesn t exit back to userspace but instead makes a u turn and auto retries the syscall again which in this case would serve the purpose of effecting a retry on some heavily contended locks and so in principle glibc shouldn t have to do any magic and the program itself shouldn t have to do some sort of eintr loop and at least if things work as intended no erestartsys values should be seen on the userspace side yet here we are it should also be noted that other udev spawned programs e g udisks part id also occasionally encountered the exact same syscall error with the same erestartsys error often well correlated with the failure in zvol id presumably due to both programs running at nearly the same time and both facing similar lock contention i did hack around with the zvol id program and experimented with putting the open syscall into a loop that would retry on failure if errno i put number of tries printouts to stderr in that loop and i found that the open call would eventually succeed but generally after something on the order of retries probably would fare better with some kind of sleep call in between but ehhh i do half wonder if the reorganization that happened in has anything to do with this issue prior to that commit zvol first open would directly return set error erestartsys whereas after the commit zvol first open in one file does return set error eintr while zvol open in a different file does some eintr to erestartsys stuff doesn t seem like the whole story by any means but possibly a complicating factor i also wonder if there was some internal change to how the linux kernel does its erestartsys magic perhaps in i haven t been able to actually track down where that logic is located at the moment i think it used to be in one particular file but has since been moved to some other file and my on the fly kretprobes knowledge apparently isn t good enough to figure out how to just print out a damn stack trace whenever zvol first open returns eintr other issues and prs of similarity or relevance ancient issue concerning deadlocks when using zvols as vdevs for whatever pathological reason someone would want to do such a thing resolved by which originally introduced the erestartsys mechanism to zvol first open pr a month after the above tweaking the code a bit issue concerning deadlocks on cpu systems due to endless erestartsys retries without any possibility for task switching to take place and resolve the lock situation pr fixing the above issue by adding the explicit schedule call in the erestartsys case issue concerning lock contention and erestartsys in zvol open never resolved closed as stale information that might kinda help reproduce the problem maybe perhaps i don t know if i have any specific reliable way to reproduce the problem the best i can say is that my pool has a lot of zvols dozens to hundreds particularly when snapdev visible and that i see this pretty consistently whenever a bunch of dev zd nodes come into existence at the same time and make systemd udevd spin up a crapton of workers that all attempt to access some large number of those dev nodes at the same time undoubtedly running into some degree of lock contention i don t do any exotic things like attempting to build nested zfs contraptions involving using zvols as vdevs i generally regard myself as a sane person i use a custom kernel that has among other things config preempt y and config hz the involuntary preemption thing could be relevant not entirely sure to be honest this has been happening on an smp system with multiple cores amd fx if it s of any interest i m currently running systemd udev version i believe this was happening on as well and possibly prior to that i m sure i was also seeing this behavior back on kernel at which time i was using zfs oh yeah and i guess that little udev rule file i posted earlier that enables debug log level for dev zd dev nodes is probably a handy thing to have around if you re trying to reproduce this logs of interest nothing of particular note shows up in proc spl kstat zfs dbgmsg with zfs flags what i ve posted below however is some interesting udev log level debug output from the journal isolated out for one particular zvol device that had difficulty when i switched snapdev hidden to snapdev visible on a particular volume in this case i was using an unmodified zvol id binary that didn t have any printouts added to indicate e g what errno was but you can see it from the udisks part id invocation that also failed on the open syscall systemd udevd the log level is changed to debug while processing device seqnum action add systemd udevd usr lib udev rules d udev default rules group systemd udevd usr lib udev rules d zvol rules running program usr lib udev zvol id dev systemd udevd starting usr lib udev zvol id dev systemd udevd successfully forked off spawn as pid systemd udevd usr lib udev zvol id dev out unable to open device file dev systemd udevd process usr lib udev zvol id dev succeeded systemd udevd usr lib udev rules d zvol rules link zvol unable systemd udevd usr lib udev rules d zvol rules link to systemd udevd usr lib udev rules d zvol rules link open systemd udevd usr lib udev rules d zvol rules link device systemd udevd usr lib udev rules d zvol rules link file systemd udevd usr lib udev rules d zvol rules link dev systemd udevd usr lib udev rules d udisks rules importing properties from results of udisks part id dev systemd udevd starting udisks part id dev systemd udevd successfully forked off spawn as pid systemd udevd udisks part id dev err using device file dev syspath sys devices virtual block offset ao and number for dev systemd udevd udisks part id dev err error opening dev unknown error systemd udevd process udisks part id dev succeeded systemd udevd handling device node dev devnum systemd udevd setting permissions dev uid gid mode systemd udevd found claiming run udev links file systemd udevd creating symlink dev file to systemd udevd found claiming run udev links open systemd udevd creating symlink dev open to systemd udevd found claiming run udev links zvol systemd udevd creating symlink dev zvol unable to systemd udevd found claiming run udev links to systemd udevd creating symlink dev to to systemd udevd found claiming run udev links dev systemd udevd creating symlink dev dev to systemd udevd found claiming run udev links device systemd udevd creating symlink dev device to systemd udevd creating symlink dev block to systemd udevd sd device created db file run udev data for devices virtual block systemd udevd handling device node dev devnum systemd udevd preserve permissions of dev uid gid mode systemd udevd found claiming run udev links file systemd udevd preserve already existing symlink dev file to systemd udevd found claiming run udev links open systemd udevd preserve already existing symlink dev open to systemd udevd found claiming run udev links zvol systemd udevd preserve already existing symlink dev zvol unable to systemd udevd found claiming run udev links to systemd udevd preserve already existing symlink dev to to systemd udevd found claiming run udev links dev systemd udevd preserve already existing symlink dev dev to systemd udevd found claiming run udev links device systemd udevd preserve already existing symlink dev device to systemd udevd preserve already existing symlink dev block to systemd udevd adding watch on dev systemd udevd device processed seqnum action add systemd udevd sd device monitor passed byte to netlink monitor in case you read the log above and are now thinking wtf are those symlinks in the log sequence posted above it s hard not to notice that another idiotic thing is going on because there s some goofs in the udev rules file and in zvol id the nonzero exit status of from zvol id is modulo d into which of course is then treated as a success meaning that the contents of stdout are not ignored but are consumed normally as if they were the name of the dev zvol symlink to create and then zvol id for reasons i don t particularly understand only ever prints stuff including its error messages to stdout combine that with the wonders of space separated list syntax and you wind up with udev deciding that the rules are requesting that the following symlinks be created dev zvol unable dev dev to dev dev open dev dev device dev dev file dev dev dev dev i plan to address this in a separate pr that i have pretty much all lined up and ready to go already the zvol rules file is extremely ancient like it s literally a decade old and it uses a fairly impressive number of deprecated syntax quirks for a mere one liner file most of the code for zvol id is about a decade old as well and does dumb stuff like printing error messages to stdout so yeah i ll be taking care of all of this particular dumbness myself shortly that pr will fix the bizarre symlinks symptom that s been going on but it doesn t do anything to address the core mystery of why the hell are these zvol open calls failing and in such a way that errno erestartsys is getting to userspace stuff i can do to help if this issue turns out to be a giant pain to reproduce i m happy to do stuff like flipping on zfs flags bits dumping various logs adding extra debug printouts in particular places creating building running custom one off builds of the zfs module that i use on my personal system with my actual data with reckless abandon basically whatever helps track this down 😄
| 1
|
18,844
| 3,089,693,698
|
IssuesEvent
|
2015-08-25 23:03:48
|
google/googlemock
|
https://api.github.com/repos/google/googlemock
|
closed
|
looser throw specifier for
|
auto-migrated Priority-Medium Type-Defect
|
```
IMPORTANT NOTE: PLEASE send issues and requests to
http://groups.google.com/group/googlemock *instead of here*.
This issue tracker is NOT regularly monitored.
If you really need to create a new issue, please provide the information
asked for below.
What steps will reproduce the problem?
1. When I make mock a method with throw() specifier,
It is not built.
MOCK_METHOD0(fn, void() throw (exception));
2. The following error happens.
ClassNameTest.cpp:40 error: looser throw specifier for `virtual void ClassName::functionName()'
ClassName.h:20: error: overriding `virtual void ClassName::functionName() throw (std::exception)'
What is the expected output? What do you see instead?
Which version of Google Mock are you using? On what operating system?
Google Mock : v 1.7.0
Google Test : v 1.7.0
Please provide any additional information below.
```
Original issue reported on code.google.com by `cjw...@gmail.com` on 29 Jul 2014 at 11:50
|
1.0
|
looser throw specifier for - ```
IMPORTANT NOTE: PLEASE send issues and requests to
http://groups.google.com/group/googlemock *instead of here*.
This issue tracker is NOT regularly monitored.
If you really need to create a new issue, please provide the information
asked for below.
What steps will reproduce the problem?
1. When I make mock a method with throw() specifier,
It is not built.
MOCK_METHOD0(fn, void() throw (exception));
2. The following error happens.
ClassNameTest.cpp:40 error: looser throw specifier for `virtual void ClassName::functionName()'
ClassName.h:20: error: overriding `virtual void ClassName::functionName() throw (std::exception)'
What is the expected output? What do you see instead?
Which version of Google Mock are you using? On what operating system?
Google Mock : v 1.7.0
Google Test : v 1.7.0
Please provide any additional information below.
```
Original issue reported on code.google.com by `cjw...@gmail.com` on 29 Jul 2014 at 11:50
|
defect
|
looser throw specifier for important note please send issues and requests to instead of here this issue tracker is not regularly monitored if you really need to create a new issue please provide the information asked for below what steps will reproduce the problem when i make mock a method with throw specifier it is not built mock fn void throw exception the following error happens classnametest cpp error looser throw specifier for virtual void classname functionname classname h error overriding virtual void classname functionname throw std exception what is the expected output what do you see instead which version of google mock are you using on what operating system google mock v google test v please provide any additional information below original issue reported on code google com by cjw gmail com on jul at
| 1
|
30,816
| 14,674,623,736
|
IssuesEvent
|
2020-12-30 15:43:56
|
sergiorribeiro/webmetry
|
https://api.github.com/repos/sergiorribeiro/webmetry
|
opened
|
[Controller] Controller/api/v1/investment_report_document_sets/preview_totals
|
controller needs squad prodops transaction-performance
|
The transaction **`Controller/api/v1/investment_report_document_sets/preview_totals` (Controller)** violated a performance threshold.
## Violations:
- [2020-12-30] Maximum execution duration during the current week was exceeded. Duration: **`1.4 min`**. Limit: **`30 s`**. <!-- /// -->
## Weekly transaction performance:
### Evolution graph (percentile 95):
```
[2020-12-21] ~ [2020-12-28] 🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦 26.5 s
[2020-12-14] ~ [2020-12-21] 🟦🟦🟦🟦🟦⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️ 7.4 s
[2020-12-07] ~ [2020-12-14] 🟦🟦🟦🟦🟦⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️ 6.6 s
[2020-11-30] ~ [2020-12-07] 🟦🟦🟦🟦⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️ 5.6 s
```
### Weekly indicators:
| Indicator | Week -3 | Week -2 | Week -1 | Week 0 |
|-|-|-|-|-|
| Above average hits | 2 | 5 | 2 | 6 |
| Max | 1.6 min | 57.1 s | 49.4 s | 1.4 min |
| Average | 1.4 s | 1.6 s | 2.1 s | 4.0 s |
| Percentile 95 | 5.6 s | 6.6 s | 7.4 s | 26.5 s |
### Month totals:
| Indicator | Value |
|-|-|
| Max | 1.6 min |
| Average | 1.8 s |
| Percentile 95 | 6.6 s |
<!-- [EPID:7ea343ce7f54566e9bb049d39803cf5548e43654] -->
|
True
|
[Controller] Controller/api/v1/investment_report_document_sets/preview_totals - The transaction **`Controller/api/v1/investment_report_document_sets/preview_totals` (Controller)** violated a performance threshold.
## Violations:
- [2020-12-30] Maximum execution duration during the current week was exceeded. Duration: **`1.4 min`**. Limit: **`30 s`**. <!-- /// -->
## Weekly transaction performance:
### Evolution graph (percentile 95):
```
[2020-12-21] ~ [2020-12-28] 🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦 26.5 s
[2020-12-14] ~ [2020-12-21] 🟦🟦🟦🟦🟦⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️ 7.4 s
[2020-12-07] ~ [2020-12-14] 🟦🟦🟦🟦🟦⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️ 6.6 s
[2020-11-30] ~ [2020-12-07] 🟦🟦🟦🟦⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️ 5.6 s
```
### Weekly indicators:
| Indicator | Week -3 | Week -2 | Week -1 | Week 0 |
|-|-|-|-|-|
| Above average hits | 2 | 5 | 2 | 6 |
| Max | 1.6 min | 57.1 s | 49.4 s | 1.4 min |
| Average | 1.4 s | 1.6 s | 2.1 s | 4.0 s |
| Percentile 95 | 5.6 s | 6.6 s | 7.4 s | 26.5 s |
### Month totals:
| Indicator | Value |
|-|-|
| Max | 1.6 min |
| Average | 1.8 s |
| Percentile 95 | 6.6 s |
<!-- [EPID:7ea343ce7f54566e9bb049d39803cf5548e43654] -->
|
non_defect
|
controller api investment report document sets preview totals the transaction controller api investment report document sets preview totals controller violated a performance threshold violations maximum execution duration during the current week was exceeded duration min limit s weekly transaction performance evolution graph percentile 🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦🟦 s 🟦🟦🟦🟦🟦⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️ s 🟦🟦🟦🟦🟦⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️ s 🟦🟦🟦🟦⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️ s weekly indicators indicator week week week week above average hits max min s s min average s s s s percentile s s s s month totals indicator value max min average s percentile s
| 0
|
115,090
| 9,781,036,212
|
IssuesEvent
|
2019-06-07 18:35:35
|
dojot/dojot
|
https://api.github.com/repos/dojot/dojot
|
closed
|
[GUI] [Template] Metadata value type empty: the text was not translated
|
Epic: i18n Priority:Low Status:ToTest Team:Frontend Type:Bug
|
The text was not translated into Portuguese:

**Steps to reproduce the problem**:
1. Click "Novo Modelo"
2. Fill in template name
3. Click "Novo Atributo"
4. Fill in attribute name, attribute type, value type and value
5. Click "Novo Metadado"
6. Fill in attribute name and attribute type
7. Click "Adicionar"
**Note**: the text for empty attribute type has been translated
**Affected Version**: 58.2-20190321
|
1.0
|
[GUI] [Template] Metadata value type empty: the text was not translated - The text was not translated into Portuguese:

**Steps to reproduce the problem**:
1. Click "Novo Modelo"
2. Fill in template name
3. Click "Novo Atributo"
4. Fill in attribute name, attribute type, value type and value
5. Click "Novo Metadado"
6. Fill in attribute name and attribute type
7. Click "Adicionar"
**Note**: the text for empty attribute type has been translated
**Affected Version**: 58.2-20190321
|
non_defect
|
metadata value type empty the text was not translated the text was not translated into portuguese steps to reproduce the problem click novo modelo fill in template name click novo atributo fill in attribute name attribute type value type and value click novo metadado fill in attribute name and attribute type click adicionar note the text for empty attribute type has been translated affected version
| 0
|
65,558
| 19,572,968,455
|
IssuesEvent
|
2022-01-04 12:16:15
|
pymc-devs/pymc
|
https://api.github.com/repos/pymc-devs/pymc
|
opened
|
`pm.Data` silently missing from `InferenceData` when dims match the variable name
|
defects beginner friendly
|
Xarray, and thereby `InferenceData` don't support labeling dimensions with the same name as the variable.
```python
with pm.Model() as pmodel:
pm.Data("city", numpy.arange(5), dims="cities") # ✔ ends up in .constant_data as expected
pm.Data("time", numpy.arange(5), dims="time") # ❌ silently missing
pm.Normal("a") # ❌ errors in InferenceData conversion
idata = pm.sample(chains=1)
```
Only variable "a" caused an error - but unfortunately only after MCMC.
```
MissingDimensionsError: 'a' has more than 1-dimension and the same name as one of its dimensions ('chain', 'draw', 'a').
xarray disallows such variables because they conflict with the coordinates used to label dimensions.
```
Since dims are passed at creation of the variables, we should raise that error in `Model.add_random_variable`. That will raise the error much earlier, and work for variables and data.
https://github.com/pymc-devs/pymc/blob/14c4f39122ae313e25b2698195067ec44b69b26a/pymc/model.py#L1416-L1429
## Versions and main components
* PyMC/PyMC3 Version: latest
|
1.0
|
`pm.Data` silently missing from `InferenceData` when dims match the variable name - Xarray, and thereby `InferenceData` don't support labeling dimensions with the same name as the variable.
```python
with pm.Model() as pmodel:
pm.Data("city", numpy.arange(5), dims="cities") # ✔ ends up in .constant_data as expected
pm.Data("time", numpy.arange(5), dims="time") # ❌ silently missing
pm.Normal("a") # ❌ errors in InferenceData conversion
idata = pm.sample(chains=1)
```
Only variable "a" caused an error - but unfortunately only after MCMC.
```
MissingDimensionsError: 'a' has more than 1-dimension and the same name as one of its dimensions ('chain', 'draw', 'a').
xarray disallows such variables because they conflict with the coordinates used to label dimensions.
```
Since dims are passed at creation of the variables, we should raise that error in `Model.add_random_variable`. That will raise the error much earlier, and work for variables and data.
https://github.com/pymc-devs/pymc/blob/14c4f39122ae313e25b2698195067ec44b69b26a/pymc/model.py#L1416-L1429
## Versions and main components
* PyMC/PyMC3 Version: latest
|
defect
|
pm data silently missing from inferencedata when dims match the variable name xarray and thereby inferencedata don t support labeling dimensions with the same name as the variable python with pm model as pmodel pm data city numpy arange dims cities ✔ ends up in constant data as expected pm data time numpy arange dims time ❌ silently missing pm normal a ❌ errors in inferencedata conversion idata pm sample chains only variable a caused an error but unfortunately only after mcmc missingdimensionserror a has more than dimension and the same name as one of its dimensions chain draw a xarray disallows such variables because they conflict with the coordinates used to label dimensions since dims are passed at creation of the variables we should raise that error in model add random variable that will raise the error much earlier and work for variables and data versions and main components pymc version latest
| 1
|
240,909
| 7,807,268,184
|
IssuesEvent
|
2018-06-11 16:18:45
|
concrete5/concrete5
|
https://api.github.com/repos/concrete5/concrete5
|
closed
|
FileFolder::getNodeByName and duplicated folder names
|
help wanted priority:like to have type:enhancement
|
Let's assume we have this folder structure:
```
╖
╠═ Folder A
║ ╠═ Sub 1
║ ╚═ Sub 2
╚═ Folder B
╠═ Sub 1
╚═ Sub 2
```
What `FileFolder::getNodeByName('Sub 1')` will return? Right now the result is intererminate: we'll receive one of the two `Sub 1` folders.
AFAIK, the only way to retrieve `Folder A` / `Sub 1` is to use a combination of `getRootFolder` + `populateDirectChildrenOnly` + `getChildNodes` + `getTreeNodeName`.
What about adding a new method to the Concrete\Core\Tree\Node\Node class?
I'm thinking about something like this:
```php
/**
* @param string[] $names
*
* @return static|null
*/
public function getChildByPath(array $names)
{
if (count($names) === 0) {
$result = $this;
} else {
$childName = array_shift($names);
$result = null;
$this->populateDirectChildrenOnly();
foreach ($this->childNodes as $childNode) {
if ($childNode->getTreeNodeName() === $childName) {
$result = $childNode->getChildByPath($names);
if ($result !== null) {
break;
}
}
}
}
return $result;
}
```
That way, to get the `Folder A` / `Sub 1` folder we could simply need this:
```php
$fs = new Concrete\Core\File\Filesystem();
$fs->getRootFolder()->getChildByPath(['Folder A', 'Sub 1']);
```
|
1.0
|
FileFolder::getNodeByName and duplicated folder names - Let's assume we have this folder structure:
```
╖
╠═ Folder A
║ ╠═ Sub 1
║ ╚═ Sub 2
╚═ Folder B
╠═ Sub 1
╚═ Sub 2
```
What `FileFolder::getNodeByName('Sub 1')` will return? Right now the result is intererminate: we'll receive one of the two `Sub 1` folders.
AFAIK, the only way to retrieve `Folder A` / `Sub 1` is to use a combination of `getRootFolder` + `populateDirectChildrenOnly` + `getChildNodes` + `getTreeNodeName`.
What about adding a new method to the Concrete\Core\Tree\Node\Node class?
I'm thinking about something like this:
```php
/**
* @param string[] $names
*
* @return static|null
*/
public function getChildByPath(array $names)
{
if (count($names) === 0) {
$result = $this;
} else {
$childName = array_shift($names);
$result = null;
$this->populateDirectChildrenOnly();
foreach ($this->childNodes as $childNode) {
if ($childNode->getTreeNodeName() === $childName) {
$result = $childNode->getChildByPath($names);
if ($result !== null) {
break;
}
}
}
}
return $result;
}
```
That way, to get the `Folder A` / `Sub 1` folder we could simply need this:
```php
$fs = new Concrete\Core\File\Filesystem();
$fs->getRootFolder()->getChildByPath(['Folder A', 'Sub 1']);
```
|
non_defect
|
filefolder getnodebyname and duplicated folder names let s assume we have this folder structure ╖ ╠═ folder a ║ ╠═ sub ║ ╚═ sub ╚═ folder b ╠═ sub ╚═ sub what filefolder getnodebyname sub will return right now the result is intererminate we ll receive one of the two sub folders afaik the only way to retrieve folder a sub is to use a combination of getrootfolder populatedirectchildrenonly getchildnodes gettreenodename what about adding a new method to the concrete core tree node node class i m thinking about something like this php param string names return static null public function getchildbypath array names if count names result this else childname array shift names result null this populatedirectchildrenonly foreach this childnodes as childnode if childnode gettreenodename childname result childnode getchildbypath names if result null break return result that way to get the folder a sub folder we could simply need this php fs new concrete core file filesystem fs getrootfolder getchildbypath
| 0
|
19,872
| 3,267,201,749
|
IssuesEvent
|
2015-10-23 01:16:51
|
umple/umple
|
https://api.github.com/repos/umple/umple
|
closed
|
Download links on the 'Umple Tools' userdoc page are out of date
|
Diffic-VEasy Priority-Medium Status-Accepted Type-Defect
|
Originally reported on Google Code with ID 706
Owned by @umple
* * *
http://cruise.eecs.uottawa.ca/umple/UmpleTools.html
**What is the expected output? What do you see instead?**
They link to: https://code.google.com/p/umple/downloads/list
but they should probably link to: https://github.com/umple/Umple/releases/tag/v.1.22.0.5146
-or-
http://try.umple.org/scripts/umple.jar
**Please use labels and text to provide additional information.**
* * *
Reported by `jzwiep` on 2015-04-13 04:43:47
|
1.0
|
Download links on the 'Umple Tools' userdoc page are out of date - Originally reported on Google Code with ID 706
Owned by @umple
* * *
http://cruise.eecs.uottawa.ca/umple/UmpleTools.html
**What is the expected output? What do you see instead?**
They link to: https://code.google.com/p/umple/downloads/list
but they should probably link to: https://github.com/umple/Umple/releases/tag/v.1.22.0.5146
-or-
http://try.umple.org/scripts/umple.jar
**Please use labels and text to provide additional information.**
* * *
Reported by `jzwiep` on 2015-04-13 04:43:47
|
defect
|
download links on the umple tools userdoc page are out of date originally reported on google code with id owned by umple what is the expected output what do you see instead they link to but they should probably link to or please use labels and text to provide additional information reported by jzwiep on
| 1
|
328,154
| 9,990,258,765
|
IssuesEvent
|
2019-07-11 08:26:15
|
webcompat/web-bugs
|
https://api.github.com/repos/webcompat/web-bugs
|
closed
|
accounts.google.com - site is not usable
|
browser-fenix engine-gecko priority-critical
|
<!-- @browser: Firefox Mobile 68.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 9; Mobile; rv:68.0) Gecko/68.0 Firefox/68.0 -->
<!-- @reported_with: -->
<!-- @extra_labels: browser-fenix -->
**URL**: https://accounts.google.com/o/oauth2/auth?redirect_uri=storagerelay://https/www.valueresearchonline.com?id=auth44081
**Browser / Version**: Firefox Mobile 68.0
**Operating System**: Android
**Tested Another Browser**: Yes
**Problem type**: Site is not usable
**Description**: not loading
**Steps to Reproduce**:
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_
|
1.0
|
accounts.google.com - site is not usable - <!-- @browser: Firefox Mobile 68.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 9; Mobile; rv:68.0) Gecko/68.0 Firefox/68.0 -->
<!-- @reported_with: -->
<!-- @extra_labels: browser-fenix -->
**URL**: https://accounts.google.com/o/oauth2/auth?redirect_uri=storagerelay://https/www.valueresearchonline.com?id=auth44081
**Browser / Version**: Firefox Mobile 68.0
**Operating System**: Android
**Tested Another Browser**: Yes
**Problem type**: Site is not usable
**Description**: not loading
**Steps to Reproduce**:
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_
|
non_defect
|
accounts google com site is not usable url browser version firefox mobile operating system android tested another browser yes problem type site is not usable description not loading steps to reproduce browser configuration none from with ❤️
| 0
|
233,008
| 18,942,803,691
|
IssuesEvent
|
2021-11-18 06:21:26
|
milvus-io/milvus
|
https://api.github.com/repos/milvus-io/milvus
|
closed
|
[Bug]: Test case "test_delete_not_existed_values" failed for parameter was re-valued in function "equal_entities_list"
|
kind/bug area/test
|
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Environment
```markdown
- Milvus version: latest
- Deployment mode(standalone or cluster):
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS):
- CPU/Memory:
- GPU:
- Others:
```
### Current Behavior
In the following function, "exp" was changed through remove operation, which is not expected.
Suggested: deep copy of "exp" like: exp1 = copy.deepcopy(exp)
```python
def equal_entities_list(exp, actual, with_vec=False):
"""
compare two entities lists in inconsistent order
:param with_vec: whether entities with vec field
:param exp: exp entities list, list of dict
:param actual: actual entities list, list of dict
:return: True or False
example:
exp = [{"int": 0, "vec": [0.999999, 0.111111]}, {"int": 1, "vec": [0.888888, 0.222222]}]
actual = [{"int": 1, "vec": [0.888888, 0.222222]}, {"int": 0, "vec": [0.999999, 0.111111]}]
exp = actual
"""
if len(exp) != len(actual):
return False
if with_vec:
for a in actual:
# if vec field returned in query res
if entity_in(a, exp):
try:
# if vec field returned in query res
remove_entity(a, exp)
except Exception as ex:
log.error(ex)
else:
for a in actual:
if a in exp:
try:
exp.remove(a)
except Exception as ex:
log.error(ex)
return True if len(exp) == 0 else False
```
### Expected Behavior
See at current behaviour
### Steps To Reproduce
```markdown
NA
```
### Anything else?
_No response_
|
1.0
|
[Bug]: Test case "test_delete_not_existed_values" failed for parameter was re-valued in function "equal_entities_list" - ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Environment
```markdown
- Milvus version: latest
- Deployment mode(standalone or cluster):
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS):
- CPU/Memory:
- GPU:
- Others:
```
### Current Behavior
In the following function, "exp" was changed through remove operation, which is not expected.
Suggested: deep copy of "exp" like: exp1 = copy.deepcopy(exp)
```python
def equal_entities_list(exp, actual, with_vec=False):
"""
compare two entities lists in inconsistent order
:param with_vec: whether entities with vec field
:param exp: exp entities list, list of dict
:param actual: actual entities list, list of dict
:return: True or False
example:
exp = [{"int": 0, "vec": [0.999999, 0.111111]}, {"int": 1, "vec": [0.888888, 0.222222]}]
actual = [{"int": 1, "vec": [0.888888, 0.222222]}, {"int": 0, "vec": [0.999999, 0.111111]}]
exp = actual
"""
if len(exp) != len(actual):
return False
if with_vec:
for a in actual:
# if vec field returned in query res
if entity_in(a, exp):
try:
# if vec field returned in query res
remove_entity(a, exp)
except Exception as ex:
log.error(ex)
else:
for a in actual:
if a in exp:
try:
exp.remove(a)
except Exception as ex:
log.error(ex)
return True if len(exp) == 0 else False
```
### Expected Behavior
See at current behaviour
### Steps To Reproduce
```markdown
NA
```
### Anything else?
_No response_
|
non_defect
|
test case test delete not existed values failed for parameter was re valued in function equal entities list is there an existing issue for this i have searched the existing issues environment markdown milvus version latest deployment mode standalone or cluster sdk version e g pymilvus os ubuntu or centos cpu memory gpu others current behavior in the following function exp was changed through remove operation which is not expected suggested deep copy of exp like copy deepcopy exp python def equal entities list exp actual with vec false compare two entities lists in inconsistent order param with vec whether entities with vec field param exp exp entities list list of dict param actual actual entities list list of dict return true or false example exp int vec actual int vec exp actual if len exp len actual return false if with vec for a in actual if vec field returned in query res if entity in a exp try if vec field returned in query res remove entity a exp except exception as ex log error ex else for a in actual if a in exp try exp remove a except exception as ex log error ex return true if len exp else false expected behavior see at current behaviour steps to reproduce markdown na anything else no response
| 0
|
90,095
| 15,856,060,867
|
IssuesEvent
|
2021-04-08 01:25:32
|
rammatzkvosky/react-middle-truncate
|
https://api.github.com/repos/rammatzkvosky/react-middle-truncate
|
opened
|
CVE-2020-11022 (Medium) detected in jquery-1.7.1.min.js, jquery-2.1.4.min.js
|
security vulnerability
|
## CVE-2020-11022 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>jquery-1.7.1.min.js</b>, <b>jquery-2.1.4.min.js</b></p></summary>
<p>
<details><summary><b>jquery-1.7.1.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.1/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.1/jquery.min.js</a></p>
<p>Path to dependency file: react-middle-truncate/node_modules/vm-browserify/example/run/index.html</p>
<p>Path to vulnerable library: react-middle-truncate/node_modules/vm-browserify/example/run/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.7.1.min.js** (Vulnerable Library)
</details>
<details><summary><b>jquery-2.1.4.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/2.1.4/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/2.1.4/jquery.min.js</a></p>
<p>Path to dependency file: react-middle-truncate/node_modules/js-base64/test/index.html</p>
<p>Path to vulnerable library: react-middle-truncate/node_modules/js-base64/test/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-2.1.4.min.js** (Vulnerable Library)
</details>
</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 jQuery versions greater than or equal to 1.2 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
<p>Publish Date: 2020-04-29
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-11022>CVE-2020-11022</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://blog.jquery.com/2020/04/10/jquery-3-5-0-released/">https://blog.jquery.com/2020/04/10/jquery-3-5-0-released/</a></p>
<p>Release Date: 2020-04-29</p>
<p>Fix Resolution: jQuery - 3.5.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"JavaScript","packageName":"jquery","packageVersion":"1.7.1","packageFilePaths":["/node_modules/vm-browserify/example/run/index.html"],"isTransitiveDependency":false,"dependencyTree":"jquery:1.7.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"jQuery - 3.5.0"},{"packageType":"JavaScript","packageName":"jquery","packageVersion":"2.1.4","packageFilePaths":["/node_modules/js-base64/test/index.html"],"isTransitiveDependency":false,"dependencyTree":"jquery:2.1.4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"jQuery - 3.5.0"}],"baseBranches":[],"vulnerabilityIdentifier":"CVE-2020-11022","vulnerabilityDetails":"In jQuery versions greater than or equal to 1.2 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery\u0027s DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-11022","cvss3Severity":"medium","cvss3Score":"6.1","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Changed","C":"Low","UI":"Required","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> -->
|
True
|
CVE-2020-11022 (Medium) detected in jquery-1.7.1.min.js, jquery-2.1.4.min.js - ## CVE-2020-11022 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>jquery-1.7.1.min.js</b>, <b>jquery-2.1.4.min.js</b></p></summary>
<p>
<details><summary><b>jquery-1.7.1.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.1/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.1/jquery.min.js</a></p>
<p>Path to dependency file: react-middle-truncate/node_modules/vm-browserify/example/run/index.html</p>
<p>Path to vulnerable library: react-middle-truncate/node_modules/vm-browserify/example/run/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.7.1.min.js** (Vulnerable Library)
</details>
<details><summary><b>jquery-2.1.4.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/2.1.4/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/2.1.4/jquery.min.js</a></p>
<p>Path to dependency file: react-middle-truncate/node_modules/js-base64/test/index.html</p>
<p>Path to vulnerable library: react-middle-truncate/node_modules/js-base64/test/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-2.1.4.min.js** (Vulnerable Library)
</details>
</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 jQuery versions greater than or equal to 1.2 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
<p>Publish Date: 2020-04-29
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-11022>CVE-2020-11022</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://blog.jquery.com/2020/04/10/jquery-3-5-0-released/">https://blog.jquery.com/2020/04/10/jquery-3-5-0-released/</a></p>
<p>Release Date: 2020-04-29</p>
<p>Fix Resolution: jQuery - 3.5.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"JavaScript","packageName":"jquery","packageVersion":"1.7.1","packageFilePaths":["/node_modules/vm-browserify/example/run/index.html"],"isTransitiveDependency":false,"dependencyTree":"jquery:1.7.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"jQuery - 3.5.0"},{"packageType":"JavaScript","packageName":"jquery","packageVersion":"2.1.4","packageFilePaths":["/node_modules/js-base64/test/index.html"],"isTransitiveDependency":false,"dependencyTree":"jquery:2.1.4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"jQuery - 3.5.0"}],"baseBranches":[],"vulnerabilityIdentifier":"CVE-2020-11022","vulnerabilityDetails":"In jQuery versions greater than or equal to 1.2 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery\u0027s DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-11022","cvss3Severity":"medium","cvss3Score":"6.1","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Changed","C":"Low","UI":"Required","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> -->
|
non_defect
|
cve medium detected in jquery min js jquery min js cve medium severity vulnerability vulnerable libraries jquery min js jquery min js jquery min js javascript library for dom operations library home page a href path to dependency file react middle truncate node modules vm browserify example run index html path to vulnerable library react middle truncate node modules vm browserify example run index html dependency hierarchy x jquery min js vulnerable library jquery min js javascript library for dom operations library home page a href path to dependency file react middle truncate node modules js test index html path to vulnerable library react middle truncate node modules js test index html dependency hierarchy x jquery min js vulnerable library vulnerability details in jquery versions greater than or equal to and before passing html from untrusted sources even after sanitizing it to one of jquery s dom manipulation methods i e html append and others may execute untrusted code this problem is patched in jquery publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution jquery isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree jquery isminimumfixversionavailable true minimumfixversion jquery packagetype javascript packagename jquery packageversion packagefilepaths istransitivedependency false dependencytree jquery isminimumfixversionavailable true minimumfixversion jquery basebranches vulnerabilityidentifier cve vulnerabilitydetails in jquery versions greater than or equal to and before passing html from untrusted sources even after sanitizing it to one of jquery dom manipulation methods i e html append and others may execute untrusted code this problem is patched in jquery vulnerabilityurl
| 0
|
7,436
| 2,610,383,368
|
IssuesEvent
|
2015-02-26 20:04:04
|
chrsmith/hedgewars
|
https://api.github.com/repos/chrsmith/hedgewars
|
closed
|
Top CMakeLists.txt assumes debug configuration if CMAKE_BUILD_TYPE is not Release
|
auto-migrated Priority-Medium Type-Defect
|
```
Currently, CMakeLists.txt thinks that if the build type is not Release, then
debug configuration should be used:
if(CMAKE_BUILD_TYPE MATCHES RELEASE OR CMAKE_BUILD_TYPE MATCHES "Release")
message(STATUS "Building Release")
set(Optz true)
else()
message(STATUS "Building Debug")
set(Optz false)
endif()
But this doesn't account for custom build types, like the one used in Gentoo
(see
http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/eclass/cmake-utils.eclas
s?view=markup for details on CMake project handling). The relevant code could
be changed to
if(CMAKE_BUILD_TYPE MATCHES DEBUG OR CMAKE_BUILD_TYPE MATCHES "Debug")
message(STATUS "Building Debug")
set(Optz false)
else()
message(STATUS "Building Release")
set(Optz true)
endif()
```
-----
Original issue reported on code.google.com by `andrey.vihrov` on 24 Sep 2011 at 9:03
|
1.0
|
Top CMakeLists.txt assumes debug configuration if CMAKE_BUILD_TYPE is not Release - ```
Currently, CMakeLists.txt thinks that if the build type is not Release, then
debug configuration should be used:
if(CMAKE_BUILD_TYPE MATCHES RELEASE OR CMAKE_BUILD_TYPE MATCHES "Release")
message(STATUS "Building Release")
set(Optz true)
else()
message(STATUS "Building Debug")
set(Optz false)
endif()
But this doesn't account for custom build types, like the one used in Gentoo
(see
http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/eclass/cmake-utils.eclas
s?view=markup for details on CMake project handling). The relevant code could
be changed to
if(CMAKE_BUILD_TYPE MATCHES DEBUG OR CMAKE_BUILD_TYPE MATCHES "Debug")
message(STATUS "Building Debug")
set(Optz false)
else()
message(STATUS "Building Release")
set(Optz true)
endif()
```
-----
Original issue reported on code.google.com by `andrey.vihrov` on 24 Sep 2011 at 9:03
|
defect
|
top cmakelists txt assumes debug configuration if cmake build type is not release currently cmakelists txt thinks that if the build type is not release then debug configuration should be used if cmake build type matches release or cmake build type matches release message status building release set optz true else message status building debug set optz false endif but this doesn t account for custom build types like the one used in gentoo see s view markup for details on cmake project handling the relevant code could be changed to if cmake build type matches debug or cmake build type matches debug message status building debug set optz false else message status building release set optz true endif original issue reported on code google com by andrey vihrov on sep at
| 1
|
6,395
| 2,610,242,187
|
IssuesEvent
|
2015-02-26 19:17:06
|
chrsmith/jsjsj122
|
https://api.github.com/repos/chrsmith/jsjsj122
|
opened
|
台州割包皮包茎哪家正规
|
auto-migrated Priority-Medium Type-Defect
|
```
台州割包皮包茎哪家正规【台州五洲生殖医院】24小时健康咨
询热线:0576-88066933-(扣扣800080609)-(微信号tzwzszyy)医院地址:台州
市椒江区枫南路229号(枫南大转盘旁)乘车线路:乘坐104、108�
��118、198及椒江一金清公交车直达枫南小区,乘坐107、105、109
、112、901、 902公交车到星星广场下车,步行即可到院。
诊疗项目:阳痿,早泄,前列腺炎,前列腺增生,龟头炎,��
�精,无精。包皮包茎,精索静脉曲张,淋病等。
台州五洲生殖医院是台州最大的男科医院,权威专家在线免��
�咨询,拥有专业完善的男科检查治疗设备,严格按照国家标�
��收费。尖端医疗设备,与世界同步。权威专家,成就专业典
范。人性化服务,一切以患者为中心。
看男科就选台州五洲生殖医院,专业男科为男人。
```
-----
Original issue reported on code.google.com by `poweragr...@gmail.com` on 31 May 2014 at 1:11
|
1.0
|
台州割包皮包茎哪家正规 - ```
台州割包皮包茎哪家正规【台州五洲生殖医院】24小时健康咨
询热线:0576-88066933-(扣扣800080609)-(微信号tzwzszyy)医院地址:台州
市椒江区枫南路229号(枫南大转盘旁)乘车线路:乘坐104、108�
��118、198及椒江一金清公交车直达枫南小区,乘坐107、105、109
、112、901、 902公交车到星星广场下车,步行即可到院。
诊疗项目:阳痿,早泄,前列腺炎,前列腺增生,龟头炎,��
�精,无精。包皮包茎,精索静脉曲张,淋病等。
台州五洲生殖医院是台州最大的男科医院,权威专家在线免��
�咨询,拥有专业完善的男科检查治疗设备,严格按照国家标�
��收费。尖端医疗设备,与世界同步。权威专家,成就专业典
范。人性化服务,一切以患者为中心。
看男科就选台州五洲生殖医院,专业男科为男人。
```
-----
Original issue reported on code.google.com by `poweragr...@gmail.com` on 31 May 2014 at 1:11
|
defect
|
台州割包皮包茎哪家正规 台州割包皮包茎哪家正规【台州五洲生殖医院】 询热线 微信号tzwzszyy 医院地址 台州 (枫南大转盘旁)乘车线路 、 � �� 、 , 、 、 、 、 、 ,步行即可到院。 诊疗项目:阳痿,早泄,前列腺炎,前列腺增生,龟头炎,�� �精,无精。包皮包茎,精索静脉曲张,淋病等。 台州五洲生殖医院是台州最大的男科医院,权威专家在线免�� �咨询,拥有专业完善的男科检查治疗设备,严格按照国家标� ��收费。尖端医疗设备,与世界同步。权威专家,成就专业典 范。人性化服务,一切以患者为中心。 看男科就选台州五洲生殖医院,专业男科为男人。 original issue reported on code google com by poweragr gmail com on may at
| 1
|
100,519
| 16,489,895,922
|
IssuesEvent
|
2021-05-25 01:07:10
|
billmcchesney1/jazz
|
https://api.github.com/repos/billmcchesney1/jazz
|
opened
|
CVE-2021-23362 (Medium) detected in multiple libraries
|
security vulnerability
|
## CVE-2021-23362 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>hosted-git-info-2.8.8.tgz</b>, <b>hosted-git-info-2.7.1.tgz</b>, <b>hosted-git-info-2.5.0.tgz</b></p></summary>
<p>
<details><summary><b>hosted-git-info-2.8.8.tgz</b></p></summary>
<p>Provides metadata and conversions from repository urls for Github, Bitbucket and Gitlab</p>
<p>Library home page: <a href="https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.8.8.tgz">https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.8.8.tgz</a></p>
<p>Path to dependency file: jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/package.json</p>
<p>Path to vulnerable library: jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/node_modules/hosted-git-info/package.json,jazz/templates/angular-website-template/app/node_modules/hosted-git-info/package.json,jazz/core/jazz_ui/node_modules/hosted-git-info/package.json,jazz/templates/react-website-template/app/node_modules/hosted-git-info/package.json</p>
<p>
Dependency Hierarchy:
- cli-1.7.4.tgz (Root Library)
- node-sass-4.14.1.tgz
- meow-3.7.0.tgz
- normalize-package-data-2.5.0.tgz
- :x: **hosted-git-info-2.8.8.tgz** (Vulnerable Library)
</details>
<details><summary><b>hosted-git-info-2.7.1.tgz</b></p></summary>
<p>Provides metadata and conversions from repository urls for Github, Bitbucket and Gitlab</p>
<p>Library home page: <a href="https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.7.1.tgz">https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.7.1.tgz</a></p>
<p>Path to dependency file: jazz/core/jazz_delete-serverless-service/package.json</p>
<p>Path to vulnerable library: jazz/core/jazz_delete-serverless-service/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_deployments/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_create-serverless-service/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_logs/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_services/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_environments/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_is-service-available/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_events/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_t-vault/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_events/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_environment-event-handler/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_deployments-event-handler/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_services-handler/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_acl/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_es-kinesis-log-streamer/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_scm-webhook/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_codeq/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_logout/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_assets/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_test-lambda/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_login/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_is-slack-channel-available/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_deployments/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_usermanagement/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_metrics/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_cloud-logs-streamer/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_slack-channel/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_services/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_asset-event-handler/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_splunk-kinesis-log-streamer/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_events-handler/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_email/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_cognito-admin-authorizer/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_cognito-authorizer/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_apigee-proxy-aws/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_slack-event-handler/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_admin/node_modules/nyc/node_modules/hosted-git-info/package.json</p>
<p>
Dependency Hierarchy:
- nyc-13.3.0.tgz (Root Library)
- test-exclude-5.1.0.tgz
- read-pkg-up-4.0.0.tgz
- read-pkg-3.0.0.tgz
- normalize-package-data-2.5.0.tgz
- :x: **hosted-git-info-2.7.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>hosted-git-info-2.5.0.tgz</b></p></summary>
<p>Provides metadata and conversions from repository urls for Github, Bitbucket and Gitlab</p>
<p>Library home page: <a href="https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.5.0.tgz">https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.5.0.tgz</a></p>
<p>Path to dependency file: jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ngx-slimscroll/ngx-slimscroll/package.json</p>
<p>Path to vulnerable library: jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ngx-slimscroll/ngx-slimscroll/node_modules/hosted-git-info/package.json</p>
<p>
Dependency Hierarchy:
- webpack-3.0.0.tgz (Root Library)
- yargs-6.6.0.tgz
- read-pkg-up-1.0.1.tgz
- read-pkg-1.1.0.tgz
- normalize-package-data-2.4.0.tgz
- :x: **hosted-git-info-2.5.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/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The package hosted-git-info before 3.0.8 are vulnerable to Regular Expression Denial of Service (ReDoS) via regular expression shortcutMatch in the fromUrl function in index.js. The affected regular expression exhibits polynomial worst-case time complexity.
<p>Publish Date: 2021-03-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23362>CVE-2021-23362</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.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-43f8-2h32-f4cj">https://github.com/advisories/GHSA-43f8-2h32-f4cj</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: hosted-git-info - 2.8.9,3.0.8</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"hosted-git-info","packageVersion":"2.8.8","packageFilePaths":["/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/package.json","/templates/angular-website-template/app/package.json","/core/jazz_ui/package.json","/templates/react-website-template/app/package.json"],"isTransitiveDependency":true,"dependencyTree":"@angular/cli:1.7.4;node-sass:4.14.1;meow:3.7.0;normalize-package-data:2.5.0;hosted-git-info:2.8.8","isMinimumFixVersionAvailable":true,"minimumFixVersion":"hosted-git-info - 2.8.9,3.0.8"},{"packageType":"javascript/Node.js","packageName":"hosted-git-info","packageVersion":"2.7.1","packageFilePaths":["/core/jazz_delete-serverless-service/package.json","/core/jazz_deployments-event-handler/package.json","/core/jazz_create-serverless-service/package.json","/core/jazz_logs/package.json","/core/jazz_services/package.json","/core/jazz_environments/package.json","/core/jazz_is-service-available/package.json","/core/jazz_events/package.json","/core/jazz_t-vault/package.json","/core/jazz_events-handler/package.json","/core/jazz_environment-event-handler/package.json","/core/jazz_services-handler/package.json","/core/jazz_acl/package.json","/core/jazz_es-kinesis-log-streamer/package.json","/core/jazz_scm-webhook/package.json","/core/jazz_codeq/package.json","/core/jazz_logout/package.json","/core/jazz_assets/package.json","/core/jazz_test-lambda/package.json","/core/jazz_login/package.json","/core/jazz_is-slack-channel-available/package.json","/core/jazz_deployments/package.json","/core/jazz_usermanagement/package.json","/core/jazz_metrics/package.json","/core/jazz_cloud-logs-streamer/package.json","/core/jazz_slack-channel/package.json","/core/jazz_asset-event-handler/package.json","/core/jazz_splunk-kinesis-log-streamer/package.json","/core/jazz_email/package.json","/core/jazz_cognito-admin-authorizer/package.json","/core/jazz_cognito-authorizer/package.json","/core/jazz_apigee-proxy-aws/package.json","/core/jazz_slack-event-handler/package.json","/core/jazz_admin/package.json"],"isTransitiveDependency":true,"dependencyTree":"nyc:13.3.0;test-exclude:5.1.0;read-pkg-up:4.0.0;read-pkg:3.0.0;normalize-package-data:2.5.0;hosted-git-info:2.7.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"hosted-git-info - 2.8.9,3.0.8"},{"packageType":"javascript/Node.js","packageName":"hosted-git-info","packageVersion":"2.5.0","packageFilePaths":["/core/jazz_ui/src/app/primary-components/daterange-picker/ngx-slimscroll/ngx-slimscroll/package.json"],"isTransitiveDependency":true,"dependencyTree":"webpack:3.0.0;yargs:6.6.0;read-pkg-up:1.0.1;read-pkg:1.1.0;normalize-package-data:2.4.0;hosted-git-info:2.5.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"hosted-git-info - 2.8.9,3.0.8"}],"baseBranches":["develop"],"vulnerabilityIdentifier":"CVE-2021-23362","vulnerabilityDetails":"The package hosted-git-info before 3.0.8 are vulnerable to Regular Expression Denial of Service (ReDoS) via regular expression shortcutMatch in the fromUrl function in index.js. The affected regular expression exhibits polynomial worst-case time complexity.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23362","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"Low","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> -->
|
True
|
CVE-2021-23362 (Medium) detected in multiple libraries - ## CVE-2021-23362 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>hosted-git-info-2.8.8.tgz</b>, <b>hosted-git-info-2.7.1.tgz</b>, <b>hosted-git-info-2.5.0.tgz</b></p></summary>
<p>
<details><summary><b>hosted-git-info-2.8.8.tgz</b></p></summary>
<p>Provides metadata and conversions from repository urls for Github, Bitbucket and Gitlab</p>
<p>Library home page: <a href="https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.8.8.tgz">https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.8.8.tgz</a></p>
<p>Path to dependency file: jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/package.json</p>
<p>Path to vulnerable library: jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/node_modules/hosted-git-info/package.json,jazz/templates/angular-website-template/app/node_modules/hosted-git-info/package.json,jazz/core/jazz_ui/node_modules/hosted-git-info/package.json,jazz/templates/react-website-template/app/node_modules/hosted-git-info/package.json</p>
<p>
Dependency Hierarchy:
- cli-1.7.4.tgz (Root Library)
- node-sass-4.14.1.tgz
- meow-3.7.0.tgz
- normalize-package-data-2.5.0.tgz
- :x: **hosted-git-info-2.8.8.tgz** (Vulnerable Library)
</details>
<details><summary><b>hosted-git-info-2.7.1.tgz</b></p></summary>
<p>Provides metadata and conversions from repository urls for Github, Bitbucket and Gitlab</p>
<p>Library home page: <a href="https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.7.1.tgz">https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.7.1.tgz</a></p>
<p>Path to dependency file: jazz/core/jazz_delete-serverless-service/package.json</p>
<p>Path to vulnerable library: jazz/core/jazz_delete-serverless-service/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_deployments/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_create-serverless-service/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_logs/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_services/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_environments/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_is-service-available/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_events/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_t-vault/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_events/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_environment-event-handler/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_deployments-event-handler/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_services-handler/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_acl/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_es-kinesis-log-streamer/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_scm-webhook/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_codeq/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_logout/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_assets/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_test-lambda/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_login/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_is-slack-channel-available/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_deployments/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_usermanagement/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_metrics/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_cloud-logs-streamer/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_slack-channel/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_services/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_asset-event-handler/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_splunk-kinesis-log-streamer/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_events-handler/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_email/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_cognito-admin-authorizer/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_cognito-authorizer/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_apigee-proxy-aws/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_slack-event-handler/node_modules/nyc/node_modules/hosted-git-info/package.json,jazz/core/jazz_admin/node_modules/nyc/node_modules/hosted-git-info/package.json</p>
<p>
Dependency Hierarchy:
- nyc-13.3.0.tgz (Root Library)
- test-exclude-5.1.0.tgz
- read-pkg-up-4.0.0.tgz
- read-pkg-3.0.0.tgz
- normalize-package-data-2.5.0.tgz
- :x: **hosted-git-info-2.7.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>hosted-git-info-2.5.0.tgz</b></p></summary>
<p>Provides metadata and conversions from repository urls for Github, Bitbucket and Gitlab</p>
<p>Library home page: <a href="https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.5.0.tgz">https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.5.0.tgz</a></p>
<p>Path to dependency file: jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ngx-slimscroll/ngx-slimscroll/package.json</p>
<p>Path to vulnerable library: jazz/core/jazz_ui/src/app/primary-components/daterange-picker/ngx-slimscroll/ngx-slimscroll/node_modules/hosted-git-info/package.json</p>
<p>
Dependency Hierarchy:
- webpack-3.0.0.tgz (Root Library)
- yargs-6.6.0.tgz
- read-pkg-up-1.0.1.tgz
- read-pkg-1.1.0.tgz
- normalize-package-data-2.4.0.tgz
- :x: **hosted-git-info-2.5.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/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The package hosted-git-info before 3.0.8 are vulnerable to Regular Expression Denial of Service (ReDoS) via regular expression shortcutMatch in the fromUrl function in index.js. The affected regular expression exhibits polynomial worst-case time complexity.
<p>Publish Date: 2021-03-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23362>CVE-2021-23362</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.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-43f8-2h32-f4cj">https://github.com/advisories/GHSA-43f8-2h32-f4cj</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: hosted-git-info - 2.8.9,3.0.8</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"hosted-git-info","packageVersion":"2.8.8","packageFilePaths":["/core/jazz_ui/src/app/primary-components/daterange-picker/ng2-datepicker/package.json","/templates/angular-website-template/app/package.json","/core/jazz_ui/package.json","/templates/react-website-template/app/package.json"],"isTransitiveDependency":true,"dependencyTree":"@angular/cli:1.7.4;node-sass:4.14.1;meow:3.7.0;normalize-package-data:2.5.0;hosted-git-info:2.8.8","isMinimumFixVersionAvailable":true,"minimumFixVersion":"hosted-git-info - 2.8.9,3.0.8"},{"packageType":"javascript/Node.js","packageName":"hosted-git-info","packageVersion":"2.7.1","packageFilePaths":["/core/jazz_delete-serverless-service/package.json","/core/jazz_deployments-event-handler/package.json","/core/jazz_create-serverless-service/package.json","/core/jazz_logs/package.json","/core/jazz_services/package.json","/core/jazz_environments/package.json","/core/jazz_is-service-available/package.json","/core/jazz_events/package.json","/core/jazz_t-vault/package.json","/core/jazz_events-handler/package.json","/core/jazz_environment-event-handler/package.json","/core/jazz_services-handler/package.json","/core/jazz_acl/package.json","/core/jazz_es-kinesis-log-streamer/package.json","/core/jazz_scm-webhook/package.json","/core/jazz_codeq/package.json","/core/jazz_logout/package.json","/core/jazz_assets/package.json","/core/jazz_test-lambda/package.json","/core/jazz_login/package.json","/core/jazz_is-slack-channel-available/package.json","/core/jazz_deployments/package.json","/core/jazz_usermanagement/package.json","/core/jazz_metrics/package.json","/core/jazz_cloud-logs-streamer/package.json","/core/jazz_slack-channel/package.json","/core/jazz_asset-event-handler/package.json","/core/jazz_splunk-kinesis-log-streamer/package.json","/core/jazz_email/package.json","/core/jazz_cognito-admin-authorizer/package.json","/core/jazz_cognito-authorizer/package.json","/core/jazz_apigee-proxy-aws/package.json","/core/jazz_slack-event-handler/package.json","/core/jazz_admin/package.json"],"isTransitiveDependency":true,"dependencyTree":"nyc:13.3.0;test-exclude:5.1.0;read-pkg-up:4.0.0;read-pkg:3.0.0;normalize-package-data:2.5.0;hosted-git-info:2.7.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"hosted-git-info - 2.8.9,3.0.8"},{"packageType":"javascript/Node.js","packageName":"hosted-git-info","packageVersion":"2.5.0","packageFilePaths":["/core/jazz_ui/src/app/primary-components/daterange-picker/ngx-slimscroll/ngx-slimscroll/package.json"],"isTransitiveDependency":true,"dependencyTree":"webpack:3.0.0;yargs:6.6.0;read-pkg-up:1.0.1;read-pkg:1.1.0;normalize-package-data:2.4.0;hosted-git-info:2.5.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"hosted-git-info - 2.8.9,3.0.8"}],"baseBranches":["develop"],"vulnerabilityIdentifier":"CVE-2021-23362","vulnerabilityDetails":"The package hosted-git-info before 3.0.8 are vulnerable to Regular Expression Denial of Service (ReDoS) via regular expression shortcutMatch in the fromUrl function in index.js. The affected regular expression exhibits polynomial worst-case time complexity.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23362","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"Low","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> -->
|
non_defect
|
cve medium detected in multiple libraries cve medium severity vulnerability vulnerable libraries hosted git info tgz hosted git info tgz hosted git info tgz hosted git info tgz provides metadata and conversions from repository urls for github bitbucket and gitlab library home page a href path to dependency file jazz core jazz ui src app primary components daterange picker datepicker package json path to vulnerable library jazz core jazz ui src app primary components daterange picker datepicker node modules hosted git info package json jazz templates angular website template app node modules hosted git info package json jazz core jazz ui node modules hosted git info package json jazz templates react website template app node modules hosted git info package json dependency hierarchy cli tgz root library node sass tgz meow tgz normalize package data tgz x hosted git info tgz vulnerable library hosted git info tgz provides metadata and conversions from repository urls for github bitbucket and gitlab library home page a href path to dependency file jazz core jazz delete serverless service package json path to vulnerable library jazz core jazz delete serverless service node modules nyc node modules hosted git info package json jazz core jazz deployments node modules nyc node modules hosted git info package json jazz core jazz create serverless service node modules nyc node modules hosted git info package json jazz core jazz logs node modules nyc node modules hosted git info package json jazz core jazz services node modules nyc node modules hosted git info package json jazz core jazz environments node modules nyc node modules hosted git info package json jazz core jazz is service available node modules nyc node modules hosted git info package json jazz core jazz events node modules nyc node modules hosted git info package json jazz core jazz t vault node modules nyc node modules hosted git info package json jazz core jazz events node modules nyc node modules hosted git info package json jazz core jazz environment event handler node modules nyc node modules hosted git info package json jazz core jazz deployments event handler node modules nyc node modules hosted git info package json jazz core jazz services handler node modules nyc node modules hosted git info package json jazz core jazz acl node modules nyc node modules hosted git info package json jazz core jazz es kinesis log streamer node modules nyc node modules hosted git info package json jazz core jazz scm webhook node modules nyc node modules hosted git info package json jazz core jazz codeq node modules nyc node modules hosted git info package json jazz core jazz logout node modules nyc node modules hosted git info package json jazz core jazz assets node modules nyc node modules hosted git info package json jazz core jazz test lambda node modules nyc node modules hosted git info package json jazz core jazz login node modules nyc node modules hosted git info package json jazz core jazz is slack channel available node modules nyc node modules hosted git info package json jazz core jazz deployments node modules nyc node modules hosted git info package json jazz core jazz usermanagement node modules nyc node modules hosted git info package json jazz core jazz metrics node modules nyc node modules hosted git info package json jazz core jazz cloud logs streamer node modules nyc node modules hosted git info package json jazz core jazz slack channel node modules nyc node modules hosted git info package json jazz core jazz services node modules nyc node modules hosted git info package json jazz core jazz asset event handler node modules nyc node modules hosted git info package json jazz core jazz splunk kinesis log streamer node modules nyc node modules hosted git info package json jazz core jazz events handler node modules nyc node modules hosted git info package json jazz core jazz email node modules nyc node modules hosted git info package json jazz core jazz cognito admin authorizer node modules nyc node modules hosted git info package json jazz core jazz cognito authorizer node modules nyc node modules hosted git info package json jazz core jazz apigee proxy aws node modules nyc node modules hosted git info package json jazz core jazz slack event handler node modules nyc node modules hosted git info package json jazz core jazz admin node modules nyc node modules hosted git info package json dependency hierarchy nyc tgz root library test exclude tgz read pkg up tgz read pkg tgz normalize package data tgz x hosted git info tgz vulnerable library hosted git info tgz provides metadata and conversions from repository urls for github bitbucket and gitlab library home page a href path to dependency file jazz core jazz ui src app primary components daterange picker ngx slimscroll ngx slimscroll package json path to vulnerable library jazz core jazz ui src app primary components daterange picker ngx slimscroll ngx slimscroll node modules hosted git info package json dependency hierarchy webpack tgz root library yargs tgz read pkg up tgz read pkg tgz normalize package data tgz x hosted git info tgz vulnerable library found in base branch develop vulnerability details the package hosted git info before are vulnerable to regular expression denial of service redos via regular expression shortcutmatch in the fromurl function in index js the affected regular expression exhibits polynomial worst case time complexity 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 low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution hosted git info isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree angular cli node sass meow normalize package data hosted git info isminimumfixversionavailable true minimumfixversion hosted git info packagetype javascript node js packagename hosted git info packageversion packagefilepaths istransitivedependency true dependencytree nyc test exclude read pkg up read pkg normalize package data hosted git info isminimumfixversionavailable true minimumfixversion hosted git info packagetype javascript node js packagename hosted git info packageversion packagefilepaths istransitivedependency true dependencytree webpack yargs read pkg up read pkg normalize package data hosted git info isminimumfixversionavailable true minimumfixversion hosted git info basebranches vulnerabilityidentifier cve vulnerabilitydetails the package hosted git info before are vulnerable to regular expression denial of service redos via regular expression shortcutmatch in the fromurl function in index js the affected regular expression exhibits polynomial worst case time complexity vulnerabilityurl
| 0
|
82,316
| 15,646,542,897
|
IssuesEvent
|
2021-03-23 01:10:09
|
jgeraigery/fac
|
https://api.github.com/repos/jgeraigery/fac
|
opened
|
CVE-2021-23337 (High) detected in multiple libraries
|
security vulnerability
|
## CVE-2021-23337 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>lodash-4.17.15.tgz</b>, <b>lodash-0.9.2.tgz</b>, <b>lodash-2.4.2.tgz</b>, <b>lodash-3.10.1.tgz</b></p></summary>
<p>
<details><summary><b>lodash-4.17.15.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz</a></p>
<p>Path to dependency file: fac/package.json</p>
<p>Path to vulnerable library: fac/node_modules/form-data/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- karma-phantomjs-launcher-0.1.4.tgz (Root Library)
- phantomjs-1.9.20.tgz
- request-2.67.0.tgz
- form-data-1.0.1.tgz
- async-2.6.3.tgz
- :x: **lodash-4.17.15.tgz** (Vulnerable Library)
</details>
<details><summary><b>lodash-0.9.2.tgz</b></p></summary>
<p>A utility library delivering consistency, customization, performance, and extras.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-0.9.2.tgz">https://registry.npmjs.org/lodash/-/lodash-0.9.2.tgz</a></p>
<p>Path to dependency file: fac/package.json</p>
<p>Path to vulnerable library: fac/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- grunt-0.4.5.tgz (Root Library)
- :x: **lodash-0.9.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>lodash-2.4.2.tgz</b></p></summary>
<p>A utility library delivering consistency, customization, performance, & extras.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a></p>
<p>Path to dependency file: fac/package.json</p>
<p>Path to vulnerable library: fac/node_modules/grunt-karma/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- grunt-0.4.5.tgz (Root Library)
- findup-sync-0.1.3.tgz
- :x: **lodash-2.4.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>lodash-3.10.1.tgz</b></p></summary>
<p>The modern build of lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz">https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz</a></p>
<p>Path to dependency file: fac/package.json</p>
<p>Path to vulnerable library: fac/node_modules/karma/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- karma-0.12.37.tgz (Root Library)
- :x: **lodash-3.10.1.tgz** (Vulnerable Library)
</details>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
<p>Publish Date: 2021-02-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337>CVE-2021-23337</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.2</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- 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://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c">https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c</a></p>
<p>Release Date: 2021-02-15</p>
<p>Fix Resolution: lodash - 4.17.21</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"lodash","packageVersion":"4.17.15","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"karma-phantomjs-launcher:0.1.4;phantomjs:1.9.20;request:2.67.0;form-data:1.0.1;async:2.6.3;lodash:4.17.15","isMinimumFixVersionAvailable":true,"minimumFixVersion":"lodash - 4.17.21"},{"packageType":"javascript/Node.js","packageName":"lodash","packageVersion":"0.9.2","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt:0.4.5;lodash:0.9.2","isMinimumFixVersionAvailable":true,"minimumFixVersion":"lodash - 4.17.21"},{"packageType":"javascript/Node.js","packageName":"lodash","packageVersion":"2.4.2","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt:0.4.5;findup-sync:0.1.3;lodash:2.4.2","isMinimumFixVersionAvailable":true,"minimumFixVersion":"lodash - 4.17.21"},{"packageType":"javascript/Node.js","packageName":"lodash","packageVersion":"3.10.1","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"karma:0.12.37;lodash:3.10.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"lodash - 4.17.21"}],"baseBranches":[],"vulnerabilityIdentifier":"CVE-2021-23337","vulnerabilityDetails":"Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337","cvss3Severity":"high","cvss3Score":"7.2","cvss3Metrics":{"A":"High","AC":"Low","PR":"High","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> -->
|
True
|
CVE-2021-23337 (High) detected in multiple libraries - ## CVE-2021-23337 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>lodash-4.17.15.tgz</b>, <b>lodash-0.9.2.tgz</b>, <b>lodash-2.4.2.tgz</b>, <b>lodash-3.10.1.tgz</b></p></summary>
<p>
<details><summary><b>lodash-4.17.15.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz</a></p>
<p>Path to dependency file: fac/package.json</p>
<p>Path to vulnerable library: fac/node_modules/form-data/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- karma-phantomjs-launcher-0.1.4.tgz (Root Library)
- phantomjs-1.9.20.tgz
- request-2.67.0.tgz
- form-data-1.0.1.tgz
- async-2.6.3.tgz
- :x: **lodash-4.17.15.tgz** (Vulnerable Library)
</details>
<details><summary><b>lodash-0.9.2.tgz</b></p></summary>
<p>A utility library delivering consistency, customization, performance, and extras.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-0.9.2.tgz">https://registry.npmjs.org/lodash/-/lodash-0.9.2.tgz</a></p>
<p>Path to dependency file: fac/package.json</p>
<p>Path to vulnerable library: fac/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- grunt-0.4.5.tgz (Root Library)
- :x: **lodash-0.9.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>lodash-2.4.2.tgz</b></p></summary>
<p>A utility library delivering consistency, customization, performance, & extras.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a></p>
<p>Path to dependency file: fac/package.json</p>
<p>Path to vulnerable library: fac/node_modules/grunt-karma/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- grunt-0.4.5.tgz (Root Library)
- findup-sync-0.1.3.tgz
- :x: **lodash-2.4.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>lodash-3.10.1.tgz</b></p></summary>
<p>The modern build of lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz">https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz</a></p>
<p>Path to dependency file: fac/package.json</p>
<p>Path to vulnerable library: fac/node_modules/karma/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- karma-0.12.37.tgz (Root Library)
- :x: **lodash-3.10.1.tgz** (Vulnerable Library)
</details>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
<p>Publish Date: 2021-02-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337>CVE-2021-23337</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.2</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- 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://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c">https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c</a></p>
<p>Release Date: 2021-02-15</p>
<p>Fix Resolution: lodash - 4.17.21</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"lodash","packageVersion":"4.17.15","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"karma-phantomjs-launcher:0.1.4;phantomjs:1.9.20;request:2.67.0;form-data:1.0.1;async:2.6.3;lodash:4.17.15","isMinimumFixVersionAvailable":true,"minimumFixVersion":"lodash - 4.17.21"},{"packageType":"javascript/Node.js","packageName":"lodash","packageVersion":"0.9.2","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt:0.4.5;lodash:0.9.2","isMinimumFixVersionAvailable":true,"minimumFixVersion":"lodash - 4.17.21"},{"packageType":"javascript/Node.js","packageName":"lodash","packageVersion":"2.4.2","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt:0.4.5;findup-sync:0.1.3;lodash:2.4.2","isMinimumFixVersionAvailable":true,"minimumFixVersion":"lodash - 4.17.21"},{"packageType":"javascript/Node.js","packageName":"lodash","packageVersion":"3.10.1","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"karma:0.12.37;lodash:3.10.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"lodash - 4.17.21"}],"baseBranches":[],"vulnerabilityIdentifier":"CVE-2021-23337","vulnerabilityDetails":"Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337","cvss3Severity":"high","cvss3Score":"7.2","cvss3Metrics":{"A":"High","AC":"Low","PR":"High","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> -->
|
non_defect
|
cve high detected in multiple libraries cve high severity vulnerability vulnerable libraries lodash tgz lodash tgz lodash tgz lodash tgz lodash tgz lodash modular utilities library home page a href path to dependency file fac package json path to vulnerable library fac node modules form data node modules lodash package json dependency hierarchy karma phantomjs launcher tgz root library phantomjs tgz request tgz form data tgz async tgz x lodash tgz vulnerable library lodash tgz a utility library delivering consistency customization performance and extras library home page a href path to dependency file fac package json path to vulnerable library fac node modules lodash package json dependency hierarchy grunt tgz root library x lodash tgz vulnerable library lodash tgz a utility library delivering consistency customization performance extras library home page a href path to dependency file fac package json path to vulnerable library fac node modules grunt karma node modules lodash package json dependency hierarchy grunt tgz root library findup sync tgz x lodash tgz vulnerable library lodash tgz the modern build of lodash modular utilities library home page a href path to dependency file fac package json path to vulnerable library fac node modules karma node modules lodash package json dependency hierarchy karma tgz root library x lodash tgz vulnerable library vulnerability details lodash versions prior to are vulnerable to command injection via the template function publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low 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 lodash isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree karma phantomjs launcher phantomjs request form data async lodash isminimumfixversionavailable true minimumfixversion lodash packagetype javascript node js packagename lodash packageversion packagefilepaths istransitivedependency true dependencytree grunt lodash isminimumfixversionavailable true minimumfixversion lodash packagetype javascript node js packagename lodash packageversion packagefilepaths istransitivedependency true dependencytree grunt findup sync lodash isminimumfixversionavailable true minimumfixversion lodash packagetype javascript node js packagename lodash packageversion packagefilepaths istransitivedependency true dependencytree karma lodash isminimumfixversionavailable true minimumfixversion lodash basebranches vulnerabilityidentifier cve vulnerabilitydetails lodash versions prior to are vulnerable to command injection via the template function vulnerabilityurl
| 0
|
651,692
| 21,485,347,989
|
IssuesEvent
|
2022-04-26 22:28:08
|
okTurtles/group-income
|
https://api.github.com/repos/okTurtles/group-income
|
closed
|
Remove the deprecated Mailbox/Inbox
|
Kind:Enhancement App:Frontend Priority:High Note:UI/UX
|
### Problem
This page and its navbar item should be removed:
<img width="571" alt="Screen Shot 2022-04-21 at 10 58 36 PM" src="https://user-images.githubusercontent.com/138706/164612627-a9c565d9-af32-4475-b963-c3cc7d48abb3.png">
### Solution
Remove from the project.
|
1.0
|
Remove the deprecated Mailbox/Inbox - ### Problem
This page and its navbar item should be removed:
<img width="571" alt="Screen Shot 2022-04-21 at 10 58 36 PM" src="https://user-images.githubusercontent.com/138706/164612627-a9c565d9-af32-4475-b963-c3cc7d48abb3.png">
### Solution
Remove from the project.
|
non_defect
|
remove the deprecated mailbox inbox problem this page and its navbar item should be removed img width alt screen shot at pm src solution remove from the project
| 0
|
45,858
| 13,055,810,395
|
IssuesEvent
|
2020-07-30 02:48:24
|
icecube-trac/tix2
|
https://api.github.com/repos/icecube-trac/tix2
|
opened
|
GLshovel File-> Open I3 file on Mac OS 10.5 hangs (Trac #146)
|
IceTray Incomplete Migration Migrated from Trac defect
|
Migrated from https://code.icecube.wisc.edu/ticket/146
```json
{
"status": "closed",
"changetime": "2009-03-06T01:42:38",
"description": "",
"reporter": "blaufuss",
"cc": "",
"resolution": "fixed",
"_ts": "1236303758000000",
"component": "IceTray",
"summary": "GLshovel File-> Open I3 file on Mac OS 10.5 hangs",
"priority": "normal",
"keywords": "",
"time": "2008-10-22T16:12:45",
"milestone": "",
"owner": "troy",
"type": "defect"
}
```
|
1.0
|
GLshovel File-> Open I3 file on Mac OS 10.5 hangs (Trac #146) - Migrated from https://code.icecube.wisc.edu/ticket/146
```json
{
"status": "closed",
"changetime": "2009-03-06T01:42:38",
"description": "",
"reporter": "blaufuss",
"cc": "",
"resolution": "fixed",
"_ts": "1236303758000000",
"component": "IceTray",
"summary": "GLshovel File-> Open I3 file on Mac OS 10.5 hangs",
"priority": "normal",
"keywords": "",
"time": "2008-10-22T16:12:45",
"milestone": "",
"owner": "troy",
"type": "defect"
}
```
|
defect
|
glshovel file open file on mac os hangs trac migrated from json status closed changetime description reporter blaufuss cc resolution fixed ts component icetray summary glshovel file open file on mac os hangs priority normal keywords time milestone owner troy type defect
| 1
|
30,087
| 6,019,264,830
|
IssuesEvent
|
2017-06-07 14:11:30
|
idaholab/raven
|
https://api.github.com/repos/idaholab/raven
|
closed
|
CSV writer in Dymola code interface
|
defect priority_normal
|
--------
Issue Description
--------
##### What did you see?
The csv writer in the Dymola code interface places quotes around variable names that contin commas, i.e. 3 variables 1) a 2) b,c 3) d will be output as a,"b,c",d.
The RAVEN csv reader does not support this convention.
##### Do you have a suggested fix for the development team?
The Dymola code interface csv writer should replace commas in variable names with another character.
----------------
For Change Control Board: Issue Review
----------------
This review should occur before any development is performed as a response to this issue.
- [x] 1. Is it tagged with a type: defect or improvement?
- [x] 2. Is it tagged with a priority: critical, normal or minor?
- [x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
- [x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users. __it does not produce wrong results, as instead the run will error out; this is also a fairly fringe case.__
- [x] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)
-------
For Change Control Board: Issue Closure
-------
This review should occur when the issue is imminently going to be closed.
- [x] 1. If the issue is a defect, is the defect fixed?
- [x] 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
- [ ] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)? __The current group of users has been aware; however, it might be worthwhile to send an email to the user list.__
- [x] 4. If the issue is a defect, does it impact the latest stable branch? If yes, is there any issue tagged with stable (create if needed)? __no stable merge needed__
- [x] 5. If the issue is being closed without a merge request, has an explanation of why it is being closed been provided?
|
1.0
|
CSV writer in Dymola code interface - --------
Issue Description
--------
##### What did you see?
The csv writer in the Dymola code interface places quotes around variable names that contin commas, i.e. 3 variables 1) a 2) b,c 3) d will be output as a,"b,c",d.
The RAVEN csv reader does not support this convention.
##### Do you have a suggested fix for the development team?
The Dymola code interface csv writer should replace commas in variable names with another character.
----------------
For Change Control Board: Issue Review
----------------
This review should occur before any development is performed as a response to this issue.
- [x] 1. Is it tagged with a type: defect or improvement?
- [x] 2. Is it tagged with a priority: critical, normal or minor?
- [x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
- [x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users. __it does not produce wrong results, as instead the run will error out; this is also a fairly fringe case.__
- [x] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)
-------
For Change Control Board: Issue Closure
-------
This review should occur when the issue is imminently going to be closed.
- [x] 1. If the issue is a defect, is the defect fixed?
- [x] 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
- [ ] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)? __The current group of users has been aware; however, it might be worthwhile to send an email to the user list.__
- [x] 4. If the issue is a defect, does it impact the latest stable branch? If yes, is there any issue tagged with stable (create if needed)? __no stable merge needed__
- [x] 5. If the issue is being closed without a merge request, has an explanation of why it is being closed been provided?
|
defect
|
csv writer in dymola code interface issue description what did you see the csv writer in the dymola code interface places quotes around variable names that contin commas i e variables a b c d will be output as a b c d the raven csv reader does not support this convention do you have a suggested fix for the development team the dymola code interface csv writer should replace commas in variable names with another character for change control board issue review this review should occur before any development is performed as a response to this issue is it tagged with a type defect or improvement is it tagged with a priority critical normal or minor if it will impact requirements or requirements tests is it tagged with requirements if it is a defect can it cause wrong results for users if so an email needs to be sent to the users it does not produce wrong results as instead the run will error out this is also a fairly fringe case is a rationale provided such as explaining why the improvement is needed or why current code is wrong for change control board issue closure this review should occur when the issue is imminently going to be closed if the issue is a defect is the defect fixed if the issue is a defect is the defect tested for in the regression test system if not explain why not if the issue can impact users has an email to the users group been written the email should specify if the defect impacts stable or master the current group of users has been aware however it might be worthwhile to send an email to the user list if the issue is a defect does it impact the latest stable branch if yes is there any issue tagged with stable create if needed no stable merge needed if the issue is being closed without a merge request has an explanation of why it is being closed been provided
| 1
|
177,198
| 28,370,675,275
|
IssuesEvent
|
2023-04-12 16:44:05
|
department-of-veterans-affairs/va.gov-team
|
https://api.github.com/repos/department-of-veterans-affairs/va.gov-team
|
reopened
|
SB Phase 2: Define
|
service-design
|
## Align on the goal and the scope of the mapping initiative
A service blueprint should have a very specific service, or portion of a service, to focus on. Furthermore, this portion should be agreed upon, so you’ll want to involve all relevant stakeholders in this phase.
If anything, err on the side of being small and focused when identifying the scenario to evaluate.
## Steps:
- [x] Pre-populate our [workshop template](https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1678224119326/7ed7cb3855c6bea8fa7be41a40ed6dcb3cea8061?sender=u311209e67c8c21a1b37a8167)
- [x] Conduct team workshop as a test run
- [x] Establish where we as a team think the scenario [Begins and Ends](https://lucid.app/lucidchart/e2d771f0-6d82-4f13-8411-9e983ec0687d/edit?invitationId=inv_fc1e26fe-e5c7-4a42-902d-2999a568b8b6&page=HWuo9Qg1GJTA#)
- [x] Evaluate who we believe the appropriate [stakeholders and SMEs](https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1678224119326/7ed7cb3855c6bea8fa7be41a40ed6dcb3cea8061?wid=6-1677884991294) might be
- [x] Reach out to Platform Leadership for more guidance if necessary
- [x] Follow guidance outlined in our [Phase 2: Define](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2436169785/Phase+2+Define) documentation to prep for definition activities: organize Mural template and other supporting documents
- [x] Establish and align on a [kickoff plan](https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1679427985259/3ae96553b4caa4f8f3d24b6cb7cb40d58d2ec333?sender=u311209e67c8c21a1b37a8167) and ways of working: prepare the messaging needed to convey what to expect and how we'll collaborate
### Notes/References:
### Goals:
- Define the desired outcome of the map.
- Why are we mapping this thing?
- What do we want to learn?
### Scope: (8-12 customer actions is a good target)
-Fine tune w/ stakeholders where the specific Start and Stop of the scenario should be
-Will this be focused on the Current State or Future State
-Is there an existing process that they think they want mapped?
### Clarifying Questions to ask:
1. Stakeholders: Will the requesting team be the ultimate consumer of this product (that is, are they doing this to show to a stakeholder of theirs?)
2. Our team: How will we measure success?
### Needs/Opportunities/Challenges:
Set expectations on the time it takes to create such a blueprint
## Acceptance Criteria
- [x] Kickoff plan is ready to share
|
1.0
|
SB Phase 2: Define - ## Align on the goal and the scope of the mapping initiative
A service blueprint should have a very specific service, or portion of a service, to focus on. Furthermore, this portion should be agreed upon, so you’ll want to involve all relevant stakeholders in this phase.
If anything, err on the side of being small and focused when identifying the scenario to evaluate.
## Steps:
- [x] Pre-populate our [workshop template](https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1678224119326/7ed7cb3855c6bea8fa7be41a40ed6dcb3cea8061?sender=u311209e67c8c21a1b37a8167)
- [x] Conduct team workshop as a test run
- [x] Establish where we as a team think the scenario [Begins and Ends](https://lucid.app/lucidchart/e2d771f0-6d82-4f13-8411-9e983ec0687d/edit?invitationId=inv_fc1e26fe-e5c7-4a42-902d-2999a568b8b6&page=HWuo9Qg1GJTA#)
- [x] Evaluate who we believe the appropriate [stakeholders and SMEs](https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1678224119326/7ed7cb3855c6bea8fa7be41a40ed6dcb3cea8061?wid=6-1677884991294) might be
- [x] Reach out to Platform Leadership for more guidance if necessary
- [x] Follow guidance outlined in our [Phase 2: Define](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2436169785/Phase+2+Define) documentation to prep for definition activities: organize Mural template and other supporting documents
- [x] Establish and align on a [kickoff plan](https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1679427985259/3ae96553b4caa4f8f3d24b6cb7cb40d58d2ec333?sender=u311209e67c8c21a1b37a8167) and ways of working: prepare the messaging needed to convey what to expect and how we'll collaborate
### Notes/References:
### Goals:
- Define the desired outcome of the map.
- Why are we mapping this thing?
- What do we want to learn?
### Scope: (8-12 customer actions is a good target)
-Fine tune w/ stakeholders where the specific Start and Stop of the scenario should be
-Will this be focused on the Current State or Future State
-Is there an existing process that they think they want mapped?
### Clarifying Questions to ask:
1. Stakeholders: Will the requesting team be the ultimate consumer of this product (that is, are they doing this to show to a stakeholder of theirs?)
2. Our team: How will we measure success?
### Needs/Opportunities/Challenges:
Set expectations on the time it takes to create such a blueprint
## Acceptance Criteria
- [x] Kickoff plan is ready to share
|
non_defect
|
sb phase define align on the goal and the scope of the mapping initiative a service blueprint should have a very specific service or portion of a service to focus on furthermore this portion should be agreed upon so you’ll want to involve all relevant stakeholders in this phase if anything err on the side of being small and focused when identifying the scenario to evaluate steps pre populate our conduct team workshop as a test run establish where we as a team think the scenario evaluate who we believe the appropriate might be reach out to platform leadership for more guidance if necessary follow guidance outlined in our documentation to prep for definition activities organize mural template and other supporting documents establish and align on a and ways of working prepare the messaging needed to convey what to expect and how we ll collaborate notes references goals define the desired outcome of the map why are we mapping this thing what do we want to learn scope customer actions is a good target fine tune w stakeholders where the specific start and stop of the scenario should be will this be focused on the current state or future state is there an existing process that they think they want mapped clarifying questions to ask stakeholders will the requesting team be the ultimate consumer of this product that is are they doing this to show to a stakeholder of theirs our team how will we measure success needs opportunities challenges set expectations on the time it takes to create such a blueprint acceptance criteria kickoff plan is ready to share
| 0
|
50,540
| 21,176,263,592
|
IssuesEvent
|
2022-04-08 00:21:49
|
elastic/kibana
|
https://api.github.com/repos/elastic/kibana
|
closed
|
[test-failed]: X-Pack Reporting API Integration Tests1.x-pack/test/reporting_api_integration/reporting_and_security/spaces·ts - Reporting APIs Exports and Spaces should complete a job of PDF export of a dashboard in non-default space
|
failed-test test-cloud Team:Reporting Services v8.2.0
|
**Version: 8.2.0**
**Class: X-Pack Reporting API Integration Tests1.x-pack/test/reporting_api_integration/reporting_and_security/spaces·ts**
**Stack Trace:**
```
[Error [TimeoutError]: Timeout has occurred] { stack: undefined }
```
**Other test failures:**
_Test Report: https://internal-ci.elastic.co/view/Stack%20Tests/job/elastic+estf-cloud-kibana-tests/3093/testReport/_
|
1.0
|
[test-failed]: X-Pack Reporting API Integration Tests1.x-pack/test/reporting_api_integration/reporting_and_security/spaces·ts - Reporting APIs Exports and Spaces should complete a job of PDF export of a dashboard in non-default space - **Version: 8.2.0**
**Class: X-Pack Reporting API Integration Tests1.x-pack/test/reporting_api_integration/reporting_and_security/spaces·ts**
**Stack Trace:**
```
[Error [TimeoutError]: Timeout has occurred] { stack: undefined }
```
**Other test failures:**
_Test Report: https://internal-ci.elastic.co/view/Stack%20Tests/job/elastic+estf-cloud-kibana-tests/3093/testReport/_
|
non_defect
|
x pack reporting api integration x pack test reporting api integration reporting and security spaces·ts reporting apis exports and spaces should complete a job of pdf export of a dashboard in non default space version class x pack reporting api integration x pack test reporting api integration reporting and security spaces·ts stack trace timeout has occurred stack undefined other test failures test report
| 0
|
18,690
| 3,080,680,562
|
IssuesEvent
|
2015-08-22 00:32:16
|
jameslh/pagedown
|
https://api.github.com/repos/jameslh/pagedown
|
closed
|
"Add heading" with no selected text doesn't add heading.
|
auto-migrated Priority-Medium Type-Defect
|
```
What steps will reproduce the problem?
1. Type in "balpha is awesome at "
2. Hit Ctrl-H or "Add header"
What is the expected output? What do you see instead?
balpha is awesome at ## Heading ##
(as opposed to)
balpha is awesome at
## Heading ##
What version of the product are you using? On what operating system?
Repro'd on Discourse and SE.
Please provide any additional information below.
I _think_ it would be enough to change
https://code.google.com/p/pagedown/source/browse/Markdown.Editor.js#2182 so
that chunkStart and chunkEnd also add newlines, perhaps like so:
// If we clicked the button with no selected text, we just
// make a level 2 hash header around some default text.
if (!chunk.selection) {
chunk.startTag = "\n\n## ";
chunk.selection = this.getString("headingexample");
chunk.endTag = " ##\n\n";
return;
}
(Sorry, I don't have Mercurial or Node installed right now.)
```
Original issue reported on code.google.com by `badpazzword@gmail.com` on 22 Sep 2014 at 9:28
|
1.0
|
"Add heading" with no selected text doesn't add heading. - ```
What steps will reproduce the problem?
1. Type in "balpha is awesome at "
2. Hit Ctrl-H or "Add header"
What is the expected output? What do you see instead?
balpha is awesome at ## Heading ##
(as opposed to)
balpha is awesome at
## Heading ##
What version of the product are you using? On what operating system?
Repro'd on Discourse and SE.
Please provide any additional information below.
I _think_ it would be enough to change
https://code.google.com/p/pagedown/source/browse/Markdown.Editor.js#2182 so
that chunkStart and chunkEnd also add newlines, perhaps like so:
// If we clicked the button with no selected text, we just
// make a level 2 hash header around some default text.
if (!chunk.selection) {
chunk.startTag = "\n\n## ";
chunk.selection = this.getString("headingexample");
chunk.endTag = " ##\n\n";
return;
}
(Sorry, I don't have Mercurial or Node installed right now.)
```
Original issue reported on code.google.com by `badpazzword@gmail.com` on 22 Sep 2014 at 9:28
|
defect
|
add heading with no selected text doesn t add heading what steps will reproduce the problem type in balpha is awesome at hit ctrl h or add header what is the expected output what do you see instead balpha is awesome at heading as opposed to balpha is awesome at heading what version of the product are you using on what operating system repro d on discourse and se please provide any additional information below i think it would be enough to change so that chunkstart and chunkend also add newlines perhaps like so if we clicked the button with no selected text we just make a level hash header around some default text if chunk selection chunk starttag n n chunk selection this getstring headingexample chunk endtag n n return sorry i don t have mercurial or node installed right now original issue reported on code google com by badpazzword gmail com on sep at
| 1
|
27,789
| 5,103,087,064
|
IssuesEvent
|
2017-01-04 20:17:25
|
mkeymolen/DavisVantage.WeatherReader
|
https://api.github.com/repos/mkeymolen/DavisVantage.WeatherReader
|
closed
|
sometimes there is an infinite loop while trying to read weatherdata
|
defect
|
if the response from the console to the read command is empty, the library is stuck in an infinite loop while trying to search the ACK response byte
|
1.0
|
sometimes there is an infinite loop while trying to read weatherdata - if the response from the console to the read command is empty, the library is stuck in an infinite loop while trying to search the ACK response byte
|
defect
|
sometimes there is an infinite loop while trying to read weatherdata if the response from the console to the read command is empty the library is stuck in an infinite loop while trying to search the ack response byte
| 1
|
128,041
| 10,512,496,419
|
IssuesEvent
|
2019-09-27 18:03:44
|
MicrosoftDocs/visualstudio-docs
|
https://api.github.com/repos/MicrosoftDocs/visualstudio-docs
|
closed
|
How to do this in VS 2019?
|
Pri2 area - C++ area - test doc-bug visual-studio-windows/prod vs-ide-test/tech
|
I tried to do this in VS 2019 preview, but it appears to be not yet available?
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: f45fbddc-51f2-1c42-eaf2-f78e6220a9e7
* Version Independent ID: 1ce72223-80ab-651a-40f3-dc8112b2a3cf
* Content: [How to use Boost.Test for C++ - Visual Studio](https://docs.microsoft.com/en-us/visualstudio/test/how-to-use-boost-test-for-cpp?view=vs-2019#feedback)
* Content Source: [docs/test/how-to-use-boost-test-for-cpp.md](https://github.com/MicrosoftDocs/visualstudio-docs/blob/master/docs/test/how-to-use-boost-test-for-cpp.md)
* Product: **visual-studio-windows**
* Technology: **vs-ide-test**
* GitHub Login: @mikeblome
* Microsoft Alias: **mblome**
|
2.0
|
How to do this in VS 2019? - I tried to do this in VS 2019 preview, but it appears to be not yet available?
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: f45fbddc-51f2-1c42-eaf2-f78e6220a9e7
* Version Independent ID: 1ce72223-80ab-651a-40f3-dc8112b2a3cf
* Content: [How to use Boost.Test for C++ - Visual Studio](https://docs.microsoft.com/en-us/visualstudio/test/how-to-use-boost-test-for-cpp?view=vs-2019#feedback)
* Content Source: [docs/test/how-to-use-boost-test-for-cpp.md](https://github.com/MicrosoftDocs/visualstudio-docs/blob/master/docs/test/how-to-use-boost-test-for-cpp.md)
* Product: **visual-studio-windows**
* Technology: **vs-ide-test**
* GitHub Login: @mikeblome
* Microsoft Alias: **mblome**
|
non_defect
|
how to do this in vs i tried to do this in vs preview but it appears to be not yet available 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 visual studio windows technology vs ide test github login mikeblome microsoft alias mblome
| 0
|
53,658
| 11,101,472,954
|
IssuesEvent
|
2019-12-16 21:31:04
|
aws/aws-cdk
|
https://api.github.com/repos/aws/aws-cdk
|
closed
|
How to deploy SPA to S3 using CDK in a pipeline
|
closing-soon-if-no-response guidance package/codepipeline
|
I have a single page react application that I want to host in S3. The source is in git and I would like to set up a Pipeline such that when I push to master it fetches the source, builds it and deploys to S3. Pretty straight forward. I have created a CDK stack for deploying to S3, and it looks like this:
```ts
import { Construct, StackProps, Stack, RemovalPolicy, CfnParameter } from '@aws-cdk/core';
import { Bucket, HttpMethods } from "@aws-cdk/aws-s3";
import { BucketDeployment, Source, ISource } from "@aws-cdk/aws-s3-deployment";
import { CloudFrontWebDistribution } from '@aws-cdk/aws-cloudfront';
export default function createReactStack(scope: Construct, name: string, props?: StackProps) {
const stack = new Stack(scope, `${name}-React`, props);
// This works locally...
const source = Source.asset('../react/build');
// ... but in the pipeline I need the following line
const source = createSourceAsset(stack);
const bucket = createBucket(stack);
createDeploySourceToBucket(stack, source, bucket);
createCloudFront(stack, bucket);
return stack;
}
function createSourceAsset(stack: Stack) {
const bucketName = new CfnParameter(stack, `${stack.stackName}-bucketName`).valueAsString;
const zipFile = new CfnParameter(stack, `${stack.stackName}-zipFile`).valueAsString;
return Source.bucket(Bucket.fromBucketName(stack, 'bucketName', bucketName), zipFile);
}
function createBucket(stack: Stack): Bucket {
return new Bucket(stack, `${stack.stackName}.Bucket`, {
removalPolicy: RemovalPolicy.DESTROY,
websiteIndexDocument: 'index.html',
websiteErrorDocument: 'index.html',
publicReadAccess: true,
cors: [
{
allowedOrigins: ['*'],
allowedMethods: [HttpMethods.GET],
}
]
});
}
function createDeploySourceToBucket(stack: Stack, source: ISource, bucket: Bucket) {
return new BucketDeployment(stack, `${stack.stackName}.BucketDeployment`, {
sources: [source],
destinationBucket: bucket
});
}
function createCloudFront(stack: Stack, bucket: Bucket) {
new CloudFrontWebDistribution(stack, `${stack.stackName}.CloudFront`, {
originConfigs: [
{
s3OriginSource: {
s3BucketSource: bucket
},
behaviors: [
{ isDefaultBehavior: true }
]
}
]
});
}
```
This works well from a local environment, I'm able to run `cdk synth` and `cdk deploy` to deploy this stack.
But I don't want to manually deploy it, I want to set up a pipeline to deploy it. My pipeline has 4 stages:
* Get the source (using `S3SourceAction`)
* Build the react SPA app (using `CodeBuildAction`)
* Synth the CloudFormation templates (using `CodeBuildAction`)
* Deploy the stack based on the template (using `CloudFormationCreateUpdateStackAction`)
The first three steps are straight forward, but the last step seems impossible to achieve.
I've tried using `CloudFormationCreateUpdateStackAction`, like this:
```ts
new CloudFormationCreateUpdateStackAction({
actionName: `Deploy-Cdk`,
templatePath: input.atPath(
`${stackName}.template.json`
),
stackName,
adminPermissions: true,
extraInputs: [source],
parameterOverrides: {
[`${stackName}-bucketName`]: source.s3Location.bucketName,
[`${stackName}-zipFile`]: source.s3Location.objectKey
}
})
```
But when I do I get an error in the pipeline like this:

These seem to be parameters needed by `BucketDeployment`, and their values are magically set by `cdk deploy` but not by `CloudFormationCreateUpdateStackAction`. How can I make this work in Pipeline? The assetParameters seem to have two hashes as part of them, how can I generate them correctly?
|
1.0
|
How to deploy SPA to S3 using CDK in a pipeline - I have a single page react application that I want to host in S3. The source is in git and I would like to set up a Pipeline such that when I push to master it fetches the source, builds it and deploys to S3. Pretty straight forward. I have created a CDK stack for deploying to S3, and it looks like this:
```ts
import { Construct, StackProps, Stack, RemovalPolicy, CfnParameter } from '@aws-cdk/core';
import { Bucket, HttpMethods } from "@aws-cdk/aws-s3";
import { BucketDeployment, Source, ISource } from "@aws-cdk/aws-s3-deployment";
import { CloudFrontWebDistribution } from '@aws-cdk/aws-cloudfront';
export default function createReactStack(scope: Construct, name: string, props?: StackProps) {
const stack = new Stack(scope, `${name}-React`, props);
// This works locally...
const source = Source.asset('../react/build');
// ... but in the pipeline I need the following line
const source = createSourceAsset(stack);
const bucket = createBucket(stack);
createDeploySourceToBucket(stack, source, bucket);
createCloudFront(stack, bucket);
return stack;
}
function createSourceAsset(stack: Stack) {
const bucketName = new CfnParameter(stack, `${stack.stackName}-bucketName`).valueAsString;
const zipFile = new CfnParameter(stack, `${stack.stackName}-zipFile`).valueAsString;
return Source.bucket(Bucket.fromBucketName(stack, 'bucketName', bucketName), zipFile);
}
function createBucket(stack: Stack): Bucket {
return new Bucket(stack, `${stack.stackName}.Bucket`, {
removalPolicy: RemovalPolicy.DESTROY,
websiteIndexDocument: 'index.html',
websiteErrorDocument: 'index.html',
publicReadAccess: true,
cors: [
{
allowedOrigins: ['*'],
allowedMethods: [HttpMethods.GET],
}
]
});
}
function createDeploySourceToBucket(stack: Stack, source: ISource, bucket: Bucket) {
return new BucketDeployment(stack, `${stack.stackName}.BucketDeployment`, {
sources: [source],
destinationBucket: bucket
});
}
function createCloudFront(stack: Stack, bucket: Bucket) {
new CloudFrontWebDistribution(stack, `${stack.stackName}.CloudFront`, {
originConfigs: [
{
s3OriginSource: {
s3BucketSource: bucket
},
behaviors: [
{ isDefaultBehavior: true }
]
}
]
});
}
```
This works well from a local environment, I'm able to run `cdk synth` and `cdk deploy` to deploy this stack.
But I don't want to manually deploy it, I want to set up a pipeline to deploy it. My pipeline has 4 stages:
* Get the source (using `S3SourceAction`)
* Build the react SPA app (using `CodeBuildAction`)
* Synth the CloudFormation templates (using `CodeBuildAction`)
* Deploy the stack based on the template (using `CloudFormationCreateUpdateStackAction`)
The first three steps are straight forward, but the last step seems impossible to achieve.
I've tried using `CloudFormationCreateUpdateStackAction`, like this:
```ts
new CloudFormationCreateUpdateStackAction({
actionName: `Deploy-Cdk`,
templatePath: input.atPath(
`${stackName}.template.json`
),
stackName,
adminPermissions: true,
extraInputs: [source],
parameterOverrides: {
[`${stackName}-bucketName`]: source.s3Location.bucketName,
[`${stackName}-zipFile`]: source.s3Location.objectKey
}
})
```
But when I do I get an error in the pipeline like this:

These seem to be parameters needed by `BucketDeployment`, and their values are magically set by `cdk deploy` but not by `CloudFormationCreateUpdateStackAction`. How can I make this work in Pipeline? The assetParameters seem to have two hashes as part of them, how can I generate them correctly?
|
non_defect
|
how to deploy spa to using cdk in a pipeline i have a single page react application that i want to host in the source is in git and i would like to set up a pipeline such that when i push to master it fetches the source builds it and deploys to pretty straight forward i have created a cdk stack for deploying to and it looks like this ts import construct stackprops stack removalpolicy cfnparameter from aws cdk core import bucket httpmethods from aws cdk aws import bucketdeployment source isource from aws cdk aws deployment import cloudfrontwebdistribution from aws cdk aws cloudfront export default function createreactstack scope construct name string props stackprops const stack new stack scope name react props this works locally const source source asset react build but in the pipeline i need the following line const source createsourceasset stack const bucket createbucket stack createdeploysourcetobucket stack source bucket createcloudfront stack bucket return stack function createsourceasset stack stack const bucketname new cfnparameter stack stack stackname bucketname valueasstring const zipfile new cfnparameter stack stack stackname zipfile valueasstring return source bucket bucket frombucketname stack bucketname bucketname zipfile function createbucket stack stack bucket return new bucket stack stack stackname bucket removalpolicy removalpolicy destroy websiteindexdocument index html websiteerrordocument index html publicreadaccess true cors allowedorigins allowedmethods function createdeploysourcetobucket stack stack source isource bucket bucket return new bucketdeployment stack stack stackname bucketdeployment sources destinationbucket bucket function createcloudfront stack stack bucket bucket new cloudfrontwebdistribution stack stack stackname cloudfront originconfigs bucket behaviors isdefaultbehavior true this works well from a local environment i m able to run cdk synth and cdk deploy to deploy this stack but i don t want to manually deploy it i want to set up a pipeline to deploy it my pipeline has stages get the source using build the react spa app using codebuildaction synth the cloudformation templates using codebuildaction deploy the stack based on the template using cloudformationcreateupdatestackaction the first three steps are straight forward but the last step seems impossible to achieve i ve tried using cloudformationcreateupdatestackaction like this ts new cloudformationcreateupdatestackaction actionname deploy cdk templatepath input atpath stackname template json stackname adminpermissions true extrainputs parameteroverrides source bucketname source objectkey but when i do i get an error in the pipeline like this these seem to be parameters needed by bucketdeployment and their values are magically set by cdk deploy but not by cloudformationcreateupdatestackaction how can i make this work in pipeline the assetparameters seem to have two hashes as part of them how can i generate them correctly
| 0
|
29,211
| 5,609,485,344
|
IssuesEvent
|
2017-04-02 01:29:24
|
Cockatrice/Cockatrice
|
https://api.github.com/repos/Cockatrice/Cockatrice
|
closed
|
Cannot add/delete buddies
|
App - Cockatrice Defect - Regression
|
This issue was unfortunately caused by #2501.
This is a bad regression that causes the "Add/remove buddylist/ignorelist" buttons to not populate.
Build before merge:
<img width="227" alt="screenshot 2017-04-01 01 44 13" src="https://cloud.githubusercontent.com/assets/7460172/24575759/b782025c-167c-11e7-9c6d-68ed3acf47fd.png">
Build after merge:
<img width="233" alt="screenshot 2017-04-01 01 43 28" src="https://cloud.githubusercontent.com/assets/7460172/24575757/b06ab1bc-167c-11e7-9fb0-9b091cc1f59c.png">
|
1.0
|
Cannot add/delete buddies - This issue was unfortunately caused by #2501.
This is a bad regression that causes the "Add/remove buddylist/ignorelist" buttons to not populate.
Build before merge:
<img width="227" alt="screenshot 2017-04-01 01 44 13" src="https://cloud.githubusercontent.com/assets/7460172/24575759/b782025c-167c-11e7-9c6d-68ed3acf47fd.png">
Build after merge:
<img width="233" alt="screenshot 2017-04-01 01 43 28" src="https://cloud.githubusercontent.com/assets/7460172/24575757/b06ab1bc-167c-11e7-9fb0-9b091cc1f59c.png">
|
defect
|
cannot add delete buddies this issue was unfortunately caused by this is a bad regression that causes the add remove buddylist ignorelist buttons to not populate build before merge img width alt screenshot src build after merge img width alt screenshot src
| 1
|
54,869
| 23,347,813,759
|
IssuesEvent
|
2022-08-09 19:48:33
|
cityofaustin/atd-data-tech
|
https://api.github.com/repos/cityofaustin/atd-data-tech
|
closed
|
Execute 4 tasks supporting the test deployment system
|
Workgroup: DTS Service: Dev Need: 1-Must Have Product: Moped Type: DevOps
|
During a conversation with @mddilley on July 19th, 2022, we agreed that these would be good tasks for me to work on next in support of our joint work on the test development system:
* [x] Use Mike's work re: postgres, change to the `graphql-engine` image
* [x] Write a function which can do `slug = generate_slug(feature_branch)`
* [x] Write a MVP github action which invokes a prefect flow passing an argument
* [x] Extend the ECS to block until the ECS containers become responsive
|
1.0
|
Execute 4 tasks supporting the test deployment system - During a conversation with @mddilley on July 19th, 2022, we agreed that these would be good tasks for me to work on next in support of our joint work on the test development system:
* [x] Use Mike's work re: postgres, change to the `graphql-engine` image
* [x] Write a function which can do `slug = generate_slug(feature_branch)`
* [x] Write a MVP github action which invokes a prefect flow passing an argument
* [x] Extend the ECS to block until the ECS containers become responsive
|
non_defect
|
execute tasks supporting the test deployment system during a conversation with mddilley on july we agreed that these would be good tasks for me to work on next in support of our joint work on the test development system use mike s work re postgres change to the graphql engine image write a function which can do slug generate slug feature branch write a mvp github action which invokes a prefect flow passing an argument extend the ecs to block until the ecs containers become responsive
| 0
|
121,181
| 12,110,682,000
|
IssuesEvent
|
2020-04-21 10:51:10
|
ga-devfront/scroll-listener
|
https://api.github.com/repos/ga-devfront/scroll-listener
|
opened
|
Update README
|
documentation
|
The README should coutain :
- a quick description of npm.
- npm & depot badges.
- npm installation.
- npm utilisation.
- npm options.
- contributors.
- license.
|
1.0
|
Update README - The README should coutain :
- a quick description of npm.
- npm & depot badges.
- npm installation.
- npm utilisation.
- npm options.
- contributors.
- license.
|
non_defect
|
update readme the readme should coutain a quick description of npm npm depot badges npm installation npm utilisation npm options contributors license
| 0
|
315,189
| 23,547,857,889
|
IssuesEvent
|
2022-08-21 11:46:07
|
alpacahq/alpaca-py
|
https://api.github.com/repos/alpacahq/alpaca-py
|
closed
|
[Question]: Lack of latest trade example in docs
|
documentation enhancement
|
### Question form pre-submit checklist.
- [X] I have searched the existing issues to ensure there isn't already an issue about this question.
- [X] My question has to do with the Python SDK and isn't a general question about the API. (If it is please open your issue [here](https://github.com/alpacahq/Alpaca-API))
- [X] My question isn't about how to do a specific algorithm or asking for trade advice (answers to these are outside the scope of this repo).
### Question
I have searched in Google and documentation page:
https://alpaca.markets/docs/python-sdk/market_data.html
I couldn't find an example on how to get the **latest trade** with `alpaca-py 0.5.3`
With `alpaca-trade-api 2.3.0` is as simple as this: `api.get_latest_trade("AAPL")`
Thanks in advance for your response.
Regards,
|
1.0
|
[Question]: Lack of latest trade example in docs - ### Question form pre-submit checklist.
- [X] I have searched the existing issues to ensure there isn't already an issue about this question.
- [X] My question has to do with the Python SDK and isn't a general question about the API. (If it is please open your issue [here](https://github.com/alpacahq/Alpaca-API))
- [X] My question isn't about how to do a specific algorithm or asking for trade advice (answers to these are outside the scope of this repo).
### Question
I have searched in Google and documentation page:
https://alpaca.markets/docs/python-sdk/market_data.html
I couldn't find an example on how to get the **latest trade** with `alpaca-py 0.5.3`
With `alpaca-trade-api 2.3.0` is as simple as this: `api.get_latest_trade("AAPL")`
Thanks in advance for your response.
Regards,
|
non_defect
|
lack of latest trade example in docs question form pre submit checklist i have searched the existing issues to ensure there isn t already an issue about this question my question has to do with the python sdk and isn t a general question about the api if it is please open your issue my question isn t about how to do a specific algorithm or asking for trade advice answers to these are outside the scope of this repo question i have searched in google and documentation page i couldn t find an example on how to get the latest trade with alpaca py with alpaca trade api is as simple as this api get latest trade aapl thanks in advance for your response regards
| 0
|
84,084
| 16,448,561,189
|
IssuesEvent
|
2021-05-20 23:44:20
|
jhona-tam/Farmacia
|
https://api.github.com/repos/jhona-tam/Farmacia
|
closed
|
Cambiar foto de producto
|
code documentation
|
- cambiar foto de producto con formdata y editar datos de producto
- hacer modal para el form
- mantener diseño y responsive
- ordenar codigo
|
1.0
|
Cambiar foto de producto - - cambiar foto de producto con formdata y editar datos de producto
- hacer modal para el form
- mantener diseño y responsive
- ordenar codigo
|
non_defect
|
cambiar foto de producto cambiar foto de producto con formdata y editar datos de producto hacer modal para el form mantener diseño y responsive ordenar codigo
| 0
|
205,214
| 7,094,746,061
|
IssuesEvent
|
2018-01-13 07:56:56
|
Spartan97/OldTimeHockey
|
https://api.github.com/repos/Spartan97/OldTimeHockey
|
opened
|
Bot to send out replacement manager invites
|
Administrative Low Priority
|
This would be pretty cool - I think we have all the tools to do it:
1. Scrape FF for inactives list (already done)
2. Kick them (this is the part I'm unsure of - would have to get the bot to login as NLF)
3. Find oldest (un-removed) post in wait list thread.
4. Cross-reference registration
5. Send invite and remove post.
|
1.0
|
Bot to send out replacement manager invites - This would be pretty cool - I think we have all the tools to do it:
1. Scrape FF for inactives list (already done)
2. Kick them (this is the part I'm unsure of - would have to get the bot to login as NLF)
3. Find oldest (un-removed) post in wait list thread.
4. Cross-reference registration
5. Send invite and remove post.
|
non_defect
|
bot to send out replacement manager invites this would be pretty cool i think we have all the tools to do it scrape ff for inactives list already done kick them this is the part i m unsure of would have to get the bot to login as nlf find oldest un removed post in wait list thread cross reference registration send invite and remove post
| 0
|
53,586
| 13,261,941,114
|
IssuesEvent
|
2020-08-20 20:48:54
|
icecube-trac/tix4
|
https://api.github.com/repos/icecube-trac/tix4
|
closed
|
[mue] muex can't handle pulse series with only one pulse (Trac #1715)
|
Migrated from Trac combo reconstruction defect
|
when running muex on a pulse series with only one pulse in it, it throws a seg fault:
/cvmfs/icecube.opensciencegrid.org/py2-v1/RHEL_6_x86_64/metaprojects/icerec/V04-11-02/env-shell.sh: line 155: 27823 Segmentation fault PATH=$_PATH LD_LIBRARY_PATH=$_LD_LIBRARY_PATH DYLD_LIBRARY_PATH=$_DYLD_LIBRARY_PATH PYTHONPATH=$_PYTHONPATH ICETRAY_CLASSPATH=$_ICETRAY_CLASSPATH I3_PLATFORM="" I3_SRC=$_I3_SRC I3_BUILD=$_I3_BUILD I3_PORTS=$_I3_PORTS I3_TESTDATA=$_I3_TESTDATA ROOTSYS=/cvmfs/icecube.opensciencegrid.org/py2-v1/RHEL_6_x86_64/i3ports/root-v5.34.18 I3_SHELL=$_I3_SHELL $NEW_SHELL $ARGV
I created a minimal test which can be found here:
/data/user/nwandkowsky/mue/test.py
The command to run can be found at the top of this file.
<details>
<summary><em>Migrated from <a href="https://code.icecube.wisc.edu/projects/icecube/ticket/1715">https://code.icecube.wisc.edu/projects/icecube/ticket/1715</a>, reported by nwandkowskyand owned by dima</em></summary>
<p>
```json
{
"status": "closed",
"changetime": "2019-02-13T14:12:58",
"_ts": "1550067178841456",
"description": "when running muex on a pulse series with only one pulse in it, it throws a seg fault:\n\n/cvmfs/icecube.opensciencegrid.org/py2-v1/RHEL_6_x86_64/metaprojects/icerec/V04-11-02/env-shell.sh: line 155: 27823 Segmentation fault PATH=$_PATH LD_LIBRARY_PATH=$_LD_LIBRARY_PATH DYLD_LIBRARY_PATH=$_DYLD_LIBRARY_PATH PYTHONPATH=$_PYTHONPATH ICETRAY_CLASSPATH=$_ICETRAY_CLASSPATH I3_PLATFORM=\"\" I3_SRC=$_I3_SRC I3_BUILD=$_I3_BUILD I3_PORTS=$_I3_PORTS I3_TESTDATA=$_I3_TESTDATA ROOTSYS=/cvmfs/icecube.opensciencegrid.org/py2-v1/RHEL_6_x86_64/i3ports/root-v5.34.18 I3_SHELL=$_I3_SHELL $NEW_SHELL $ARGV\n\nI created a minimal test which can be found here:\n/data/user/nwandkowsky/mue/test.py\nThe command to run can be found at the top of this file.\n\n\n\n",
"reporter": "nwandkowsky",
"cc": "",
"resolution": "fixed",
"time": "2016-05-20T16:05:41",
"component": "combo reconstruction",
"summary": "[mue] muex can't handle pulse series with only one pulse",
"priority": "major",
"keywords": "",
"milestone": "",
"owner": "dima",
"type": "defect"
}
```
</p>
</details>
|
1.0
|
[mue] muex can't handle pulse series with only one pulse (Trac #1715) - when running muex on a pulse series with only one pulse in it, it throws a seg fault:
/cvmfs/icecube.opensciencegrid.org/py2-v1/RHEL_6_x86_64/metaprojects/icerec/V04-11-02/env-shell.sh: line 155: 27823 Segmentation fault PATH=$_PATH LD_LIBRARY_PATH=$_LD_LIBRARY_PATH DYLD_LIBRARY_PATH=$_DYLD_LIBRARY_PATH PYTHONPATH=$_PYTHONPATH ICETRAY_CLASSPATH=$_ICETRAY_CLASSPATH I3_PLATFORM="" I3_SRC=$_I3_SRC I3_BUILD=$_I3_BUILD I3_PORTS=$_I3_PORTS I3_TESTDATA=$_I3_TESTDATA ROOTSYS=/cvmfs/icecube.opensciencegrid.org/py2-v1/RHEL_6_x86_64/i3ports/root-v5.34.18 I3_SHELL=$_I3_SHELL $NEW_SHELL $ARGV
I created a minimal test which can be found here:
/data/user/nwandkowsky/mue/test.py
The command to run can be found at the top of this file.
<details>
<summary><em>Migrated from <a href="https://code.icecube.wisc.edu/projects/icecube/ticket/1715">https://code.icecube.wisc.edu/projects/icecube/ticket/1715</a>, reported by nwandkowskyand owned by dima</em></summary>
<p>
```json
{
"status": "closed",
"changetime": "2019-02-13T14:12:58",
"_ts": "1550067178841456",
"description": "when running muex on a pulse series with only one pulse in it, it throws a seg fault:\n\n/cvmfs/icecube.opensciencegrid.org/py2-v1/RHEL_6_x86_64/metaprojects/icerec/V04-11-02/env-shell.sh: line 155: 27823 Segmentation fault PATH=$_PATH LD_LIBRARY_PATH=$_LD_LIBRARY_PATH DYLD_LIBRARY_PATH=$_DYLD_LIBRARY_PATH PYTHONPATH=$_PYTHONPATH ICETRAY_CLASSPATH=$_ICETRAY_CLASSPATH I3_PLATFORM=\"\" I3_SRC=$_I3_SRC I3_BUILD=$_I3_BUILD I3_PORTS=$_I3_PORTS I3_TESTDATA=$_I3_TESTDATA ROOTSYS=/cvmfs/icecube.opensciencegrid.org/py2-v1/RHEL_6_x86_64/i3ports/root-v5.34.18 I3_SHELL=$_I3_SHELL $NEW_SHELL $ARGV\n\nI created a minimal test which can be found here:\n/data/user/nwandkowsky/mue/test.py\nThe command to run can be found at the top of this file.\n\n\n\n",
"reporter": "nwandkowsky",
"cc": "",
"resolution": "fixed",
"time": "2016-05-20T16:05:41",
"component": "combo reconstruction",
"summary": "[mue] muex can't handle pulse series with only one pulse",
"priority": "major",
"keywords": "",
"milestone": "",
"owner": "dima",
"type": "defect"
}
```
</p>
</details>
|
defect
|
muex can t handle pulse series with only one pulse trac when running muex on a pulse series with only one pulse in it it throws a seg fault cvmfs icecube opensciencegrid org rhel metaprojects icerec env shell sh line segmentation fault path path ld library path ld library path dyld library path dyld library path pythonpath pythonpath icetray classpath icetray classpath platform src src build build ports ports testdata testdata rootsys cvmfs icecube opensciencegrid org rhel root shell shell new shell argv i created a minimal test which can be found here data user nwandkowsky mue test py the command to run can be found at the top of this file migrated from json status closed changetime ts description when running muex on a pulse series with only one pulse in it it throws a seg fault n n cvmfs icecube opensciencegrid org rhel metaprojects icerec env shell sh line segmentation fault path path ld library path ld library path dyld library path dyld library path pythonpath pythonpath icetray classpath icetray classpath platform src src build build ports ports testdata testdata rootsys cvmfs icecube opensciencegrid org rhel root shell shell new shell argv n ni created a minimal test which can be found here n data user nwandkowsky mue test py nthe command to run can be found at the top of this file n n n n reporter nwandkowsky cc resolution fixed time component combo reconstruction summary muex can t handle pulse series with only one pulse priority major keywords milestone owner dima type defect
| 1
|
69,073
| 22,106,336,180
|
IssuesEvent
|
2022-06-01 17:19:28
|
vector-im/element-web
|
https://api.github.com/repos/vector-im/element-web
|
opened
|
Empty room with error Something went wrong! appeared
|
T-Defect
|
### Steps to reproduce
I'm not sure how to reproduce, the room appeared out of nowhere. I use the mautrix-whatsapp bridge which might (or might not) have triggered the error.
### Outcome
#### What did you expect?
No empty room should appear
#### What happened instead?
An empty room showing an error appeared
### Operating system
Arch Linux
### Browser information
Firefox 102.0b2
### URL for webapp
Private server
### Application version
Element version: 1.10.13 Olm version: 3.2.8
### Homeserver
Dendrite 0.8.7
### Will you send logs?
Yes
|
1.0
|
Empty room with error Something went wrong! appeared - ### Steps to reproduce
I'm not sure how to reproduce, the room appeared out of nowhere. I use the mautrix-whatsapp bridge which might (or might not) have triggered the error.
### Outcome
#### What did you expect?
No empty room should appear
#### What happened instead?
An empty room showing an error appeared
### Operating system
Arch Linux
### Browser information
Firefox 102.0b2
### URL for webapp
Private server
### Application version
Element version: 1.10.13 Olm version: 3.2.8
### Homeserver
Dendrite 0.8.7
### Will you send logs?
Yes
|
defect
|
empty room with error something went wrong appeared steps to reproduce i m not sure how to reproduce the room appeared out of nowhere i use the mautrix whatsapp bridge which might or might not have triggered the error outcome what did you expect no empty room should appear what happened instead an empty room showing an error appeared operating system arch linux browser information firefox url for webapp private server application version element version olm version homeserver dendrite will you send logs yes
| 1
|
70,392
| 23,151,179,305
|
IssuesEvent
|
2022-07-29 08:29:20
|
vector-im/element-web
|
https://api.github.com/repos/vector-im/element-web
|
closed
|
User avatars overlap the message line and timestamp
|
T-Defect S-Tolerable A-Timeline O-Uncommon
|
### Steps to reproduce
1. Start Element.
2. Got to any room and hover over a user's message.
3. Notice the timestamp is partially covered up.
Image to show the issue:

### Outcome
#### What did you expect?
The timestamp shouldn't appear underneath the user avatar.
#### What happened instead?
The message line, and thus the timestamp, is underneath the user avatar.
### Operating system
Arch Linux
### Application version
Element version: 1.11.1, Olm version: 3.2.8
### How did you install the app?
FlatHub
### Homeserver
matrix.org
### Will you send logs?
Yes
|
1.0
|
User avatars overlap the message line and timestamp - ### Steps to reproduce
1. Start Element.
2. Got to any room and hover over a user's message.
3. Notice the timestamp is partially covered up.
Image to show the issue:

### Outcome
#### What did you expect?
The timestamp shouldn't appear underneath the user avatar.
#### What happened instead?
The message line, and thus the timestamp, is underneath the user avatar.
### Operating system
Arch Linux
### Application version
Element version: 1.11.1, Olm version: 3.2.8
### How did you install the app?
FlatHub
### Homeserver
matrix.org
### Will you send logs?
Yes
|
defect
|
user avatars overlap the message line and timestamp steps to reproduce start element got to any room and hover over a user s message notice the timestamp is partially covered up image to show the issue outcome what did you expect the timestamp shouldn t appear underneath the user avatar what happened instead the message line and thus the timestamp is underneath the user avatar operating system arch linux application version element version olm version how did you install the app flathub homeserver matrix org will you send logs yes
| 1
|
160,154
| 25,111,293,424
|
IssuesEvent
|
2022-11-08 20:47:07
|
newjersey/navigator.business.nj.gov
|
https://api.github.com/repos/newjersey/navigator.business.nj.gov
|
closed
|
Accessibility Audit: Navigator Onboarding
|
size: ▪️▪️▪️▪️▪️▪️▪️▪️ Design Accessibility
|
**Problem Statement:** Perform an audit on the Navigator onboarding flows to document and understand how the feature compares to current A compliance.
**Benefit Hypothesis:** With comms doing a marketing push on Navigator soon, it would be beneficial to fix any accessibility issues. - "Digital access needs are sometimes treated as a feature, but we're not leaving out a feature, we're leaving out people."
**Success Criteria:** First audit of the onboarding flow has been started. Bonus if it is completed
**Out-of-scope:** Analysis and sharing of findings
**Assumptions:**
- We are checking for A compliance (per discussion on 10/24)
- We will have some dev support to perform the audit if needed
- We have access to the tools we need to perform the audit. Example, [screen readers ](https://assistivlabs.com/pricing)
- Accessibility readout [document](https://docs.google.com/document/d/16M25bJlfoDjjwPW_fl7O8EeOzdOslGEB2k8PPtLprfA/edit#)
**Feature Readiness Check List:**
- [x] Document the scope of the audit by working with devs (Faraz) to outline the current onboarding flows
- [x] Define which standards are applicable to the product (do this on [WCAG 2.2 audit doc](https://docs.google.com/spreadsheets/d/1E3bKKG4vI1ucWkUW4HNTMdy9wOeLz9Ti/edit?usp=sharing&ouid=116116843699891540443&rtpof=true&sd=true))
- [x] (bonus) See how we could utilize the Azure tool
- [ ] Conduct audit of items that the design team can test - [checklist here](https://docs.google.com/spreadsheets/d/1ivZ_JulqB_Am7B4YdPQTkOXddlB4QigD/edit#gid=1254264225)
- [x] Provide an update on Accessibility Plan to PMs/stakeholders
|
1.0
|
Accessibility Audit: Navigator Onboarding - **Problem Statement:** Perform an audit on the Navigator onboarding flows to document and understand how the feature compares to current A compliance.
**Benefit Hypothesis:** With comms doing a marketing push on Navigator soon, it would be beneficial to fix any accessibility issues. - "Digital access needs are sometimes treated as a feature, but we're not leaving out a feature, we're leaving out people."
**Success Criteria:** First audit of the onboarding flow has been started. Bonus if it is completed
**Out-of-scope:** Analysis and sharing of findings
**Assumptions:**
- We are checking for A compliance (per discussion on 10/24)
- We will have some dev support to perform the audit if needed
- We have access to the tools we need to perform the audit. Example, [screen readers ](https://assistivlabs.com/pricing)
- Accessibility readout [document](https://docs.google.com/document/d/16M25bJlfoDjjwPW_fl7O8EeOzdOslGEB2k8PPtLprfA/edit#)
**Feature Readiness Check List:**
- [x] Document the scope of the audit by working with devs (Faraz) to outline the current onboarding flows
- [x] Define which standards are applicable to the product (do this on [WCAG 2.2 audit doc](https://docs.google.com/spreadsheets/d/1E3bKKG4vI1ucWkUW4HNTMdy9wOeLz9Ti/edit?usp=sharing&ouid=116116843699891540443&rtpof=true&sd=true))
- [x] (bonus) See how we could utilize the Azure tool
- [ ] Conduct audit of items that the design team can test - [checklist here](https://docs.google.com/spreadsheets/d/1ivZ_JulqB_Am7B4YdPQTkOXddlB4QigD/edit#gid=1254264225)
- [x] Provide an update on Accessibility Plan to PMs/stakeholders
|
non_defect
|
accessibility audit navigator onboarding problem statement perform an audit on the navigator onboarding flows to document and understand how the feature compares to current a compliance benefit hypothesis with comms doing a marketing push on navigator soon it would be beneficial to fix any accessibility issues digital access needs are sometimes treated as a feature but we re not leaving out a feature we re leaving out people success criteria first audit of the onboarding flow has been started bonus if it is completed out of scope analysis and sharing of findings assumptions we are checking for a compliance per discussion on we will have some dev support to perform the audit if needed we have access to the tools we need to perform the audit example accessibility readout feature readiness check list document the scope of the audit by working with devs faraz to outline the current onboarding flows define which standards are applicable to the product do this on bonus see how we could utilize the azure tool conduct audit of items that the design team can test provide an update on accessibility plan to pms stakeholders
| 0
|
113,242
| 11,796,591,310
|
IssuesEvent
|
2020-03-18 11:04:08
|
neo4j/neo4j-java-driver-spring-boot-starter
|
https://api.github.com/repos/neo4j/neo4j-java-driver-spring-boot-starter
|
closed
|
Remove default value for required uri property.
|
documentation enhancement
|
The auto configuration of the driver is conditional:
```
@ConditionalOnProperty(prefix = "org.neo4j.driver", name = "uri")
```
We do this so that this starter doesn't clash with the current Spring Data Neo4j starter you get on start.spring.io.
If we would default to localhost, than the user would end up with a connection configured through SDN/OGM and this starter.
If the user adds this starter here, they have to be explicit in configuring the URL.
By doing so, it will than override the auto configuration of SDN/OGM.
Currently, this is not clear, as we a) don't mention it clear enough in the docs and b) default the URL in the properties.
cc @JMHReif
|
1.0
|
Remove default value for required uri property. - The auto configuration of the driver is conditional:
```
@ConditionalOnProperty(prefix = "org.neo4j.driver", name = "uri")
```
We do this so that this starter doesn't clash with the current Spring Data Neo4j starter you get on start.spring.io.
If we would default to localhost, than the user would end up with a connection configured through SDN/OGM and this starter.
If the user adds this starter here, they have to be explicit in configuring the URL.
By doing so, it will than override the auto configuration of SDN/OGM.
Currently, this is not clear, as we a) don't mention it clear enough in the docs and b) default the URL in the properties.
cc @JMHReif
|
non_defect
|
remove default value for required uri property the auto configuration of the driver is conditional conditionalonproperty prefix org driver name uri we do this so that this starter doesn t clash with the current spring data starter you get on start spring io if we would default to localhost than the user would end up with a connection configured through sdn ogm and this starter if the user adds this starter here they have to be explicit in configuring the url by doing so it will than override the auto configuration of sdn ogm currently this is not clear as we a don t mention it clear enough in the docs and b default the url in the properties cc jmhreif
| 0
|
457,862
| 13,163,840,718
|
IssuesEvent
|
2020-08-11 01:45:39
|
willyborja95/Camello
|
https://api.github.com/repos/willyborja95/Camello
|
closed
|
Add a screen for show the Privacy Policy
|
Priority: Medium Type: Feature
|
Add a screen to show the privacy policy and make him accept it when is the first time when the app is open
|
1.0
|
Add a screen for show the Privacy Policy - Add a screen to show the privacy policy and make him accept it when is the first time when the app is open
|
non_defect
|
add a screen for show the privacy policy add a screen to show the privacy policy and make him accept it when is the first time when the app is open
| 0
|
644,756
| 20,987,085,950
|
IssuesEvent
|
2022-03-29 05:10:14
|
valora-inc/wallet
|
https://api.github.com/repos/valora-inc/wallet
|
opened
|
[Query] : Sorting of the token is also applicable on view assets page similar to seen on enter amount page
|
Priority: P3 wallet qa-report qa-query
|
**Frequency :** 100%
**Repro on build version:** Android Internal Release Build V:1.29.0,iOS Internal TestFlight Release Build V:1.29.0
**Repro on device :** OnePlus 7t(11.0), Google Pixel 2XL(11.0), iPhone SE 2020(14.8.1), iPhone 7(13.3)
**Pre-condition:**
1] User must have downloaded the application
2] User must have multiple token balance in the account
3] User must be on homepage
**Repro Steps:**
1] Tap on view assets from homepage
2] Observe the sorting of the tokens
**Query :**
- Sorting of tokens is also applicable on view assets page as we are able to see the highest token balance on top of the list
- It should appear similar to the sorting seen on enter amount page after clicking on multitoken pill
**Current Behavior :** The highest token balance is seen on top of the list on view assets page
**Attachment :** [sorting](https://drive.google.com/file/d/1YidHoRHllrkGT-kWeyy4q3Q3-lrsioWt/view?usp=sharing)
|
1.0
|
[Query] : Sorting of the token is also applicable on view assets page similar to seen on enter amount page - **Frequency :** 100%
**Repro on build version:** Android Internal Release Build V:1.29.0,iOS Internal TestFlight Release Build V:1.29.0
**Repro on device :** OnePlus 7t(11.0), Google Pixel 2XL(11.0), iPhone SE 2020(14.8.1), iPhone 7(13.3)
**Pre-condition:**
1] User must have downloaded the application
2] User must have multiple token balance in the account
3] User must be on homepage
**Repro Steps:**
1] Tap on view assets from homepage
2] Observe the sorting of the tokens
**Query :**
- Sorting of tokens is also applicable on view assets page as we are able to see the highest token balance on top of the list
- It should appear similar to the sorting seen on enter amount page after clicking on multitoken pill
**Current Behavior :** The highest token balance is seen on top of the list on view assets page
**Attachment :** [sorting](https://drive.google.com/file/d/1YidHoRHllrkGT-kWeyy4q3Q3-lrsioWt/view?usp=sharing)
|
non_defect
|
sorting of the token is also applicable on view assets page similar to seen on enter amount page frequency repro on build version android internal release build v ios internal testflight release build v repro on device oneplus google pixel iphone se iphone pre condition user must have downloaded the application user must have multiple token balance in the account user must be on homepage repro steps tap on view assets from homepage observe the sorting of the tokens query sorting of tokens is also applicable on view assets page as we are able to see the highest token balance on top of the list it should appear similar to the sorting seen on enter amount page after clicking on multitoken pill current behavior the highest token balance is seen on top of the list on view assets page attachment
| 0
|
118,301
| 9,981,578,823
|
IssuesEvent
|
2019-07-10 07:51:40
|
microsoft/azure-tools-for-java
|
https://api.github.com/repos/microsoft/azure-tools-for-java
|
closed
|
[IntelliJ][Spark on Cosmos]Spark on Cosmos node is not showing up after sign in azure account of dogfood environment
|
HDInsight IntelliJ Internal Test fixed
|
Repro steps:
1. sign in with Azure account `admin@aad264.ccsctp.net`, which is an account from dogfood environment.
2. Select all the subscriptions. Error dialog pops up and `Apache Spark on Cosmos` node is not showing up.
Checked log in `idea.log` and find lines below.
```
2019-06-12 18:43:43,538 [2569979] WARN - AzureSparkCosmosClusterManager - Got exceptions when refresh Azure Data Lake Spark pool: java.lang.RuntimeException: com.microsoft.azure.hdinsight.sdk.common.errorresponse.ForbiddenHttpErrorStatus: {"error":{"code":"AuthorizationFailed","message":"The client 'admin@aad264.ccsctp.net' with object id '353f35f8-e1c3-461c-8314-5650973a5ec7' does not have authorization to perform action 'Microsoft.DataLakeAnalytics/accounts/read' over scope '/subscriptions/0afefe50-734e-4610-8c82-a144aff49dea'."}}
```
|
1.0
|
[IntelliJ][Spark on Cosmos]Spark on Cosmos node is not showing up after sign in azure account of dogfood environment - Repro steps:
1. sign in with Azure account `admin@aad264.ccsctp.net`, which is an account from dogfood environment.
2. Select all the subscriptions. Error dialog pops up and `Apache Spark on Cosmos` node is not showing up.
Checked log in `idea.log` and find lines below.
```
2019-06-12 18:43:43,538 [2569979] WARN - AzureSparkCosmosClusterManager - Got exceptions when refresh Azure Data Lake Spark pool: java.lang.RuntimeException: com.microsoft.azure.hdinsight.sdk.common.errorresponse.ForbiddenHttpErrorStatus: {"error":{"code":"AuthorizationFailed","message":"The client 'admin@aad264.ccsctp.net' with object id '353f35f8-e1c3-461c-8314-5650973a5ec7' does not have authorization to perform action 'Microsoft.DataLakeAnalytics/accounts/read' over scope '/subscriptions/0afefe50-734e-4610-8c82-a144aff49dea'."}}
```
|
non_defect
|
spark on cosmos node is not showing up after sign in azure account of dogfood environment repro steps sign in with azure account admin ccsctp net which is an account from dogfood environment select all the subscriptions error dialog pops up and apache spark on cosmos node is not showing up checked log in idea log and find lines below warn azuresparkcosmosclustermanager got exceptions when refresh azure data lake spark pool java lang runtimeexception com microsoft azure hdinsight sdk common errorresponse forbiddenhttperrorstatus error code authorizationfailed message the client admin ccsctp net with object id does not have authorization to perform action microsoft datalakeanalytics accounts read over scope subscriptions
| 0
|
17,623
| 3,631,524,874
|
IssuesEvent
|
2016-02-11 02:05:22
|
cockroachdb/cockroach
|
https://api.github.com/repos/cockroachdb/cockroach
|
opened
|
Failed tests (12666): TestChaos
|
test-failure TestChaos
|
The following test appears to have failed:
[#12666](https://circleci.com/gh/cockroachdb/cockroach/12666):
```
I0211 02:00:43.693975 27510 acceptance/chaos_test.go:160 client 2 shutting down
I0211 02:00:44.396214 27510 acceptance/chaos_test.go:160 client 0 shutting down
I0211 02:00:44.396305 27510 acceptance/chaos_test.go:193 round 2: restarting nodes [1 0 2]
W0211 02:00:44.396333 27510 acceptance/chaos_test.go:233 round 2: monkey sleeping while cluster recovers...
I0211 02:00:44.413322 27510 acceptance/chaos_test.go:307 699 120.7/sec
panic: test timed out after 5m0s
goroutine 221 [running]:
testing.startAlarm.func1()
/usr/local/go/src/testing/testing.go:703 +0x132
created by time.goFunc
/usr/local/go/src/time/sleep.go:129 +0x3a
goroutine 1 [chan receive, 4 minutes]:
testing.RunTests(0xcd8bd8, 0x1105c00, 0xe, 0xe, 0x728eadc4ff64c201)
/usr/local/go/src/testing/testing.go:562 +0x8ad
testing.(*M).Run(0xc8204bcf08, 0xcd8440)
/usr/local/go/src/testing/testing.go:494 +0x70
github.com/cockroachdb/cockroach/acceptance.TestMain(0xc8204bcf08)
/go/src/github.com/cockroachdb/cockroach/acceptance/main_test.go:140 +0x3e
main.main()
github.com/cockroachdb/cockroach/acceptance/_test/_testmain.go:78 +0x113
goroutine 17 [syscall, 4 minutes, locked to thread]:
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:1721 +0x1
goroutine 5 [chan receive]:
github.com/cockroachdb/cockroach/util/log.(*loggingT).flushDaemon(0x1121fa0)
/go/src/github.com/cockroachdb/cockroach/util/log/clog.go:1029 +0x64
created by github.com/cockroachdb/cockroach/util/log.init.1
/go/src/github.com/cockroachdb/cockroach/util/log/clog.go:610 +0xbc
goroutine 6 [syscall, 4 minutes]:
os/signal.loop()
/usr/local/go/src/os/signal/signal_unix.go:22 +0x18
created by os/signal.init.1
/usr/local/go/src/os/signal/signal_unix.go:28 +0x37
goroutine 19 [chan receive, 4 minutes]:
github.com/cockroachdb/cockroach/acceptance.TestMain.func1()
/go/src/github.com/cockroachdb/cockroach/acceptance/main_test.go:131 +0xd8
created by github.com/cockroachdb/cockroach/acceptance.TestMain
/go/src/github.com/cockroachdb/cockroach/acceptance/main_test.go:139 +0x30
goroutine 136 [chan receive, 4 minutes]:
github.com/cockroachdb/cockroach/acceptance.TestChaos.func4(0xc82004b2c0, 0xc820085e60, 0x3, 0x3)
/go/src/github.com/cockroachdb/cockroach/acceptance/chaos_test.go:167 +0x3a
github.com/cockroachdb/cockroach/acceptance.TestChaos(0xc82015a7e0)
/go/src/github.com/cockroachdb/cockroach/acceptance/chaos_test.go:308 +0x19d0
testing.tRunner(0xc82015a7e0, 0x1105c30)
/usr/local/go/src/testing/testing.go:456 +0x98
created by testing.RunTests
/usr/local/go/src/testing/testing.go:561 +0x86d
goroutine 156 [select, 4 minutes]:
net/http.(*persistConn).readLoop(0xc82035eb00)
/usr/local/go/src/net/http/transport.go:976 +0xac7
created by net/http.(*Transport).dialConn
/usr/local/go/src/net/http/transport.go:685 +0xc78
goroutine 25 [select, 4 minutes, locked to thread]:
runtime.gopark(0xcd9280, 0xc820025f28, 0xb9d648, 0x6, 0x431b18, 0x2)
/usr/local/go/src/runtime/proc.go:185 +0x163
runtime.selectgoImpl(0xc820025f28, 0x0, 0x18)
/usr/local/go/src/runtime/select.go:392 +0xa64
runtime.selectgo(0xc820025f28)
/usr/local/go/src/runtime/select.go:212 +0x12
runtime.ensureSigM.func1()
/usr/local/go/src/runtime/signal1_unix.go:227 +0x353
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:1721 +0x1
goroutine 23 [IO wait, 4 minutes]:
net.runtime_pollWait(0x7fab413a68f8, 0x72, 0xc8200141f0)
/usr/local/go/src/runtime/netpoll.go:157 +0x60
net.(*pollDesc).Wait(0xc82018c920, 0x72, 0x0, 0x0)
/usr/local/go/src/net/fd_poll_runtime.go:73 +0x3a
net.(*pollDesc).WaitRead(0xc82018c920, 0x0, 0x0)
/usr/local/go/src/net/fd_poll_runtime.go:78 +0x36
net.(*netFD).Read(0xc82018c8c0, 0xc820187000, 0x1000, 0x1000, 0x0, 0x7fab43c25050, 0xc8200141f0)
/usr/local/go/src/net/fd_unix.go:232 +0x23a
net.(*conn).Read(0xc8200da530, 0xc820187000, 0x1000, 0x1000, 0x0, 0x0, 0x0)
/usr/local/go/src/net/net.go:172 +0xe4
--
net/http.(*persistConn).readLoop(0xc820156370)
/usr/local/go/src/net/http/transport.go:876 +0xf7
created by net/http.(*Transport).dialConn
/usr/local/go/src/net/http/transport.go:685 +0xc78
goroutine 24 [select, 4 minutes]:
net/http.(*persistConn).writeLoop(0xc820156370)
/usr/local/go/src/net/http/transport.go:1009 +0x40c
created by net/http.(*Transport).dialConn
/usr/local/go/src/net/http/transport.go:686 +0xc9d
goroutine 196 [chan receive, 4 minutes]:
database/sql.(*DB).connectionOpener(0xc8203b2780)
/usr/local/go/src/database/sql/sql.go:634 +0x45
created by database/sql.Open
/usr/local/go/src/database/sql/sql.go:481 +0x336
goroutine 139 [IO wait, 4 minutes]:
net.runtime_pollWait(0x7fab413a65f8, 0x72, 0xc8200141f0)
/usr/local/go/src/runtime/netpoll.go:157 +0x60
net.(*pollDesc).Wait(0xc820556610, 0x72, 0x0, 0x0)
/usr/local/go/src/net/fd_poll_runtime.go:73 +0x3a
net.(*pollDesc).WaitRead(0xc820556610, 0x0, 0x0)
/usr/local/go/src/net/fd_poll_runtime.go:78 +0x36
net.(*netFD).Read(0xc8205565b0, 0xc82059a000, 0x1000, 0x1000, 0x0, 0x7fab43c25050, 0xc8200141f0)
/usr/local/go/src/net/fd_unix.go:232 +0x23a
net.(*conn).Read(0xc82002c050, 0xc82059a000, 0x1000, 0x1000, 0x0, 0x0, 0x0)
/usr/local/go/src/net/net.go:172 +0xe4
--
net/http.(*persistConn).readLoop(0xc820156420)
/usr/local/go/src/net/http/transport.go:876 +0xf7
created by net/http.(*Transport).dialConn
/usr/local/go/src/net/http/transport.go:685 +0xc78
goroutine 190 [chan receive, 4 minutes]:
database/sql.(*DB).connectionOpener(0xc8203b2500)
/usr/local/go/src/database/sql/sql.go:634 +0x45
created by database/sql.Open
/usr/local/go/src/database/sql/sql.go:481 +0x336
goroutine 213 [chan receive, 4 minutes]:
database/sql.(*DB).connectionOpener(0xc82000b2c0)
/usr/local/go/src/database/sql/sql.go:634 +0x45
created by database/sql.Open
/usr/local/go/src/database/sql/sql.go:481 +0x336
goroutine 140 [select, 4 minutes]:
net/http.(*persistConn).writeLoop(0xc820156420)
/usr/local/go/src/net/http/transport.go:1009 +0x40c
created by net/http.(*Transport).dialConn
/usr/local/go/src/net/http/transport.go:686 +0xc9d
goroutine 220 [chan receive, 4 minutes]:
database/sql.(*DB).connectionOpener(0xc82000b360)
/usr/local/go/src/database/sql/sql.go:634 +0x45
created by database/sql.Open
/usr/local/go/src/database/sql/sql.go:481 +0x336
goroutine 158 [select, 4 minutes]:
github.com/docker/engine-api/client/transport/cancellable.Do.func3(0x7fab413b0988, 0xc820380400, 0xc8201ff400, 0xc820386d20)
/go/src/github.com/docker/engine-api/client/transport/cancellable/cancellable.go:78 +0xee
created by github.com/docker/engine-api/client/transport/cancellable.Do
/go/src/github.com/docker/engine-api/client/transport/cancellable/cancellable.go:84 +0x335
goroutine 152 [IO wait, 4 minutes]:
net.runtime_pollWait(0x7fab413a66b8, 0x72, 0xc8200141f0)
/usr/local/go/src/runtime/netpoll.go:157 +0x60
net.(*pollDesc).Wait(0xc820385f70, 0x72, 0x0, 0x0)
/usr/local/go/src/net/fd_poll_runtime.go:73 +0x3a
net.(*pollDesc).WaitRead(0xc820385f70, 0x0, 0x0)
/usr/local/go/src/net/fd_poll_runtime.go:78 +0x36
net.(*netFD).Read(0xc820385f10, 0xc820564000, 0x1000, 0x1000, 0x0, 0x7fab43c25050, 0xc8200141f0)
/usr/local/go/src/net/fd_unix.go:232 +0x23a
net.(*conn).Read(0xc82002c078, 0xc820564000, 0x1000, 0x1000, 0x0, 0x0, 0x0)
/usr/local/go/src/net/net.go:172 +0xe4
--
github.com/cockroachdb/cockroach/acceptance/cluster.(*LocalCluster).monitor(0xc82018a000)
/go/src/github.com/cockroachdb/cockroach/acceptance/cluster/localcluster.go:459 +0x210
created by github.com/cockroachdb/cockroach/acceptance/cluster.(*LocalCluster).Start
/go/src/github.com/cockroachdb/cockroach/acceptance/cluster/localcluster.go:493 +0x3a7
goroutine 192 [chan receive, 4 minutes]:
database/sql.(*DB).connectionOpener(0xc8203b26e0)
/usr/local/go/src/database/sql/sql.go:634 +0x45
created by database/sql.Open
/usr/local/go/src/database/sql/sql.go:481 +0x336
goroutine 157 [select, 4 minutes]:
net/http.(*persistConn).writeLoop(0xc82035eb00)
/usr/local/go/src/net/http/transport.go:1009 +0x40c
created by net/http.(*Transport).dialConn
/usr/local/go/src/net/http/transport.go:686 +0xc9d
goroutine 200 [chan receive, 4 minutes]:
database/sql.(*DB).connectionOpener(0xc8203b2820)
/usr/local/go/src/database/sql/sql.go:634 +0x45
created by database/sql.Open
/usr/local/go/src/database/sql/sql.go:481 +0x336
goroutine 202 [sleep]:
time.Sleep(0x3b9aca00)
/usr/local/go/src/runtime/time.go:59 +0xf9
github.com/cockroachdb/cockroach/acceptance.TestChaos.func5(0xc82004b2c0, 0xc8204f5920, 0xc820150540, 0x3, 0xc820085e60, 0x3, 0x3, 0x7fab413b0b38, 0xc82018a000, 0xc82015a7e0, ...)
/go/src/github.com/cockroachdb/cockroach/acceptance/chaos_test.go:235 +0x875
created by github.com/cockroachdb/cockroach/acceptance.TestChaos
/go/src/github.com/cockroachdb/cockroach/acceptance/chaos_test.go:239 +0xf07
ok github.com/cockroachdb/cockroach/acceptance 1337s
```
Please assign, take a look and update the issue accordingly.
|
2.0
|
Failed tests (12666): TestChaos - The following test appears to have failed:
[#12666](https://circleci.com/gh/cockroachdb/cockroach/12666):
```
I0211 02:00:43.693975 27510 acceptance/chaos_test.go:160 client 2 shutting down
I0211 02:00:44.396214 27510 acceptance/chaos_test.go:160 client 0 shutting down
I0211 02:00:44.396305 27510 acceptance/chaos_test.go:193 round 2: restarting nodes [1 0 2]
W0211 02:00:44.396333 27510 acceptance/chaos_test.go:233 round 2: monkey sleeping while cluster recovers...
I0211 02:00:44.413322 27510 acceptance/chaos_test.go:307 699 120.7/sec
panic: test timed out after 5m0s
goroutine 221 [running]:
testing.startAlarm.func1()
/usr/local/go/src/testing/testing.go:703 +0x132
created by time.goFunc
/usr/local/go/src/time/sleep.go:129 +0x3a
goroutine 1 [chan receive, 4 minutes]:
testing.RunTests(0xcd8bd8, 0x1105c00, 0xe, 0xe, 0x728eadc4ff64c201)
/usr/local/go/src/testing/testing.go:562 +0x8ad
testing.(*M).Run(0xc8204bcf08, 0xcd8440)
/usr/local/go/src/testing/testing.go:494 +0x70
github.com/cockroachdb/cockroach/acceptance.TestMain(0xc8204bcf08)
/go/src/github.com/cockroachdb/cockroach/acceptance/main_test.go:140 +0x3e
main.main()
github.com/cockroachdb/cockroach/acceptance/_test/_testmain.go:78 +0x113
goroutine 17 [syscall, 4 minutes, locked to thread]:
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:1721 +0x1
goroutine 5 [chan receive]:
github.com/cockroachdb/cockroach/util/log.(*loggingT).flushDaemon(0x1121fa0)
/go/src/github.com/cockroachdb/cockroach/util/log/clog.go:1029 +0x64
created by github.com/cockroachdb/cockroach/util/log.init.1
/go/src/github.com/cockroachdb/cockroach/util/log/clog.go:610 +0xbc
goroutine 6 [syscall, 4 minutes]:
os/signal.loop()
/usr/local/go/src/os/signal/signal_unix.go:22 +0x18
created by os/signal.init.1
/usr/local/go/src/os/signal/signal_unix.go:28 +0x37
goroutine 19 [chan receive, 4 minutes]:
github.com/cockroachdb/cockroach/acceptance.TestMain.func1()
/go/src/github.com/cockroachdb/cockroach/acceptance/main_test.go:131 +0xd8
created by github.com/cockroachdb/cockroach/acceptance.TestMain
/go/src/github.com/cockroachdb/cockroach/acceptance/main_test.go:139 +0x30
goroutine 136 [chan receive, 4 minutes]:
github.com/cockroachdb/cockroach/acceptance.TestChaos.func4(0xc82004b2c0, 0xc820085e60, 0x3, 0x3)
/go/src/github.com/cockroachdb/cockroach/acceptance/chaos_test.go:167 +0x3a
github.com/cockroachdb/cockroach/acceptance.TestChaos(0xc82015a7e0)
/go/src/github.com/cockroachdb/cockroach/acceptance/chaos_test.go:308 +0x19d0
testing.tRunner(0xc82015a7e0, 0x1105c30)
/usr/local/go/src/testing/testing.go:456 +0x98
created by testing.RunTests
/usr/local/go/src/testing/testing.go:561 +0x86d
goroutine 156 [select, 4 minutes]:
net/http.(*persistConn).readLoop(0xc82035eb00)
/usr/local/go/src/net/http/transport.go:976 +0xac7
created by net/http.(*Transport).dialConn
/usr/local/go/src/net/http/transport.go:685 +0xc78
goroutine 25 [select, 4 minutes, locked to thread]:
runtime.gopark(0xcd9280, 0xc820025f28, 0xb9d648, 0x6, 0x431b18, 0x2)
/usr/local/go/src/runtime/proc.go:185 +0x163
runtime.selectgoImpl(0xc820025f28, 0x0, 0x18)
/usr/local/go/src/runtime/select.go:392 +0xa64
runtime.selectgo(0xc820025f28)
/usr/local/go/src/runtime/select.go:212 +0x12
runtime.ensureSigM.func1()
/usr/local/go/src/runtime/signal1_unix.go:227 +0x353
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:1721 +0x1
goroutine 23 [IO wait, 4 minutes]:
net.runtime_pollWait(0x7fab413a68f8, 0x72, 0xc8200141f0)
/usr/local/go/src/runtime/netpoll.go:157 +0x60
net.(*pollDesc).Wait(0xc82018c920, 0x72, 0x0, 0x0)
/usr/local/go/src/net/fd_poll_runtime.go:73 +0x3a
net.(*pollDesc).WaitRead(0xc82018c920, 0x0, 0x0)
/usr/local/go/src/net/fd_poll_runtime.go:78 +0x36
net.(*netFD).Read(0xc82018c8c0, 0xc820187000, 0x1000, 0x1000, 0x0, 0x7fab43c25050, 0xc8200141f0)
/usr/local/go/src/net/fd_unix.go:232 +0x23a
net.(*conn).Read(0xc8200da530, 0xc820187000, 0x1000, 0x1000, 0x0, 0x0, 0x0)
/usr/local/go/src/net/net.go:172 +0xe4
--
net/http.(*persistConn).readLoop(0xc820156370)
/usr/local/go/src/net/http/transport.go:876 +0xf7
created by net/http.(*Transport).dialConn
/usr/local/go/src/net/http/transport.go:685 +0xc78
goroutine 24 [select, 4 minutes]:
net/http.(*persistConn).writeLoop(0xc820156370)
/usr/local/go/src/net/http/transport.go:1009 +0x40c
created by net/http.(*Transport).dialConn
/usr/local/go/src/net/http/transport.go:686 +0xc9d
goroutine 196 [chan receive, 4 minutes]:
database/sql.(*DB).connectionOpener(0xc8203b2780)
/usr/local/go/src/database/sql/sql.go:634 +0x45
created by database/sql.Open
/usr/local/go/src/database/sql/sql.go:481 +0x336
goroutine 139 [IO wait, 4 minutes]:
net.runtime_pollWait(0x7fab413a65f8, 0x72, 0xc8200141f0)
/usr/local/go/src/runtime/netpoll.go:157 +0x60
net.(*pollDesc).Wait(0xc820556610, 0x72, 0x0, 0x0)
/usr/local/go/src/net/fd_poll_runtime.go:73 +0x3a
net.(*pollDesc).WaitRead(0xc820556610, 0x0, 0x0)
/usr/local/go/src/net/fd_poll_runtime.go:78 +0x36
net.(*netFD).Read(0xc8205565b0, 0xc82059a000, 0x1000, 0x1000, 0x0, 0x7fab43c25050, 0xc8200141f0)
/usr/local/go/src/net/fd_unix.go:232 +0x23a
net.(*conn).Read(0xc82002c050, 0xc82059a000, 0x1000, 0x1000, 0x0, 0x0, 0x0)
/usr/local/go/src/net/net.go:172 +0xe4
--
net/http.(*persistConn).readLoop(0xc820156420)
/usr/local/go/src/net/http/transport.go:876 +0xf7
created by net/http.(*Transport).dialConn
/usr/local/go/src/net/http/transport.go:685 +0xc78
goroutine 190 [chan receive, 4 minutes]:
database/sql.(*DB).connectionOpener(0xc8203b2500)
/usr/local/go/src/database/sql/sql.go:634 +0x45
created by database/sql.Open
/usr/local/go/src/database/sql/sql.go:481 +0x336
goroutine 213 [chan receive, 4 minutes]:
database/sql.(*DB).connectionOpener(0xc82000b2c0)
/usr/local/go/src/database/sql/sql.go:634 +0x45
created by database/sql.Open
/usr/local/go/src/database/sql/sql.go:481 +0x336
goroutine 140 [select, 4 minutes]:
net/http.(*persistConn).writeLoop(0xc820156420)
/usr/local/go/src/net/http/transport.go:1009 +0x40c
created by net/http.(*Transport).dialConn
/usr/local/go/src/net/http/transport.go:686 +0xc9d
goroutine 220 [chan receive, 4 minutes]:
database/sql.(*DB).connectionOpener(0xc82000b360)
/usr/local/go/src/database/sql/sql.go:634 +0x45
created by database/sql.Open
/usr/local/go/src/database/sql/sql.go:481 +0x336
goroutine 158 [select, 4 minutes]:
github.com/docker/engine-api/client/transport/cancellable.Do.func3(0x7fab413b0988, 0xc820380400, 0xc8201ff400, 0xc820386d20)
/go/src/github.com/docker/engine-api/client/transport/cancellable/cancellable.go:78 +0xee
created by github.com/docker/engine-api/client/transport/cancellable.Do
/go/src/github.com/docker/engine-api/client/transport/cancellable/cancellable.go:84 +0x335
goroutine 152 [IO wait, 4 minutes]:
net.runtime_pollWait(0x7fab413a66b8, 0x72, 0xc8200141f0)
/usr/local/go/src/runtime/netpoll.go:157 +0x60
net.(*pollDesc).Wait(0xc820385f70, 0x72, 0x0, 0x0)
/usr/local/go/src/net/fd_poll_runtime.go:73 +0x3a
net.(*pollDesc).WaitRead(0xc820385f70, 0x0, 0x0)
/usr/local/go/src/net/fd_poll_runtime.go:78 +0x36
net.(*netFD).Read(0xc820385f10, 0xc820564000, 0x1000, 0x1000, 0x0, 0x7fab43c25050, 0xc8200141f0)
/usr/local/go/src/net/fd_unix.go:232 +0x23a
net.(*conn).Read(0xc82002c078, 0xc820564000, 0x1000, 0x1000, 0x0, 0x0, 0x0)
/usr/local/go/src/net/net.go:172 +0xe4
--
github.com/cockroachdb/cockroach/acceptance/cluster.(*LocalCluster).monitor(0xc82018a000)
/go/src/github.com/cockroachdb/cockroach/acceptance/cluster/localcluster.go:459 +0x210
created by github.com/cockroachdb/cockroach/acceptance/cluster.(*LocalCluster).Start
/go/src/github.com/cockroachdb/cockroach/acceptance/cluster/localcluster.go:493 +0x3a7
goroutine 192 [chan receive, 4 minutes]:
database/sql.(*DB).connectionOpener(0xc8203b26e0)
/usr/local/go/src/database/sql/sql.go:634 +0x45
created by database/sql.Open
/usr/local/go/src/database/sql/sql.go:481 +0x336
goroutine 157 [select, 4 minutes]:
net/http.(*persistConn).writeLoop(0xc82035eb00)
/usr/local/go/src/net/http/transport.go:1009 +0x40c
created by net/http.(*Transport).dialConn
/usr/local/go/src/net/http/transport.go:686 +0xc9d
goroutine 200 [chan receive, 4 minutes]:
database/sql.(*DB).connectionOpener(0xc8203b2820)
/usr/local/go/src/database/sql/sql.go:634 +0x45
created by database/sql.Open
/usr/local/go/src/database/sql/sql.go:481 +0x336
goroutine 202 [sleep]:
time.Sleep(0x3b9aca00)
/usr/local/go/src/runtime/time.go:59 +0xf9
github.com/cockroachdb/cockroach/acceptance.TestChaos.func5(0xc82004b2c0, 0xc8204f5920, 0xc820150540, 0x3, 0xc820085e60, 0x3, 0x3, 0x7fab413b0b38, 0xc82018a000, 0xc82015a7e0, ...)
/go/src/github.com/cockroachdb/cockroach/acceptance/chaos_test.go:235 +0x875
created by github.com/cockroachdb/cockroach/acceptance.TestChaos
/go/src/github.com/cockroachdb/cockroach/acceptance/chaos_test.go:239 +0xf07
ok github.com/cockroachdb/cockroach/acceptance 1337s
```
Please assign, take a look and update the issue accordingly.
|
non_defect
|
failed tests testchaos the following test appears to have failed acceptance chaos test go client shutting down acceptance chaos test go client shutting down acceptance chaos test go round restarting nodes acceptance chaos test go round monkey sleeping while cluster recovers acceptance chaos test go sec panic test timed out after goroutine testing startalarm usr local go src testing testing go created by time gofunc usr local go src time sleep go goroutine testing runtests usr local go src testing testing go testing m run usr local go src testing testing go github com cockroachdb cockroach acceptance testmain go src github com cockroachdb cockroach acceptance main test go main main github com cockroachdb cockroach acceptance test testmain go goroutine runtime goexit usr local go src runtime asm s goroutine github com cockroachdb cockroach util log loggingt flushdaemon go src github com cockroachdb cockroach util log clog go created by github com cockroachdb cockroach util log init go src github com cockroachdb cockroach util log clog go goroutine os signal loop usr local go src os signal signal unix go created by os signal init usr local go src os signal signal unix go goroutine github com cockroachdb cockroach acceptance testmain go src github com cockroachdb cockroach acceptance main test go created by github com cockroachdb cockroach acceptance testmain go src github com cockroachdb cockroach acceptance main test go goroutine github com cockroachdb cockroach acceptance testchaos go src github com cockroachdb cockroach acceptance chaos test go github com cockroachdb cockroach acceptance testchaos go src github com cockroachdb cockroach acceptance chaos test go testing trunner usr local go src testing testing go created by testing runtests usr local go src testing testing go goroutine net http persistconn readloop usr local go src net http transport go created by net http transport dialconn usr local go src net http transport go goroutine runtime gopark usr local go src runtime proc go runtime selectgoimpl usr local go src runtime select go runtime selectgo usr local go src runtime select go runtime ensuresigm usr local go src runtime unix go runtime goexit usr local go src runtime asm s goroutine net runtime pollwait usr local go src runtime netpoll go net polldesc wait usr local go src net fd poll runtime go net polldesc waitread usr local go src net fd poll runtime go net netfd read usr local go src net fd unix go net conn read usr local go src net net go net http persistconn readloop usr local go src net http transport go created by net http transport dialconn usr local go src net http transport go goroutine net http persistconn writeloop usr local go src net http transport go created by net http transport dialconn usr local go src net http transport go goroutine database sql db connectionopener usr local go src database sql sql go created by database sql open usr local go src database sql sql go goroutine net runtime pollwait usr local go src runtime netpoll go net polldesc wait usr local go src net fd poll runtime go net polldesc waitread usr local go src net fd poll runtime go net netfd read usr local go src net fd unix go net conn read usr local go src net net go net http persistconn readloop usr local go src net http transport go created by net http transport dialconn usr local go src net http transport go goroutine database sql db connectionopener usr local go src database sql sql go created by database sql open usr local go src database sql sql go goroutine database sql db connectionopener usr local go src database sql sql go created by database sql open usr local go src database sql sql go goroutine net http persistconn writeloop usr local go src net http transport go created by net http transport dialconn usr local go src net http transport go goroutine database sql db connectionopener usr local go src database sql sql go created by database sql open usr local go src database sql sql go goroutine github com docker engine api client transport cancellable do go src github com docker engine api client transport cancellable cancellable go created by github com docker engine api client transport cancellable do go src github com docker engine api client transport cancellable cancellable go goroutine net runtime pollwait usr local go src runtime netpoll go net polldesc wait usr local go src net fd poll runtime go net polldesc waitread usr local go src net fd poll runtime go net netfd read usr local go src net fd unix go net conn read usr local go src net net go github com cockroachdb cockroach acceptance cluster localcluster monitor go src github com cockroachdb cockroach acceptance cluster localcluster go created by github com cockroachdb cockroach acceptance cluster localcluster start go src github com cockroachdb cockroach acceptance cluster localcluster go goroutine database sql db connectionopener usr local go src database sql sql go created by database sql open usr local go src database sql sql go goroutine net http persistconn writeloop usr local go src net http transport go created by net http transport dialconn usr local go src net http transport go goroutine database sql db connectionopener usr local go src database sql sql go created by database sql open usr local go src database sql sql go goroutine time sleep usr local go src runtime time go github com cockroachdb cockroach acceptance testchaos go src github com cockroachdb cockroach acceptance chaos test go created by github com cockroachdb cockroach acceptance testchaos go src github com cockroachdb cockroach acceptance chaos test go ok github com cockroachdb cockroach acceptance please assign take a look and update the issue accordingly
| 0
|
17,394
| 3,003,912,627
|
IssuesEvent
|
2015-07-25 11:32:05
|
bk79/i2c-gps-nav
|
https://api.github.com/repos/bk79/i2c-gps-nav
|
closed
|
RTH slightly different heading ?
|
auto-migrated Priority-Medium Type-Defect
|
```
What steps will reproduce the problem?
1. Position Hold at North-northeast (copter was about 10m away from home).
2. RTH turned on.
3. copter moved like arc.
What is the expected output? What do you see instead?
copter will move straight.
What version of the product are you using? On what operating system?
I2C_GPS_NAV 2.1 ,MultiWii 2.1 (may be r1311) ,Win7
Please provide any additional information below.
I2C_GPS_NAV.ino
#1318 i2c_dataset.home_to_copter_bearing = GPS_bearing(...)
will overflow? when GPS_bearing() > about 328deg
Sorry I'm not good at english.
```
Original issue reported on code.google.com by `jyskei8...@gmail.com` on 26 Jan 2013 at 10:47
|
1.0
|
RTH slightly different heading ? - ```
What steps will reproduce the problem?
1. Position Hold at North-northeast (copter was about 10m away from home).
2. RTH turned on.
3. copter moved like arc.
What is the expected output? What do you see instead?
copter will move straight.
What version of the product are you using? On what operating system?
I2C_GPS_NAV 2.1 ,MultiWii 2.1 (may be r1311) ,Win7
Please provide any additional information below.
I2C_GPS_NAV.ino
#1318 i2c_dataset.home_to_copter_bearing = GPS_bearing(...)
will overflow? when GPS_bearing() > about 328deg
Sorry I'm not good at english.
```
Original issue reported on code.google.com by `jyskei8...@gmail.com` on 26 Jan 2013 at 10:47
|
defect
|
rth slightly different heading what steps will reproduce the problem position hold at north northeast copter was about away from home rth turned on copter moved like arc what is the expected output what do you see instead copter will move straight what version of the product are you using on what operating system gps nav multiwii may be please provide any additional information below gps nav ino dataset home to copter bearing gps bearing will overflow when gps bearing about sorry i m not good at english original issue reported on code google com by gmail com on jan at
| 1
|
50,277
| 13,187,418,549
|
IssuesEvent
|
2020-08-13 03:21:06
|
icecube-trac/tix3
|
https://api.github.com/repos/icecube-trac/tix3
|
closed
|
icetray-inspect and tableio (Trac #442)
|
Migrated from Trac defect documentation
|
icetray-inspect is outputting bad xml in tableio (and rootwriter)
see: http://codepad.org/ayhbgbxE
<details>
<summary>_Migrated from https://code.icecube.wisc.edu/ticket/442
, reported by nega and owned by jvansanten_</summary>
<p>
```json
{
"status": "closed",
"changetime": "2012-10-31T18:05:55",
"description": "icetray-inspect is outputting bad xml in tableio (and rootwriter)\n\nsee: http://codepad.org/ayhbgbxE",
"reporter": "nega",
"cc": "",
"resolution": "fixed",
"_ts": "1351706755000000",
"component": "documentation",
"summary": "icetray-inspect and tableio",
"priority": "major",
"keywords": "",
"time": "2012-09-14T18:24:26",
"milestone": "",
"owner": "jvansanten",
"type": "defect"
}
```
</p>
</details>
|
1.0
|
icetray-inspect and tableio (Trac #442) - icetray-inspect is outputting bad xml in tableio (and rootwriter)
see: http://codepad.org/ayhbgbxE
<details>
<summary>_Migrated from https://code.icecube.wisc.edu/ticket/442
, reported by nega and owned by jvansanten_</summary>
<p>
```json
{
"status": "closed",
"changetime": "2012-10-31T18:05:55",
"description": "icetray-inspect is outputting bad xml in tableio (and rootwriter)\n\nsee: http://codepad.org/ayhbgbxE",
"reporter": "nega",
"cc": "",
"resolution": "fixed",
"_ts": "1351706755000000",
"component": "documentation",
"summary": "icetray-inspect and tableio",
"priority": "major",
"keywords": "",
"time": "2012-09-14T18:24:26",
"milestone": "",
"owner": "jvansanten",
"type": "defect"
}
```
</p>
</details>
|
defect
|
icetray inspect and tableio trac icetray inspect is outputting bad xml in tableio and rootwriter see migrated from reported by nega and owned by jvansanten json status closed changetime description icetray inspect is outputting bad xml in tableio and rootwriter n nsee reporter nega cc resolution fixed ts component documentation summary icetray inspect and tableio priority major keywords time milestone owner jvansanten type defect
| 1
|
242,157
| 26,257,122,632
|
IssuesEvent
|
2023-01-06 02:25:41
|
GuyBarGil/WebGoat
|
https://api.github.com/repos/GuyBarGil/WebGoat
|
opened
|
CVE-2022-41854 (Medium) detected in snakeyaml-1.27.jar
|
security vulnerability
|
## CVE-2022-41854 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>snakeyaml-1.27.jar</b></p></summary>
<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: /webgoat-server/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.27/snakeyaml-1.27.jar,/home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.27/snakeyaml-1.27.jar,/home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.27/snakeyaml-1.27.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-validation-2.4.3.jar (Root Library)
- spring-boot-starter-2.4.3.jar
- :x: **snakeyaml-1.27.jar** (Vulnerable Library)
<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>
Those using Snakeyaml to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stack overflow. This effect may support a denial of service attack.
<p>Publish Date: 2022-11-11
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-41854>CVE-2022-41854</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.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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://bitbucket.org/snakeyaml/snakeyaml/issues/531/">https://bitbucket.org/snakeyaml/snakeyaml/issues/531/</a></p>
<p>Release Date: 2022-11-11</p>
<p>Fix Resolution (org.yaml:snakeyaml): 1.32</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-validation): 3.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2022-41854 (Medium) detected in snakeyaml-1.27.jar - ## CVE-2022-41854 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>snakeyaml-1.27.jar</b></p></summary>
<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: /webgoat-server/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.27/snakeyaml-1.27.jar,/home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.27/snakeyaml-1.27.jar,/home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.27/snakeyaml-1.27.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-validation-2.4.3.jar (Root Library)
- spring-boot-starter-2.4.3.jar
- :x: **snakeyaml-1.27.jar** (Vulnerable Library)
<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>
Those using Snakeyaml to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stack overflow. This effect may support a denial of service attack.
<p>Publish Date: 2022-11-11
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-41854>CVE-2022-41854</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.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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://bitbucket.org/snakeyaml/snakeyaml/issues/531/">https://bitbucket.org/snakeyaml/snakeyaml/issues/531/</a></p>
<p>Release Date: 2022-11-11</p>
<p>Fix Resolution (org.yaml:snakeyaml): 1.32</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-validation): 3.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_defect
|
cve medium detected in snakeyaml jar cve medium severity vulnerability vulnerable library snakeyaml jar yaml parser and emitter for java library home page a href path to dependency file webgoat server pom xml path to vulnerable library home wss scanner repository org yaml snakeyaml snakeyaml jar home wss scanner repository org yaml snakeyaml snakeyaml jar home wss scanner repository org yaml snakeyaml snakeyaml jar dependency hierarchy spring boot starter validation jar root library spring boot starter jar x snakeyaml jar vulnerable library found in base branch develop vulnerability details those using snakeyaml to parse untrusted yaml files may be vulnerable to denial of service attacks dos if the parser is running on user supplied input an attacker may supply content that causes the parser to crash by stack overflow this effect may support a denial of service attack publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact 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 yaml snakeyaml direct dependency fix resolution org springframework boot spring boot starter validation step up your open source security game with mend
| 0
|
318,426
| 9,692,209,433
|
IssuesEvent
|
2019-05-24 13:18:05
|
yalla-coop/presspad
|
https://api.github.com/repos/yalla-coop/presspad
|
closed
|
INTERN: I can sign up
|
T2h intern priority-2 user-story
|
- [x] Title
- [x] Register form
- [x] form heading
- [x] name
- [x] email
- [x] organisation code
- [x] password
- [x] confirm my password
- [x] sign up button
- [x] Error handling (e.g. checking the code is valid)
- [x] On successful completion add user to database
- [x] On successful completion redirect user to the complete profile page
|
1.0
|
INTERN: I can sign up - - [x] Title
- [x] Register form
- [x] form heading
- [x] name
- [x] email
- [x] organisation code
- [x] password
- [x] confirm my password
- [x] sign up button
- [x] Error handling (e.g. checking the code is valid)
- [x] On successful completion add user to database
- [x] On successful completion redirect user to the complete profile page
|
non_defect
|
intern i can sign up title register form form heading name email organisation code password confirm my password sign up button error handling e g checking the code is valid on successful completion add user to database on successful completion redirect user to the complete profile page
| 0
|
19,057
| 3,130,709,517
|
IssuesEvent
|
2015-09-09 10:59:34
|
ElectronicFreaker/gag
|
https://api.github.com/repos/ElectronicFreaker/gag
|
closed
|
@OhNoYouDidnt does not comply with industry standard terminology
|
auto-migrated Priority-Medium Type-Defect
|
```
Generally accepted practice is to flag operations that are performed with
unbelievable disregard for social custom with the tag @OhNoYouDi-int
```
Original issue reported on code.google.com by `phi...@gmail.com` on 12 Sep 2011 at 10:42
|
1.0
|
@OhNoYouDidnt does not comply with industry standard terminology - ```
Generally accepted practice is to flag operations that are performed with
unbelievable disregard for social custom with the tag @OhNoYouDi-int
```
Original issue reported on code.google.com by `phi...@gmail.com` on 12 Sep 2011 at 10:42
|
defect
|
ohnoyoudidnt does not comply with industry standard terminology generally accepted practice is to flag operations that are performed with unbelievable disregard for social custom with the tag ohnoyoudi int original issue reported on code google com by phi gmail com on sep at
| 1
|
43,614
| 11,777,420,165
|
IssuesEvent
|
2020-03-16 14:47:57
|
department-of-veterans-affairs/va.gov-team
|
https://api.github.com/repos/department-of-veterans-affairs/va.gov-team
|
opened
|
[COLOR, COGNITION]: CONSIDER changing background of map attribution
|
508-defect-4 508-issue-cognition 508/Accessibility vsa vsa-facilities
|
# [508-defect-4](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/accessibility/guidance/defect-severity-rubric.md#508-defect-4)
**Feedback framework**
- **❗️ Must** for if the feedback must be applied
- **⚠️Should** if the feedback is best practice
- **✔️ Consider** for suggestions/enhancements
## Description
**This is a relatively minor thing to consider.** Currently, Mapbox's attribution is placed in a transparent background layered over the map. Depending on where the user focuses the map, it may be hard to distinguish the text of the attribution. Relatively 'textured' areas of the map increase the contrast issues.
**Consider** making the background white or moving the attribution to just below the map instead of an overlay, since there are places the attribution overlays that do not meet contrast requirement of 4.5:1 for WCAG 2.0 Level AA for normal text. In mobile view, the text is especially small, and the contrast issue is really tough. See screenshots for examples of challenges our users may encounter, and recognize many have vision considerations such as low-vision and colorblindness.
## Point of Contact
**VFS Point of Contact:** Jennifer
## Acceptance Criteria
As a low vision user, I want to read the content of the website without any color contrast issues that may confuse.
## Environment
* Operating System: all
* Browser: all
* Server destination: production
## Steps to Recreate
1. Enter `https://www.va.gov/find-locations` in browser
2. Navigate to a destination with lots of water, greenery, and streets (such as Port St Lucie, FL)
3. Observe the text of the attribution and map, links on blue or green
4. Perform the same check using a mobile device
## Possible Fixes (optional)
For the `<div class="leaflet-control-attribution leaflet-control…"`, adjust the CSS to make the background 100% white, or move the attribution to just below the map. As a side consideration, the attribution text on mobile may be smaller than the design system minimum requirements.
```diff
<!-- current styling -->
.leaflet-container .leaflet-control-attribution {
background: #fff;
! background: hsla(0,0%,100%,.7);
margin: 0;
}
<!-- possible fix -->
.leaflet-container .leaflet-control-attribution {
background: #fff;
+ background: hsla(0,0%,100%,1);
margin: 0;
}
```
### hsla(0,0,100%,.7)

### hsla(0,0,100%,1)

## WCAG or Vendor Guidance (optional)
* [WCAG 2.0 and Link Colors](https://webaim.org/blog/wcag-2-0-and-link-colors/)
## Screenshots or Trace Logs


### mobile examples





|
1.0
|
[COLOR, COGNITION]: CONSIDER changing background of map attribution - # [508-defect-4](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/accessibility/guidance/defect-severity-rubric.md#508-defect-4)
**Feedback framework**
- **❗️ Must** for if the feedback must be applied
- **⚠️Should** if the feedback is best practice
- **✔️ Consider** for suggestions/enhancements
## Description
**This is a relatively minor thing to consider.** Currently, Mapbox's attribution is placed in a transparent background layered over the map. Depending on where the user focuses the map, it may be hard to distinguish the text of the attribution. Relatively 'textured' areas of the map increase the contrast issues.
**Consider** making the background white or moving the attribution to just below the map instead of an overlay, since there are places the attribution overlays that do not meet contrast requirement of 4.5:1 for WCAG 2.0 Level AA for normal text. In mobile view, the text is especially small, and the contrast issue is really tough. See screenshots for examples of challenges our users may encounter, and recognize many have vision considerations such as low-vision and colorblindness.
## Point of Contact
**VFS Point of Contact:** Jennifer
## Acceptance Criteria
As a low vision user, I want to read the content of the website without any color contrast issues that may confuse.
## Environment
* Operating System: all
* Browser: all
* Server destination: production
## Steps to Recreate
1. Enter `https://www.va.gov/find-locations` in browser
2. Navigate to a destination with lots of water, greenery, and streets (such as Port St Lucie, FL)
3. Observe the text of the attribution and map, links on blue or green
4. Perform the same check using a mobile device
## Possible Fixes (optional)
For the `<div class="leaflet-control-attribution leaflet-control…"`, adjust the CSS to make the background 100% white, or move the attribution to just below the map. As a side consideration, the attribution text on mobile may be smaller than the design system minimum requirements.
```diff
<!-- current styling -->
.leaflet-container .leaflet-control-attribution {
background: #fff;
! background: hsla(0,0%,100%,.7);
margin: 0;
}
<!-- possible fix -->
.leaflet-container .leaflet-control-attribution {
background: #fff;
+ background: hsla(0,0%,100%,1);
margin: 0;
}
```
### hsla(0,0,100%,.7)

### hsla(0,0,100%,1)

## WCAG or Vendor Guidance (optional)
* [WCAG 2.0 and Link Colors](https://webaim.org/blog/wcag-2-0-and-link-colors/)
## Screenshots or Trace Logs


### mobile examples





|
defect
|
consider changing background of map attribution feedback framework ❗️ must for if the feedback must be applied ⚠️should if the feedback is best practice ✔️ consider for suggestions enhancements description this is a relatively minor thing to consider currently mapbox s attribution is placed in a transparent background layered over the map depending on where the user focuses the map it may be hard to distinguish the text of the attribution relatively textured areas of the map increase the contrast issues consider making the background white or moving the attribution to just below the map instead of an overlay since there are places the attribution overlays that do not meet contrast requirement of for wcag level aa for normal text in mobile view the text is especially small and the contrast issue is really tough see screenshots for examples of challenges our users may encounter and recognize many have vision considerations such as low vision and colorblindness point of contact vfs point of contact jennifer acceptance criteria as a low vision user i want to read the content of the website without any color contrast issues that may confuse environment operating system all browser all server destination production steps to recreate enter in browser navigate to a destination with lots of water greenery and streets such as port st lucie fl observe the text of the attribution and map links on blue or green perform the same check using a mobile device possible fixes optional for the div class leaflet control attribution leaflet control… adjust the css to make the background white or move the attribution to just below the map as a side consideration the attribution text on mobile may be smaller than the design system minimum requirements diff leaflet container leaflet control attribution background fff background hsla margin leaflet container leaflet control attribution background fff background hsla margin hsla hsla wcag or vendor guidance optional screenshots or trace logs mobile examples
| 1
|
349,240
| 31,788,664,458
|
IssuesEvent
|
2023-09-13 00:14:30
|
ewlu/riscv-gnu-toolchain
|
https://api.github.com/repos/ewlu/riscv-gnu-toolchain
|
closed
|
Testsuite Status 7997f0d35efca8a24d1b0ceae5066b1019d633d7
|
bug testsuite-failure
|
# Summary
|New Failures|gcc|g++|gfortran|Previous Hash|
|---|---|---|---|---|
|linux: RVA23U64 profile lp64d medlow|23/16|0/0|0/0|[449ab115dece8ac8e8f27d2d7b5bc653a2c75d3a](https://github.com/gcc-mirror/gcc/compare/449ab115dece8ac8e8f27d2d7b5bc653a2c75d3a...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|linux: rv64gcv lp64d medlow|3/1|0/0|0/0|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|linux: rv64imafdc lp64d medlow multilib|3/1|0/0|0/0|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|Resolved Failures|gcc|g++|gfortran|Previous Hash|
|---|---|---|---|---|
|linux: RVA23U64 profile lp64d medlow|21/4|0/0|0/0|[449ab115dece8ac8e8f27d2d7b5bc653a2c75d3a](https://github.com/gcc-mirror/gcc/compare/449ab115dece8ac8e8f27d2d7b5bc653a2c75d3a...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|linux: rv32gcv ilp32d medlow|3/1|0/0|0/0|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|Unresolved Failures|gcc|g++|gfortran|Previous Hash|
|---|---|---|---|---|
|linux: RVA23U64 profile lp64d medlow|20772/4297|10224/2611|18587/3133|[449ab115dece8ac8e8f27d2d7b5bc653a2c75d3a](https://github.com/gcc-mirror/gcc/compare/449ab115dece8ac8e8f27d2d7b5bc653a2c75d3a...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|linux: rv32 Bitmanip ilp32d medlow|39/32|11/4|12/2|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|linux: rv32 Vector Crypto ilp32d medlow|78/64|15/8|79/14|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|linux: rv32gcv ilp32d medlow|75/63|15/8|79/14|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|linux: rv64 Bitmanip lp64d medlow|36/27|9/3|12/2|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|linux: rv64 Vector Crypto lp64d medlow|51/44|10/4|79/14|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|linux: rv64gcv lp64d medlow|51/44|10/4|79/14|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|linux: rv64imafdc lp64d medlow multilib|16/9|9/3|12/2|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|newlib: RVA23U64 profile lp64d medlow|1240/365|1173/331|0/0|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|newlib: rv32 Bitmanip ilp32d medlow|64/15|17/6|0/0|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|newlib: rv32 Vector Crypto ilp32d medlow|104/50|21/10|0/0|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|newlib: rv32gc ilp32d medlow multilib|64/15|17/6|0/0|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|newlib: rv32gcv ilp32d medlow|100/46|21/10|0/0|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|newlib: rv64 Bitmanip lp64d medlow|63/20|15/5|0/0|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|newlib: rv64 Vector Crypto lp64d medlow|85/42|16/6|0/0|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|newlib: rv64gc lp64d medlow multilib|56/13|15/5|0/0|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|newlib: rv64gcv lp64d medlow|81/38|16/6|0/0|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
## Architecture Specific New Failures
linux rv64imafdcv_zicond_zawrs_zbc_zvkng_zvksg_zvbb_zvbc_zicsr_zba_zbb_zbs_zicbom_zicbop_zicboz_zfhmin_zkt lp64d:
```
FAIL: gcc.dg/torture/pr111137.c -O0 execution test
FAIL: gcc.dg/torture/pr111137.c -O1 execution test
FAIL: gcc.dg/torture/pr111137.c -O2 execution test
FAIL: gcc.dg/torture/pr111137.c -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test
FAIL: gcc.dg/torture/pr111137.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects execution test
FAIL: gcc.dg/torture/pr111137.c -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test
FAIL: gcc.dg/torture/pr111137.c -O3 -g execution test
FAIL: gcc.dg/torture/pr111137.c -Os execution test
FAIL: gcc.target/riscv/rvv/autovec/gather-scatter/mask_gather_load_run-11.c execution test
FAIL: gcc.target/riscv/rvv/autovec/reduc/extract_last_run-1.c execution test
FAIL: gcc.target/riscv/rvv/autovec/reduc/extract_last_run-10.c execution test
FAIL: gcc.target/riscv/rvv/autovec/reduc/extract_last_run-11.c execution test
FAIL: gcc.target/riscv/rvv/autovec/reduc/extract_last_run-12.c execution test
FAIL: gcc.target/riscv/rvv/autovec/reduc/extract_last_run-13.c execution test
FAIL: gcc.target/riscv/rvv/autovec/reduc/extract_last_run-14.c execution test
FAIL: gcc.target/riscv/rvv/autovec/reduc/extract_last_run-2.c execution test
FAIL: gcc.target/riscv/rvv/autovec/reduc/extract_last_run-3.c execution test
FAIL: gcc.target/riscv/rvv/autovec/reduc/extract_last_run-4.c execution test
FAIL: gcc.target/riscv/rvv/autovec/reduc/extract_last_run-5.c execution test
FAIL: gcc.target/riscv/rvv/autovec/reduc/extract_last_run-6.c execution test
FAIL: gcc.target/riscv/rvv/autovec/reduc/extract_last_run-7.c execution test
FAIL: gcc.target/riscv/rvv/autovec/reduc/extract_last_run-8.c execution test
FAIL: gcc.target/riscv/rvv/autovec/reduc/extract_last_run-9.c execution test
```
linux rv64gcv lp64d:
```
FAIL: gcc.dg/tree-prof/time-profiler-2.c scan-ipa-dump-times profile "Read tp_first_run: 0" 2
FAIL: gcc.dg/tree-prof/time-profiler-2.c scan-ipa-dump-times profile "Read tp_first_run: 2" 1
FAIL: gcc.dg/tree-prof/time-profiler-2.c scan-ipa-dump-times profile "Read tp_first_run: 3" 1
```
linux rv64gc lp64d multilib:
```
FAIL: gcc.dg/tree-prof/time-profiler-2.c scan-ipa-dump-times profile "Read tp_first_run: 0" 2
FAIL: gcc.dg/tree-prof/time-profiler-2.c scan-ipa-dump-times profile "Read tp_first_run: 2" 1
FAIL: gcc.dg/tree-prof/time-profiler-2.c scan-ipa-dump-times profile "Read tp_first_run: 3" 1
```
## Architecture Specific Resolved Failures
linux rv64imafdcv_zicond_zawrs_zbc_zvkng_zvksg_zvbb_zvbc_zicsr_zba_zbb_zbs_zicbom_zicbop_zicboz_zfhmin_zkt lp64d:
```
FAIL: gcc.target/riscv/rvv/autovec/gather-scatter/mask_gather_load-11.c (internal compiler error: in get_group_load_store_type, at tree-vect-stmts.cc:2121)
FAIL: gcc.target/riscv/rvv/autovec/gather-scatter/mask_gather_load-11.c (test for excess errors)
FAIL: gcc.target/riscv/rvv/autovec/gather-scatter/mask_gather_load-11.c scan-tree-dump-times vect "vectorized 1 loops in function" 88
FAIL: gcc.target/riscv/rvv/autovec/gather-scatter/mask_gather_load_run-11.c (internal compiler error: in get_group_load_store_type, at tree-vect-stmts.cc:2121)
FAIL: gcc.target/riscv/rvv/autovec/gather-scatter/mask_gather_load_run-11.c (test for excess errors)
FAIL: gcc.target/riscv/stack_save_restore_1.c -O0 check-function-bodies bar
FAIL: gcc.target/riscv/stack_save_restore_1.c -O1 check-function-bodies bar
FAIL: gcc.target/riscv/stack_save_restore_1.c -O2 check-function-bodies bar
FAIL: gcc.target/riscv/stack_save_restore_1.c -O2 -flto -fno-use-linker-plugin -flto-partition=none check-function-bodies bar
FAIL: gcc.target/riscv/stack_save_restore_1.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects check-function-bodies bar
FAIL: gcc.target/riscv/stack_save_restore_1.c -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions check-function-bodies bar
FAIL: gcc.target/riscv/stack_save_restore_1.c -O3 -g check-function-bodies bar
FAIL: gcc.target/riscv/stack_save_restore_1.c -Os check-function-bodies bar
FAIL: gcc.target/riscv/stack_save_restore_2.c -O0 check-function-bodies bar
FAIL: gcc.target/riscv/stack_save_restore_2.c -O1 check-function-bodies bar
FAIL: gcc.target/riscv/stack_save_restore_2.c -O2 check-function-bodies bar
FAIL: gcc.target/riscv/stack_save_restore_2.c -O2 -flto -fno-use-linker-plugin -flto-partition=none check-function-bodies bar
FAIL: gcc.target/riscv/stack_save_restore_2.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects check-function-bodies bar
FAIL: gcc.target/riscv/stack_save_restore_2.c -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions check-function-bodies bar
FAIL: gcc.target/riscv/stack_save_restore_2.c -O3 -g check-function-bodies bar
FAIL: gcc.target/riscv/stack_save_restore_2.c -Os check-function-bodies bar
```
linux rv32gcv ilp32d:
```
FAIL: gcc.dg/tree-prof/time-profiler-2.c scan-ipa-dump-times profile "Read tp_first_run: 0" 2
FAIL: gcc.dg/tree-prof/time-profiler-2.c scan-ipa-dump-times profile "Read tp_first_run: 2" 1
FAIL: gcc.dg/tree-prof/time-profiler-2.c scan-ipa-dump-times profile "Read tp_first_run: 3" 1
```
Associated run is: https://github.com/patrick-rivos/riscv-gnu-toolchain/actions/runs/5990805569
|
1.0
|
Testsuite Status 7997f0d35efca8a24d1b0ceae5066b1019d633d7 - # Summary
|New Failures|gcc|g++|gfortran|Previous Hash|
|---|---|---|---|---|
|linux: RVA23U64 profile lp64d medlow|23/16|0/0|0/0|[449ab115dece8ac8e8f27d2d7b5bc653a2c75d3a](https://github.com/gcc-mirror/gcc/compare/449ab115dece8ac8e8f27d2d7b5bc653a2c75d3a...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|linux: rv64gcv lp64d medlow|3/1|0/0|0/0|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|linux: rv64imafdc lp64d medlow multilib|3/1|0/0|0/0|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|Resolved Failures|gcc|g++|gfortran|Previous Hash|
|---|---|---|---|---|
|linux: RVA23U64 profile lp64d medlow|21/4|0/0|0/0|[449ab115dece8ac8e8f27d2d7b5bc653a2c75d3a](https://github.com/gcc-mirror/gcc/compare/449ab115dece8ac8e8f27d2d7b5bc653a2c75d3a...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|linux: rv32gcv ilp32d medlow|3/1|0/0|0/0|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|Unresolved Failures|gcc|g++|gfortran|Previous Hash|
|---|---|---|---|---|
|linux: RVA23U64 profile lp64d medlow|20772/4297|10224/2611|18587/3133|[449ab115dece8ac8e8f27d2d7b5bc653a2c75d3a](https://github.com/gcc-mirror/gcc/compare/449ab115dece8ac8e8f27d2d7b5bc653a2c75d3a...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|linux: rv32 Bitmanip ilp32d medlow|39/32|11/4|12/2|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|linux: rv32 Vector Crypto ilp32d medlow|78/64|15/8|79/14|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|linux: rv32gcv ilp32d medlow|75/63|15/8|79/14|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|linux: rv64 Bitmanip lp64d medlow|36/27|9/3|12/2|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|linux: rv64 Vector Crypto lp64d medlow|51/44|10/4|79/14|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|linux: rv64gcv lp64d medlow|51/44|10/4|79/14|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|linux: rv64imafdc lp64d medlow multilib|16/9|9/3|12/2|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|newlib: RVA23U64 profile lp64d medlow|1240/365|1173/331|0/0|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|newlib: rv32 Bitmanip ilp32d medlow|64/15|17/6|0/0|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|newlib: rv32 Vector Crypto ilp32d medlow|104/50|21/10|0/0|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|newlib: rv32gc ilp32d medlow multilib|64/15|17/6|0/0|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|newlib: rv32gcv ilp32d medlow|100/46|21/10|0/0|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|newlib: rv64 Bitmanip lp64d medlow|63/20|15/5|0/0|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|newlib: rv64 Vector Crypto lp64d medlow|85/42|16/6|0/0|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|newlib: rv64gc lp64d medlow multilib|56/13|15/5|0/0|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
|newlib: rv64gcv lp64d medlow|81/38|16/6|0/0|[44bcb51eb0d5cac6eb2de54541ca8e6c2d738160](https://github.com/gcc-mirror/gcc/compare/44bcb51eb0d5cac6eb2de54541ca8e6c2d738160...7997f0d35efca8a24d1b0ceae5066b1019d633d7)|
## Architecture Specific New Failures
linux rv64imafdcv_zicond_zawrs_zbc_zvkng_zvksg_zvbb_zvbc_zicsr_zba_zbb_zbs_zicbom_zicbop_zicboz_zfhmin_zkt lp64d:
```
FAIL: gcc.dg/torture/pr111137.c -O0 execution test
FAIL: gcc.dg/torture/pr111137.c -O1 execution test
FAIL: gcc.dg/torture/pr111137.c -O2 execution test
FAIL: gcc.dg/torture/pr111137.c -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test
FAIL: gcc.dg/torture/pr111137.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects execution test
FAIL: gcc.dg/torture/pr111137.c -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test
FAIL: gcc.dg/torture/pr111137.c -O3 -g execution test
FAIL: gcc.dg/torture/pr111137.c -Os execution test
FAIL: gcc.target/riscv/rvv/autovec/gather-scatter/mask_gather_load_run-11.c execution test
FAIL: gcc.target/riscv/rvv/autovec/reduc/extract_last_run-1.c execution test
FAIL: gcc.target/riscv/rvv/autovec/reduc/extract_last_run-10.c execution test
FAIL: gcc.target/riscv/rvv/autovec/reduc/extract_last_run-11.c execution test
FAIL: gcc.target/riscv/rvv/autovec/reduc/extract_last_run-12.c execution test
FAIL: gcc.target/riscv/rvv/autovec/reduc/extract_last_run-13.c execution test
FAIL: gcc.target/riscv/rvv/autovec/reduc/extract_last_run-14.c execution test
FAIL: gcc.target/riscv/rvv/autovec/reduc/extract_last_run-2.c execution test
FAIL: gcc.target/riscv/rvv/autovec/reduc/extract_last_run-3.c execution test
FAIL: gcc.target/riscv/rvv/autovec/reduc/extract_last_run-4.c execution test
FAIL: gcc.target/riscv/rvv/autovec/reduc/extract_last_run-5.c execution test
FAIL: gcc.target/riscv/rvv/autovec/reduc/extract_last_run-6.c execution test
FAIL: gcc.target/riscv/rvv/autovec/reduc/extract_last_run-7.c execution test
FAIL: gcc.target/riscv/rvv/autovec/reduc/extract_last_run-8.c execution test
FAIL: gcc.target/riscv/rvv/autovec/reduc/extract_last_run-9.c execution test
```
linux rv64gcv lp64d:
```
FAIL: gcc.dg/tree-prof/time-profiler-2.c scan-ipa-dump-times profile "Read tp_first_run: 0" 2
FAIL: gcc.dg/tree-prof/time-profiler-2.c scan-ipa-dump-times profile "Read tp_first_run: 2" 1
FAIL: gcc.dg/tree-prof/time-profiler-2.c scan-ipa-dump-times profile "Read tp_first_run: 3" 1
```
linux rv64gc lp64d multilib:
```
FAIL: gcc.dg/tree-prof/time-profiler-2.c scan-ipa-dump-times profile "Read tp_first_run: 0" 2
FAIL: gcc.dg/tree-prof/time-profiler-2.c scan-ipa-dump-times profile "Read tp_first_run: 2" 1
FAIL: gcc.dg/tree-prof/time-profiler-2.c scan-ipa-dump-times profile "Read tp_first_run: 3" 1
```
## Architecture Specific Resolved Failures
linux rv64imafdcv_zicond_zawrs_zbc_zvkng_zvksg_zvbb_zvbc_zicsr_zba_zbb_zbs_zicbom_zicbop_zicboz_zfhmin_zkt lp64d:
```
FAIL: gcc.target/riscv/rvv/autovec/gather-scatter/mask_gather_load-11.c (internal compiler error: in get_group_load_store_type, at tree-vect-stmts.cc:2121)
FAIL: gcc.target/riscv/rvv/autovec/gather-scatter/mask_gather_load-11.c (test for excess errors)
FAIL: gcc.target/riscv/rvv/autovec/gather-scatter/mask_gather_load-11.c scan-tree-dump-times vect "vectorized 1 loops in function" 88
FAIL: gcc.target/riscv/rvv/autovec/gather-scatter/mask_gather_load_run-11.c (internal compiler error: in get_group_load_store_type, at tree-vect-stmts.cc:2121)
FAIL: gcc.target/riscv/rvv/autovec/gather-scatter/mask_gather_load_run-11.c (test for excess errors)
FAIL: gcc.target/riscv/stack_save_restore_1.c -O0 check-function-bodies bar
FAIL: gcc.target/riscv/stack_save_restore_1.c -O1 check-function-bodies bar
FAIL: gcc.target/riscv/stack_save_restore_1.c -O2 check-function-bodies bar
FAIL: gcc.target/riscv/stack_save_restore_1.c -O2 -flto -fno-use-linker-plugin -flto-partition=none check-function-bodies bar
FAIL: gcc.target/riscv/stack_save_restore_1.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects check-function-bodies bar
FAIL: gcc.target/riscv/stack_save_restore_1.c -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions check-function-bodies bar
FAIL: gcc.target/riscv/stack_save_restore_1.c -O3 -g check-function-bodies bar
FAIL: gcc.target/riscv/stack_save_restore_1.c -Os check-function-bodies bar
FAIL: gcc.target/riscv/stack_save_restore_2.c -O0 check-function-bodies bar
FAIL: gcc.target/riscv/stack_save_restore_2.c -O1 check-function-bodies bar
FAIL: gcc.target/riscv/stack_save_restore_2.c -O2 check-function-bodies bar
FAIL: gcc.target/riscv/stack_save_restore_2.c -O2 -flto -fno-use-linker-plugin -flto-partition=none check-function-bodies bar
FAIL: gcc.target/riscv/stack_save_restore_2.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects check-function-bodies bar
FAIL: gcc.target/riscv/stack_save_restore_2.c -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions check-function-bodies bar
FAIL: gcc.target/riscv/stack_save_restore_2.c -O3 -g check-function-bodies bar
FAIL: gcc.target/riscv/stack_save_restore_2.c -Os check-function-bodies bar
```
linux rv32gcv ilp32d:
```
FAIL: gcc.dg/tree-prof/time-profiler-2.c scan-ipa-dump-times profile "Read tp_first_run: 0" 2
FAIL: gcc.dg/tree-prof/time-profiler-2.c scan-ipa-dump-times profile "Read tp_first_run: 2" 1
FAIL: gcc.dg/tree-prof/time-profiler-2.c scan-ipa-dump-times profile "Read tp_first_run: 3" 1
```
Associated run is: https://github.com/patrick-rivos/riscv-gnu-toolchain/actions/runs/5990805569
|
non_defect
|
testsuite status summary new failures gcc g gfortran previous hash linux profile medlow linux medlow linux medlow multilib resolved failures gcc g gfortran previous hash linux profile medlow linux medlow unresolved failures gcc g gfortran previous hash linux profile medlow linux bitmanip medlow linux vector crypto medlow linux medlow linux bitmanip medlow linux vector crypto medlow linux medlow linux medlow multilib newlib profile medlow newlib bitmanip medlow newlib vector crypto medlow newlib medlow multilib newlib medlow newlib bitmanip medlow newlib vector crypto medlow newlib medlow multilib newlib medlow architecture specific new failures linux zicond zawrs zbc zvkng zvksg zvbb zvbc zicsr zba zbb zbs zicbom zicbop zicboz zfhmin zkt fail gcc dg torture c execution test fail gcc dg torture c execution test fail gcc dg torture c execution test fail gcc dg torture c flto fno use linker plugin flto partition none execution test fail gcc dg torture c flto fuse linker plugin fno fat lto objects execution test fail gcc dg torture c fomit frame pointer funroll loops fpeel loops ftracer finline functions execution test fail gcc dg torture c g execution test fail gcc dg torture c os execution test fail gcc target riscv rvv autovec gather scatter mask gather load run c execution test fail gcc target riscv rvv autovec reduc extract last run c execution test fail gcc target riscv rvv autovec reduc extract last run c execution test fail gcc target riscv rvv autovec reduc extract last run c execution test fail gcc target riscv rvv autovec reduc extract last run c execution test fail gcc target riscv rvv autovec reduc extract last run c execution test fail gcc target riscv rvv autovec reduc extract last run c execution test fail gcc target riscv rvv autovec reduc extract last run c execution test fail gcc target riscv rvv autovec reduc extract last run c execution test fail gcc target riscv rvv autovec reduc extract last run c execution test fail gcc target riscv rvv autovec reduc extract last run c execution test fail gcc target riscv rvv autovec reduc extract last run c execution test fail gcc target riscv rvv autovec reduc extract last run c execution test fail gcc target riscv rvv autovec reduc extract last run c execution test fail gcc target riscv rvv autovec reduc extract last run c execution test linux fail gcc dg tree prof time profiler c scan ipa dump times profile read tp first run fail gcc dg tree prof time profiler c scan ipa dump times profile read tp first run fail gcc dg tree prof time profiler c scan ipa dump times profile read tp first run linux multilib fail gcc dg tree prof time profiler c scan ipa dump times profile read tp first run fail gcc dg tree prof time profiler c scan ipa dump times profile read tp first run fail gcc dg tree prof time profiler c scan ipa dump times profile read tp first run architecture specific resolved failures linux zicond zawrs zbc zvkng zvksg zvbb zvbc zicsr zba zbb zbs zicbom zicbop zicboz zfhmin zkt fail gcc target riscv rvv autovec gather scatter mask gather load c internal compiler error in get group load store type at tree vect stmts cc fail gcc target riscv rvv autovec gather scatter mask gather load c test for excess errors fail gcc target riscv rvv autovec gather scatter mask gather load c scan tree dump times vect vectorized loops in function fail gcc target riscv rvv autovec gather scatter mask gather load run c internal compiler error in get group load store type at tree vect stmts cc fail gcc target riscv rvv autovec gather scatter mask gather load run c test for excess errors fail gcc target riscv stack save restore c check function bodies bar fail gcc target riscv stack save restore c check function bodies bar fail gcc target riscv stack save restore c check function bodies bar fail gcc target riscv stack save restore c flto fno use linker plugin flto partition none check function bodies bar fail gcc target riscv stack save restore c flto fuse linker plugin fno fat lto objects check function bodies bar fail gcc target riscv stack save restore c fomit frame pointer funroll loops fpeel loops ftracer finline functions check function bodies bar fail gcc target riscv stack save restore c g check function bodies bar fail gcc target riscv stack save restore c os check function bodies bar fail gcc target riscv stack save restore c check function bodies bar fail gcc target riscv stack save restore c check function bodies bar fail gcc target riscv stack save restore c check function bodies bar fail gcc target riscv stack save restore c flto fno use linker plugin flto partition none check function bodies bar fail gcc target riscv stack save restore c flto fuse linker plugin fno fat lto objects check function bodies bar fail gcc target riscv stack save restore c fomit frame pointer funroll loops fpeel loops ftracer finline functions check function bodies bar fail gcc target riscv stack save restore c g check function bodies bar fail gcc target riscv stack save restore c os check function bodies bar linux fail gcc dg tree prof time profiler c scan ipa dump times profile read tp first run fail gcc dg tree prof time profiler c scan ipa dump times profile read tp first run fail gcc dg tree prof time profiler c scan ipa dump times profile read tp first run associated run is
| 0
|
5,438
| 2,610,187,644
|
IssuesEvent
|
2015-02-26 18:59:29
|
chrsmith/quchuseban
|
https://api.github.com/repos/chrsmith/quchuseban
|
opened
|
转载有遗传色斑怎么办
|
auto-migrated Priority-Medium Type-Defect
|
```
《摘要》
雀斑是我们皮肤较容易出现的问题之一,所有皮下色素异常��
�称黄褐斑,也叫黑斑,最常见的雀斑雀斑又称蝴蝶斑、妊娠�
��,中医称为“肝斑”、“黧黑斑”,呈片状,对称性分布,
黄褐色或黑色,多以鼻梁为中心,生于面颊、颧骨、额头部��
�,也有发生于上唇和眉骨部位的,发生人群以中青年女性为�
��,是很多女性朋友最担心的“面子”问题之一。有遗传色斑
怎么办,
《客户案例》
莫名其妙的,脸上不知不觉长了一些小斑点,说多不多��
�说少也不少,怪郁闷的。先自我介绍一下:我28岁,没生过BB
,在一家航空公司工作,按照工作环境来讲,也晒不到太阳��
�不应该长斑点的,可还是莫名其妙的产生了,我在网上查了�
��多原因,最后自己判断可能是常期用电脑,电脑辅射造成的
。尽管这个理由有点牵强。但也只能这样认为了,由于我的��
�肤比较白,所以长点斑看的清清楚楚,弄的我的心情也不太�
��,每天早上在办公室看到丽丽那白净的肌肤,就更有点郁闷
了,唉,爱美之心,人皆有之吧。更何况我是一个爱美一族��
�。<br>
女人有时比较逗,一方面没有信心,但另一方面有抱有��
�望,一个偶然的下午,我在百度贴吧里看到有很多人说「黛�
��薇尔精华液」从色斑根源入手的纯植物配方祛斑产品,看到
那么多人说好还是有点心动的,然后就想反正那么多次都失��
�了,那就再试一次吧,反正是纯植物配方的也不会有什么副�
��用,大不了就当调节内分泌的精华了!天天朝九晚五的上班��
�也早晚按时使用「黛芙薇尔精华液」,时间长了都当作一个�
��惯了也没有太在意,知道有一天下班时候一个同事从我身边
过去不经意间说了句“美女,用什么遮瑕霜啊?脸上的斑都没�
��了。”我一听就觉得奇怪了,我用的化妆品一直没变呀。于
是就拿出粉饼盒打开一照,哎呀,还真是,斑点都淡得快看��
�见了呢。<br>
呵呵,还真是“有意栽花花不开,无心插柳柳成荫”啊��
�虽然现在已经差不多看不见了,不过我还想再使用一个周期�
��固一下呢
阅读了有遗传色斑怎么办,再看脸上容易长斑的原因:
《色斑形成原因》
内部因素
一、压力
当人受到压力时,就会分泌肾上腺素,为对付压力而做��
�备。如果长期受到压力,人体新陈代谢的平衡就会遭到破坏�
��皮肤所需的营养供应趋于缓慢,色素母细胞就会变得很活跃
。
二、荷尔蒙分泌失调
避孕药里所含的女性荷尔蒙雌激素,会刺激麦拉宁细胞��
�分泌而形成不均匀的斑点,因避孕药而形成的斑点,虽然在�
��药中断后会停止,但仍会在皮肤上停留很长一段时间。怀孕
中因女性荷尔蒙雌激素的增加,从怀孕4—5个月开始会容易出
现斑,这时候出现的斑点在产后大部分会消失。可是,新陈��
�谢不正常、肌肤裸露在强烈的紫外线下、精神上受到压力等�
��因,都会使斑加深。有时新长出的斑,产后也不会消失,所
以需要更加注意。
三、新陈代谢缓慢
肝的新陈代谢功能不正常或卵巢功能减退时也会出现斑��
�因为新陈代谢不顺畅、或内分泌失调,使身体处于敏感状态�
��,从而加剧色素问题。我们常说的便秘会形成斑,其实就是
内分泌失调导致过敏体质而形成的。另外,身体状态不正常��
�时候,紫外线的照射也会加速斑的形成。
四、错误的使用化妆品
使用了不适合自己皮肤的化妆品,会导致皮肤过敏。在��
�疗的过程中如过量照射到紫外线,皮肤会为了抵御外界的侵�
��,在有炎症的部位聚集麦拉宁色素,这样会出现色素沉着的
问题。
外部因素
一、紫外线
照射紫外线的时候,人体为了保护皮肤,会在基底层产��
�很多麦拉宁色素。所以为了保护皮肤,会在敏感部位聚集更�
��的色素。经常裸露在强烈的阳光底下不仅促进皮肤的老化,
还会引起黑斑、雀斑等色素沉着的皮肤疾患。
二、不良的清洁习惯
因强烈的清洁习惯使皮肤变得敏感,这样会刺激皮肤。��
�皮肤敏感时,人体为了保护皮肤,黑色素细胞会分泌很多麦�
��宁色素,当色素过剩时就出现了斑、瑕疵等皮肤色素沉着的
问题。
三、遗传基因
父母中有长斑的,则本人长斑的概率就很高,这种情况��
�一定程度上就可判定是遗传基因的作用。所以家里特别是长�
��有长斑的人,要注意避免引发长斑的重要因素之一——紫外
线照射,这是预防斑必须注意的。
《有疑问帮你解决》
1,黛芙薇尔精华液真的有效果吗?真的可以把脸上的黄褐��
�去掉吗?
答:黛芙薇尔精华液DNA精华能够有效的修复周围难以触��
�的色斑,其独有的纳豆成分为皮肤的美白与靓丽,提供了必�
��可少的营养物质,可以有效的去除黄褐斑,黄褐斑,黄褐斑
,蝴蝶斑,晒斑、妊娠斑等。它它完全突破了传统的美肤时��
�,宛如在皮肤中注入了一杯兼具活化、再生、滋养等功效的�
��尾酒,同时为脸部提供大量有机维生素精华,脸部的改变显
而易见。自产品上市以来,老顾客纷纷介绍新顾客,71%的新��
�客都是通过老顾客介绍而来,口碑由此而来!
2,服用黛芙薇尔美白,会伤身体吗?有副作用吗?
答:黛芙薇尔精华液应用了精纯复合配方和领先的分类��
�斑科技,并将“DNA美肤系统”疗法应用到了该产品中,能彻�
��祛除黄褐斑,蝴蝶斑,妊娠斑,晒斑,黄褐斑,老年斑,有
效淡化黄褐斑至接近肤色。黛芙薇尔通过法国、美国、台湾��
�地的专家通力协作,超过10年的研究以全新的DNA肌肤修复技��
�,挑战传统化学护肤理念,不懈追寻发现破译大自然的美丽�
��迹,令每一位爱美的女性都能享受到科技创新所带来的自然
之美。
专为亚洲女性肤质研制,精心呵护女性美丽,多年来,为数��
�百万计的女性解除了黄褐斑困扰。深得广大女性朋友的信赖!
3,去除黄褐斑之后,会反弹吗?
答:很多曾经长了黄褐斑的人士,自从选择了黛芙薇尔��
�白,就一劳永逸。这款祛斑产品是经过数十位权威祛斑专家�
��据斑的形成原因精心研制而成用事实说话,让消费者打分。
树立权威品牌!我们的很多新客户都是老客户介绍而来,请问�
��如果效果不好,会有客户转介绍吗?
4,你们的价格有点贵,能不能便宜一点?
答:如果您使用西药最少需要2000元,煎服的药最少需要3
000元,做手术最少是5000元,而这些毫无疑问,不会对彻底去�
��你的斑点有任何帮助!一分价钱,一份价值,我们现在做的��
�是一个口碑,一个品牌,价钱并不高。如果花这点钱把你的�
��褐斑彻底去除,你还会觉得贵吗?你还会再去花那么多冤枉��
�,不但斑没去掉,还把自己的皮肤弄的越来越糟吗
5,我适合用黛芙薇尔精华液吗?
答:黛芙薇尔适用人群:
1、生理紊乱引起的黄褐斑人群
2、生育引起的妊娠斑人群
3、年纪增长引起的老年斑人群
4、化妆品色素沉积、辐射斑人群
5、长期日照引起的日晒斑人群
6、肌肤暗淡急需美白的人群
《祛斑小方法》
有遗传色斑怎么办,同时为您分享祛斑小方法
1、将鲜明萝卜辟碎挤汁,取10-30毫升,每日上晚洗完脸后涂��
�,待干后,洗净。此外,每日喝一杯胡萝卜,可美白肌肤。
2.将柠檬汁搅汁,加糖水适量饮用。柠檬中含有大量维生素C��
�钙、磷、铁等。常饮柠檬汁不仅可美白肌肤,还能使黑色素�
��淀,达到祛斑的作用。
```
-----
Original issue reported on code.google.com by `additive...@gmail.com` on 1 Jul 2014 at 4:15
|
1.0
|
转载有遗传色斑怎么办 - ```
《摘要》
雀斑是我们皮肤较容易出现的问题之一,所有皮下色素异常��
�称黄褐斑,也叫黑斑,最常见的雀斑雀斑又称蝴蝶斑、妊娠�
��,中医称为“肝斑”、“黧黑斑”,呈片状,对称性分布,
黄褐色或黑色,多以鼻梁为中心,生于面颊、颧骨、额头部��
�,也有发生于上唇和眉骨部位的,发生人群以中青年女性为�
��,是很多女性朋友最担心的“面子”问题之一。有遗传色斑
怎么办,
《客户案例》
莫名其妙的,脸上不知不觉长了一些小斑点,说多不多��
�说少也不少,怪郁闷的。先自我介绍一下:我28岁,没生过BB
,在一家航空公司工作,按照工作环境来讲,也晒不到太阳��
�不应该长斑点的,可还是莫名其妙的产生了,我在网上查了�
��多原因,最后自己判断可能是常期用电脑,电脑辅射造成的
。尽管这个理由有点牵强。但也只能这样认为了,由于我的��
�肤比较白,所以长点斑看的清清楚楚,弄的我的心情也不太�
��,每天早上在办公室看到丽丽那白净的肌肤,就更有点郁闷
了,唉,爱美之心,人皆有之吧。更何况我是一个爱美一族��
�。<br>
女人有时比较逗,一方面没有信心,但另一方面有抱有��
�望,一个偶然的下午,我在百度贴吧里看到有很多人说「黛�
��薇尔精华液」从色斑根源入手的纯植物配方祛斑产品,看到
那么多人说好还是有点心动的,然后就想反正那么多次都失��
�了,那就再试一次吧,反正是纯植物配方的也不会有什么副�
��用,大不了就当调节内分泌的精华了!天天朝九晚五的上班��
�也早晚按时使用「黛芙薇尔精华液」,时间长了都当作一个�
��惯了也没有太在意,知道有一天下班时候一个同事从我身边
过去不经意间说了句“美女,用什么遮瑕霜啊?脸上的斑都没�
��了。”我一听就觉得奇怪了,我用的化妆品一直没变呀。于
是就拿出粉饼盒打开一照,哎呀,还真是,斑点都淡得快看��
�见了呢。<br>
呵呵,还真是“有意栽花花不开,无心插柳柳成荫”啊��
�虽然现在已经差不多看不见了,不过我还想再使用一个周期�
��固一下呢
阅读了有遗传色斑怎么办,再看脸上容易长斑的原因:
《色斑形成原因》
内部因素
一、压力
当人受到压力时,就会分泌肾上腺素,为对付压力而做��
�备。如果长期受到压力,人体新陈代谢的平衡就会遭到破坏�
��皮肤所需的营养供应趋于缓慢,色素母细胞就会变得很活跃
。
二、荷尔蒙分泌失调
避孕药里所含的女性荷尔蒙雌激素,会刺激麦拉宁细胞��
�分泌而形成不均匀的斑点,因避孕药而形成的斑点,虽然在�
��药中断后会停止,但仍会在皮肤上停留很长一段时间。怀孕
中因女性荷尔蒙雌激素的增加,从怀孕4—5个月开始会容易出
现斑,这时候出现的斑点在产后大部分会消失。可是,新陈��
�谢不正常、肌肤裸露在强烈的紫外线下、精神上受到压力等�
��因,都会使斑加深。有时新长出的斑,产后也不会消失,所
以需要更加注意。
三、新陈代谢缓慢
肝的新陈代谢功能不正常或卵巢功能减退时也会出现斑��
�因为新陈代谢不顺畅、或内分泌失调,使身体处于敏感状态�
��,从而加剧色素问题。我们常说的便秘会形成斑,其实就是
内分泌失调导致过敏体质而形成的。另外,身体状态不正常��
�时候,紫外线的照射也会加速斑的形成。
四、错误的使用化妆品
使用了不适合自己皮肤的化妆品,会导致皮肤过敏。在��
�疗的过程中如过量照射到紫外线,皮肤会为了抵御外界的侵�
��,在有炎症的部位聚集麦拉宁色素,这样会出现色素沉着的
问题。
外部因素
一、紫外线
照射紫外线的时候,人体为了保护皮肤,会在基底层产��
�很多麦拉宁色素。所以为了保护皮肤,会在敏感部位聚集更�
��的色素。经常裸露在强烈的阳光底下不仅促进皮肤的老化,
还会引起黑斑、雀斑等色素沉着的皮肤疾患。
二、不良的清洁习惯
因强烈的清洁习惯使皮肤变得敏感,这样会刺激皮肤。��
�皮肤敏感时,人体为了保护皮肤,黑色素细胞会分泌很多麦�
��宁色素,当色素过剩时就出现了斑、瑕疵等皮肤色素沉着的
问题。
三、遗传基因
父母中有长斑的,则本人长斑的概率就很高,这种情况��
�一定程度上就可判定是遗传基因的作用。所以家里特别是长�
��有长斑的人,要注意避免引发长斑的重要因素之一——紫外
线照射,这是预防斑必须注意的。
《有疑问帮你解决》
1,黛芙薇尔精华液真的有效果吗?真的可以把脸上的黄褐��
�去掉吗?
答:黛芙薇尔精华液DNA精华能够有效的修复周围难以触��
�的色斑,其独有的纳豆成分为皮肤的美白与靓丽,提供了必�
��可少的营养物质,可以有效的去除黄褐斑,黄褐斑,黄褐斑
,蝴蝶斑,晒斑、妊娠斑等。它它完全突破了传统的美肤时��
�,宛如在皮肤中注入了一杯兼具活化、再生、滋养等功效的�
��尾酒,同时为脸部提供大量有机维生素精华,脸部的改变显
而易见。自产品上市以来,老顾客纷纷介绍新顾客,71%的新��
�客都是通过老顾客介绍而来,口碑由此而来!
2,服用黛芙薇尔美白,会伤身体吗?有副作用吗?
答:黛芙薇尔精华液应用了精纯复合配方和领先的分类��
�斑科技,并将“DNA美肤系统”疗法应用到了该产品中,能彻�
��祛除黄褐斑,蝴蝶斑,妊娠斑,晒斑,黄褐斑,老年斑,有
效淡化黄褐斑至接近肤色。黛芙薇尔通过法国、美国、台湾��
�地的专家通力协作,超过10年的研究以全新的DNA肌肤修复技��
�,挑战传统化学护肤理念,不懈追寻发现破译大自然的美丽�
��迹,令每一位爱美的女性都能享受到科技创新所带来的自然
之美。
专为亚洲女性肤质研制,精心呵护女性美丽,多年来,为数��
�百万计的女性解除了黄褐斑困扰。深得广大女性朋友的信赖!
3,去除黄褐斑之后,会反弹吗?
答:很多曾经长了黄褐斑的人士,自从选择了黛芙薇尔��
�白,就一劳永逸。这款祛斑产品是经过数十位权威祛斑专家�
��据斑的形成原因精心研制而成用事实说话,让消费者打分。
树立权威品牌!我们的很多新客户都是老客户介绍而来,请问�
��如果效果不好,会有客户转介绍吗?
4,你们的价格有点贵,能不能便宜一点?
答:如果您使用西药最少需要2000元,煎服的药最少需要3
000元,做手术最少是5000元,而这些毫无疑问,不会对彻底去�
��你的斑点有任何帮助!一分价钱,一份价值,我们现在做的��
�是一个口碑,一个品牌,价钱并不高。如果花这点钱把你的�
��褐斑彻底去除,你还会觉得贵吗?你还会再去花那么多冤枉��
�,不但斑没去掉,还把自己的皮肤弄的越来越糟吗
5,我适合用黛芙薇尔精华液吗?
答:黛芙薇尔适用人群:
1、生理紊乱引起的黄褐斑人群
2、生育引起的妊娠斑人群
3、年纪增长引起的老年斑人群
4、化妆品色素沉积、辐射斑人群
5、长期日照引起的日晒斑人群
6、肌肤暗淡急需美白的人群
《祛斑小方法》
有遗传色斑怎么办,同时为您分享祛斑小方法
1、将鲜明萝卜辟碎挤汁,取10-30毫升,每日上晚洗完脸后涂��
�,待干后,洗净。此外,每日喝一杯胡萝卜,可美白肌肤。
2.将柠檬汁搅汁,加糖水适量饮用。柠檬中含有大量维生素C��
�钙、磷、铁等。常饮柠檬汁不仅可美白肌肤,还能使黑色素�
��淀,达到祛斑的作用。
```
-----
Original issue reported on code.google.com by `additive...@gmail.com` on 1 Jul 2014 at 4:15
|
defect
|
转载有遗传色斑怎么办 《摘要》 雀斑是我们皮肤较容易出现的问题之一,所有皮下色素异常�� �称黄褐斑,也叫黑斑,最常见的雀斑雀斑又称蝴蝶斑、妊娠� ��,中医称为“肝斑”、“黧黑斑”,呈片状,对称性分布, 黄褐色或黑色,多以鼻梁为中心,生于面颊、颧骨、额头部�� �,也有发生于上唇和眉骨部位的,发生人群以中青年女性为� ��,是很多女性朋友最担心的“面子”问题之一。有遗传色斑 怎么办, 《客户案例》 莫名其妙的,脸上不知不觉长了一些小斑点,说多不多�� �说少也不少,怪郁闷的。先自我介绍一下: ,没生过bb ,在一家航空公司工作,按照工作环境来讲,也晒不到太阳�� �不应该长斑点的,可还是莫名其妙的产生了,我在网上查了� ��多原因,最后自己判断可能是常期用电脑,电脑辅射造成的 。尽管这个理由有点牵强。但也只能这样认为了,由于我的�� �肤比较白,所以长点斑看的清清楚楚,弄的我的心情也不太� ��,每天早上在办公室看到丽丽那白净的肌肤,就更有点郁闷 了,唉,爱美之心,人皆有之吧。更何况我是一个爱美一族�� �。 女人有时比较逗,一方面没有信心,但另一方面有抱有�� �望,一个偶然的下午,我在百度贴吧里看到有很多人说「黛� ��薇尔精华液」从色斑根源入手的纯植物配方祛斑产品,看到 那么多人说好还是有点心动的,然后就想反正那么多次都失�� �了,那就再试一次吧,反正是纯植物配方的也不会有什么副� ��用,大不了就当调节内分泌的精华了 天天朝九晚五的上班�� �也早晚按时使用「黛芙薇尔精华液」,时间长了都当作一个� ��惯了也没有太在意,知道有一天下班时候一个同事从我身边 过去不经意间说了句“美女,用什么遮瑕霜啊 脸上的斑都没� ��了。”我一听就觉得奇怪了,我用的化妆品一直没变呀。于 是就拿出粉饼盒打开一照,哎呀,还真是,斑点都淡得快看�� �见了呢。 呵呵,还真是“有意栽花花不开,无心插柳柳成荫”啊�� �虽然现在已经差不多看不见了,不过我还想再使用一个周期� ��固一下呢 阅读了有遗传色斑怎么办,再看脸上容易长斑的原因: 《色斑形成原因》 内部因素 一、压力 当人受到压力时,就会分泌肾上腺素,为对付压力而做�� �备。如果长期受到压力,人体新陈代谢的平衡就会遭到破坏� ��皮肤所需的营养供应趋于缓慢,色素母细胞就会变得很活跃 。 二、荷尔蒙分泌失调 避孕药里所含的女性荷尔蒙雌激素,会刺激麦拉宁细胞�� �分泌而形成不均匀的斑点,因避孕药而形成的斑点,虽然在� ��药中断后会停止,但仍会在皮肤上停留很长一段时间。怀孕 中因女性荷尔蒙雌激素的增加, — 现斑,这时候出现的斑点在产后大部分会消失。可是,新陈�� �谢不正常、肌肤裸露在强烈的紫外线下、精神上受到压力等� ��因,都会使斑加深。有时新长出的斑,产后也不会消失,所 以需要更加注意。 三、新陈代谢缓慢 肝的新陈代谢功能不正常或卵巢功能减退时也会出现斑�� �因为新陈代谢不顺畅、或内分泌失调,使身体处于敏感状态� ��,从而加剧色素问题。我们常说的便秘会形成斑,其实就是 内分泌失调导致过敏体质而形成的。另外,身体状态不正常�� �时候,紫外线的照射也会加速斑的形成。 四、错误的使用化妆品 使用了不适合自己皮肤的化妆品,会导致皮肤过敏。在�� �疗的过程中如过量照射到紫外线,皮肤会为了抵御外界的侵� ��,在有炎症的部位聚集麦拉宁色素,这样会出现色素沉着的 问题。 外部因素 一、紫外线 照射紫外线的时候,人体为了保护皮肤,会在基底层产�� �很多麦拉宁色素。所以为了保护皮肤,会在敏感部位聚集更� ��的色素。经常裸露在强烈的阳光底下不仅促进皮肤的老化, 还会引起黑斑、雀斑等色素沉着的皮肤疾患。 二、不良的清洁习惯 因强烈的清洁习惯使皮肤变得敏感,这样会刺激皮肤。�� �皮肤敏感时,人体为了保护皮肤,黑色素细胞会分泌很多麦� ��宁色素,当色素过剩时就出现了斑、瑕疵等皮肤色素沉着的 问题。 三、遗传基因 父母中有长斑的,则本人长斑的概率就很高,这种情况�� �一定程度上就可判定是遗传基因的作用。所以家里特别是长� ��有长斑的人,要注意避免引发长斑的重要因素之一——紫外 线照射,这是预防斑必须注意的。 《有疑问帮你解决》 黛芙薇尔精华液真的有效果吗 真的可以把脸上的黄褐�� �去掉吗 答:黛芙薇尔精华液dna精华能够有效的修复周围难以触�� �的色斑,其独有的纳豆成分为皮肤的美白与靓丽,提供了必� ��可少的营养物质,可以有效的去除黄褐斑,黄褐斑,黄褐斑 ,蝴蝶斑,晒斑、妊娠斑等。它它完全突破了传统的美肤时�� �,宛如在皮肤中注入了一杯兼具活化、再生、滋养等功效的� ��尾酒,同时为脸部提供大量有机维生素精华,脸部的改变显 而易见。自产品上市以来,老顾客纷纷介绍新顾客, 的新�� �客都是通过老顾客介绍而来,口碑由此而来 ,服用黛芙薇尔美白,会伤身体吗 有副作用吗 答:黛芙薇尔精华液应用了精纯复合配方和领先的分类�� �斑科技,并将“dna美肤系统”疗法应用到了该产品中,能彻� ��祛除黄褐斑,蝴蝶斑,妊娠斑,晒斑,黄褐斑,老年斑,有 效淡化黄褐斑至接近肤色。黛芙薇尔通过法国、美国、台湾�� �地的专家通力协作, �� �,挑战传统化学护肤理念,不懈追寻发现破译大自然的美丽� ��迹,令每一位爱美的女性都能享受到科技创新所带来的自然 之美。 专为亚洲女性肤质研制,精心呵护女性美丽,多年来,为数�� �百万计的女性解除了黄褐斑困扰。深得广大女性朋友的信赖 ,去除黄褐斑之后,会反弹吗 答:很多曾经长了黄褐斑的人士,自从选择了黛芙薇尔�� �白,就一劳永逸。这款祛斑产品是经过数十位权威祛斑专家� ��据斑的形成原因精心研制而成用事实说话,让消费者打分。 树立权威品牌 我们的很多新客户都是老客户介绍而来,请问� ��如果效果不好,会有客户转介绍吗 ,你们的价格有点贵,能不能便宜一点 答: , , ,而这些毫无疑问,不会对彻底去� ��你的斑点有任何帮助 一分价钱,一份价值,我们现在做的�� �是一个口碑,一个品牌,价钱并不高。如果花这点钱把你的� ��褐斑彻底去除,你还会觉得贵吗 你还会再去花那么多冤枉�� �,不但斑没去掉,还把自己的皮肤弄的越来越糟吗 ,我适合用黛芙薇尔精华液吗 答:黛芙薇尔适用人群: 、生理紊乱引起的黄褐斑人群 、生育引起的妊娠斑人群 、年纪增长引起的老年斑人群 、化妆品色素沉积、辐射斑人群 、长期日照引起的日晒斑人群 、肌肤暗淡急需美白的人群 《祛斑小方法》 有遗传色斑怎么办,同时为您分享祛斑小方法 、将鲜明萝卜辟碎挤汁, ,每日上晚洗完脸后涂�� �,待干后,洗净。此外,每日喝一杯胡萝卜,可美白肌肤。 将柠檬汁搅汁,加糖水适量饮用。柠檬中含有大量维生素c�� �钙、磷、铁等。常饮柠檬汁不仅可美白肌肤,还能使黑色素� ��淀,达到祛斑的作用。 original issue reported on code google com by additive gmail com on jul at
| 1
|
96,996
| 16,177,554,078
|
IssuesEvent
|
2021-05-03 09:25:14
|
Vento-Nuenenen/lola
|
https://api.github.com/repos/Vento-Nuenenen/lola
|
closed
|
CVE-2021-28092 (High) detected in is-svg-3.0.0.tgz - autoclosed
|
security vulnerability
|
## CVE-2021-28092 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>is-svg-3.0.0.tgz</b></p></summary>
<p>Check if a string or buffer is SVG</p>
<p>Library home page: <a href="https://registry.npmjs.org/is-svg/-/is-svg-3.0.0.tgz">https://registry.npmjs.org/is-svg/-/is-svg-3.0.0.tgz</a></p>
<p>Path to dependency file: lola/package.json</p>
<p>Path to vulnerable library: lola/node_modules/is-svg/package.json</p>
<p>
Dependency Hierarchy:
- laravel-mix-6.0.16.tgz (Root Library)
- cssnano-4.1.10.tgz
- cssnano-preset-default-4.0.7.tgz
- postcss-svgo-4.0.2.tgz
- :x: **is-svg-3.0.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Vento-Nuenenen/lola/commit/8c5c9c5cb56c7e67959694247dd5007a1e4018bc">8c5c9c5cb56c7e67959694247dd5007a1e4018bc</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>
The is-svg package 2.1.0 through 4.2.1 for Node.js uses a regular expression that is vulnerable to Regular Expression Denial of Service (ReDoS). If an attacker provides a malicious string, is-svg will get stuck processing the input for a very long time.
<p>Publish Date: 2021-03-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-28092>CVE-2021-28092</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-28092">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-28092</a></p>
<p>Release Date: 2021-03-12</p>
<p>Fix Resolution: v4.2.2</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-28092 (High) detected in is-svg-3.0.0.tgz - autoclosed - ## CVE-2021-28092 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>is-svg-3.0.0.tgz</b></p></summary>
<p>Check if a string or buffer is SVG</p>
<p>Library home page: <a href="https://registry.npmjs.org/is-svg/-/is-svg-3.0.0.tgz">https://registry.npmjs.org/is-svg/-/is-svg-3.0.0.tgz</a></p>
<p>Path to dependency file: lola/package.json</p>
<p>Path to vulnerable library: lola/node_modules/is-svg/package.json</p>
<p>
Dependency Hierarchy:
- laravel-mix-6.0.16.tgz (Root Library)
- cssnano-4.1.10.tgz
- cssnano-preset-default-4.0.7.tgz
- postcss-svgo-4.0.2.tgz
- :x: **is-svg-3.0.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Vento-Nuenenen/lola/commit/8c5c9c5cb56c7e67959694247dd5007a1e4018bc">8c5c9c5cb56c7e67959694247dd5007a1e4018bc</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>
The is-svg package 2.1.0 through 4.2.1 for Node.js uses a regular expression that is vulnerable to Regular Expression Denial of Service (ReDoS). If an attacker provides a malicious string, is-svg will get stuck processing the input for a very long time.
<p>Publish Date: 2021-03-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-28092>CVE-2021-28092</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-28092">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-28092</a></p>
<p>Release Date: 2021-03-12</p>
<p>Fix Resolution: v4.2.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_defect
|
cve high detected in is svg tgz autoclosed cve high severity vulnerability vulnerable library is svg tgz check if a string or buffer is svg library home page a href path to dependency file lola package json path to vulnerable library lola node modules is svg package json dependency hierarchy laravel mix tgz root library cssnano tgz cssnano preset default tgz postcss svgo tgz x is svg tgz vulnerable library found in head commit a href found in base branch master vulnerability details the is svg package through for node js uses a regular expression that is vulnerable to regular expression denial of service redos if an attacker provides a malicious string is svg will get stuck processing the input for a very long time 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 whitesource
| 0
|
44,718
| 12,360,546,033
|
IssuesEvent
|
2020-05-17 15:42:57
|
nsalomonis/altanalyze
|
https://api.github.com/repos/nsalomonis/altanalyze
|
closed
|
Batch effect error
|
Priority-Medium Type-Defect auto-migrated
|
```
Hello!
I kindly wanted to ask if you could help me to solve the batch effect removal
error:
What steps will reproduce the problem?
1. Batch effect removal
What is the expected output? What do you see instead?
Traceback (most recent call last):
File "ExpressionBuilder.pyc", line 1492, in remoteExpressionBuilder
File "combat.pyc", line 7, in <module>
File "patsy\__init__.pyc", line 77, in <module>
File "patsy\highlevel.pyc", line 20, in <module>
File "patsy\desc.pyc", line 84, in <module>
File "<string>", line 1, in <module>
ImportError: No module named builtins
What version of the product are you using? On what operating system?
2.0.8.1, Windows 7
Thank you!!
```
Original issue reported on code.google.com by `gitarres...@gmail.com` on 19 May 2015 at 12:26
|
1.0
|
Batch effect error - ```
Hello!
I kindly wanted to ask if you could help me to solve the batch effect removal
error:
What steps will reproduce the problem?
1. Batch effect removal
What is the expected output? What do you see instead?
Traceback (most recent call last):
File "ExpressionBuilder.pyc", line 1492, in remoteExpressionBuilder
File "combat.pyc", line 7, in <module>
File "patsy\__init__.pyc", line 77, in <module>
File "patsy\highlevel.pyc", line 20, in <module>
File "patsy\desc.pyc", line 84, in <module>
File "<string>", line 1, in <module>
ImportError: No module named builtins
What version of the product are you using? On what operating system?
2.0.8.1, Windows 7
Thank you!!
```
Original issue reported on code.google.com by `gitarres...@gmail.com` on 19 May 2015 at 12:26
|
defect
|
batch effect error hello i kindly wanted to ask if you could help me to solve the batch effect removal error what steps will reproduce the problem batch effect removal what is the expected output what do you see instead traceback most recent call last file expressionbuilder pyc line in remoteexpressionbuilder file combat pyc line in file patsy init pyc line in file patsy highlevel pyc line in file patsy desc pyc line in file line in importerror no module named builtins what version of the product are you using on what operating system windows thank you original issue reported on code google com by gitarres gmail com on may at
| 1
|
52,715
| 13,224,962,494
|
IssuesEvent
|
2020-08-17 20:12:27
|
icecube-trac/tix4
|
https://api.github.com/repos/icecube-trac/tix4
|
closed
|
compiling IceVer with suse 11 and gcc 4.3.2 (Trac #210)
|
IceVer Migrated from Trac defect
|
```text
To: dataclass
Subject: [dataclass] compiling IceVer with suse 11 and gcc 4.3.2
Date: Wed, 1 Sep 2010 10:25:50 +0200
Hi,
I'm not sure if this is the right list but it can't be totally wrong.
I'm doing simulation production on a cluster running suse 11 and gcc 4.3.2
and I had some problems compiling IceVer/V03-00-03_sim which I hadn't when
it was suse 10 and gcc 4.1.2
1. cmake sets 'CURSES_NCURSES_INCLUDE_PATH:PATH=/usr/include/' but the
ncurses files are in '/usr/include/ncurses' and there are no links, so I had
to change it in the CMakeCache.txt
2. map.h could not be found. To solve this I changed '#include "map.h"' to
'#include <map>' in
'IceVer/V03-00-03_sim/src/interstring-verification/private/avgTDP/avgTDP.cxx'
and
'IceVer/V03-00-03_sim/src/interstring-verification/private/cmpTDP/cmpTDP.cxx'
3. vector.h could not be found. Same solution as with map.h: '#include
"vector.h"' --> '#include <vector>' in
'V03-00-03_sim/src/toptiming-verification/public/toptiming-verification/reco/I3TopCombiFitParams.h'
For 2&3 I first tried adding the paths where the files are to $CPATH, but
this ended up in a 'includes nested to deeply' error.
After this modifications compiling works fine and simulation doesn't throw
any errors.
Nevertheless there lots of warnings about functions which will not be
support in the future:
/usr/include/c++/4.3/backward/backward_warning.h:33:2: warning: #warning
This
file includes at least one deprecated or antiquated header which may be
removed without further notice at a future date. Please use a non-
deprecated interface with equivalent functionality instead. For a listing
of replacement headers and interfaces, consult the file backward_warning.h.
To disable this warning use -Wno-deprecated.
<details>
<summary><em>Migrated from <a href="https://code.icecube.wisc.edu/projects/icecube/ticket/210">https://code.icecube.wisc.edu/projects/icecube/ticket/210</a>, reported by nega</summary>
<p>
```json
{
"status": "closed",
"changetime": "2010-09-02T20:52:14",
"_ts": "1283460734000000",
"description": "{{{\n\nTo: dataclass\nSubject: [dataclass] compiling IceVer with suse 11 and gcc 4.3.2\nDate: Wed, 1 Sep 2010 10:25:50 +0200\n\nHi,\nI'm not sure if this is the right list but it can't be totally wrong.\n\nI'm doing simulation production on a cluster running suse 11 and gcc 4.3.2\nand I had some problems compiling IceVer/V03-00-03_sim which I hadn't when\nit was suse 10 and gcc 4.1.2\n\n1. cmake sets 'CURSES_NCURSES_INCLUDE_PATH:PATH=/usr/include/' but the\nncurses files are in '/usr/include/ncurses' and there are no links, so I had\nto change it in the CMakeCache.txt\n\n2. map.h could not be found. To solve this I changed '#include \"map.h\"' to\n'#include <map>' in\n'IceVer/V03-00-03_sim/src/interstring-verification/private/avgTDP/avgTDP.cxx'\nand\n'IceVer/V03-00-03_sim/src/interstring-verification/private/cmpTDP/cmpTDP.cxx'\n\n3. vector.h could not be found. Same solution as with map.h: '#include\n\"vector.h\"' --> '#include <vector>' in\n'V03-00-03_sim/src/toptiming-verification/public/toptiming-verification/reco/I3TopCombiFitParams.h'\n\nFor 2&3 I first tried adding the paths where the files are to $CPATH, but\nthis ended up in a 'includes nested to deeply' error.\n\nAfter this modifications compiling works fine and simulation doesn't throw\nany errors.\n\nNevertheless there lots of warnings about functions which will not be\nsupport in the future:\n\n/usr/include/c++/4.3/backward/backward_warning.h:33:2: warning: #warning\nThis\nfile includes at least one deprecated or antiquated header which may be\nremoved without further notice at a future date. Please use a non-\ndeprecated interface with equivalent functionality instead. For a listing\nof replacement headers and interfaces, consult the file backward_warning.h.\nTo disable this warning use -Wno-deprecated.\n\n",
"reporter": "nega",
"cc": "",
"resolution": "fixed",
"time": "2010-09-02T20:33:50",
"component": "IceVer",
"summary": "compiling IceVer with suse 11 and gcc 4.3.2",
"priority": "normal",
"keywords": "",
"milestone": "",
"owner": "",
"type": "defect"
}
```
</p>
</details>
|
1.0
|
compiling IceVer with suse 11 and gcc 4.3.2 (Trac #210) -
```text
To: dataclass
Subject: [dataclass] compiling IceVer with suse 11 and gcc 4.3.2
Date: Wed, 1 Sep 2010 10:25:50 +0200
Hi,
I'm not sure if this is the right list but it can't be totally wrong.
I'm doing simulation production on a cluster running suse 11 and gcc 4.3.2
and I had some problems compiling IceVer/V03-00-03_sim which I hadn't when
it was suse 10 and gcc 4.1.2
1. cmake sets 'CURSES_NCURSES_INCLUDE_PATH:PATH=/usr/include/' but the
ncurses files are in '/usr/include/ncurses' and there are no links, so I had
to change it in the CMakeCache.txt
2. map.h could not be found. To solve this I changed '#include "map.h"' to
'#include <map>' in
'IceVer/V03-00-03_sim/src/interstring-verification/private/avgTDP/avgTDP.cxx'
and
'IceVer/V03-00-03_sim/src/interstring-verification/private/cmpTDP/cmpTDP.cxx'
3. vector.h could not be found. Same solution as with map.h: '#include
"vector.h"' --> '#include <vector>' in
'V03-00-03_sim/src/toptiming-verification/public/toptiming-verification/reco/I3TopCombiFitParams.h'
For 2&3 I first tried adding the paths where the files are to $CPATH, but
this ended up in a 'includes nested to deeply' error.
After this modifications compiling works fine and simulation doesn't throw
any errors.
Nevertheless there lots of warnings about functions which will not be
support in the future:
/usr/include/c++/4.3/backward/backward_warning.h:33:2: warning: #warning
This
file includes at least one deprecated or antiquated header which may be
removed without further notice at a future date. Please use a non-
deprecated interface with equivalent functionality instead. For a listing
of replacement headers and interfaces, consult the file backward_warning.h.
To disable this warning use -Wno-deprecated.
<details>
<summary><em>Migrated from <a href="https://code.icecube.wisc.edu/projects/icecube/ticket/210">https://code.icecube.wisc.edu/projects/icecube/ticket/210</a>, reported by nega</summary>
<p>
```json
{
"status": "closed",
"changetime": "2010-09-02T20:52:14",
"_ts": "1283460734000000",
"description": "{{{\n\nTo: dataclass\nSubject: [dataclass] compiling IceVer with suse 11 and gcc 4.3.2\nDate: Wed, 1 Sep 2010 10:25:50 +0200\n\nHi,\nI'm not sure if this is the right list but it can't be totally wrong.\n\nI'm doing simulation production on a cluster running suse 11 and gcc 4.3.2\nand I had some problems compiling IceVer/V03-00-03_sim which I hadn't when\nit was suse 10 and gcc 4.1.2\n\n1. cmake sets 'CURSES_NCURSES_INCLUDE_PATH:PATH=/usr/include/' but the\nncurses files are in '/usr/include/ncurses' and there are no links, so I had\nto change it in the CMakeCache.txt\n\n2. map.h could not be found. To solve this I changed '#include \"map.h\"' to\n'#include <map>' in\n'IceVer/V03-00-03_sim/src/interstring-verification/private/avgTDP/avgTDP.cxx'\nand\n'IceVer/V03-00-03_sim/src/interstring-verification/private/cmpTDP/cmpTDP.cxx'\n\n3. vector.h could not be found. Same solution as with map.h: '#include\n\"vector.h\"' --> '#include <vector>' in\n'V03-00-03_sim/src/toptiming-verification/public/toptiming-verification/reco/I3TopCombiFitParams.h'\n\nFor 2&3 I first tried adding the paths where the files are to $CPATH, but\nthis ended up in a 'includes nested to deeply' error.\n\nAfter this modifications compiling works fine and simulation doesn't throw\nany errors.\n\nNevertheless there lots of warnings about functions which will not be\nsupport in the future:\n\n/usr/include/c++/4.3/backward/backward_warning.h:33:2: warning: #warning\nThis\nfile includes at least one deprecated or antiquated header which may be\nremoved without further notice at a future date. Please use a non-\ndeprecated interface with equivalent functionality instead. For a listing\nof replacement headers and interfaces, consult the file backward_warning.h.\nTo disable this warning use -Wno-deprecated.\n\n",
"reporter": "nega",
"cc": "",
"resolution": "fixed",
"time": "2010-09-02T20:33:50",
"component": "IceVer",
"summary": "compiling IceVer with suse 11 and gcc 4.3.2",
"priority": "normal",
"keywords": "",
"milestone": "",
"owner": "",
"type": "defect"
}
```
</p>
</details>
|
defect
|
compiling icever with suse and gcc trac text to dataclass subject compiling icever with suse and gcc date wed sep hi i m not sure if this is the right list but it can t be totally wrong i m doing simulation production on a cluster running suse and gcc and i had some problems compiling icever sim which i hadn t when it was suse and gcc cmake sets curses ncurses include path path usr include but the ncurses files are in usr include ncurses and there are no links so i had to change it in the cmakecache txt map h could not be found to solve this i changed include map h to include in icever sim src interstring verification private avgtdp avgtdp cxx and icever sim src interstring verification private cmptdp cmptdp cxx vector h could not be found same solution as with map h include vector h include in sim src toptiming verification public toptiming verification reco h for i first tried adding the paths where the files are to cpath but this ended up in a includes nested to deeply error after this modifications compiling works fine and simulation doesn t throw any errors nevertheless there lots of warnings about functions which will not be support in the future usr include c backward backward warning h warning warning this file includes at least one deprecated or antiquated header which may be removed without further notice at a future date please use a non deprecated interface with equivalent functionality instead for a listing of replacement headers and interfaces consult the file backward warning h to disable this warning use wno deprecated migrated from json status closed changetime ts description n nto dataclass nsubject compiling icever with suse and gcc ndate wed sep n nhi ni m not sure if this is the right list but it can t be totally wrong n ni m doing simulation production on a cluster running suse and gcc nand i had some problems compiling icever sim which i hadn t when nit was suse and gcc n cmake sets curses ncurses include path path usr include but the nncurses files are in usr include ncurses and there are no links so i had nto change it in the cmakecache txt n map h could not be found to solve this i changed include map h to n include in n icever sim src interstring verification private avgtdp avgtdp cxx nand n icever sim src interstring verification private cmptdp cmptdp cxx n vector h could not be found same solution as with map h include n vector h include in n sim src toptiming verification public toptiming verification reco h n nfor i first tried adding the paths where the files are to cpath but nthis ended up in a includes nested to deeply error n nafter this modifications compiling works fine and simulation doesn t throw nany errors n nnevertheless there lots of warnings about functions which will not be nsupport in the future n n usr include c backward backward warning h warning warning nthis nfile includes at least one deprecated or antiquated header which may be nremoved without further notice at a future date please use a non ndeprecated interface with equivalent functionality instead for a listing nof replacement headers and interfaces consult the file backward warning h nto disable this warning use wno deprecated n n reporter nega cc resolution fixed time component icever summary compiling icever with suse and gcc priority normal keywords milestone owner type defect
| 1
|
7,988
| 2,611,071,320
|
IssuesEvent
|
2015-02-27 00:33:18
|
alistairreilly/andors-trail
|
https://api.github.com/repos/alistairreilly/andors-trail
|
opened
|
Force-close when a monster dies from an actor condition
|
auto-migrated Milestone-0.6.12 Type-Defect
|
```
Andor's Trail v0.6.12.
How to reproduce:
1. Equip a weapon that causes an actor condition on the target when attacking
(such as the barbed dagger)
2. Cause some damage to the monster, so that the monster gets the condition
3. Disengage combat (flee)
4. Wait until the monster dies from the lingering condition.
5. As soon as the monster dies, the game force-closes.
The stacktrace points to a ConcurrentModificationException on
ActorStatsController.java:251 .
Thanks to Xero from the forums for finding the bug!
http://andorstrail.com/viewtopic.php?f=3&t=2397
```
Original issue reported on code.google.com by `oskar.wi...@gmail.com` on 27 Jan 2013 at 11:35
|
1.0
|
Force-close when a monster dies from an actor condition - ```
Andor's Trail v0.6.12.
How to reproduce:
1. Equip a weapon that causes an actor condition on the target when attacking
(such as the barbed dagger)
2. Cause some damage to the monster, so that the monster gets the condition
3. Disengage combat (flee)
4. Wait until the monster dies from the lingering condition.
5. As soon as the monster dies, the game force-closes.
The stacktrace points to a ConcurrentModificationException on
ActorStatsController.java:251 .
Thanks to Xero from the forums for finding the bug!
http://andorstrail.com/viewtopic.php?f=3&t=2397
```
Original issue reported on code.google.com by `oskar.wi...@gmail.com` on 27 Jan 2013 at 11:35
|
defect
|
force close when a monster dies from an actor condition andor s trail how to reproduce equip a weapon that causes an actor condition on the target when attacking such as the barbed dagger cause some damage to the monster so that the monster gets the condition disengage combat flee wait until the monster dies from the lingering condition as soon as the monster dies the game force closes the stacktrace points to a concurrentmodificationexception on actorstatscontroller java thanks to xero from the forums for finding the bug original issue reported on code google com by oskar wi gmail com on jan at
| 1
|
213,539
| 24,008,482,542
|
IssuesEvent
|
2022-09-14 16:36:57
|
elastic/kibana
|
https://api.github.com/repos/elastic/kibana
|
closed
|
[Security Solution] Setting timeframe to "Now" under rule preview makes it red and "Refresh" button gets disabled.
|
bug impact:medium Team:Detections and Resp Team: SecuritySolution Team:Detection Alerts v8.5.0
|
**Describe the bug:**
[Security Solution] Setting timeframe to "Now" under rule preview makes it red and "Refresh" button gets disabled.
**Build Details:**
```
Version: Mains
Commit: 59ea09f9ee7df07bd75cbb64faf72793e19127e4
```
**Preconditions:**
1. Elastic search should be running.
2. Kibana should be running.
**Steps to Reproduce:**
1. Navigate to Security-->Manage-->Rules.
2. Create custom query rule.
3. Click on edit rule settings under rule details page.
4. Click on "Rule Preview" button.
5. Click on the timeframe text box.
6. From the Now tab set data and time as `now`
**Actual result:**
Timeframe values becomes red and refresh button gets disabled.
**Expected result:**
Timeframe values should not be red and refresh button should be enabled.
**Screen Records:**
https://user-images.githubusercontent.com/91867110/190131179-1d53f594-d15f-4b99-a28c-f351ddbc1c96.mp4
|
True
|
[Security Solution] Setting timeframe to "Now" under rule preview makes it red and "Refresh" button gets disabled. - **Describe the bug:**
[Security Solution] Setting timeframe to "Now" under rule preview makes it red and "Refresh" button gets disabled.
**Build Details:**
```
Version: Mains
Commit: 59ea09f9ee7df07bd75cbb64faf72793e19127e4
```
**Preconditions:**
1. Elastic search should be running.
2. Kibana should be running.
**Steps to Reproduce:**
1. Navigate to Security-->Manage-->Rules.
2. Create custom query rule.
3. Click on edit rule settings under rule details page.
4. Click on "Rule Preview" button.
5. Click on the timeframe text box.
6. From the Now tab set data and time as `now`
**Actual result:**
Timeframe values becomes red and refresh button gets disabled.
**Expected result:**
Timeframe values should not be red and refresh button should be enabled.
**Screen Records:**
https://user-images.githubusercontent.com/91867110/190131179-1d53f594-d15f-4b99-a28c-f351ddbc1c96.mp4
|
non_defect
|
setting timeframe to now under rule preview makes it red and refresh button gets disabled describe the bug setting timeframe to now under rule preview makes it red and refresh button gets disabled build details version mains commit preconditions elastic search should be running kibana should be running steps to reproduce navigate to security manage rules create custom query rule click on edit rule settings under rule details page click on rule preview button click on the timeframe text box from the now tab set data and time as now actual result timeframe values becomes red and refresh button gets disabled expected result timeframe values should not be red and refresh button should be enabled screen records
| 0
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.