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
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
11,391
| 3,488,360,933
|
IssuesEvent
|
2016-01-02 21:59:53
|
blastpad/BlastPad_UI
|
https://api.github.com/repos/blastpad/BlastPad_UI
|
opened
|
Improve Installation Instructions to Documentation
|
documentation
|
Improve the current installation instructions in the Documentation.
Install BlastPad UI and document the process in the documentation.
The documentation page is here:
https://github.com/blastpad/BlastPad_UI/wiki
Simply click edit to start editing or message me for more information.
|
1.0
|
Improve Installation Instructions to Documentation - Improve the current installation instructions in the Documentation.
Install BlastPad UI and document the process in the documentation.
The documentation page is here:
https://github.com/blastpad/BlastPad_UI/wiki
Simply click edit to start editing or message me for more information.
|
non_test
|
improve installation instructions to documentation improve the current installation instructions in the documentation install blastpad ui and document the process in the documentation the documentation page is here simply click edit to start editing or message me for more information
| 0
|
309,608
| 26,669,919,907
|
IssuesEvent
|
2023-01-26 09:21:48
|
cockroachdb/cockroach
|
https://api.github.com/repos/cockroachdb/cockroach
|
opened
|
sql: TestExperimentalRelocateVoters failed
|
C-test-failure O-robot branch-master
|
sql.TestExperimentalRelocateVoters [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/8457692?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/8457692?buildTab=artifacts#/) on master @ [9caf75810ff7dbfa42d16b746c21c86bfa0c6324](https://github.com/cockroachdb/cockroach/commits/9caf75810ff7dbfa42d16b746c21c86bfa0c6324):
```
Goroutine 597754 (running) created at:
github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).RunAsyncTaskEx()
github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:461 +0x619
github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*raftScheduler).Start()
github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/scheduler.go:240 +0x319
github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*Store).processRaft()
github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/store_raft.go:715 +0xe6
github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*Store).Start()
github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/store.go:1886 +0x162a
github.com/cockroachdb/cockroach/pkg/server.(*Node).start()
github.com/cockroachdb/cockroach/pkg/server/node.go:476 +0x14f3
github.com/cockroachdb/cockroach/pkg/server.(*Server).PreStart()
github.com/cockroachdb/cockroach/pkg/server/server.go:1621 +0x3c7a
github.com/cockroachdb/cockroach/pkg/server.(*Server).Start()
github.com/cockroachdb/cockroach/pkg/server/server.go:1181 +0x44
github.com/cockroachdb/cockroach/pkg/server.(*TestServer).Start()
github.com/cockroachdb/cockroach/pkg/server/testserver.go:598 +0x6c
github.com/cockroachdb/cockroach/pkg/testutils/testcluster.(*TestCluster).startServer()
github.com/cockroachdb/cockroach/pkg/testutils/testcluster/testcluster.go:577 +0xd4
github.com/cockroachdb/cockroach/pkg/testutils/testcluster.(*TestCluster).Start()
github.com/cockroachdb/cockroach/pkg/testutils/testcluster/testcluster.go:391 +0x826
github.com/cockroachdb/cockroach/pkg/testutils/testcluster.(*TestCluster).startServer()
github.com/cockroachdb/cockroach/pkg/testutils/testcluster/testcluster.go:577 +0xd4
github.com/cockroachdb/cockroach/pkg/testutils/testcluster.(*TestCluster).Start()
github.com/cockroachdb/cockroach/pkg/testutils/testcluster/testcluster.go:391 +0x826
github.com/cockroachdb/cockroach/pkg/testutils/testcluster.(*TestCluster).startServer()
github.com/cockroachdb/cockroach/pkg/testutils/testcluster/testcluster.go:577 +0xd4
github.com/cockroachdb/cockroach/pkg/testutils/testcluster.(*TestCluster).Start()
github.com/cockroachdb/cockroach/pkg/testutils/testcluster/testcluster.go:391 +0x826
github.com/cockroachdb/cockroach/pkg/server.(*Server).PreStart()
github.com/cockroachdb/cockroach/pkg/server/server.go:1758 +0x505c
github.com/cockroachdb/cockroach/pkg/server.(*Server).Start()
github.com/cockroachdb/cockroach/pkg/server/server.go:1181 +0x44
github.com/cockroachdb/cockroach/pkg/server.(*TestServer).Start()
github.com/cockroachdb/cockroach/pkg/server/testserver.go:598 +0x6c
github.com/cockroachdb/cockroach/pkg/testutils/testcluster.(*TestCluster).startServer()
github.com/cockroachdb/cockroach/pkg/testutils/testcluster/testcluster.go:577 +0xd4
github.com/cockroachdb/cockroach/pkg/testutils/testcluster.(*TestCluster).Start()
github.com/cockroachdb/cockroach/pkg/testutils/testcluster/testcluster.go:391 +0x826
github.com/cockroachdb/cockroach/pkg/testutils/serverutils.StartNewTestCluster()
github.com/cockroachdb/cockroach/pkg/testutils/serverutils/test_cluster_shim.go:266 +0x144
github.com/cockroachdb/cockroach/pkg/sql_test.testCase.runTest()
github.com/cockroachdb/cockroach/pkg/sql_test/pkg/sql/multitenant_admin_function_test.go:255 +0x1e4
github.com/cockroachdb/cockroach/pkg/sql_test.TestExperimentalRelocateVoters.func1()
github.com/cockroachdb/cockroach/pkg/sql_test/pkg/sql/multitenant_admin_function_test.go:715 +0x13b
testing.tRunner()
GOROOT/src/testing/testing.go:1446 +0x216
testing.(*T).Run.func1()
GOROOT/src/testing/testing.go:1493 +0x47
==================
```
<p>Parameters: <code>TAGS=bazel,gss,race</code>
</p>
<details><summary>Help</summary>
<p>
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
</p>
</details>
/cc @cockroachdb/sql-queries
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestExperimentalRelocateVoters.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
|
1.0
|
sql: TestExperimentalRelocateVoters failed - sql.TestExperimentalRelocateVoters [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/8457692?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/8457692?buildTab=artifacts#/) on master @ [9caf75810ff7dbfa42d16b746c21c86bfa0c6324](https://github.com/cockroachdb/cockroach/commits/9caf75810ff7dbfa42d16b746c21c86bfa0c6324):
```
Goroutine 597754 (running) created at:
github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).RunAsyncTaskEx()
github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:461 +0x619
github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*raftScheduler).Start()
github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/scheduler.go:240 +0x319
github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*Store).processRaft()
github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/store_raft.go:715 +0xe6
github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*Store).Start()
github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/store.go:1886 +0x162a
github.com/cockroachdb/cockroach/pkg/server.(*Node).start()
github.com/cockroachdb/cockroach/pkg/server/node.go:476 +0x14f3
github.com/cockroachdb/cockroach/pkg/server.(*Server).PreStart()
github.com/cockroachdb/cockroach/pkg/server/server.go:1621 +0x3c7a
github.com/cockroachdb/cockroach/pkg/server.(*Server).Start()
github.com/cockroachdb/cockroach/pkg/server/server.go:1181 +0x44
github.com/cockroachdb/cockroach/pkg/server.(*TestServer).Start()
github.com/cockroachdb/cockroach/pkg/server/testserver.go:598 +0x6c
github.com/cockroachdb/cockroach/pkg/testutils/testcluster.(*TestCluster).startServer()
github.com/cockroachdb/cockroach/pkg/testutils/testcluster/testcluster.go:577 +0xd4
github.com/cockroachdb/cockroach/pkg/testutils/testcluster.(*TestCluster).Start()
github.com/cockroachdb/cockroach/pkg/testutils/testcluster/testcluster.go:391 +0x826
github.com/cockroachdb/cockroach/pkg/testutils/testcluster.(*TestCluster).startServer()
github.com/cockroachdb/cockroach/pkg/testutils/testcluster/testcluster.go:577 +0xd4
github.com/cockroachdb/cockroach/pkg/testutils/testcluster.(*TestCluster).Start()
github.com/cockroachdb/cockroach/pkg/testutils/testcluster/testcluster.go:391 +0x826
github.com/cockroachdb/cockroach/pkg/testutils/testcluster.(*TestCluster).startServer()
github.com/cockroachdb/cockroach/pkg/testutils/testcluster/testcluster.go:577 +0xd4
github.com/cockroachdb/cockroach/pkg/testutils/testcluster.(*TestCluster).Start()
github.com/cockroachdb/cockroach/pkg/testutils/testcluster/testcluster.go:391 +0x826
github.com/cockroachdb/cockroach/pkg/server.(*Server).PreStart()
github.com/cockroachdb/cockroach/pkg/server/server.go:1758 +0x505c
github.com/cockroachdb/cockroach/pkg/server.(*Server).Start()
github.com/cockroachdb/cockroach/pkg/server/server.go:1181 +0x44
github.com/cockroachdb/cockroach/pkg/server.(*TestServer).Start()
github.com/cockroachdb/cockroach/pkg/server/testserver.go:598 +0x6c
github.com/cockroachdb/cockroach/pkg/testutils/testcluster.(*TestCluster).startServer()
github.com/cockroachdb/cockroach/pkg/testutils/testcluster/testcluster.go:577 +0xd4
github.com/cockroachdb/cockroach/pkg/testutils/testcluster.(*TestCluster).Start()
github.com/cockroachdb/cockroach/pkg/testutils/testcluster/testcluster.go:391 +0x826
github.com/cockroachdb/cockroach/pkg/testutils/serverutils.StartNewTestCluster()
github.com/cockroachdb/cockroach/pkg/testutils/serverutils/test_cluster_shim.go:266 +0x144
github.com/cockroachdb/cockroach/pkg/sql_test.testCase.runTest()
github.com/cockroachdb/cockroach/pkg/sql_test/pkg/sql/multitenant_admin_function_test.go:255 +0x1e4
github.com/cockroachdb/cockroach/pkg/sql_test.TestExperimentalRelocateVoters.func1()
github.com/cockroachdb/cockroach/pkg/sql_test/pkg/sql/multitenant_admin_function_test.go:715 +0x13b
testing.tRunner()
GOROOT/src/testing/testing.go:1446 +0x216
testing.(*T).Run.func1()
GOROOT/src/testing/testing.go:1493 +0x47
==================
```
<p>Parameters: <code>TAGS=bazel,gss,race</code>
</p>
<details><summary>Help</summary>
<p>
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
</p>
</details>
/cc @cockroachdb/sql-queries
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestExperimentalRelocateVoters.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
|
test
|
sql testexperimentalrelocatevoters failed sql testexperimentalrelocatevoters with on master goroutine running created at github com cockroachdb cockroach pkg util stop stopper runasynctaskex github com cockroachdb cockroach pkg util stop stopper go github com cockroachdb cockroach pkg kv kvserver raftscheduler start github com cockroachdb cockroach pkg kv kvserver pkg kv kvserver scheduler go github com cockroachdb cockroach pkg kv kvserver store processraft github com cockroachdb cockroach pkg kv kvserver pkg kv kvserver store raft go github com cockroachdb cockroach pkg kv kvserver store start github com cockroachdb cockroach pkg kv kvserver pkg kv kvserver store go github com cockroachdb cockroach pkg server node start github com cockroachdb cockroach pkg server node go github com cockroachdb cockroach pkg server server prestart github com cockroachdb cockroach pkg server server go github com cockroachdb cockroach pkg server server start github com cockroachdb cockroach pkg server server go github com cockroachdb cockroach pkg server testserver start github com cockroachdb cockroach pkg server testserver go github com cockroachdb cockroach pkg testutils testcluster testcluster startserver github com cockroachdb cockroach pkg testutils testcluster testcluster go github com cockroachdb cockroach pkg testutils testcluster testcluster start github com cockroachdb cockroach pkg testutils testcluster testcluster go github com cockroachdb cockroach pkg testutils testcluster testcluster startserver github com cockroachdb cockroach pkg testutils testcluster testcluster go github com cockroachdb cockroach pkg testutils testcluster testcluster start github com cockroachdb cockroach pkg testutils testcluster testcluster go github com cockroachdb cockroach pkg testutils testcluster testcluster startserver github com cockroachdb cockroach pkg testutils testcluster testcluster go github com cockroachdb cockroach pkg testutils testcluster testcluster start github com cockroachdb cockroach pkg testutils testcluster testcluster go github com cockroachdb cockroach pkg server server prestart github com cockroachdb cockroach pkg server server go github com cockroachdb cockroach pkg server server start github com cockroachdb cockroach pkg server server go github com cockroachdb cockroach pkg server testserver start github com cockroachdb cockroach pkg server testserver go github com cockroachdb cockroach pkg testutils testcluster testcluster startserver github com cockroachdb cockroach pkg testutils testcluster testcluster go github com cockroachdb cockroach pkg testutils testcluster testcluster start github com cockroachdb cockroach pkg testutils testcluster testcluster go github com cockroachdb cockroach pkg testutils serverutils startnewtestcluster github com cockroachdb cockroach pkg testutils serverutils test cluster shim go github com cockroachdb cockroach pkg sql test testcase runtest github com cockroachdb cockroach pkg sql test pkg sql multitenant admin function test go github com cockroachdb cockroach pkg sql test testexperimentalrelocatevoters github com cockroachdb cockroach pkg sql test pkg sql multitenant admin function test go testing trunner goroot src testing testing go testing t run goroot src testing testing go parameters tags bazel gss race help see also cc cockroachdb sql queries
| 1
|
197,872
| 14,946,957,827
|
IssuesEvent
|
2021-01-26 07:50:35
|
knative/eventing
|
https://api.github.com/repos/knative/eventing
|
closed
|
E2E tests dont work on kubernetes 1.20.0
|
area/test-and-release kind/bug priority/awaiting-more-evidence
|
**Describe the bug**
On 1.20.0 (via KIND), the e2e tests are failing:
https://github.com/knative/eventing/pull/4729/checks?check_run_id=1694713248
**Expected behavior**
Works...
**To Reproduce**
Steps to reproduce the behavior.
**Knative release version**
0.20+
|
1.0
|
E2E tests dont work on kubernetes 1.20.0 - **Describe the bug**
On 1.20.0 (via KIND), the e2e tests are failing:
https://github.com/knative/eventing/pull/4729/checks?check_run_id=1694713248
**Expected behavior**
Works...
**To Reproduce**
Steps to reproduce the behavior.
**Knative release version**
0.20+
|
test
|
tests dont work on kubernetes describe the bug on via kind the tests are failing expected behavior works to reproduce steps to reproduce the behavior knative release version
| 1
|
819,935
| 30,756,189,020
|
IssuesEvent
|
2023-07-29 04:33:54
|
primaryodors/primarydock
|
https://api.github.com/repos/primaryodors/primarydock
|
closed
|
An OR has been directly observed in its agonist bound state.
|
high priority
|
https://doi.org/10.1101/2022.12.20.520951
https://www.biorxiv.org/content/10.1101/2022.12.20.520951v1.full.pdf
Protein structure (not yet available): https://www.rcsb.org/structure/unreleased/8F76
The binding site does not consist of the residues identified by Man et al, meaning at least some ORs cannot be predicted using the current prediction attempts. All "method" and "corr" files located in the predict/ folder should now be assumed obsolete.
The binding of propionate in OR51E2 happens in a pocket delineated by F4.57 and L4.60 near the extracellular end of TMR4, aided by hydrogen bonds to Q45.53 and S6.55. H45.52 also appears to coordinate to the ligand, and is experimentally necessary for activation. The charged carboxylic acid group of propionate draws R6.59 nearer to TMR4, causing the extracellular end of TMR6 to rock inwards, accompanied by a counter motion of the cytoplasmic end. This appears to be what activates the receptor.
Propionate and acetate are small molecules that easily fit into this pocket. Larger carboxylic acids do not favor the active configuration. Mutagenesis of F4.57A causes the receptor to respond best to octanoic acid, while the L4.60A mutant prefers hexanoic acid, both in accord with the respectively larger pocket sizes. So it would seem that the ligand must make contact with a threshold surface area of the inside of the pocket, and be small enough to favor the inward motion of the top of TMR6, in order to be an agonist.
Accurate predictions will involve:
- Ensuring that the primarydock app correctly places the ligand into the pocket;
- Ensuring that agonist ligands favor the active state, defined by the rocking motion of TMR6;
- Testing this binding site, and other possible binding sites, for other empirical pairs;
- Identifying any other ways that a ligand might prefer the active position of TMR6.
Note that for thiol-sensitive receptors of the OR2 family, the presence of a copper binding site on TMR5 seems almost certain. How this will interact with the motion of TMR6 is another avenue to explore. Some ORs may have as yet undiscovered metal binding sites that may be revealed by a careful search.
This does not apply to TAARs, VN1Rs, or MS4As. TAARs probably function via their W6.48 trip switch, which ORs lack in favor of a FYG motif. The activation changes for VN1Rs and MS4As are still unknown.
|
1.0
|
An OR has been directly observed in its agonist bound state. - https://doi.org/10.1101/2022.12.20.520951
https://www.biorxiv.org/content/10.1101/2022.12.20.520951v1.full.pdf
Protein structure (not yet available): https://www.rcsb.org/structure/unreleased/8F76
The binding site does not consist of the residues identified by Man et al, meaning at least some ORs cannot be predicted using the current prediction attempts. All "method" and "corr" files located in the predict/ folder should now be assumed obsolete.
The binding of propionate in OR51E2 happens in a pocket delineated by F4.57 and L4.60 near the extracellular end of TMR4, aided by hydrogen bonds to Q45.53 and S6.55. H45.52 also appears to coordinate to the ligand, and is experimentally necessary for activation. The charged carboxylic acid group of propionate draws R6.59 nearer to TMR4, causing the extracellular end of TMR6 to rock inwards, accompanied by a counter motion of the cytoplasmic end. This appears to be what activates the receptor.
Propionate and acetate are small molecules that easily fit into this pocket. Larger carboxylic acids do not favor the active configuration. Mutagenesis of F4.57A causes the receptor to respond best to octanoic acid, while the L4.60A mutant prefers hexanoic acid, both in accord with the respectively larger pocket sizes. So it would seem that the ligand must make contact with a threshold surface area of the inside of the pocket, and be small enough to favor the inward motion of the top of TMR6, in order to be an agonist.
Accurate predictions will involve:
- Ensuring that the primarydock app correctly places the ligand into the pocket;
- Ensuring that agonist ligands favor the active state, defined by the rocking motion of TMR6;
- Testing this binding site, and other possible binding sites, for other empirical pairs;
- Identifying any other ways that a ligand might prefer the active position of TMR6.
Note that for thiol-sensitive receptors of the OR2 family, the presence of a copper binding site on TMR5 seems almost certain. How this will interact with the motion of TMR6 is another avenue to explore. Some ORs may have as yet undiscovered metal binding sites that may be revealed by a careful search.
This does not apply to TAARs, VN1Rs, or MS4As. TAARs probably function via their W6.48 trip switch, which ORs lack in favor of a FYG motif. The activation changes for VN1Rs and MS4As are still unknown.
|
non_test
|
an or has been directly observed in its agonist bound state protein structure not yet available the binding site does not consist of the residues identified by man et al meaning at least some ors cannot be predicted using the current prediction attempts all method and corr files located in the predict folder should now be assumed obsolete the binding of propionate in happens in a pocket delineated by and near the extracellular end of aided by hydrogen bonds to and also appears to coordinate to the ligand and is experimentally necessary for activation the charged carboxylic acid group of propionate draws nearer to causing the extracellular end of to rock inwards accompanied by a counter motion of the cytoplasmic end this appears to be what activates the receptor propionate and acetate are small molecules that easily fit into this pocket larger carboxylic acids do not favor the active configuration mutagenesis of causes the receptor to respond best to octanoic acid while the mutant prefers hexanoic acid both in accord with the respectively larger pocket sizes so it would seem that the ligand must make contact with a threshold surface area of the inside of the pocket and be small enough to favor the inward motion of the top of in order to be an agonist accurate predictions will involve ensuring that the primarydock app correctly places the ligand into the pocket ensuring that agonist ligands favor the active state defined by the rocking motion of testing this binding site and other possible binding sites for other empirical pairs identifying any other ways that a ligand might prefer the active position of note that for thiol sensitive receptors of the family the presence of a copper binding site on seems almost certain how this will interact with the motion of is another avenue to explore some ors may have as yet undiscovered metal binding sites that may be revealed by a careful search this does not apply to taars or taars probably function via their trip switch which ors lack in favor of a fyg motif the activation changes for and are still unknown
| 0
|
21,980
| 3,930,234,553
|
IssuesEvent
|
2016-04-25 06:57:10
|
Microsoft/vscode
|
https://api.github.com/repos/Microsoft/vscode
|
closed
|
Debug Console output not printing output at correct interval
|
debug v-test
|
- VSCode Version: 1.0.1-alpha
- OS Version: Windows 10
Steps to Reproduce:
I was testing in Powershell but I was able to reproduce for Javascript.
1. Add the below code and debug with the Powershell extension
2. Observe the speed of the output numbers.
With Start-Sleep set at 100ms output prints 6 lines per refresh instead of printing one line every 100ms. Set at 200ms, 3 lines are printed per refresh, etc.
```powershell
function Write-Item($itemCount) {
$i = 1
while ($i -le $itemCount) {
$str = "Output $i"
Write-Output $str
# In the gutter on the left, right click and select "Add Conditional Breakpoint"
# on the next line. Use the condition: $i -eq 25
$i = $i + 1
# Slow down execution a bit so user can test the "Pause debugger" feature.
Start-Sleep -Milliseconds 100
}
}
# Do-Work will be underlined in green if you haven't disable script analysis.
# Hover over the function name below to see the PSScriptAnalyzer warning that "Do-Work"
# doesn't use an approved verb.
function Do-Work($workCount) {
Write-Output "Doing work..."
Write-Item $workcount
Write-Host "Done!"
}
Do-Work 50
```
|
1.0
|
Debug Console output not printing output at correct interval - - VSCode Version: 1.0.1-alpha
- OS Version: Windows 10
Steps to Reproduce:
I was testing in Powershell but I was able to reproduce for Javascript.
1. Add the below code and debug with the Powershell extension
2. Observe the speed of the output numbers.
With Start-Sleep set at 100ms output prints 6 lines per refresh instead of printing one line every 100ms. Set at 200ms, 3 lines are printed per refresh, etc.
```powershell
function Write-Item($itemCount) {
$i = 1
while ($i -le $itemCount) {
$str = "Output $i"
Write-Output $str
# In the gutter on the left, right click and select "Add Conditional Breakpoint"
# on the next line. Use the condition: $i -eq 25
$i = $i + 1
# Slow down execution a bit so user can test the "Pause debugger" feature.
Start-Sleep -Milliseconds 100
}
}
# Do-Work will be underlined in green if you haven't disable script analysis.
# Hover over the function name below to see the PSScriptAnalyzer warning that "Do-Work"
# doesn't use an approved verb.
function Do-Work($workCount) {
Write-Output "Doing work..."
Write-Item $workcount
Write-Host "Done!"
}
Do-Work 50
```
|
test
|
debug console output not printing output at correct interval vscode version alpha os version windows steps to reproduce i was testing in powershell but i was able to reproduce for javascript add the below code and debug with the powershell extension observe the speed of the output numbers with start sleep set at output prints lines per refresh instead of printing one line every set at lines are printed per refresh etc powershell function write item itemcount i while i le itemcount str output i write output str in the gutter on the left right click and select add conditional breakpoint on the next line use the condition i eq i i slow down execution a bit so user can test the pause debugger feature start sleep milliseconds do work will be underlined in green if you haven t disable script analysis hover over the function name below to see the psscriptanalyzer warning that do work doesn t use an approved verb function do work workcount write output doing work write item workcount write host done do work
| 1
|
311,038
| 23,367,851,848
|
IssuesEvent
|
2022-08-10 16:55:36
|
open-metadata/OpenMetadata
|
https://api.github.com/repos/open-metadata/OpenMetadata
|
closed
|
Improvement(UI): Make docs styling responsive for better view on mobile devices.
|
documentation UI
|
**Affected module**
UI
**Describe the bug**
The view of the documentation of OM on mobile devices is not proper.
**To Reproduce**
<img width="403" alt="Screenshot 2022-08-10 at 10 22 21 PM" src="https://user-images.githubusercontent.com/51777795/183969600-504f0a12-f2e4-45b4-a08f-1781678a1858.png">
**Expected behavior**
Styling should be proper for better readability on mobile devices.
**Version:**
- OS: [e.g. iOS]
- Python version:
- OpenMetadata version: [e.g. 0.8]
- OpenMetadata Ingestion package version: [e.g. `openmetadata-ingestion[docker]==XYZ`]
**Additional context**
Add any other context about the problem here.
|
1.0
|
Improvement(UI): Make docs styling responsive for better view on mobile devices. - **Affected module**
UI
**Describe the bug**
The view of the documentation of OM on mobile devices is not proper.
**To Reproduce**
<img width="403" alt="Screenshot 2022-08-10 at 10 22 21 PM" src="https://user-images.githubusercontent.com/51777795/183969600-504f0a12-f2e4-45b4-a08f-1781678a1858.png">
**Expected behavior**
Styling should be proper for better readability on mobile devices.
**Version:**
- OS: [e.g. iOS]
- Python version:
- OpenMetadata version: [e.g. 0.8]
- OpenMetadata Ingestion package version: [e.g. `openmetadata-ingestion[docker]==XYZ`]
**Additional context**
Add any other context about the problem here.
|
non_test
|
improvement ui make docs styling responsive for better view on mobile devices affected module ui describe the bug the view of the documentation of om on mobile devices is not proper to reproduce img width alt screenshot at pm src expected behavior styling should be proper for better readability on mobile devices version os python version openmetadata version openmetadata ingestion package version xyz additional context add any other context about the problem here
| 0
|
204,628
| 15,938,128,371
|
IssuesEvent
|
2021-04-14 13:16:15
|
nodeshift/npcheck
|
https://api.github.com/repos/nodeshift/npcheck
|
closed
|
Issue when running npcheck selecting a native-addon
|
documentation
|
`UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'node-rdkafka' of undefined`
npcheck.json:
```js
{
"modules": [
{
"name": "node-rdkafka",
"npmLink": "https://www.npmjs.com/package/node-rdkafka"
}
],
"licenses": {
"allow": ["MIT", "Apache-2.0"]
}
}
```
|
1.0
|
Issue when running npcheck selecting a native-addon - `UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'node-rdkafka' of undefined`
npcheck.json:
```js
{
"modules": [
{
"name": "node-rdkafka",
"npmLink": "https://www.npmjs.com/package/node-rdkafka"
}
],
"licenses": {
"allow": ["MIT", "Apache-2.0"]
}
}
```
|
non_test
|
issue when running npcheck selecting a native addon unhandledpromiserejectionwarning typeerror cannot read property node rdkafka of undefined npcheck json js modules name node rdkafka npmlink licenses allow
| 0
|
105,778
| 16,658,238,437
|
IssuesEvent
|
2021-06-05 23:00:29
|
veritem/rfid_transaction
|
https://api.github.com/repos/veritem/rfid_transaction
|
opened
|
CVE-2021-23382 (Medium) detected in postcss-6.0.23.tgz
|
security vulnerability
|
## CVE-2021-23382 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>postcss-6.0.23.tgz</b></p></summary>
<p>Tool for transforming styles with JS plugins</p>
<p>Library home page: <a href="https://registry.npmjs.org/postcss/-/postcss-6.0.23.tgz">https://registry.npmjs.org/postcss/-/postcss-6.0.23.tgz</a></p>
<p>Path to dependency file: rfid_transaction/frontend/package.json</p>
<p>Path to vulnerable library: rfid_transaction/frontend/node_modules/postcss-functions/node_modules/postcss/package.json</p>
<p>
Dependency Hierarchy:
- tailwindcss-2.1.4.tgz (Root Library)
- postcss-functions-3.0.0.tgz
- :x: **postcss-6.0.23.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/veritem/rfid_transaction/commit/3647288a2edd1c830ab127bf57ab0a0ba7e93f4f">3647288a2edd1c830ab127bf57ab0a0ba7e93f4f</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The package postcss before 8.2.13 are vulnerable to Regular Expression Denial of Service (ReDoS) via getAnnotationURL() and loadAnnotation() in lib/previous-map.js. The vulnerable regexes are caused mainly by the sub-pattern \/\*\s* sourceMappingURL=(.*).
<p>Publish Date: 2021-04-26
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23382>CVE-2021-23382</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23382">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23382</a></p>
<p>Release Date: 2021-04-26</p>
<p>Fix Resolution: postcss - 8.2.13</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2021-23382 (Medium) detected in postcss-6.0.23.tgz - ## CVE-2021-23382 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>postcss-6.0.23.tgz</b></p></summary>
<p>Tool for transforming styles with JS plugins</p>
<p>Library home page: <a href="https://registry.npmjs.org/postcss/-/postcss-6.0.23.tgz">https://registry.npmjs.org/postcss/-/postcss-6.0.23.tgz</a></p>
<p>Path to dependency file: rfid_transaction/frontend/package.json</p>
<p>Path to vulnerable library: rfid_transaction/frontend/node_modules/postcss-functions/node_modules/postcss/package.json</p>
<p>
Dependency Hierarchy:
- tailwindcss-2.1.4.tgz (Root Library)
- postcss-functions-3.0.0.tgz
- :x: **postcss-6.0.23.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/veritem/rfid_transaction/commit/3647288a2edd1c830ab127bf57ab0a0ba7e93f4f">3647288a2edd1c830ab127bf57ab0a0ba7e93f4f</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The package postcss before 8.2.13 are vulnerable to Regular Expression Denial of Service (ReDoS) via getAnnotationURL() and loadAnnotation() in lib/previous-map.js. The vulnerable regexes are caused mainly by the sub-pattern \/\*\s* sourceMappingURL=(.*).
<p>Publish Date: 2021-04-26
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23382>CVE-2021-23382</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23382">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23382</a></p>
<p>Release Date: 2021-04-26</p>
<p>Fix Resolution: postcss - 8.2.13</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 postcss tgz cve medium severity vulnerability vulnerable library postcss tgz tool for transforming styles with js plugins library home page a href path to dependency file rfid transaction frontend package json path to vulnerable library rfid transaction frontend node modules postcss functions node modules postcss package json dependency hierarchy tailwindcss tgz root library postcss functions tgz x postcss tgz vulnerable library found in head commit a href found in base branch main vulnerability details the package postcss before are vulnerable to regular expression denial of service redos via getannotationurl and loadannotation in lib previous map js the vulnerable regexes are caused mainly by the sub pattern s sourcemappingurl publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution postcss step up your open source security game with whitesource
| 0
|
28,598
| 12,890,890,935
|
IssuesEvent
|
2020-07-13 16:45:16
|
elastic/kibana
|
https://api.github.com/repos/elastic/kibana
|
opened
|
Document reporting network policy
|
Team:Reporting Services docs
|
The options for configuring Reporting's network policy are not documented currently. Having docs explaining how and why to use this would help users further secure their Kibana installations.
|
1.0
|
Document reporting network policy - The options for configuring Reporting's network policy are not documented currently. Having docs explaining how and why to use this would help users further secure their Kibana installations.
|
non_test
|
document reporting network policy the options for configuring reporting s network policy are not documented currently having docs explaining how and why to use this would help users further secure their kibana installations
| 0
|
220,850
| 17,264,551,176
|
IssuesEvent
|
2021-07-22 12:17:01
|
Gepardec/mega
|
https://api.github.com/repos/Gepardec/mega
|
closed
|
As OM I want to assign comments to an employee.
|
test failed user story
|
- [x] add the "Anmerkungen" area in the OM-view as in the design (except the icons and the inline comment)
- [x] add one icon (not as in the om_design!) in the OM-view which opens the comment view for one employee
- [x] Comment area (see design): see all notes of the active month and employee (necessary information of comments: Creator, Timestamp, Text, Status)
- [x] the OM is only able to edit and delete the own comments which are not marked as done (e.g. the OM can not edit a comment of the PM)
- [x] As OM I want to add links to the comment (which are shown in a second step in the notification mail as links - not text only)
- [x] As OM I want to have multiple lines in the comment (maybe the design must be adapted)
- [x] As OM I want to add a maximum of 500 letters
- [x] the employee gets within 5 min notified about a new comment (or a change)
|
1.0
|
As OM I want to assign comments to an employee. - - [x] add the "Anmerkungen" area in the OM-view as in the design (except the icons and the inline comment)
- [x] add one icon (not as in the om_design!) in the OM-view which opens the comment view for one employee
- [x] Comment area (see design): see all notes of the active month and employee (necessary information of comments: Creator, Timestamp, Text, Status)
- [x] the OM is only able to edit and delete the own comments which are not marked as done (e.g. the OM can not edit a comment of the PM)
- [x] As OM I want to add links to the comment (which are shown in a second step in the notification mail as links - not text only)
- [x] As OM I want to have multiple lines in the comment (maybe the design must be adapted)
- [x] As OM I want to add a maximum of 500 letters
- [x] the employee gets within 5 min notified about a new comment (or a change)
|
test
|
as om i want to assign comments to an employee add the anmerkungen area in the om view as in the design except the icons and the inline comment add one icon not as in the om design in the om view which opens the comment view for one employee comment area see design see all notes of the active month and employee necessary information of comments creator timestamp text status the om is only able to edit and delete the own comments which are not marked as done e g the om can not edit a comment of the pm as om i want to add links to the comment which are shown in a second step in the notification mail as links not text only as om i want to have multiple lines in the comment maybe the design must be adapted as om i want to add a maximum of letters the employee gets within min notified about a new comment or a change
| 1
|
108,105
| 9,259,908,523
|
IssuesEvent
|
2019-03-18 02:41:37
|
xcat2/xcat-core
|
https://api.github.com/repos/xcat2/xcat-core
|
closed
|
[FVT]:update case xcatconfig_u_check_xcatsslversion_rhels_sles and xcatconfig_u_check_xcatsslversion_ubuntu according to xcatsslversion default value is changed to blank
|
component:test
|
Since xcatsslversion default value is changed in pr https://github.com/xcat2/xcat-core/pull/6061
Need to update case xcatconfig_u_check_xcatsslversion_rhels_sles and xcatconfig_u_check_xcatsslversion_ubuntu
|
1.0
|
[FVT]:update case xcatconfig_u_check_xcatsslversion_rhels_sles and xcatconfig_u_check_xcatsslversion_ubuntu according to xcatsslversion default value is changed to blank - Since xcatsslversion default value is changed in pr https://github.com/xcat2/xcat-core/pull/6061
Need to update case xcatconfig_u_check_xcatsslversion_rhels_sles and xcatconfig_u_check_xcatsslversion_ubuntu
|
test
|
update case xcatconfig u check xcatsslversion rhels sles and xcatconfig u check xcatsslversion ubuntu according to xcatsslversion default value is changed to blank since xcatsslversion default value is changed in pr need to update case xcatconfig u check xcatsslversion rhels sles and xcatconfig u check xcatsslversion ubuntu
| 1
|
205,150
| 15,594,118,174
|
IssuesEvent
|
2021-03-18 13:34:32
|
ESMValGroup/ESMValCore
|
https://api.github.com/repos/ESMValGroup/ESMValCore
|
opened
|
Should we test every PR with Python 3.6?
|
enhancement testing
|
**Is your feature request related to a problem? Please describe.**
The installation guide mentions that we support Python 3.6 and up (https://docs.esmvaltool.org/en/latest/quickstart/installation.html). However, CircleCI runs the test on every commit with a higher version. Actually I'm not sure which version, because it just pulls the docker container (but it's not 3.6).
In my opinion, if we are supporting Python 3.6, we should make sure that we test against 3.6 as the lowest version. This to make sure that we do not 'accidentally' add code or features that are not supported by 3.6, for example in #1042, where this came up.
Note that Python 3.6 support will be dropped later this year (https://endoflife.date/python).
**Would you be able to help out?**
Would you have the time and skills to implement the solution yourself?
|
1.0
|
Should we test every PR with Python 3.6? - **Is your feature request related to a problem? Please describe.**
The installation guide mentions that we support Python 3.6 and up (https://docs.esmvaltool.org/en/latest/quickstart/installation.html). However, CircleCI runs the test on every commit with a higher version. Actually I'm not sure which version, because it just pulls the docker container (but it's not 3.6).
In my opinion, if we are supporting Python 3.6, we should make sure that we test against 3.6 as the lowest version. This to make sure that we do not 'accidentally' add code or features that are not supported by 3.6, for example in #1042, where this came up.
Note that Python 3.6 support will be dropped later this year (https://endoflife.date/python).
**Would you be able to help out?**
Would you have the time and skills to implement the solution yourself?
|
test
|
should we test every pr with python is your feature request related to a problem please describe the installation guide mentions that we support python and up however circleci runs the test on every commit with a higher version actually i m not sure which version because it just pulls the docker container but it s not in my opinion if we are supporting python we should make sure that we test against as the lowest version this to make sure that we do not accidentally add code or features that are not supported by for example in where this came up note that python support will be dropped later this year would you be able to help out would you have the time and skills to implement the solution yourself
| 1
|
184,286
| 14,974,150,907
|
IssuesEvent
|
2021-01-28 02:50:09
|
dianariyanto/virtual-display-linux
|
https://api.github.com/repos/dianariyanto/virtual-display-linux
|
closed
|
How to Undo Changes
|
documentation
|
I ran the script and immediately my computer started hitching in the terminal and weird artifacts appeared on my desktop icons and backgrounds.
How do I revert the changes that the script made?
|
1.0
|
How to Undo Changes - I ran the script and immediately my computer started hitching in the terminal and weird artifacts appeared on my desktop icons and backgrounds.
How do I revert the changes that the script made?
|
non_test
|
how to undo changes i ran the script and immediately my computer started hitching in the terminal and weird artifacts appeared on my desktop icons and backgrounds how do i revert the changes that the script made
| 0
|
8,524
| 2,611,516,288
|
IssuesEvent
|
2015-02-27 05:51:23
|
chrsmith/hedgewars
|
https://api.github.com/repos/chrsmith/hedgewars
|
closed
|
No more std::string in feedbackdialog.cpp
|
auto-migrated Priority-Medium Type-Defect
|
```
What steps will reproduce the problem?
1.
2.
3.
What is the expected output? What do you see instead?
What version of the product are you using? On what operating system?
Hedgewars 0.9.19 "alpha3"
Windows 8 Pro 64bit
Please provide any additional information below.
This issue was mentioned by unC0Rr. I fixed it as Koda requested afterwards.
No more std::string in feedbackdialog.cpp, they were "replaced" with
equivalents from Qt.
```
Original issue reported on code.google.com by `inufa...@gmail.com` on 11 Mar 2013 at 1:42
Attachments:
* [inu_no.more.std-string.diff](https://storage.googleapis.com/google-code-attachments/hedgewars/issue-566/comment-0/inu_no.more.std-string.diff)
|
1.0
|
No more std::string in feedbackdialog.cpp - ```
What steps will reproduce the problem?
1.
2.
3.
What is the expected output? What do you see instead?
What version of the product are you using? On what operating system?
Hedgewars 0.9.19 "alpha3"
Windows 8 Pro 64bit
Please provide any additional information below.
This issue was mentioned by unC0Rr. I fixed it as Koda requested afterwards.
No more std::string in feedbackdialog.cpp, they were "replaced" with
equivalents from Qt.
```
Original issue reported on code.google.com by `inufa...@gmail.com` on 11 Mar 2013 at 1:42
Attachments:
* [inu_no.more.std-string.diff](https://storage.googleapis.com/google-code-attachments/hedgewars/issue-566/comment-0/inu_no.more.std-string.diff)
|
non_test
|
no more std string in feedbackdialog cpp what steps will reproduce the problem what is the expected output what do you see instead what version of the product are you using on what operating system hedgewars windows pro please provide any additional information below this issue was mentioned by i fixed it as koda requested afterwards no more std string in feedbackdialog cpp they were replaced with equivalents from qt original issue reported on code google com by inufa gmail com on mar at attachments
| 0
|
64,602
| 18,759,507,153
|
IssuesEvent
|
2021-11-05 14:55:05
|
vector-im/element-android
|
https://api.github.com/repos/vector-im/element-android
|
closed
|
Video size not reduce after auto compress before send video
|
T-Defect A-VideoCompression
|
### Steps to reproduce
1. Capture video by phone ~74 Mb size
2. Try send from gallery
3. See compressing...
4. See, that sending original size of video - ~74 Mb
### What happened?
Element not reduce size of video before send. But show process "compressing".
### What did you expect?
I expect reduce size of video before send to chat.
### What happened?
Video size not reduced.
### Your phone model
Yotaphone 2
### Operating system version
android 6.0.1
### Application version and app store
Element android gplay 1.2.2
### Homeserver
rsprim.ru
### Have you submitted a rageshake?
Yes
|
1.0
|
Video size not reduce after auto compress before send video - ### Steps to reproduce
1. Capture video by phone ~74 Mb size
2. Try send from gallery
3. See compressing...
4. See, that sending original size of video - ~74 Mb
### What happened?
Element not reduce size of video before send. But show process "compressing".
### What did you expect?
I expect reduce size of video before send to chat.
### What happened?
Video size not reduced.
### Your phone model
Yotaphone 2
### Operating system version
android 6.0.1
### Application version and app store
Element android gplay 1.2.2
### Homeserver
rsprim.ru
### Have you submitted a rageshake?
Yes
|
non_test
|
video size not reduce after auto compress before send video steps to reproduce capture video by phone mb size try send from gallery see compressing see that sending original size of video mb what happened element not reduce size of video before send but show process compressing what did you expect i expect reduce size of video before send to chat what happened video size not reduced your phone model yotaphone operating system version android application version and app store element android gplay homeserver rsprim ru have you submitted a rageshake yes
| 0
|
26,768
| 11,396,105,467
|
IssuesEvent
|
2020-01-30 12:55:07
|
scriptex/AnimateMe
|
https://api.github.com/repos/scriptex/AnimateMe
|
opened
|
CVE-2015-9251 (Medium) detected in jquery-1.11.1.min.js, jquery-1.12.4.min.js
|
security vulnerability
|
## CVE-2015-9251 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>jquery-1.11.1.min.js</b>, <b>jquery-1.12.4.min.js</b></p></summary>
<p>
<details><summary><b>jquery-1.11.1.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.11.1/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.11.1/jquery.min.js</a></p>
<p>Path to dependency file: /tmp/ws-scm/AnimateMe/node_modules/@babel/compat-data/build/compat-table/es2016plus/compiler-skeleton.html</p>
<p>Path to vulnerable library: /AnimateMe/node_modules/@babel/compat-data/build/compat-table/es2016plus/compiler-skeleton.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.11.1.min.js** (Vulnerable Library)
</details>
<details><summary><b>jquery-1.12.4.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.12.4/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.12.4/jquery.min.js</a></p>
<p>Path to dependency file: /tmp/ws-scm/AnimateMe/node_modules/@babel/compat-data/build/compat-table/es2016plus/index.html</p>
<p>Path to vulnerable library: /AnimateMe/node_modules/@babel/compat-data/build/compat-table/es2016plus/index.html,/AnimateMe/node_modules/@babel/compat-data/build/compat-table/es5/skeleton.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.12.4.min.js** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/scriptex/AnimateMe/commit/8195843b5d64a21b9a0c00753c65dc738dd7e968">8195843b5d64a21b9a0c00753c65dc738dd7e968</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>
jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS) attacks when a cross-domain Ajax request is performed without the dataType option, causing text/javascript responses to be executed.
<p>Publish Date: 2018-01-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-9251>CVE-2015-9251</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2015-9251">https://nvd.nist.gov/vuln/detail/CVE-2015-9251</a></p>
<p>Release Date: 2018-01-18</p>
<p>Fix Resolution: jQuery - v3.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2015-9251 (Medium) detected in jquery-1.11.1.min.js, jquery-1.12.4.min.js - ## CVE-2015-9251 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>jquery-1.11.1.min.js</b>, <b>jquery-1.12.4.min.js</b></p></summary>
<p>
<details><summary><b>jquery-1.11.1.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.11.1/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.11.1/jquery.min.js</a></p>
<p>Path to dependency file: /tmp/ws-scm/AnimateMe/node_modules/@babel/compat-data/build/compat-table/es2016plus/compiler-skeleton.html</p>
<p>Path to vulnerable library: /AnimateMe/node_modules/@babel/compat-data/build/compat-table/es2016plus/compiler-skeleton.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.11.1.min.js** (Vulnerable Library)
</details>
<details><summary><b>jquery-1.12.4.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.12.4/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.12.4/jquery.min.js</a></p>
<p>Path to dependency file: /tmp/ws-scm/AnimateMe/node_modules/@babel/compat-data/build/compat-table/es2016plus/index.html</p>
<p>Path to vulnerable library: /AnimateMe/node_modules/@babel/compat-data/build/compat-table/es2016plus/index.html,/AnimateMe/node_modules/@babel/compat-data/build/compat-table/es5/skeleton.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.12.4.min.js** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/scriptex/AnimateMe/commit/8195843b5d64a21b9a0c00753c65dc738dd7e968">8195843b5d64a21b9a0c00753c65dc738dd7e968</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>
jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS) attacks when a cross-domain Ajax request is performed without the dataType option, causing text/javascript responses to be executed.
<p>Publish Date: 2018-01-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-9251>CVE-2015-9251</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2015-9251">https://nvd.nist.gov/vuln/detail/CVE-2015-9251</a></p>
<p>Release Date: 2018-01-18</p>
<p>Fix Resolution: jQuery - v3.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_test
|
cve medium detected in jquery min js jquery min js cve medium severity vulnerability vulnerable libraries jquery min js jquery min js jquery min js javascript library for dom operations library home page a href path to dependency file tmp ws scm animateme node modules babel compat data build compat table compiler skeleton html path to vulnerable library animateme node modules babel compat data build compat table compiler skeleton html dependency hierarchy x jquery min js vulnerable library jquery min js javascript library for dom operations library home page a href path to dependency file tmp ws scm animateme node modules babel compat data build compat table index html path to vulnerable library animateme node modules babel compat data build compat table index html animateme node modules babel compat data build compat table skeleton html dependency hierarchy x jquery min js vulnerable library found in head commit a href vulnerability details jquery before is vulnerable to cross site scripting xss attacks when a cross domain ajax request is performed without the datatype option causing text javascript responses to be executed publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution jquery step up your open source security game with whitesource
| 0
|
336,709
| 30,217,518,463
|
IssuesEvent
|
2023-07-05 16:38:23
|
apache/lucene
|
https://api.github.com/repos/apache/lucene
|
opened
|
Reproducible TestDrillSideways failure
|
type:test
|
### Description
The following gradle command fails reproducibly on `branch_9x` with the following error:
```
> java.lang.AssertionError
> at __randomizedtesting.SeedInfo.seed([EA93FFB2BD206B3C:98DFDABD0C40DD4F]:0)
> at junit@4.13.1/org.junit.Assert.fail(Assert.java:87)
> at junit@4.13.1/org.junit.Assert.assertTrue(Assert.java:42)
> at junit@4.13.1/org.junit.Assert.assertFalse(Assert.java:65)
> at junit@4.13.1/org.junit.Assert.assertFalse(Assert.java:75)
> at org.apache.lucene.facet.TestDrillSideways.verifyEquals(TestDrillSideways.java:1776)
> at org.apache.lucene.facet.TestDrillSideways.testRandom(TestDrillSideways.java:1338)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:568)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1758)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:946)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:982)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:996)
> at org.apache.lucene.test_framework@9.8.0-SNAPSHOT/org.apache.lucene.tests.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:48)
> at org.apache.lucene.test_framework@9.8.0-SNAPSHOT/org.apache.lucene.tests.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
> at org.apache.lucene.test_framework@9.8.0-SNAPSHOT/org.apache.lucene.tests.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:45)
> at org.apache.lucene.test_framework@9.8.0-SNAPSHOT/org.apache.lucene.tests.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:60)
> at org.apache.lucene.test_framework@9.8.0-SNAPSHOT/org.apache.lucene.tests.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:44)
> at junit@4.13.1/org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:390)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:843)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:490)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:955)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.RandomizedRunner$5.evaluate(RandomizedRunner.java:840)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.RandomizedRunner$6.evaluate(RandomizedRunner.java:891)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:902)
> at org.apache.lucene.test_framework@9.8.0-SNAPSHOT/org.apache.lucene.tests.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> at org.apache.lucene.test_framework@9.8.0-SNAPSHOT/org.apache.lucene.tests.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:38)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> at org.apache.lucene.test_framework@9.8.0-SNAPSHOT/org.apache.lucene.tests.util.TestRuleAssertionsRequired$1.evaluate(TestRuleAssertionsRequired.java:53)
> at org.apache.lucene.test_framework@9.8.0-SNAPSHOT/org.apache.lucene.tests.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
> at org.apache.lucene.test_framework@9.8.0-SNAPSHOT/org.apache.lucene.tests.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:44)
> at org.apache.lucene.test_framework@9.8.0-SNAPSHOT/org.apache.lucene.tests.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:60)
> at org.apache.lucene.test_framework@9.8.0-SNAPSHOT/org.apache.lucene.tests.util.TestRuleIgnoreTestSuites$1.evaluate(TestRuleIgnoreTestSuites.java:47)
> at junit@4.13.1/org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:390)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.ThreadLeakControl.lambda$forkTimeoutingTask$0(ThreadLeakControl.java:850)
> at java.base/java.lang.Thread.run(Thread.java:833)
2> NOTE: reproduce with: gradlew test --tests TestDrillSideways.testRandom -Dtests.seed=EA93FFB2BD206B3C -Dtests.locale=ar-OM -Dtests.timezone=Asia/Damascus -Dtests.asserts=true -Dtests.file.encoding=UTF-8
```
### Gradle command to reproduce
`./gradlew test --tests TestDrillSideways.testRandom -Dtests.seed=EA93FFB2BD206B3C -Dtests.locale=ar-OM -Dtests.timezone=Asia/Damascus -Dtests.asserts=true -Dtests.file.encoding=UTF-8`
|
1.0
|
Reproducible TestDrillSideways failure - ### Description
The following gradle command fails reproducibly on `branch_9x` with the following error:
```
> java.lang.AssertionError
> at __randomizedtesting.SeedInfo.seed([EA93FFB2BD206B3C:98DFDABD0C40DD4F]:0)
> at junit@4.13.1/org.junit.Assert.fail(Assert.java:87)
> at junit@4.13.1/org.junit.Assert.assertTrue(Assert.java:42)
> at junit@4.13.1/org.junit.Assert.assertFalse(Assert.java:65)
> at junit@4.13.1/org.junit.Assert.assertFalse(Assert.java:75)
> at org.apache.lucene.facet.TestDrillSideways.verifyEquals(TestDrillSideways.java:1776)
> at org.apache.lucene.facet.TestDrillSideways.testRandom(TestDrillSideways.java:1338)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:568)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1758)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:946)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:982)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:996)
> at org.apache.lucene.test_framework@9.8.0-SNAPSHOT/org.apache.lucene.tests.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:48)
> at org.apache.lucene.test_framework@9.8.0-SNAPSHOT/org.apache.lucene.tests.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
> at org.apache.lucene.test_framework@9.8.0-SNAPSHOT/org.apache.lucene.tests.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:45)
> at org.apache.lucene.test_framework@9.8.0-SNAPSHOT/org.apache.lucene.tests.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:60)
> at org.apache.lucene.test_framework@9.8.0-SNAPSHOT/org.apache.lucene.tests.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:44)
> at junit@4.13.1/org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:390)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:843)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:490)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:955)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.RandomizedRunner$5.evaluate(RandomizedRunner.java:840)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.RandomizedRunner$6.evaluate(RandomizedRunner.java:891)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:902)
> at org.apache.lucene.test_framework@9.8.0-SNAPSHOT/org.apache.lucene.tests.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> at org.apache.lucene.test_framework@9.8.0-SNAPSHOT/org.apache.lucene.tests.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:38)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> at org.apache.lucene.test_framework@9.8.0-SNAPSHOT/org.apache.lucene.tests.util.TestRuleAssertionsRequired$1.evaluate(TestRuleAssertionsRequired.java:53)
> at org.apache.lucene.test_framework@9.8.0-SNAPSHOT/org.apache.lucene.tests.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
> at org.apache.lucene.test_framework@9.8.0-SNAPSHOT/org.apache.lucene.tests.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:44)
> at org.apache.lucene.test_framework@9.8.0-SNAPSHOT/org.apache.lucene.tests.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:60)
> at org.apache.lucene.test_framework@9.8.0-SNAPSHOT/org.apache.lucene.tests.util.TestRuleIgnoreTestSuites$1.evaluate(TestRuleIgnoreTestSuites.java:47)
> at junit@4.13.1/org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:390)
> at randomizedtesting.runner@2.8.1/com.carrotsearch.randomizedtesting.ThreadLeakControl.lambda$forkTimeoutingTask$0(ThreadLeakControl.java:850)
> at java.base/java.lang.Thread.run(Thread.java:833)
2> NOTE: reproduce with: gradlew test --tests TestDrillSideways.testRandom -Dtests.seed=EA93FFB2BD206B3C -Dtests.locale=ar-OM -Dtests.timezone=Asia/Damascus -Dtests.asserts=true -Dtests.file.encoding=UTF-8
```
### Gradle command to reproduce
`./gradlew test --tests TestDrillSideways.testRandom -Dtests.seed=EA93FFB2BD206B3C -Dtests.locale=ar-OM -Dtests.timezone=Asia/Damascus -Dtests.asserts=true -Dtests.file.encoding=UTF-8`
|
test
|
reproducible testdrillsideways failure description the following gradle command fails reproducibly on branch with the following error java lang assertionerror at randomizedtesting seedinfo seed at junit org junit assert fail assert java at junit org junit assert asserttrue assert java at junit org junit assert assertfalse assert java at junit org junit assert assertfalse assert java at org apache lucene facet testdrillsideways verifyequals testdrillsideways java at org apache lucene facet testdrillsideways testrandom testdrillsideways java at java base jdk internal reflect nativemethodaccessorimpl native method at java base jdk internal reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at java base jdk internal reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java base java lang reflect method invoke method java at randomizedtesting runner com carrotsearch randomizedtesting randomizedrunner invoke randomizedrunner java at randomizedtesting runner com carrotsearch randomizedtesting randomizedrunner evaluate randomizedrunner java at randomizedtesting runner com carrotsearch randomizedtesting randomizedrunner evaluate randomizedrunner java at randomizedtesting runner com carrotsearch randomizedtesting randomizedrunner evaluate randomizedrunner java at org apache lucene test framework snapshot org apache lucene tests util testrulesetupteardownchained evaluate testrulesetupteardownchained java at org apache lucene test framework snapshot org apache lucene tests util abstractbeforeafterrule evaluate abstractbeforeafterrule java at org apache lucene test framework snapshot org apache lucene tests util testrulethreadandtestname evaluate testrulethreadandtestname java at org apache lucene test framework snapshot org apache lucene tests util testruleignoreaftermaxfailures evaluate testruleignoreaftermaxfailures java at org apache lucene test framework snapshot org apache lucene tests util testrulemarkfailure evaluate testrulemarkfailure java at junit org junit rules runrules evaluate runrules java at randomizedtesting runner com carrotsearch randomizedtesting rules statementadapter evaluate statementadapter java at randomizedtesting runner com carrotsearch randomizedtesting threadleakcontrol statementrunner run threadleakcontrol java at randomizedtesting runner com carrotsearch randomizedtesting threadleakcontrol forktimeoutingtask threadleakcontrol java at randomizedtesting runner com carrotsearch randomizedtesting threadleakcontrol evaluate threadleakcontrol java at randomizedtesting runner com carrotsearch randomizedtesting randomizedrunner runsingletest randomizedrunner java at randomizedtesting runner com carrotsearch randomizedtesting randomizedrunner evaluate randomizedrunner java at randomizedtesting runner com carrotsearch randomizedtesting randomizedrunner evaluate randomizedrunner java at randomizedtesting runner com carrotsearch randomizedtesting randomizedrunner evaluate randomizedrunner java at org apache lucene test framework snapshot org apache lucene tests util abstractbeforeafterrule evaluate abstractbeforeafterrule java at randomizedtesting runner com carrotsearch randomizedtesting rules statementadapter evaluate statementadapter java at org apache lucene test framework snapshot org apache lucene tests util testrulestoreclassname evaluate testrulestoreclassname java at randomizedtesting runner com carrotsearch randomizedtesting rules noshadowingoroverridesonmethodsrule evaluate noshadowingoroverridesonmethodsrule java at randomizedtesting runner com carrotsearch randomizedtesting rules noshadowingoroverridesonmethodsrule evaluate noshadowingoroverridesonmethodsrule java at randomizedtesting runner com carrotsearch randomizedtesting rules statementadapter evaluate statementadapter java at randomizedtesting runner com carrotsearch randomizedtesting rules statementadapter evaluate statementadapter java at org apache lucene test framework snapshot org apache lucene tests util testruleassertionsrequired evaluate testruleassertionsrequired java at org apache lucene test framework snapshot org apache lucene tests util abstractbeforeafterrule evaluate abstractbeforeafterrule java at org apache lucene test framework snapshot org apache lucene tests util testrulemarkfailure evaluate testrulemarkfailure java at org apache lucene test framework snapshot org apache lucene tests util testruleignoreaftermaxfailures evaluate testruleignoreaftermaxfailures java at org apache lucene test framework snapshot org apache lucene tests util testruleignoretestsuites evaluate testruleignoretestsuites java at junit org junit rules runrules evaluate runrules java at randomizedtesting runner com carrotsearch randomizedtesting rules statementadapter evaluate statementadapter java at randomizedtesting runner com carrotsearch randomizedtesting threadleakcontrol statementrunner run threadleakcontrol java at randomizedtesting runner com carrotsearch randomizedtesting threadleakcontrol lambda forktimeoutingtask threadleakcontrol java at java base java lang thread run thread java note reproduce with gradlew test tests testdrillsideways testrandom dtests seed dtests locale ar om dtests timezone asia damascus dtests asserts true dtests file encoding utf gradle command to reproduce gradlew test tests testdrillsideways testrandom dtests seed dtests locale ar om dtests timezone asia damascus dtests asserts true dtests file encoding utf
| 1
|
385,683
| 11,424,503,416
|
IssuesEvent
|
2020-02-03 17:53:23
|
krzychu124/Cities-Skylines-Traffic-Manager-President-Edition
|
https://api.github.com/repos/krzychu124/Cities-Skylines-Traffic-Manager-President-Edition
|
closed
|
Getting ready for v11 release
|
11 ALPHA LABS high priority in-progress
|
Planned steps for release of v11 STABLE:
1. Update alpha workshop to alpha 12 (bug fixes to array index errors, localisation updates, etc) - @aubergine10
2. Make sure that's working well (confirm bugs fixed) - whole team needs to be on lookout for error reports
3. Update changelog to fill in missing info about alpha releases etc (via PR #431) - @aubergine10
4. Update graphics for workshop pages (see notes below) - @FireController1847 can u do that?
5. Change mod name/version as applicable for LABS/STABLE builds - anyone with source access
6. Once we confirm 11-alpha12 is bug free, we can then update the two workshop pages (text will need some tweaks) - @aubergine10 and @krzychu124
7. Once 6 is done, it marks the offiical 'end of life' and obsolecence of LinuxFan's version / page; a comment will be posted to that page as necessary to remind users to move over to v11
#### Changes to workshop pages
Old STABLE page (linuxfan's page):
* We are not able to alter anything on this page :(
LABS workshop page (krzychu1245's page):
* Will become "TM:PE V11 STABLE"
* Use `RELEASE` (ie. STABLE) builds
* Preivew image and thumbnail to be updated to reflect new name/version
* Add "V11" and "STABLE" to the images to make different from linuxfan images
* Updated occasionally to latest stable builds
ALPHA workshp page (aubergine18's page):
* Will become "TM:PE V11 LABS"
* Use `RELEASE LABS` builds
* Preview image and thumbnail to be updated to reflect new name/version
* Regular updates soon after any PRs are merged so we get fast end-user feedback cycle going and thus faster progression of new features to stable releases
#### Other stuff
What happens to labels used on github? I propose:
* LABS -> rename to V11 STABLE
* 11 ALPHA -> rename to V11 LABS
lmk if I missed anything...
|
1.0
|
Getting ready for v11 release - Planned steps for release of v11 STABLE:
1. Update alpha workshop to alpha 12 (bug fixes to array index errors, localisation updates, etc) - @aubergine10
2. Make sure that's working well (confirm bugs fixed) - whole team needs to be on lookout for error reports
3. Update changelog to fill in missing info about alpha releases etc (via PR #431) - @aubergine10
4. Update graphics for workshop pages (see notes below) - @FireController1847 can u do that?
5. Change mod name/version as applicable for LABS/STABLE builds - anyone with source access
6. Once we confirm 11-alpha12 is bug free, we can then update the two workshop pages (text will need some tweaks) - @aubergine10 and @krzychu124
7. Once 6 is done, it marks the offiical 'end of life' and obsolecence of LinuxFan's version / page; a comment will be posted to that page as necessary to remind users to move over to v11
#### Changes to workshop pages
Old STABLE page (linuxfan's page):
* We are not able to alter anything on this page :(
LABS workshop page (krzychu1245's page):
* Will become "TM:PE V11 STABLE"
* Use `RELEASE` (ie. STABLE) builds
* Preivew image and thumbnail to be updated to reflect new name/version
* Add "V11" and "STABLE" to the images to make different from linuxfan images
* Updated occasionally to latest stable builds
ALPHA workshp page (aubergine18's page):
* Will become "TM:PE V11 LABS"
* Use `RELEASE LABS` builds
* Preview image and thumbnail to be updated to reflect new name/version
* Regular updates soon after any PRs are merged so we get fast end-user feedback cycle going and thus faster progression of new features to stable releases
#### Other stuff
What happens to labels used on github? I propose:
* LABS -> rename to V11 STABLE
* 11 ALPHA -> rename to V11 LABS
lmk if I missed anything...
|
non_test
|
getting ready for release planned steps for release of stable update alpha workshop to alpha bug fixes to array index errors localisation updates etc make sure that s working well confirm bugs fixed whole team needs to be on lookout for error reports update changelog to fill in missing info about alpha releases etc via pr update graphics for workshop pages see notes below can u do that change mod name version as applicable for labs stable builds anyone with source access once we confirm is bug free we can then update the two workshop pages text will need some tweaks and once is done it marks the offiical end of life and obsolecence of linuxfan s version page a comment will be posted to that page as necessary to remind users to move over to changes to workshop pages old stable page linuxfan s page we are not able to alter anything on this page labs workshop page s page will become tm pe stable use release ie stable builds preivew image and thumbnail to be updated to reflect new name version add and stable to the images to make different from linuxfan images updated occasionally to latest stable builds alpha workshp page s page will become tm pe labs use release labs builds preview image and thumbnail to be updated to reflect new name version regular updates soon after any prs are merged so we get fast end user feedback cycle going and thus faster progression of new features to stable releases other stuff what happens to labels used on github i propose labs rename to stable alpha rename to labs lmk if i missed anything
| 0
|
136,520
| 11,049,370,116
|
IssuesEvent
|
2019-12-09 23:30:18
|
MangopearUK/European-Boating-Association--Theme
|
https://api.github.com/repos/MangopearUK/European-Boating-Association--Theme
|
closed
|
Test & audit: EBA General Assembly 2019-GA1 Malta: REMINDER
|
Testing: second round
|
Page URL: https://eba.eu.com/membership/secretariat-announcements/eba-general-assembly-2019-ga1-malta-reminder/
## Table of contents
- [x] **Task 1:** Perform automated audits _(10 tasks)_
- [x] **Task 2:** Manual standards & accessibility tests _(61 tasks)_
- [x] **Task 3:** Breakpoint testing _(15 tasks)_
- [x] **Task 4:** Re-run automated audits _(10 tasks)_
## 1: Perform automated audits _(10 tasks)_
### Lighthouse:
- [x] Run "Accessibility" audit in lighthouse _(using incognito tab)_
- [x] Run "Performance" audit in lighthouse _(using incognito tab)_
- [x] Run "Best practices" audit in lighthouse _(using incognito tab)_
- [x] Run "SEO" audit in lighthouse _(using incognito tab)_
- [x] Run "PWA" audit in lighthouse _(using incognito tab)_
### Pingdom
- [x] Run full audit of the the page's performance in Pingdom
### Browser's console
- [x] Check Chrome's console for errors
### Log results of audits
- [x] Screenshot snapshot of the lighthouse audits
- [x] Upload PDF of detailed lighthouse reports
- [x] Provide a screenshot of any console errors
## 2: Manual standards & accessibility tests _(61 tasks)_
### Forms
- [x] Give all form elements permanently visible labels
- [x] Place labels above form elements
- [x] Mark invalid fields clearly and provide associated error messages
- [x] Make forms as short as possible; offer shortcuts like autocompleting the address using the postcode
- [x] Ensure all form fields have the correct requried state
- [x] Provide status and error messages as WAI-ARIA live regions
### Readability of content
- [x] Ensure page has good grammar
- [x] Ensure page content has been spell-checked
- [x] Make sure headings are in logical order
- [x] Ensure the same content is available across different devices and platforms
- [x] Begin long, multi-section documents with a table of contents
### Presentation
- [x] Make sure all content is formatted correctly
- [x] Avoid all-caps text
- [x] Make sure data tables wider than their container can be scrolled horizontally
- [x] Use the same design patterns to solve the same problems
- [x] Do not mark up subheadings/straplines with separate heading elements
### Links & buttons
#### Links
- [x] Check all links to ensure they work
- [x] Check all links to third party websites use `rel="noopener"`
- [x] Make sure the purpose of a link is clearly described: "read more" vs. "read more about accessibility"
- [x] Provide a skip link if necessary
- [x] Underline links — at least in body copy
- [x] Warn users of links that have unusual behaviors, like linking off-site, or loading a new tab (i.e. aria-label)
#### Buttons
- [x] Ensure primary calls to action are easy to recognize and reach
- [x] Provide clear, unambiguous focus styles
- [x] Ensure states (pressed, expanded, invalid, etc) are communicated to assistive software
- [x] Ensure disabled controls are not focusable
- [x] Make sure controls within hidden content are not focusable
- [x] Provide large touch "targets" for interactive elements
- [x] Make controls look like controls; give them strong perceived affordance
- [x] Use well-established, therefore recognizable, icons and symbols
### Assistive technology
- [x] Ensure content is not obscured through zooming
- [x] Support Windows high contrast mode (use images, not background images)
- [x] Provide alternative text for salient images
- [x] Make scrollable elements focusable for keyboard users
- [x] Ensure keyboard focus order is logical regarding visual layout
- [x] Match semantics to behavior for assistive technology users
- [x] Provide a default language and use lang="[ISO code]" for subsections in different languages
- [x] Inform the user when there are important changes to the application state
- [x] Do not hijack standard scrolling behavior
- [x] Do not instate "infinite scroll" by default; provide buttons to load more items
### General accessibility
- [x] Make sure text and background colors contrast sufficiently
- [x] Do not rely on color for differentiation of visual elements
- [x] Avoid images of text — text that cannot be translated, selected, or understood by assistive tech
- [x] Provide a print stylesheet
- [x] Honour requests to remove animation via the prefers-reduced-motion media query
### SEO
- [x] Ensure all pages have appropriate title
- [x] Ensure all pages have meta descriptions
- [x] Make content easier to find and improve search results with structured data [Read more](https://developers.google.com/search/docs/guides/prototype)
- [x] Check whether page should be appearing in sitemap
- [x] Make sure page has Facebook and Twitter large image previews set correctly
- [x] Check canonical links for page
- [x] Mark as cornerstone content?
### Performance
- [x] Ensure all CSS assets are minified and concatenated
- [x] Ensure all JS assets are minified and concatenated
- [x] Ensure all images are compressed
- [x] Where possible, remove redundant code
- [x] Ensure all SVG assets have been optimised
- [x] Make sure styles and scripts are not render blocking
- [x] Ensure large image assets are lazy loaded
### Other
- [x] Make sure all content belongs to a landmark element
- [x] Provide a manifest.json file for identifiable homescreen entries
## 3: Breakpoint testing _(15 tasks)_
### Desktop
- [x] Provide a full screenshot of **1920px** wide page
- [x] Provide a full screenshot of **1500px** wide page
- [x] Provide a full screenshot of **1280px** wide page
- [x] Provide a full screenshot of **1024px** wide page
### Tablet
- [x] Provide a full screenshot of **960px** wide page
- [x] Provide a full screenshot of **800px** wide page
- [x] Provide a full screenshot of **760px** wide page
- [x] Provide a full screenshot of **650px** wide page
### Mobile
- [x] Provide a full screenshot of **600px** wide page
- [x] Provide a full screenshot of **500px** wide page
- [x] Provide a full screenshot of **450px** wide page
- [x] Provide a full screenshot of **380px** wide page
- [x] Provide a full screenshot of **320px** wide page
- [x] Provide a full screenshot of **280px** wide page
- [x] Provide a full screenshot of **250px** wide page
## 4: Re-run automated audits _(10 tasks)_
### Lighthouse:
- [x] Run "Accessibility" audit in lighthouse _(using incognito tab)_
- [x] Run "Performance" audit in lighthouse _(using incognito tab)_
- [x] Run "Best practices" audit in lighthouse _(using incognito tab)_
- [x] Run "SEO" audit in lighthouse _(using incognito tab)_
- [x] Run "PWA" audit in lighthouse _(using incognito tab)_
### Pingdom
- [x] Run full audit of the the page's performance in Pingdom
### Browser's console
- [x] Check Chrome's console for errors
### Log results of audits
- [x] Screenshot snapshot of the lighthouse audits
- [x] Upload PDF of detailed lighthouse reports
- [x] Provide a screenshot of any console errors
|
1.0
|
Test & audit: EBA General Assembly 2019-GA1 Malta: REMINDER - Page URL: https://eba.eu.com/membership/secretariat-announcements/eba-general-assembly-2019-ga1-malta-reminder/
## Table of contents
- [x] **Task 1:** Perform automated audits _(10 tasks)_
- [x] **Task 2:** Manual standards & accessibility tests _(61 tasks)_
- [x] **Task 3:** Breakpoint testing _(15 tasks)_
- [x] **Task 4:** Re-run automated audits _(10 tasks)_
## 1: Perform automated audits _(10 tasks)_
### Lighthouse:
- [x] Run "Accessibility" audit in lighthouse _(using incognito tab)_
- [x] Run "Performance" audit in lighthouse _(using incognito tab)_
- [x] Run "Best practices" audit in lighthouse _(using incognito tab)_
- [x] Run "SEO" audit in lighthouse _(using incognito tab)_
- [x] Run "PWA" audit in lighthouse _(using incognito tab)_
### Pingdom
- [x] Run full audit of the the page's performance in Pingdom
### Browser's console
- [x] Check Chrome's console for errors
### Log results of audits
- [x] Screenshot snapshot of the lighthouse audits
- [x] Upload PDF of detailed lighthouse reports
- [x] Provide a screenshot of any console errors
## 2: Manual standards & accessibility tests _(61 tasks)_
### Forms
- [x] Give all form elements permanently visible labels
- [x] Place labels above form elements
- [x] Mark invalid fields clearly and provide associated error messages
- [x] Make forms as short as possible; offer shortcuts like autocompleting the address using the postcode
- [x] Ensure all form fields have the correct requried state
- [x] Provide status and error messages as WAI-ARIA live regions
### Readability of content
- [x] Ensure page has good grammar
- [x] Ensure page content has been spell-checked
- [x] Make sure headings are in logical order
- [x] Ensure the same content is available across different devices and platforms
- [x] Begin long, multi-section documents with a table of contents
### Presentation
- [x] Make sure all content is formatted correctly
- [x] Avoid all-caps text
- [x] Make sure data tables wider than their container can be scrolled horizontally
- [x] Use the same design patterns to solve the same problems
- [x] Do not mark up subheadings/straplines with separate heading elements
### Links & buttons
#### Links
- [x] Check all links to ensure they work
- [x] Check all links to third party websites use `rel="noopener"`
- [x] Make sure the purpose of a link is clearly described: "read more" vs. "read more about accessibility"
- [x] Provide a skip link if necessary
- [x] Underline links — at least in body copy
- [x] Warn users of links that have unusual behaviors, like linking off-site, or loading a new tab (i.e. aria-label)
#### Buttons
- [x] Ensure primary calls to action are easy to recognize and reach
- [x] Provide clear, unambiguous focus styles
- [x] Ensure states (pressed, expanded, invalid, etc) are communicated to assistive software
- [x] Ensure disabled controls are not focusable
- [x] Make sure controls within hidden content are not focusable
- [x] Provide large touch "targets" for interactive elements
- [x] Make controls look like controls; give them strong perceived affordance
- [x] Use well-established, therefore recognizable, icons and symbols
### Assistive technology
- [x] Ensure content is not obscured through zooming
- [x] Support Windows high contrast mode (use images, not background images)
- [x] Provide alternative text for salient images
- [x] Make scrollable elements focusable for keyboard users
- [x] Ensure keyboard focus order is logical regarding visual layout
- [x] Match semantics to behavior for assistive technology users
- [x] Provide a default language and use lang="[ISO code]" for subsections in different languages
- [x] Inform the user when there are important changes to the application state
- [x] Do not hijack standard scrolling behavior
- [x] Do not instate "infinite scroll" by default; provide buttons to load more items
### General accessibility
- [x] Make sure text and background colors contrast sufficiently
- [x] Do not rely on color for differentiation of visual elements
- [x] Avoid images of text — text that cannot be translated, selected, or understood by assistive tech
- [x] Provide a print stylesheet
- [x] Honour requests to remove animation via the prefers-reduced-motion media query
### SEO
- [x] Ensure all pages have appropriate title
- [x] Ensure all pages have meta descriptions
- [x] Make content easier to find and improve search results with structured data [Read more](https://developers.google.com/search/docs/guides/prototype)
- [x] Check whether page should be appearing in sitemap
- [x] Make sure page has Facebook and Twitter large image previews set correctly
- [x] Check canonical links for page
- [x] Mark as cornerstone content?
### Performance
- [x] Ensure all CSS assets are minified and concatenated
- [x] Ensure all JS assets are minified and concatenated
- [x] Ensure all images are compressed
- [x] Where possible, remove redundant code
- [x] Ensure all SVG assets have been optimised
- [x] Make sure styles and scripts are not render blocking
- [x] Ensure large image assets are lazy loaded
### Other
- [x] Make sure all content belongs to a landmark element
- [x] Provide a manifest.json file for identifiable homescreen entries
## 3: Breakpoint testing _(15 tasks)_
### Desktop
- [x] Provide a full screenshot of **1920px** wide page
- [x] Provide a full screenshot of **1500px** wide page
- [x] Provide a full screenshot of **1280px** wide page
- [x] Provide a full screenshot of **1024px** wide page
### Tablet
- [x] Provide a full screenshot of **960px** wide page
- [x] Provide a full screenshot of **800px** wide page
- [x] Provide a full screenshot of **760px** wide page
- [x] Provide a full screenshot of **650px** wide page
### Mobile
- [x] Provide a full screenshot of **600px** wide page
- [x] Provide a full screenshot of **500px** wide page
- [x] Provide a full screenshot of **450px** wide page
- [x] Provide a full screenshot of **380px** wide page
- [x] Provide a full screenshot of **320px** wide page
- [x] Provide a full screenshot of **280px** wide page
- [x] Provide a full screenshot of **250px** wide page
## 4: Re-run automated audits _(10 tasks)_
### Lighthouse:
- [x] Run "Accessibility" audit in lighthouse _(using incognito tab)_
- [x] Run "Performance" audit in lighthouse _(using incognito tab)_
- [x] Run "Best practices" audit in lighthouse _(using incognito tab)_
- [x] Run "SEO" audit in lighthouse _(using incognito tab)_
- [x] Run "PWA" audit in lighthouse _(using incognito tab)_
### Pingdom
- [x] Run full audit of the the page's performance in Pingdom
### Browser's console
- [x] Check Chrome's console for errors
### Log results of audits
- [x] Screenshot snapshot of the lighthouse audits
- [x] Upload PDF of detailed lighthouse reports
- [x] Provide a screenshot of any console errors
|
test
|
test audit eba general assembly malta reminder page url table of contents task perform automated audits tasks task manual standards accessibility tests tasks task breakpoint testing tasks task re run automated audits tasks perform automated audits tasks lighthouse run accessibility audit in lighthouse using incognito tab run performance audit in lighthouse using incognito tab run best practices audit in lighthouse using incognito tab run seo audit in lighthouse using incognito tab run pwa audit in lighthouse using incognito tab pingdom run full audit of the the page s performance in pingdom browser s console check chrome s console for errors log results of audits screenshot snapshot of the lighthouse audits upload pdf of detailed lighthouse reports provide a screenshot of any console errors manual standards accessibility tests tasks forms give all form elements permanently visible labels place labels above form elements mark invalid fields clearly and provide associated error messages make forms as short as possible offer shortcuts like autocompleting the address using the postcode ensure all form fields have the correct requried state provide status and error messages as wai aria live regions readability of content ensure page has good grammar ensure page content has been spell checked make sure headings are in logical order ensure the same content is available across different devices and platforms begin long multi section documents with a table of contents presentation make sure all content is formatted correctly avoid all caps text make sure data tables wider than their container can be scrolled horizontally use the same design patterns to solve the same problems do not mark up subheadings straplines with separate heading elements links buttons links check all links to ensure they work check all links to third party websites use rel noopener make sure the purpose of a link is clearly described read more vs read more about accessibility provide a skip link if necessary underline links — at least in body copy warn users of links that have unusual behaviors like linking off site or loading a new tab i e aria label buttons ensure primary calls to action are easy to recognize and reach provide clear unambiguous focus styles ensure states pressed expanded invalid etc are communicated to assistive software ensure disabled controls are not focusable make sure controls within hidden content are not focusable provide large touch targets for interactive elements make controls look like controls give them strong perceived affordance use well established therefore recognizable icons and symbols assistive technology ensure content is not obscured through zooming support windows high contrast mode use images not background images provide alternative text for salient images make scrollable elements focusable for keyboard users ensure keyboard focus order is logical regarding visual layout match semantics to behavior for assistive technology users provide a default language and use lang for subsections in different languages inform the user when there are important changes to the application state do not hijack standard scrolling behavior do not instate infinite scroll by default provide buttons to load more items general accessibility make sure text and background colors contrast sufficiently do not rely on color for differentiation of visual elements avoid images of text — text that cannot be translated selected or understood by assistive tech provide a print stylesheet honour requests to remove animation via the prefers reduced motion media query seo ensure all pages have appropriate title ensure all pages have meta descriptions make content easier to find and improve search results with structured data check whether page should be appearing in sitemap make sure page has facebook and twitter large image previews set correctly check canonical links for page mark as cornerstone content performance ensure all css assets are minified and concatenated ensure all js assets are minified and concatenated ensure all images are compressed where possible remove redundant code ensure all svg assets have been optimised make sure styles and scripts are not render blocking ensure large image assets are lazy loaded other make sure all content belongs to a landmark element provide a manifest json file for identifiable homescreen entries breakpoint testing tasks desktop provide a full screenshot of wide page provide a full screenshot of wide page provide a full screenshot of wide page provide a full screenshot of wide page tablet provide a full screenshot of wide page provide a full screenshot of wide page provide a full screenshot of wide page provide a full screenshot of wide page mobile provide a full screenshot of wide page provide a full screenshot of wide page provide a full screenshot of wide page provide a full screenshot of wide page provide a full screenshot of wide page provide a full screenshot of wide page provide a full screenshot of wide page re run automated audits tasks lighthouse run accessibility audit in lighthouse using incognito tab run performance audit in lighthouse using incognito tab run best practices audit in lighthouse using incognito tab run seo audit in lighthouse using incognito tab run pwa audit in lighthouse using incognito tab pingdom run full audit of the the page s performance in pingdom browser s console check chrome s console for errors log results of audits screenshot snapshot of the lighthouse audits upload pdf of detailed lighthouse reports provide a screenshot of any console errors
| 1
|
415,937
| 12,137,219,669
|
IssuesEvent
|
2020-04-23 15:25:41
|
luna/enso
|
https://api.github.com/repos/luna/enso
|
closed
|
Implement Dataflow Analysis
|
Category: Compiler Category: Interpreter Category: Tooling Change: Non-Breaking Difficulty: Core Contributor Priority: Medium Type: Enhancement
|
### Summary
While the caching mechanism implemented in #309 allows us to cache and evict values in the introspected scope, it has to be done manually. In order to make this entirely seamless for our users we need to have a pass that automatically analyses data dependencies and provides an API for getting at this information such that it can later be used for caching decisions.
### Value
This analysis lets us provide totally seamless value caching behaviour for our users.
### Specification
- [x] Implement a dataflow analysis pass into the compiler. This should output a graph of data depencencies as annotations on the graph.
- [x] Determine the most-appropriate, local cache eviction strategy for Enso. This needs to account for values, types, and various other non-obvious changes in the data dependencies.
- [x] The intial caching strategy should invalidate all call sites for a method when a method is changed. This should be constrained in future as part of the efforts to make it more sophisticated.
### Acceptance Criteria & Test Cases
- We have the necessary information in the compiler for the language server to control the cache properly.
|
1.0
|
Implement Dataflow Analysis - ### Summary
While the caching mechanism implemented in #309 allows us to cache and evict values in the introspected scope, it has to be done manually. In order to make this entirely seamless for our users we need to have a pass that automatically analyses data dependencies and provides an API for getting at this information such that it can later be used for caching decisions.
### Value
This analysis lets us provide totally seamless value caching behaviour for our users.
### Specification
- [x] Implement a dataflow analysis pass into the compiler. This should output a graph of data depencencies as annotations on the graph.
- [x] Determine the most-appropriate, local cache eviction strategy for Enso. This needs to account for values, types, and various other non-obvious changes in the data dependencies.
- [x] The intial caching strategy should invalidate all call sites for a method when a method is changed. This should be constrained in future as part of the efforts to make it more sophisticated.
### Acceptance Criteria & Test Cases
- We have the necessary information in the compiler for the language server to control the cache properly.
|
non_test
|
implement dataflow analysis summary while the caching mechanism implemented in allows us to cache and evict values in the introspected scope it has to be done manually in order to make this entirely seamless for our users we need to have a pass that automatically analyses data dependencies and provides an api for getting at this information such that it can later be used for caching decisions value this analysis lets us provide totally seamless value caching behaviour for our users specification implement a dataflow analysis pass into the compiler this should output a graph of data depencencies as annotations on the graph determine the most appropriate local cache eviction strategy for enso this needs to account for values types and various other non obvious changes in the data dependencies the intial caching strategy should invalidate all call sites for a method when a method is changed this should be constrained in future as part of the efforts to make it more sophisticated acceptance criteria test cases we have the necessary information in the compiler for the language server to control the cache properly
| 0
|
213,329
| 16,519,964,960
|
IssuesEvent
|
2021-05-26 13:38:08
|
NetworkGradeLinux/mion-docs
|
https://api.github.com/repos/NetworkGradeLinux/mion-docs
|
opened
|
Document Stratum
|
documentation medium
|
Stratum info will need to be added to the main docs and any relevant repo level docs
|
1.0
|
Document Stratum - Stratum info will need to be added to the main docs and any relevant repo level docs
|
non_test
|
document stratum stratum info will need to be added to the main docs and any relevant repo level docs
| 0
|
345,626
| 30,828,233,851
|
IssuesEvent
|
2023-08-01 22:08:17
|
confidential-containers/cloud-api-adaptor
|
https://api.github.com/repos/confidential-containers/cloud-api-adaptor
|
opened
|
Azure-Test-Provisioner: Remove the confusing & convoluted code
|
provider/azure e2e-test
|
Right now the Azure test provisioner code has cyclical way where we (1) convert the map[string]string into concrete struct and in other place (2) we again convert that concrete struct into map[string]string.
(1) https://github.com/confidential-containers/cloud-api-adaptor/blob/b03177aa1ddeb121cd5e983d88c4d6b1e8a9a135/test/provisioner/provision_azure_initializer.go#L54-L69
(2) https://github.com/confidential-containers/cloud-api-adaptor/blob/b03177aa1ddeb121cd5e983d88c4d6b1e8a9a135/test/provisioner/provision_azure.go#L353-L366
|
1.0
|
Azure-Test-Provisioner: Remove the confusing & convoluted code - Right now the Azure test provisioner code has cyclical way where we (1) convert the map[string]string into concrete struct and in other place (2) we again convert that concrete struct into map[string]string.
(1) https://github.com/confidential-containers/cloud-api-adaptor/blob/b03177aa1ddeb121cd5e983d88c4d6b1e8a9a135/test/provisioner/provision_azure_initializer.go#L54-L69
(2) https://github.com/confidential-containers/cloud-api-adaptor/blob/b03177aa1ddeb121cd5e983d88c4d6b1e8a9a135/test/provisioner/provision_azure.go#L353-L366
|
test
|
azure test provisioner remove the confusing convoluted code right now the azure test provisioner code has cyclical way where we convert the map string into concrete struct and in other place we again convert that concrete struct into map string
| 1
|
118,968
| 15,384,436,137
|
IssuesEvent
|
2021-03-03 04:41:51
|
TheAlphamerc/flutter_twitter_clone
|
https://api.github.com/repos/TheAlphamerc/flutter_twitter_clone
|
closed
|
Swipe indicator (iphone x and up)
|
Design fix good first issue
|
Can we make that bottom menu bar recognise iOS devices with swipe indicator and automatically move bottom bar up?
|
1.0
|
Swipe indicator (iphone x and up) - Can we make that bottom menu bar recognise iOS devices with swipe indicator and automatically move bottom bar up?
|
non_test
|
swipe indicator iphone x and up can we make that bottom menu bar recognise ios devices with swipe indicator and automatically move bottom bar up
| 0
|
229,711
| 18,418,198,793
|
IssuesEvent
|
2021-10-13 13:39:17
|
elastic/kibana
|
https://api.github.com/repos/elastic/kibana
|
closed
|
Failing test: X-Pack API Integration Tests.x-pack/test/api_integration/apis/maps/get_tile·js - apis Maps endpoints getTile should return vector tile containing document
|
blocker Team:Geo failed-test skipped-test v7.16.0
|
A test failed on a tracked branch
```
Error: expected { bytes: 9583,
_index: 'logstash-2015.09.20',
_id: 'AU_x3_g3GFA8no6QjkGu',
__kbn__feature_id__: 'logstash-2015.09.20:AU_x3_g3GFA8no6QjkGu:0' } to sort of equal { __kbn__feature_id__: 'logstash-2015.09.20:AU_x3_BsGFA8no6Qjjug:0',
_id: 'AU_x3_BsGFA8no6Qjjug',
_index: 'logstash-2015.09.20',
bytes: 9252,
'machine.os.raw': 'ios' }
at Assertion.assert (/opt/local-ssd/buildkite/builds/kb-cigroup-6-f209dc9c2248ec1a/elastic/kibana-hourly/kibana/node_modules/@kbn/expect/expect.js:100:11)
at Assertion.eql (/opt/local-ssd/buildkite/builds/kb-cigroup-6-f209dc9c2248ec1a/elastic/kibana-hourly/kibana/node_modules/@kbn/expect/expect.js:244:8)
at Context.<anonymous> (test/api_integration/apis/maps/get_tile.js:39:37)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at Object.apply (/opt/local-ssd/buildkite/builds/kb-cigroup-6-f209dc9c2248ec1a/elastic/kibana-hourly/kibana/node_modules/@kbn/test/target_node/functional_test_runner/lib/mocha/wrap_function.js:87:16) {
actual: '{\n' +
' "__kbn__feature_id__": "logstash-2015.09.20:AU_x3_g3GFA8no6QjkGu:0"\n' +
' "_id": "AU_x3_g3GFA8no6QjkGu"\n' +
' "_index": "logstash-2015.09.20"\n' +
' "bytes": 9583\n' +
'}',
expected: '{\n' +
' "__kbn__feature_id__": "logstash-2015.09.20:AU_x3_BsGFA8no6Qjjug:0"\n' +
' "_id": "AU_x3_BsGFA8no6Qjjug"\n' +
' "_index": "logstash-2015.09.20"\n' +
' "bytes": 9252\n' +
' "machine.os.raw": "ios"\n' +
'}',
showDiff: true
}
```
First failure: [CI Build - 7.x](https://buildkite.com/elastic/kibana-hourly/builds/1191#9718457e-86cf-47c3-8fe7-16553c939eb2)
<!-- kibanaCiData = {"failed-test":{"test.class":"X-Pack API Integration Tests.x-pack/test/api_integration/apis/maps/get_tile·js","test.name":"apis Maps endpoints getTile should return vector tile containing document","test.failCount":17}} -->
|
2.0
|
Failing test: X-Pack API Integration Tests.x-pack/test/api_integration/apis/maps/get_tile·js - apis Maps endpoints getTile should return vector tile containing document - A test failed on a tracked branch
```
Error: expected { bytes: 9583,
_index: 'logstash-2015.09.20',
_id: 'AU_x3_g3GFA8no6QjkGu',
__kbn__feature_id__: 'logstash-2015.09.20:AU_x3_g3GFA8no6QjkGu:0' } to sort of equal { __kbn__feature_id__: 'logstash-2015.09.20:AU_x3_BsGFA8no6Qjjug:0',
_id: 'AU_x3_BsGFA8no6Qjjug',
_index: 'logstash-2015.09.20',
bytes: 9252,
'machine.os.raw': 'ios' }
at Assertion.assert (/opt/local-ssd/buildkite/builds/kb-cigroup-6-f209dc9c2248ec1a/elastic/kibana-hourly/kibana/node_modules/@kbn/expect/expect.js:100:11)
at Assertion.eql (/opt/local-ssd/buildkite/builds/kb-cigroup-6-f209dc9c2248ec1a/elastic/kibana-hourly/kibana/node_modules/@kbn/expect/expect.js:244:8)
at Context.<anonymous> (test/api_integration/apis/maps/get_tile.js:39:37)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at Object.apply (/opt/local-ssd/buildkite/builds/kb-cigroup-6-f209dc9c2248ec1a/elastic/kibana-hourly/kibana/node_modules/@kbn/test/target_node/functional_test_runner/lib/mocha/wrap_function.js:87:16) {
actual: '{\n' +
' "__kbn__feature_id__": "logstash-2015.09.20:AU_x3_g3GFA8no6QjkGu:0"\n' +
' "_id": "AU_x3_g3GFA8no6QjkGu"\n' +
' "_index": "logstash-2015.09.20"\n' +
' "bytes": 9583\n' +
'}',
expected: '{\n' +
' "__kbn__feature_id__": "logstash-2015.09.20:AU_x3_BsGFA8no6Qjjug:0"\n' +
' "_id": "AU_x3_BsGFA8no6Qjjug"\n' +
' "_index": "logstash-2015.09.20"\n' +
' "bytes": 9252\n' +
' "machine.os.raw": "ios"\n' +
'}',
showDiff: true
}
```
First failure: [CI Build - 7.x](https://buildkite.com/elastic/kibana-hourly/builds/1191#9718457e-86cf-47c3-8fe7-16553c939eb2)
<!-- kibanaCiData = {"failed-test":{"test.class":"X-Pack API Integration Tests.x-pack/test/api_integration/apis/maps/get_tile·js","test.name":"apis Maps endpoints getTile should return vector tile containing document","test.failCount":17}} -->
|
test
|
failing test x pack api integration tests x pack test api integration apis maps get tile·js apis maps endpoints gettile should return vector tile containing document a test failed on a tracked branch error expected bytes index logstash id au kbn feature id logstash au to sort of equal kbn feature id logstash au id au index logstash bytes machine os raw ios at assertion assert opt local ssd buildkite builds kb cigroup elastic kibana hourly kibana node modules kbn expect expect js at assertion eql opt local ssd buildkite builds kb cigroup elastic kibana hourly kibana node modules kbn expect expect js at context test api integration apis maps get tile js at runmicrotasks at processticksandrejections internal process task queues js at object apply opt local ssd buildkite builds kb cigroup elastic kibana hourly kibana node modules kbn test target node functional test runner lib mocha wrap function js actual n kbn feature id logstash au n id au n index logstash n bytes n expected n kbn feature id logstash au n id au n index logstash n bytes n machine os raw ios n showdiff true first failure
| 1
|
533,814
| 15,603,397,109
|
IssuesEvent
|
2021-03-19 01:47:34
|
halloweentown/SOEN341-W21-A7
|
https://api.github.com/repos/halloweentown/SOEN341-W21-A7
|
closed
|
[US-13] As a User I want to follow another user so that I can view future posts from that user [7]
|
Epic High Priority Medium Risk User Story
|
Users shall be able to follow people that they like by clicking a button
### **Functional Requirements**
- [x] Be able to follow another user
- [ ] able to view their future posts
### **Specifications**
Quantitative PASS/FAIL performance metrics that must be met by the implementation. ex:
- [x] Visual indicator that you are following the user
- [ ] Content from followed users appears for currently logged in user
### **Tasks**
- [ ] Create user pages
- [x] Create a button which allows you to follow another user
- [x] Save in the database who the user is following
- [x] Save in database who have followed you
### **Acceptance Criteria**
<!-- Card can be marked as 'Done' when the following have been completed: -->
1. When the user has an account and wants to follow another user
2. Then the user should be able to click a follow button and update their database
|
1.0
|
[US-13] As a User I want to follow another user so that I can view future posts from that user [7] - Users shall be able to follow people that they like by clicking a button
### **Functional Requirements**
- [x] Be able to follow another user
- [ ] able to view their future posts
### **Specifications**
Quantitative PASS/FAIL performance metrics that must be met by the implementation. ex:
- [x] Visual indicator that you are following the user
- [ ] Content from followed users appears for currently logged in user
### **Tasks**
- [ ] Create user pages
- [x] Create a button which allows you to follow another user
- [x] Save in the database who the user is following
- [x] Save in database who have followed you
### **Acceptance Criteria**
<!-- Card can be marked as 'Done' when the following have been completed: -->
1. When the user has an account and wants to follow another user
2. Then the user should be able to click a follow button and update their database
|
non_test
|
as a user i want to follow another user so that i can view future posts from that user users shall be able to follow people that they like by clicking a button functional requirements be able to follow another user able to view their future posts specifications quantitative pass fail performance metrics that must be met by the implementation ex visual indicator that you are following the user content from followed users appears for currently logged in user tasks create user pages create a button which allows you to follow another user save in the database who the user is following save in database who have followed you acceptance criteria when the user has an account and wants to follow another user then the user should be able to click a follow button and update their database
| 0
|
450,466
| 31,925,817,216
|
IssuesEvent
|
2023-09-19 01:37:41
|
aaronthangnguyen/cen4010-swe1
|
https://api.github.com/repos/aaronthangnguyen/cen4010-swe1
|
closed
|
Schema Reference
|
documentation
|
### Overview
Document database schemas in wiki.
### Wiki
https://github.com/aaronthangnguyen/cen4010-swe1/wiki/Schema-Reference
### Tasks
- [x] `Author` schema @aaronthangnguyen
- [x] `Book` schema @aaronthangnguyen
|
1.0
|
Schema Reference - ### Overview
Document database schemas in wiki.
### Wiki
https://github.com/aaronthangnguyen/cen4010-swe1/wiki/Schema-Reference
### Tasks
- [x] `Author` schema @aaronthangnguyen
- [x] `Book` schema @aaronthangnguyen
|
non_test
|
schema reference overview document database schemas in wiki wiki tasks author schema aaronthangnguyen book schema aaronthangnguyen
| 0
|
252,970
| 21,642,615,339
|
IssuesEvent
|
2022-05-05 20:30:51
|
dask/distributed
|
https://api.github.com/repos/dask/distributed
|
opened
|
CI failure from `test_flight_to_executing_via_cancelled_resumed`
|
flaky test
|
Seeing `test_flight_to_executing_via_cancelled_resumed` on `main`
https://github.com/dask/distributed/runs/6300892664?check_suite_focus=true
|
1.0
|
CI failure from `test_flight_to_executing_via_cancelled_resumed` - Seeing `test_flight_to_executing_via_cancelled_resumed` on `main`
https://github.com/dask/distributed/runs/6300892664?check_suite_focus=true
|
test
|
ci failure from test flight to executing via cancelled resumed seeing test flight to executing via cancelled resumed on main
| 1
|
181,554
| 14,049,796,288
|
IssuesEvent
|
2020-11-02 10:47:06
|
mindsdb/mindsdb
|
https://api.github.com/repos/mindsdb/mindsdb
|
opened
|
Introduce "user flow" tests
|
tests
|
Introduce one or two tests that attempt to mimic various ways a user might use mindsdb.
## Flow I
1. Connect a database (create an integration) via the http api
2. Create a model from the database using SQL
3. Analyse the model via the http api
4. Analyse the datasource it was trained on via the http api
6. Upload a datasource via the http api
7. Predict with that datasource from the database using SQL
8. Delete the model via the HTTP API
9. Make sure the `mindsdb` database no longer has the model
## Flow II
1. Start mindsdb (http api only)
2. Upload a dataset.
3. Add a database integration via the HTTP API
4. Restart mindsdb (with the mysql api only this time around) and make sure the database is connected
5. Train a model via an insert query
6. Make a prediction by specifying the columns independently via `WHERE`
|
1.0
|
Introduce "user flow" tests - Introduce one or two tests that attempt to mimic various ways a user might use mindsdb.
## Flow I
1. Connect a database (create an integration) via the http api
2. Create a model from the database using SQL
3. Analyse the model via the http api
4. Analyse the datasource it was trained on via the http api
6. Upload a datasource via the http api
7. Predict with that datasource from the database using SQL
8. Delete the model via the HTTP API
9. Make sure the `mindsdb` database no longer has the model
## Flow II
1. Start mindsdb (http api only)
2. Upload a dataset.
3. Add a database integration via the HTTP API
4. Restart mindsdb (with the mysql api only this time around) and make sure the database is connected
5. Train a model via an insert query
6. Make a prediction by specifying the columns independently via `WHERE`
|
test
|
introduce user flow tests introduce one or two tests that attempt to mimic various ways a user might use mindsdb flow i connect a database create an integration via the http api create a model from the database using sql analyse the model via the http api analyse the datasource it was trained on via the http api upload a datasource via the http api predict with that datasource from the database using sql delete the model via the http api make sure the mindsdb database no longer has the model flow ii start mindsdb http api only upload a dataset add a database integration via the http api restart mindsdb with the mysql api only this time around and make sure the database is connected train a model via an insert query make a prediction by specifying the columns independently via where
| 1
|
32,662
| 4,388,771,735
|
IssuesEvent
|
2016-08-08 19:58:02
|
hacklabr/paralapraca
|
https://api.github.com/repos/hacklabr/paralapraca
|
closed
|
Alterações na tela de tópico
|
design front-end seção: fórum
|
https://app.zeplin.io/project.html#pid=576ad22a40ea7eb4350a160f&sid=577d8bb858720b523d390e73
- [x] adicionar "última edição" no post e comentários
- [x] adicionar botão de "criar novo tópico" no header
|
1.0
|
Alterações na tela de tópico - https://app.zeplin.io/project.html#pid=576ad22a40ea7eb4350a160f&sid=577d8bb858720b523d390e73
- [x] adicionar "última edição" no post e comentários
- [x] adicionar botão de "criar novo tópico" no header
|
non_test
|
alterações na tela de tópico adicionar última edição no post e comentários adicionar botão de criar novo tópico no header
| 0
|
19,531
| 3,218,759,178
|
IssuesEvent
|
2015-10-08 04:35:21
|
pellcorp/tcpmon
|
https://api.github.com/repos/pellcorp/tcpmon
|
closed
|
Central Maven Repository
|
auto-migrated Priority-Medium Type-Defect
|
```
Hi,
is the tcpmon jar also available at the Central Maven Repository? If not, is it
planned to put it there?
Regards,
Stefan
```
Original issue reported on code.google.com by `mccabe....@googlemail.com` on 20 Mar 2013 at 3:17
|
1.0
|
Central Maven Repository - ```
Hi,
is the tcpmon jar also available at the Central Maven Repository? If not, is it
planned to put it there?
Regards,
Stefan
```
Original issue reported on code.google.com by `mccabe....@googlemail.com` on 20 Mar 2013 at 3:17
|
non_test
|
central maven repository hi is the tcpmon jar also available at the central maven repository if not is it planned to put it there regards stefan original issue reported on code google com by mccabe googlemail com on mar at
| 0
|
80,043
| 7,737,697,440
|
IssuesEvent
|
2018-05-28 09:10:59
|
openPMD/openPMD-api
|
https://api.github.com/repos/openPMD/openPMD-api
|
opened
|
C++17 Tests
|
good first issue help wanted tests third party
|
C++17 changed and improved quite a bit in stdlibs, especially with smart pointers.
We should add a coverage matrix entry for C++17 checking we are forward compatible.
|
1.0
|
C++17 Tests - C++17 changed and improved quite a bit in stdlibs, especially with smart pointers.
We should add a coverage matrix entry for C++17 checking we are forward compatible.
|
test
|
c tests c changed and improved quite a bit in stdlibs especially with smart pointers we should add a coverage matrix entry for c checking we are forward compatible
| 1
|
161,999
| 25,460,873,556
|
IssuesEvent
|
2022-11-24 18:50:07
|
kodadot/nft-gallery
|
https://api.github.com/repos/kodadot/nft-gallery
|
opened
|
Wallet connect dialog v2
|
design-request
|
Hello, I'll be working on the connect wallet dialog's improvements.
connected with:
#4144
#4303
|
1.0
|
Wallet connect dialog v2 - Hello, I'll be working on the connect wallet dialog's improvements.
connected with:
#4144
#4303
|
non_test
|
wallet connect dialog hello i ll be working on the connect wallet dialog s improvements connected with
| 0
|
46,811
| 11,889,006,439
|
IssuesEvent
|
2020-03-28 11:45:15
|
GoogleCloudPlatform/python-docs-samples
|
https://api.github.com/repos/GoogleCloudPlatform/python-docs-samples
|
opened
|
video.cloud-client.analyze.beta_snippets_test: test_track_objects failed
|
buildcop: issue priority: p1 type: bug
|
This test failed!
To configure my behavior, see [the Build Cop Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/master/packages/buildcop).
If I'm commenting on this issue too often, add the `buildcop: quiet` label and
I will stop commenting.
---
commit: c9a1257b7d3146c387ca26aed8a3771117b87873
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/8183963f-ed37-4e2e-a2e9-1d71546b5887), [Sponge](http://sponge2/8183963f-ed37-4e2e-a2e9-1d71546b5887)
status: failed
|
1.0
|
video.cloud-client.analyze.beta_snippets_test: test_track_objects failed - This test failed!
To configure my behavior, see [the Build Cop Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/master/packages/buildcop).
If I'm commenting on this issue too often, add the `buildcop: quiet` label and
I will stop commenting.
---
commit: c9a1257b7d3146c387ca26aed8a3771117b87873
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/8183963f-ed37-4e2e-a2e9-1d71546b5887), [Sponge](http://sponge2/8183963f-ed37-4e2e-a2e9-1d71546b5887)
status: failed
|
non_test
|
video cloud client analyze beta snippets test test track objects failed this test failed to configure my behavior see if i m commenting on this issue too often add the buildcop quiet label and i will stop commenting commit buildurl status failed
| 0
|
278,461
| 8,641,725,256
|
IssuesEvent
|
2018-11-24 20:56:09
|
kubeflow/kubeflow
|
https://api.github.com/repos/kubeflow/kubeflow
|
opened
|
Ingress and ArgoCD
|
area/0.5.0 priority/p2
|
We should figure out how to configure ingress and Kubeflow networking with ArgoCD.
See docs:
https://github.com/argoproj/argo-cd/blob/master/docs/ingress.md
By default ArgoCD expects to terminate TLS. That makes sense when ArgoCD is directly exposed (e.g. via LoadBalancer). But in our case it might make more sense to put it behind the same proxy and ingress we use for all of Kubeflow. In which case we can terminate TLS in front of ArgoCD server.
We might also want to integrate with ISTIO to mediate access to ArgoCD.
ArgoCD has an option "--insecure" to disable TLS.
https://github.com/argoproj/argo-cd/blob/master/docs/ingress.md
See also:
argoproj/argo-cd/issues#828
|
1.0
|
Ingress and ArgoCD - We should figure out how to configure ingress and Kubeflow networking with ArgoCD.
See docs:
https://github.com/argoproj/argo-cd/blob/master/docs/ingress.md
By default ArgoCD expects to terminate TLS. That makes sense when ArgoCD is directly exposed (e.g. via LoadBalancer). But in our case it might make more sense to put it behind the same proxy and ingress we use for all of Kubeflow. In which case we can terminate TLS in front of ArgoCD server.
We might also want to integrate with ISTIO to mediate access to ArgoCD.
ArgoCD has an option "--insecure" to disable TLS.
https://github.com/argoproj/argo-cd/blob/master/docs/ingress.md
See also:
argoproj/argo-cd/issues#828
|
non_test
|
ingress and argocd we should figure out how to configure ingress and kubeflow networking with argocd see docs by default argocd expects to terminate tls that makes sense when argocd is directly exposed e g via loadbalancer but in our case it might make more sense to put it behind the same proxy and ingress we use for all of kubeflow in which case we can terminate tls in front of argocd server we might also want to integrate with istio to mediate access to argocd argocd has an option insecure to disable tls see also argoproj argo cd issues
| 0
|
292,536
| 8,959,287,682
|
IssuesEvent
|
2019-01-27 21:11:59
|
aaugustin/websockets
|
https://api.github.com/repos/aaugustin/websockets
|
closed
|
[Suggestion] Echo server demo not compatibility with python 3.5
|
enhancement low priority
|
It would be nice to have a working example for people under 3.6.
This is how I get it working with 3.5.
First make an iterable object, bind the socket to it, and for every next iter, I will await on the socket.recv().
```python
class IterSocket:
def __init__(self, socket):
self.socket = socket
def __aiter__(self):
return self
async def __anext__(self):
return await self.socket.recv()
```
And finally, just wrap the websocket instance in this IterSocket object, and the rest is all the same in the docs.
```python
async def echo(websocket, path):
async for message in IterSocket(websocket):
await websocket.send(message)
```
Hope someone find this useful.
|
1.0
|
[Suggestion] Echo server demo not compatibility with python 3.5 - It would be nice to have a working example for people under 3.6.
This is how I get it working with 3.5.
First make an iterable object, bind the socket to it, and for every next iter, I will await on the socket.recv().
```python
class IterSocket:
def __init__(self, socket):
self.socket = socket
def __aiter__(self):
return self
async def __anext__(self):
return await self.socket.recv()
```
And finally, just wrap the websocket instance in this IterSocket object, and the rest is all the same in the docs.
```python
async def echo(websocket, path):
async for message in IterSocket(websocket):
await websocket.send(message)
```
Hope someone find this useful.
|
non_test
|
echo server demo not compatibility with python it would be nice to have a working example for people under this is how i get it working with first make an iterable object bind the socket to it and for every next iter i will await on the socket recv python class itersocket def init self socket self socket socket def aiter self return self async def anext self return await self socket recv and finally just wrap the websocket instance in this itersocket object and the rest is all the same in the docs python async def echo websocket path async for message in itersocket websocket await websocket send message hope someone find this useful
| 0
|
83,674
| 7,879,245,539
|
IssuesEvent
|
2018-06-26 12:53:31
|
Microsoft/vscode
|
https://api.github.com/repos/Microsoft/vscode
|
closed
|
Test improved workspace edit api
|
testplan-item
|
Refs: #10659
- [x] win @isidorn
- [x] linux @joaomoreno
Complexity: 2
We have enhanced the WorkspaceEdit-api to allow to create, delete, and rename files. Test that
* everything works as advertised
* things behave reasonable in corner cases, e.g. delete a file, then update it
|
1.0
|
Test improved workspace edit api - Refs: #10659
- [x] win @isidorn
- [x] linux @joaomoreno
Complexity: 2
We have enhanced the WorkspaceEdit-api to allow to create, delete, and rename files. Test that
* everything works as advertised
* things behave reasonable in corner cases, e.g. delete a file, then update it
|
test
|
test improved workspace edit api refs win isidorn linux joaomoreno complexity we have enhanced the workspaceedit api to allow to create delete and rename files test that everything works as advertised things behave reasonable in corner cases e g delete a file then update it
| 1
|
301,320
| 9,219,058,334
|
IssuesEvent
|
2019-03-11 14:42:00
|
sevenzk/SJKTCI
|
https://api.github.com/repos/sevenzk/SJKTCI
|
closed
|
[Ambil Order] Ditambahkan remaining Qty di grid sebelah kiri
|
Priority enhancement fixed
|
Ditambahkan remaining Qty di grid sebelah kiri di sebelah Qty dan Warna / Ukuran dihapus seperti gambar di bawah:
|
1.0
|
[Ambil Order] Ditambahkan remaining Qty di grid sebelah kiri - Ditambahkan remaining Qty di grid sebelah kiri di sebelah Qty dan Warna / Ukuran dihapus seperti gambar di bawah:
|
non_test
|
ditambahkan remaining qty di grid sebelah kiri ditambahkan remaining qty di grid sebelah kiri di sebelah qty dan warna ukuran dihapus seperti gambar di bawah
| 0
|
55,599
| 13,647,428,592
|
IssuesEvent
|
2020-09-26 03:15:25
|
TerryCavanagh/diceydungeonsbeta
|
https://api.github.com/repos/TerryCavanagh/diceydungeonsbeta
|
closed
|
Combine Summer and Winter Solstice
|
v0.5: 21st June Build
|
Weird idea: combine these into one card. The upgrade changes it from summer to winter.
|
1.0
|
Combine Summer and Winter Solstice - Weird idea: combine these into one card. The upgrade changes it from summer to winter.
|
non_test
|
combine summer and winter solstice weird idea combine these into one card the upgrade changes it from summer to winter
| 0
|
130,470
| 12,429,742,812
|
IssuesEvent
|
2020-05-25 09:02:58
|
music-encoding/guidelines
|
https://api.github.com/repos/music-encoding/guidelines
|
closed
|
Revise 10: Analysis Markup and Harmonies
|
documentation
|
This issue can be used to discuss chapter 10 of the guidelines.
|
1.0
|
Revise 10: Analysis Markup and Harmonies - This issue can be used to discuss chapter 10 of the guidelines.
|
non_test
|
revise analysis markup and harmonies this issue can be used to discuss chapter of the guidelines
| 0
|
26,743
| 4,241,276,409
|
IssuesEvent
|
2016-07-06 15:51:11
|
IgniteUI/ignite-ui
|
https://api.github.com/repos/IgniteUI/ignite-ui
|
closed
|
Generate HTML reports, only when executed for a specific control
|
nice-to-have tests
|
Such a report should be generated only when requested. `grunt verify:control` should not automatically generate such.
|
1.0
|
Generate HTML reports, only when executed for a specific control - Such a report should be generated only when requested. `grunt verify:control` should not automatically generate such.
|
test
|
generate html reports only when executed for a specific control such a report should be generated only when requested grunt verify control should not automatically generate such
| 1
|
226,915
| 25,010,697,267
|
IssuesEvent
|
2022-11-03 15:03:28
|
joshbnewton31080/SecurityShepherd
|
https://api.github.com/repos/joshbnewton31080/SecurityShepherd
|
closed
|
CVE-2022-31160 (Medium) detected in jquery-ui-1.8.19.min.js, jquery-ui-1.11.4.min.js - autoclosed
|
security vulnerability
|
## CVE-2022-31160 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>jquery-ui-1.8.19.min.js</b>, <b>jquery-ui-1.11.4.min.js</b></p></summary>
<p>
<details><summary><b>jquery-ui-1.8.19.min.js</b></p></summary>
<p>A curated set of user interface interactions, effects, widgets, and themes built on top of the jQuery JavaScript Library.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.8.19/jquery-ui.min.js">https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.8.19/jquery-ui.min.js</a></p>
<p>Path to dependency file: /src/main/webapp/index.jsp</p>
<p>Path to vulnerable library: /src/main/webapp/js/jqueryUI.js,/src/main/webapp/js/jqueryUI.js</p>
<p>
Dependency Hierarchy:
- :x: **jquery-ui-1.8.19.min.js** (Vulnerable Library)
</details>
<details><summary><b>jquery-ui-1.11.4.min.js</b></p></summary>
<p>A curated set of user interface interactions, effects, widgets, and themes built on top of the jQuery JavaScript Library.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.11.4/jquery-ui.min.js">https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.11.4/jquery-ui.min.js</a></p>
<p>Path to vulnerable library: /src/main/webapp/js/jquery-ui.min.js</p>
<p>
Dependency Hierarchy:
- :x: **jquery-ui-1.11.4.min.js** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/joshbnewton31080/SecurityShepherd/commit/76e744c932c4febe1f9aa5d8bd423657aef431e0">76e744c932c4febe1f9aa5d8bd423657aef431e0</a></p>
<p>Found in base branch: <b>dev</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
jQuery UI is a curated set of user interface interactions, effects, widgets, and themes built on top of jQuery. Versions prior to 1.13.2 are potentially vulnerable to cross-site scripting. Initializing a checkboxradio widget on an input enclosed within a label makes that parent label contents considered as the input label. Calling `.checkboxradio( "refresh" )` on such a widget and the initial HTML contained encoded HTML entities will make them erroneously get decoded. This can lead to potentially executing JavaScript code. The bug has been patched in jQuery UI 1.13.2. To remediate the issue, someone who can change the initial HTML can wrap all the non-input contents of the `label` in a `span`.
<p>Publish Date: 2022-07-20
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-31160>CVE-2022-31160</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31160">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31160</a></p>
<p>Release Date: 2022-07-20</p>
<p>Fix Resolution: jquery-ui - 1.13.2</p>
</p>
</details>
<p></p>
|
True
|
CVE-2022-31160 (Medium) detected in jquery-ui-1.8.19.min.js, jquery-ui-1.11.4.min.js - autoclosed - ## CVE-2022-31160 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>jquery-ui-1.8.19.min.js</b>, <b>jquery-ui-1.11.4.min.js</b></p></summary>
<p>
<details><summary><b>jquery-ui-1.8.19.min.js</b></p></summary>
<p>A curated set of user interface interactions, effects, widgets, and themes built on top of the jQuery JavaScript Library.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.8.19/jquery-ui.min.js">https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.8.19/jquery-ui.min.js</a></p>
<p>Path to dependency file: /src/main/webapp/index.jsp</p>
<p>Path to vulnerable library: /src/main/webapp/js/jqueryUI.js,/src/main/webapp/js/jqueryUI.js</p>
<p>
Dependency Hierarchy:
- :x: **jquery-ui-1.8.19.min.js** (Vulnerable Library)
</details>
<details><summary><b>jquery-ui-1.11.4.min.js</b></p></summary>
<p>A curated set of user interface interactions, effects, widgets, and themes built on top of the jQuery JavaScript Library.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.11.4/jquery-ui.min.js">https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.11.4/jquery-ui.min.js</a></p>
<p>Path to vulnerable library: /src/main/webapp/js/jquery-ui.min.js</p>
<p>
Dependency Hierarchy:
- :x: **jquery-ui-1.11.4.min.js** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/joshbnewton31080/SecurityShepherd/commit/76e744c932c4febe1f9aa5d8bd423657aef431e0">76e744c932c4febe1f9aa5d8bd423657aef431e0</a></p>
<p>Found in base branch: <b>dev</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
jQuery UI is a curated set of user interface interactions, effects, widgets, and themes built on top of jQuery. Versions prior to 1.13.2 are potentially vulnerable to cross-site scripting. Initializing a checkboxradio widget on an input enclosed within a label makes that parent label contents considered as the input label. Calling `.checkboxradio( "refresh" )` on such a widget and the initial HTML contained encoded HTML entities will make them erroneously get decoded. This can lead to potentially executing JavaScript code. The bug has been patched in jQuery UI 1.13.2. To remediate the issue, someone who can change the initial HTML can wrap all the non-input contents of the `label` in a `span`.
<p>Publish Date: 2022-07-20
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-31160>CVE-2022-31160</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31160">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31160</a></p>
<p>Release Date: 2022-07-20</p>
<p>Fix Resolution: jquery-ui - 1.13.2</p>
</p>
</details>
<p></p>
|
non_test
|
cve medium detected in jquery ui min js jquery ui min js autoclosed cve medium severity vulnerability vulnerable libraries jquery ui min js jquery ui min js jquery ui min js a curated set of user interface interactions effects widgets and themes built on top of the jquery javascript library library home page a href path to dependency file src main webapp index jsp path to vulnerable library src main webapp js jqueryui js src main webapp js jqueryui js dependency hierarchy x jquery ui min js vulnerable library jquery ui min js a curated set of user interface interactions effects widgets and themes built on top of the jquery javascript library library home page a href path to vulnerable library src main webapp js jquery ui min js dependency hierarchy x jquery ui min js vulnerable library found in head commit a href found in base branch dev vulnerability details jquery ui is a curated set of user interface interactions effects widgets and themes built on top of jquery versions prior to are potentially vulnerable to cross site scripting initializing a checkboxradio widget on an input enclosed within a label makes that parent label contents considered as the input label calling checkboxradio refresh on such a widget and the initial html contained encoded html entities will make them erroneously get decoded this can lead to potentially executing javascript code the bug has been patched in jquery ui to remediate the issue someone who can change the initial html can wrap all the non input contents of the label in a span publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution jquery ui
| 0
|
107,348
| 9,210,116,284
|
IssuesEvent
|
2019-03-09 01:48:57
|
Microsoft/vs-streamjsonrpc
|
https://api.github.com/repos/Microsoft/vs-streamjsonrpc
|
opened
|
PerfTests.BurstInvokeMessages test fails sometimes
|
test bug
|
From [this build](https://dev.azure.com/azure-public/vside/_build/results?buildId=4180&view=logs&jobId=0da5d1d9-276d-5173-c4c4-9d4d4ed14fdb&taskId=3367cfe7-6aa5-5a88-c888-e6814d74f6eb&lineStart=6967&lineEnd=7005&colStart=1&colEnd=1)
```
Failed PerfTests.BurstInvokeMessages(serverStream: FullDuplexStream { BeforeWrite = null, CanRead = True, CanSeek = False, CanTimeout = False, CanWrite = True, ... }, clientStream: FullDuplexStream { BeforeWrite = null, CanRead = True, CanSeek = False, CanTimeout = False, CanWrite = True, ... })
Error Message:
StreamJsonRpc.ConnectionLostException : The JSON-RPC connection with the remote party was lost before the request could complete.
Stack Trace:
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at StreamJsonRpc.JsonRpc.<InvokeCoreAsync>d__88`1.MoveNext() in /__w/1/s/src/StreamJsonRpc/JsonRpc.cs:line 1128
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at PerfTests.<BurstInvokeMessages>d__6.MoveNext() in /__w/1/s/src/StreamJsonRpc.Tests/PerfTests.cs:line 147
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
Standard Output Messages:
Server Critical: 13 : Connection closing (StreamError: Reading JSON RPC from the stream failed with BadRpcHeaderException: Header does not end with expected
character sequence:
). StreamJsonRpc.BadRpcHeaderException: Header does not end with expected
character sequence:
at StreamJsonRpc.HeaderDelimitedMessageHandler.<ReadHeadersAsync>d__35.MoveNext() in /__w/1/s/src/StreamJsonRpc/HeaderDelimitedMessageHandler.cs:line 441
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at StreamJsonRpc.HeaderDelimitedMessageHandler.<ReadCoreAsync>d__25.MoveNext() in /__w/1/s/src/StreamJsonRpc/HeaderDelimitedMessageHandler.cs:line 171
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at StreamJsonRpc.MessageHandlerBase.<ReadAsync>d__14.MoveNext() in /__w/1/s/src/StreamJsonRpc/MessageHandlerBase.cs:line 93
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at StreamJsonRpc.JsonRpc.<ReadAndHandleRequestsAsync>d__98.MoveNext() in /__w/1/s/src/StreamJsonRpc/JsonRpc.cs:line 1603
```
|
1.0
|
PerfTests.BurstInvokeMessages test fails sometimes - From [this build](https://dev.azure.com/azure-public/vside/_build/results?buildId=4180&view=logs&jobId=0da5d1d9-276d-5173-c4c4-9d4d4ed14fdb&taskId=3367cfe7-6aa5-5a88-c888-e6814d74f6eb&lineStart=6967&lineEnd=7005&colStart=1&colEnd=1)
```
Failed PerfTests.BurstInvokeMessages(serverStream: FullDuplexStream { BeforeWrite = null, CanRead = True, CanSeek = False, CanTimeout = False, CanWrite = True, ... }, clientStream: FullDuplexStream { BeforeWrite = null, CanRead = True, CanSeek = False, CanTimeout = False, CanWrite = True, ... })
Error Message:
StreamJsonRpc.ConnectionLostException : The JSON-RPC connection with the remote party was lost before the request could complete.
Stack Trace:
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at StreamJsonRpc.JsonRpc.<InvokeCoreAsync>d__88`1.MoveNext() in /__w/1/s/src/StreamJsonRpc/JsonRpc.cs:line 1128
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at PerfTests.<BurstInvokeMessages>d__6.MoveNext() in /__w/1/s/src/StreamJsonRpc.Tests/PerfTests.cs:line 147
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
Standard Output Messages:
Server Critical: 13 : Connection closing (StreamError: Reading JSON RPC from the stream failed with BadRpcHeaderException: Header does not end with expected
character sequence:
). StreamJsonRpc.BadRpcHeaderException: Header does not end with expected
character sequence:
at StreamJsonRpc.HeaderDelimitedMessageHandler.<ReadHeadersAsync>d__35.MoveNext() in /__w/1/s/src/StreamJsonRpc/HeaderDelimitedMessageHandler.cs:line 441
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at StreamJsonRpc.HeaderDelimitedMessageHandler.<ReadCoreAsync>d__25.MoveNext() in /__w/1/s/src/StreamJsonRpc/HeaderDelimitedMessageHandler.cs:line 171
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at StreamJsonRpc.MessageHandlerBase.<ReadAsync>d__14.MoveNext() in /__w/1/s/src/StreamJsonRpc/MessageHandlerBase.cs:line 93
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at StreamJsonRpc.JsonRpc.<ReadAndHandleRequestsAsync>d__98.MoveNext() in /__w/1/s/src/StreamJsonRpc/JsonRpc.cs:line 1603
```
|
test
|
perftests burstinvokemessages test fails sometimes from failed perftests burstinvokemessages serverstream fullduplexstream beforewrite null canread true canseek false cantimeout false canwrite true clientstream fullduplexstream beforewrite null canread true canseek false cantimeout false canwrite true error message streamjsonrpc connectionlostexception the json rpc connection with the remote party was lost before the request could complete stack trace at system runtime compilerservices taskawaiter throwfornonsuccess task task at system runtime compilerservices taskawaiter handlenonsuccessanddebuggernotification task task at streamjsonrpc jsonrpc d movenext in w s src streamjsonrpc jsonrpc cs line end of stack trace from previous location where exception was thrown at system runtime compilerservices taskawaiter throwfornonsuccess task task at system runtime compilerservices taskawaiter handlenonsuccessanddebuggernotification task task at perftests d movenext in w s src streamjsonrpc tests perftests cs line end of stack trace from previous location where exception was thrown at system runtime compilerservices taskawaiter throwfornonsuccess task task at system runtime compilerservices taskawaiter handlenonsuccessanddebuggernotification task task end of stack trace from previous location where exception was thrown at system runtime compilerservices taskawaiter throwfornonsuccess task task at system runtime compilerservices taskawaiter handlenonsuccessanddebuggernotification task task end of stack trace from previous location where exception was thrown at system runtime compilerservices taskawaiter throwfornonsuccess task task at system runtime compilerservices taskawaiter handlenonsuccessanddebuggernotification task task standard output messages server critical connection closing streamerror reading json rpc from the stream failed with badrpcheaderexception header does not end with expected character sequence streamjsonrpc badrpcheaderexception header does not end with expected character sequence at streamjsonrpc headerdelimitedmessagehandler d movenext in w s src streamjsonrpc headerdelimitedmessagehandler cs line end of stack trace from previous location where exception was thrown at system runtime compilerservices taskawaiter throwfornonsuccess task task at system runtime compilerservices taskawaiter handlenonsuccessanddebuggernotification task task at streamjsonrpc headerdelimitedmessagehandler d movenext in w s src streamjsonrpc headerdelimitedmessagehandler cs line end of stack trace from previous location where exception was thrown at system runtime compilerservices taskawaiter throwfornonsuccess task task at system runtime compilerservices taskawaiter handlenonsuccessanddebuggernotification task task at streamjsonrpc messagehandlerbase d movenext in w s src streamjsonrpc messagehandlerbase cs line end of stack trace from previous location where exception was thrown at system runtime compilerservices taskawaiter throwfornonsuccess task task at system runtime compilerservices taskawaiter handlenonsuccessanddebuggernotification task task at streamjsonrpc jsonrpc d movenext in w s src streamjsonrpc jsonrpc cs line
| 1
|
9,695
| 3,306,195,610
|
IssuesEvent
|
2015-11-04 10:25:57
|
workshopper/workshopper-adventure
|
https://api.github.com/repos/workshopper/workshopper-adventure
|
opened
|
Add information about the difference between workshopper, adventure and workshopper-adventure.
|
documentation
|
At this point it is slightly unclear what the difference between those frameworks is. It would be good to make clear why they existed and what they can do.
|
1.0
|
Add information about the difference between workshopper, adventure and workshopper-adventure. - At this point it is slightly unclear what the difference between those frameworks is. It would be good to make clear why they existed and what they can do.
|
non_test
|
add information about the difference between workshopper adventure and workshopper adventure at this point it is slightly unclear what the difference between those frameworks is it would be good to make clear why they existed and what they can do
| 0
|
19,050
| 3,744,318,825
|
IssuesEvent
|
2016-03-10 01:07:40
|
rancher/rancher
|
https://api.github.com/repos/rancher/rancher
|
closed
|
Docke 1.9 named volumes removed with last container
|
kind/enhancement release/v1.0.0 status/resolved status/to-test
|
In Docker 1.9 volumes are a top level entity, and can be created and named. A named volume is a replacement for data containers, and to some extent lines up with host bind mounts for explicitly knowing where data is being stored.
Current Rancher behavior cleans up volumes attached to containers. Now that named volumes are an option, we should likely not delete the named volume when the container is removed. It is possible a user would want to use it again.
|
1.0
|
Docke 1.9 named volumes removed with last container - In Docker 1.9 volumes are a top level entity, and can be created and named. A named volume is a replacement for data containers, and to some extent lines up with host bind mounts for explicitly knowing where data is being stored.
Current Rancher behavior cleans up volumes attached to containers. Now that named volumes are an option, we should likely not delete the named volume when the container is removed. It is possible a user would want to use it again.
|
test
|
docke named volumes removed with last container in docker volumes are a top level entity and can be created and named a named volume is a replacement for data containers and to some extent lines up with host bind mounts for explicitly knowing where data is being stored current rancher behavior cleans up volumes attached to containers now that named volumes are an option we should likely not delete the named volume when the container is removed it is possible a user would want to use it again
| 1
|
209,463
| 7,176,332,112
|
IssuesEvent
|
2018-01-31 09:41:43
|
hazelcast/hazelcast
|
https://api.github.com/repos/hazelcast/hazelcast
|
closed
|
Write Consistency Improvements
|
Priority: Medium Source: Internal Team: Core Type: Enhancement
|
- [x] Sync writes and sync backups should be consistent and synchronous from caller point of view.
- [x] Graceful shutdown should:
- [x] prevent receiving new operations
- [x] wait for in-flight operations to finish and send responses back to callers
https://hazelcast.atlassian.net/wiki/display/PM/Write+Consistency+Improvements
|
1.0
|
Write Consistency Improvements - - [x] Sync writes and sync backups should be consistent and synchronous from caller point of view.
- [x] Graceful shutdown should:
- [x] prevent receiving new operations
- [x] wait for in-flight operations to finish and send responses back to callers
https://hazelcast.atlassian.net/wiki/display/PM/Write+Consistency+Improvements
|
non_test
|
write consistency improvements sync writes and sync backups should be consistent and synchronous from caller point of view graceful shutdown should prevent receiving new operations wait for in flight operations to finish and send responses back to callers
| 0
|
301,524
| 26,054,718,234
|
IssuesEvent
|
2022-12-22 23:15:48
|
dagger/dagger
|
https://api.github.com/repos/dagger/dagger
|
closed
|
Port and re-enable docs integration tests
|
area/tests area/ci
|
Docs integration tests (`./docs/learn/tests`) were never ported after the Europa release.
We need to have basic coverage, at least of the getting started example.
|
1.0
|
Port and re-enable docs integration tests - Docs integration tests (`./docs/learn/tests`) were never ported after the Europa release.
We need to have basic coverage, at least of the getting started example.
|
test
|
port and re enable docs integration tests docs integration tests docs learn tests were never ported after the europa release we need to have basic coverage at least of the getting started example
| 1
|
136,646
| 30,567,987,636
|
IssuesEvent
|
2023-07-20 19:24:19
|
PolicyEngine/policyengine-us
|
https://api.github.com/repos/PolicyEngine/policyengine-us
|
closed
|
Reduce state itemized deductions code duplication
|
code-health state-income-tax
|
Most state income taxes involve calculation of itemized deductions based on federal itemized deductions with some revisions. The code to do that is repeated for every state that has itemized deductions, which is not only error prone (having multiple implementations of what should be the same logic) but involves extra computation. Both these problems would be eliminated by adding two new variables (`itemized_deductions_less_salt` and `capped_property_taxes`) and then using them when appropriate to reduce state income tax code duplication.
|
1.0
|
Reduce state itemized deductions code duplication - Most state income taxes involve calculation of itemized deductions based on federal itemized deductions with some revisions. The code to do that is repeated for every state that has itemized deductions, which is not only error prone (having multiple implementations of what should be the same logic) but involves extra computation. Both these problems would be eliminated by adding two new variables (`itemized_deductions_less_salt` and `capped_property_taxes`) and then using them when appropriate to reduce state income tax code duplication.
|
non_test
|
reduce state itemized deductions code duplication most state income taxes involve calculation of itemized deductions based on federal itemized deductions with some revisions the code to do that is repeated for every state that has itemized deductions which is not only error prone having multiple implementations of what should be the same logic but involves extra computation both these problems would be eliminated by adding two new variables itemized deductions less salt and capped property taxes and then using them when appropriate to reduce state income tax code duplication
| 0
|
188,353
| 14,444,166,758
|
IssuesEvent
|
2020-12-07 20:48:16
|
RockefellerArchiveCenter/dimes
|
https://api.github.com/repos/RockefellerArchiveCenter/dimes
|
closed
|
Add link to objects from MyList
|
my list ux testing
|
## Is your feature request related to a problem? Please describe.
Usability testing showed that users sought a link directly to the object url from My List, instead of only a link to the parent collection.
## Describe the solution you'd like
Make the object title in My List a link. This link should probably be styled with an underline, because otherwise I don't think it is clearly a link from the context.
|
1.0
|
Add link to objects from MyList - ## Is your feature request related to a problem? Please describe.
Usability testing showed that users sought a link directly to the object url from My List, instead of only a link to the parent collection.
## Describe the solution you'd like
Make the object title in My List a link. This link should probably be styled with an underline, because otherwise I don't think it is clearly a link from the context.
|
test
|
add link to objects from mylist is your feature request related to a problem please describe usability testing showed that users sought a link directly to the object url from my list instead of only a link to the parent collection describe the solution you d like make the object title in my list a link this link should probably be styled with an underline because otherwise i don t think it is clearly a link from the context
| 1
|
25,592
| 5,184,683,100
|
IssuesEvent
|
2017-01-20 07:28:03
|
christhekeele/mnemonix
|
https://api.github.com/repos/christhekeele/mnemonix
|
closed
|
Support an Expiration capability
|
Kind: Documentation Kind: Feature Status: In Development Status: Needs Discussion
|
This depends on #2.
Requirements are:
- a`Mnemonix.Utility.Expiry` polyfill for many stores
- the introduction of at least one API method `Mnemonix.expires(store, key, ttl)`
- the introduction of at least one callback `Mnemonix.Store.Behaviour.expires/3`
- raising `Mnemonix.UtilityNotSupportedException in`Mnemonix.Store.Behaviour.Default.expires/3` and kin
- implementing native and polyfill behaviour in all existing stores
The polyfill will have to touch `put/3` to thread a `ttl` on write and a `fetch/2` to no-op the read and `delete/2` the key if the `ttl` is up.
This would allow for store-wide expiration of entries, and explicit control of key ttls. The question of whether or not to allow expiry individual entries on write in a single operation is more nuanced. It may require adding a hash of opts to every `Mnemonix` API function, which might be inevitable, but I'd like to put that off as long as possible.
|
1.0
|
Support an Expiration capability - This depends on #2.
Requirements are:
- a`Mnemonix.Utility.Expiry` polyfill for many stores
- the introduction of at least one API method `Mnemonix.expires(store, key, ttl)`
- the introduction of at least one callback `Mnemonix.Store.Behaviour.expires/3`
- raising `Mnemonix.UtilityNotSupportedException in`Mnemonix.Store.Behaviour.Default.expires/3` and kin
- implementing native and polyfill behaviour in all existing stores
The polyfill will have to touch `put/3` to thread a `ttl` on write and a `fetch/2` to no-op the read and `delete/2` the key if the `ttl` is up.
This would allow for store-wide expiration of entries, and explicit control of key ttls. The question of whether or not to allow expiry individual entries on write in a single operation is more nuanced. It may require adding a hash of opts to every `Mnemonix` API function, which might be inevitable, but I'd like to put that off as long as possible.
|
non_test
|
support an expiration capability this depends on requirements are a mnemonix utility expiry polyfill for many stores the introduction of at least one api method mnemonix expires store key ttl the introduction of at least one callback mnemonix store behaviour expires raising mnemonix utilitynotsupportedexception in mnemonix store behaviour default expires and kin implementing native and polyfill behaviour in all existing stores the polyfill will have to touch put to thread a ttl on write and a fetch to no op the read and delete the key if the ttl is up this would allow for store wide expiration of entries and explicit control of key ttls the question of whether or not to allow expiry individual entries on write in a single operation is more nuanced it may require adding a hash of opts to every mnemonix api function which might be inevitable but i d like to put that off as long as possible
| 0
|
109,889
| 23,837,856,956
|
IssuesEvent
|
2022-09-06 07:48:02
|
puzzle/decidim-zuerich
|
https://api.github.com/repos/puzzle/decidim-zuerich
|
closed
|
Ortsbezeichnungen werden vom Geocoder nicht identifiziert.
|
bug geocoder/map
|
Ortsbezeichnungen werden vom Geocoder nicht erkannt, obwohl sie von OSM so vorgeschlagen und übernommen werden.
Nachstellbar hier: https://mitwirken.integ.stadt-zuerich.ch/admin/participatory_processes/test/components/286/manage/meetings/78/edit
-> es klappt, wenn der Kindergarten-Teil weggelassen wird. Ich habe mit unterschiedlichen Adressen gespielt (wegen Abständen und Sonderzeichen) und es spielt keine Rolle: Sobald eine Ortsbezeichnung da ist (wie von OSM vorgeschlagen) wird die Adresse nicht übernommen.
Was wäre zur Lösung einfacher:
1. Fix, sodass die Orte erkannt werden, oder
2. Ausschalten, dass Ortsbezeichnungen überhaupt vorgeschlagen werden?
|
1.0
|
Ortsbezeichnungen werden vom Geocoder nicht identifiziert. - Ortsbezeichnungen werden vom Geocoder nicht erkannt, obwohl sie von OSM so vorgeschlagen und übernommen werden.
Nachstellbar hier: https://mitwirken.integ.stadt-zuerich.ch/admin/participatory_processes/test/components/286/manage/meetings/78/edit
-> es klappt, wenn der Kindergarten-Teil weggelassen wird. Ich habe mit unterschiedlichen Adressen gespielt (wegen Abständen und Sonderzeichen) und es spielt keine Rolle: Sobald eine Ortsbezeichnung da ist (wie von OSM vorgeschlagen) wird die Adresse nicht übernommen.
Was wäre zur Lösung einfacher:
1. Fix, sodass die Orte erkannt werden, oder
2. Ausschalten, dass Ortsbezeichnungen überhaupt vorgeschlagen werden?
|
non_test
|
ortsbezeichnungen werden vom geocoder nicht identifiziert ortsbezeichnungen werden vom geocoder nicht erkannt obwohl sie von osm so vorgeschlagen und übernommen werden nachstellbar hier es klappt wenn der kindergarten teil weggelassen wird ich habe mit unterschiedlichen adressen gespielt wegen abständen und sonderzeichen und es spielt keine rolle sobald eine ortsbezeichnung da ist wie von osm vorgeschlagen wird die adresse nicht übernommen was wäre zur lösung einfacher fix sodass die orte erkannt werden oder ausschalten dass ortsbezeichnungen überhaupt vorgeschlagen werden
| 0
|
204,643
| 15,512,132,140
|
IssuesEvent
|
2021-03-12 01:03:17
|
pixeline/bugs
|
https://api.github.com/repos/pixeline/bugs
|
closed
|
New issue: Impossible to add a New Issue into admin mode
|
Testers needed Wait for your comments bug ¿ Fixed ?
|
Hello Patrick,
Avec le package du 10-03 je ne peux plus ajouter de nouveaux tickets.
En cliquant sur le bouton j'ai l'erreur suivante:
Unhandled Exception
Message:
syntax error, unexpected end of file
Location:
E:\xampp\htdocs\bugtracker2\app\laravel\view.php(353) : eval()'d code on line 236
Stack Trace:
#0 E:\xampp\htdocs\bugtracker2\app\laravel\view.php(324): Laravel\View->get()
#1 E:\xampp\htdocs\bugtracker2\app\laravel\view.php(406): Laravel\View->render()
#2 E:\xampp\htdocs\bugtracker2\app\laravel\view.php(341): Laravel\View->data()
#3 E:\xampp\htdocs\bugtracker2\app\laravel\view.php(324): Laravel\View->get()
#4 E:\xampp\htdocs\bugtracker2\app\laravel\view.php(534): Laravel\View->render()
#5 E:\xampp\htdocs\bugtracker2\app\laravel\response.php(240): Laravel\View->__toString()
#6 E:\xampp\htdocs\bugtracker2\app\laravel\laravel.php(173): Laravel\Response->render()
#7 E:\xampp\htdocs\bugtracker2\index.php(19): require('E:\\xampp\\htdocs...')
#8 {main}
|
1.0
|
New issue: Impossible to add a New Issue into admin mode - Hello Patrick,
Avec le package du 10-03 je ne peux plus ajouter de nouveaux tickets.
En cliquant sur le bouton j'ai l'erreur suivante:
Unhandled Exception
Message:
syntax error, unexpected end of file
Location:
E:\xampp\htdocs\bugtracker2\app\laravel\view.php(353) : eval()'d code on line 236
Stack Trace:
#0 E:\xampp\htdocs\bugtracker2\app\laravel\view.php(324): Laravel\View->get()
#1 E:\xampp\htdocs\bugtracker2\app\laravel\view.php(406): Laravel\View->render()
#2 E:\xampp\htdocs\bugtracker2\app\laravel\view.php(341): Laravel\View->data()
#3 E:\xampp\htdocs\bugtracker2\app\laravel\view.php(324): Laravel\View->get()
#4 E:\xampp\htdocs\bugtracker2\app\laravel\view.php(534): Laravel\View->render()
#5 E:\xampp\htdocs\bugtracker2\app\laravel\response.php(240): Laravel\View->__toString()
#6 E:\xampp\htdocs\bugtracker2\app\laravel\laravel.php(173): Laravel\Response->render()
#7 E:\xampp\htdocs\bugtracker2\index.php(19): require('E:\\xampp\\htdocs...')
#8 {main}
|
test
|
new issue impossible to add a new issue into admin mode hello patrick avec le package du je ne peux plus ajouter de nouveaux tickets en cliquant sur le bouton j ai l erreur suivante unhandled exception message syntax error unexpected end of file location e xampp htdocs app laravel view php eval d code on line stack trace e xampp htdocs app laravel view php laravel view get e xampp htdocs app laravel view php laravel view render e xampp htdocs app laravel view php laravel view data e xampp htdocs app laravel view php laravel view get e xampp htdocs app laravel view php laravel view render e xampp htdocs app laravel response php laravel view tostring e xampp htdocs app laravel laravel php laravel response render e xampp htdocs index php require e xampp htdocs main
| 1
|
92,592
| 8,371,545,650
|
IssuesEvent
|
2018-10-05 01:19:26
|
kubernetes/kubernetes
|
https://api.github.com/repos/kubernetes/kubernetes
|
closed
|
Port test/e2e_node/kubelet_test to test/e2e/common
|
area/test kind/cleanup sig/node
|
**What happened**:
These tests are errantly listed as `[Conformance]` (ref: https://github.com/kubernetes/kubernetes/pull/67084) but aren't actually run as part of Conformance. They need to be moved to test/e2e/common to be included.
To my eyes they may meet the criteria for conformance. There's definitely nothing about them that is node specific. They should be running as part of our regular CI, and they should probably be running as presubmits. Porting them to test/e2e/common would cause this to happen.
/kind cleanup
/sig node
/area test
/assign @mgdevstack @mkurylec
|
1.0
|
Port test/e2e_node/kubelet_test to test/e2e/common - **What happened**:
These tests are errantly listed as `[Conformance]` (ref: https://github.com/kubernetes/kubernetes/pull/67084) but aren't actually run as part of Conformance. They need to be moved to test/e2e/common to be included.
To my eyes they may meet the criteria for conformance. There's definitely nothing about them that is node specific. They should be running as part of our regular CI, and they should probably be running as presubmits. Porting them to test/e2e/common would cause this to happen.
/kind cleanup
/sig node
/area test
/assign @mgdevstack @mkurylec
|
test
|
port test node kubelet test to test common what happened these tests are errantly listed as ref but aren t actually run as part of conformance they need to be moved to test common to be included to my eyes they may meet the criteria for conformance there s definitely nothing about them that is node specific they should be running as part of our regular ci and they should probably be running as presubmits porting them to test common would cause this to happen kind cleanup sig node area test assign mgdevstack mkurylec
| 1
|
112,078
| 9,553,121,816
|
IssuesEvent
|
2019-05-02 18:25:20
|
aws/amazon-ecs-agent
|
https://api.github.com/repos/aws/amazon-ecs-agent
|
closed
|
Flaky Integ Test - TestShutdownOrder hangs occasionally
|
kind/testing
|
<!--
For urgent operational issues, please contact AWS Support directly.
https://aws.amazon.com/premiumsupport/
Please provide the following information:
-->
### Summary
<!-- Please provide a brief outline of the issue -->
TestShutdownOrder hung occasionally. It doesn't look like we happen to reach timeout on this test from the total running time seen in logs.
### Description
<!-- Provide detailed information about this issue -->
<!-- Not required for feature requests -->
### Expected Behavior
Test passes in ~20s.
### Observed Behavior
Test hung.
### Environment Details
<!--
Examples:
* docker info
* curl http://localhost:51678/v1/metadata
* df -h
-->
### Supporting Log Snippets
<!--
Please have a look at https://github.com/awslabs/ecs-logs-collector
for the data we typically require for investigation
Please note that GitHub issues are public, remove sensitive data from logs before posting.
If you are not comfortable posting your logs here, please let us know and we
can provide an alternate method.
-->
```
=== RUN TestShutdownOrder
2019-03-08T01:16:19Z [INFO] Managed task [testDependencyHealthyTimeout]: redundant container state change. dependency to STOPPED, but already STOPPED
2019-03-08T01:16:19Z [INFO] Image excluded from cleanup: amazon/amazon-ecs-agent:latest
2019-03-08T01:16:19Z [INFO] Image excluded from cleanup: amazon/amazon-ecs-pause:0.1.0
2019-03-08T01:16:19Z [WARN] Unable to fetch user data: blackholed
2019-03-08T01:16:19Z [CRITICAL] Unable to communicate with EC2 Metadata service to infer region: blackholed
2019-03-08T01:16:19Z [CRITICAL] Configuration key not set, key: AWSRegion
2019-03-08T01:16:19Z [INFO] Unable to get Docker client for version 1.17: version detection using MinAPIVersion: unsupported version: 1.17
2019-03-08T01:16:19Z [INFO] Unable to get Docker client for version 1.18: version detection using MinAPIVersion: unsupported version: 1.18
2019-03-08T01:16:19Z [INFO] Unable to get Docker client for version 1.19: version detection using MinAPIVersion: unsupported version: 1.19
2019-03-08T01:16:19Z [INFO] Unable to get Docker client for version 1.20: version detection using MinAPIVersion: unsupported version: 1.20
2019-03-08T01:16:19Z [INFO] Unable to get Docker client for version 1.21: version detection using MinAPIVersion: unsupported version: 1.21
2019-03-08T01:16:19Z [INFO] Unable to get Docker client for version 1.22: version detection using MinAPIVersion: unsupported version: 1.22
2019-03-08T01:16:19Z [INFO] Unable to get Docker client for version 1.23: version detection using MinAPIVersion: unsupported version: 1.23
2019-03-08T01:16:19Z [INFO] Unable to get Docker client for version 1.31: version detection using MinAPIVersion: unsupported version: 1.31
2019-03-08T01:16:19Z [INFO] Unable to get Docker client for version 1.32: version detection using MinAPIVersion: unsupported version: 1.32
2019-03-08T01:16:19Z [INFO] Managed task [testShutdownOrder]: unable to create task state change event []: create task state change event api: status not recognized by ECS: NONE
2019-03-08T01:16:19Z [INFO] Task engine [testShutdownOrder]: found cached image microsoft/windowsservercore, use it directly for container C
2019-03-08T01:16:19Z [INFO] Adding image name- microsoft/windowsservercore to Image state- sha256:1fbef5019583cc35cbbe6a350b69f0b615fd2834d628ffeefef2f9f51e01a607
2019-03-08T01:16:19Z [INFO] Updating container reference C in Image State - sha256:1fbef5019583cc35cbbe6a350b69f0b615fd2834d628ffeefef2f9f51e01a607
2019-03-08T01:16:19Z [WARN] Managed task [testShutdownOrder]: failed to write container [C] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:19Z [INFO] Task engine [testShutdownOrder]: creating container: C
2019-03-08T01:16:19Z [WARN] Task testShutdownOrder container C memory setting is too low, increasing to 268435456 bytes
2019-03-08T01:16:19Z [INFO] Task engine [testShutdownOrder]: created container name mapping for task: C -> ecs-family-1-C-dcfcb2cf85f7d2c6a701
2019-03-08T01:16:19Z [INFO] Task engine [testShutdownOrder]: created docker container for task: C -> 7a52372dc0661a1b400113e33ddf2d3a6d2785ecf7edc04e86ae3f2d93c6e329
2019-03-08T01:16:19Z [INFO] Task engine [testShutdownOrder]: created docker container for task: C -> 7a52372dc0661a1b400113e33ddf2d3a6d2785ecf7edc04e86ae3f2d93c6e329, took 19.5202ms
2019-03-08T01:16:19Z [WARN] Managed task [testShutdownOrder]: failed to write container [C] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:19Z [INFO] Task engine [testShutdownOrder]: starting container: C
2019-03-08T01:16:23Z [INFO] Task engine [testShutdownOrder]: started docker container for task: C -> 7a52372dc0661a1b400113e33ddf2d3a6d2785ecf7edc04e86ae3f2d93c6e329, took 3.1258983s
2019-03-08T01:16:23Z [WARN] Managed task [testShutdownOrder]: failed to write container [C] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:23Z [INFO] Managed task [testShutdownOrder]: sending container change event [C]: testShutdownOrder C -> RUNNING, Known Sent: NONE
2019-03-08T01:16:23Z [INFO] Managed task [testShutdownOrder]: sent container change event [C]: testShutdownOrder C -> RUNNING, Known Sent: NONE
2019-03-08T01:16:23Z [INFO] Managed task [testShutdownOrder]: redundant container state change. C to RUNNING, but already RUNNING
2019-03-08T01:16:23Z [INFO] Task engine [testShutdownOrder]: found cached image microsoft/windowsservercore, use it directly for container B
2019-03-08T01:16:23Z [INFO] Updating container reference B in Image State - sha256:1fbef5019583cc35cbbe6a350b69f0b615fd2834d628ffeefef2f9f51e01a607
2019-03-08T01:16:23Z [WARN] Managed task [testShutdownOrder]: failed to write container [B] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:23Z [INFO] Task engine [testShutdownOrder]: creating container: B
2019-03-08T01:16:23Z [WARN] Task testShutdownOrder container B memory setting is too low, increasing to 268435456 bytes
2019-03-08T01:16:23Z [INFO] Task engine [testShutdownOrder]: created container name mapping for task: B -> ecs-family-1-B-fe8a908adaea8ec2b701
2019-03-08T01:16:23Z [INFO] Task engine [testShutdownOrder]: created docker container for task: B -> daf91503ac66de49629ff1463f57e74aa3f3d07f9819615189d76c1b7cef5c4b
2019-03-08T01:16:23Z [INFO] Task engine [testShutdownOrder]: created docker container for task: B -> daf91503ac66de49629ff1463f57e74aa3f3d07f9819615189d76c1b7cef5c4b, took 27.3455ms
2019-03-08T01:16:23Z [WARN] Managed task [testShutdownOrder]: failed to write container [B] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:23Z [INFO] Task engine [testShutdownOrder]: starting container: B
2019-03-08T01:16:25Z [INFO] Task engine [testShutdownOrder]: started docker container for task: B -> daf91503ac66de49629ff1463f57e74aa3f3d07f9819615189d76c1b7cef5c4b, took 1.9657666s
2019-03-08T01:16:25Z [WARN] Managed task [testShutdownOrder]: failed to write container [B] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:25Z [INFO] Managed task [testShutdownOrder]: sending container change event [B]: testShutdownOrder B -> RUNNING, Known Sent: NONE
2019-03-08T01:16:25Z [INFO] Managed task [testShutdownOrder]: sent container change event [B]: testShutdownOrder B -> RUNNING, Known Sent: NONE
2019-03-08T01:16:25Z [INFO] Managed task [testShutdownOrder]: redundant container state change. B to RUNNING, but already RUNNING
2019-03-08T01:16:25Z [INFO] Task engine [testShutdownOrder]: found cached image microsoft/windowsservercore, use it directly for container A
2019-03-08T01:16:25Z [INFO] Updating container reference A in Image State - sha256:1fbef5019583cc35cbbe6a350b69f0b615fd2834d628ffeefef2f9f51e01a607
2019-03-08T01:16:25Z [WARN] Managed task [testShutdownOrder]: failed to write container [A] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:25Z [INFO] Task engine [testShutdownOrder]: creating container: A
2019-03-08T01:16:25Z [WARN] Task testShutdownOrder container A memory setting is too low, increasing to 268435456 bytes
2019-03-08T01:16:25Z [INFO] Task engine [testShutdownOrder]: created container name mapping for task: A -> ecs-family-1-A-d2eebd8a90d7aae53900
2019-03-08T01:16:25Z [INFO] Task engine [testShutdownOrder]: created docker container for task: A -> a57081700e465e60ebbd3ef1bc3204deac1b505fcc0c2ef6b849cc8446d11d80
2019-03-08T01:16:25Z [INFO] Task engine [testShutdownOrder]: created docker container for task: A -> a57081700e465e60ebbd3ef1bc3204deac1b505fcc0c2ef6b849cc8446d11d80, took 33.2086ms
2019-03-08T01:16:25Z [WARN] Managed task [testShutdownOrder]: failed to write container [A] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:25Z [INFO] Task engine [testShutdownOrder]: starting container: A
2019-03-08T01:16:29Z [INFO] Task engine [testShutdownOrder]: started docker container for task: A -> a57081700e465e60ebbd3ef1bc3204deac1b505fcc0c2ef6b849cc8446d11d80, took 4.3983237s
2019-03-08T01:16:29Z [WARN] Managed task [testShutdownOrder]: failed to write container [A] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:29Z [INFO] Managed task [testShutdownOrder]: sending container change event [A]: testShutdownOrder A -> RUNNING, Known Sent: NONE
2019-03-08T01:16:29Z [INFO] Managed task [testShutdownOrder]: sent container change event [A]: testShutdownOrder A -> RUNNING, Known Sent: NONE
2019-03-08T01:16:29Z [INFO] Managed task [testShutdownOrder]: redundant container state change. A to RUNNING, but already RUNNING
2019-03-08T01:16:29Z [INFO] Task engine [testShutdownOrder]: found cached image microsoft/windowsservercore, use it directly for container parent
2019-03-08T01:16:29Z [INFO] Updating container reference parent in Image State - sha256:1fbef5019583cc35cbbe6a350b69f0b615fd2834d628ffeefef2f9f51e01a607
2019-03-08T01:16:29Z [WARN] Managed task [testShutdownOrder]: failed to write container [parent] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:29Z [INFO] Task engine [testShutdownOrder]: creating container: parent
2019-03-08T01:16:29Z [WARN] Task testShutdownOrder container parent memory setting is too low, increasing to 268435456 bytes
2019-03-08T01:16:29Z [INFO] Task engine [testShutdownOrder]: created container name mapping for task: parent -> ecs-family-1-parent-a0d1c1f9f9e3c498a801
2019-03-08T01:16:29Z [INFO] Task engine [testShutdownOrder]: created docker container for task: parent -> b8ed239e5294c9177f1be41642a24d069b63e4c9d5a81b1fc8b56158d6485947
2019-03-08T01:16:29Z [INFO] Task engine [testShutdownOrder]: created docker container for task: parent -> b8ed239e5294c9177f1be41642a24d069b63e4c9d5a81b1fc8b56158d6485947, took 22.4593ms
2019-03-08T01:16:29Z [WARN] Managed task [testShutdownOrder]: failed to write container [parent] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:29Z [INFO] Managed task [testShutdownOrder]: unable to create task state change event []: create task state change event api: status not recognized by ECS: CREATED
2019-03-08T01:16:29Z [INFO] Task engine [testShutdownOrder]: starting container: parent
2019-03-08T01:16:33Z [INFO] Task engine [testShutdownOrder]: started docker container for task: parent -> b8ed239e5294c9177f1be41642a24d069b63e4c9d5a81b1fc8b56158d6485947, took 4.0985045s
2019-03-08T01:16:33Z [WARN] Managed task [testShutdownOrder]: failed to write container [parent] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:33Z [INFO] Managed task [testShutdownOrder]: sending container change event [parent]: testShutdownOrder parent -> RUNNING, Known Sent: NONE
2019-03-08T01:16:33Z [INFO] Managed task [testShutdownOrder]: sent container change event [parent]: testShutdownOrder parent -> RUNNING, Known Sent: NONE
2019-03-08T01:16:33Z [INFO] Managed task [testShutdownOrder]: sending task change event [testShutdownOrder -> RUNNING, Known Sent: NONE, PullStartedAt: 0001-01-01 00:00:00 +0000 UTC, PullStoppedAt: 0001-01-01 00:00:00 +0000 UTC, ExecutionStoppedAt: 0001-01-01 00:00:00 +0000 UTC]
2019-03-08T01:16:33Z [INFO] Managed task [testShutdownOrder]: sent task change event [testShutdownOrder -> RUNNING, Known Sent: NONE, PullStartedAt: 0001-01-01 00:00:00 +0000 UTC, PullStoppedAt: 0001-01-01 00:00:00 +0000 UTC, ExecutionStoppedAt: 0001-01-01 00:00:00 +0000 UTC]
2019-03-08T01:16:33Z [INFO] Managed task [testShutdownOrder]: task at steady state: RUNNING
2019-03-08T01:16:33Z [INFO] Managed task [testShutdownOrder]: redundant container state change. parent to RUNNING, but already RUNNING
2019-03-08T01:16:33Z [INFO] Managed task [testShutdownOrder]: task at steady state: RUNNING
2019-03-08T01:16:39Z [INFO] Task [testShutdownOrder]: recording execution stopped time. Essential container [parent] stopped at: 2019-03-08 01:16:39.9535716 +0000 GMT m=+688.132778001
2019-03-08T01:16:39Z [WARN] Managed task [testShutdownOrder]: failed to write container [parent] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:39Z [INFO] Managed task [testShutdownOrder]: sending container change event [parent]: testShutdownOrder parent -> STOPPED, Exit 0, , Known Sent: NONE
2019-03-08T01:16:39Z [INFO] Managed task [testShutdownOrder]: sent container change event [parent]: testShutdownOrder parent -> STOPPED, Exit 0, , Known Sent: NONE
2019-03-08T01:16:39Z [INFO] Task engine [testShutdownOrder]: stopping container [A]
2019-03-08T01:16:40Z [WARN] Managed task [testShutdownOrder]: failed to write container [A] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:40Z [INFO] Managed task [testShutdownOrder]: sending container change event [A]: testShutdownOrder A -> STOPPED, Exit 1073807364, , Known Sent: NONE
2019-03-08T01:16:40Z [INFO] Managed task [testShutdownOrder]: sent container change event [A]: testShutdownOrder A -> STOPPED, Exit 1073807364, , Known Sent: NONE
2019-03-08T01:16:40Z [INFO] Task engine [testShutdownOrder]: stopping container [B]
2019-03-08T01:16:40Z [INFO] Managed task [testShutdownOrder]: redundant container state change. A to STOPPED, but already STOPPED
2019-03-08T01:16:40Z [INFO] Managed task [testShutdownOrder]: redundant container state change. A to STOPPED, but already STOPPED
2019-03-08T01:16:40Z [WARN] Managed task [testShutdownOrder]: failed to write container [B] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:40Z [INFO] Managed task [testShutdownOrder]: sending container change event [B]: testShutdownOrder B -> STOPPED, Exit 1073807364, , Known Sent: NONE
2019-03-08T01:16:40Z [INFO] Managed task [testShutdownOrder]: sent container change event [B]: testShutdownOrder B -> STOPPED, Exit 1073807364, , Known Sent: NONE
2019-03-08T01:16:40Z [INFO] Task engine [testShutdownOrder]: stopping container [C]
2019-03-08T01:16:40Z [INFO] Managed task [testShutdownOrder]: redundant container state change. B to STOPPED, but already STOPPED
2019-03-08T01:16:40Z [INFO] Managed task [testShutdownOrder]: redundant container state change. B to STOPPED, but already STOPPED
2019-03-08T01:16:41Z [WARN] Managed task [testShutdownOrder]: failed to write container [C] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:41Z [INFO] Managed task [testShutdownOrder]: sending container change event [C]: testShutdownOrder C -> STOPPED, Exit 1073807364, , Known Sent: NONE
2019-03-08T01:16:41Z [INFO] Managed task [testShutdownOrder]: sent container change event [C]: testShutdownOrder C -> STOPPED, Exit 1073807364, , Known Sent: NONE
2019-03-08T01:16:41Z [INFO] Managed task [testShutdownOrder]: sending task change event [testShutdownOrder -> STOPPED, Known Sent: NONE, PullStartedAt: 0001-01-01 00:00:00 +0000 UTC, PullStoppedAt: 0001-01-01 00:00:00 +0000 UTC, ExecutionStoppedAt: 2019-03-08 01:16:39.9535716 +0000 GMT m=+688.132778001]
panic: test timed out after 35m0s
```
|
1.0
|
Flaky Integ Test - TestShutdownOrder hangs occasionally - <!--
For urgent operational issues, please contact AWS Support directly.
https://aws.amazon.com/premiumsupport/
Please provide the following information:
-->
### Summary
<!-- Please provide a brief outline of the issue -->
TestShutdownOrder hung occasionally. It doesn't look like we happen to reach timeout on this test from the total running time seen in logs.
### Description
<!-- Provide detailed information about this issue -->
<!-- Not required for feature requests -->
### Expected Behavior
Test passes in ~20s.
### Observed Behavior
Test hung.
### Environment Details
<!--
Examples:
* docker info
* curl http://localhost:51678/v1/metadata
* df -h
-->
### Supporting Log Snippets
<!--
Please have a look at https://github.com/awslabs/ecs-logs-collector
for the data we typically require for investigation
Please note that GitHub issues are public, remove sensitive data from logs before posting.
If you are not comfortable posting your logs here, please let us know and we
can provide an alternate method.
-->
```
=== RUN TestShutdownOrder
2019-03-08T01:16:19Z [INFO] Managed task [testDependencyHealthyTimeout]: redundant container state change. dependency to STOPPED, but already STOPPED
2019-03-08T01:16:19Z [INFO] Image excluded from cleanup: amazon/amazon-ecs-agent:latest
2019-03-08T01:16:19Z [INFO] Image excluded from cleanup: amazon/amazon-ecs-pause:0.1.0
2019-03-08T01:16:19Z [WARN] Unable to fetch user data: blackholed
2019-03-08T01:16:19Z [CRITICAL] Unable to communicate with EC2 Metadata service to infer region: blackholed
2019-03-08T01:16:19Z [CRITICAL] Configuration key not set, key: AWSRegion
2019-03-08T01:16:19Z [INFO] Unable to get Docker client for version 1.17: version detection using MinAPIVersion: unsupported version: 1.17
2019-03-08T01:16:19Z [INFO] Unable to get Docker client for version 1.18: version detection using MinAPIVersion: unsupported version: 1.18
2019-03-08T01:16:19Z [INFO] Unable to get Docker client for version 1.19: version detection using MinAPIVersion: unsupported version: 1.19
2019-03-08T01:16:19Z [INFO] Unable to get Docker client for version 1.20: version detection using MinAPIVersion: unsupported version: 1.20
2019-03-08T01:16:19Z [INFO] Unable to get Docker client for version 1.21: version detection using MinAPIVersion: unsupported version: 1.21
2019-03-08T01:16:19Z [INFO] Unable to get Docker client for version 1.22: version detection using MinAPIVersion: unsupported version: 1.22
2019-03-08T01:16:19Z [INFO] Unable to get Docker client for version 1.23: version detection using MinAPIVersion: unsupported version: 1.23
2019-03-08T01:16:19Z [INFO] Unable to get Docker client for version 1.31: version detection using MinAPIVersion: unsupported version: 1.31
2019-03-08T01:16:19Z [INFO] Unable to get Docker client for version 1.32: version detection using MinAPIVersion: unsupported version: 1.32
2019-03-08T01:16:19Z [INFO] Managed task [testShutdownOrder]: unable to create task state change event []: create task state change event api: status not recognized by ECS: NONE
2019-03-08T01:16:19Z [INFO] Task engine [testShutdownOrder]: found cached image microsoft/windowsservercore, use it directly for container C
2019-03-08T01:16:19Z [INFO] Adding image name- microsoft/windowsservercore to Image state- sha256:1fbef5019583cc35cbbe6a350b69f0b615fd2834d628ffeefef2f9f51e01a607
2019-03-08T01:16:19Z [INFO] Updating container reference C in Image State - sha256:1fbef5019583cc35cbbe6a350b69f0b615fd2834d628ffeefef2f9f51e01a607
2019-03-08T01:16:19Z [WARN] Managed task [testShutdownOrder]: failed to write container [C] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:19Z [INFO] Task engine [testShutdownOrder]: creating container: C
2019-03-08T01:16:19Z [WARN] Task testShutdownOrder container C memory setting is too low, increasing to 268435456 bytes
2019-03-08T01:16:19Z [INFO] Task engine [testShutdownOrder]: created container name mapping for task: C -> ecs-family-1-C-dcfcb2cf85f7d2c6a701
2019-03-08T01:16:19Z [INFO] Task engine [testShutdownOrder]: created docker container for task: C -> 7a52372dc0661a1b400113e33ddf2d3a6d2785ecf7edc04e86ae3f2d93c6e329
2019-03-08T01:16:19Z [INFO] Task engine [testShutdownOrder]: created docker container for task: C -> 7a52372dc0661a1b400113e33ddf2d3a6d2785ecf7edc04e86ae3f2d93c6e329, took 19.5202ms
2019-03-08T01:16:19Z [WARN] Managed task [testShutdownOrder]: failed to write container [C] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:19Z [INFO] Task engine [testShutdownOrder]: starting container: C
2019-03-08T01:16:23Z [INFO] Task engine [testShutdownOrder]: started docker container for task: C -> 7a52372dc0661a1b400113e33ddf2d3a6d2785ecf7edc04e86ae3f2d93c6e329, took 3.1258983s
2019-03-08T01:16:23Z [WARN] Managed task [testShutdownOrder]: failed to write container [C] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:23Z [INFO] Managed task [testShutdownOrder]: sending container change event [C]: testShutdownOrder C -> RUNNING, Known Sent: NONE
2019-03-08T01:16:23Z [INFO] Managed task [testShutdownOrder]: sent container change event [C]: testShutdownOrder C -> RUNNING, Known Sent: NONE
2019-03-08T01:16:23Z [INFO] Managed task [testShutdownOrder]: redundant container state change. C to RUNNING, but already RUNNING
2019-03-08T01:16:23Z [INFO] Task engine [testShutdownOrder]: found cached image microsoft/windowsservercore, use it directly for container B
2019-03-08T01:16:23Z [INFO] Updating container reference B in Image State - sha256:1fbef5019583cc35cbbe6a350b69f0b615fd2834d628ffeefef2f9f51e01a607
2019-03-08T01:16:23Z [WARN] Managed task [testShutdownOrder]: failed to write container [B] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:23Z [INFO] Task engine [testShutdownOrder]: creating container: B
2019-03-08T01:16:23Z [WARN] Task testShutdownOrder container B memory setting is too low, increasing to 268435456 bytes
2019-03-08T01:16:23Z [INFO] Task engine [testShutdownOrder]: created container name mapping for task: B -> ecs-family-1-B-fe8a908adaea8ec2b701
2019-03-08T01:16:23Z [INFO] Task engine [testShutdownOrder]: created docker container for task: B -> daf91503ac66de49629ff1463f57e74aa3f3d07f9819615189d76c1b7cef5c4b
2019-03-08T01:16:23Z [INFO] Task engine [testShutdownOrder]: created docker container for task: B -> daf91503ac66de49629ff1463f57e74aa3f3d07f9819615189d76c1b7cef5c4b, took 27.3455ms
2019-03-08T01:16:23Z [WARN] Managed task [testShutdownOrder]: failed to write container [B] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:23Z [INFO] Task engine [testShutdownOrder]: starting container: B
2019-03-08T01:16:25Z [INFO] Task engine [testShutdownOrder]: started docker container for task: B -> daf91503ac66de49629ff1463f57e74aa3f3d07f9819615189d76c1b7cef5c4b, took 1.9657666s
2019-03-08T01:16:25Z [WARN] Managed task [testShutdownOrder]: failed to write container [B] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:25Z [INFO] Managed task [testShutdownOrder]: sending container change event [B]: testShutdownOrder B -> RUNNING, Known Sent: NONE
2019-03-08T01:16:25Z [INFO] Managed task [testShutdownOrder]: sent container change event [B]: testShutdownOrder B -> RUNNING, Known Sent: NONE
2019-03-08T01:16:25Z [INFO] Managed task [testShutdownOrder]: redundant container state change. B to RUNNING, but already RUNNING
2019-03-08T01:16:25Z [INFO] Task engine [testShutdownOrder]: found cached image microsoft/windowsservercore, use it directly for container A
2019-03-08T01:16:25Z [INFO] Updating container reference A in Image State - sha256:1fbef5019583cc35cbbe6a350b69f0b615fd2834d628ffeefef2f9f51e01a607
2019-03-08T01:16:25Z [WARN] Managed task [testShutdownOrder]: failed to write container [A] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:25Z [INFO] Task engine [testShutdownOrder]: creating container: A
2019-03-08T01:16:25Z [WARN] Task testShutdownOrder container A memory setting is too low, increasing to 268435456 bytes
2019-03-08T01:16:25Z [INFO] Task engine [testShutdownOrder]: created container name mapping for task: A -> ecs-family-1-A-d2eebd8a90d7aae53900
2019-03-08T01:16:25Z [INFO] Task engine [testShutdownOrder]: created docker container for task: A -> a57081700e465e60ebbd3ef1bc3204deac1b505fcc0c2ef6b849cc8446d11d80
2019-03-08T01:16:25Z [INFO] Task engine [testShutdownOrder]: created docker container for task: A -> a57081700e465e60ebbd3ef1bc3204deac1b505fcc0c2ef6b849cc8446d11d80, took 33.2086ms
2019-03-08T01:16:25Z [WARN] Managed task [testShutdownOrder]: failed to write container [A] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:25Z [INFO] Task engine [testShutdownOrder]: starting container: A
2019-03-08T01:16:29Z [INFO] Task engine [testShutdownOrder]: started docker container for task: A -> a57081700e465e60ebbd3ef1bc3204deac1b505fcc0c2ef6b849cc8446d11d80, took 4.3983237s
2019-03-08T01:16:29Z [WARN] Managed task [testShutdownOrder]: failed to write container [A] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:29Z [INFO] Managed task [testShutdownOrder]: sending container change event [A]: testShutdownOrder A -> RUNNING, Known Sent: NONE
2019-03-08T01:16:29Z [INFO] Managed task [testShutdownOrder]: sent container change event [A]: testShutdownOrder A -> RUNNING, Known Sent: NONE
2019-03-08T01:16:29Z [INFO] Managed task [testShutdownOrder]: redundant container state change. A to RUNNING, but already RUNNING
2019-03-08T01:16:29Z [INFO] Task engine [testShutdownOrder]: found cached image microsoft/windowsservercore, use it directly for container parent
2019-03-08T01:16:29Z [INFO] Updating container reference parent in Image State - sha256:1fbef5019583cc35cbbe6a350b69f0b615fd2834d628ffeefef2f9f51e01a607
2019-03-08T01:16:29Z [WARN] Managed task [testShutdownOrder]: failed to write container [parent] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:29Z [INFO] Task engine [testShutdownOrder]: creating container: parent
2019-03-08T01:16:29Z [WARN] Task testShutdownOrder container parent memory setting is too low, increasing to 268435456 bytes
2019-03-08T01:16:29Z [INFO] Task engine [testShutdownOrder]: created container name mapping for task: parent -> ecs-family-1-parent-a0d1c1f9f9e3c498a801
2019-03-08T01:16:29Z [INFO] Task engine [testShutdownOrder]: created docker container for task: parent -> b8ed239e5294c9177f1be41642a24d069b63e4c9d5a81b1fc8b56158d6485947
2019-03-08T01:16:29Z [INFO] Task engine [testShutdownOrder]: created docker container for task: parent -> b8ed239e5294c9177f1be41642a24d069b63e4c9d5a81b1fc8b56158d6485947, took 22.4593ms
2019-03-08T01:16:29Z [WARN] Managed task [testShutdownOrder]: failed to write container [parent] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:29Z [INFO] Managed task [testShutdownOrder]: unable to create task state change event []: create task state change event api: status not recognized by ECS: CREATED
2019-03-08T01:16:29Z [INFO] Task engine [testShutdownOrder]: starting container: parent
2019-03-08T01:16:33Z [INFO] Task engine [testShutdownOrder]: started docker container for task: parent -> b8ed239e5294c9177f1be41642a24d069b63e4c9d5a81b1fc8b56158d6485947, took 4.0985045s
2019-03-08T01:16:33Z [WARN] Managed task [testShutdownOrder]: failed to write container [parent] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:33Z [INFO] Managed task [testShutdownOrder]: sending container change event [parent]: testShutdownOrder parent -> RUNNING, Known Sent: NONE
2019-03-08T01:16:33Z [INFO] Managed task [testShutdownOrder]: sent container change event [parent]: testShutdownOrder parent -> RUNNING, Known Sent: NONE
2019-03-08T01:16:33Z [INFO] Managed task [testShutdownOrder]: sending task change event [testShutdownOrder -> RUNNING, Known Sent: NONE, PullStartedAt: 0001-01-01 00:00:00 +0000 UTC, PullStoppedAt: 0001-01-01 00:00:00 +0000 UTC, ExecutionStoppedAt: 0001-01-01 00:00:00 +0000 UTC]
2019-03-08T01:16:33Z [INFO] Managed task [testShutdownOrder]: sent task change event [testShutdownOrder -> RUNNING, Known Sent: NONE, PullStartedAt: 0001-01-01 00:00:00 +0000 UTC, PullStoppedAt: 0001-01-01 00:00:00 +0000 UTC, ExecutionStoppedAt: 0001-01-01 00:00:00 +0000 UTC]
2019-03-08T01:16:33Z [INFO] Managed task [testShutdownOrder]: task at steady state: RUNNING
2019-03-08T01:16:33Z [INFO] Managed task [testShutdownOrder]: redundant container state change. parent to RUNNING, but already RUNNING
2019-03-08T01:16:33Z [INFO] Managed task [testShutdownOrder]: task at steady state: RUNNING
2019-03-08T01:16:39Z [INFO] Task [testShutdownOrder]: recording execution stopped time. Essential container [parent] stopped at: 2019-03-08 01:16:39.9535716 +0000 GMT m=+688.132778001
2019-03-08T01:16:39Z [WARN] Managed task [testShutdownOrder]: failed to write container [parent] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:39Z [INFO] Managed task [testShutdownOrder]: sending container change event [parent]: testShutdownOrder parent -> STOPPED, Exit 0, , Known Sent: NONE
2019-03-08T01:16:39Z [INFO] Managed task [testShutdownOrder]: sent container change event [parent]: testShutdownOrder parent -> STOPPED, Exit 0, , Known Sent: NONE
2019-03-08T01:16:39Z [INFO] Task engine [testShutdownOrder]: stopping container [A]
2019-03-08T01:16:40Z [WARN] Managed task [testShutdownOrder]: failed to write container [A] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:40Z [INFO] Managed task [testShutdownOrder]: sending container change event [A]: testShutdownOrder A -> STOPPED, Exit 1073807364, , Known Sent: NONE
2019-03-08T01:16:40Z [INFO] Managed task [testShutdownOrder]: sent container change event [A]: testShutdownOrder A -> STOPPED, Exit 1073807364, , Known Sent: NONE
2019-03-08T01:16:40Z [INFO] Task engine [testShutdownOrder]: stopping container [B]
2019-03-08T01:16:40Z [INFO] Managed task [testShutdownOrder]: redundant container state change. A to STOPPED, but already STOPPED
2019-03-08T01:16:40Z [INFO] Managed task [testShutdownOrder]: redundant container state change. A to STOPPED, but already STOPPED
2019-03-08T01:16:40Z [WARN] Managed task [testShutdownOrder]: failed to write container [B] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:40Z [INFO] Managed task [testShutdownOrder]: sending container change event [B]: testShutdownOrder B -> STOPPED, Exit 1073807364, , Known Sent: NONE
2019-03-08T01:16:40Z [INFO] Managed task [testShutdownOrder]: sent container change event [B]: testShutdownOrder B -> STOPPED, Exit 1073807364, , Known Sent: NONE
2019-03-08T01:16:40Z [INFO] Task engine [testShutdownOrder]: stopping container [C]
2019-03-08T01:16:40Z [INFO] Managed task [testShutdownOrder]: redundant container state change. B to STOPPED, but already STOPPED
2019-03-08T01:16:40Z [INFO] Managed task [testShutdownOrder]: redundant container state change. B to STOPPED, but already STOPPED
2019-03-08T01:16:41Z [WARN] Managed task [testShutdownOrder]: failed to write container [C] change event to tcs event stream: Event stream is closed
2019-03-08T01:16:41Z [INFO] Managed task [testShutdownOrder]: sending container change event [C]: testShutdownOrder C -> STOPPED, Exit 1073807364, , Known Sent: NONE
2019-03-08T01:16:41Z [INFO] Managed task [testShutdownOrder]: sent container change event [C]: testShutdownOrder C -> STOPPED, Exit 1073807364, , Known Sent: NONE
2019-03-08T01:16:41Z [INFO] Managed task [testShutdownOrder]: sending task change event [testShutdownOrder -> STOPPED, Known Sent: NONE, PullStartedAt: 0001-01-01 00:00:00 +0000 UTC, PullStoppedAt: 0001-01-01 00:00:00 +0000 UTC, ExecutionStoppedAt: 2019-03-08 01:16:39.9535716 +0000 GMT m=+688.132778001]
panic: test timed out after 35m0s
```
|
test
|
flaky integ test testshutdownorder hangs occasionally for urgent operational issues please contact aws support directly please provide the following information summary testshutdownorder hung occasionally it doesn t look like we happen to reach timeout on this test from the total running time seen in logs description expected behavior test passes in observed behavior test hung environment details examples docker info curl df h supporting log snippets please have a look at for the data we typically require for investigation please note that github issues are public remove sensitive data from logs before posting if you are not comfortable posting your logs here please let us know and we can provide an alternate method run testshutdownorder managed task redundant container state change dependency to stopped but already stopped image excluded from cleanup amazon amazon ecs agent latest image excluded from cleanup amazon amazon ecs pause unable to fetch user data blackholed unable to communicate with metadata service to infer region blackholed configuration key not set key awsregion unable to get docker client for version version detection using minapiversion unsupported version unable to get docker client for version version detection using minapiversion unsupported version unable to get docker client for version version detection using minapiversion unsupported version unable to get docker client for version version detection using minapiversion unsupported version unable to get docker client for version version detection using minapiversion unsupported version unable to get docker client for version version detection using minapiversion unsupported version unable to get docker client for version version detection using minapiversion unsupported version unable to get docker client for version version detection using minapiversion unsupported version unable to get docker client for version version detection using minapiversion unsupported version managed task unable to create task state change event create task state change event api status not recognized by ecs none task engine found cached image microsoft windowsservercore use it directly for container c adding image name microsoft windowsservercore to image state updating container reference c in image state managed task failed to write container change event to tcs event stream event stream is closed task engine creating container c task testshutdownorder container c memory setting is too low increasing to bytes task engine created container name mapping for task c ecs family c task engine created docker container for task c task engine created docker container for task c took managed task failed to write container change event to tcs event stream event stream is closed task engine starting container c task engine started docker container for task c took managed task failed to write container change event to tcs event stream event stream is closed managed task sending container change event testshutdownorder c running known sent none managed task sent container change event testshutdownorder c running known sent none managed task redundant container state change c to running but already running task engine found cached image microsoft windowsservercore use it directly for container b updating container reference b in image state managed task failed to write container change event to tcs event stream event stream is closed task engine creating container b task testshutdownorder container b memory setting is too low increasing to bytes task engine created container name mapping for task b ecs family b task engine created docker container for task b task engine created docker container for task b took managed task failed to write container change event to tcs event stream event stream is closed task engine starting container b task engine started docker container for task b took managed task failed to write container change event to tcs event stream event stream is closed managed task sending container change event testshutdownorder b running known sent none managed task sent container change event testshutdownorder b running known sent none managed task redundant container state change b to running but already running task engine found cached image microsoft windowsservercore use it directly for container a updating container reference a in image state managed task failed to write container change event to tcs event stream event stream is closed task engine creating container a task testshutdownorder container a memory setting is too low increasing to bytes task engine created container name mapping for task a ecs family a task engine created docker container for task a task engine created docker container for task a took managed task failed to write container change event to tcs event stream event stream is closed task engine starting container a task engine started docker container for task a took managed task failed to write container change event to tcs event stream event stream is closed managed task sending container change event testshutdownorder a running known sent none managed task sent container change event testshutdownorder a running known sent none managed task redundant container state change a to running but already running task engine found cached image microsoft windowsservercore use it directly for container parent updating container reference parent in image state managed task failed to write container change event to tcs event stream event stream is closed task engine creating container parent task testshutdownorder container parent memory setting is too low increasing to bytes task engine created container name mapping for task parent ecs family parent task engine created docker container for task parent task engine created docker container for task parent took managed task failed to write container change event to tcs event stream event stream is closed managed task unable to create task state change event create task state change event api status not recognized by ecs created task engine starting container parent task engine started docker container for task parent took managed task failed to write container change event to tcs event stream event stream is closed managed task sending container change event testshutdownorder parent running known sent none managed task sent container change event testshutdownorder parent running known sent none managed task sending task change event managed task sent task change event managed task task at steady state running managed task redundant container state change parent to running but already running managed task task at steady state running task recording execution stopped time essential container stopped at gmt m managed task failed to write container change event to tcs event stream event stream is closed managed task sending container change event testshutdownorder parent stopped exit known sent none managed task sent container change event testshutdownorder parent stopped exit known sent none task engine stopping container managed task failed to write container change event to tcs event stream event stream is closed managed task sending container change event testshutdownorder a stopped exit known sent none managed task sent container change event testshutdownorder a stopped exit known sent none task engine stopping container managed task redundant container state change a to stopped but already stopped managed task redundant container state change a to stopped but already stopped managed task failed to write container change event to tcs event stream event stream is closed managed task sending container change event testshutdownorder b stopped exit known sent none managed task sent container change event testshutdownorder b stopped exit known sent none task engine stopping container managed task redundant container state change b to stopped but already stopped managed task redundant container state change b to stopped but already stopped managed task failed to write container change event to tcs event stream event stream is closed managed task sending container change event testshutdownorder c stopped exit known sent none managed task sent container change event testshutdownorder c stopped exit known sent none managed task sending task change event panic test timed out after
| 1
|
50,961
| 6,137,240,897
|
IssuesEvent
|
2017-06-26 11:43:58
|
xcat2/xcat-core
|
https://api.github.com/repos/xcat2/xcat-core
|
opened
|
[fvt]x86_64 physical machine could not powering on
|
component:test
|
env:
1. x86_64 physical machine:
c910f04x18
[root@c910f04x30v02 ~]# lsdef c910f04x18
Object name: c910f04x18
arch=x86_64
bmc=10.4.18.254
cons=ipmi
currchain=boot
currstate=install rhels7.3-x86_64-compute
groups=ipmi
installnic=mac
ip=10.4.18.1
mac=40:F2:E9:0A:4E:C4
mgt=ipmi
monserver=c910f04x30v02
netboot=xnba
nfsserver=c910f04x30v02
os=rhels7.3
postbootscripts=otherpkgs
postscripts=syslog,remoteshell,syncfiles,setupntp
primarynic=mac
profile=compute
provmethod=rhels7.3-x86_64-install-compute
serialport=0
serialspeed=115200
status=powering-on
statustime=06-26-2017 07:39:21
tftpserver=c910f04x30v02
xcatmaster=c910f04x30v02
2.[root@c910f04x30v02 ~]# rpower c910f04x18 stat
c910f04x18: off
[root@c910f04x30v02 ~]# rpower c910f04x18 on
c910f04x18: on
[root@c910f04x30v02 ~]# rpower c910f04x18 stat
c910f04x18: off
--------------------> could not powering on and gongjie help to update the firmware but failed
|
1.0
|
[fvt]x86_64 physical machine could not powering on - env:
1. x86_64 physical machine:
c910f04x18
[root@c910f04x30v02 ~]# lsdef c910f04x18
Object name: c910f04x18
arch=x86_64
bmc=10.4.18.254
cons=ipmi
currchain=boot
currstate=install rhels7.3-x86_64-compute
groups=ipmi
installnic=mac
ip=10.4.18.1
mac=40:F2:E9:0A:4E:C4
mgt=ipmi
monserver=c910f04x30v02
netboot=xnba
nfsserver=c910f04x30v02
os=rhels7.3
postbootscripts=otherpkgs
postscripts=syslog,remoteshell,syncfiles,setupntp
primarynic=mac
profile=compute
provmethod=rhels7.3-x86_64-install-compute
serialport=0
serialspeed=115200
status=powering-on
statustime=06-26-2017 07:39:21
tftpserver=c910f04x30v02
xcatmaster=c910f04x30v02
2.[root@c910f04x30v02 ~]# rpower c910f04x18 stat
c910f04x18: off
[root@c910f04x30v02 ~]# rpower c910f04x18 on
c910f04x18: on
[root@c910f04x30v02 ~]# rpower c910f04x18 stat
c910f04x18: off
--------------------> could not powering on and gongjie help to update the firmware but failed
|
test
|
physical machine could not powering on env physical machine lsdef object name arch bmc cons ipmi currchain boot currstate install compute groups ipmi installnic mac ip mac mgt ipmi monserver netboot xnba nfsserver os postbootscripts otherpkgs postscripts syslog remoteshell syncfiles setupntp primarynic mac profile compute provmethod install compute serialport serialspeed status powering on statustime tftpserver xcatmaster rpower stat off rpower on on rpower stat off could not powering on and gongjie help to update the firmware but failed
| 1
|
687,618
| 23,533,548,877
|
IssuesEvent
|
2022-08-19 17:52:31
|
project-chip/zap
|
https://api.github.com/repos/project-chip/zap
|
opened
|
Cleanup zap/repo/src-electron/generator/matter/app/zap-templates/common
|
high priority MatterZapCleanup
|
This may go hand in hand with ZAP#680 but if you can separate it then well and good.
The goal is to eventually cleanup the matter specific zap code to not have any state for eg in ClustersHelper.js
During this cleanup we want to do the following:
- Go through the matter directory in this issue. See if these helpers can have code pushed to the backend sql queries.
- See if the helpers can use any of the existing helper logic and can remove code redundancy
- Add unit tests for each of the helpers listed
- Make sure to have a CHIP/Zigbee repo branch that points to your changes and passes the CI on both places
- Also if you can fix anything new apart from what is listed then fix those issues as well.
|
1.0
|
Cleanup zap/repo/src-electron/generator/matter/app/zap-templates/common - This may go hand in hand with ZAP#680 but if you can separate it then well and good.
The goal is to eventually cleanup the matter specific zap code to not have any state for eg in ClustersHelper.js
During this cleanup we want to do the following:
- Go through the matter directory in this issue. See if these helpers can have code pushed to the backend sql queries.
- See if the helpers can use any of the existing helper logic and can remove code redundancy
- Add unit tests for each of the helpers listed
- Make sure to have a CHIP/Zigbee repo branch that points to your changes and passes the CI on both places
- Also if you can fix anything new apart from what is listed then fix those issues as well.
|
non_test
|
cleanup zap repo src electron generator matter app zap templates common this may go hand in hand with zap but if you can separate it then well and good the goal is to eventually cleanup the matter specific zap code to not have any state for eg in clustershelper js during this cleanup we want to do the following go through the matter directory in this issue see if these helpers can have code pushed to the backend sql queries see if the helpers can use any of the existing helper logic and can remove code redundancy add unit tests for each of the helpers listed make sure to have a chip zigbee repo branch that points to your changes and passes the ci on both places also if you can fix anything new apart from what is listed then fix those issues as well
| 0
|
372,148
| 11,009,748,763
|
IssuesEvent
|
2019-12-04 13:19:19
|
ahmedkaludi/accelerated-mobile-pages
|
https://api.github.com/repos/ahmedkaludi/accelerated-mobile-pages
|
closed
|
Tooltip alignment is missing in Advertisement
|
NEXT UPDATE [Priority: HIGH] bug
|
Tooltip alignment is missing in AMP option panel ->Settings -> Advertisement -> Ad type
https://take.ms/VnMPo
Note: Please check all the Tooltip alignment in AMP option panel
|
1.0
|
Tooltip alignment is missing in Advertisement - Tooltip alignment is missing in AMP option panel ->Settings -> Advertisement -> Ad type
https://take.ms/VnMPo
Note: Please check all the Tooltip alignment in AMP option panel
|
non_test
|
tooltip alignment is missing in advertisement tooltip alignment is missing in amp option panel settings advertisement ad type note please check all the tooltip alignment in amp option panel
| 0
|
42,979
| 7,009,800,436
|
IssuesEvent
|
2017-12-19 20:32:59
|
aspnetboilerplate/aspnetboilerplate
|
https://api.github.com/repos/aspnetboilerplate/aspnetboilerplate
|
closed
|
Document ISmtpEmailSender and IEmailSender
|
documentation
|
Could you please document EmailSender functions and Configurations?!
|
1.0
|
Document ISmtpEmailSender and IEmailSender - Could you please document EmailSender functions and Configurations?!
|
non_test
|
document ismtpemailsender and iemailsender could you please document emailsender functions and configurations
| 0
|
352,001
| 32,040,419,599
|
IssuesEvent
|
2023-09-22 18:49:13
|
yugabyte/yugabyte-db
|
https://api.github.com/repos/yugabyte/yugabyte-db
|
closed
|
TestRpc.TestConnectionKeepalive fails frequently on mac only
|
kind/bug kind/failing-test area/docdb priority/medium
|
Jira Link: [DB-1386](https://yugabyte.atlassian.net/browse/DB-1386)
https://jenkins.dev.yugabyte.com/job/github-yugabyte-db-mac-master-clang-debug/lastCompletedBuild/testReport/junit/(root)/TestRpc/TestConnectionKeepalive/history/
on Mac
vs
https://jenkins.dev.yugabyte.com/job/github-yugabyte-db-centos-master-clang-debug/lastCompletedBuild/testReport/junit/(root)/TestRpc/TestConnectionKeepalive/history/
on Centos
It failed in 80 / 100 commits as reported by detective-gcp.dev.yugabyte.com/stability?num_commits=100 and it appears all of them are on Mac.
Previous issue #1649 fixed by Timur @ttyusupov
Ran this locally ybd debug --cxx-test rpc_rpc-test --gtest_filter TestRpc.TestConnectionKeepalive -n 1000 and it always succeeds.
|
1.0
|
TestRpc.TestConnectionKeepalive fails frequently on mac only - Jira Link: [DB-1386](https://yugabyte.atlassian.net/browse/DB-1386)
https://jenkins.dev.yugabyte.com/job/github-yugabyte-db-mac-master-clang-debug/lastCompletedBuild/testReport/junit/(root)/TestRpc/TestConnectionKeepalive/history/
on Mac
vs
https://jenkins.dev.yugabyte.com/job/github-yugabyte-db-centos-master-clang-debug/lastCompletedBuild/testReport/junit/(root)/TestRpc/TestConnectionKeepalive/history/
on Centos
It failed in 80 / 100 commits as reported by detective-gcp.dev.yugabyte.com/stability?num_commits=100 and it appears all of them are on Mac.
Previous issue #1649 fixed by Timur @ttyusupov
Ran this locally ybd debug --cxx-test rpc_rpc-test --gtest_filter TestRpc.TestConnectionKeepalive -n 1000 and it always succeeds.
|
test
|
testrpc testconnectionkeepalive fails frequently on mac only jira link on mac vs on centos it failed in commits as reported by detective gcp dev yugabyte com stability num commits and it appears all of them are on mac previous issue fixed by timur ttyusupov ran this locally ybd debug cxx test rpc rpc test gtest filter testrpc testconnectionkeepalive n and it always succeeds
| 1
|
39,864
| 8,695,338,301
|
IssuesEvent
|
2018-12-04 14:57:35
|
Yoast/wordpress-seo
|
https://api.github.com/repos/Yoast/wordpress-seo
|
closed
|
“Profile” custom post name
|
bug code-review support
|
<!-- Please use this template when creating an issue.
- Please check the boxes after you've created your issue.
- Please use the latest version of Yoast SEO.-->
* [x] I've read and understood the [contribution guidelines](https://github.com/Yoast/wordpress-seo/blob/trunk/.github/CONTRIBUTING.md).
* [x] I've searched for any related issues and avoided creating a duplicate issue.
### Please give us a description of what happened.
When I use the "profile" slug for a custom post, the post doesn't appear in the Yoast SEO > Search Appearance > Content Types
Further discussion here:
https://wordpress.org/support/topic/profile-custom-post-and-yoast/
### Technical info
* WordPress version: 4.9.8
* Yoast SEO version: 9.1
<!-- You can check these boxes once you've created the issue. -->
<!-- You can check these boxes once you've created the issue. -->
* Which browser is affected (or browsers):
- [ ] IE11
- [x] Edge
- [ ] Chrome
- [x] Firefox
- [ ] Safari
* Relevant plugins in case of a bug: Toolset Types (for creating custom posts; ver. 3.1.2)
<!-- Please make sure you can reproduce this bug with a default theme such as Twenty Seventeen. Sometimes issues may occur due to theme conflicts. -->
* Tested with theme: Twenty Seventeen, GeneratePress (ver. 2.1.4)
|
1.0
|
“Profile” custom post name - <!-- Please use this template when creating an issue.
- Please check the boxes after you've created your issue.
- Please use the latest version of Yoast SEO.-->
* [x] I've read and understood the [contribution guidelines](https://github.com/Yoast/wordpress-seo/blob/trunk/.github/CONTRIBUTING.md).
* [x] I've searched for any related issues and avoided creating a duplicate issue.
### Please give us a description of what happened.
When I use the "profile" slug for a custom post, the post doesn't appear in the Yoast SEO > Search Appearance > Content Types
Further discussion here:
https://wordpress.org/support/topic/profile-custom-post-and-yoast/
### Technical info
* WordPress version: 4.9.8
* Yoast SEO version: 9.1
<!-- You can check these boxes once you've created the issue. -->
<!-- You can check these boxes once you've created the issue. -->
* Which browser is affected (or browsers):
- [ ] IE11
- [x] Edge
- [ ] Chrome
- [x] Firefox
- [ ] Safari
* Relevant plugins in case of a bug: Toolset Types (for creating custom posts; ver. 3.1.2)
<!-- Please make sure you can reproduce this bug with a default theme such as Twenty Seventeen. Sometimes issues may occur due to theme conflicts. -->
* Tested with theme: Twenty Seventeen, GeneratePress (ver. 2.1.4)
|
non_test
|
“profile” custom post name please use this template when creating an issue please check the boxes after you ve created your issue please use the latest version of yoast seo i ve read and understood the i ve searched for any related issues and avoided creating a duplicate issue please give us a description of what happened when i use the profile slug for a custom post the post doesn t appear in the yoast seo search appearance content types further discussion here technical info wordpress version yoast seo version which browser is affected or browsers edge chrome firefox safari relevant plugins in case of a bug toolset types for creating custom posts ver tested with theme twenty seventeen generatepress ver
| 0
|
239,056
| 19,807,226,758
|
IssuesEvent
|
2022-01-19 08:23:55
|
elisebeall/spacecase
|
https://api.github.com/repos/elisebeall/spacecase
|
closed
|
[🧑💻] Testing : Main Page User Flow : Search
|
testing
|
😊 As a user, I should be able to search the spacecraft that is displayed, so that I can find the one about which I want to view details.
☹️ As a user, I should be told when there are no search results that match my query.
|
1.0
|
[🧑💻] Testing : Main Page User Flow : Search - 😊 As a user, I should be able to search the spacecraft that is displayed, so that I can find the one about which I want to view details.
☹️ As a user, I should be told when there are no search results that match my query.
|
test
|
testing main page user flow search 😊 as a user i should be able to search the spacecraft that is displayed so that i can find the one about which i want to view details ☹️ as a user i should be told when there are no search results that match my query
| 1
|
34,565
| 9,415,197,537
|
IssuesEvent
|
2019-04-10 12:05:05
|
jOOQ/jOOQ
|
https://api.github.com/repos/jOOQ/jOOQ
|
opened
|
Add a parent pom.xml for all examples
|
C: Build C: Documentation E: All Editions P: Medium T: Enhancement
|
A lot of examples share some plugins / dependencies. Re-defining them in each example creates too much noise. We should have a parent pom.xml for these examples instead.
|
1.0
|
Add a parent pom.xml for all examples - A lot of examples share some plugins / dependencies. Re-defining them in each example creates too much noise. We should have a parent pom.xml for these examples instead.
|
non_test
|
add a parent pom xml for all examples a lot of examples share some plugins dependencies re defining them in each example creates too much noise we should have a parent pom xml for these examples instead
| 0
|
325,720
| 27,957,589,577
|
IssuesEvent
|
2023-03-24 13:31:07
|
opeolluwa/racoon
|
https://api.github.com/repos/opeolluwa/racoon
|
closed
|
Write a test for an helper function
|
enhancement good first issue test easy
|
[`set_jwt_exp()`](https://github.com/opeolluwa/racoon/blob/master/src/utils/jwt.rs#L154) is an utility function that accepts time in minutes as an argument and converts the parameter to milliseconds.
It finally adds the converted parameter to the current UNIX epoch timestamp, and, finally return the summation.
1. Move the [test(s) module](https://github.com/opeolluwa/racoon/blob/master/src/utils/jwt.rs#L54) available in the file to the base of the file.
2. Write a test to validate the workings of the `set_jwt_exp` function
|
1.0
|
Write a test for an helper function - [`set_jwt_exp()`](https://github.com/opeolluwa/racoon/blob/master/src/utils/jwt.rs#L154) is an utility function that accepts time in minutes as an argument and converts the parameter to milliseconds.
It finally adds the converted parameter to the current UNIX epoch timestamp, and, finally return the summation.
1. Move the [test(s) module](https://github.com/opeolluwa/racoon/blob/master/src/utils/jwt.rs#L54) available in the file to the base of the file.
2. Write a test to validate the workings of the `set_jwt_exp` function
|
test
|
write a test for an helper function is an utility function that accepts time in minutes as an argument and converts the parameter to milliseconds it finally adds the converted parameter to the current unix epoch timestamp and finally return the summation move the available in the file to the base of the file write a test to validate the workings of the set jwt exp function
| 1
|
110,460
| 16,979,916,151
|
IssuesEvent
|
2021-06-30 07:29:51
|
SmartBear/ready-mqtt-plugin
|
https://api.github.com/repos/SmartBear/ready-mqtt-plugin
|
closed
|
CVE-2020-26258 (High) detected in xstream-1.4.12.jar - autoclosed
|
security vulnerability
|
## CVE-2020-26258 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xstream-1.4.12.jar</b></p></summary>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Library home page: <a href="http://x-stream.github.io">http://x-stream.github.io</a></p>
<p>Path to dependency file: ready-mqtt-plugin/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.12/xstream-1.4.12.jar</p>
<p>
Dependency Hierarchy:
- ready-api-soapui-pro-3.3.1.jar (Root Library)
- ready-api-soapui-3.3.1.jar
- :x: **xstream-1.4.12.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/SmartBear/ready-mqtt-plugin/commit/72456065a443f2258660fde64bebd87fcbc170bb">72456065a443f2258660fde64bebd87fcbc170bb</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.15, a Server-Side Forgery Request vulnerability can be activated when unmarshalling. The vulnerability may allow a remote attacker to request data from internal resources that are not publicly available only by manipulating the processed input stream. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.15. The reported vulnerability does not exist if running Java 15 or higher. No user is affected who followed the recommendation to setup XStream's Security Framework with a whitelist! Anyone relying on XStream's default blacklist can immediately switch to a whilelist for the allowed types to avoid the vulnerability. Users of XStream 1.4.14 or below who still want to use XStream default blacklist can use a workaround described in more detailed in the referenced advisories.
<p>Publish Date: 2020-12-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-26258>CVE-2020-26258</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.7</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-4cch-wxpw-8p28">https://github.com/x-stream/xstream/security/advisories/GHSA-4cch-wxpw-8p28</a></p>
<p>Release Date: 2020-12-16</p>
<p>Fix Resolution: com.thoughtworks.xstream:xstream:1.4.15</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"com.thoughtworks.xstream","packageName":"xstream","packageVersion":"1.4.12","packageFilePaths":["/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"com.smartbear:ready-api-soapui-pro:3.3.1;com.smartbear:ready-api-soapui:3.3.1;com.thoughtworks.xstream:xstream:1.4.12","isMinimumFixVersionAvailable":true,"minimumFixVersion":"com.thoughtworks.xstream:xstream:1.4.15"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-26258","vulnerabilityDetails":"XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.15, a Server-Side Forgery Request vulnerability can be activated when unmarshalling. The vulnerability may allow a remote attacker to request data from internal resources that are not publicly available only by manipulating the processed input stream. If you rely on XStream\u0027s default blacklist of the Security Framework, you will have to use at least version 1.4.15. The reported vulnerability does not exist if running Java 15 or higher. No user is affected who followed the recommendation to setup XStream\u0027s Security Framework with a whitelist! Anyone relying on XStream\u0027s default blacklist can immediately switch to a whilelist for the allowed types to avoid the vulnerability. Users of XStream 1.4.14 or below who still want to use XStream default blacklist can use a workaround described in more detailed in the referenced advisories.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-26258","cvss3Severity":"high","cvss3Score":"7.7","cvss3Metrics":{"A":"None","AC":"Low","PR":"Low","S":"Changed","C":"High","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> -->
|
True
|
CVE-2020-26258 (High) detected in xstream-1.4.12.jar - autoclosed - ## CVE-2020-26258 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xstream-1.4.12.jar</b></p></summary>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Library home page: <a href="http://x-stream.github.io">http://x-stream.github.io</a></p>
<p>Path to dependency file: ready-mqtt-plugin/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.12/xstream-1.4.12.jar</p>
<p>
Dependency Hierarchy:
- ready-api-soapui-pro-3.3.1.jar (Root Library)
- ready-api-soapui-3.3.1.jar
- :x: **xstream-1.4.12.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/SmartBear/ready-mqtt-plugin/commit/72456065a443f2258660fde64bebd87fcbc170bb">72456065a443f2258660fde64bebd87fcbc170bb</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.15, a Server-Side Forgery Request vulnerability can be activated when unmarshalling. The vulnerability may allow a remote attacker to request data from internal resources that are not publicly available only by manipulating the processed input stream. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.15. The reported vulnerability does not exist if running Java 15 or higher. No user is affected who followed the recommendation to setup XStream's Security Framework with a whitelist! Anyone relying on XStream's default blacklist can immediately switch to a whilelist for the allowed types to avoid the vulnerability. Users of XStream 1.4.14 or below who still want to use XStream default blacklist can use a workaround described in more detailed in the referenced advisories.
<p>Publish Date: 2020-12-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-26258>CVE-2020-26258</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.7</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-4cch-wxpw-8p28">https://github.com/x-stream/xstream/security/advisories/GHSA-4cch-wxpw-8p28</a></p>
<p>Release Date: 2020-12-16</p>
<p>Fix Resolution: com.thoughtworks.xstream:xstream:1.4.15</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"com.thoughtworks.xstream","packageName":"xstream","packageVersion":"1.4.12","packageFilePaths":["/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"com.smartbear:ready-api-soapui-pro:3.3.1;com.smartbear:ready-api-soapui:3.3.1;com.thoughtworks.xstream:xstream:1.4.12","isMinimumFixVersionAvailable":true,"minimumFixVersion":"com.thoughtworks.xstream:xstream:1.4.15"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-26258","vulnerabilityDetails":"XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.15, a Server-Side Forgery Request vulnerability can be activated when unmarshalling. The vulnerability may allow a remote attacker to request data from internal resources that are not publicly available only by manipulating the processed input stream. If you rely on XStream\u0027s default blacklist of the Security Framework, you will have to use at least version 1.4.15. The reported vulnerability does not exist if running Java 15 or higher. No user is affected who followed the recommendation to setup XStream\u0027s Security Framework with a whitelist! Anyone relying on XStream\u0027s default blacklist can immediately switch to a whilelist for the allowed types to avoid the vulnerability. Users of XStream 1.4.14 or below who still want to use XStream default blacklist can use a workaround described in more detailed in the referenced advisories.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-26258","cvss3Severity":"high","cvss3Score":"7.7","cvss3Metrics":{"A":"None","AC":"Low","PR":"Low","S":"Changed","C":"High","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> -->
|
non_test
|
cve high detected in xstream jar autoclosed cve high severity vulnerability vulnerable library xstream jar xstream is a serialization library from java objects to xml and back library home page a href path to dependency file ready mqtt plugin pom xml path to vulnerable library home wss scanner repository com thoughtworks xstream xstream xstream jar dependency hierarchy ready api soapui pro jar root library ready api soapui jar x xstream jar vulnerable library found in head commit a href found in base branch master vulnerability details xstream is a java library to serialize objects to xml and back again in xstream before version a server side forgery request vulnerability can be activated when unmarshalling the vulnerability may allow a remote attacker to request data from internal resources that are not publicly available only by manipulating the processed input stream if you rely on xstream s default blacklist of the security framework you will have to use at least version the reported vulnerability does not exist if running java or higher no user is affected who followed the recommendation to setup xstream s security framework with a whitelist anyone relying on xstream s default blacklist can immediately switch to a whilelist for the allowed types to avoid the vulnerability users of xstream or below who still want to use xstream default blacklist can use a workaround described in more detailed in the referenced advisories publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope changed impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution com thoughtworks xstream xstream isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree com smartbear ready api soapui pro com smartbear ready api soapui com thoughtworks xstream xstream isminimumfixversionavailable true minimumfixversion com thoughtworks xstream xstream basebranches vulnerabilityidentifier cve vulnerabilitydetails xstream is a java library to serialize objects to xml and back again in xstream before version a server side forgery request vulnerability can be activated when unmarshalling the vulnerability may allow a remote attacker to request data from internal resources that are not publicly available only by manipulating the processed input stream if you rely on xstream default blacklist of the security framework you will have to use at least version the reported vulnerability does not exist if running java or higher no user is affected who followed the recommendation to setup xstream security framework with a whitelist anyone relying on xstream default blacklist can immediately switch to a whilelist for the allowed types to avoid the vulnerability users of xstream or below who still want to use xstream default blacklist can use a workaround described in more detailed in the referenced advisories vulnerabilityurl
| 0
|
144,861
| 11,634,247,706
|
IssuesEvent
|
2020-02-28 10:00:05
|
threefoldtech/home
|
https://api.github.com/repos/threefoldtech/home
|
closed
|
TECHNICAL: 29 word wallet seeds should be converted.
|
retested type_story
|
# What
Some early TFT buyers have 29 word phrases, we should see what we can do to ensure this doesn't break, and convert them to 24 word phrases.
# How
To be decided by R&D team.
# Extra
See following links.
1) https://github.com/threefoldfoundation/tft-stellar/blob/master/specs/conversion/locking.md#distinction-between-locked-and-unlocked-addresses
2) https://github.com/threefoldfoundation/tft-stellar/blob/master/specs/conversion/addressdistinction.md
|
1.0
|
TECHNICAL: 29 word wallet seeds should be converted. - # What
Some early TFT buyers have 29 word phrases, we should see what we can do to ensure this doesn't break, and convert them to 24 word phrases.
# How
To be decided by R&D team.
# Extra
See following links.
1) https://github.com/threefoldfoundation/tft-stellar/blob/master/specs/conversion/locking.md#distinction-between-locked-and-unlocked-addresses
2) https://github.com/threefoldfoundation/tft-stellar/blob/master/specs/conversion/addressdistinction.md
|
test
|
technical word wallet seeds should be converted what some early tft buyers have word phrases we should see what we can do to ensure this doesn t break and convert them to word phrases how to be decided by r d team extra see following links
| 1
|
296,930
| 25,584,857,675
|
IssuesEvent
|
2022-12-01 08:31:48
|
gama-platform/gama
|
https://api.github.com/repos/gama-platform/gama
|
closed
|
The "reload" experiment from "Create Simulation from file.gaml" library model file raises ConversionException
|
😱 Bug About Models Library 👍 Fix to be tested
|
**Describe the bug**
When trying to load the `saveSimu.gsim` file in the `reload` experiment from `Create Simulation from file.gaml`, a ConversionException is raised.
**To Reproduce**
Steps to reproduce the behavior:
1. Open `Create Simulation from file.gaml` in gama
2. run the `saveSimu` experiment until it reaches 5 steps and saves the simulation
3. run the `reloadSimu` experiment
4. See error
```
1 occurence in reloadSimu0 at cycle 0: Java error: ConversionException
in create simulation from: file<int, string>('saveSimu.gsim') ;
ConversionException:
---- Debugging information ----
cause-exception : java.lang.ClassCastException
cause-message : class ummisco.gama.serializer.gamaType.reference.ReferenceToAgent cannot be cast to class msi.gama.metamodel.agent.IAgent (ummisco.gama.serializer.gamaType.reference.ReferenceToAgent is in unnamed module of loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @7a4ae153; msi.gama.metamodel.agent.IAgent is in unnamed module of loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @155d65a)
class : ummisco.gama.serializer.gamaType.reference.ReferenceAgent
required-type : ummisco.gama.serializer.gamaType.reference.ReferenceAgent
converter-type : ummisco.gama.serializer.gamaType.converters.ReferenceAgentConverter
path : /msi.gama.metamodel.agent.SavedAgent/variables/data/msi.gama.util.GamaMap/valuesMapReducer/entry/msi.gama.metamodel.agent.MinimalAgent/agentReference
class[1] : msi.gama.metamodel.agent.MinimalAgent
required-type[1] : msi.gama.metamodel.agent.MinimalAgent
converter-type[1] : ummisco.gama.serializer.gamaType.converters.GamaAgentConverter
path[1] : /msi.gama.metamodel.agent.SavedAgent/variables/data/msi.gama.util.GamaMap/valuesMapReducer/entry/msi.gama.metamodel.agent.MinimalAgent
class[2] : java.util.LinkedHashMap
required-type[2] : java.util.LinkedHashMap
converter-type[2] : com.thoughtworks.xstream.converters.collections.MapConverter
class[3] : ummisco.gama.serializer.gamaType.reduced.GamaMapReducer
required-type[3] : ummisco.gama.serializer.gamaType.reduced.GamaMapReducer
converter-type[3] : com.thoughtworks.xstream.converters.reflection.ReflectionConverter
class[4] : msi.gama.util.GamaMap
required-type[4] : msi.gama.util.GamaMap
converter-type[4] : ummisco.gama.serializer.gamaType.converters.GamaMapConverter
class[5] : java.util.ArrayList
required-type[5] : java.util.ArrayList
converter-type[5] : com.thoughtworks.xstream.converters.collections.CollectionConverter
class[6] : msi.gama.metamodel.agent.SavedAgent
required-type[6] : msi.gama.metamodel.agent.SavedAgent
converter-type[6] : ummisco.gama.serializer.gamaType.converters.SavedAgentConverter
version : 1.4.18
-------------------------------
com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:77)
com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:72)
com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)
com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50)
ummisco.gama.serializer.gamaType.converters.GamaAgentConverter.read(GamaAgentConverter.java:59)
ummisco.gama.serializer.gamaType.converters.GamaAgentConverter.read(GamaAgentConverter.java:1)
ummisco.gama.serializer.gamaType.converters.IGamaConverter.unmarshal(IGamaConverter.java:45)
in agent reloadSimu0
```
**Expected behavior**
The simulation is loaded without any exception
|
1.0
|
The "reload" experiment from "Create Simulation from file.gaml" library model file raises ConversionException - **Describe the bug**
When trying to load the `saveSimu.gsim` file in the `reload` experiment from `Create Simulation from file.gaml`, a ConversionException is raised.
**To Reproduce**
Steps to reproduce the behavior:
1. Open `Create Simulation from file.gaml` in gama
2. run the `saveSimu` experiment until it reaches 5 steps and saves the simulation
3. run the `reloadSimu` experiment
4. See error
```
1 occurence in reloadSimu0 at cycle 0: Java error: ConversionException
in create simulation from: file<int, string>('saveSimu.gsim') ;
ConversionException:
---- Debugging information ----
cause-exception : java.lang.ClassCastException
cause-message : class ummisco.gama.serializer.gamaType.reference.ReferenceToAgent cannot be cast to class msi.gama.metamodel.agent.IAgent (ummisco.gama.serializer.gamaType.reference.ReferenceToAgent is in unnamed module of loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @7a4ae153; msi.gama.metamodel.agent.IAgent is in unnamed module of loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @155d65a)
class : ummisco.gama.serializer.gamaType.reference.ReferenceAgent
required-type : ummisco.gama.serializer.gamaType.reference.ReferenceAgent
converter-type : ummisco.gama.serializer.gamaType.converters.ReferenceAgentConverter
path : /msi.gama.metamodel.agent.SavedAgent/variables/data/msi.gama.util.GamaMap/valuesMapReducer/entry/msi.gama.metamodel.agent.MinimalAgent/agentReference
class[1] : msi.gama.metamodel.agent.MinimalAgent
required-type[1] : msi.gama.metamodel.agent.MinimalAgent
converter-type[1] : ummisco.gama.serializer.gamaType.converters.GamaAgentConverter
path[1] : /msi.gama.metamodel.agent.SavedAgent/variables/data/msi.gama.util.GamaMap/valuesMapReducer/entry/msi.gama.metamodel.agent.MinimalAgent
class[2] : java.util.LinkedHashMap
required-type[2] : java.util.LinkedHashMap
converter-type[2] : com.thoughtworks.xstream.converters.collections.MapConverter
class[3] : ummisco.gama.serializer.gamaType.reduced.GamaMapReducer
required-type[3] : ummisco.gama.serializer.gamaType.reduced.GamaMapReducer
converter-type[3] : com.thoughtworks.xstream.converters.reflection.ReflectionConverter
class[4] : msi.gama.util.GamaMap
required-type[4] : msi.gama.util.GamaMap
converter-type[4] : ummisco.gama.serializer.gamaType.converters.GamaMapConverter
class[5] : java.util.ArrayList
required-type[5] : java.util.ArrayList
converter-type[5] : com.thoughtworks.xstream.converters.collections.CollectionConverter
class[6] : msi.gama.metamodel.agent.SavedAgent
required-type[6] : msi.gama.metamodel.agent.SavedAgent
converter-type[6] : ummisco.gama.serializer.gamaType.converters.SavedAgentConverter
version : 1.4.18
-------------------------------
com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:77)
com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:72)
com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)
com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50)
ummisco.gama.serializer.gamaType.converters.GamaAgentConverter.read(GamaAgentConverter.java:59)
ummisco.gama.serializer.gamaType.converters.GamaAgentConverter.read(GamaAgentConverter.java:1)
ummisco.gama.serializer.gamaType.converters.IGamaConverter.unmarshal(IGamaConverter.java:45)
in agent reloadSimu0
```
**Expected behavior**
The simulation is loaded without any exception
|
test
|
the reload experiment from create simulation from file gaml library model file raises conversionexception describe the bug when trying to load the savesimu gsim file in the reload experiment from create simulation from file gaml a conversionexception is raised to reproduce steps to reproduce the behavior open create simulation from file gaml in gama run the savesimu experiment until it reaches steps and saves the simulation run the reloadsimu experiment see error occurence in at cycle java error conversionexception in create simulation from file savesimu gsim conversionexception debugging information cause exception java lang classcastexception cause message class ummisco gama serializer gamatype reference referencetoagent cannot be cast to class msi gama metamodel agent iagent ummisco gama serializer gamatype reference referencetoagent is in unnamed module of loader org eclipse osgi internal loader equinoxclassloader msi gama metamodel agent iagent is in unnamed module of loader org eclipse osgi internal loader equinoxclassloader class ummisco gama serializer gamatype reference referenceagent required type ummisco gama serializer gamatype reference referenceagent converter type ummisco gama serializer gamatype converters referenceagentconverter path msi gama metamodel agent savedagent variables data msi gama util gamamap valuesmapreducer entry msi gama metamodel agent minimalagent agentreference class msi gama metamodel agent minimalagent required type msi gama metamodel agent minimalagent converter type ummisco gama serializer gamatype converters gamaagentconverter path msi gama metamodel agent savedagent variables data msi gama util gamamap valuesmapreducer entry msi gama metamodel agent minimalagent class java util linkedhashmap required type java util linkedhashmap converter type com thoughtworks xstream converters collections mapconverter class ummisco gama serializer gamatype reduced gamamapreducer required type ummisco gama serializer gamatype reduced gamamapreducer converter type com thoughtworks xstream converters reflection reflectionconverter class msi gama util gamamap required type msi gama util gamamap converter type ummisco gama serializer gamatype converters gamamapconverter class java util arraylist required type java util arraylist converter type com thoughtworks xstream converters collections collectionconverter class msi gama metamodel agent savedagent required type msi gama metamodel agent savedagent converter type ummisco gama serializer gamatype converters savedagentconverter version com thoughtworks xstream core treeunmarshaller convert treeunmarshaller java com thoughtworks xstream core abstractreferenceunmarshaller convert abstractreferenceunmarshaller java com thoughtworks xstream core treeunmarshaller convertanother treeunmarshaller java com thoughtworks xstream core treeunmarshaller convertanother treeunmarshaller java ummisco gama serializer gamatype converters gamaagentconverter read gamaagentconverter java ummisco gama serializer gamatype converters gamaagentconverter read gamaagentconverter java ummisco gama serializer gamatype converters igamaconverter unmarshal igamaconverter java in agent expected behavior the simulation is loaded without any exception
| 1
|
219,674
| 7,344,888,087
|
IssuesEvent
|
2018-03-07 15:53:26
|
ParabolInc/action
|
https://api.github.com/repos/ParabolInc/action
|
closed
|
When user accepts expired invitation, gets ducks forever
|
bug help wanted low priority
|
## Issue - Bug
When a user accepts an expired invitation, they see an error toast telling them the invitation has expired, but also get ducks forever. We should redirect them to `/me` or to the welcome wizard (if they don't belong to a team yet).
Reproduction steps:
1) Open two browser windows, log into each as a different user
2) From the first browser, invite a third, _new_ user by email address
3) "MIstakenly" accept that invitation by using the link in the second browser window
4) Log out of Parabol in the second browser window
5) In the second browser window, attempt to use the invitation link and create a new user when prompted to do so
6) Observe toast and duckies
|
1.0
|
When user accepts expired invitation, gets ducks forever - ## Issue - Bug
When a user accepts an expired invitation, they see an error toast telling them the invitation has expired, but also get ducks forever. We should redirect them to `/me` or to the welcome wizard (if they don't belong to a team yet).
Reproduction steps:
1) Open two browser windows, log into each as a different user
2) From the first browser, invite a third, _new_ user by email address
3) "MIstakenly" accept that invitation by using the link in the second browser window
4) Log out of Parabol in the second browser window
5) In the second browser window, attempt to use the invitation link and create a new user when prompted to do so
6) Observe toast and duckies
|
non_test
|
when user accepts expired invitation gets ducks forever issue bug when a user accepts an expired invitation they see an error toast telling them the invitation has expired but also get ducks forever we should redirect them to me or to the welcome wizard if they don t belong to a team yet reproduction steps open two browser windows log into each as a different user from the first browser invite a third new user by email address mistakenly accept that invitation by using the link in the second browser window log out of parabol in the second browser window in the second browser window attempt to use the invitation link and create a new user when prompted to do so observe toast and duckies
| 0
|
141,942
| 11,448,221,120
|
IssuesEvent
|
2020-02-06 02:33:15
|
djyoon956/OWL
|
https://api.github.com/repos/djyoon956/OWL
|
reopened
|
[프로젝트] 테스트
|
test 최종
|
- [x] 프로젝트 생성후 모달창 reset 안됨 - @Lee-JeongEun23
- [x] ~~프로젝트는 삭제가 안됨~~ - @Lee-JeongEun23
- [x] 프로젝트 종료일 전에는 PM 탈퇴 불가 - @Lee-JeongEun23
- [x] ~~팀원이 프로젝트 색상을 바꾸면 모두 바뀌지 않음~~ - @Lee-JeongEun23
|
1.0
|
[프로젝트] 테스트 - - [x] 프로젝트 생성후 모달창 reset 안됨 - @Lee-JeongEun23
- [x] ~~프로젝트는 삭제가 안됨~~ - @Lee-JeongEun23
- [x] 프로젝트 종료일 전에는 PM 탈퇴 불가 - @Lee-JeongEun23
- [x] ~~팀원이 프로젝트 색상을 바꾸면 모두 바뀌지 않음~~ - @Lee-JeongEun23
|
test
|
테스트 프로젝트 생성후 모달창 reset 안됨 lee 프로젝트는 삭제가 안됨 lee 프로젝트 종료일 전에는 pm 탈퇴 불가 lee 팀원이 프로젝트 색상을 바꾸면 모두 바뀌지 않음 lee
| 1
|
253,086
| 21,650,594,967
|
IssuesEvent
|
2022-05-06 08:57:05
|
mozilla-mobile/fenix
|
https://api.github.com/repos/mozilla-mobile/fenix
|
opened
|
Intermittent UI test failure - < StartupExcessiveResourceUseTest. verifyRunBlockingAndStrictModeSuppresionCount >
|
eng:intermittent-test
|
### Firebase Test Run: [Firebase link](https://console.firebase.google.com/u/0/project/moz-fenix/testlab/histories/bh.66b7091e15d53d45/matrices/9187259850505635139/executions/bs.3fb2773f55808a1e/testcases/1/test-cases)
### Stacktrace:
java.lang.AssertionError: ConstraintLayout being a common direct descendant of a RecyclerView count does not match expected count.
If this PR removed a ConstraintLayout being a common direct descendant of a RecyclerView call, great! Please decrease the count.
Did this PR add or call code that increases the ConstraintLayout being a common direct descendant of a RecyclerView count?
Did you know that ConstraintLayouts are slow to inflate and are primarily used to flatten deep view hierarchies so can be under-performant as a common RecyclerView child?
Please do your best to implement a solution without adding ConstraintLayout being a common direct descendant of a RecyclerView calls.
Please consult the perf team if you have questions or believe that having this call
is the optimal solution.
Please note that we're not sure if this is a useful metric to assert: with your feedback, we'll find out over time if it is or is not. expected:<4> but was:<5>
at org.junit.Assert.fail(Assert.java:89)
at org.junit.Assert.failNotEquals(Assert.java:835)
at org.junit.Assert.assertEquals(Assert.java:120)
at org.mozilla.fenix.perf.StartupExcessiveResourceUseTest.verifyRunBlockingAndStrictModeSuppresionCount(StartupExcessiveResourceUseTest.kt:90)
### Build: 5/6 Main
|
1.0
|
Intermittent UI test failure - < StartupExcessiveResourceUseTest. verifyRunBlockingAndStrictModeSuppresionCount > - ### Firebase Test Run: [Firebase link](https://console.firebase.google.com/u/0/project/moz-fenix/testlab/histories/bh.66b7091e15d53d45/matrices/9187259850505635139/executions/bs.3fb2773f55808a1e/testcases/1/test-cases)
### Stacktrace:
java.lang.AssertionError: ConstraintLayout being a common direct descendant of a RecyclerView count does not match expected count.
If this PR removed a ConstraintLayout being a common direct descendant of a RecyclerView call, great! Please decrease the count.
Did this PR add or call code that increases the ConstraintLayout being a common direct descendant of a RecyclerView count?
Did you know that ConstraintLayouts are slow to inflate and are primarily used to flatten deep view hierarchies so can be under-performant as a common RecyclerView child?
Please do your best to implement a solution without adding ConstraintLayout being a common direct descendant of a RecyclerView calls.
Please consult the perf team if you have questions or believe that having this call
is the optimal solution.
Please note that we're not sure if this is a useful metric to assert: with your feedback, we'll find out over time if it is or is not. expected:<4> but was:<5>
at org.junit.Assert.fail(Assert.java:89)
at org.junit.Assert.failNotEquals(Assert.java:835)
at org.junit.Assert.assertEquals(Assert.java:120)
at org.mozilla.fenix.perf.StartupExcessiveResourceUseTest.verifyRunBlockingAndStrictModeSuppresionCount(StartupExcessiveResourceUseTest.kt:90)
### Build: 5/6 Main
|
test
|
intermittent ui test failure firebase test run stacktrace java lang assertionerror constraintlayout being a common direct descendant of a recyclerview count does not match expected count if this pr removed a constraintlayout being a common direct descendant of a recyclerview call great please decrease the count did this pr add or call code that increases the constraintlayout being a common direct descendant of a recyclerview count did you know that constraintlayouts are slow to inflate and are primarily used to flatten deep view hierarchies so can be under performant as a common recyclerview child please do your best to implement a solution without adding constraintlayout being a common direct descendant of a recyclerview calls please consult the perf team if you have questions or believe that having this call is the optimal solution please note that we re not sure if this is a useful metric to assert with your feedback we ll find out over time if it is or is not expected but was at org junit assert fail assert java at org junit assert failnotequals assert java at org junit assert assertequals assert java at org mozilla fenix perf startupexcessiveresourceusetest verifyrunblockingandstrictmodesuppresioncount startupexcessiveresourceusetest kt build main
| 1
|
94,214
| 8,476,470,328
|
IssuesEvent
|
2018-10-24 22:04:30
|
ORNL-CEES/DataTransferKit
|
https://api.github.com/repos/ORNL-CEES/DataTransferKit
|
closed
|
CII best practices
|
Low Priority New Feature Testing
|
I've been listening to ChangeLog podcast recently about Core Infrastructure Initiative. In short, they propose a list of things a project should follow. This was mostly for core projects, but I thought that we may find some interesting things to look at. The list of criteria is [here](https://github.com/linuxfoundation/cii-best-practices-badge/blob/master/doc/criteria.md).
One of the things they recommend is doing static and dynamic analysis of the code. We don't do that, I think.
|
1.0
|
CII best practices - I've been listening to ChangeLog podcast recently about Core Infrastructure Initiative. In short, they propose a list of things a project should follow. This was mostly for core projects, but I thought that we may find some interesting things to look at. The list of criteria is [here](https://github.com/linuxfoundation/cii-best-practices-badge/blob/master/doc/criteria.md).
One of the things they recommend is doing static and dynamic analysis of the code. We don't do that, I think.
|
test
|
cii best practices i ve been listening to changelog podcast recently about core infrastructure initiative in short they propose a list of things a project should follow this was mostly for core projects but i thought that we may find some interesting things to look at the list of criteria is one of the things they recommend is doing static and dynamic analysis of the code we don t do that i think
| 1
|
464,027
| 13,305,204,255
|
IssuesEvent
|
2020-08-25 18:09:45
|
google/gvisor
|
https://api.github.com/repos/google/gvisor
|
closed
|
API to list all ARP/NDP entries
|
area: networking priority: p2 type: enhancement
|
An API needs to be exposed on `tcpip.stack.Stack` to list all IP address to MAC address associations on a given NIC. This will be used for network testing and manual debugging. Partially unblocks running the ARP and NDP IxANVL test suites.
|
1.0
|
API to list all ARP/NDP entries - An API needs to be exposed on `tcpip.stack.Stack` to list all IP address to MAC address associations on a given NIC. This will be used for network testing and manual debugging. Partially unblocks running the ARP and NDP IxANVL test suites.
|
non_test
|
api to list all arp ndp entries an api needs to be exposed on tcpip stack stack to list all ip address to mac address associations on a given nic this will be used for network testing and manual debugging partially unblocks running the arp and ndp ixanvl test suites
| 0
|
143,240
| 19,161,734,534
|
IssuesEvent
|
2021-12-03 01:31:50
|
KingdomB/liri-node-app
|
https://api.github.com/repos/KingdomB/liri-node-app
|
opened
|
CVE-2021-32804 (High) detected in tar-2.2.1.tgz
|
security vulnerability
|
## CVE-2021-32804 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tar-2.2.1.tgz</b></p></summary>
<p>tar for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-2.2.1.tgz">https://registry.npmjs.org/tar/-/tar-2.2.1.tgz</a></p>
<p>Path to dependency file: /liri-node-app/package.json</p>
<p>Path to vulnerable library: liri-node-app/node_modules/npm/node_modules/node-gyp/node_modules/tar/package.json</p>
<p>
Dependency Hierarchy:
- npm-6.9.0.tgz (Root Library)
- node-gyp-3.8.0.tgz
- :x: **tar-2.2.1.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The npm package "tar" (aka node-tar) before versions 6.1.1, 5.0.6, 4.4.14, and 3.3.2 has a arbitrary File Creation/Overwrite vulnerability due to insufficient absolute path sanitization. node-tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the `preservePaths` flag is not set to `true`. This is achieved by stripping the absolute path root from any absolute file paths contained in a tar file. For example `/home/user/.bashrc` would turn into `home/user/.bashrc`. This logic was insufficient when file paths contained repeated path roots such as `////home/user/.bashrc`. `node-tar` would only strip a single path root from such paths. When given an absolute file path with repeating path roots, the resulting path (e.g. `///home/user/.bashrc`) would still resolve to an absolute path, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.2, 4.4.14, 5.0.6 and 6.1.1. Users may work around this vulnerability without upgrading by creating a custom `onentry` method which sanitizes the `entry.path` or a `filter` method which removes entries with absolute paths. See referenced GitHub Advisory for details. Be aware of CVE-2021-32803 which fixes a similar bug in later versions of tar.
<p>Publish Date: 2021-08-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-32804>CVE-2021-32804</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: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/npm/node-tar/security/advisories/GHSA-3jfq-g458-7qm9">https://github.com/npm/node-tar/security/advisories/GHSA-3jfq-g458-7qm9</a></p>
<p>Release Date: 2021-08-03</p>
<p>Fix Resolution: tar - 3.2.2, 4.4.14, 5.0.6, 6.1.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2021-32804 (High) detected in tar-2.2.1.tgz - ## CVE-2021-32804 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tar-2.2.1.tgz</b></p></summary>
<p>tar for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-2.2.1.tgz">https://registry.npmjs.org/tar/-/tar-2.2.1.tgz</a></p>
<p>Path to dependency file: /liri-node-app/package.json</p>
<p>Path to vulnerable library: liri-node-app/node_modules/npm/node_modules/node-gyp/node_modules/tar/package.json</p>
<p>
Dependency Hierarchy:
- npm-6.9.0.tgz (Root Library)
- node-gyp-3.8.0.tgz
- :x: **tar-2.2.1.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The npm package "tar" (aka node-tar) before versions 6.1.1, 5.0.6, 4.4.14, and 3.3.2 has a arbitrary File Creation/Overwrite vulnerability due to insufficient absolute path sanitization. node-tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the `preservePaths` flag is not set to `true`. This is achieved by stripping the absolute path root from any absolute file paths contained in a tar file. For example `/home/user/.bashrc` would turn into `home/user/.bashrc`. This logic was insufficient when file paths contained repeated path roots such as `////home/user/.bashrc`. `node-tar` would only strip a single path root from such paths. When given an absolute file path with repeating path roots, the resulting path (e.g. `///home/user/.bashrc`) would still resolve to an absolute path, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.2, 4.4.14, 5.0.6 and 6.1.1. Users may work around this vulnerability without upgrading by creating a custom `onentry` method which sanitizes the `entry.path` or a `filter` method which removes entries with absolute paths. See referenced GitHub Advisory for details. Be aware of CVE-2021-32803 which fixes a similar bug in later versions of tar.
<p>Publish Date: 2021-08-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-32804>CVE-2021-32804</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: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/npm/node-tar/security/advisories/GHSA-3jfq-g458-7qm9">https://github.com/npm/node-tar/security/advisories/GHSA-3jfq-g458-7qm9</a></p>
<p>Release Date: 2021-08-03</p>
<p>Fix Resolution: tar - 3.2.2, 4.4.14, 5.0.6, 6.1.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 tar tgz cve high severity vulnerability vulnerable library tar tgz tar for node library home page a href path to dependency file liri node app package json path to vulnerable library liri node app node modules npm node modules node gyp node modules tar package json dependency hierarchy npm tgz root library node gyp tgz x tar tgz vulnerable library vulnerability details the npm package tar aka node tar before versions and has a arbitrary file creation overwrite vulnerability due to insufficient absolute path sanitization node tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the preservepaths flag is not set to true this is achieved by stripping the absolute path root from any absolute file paths contained in a tar file for example home user bashrc would turn into home user bashrc this logic was insufficient when file paths contained repeated path roots such as home user bashrc node tar would only strip a single path root from such paths when given an absolute file path with repeating path roots the resulting path e g home user bashrc would still resolve to an absolute path thus allowing arbitrary file creation and overwrite this issue was addressed in releases and users may work around this vulnerability without upgrading by creating a custom onentry method which sanitizes the entry path or a filter method which removes entries with absolute paths see referenced github advisory for details be aware of cve which fixes a similar bug in later versions of tar publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution tar step up your open source security game with whitesource
| 0
|
59,498
| 6,653,624,135
|
IssuesEvent
|
2017-09-29 09:10:59
|
Transkribus/TWI-edit
|
https://api.github.com/repos/Transkribus/TWI-edit
|
closed
|
Line-by-line zooming out behaves strange
|
bug ready to test
|
Initial view:
Zooming with mouse wheel (cursor approximately 1/3 from right border, vertically centered):
Would expect some regularity here, e.g. the top left corner of the image to remain in the same position, i.e. for zooming out only scaling but fixed top left corner - or to be consistent with the zoom buttons in the tool bar: keep the focus point in the center of the snipped and only zoom in/out at this position.
For zooming in, the focus point should indeed be the position of the mouse cursor.
Suggestion for quick fix alternative: disable zooming for mouse gestures.
|
1.0
|
Line-by-line zooming out behaves strange - Initial view:
Zooming with mouse wheel (cursor approximately 1/3 from right border, vertically centered):
Would expect some regularity here, e.g. the top left corner of the image to remain in the same position, i.e. for zooming out only scaling but fixed top left corner - or to be consistent with the zoom buttons in the tool bar: keep the focus point in the center of the snipped and only zoom in/out at this position.
For zooming in, the focus point should indeed be the position of the mouse cursor.
Suggestion for quick fix alternative: disable zooming for mouse gestures.
|
test
|
line by line zooming out behaves strange initial view zooming with mouse wheel cursor approximately from right border vertically centered would expect some regularity here e g the top left corner of the image to remain in the same position i e for zooming out only scaling but fixed top left corner or to be consistent with the zoom buttons in the tool bar keep the focus point in the center of the snipped and only zoom in out at this position for zooming in the focus point should indeed be the position of the mouse cursor suggestion for quick fix alternative disable zooming for mouse gestures
| 1
|
469,462
| 13,509,271,057
|
IssuesEvent
|
2020-09-14 08:58:01
|
ioanniswd/pot
|
https://api.github.com/repos/ioanniswd/pot
|
closed
|
Refactor the way tables are being printed
|
High Priority
|
At first, the simplicity of the cases to cover made the current approach of printing tables of data simplistic. With more columns and ways to align said data, the need arises for a consistent way to print table data.
|
1.0
|
Refactor the way tables are being printed - At first, the simplicity of the cases to cover made the current approach of printing tables of data simplistic. With more columns and ways to align said data, the need arises for a consistent way to print table data.
|
non_test
|
refactor the way tables are being printed at first the simplicity of the cases to cover made the current approach of printing tables of data simplistic with more columns and ways to align said data the need arises for a consistent way to print table data
| 0
|
395,777
| 27,087,069,644
|
IssuesEvent
|
2023-02-14 17:47:17
|
cloudflare/cloudflare-docs
|
https://api.github.com/repos/cloudflare/cloudflare-docs
|
closed
|
List Algorithm 13 alternative name
|
documentation content:edit
|
### Which Cloudflare product does this pertain to?
DNS
### Existing documentation URL(s)
https://developers.cloudflare.com/dns/additional-options/dnssec
https://dash.cloudflare.com -> DNSSEC Setup fields
### Section that requires update
https://developers.cloudflare.com/dns/additional-options/dnssec
---Step 2 - Add DS record to your registrar
https://dash.cloudflare.com -> DNSSEC Setup fields
--- Algorithm
### What needs to change?
This suggestion is also for the dashboard when enabling DSSEC on a website and it provides you with all the fields to enter on the registrar. Add alternative name for Algorithm 13.
### How should it change?
https://developers.cloudflare.com/dns/additional-options/dnssec
---Step 2 - Add DS record to your registrar
------ If algorithm 13 is not listed by your registrar, it may also be called "ECDSA Curve P-256 with SHA-256".
https://dash.cloudflare.com -> DNSSEC Setup fields
--- Algorithm: 13 aka "ECDSA Curve P-256 with SHA-256"
### Additional information
|
1.0
|
List Algorithm 13 alternative name - ### Which Cloudflare product does this pertain to?
DNS
### Existing documentation URL(s)
https://developers.cloudflare.com/dns/additional-options/dnssec
https://dash.cloudflare.com -> DNSSEC Setup fields
### Section that requires update
https://developers.cloudflare.com/dns/additional-options/dnssec
---Step 2 - Add DS record to your registrar
https://dash.cloudflare.com -> DNSSEC Setup fields
--- Algorithm
### What needs to change?
This suggestion is also for the dashboard when enabling DSSEC on a website and it provides you with all the fields to enter on the registrar. Add alternative name for Algorithm 13.
### How should it change?
https://developers.cloudflare.com/dns/additional-options/dnssec
---Step 2 - Add DS record to your registrar
------ If algorithm 13 is not listed by your registrar, it may also be called "ECDSA Curve P-256 with SHA-256".
https://dash.cloudflare.com -> DNSSEC Setup fields
--- Algorithm: 13 aka "ECDSA Curve P-256 with SHA-256"
### Additional information
|
non_test
|
list algorithm alternative name which cloudflare product does this pertain to dns existing documentation url s dnssec setup fields section that requires update step add ds record to your registrar dnssec setup fields algorithm what needs to change this suggestion is also for the dashboard when enabling dssec on a website and it provides you with all the fields to enter on the registrar add alternative name for algorithm how should it change step add ds record to your registrar if algorithm is not listed by your registrar it may also be called ecdsa curve p with sha dnssec setup fields algorithm aka ecdsa curve p with sha additional information
| 0
|
161,563
| 12,551,448,672
|
IssuesEvent
|
2020-06-06 14:48:12
|
Speedfan94/PDS_Project
|
https://api.github.com/repos/Speedfan94/PDS_Project
|
closed
|
test datapreparation
|
module/cleaning type/testing
|
our datapreparation algorithms should be tested in a notebook
_optional: analyzing runtime of reset index methods_
ideas:
- choose a specific bike from original df
- print and compare these bike data with the results of the datapreparation df
|
1.0
|
test datapreparation - our datapreparation algorithms should be tested in a notebook
_optional: analyzing runtime of reset index methods_
ideas:
- choose a specific bike from original df
- print and compare these bike data with the results of the datapreparation df
|
test
|
test datapreparation our datapreparation algorithms should be tested in a notebook optional analyzing runtime of reset index methods ideas choose a specific bike from original df print and compare these bike data with the results of the datapreparation df
| 1
|
40,679
| 10,564,916,294
|
IssuesEvent
|
2019-10-05 06:40:54
|
scality/metalk8s
|
https://api.github.com/repos/scality/metalk8s
|
closed
|
Build the documentation inside a container
|
build medium moonshot
|
**Component**:
buildchain
**Why this is needed**:
We are now shipping the documentation as a PDF in the ISO, consequently we now build the PDF during the build process and this requires some new dependencies (such as a LaTeX distribution, which can be quite big…).
Since people may simply want generate an ISO and have nothing to do with the doc itself, it's annoying to require them to install those new dependencies.
To circumvent this issue, we can instead use a container that contains the dependencies to build the documentation.
**What should be done**:
Use a container to build the documentation (we already use one in the CI, try to reuse it)
**Implementation proposal** (strongly recommended):
- add a new builder image in the buildchain
- use the builder image for the `doc:*` targets
**Test plan**:
Try to build an ISO without LaTeX installed on your machine.
|
1.0
|
Build the documentation inside a container - **Component**:
buildchain
**Why this is needed**:
We are now shipping the documentation as a PDF in the ISO, consequently we now build the PDF during the build process and this requires some new dependencies (such as a LaTeX distribution, which can be quite big…).
Since people may simply want generate an ISO and have nothing to do with the doc itself, it's annoying to require them to install those new dependencies.
To circumvent this issue, we can instead use a container that contains the dependencies to build the documentation.
**What should be done**:
Use a container to build the documentation (we already use one in the CI, try to reuse it)
**Implementation proposal** (strongly recommended):
- add a new builder image in the buildchain
- use the builder image for the `doc:*` targets
**Test plan**:
Try to build an ISO without LaTeX installed on your machine.
|
non_test
|
build the documentation inside a container component buildchain why this is needed we are now shipping the documentation as a pdf in the iso consequently we now build the pdf during the build process and this requires some new dependencies such as a latex distribution which can be quite big… since people may simply want generate an iso and have nothing to do with the doc itself it s annoying to require them to install those new dependencies to circumvent this issue we can instead use a container that contains the dependencies to build the documentation what should be done use a container to build the documentation we already use one in the ci try to reuse it implementation proposal strongly recommended add a new builder image in the buildchain use the builder image for the doc targets test plan try to build an iso without latex installed on your machine
| 0
|
30,494
| 8,555,137,134
|
IssuesEvent
|
2018-11-08 09:10:26
|
mozilla-mobile/reference-browser
|
https://api.github.com/repos/mozilla-mobile/reference-browser
|
opened
|
Cleanup flavors and build in parallel
|
🏗️ build 🤖 automation
|
Let's speed up our builds:
* Build all variants in parallel
* Remove unneeded variants (Maybe we should just go with GeckoView Nightly only for now?)
|
1.0
|
Cleanup flavors and build in parallel - Let's speed up our builds:
* Build all variants in parallel
* Remove unneeded variants (Maybe we should just go with GeckoView Nightly only for now?)
|
non_test
|
cleanup flavors and build in parallel let s speed up our builds build all variants in parallel remove unneeded variants maybe we should just go with geckoview nightly only for now
| 0
|
242,949
| 20,327,345,119
|
IssuesEvent
|
2022-02-18 07:19:52
|
MohistMC/Mohist
|
https://api.github.com/repos/MohistMC/Mohist
|
reopened
|
The server cannot start
|
1.16.5 Wait Needs Testing
|
<!-- ISSUE_TEMPLATE_3 -> IMPORTANT: DO NOT DELETE THIS LINE.-->
<!-- Thank you for reporting ! Please note that issues can take a lot of time to be fixed and there is no eta.-->
<!-- If you don't know where to upload your logs and crash reports, you can use these websites : -->
<!-- https://gist.github.com (recommended) -->
<!-- https://mclo.gs -->
<!-- https://haste.mohistmc.com -->
<!-- https://pastebin.com -->
<!-- TO FILL THIS TEMPLATE, YOU NEED TO REPLACE THE {} BY WHAT YOU WANT -->
**Minecraft Version :**1.16.5
**Mohist Version :** mohist-1.16.5-955-server.jar
**Operating System :** Windows
**Logs :** Server logs:[2022-02-18-1.log](https://github.com/MohistMC/Mohist/files/8094748/2022-02-18-1.log)
**Mod list :** [modslist.txt](https://github.com/MohistMC/Mohist/files/8094735/modslist.txt)
**Description of issue :** After adding all the mods, the server was started, but there was no way to start and an error was reported
|
1.0
|
The server cannot start - <!-- ISSUE_TEMPLATE_3 -> IMPORTANT: DO NOT DELETE THIS LINE.-->
<!-- Thank you for reporting ! Please note that issues can take a lot of time to be fixed and there is no eta.-->
<!-- If you don't know where to upload your logs and crash reports, you can use these websites : -->
<!-- https://gist.github.com (recommended) -->
<!-- https://mclo.gs -->
<!-- https://haste.mohistmc.com -->
<!-- https://pastebin.com -->
<!-- TO FILL THIS TEMPLATE, YOU NEED TO REPLACE THE {} BY WHAT YOU WANT -->
**Minecraft Version :**1.16.5
**Mohist Version :** mohist-1.16.5-955-server.jar
**Operating System :** Windows
**Logs :** Server logs:[2022-02-18-1.log](https://github.com/MohistMC/Mohist/files/8094748/2022-02-18-1.log)
**Mod list :** [modslist.txt](https://github.com/MohistMC/Mohist/files/8094735/modslist.txt)
**Description of issue :** After adding all the mods, the server was started, but there was no way to start and an error was reported
|
test
|
the server cannot start important do not delete this line minecraft version mohist version mohist server jar operating system windows logs server logs mod list description of issue after adding all the mods the server was started but there was no way to start and an error was reported
| 1
|
108,157
| 9,284,513,547
|
IssuesEvent
|
2019-03-21 02:02:13
|
cockroachdb/cockroach
|
https://api.github.com/repos/cockroachdb/cockroach
|
closed
|
roachtest: kv0/enc=false/nodes=3/cpu=96 failed
|
C-test-failure O-roachtest O-robot
|
SHA: https://github.com/cockroachdb/cockroach/commits/3a7ea2d8c9d4a3e0d97f8f106fcf95b3f03765ec
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 && \
stdbuf -oL -eL \
make stressrace TESTS=kv0/enc=false/nodes=3/cpu=96 PKG=roachtest TESTTIMEOUT=5m STRESSFLAGS='-maxtime 20m -timeout 10m' 2>&1 | tee /tmp/stress.log
```
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=1187484&tab=buildLog
```
The test failed on master:
cluster.go:1267,kv.go:69,cluster.go:1605,errgroup.go:57: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/bin/roachprod run teamcity-1187484-kv0-enc-false-nodes-3-cpu-96:4 -- ./workload run kv --init --splits=1000 --histograms=logs/stats.json --concurrency=192 --duration=10m --read-percent=0 {pgurl:1-3} returned:
stderr:
stdout:
Error: dial tcp 172.31.34.229:26257: connect: connection timed out
Error: exit status 1
: exit status 1
cluster.go:1626,kv.go:72,kv.go:137,test.go:1214: Goexit() was called
```
|
2.0
|
roachtest: kv0/enc=false/nodes=3/cpu=96 failed - SHA: https://github.com/cockroachdb/cockroach/commits/3a7ea2d8c9d4a3e0d97f8f106fcf95b3f03765ec
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 && \
stdbuf -oL -eL \
make stressrace TESTS=kv0/enc=false/nodes=3/cpu=96 PKG=roachtest TESTTIMEOUT=5m STRESSFLAGS='-maxtime 20m -timeout 10m' 2>&1 | tee /tmp/stress.log
```
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=1187484&tab=buildLog
```
The test failed on master:
cluster.go:1267,kv.go:69,cluster.go:1605,errgroup.go:57: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/bin/roachprod run teamcity-1187484-kv0-enc-false-nodes-3-cpu-96:4 -- ./workload run kv --init --splits=1000 --histograms=logs/stats.json --concurrency=192 --duration=10m --read-percent=0 {pgurl:1-3} returned:
stderr:
stdout:
Error: dial tcp 172.31.34.229:26257: connect: connection timed out
Error: exit status 1
: exit status 1
cluster.go:1626,kv.go:72,kv.go:137,test.go:1214: Goexit() was called
```
|
test
|
roachtest enc false nodes cpu 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 stdbuf ol el make stressrace tests enc false nodes cpu pkg roachtest testtimeout stressflags maxtime timeout tee tmp stress log failed test the test failed on master cluster go kv go cluster go errgroup go home agent work go src github com cockroachdb cockroach bin roachprod run teamcity enc false nodes cpu workload run kv init splits histograms logs stats json concurrency duration read percent pgurl returned stderr stdout error dial tcp connect connection timed out error exit status exit status cluster go kv go kv go test go goexit was called
| 1
|
252,806
| 8,042,427,814
|
IssuesEvent
|
2018-07-31 08:07:06
|
telerik/kendo-ui-core
|
https://api.github.com/repos/telerik/kendo-ui-core
|
opened
|
Clicking on a Checkbox in Batch Editing Exits Edit Mode
|
Bug C: Grid Kendo1 Priority 3 SEV: Medium
|
### Bug report
Clicking on a checkbox in batch editing exits edit mode in Mozilla and Safari on MacOS.
### Reproduction of the problem
1. Open the[ Demo ](http://dojo.telerik.com/aMaqiJEJ)
2. Click on any cell of the Mod1 column.
3. Click the checkbox to edit the current item
### Current behavior
The current item is not updated and the grid is no longer in edit mode.
### Expected/desired behavior
The current item should be updated and the grid should not exit edit mode
### Environment
* **Kendo UI version:** 2018.2.620
* **Browser:** [Firefox XX | Safari XX ]
|
1.0
|
Clicking on a Checkbox in Batch Editing Exits Edit Mode - ### Bug report
Clicking on a checkbox in batch editing exits edit mode in Mozilla and Safari on MacOS.
### Reproduction of the problem
1. Open the[ Demo ](http://dojo.telerik.com/aMaqiJEJ)
2. Click on any cell of the Mod1 column.
3. Click the checkbox to edit the current item
### Current behavior
The current item is not updated and the grid is no longer in edit mode.
### Expected/desired behavior
The current item should be updated and the grid should not exit edit mode
### Environment
* **Kendo UI version:** 2018.2.620
* **Browser:** [Firefox XX | Safari XX ]
|
non_test
|
clicking on a checkbox in batch editing exits edit mode bug report clicking on a checkbox in batch editing exits edit mode in mozilla and safari on macos reproduction of the problem open the click on any cell of the column click the checkbox to edit the current item current behavior the current item is not updated and the grid is no longer in edit mode expected desired behavior the current item should be updated and the grid should not exit edit mode environment kendo ui version browser
| 0
|
174,997
| 13,528,251,483
|
IssuesEvent
|
2020-09-15 16:27:16
|
kubernetes-sigs/cluster-api
|
https://api.github.com/repos/kubernetes-sigs/cluster-api
|
closed
|
[e2e] Remove CNIManifestPath from the test framework
|
area/api area/testing kind/cleanup priority/important-longterm
|
CNI in e2e tests will be installed using ClusterResourceSet going forward, we can remove CNIManifestPath from ApplyClusterTemplateAndWaitInput. Since this is a breaking change, we should add this change in the release notes.
Here is the PR to revert this change for v0.3.8 release as it was not added to the release notes: https://github.com/kubernetes-sigs/cluster-api/pull/3608
/kind cleanup
|
1.0
|
[e2e] Remove CNIManifestPath from the test framework - CNI in e2e tests will be installed using ClusterResourceSet going forward, we can remove CNIManifestPath from ApplyClusterTemplateAndWaitInput. Since this is a breaking change, we should add this change in the release notes.
Here is the PR to revert this change for v0.3.8 release as it was not added to the release notes: https://github.com/kubernetes-sigs/cluster-api/pull/3608
/kind cleanup
|
test
|
remove cnimanifestpath from the test framework cni in tests will be installed using clusterresourceset going forward we can remove cnimanifestpath from applyclustertemplateandwaitinput since this is a breaking change we should add this change in the release notes here is the pr to revert this change for release as it was not added to the release notes kind cleanup
| 1
|
196,578
| 14,880,333,391
|
IssuesEvent
|
2021-01-20 09:02:41
|
ryanheise/just_audio
|
https://api.github.com/repos/ryanheise/just_audio
|
closed
|
Setting initial duration throws a NullPointerException
|
3 testing bug
|
<!-- ALL SECTIONS BELOW MUST BE COMPLETED -->
**Which API doesn't behave as documented, and how does it misbehave?**
Attempting to set an initial duration either via:
```
await _player.setUrl(
'https://s3.amazonaws.com/scifri-segments/scifri201711241.mp3',
initialPosition: Duration(seconds: 10));
```
For example or:
```
await _player.setAudioSource(
AudioSource.uri(
Uri.parse(
"https://s3.amazonaws.com/scifri-segments/scifri201711241.mp3"),
tag: AudioMetadata(
album: "Science Friday",
title: "From Cat Rheology To Operatic Incompetence",
artwork:
"https://media.wnyc.org/i/1400/1400/l/80/1/ScienceFriday_WNYCStudios_1400.jpg",
),
),
initialPosition: Duration(seconds: 1),
);
```
Issue occurs for both local and streamed files.
**Minimal reproduction project**
Please find a version of your example application that reproduces this error [here](https://github.com/amugofjava/just_audio)
**To Reproduce (i.e. user steps, not code)**
Run the example and it should fail straight away
**Error messages**
```
W/System.err(32373): java.lang.NullPointerException: Attempt to invoke virtual method 'int java.lang.Integer.intValue()' on a null object reference
W/System.err(32373): at com.ryanheise.just_audio.AudioPlayer.onTimelineChanged(AudioPlayer.java:191)
W/System.err(32373): at com.google.android.exoplayer2.ExoPlayerImpl$PlaybackInfoUpdate.lambda$run$0$ExoPlayerImpl$PlaybackInfoUpdate(ExoPlayerImpl.java:1410)
W/System.err(32373): at com.google.android.exoplayer2.-$$Lambda$ExoPlayerImpl$PlaybackInfoUpdate$N_S5kRfhaRTAkH28P5luFgKnFjQ.invokeListener(Unknown Source:2)
W/System.err(32373): at com.google.android.exoplayer2.BasePlayer$ListenerHolder.invoke(BasePlayer.java:279)
W/System.err(32373): at com.google.android.exoplayer2.ExoPlayerImpl.invokeAll(ExoPlayerImpl.java:1496)
W/System.err(32373): at com.google.android.exoplayer2.ExoPlayerImpl.access$100(ExoPlayerImpl.java:56)
W/System.err(32373): at com.google.android.exoplayer2.ExoPlayerImpl$PlaybackInfoUpdate.run(ExoPlayerImpl.java:1408)
W/System.err(32373): at com.google.android.exoplayer2.ExoPlayerImpl.notifyListeners(ExoPlayerImpl.java:1326)
W/System.err(32373): at com.google.android.exoplayer2.ExoPlayerImpl.updatePlaybackInfo(ExoPlayerImpl.java:954)
W/System.err(32373): at com.google.android.exoplayer2.ExoPlayerImpl.setMediaSourcesInternal(ExoPlayerImpl.java:1062)
W/System.err(32373): at com.google.android.exoplayer2.ExoPlayerImpl.setMediaSources(ExoPlayerImpl.java:384)
W/System.err(32373): at com.google.android.exoplayer2.ExoPlayerImpl.setMediaSources(ExoPlayerImpl.java:379)
W/System.err(32373): at com.google.android.exoplayer2.ExoPlayerImpl.setMediaSource(ExoPlayerImpl.java:363)
W/System.err(32373): at com.google.android.exoplayer2.SimpleExoPlayer.setMediaSource(SimpleExoPlayer.java:1499)
W/System.err(32373): at com.ryanheise.just_audio.AudioPlayer.load(AudioPlayer.java:525)
W/System.err(32373): at com.ryanheise.just_audio.AudioPlayer.onMethodCall(AudioPlayer.java:289)
W/System.err(32373): at io.flutter.plugin.common.MethodChannel$IncomingMethodCallHandler.onMessage(MethodChannel.java:233)
W/System.err(32373): at io.flutter.embedding.engine.dart.DartMessenger.handleMessageFromDart(DartMessenger.java:85)
W/System.err(32373): at io.flutter.embedding.engine.FlutterJNI.handlePlatformMessage(FlutterJNI.java:692)
W/System.err(32373): at android.os.MessageQueue.nativePollOnce(Native Method)
W/System.err(32373): at android.os.MessageQueue.next(MessageQueue.java:335)
W/System.err(32373): at android.os.Looper.loop(Looper.java:183)
W/System.err(32373): at android.app.ActivityThread.main(ActivityThread.java:7656)
W/System.err(32373): at java.lang.reflect.Method.invoke(Native Method)
W/System.err(32373): at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
W/System.err(32373): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
I/flutter (32373): #0 AudioPlayer._load (package:just_audio/just_audio.dart:637:11)
```
**Expected behavior**
Playback should start from the `Duration` value. If you set `preload` to false the exception is not thrown, but you can no longer hear any audio playback; if I set `preload` to false and manually call the `.load()` method the above exception is thrown. If I remove the Duration playback works correctly.
**Smartphone (please complete the following information):**
- Device: Android 11 emulator.
- OS: Android
**Flutter SDK version**
```
[✓] Flutter (Channel stable, 1.22.5, on Linux, locale en_GB.UTF-8)
• Flutter version 1.22.5 at /home/ben/Development/flutter
• Framework revision 7891006299 (5 weeks ago), 2020-12-10 11:54:40 -0800
• Engine revision ae90085a84
• Dart version 2.10.4
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
• Android SDK at /media/ubuntudata/Development/android/sdk
• Platform android-30, build-tools 30.0.3
• Java binary at: /home/ben/Development/android/android-studio/jre/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
• All Android licenses accepted.
[✓] Android Studio (version 4.0)
• Android Studio at /home/ben/Development/android/android-studio
• Flutter plugin version 50.0.1
• Dart plugin version 193.7547
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
[✓] VS Code (version 1.52.1)
• VS Code at /usr/share/code
• Flutter extension version 3.18.1
[✓] Connected device (1 available)
• sdk gphone x86 64 (mobile) • emulator-5554 • android-x64 • Android 11 (API 30) (emulator)
• No issues found!
```
**Additional context**
I used to use the `seek` method after setting the URL to set the start position, but I don't think I can do this any more as you can't do it before a file is playing. Do I have that correct?
Many thanks for a great library.
|
1.0
|
Setting initial duration throws a NullPointerException - <!-- ALL SECTIONS BELOW MUST BE COMPLETED -->
**Which API doesn't behave as documented, and how does it misbehave?**
Attempting to set an initial duration either via:
```
await _player.setUrl(
'https://s3.amazonaws.com/scifri-segments/scifri201711241.mp3',
initialPosition: Duration(seconds: 10));
```
For example or:
```
await _player.setAudioSource(
AudioSource.uri(
Uri.parse(
"https://s3.amazonaws.com/scifri-segments/scifri201711241.mp3"),
tag: AudioMetadata(
album: "Science Friday",
title: "From Cat Rheology To Operatic Incompetence",
artwork:
"https://media.wnyc.org/i/1400/1400/l/80/1/ScienceFriday_WNYCStudios_1400.jpg",
),
),
initialPosition: Duration(seconds: 1),
);
```
Issue occurs for both local and streamed files.
**Minimal reproduction project**
Please find a version of your example application that reproduces this error [here](https://github.com/amugofjava/just_audio)
**To Reproduce (i.e. user steps, not code)**
Run the example and it should fail straight away
**Error messages**
```
W/System.err(32373): java.lang.NullPointerException: Attempt to invoke virtual method 'int java.lang.Integer.intValue()' on a null object reference
W/System.err(32373): at com.ryanheise.just_audio.AudioPlayer.onTimelineChanged(AudioPlayer.java:191)
W/System.err(32373): at com.google.android.exoplayer2.ExoPlayerImpl$PlaybackInfoUpdate.lambda$run$0$ExoPlayerImpl$PlaybackInfoUpdate(ExoPlayerImpl.java:1410)
W/System.err(32373): at com.google.android.exoplayer2.-$$Lambda$ExoPlayerImpl$PlaybackInfoUpdate$N_S5kRfhaRTAkH28P5luFgKnFjQ.invokeListener(Unknown Source:2)
W/System.err(32373): at com.google.android.exoplayer2.BasePlayer$ListenerHolder.invoke(BasePlayer.java:279)
W/System.err(32373): at com.google.android.exoplayer2.ExoPlayerImpl.invokeAll(ExoPlayerImpl.java:1496)
W/System.err(32373): at com.google.android.exoplayer2.ExoPlayerImpl.access$100(ExoPlayerImpl.java:56)
W/System.err(32373): at com.google.android.exoplayer2.ExoPlayerImpl$PlaybackInfoUpdate.run(ExoPlayerImpl.java:1408)
W/System.err(32373): at com.google.android.exoplayer2.ExoPlayerImpl.notifyListeners(ExoPlayerImpl.java:1326)
W/System.err(32373): at com.google.android.exoplayer2.ExoPlayerImpl.updatePlaybackInfo(ExoPlayerImpl.java:954)
W/System.err(32373): at com.google.android.exoplayer2.ExoPlayerImpl.setMediaSourcesInternal(ExoPlayerImpl.java:1062)
W/System.err(32373): at com.google.android.exoplayer2.ExoPlayerImpl.setMediaSources(ExoPlayerImpl.java:384)
W/System.err(32373): at com.google.android.exoplayer2.ExoPlayerImpl.setMediaSources(ExoPlayerImpl.java:379)
W/System.err(32373): at com.google.android.exoplayer2.ExoPlayerImpl.setMediaSource(ExoPlayerImpl.java:363)
W/System.err(32373): at com.google.android.exoplayer2.SimpleExoPlayer.setMediaSource(SimpleExoPlayer.java:1499)
W/System.err(32373): at com.ryanheise.just_audio.AudioPlayer.load(AudioPlayer.java:525)
W/System.err(32373): at com.ryanheise.just_audio.AudioPlayer.onMethodCall(AudioPlayer.java:289)
W/System.err(32373): at io.flutter.plugin.common.MethodChannel$IncomingMethodCallHandler.onMessage(MethodChannel.java:233)
W/System.err(32373): at io.flutter.embedding.engine.dart.DartMessenger.handleMessageFromDart(DartMessenger.java:85)
W/System.err(32373): at io.flutter.embedding.engine.FlutterJNI.handlePlatformMessage(FlutterJNI.java:692)
W/System.err(32373): at android.os.MessageQueue.nativePollOnce(Native Method)
W/System.err(32373): at android.os.MessageQueue.next(MessageQueue.java:335)
W/System.err(32373): at android.os.Looper.loop(Looper.java:183)
W/System.err(32373): at android.app.ActivityThread.main(ActivityThread.java:7656)
W/System.err(32373): at java.lang.reflect.Method.invoke(Native Method)
W/System.err(32373): at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
W/System.err(32373): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
I/flutter (32373): #0 AudioPlayer._load (package:just_audio/just_audio.dart:637:11)
```
**Expected behavior**
Playback should start from the `Duration` value. If you set `preload` to false the exception is not thrown, but you can no longer hear any audio playback; if I set `preload` to false and manually call the `.load()` method the above exception is thrown. If I remove the Duration playback works correctly.
**Smartphone (please complete the following information):**
- Device: Android 11 emulator.
- OS: Android
**Flutter SDK version**
```
[✓] Flutter (Channel stable, 1.22.5, on Linux, locale en_GB.UTF-8)
• Flutter version 1.22.5 at /home/ben/Development/flutter
• Framework revision 7891006299 (5 weeks ago), 2020-12-10 11:54:40 -0800
• Engine revision ae90085a84
• Dart version 2.10.4
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
• Android SDK at /media/ubuntudata/Development/android/sdk
• Platform android-30, build-tools 30.0.3
• Java binary at: /home/ben/Development/android/android-studio/jre/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
• All Android licenses accepted.
[✓] Android Studio (version 4.0)
• Android Studio at /home/ben/Development/android/android-studio
• Flutter plugin version 50.0.1
• Dart plugin version 193.7547
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
[✓] VS Code (version 1.52.1)
• VS Code at /usr/share/code
• Flutter extension version 3.18.1
[✓] Connected device (1 available)
• sdk gphone x86 64 (mobile) • emulator-5554 • android-x64 • Android 11 (API 30) (emulator)
• No issues found!
```
**Additional context**
I used to use the `seek` method after setting the URL to set the start position, but I don't think I can do this any more as you can't do it before a file is playing. Do I have that correct?
Many thanks for a great library.
|
test
|
setting initial duration throws a nullpointerexception which api doesn t behave as documented and how does it misbehave attempting to set an initial duration either via await player seturl initialposition duration seconds for example or await player setaudiosource audiosource uri uri parse tag audiometadata album science friday title from cat rheology to operatic incompetence artwork initialposition duration seconds issue occurs for both local and streamed files minimal reproduction project please find a version of your example application that reproduces this error to reproduce i e user steps not code run the example and it should fail straight away error messages w system err java lang nullpointerexception attempt to invoke virtual method int java lang integer intvalue on a null object reference w system err at com ryanheise just audio audioplayer ontimelinechanged audioplayer java w system err at com google android exoplayerimpl playbackinfoupdate lambda run exoplayerimpl playbackinfoupdate exoplayerimpl java w system err at com google android lambda exoplayerimpl playbackinfoupdate n invokelistener unknown source w system err at com google android baseplayer listenerholder invoke baseplayer java w system err at com google android exoplayerimpl invokeall exoplayerimpl java w system err at com google android exoplayerimpl access exoplayerimpl java w system err at com google android exoplayerimpl playbackinfoupdate run exoplayerimpl java w system err at com google android exoplayerimpl notifylisteners exoplayerimpl java w system err at com google android exoplayerimpl updateplaybackinfo exoplayerimpl java w system err at com google android exoplayerimpl setmediasourcesinternal exoplayerimpl java w system err at com google android exoplayerimpl setmediasources exoplayerimpl java w system err at com google android exoplayerimpl setmediasources exoplayerimpl java w system err at com google android exoplayerimpl setmediasource exoplayerimpl java w system err at com google android simpleexoplayer setmediasource simpleexoplayer java w system err at com ryanheise just audio audioplayer load audioplayer java w system err at com ryanheise just audio audioplayer onmethodcall audioplayer java w system err at io flutter plugin common methodchannel incomingmethodcallhandler onmessage methodchannel java w system err at io flutter embedding engine dart dartmessenger handlemessagefromdart dartmessenger java w system err at io flutter embedding engine flutterjni handleplatformmessage flutterjni java w system err at android os messagequeue nativepollonce native method w system err at android os messagequeue next messagequeue java w system err at android os looper loop looper java w system err at android app activitythread main activitythread java w system err at java lang reflect method invoke native method w system err at com android internal os runtimeinit methodandargscaller run runtimeinit java w system err at com android internal os zygoteinit main zygoteinit java i flutter audioplayer load package just audio just audio dart expected behavior playback should start from the duration value if you set preload to false the exception is not thrown but you can no longer hear any audio playback if i set preload to false and manually call the load method the above exception is thrown if i remove the duration playback works correctly smartphone please complete the following information device android emulator os android flutter sdk version flutter channel stable on linux locale en gb utf • flutter version at home ben development flutter • framework revision weeks ago • engine revision • dart version android toolchain develop for android devices android sdk version • android sdk at media ubuntudata development android sdk • platform android build tools • java binary at home ben development android android studio jre bin java • java version openjdk runtime environment build release • all android licenses accepted android studio version • android studio at home ben development android android studio • flutter plugin version • dart plugin version • java version openjdk runtime environment build release vs code version • vs code at usr share code • flutter extension version connected device available • sdk gphone mobile • emulator • android • android api emulator • no issues found additional context i used to use the seek method after setting the url to set the start position but i don t think i can do this any more as you can t do it before a file is playing do i have that correct many thanks for a great library
| 1
|
86,409
| 8,035,345,932
|
IssuesEvent
|
2018-07-30 03:52:02
|
8xprotocol/contracts
|
https://api.github.com/repos/8xprotocol/contracts
|
closed
|
Complete Test Implementations for Executor Tests
|
Executor in progress testing
|
- [ ] REF: https://github.com/8xprotocol/contracts/blob/master/test/executor.js#L58
- [ ] REF: https://github.com/8xprotocol/contracts/blob/master/test/executor.js#L73
- [ ] REF: https://github.com/8xprotocol/contracts/blob/master/test/executor.js#L78
- [ ] REF: https://github.com/8xprotocol/contracts/blob/master/test/executor.js#L79
- [ ] REF: https://github.com/8xprotocol/contracts/blob/master/test/executor.js#L85
- [ ] REF: https://github.com/8xprotocol/contracts/blob/master/test/executor.js#L92
- [ ] REF: https://github.com/8xprotocol/contracts/blob/master/test/executor.js#L99
- [ ] REF: https://github.com/8xprotocol/contracts/blob/master/test/executor.js#L108
|
1.0
|
Complete Test Implementations for Executor Tests - - [ ] REF: https://github.com/8xprotocol/contracts/blob/master/test/executor.js#L58
- [ ] REF: https://github.com/8xprotocol/contracts/blob/master/test/executor.js#L73
- [ ] REF: https://github.com/8xprotocol/contracts/blob/master/test/executor.js#L78
- [ ] REF: https://github.com/8xprotocol/contracts/blob/master/test/executor.js#L79
- [ ] REF: https://github.com/8xprotocol/contracts/blob/master/test/executor.js#L85
- [ ] REF: https://github.com/8xprotocol/contracts/blob/master/test/executor.js#L92
- [ ] REF: https://github.com/8xprotocol/contracts/blob/master/test/executor.js#L99
- [ ] REF: https://github.com/8xprotocol/contracts/blob/master/test/executor.js#L108
|
test
|
complete test implementations for executor tests ref ref ref ref ref ref ref ref
| 1
|
276,233
| 23,978,244,251
|
IssuesEvent
|
2022-09-13 13:17:21
|
magma/magma
|
https://api.github.com/repos/magma/magma
|
closed
|
Parallelize Bazel LTE integ tests and sudo tests
|
component: ci LTE-Integration-Test bazel willfix
|
- The sudo tests take ca 40m, the LTE integ tests take ca. 1h40m without the sudo tests.
- The setup of the VM does not take very long and thus splitting the workflow into an LTE integ test and a sudo workflow would save the integ test workflow 40m and the sudo test workflow might only take an hour or so.
* split sudo and integ test in two jobs that can run in parallel
* do not create magma dev vm once at the beginning - in the future we might use different vms for integ and sudo tests (magma dev vs magma_deb)
|
1.0
|
Parallelize Bazel LTE integ tests and sudo tests - - The sudo tests take ca 40m, the LTE integ tests take ca. 1h40m without the sudo tests.
- The setup of the VM does not take very long and thus splitting the workflow into an LTE integ test and a sudo workflow would save the integ test workflow 40m and the sudo test workflow might only take an hour or so.
* split sudo and integ test in two jobs that can run in parallel
* do not create magma dev vm once at the beginning - in the future we might use different vms for integ and sudo tests (magma dev vs magma_deb)
|
test
|
parallelize bazel lte integ tests and sudo tests the sudo tests take ca the lte integ tests take ca without the sudo tests the setup of the vm does not take very long and thus splitting the workflow into an lte integ test and a sudo workflow would save the integ test workflow and the sudo test workflow might only take an hour or so split sudo and integ test in two jobs that can run in parallel do not create magma dev vm once at the beginning in the future we might use different vms for integ and sudo tests magma dev vs magma deb
| 1
|
395,277
| 27,063,670,422
|
IssuesEvent
|
2023-02-13 21:59:52
|
DevelopingSpace/starchart
|
https://api.github.com/repos/DevelopingSpace/starchart
|
closed
|
Blues stack start checklist
|
category: documentation
|
We are having multiple problems with this, so I made a checklist of issues to keep track.
- [x] [Add initial code (issue)](https://github.com/Seneca-CDOT/starchart/issues/7):
- [x] [Add blues stack PR](https://github.com/Seneca-CDOT/starchart/pull/38)
---
- [ ] [Create documentation how to run it (issue)](https://github.com/Seneca-CDOT/starchart/issues/12):
- [x] [Initial documentation started](https://github.com/Seneca-CDOT/starchart/wiki/%5BUnder-construction%5D-Set-up-documentation)
- [x] ~~[Fix a bug with docker and database](https://github.com/Seneca-CDOT/starchart/pull/40) | @Ririio 's setup attempt~~ - more of a database issue rather than blue stack
- [x] [Fix a bug with startup configuration (issue)](https://github.com/Seneca-CDOT/starchart/issues/52) | @shawnyu5 setup attempt
- [x] Update documentation and code until people can reliably setup their projects
|
1.0
|
Blues stack start checklist - We are having multiple problems with this, so I made a checklist of issues to keep track.
- [x] [Add initial code (issue)](https://github.com/Seneca-CDOT/starchart/issues/7):
- [x] [Add blues stack PR](https://github.com/Seneca-CDOT/starchart/pull/38)
---
- [ ] [Create documentation how to run it (issue)](https://github.com/Seneca-CDOT/starchart/issues/12):
- [x] [Initial documentation started](https://github.com/Seneca-CDOT/starchart/wiki/%5BUnder-construction%5D-Set-up-documentation)
- [x] ~~[Fix a bug with docker and database](https://github.com/Seneca-CDOT/starchart/pull/40) | @Ririio 's setup attempt~~ - more of a database issue rather than blue stack
- [x] [Fix a bug with startup configuration (issue)](https://github.com/Seneca-CDOT/starchart/issues/52) | @shawnyu5 setup attempt
- [x] Update documentation and code until people can reliably setup their projects
|
non_test
|
blues stack start checklist we are having multiple problems with this so i made a checklist of issues to keep track ririio s setup attempt more of a database issue rather than blue stack setup attempt update documentation and code until people can reliably setup their projects
| 0
|
326,065
| 27,975,350,915
|
IssuesEvent
|
2023-03-25 14:12:48
|
dudykr/stc
|
https://api.github.com/repos/dudykr/stc
|
opened
|
Fix unit test for `tests/pass-only/typeNarrowing/.seq-1.ts`
|
tsc-unit-test
|
---
Related test: https://github.com/dudykr/stc/blob/main/crates/stc_ts_file_analyzer/tests/pass-only/typeNarrowing/.seq-1.ts
---
This issue is created by sync script.
|
1.0
|
Fix unit test for `tests/pass-only/typeNarrowing/.seq-1.ts` -
---
Related test: https://github.com/dudykr/stc/blob/main/crates/stc_ts_file_analyzer/tests/pass-only/typeNarrowing/.seq-1.ts
---
This issue is created by sync script.
|
test
|
fix unit test for tests pass only typenarrowing seq ts related test this issue is created by sync script
| 1
|
13,410
| 3,332,066,525
|
IssuesEvent
|
2015-11-11 18:29:51
|
t2davis/Squad
|
https://api.github.com/repos/t2davis/Squad
|
opened
|
buddybuild feedback from Mariajfdavis@gmail.com on build #11: I don't live here
|
1.0 BetaTester
|
Feedback from Mariajfdavis@gmail.com : I don't live here
<img src="https://s3-us-west-2.amazonaws.com/buddybuild-screenshots/5642b68257de0f0100c2f1c9/5642f4b857de0f0100c2f1f1/6e996daf-d02a-466b-9de5-b737cbaf1818.jpg" width="33%" height="33%" />
|
1.0
|
buddybuild feedback from Mariajfdavis@gmail.com on build #11: I don't live here - Feedback from Mariajfdavis@gmail.com : I don't live here
<img src="https://s3-us-west-2.amazonaws.com/buddybuild-screenshots/5642b68257de0f0100c2f1c9/5642f4b857de0f0100c2f1f1/6e996daf-d02a-466b-9de5-b737cbaf1818.jpg" width="33%" height="33%" />
|
test
|
buddybuild feedback from mariajfdavis gmail com on build i don t live here feedback from mariajfdavis gmail com i don t live here
| 1
|
174,354
| 13,484,464,994
|
IssuesEvent
|
2020-09-11 06:25:21
|
ProjectBabbler/ebird-api
|
https://api.github.com/repos/ProjectBabbler/ebird-api
|
closed
|
Clean up acceptance tests
|
testing
|
Refactor the acceptance tests so the entire suite can be run using
``` bash
python -m tests.acceptance
```
|
1.0
|
Clean up acceptance tests - Refactor the acceptance tests so the entire suite can be run using
``` bash
python -m tests.acceptance
```
|
test
|
clean up acceptance tests refactor the acceptance tests so the entire suite can be run using bash python m tests acceptance
| 1
|
26,855
| 4,258,146,034
|
IssuesEvent
|
2016-07-11 04:31:20
|
linz/QGIS-AIMS-Plugin
|
https://api.github.com/repos/linz/QGIS-AIMS-Plugin
|
reopened
|
Tighten up security and authentication
|
enhancement priority/high test
|
Would be good to tighten up security and authentication if possible. e.g. not store plain text passwords in users credential stores and at least use hashed passwords. Leave this as a low priority for now until full security risk review has been done.
|
1.0
|
Tighten up security and authentication - Would be good to tighten up security and authentication if possible. e.g. not store plain text passwords in users credential stores and at least use hashed passwords. Leave this as a low priority for now until full security risk review has been done.
|
test
|
tighten up security and authentication would be good to tighten up security and authentication if possible e g not store plain text passwords in users credential stores and at least use hashed passwords leave this as a low priority for now until full security risk review has been done
| 1
|
151,936
| 12,066,325,228
|
IssuesEvent
|
2020-04-16 11:33:27
|
knative/eventing
|
https://api.github.com/repos/knative/eventing
|
closed
|
Conformance tests for channel CRD status requirements
|
area/channels area/test-and-release kind/feature-request
|
**Problem**
Following tasks are created according to the [spec](https://github.com/knative/eventing/blob/master/docs/spec/channel.md).
**Note**: this ticket is only for CRD validation. Values of the fields in the status are to be tested in https://github.com/knative/eventing/issues/2992.
Tests:
- [ ] v1alpha1: Channel CRD MUST have a`status` subresource which contains `address` and
`subscribableStatus.subscribers` (as an array).
- [ ] v1alpha1: Channel CRD SHOULD have a`status` subresource which contains `observedGeneration` and
`conditions` (as an array). If they don't exist, report them.
- [ ] v1beta1: Channel CRD MUST have a`status` subresource which contains `address` and
`subscribers` (as an array).
- [ ] v1beta1: Channel CRD SHOULD have a`status` subresource which contains `observedGeneration` and
`conditions` (as an array). If they don't exist, report them.
Note: As there's no way of knowing what channel spec version the channel supports, instantiate a channel and then check the annotation `messaging.knative.dev/subscribable` in the channel instance . There's more info for this in https://github.com/knative/eventing/issues/2987.
Note 2: Reporting the missing optional features is perhaps something done in serving conformance tests.
**[Persona:](https://github.com/knative/eventing/blob/master/docs/personas.md)**
System Integrator, Contributors
**Exit Criteria**
Test required behavior of channel, maybe report on optional capabilities.
**Time Estimate (optional):**
2d
|
1.0
|
Conformance tests for channel CRD status requirements - **Problem**
Following tasks are created according to the [spec](https://github.com/knative/eventing/blob/master/docs/spec/channel.md).
**Note**: this ticket is only for CRD validation. Values of the fields in the status are to be tested in https://github.com/knative/eventing/issues/2992.
Tests:
- [ ] v1alpha1: Channel CRD MUST have a`status` subresource which contains `address` and
`subscribableStatus.subscribers` (as an array).
- [ ] v1alpha1: Channel CRD SHOULD have a`status` subresource which contains `observedGeneration` and
`conditions` (as an array). If they don't exist, report them.
- [ ] v1beta1: Channel CRD MUST have a`status` subresource which contains `address` and
`subscribers` (as an array).
- [ ] v1beta1: Channel CRD SHOULD have a`status` subresource which contains `observedGeneration` and
`conditions` (as an array). If they don't exist, report them.
Note: As there's no way of knowing what channel spec version the channel supports, instantiate a channel and then check the annotation `messaging.knative.dev/subscribable` in the channel instance . There's more info for this in https://github.com/knative/eventing/issues/2987.
Note 2: Reporting the missing optional features is perhaps something done in serving conformance tests.
**[Persona:](https://github.com/knative/eventing/blob/master/docs/personas.md)**
System Integrator, Contributors
**Exit Criteria**
Test required behavior of channel, maybe report on optional capabilities.
**Time Estimate (optional):**
2d
|
test
|
conformance tests for channel crd status requirements problem following tasks are created according to the note this ticket is only for crd validation values of the fields in the status are to be tested in tests channel crd must have a status subresource which contains address and subscribablestatus subscribers as an array channel crd should have a status subresource which contains observedgeneration and conditions as an array if they don t exist report them channel crd must have a status subresource which contains address and subscribers as an array channel crd should have a status subresource which contains observedgeneration and conditions as an array if they don t exist report them note as there s no way of knowing what channel spec version the channel supports instantiate a channel and then check the annotation messaging knative dev subscribable in the channel instance there s more info for this in note reporting the missing optional features is perhaps something done in serving conformance tests system integrator contributors exit criteria test required behavior of channel maybe report on optional capabilities time estimate optional
| 1
|
97,001
| 8,639,666,745
|
IssuesEvent
|
2018-11-23 20:37:19
|
w3c/svgwg
|
https://api.github.com/repos/w3c/svgwg
|
closed
|
Add non-attached elements to non-rendered elements
|
Needs tests Rendering Model chapter
|
From the current spec text, it is not clear that non-attached elements count as non-rendered elements.
https://www.w3.org/TR/SVG2/render.html#Rendered-vs-NonRendered
|
1.0
|
Add non-attached elements to non-rendered elements - From the current spec text, it is not clear that non-attached elements count as non-rendered elements.
https://www.w3.org/TR/SVG2/render.html#Rendered-vs-NonRendered
|
test
|
add non attached elements to non rendered elements from the current spec text it is not clear that non attached elements count as non rendered elements
| 1
|
67,007
| 3,265,290,622
|
IssuesEvent
|
2015-10-22 15:38:34
|
giseislab/gismotools
|
https://api.github.com/repos/giseislab/gismotools
|
closed
|
correlation/conv and deconv not functional
|
auto-migrated Priority-Low Type-Enhancement Usability
|
```
These convolution/deconvolution routines were committed prematurely and are
not yet functional. How to fix it? I am not sure - probably stare at it for
hours.
Please use labels and text to provide additional information.
```
Original issue reported on code.google.com by `mew...@gmail.com` on 23 Jan 2010 at 8:26
|
1.0
|
correlation/conv and deconv not functional - ```
These convolution/deconvolution routines were committed prematurely and are
not yet functional. How to fix it? I am not sure - probably stare at it for
hours.
Please use labels and text to provide additional information.
```
Original issue reported on code.google.com by `mew...@gmail.com` on 23 Jan 2010 at 8:26
|
non_test
|
correlation conv and deconv not functional these convolution deconvolution routines were committed prematurely and are not yet functional how to fix it i am not sure probably stare at it for hours please use labels and text to provide additional information original issue reported on code google com by mew gmail com on jan at
| 0
|
222,557
| 17,461,540,850
|
IssuesEvent
|
2021-08-06 11:12:28
|
jenkinsci/ecutest-plugin
|
https://api.github.com/repos/jenkinsci/ecutest-plugin
|
closed
|
Ensure ECU-TEST 2021.2 compatibility
|
feature ecu-test
|
<!--
For reporting issues containing NDA relevant information please use our [TraceTronic Support Center](https://support.tracetronic.com).
-->
**Describe the feature request**
Ensure compatibility with ECU-TEST 2021.2 (especially COM API) while retaining backward compatibility with ECU-TEST 7.x and above.
**Additional context**
Release date was on 30..07.2021.
|
1.0
|
Ensure ECU-TEST 2021.2 compatibility - <!--
For reporting issues containing NDA relevant information please use our [TraceTronic Support Center](https://support.tracetronic.com).
-->
**Describe the feature request**
Ensure compatibility with ECU-TEST 2021.2 (especially COM API) while retaining backward compatibility with ECU-TEST 7.x and above.
**Additional context**
Release date was on 30..07.2021.
|
test
|
ensure ecu test compatibility for reporting issues containing nda relevant information please use our describe the feature request ensure compatibility with ecu test especially com api while retaining backward compatibility with ecu test x and above additional context release date was on
| 1
|
9,409
| 3,039,594,071
|
IssuesEvent
|
2015-08-07 09:58:36
|
fifthweek/fifthweek-web
|
https://api.github.com/repos/fifthweek/fifthweek-web
|
closed
|
Route tests in e2e tests instead of unit tests
|
SP-3 testing
|
Acceptance criteria:
- Every route change is tested in e2e.
- No route/`$state` testing is done from unit tests.
- State mock js is removed (originally used for unit testing $state)
|
1.0
|
Route tests in e2e tests instead of unit tests - Acceptance criteria:
- Every route change is tested in e2e.
- No route/`$state` testing is done from unit tests.
- State mock js is removed (originally used for unit testing $state)
|
test
|
route tests in tests instead of unit tests acceptance criteria every route change is tested in no route state testing is done from unit tests state mock js is removed originally used for unit testing state
| 1
|
328,487
| 24,186,861,197
|
IssuesEvent
|
2022-09-23 14:00:08
|
zephyrproject-rtos/zephyr
|
https://api.github.com/repos/zephyrproject-rtos/zephyr
|
opened
|
Documentation: Broken links in the documentation at docs.zephyrproject.org/
|
bug area: Documentation
|
**Describe the bug**
Using a linkchecker (https://github.com/linkchecker/linkchecker) I've been able to produce a list of broken URLs/links found the in documentation.
The linkchecker was run with `linkchecker --no-robots --check-extern --no-warnings`.
I've run it twice: Once locally on locally built and hosted documentation (SHA: `dca9c2b165b92e90d38a5002ae7e6ad013daf04d`), and once on the actual documentation found at https://docs.zephyrproject.org.
The result for the local run is attached here.
The result for the remote run is still being compiled, and will be added later.
**To Reproduce**
Steps to reproduce the behavior:
1. Download and install linkchecker
2. Run with `linkchecker --no-robots --check-extern --no-warnings https://docs.zephyrproject.org.`
**Expected behavior**
Ideally no URLs should return an error.
**Impact**
Annoyance or missing information.
**Logs and console output**
See attached files
**Environment (please complete the following information):**
- Commit SHA or Version used: `dca9c2b165b92e90d38a5002ae7e6ad013daf04d`
**Additional context**
See attached files
To make the links in the txt-file directly usable, I would suggest do a simple search-and-replace of `http://localhost:9000` to `https://docs.zephyrproject.org`
File from local run (only on latest docs) containing 119 `404`s:
[linkchecker_local.txt](https://github.com/zephyrproject-rtos/zephyr/files/9634256/linkchecker_local.txt)
|
1.0
|
Documentation: Broken links in the documentation at docs.zephyrproject.org/ - **Describe the bug**
Using a linkchecker (https://github.com/linkchecker/linkchecker) I've been able to produce a list of broken URLs/links found the in documentation.
The linkchecker was run with `linkchecker --no-robots --check-extern --no-warnings`.
I've run it twice: Once locally on locally built and hosted documentation (SHA: `dca9c2b165b92e90d38a5002ae7e6ad013daf04d`), and once on the actual documentation found at https://docs.zephyrproject.org.
The result for the local run is attached here.
The result for the remote run is still being compiled, and will be added later.
**To Reproduce**
Steps to reproduce the behavior:
1. Download and install linkchecker
2. Run with `linkchecker --no-robots --check-extern --no-warnings https://docs.zephyrproject.org.`
**Expected behavior**
Ideally no URLs should return an error.
**Impact**
Annoyance or missing information.
**Logs and console output**
See attached files
**Environment (please complete the following information):**
- Commit SHA or Version used: `dca9c2b165b92e90d38a5002ae7e6ad013daf04d`
**Additional context**
See attached files
To make the links in the txt-file directly usable, I would suggest do a simple search-and-replace of `http://localhost:9000` to `https://docs.zephyrproject.org`
File from local run (only on latest docs) containing 119 `404`s:
[linkchecker_local.txt](https://github.com/zephyrproject-rtos/zephyr/files/9634256/linkchecker_local.txt)
|
non_test
|
documentation broken links in the documentation at docs zephyrproject org describe the bug using a linkchecker i ve been able to produce a list of broken urls links found the in documentation the linkchecker was run with linkchecker no robots check extern no warnings i ve run it twice once locally on locally built and hosted documentation sha and once on the actual documentation found at the result for the local run is attached here the result for the remote run is still being compiled and will be added later to reproduce steps to reproduce the behavior download and install linkchecker run with linkchecker no robots check extern no warnings expected behavior ideally no urls should return an error impact annoyance or missing information logs and console output see attached files environment please complete the following information commit sha or version used additional context see attached files to make the links in the txt file directly usable i would suggest do a simple search and replace of to file from local run only on latest docs containing s
| 0
|
102,502
| 21,993,261,317
|
IssuesEvent
|
2022-05-26 01:46:52
|
pulumi/pulumi
|
https://api.github.com/repos/pulumi/pulumi
|
opened
|
`pulumi convert` support for string, array, non-Output properties
|
kind/bug area/codegen
|
When running `pulumi convert` on a YAML program like the one below, the generated Go is invalid as `ctx.Export` expects an Output:
```yaml
name: random
runtime: yaml
outputs:
strVar: "foo"
arrVar:
- fizz
- buzz
readme:
Fn::ReadFile: ./Pulumi.README.md
```
```go
package main
import (
"io/ioutil"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func readFileOrPanic(path string) pulumi.StringPtrInput {
data, err := ioutil.ReadFile(path)
if err != nil {
panic(err.Error())
}
return pulumi.String(string(data))
}
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
ctx.Export("strVar", "foo")
ctx.Export("arrVar", []string{
"fizz",
"buzz",
})
ctx.Export("readme", readFileOrPanic("./Pulumi.README.md"))
return nil
})
}
```
|
1.0
|
`pulumi convert` support for string, array, non-Output properties - When running `pulumi convert` on a YAML program like the one below, the generated Go is invalid as `ctx.Export` expects an Output:
```yaml
name: random
runtime: yaml
outputs:
strVar: "foo"
arrVar:
- fizz
- buzz
readme:
Fn::ReadFile: ./Pulumi.README.md
```
```go
package main
import (
"io/ioutil"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func readFileOrPanic(path string) pulumi.StringPtrInput {
data, err := ioutil.ReadFile(path)
if err != nil {
panic(err.Error())
}
return pulumi.String(string(data))
}
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
ctx.Export("strVar", "foo")
ctx.Export("arrVar", []string{
"fizz",
"buzz",
})
ctx.Export("readme", readFileOrPanic("./Pulumi.README.md"))
return nil
})
}
```
|
non_test
|
pulumi convert support for string array non output properties when running pulumi convert on a yaml program like the one below the generated go is invalid as ctx export expects an output yaml name random runtime yaml outputs strvar foo arrvar fizz buzz readme fn readfile pulumi readme md go package main import io ioutil github com pulumi pulumi sdk go pulumi func readfileorpanic path string pulumi stringptrinput data err ioutil readfile path if err nil panic err error return pulumi string string data func main pulumi run func ctx pulumi context error ctx export strvar foo ctx export arrvar string fizz buzz ctx export readme readfileorpanic pulumi readme md return nil
| 0
|
814,123
| 30,488,726,076
|
IssuesEvent
|
2023-07-18 05:52:09
|
Memmy-App/memmy
|
https://api.github.com/repos/Memmy-App/memmy
|
closed
|
Context Menu for Posts from Post Feed views
|
enhancement medium priority
|
Please add the ability to open the post context menu from the post feed view.
This should be accessible by long pressing and also a 3-dot menu in the upper right of the post card.
The context menu should contain the following actions…
1. Upvote
2. Downvote
3. Save
4. Hide
5. Report
6. Block User
7. Block Community
8. Subscribe to Community
|
1.0
|
Context Menu for Posts from Post Feed views - Please add the ability to open the post context menu from the post feed view.
This should be accessible by long pressing and also a 3-dot menu in the upper right of the post card.
The context menu should contain the following actions…
1. Upvote
2. Downvote
3. Save
4. Hide
5. Report
6. Block User
7. Block Community
8. Subscribe to Community
|
non_test
|
context menu for posts from post feed views please add the ability to open the post context menu from the post feed view this should be accessible by long pressing and also a dot menu in the upper right of the post card the context menu should contain the following actions… upvote downvote save hide report block user block community subscribe to community
| 0
|
86,952
| 17,108,280,602
|
IssuesEvent
|
2021-07-09 22:03:34
|
aws/aws-cdk
|
https://api.github.com/repos/aws/aws-cdk
|
closed
|
(aws-codepipeline): ActionDeclaration - Support CombineArtifacts configuration when BatchEnabled is enable
|
@aws-cdk/aws-codepipeline effort/small feature-request good first issue p2
|
See this [doc](https://docs.aws.amazon.com/codebuild/latest/userguide/sample-pipeline-batch.html) which says
> To enable batch builds in CodePipeline, set the BatchEnabled parameter of the configuration object to true. To combine the build artifacts into the same location, set the CombineArtifacts parameter of the configuration object to true.
The configuration object it is referring to is [this](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-codepipeline-pipeline-stages-actions.html#cfn-codepipeline-pipeline-stages-actions-configuration).
It is not possible right now to provide this on the [CodeBuildAction](https://docs.aws.amazon.com/cdk/api/latest/docs/@aws-cdk_aws-codepipeline-actions.CodeBuildAction.html)
### Use Case
We need to add a combine artifacts for batch code build action to our pipeline.
### Proposed Solution
```javascript
const codebuildAction = new codepipelineActions.CodeBuildAction({
actionName: 'Build',
project: createCodeBuildProject(),
input,
outputs,
batchEnabled: true,
combineBatchBuildArtifacts: true // something like this
})
```
would set the `CombineArtifacts` and property on Configuration to true. The implementation should happen somewhere around this [place](https://github.com/aws/aws-cdk/blob/master/packages/%40aws-cdk/aws-codepipeline-actions/lib/codebuild/build-action.ts#L216).
### Other
<!--
e.g. detailed explanation, stacktraces, related issues, suggestions on how to fix,
links for us to have context, eg. associated pull-request, stackoverflow, slack, etc
-->
* [ ] :wave: I may be able to implement this feature request
* [ ] :warning: This feature might incur a breaking change
---
This is a :rocket: Feature Request
|
1.0
|
(aws-codepipeline): ActionDeclaration - Support CombineArtifacts configuration when BatchEnabled is enable - See this [doc](https://docs.aws.amazon.com/codebuild/latest/userguide/sample-pipeline-batch.html) which says
> To enable batch builds in CodePipeline, set the BatchEnabled parameter of the configuration object to true. To combine the build artifacts into the same location, set the CombineArtifacts parameter of the configuration object to true.
The configuration object it is referring to is [this](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-codepipeline-pipeline-stages-actions.html#cfn-codepipeline-pipeline-stages-actions-configuration).
It is not possible right now to provide this on the [CodeBuildAction](https://docs.aws.amazon.com/cdk/api/latest/docs/@aws-cdk_aws-codepipeline-actions.CodeBuildAction.html)
### Use Case
We need to add a combine artifacts for batch code build action to our pipeline.
### Proposed Solution
```javascript
const codebuildAction = new codepipelineActions.CodeBuildAction({
actionName: 'Build',
project: createCodeBuildProject(),
input,
outputs,
batchEnabled: true,
combineBatchBuildArtifacts: true // something like this
})
```
would set the `CombineArtifacts` and property on Configuration to true. The implementation should happen somewhere around this [place](https://github.com/aws/aws-cdk/blob/master/packages/%40aws-cdk/aws-codepipeline-actions/lib/codebuild/build-action.ts#L216).
### Other
<!--
e.g. detailed explanation, stacktraces, related issues, suggestions on how to fix,
links for us to have context, eg. associated pull-request, stackoverflow, slack, etc
-->
* [ ] :wave: I may be able to implement this feature request
* [ ] :warning: This feature might incur a breaking change
---
This is a :rocket: Feature Request
|
non_test
|
aws codepipeline actiondeclaration support combineartifacts configuration when batchenabled is enable see this which says to enable batch builds in codepipeline set the batchenabled parameter of the configuration object to true to combine the build artifacts into the same location set the combineartifacts parameter of the configuration object to true the configuration object it is referring to is it is not possible right now to provide this on the use case we need to add a combine artifacts for batch code build action to our pipeline proposed solution javascript const codebuildaction new codepipelineactions codebuildaction actionname build project createcodebuildproject input outputs batchenabled true combinebatchbuildartifacts true something like this would set the combineartifacts and property on configuration to true the implementation should happen somewhere around this other e g detailed explanation stacktraces related issues suggestions on how to fix links for us to have context eg associated pull request stackoverflow slack etc wave i may be able to implement this feature request warning this feature might incur a breaking change this is a rocket feature request
| 0
|
286,240
| 21,568,394,949
|
IssuesEvent
|
2022-05-02 03:51:44
|
Divested-Mobile/Mull-Fenix
|
https://api.github.com/repos/Divested-Mobile/Mull-Fenix
|
closed
|
Youtube videos do not start to play (and https issue)
|
documentation
|
Today, i have tried to play a Youtube video in the browser. If i click the play button, the video loads but didn't play. I don't know, if this is because of some setting from arkenfox.
Some similar thing but unrelated to youtube, is the following: I have a url not protected by https. Instead of this it is a standard http url. I can try to proceed and load the url, but click the dedicated button does nothing. Also when i open a https url with self generated certificate, i have such a button to allow opening of this url. If i click the button to allow, nothing happens. If both issues are not related to each other, please let me know, then we can create 2 separate issues, but for me it feels like the same issue.
I have tried all the above things with Fennec from F-Droid. There i have no such issues.
If this is a arkenfox issue, it would be nice to disable optionally some of the arkenfox settings.
|
1.0
|
Youtube videos do not start to play (and https issue) - Today, i have tried to play a Youtube video in the browser. If i click the play button, the video loads but didn't play. I don't know, if this is because of some setting from arkenfox.
Some similar thing but unrelated to youtube, is the following: I have a url not protected by https. Instead of this it is a standard http url. I can try to proceed and load the url, but click the dedicated button does nothing. Also when i open a https url with self generated certificate, i have such a button to allow opening of this url. If i click the button to allow, nothing happens. If both issues are not related to each other, please let me know, then we can create 2 separate issues, but for me it feels like the same issue.
I have tried all the above things with Fennec from F-Droid. There i have no such issues.
If this is a arkenfox issue, it would be nice to disable optionally some of the arkenfox settings.
|
non_test
|
youtube videos do not start to play and https issue today i have tried to play a youtube video in the browser if i click the play button the video loads but didn t play i don t know if this is because of some setting from arkenfox some similar thing but unrelated to youtube is the following i have a url not protected by https instead of this it is a standard http url i can try to proceed and load the url but click the dedicated button does nothing also when i open a https url with self generated certificate i have such a button to allow opening of this url if i click the button to allow nothing happens if both issues are not related to each other please let me know then we can create separate issues but for me it feels like the same issue i have tried all the above things with fennec from f droid there i have no such issues if this is a arkenfox issue it would be nice to disable optionally some of the arkenfox settings
| 0
|
16,675
| 3,549,388,149
|
IssuesEvent
|
2016-01-20 17:48:01
|
mesosphere/kubernetes-mesos
|
https://api.github.com/repos/mesosphere/kubernetes-mesos
|
opened
|
SchedulerPredicates: validates that NodeSelector is respected if not matching
|
class/bug tests/conformance
|
https://teamcity.mesosphere.io/viewLog.html?tab=buildLog&logTab=tree&filter=debug&expand=all&buildId=105601#_focus=3095
```
[19:14:17][Step 7/7] SchedulerPredicates [Serial]
[19:14:17][Step 7/7] validates that NodeSelector is respected if not matching [Conformance]
[19:14:17][Step 7/7] /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/scheduler_predicates.go:393
[19:14:17][Step 7/7] [BeforeEach] SchedulerPredicates [Serial]
[19:14:17][Step 7/7] /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework.go:68
[19:14:17][Step 7/7] STEP: Creating a kubernetes client
[19:14:17][Step 7/7] Jan 15 00:14:17.809: INFO: >>> testContext.KubeConfig: /root/.kube/config
[19:14:17][Step 7/7]
[19:14:17][Step 7/7] STEP: Building a namespace api object
[19:14:17][Step 7/7] Jan 15 00:14:17.812: INFO: Waiting up to 2m0s for service account default to be provisioned in ns e2e-tests-sched-pred-coi56
[19:14:17][Step 7/7] Jan 15 00:14:17.828: INFO: Service account default in ns e2e-tests-sched-pred-coi56 had 0 secrets, ignoring for 2s: <nil>
[19:14:19][Step 7/7] Jan 15 00:14:19.830: INFO: Service account default in ns e2e-tests-sched-pred-coi56 with secrets found. (2.018097501s)
[19:14:19][Step 7/7] STEP: Waiting for a default service account to be provisioned in namespace
[19:14:19][Step 7/7] Jan 15 00:14:19.830: INFO: Waiting up to 2m0s for service account default to be provisioned in ns e2e-tests-sched-pred-coi56
[19:14:19][Step 7/7] Jan 15 00:14:19.831: INFO: Service account default in ns e2e-tests-sched-pred-coi56 with secrets found. (1.023196ms)
[19:14:19][Step 7/7] [BeforeEach] SchedulerPredicates [Serial]
[19:14:19][Step 7/7] /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/scheduler_predicates.go:198
[19:14:19][Step 7/7] [It] validates that NodeSelector is respected if not matching [Conformance]
[19:14:19][Step 7/7] /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/scheduler_predicates.go:393
[19:14:19][Step 7/7] STEP: Trying to schedule Pod with nonempty NodeSelector.
[19:14:19][Step 7/7] Jan 15 00:14:19.839: INFO: Sleeping 10 seconds and crossing our fingers that scheduler will run in that time.
[19:14:29][Step 7/7] [AfterEach] SchedulerPredicates [Serial]
[19:14:29][Step 7/7] /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/scheduler_predicates.go:190
[19:14:29][Step 7/7] [AfterEach] SchedulerPredicates [Serial]
[19:14:29][Step 7/7] /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework.go:69
[19:14:29][Step 7/7] STEP: Collecting events from namespace "e2e-tests-sched-pred-coi56".
[19:14:29][Step 7/7] Jan 15 00:14:29.863: INFO: event for restricted-pod: {scheduler } FailedScheduling: Error scheduling: No suitable offers for pod/task
[19:14:29][Step 7/7] Jan 15 00:14:29.866: INFO: POD NODE PHASE GRACE CONDITIONS
[19:14:29][Step 7/7] Jan 15 00:14:29.866: INFO: restricted-pod Pending []
[19:14:29][Step 7/7] Jan 15 00:14:29.866: INFO: kube-dns-v10-1w8zl 172.17.0.10 Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-01-14 23:58:43 +0000 UTC }]
[19:14:29][Step 7/7] Jan 15 00:14:29.866: INFO: kube-ui-v4-hp9km 172.17.0.7 Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-01-14 23:58:21 +0000 UTC }]
[19:14:29][Step 7/7] Jan 15 00:14:29.866: INFO:
[19:14:29][Step 7/7] Jan 15 00:14:29.868: INFO:
[19:14:29][Step 7/7] Logging node info for node 172.17.0.10
[19:14:29][Step 7/7] Jan 15 00:14:29.870: INFO: Node Info: &{{ } {172.17.0.10 /api/v1/nodes/172.17.0.10 a6db09dd-bb1a-11e5-99da-0242ac110006 1358 0 2016-01-14 23:58:04 +0000 UTC <nil> <nil> map[kubernetes.io/hostname:172.17.0.10 k8s.mesosphere.io/attribute-gen:2012 k8s.mesosphere.io/attribute-rack:2] map[k8s.mesosphere.io/executorId:b8ea8e7042075f9a_k8sm-executor k8s.mesosphere.io/executorResources:CgRjcHVzEAAaCQkAAAAAAADwPzIBKg==,CgNtZW0QABoJCQAAAAAAAGBAMgEq]} { 172.17.0.10 false} {map[memory:{1879048192.000 BinarySI} pods:{40.000 DecimalSI} cpu:{5.000 DecimalSI}] map[cpu:{5.000 DecimalSI} memory:{1879048192.000 BinarySI} pods:{40.000 DecimalSI}] Pending [{Ready True 2016-01-15 00:14:26 +0000 UTC 0001-01-01 00:00:00 +0000 UTC KubeletReady kubelet is posting ready status} {OutOfDisk False 2016-01-15 00:14:26 +0000 UTC 2016-01-14 23:58:13 +0000 UTC KubeletHasSufficientDisk kubelet has sufficient disk space available}] [{LegacyHostIP 172.17.0.10} {InternalIP 172.17.0.10}] {{10250}} { EC2EC3C2-0A15-BB49-1F80-8085C3189D05 e0b2293d-9331-4bcc-884c-57753777d9fe 3.19.0-39-generic Ubuntu 14.04.3 LTS docker://1.8.2 v1.2.0-alpha.6.10+b7b6c4251e21b7 v1.2.0-alpha.6.10+b7b6c4251e21b7} [{[gcr.io/google_containers/kube2sky:1.12] 24482187} {[gcr.io/google_containers/mounttest:0.5] 1718853} {[gcr.io/google_containers/skydns:2015-10-13-8c72f8c] 40547562} {[gcr.io/google_containers/pause:2.0] 350164} {[gcr.io/google_containers/portforwardtester:1.0] 2296329} {[gcr.io/google_containers/nettest:1.6] 10374838} {[gcr.io/google_containers/exechealthz:1.0] 7095869} {[gcr.io/google_containers/etcd:2.0.9] 12819040} {[gcr.io/google_containers/update-demo:nautilus] 4555533} {[gcr.io/google_containers/busybox:latest] 2429728}]}}
[19:14:29][Step 7/7] Jan 15 00:14:29.870: INFO:
[19:14:29][Step 7/7] Logging kubelet events for node 172.17.0.10
[19:14:29][Step 7/7] Jan 15 00:14:29.874: INFO:
[19:14:29][Step 7/7] Logging pods the kubelet thinks is on node 172.17.0.10
[19:14:29][Step 7/7] Jan 15 00:14:29.878: INFO: kube-dns-v10-1w8zl started at <nil> (0 container statuses recorded)
[19:14:30][Step 7/7] Jan 15 00:14:30.045: INFO: ERROR kubelet_docker_errors{operation_type="inspect_image"} => 10 @[0]
[19:14:30][Step 7/7] Jan 15 00:14:30.045: INFO: ERROR kubelet_docker_errors{operation_type="stop_container"} => 16 @[0]
[19:14:30][Step 7/7] Jan 15 00:14:30.045: INFO:
[19:14:30][Step 7/7] Latency metrics for node 172.17.0.10
[19:14:30][Step 7/7] Jan 15 00:14:30.045: INFO: {Operation:stop_container Method:docker_operations_latency_microseconds Quantile:0.99 Latency:25.021103s}
[19:14:30][Step 7/7] Jan 15 00:14:30.045: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.99 Latency:18.290728s}
[19:14:30][Step 7/7] Jan 15 00:14:30.045: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.9 Latency:14.378835s}
[19:14:30][Step 7/7] Jan 15 00:14:30.045: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.5 Latency:12.101871s}
[19:14:30][Step 7/7] Jan 15 00:14:30.045: INFO:
[19:14:30][Step 7/7] Logging node info for node 172.17.0.7
[19:14:30][Step 7/7] Jan 15 00:14:30.212: INFO: Node Info: &{{ } {172.17.0.7 /api/v1/nodes/172.17.0.7 a4f953ed-bb1a-11e5-99da-0242ac110006 1354 0 2016-01-14 23:58:01 +0000 UTC <nil> <nil> map[k8s.mesosphere.io/attribute-gen:2011 k8s.mesosphere.io/attribute-rack:1 kubernetes.io/e2e-259d3f2d-bb1b-11e5-8802-0242ac110002:42 kubernetes.io/hostname:172.17.0.7] map[k8s.mesosphere.io/executorId:b8ea8e7042075f9a_k8sm-executor k8s.mesosphere.io/executorResources:CgRjcHVzEAAaCQkAAAAAAADwPzIBKg==,CgNtZW0QABoJCQAAAAAAAGBAMgEq]} { 172.17.0.7 false} {map[memory:{1207959552.000 BinarySI} pods:{40.000 DecimalSI} cpu:{3.000 DecimalSI}] map[memory:{1207959552.000 BinarySI} pods:{40.000 DecimalSI} cpu:{3.000 DecimalSI}] Pending [{Ready True 2016-01-15 00:14:21 +0000 UTC 0001-01-01 00:00:00 +0000 UTC KubeletReady kubelet is posting ready status} {OutOfDisk False 2016-01-15 00:14:21 +0000 UTC 2016-01-14 23:58:08 +0000 UTC KubeletHasSufficientDisk kubelet has sufficient disk space available}] [{LegacyHostIP 172.17.0.7} {InternalIP 172.17.0.7}] {{10250}} { EC2EC3C2-0A15-BB49-1F80-8085C3189D05 e0b2293d-9331-4bcc-884c-57753777d9fe 3.19.0-39-generic Ubuntu 14.04.3 LTS docker://1.8.2 v1.2.0-alpha.6.10+b7b6c4251e21b7 v1.2.0-alpha.6.10+b7b6c4251e21b7} [{[redis:latest] 151265773} {[nginx:latest] 133816162} {[gcr.io/google_containers/kube-ui:v4] 5676927} {[gcr.io/google_containers/mounttest:0.6] 2084693} {[gcr.io/google_containers/mounttest-user:0.3] 1718853} {[gcr.io/google_containers/mounttest:0.5] 1718853} {[gcr.io/google_containers/pause:2.0] 350164} {[gcr.io/google_containers/porter:cd5cb5791ebaa8641955f0e8c2a9bed669b1eaab] 5010921} {[gcr.io/google_containers/portforwardtester:1.0] 2296329} {[gcr.io/google_containers/update-demo:nautilus] 4555533} {[gcr.io/google_containers/nginx:1.7.9] 91641000} {[gcr.io/google_containers/test-webserver:latest] 4534272}]}}
[19:14:30][Step 7/7] Jan 15 00:14:30.212: INFO:
[19:14:30][Step 7/7] Logging kubelet events for node 172.17.0.7
[19:14:30][Step 7/7] Jan 15 00:14:30.412: INFO:
[19:14:30][Step 7/7] Logging pods the kubelet thinks is on node 172.17.0.7
[19:14:30][Step 7/7] Jan 15 00:14:30.614: INFO: kube-ui-v4-hp9km started at <nil> (0 container statuses recorded)
[19:14:30][Step 7/7] Jan 15 00:14:30.831: INFO: ERROR kubelet_docker_errors{operation_type="inspect_image"} => 12 @[0]
[19:14:30][Step 7/7] Jan 15 00:14:30.831: INFO: ERROR kubelet_docker_errors{operation_type="logs"} => 1 @[0]
[19:14:30][Step 7/7] Jan 15 00:14:30.831: INFO: ERROR kubelet_docker_errors{operation_type="stop_container"} => 21 @[0]
[19:14:30][Step 7/7] Jan 15 00:14:30.831: INFO:
[19:14:30][Step 7/7] Latency metrics for node 172.17.0.7
[19:14:30][Step 7/7] Jan 15 00:14:30.831: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.9 Latency:22.126055s}
[19:14:30][Step 7/7] Jan 15 00:14:30.831: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.99 Latency:22.126055s}
[19:14:30][Step 7/7] Jan 15 00:14:30.831: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.5 Latency:12.68052s}
[19:14:30][Step 7/7] Jan 15 00:14:30.831: INFO: Waiting up to 1m0s for all nodes to be ready
[19:14:31][Step 7/7] STEP: Destroying namespace "e2e-tests-sched-pred-coi56" for this suite.
[19:14:31][Step 7/7]
[19:14:31][Step 7/7] • Failure [13.802 seconds]
[19:14:31][Step 7/7] SchedulerPredicates [Serial]
[19:14:31][Step 7/7] /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/scheduler_predicates.go:473
[19:14:31][Step 7/7] validates that NodeSelector is respected if not matching [Conformance] [It]
[19:14:31][Step 7/7] /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/scheduler_predicates.go:393
[19:14:31][Step 7/7]
[19:14:31][Step 7/7]
[19:14:31][Step 7/7] Expected
[19:14:31][Step 7/7] <[]api.Event | len:0, cap:0>: []
[19:14:31][Step 7/7] not to be empty
[19:14:31][Step 7/7]
[19:14:31][Step 7/7] /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/scheduler_predicates.go:140
```
|
1.0
|
SchedulerPredicates: validates that NodeSelector is respected if not matching - https://teamcity.mesosphere.io/viewLog.html?tab=buildLog&logTab=tree&filter=debug&expand=all&buildId=105601#_focus=3095
```
[19:14:17][Step 7/7] SchedulerPredicates [Serial]
[19:14:17][Step 7/7] validates that NodeSelector is respected if not matching [Conformance]
[19:14:17][Step 7/7] /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/scheduler_predicates.go:393
[19:14:17][Step 7/7] [BeforeEach] SchedulerPredicates [Serial]
[19:14:17][Step 7/7] /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework.go:68
[19:14:17][Step 7/7] STEP: Creating a kubernetes client
[19:14:17][Step 7/7] Jan 15 00:14:17.809: INFO: >>> testContext.KubeConfig: /root/.kube/config
[19:14:17][Step 7/7]
[19:14:17][Step 7/7] STEP: Building a namespace api object
[19:14:17][Step 7/7] Jan 15 00:14:17.812: INFO: Waiting up to 2m0s for service account default to be provisioned in ns e2e-tests-sched-pred-coi56
[19:14:17][Step 7/7] Jan 15 00:14:17.828: INFO: Service account default in ns e2e-tests-sched-pred-coi56 had 0 secrets, ignoring for 2s: <nil>
[19:14:19][Step 7/7] Jan 15 00:14:19.830: INFO: Service account default in ns e2e-tests-sched-pred-coi56 with secrets found. (2.018097501s)
[19:14:19][Step 7/7] STEP: Waiting for a default service account to be provisioned in namespace
[19:14:19][Step 7/7] Jan 15 00:14:19.830: INFO: Waiting up to 2m0s for service account default to be provisioned in ns e2e-tests-sched-pred-coi56
[19:14:19][Step 7/7] Jan 15 00:14:19.831: INFO: Service account default in ns e2e-tests-sched-pred-coi56 with secrets found. (1.023196ms)
[19:14:19][Step 7/7] [BeforeEach] SchedulerPredicates [Serial]
[19:14:19][Step 7/7] /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/scheduler_predicates.go:198
[19:14:19][Step 7/7] [It] validates that NodeSelector is respected if not matching [Conformance]
[19:14:19][Step 7/7] /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/scheduler_predicates.go:393
[19:14:19][Step 7/7] STEP: Trying to schedule Pod with nonempty NodeSelector.
[19:14:19][Step 7/7] Jan 15 00:14:19.839: INFO: Sleeping 10 seconds and crossing our fingers that scheduler will run in that time.
[19:14:29][Step 7/7] [AfterEach] SchedulerPredicates [Serial]
[19:14:29][Step 7/7] /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/scheduler_predicates.go:190
[19:14:29][Step 7/7] [AfterEach] SchedulerPredicates [Serial]
[19:14:29][Step 7/7] /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework.go:69
[19:14:29][Step 7/7] STEP: Collecting events from namespace "e2e-tests-sched-pred-coi56".
[19:14:29][Step 7/7] Jan 15 00:14:29.863: INFO: event for restricted-pod: {scheduler } FailedScheduling: Error scheduling: No suitable offers for pod/task
[19:14:29][Step 7/7] Jan 15 00:14:29.866: INFO: POD NODE PHASE GRACE CONDITIONS
[19:14:29][Step 7/7] Jan 15 00:14:29.866: INFO: restricted-pod Pending []
[19:14:29][Step 7/7] Jan 15 00:14:29.866: INFO: kube-dns-v10-1w8zl 172.17.0.10 Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-01-14 23:58:43 +0000 UTC }]
[19:14:29][Step 7/7] Jan 15 00:14:29.866: INFO: kube-ui-v4-hp9km 172.17.0.7 Running [{Ready True 0001-01-01 00:00:00 +0000 UTC 2016-01-14 23:58:21 +0000 UTC }]
[19:14:29][Step 7/7] Jan 15 00:14:29.866: INFO:
[19:14:29][Step 7/7] Jan 15 00:14:29.868: INFO:
[19:14:29][Step 7/7] Logging node info for node 172.17.0.10
[19:14:29][Step 7/7] Jan 15 00:14:29.870: INFO: Node Info: &{{ } {172.17.0.10 /api/v1/nodes/172.17.0.10 a6db09dd-bb1a-11e5-99da-0242ac110006 1358 0 2016-01-14 23:58:04 +0000 UTC <nil> <nil> map[kubernetes.io/hostname:172.17.0.10 k8s.mesosphere.io/attribute-gen:2012 k8s.mesosphere.io/attribute-rack:2] map[k8s.mesosphere.io/executorId:b8ea8e7042075f9a_k8sm-executor k8s.mesosphere.io/executorResources:CgRjcHVzEAAaCQkAAAAAAADwPzIBKg==,CgNtZW0QABoJCQAAAAAAAGBAMgEq]} { 172.17.0.10 false} {map[memory:{1879048192.000 BinarySI} pods:{40.000 DecimalSI} cpu:{5.000 DecimalSI}] map[cpu:{5.000 DecimalSI} memory:{1879048192.000 BinarySI} pods:{40.000 DecimalSI}] Pending [{Ready True 2016-01-15 00:14:26 +0000 UTC 0001-01-01 00:00:00 +0000 UTC KubeletReady kubelet is posting ready status} {OutOfDisk False 2016-01-15 00:14:26 +0000 UTC 2016-01-14 23:58:13 +0000 UTC KubeletHasSufficientDisk kubelet has sufficient disk space available}] [{LegacyHostIP 172.17.0.10} {InternalIP 172.17.0.10}] {{10250}} { EC2EC3C2-0A15-BB49-1F80-8085C3189D05 e0b2293d-9331-4bcc-884c-57753777d9fe 3.19.0-39-generic Ubuntu 14.04.3 LTS docker://1.8.2 v1.2.0-alpha.6.10+b7b6c4251e21b7 v1.2.0-alpha.6.10+b7b6c4251e21b7} [{[gcr.io/google_containers/kube2sky:1.12] 24482187} {[gcr.io/google_containers/mounttest:0.5] 1718853} {[gcr.io/google_containers/skydns:2015-10-13-8c72f8c] 40547562} {[gcr.io/google_containers/pause:2.0] 350164} {[gcr.io/google_containers/portforwardtester:1.0] 2296329} {[gcr.io/google_containers/nettest:1.6] 10374838} {[gcr.io/google_containers/exechealthz:1.0] 7095869} {[gcr.io/google_containers/etcd:2.0.9] 12819040} {[gcr.io/google_containers/update-demo:nautilus] 4555533} {[gcr.io/google_containers/busybox:latest] 2429728}]}}
[19:14:29][Step 7/7] Jan 15 00:14:29.870: INFO:
[19:14:29][Step 7/7] Logging kubelet events for node 172.17.0.10
[19:14:29][Step 7/7] Jan 15 00:14:29.874: INFO:
[19:14:29][Step 7/7] Logging pods the kubelet thinks is on node 172.17.0.10
[19:14:29][Step 7/7] Jan 15 00:14:29.878: INFO: kube-dns-v10-1w8zl started at <nil> (0 container statuses recorded)
[19:14:30][Step 7/7] Jan 15 00:14:30.045: INFO: ERROR kubelet_docker_errors{operation_type="inspect_image"} => 10 @[0]
[19:14:30][Step 7/7] Jan 15 00:14:30.045: INFO: ERROR kubelet_docker_errors{operation_type="stop_container"} => 16 @[0]
[19:14:30][Step 7/7] Jan 15 00:14:30.045: INFO:
[19:14:30][Step 7/7] Latency metrics for node 172.17.0.10
[19:14:30][Step 7/7] Jan 15 00:14:30.045: INFO: {Operation:stop_container Method:docker_operations_latency_microseconds Quantile:0.99 Latency:25.021103s}
[19:14:30][Step 7/7] Jan 15 00:14:30.045: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.99 Latency:18.290728s}
[19:14:30][Step 7/7] Jan 15 00:14:30.045: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.9 Latency:14.378835s}
[19:14:30][Step 7/7] Jan 15 00:14:30.045: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.5 Latency:12.101871s}
[19:14:30][Step 7/7] Jan 15 00:14:30.045: INFO:
[19:14:30][Step 7/7] Logging node info for node 172.17.0.7
[19:14:30][Step 7/7] Jan 15 00:14:30.212: INFO: Node Info: &{{ } {172.17.0.7 /api/v1/nodes/172.17.0.7 a4f953ed-bb1a-11e5-99da-0242ac110006 1354 0 2016-01-14 23:58:01 +0000 UTC <nil> <nil> map[k8s.mesosphere.io/attribute-gen:2011 k8s.mesosphere.io/attribute-rack:1 kubernetes.io/e2e-259d3f2d-bb1b-11e5-8802-0242ac110002:42 kubernetes.io/hostname:172.17.0.7] map[k8s.mesosphere.io/executorId:b8ea8e7042075f9a_k8sm-executor k8s.mesosphere.io/executorResources:CgRjcHVzEAAaCQkAAAAAAADwPzIBKg==,CgNtZW0QABoJCQAAAAAAAGBAMgEq]} { 172.17.0.7 false} {map[memory:{1207959552.000 BinarySI} pods:{40.000 DecimalSI} cpu:{3.000 DecimalSI}] map[memory:{1207959552.000 BinarySI} pods:{40.000 DecimalSI} cpu:{3.000 DecimalSI}] Pending [{Ready True 2016-01-15 00:14:21 +0000 UTC 0001-01-01 00:00:00 +0000 UTC KubeletReady kubelet is posting ready status} {OutOfDisk False 2016-01-15 00:14:21 +0000 UTC 2016-01-14 23:58:08 +0000 UTC KubeletHasSufficientDisk kubelet has sufficient disk space available}] [{LegacyHostIP 172.17.0.7} {InternalIP 172.17.0.7}] {{10250}} { EC2EC3C2-0A15-BB49-1F80-8085C3189D05 e0b2293d-9331-4bcc-884c-57753777d9fe 3.19.0-39-generic Ubuntu 14.04.3 LTS docker://1.8.2 v1.2.0-alpha.6.10+b7b6c4251e21b7 v1.2.0-alpha.6.10+b7b6c4251e21b7} [{[redis:latest] 151265773} {[nginx:latest] 133816162} {[gcr.io/google_containers/kube-ui:v4] 5676927} {[gcr.io/google_containers/mounttest:0.6] 2084693} {[gcr.io/google_containers/mounttest-user:0.3] 1718853} {[gcr.io/google_containers/mounttest:0.5] 1718853} {[gcr.io/google_containers/pause:2.0] 350164} {[gcr.io/google_containers/porter:cd5cb5791ebaa8641955f0e8c2a9bed669b1eaab] 5010921} {[gcr.io/google_containers/portforwardtester:1.0] 2296329} {[gcr.io/google_containers/update-demo:nautilus] 4555533} {[gcr.io/google_containers/nginx:1.7.9] 91641000} {[gcr.io/google_containers/test-webserver:latest] 4534272}]}}
[19:14:30][Step 7/7] Jan 15 00:14:30.212: INFO:
[19:14:30][Step 7/7] Logging kubelet events for node 172.17.0.7
[19:14:30][Step 7/7] Jan 15 00:14:30.412: INFO:
[19:14:30][Step 7/7] Logging pods the kubelet thinks is on node 172.17.0.7
[19:14:30][Step 7/7] Jan 15 00:14:30.614: INFO: kube-ui-v4-hp9km started at <nil> (0 container statuses recorded)
[19:14:30][Step 7/7] Jan 15 00:14:30.831: INFO: ERROR kubelet_docker_errors{operation_type="inspect_image"} => 12 @[0]
[19:14:30][Step 7/7] Jan 15 00:14:30.831: INFO: ERROR kubelet_docker_errors{operation_type="logs"} => 1 @[0]
[19:14:30][Step 7/7] Jan 15 00:14:30.831: INFO: ERROR kubelet_docker_errors{operation_type="stop_container"} => 21 @[0]
[19:14:30][Step 7/7] Jan 15 00:14:30.831: INFO:
[19:14:30][Step 7/7] Latency metrics for node 172.17.0.7
[19:14:30][Step 7/7] Jan 15 00:14:30.831: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.9 Latency:22.126055s}
[19:14:30][Step 7/7] Jan 15 00:14:30.831: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.99 Latency:22.126055s}
[19:14:30][Step 7/7] Jan 15 00:14:30.831: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.5 Latency:12.68052s}
[19:14:30][Step 7/7] Jan 15 00:14:30.831: INFO: Waiting up to 1m0s for all nodes to be ready
[19:14:31][Step 7/7] STEP: Destroying namespace "e2e-tests-sched-pred-coi56" for this suite.
[19:14:31][Step 7/7]
[19:14:31][Step 7/7] • Failure [13.802 seconds]
[19:14:31][Step 7/7] SchedulerPredicates [Serial]
[19:14:31][Step 7/7] /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/scheduler_predicates.go:473
[19:14:31][Step 7/7] validates that NodeSelector is respected if not matching [Conformance] [It]
[19:14:31][Step 7/7] /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/scheduler_predicates.go:393
[19:14:31][Step 7/7]
[19:14:31][Step 7/7]
[19:14:31][Step 7/7] Expected
[19:14:31][Step 7/7] <[]api.Event | len:0, cap:0>: []
[19:14:31][Step 7/7] not to be empty
[19:14:31][Step 7/7]
[19:14:31][Step 7/7] /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/scheduler_predicates.go:140
```
|
test
|
schedulerpredicates validates that nodeselector is respected if not matching schedulerpredicates validates that nodeselector is respected if not matching go src github com googlecloudplatform kubernetes output local go src io kubernetes test scheduler predicates go schedulerpredicates go src github com googlecloudplatform kubernetes output local go src io kubernetes test framework go step creating a kubernetes client jan info testcontext kubeconfig root kube config step building a namespace api object jan info waiting up to for service account default to be provisioned in ns tests sched pred jan info service account default in ns tests sched pred had secrets ignoring for jan info service account default in ns tests sched pred with secrets found step waiting for a default service account to be provisioned in namespace jan info waiting up to for service account default to be provisioned in ns tests sched pred jan info service account default in ns tests sched pred with secrets found schedulerpredicates go src github com googlecloudplatform kubernetes output local go src io kubernetes test scheduler predicates go validates that nodeselector is respected if not matching go src github com googlecloudplatform kubernetes output local go src io kubernetes test scheduler predicates go step trying to schedule pod with nonempty nodeselector jan info sleeping seconds and crossing our fingers that scheduler will run in that time schedulerpredicates go src github com googlecloudplatform kubernetes output local go src io kubernetes test scheduler predicates go schedulerpredicates go src github com googlecloudplatform kubernetes output local go src io kubernetes test framework go step collecting events from namespace tests sched pred jan info event for restricted pod scheduler failedscheduling error scheduling no suitable offers for pod task jan info pod node phase grace conditions jan info restricted pod pending jan info kube dns running jan info kube ui running jan info jan info logging node info for node jan info node info api nodes utc map map false map map pending generic ubuntu lts docker alpha alpha jan info logging kubelet events for node jan info logging pods the kubelet thinks is on node jan info kube dns started at container statuses recorded jan info error kubelet docker errors operation type inspect image jan info error kubelet docker errors operation type stop container jan info latency metrics for node jan info operation stop container method docker operations latency microseconds quantile latency jan info operation method pod start latency microseconds quantile latency jan info operation method pod start latency microseconds quantile latency jan info operation method pod start latency microseconds quantile latency jan info logging node info for node jan info node info api nodes utc map map false map map pending generic ubuntu lts docker alpha alpha jan info logging kubelet events for node jan info logging pods the kubelet thinks is on node jan info kube ui started at container statuses recorded jan info error kubelet docker errors operation type inspect image jan info error kubelet docker errors operation type logs jan info error kubelet docker errors operation type stop container jan info latency metrics for node jan info operation method pod start latency microseconds quantile latency jan info operation method pod start latency microseconds quantile latency jan info operation method pod start latency microseconds quantile latency jan info waiting up to for all nodes to be ready step destroying namespace tests sched pred for this suite • failure schedulerpredicates go src github com googlecloudplatform kubernetes output local go src io kubernetes test scheduler predicates go validates that nodeselector is respected if not matching go src github com googlecloudplatform kubernetes output local go src io kubernetes test scheduler predicates go expected not to be empty go src github com googlecloudplatform kubernetes output local go src io kubernetes test scheduler predicates go
| 1
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.