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
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
6,510
| 2,848,817,497
|
IssuesEvent
|
2015-05-30 05:17:27
|
pods-framework/pods
|
https://api.github.com/repos/pods-framework/pods
|
closed
|
Delete Not Working for Edit Items
|
Bug: Normal Fixed / Needs Testing Needs Research PR 2.x Submitted PR 3.0 Submitted Verified/Reproduced
|
When editing an item, the delete link in the right sidebar does not seem to be working. Tested with default TwentyFifteen theme. It takes you back to list screen, but the item you just deleted remains.
|
1.0
|
Delete Not Working for Edit Items - When editing an item, the delete link in the right sidebar does not seem to be working. Tested with default TwentyFifteen theme. It takes you back to list screen, but the item you just deleted remains.
|
test
|
delete not working for edit items when editing an item the delete link in the right sidebar does not seem to be working tested with default twentyfifteen theme it takes you back to list screen but the item you just deleted remains
| 1
|
188,911
| 14,479,522,377
|
IssuesEvent
|
2020-12-10 09:55:28
|
kalexmills/github-vet-tests-dec2020
|
https://api.github.com/repos/kalexmills/github-vet-tests-dec2020
|
closed
|
nextradata/pdfcpu: pkg/api/process_test.go; 11 LoC
|
fresh small test
|
Found a possible issue in [nextradata/pdfcpu](https://www.github.com/nextradata/pdfcpu) at [pkg/api/process_test.go](https://github.com/nextradata/pdfcpu/blob/7cb4f3682d25109172045b6eb4c265660d138721/pkg/api/process_test.go#L579-L589)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first
issue it finds, so please do not limit your consideration to the contents of the below message.
> reference to fn is reassigned at line 582
[Click here to see the code in its original context.](https://github.com/nextradata/pdfcpu/blob/7cb4f3682d25109172045b6eb4c265660d138721/pkg/api/process_test.go#L579-L589)
<details>
<summary>Click here to show the 11 line(s) of Go which triggered the analyzer.</summary>
```go
for _, fn := range []string{"5116.DCT_Filter.pdf", "testImage.pdf", "go.pdf"} {
fn = "testdata/" + fn
cmd.InFile = &fn
_, err := Process(cmd)
if err != nil {
t.Fatalf("TestExtractFontsCommand: %v\n", err)
}
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: 7cb4f3682d25109172045b6eb4c265660d138721
|
1.0
|
nextradata/pdfcpu: pkg/api/process_test.go; 11 LoC -
Found a possible issue in [nextradata/pdfcpu](https://www.github.com/nextradata/pdfcpu) at [pkg/api/process_test.go](https://github.com/nextradata/pdfcpu/blob/7cb4f3682d25109172045b6eb4c265660d138721/pkg/api/process_test.go#L579-L589)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first
issue it finds, so please do not limit your consideration to the contents of the below message.
> reference to fn is reassigned at line 582
[Click here to see the code in its original context.](https://github.com/nextradata/pdfcpu/blob/7cb4f3682d25109172045b6eb4c265660d138721/pkg/api/process_test.go#L579-L589)
<details>
<summary>Click here to show the 11 line(s) of Go which triggered the analyzer.</summary>
```go
for _, fn := range []string{"5116.DCT_Filter.pdf", "testImage.pdf", "go.pdf"} {
fn = "testdata/" + fn
cmd.InFile = &fn
_, err := Process(cmd)
if err != nil {
t.Fatalf("TestExtractFontsCommand: %v\n", err)
}
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: 7cb4f3682d25109172045b6eb4c265660d138721
|
test
|
nextradata pdfcpu pkg api process test go loc found a possible issue in at below is the message reported by the analyzer for this snippet of code beware that the analyzer only reports the first issue it finds so please do not limit your consideration to the contents of the below message reference to fn is reassigned at line click here to show the line s of go which triggered the analyzer go for fn range string dct filter pdf testimage pdf go pdf fn testdata fn cmd infile fn err process cmd if err nil t fatalf testextractfontscommand v n err leave a reaction on this issue to contribute to the project by classifying this instance as a bug mitigated or desirable behavior rocket see the descriptions of the classifications for more information commit id
| 1
|
42,828
| 5,477,800,781
|
IssuesEvent
|
2017-03-12 12:20:52
|
TEAMMATES/teammates
|
https://api.github.com/repos/TEAMMATES/teammates
|
closed
|
Random test fail in *LogicTest.java recently
|
a-Testing c.Bug p.Medium
|
There are test failures on Travis or Appveyor for `*Logic` recently. This may be caused by #6655, which use `dependsOnGroup` to control the order of test cases.
|
1.0
|
Random test fail in *LogicTest.java recently - There are test failures on Travis or Appveyor for `*Logic` recently. This may be caused by #6655, which use `dependsOnGroup` to control the order of test cases.
|
test
|
random test fail in logictest java recently there are test failures on travis or appveyor for logic recently this may be caused by which use dependsongroup to control the order of test cases
| 1
|
321,440
| 27,530,223,056
|
IssuesEvent
|
2023-03-06 21:24:49
|
cockroachdb/cockroach
|
https://api.github.com/repos/cockroachdb/cockroach
|
closed
|
pkg/ccl/spanconfigccl/spanconfigreconcilerccl/spanconfigreconcilerccl_test: TestDataDriven failed
|
C-test-failure O-robot branch-master T-kv
|
pkg/ccl/spanconfigccl/spanconfigreconcilerccl/spanconfigreconcilerccl_test.TestDataDriven [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/8926755?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/8926755?buildTab=artifacts#/) on master @ [cf14ad694ee562676f53e36fa8495206c3aed61f](https://github.com/cockroachdb/cockroach/commits/cf14ad694ee562676f53e36fa8495206c3aed61f):
```
delete {source=1,target=2}
datadriven_test.go:124:
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3334/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-fastbuild/bin/pkg/ccl/spanconfigccl/spanconfigreconcilerccl/spanconfigreconcilerccl_test_/spanconfigreconcilerccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/spanconfigccl/spanconfigreconcilerccl/testdata/protectedts:127:
state [1 args]
<no input to command>
----
/{Min-System/NodeLiveness} ttl_seconds=3600 num_replicas=5
/System/NodeLiveness{-Max} ttl_seconds=600 num_replicas=5
...
datadriven_test.go:124:
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3334/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-fastbuild/bin/pkg/ccl/spanconfigccl/spanconfigreconcilerccl/spanconfigreconcilerccl_test_/spanconfigreconcilerccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/spanconfigccl/spanconfigreconcilerccl/testdata/protectedts:134:
release [1 args]
<no input to command>
----
datadriven_test.go:124:
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3334/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-fastbuild/bin/pkg/ccl/spanconfigccl/spanconfigreconcilerccl/spanconfigreconcilerccl_test_/spanconfigreconcilerccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/spanconfigccl/spanconfigreconcilerccl/testdata/protectedts:137:
release [1 args]
<no input to command>
----
datadriven_test.go:124:
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3334/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-fastbuild/bin/pkg/ccl/spanconfigccl/spanconfigreconcilerccl/spanconfigreconcilerccl_test_/spanconfigreconcilerccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/spanconfigccl/spanconfigreconcilerccl/testdata/protectedts:140:
expected:
delete /Table/10{6-7}
upsert /Table/10{6-7} range default
delete /Table/10{7-8}
upsert /Table/10{7-8} range default
found:
delete /Table/10{6-7}
upsert /Table/10{6-7} protection_policies=[{ts: 4}]
delete /Table/10{7-8}
upsert /Table/10{7-8} protection_policies=[{ts: 4}]
delete /Table/10{6-7}
upsert /Table/10{6-7} range default
delete /Table/10{7-8}
upsert /Table/10{7-8} range default
I230305 07:17:29.933256 6856383 testutils/testcluster/testcluster.go:148 [T1] 2905 TestCluster quiescing nodes
W230305 07:17:29.933747 6887737 jobs/registry.go:1080 [T1,n1] 2906 canceling all adopted jobs due to stopper quiescing
I230305 07:17:29.934606 6872550 server/start_listen.go:103 [T1,n1] 2907 server shutting down: instructing cmux to stop accepting
I230305 07:17:29.935300 7102142 jobs/registry.go:1495 [T1,n1] 2908 KEY VISUALIZER job 100: stepping through state succeeded
I230305 07:17:29.936114 6887421 sql/stats/automatic_stats.go:507 [T1,n1] 2909 quiescing auto stats refresher
W230305 07:17:29.937715 7510389 kv/kvserver/intentresolver/intent_resolver.go:826 [T1] 2910 failed to gc transaction record: could not GC completed transaction anchored at /Table/31/1/1/0: node unavailable; try another peer
W230305 07:17:29.941171 6881647 sql/sqlliveness/slinstance/slinstance.go:312 [T1,n1] 2911 exiting heartbeat loop
W230305 07:17:29.941313 6881647 sql/sqlliveness/slinstance/slinstance.go:297 [T1,n1] 2912 exiting heartbeat loop
E230305 07:17:29.941436 6881647 server/server_sql.go:477 [T1,n1] 2913 failed to run update of instance with new session ID: node unavailable; try another peer
E230305 07:17:29.948053 6887814 jobs/registry.go:1064 [T1,n1] 2914 error processing claimed jobs: could not query for claimed jobs: select-running/get-claimed-jobs: failed to read query result: query execution canceled
W230305 07:17:29.951681 7102142 jobs/adopt.go:457 [T1,n1] 2915 could not clear job claim: clear-job-claim: node unavailable; try another peer
W230305 07:17:29.953911 7129191 jobs/adopt.go:457 [T1,n1] 2916 could not clear job claim: clear-job-claim: failed to send RPC: sending to all replicas failed; last error: ba: Scan [/Table/15/1/101,/Table/15/1/102), [txn: 41f3b112], [can-forward-ts] RPC error: node unavailable; try another peer
--- FAIL: TestDataDriven/protectedts (7.79s)
```
<p>Parameters: <code>TAGS=bazel,gss,deadlock</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/kv
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestDataDriven.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-25036
|
1.0
|
pkg/ccl/spanconfigccl/spanconfigreconcilerccl/spanconfigreconcilerccl_test: TestDataDriven failed - pkg/ccl/spanconfigccl/spanconfigreconcilerccl/spanconfigreconcilerccl_test.TestDataDriven [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/8926755?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/8926755?buildTab=artifacts#/) on master @ [cf14ad694ee562676f53e36fa8495206c3aed61f](https://github.com/cockroachdb/cockroach/commits/cf14ad694ee562676f53e36fa8495206c3aed61f):
```
delete {source=1,target=2}
datadriven_test.go:124:
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3334/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-fastbuild/bin/pkg/ccl/spanconfigccl/spanconfigreconcilerccl/spanconfigreconcilerccl_test_/spanconfigreconcilerccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/spanconfigccl/spanconfigreconcilerccl/testdata/protectedts:127:
state [1 args]
<no input to command>
----
/{Min-System/NodeLiveness} ttl_seconds=3600 num_replicas=5
/System/NodeLiveness{-Max} ttl_seconds=600 num_replicas=5
...
datadriven_test.go:124:
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3334/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-fastbuild/bin/pkg/ccl/spanconfigccl/spanconfigreconcilerccl/spanconfigreconcilerccl_test_/spanconfigreconcilerccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/spanconfigccl/spanconfigreconcilerccl/testdata/protectedts:134:
release [1 args]
<no input to command>
----
datadriven_test.go:124:
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3334/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-fastbuild/bin/pkg/ccl/spanconfigccl/spanconfigreconcilerccl/spanconfigreconcilerccl_test_/spanconfigreconcilerccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/spanconfigccl/spanconfigreconcilerccl/testdata/protectedts:137:
release [1 args]
<no input to command>
----
datadriven_test.go:124:
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3334/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-fastbuild/bin/pkg/ccl/spanconfigccl/spanconfigreconcilerccl/spanconfigreconcilerccl_test_/spanconfigreconcilerccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/spanconfigccl/spanconfigreconcilerccl/testdata/protectedts:140:
expected:
delete /Table/10{6-7}
upsert /Table/10{6-7} range default
delete /Table/10{7-8}
upsert /Table/10{7-8} range default
found:
delete /Table/10{6-7}
upsert /Table/10{6-7} protection_policies=[{ts: 4}]
delete /Table/10{7-8}
upsert /Table/10{7-8} protection_policies=[{ts: 4}]
delete /Table/10{6-7}
upsert /Table/10{6-7} range default
delete /Table/10{7-8}
upsert /Table/10{7-8} range default
I230305 07:17:29.933256 6856383 testutils/testcluster/testcluster.go:148 [T1] 2905 TestCluster quiescing nodes
W230305 07:17:29.933747 6887737 jobs/registry.go:1080 [T1,n1] 2906 canceling all adopted jobs due to stopper quiescing
I230305 07:17:29.934606 6872550 server/start_listen.go:103 [T1,n1] 2907 server shutting down: instructing cmux to stop accepting
I230305 07:17:29.935300 7102142 jobs/registry.go:1495 [T1,n1] 2908 KEY VISUALIZER job 100: stepping through state succeeded
I230305 07:17:29.936114 6887421 sql/stats/automatic_stats.go:507 [T1,n1] 2909 quiescing auto stats refresher
W230305 07:17:29.937715 7510389 kv/kvserver/intentresolver/intent_resolver.go:826 [T1] 2910 failed to gc transaction record: could not GC completed transaction anchored at /Table/31/1/1/0: node unavailable; try another peer
W230305 07:17:29.941171 6881647 sql/sqlliveness/slinstance/slinstance.go:312 [T1,n1] 2911 exiting heartbeat loop
W230305 07:17:29.941313 6881647 sql/sqlliveness/slinstance/slinstance.go:297 [T1,n1] 2912 exiting heartbeat loop
E230305 07:17:29.941436 6881647 server/server_sql.go:477 [T1,n1] 2913 failed to run update of instance with new session ID: node unavailable; try another peer
E230305 07:17:29.948053 6887814 jobs/registry.go:1064 [T1,n1] 2914 error processing claimed jobs: could not query for claimed jobs: select-running/get-claimed-jobs: failed to read query result: query execution canceled
W230305 07:17:29.951681 7102142 jobs/adopt.go:457 [T1,n1] 2915 could not clear job claim: clear-job-claim: node unavailable; try another peer
W230305 07:17:29.953911 7129191 jobs/adopt.go:457 [T1,n1] 2916 could not clear job claim: clear-job-claim: failed to send RPC: sending to all replicas failed; last error: ba: Scan [/Table/15/1/101,/Table/15/1/102), [txn: 41f3b112], [can-forward-ts] RPC error: node unavailable; try another peer
--- FAIL: TestDataDriven/protectedts (7.79s)
```
<p>Parameters: <code>TAGS=bazel,gss,deadlock</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/kv
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestDataDriven.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-25036
|
test
|
pkg ccl spanconfigccl spanconfigreconcilerccl spanconfigreconcilerccl test testdatadriven failed pkg ccl spanconfigccl spanconfigreconcilerccl spanconfigreconcilerccl test testdatadriven with on master delete source target datadriven test go home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out fastbuild bin pkg ccl spanconfigccl spanconfigreconcilerccl spanconfigreconcilerccl test spanconfigreconcilerccl test runfiles com github cockroachdb cockroach pkg ccl spanconfigccl spanconfigreconcilerccl testdata protectedts state min system nodeliveness ttl seconds num replicas system nodeliveness max ttl seconds num replicas datadriven test go home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out fastbuild bin pkg ccl spanconfigccl spanconfigreconcilerccl spanconfigreconcilerccl test spanconfigreconcilerccl test runfiles com github cockroachdb cockroach pkg ccl spanconfigccl spanconfigreconcilerccl testdata protectedts release datadriven test go home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out fastbuild bin pkg ccl spanconfigccl spanconfigreconcilerccl spanconfigreconcilerccl test spanconfigreconcilerccl test runfiles com github cockroachdb cockroach pkg ccl spanconfigccl spanconfigreconcilerccl testdata protectedts release datadriven test go home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out fastbuild bin pkg ccl spanconfigccl spanconfigreconcilerccl spanconfigreconcilerccl test spanconfigreconcilerccl test runfiles com github cockroachdb cockroach pkg ccl spanconfigccl spanconfigreconcilerccl testdata protectedts expected delete table upsert table range default delete table upsert table range default found delete table upsert table protection policies delete table upsert table protection policies delete table upsert table range default delete table upsert table range default testutils testcluster testcluster go testcluster quiescing nodes jobs registry go canceling all adopted jobs due to stopper quiescing server start listen go server shutting down instructing cmux to stop accepting jobs registry go key visualizer job stepping through state succeeded sql stats automatic stats go quiescing auto stats refresher kv kvserver intentresolver intent resolver go failed to gc transaction record could not gc completed transaction anchored at table node unavailable try another peer sql sqlliveness slinstance slinstance go exiting heartbeat loop sql sqlliveness slinstance slinstance go exiting heartbeat loop server server sql go failed to run update of instance with new session id node unavailable try another peer jobs registry go error processing claimed jobs could not query for claimed jobs select running get claimed jobs failed to read query result query execution canceled jobs adopt go could not clear job claim clear job claim node unavailable try another peer jobs adopt go could not clear job claim clear job claim failed to send rpc sending to all replicas failed last error ba scan rpc error node unavailable try another peer fail testdatadriven protectedts parameters tags bazel gss deadlock help see also cc cockroachdb kv jira issue crdb
| 1
|
341,043
| 30,564,447,045
|
IssuesEvent
|
2023-07-20 16:40:42
|
giorgi-injgia-1-btu-edu-ge/final_git
|
https://api.github.com/repos/giorgi-injgia-1-btu-edu-ge/final_git
|
opened
|
6150b2a failed unit and formatting tests.
|
ci-pytest ci-black
|
Results of latest checkings
6150b2a3153204ca158f6b738966877fedb508dc failed unit and formatting tests.
pytest bisect result [20d635a3ba1a4d617387ecac936132bc0571c6d9] pytest_absent_black_failed
black bisect result [20d635a3ba1a4d617387ecac936132bc0571c6d9] pytest_absent_black_failed
Pytest report: <a href="https://github.com/giorgi-injgia-1-btu-edu-ge/test-repo/blob/report_branch/6150b2a3153204ca158f6b738966877fedb508dc-1689871237/pytest.html">pytest report</a>
Black report: <a href="https://github.com/giorgi-injgia-1-btu-edu-ge/test-repo/blob/report_branch/6150b2a3153204ca158f6b738966877fedb508dc-1689871237/black.html">black report</a>
|
1.0
|
6150b2a failed unit and formatting tests. - Results of latest checkings
6150b2a3153204ca158f6b738966877fedb508dc failed unit and formatting tests.
pytest bisect result [20d635a3ba1a4d617387ecac936132bc0571c6d9] pytest_absent_black_failed
black bisect result [20d635a3ba1a4d617387ecac936132bc0571c6d9] pytest_absent_black_failed
Pytest report: <a href="https://github.com/giorgi-injgia-1-btu-edu-ge/test-repo/blob/report_branch/6150b2a3153204ca158f6b738966877fedb508dc-1689871237/pytest.html">pytest report</a>
Black report: <a href="https://github.com/giorgi-injgia-1-btu-edu-ge/test-repo/blob/report_branch/6150b2a3153204ca158f6b738966877fedb508dc-1689871237/black.html">black report</a>
|
test
|
failed unit and formatting tests results of latest checkings failed unit and formatting tests pytest bisect result pytest absent black failed black bisect result pytest absent black failed pytest report black report
| 1
|
317,473
| 27,239,601,841
|
IssuesEvent
|
2023-02-21 19:10:10
|
rancher/dashboard
|
https://api.github.com/repos/rancher/dashboard
|
closed
|
When creating a PSACT value as YAML, you are not redirected back to the `Pod Security Admissions` tab
|
kind/bug [zube]: To Test QA/XS team/area2 size/1 area/psa
|
**Is your feature request related to a problem? Please describe.**
<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
When creating a new PSACT value, when attempting to do so while editing as YAML, the following behavior happens:
As seen in the above video, the new PSACT value creates, but rather than go back to the `Pod Security Admissions` tab and show all of the created templates, it simply says `Saved` and stays on the same edited YAML screen. Additionally, clicking `Create` again gives the expected error shown as the value is already created.
**Describe the solution you'd like**
<!-- A clear and concise description of what you want to happen. -->
If a user is creating a PSACT value via YAML, once it has been successfully created, they should be redirected to the `Pod Security Admissions` tab.
|
1.0
|
When creating a PSACT value as YAML, you are not redirected back to the `Pod Security Admissions` tab - **Is your feature request related to a problem? Please describe.**
<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
When creating a new PSACT value, when attempting to do so while editing as YAML, the following behavior happens:
As seen in the above video, the new PSACT value creates, but rather than go back to the `Pod Security Admissions` tab and show all of the created templates, it simply says `Saved` and stays on the same edited YAML screen. Additionally, clicking `Create` again gives the expected error shown as the value is already created.
**Describe the solution you'd like**
<!-- A clear and concise description of what you want to happen. -->
If a user is creating a PSACT value via YAML, once it has been successfully created, they should be redirected to the `Pod Security Admissions` tab.
|
test
|
when creating a psact value as yaml you are not redirected back to the pod security admissions tab is your feature request related to a problem please describe when creating a new psact value when attempting to do so while editing as yaml the following behavior happens as seen in the above video the new psact value creates but rather than go back to the pod security admissions tab and show all of the created templates it simply says saved and stays on the same edited yaml screen additionally clicking create again gives the expected error shown as the value is already created describe the solution you d like if a user is creating a psact value via yaml once it has been successfully created they should be redirected to the pod security admissions tab
| 1
|
148,301
| 11,846,646,491
|
IssuesEvent
|
2020-03-24 10:33:51
|
microsoft/azure-tools-for-java
|
https://api.github.com/repos/microsoft/azure-tools-for-java
|
opened
|
[IntelliJ][2020.1 EAP] When submit on synapse,there will show "Error running: unknown error"
|
HDInsight IntelliJ Internal Test eap
|
IntelliJ Version: IntelliJ 2020.1 EAP
Build: https://dev.azure.com/mseng/VSJava/_build/results?buildId=11762502&view=artifacts&type=publishedArtifacts
Repro Step:
1.Create a synapse config
2.Submit this job
Results:
Error running: unknown error
|
1.0
|
[IntelliJ][2020.1 EAP] When submit on synapse,there will show "Error running: unknown error" - IntelliJ Version: IntelliJ 2020.1 EAP
Build: https://dev.azure.com/mseng/VSJava/_build/results?buildId=11762502&view=artifacts&type=publishedArtifacts
Repro Step:
1.Create a synapse config
2.Submit this job
Results:
Error running: unknown error
|
test
|
when submit on synapse there will show error running unknown error intellij version intellij eap build repro step create a synapse config submit this job results error running unknown error
| 1
|
280,354
| 8,680,760,183
|
IssuesEvent
|
2018-12-01 13:53:55
|
webcompat/web-bugs
|
https://api.github.com/repos/webcompat/web-bugs
|
opened
|
www.homebook.pl - desktop site instead of mobile site
|
browser-firefox-mobile priority-normal
|
<!-- @browser: Firefox Mobile 65.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 8.0.0; Mobile; rv:65.0) Gecko/65.0 Firefox/65.0 -->
<!-- @reported_with: mobile-reporter -->
**URL**: https://www.homebook.pl/
**Browser / Version**: Firefox Mobile 65.0
**Operating System**: Android 8.0.0
**Tested Another Browser**: Yes
**Problem type**: Desktop site instead of mobile site
**Description**: Desktop site, which can't be scrolled horizontally
**Steps to Reproduce**:
[](https://webcompat.com/uploads/2018/12/c231a2bb-8bb7-4fee-9f53-4281cce589b4.jpeg)
<details>
<summary>Browser Configuration</summary>
<ul>
<li>mixed active content blocked: false</li><li>image.mem.shared: true</li><li>buildID: 20181130093534</li><li>tracking content blocked: false</li><li>gfx.webrender.blob-images: true</li><li>hasTouchScreen: true</li><li>mixed passive content blocked: false</li><li>gfx.webrender.enabled: false</li><li>gfx.webrender.all: false</li><li>channel: nightly</li>
</ul>
<p>Console Messages:</p>
<pre>
[u'[JavaScript Warning: "Wczytanie nie powiodo si dla elementu script ze rdem https://connect.facebook.net/en_US/fbevents.js." {file: "https://www.homebook.pl/inspiracje/kuchnia/618589_-kuchnia-styl-nowoczesny" line: 1}]', u'[JavaScript Warning: "Wczytanie nie powiodo si dla elementu script ze rdem https://www.homebook.pl/Content/v1/scripts_raw/showads.js." {file: "https://www.homebook.pl/inspiracje/kuchnia/618589_-kuchnia-styl-nowoczesny" line: 5052}]', u'[JavaScript Warning: "Wczytanie nie powiodo si dla elementu script ze rdem https://gapl.hit.gemius.pl/xgemius.js." {file: "https://www.homebook.pl/inspiracje/kuchnia/618589_-kuchnia-styl-nowoczesny" line: 1}]']
</pre>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_
|
1.0
|
www.homebook.pl - desktop site instead of mobile site - <!-- @browser: Firefox Mobile 65.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 8.0.0; Mobile; rv:65.0) Gecko/65.0 Firefox/65.0 -->
<!-- @reported_with: mobile-reporter -->
**URL**: https://www.homebook.pl/
**Browser / Version**: Firefox Mobile 65.0
**Operating System**: Android 8.0.0
**Tested Another Browser**: Yes
**Problem type**: Desktop site instead of mobile site
**Description**: Desktop site, which can't be scrolled horizontally
**Steps to Reproduce**:
[](https://webcompat.com/uploads/2018/12/c231a2bb-8bb7-4fee-9f53-4281cce589b4.jpeg)
<details>
<summary>Browser Configuration</summary>
<ul>
<li>mixed active content blocked: false</li><li>image.mem.shared: true</li><li>buildID: 20181130093534</li><li>tracking content blocked: false</li><li>gfx.webrender.blob-images: true</li><li>hasTouchScreen: true</li><li>mixed passive content blocked: false</li><li>gfx.webrender.enabled: false</li><li>gfx.webrender.all: false</li><li>channel: nightly</li>
</ul>
<p>Console Messages:</p>
<pre>
[u'[JavaScript Warning: "Wczytanie nie powiodo si dla elementu script ze rdem https://connect.facebook.net/en_US/fbevents.js." {file: "https://www.homebook.pl/inspiracje/kuchnia/618589_-kuchnia-styl-nowoczesny" line: 1}]', u'[JavaScript Warning: "Wczytanie nie powiodo si dla elementu script ze rdem https://www.homebook.pl/Content/v1/scripts_raw/showads.js." {file: "https://www.homebook.pl/inspiracje/kuchnia/618589_-kuchnia-styl-nowoczesny" line: 5052}]', u'[JavaScript Warning: "Wczytanie nie powiodo si dla elementu script ze rdem https://gapl.hit.gemius.pl/xgemius.js." {file: "https://www.homebook.pl/inspiracje/kuchnia/618589_-kuchnia-styl-nowoczesny" line: 1}]']
</pre>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_
|
non_test
|
desktop site instead of mobile site url browser version firefox mobile operating system android tested another browser yes problem type desktop site instead of mobile site description desktop site which can t be scrolled horizontally steps to reproduce browser configuration mixed active content blocked false image mem shared true buildid tracking content blocked false gfx webrender blob images true hastouchscreen true mixed passive content blocked false gfx webrender enabled false gfx webrender all false channel nightly console messages u u from with ❤️
| 0
|
629,511
| 20,035,108,270
|
IssuesEvent
|
2022-02-02 11:01:28
|
Selleo/til
|
https://api.github.com/repos/Selleo/til
|
closed
|
Missing focus outline for checkboxes
|
bug 🐛 frontend low priority good first issue 🍎
|
Checkboxes in Add form don't have "focus" styles so when a user is using keyboard navigation, doesn't see that checkbox is focused
|
1.0
|
Missing focus outline for checkboxes - Checkboxes in Add form don't have "focus" styles so when a user is using keyboard navigation, doesn't see that checkbox is focused
|
non_test
|
missing focus outline for checkboxes checkboxes in add form don t have focus styles so when a user is using keyboard navigation doesn t see that checkbox is focused
| 0
|
229,153
| 18,286,640,698
|
IssuesEvent
|
2021-10-05 11:02:56
|
DILCISBoard/eark-ip-test-corpus
|
https://api.github.com/repos/DILCISBoard/eark-ip-test-corpus
|
closed
|
CSIPSTR2 Test Case Description
|
duplicate test case ready
|
**Specification:**
- **Name:** E-ARK CSIP
**Version:** 2.0-DRAFT
**URL:** http://earkcsip.dilcis.eu/
**Requirement:**
- **Id:** CSIPSTR2
- **Link:** http://earkcsip.dilcis.eu/#CSIPSTR2
**Corpus Folder:** `corpora/csip/structure/folders/`
**Error Level:** WARNING
**Description:**
> The Information Package folder SHOULD be named with the ID or name of the Information Package;
This only makes sense if correlated against other sources of the ID, e.g. in the `mets/@OBJID` element. Put another way, the requirement says that there should be a meaningful name, but stipulates no form for the name. Beyond saying that it can’t be an empty string, which isn’t possible given it’s a folder name, we’re not prescribing what’s meaningful to an organisation. In this case the test might be a warning if the name of the root folder and the `mets/@OBJID` attribute don’t match, which is more easily achieved as a CSIP2 test, when the attribute value is parsed.
|
1.0
|
CSIPSTR2 Test Case Description - **Specification:**
- **Name:** E-ARK CSIP
**Version:** 2.0-DRAFT
**URL:** http://earkcsip.dilcis.eu/
**Requirement:**
- **Id:** CSIPSTR2
- **Link:** http://earkcsip.dilcis.eu/#CSIPSTR2
**Corpus Folder:** `corpora/csip/structure/folders/`
**Error Level:** WARNING
**Description:**
> The Information Package folder SHOULD be named with the ID or name of the Information Package;
This only makes sense if correlated against other sources of the ID, e.g. in the `mets/@OBJID` element. Put another way, the requirement says that there should be a meaningful name, but stipulates no form for the name. Beyond saying that it can’t be an empty string, which isn’t possible given it’s a folder name, we’re not prescribing what’s meaningful to an organisation. In this case the test might be a warning if the name of the root folder and the `mets/@OBJID` attribute don’t match, which is more easily achieved as a CSIP2 test, when the attribute value is parsed.
|
test
|
test case description specification name e ark csip version draft url requirement id link corpus folder corpora csip structure folders error level warning description the information package folder should be named with the id or name of the information package this only makes sense if correlated against other sources of the id e g in the mets objid element put another way the requirement says that there should be a meaningful name but stipulates no form for the name beyond saying that it can’t be an empty string which isn’t possible given it’s a folder name we’re not prescribing what’s meaningful to an organisation in this case the test might be a warning if the name of the root folder and the mets objid attribute don’t match which is more easily achieved as a test when the attribute value is parsed
| 1
|
222,926
| 24,711,484,517
|
IssuesEvent
|
2022-10-20 01:25:11
|
anakos9/Questributions
|
https://api.github.com/repos/anakos9/Questributions
|
opened
|
CVE-2022-3517 (High) detected in minimatch-3.0.4.tgz
|
security vulnerability
|
## CVE-2022-3517 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>minimatch-3.0.4.tgz</b></p></summary>
<p>a glob matcher in javascript</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimatch/-/minimatch-3.0.4.tgz">https://registry.npmjs.org/minimatch/-/minimatch-3.0.4.tgz</a></p>
<p>Path to dependency file: /Questributions/package.json</p>
<p>Path to vulnerable library: /node_modules/minimatch/package.json</p>
<p>
Dependency Hierarchy:
- webpack-dev-server-3.7.1.tgz (Root Library)
- chokidar-2.1.6.tgz
- fsevents-1.2.9.tgz
- node-pre-gyp-0.12.0.tgz
- npm-packlist-1.4.1.tgz
- ignore-walk-3.0.1.tgz
- :x: **minimatch-3.0.4.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>
A vulnerability was found in the minimatch package. This flaw allows a Regular Expression Denial of Service (ReDoS) when calling the braceExpand function with specific arguments, resulting in a Denial of Service.
<p>Publish Date: 2022-10-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-3517>CVE-2022-3517</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2022-10-17</p>
<p>Fix Resolution: minimatch - 3.0.5</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2022-3517 (High) detected in minimatch-3.0.4.tgz - ## CVE-2022-3517 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>minimatch-3.0.4.tgz</b></p></summary>
<p>a glob matcher in javascript</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimatch/-/minimatch-3.0.4.tgz">https://registry.npmjs.org/minimatch/-/minimatch-3.0.4.tgz</a></p>
<p>Path to dependency file: /Questributions/package.json</p>
<p>Path to vulnerable library: /node_modules/minimatch/package.json</p>
<p>
Dependency Hierarchy:
- webpack-dev-server-3.7.1.tgz (Root Library)
- chokidar-2.1.6.tgz
- fsevents-1.2.9.tgz
- node-pre-gyp-0.12.0.tgz
- npm-packlist-1.4.1.tgz
- ignore-walk-3.0.1.tgz
- :x: **minimatch-3.0.4.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>
A vulnerability was found in the minimatch package. This flaw allows a Regular Expression Denial of Service (ReDoS) when calling the braceExpand function with specific arguments, resulting in a Denial of Service.
<p>Publish Date: 2022-10-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-3517>CVE-2022-3517</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2022-10-17</p>
<p>Fix Resolution: minimatch - 3.0.5</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_test
|
cve high detected in minimatch tgz cve high severity vulnerability vulnerable library minimatch tgz a glob matcher in javascript library home page a href path to dependency file questributions package json path to vulnerable library node modules minimatch package json dependency hierarchy webpack dev server tgz root library chokidar tgz fsevents tgz node pre gyp tgz npm packlist tgz ignore walk tgz x minimatch tgz vulnerable library vulnerability details a vulnerability was found in the minimatch package this flaw allows a regular expression denial of service redos when calling the braceexpand function with specific arguments resulting in a denial of service publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version release date fix resolution minimatch step up your open source security game with mend
| 0
|
108,935
| 9,336,518,522
|
IssuesEvent
|
2019-03-28 21:28:22
|
istio/istio
|
https://api.github.com/repos/istio/istio
|
opened
|
Stale bot ignores "no stalebot" label.
|
area/test and release no stalebot
|
PRs tagged with "no stalebot" label are still being tagged as stale by the stale bot. The label should be honored.
|
1.0
|
Stale bot ignores "no stalebot" label. - PRs tagged with "no stalebot" label are still being tagged as stale by the stale bot. The label should be honored.
|
test
|
stale bot ignores no stalebot label prs tagged with no stalebot label are still being tagged as stale by the stale bot the label should be honored
| 1
|
39,112
| 9,204,183,196
|
IssuesEvent
|
2019-03-08 06:18:25
|
bridgedotnet/Bridge
|
https://api.github.com/repos/bridgedotnet/Bridge
|
closed
|
Error with generics in Module
|
defect in-progress
|
A description of the issue.
### Steps To Reproduce
https://deck.net/a62bd78c412c66b2194b59cc88ab0be9
```csharp
[Module(Bridge.ModuleType.UMD)]
public class Program
{
public static ILazy<Class1> lazyClass1;
public static void Main()
{
lazyClass1 = new Lazy<Class1>();
Ololo(lazyClass1);
}
internal static void Ololo(ILazy<Class1> lst)
{
lst.Value();
}
}
[Module(Bridge.ModuleType.UMD, "Module1")]
public class Class1
{
}
[Module(Bridge.ModuleType.UMD, "Module2")]
public interface ILazy<T> where T : class
{
/// <summary>
/// Get Resolved Type T
/// </summary>
/// <returns>Resolved Type T</returns>
T Value();
}
[Module(Bridge.ModuleType.UMD, "Module2")]
public class Lazy<T> : ILazy<T> where T : class
{
public T Value()
{
return default(T);
}
}
```
i've an exception:
`Uncaught TypeError: lst.Module2$Demo$ILazy$1$Module1$Demo$Class1$Value is not a function
at Function.Ololo`
### Here is generated code:
```js
Ololo: function (lst) {
lst.Module2$Demo$ILazy$1$Module1$Demo$Class1$Value();
}
```
but in js object i have value: `lst.Module2$Demo$ILazy$1$Demo$Class1$Value`.
in my opinion, generated code is right, but wrong in my object
|
1.0
|
Error with generics in Module - A description of the issue.
### Steps To Reproduce
https://deck.net/a62bd78c412c66b2194b59cc88ab0be9
```csharp
[Module(Bridge.ModuleType.UMD)]
public class Program
{
public static ILazy<Class1> lazyClass1;
public static void Main()
{
lazyClass1 = new Lazy<Class1>();
Ololo(lazyClass1);
}
internal static void Ololo(ILazy<Class1> lst)
{
lst.Value();
}
}
[Module(Bridge.ModuleType.UMD, "Module1")]
public class Class1
{
}
[Module(Bridge.ModuleType.UMD, "Module2")]
public interface ILazy<T> where T : class
{
/// <summary>
/// Get Resolved Type T
/// </summary>
/// <returns>Resolved Type T</returns>
T Value();
}
[Module(Bridge.ModuleType.UMD, "Module2")]
public class Lazy<T> : ILazy<T> where T : class
{
public T Value()
{
return default(T);
}
}
```
i've an exception:
`Uncaught TypeError: lst.Module2$Demo$ILazy$1$Module1$Demo$Class1$Value is not a function
at Function.Ololo`
### Here is generated code:
```js
Ololo: function (lst) {
lst.Module2$Demo$ILazy$1$Module1$Demo$Class1$Value();
}
```
but in js object i have value: `lst.Module2$Demo$ILazy$1$Demo$Class1$Value`.
in my opinion, generated code is right, but wrong in my object
|
non_test
|
error with generics in module a description of the issue steps to reproduce csharp public class program public static ilazy public static void main new lazy ololo internal static void ololo ilazy lst lst value public class public interface ilazy where t class get resolved type t resolved type t t value public class lazy ilazy where t class public t value return default t i ve an exception uncaught typeerror lst demo ilazy demo value is not a function at function ololo here is generated code js ololo function lst lst demo ilazy demo value but in js object i have value lst demo ilazy demo value in my opinion generated code is right but wrong in my object
| 0
|
51,971
| 6,205,147,883
|
IssuesEvent
|
2017-07-06 15:33:37
|
ProjectSidewalk/SidewalkWebpage
|
https://api.github.com/repos/ProjectSidewalk/SidewalkWebpage
|
closed
|
Sign-in during missions changes progress
|
bug Priority: Low Relaunch Testing
|
Related to #734 and #285. Signing in during the middle of a mission adds to current mission progress after jumping to a new mission.
|
1.0
|
Sign-in during missions changes progress - Related to #734 and #285. Signing in during the middle of a mission adds to current mission progress after jumping to a new mission.
|
test
|
sign in during missions changes progress related to and signing in during the middle of a mission adds to current mission progress after jumping to a new mission
| 1
|
638,958
| 20,743,345,265
|
IssuesEvent
|
2022-03-14 19:59:17
|
opendp/dpcreator
|
https://api.github.com/repos/opendp/dpcreator
|
closed
|
display 3 decimal places for epsilon
|
DP Creator demo-priority UI Related
|
On the Create statistics page, display 3 decimal places for epsilon
|
1.0
|
display 3 decimal places for epsilon - On the Create statistics page, display 3 decimal places for epsilon
|
non_test
|
display decimal places for epsilon on the create statistics page display decimal places for epsilon
| 0
|
246,861
| 20,922,212,265
|
IssuesEvent
|
2022-03-24 18:30:50
|
pytorch/pytorch
|
https://api.github.com/repos/pytorch/pytorch
|
closed
|
DISABLED test_script_pack_padded_sequence (test_jit.TestScript)
|
high priority oncall: jit triaged module: flaky-tests skipped
|
Previous failed runs:
https://circleci.com/gh/pytorch/pytorch/4682966
Subsequent succeeded runs:
https://circleci.com/gh/pytorch/pytorch/4682247
https://circleci.com/gh/pytorch/pytorch/4682241
Today, it consistently fails:
https://circleci.com/gh/pytorch/pytorch/4687625
https://circleci.com/gh/pytorch/pytorch/4687610
https://circleci.com/gh/pytorch/pytorch/4686149
@ljk53 tried reverting the seemingly culprit PR #32814 and #34055, but the error persist.
I am going to disable this test while JIT team investigating it.
cc @ezyang @gchanan @zou3519 @bdhirsh @suo
|
1.0
|
DISABLED test_script_pack_padded_sequence (test_jit.TestScript) - Previous failed runs:
https://circleci.com/gh/pytorch/pytorch/4682966
Subsequent succeeded runs:
https://circleci.com/gh/pytorch/pytorch/4682247
https://circleci.com/gh/pytorch/pytorch/4682241
Today, it consistently fails:
https://circleci.com/gh/pytorch/pytorch/4687625
https://circleci.com/gh/pytorch/pytorch/4687610
https://circleci.com/gh/pytorch/pytorch/4686149
@ljk53 tried reverting the seemingly culprit PR #32814 and #34055, but the error persist.
I am going to disable this test while JIT team investigating it.
cc @ezyang @gchanan @zou3519 @bdhirsh @suo
|
test
|
disabled test script pack padded sequence test jit testscript previous failed runs subsequent succeeded runs today it consistently fails tried reverting the seemingly culprit pr and but the error persist i am going to disable this test while jit team investigating it cc ezyang gchanan bdhirsh suo
| 1
|
281,086
| 24,361,714,082
|
IssuesEvent
|
2022-10-03 12:17:00
|
mozilla-mobile/fenix
|
https://api.github.com/repos/mozilla-mobile/fenix
|
closed
|
Intermittent UI test failure - selectAllAndCopyTextTest
|
eng:intermittent-test eng:disabled-test eng:ui-test
|
### Firebase Test Run:
https://console.firebase.google.com/project/moz-fenix/testlab/histories/bh.66b7091e15d53d45/matrices/5675668473229135495/executions/bs.8a87d572c8c3fc08
### Stacktrace:
`java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:87)
at org.junit.Assert.assertTrue(Assert.java:42)
at org.junit.Assert.assertNotNull(Assert.java:713)
at org.junit.Assert.assertNotNull(Assert.java:723)
at org.mozilla.fenix.helpers.ext.WaitNotNullKt.waitNotNull(WaitNotNull.kt:20)
at org.mozilla.fenix.ui.robots.NavigationToolbarRobotKt.openEditURLView(NavigationToolbarRobot.kt:255)
at org.mozilla.fenix.ui.robots.NavigationToolbarRobot$Transition.enterURLAndEnterToBrowser(NavigationToolbarRobot.kt:95)
at org.mozilla.fenix.ui.SmokeTest.selectAllAndCopyTextTest(SmokeTest.kt:942)`
### Build:
8/25 main
┆Issue is synchronized with this [Jira Task](https://mozilla-hub.atlassian.net/browse/FNXV2-21401)
|
3.0
|
Intermittent UI test failure - selectAllAndCopyTextTest - ### Firebase Test Run:
https://console.firebase.google.com/project/moz-fenix/testlab/histories/bh.66b7091e15d53d45/matrices/5675668473229135495/executions/bs.8a87d572c8c3fc08
### Stacktrace:
`java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:87)
at org.junit.Assert.assertTrue(Assert.java:42)
at org.junit.Assert.assertNotNull(Assert.java:713)
at org.junit.Assert.assertNotNull(Assert.java:723)
at org.mozilla.fenix.helpers.ext.WaitNotNullKt.waitNotNull(WaitNotNull.kt:20)
at org.mozilla.fenix.ui.robots.NavigationToolbarRobotKt.openEditURLView(NavigationToolbarRobot.kt:255)
at org.mozilla.fenix.ui.robots.NavigationToolbarRobot$Transition.enterURLAndEnterToBrowser(NavigationToolbarRobot.kt:95)
at org.mozilla.fenix.ui.SmokeTest.selectAllAndCopyTextTest(SmokeTest.kt:942)`
### Build:
8/25 main
┆Issue is synchronized with this [Jira Task](https://mozilla-hub.atlassian.net/browse/FNXV2-21401)
|
test
|
intermittent ui test failure selectallandcopytexttest firebase test run stacktrace java lang assertionerror at org junit assert fail assert java at org junit assert asserttrue assert java at org junit assert assertnotnull assert java at org junit assert assertnotnull assert java at org mozilla fenix helpers ext waitnotnullkt waitnotnull waitnotnull kt at org mozilla fenix ui robots navigationtoolbarrobotkt openediturlview navigationtoolbarrobot kt at org mozilla fenix ui robots navigationtoolbarrobot transition enterurlandentertobrowser navigationtoolbarrobot kt at org mozilla fenix ui smoketest selectallandcopytexttest smoketest kt build main ┆issue is synchronized with this
| 1
|
194,989
| 14,698,212,623
|
IssuesEvent
|
2021-01-04 05:53:03
|
github-vet/rangeloop-pointer-findings
|
https://api.github.com/repos/github-vet/rangeloop-pointer-findings
|
closed
|
apache/trafficcontrol: traffic_ops/testing/api/v1/profile_parameters_test.go; 9 LoC
|
fresh test tiny
|
Found a possible issue in [apache/trafficcontrol](https://www.github.com/apache/trafficcontrol) at [traffic_ops/testing/api/v1/profile_parameters_test.go](https://github.com/apache/trafficcontrol/blob/5ccc77a18d2f6ae451b26109895661741257e0c8/traffic_ops/testing/api/v1/profile_parameters_test.go#L132-L140)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.
> range-loop variable pp used in defer or goroutine at line 137
[Click here to see the code in its original context.](https://github.com/apache/trafficcontrol/blob/5ccc77a18d2f6ae451b26109895661741257e0c8/traffic_ops/testing/api/v1/profile_parameters_test.go#L132-L140)
<details>
<summary>Click here to show the 9 line(s) of Go which triggered the analyzer.</summary>
```go
for _, pp := range testData.ProfileParameters {
wg.Add(1)
go func() {
defer wg.Done()
DeleteTestProfileParameter(t, pp)
}()
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: 5ccc77a18d2f6ae451b26109895661741257e0c8
|
1.0
|
apache/trafficcontrol: traffic_ops/testing/api/v1/profile_parameters_test.go; 9 LoC -
Found a possible issue in [apache/trafficcontrol](https://www.github.com/apache/trafficcontrol) at [traffic_ops/testing/api/v1/profile_parameters_test.go](https://github.com/apache/trafficcontrol/blob/5ccc77a18d2f6ae451b26109895661741257e0c8/traffic_ops/testing/api/v1/profile_parameters_test.go#L132-L140)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.
> range-loop variable pp used in defer or goroutine at line 137
[Click here to see the code in its original context.](https://github.com/apache/trafficcontrol/blob/5ccc77a18d2f6ae451b26109895661741257e0c8/traffic_ops/testing/api/v1/profile_parameters_test.go#L132-L140)
<details>
<summary>Click here to show the 9 line(s) of Go which triggered the analyzer.</summary>
```go
for _, pp := range testData.ProfileParameters {
wg.Add(1)
go func() {
defer wg.Done()
DeleteTestProfileParameter(t, pp)
}()
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: 5ccc77a18d2f6ae451b26109895661741257e0c8
|
test
|
apache trafficcontrol traffic ops testing api profile parameters test go loc found a possible issue in at below is the message reported by the analyzer for this snippet of code beware that the analyzer only reports the first issue it finds so please do not limit your consideration to the contents of the below message range loop variable pp used in defer or goroutine at line click here to show the line s of go which triggered the analyzer go for pp range testdata profileparameters wg add go func defer wg done deletetestprofileparameter t pp leave a reaction on this issue to contribute to the project by classifying this instance as a bug mitigated or desirable behavior rocket see the descriptions of the classifications for more information commit id
| 1
|
156,630
| 13,652,033,685
|
IssuesEvent
|
2020-09-27 05:03:52
|
nucypher/nucypher
|
https://api.github.com/repos/nucypher/nucypher
|
opened
|
Clarify Worker requirements "Dedicated Machine" -> "Machine or VPS"
|
Documentation
|
We do not mean to indicate that "dedicated hardware" as offered by some cloud providers is required.
|
1.0
|
Clarify Worker requirements "Dedicated Machine" -> "Machine or VPS" - We do not mean to indicate that "dedicated hardware" as offered by some cloud providers is required.
|
non_test
|
clarify worker requirements dedicated machine machine or vps we do not mean to indicate that dedicated hardware as offered by some cloud providers is required
| 0
|
128,397
| 10,531,317,806
|
IssuesEvent
|
2019-10-01 08:15:14
|
voyages-sncf-technologies/hesperides
|
https://api.github.com/repos/voyages-sncf-technologies/hesperides
|
closed
|
Global property usage in iterable properties
|
bug good first issue test-manquant user request v3
|
The feature that allow to find usage of global properties doesn't work if the global property is referenced in an iterable section.
|
1.0
|
Global property usage in iterable properties - The feature that allow to find usage of global properties doesn't work if the global property is referenced in an iterable section.
|
test
|
global property usage in iterable properties the feature that allow to find usage of global properties doesn t work if the global property is referenced in an iterable section
| 1
|
63,958
| 6,888,991,168
|
IssuesEvent
|
2017-11-22 08:47:58
|
EyeSeeTea/dhis2-android-trackercapture
|
https://api.github.com/repos/EyeSeeTea/dhis2-android-trackercapture
|
closed
|
Implement URL, Datetime and Time types
|
complexity - med (1-5hr) priority - high testing type - feature
|
@idelcano please just assess the dimension of this task and talk to me before doing anything
|
1.0
|
Implement URL, Datetime and Time types - @idelcano please just assess the dimension of this task and talk to me before doing anything
|
test
|
implement url datetime and time types idelcano please just assess the dimension of this task and talk to me before doing anything
| 1
|
134,395
| 10,906,262,527
|
IssuesEvent
|
2019-11-20 12:34:22
|
Laravel-Backpack/CRUD
|
https://api.github.com/repos/Laravel-Backpack/CRUD
|
closed
|
[4.0.7] select2_ajax filter breaks "Remove filters" button
|
testing or needs confirmation working on it
|
# Bug report
### What I did
1 - Add a select2_ajax filter
2 - Filter the results
3 - Click in the "Remove filters" button
### What I expected to happen
The filters should be removed
### What happened
The filter is removed from the interface, but the list return zero results:
### What I've already tried to fix it
What I can tell is that the filter key is still present when we remove the filter, but it has no value.
To avoid the empty results I added a check in the filter function:
### Backpack, Laravel, PHP, DB version
### PHP VERSION:
PHP 7.2.22 (cli) (built: Sep 8 2019 15:19:13) ( NTS )
### LARAVEL VERSION:
laravel/framework v6.1.0
### BACKPACK VERSION:
backpack/crud 4.0.7
backpack/generators 2.0.4
backpack/permissionmanager 5.0.1
|
1.0
|
[4.0.7] select2_ajax filter breaks "Remove filters" button - # Bug report
### What I did
1 - Add a select2_ajax filter
2 - Filter the results
3 - Click in the "Remove filters" button
### What I expected to happen
The filters should be removed
### What happened
The filter is removed from the interface, but the list return zero results:
### What I've already tried to fix it
What I can tell is that the filter key is still present when we remove the filter, but it has no value.
To avoid the empty results I added a check in the filter function:
### Backpack, Laravel, PHP, DB version
### PHP VERSION:
PHP 7.2.22 (cli) (built: Sep 8 2019 15:19:13) ( NTS )
### LARAVEL VERSION:
laravel/framework v6.1.0
### BACKPACK VERSION:
backpack/crud 4.0.7
backpack/generators 2.0.4
backpack/permissionmanager 5.0.1
|
test
|
ajax filter breaks remove filters button bug report what i did add a ajax filter filter the results click in the remove filters button what i expected to happen the filters should be removed what happened the filter is removed from the interface but the list return zero results what i ve already tried to fix it what i can tell is that the filter key is still present when we remove the filter but it has no value to avoid the empty results i added a check in the filter function backpack laravel php db version php version php cli built sep nts laravel version laravel framework backpack version backpack crud backpack generators backpack permissionmanager
| 1
|
141,006
| 11,387,011,498
|
IssuesEvent
|
2020-01-29 14:19:33
|
MachoThemes/modula-importer
|
https://api.github.com/repos/MachoThemes/modula-importer
|
closed
|
Rename to "Migrate" instead of importer
|
enhancement needs testing
|
Import/Export means moving existing albums/galleries to another site.
This is a migration tool from other galleries.
|
1.0
|
Rename to "Migrate" instead of importer - Import/Export means moving existing albums/galleries to another site.
This is a migration tool from other galleries.
|
test
|
rename to migrate instead of importer import export means moving existing albums galleries to another site this is a migration tool from other galleries
| 1
|
311,851
| 26,821,115,634
|
IssuesEvent
|
2023-02-02 09:32:56
|
wazuh/wazuh
|
https://api.github.com/repos/wazuh/wazuh
|
opened
|
Design and develop new API integration tests for `POST /events`
|
type/enhancement type/test module/api team/framework
|
## Description
As part of https://github.com/wazuh/wazuh/issues/16067, we need to design new AIT for the proposed endpoint. This development will follow **TDD**, making this issue a blocker for the main developing one.
Since the tests must consider and expect all kind of query parameters, JSON bodies and responses; we need to first design all of them in this issue before implementing them.
## Checks
The following elements have been updated or reviewed (should also be checked if no modification is required):
- [ ] Tests (unit tests, API integration tests).
- [ ] Changelog.
- [ ] Documentation.
- [ ] Integration test mapping (using `api/test/integration/mapping/_test_mapping.py`).
|
1.0
|
Design and develop new API integration tests for `POST /events` - ## Description
As part of https://github.com/wazuh/wazuh/issues/16067, we need to design new AIT for the proposed endpoint. This development will follow **TDD**, making this issue a blocker for the main developing one.
Since the tests must consider and expect all kind of query parameters, JSON bodies and responses; we need to first design all of them in this issue before implementing them.
## Checks
The following elements have been updated or reviewed (should also be checked if no modification is required):
- [ ] Tests (unit tests, API integration tests).
- [ ] Changelog.
- [ ] Documentation.
- [ ] Integration test mapping (using `api/test/integration/mapping/_test_mapping.py`).
|
test
|
design and develop new api integration tests for post events description as part of we need to design new ait for the proposed endpoint this development will follow tdd making this issue a blocker for the main developing one since the tests must consider and expect all kind of query parameters json bodies and responses we need to first design all of them in this issue before implementing them checks the following elements have been updated or reviewed should also be checked if no modification is required tests unit tests api integration tests changelog documentation integration test mapping using api test integration mapping test mapping py
| 1
|
150,241
| 5,741,388,106
|
IssuesEvent
|
2017-04-24 05:27:25
|
turt2live/matrix-voyager-bot
|
https://api.github.com/repos/turt2live/matrix-voyager-bot
|
closed
|
Cannot link yourself a room anymore
|
bug priority
|
There's a database error related to a column not being found on the links table in the log.
|
1.0
|
Cannot link yourself a room anymore - There's a database error related to a column not being found on the links table in the log.
|
non_test
|
cannot link yourself a room anymore there s a database error related to a column not being found on the links table in the log
| 0
|
350,117
| 24,969,299,366
|
IssuesEvent
|
2022-11-01 22:41:42
|
arkinmodi/project-sayyara
|
https://api.github.com/repos/arkinmodi/project-sayyara
|
opened
|
[Design] Design Documentation
|
documentation Epic needs breakdown
|
**[MG Report](https://github.com/arkinmodi/project-sayyara/blob/main/docs/Design/MG/MG.pdf) | [MIS Report](https://github.com/arkinmodi/project-sayyara/blob/main/docs/Design/MIS/MIS.pdf) | [Rubric](https://gitlab.cas.mcmaster.ca/courses/capstone/-/blob/main/Rubrics/DesDoc.xlsx) | [Examples](https://gitlab.cas.mcmaster.ca/courses/capstone/-/tree/main/SamplesOfStudentWork/Design)**
**Reference Slides**
- [Lecture ??](https://gitlab.cas.mcmaster.ca/courses/capstone/-/blob/main/Lectures)
### Sections
- [ ] ...
|
1.0
|
[Design] Design Documentation - **[MG Report](https://github.com/arkinmodi/project-sayyara/blob/main/docs/Design/MG/MG.pdf) | [MIS Report](https://github.com/arkinmodi/project-sayyara/blob/main/docs/Design/MIS/MIS.pdf) | [Rubric](https://gitlab.cas.mcmaster.ca/courses/capstone/-/blob/main/Rubrics/DesDoc.xlsx) | [Examples](https://gitlab.cas.mcmaster.ca/courses/capstone/-/tree/main/SamplesOfStudentWork/Design)**
**Reference Slides**
- [Lecture ??](https://gitlab.cas.mcmaster.ca/courses/capstone/-/blob/main/Lectures)
### Sections
- [ ] ...
|
non_test
|
design documentation reference slides sections
| 0
|
64,895
| 26,904,399,500
|
IssuesEvent
|
2023-02-06 17:52:52
|
master-co/css
|
https://api.github.com/repos/master-co/css
|
closed
|
✨ Hover and preview CSS rules with `config.classes`
|
enhancement language service
|
### Description
Here are the features currently supported by Master CSS Language Service:
<img width="681" alt="Screenshot 2023-02-03 at 6 19 26 PM" src="https://user-images.githubusercontent.com/33840671/216575176-2379d8e9-f7e2-4d39-b91e-54156160c3a3.png">
master.css.js
```ts
export const config = {
classes: {
btn: 'font:14 p:8|16'
}
}
```
When you hover over the `btn` class in the markup:
```html
<a class="btn">
```
You can preview the CSS rules generated by `btn`:
```css
.btn, .font\:14 {
font-size: 0.875rem
}
.btn, .p\:8\|16 {
padding: 0.5rem 1rem
}
```
|
1.0
|
✨ Hover and preview CSS rules with `config.classes` - ### Description
Here are the features currently supported by Master CSS Language Service:
<img width="681" alt="Screenshot 2023-02-03 at 6 19 26 PM" src="https://user-images.githubusercontent.com/33840671/216575176-2379d8e9-f7e2-4d39-b91e-54156160c3a3.png">
master.css.js
```ts
export const config = {
classes: {
btn: 'font:14 p:8|16'
}
}
```
When you hover over the `btn` class in the markup:
```html
<a class="btn">
```
You can preview the CSS rules generated by `btn`:
```css
.btn, .font\:14 {
font-size: 0.875rem
}
.btn, .p\:8\|16 {
padding: 0.5rem 1rem
}
```
|
non_test
|
✨ hover and preview css rules with config classes description here are the features currently supported by master css language service img width alt screenshot at pm src master css js ts export const config classes btn font p when you hover over the btn class in the markup html you can preview the css rules generated by btn css btn font font size btn p padding
| 0
|
34,365
| 7,447,788,689
|
IssuesEvent
|
2018-03-28 13:35:50
|
kerdokullamae/test_koik_issued
|
https://api.github.com/repos/kerdokullamae/test_koik_issued
|
closed
|
Puuduvad Isiku andmeväljad Nimetuse lühendid ja Nimevormid
|
P: high R: invalid T: defect
|
**Reported by aadikaljuvee on 19 Sep 2012 13:31 UTC**
Isiku/Org. andmeväljadest puuduvad "Nimetuse lühendid" ja "Nimevormid"
|
1.0
|
Puuduvad Isiku andmeväljad Nimetuse lühendid ja Nimevormid - **Reported by aadikaljuvee on 19 Sep 2012 13:31 UTC**
Isiku/Org. andmeväljadest puuduvad "Nimetuse lühendid" ja "Nimevormid"
|
non_test
|
puuduvad isiku andmeväljad nimetuse lühendid ja nimevormid reported by aadikaljuvee on sep utc isiku org andmeväljadest puuduvad nimetuse lühendid ja nimevormid
| 0
|
96,982
| 8,639,112,254
|
IssuesEvent
|
2018-11-23 17:11:08
|
SME-Issues/issues
|
https://api.github.com/repos/SME-Issues/issues
|
closed
|
Query Balance Tests Multiple Contexts - 23/11/2018 - 5004
|
NLP Api pulse_tests
|
**Query Balance Tests Multiple Contexts**
- Total: 6
- Passed: 1
- **Full Pass: 1 (25%)**
- Not Understood: 0
- Error (not understood): 2
- Failed but Understood: 3 (75%)
|
1.0
|
Query Balance Tests Multiple Contexts - 23/11/2018 - 5004 - **Query Balance Tests Multiple Contexts**
- Total: 6
- Passed: 1
- **Full Pass: 1 (25%)**
- Not Understood: 0
- Error (not understood): 2
- Failed but Understood: 3 (75%)
|
test
|
query balance tests multiple contexts query balance tests multiple contexts total passed full pass not understood error not understood failed but understood
| 1
|
99,496
| 8,701,814,365
|
IssuesEvent
|
2018-12-05 12:43:46
|
nhsconnect/gpconnect-provider-testing
|
https://api.github.com/repos/nhsconnect/gpconnect-provider-testing
|
closed
|
Check the JWT has a correct 'header part' as per the spec
|
Automated test Core
|
The demonstrator (both versions) is having a check added to ensure the JWT header part is correctly populated as per the spec:
https://github.com/nhsconnect/gpconnect-demonstrator/issues/155
To make sure that the provider test suite continues to function without problem, this ticket is to verify that the test suite is indeed sending the 'header part' through correctly, and if not, to add this in.
The correct header part looks like this (before being encoding):
{
"alg": "none",
"typ": "JWT"
}
|
1.0
|
Check the JWT has a correct 'header part' as per the spec - The demonstrator (both versions) is having a check added to ensure the JWT header part is correctly populated as per the spec:
https://github.com/nhsconnect/gpconnect-demonstrator/issues/155
To make sure that the provider test suite continues to function without problem, this ticket is to verify that the test suite is indeed sending the 'header part' through correctly, and if not, to add this in.
The correct header part looks like this (before being encoding):
{
"alg": "none",
"typ": "JWT"
}
|
test
|
check the jwt has a correct header part as per the spec the demonstrator both versions is having a check added to ensure the jwt header part is correctly populated as per the spec to make sure that the provider test suite continues to function without problem this ticket is to verify that the test suite is indeed sending the header part through correctly and if not to add this in the correct header part looks like this before being encoding alg none typ jwt
| 1
|
263,444
| 23,058,588,673
|
IssuesEvent
|
2022-07-25 07:51:25
|
wso2/product-is
|
https://api.github.com/repos/wso2/product-is
|
closed
|
Cannot create organizations with the same organization name
|
ui Priority/High Severity/Major bug QA-Reported IS-6.0.0-Test-Hackathon frontend Organization Management
|
**Describe the issue:**
As I got to know, we can create organizations with the same name as there are no restrictions on the backend side. But when trying to create an organization with the same name under the sub-organization, it doesn't allow to create it.
https://user-images.githubusercontent.com/13362482/180147737-2dcaffc8-5f87-4e88-b6d7-2c2e0aad7237.mov
**How to reproduce:**
- Log in to the console (https://localhost:9443/console) as an admin user
- Create an organization with the name 'Star'
- Create another organization called 'MedLife'
- Create a sub org under MedLife with the same name 'Star'
- Even though it's a child org of a sub-organization of MedLife, It won't allow the creation of an organization with the same name.
- It validates the case-sensitiveness when creating organizations.
**Expected behavior:**
There can be scenarios to have the same name when creating organizations. Hence users should be able to create organizations with the same name.
**Environment information** (_Please complete the following information; remove any unnecessary fields_) **:**
- Product Version: [e.g., IS 5.10.0, IS 5.9.0]
- OS: [e.g., Windows, Linux, Mac]
- Database: [e.g., MySQL, H2]
- Userstore: [e.g., LDAP, JDBC]
---
### Optional Fields
**Related issues:**
<!-- Any related issues from this/other repositories-->
**Suggested labels:**
<!-- Only to be used by non-members -->
|
1.0
|
Cannot create organizations with the same organization name - **Describe the issue:**
As I got to know, we can create organizations with the same name as there are no restrictions on the backend side. But when trying to create an organization with the same name under the sub-organization, it doesn't allow to create it.
https://user-images.githubusercontent.com/13362482/180147737-2dcaffc8-5f87-4e88-b6d7-2c2e0aad7237.mov
**How to reproduce:**
- Log in to the console (https://localhost:9443/console) as an admin user
- Create an organization with the name 'Star'
- Create another organization called 'MedLife'
- Create a sub org under MedLife with the same name 'Star'
- Even though it's a child org of a sub-organization of MedLife, It won't allow the creation of an organization with the same name.
- It validates the case-sensitiveness when creating organizations.
**Expected behavior:**
There can be scenarios to have the same name when creating organizations. Hence users should be able to create organizations with the same name.
**Environment information** (_Please complete the following information; remove any unnecessary fields_) **:**
- Product Version: [e.g., IS 5.10.0, IS 5.9.0]
- OS: [e.g., Windows, Linux, Mac]
- Database: [e.g., MySQL, H2]
- Userstore: [e.g., LDAP, JDBC]
---
### Optional Fields
**Related issues:**
<!-- Any related issues from this/other repositories-->
**Suggested labels:**
<!-- Only to be used by non-members -->
|
test
|
cannot create organizations with the same organization name describe the issue as i got to know we can create organizations with the same name as there are no restrictions on the backend side but when trying to create an organization with the same name under the sub organization it doesn t allow to create it how to reproduce log in to the console as an admin user create an organization with the name star create another organization called medlife create a sub org under medlife with the same name star even though it s a child org of a sub organization of medlife it won t allow the creation of an organization with the same name it validates the case sensitiveness when creating organizations expected behavior there can be scenarios to have the same name when creating organizations hence users should be able to create organizations with the same name environment information please complete the following information remove any unnecessary fields product version os database userstore optional fields related issues suggested labels
| 1
|
244,748
| 26,472,740,304
|
IssuesEvent
|
2023-01-17 08:50:21
|
postgres-ai/database-lab-engine
|
https://api.github.com/repos/postgres-ai/database-lab-engine
|
closed
|
CVE-2022-37599 (High) detected in loader-utils-2.0.2.tgz, loader-utils-2.0.0.tgz
|
security vulnerability
|
## CVE-2022-37599 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>loader-utils-2.0.2.tgz</b>, <b>loader-utils-2.0.0.tgz</b></p></summary>
<p>
<details><summary><b>loader-utils-2.0.2.tgz</b></p></summary>
<p>utils for webpack loaders</p>
<p>Library home page: <a href="https://registry.npmjs.org/loader-utils/-/loader-utils-2.0.2.tgz">https://registry.npmjs.org/loader-utils/-/loader-utils-2.0.2.tgz</a></p>
<p>
Dependency Hierarchy:
- @postgres.ai/ce-1.0.0.tgz (Root Library)
- react-scripts-5.0.1.tgz
- webpack-5.5.0.tgz
- :x: **loader-utils-2.0.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>loader-utils-2.0.0.tgz</b></p></summary>
<p>utils for webpack loaders</p>
<p>Library home page: <a href="https://registry.npmjs.org/loader-utils/-/loader-utils-2.0.0.tgz">https://registry.npmjs.org/loader-utils/-/loader-utils-2.0.0.tgz</a></p>
<p>
Dependency Hierarchy:
- @postgres.ai/ce-1.0.0.tgz (Root Library)
- react-scripts-5.0.1.tgz
- file-loader-6.2.0.tgz
- :x: **loader-utils-2.0.0.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/postgres-ai/database-lab-engine/commit/b3ac62d12e3d43994ff7ad836e34da801ed665fb">b3ac62d12e3d43994ff7ad836e34da801ed665fb</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A Regular expression denial of service (ReDoS) flaw was found in Function interpolateName in interpolateName.js in webpack loader-utils 2.0.0 via the resourcePath variable in interpolateName.js.
<p>Publish Date: 2022-10-11
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-37599>CVE-2022-37599</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-hhq3-ff78-jv3g">https://github.com/advisories/GHSA-hhq3-ff78-jv3g</a></p>
<p>Release Date: 2022-10-11</p>
<p>Fix Resolution: loader-utils - 1.4.2,2.0.4,3.2.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2022-37599 (High) detected in loader-utils-2.0.2.tgz, loader-utils-2.0.0.tgz - ## CVE-2022-37599 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>loader-utils-2.0.2.tgz</b>, <b>loader-utils-2.0.0.tgz</b></p></summary>
<p>
<details><summary><b>loader-utils-2.0.2.tgz</b></p></summary>
<p>utils for webpack loaders</p>
<p>Library home page: <a href="https://registry.npmjs.org/loader-utils/-/loader-utils-2.0.2.tgz">https://registry.npmjs.org/loader-utils/-/loader-utils-2.0.2.tgz</a></p>
<p>
Dependency Hierarchy:
- @postgres.ai/ce-1.0.0.tgz (Root Library)
- react-scripts-5.0.1.tgz
- webpack-5.5.0.tgz
- :x: **loader-utils-2.0.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>loader-utils-2.0.0.tgz</b></p></summary>
<p>utils for webpack loaders</p>
<p>Library home page: <a href="https://registry.npmjs.org/loader-utils/-/loader-utils-2.0.0.tgz">https://registry.npmjs.org/loader-utils/-/loader-utils-2.0.0.tgz</a></p>
<p>
Dependency Hierarchy:
- @postgres.ai/ce-1.0.0.tgz (Root Library)
- react-scripts-5.0.1.tgz
- file-loader-6.2.0.tgz
- :x: **loader-utils-2.0.0.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/postgres-ai/database-lab-engine/commit/b3ac62d12e3d43994ff7ad836e34da801ed665fb">b3ac62d12e3d43994ff7ad836e34da801ed665fb</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A Regular expression denial of service (ReDoS) flaw was found in Function interpolateName in interpolateName.js in webpack loader-utils 2.0.0 via the resourcePath variable in interpolateName.js.
<p>Publish Date: 2022-10-11
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-37599>CVE-2022-37599</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-hhq3-ff78-jv3g">https://github.com/advisories/GHSA-hhq3-ff78-jv3g</a></p>
<p>Release Date: 2022-10-11</p>
<p>Fix Resolution: loader-utils - 1.4.2,2.0.4,3.2.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_test
|
cve high detected in loader utils tgz loader utils tgz cve high severity vulnerability vulnerable libraries loader utils tgz loader utils tgz loader utils tgz utils for webpack loaders library home page a href dependency hierarchy postgres ai ce tgz root library react scripts tgz webpack tgz x loader utils tgz vulnerable library loader utils tgz utils for webpack loaders library home page a href dependency hierarchy postgres ai ce tgz root library react scripts tgz file loader tgz x loader utils tgz vulnerable library found in head commit a href found in base branch master vulnerability details a regular expression denial of service redos flaw was found in function interpolatename in interpolatename js in webpack loader utils via the resourcepath variable in interpolatename js publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution loader utils step up your open source security game with mend
| 0
|
175,749
| 13,608,162,059
|
IssuesEvent
|
2020-09-23 01:34:10
|
kubernetes/kubernetes
|
https://api.github.com/repos/kubernetes/kubernetes
|
closed
|
scheduler_perf: use time.Ticker in throughput measurement
|
kind/cleanup sig/scheduling sig/testing
|
https://github.com/kubernetes/kubernetes/blob/b56d0acaf5bead31bd17d3b88d4a167fcbac7866/test/integration/scheduler_perf/util.go#L244
https://golang.org/pkg/time/#Ticker
/sig scheduling
/sig testing
/assign
|
1.0
|
scheduler_perf: use time.Ticker in throughput measurement - https://github.com/kubernetes/kubernetes/blob/b56d0acaf5bead31bd17d3b88d4a167fcbac7866/test/integration/scheduler_perf/util.go#L244
https://golang.org/pkg/time/#Ticker
/sig scheduling
/sig testing
/assign
|
test
|
scheduler perf use time ticker in throughput measurement sig scheduling sig testing assign
| 1
|
24,982
| 5,115,645,207
|
IssuesEvent
|
2017-01-06 22:29:41
|
heidelberg-makerspace/do-something
|
https://api.github.com/repos/heidelberg-makerspace/do-something
|
closed
|
laser exhaust system asks for maintenance
|
cleaning documentation Laser cutter
|
Our exhaust system (VacuAir UML 500, not listed in [cameo's selection](https://www.cameo-laser.de/de/systeme/absauganlagen/) anymore) has a flashing red/green light and the remote reads "Sichtkontrolle" or "Wartung Akt. Kohle" if you confirm having looked inside.
It appears this is more than just a "I've run for 100 h, please check me" thing, unfortunately there does not seem to be a manual... I'll get in touch with our technician and ask for one.
|
1.0
|
laser exhaust system asks for maintenance - Our exhaust system (VacuAir UML 500, not listed in [cameo's selection](https://www.cameo-laser.de/de/systeme/absauganlagen/) anymore) has a flashing red/green light and the remote reads "Sichtkontrolle" or "Wartung Akt. Kohle" if you confirm having looked inside.
It appears this is more than just a "I've run for 100 h, please check me" thing, unfortunately there does not seem to be a manual... I'll get in touch with our technician and ask for one.
|
non_test
|
laser exhaust system asks for maintenance our exhaust system vacuair uml not listed in anymore has a flashing red green light and the remote reads sichtkontrolle or wartung akt kohle if you confirm having looked inside it appears this is more than just a i ve run for h please check me thing unfortunately there does not seem to be a manual i ll get in touch with our technician and ask for one
| 0
|
233,014
| 7,688,993,564
|
IssuesEvent
|
2018-05-17 11:15:15
|
webcompat/web-bugs
|
https://api.github.com/repos/webcompat/web-bugs
|
closed
|
keep.google.com - see bug description
|
browser-firefox priority-critical
|
<!-- @browser: Firefox 61.0 -->
<!-- @ua_header: Mozilla/5.0 (X11; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0 -->
<!-- @reported_with: desktop-reporter -->
**URL**: https://keep.google.com/#home
**Browser / Version**: Firefox 61.0
**Operating System**: Linux
**Tested Another Browser**: Yes
**Problem type**: Something else
**Description**: Scrolling inside a focused note can sometimes also scroll the background page of notes
**Steps to Reproduce**:
1. Click to focus note
2. Scroll rapidly up and down inside note (easier with smooth-scrolling touchpad like Macbook Pro)
It might be easier to reproduce using a note that doesn't have its own scrollbar.
<details>
<summary>Browser Configuration</summary>
<ul>
<li>buildID: 20180515122839</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.all: false</li><li>layers.acceleration.force-enabled: false</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>channel: aurora</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_
|
1.0
|
keep.google.com - see bug description - <!-- @browser: Firefox 61.0 -->
<!-- @ua_header: Mozilla/5.0 (X11; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0 -->
<!-- @reported_with: desktop-reporter -->
**URL**: https://keep.google.com/#home
**Browser / Version**: Firefox 61.0
**Operating System**: Linux
**Tested Another Browser**: Yes
**Problem type**: Something else
**Description**: Scrolling inside a focused note can sometimes also scroll the background page of notes
**Steps to Reproduce**:
1. Click to focus note
2. Scroll rapidly up and down inside note (easier with smooth-scrolling touchpad like Macbook Pro)
It might be easier to reproduce using a note that doesn't have its own scrollbar.
<details>
<summary>Browser Configuration</summary>
<ul>
<li>buildID: 20180515122839</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.all: false</li><li>layers.acceleration.force-enabled: false</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>channel: aurora</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_
|
non_test
|
keep google com see bug description url browser version firefox operating system linux tested another browser yes problem type something else description scrolling inside a focused note can sometimes also scroll the background page of notes steps to reproduce click to focus note scroll rapidly up and down inside note easier with smooth scrolling touchpad like macbook pro it might be easier to reproduce using a note that doesn t have its own scrollbar browser configuration buildid gfx webrender blob images true gfx webrender all false layers acceleration force enabled false gfx webrender enabled false image mem shared true channel aurora from with ❤️
| 0
|
192,260
| 14,612,792,717
|
IssuesEvent
|
2020-12-22 06:56:24
|
github-vet/rangeloop-pointer-findings
|
https://api.github.com/repos/github-vet/rangeloop-pointer-findings
|
closed
|
YanshuoH/youkonger-backend: controllers/api/api_suite_test.go; 3 LoC
|
fresh test tiny
|
Found a possible issue in [YanshuoH/youkonger-backend](https://www.github.com/YanshuoH/youkonger-backend) at [controllers/api/api_suite_test.go](https://github.com/YanshuoH/youkonger-backend/blob/dcd1175b9976855007d9c3cdc9c70ec685dd5f14/controllers/api/api_suite_test.go#L70-L72)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first
issue it finds, so please do not limit your consideration to the contents of the below message.
> function call at line 71 may store a reference to ed
[Click here to see the code in its original context.](https://github.com/YanshuoH/youkonger-backend/blob/dcd1175b9976855007d9c3cdc9c70ec685dd5f14/controllers/api/api_suite_test.go#L70-L72)
<details>
<summary>Click here to show the 3 line(s) of Go which triggered the analyzer.</summary>
```go
for _, ed := range eventDateSet {
conn.Create(&ed)
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: dcd1175b9976855007d9c3cdc9c70ec685dd5f14
|
1.0
|
YanshuoH/youkonger-backend: controllers/api/api_suite_test.go; 3 LoC -
Found a possible issue in [YanshuoH/youkonger-backend](https://www.github.com/YanshuoH/youkonger-backend) at [controllers/api/api_suite_test.go](https://github.com/YanshuoH/youkonger-backend/blob/dcd1175b9976855007d9c3cdc9c70ec685dd5f14/controllers/api/api_suite_test.go#L70-L72)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first
issue it finds, so please do not limit your consideration to the contents of the below message.
> function call at line 71 may store a reference to ed
[Click here to see the code in its original context.](https://github.com/YanshuoH/youkonger-backend/blob/dcd1175b9976855007d9c3cdc9c70ec685dd5f14/controllers/api/api_suite_test.go#L70-L72)
<details>
<summary>Click here to show the 3 line(s) of Go which triggered the analyzer.</summary>
```go
for _, ed := range eventDateSet {
conn.Create(&ed)
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: dcd1175b9976855007d9c3cdc9c70ec685dd5f14
|
test
|
yanshuoh youkonger backend controllers api api suite test go loc found a possible issue in at below is the message reported by the analyzer for this snippet of code beware that the analyzer only reports the first issue it finds so please do not limit your consideration to the contents of the below message function call at line may store a reference to ed click here to show the line s of go which triggered the analyzer go for ed range eventdateset conn create ed leave a reaction on this issue to contribute to the project by classifying this instance as a bug mitigated or desirable behavior rocket see the descriptions of the classifications for more information commit id
| 1
|
278,597
| 24,162,104,765
|
IssuesEvent
|
2022-09-22 12:30:21
|
Tencent/bk-job
|
https://api.github.com/repos/Tencent/bk-job
|
closed
|
bugfix: 菜单的图标重复了
|
kind/bug stage/test accepted
|
**Version / Branch / tag**
≥3.5.1
**出了什么问题？(What Happened?)**
这两边的图标怎么一模一样？？
**如何复现？(How to reproduce?)**
**预期结果(What you expect?)**
高危语句规则和检测记录的icon找carrie拿一下
|
1.0
|
bugfix: 菜单的图标重复了 - **Version / Branch / tag**
≥3.5.1
**出了什么问题？(What Happened?)**
这两边的图标怎么一模一样？？
**如何复现？(How to reproduce?)**
**预期结果(What you expect?)**
高危语句规则和检测记录的icon找carrie拿一下
|
test
|
bugfix 菜单的图标重复了 version branch tag ≥ 出了什么问题？ what happened 这两边的图标怎么一模一样？？ 如何复现？ how to reproduce 预期结果 what you expect 高危语句规则和检测记录的icon找carrie拿一下
| 1
|
243,573
| 20,425,170,726
|
IssuesEvent
|
2022-02-24 02:29:53
|
IntellectualSites/PlotSquared
|
https://api.github.com/repos/IntellectualSites/PlotSquared
|
opened
|
Creepers Grief With Explosion Flag = False
|
Requires Testing
|
### Server Implementation
Paper
### Server Version
1.18.1
### Describe the bug
Even with explosions flag set to false creepers still explode and cause damage to the ground.
### To Reproduce
Claim a plot
Set explosions flag to false
Ignite a creeper with flint & steel or wait for one to explode
Be perplexed at the new hole in the ground
### Expected behaviour
A beautiful plot with no holes
### Screenshots / Videos
https://gyazo.com/615d9f472d6ef76b3acf450d73ccdafa
https://gyazo.com/8452c15751434192d49942b7fa917242
### Error log (if applicable)
N/A
### Plot Debugpaste
https://athion.net/ISPaster/paste/view/d71728e737f947f38a69380e800b241a
### PlotSquared Version
PlotSquared version 6.5.1-Premium
### Checklist
- [X] I have included a Plot debugpaste.
- [X] I am using the newest build from https://www.spigotmc.org/resources/77506/ and the issue still persists.
### Anything else?
_No response_
|
1.0
|
Creepers Grief With Explosion Flag = False - ### Server Implementation
Paper
### Server Version
1.18.1
### Describe the bug
Even with explosions flag set to false creepers still explode and cause damage to the ground.
### To Reproduce
Claim a plot
Set explosions flag to false
Ignite a creeper with flint & steel or wait for one to explode
Be perplexed at the new hole in the ground
### Expected behaviour
A beautiful plot with no holes
### Screenshots / Videos
https://gyazo.com/615d9f472d6ef76b3acf450d73ccdafa
https://gyazo.com/8452c15751434192d49942b7fa917242
### Error log (if applicable)
N/A
### Plot Debugpaste
https://athion.net/ISPaster/paste/view/d71728e737f947f38a69380e800b241a
### PlotSquared Version
PlotSquared version 6.5.1-Premium
### Checklist
- [X] I have included a Plot debugpaste.
- [X] I am using the newest build from https://www.spigotmc.org/resources/77506/ and the issue still persists.
### Anything else?
_No response_
|
test
|
creepers grief with explosion flag false server implementation paper server version describe the bug even with explosions flag set to false creepers still explode and cause damage to the ground to reproduce claim a plot set explosions flag to false ignite a creeper with flint steel or wait for one to explode be perplexed at the new hole in the ground expected behaviour a beautiful plot with no holes screenshots videos error log if applicable n a plot debugpaste plotsquared version plotsquared version premium checklist i have included a plot debugpaste i am using the newest build from and the issue still persists anything else no response
| 1
|
32,114
| 4,750,952,753
|
IssuesEvent
|
2016-10-22 16:27:47
|
brave/browser-laptop
|
https://api.github.com/repos/brave/browser-laptop
|
closed
|
Manual tests for Windows x64 0.12.6 RC1
|
OS/Windows tests
|
## Installer
1. [x] Check that installer is close to the size of last release.
2. [x] Check signature: If OS Run `spctl --assess --verbose /Applications/Brave.app/` and make sure it returns `accepted`. If Windows right click on the installer exe and go to Properties, go to the Digital Signatures tab and double click on the signature. Make sure it says "The digital signature is OK" in the popup window.
3. [x] Check Brave, electron, and libchromiumcontent version in About and make sure it is EXACTLY as expected.
## Per release specialty tests
RC 1
- [x] Selecting and Cutting the UrlBar text reverts the text back ([#4941](https://github.com/brave/browser-laptop/issues/4941))
- [x] tab bar and find bar unaligned design ([#5005](https://github.com/brave/browser-laptop/issues/5005))
- [x] Bookmark Icon position in title mode looks bad ([#4985](https://github.com/brave/browser-laptop/issues/4985))
- [x] Bookmark Icon position in title mode looks bad ([#5041](https://github.com/brave/browser-laptop/pull/5041))
- [x] Creating a bookmark in about:bookmark page creates a folder instead of bookmark ([#5031](https://github.com/brave/browser-laptop/issues/5031))
- [x] Add missing location to "new bookmark" button on about:bookmarks ([#5038](https://github.com/brave/browser-laptop/pull/5038))
- [x] Disable option to add a bookmark without location and a folder without a title. ([#5034](https://github.com/brave/browser-laptop/pull/5034))
- [x] Deleting newtab added as a bookmark crashes Brave ([#5010](https://github.com/brave/browser-laptop/issues/5010))
- [ ] Clicking on Allow protocol registration opens up system settings ([#5028](https://github.com/brave/browser-laptop/issues/5028))
- [x] Upgrade to brave/electron 1.4.17 ([#5016](https://github.com/brave/browser-laptop/issues/5016))
## Ledger
1. [ ] Create a wallet with a value other than $5 selected in the monthly budget dropdown. Click on the 'Add Funds' button and check that Coinbase transactions are blocked.
2. [x] Remove all `ledger-*.json` files from `~/Library/Application\ Support/Brave/`. Go to the Payments tab in about:preferences, enable payments, click on `create wallet`. Check that the `add funds` button appears after a wallet is created.
3. [ ] Click on `add funds` and verify that adding funds through Coinbase increases the account balance.
4. [ ] Repeat the step above but add funds by scanning the QR code in a mobile bitcoin app instead of through Coinbase.
5. [x] Visit nytimes.com for a few seconds and make sure it shows up in the Payments table.
6. [x] Go to https://jsfiddle.net/LnwtLckc/5/ and click the register button. In the Payments tab, click `add funds`. Verify that the `transfer funds` button is visible and that clicking on `transfer funds` opens a jsfiddle URL in a new tab.
7. [x] Go to https://jsfiddle.net/LnwtLckc/5/ and click `unregister`. Verify that the `transfer funds` button no longer appears in the `add funds` modal.
8. [x] Check that disabling payments and enabling them again does not lose state.
## Data
1. [x] Make sure that data from the last version appears in the new version OK.
2. [x] Test that the previous version's cookies are preserved in the next version.
## About pages
1. [x] Test that about:adblock loads
2. [x] Test that about:autofill loads
3. [x] Test that about:bookmarks loads bookmarks
4. [x] Test that about:downloads loads downloads
5. [x] Test that about:extensions loads
6. [x] Test that about:history loads history
7. [x] Test that about:passwords loads
8. [x] Test that about:preferences changing a preference takes effect right away
9. [x] Test that about:preferences language change takes effect on re-start
10. [x] Test that about.com without the http protocol is loaded from URL bar
## Bookmarks
1. [x] Test that creating a bookmark on the bookmarks toolbar works
2. [x] Test that creating a bookmark folder on the bookmarks toolbar works
3. [x] Test that moving a bookmark into a folder by drag and drop on the bookmarks folder works
4. [x] Test that clicking a bookmark in the toolbar loads the bookmark.
5. [x] Test that clicking a bookmark in a bookmark toolbar folder loads the bookmark.
## Context menus
1. [x] Make sure context menu items in the URL bar work
2. [x] Make sure context menu items on content work with no selected text.
3. [x] Make sure context menu items on content work with selected text.
4. [x] Make sure context menu items on content work inside an editable control (input, textarea, or contenteditable).
## Find on page
1. [x] Ensure search box is shown with shortcut
2. [x] Test successful find
3. [x] Test forward and backward find navigation
4. [x] Test failed find shows 0 results
5. [x] Test match case find
## Geolocation
1. [x] Check that https://developer.mozilla.org/en-US/docs/Web/API/Geolocation/Using_geolocation works
## Site hacks
1. [x] Test https://www.twitch.tv/adobe sub-page loads a video and you can play it
## Downloads
1. [x] Test downloading a file works and that all actions on the download item works.
## Fullscreen
1. [x] Test that entering full screen window works View -> Toggle Full Screen. And exit back (Not Esc).
2. [x] Test that entering HTML5 full screen works. And Esc to go back. (youtube.com)
## Tabs and Pinning
1. [x] Test that tabs are pinnable
2. [x] Test that tabs are unpinnable
3. [x] Test that tabs are draggable to same tabset
4. [x] Test that tabs are draggable to alternate tabset
## Zoom
1. [x] Test zoom in / out shortcut works
2. [x] Test hamburger menu zooms.
3. [x] Test zoom saved when you close the browser and restore on a single site.
4. [x] Test zoom saved when you navigate within a single origin site.
5. [x] Test that navigating to a different origin resets the zoom
## Bravery settings
1. [x] Check that HTTPS Everywhere works by loading http://www.apple.com
2. [x] Turning HTTPS Everywhere off and shields off both disable the redirect to https://www.apple.com
3. [x] Check that ad replacement works on http://slashdot.org
4. [x] Check that toggling to blocking and allow ads works as expected.
5. [x] Test that clicking through a cert error in https://badssl.com/ works.
6. [x] Test that Safe Browsing works (http://excellentmovies.net/)
7. [x] Turning Safe Browsing off and shields off both disable safe browsing for http://excellentmovies.net/.
8. [x] Visit https://brianbondy.com/ and then turn on script blocking, nothing should load. Allow it from the script blocking UI in the URL bar and it should work.
9. [x] Test that about:preferences default Bravery settings take effect on pages with no site settings.
10. [x] Test that turning on fingerprinting protection in about:preferences shows 3 fingerprints blocked at https://jsfiddle.net/bkf50r8v/13/. Test that turning it off in the Bravery menu shows 0 fingerprints blocked.
11. [x] Test that 3rd party storage results are blank at https://jsfiddle.net/7ke9r14a/9/ when 3rd party cookies are blocked and not blank when 3rd party cookies are unblocked.
12. [x] Test that audio fingerprint is blocked at https://audiofingerprint.openwpm.com/ when fingerprinting protection is on.
## Content tests
1. [x] Go to https://brianbondy.com/ and click on the twitter icon on the top right. Test that context menus work in the new twitter tab.
2. [x] Load twitter and click on a tweet so the popup div shows. Click to dismiss and repeat with another div. Make sure it shows.
3. [x] Go to http://www.bennish.net/web-notifications.html and test that clicking on 'Show' pops up a notification asking for permission. Make sure that clicking 'Deny' leads to no notifications being shown.
4. [x] Go to https://trac.torproject.org/projects/tor/login and make sure that the password can be saved. Make sure the saved password shows up in `about:passwords`. Then reload https://trac.torproject.org/projects/tor/login and make sure the password is autofilled.
5. [x] Open a github issue and type some misspellings, make sure they are underlined.
6. [x] Make sure that right clicking on a word with suggestions gives a suggestion and that clicking on the suggestion replaces the text.
7. [x] Make sure that Command + Click (Control + Click on Windows, Control + Click on Ubuntu) on a link opens a new tab but does NOT switch to it. Click on it and make sure it is already loaded.
8. [x] Open an email on http://mail.google.com/ or inbox.google.com and click on a link. Make sure it works.
9. [x] Test that PDF is loaded at http://www.orimi.com/pdf-test.pdf
10. [x] Test that https://mixed-script.badssl.com/ shows up as grey not red (no mixed content scripts are run).
## Flash tests
1. [x] Turn on Flash in about:preferences#security. Test that clicking on 'Install Flash' banner on myspace.com shows a notification to allow Flash and that the banner disappears when 'Allow' is clicked.
2. [x] Test that flash placeholder appears on http://www.y8.com/games/superfighters
## Autofill tests
1. [x] Test that autofill works on http://www.roboform.com/filling-test-all-fields
## Session storage
Do not forget to make a backup of your entire `~/Library/Application\ Support/Brave` folder.
1. [x] Temporarily move away your `~/Library/Application\ Support/Brave/session-store-1` and test that clean session storage works. (`%appdata%\Brave in Windows`, `./config/brave` in Ubuntu)
2. [x] Test that windows and tabs restore when closed, including active tab.
3. [x] Move away your entire `~/Library/Application\ Support/Brave` folder (`%appdata%\Brave in Windows`, `./config/brave` in Ubuntu)
## Cookie and Cache
1. [x] Make a backup of your profile, turn on all clearing in preferences and shut down. Make sure when you bring the browser back up everything is gone that is specified.
2. [x] Go to http://samy.pl/evercookie/ and set an evercookie. Check that going to prefs, clearing site data and cache, and going back to the Evercookie site does not remember the old evercookie value.
## Update tests
1. [x] Test that updating using `BRAVE_UPDATE_VERSION=0.8.3` env variable works correctly.
|
1.0
|
Manual tests for Windows x64 0.12.6 RC1 - ## Installer
1. [x] Check that installer is close to the size of last release.
2. [x] Check signature: If OS Run `spctl --assess --verbose /Applications/Brave.app/` and make sure it returns `accepted`. If Windows right click on the installer exe and go to Properties, go to the Digital Signatures tab and double click on the signature. Make sure it says "The digital signature is OK" in the popup window.
3. [x] Check Brave, electron, and libchromiumcontent version in About and make sure it is EXACTLY as expected.
## Per release specialty tests
RC 1
- [x] Selecting and Cutting the UrlBar text reverts the text back ([#4941](https://github.com/brave/browser-laptop/issues/4941))
- [x] tab bar and find bar unaligned design ([#5005](https://github.com/brave/browser-laptop/issues/5005))
- [x] Bookmark Icon position in title mode looks bad ([#4985](https://github.com/brave/browser-laptop/issues/4985))
- [x] Bookmark Icon position in title mode looks bad ([#5041](https://github.com/brave/browser-laptop/pull/5041))
- [x] Creating a bookmark in about:bookmark page creates a folder instead of bookmark ([#5031](https://github.com/brave/browser-laptop/issues/5031))
- [x] Add missing location to "new bookmark" button on about:bookmarks ([#5038](https://github.com/brave/browser-laptop/pull/5038))
- [x] Disable option to add a bookmark without location and a folder without a title. ([#5034](https://github.com/brave/browser-laptop/pull/5034))
- [x] Deleting newtab added as a bookmark crashes Brave ([#5010](https://github.com/brave/browser-laptop/issues/5010))
- [ ] Clicking on Allow protocol registration opens up system settings ([#5028](https://github.com/brave/browser-laptop/issues/5028))
- [x] Upgrade to brave/electron 1.4.17 ([#5016](https://github.com/brave/browser-laptop/issues/5016))
## Ledger
1. [ ] Create a wallet with a value other than $5 selected in the monthly budget dropdown. Click on the 'Add Funds' button and check that Coinbase transactions are blocked.
2. [x] Remove all `ledger-*.json` files from `~/Library/Application\ Support/Brave/`. Go to the Payments tab in about:preferences, enable payments, click on `create wallet`. Check that the `add funds` button appears after a wallet is created.
3. [ ] Click on `add funds` and verify that adding funds through Coinbase increases the account balance.
4. [ ] Repeat the step above but add funds by scanning the QR code in a mobile bitcoin app instead of through Coinbase.
5. [x] Visit nytimes.com for a few seconds and make sure it shows up in the Payments table.
6. [x] Go to https://jsfiddle.net/LnwtLckc/5/ and click the register button. In the Payments tab, click `add funds`. Verify that the `transfer funds` button is visible and that clicking on `transfer funds` opens a jsfiddle URL in a new tab.
7. [x] Go to https://jsfiddle.net/LnwtLckc/5/ and click `unregister`. Verify that the `transfer funds` button no longer appears in the `add funds` modal.
8. [x] Check that disabling payments and enabling them again does not lose state.
## Data
1. [x] Make sure that data from the last version appears in the new version OK.
2. [x] Test that the previous version's cookies are preserved in the next version.
## About pages
1. [x] Test that about:adblock loads
2. [x] Test that about:autofill loads
3. [x] Test that about:bookmarks loads bookmarks
4. [x] Test that about:downloads loads downloads
5. [x] Test that about:extensions loads
6. [x] Test that about:history loads history
7. [x] Test that about:passwords loads
8. [x] Test that about:preferences changing a preference takes effect right away
9. [x] Test that about:preferences language change takes effect on re-start
10. [x] Test that about.com without the http protocol is loaded from URL bar
## Bookmarks
1. [x] Test that creating a bookmark on the bookmarks toolbar works
2. [x] Test that creating a bookmark folder on the bookmarks toolbar works
3. [x] Test that moving a bookmark into a folder by drag and drop on the bookmarks folder works
4. [x] Test that clicking a bookmark in the toolbar loads the bookmark.
5. [x] Test that clicking a bookmark in a bookmark toolbar folder loads the bookmark.
## Context menus
1. [x] Make sure context menu items in the URL bar work
2. [x] Make sure context menu items on content work with no selected text.
3. [x] Make sure context menu items on content work with selected text.
4. [x] Make sure context menu items on content work inside an editable control (input, textarea, or contenteditable).
## Find on page
1. [x] Ensure search box is shown with shortcut
2. [x] Test successful find
3. [x] Test forward and backward find navigation
4. [x] Test failed find shows 0 results
5. [x] Test match case find
## Geolocation
1. [x] Check that https://developer.mozilla.org/en-US/docs/Web/API/Geolocation/Using_geolocation works
## Site hacks
1. [x] Test https://www.twitch.tv/adobe sub-page loads a video and you can play it
## Downloads
1. [x] Test downloading a file works and that all actions on the download item works.
## Fullscreen
1. [x] Test that entering full screen window works View -> Toggle Full Screen. And exit back (Not Esc).
2. [x] Test that entering HTML5 full screen works. And Esc to go back. (youtube.com)
## Tabs and Pinning
1. [x] Test that tabs are pinnable
2. [x] Test that tabs are unpinnable
3. [x] Test that tabs are draggable to same tabset
4. [x] Test that tabs are draggable to alternate tabset
## Zoom
1. [x] Test zoom in / out shortcut works
2. [x] Test hamburger menu zooms.
3. [x] Test zoom saved when you close the browser and restore on a single site.
4. [x] Test zoom saved when you navigate within a single origin site.
5. [x] Test that navigating to a different origin resets the zoom
## Bravery settings
1. [x] Check that HTTPS Everywhere works by loading http://www.apple.com
2. [x] Turning HTTPS Everywhere off and shields off both disable the redirect to https://www.apple.com
3. [x] Check that ad replacement works on http://slashdot.org
4. [x] Check that toggling to blocking and allow ads works as expected.
5. [x] Test that clicking through a cert error in https://badssl.com/ works.
6. [x] Test that Safe Browsing works (http://excellentmovies.net/)
7. [x] Turning Safe Browsing off and shields off both disable safe browsing for http://excellentmovies.net/.
8. [x] Visit https://brianbondy.com/ and then turn on script blocking, nothing should load. Allow it from the script blocking UI in the URL bar and it should work.
9. [x] Test that about:preferences default Bravery settings take effect on pages with no site settings.
10. [x] Test that turning on fingerprinting protection in about:preferences shows 3 fingerprints blocked at https://jsfiddle.net/bkf50r8v/13/. Test that turning it off in the Bravery menu shows 0 fingerprints blocked.
11. [x] Test that 3rd party storage results are blank at https://jsfiddle.net/7ke9r14a/9/ when 3rd party cookies are blocked and not blank when 3rd party cookies are unblocked.
12. [x] Test that audio fingerprint is blocked at https://audiofingerprint.openwpm.com/ when fingerprinting protection is on.
## Content tests
1. [x] Go to https://brianbondy.com/ and click on the twitter icon on the top right. Test that context menus work in the new twitter tab.
2. [x] Load twitter and click on a tweet so the popup div shows. Click to dismiss and repeat with another div. Make sure it shows.
3. [x] Go to http://www.bennish.net/web-notifications.html and test that clicking on 'Show' pops up a notification asking for permission. Make sure that clicking 'Deny' leads to no notifications being shown.
4. [x] Go to https://trac.torproject.org/projects/tor/login and make sure that the password can be saved. Make sure the saved password shows up in `about:passwords`. Then reload https://trac.torproject.org/projects/tor/login and make sure the password is autofilled.
5. [x] Open a github issue and type some misspellings, make sure they are underlined.
6. [x] Make sure that right clicking on a word with suggestions gives a suggestion and that clicking on the suggestion replaces the text.
7. [x] Make sure that Command + Click (Control + Click on Windows, Control + Click on Ubuntu) on a link opens a new tab but does NOT switch to it. Click on it and make sure it is already loaded.
8. [x] Open an email on http://mail.google.com/ or inbox.google.com and click on a link. Make sure it works.
9. [x] Test that PDF is loaded at http://www.orimi.com/pdf-test.pdf
10. [x] Test that https://mixed-script.badssl.com/ shows up as grey not red (no mixed content scripts are run).
## Flash tests
1. [x] Turn on Flash in about:preferences#security. Test that clicking on 'Install Flash' banner on myspace.com shows a notification to allow Flash and that the banner disappears when 'Allow' is clicked.
2. [x] Test that flash placeholder appears on http://www.y8.com/games/superfighters
## Autofill tests
1. [x] Test that autofill works on http://www.roboform.com/filling-test-all-fields
## Session storage
Do not forget to make a backup of your entire `~/Library/Application\ Support/Brave` folder.
1. [x] Temporarily move away your `~/Library/Application\ Support/Brave/session-store-1` and test that clean session storage works. (`%appdata%\Brave in Windows`, `./config/brave` in Ubuntu)
2. [x] Test that windows and tabs restore when closed, including active tab.
3. [x] Move away your entire `~/Library/Application\ Support/Brave` folder (`%appdata%\Brave in Windows`, `./config/brave` in Ubuntu)
## Cookie and Cache
1. [x] Make a backup of your profile, turn on all clearing in preferences and shut down. Make sure when you bring the browser back up everything is gone that is specified.
2. [x] Go to http://samy.pl/evercookie/ and set an evercookie. Check that going to prefs, clearing site data and cache, and going back to the Evercookie site does not remember the old evercookie value.
## Update tests
1. [x] Test that updating using `BRAVE_UPDATE_VERSION=0.8.3` env variable works correctly.
|
test
|
manual tests for windows installer check that installer is close to the size of last release check signature if os run spctl assess verbose applications brave app and make sure it returns accepted if windows right click on the installer exe and go to properties go to the digital signatures tab and double click on the signature make sure it says the digital signature is ok in the popup window check brave electron and libchromiumcontent version in about and make sure it is exactly as expected per release specialty tests rc selecting and cutting the urlbar text reverts the text back tab bar and find bar unaligned design bookmark icon position in title mode looks bad bookmark icon position in title mode looks bad creating a bookmark in about bookmark page creates a folder instead of bookmark add missing location to new bookmark button on about bookmarks disable option to add a bookmark without location and a folder without a title deleting newtab added as a bookmark crashes brave clicking on allow protocol registration opens up system settings upgrade to brave electron ledger create a wallet with a value other than selected in the monthly budget dropdown click on the add funds button and check that coinbase transactions are blocked remove all ledger json files from library application support brave go to the payments tab in about preferences enable payments click on create wallet check that the add funds button appears after a wallet is created click on add funds and verify that adding funds through coinbase increases the account balance repeat the step above but add funds by scanning the qr code in a mobile bitcoin app instead of through coinbase visit nytimes com for a few seconds and make sure it shows up in the payments table go to and click the register button in the payments tab click add funds verify that the transfer funds button is visible and that clicking on transfer funds opens a jsfiddle url in a new tab go to and click unregister verify that the transfer funds button no longer appears in the add funds modal check that disabling payments and enabling them again does not lose state data make sure that data from the last version appears in the new version ok test that the previous version s cookies are preserved in the next version about pages test that about adblock loads test that about autofill loads test that about bookmarks loads bookmarks test that about downloads loads downloads test that about extensions loads test that about history loads history test that about passwords loads test that about preferences changing a preference takes effect right away test that about preferences language change takes effect on re start test that about com without the http protocol is loaded from url bar bookmarks test that creating a bookmark on the bookmarks toolbar works test that creating a bookmark folder on the bookmarks toolbar works test that moving a bookmark into a folder by drag and drop on the bookmarks folder works test that clicking a bookmark in the toolbar loads the bookmark test that clicking a bookmark in a bookmark toolbar folder loads the bookmark context menus make sure context menu items in the url bar work make sure context menu items on content work with no selected text make sure context menu items on content work with selected text make sure context menu items on content work inside an editable control input textarea or contenteditable find on page ensure search box is shown with shortcut test successful find test forward and backward find navigation test failed find shows results test match case find geolocation check that works site hacks test sub page loads a video and you can play it downloads test downloading a file works and that all actions on the download item works fullscreen test that entering full screen window works view toggle full screen and exit back not esc test that entering full screen works and esc to go back youtube com tabs and pinning test that tabs are pinnable test that tabs are unpinnable test that tabs are draggable to same tabset test that tabs are draggable to alternate tabset zoom test zoom in out shortcut works test hamburger menu zooms test zoom saved when you close the browser and restore on a single site test zoom saved when you navigate within a single origin site test that navigating to a different origin resets the zoom bravery settings check that https everywhere works by loading turning https everywhere off and shields off both disable the redirect to check that ad replacement works on check that toggling to blocking and allow ads works as expected test that clicking through a cert error in works test that safe browsing works turning safe browsing off and shields off both disable safe browsing for visit and then turn on script blocking nothing should load allow it from the script blocking ui in the url bar and it should work test that about preferences default bravery settings take effect on pages with no site settings test that turning on fingerprinting protection in about preferences shows fingerprints blocked at test that turning it off in the bravery menu shows fingerprints blocked test that party storage results are blank at when party cookies are blocked and not blank when party cookies are unblocked test that audio fingerprint is blocked at when fingerprinting protection is on content tests go to and click on the twitter icon on the top right test that context menus work in the new twitter tab load twitter and click on a tweet so the popup div shows click to dismiss and repeat with another div make sure it shows go to and test that clicking on show pops up a notification asking for permission make sure that clicking deny leads to no notifications being shown go to and make sure that the password can be saved make sure the saved password shows up in about passwords then reload and make sure the password is autofilled open a github issue and type some misspellings make sure they are underlined make sure that right clicking on a word with suggestions gives a suggestion and that clicking on the suggestion replaces the text make sure that command click control click on windows control click on ubuntu on a link opens a new tab but does not switch to it click on it and make sure it is already loaded open an email on or inbox google com and click on a link make sure it works test that pdf is loaded at test that shows up as grey not red no mixed content scripts are run flash tests turn on flash in about preferences security test that clicking on install flash banner on myspace com shows a notification to allow flash and that the banner disappears when allow is clicked test that flash placeholder appears on autofill tests test that autofill works on session storage do not forget to make a backup of your entire library application support brave folder temporarily move away your library application support brave session store and test that clean session storage works appdata brave in windows config brave in ubuntu test that windows and tabs restore when closed including active tab move away your entire library application support brave folder appdata brave in windows config brave in ubuntu cookie and cache make a backup of your profile turn on all clearing in preferences and shut down make sure when you bring the browser back up everything is gone that is specified go to and set an evercookie check that going to prefs clearing site data and cache and going back to the evercookie site does not remember the old evercookie value update tests test that updating using brave update version env variable works correctly
| 1
|
536,235
| 15,706,398,216
|
IssuesEvent
|
2021-03-26 17:22:37
|
Automattic/woocommerce-payments
|
https://api.github.com/repos/Automattic/woocommerce-payments
|
closed
|
Purchasing a free trial subscription using a saved card doesn't save a payment token to subscription
|
component: saved cards and subscriptions priority: high size: small status: has PR type: bug
|
## What's expected to happen?
1. Buy a subscription with a free trial using an already saved card.
1. (Payment token is saved to the subscription order).
1. Renewals will used the card chosen during checkout.
## What actually happens?
1. Buy a subscription with a free trial using an already saved card.
1. (No payment token is saved to the subscription order).
1. Renewals will fail because no payment token is available for the order.
## Context
>I tried to purchase a free trial subscription using a saved card, and it could not be renewed. The error was `There is no saved payment token for order #159` and it also happened after applying #1288.
>
>At this point, I'm wondering whether removing the early return statement that introduced this bug wouldn't be a simpler fix until the more robust changes are addressed in #1289 and #1293.
>
>_Originally posted by @luizreis in https://github.com/Automattic/woocommerce-payments/issues/1185#issuecomment-802080518_
## Steps to reproduce (kudos to @luizreis)
1. Add a card to the customer using the My Account page, or saving it during a regular purchase
2. Create a Subscription with a free trial, which is processed as a $0 order, and use the saved card to pay for it
3. Using the My subscriptions page or the admin subscription view, process an early renewal of that subscription
4. The renewal should fail with a `There is no saved payment token for order` error as the token was not added to the subscription order during checkout, which happens because the payment method doesn't have to be saved and the order doesn't have to be paid
## ZenDesk tickets
3807165-zen
|
1.0
|
Purchasing a free trial subscription using a saved card doesn't save a payment token to subscription - ## What's expected to happen?
1. Buy a subscription with a free trial using an already saved card.
1. (Payment token is saved to the subscription order).
1. Renewals will used the card chosen during checkout.
## What actually happens?
1. Buy a subscription with a free trial using an already saved card.
1. (No payment token is saved to the subscription order).
1. Renewals will fail because no payment token is available for the order.
## Context
>I tried to purchase a free trial subscription using a saved card, and it could not be renewed. The error was `There is no saved payment token for order #159` and it also happened after applying #1288.
>
>At this point, I'm wondering whether removing the early return statement that introduced this bug wouldn't be a simpler fix until the more robust changes are addressed in #1289 and #1293.
>
>_Originally posted by @luizreis in https://github.com/Automattic/woocommerce-payments/issues/1185#issuecomment-802080518_
## Steps to reproduce (kudos to @luizreis)
1. Add a card to the customer using the My Account page, or saving it during a regular purchase
2. Create a Subscription with a free trial, which is processed as a $0 order, and use the saved card to pay for it
3. Using the My subscriptions page or the admin subscription view, process an early renewal of that subscription
4. The renewal should fail with a `There is no saved payment token for order` error as the token was not added to the subscription order during checkout, which happens because the payment method doesn't have to be saved and the order doesn't have to be paid
## ZenDesk tickets
3807165-zen
|
non_test
|
purchasing a free trial subscription using a saved card doesn t save a payment token to subscription what s expected to happen buy a subscription with a free trial using an already saved card payment token is saved to the subscription order renewals will used the card chosen during checkout what actually happens buy a subscription with a free trial using an already saved card no payment token is saved to the subscription order renewals will fail because no payment token is available for the order context i tried to purchase a free trial subscription using a saved card and it could not be renewed the error was there is no saved payment token for order and it also happened after applying at this point i m wondering whether removing the early return statement that introduced this bug wouldn t be a simpler fix until the more robust changes are addressed in and originally posted by luizreis in steps to reproduce kudos to luizreis add a card to the customer using the my account page or saving it during a regular purchase create a subscription with a free trial which is processed as a order and use the saved card to pay for it using the my subscriptions page or the admin subscription view process an early renewal of that subscription the renewal should fail with a there is no saved payment token for order error as the token was not added to the subscription order during checkout which happens because the payment method doesn t have to be saved and the order doesn t have to be paid zendesk tickets zen
| 0
|
49,585
| 6,033,615,614
|
IssuesEvent
|
2017-06-09 08:49:55
|
ssllabs/ssllabs-scan
|
https://api.github.com/repos/ssllabs/ssllabs-scan
|
closed
|
Support RFC 7919
|
client test
|
https://tools.ietf.org/html/rfc7919
Firefox supports one of these at the moment: ffdhe2048(256)
EDIT: Changed ticket name after realising that the new RFC applies equally when testing what it's at the moment called "named curves". Thus it applies to both server and client tests.
|
1.0
|
Support RFC 7919 - https://tools.ietf.org/html/rfc7919
Firefox supports one of these at the moment: ffdhe2048(256)
EDIT: Changed ticket name after realising that the new RFC applies equally when testing what it's at the moment called "named curves". Thus it applies to both server and client tests.
|
test
|
support rfc firefox supports one of these at the moment edit changed ticket name after realising that the new rfc applies equally when testing what it s at the moment called named curves thus it applies to both server and client tests
| 1
|
679,323
| 23,228,629,275
|
IssuesEvent
|
2022-08-03 04:44:43
|
chloebrett/mlvet
|
https://api.github.com/repos/chloebrett/mlvet
|
closed
|
Cut and paste does not handle spaces properly
|
high priority
|
Subissue of #93
If you cut and paste a sequence of words, some of the spaces between words disappear.
Before:
<img width="467" alt="Screen Shot 2022-05-22 at 11 43 49 am" src="https://user-images.githubusercontent.com/6735055/169674801-b6f9c71e-f690-488c-b6f1-2d397e0cc790.png">
After:
<img width="464" alt="Screen Shot 2022-05-22 at 11 44 24 am" src="https://user-images.githubusercontent.com/6735055/169674811-16c63bc2-5c39-45c2-a937-d212f1c916d8.png">
|
1.0
|
Cut and paste does not handle spaces properly - Subissue of #93
If you cut and paste a sequence of words, some of the spaces between words disappear.
Before:
<img width="467" alt="Screen Shot 2022-05-22 at 11 43 49 am" src="https://user-images.githubusercontent.com/6735055/169674801-b6f9c71e-f690-488c-b6f1-2d397e0cc790.png">
After:
<img width="464" alt="Screen Shot 2022-05-22 at 11 44 24 am" src="https://user-images.githubusercontent.com/6735055/169674811-16c63bc2-5c39-45c2-a937-d212f1c916d8.png">
|
non_test
|
cut and paste does not handle spaces properly subissue of if you cut and paste a sequence of words some of the spaces between words disappear before img width alt screen shot at am src after img width alt screen shot at am src
| 0
|
236,491
| 19,552,471,561
|
IssuesEvent
|
2022-01-03 00:57:31
|
Exiled-Team/AdminTools
|
https://api.github.com/repos/Exiled-Team/AdminTools
|
closed
|
Spawn Workbench not working
|
requires testing
|
**Describe the bug**
using the spawn workbench command doesn't do anything but if someone else stands where you created one they start floating
**To Reproduce**
Steps to reproduce the behavior:
1. Go to ra panel
2. Click on text based ra
3. use spawn workbench command
4. workbench is invisible, get someone else to stand where it is and they will start floating as well
**Expected behavior**
A clear and concise description of what you expected to happen.
**Server logs**
Please include a pastebin of your localadmin log file (or both MA_log and SCP_log files if you use MultiAdmin) from the time in which the bug occured
**EXILED Version ("latest" is not a version):**
**Results of `show plugins` command in console:**
**Additional context**
Add any other context about the problem here.
|
1.0
|
Spawn Workbench not working - **Describe the bug**
using the spawn workbench command doesn't do anything but if someone else stands where you created one they start floating
**To Reproduce**
Steps to reproduce the behavior:
1. Go to ra panel
2. Click on text based ra
3. use spawn workbench command
4. workbench is invisible, get someone else to stand where it is and they will start floating as well
**Expected behavior**
A clear and concise description of what you expected to happen.
**Server logs**
Please include a pastebin of your localadmin log file (or both MA_log and SCP_log files if you use MultiAdmin) from the time in which the bug occured
**EXILED Version ("latest" is not a version):**
**Results of `show plugins` command in console:**
**Additional context**
Add any other context about the problem here.
|
test
|
spawn workbench not working describe the bug using the spawn workbench command doesn t do anything but if someone else stands where you created one they start floating to reproduce steps to reproduce the behavior go to ra panel click on text based ra use spawn workbench command workbench is invisible get someone else to stand where it is and they will start floating as well expected behavior a clear and concise description of what you expected to happen server logs please include a pastebin of your localadmin log file or both ma log and scp log files if you use multiadmin from the time in which the bug occured exiled version latest is not a version results of show plugins command in console additional context add any other context about the problem here
| 1
|
228,107
| 18,158,416,662
|
IssuesEvent
|
2021-09-27 06:36:56
|
apache/superset
|
https://api.github.com/repos/apache/superset
|
closed
|
[native filter] datetime data in value filter is not readable in filter indicator
|
P2 viz:dashboard:native-filter #bug test:case Preset-QA
|
Datetime data in value filter is not readable in filter indicator
### Expected results
Datetime data in value filter is readable in filter indicator
### Actual results
Datetime data in value filter is not readable in filter indicator
#### Screenshots
<img width="1789" alt="Screen Shot 2021-09-23 at 1 05 50 AM" src="https://user-images.githubusercontent.com/81597121/134473837-ab2201d0-b354-4759-9b0c-3ad597ad6dc6.png">
#### How to reproduce the bug
1. create value filter with datatime column
2. applied filter on charts
3. open indicator and observe
4. See error
### Environment
(please complete the following information):
- browser type and version:
- superset version: master
- python version: `python --version`
- node.js version: `node -v`
- any feature flags active:
### Checklist
Make sure to follow these steps before submitting your issue - thank you!
- [ ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
- [x] I have reproduced the issue with at least the latest released version of superset.
- [x] I have checked the issue tracker for the same issue and I haven't found one similar.
### Additional context
Add any other context about the problem here.
|
1.0
|
[native filter] datetime data in value filter is not readable in filter indicator - Datetime data in value filter is not readable in filter indicator
### Expected results
Datetime data in value filter is readable in filter indicator
### Actual results
Datetime data in value filter is not readable in filter indicator
#### Screenshots
<img width="1789" alt="Screen Shot 2021-09-23 at 1 05 50 AM" src="https://user-images.githubusercontent.com/81597121/134473837-ab2201d0-b354-4759-9b0c-3ad597ad6dc6.png">
#### How to reproduce the bug
1. create value filter with datatime column
2. applied filter on charts
3. open indicator and observe
4. See error
### Environment
(please complete the following information):
- browser type and version:
- superset version: master
- python version: `python --version`
- node.js version: `node -v`
- any feature flags active:
### Checklist
Make sure to follow these steps before submitting your issue - thank you!
- [ ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
- [x] I have reproduced the issue with at least the latest released version of superset.
- [x] I have checked the issue tracker for the same issue and I haven't found one similar.
### Additional context
Add any other context about the problem here.
|
test
|
datetime data in value filter is not readable in filter indicator datetime data in value filter is not readable in filter indicator expected results datetime data in value filter is readable in filter indicator actual results datetime data in value filter is not readable in filter indicator screenshots img width alt screen shot at am src how to reproduce the bug create value filter with datatime column applied filter on charts open indicator and observe see error environment please complete the following information browser type and version superset version master python version python version node js version node v any feature flags active checklist make sure to follow these steps before submitting your issue thank you i have checked the superset logs for python stacktraces and included it here as text if there are any i have reproduced the issue with at least the latest released version of superset i have checked the issue tracker for the same issue and i haven t found one similar additional context add any other context about the problem here
| 1
|
278,711
| 24,169,603,156
|
IssuesEvent
|
2022-09-22 17:56:45
|
chocolatey/choco
|
https://api.github.com/repos/chocolatey/choco
|
closed
|
Upgrade all reuses overridden package parameters when useRememberedArgumentsForUpgrades feature is turned on
|
Bug Priority_HIGH 3 - Review ADD AUTO TESTS
|
### What You Are Seeing?
I have a multitude of packages installed via chocolatey, a number of which I have set custom install directories for. Chocolatey regularly shows error messages that indicate that the overridden parameters for another package are used. For instance:
```
ERROR: Running ["C:\Users\Dual Infinity\AppData\Local\Temp\chocolatey\TotalCommander\9.10\INSTALL.exe" INSTALLDIR=C:\Frameworks\NodeJS] was not successful. Exit code was '1'. See log for possible error messages.
The upgrade of totalcommander was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\TotalCommander\tools\chocolateyInstall.ps1'.
See log for details.
```
It seems to use the last overridden parameters encountered.
Addendum 2017-11-07:
The issue is usually resolved by running the upgrade all command multiple times. It does not seem random, but it does seem that if a package with custom parameters was installed successfully its parameters are not read and do not conflict in the subsequent run of upgrade all.
### What is Expected?
Chocolatey should (obviously) not reuse package parameters for other packages.
### How Did You Get This To Happen? (Steps to Reproduce)
In essence, this would entail setting custom install dirs for multiple packages and running chocolatey upgrade all.
### Output Log
See zip:
[dinfinity.chocolatey.log.2017-11-06.zip](https://github.com/chocolatey/choco/files/1446353/dinfinity.chocolatey.log.2017-11-06.zip)
### Related
* https://github.com/chocolatey/choco/issues/797
|
1.0
|
Upgrade all reuses overridden package parameters when useRememberedArgumentsForUpgrades feature is turned on - ### What You Are Seeing?
I have a multitude of packages installed via chocolatey, a number of which I have set custom install directories for. Chocolatey regularly shows error messages that indicate that the overridden parameters for another package are used. For instance:
```
ERROR: Running ["C:\Users\Dual Infinity\AppData\Local\Temp\chocolatey\TotalCommander\9.10\INSTALL.exe" INSTALLDIR=C:\Frameworks\NodeJS] was not successful. Exit code was '1'. See log for possible error messages.
The upgrade of totalcommander was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\TotalCommander\tools\chocolateyInstall.ps1'.
See log for details.
```
It seems to use the last overridden parameters encountered.
Addendum 2017-11-07:
The issue is usually resolved by running the upgrade all command multiple times. It does not seem random, but it does seem that if a package with custom parameters was installed successfully its parameters are not read and do not conflict in the subsequent run of upgrade all.
### What is Expected?
Chocolatey should (obviously) not reuse package parameters for other packages.
### How Did You Get This To Happen? (Steps to Reproduce)
In essence, this would entail setting custom install dirs for multiple packages and running chocolatey upgrade all.
### Output Log
See zip:
[dinfinity.chocolatey.log.2017-11-06.zip](https://github.com/chocolatey/choco/files/1446353/dinfinity.chocolatey.log.2017-11-06.zip)
### Related
* https://github.com/chocolatey/choco/issues/797
|
test
|
upgrade all reuses overridden package parameters when userememberedargumentsforupgrades feature is turned on what you are seeing i have a multitude of packages installed via chocolatey a number of which i have set custom install directories for chocolatey regularly shows error messages that indicate that the overridden parameters for another package are used for instance error running was not successful exit code was see log for possible error messages the upgrade of totalcommander was not successful error while running c programdata chocolatey lib totalcommander tools chocolateyinstall see log for details it seems to use the last overridden parameters encountered addendum the issue is usually resolved by running the upgrade all command multiple times it does not seem random but it does seem that if a package with custom parameters was installed successfully its parameters are not read and do not conflict in the subsequent run of upgrade all what is expected chocolatey should obviously not reuse package parameters for other packages how did you get this to happen steps to reproduce in essence this would entail setting custom install dirs for multiple packages and running chocolatey upgrade all output log see zip related
| 1
|
147,831
| 11,809,433,121
|
IssuesEvent
|
2020-03-19 14:57:08
|
phetsims/bending-light
|
https://api.github.com/repos/phetsims/bending-light
|
opened
|
CT PhET-iO API error
|
type:automated-testing
|
```
bending-light : phet-io-fuzz : require.js : load
https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/bending-light/bending-light_en.html?postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload&brand=phet-io&phetioStandalone&ea&fuzz&memoryLimit=1000
Query: brand=phet-io&phetioStandalone&ea&fuzz&memoryLimit=1000
Uncaught Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/assert/js/assert.js?bust=1584609658817:22:13)
at PhetioAPIValidation.assertAPIError (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:277:15)
at PhetioAPIValidation.onSimStarted (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:106:16)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io/js/phetioEngine.js:158:27
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/TinyEmitter.js:65:53)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:33:29
at Emitter.execute (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Action.js:224:18)
at Emitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:58:19)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/joist/js/Sim.js:842:48
id: Bayes Chrome
Approximately 3/18/2020, 10:15:44 PM
bending-light : phet-io-fuzz : require.js : run
https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/bending-light/bending-light_en.html?postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload&brand=phet-io&phetioStandalone&ea&fuzz&memoryLimit=1000
Query: brand=phet-io&phetioStandalone&ea&fuzz&memoryLimit=1000
Uncaught Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/assert/js/assert.js?bust=1584609658817:22:13)
at PhetioAPIValidation.assertAPIError (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:277:15)
at PhetioAPIValidation.onSimStarted (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:106:16)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io/js/phetioEngine.js:158:27
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/TinyEmitter.js:65:53)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:33:29
at Emitter.execute (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Action.js:224:18)
at Emitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:58:19)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/joist/js/Sim.js:842:48
id: Bayes Chrome
Approximately 3/18/2020, 10:15:44 PM
bending-light : phet-io-mirror-inputs-fuzz : require.js : run
https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io-wrappers/mirror-inputs/?sim=bending-light&phetioDebug&fuzz&postMessageToParent&postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload
Uncaught Error: Uncaught Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/assert/js/assert.js?bust=1584600800566:22:13)
at PhetioAPIValidation.assertAPIError (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:277:15)
at PhetioAPIValidation.onSimStarted (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:106:16)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io/js/phetioEngine.js:158:27
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/TinyEmitter.js:65:53)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:33:29
at Emitter.execute (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Action.js:224:18)
at Emitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:58:19)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/joist/js/Sim.js:842:48
id: Bayes Chrome
Approximately 3/18/2020, 10:15:44 PM
bending-light : phet-io-mirror-inputs-fuzz : require.js : run
https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io-wrappers/mirror-inputs/?sim=bending-light&phetioDebug&fuzz&postMessageToParent&postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload
Uncaught Error: Uncaught Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/assert/js/assert.js?bust=1584623806278:22:13)
at PhetioAPIValidation.assertAPIError (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:277:15)
at PhetioAPIValidation.onSimStarted (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:106:16)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io/js/phetioEngine.js:158:27
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/TinyEmitter.js:65:53)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:33:29
at Emitter.execute (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Action.js:224:18)
at Emitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:58:19)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/joist/js/Sim.js:842:48
id: Bayes Chrome
Approximately 3/18/2020, 10:15:44 PM
bending-light : phet-io-state-fuzz : require.js : run
https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io-wrappers/state/?sim=bending-light&phetioDebug&fuzz&postMessageToParent&postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload
Uncaught Error: Uncaught Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/assert/js/assert.js?bust=1584597600498:22:13)
at PhetioAPIValidation.assertAPIError (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:277:15)
at PhetioAPIValidation.onSimStarted (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:106:16)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io/js/phetioEngine.js:158:27
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/TinyEmitter.js:65:53)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:33:29
at Emitter.execute (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Action.js:224:18)
at Emitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:58:19)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/joist/js/Sim.js:842:48
id: Bayes Chrome
Approximately 3/18/2020, 10:15:44 PM
bending-light : phet-io-state-fuzz : require.js : run
https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io-wrappers/state/?sim=bending-light&phetioDebug&fuzz&postMessageToParent&postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload
Uncaught Error: Uncaught Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/assert/js/assert.js?bust=1584597600505:22:13)
at PhetioAPIValidation.assertAPIError (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:277:15)
at PhetioAPIValidation.onSimStarted (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:106:16)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io/js/phetioEngine.js:158:27
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/TinyEmitter.js:65:53)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:33:29
at Emitter.execute (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Action.js:224:18)
at Emitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:58:19)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/joist/js/Sim.js:842:48
id: Bayes Chrome
Approximately 3/18/2020, 10:15:44 PM
bending-light : phet-io-state-fuzz : require.js : run
https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io-wrappers/state/?sim=bending-light&phetioDebug&fuzz&postMessageToParent&postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload
Uncaught Error: Uncaught Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/assert/js/assert.js?bust=1584612057568:22:13)
at PhetioAPIValidation.assertAPIError (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:277:15)
at PhetioAPIValidation.onSimStarted (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:106:16)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io/js/phetioEngine.js:158:27
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/TinyEmitter.js:65:53)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:33:29
at Emitter.execute (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Action.js:224:18)
at Emitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:58:19)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/joist/js/Sim.js:842:48
id: Bayes Chrome
Approximately 3/18/2020, 10:15:44 PM
bending-light : phet-io-state-fuzz : require.js : run
https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io-wrappers/state/?sim=bending-light&phetioDebug&fuzz&postMessageToParent&postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload
Uncaught Error: Uncaught Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/assert/js/assert.js?bust=1584612057577:22:13)
at PhetioAPIValidation.assertAPIError (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:277:15)
at PhetioAPIValidation.onSimStarted (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:106:16)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io/js/phetioEngine.js:158:27
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/TinyEmitter.js:65:53)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:33:29
at Emitter.execute (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Action.js:224:18)
at Emitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:58:19)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/joist/js/Sim.js:842:48
id: Bayes Chrome
Approximately 3/18/2020, 10:15:44 PM
bending-light : phet-io-studio-fuzz : require.js : run
https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/studio/?sim=bending-light&phetioDebug&fuzz&postMessageToParent&postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload
Uncaught Error: Uncaught Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/assert/js/assert.js?bust=1584601684049:22:13)
at PhetioAPIValidation.assertAPIError (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:277:15)
at PhetioAPIValidation.onSimStarted (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:106:16)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io/js/phetioEngine.js:158:27
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/TinyEmitter.js:65:53)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:33:29
at Emitter.execute (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Action.js:224:18)
at Emitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:58:19)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/joist/js/Sim.js:842:48
id: Bayes Chrome
Approximately 3/18/2020, 10:15:44 PM
bending-light : phet-io-studio-fuzz : require.js : run
https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/studio/?sim=bending-light&phetioDebug&fuzz&postMessageToParent&postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload
Uncaught Error: Uncaught Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/assert/js/assert.js?bust=1584615095455:22:13)
at PhetioAPIValidation.assertAPIError (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:277:15)
at PhetioAPIValidation.onSimStarted (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:106:16)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io/js/phetioEngine.js:158:27
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/TinyEmitter.js:65:53)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:33:29
at Emitter.execute (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Action.js:224:18)
at Emitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:58:19)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/joist/js/Sim.js:842:48
id: Bayes Chrome
Approximately 3/18/2020, 10:15:44 PM
bending-light : phet-io-studio-fuzz : require.js : run
https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/studio/?sim=bending-light&phetioDebug&fuzz&postMessageToParent&postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload
Uncaught Error: Uncaught Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/assert/js/assert.js?bust=1584625523016:22:13)
at PhetioAPIValidation.assertAPIError (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:277:15)
at PhetioAPIValidation.onSimStarted (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:106:16)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io/js/phetioEngine.js:158:27
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/TinyEmitter.js:65:53)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:33:29
at Emitter.execute (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Action.js:224:18)
at Emitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:58:19)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/joist/js/Sim.js:842:48
id: Bayes Chrome
```
|
1.0
|
CT PhET-iO API error - ```
bending-light : phet-io-fuzz : require.js : load
https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/bending-light/bending-light_en.html?postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload&brand=phet-io&phetioStandalone&ea&fuzz&memoryLimit=1000
Query: brand=phet-io&phetioStandalone&ea&fuzz&memoryLimit=1000
Uncaught Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/assert/js/assert.js?bust=1584609658817:22:13)
at PhetioAPIValidation.assertAPIError (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:277:15)
at PhetioAPIValidation.onSimStarted (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:106:16)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io/js/phetioEngine.js:158:27
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/TinyEmitter.js:65:53)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:33:29
at Emitter.execute (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Action.js:224:18)
at Emitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:58:19)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/joist/js/Sim.js:842:48
id: Bayes Chrome
Approximately 3/18/2020, 10:15:44 PM
bending-light : phet-io-fuzz : require.js : run
https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/bending-light/bending-light_en.html?postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload&brand=phet-io&phetioStandalone&ea&fuzz&memoryLimit=1000
Query: brand=phet-io&phetioStandalone&ea&fuzz&memoryLimit=1000
Uncaught Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/assert/js/assert.js?bust=1584609658817:22:13)
at PhetioAPIValidation.assertAPIError (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:277:15)
at PhetioAPIValidation.onSimStarted (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:106:16)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io/js/phetioEngine.js:158:27
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/TinyEmitter.js:65:53)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:33:29
at Emitter.execute (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Action.js:224:18)
at Emitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:58:19)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/joist/js/Sim.js:842:48
id: Bayes Chrome
Approximately 3/18/2020, 10:15:44 PM
bending-light : phet-io-mirror-inputs-fuzz : require.js : run
https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io-wrappers/mirror-inputs/?sim=bending-light&phetioDebug&fuzz&postMessageToParent&postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload
Uncaught Error: Uncaught Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/assert/js/assert.js?bust=1584600800566:22:13)
at PhetioAPIValidation.assertAPIError (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:277:15)
at PhetioAPIValidation.onSimStarted (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:106:16)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io/js/phetioEngine.js:158:27
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/TinyEmitter.js:65:53)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:33:29
at Emitter.execute (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Action.js:224:18)
at Emitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:58:19)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/joist/js/Sim.js:842:48
id: Bayes Chrome
Approximately 3/18/2020, 10:15:44 PM
bending-light : phet-io-mirror-inputs-fuzz : require.js : run
https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io-wrappers/mirror-inputs/?sim=bending-light&phetioDebug&fuzz&postMessageToParent&postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload
Uncaught Error: Uncaught Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/assert/js/assert.js?bust=1584623806278:22:13)
at PhetioAPIValidation.assertAPIError (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:277:15)
at PhetioAPIValidation.onSimStarted (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:106:16)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io/js/phetioEngine.js:158:27
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/TinyEmitter.js:65:53)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:33:29
at Emitter.execute (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Action.js:224:18)
at Emitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:58:19)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/joist/js/Sim.js:842:48
id: Bayes Chrome
Approximately 3/18/2020, 10:15:44 PM
bending-light : phet-io-state-fuzz : require.js : run
https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io-wrappers/state/?sim=bending-light&phetioDebug&fuzz&postMessageToParent&postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload
Uncaught Error: Uncaught Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/assert/js/assert.js?bust=1584597600498:22:13)
at PhetioAPIValidation.assertAPIError (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:277:15)
at PhetioAPIValidation.onSimStarted (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:106:16)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io/js/phetioEngine.js:158:27
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/TinyEmitter.js:65:53)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:33:29
at Emitter.execute (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Action.js:224:18)
at Emitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:58:19)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/joist/js/Sim.js:842:48
id: Bayes Chrome
Approximately 3/18/2020, 10:15:44 PM
bending-light : phet-io-state-fuzz : require.js : run
https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io-wrappers/state/?sim=bending-light&phetioDebug&fuzz&postMessageToParent&postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload
Uncaught Error: Uncaught Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/assert/js/assert.js?bust=1584597600505:22:13)
at PhetioAPIValidation.assertAPIError (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:277:15)
at PhetioAPIValidation.onSimStarted (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:106:16)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io/js/phetioEngine.js:158:27
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/TinyEmitter.js:65:53)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:33:29
at Emitter.execute (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Action.js:224:18)
at Emitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:58:19)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/joist/js/Sim.js:842:48
id: Bayes Chrome
Approximately 3/18/2020, 10:15:44 PM
bending-light : phet-io-state-fuzz : require.js : run
https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io-wrappers/state/?sim=bending-light&phetioDebug&fuzz&postMessageToParent&postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload
Uncaught Error: Uncaught Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/assert/js/assert.js?bust=1584612057568:22:13)
at PhetioAPIValidation.assertAPIError (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:277:15)
at PhetioAPIValidation.onSimStarted (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:106:16)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io/js/phetioEngine.js:158:27
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/TinyEmitter.js:65:53)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:33:29
at Emitter.execute (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Action.js:224:18)
at Emitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:58:19)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/joist/js/Sim.js:842:48
id: Bayes Chrome
Approximately 3/18/2020, 10:15:44 PM
bending-light : phet-io-state-fuzz : require.js : run
https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io-wrappers/state/?sim=bending-light&phetioDebug&fuzz&postMessageToParent&postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload
Uncaught Error: Uncaught Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/assert/js/assert.js?bust=1584612057577:22:13)
at PhetioAPIValidation.assertAPIError (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:277:15)
at PhetioAPIValidation.onSimStarted (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:106:16)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io/js/phetioEngine.js:158:27
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/TinyEmitter.js:65:53)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:33:29
at Emitter.execute (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Action.js:224:18)
at Emitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:58:19)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/joist/js/Sim.js:842:48
id: Bayes Chrome
Approximately 3/18/2020, 10:15:44 PM
bending-light : phet-io-studio-fuzz : require.js : run
https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/studio/?sim=bending-light&phetioDebug&fuzz&postMessageToParent&postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload
Uncaught Error: Uncaught Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/assert/js/assert.js?bust=1584601684049:22:13)
at PhetioAPIValidation.assertAPIError (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:277:15)
at PhetioAPIValidation.onSimStarted (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:106:16)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io/js/phetioEngine.js:158:27
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/TinyEmitter.js:65:53)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:33:29
at Emitter.execute (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Action.js:224:18)
at Emitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:58:19)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/joist/js/Sim.js:842:48
id: Bayes Chrome
Approximately 3/18/2020, 10:15:44 PM
bending-light : phet-io-studio-fuzz : require.js : run
https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/studio/?sim=bending-light&phetioDebug&fuzz&postMessageToParent&postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload
Uncaught Error: Uncaught Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/assert/js/assert.js?bust=1584615095455:22:13)
at PhetioAPIValidation.assertAPIError (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:277:15)
at PhetioAPIValidation.onSimStarted (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:106:16)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io/js/phetioEngine.js:158:27
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/TinyEmitter.js:65:53)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:33:29
at Emitter.execute (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Action.js:224:18)
at Emitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:58:19)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/joist/js/Sim.js:842:48
id: Bayes Chrome
Approximately 3/18/2020, 10:15:44 PM
bending-light : phet-io-studio-fuzz : require.js : run
https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/studio/?sim=bending-light&phetioDebug&fuzz&postMessageToParent&postMessageOnLoad&postMessageOnError&postMessageOnBeforeUnload
Uncaught Error: Uncaught Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
Error: Assertion failed: PhET-iO API error:
bendingLight.introScreen.bottomMediumProperty: 5. When the sim is finished starting up, all non-dynamic schema entries must be registered.
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/assert/js/assert.js?bust=1584625523016:22:13)
at PhetioAPIValidation.assertAPIError (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:277:15)
at PhetioAPIValidation.onSimStarted (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/tandem/js/phetioAPIValidation.js:106:16)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/phet-io/js/phetioEngine.js:158:27
at TinyEmitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/TinyEmitter.js:65:53)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:33:29
at Emitter.execute (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Action.js:224:18)
at Emitter.emit (https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/axon/js/Emitter.js:58:19)
at https://bayes.colorado.edu/continuous-testing/snapshot-1584591344628/joist/js/Sim.js:842:48
id: Bayes Chrome
```
|
test
|
ct phet io api error bending light phet io fuzz require js load query brand phet io phetiostandalone ea fuzz memorylimit uncaught error assertion failed phet io api error bendinglight introscreen bottommediumproperty when the sim is finished starting up all non dynamic schema entries must be registered error assertion failed phet io api error bendinglight introscreen bottommediumproperty when the sim is finished starting up all non dynamic schema entries must be registered at window assertions assertfunction at phetioapivalidation assertapierror at phetioapivalidation onsimstarted at at tinyemitter emit at at emitter execute at emitter emit at id bayes chrome approximately pm bending light phet io fuzz require js run query brand phet io phetiostandalone ea fuzz memorylimit uncaught error assertion failed phet io api error bendinglight introscreen bottommediumproperty when the sim is finished starting up all non dynamic schema entries must be registered error assertion failed phet io api error bendinglight introscreen bottommediumproperty when the sim is finished starting up all non dynamic schema entries must be registered at window assertions assertfunction at phetioapivalidation assertapierror at phetioapivalidation onsimstarted at at tinyemitter emit at at emitter execute at emitter emit at id bayes chrome approximately pm bending light phet io mirror inputs fuzz require js run uncaught error uncaught error assertion failed phet io api error bendinglight introscreen bottommediumproperty when the sim is finished starting up all non dynamic schema entries must be registered error assertion failed phet io api error bendinglight introscreen bottommediumproperty when the sim is finished starting up all non dynamic schema entries must be registered at window assertions assertfunction at phetioapivalidation assertapierror at phetioapivalidation onsimstarted at at tinyemitter emit at at emitter execute at emitter emit at id bayes chrome approximately pm bending light phet io mirror inputs fuzz require js run uncaught error uncaught error assertion failed phet io api error bendinglight introscreen bottommediumproperty when the sim is finished starting up all non dynamic schema entries must be registered error assertion failed phet io api error bendinglight introscreen bottommediumproperty when the sim is finished starting up all non dynamic schema entries must be registered at window assertions assertfunction at phetioapivalidation assertapierror at phetioapivalidation onsimstarted at at tinyemitter emit at at emitter execute at emitter emit at id bayes chrome approximately pm bending light phet io state fuzz require js run uncaught error uncaught error assertion failed phet io api error bendinglight introscreen bottommediumproperty when the sim is finished starting up all non dynamic schema entries must be registered error assertion failed phet io api error bendinglight introscreen bottommediumproperty when the sim is finished starting up all non dynamic schema entries must be registered at window assertions assertfunction at phetioapivalidation assertapierror at phetioapivalidation onsimstarted at at tinyemitter emit at at emitter execute at emitter emit at id bayes chrome approximately pm bending light phet io state fuzz require js run uncaught error uncaught error assertion failed phet io api error bendinglight introscreen bottommediumproperty when the sim is finished starting up all non dynamic schema entries must be registered error assertion failed phet io api error bendinglight introscreen bottommediumproperty when the sim is finished starting up all non dynamic schema entries must be registered at window assertions assertfunction at phetioapivalidation assertapierror at phetioapivalidation onsimstarted at at tinyemitter emit at at emitter execute at emitter emit at id bayes chrome approximately pm bending light phet io state fuzz require js run uncaught error uncaught error assertion failed phet io api error bendinglight introscreen bottommediumproperty when the sim is finished starting up all non dynamic schema entries must be registered error assertion failed phet io api error bendinglight introscreen bottommediumproperty when the sim is finished starting up all non dynamic schema entries must be registered at window assertions assertfunction at phetioapivalidation assertapierror at phetioapivalidation onsimstarted at at tinyemitter emit at at emitter execute at emitter emit at id bayes chrome approximately pm bending light phet io state fuzz require js run uncaught error uncaught error assertion failed phet io api error bendinglight introscreen bottommediumproperty when the sim is finished starting up all non dynamic schema entries must be registered error assertion failed phet io api error bendinglight introscreen bottommediumproperty when the sim is finished starting up all non dynamic schema entries must be registered at window assertions assertfunction at phetioapivalidation assertapierror at phetioapivalidation onsimstarted at at tinyemitter emit at at emitter execute at emitter emit at id bayes chrome approximately pm bending light phet io studio fuzz require js run uncaught error uncaught error assertion failed phet io api error bendinglight introscreen bottommediumproperty when the sim is finished starting up all non dynamic schema entries must be registered error assertion failed phet io api error bendinglight introscreen bottommediumproperty when the sim is finished starting up all non dynamic schema entries must be registered at window assertions assertfunction at phetioapivalidation assertapierror at phetioapivalidation onsimstarted at at tinyemitter emit at at emitter execute at emitter emit at id bayes chrome approximately pm bending light phet io studio fuzz require js run uncaught error uncaught error assertion failed phet io api error bendinglight introscreen bottommediumproperty when the sim is finished starting up all non dynamic schema entries must be registered error assertion failed phet io api error bendinglight introscreen bottommediumproperty when the sim is finished starting up all non dynamic schema entries must be registered at window assertions assertfunction at phetioapivalidation assertapierror at phetioapivalidation onsimstarted at at tinyemitter emit at at emitter execute at emitter emit at id bayes chrome approximately pm bending light phet io studio fuzz require js run uncaught error uncaught error assertion failed phet io api error bendinglight introscreen bottommediumproperty when the sim is finished starting up all non dynamic schema entries must be registered error assertion failed phet io api error bendinglight introscreen bottommediumproperty when the sim is finished starting up all non dynamic schema entries must be registered at window assertions assertfunction at phetioapivalidation assertapierror at phetioapivalidation onsimstarted at at tinyemitter emit at at emitter execute at emitter emit at id bayes chrome
| 1
|
312,180
| 26,845,071,264
|
IssuesEvent
|
2023-02-03 06:00:26
|
sonic-net/sonic-mgmt
|
https://api.github.com/repos/sonic-net/sonic-mgmt
|
closed
|
Validate headroom usage for PFC Traffic
|
Test gap
|
<!--
If you are reporting a new issue, make sure that we do not have any duplicates
already open. You can ensure this by searching the issue list for this
repository. If there is a duplicate, please close your issue and add a comment
to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to
include the BUG REPORT INFORMATION shown below. If you fail to provide this
information within 7 days, we cannot debug your issue and will close it. We
will, however, reopen it if you later provide the information.
For more information about reporting issues, see
https://github.com/sonic-net/SONiC/wiki#report-issues
---------------------------------------------------
GENERAL SUPPORT INFORMATION
---------------------------------------------------
The GitHub issue tracker is for bug reports and feature requests.
General support can be found at the following locations:
- SONiC Support Forums - https://groups.google.com/forum/#!forum/sonicproject
---------------------------------------------------
BUG REPORT INFORMATION
---------------------------------------------------
Use the commands below to provide key information from your environment:
You do NOT have to include this information if this is a FEATURE REQUEST
-->
**Description**
Validating PFC headroom usage for varying response times to PFC Pause Frames from different DUTs. Test Case can be found here https://github.com/developfast/sonic-mgmt/blob/dojha/headroom-doc/docs/testplan/pfc/PFC_PAUSE_RESPONSE_HEADROOM_README.md
<!--
Briefly describe the problem you are having in a few paragraphs.
-->
|
1.0
|
Validate headroom usage for PFC Traffic - <!--
If you are reporting a new issue, make sure that we do not have any duplicates
already open. You can ensure this by searching the issue list for this
repository. If there is a duplicate, please close your issue and add a comment
to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to
include the BUG REPORT INFORMATION shown below. If you fail to provide this
information within 7 days, we cannot debug your issue and will close it. We
will, however, reopen it if you later provide the information.
For more information about reporting issues, see
https://github.com/sonic-net/SONiC/wiki#report-issues
---------------------------------------------------
GENERAL SUPPORT INFORMATION
---------------------------------------------------
The GitHub issue tracker is for bug reports and feature requests.
General support can be found at the following locations:
- SONiC Support Forums - https://groups.google.com/forum/#!forum/sonicproject
---------------------------------------------------
BUG REPORT INFORMATION
---------------------------------------------------
Use the commands below to provide key information from your environment:
You do NOT have to include this information if this is a FEATURE REQUEST
-->
**Description**
Validating PFC headroom usage for varying response times to PFC Pause Frames from different DUTs. Test Case can be found here https://github.com/developfast/sonic-mgmt/blob/dojha/headroom-doc/docs/testplan/pfc/PFC_PAUSE_RESPONSE_HEADROOM_README.md
<!--
Briefly describe the problem you are having in a few paragraphs.
-->
|
test
|
validate headroom usage for pfc traffic if you are reporting a new issue make sure that we do not have any duplicates already open you can ensure this by searching the issue list for this repository if there is a duplicate please close your issue and add a comment to the existing issue instead if you suspect your issue is a bug please edit your issue description to include the bug report information shown below if you fail to provide this information within days we cannot debug your issue and will close it we will however reopen it if you later provide the information for more information about reporting issues see general support information the github issue tracker is for bug reports and feature requests general support can be found at the following locations sonic support forums bug report information use the commands below to provide key information from your environment you do not have to include this information if this is a feature request description validating pfc headroom usage for varying response times to pfc pause frames from different duts test case can be found here briefly describe the problem you are having in a few paragraphs
| 1
|
123,239
| 26,234,219,852
|
IssuesEvent
|
2023-01-05 05:02:26
|
flutter/website
|
https://api.github.com/repos/flutter/website
|
closed
|
'Codelabs' page issue
|
p2-medium e2-days codelab-external
|
Page URL: https://codelabs.developers.google.com/codelabs/flutter#0
Page source: https://github.com/flutter/website/tree/master/src/docs/codelabs/index.md
Found a typo? You can fix it yourself by going to the page source and clicking the pencil icon. Or finish creating this issue.
Description of issue:
No " next " button for mobile web view, so it stuck
This is a normal working Desktop version ;
This is same page on mobile and cant go to next page , the button is actually there but too down, only little blue is there.. and completely cant see in some mobile browsers like opera mobile ;
|
1.0
|
'Codelabs' page issue - Page URL: https://codelabs.developers.google.com/codelabs/flutter#0
Page source: https://github.com/flutter/website/tree/master/src/docs/codelabs/index.md
Found a typo? You can fix it yourself by going to the page source and clicking the pencil icon. Or finish creating this issue.
Description of issue:
No " next " button for mobile web view, so it stuck
This is a normal working Desktop version ;
This is same page on mobile and cant go to next page , the button is actually there but too down, only little blue is there.. and completely cant see in some mobile browsers like opera mobile ;
|
non_test
|
codelabs page issue page url page source found a typo you can fix it yourself by going to the page source and clicking the pencil icon or finish creating this issue description of issue no next button for mobile web view so it stuck this is a normal working desktop version this is same page on mobile and cant go to next page the button is actually there but too down only little blue is there and completely cant see in some mobile browsers like opera mobile
| 0
|
118,036
| 11,960,803,511
|
IssuesEvent
|
2020-04-05 05:10:54
|
Josh-McMillan/Community-Game
|
https://api.github.com/repos/Josh-McMillan/Community-Game
|
opened
|
Instructions for Repository Access
|
documentation
|
It seems that not everyone has access to fork or clone the repo, so it's probably a good idea in the Workflow wiki page to add that people need to be added as collaborators before they can get started working.
The process for that is as outlined:
- Message me (SpatialPlays) on Discord with either your email or your GitHub username
- I'll add you to the collaborators list as soon as I have an opportunity
- After you're added, you may continue as outlined in the Workflow documentation
|
1.0
|
Instructions for Repository Access - It seems that not everyone has access to fork or clone the repo, so it's probably a good idea in the Workflow wiki page to add that people need to be added as collaborators before they can get started working.
The process for that is as outlined:
- Message me (SpatialPlays) on Discord with either your email or your GitHub username
- I'll add you to the collaborators list as soon as I have an opportunity
- After you're added, you may continue as outlined in the Workflow documentation
|
non_test
|
instructions for repository access it seems that not everyone has access to fork or clone the repo so it s probably a good idea in the workflow wiki page to add that people need to be added as collaborators before they can get started working the process for that is as outlined message me spatialplays on discord with either your email or your github username i ll add you to the collaborators list as soon as i have an opportunity after you re added you may continue as outlined in the workflow documentation
| 0
|
476,514
| 13,745,920,879
|
IssuesEvent
|
2020-10-06 04:18:11
|
canonical-web-and-design/maas-ui
|
https://api.github.com/repos/canonical-web-and-design/maas-ui
|
closed
|
[UI] maas should allow comment on why a system is broken
|
Priority: Medium
|
Bug originally filed by smoser at https://bugs.launchpad.net/bugs/1441160
we just had a situation where a collegue of mine asked "Why is system X in BROKEN". I did not know, as another team member had put it in.
It would be nice if maas did 2 things:
a.) stored the user who did this
this would allow me to ask the user who did, why it was in BROKEN
b.) stored a text field as "why".
this would allow us or the user to input a external tracking id or comments as to what was wrong.
|
1.0
|
[UI] maas should allow comment on why a system is broken - Bug originally filed by smoser at https://bugs.launchpad.net/bugs/1441160
we just had a situation where a collegue of mine asked "Why is system X in BROKEN". I did not know, as another team member had put it in.
It would be nice if maas did 2 things:
a.) stored the user who did this
this would allow me to ask the user who did, why it was in BROKEN
b.) stored a text field as "why".
this would allow us or the user to input a external tracking id or comments as to what was wrong.
|
non_test
|
maas should allow comment on why a system is broken bug originally filed by smoser at we just had a situation where a collegue of mine asked why is system x in broken i did not know as another team member had put it in it would be nice if maas did things a stored the user who did this this would allow me to ask the user who did why it was in broken b stored a text field as why this would allow us or the user to input a external tracking id or comments as to what was wrong
| 0
|
758,231
| 26,546,946,062
|
IssuesEvent
|
2023-01-20 01:39:55
|
vircadia/vircadia-web-sdk
|
https://api.github.com/repos/vircadia/vircadia-web-sdk
|
opened
|
Add protocol and API for determining metaverse that the domain server is using
|
enhancement high priority
|
If the user (app + SDK) logs into one metaverse but the domain server is using a different metaverse then things won't work.
|
1.0
|
Add protocol and API for determining metaverse that the domain server is using - If the user (app + SDK) logs into one metaverse but the domain server is using a different metaverse then things won't work.
|
non_test
|
add protocol and api for determining metaverse that the domain server is using if the user app sdk logs into one metaverse but the domain server is using a different metaverse then things won t work
| 0
|
156,266
| 5,966,419,845
|
IssuesEvent
|
2017-05-30 13:59:00
|
voteamerica/voteamerica.github.io
|
https://api.github.com/repos/voteamerica/voteamerica.github.io
|
closed
|
Remove 866-OURVOTE from the top bar
|
high priority
|
Looks like this slipped back in after we removed it last year. People were calling this instead of our phone line, which resulted in the other phone line being clogged.
Call 1-866-OURVOTE for voter support.
|
1.0
|
Remove 866-OURVOTE from the top bar - Looks like this slipped back in after we removed it last year. People were calling this instead of our phone line, which resulted in the other phone line being clogged.
Call 1-866-OURVOTE for voter support.
|
non_test
|
remove ourvote from the top bar looks like this slipped back in after we removed it last year people were calling this instead of our phone line which resulted in the other phone line being clogged call ourvote for voter support
| 0
|
104,027
| 8,958,629,463
|
IssuesEvent
|
2019-01-27 15:52:18
|
publiclab/PublicLab.Editor
|
https://api.github.com/repos/publiclab/PublicLab.Editor
|
closed
|
Add test for empty bold tags functionality
|
first-timers-only in progress testing
|
Hi, this is a [first-timers-only issue](https://publiclab.github.io/community-toolbox/#r=all). This means we've worked to make it more legible to folks who either **haven't contributed to our codebase before, or even folks who haven't contributed to open source before**.
If that's you, we're interested in helping you take the first step and can answer questions and help you out as you do. Note that we're especially interested in contributions from people from groups underrepresented in free and open source software!
We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝
If you have contributed before, **consider leaving this one for someone new**, and looking through our general [help wanted](https://github.com/publiclab/publiclab.Editor/labels/help-wanted) issues. Thanks!
### 🤔 What you will need to know.
Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.
### Problem
To implement a test for detecting empty bold tags (for #198). This test would help automate builds determine whether the #198 functionality is working fine or not.
### 📋 Step by Step
- [ ] 🙋 **Claim this issue**: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!
- [ ] Fork and clone this repository
- [ ] Create a new uniquely named branch and checkout to it
- [ ] Install dependencies using `npm install`
- [ ] Install grunt cli using `npm install -g grunt-cli`
### Implement the Solution
The corresponding test for this feature can be implemented by adding the following funtion to `./spec/javascripts/rich_text_module_spec.js` file.
````js
it("displays alert for empty bold tags",function() {
var enter = jQuery.Event("keydown", {keyCode:13})
var temp_el = module.textarea
module.setMode('markdown');
module.textarea.innerHTML = '**';
$(temp_el).trigger(enter)
module.textarea.innerHTML = '**';
$(temp_el).trigger(enter)
expect($('.invalid-bold-tags-warning').length).not.toBeNull();
})
````
- [ ] Build using `grunt build`
- [ ] Test your assertions using `grunt jasmine`. If all specs pass, follow next steps.
- [ ] 💾 **Commit** your changes
- [ ] 🔀 **Start a Pull Request**. There are two ways how you can start a pull request:
1. If you are familiar with the terminal or would like to learn it, [here is a great tutorial](https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github) on how to send a pull request using the terminal.
2. You can also [edit files directly in your browser](https://help.github.com/articles/editing-files-in-your-repository/) and open a pull request from there.
- [ ] 🏁 **Done** Ask in comments for a review :)
### 🤔❓ Questions?
Leave a comment below!
### Is someone else already working on this?
We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. **If someone seem stuck, offer them some help!** Otherwise, [take a look at some other issues you can help with](https://publiclab.github.io/community-toolbox/#r=all). Thanks!
|
1.0
|
Add test for empty bold tags functionality - Hi, this is a [first-timers-only issue](https://publiclab.github.io/community-toolbox/#r=all). This means we've worked to make it more legible to folks who either **haven't contributed to our codebase before, or even folks who haven't contributed to open source before**.
If that's you, we're interested in helping you take the first step and can answer questions and help you out as you do. Note that we're especially interested in contributions from people from groups underrepresented in free and open source software!
We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝
If you have contributed before, **consider leaving this one for someone new**, and looking through our general [help wanted](https://github.com/publiclab/publiclab.Editor/labels/help-wanted) issues. Thanks!
### 🤔 What you will need to know.
Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.
### Problem
To implement a test for detecting empty bold tags (for #198). This test would help automate builds determine whether the #198 functionality is working fine or not.
### 📋 Step by Step
- [ ] 🙋 **Claim this issue**: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!
- [ ] Fork and clone this repository
- [ ] Create a new uniquely named branch and checkout to it
- [ ] Install dependencies using `npm install`
- [ ] Install grunt cli using `npm install -g grunt-cli`
### Implement the Solution
The corresponding test for this feature can be implemented by adding the following funtion to `./spec/javascripts/rich_text_module_spec.js` file.
````js
it("displays alert for empty bold tags",function() {
var enter = jQuery.Event("keydown", {keyCode:13})
var temp_el = module.textarea
module.setMode('markdown');
module.textarea.innerHTML = '**';
$(temp_el).trigger(enter)
module.textarea.innerHTML = '**';
$(temp_el).trigger(enter)
expect($('.invalid-bold-tags-warning').length).not.toBeNull();
})
````
- [ ] Build using `grunt build`
- [ ] Test your assertions using `grunt jasmine`. If all specs pass, follow next steps.
- [ ] 💾 **Commit** your changes
- [ ] 🔀 **Start a Pull Request**. There are two ways how you can start a pull request:
1. If you are familiar with the terminal or would like to learn it, [here is a great tutorial](https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github) on how to send a pull request using the terminal.
2. You can also [edit files directly in your browser](https://help.github.com/articles/editing-files-in-your-repository/) and open a pull request from there.
- [ ] 🏁 **Done** Ask in comments for a review :)
### 🤔❓ Questions?
Leave a comment below!
### Is someone else already working on this?
We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. **If someone seem stuck, offer them some help!** Otherwise, [take a look at some other issues you can help with](https://publiclab.github.io/community-toolbox/#r=all). Thanks!
|
test
|
add test for empty bold tags functionality hi this is a this means we ve worked to make it more legible to folks who either haven t contributed to our codebase before or even folks who haven t contributed to open source before if that s you we re interested in helping you take the first step and can answer questions and help you out as you do note that we re especially interested in contributions from people from groups underrepresented in free and open source software we know that the process of creating a pull request is the biggest barrier for new contributors this issue is for you 💝 if you have contributed before consider leaving this one for someone new and looking through our general issues thanks 🤔 what you will need to know nothing this issue is meant to welcome you to open source we are happy to walk you through the process problem to implement a test for detecting empty bold tags for this test would help automate builds determine whether the functionality is working fine or not 📋 step by step 🙋 claim this issue comment below if someone else has claimed it ask if they ve opened a pull request already and if they re stuck maybe you can help them solve a problem or move it along fork and clone this repository create a new uniquely named branch and checkout to it install dependencies using npm install install grunt cli using npm install g grunt cli implement the solution the corresponding test for this feature can be implemented by adding the following funtion to spec javascripts rich text module spec js file js it displays alert for empty bold tags function var enter jquery event keydown keycode var temp el module textarea module setmode markdown module textarea innerhtml temp el trigger enter module textarea innerhtml temp el trigger enter expect invalid bold tags warning length not tobenull build using grunt build test your assertions using grunt jasmine if all specs pass follow next steps 💾 commit your changes 🔀 start a pull request there are two ways how you can start a pull request if you are familiar with the terminal or would like to learn it on how to send a pull request using the terminal you can also and open a pull request from there 🏁 done ask in comments for a review 🤔❓ questions leave a comment below is someone else already working on this we encourage you to link to this issue by mentioning the issue in your pull request so we can see if someone s already started on it if someone seem stuck offer them some help otherwise thanks
| 1
|
30,650
| 2,724,500,785
|
IssuesEvent
|
2015-04-14 18:11:26
|
CruxFramework/crux-widgets
|
https://api.github.com/repos/CruxFramework/crux-widgets
|
closed
|
Error when using DeviceAdaptive widgets with renderWidgetWithIDs options turned on
|
bug imported Milestone-M14-C2 Priority-Medium
|
_From [trbustam...@gmail.com](https://code.google.com/u/117925048001886933493/) on March 25, 2014 18:47:15_
What steps will reproduce the problem? 1. declare one DeviceAdaptive widget on your view
2. configure on Crux.properties renderWidgetsWithIDs=true
3. run the application What is the expected output? What do you see instead? A Class Cast exception occurs on ViewFactoryUtils.updateWidgetElementId method What version of the product are you using? On what operating system? On what Browser? Any browser Please provide any additional information below.
_Original issue: http://code.google.com/p/crux-framework/issues/detail?id=338_
|
1.0
|
Error when using DeviceAdaptive widgets with renderWidgetWithIDs options turned on - _From [trbustam...@gmail.com](https://code.google.com/u/117925048001886933493/) on March 25, 2014 18:47:15_
What steps will reproduce the problem? 1. declare one DeviceAdaptive widget on your view
2. configure on Crux.properties renderWidgetsWithIDs=true
3. run the application What is the expected output? What do you see instead? A Class Cast exception occurs on ViewFactoryUtils.updateWidgetElementId method What version of the product are you using? On what operating system? On what Browser? Any browser Please provide any additional information below.
_Original issue: http://code.google.com/p/crux-framework/issues/detail?id=338_
|
non_test
|
error when using deviceadaptive widgets with renderwidgetwithids options turned on from on march what steps will reproduce the problem declare one deviceadaptive widget on your view configure on crux properties renderwidgetswithids true run the application what is the expected output what do you see instead a class cast exception occurs on viewfactoryutils updatewidgetelementid method what version of the product are you using on what operating system on what browser any browser please provide any additional information below original issue
| 0
|
8,283
| 2,977,936,211
|
IssuesEvent
|
2015-07-16 00:33:41
|
andmarti1424/scim
|
https://api.github.com/repos/andmarti1424/scim
|
closed
|
Undo does not undo 'copies'
|
fixed - test pending
|
Thanks so much for making this andmarti1424; great program!
If I type 'ma', then paste it with 'ca', then hit 'u'. It says "No undo's left."
|
1.0
|
Undo does not undo 'copies' - Thanks so much for making this andmarti1424; great program!
If I type 'ma', then paste it with 'ca', then hit 'u'. It says "No undo's left."
|
test
|
undo does not undo copies thanks so much for making this great program if i type ma then paste it with ca then hit u it says no undo s left
| 1
|
711,001
| 24,446,711,669
|
IssuesEvent
|
2022-10-06 18:37:57
|
thoth-station/thamos
|
https://api.github.com/repos/thoth-station/thamos
|
closed
|
thoth search url of output results in 404
|
priority/critical-urgent kind/bug triage/accepted
|
## Bug description
doing a `thamos advise` on ps-cv results in a not usable link to thoth-station/search
### Steps to Reproduce
Steps to reproduce the behavior:
1. close
2. run `thamos advise`
3. click on link https://thoth-station.ninja/search/adviser-220819120526-a10d2f0803fbe0f2/summary
4. See error
### Actual behavior
shows broken link
### Expected behavior
shows accessible link
### Environment information
```
$ thamos version
Thamos Client version: 1.27.9
Thoth API https://khemenu.thoth-station.ninja/api/v1: 0.35.2
```
### Additional context
<!-- Add any additional context information about the problem here. -->
|
1.0
|
thoth search url of output results in 404 - ## Bug description
doing a `thamos advise` on ps-cv results in a not usable link to thoth-station/search
### Steps to Reproduce
Steps to reproduce the behavior:
1. close
2. run `thamos advise`
3. click on link https://thoth-station.ninja/search/adviser-220819120526-a10d2f0803fbe0f2/summary
4. See error
### Actual behavior
shows broken link
### Expected behavior
shows accessible link
### Environment information
```
$ thamos version
Thamos Client version: 1.27.9
Thoth API https://khemenu.thoth-station.ninja/api/v1: 0.35.2
```
### Additional context
<!-- Add any additional context information about the problem here. -->
|
non_test
|
thoth search url of output results in bug description doing a thamos advise on ps cv results in a not usable link to thoth station search steps to reproduce steps to reproduce the behavior close run thamos advise click on link see error actual behavior shows broken link expected behavior shows accessible link environment information thamos version thamos client version thoth api additional context
| 0
|
238,124
| 18,234,341,585
|
IssuesEvent
|
2021-10-01 03:54:37
|
Jordan-Sun/WashULostNFound
|
https://api.github.com/repos/Jordan-Sun/WashULostNFound
|
closed
|
Instructions Tutorial in the start that you can skip or go through
|
documentation init
|
Home page is not self explanatory, maybe have a tutorial in the start that explains what you have to do and runs you through the app’s functionality.
|
1.0
|
Instructions Tutorial in the start that you can skip or go through - Home page is not self explanatory, maybe have a tutorial in the start that explains what you have to do and runs you through the app’s functionality.
|
non_test
|
instructions tutorial in the start that you can skip or go through home page is not self explanatory maybe have a tutorial in the start that explains what you have to do and runs you through the app’s functionality
| 0
|
238,325
| 19,712,191,183
|
IssuesEvent
|
2022-01-13 07:10:54
|
milvus-io/milvus
|
https://api.github.com/repos/milvus-io/milvus
|
opened
|
[Bug]: [benchmark][cluster][performance] 50 million data sets create hnsw index, the index creation time does not decrease with the increase of indexnodes
|
kind/bug needs-triage test/benchmark performance tuning
|
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Environment
```markdown
- Milvus version:
- Deployment mode(standalone or cluster):
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS):
- CPU/Memory:
- GPU:
- Others:
```
### Current Behavior
**50 million data sets create hnsw index, the index creation time does not decrease with the increase of indexnodes**
<img width="1344" alt="截屏2022-01-13 15 09 40" src="https://user-images.githubusercontent.com/26307815/149282464-e4eaac4e-850d-4a9a-9b23-7c8bd54d1778.png">
### Expected Behavior
**50 million datasets create hnsw index, the index creation time decreases with the increase of indexnodes**
### Steps To Reproduce
```markdown
1、create collection
2、insert 50 million dataset
3、flush collection
4、build index
```
### Anything else?
_No response_
|
1.0
|
[Bug]: [benchmark][cluster][performance] 50 million data sets create hnsw index, the index creation time does not decrease with the increase of indexnodes - ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Environment
```markdown
- Milvus version:
- Deployment mode(standalone or cluster):
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS):
- CPU/Memory:
- GPU:
- Others:
```
### Current Behavior
**50 million data sets create hnsw index, the index creation time does not decrease with the increase of indexnodes**
<img width="1344" alt="截屏2022-01-13 15 09 40" src="https://user-images.githubusercontent.com/26307815/149282464-e4eaac4e-850d-4a9a-9b23-7c8bd54d1778.png">
### Expected Behavior
**50 million datasets create hnsw index, the index creation time decreases with the increase of indexnodes**
### Steps To Reproduce
```markdown
1、create collection
2、insert 50 million dataset
3、flush collection
4、build index
```
### Anything else?
_No response_
|
test
|
million data sets create hnsw index the index creation time does not decrease with the increase of indexnodes is there an existing issue for this i have searched the existing issues environment markdown milvus version deployment mode standalone or cluster sdk version e g pymilvus os ubuntu or centos cpu memory gpu others current behavior million data sets create hnsw index the index creation time does not decrease with the increase of indexnodes img width alt src expected behavior million datasets create hnsw index the index creation time decreases with the increase of indexnodes steps to reproduce markdown 、create collection 、insert million dataset 、flush collection 、build index anything else no response
| 1
|
42,976
| 7,009,692,541
|
IssuesEvent
|
2017-12-19 20:07:03
|
habitat-sh/habitat
|
https://api.github.com/repos/habitat-sh/habitat
|
closed
|
Tutorial: config overrides not working in studio
|
A-documentation C-chore E-easy
|
Hi, I was going through https://www.habitat.sh/tutorials/getting-started/linux/process-build/ and hit a snag. Passing in config overrides when starting the application doesn't appear to work.
Screenshot of relevant files and behavior:
System info:
```
+$ uname -a
Linux silverweed 4.10.13-1-ARCH #1 SMP PREEMPT Thu Apr 27 12:15:09 CEST 2017 x86_64 GNU/Linux
+$ hab --version
hab 0.26.1/20170715033447
```
If it's useful, here's the Rust debug info:
```
[1][default:/src:0]# RUST_LOG=debug RUST_BACKTRACE=1 HAB_MYTUTORIALAPP='message = "Habitat rocks!"' hab start trevorbramble/mytutorialapp
DEBUG:habitat_common::ui: InputStream(stdin): { is_a_terminal(): true }
DEBUG:habitat_common::ui: OutputStream(stdout): { is_colored(): true, supports_color(): true, is_a_terminal(): true }
DEBUG:habitat_common::ui: OutputStream(stderr): { is_colored(): true, supports_color(): true, is_a_terminal(): true }
DEBUG:habitat_core::os::process::imp: Calling execvp(): ("/hab/pkgs/core/hab-launcher/4435/20170715015238/bin/hab-launch") ["start", "trevorbramble/mytutorialapp"]
DEBUG:habitat_launcher::server: Starting Supervisor...
DEBUG:habitat_launcher::server: Supervisor exited: exit code: 84
[1]+ Done hab sup run $* > /hab/sup/default/sup.log (wd: /)
(wd now: /src)
```
The super-boring env situation:
```
[2][default:/src:0]# env |grep HAB| grep -v HAB_AUTH_TOKEN
HAB_ORIGIN=trevorbramble
[3][default:/src:0]# logout
:$ env |grep HAB| grep -v HAB_AUTH_TOKEN
+$
```
|
1.0
|
Tutorial: config overrides not working in studio - Hi, I was going through https://www.habitat.sh/tutorials/getting-started/linux/process-build/ and hit a snag. Passing in config overrides when starting the application doesn't appear to work.
Screenshot of relevant files and behavior:
System info:
```
+$ uname -a
Linux silverweed 4.10.13-1-ARCH #1 SMP PREEMPT Thu Apr 27 12:15:09 CEST 2017 x86_64 GNU/Linux
+$ hab --version
hab 0.26.1/20170715033447
```
If it's useful, here's the Rust debug info:
```
[1][default:/src:0]# RUST_LOG=debug RUST_BACKTRACE=1 HAB_MYTUTORIALAPP='message = "Habitat rocks!"' hab start trevorbramble/mytutorialapp
DEBUG:habitat_common::ui: InputStream(stdin): { is_a_terminal(): true }
DEBUG:habitat_common::ui: OutputStream(stdout): { is_colored(): true, supports_color(): true, is_a_terminal(): true }
DEBUG:habitat_common::ui: OutputStream(stderr): { is_colored(): true, supports_color(): true, is_a_terminal(): true }
DEBUG:habitat_core::os::process::imp: Calling execvp(): ("/hab/pkgs/core/hab-launcher/4435/20170715015238/bin/hab-launch") ["start", "trevorbramble/mytutorialapp"]
DEBUG:habitat_launcher::server: Starting Supervisor...
DEBUG:habitat_launcher::server: Supervisor exited: exit code: 84
[1]+ Done hab sup run $* > /hab/sup/default/sup.log (wd: /)
(wd now: /src)
```
The super-boring env situation:
```
[2][default:/src:0]# env |grep HAB| grep -v HAB_AUTH_TOKEN
HAB_ORIGIN=trevorbramble
[3][default:/src:0]# logout
:$ env |grep HAB| grep -v HAB_AUTH_TOKEN
+$
```
|
non_test
|
tutorial config overrides not working in studio hi i was going through and hit a snag passing in config overrides when starting the application doesn t appear to work screenshot of relevant files and behavior system info uname a linux silverweed arch smp preempt thu apr cest gnu linux hab version hab if it s useful here s the rust debug info rust log debug rust backtrace hab mytutorialapp message habitat rocks hab start trevorbramble mytutorialapp debug habitat common ui inputstream stdin is a terminal true debug habitat common ui outputstream stdout is colored true supports color true is a terminal true debug habitat common ui outputstream stderr is colored true supports color true is a terminal true debug habitat core os process imp calling execvp hab pkgs core hab launcher bin hab launch debug habitat launcher server starting supervisor debug habitat launcher server supervisor exited exit code done hab sup run hab sup default sup log wd wd now src the super boring env situation env grep hab grep v hab auth token hab origin trevorbramble logout env grep hab grep v hab auth token
| 0
|
6,899
| 2,868,636,031
|
IssuesEvent
|
2015-06-05 20:04:51
|
GoogleCloudPlatform/kubernetes
|
https://api.github.com/repos/GoogleCloudPlatform/kubernetes
|
closed
|
Multiple e2e tests fail with "Missing service account" when run in parallel
|
priority/P0 team/testing
|
Some examples below (from our Jenkins e2e continuous integration):
Docker Containers should be able to override the image's default command and arguments
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/docker_containers.go:81
Failed to create pod: Pod "client-containers-6bd82955-0ae5-11e5-9b61-42010af01555" is forbidden: Missing service account e2e-tests-containers-afbfc705-8f08-4d3a-8927-cff5845472f7/default: <nil>
=========
hostDir MOD volume on tmpfs should have the correct mode
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/host_path.go:75
Failed to create pod: Pod "pod-ed43f1af-0aea-11e5-8379-42010af01555" is forbidden: Missing service account e2e-tests-hostdir-2f80b7b2-0256-4246-8187-342aab3eda0f/default: <nil>
==================
Pods should be restarted with a docker exec "cat /tmp/health" liveness probe
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/pods.go:451
creating pod liveness-exec
Expected error:
<*errors.StatusError | 0xc208546d00>: {
ErrStatus: {
TypeMeta: {Kind: "", APIVersion: ""},
ListMeta: {SelfLink: "", ResourceVersion: ""},
Status: "Failure",
Message: "Pod \"liveness-exec\" is forbidden: Missing service account e2e-test-44eb32f3-0af7-11e5-b2d4-42010af01555/default: <nil>",
Reason: "Forbidden",
Details: {ID: "liveness-exec", Kind: "Pod", Causes: nil, RetryAfterSeconds: 0},
Code: 403,
},
}
Pod "liveness-exec" is forbidden: Missing service account e2e-test-44eb32f3-0af7-11e5-b2d4-42010af01555/default: <nil>
not to have occurred
|
1.0
|
Multiple e2e tests fail with "Missing service account" when run in parallel - Some examples below (from our Jenkins e2e continuous integration):
Docker Containers should be able to override the image's default command and arguments
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/docker_containers.go:81
Failed to create pod: Pod "client-containers-6bd82955-0ae5-11e5-9b61-42010af01555" is forbidden: Missing service account e2e-tests-containers-afbfc705-8f08-4d3a-8927-cff5845472f7/default: <nil>
=========
hostDir MOD volume on tmpfs should have the correct mode
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/host_path.go:75
Failed to create pod: Pod "pod-ed43f1af-0aea-11e5-8379-42010af01555" is forbidden: Missing service account e2e-tests-hostdir-2f80b7b2-0256-4246-8187-342aab3eda0f/default: <nil>
==================
Pods should be restarted with a docker exec "cat /tmp/health" liveness probe
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/pods.go:451
creating pod liveness-exec
Expected error:
<*errors.StatusError | 0xc208546d00>: {
ErrStatus: {
TypeMeta: {Kind: "", APIVersion: ""},
ListMeta: {SelfLink: "", ResourceVersion: ""},
Status: "Failure",
Message: "Pod \"liveness-exec\" is forbidden: Missing service account e2e-test-44eb32f3-0af7-11e5-b2d4-42010af01555/default: <nil>",
Reason: "Forbidden",
Details: {ID: "liveness-exec", Kind: "Pod", Causes: nil, RetryAfterSeconds: 0},
Code: 403,
},
}
Pod "liveness-exec" is forbidden: Missing service account e2e-test-44eb32f3-0af7-11e5-b2d4-42010af01555/default: <nil>
not to have occurred
|
test
|
multiple tests fail with missing service account when run in parallel some examples below from our jenkins continuous integration docker containers should be able to override the image s default command and arguments go src github com googlecloudplatform kubernetes output dockerized go src github com googlecloudplatform kubernetes test docker containers go failed to create pod pod client containers is forbidden missing service account tests containers default hostdir mod volume on tmpfs should have the correct mode go src github com googlecloudplatform kubernetes output dockerized go src github com googlecloudplatform kubernetes test host path go failed to create pod pod pod is forbidden missing service account tests hostdir default pods should be restarted with a docker exec cat tmp health liveness probe go src github com googlecloudplatform kubernetes output dockerized go src github com googlecloudplatform kubernetes test pods go creating pod liveness exec expected error errstatus typemeta kind apiversion listmeta selflink resourceversion status failure message pod liveness exec is forbidden missing service account test default reason forbidden details id liveness exec kind pod causes nil retryafterseconds code pod liveness exec is forbidden missing service account test default not to have occurred
| 1
|
206,205
| 7,110,200,692
|
IssuesEvent
|
2018-01-17 09:49:13
|
cims-bioko/cims-tablet
|
https://api.github.com/repos/cims-bioko/cims-tablet
|
closed
|
Model residencies in separate table
|
internal / refactoring low priority
|
Currently residencies are modeled as an Individual attribute.
To facilitate syncing data with the server, we will instead model residencies using a separate residency table. The table will include columns for Individual Id and Location Id.
|
1.0
|
Model residencies in separate table - Currently residencies are modeled as an Individual attribute.
To facilitate syncing data with the server, we will instead model residencies using a separate residency table. The table will include columns for Individual Id and Location Id.
|
non_test
|
model residencies in separate table currently residencies are modeled as an individual attribute to facilitate syncing data with the server we will instead model residencies using a separate residency table the table will include columns for individual id and location id
| 0
|
178,895
| 6,619,863,372
|
IssuesEvent
|
2017-09-21 13:47:38
|
Jdoyle112/SurvivalBowl
|
https://api.github.com/repos/Jdoyle112/SurvivalBowl
|
closed
|
Change roster select tool to resemble draftkings
|
priority:major type:improvement
|
Have all available players in a list with an add button which would populate a roster form to the right with your selected lineup.
|
1.0
|
Change roster select tool to resemble draftkings - Have all available players in a list with an add button which would populate a roster form to the right with your selected lineup.
|
non_test
|
change roster select tool to resemble draftkings have all available players in a list with an add button which would populate a roster form to the right with your selected lineup
| 0
|
35,215
| 14,633,021,407
|
IssuesEvent
|
2020-12-24 00:22:31
|
layer5io/meshkit
|
https://api.github.com/repos/layer5io/meshkit
|
closed
|
Segmentation fault in constructObject function
|
kind/bug priority/high service-mesh/istio
|
**Description**
When installing istio, the install fails with the following error
```
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x16d84be]
goroutine 14 [running]:
github.com/layer5io/meshkit/utils/kubernetes.constructObject(0x22c0620, 0xc0003c51e0, 0xc000aba2c0, 0x17, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
/home/utkarsh/go/pkg/mod/github.com/layer5io/meshkit@v0.1.31/utils/kubernetes/apply-manifest.go:107 +0xbe
github.com/layer5io/meshkit/utils/kubernetes.(*Client).ApplyManifest(0xc0005ebc00, 0xc0004a63c0, 0xef, 0xf0, 0x0, 0x0, 0x7f7f6c180001, 0xc0008878b0, 0x0)
/home/utkarsh/go/pkg/mod/github.com/layer5io/meshkit@v0.1.31/utils/kubernetes/apply-manifest.go:48 +0x1d1
github.com/layer5io/meshery-istio/istio.(*Istio).applyManifest(0xc0000f4000, 0xc0004a63c0, 0xef, 0xf0, 0x0, 0x0, 0x0, 0x0, 0x4161fd)
/home/utkarsh/dev/layer5/meshery-istio/istio/install.go:98 +0x136
github.com/layer5io/meshery-istio/istio.(*Istio).installIstio(0xc0000f4000, 0xc000a0b500, 0xc0000cb618, 0x5, 0xc0000cb000, 0x7, 0xc0007fc284, 0x7f7f96a5e7d0, 0xc00092d8c0, 0xc000073740)
/home/utkarsh/dev/layer5/meshery-istio/istio/install.go:52 +0x534
github.com/layer5io/meshery-istio/istio.(*Istio).ApplyOperation.func1(0xc0005bc0a0, 0xc0000caff8, 0x5, 0xc0000cb000, 0x7, 0xc0000cb010, 0xb, 0x0, 0x0, 0x0, ...)
/home/utkarsh/dev/layer5/meshery-istio/istio/istio.go:50 +0xd1
created by github.com/layer5io/meshery-istio/istio.(*Istio).ApplyOperation
/home/utkarsh/dev/layer5/meshery-istio/istio/istio.go:48 +0x277
exit status 2
```
**Expected Behavior**
Installation should succeed without any issues.
**Environment:**
- Meshkit - v0.1.31
---
**To Reproduce**
Steps to reproduce the behavior:
1. Get the latest version of istio adapter
2. Install istio from the meshery ui
|
1.0
|
Segmentation fault in constructObject function - **Description**
When installing istio, the install fails with the following error
```
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x16d84be]
goroutine 14 [running]:
github.com/layer5io/meshkit/utils/kubernetes.constructObject(0x22c0620, 0xc0003c51e0, 0xc000aba2c0, 0x17, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
/home/utkarsh/go/pkg/mod/github.com/layer5io/meshkit@v0.1.31/utils/kubernetes/apply-manifest.go:107 +0xbe
github.com/layer5io/meshkit/utils/kubernetes.(*Client).ApplyManifest(0xc0005ebc00, 0xc0004a63c0, 0xef, 0xf0, 0x0, 0x0, 0x7f7f6c180001, 0xc0008878b0, 0x0)
/home/utkarsh/go/pkg/mod/github.com/layer5io/meshkit@v0.1.31/utils/kubernetes/apply-manifest.go:48 +0x1d1
github.com/layer5io/meshery-istio/istio.(*Istio).applyManifest(0xc0000f4000, 0xc0004a63c0, 0xef, 0xf0, 0x0, 0x0, 0x0, 0x0, 0x4161fd)
/home/utkarsh/dev/layer5/meshery-istio/istio/install.go:98 +0x136
github.com/layer5io/meshery-istio/istio.(*Istio).installIstio(0xc0000f4000, 0xc000a0b500, 0xc0000cb618, 0x5, 0xc0000cb000, 0x7, 0xc0007fc284, 0x7f7f96a5e7d0, 0xc00092d8c0, 0xc000073740)
/home/utkarsh/dev/layer5/meshery-istio/istio/install.go:52 +0x534
github.com/layer5io/meshery-istio/istio.(*Istio).ApplyOperation.func1(0xc0005bc0a0, 0xc0000caff8, 0x5, 0xc0000cb000, 0x7, 0xc0000cb010, 0xb, 0x0, 0x0, 0x0, ...)
/home/utkarsh/dev/layer5/meshery-istio/istio/istio.go:50 +0xd1
created by github.com/layer5io/meshery-istio/istio.(*Istio).ApplyOperation
/home/utkarsh/dev/layer5/meshery-istio/istio/istio.go:48 +0x277
exit status 2
```
**Expected Behavior**
Installation should succeed without any issues.
**Environment:**
- Meshkit - v0.1.31
---
**To Reproduce**
Steps to reproduce the behavior:
1. Get the latest version of istio adapter
2. Install istio from the meshery ui
|
non_test
|
segmentation fault in constructobject function description when installing istio the install fails with the following error panic runtime error invalid memory address or nil pointer dereference goroutine github com meshkit utils kubernetes constructobject home utkarsh go pkg mod github com meshkit utils kubernetes apply manifest go github com meshkit utils kubernetes client applymanifest home utkarsh go pkg mod github com meshkit utils kubernetes apply manifest go github com meshery istio istio istio applymanifest home utkarsh dev meshery istio istio install go github com meshery istio istio istio installistio home utkarsh dev meshery istio istio install go github com meshery istio istio istio applyoperation home utkarsh dev meshery istio istio istio go created by github com meshery istio istio istio applyoperation home utkarsh dev meshery istio istio istio go exit status expected behavior installation should succeed without any issues environment meshkit to reproduce steps to reproduce the behavior get the latest version of istio adapter install istio from the meshery ui
| 0
|
110,744
| 9,476,736,404
|
IssuesEvent
|
2019-04-19 16:03:58
|
daniel-vera-g/dotfiles
|
https://api.github.com/repos/daniel-vera-g/dotfiles
|
closed
|
Organize indicators in right way
|
config to-test
|
`~/.local/share/indicators/application/ordering-override.keyfile `:
```
[Ordering Index Overrides]
nm-applet=1
gnome-power-manager=2
ibus=3
gst-keyboard-xkb=4
gsd-keyboard-xkb=5
indicator-solaar=6
Shutter=7
AutoKey=8
copyq=9
caffeine-cup-empty=10
redshift=11
safeeyes=12
dropbox-client-2872=13
indicator-diskman=14
multiload=15
netspeed=16
```
Sources:
https://www.google.com/search?client=ubuntu&channel=fs&q=organize+indicators+ubuntu&ie=utf-8&oe=utf-8 | organize indicators ubuntu - Google-Suche
https://askubuntu.com/questions/987322/how-to-re-arrange-application-indicators-in-top-bar-ubuntu-17-10 | How to re-arrange application indicators in top bar? (Ubuntu 17.10) - Ask Ubuntu
http://www.webupd8.org/2011/06/how-to-change-application-indicators.html | How To Change Application Indicators Order In The Ubuntu Indicator Applet ~ Web Upd8: Ubuntu / Linux blog
https://askubuntu.com/questions/26114/is-it-possible-to-change-the-order-of-icons-in-the-indicator-applet | Is it possible to change the order of icons in the indicator applet? - Ask Ubuntu
|
1.0
|
Organize indicators in right way - `~/.local/share/indicators/application/ordering-override.keyfile `:
```
[Ordering Index Overrides]
nm-applet=1
gnome-power-manager=2
ibus=3
gst-keyboard-xkb=4
gsd-keyboard-xkb=5
indicator-solaar=6
Shutter=7
AutoKey=8
copyq=9
caffeine-cup-empty=10
redshift=11
safeeyes=12
dropbox-client-2872=13
indicator-diskman=14
multiload=15
netspeed=16
```
Sources:
https://www.google.com/search?client=ubuntu&channel=fs&q=organize+indicators+ubuntu&ie=utf-8&oe=utf-8 | organize indicators ubuntu - Google-Suche
https://askubuntu.com/questions/987322/how-to-re-arrange-application-indicators-in-top-bar-ubuntu-17-10 | How to re-arrange application indicators in top bar? (Ubuntu 17.10) - Ask Ubuntu
http://www.webupd8.org/2011/06/how-to-change-application-indicators.html | How To Change Application Indicators Order In The Ubuntu Indicator Applet ~ Web Upd8: Ubuntu / Linux blog
https://askubuntu.com/questions/26114/is-it-possible-to-change-the-order-of-icons-in-the-indicator-applet | Is it possible to change the order of icons in the indicator applet? - Ask Ubuntu
|
test
|
organize indicators in right way local share indicators application ordering override keyfile nm applet gnome power manager ibus gst keyboard xkb gsd keyboard xkb indicator solaar shutter autokey copyq caffeine cup empty redshift safeeyes dropbox client indicator diskman multiload netspeed sources organize indicators ubuntu google suche how to re arrange application indicators in top bar ubuntu ask ubuntu how to change application indicators order in the ubuntu indicator applet web ubuntu linux blog is it possible to change the order of icons in the indicator applet ask ubuntu
| 1
|
109,182
| 9,370,497,852
|
IssuesEvent
|
2019-04-03 13:35:55
|
cockroachdb/cockroach
|
https://api.github.com/repos/cockroachdb/cockroach
|
closed
|
roachtest: ycsb/F/nodes=3/cpu=32 failed
|
C-test-failure O-roachtest O-robot
|
SHA: https://github.com/cockroachdb/cockroach/commits/c6df752eefe4609b8a5bbada0955f79a2cfb790e
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=ycsb/F/nodes=3/cpu=32 PKG=roachtest TESTTIMEOUT=5m STRESSFLAGS='-maxtime 20m -timeout 10m' 2>&1 | tee /tmp/stress.log
```
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=1217767&tab=buildLog
```
The test failed on master:
cluster.go:1255,ycsb.go:29,ycsb.go:65,test.go:1228: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/bin/roachprod start teamcity-1217767-ycsb-f-nodes-3-cpu-32:1-3 returned:
stderr:
stdout:
.
* - Any user, connecting as root, can read or write any data in your cluster.
* - There is no network encryption nor authentication, and thus no confidentiality.
*
* Check out how to secure your cluster: https://www.cockroachlabs.com/docs/v19.1/secure-a-cluster.html
*
*
* ERROR: failed to start server: invalid --advertise-addr: lookup ip-10-12-47-252 on 10.12.0.2:53: no such host
*
Failed running "start"
E190403 06:47:47.201911 1 cli/error.go:229 exit status 1
Error: exit status 1
Failed running "start"
github.com/cockroachdb/cockroach/pkg/cmd/roachprod/install.Cockroach.Start.func7
/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/install/cockroach.go:397
github.com/cockroachdb/cockroach/pkg/cmd/roachprod/install.(*SyncedCluster).Parallel.func1.1
/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/install/cluster_synced.go:1417
runtime.goexit
/usr/local/go/src/runtime/asm_amd64.s:1333:
I190403 06:47:47.217918 1 cluster_synced.go:1499 command failed
: exit status 1
```
|
2.0
|
roachtest: ycsb/F/nodes=3/cpu=32 failed - SHA: https://github.com/cockroachdb/cockroach/commits/c6df752eefe4609b8a5bbada0955f79a2cfb790e
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=ycsb/F/nodes=3/cpu=32 PKG=roachtest TESTTIMEOUT=5m STRESSFLAGS='-maxtime 20m -timeout 10m' 2>&1 | tee /tmp/stress.log
```
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=1217767&tab=buildLog
```
The test failed on master:
cluster.go:1255,ycsb.go:29,ycsb.go:65,test.go:1228: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/bin/roachprod start teamcity-1217767-ycsb-f-nodes-3-cpu-32:1-3 returned:
stderr:
stdout:
.
* - Any user, connecting as root, can read or write any data in your cluster.
* - There is no network encryption nor authentication, and thus no confidentiality.
*
* Check out how to secure your cluster: https://www.cockroachlabs.com/docs/v19.1/secure-a-cluster.html
*
*
* ERROR: failed to start server: invalid --advertise-addr: lookup ip-10-12-47-252 on 10.12.0.2:53: no such host
*
Failed running "start"
E190403 06:47:47.201911 1 cli/error.go:229 exit status 1
Error: exit status 1
Failed running "start"
github.com/cockroachdb/cockroach/pkg/cmd/roachprod/install.Cockroach.Start.func7
/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/install/cockroach.go:397
github.com/cockroachdb/cockroach/pkg/cmd/roachprod/install.(*SyncedCluster).Parallel.func1.1
/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/install/cluster_synced.go:1417
runtime.goexit
/usr/local/go/src/runtime/asm_amd64.s:1333:
I190403 06:47:47.217918 1 cluster_synced.go:1499 command failed
: exit status 1
```
|
test
|
roachtest ycsb f 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 ycsb f nodes cpu pkg roachtest testtimeout stressflags maxtime timeout tee tmp stress log failed test the test failed on master cluster go ycsb go ycsb go test go home agent work go src github com cockroachdb cockroach bin roachprod start teamcity ycsb f nodes cpu returned stderr stdout any user connecting as root can read or write any data in your cluster there is no network encryption nor authentication and thus no confidentiality check out how to secure your cluster error failed to start server invalid advertise addr lookup ip on no such host failed running start cli error go exit status error exit status failed running start github com cockroachdb cockroach pkg cmd roachprod install cockroach start home agent work go src github com cockroachdb cockroach pkg cmd roachprod install cockroach go github com cockroachdb cockroach pkg cmd roachprod install syncedcluster parallel home agent work go src github com cockroachdb cockroach pkg cmd roachprod install cluster synced go runtime goexit usr local go src runtime asm s cluster synced go command failed exit status
| 1
|
13,444
| 3,146,610,904
|
IssuesEvent
|
2015-09-15 00:25:57
|
openpowerquality/opqbox2
|
https://api.github.com/repos/openpowerquality/opqbox2
|
opened
|
Enable firmware to assess state of charge of supercapicitor
|
G2 Design 2
|
How does the processor know about the state-of-charge of the supercap? The firmware should behave differently, based on the state of charge, during power disturbances, right? Don't make the mistake of assuming that you know the state of charge based on time, and voltage measurements... lots of ways to get burned doing that. (From Alex)
|
1.0
|
Enable firmware to assess state of charge of supercapicitor - How does the processor know about the state-of-charge of the supercap? The firmware should behave differently, based on the state of charge, during power disturbances, right? Don't make the mistake of assuming that you know the state of charge based on time, and voltage measurements... lots of ways to get burned doing that. (From Alex)
|
non_test
|
enable firmware to assess state of charge of supercapicitor how does the processor know about the state of charge of the supercap the firmware should behave differently based on the state of charge during power disturbances right don t make the mistake of assuming that you know the state of charge based on time and voltage measurements lots of ways to get burned doing that from alex
| 0
|
768,935
| 26,988,141,032
|
IssuesEvent
|
2023-02-09 17:37:18
|
slynch8/10x
|
https://api.github.com/repos/slynch8/10x
|
closed
|
Pressing ; pastes random line
|
bug Priority 2 current
|
Here you can see the problem in action:
I'm pressing ; followed by Ctrl+Z several times. The line being pasted is not in the clipboard, it seems to be coming from a different location in the same file. This only started occurring after a recent update. I've checked that the ; key is not associated to any command.
|
1.0
|
Pressing ; pastes random line - Here you can see the problem in action:
I'm pressing ; followed by Ctrl+Z several times. The line being pasted is not in the clipboard, it seems to be coming from a different location in the same file. This only started occurring after a recent update. I've checked that the ; key is not associated to any command.
|
non_test
|
pressing pastes random line here you can see the problem in action i m pressing followed by ctrl z several times the line being pasted is not in the clipboard it seems to be coming from a different location in the same file this only started occurring after a recent update i ve checked that the key is not associated to any command
| 0
|
140,378
| 18,901,265,047
|
IssuesEvent
|
2021-11-16 01:21:57
|
anichols11/togglr-ui
|
https://api.github.com/repos/anichols11/togglr-ui
|
opened
|
WS-2019-0427 (Medium) detected in elliptic-6.4.0.tgz
|
security vulnerability
|
## WS-2019-0427 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>elliptic-6.4.0.tgz</b></p></summary>
<p>EC cryptography</p>
<p>Library home page: <a href="https://registry.npmjs.org/elliptic/-/elliptic-6.4.0.tgz">https://registry.npmjs.org/elliptic/-/elliptic-6.4.0.tgz</a></p>
<p>Path to dependency file: togglr-ui/package.json</p>
<p>Path to vulnerable library: togglr-ui/node_modules/elliptic/package.json</p>
<p>
Dependency Hierarchy:
- nuxt-1.4.2.tgz (Root Library)
- webpack-3.12.0.tgz
- node-libs-browser-2.1.0.tgz
- crypto-browserify-3.12.0.tgz
- create-ecdh-4.0.3.tgz
- :x: **elliptic-6.4.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The function getNAF() in elliptic library has information leakage. This issue is mitigated in version 6.5.2
<p>Publish Date: 2019-11-22
<p>URL: <a href=https://github.com/indutny/elliptic/commit/ec735edde187a43693197f6fa3667ceade751a3a>WS-2019-0427</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.0</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: N/A
- Attack Complexity: N/A
- Privileges Required: N/A
- User Interaction: N/A
- Scope: N/A
- Impact Metrics:
- Confidentiality Impact: N/A
- Integrity Impact: N/A
- Availability Impact: N/A
</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/indutny/elliptic/commit/ec735edde187a43693197f6fa3667ceade751a3a">https://github.com/indutny/elliptic/commit/ec735edde187a43693197f6fa3667ceade751a3a</a></p>
<p>Release Date: 2019-11-22</p>
<p>Fix Resolution: v6.5.2</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"elliptic","packageVersion":"6.4.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"nuxt:1.4.2;webpack:3.12.0;node-libs-browser:2.1.0;crypto-browserify:3.12.0;create-ecdh:4.0.3;elliptic:6.4.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"v6.5.2"}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2019-0427","vulnerabilityDetails":"The function getNAF() in elliptic library has information leakage. This issue is mitigated in version 6.5.2","vulnerabilityUrl":"https://github.com/indutny/elliptic/commit/ec735edde187a43693197f6fa3667ceade751a3a","cvss3Severity":"medium","cvss3Score":"5.0","cvss3Metrics":{"A":"N/A","AC":"N/A","PR":"N/A","S":"N/A","C":"N/A","UI":"N/A","AV":"N/A","I":"N/A"},"extraData":{}}</REMEDIATE> -->
|
True
|
WS-2019-0427 (Medium) detected in elliptic-6.4.0.tgz - ## WS-2019-0427 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>elliptic-6.4.0.tgz</b></p></summary>
<p>EC cryptography</p>
<p>Library home page: <a href="https://registry.npmjs.org/elliptic/-/elliptic-6.4.0.tgz">https://registry.npmjs.org/elliptic/-/elliptic-6.4.0.tgz</a></p>
<p>Path to dependency file: togglr-ui/package.json</p>
<p>Path to vulnerable library: togglr-ui/node_modules/elliptic/package.json</p>
<p>
Dependency Hierarchy:
- nuxt-1.4.2.tgz (Root Library)
- webpack-3.12.0.tgz
- node-libs-browser-2.1.0.tgz
- crypto-browserify-3.12.0.tgz
- create-ecdh-4.0.3.tgz
- :x: **elliptic-6.4.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The function getNAF() in elliptic library has information leakage. This issue is mitigated in version 6.5.2
<p>Publish Date: 2019-11-22
<p>URL: <a href=https://github.com/indutny/elliptic/commit/ec735edde187a43693197f6fa3667ceade751a3a>WS-2019-0427</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.0</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: N/A
- Attack Complexity: N/A
- Privileges Required: N/A
- User Interaction: N/A
- Scope: N/A
- Impact Metrics:
- Confidentiality Impact: N/A
- Integrity Impact: N/A
- Availability Impact: N/A
</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/indutny/elliptic/commit/ec735edde187a43693197f6fa3667ceade751a3a">https://github.com/indutny/elliptic/commit/ec735edde187a43693197f6fa3667ceade751a3a</a></p>
<p>Release Date: 2019-11-22</p>
<p>Fix Resolution: v6.5.2</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"elliptic","packageVersion":"6.4.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"nuxt:1.4.2;webpack:3.12.0;node-libs-browser:2.1.0;crypto-browserify:3.12.0;create-ecdh:4.0.3;elliptic:6.4.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"v6.5.2"}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2019-0427","vulnerabilityDetails":"The function getNAF() in elliptic library has information leakage. This issue is mitigated in version 6.5.2","vulnerabilityUrl":"https://github.com/indutny/elliptic/commit/ec735edde187a43693197f6fa3667ceade751a3a","cvss3Severity":"medium","cvss3Score":"5.0","cvss3Metrics":{"A":"N/A","AC":"N/A","PR":"N/A","S":"N/A","C":"N/A","UI":"N/A","AV":"N/A","I":"N/A"},"extraData":{}}</REMEDIATE> -->
|
non_test
|
ws medium detected in elliptic tgz ws medium severity vulnerability vulnerable library elliptic tgz ec cryptography library home page a href path to dependency file togglr ui package json path to vulnerable library togglr ui node modules elliptic package json dependency hierarchy nuxt tgz root library webpack tgz node libs browser tgz crypto browserify tgz create ecdh tgz x elliptic tgz vulnerable library found in base branch master vulnerability details the function getnaf in elliptic library has information leakage this issue is mitigated in version publish date url a href cvss score details base score metrics exploitability metrics attack vector n a attack complexity n a privileges required n a user interaction n a scope n a impact metrics confidentiality impact n a integrity impact n a availability impact n a for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree nuxt webpack node libs browser crypto browserify create ecdh elliptic isminimumfixversionavailable true minimumfixversion basebranches vulnerabilityidentifier ws vulnerabilitydetails the function getnaf in elliptic library has information leakage this issue is mitigated in version vulnerabilityurl
| 0
|
30,528
| 4,210,157,037
|
IssuesEvent
|
2016-06-29 08:55:37
|
pythonapis/6ZJYP2PXGY5CWP2LWTZZFRIL
|
https://api.github.com/repos/pythonapis/6ZJYP2PXGY5CWP2LWTZZFRIL
|
reopened
|
fwCKnrq7gwgehjFtQlBdPiQT7Q9y1oFQPtoX+lQDgnIuK28jMt1i0E9B8QrV831FO/QwiOVYOCt9/h8rAXc1SinCJ4/Fr+09saLj8XZgyAgD95ajNZf2WecD5YDTWAUwMT01uhPiZb0Lyn8zzw6Hc7l8sK7FApRpPyoJKefp+U4=
|
design
|
0OrcSXu7y5KbI4sYxXCVXaVhLvaMX85OWz1zkqy49az816wbCNsCNrz/ZCZR9bzsAm+Vizqf6f2P02nYLajpu88Pdhf0d3stohXO8hK1Yutnmj/Z8+QdDTro7Xcor37WkippFsXqn9W6+WxOreOpG7VaJNa/+mJhjJfntT3Jw1lUkDznIxXx2DJDq7JXQr5YuyIri2UGt3tsLtFFy1n5N/f4Lge9OVMgnkV9c1tyuB6lYS72jF/OTls9c5KsuPWs2LVbDgGR5jjxgPB34oE0kdIYIQ6MxOGnm4VL4ouwM/76uz0ay3gR9DqMHXGCkfVctzDZW0rHZ3IyhZIlp4izEpPtsQH7oMt7E7y0tx8VqzNTPWJVr/LegPKtq+y40T92/3sX+YRiOlK8apEFHRQIx2Z14zwhxSngPwTssXy9isKI/SSKuMyiKmZpHKr7n21Jt5TMh4r9Tun+S28oLqo6jJ6wabUxxHw4klaW4kk6Yl8S24bQGUEygeweFciwmEVeYkx3HEi330RAuA3k3aIrUK8kcooV4dBEHUIVlmfEdVES24bQGUEygeweFciwmEVeU1aKAfMpHUwbFAwa9Us/G9JDWSQeJqIzzjVsUBms2Btk/Of3kU4VYClVdN38u55tpmn4yrobLCHO6fG6NvraQGX+QEXUqLHnjAr/F9INayxR2Qd2Dvsj5NgCOk1umnF4nAbKgVdvOxrRST27laQZ+kJy0bp2aqARBXVz1Ua5r9jA+H3kyulVFYPPtLb5vZ7knbTRX5gcgpqTZzNvZDLn2nDr/vyDQKfw2i1epcKoDra9fHpTiGiUeSPaFfNR7rhGbRKdwxQtLujPin79ePVceZ1xrbUxNwAld9ntB9Rb6bEeYiu+3C0/zytHaG3tbnfqbv5wwzWzBg9AzpYnLpDj4kwfq2CaHZzsi2D8TF96s7/EGoGVya1Y/tWSCgBXauO41Sks8OiFbs6juEJB27Du+JBfFZbLJdzmKWMlCKzAkRGLB7OquwTZR8/G9MB1Z0aaMhqOvvkQvPW6AAUyvjFFRdmmLw93Rtze5B3GkoqgnrYR4GWhlWvdcPZv79opWS+POjPZa207gIknuB+r3ZGnNFU2lNbi2V687tit4bcQSuQbe7X92qPoERaGmvRZQhEkM7ybBo8vZpFk7kp67M/aryqKSteCeIhlAiA8euDzEziJxfCWhjtdP1ns8WeAg8098wS5zhu03jtBeYjwRjkHDaJGMKKaJVHNqr6VhOZGNwg=
|
1.0
|
fwCKnrq7gwgehjFtQlBdPiQT7Q9y1oFQPtoX+lQDgnIuK28jMt1i0E9B8QrV831FO/QwiOVYOCt9/h8rAXc1SinCJ4/Fr+09saLj8XZgyAgD95ajNZf2WecD5YDTWAUwMT01uhPiZb0Lyn8zzw6Hc7l8sK7FApRpPyoJKefp+U4= - 0OrcSXu7y5KbI4sYxXCVXaVhLvaMX85OWz1zkqy49az816wbCNsCNrz/ZCZR9bzsAm+Vizqf6f2P02nYLajpu88Pdhf0d3stohXO8hK1Yutnmj/Z8+QdDTro7Xcor37WkippFsXqn9W6+WxOreOpG7VaJNa/+mJhjJfntT3Jw1lUkDznIxXx2DJDq7JXQr5YuyIri2UGt3tsLtFFy1n5N/f4Lge9OVMgnkV9c1tyuB6lYS72jF/OTls9c5KsuPWs2LVbDgGR5jjxgPB34oE0kdIYIQ6MxOGnm4VL4ouwM/76uz0ay3gR9DqMHXGCkfVctzDZW0rHZ3IyhZIlp4izEpPtsQH7oMt7E7y0tx8VqzNTPWJVr/LegPKtq+y40T92/3sX+YRiOlK8apEFHRQIx2Z14zwhxSngPwTssXy9isKI/SSKuMyiKmZpHKr7n21Jt5TMh4r9Tun+S28oLqo6jJ6wabUxxHw4klaW4kk6Yl8S24bQGUEygeweFciwmEVeYkx3HEi330RAuA3k3aIrUK8kcooV4dBEHUIVlmfEdVES24bQGUEygeweFciwmEVeU1aKAfMpHUwbFAwa9Us/G9JDWSQeJqIzzjVsUBms2Btk/Of3kU4VYClVdN38u55tpmn4yrobLCHO6fG6NvraQGX+QEXUqLHnjAr/F9INayxR2Qd2Dvsj5NgCOk1umnF4nAbKgVdvOxrRST27laQZ+kJy0bp2aqARBXVz1Ua5r9jA+H3kyulVFYPPtLb5vZ7knbTRX5gcgpqTZzNvZDLn2nDr/vyDQKfw2i1epcKoDra9fHpTiGiUeSPaFfNR7rhGbRKdwxQtLujPin79ePVceZ1xrbUxNwAld9ntB9Rb6bEeYiu+3C0/zytHaG3tbnfqbv5wwzWzBg9AzpYnLpDj4kwfq2CaHZzsi2D8TF96s7/EGoGVya1Y/tWSCgBXauO41Sks8OiFbs6juEJB27Du+JBfFZbLJdzmKWMlCKzAkRGLB7OquwTZR8/G9MB1Z0aaMhqOvvkQvPW6AAUyvjFFRdmmLw93Rtze5B3GkoqgnrYR4GWhlWvdcPZv79opWS+POjPZa207gIknuB+r3ZGnNFU2lNbi2V687tit4bcQSuQbe7X92qPoERaGmvRZQhEkM7ybBo8vZpFk7kp67M/aryqKSteCeIhlAiA8euDzEziJxfCWhjtdP1ns8WeAg8098wS5zhu03jtBeYjwRjkHDaJGMKKaJVHNqr6VhOZGNwg=
|
non_test
|
fr legpktq qexuqlhnjar
| 0
|
637,378
| 20,626,729,839
|
IssuesEvent
|
2022-03-07 23:37:49
|
AY2122S2-CS2113T-T09-3/tp
|
https://api.github.com/repos/AY2122S2-CS2113T-T09-3/tp
|
opened
|
Create greet, help & bye to help with the UI
|
type.Task priority.Low
|
Just general strings to interact with the administrator user
|
1.0
|
Create greet, help & bye to help with the UI - Just general strings to interact with the administrator user
|
non_test
|
create greet help bye to help with the ui just general strings to interact with the administrator user
| 0
|
138,222
| 18,771,760,046
|
IssuesEvent
|
2021-11-07 00:12:56
|
samqws-marketing/fico-xpress_vdlx-datagrid
|
https://api.github.com/repos/samqws-marketing/fico-xpress_vdlx-datagrid
|
opened
|
CVE-2020-7608 (Medium) detected in yargs-parser-13.1.1.tgz, yargs-parser-15.0.0.tgz
|
security vulnerability
|
## CVE-2020-7608 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>yargs-parser-13.1.1.tgz</b>, <b>yargs-parser-15.0.0.tgz</b></p></summary>
<p>
<details><summary><b>yargs-parser-13.1.1.tgz</b></p></summary>
<p>the mighty option parser used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/yargs-parser/-/yargs-parser-13.1.1.tgz">https://registry.npmjs.org/yargs-parser/-/yargs-parser-13.1.1.tgz</a></p>
<p>Path to dependency file: fico-xpress_vdlx-datagrid/package.json</p>
<p>Path to vulnerable library: fico-xpress_vdlx-datagrid/node_modules/yargs-parser/package.json</p>
<p>
Dependency Hierarchy:
- bestzip-2.1.5.tgz (Root Library)
- yargs-13.3.0.tgz
- :x: **yargs-parser-13.1.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>yargs-parser-15.0.0.tgz</b></p></summary>
<p>the mighty option parser used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/yargs-parser/-/yargs-parser-15.0.0.tgz">https://registry.npmjs.org/yargs-parser/-/yargs-parser-15.0.0.tgz</a></p>
<p>Path to dependency file: fico-xpress_vdlx-datagrid/package.json</p>
<p>Path to vulnerable library: fico-xpress_vdlx-datagrid/node_modules/purgecss/node_modules/yargs-parser/package.json</p>
<p>
Dependency Hierarchy:
- parcel-bundler-1.12.4.tgz (Root Library)
- htmlnano-0.2.5.tgz
- purgecss-1.4.1.tgz
- yargs-14.2.0.tgz
- :x: **yargs-parser-15.0.0.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/samqws-marketing/fico-xpress_vdlx-datagrid/commit/1034e9edaadc6cb260836b29dab13197a606790b">1034e9edaadc6cb260836b29dab13197a606790b</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
yargs-parser could be tricked into adding or modifying properties of Object.prototype using a "__proto__" payload.
<p>Publish Date: 2020-03-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7608>CVE-2020-7608</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: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/yargs/yargs-parser/commit/63810ca1ae1a24b08293a4d971e70e058c7a41e2">https://github.com/yargs/yargs-parser/commit/63810ca1ae1a24b08293a4d971e70e058c7a41e2</a></p>
<p>Release Date: 2020-06-05</p>
<p>Fix Resolution: 5.0.1;13.1.2;15.0.1;18.1.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"yargs-parser","packageVersion":"13.1.1","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"bestzip:2.1.5;yargs:13.3.0;yargs-parser:13.1.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"5.0.1;13.1.2;15.0.1;18.1.1"},{"packageType":"javascript/Node.js","packageName":"yargs-parser","packageVersion":"15.0.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"parcel-bundler:1.12.4;htmlnano:0.2.5;purgecss:1.4.1;yargs:14.2.0;yargs-parser:15.0.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"5.0.1;13.1.2;15.0.1;18.1.1"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-7608","vulnerabilityDetails":"yargs-parser could be tricked into adding or modifying properties of Object.prototype using a \"__proto__\" payload.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7608","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"Low","AC":"Low","PR":"Low","S":"Unchanged","C":"Low","UI":"None","AV":"Local","I":"Low"},"extraData":{}}</REMEDIATE> -->
|
True
|
CVE-2020-7608 (Medium) detected in yargs-parser-13.1.1.tgz, yargs-parser-15.0.0.tgz - ## CVE-2020-7608 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>yargs-parser-13.1.1.tgz</b>, <b>yargs-parser-15.0.0.tgz</b></p></summary>
<p>
<details><summary><b>yargs-parser-13.1.1.tgz</b></p></summary>
<p>the mighty option parser used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/yargs-parser/-/yargs-parser-13.1.1.tgz">https://registry.npmjs.org/yargs-parser/-/yargs-parser-13.1.1.tgz</a></p>
<p>Path to dependency file: fico-xpress_vdlx-datagrid/package.json</p>
<p>Path to vulnerable library: fico-xpress_vdlx-datagrid/node_modules/yargs-parser/package.json</p>
<p>
Dependency Hierarchy:
- bestzip-2.1.5.tgz (Root Library)
- yargs-13.3.0.tgz
- :x: **yargs-parser-13.1.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>yargs-parser-15.0.0.tgz</b></p></summary>
<p>the mighty option parser used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/yargs-parser/-/yargs-parser-15.0.0.tgz">https://registry.npmjs.org/yargs-parser/-/yargs-parser-15.0.0.tgz</a></p>
<p>Path to dependency file: fico-xpress_vdlx-datagrid/package.json</p>
<p>Path to vulnerable library: fico-xpress_vdlx-datagrid/node_modules/purgecss/node_modules/yargs-parser/package.json</p>
<p>
Dependency Hierarchy:
- parcel-bundler-1.12.4.tgz (Root Library)
- htmlnano-0.2.5.tgz
- purgecss-1.4.1.tgz
- yargs-14.2.0.tgz
- :x: **yargs-parser-15.0.0.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/samqws-marketing/fico-xpress_vdlx-datagrid/commit/1034e9edaadc6cb260836b29dab13197a606790b">1034e9edaadc6cb260836b29dab13197a606790b</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
yargs-parser could be tricked into adding or modifying properties of Object.prototype using a "__proto__" payload.
<p>Publish Date: 2020-03-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7608>CVE-2020-7608</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: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/yargs/yargs-parser/commit/63810ca1ae1a24b08293a4d971e70e058c7a41e2">https://github.com/yargs/yargs-parser/commit/63810ca1ae1a24b08293a4d971e70e058c7a41e2</a></p>
<p>Release Date: 2020-06-05</p>
<p>Fix Resolution: 5.0.1;13.1.2;15.0.1;18.1.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"yargs-parser","packageVersion":"13.1.1","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"bestzip:2.1.5;yargs:13.3.0;yargs-parser:13.1.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"5.0.1;13.1.2;15.0.1;18.1.1"},{"packageType":"javascript/Node.js","packageName":"yargs-parser","packageVersion":"15.0.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"parcel-bundler:1.12.4;htmlnano:0.2.5;purgecss:1.4.1;yargs:14.2.0;yargs-parser:15.0.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"5.0.1;13.1.2;15.0.1;18.1.1"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-7608","vulnerabilityDetails":"yargs-parser could be tricked into adding or modifying properties of Object.prototype using a \"__proto__\" payload.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7608","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"Low","AC":"Low","PR":"Low","S":"Unchanged","C":"Low","UI":"None","AV":"Local","I":"Low"},"extraData":{}}</REMEDIATE> -->
|
non_test
|
cve medium detected in yargs parser tgz yargs parser tgz cve medium severity vulnerability vulnerable libraries yargs parser tgz yargs parser tgz yargs parser tgz the mighty option parser used by yargs library home page a href path to dependency file fico xpress vdlx datagrid package json path to vulnerable library fico xpress vdlx datagrid node modules yargs parser package json dependency hierarchy bestzip tgz root library yargs tgz x yargs parser tgz vulnerable library yargs parser tgz the mighty option parser used by yargs library home page a href path to dependency file fico xpress vdlx datagrid package json path to vulnerable library fico xpress vdlx datagrid node modules purgecss node modules yargs parser package json dependency hierarchy parcel bundler tgz root library htmlnano tgz purgecss tgz yargs tgz x yargs parser tgz vulnerable library found in head commit a href found in base branch master vulnerability details yargs parser could be tricked into adding or modifying properties of object prototype using a proto payload publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact low integrity impact low availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree bestzip yargs yargs parser isminimumfixversionavailable true minimumfixversion packagetype javascript node js packagename yargs parser packageversion packagefilepaths istransitivedependency true dependencytree parcel bundler htmlnano purgecss yargs yargs parser isminimumfixversionavailable true minimumfixversion basebranches vulnerabilityidentifier cve vulnerabilitydetails yargs parser could be tricked into adding or modifying properties of object prototype using a proto payload vulnerabilityurl
| 0
|
611,079
| 18,944,308,601
|
IssuesEvent
|
2021-11-18 08:29:00
|
DISSINET/InkVisitor
|
https://api.github.com/repos/DISSINET/InkVisitor
|
opened
|
Detail: Language -> Label language
|
priority
|
The label "Language" of the in-entity property confuses users if the entity is Text: they think it describes the language of the Text, while it describes the language of the _label_. Please relabel to "Label language". If absolutely necessary for lack of space, you can abbreviate to "Label lang.".
|
1.0
|
Detail: Language -> Label language - The label "Language" of the in-entity property confuses users if the entity is Text: they think it describes the language of the Text, while it describes the language of the _label_. Please relabel to "Label language". If absolutely necessary for lack of space, you can abbreviate to "Label lang.".
|
non_test
|
detail language label language the label language of the in entity property confuses users if the entity is text they think it describes the language of the text while it describes the language of the label please relabel to label language if absolutely necessary for lack of space you can abbreviate to label lang
| 0
|
140,875
| 11,372,092,127
|
IssuesEvent
|
2020-01-28 00:35:33
|
brave/brave-browser
|
https://api.github.com/repos/brave/brave-browser
|
opened
|
text update needed on Dashboard Settings
|
QA/Test-Plan-Specified QA/Yes feature/new-tab release-notes/exclude
|
<!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue.
PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE.
INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED-->
## Description
Per the spec for SNTP, `Show Background Image` should be updated to `Show Background Images`.
## Steps to Reproduce
<!--Please add a series of steps to reproduce the issue-->
1. Clean profile
2. Enable SNTP from flags, relaunch
3. Open Dashboard Settings on NTP
## Actual result:
<img width="435" alt="Screen Shot 2020-01-27 at 7 32 55 PM" src="https://user-images.githubusercontent.com/28145373/73225841-01aa4280-413c-11ea-9c2d-f20498cc0369.png">
## Expected result:
Should say `Show Background Images`
## Reproduces how often:
<!--[Easily reproduced/Intermittent issue/No steps to reproduce]-->
easily
## Brave version (brave://version info)
<!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details-->
Brave | 1.5.62 Chromium: 79.0.3945.130 (Official Build) nightly (64-bit)
-- | --
Revision | e22de67c28798d98833a7137c0e22876237fc40a-refs/branch-heads/3945@{#1047}
OS | macOS Version 10.14.6 (Build 18G103)
## Version/Channel Information:
<!--Does this issue happen on any other channels? Or is it specific to a certain channel?-->
- Can you reproduce this issue with the current release?
- Can you reproduce this issue with the beta channel?
- Can you reproduce this issue with the dev channel?
- Can you reproduce this issue with the nightly channel? yes
## Other Additional Information:
- Does the issue resolve itself when disabling Brave Shields?
- Does the issue resolve itself when disabling Brave Rewards?
- Is the issue reproducible on the latest version of Chrome?
## Miscellaneous Information:
cc @brave/legacy_qa @rebron @petemill
|
1.0
|
text update needed on Dashboard Settings - <!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue.
PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE.
INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED-->
## Description
Per the spec for SNTP, `Show Background Image` should be updated to `Show Background Images`.
## Steps to Reproduce
<!--Please add a series of steps to reproduce the issue-->
1. Clean profile
2. Enable SNTP from flags, relaunch
3. Open Dashboard Settings on NTP
## Actual result:
<img width="435" alt="Screen Shot 2020-01-27 at 7 32 55 PM" src="https://user-images.githubusercontent.com/28145373/73225841-01aa4280-413c-11ea-9c2d-f20498cc0369.png">
## Expected result:
Should say `Show Background Images`
## Reproduces how often:
<!--[Easily reproduced/Intermittent issue/No steps to reproduce]-->
easily
## Brave version (brave://version info)
<!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details-->
Brave | 1.5.62 Chromium: 79.0.3945.130 (Official Build) nightly (64-bit)
-- | --
Revision | e22de67c28798d98833a7137c0e22876237fc40a-refs/branch-heads/3945@{#1047}
OS | macOS Version 10.14.6 (Build 18G103)
## Version/Channel Information:
<!--Does this issue happen on any other channels? Or is it specific to a certain channel?-->
- Can you reproduce this issue with the current release?
- Can you reproduce this issue with the beta channel?
- Can you reproduce this issue with the dev channel?
- Can you reproduce this issue with the nightly channel? yes
## Other Additional Information:
- Does the issue resolve itself when disabling Brave Shields?
- Does the issue resolve itself when disabling Brave Rewards?
- Is the issue reproducible on the latest version of Chrome?
## Miscellaneous Information:
cc @brave/legacy_qa @rebron @petemill
|
test
|
text update needed on dashboard settings have you searched for similar issues before submitting this issue please check the open issues and add a note before logging a new issue please use the template below to provide information about the issue insufficient info will get the issue closed it will only be reopened after sufficient info is provided description per the spec for sntp show background image should be updated to show background images steps to reproduce clean profile enable sntp from flags relaunch open dashboard settings on ntp actual result img width alt screen shot at pm src expected result should say show background images reproduces how often easily brave version brave version info brave chromium official build nightly bit revision refs branch heads os macos version build version channel information can you reproduce this issue with the current release can you reproduce this issue with the beta channel can you reproduce this issue with the dev channel can you reproduce this issue with the nightly channel yes other additional information does the issue resolve itself when disabling brave shields does the issue resolve itself when disabling brave rewards is the issue reproducible on the latest version of chrome miscellaneous information cc brave legacy qa rebron petemill
| 1
|
117,222
| 9,916,384,594
|
IssuesEvent
|
2019-06-28 19:46:22
|
dojot/dojot
|
https://api.github.com/repos/dojot/dojot
|
closed
|
Remove firmware images without any confirmation
|
Priority:Medium Status:ToTest Team:Frontend Type:Bug
|
You can remove firmware images associated with a template without any confirmation. This behavior differs how other elements are removed in the GUI.
|
1.0
|
Remove firmware images without any confirmation - You can remove firmware images associated with a template without any confirmation. This behavior differs how other elements are removed in the GUI.
|
test
|
remove firmware images without any confirmation you can remove firmware images associated with a template without any confirmation this behavior differs how other elements are removed in the gui
| 1
|
76,682
| 7,543,200,515
|
IssuesEvent
|
2018-04-17 14:55:49
|
ODM2/ODM2DataSharingPortal
|
https://api.github.com/repos/ODM2/ODM2DataSharingPortal
|
closed
|
Restyle Site: Restyle the My Sites Page
|
enhancement in progress ready for testing tested
|
This page will largely stay the same, but needs to be restyled to take on the WikiWatershed styling. I've showed the registered and followed sites below in tables, but for now you can keep the tiles you have if you want.
Since we will potentially be having both EnviroDIY and Leaf Pack Network data on the same site, we will have to remove the Latest Measurement from the tile if you choose to keep the tiles because not all sites will have sensor data. If you keep the tiles you have now for each of the sites, I also suggest making the names of the sites in the green box at the top smaller so you can fit more of them on a page.
This will replace the My Sites page of http://data.envirodiy.org
|
2.0
|
Restyle Site: Restyle the My Sites Page - This page will largely stay the same, but needs to be restyled to take on the WikiWatershed styling. I've showed the registered and followed sites below in tables, but for now you can keep the tiles you have if you want.
Since we will potentially be having both EnviroDIY and Leaf Pack Network data on the same site, we will have to remove the Latest Measurement from the tile if you choose to keep the tiles because not all sites will have sensor data. If you keep the tiles you have now for each of the sites, I also suggest making the names of the sites in the green box at the top smaller so you can fit more of them on a page.
This will replace the My Sites page of http://data.envirodiy.org
|
test
|
restyle site restyle the my sites page this page will largely stay the same but needs to be restyled to take on the wikiwatershed styling i ve showed the registered and followed sites below in tables but for now you can keep the tiles you have if you want since we will potentially be having both envirodiy and leaf pack network data on the same site we will have to remove the latest measurement from the tile if you choose to keep the tiles because not all sites will have sensor data if you keep the tiles you have now for each of the sites i also suggest making the names of the sites in the green box at the top smaller so you can fit more of them on a page this will replace the my sites page of
| 1
|
107,449
| 11,544,397,222
|
IssuesEvent
|
2020-02-18 11:23:20
|
HQ20/contracts
|
https://api.github.com/repos/HQ20/contracts
|
closed
|
Update main README.md with new modules
|
documentation
|
I think the main README.md folder scheme needs to be updated according to the changelog.
|
1.0
|
Update main README.md with new modules - I think the main README.md folder scheme needs to be updated according to the changelog.
|
non_test
|
update main readme md with new modules i think the main readme md folder scheme needs to be updated according to the changelog
| 0
|
41,807
| 5,379,484,465
|
IssuesEvent
|
2017-02-23 17:16:22
|
elegantthemes/Divi-Beta
|
https://api.github.com/repos/elegantthemes/Divi-Beta
|
closed
|
Uncaught TypeError: $et_pb_ab_goal.visible is not a function
|
!IMPORTANT BUG DESIGN SIGNOFF QUALITY ASSURED READY FOR REVIEW
|
### Problem:
### Steps To Reproduce:
1. Edit an existing page using the VB.
2. Open the BB and set up a split test.
3. Switch to VB and check console.
## Attached PR
- https://github.com/elegantthemes/submodule-builder/pull/1755
|
1.0
|
Uncaught TypeError: $et_pb_ab_goal.visible is not a function - ### Problem:
### Steps To Reproduce:
1. Edit an existing page using the VB.
2. Open the BB and set up a split test.
3. Switch to VB and check console.
## Attached PR
- https://github.com/elegantthemes/submodule-builder/pull/1755
|
non_test
|
uncaught typeerror et pb ab goal visible is not a function problem steps to reproduce edit an existing page using the vb open the bb and set up a split test switch to vb and check console attached pr
| 0
|
443,382
| 30,887,317,294
|
IssuesEvent
|
2023-08-03 23:38:23
|
bluementat/PingPongTracker
|
https://api.github.com/repos/bluementat/PingPongTracker
|
opened
|
Update README.dm - Remove default notes and entries
|
documentation
|
- [ ] Get a new logo
- [ ] Create a new "Built With" Icon for .NET
- [ ] Installation section of the README
- [ ] Contact Information
- [ ] Acknowledgements
|
1.0
|
Update README.dm - Remove default notes and entries -
- [ ] Get a new logo
- [ ] Create a new "Built With" Icon for .NET
- [ ] Installation section of the README
- [ ] Contact Information
- [ ] Acknowledgements
|
non_test
|
update readme dm remove default notes and entries get a new logo create a new built with icon for net installation section of the readme contact information acknowledgements
| 0
|
72,600
| 7,302,654,998
|
IssuesEvent
|
2018-02-27 10:24:03
|
cockroachdb/cockroach
|
https://api.github.com/repos/cockroachdb/cockroach
|
closed
|
teamcity: failed tests on release-2.0: acceptance/TestVersionUpgrade, acceptance/TestVersionUpgrade: TestVersionUpgrade/runMode=local, acceptance/TestVersionUpgrade, acceptance/TestVersionUpgrade: TestVersionUpgrade/runMode=local
|
Robot test-failure
|
The following tests appear to have failed:
[#537295](https://teamcity.cockroachdb.com/viewLog.html?buildId=537295):
```
--- FAIL: acceptance/TestVersionUpgrade (31.260s)
test_log_scope.go:81: test logs captured to: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/logTestVersionUpgrade933103484
test_log_scope.go:62: use -show-logs to present logs inline
--- FAIL: acceptance/TestVersionUpgrade: TestVersionUpgrade/runMode=local (31.260s)
version_upgrade_test.go:179: binary=v1.1.0
version_upgrade_test.go:179: cluster=1.0
version_upgrade_test.go:179: cluster=1.0-3
version_upgrade_test.go:179: binary=v1.1.1
version_upgrade_test.go:179: cluster=1.1
version_upgrade_test.go:179: binary=source
<autogenerated>:1: dial tcp 127.0.0.1:33243: getsockopt: connection refused
------- Stdout: -------
CockroachDB node starting at 2018-02-26 22:18:17.350119009 +0000 UTC
build: CCL v1.0.6 @ 2017/09/14 15:15:48 (go1.8.3)
admin: http://127.0.0.1:37873
sql: postgresql://root@127.0.0.1:37597?sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/1
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/1
status: initialized new cluster
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 1
CockroachDB node starting at 2018-02-26 22:18:17.719905246 +0000 UTC
build: CCL v1.0.6 @ 2017/09/14 15:15:48 (go1.8.3)
admin: http://127.0.0.1:35189
sql: postgresql://root@127.0.0.1:43741?sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/3
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/3
status: initialized new node, joined pre-existing cluster
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 2
CockroachDB node starting at 2018-02-26 22:18:17.726668561 +0000 UTC
build: CCL v1.0.6 @ 2017/09/14 15:15:48 (go1.8.3)
admin: http://127.0.0.1:45069
sql: postgresql://root@127.0.0.1:46723?sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/2
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/2
status: initialized new node, joined pre-existing cluster
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 3
CockroachDB node starting at 2018-02-26 22:18:24.993122797 +0000 UTC (took 5.4s)
build: CCL v1.1.0 @ 2017/10/12 14:50:18 (go1.8.3)
admin: http://127.0.0.1:37221
sql: postgresql://root@127.0.0.1:33783?application_name=cockroach&sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/1
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/1
status: restarted pre-existing node
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 1
CockroachDB node starting at 2018-02-26 22:18:26.845366994 +0000 UTC (took 0.6s)
build: CCL v1.1.0 @ 2017/10/12 14:50:18 (go1.8.3)
admin: http://127.0.0.1:37821
sql: postgresql://root@127.0.0.1:45945?application_name=cockroach&sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/2
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/2
status: restarted pre-existing node
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 3
CockroachDB node starting at 2018-02-26 22:18:28.826451577 +0000 UTC (took 0.6s)
build: CCL v1.1.0 @ 2017/10/12 14:50:18 (go1.8.3)
admin: http://127.0.0.1:36043
sql: postgresql://root@127.0.0.1:33793?application_name=cockroach&sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/3
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/3
status: restarted pre-existing node
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 2
CockroachDB node starting at 2018-02-26 22:18:39.209033895 +0000 UTC (took 6.3s)
build: CCL v1.1.1 @ 2017/10/19 15:31:46 (go1.8.3)
admin: http://127.0.0.1:43913
sql: postgresql://root@127.0.0.1:33243?application_name=cockroach&sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/1
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/1
status: restarted pre-existing node
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 1
CockroachDB node starting at 2018-02-26 22:18:41.031536271 +0000 UTC (took 0.6s)
build: CCL v1.1.1 @ 2017/10/19 15:31:46 (go1.8.3)
admin: http://127.0.0.1:42353
sql: postgresql://root@127.0.0.1:39039?application_name=cockroach&sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/2
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/2
status: restarted pre-existing node
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 3
CockroachDB node starting at 2018-02-26 22:18:42.978773975 +0000 UTC (took 0.6s)
build: CCL v1.1.1 @ 2017/10/19 15:31:46 (go1.8.3)
admin: http://127.0.0.1:36443
sql: postgresql://root@127.0.0.1:36029?application_name=cockroach&sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/3
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/3
status: restarted pre-existing node
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 2
test logs left over in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/logTestVersionUpgrade933103484
--- FAIL: acceptance/TestVersionUpgrade (31.260s)
test_log_scope.go:81: test logs captured to: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/logTestVersionUpgrade933103484
test_log_scope.go:62: use -show-logs to present logs inline
--- FAIL: acceptance/TestVersionUpgrade: TestVersionUpgrade/runMode=local (31.260s)
version_upgrade_test.go:179: binary=v1.1.0
version_upgrade_test.go:179: cluster=1.0
version_upgrade_test.go:179: cluster=1.0-3
version_upgrade_test.go:179: binary=v1.1.1
version_upgrade_test.go:179: cluster=1.1
version_upgrade_test.go:179: binary=source
<autogenerated>:1: dial tcp 127.0.0.1:33243: getsockopt: connection refused
------- Stdout: -------
CockroachDB node starting at 2018-02-26 22:18:17.350119009 +0000 UTC
build: CCL v1.0.6 @ 2017/09/14 15:15:48 (go1.8.3)
admin: http://127.0.0.1:37873
sql: postgresql://root@127.0.0.1:37597?sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/1
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/1
status: initialized new cluster
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 1
CockroachDB node starting at 2018-02-26 22:18:17.719905246 +0000 UTC
build: CCL v1.0.6 @ 2017/09/14 15:15:48 (go1.8.3)
admin: http://127.0.0.1:35189
sql: postgresql://root@127.0.0.1:43741?sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/3
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/3
status: initialized new node, joined pre-existing cluster
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 2
CockroachDB node starting at 2018-02-26 22:18:17.726668561 +0000 UTC
build: CCL v1.0.6 @ 2017/09/14 15:15:48 (go1.8.3)
admin: http://127.0.0.1:45069
sql: postgresql://root@127.0.0.1:46723?sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/2
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/2
status: initialized new node, joined pre-existing cluster
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 3
CockroachDB node starting at 2018-02-26 22:18:24.993122797 +0000 UTC (took 5.4s)
build: CCL v1.1.0 @ 2017/10/12 14:50:18 (go1.8.3)
admin: http://127.0.0.1:37221
sql: postgresql://root@127.0.0.1:33783?application_name=cockroach&sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/1
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/1
status: restarted pre-existing node
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 1
CockroachDB node starting at 2018-02-26 22:18:26.845366994 +0000 UTC (took 0.6s)
build: CCL v1.1.0 @ 2017/10/12 14:50:18 (go1.8.3)
admin: http://127.0.0.1:37821
sql: postgresql://root@127.0.0.1:45945?application_name=cockroach&sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/2
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/2
status: restarted pre-existing node
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 3
CockroachDB node starting at 2018-02-26 22:18:28.826451577 +0000 UTC (took 0.6s)
build: CCL v1.1.0 @ 2017/10/12 14:50:18 (go1.8.3)
admin: http://127.0.0.1:36043
sql: postgresql://root@127.0.0.1:33793?application_name=cockroach&sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/3
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/3
status: restarted pre-existing node
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 2
CockroachDB node starting at 2018-02-26 22:18:39.209033895 +0000 UTC (took 6.3s)
build: CCL v1.1.1 @ 2017/10/19 15:31:46 (go1.8.3)
admin: http://127.0.0.1:43913
sql: postgresql://root@127.0.0.1:33243?application_name=cockroach&sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/1
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/1
status: restarted pre-existing node
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 1
CockroachDB node starting at 2018-02-26 22:18:41.031536271 +0000 UTC (took 0.6s)
build: CCL v1.1.1 @ 2017/10/19 15:31:46 (go1.8.3)
admin: http://127.0.0.1:42353
sql: postgresql://root@127.0.0.1:39039?application_name=cockroach&sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/2
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/2
status: restarted pre-existing node
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 3
CockroachDB node starting at 2018-02-26 22:18:42.978773975 +0000 UTC (took 0.6s)
build: CCL v1.1.1 @ 2017/10/19 15:31:46 (go1.8.3)
admin: http://127.0.0.1:36443
sql: postgresql://root@127.0.0.1:36029?application_name=cockroach&sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/3
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/3
status: restarted pre-existing node
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 2
test logs left over in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/logTestVersionUpgrade933103484
```
Please assign, take a look and update the issue accordingly.
|
1.0
|
teamcity: failed tests on release-2.0: acceptance/TestVersionUpgrade, acceptance/TestVersionUpgrade: TestVersionUpgrade/runMode=local, acceptance/TestVersionUpgrade, acceptance/TestVersionUpgrade: TestVersionUpgrade/runMode=local - The following tests appear to have failed:
[#537295](https://teamcity.cockroachdb.com/viewLog.html?buildId=537295):
```
--- FAIL: acceptance/TestVersionUpgrade (31.260s)
test_log_scope.go:81: test logs captured to: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/logTestVersionUpgrade933103484
test_log_scope.go:62: use -show-logs to present logs inline
--- FAIL: acceptance/TestVersionUpgrade: TestVersionUpgrade/runMode=local (31.260s)
version_upgrade_test.go:179: binary=v1.1.0
version_upgrade_test.go:179: cluster=1.0
version_upgrade_test.go:179: cluster=1.0-3
version_upgrade_test.go:179: binary=v1.1.1
version_upgrade_test.go:179: cluster=1.1
version_upgrade_test.go:179: binary=source
<autogenerated>:1: dial tcp 127.0.0.1:33243: getsockopt: connection refused
------- Stdout: -------
CockroachDB node starting at 2018-02-26 22:18:17.350119009 +0000 UTC
build: CCL v1.0.6 @ 2017/09/14 15:15:48 (go1.8.3)
admin: http://127.0.0.1:37873
sql: postgresql://root@127.0.0.1:37597?sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/1
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/1
status: initialized new cluster
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 1
CockroachDB node starting at 2018-02-26 22:18:17.719905246 +0000 UTC
build: CCL v1.0.6 @ 2017/09/14 15:15:48 (go1.8.3)
admin: http://127.0.0.1:35189
sql: postgresql://root@127.0.0.1:43741?sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/3
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/3
status: initialized new node, joined pre-existing cluster
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 2
CockroachDB node starting at 2018-02-26 22:18:17.726668561 +0000 UTC
build: CCL v1.0.6 @ 2017/09/14 15:15:48 (go1.8.3)
admin: http://127.0.0.1:45069
sql: postgresql://root@127.0.0.1:46723?sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/2
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/2
status: initialized new node, joined pre-existing cluster
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 3
CockroachDB node starting at 2018-02-26 22:18:24.993122797 +0000 UTC (took 5.4s)
build: CCL v1.1.0 @ 2017/10/12 14:50:18 (go1.8.3)
admin: http://127.0.0.1:37221
sql: postgresql://root@127.0.0.1:33783?application_name=cockroach&sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/1
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/1
status: restarted pre-existing node
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 1
CockroachDB node starting at 2018-02-26 22:18:26.845366994 +0000 UTC (took 0.6s)
build: CCL v1.1.0 @ 2017/10/12 14:50:18 (go1.8.3)
admin: http://127.0.0.1:37821
sql: postgresql://root@127.0.0.1:45945?application_name=cockroach&sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/2
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/2
status: restarted pre-existing node
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 3
CockroachDB node starting at 2018-02-26 22:18:28.826451577 +0000 UTC (took 0.6s)
build: CCL v1.1.0 @ 2017/10/12 14:50:18 (go1.8.3)
admin: http://127.0.0.1:36043
sql: postgresql://root@127.0.0.1:33793?application_name=cockroach&sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/3
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/3
status: restarted pre-existing node
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 2
CockroachDB node starting at 2018-02-26 22:18:39.209033895 +0000 UTC (took 6.3s)
build: CCL v1.1.1 @ 2017/10/19 15:31:46 (go1.8.3)
admin: http://127.0.0.1:43913
sql: postgresql://root@127.0.0.1:33243?application_name=cockroach&sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/1
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/1
status: restarted pre-existing node
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 1
CockroachDB node starting at 2018-02-26 22:18:41.031536271 +0000 UTC (took 0.6s)
build: CCL v1.1.1 @ 2017/10/19 15:31:46 (go1.8.3)
admin: http://127.0.0.1:42353
sql: postgresql://root@127.0.0.1:39039?application_name=cockroach&sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/2
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/2
status: restarted pre-existing node
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 3
CockroachDB node starting at 2018-02-26 22:18:42.978773975 +0000 UTC (took 0.6s)
build: CCL v1.1.1 @ 2017/10/19 15:31:46 (go1.8.3)
admin: http://127.0.0.1:36443
sql: postgresql://root@127.0.0.1:36029?application_name=cockroach&sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/3
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/3
status: restarted pre-existing node
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 2
test logs left over in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/logTestVersionUpgrade933103484
--- FAIL: acceptance/TestVersionUpgrade (31.260s)
test_log_scope.go:81: test logs captured to: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/logTestVersionUpgrade933103484
test_log_scope.go:62: use -show-logs to present logs inline
--- FAIL: acceptance/TestVersionUpgrade: TestVersionUpgrade/runMode=local (31.260s)
version_upgrade_test.go:179: binary=v1.1.0
version_upgrade_test.go:179: cluster=1.0
version_upgrade_test.go:179: cluster=1.0-3
version_upgrade_test.go:179: binary=v1.1.1
version_upgrade_test.go:179: cluster=1.1
version_upgrade_test.go:179: binary=source
<autogenerated>:1: dial tcp 127.0.0.1:33243: getsockopt: connection refused
------- Stdout: -------
CockroachDB node starting at 2018-02-26 22:18:17.350119009 +0000 UTC
build: CCL v1.0.6 @ 2017/09/14 15:15:48 (go1.8.3)
admin: http://127.0.0.1:37873
sql: postgresql://root@127.0.0.1:37597?sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/1
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/1
status: initialized new cluster
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 1
CockroachDB node starting at 2018-02-26 22:18:17.719905246 +0000 UTC
build: CCL v1.0.6 @ 2017/09/14 15:15:48 (go1.8.3)
admin: http://127.0.0.1:35189
sql: postgresql://root@127.0.0.1:43741?sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/3
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/3
status: initialized new node, joined pre-existing cluster
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 2
CockroachDB node starting at 2018-02-26 22:18:17.726668561 +0000 UTC
build: CCL v1.0.6 @ 2017/09/14 15:15:48 (go1.8.3)
admin: http://127.0.0.1:45069
sql: postgresql://root@127.0.0.1:46723?sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/2
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/2
status: initialized new node, joined pre-existing cluster
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 3
CockroachDB node starting at 2018-02-26 22:18:24.993122797 +0000 UTC (took 5.4s)
build: CCL v1.1.0 @ 2017/10/12 14:50:18 (go1.8.3)
admin: http://127.0.0.1:37221
sql: postgresql://root@127.0.0.1:33783?application_name=cockroach&sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/1
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/1
status: restarted pre-existing node
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 1
CockroachDB node starting at 2018-02-26 22:18:26.845366994 +0000 UTC (took 0.6s)
build: CCL v1.1.0 @ 2017/10/12 14:50:18 (go1.8.3)
admin: http://127.0.0.1:37821
sql: postgresql://root@127.0.0.1:45945?application_name=cockroach&sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/2
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/2
status: restarted pre-existing node
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 3
CockroachDB node starting at 2018-02-26 22:18:28.826451577 +0000 UTC (took 0.6s)
build: CCL v1.1.0 @ 2017/10/12 14:50:18 (go1.8.3)
admin: http://127.0.0.1:36043
sql: postgresql://root@127.0.0.1:33793?application_name=cockroach&sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/3
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/3
status: restarted pre-existing node
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 2
CockroachDB node starting at 2018-02-26 22:18:39.209033895 +0000 UTC (took 6.3s)
build: CCL v1.1.1 @ 2017/10/19 15:31:46 (go1.8.3)
admin: http://127.0.0.1:43913
sql: postgresql://root@127.0.0.1:33243?application_name=cockroach&sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/1
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/1
status: restarted pre-existing node
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 1
CockroachDB node starting at 2018-02-26 22:18:41.031536271 +0000 UTC (took 0.6s)
build: CCL v1.1.1 @ 2017/10/19 15:31:46 (go1.8.3)
admin: http://127.0.0.1:42353
sql: postgresql://root@127.0.0.1:39039?application_name=cockroach&sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/2
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/2
status: restarted pre-existing node
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 3
CockroachDB node starting at 2018-02-26 22:18:42.978773975 +0000 UTC (took 0.6s)
build: CCL v1.1.1 @ 2017/10/19 15:31:46 (go1.8.3)
admin: http://127.0.0.1:36443
sql: postgresql://root@127.0.0.1:36029?application_name=cockroach&sslmode=disable
logs: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/TestVersionUpgrade/runMode=local/3
store[0]: path=/home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/acceptance/.localcluster160793259/3
status: restarted pre-existing node
clusterID: 5b091fb5-a065-4898-96a4-3fceff9492e3
nodeID: 2
test logs left over in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/acceptance/logTestVersionUpgrade933103484
```
Please assign, take a look and update the issue accordingly.
|
test
|
teamcity failed tests on release acceptance testversionupgrade acceptance testversionupgrade testversionupgrade runmode local acceptance testversionupgrade acceptance testversionupgrade testversionupgrade runmode local the following tests appear to have failed fail acceptance testversionupgrade test log scope go test logs captured to home agent work go src github com cockroachdb cockroach artifacts acceptance test log scope go use show logs to present logs inline fail acceptance testversionupgrade testversionupgrade runmode local version upgrade test go binary version upgrade test go cluster version upgrade test go cluster version upgrade test go binary version upgrade test go cluster version upgrade test go binary source dial tcp getsockopt connection refused stdout cockroachdb node starting at utc build ccl admin sql postgresql root sslmode disable logs home agent work go src github com cockroachdb cockroach artifacts acceptance testversionupgrade runmode local store path home agent work go src github com cockroachdb cockroach pkg acceptance status initialized new cluster clusterid nodeid cockroachdb node starting at utc build ccl admin sql postgresql root sslmode disable logs home agent work go src github com cockroachdb cockroach artifacts acceptance testversionupgrade runmode local store path home agent work go src github com cockroachdb cockroach pkg acceptance status initialized new node joined pre existing cluster clusterid nodeid cockroachdb node starting at utc build ccl admin sql postgresql root sslmode disable logs home agent work go src github com cockroachdb cockroach artifacts acceptance testversionupgrade runmode local store path home agent work go src github com cockroachdb cockroach pkg acceptance status initialized new node joined pre existing cluster clusterid nodeid cockroachdb node starting at utc took build ccl admin sql postgresql root application name cockroach sslmode disable logs home agent work go src github com cockroachdb cockroach artifacts acceptance testversionupgrade runmode local store path home agent work go src github com cockroachdb cockroach pkg acceptance status restarted pre existing node clusterid nodeid cockroachdb node starting at utc took build ccl admin sql postgresql root application name cockroach sslmode disable logs home agent work go src github com cockroachdb cockroach artifacts acceptance testversionupgrade runmode local store path home agent work go src github com cockroachdb cockroach pkg acceptance status restarted pre existing node clusterid nodeid cockroachdb node starting at utc took build ccl admin sql postgresql root application name cockroach sslmode disable logs home agent work go src github com cockroachdb cockroach artifacts acceptance testversionupgrade runmode local store path home agent work go src github com cockroachdb cockroach pkg acceptance status restarted pre existing node clusterid nodeid cockroachdb node starting at utc took build ccl admin sql postgresql root application name cockroach sslmode disable logs home agent work go src github com cockroachdb cockroach artifacts acceptance testversionupgrade runmode local store path home agent work go src github com cockroachdb cockroach pkg acceptance status restarted pre existing node clusterid nodeid cockroachdb node starting at utc took build ccl admin sql postgresql root application name cockroach sslmode disable logs home agent work go src github com cockroachdb cockroach artifacts acceptance testversionupgrade runmode local store path home agent work go src github com cockroachdb cockroach pkg acceptance status restarted pre existing node clusterid nodeid cockroachdb node starting at utc took build ccl admin sql postgresql root application name cockroach sslmode disable logs home agent work go src github com cockroachdb cockroach artifacts acceptance testversionupgrade runmode local store path home agent work go src github com cockroachdb cockroach pkg acceptance status restarted pre existing node clusterid nodeid test logs left over in home agent work go src github com cockroachdb cockroach artifacts acceptance fail acceptance testversionupgrade test log scope go test logs captured to home agent work go src github com cockroachdb cockroach artifacts acceptance test log scope go use show logs to present logs inline fail acceptance testversionupgrade testversionupgrade runmode local version upgrade test go binary version upgrade test go cluster version upgrade test go cluster version upgrade test go binary version upgrade test go cluster version upgrade test go binary source dial tcp getsockopt connection refused stdout cockroachdb node starting at utc build ccl admin sql postgresql root sslmode disable logs home agent work go src github com cockroachdb cockroach artifacts acceptance testversionupgrade runmode local store path home agent work go src github com cockroachdb cockroach pkg acceptance status initialized new cluster clusterid nodeid cockroachdb node starting at utc build ccl admin sql postgresql root sslmode disable logs home agent work go src github com cockroachdb cockroach artifacts acceptance testversionupgrade runmode local store path home agent work go src github com cockroachdb cockroach pkg acceptance status initialized new node joined pre existing cluster clusterid nodeid cockroachdb node starting at utc build ccl admin sql postgresql root sslmode disable logs home agent work go src github com cockroachdb cockroach artifacts acceptance testversionupgrade runmode local store path home agent work go src github com cockroachdb cockroach pkg acceptance status initialized new node joined pre existing cluster clusterid nodeid cockroachdb node starting at utc took build ccl admin sql postgresql root application name cockroach sslmode disable logs home agent work go src github com cockroachdb cockroach artifacts acceptance testversionupgrade runmode local store path home agent work go src github com cockroachdb cockroach pkg acceptance status restarted pre existing node clusterid nodeid cockroachdb node starting at utc took build ccl admin sql postgresql root application name cockroach sslmode disable logs home agent work go src github com cockroachdb cockroach artifacts acceptance testversionupgrade runmode local store path home agent work go src github com cockroachdb cockroach pkg acceptance status restarted pre existing node clusterid nodeid cockroachdb node starting at utc took build ccl admin sql postgresql root application name cockroach sslmode disable logs home agent work go src github com cockroachdb cockroach artifacts acceptance testversionupgrade runmode local store path home agent work go src github com cockroachdb cockroach pkg acceptance status restarted pre existing node clusterid nodeid cockroachdb node starting at utc took build ccl admin sql postgresql root application name cockroach sslmode disable logs home agent work go src github com cockroachdb cockroach artifacts acceptance testversionupgrade runmode local store path home agent work go src github com cockroachdb cockroach pkg acceptance status restarted pre existing node clusterid nodeid cockroachdb node starting at utc took build ccl admin sql postgresql root application name cockroach sslmode disable logs home agent work go src github com cockroachdb cockroach artifacts acceptance testversionupgrade runmode local store path home agent work go src github com cockroachdb cockroach pkg acceptance status restarted pre existing node clusterid nodeid cockroachdb node starting at utc took build ccl admin sql postgresql root application name cockroach sslmode disable logs home agent work go src github com cockroachdb cockroach artifacts acceptance testversionupgrade runmode local store path home agent work go src github com cockroachdb cockroach pkg acceptance status restarted pre existing node clusterid nodeid test logs left over in home agent work go src github com cockroachdb cockroach artifacts acceptance please assign take a look and update the issue accordingly
| 1
|
4,910
| 2,755,386,823
|
IssuesEvent
|
2015-04-26 16:09:03
|
BugBuster1701/banner
|
https://api.github.com/repos/BugBuster1701/banner
|
closed
|
[Insight] Boolean should be compared strictly - in classes/BannerStatisticsHelper.php, line 75
|
Insight Test is running
|
**[in classes/BannerStatisticsHelper.php, line 75](https://github.com/BugBuster1701/banner/blob/50c7a9adb3cff1a591f403f8a67a5333a1f43c52/classes/BannerStatisticsHelper.php#L75)**
> With booleans, only strict comparison (with `===` operator) should be used to lower bug risks and to improve performances.
```php
* Return the current object instance (Singleton)
* @return BannerStatisticsHelper
*/
public static function getInstance()
{
if (self::$instance == null)
{
self::$instance = new BannerStatisticsHelper();
}
return self::$instance;
```
---------------------
_Posted from [SensioLabsInsight](https://insight.sensiolabs.com/projects/288d9e0d-3710-438a-b8b1-ecfcc697ea86/analyses/2?status=violations)_
|
1.0
|
[Insight] Boolean should be compared strictly - in classes/BannerStatisticsHelper.php, line 75 - **[in classes/BannerStatisticsHelper.php, line 75](https://github.com/BugBuster1701/banner/blob/50c7a9adb3cff1a591f403f8a67a5333a1f43c52/classes/BannerStatisticsHelper.php#L75)**
> With booleans, only strict comparison (with `===` operator) should be used to lower bug risks and to improve performances.
```php
* Return the current object instance (Singleton)
* @return BannerStatisticsHelper
*/
public static function getInstance()
{
if (self::$instance == null)
{
self::$instance = new BannerStatisticsHelper();
}
return self::$instance;
```
---------------------
_Posted from [SensioLabsInsight](https://insight.sensiolabs.com/projects/288d9e0d-3710-438a-b8b1-ecfcc697ea86/analyses/2?status=violations)_
|
test
|
boolean should be compared strictly in classes bannerstatisticshelper php line with booleans only strict comparison with operator should be used to lower bug risks and to improve performances php return the current object instance singleton return bannerstatisticshelper public static function getinstance if self instance null self instance new bannerstatisticshelper return self instance posted from
| 1
|
336,873
| 30,225,471,558
|
IssuesEvent
|
2023-07-05 23:50:00
|
unifyai/ivy
|
https://api.github.com/repos/unifyai/ivy
|
closed
|
Examine `test_utilities` tests
|
PyTorch Frontend Testing Test Sweep ToDo_internal
|
Ensure a comprehensive examination of all tests to confirm their alignment with the current test writing policy. Ensure the tests follow the following guidelines, among others:
1. Avoid restricting the use of `get_dtypes` to specific kinds (`float`, `int`) unless absolutely necessary; the default value should be used when possible.
2. Avoid the use of `assume` to bypass specific data types.
3. Unless necessary, avoid restricting the generation of numbers with `min_value` or `max_value`. For example, it is acceptable to set a maximum value for the `pad` function if the `pad_value` value can halt the test.
4. Ensure proper use of strategies.
5. Verify that all tests are executed rather than skipped by `test_values=False`, unless the test logic is implemented within the test body itself.
6. Confirm that testing is comprehensive and complete, meaning that all possible combinations of inputs are tested.
7. Avoid manually setting test parameters, including native array flags, container flags, the number of positional arguments, etc.
8. Ensure that no parameters are skipped during testing.
> Always refer to the documentation for **Ivy Tests** and **Ivy Frontend Tests** for complete test writing policy.
If a test function does not require update, simply mark the function in the list as completed, otherwise create an issue for that test function.
- [x] test_torch_result_type
- [ ] #15880
- [x] test_torch_utilities_bincount
|
2.0
|
Examine `test_utilities` tests - Ensure a comprehensive examination of all tests to confirm their alignment with the current test writing policy. Ensure the tests follow the following guidelines, among others:
1. Avoid restricting the use of `get_dtypes` to specific kinds (`float`, `int`) unless absolutely necessary; the default value should be used when possible.
2. Avoid the use of `assume` to bypass specific data types.
3. Unless necessary, avoid restricting the generation of numbers with `min_value` or `max_value`. For example, it is acceptable to set a maximum value for the `pad` function if the `pad_value` value can halt the test.
4. Ensure proper use of strategies.
5. Verify that all tests are executed rather than skipped by `test_values=False`, unless the test logic is implemented within the test body itself.
6. Confirm that testing is comprehensive and complete, meaning that all possible combinations of inputs are tested.
7. Avoid manually setting test parameters, including native array flags, container flags, the number of positional arguments, etc.
8. Ensure that no parameters are skipped during testing.
> Always refer to the documentation for **Ivy Tests** and **Ivy Frontend Tests** for complete test writing policy.
If a test function does not require update, simply mark the function in the list as completed, otherwise create an issue for that test function.
- [x] test_torch_result_type
- [ ] #15880
- [x] test_torch_utilities_bincount
|
test
|
examine test utilities tests ensure a comprehensive examination of all tests to confirm their alignment with the current test writing policy ensure the tests follow the following guidelines among others avoid restricting the use of get dtypes to specific kinds float int unless absolutely necessary the default value should be used when possible avoid the use of assume to bypass specific data types unless necessary avoid restricting the generation of numbers with min value or max value for example it is acceptable to set a maximum value for the pad function if the pad value value can halt the test ensure proper use of strategies verify that all tests are executed rather than skipped by test values false unless the test logic is implemented within the test body itself confirm that testing is comprehensive and complete meaning that all possible combinations of inputs are tested avoid manually setting test parameters including native array flags container flags the number of positional arguments etc ensure that no parameters are skipped during testing always refer to the documentation for ivy tests and ivy frontend tests for complete test writing policy if a test function does not require update simply mark the function in the list as completed otherwise create an issue for that test function test torch result type test torch utilities bincount
| 1
|
82,253
| 3,604,653,523
|
IssuesEvent
|
2016-02-03 23:50:21
|
kubernetes/kubernetes
|
https://api.github.com/repos/kubernetes/kubernetes
|
opened
|
Umbrella issue for kubectl config command overhaul
|
component/kubectl help-wanted priority/P2 team/ux
|
`kubectl config` strongly departs from the command and output conventions of other commands. It shouldn't.
Current commands:
https://github.com/kubernetes/kubernetes/blob/master/docs/user-guide/kubectl/kubectl_config.md
Conventions:
https://github.com/kubernetes/kubernetes/blob/master/docs/devel/kubectl-conventions.md
Related: #5592, #7804, #8593, #8817, #9298, #10516, #10626, #10693, #10735, #11233, #16085, #16935, #20374
TODO: Create proposal
cc @jlowdermilk @deads2k @thockin @quinton-hoole @kubernetes/kubectl
|
1.0
|
Umbrella issue for kubectl config command overhaul - `kubectl config` strongly departs from the command and output conventions of other commands. It shouldn't.
Current commands:
https://github.com/kubernetes/kubernetes/blob/master/docs/user-guide/kubectl/kubectl_config.md
Conventions:
https://github.com/kubernetes/kubernetes/blob/master/docs/devel/kubectl-conventions.md
Related: #5592, #7804, #8593, #8817, #9298, #10516, #10626, #10693, #10735, #11233, #16085, #16935, #20374
TODO: Create proposal
cc @jlowdermilk @deads2k @thockin @quinton-hoole @kubernetes/kubectl
|
non_test
|
umbrella issue for kubectl config command overhaul kubectl config strongly departs from the command and output conventions of other commands it shouldn t current commands conventions related todo create proposal cc jlowdermilk thockin quinton hoole kubernetes kubectl
| 0
|
412,941
| 12,058,509,296
|
IssuesEvent
|
2020-04-15 17:35:15
|
localstack/localstack
|
https://api.github.com/repos/localstack/localstack
|
closed
|
Add SNS subscription filter policy "exists" operator support
|
feature-missing priority-high
|
<!-- Love localstack? Please consider supporting our collective:
👉 https://opencollective.com/localstack/donate -->
The ["exists"](https://docs.aws.amazon.com/sns/latest/dg/sns-subscription-filter-policies.html#attribute-key-matching) operator is not supported in the SNS Filter Policy. This operator works upon attribute keys, but only attribute value based operators seem to currently work:
https://github.com/localstack/localstack/blob/950699c7b1256afc61d15dbff2a519e2db10635e/localstack/services/sns/sns_listener.py#L467-L482
Although using _FilterPolicy_ at all seems problematic at the moment too: https://github.com/localstack/localstack/issues/684#issuecomment-547978594
|
1.0
|
Add SNS subscription filter policy "exists" operator support - <!-- Love localstack? Please consider supporting our collective:
👉 https://opencollective.com/localstack/donate -->
The ["exists"](https://docs.aws.amazon.com/sns/latest/dg/sns-subscription-filter-policies.html#attribute-key-matching) operator is not supported in the SNS Filter Policy. This operator works upon attribute keys, but only attribute value based operators seem to currently work:
https://github.com/localstack/localstack/blob/950699c7b1256afc61d15dbff2a519e2db10635e/localstack/services/sns/sns_listener.py#L467-L482
Although using _FilterPolicy_ at all seems problematic at the moment too: https://github.com/localstack/localstack/issues/684#issuecomment-547978594
|
non_test
|
add sns subscription filter policy exists operator support love localstack please consider supporting our collective 👉 the operator is not supported in the sns filter policy this operator works upon attribute keys but only attribute value based operators seem to currently work although using filterpolicy at all seems problematic at the moment too
| 0
|
694,484
| 23,815,737,362
|
IssuesEvent
|
2022-09-05 06:30:01
|
YangCatalog/backend
|
https://api.github.com/repos/YangCatalog/backend
|
closed
|
Move from ciscosparkapi to webexteamssdk
|
maintenance Priority: Medium
|
The thing is that we are still using pip package called ciscosparkapi for sending messages to WebexTeams, but there is a new "version" called webexteamssdk: https://pypi.org/project/webexteamssdk/
According to the documentation: The Cisco Spark API library has been deprecated and is no longer supported;
So we need to replace ciscosparkapi with webexteamssdk
|
1.0
|
Move from ciscosparkapi to webexteamssdk - The thing is that we are still using pip package called ciscosparkapi for sending messages to WebexTeams, but there is a new "version" called webexteamssdk: https://pypi.org/project/webexteamssdk/
According to the documentation: The Cisco Spark API library has been deprecated and is no longer supported;
So we need to replace ciscosparkapi with webexteamssdk
|
non_test
|
move from ciscosparkapi to webexteamssdk the thing is that we are still using pip package called ciscosparkapi for sending messages to webexteams but there is a new version called webexteamssdk according to the documentation the cisco spark api library has been deprecated and is no longer supported so we need to replace ciscosparkapi with webexteamssdk
| 0
|
25,615
| 4,417,702,981
|
IssuesEvent
|
2016-08-15 07:21:07
|
snowie2000/mactype
|
https://api.github.com/repos/snowie2000/mactype
|
closed
|
MacType doesn't work on my OneNote 2013
|
auto-migrated Priority-Medium Type-Defect
|
```
My MacType setting is "Registry" mode.
My computer OS is Windows 7
My mactype is the latest.
```
Original issue reported on code.google.com by `JLuc...@gmail.com` on 29 Mar 2014 at 11:26
|
1.0
|
MacType doesn't work on my OneNote 2013 - ```
My MacType setting is "Registry" mode.
My computer OS is Windows 7
My mactype is the latest.
```
Original issue reported on code.google.com by `JLuc...@gmail.com` on 29 Mar 2014 at 11:26
|
non_test
|
mactype doesn t work on my onenote my mactype setting is registry mode my computer os is windows my mactype is the latest original issue reported on code google com by jluc gmail com on mar at
| 0
|
227,836
| 18,103,577,731
|
IssuesEvent
|
2021-09-22 16:36:03
|
godotengine/godot
|
https://api.github.com/repos/godotengine/godot
|
closed
|
Static Body `_ready()` is run before than parent (Spatial) `_ready()`
|
bug topic:core needs testing
|
### Godot version
3.3.2.stable.custom_build
### System information
NIXOS, Windows (Steam version)
### Issue description
Static Body `_ready()` function seems to be running before than parent `_ready()` functions.
There is no clear indication why this happens and is different from normal (up to down).
Same behavior can be seen in also in Windows (Steam) version of engine.
### Steps to reproduce
I included minimal project that contains example.
- Create project
- Add Spatial
- Add Static Body as child for Spatial
On both add scripts to print in `_init()` and `_ready()`
### Minimal reproduction project
[ready_fu.zip](https://github.com/godotengine/godot/files/7212265/ready_fu.zip)
|
1.0
|
Static Body `_ready()` is run before than parent (Spatial) `_ready()` - ### Godot version
3.3.2.stable.custom_build
### System information
NIXOS, Windows (Steam version)
### Issue description
Static Body `_ready()` function seems to be running before than parent `_ready()` functions.
There is no clear indication why this happens and is different from normal (up to down).
Same behavior can be seen in also in Windows (Steam) version of engine.
### Steps to reproduce
I included minimal project that contains example.
- Create project
- Add Spatial
- Add Static Body as child for Spatial
On both add scripts to print in `_init()` and `_ready()`
### Minimal reproduction project
[ready_fu.zip](https://github.com/godotengine/godot/files/7212265/ready_fu.zip)
|
test
|
static body ready is run before than parent spatial ready godot version stable custom build system information nixos windows steam version issue description static body ready function seems to be running before than parent ready functions there is no clear indication why this happens and is different from normal up to down same behavior can be seen in also in windows steam version of engine steps to reproduce i included minimal project that contains example create project add spatial add static body as child for spatial on both add scripts to print in init and ready minimal reproduction project
| 1
|
220,665
| 17,225,970,469
|
IssuesEvent
|
2021-07-20 01:45:28
|
apache/rocketmq
|
https://api.github.com/repos/apache/rocketmq
|
closed
|
add msgTraceEnable config in transaction producer benchmark
|
enhancement test
|
**FEATURE REQUEST**
1. Please describe the feature you are requesting.
add msgTraceEnable config in transaction producer benchmark
2. Provide any additional detail on your proposed use case for this feature.
3. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?
nice-to-have
|
1.0
|
add msgTraceEnable config in transaction producer benchmark -
**FEATURE REQUEST**
1. Please describe the feature you are requesting.
add msgTraceEnable config in transaction producer benchmark
2. Provide any additional detail on your proposed use case for this feature.
3. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?
nice-to-have
|
test
|
add msgtraceenable config in transaction producer benchmark feature request please describe the feature you are requesting add msgtraceenable config in transaction producer benchmark provide any additional detail on your proposed use case for this feature indicate the importance of this issue to you blocker must have should have nice to have are you currently using any workarounds to address this issue nice to have
| 1
|
312,109
| 26,837,567,050
|
IssuesEvent
|
2023-02-02 20:52:46
|
Azure/azure-sdk-for-net
|
https://api.github.com/repos/Azure/azure-sdk-for-net
|
closed
|
[FormRecognizer] CreateComposedModel failing in nightly runs
|
Client Cognitive - Form Recognizer test-reliability
|
FormRecognizer nightly test runs are failing with:
> Error message
> Azure.RequestFailedException : Generic error during prediction.
> Status: 200 (OK)
> ErrorCode: 3014
>
> Additional Information:
> error-0: 3014: Generic error during prediction.
>
> Content:
>
> Headers:
> ms-azure-ai-errorcode: REDACTED
> x-envoy-upstream-service-time: 33
> apim-request-id: ef12fb10-cedc-475d-b120-c7fac2b1100d
> Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
> X-Content-Type-Options: nosniff
> x-ms-region: REDACTED
> Date: Thu, 05 Jan 2023 05:18:27 GMT
> Content-Length: 213
> Content-Type: application/json; charset=utf-8
>
> Data:
> error-0: 3014: Generic error during prediction.
>
>
> Stack trace
> at Azure.Core.OperationInternal`1.GetResponseFromState(OperationState`1 state) in /mnt/vss/_work/1/s/sdk/core/Azure.Core/src/Shared/OperationInternalOfT.cs:line 289
> at Azure.Core.OperationInternal`1.UpdateStatusAsync(Boolean async, CancellationToken cancellationToken)
> at Azure.Core.OperationInternalBase.UpdateStatusAsync(CancellationToken cancellationToken) in /mnt/vss/_work/1/s/sdk/core/Azure.Core/src/Shared/OperationInternalBase.cs:line 87
> at Azure.Core.OperationPoller.WaitForCompletionAsync(Boolean async, OperationInternalBase operation, Nullable`1 suggestedInterval, CancellationToken cancellationToken) in /mnt/vss/_work/1/s/sdk/core/Azure.Core/src/Shared/OperationPoller.cs:line 79
> at Azure.Core.OperationInternalBase.WaitForCompletionResponseAsync(Boolean async, Nullable`1 pollingInterval, String scopeName, CancellationToken cancellationToken) in /mnt/vss/_work/1/s/sdk/core/Azure.Core/src/Shared/OperationInternalBase.cs:line 202
> at Azure.Core.OperationInternal`1.WaitForCompletionAsync(Boolean async, Nullable`1 pollingInterval, CancellationToken cancellationToken) in /mnt/vss/_work/1/s/sdk/core/Azure.Core/src/Shared/OperationInternalOfT.cs:line 242
> at Azure.Core.OperationInternal`1.WaitForCompletionAsync(CancellationToken cancellationToken) in /mnt/vss/_work/1/s/sdk/core/Azure.Core/src/Shared/OperationInternalOfT.cs:line 177
> at Azure.AI.FormRecognizer.Models.RecognizeCustomFormsOperation.WaitForCompletionAsync(CancellationToken cancellationToken) in /mnt/vss/_work/1/s/sdk/formrecognizer/Azure.AI.FormRecognizer/src/FormRecognizerClient/RecognizeCustomFormsOperation.cs:line 77
> at Azure.AI.FormRecognizer.Samples.FormRecognizerSamples.CreateComposedModel() in /mnt/vss/_work/1/s/sdk/formrecognizer/Azure.AI.FormRecognizer/tests/samples/V3.1/Sample11_ComposedModel.cs:line 136
> at NUnit.Framework.Internal.TaskAwaitAdapter.GenericAdapter`1.BlockUntilCompleted()
> at NUnit.Framework.Internal.MessagePumpStrategy.NoMessagePumpStrategy.WaitForCompletion(AwaitAdapter awaiter)
> at NUnit.Framework.Internal.AsyncToSyncAdapter.Await(Func`1 invoke)
> at NUnit.Framework.Internal.Commands.TestMethodCommand.RunTestMethod(TestExecutionContext context)
> at NUnit.Framework.Internal.Commands.TestMethodCommand.Execute(TestExecutionContext context)
> at NUnit.Framework.Internal.Commands.BeforeAndAfterTestCommand.<>c__DisplayClass1_0.<Execute>b__0()
> at NUnit.Framework.Internal.Commands.BeforeAndAfterTestCommand.RunTestMethodInThreadAbortSafeZone(TestExecutionContext context, Action action)
For more details check here:
- https://dev.azure.com/azure-sdk/internal/_build/results?buildId=2093097&view=results
@jsquire for notification.
|
1.0
|
[FormRecognizer] CreateComposedModel failing in nightly runs - FormRecognizer nightly test runs are failing with:
> Error message
> Azure.RequestFailedException : Generic error during prediction.
> Status: 200 (OK)
> ErrorCode: 3014
>
> Additional Information:
> error-0: 3014: Generic error during prediction.
>
> Content:
>
> Headers:
> ms-azure-ai-errorcode: REDACTED
> x-envoy-upstream-service-time: 33
> apim-request-id: ef12fb10-cedc-475d-b120-c7fac2b1100d
> Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
> X-Content-Type-Options: nosniff
> x-ms-region: REDACTED
> Date: Thu, 05 Jan 2023 05:18:27 GMT
> Content-Length: 213
> Content-Type: application/json; charset=utf-8
>
> Data:
> error-0: 3014: Generic error during prediction.
>
>
> Stack trace
> at Azure.Core.OperationInternal`1.GetResponseFromState(OperationState`1 state) in /mnt/vss/_work/1/s/sdk/core/Azure.Core/src/Shared/OperationInternalOfT.cs:line 289
> at Azure.Core.OperationInternal`1.UpdateStatusAsync(Boolean async, CancellationToken cancellationToken)
> at Azure.Core.OperationInternalBase.UpdateStatusAsync(CancellationToken cancellationToken) in /mnt/vss/_work/1/s/sdk/core/Azure.Core/src/Shared/OperationInternalBase.cs:line 87
> at Azure.Core.OperationPoller.WaitForCompletionAsync(Boolean async, OperationInternalBase operation, Nullable`1 suggestedInterval, CancellationToken cancellationToken) in /mnt/vss/_work/1/s/sdk/core/Azure.Core/src/Shared/OperationPoller.cs:line 79
> at Azure.Core.OperationInternalBase.WaitForCompletionResponseAsync(Boolean async, Nullable`1 pollingInterval, String scopeName, CancellationToken cancellationToken) in /mnt/vss/_work/1/s/sdk/core/Azure.Core/src/Shared/OperationInternalBase.cs:line 202
> at Azure.Core.OperationInternal`1.WaitForCompletionAsync(Boolean async, Nullable`1 pollingInterval, CancellationToken cancellationToken) in /mnt/vss/_work/1/s/sdk/core/Azure.Core/src/Shared/OperationInternalOfT.cs:line 242
> at Azure.Core.OperationInternal`1.WaitForCompletionAsync(CancellationToken cancellationToken) in /mnt/vss/_work/1/s/sdk/core/Azure.Core/src/Shared/OperationInternalOfT.cs:line 177
> at Azure.AI.FormRecognizer.Models.RecognizeCustomFormsOperation.WaitForCompletionAsync(CancellationToken cancellationToken) in /mnt/vss/_work/1/s/sdk/formrecognizer/Azure.AI.FormRecognizer/src/FormRecognizerClient/RecognizeCustomFormsOperation.cs:line 77
> at Azure.AI.FormRecognizer.Samples.FormRecognizerSamples.CreateComposedModel() in /mnt/vss/_work/1/s/sdk/formrecognizer/Azure.AI.FormRecognizer/tests/samples/V3.1/Sample11_ComposedModel.cs:line 136
> at NUnit.Framework.Internal.TaskAwaitAdapter.GenericAdapter`1.BlockUntilCompleted()
> at NUnit.Framework.Internal.MessagePumpStrategy.NoMessagePumpStrategy.WaitForCompletion(AwaitAdapter awaiter)
> at NUnit.Framework.Internal.AsyncToSyncAdapter.Await(Func`1 invoke)
> at NUnit.Framework.Internal.Commands.TestMethodCommand.RunTestMethod(TestExecutionContext context)
> at NUnit.Framework.Internal.Commands.TestMethodCommand.Execute(TestExecutionContext context)
> at NUnit.Framework.Internal.Commands.BeforeAndAfterTestCommand.<>c__DisplayClass1_0.<Execute>b__0()
> at NUnit.Framework.Internal.Commands.BeforeAndAfterTestCommand.RunTestMethodInThreadAbortSafeZone(TestExecutionContext context, Action action)
For more details check here:
- https://dev.azure.com/azure-sdk/internal/_build/results?buildId=2093097&view=results
@jsquire for notification.
|
test
|
createcomposedmodel failing in nightly runs formrecognizer nightly test runs are failing with error message azure requestfailedexception generic error during prediction status ok errorcode additional information error generic error during prediction content headers ms azure ai errorcode redacted x envoy upstream service time apim request id cedc strict transport security max age includesubdomains preload x content type options nosniff x ms region redacted date thu jan gmt content length content type application json charset utf data error generic error during prediction stack trace at azure core operationinternal getresponsefromstate operationstate state in mnt vss work s sdk core azure core src shared operationinternaloft cs line at azure core operationinternal updatestatusasync boolean async cancellationtoken cancellationtoken at azure core operationinternalbase updatestatusasync cancellationtoken cancellationtoken in mnt vss work s sdk core azure core src shared operationinternalbase cs line at azure core operationpoller waitforcompletionasync boolean async operationinternalbase operation nullable suggestedinterval cancellationtoken cancellationtoken in mnt vss work s sdk core azure core src shared operationpoller cs line at azure core operationinternalbase waitforcompletionresponseasync boolean async nullable pollinginterval string scopename cancellationtoken cancellationtoken in mnt vss work s sdk core azure core src shared operationinternalbase cs line at azure core operationinternal waitforcompletionasync boolean async nullable pollinginterval cancellationtoken cancellationtoken in mnt vss work s sdk core azure core src shared operationinternaloft cs line at azure core operationinternal waitforcompletionasync cancellationtoken cancellationtoken in mnt vss work s sdk core azure core src shared operationinternaloft cs line at azure ai formrecognizer models recognizecustomformsoperation waitforcompletionasync cancellationtoken cancellationtoken in mnt vss work s sdk formrecognizer azure ai formrecognizer src formrecognizerclient recognizecustomformsoperation cs line at azure ai formrecognizer samples formrecognizersamples createcomposedmodel in mnt vss work s sdk formrecognizer azure ai formrecognizer tests samples composedmodel cs line at nunit framework internal taskawaitadapter genericadapter blockuntilcompleted at nunit framework internal messagepumpstrategy nomessagepumpstrategy waitforcompletion awaitadapter awaiter at nunit framework internal asynctosyncadapter await func invoke at nunit framework internal commands testmethodcommand runtestmethod testexecutioncontext context at nunit framework internal commands testmethodcommand execute testexecutioncontext context at nunit framework internal commands beforeandaftertestcommand c b at nunit framework internal commands beforeandaftertestcommand runtestmethodinthreadabortsafezone testexecutioncontext context action action for more details check here jsquire for notification
| 1
|
33,116
| 9,022,890,097
|
IssuesEvent
|
2019-02-07 04:10:03
|
eclipse/openj9
|
https://api.github.com/repos/eclipse/openj9
|
opened
|
Running Java 12 pipelines
|
comp:build
|
Tried to run Java 12 functional.sanity testing with the changes from #3980 and #4531
https://ci.eclipse.org/openj9/view/Pipelines/job/Pipeline-Release-Build/30/
Seems like a setting is missing because the testing is looking for the jdk8 directory j2sdk-image.
`19:48:18 /home/jenkins/workspace/Test-sanity.functional-JDK12-linux_x86-64_cmprssptrs/openjdk-tests/functional/DDR_Test/build.xml:59: Error running /home/jenkins/workspace/Test-sanity.functional-JDK12-linux_x86-64_cmprssptrs/openjdkbinary/j2sdk-image/bin/../../bin/javac compiler`
|
1.0
|
Running Java 12 pipelines - Tried to run Java 12 functional.sanity testing with the changes from #3980 and #4531
https://ci.eclipse.org/openj9/view/Pipelines/job/Pipeline-Release-Build/30/
Seems like a setting is missing because the testing is looking for the jdk8 directory j2sdk-image.
`19:48:18 /home/jenkins/workspace/Test-sanity.functional-JDK12-linux_x86-64_cmprssptrs/openjdk-tests/functional/DDR_Test/build.xml:59: Error running /home/jenkins/workspace/Test-sanity.functional-JDK12-linux_x86-64_cmprssptrs/openjdkbinary/j2sdk-image/bin/../../bin/javac compiler`
|
non_test
|
running java pipelines tried to run java functional sanity testing with the changes from and seems like a setting is missing because the testing is looking for the directory image home jenkins workspace test sanity functional linux cmprssptrs openjdk tests functional ddr test build xml error running home jenkins workspace test sanity functional linux cmprssptrs openjdkbinary image bin bin javac compiler
| 0
|
606,489
| 18,763,396,712
|
IssuesEvent
|
2021-11-05 19:26:38
|
AY2122S1-CS2103T-F13-2/tp
|
https://api.github.com/repos/AY2122S1-CS2103T-F13-2/tp
|
closed
|
[PE-D] Recurring tasks that has passed the task time (overdue) just disappear from the list
|
priority.Medium
|
When making a recurring weekly task and it has passed the timing of the task, it will automatically change to next week's date and the previous task that is still not marked as done has disappeared from the task list.
Perhaps a user might want to complete an overdue recurring task instead of deleting it from the task list.
<!--session: 1635494199862-f58baa04-a233-4bab-ab3c-e2416d5c46ac--><!--Version: Web v3.4.1-->
-------------
Labels: `severity.High` `type.FeatureFlaw`
original: alissayarmantho/ped#12
|
1.0
|
[PE-D] Recurring tasks that has passed the task time (overdue) just disappear from the list - When making a recurring weekly task and it has passed the timing of the task, it will automatically change to next week's date and the previous task that is still not marked as done has disappeared from the task list.
Perhaps a user might want to complete an overdue recurring task instead of deleting it from the task list.
<!--session: 1635494199862-f58baa04-a233-4bab-ab3c-e2416d5c46ac--><!--Version: Web v3.4.1-->
-------------
Labels: `severity.High` `type.FeatureFlaw`
original: alissayarmantho/ped#12
|
non_test
|
recurring tasks that has passed the task time overdue just disappear from the list when making a recurring weekly task and it has passed the timing of the task it will automatically change to next week s date and the previous task that is still not marked as done has disappeared from the task list perhaps a user might want to complete an overdue recurring task instead of deleting it from the task list labels severity high type featureflaw original alissayarmantho ped
| 0
|
654,313
| 21,647,897,982
|
IssuesEvent
|
2022-05-06 05:45:34
|
apache/incubator-kyuubi
|
https://api.github.com/repos/apache/incubator-kyuubi
|
closed
|
[Bug] Kyuubi swagger does not show the request/response schema
|
kind:bug priority:major
|
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
### Search before asking
- [X] I have searched in the [issues](https://github.com/apache/incubator-kyuubi/issues?q=is%3Aissue) and found no similar issues.
### Describe the bug
Kyuubi swagger does not show the request/response schema.
<img width="1498" alt="image" src="https://user-images.githubusercontent.com/6757692/166659510-dfff1711-dea9-4405-9056-6d8ee714fc3b.png">
<img width="1593" alt="image" src="https://user-images.githubusercontent.com/6757692/166659561-35f30f25-2a02-47ac-a6c0-a1933d08181a.png">
### Affects Version(s)
1.6.0
### Kyuubi Server Log Output
_No response_
### Kyuubi Engine Log Output
_No response_
### Kyuubi Server Configurations
_No response_
### Kyuubi Engine Configurations
_No response_
### Additional context
_No response_
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
|
1.0
|
[Bug] Kyuubi swagger does not show the request/response schema - ### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
### Search before asking
- [X] I have searched in the [issues](https://github.com/apache/incubator-kyuubi/issues?q=is%3Aissue) and found no similar issues.
### Describe the bug
Kyuubi swagger does not show the request/response schema.
<img width="1498" alt="image" src="https://user-images.githubusercontent.com/6757692/166659510-dfff1711-dea9-4405-9056-6d8ee714fc3b.png">
<img width="1593" alt="image" src="https://user-images.githubusercontent.com/6757692/166659561-35f30f25-2a02-47ac-a6c0-a1933d08181a.png">
### Affects Version(s)
1.6.0
### Kyuubi Server Log Output
_No response_
### Kyuubi Engine Log Output
_No response_
### Kyuubi Server Configurations
_No response_
### Kyuubi Engine Configurations
_No response_
### Additional context
_No response_
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
|
non_test
|
kyuubi swagger does not show the request response schema code of conduct i agree to follow this project s search before asking i have searched in the and found no similar issues describe the bug kyuubi swagger does not show the request response schema img width alt image src img width alt image src affects version s kyuubi server log output no response kyuubi engine log output no response kyuubi server configurations no response kyuubi engine configurations no response additional context no response are you willing to submit pr yes i am willing to submit a pr
| 0
|
24,956
| 17,949,374,298
|
IssuesEvent
|
2021-09-12 12:34:07
|
m-labs/artiq
|
https://api.github.com/repos/m-labs/artiq
|
closed
|
bitstream and device_db builder, EEM I2C tree verification
|
area:gateware area:infrastructure area:packaging type:feature type:needs-funding complexity:invasive
|
With the Sinara EEMs implying mutually incompatible RTIO Phys we need to build per-setup bitstreams.
A potential idea (RFC) would be:
* (optionally) upload a minimal bistream and query EEM types and channel settings (e.g. directions) through I2C
* generate and have the user write/edit a EEM and channel RTIO description
* generate, package bitstream, maybe with a build service
* generate `device_db.pyon` template
* (optionally) verify bitstream correctness w.r.t. EEMs using I2C
* get rid of the various `FIRST_X_CHANNEL` constants
* figure out `ref_multiplier` implicit definition through existence of serdes TTL channels
C.f.
* #581 #564 for growing differentiation of TTL channel types
* #595 #788 are incompatible with other EEMs
Related:
* #781
* #779
Components:
* https://github.com/quartiq/kasli-i2c
|
1.0
|
bitstream and device_db builder, EEM I2C tree verification - With the Sinara EEMs implying mutually incompatible RTIO Phys we need to build per-setup bitstreams.
A potential idea (RFC) would be:
* (optionally) upload a minimal bistream and query EEM types and channel settings (e.g. directions) through I2C
* generate and have the user write/edit a EEM and channel RTIO description
* generate, package bitstream, maybe with a build service
* generate `device_db.pyon` template
* (optionally) verify bitstream correctness w.r.t. EEMs using I2C
* get rid of the various `FIRST_X_CHANNEL` constants
* figure out `ref_multiplier` implicit definition through existence of serdes TTL channels
C.f.
* #581 #564 for growing differentiation of TTL channel types
* #595 #788 are incompatible with other EEMs
Related:
* #781
* #779
Components:
* https://github.com/quartiq/kasli-i2c
|
non_test
|
bitstream and device db builder eem tree verification with the sinara eems implying mutually incompatible rtio phys we need to build per setup bitstreams a potential idea rfc would be optionally upload a minimal bistream and query eem types and channel settings e g directions through generate and have the user write edit a eem and channel rtio description generate package bitstream maybe with a build service generate device db pyon template optionally verify bitstream correctness w r t eems using get rid of the various first x channel constants figure out ref multiplier implicit definition through existence of serdes ttl channels c f for growing differentiation of ttl channel types are incompatible with other eems related components
| 0
|
1,032
| 13,130,290,461
|
IssuesEvent
|
2020-08-06 15:08:55
|
MicrosoftDocs/sql-docs
|
https://api.github.com/repos/MicrosoftDocs/sql-docs
|
closed
|
Estimates are way under actual size and not helpful
|
Pri2 assigned-to-author doc-bug sql/prod supportability/tech
|
Using this page, my estimates were way off from what the actual size of the index is. I believe the issue is in Step 2.4. It states:
> If there are variable-length columns in the index key, including any necessary clustering key columns as described previously in Step 2.2, determine how much space is used to store the columns within the index row ... If there are no variable-length columns, set Variable_Leaf_Size to 0.
This makes it sound like the formula should only be used when there are Variable Length Columns in the Index Key. However, when I took that approach, my estimates were way off because my indexes didn't have any variable length columns in the Index Key, and therefore I was setting the Variable_Leaf_Size to 0.
I'm assuming this is incorrect, as when I started using the formula in this step, my estimates were closer to what they should have been, even though I have no variable key columns in my index key. Plus it doesn't make sense that the calculation for the Variable_Leaf_Size should be dependent on if there is a variable column in the index key.
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: acd0f89f-5bd7-5332-fbb5-2c362d9da599
* Version Independent ID: 78e1a2f9-2aa1-06a8-ff64-21cfe75b2540
* Content: [Estimate the Size of a Nonclustered Index - SQL Server](https://docs.microsoft.com/en-us/sql/relational-databases/databases/estimate-the-size-of-a-nonclustered-index?view=sql-server-2017)
* Content Source: [docs/relational-databases/databases/estimate-the-size-of-a-nonclustered-index.md](https://github.com/MicrosoftDocs/sql-docs/blob/live/docs/relational-databases/databases/estimate-the-size-of-a-nonclustered-index.md)
* Product: **sql**
* Technology: **supportability**
* GitHub Login: @stevestein
* Microsoft Alias: **sstein**
|
True
|
Estimates are way under actual size and not helpful -
Using this page, my estimates were way off from what the actual size of the index is. I believe the issue is in Step 2.4. It states:
> If there are variable-length columns in the index key, including any necessary clustering key columns as described previously in Step 2.2, determine how much space is used to store the columns within the index row ... If there are no variable-length columns, set Variable_Leaf_Size to 0.
This makes it sound like the formula should only be used when there are Variable Length Columns in the Index Key. However, when I took that approach, my estimates were way off because my indexes didn't have any variable length columns in the Index Key, and therefore I was setting the Variable_Leaf_Size to 0.
I'm assuming this is incorrect, as when I started using the formula in this step, my estimates were closer to what they should have been, even though I have no variable key columns in my index key. Plus it doesn't make sense that the calculation for the Variable_Leaf_Size should be dependent on if there is a variable column in the index key.
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: acd0f89f-5bd7-5332-fbb5-2c362d9da599
* Version Independent ID: 78e1a2f9-2aa1-06a8-ff64-21cfe75b2540
* Content: [Estimate the Size of a Nonclustered Index - SQL Server](https://docs.microsoft.com/en-us/sql/relational-databases/databases/estimate-the-size-of-a-nonclustered-index?view=sql-server-2017)
* Content Source: [docs/relational-databases/databases/estimate-the-size-of-a-nonclustered-index.md](https://github.com/MicrosoftDocs/sql-docs/blob/live/docs/relational-databases/databases/estimate-the-size-of-a-nonclustered-index.md)
* Product: **sql**
* Technology: **supportability**
* GitHub Login: @stevestein
* Microsoft Alias: **sstein**
|
non_test
|
estimates are way under actual size and not helpful using this page my estimates were way off from what the actual size of the index is i believe the issue is in step it states if there are variable length columns in the index key including any necessary clustering key columns as described previously in step determine how much space is used to store the columns within the index row if there are no variable length columns set variable leaf size to this makes it sound like the formula should only be used when there are variable length columns in the index key however when i took that approach my estimates were way off because my indexes didn t have any variable length columns in the index key and therefore i was setting the variable leaf size to i m assuming this is incorrect as when i started using the formula in this step my estimates were closer to what they should have been even though i have no variable key columns in my index key plus it doesn t make sense that the calculation for the variable leaf size should be dependent on if there is a variable column in the index key document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source product sql technology supportability github login stevestein microsoft alias sstein
| 0
|
263,181
| 28,026,457,414
|
IssuesEvent
|
2023-03-28 09:26:51
|
Dima2021/cargo-audit
|
https://api.github.com/repos/Dima2021/cargo-audit
|
closed
|
CVE-2018-25023 (High) detected in smallvec-0.6.14.crate - autoclosed
|
Mend: dependency security vulnerability
|
## CVE-2018-25023 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>smallvec-0.6.14.crate</b></p></summary>
<p>'Small vector' optimization: store up to a small number of items on the stack</p>
<p>Library home page: <a href="https://crates.io/api/v1/crates/smallvec/0.6.14/download">https://crates.io/api/v1/crates/smallvec/0.6.14/download</a></p>
<p>
Dependency Hierarchy:
- abscissa_core-0.5.2.crate (Root Library)
- tracing-subscriber-0.1.6.crate
- :x: **smallvec-0.6.14.crate** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
An issue was discovered in the smallvec crate before 0.6.13 for Rust. It can create an uninitialized value of any type, including a reference type.
<p>Publish Date: 2021-12-27
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-25023>CVE-2018-25023</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</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://rustsec.org/advisories/RUSTSEC-2018-0018.html">https://rustsec.org/advisories/RUSTSEC-2018-0018.html</a></p>
<p>Release Date: 2021-12-27</p>
<p>Fix Resolution: smallvec - 0.6.13</p>
</p>
</details>
<p></p>
|
True
|
CVE-2018-25023 (High) detected in smallvec-0.6.14.crate - autoclosed - ## CVE-2018-25023 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>smallvec-0.6.14.crate</b></p></summary>
<p>'Small vector' optimization: store up to a small number of items on the stack</p>
<p>Library home page: <a href="https://crates.io/api/v1/crates/smallvec/0.6.14/download">https://crates.io/api/v1/crates/smallvec/0.6.14/download</a></p>
<p>
Dependency Hierarchy:
- abscissa_core-0.5.2.crate (Root Library)
- tracing-subscriber-0.1.6.crate
- :x: **smallvec-0.6.14.crate** (Vulnerable Library)
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
An issue was discovered in the smallvec crate before 0.6.13 for Rust. It can create an uninitialized value of any type, including a reference type.
<p>Publish Date: 2021-12-27
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-25023>CVE-2018-25023</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</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://rustsec.org/advisories/RUSTSEC-2018-0018.html">https://rustsec.org/advisories/RUSTSEC-2018-0018.html</a></p>
<p>Release Date: 2021-12-27</p>
<p>Fix Resolution: smallvec - 0.6.13</p>
</p>
</details>
<p></p>
|
non_test
|
cve high detected in smallvec crate autoclosed cve high severity vulnerability vulnerable library smallvec crate small vector optimization store up to a small number of items on the stack library home page a href dependency hierarchy abscissa core crate root library tracing subscriber crate x smallvec crate vulnerable library found in base branch main vulnerability details an issue was discovered in the smallvec crate before for rust it can create an uninitialized value of any type including a reference type publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution smallvec
| 0
|
159,956
| 6,065,125,994
|
IssuesEvent
|
2017-06-14 15:36:18
|
kubernetes/kubernetes
|
https://api.github.com/repos/kubernetes/kubernetes
|
closed
|
apiserver and kubelet don't agree on what names to use in TLS verification
|
priority/backlog sig/cluster-lifecycle sig/node
|
The kubelet will generate its own self-signed TLS certificates if none exist, and it uses the public IP of the server as the identifier.
apiserver, however, will attempt connections using hostnames where possible. This can cause a mismatch, such as when using `kubectl exec`, where an error will be thrown in the form of:
```
Nov 12 19:49:42 master kube-apiserver[985]: E1112 19:49:42.117202 985 errors.go:62] apiserver received an error that is not an api.Status: x509: certificate is valid for 10.1.24.65@1446839265, not ip-10-1-24-65.us-west-1.compute.internal
```
The kubelet should probably attempt to determine its hostname via reverse lookup to generate its cert, or the two should know to do identity checks via IP address, so that this doesn't happen.
|
1.0
|
apiserver and kubelet don't agree on what names to use in TLS verification - The kubelet will generate its own self-signed TLS certificates if none exist, and it uses the public IP of the server as the identifier.
apiserver, however, will attempt connections using hostnames where possible. This can cause a mismatch, such as when using `kubectl exec`, where an error will be thrown in the form of:
```
Nov 12 19:49:42 master kube-apiserver[985]: E1112 19:49:42.117202 985 errors.go:62] apiserver received an error that is not an api.Status: x509: certificate is valid for 10.1.24.65@1446839265, not ip-10-1-24-65.us-west-1.compute.internal
```
The kubelet should probably attempt to determine its hostname via reverse lookup to generate its cert, or the two should know to do identity checks via IP address, so that this doesn't happen.
|
non_test
|
apiserver and kubelet don t agree on what names to use in tls verification the kubelet will generate its own self signed tls certificates if none exist and it uses the public ip of the server as the identifier apiserver however will attempt connections using hostnames where possible this can cause a mismatch such as when using kubectl exec where an error will be thrown in the form of nov master kube apiserver errors go apiserver received an error that is not an api status certificate is valid for not ip us west compute internal the kubelet should probably attempt to determine its hostname via reverse lookup to generate its cert or the two should know to do identity checks via ip address so that this doesn t happen
| 0
|
216,929
| 16,674,627,387
|
IssuesEvent
|
2021-06-07 14:49:29
|
cloudflare/cloudflare-docs
|
https://api.github.com/repos/cloudflare/cloudflare-docs
|
closed
|
Set Framework preset to Hexo
|
documentation
|
Why can't I Set Framework preset to Hexo? It can be used before, but I accidentally deleted the project because I changed my GitHub user name.
|
1.0
|
Set Framework preset to Hexo - Why can't I Set Framework preset to Hexo? It can be used before, but I accidentally deleted the project because I changed my GitHub user name.
|
non_test
|
set framework preset to hexo why can t i set framework preset to hexo it can be used before but i accidentally deleted the project because i changed my github user name
| 0
|
41,708
| 5,355,700,215
|
IssuesEvent
|
2017-02-20 13:46:38
|
maryvilledev/skilldirectoryui
|
https://api.github.com/repos/maryvilledev/skilldirectoryui
|
closed
|
Skill Reviews that are longer than 2 lines have a wrapping problem on the skill page
|
bug UIDesign
|
Adding photo as an example. The Text should all be inline.
|
1.0
|
Skill Reviews that are longer than 2 lines have a wrapping problem on the skill page - Adding photo as an example. The Text should all be inline.
|
non_test
|
skill reviews that are longer than lines have a wrapping problem on the skill page adding photo as an example the text should all be inline
| 0
|
37,692
| 5,140,268,440
|
IssuesEvent
|
2017-01-12 03:59:17
|
freeCodeCamp/freeCodeCamp
|
https://api.github.com/repos/freeCodeCamp/freeCodeCamp
|
closed
|
Bootstrap challenge passed with wrong answer
|
tests
|
Similar to issue #12426 I just fixed
Challenge ["Responsively Style Checkboxes"](https://www.freecodecamp.com/challenges/responsively-style-checkboxes ) requires to wrap exactly 3 checkboxes inside of a div.row. It passes if you wrap 1 or more checkboxes.
I can also apply this fix if you want. I just don't know how this works, so I figured I should open an issue rather than sending it with the other pull request. Is that how it's supposed to be?
Thanks!
|
1.0
|
Bootstrap challenge passed with wrong answer - Similar to issue #12426 I just fixed
Challenge ["Responsively Style Checkboxes"](https://www.freecodecamp.com/challenges/responsively-style-checkboxes ) requires to wrap exactly 3 checkboxes inside of a div.row. It passes if you wrap 1 or more checkboxes.
I can also apply this fix if you want. I just don't know how this works, so I figured I should open an issue rather than sending it with the other pull request. Is that how it's supposed to be?
Thanks!
|
test
|
bootstrap challenge passed with wrong answer similar to issue i just fixed challenge requires to wrap exactly checkboxes inside of a div row it passes if you wrap or more checkboxes i can also apply this fix if you want i just don t know how this works so i figured i should open an issue rather than sending it with the other pull request is that how it s supposed to be thanks
| 1
|
190,019
| 14,530,790,635
|
IssuesEvent
|
2020-12-14 19:47:32
|
PowerShell/PowerShell
|
https://api.github.com/repos/PowerShell/PowerShell
|
opened
|
Debian 11 parameter binding release test failure
|
Issue-Bug Release-Testing
|
<!--
For Windows PowerShell 5.1 issues, suggestions, or feature requests please use the following link instead:
Windows PowerShell [UserVoice](https://windowsserver.uservoice.com/forums/301869-powershell)
This repository is **ONLY** for PowerShell Core 6 and PowerShell 7+ issues.
- Make sure you are able to repro it on the [latest released version](https://github.com/PowerShell/PowerShell/releases)
- Search the existing issues.
- Refer to the [FAQ](https://github.com/PowerShell/PowerShell/blob/master/docs/FAQ.md).
- Refer to the [known issues](https://docs.microsoft.com/powershell/scripting/whats-new/known-issues-ps6).
-->
## Steps to reproduce
Failure at:
https://github.com/PowerShell/PowerShell/blob/41cfc4e429aad931fca15e5f6932b5149a1655ca/test/powershell/engine/ParameterBinding/ParameterBinding.Tests.ps1#L310
with the error message:
```
Expected $false to not be found in collection @($true, $false, $false, $false, $false), but it was found.
```
|
1.0
|
Debian 11 parameter binding release test failure - <!--
For Windows PowerShell 5.1 issues, suggestions, or feature requests please use the following link instead:
Windows PowerShell [UserVoice](https://windowsserver.uservoice.com/forums/301869-powershell)
This repository is **ONLY** for PowerShell Core 6 and PowerShell 7+ issues.
- Make sure you are able to repro it on the [latest released version](https://github.com/PowerShell/PowerShell/releases)
- Search the existing issues.
- Refer to the [FAQ](https://github.com/PowerShell/PowerShell/blob/master/docs/FAQ.md).
- Refer to the [known issues](https://docs.microsoft.com/powershell/scripting/whats-new/known-issues-ps6).
-->
## Steps to reproduce
Failure at:
https://github.com/PowerShell/PowerShell/blob/41cfc4e429aad931fca15e5f6932b5149a1655ca/test/powershell/engine/ParameterBinding/ParameterBinding.Tests.ps1#L310
with the error message:
```
Expected $false to not be found in collection @($true, $false, $false, $false, $false), but it was found.
```
|
test
|
debian parameter binding release test failure for windows powershell issues suggestions or feature requests please use the following link instead windows powershell this repository is only for powershell core and powershell issues make sure you are able to repro it on the search the existing issues refer to the refer to the steps to reproduce failure at with the error message expected false to not be found in collection true false false false false but it was found
| 1
|
233,348
| 25,764,501,240
|
IssuesEvent
|
2022-12-09 00:06:38
|
bitbar/testdroid-api-client-python
|
https://api.github.com/repos/bitbar/testdroid-api-client-python
|
opened
|
CVE-2022-23491 (Medium) detected in certifi-2020.12.5-py2.py3-none-any.whl
|
security vulnerability
|
## CVE-2022-23491 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>certifi-2020.12.5-py2.py3-none-any.whl</b></p></summary>
<p>Python package for providing Mozilla's CA Bundle.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/5e/a0/5f06e1e1d463903cf0c0eebeb751791119ed7a4b3737fdc9a77f1cdfb51f/certifi-2020.12.5-py2.py3-none-any.whl">https://files.pythonhosted.org/packages/5e/a0/5f06e1e1d463903cf0c0eebeb751791119ed7a4b3737fdc9a77f1cdfb51f/certifi-2020.12.5-py2.py3-none-any.whl</a></p>
<p>Path to dependency file: /tmp/ws-scm/testdroid-api-client-python</p>
<p>Path to vulnerable library: /tmp/ws-scm/testdroid-api-client-python</p>
<p>
Dependency Hierarchy:
- requests-2.25.0-py2.py3-none-any.whl (Root Library)
- :x: **certifi-2020.12.5-py2.py3-none-any.whl** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Certifi is a curated collection of Root Certificates for validating the trustworthiness of SSL certificates while verifying the identity of TLS hosts. Certifi 2022.12.07 removes root certificates from "TrustCor" from the root store. These are in the process of being removed from Mozilla's trust store. TrustCor's root certificates are being removed pursuant to an investigation prompted by media reporting that TrustCor's ownership also operated a business that produced spyware. Conclusions of Mozilla's investigation can be found in the linked google group discussion.
<p>Publish Date: 2022-12-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-23491>CVE-2022-23491</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.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: High
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.cve.org/CVERecord?id=CVE-2022-23491">https://www.cve.org/CVERecord?id=CVE-2022-23491</a></p>
<p>Release Date: 2022-12-07</p>
<p>Fix Resolution: certifi - 2022.12.07</p>
</p>
</details>
<p></p>
|
True
|
CVE-2022-23491 (Medium) detected in certifi-2020.12.5-py2.py3-none-any.whl - ## CVE-2022-23491 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>certifi-2020.12.5-py2.py3-none-any.whl</b></p></summary>
<p>Python package for providing Mozilla's CA Bundle.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/5e/a0/5f06e1e1d463903cf0c0eebeb751791119ed7a4b3737fdc9a77f1cdfb51f/certifi-2020.12.5-py2.py3-none-any.whl">https://files.pythonhosted.org/packages/5e/a0/5f06e1e1d463903cf0c0eebeb751791119ed7a4b3737fdc9a77f1cdfb51f/certifi-2020.12.5-py2.py3-none-any.whl</a></p>
<p>Path to dependency file: /tmp/ws-scm/testdroid-api-client-python</p>
<p>Path to vulnerable library: /tmp/ws-scm/testdroid-api-client-python</p>
<p>
Dependency Hierarchy:
- requests-2.25.0-py2.py3-none-any.whl (Root Library)
- :x: **certifi-2020.12.5-py2.py3-none-any.whl** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Certifi is a curated collection of Root Certificates for validating the trustworthiness of SSL certificates while verifying the identity of TLS hosts. Certifi 2022.12.07 removes root certificates from "TrustCor" from the root store. These are in the process of being removed from Mozilla's trust store. TrustCor's root certificates are being removed pursuant to an investigation prompted by media reporting that TrustCor's ownership also operated a business that produced spyware. Conclusions of Mozilla's investigation can be found in the linked google group discussion.
<p>Publish Date: 2022-12-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-23491>CVE-2022-23491</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.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: High
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.cve.org/CVERecord?id=CVE-2022-23491">https://www.cve.org/CVERecord?id=CVE-2022-23491</a></p>
<p>Release Date: 2022-12-07</p>
<p>Fix Resolution: certifi - 2022.12.07</p>
</p>
</details>
<p></p>
|
non_test
|
cve medium detected in certifi none any whl cve medium severity vulnerability vulnerable library certifi none any whl python package for providing mozilla s ca bundle library home page a href path to dependency file tmp ws scm testdroid api client python path to vulnerable library tmp ws scm testdroid api client python dependency hierarchy requests none any whl root library x certifi none any whl vulnerable library found in base branch master vulnerability details certifi is a curated collection of root certificates for validating the trustworthiness of ssl certificates while verifying the identity of tls hosts certifi removes root certificates from trustcor from the root store these are in the process of being removed from mozilla s trust store trustcor s root certificates are being removed pursuant to an investigation prompted by media reporting that trustcor s ownership also operated a business that produced spyware conclusions of mozilla s investigation can be found in the linked google group discussion publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required high user interaction none scope changed impact metrics confidentiality impact none integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution certifi
| 0
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.