Unnamed: 0
int64 0
832k
| id
float64 2.49B
32.1B
| type
stringclasses 1
value | created_at
stringlengths 19
19
| repo
stringlengths 4
112
| repo_url
stringlengths 33
141
| action
stringclasses 3
values | title
stringlengths 1
1.02k
| labels
stringlengths 4
1.54k
| body
stringlengths 1
262k
| index
stringclasses 17
values | text_combine
stringlengths 95
262k
| label
stringclasses 2
values | text
stringlengths 96
252k
| binary_label
int64 0
1
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
101,105
| 8,774,790,898
|
IssuesEvent
|
2018-12-18 20:56:45
|
cockroachdb/cockroach
|
https://api.github.com/repos/cockroachdb/cockroach
|
closed
|
roachtest: schemachange/kv failed
|
C-test-failure O-robot
|
SHA: https://github.com/cockroachdb/cockroach/commits/704e5b8e9619a5015fa4ccbd13de2e5353221ca5
Parameters:
To repro, try:
```
# Don't forget to check out a clean suitable branch and experiment with the
# stress invocation until the desired results present themselves. For example,
# using stress instead of stressrace and passing the '-p' stressflag which
# controls concurrency.
./scripts/gceworker.sh start && ./scripts/gceworker.sh mosh
cd ~/go/src/github.com/cockroachdb/cockroach && \
make stressrace TESTS=schemachange/kv PKG=roachtest TESTTIMEOUT=5m STRESSFLAGS='-maxtime 20m -timeout 10m' 2>&1 | tee /tmp/stress.log
```
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=1019281&tab=buildLog
```
The test failed on master:
test.go:645,cluster.go:1484,schemachange.go:74: pq: the batch experienced mixed success and failure
```
|
1.0
|
roachtest: schemachange/kv failed - SHA: https://github.com/cockroachdb/cockroach/commits/704e5b8e9619a5015fa4ccbd13de2e5353221ca5
Parameters:
To repro, try:
```
# Don't forget to check out a clean suitable branch and experiment with the
# stress invocation until the desired results present themselves. For example,
# using stress instead of stressrace and passing the '-p' stressflag which
# controls concurrency.
./scripts/gceworker.sh start && ./scripts/gceworker.sh mosh
cd ~/go/src/github.com/cockroachdb/cockroach && \
make stressrace TESTS=schemachange/kv PKG=roachtest TESTTIMEOUT=5m STRESSFLAGS='-maxtime 20m -timeout 10m' 2>&1 | tee /tmp/stress.log
```
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=1019281&tab=buildLog
```
The test failed on master:
test.go:645,cluster.go:1484,schemachange.go:74: pq: the batch experienced mixed success and failure
```
|
test
|
roachtest schemachange kv failed sha parameters to repro try don t forget to check out a clean suitable branch and experiment with the stress invocation until the desired results present themselves for example using stress instead of stressrace and passing the p stressflag which controls concurrency scripts gceworker sh start scripts gceworker sh mosh cd go src github com cockroachdb cockroach make stressrace tests schemachange kv pkg roachtest testtimeout stressflags maxtime timeout tee tmp stress log failed test the test failed on master test go cluster go schemachange go pq the batch experienced mixed success and failure
| 1
|
227,966
| 18,143,904,121
|
IssuesEvent
|
2021-09-25 04:26:51
|
phetsims/circuit-construction-kit-common
|
https://api.github.com/repos/phetsims/circuit-construction-kit-common
|
closed
|
CT pageNumber out of range
|
type:automated-testing
|
Seems to be in CCK DC
```
circuit-construction-kit-dc : phet-io-state-fuzz : unbuilt
https://bayes.colorado.edu/continuous-testing/ct-snapshots/1632508894542/phet-io-wrappers/state/?sim=circuit-construction-kit-dc&phetioDebug&fuzz&wrapperContinuousTest=%7B%22test%22%3A%5B%22circuit-construction-kit-dc%22%2C%22phet-io-state-fuzz%22%2C%22unbuilt%22%5D%2C%22snapshotName%22%3A%22snapshot-1632508894542%22%2C%22timestamp%22%3A1632514826987%7D
Uncaught Error: Uncaught Error: Assertion failed: pageNumber out of range: 3
Error: Assertion failed: pageNumber out of range: 3
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1632508894542/assert/js/assert.js:25:13)
at pageNumberListener (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1632508894542/sun/js/Carousel.js:270:17)
at TinyProperty.emit (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1632508894542/axon/js/TinyEmitter.js:86:9)
at Property._notifyListeners (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1632508894542/axon/js/Property.js:271:23)
at Property.set (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1632508894542/axon/js/Property.js:186:14)
at https://bayes.colorado.edu/continuous-testing/ct-snapshots/1632508894542/sun/js/Carousel.js:327:54
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1632508894542/axon/js/TinyEmitter.js:86:9)
at https://bayes.colorado.edu/continuous-testing/ct-snapshots/1632508894542/axon/js/Emitter.js:39:24
at Emitter.execute (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1632508894542/axon/js/Action.js:227:18)
at Emitter.emit (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1632508894542/axon/js/Emitter.js:64:19)
id: Bayes Chrome
Snapshot from 9/24/2021, 12:41:34 PM
```
|
1.0
|
CT pageNumber out of range - Seems to be in CCK DC
```
circuit-construction-kit-dc : phet-io-state-fuzz : unbuilt
https://bayes.colorado.edu/continuous-testing/ct-snapshots/1632508894542/phet-io-wrappers/state/?sim=circuit-construction-kit-dc&phetioDebug&fuzz&wrapperContinuousTest=%7B%22test%22%3A%5B%22circuit-construction-kit-dc%22%2C%22phet-io-state-fuzz%22%2C%22unbuilt%22%5D%2C%22snapshotName%22%3A%22snapshot-1632508894542%22%2C%22timestamp%22%3A1632514826987%7D
Uncaught Error: Uncaught Error: Assertion failed: pageNumber out of range: 3
Error: Assertion failed: pageNumber out of range: 3
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1632508894542/assert/js/assert.js:25:13)
at pageNumberListener (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1632508894542/sun/js/Carousel.js:270:17)
at TinyProperty.emit (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1632508894542/axon/js/TinyEmitter.js:86:9)
at Property._notifyListeners (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1632508894542/axon/js/Property.js:271:23)
at Property.set (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1632508894542/axon/js/Property.js:186:14)
at https://bayes.colorado.edu/continuous-testing/ct-snapshots/1632508894542/sun/js/Carousel.js:327:54
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1632508894542/axon/js/TinyEmitter.js:86:9)
at https://bayes.colorado.edu/continuous-testing/ct-snapshots/1632508894542/axon/js/Emitter.js:39:24
at Emitter.execute (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1632508894542/axon/js/Action.js:227:18)
at Emitter.emit (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1632508894542/axon/js/Emitter.js:64:19)
id: Bayes Chrome
Snapshot from 9/24/2021, 12:41:34 PM
```
|
test
|
ct pagenumber out of range seems to be in cck dc circuit construction kit dc phet io state fuzz unbuilt uncaught error uncaught error assertion failed pagenumber out of range error assertion failed pagenumber out of range at window assertions assertfunction at pagenumberlistener at tinyproperty emit at property notifylisteners at property set at at tinyemitter emit at at emitter execute at emitter emit id bayes chrome snapshot from pm
| 1
|
346,494
| 30,922,829,668
|
IssuesEvent
|
2023-08-06 05:27:32
|
cockroachdb/cockroach
|
https://api.github.com/repos/cockroachdb/cockroach
|
opened
|
sql/tests: TestRandomSyntaxGeneration failed
|
C-test-failure O-robot T-sql-foundations branch-release-23.1
|
sql/tests.TestRandomSyntaxGeneration [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RandomSyntaxTestsBazel/11207278?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RandomSyntaxTestsBazel/11207278?buildTab=artifacts#/) on release-23.1 @ [aad4fd4312460e6689f543eaff85b1bca8cebf91](https://github.com/cockroachdb/cockroach/commits/aad4fd4312460e6689f543eaff85b1bca8cebf91):
```
rsg_test.go:832: 1m15s of 5m0s: 182317 executions, 10418 successful
rsg_test.go:832: 1m20s of 5m0s: 193283 executions, 10937 successful
rsg_test.go:832: 1m25s of 5m0s: 205815 executions, 11536 successful
rsg_test.go:832: 1m30s of 5m0s: 217091 executions, 12088 successful
rsg_test.go:832: 1m35s of 5m0s: 229092 executions, 12685 successful
rsg_test.go:832: 1m40s of 5m0s: 239923 executions, 13282 successful
rsg_test.go:832: 1m45s of 5m0s: 252291 executions, 13893 successful
rsg_test.go:832: 1m50s of 5m0s: 263515 executions, 14462 successful
rsg_test.go:832: 1m55s of 5m0s: 275985 executions, 15098 successful
rsg_test.go:832: 2m0s of 5m0s: 287831 executions, 15690 successful
rsg_test.go:832: 2m5s of 5m0s: 300975 executions, 16276 successful
rsg_test.go:832: 2m10s of 5m0s: 314293 executions, 16913 successful
rsg_test.go:832: 2m15s of 5m0s: 327093 executions, 17484 successful
rsg_test.go:832: 2m20s of 5m0s: 339063 executions, 18048 successful
rsg_test.go:832: 2m25s of 5m0s: 351331 executions, 18626 successful
rsg_test.go:832: 2m30s of 5m0s: 363619 executions, 19180 successful
rsg_test.go:832: 2m35s of 5m0s: 375824 executions, 19786 successful
rsg_test.go:832: 2m40s of 5m0s: 387814 executions, 20359 successful
rsg_test.go:832: 2m45s of 5m0s: 400166 executions, 20938 successful
rsg_test.go:832: 2m50s of 5m0s: 412899 executions, 21524 successful
rsg_test.go:832: 2m55s of 5m0s: 424610 executions, 22093 successful
rsg_test.go:832: 3m0s of 5m0s: 436781 executions, 22693 successful
rsg_test.go:832: 3m5s of 5m0s: 448720 executions, 23244 successful
rsg_test.go:832: 3m10s of 5m0s: 461336 executions, 23819 successful
rsg_test.go:832: 3m15s of 5m0s: 473277 executions, 24380 successful
rsg_test.go:832: 3m20s of 5m0s: 485527 executions, 24972 successful
rsg_test.go:832: 3m25s of 5m0s: 497939 executions, 25576 successful
rsg_test.go:832: 3m30s of 5m0s: 509100 executions, 26096 successful
rsg_test.go:832: 3m35s of 5m0s: 521123 executions, 26666 successful
rsg_test.go:832: 3m40s of 5m0s: 532867 executions, 27199 successful
rsg_test.go:832: 3m45s of 5m0s: 545023 executions, 27754 successful
rsg_test.go:832: 3m50s of 5m0s: 557377 executions, 28322 successful
rsg_test.go:832: 3m55s of 5m0s: 570801 executions, 28921 successful
rsg_test.go:832: 4m0s of 5m0s: 583600 executions, 29512 successful
rsg_test.go:832: 4m5s of 5m0s: 595986 executions, 30084 successful
rsg_test.go:832: 4m10s of 5m0s: 608388 executions, 30648 successful
rsg_test.go:832: 4m15s of 5m0s: 620520 executions, 31229 successful
rsg_test.go:832: 4m20s of 5m0s: 631992 executions, 31770 successful
rsg_test.go:832: 4m25s of 5m0s: 643802 executions, 32350 successful
rsg_test.go:832: 4m30s of 5m0s: 655154 executions, 32881 successful
rsg_test.go:832: 4m35s of 5m0s: 667726 executions, 33492 successful
rsg_test.go:832: 4m40s of 5m0s: 679127 executions, 34012 successful
rsg_test.go:832: 4m45s of 5m0s: 691498 executions, 34614 successful
rsg_test.go:832: 4m50s of 5m0s: 704176 executions, 35164 successful
rsg_test.go:832: 4m55s of 5m0s: 716561 executions, 35729 successful
rsg_test.go:868: 728465 executions, 36278 successful
rsg_test.go:876: cannot parse output of Format: sql="CREATE CHANGEFEED FOR SURVIVE . ident . FAMILY , ISERROR INTO PLACEHOLDER WITH OPTIONS ( BUCKET_COUNT )", formattedSQL="CREATE CHANGEFEED FOR TABLE survive.ident.family, TABLE \"iserror\" INTO 'placeholder' WITH bucket_count": at or near "with": syntax error
rsg_test.go:304: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/d437d2c847dfedbc4972f231c3331c8e/logTestRandomSyntaxGeneration437488720
--- FAIL: TestRandomSyntaxGeneration (301.98s)
```
<details><summary>Help</summary>
<p>
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
</p>
</details>
<details><summary>Same failure on other branches</summary>
<p>
- #108233 sql/tests: TestRandomSyntaxGeneration failed [C-test-failure O-robot T-sql-foundations branch-release-22.2]
- #108083 sql/tests: TestRandomSyntaxGeneration failed [index visibility precision] [C-test-failure O-robot T-sql-foundations X-noreuse branch-master]
</p>
</details>
/cc @cockroachdb/sql-foundations
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestRandomSyntaxGeneration.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
|
1.0
|
sql/tests: TestRandomSyntaxGeneration failed - sql/tests.TestRandomSyntaxGeneration [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RandomSyntaxTestsBazel/11207278?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RandomSyntaxTestsBazel/11207278?buildTab=artifacts#/) on release-23.1 @ [aad4fd4312460e6689f543eaff85b1bca8cebf91](https://github.com/cockroachdb/cockroach/commits/aad4fd4312460e6689f543eaff85b1bca8cebf91):
```
rsg_test.go:832: 1m15s of 5m0s: 182317 executions, 10418 successful
rsg_test.go:832: 1m20s of 5m0s: 193283 executions, 10937 successful
rsg_test.go:832: 1m25s of 5m0s: 205815 executions, 11536 successful
rsg_test.go:832: 1m30s of 5m0s: 217091 executions, 12088 successful
rsg_test.go:832: 1m35s of 5m0s: 229092 executions, 12685 successful
rsg_test.go:832: 1m40s of 5m0s: 239923 executions, 13282 successful
rsg_test.go:832: 1m45s of 5m0s: 252291 executions, 13893 successful
rsg_test.go:832: 1m50s of 5m0s: 263515 executions, 14462 successful
rsg_test.go:832: 1m55s of 5m0s: 275985 executions, 15098 successful
rsg_test.go:832: 2m0s of 5m0s: 287831 executions, 15690 successful
rsg_test.go:832: 2m5s of 5m0s: 300975 executions, 16276 successful
rsg_test.go:832: 2m10s of 5m0s: 314293 executions, 16913 successful
rsg_test.go:832: 2m15s of 5m0s: 327093 executions, 17484 successful
rsg_test.go:832: 2m20s of 5m0s: 339063 executions, 18048 successful
rsg_test.go:832: 2m25s of 5m0s: 351331 executions, 18626 successful
rsg_test.go:832: 2m30s of 5m0s: 363619 executions, 19180 successful
rsg_test.go:832: 2m35s of 5m0s: 375824 executions, 19786 successful
rsg_test.go:832: 2m40s of 5m0s: 387814 executions, 20359 successful
rsg_test.go:832: 2m45s of 5m0s: 400166 executions, 20938 successful
rsg_test.go:832: 2m50s of 5m0s: 412899 executions, 21524 successful
rsg_test.go:832: 2m55s of 5m0s: 424610 executions, 22093 successful
rsg_test.go:832: 3m0s of 5m0s: 436781 executions, 22693 successful
rsg_test.go:832: 3m5s of 5m0s: 448720 executions, 23244 successful
rsg_test.go:832: 3m10s of 5m0s: 461336 executions, 23819 successful
rsg_test.go:832: 3m15s of 5m0s: 473277 executions, 24380 successful
rsg_test.go:832: 3m20s of 5m0s: 485527 executions, 24972 successful
rsg_test.go:832: 3m25s of 5m0s: 497939 executions, 25576 successful
rsg_test.go:832: 3m30s of 5m0s: 509100 executions, 26096 successful
rsg_test.go:832: 3m35s of 5m0s: 521123 executions, 26666 successful
rsg_test.go:832: 3m40s of 5m0s: 532867 executions, 27199 successful
rsg_test.go:832: 3m45s of 5m0s: 545023 executions, 27754 successful
rsg_test.go:832: 3m50s of 5m0s: 557377 executions, 28322 successful
rsg_test.go:832: 3m55s of 5m0s: 570801 executions, 28921 successful
rsg_test.go:832: 4m0s of 5m0s: 583600 executions, 29512 successful
rsg_test.go:832: 4m5s of 5m0s: 595986 executions, 30084 successful
rsg_test.go:832: 4m10s of 5m0s: 608388 executions, 30648 successful
rsg_test.go:832: 4m15s of 5m0s: 620520 executions, 31229 successful
rsg_test.go:832: 4m20s of 5m0s: 631992 executions, 31770 successful
rsg_test.go:832: 4m25s of 5m0s: 643802 executions, 32350 successful
rsg_test.go:832: 4m30s of 5m0s: 655154 executions, 32881 successful
rsg_test.go:832: 4m35s of 5m0s: 667726 executions, 33492 successful
rsg_test.go:832: 4m40s of 5m0s: 679127 executions, 34012 successful
rsg_test.go:832: 4m45s of 5m0s: 691498 executions, 34614 successful
rsg_test.go:832: 4m50s of 5m0s: 704176 executions, 35164 successful
rsg_test.go:832: 4m55s of 5m0s: 716561 executions, 35729 successful
rsg_test.go:868: 728465 executions, 36278 successful
rsg_test.go:876: cannot parse output of Format: sql="CREATE CHANGEFEED FOR SURVIVE . ident . FAMILY , ISERROR INTO PLACEHOLDER WITH OPTIONS ( BUCKET_COUNT )", formattedSQL="CREATE CHANGEFEED FOR TABLE survive.ident.family, TABLE \"iserror\" INTO 'placeholder' WITH bucket_count": at or near "with": syntax error
rsg_test.go:304: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/d437d2c847dfedbc4972f231c3331c8e/logTestRandomSyntaxGeneration437488720
--- FAIL: TestRandomSyntaxGeneration (301.98s)
```
<details><summary>Help</summary>
<p>
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
</p>
</details>
<details><summary>Same failure on other branches</summary>
<p>
- #108233 sql/tests: TestRandomSyntaxGeneration failed [C-test-failure O-robot T-sql-foundations branch-release-22.2]
- #108083 sql/tests: TestRandomSyntaxGeneration failed [index visibility precision] [C-test-failure O-robot T-sql-foundations X-noreuse branch-master]
</p>
</details>
/cc @cockroachdb/sql-foundations
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestRandomSyntaxGeneration.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
|
test
|
sql tests testrandomsyntaxgeneration failed sql tests testrandomsyntaxgeneration with on release rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go of executions successful rsg test go executions successful rsg test go cannot parse output of format sql create changefeed for survive ident family iserror into placeholder with options bucket count formattedsql create changefeed for table survive ident family table iserror into placeholder with bucket count at or near with syntax error rsg test go test log scope end test logs left over in artifacts tmp tmp fail testrandomsyntaxgeneration help see also same failure on other branches sql tests testrandomsyntaxgeneration failed sql tests testrandomsyntaxgeneration failed cc cockroachdb sql foundations
| 1
|
8,042
| 2,956,487,781
|
IssuesEvent
|
2015-07-08 11:38:35
|
stefan-kolb/paas-profiles
|
https://api.github.com/repos/stefan-kolb/paas-profiles
|
closed
|
Check tests and try to remove distracting Mongoid warnings
|
bug test
|
ruby -W0 -Ispec spec/models/event_spec.rb
|
1.0
|
Check tests and try to remove distracting Mongoid warnings - ruby -W0 -Ispec spec/models/event_spec.rb
|
test
|
check tests and try to remove distracting mongoid warnings ruby ispec spec models event spec rb
| 1
|
598,738
| 18,251,024,283
|
IssuesEvent
|
2021-10-02 07:46:18
|
Ghost-chu/QuickShop-Reremake
|
https://api.github.com/repos/Ghost-chu/QuickShop-Reremake
|
closed
|
Setting tax account per shop
|
Enhancement Priority：Minor Should Implement By Addon
|
**Describe the Feature**
It would be nice to be able to set the tax account per each shop, not only on global level. My players want money to go to their faction account instead of a global server account. I would like to give them the possibility to gain tax from shops created on their land.
Could you please add such a feature?
|
1.0
|
Setting tax account per shop - **Describe the Feature**
It would be nice to be able to set the tax account per each shop, not only on global level. My players want money to go to their faction account instead of a global server account. I would like to give them the possibility to gain tax from shops created on their land.
Could you please add such a feature?
|
non_test
|
setting tax account per shop describe the feature it would be nice to be able to set the tax account per each shop not only on global level my players want money to go to their faction account instead of a global server account i would like to give them the possibility to gain tax from shops created on their land could you please add such a feature
| 0
|
214,980
| 7,285,299,513
|
IssuesEvent
|
2018-02-23 03:12:39
|
kcigeospatial/balt_co_ETL
|
https://api.github.com/repos/kcigeospatial/balt_co_ETL
|
closed
|
Stormwater - Selection Set 1A - migrated records also show up in append_failure
|
high priority item
|
See ETL output file: \\vm-wsscmta\export\MDE_2018_01_29_15_56.zip
The BMP table contains 710 records. All 710 records are also found in the Append_Failure_BMP_p_to_BMP table. If I understand correctly, records should be in one or the other, but not both.
Note that the 710 records are not quite correct in terms of the selection set, but keeping that issue separate and unique for now.
|
1.0
|
Stormwater - Selection Set 1A - migrated records also show up in append_failure - See ETL output file: \\vm-wsscmta\export\MDE_2018_01_29_15_56.zip
The BMP table contains 710 records. All 710 records are also found in the Append_Failure_BMP_p_to_BMP table. If I understand correctly, records should be in one or the other, but not both.
Note that the 710 records are not quite correct in terms of the selection set, but keeping that issue separate and unique for now.
|
non_test
|
stormwater selection set migrated records also show up in append failure see etl output file vm wsscmta export mde zip the bmp table contains records all records are also found in the append failure bmp p to bmp table if i understand correctly records should be in one or the other but not both note that the records are not quite correct in terms of the selection set but keeping that issue separate and unique for now
| 0
|
214,363
| 24,069,539,751
|
IssuesEvent
|
2022-09-18 01:02:08
|
Gal-Doron/operator-registry
|
https://api.github.com/repos/Gal-Doron/operator-registry
|
closed
|
CVE-2022-21698 (High) detected in multiple libraries - autoclosed
|
security vulnerability
|
## CVE-2022-21698 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>github.com/docker/cli-v20.10.12</b>, <b>github.com/docker/distribution-v2.8.0-beta.1</b>, <b>github.com/containerd/containerd-v1.4.11</b>, <b>github.com/prometheus/client_golang-v1.11.0</b>, <b>github.com/operator-framework/api-v0.12.0</b>, <b>github.com/docker/docker-v20.10.16</b></p></summary>
<p>
<details><summary><b>github.com/docker/cli-v20.10.12</b></p></summary>
<p>The Docker CLI</p>
<p>
Dependency Hierarchy:
- :x: **github.com/docker/cli-v20.10.12** (Vulnerable Library)
</details>
<details><summary><b>github.com/docker/distribution-v2.8.0-beta.1</b></p></summary>
<p>The toolkit to pack, ship, store, and deliver container content</p>
<p>
Dependency Hierarchy:
- :x: **github.com/docker/distribution-v2.8.0-beta.1** (Vulnerable Library)
</details>
<details><summary><b>github.com/containerd/containerd-v1.4.11</b></p></summary>
<p>An open and reliable container runtime</p>
<p>
Dependency Hierarchy:
- :x: **github.com/containerd/containerd-v1.4.11** (Vulnerable Library)
</details>
<details><summary><b>github.com/prometheus/client_golang-v1.11.0</b></p></summary>
<p>Prometheus instrumentation library for Go applications</p>
<p>
Dependency Hierarchy:
- github.com/docker/distribution-v2.8.0-beta.1 (Root Library)
- github.com/docker/go-metrics-v0.0.1
- :x: **github.com/prometheus/client_golang-v1.11.0** (Vulnerable Library)
</details>
<details><summary><b>github.com/operator-framework/api-v0.12.0</b></p></summary>
<p>Contains the API definitions used by OLM and Marketplace</p>
<p>
Dependency Hierarchy:
- :x: **github.com/operator-framework/api-v0.12.0** (Vulnerable Library)
</details>
<details><summary><b>github.com/docker/docker-v20.10.16</b></p></summary>
<p>Moby Project - a collaborative project for the container ecosystem to assemble container-based systems</p>
<p>
Dependency Hierarchy:
- :x: **github.com/docker/docker-v20.10.16** (Vulnerable Library)
</details>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
client_golang is the instrumentation library for Go applications in Prometheus, and the promhttp package in client_golang provides tooling around HTTP servers and clients. In client_golang prior to version 1.11.1, HTTP server is susceptible to a Denial of Service through unbounded cardinality, and potential memory exhaustion, when handling requests with non-standard HTTP methods. In order to be affected, an instrumented software must use any of `promhttp.InstrumentHandler*` middleware except `RequestsInFlight`; not filter any specific methods (e.g GET) before middleware; pass metric with `method` label name to our middleware; and not have any firewall/LB/proxy that filters away requests with unknown `method`. client_golang version 1.11.1 contains a patch for this issue. Several workarounds are available, including removing the `method` label name from counter/gauge used in the InstrumentHandler; turning off affected promhttp handlers; adding custom middleware before promhttp handler that will sanitize the request method given by Go http.Request; and using a reverse proxy or web application firewall, configured to only allow a limited set of methods.
<p>Publish Date: 2022-02-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-21698>CVE-2022-21698</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/prometheus/client_golang/security/advisories/GHSA-cg3q-j54f-5p7p">https://github.com/prometheus/client_golang/security/advisories/GHSA-cg3q-j54f-5p7p</a></p>
<p>Release Date: 2022-02-15</p>
<p>Fix Resolution: v1.11.1</p>
</p>
</details>
<p></p>
|
True
|
CVE-2022-21698 (High) detected in multiple libraries - autoclosed - ## CVE-2022-21698 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>github.com/docker/cli-v20.10.12</b>, <b>github.com/docker/distribution-v2.8.0-beta.1</b>, <b>github.com/containerd/containerd-v1.4.11</b>, <b>github.com/prometheus/client_golang-v1.11.0</b>, <b>github.com/operator-framework/api-v0.12.0</b>, <b>github.com/docker/docker-v20.10.16</b></p></summary>
<p>
<details><summary><b>github.com/docker/cli-v20.10.12</b></p></summary>
<p>The Docker CLI</p>
<p>
Dependency Hierarchy:
- :x: **github.com/docker/cli-v20.10.12** (Vulnerable Library)
</details>
<details><summary><b>github.com/docker/distribution-v2.8.0-beta.1</b></p></summary>
<p>The toolkit to pack, ship, store, and deliver container content</p>
<p>
Dependency Hierarchy:
- :x: **github.com/docker/distribution-v2.8.0-beta.1** (Vulnerable Library)
</details>
<details><summary><b>github.com/containerd/containerd-v1.4.11</b></p></summary>
<p>An open and reliable container runtime</p>
<p>
Dependency Hierarchy:
- :x: **github.com/containerd/containerd-v1.4.11** (Vulnerable Library)
</details>
<details><summary><b>github.com/prometheus/client_golang-v1.11.0</b></p></summary>
<p>Prometheus instrumentation library for Go applications</p>
<p>
Dependency Hierarchy:
- github.com/docker/distribution-v2.8.0-beta.1 (Root Library)
- github.com/docker/go-metrics-v0.0.1
- :x: **github.com/prometheus/client_golang-v1.11.0** (Vulnerable Library)
</details>
<details><summary><b>github.com/operator-framework/api-v0.12.0</b></p></summary>
<p>Contains the API definitions used by OLM and Marketplace</p>
<p>
Dependency Hierarchy:
- :x: **github.com/operator-framework/api-v0.12.0** (Vulnerable Library)
</details>
<details><summary><b>github.com/docker/docker-v20.10.16</b></p></summary>
<p>Moby Project - a collaborative project for the container ecosystem to assemble container-based systems</p>
<p>
Dependency Hierarchy:
- :x: **github.com/docker/docker-v20.10.16** (Vulnerable Library)
</details>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
client_golang is the instrumentation library for Go applications in Prometheus, and the promhttp package in client_golang provides tooling around HTTP servers and clients. In client_golang prior to version 1.11.1, HTTP server is susceptible to a Denial of Service through unbounded cardinality, and potential memory exhaustion, when handling requests with non-standard HTTP methods. In order to be affected, an instrumented software must use any of `promhttp.InstrumentHandler*` middleware except `RequestsInFlight`; not filter any specific methods (e.g GET) before middleware; pass metric with `method` label name to our middleware; and not have any firewall/LB/proxy that filters away requests with unknown `method`. client_golang version 1.11.1 contains a patch for this issue. Several workarounds are available, including removing the `method` label name from counter/gauge used in the InstrumentHandler; turning off affected promhttp handlers; adding custom middleware before promhttp handler that will sanitize the request method given by Go http.Request; and using a reverse proxy or web application firewall, configured to only allow a limited set of methods.
<p>Publish Date: 2022-02-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-21698>CVE-2022-21698</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/prometheus/client_golang/security/advisories/GHSA-cg3q-j54f-5p7p">https://github.com/prometheus/client_golang/security/advisories/GHSA-cg3q-j54f-5p7p</a></p>
<p>Release Date: 2022-02-15</p>
<p>Fix Resolution: v1.11.1</p>
</p>
</details>
<p></p>
|
non_test
|
cve high detected in multiple libraries autoclosed cve high severity vulnerability vulnerable libraries github com docker cli github com docker distribution beta github com containerd containerd github com prometheus client golang github com operator framework api github com docker docker github com docker cli the docker cli dependency hierarchy x github com docker cli vulnerable library github com docker distribution beta the toolkit to pack ship store and deliver container content dependency hierarchy x github com docker distribution beta vulnerable library github com containerd containerd an open and reliable container runtime dependency hierarchy x github com containerd containerd vulnerable library github com prometheus client golang prometheus instrumentation library for go applications dependency hierarchy github com docker distribution beta root library github com docker go metrics x github com prometheus client golang vulnerable library github com operator framework api contains the api definitions used by olm and marketplace dependency hierarchy x github com operator framework api vulnerable library github com docker docker moby project a collaborative project for the container ecosystem to assemble container based systems dependency hierarchy x github com docker docker vulnerable library found in base branch master vulnerability details client golang is the instrumentation library for go applications in prometheus and the promhttp package in client golang provides tooling around http servers and clients in client golang prior to version http server is susceptible to a denial of service through unbounded cardinality and potential memory exhaustion when handling requests with non standard http methods in order to be affected an instrumented software must use any of promhttp instrumenthandler middleware except requestsinflight not filter any specific methods e g get before middleware pass metric with method label name to our middleware and not have any firewall lb proxy that filters away requests with unknown method client golang version contains a patch for this issue several workarounds are available including removing the method label name from counter gauge used in the instrumenthandler turning off affected promhttp handlers adding custom middleware before promhttp handler that will sanitize the request method given by go http request and using a reverse proxy or web application firewall configured to only allow a limited set of methods 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
| 0
|
218,733
| 17,018,366,409
|
IssuesEvent
|
2021-07-02 15:02:58
|
ProfessorAmanda/econsimulations
|
https://api.github.com/repos/ProfessorAmanda/econsimulations
|
opened
|
Standardize button for Hypothesis Testing graph
|
Hypothesis Testing enhancement
|
It'd be great to have a "standardize" button for the right-hand-side simulation graph, to cover values of x_bar to z/t scores. That would be especially helpful in the case of t, as we discussed.
|
1.0
|
Standardize button for Hypothesis Testing graph - It'd be great to have a "standardize" button for the right-hand-side simulation graph, to cover values of x_bar to z/t scores. That would be especially helpful in the case of t, as we discussed.
|
test
|
standardize button for hypothesis testing graph it d be great to have a standardize button for the right hand side simulation graph to cover values of x bar to z t scores that would be especially helpful in the case of t as we discussed
| 1
|
375,450
| 11,104,670,008
|
IssuesEvent
|
2019-12-17 08:10:55
|
wso2/ballerina-message-broker
|
https://api.github.com/repos/wso2/ballerina-message-broker
|
closed
|
Support for SCIM to integrate with SCIM compatible IDP
|
Complexity/Moderate Module/broker-auth Priority/Highest Severity/Critical Type/New Feature
|
**Description:**
<!-- Give a brief description of the issue -->
References:
https://docs.wso2.com/display/IS530/SCIM+1.1+APIs
|
1.0
|
Support for SCIM to integrate with SCIM compatible IDP - **Description:**
<!-- Give a brief description of the issue -->
References:
https://docs.wso2.com/display/IS530/SCIM+1.1+APIs
|
non_test
|
support for scim to integrate with scim compatible idp description references
| 0
|
294,033
| 9,012,398,338
|
IssuesEvent
|
2019-02-05 16:47:55
|
StrangeLoopGames/EcoIssues
|
https://api.github.com/repos/StrangeLoopGames/EcoIssues
|
closed
|
0.8 Treasury issues.
|
D3nnis3n's List Fixed High Priority Quality Assurance
|
1) tax and allocate not work (but show message in chat)
2) both actions (tax\allocate) show as tax.
3) "taxed everyone" show everytime (even if no person to tax\allocate selected)
4) no button to show all money (e.g. for taxing)
5) "dump" require confirmation before execute.
6) Need to add "No currency in treasury" information to Treasury UI
|
1.0
|
0.8 Treasury issues. - 1) tax and allocate not work (but show message in chat)
2) both actions (tax\allocate) show as tax.
3) "taxed everyone" show everytime (even if no person to tax\allocate selected)
4) no button to show all money (e.g. for taxing)
5) "dump" require confirmation before execute.
6) Need to add "No currency in treasury" information to Treasury UI
|
non_test
|
treasury issues tax and allocate not work but show message in chat both actions tax allocate show as tax taxed everyone show everytime even if no person to tax allocate selected no button to show all money e g for taxing dump require confirmation before execute need to add no currency in treasury information to treasury ui
| 0
|
266,950
| 23,269,607,058
|
IssuesEvent
|
2022-08-04 21:10:39
|
vectordotdev/vector
|
https://api.github.com/repos/vectordotdev/vector
|
closed
|
Flakey test `test_buffering` on Windows
|
domain: tests
|
Failure: https://github.com/timberio/vector/pull/4437/checks?check_run_id=1222218702
```
failures:
---- test_buffering stdout ----
thread 'main' panicked at 'assertion failed: `(left == right)`
left: `20`,
right: `10`', tests\buffering.rs:132:9
stack backtrace:
0: 0x7ff788c9d56f - backtrace::backtrace::trace_unsynchronized
at C:\Users\VssAdministrator\.cargo\registry\src\github.com-1ecc6299db9ec823\backtrace-0.3.46\src\backtrace\mod.rs:66
1: 0x7ff788c9d56f - std::sys_common::backtrace::_print_fmt
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libstd\sys_common\backtrace.rs:78
2: 0x7ff788c9d56f - std::sys_common::backtrace::_print::{{impl}}::fmt
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libstd\sys_common\backtrace.rs:59
3: 0x7ff788cbf55b - core::fmt::write
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libcore\fmt\mod.rs:1069
4: 0x7ff78510a89c - std::io::Write::write_fmt<test::helpers::sink::Sink>
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\src\libstd\io\mod.rs:1504
5: 0x7ff788c8f288 - std::io::impls::{{impl}}::write_fmt<Write>
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libstd\io\impls.rs:156
6: 0x7ff788ca0b1c - std::sys_common::backtrace::_print
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libstd\sys_common\backtrace.rs:62
7: 0x7ff788ca0b1c - std::sys_common::backtrace::print
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libstd\sys_common\backtrace.rs:49
8: 0x7ff788ca0b1c - std::panicking::default_hook::{{closure}}
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libstd\panicking.rs:198
9: 0x7ff788ca06fe - std::panicking::default_hook
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libstd\panicking.rs:215
10: 0x7ff788ca1307 - std::panicking::rust_panic_with_hook
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libstd\panicking.rs:511
11: 0x7ff788ca0e8f - std::panicking::begin_panic_handler
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libstd\panicking.rs:419
12: 0x7ff788ca0dfc - std::panicking::begin_panic_fmt
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libtest\lib.rs:475
38: 0x7ff7851365b6 - test::run_test
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libtest\lib.rs:505
39: 0x7ff785120a27 - test::run_tests
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libtest\lib.rs:284
40: 0x7ff785120a27 - test::console::run_tests_console
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libtest\console.rs:280
41: 0x7ff785132001 - test::test_main
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libtest\lib.rs:120
42: 0x7ff785133992 - test::test_main_static
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libtest\lib.rs:139
43: 0x7ff7850d5458 - buffering::test_buffering
44: 0x7ff7850e18db - std::rt::lang_start::{{closure}}<()>
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\src\libstd\rt.rs:67
45: 0x7ff788ca162a - std::rt::lang_start_internal::{{closure}}
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libstd\rt.rs:52
46: 0x7ff788ca162a - std::panicking::try::do_call
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libstd\panicking.rs:331
47: 0x7ff788ca162a - std::panicking::try
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libstd\panicking.rs:274
48: 0x7ff788ca162a - std::panic::catch_unwind
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libstd\panic.rs:394
49: 0x7ff788ca162a - std::rt::lang_start_internal
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libstd\rt.rs:51
50: 0x7ff7850e18b3 - std::rt::lang_start<()>
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\src\libstd\rt.rs:67
51: 0x7ff7850d5480 - main
52: 0x7ff788ea52c4 - invoke_main
at D:\agent\_work\9\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:78
53: 0x7ff788ea52c4 - __scrt_common_main_seh
at D:\agent\_work\9\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:288
54: 0x7ffa62fd7974 - BaseThreadInitThunk
55: 0x7ffa656aa271 - RtlUserThreadStart
failures:
test_buffering
```
|
1.0
|
Flakey test `test_buffering` on Windows - Failure: https://github.com/timberio/vector/pull/4437/checks?check_run_id=1222218702
```
failures:
---- test_buffering stdout ----
thread 'main' panicked at 'assertion failed: `(left == right)`
left: `20`,
right: `10`', tests\buffering.rs:132:9
stack backtrace:
0: 0x7ff788c9d56f - backtrace::backtrace::trace_unsynchronized
at C:\Users\VssAdministrator\.cargo\registry\src\github.com-1ecc6299db9ec823\backtrace-0.3.46\src\backtrace\mod.rs:66
1: 0x7ff788c9d56f - std::sys_common::backtrace::_print_fmt
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libstd\sys_common\backtrace.rs:78
2: 0x7ff788c9d56f - std::sys_common::backtrace::_print::{{impl}}::fmt
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libstd\sys_common\backtrace.rs:59
3: 0x7ff788cbf55b - core::fmt::write
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libcore\fmt\mod.rs:1069
4: 0x7ff78510a89c - std::io::Write::write_fmt<test::helpers::sink::Sink>
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\src\libstd\io\mod.rs:1504
5: 0x7ff788c8f288 - std::io::impls::{{impl}}::write_fmt<Write>
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libstd\io\impls.rs:156
6: 0x7ff788ca0b1c - std::sys_common::backtrace::_print
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libstd\sys_common\backtrace.rs:62
7: 0x7ff788ca0b1c - std::sys_common::backtrace::print
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libstd\sys_common\backtrace.rs:49
8: 0x7ff788ca0b1c - std::panicking::default_hook::{{closure}}
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libstd\panicking.rs:198
9: 0x7ff788ca06fe - std::panicking::default_hook
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libstd\panicking.rs:215
10: 0x7ff788ca1307 - std::panicking::rust_panic_with_hook
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libstd\panicking.rs:511
11: 0x7ff788ca0e8f - std::panicking::begin_panic_handler
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libstd\panicking.rs:419
12: 0x7ff788ca0dfc - std::panicking::begin_panic_fmt
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libtest\lib.rs:475
38: 0x7ff7851365b6 - test::run_test
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libtest\lib.rs:505
39: 0x7ff785120a27 - test::run_tests
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libtest\lib.rs:284
40: 0x7ff785120a27 - test::console::run_tests_console
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libtest\console.rs:280
41: 0x7ff785132001 - test::test_main
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libtest\lib.rs:120
42: 0x7ff785133992 - test::test_main_static
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libtest\lib.rs:139
43: 0x7ff7850d5458 - buffering::test_buffering
44: 0x7ff7850e18db - std::rt::lang_start::{{closure}}<()>
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\src\libstd\rt.rs:67
45: 0x7ff788ca162a - std::rt::lang_start_internal::{{closure}}
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libstd\rt.rs:52
46: 0x7ff788ca162a - std::panicking::try::do_call
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libstd\panicking.rs:331
47: 0x7ff788ca162a - std::panicking::try
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libstd\panicking.rs:274
48: 0x7ff788ca162a - std::panic::catch_unwind
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libstd\panic.rs:394
49: 0x7ff788ca162a - std::rt::lang_start_internal
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\/src\libstd\rt.rs:51
50: 0x7ff7850e18b3 - std::rt::lang_start<()>
at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4\src\libstd\rt.rs:67
51: 0x7ff7850d5480 - main
52: 0x7ff788ea52c4 - invoke_main
at D:\agent\_work\9\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:78
53: 0x7ff788ea52c4 - __scrt_common_main_seh
at D:\agent\_work\9\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:288
54: 0x7ffa62fd7974 - BaseThreadInitThunk
55: 0x7ffa656aa271 - RtlUserThreadStart
failures:
test_buffering
```
|
test
|
flakey test test buffering on windows failure failures test buffering stdout thread main panicked at assertion failed left right left right tests buffering rs stack backtrace backtrace backtrace trace unsynchronized at c users vssadministrator cargo registry src github com backtrace src backtrace mod rs std sys common backtrace print fmt at rustc src libstd sys common backtrace rs std sys common backtrace print impl fmt at rustc src libstd sys common backtrace rs core fmt write at rustc src libcore fmt mod rs std io write write fmt at rustc src libstd io mod rs std io impls impl write fmt at rustc src libstd io impls rs std sys common backtrace print at rustc src libstd sys common backtrace rs std sys common backtrace print at rustc src libstd sys common backtrace rs std panicking default hook closure at rustc src libstd panicking rs std panicking default hook at rustc src libstd panicking rs std panicking rust panic with hook at rustc src libstd panicking rs std panicking begin panic handler at rustc src libstd panicking rs std panicking begin panic fmt at rustc src libtest lib rs test run test at rustc src libtest lib rs test run tests at rustc src libtest lib rs test console run tests console at rustc src libtest console rs test test main at rustc src libtest lib rs test test main static at rustc src libtest lib rs buffering test buffering std rt lang start closure at rustc src libstd rt rs std rt lang start internal closure at rustc src libstd rt rs std panicking try do call at rustc src libstd panicking rs std panicking try at rustc src libstd panicking rs std panic catch unwind at rustc src libstd panic rs std rt lang start internal at rustc src libstd rt rs std rt lang start at rustc src libstd rt rs main invoke main at d agent work s src vctools crt vcstartup src startup exe common inl scrt common main seh at d agent work s src vctools crt vcstartup src startup exe common inl basethreadinitthunk rtluserthreadstart failures test buffering
| 1
|
229,847
| 18,444,184,851
|
IssuesEvent
|
2021-10-14 22:19:42
|
hashgraph/hedera-services
|
https://api.github.com/repos/hashgraph/hedera-services
|
closed
|
EET testClient does not aggregate token transfers properly.
|
Test Development bug
|
### Description
When we perform an operation like this :
```
cryptoTransfer(
moving(10, token).between(TOKEN_TREASURY, thirdUser),
moving(20, token).between(TOKEN_TREASURY, firstUser)
)
```
EET produces the following transfer list:
```
tokenTransfers=0.0.1022([0.0.1018 -> -10, 0.0.1021 <- +10, 0.0.1018 -> -20, 0.0.1019 <- +20])([])}
```
This results in `ACCOUNT_REPEATED_IN_ACCOUNT_AMOUNTS` response from the nodes.
### Steps to reproduce
Perform a test that does a crypto transfer similar to
```
cryptoTransfer(
moving(10, token).between(TOKEN_TREASURY, thirdUser),
moving(20, token).between(TOKEN_TREASURY, firstUser)
)
```
### Additional context
_No response_
### Hedera network
other
### Version
v0.19.0
### Operating system
_No response_
|
1.0
|
EET testClient does not aggregate token transfers properly. - ### Description
When we perform an operation like this :
```
cryptoTransfer(
moving(10, token).between(TOKEN_TREASURY, thirdUser),
moving(20, token).between(TOKEN_TREASURY, firstUser)
)
```
EET produces the following transfer list:
```
tokenTransfers=0.0.1022([0.0.1018 -> -10, 0.0.1021 <- +10, 0.0.1018 -> -20, 0.0.1019 <- +20])([])}
```
This results in `ACCOUNT_REPEATED_IN_ACCOUNT_AMOUNTS` response from the nodes.
### Steps to reproduce
Perform a test that does a crypto transfer similar to
```
cryptoTransfer(
moving(10, token).between(TOKEN_TREASURY, thirdUser),
moving(20, token).between(TOKEN_TREASURY, firstUser)
)
```
### Additional context
_No response_
### Hedera network
other
### Version
v0.19.0
### Operating system
_No response_
|
test
|
eet testclient does not aggregate token transfers properly description when we perform an operation like this cryptotransfer moving token between token treasury thirduser moving token between token treasury firstuser eet produces the following transfer list tokentransfers this results in account repeated in account amounts response from the nodes steps to reproduce perform a test that does a crypto transfer similar to cryptotransfer moving token between token treasury thirduser moving token between token treasury firstuser additional context no response hedera network other version operating system no response
| 1
|
199,049
| 6,980,316,123
|
IssuesEvent
|
2017-12-13 01:00:38
|
krokodilj/kits
|
https://api.github.com/repos/krokodilj/kits
|
opened
|
README badges for Travis and Sonar
|
low priority sonar travis
|
## Expected Behavior
<!--- If you're describing a bug, tell us what should happen -->
<!--- If you're suggesting a change/improvement, tell us how it should work -->
Badges should be displayed in README with proper status and link to Travis/Sonar page
## Current Behavior
<!--- If describing a bug, tell us what happens instead of the expected behavior -->
<!--- If suggesting a change/improvement, explain the difference from current behavior -->
There are two badges, their status is fixed at the moment.
Clicking on Travis badge leads to the appropriate TravisCI build page.
Clicking on Sonar badge leads to sonarqube homepage. It doesn't work properly.
## Possible Solution
<!--- Not obligatory, but suggest a fix/reason for the bug, -->
<!--- or ideas how to implement the addition or change -->
Search the web for possible markup changes in README to fix the badges.
|
1.0
|
README badges for Travis and Sonar - ## Expected Behavior
<!--- If you're describing a bug, tell us what should happen -->
<!--- If you're suggesting a change/improvement, tell us how it should work -->
Badges should be displayed in README with proper status and link to Travis/Sonar page
## Current Behavior
<!--- If describing a bug, tell us what happens instead of the expected behavior -->
<!--- If suggesting a change/improvement, explain the difference from current behavior -->
There are two badges, their status is fixed at the moment.
Clicking on Travis badge leads to the appropriate TravisCI build page.
Clicking on Sonar badge leads to sonarqube homepage. It doesn't work properly.
## Possible Solution
<!--- Not obligatory, but suggest a fix/reason for the bug, -->
<!--- or ideas how to implement the addition or change -->
Search the web for possible markup changes in README to fix the badges.
|
non_test
|
readme badges for travis and sonar expected behavior badges should be displayed in readme with proper status and link to travis sonar page current behavior there are two badges their status is fixed at the moment clicking on travis badge leads to the appropriate travisci build page clicking on sonar badge leads to sonarqube homepage it doesn t work properly possible solution search the web for possible markup changes in readme to fix the badges
| 0
|
303,307
| 26,198,872,092
|
IssuesEvent
|
2023-01-03 15:43:53
|
cockroachdb/cockroach
|
https://api.github.com/repos/cockroachdb/cockroach
|
closed
|
roachtest: backupTPCC failed
|
C-test-failure O-robot O-roachtest release-blocker T-disaster-recovery branch-release-22.2
|
roachtest.backupTPCC [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/8147282?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/8147282?buildTab=artifacts#/backupTPCC) on release-22.2 @ [07a53a36601e9ca5fcffcff55f69b43c6dfbf1c1](https://github.com/cockroachdb/cockroach/commits/07a53a36601e9ca5fcffcff55f69b43c6dfbf1c1):
```
test artifacts and logs in: /artifacts/backupTPCC/run_1
(test_impl.go:286).Fatal: monitor failure: monitor task failed: pq: Use of BACKUP with incremental requires an enterprise license. Your evaluation license expired on December 30, 2022. If you're interested in getting a new license, please contact subscriptions@cockroachlabs.com and we can help you out.
```
<p>Parameters: <code>ROACHTEST_cloud=gce</code>
, <code>ROACHTEST_cpu=4</code>
, <code>ROACHTEST_encrypted=false</code>
, <code>ROACHTEST_ssd=0</code>
</p>
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
<details><summary>Same failure on other branches</summary>
<p>
- #94478 roachtest: backupTPCC failed [C-test-failure O-roachtest O-robot T-disaster-recovery branch-release-22.1 release-blocker]
</p>
</details>
/cc @cockroachdb/disaster-recovery
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*backupTPCC.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-22926
|
2.0
|
roachtest: backupTPCC failed - roachtest.backupTPCC [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/8147282?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/8147282?buildTab=artifacts#/backupTPCC) on release-22.2 @ [07a53a36601e9ca5fcffcff55f69b43c6dfbf1c1](https://github.com/cockroachdb/cockroach/commits/07a53a36601e9ca5fcffcff55f69b43c6dfbf1c1):
```
test artifacts and logs in: /artifacts/backupTPCC/run_1
(test_impl.go:286).Fatal: monitor failure: monitor task failed: pq: Use of BACKUP with incremental requires an enterprise license. Your evaluation license expired on December 30, 2022. If you're interested in getting a new license, please contact subscriptions@cockroachlabs.com and we can help you out.
```
<p>Parameters: <code>ROACHTEST_cloud=gce</code>
, <code>ROACHTEST_cpu=4</code>
, <code>ROACHTEST_encrypted=false</code>
, <code>ROACHTEST_ssd=0</code>
</p>
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
<details><summary>Same failure on other branches</summary>
<p>
- #94478 roachtest: backupTPCC failed [C-test-failure O-roachtest O-robot T-disaster-recovery branch-release-22.1 release-blocker]
</p>
</details>
/cc @cockroachdb/disaster-recovery
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*backupTPCC.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-22926
|
test
|
roachtest backuptpcc failed roachtest backuptpcc with on release test artifacts and logs in artifacts backuptpcc run test impl go fatal monitor failure monitor task failed pq use of backup with incremental requires an enterprise license your evaluation license expired on december if you re interested in getting a new license please contact subscriptions cockroachlabs com and we can help you out parameters roachtest cloud gce roachtest cpu roachtest encrypted false roachtest ssd help see see same failure on other branches roachtest backuptpcc failed cc cockroachdb disaster recovery jira issue crdb
| 1
|
225,494
| 17,268,023,959
|
IssuesEvent
|
2021-07-22 15:55:55
|
rafkub/oop-principles
|
https://api.github.com/repos/rafkub/oop-principles
|
closed
|
Illustrate High Cohesion
|
documentation feature
|
- [ ] Code showing Low Cohesion
- [ ] Code showing High Cohesion
- [ ] README.md with short explanation of High Cohesion
|
1.0
|
Illustrate High Cohesion - - [ ] Code showing Low Cohesion
- [ ] Code showing High Cohesion
- [ ] README.md with short explanation of High Cohesion
|
non_test
|
illustrate high cohesion code showing low cohesion code showing high cohesion readme md with short explanation of high cohesion
| 0
|
333,283
| 29,520,319,239
|
IssuesEvent
|
2023-06-05 00:35:23
|
cse110-sp23-group1/Origami-Fortune-Teller
|
https://api.github.com/repos/cse110-sp23-group1/Origami-Fortune-Teller
|
opened
|
Create E2E test for general user flow throughout the site.
|
testing
|
- [ ] Test to make sure user sees correct fortunes on site load.
- [ ] Test to make sure changed preset is reflected correctly.
- [ ] Test to make sure correct SVG is shown at each animation step.
- [ ] Test to make sure hovering over a flap changes color.
- [ ] Test to make sure word on end flap is reflected correctly.
- [ ] Test to make sure reset/play again buttons work correctly.
please add more tests.
|
1.0
|
Create E2E test for general user flow throughout the site. - - [ ] Test to make sure user sees correct fortunes on site load.
- [ ] Test to make sure changed preset is reflected correctly.
- [ ] Test to make sure correct SVG is shown at each animation step.
- [ ] Test to make sure hovering over a flap changes color.
- [ ] Test to make sure word on end flap is reflected correctly.
- [ ] Test to make sure reset/play again buttons work correctly.
please add more tests.
|
test
|
create test for general user flow throughout the site test to make sure user sees correct fortunes on site load test to make sure changed preset is reflected correctly test to make sure correct svg is shown at each animation step test to make sure hovering over a flap changes color test to make sure word on end flap is reflected correctly test to make sure reset play again buttons work correctly please add more tests
| 1
|
187,623
| 6,759,794,878
|
IssuesEvent
|
2017-10-24 18:20:25
|
cyclejs/cyclejs
|
https://api.github.com/repos/cyclejs/cyclejs
|
closed
|
Get source maps right in all packages
|
issue is bug priority 3 (should) scope: misc size S
|
What I've described [in xstream](https://github.com/staltz/xstream/issues/221) is probably going on in at least some of the packages here. At least for `@cycle/history`, I get this:
```
WARNING in ./node_modules/@cycle/history/lib/es6/captureClicks.js
(Emitted value instead of an instance of Error) Cannot find source file '../../src/captureClicks.ts': Error: Can't resolve '../../src/captureClicks.ts' in '/home/s
hahar/src/cyclejs-components/www/node_modules/@cycle/history/lib/es6'
@ ./node_modules/@cycle/history/lib/es6/index.js 75:0-48 @ ./src/index.ts
WARNING in ./node_modules/@cycle/history/lib/es6/createHistory$.js
(Emitted value instead of an instance of Error) Cannot find source file '../../src/createHistory$.ts': Error: Can't resolve '../../src/createHistory$.ts' in '/home
/shahar/src/cyclejs-components/www/node_modules/@cycle/history/lib/es6'
@ ./node_modules/@cycle/history/lib/es6/drivers.js 2:0-50
@ ./node_modules/@cycle/history/lib/es6/index.js @ ./src/index.ts
WARNING in ./node_modules/@cycle/history/lib/es6/drivers.js
(Emitted value instead of an instance of Error) Cannot find source file '../../src/drivers.ts': Error: Can't resolve '../../src/drivers.ts' in '/home/shahar/src/cy
clejs-components/www/node_modules/@cycle/history/lib/es6'
@ ./node_modules/@cycle/history/lib/es6/index.js 37:0-46 54:0-50 93:0-52 @ ./src/index.ts
WARNING in ./node_modules/@cycle/history/lib/es6/index.js
(Emitted value instead of an instance of Error) Cannot find source file '../../src/index.ts': Error: Can't resolve '../../src/index.ts' in '/home/shahar/src/cyclej
s-components/www/node_modules/@cycle/history/lib/es6'
@ ./src/index.ts 4:18-43
```
|
1.0
|
Get source maps right in all packages - What I've described [in xstream](https://github.com/staltz/xstream/issues/221) is probably going on in at least some of the packages here. At least for `@cycle/history`, I get this:
```
WARNING in ./node_modules/@cycle/history/lib/es6/captureClicks.js
(Emitted value instead of an instance of Error) Cannot find source file '../../src/captureClicks.ts': Error: Can't resolve '../../src/captureClicks.ts' in '/home/s
hahar/src/cyclejs-components/www/node_modules/@cycle/history/lib/es6'
@ ./node_modules/@cycle/history/lib/es6/index.js 75:0-48 @ ./src/index.ts
WARNING in ./node_modules/@cycle/history/lib/es6/createHistory$.js
(Emitted value instead of an instance of Error) Cannot find source file '../../src/createHistory$.ts': Error: Can't resolve '../../src/createHistory$.ts' in '/home
/shahar/src/cyclejs-components/www/node_modules/@cycle/history/lib/es6'
@ ./node_modules/@cycle/history/lib/es6/drivers.js 2:0-50
@ ./node_modules/@cycle/history/lib/es6/index.js @ ./src/index.ts
WARNING in ./node_modules/@cycle/history/lib/es6/drivers.js
(Emitted value instead of an instance of Error) Cannot find source file '../../src/drivers.ts': Error: Can't resolve '../../src/drivers.ts' in '/home/shahar/src/cy
clejs-components/www/node_modules/@cycle/history/lib/es6'
@ ./node_modules/@cycle/history/lib/es6/index.js 37:0-46 54:0-50 93:0-52 @ ./src/index.ts
WARNING in ./node_modules/@cycle/history/lib/es6/index.js
(Emitted value instead of an instance of Error) Cannot find source file '../../src/index.ts': Error: Can't resolve '../../src/index.ts' in '/home/shahar/src/cyclej
s-components/www/node_modules/@cycle/history/lib/es6'
@ ./src/index.ts 4:18-43
```
|
non_test
|
get source maps right in all packages what i ve described is probably going on in at least some of the packages here at least for cycle history i get this warning in node modules cycle history lib captureclicks js emitted value instead of an instance of error cannot find source file src captureclicks ts error can t resolve src captureclicks ts in home s hahar src cyclejs components www node modules cycle history lib node modules cycle history lib index js src index ts warning in node modules cycle history lib createhistory js emitted value instead of an instance of error cannot find source file src createhistory ts error can t resolve src createhistory ts in home shahar src cyclejs components www node modules cycle history lib node modules cycle history lib drivers js node modules cycle history lib index js src index ts warning in node modules cycle history lib drivers js emitted value instead of an instance of error cannot find source file src drivers ts error can t resolve src drivers ts in home shahar src cy clejs components www node modules cycle history lib node modules cycle history lib index js src index ts warning in node modules cycle history lib index js emitted value instead of an instance of error cannot find source file src index ts error can t resolve src index ts in home shahar src cyclej s components www node modules cycle history lib src index ts
| 0
|
235,643
| 18,054,111,268
|
IssuesEvent
|
2021-09-20 05:01:26
|
bstudios/adam-rms
|
https://api.github.com/repos/bstudios/adam-rms
|
opened
|
[DOCS] Various Documentation updates
|
documentation
|
### What would you like the training to cover?
- [ ] Interface introduction (what do Icons mean etc)
- [ ] User account pages
- [ ] Linked asset documentation (child vs parent)
- [ ] Public Site
### Is this already partially covered elsewhere?
No
### Anything else?
_No response_
|
1.0
|
[DOCS] Various Documentation updates - ### What would you like the training to cover?
- [ ] Interface introduction (what do Icons mean etc)
- [ ] User account pages
- [ ] Linked asset documentation (child vs parent)
- [ ] Public Site
### Is this already partially covered elsewhere?
No
### Anything else?
_No response_
|
non_test
|
various documentation updates what would you like the training to cover interface introduction what do icons mean etc user account pages linked asset documentation child vs parent public site is this already partially covered elsewhere no anything else no response
| 0
|
236,861
| 19,580,287,477
|
IssuesEvent
|
2022-01-04 20:19:46
|
cockroachdb/cockroach
|
https://api.github.com/repos/cockroachdb/cockroach
|
closed
|
roachtest: pgx failed
|
C-test-failure O-robot O-roachtest branch-master release-blocker
|
roachtest.pgx [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=3993762&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=3993762&tab=artifacts#/pgx) on master @ [8c1528fff5c132b971428bc7f18bf0ea5eb16799](https://github.com/cockroachdb/cockroach/commits/8c1528fff5c132b971428bc7f18bf0ea5eb16799):
```
The test failed on branch=master, cloud=gce:
test artifacts and logs in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/pgx/run_1
orm_helpers.go:245,orm_helpers.go:171,pgx.go:141,pgx.go:152,test_runner.go:780:
Tests run on Cockroach v22.1.0-alpha.00000000-2441-g8c1528fff5
Tests run against pgx v4.11.0
184 Total Tests Run
183 tests passed
1 test failed
29 tests skipped
3 tests ignored
0 tests passed unexpectedly
1 test failed unexpectedly
0 tests expected failed but skipped
0 tests expected failed but not run
---
--- FAIL: v4.TestConnSendBatchMany - unknown (unexpected)
For a full summary look at the pgx artifacts
An updated blocklist (pgxBlocklist22_1) is available in the artifacts' pgx log
```
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/sql-experience
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*pgx.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
|
2.0
|
roachtest: pgx failed - roachtest.pgx [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=3993762&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=3993762&tab=artifacts#/pgx) on master @ [8c1528fff5c132b971428bc7f18bf0ea5eb16799](https://github.com/cockroachdb/cockroach/commits/8c1528fff5c132b971428bc7f18bf0ea5eb16799):
```
The test failed on branch=master, cloud=gce:
test artifacts and logs in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/pgx/run_1
orm_helpers.go:245,orm_helpers.go:171,pgx.go:141,pgx.go:152,test_runner.go:780:
Tests run on Cockroach v22.1.0-alpha.00000000-2441-g8c1528fff5
Tests run against pgx v4.11.0
184 Total Tests Run
183 tests passed
1 test failed
29 tests skipped
3 tests ignored
0 tests passed unexpectedly
1 test failed unexpectedly
0 tests expected failed but skipped
0 tests expected failed but not run
---
--- FAIL: v4.TestConnSendBatchMany - unknown (unexpected)
For a full summary look at the pgx artifacts
An updated blocklist (pgxBlocklist22_1) is available in the artifacts' pgx log
```
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/sql-experience
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*pgx.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
|
test
|
roachtest pgx failed roachtest pgx with on master the test failed on branch master cloud gce test artifacts and logs in home agent work go src github com cockroachdb cockroach artifacts pgx run orm helpers go orm helpers go pgx go pgx go test runner go tests run on cockroach alpha tests run against pgx total tests run tests passed test failed tests skipped tests ignored tests passed unexpectedly test failed unexpectedly tests expected failed but skipped tests expected failed but not run fail testconnsendbatchmany unknown unexpected for a full summary look at the pgx artifacts an updated blocklist is available in the artifacts pgx log help see see cc cockroachdb sql experience
| 1
|
171,688
| 13,244,237,657
|
IssuesEvent
|
2020-08-19 12:45:58
|
cockroachdb/cockroach
|
https://api.github.com/repos/cockroachdb/cockroach
|
closed
|
roachtest: acceptance/version-upgrade replica divergence
|
C-test-failure
|
Got this one in TC
https://teamcity.cockroachdb.com/viewLog.html?buildId=2193857&buildTypeId=Cockroach_UnitTests
```
| runtime.goexit
| /usr/local/go/src/runtime/asm_amd64.s:1357
Wraps: (2) 5 safe details enclosed
Wraps: (3) r273 (/Table/39) is inconsistent: RANGE_INCONSISTENT
| (n4,s4):2: checksum ed7dab4b5c025c23de1aa6b05b6ed71de040f8305e2cfc84ad9075efbc915dc7cc15506bc9643f915ef63342f0adacc72bf7972a60150b3c278e77a7c0c24be2
| - stats: contains_estimates:0 last_update_nanos:1597771902160888573 intent_age:0 gc_bytes_age:111375 live_bytes:448 live_count:8 key_bytes:1624 key_count:8 val_bytes:2520 val_count:120 intent_bytes:0 intent_count:0 sys_bytes:855 sys_count:11 abort_span_bytes:3
| - stats.Sub(recomputation): last_update_nanos:1597771902160888573 gc_bytes_age:111375 live_bytes:448 live_count:8 key_bytes:1624 key_count:8 val_bytes:2520 val_count:120 sys_bytes:855 sys_count:11 abort_span_bytes:3
| (n1,s1):1: checksum ed7dab4b5c025c23de1aa6b05b6ed71de040f8305e2cfc84ad9075efbc915dc7cc15506bc9643f915ef63342f0adacc72bf7972a60150b3c278e77a7c0c24be2
| - stats: contains_estimates:0 last_update_nanos:1597771902160888573 intent_age:0 gc_bytes_age:111375 live_bytes:448 live_count:8 key_bytes:1624 key_count:8 val_bytes:2520 val_count:120 intent_bytes:0 intent_count:0 sys_bytes:855 sys_count:11 abort_span_bytes:3
| - stats.Sub(recomputation): last_update_nanos:1597771902160888573 gc_bytes_age:111375 live_bytes:448 live_count:8 key_bytes:1624 key_count:8 val_bytes:2520 val_count:120 sys_bytes:855 sys_count:11 abort_span_bytes:3
| (n3,s3):3: checksum eeae37c2fd09b4d36ab136d6287ac83602355685d37478b4868aa74c9141e02dc91caab524eb7a3a31d1fa98c531d04849ac866bdc30b03a2847d1a3b047630c [minority]
| - stats: contains_estimates:0 last_update_nanos:1597771902160888573 intent_age:0 gc_bytes_age:111375 live_bytes:448 live_count:8 key_bytes:1624 key_count:8 val_bytes:2520 val_count:120 intent_bytes:0 intent_count:0 sys_bytes:855 sys_count:11 abort_span_bytes:0
| - stats.Sub(recomputation): last_update_nanos:1597771902160888573 gc_bytes_age:111375 live_bytes:448 live_count:8 key_bytes:1624 key_count:8 val_bytes:2520 val_count:120 sys_bytes:855 sys_count:11
Error types: (1) *withstack.withStack (2) *safedetails.withSafeDetails (3) *errors.errorString
test artifacts and logs in: artifacts/acceptance/version-upgrade/run_1
cluster.go:1699,test_runner.go:837: r273 (/Table/39) is inconsistent: RANGE_INCONSISTENT
(1) attached stack trace
| main.(*cluster).CheckReplicaDivergenceOnDB
| /go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:1650
| main.(*cluster).FailOnReplicaDivergence.func2
| /go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:1696
| github.com/cockroachdb/cockroach/pkg/util/contextutil.RunWithTimeout
| /go/src/github.com/cockroachdb/cockroach/pkg/util/contextutil/context.go:135
| main.(*cluster).FailOnReplicaDivergence
| /go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:1693
| main.(*testRunner).runTest
| /go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/test_runner.go:837
| main.(*testRunner).runWorker
| /go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/test_runner.go:464
| main.(*testRunner).Run.func2
| /go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/test_runner.go:275
| github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).RunWorker.func1
| /go/src/github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:222
| runtime.goexit
| /usr/local/go/src/runtime/asm_amd64.s:1357
Wraps: (2) 5 safe details enclosed
```
https://teamcity.cockroachdb.com/viewLog.html?buildId=2193857&buildTypeId=Cockroach_UnitTests
|
1.0
|
roachtest: acceptance/version-upgrade replica divergence - Got this one in TC
https://teamcity.cockroachdb.com/viewLog.html?buildId=2193857&buildTypeId=Cockroach_UnitTests
```
| runtime.goexit
| /usr/local/go/src/runtime/asm_amd64.s:1357
Wraps: (2) 5 safe details enclosed
Wraps: (3) r273 (/Table/39) is inconsistent: RANGE_INCONSISTENT
| (n4,s4):2: checksum ed7dab4b5c025c23de1aa6b05b6ed71de040f8305e2cfc84ad9075efbc915dc7cc15506bc9643f915ef63342f0adacc72bf7972a60150b3c278e77a7c0c24be2
| - stats: contains_estimates:0 last_update_nanos:1597771902160888573 intent_age:0 gc_bytes_age:111375 live_bytes:448 live_count:8 key_bytes:1624 key_count:8 val_bytes:2520 val_count:120 intent_bytes:0 intent_count:0 sys_bytes:855 sys_count:11 abort_span_bytes:3
| - stats.Sub(recomputation): last_update_nanos:1597771902160888573 gc_bytes_age:111375 live_bytes:448 live_count:8 key_bytes:1624 key_count:8 val_bytes:2520 val_count:120 sys_bytes:855 sys_count:11 abort_span_bytes:3
| (n1,s1):1: checksum ed7dab4b5c025c23de1aa6b05b6ed71de040f8305e2cfc84ad9075efbc915dc7cc15506bc9643f915ef63342f0adacc72bf7972a60150b3c278e77a7c0c24be2
| - stats: contains_estimates:0 last_update_nanos:1597771902160888573 intent_age:0 gc_bytes_age:111375 live_bytes:448 live_count:8 key_bytes:1624 key_count:8 val_bytes:2520 val_count:120 intent_bytes:0 intent_count:0 sys_bytes:855 sys_count:11 abort_span_bytes:3
| - stats.Sub(recomputation): last_update_nanos:1597771902160888573 gc_bytes_age:111375 live_bytes:448 live_count:8 key_bytes:1624 key_count:8 val_bytes:2520 val_count:120 sys_bytes:855 sys_count:11 abort_span_bytes:3
| (n3,s3):3: checksum eeae37c2fd09b4d36ab136d6287ac83602355685d37478b4868aa74c9141e02dc91caab524eb7a3a31d1fa98c531d04849ac866bdc30b03a2847d1a3b047630c [minority]
| - stats: contains_estimates:0 last_update_nanos:1597771902160888573 intent_age:0 gc_bytes_age:111375 live_bytes:448 live_count:8 key_bytes:1624 key_count:8 val_bytes:2520 val_count:120 intent_bytes:0 intent_count:0 sys_bytes:855 sys_count:11 abort_span_bytes:0
| - stats.Sub(recomputation): last_update_nanos:1597771902160888573 gc_bytes_age:111375 live_bytes:448 live_count:8 key_bytes:1624 key_count:8 val_bytes:2520 val_count:120 sys_bytes:855 sys_count:11
Error types: (1) *withstack.withStack (2) *safedetails.withSafeDetails (3) *errors.errorString
test artifacts and logs in: artifacts/acceptance/version-upgrade/run_1
cluster.go:1699,test_runner.go:837: r273 (/Table/39) is inconsistent: RANGE_INCONSISTENT
(1) attached stack trace
| main.(*cluster).CheckReplicaDivergenceOnDB
| /go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:1650
| main.(*cluster).FailOnReplicaDivergence.func2
| /go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:1696
| github.com/cockroachdb/cockroach/pkg/util/contextutil.RunWithTimeout
| /go/src/github.com/cockroachdb/cockroach/pkg/util/contextutil/context.go:135
| main.(*cluster).FailOnReplicaDivergence
| /go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:1693
| main.(*testRunner).runTest
| /go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/test_runner.go:837
| main.(*testRunner).runWorker
| /go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/test_runner.go:464
| main.(*testRunner).Run.func2
| /go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/test_runner.go:275
| github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).RunWorker.func1
| /go/src/github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:222
| runtime.goexit
| /usr/local/go/src/runtime/asm_amd64.s:1357
Wraps: (2) 5 safe details enclosed
```
https://teamcity.cockroachdb.com/viewLog.html?buildId=2193857&buildTypeId=Cockroach_UnitTests
|
test
|
roachtest acceptance version upgrade replica divergence got this one in tc runtime goexit usr local go src runtime asm s wraps safe details enclosed wraps table is inconsistent range inconsistent checksum stats contains estimates last update nanos intent age gc bytes age live bytes live count key bytes key count val bytes val count intent bytes intent count sys bytes sys count abort span bytes stats sub recomputation last update nanos gc bytes age live bytes live count key bytes key count val bytes val count sys bytes sys count abort span bytes checksum stats contains estimates last update nanos intent age gc bytes age live bytes live count key bytes key count val bytes val count intent bytes intent count sys bytes sys count abort span bytes stats sub recomputation last update nanos gc bytes age live bytes live count key bytes key count val bytes val count sys bytes sys count abort span bytes checksum stats contains estimates last update nanos intent age gc bytes age live bytes live count key bytes key count val bytes val count intent bytes intent count sys bytes sys count abort span bytes stats sub recomputation last update nanos gc bytes age live bytes live count key bytes key count val bytes val count sys bytes sys count error types withstack withstack safedetails withsafedetails errors errorstring test artifacts and logs in artifacts acceptance version upgrade run cluster go test runner go table is inconsistent range inconsistent attached stack trace main cluster checkreplicadivergenceondb go src github com cockroachdb cockroach pkg cmd roachtest cluster go main cluster failonreplicadivergence go src github com cockroachdb cockroach pkg cmd roachtest cluster go github com cockroachdb cockroach pkg util contextutil runwithtimeout go src github com cockroachdb cockroach pkg util contextutil context go main cluster failonreplicadivergence go src github com cockroachdb cockroach pkg cmd roachtest cluster go main testrunner runtest go src github com cockroachdb cockroach pkg cmd roachtest test runner go main testrunner runworker go src github com cockroachdb cockroach pkg cmd roachtest test runner go main testrunner run go src github com cockroachdb cockroach pkg cmd roachtest test runner go github com cockroachdb cockroach pkg util stop stopper runworker go src github com cockroachdb cockroach pkg util stop stopper go runtime goexit usr local go src runtime asm s wraps safe details enclosed
| 1
|
117,330
| 15,087,278,682
|
IssuesEvent
|
2021-02-05 21:50:51
|
vmware/clarity
|
https://api.github.com/repos/vmware/clarity
|
closed
|
Justified Tabs component (new)
|
Dev priority: 1 low type: design type: new component ux: ready
|
### Description
Justified tabs allow you to justify the tabs across the width of the container. The width is distributed equally between tabs and the labels are center-aligned. This layout works best for small containers (width less than 500 px) with 2 to 4 tabs.
### Documentation
#### With Smart Resizing
By default, smart resizing is enabled for justified tabs. When the width of the container exceeds the threshold (pre-defined as 500 px), the container automatically switches to regular tabs.
This is helpful when developing responsive applications that will be accessed on all form factors: from phones to large displays. On the phone, the screen width is small and the use case is typically limited. With the few tabs you might need to display, it is helpful to justify the tabs to maximize the touch area for each tab. When the application is viewed on a larger display, the component automatically switches to regular tabs, which allows you to contextually display additional tabs (and even use tab overflow functionality) for a more in-depth use case.
#### Without Smart Resizing
You can also use justified tabs without smart resizing.
This is helpful when you want to justify tabs purely from a stylistic point of view. This style is often seen in marketing pages and in software applications such as the Safari Browser and the Mac Finder. However, use this style with discretion. In large containers, the tab labels might be spaced far apart and affect the visual discoverability of the non-active tabs.
#### Labels
In addition to the general tab usage guidelines below, consider the following when labeling justified tabs:
• A minimum of 12 px padding is applied to the left and right of each tab label.
• If the labels are too long to fit in a single line, then they will wrap.
<br>
<img src="https://user-images.githubusercontent.com/31904821/30993167-7111a420-a462-11e7-8202-5b7e617de666.png" height="151" width="392">
<br>
|
1.0
|
Justified Tabs component (new) - ### Description
Justified tabs allow you to justify the tabs across the width of the container. The width is distributed equally between tabs and the labels are center-aligned. This layout works best for small containers (width less than 500 px) with 2 to 4 tabs.
### Documentation
#### With Smart Resizing
By default, smart resizing is enabled for justified tabs. When the width of the container exceeds the threshold (pre-defined as 500 px), the container automatically switches to regular tabs.
This is helpful when developing responsive applications that will be accessed on all form factors: from phones to large displays. On the phone, the screen width is small and the use case is typically limited. With the few tabs you might need to display, it is helpful to justify the tabs to maximize the touch area for each tab. When the application is viewed on a larger display, the component automatically switches to regular tabs, which allows you to contextually display additional tabs (and even use tab overflow functionality) for a more in-depth use case.
#### Without Smart Resizing
You can also use justified tabs without smart resizing.
This is helpful when you want to justify tabs purely from a stylistic point of view. This style is often seen in marketing pages and in software applications such as the Safari Browser and the Mac Finder. However, use this style with discretion. In large containers, the tab labels might be spaced far apart and affect the visual discoverability of the non-active tabs.
#### Labels
In addition to the general tab usage guidelines below, consider the following when labeling justified tabs:
• A minimum of 12 px padding is applied to the left and right of each tab label.
• If the labels are too long to fit in a single line, then they will wrap.
<br>
<img src="https://user-images.githubusercontent.com/31904821/30993167-7111a420-a462-11e7-8202-5b7e617de666.png" height="151" width="392">
<br>
|
non_test
|
justified tabs component new description justified tabs allow you to justify the tabs across the width of the container the width is distributed equally between tabs and the labels are center aligned this layout works best for small containers width less than px with to tabs documentation with smart resizing by default smart resizing is enabled for justified tabs when the width of the container exceeds the threshold pre defined as px the container automatically switches to regular tabs this is helpful when developing responsive applications that will be accessed on all form factors from phones to large displays on the phone the screen width is small and the use case is typically limited with the few tabs you might need to display it is helpful to justify the tabs to maximize the touch area for each tab when the application is viewed on a larger display the component automatically switches to regular tabs which allows you to contextually display additional tabs and even use tab overflow functionality for a more in depth use case without smart resizing you can also use justified tabs without smart resizing this is helpful when you want to justify tabs purely from a stylistic point of view this style is often seen in marketing pages and in software applications such as the safari browser and the mac finder however use this style with discretion in large containers the tab labels might be spaced far apart and affect the visual discoverability of the non active tabs labels in addition to the general tab usage guidelines below consider the following when labeling justified tabs • a minimum of px padding is applied to the left and right of each tab label • if the labels are too long to fit in a single line then they will wrap
| 0
|
133,449
| 10,822,166,212
|
IssuesEvent
|
2019-11-08 20:31:28
|
scalacenter/bloop
|
https://api.github.com/repos/scalacenter/bloop
|
closed
|
Passing JVM options to test throws unrecognised option
|
bug needs information task / test
|
```
bloop test dse-db -- -J-Xmx1024M
[E] Unrecognized option: -J-Xmx1024M
[E] Error: Could not create the Java Virtual Machine.
[E] Error: A fatal exception has occurred. Program will exit.
===============================================
Total duration: 0ms
No test suites were run.
===============================================
```
`-J` prefix is not stripped?
|
1.0
|
Passing JVM options to test throws unrecognised option - ```
bloop test dse-db -- -J-Xmx1024M
[E] Unrecognized option: -J-Xmx1024M
[E] Error: Could not create the Java Virtual Machine.
[E] Error: A fatal exception has occurred. Program will exit.
===============================================
Total duration: 0ms
No test suites were run.
===============================================
```
`-J` prefix is not stripped?
|
test
|
passing jvm options to test throws unrecognised option bloop test dse db j unrecognized option j error could not create the java virtual machine error a fatal exception has occurred program will exit total duration no test suites were run j prefix is not stripped
| 1
|
5,856
| 2,796,439,139
|
IssuesEvent
|
2015-05-12 07:31:05
|
h2opaulh2o/IP-A3-Project
|
https://api.github.com/repos/h2opaulh2o/IP-A3-Project
|
closed
|
Run tests made for XMLReader and XMLWriter
|
Testing
|
Run the tests made for XMLReader and XMLWriter and document the result. (The classes that are tested, short description of how it is implemented and whether or not the tests passed. If it didn't passed the test please add some opinions about what do you think is wrong.) The documentation will be sent to me (sirbucristina.is@gmail.com)
|
1.0
|
Run tests made for XMLReader and XMLWriter - Run the tests made for XMLReader and XMLWriter and document the result. (The classes that are tested, short description of how it is implemented and whether or not the tests passed. If it didn't passed the test please add some opinions about what do you think is wrong.) The documentation will be sent to me (sirbucristina.is@gmail.com)
|
test
|
run tests made for xmlreader and xmlwriter run the tests made for xmlreader and xmlwriter and document the result the classes that are tested short description of how it is implemented and whether or not the tests passed if it didn t passed the test please add some opinions about what do you think is wrong the documentation will be sent to me sirbucristina is gmail com
| 1
|
312,538
| 23,431,280,977
|
IssuesEvent
|
2022-08-15 02:57:08
|
DevOps-Sum22-Inventory-Squad/inventory
|
https://api.github.com/repos/DevOps-Sum22-Inventory-Squad/inventory
|
closed
|
Need to create documentation for Create Inventory service
|
documentation
|
**As a** Product Owner
**I need** to use Swagger to create interactive documentation for Create Inventory
**So that** REST API can be referred and tested in link BASE_URL+ /apidocs/
### Details and Assumptions
* There is a home page with UI for Inventory service.
* Create service is written with Flask-RESTX
### Acceptance Criteria
```gherkin
Given a REST API for creating an inventory item
When entering link BASE_URL + /apidocs/ on Home Page
Then Usage of the API is explained and can be interactively tested in the sub-page.
```
|
1.0
|
Need to create documentation for Create Inventory service - **As a** Product Owner
**I need** to use Swagger to create interactive documentation for Create Inventory
**So that** REST API can be referred and tested in link BASE_URL+ /apidocs/
### Details and Assumptions
* There is a home page with UI for Inventory service.
* Create service is written with Flask-RESTX
### Acceptance Criteria
```gherkin
Given a REST API for creating an inventory item
When entering link BASE_URL + /apidocs/ on Home Page
Then Usage of the API is explained and can be interactively tested in the sub-page.
```
|
non_test
|
need to create documentation for create inventory service as a product owner i need to use swagger to create interactive documentation for create inventory so that rest api can be referred and tested in link base url apidocs details and assumptions there is a home page with ui for inventory service create service is written with flask restx acceptance criteria gherkin given a rest api for creating an inventory item when entering link base url apidocs on home page then usage of the api is explained and can be interactively tested in the sub page
| 0
|
30,913
| 4,668,604,911
|
IssuesEvent
|
2016-10-06 03:33:33
|
Microsoft/vsts-tasks
|
https://api.github.com/repos/Microsoft/vsts-tasks
|
closed
|
Is TestAgentInstall.ps1 is missing the negative sign on line 71?
|
Area: Test
|
The code segment below from vsts-tasks/Tasks/DeployVisualStudioTestAgent/TestAgentInstall.ps1 looks like its missing the negative sign preceding the exit code const.
``` if($exitCode -eq 2147205120) ```
Is this intended to be the positive value?
|
1.0
|
Is TestAgentInstall.ps1 is missing the negative sign on line 71? - The code segment below from vsts-tasks/Tasks/DeployVisualStudioTestAgent/TestAgentInstall.ps1 looks like its missing the negative sign preceding the exit code const.
``` if($exitCode -eq 2147205120) ```
Is this intended to be the positive value?
|
test
|
is testagentinstall is missing the negative sign on line the code segment below from vsts tasks tasks deployvisualstudiotestagent testagentinstall looks like its missing the negative sign preceding the exit code const if exitcode eq is this intended to be the positive value
| 1
|
139,111
| 11,251,698,628
|
IssuesEvent
|
2020-01-11 02:04:17
|
microsoft/AzureStorageExplorer
|
https://api.github.com/repos/microsoft/AzureStorageExplorer
|
closed
|
Unnecessary horizontal scroll bar appears in bob container delete dialog
|
:computer: mac :heavy_check_mark: merged 🧪 testing
|
**Storage Explorer Version:** 1.12.0
**Build:** [20200109.2](https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=3369695&view=results)
**Branch:** rel/1.12.0
**Platform/OS:** MacOS High Sierra (10.13.6 & 10.15.2)
**Architecture:** x64
**Regression From:** Not a regression
**Steps to reproduce:**
1. Open Storage Explorer -> Select subscription '**Azure Tools Manual Testing 1**'.
2. Expand Storage Accounts -> Select account '**abcdisistestv2**'.
3. Expand the storage account -> Blob Containers.
4. Select blob container '**test**' -> Right click it and click 'Delete'.
5. Check the delete dialog.
**Expect Experience:**
The delete dialog shows well.
**Actual Experience:**
The delete dialog shows odd.
|
1.0
|
Unnecessary horizontal scroll bar appears in bob container delete dialog - **Storage Explorer Version:** 1.12.0
**Build:** [20200109.2](https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=3369695&view=results)
**Branch:** rel/1.12.0
**Platform/OS:** MacOS High Sierra (10.13.6 & 10.15.2)
**Architecture:** x64
**Regression From:** Not a regression
**Steps to reproduce:**
1. Open Storage Explorer -> Select subscription '**Azure Tools Manual Testing 1**'.
2. Expand Storage Accounts -> Select account '**abcdisistestv2**'.
3. Expand the storage account -> Blob Containers.
4. Select blob container '**test**' -> Right click it and click 'Delete'.
5. Check the delete dialog.
**Expect Experience:**
The delete dialog shows well.
**Actual Experience:**
The delete dialog shows odd.
|
test
|
unnecessary horizontal scroll bar appears in bob container delete dialog storage explorer version build branch rel platform os macos high sierra architecture regression from not a regression steps to reproduce open storage explorer select subscription azure tools manual testing expand storage accounts select account expand the storage account blob containers select blob container test right click it and click delete check the delete dialog expect experience the delete dialog shows well actual experience the delete dialog shows odd
| 1
|
79,011
| 9,816,572,481
|
IssuesEvent
|
2019-06-13 14:55:11
|
JoanRosell/BatallaNaval
|
https://api.github.com/repos/JoanRosell/BatallaNaval
|
closed
|
InputHandler class
|
design good first issue
|
# InputHandler
## Gestión del input
Su responsabilidad principal es **interpretar el input** del usuario y **transformarlo en operaciones** que el resto de clases puedan realizar.
Puesto que la librería gráfica que tenemos ya se encarga de la captura de eventos esta clase solo se encarga de procesar esos eventos y mandar instrucciones al resto de objetos.
### Colaboraciones
Colabora con las clases **Board** y **Player** para realizar operaciones sobre las celdas del tablero.
### Tareas pendientes
Falta acabar de definir su interfaz pública y diseñar sus operaciones críticas. En joc.cpp hay un pequeño esbozo de la funcionalidad básica para el despliegue de barcos de los jugadores.
- [ ] Terminar diseño general
- [ ] Diseñar casos de uso
- [ ] Diseñar el formato de las comunicaciones entre las distintas clases
Una vez terminada la fase de diseño pasaremos a realizar una implementación iterativa con el resto de clases colaboradoras. Tener claro el diseño de las comunicaciones entre estas es **crítico**, pues cambiarlo más adelante será un problema.
|
1.0
|
InputHandler class - # InputHandler
## Gestión del input
Su responsabilidad principal es **interpretar el input** del usuario y **transformarlo en operaciones** que el resto de clases puedan realizar.
Puesto que la librería gráfica que tenemos ya se encarga de la captura de eventos esta clase solo se encarga de procesar esos eventos y mandar instrucciones al resto de objetos.
### Colaboraciones
Colabora con las clases **Board** y **Player** para realizar operaciones sobre las celdas del tablero.
### Tareas pendientes
Falta acabar de definir su interfaz pública y diseñar sus operaciones críticas. En joc.cpp hay un pequeño esbozo de la funcionalidad básica para el despliegue de barcos de los jugadores.
- [ ] Terminar diseño general
- [ ] Diseñar casos de uso
- [ ] Diseñar el formato de las comunicaciones entre las distintas clases
Una vez terminada la fase de diseño pasaremos a realizar una implementación iterativa con el resto de clases colaboradoras. Tener claro el diseño de las comunicaciones entre estas es **crítico**, pues cambiarlo más adelante será un problema.
|
non_test
|
inputhandler class inputhandler gestión del input su responsabilidad principal es interpretar el input del usuario y transformarlo en operaciones que el resto de clases puedan realizar puesto que la librería gráfica que tenemos ya se encarga de la captura de eventos esta clase solo se encarga de procesar esos eventos y mandar instrucciones al resto de objetos colaboraciones colabora con las clases board y player para realizar operaciones sobre las celdas del tablero tareas pendientes falta acabar de definir su interfaz pública y diseñar sus operaciones críticas en joc cpp hay un pequeño esbozo de la funcionalidad básica para el despliegue de barcos de los jugadores terminar diseño general diseñar casos de uso diseñar el formato de las comunicaciones entre las distintas clases una vez terminada la fase de diseño pasaremos a realizar una implementación iterativa con el resto de clases colaboradoras tener claro el diseño de las comunicaciones entre estas es crítico pues cambiarlo más adelante será un problema
| 0
|
40,233
| 6,808,485,048
|
IssuesEvent
|
2017-11-04 03:26:45
|
canjs/can-util
|
https://api.github.com/repos/canjs/can-util
|
opened
|
Add actual @deprecated tags to all the deprecated docs
|
documentation
|
Right now their descriptions mention that they’re deprecated, but the `@deprecated` tag will make it more apparent (and also provide a version number for when they were deprecated).
|
1.0
|
Add actual @deprecated tags to all the deprecated docs - Right now their descriptions mention that they’re deprecated, but the `@deprecated` tag will make it more apparent (and also provide a version number for when they were deprecated).
|
non_test
|
add actual deprecated tags to all the deprecated docs right now their descriptions mention that they’re deprecated but the deprecated tag will make it more apparent and also provide a version number for when they were deprecated
| 0
|
809,784
| 30,210,152,121
|
IssuesEvent
|
2023-07-05 12:16:26
|
latteart-org/latteart
|
https://api.github.com/repos/latteart-org/latteart
|
closed
|
記録の一時停止が含まれるテスト結果に対してリプレイを実行するとエラーになる
|
Type: Bug Priority: Should Effort: 1
|
リプレイ実行時のダイアログに記録の一時停止前まで実行されると警告文が表示されるが、実際に実行するとエラーとなる。
また、エラーが発生した操作がエラーダイアログに表示されない。
## 期待結果
~~記録の一時停止前まで実行されてエラーなく終了すること。~~
リプレイ実行時のダイアログに、一時停止・再開が含まれるため正常に動作しない可能性がある旨をメッセージとして表示した上で、pause_capturing、resume_capturing行はすべて無視してリプレイが実行されること。
|
1.0
|
記録の一時停止が含まれるテスト結果に対してリプレイを実行するとエラーになる - リプレイ実行時のダイアログに記録の一時停止前まで実行されると警告文が表示されるが、実際に実行するとエラーとなる。
また、エラーが発生した操作がエラーダイアログに表示されない。
## 期待結果
~~記録の一時停止前まで実行されてエラーなく終了すること。~~
リプレイ実行時のダイアログに、一時停止・再開が含まれるため正常に動作しない可能性がある旨をメッセージとして表示した上で、pause_capturing、resume_capturing行はすべて無視してリプレイが実行されること。
|
non_test
|
記録の一時停止が含まれるテスト結果に対してリプレイを実行するとエラーになる リプレイ実行時のダイアログに記録の一時停止前まで実行されると警告文が表示されるが、実際に実行するとエラーとなる。 また、エラーが発生した操作がエラーダイアログに表示されない。 期待結果 記録の一時停止前まで実行されてエラーなく終了すること。 リプレイ実行時のダイアログに、一時停止・再開が含まれるため正常に動作しない可能性がある旨をメッセージとして表示した上で、pause capturing、resume capturing行はすべて無視してリプレイが実行されること。
| 0
|
261,036
| 22,689,058,399
|
IssuesEvent
|
2022-07-04 17:16:05
|
telosnetwork/open-block-explorer
|
https://api.github.com/repos/telosnetwork/open-block-explorer
|
opened
|
BUG - 'account not found' toast while loading faucet account
|
bug testnet
|
**Describe the bug**
'account not found' toast displays for faucet account
**To Reproduce**
Steps to reproduce the behavior:
1. Go to https://explorer-test.telos.net/account/faucet.tf
2. See 'account not found' toast
**Expected behavior**
toast should not appear (valid account that loads)
**Screenshots**
|
1.0
|
BUG - 'account not found' toast while loading faucet account - **Describe the bug**
'account not found' toast displays for faucet account
**To Reproduce**
Steps to reproduce the behavior:
1. Go to https://explorer-test.telos.net/account/faucet.tf
2. See 'account not found' toast
**Expected behavior**
toast should not appear (valid account that loads)
**Screenshots**
|
test
|
bug account not found toast while loading faucet account describe the bug account not found toast displays for faucet account to reproduce steps to reproduce the behavior go to see account not found toast expected behavior toast should not appear valid account that loads screenshots
| 1
|
321,378
| 27,523,825,018
|
IssuesEvent
|
2023-03-06 16:39:35
|
NYCPlanning/labs-streets
|
https://api.github.com/repos/NYCPlanning/labs-streets
|
closed
|
Add a test for layer order
|
Testing
|
We should add a test to make sure that the map respects config-driven layer ordering. This could be as simple as checking the style object's layers
|
1.0
|
Add a test for layer order - We should add a test to make sure that the map respects config-driven layer ordering. This could be as simple as checking the style object's layers
|
test
|
add a test for layer order we should add a test to make sure that the map respects config driven layer ordering this could be as simple as checking the style object s layers
| 1
|
193,746
| 22,216,316,842
|
IssuesEvent
|
2022-06-08 02:17:44
|
maddyCode23/linux-4.1.15
|
https://api.github.com/repos/maddyCode23/linux-4.1.15
|
reopened
|
CVE-2017-16531 (Medium) detected in linux-stable-rtv4.1.33
|
security vulnerability
|
## CVE-2017-16531 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>
<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/maddyCode23/linux-4.1.15/commit/f1f3d2b150be669390b32dfea28e773471bdd6e7">f1f3d2b150be669390b32dfea28e773471bdd6e7</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
</p>
</details>
<p></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>
drivers/usb/core/config.c in the Linux kernel before 4.13.6 allows local users to cause a denial of service (out-of-bounds read and system crash) or possibly have unspecified other impact via a crafted USB device, related to the USB_DT_INTERFACE_ASSOCIATION descriptor.
<p>Publish Date: 2017-11-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16531>CVE-2017-16531</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Physical
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</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://nvd.nist.gov/vuln/detail/CVE-2017-16531">https://nvd.nist.gov/vuln/detail/CVE-2017-16531</a></p>
<p>Release Date: 2017-11-04</p>
<p>Fix Resolution: 4.13.6</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-2017-16531 (Medium) detected in linux-stable-rtv4.1.33 - ## CVE-2017-16531 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>
<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/maddyCode23/linux-4.1.15/commit/f1f3d2b150be669390b32dfea28e773471bdd6e7">f1f3d2b150be669390b32dfea28e773471bdd6e7</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
</p>
</details>
<p></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>
drivers/usb/core/config.c in the Linux kernel before 4.13.6 allows local users to cause a denial of service (out-of-bounds read and system crash) or possibly have unspecified other impact via a crafted USB device, related to the USB_DT_INTERFACE_ASSOCIATION descriptor.
<p>Publish Date: 2017-11-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16531>CVE-2017-16531</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Physical
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</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://nvd.nist.gov/vuln/detail/CVE-2017-16531">https://nvd.nist.gov/vuln/detail/CVE-2017-16531</a></p>
<p>Release Date: 2017-11-04</p>
<p>Fix Resolution: 4.13.6</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_test
|
cve medium detected in linux stable cve medium severity vulnerability vulnerable library linux stable julia cartwright s fork of linux stable rt git library home page a href found in head commit a href found in base branch master vulnerable source files vulnerability details drivers usb core config c in the linux kernel before allows local users to cause a denial of service out of bounds read and system crash or possibly have unspecified other impact via a crafted usb device related to the usb dt interface association descriptor publish date url a href cvss score details base score metrics exploitability metrics attack vector physical attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource
| 0
|
273,089
| 23,726,463,016
|
IssuesEvent
|
2022-08-30 20:07:02
|
mozilla-mobile/mobile-test-eng
|
https://api.github.com/repos/mozilla-mobile/mobile-test-eng
|
opened
|
Refactor Fenix UI test jobs to ARM from x86
|
android infra:ui-test
|
See #712
We're seeing the speed and stability benefits from the beta ARM emulators on Firebase Test Lab. This ticket will refactor our Flank configurations and the `Jobs` defined in `ui-test.yml` to replace `x86` with `arm`
Move away from `Pixel2` `x86` to `Pixel2.arm` `arm64v8a`
|
1.0
|
Refactor Fenix UI test jobs to ARM from x86 - See #712
We're seeing the speed and stability benefits from the beta ARM emulators on Firebase Test Lab. This ticket will refactor our Flank configurations and the `Jobs` defined in `ui-test.yml` to replace `x86` with `arm`
Move away from `Pixel2` `x86` to `Pixel2.arm` `arm64v8a`
|
test
|
refactor fenix ui test jobs to arm from see we re seeing the speed and stability benefits from the beta arm emulators on firebase test lab this ticket will refactor our flank configurations and the jobs defined in ui test yml to replace with arm move away from to arm
| 1
|
38,461
| 4,957,528,077
|
IssuesEvent
|
2016-12-02 05:07:17
|
hoburg/gpkit
|
https://api.github.com/repos/hoburg/gpkit
|
closed
|
Supporting equality constraints in signomials?
|
design discussion
|
When I try to put an equality constraint in a signomial, I get the following error:
```
TypeError: Iterable ......... contains element 'False' of invalid class <type 'bool'>.
```
Obviously, an easy work around is to add both `<=` and `>=` constraints, but should we not support equality constraints? Sorry if this is something that has already been discussed and decided upon.
Also sidenote: what happened to getting rid of `SignomialsEnabled`?
|
1.0
|
Supporting equality constraints in signomials? - When I try to put an equality constraint in a signomial, I get the following error:
```
TypeError: Iterable ......... contains element 'False' of invalid class <type 'bool'>.
```
Obviously, an easy work around is to add both `<=` and `>=` constraints, but should we not support equality constraints? Sorry if this is something that has already been discussed and decided upon.
Also sidenote: what happened to getting rid of `SignomialsEnabled`?
|
non_test
|
supporting equality constraints in signomials when i try to put an equality constraint in a signomial i get the following error typeerror iterable contains element false of invalid class obviously an easy work around is to add both constraints but should we not support equality constraints sorry if this is something that has already been discussed and decided upon also sidenote what happened to getting rid of signomialsenabled
| 0
|
79,399
| 7,714,451,829
|
IssuesEvent
|
2018-05-23 02:09:18
|
apache/bookkeeper
|
https://api.github.com/repos/apache/bookkeeper
|
closed
|
org.apache.distributedlog.fs.TestDLFileSystem fails on CI
|
area/dlog area/tests release/4.8.0 type/task
|
The tests seems flaky
org.apache.distributedlog.fs.TestDLFileSystem.testBasicIO
Failing for the past 1 build (Since Instabile#40 )
Took 0.88 s.
Error Message
/tmp/testBasicIO (Permission denied)
Stacktrace
java.io.FileNotFoundException: /tmp/testBasicIO (Permission denied)
at org.apache.distributedlog.fs.TestDLFileSystem.testBasicIO(TestDLFileSystem.java:68
|
1.0
|
org.apache.distributedlog.fs.TestDLFileSystem fails on CI - The tests seems flaky
org.apache.distributedlog.fs.TestDLFileSystem.testBasicIO
Failing for the past 1 build (Since Instabile#40 )
Took 0.88 s.
Error Message
/tmp/testBasicIO (Permission denied)
Stacktrace
java.io.FileNotFoundException: /tmp/testBasicIO (Permission denied)
at org.apache.distributedlog.fs.TestDLFileSystem.testBasicIO(TestDLFileSystem.java:68
|
test
|
org apache distributedlog fs testdlfilesystem fails on ci the tests seems flaky org apache distributedlog fs testdlfilesystem testbasicio failing for the past build since instabile took s error message tmp testbasicio permission denied stacktrace java io filenotfoundexception tmp testbasicio permission denied at org apache distributedlog fs testdlfilesystem testbasicio testdlfilesystem java
| 1
|
61,115
| 12,146,574,110
|
IssuesEvent
|
2020-04-24 11:25:28
|
fac19/Week8-BFOP
|
https://api.github.com/repos/fac19/Week8-BFOP
|
closed
|
Reimplementing form validation
|
code review
|
You've written quite a bit of code to implement your own form validation for sign up. This isn't necessarily bad, and it's a good learning exercise, but I wanted to point out that it might be easier to let the browser handle as much of it as possible.
For example the browser will keep track of invalid inputs automatically, so you don't need your own `valid` object. Since you're using a `type="email"` input the browser could tell you if the email is invalid and you could drop the giant regexp etc.
Maybe have a look back at the [validation workshop](https://github.com/oliverjam/learn-form-validation).
You also have some buggy behaviour with your one: the password info disappears as soon as I start typing, and there's no indication that the input is invalid when I try to submit. It just doesn't do anything.
|
1.0
|
Reimplementing form validation - You've written quite a bit of code to implement your own form validation for sign up. This isn't necessarily bad, and it's a good learning exercise, but I wanted to point out that it might be easier to let the browser handle as much of it as possible.
For example the browser will keep track of invalid inputs automatically, so you don't need your own `valid` object. Since you're using a `type="email"` input the browser could tell you if the email is invalid and you could drop the giant regexp etc.
Maybe have a look back at the [validation workshop](https://github.com/oliverjam/learn-form-validation).
You also have some buggy behaviour with your one: the password info disappears as soon as I start typing, and there's no indication that the input is invalid when I try to submit. It just doesn't do anything.
|
non_test
|
reimplementing form validation you ve written quite a bit of code to implement your own form validation for sign up this isn t necessarily bad and it s a good learning exercise but i wanted to point out that it might be easier to let the browser handle as much of it as possible for example the browser will keep track of invalid inputs automatically so you don t need your own valid object since you re using a type email input the browser could tell you if the email is invalid and you could drop the giant regexp etc maybe have a look back at the you also have some buggy behaviour with your one the password info disappears as soon as i start typing and there s no indication that the input is invalid when i try to submit it just doesn t do anything
| 0
|
189,148
| 14,491,094,320
|
IssuesEvent
|
2020-12-11 03:47:37
|
kalexmills/github-vet-tests-dec2020
|
https://api.github.com/repos/kalexmills/github-vet-tests-dec2020
|
closed
|
Bnei-Baruch/jukfs: pkg/blobstore/mergedenum_test.go; 24 LoC
|
fresh small test
|
Found a possible issue in [Bnei-Baruch/jukfs](https://www.github.com/Bnei-Baruch/jukfs) at [pkg/blobstore/mergedenum_test.go](https://github.com/Bnei-Baruch/jukfs/blob/379680d5e2ea6d093d5992d6bd5bea95b6aeb6b8/pkg/blobstore/mergedenum_test.go#L106-L129)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first
issue it finds, so please do not limit your consideration to the contents of the below message.
> range-loop variable tt used in defer or goroutine at line 116
[Click here to see the code in its original context.](https://github.com/Bnei-Baruch/jukfs/blob/379680d5e2ea6d093d5992d6bd5bea95b6aeb6b8/pkg/blobstore/mergedenum_test.go#L106-L129)
<details>
<summary>Click here to show the 24 line(s) of Go which triggered the analyzer.</summary>
```go
for _, tt := range mergedTests {
ctx := context.TODO()
var got []string
ch := make(chan blob.SizedRef)
errc := make(chan error)
limit := tt.limit
if limit == 0 {
limit = 1e9
}
go func() {
errc <- MergedEnumerate(ctx, ch, tt.srcs, tt.after, limit)
}()
for sb := range ch {
got = append(got, sb.Ref.String())
}
if err := <-errc; err != nil {
t.Errorf("%s. MergedEnumerate = %v", tt.name, err)
continue
}
if !reflect.DeepEqual(got, tt.want) {
t.Errorf("%s. different:\n got = %v\nwant = %v", tt.name, got, tt.want)
continue
}
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: 379680d5e2ea6d093d5992d6bd5bea95b6aeb6b8
|
1.0
|
Bnei-Baruch/jukfs: pkg/blobstore/mergedenum_test.go; 24 LoC -
Found a possible issue in [Bnei-Baruch/jukfs](https://www.github.com/Bnei-Baruch/jukfs) at [pkg/blobstore/mergedenum_test.go](https://github.com/Bnei-Baruch/jukfs/blob/379680d5e2ea6d093d5992d6bd5bea95b6aeb6b8/pkg/blobstore/mergedenum_test.go#L106-L129)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first
issue it finds, so please do not limit your consideration to the contents of the below message.
> range-loop variable tt used in defer or goroutine at line 116
[Click here to see the code in its original context.](https://github.com/Bnei-Baruch/jukfs/blob/379680d5e2ea6d093d5992d6bd5bea95b6aeb6b8/pkg/blobstore/mergedenum_test.go#L106-L129)
<details>
<summary>Click here to show the 24 line(s) of Go which triggered the analyzer.</summary>
```go
for _, tt := range mergedTests {
ctx := context.TODO()
var got []string
ch := make(chan blob.SizedRef)
errc := make(chan error)
limit := tt.limit
if limit == 0 {
limit = 1e9
}
go func() {
errc <- MergedEnumerate(ctx, ch, tt.srcs, tt.after, limit)
}()
for sb := range ch {
got = append(got, sb.Ref.String())
}
if err := <-errc; err != nil {
t.Errorf("%s. MergedEnumerate = %v", tt.name, err)
continue
}
if !reflect.DeepEqual(got, tt.want) {
t.Errorf("%s. different:\n got = %v\nwant = %v", tt.name, got, tt.want)
continue
}
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: 379680d5e2ea6d093d5992d6bd5bea95b6aeb6b8
|
test
|
bnei baruch jukfs pkg blobstore mergedenum test go loc found a possible issue in at below is the message reported by the analyzer for this snippet of code beware that the analyzer only reports the first issue it finds so please do not limit your consideration to the contents of the below message range loop variable tt used in defer or goroutine at line click here to show the line s of go which triggered the analyzer go for tt range mergedtests ctx context todo var got string ch make chan blob sizedref errc make chan error limit tt limit if limit limit go func errc mergedenumerate ctx ch tt srcs tt after limit for sb range ch got append got sb ref string if err errc err nil t errorf s mergedenumerate v tt name err continue if reflect deepequal got tt want t errorf s different n got v nwant v tt name got tt want continue leave a reaction on this issue to contribute to the project by classifying this instance as a bug mitigated or desirable behavior rocket see the descriptions of the classifications for more information commit id
| 1
|
134,377
| 10,905,105,228
|
IssuesEvent
|
2019-11-20 10:05:00
|
spring-projects/spring-framework
|
https://api.github.com/repos/spring-projects/spring-framework
|
closed
|
Inconsistent validation of query parameters when using MockMvc
|
in: test in: web status: feedback-provided status: waiting-for-triage
|
**Affects:** `spring-test:5.1.6`
---
When using `MockMvc` to perform test requests of a `@Validated` controller endpoint, validations (javax.validation.constraints) are not applied in certain cases depending on the formatting of the URI.
```java
mockMvc.perform(get("/my-endpoint?param={param}", "value"))... // Works
mockMvc.perform(get(format("/my-endpoint?param=%s", "value")))... // Works
mockMvc.perform(get("/my-endpoint?param=%s", "value"))... // Works, but not when doing validation
mockMvc.perform(get("/my-endpoint?param={}", "value"))... // Works, but not when doing validation
```
Just raising this in case it can be made more consistent or if this might help someone else in the future.
|
1.0
|
Inconsistent validation of query parameters when using MockMvc - **Affects:** `spring-test:5.1.6`
---
When using `MockMvc` to perform test requests of a `@Validated` controller endpoint, validations (javax.validation.constraints) are not applied in certain cases depending on the formatting of the URI.
```java
mockMvc.perform(get("/my-endpoint?param={param}", "value"))... // Works
mockMvc.perform(get(format("/my-endpoint?param=%s", "value")))... // Works
mockMvc.perform(get("/my-endpoint?param=%s", "value"))... // Works, but not when doing validation
mockMvc.perform(get("/my-endpoint?param={}", "value"))... // Works, but not when doing validation
```
Just raising this in case it can be made more consistent or if this might help someone else in the future.
|
test
|
inconsistent validation of query parameters when using mockmvc affects spring test when using mockmvc to perform test requests of a validated controller endpoint validations javax validation constraints are not applied in certain cases depending on the formatting of the uri java mockmvc perform get my endpoint param param value works mockmvc perform get format my endpoint param s value works mockmvc perform get my endpoint param s value works but not when doing validation mockmvc perform get my endpoint param value works but not when doing validation just raising this in case it can be made more consistent or if this might help someone else in the future
| 1
|
392,479
| 11,591,907,959
|
IssuesEvent
|
2020-02-24 10:23:10
|
luna/enso
|
https://api.github.com/repos/luna/enso
|
closed
|
Implement Multiclient Write Lock
|
Category: Tooling Change: Non-Breaking Difficulty: Hard Priority: Medium Type: Enhancement
|
### Summary
It is important for our users that they are able to connect multiple IDE clients to a single running Enso project. This enables a multitude of sharing and collaborative workflows, letting users work seamlessly together from their own machines. While, initially, we only aim to have rudimentary multi-client support. we want to evolve to support collaborative real-time editing in the future, and so the implementation should account for this.
Furthermore, we want to remain compatible with the single-client LSP as we implement this, so care will need to be taken to ensure that we remain compatible while creating an authorisation flow for additional connections.
### Value
We have rudimentary multi-client support in the engine, allowing multiple users to connect to one instance at once. Furthermore, maintiain LSP compatibility.
### Specification
- [ ] Create a concept of the 'write lock'. The engine will only accept `didChange` messages from the client currently holding the write lock.
+ Write lock should be automatically granted to the first client to connect.
+ If any client makes a change without holding the write lock, the change should be denied.
- [ ] Implement the write lock on top of the capabilities system from #464.
+ [ ] Create a capability `canEdit` as specified in the design document.
+ [ ] Use it to prepare for the above behaviour. It cannot be completed as part of this issue as the text functionality does not yet exist.
- [ ] Ensure that the specification document is up to date with respect to any changes to the protocol.
### Acceptance Criteria & Test Cases
- We can support multiple clients connecting to a single engine instance, where only one client is able to write at any given time.
- This functionality is rigorously tested using stub endpoints.
|
1.0
|
Implement Multiclient Write Lock - ### Summary
It is important for our users that they are able to connect multiple IDE clients to a single running Enso project. This enables a multitude of sharing and collaborative workflows, letting users work seamlessly together from their own machines. While, initially, we only aim to have rudimentary multi-client support. we want to evolve to support collaborative real-time editing in the future, and so the implementation should account for this.
Furthermore, we want to remain compatible with the single-client LSP as we implement this, so care will need to be taken to ensure that we remain compatible while creating an authorisation flow for additional connections.
### Value
We have rudimentary multi-client support in the engine, allowing multiple users to connect to one instance at once. Furthermore, maintiain LSP compatibility.
### Specification
- [ ] Create a concept of the 'write lock'. The engine will only accept `didChange` messages from the client currently holding the write lock.
+ Write lock should be automatically granted to the first client to connect.
+ If any client makes a change without holding the write lock, the change should be denied.
- [ ] Implement the write lock on top of the capabilities system from #464.
+ [ ] Create a capability `canEdit` as specified in the design document.
+ [ ] Use it to prepare for the above behaviour. It cannot be completed as part of this issue as the text functionality does not yet exist.
- [ ] Ensure that the specification document is up to date with respect to any changes to the protocol.
### Acceptance Criteria & Test Cases
- We can support multiple clients connecting to a single engine instance, where only one client is able to write at any given time.
- This functionality is rigorously tested using stub endpoints.
|
non_test
|
implement multiclient write lock summary it is important for our users that they are able to connect multiple ide clients to a single running enso project this enables a multitude of sharing and collaborative workflows letting users work seamlessly together from their own machines while initially we only aim to have rudimentary multi client support we want to evolve to support collaborative real time editing in the future and so the implementation should account for this furthermore we want to remain compatible with the single client lsp as we implement this so care will need to be taken to ensure that we remain compatible while creating an authorisation flow for additional connections value we have rudimentary multi client support in the engine allowing multiple users to connect to one instance at once furthermore maintiain lsp compatibility specification create a concept of the write lock the engine will only accept didchange messages from the client currently holding the write lock write lock should be automatically granted to the first client to connect if any client makes a change without holding the write lock the change should be denied implement the write lock on top of the capabilities system from create a capability canedit as specified in the design document use it to prepare for the above behaviour it cannot be completed as part of this issue as the text functionality does not yet exist ensure that the specification document is up to date with respect to any changes to the protocol acceptance criteria test cases we can support multiple clients connecting to a single engine instance where only one client is able to write at any given time this functionality is rigorously tested using stub endpoints
| 0
|
25,532
| 4,161,055,137
|
IssuesEvent
|
2016-06-17 15:20:11
|
phetsims/circuit-construction-kit
|
https://api.github.com/repos/phetsims/circuit-construction-kit
|
closed
|
Deleting components can delete vertices from the black box
|
circuit-construction-kit:black-box-study status:fixed-pending-testing type:bug
|
Black box vertices can be deleted while building a circuit. They will return upon most sim state changes, however. This will happen when deleting an object from such a vertex, only in Build mode and only if nothing else is attached to the vertex. The vertex on the right will be deleted since nothing else is attached to it, the vertex on the right will remain because the battery is attached:
For #126.
|
1.0
|
Deleting components can delete vertices from the black box - Black box vertices can be deleted while building a circuit. They will return upon most sim state changes, however. This will happen when deleting an object from such a vertex, only in Build mode and only if nothing else is attached to the vertex. The vertex on the right will be deleted since nothing else is attached to it, the vertex on the right will remain because the battery is attached:
For #126.
|
test
|
deleting components can delete vertices from the black box black box vertices can be deleted while building a circuit they will return upon most sim state changes however this will happen when deleting an object from such a vertex only in build mode and only if nothing else is attached to the vertex the vertex on the right will be deleted since nothing else is attached to it the vertex on the right will remain because the battery is attached for
| 1
|
70,336
| 7,183,531,136
|
IssuesEvent
|
2018-02-01 13:44:57
|
yogstation13/yogstation-old
|
https://api.github.com/repos/yogstation13/yogstation-old
|
closed
|
(blank)Station
|
Map Requires Testing
|
This is it boys, the grand _**certain project**_ I've been hinting at for some time now. We all love our classic box station, but as yog grows the cramped maint hallways and limited number of supplies can only be crammed into so much space. As of now, with our 50-70 peak player count, box is just way to small, and with meta being the next biggest one up, we're just not at the point to be on such a massive map consistently. So about a month ago I whipped out the ol' sketchpad and started doodling concepts for a completely new station unique to Yog and designed to fit the bill of our player count and community for a more efficient, balanced, and thoroughly enjoyable spessman experience.
I'll get with anyone who wants to take part in this clusterfuck sometime this week and start organizing this blasphemy. It's not going to come quick, but it'll be worth it. As for the issue title, I'm still working on a name for it, all suggestions are welcome. I'll post rough layout pictures sometime this week as well, god willing with school and all. Any and all contributors are going to be mentioned somewhere in the code for the .dmm or even in some hidden z-level of the map so I encourage all forms of participation whether it be here on the git or merging on dream maker.
thanks lads.
|
1.0
|
(blank)Station - This is it boys, the grand _**certain project**_ I've been hinting at for some time now. We all love our classic box station, but as yog grows the cramped maint hallways and limited number of supplies can only be crammed into so much space. As of now, with our 50-70 peak player count, box is just way to small, and with meta being the next biggest one up, we're just not at the point to be on such a massive map consistently. So about a month ago I whipped out the ol' sketchpad and started doodling concepts for a completely new station unique to Yog and designed to fit the bill of our player count and community for a more efficient, balanced, and thoroughly enjoyable spessman experience.
I'll get with anyone who wants to take part in this clusterfuck sometime this week and start organizing this blasphemy. It's not going to come quick, but it'll be worth it. As for the issue title, I'm still working on a name for it, all suggestions are welcome. I'll post rough layout pictures sometime this week as well, god willing with school and all. Any and all contributors are going to be mentioned somewhere in the code for the .dmm or even in some hidden z-level of the map so I encourage all forms of participation whether it be here on the git or merging on dream maker.
thanks lads.
|
test
|
blank station this is it boys the grand certain project i ve been hinting at for some time now we all love our classic box station but as yog grows the cramped maint hallways and limited number of supplies can only be crammed into so much space as of now with our peak player count box is just way to small and with meta being the next biggest one up we re just not at the point to be on such a massive map consistently so about a month ago i whipped out the ol sketchpad and started doodling concepts for a completely new station unique to yog and designed to fit the bill of our player count and community for a more efficient balanced and thoroughly enjoyable spessman experience i ll get with anyone who wants to take part in this clusterfuck sometime this week and start organizing this blasphemy it s not going to come quick but it ll be worth it as for the issue title i m still working on a name for it all suggestions are welcome i ll post rough layout pictures sometime this week as well god willing with school and all any and all contributors are going to be mentioned somewhere in the code for the dmm or even in some hidden z level of the map so i encourage all forms of participation whether it be here on the git or merging on dream maker thanks lads
| 1
|
762,623
| 26,725,682,549
|
IssuesEvent
|
2023-01-29 17:31:36
|
EQAR/eqar_backend
|
https://api.github.com/repos/EQAR/eqar_backend
|
closed
|
Reports: improve facet search
|
enhancement web API high priority
|
Why:
- API users have identified an institution, now want to search the list of programme reports
- improve display of reports in our own web interface
- enhance search functions
Enhancements needed:
- record all institution IDs for which a report should be shown (i.e. hierarchically linked + historically linked when report valid at the time of historical event) as search facets
- allow facet search by multiple values (i.e. passed as array, with OR logic - e.g. reports with low level flag OR no flag, or reports from two or three different agencies - different facets should still combine with AND logic)
- allow two different date-based searches:
- by report date (valid_from), ideally based on date range
- by report being valid on a specified date (range optional)
(I think we have the latter already, but only based on year - exact date would be best.)
|
1.0
|
Reports: improve facet search - Why:
- API users have identified an institution, now want to search the list of programme reports
- improve display of reports in our own web interface
- enhance search functions
Enhancements needed:
- record all institution IDs for which a report should be shown (i.e. hierarchically linked + historically linked when report valid at the time of historical event) as search facets
- allow facet search by multiple values (i.e. passed as array, with OR logic - e.g. reports with low level flag OR no flag, or reports from two or three different agencies - different facets should still combine with AND logic)
- allow two different date-based searches:
- by report date (valid_from), ideally based on date range
- by report being valid on a specified date (range optional)
(I think we have the latter already, but only based on year - exact date would be best.)
|
non_test
|
reports improve facet search why api users have identified an institution now want to search the list of programme reports improve display of reports in our own web interface enhance search functions enhancements needed record all institution ids for which a report should be shown i e hierarchically linked historically linked when report valid at the time of historical event as search facets allow facet search by multiple values i e passed as array with or logic e g reports with low level flag or no flag or reports from two or three different agencies different facets should still combine with and logic allow two different date based searches by report date valid from ideally based on date range by report being valid on a specified date range optional i think we have the latter already but only based on year exact date would be best
| 0
|
550,891
| 16,134,065,025
|
IssuesEvent
|
2021-04-29 09:27:36
|
telstra/open-kilda
|
https://api.github.com/repos/telstra/open-kilda
|
opened
|
the 'round_trip_status' field is not cleared when a link is MOVED
|
bug priority/4-low
|
**Steps to reproduce:**
1. find an RTL link;
2. make sure that `round_trip_status` is `DISCOVERED`;
3. move the link;
4. check `round_trip_status` on the `MOVED` link.
**Expected result:**
`round_trip_status` is not `DISCOVERED`;
**Actual result:**
```
"state": "MOVED",
"actual_state": "MOVED",
"round_trip_status": "DISCOVERED",
```
|
1.0
|
the 'round_trip_status' field is not cleared when a link is MOVED - **Steps to reproduce:**
1. find an RTL link;
2. make sure that `round_trip_status` is `DISCOVERED`;
3. move the link;
4. check `round_trip_status` on the `MOVED` link.
**Expected result:**
`round_trip_status` is not `DISCOVERED`;
**Actual result:**
```
"state": "MOVED",
"actual_state": "MOVED",
"round_trip_status": "DISCOVERED",
```
|
non_test
|
the round trip status field is not cleared when a link is moved steps to reproduce find an rtl link make sure that round trip status is discovered move the link check round trip status on the moved link expected result round trip status is not discovered actual result state moved actual state moved round trip status discovered
| 0
|
144,116
| 11,595,524,933
|
IssuesEvent
|
2020-02-24 17:09:21
|
elastic/kibana
|
https://api.github.com/repos/elastic/kibana
|
closed
|
management scripted fields test failures (2)
|
Feature:Kibana Management Team:KibanaApp failed-test test test-cloud test_ui_functional
|
**✖ fail: "management scripted fields preview should display script results when script is valid"**
│ Error: expected '[{"_id":"3I-1tmIBqAWdAm-tPE6p","myScriptedField":[24322]},{"_id":"3Y-1tmIBqAWdAm-tPE6p","myScriptedField":[18618]},{"_id":"3o-1tmIBqAWdAm-tPE6p","myScriptedField":[9742]},{"_id":"34-1tmIBqAWdAm-tPE6p","myScriptedField":[1268]},{"_id":"4I-1tmIBqAWdAm-tPE6p","myScriptedField":[7622]},{"_id":"4Y-1tmIBqAWdAm-tPE6p","myScriptedField":[9656]},{"_id":"4o-1tmIBqAWdAm-tPE6p","myScriptedField":[16618]},{"_id":"44-1tmIBqAWdAm-tPE6p","myScriptedField":[19196]},{"_id":"5I-1tmIBqAWdAm-tPE6p","myScriptedField":[3444]},{"_id":"5Y-1tmIBqAWdAm-tPE6p","myScriptedField":[18462]}]' to contain '"myScriptedField":[6196'
│ at Assertion.assert (packages/kbn-expect/expect.js:100:11)
│ at Assertion.string.Assertion.contain (packages/kbn-expect/expect.js:415:10)
│ at Context.contain (test/functional/apps/management/_scripted_fields_preview.js:54:51)
│ at process._tickCallback (internal/process/next_tick.js:68:7)
**✖ fail: "management scripted fields preview should display additional fields"**
│ Error: expected '[{"_id":"3I-1tmIBqAWdAm-tPE6p","bytes":12161,"myScriptedField":[24322]},{"_id":"3Y-1tmIBqAWdAm-tPE6p","bytes":9309,"myScriptedField":[18618]},{"_id":"3o-1tmIBqAWdAm-tPE6p","bytes":4871,"myScriptedField":[9742]},{"_id":"34-1tmIBqAWdAm-tPE6p","bytes":634,"myScriptedField":[1268]},{"_id":"4I-1tmIBqAWdAm-tPE6p","bytes":3811,"myScriptedField":[7622]},{"_id":"4Y-1tmIBqAWdAm-tPE6p","bytes":4828,"myScriptedField":[9656]},{"_id":"4o-1tmIBqAWdAm-tPE6p","bytes":8309,"myScriptedField":[16618]},{"_id":"44-1tmIBqAWdAm-tPE6p","bytes":9598,"myScriptedField":[19196]},{"_id":"5I-1tmIBqAWdAm-tPE6p","bytes":1722,"myScriptedField":[3444]},{"_id":"5Y-1tmIBqAWdAm-tPE6p","bytes":9231,"myScriptedField":[18462]}]' to contain '"bytes":3098'
│ at Assertion.assert (packages/kbn-expect/expect.js:100:11)
│ at Assertion.string.Assertion.contain (packages/kbn-expect/expect.js:415:10)
│ at Context.contain (test/functional/apps/management/_scripted_fields_preview.js:59:51)
│ at process._tickCallback (internal/process/next_tick.js:68:7)
**Version: 7.2, 7.1, 6.8**
|
4.0
|
management scripted fields test failures (2) - **✖ fail: "management scripted fields preview should display script results when script is valid"**
│ Error: expected '[{"_id":"3I-1tmIBqAWdAm-tPE6p","myScriptedField":[24322]},{"_id":"3Y-1tmIBqAWdAm-tPE6p","myScriptedField":[18618]},{"_id":"3o-1tmIBqAWdAm-tPE6p","myScriptedField":[9742]},{"_id":"34-1tmIBqAWdAm-tPE6p","myScriptedField":[1268]},{"_id":"4I-1tmIBqAWdAm-tPE6p","myScriptedField":[7622]},{"_id":"4Y-1tmIBqAWdAm-tPE6p","myScriptedField":[9656]},{"_id":"4o-1tmIBqAWdAm-tPE6p","myScriptedField":[16618]},{"_id":"44-1tmIBqAWdAm-tPE6p","myScriptedField":[19196]},{"_id":"5I-1tmIBqAWdAm-tPE6p","myScriptedField":[3444]},{"_id":"5Y-1tmIBqAWdAm-tPE6p","myScriptedField":[18462]}]' to contain '"myScriptedField":[6196'
│ at Assertion.assert (packages/kbn-expect/expect.js:100:11)
│ at Assertion.string.Assertion.contain (packages/kbn-expect/expect.js:415:10)
│ at Context.contain (test/functional/apps/management/_scripted_fields_preview.js:54:51)
│ at process._tickCallback (internal/process/next_tick.js:68:7)
**✖ fail: "management scripted fields preview should display additional fields"**
│ Error: expected '[{"_id":"3I-1tmIBqAWdAm-tPE6p","bytes":12161,"myScriptedField":[24322]},{"_id":"3Y-1tmIBqAWdAm-tPE6p","bytes":9309,"myScriptedField":[18618]},{"_id":"3o-1tmIBqAWdAm-tPE6p","bytes":4871,"myScriptedField":[9742]},{"_id":"34-1tmIBqAWdAm-tPE6p","bytes":634,"myScriptedField":[1268]},{"_id":"4I-1tmIBqAWdAm-tPE6p","bytes":3811,"myScriptedField":[7622]},{"_id":"4Y-1tmIBqAWdAm-tPE6p","bytes":4828,"myScriptedField":[9656]},{"_id":"4o-1tmIBqAWdAm-tPE6p","bytes":8309,"myScriptedField":[16618]},{"_id":"44-1tmIBqAWdAm-tPE6p","bytes":9598,"myScriptedField":[19196]},{"_id":"5I-1tmIBqAWdAm-tPE6p","bytes":1722,"myScriptedField":[3444]},{"_id":"5Y-1tmIBqAWdAm-tPE6p","bytes":9231,"myScriptedField":[18462]}]' to contain '"bytes":3098'
│ at Assertion.assert (packages/kbn-expect/expect.js:100:11)
│ at Assertion.string.Assertion.contain (packages/kbn-expect/expect.js:415:10)
│ at Context.contain (test/functional/apps/management/_scripted_fields_preview.js:59:51)
│ at process._tickCallback (internal/process/next_tick.js:68:7)
**Version: 7.2, 7.1, 6.8**
|
test
|
management scripted fields test failures ✖ fail management scripted fields preview should display script results when script is valid │ error expected id myscriptedfield id myscriptedfield id myscriptedfield id myscriptedfield id myscriptedfield id myscriptedfield id myscriptedfield id myscriptedfield id myscriptedfield to contain myscriptedfield │ at assertion assert packages kbn expect expect js │ at assertion string assertion contain packages kbn expect expect js │ at context contain test functional apps management scripted fields preview js │ at process tickcallback internal process next tick js ✖ fail management scripted fields preview should display additional fields │ error expected id bytes myscriptedfield id bytes myscriptedfield id bytes myscriptedfield id bytes myscriptedfield id bytes myscriptedfield id bytes myscriptedfield id bytes myscriptedfield id bytes myscriptedfield id bytes myscriptedfield to contain bytes │ at assertion assert packages kbn expect expect js │ at assertion string assertion contain packages kbn expect expect js │ at context contain test functional apps management scripted fields preview js │ at process tickcallback internal process next tick js version
| 1
|
6,080
| 2,811,772,132
|
IssuesEvent
|
2015-05-18 01:04:33
|
BVLC/caffe
|
https://api.github.com/repos/BVLC/caffe
|
opened
|
Test and support Python 3
|
Python Python 3 testing
|
Thanks to @philkr and others, pycaffe has been made to work with Python 3. We may as well keep it working and declare our support for it, but we'll need Travis to run `pytest` with Python 3 as well before we can do that.
|
1.0
|
Test and support Python 3 - Thanks to @philkr and others, pycaffe has been made to work with Python 3. We may as well keep it working and declare our support for it, but we'll need Travis to run `pytest` with Python 3 as well before we can do that.
|
test
|
test and support python thanks to philkr and others pycaffe has been made to work with python we may as well keep it working and declare our support for it but we ll need travis to run pytest with python as well before we can do that
| 1
|
274,163
| 23,815,150,255
|
IssuesEvent
|
2022-09-05 05:41:27
|
proarc/proarc
|
https://api.github.com/repos/proarc/proarc
|
closed
|
Hranaté závorky jedním klikem (jádro)
|
Nový klient 7 návrh na zavření 6 k testování Release-3.8
|
Zakládám ještě i tady - je třeba dodělat v jádře vše potřebné, aby mohlo fungovat tohle: https://github.com/proarc/proarc-client/issues/62.
|
1.0
|
Hranaté závorky jedním klikem (jádro) - Zakládám ještě i tady - je třeba dodělat v jádře vše potřebné, aby mohlo fungovat tohle: https://github.com/proarc/proarc-client/issues/62.
|
test
|
hranaté závorky jedním klikem jádro zakládám ještě i tady je třeba dodělat v jádře vše potřebné aby mohlo fungovat tohle
| 1
|
321,745
| 27,551,526,104
|
IssuesEvent
|
2023-03-07 15:13:53
|
godotengine/godot
|
https://api.github.com/repos/godotengine/godot
|
closed
|
First Character of Label Text Gets Drawn in the Middle of the Screen
|
bug topic:rendering needs testing topic:2d
|
### Godot version
Godot Engine v4.0.stable.official.92bee43ad
### System information
Windows 10 Vulkan API 1.2.154 - Forward Mobile - Using Vulkan Device #0: Intel - Intel(R) Iris(R) Plus Graphics 655
### Issue description
This issue happens on an Intel i5-8279U mini-pc. It does not occur on my Ryzen 5 5500U laptop.
Both the Mobile and Forward+ renderers give the same bugged result. The compatibility renderer does not have this issue.
Here is the minimal project and issue in one picture:
It seems that the "A" is drawn at the top left corner based on the location of the root node before the camera view is taken into account, then the rest of the text is drawn at the correct location.
### Steps to reproduce
(Pictured above)
There are no scripts involved. All I did was add the "ACB..." text to the Label and change the font color to red for better visibility, as well as the Godot icon to the Sprite2D. All other parameters are at default values.
The issue does not occur without both the Sprite2D and the Camera2D present in the Player node.
edit: the Player node is not needed. Sprite2D and Camera2D can just be children of Main.
### Minimal reproduction project
[LabelTest.zip](https://github.com/godotengine/godot/files/10910537/LabelTest.zip)
|
1.0
|
First Character of Label Text Gets Drawn in the Middle of the Screen - ### Godot version
Godot Engine v4.0.stable.official.92bee43ad
### System information
Windows 10 Vulkan API 1.2.154 - Forward Mobile - Using Vulkan Device #0: Intel - Intel(R) Iris(R) Plus Graphics 655
### Issue description
This issue happens on an Intel i5-8279U mini-pc. It does not occur on my Ryzen 5 5500U laptop.
Both the Mobile and Forward+ renderers give the same bugged result. The compatibility renderer does not have this issue.
Here is the minimal project and issue in one picture:
It seems that the "A" is drawn at the top left corner based on the location of the root node before the camera view is taken into account, then the rest of the text is drawn at the correct location.
### Steps to reproduce
(Pictured above)
There are no scripts involved. All I did was add the "ACB..." text to the Label and change the font color to red for better visibility, as well as the Godot icon to the Sprite2D. All other parameters are at default values.
The issue does not occur without both the Sprite2D and the Camera2D present in the Player node.
edit: the Player node is not needed. Sprite2D and Camera2D can just be children of Main.
### Minimal reproduction project
[LabelTest.zip](https://github.com/godotengine/godot/files/10910537/LabelTest.zip)
|
test
|
first character of label text gets drawn in the middle of the screen godot version godot engine stable official system information windows vulkan api forward mobile using vulkan device intel intel r iris r plus graphics issue description this issue happens on an intel mini pc it does not occur on my ryzen laptop both the mobile and forward renderers give the same bugged result the compatibility renderer does not have this issue here is the minimal project and issue in one picture it seems that the a is drawn at the top left corner based on the location of the root node before the camera view is taken into account then the rest of the text is drawn at the correct location steps to reproduce pictured above there are no scripts involved all i did was add the acb text to the label and change the font color to red for better visibility as well as the godot icon to the all other parameters are at default values the issue does not occur without both the and the present in the player node edit the player node is not needed and can just be children of main minimal reproduction project
| 1
|
2,659
| 3,797,896,332
|
IssuesEvent
|
2016-03-23 10:09:09
|
beavyHQ/beavy
|
https://api.github.com/repos/beavyHQ/beavy
|
opened
|
[Discussion]: Run installs every time you do vagrant up?
|
enhancement infrastructure question
|
We could have a [provisioner inside](https://www.vagrantup.com/docs/provisioning/basic_usage.html) our vagrant which runs every time you start vagrant (via `vagrant up`). We could add a provisioner, which autmoatically runs `npm install --all` and `python install.py` in `/vagrant` every time, thus allowing to have on command to basically provision the entire setup and not having to wait for `./start.sh` to finish its first round after.
However, this comes with the following drawbacks: whether you want to or not, this would always try to update these modules. That could cost time and with us still running installs in `start.sh`, actually means the setup takes a bit longer (as npm install is very connection intensive and slow in figuring out, everything is up to date). Secondly, this would fail if you don't have a `config.yml` because python install depends on that. And lastly would delay the time before vagrant is up in the first place.
Not sure about this. Thoughts?
|
1.0
|
[Discussion]: Run installs every time you do vagrant up? - We could have a [provisioner inside](https://www.vagrantup.com/docs/provisioning/basic_usage.html) our vagrant which runs every time you start vagrant (via `vagrant up`). We could add a provisioner, which autmoatically runs `npm install --all` and `python install.py` in `/vagrant` every time, thus allowing to have on command to basically provision the entire setup and not having to wait for `./start.sh` to finish its first round after.
However, this comes with the following drawbacks: whether you want to or not, this would always try to update these modules. That could cost time and with us still running installs in `start.sh`, actually means the setup takes a bit longer (as npm install is very connection intensive and slow in figuring out, everything is up to date). Secondly, this would fail if you don't have a `config.yml` because python install depends on that. And lastly would delay the time before vagrant is up in the first place.
Not sure about this. Thoughts?
|
non_test
|
run installs every time you do vagrant up we could have a our vagrant which runs every time you start vagrant via vagrant up we could add a provisioner which autmoatically runs npm install all and python install py in vagrant every time thus allowing to have on command to basically provision the entire setup and not having to wait for start sh to finish its first round after however this comes with the following drawbacks whether you want to or not this would always try to update these modules that could cost time and with us still running installs in start sh actually means the setup takes a bit longer as npm install is very connection intensive and slow in figuring out everything is up to date secondly this would fail if you don t have a config yml because python install depends on that and lastly would delay the time before vagrant is up in the first place not sure about this thoughts
| 0
|
20,223
| 28,807,869,368
|
IssuesEvent
|
2023-05-03 00:17:32
|
iPortalTeam/ImmersivePortalsMod
|
https://api.github.com/repos/iPortalTeam/ImmersivePortalsMod
|
closed
|
incompatible with optifine g8
|
Mod Compatibility won't fix
|
plz help the mod isnt compatible with optifine hd g8
it just crashes with a blank error
heres the crash log
[crash-2021-11-25_17.44.10-client.txt](https://github.com/qouteall/ImmersivePortalsMod/files/7610872/crash-2021-11-25_17.44.10-client.txt)
|
True
|
incompatible with optifine g8 - plz help the mod isnt compatible with optifine hd g8
it just crashes with a blank error
heres the crash log
[crash-2021-11-25_17.44.10-client.txt](https://github.com/qouteall/ImmersivePortalsMod/files/7610872/crash-2021-11-25_17.44.10-client.txt)
|
non_test
|
incompatible with optifine plz help the mod isnt compatible with optifine hd it just crashes with a blank error heres the crash log
| 0
|
13,699
| 16,456,105,817
|
IssuesEvent
|
2021-05-21 12:48:05
|
googleapis/python-securitycenter
|
https://api.github.com/repos/googleapis/python-securitycenter
|
closed
|
Release as GA
|
api: securitycenter type: process
|
[GA release template](https://github.com/googleapis/google-cloud-common/issues/287)
## Required
- [x] 28 days elapsed since last beta release with new API surface **RELEASE ON/AFTER: April 1 2021**
- [x] Server API is GA
- [x] Package API is stable, and we can commit to backward compatibility
- [x] All dependencies are GA
|
1.0
|
Release as GA - [GA release template](https://github.com/googleapis/google-cloud-common/issues/287)
## Required
- [x] 28 days elapsed since last beta release with new API surface **RELEASE ON/AFTER: April 1 2021**
- [x] Server API is GA
- [x] Package API is stable, and we can commit to backward compatibility
- [x] All dependencies are GA
|
non_test
|
release as ga required days elapsed since last beta release with new api surface release on after april server api is ga package api is stable and we can commit to backward compatibility all dependencies are ga
| 0
|
60,551
| 6,705,882,252
|
IssuesEvent
|
2017-10-12 03:16:24
|
IF977/WhereIGo
|
https://api.github.com/repos/IF977/WhereIGo
|
opened
|
[2-1] Testes de avaliação de estabelecimento
|
testes
|
Itens a serem realizados:
- Criar testes de avaliação de estabelecimento com Rspec/Cucumber
|
1.0
|
[2-1] Testes de avaliação de estabelecimento - Itens a serem realizados:
- Criar testes de avaliação de estabelecimento com Rspec/Cucumber
|
test
|
testes de avaliação de estabelecimento itens a serem realizados criar testes de avaliação de estabelecimento com rspec cucumber
| 1
|
183,988
| 14,265,964,590
|
IssuesEvent
|
2020-11-20 17:56:15
|
tarantool/tarantool
|
https://api.github.com/repos/tarantool/tarantool
|
closed
|
test: flaky unit/swim.test test
|
flaky test qa
|
Tarantool version:
Tarantool 2.6.0-142-g6a47a75e97
Target: Linux-x86_64-RelWithDebInfo
Build options: cmake . -DCMAKE_INSTALL_PREFIX=/usr/local -DENABLE_BACKTRACE=ON
Compiler: /usr/bin/cc /usr/bin/c++
C_FLAGS: -fexceptions -funwind-tables -fno-omit-frame-pointer -fno-stack-protector -fno-common -fopenmp -msse2 -std=c11 -Wall -Wextra -Wno-strict-aliasing -Wno-char-subscripts -Wno-format-truncation -Wno-gnu-alignof-expression -fno-gnu89-inline -Wno-cast-function-type -Werror
CXX_FLAGS: -fexceptions -funwind-tables -fno-omit-frame-pointer -fno-stack-protector -fno-common -fopenmp -msse2 -std=c++11 -Wall -Wextra -Wno-strict-aliasing -Wno-char-subscripts -Wno-format-truncation -Wno-invalid-offsetof -Wno-gnu-alignof-expression -Wno-cast-function-type -Werror
OS version:
Linux (Debian *)
Bug description:
https://gitlab.com/tarantool/tarantool/-/jobs/771421662#L4457
https://gitlab.com/tarantool/tarantool/-/jobs/771888996#L4058
https://gitlab.com/tarantool/tarantool/-/jobs/822238802#L3007
[artifacts.zip](https://github.com/tarantool/tarantool/files/5352985/artifacts.zip)
Checksum of the results file is not usable due to changing data in results.
```
[081] --- unit/swim.result Fri Oct 2 12:54:07 2020
[081] +++ unit/swim.reject Sun Oct 4 02:51:30 2020
[081] @@ -115,7 +115,12 @@
[081] ok 2 - but it is never deleted due to the cfg option
[081] ok 11 - subtests
[081] *** swim_test_undead: done ***
[081] - *** swim_test_packet_loss ***
[081] + *** swim_tes # Failed test 'S1 is still alive everywhere'
[081] + # in /builds/M4RrgQZ3/0/tarantool/tarantool/test/unit/swim.c at line 753
[081] + # Looks like you failed 1 test of 2 run.
[081] +# Failed test 'subtests'
[081] +# in /builds/M4RrgQZ3/0/tarantool/tarantool/test/unit/unit.c at line 54
[081] +t_packet_loss ***
[081] 1..5
[081] ok 1 - drop rate = 5.00, but the failure is disseminated
[081] ok 2 - drop rate = 10.00, but the failure is disseminated
[081] @@ -171,9 +176,9 @@
[081] *** swim_test_payload_basic: done ***
[081] *** swim_test_indirect_ping ***
[081] 1..2
[081] - ok 1 - S1 is still alive everywhere
[081] + not ok 1 - S1 is still alive everywhere
[081] ok 2 - as well as S2 - they communicated via S3
[081] -ok 17 - subtests
[081] +not ok 17 - subtests
[081] *** swim_test_indirect_ping: done ***
[081] *** swim_test_encryption ***
[081] 1..3
[081] @@ -221,7 +226,8 @@
[081] *** swim_test_generation: done ***
[081] *** swim_test_dissemination_speed ***
[081] 1..2
[081] - ok 1 - dissemination work in log time even at the very start of a cluster
[081] + # Looks like you failed 1 test of 23 run.
[081] +ok 1 - dissemination work in log time even at the very start of a cluster
[081] ok 2 - dissemination can withstand an event storm
[081] ok 22 - subtests
[081] *** swim_test_dissemination_speed: done ***
```
Steps to reproduce:
Optional (but very desirable):
* coredump
* backtrace
* netstat
|
1.0
|
test: flaky unit/swim.test test - Tarantool version:
Tarantool 2.6.0-142-g6a47a75e97
Target: Linux-x86_64-RelWithDebInfo
Build options: cmake . -DCMAKE_INSTALL_PREFIX=/usr/local -DENABLE_BACKTRACE=ON
Compiler: /usr/bin/cc /usr/bin/c++
C_FLAGS: -fexceptions -funwind-tables -fno-omit-frame-pointer -fno-stack-protector -fno-common -fopenmp -msse2 -std=c11 -Wall -Wextra -Wno-strict-aliasing -Wno-char-subscripts -Wno-format-truncation -Wno-gnu-alignof-expression -fno-gnu89-inline -Wno-cast-function-type -Werror
CXX_FLAGS: -fexceptions -funwind-tables -fno-omit-frame-pointer -fno-stack-protector -fno-common -fopenmp -msse2 -std=c++11 -Wall -Wextra -Wno-strict-aliasing -Wno-char-subscripts -Wno-format-truncation -Wno-invalid-offsetof -Wno-gnu-alignof-expression -Wno-cast-function-type -Werror
OS version:
Linux (Debian *)
Bug description:
https://gitlab.com/tarantool/tarantool/-/jobs/771421662#L4457
https://gitlab.com/tarantool/tarantool/-/jobs/771888996#L4058
https://gitlab.com/tarantool/tarantool/-/jobs/822238802#L3007
[artifacts.zip](https://github.com/tarantool/tarantool/files/5352985/artifacts.zip)
Checksum of the results file is not usable due to changing data in results.
```
[081] --- unit/swim.result Fri Oct 2 12:54:07 2020
[081] +++ unit/swim.reject Sun Oct 4 02:51:30 2020
[081] @@ -115,7 +115,12 @@
[081] ok 2 - but it is never deleted due to the cfg option
[081] ok 11 - subtests
[081] *** swim_test_undead: done ***
[081] - *** swim_test_packet_loss ***
[081] + *** swim_tes # Failed test 'S1 is still alive everywhere'
[081] + # in /builds/M4RrgQZ3/0/tarantool/tarantool/test/unit/swim.c at line 753
[081] + # Looks like you failed 1 test of 2 run.
[081] +# Failed test 'subtests'
[081] +# in /builds/M4RrgQZ3/0/tarantool/tarantool/test/unit/unit.c at line 54
[081] +t_packet_loss ***
[081] 1..5
[081] ok 1 - drop rate = 5.00, but the failure is disseminated
[081] ok 2 - drop rate = 10.00, but the failure is disseminated
[081] @@ -171,9 +176,9 @@
[081] *** swim_test_payload_basic: done ***
[081] *** swim_test_indirect_ping ***
[081] 1..2
[081] - ok 1 - S1 is still alive everywhere
[081] + not ok 1 - S1 is still alive everywhere
[081] ok 2 - as well as S2 - they communicated via S3
[081] -ok 17 - subtests
[081] +not ok 17 - subtests
[081] *** swim_test_indirect_ping: done ***
[081] *** swim_test_encryption ***
[081] 1..3
[081] @@ -221,7 +226,8 @@
[081] *** swim_test_generation: done ***
[081] *** swim_test_dissemination_speed ***
[081] 1..2
[081] - ok 1 - dissemination work in log time even at the very start of a cluster
[081] + # Looks like you failed 1 test of 23 run.
[081] +ok 1 - dissemination work in log time even at the very start of a cluster
[081] ok 2 - dissemination can withstand an event storm
[081] ok 22 - subtests
[081] *** swim_test_dissemination_speed: done ***
```
Steps to reproduce:
Optional (but very desirable):
* coredump
* backtrace
* netstat
|
test
|
test flaky unit swim test test tarantool version tarantool target linux relwithdebinfo build options cmake dcmake install prefix usr local denable backtrace on compiler usr bin cc usr bin c c flags fexceptions funwind tables fno omit frame pointer fno stack protector fno common fopenmp std wall wextra wno strict aliasing wno char subscripts wno format truncation wno gnu alignof expression fno inline wno cast function type werror cxx flags fexceptions funwind tables fno omit frame pointer fno stack protector fno common fopenmp std c wall wextra wno strict aliasing wno char subscripts wno format truncation wno invalid offsetof wno gnu alignof expression wno cast function type werror os version linux debian bug description checksum of the results file is not usable due to changing data in results unit swim result fri oct unit swim reject sun oct ok but it is never deleted due to the cfg option ok subtests swim test undead done swim test packet loss swim tes failed test is still alive everywhere in builds tarantool tarantool test unit swim c at line looks like you failed test of run failed test subtests in builds tarantool tarantool test unit unit c at line t packet loss ok drop rate but the failure is disseminated ok drop rate but the failure is disseminated swim test payload basic done swim test indirect ping ok is still alive everywhere not ok is still alive everywhere ok as well as they communicated via ok subtests not ok subtests swim test indirect ping done swim test encryption swim test generation done swim test dissemination speed ok dissemination work in log time even at the very start of a cluster looks like you failed test of run ok dissemination work in log time even at the very start of a cluster ok dissemination can withstand an event storm ok subtests swim test dissemination speed done steps to reproduce optional but very desirable coredump backtrace netstat
| 1
|
3,052
| 3,778,670,485
|
IssuesEvent
|
2016-03-18 02:12:46
|
ecreatorsau/status
|
https://api.github.com/repos/ecreatorsau/status
|
closed
|
Connectivity Issues
|
degraded performance Moodle Hosting
|
Between 2:15 PM PDT and 3:40 PM PDT we experienced an Internet connectivity issue due to an impairment within Telstra's network which affected traffic from some end-user networks and the AP-SOUTHEAST-2 Region. Connectivity to instances and services within the Region was not impacted by the event. The issue has been resolved and connectivity has been restored.
|
True
|
Connectivity Issues - Between 2:15 PM PDT and 3:40 PM PDT we experienced an Internet connectivity issue due to an impairment within Telstra's network which affected traffic from some end-user networks and the AP-SOUTHEAST-2 Region. Connectivity to instances and services within the Region was not impacted by the event. The issue has been resolved and connectivity has been restored.
|
non_test
|
connectivity issues between pm pdt and pm pdt we experienced an internet connectivity issue due to an impairment within telstra s network which affected traffic from some end user networks and the ap southeast region connectivity to instances and services within the region was not impacted by the event the issue has been resolved and connectivity has been restored
| 0
|
176,336
| 21,408,247,842
|
IssuesEvent
|
2022-04-22 00:51:55
|
thor-it/thor-sso
|
https://api.github.com/repos/thor-it/thor-sso
|
closed
|
ng.theme.shared-4.0.2.tgz: 1 vulnerabilities (highest severity is: 7.5) - autoclosed
|
security vulnerability
|
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ng.theme.shared-4.0.2.tgz</b></p></summary>
<p></p>
<p>Path to dependency file: /angular/package.json</p>
<p>Path to vulnerable library: /angular/node_modules/moment/package.json</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/thor-it/thor-sso/commit/2e5128b82914ee6f0021bd2c18fef7b5c70d6088">2e5128b82914ee6f0021bd2c18fef7b5c70d6088</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2022-24785](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-24785) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | moment-2.29.1.tgz | Transitive | 5.0.0-beta.1 | ❌ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-24785</summary>
### Vulnerable Library - <b>moment-2.29.1.tgz</b></p>
<p>Parse, validate, manipulate, and display dates</p>
<p>Library home page: <a href="https://registry.npmjs.org/moment/-/moment-2.29.1.tgz">https://registry.npmjs.org/moment/-/moment-2.29.1.tgz</a></p>
<p>Path to dependency file: /angular/package.json</p>
<p>Path to vulnerable library: /angular/node_modules/moment/package.json</p>
<p>
Dependency Hierarchy:
- ng.theme.shared-4.0.2.tgz (Root Library)
- chart.js-2.9.4.tgz
- :x: **moment-2.29.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/thor-it/thor-sso/commit/2e5128b82914ee6f0021bd2c18fef7b5c70d6088">2e5128b82914ee6f0021bd2c18fef7b5c70d6088</a></p>
<p>Found in base branch: <b>develop</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Moment.js is a JavaScript date library for parsing, validating, manipulating, and formatting dates. A path traversal vulnerability impacts npm (server) users of Moment.js between versions 1.0.1 and 2.29.1, especially if a user-provided locale string is directly used to switch moment locale. This problem is patched in 2.29.2, and the patch can be applied to all affected versions. As a workaround, sanitize the user-provided locale name before passing it to Moment.js.
<p>Publish Date: 2022-04-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-24785>CVE-2022-24785</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/moment/moment/security/advisories/GHSA-8hfj-j24r-96c4">https://github.com/moment/moment/security/advisories/GHSA-8hfj-j24r-96c4</a></p>
<p>Release Date: 2022-04-04</p>
<p>Fix Resolution (moment): 2.29.2</p>
<p>Direct dependency fix Resolution (@abp/ng.theme.shared): 5.0.0-beta.1</p>
</p>
<p></p>
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details>
<!-- <REMEDIATE>[{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"@abp/ng.theme.shared","packageVersion":"4.0.2","packageFilePaths":["/angular/package.json"],"isTransitiveDependency":false,"dependencyTree":"@abp/ng.theme.shared:4.0.2","isMinimumFixVersionAvailable":true,"minimumFixVersion":"5.0.0-beta.1","isBinary":false}],"baseBranches":["develop"],"vulnerabilityIdentifier":"CVE-2022-24785","vulnerabilityDetails":"Moment.js is a JavaScript date library for parsing, validating, manipulating, and formatting dates. A path traversal vulnerability impacts npm (server) users of Moment.js between versions 1.0.1 and 2.29.1, especially if a user-provided locale string is directly used to switch moment locale. This problem is patched in 2.29.2, and the patch can be applied to all affected versions. As a workaround, sanitize the user-provided locale name before passing it to Moment.js.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-24785","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"High"},"extraData":{}}]</REMEDIATE> -->
|
True
|
ng.theme.shared-4.0.2.tgz: 1 vulnerabilities (highest severity is: 7.5) - autoclosed - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ng.theme.shared-4.0.2.tgz</b></p></summary>
<p></p>
<p>Path to dependency file: /angular/package.json</p>
<p>Path to vulnerable library: /angular/node_modules/moment/package.json</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/thor-it/thor-sso/commit/2e5128b82914ee6f0021bd2c18fef7b5c70d6088">2e5128b82914ee6f0021bd2c18fef7b5c70d6088</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2022-24785](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-24785) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | moment-2.29.1.tgz | Transitive | 5.0.0-beta.1 | ❌ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-24785</summary>
### Vulnerable Library - <b>moment-2.29.1.tgz</b></p>
<p>Parse, validate, manipulate, and display dates</p>
<p>Library home page: <a href="https://registry.npmjs.org/moment/-/moment-2.29.1.tgz">https://registry.npmjs.org/moment/-/moment-2.29.1.tgz</a></p>
<p>Path to dependency file: /angular/package.json</p>
<p>Path to vulnerable library: /angular/node_modules/moment/package.json</p>
<p>
Dependency Hierarchy:
- ng.theme.shared-4.0.2.tgz (Root Library)
- chart.js-2.9.4.tgz
- :x: **moment-2.29.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/thor-it/thor-sso/commit/2e5128b82914ee6f0021bd2c18fef7b5c70d6088">2e5128b82914ee6f0021bd2c18fef7b5c70d6088</a></p>
<p>Found in base branch: <b>develop</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Moment.js is a JavaScript date library for parsing, validating, manipulating, and formatting dates. A path traversal vulnerability impacts npm (server) users of Moment.js between versions 1.0.1 and 2.29.1, especially if a user-provided locale string is directly used to switch moment locale. This problem is patched in 2.29.2, and the patch can be applied to all affected versions. As a workaround, sanitize the user-provided locale name before passing it to Moment.js.
<p>Publish Date: 2022-04-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-24785>CVE-2022-24785</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/moment/moment/security/advisories/GHSA-8hfj-j24r-96c4">https://github.com/moment/moment/security/advisories/GHSA-8hfj-j24r-96c4</a></p>
<p>Release Date: 2022-04-04</p>
<p>Fix Resolution (moment): 2.29.2</p>
<p>Direct dependency fix Resolution (@abp/ng.theme.shared): 5.0.0-beta.1</p>
</p>
<p></p>
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details>
<!-- <REMEDIATE>[{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"@abp/ng.theme.shared","packageVersion":"4.0.2","packageFilePaths":["/angular/package.json"],"isTransitiveDependency":false,"dependencyTree":"@abp/ng.theme.shared:4.0.2","isMinimumFixVersionAvailable":true,"minimumFixVersion":"5.0.0-beta.1","isBinary":false}],"baseBranches":["develop"],"vulnerabilityIdentifier":"CVE-2022-24785","vulnerabilityDetails":"Moment.js is a JavaScript date library for parsing, validating, manipulating, and formatting dates. A path traversal vulnerability impacts npm (server) users of Moment.js between versions 1.0.1 and 2.29.1, especially if a user-provided locale string is directly used to switch moment locale. This problem is patched in 2.29.2, and the patch can be applied to all affected versions. As a workaround, sanitize the user-provided locale name before passing it to Moment.js.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-24785","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"High"},"extraData":{}}]</REMEDIATE> -->
|
non_test
|
ng theme shared tgz vulnerabilities highest severity is autoclosed vulnerable library ng theme shared tgz path to dependency file angular package json path to vulnerable library angular node modules moment package json found in head commit a href vulnerabilities cve severity cvss dependency type fixed in remediation available high moment tgz transitive beta details cve vulnerable library moment tgz parse validate manipulate and display dates library home page a href path to dependency file angular package json path to vulnerable library angular node modules moment package json dependency hierarchy ng theme shared tgz root library chart js tgz x moment tgz vulnerable library found in head commit a href found in base branch develop vulnerability details moment js is a javascript date library for parsing validating manipulating and formatting dates a path traversal vulnerability impacts npm server users of moment js between versions and especially if a user provided locale string is directly used to switch moment locale this problem is patched in and the patch can be applied to all affected versions as a workaround sanitize the user provided locale name before passing it to moment js 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 high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution moment direct dependency fix resolution abp ng theme shared beta step up your open source security game with whitesource istransitivedependency false dependencytree abp ng theme shared isminimumfixversionavailable true minimumfixversion beta isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails moment js is a javascript date library for parsing validating manipulating and formatting dates a path traversal vulnerability impacts npm server users of moment js between versions and especially if a user provided locale string is directly used to switch moment locale this problem is patched in and the patch can be applied to all affected versions as a workaround sanitize the user provided locale name before passing it to moment js vulnerabilityurl
| 0
|
166,970
| 6,329,580,892
|
IssuesEvent
|
2017-07-26 03:37:40
|
tunga-io/tunga-web
|
https://api.github.com/repos/tunga-io/tunga-web
|
closed
|
Developer rating enhancement
|
enhancement feature High priority Must have reviewing This week
|
<!--
PLEASE HELP US PROCESS GITHUB ISSUES FASTER BY PROVIDING THE FOLLOWING INFORMATION.
-->
## I'm submitting a ...
<!-- Check one of the following options with "x" and add the appropriate label to the issue as well -->
<pre><code>
[ ] Bug report <!-- Please search this repo for a similar issue or PR before submitting -->
[X] Feature request
[ ] Regression (behavior that used to work and stopped working in a new release)
</code></pre>
## Current behavior
<!-- Describe how the issue manifests. -->
The architecture for rating developers is in place. However, we still expect clients to go over it manually, as in: they go the platform and leave a rating behind.
## Expected behavior
<!-- Describe what the desired behavior would be. -->
As soon as a task is finished and payment is being finalized, I'd like a pop up to appear with to the profile of the the developer on the left and an easy rating system on the right. The rating system consists of a rating option as we know it: from 1 to 5 stars. Below this is a small text field where a client can choose (so this is optional, not mandatory) to leave a few comments behind.
The text above the star rating should be: How would you rate this developer?
The text above the text field should: Is there anything you would like to say about the developer?
## Minimal instructions for reproducing the problem (optional for feature requests)
<!--
For bug reports please provide the *STEPS TO REPRODUCE* and if possible a *MINIMAL DEMO* of the problem via
https://plnkr.co or similar.
-->
## What is the motivation / use case for changing the behavior?
<!-- Describe the motivation or the concrete use case. -->
## Please tell us about your environment (optional for feature requests)
<pre><code>
Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
- [ ] Other version XX <!-- Replace Other with name of browser -->
Operating System:
- [ ] macOS version XX
- [ ] Windows version XX
- [ ] Linux <!-- Add flavor name here --> XX
- [ ] Android version XX
- [ ] iOS version XX
- [ ] Windows Phone version XX
- [ ] Other version XX <!-- Replace Other with name of OS -->
Environment/ Server:
- [ ] Production
- [ ] Staging
- [ ] Test
- [ ] Development
<!-- If possible, check whether this is still an issue on the test server first -->
For Developer issues:
- Node version: XX <!-- use `node --version` -->
- Platform: <!-- Mac, Linux, Windows -->
Others:
<!-- Anything else relevant? Operating system version, IDE, package manager, HTTP server, ... -->
</code></pre>
|
1.0
|
Developer rating enhancement - <!--
PLEASE HELP US PROCESS GITHUB ISSUES FASTER BY PROVIDING THE FOLLOWING INFORMATION.
-->
## I'm submitting a ...
<!-- Check one of the following options with "x" and add the appropriate label to the issue as well -->
<pre><code>
[ ] Bug report <!-- Please search this repo for a similar issue or PR before submitting -->
[X] Feature request
[ ] Regression (behavior that used to work and stopped working in a new release)
</code></pre>
## Current behavior
<!-- Describe how the issue manifests. -->
The architecture for rating developers is in place. However, we still expect clients to go over it manually, as in: they go the platform and leave a rating behind.
## Expected behavior
<!-- Describe what the desired behavior would be. -->
As soon as a task is finished and payment is being finalized, I'd like a pop up to appear with to the profile of the the developer on the left and an easy rating system on the right. The rating system consists of a rating option as we know it: from 1 to 5 stars. Below this is a small text field where a client can choose (so this is optional, not mandatory) to leave a few comments behind.
The text above the star rating should be: How would you rate this developer?
The text above the text field should: Is there anything you would like to say about the developer?
## Minimal instructions for reproducing the problem (optional for feature requests)
<!--
For bug reports please provide the *STEPS TO REPRODUCE* and if possible a *MINIMAL DEMO* of the problem via
https://plnkr.co or similar.
-->
## What is the motivation / use case for changing the behavior?
<!-- Describe the motivation or the concrete use case. -->
## Please tell us about your environment (optional for feature requests)
<pre><code>
Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
- [ ] Other version XX <!-- Replace Other with name of browser -->
Operating System:
- [ ] macOS version XX
- [ ] Windows version XX
- [ ] Linux <!-- Add flavor name here --> XX
- [ ] Android version XX
- [ ] iOS version XX
- [ ] Windows Phone version XX
- [ ] Other version XX <!-- Replace Other with name of OS -->
Environment/ Server:
- [ ] Production
- [ ] Staging
- [ ] Test
- [ ] Development
<!-- If possible, check whether this is still an issue on the test server first -->
For Developer issues:
- Node version: XX <!-- use `node --version` -->
- Platform: <!-- Mac, Linux, Windows -->
Others:
<!-- Anything else relevant? Operating system version, IDE, package manager, HTTP server, ... -->
</code></pre>
|
non_test
|
developer rating enhancement please help us process github issues faster by providing the following information i m submitting a bug report feature request regression behavior that used to work and stopped working in a new release current behavior the architecture for rating developers is in place however we still expect clients to go over it manually as in they go the platform and leave a rating behind expected behavior as soon as a task is finished and payment is being finalized i d like a pop up to appear with to the profile of the the developer on the left and an easy rating system on the right the rating system consists of a rating option as we know it from to stars below this is a small text field where a client can choose so this is optional not mandatory to leave a few comments behind the text above the star rating should be how would you rate this developer the text above the text field should is there anything you would like to say about the developer minimal instructions for reproducing the problem optional for feature requests for bug reports please provide the steps to reproduce and if possible a minimal demo of the problem via or similar what is the motivation use case for changing the behavior please tell us about your environment optional for feature requests browser chrome desktop version xx chrome android version xx chrome ios version xx firefox version xx safari desktop version xx safari ios version xx ie version xx edge version xx other version xx operating system macos version xx windows version xx linux xx android version xx ios version xx windows phone version xx other version xx environment server production staging test development for developer issues node version xx platform others
| 0
|
15,551
| 3,475,274,549
|
IssuesEvent
|
2015-12-25 12:58:54
|
FedericoElles/KazokuNabi
|
https://api.github.com/repos/FedericoElles/KazokuNabi
|
closed
|
OnPause, OnResume GPS fix
|
test
|
In Android, GPS is still obtained by webview if app goes to background.
javascript:window._onPause();
javascript:window._onResume();
|
1.0
|
OnPause, OnResume GPS fix - In Android, GPS is still obtained by webview if app goes to background.
javascript:window._onPause();
javascript:window._onResume();
|
test
|
onpause onresume gps fix in android gps is still obtained by webview if app goes to background javascript window onpause javascript window onresume
| 1
|
139,596
| 11,274,498,761
|
IssuesEvent
|
2020-01-14 18:42:10
|
aliasrobotics/RVD
|
https://api.github.com/repos/aliasrobotics/RVD
|
opened
|
(error) Resource leak
|
bug cppcheck static analysis testing triage
|
```yaml
{
"id": 1,
"cve": "None",
"description": "[src/industrial_calibration/intrinsic_cal/src/ical_srv.cpp:441]: (error) Resource leak: fp",
"system": "src/industrial_calibration/intrinsic_cal/src/ical_srv.cpp",
"title": "(error) Resource leak",
"severity": {
"severity-description": "",
"cvss-score": 0,
"rvss-vector": "",
"rvss-score": 0,
"cvss-vector": ""
},
"vendor": null,
"exploitation": {
"exploitation-image": "",
"exploitation-vector": "",
"description": ""
},
"type": "bug",
"mitigation": {
"date-mitigation": "",
"pull-request": "",
"description": ""
},
"links": "",
"keywords": [
"cppcheck",
"static analysis",
"testing",
"triage",
"bug"
],
"cwe": "None",
"flaw": {
"application": "N/A",
"phase": "testing",
"languages": "None",
"reproduction": "See artifacts below (if available)",
"specificity": "N/A",
"date-detected": "2020-01-14 (18:42)",
"architectural-location": "N/A",
"subsystem": "N/A",
"reproduction-image": "gitlab.com/aliasrobotics/offensive/alurity/pipelines/active/pipeline_ros_industrial/-/jobs/402982901/artifacts/download",
"date-reported": "2020-01-14 (18:42)",
"reproducibility": "always",
"detected-by-method": "testing static",
"reported-by-relationship": "automatic",
"trace": "",
"reported-by": "Alias Robotics",
"issue": "",
"package": "N/A",
"detected-by": "Alias Robotics"
}
}
```
|
1.0
|
(error) Resource leak - ```yaml
{
"id": 1,
"cve": "None",
"description": "[src/industrial_calibration/intrinsic_cal/src/ical_srv.cpp:441]: (error) Resource leak: fp",
"system": "src/industrial_calibration/intrinsic_cal/src/ical_srv.cpp",
"title": "(error) Resource leak",
"severity": {
"severity-description": "",
"cvss-score": 0,
"rvss-vector": "",
"rvss-score": 0,
"cvss-vector": ""
},
"vendor": null,
"exploitation": {
"exploitation-image": "",
"exploitation-vector": "",
"description": ""
},
"type": "bug",
"mitigation": {
"date-mitigation": "",
"pull-request": "",
"description": ""
},
"links": "",
"keywords": [
"cppcheck",
"static analysis",
"testing",
"triage",
"bug"
],
"cwe": "None",
"flaw": {
"application": "N/A",
"phase": "testing",
"languages": "None",
"reproduction": "See artifacts below (if available)",
"specificity": "N/A",
"date-detected": "2020-01-14 (18:42)",
"architectural-location": "N/A",
"subsystem": "N/A",
"reproduction-image": "gitlab.com/aliasrobotics/offensive/alurity/pipelines/active/pipeline_ros_industrial/-/jobs/402982901/artifacts/download",
"date-reported": "2020-01-14 (18:42)",
"reproducibility": "always",
"detected-by-method": "testing static",
"reported-by-relationship": "automatic",
"trace": "",
"reported-by": "Alias Robotics",
"issue": "",
"package": "N/A",
"detected-by": "Alias Robotics"
}
}
```
|
test
|
error resource leak yaml id cve none description error resource leak fp system src industrial calibration intrinsic cal src ical srv cpp title error resource leak severity severity description cvss score rvss vector rvss score cvss vector vendor null exploitation exploitation image exploitation vector description type bug mitigation date mitigation pull request description links keywords cppcheck static analysis testing triage bug cwe none flaw application n a phase testing languages none reproduction see artifacts below if available specificity n a date detected architectural location n a subsystem n a reproduction image gitlab com aliasrobotics offensive alurity pipelines active pipeline ros industrial jobs artifacts download date reported reproducibility always detected by method testing static reported by relationship automatic trace reported by alias robotics issue package n a detected by alias robotics
| 1
|
327,926
| 28,091,268,880
|
IssuesEvent
|
2023-03-30 13:12:48
|
software-mansion/starknet-jvm
|
https://api.github.com/repos/software-mansion/starknet-jvm
|
closed
|
Tests per block hash/number
|
enhancement good first issue question tests
|
### Feature Request
From discussion:
https://github.com/software-mansion/starknet-jvm/pull/212#discussion_r1048513266
We should look through the tests and uncomment/adjust the ones that have been marked as untestable with current devnet implementation, if possible
|
1.0
|
Tests per block hash/number - ### Feature Request
From discussion:
https://github.com/software-mansion/starknet-jvm/pull/212#discussion_r1048513266
We should look through the tests and uncomment/adjust the ones that have been marked as untestable with current devnet implementation, if possible
|
test
|
tests per block hash number feature request from discussion we should look through the tests and uncomment adjust the ones that have been marked as untestable with current devnet implementation if possible
| 1
|
115,608
| 17,332,476,764
|
IssuesEvent
|
2021-07-28 05:37:57
|
panasalap/OpenJPEG-2.3.0
|
https://api.github.com/repos/panasalap/OpenJPEG-2.3.0
|
opened
|
CVE-2018-21010 (High) detected in openjpegv2.3.0
|
security vulnerability
|
## CVE-2018-21010 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>openjpegv2.3.0</b></p></summary>
<p>
<p>Official repository of the OpenJPEG project</p>
<p>Library home page: <a href=https://github.com/uclouvain/openjpeg.git>https://github.com/uclouvain/openjpeg.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/panasalap/OpenJPEG-2.3.0/commit/30e3071433b955b5059410d8045ce956198293d7">30e3071433b955b5059410d8045ce956198293d7</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>OpenJPEG-2.3.0/src/bin/common/color.c</b>
</p>
</details>
<p></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>
OpenJPEG before 2.3.1 has a heap buffer overflow in color_apply_icc_profile in bin/common/color.c.
<p>Publish Date: 2019-09-05
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-21010>CVE-2018-21010</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-21010">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-21010</a></p>
<p>Release Date: 2019-09-05</p>
<p>Fix Resolution: 2.3.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2018-21010 (High) detected in openjpegv2.3.0 - ## CVE-2018-21010 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>openjpegv2.3.0</b></p></summary>
<p>
<p>Official repository of the OpenJPEG project</p>
<p>Library home page: <a href=https://github.com/uclouvain/openjpeg.git>https://github.com/uclouvain/openjpeg.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/panasalap/OpenJPEG-2.3.0/commit/30e3071433b955b5059410d8045ce956198293d7">30e3071433b955b5059410d8045ce956198293d7</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>OpenJPEG-2.3.0/src/bin/common/color.c</b>
</p>
</details>
<p></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>
OpenJPEG before 2.3.1 has a heap buffer overflow in color_apply_icc_profile in bin/common/color.c.
<p>Publish Date: 2019-09-05
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-21010>CVE-2018-21010</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-21010">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-21010</a></p>
<p>Release Date: 2019-09-05</p>
<p>Fix Resolution: 2.3.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_test
|
cve high detected in cve high severity vulnerability vulnerable library official repository of the openjpeg project library home page a href found in head commit a href found in base branch master vulnerable source files openjpeg src bin common color c vulnerability details openjpeg before has a heap buffer overflow in color apply icc profile in bin common color c publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource
| 0
|
117,340
| 9,924,054,805
|
IssuesEvent
|
2019-07-01 08:48:54
|
e107inc/e107
|
https://api.github.com/repos/e107inc/e107
|
closed
|
not working comments
|
testing required
|
Tested, it works with php 5.6
But I have new demo site on version 7.2 (not sure if it's related)
- version 2.2.1 from e107.org is used, not latest github version
- I switched to bootstrap3 to be sure it's not theme related or bootstrap version.
After click on button Send it looks like nothing happened, but comment is visible after refresh.
There is error in console:
Thanks
|
1.0
|
not working comments - Tested, it works with php 5.6
But I have new demo site on version 7.2 (not sure if it's related)
- version 2.2.1 from e107.org is used, not latest github version
- I switched to bootstrap3 to be sure it's not theme related or bootstrap version.
After click on button Send it looks like nothing happened, but comment is visible after refresh.
There is error in console:
Thanks
|
test
|
not working comments tested it works with php but i have new demo site on version not sure if it s related version from org is used not latest github version i switched to to be sure it s not theme related or bootstrap version after click on button send it looks like nothing happened but comment is visible after refresh there is error in console thanks
| 1
|
133,707
| 10,860,098,011
|
IssuesEvent
|
2019-11-14 08:16:26
|
microsoft/azure-tools-for-java
|
https://api.github.com/repos/microsoft/azure-tools-for-java
|
closed
|
[IntelliJ][ReportedByUser] Uncaught Exception java.security.PrivilegedActionException: java.security.PrivilegedActionException: java.lang.reflect.InvocationTargetException
|
HDInsight IntelliJ Internal Test System Telemetry bug fixed
|
IntelliJ build version: 2019.2.1 IC-192.6262.41
OS: Windows 10
JDK: JetBrains s.r.o 11.0.3
Plugin version: 3.26.0-2019.2
Additional Info: None
Build:azure-toolkit-for-intellij-2019.2.develop.1234.09-05-2019
Repro Steps:
1.Create a new project.
2.Create an Arcadia config file.
3.Fill in the locally run config and leave the remotely run settings file blank.
4.Click TOOLS-->Spark Console -->Run Spark Local Console
5. After the local running is successful ,directly click Run spark livy interactive session console
Result:
**Red exclamation mark pops up in the lower right corner**
Expectation:
**Pop up a prompt to set the configuration file**
Parent component:
```
com.intellij.openapi.wm.impl.IdeRootPane[,8,8,1441x818,invalid,layout=com.intellij.openapi.wm.impl.IdeRootPane$MyRootLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=449,maximumSize=,minimumSize=,preferredSize=]
```
Error message:
```
java.security.PrivilegedActionException: java.security.PrivilegedActionException: java.lang.reflect.InvocationTargetException
at java.base/java.security.AccessController.doPrivileged(Native Method)
at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:748)
at com.intellij.ide.IdeEventQueue.defaultDispatchEvent(IdeEventQueue.java:817)
at com.intellij.ide.IdeEventQueue._dispatchEvent(IdeEventQueue.java:762)
at com.intellij.ide.IdeEventQueue.lambda$dispatchEvent$8(IdeEventQueue.java:405)
at com.intellij.openapi.progress.impl.CoreProgressManager.computePrioritized(CoreProgressManager.java:704)
at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:404)
at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
Caused by: java.security.PrivilegedActionException: java.lang.reflect.InvocationTargetException
at java.base/java.security.AccessController.doPrivileged(Native Method)
at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:95)
at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:751)
at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:749)
... 14 more
Caused by: java.lang.reflect.InvocationTargetException
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at com.microsoft.azure.hdinsight.spark.console.RunSparkConsoleActionDelegate.actionPerformed(RunSparkConsoleActionDelegate.kt:59)
at com.intellij.openapi.actionSystem.ex.ActionUtil$1.run(ActionUtil.java:265)
at com.intellij.openapi.actionSystem.ex.ActionUtil.performActionDumbAware(ActionUtil.java:282)
at com.intellij.openapi.actionSystem.impl.ActionMenuItem$ActionTransmitter.lambda$actionPerformed$0(ActionMenuItem.java:292)
at com.intellij.openapi.wm.impl.FocusManagerImpl.runOnOwnContext(FocusManagerImpl.java:265)
at com.intellij.openapi.wm.impl.IdeFocusManagerImpl.runOnOwnContext(IdeFocusManagerImpl.java:107)
at com.intellij.openapi.actionSystem.impl.ActionMenuItem$ActionTransmitter.actionPerformed(ActionMenuItem.java:282)
at java.desktop/javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1967)
at com.intellij.openapi.actionSystem.impl.ActionMenuItem.lambda$fireActionPerformed$0(ActionMenuItem.java:111)
at com.intellij.openapi.application.TransactionGuardImpl.runSyncTransaction(TransactionGuardImpl.java:82)
at com.intellij.openapi.application.TransactionGuardImpl.lambda$submitTransaction$1(TransactionGuardImpl.java:106)
at com.intellij.openapi.application.TransactionGuardImpl.submitTransaction(TransactionGuardImpl.java:115)
at com.intellij.openapi.application.TransactionGuard.submitTransaction(TransactionGuard.java:121)
at com.intellij.openapi.actionSystem.impl.ActionMenuItem.fireActionPerformed(ActionMenuItem.java:111)
at com.intellij.ui.plaf.beg.BegMenuItemUI.doClick(BegMenuItemUI.java:524)
at com.intellij.ui.plaf.beg.BegMenuItemUI.access$300(BegMenuItemUI.java:35)
at com.intellij.ui.plaf.beg.BegMenuItemUI$MyMouseInputHandler.mouseReleased(BegMenuItemUI.java:546)
at java.desktop/java.awt.Component.processMouseEvent(Component.java:6651)
at java.desktop/javax.swing.JComponent.processMouseEvent(JComponent.java:3342)
at java.desktop/java.awt.Component.processEvent(Component.java:6416)
at java.desktop/java.awt.Container.processEvent(Container.java:2263)
at java.desktop/java.awt.Component.dispatchEventImpl(Component.java:5026)
at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2321)
at java.desktop/java.awt.Component.dispatchEvent(Component.java:4858)
at java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4918)
at java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4547)
at java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4488)
at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2307)
at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2772)
at java.desktop/java.awt.Component.dispatchEvent(Component.java:4858)
at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:778)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:727)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
... 19 more
Caused by: kotlin.UninitializedPropertyAccessException: lateinit property tenantId has not been initialized
at com.microsoft.azure.hdinsight.spark.run.configuration.ArcadiaSparkSubmitModel.getTenantId(ArcadiaSparkSubmitModel.kt:37)
at com.microsoft.azure.projectarcadia.spark.console.ArcadiaSparkScalaLivyConsoleRunConfiguration.checkRunnerSettings(ArcadiaSparkScalaLivyConsoleRunConfiguration.kt:71)
at com.microsoft.azure.hdinsight.spark.run.action.RunConfigurationActionUtils.checkRunnerSettings(RunConfigurationActionUtils.kt:87)
at com.microsoft.azure.hdinsight.spark.run.action.RunConfigurationActionUtils.getRunConfigurationError(RunConfigurationActionUtils.kt:92)
at com.microsoft.azure.hdinsight.spark.run.action.RunConfigurationActionUtils.runEnvironmentProfileWithCheckSettings(RunConfigurationActionUtils.kt:53)
at com.microsoft.azure.hdinsight.spark.console.RunSparkScalaConsoleAction.runFromSetting(RunSparkScalaConsoleAction.kt:144)
at com.microsoft.azure.hdinsight.spark.console.RunSparkScalaConsoleAction.access$runFromSetting(RunSparkScalaConsoleAction.kt:52)
at com.microsoft.azure.hdinsight.spark.console.RunSparkScalaConsoleAction$runExisting$1.invoke(RunSparkScalaConsoleAction.kt:119)
at com.microsoft.azure.hdinsight.spark.console.RunSparkScalaConsoleAction$runExisting$1.invoke(RunSparkScalaConsoleAction.kt:52)
at com.microsoft.intellij.util.ApplicationHelpersKt.runInReadAction(ApplicationHelpers.kt:42)
at com.microsoft.azure.hdinsight.spark.console.RunSparkScalaConsoleAction.runExisting(RunSparkScalaConsoleAction.kt:118)
at com.microsoft.azure.hdinsight.spark.console.RunSparkScalaConsoleAction.onActionPerformed(RunSparkScalaConsoleAction.kt:71)
at com.microsoft.azuretools.ijidea.utility.AzureAnAction.actionPerformed(AzureAnAction.java:75)
... 56 more
```
|
1.0
|
[IntelliJ][ReportedByUser] Uncaught Exception java.security.PrivilegedActionException: java.security.PrivilegedActionException: java.lang.reflect.InvocationTargetException - IntelliJ build version: 2019.2.1 IC-192.6262.41
OS: Windows 10
JDK: JetBrains s.r.o 11.0.3
Plugin version: 3.26.0-2019.2
Additional Info: None
Build:azure-toolkit-for-intellij-2019.2.develop.1234.09-05-2019
Repro Steps:
1.Create a new project.
2.Create an Arcadia config file.
3.Fill in the locally run config and leave the remotely run settings file blank.
4.Click TOOLS-->Spark Console -->Run Spark Local Console
5. After the local running is successful ,directly click Run spark livy interactive session console
Result:
**Red exclamation mark pops up in the lower right corner**
Expectation:
**Pop up a prompt to set the configuration file**
Parent component:
```
com.intellij.openapi.wm.impl.IdeRootPane[,8,8,1441x818,invalid,layout=com.intellij.openapi.wm.impl.IdeRootPane$MyRootLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=449,maximumSize=,minimumSize=,preferredSize=]
```
Error message:
```
java.security.PrivilegedActionException: java.security.PrivilegedActionException: java.lang.reflect.InvocationTargetException
at java.base/java.security.AccessController.doPrivileged(Native Method)
at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:748)
at com.intellij.ide.IdeEventQueue.defaultDispatchEvent(IdeEventQueue.java:817)
at com.intellij.ide.IdeEventQueue._dispatchEvent(IdeEventQueue.java:762)
at com.intellij.ide.IdeEventQueue.lambda$dispatchEvent$8(IdeEventQueue.java:405)
at com.intellij.openapi.progress.impl.CoreProgressManager.computePrioritized(CoreProgressManager.java:704)
at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:404)
at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
Caused by: java.security.PrivilegedActionException: java.lang.reflect.InvocationTargetException
at java.base/java.security.AccessController.doPrivileged(Native Method)
at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:95)
at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:751)
at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:749)
... 14 more
Caused by: java.lang.reflect.InvocationTargetException
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at com.microsoft.azure.hdinsight.spark.console.RunSparkConsoleActionDelegate.actionPerformed(RunSparkConsoleActionDelegate.kt:59)
at com.intellij.openapi.actionSystem.ex.ActionUtil$1.run(ActionUtil.java:265)
at com.intellij.openapi.actionSystem.ex.ActionUtil.performActionDumbAware(ActionUtil.java:282)
at com.intellij.openapi.actionSystem.impl.ActionMenuItem$ActionTransmitter.lambda$actionPerformed$0(ActionMenuItem.java:292)
at com.intellij.openapi.wm.impl.FocusManagerImpl.runOnOwnContext(FocusManagerImpl.java:265)
at com.intellij.openapi.wm.impl.IdeFocusManagerImpl.runOnOwnContext(IdeFocusManagerImpl.java:107)
at com.intellij.openapi.actionSystem.impl.ActionMenuItem$ActionTransmitter.actionPerformed(ActionMenuItem.java:282)
at java.desktop/javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1967)
at com.intellij.openapi.actionSystem.impl.ActionMenuItem.lambda$fireActionPerformed$0(ActionMenuItem.java:111)
at com.intellij.openapi.application.TransactionGuardImpl.runSyncTransaction(TransactionGuardImpl.java:82)
at com.intellij.openapi.application.TransactionGuardImpl.lambda$submitTransaction$1(TransactionGuardImpl.java:106)
at com.intellij.openapi.application.TransactionGuardImpl.submitTransaction(TransactionGuardImpl.java:115)
at com.intellij.openapi.application.TransactionGuard.submitTransaction(TransactionGuard.java:121)
at com.intellij.openapi.actionSystem.impl.ActionMenuItem.fireActionPerformed(ActionMenuItem.java:111)
at com.intellij.ui.plaf.beg.BegMenuItemUI.doClick(BegMenuItemUI.java:524)
at com.intellij.ui.plaf.beg.BegMenuItemUI.access$300(BegMenuItemUI.java:35)
at com.intellij.ui.plaf.beg.BegMenuItemUI$MyMouseInputHandler.mouseReleased(BegMenuItemUI.java:546)
at java.desktop/java.awt.Component.processMouseEvent(Component.java:6651)
at java.desktop/javax.swing.JComponent.processMouseEvent(JComponent.java:3342)
at java.desktop/java.awt.Component.processEvent(Component.java:6416)
at java.desktop/java.awt.Container.processEvent(Container.java:2263)
at java.desktop/java.awt.Component.dispatchEventImpl(Component.java:5026)
at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2321)
at java.desktop/java.awt.Component.dispatchEvent(Component.java:4858)
at java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4918)
at java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4547)
at java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4488)
at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2307)
at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2772)
at java.desktop/java.awt.Component.dispatchEvent(Component.java:4858)
at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:778)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:727)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
... 19 more
Caused by: kotlin.UninitializedPropertyAccessException: lateinit property tenantId has not been initialized
at com.microsoft.azure.hdinsight.spark.run.configuration.ArcadiaSparkSubmitModel.getTenantId(ArcadiaSparkSubmitModel.kt:37)
at com.microsoft.azure.projectarcadia.spark.console.ArcadiaSparkScalaLivyConsoleRunConfiguration.checkRunnerSettings(ArcadiaSparkScalaLivyConsoleRunConfiguration.kt:71)
at com.microsoft.azure.hdinsight.spark.run.action.RunConfigurationActionUtils.checkRunnerSettings(RunConfigurationActionUtils.kt:87)
at com.microsoft.azure.hdinsight.spark.run.action.RunConfigurationActionUtils.getRunConfigurationError(RunConfigurationActionUtils.kt:92)
at com.microsoft.azure.hdinsight.spark.run.action.RunConfigurationActionUtils.runEnvironmentProfileWithCheckSettings(RunConfigurationActionUtils.kt:53)
at com.microsoft.azure.hdinsight.spark.console.RunSparkScalaConsoleAction.runFromSetting(RunSparkScalaConsoleAction.kt:144)
at com.microsoft.azure.hdinsight.spark.console.RunSparkScalaConsoleAction.access$runFromSetting(RunSparkScalaConsoleAction.kt:52)
at com.microsoft.azure.hdinsight.spark.console.RunSparkScalaConsoleAction$runExisting$1.invoke(RunSparkScalaConsoleAction.kt:119)
at com.microsoft.azure.hdinsight.spark.console.RunSparkScalaConsoleAction$runExisting$1.invoke(RunSparkScalaConsoleAction.kt:52)
at com.microsoft.intellij.util.ApplicationHelpersKt.runInReadAction(ApplicationHelpers.kt:42)
at com.microsoft.azure.hdinsight.spark.console.RunSparkScalaConsoleAction.runExisting(RunSparkScalaConsoleAction.kt:118)
at com.microsoft.azure.hdinsight.spark.console.RunSparkScalaConsoleAction.onActionPerformed(RunSparkScalaConsoleAction.kt:71)
at com.microsoft.azuretools.ijidea.utility.AzureAnAction.actionPerformed(AzureAnAction.java:75)
... 56 more
```
|
test
|
uncaught exception java security privilegedactionexception java security privilegedactionexception java lang reflect invocationtargetexception intellij build version ic os windows jdk jetbrains s r o plugin version additional info none build azure toolkit for intellij develop repro steps create a new project create an arcadia config file fill in the locally run config and leave the remotely run settings file blank click tools spark console run spark local console after the local running is successful directly click run spark livy interactive session console result red exclamation mark pops up in the lower right corner expectation pop up a prompt to set the configuration file parent component com intellij openapi wm impl iderootpane error message java security privilegedactionexception java security privilegedactionexception java lang reflect invocationtargetexception at java base java security accesscontroller doprivileged native method at java base java security protectiondomain javasecurityaccessimpl dointersectionprivilege protectiondomain java at java desktop java awt eventqueue dispatchevent eventqueue java at com intellij ide ideeventqueue defaultdispatchevent ideeventqueue java at com intellij ide ideeventqueue dispatchevent ideeventqueue java at com intellij ide ideeventqueue lambda dispatchevent ideeventqueue java at com intellij openapi progress impl coreprogressmanager computeprioritized coreprogressmanager java at com intellij ide ideeventqueue dispatchevent ideeventqueue java at java desktop java awt eventdispatchthread pumponeeventforfilters eventdispatchthread java at java desktop java awt eventdispatchthread pumpeventsforfilter eventdispatchthread java at java desktop java awt eventdispatchthread pumpeventsforhierarchy eventdispatchthread java at java desktop java awt eventdispatchthread pumpevents eventdispatchthread java at java desktop java awt eventdispatchthread pumpevents eventdispatchthread java at java desktop java awt eventdispatchthread run eventdispatchthread java caused by java security privilegedactionexception java lang reflect invocationtargetexception at java base java security accesscontroller doprivileged native method at java base java security protectiondomain javasecurityaccessimpl dointersectionprivilege protectiondomain java at java base java security protectiondomain javasecurityaccessimpl dointersectionprivilege protectiondomain java at java desktop java awt eventqueue run eventqueue java at java desktop java awt eventqueue run eventqueue java more caused by java lang reflect invocationtargetexception at java base jdk internal reflect nativemethodaccessorimpl native method at java base jdk internal reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at java base jdk internal reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java base java lang reflect method invoke method java at com microsoft azure hdinsight spark console runsparkconsoleactiondelegate actionperformed runsparkconsoleactiondelegate kt at com intellij openapi actionsystem ex actionutil run actionutil java at com intellij openapi actionsystem ex actionutil performactiondumbaware actionutil java at com intellij openapi actionsystem impl actionmenuitem actiontransmitter lambda actionperformed actionmenuitem java at com intellij openapi wm impl focusmanagerimpl runonowncontext focusmanagerimpl java at com intellij openapi wm impl idefocusmanagerimpl runonowncontext idefocusmanagerimpl java at com intellij openapi actionsystem impl actionmenuitem actiontransmitter actionperformed actionmenuitem java at java desktop javax swing abstractbutton fireactionperformed abstractbutton java at com intellij openapi actionsystem impl actionmenuitem lambda fireactionperformed actionmenuitem java at com intellij openapi application transactionguardimpl runsynctransaction transactionguardimpl java at com intellij openapi application transactionguardimpl lambda submittransaction transactionguardimpl java at com intellij openapi application transactionguardimpl submittransaction transactionguardimpl java at com intellij openapi application transactionguard submittransaction transactionguard java at com intellij openapi actionsystem impl actionmenuitem fireactionperformed actionmenuitem java at com intellij ui plaf beg begmenuitemui doclick begmenuitemui java at com intellij ui plaf beg begmenuitemui access begmenuitemui java at com intellij ui plaf beg begmenuitemui mymouseinputhandler mousereleased begmenuitemui java at java desktop java awt component processmouseevent component java at java desktop javax swing jcomponent processmouseevent jcomponent java at java desktop java awt component processevent component java at java desktop java awt container processevent container java at java desktop java awt component dispatcheventimpl component java at java desktop java awt container dispatcheventimpl container java at java desktop java awt component dispatchevent component java at java desktop java awt lightweightdispatcher retargetmouseevent container java at java desktop java awt lightweightdispatcher processmouseevent container java at java desktop java awt lightweightdispatcher dispatchevent container java at java desktop java awt container dispatcheventimpl container java at java desktop java awt window dispatcheventimpl window java at java desktop java awt component dispatchevent component java at java desktop java awt eventqueue dispatcheventimpl eventqueue java at java desktop java awt eventqueue run eventqueue java at java desktop java awt eventqueue run eventqueue java more caused by kotlin uninitializedpropertyaccessexception lateinit property tenantid has not been initialized at com microsoft azure hdinsight spark run configuration arcadiasparksubmitmodel gettenantid arcadiasparksubmitmodel kt at com microsoft azure projectarcadia spark console arcadiasparkscalalivyconsolerunconfiguration checkrunnersettings arcadiasparkscalalivyconsolerunconfiguration kt at com microsoft azure hdinsight spark run action runconfigurationactionutils checkrunnersettings runconfigurationactionutils kt at com microsoft azure hdinsight spark run action runconfigurationactionutils getrunconfigurationerror runconfigurationactionutils kt at com microsoft azure hdinsight spark run action runconfigurationactionutils runenvironmentprofilewithchecksettings runconfigurationactionutils kt at com microsoft azure hdinsight spark console runsparkscalaconsoleaction runfromsetting runsparkscalaconsoleaction kt at com microsoft azure hdinsight spark console runsparkscalaconsoleaction access runfromsetting runsparkscalaconsoleaction kt at com microsoft azure hdinsight spark console runsparkscalaconsoleaction runexisting invoke runsparkscalaconsoleaction kt at com microsoft azure hdinsight spark console runsparkscalaconsoleaction runexisting invoke runsparkscalaconsoleaction kt at com microsoft intellij util applicationhelperskt runinreadaction applicationhelpers kt at com microsoft azure hdinsight spark console runsparkscalaconsoleaction runexisting runsparkscalaconsoleaction kt at com microsoft azure hdinsight spark console runsparkscalaconsoleaction onactionperformed runsparkscalaconsoleaction kt at com microsoft azuretools ijidea utility azureanaction actionperformed azureanaction java more
| 1
|
255,610
| 8,125,825,033
|
IssuesEvent
|
2018-08-16 22:30:34
|
imgix/react-imgix
|
https://api.github.com/repos/imgix/react-imgix
|
closed
|
Picture Support for Responsive images not working
|
Priority: Medium Status: Discussion Type: Question
|
**type:** question
**react-imgix version:** `7.1.1`
**Code**
```js
<div className={classes.image}>
<Imgix
src={src}
onMounted={ar => {
console.log(ar)
}}
width={1400}
fit={'clip'}
auto={['format', 'compress']}
type="picture"
>
<Imgix
src={src}
width={400}
type="source"
imgProps={{media: '(min-width: 768px)'}}
/>
<Imgix
src={src}
width={200}
type="source"
imgProps={{media: '(min-width: 320px)'}}
/>
</Imgix>
</div>
```
**Actual behavior:**
For some reason it resizes it to really finny size.
[](https://postimg.cc/image/qaa5dea0d/)
React Version: 16.3.2
|
1.0
|
Picture Support for Responsive images not working - **type:** question
**react-imgix version:** `7.1.1`
**Code**
```js
<div className={classes.image}>
<Imgix
src={src}
onMounted={ar => {
console.log(ar)
}}
width={1400}
fit={'clip'}
auto={['format', 'compress']}
type="picture"
>
<Imgix
src={src}
width={400}
type="source"
imgProps={{media: '(min-width: 768px)'}}
/>
<Imgix
src={src}
width={200}
type="source"
imgProps={{media: '(min-width: 320px)'}}
/>
</Imgix>
</div>
```
**Actual behavior:**
For some reason it resizes it to really finny size.
[](https://postimg.cc/image/qaa5dea0d/)
React Version: 16.3.2
|
non_test
|
picture support for responsive images not working type question react imgix version code js imgix src src onmounted ar console log ar width fit clip auto type picture imgix src src width type source imgprops media min width imgix src src width type source imgprops media min width actual behavior for some reason it resizes it to really finny size react version
| 0
|
304,154
| 26,256,171,743
|
IssuesEvent
|
2023-01-06 01:02:50
|
backend-br/vagas
|
https://api.github.com/repos/backend-br/vagas
|
closed
|
[Remoto] Developer - Multinacional ESSS
|
CLT Pleno Sênior Júnior Python Flask Remoto Especialista Testes automatizados TypeScript Docker Stale
|
<!-- Por favor, poste apenas vagas para backend. -->
## Nossa empresa
A ESSS é uma multinacional brasileira sediada na cidade de Florianópolis/SC. Disponibilizamos ao mercado as mais avançadas ferramentas de CAE na área de fluidodinâmica, análise estrutural, eletromagnetismo e multifísica, além de customização e desenvolvimento de softwares sob medida de acordo com a necessidade de cada cliente. Estamos presentes no Brasil e no exterior, incluindo Argentina, Chile, Colômbia, Peru, Portugal, Espanha, México e Estados Unidos.
Se você acredita que suas habilidades, talento e experiências são diferenciados para trabalhar em um time de alta performance, responsável pela resolução de problemas por meio da tecnologia e desenvolvimento de softwares, faça sua inscrição.
## Descrição da vaga
Se você é um entusiasta por inovação e tecnologia e busca uma empresa onde possa compartilhar ideias, conquistas e trabalhar em um ambiente saudável, onde possa se desenvolver pessoal e profissionalmente, estamos com oportunidades em aberto para Desenvolvedor de Software.
Para essa posição seus principais desafios serão:
Desenvolver softwares de simulação computacional para engenharia.
Desenvolver aplicações Web com testes automatizados (testes unitários e de aceitação).
Integrar as bibliotecas desenvolvidas pelo nosso time de desenvolvimento numérico e científico em aplicações gráficas para o usuário final.
Tecnologias que Utilizamos:
Python 3 e TypeScript.
Aplicações Web em Angular.
Back-end utilizando Flask, SQLAlchemy, Celery.
Banco de dados Postgres.
Infraestrutura com Docker.
Testes automatizados (unitários, integração e end-to-end).
Metodologias Ágeis (Integração Contínua, Revisão de Código, SCRUM).
## Local
Remoto ou Florianópolis/SC
## Requisitos
Requisitos Exigidos:
Experiência com algum framework web (de preferência Angular)
Experiência com desenvolvimento de APIs REST
Não é necessário conhecimento em todas tecnologias listadas acima, entretanto experiência prévia será considerada para definição do nível do cargo (júnior/pleno)
Inglês intermediário.
Requisitos Desejados:
Experiência com Docker
Experiencia com Python
Conhecimento de RxJS, CSS
Conhecimento de banco de dados relacionais
## Benefícios
Plano de saúde nacional com subsídio integral sem coparticipação (melhor operadora da região).
Cartão de benefícios flexíveis.
Licença maternidade e paternidade estendidas.
Oportunidade para contribuição em projetos open source.
Incentivo a educação continuada através de cursos, treinamentos e especializações e auxílio idiomas.
Incentivo a publicações, participações em eventos de tecnologia relevantes para seu trabalho.
Mais de 20 outros benefícios.
## Contratação
CLT
## Como se candidatar
Nos envie e-mail com seu CV para selection@esss.co ou se cadastre no link: https://esss.gupy.io/jobs/3242317
## Labels
<!-- Retire os labels que não fazem sentido à vaga. -->
### Nível
- Pleno
- Sênior
- Especialista
### Regime
- CLT
### Alocação
- Remoto
|
1.0
|
[Remoto] Developer - Multinacional ESSS - <!-- Por favor, poste apenas vagas para backend. -->
## Nossa empresa
A ESSS é uma multinacional brasileira sediada na cidade de Florianópolis/SC. Disponibilizamos ao mercado as mais avançadas ferramentas de CAE na área de fluidodinâmica, análise estrutural, eletromagnetismo e multifísica, além de customização e desenvolvimento de softwares sob medida de acordo com a necessidade de cada cliente. Estamos presentes no Brasil e no exterior, incluindo Argentina, Chile, Colômbia, Peru, Portugal, Espanha, México e Estados Unidos.
Se você acredita que suas habilidades, talento e experiências são diferenciados para trabalhar em um time de alta performance, responsável pela resolução de problemas por meio da tecnologia e desenvolvimento de softwares, faça sua inscrição.
## Descrição da vaga
Se você é um entusiasta por inovação e tecnologia e busca uma empresa onde possa compartilhar ideias, conquistas e trabalhar em um ambiente saudável, onde possa se desenvolver pessoal e profissionalmente, estamos com oportunidades em aberto para Desenvolvedor de Software.
Para essa posição seus principais desafios serão:
Desenvolver softwares de simulação computacional para engenharia.
Desenvolver aplicações Web com testes automatizados (testes unitários e de aceitação).
Integrar as bibliotecas desenvolvidas pelo nosso time de desenvolvimento numérico e científico em aplicações gráficas para o usuário final.
Tecnologias que Utilizamos:
Python 3 e TypeScript.
Aplicações Web em Angular.
Back-end utilizando Flask, SQLAlchemy, Celery.
Banco de dados Postgres.
Infraestrutura com Docker.
Testes automatizados (unitários, integração e end-to-end).
Metodologias Ágeis (Integração Contínua, Revisão de Código, SCRUM).
## Local
Remoto ou Florianópolis/SC
## Requisitos
Requisitos Exigidos:
Experiência com algum framework web (de preferência Angular)
Experiência com desenvolvimento de APIs REST
Não é necessário conhecimento em todas tecnologias listadas acima, entretanto experiência prévia será considerada para definição do nível do cargo (júnior/pleno)
Inglês intermediário.
Requisitos Desejados:
Experiência com Docker
Experiencia com Python
Conhecimento de RxJS, CSS
Conhecimento de banco de dados relacionais
## Benefícios
Plano de saúde nacional com subsídio integral sem coparticipação (melhor operadora da região).
Cartão de benefícios flexíveis.
Licença maternidade e paternidade estendidas.
Oportunidade para contribuição em projetos open source.
Incentivo a educação continuada através de cursos, treinamentos e especializações e auxílio idiomas.
Incentivo a publicações, participações em eventos de tecnologia relevantes para seu trabalho.
Mais de 20 outros benefícios.
## Contratação
CLT
## Como se candidatar
Nos envie e-mail com seu CV para selection@esss.co ou se cadastre no link: https://esss.gupy.io/jobs/3242317
## Labels
<!-- Retire os labels que não fazem sentido à vaga. -->
### Nível
- Pleno
- Sênior
- Especialista
### Regime
- CLT
### Alocação
- Remoto
|
test
|
developer multinacional esss nossa empresa a esss é uma multinacional brasileira sediada na cidade de florianópolis sc disponibilizamos ao mercado as mais avançadas ferramentas de cae na área de fluidodinâmica análise estrutural eletromagnetismo e multifísica além de customização e desenvolvimento de softwares sob medida de acordo com a necessidade de cada cliente estamos presentes no brasil e no exterior incluindo argentina chile colômbia peru portugal espanha méxico e estados unidos se você acredita que suas habilidades talento e experiências são diferenciados para trabalhar em um time de alta performance responsável pela resolução de problemas por meio da tecnologia e desenvolvimento de softwares faça sua inscrição descrição da vaga se você é um entusiasta por inovação e tecnologia e busca uma empresa onde possa compartilhar ideias conquistas e trabalhar em um ambiente saudável onde possa se desenvolver pessoal e profissionalmente estamos com oportunidades em aberto para desenvolvedor de software para essa posição seus principais desafios serão desenvolver softwares de simulação computacional para engenharia desenvolver aplicações web com testes automatizados testes unitários e de aceitação integrar as bibliotecas desenvolvidas pelo nosso time de desenvolvimento numérico e científico em aplicações gráficas para o usuário final tecnologias que utilizamos python e typescript aplicações web em angular back end utilizando flask sqlalchemy celery banco de dados postgres infraestrutura com docker testes automatizados unitários integração e end to end metodologias ágeis integração contínua revisão de código scrum local remoto ou florianópolis sc requisitos requisitos exigidos experiência com algum framework web de preferência angular experiência com desenvolvimento de apis rest não é necessário conhecimento em todas tecnologias listadas acima entretanto experiência prévia será considerada para definição do nível do cargo júnior pleno inglês intermediário requisitos desejados experiência com docker experiencia com python conhecimento de rxjs css conhecimento de banco de dados relacionais benefícios plano de saúde nacional com subsídio integral sem coparticipação melhor operadora da região cartão de benefícios flexíveis licença maternidade e paternidade estendidas oportunidade para contribuição em projetos open source incentivo a educação continuada através de cursos treinamentos e especializações e auxílio idiomas incentivo a publicações participações em eventos de tecnologia relevantes para seu trabalho mais de outros benefícios contratação clt como se candidatar nos envie e mail com seu cv para selection esss co ou se cadastre no link labels nível pleno sênior especialista regime clt alocação remoto
| 1
|
93,829
| 10,775,593,601
|
IssuesEvent
|
2019-11-03 15:20:35
|
ilkilab/agorakube
|
https://api.github.com/repos/ilkilab/agorakube
|
closed
|
Add in the doc an array that explain what params we can use in Agorakube
|
documentation good first issue help wanted up-for-grabs
|
**Describe the solution you'd like**
Add in the doc an array that explain what params we can use in Agorakube
**Additional context**
Today, Agorakube doesn't have a clear array that match all possible parameters with their definition and teir possible values (with defaults). Please add this to the docummentation (README.md and docs/instructions.md) to make Agorakube customization easier.
|
1.0
|
Add in the doc an array that explain what params we can use in Agorakube - **Describe the solution you'd like**
Add in the doc an array that explain what params we can use in Agorakube
**Additional context**
Today, Agorakube doesn't have a clear array that match all possible parameters with their definition and teir possible values (with defaults). Please add this to the docummentation (README.md and docs/instructions.md) to make Agorakube customization easier.
|
non_test
|
add in the doc an array that explain what params we can use in agorakube describe the solution you d like add in the doc an array that explain what params we can use in agorakube additional context today agorakube doesn t have a clear array that match all possible parameters with their definition and teir possible values with defaults please add this to the docummentation readme md and docs instructions md to make agorakube customization easier
| 0
|
383,949
| 11,364,855,146
|
IssuesEvent
|
2020-01-27 09:21:06
|
ECLK/Nomination
|
https://api.github.com/repos/ECLK/Nomination
|
closed
|
Attach manual payslip to the nomination payment section
|
Nomination payment Priority 1
|
Currently there is no any option to attach a manual payslip to the nomination payment section.
after completed this issue, ec user should be able to attach signed payslip for each nomination payment
**solution**
- Implement ui components for attach document in the nomination payment dialog
- Save document original name and hashed name in database for further reference
- api details will be provide later
**Path**
1. Login in using payment admin account
2. Click on Nomination payment tab on left navigation bar
3. Click on add new payment button
4. Attach document component should be on this dialog
|
1.0
|
Attach manual payslip to the nomination payment section - Currently there is no any option to attach a manual payslip to the nomination payment section.
after completed this issue, ec user should be able to attach signed payslip for each nomination payment
**solution**
- Implement ui components for attach document in the nomination payment dialog
- Save document original name and hashed name in database for further reference
- api details will be provide later
**Path**
1. Login in using payment admin account
2. Click on Nomination payment tab on left navigation bar
3. Click on add new payment button
4. Attach document component should be on this dialog
|
non_test
|
attach manual payslip to the nomination payment section currently there is no any option to attach a manual payslip to the nomination payment section after completed this issue ec user should be able to attach signed payslip for each nomination payment solution implement ui components for attach document in the nomination payment dialog save document original name and hashed name in database for further reference api details will be provide later path login in using payment admin account click on nomination payment tab on left navigation bar click on add new payment button attach document component should be on this dialog
| 0
|
170,374
| 13,185,158,045
|
IssuesEvent
|
2020-08-12 20:50:13
|
cloudevents/sdk-javascript
|
https://api.github.com/repos/cloudevents/sdk-javascript
|
closed
|
Test run shows pending tests
|
good first issue module/test status/no-issue-activity type/question
|
At the end of a `npm run test`, there says there is 6 pending tests.
```
~/develop/cloudevents/sdk-javascript(master) » ./node_modules/mocha/bin/mocha --require ts-node/register test/cloud_event_test.ts
A CloudEvent
✓ Can be constructed with a typed Message
✓ serializes as JSON with toString()
A 1.0 CloudEvent
✓ has retreivable source and type attributes
✓ defaults to specversion 1.0
✓ generates an ID if one is not provided in the constructor
✓ can be constructed with an ID
✓ generates a timestamp by default
✓ can be constructed with a timestamp
✓ can be constructed with a datacontenttype
✓ can be constructed with a dataschema
✓ can be constructed with a subject
✓ throws a TypeError when constructed with a schemaurl
✓ can be constructed with data
✓ can be constructed with extensions
- throws ValidationError if the CloudEvent does not conform to the schema
- returns a JSON string even if format is invalid
- correctly formats a CloudEvent as JSON
A 0.3 CloudEvent
✓ has retreivable source and type attributes
✓ generates an ID if one is not provided in the constructor
✓ generates a timestamp by default
✓ can be constructed with a timestamp
✓ can be constructed with a datacontenttype
✓ can be constructed with a datacontentencoding
✓ can be constructed with a schemaurl
✓ can be constructed with a subject
✓ throws a TypeError when constructed with a dataschema
✓ can be constructed with data
- throws ValidationError if the CloudEvent does not conform to the schema
- returns a JSON string even if format is invalid
- correctly formats a CloudEvent as JSON
24 passing (11ms)
6 pending
```
There are 6 tests here, https://github.com/cloudevents/sdk-javascript/blob/master/test/cloud_event_test.ts#L104 that don't do anything.
Were these just place holders when doing the TS re-write and should be removed? or do they need to be implemented?
|
1.0
|
Test run shows pending tests - At the end of a `npm run test`, there says there is 6 pending tests.
```
~/develop/cloudevents/sdk-javascript(master) » ./node_modules/mocha/bin/mocha --require ts-node/register test/cloud_event_test.ts
A CloudEvent
✓ Can be constructed with a typed Message
✓ serializes as JSON with toString()
A 1.0 CloudEvent
✓ has retreivable source and type attributes
✓ defaults to specversion 1.0
✓ generates an ID if one is not provided in the constructor
✓ can be constructed with an ID
✓ generates a timestamp by default
✓ can be constructed with a timestamp
✓ can be constructed with a datacontenttype
✓ can be constructed with a dataschema
✓ can be constructed with a subject
✓ throws a TypeError when constructed with a schemaurl
✓ can be constructed with data
✓ can be constructed with extensions
- throws ValidationError if the CloudEvent does not conform to the schema
- returns a JSON string even if format is invalid
- correctly formats a CloudEvent as JSON
A 0.3 CloudEvent
✓ has retreivable source and type attributes
✓ generates an ID if one is not provided in the constructor
✓ generates a timestamp by default
✓ can be constructed with a timestamp
✓ can be constructed with a datacontenttype
✓ can be constructed with a datacontentencoding
✓ can be constructed with a schemaurl
✓ can be constructed with a subject
✓ throws a TypeError when constructed with a dataschema
✓ can be constructed with data
- throws ValidationError if the CloudEvent does not conform to the schema
- returns a JSON string even if format is invalid
- correctly formats a CloudEvent as JSON
24 passing (11ms)
6 pending
```
There are 6 tests here, https://github.com/cloudevents/sdk-javascript/blob/master/test/cloud_event_test.ts#L104 that don't do anything.
Were these just place holders when doing the TS re-write and should be removed? or do they need to be implemented?
|
test
|
test run shows pending tests at the end of a npm run test there says there is pending tests develop cloudevents sdk javascript master » node modules mocha bin mocha require ts node register test cloud event test ts a cloudevent ✓ can be constructed with a typed message ✓ serializes as json with tostring a cloudevent ✓ has retreivable source and type attributes ✓ defaults to specversion ✓ generates an id if one is not provided in the constructor ✓ can be constructed with an id ✓ generates a timestamp by default ✓ can be constructed with a timestamp ✓ can be constructed with a datacontenttype ✓ can be constructed with a dataschema ✓ can be constructed with a subject ✓ throws a typeerror when constructed with a schemaurl ✓ can be constructed with data ✓ can be constructed with extensions throws validationerror if the cloudevent does not conform to the schema returns a json string even if format is invalid correctly formats a cloudevent as json a cloudevent ✓ has retreivable source and type attributes ✓ generates an id if one is not provided in the constructor ✓ generates a timestamp by default ✓ can be constructed with a timestamp ✓ can be constructed with a datacontenttype ✓ can be constructed with a datacontentencoding ✓ can be constructed with a schemaurl ✓ can be constructed with a subject ✓ throws a typeerror when constructed with a dataschema ✓ can be constructed with data throws validationerror if the cloudevent does not conform to the schema returns a json string even if format is invalid correctly formats a cloudevent as json passing pending there are tests here that don t do anything were these just place holders when doing the ts re write and should be removed or do they need to be implemented
| 1
|
48,964
| 5,995,181,701
|
IssuesEvent
|
2017-06-03 01:01:07
|
code4craft/webmagic
|
https://api.github.com/repos/code4craft/webmagic
|
closed
|
默认的调度器QueueScheduler不支持重试
|
bug toTest
|
因为其继承的DuplicateRemovedScheduler内的HashSetDuplicateRemover会将曾经访问过的链接去重。这将导致Spider设置循环重试次数无效。去重的逻辑影响到了重试的逻辑，好像不是很合理。
|
1.0
|
默认的调度器QueueScheduler不支持重试 - 因为其继承的DuplicateRemovedScheduler内的HashSetDuplicateRemover会将曾经访问过的链接去重。这将导致Spider设置循环重试次数无效。去重的逻辑影响到了重试的逻辑，好像不是很合理。
|
test
|
默认的调度器queuescheduler不支持重试 因为其继承的duplicateremovedscheduler内的hashsetduplicateremover会将曾经访问过的链接去重。这将导致spider设置循环重试次数无效。去重的逻辑影响到了重试的逻辑，好像不是很合理。
| 1
|
188,488
| 15,163,551,272
|
IssuesEvent
|
2021-02-12 12:23:24
|
kartoza/qgis_geonode
|
https://api.github.com/repos/kartoza/qgis_geonode
|
closed
|
Please create basic developer docs
|
size: 1 type: bug type: documentation
|
I would like to test the plugin as you work on it but I need basic information on how to get the plugin running on my system from a git clone. Please add to the readme.
|
1.0
|
Please create basic developer docs - I would like to test the plugin as you work on it but I need basic information on how to get the plugin running on my system from a git clone. Please add to the readme.
|
non_test
|
please create basic developer docs i would like to test the plugin as you work on it but i need basic information on how to get the plugin running on my system from a git clone please add to the readme
| 0
|
5,518
| 3,604,052,130
|
IssuesEvent
|
2016-02-03 21:23:26
|
openshift/origin
|
https://api.github.com/repos/openshift/origin
|
reopened
|
Improve build validation error message
|
area/usability component/build priority/P3
|
Some validation error messages include complex Go structs that are hard to understand by an end user.
Example:
```console
$ oc new-build -D 'FROM busybox:1'
$ oc edit bc
...
# %!s(func(runtime.Object) (string, error)=0x50c8c0) busybox was not valid:
# * invalid value '<*>(0xc20b3f0630){DockerStrategy:<*>(0xc213a60be0){From:<*>(0xc20ce1bb20){Kind:ImageStreamTag Namespace: Name:busybox:1 UID: APIVersion: ResourceVersion: FieldPath:} PullSecret:<nil> NoCache:false Env:<nil> ForcePull:false DockerfilePath:} SourceStrategy:<nil> CustomStrategy:<*>(0xc20d6f8600){From:{Kind:ImageStreamTag Namespace: Name: UID: APIVersion: ResourceVersion: FieldPath:} PullSecret:<nil> Env:<nil> ExposeDockerSocket:false ForcePull:true Secrets:<nil> BuildAPIVersion:}}', Details: must provide a value for exactly one of sourceStrategy, customStrategy, or dockerStrategy
```
The error message shows up not only in `oc edit`, but any other place that uses the API.
Proposal: improve the message, to have more readable information, perhaps render the invalid field as JSON.
|
1.0
|
Improve build validation error message - Some validation error messages include complex Go structs that are hard to understand by an end user.
Example:
```console
$ oc new-build -D 'FROM busybox:1'
$ oc edit bc
...
# %!s(func(runtime.Object) (string, error)=0x50c8c0) busybox was not valid:
# * invalid value '<*>(0xc20b3f0630){DockerStrategy:<*>(0xc213a60be0){From:<*>(0xc20ce1bb20){Kind:ImageStreamTag Namespace: Name:busybox:1 UID: APIVersion: ResourceVersion: FieldPath:} PullSecret:<nil> NoCache:false Env:<nil> ForcePull:false DockerfilePath:} SourceStrategy:<nil> CustomStrategy:<*>(0xc20d6f8600){From:{Kind:ImageStreamTag Namespace: Name: UID: APIVersion: ResourceVersion: FieldPath:} PullSecret:<nil> Env:<nil> ExposeDockerSocket:false ForcePull:true Secrets:<nil> BuildAPIVersion:}}', Details: must provide a value for exactly one of sourceStrategy, customStrategy, or dockerStrategy
```
The error message shows up not only in `oc edit`, but any other place that uses the API.
Proposal: improve the message, to have more readable information, perhaps render the invalid field as JSON.
|
non_test
|
improve build validation error message some validation error messages include complex go structs that are hard to understand by an end user example console oc new build d from busybox oc edit bc s func runtime object string error busybox was not valid invalid value dockerstrategy from kind imagestreamtag namespace name busybox uid apiversion resourceversion fieldpath pullsecret nocache false env forcepull false dockerfilepath sourcestrategy customstrategy from kind imagestreamtag namespace name uid apiversion resourceversion fieldpath pullsecret env exposedockersocket false forcepull true secrets buildapiversion details must provide a value for exactly one of sourcestrategy customstrategy or dockerstrategy the error message shows up not only in oc edit but any other place that uses the api proposal improve the message to have more readable information perhaps render the invalid field as json
| 0
|
265,535
| 20,101,377,863
|
IssuesEvent
|
2022-02-07 04:54:29
|
SOunit/the_mern_fullstack_guide
|
https://api.github.com/repos/SOunit/the_mern_fullstack_guide
|
closed
|
section13 deploy
|
documentation
|
# refs
- project have to be root for deployment
https://github.com/SOunit/the_mern_stack_heroku_react
https://github.com/SOunit/the_mern_stack_heroku_node
# deploy steps overview
- develop & test your code
- swap url and credentials to production setting(using environment variables)
- build & deploy
- test deployed app, monitor and adjust
# environment variable
## backend
- nodemon.json
- access data using process.env.KEY_NAME
## frontend
- .env
- REACT_APP_
- all credential file goes to client, web browser. no credential code should be inside the client.
# mongo atlas setup
- create production cluster
- create production user
- limit IP address
- limit service
# react lazy loading
- to minimize initial load content
- use lazy
```
const Users = lazy(() => import("./user/pages/Users"));
const NewPlace = lazy(() => import("./places/pages/NewPlace"));
const UserPlaces = lazy(() => import("./places/pages/UserPlaces"));
const UpdatePlace = lazy(() => import("./places/pages/UpdatePlace"));
const Auth = lazy(() => import("./user/pages/Auth"));
```
- use suspense to render lazy component
```
<main>
<Suspense
fallback={
<div className="center">
<LoadingSpinner />
</div>
}
>
{routes}
</Suspense>
</main>
```
# main 2 approaches
## deploy 2 separated apps
- 1 static hosting server for react deploy
- 1 node.js hosting server
- setup for cors header
# Heroku deploy
- create a new app
- use heroku git
- login
```
heroku login
```
- add env variable
settings > config var
# mongo atlas setup
- open ip to public because heroku has dynamic ip
- you can setup static ip address using package or paid plan
- if ip is public, still you need user name and password to login to mongo atlas
# react
## serve
check build file in local
```
npx serve
```
# firebasetool
- install ( official doc command run into error when firebase init command run)
```
npm install -g firebase-tools
```
## ref
https://dashboard.heroku.com/apps/max-mern-9230930/deploy/heroku-git
|
1.0
|
section13 deploy - # refs
- project have to be root for deployment
https://github.com/SOunit/the_mern_stack_heroku_react
https://github.com/SOunit/the_mern_stack_heroku_node
# deploy steps overview
- develop & test your code
- swap url and credentials to production setting(using environment variables)
- build & deploy
- test deployed app, monitor and adjust
# environment variable
## backend
- nodemon.json
- access data using process.env.KEY_NAME
## frontend
- .env
- REACT_APP_
- all credential file goes to client, web browser. no credential code should be inside the client.
# mongo atlas setup
- create production cluster
- create production user
- limit IP address
- limit service
# react lazy loading
- to minimize initial load content
- use lazy
```
const Users = lazy(() => import("./user/pages/Users"));
const NewPlace = lazy(() => import("./places/pages/NewPlace"));
const UserPlaces = lazy(() => import("./places/pages/UserPlaces"));
const UpdatePlace = lazy(() => import("./places/pages/UpdatePlace"));
const Auth = lazy(() => import("./user/pages/Auth"));
```
- use suspense to render lazy component
```
<main>
<Suspense
fallback={
<div className="center">
<LoadingSpinner />
</div>
}
>
{routes}
</Suspense>
</main>
```
# main 2 approaches
## deploy 2 separated apps
- 1 static hosting server for react deploy
- 1 node.js hosting server
- setup for cors header
# Heroku deploy
- create a new app
- use heroku git
- login
```
heroku login
```
- add env variable
settings > config var
# mongo atlas setup
- open ip to public because heroku has dynamic ip
- you can setup static ip address using package or paid plan
- if ip is public, still you need user name and password to login to mongo atlas
# react
## serve
check build file in local
```
npx serve
```
# firebasetool
- install ( official doc command run into error when firebase init command run)
```
npm install -g firebase-tools
```
## ref
https://dashboard.heroku.com/apps/max-mern-9230930/deploy/heroku-git
|
non_test
|
deploy refs project have to be root for deployment deploy steps overview develop test your code swap url and credentials to production setting using environment variables build deploy test deployed app monitor and adjust environment variable backend nodemon json access data using process env key name frontend env react app all credential file goes to client web browser no credential code should be inside the client mongo atlas setup create production cluster create production user limit ip address limit service react lazy loading to minimize initial load content use lazy const users lazy import user pages users const newplace lazy import places pages newplace const userplaces lazy import places pages userplaces const updateplace lazy import places pages updateplace const auth lazy import user pages auth use suspense to render lazy component suspense fallback routes main approaches deploy separated apps static hosting server for react deploy node js hosting server setup for cors header heroku deploy create a new app use heroku git login heroku login add env variable settings config var mongo atlas setup open ip to public because heroku has dynamic ip you can setup static ip address using package or paid plan if ip is public still you need user name and password to login to mongo atlas react serve check build file in local npx serve firebasetool install official doc command run into error when firebase init command run npm install g firebase tools ref
| 0
|
501,753
| 14,532,803,539
|
IssuesEvent
|
2020-12-14 23:07:26
|
NuGet/Home
|
https://api.github.com/repos/NuGet/Home
|
closed
|
NuGet should not install unlisted packages
|
Category:Customer Sprint Category:Quality Week Functionality:Install Pipeline:Backlog Priority:2 Product:NuGet.exe Product:dotnet.exe
|
NuGet should not install unlisted packages unless the version number is specified. So the following commands should not add an unlisted nuget package:
`dotnet add package <packageID>`
`nuget install <packageID>`
|
1.0
|
NuGet should not install unlisted packages - NuGet should not install unlisted packages unless the version number is specified. So the following commands should not add an unlisted nuget package:
`dotnet add package <packageID>`
`nuget install <packageID>`
|
non_test
|
nuget should not install unlisted packages nuget should not install unlisted packages unless the version number is specified so the following commands should not add an unlisted nuget package dotnet add package nuget install
| 0
|
17,571
| 3,621,533,497
|
IssuesEvent
|
2016-02-09 00:41:37
|
kubernetes/kubernetes
|
https://api.github.com/repos/kubernetes/kubernetes
|
closed
|
GKE upgrade e2e tests leaking target pools, forwarding rules, and firewall rules
|
area/test davidopp kind/flake priority/P1 team/control-plane
|
Our `kubernetes-upgrade-gce` Jenkins job has been broken for quite a while now, and it looks like it's due to target pools and/or forwarding rules leaking and exceeding quota:
```
Sep 2 00:48:45.094: INFO: event for mutability-service-test: {service-controller } creating loadbalancer: creating loadbalancer
Sep 2 00:48:45.094: INFO: event for mutability-service-test: {service-controller } creating loadbalancer failed: error creating load balancer (will retry): failed to create external load balancer for service e2e-tests-services-mrlvq/mutability-service-test: googleapi: Error 403: Quota 'TARGET_POOLS' exceeded. Limit: 50.0
```
I've cleared out the old rules, and I'll try to diagnose what's leaking them and why.
|
1.0
|
GKE upgrade e2e tests leaking target pools, forwarding rules, and firewall rules - Our `kubernetes-upgrade-gce` Jenkins job has been broken for quite a while now, and it looks like it's due to target pools and/or forwarding rules leaking and exceeding quota:
```
Sep 2 00:48:45.094: INFO: event for mutability-service-test: {service-controller } creating loadbalancer: creating loadbalancer
Sep 2 00:48:45.094: INFO: event for mutability-service-test: {service-controller } creating loadbalancer failed: error creating load balancer (will retry): failed to create external load balancer for service e2e-tests-services-mrlvq/mutability-service-test: googleapi: Error 403: Quota 'TARGET_POOLS' exceeded. Limit: 50.0
```
I've cleared out the old rules, and I'll try to diagnose what's leaking them and why.
|
test
|
gke upgrade tests leaking target pools forwarding rules and firewall rules our kubernetes upgrade gce jenkins job has been broken for quite a while now and it looks like it s due to target pools and or forwarding rules leaking and exceeding quota sep info event for mutability service test service controller creating loadbalancer creating loadbalancer sep info event for mutability service test service controller creating loadbalancer failed error creating load balancer will retry failed to create external load balancer for service tests services mrlvq mutability service test googleapi error quota target pools exceeded limit i ve cleared out the old rules and i ll try to diagnose what s leaking them and why
| 1
|
393,029
| 26,969,170,657
|
IssuesEvent
|
2023-02-09 02:16:30
|
ClaireG-J/IntroSE_03
|
https://api.github.com/repos/ClaireG-J/IntroSE_03
|
closed
|
SRS Appendices Completion
|
documentation
|
The SRS Appendices need completion. This includes:
* Appendix A: Glossary
* Appendix B: Analysis Models
* Appendix C: To Be Determined List
|
1.0
|
SRS Appendices Completion - The SRS Appendices need completion. This includes:
* Appendix A: Glossary
* Appendix B: Analysis Models
* Appendix C: To Be Determined List
|
non_test
|
srs appendices completion the srs appendices need completion this includes appendix a glossary appendix b analysis models appendix c to be determined list
| 0
|
172,315
| 21,043,354,843
|
IssuesEvent
|
2022-03-31 14:06:47
|
jgeraigery/dynatrace-service-broker
|
https://api.github.com/repos/jgeraigery/dynatrace-service-broker
|
opened
|
CVE-2015-5346 (High) detected in tomcat-embed-core-8.0.15.jar
|
security vulnerability
|
## CVE-2015-5346 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tomcat-embed-core-8.0.15.jar</b></p></summary>
<p>Core Tomcat implementation</p>
<p>Library home page: <a href="http://tomcat.apache.org/">http://tomcat.apache.org/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.0.15/tomcat-embed-core-8.0.15.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-1.1.9.RELEASE.jar (Root Library)
- spring-boot-starter-tomcat-1.1.9.RELEASE.jar
- :x: **tomcat-embed-core-8.0.15.jar** (Vulnerable Library)
<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>
Session fixation vulnerability in Apache Tomcat 7.x before 7.0.66, 8.x before 8.0.30, and 9.x before 9.0.0.M2, when different session settings are used for deployments of multiple versions of the same web application, might allow remote attackers to hijack web sessions by leveraging use of a requestedSessionSSL field for an unintended request, related to CoyoteAdapter.java and Request.java.
<p>Publish Date: 2016-02-25
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-5346>CVE-2015-5346</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-5346">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-5346</a></p>
<p>Release Date: 2016-02-25</p>
<p>Fix Resolution: org.apache.tomcat.embed:tomcat-embed-core:9.0.0.M21,8.0.30,7.0.66,org.apache.tomcat:tomcat-catalina:9.0.0.M21,8.0.30,7.0.66</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.apache.tomcat.embed","packageName":"tomcat-embed-core","packageVersion":"8.0.15","packageFilePaths":["/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"org.springframework.boot:spring-boot-starter-web:1.1.9.RELEASE;org.springframework.boot:spring-boot-starter-tomcat:1.1.9.RELEASE;org.apache.tomcat.embed:tomcat-embed-core:8.0.15","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.apache.tomcat.embed:tomcat-embed-core:9.0.0.M21,8.0.30,7.0.66,org.apache.tomcat:tomcat-catalina:9.0.0.M21,8.0.30,7.0.66","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2015-5346","vulnerabilityDetails":"Session fixation vulnerability in Apache Tomcat 7.x before 7.0.66, 8.x before 8.0.30, and 9.x before 9.0.0.M2, when different session settings are used for deployments of multiple versions of the same web application, might allow remote attackers to hijack web sessions by leveraging use of a requestedSessionSSL field for an unintended request, related to CoyoteAdapter.java and Request.java.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-5346","cvss3Severity":"high","cvss3Score":"8.1","cvss3Metrics":{"A":"High","AC":"High","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> -->
|
True
|
CVE-2015-5346 (High) detected in tomcat-embed-core-8.0.15.jar - ## CVE-2015-5346 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tomcat-embed-core-8.0.15.jar</b></p></summary>
<p>Core Tomcat implementation</p>
<p>Library home page: <a href="http://tomcat.apache.org/">http://tomcat.apache.org/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.0.15/tomcat-embed-core-8.0.15.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-1.1.9.RELEASE.jar (Root Library)
- spring-boot-starter-tomcat-1.1.9.RELEASE.jar
- :x: **tomcat-embed-core-8.0.15.jar** (Vulnerable Library)
<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>
Session fixation vulnerability in Apache Tomcat 7.x before 7.0.66, 8.x before 8.0.30, and 9.x before 9.0.0.M2, when different session settings are used for deployments of multiple versions of the same web application, might allow remote attackers to hijack web sessions by leveraging use of a requestedSessionSSL field for an unintended request, related to CoyoteAdapter.java and Request.java.
<p>Publish Date: 2016-02-25
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-5346>CVE-2015-5346</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-5346">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-5346</a></p>
<p>Release Date: 2016-02-25</p>
<p>Fix Resolution: org.apache.tomcat.embed:tomcat-embed-core:9.0.0.M21,8.0.30,7.0.66,org.apache.tomcat:tomcat-catalina:9.0.0.M21,8.0.30,7.0.66</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.apache.tomcat.embed","packageName":"tomcat-embed-core","packageVersion":"8.0.15","packageFilePaths":["/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"org.springframework.boot:spring-boot-starter-web:1.1.9.RELEASE;org.springframework.boot:spring-boot-starter-tomcat:1.1.9.RELEASE;org.apache.tomcat.embed:tomcat-embed-core:8.0.15","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.apache.tomcat.embed:tomcat-embed-core:9.0.0.M21,8.0.30,7.0.66,org.apache.tomcat:tomcat-catalina:9.0.0.M21,8.0.30,7.0.66","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2015-5346","vulnerabilityDetails":"Session fixation vulnerability in Apache Tomcat 7.x before 7.0.66, 8.x before 8.0.30, and 9.x before 9.0.0.M2, when different session settings are used for deployments of multiple versions of the same web application, might allow remote attackers to hijack web sessions by leveraging use of a requestedSessionSSL field for an unintended request, related to CoyoteAdapter.java and Request.java.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-5346","cvss3Severity":"high","cvss3Score":"8.1","cvss3Metrics":{"A":"High","AC":"High","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> -->
|
non_test
|
cve high detected in tomcat embed core jar cve high severity vulnerability vulnerable library tomcat embed core jar core tomcat implementation library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar dependency hierarchy spring boot starter web release jar root library spring boot starter tomcat release jar x tomcat embed core jar vulnerable library found in base branch master vulnerability details session fixation vulnerability in apache tomcat x before x before and x before when different session settings are used for deployments of multiple versions of the same web application might allow remote attackers to hijack web sessions by leveraging use of a requestedsessionssl field for an unintended request related to coyoteadapter java and request java publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org apache tomcat embed tomcat embed core org apache tomcat tomcat catalina isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree org springframework boot spring boot starter web release org springframework boot spring boot starter tomcat release org apache tomcat embed tomcat embed core isminimumfixversionavailable true minimumfixversion org apache tomcat embed tomcat embed core org apache tomcat tomcat catalina isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails session fixation vulnerability in apache tomcat x before x before and x before when different session settings are used for deployments of multiple versions of the same web application might allow remote attackers to hijack web sessions by leveraging use of a requestedsessionssl field for an unintended request related to coyoteadapter java and request java vulnerabilityurl
| 0
|
659,385
| 21,924,974,781
|
IssuesEvent
|
2022-05-23 02:24:03
|
wintercms/wn-redirect-plugin
|
https://api.github.com/repos/wintercms/wn-redirect-plugin
|
closed
|
Invalid security token error on Statistics page
|
Priority: Medium Status: Completed Type: Bug
|
With latest changes on 1.1.8-dev branch (probably because of https://github.com/wintercms/winter/commit/f79e672a13404bd1bbba6bd0d182fc1fdcdd08e2) it's not possible to view Statistics page of plugin, the AJAX handler error pop-up is shown:
With message "Invalid security token error" and no data is shown/returned (loading indicators are spinning forever).
This happens because on Statistics page AJAX POST requests are made to gather the information so the following check fails:
https://github.com/wintercms/winter/blob/0c5099f0b102fc43634bce01cfeafb1763a39251/modules/backend/classes/Controller.php#L207
|
1.0
|
Invalid security token error on Statistics page - With latest changes on 1.1.8-dev branch (probably because of https://github.com/wintercms/winter/commit/f79e672a13404bd1bbba6bd0d182fc1fdcdd08e2) it's not possible to view Statistics page of plugin, the AJAX handler error pop-up is shown:
With message "Invalid security token error" and no data is shown/returned (loading indicators are spinning forever).
This happens because on Statistics page AJAX POST requests are made to gather the information so the following check fails:
https://github.com/wintercms/winter/blob/0c5099f0b102fc43634bce01cfeafb1763a39251/modules/backend/classes/Controller.php#L207
|
non_test
|
invalid security token error on statistics page with latest changes on dev branch probably because of it s not possible to view statistics page of plugin the ajax handler error pop up is shown with message invalid security token error and no data is shown returned loading indicators are spinning forever this happens because on statistics page ajax post requests are made to gather the information so the following check fails
| 0
|
388,628
| 11,490,036,612
|
IssuesEvent
|
2020-02-11 16:25:57
|
synackray/vcenter-netbox-sync
|
https://api.github.com/repos/synackray/vcenter-netbox-sync
|
closed
|
Query DNS for PTR lookups and populate dns_name field for IP address objects
|
Priority: Medium Status: Completed Type: Enhancement
|
I would like to know if it's possible to add a DNS query for each IP address found, to resolve it's PTR record and store the result to the dns_name field?
|
1.0
|
Query DNS for PTR lookups and populate dns_name field for IP address objects - I would like to know if it's possible to add a DNS query for each IP address found, to resolve it's PTR record and store the result to the dns_name field?
|
non_test
|
query dns for ptr lookups and populate dns name field for ip address objects i would like to know if it s possible to add a dns query for each ip address found to resolve it s ptr record and store the result to the dns name field
| 0
|
107,812
| 9,223,807,386
|
IssuesEvent
|
2019-03-12 05:24:00
|
readsoftware/ReadIssues
|
https://api.github.com/repos/readsoftware/ReadIssues
|
closed
|
Parser, Edition VE - IntraSyllable Compound Break
|
Bug Priority 2 Test V1RC
|
Attempted to import via parser. We want to create a 2 token compound ajav-agreṇa with an intra syllable compound break v-a
Parser creates 2 syllables rather than breaking va across the compound break.
|
1.0
|
Parser, Edition VE - IntraSyllable Compound Break - Attempted to import via parser. We want to create a 2 token compound ajav-agreṇa with an intra syllable compound break v-a
Parser creates 2 syllables rather than breaking va across the compound break.
|
test
|
parser edition ve intrasyllable compound break attempted to import via parser we want to create a token compound ajav agreṇa with an intra syllable compound break v a parser creates syllables rather than breaking va across the compound break
| 1
|
193,569
| 14,657,177,412
|
IssuesEvent
|
2020-12-28 15:02:28
|
github-vet/rangeloop-pointer-findings
|
https://api.github.com/repos/github-vet/rangeloop-pointer-findings
|
closed
|
oasisprotocol/oasis-core: go/runtime/transaction/transaction_test.go; 4 LoC
|
fresh test tiny
|
Found a possible issue in [oasisprotocol/oasis-core](https://www.github.com/oasisprotocol/oasis-core) at [go/runtime/transaction/transaction_test.go](https://github.com/oasisprotocol/oasis-core/blob/adc59680d66890c9613a16f573986dca164109ed/go/runtime/transaction/transaction_test.go#L79-L82)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.
>
[Click here to see the code in its original context.](https://github.com/oasisprotocol/oasis-core/blob/adc59680d66890c9613a16f573986dca164109ed/go/runtime/transaction/transaction_test.go#L79-L82)
<details>
<summary>Click here to show the 4 line(s) of Go which triggered the analyzer.</summary>
```go
for _, checkTx := range testTxns {
require.Contains(t, txnsByHash, checkTx.Hash(), "transaction should exist")
require.True(t, txnsByHash[checkTx.Hash()].Equal(&checkTx), "transaction should have the correct artifacts") // nolint: gosec
}
```
</details>
<details>
<summary>Click here to show extra information the analyzer produced.</summary>
```
No path was found through the callgraph that could lead to a function which writes a pointer argument.
No path was found through the callgraph that could lead to a function which passes a pointer to third-party code.
root signature {Equal 1} was not found in the callgraph; reference was passed directly to third-party code
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: adc59680d66890c9613a16f573986dca164109ed
|
1.0
|
oasisprotocol/oasis-core: go/runtime/transaction/transaction_test.go; 4 LoC -
Found a possible issue in [oasisprotocol/oasis-core](https://www.github.com/oasisprotocol/oasis-core) at [go/runtime/transaction/transaction_test.go](https://github.com/oasisprotocol/oasis-core/blob/adc59680d66890c9613a16f573986dca164109ed/go/runtime/transaction/transaction_test.go#L79-L82)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.
>
[Click here to see the code in its original context.](https://github.com/oasisprotocol/oasis-core/blob/adc59680d66890c9613a16f573986dca164109ed/go/runtime/transaction/transaction_test.go#L79-L82)
<details>
<summary>Click here to show the 4 line(s) of Go which triggered the analyzer.</summary>
```go
for _, checkTx := range testTxns {
require.Contains(t, txnsByHash, checkTx.Hash(), "transaction should exist")
require.True(t, txnsByHash[checkTx.Hash()].Equal(&checkTx), "transaction should have the correct artifacts") // nolint: gosec
}
```
</details>
<details>
<summary>Click here to show extra information the analyzer produced.</summary>
```
No path was found through the callgraph that could lead to a function which writes a pointer argument.
No path was found through the callgraph that could lead to a function which passes a pointer to third-party code.
root signature {Equal 1} was not found in the callgraph; reference was passed directly to third-party code
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: adc59680d66890c9613a16f573986dca164109ed
|
test
|
oasisprotocol oasis core go runtime transaction transaction test go loc found a possible issue in at below is the message reported by the analyzer for this snippet of code beware that the analyzer only reports the first issue it finds so please do not limit your consideration to the contents of the below message click here to show the line s of go which triggered the analyzer go for checktx range testtxns require contains t txnsbyhash checktx hash transaction should exist require true t txnsbyhash equal checktx transaction should have the correct artifacts nolint gosec click here to show extra information the analyzer produced no path was found through the callgraph that could lead to a function which writes a pointer argument no path was found through the callgraph that could lead to a function which passes a pointer to third party code root signature equal was not found in the callgraph reference was passed directly to third party code leave a reaction on this issue to contribute to the project by classifying this instance as a bug mitigated or desirable behavior rocket see the descriptions of the classifications for more information commit id
| 1
|
250,447
| 21,299,821,117
|
IssuesEvent
|
2022-04-15 00:34:13
|
UglyToad/PdfPig
|
https://api.github.com/repos/UglyToad/PdfPig
|
closed
|
Unable to read the file. Throwing error "Value was either too large or too small for an Int32"
|
bug testing
|
Hi,
Thanks for providing us with this great tool.
I'm currently using v 0.1.5 and having an issue when we try to open certain PDF files. Most of the PDF work fine but a small number throws the below error stack.
**_at System.Decimal.ToInt32(Decimal d)
at UglyToad.PdfPig.Tokens.NumericToken.get_Int()
at UglyToad.PdfPig.Encryption.EncryptionDictionaryFactory.Read(DictionaryToken encryptionDictionary, IPdfTokenScanner tokenScanner)
at UglyToad.PdfPig.Parser.PdfDocumentFactory.ParseTrailer(CrossReferenceTable crossReferenceTable, Boolean isLenientParsing, IPdfTokenScanner pdfTokenScanner, EncryptionDictionary& encryptionDictionary)
at UglyToad.PdfPig.Parser.PdfDocumentFactory.OpenDocument(IInputBytes inputBytes, ISeekableTokenScanner scanner, ILog log, Boolean isLenientParsing, IReadOnlyList`1 passwords, Boolean clipPaths)
at UglyToad.PdfPig.Parser.PdfDocumentFactory.Open(IInputBytes inputBytes, ParsingOptions options)
at UglyToad.PdfPig.PdfDocument.Open(Byte[] fileBytes, ParsingOptions options)_**
The above error happen on the below line of code which tries to open the file using bytes or Stream.
_**_PdfDocument document = PdfDocument.Open(verifyFile.fileByte, parOpt);_**_
Please can you help look in to this. Really appreciate your help!
Thanks,
Andy
|
1.0
|
Unable to read the file. Throwing error "Value was either too large or too small for an Int32" - Hi,
Thanks for providing us with this great tool.
I'm currently using v 0.1.5 and having an issue when we try to open certain PDF files. Most of the PDF work fine but a small number throws the below error stack.
**_at System.Decimal.ToInt32(Decimal d)
at UglyToad.PdfPig.Tokens.NumericToken.get_Int()
at UglyToad.PdfPig.Encryption.EncryptionDictionaryFactory.Read(DictionaryToken encryptionDictionary, IPdfTokenScanner tokenScanner)
at UglyToad.PdfPig.Parser.PdfDocumentFactory.ParseTrailer(CrossReferenceTable crossReferenceTable, Boolean isLenientParsing, IPdfTokenScanner pdfTokenScanner, EncryptionDictionary& encryptionDictionary)
at UglyToad.PdfPig.Parser.PdfDocumentFactory.OpenDocument(IInputBytes inputBytes, ISeekableTokenScanner scanner, ILog log, Boolean isLenientParsing, IReadOnlyList`1 passwords, Boolean clipPaths)
at UglyToad.PdfPig.Parser.PdfDocumentFactory.Open(IInputBytes inputBytes, ParsingOptions options)
at UglyToad.PdfPig.PdfDocument.Open(Byte[] fileBytes, ParsingOptions options)_**
The above error happen on the below line of code which tries to open the file using bytes or Stream.
_**_PdfDocument document = PdfDocument.Open(verifyFile.fileByte, parOpt);_**_
Please can you help look in to this. Really appreciate your help!
Thanks,
Andy
|
test
|
unable to read the file throwing error value was either too large or too small for an hi thanks for providing us with this great tool i m currently using v and having an issue when we try to open certain pdf files most of the pdf work fine but a small number throws the below error stack at system decimal decimal d at uglytoad pdfpig tokens numerictoken get int at uglytoad pdfpig encryption encryptiondictionaryfactory read dictionarytoken encryptiondictionary ipdftokenscanner tokenscanner at uglytoad pdfpig parser pdfdocumentfactory parsetrailer crossreferencetable crossreferencetable boolean islenientparsing ipdftokenscanner pdftokenscanner encryptiondictionary encryptiondictionary at uglytoad pdfpig parser pdfdocumentfactory opendocument iinputbytes inputbytes iseekabletokenscanner scanner ilog log boolean islenientparsing ireadonlylist passwords boolean clippaths at uglytoad pdfpig parser pdfdocumentfactory open iinputbytes inputbytes parsingoptions options at uglytoad pdfpig pdfdocument open byte filebytes parsingoptions options the above error happen on the below line of code which tries to open the file using bytes or stream pdfdocument document pdfdocument open verifyfile filebyte paropt please can you help look in to this really appreciate your help thanks andy
| 1
|
221,271
| 7,375,260,769
|
IssuesEvent
|
2018-03-13 23:29:44
|
facelessuser/backrefs
|
https://api.github.com/repos/facelessuser/backrefs
|
closed
|
Handle Unicode strings with true format string logic
|
Enhancement Priority - Medium
|
Regex, when doing format replacements, allows for `!s`, `!r`, and `!a` (though `!a` is omitted in PY2).
For completeness, add support for these even if it is unlikely that these would ever be used. There isn't really a practical case for this, it would just be nice if these don't break things.
Regex actually applies these to the capture group except when specifying a sub capture `{1[2]}`. This is weird and I don't care to mimic that, so this will apply to the captured string always.
Due to the complexity of handling string casing, we mimic formatting without actually calling the "format" function on the template's string object. For this reason, formatting actually works in byte strings because our algorithm has no restriction in this case. Even though `{}` style formatting is not officially supported byte strings.
We will most likely implement things like they are in with Python 3.5's `%` style byte string formatting:
- `!r` == `repr(bstring).encode('ascii','backslashreplace')`
- `!a` will work like `!r`
- `!s` probably shouldn't actually be supported as `!b` would actually make more sense, but for now, we'll make this work like this: `bstring.encode('ascii','backslashreplace')` and keep things consistent and not add something new like `!b`.
For Unicode strings, we'll just do the expected things:
- `!s` == `str(string)`
- `!a` == `ascii(string)`
- `!r` == `repr(string)`
|
1.0
|
Handle Unicode strings with true format string logic - Regex, when doing format replacements, allows for `!s`, `!r`, and `!a` (though `!a` is omitted in PY2).
For completeness, add support for these even if it is unlikely that these would ever be used. There isn't really a practical case for this, it would just be nice if these don't break things.
Regex actually applies these to the capture group except when specifying a sub capture `{1[2]}`. This is weird and I don't care to mimic that, so this will apply to the captured string always.
Due to the complexity of handling string casing, we mimic formatting without actually calling the "format" function on the template's string object. For this reason, formatting actually works in byte strings because our algorithm has no restriction in this case. Even though `{}` style formatting is not officially supported byte strings.
We will most likely implement things like they are in with Python 3.5's `%` style byte string formatting:
- `!r` == `repr(bstring).encode('ascii','backslashreplace')`
- `!a` will work like `!r`
- `!s` probably shouldn't actually be supported as `!b` would actually make more sense, but for now, we'll make this work like this: `bstring.encode('ascii','backslashreplace')` and keep things consistent and not add something new like `!b`.
For Unicode strings, we'll just do the expected things:
- `!s` == `str(string)`
- `!a` == `ascii(string)`
- `!r` == `repr(string)`
|
non_test
|
handle unicode strings with true format string logic regex when doing format replacements allows for s r and a though a is omitted in for completeness add support for these even if it is unlikely that these would ever be used there isn t really a practical case for this it would just be nice if these don t break things regex actually applies these to the capture group except when specifying a sub capture this is weird and i don t care to mimic that so this will apply to the captured string always due to the complexity of handling string casing we mimic formatting without actually calling the format function on the template s string object for this reason formatting actually works in byte strings because our algorithm has no restriction in this case even though style formatting is not officially supported byte strings we will most likely implement things like they are in with python s style byte string formatting r repr bstring encode ascii backslashreplace a will work like r s probably shouldn t actually be supported as b would actually make more sense but for now we ll make this work like this bstring encode ascii backslashreplace and keep things consistent and not add something new like b for unicode strings we ll just do the expected things s str string a ascii string r repr string
| 0
|
276,016
| 20,964,146,808
|
IssuesEvent
|
2022-03-28 03:49:48
|
gatsbyjs/gatsby
|
https://api.github.com/repos/gatsbyjs/gatsby
|
closed
|
Shopify no longer uses private apps and passwords
|
type: documentation stale? status: needs more info
|
### Preliminary Checks
- [X] This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/gatsbyjs/gatsby/issues
- [X] This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions
### Summary
Shopify has deprecated the use of private apps as of a couple of months ago. They are now custom apps and no longer use a password, it is just an access token. https://help.shopify.com/en/manual/apps/private-apps
### Steps to Resolve this Issue
1. Update the documentation on this page
2. Update the plugin
|
1.0
|
Shopify no longer uses private apps and passwords - ### Preliminary Checks
- [X] This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/gatsbyjs/gatsby/issues
- [X] This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions
### Summary
Shopify has deprecated the use of private apps as of a couple of months ago. They are now custom apps and no longer use a password, it is just an access token. https://help.shopify.com/en/manual/apps/private-apps
### Steps to Resolve this Issue
1. Update the documentation on this page
2. Update the plugin
|
non_test
|
shopify no longer uses private apps and passwords preliminary checks this issue is not a duplicate before opening a new issue please search existing issues this issue is not a question feature request rfc or anything other than a bug report please post those things in github discussions summary shopify has deprecated the use of private apps as of a couple of months ago they are now custom apps and no longer use a password it is just an access token steps to resolve this issue update the documentation on this page update the plugin
| 0
|
154,592
| 12,220,245,276
|
IssuesEvent
|
2020-05-02 00:36:46
|
Xmetalfanx/linuxSetup
|
https://api.github.com/repos/Xmetalfanx/linuxSetup
|
closed
|
Wine (Default or WineHQ) on Linux Mint
|
Needs Testing Priority
|
I want to check Mint too .. JUST IN CASE there is different code needed vs stock Ubuntu/Ubuntu flavors
|
1.0
|
Wine (Default or WineHQ) on Linux Mint - I want to check Mint too .. JUST IN CASE there is different code needed vs stock Ubuntu/Ubuntu flavors
|
test
|
wine default or winehq on linux mint i want to check mint too just in case there is different code needed vs stock ubuntu ubuntu flavors
| 1
|
219,089
| 17,063,502,828
|
IssuesEvent
|
2021-07-07 02:32:10
|
Azure/azure-sdk-for-python
|
https://api.github.com/repos/Azure/azure-sdk-for-python
|
closed
|
Container Repository samples issues
|
Client Container Repository needs-team-triage test-manual-pass
|
1.
Section [link1](https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/containerregistry/azure-containerregistry/samples/sample_delete_old_tags.py#L48):
Reason1:
for tag in tags[3:]:
TypeError: 'ItemPaged' object is not subscriptable.
Suggestion1:
Update to:
```
for tag in client.list_tag_properties(repository, order_by=TagOrder.LAST_UPDATE_TIME_DESCENDING):
tag_count += 1
if tag_count > 3:
client.delete_tag(repository, tag.name)
```
Suggestion2:
Add code:
```
if __name__ == "__main__":
sample = DeleteOperations()
sample.delete_old_tags()
```
2.
Section [link](https://github.com/Azure/azure-sdk-for-python/blob/master/sdk/containerregistry/azure-containerregistry/samples/async_samples/sample_delete_old_tags_async.py#L62):
Suggestion:
Add `await` before `sample.delete_old_tags()`.
@jongio for notification.
|
1.0
|
Container Repository samples issues - 1.
Section [link1](https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/containerregistry/azure-containerregistry/samples/sample_delete_old_tags.py#L48):
Reason1:
for tag in tags[3:]:
TypeError: 'ItemPaged' object is not subscriptable.
Suggestion1:
Update to:
```
for tag in client.list_tag_properties(repository, order_by=TagOrder.LAST_UPDATE_TIME_DESCENDING):
tag_count += 1
if tag_count > 3:
client.delete_tag(repository, tag.name)
```
Suggestion2:
Add code:
```
if __name__ == "__main__":
sample = DeleteOperations()
sample.delete_old_tags()
```
2.
Section [link](https://github.com/Azure/azure-sdk-for-python/blob/master/sdk/containerregistry/azure-containerregistry/samples/async_samples/sample_delete_old_tags_async.py#L62):
Suggestion:
Add `await` before `sample.delete_old_tags()`.
@jongio for notification.
|
test
|
container repository samples issues section for tag in tags typeerror itempaged object is not subscriptable update to for tag in client list tag properties repository order by tagorder last update time descending tag count if tag count client delete tag repository tag name add code if name main sample deleteoperations sample delete old tags section suggestion add await before sample delete old tags jongio for notification
| 1
|
31,792
| 12,017,061,065
|
IssuesEvent
|
2020-04-10 17:30:52
|
shehackspurple/dotnetcore-webapp
|
https://api.github.com/repos/shehackspurple/dotnetcore-webapp
|
opened
|
CVE-2012-0007 (Medium) detected in antixss.4.0.1.nupkg
|
security vulnerability
|
## CVE-2012-0007 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>antixss.4.0.1.nupkg</b></p></summary>
<p>AntiXSS is an encoding library which uses a safe list approach to encoding. It provides Html, XML, U...</p>
<p>Library home page: <a href="https://api.nuget.org/packages/antixss.4.0.1.nupkg">https://api.nuget.org/packages/antixss.4.0.1.nupkg</a></p>
<p>Path to dependency file: /tmp/ws-scm/dotnetcore-webapp/dotnetcore-webapp.csproj</p>
<p>Path to vulnerable library: /dotnetcore-webapp/dotnetcore-webapp.csproj</p>
<p>
Dependency Hierarchy:
- :x: **antixss.4.0.1.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shehackspurple/dotnetcore-webapp/commit/d25602766a3eb2c75b117b5e1b558f10498b53c4">d25602766a3eb2c75b117b5e1b558f10498b53c4</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The Microsoft Anti-Cross Site Scripting (AntiXSS) Library 3.x and 4.0 does not properly evaluate characters after the detection of a Cascading Style Sheets (CSS) escaped character, which allows remote attackers to conduct cross-site scripting (XSS) attacks via HTML input, aka "AntiXSS Library Bypass Vulnerability."
<p>Publish Date: 2012-01-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-0007>CVE-2012-0007</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>4.3</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="http://www.securitytracker.com/id?1026499">http://www.securitytracker.com/id?1026499</a></p>
<p>Release Date: 2017-12-31</p>
<p>Fix Resolution: The vendor has issued the following fixes:
Microsoft Anti-Cross Site Scripting Library V3.x and Microsoft Anti-Cross Site Scripting Library V4.0:
http://www.microsoft.com/downloads/details.aspx?familyid=b3ef05ce-70fe-4f25-9aee-cb7a42a53d11
The Microsoft advisory is available at:
http://technet.microsoft.com/en-us/security/bulletin/ms12-007</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-2012-0007 (Medium) detected in antixss.4.0.1.nupkg - ## CVE-2012-0007 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>antixss.4.0.1.nupkg</b></p></summary>
<p>AntiXSS is an encoding library which uses a safe list approach to encoding. It provides Html, XML, U...</p>
<p>Library home page: <a href="https://api.nuget.org/packages/antixss.4.0.1.nupkg">https://api.nuget.org/packages/antixss.4.0.1.nupkg</a></p>
<p>Path to dependency file: /tmp/ws-scm/dotnetcore-webapp/dotnetcore-webapp.csproj</p>
<p>Path to vulnerable library: /dotnetcore-webapp/dotnetcore-webapp.csproj</p>
<p>
Dependency Hierarchy:
- :x: **antixss.4.0.1.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shehackspurple/dotnetcore-webapp/commit/d25602766a3eb2c75b117b5e1b558f10498b53c4">d25602766a3eb2c75b117b5e1b558f10498b53c4</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The Microsoft Anti-Cross Site Scripting (AntiXSS) Library 3.x and 4.0 does not properly evaluate characters after the detection of a Cascading Style Sheets (CSS) escaped character, which allows remote attackers to conduct cross-site scripting (XSS) attacks via HTML input, aka "AntiXSS Library Bypass Vulnerability."
<p>Publish Date: 2012-01-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-0007>CVE-2012-0007</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>4.3</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="http://www.securitytracker.com/id?1026499">http://www.securitytracker.com/id?1026499</a></p>
<p>Release Date: 2017-12-31</p>
<p>Fix Resolution: The vendor has issued the following fixes:
Microsoft Anti-Cross Site Scripting Library V3.x and Microsoft Anti-Cross Site Scripting Library V4.0:
http://www.microsoft.com/downloads/details.aspx?familyid=b3ef05ce-70fe-4f25-9aee-cb7a42a53d11
The Microsoft advisory is available at:
http://technet.microsoft.com/en-us/security/bulletin/ms12-007</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_test
|
cve medium detected in antixss nupkg cve medium severity vulnerability vulnerable library antixss nupkg antixss is an encoding library which uses a safe list approach to encoding it provides html xml u library home page a href path to dependency file tmp ws scm dotnetcore webapp dotnetcore webapp csproj path to vulnerable library dotnetcore webapp dotnetcore webapp csproj dependency hierarchy x antixss nupkg vulnerable library found in head commit a href vulnerability details the microsoft anti cross site scripting antixss library x and does not properly evaluate characters after the detection of a cascading style sheets css escaped character which allows remote attackers to conduct cross site scripting xss attacks via html input aka antixss library bypass vulnerability publish date url a href cvss score details base score metrics not available suggested fix type upgrade version origin a href release date fix resolution the vendor has issued the following fixes microsoft anti cross site scripting library x and microsoft anti cross site scripting library the microsoft advisory is available at step up your open source security game with whitesource
| 0
|
213,846
| 16,541,099,435
|
IssuesEvent
|
2021-05-27 16:53:53
|
dotnet/efcore
|
https://api.github.com/repos/dotnet/efcore
|
opened
|
Add code coverage report to AzDo
|
area-test type-enhancement
|
https://docs.microsoft.com/azure/devops/pipelines/tasks/test/publish-code-coverage-results
https://docs.microsoft.com/dotnet/core/testing/unit-testing-code-coverage?tabs=windows
```dotnet test --collect:"XPlat Code Coverage"```
```dotnet test /p:CollectCoverage=true /p:CoverletOutputFormat=cobertura```
Related: https://github.com/dotnet/efcore/issues/22589
|
1.0
|
Add code coverage report to AzDo - https://docs.microsoft.com/azure/devops/pipelines/tasks/test/publish-code-coverage-results
https://docs.microsoft.com/dotnet/core/testing/unit-testing-code-coverage?tabs=windows
```dotnet test --collect:"XPlat Code Coverage"```
```dotnet test /p:CollectCoverage=true /p:CoverletOutputFormat=cobertura```
Related: https://github.com/dotnet/efcore/issues/22589
|
test
|
add code coverage report to azdo dotnet test collect xplat code coverage dotnet test p collectcoverage true p coverletoutputformat cobertura related
| 1
|
94,144
| 8,474,385,727
|
IssuesEvent
|
2018-10-24 16:01:15
|
aspnet/AspNetCore
|
https://api.github.com/repos/aspnet/AspNetCore
|
closed
|
Test failure: TestLogEscapesIllegalFileNames
|
Branch:master Branch:release/2.2 test-failure
|
This issue was made automatically. If there is a problem contact ryanbrandenburg.
This test [failed](https://dnceng.visualstudio.com/9ee6d478-d288-47f7-aacc-f6e6d082ae6d/_build/results?buildId=33625) with the following error:
```
Assert.Equal() Failure
↓ (pos 7)
Expected: Testing-https_localhost_5000
Actual: Testingst_5000
↑ (pos 7)
```
Other tests within that build may have failed with a similar message, but they are not listed here. Check the link above for more info.
This test failed on master.
CC Eilon
|
1.0
|
Test failure: TestLogEscapesIllegalFileNames - This issue was made automatically. If there is a problem contact ryanbrandenburg.
This test [failed](https://dnceng.visualstudio.com/9ee6d478-d288-47f7-aacc-f6e6d082ae6d/_build/results?buildId=33625) with the following error:
```
Assert.Equal() Failure
↓ (pos 7)
Expected: Testing-https_localhost_5000
Actual: Testingst_5000
↑ (pos 7)
```
Other tests within that build may have failed with a similar message, but they are not listed here. Check the link above for more info.
This test failed on master.
CC Eilon
|
test
|
test failure testlogescapesillegalfilenames this issue was made automatically if there is a problem contact ryanbrandenburg this test with the following error assert equal failure ↓ pos expected testing https localhost actual testingst ↑ pos other tests within that build may have failed with a similar message but they are not listed here check the link above for more info this test failed on master cc eilon
| 1
|
190,936
| 14,589,250,041
|
IssuesEvent
|
2020-12-19 01:06:30
|
kalexmills/github-vet-tests-dec2020
|
https://api.github.com/repos/kalexmills/github-vet-tests-dec2020
|
closed
|
terraform-providers/terraform-provider-oci: oci/analytics_analytics_instance_test.go; 16 LoC
|
fresh small test
|
Found a possible issue in [terraform-providers/terraform-provider-oci](https://www.github.com/terraform-providers/terraform-provider-oci) at [oci/analytics_analytics_instance_test.go](https://github.com/terraform-providers/terraform-provider-oci/blob/507acd0ed6517dbca2fbcfb8100874929c8fd8e1/oci/analytics_analytics_instance_test.go#L512-L527)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first
issue it finds, so please do not limit your consideration to the contents of the below message.
> reference to analyticsInstanceId is reassigned at line 516
[Click here to see the code in its original context.](https://github.com/terraform-providers/terraform-provider-oci/blob/507acd0ed6517dbca2fbcfb8100874929c8fd8e1/oci/analytics_analytics_instance_test.go#L512-L527)
<details>
<summary>Click here to show the 16 line(s) of Go which triggered the analyzer.</summary>
```go
for _, analyticsInstanceId := range analyticsInstanceIds {
if ok := SweeperDefaultResourceId[analyticsInstanceId]; !ok {
deleteAnalyticsInstanceRequest := oci_analytics.DeleteAnalyticsInstanceRequest{}
deleteAnalyticsInstanceRequest.AnalyticsInstanceId = &analyticsInstanceId
deleteAnalyticsInstanceRequest.RequestMetadata.RetryPolicy = getRetryPolicy(true, "analytics")
_, error := analyticsClient.DeleteAnalyticsInstance(context.Background(), deleteAnalyticsInstanceRequest)
if error != nil {
fmt.Printf("Error deleting AnalyticsInstance %s %s, It is possible that the resource is already deleted. Please verify manually \n", analyticsInstanceId, error)
continue
}
waitTillCondition(testAccProvider, &analyticsInstanceId, analyticsInstanceSweepWaitCondition, time.Duration(3*time.Minute),
analyticsInstanceSweepResponseFetchOperation, "analytics", true)
}
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: 507acd0ed6517dbca2fbcfb8100874929c8fd8e1
|
1.0
|
terraform-providers/terraform-provider-oci: oci/analytics_analytics_instance_test.go; 16 LoC -
Found a possible issue in [terraform-providers/terraform-provider-oci](https://www.github.com/terraform-providers/terraform-provider-oci) at [oci/analytics_analytics_instance_test.go](https://github.com/terraform-providers/terraform-provider-oci/blob/507acd0ed6517dbca2fbcfb8100874929c8fd8e1/oci/analytics_analytics_instance_test.go#L512-L527)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first
issue it finds, so please do not limit your consideration to the contents of the below message.
> reference to analyticsInstanceId is reassigned at line 516
[Click here to see the code in its original context.](https://github.com/terraform-providers/terraform-provider-oci/blob/507acd0ed6517dbca2fbcfb8100874929c8fd8e1/oci/analytics_analytics_instance_test.go#L512-L527)
<details>
<summary>Click here to show the 16 line(s) of Go which triggered the analyzer.</summary>
```go
for _, analyticsInstanceId := range analyticsInstanceIds {
if ok := SweeperDefaultResourceId[analyticsInstanceId]; !ok {
deleteAnalyticsInstanceRequest := oci_analytics.DeleteAnalyticsInstanceRequest{}
deleteAnalyticsInstanceRequest.AnalyticsInstanceId = &analyticsInstanceId
deleteAnalyticsInstanceRequest.RequestMetadata.RetryPolicy = getRetryPolicy(true, "analytics")
_, error := analyticsClient.DeleteAnalyticsInstance(context.Background(), deleteAnalyticsInstanceRequest)
if error != nil {
fmt.Printf("Error deleting AnalyticsInstance %s %s, It is possible that the resource is already deleted. Please verify manually \n", analyticsInstanceId, error)
continue
}
waitTillCondition(testAccProvider, &analyticsInstanceId, analyticsInstanceSweepWaitCondition, time.Duration(3*time.Minute),
analyticsInstanceSweepResponseFetchOperation, "analytics", true)
}
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: 507acd0ed6517dbca2fbcfb8100874929c8fd8e1
|
test
|
terraform providers terraform provider oci oci analytics analytics instance test go loc found a possible issue in at below is the message reported by the analyzer for this snippet of code beware that the analyzer only reports the first issue it finds so please do not limit your consideration to the contents of the below message reference to analyticsinstanceid is reassigned at line click here to show the line s of go which triggered the analyzer go for analyticsinstanceid range analyticsinstanceids if ok sweeperdefaultresourceid ok deleteanalyticsinstancerequest oci analytics deleteanalyticsinstancerequest deleteanalyticsinstancerequest analyticsinstanceid analyticsinstanceid deleteanalyticsinstancerequest requestmetadata retrypolicy getretrypolicy true analytics error analyticsclient deleteanalyticsinstance context background deleteanalyticsinstancerequest if error nil fmt printf error deleting analyticsinstance s s it is possible that the resource is already deleted please verify manually n analyticsinstanceid error continue waittillcondition testaccprovider analyticsinstanceid analyticsinstancesweepwaitcondition time duration time minute analyticsinstancesweepresponsefetchoperation analytics true leave a reaction on this issue to contribute to the project by classifying this instance as a bug mitigated or desirable behavior rocket see the descriptions of the classifications for more information commit id
| 1
|
214,214
| 7,267,852,714
|
IssuesEvent
|
2018-02-20 07:43:21
|
webcompat/web-bugs
|
https://api.github.com/repos/webcompat/web-bugs
|
closed
|
www.rakuten.com - site is not usable
|
browser-firefox priority-normal type-stylo
|
<!-- @browser: Firefox 59.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0 -->
<!-- @reported_with: desktop-reporter -->
<!-- @extra_labels: type-stylo -->
**URL**: https://www.rakuten.com/
**Browser / Version**: Firefox 59.0
**Operating System**: Windows 10
**Tested Another Browser**: Unknown
**Problem type**: Site is not usable
**Description**: Access Denied if privacy.firstparty.isolate is enabled on rakuten.com
**Steps to Reproduce**:
Installed 'First-party Isolation' which changed the pref privacy.firstparty.isolate .
_From [webcompat.com](https://webcompat.com/) with ❤️_
|
1.0
|
www.rakuten.com - site is not usable - <!-- @browser: Firefox 59.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0 -->
<!-- @reported_with: desktop-reporter -->
<!-- @extra_labels: type-stylo -->
**URL**: https://www.rakuten.com/
**Browser / Version**: Firefox 59.0
**Operating System**: Windows 10
**Tested Another Browser**: Unknown
**Problem type**: Site is not usable
**Description**: Access Denied if privacy.firstparty.isolate is enabled on rakuten.com
**Steps to Reproduce**:
Installed 'First-party Isolation' which changed the pref privacy.firstparty.isolate .
_From [webcompat.com](https://webcompat.com/) with ❤️_
|
non_test
|
site is not usable url browser version firefox operating system windows tested another browser unknown problem type site is not usable description access denied if privacy firstparty isolate is enabled on rakuten com steps to reproduce installed first party isolation which changed the pref privacy firstparty isolate from with ❤️
| 0
|
200,336
| 15,100,241,942
|
IssuesEvent
|
2021-02-08 05:01:33
|
kubernetes/test-infra
|
https://api.github.com/repos/kubernetes/test-infra
|
closed
|
Don't suggest a reviewer I've already assigned.
|
area/prow kind/bug lifecycle/rotten sig/contributor-experience sig/testing
|
```
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: ixdy, mml
We suggest the following additional approver: roberthbailey
Assign the PR to them by writing /assign @roberthbailey in a comment when ready.
```
roberthbailey was already assigned when the bot [said that](https://github.com/kubernetes/kubernetes/pull/51649#issuecomment-326140621)
|
1.0
|
Don't suggest a reviewer I've already assigned. - ```
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: ixdy, mml
We suggest the following additional approver: roberthbailey
Assign the PR to them by writing /assign @roberthbailey in a comment when ready.
```
roberthbailey was already assigned when the bot [said that](https://github.com/kubernetes/kubernetes/pull/51649#issuecomment-326140621)
|
test
|
don t suggest a reviewer i ve already assigned this pr is not approved this pull request has been approved by ixdy mml we suggest the following additional approver roberthbailey assign the pr to them by writing assign roberthbailey in a comment when ready roberthbailey was already assigned when the bot
| 1
|
66,292
| 3,252,067,682
|
IssuesEvent
|
2015-10-19 13:21:24
|
cs2103aug2015-t09-4j/main
|
https://api.github.com/repos/cs2103aug2015-t09-4j/main
|
closed
|
A user can perform instructions in just one line of command
|
priority.high type.story
|
...so that one is able to efficiently form the task manager
|
1.0
|
A user can perform instructions in just one line of command - ...so that one is able to efficiently form the task manager
|
non_test
|
a user can perform instructions in just one line of command so that one is able to efficiently form the task manager
| 0
|
288,388
| 24,902,617,392
|
IssuesEvent
|
2022-10-28 23:14:54
|
Granulate/gprofiler
|
https://api.github.com/repos/Granulate/gprofiler
|
closed
|
tests: nodejs: flaky attach-maps
|
runtime/nodejs tests
|
See 2 test failures here: https://github.com/Granulate/gprofiler/actions/runs/3243777862/jobs/5320303422. They are flaky.
In both cases, the error is:
```
[2022-10-13 17:29:46,323] WARNING: gprofiler.profilers.node: Could not create debug symbols for pid 22987. Reason: HTTPConnectionPool(host='127.0.0.1', port=9229): Max retries exceeded with url: /json/list (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f1691fd6370>: Failed to establish a new connection: [Errno 111] Connection refused'))
```
At least in one of them, I see this:
```
--------------------------- Captured stdout teardown ---------------------------
stdout:
stderr: Debugger listening on ws://127.0.0.1:9229/19543cbe-cfe6-44e3-9a74-991b667f88e5
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
```
which tells us that the debug port was indeed opened and we did manage to connect to it... So this failure isn't obvious to me. Is it because we wait too little time for the debugger to start?
|
1.0
|
tests: nodejs: flaky attach-maps - See 2 test failures here: https://github.com/Granulate/gprofiler/actions/runs/3243777862/jobs/5320303422. They are flaky.
In both cases, the error is:
```
[2022-10-13 17:29:46,323] WARNING: gprofiler.profilers.node: Could not create debug symbols for pid 22987. Reason: HTTPConnectionPool(host='127.0.0.1', port=9229): Max retries exceeded with url: /json/list (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f1691fd6370>: Failed to establish a new connection: [Errno 111] Connection refused'))
```
At least in one of them, I see this:
```
--------------------------- Captured stdout teardown ---------------------------
stdout:
stderr: Debugger listening on ws://127.0.0.1:9229/19543cbe-cfe6-44e3-9a74-991b667f88e5
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
```
which tells us that the debug port was indeed opened and we did manage to connect to it... So this failure isn't obvious to me. Is it because we wait too little time for the debugger to start?
|
test
|
tests nodejs flaky attach maps see test failures here they are flaky in both cases the error is warning gprofiler profilers node could not create debug symbols for pid reason httpconnectionpool host port max retries exceeded with url json list caused by newconnectionerror failed to establish a new connection connection refused at least in one of them i see this captured stdout teardown stdout stderr debugger listening on ws for help see debugger attached which tells us that the debug port was indeed opened and we did manage to connect to it so this failure isn t obvious to me is it because we wait too little time for the debugger to start
| 1
|
229,807
| 18,434,705,450
|
IssuesEvent
|
2021-10-14 11:45:36
|
apache/shardingsphere
|
https://api.github.com/repos/apache/shardingsphere
|
closed
|
Add unit test for shardingsphere-standalone-mode
|
in: test good first issue
|
Hello, I want to add unit test for shardingsphere-standalone-mode.
- [x] StandalonePersistRepositoryConfigurationYamlSwapper
- [x] StandaloneContextManagerBuilder
|
1.0
|
Add unit test for shardingsphere-standalone-mode - Hello, I want to add unit test for shardingsphere-standalone-mode.
- [x] StandalonePersistRepositoryConfigurationYamlSwapper
- [x] StandaloneContextManagerBuilder
|
test
|
add unit test for shardingsphere standalone mode hello i want to add unit test for shardingsphere standalone mode standalonepersistrepositoryconfigurationyamlswapper standalonecontextmanagerbuilder
| 1
|
127,847
| 10,490,741,570
|
IssuesEvent
|
2019-09-25 09:36:28
|
SAP/cloud-commerce-spartacus-storefront
|
https://api.github.com/repos/SAP/cloud-commerce-spartacus-storefront
|
closed
|
express-checkout.e2e-spec.ts failing
|
e2e-tests express-checkout priority/HIGH type/bug
|
**after merging the new features to develop on sept19 (release 1.2.x) , the following tests have been failing and need to be fixed:
regression/express-checkout.e2e-spec.ts
it's expecting the cart to have 1 product, but the cart is empty, so it fails.
|
1.0
|
express-checkout.e2e-spec.ts failing - **after merging the new features to develop on sept19 (release 1.2.x) , the following tests have been failing and need to be fixed:
regression/express-checkout.e2e-spec.ts
it's expecting the cart to have 1 product, but the cart is empty, so it fails.
|
test
|
express checkout spec ts failing after merging the new features to develop on release x the following tests have been failing and need to be fixed regression express checkout spec ts it s expecting the cart to have product but the cart is empty so it fails
| 1
|
345,212
| 30,792,661,337
|
IssuesEvent
|
2023-07-31 17:20:17
|
MD-Anderson-Bioinformatics/NG-CHM
|
https://api.github.com/repos/MD-Anderson-Bioinformatics/NG-CHM
|
closed
|
Top Items text and lines not properly aligned in pdf.
|
bug pdf 2.20.3 passed retest
|
Top items displayed on Summary Map PDF, but not aligned with lines pointing to corresponding rows and columns on map.
[tcga_rnaseqv2_acc_v2.0_gene_sample (1).pdf](https://github.com/MD-Anderson-Bioinformatics/NG-CHM/files/8092379/tcga_rnaseqv2_acc_v2.0_gene_sample.1.pdf)
|
1.0
|
Top Items text and lines not properly aligned in pdf. - Top items displayed on Summary Map PDF, but not aligned with lines pointing to corresponding rows and columns on map.
[tcga_rnaseqv2_acc_v2.0_gene_sample (1).pdf](https://github.com/MD-Anderson-Bioinformatics/NG-CHM/files/8092379/tcga_rnaseqv2_acc_v2.0_gene_sample.1.pdf)
|
test
|
top items text and lines not properly aligned in pdf top items displayed on summary map pdf but not aligned with lines pointing to corresponding rows and columns on map
| 1
|
770,304
| 27,036,424,754
|
IssuesEvent
|
2023-02-12 20:42:09
|
ut-issl/s2e-core
|
https://api.github.com/repos/ut-issl/s2e-core
|
closed
|
Integrate CMakeList in `library` and `interface`
|
priority::medium major update
|
## Overview
Integrate CMakeList in `library` and `interface`
## Details
`library`と`interface`内のCMakeListは更にその中の細かなディレクトリ毎にCMakeListがある構成だが、他のディレクトリと粒度があっていないし、無駄な気がするので統合したい
## Conditions for close
NA
## Supplement
NA
## Note
NA
|
1.0
|
Integrate CMakeList in `library` and `interface` - ## Overview
Integrate CMakeList in `library` and `interface`
## Details
`library`と`interface`内のCMakeListは更にその中の細かなディレクトリ毎にCMakeListがある構成だが、他のディレクトリと粒度があっていないし、無駄な気がするので統合したい
## Conditions for close
NA
## Supplement
NA
## Note
NA
|
non_test
|
integrate cmakelist in library and interface overview integrate cmakelist in library and interface details library と interface 内のcmakelistは更にその中の細かなディレクトリ毎にcmakelistがある構成だが、他のディレクトリと粒度があっていないし、無駄な気がするので統合したい conditions for close na supplement na note na
| 0
|
445,044
| 31,162,332,645
|
IssuesEvent
|
2023-08-16 16:55:23
|
rancher/qa-tasks
|
https://api.github.com/repos/rancher/qa-tasks
|
closed
|
document `Recovering etcd without a snapshot` for rke2/k3s
|
documentation team/area2 [zube]: Done kind/task
|
Is this "Recovering etcd without a Snapshot" [procedure](https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/restore-rancher-launched-kubernetes-clusters-from-backup#recovering-etcd-without-a-snapshot) (page refers to RKE1) a supported scenario for RKE2/K3s? If so, are there docs/test case or steps I can reference to see what the steps are for RKE2?
|
1.0
|
document `Recovering etcd without a snapshot` for rke2/k3s - Is this "Recovering etcd without a Snapshot" [procedure](https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/restore-rancher-launched-kubernetes-clusters-from-backup#recovering-etcd-without-a-snapshot) (page refers to RKE1) a supported scenario for RKE2/K3s? If so, are there docs/test case or steps I can reference to see what the steps are for RKE2?
|
non_test
|
document recovering etcd without a snapshot for is this recovering etcd without a snapshot page refers to a supported scenario for if so are there docs test case or steps i can reference to see what the steps are for
| 0
|
189,952
| 14,529,340,766
|
IssuesEvent
|
2020-12-14 17:40:40
|
galaxyproject/galaxy
|
https://api.github.com/repos/galaxyproject/galaxy
|
opened
|
Performance Test Suite with High Value Initial Tests
|
area/performance area/testing kind/feature
|
https://github.com/galaxyproject/galaxy/pull/10117 adds a new test suite (lib/galaxy_test/performance) and migrates some older manual performance testing stuff for workflows into a modern, automated pytest framework. I think getting that merged is the first step and then adding a few more test types.
Some high-value possibilities include tests that cover:
- Community workflows
- Subworkflows
- "workflows" (in a broad sense or in the Galaxy sense) with lots of little files/jobss.
- Tools/Jobs that produce a high number of discovered datasets during the
- Something non-job related that we've had problems with in the past - maybe loading a large number workflows/histories/etc... via their index endpoint.
I think for Q1 we should aim to have the suite in the PR merged and available to run against PRs (either have them run on GithubActions with each PR or have a command available so we can run them at a bit of a larger scale "as needed") and add *at least one* more of the test cases from the list above as well as some documentation for writing the tests cases?
|
1.0
|
Performance Test Suite with High Value Initial Tests - https://github.com/galaxyproject/galaxy/pull/10117 adds a new test suite (lib/galaxy_test/performance) and migrates some older manual performance testing stuff for workflows into a modern, automated pytest framework. I think getting that merged is the first step and then adding a few more test types.
Some high-value possibilities include tests that cover:
- Community workflows
- Subworkflows
- "workflows" (in a broad sense or in the Galaxy sense) with lots of little files/jobss.
- Tools/Jobs that produce a high number of discovered datasets during the
- Something non-job related that we've had problems with in the past - maybe loading a large number workflows/histories/etc... via their index endpoint.
I think for Q1 we should aim to have the suite in the PR merged and available to run against PRs (either have them run on GithubActions with each PR or have a command available so we can run them at a bit of a larger scale "as needed") and add *at least one* more of the test cases from the list above as well as some documentation for writing the tests cases?
|
test
|
performance test suite with high value initial tests adds a new test suite lib galaxy test performance and migrates some older manual performance testing stuff for workflows into a modern automated pytest framework i think getting that merged is the first step and then adding a few more test types some high value possibilities include tests that cover community workflows subworkflows workflows in a broad sense or in the galaxy sense with lots of little files jobss tools jobs that produce a high number of discovered datasets during the something non job related that we ve had problems with in the past maybe loading a large number workflows histories etc via their index endpoint i think for we should aim to have the suite in the pr merged and available to run against prs either have them run on githubactions with each pr or have a command available so we can run them at a bit of a larger scale as needed and add at least one more of the test cases from the list above as well as some documentation for writing the tests cases
| 1
|
275,887
| 23,951,519,962
|
IssuesEvent
|
2022-09-12 11:56:36
|
cockroachdb/cockroach
|
https://api.github.com/repos/cockroachdb/cockroach
|
closed
|
roachtest: cdc/initial-scan failed
|
C-test-failure O-robot O-roachtest branch-master release-blocker T-cdc
|
roachtest.cdc/initial-scan [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/6400376?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/6400376?buildTab=artifacts#/cdc/initial-scan) on master @ [a82711442c65cf14489c55041b45b11a1e38415b](https://github.com/cockroachdb/cockroach/commits/a82711442c65cf14489c55041b45b11a1e38415b):
```
| 192.0s 0 1.0 2.4 50.3 50.3 50.3 50.3 delivery
| 192.0s 0 29.0 20.9 24.1 48.2 48.2 48.2 newOrder
| 192.0s 0 2.0 2.1 4.1 6.3 6.3 6.3 orderStatus
| 192.0s 0 25.0 22.0 13.1 16.3 16.8 16.8 payment
| 192.0s 0 1.0 2.2 8.1 8.1 8.1 8.1 stockLevel
| _elapsed___errors__ops/sec(inst)___ops/sec(cum)__p50(ms)__p95(ms)__p99(ms)_pMax(ms)
| 193.0s 0 2.0 2.4 35.7 39.8 39.8 39.8 delivery
| 193.0s 0 23.0 20.9 23.1 30.4 31.5 31.5 newOrder
| 193.0s 0 2.0 2.1 5.5 6.0 6.0 6.0 orderStatus
| 193.0s 0 18.0 22.0 12.6 16.8 22.0 22.0 payment
| 193.0s 0 2.0 2.2 12.1 18.9 18.9 18.9 stockLevel
Wraps: (4) COMMAND_PROBLEM
Wraps: (5) Node 4. Command with error:
| ``````
| ./workload run tpcc --warehouses=100 --duration=30m {pgurl:1-3}
| ``````
Wraps: (6) exit status 1
Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *cluster.WithCommandDetails (4) errors.Cmd (5) *hintdetail.withDetail (6) *exec.ExitError
monitor.go:127,cdc.go:300,cdc.go:699,test_runner.go:906: monitor failure: monitor task failed: t.Fatal() was called
(1) attached stack trace
-- stack trace:
| main.(*monitorImpl).WaitE
| main/pkg/cmd/roachtest/monitor.go:115
| main.(*monitorImpl).Wait
| main/pkg/cmd/roachtest/monitor.go:123
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.cdcBasicTest
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/cdc.go:300
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.registerCDC.func3
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/cdc.go:699
| main.(*testRunner).runTest.func2
| main/pkg/cmd/roachtest/test_runner.go:906
Wraps: (2) monitor failure
Wraps: (3) attached stack trace
-- stack trace:
| main.(*monitorImpl).wait.func2
| main/pkg/cmd/roachtest/monitor.go:171
Wraps: (4) monitor task failed
Wraps: (5) attached stack trace
-- stack trace:
| main.init
| main/pkg/cmd/roachtest/monitor.go:80
| runtime.doInit
| GOROOT/src/runtime/proc.go:6340
| runtime.main
| GOROOT/src/runtime/proc.go:233
| runtime.goexit
| GOROOT/src/runtime/asm_amd64.s:1594
Wraps: (6) t.Fatal() was called
Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *withstack.withStack (4) *errutil.withPrefix (5) *withstack.withStack (6) *errutil.leafError
```
<p>Parameters: <code>ROACHTEST_cloud=gce</code>
, <code>ROACHTEST_cpu=16</code>
, <code>ROACHTEST_ssd=0</code>
</p>
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/cdc
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*cdc/initial-scan.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-19472
|
2.0
|
roachtest: cdc/initial-scan failed - roachtest.cdc/initial-scan [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/6400376?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/6400376?buildTab=artifacts#/cdc/initial-scan) on master @ [a82711442c65cf14489c55041b45b11a1e38415b](https://github.com/cockroachdb/cockroach/commits/a82711442c65cf14489c55041b45b11a1e38415b):
```
| 192.0s 0 1.0 2.4 50.3 50.3 50.3 50.3 delivery
| 192.0s 0 29.0 20.9 24.1 48.2 48.2 48.2 newOrder
| 192.0s 0 2.0 2.1 4.1 6.3 6.3 6.3 orderStatus
| 192.0s 0 25.0 22.0 13.1 16.3 16.8 16.8 payment
| 192.0s 0 1.0 2.2 8.1 8.1 8.1 8.1 stockLevel
| _elapsed___errors__ops/sec(inst)___ops/sec(cum)__p50(ms)__p95(ms)__p99(ms)_pMax(ms)
| 193.0s 0 2.0 2.4 35.7 39.8 39.8 39.8 delivery
| 193.0s 0 23.0 20.9 23.1 30.4 31.5 31.5 newOrder
| 193.0s 0 2.0 2.1 5.5 6.0 6.0 6.0 orderStatus
| 193.0s 0 18.0 22.0 12.6 16.8 22.0 22.0 payment
| 193.0s 0 2.0 2.2 12.1 18.9 18.9 18.9 stockLevel
Wraps: (4) COMMAND_PROBLEM
Wraps: (5) Node 4. Command with error:
| ``````
| ./workload run tpcc --warehouses=100 --duration=30m {pgurl:1-3}
| ``````
Wraps: (6) exit status 1
Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *cluster.WithCommandDetails (4) errors.Cmd (5) *hintdetail.withDetail (6) *exec.ExitError
monitor.go:127,cdc.go:300,cdc.go:699,test_runner.go:906: monitor failure: monitor task failed: t.Fatal() was called
(1) attached stack trace
-- stack trace:
| main.(*monitorImpl).WaitE
| main/pkg/cmd/roachtest/monitor.go:115
| main.(*monitorImpl).Wait
| main/pkg/cmd/roachtest/monitor.go:123
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.cdcBasicTest
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/cdc.go:300
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.registerCDC.func3
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/cdc.go:699
| main.(*testRunner).runTest.func2
| main/pkg/cmd/roachtest/test_runner.go:906
Wraps: (2) monitor failure
Wraps: (3) attached stack trace
-- stack trace:
| main.(*monitorImpl).wait.func2
| main/pkg/cmd/roachtest/monitor.go:171
Wraps: (4) monitor task failed
Wraps: (5) attached stack trace
-- stack trace:
| main.init
| main/pkg/cmd/roachtest/monitor.go:80
| runtime.doInit
| GOROOT/src/runtime/proc.go:6340
| runtime.main
| GOROOT/src/runtime/proc.go:233
| runtime.goexit
| GOROOT/src/runtime/asm_amd64.s:1594
Wraps: (6) t.Fatal() was called
Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *withstack.withStack (4) *errutil.withPrefix (5) *withstack.withStack (6) *errutil.leafError
```
<p>Parameters: <code>ROACHTEST_cloud=gce</code>
, <code>ROACHTEST_cpu=16</code>
, <code>ROACHTEST_ssd=0</code>
</p>
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/cdc
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*cdc/initial-scan.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-19472
|
test
|
roachtest cdc initial scan failed roachtest cdc initial scan with on master delivery neworder orderstatus payment stocklevel elapsed errors ops sec inst ops sec cum ms ms ms pmax ms delivery neworder orderstatus payment stocklevel wraps command problem wraps node command with error workload run tpcc warehouses duration pgurl wraps exit status error types withstack withstack errutil withprefix cluster withcommanddetails errors cmd hintdetail withdetail exec exiterror monitor go cdc go cdc go test runner go monitor failure monitor task failed t fatal was called attached stack trace stack trace main monitorimpl waite main pkg cmd roachtest monitor go main monitorimpl wait main pkg cmd roachtest monitor go github com cockroachdb cockroach pkg cmd roachtest tests cdcbasictest github com cockroachdb cockroach pkg cmd roachtest tests cdc go github com cockroachdb cockroach pkg cmd roachtest tests registercdc github com cockroachdb cockroach pkg cmd roachtest tests cdc go main testrunner runtest main pkg cmd roachtest test runner go wraps monitor failure wraps attached stack trace stack trace main monitorimpl wait main pkg cmd roachtest monitor go wraps monitor task failed wraps attached stack trace stack trace main init main pkg cmd roachtest monitor go runtime doinit goroot src runtime proc go runtime main goroot src runtime proc go runtime goexit goroot src runtime asm s wraps t fatal was called error types withstack withstack errutil withprefix withstack withstack errutil withprefix withstack withstack errutil leaferror parameters roachtest cloud gce roachtest cpu roachtest ssd help see see cc cockroachdb cdc jira issue crdb
| 1
|
42,483
| 22,628,385,561
|
IssuesEvent
|
2022-06-30 12:46:05
|
KSPModdingLibs/KSPCommunityFixes
|
https://api.github.com/repos/KSPModdingLibs/KSPCommunityFixes
|
closed
|
KSP memory leaks
|
kspBug kspPerformance
|
KSP is leaking managed memory from various places, but mainly due to GameEvents delegates that are never removed.
Worst offender by far is the `PartSet` class which is holding `Part` references, is instantiated (massively) and owned by a bunch of classes (`ShipConstruct`, `Vessel`, `Part`...) and is subscribing to 2 `GameEvents`. It attempts to unsubscribe from those `GameEvents` with a GC finalizer, which obviously doesn't work since the `GameEvents` subscriptions are preventing those objects from being collected in the first place.
There are many other offenders, with the end result being that all `Vessel` or `Part` ever instantiated will actually **never** be collected. Since those are rather top level objects themself holding a rather large reference tree, the end result is an ever ballooning heap allocated memory. On average, for a stock game (figures will likely be much higher with mods), every part ever instantiated will cause a permanent leak of ~0.2MB.
As shown in the following table, quick-loading the same flight scene with a ~150 parts vessel causes a leak of about ~30 MB per scene switch. After 17 scene switches, about 450 MB of memory is forever lost.
|Scene load #|GameEvents callbacks (Stock)|GameEvents callbacks (KSPCF)|Allocated heap (MB) (Stock)|Allocated heap (MB) (KSPCF)|Leaks (MB) (Stock)|Leaks (MB) (KSPCF)|
|------------|----------------------------|----------------------------|---------------------------|---------------------------|------------------|------------------|
|1 |3142 |1020 |742,0 |783,5 | | |
|2 |5268 |1024 |805,1 |856,4 | | |
|3 |7394 |1046 |834,2 |878,8 |29,1 |22,3 |
|4 |9520 |1032 |850,5 |882,9 |16,3 |4,1 |
|5 |11646 |1036 |877,8 |874,6 |27,3 |\-8,2 |
|6 |13772 |1040 |906,5 |852,6 |28,7 |\-22,1 |
|7 |15898 |1044 |933,7 |858,9 |27,2 |6,3 |
|8 |18024 |1048 |966,9 |849,7 |33,2 |\-9,2 |
|9 |20150 |1052 |1012,4 |880,8 |45,6 |31,2 |
|10 |22276 |1056 |1090,6 |850,4 |78,1 |\-30,4 |
|11 |24402 |1060 |1121,3 |810,7 |30,7 |\-39,8 |
|12 |26528 |1064 |1150,0 |827,2 |28,7 |16,6 |
|13 |28654 |1068 |1179,6 |849,1 |29,7 |21,8 |
|14 |30780 |1072 |1212,4 |891,1 |32,8 |42,1 |
|15 |32906 |1076 |1239,0 |850,4 |26,6 |\-40,7 |
|16 |35032 |1080 |1270,8 |849,4 |31,7 |\-1,0 |
|17 |37158 |1084 |1301,5 |850,0 |30,7 |0,6 |
Note that aside from increasing memory usage, this also cause performance degradation :
- Heap will become more fragmented and GC collections will take longer.
- "Dead" GameEvents delegate are still called, slowing down event processing and potentially causing weird side issues.
The KSPCF **MemoryLeaks** patch add a callback when a scene is exited, and walks through all `GameEvents` delegates to remove entries whose owner is a destroyed `UnityEngine.Object` derivative. There are just to many cases of leaked `GameEvents`, so instead of trying to fix every one of them, this is a cheap way to work around the whole issue. Moreover, this will also cover leaks coming from plugins (which I suspect are even worse offenders than stock).
A specific handling is added for the `PartSet` GameEvents leaks, since the class doesn't derive from `UnityEngine.Object`.
The patch also implement various concrete fixes for a bunch of non-GameEvents related leaks, mainly caused by static fields misuse and lazyness.
|
True
|
KSP memory leaks - KSP is leaking managed memory from various places, but mainly due to GameEvents delegates that are never removed.
Worst offender by far is the `PartSet` class which is holding `Part` references, is instantiated (massively) and owned by a bunch of classes (`ShipConstruct`, `Vessel`, `Part`...) and is subscribing to 2 `GameEvents`. It attempts to unsubscribe from those `GameEvents` with a GC finalizer, which obviously doesn't work since the `GameEvents` subscriptions are preventing those objects from being collected in the first place.
There are many other offenders, with the end result being that all `Vessel` or `Part` ever instantiated will actually **never** be collected. Since those are rather top level objects themself holding a rather large reference tree, the end result is an ever ballooning heap allocated memory. On average, for a stock game (figures will likely be much higher with mods), every part ever instantiated will cause a permanent leak of ~0.2MB.
As shown in the following table, quick-loading the same flight scene with a ~150 parts vessel causes a leak of about ~30 MB per scene switch. After 17 scene switches, about 450 MB of memory is forever lost.
|Scene load #|GameEvents callbacks (Stock)|GameEvents callbacks (KSPCF)|Allocated heap (MB) (Stock)|Allocated heap (MB) (KSPCF)|Leaks (MB) (Stock)|Leaks (MB) (KSPCF)|
|------------|----------------------------|----------------------------|---------------------------|---------------------------|------------------|------------------|
|1 |3142 |1020 |742,0 |783,5 | | |
|2 |5268 |1024 |805,1 |856,4 | | |
|3 |7394 |1046 |834,2 |878,8 |29,1 |22,3 |
|4 |9520 |1032 |850,5 |882,9 |16,3 |4,1 |
|5 |11646 |1036 |877,8 |874,6 |27,3 |\-8,2 |
|6 |13772 |1040 |906,5 |852,6 |28,7 |\-22,1 |
|7 |15898 |1044 |933,7 |858,9 |27,2 |6,3 |
|8 |18024 |1048 |966,9 |849,7 |33,2 |\-9,2 |
|9 |20150 |1052 |1012,4 |880,8 |45,6 |31,2 |
|10 |22276 |1056 |1090,6 |850,4 |78,1 |\-30,4 |
|11 |24402 |1060 |1121,3 |810,7 |30,7 |\-39,8 |
|12 |26528 |1064 |1150,0 |827,2 |28,7 |16,6 |
|13 |28654 |1068 |1179,6 |849,1 |29,7 |21,8 |
|14 |30780 |1072 |1212,4 |891,1 |32,8 |42,1 |
|15 |32906 |1076 |1239,0 |850,4 |26,6 |\-40,7 |
|16 |35032 |1080 |1270,8 |849,4 |31,7 |\-1,0 |
|17 |37158 |1084 |1301,5 |850,0 |30,7 |0,6 |
Note that aside from increasing memory usage, this also cause performance degradation :
- Heap will become more fragmented and GC collections will take longer.
- "Dead" GameEvents delegate are still called, slowing down event processing and potentially causing weird side issues.
The KSPCF **MemoryLeaks** patch add a callback when a scene is exited, and walks through all `GameEvents` delegates to remove entries whose owner is a destroyed `UnityEngine.Object` derivative. There are just to many cases of leaked `GameEvents`, so instead of trying to fix every one of them, this is a cheap way to work around the whole issue. Moreover, this will also cover leaks coming from plugins (which I suspect are even worse offenders than stock).
A specific handling is added for the `PartSet` GameEvents leaks, since the class doesn't derive from `UnityEngine.Object`.
The patch also implement various concrete fixes for a bunch of non-GameEvents related leaks, mainly caused by static fields misuse and lazyness.
|
non_test
|
ksp memory leaks ksp is leaking managed memory from various places but mainly due to gameevents delegates that are never removed worst offender by far is the partset class which is holding part references is instantiated massively and owned by a bunch of classes shipconstruct vessel part and is subscribing to gameevents it attempts to unsubscribe from those gameevents with a gc finalizer which obviously doesn t work since the gameevents subscriptions are preventing those objects from being collected in the first place there are many other offenders with the end result being that all vessel or part ever instantiated will actually never be collected since those are rather top level objects themself holding a rather large reference tree the end result is an ever ballooning heap allocated memory on average for a stock game figures will likely be much higher with mods every part ever instantiated will cause a permanent leak of as shown in the following table quick loading the same flight scene with a parts vessel causes a leak of about mb per scene switch after scene switches about mb of memory is forever lost scene load gameevents callbacks stock gameevents callbacks kspcf allocated heap mb stock allocated heap mb kspcf leaks mb stock leaks mb kspcf note that aside from increasing memory usage this also cause performance degradation heap will become more fragmented and gc collections will take longer dead gameevents delegate are still called slowing down event processing and potentially causing weird side issues the kspcf memoryleaks patch add a callback when a scene is exited and walks through all gameevents delegates to remove entries whose owner is a destroyed unityengine object derivative there are just to many cases of leaked gameevents so instead of trying to fix every one of them this is a cheap way to work around the whole issue moreover this will also cover leaks coming from plugins which i suspect are even worse offenders than stock a specific handling is added for the partset gameevents leaks since the class doesn t derive from unityengine object the patch also implement various concrete fixes for a bunch of non gameevents related leaks mainly caused by static fields misuse and lazyness
| 0
|
309,490
| 26,663,987,077
|
IssuesEvent
|
2023-01-26 00:34:32
|
devssa/onde-codar-em-salvador
|
https://api.github.com/repos/devssa/onde-codar-em-salvador
|
closed
|
[QUALIDADE] [AUTOMACAO] [JUNIOR] [SALVADOR] [TAMBEM PCD] Analista de Qualidade de Software Júnior (Automação) na [CUBOS]
|
SALVADOR JUNIOR MOBILE CASOS DE USO CENÁRIOS DE TESTE QUALIDADE TESTES AUTOMATIZADOS DESENVOLVIMENTO WEB HELP WANTED VAGA PARA PCD TAMBÉM Stale
|
<!--
==================================================
POR FAVOR, SÓ POSTE SE A VAGA FOR PARA SALVADOR E CIDADES VIZINHAS!
Use: "Desenvolvedor Front-end" ao invés de
"Front-End Developer" \o/
Exemplo: `[JAVASCRIPT] [MYSQL] [NODE.JS] Desenvolvedor Front-End na [NOME DA EMPRESA]`
==================================================
-->
## Descrição da vaga
- A Cubos existe para transformar a realidade ao seu redor. Temos um desejo pujante de criar, impactar, aprender e causar uma diferença significativa na vida das pessoas através da tecnologia.
- Nosso alicerce é a educação: somos um hub, absorvendo, compartilhando, produzindo conhecimento. Todo esse conteúdo se reflete nos nossos serviços e produtos, culminando em entregas incríveis, com foco na melhor experiência para o usuário. Vamos além do desenvolvimento. Por isso, não nos limitamos pelo padrão, assumimos riscos que nos dão a adrenalina necessária para alcançar resultados desafiadores. Todos os dias cuidamos das pessoas: aquelas que estão na Cubos; aquelas que são familiares e amigos; aquelas que são parceiros; aquelas que vemos no dia a dia; aquelas que nos tocam.
- Oferecemos um ambiente colaborativo com bastante café, flexibilidade, pessoas incríveis dispostas a aprender e ensinar. Usamos tecnologia porque dá acessibilidade de conhecimento, porque simplifica o mundo, porque tecnologia é sinônimo de evolução, porque tecnologia é consequência da própria existência humana. Criamos tecnologia com significado.
- Como Analista de Qualidade você será responsável por testar e validar as funcionalidades implementadas pelos desenvolvedores (seja melhor amigo dels :P).
### RESPONSABILIDADES E ATRIBUIÇÕES
- Contribuir estrategicamente na elaboração do planejamento e execução de testes visando a qualidade e o prazo;
- Desenvolver casos de uso e cenários para testes;
- Analisar, executar, documentar e sugerir melhorias nos testes conforme casos de testes, condições de testes, etc.;
- Validar a correção dos defeitos e customizações identificados.
## Local
- Salvador
## Benefícios
- Vale refeição ou alimentação;
- Plano de saúde ;
- Plano odontológico;
- Vale transporte;
- Aulas semanais multidisciplinares.
## Requisitos
**Obrigatórios:**
- Conhecimento em automação de testes;
- Experiência com a criação de casos de uso e cenários de testes;
- Conhecimento em testes de aplicação web e mobile;
- Ser curioso(a), inquieto(a) e estar sempre em busca de novas soluções e aprendizados;
- Disposição para ajudar e compartilhar conhecimento.
**Diferenciais:**
- Conhecimento em criação de documento BDD;
- Conhecimento em Agile Test;
- Conhecimento em alguma linguagem de programação.
## Contratação
- a combinar
## Nossa empresa
- A Cubos existe para transformar a realidade ao seu redor. Temos um desejo pujante de criar, impactar, aprender e causar uma diferença significativa na vida das pessoas através da tecnologia.
- Nosso alicerce é a educação: somos um hub, absorvendo, compartilhando, produzindo conhecimento. Todo esse conteúdo se reflete nos nossos serviços e produtos, culminando em entregas incríveis, com foco na melhor experiência para o usuário. Vamos além do desenvolvimento. Por isso, não nos limitamos pelo padrão, assumimos riscos que nos dão a adrenalina necessária para alcançar resultados desafiadores. Todos os dias cuidamos das pessoas: aquelas que estão na Cubos; aquelas que são familiares e amigos; aquelas que são parceiros; aquelas que vemos no dia a dia; aquelas que nos tocam.
- Nossa causa é infinita. Perseguimos três caminhos: construção de negócios, impacto nas empresas e educação das pessoas. Temos bastante energia e leveza para encarar os desafios de cada caminho. E, principalmente, sabemos que estamos com mentes e corações excepcionais lado a lado.
- Criamos porque temos mentes ativas e inquietas, porque vamos a fundo na observação e entendimento de uma situação, porque amamos dar vida a uma solução. Usamos tecnologia porque dá acessibilidade de conhecimento, porque simplifica o mundo, porque tecnologia é sinônimo de evolução, porque tecnologia é consequência da própria existência humana. Imprimimos significado porque nos preocupamos com o impacto das nossas ações, porque temos apreço pela essência de cada produto, porque queremos relevância em tudo o que fazemos.
- Criamos tecnologia com significado.
## Como se candidatar
- [Clique aqui para se candidatar](https://cubos.gupy.io/jobs/434583?jobBoardSource=gupy_public_page)
|
2.0
|
[QUALIDADE] [AUTOMACAO] [JUNIOR] [SALVADOR] [TAMBEM PCD] Analista de Qualidade de Software Júnior (Automação) na [CUBOS] - <!--
==================================================
POR FAVOR, SÓ POSTE SE A VAGA FOR PARA SALVADOR E CIDADES VIZINHAS!
Use: "Desenvolvedor Front-end" ao invés de
"Front-End Developer" \o/
Exemplo: `[JAVASCRIPT] [MYSQL] [NODE.JS] Desenvolvedor Front-End na [NOME DA EMPRESA]`
==================================================
-->
## Descrição da vaga
- A Cubos existe para transformar a realidade ao seu redor. Temos um desejo pujante de criar, impactar, aprender e causar uma diferença significativa na vida das pessoas através da tecnologia.
- Nosso alicerce é a educação: somos um hub, absorvendo, compartilhando, produzindo conhecimento. Todo esse conteúdo se reflete nos nossos serviços e produtos, culminando em entregas incríveis, com foco na melhor experiência para o usuário. Vamos além do desenvolvimento. Por isso, não nos limitamos pelo padrão, assumimos riscos que nos dão a adrenalina necessária para alcançar resultados desafiadores. Todos os dias cuidamos das pessoas: aquelas que estão na Cubos; aquelas que são familiares e amigos; aquelas que são parceiros; aquelas que vemos no dia a dia; aquelas que nos tocam.
- Oferecemos um ambiente colaborativo com bastante café, flexibilidade, pessoas incríveis dispostas a aprender e ensinar. Usamos tecnologia porque dá acessibilidade de conhecimento, porque simplifica o mundo, porque tecnologia é sinônimo de evolução, porque tecnologia é consequência da própria existência humana. Criamos tecnologia com significado.
- Como Analista de Qualidade você será responsável por testar e validar as funcionalidades implementadas pelos desenvolvedores (seja melhor amigo dels :P).
### RESPONSABILIDADES E ATRIBUIÇÕES
- Contribuir estrategicamente na elaboração do planejamento e execução de testes visando a qualidade e o prazo;
- Desenvolver casos de uso e cenários para testes;
- Analisar, executar, documentar e sugerir melhorias nos testes conforme casos de testes, condições de testes, etc.;
- Validar a correção dos defeitos e customizações identificados.
## Local
- Salvador
## Benefícios
- Vale refeição ou alimentação;
- Plano de saúde ;
- Plano odontológico;
- Vale transporte;
- Aulas semanais multidisciplinares.
## Requisitos
**Obrigatórios:**
- Conhecimento em automação de testes;
- Experiência com a criação de casos de uso e cenários de testes;
- Conhecimento em testes de aplicação web e mobile;
- Ser curioso(a), inquieto(a) e estar sempre em busca de novas soluções e aprendizados;
- Disposição para ajudar e compartilhar conhecimento.
**Diferenciais:**
- Conhecimento em criação de documento BDD;
- Conhecimento em Agile Test;
- Conhecimento em alguma linguagem de programação.
## Contratação
- a combinar
## Nossa empresa
- A Cubos existe para transformar a realidade ao seu redor. Temos um desejo pujante de criar, impactar, aprender e causar uma diferença significativa na vida das pessoas através da tecnologia.
- Nosso alicerce é a educação: somos um hub, absorvendo, compartilhando, produzindo conhecimento. Todo esse conteúdo se reflete nos nossos serviços e produtos, culminando em entregas incríveis, com foco na melhor experiência para o usuário. Vamos além do desenvolvimento. Por isso, não nos limitamos pelo padrão, assumimos riscos que nos dão a adrenalina necessária para alcançar resultados desafiadores. Todos os dias cuidamos das pessoas: aquelas que estão na Cubos; aquelas que são familiares e amigos; aquelas que são parceiros; aquelas que vemos no dia a dia; aquelas que nos tocam.
- Nossa causa é infinita. Perseguimos três caminhos: construção de negócios, impacto nas empresas e educação das pessoas. Temos bastante energia e leveza para encarar os desafios de cada caminho. E, principalmente, sabemos que estamos com mentes e corações excepcionais lado a lado.
- Criamos porque temos mentes ativas e inquietas, porque vamos a fundo na observação e entendimento de uma situação, porque amamos dar vida a uma solução. Usamos tecnologia porque dá acessibilidade de conhecimento, porque simplifica o mundo, porque tecnologia é sinônimo de evolução, porque tecnologia é consequência da própria existência humana. Imprimimos significado porque nos preocupamos com o impacto das nossas ações, porque temos apreço pela essência de cada produto, porque queremos relevância em tudo o que fazemos.
- Criamos tecnologia com significado.
## Como se candidatar
- [Clique aqui para se candidatar](https://cubos.gupy.io/jobs/434583?jobBoardSource=gupy_public_page)
|
test
|
analista de qualidade de software júnior automação na por favor só poste se a vaga for para salvador e cidades vizinhas use desenvolvedor front end ao invés de front end developer o exemplo desenvolvedor front end na descrição da vaga a cubos existe para transformar a realidade ao seu redor temos um desejo pujante de criar impactar aprender e causar uma diferença significativa na vida das pessoas através da tecnologia nosso alicerce é a educação somos um hub absorvendo compartilhando produzindo conhecimento todo esse conteúdo se reflete nos nossos serviços e produtos culminando em entregas incríveis com foco na melhor experiência para o usuário vamos além do desenvolvimento por isso não nos limitamos pelo padrão assumimos riscos que nos dão a adrenalina necessária para alcançar resultados desafiadores todos os dias cuidamos das pessoas aquelas que estão na cubos aquelas que são familiares e amigos aquelas que são parceiros aquelas que vemos no dia a dia aquelas que nos tocam oferecemos um ambiente colaborativo com bastante café flexibilidade pessoas incríveis dispostas a aprender e ensinar usamos tecnologia porque dá acessibilidade de conhecimento porque simplifica o mundo porque tecnologia é sinônimo de evolução porque tecnologia é consequência da própria existência humana criamos tecnologia com significado como analista de qualidade você será responsável por testar e validar as funcionalidades implementadas pelos desenvolvedores seja melhor amigo dels p responsabilidades e atribuições contribuir estrategicamente na elaboração do planejamento e execução de testes visando a qualidade e o prazo desenvolver casos de uso e cenários para testes analisar executar documentar e sugerir melhorias nos testes conforme casos de testes condições de testes etc validar a correção dos defeitos e customizações identificados local salvador benefícios vale refeição ou alimentação plano de saúde plano odontológico vale transporte aulas semanais multidisciplinares requisitos obrigatórios conhecimento em automação de testes experiência com a criação de casos de uso e cenários de testes conhecimento em testes de aplicação web e mobile ser curioso a inquieto a e estar sempre em busca de novas soluções e aprendizados disposição para ajudar e compartilhar conhecimento diferenciais conhecimento em criação de documento bdd conhecimento em agile test conhecimento em alguma linguagem de programação contratação a combinar nossa empresa a cubos existe para transformar a realidade ao seu redor temos um desejo pujante de criar impactar aprender e causar uma diferença significativa na vida das pessoas através da tecnologia nosso alicerce é a educação somos um hub absorvendo compartilhando produzindo conhecimento todo esse conteúdo se reflete nos nossos serviços e produtos culminando em entregas incríveis com foco na melhor experiência para o usuário vamos além do desenvolvimento por isso não nos limitamos pelo padrão assumimos riscos que nos dão a adrenalina necessária para alcançar resultados desafiadores todos os dias cuidamos das pessoas aquelas que estão na cubos aquelas que são familiares e amigos aquelas que são parceiros aquelas que vemos no dia a dia aquelas que nos tocam nossa causa é infinita perseguimos três caminhos construção de negócios impacto nas empresas e educação das pessoas temos bastante energia e leveza para encarar os desafios de cada caminho e principalmente sabemos que estamos com mentes e corações excepcionais lado a lado criamos porque temos mentes ativas e inquietas porque vamos a fundo na observação e entendimento de uma situação porque amamos dar vida a uma solução usamos tecnologia porque dá acessibilidade de conhecimento porque simplifica o mundo porque tecnologia é sinônimo de evolução porque tecnologia é consequência da própria existência humana imprimimos significado porque nos preocupamos com o impacto das nossas ações porque temos apreço pela essência de cada produto porque queremos relevância em tudo o que fazemos criamos tecnologia com significado como se candidatar
| 1
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.