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
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
83,061
| 7,860,540,079
|
IssuesEvent
|
2018-06-21 20:20:17
|
rancher/rancher
|
https://api.github.com/repos/rancher/rancher
|
closed
|
kubelets not restarted if Azure cloud-provider is updated
|
area/rke kind/bug status/resolved status/to-test version/2.0
|
**Rancher versions:**
rancher/rancher: v2.0.2
**Steps to Reproduce:**
In GUI, Edit the Cluster and Update Azure Cloud-Provider setting.
Save changes.
The new config gets written, but the kubelets don't get restarted to pick up the changes in the config.
|
1.0
|
kubelets not restarted if Azure cloud-provider is updated - **Rancher versions:**
rancher/rancher: v2.0.2
**Steps to Reproduce:**
In GUI, Edit the Cluster and Update Azure Cloud-Provider setting.
Save changes.
The new config gets written, but the kubelets don't get restarted to pick up the changes in the config.
|
test
|
kubelets not restarted if azure cloud provider is updated rancher versions rancher rancher steps to reproduce in gui edit the cluster and update azure cloud provider setting save changes the new config gets written but the kubelets don t get restarted to pick up the changes in the config
| 1
|
109,858
| 23,830,605,161
|
IssuesEvent
|
2022-09-05 20:13:49
|
alefragnani/vscode-bookmarks
|
https://api.github.com/repos/alefragnani/vscode-bookmarks
|
closed
|
[BUG] - Bookmark on a line prevents click to toggle breakpoint
|
bug duplicate depends on caused by vscode
|
When a line is bookmarked, the bookmark appears behind a debug breakpoint (red dot). You then can't click the red dot to toggle it on/off.
|
1.0
|
[BUG] - Bookmark on a line prevents click to toggle breakpoint - When a line is bookmarked, the bookmark appears behind a debug breakpoint (red dot). You then can't click the red dot to toggle it on/off.
|
non_test
|
bookmark on a line prevents click to toggle breakpoint when a line is bookmarked the bookmark appears behind a debug breakpoint red dot you then can t click the red dot to toggle it on off
| 0
|
184,038
| 6,700,447,267
|
IssuesEvent
|
2017-10-11 04:52:08
|
jwwolfe/innsystems
|
https://api.github.com/repos/jwwolfe/innsystems
|
closed
|
Testing client connection
|
auto-migrated Component-Logic Priority-Low Type-Enhancement
|
```
Add a "ping" routine into the netController to determine periodically
whether or not the clients are still alive and active and if not remove
them from the list of connected clients
```
Original issue reported on code.google.com by `darkbird44@gmail.com` on 7 Mar 2007 at 5:38
|
1.0
|
Testing client connection - ```
Add a "ping" routine into the netController to determine periodically
whether or not the clients are still alive and active and if not remove
them from the list of connected clients
```
Original issue reported on code.google.com by `darkbird44@gmail.com` on 7 Mar 2007 at 5:38
|
non_test
|
testing client connection add a ping routine into the netcontroller to determine periodically whether or not the clients are still alive and active and if not remove them from the list of connected clients original issue reported on code google com by gmail com on mar at
| 0
|
71,450
| 7,245,095,821
|
IssuesEvent
|
2018-02-14 16:58:16
|
mono/mono
|
https://api.github.com/repos/mono/mono
|
closed
|
Invalid cast is not checked for nullable types
|
area-Runtime: JIT disabled-test
|
## Steps to Reproduce
```c#
using System;
class Program {
static void Main (string [] args)
{
DayOfWeek enumValue = DayOfWeek.Monday;
object value = (int)enumValue;
var res = (DayOfWeek?)value; // Should throw
return;
}
}
```
## Current Behavior
No exception
## Expected Behavior
System.InvalidCastException
### On which platforms did you notice this
[ ] macOS
[ ] Linux
[ ] Windows
**Version Used**:
<!--
You can use `mono --version` or About dialog to obtain this information.
-->
### Stacktrace
```
Please paste the stacktrace here if available.
```
|
1.0
|
Invalid cast is not checked for nullable types - ## Steps to Reproduce
```c#
using System;
class Program {
static void Main (string [] args)
{
DayOfWeek enumValue = DayOfWeek.Monday;
object value = (int)enumValue;
var res = (DayOfWeek?)value; // Should throw
return;
}
}
```
## Current Behavior
No exception
## Expected Behavior
System.InvalidCastException
### On which platforms did you notice this
[ ] macOS
[ ] Linux
[ ] Windows
**Version Used**:
<!--
You can use `mono --version` or About dialog to obtain this information.
-->
### Stacktrace
```
Please paste the stacktrace here if available.
```
|
test
|
invalid cast is not checked for nullable types steps to reproduce c using system class program static void main string args dayofweek enumvalue dayofweek monday object value int enumvalue var res dayofweek value should throw return current behavior no exception expected behavior system invalidcastexception on which platforms did you notice this macos linux windows version used you can use mono version or about dialog to obtain this information stacktrace please paste the stacktrace here if available
| 1
|
346,298
| 30,882,789,882
|
IssuesEvent
|
2023-08-03 19:00:14
|
cockroachdb/cockroach
|
https://api.github.com/repos/cockroachdb/cockroach
|
closed
|
roachtest: backup-restore/mixed-version failed [upgrade time out: slow "create and index new computed columns on system sql stats tables"]
|
C-test-failure O-robot O-roachtest T-testeng X-noreuse branch-release-23.1
|
roachtest.backup-restore/mixed-version [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/11016945?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/11016945?buildTab=artifacts#/backup-restore/mixed-version) on release-23.1 @ [81e44ab558b20b0ff55020ff05621c0ef43b4241](https://github.com/cockroachdb/cockroach/commits/81e44ab558b20b0ff55020ff05621c0ef43b4241):
```
(mixedversion.go:475).Run: mixed-version test failure while running step 34 (wait for nodes :1-4 to all have the same cluster version (same as binary version of node 1)): 1: expected cluster version 23.1, got 22.2-90
test artifacts and logs in: /artifacts/backup-restore/mixed-version/run_1
```
<p>Parameters: <code>ROACHTEST_arch=amd64</code>
, <code>ROACHTEST_cloud=gce</code>
, <code>ROACHTEST_cpu=4</code>
, <code>ROACHTEST_encrypted=true</code>
, <code>ROACHTEST_ssd=0</code>
</p>
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/disaster-recovery
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*backup-restore/mixed-version.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-30029
|
3.0
|
roachtest: backup-restore/mixed-version failed [upgrade time out: slow "create and index new computed columns on system sql stats tables"] - roachtest.backup-restore/mixed-version [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/11016945?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/11016945?buildTab=artifacts#/backup-restore/mixed-version) on release-23.1 @ [81e44ab558b20b0ff55020ff05621c0ef43b4241](https://github.com/cockroachdb/cockroach/commits/81e44ab558b20b0ff55020ff05621c0ef43b4241):
```
(mixedversion.go:475).Run: mixed-version test failure while running step 34 (wait for nodes :1-4 to all have the same cluster version (same as binary version of node 1)): 1: expected cluster version 23.1, got 22.2-90
test artifacts and logs in: /artifacts/backup-restore/mixed-version/run_1
```
<p>Parameters: <code>ROACHTEST_arch=amd64</code>
, <code>ROACHTEST_cloud=gce</code>
, <code>ROACHTEST_cpu=4</code>
, <code>ROACHTEST_encrypted=true</code>
, <code>ROACHTEST_ssd=0</code>
</p>
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/disaster-recovery
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*backup-restore/mixed-version.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-30029
|
test
|
roachtest backup restore mixed version failed roachtest backup restore mixed version with on release mixedversion go run mixed version test failure while running step wait for nodes to all have the same cluster version same as binary version of node expected cluster version got test artifacts and logs in artifacts backup restore mixed version run parameters roachtest arch roachtest cloud gce roachtest cpu roachtest encrypted true roachtest ssd help see see cc cockroachdb disaster recovery jira issue crdb
| 1
|
95,080
| 8,530,659,023
|
IssuesEvent
|
2018-11-04 01:30:24
|
snext1220/stext
|
https://api.github.com/repos/snext1220/stext
|
closed
|
free3の追加
|
Testing enhancement
|
#7 よりの派生です。
ダイアログボックスのレイアウトを変更しない範囲で、ということで、まずはfree3を追加しました。
伴い、以下の要素も対応予定です。
- [x] ダイアログでのfree3属性の読み書き
- [x] scene要素のfree3属性
- [x] free3による分岐
- [x] GBAT2STextへのfree3追加
|
1.0
|
free3の追加 - #7 よりの派生です。
ダイアログボックスのレイアウトを変更しない範囲で、ということで、まずはfree3を追加しました。
伴い、以下の要素も対応予定です。
- [x] ダイアログでのfree3属性の読み書き
- [x] scene要素のfree3属性
- [x] free3による分岐
- [x] GBAT2STextへのfree3追加
|
test
|
よりの派生です。 ダイアログボックスのレイアウトを変更しない範囲で、ということで、 。 伴い、以下の要素も対応予定です。
| 1
|
190,221
| 14,538,418,395
|
IssuesEvent
|
2020-12-15 10:26:51
|
mysociety/alaveteli
|
https://api.github.com/repos/mysociety/alaveteli
|
closed
|
Rendering exceptions while running integration specs can disguise failures
|
bug f:framework test-suite
|
Due to having `Rails.application.config.action_dispatch.show_exceptions = true` in a before suite callback [1] means Rails' development in-browser exception rendering is turned on. If we have integration specs where with an expectation like:
```
expect(page).to have_content("foo")
```
the `have_content` line could appear in the stacktrace meaning this expectation will pass.
This hid the errors seen in #6006 when `spec/integration/classify_request_spec.rb` was tested before some (all?) controller spec. Somehow if controller spec was run first it resulted in the exceptions not being shown.
We should consider not setting `show_exceptions = true`.
[1] https://github.com/mysociety/alaveteli/blob/8959f3f/spec/spec_helper.rb#L116-L122
|
1.0
|
Rendering exceptions while running integration specs can disguise failures - Due to having `Rails.application.config.action_dispatch.show_exceptions = true` in a before suite callback [1] means Rails' development in-browser exception rendering is turned on. If we have integration specs where with an expectation like:
```
expect(page).to have_content("foo")
```
the `have_content` line could appear in the stacktrace meaning this expectation will pass.
This hid the errors seen in #6006 when `spec/integration/classify_request_spec.rb` was tested before some (all?) controller spec. Somehow if controller spec was run first it resulted in the exceptions not being shown.
We should consider not setting `show_exceptions = true`.
[1] https://github.com/mysociety/alaveteli/blob/8959f3f/spec/spec_helper.rb#L116-L122
|
test
|
rendering exceptions while running integration specs can disguise failures due to having rails application config action dispatch show exceptions true in a before suite callback means rails development in browser exception rendering is turned on if we have integration specs where with an expectation like expect page to have content foo the have content line could appear in the stacktrace meaning this expectation will pass this hid the errors seen in when spec integration classify request spec rb was tested before some all controller spec somehow if controller spec was run first it resulted in the exceptions not being shown we should consider not setting show exceptions true
| 1
|
517,075
| 14,994,284,309
|
IssuesEvent
|
2021-01-29 12:40:30
|
bounswe/bounswe2020group5
|
https://api.github.com/repos/bounswe/bounswe2020group5
|
closed
|
frontend / googlemap
|
Priority: High Status: Needs Review frontend
|
Google map is going to be integrated in sign in as well as profile page.
|
1.0
|
frontend / googlemap - Google map is going to be integrated in sign in as well as profile page.
|
non_test
|
frontend googlemap google map is going to be integrated in sign in as well as profile page
| 0
|
323,997
| 27,768,118,450
|
IssuesEvent
|
2023-03-16 12:51:14
|
kotest/kotest
|
https://api.github.com/repos/kotest/kotest
|
closed
|
Codepoint.ascii() does not cover the whole ASCII range.
|
Good First Issue property-testing
|
**Kotest 5.5.4**
The generator only generates codepoints from " " (32) to "z" (122) which is not even the entire printable ASCII range!
According to [Wikipedia: ASCII](https://en.wikipedia.org/wiki/ASCII), the ASCII code points are 0..127 and the printable ones are 32..126.
|
1.0
|
Codepoint.ascii() does not cover the whole ASCII range. - **Kotest 5.5.4**
The generator only generates codepoints from " " (32) to "z" (122) which is not even the entire printable ASCII range!
According to [Wikipedia: ASCII](https://en.wikipedia.org/wiki/ASCII), the ASCII code points are 0..127 and the printable ones are 32..126.
|
test
|
codepoint ascii does not cover the whole ascii range kotest the generator only generates codepoints from to z which is not even the entire printable ascii range according to the ascii code points are and the printable ones are
| 1
|
146,664
| 19,440,612,481
|
IssuesEvent
|
2021-12-22 00:01:02
|
dotnet/runtime
|
https://api.github.com/repos/dotnet/runtime
|
closed
|
Move/create authorization classes in .Net Core
|
api-suggestion area-System.Security needs more info no recent activity
|
The Microsoft.AspNetCore.Authorization namespace contains classes that are useful in .Net Core and is not dependent on ASP.Net Core, please make them available in a .Net Core namespace. Ref. [Make Authorization available outside of ASP.NET Core](https://github.com/aspnet/Security/issues/1480)
|
True
|
Move/create authorization classes in .Net Core - The Microsoft.AspNetCore.Authorization namespace contains classes that are useful in .Net Core and is not dependent on ASP.Net Core, please make them available in a .Net Core namespace. Ref. [Make Authorization available outside of ASP.NET Core](https://github.com/aspnet/Security/issues/1480)
|
non_test
|
move create authorization classes in net core the microsoft aspnetcore authorization namespace contains classes that are useful in net core and is not dependent on asp net core please make them available in a net core namespace ref
| 0
|
3,398
| 2,684,736,732
|
IssuesEvent
|
2015-03-29 09:42:23
|
cgeo/cgeo
|
https://api.github.com/repos/cgeo/cgeo
|
opened
|
Time selector for GK logs does not respect locale settings
|
Frontend Design GK low
|
2015.03.29-NB:
- Open the logging page for a geokret
- The time selector defaults to 12hour format (AM/PM) although my local setting should be 24hour format
|
1.0
|
Time selector for GK logs does not respect locale settings - 2015.03.29-NB:
- Open the logging page for a geokret
- The time selector defaults to 12hour format (AM/PM) although my local setting should be 24hour format
|
non_test
|
time selector for gk logs does not respect locale settings nb open the logging page for a geokret the time selector defaults to format am pm although my local setting should be format
| 0
|
115,847
| 9,814,973,109
|
IssuesEvent
|
2019-06-13 11:30:42
|
googleapis/google-cloud-python
|
https://api.github.com/repos/googleapis/google-cloud-python
|
closed
|
Pub/Sub: Add subscriber unit tests
|
api: pubsub testing type: cleanup
|
The test here doesn't check if `max_bytes` is abided by the subscriber client. A better test would do that and also check if `max_messages` is adhered to. What we observe now is that FlowControl doesn't work properly (#7677).
```python
def test_subscribe_options(manager_open):
creds = mock.Mock(spec=credentials.Credentials)
client = subscriber.Client(credentials=creds)
flow_control = types.FlowControl(max_bytes=42)
scheduler = mock.sentinel.scheduler
future = client.subscribe(
"sub_name_a",
callback=mock.sentinel.callback,
flow_control=flow_control,
scheduler=scheduler,
)
assert isinstance(future, futures.StreamingPullFuture)
assert future._manager._subscription == "sub_name_a"
assert future._manager.flow_control == flow_control
assert future._manager._scheduler == scheduler
manager_open.assert_called_once_with(mock.ANY, mock.sentinel.callback)
```
|
1.0
|
Pub/Sub: Add subscriber unit tests - The test here doesn't check if `max_bytes` is abided by the subscriber client. A better test would do that and also check if `max_messages` is adhered to. What we observe now is that FlowControl doesn't work properly (#7677).
```python
def test_subscribe_options(manager_open):
creds = mock.Mock(spec=credentials.Credentials)
client = subscriber.Client(credentials=creds)
flow_control = types.FlowControl(max_bytes=42)
scheduler = mock.sentinel.scheduler
future = client.subscribe(
"sub_name_a",
callback=mock.sentinel.callback,
flow_control=flow_control,
scheduler=scheduler,
)
assert isinstance(future, futures.StreamingPullFuture)
assert future._manager._subscription == "sub_name_a"
assert future._manager.flow_control == flow_control
assert future._manager._scheduler == scheduler
manager_open.assert_called_once_with(mock.ANY, mock.sentinel.callback)
```
|
test
|
pub sub add subscriber unit tests the test here doesn t check if max bytes is abided by the subscriber client a better test would do that and also check if max messages is adhered to what we observe now is that flowcontrol doesn t work properly python def test subscribe options manager open creds mock mock spec credentials credentials client subscriber client credentials creds flow control types flowcontrol max bytes scheduler mock sentinel scheduler future client subscribe sub name a callback mock sentinel callback flow control flow control scheduler scheduler assert isinstance future futures streamingpullfuture assert future manager subscription sub name a assert future manager flow control flow control assert future manager scheduler scheduler manager open assert called once with mock any mock sentinel callback
| 1
|
30,350
| 24,757,744,401
|
IssuesEvent
|
2022-10-21 19:34:38
|
provectus/kafka-ui
|
https://api.github.com/repos/provectus/kafka-ui
|
opened
|
Add an ability to deploy feature envs from forked repos
|
type/enhancement status/accepted scope/infrastructure
|
Currently it's not possible to exec feature testing workflows on PRs which have been opened on forked repos (due to pull_request_target)
A possible solution: checkout the forked branch, push it to our repo (on request, on added label) and run the workflow as usual
|
1.0
|
Add an ability to deploy feature envs from forked repos - Currently it's not possible to exec feature testing workflows on PRs which have been opened on forked repos (due to pull_request_target)
A possible solution: checkout the forked branch, push it to our repo (on request, on added label) and run the workflow as usual
|
non_test
|
add an ability to deploy feature envs from forked repos currently it s not possible to exec feature testing workflows on prs which have been opened on forked repos due to pull request target a possible solution checkout the forked branch push it to our repo on request on added label and run the workflow as usual
| 0
|
311,500
| 26,795,272,685
|
IssuesEvent
|
2023-02-01 11:24:01
|
galaxyproject/galaxy
|
https://api.github.com/repos/galaxyproject/galaxy
|
closed
|
History selector dosen't show selection on current history
|
area/UI-UX area/accessibility release-testing-23.0
|
In the history selector, it is not possible to see if the current history is selected.
**To Reproduce**
Steps to reproduce the behavior:
1. Open "Show Histories Side-by-Side" from the current History menu
2. Hide all Histories
3. attempt to re-add current history
**Expected behavior**
The popup clearly shows if the current history is selected
**Screenshots**
Not selected:
Selected:
|
1.0
|
History selector dosen't show selection on current history - In the history selector, it is not possible to see if the current history is selected.
**To Reproduce**
Steps to reproduce the behavior:
1. Open "Show Histories Side-by-Side" from the current History menu
2. Hide all Histories
3. attempt to re-add current history
**Expected behavior**
The popup clearly shows if the current history is selected
**Screenshots**
Not selected:
Selected:
|
test
|
history selector dosen t show selection on current history in the history selector it is not possible to see if the current history is selected to reproduce steps to reproduce the behavior open show histories side by side from the current history menu hide all histories attempt to re add current history expected behavior the popup clearly shows if the current history is selected screenshots not selected selected
| 1
|
312,511
| 26,869,385,530
|
IssuesEvent
|
2023-02-04 08:57:04
|
saleor/saleor-dashboard
|
https://api.github.com/repos/saleor/saleor-dashboard
|
closed
|
Cypress test fail: should create page with NUMERIC attribute
|
stale tests
|
**Known bug for versions:**
v38: true
**Additional Info:**
Spec: Tests for pages
|
1.0
|
Cypress test fail: should create page with NUMERIC attribute - **Known bug for versions:**
v38: true
**Additional Info:**
Spec: Tests for pages
|
test
|
cypress test fail should create page with numeric attribute known bug for versions true additional info spec tests for pages
| 1
|
41,513
| 5,367,468,956
|
IssuesEvent
|
2017-02-22 04:24:08
|
fossasia/open-event-android
|
https://api.github.com/repos/fossasia/open-event-android
|
opened
|
Test Generator and App with FOSSASIA Summit 2017 API
|
Test
|
API of the 2017 summit is: https://eventyay.com/api/v1/events/6?include=sessions,microlocations,tracks,speakers,sponsors
Please test the app with this link and ensure all areas are working as expected.
Cheers.
|
1.0
|
Test Generator and App with FOSSASIA Summit 2017 API - API of the 2017 summit is: https://eventyay.com/api/v1/events/6?include=sessions,microlocations,tracks,speakers,sponsors
Please test the app with this link and ensure all areas are working as expected.
Cheers.
|
test
|
test generator and app with fossasia summit api api of the summit is please test the app with this link and ensure all areas are working as expected cheers
| 1
|
36,909
| 5,095,348,923
|
IssuesEvent
|
2017-01-03 14:57:15
|
cockroachdb/cockroach
|
https://api.github.com/repos/cockroachdb/cockroach
|
closed
|
github.com/cockroachdb/cockroach/pkg/cli: TestDumpRandom failed under stress
|
Robot test-failure
|
SHA: https://github.com/cockroachdb/cockroach/commits/de4c1955456b9793ca7ebea7887348cd0afc2791
Parameters:
```
COCKROACH_PROPOSER_EVALUATED_KV=true
TAGS=
GOFLAGS=
```
Stress build found a failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=105365&tab=buildLog
```
W170102 07:35:39.555723 2079 server/status/runtime.go:116 Could not parse build timestamp: parsing time "" as "2006/01/02 15:04:05": cannot parse "" as "2006"
E170102 07:35:39.573518 2230 storage/queue.go:597 [split,n1,s1,r1/1:/{Min-Table/11},@c420ce1b00] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170102 07:35:39.585830 2230 storage/queue.go:597 [split,n1,s1,r2/1:/Table/1{1-2},@c4205d4000] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170102 07:35:39.591101 2230 storage/queue.go:597 [split,n1,s1,r3/1:/Table/1{2-3},@c420d52480] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
E170102 07:35:39.716823 2230 storage/queue.go:597 [split,n1,s1,r6/1:/Table/5{0-1},@c420eb1b00] unable to split [n1,s1,r6/1:/Table/5{0-1}] at key "/Table/52/0": key range /Table/52/0-/Table/52/0 outside of bounds of range /Table/50-/Max
W170102 07:35:39.996388 2215 util/hlc/hlc.go:145 backward time jump detected (-0.337435 seconds)
dump_test.go:233: random seed: -3556820822305715880
dump_test.go:243: random iteration 0: 466 rows
dump_test.go:283: pq: storage/store.go:2368: rejecting command with timestamp in the future: 1483342540333791760 (336.103316ms ahead)
```
|
1.0
|
github.com/cockroachdb/cockroach/pkg/cli: TestDumpRandom failed under stress - SHA: https://github.com/cockroachdb/cockroach/commits/de4c1955456b9793ca7ebea7887348cd0afc2791
Parameters:
```
COCKROACH_PROPOSER_EVALUATED_KV=true
TAGS=
GOFLAGS=
```
Stress build found a failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=105365&tab=buildLog
```
W170102 07:35:39.555723 2079 server/status/runtime.go:116 Could not parse build timestamp: parsing time "" as "2006/01/02 15:04:05": cannot parse "" as "2006"
E170102 07:35:39.573518 2230 storage/queue.go:597 [split,n1,s1,r1/1:/{Min-Table/11},@c420ce1b00] unable to split [n1,s1,r1/1:/{Min-Table/11}] at key "/Table/12/0": key range /Table/12/0-/Table/12/0 outside of bounds of range /Min-/Max
E170102 07:35:39.585830 2230 storage/queue.go:597 [split,n1,s1,r2/1:/Table/1{1-2},@c4205d4000] unable to split [n1,s1,r2/1:/Table/1{1-2}] at key "/Table/13/0": key range /Table/13/0-/Table/13/0 outside of bounds of range /Table/11-/Max
E170102 07:35:39.591101 2230 storage/queue.go:597 [split,n1,s1,r3/1:/Table/1{2-3},@c420d52480] unable to split [n1,s1,r3/1:/Table/1{2-3}] at key "/Table/14/0": key range /Table/14/0-/Table/14/0 outside of bounds of range /Table/12-/Max
E170102 07:35:39.716823 2230 storage/queue.go:597 [split,n1,s1,r6/1:/Table/5{0-1},@c420eb1b00] unable to split [n1,s1,r6/1:/Table/5{0-1}] at key "/Table/52/0": key range /Table/52/0-/Table/52/0 outside of bounds of range /Table/50-/Max
W170102 07:35:39.996388 2215 util/hlc/hlc.go:145 backward time jump detected (-0.337435 seconds)
dump_test.go:233: random seed: -3556820822305715880
dump_test.go:243: random iteration 0: 466 rows
dump_test.go:283: pq: storage/store.go:2368: rejecting command with timestamp in the future: 1483342540333791760 (336.103316ms ahead)
```
|
test
|
github com cockroachdb cockroach pkg cli testdumprandom failed under stress sha parameters cockroach proposer evaluated kv true tags goflags stress build found a failed test server status runtime go could not parse build timestamp parsing time as cannot parse as storage queue go unable to split at key table key range table table outside of bounds of range min max storage queue go unable to split at key table key range table table outside of bounds of range table max storage queue go unable to split at key table key range table table outside of bounds of range table max storage queue go unable to split at key table key range table table outside of bounds of range table max util hlc hlc go backward time jump detected seconds dump test go random seed dump test go random iteration rows dump test go pq storage store go rejecting command with timestamp in the future ahead
| 1
|
339,766
| 10,261,743,463
|
IssuesEvent
|
2019-08-22 10:38:19
|
vmware/vic
|
https://api.github.com/repos/vmware/vic
|
closed
|
firewall status delayed on vcenter
|
component/install component/vicadmin impact/doc priority/p4
|
In a vCenter environment, after updating the firewall allowed IP rules on one of the managed hosts the data about the updated firewall rules is delayed in updating for an undetermined amount of time.
The result of this is that vicadmin can show an incorrect firewall status and that VCH create checks will operate based on stale state and incorrectly report success/failure.
This log shows that the VCH deployed at 10.161.23.216 is allowed by the nfsClient firewall rule, even though that specific allowed IP was removed several minutes ago. The firewall is behaving correctly in this case because I can't run/attach a container with the VCH IP not in the allowed IP list.
vicadmin.log
```
time=2016-11-11T23:10:44.930829084Z level=debug msg=[ END ] [github.com/vmware/vic/lib/install/validate.CreateFromVCHConfig:61] [477.074µs]
time="2016-11-11T23:10:44Z" level=info msg="Using management IP {10.161.23.216 ffffe000} for firewall check"
time="2016-11-11T23:10:44Z" level=info msg="Firewall status: ENABLED on \"/ha-datacenter/host/10.161.22.8/10.161.22.8\""
time="2016-11-11T23:10:44Z" level=debug msg="filtered rules: [{{} nfsClient NFS Client false [{{} 0 65535 outbound dst tcp}] true 0xc4205d1bc0}]"
time="2016-11-11T23:10:44Z" level=debug msg="filtered IPs: [10.162.203.56 10.166.2.116 10.162.202.248 10.162.202.209 10.161.23.216] networks: [] allIP: false rule: nfsClient"
time="2016-11-11T23:10:44Z" level=info msg="Firewall configuration OK on hosts:"
time="2016-11-11T23:10:44Z" level=info msg="\t\"/ha-datacenter/host/10.161.22.8/10.161.22.8\""
```
This log shows (incorrectly) that host 10.161.23.216 is allowed by firewall rules
vic-machine create
```
DEBU[2016-11-11T17:25:03-06:00] Network configuration:
DEBU[2016-11-11T17:25:03-06:00] Network: client NetworkEndpoint: &{{ client } true 10.161.23.216/24 {<nil> <nil>} {{ Network:network-18 client } {10.161.23.1 ffffff00} false [] [] []} []}
DEBU[2016-11-11T17:25:03-06:00] Network: management NetworkEndpoint: &{{ } true 10.161.23.216/24 {<nil> <nil>} {{ Network:network-18 management } {10.161.23.1 ffffff00} false [] [] []} []}
DEBU[2016-11-11T17:25:03-06:00] Network: external NetworkEndpoint: &{{ external } true 10.161.23.216/24 {<nil> <nil>} {{ Network:network-18 external } {10.161.23.1 ffffff00} true [] [] []} []}
time=2016-11-11T17:25:03.460107249-06:00 level=debug msg=[BEGIN]
...
[github.com/vmware/vic/lib/install/validate.(*Validator).CheckFirewall:86]
DEBU[2016-11-11T17:25:04-06:00] Checking firewall with management network IP {10.161.23.216 ffffff00}
INFO[2016-11-11T17:25:05-06:00] Firewall status: ENABLED on "/ha-datacenter/host/10.161.22.8/10.161.22.8"
DEBU[2016-11-11T17:25:06-06:00] filtered rules: [{{} nfsClient NFS Client false [{{} 0 65535 outbound dst tcp}] true 0xc420010640}]
DEBU[2016-11-11T17:25:06-06:00] filtered IPs: [10.162.203.56 10.166.2.116 10.162.202.248 10.162.202.209 10.161.23.216] networks: [] allIP: false rule: nfsClient
INFO[2016-11-11T17:25:06-06:00] Firewall configuration OK on hosts:
INFO[2016-11-11T17:25:06-06:00] "/ha-datacenter/host/10.161.22.8/10.161.22.8"
```
|
1.0
|
firewall status delayed on vcenter - In a vCenter environment, after updating the firewall allowed IP rules on one of the managed hosts the data about the updated firewall rules is delayed in updating for an undetermined amount of time.
The result of this is that vicadmin can show an incorrect firewall status and that VCH create checks will operate based on stale state and incorrectly report success/failure.
This log shows that the VCH deployed at 10.161.23.216 is allowed by the nfsClient firewall rule, even though that specific allowed IP was removed several minutes ago. The firewall is behaving correctly in this case because I can't run/attach a container with the VCH IP not in the allowed IP list.
vicadmin.log
```
time=2016-11-11T23:10:44.930829084Z level=debug msg=[ END ] [github.com/vmware/vic/lib/install/validate.CreateFromVCHConfig:61] [477.074µs]
time="2016-11-11T23:10:44Z" level=info msg="Using management IP {10.161.23.216 ffffe000} for firewall check"
time="2016-11-11T23:10:44Z" level=info msg="Firewall status: ENABLED on \"/ha-datacenter/host/10.161.22.8/10.161.22.8\""
time="2016-11-11T23:10:44Z" level=debug msg="filtered rules: [{{} nfsClient NFS Client false [{{} 0 65535 outbound dst tcp}] true 0xc4205d1bc0}]"
time="2016-11-11T23:10:44Z" level=debug msg="filtered IPs: [10.162.203.56 10.166.2.116 10.162.202.248 10.162.202.209 10.161.23.216] networks: [] allIP: false rule: nfsClient"
time="2016-11-11T23:10:44Z" level=info msg="Firewall configuration OK on hosts:"
time="2016-11-11T23:10:44Z" level=info msg="\t\"/ha-datacenter/host/10.161.22.8/10.161.22.8\""
```
This log shows (incorrectly) that host 10.161.23.216 is allowed by firewall rules
vic-machine create
```
DEBU[2016-11-11T17:25:03-06:00] Network configuration:
DEBU[2016-11-11T17:25:03-06:00] Network: client NetworkEndpoint: &{{ client } true 10.161.23.216/24 {<nil> <nil>} {{ Network:network-18 client } {10.161.23.1 ffffff00} false [] [] []} []}
DEBU[2016-11-11T17:25:03-06:00] Network: management NetworkEndpoint: &{{ } true 10.161.23.216/24 {<nil> <nil>} {{ Network:network-18 management } {10.161.23.1 ffffff00} false [] [] []} []}
DEBU[2016-11-11T17:25:03-06:00] Network: external NetworkEndpoint: &{{ external } true 10.161.23.216/24 {<nil> <nil>} {{ Network:network-18 external } {10.161.23.1 ffffff00} true [] [] []} []}
time=2016-11-11T17:25:03.460107249-06:00 level=debug msg=[BEGIN]
...
[github.com/vmware/vic/lib/install/validate.(*Validator).CheckFirewall:86]
DEBU[2016-11-11T17:25:04-06:00] Checking firewall with management network IP {10.161.23.216 ffffff00}
INFO[2016-11-11T17:25:05-06:00] Firewall status: ENABLED on "/ha-datacenter/host/10.161.22.8/10.161.22.8"
DEBU[2016-11-11T17:25:06-06:00] filtered rules: [{{} nfsClient NFS Client false [{{} 0 65535 outbound dst tcp}] true 0xc420010640}]
DEBU[2016-11-11T17:25:06-06:00] filtered IPs: [10.162.203.56 10.166.2.116 10.162.202.248 10.162.202.209 10.161.23.216] networks: [] allIP: false rule: nfsClient
INFO[2016-11-11T17:25:06-06:00] Firewall configuration OK on hosts:
INFO[2016-11-11T17:25:06-06:00] "/ha-datacenter/host/10.161.22.8/10.161.22.8"
```
|
non_test
|
firewall status delayed on vcenter in a vcenter environment after updating the firewall allowed ip rules on one of the managed hosts the data about the updated firewall rules is delayed in updating for an undetermined amount of time the result of this is that vicadmin can show an incorrect firewall status and that vch create checks will operate based on stale state and incorrectly report success failure this log shows that the vch deployed at is allowed by the nfsclient firewall rule even though that specific allowed ip was removed several minutes ago the firewall is behaving correctly in this case because i can t run attach a container with the vch ip not in the allowed ip list vicadmin log time level debug msg time level info msg using management ip for firewall check time level info msg firewall status enabled on ha datacenter host time level debug msg filtered rules true time level debug msg filtered ips networks allip false rule nfsclient time level info msg firewall configuration ok on hosts time level info msg t ha datacenter host this log shows incorrectly that host is allowed by firewall rules vic machine create debu network configuration debu network client networkendpoint client true network network client false debu network management networkendpoint true network network management false debu network external networkendpoint external true network network external true time level debug msg debu checking firewall with management network ip info firewall status enabled on ha datacenter host debu filtered rules true debu filtered ips networks allip false rule nfsclient info firewall configuration ok on hosts info ha datacenter host
| 0
|
168,336
| 13,079,810,502
|
IssuesEvent
|
2020-08-01 04:55:33
|
cockroachdb/cockroach
|
https://api.github.com/repos/cockroachdb/cockroach
|
closed
|
roachtest: pgjdbc failed
|
C-test-failure O-roachtest O-robot branch-provisional_202007071743_v20.2.0-alpha.2 release-blocker
|
[(roachtest).pgjdbc failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=2071705&tab=buildLog) on [provisional_202007071743_v20.2.0-alpha.2@0b6e118bc1bcba4cfb4fc6c660153ec5be3989e8](https://github.com/cockroachdb/cockroach/commits/0b6e118bc1bcba4cfb4fc6c660153ec5be3989e8):
```
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithRepeatedInsertStatement[binary = REGULAR, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testWarningsAreCleared[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testSelectInBatchThrows[binary = FORCE, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testSelectInBatchThrows[binary = REGULAR, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testServerPrepareMultipleRows[binary = FORCE, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testStringAddBatchOnPreparedStatement[binary = FORCE, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithAlternatingAndUnknownTypes4[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithAlternatingAndUnknownTypes4[binary = FORCE, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testNoServerPrepareOneRow[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithAlternatingAndUnknownTypes5[binary = REGULAR, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testExecuteEmptyBatch[binary = REGULAR, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testClearPreparedNoArgBatch[binary = FORCE, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithAlternatingAndUnknownTypes3[binary = REGULAR, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testEmptyClearBatch[binary = REGULAR, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testClearPreparedNoArgBatch[binary = REGULAR, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testNoServerPrepareOneRow[binary = FORCE, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchEscapeProcessing[binary = REGULAR, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithMultiInsert[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testExecuteEmptyBatch[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithAlternatingAndUnknownTypes5[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testTransactionalBehaviour[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testPreparedNoParameters[binary = FORCE, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithRepeatedInsertStatement[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchEscapeProcessing[binary = FORCE, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testSupportsBatchUpdates[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testTransactionalBehaviour[binary = FORCE, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testStringAddBatchOnPreparedStatement[binary = REGULAR, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testNoServerPrepareOneRow[binary = REGULAR, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithAlternatingAndUnknownTypes5[binary = FORCE, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testSmallBatchUpdateFailureSimple[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithAlternatingAndUnknownTypes5[binary = FORCE, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testTransactionalBehaviour[binary = REGULAR, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testNoServerPrepareOneRow[binary = FORCE, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testSupportsBatchUpdates[binary = REGULAR, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithTwoMultiInsertStatements[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithAlternatingAndUnknownTypes1[binary = FORCE, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testStringAddBatchOnPreparedStatement[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testClearBatch[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithRepeatedInsertStatement[binary = FORCE, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchedInsertReWriteEnabledTest.testBatchWithReWrittenBatchStatementWithSemiColon[3: autoCommit=NO, binary=FORCE] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testTransactionalBehaviour[binary = FORCE, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithAlternatingAndUnknownTypes1[binary = FORCE, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithAlternatingAndUnknownTypes1[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testEmptyClearBatch[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithAlternatingAndUnknownTypes2[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithAlternatingAndUnknownTypes3[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithAlternatingAndUnknownTypes6[binary = REGULAR, insertRewrite = false] - (unexpected)
For a full summary look at the pgjdbc artifacts
An updated blocklist (pgjdbcBlockList20_2) is available in the artifacts' pgjdbc log
```
<details><summary>More</summary><p>
Artifacts: [/pgjdbc](https://teamcity.cockroachdb.com/viewLog.html?buildId=2071705&tab=artifacts#/pgjdbc)
Related:
- #49735 roachtest: pgjdbc failed [C-test-failure](https://api.github.com/repos/cockroachdb/cockroach/labels/C-test-failure) [O-roachtest](https://api.github.com/repos/cockroachdb/cockroach/labels/O-roachtest) [O-robot](https://api.github.com/repos/cockroachdb/cockroach/labels/O-robot) [branch-release-20.1](https://api.github.com/repos/cockroachdb/cockroach/labels/branch-release-20.1) [release-blocker](https://api.github.com/repos/cockroachdb/cockroach/labels/release-blocker)
- #49517 roachtest: pgjdbc failed [C-test-failure](https://api.github.com/repos/cockroachdb/cockroach/labels/C-test-failure) [O-roachtest](https://api.github.com/repos/cockroachdb/cockroach/labels/O-roachtest) [O-robot](https://api.github.com/repos/cockroachdb/cockroach/labels/O-robot) [branch-master](https://api.github.com/repos/cockroachdb/cockroach/labels/branch-master) [release-blocker](https://api.github.com/repos/cockroachdb/cockroach/labels/release-blocker)
[See this test on roachdash](https://roachdash.crdb.dev/?filter=status%3Aopen+t%3A.%2Apgjdbc.%2A&sort=title&restgroup=false&display=lastcommented+project)
<sub>powered by [pkg/cmd/internal/issues](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)</sub></p></details>
|
2.0
|
roachtest: pgjdbc failed - [(roachtest).pgjdbc failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=2071705&tab=buildLog) on [provisional_202007071743_v20.2.0-alpha.2@0b6e118bc1bcba4cfb4fc6c660153ec5be3989e8](https://github.com/cockroachdb/cockroach/commits/0b6e118bc1bcba4cfb4fc6c660153ec5be3989e8):
```
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithRepeatedInsertStatement[binary = REGULAR, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testWarningsAreCleared[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testSelectInBatchThrows[binary = FORCE, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testSelectInBatchThrows[binary = REGULAR, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testServerPrepareMultipleRows[binary = FORCE, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testStringAddBatchOnPreparedStatement[binary = FORCE, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithAlternatingAndUnknownTypes4[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithAlternatingAndUnknownTypes4[binary = FORCE, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testNoServerPrepareOneRow[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithAlternatingAndUnknownTypes5[binary = REGULAR, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testExecuteEmptyBatch[binary = REGULAR, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testClearPreparedNoArgBatch[binary = FORCE, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithAlternatingAndUnknownTypes3[binary = REGULAR, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testEmptyClearBatch[binary = REGULAR, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testClearPreparedNoArgBatch[binary = REGULAR, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testNoServerPrepareOneRow[binary = FORCE, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchEscapeProcessing[binary = REGULAR, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithMultiInsert[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testExecuteEmptyBatch[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithAlternatingAndUnknownTypes5[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testTransactionalBehaviour[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testPreparedNoParameters[binary = FORCE, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithRepeatedInsertStatement[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchEscapeProcessing[binary = FORCE, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testSupportsBatchUpdates[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testTransactionalBehaviour[binary = FORCE, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testStringAddBatchOnPreparedStatement[binary = REGULAR, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testNoServerPrepareOneRow[binary = REGULAR, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithAlternatingAndUnknownTypes5[binary = FORCE, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testSmallBatchUpdateFailureSimple[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithAlternatingAndUnknownTypes5[binary = FORCE, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testTransactionalBehaviour[binary = REGULAR, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testNoServerPrepareOneRow[binary = FORCE, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testSupportsBatchUpdates[binary = REGULAR, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithTwoMultiInsertStatements[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithAlternatingAndUnknownTypes1[binary = FORCE, insertRewrite = false] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testStringAddBatchOnPreparedStatement[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testClearBatch[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithRepeatedInsertStatement[binary = FORCE, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchedInsertReWriteEnabledTest.testBatchWithReWrittenBatchStatementWithSemiColon[3: autoCommit=NO, binary=FORCE] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testTransactionalBehaviour[binary = FORCE, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithAlternatingAndUnknownTypes1[binary = FORCE, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithAlternatingAndUnknownTypes1[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testEmptyClearBatch[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithAlternatingAndUnknownTypes2[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithAlternatingAndUnknownTypes3[binary = REGULAR, insertRewrite = true] - (unexpected)
--- PASS: org.postgresql.test.jdbc2.BatchExecuteTest.testBatchWithAlternatingAndUnknownTypes6[binary = REGULAR, insertRewrite = false] - (unexpected)
For a full summary look at the pgjdbc artifacts
An updated blocklist (pgjdbcBlockList20_2) is available in the artifacts' pgjdbc log
```
<details><summary>More</summary><p>
Artifacts: [/pgjdbc](https://teamcity.cockroachdb.com/viewLog.html?buildId=2071705&tab=artifacts#/pgjdbc)
Related:
- #49735 roachtest: pgjdbc failed [C-test-failure](https://api.github.com/repos/cockroachdb/cockroach/labels/C-test-failure) [O-roachtest](https://api.github.com/repos/cockroachdb/cockroach/labels/O-roachtest) [O-robot](https://api.github.com/repos/cockroachdb/cockroach/labels/O-robot) [branch-release-20.1](https://api.github.com/repos/cockroachdb/cockroach/labels/branch-release-20.1) [release-blocker](https://api.github.com/repos/cockroachdb/cockroach/labels/release-blocker)
- #49517 roachtest: pgjdbc failed [C-test-failure](https://api.github.com/repos/cockroachdb/cockroach/labels/C-test-failure) [O-roachtest](https://api.github.com/repos/cockroachdb/cockroach/labels/O-roachtest) [O-robot](https://api.github.com/repos/cockroachdb/cockroach/labels/O-robot) [branch-master](https://api.github.com/repos/cockroachdb/cockroach/labels/branch-master) [release-blocker](https://api.github.com/repos/cockroachdb/cockroach/labels/release-blocker)
[See this test on roachdash](https://roachdash.crdb.dev/?filter=status%3Aopen+t%3A.%2Apgjdbc.%2A&sort=title&restgroup=false&display=lastcommented+project)
<sub>powered by [pkg/cmd/internal/issues](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)</sub></p></details>
|
test
|
roachtest pgjdbc failed on pass org postgresql test batchexecutetest testbatchwithrepeatedinsertstatement unexpected pass org postgresql test batchexecutetest testwarningsarecleared unexpected pass org postgresql test batchexecutetest testselectinbatchthrows unexpected pass org postgresql test batchexecutetest testselectinbatchthrows unexpected pass org postgresql test batchexecutetest testserverpreparemultiplerows unexpected pass org postgresql test batchexecutetest teststringaddbatchonpreparedstatement unexpected pass org postgresql test batchexecutetest unexpected pass org postgresql test batchexecutetest unexpected pass org postgresql test batchexecutetest testnoserverprepareonerow unexpected pass org postgresql test batchexecutetest unexpected pass org postgresql test batchexecutetest testexecuteemptybatch unexpected pass org postgresql test batchexecutetest testclearpreparednoargbatch unexpected pass org postgresql test batchexecutetest unexpected pass org postgresql test batchexecutetest testemptyclearbatch unexpected pass org postgresql test batchexecutetest testclearpreparednoargbatch unexpected pass org postgresql test batchexecutetest testnoserverprepareonerow unexpected pass org postgresql test batchexecutetest testbatchescapeprocessing unexpected pass org postgresql test batchexecutetest testbatchwithmultiinsert unexpected pass org postgresql test batchexecutetest testexecuteemptybatch unexpected pass org postgresql test batchexecutetest unexpected pass org postgresql test batchexecutetest testtransactionalbehaviour unexpected pass org postgresql test batchexecutetest testpreparednoparameters unexpected pass org postgresql test batchexecutetest testbatchwithrepeatedinsertstatement unexpected pass org postgresql test batchexecutetest testbatchescapeprocessing unexpected pass org postgresql test batchexecutetest testsupportsbatchupdates unexpected pass org postgresql test batchexecutetest testtransactionalbehaviour unexpected pass org postgresql test batchexecutetest teststringaddbatchonpreparedstatement unexpected pass org postgresql test batchexecutetest testnoserverprepareonerow unexpected pass org postgresql test batchexecutetest unexpected pass org postgresql test batchexecutetest testsmallbatchupdatefailuresimple unexpected pass org postgresql test batchexecutetest unexpected pass org postgresql test batchexecutetest testtransactionalbehaviour unexpected pass org postgresql test batchexecutetest testnoserverprepareonerow unexpected pass org postgresql test batchexecutetest testsupportsbatchupdates unexpected pass org postgresql test batchexecutetest testbatchwithtwomultiinsertstatements unexpected pass org postgresql test batchexecutetest unexpected pass org postgresql test batchexecutetest teststringaddbatchonpreparedstatement unexpected pass org postgresql test batchexecutetest testclearbatch unexpected pass org postgresql test batchexecutetest testbatchwithrepeatedinsertstatement unexpected pass org postgresql test batchedinsertrewriteenabledtest testbatchwithrewrittenbatchstatementwithsemicolon unexpected pass org postgresql test batchexecutetest testtransactionalbehaviour unexpected pass org postgresql test batchexecutetest unexpected pass org postgresql test batchexecutetest unexpected pass org postgresql test batchexecutetest testemptyclearbatch unexpected pass org postgresql test batchexecutetest unexpected pass org postgresql test batchexecutetest unexpected pass org postgresql test batchexecutetest unexpected for a full summary look at the pgjdbc artifacts an updated blocklist is available in the artifacts pgjdbc log more artifacts related roachtest pgjdbc failed roachtest pgjdbc failed powered by
| 1
|
473,457
| 13,642,643,981
|
IssuesEvent
|
2020-09-25 15:50:01
|
craftercms/craftercms
|
https://api.github.com/repos/craftercms/craftercms
|
opened
|
[studio] Prevent null commit ID items from being inserted into the new Item table
|
enhancement priority: high
|
Check for null commit ID and try to figure out the reason for the null commit ID.
Ping me to discuss findings and design to address this.
|
1.0
|
[studio] Prevent null commit ID items from being inserted into the new Item table - Check for null commit ID and try to figure out the reason for the null commit ID.
Ping me to discuss findings and design to address this.
|
non_test
|
prevent null commit id items from being inserted into the new item table check for null commit id and try to figure out the reason for the null commit id ping me to discuss findings and design to address this
| 0
|
3,041
| 2,652,790,267
|
IssuesEvent
|
2015-03-16 19:17:11
|
softlayer/sl-ember-components
|
https://api.github.com/repos/softlayer/sl-ember-components
|
closed
|
Add tests for sl-calendar-day component
|
0 - Backlog sl-calendar tests
|
<!---
@huboard:{"order":2.1316282072803006e-14,"milestone_order":203,"custom_state":""}
-->
|
1.0
|
Add tests for sl-calendar-day component -
<!---
@huboard:{"order":2.1316282072803006e-14,"milestone_order":203,"custom_state":""}
-->
|
test
|
add tests for sl calendar day component huboard order milestone order custom state
| 1
|
116,393
| 9,851,167,045
|
IssuesEvent
|
2019-06-19 09:48:38
|
w3c/wot-thing-description
|
https://api.github.com/repos/w3c/wot-thing-description
|
closed
|
[Testing] Manual Validation is needed for Multilanguage Assertions
|
Manual Validation Testing by PR transition
|
The following need additional validation:
- [x] td-multi-languages-consistent
- [x] td-multilanguage-language-tag
- [x] td-titles-descriptions
- [x] td-ns-multilanguage-content-negotiation
- [x] td-ns-multilanguage-content-negotiation-no-multi
Note however that there is an ambiguity in td-titles-descriptions which is why there are some "failures" in the test results. A PR to resolve this ambiguity (using some informative explanatory text) would be useful, and a future spec may want to more carefully word this assertion.
|
1.0
|
[Testing] Manual Validation is needed for Multilanguage Assertions - The following need additional validation:
- [x] td-multi-languages-consistent
- [x] td-multilanguage-language-tag
- [x] td-titles-descriptions
- [x] td-ns-multilanguage-content-negotiation
- [x] td-ns-multilanguage-content-negotiation-no-multi
Note however that there is an ambiguity in td-titles-descriptions which is why there are some "failures" in the test results. A PR to resolve this ambiguity (using some informative explanatory text) would be useful, and a future spec may want to more carefully word this assertion.
|
test
|
manual validation is needed for multilanguage assertions the following need additional validation td multi languages consistent td multilanguage language tag td titles descriptions td ns multilanguage content negotiation td ns multilanguage content negotiation no multi note however that there is an ambiguity in td titles descriptions which is why there are some failures in the test results a pr to resolve this ambiguity using some informative explanatory text would be useful and a future spec may want to more carefully word this assertion
| 1
|
54,660
| 13,915,833,757
|
IssuesEvent
|
2020-10-21 01:43:54
|
rvvergara/bookstore-react-redux-app
|
https://api.github.com/repos/rvvergara/bookstore-react-redux-app
|
opened
|
CVE-2020-15366 (Medium) detected in ajv-6.10.0.tgz
|
security vulnerability
|
## CVE-2020-15366 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ajv-6.10.0.tgz</b></p></summary>
<p>Another JSON Schema Validator</p>
<p>Library home page: <a href="https://registry.npmjs.org/ajv/-/ajv-6.10.0.tgz">https://registry.npmjs.org/ajv/-/ajv-6.10.0.tgz</a></p>
<p>Path to dependency file: bookstore-react-redux-app/node_modules/ajv/package.json</p>
<p>Path to vulnerable library: bookstore-react-redux-app/node_modules/ajv/package.json</p>
<p>
Dependency Hierarchy:
- eslint-5.16.0.tgz (Root Library)
- :x: **ajv-6.10.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/rvvergara/bookstore-react-redux-app/commit/01ffbd3dcc605308fae3822634c12ea63c7a51f8">01ffbd3dcc605308fae3822634c12ea63c7a51f8</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
An issue was discovered in ajv.validate() in Ajv (aka Another JSON Schema Validator) 6.12.2. A carefully crafted JSON schema could be provided that allows execution of other code by prototype pollution. (While untrusted schemas are recommended against, the worst case of an untrusted schema should be a denial of service, not execution of code.)
<p>Publish Date: 2020-07-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15366>CVE-2020-15366</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.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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/ajv-validator/ajv/releases/tag/v6.12.3">https://github.com/ajv-validator/ajv/releases/tag/v6.12.3</a></p>
<p>Release Date: 2020-07-15</p>
<p>Fix Resolution: ajv - 6.12.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2020-15366 (Medium) detected in ajv-6.10.0.tgz - ## CVE-2020-15366 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ajv-6.10.0.tgz</b></p></summary>
<p>Another JSON Schema Validator</p>
<p>Library home page: <a href="https://registry.npmjs.org/ajv/-/ajv-6.10.0.tgz">https://registry.npmjs.org/ajv/-/ajv-6.10.0.tgz</a></p>
<p>Path to dependency file: bookstore-react-redux-app/node_modules/ajv/package.json</p>
<p>Path to vulnerable library: bookstore-react-redux-app/node_modules/ajv/package.json</p>
<p>
Dependency Hierarchy:
- eslint-5.16.0.tgz (Root Library)
- :x: **ajv-6.10.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/rvvergara/bookstore-react-redux-app/commit/01ffbd3dcc605308fae3822634c12ea63c7a51f8">01ffbd3dcc605308fae3822634c12ea63c7a51f8</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
An issue was discovered in ajv.validate() in Ajv (aka Another JSON Schema Validator) 6.12.2. A carefully crafted JSON schema could be provided that allows execution of other code by prototype pollution. (While untrusted schemas are recommended against, the worst case of an untrusted schema should be a denial of service, not execution of code.)
<p>Publish Date: 2020-07-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15366>CVE-2020-15366</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.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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/ajv-validator/ajv/releases/tag/v6.12.3">https://github.com/ajv-validator/ajv/releases/tag/v6.12.3</a></p>
<p>Release Date: 2020-07-15</p>
<p>Fix Resolution: ajv - 6.12.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_test
|
cve medium detected in ajv tgz cve medium severity vulnerability vulnerable library ajv tgz another json schema validator library home page a href path to dependency file bookstore react redux app node modules ajv package json path to vulnerable library bookstore react redux app node modules ajv package json dependency hierarchy eslint tgz root library x ajv tgz vulnerable library found in head commit a href vulnerability details an issue was discovered in ajv validate in ajv aka another json schema validator a carefully crafted json schema could be provided that allows execution of other code by prototype pollution while untrusted schemas are recommended against the worst case of an untrusted schema should be a denial of service not execution of code publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact 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 ajv step up your open source security game with whitesource
| 0
|
83,782
| 15,720,725,506
|
IssuesEvent
|
2021-03-29 01:00:32
|
billmcchesney1/pacbot
|
https://api.github.com/repos/billmcchesney1/pacbot
|
opened
|
CVE-2021-24122 (Medium) detected in tomcat-embed-core-8.5.32.jar
|
security vulnerability
|
## CVE-2021-24122 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tomcat-embed-core-8.5.32.jar</b></p></summary>
<p>Core Tomcat implementation</p>
<p>Library home page: <a href="http://tomcat.apache.org/">http://tomcat.apache.org/</a></p>
<p>Path to dependency file: pacbot/api/pacman-api-admin/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar</p>
<p>
Dependency Hierarchy:
- spring-cloud-config-server-2.0.0.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.0.4.RELEASE.jar
- spring-boot-starter-tomcat-2.0.4.RELEASE.jar
- :x: **tomcat-embed-core-8.5.32.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
When serving resources from a network location using the NTFS file system, Apache Tomcat versions 10.0.0-M1 to 10.0.0-M9, 9.0.0.M1 to 9.0.39, 8.5.0 to 8.5.59 and 7.0.0 to 7.0.106 were susceptible to JSP source code disclosure in some configurations. The root cause was the unexpected behaviour of the JRE API File.getCanonicalPath() which in turn was caused by the inconsistent behaviour of the Windows API (FindFirstFileW) in some circumstances.
<p>Publish Date: 2021-01-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-24122>CVE-2021-24122</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.9</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-24122">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-24122</a></p>
<p>Release Date: 2021-01-14</p>
<p>Fix Resolution: org.apache.tomcat.embed:tomcat-embed-core:7.0.107,8.5.60,9.0.40,10.0.0-M10;org.apache.tomcat:tomcat-catalina:7.0.107,8.5.60,9.0.40,10.0.0-M10</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.apache.tomcat.embed","packageName":"tomcat-embed-core","packageVersion":"8.5.32","packageFilePaths":["/api/pacman-api-admin/pom.xml","/api/pacman-api-asset/pom.xml","/api/pacman-api-auth/pom.xml","/commons/pac-api-commons/pom.xml","/api/pacman-api-config/pom.xml","/api/pacman-api-statistics/pom.xml","/api/pacman-api-notifications/pom.xml","/api/pacman-api-compliance/pom.xml","/api/pacman-api-vulnerability/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"org.springframework.cloud:spring-cloud-config-server:2.0.0.RELEASE;org.springframework.boot:spring-boot-starter-web:2.0.4.RELEASE;org.springframework.boot:spring-boot-starter-tomcat:2.0.4.RELEASE;org.apache.tomcat.embed:tomcat-embed-core:8.5.32","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.apache.tomcat.embed:tomcat-embed-core:7.0.107,8.5.60,9.0.40,10.0.0-M10;org.apache.tomcat:tomcat-catalina:7.0.107,8.5.60,9.0.40,10.0.0-M10"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-24122","vulnerabilityDetails":"When serving resources from a network location using the NTFS file system, Apache Tomcat versions 10.0.0-M1 to 10.0.0-M9, 9.0.0.M1 to 9.0.39, 8.5.0 to 8.5.59 and 7.0.0 to 7.0.106 were susceptible to JSP source code disclosure in some configurations. The root cause was the unexpected behaviour of the JRE API File.getCanonicalPath() which in turn was caused by the inconsistent behaviour of the Windows API (FindFirstFileW) in some circumstances.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-24122","cvss3Severity":"medium","cvss3Score":"5.9","cvss3Metrics":{"A":"None","AC":"High","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> -->
|
True
|
CVE-2021-24122 (Medium) detected in tomcat-embed-core-8.5.32.jar - ## CVE-2021-24122 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tomcat-embed-core-8.5.32.jar</b></p></summary>
<p>Core Tomcat implementation</p>
<p>Library home page: <a href="http://tomcat.apache.org/">http://tomcat.apache.org/</a></p>
<p>Path to dependency file: pacbot/api/pacman-api-admin/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar,/home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.32/tomcat-embed-core-8.5.32.jar</p>
<p>
Dependency Hierarchy:
- spring-cloud-config-server-2.0.0.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.0.4.RELEASE.jar
- spring-boot-starter-tomcat-2.0.4.RELEASE.jar
- :x: **tomcat-embed-core-8.5.32.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
When serving resources from a network location using the NTFS file system, Apache Tomcat versions 10.0.0-M1 to 10.0.0-M9, 9.0.0.M1 to 9.0.39, 8.5.0 to 8.5.59 and 7.0.0 to 7.0.106 were susceptible to JSP source code disclosure in some configurations. The root cause was the unexpected behaviour of the JRE API File.getCanonicalPath() which in turn was caused by the inconsistent behaviour of the Windows API (FindFirstFileW) in some circumstances.
<p>Publish Date: 2021-01-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-24122>CVE-2021-24122</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.9</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-24122">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-24122</a></p>
<p>Release Date: 2021-01-14</p>
<p>Fix Resolution: org.apache.tomcat.embed:tomcat-embed-core:7.0.107,8.5.60,9.0.40,10.0.0-M10;org.apache.tomcat:tomcat-catalina:7.0.107,8.5.60,9.0.40,10.0.0-M10</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.apache.tomcat.embed","packageName":"tomcat-embed-core","packageVersion":"8.5.32","packageFilePaths":["/api/pacman-api-admin/pom.xml","/api/pacman-api-asset/pom.xml","/api/pacman-api-auth/pom.xml","/commons/pac-api-commons/pom.xml","/api/pacman-api-config/pom.xml","/api/pacman-api-statistics/pom.xml","/api/pacman-api-notifications/pom.xml","/api/pacman-api-compliance/pom.xml","/api/pacman-api-vulnerability/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"org.springframework.cloud:spring-cloud-config-server:2.0.0.RELEASE;org.springframework.boot:spring-boot-starter-web:2.0.4.RELEASE;org.springframework.boot:spring-boot-starter-tomcat:2.0.4.RELEASE;org.apache.tomcat.embed:tomcat-embed-core:8.5.32","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.apache.tomcat.embed:tomcat-embed-core:7.0.107,8.5.60,9.0.40,10.0.0-M10;org.apache.tomcat:tomcat-catalina:7.0.107,8.5.60,9.0.40,10.0.0-M10"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-24122","vulnerabilityDetails":"When serving resources from a network location using the NTFS file system, Apache Tomcat versions 10.0.0-M1 to 10.0.0-M9, 9.0.0.M1 to 9.0.39, 8.5.0 to 8.5.59 and 7.0.0 to 7.0.106 were susceptible to JSP source code disclosure in some configurations. The root cause was the unexpected behaviour of the JRE API File.getCanonicalPath() which in turn was caused by the inconsistent behaviour of the Windows API (FindFirstFileW) in some circumstances.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-24122","cvss3Severity":"medium","cvss3Score":"5.9","cvss3Metrics":{"A":"None","AC":"High","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> -->
|
non_test
|
cve medium detected in tomcat embed core jar cve medium severity vulnerability vulnerable library tomcat embed core jar core tomcat implementation library home page a href path to dependency file pacbot api pacman api admin pom xml path to vulnerable library home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar dependency hierarchy spring cloud config server release jar root library spring boot starter web release jar spring boot starter tomcat release jar x tomcat embed core jar vulnerable library found in base branch master vulnerability details when serving resources from a network location using the ntfs file system apache tomcat versions to to to and to were susceptible to jsp source code disclosure in some configurations the root cause was the unexpected behaviour of the jre api file getcanonicalpath which in turn was caused by the inconsistent behaviour of the windows api findfirstfilew in some circumstances publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org apache tomcat embed tomcat embed core org apache tomcat tomcat catalina isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree org springframework cloud spring cloud config server release org springframework boot spring boot starter web release org springframework boot spring boot starter tomcat release org apache tomcat embed tomcat embed core isminimumfixversionavailable true minimumfixversion org apache tomcat embed tomcat embed core org apache tomcat tomcat catalina basebranches vulnerabilityidentifier cve vulnerabilitydetails when serving resources from a network location using the ntfs file system apache tomcat versions to to to and to were susceptible to jsp source code disclosure in some configurations the root cause was the unexpected behaviour of the jre api file getcanonicalpath which in turn was caused by the inconsistent behaviour of the windows api findfirstfilew in some circumstances vulnerabilityurl
| 0
|
190,590
| 14,563,316,556
|
IssuesEvent
|
2020-12-17 02:13:08
|
microsoft/AzureStorageExplorer
|
https://api.github.com/repos/microsoft/AzureStorageExplorer
|
closed
|
The rename activity log is not completed after the rename action is successfully
|
:beetle: regression :gear: blobs 🧪 testing
|
**Storage Explorer Version:** 1.17.0
**Build Number:** 20201216.1
**Branch:** main
**Platform/OS:** Windows 10/ Linux Ubuntu 16.04/ MacOS Catalina
**Architecture:** ia32/x64
**Regression From:** Previous release (1.17.0)
## Steps to Reproduce ##
1. Expand one ADLS Gen2 storage account -> Blob Containers.
2. Create a blob container -> Upload one blob.
3. Rename the blob with a valid name.
4. Check whether the rename activity log is completed in Activities after the renamed blob shows in the editor.
## Expected Experience ##
The rename activity log is completed.
## Actual Experience ##
The rename activity log is not completed.
|
1.0
|
The rename activity log is not completed after the rename action is successfully - **Storage Explorer Version:** 1.17.0
**Build Number:** 20201216.1
**Branch:** main
**Platform/OS:** Windows 10/ Linux Ubuntu 16.04/ MacOS Catalina
**Architecture:** ia32/x64
**Regression From:** Previous release (1.17.0)
## Steps to Reproduce ##
1. Expand one ADLS Gen2 storage account -> Blob Containers.
2. Create a blob container -> Upload one blob.
3. Rename the blob with a valid name.
4. Check whether the rename activity log is completed in Activities after the renamed blob shows in the editor.
## Expected Experience ##
The rename activity log is completed.
## Actual Experience ##
The rename activity log is not completed.
|
test
|
the rename activity log is not completed after the rename action is successfully storage explorer version build number branch main platform os windows linux ubuntu macos catalina architecture regression from previous release steps to reproduce expand one adls storage account blob containers create a blob container upload one blob rename the blob with a valid name check whether the rename activity log is completed in activities after the renamed blob shows in the editor expected experience the rename activity log is completed actual experience the rename activity log is not completed
| 1
|
73,849
| 24,831,942,288
|
IssuesEvent
|
2022-10-26 04:53:24
|
SAP/fundamental-ngx
|
https://api.github.com/repos/SAP/fundamental-ngx
|
closed
|
Defect Hunting: List issue
|
bug core Defect Hunting quick fix
|
#### Is this a bug, enhancement, or feature request?
bug
#### Briefly describe your proposal.
- [x] List item with navigation is not clickable via space/enter keys
- [x] List headers should not receive focus
Screen Shot 2022-07-11 at 2.58.15 PM
From the fiori design guidelines:
<img width="591" alt="Screen Shot 2022-07-11 at 2 58 09 PM" src="https://user-images.githubusercontent.com/2471874/178357083-5743a370-2018-4c30-a359-e28b701b495d.png">
|
1.0
|
Defect Hunting: List issue - #### Is this a bug, enhancement, or feature request?
bug
#### Briefly describe your proposal.
- [x] List item with navigation is not clickable via space/enter keys
- [x] List headers should not receive focus
Screen Shot 2022-07-11 at 2.58.15 PM
From the fiori design guidelines:
<img width="591" alt="Screen Shot 2022-07-11 at 2 58 09 PM" src="https://user-images.githubusercontent.com/2471874/178357083-5743a370-2018-4c30-a359-e28b701b495d.png">
|
non_test
|
defect hunting list issue is this a bug enhancement or feature request bug briefly describe your proposal list item with navigation is not clickable via space enter keys list headers should not receive focus screen shot at pm from the fiori design guidelines img width alt screen shot at pm src
| 0
|
272,818
| 23,705,651,874
|
IssuesEvent
|
2022-08-30 00:37:55
|
PathmindAI/nativerl
|
https://api.github.com/repos/PathmindAI/nativerl
|
closed
|
Add checks for expected metrics levels
|
tests
|
so we can make sure issues like #441 and https://github.com/SkymindIO/nativerl/pull/499 don't regress
this specific test would go in test_training.py, and test a multi agent model like multi mouse and cheese. it might be tough though since the metric is either one or zero
|
1.0
|
Add checks for expected metrics levels - so we can make sure issues like #441 and https://github.com/SkymindIO/nativerl/pull/499 don't regress
this specific test would go in test_training.py, and test a multi agent model like multi mouse and cheese. it might be tough though since the metric is either one or zero
|
test
|
add checks for expected metrics levels so we can make sure issues like and don t regress this specific test would go in test training py and test a multi agent model like multi mouse and cheese it might be tough though since the metric is either one or zero
| 1
|
264,649
| 20,027,230,862
|
IssuesEvent
|
2022-02-01 22:56:43
|
Schots/mlops_project
|
https://api.github.com/repos/Schots/mlops_project
|
closed
|
Update README
|
documentation good first issue
|
A pre-commit section should be created with some figures to clarify the flow of commiting to this project. @bobcastaldeli
|
1.0
|
Update README - A pre-commit section should be created with some figures to clarify the flow of commiting to this project. @bobcastaldeli
|
non_test
|
update readme a pre commit section should be created with some figures to clarify the flow of commiting to this project bobcastaldeli
| 0
|
118,346
| 9,983,467,370
|
IssuesEvent
|
2019-07-10 12:29:57
|
mozilla-mobile/android-components
|
https://api.github.com/repos/mozilla-mobile/android-components
|
opened
|
Experiment and prototype cross-browser test suite
|
✅ testing 🔬 Research
|
As part of the following project we want to explore shipping a cross-browser test suite living in the AC repository:
https://github.com/orgs/mozilla-mobile/projects/39
This issue is about exploring solutions to that problem and prototyping some ideas.
|
1.0
|
Experiment and prototype cross-browser test suite - As part of the following project we want to explore shipping a cross-browser test suite living in the AC repository:
https://github.com/orgs/mozilla-mobile/projects/39
This issue is about exploring solutions to that problem and prototyping some ideas.
|
test
|
experiment and prototype cross browser test suite as part of the following project we want to explore shipping a cross browser test suite living in the ac repository this issue is about exploring solutions to that problem and prototyping some ideas
| 1
|
204,024
| 15,398,032,175
|
IssuesEvent
|
2021-03-03 23:12:00
|
elastic/elasticsearch
|
https://api.github.com/repos/elastic/elasticsearch
|
closed
|
[CI] IndicesClientIT.testGetAlias failed in 7.0
|
:Core/Features/Features >test-failure Team:Core/Features
|
This failed once today : https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+7.0+intake/414/consoleText
```
FAILURE 0.39s | IndicesClientIT.testGetAlias <<< FAILURES!
> Throwable #1: java.lang.AssertionError:
> Expected: <3>
> but: was <4>
> at __randomizedtesting.SeedInfo.seed([7D6ACC21848938CE:4EF959EF7D88BE75]:0)
> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
> at org.elasticsearch.client.IndicesClientIT.testGetAlias(IndicesClientIT.java:1264)
> at java.lang.Thread.run(Thread.java:748)
```
and I could see
```
[2019-03-14T13:57:11,944][ERROR][o.e.x.w.Watcher ] [node-0] triggered watches could not be deleted [my_watch_id_997cf558-4b75-4e08-a017-914ac49931a1-2019-03-14T13:57:11.806Z], failure [[.triggered_watches] IndexNotFoundException[no such index [.triggered_watches]]]
... SKIPPED 53 LINES ...
[2019-03-14T13:57:13,183][ERROR][o.e.x.w.Watcher ] [node-0] triggered watches could not be deleted [my_watch_id_0faecf2d-31ed-45b6-a391-78d48c41d51f-2019-03-14T13:57:13.085Z], failure [[.triggered_watches] IndexNotFoundException[no such index [.triggered_watches]]]
[2019-03-14T13:57:13,205][ERROR][o.e.x.w.Watcher ] [node-0] triggered watches could not be deleted [my_watch_id_96c39ff3-7197-4fb1-8413-33653344626f-2019-03-14T13:57:13.203Z], failure [[.triggered_watches] IndexNotFoundException[no such index [.triggered_watches]]]
... SKIPPED 1831 LINES ...
[2019-03-14T13:57:44,866][ERROR][o.e.x.m.j.p.a.w.JsonDataToProcessWriter] [node-0] Cannot parse timestamp '' as epoch value
[2019-03-14T13:57:44,866][ERROR][o.e.x.m.j.p.a.w.JsonDataToProcessWriter] [node-0] Cannot parse timestamp '' as epoch value
[2019-03-14T13:57:44,877][ERROR][o.e.x.m.j.p.a.w.JsonDataToProcessWriter] [node-0] Cannot parse timestamp '' as epoch value
... SKIPPED 292 LINES ...
[2019-03-14T13:57:53,099][WARN ][o.e.x.m.d.DatafeedManager] [node-0] [start-datafeed-job] Datafeed lookback retrieved no data
... SKIPPED 605 LINES ...
```
but I'm not entirely sure whether this is related. The
```
./gradlew :client:rest-high-level:integTestRunner \
-Dtests.seed=7D6ACC21848938CE \
-Dtests.class=org.elasticsearch.client.IndicesClientIT \
-Dtests.method="testGetAlias" \
-Dtests.security.manager=true \
-Dtests.locale=es-DO \
-Dtests.timezone=America/Montreal \
-Dcompiler.java=11 \
-Druntime.java=8
```
does not reproduce locally. I'm not muting this since it has failed only once before ( March 8 : https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.6+multijob-unix-compatibility/os=ubuntu-16.04&&immutable/159/console )
|
1.0
|
[CI] IndicesClientIT.testGetAlias failed in 7.0 - This failed once today : https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+7.0+intake/414/consoleText
```
FAILURE 0.39s | IndicesClientIT.testGetAlias <<< FAILURES!
> Throwable #1: java.lang.AssertionError:
> Expected: <3>
> but: was <4>
> at __randomizedtesting.SeedInfo.seed([7D6ACC21848938CE:4EF959EF7D88BE75]:0)
> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
> at org.elasticsearch.client.IndicesClientIT.testGetAlias(IndicesClientIT.java:1264)
> at java.lang.Thread.run(Thread.java:748)
```
and I could see
```
[2019-03-14T13:57:11,944][ERROR][o.e.x.w.Watcher ] [node-0] triggered watches could not be deleted [my_watch_id_997cf558-4b75-4e08-a017-914ac49931a1-2019-03-14T13:57:11.806Z], failure [[.triggered_watches] IndexNotFoundException[no such index [.triggered_watches]]]
... SKIPPED 53 LINES ...
[2019-03-14T13:57:13,183][ERROR][o.e.x.w.Watcher ] [node-0] triggered watches could not be deleted [my_watch_id_0faecf2d-31ed-45b6-a391-78d48c41d51f-2019-03-14T13:57:13.085Z], failure [[.triggered_watches] IndexNotFoundException[no such index [.triggered_watches]]]
[2019-03-14T13:57:13,205][ERROR][o.e.x.w.Watcher ] [node-0] triggered watches could not be deleted [my_watch_id_96c39ff3-7197-4fb1-8413-33653344626f-2019-03-14T13:57:13.203Z], failure [[.triggered_watches] IndexNotFoundException[no such index [.triggered_watches]]]
... SKIPPED 1831 LINES ...
[2019-03-14T13:57:44,866][ERROR][o.e.x.m.j.p.a.w.JsonDataToProcessWriter] [node-0] Cannot parse timestamp '' as epoch value
[2019-03-14T13:57:44,866][ERROR][o.e.x.m.j.p.a.w.JsonDataToProcessWriter] [node-0] Cannot parse timestamp '' as epoch value
[2019-03-14T13:57:44,877][ERROR][o.e.x.m.j.p.a.w.JsonDataToProcessWriter] [node-0] Cannot parse timestamp '' as epoch value
... SKIPPED 292 LINES ...
[2019-03-14T13:57:53,099][WARN ][o.e.x.m.d.DatafeedManager] [node-0] [start-datafeed-job] Datafeed lookback retrieved no data
... SKIPPED 605 LINES ...
```
but I'm not entirely sure whether this is related. The
```
./gradlew :client:rest-high-level:integTestRunner \
-Dtests.seed=7D6ACC21848938CE \
-Dtests.class=org.elasticsearch.client.IndicesClientIT \
-Dtests.method="testGetAlias" \
-Dtests.security.manager=true \
-Dtests.locale=es-DO \
-Dtests.timezone=America/Montreal \
-Dcompiler.java=11 \
-Druntime.java=8
```
does not reproduce locally. I'm not muting this since it has failed only once before ( March 8 : https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.6+multijob-unix-compatibility/os=ubuntu-16.04&&immutable/159/console )
|
test
|
indicesclientit testgetalias failed in this failed once today failure indicesclientit testgetalias failures throwable java lang assertionerror expected but was at randomizedtesting seedinfo seed at org hamcrest matcherassert assertthat matcherassert java at org elasticsearch client indicesclientit testgetalias indicesclientit java at java lang thread run thread java and i could see triggered watches could not be deleted failure indexnotfoundexception skipped lines triggered watches could not be deleted failure indexnotfoundexception triggered watches could not be deleted failure indexnotfoundexception skipped lines cannot parse timestamp as epoch value cannot parse timestamp as epoch value cannot parse timestamp as epoch value skipped lines datafeed lookback retrieved no data skipped lines but i m not entirely sure whether this is related the gradlew client rest high level integtestrunner dtests seed dtests class org elasticsearch client indicesclientit dtests method testgetalias dtests security manager true dtests locale es do dtests timezone america montreal dcompiler java druntime java does not reproduce locally i m not muting this since it has failed only once before march
| 1
|
297,889
| 25,770,230,896
|
IssuesEvent
|
2022-12-09 07:13:21
|
red/red
|
https://api.github.com/repos/red/red
|
closed
|
[View] draw crashes Red if <bg> is used with rtd-layout
|
status.built status.tested type.bug GUI
|
**Describe the bug**
`draw` crashes Red if `<bg>` is used with `rtd-layout`
**To reproduce**
`draw size-text r: rtd-layout [<bg> 255.0.0 "a" </bg> ] compose [text 0x0 (r)]`
**Expected behavior**
No crash.
**Platform version**
```
>> about
Red 0.6.4 for Windows built 26-Nov-2022/15:40:58+01:00 commit #94beb4d
```
|
1.0
|
[View] draw crashes Red if <bg> is used with rtd-layout - **Describe the bug**
`draw` crashes Red if `<bg>` is used with `rtd-layout`
**To reproduce**
`draw size-text r: rtd-layout [<bg> 255.0.0 "a" </bg> ] compose [text 0x0 (r)]`
**Expected behavior**
No crash.
**Platform version**
```
>> about
Red 0.6.4 for Windows built 26-Nov-2022/15:40:58+01:00 commit #94beb4d
```
|
test
|
draw crashes red if is used with rtd layout describe the bug draw crashes red if is used with rtd layout to reproduce draw size text r rtd layout compose expected behavior no crash platform version about red for windows built nov commit
| 1
|
2,183
| 2,700,954,093
|
IssuesEvent
|
2015-04-04 19:09:05
|
CMPUT301W15T13/TravelPlanner
|
https://api.github.com/repos/CMPUT301W15T13/TravelPlanner
|
closed
|
07.02.01
|
Code
|
As a claimant, I want a visual warning when trying to submit an expense claim when there are fields with missing values or there are any incompleteness indicators on the expense items.
|
1.0
|
07.02.01 - As a claimant, I want a visual warning when trying to submit an expense claim when there are fields with missing values or there are any incompleteness indicators on the expense items.
|
non_test
|
as a claimant i want a visual warning when trying to submit an expense claim when there are fields with missing values or there are any incompleteness indicators on the expense items
| 0
|
309,954
| 9,483,442,484
|
IssuesEvent
|
2019-04-22 00:18:35
|
minishift/minishift
|
https://api.github.com/repos/minishift/minishift
|
closed
|
Che addon: add support for multi user Che
|
kind/feature priority/major status/stale
|
### General information
Che minishift addon currently supports only [Che single user](https://www.eclipse.org/che/docs/openshift-single-user.html). We want to add support for [Che multi user](https://www.eclipse.org/che/docs/openshift-multi-user.html) too.
This issue is part of the discussion we are having with Che community to drop Che single user support at all (c.f. https://github.com/eclipse/che/issues/10996). Anyway this issue is not about dropping the support for single user but adding an option to run Che multi user.
C.f. rh-che (multi user) minishift addon https://github.com/redhat-developer/rh-che/tree/master/openshift/minishift-addons
|
1.0
|
Che addon: add support for multi user Che - ### General information
Che minishift addon currently supports only [Che single user](https://www.eclipse.org/che/docs/openshift-single-user.html). We want to add support for [Che multi user](https://www.eclipse.org/che/docs/openshift-multi-user.html) too.
This issue is part of the discussion we are having with Che community to drop Che single user support at all (c.f. https://github.com/eclipse/che/issues/10996). Anyway this issue is not about dropping the support for single user but adding an option to run Che multi user.
C.f. rh-che (multi user) minishift addon https://github.com/redhat-developer/rh-che/tree/master/openshift/minishift-addons
|
non_test
|
che addon add support for multi user che general information che minishift addon currently supports only we want to add support for too this issue is part of the discussion we are having with che community to drop che single user support at all c f anyway this issue is not about dropping the support for single user but adding an option to run che multi user c f rh che multi user minishift addon
| 0
|
8,372
| 2,611,494,932
|
IssuesEvent
|
2015-02-27 05:34:47
|
chrsmith/hedgewars
|
https://api.github.com/repos/chrsmith/hedgewars
|
closed
|
Drawn map canvas and alt-tab impression
|
auto-migrated Priority-Medium Type-Defect
|
```
What steps will reproduce the problem?
Steps need to be done 1 by one if you will avoid any or already done all of
them you have to run again hedgewars to try reproducing the issue.
1. Open hedgewars go straight to multiplayer.
2. Choose handdrawn map and click on map to draw.
3. Draw something.
4. change position of hedgewars window then change to another window and again
change position of hedgewars window.
5. Repeat step 4 to see the results sometimes it happens sometimes not...
What is the expected output? What do you see instead?
See attached file
What version of the product are you using? On what operating system?
Ubuntu 11.10
Trunk
Please provide any additional information below.
```
Original issue reported on code.google.com by `dsa.wow....@gmail.com` on 1 Apr 2012 at 9:58
Attachments:
* [Error.png](https://storage.googleapis.com/google-code-attachments/hedgewars/issue-381/comment-0/Error.png)
|
1.0
|
Drawn map canvas and alt-tab impression - ```
What steps will reproduce the problem?
Steps need to be done 1 by one if you will avoid any or already done all of
them you have to run again hedgewars to try reproducing the issue.
1. Open hedgewars go straight to multiplayer.
2. Choose handdrawn map and click on map to draw.
3. Draw something.
4. change position of hedgewars window then change to another window and again
change position of hedgewars window.
5. Repeat step 4 to see the results sometimes it happens sometimes not...
What is the expected output? What do you see instead?
See attached file
What version of the product are you using? On what operating system?
Ubuntu 11.10
Trunk
Please provide any additional information below.
```
Original issue reported on code.google.com by `dsa.wow....@gmail.com` on 1 Apr 2012 at 9:58
Attachments:
* [Error.png](https://storage.googleapis.com/google-code-attachments/hedgewars/issue-381/comment-0/Error.png)
|
non_test
|
drawn map canvas and alt tab impression what steps will reproduce the problem steps need to be done by one if you will avoid any or already done all of them you have to run again hedgewars to try reproducing the issue open hedgewars go straight to multiplayer choose handdrawn map and click on map to draw draw something change position of hedgewars window then change to another window and again change position of hedgewars window repeat step to see the results sometimes it happens sometimes not what is the expected output what do you see instead see attached file what version of the product are you using on what operating system ubuntu trunk please provide any additional information below original issue reported on code google com by dsa wow gmail com on apr at attachments
| 0
|
150,791
| 11,984,871,118
|
IssuesEvent
|
2020-04-07 16:31:49
|
phetsims/number-line-integers
|
https://api.github.com/repos/phetsims/number-line-integers
|
closed
|
CT Licenses for media types
|
type:automated-testing
|
Also in Operations
```
number-line-integers : build : phet
Failure to grunt snapshot-1586137274058/number-line-integers:
Running "lint-all" task
Running "report-media" task
>> not-annotated: number-line-common/images/piggy-bank-with-flowers.png
>> not-annotated: number-line-common/images/piggy-bank-with-lightning.png
Fatal error: There is an issue with the licenses for media types.
Approximately 4/5/2020, 7:41:14 PM
```
|
1.0
|
CT Licenses for media types - Also in Operations
```
number-line-integers : build : phet
Failure to grunt snapshot-1586137274058/number-line-integers:
Running "lint-all" task
Running "report-media" task
>> not-annotated: number-line-common/images/piggy-bank-with-flowers.png
>> not-annotated: number-line-common/images/piggy-bank-with-lightning.png
Fatal error: There is an issue with the licenses for media types.
Approximately 4/5/2020, 7:41:14 PM
```
|
test
|
ct licenses for media types also in operations number line integers build phet failure to grunt snapshot number line integers running lint all task running report media task not annotated number line common images piggy bank with flowers png not annotated number line common images piggy bank with lightning png fatal error there is an issue with the licenses for media types approximately pm
| 1
|
51,755
| 6,196,148,908
|
IssuesEvent
|
2017-07-05 14:11:32
|
MTG/freesound
|
https://api.github.com/repos/MTG/freesound
|
closed
|
User search in admin is slow again
|
Testing
|
In https://github.com/MTG/freesound/issues/656 we made some improvements to user search to be able to search by name or email.
This operation is getting slower again, and we've also had reports of timeouts when we just show the user list (50 users + pager).
To speed up search, we should look at removing the option of wildcard search and just go for exact matches. To speed up the list, see if the bottleneck is in the query to get the user data, or to get the information for the pager.
|
1.0
|
User search in admin is slow again - In https://github.com/MTG/freesound/issues/656 we made some improvements to user search to be able to search by name or email.
This operation is getting slower again, and we've also had reports of timeouts when we just show the user list (50 users + pager).
To speed up search, we should look at removing the option of wildcard search and just go for exact matches. To speed up the list, see if the bottleneck is in the query to get the user data, or to get the information for the pager.
|
test
|
user search in admin is slow again in we made some improvements to user search to be able to search by name or email this operation is getting slower again and we ve also had reports of timeouts when we just show the user list users pager to speed up search we should look at removing the option of wildcard search and just go for exact matches to speed up the list see if the bottleneck is in the query to get the user data or to get the information for the pager
| 1
|
22,616
| 6,275,093,697
|
IssuesEvent
|
2017-07-18 05:25:38
|
oppia/oppia
|
https://api.github.com/repos/oppia/oppia
|
closed
|
Abstracting training of classifier away from learner view
|
loc: backend owner: @anmolshkl TODO: code type: feature (important)
|
Current scenario: The training of the classifier is presently done when the first request for prediction is handled by the ClassifyHandler. So, the training of the classifier depends on the first learner who submits an answer to some state in an exploration.
This behavior is not very effective as the training could technically be done right when we save an exploration.
Expected behavior: We would like to move the training part into a function which could be called when the exploration is saved. So, the classifier is trained when an exploration is created and the training would be triggered by the creator. This, in turn, makes sure that the ClassifyHandler handles only predictions and the not training (which is what we would like)
CC @anmolshkl (One query: The save_exploration() method is sort of called every time an update is made too right? So, keeping training in there would be counter-productive since we would re train every time the creator makes any change to the exploration. Could we keep training inside create_exploration() method?
Yet again, the re-training under save_exploration() could help us when we actually need to re-train - based on our discussions for threshold of retraining in the doc. So, this is an option as well.)
|
1.0
|
Abstracting training of classifier away from learner view - Current scenario: The training of the classifier is presently done when the first request for prediction is handled by the ClassifyHandler. So, the training of the classifier depends on the first learner who submits an answer to some state in an exploration.
This behavior is not very effective as the training could technically be done right when we save an exploration.
Expected behavior: We would like to move the training part into a function which could be called when the exploration is saved. So, the classifier is trained when an exploration is created and the training would be triggered by the creator. This, in turn, makes sure that the ClassifyHandler handles only predictions and the not training (which is what we would like)
CC @anmolshkl (One query: The save_exploration() method is sort of called every time an update is made too right? So, keeping training in there would be counter-productive since we would re train every time the creator makes any change to the exploration. Could we keep training inside create_exploration() method?
Yet again, the re-training under save_exploration() could help us when we actually need to re-train - based on our discussions for threshold of retraining in the doc. So, this is an option as well.)
|
non_test
|
abstracting training of classifier away from learner view current scenario the training of the classifier is presently done when the first request for prediction is handled by the classifyhandler so the training of the classifier depends on the first learner who submits an answer to some state in an exploration this behavior is not very effective as the training could technically be done right when we save an exploration expected behavior we would like to move the training part into a function which could be called when the exploration is saved so the classifier is trained when an exploration is created and the training would be triggered by the creator this in turn makes sure that the classifyhandler handles only predictions and the not training which is what we would like cc anmolshkl one query the save exploration method is sort of called every time an update is made too right so keeping training in there would be counter productive since we would re train every time the creator makes any change to the exploration could we keep training inside create exploration method yet again the re training under save exploration could help us when we actually need to re train based on our discussions for threshold of retraining in the doc so this is an option as well
| 0
|
57,321
| 24,098,982,932
|
IssuesEvent
|
2022-09-19 21:43:25
|
elastic/kibana
|
https://api.github.com/repos/elastic/kibana
|
closed
|
Unsetting a field format is not possible
|
bug Team:AppServicesSv duplicate impact:medium
|
**Kibana version:** 8.3.3
**Elasticsearch version:** 8.3.3
**Server OS version:** Linux
**Browser version:** Chrome 104
**Browser OS version:** macOS
**Original install method (e.g. download page, yum, from source, etc.):** Docker image
**Describe the bug:**
When I set a specific format for a field in a data view, I can no longer unset it. It always resets to the previously chosen format.
**Steps to reproduce:**
1. Select a format for field in a data view, e.g. Bytes
2. Save it
3. Turn off the format
4. Save it
5. Refresh the page
6. Notice that the format stays at the previously selected one
**Expected behavior:**
The format should return to being unset.
**Screenshots (if relevant):**
Before unsetting it, I had explicitly changed this field to be a Number:
I then unset it here:
<img width="566" alt="image" src="https://user-images.githubusercontent.com/582444/185087638-85e9c29d-17fb-42d8-a7ce-f9259a36bc2d.png">
Then I save it, and it looks like being saved:
But when I refresh the page, the format is still set as Number.
|
1.0
|
Unsetting a field format is not possible - **Kibana version:** 8.3.3
**Elasticsearch version:** 8.3.3
**Server OS version:** Linux
**Browser version:** Chrome 104
**Browser OS version:** macOS
**Original install method (e.g. download page, yum, from source, etc.):** Docker image
**Describe the bug:**
When I set a specific format for a field in a data view, I can no longer unset it. It always resets to the previously chosen format.
**Steps to reproduce:**
1. Select a format for field in a data view, e.g. Bytes
2. Save it
3. Turn off the format
4. Save it
5. Refresh the page
6. Notice that the format stays at the previously selected one
**Expected behavior:**
The format should return to being unset.
**Screenshots (if relevant):**
Before unsetting it, I had explicitly changed this field to be a Number:
I then unset it here:
<img width="566" alt="image" src="https://user-images.githubusercontent.com/582444/185087638-85e9c29d-17fb-42d8-a7ce-f9259a36bc2d.png">
Then I save it, and it looks like being saved:
But when I refresh the page, the format is still set as Number.
|
non_test
|
unsetting a field format is not possible kibana version elasticsearch version server os version linux browser version chrome browser os version macos original install method e g download page yum from source etc docker image describe the bug when i set a specific format for a field in a data view i can no longer unset it it always resets to the previously chosen format steps to reproduce select a format for field in a data view e g bytes save it turn off the format save it refresh the page notice that the format stays at the previously selected one expected behavior the format should return to being unset screenshots if relevant before unsetting it i had explicitly changed this field to be a number i then unset it here img width alt image src then i save it and it looks like being saved but when i refresh the page the format is still set as number
| 0
|
692,662
| 23,745,020,999
|
IssuesEvent
|
2022-08-31 15:16:27
|
open-telemetry/opentelemetry-collector-contrib
|
https://api.github.com/repos/open-telemetry/opentelemetry-collector-contrib
|
closed
|
Support concurrent file storage extensions
|
priority:p2
|
**Is your feature request related to a problem? Please describe.**
The contrib has two storage extension implementations - [dbstorage](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/extension/storage/dbstorage) and [filestorage](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/extension/storage/filestorage), for which there are several use cases:
* [persistent buffering](https://github.com/open-telemetry/opentelemetry-collector/tree/main/exporter/exporterhelper#persistent-queue) in queued_retry (essentially any exporter)
* [filelog receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/filelogreceiver), which when storage extensions is enabled will automatically use it for persisting status of file tailing
Currently, only one instance of the storage extension can be used, which is limiting the flexibility to have separate config for each of the purposes. The limitation is likely to avoid referencing the storage ID and instead relying on using the only available one ([example](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/pkg/stanza/adapter/storage.go)) without the need to reference it, though it is also somewhat limiting
It was [brought during the review of enabling persistent queue capability](https://github.com/open-telemetry/opentelemetry-collector/pull/5457#discussion_r890268669) by default in the collector build. The proposal was to include additional property, where the specific instance could be references, e.g.
```yaml
storage: file_storage/foo
...
extensions:
file_storage/foo:
directory: foo
```
**Describe the solution you'd like**
~Deprecate the current automated attachment of file storage extension to filelog receiver and `persistent_storage_enabled` flag of queued_retry.~ Provide new configuration property `storage` which could be used to specify which file storage extension should be used when more than one is available.
The (draft) [implementation for enabling persistent queue](https://github.com/open-telemetry/opentelemetry-collector/pull/5457) addresses this change for queued_retry
|
1.0
|
Support concurrent file storage extensions - **Is your feature request related to a problem? Please describe.**
The contrib has two storage extension implementations - [dbstorage](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/extension/storage/dbstorage) and [filestorage](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/extension/storage/filestorage), for which there are several use cases:
* [persistent buffering](https://github.com/open-telemetry/opentelemetry-collector/tree/main/exporter/exporterhelper#persistent-queue) in queued_retry (essentially any exporter)
* [filelog receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/filelogreceiver), which when storage extensions is enabled will automatically use it for persisting status of file tailing
Currently, only one instance of the storage extension can be used, which is limiting the flexibility to have separate config for each of the purposes. The limitation is likely to avoid referencing the storage ID and instead relying on using the only available one ([example](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/pkg/stanza/adapter/storage.go)) without the need to reference it, though it is also somewhat limiting
It was [brought during the review of enabling persistent queue capability](https://github.com/open-telemetry/opentelemetry-collector/pull/5457#discussion_r890268669) by default in the collector build. The proposal was to include additional property, where the specific instance could be references, e.g.
```yaml
storage: file_storage/foo
...
extensions:
file_storage/foo:
directory: foo
```
**Describe the solution you'd like**
~Deprecate the current automated attachment of file storage extension to filelog receiver and `persistent_storage_enabled` flag of queued_retry.~ Provide new configuration property `storage` which could be used to specify which file storage extension should be used when more than one is available.
The (draft) [implementation for enabling persistent queue](https://github.com/open-telemetry/opentelemetry-collector/pull/5457) addresses this change for queued_retry
|
non_test
|
support concurrent file storage extensions is your feature request related to a problem please describe the contrib has two storage extension implementations and for which there are several use cases in queued retry essentially any exporter which when storage extensions is enabled will automatically use it for persisting status of file tailing currently only one instance of the storage extension can be used which is limiting the flexibility to have separate config for each of the purposes the limitation is likely to avoid referencing the storage id and instead relying on using the only available one without the need to reference it though it is also somewhat limiting it was by default in the collector build the proposal was to include additional property where the specific instance could be references e g yaml storage file storage foo extensions file storage foo directory foo describe the solution you d like deprecate the current automated attachment of file storage extension to filelog receiver and persistent storage enabled flag of queued retry provide new configuration property storage which could be used to specify which file storage extension should be used when more than one is available the draft addresses this change for queued retry
| 0
|
156,116
| 12,296,985,028
|
IssuesEvent
|
2020-05-11 08:02:03
|
input-output-hk/ouroboros-network
|
https://api.github.com/repos/input-output-hk/ouroboros-network
|
closed
|
Shelley: initial UTxO
|
consensus priority high shelley ledger integration shelley testnet
|
`protocolInfoShelley` still mentions a dummy `genesisUtxO`:
https://github.com/input-output-hk/ouroboros-network/blob/eec4a136bb51d882ab4cf4de552f1ce978459f56/ouroboros-consensus-shelley/src/Ouroboros/Consensus/Shelley/Node.hs#L251
We should define a proper initial UTxO.
|
1.0
|
Shelley: initial UTxO - `protocolInfoShelley` still mentions a dummy `genesisUtxO`:
https://github.com/input-output-hk/ouroboros-network/blob/eec4a136bb51d882ab4cf4de552f1ce978459f56/ouroboros-consensus-shelley/src/Ouroboros/Consensus/Shelley/Node.hs#L251
We should define a proper initial UTxO.
|
test
|
shelley initial utxo protocolinfoshelley still mentions a dummy genesisutxo we should define a proper initial utxo
| 1
|
26,326
| 19,988,465,116
|
IssuesEvent
|
2022-01-31 00:57:18
|
APSIMInitiative/ApsimX
|
https://api.github.com/repos/APSIMInitiative/ApsimX
|
closed
|
Ability to write to Summary in OnCompleted
|
bug interface/infrastructure
|
Relates to #6586 at end of conversation
https://github.com/APSIMInitiative/ApsimX/issues/6586#issuecomment-892269363
I would like to be able to trap errors generated while trying to create SQL queries in OnCompleted and present them in the Summary and keep going ignoring the bad sql and reporting all issues at the end. This is because I need to be assured that all reports have been created and written before creating SQL views that may include other report tables. Unfortunately, the summery cannot write in OnCompleted
I don't mind which approach suggested by @hol430 is used.
|
1.0
|
Ability to write to Summary in OnCompleted - Relates to #6586 at end of conversation
https://github.com/APSIMInitiative/ApsimX/issues/6586#issuecomment-892269363
I would like to be able to trap errors generated while trying to create SQL queries in OnCompleted and present them in the Summary and keep going ignoring the bad sql and reporting all issues at the end. This is because I need to be assured that all reports have been created and written before creating SQL views that may include other report tables. Unfortunately, the summery cannot write in OnCompleted
I don't mind which approach suggested by @hol430 is used.
|
non_test
|
ability to write to summary in oncompleted relates to at end of conversation i would like to be able to trap errors generated while trying to create sql queries in oncompleted and present them in the summary and keep going ignoring the bad sql and reporting all issues at the end this is because i need to be assured that all reports have been created and written before creating sql views that may include other report tables unfortunately the summery cannot write in oncompleted i don t mind which approach suggested by is used
| 0
|
63,568
| 14,656,739,726
|
IssuesEvent
|
2020-12-28 14:05:28
|
fu1771695yongxie/reselect
|
https://api.github.com/repos/fu1771695yongxie/reselect
|
opened
|
WS-2019-0332 (Medium) detected in handlebars-4.0.5.tgz
|
security vulnerability
|
## WS-2019-0332 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>handlebars-4.0.5.tgz</b></p></summary>
<p>Handlebars provides the power necessary to let you build semantic templates effectively with no frustration</p>
<p>Library home page: <a href="https://registry.npmjs.org/handlebars/-/handlebars-4.0.5.tgz">https://registry.npmjs.org/handlebars/-/handlebars-4.0.5.tgz</a></p>
<p>Path to dependency file: reselect/package.json</p>
<p>Path to vulnerable library: reselect/node_modules/nyc/node_modules/istanbul/node_modules/handlebars/package.json</p>
<p>
Dependency Hierarchy:
- nyc-6.6.1.tgz (Root Library)
- istanbul-0.4.3.tgz
- :x: **handlebars-4.0.5.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/fu1771695yongxie/reselect/commit/30a24d2b9329ca199f434fdf24bc4cbb57602f62">30a24d2b9329ca199f434fdf24bc4cbb57602f62</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>
Arbitrary Code Execution vulnerability found in handlebars before 4.5.3. Lookup helper fails to validate templates. Attack may submit templates that execute arbitrary JavaScript in the system.It is due to an incomplete fix for a WS-2019-0331.
<p>Publish Date: 2019-11-17
<p>URL: <a href=https://github.com/wycats/handlebars.js/commit/198887808780bbef9dba67a8af68ece091d5baa7>WS-2019-0332</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/1324">https://www.npmjs.com/advisories/1324</a></p>
<p>Release Date: 2019-12-05</p>
<p>Fix Resolution: handlebars - 4.5.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
WS-2019-0332 (Medium) detected in handlebars-4.0.5.tgz - ## WS-2019-0332 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>handlebars-4.0.5.tgz</b></p></summary>
<p>Handlebars provides the power necessary to let you build semantic templates effectively with no frustration</p>
<p>Library home page: <a href="https://registry.npmjs.org/handlebars/-/handlebars-4.0.5.tgz">https://registry.npmjs.org/handlebars/-/handlebars-4.0.5.tgz</a></p>
<p>Path to dependency file: reselect/package.json</p>
<p>Path to vulnerable library: reselect/node_modules/nyc/node_modules/istanbul/node_modules/handlebars/package.json</p>
<p>
Dependency Hierarchy:
- nyc-6.6.1.tgz (Root Library)
- istanbul-0.4.3.tgz
- :x: **handlebars-4.0.5.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/fu1771695yongxie/reselect/commit/30a24d2b9329ca199f434fdf24bc4cbb57602f62">30a24d2b9329ca199f434fdf24bc4cbb57602f62</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>
Arbitrary Code Execution vulnerability found in handlebars before 4.5.3. Lookup helper fails to validate templates. Attack may submit templates that execute arbitrary JavaScript in the system.It is due to an incomplete fix for a WS-2019-0331.
<p>Publish Date: 2019-11-17
<p>URL: <a href=https://github.com/wycats/handlebars.js/commit/198887808780bbef9dba67a8af68ece091d5baa7>WS-2019-0332</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/1324">https://www.npmjs.com/advisories/1324</a></p>
<p>Release Date: 2019-12-05</p>
<p>Fix Resolution: handlebars - 4.5.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_test
|
ws medium detected in handlebars tgz ws medium severity vulnerability vulnerable library handlebars tgz handlebars provides the power necessary to let you build semantic templates effectively with no frustration library home page a href path to dependency file reselect package json path to vulnerable library reselect node modules nyc node modules istanbul node modules handlebars package json dependency hierarchy nyc tgz root library istanbul tgz x handlebars tgz vulnerable library found in head commit a href found in base branch master vulnerability details arbitrary code execution vulnerability found in handlebars before lookup helper fails to validate templates attack may submit templates that execute arbitrary javascript in the system it is due to an incomplete fix for a ws publish date url a href cvss score details base score metrics not available suggested fix type upgrade version origin a href release date fix resolution handlebars step up your open source security game with whitesource
| 0
|
43,136
| 5,522,061,336
|
IssuesEvent
|
2017-03-19 20:30:26
|
BelayTechnologies/XesterUI
|
https://api.github.com/repos/BelayTechnologies/XesterUI
|
closed
|
Create Entry for target if a new item is detected during test
|
enhancement TestRun-Manager
|
Straight forward.
Get the Target name, see if it exists, if not, enter it with the type.
|
1.0
|
Create Entry for target if a new item is detected during test - Straight forward.
Get the Target name, see if it exists, if not, enter it with the type.
|
test
|
create entry for target if a new item is detected during test straight forward get the target name see if it exists if not enter it with the type
| 1
|
452,184
| 13,046,748,776
|
IssuesEvent
|
2020-07-29 09:30:44
|
mantidproject/mantid
|
https://api.github.com/repos/mantidproject/mantid
|
closed
|
SliceViewer cursor position
|
Diffraction Low Priority MantidPlot Stale Vates
|
This issue was originally [TRAC 6498](http://trac.mantidproject.org/mantid/ticket/6498)
It's not clear (at least for someone seeing SliceViewer for the first time) what coordinates are used in reporting of the cursor position.
|
1.0
|
SliceViewer cursor position - This issue was originally [TRAC 6498](http://trac.mantidproject.org/mantid/ticket/6498)
It's not clear (at least for someone seeing SliceViewer for the first time) what coordinates are used in reporting of the cursor position.
|
non_test
|
sliceviewer cursor position this issue was originally it s not clear at least for someone seeing sliceviewer for the first time what coordinates are used in reporting of the cursor position
| 0
|
297,049
| 25,596,020,898
|
IssuesEvent
|
2022-12-01 16:14:33
|
apache/beam
|
https://api.github.com/repos/apache/beam
|
closed
|
[Failing Test]: Local environment tests failing on GHA
|
python tests core P1 bug failing test permared
|
### What happened?
These tests are consistently failing - https://github.com/apache/beam/actions/workflows/local_env_tests.yml?query=branch%3Amaster
### Issue Failure
Failure: Test is continually failing
### Issue Priority
Priority: 1
### Issue Component
Component: sdk-py-core
|
2.0
|
[Failing Test]: Local environment tests failing on GHA - ### What happened?
These tests are consistently failing - https://github.com/apache/beam/actions/workflows/local_env_tests.yml?query=branch%3Amaster
### Issue Failure
Failure: Test is continually failing
### Issue Priority
Priority: 1
### Issue Component
Component: sdk-py-core
|
test
|
local environment tests failing on gha what happened these tests are consistently failing issue failure failure test is continually failing issue priority priority issue component component sdk py core
| 1
|
116,977
| 9,905,026,226
|
IssuesEvent
|
2019-06-27 10:31:36
|
cockroachdb/cockroach
|
https://api.github.com/repos/cockroachdb/cockroach
|
closed
|
teamcity: failed test: TestChangefeedNemeses
|
C-test-failure O-robot
|
The following tests appear to have failed on master (test): TestChangefeedNemeses, TestChangefeedNemeses/cloudstorage
You may want to check [for open issues](https://github.com/cockroachdb/cockroach/issues?q=is%3Aissue+is%3Aopen+TestChangefeedNemeses).
[#1362361](https://teamcity.cockroachdb.com/viewLog.html?buildId=1362361):
```
TestChangefeedNemeses/cloudstorage
... [async] kv.TxnCoordSender: heartbeat loop
1 [async] job-463805198821392385
1 [async] closedts-rangefeed-subscriber
1 [async] changefeed-poller
I190627 05:15:17.053422 93502 util/stop/stopper.go:542 quiescing; tasks left:
3 [async] rangefeed: output loop
2 [async] storage.IntentResolver: cleanup txn records
1 [async] kv.TxnCoordSender: heartbeat loop
1 [async] job-463805198821392385
1 [async] closedts-rangefeed-subscriber
1 [async] changefeed-poller
I190627 05:15:17.053462 93502 util/stop/stopper.go:542 quiescing; tasks left:
2 [async] storage.IntentResolver: cleanup txn records
2 [async] rangefeed: output loop
1 [async] kv.TxnCoordSender: heartbeat loop
1 [async] job-463805198821392385
1 [async] closedts-rangefeed-subscriber
1 [async] changefeed-poller
I190627 05:15:17.053497 93502 util/stop/stopper.go:542 quiescing; tasks left:
2 [async] rangefeed: output loop
1 [async] storage.IntentResolver: cleanup txn records
1 [async] kv.TxnCoordSender: heartbeat loop
1 [async] job-463805198821392385
1 [async] closedts-rangefeed-subscriber
1 [async] changefeed-poller
I190627 05:15:17.053528 93502 util/stop/stopper.go:542 quiescing; tasks left:
1 [async] storage.IntentResolver: cleanup txn records
1 [async] rangefeed: output loop
1 [async] kv.TxnCoordSender: heartbeat loop
1 [async] job-463805198821392385
1 [async] closedts-rangefeed-subscriber
1 [async] changefeed-poller
I190627 05:15:17.053589 93502 util/stop/stopper.go:542 quiescing; tasks left:
1 [async] rangefeed: output loop
1 [async] kv.TxnCoordSender: heartbeat loop
1 [async] job-463805198821392385
1 [async] closedts-rangefeed-subscriber
1 [async] changefeed-poller
I190627 05:15:17.053760 93502 util/stop/stopper.go:542 quiescing; tasks left:
1 [async] rangefeed: output loop
1 [async] job-463805198821392385
1 [async] closedts-rangefeed-subscriber
1 [async] changefeed-poller
I190627 05:15:17.053883 93502 util/stop/stopper.go:542 quiescing; tasks left:
1 [async] job-463805198821392385
1 [async] closedts-rangefeed-subscriber
1 [async] changefeed-poller
I190627 05:15:17.054037 93502 util/stop/stopper.go:542 quiescing; tasks left:
1 [async] job-463805198821392385
1 [async] changefeed-poller
E190627 05:15:17.054081 93677 jobs/registry.go:323 error while adopting jobs: adopt-job: node unavailable; try another peer
I190627 05:15:17.057715 93502 util/stop/stopper.go:542 quiescing; tasks left:
1 [async] job-463805198821392385
W190627 05:15:17.057852 94492 ccl/changefeedccl/changefeed_stmt.go:488 [n1] CHANGEFEED job 463805198821392385 returning with error: node unavailable; try another peer
fetching changes for /Table/{3-4}
-- safe details:
fetching changes for %s
-- arg 0: roachpb.Span
-- stack trace:
github.com/cockroachdb/cockroach/pkg/ccl/changefeedccl.fetchTableDescriptorVersions
/go/src/github.com/cockroachdb/cockroach/pkg/ccl/changefeedccl/table_history.go:246
github.com/cockroachdb/cockroach/pkg/ccl/changefeedccl.(*poller).updateTableHistory
/go/src/github.com/cockroachdb/cockroach/pkg/ccl/changefeedccl/poller.go:445
github.com/cockroachdb/cockroach/pkg/ccl/changefeedccl.(*poller).pollTableHistory
/go/src/github.com/cockroachdb/cockroach/pkg/ccl/changefeedccl/poller.go:454
github.com/cockroachdb/cockroach/pkg/util/ctxgroup.Group.GoCtx.func1
/go/src/github.com/cockroachdb/cockroach/pkg/util/ctxgroup/ctxgroup.go:166
github.com/cockroachdb/cockroach/vendor/golang.org/x/sync/errgroup.(*Group).Go.func1
/go/src/github.com/cockroachdb/cockroach/vendor/golang.org/x/sync/errgroup/errgroup.go:57
runtime.goexit
/usr/local/go/src/runtime/asm_amd64.s:1337
nemeses_test.go:32: topic foo partition : saw new row timestamp 1561612516455427509.0000000000 after 1561612516627081973.0000000000 was seen
TestChangefeedNemeses
--- FAIL: test/TestChangefeedNemeses (8.560s)
```
Please assign, take a look and update the issue accordingly.
|
1.0
|
teamcity: failed test: TestChangefeedNemeses - The following tests appear to have failed on master (test): TestChangefeedNemeses, TestChangefeedNemeses/cloudstorage
You may want to check [for open issues](https://github.com/cockroachdb/cockroach/issues?q=is%3Aissue+is%3Aopen+TestChangefeedNemeses).
[#1362361](https://teamcity.cockroachdb.com/viewLog.html?buildId=1362361):
```
TestChangefeedNemeses/cloudstorage
... [async] kv.TxnCoordSender: heartbeat loop
1 [async] job-463805198821392385
1 [async] closedts-rangefeed-subscriber
1 [async] changefeed-poller
I190627 05:15:17.053422 93502 util/stop/stopper.go:542 quiescing; tasks left:
3 [async] rangefeed: output loop
2 [async] storage.IntentResolver: cleanup txn records
1 [async] kv.TxnCoordSender: heartbeat loop
1 [async] job-463805198821392385
1 [async] closedts-rangefeed-subscriber
1 [async] changefeed-poller
I190627 05:15:17.053462 93502 util/stop/stopper.go:542 quiescing; tasks left:
2 [async] storage.IntentResolver: cleanup txn records
2 [async] rangefeed: output loop
1 [async] kv.TxnCoordSender: heartbeat loop
1 [async] job-463805198821392385
1 [async] closedts-rangefeed-subscriber
1 [async] changefeed-poller
I190627 05:15:17.053497 93502 util/stop/stopper.go:542 quiescing; tasks left:
2 [async] rangefeed: output loop
1 [async] storage.IntentResolver: cleanup txn records
1 [async] kv.TxnCoordSender: heartbeat loop
1 [async] job-463805198821392385
1 [async] closedts-rangefeed-subscriber
1 [async] changefeed-poller
I190627 05:15:17.053528 93502 util/stop/stopper.go:542 quiescing; tasks left:
1 [async] storage.IntentResolver: cleanup txn records
1 [async] rangefeed: output loop
1 [async] kv.TxnCoordSender: heartbeat loop
1 [async] job-463805198821392385
1 [async] closedts-rangefeed-subscriber
1 [async] changefeed-poller
I190627 05:15:17.053589 93502 util/stop/stopper.go:542 quiescing; tasks left:
1 [async] rangefeed: output loop
1 [async] kv.TxnCoordSender: heartbeat loop
1 [async] job-463805198821392385
1 [async] closedts-rangefeed-subscriber
1 [async] changefeed-poller
I190627 05:15:17.053760 93502 util/stop/stopper.go:542 quiescing; tasks left:
1 [async] rangefeed: output loop
1 [async] job-463805198821392385
1 [async] closedts-rangefeed-subscriber
1 [async] changefeed-poller
I190627 05:15:17.053883 93502 util/stop/stopper.go:542 quiescing; tasks left:
1 [async] job-463805198821392385
1 [async] closedts-rangefeed-subscriber
1 [async] changefeed-poller
I190627 05:15:17.054037 93502 util/stop/stopper.go:542 quiescing; tasks left:
1 [async] job-463805198821392385
1 [async] changefeed-poller
E190627 05:15:17.054081 93677 jobs/registry.go:323 error while adopting jobs: adopt-job: node unavailable; try another peer
I190627 05:15:17.057715 93502 util/stop/stopper.go:542 quiescing; tasks left:
1 [async] job-463805198821392385
W190627 05:15:17.057852 94492 ccl/changefeedccl/changefeed_stmt.go:488 [n1] CHANGEFEED job 463805198821392385 returning with error: node unavailable; try another peer
fetching changes for /Table/{3-4}
-- safe details:
fetching changes for %s
-- arg 0: roachpb.Span
-- stack trace:
github.com/cockroachdb/cockroach/pkg/ccl/changefeedccl.fetchTableDescriptorVersions
/go/src/github.com/cockroachdb/cockroach/pkg/ccl/changefeedccl/table_history.go:246
github.com/cockroachdb/cockroach/pkg/ccl/changefeedccl.(*poller).updateTableHistory
/go/src/github.com/cockroachdb/cockroach/pkg/ccl/changefeedccl/poller.go:445
github.com/cockroachdb/cockroach/pkg/ccl/changefeedccl.(*poller).pollTableHistory
/go/src/github.com/cockroachdb/cockroach/pkg/ccl/changefeedccl/poller.go:454
github.com/cockroachdb/cockroach/pkg/util/ctxgroup.Group.GoCtx.func1
/go/src/github.com/cockroachdb/cockroach/pkg/util/ctxgroup/ctxgroup.go:166
github.com/cockroachdb/cockroach/vendor/golang.org/x/sync/errgroup.(*Group).Go.func1
/go/src/github.com/cockroachdb/cockroach/vendor/golang.org/x/sync/errgroup/errgroup.go:57
runtime.goexit
/usr/local/go/src/runtime/asm_amd64.s:1337
nemeses_test.go:32: topic foo partition : saw new row timestamp 1561612516455427509.0000000000 after 1561612516627081973.0000000000 was seen
TestChangefeedNemeses
--- FAIL: test/TestChangefeedNemeses (8.560s)
```
Please assign, take a look and update the issue accordingly.
|
test
|
teamcity failed test testchangefeednemeses the following tests appear to have failed on master test testchangefeednemeses testchangefeednemeses cloudstorage you may want to check testchangefeednemeses cloudstorage kv txncoordsender heartbeat loop job closedts rangefeed subscriber changefeed poller util stop stopper go quiescing tasks left rangefeed output loop storage intentresolver cleanup txn records kv txncoordsender heartbeat loop job closedts rangefeed subscriber changefeed poller util stop stopper go quiescing tasks left storage intentresolver cleanup txn records rangefeed output loop kv txncoordsender heartbeat loop job closedts rangefeed subscriber changefeed poller util stop stopper go quiescing tasks left rangefeed output loop storage intentresolver cleanup txn records kv txncoordsender heartbeat loop job closedts rangefeed subscriber changefeed poller util stop stopper go quiescing tasks left storage intentresolver cleanup txn records rangefeed output loop kv txncoordsender heartbeat loop job closedts rangefeed subscriber changefeed poller util stop stopper go quiescing tasks left rangefeed output loop kv txncoordsender heartbeat loop job closedts rangefeed subscriber changefeed poller util stop stopper go quiescing tasks left rangefeed output loop job closedts rangefeed subscriber changefeed poller util stop stopper go quiescing tasks left job closedts rangefeed subscriber changefeed poller util stop stopper go quiescing tasks left job changefeed poller jobs registry go error while adopting jobs adopt job node unavailable try another peer util stop stopper go quiescing tasks left job ccl changefeedccl changefeed stmt go changefeed job returning with error node unavailable try another peer fetching changes for table safe details fetching changes for s arg roachpb span stack trace github com cockroachdb cockroach pkg ccl changefeedccl fetchtabledescriptorversions go src github com cockroachdb cockroach pkg ccl changefeedccl table history go github com cockroachdb cockroach pkg ccl changefeedccl poller updatetablehistory go src github com cockroachdb cockroach pkg ccl changefeedccl poller go github com cockroachdb cockroach pkg ccl changefeedccl poller polltablehistory go src github com cockroachdb cockroach pkg ccl changefeedccl poller go github com cockroachdb cockroach pkg util ctxgroup group goctx go src github com cockroachdb cockroach pkg util ctxgroup ctxgroup go github com cockroachdb cockroach vendor golang org x sync errgroup group go go src github com cockroachdb cockroach vendor golang org x sync errgroup errgroup go runtime goexit usr local go src runtime asm s nemeses test go topic foo partition saw new row timestamp after was seen testchangefeednemeses fail test testchangefeednemeses please assign take a look and update the issue accordingly
| 1
|
302,531
| 26,149,777,945
|
IssuesEvent
|
2022-12-30 11:44:52
|
elastic/e2e-testing
|
https://api.github.com/repos/elastic/e2e-testing
|
closed
|
poll docker api for checking readiness
|
enhancement Team:Automation area:test priority:low size:S triaged
|
This came out of this PR discussion https://github.com/elastic/e2e-testing/pull/934#pullrequestreview-620101929
The basic idea is to create some additional api calls to docker for verifying things like docker images being loaded and ready prior to tagging.
We can expand on this issue further to figure out what this api would cover
|
1.0
|
poll docker api for checking readiness - This came out of this PR discussion https://github.com/elastic/e2e-testing/pull/934#pullrequestreview-620101929
The basic idea is to create some additional api calls to docker for verifying things like docker images being loaded and ready prior to tagging.
We can expand on this issue further to figure out what this api would cover
|
test
|
poll docker api for checking readiness this came out of this pr discussion the basic idea is to create some additional api calls to docker for verifying things like docker images being loaded and ready prior to tagging we can expand on this issue further to figure out what this api would cover
| 1
|
254,270
| 8,072,080,438
|
IssuesEvent
|
2018-08-06 14:58:13
|
edenlabllc/ehealth.api
|
https://api.github.com/repos/edenlabllc/ehealth.api
|
opened
|
Error to get scope for Owner PROD (jira-181)
|
kind/support priority/medium
|
Сотрудник с "id": "92a1f205-62e3-4041-86ce-40aa1ab30b08" пытается получить следующий набор scope
'employee_request:read', 'employee_request:write', 'employee_request:approve', 'employee_request:reject', 'employee:read', 'employee:write', 'employee:details', 'employee:deactivate'
employee_type: OWNER
После авторизации на сайте ehealth получаем ошибку "User requested scope that is not allowed by role based access policies".
request_id:
"5a6ad297-204e-4016-8b41-2728b679202c#181338"
Expected results:
Получение необходимых scope происходит без ошибки
employee_id: "92a1f205-62e3-4041-86ce-40aa1ab30b08"
request_id:
"5a6ad297-204e-4016-8b41-2728b679202c#181338"
|
1.0
|
Error to get scope for Owner PROD (jira-181) - Сотрудник с "id": "92a1f205-62e3-4041-86ce-40aa1ab30b08" пытается получить следующий набор scope
'employee_request:read', 'employee_request:write', 'employee_request:approve', 'employee_request:reject', 'employee:read', 'employee:write', 'employee:details', 'employee:deactivate'
employee_type: OWNER
После авторизации на сайте ehealth получаем ошибку "User requested scope that is not allowed by role based access policies".
request_id:
"5a6ad297-204e-4016-8b41-2728b679202c#181338"
Expected results:
Получение необходимых scope происходит без ошибки
employee_id: "92a1f205-62e3-4041-86ce-40aa1ab30b08"
request_id:
"5a6ad297-204e-4016-8b41-2728b679202c#181338"
|
non_test
|
error to get scope for owner prod jira сотрудник с id пытается получить следующий набор scope employee request read employee request write employee request approve employee request reject employee read employee write employee details employee deactivate employee type owner после авторизации на сайте ehealth получаем ошибку user requested scope that is not allowed by role based access policies request id expected results получение необходимых scope происходит без ошибки employee id request id
| 0
|
208,002
| 16,100,801,852
|
IssuesEvent
|
2021-04-27 09:02:23
|
pyiron/pyiron_atomistics
|
https://api.github.com/repos/pyiron/pyiron_atomistics
|
closed
|
What's the difference between SQS and SQSMaster?
|
documentation help wanted
|
Has anyone used SQS lately and knows the difference between
https://github.com/pyiron/pyiron_atomistics/blob/master/pyiron_atomistics/atomistics/master/sqsmaster.py
and
https://github.com/pyiron/pyiron_atomistics/blob/master/pyiron_atomistics/atomistics/job/sqs.py
or might even be deigned to write some docs?
|
1.0
|
What's the difference between SQS and SQSMaster? - Has anyone used SQS lately and knows the difference between
https://github.com/pyiron/pyiron_atomistics/blob/master/pyiron_atomistics/atomistics/master/sqsmaster.py
and
https://github.com/pyiron/pyiron_atomistics/blob/master/pyiron_atomistics/atomistics/job/sqs.py
or might even be deigned to write some docs?
|
non_test
|
what s the difference between sqs and sqsmaster has anyone used sqs lately and knows the difference between and or might even be deigned to write some docs
| 0
|
193,231
| 22,216,104,391
|
IssuesEvent
|
2022-06-08 01:56:20
|
maddyCode23/linux-4.1.15
|
https://api.github.com/repos/maddyCode23/linux-4.1.15
|
reopened
|
CVE-2019-20934 (Medium) detected in multiple libraries
|
security vulnerability
|
## CVE-2019-20934 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>linux-stable-rtv4.1.33</b>, <b>linux-stable-rtv4.1.33</b>, <b>linux-stable-rtv4.1.33</b></p></summary>
<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>
An issue was discovered in the Linux kernel before 5.2.6. On NUMA systems, the Linux fair scheduler has a use-after-free in show_numa_stats() because NUMA fault statistics are inappropriately freed, aka CID-16d51a590a8c.
<p>Publish Date: 2020-11-28
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-20934>CVE-2019-20934</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: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20934">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20934</a></p>
<p>Release Date: 2020-11-28</p>
<p>Fix Resolution: v5.3-rc2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2019-20934 (Medium) detected in multiple libraries - ## CVE-2019-20934 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>linux-stable-rtv4.1.33</b>, <b>linux-stable-rtv4.1.33</b>, <b>linux-stable-rtv4.1.33</b></p></summary>
<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>
An issue was discovered in the Linux kernel before 5.2.6. On NUMA systems, the Linux fair scheduler has a use-after-free in show_numa_stats() because NUMA fault statistics are inappropriately freed, aka CID-16d51a590a8c.
<p>Publish Date: 2020-11-28
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-20934>CVE-2019-20934</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: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20934">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20934</a></p>
<p>Release Date: 2020-11-28</p>
<p>Fix Resolution: v5.3-rc2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_test
|
cve medium detected in multiple libraries cve medium severity vulnerability vulnerable libraries linux stable linux stable linux stable vulnerability details an issue was discovered in the linux kernel before on numa systems the linux fair scheduler has a use after free in show numa stats because numa fault statistics are inappropriately freed aka cid publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity high privileges required low user interaction none scope unchanged impact metrics confidentiality impact low integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource
| 0
|
52,712
| 6,266,619,973
|
IssuesEvent
|
2017-07-17 03:15:38
|
learn-co-curriculum/forms-and-basic-associations-rails
|
https://api.github.com/repos/learn-co-curriculum/forms-and-basic-associations-rails
|
closed
|
strong param arrays
|
Test
|
Hi there,
Sorry for the bother. This lesson provides an example for making an array (post_ids) a strong parameter via the category_params method. This example may be incorrect. According to the rails strong parameter documentation on github (https://github.com/rails/strong_parameters), arrays must be explicitly called out in a permit method.
In other words, students may run into problems trying to emulate
```
def category_params
params.require(:category).permit(:name, :post_ids)
end
end
```
when the following is closer to what the documentation says:
```
def category_params
params.require(:category).permit(:name, {:post_ids=> []})
end
end
```
(I mention it because I had problems with this in the next lab!)
Thanks for all your hard work,
C
|
1.0
|
strong param arrays - Hi there,
Sorry for the bother. This lesson provides an example for making an array (post_ids) a strong parameter via the category_params method. This example may be incorrect. According to the rails strong parameter documentation on github (https://github.com/rails/strong_parameters), arrays must be explicitly called out in a permit method.
In other words, students may run into problems trying to emulate
```
def category_params
params.require(:category).permit(:name, :post_ids)
end
end
```
when the following is closer to what the documentation says:
```
def category_params
params.require(:category).permit(:name, {:post_ids=> []})
end
end
```
(I mention it because I had problems with this in the next lab!)
Thanks for all your hard work,
C
|
test
|
strong param arrays hi there sorry for the bother this lesson provides an example for making an array post ids a strong parameter via the category params method this example may be incorrect according to the rails strong parameter documentation on github arrays must be explicitly called out in a permit method in other words students may run into problems trying to emulate def category params params require category permit name post ids end end when the following is closer to what the documentation says def category params params require category permit name post ids end end i mention it because i had problems with this in the next lab thanks for all your hard work c
| 1
|
263,079
| 28,016,221,473
|
IssuesEvent
|
2023-03-27 23:02:22
|
Enterprise-CMCS/macpro-mdct-mcr
|
https://api.github.com/repos/Enterprise-CMCS/macpro-mdct-mcr
|
closed
|
SHF - macpro-mdct-mcr - main - MEDIUM - AWS Health - AWS_EVENTS_INCREASED_API_LATENCIES
|
security-hub main
|
**************************************************************
__This issue was generated from Security Hub data and is managed through automation.__
Please do not edit the title or body of this issue, or remove the security-hub tag. All other edits/comments are welcome.
Finding Id: arn:aws:health:us-east-1:446712541566:event/EVENTS/AWS_EVENTS_INCREASED_API_LATENCIES/AWS_EVENTS_INCREASED_API_LATENCIES_48fc885c-62c5-524d-943b-f46bccda8c25/d683c1164950044db3032f28a88293f405a88b0e
**************************************************************
## Type of Issue:
- [x] Security Hub Finding
## Title:
AWS Health - AWS_EVENTS_INCREASED_API_LATENCIES
## Id:
arn:aws:health:us-east-1:446712541566:event/EVENTS/AWS_EVENTS_INCREASED_API_LATENCIES/AWS_EVENTS_INCREASED_API_LATENCIES_48fc885c-62c5-524d-943b-f46bccda8c25/d683c1164950044db3032f28a88293f405a88b0e
(You may use this ID to lookup this finding's details in Security Hub)
## Description
We are investigating increased API latencies in the us-east-1 Region.
## Remediation
undefined
## AC:
- The security hub finding is resolved or suppressed, indicated by a Workflow Status of Resolved or Suppressed.
|
True
|
SHF - macpro-mdct-mcr - main - MEDIUM - AWS Health - AWS_EVENTS_INCREASED_API_LATENCIES - **************************************************************
__This issue was generated from Security Hub data and is managed through automation.__
Please do not edit the title or body of this issue, or remove the security-hub tag. All other edits/comments are welcome.
Finding Id: arn:aws:health:us-east-1:446712541566:event/EVENTS/AWS_EVENTS_INCREASED_API_LATENCIES/AWS_EVENTS_INCREASED_API_LATENCIES_48fc885c-62c5-524d-943b-f46bccda8c25/d683c1164950044db3032f28a88293f405a88b0e
**************************************************************
## Type of Issue:
- [x] Security Hub Finding
## Title:
AWS Health - AWS_EVENTS_INCREASED_API_LATENCIES
## Id:
arn:aws:health:us-east-1:446712541566:event/EVENTS/AWS_EVENTS_INCREASED_API_LATENCIES/AWS_EVENTS_INCREASED_API_LATENCIES_48fc885c-62c5-524d-943b-f46bccda8c25/d683c1164950044db3032f28a88293f405a88b0e
(You may use this ID to lookup this finding's details in Security Hub)
## Description
We are investigating increased API latencies in the us-east-1 Region.
## Remediation
undefined
## AC:
- The security hub finding is resolved or suppressed, indicated by a Workflow Status of Resolved or Suppressed.
|
non_test
|
shf macpro mdct mcr main medium aws health aws events increased api latencies this issue was generated from security hub data and is managed through automation please do not edit the title or body of this issue or remove the security hub tag all other edits comments are welcome finding id arn aws health us east event events aws events increased api latencies aws events increased api latencies type of issue security hub finding title aws health aws events increased api latencies id arn aws health us east event events aws events increased api latencies aws events increased api latencies you may use this id to lookup this finding s details in security hub description we are investigating increased api latencies in the us east region remediation undefined ac the security hub finding is resolved or suppressed indicated by a workflow status of resolved or suppressed
| 0
|
86,802
| 8,050,709,023
|
IssuesEvent
|
2018-08-01 14:11:49
|
eclipse/openj9
|
https://api.github.com/repos/eclipse/openj9
|
opened
|
DaaLoadTest_daa2_0 Test-sanity.system-JDK10-linux_x86-64 assert ScavengerRootScanner.hpp:105
|
test failure
|
May be the same issue as #2385
https://ci.eclipse.org/openj9/job/Test-sanity.system-JDK10-linux_x86-64/34
```
===============================================
Running test DaaLoadTest_daa2_0 ...
===============================================
DaaLoadTest_daa2_0 Start Time: Wed Aug 1 08:32:45 2018 Epoch Time (ms): 1533112365303
test with NoOptions
STF 08:32:45.464 - ========================= S T F =========================
systemtest-prereqs has been processed, and set to: /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/systemtest_prereqsRetrieving amount of free space on drive containing /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0
There is 90622 Mb free
STF 08:32:45.470 - ================== G E N E R A T I O N ==================
STF 08:32:45.471 - Checking JVM: /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdkbinary/j2sdk-image/bin/../
STF 08:32:45.471 - Starting process to generate scripts: /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdkbinary/j2sdk-image/bin/..//bin/java -Dlog4j.skipJansi=true -Djava.system.class.loader=net.adoptopenjdk.stf.runner.StfClassLoader -classpath /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../../jvmtest/systemtest/systemtest_prereqs/log4j-2.3/log4j-api-2.3.jar:/home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../../jvmtest/systemtest/systemtest_prereqs/log4j-2.3/log4j-core-2.3.jar:/home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/stf/stf.core/scripts/../bin net.adoptopenjdk.stf.runner.StfRunner -properties "/home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/stf_parameters.properties, , /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/stf/stf.core/config/stf.properties" -testDir "/home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest"
GEN 08:32:46.693 - Found test. Project: 'openj9.test.load' class: 'DaaLoadTest.class' Dir: '/home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/openj9-systemtest/openj9.test.load/bin'
GEN 08:32:46.695 - Found test. Project: 'openj9.test.load' class: 'net.openj9.stf.DaaLoadTest'
GEN Classpath directories used by project 'openj9.test.load':
GEN /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/openj9-systemtest/openj9.test.load/bin
GEN /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/stf/stf.core/bin
GEN /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/stf/stf.load/bin
GEN /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/systemtest_prereqs/log4j-2.3/log4j-api-2.3.jar
GEN /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/systemtest_prereqs/log4j-2.3/log4j-core-2.3.jar
GEN /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/systemtest_prereqs/junit-4.12/junit-4.12.jar
GEN /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/systemtest_prereqs/junit-4.12/hamcrest-core-1.3.jar
GEN 08:32:47.038 - Using Mode NoOptions. Values = ''
GEN 08:32:47.125 -
GEN 08:32:47.125 - Test command summary:
GEN 08:32:47.126 - Step Stage Command Description
GEN 08:32:47.127 - -----+--------+-----------------+------------
GEN 08:32:47.127 - 1 execute Run java Run daa load test
STF 08:32:47.169 -
STF 08:32:47.169 - Script generation completed
STF 08:32:47.169 -
STF 08:32:47.169 -
STF 08:32:47.169 - ======================= S E T U P =======================
STF 08:32:47.169 - Running setup: perl /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/setUp.pl
STF 08:32:47.233 - SETUP stage completed
STF 08:32:47.237 -
STF 08:32:47.237 - ==================== E X E C U T E - ====================
STF 08:32:47.237 - Running execute: perl /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/execute.pl
STF 08:32:47.302 -
STF 08:32:47.302 - Java version
STF 08:32:47.302 - Running: /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdkbinary/j2sdk-image/bin/../bin/java -version
openjdk version "10.0.2-internal" 2018-07-17
OpenJDK Runtime Environment (build 10.0.2-internal+0-adhoc.jenkins.Build-JDK10-linuxx86-64)
Eclipse OpenJ9 VM (build master-9f325487, JRE 10 Linux amd64-64-Bit 20180801_251 (JIT enabled, AOT enabled)
OpenJ9 - 9f325487
OMR - 848259f4
JCL - 01b7e8c89c7 based on jdk-10.0.1+10)
STF 08:32:47.517 -
STF 08:32:47.518 - +------ Step 1 - Run daa load test
STF 08:32:47.518 - | Run foreground process
STF 08:32:47.518 - | Program: /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdkbinary/j2sdk-image/bin/../bin/java
STF 08:32:47.518 - | Mnemonic: DLT
STF 08:32:47.518 - | Echo: ECHO_ON
STF 08:32:47.518 - | Expectation: CLEAN_RUN within 3h
STF 08:32:47.518 - |
STF 08:32:47.518 - Running command: /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdkbinary/j2sdk-image/bin/../bin/java -Xnocompressedrefs -classpath /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/stf/stf.load/bin:/home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/stf/stf.core/bin:/home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/systemtest_prereqs/log4j-2.3/log4j-api-2.3.jar:/home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/systemtest_prereqs/log4j-2.3/log4j-core-2.3.jar:/home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/systemtest_prereqs/junit-4.12/junit-4.12.jar:/home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/systemtest_prereqs/junit-4.12/hamcrest-core-1.3.jar:/home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/openj9-systemtest/openj9.test.daa/bin net.adoptopenjdk.loadTest.LoadTest -resultsDir /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results -resultsPrefix 1.DLT. -reportFailureLimit 1 -abortAtFailureLimit 10 -maxTotalLogFileSpace 200M -maxSingleLogSize 1/25 -suite.daa.threadCount 2 -suite.daa.totalNumberTests 4200 -suite.daa.inventoryFile /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/1.DLT.inventory/openj9.test.load/config/inventories/daa/daa2.xml -suite.daa.inventoryExcludeFile none -suite.daa.selection random -suite.daa.seed -1 -suite.daa.repeatCount 1 -suite.daa.thinkingTime 0ms..0ms
STF 08:32:47.518 - Redirecting stderr to /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/1.DLT.stderr
STF 08:32:47.518 - Redirecting stdout to /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/1.DLT.stdout
STF 08:32:47.528 - Monitoring processes: DLT
DLT 08:32:48.685 - Load test parameters
DLT 08:32:48.688 - Time limited = false
DLT 08:32:48.688 - abortIfOutOfMemory = true
DLT 08:32:48.689 - reportFailureLimit = 1
DLT 08:32:48.689 - abortAtFailureLimit = 10
DLT 08:32:48.691 - maxTotalLogFileSpace = 209715200
DLT 08:32:48.692 - maxSingleLogSize = 8388608
DLT 08:32:48.692 - Parameters for suite 0
DLT 08:32:48.693 - Suite name = daa
DLT 08:32:48.694 - Number threads = 2
DLT 08:32:48.694 - Supplied seed = -1
DLT 08:32:48.695 - Inventory file = /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/1.DLT.inventory/openj9.test.load/config/inventories/daa/daa2.xml
DLT 08:32:48.696 - Exclude file = none
DLT 08:32:48.696 - Number tests = 4200
DLT 08:32:48.697 - Repeat count = 1
DLT 08:32:48.697 - Thinking time = 0ms..0ms
DLT 08:32:48.698 - Selection mode = random
DLT 08:32:48.699 - Actual seed = 1530999103554
DLT 08:32:48.709 - Parsing inventory file. Root=/home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/1.DLT.inventory File=openj9.test.load/config/inventories/daa/daa2.xml
DLT 08:32:48.724 - Final test list:
DLT 08:32:48.727 - 0 ArbitraryJava[net.openj9.test.decimals.DecimalTestRunner invokeTest] Weighting=1
DLT 08:32:48.727 - 1 ArbitraryJava[net.openj9.test.MarshallingTestRunner invokeTest] Weighting=1
DLT 08:32:48.727 - 2 ArbitraryJava[net.openj9.test.PD2Primitive.I2PD_PD2ITestRunner invokeTest] Weighting=1
DLT 08:32:48.730 - 3 JUnit[net.openj9.test.arithmetics.TestArithmeticOperations] Weighting=1
DLT 08:32:48.731 - 4 JUnit[net.openj9.test.binaryData.TestBinaryConverters] Weighting=1
DLT 08:32:48.731 - 5 JUnit[net.openj9.test.binaryData.TestByteArray2Double] Weighting=1
DLT 08:32:48.731 - 6 JUnit[net.openj9.test.binaryData.TestByteArray2Float] Weighting=1
DLT 08:32:48.731 - 7 JUnit[net.openj9.test.binaryData.TestByteArray2Integer] Weighting=1
DLT 08:32:48.731 - 8 JUnit[net.openj9.test.binaryData.TestByteArray2IntegerNumBytes] Weighting=1
DLT 08:32:48.731 - 9 JUnit[net.openj9.test.binaryData.TestByteArray2Long] Weighting=1
DLT 08:32:48.732 - 10 JUnit[net.openj9.test.binaryData.TestByteArray2LongNumBytes] Weighting=1
DLT 08:32:48.732 - 11 JUnit[net.openj9.test.binaryData.TestByteArray2Short] Weighting=1
DLT 08:32:48.732 - 12 JUnit[net.openj9.test.binaryData.TestByteArray2ShortNumBytes] Weighting=1
DLT 08:32:48.732 - 13 JUnit[net.openj9.test.binaryData.TestDouble2ByteArray] Weighting=1
DLT 08:32:48.732 - 14 JUnit[net.openj9.test.binaryData.TestFloat2ByteArray] Weighting=1
DLT 08:32:48.732 - 15 JUnit[net.openj9.test.binaryData.TestInteger2ByteArray] Weighting=1
DLT 08:32:48.732 - 16 JUnit[net.openj9.test.binaryData.TestInteger2ByteArrayNumBytes] Weighting=1
DLT 08:32:48.733 - 17 JUnit[net.openj9.test.binaryData.TestLong2ByteArray] Weighting=1
DLT 08:32:48.733 - 18 JUnit[net.openj9.test.binaryData.TestLong2ByteArrayNumBytes] Weighting=1
DLT 08:32:48.733 - 19 JUnit[net.openj9.test.binaryData.TestShort2ByteArray] Weighting=1
DLT 08:32:48.733 - 20 JUnit[net.openj9.test.binaryData.TestShort2ByteArrayNumBytes] Weighting=1
DLT 08:32:48.733 - 21 JUnit[net.openj9.test.decimals.TestED2PD] Weighting=1
DLT 08:32:48.733 - 22 JUnit[net.openj9.test.decimals.TestPD2ED] Weighting=1
DLT 08:32:48.733 - 23 JUnit[net.openj9.test.decimals.TestPD2UD] Weighting=1
DLT 08:32:48.733 - 24 JUnit[net.openj9.test.decimals.TestUD2PD] Weighting=1
DLT 08:32:48.733 - 25 JUnit[net.openj9.test.PD2Primitive.RandomTests] Weighting=1
DLT 08:32:48.733 - 26 JUnit[net.openj9.test.PD2Primitive.TestI2PD] Weighting=1
DLT 08:32:48.734 - 27 JUnit[net.openj9.test.PD2Primitive.TestPD2I] Weighting=1
DLT 08:32:48.782 - Starting thread. Suite=0 thread=0
DLT 08:32:48.784 - Starting thread. Suite=0 thread=1
DLT 08:33:08.852 - Completed 7.5%. Number of tests started=317
DLT stderr 00007FAB24C99400: Object neither in heap nor stack-allocated in thread load-1
DLT stderr 00007FAB24C99400: O-Slot=00007FAA895DA908
DLT stderr 00007FAB24C99400: O-Slot value=00007FAB2285F2D0
DLT stderr 00007FAB24C99400: PC=00007FAA8995E898
DLT stderr 00007FAB24C99400: framesWalked=3
DLT stderr 00007FAB24C99400: arg0EA=00007FAA2C009450
DLT stderr 00007FAB24C99400: walkSP=00007FAA2C009398
DLT stderr 00007FAB24C99400: literals=0000000000000010
DLT stderr 00007FAB24C99400: jitInfo=00007FAA6B88E278
DLT stderr 00007FAB24C99400: method=00007FAA3806B6D8 (org/junit/Assert.assertEquals(Ljava/lang/String;Ljava/lang/Object;Ljava/lang/Object;)V) (JIT)
DLT stderr 00007FAB24C99400: stack=00007FAA2C002F60-00007FAA2C009FC0
DLT stderr 08:33:09.263 0x7faa44003a00 j9mm.479 * ** ASSERTION FAILED ** at ../../../../gc_glue_java/ScavengerRootScanner.hpp:105: ((MM_StackSlotValidator(MM_StackSlotValidator::NOT_ON_HEAP, *slotPtr, stackLocation, walkState).validate(_env)))
DLT stderr JVMDUMP039I Processing dump event "traceassert", detail "" at 2018/08/01 08:33:09 - please wait.
DLT stderr JVMDUMP032I JVM requested System dump using '/home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/core.20180801.083309.12484.0001.dmp' in response to an event
DLT stderr JVMPORT030W /proc/sys/kernel/core_pattern setting "|/usr/share/apport/apport %p %s %c %d %P" specifies that the core dump is to be piped to an external program. Attempting to rename either core or core.12573.
DLT stderr
DLT stderr JVMDUMP010I System dump written to /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/core.20180801.083309.12484.0001.dmp
DLT stderr JVMDUMP032I JVM requested Java dump using '/home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/javacore.20180801.083309.12484.0002.txt' in response to an event
STF 08:33:10.721 - Found dump at: /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/javacore.20180801.083309.12484.0002.txt
STF 08:33:10.721 - Found dump at: /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/core.20180801.083309.12484.0001.dmp
DLT stderr javacore file generated - /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/javacore.20180801.083309.12484.0002.txt
DLT stderr core file generated - /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/core.20180801.083309.12484.0001.dmp
DLT stderr JVMDUMP010I Java dump written to /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/javacore.20180801.083309.12484.0002.txt
DLT stderr JVMDUMP032I JVM requested Snap dump using '/home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/Snap.20180801.083309.12484.0003.trc' in response to an event
STF 08:33:10.952 - Found dump at: /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/Snap.20180801.083309.12484.0003.trc
DLT stderr Snap file generated - /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/Snap.20180801.083309.12484.0003.trc
DLT stderr JVMDUMP010I Snap dump written to /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/Snap.20180801.083309.12484.0003.trc
DLT stderr JVMDUMP013I Processed dump event "traceassert", detail "".
STF 08:33:11.184 - **FAILED** Process DLT ended with exit code (255) and not the expected exit code/s (0)
STF 08:33:11.184 - Monitoring Report Summary:
STF 08:33:11.184 - o Process DLT has crashed unexpectedly
STF 08:33:11.184 - Killing processes: DLT
STF 08:33:11.184 - o Process DLT is not running
**FAILED** at step 1 (Run daa load test). Expected return value=0 Actual=1 at /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/execute.pl line 92.
STF 08:33:11.195 - **FAILED** execute script failed. Expected return value=0 Actual=1
STF 08:33:11.195 -
STF 08:33:11.195 - ==================== T E A R D O W N ====================
STF 08:33:11.195 - Running teardown: perl /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/tearDown.pl
STF 08:33:11.258 - TEARDOWN stage completed
STF 08:33:11.263 -
STF 08:33:11.263 - ===================== R E S U L T S =====================
STF 08:33:11.263 - Stage results:
STF 08:33:11.264 - setUp: pass
STF 08:33:11.264 - execute: *fail*
STF 08:33:11.264 - teardown: pass
STF 08:33:11.264 -
STF 08:33:11.264 - Overall result: **FAILED**
DaaLoadTest_daa2_0_FAILED
```
|
1.0
|
DaaLoadTest_daa2_0 Test-sanity.system-JDK10-linux_x86-64 assert ScavengerRootScanner.hpp:105 - May be the same issue as #2385
https://ci.eclipse.org/openj9/job/Test-sanity.system-JDK10-linux_x86-64/34
```
===============================================
Running test DaaLoadTest_daa2_0 ...
===============================================
DaaLoadTest_daa2_0 Start Time: Wed Aug 1 08:32:45 2018 Epoch Time (ms): 1533112365303
test with NoOptions
STF 08:32:45.464 - ========================= S T F =========================
systemtest-prereqs has been processed, and set to: /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/systemtest_prereqsRetrieving amount of free space on drive containing /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0
There is 90622 Mb free
STF 08:32:45.470 - ================== G E N E R A T I O N ==================
STF 08:32:45.471 - Checking JVM: /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdkbinary/j2sdk-image/bin/../
STF 08:32:45.471 - Starting process to generate scripts: /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdkbinary/j2sdk-image/bin/..//bin/java -Dlog4j.skipJansi=true -Djava.system.class.loader=net.adoptopenjdk.stf.runner.StfClassLoader -classpath /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../../jvmtest/systemtest/systemtest_prereqs/log4j-2.3/log4j-api-2.3.jar:/home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../../jvmtest/systemtest/systemtest_prereqs/log4j-2.3/log4j-core-2.3.jar:/home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/stf/stf.core/scripts/../bin net.adoptopenjdk.stf.runner.StfRunner -properties "/home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/stf_parameters.properties, , /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/stf/stf.core/config/stf.properties" -testDir "/home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest"
GEN 08:32:46.693 - Found test. Project: 'openj9.test.load' class: 'DaaLoadTest.class' Dir: '/home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/openj9-systemtest/openj9.test.load/bin'
GEN 08:32:46.695 - Found test. Project: 'openj9.test.load' class: 'net.openj9.stf.DaaLoadTest'
GEN Classpath directories used by project 'openj9.test.load':
GEN /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/openj9-systemtest/openj9.test.load/bin
GEN /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/stf/stf.core/bin
GEN /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/stf/stf.load/bin
GEN /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/systemtest_prereqs/log4j-2.3/log4j-api-2.3.jar
GEN /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/systemtest_prereqs/log4j-2.3/log4j-core-2.3.jar
GEN /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/systemtest_prereqs/junit-4.12/junit-4.12.jar
GEN /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/systemtest_prereqs/junit-4.12/hamcrest-core-1.3.jar
GEN 08:32:47.038 - Using Mode NoOptions. Values = ''
GEN 08:32:47.125 -
GEN 08:32:47.125 - Test command summary:
GEN 08:32:47.126 - Step Stage Command Description
GEN 08:32:47.127 - -----+--------+-----------------+------------
GEN 08:32:47.127 - 1 execute Run java Run daa load test
STF 08:32:47.169 -
STF 08:32:47.169 - Script generation completed
STF 08:32:47.169 -
STF 08:32:47.169 -
STF 08:32:47.169 - ======================= S E T U P =======================
STF 08:32:47.169 - Running setup: perl /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/setUp.pl
STF 08:32:47.233 - SETUP stage completed
STF 08:32:47.237 -
STF 08:32:47.237 - ==================== E X E C U T E - ====================
STF 08:32:47.237 - Running execute: perl /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/execute.pl
STF 08:32:47.302 -
STF 08:32:47.302 - Java version
STF 08:32:47.302 - Running: /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdkbinary/j2sdk-image/bin/../bin/java -version
openjdk version "10.0.2-internal" 2018-07-17
OpenJDK Runtime Environment (build 10.0.2-internal+0-adhoc.jenkins.Build-JDK10-linuxx86-64)
Eclipse OpenJ9 VM (build master-9f325487, JRE 10 Linux amd64-64-Bit 20180801_251 (JIT enabled, AOT enabled)
OpenJ9 - 9f325487
OMR - 848259f4
JCL - 01b7e8c89c7 based on jdk-10.0.1+10)
STF 08:32:47.517 -
STF 08:32:47.518 - +------ Step 1 - Run daa load test
STF 08:32:47.518 - | Run foreground process
STF 08:32:47.518 - | Program: /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdkbinary/j2sdk-image/bin/../bin/java
STF 08:32:47.518 - | Mnemonic: DLT
STF 08:32:47.518 - | Echo: ECHO_ON
STF 08:32:47.518 - | Expectation: CLEAN_RUN within 3h
STF 08:32:47.518 - |
STF 08:32:47.518 - Running command: /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdkbinary/j2sdk-image/bin/../bin/java -Xnocompressedrefs -classpath /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/stf/stf.load/bin:/home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/stf/stf.core/bin:/home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/systemtest_prereqs/log4j-2.3/log4j-api-2.3.jar:/home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/systemtest_prereqs/log4j-2.3/log4j-core-2.3.jar:/home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/systemtest_prereqs/junit-4.12/junit-4.12.jar:/home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/systemtest_prereqs/junit-4.12/hamcrest-core-1.3.jar:/home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/jvmtest/systemtest/openj9-systemtest/openj9.test.daa/bin net.adoptopenjdk.loadTest.LoadTest -resultsDir /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results -resultsPrefix 1.DLT. -reportFailureLimit 1 -abortAtFailureLimit 10 -maxTotalLogFileSpace 200M -maxSingleLogSize 1/25 -suite.daa.threadCount 2 -suite.daa.totalNumberTests 4200 -suite.daa.inventoryFile /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/1.DLT.inventory/openj9.test.load/config/inventories/daa/daa2.xml -suite.daa.inventoryExcludeFile none -suite.daa.selection random -suite.daa.seed -1 -suite.daa.repeatCount 1 -suite.daa.thinkingTime 0ms..0ms
STF 08:32:47.518 - Redirecting stderr to /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/1.DLT.stderr
STF 08:32:47.518 - Redirecting stdout to /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/1.DLT.stdout
STF 08:32:47.528 - Monitoring processes: DLT
DLT 08:32:48.685 - Load test parameters
DLT 08:32:48.688 - Time limited = false
DLT 08:32:48.688 - abortIfOutOfMemory = true
DLT 08:32:48.689 - reportFailureLimit = 1
DLT 08:32:48.689 - abortAtFailureLimit = 10
DLT 08:32:48.691 - maxTotalLogFileSpace = 209715200
DLT 08:32:48.692 - maxSingleLogSize = 8388608
DLT 08:32:48.692 - Parameters for suite 0
DLT 08:32:48.693 - Suite name = daa
DLT 08:32:48.694 - Number threads = 2
DLT 08:32:48.694 - Supplied seed = -1
DLT 08:32:48.695 - Inventory file = /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/1.DLT.inventory/openj9.test.load/config/inventories/daa/daa2.xml
DLT 08:32:48.696 - Exclude file = none
DLT 08:32:48.696 - Number tests = 4200
DLT 08:32:48.697 - Repeat count = 1
DLT 08:32:48.697 - Thinking time = 0ms..0ms
DLT 08:32:48.698 - Selection mode = random
DLT 08:32:48.699 - Actual seed = 1530999103554
DLT 08:32:48.709 - Parsing inventory file. Root=/home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/1.DLT.inventory File=openj9.test.load/config/inventories/daa/daa2.xml
DLT 08:32:48.724 - Final test list:
DLT 08:32:48.727 - 0 ArbitraryJava[net.openj9.test.decimals.DecimalTestRunner invokeTest] Weighting=1
DLT 08:32:48.727 - 1 ArbitraryJava[net.openj9.test.MarshallingTestRunner invokeTest] Weighting=1
DLT 08:32:48.727 - 2 ArbitraryJava[net.openj9.test.PD2Primitive.I2PD_PD2ITestRunner invokeTest] Weighting=1
DLT 08:32:48.730 - 3 JUnit[net.openj9.test.arithmetics.TestArithmeticOperations] Weighting=1
DLT 08:32:48.731 - 4 JUnit[net.openj9.test.binaryData.TestBinaryConverters] Weighting=1
DLT 08:32:48.731 - 5 JUnit[net.openj9.test.binaryData.TestByteArray2Double] Weighting=1
DLT 08:32:48.731 - 6 JUnit[net.openj9.test.binaryData.TestByteArray2Float] Weighting=1
DLT 08:32:48.731 - 7 JUnit[net.openj9.test.binaryData.TestByteArray2Integer] Weighting=1
DLT 08:32:48.731 - 8 JUnit[net.openj9.test.binaryData.TestByteArray2IntegerNumBytes] Weighting=1
DLT 08:32:48.731 - 9 JUnit[net.openj9.test.binaryData.TestByteArray2Long] Weighting=1
DLT 08:32:48.732 - 10 JUnit[net.openj9.test.binaryData.TestByteArray2LongNumBytes] Weighting=1
DLT 08:32:48.732 - 11 JUnit[net.openj9.test.binaryData.TestByteArray2Short] Weighting=1
DLT 08:32:48.732 - 12 JUnit[net.openj9.test.binaryData.TestByteArray2ShortNumBytes] Weighting=1
DLT 08:32:48.732 - 13 JUnit[net.openj9.test.binaryData.TestDouble2ByteArray] Weighting=1
DLT 08:32:48.732 - 14 JUnit[net.openj9.test.binaryData.TestFloat2ByteArray] Weighting=1
DLT 08:32:48.732 - 15 JUnit[net.openj9.test.binaryData.TestInteger2ByteArray] Weighting=1
DLT 08:32:48.732 - 16 JUnit[net.openj9.test.binaryData.TestInteger2ByteArrayNumBytes] Weighting=1
DLT 08:32:48.733 - 17 JUnit[net.openj9.test.binaryData.TestLong2ByteArray] Weighting=1
DLT 08:32:48.733 - 18 JUnit[net.openj9.test.binaryData.TestLong2ByteArrayNumBytes] Weighting=1
DLT 08:32:48.733 - 19 JUnit[net.openj9.test.binaryData.TestShort2ByteArray] Weighting=1
DLT 08:32:48.733 - 20 JUnit[net.openj9.test.binaryData.TestShort2ByteArrayNumBytes] Weighting=1
DLT 08:32:48.733 - 21 JUnit[net.openj9.test.decimals.TestED2PD] Weighting=1
DLT 08:32:48.733 - 22 JUnit[net.openj9.test.decimals.TestPD2ED] Weighting=1
DLT 08:32:48.733 - 23 JUnit[net.openj9.test.decimals.TestPD2UD] Weighting=1
DLT 08:32:48.733 - 24 JUnit[net.openj9.test.decimals.TestUD2PD] Weighting=1
DLT 08:32:48.733 - 25 JUnit[net.openj9.test.PD2Primitive.RandomTests] Weighting=1
DLT 08:32:48.733 - 26 JUnit[net.openj9.test.PD2Primitive.TestI2PD] Weighting=1
DLT 08:32:48.734 - 27 JUnit[net.openj9.test.PD2Primitive.TestPD2I] Weighting=1
DLT 08:32:48.782 - Starting thread. Suite=0 thread=0
DLT 08:32:48.784 - Starting thread. Suite=0 thread=1
DLT 08:33:08.852 - Completed 7.5%. Number of tests started=317
DLT stderr 00007FAB24C99400: Object neither in heap nor stack-allocated in thread load-1
DLT stderr 00007FAB24C99400: O-Slot=00007FAA895DA908
DLT stderr 00007FAB24C99400: O-Slot value=00007FAB2285F2D0
DLT stderr 00007FAB24C99400: PC=00007FAA8995E898
DLT stderr 00007FAB24C99400: framesWalked=3
DLT stderr 00007FAB24C99400: arg0EA=00007FAA2C009450
DLT stderr 00007FAB24C99400: walkSP=00007FAA2C009398
DLT stderr 00007FAB24C99400: literals=0000000000000010
DLT stderr 00007FAB24C99400: jitInfo=00007FAA6B88E278
DLT stderr 00007FAB24C99400: method=00007FAA3806B6D8 (org/junit/Assert.assertEquals(Ljava/lang/String;Ljava/lang/Object;Ljava/lang/Object;)V) (JIT)
DLT stderr 00007FAB24C99400: stack=00007FAA2C002F60-00007FAA2C009FC0
DLT stderr 08:33:09.263 0x7faa44003a00 j9mm.479 * ** ASSERTION FAILED ** at ../../../../gc_glue_java/ScavengerRootScanner.hpp:105: ((MM_StackSlotValidator(MM_StackSlotValidator::NOT_ON_HEAP, *slotPtr, stackLocation, walkState).validate(_env)))
DLT stderr JVMDUMP039I Processing dump event "traceassert", detail "" at 2018/08/01 08:33:09 - please wait.
DLT stderr JVMDUMP032I JVM requested System dump using '/home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/core.20180801.083309.12484.0001.dmp' in response to an event
DLT stderr JVMPORT030W /proc/sys/kernel/core_pattern setting "|/usr/share/apport/apport %p %s %c %d %P" specifies that the core dump is to be piped to an external program. Attempting to rename either core or core.12573.
DLT stderr
DLT stderr JVMDUMP010I System dump written to /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/core.20180801.083309.12484.0001.dmp
DLT stderr JVMDUMP032I JVM requested Java dump using '/home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/javacore.20180801.083309.12484.0002.txt' in response to an event
STF 08:33:10.721 - Found dump at: /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/javacore.20180801.083309.12484.0002.txt
STF 08:33:10.721 - Found dump at: /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/core.20180801.083309.12484.0001.dmp
DLT stderr javacore file generated - /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/javacore.20180801.083309.12484.0002.txt
DLT stderr core file generated - /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/core.20180801.083309.12484.0001.dmp
DLT stderr JVMDUMP010I Java dump written to /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/javacore.20180801.083309.12484.0002.txt
DLT stderr JVMDUMP032I JVM requested Snap dump using '/home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/Snap.20180801.083309.12484.0003.trc' in response to an event
STF 08:33:10.952 - Found dump at: /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/Snap.20180801.083309.12484.0003.trc
DLT stderr Snap file generated - /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/Snap.20180801.083309.12484.0003.trc
DLT stderr JVMDUMP010I Snap dump written to /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/results/Snap.20180801.083309.12484.0003.trc
DLT stderr JVMDUMP013I Processed dump event "traceassert", detail "".
STF 08:33:11.184 - **FAILED** Process DLT ended with exit code (255) and not the expected exit code/s (0)
STF 08:33:11.184 - Monitoring Report Summary:
STF 08:33:11.184 - o Process DLT has crashed unexpectedly
STF 08:33:11.184 - Killing processes: DLT
STF 08:33:11.184 - o Process DLT is not running
**FAILED** at step 1 (Run daa load test). Expected return value=0 Actual=1 at /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/execute.pl line 92.
STF 08:33:11.195 - **FAILED** execute script failed. Expected return value=0 Actual=1
STF 08:33:11.195 -
STF 08:33:11.195 - ==================== T E A R D O W N ====================
STF 08:33:11.195 - Running teardown: perl /home/jenkins/workspace/Test-sanity.system-JDK10-linux_x86-64/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15331119301818/DaaLoadTest_daa2_0/20180801-083245-DaaLoadTest/tearDown.pl
STF 08:33:11.258 - TEARDOWN stage completed
STF 08:33:11.263 -
STF 08:33:11.263 - ===================== R E S U L T S =====================
STF 08:33:11.263 - Stage results:
STF 08:33:11.264 - setUp: pass
STF 08:33:11.264 - execute: *fail*
STF 08:33:11.264 - teardown: pass
STF 08:33:11.264 -
STF 08:33:11.264 - Overall result: **FAILED**
DaaLoadTest_daa2_0_FAILED
```
|
test
|
daaloadtest test sanity system linux assert scavengerrootscanner hpp may be the same issue as running test daaloadtest daaloadtest start time wed aug epoch time ms test with nooptions stf s t f systemtest prereqs has been processed and set to home jenkins workspace test sanity system linux jvmtest systemtest systemtest prereqsretrieving amount of free space on drive containing home jenkins workspace test sanity system linux openjdk tests testconfig scripts testkitgen testconfig test output daaloadtest there is mb free stf g e n e r a t i o n stf checking jvm home jenkins workspace test sanity system linux openjdkbinary image bin stf starting process to generate scripts home jenkins workspace test sanity system linux openjdkbinary image bin bin java skipjansi true djava system class loader net adoptopenjdk stf runner stfclassloader classpath home jenkins workspace test sanity system linux openjdk tests testconfig scripts testkitgen jvmtest systemtest systemtest prereqs api jar home jenkins workspace test sanity system linux openjdk tests testconfig scripts testkitgen jvmtest systemtest systemtest prereqs core jar home jenkins workspace test sanity system linux jvmtest systemtest stf stf core scripts bin net adoptopenjdk stf runner stfrunner properties home jenkins workspace test sanity system linux openjdk tests testconfig scripts testkitgen testconfig test output daaloadtest daaloadtest stf parameters properties home jenkins workspace test sanity system linux jvmtest systemtest stf stf core config stf properties testdir home jenkins workspace test sanity system linux openjdk tests testconfig scripts testkitgen testconfig test output daaloadtest daaloadtest gen found test project test load class daaloadtest class dir home jenkins workspace test sanity system linux jvmtest systemtest systemtest test load bin gen found test project test load class net stf daaloadtest gen classpath directories used by project test load gen home jenkins workspace test sanity system linux jvmtest systemtest systemtest test load bin gen home jenkins workspace test sanity system linux jvmtest systemtest stf stf core bin gen home jenkins workspace test sanity system linux jvmtest systemtest stf stf load bin gen home jenkins workspace test sanity system linux jvmtest systemtest systemtest prereqs api jar gen home jenkins workspace test sanity system linux jvmtest systemtest systemtest prereqs core jar gen home jenkins workspace test sanity system linux jvmtest systemtest systemtest prereqs junit junit jar gen home jenkins workspace test sanity system linux jvmtest systemtest systemtest prereqs junit hamcrest core jar gen using mode nooptions values gen gen test command summary gen step stage command description gen gen execute run java run daa load test stf stf script generation completed stf stf stf s e t u p stf running setup perl home jenkins workspace test sanity system linux openjdk tests testconfig scripts testkitgen testconfig test output daaloadtest daaloadtest setup pl stf setup stage completed stf stf e x e c u t e stf running execute perl home jenkins workspace test sanity system linux openjdk tests testconfig scripts testkitgen testconfig test output daaloadtest daaloadtest execute pl stf stf java version stf running home jenkins workspace test sanity system linux openjdkbinary image bin bin java version openjdk version internal openjdk runtime environment build internal adhoc jenkins build eclipse vm build master jre linux bit jit enabled aot enabled omr jcl based on jdk stf stf step run daa load test stf run foreground process stf program home jenkins workspace test sanity system linux openjdkbinary image bin bin java stf mnemonic dlt stf echo echo on stf expectation clean run within stf stf running command home jenkins workspace test sanity system linux openjdkbinary image bin bin java xnocompressedrefs classpath home jenkins workspace test sanity system linux jvmtest systemtest stf stf load bin home jenkins workspace test sanity system linux jvmtest systemtest stf stf core bin home jenkins workspace test sanity system linux jvmtest systemtest systemtest prereqs api jar home jenkins workspace test sanity system linux jvmtest systemtest systemtest prereqs core jar home jenkins workspace test sanity system linux jvmtest systemtest systemtest prereqs junit junit jar home jenkins workspace test sanity system linux jvmtest systemtest systemtest prereqs junit hamcrest core jar home jenkins workspace test sanity system linux jvmtest systemtest systemtest test daa bin net adoptopenjdk loadtest loadtest resultsdir home jenkins workspace test sanity system linux openjdk tests testconfig scripts testkitgen testconfig test output daaloadtest daaloadtest results resultsprefix dlt reportfailurelimit abortatfailurelimit maxtotallogfilespace maxsinglelogsize suite daa threadcount suite daa totalnumbertests suite daa inventoryfile home jenkins workspace test sanity system linux openjdk tests testconfig scripts testkitgen testconfig test output daaloadtest daaloadtest results dlt inventory test load config inventories daa xml suite daa inventoryexcludefile none suite daa selection random suite daa seed suite daa repeatcount suite daa thinkingtime stf redirecting stderr to home jenkins workspace test sanity system linux openjdk tests testconfig scripts testkitgen testconfig test output daaloadtest daaloadtest results dlt stderr stf redirecting stdout to home jenkins workspace test sanity system linux openjdk tests testconfig scripts testkitgen testconfig test output daaloadtest daaloadtest results dlt stdout stf monitoring processes dlt dlt load test parameters dlt time limited false dlt abortifoutofmemory true dlt reportfailurelimit dlt abortatfailurelimit dlt maxtotallogfilespace dlt maxsinglelogsize dlt parameters for suite dlt suite name daa dlt number threads dlt supplied seed dlt inventory file home jenkins workspace test sanity system linux openjdk tests testconfig scripts testkitgen testconfig test output daaloadtest daaloadtest results dlt inventory test load config inventories daa xml dlt exclude file none dlt number tests dlt repeat count dlt thinking time dlt selection mode random dlt actual seed dlt parsing inventory file root home jenkins workspace test sanity system linux openjdk tests testconfig scripts testkitgen testconfig test output daaloadtest daaloadtest results dlt inventory file test load config inventories daa xml dlt final test list dlt arbitraryjava weighting dlt arbitraryjava weighting dlt arbitraryjava weighting dlt junit weighting dlt junit weighting dlt junit weighting dlt junit weighting dlt junit weighting dlt junit weighting dlt junit weighting dlt junit weighting dlt junit weighting dlt junit weighting dlt junit weighting dlt junit weighting dlt junit weighting dlt junit weighting dlt junit weighting dlt junit weighting dlt junit weighting dlt junit weighting dlt junit weighting dlt junit weighting dlt junit weighting dlt junit weighting dlt junit weighting dlt junit weighting dlt junit weighting dlt starting thread suite thread dlt starting thread suite thread dlt completed number of tests started dlt stderr object neither in heap nor stack allocated in thread load dlt stderr o slot dlt stderr o slot value dlt stderr pc dlt stderr frameswalked dlt stderr dlt stderr walksp dlt stderr literals dlt stderr jitinfo dlt stderr method org junit assert assertequals ljava lang string ljava lang object ljava lang object v jit dlt stderr stack dlt stderr assertion failed at gc glue java scavengerrootscanner hpp mm stackslotvalidator mm stackslotvalidator not on heap slotptr stacklocation walkstate validate env dlt stderr processing dump event traceassert detail at please wait dlt stderr jvm requested system dump using home jenkins workspace test sanity system linux openjdk tests testconfig test output daaloadtest daaloadtest results core dmp in response to an event dlt stderr proc sys kernel core pattern setting usr share apport apport p s c d p specifies that the core dump is to be piped to an external program attempting to rename either core or core dlt stderr dlt stderr system dump written to home jenkins workspace test sanity system linux openjdk tests testconfig test output daaloadtest daaloadtest results core dmp dlt stderr jvm requested java dump using home jenkins workspace test sanity system linux openjdk tests testconfig test output daaloadtest daaloadtest results javacore txt in response to an event stf found dump at home jenkins workspace test sanity system linux openjdk tests testconfig scripts testkitgen testconfig test output daaloadtest daaloadtest results javacore txt stf found dump at home jenkins workspace test sanity system linux openjdk tests testconfig scripts testkitgen testconfig test output daaloadtest daaloadtest results core dmp dlt stderr javacore file generated home jenkins workspace test sanity system linux openjdk tests testconfig scripts testkitgen testconfig test output daaloadtest daaloadtest results javacore txt dlt stderr core file generated home jenkins workspace test sanity system linux openjdk tests testconfig scripts testkitgen testconfig test output daaloadtest daaloadtest results core dmp dlt stderr java dump written to home jenkins workspace test sanity system linux openjdk tests testconfig test output daaloadtest daaloadtest results javacore txt dlt stderr jvm requested snap dump using home jenkins workspace test sanity system linux openjdk tests testconfig test output daaloadtest daaloadtest results snap trc in response to an event stf found dump at home jenkins workspace test sanity system linux openjdk tests testconfig scripts testkitgen testconfig test output daaloadtest daaloadtest results snap trc dlt stderr snap file generated home jenkins workspace test sanity system linux openjdk tests testconfig scripts testkitgen testconfig test output daaloadtest daaloadtest results snap trc dlt stderr snap dump written to home jenkins workspace test sanity system linux openjdk tests testconfig test output daaloadtest daaloadtest results snap trc dlt stderr processed dump event traceassert detail stf failed process dlt ended with exit code and not the expected exit code s stf monitoring report summary stf o process dlt has crashed unexpectedly stf killing processes dlt stf o process dlt is not running failed at step run daa load test expected return value actual at home jenkins workspace test sanity system linux openjdk tests testconfig scripts testkitgen testconfig test output daaloadtest daaloadtest execute pl line stf failed execute script failed expected return value actual stf stf t e a r d o w n stf running teardown perl home jenkins workspace test sanity system linux openjdk tests testconfig scripts testkitgen testconfig test output daaloadtest daaloadtest teardown pl stf teardown stage completed stf stf r e s u l t s stf stage results stf setup pass stf execute fail stf teardown pass stf stf overall result failed daaloadtest failed
| 1
|
348,664
| 10,451,216,609
|
IssuesEvent
|
2019-09-19 12:23:58
|
webcompat/web-bugs
|
https://api.github.com/repos/webcompat/web-bugs
|
closed
|
www.google.com - see bug description
|
browser-firefox-mobile engine-gecko priority-critical
|
<!-- @browser: Firefox Mobile 68.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 9; Mobile; rv:68.0) Gecko/68.0 Firefox/68.0 -->
<!-- @reported_with: mobile-reporter -->
**URL**: https://www.google.com/imgres?imgurl=https://66.media.tumblr.com/eb5dda082288bd247747f2ffbd38bf63/tumblr_oc8yypdUAG1rwz8xho2_1280.png&imgrefurl=http://objectheads.tumblr.com/post/149295569421/ramdot-barcodi-object-head-barcode&h=735&w=1280&tbnid=U50KIlYgiI2GEM:&q=object+head+barcode&tbnh=90&tbnw=156&usg=AI4_-kTOOQ8HMMwm5Q0wucZbl1dhD_S3YQ&vet=1&docid=l_Ljf6VZWRiJzM&hl=en&sa=X&ved=2ahUKEwjKtPSis9XkAhV_yIsBHWDzBZQQ9QEwAnoECAkQBg#spf=1568638903181
**Browser / Version**: Firefox Mobile 68.0
**Operating System**: Android
**Tested Another Browser**: Yes
**Problem type**: Something else
**Description**: only white image appers
**Steps to Reproduce**:
Whan i look into the page nothing appers
[](https://webcompat.com/uploads/2019/9/770d5e46-543b-453f-a455-44bc64498766.jpeg)
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20190909131947</li><li>channel: beta</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_
|
1.0
|
www.google.com - see bug description - <!-- @browser: Firefox Mobile 68.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 9; Mobile; rv:68.0) Gecko/68.0 Firefox/68.0 -->
<!-- @reported_with: mobile-reporter -->
**URL**: https://www.google.com/imgres?imgurl=https://66.media.tumblr.com/eb5dda082288bd247747f2ffbd38bf63/tumblr_oc8yypdUAG1rwz8xho2_1280.png&imgrefurl=http://objectheads.tumblr.com/post/149295569421/ramdot-barcodi-object-head-barcode&h=735&w=1280&tbnid=U50KIlYgiI2GEM:&q=object+head+barcode&tbnh=90&tbnw=156&usg=AI4_-kTOOQ8HMMwm5Q0wucZbl1dhD_S3YQ&vet=1&docid=l_Ljf6VZWRiJzM&hl=en&sa=X&ved=2ahUKEwjKtPSis9XkAhV_yIsBHWDzBZQQ9QEwAnoECAkQBg#spf=1568638903181
**Browser / Version**: Firefox Mobile 68.0
**Operating System**: Android
**Tested Another Browser**: Yes
**Problem type**: Something else
**Description**: only white image appers
**Steps to Reproduce**:
Whan i look into the page nothing appers
[](https://webcompat.com/uploads/2019/9/770d5e46-543b-453f-a455-44bc64498766.jpeg)
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20190909131947</li><li>channel: beta</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_
|
non_test
|
see bug description url browser version firefox mobile operating system android tested another browser yes problem type something else description only white image appers steps to reproduce whan i look into the page nothing appers browser configuration gfx webrender all false gfx webrender blob images true gfx webrender enabled false image mem shared true buildid channel beta hastouchscreen true mixed active content blocked false mixed passive content blocked false tracking content blocked false from with ❤️
| 0
|
675,040
| 23,075,444,779
|
IssuesEvent
|
2022-07-25 22:50:00
|
ploomber/ploomber
|
https://api.github.com/repos/ploomber/ploomber
|
closed
|
adding warning on Python 3.6 deprecation
|
high priority low effort
|
We won't be supporting Python 3.6 beginning in Ploomber 0.20
There's a PR that removes everything related to it: https://github.com/ploomber/ploomber/pull/876
But we haven't sent any warnings to users
we should add one here: https://github.com/ploomber/ploomber/blob/master/src/ploomber/__init__.py
essentially, if we detect they're running 3.6, we should display a message
that should be released in the next 0.19 release. on 0.20, we merge https://github.com/ploomber/ploomber/pull/876 and remove the warning
|
1.0
|
adding warning on Python 3.6 deprecation - We won't be supporting Python 3.6 beginning in Ploomber 0.20
There's a PR that removes everything related to it: https://github.com/ploomber/ploomber/pull/876
But we haven't sent any warnings to users
we should add one here: https://github.com/ploomber/ploomber/blob/master/src/ploomber/__init__.py
essentially, if we detect they're running 3.6, we should display a message
that should be released in the next 0.19 release. on 0.20, we merge https://github.com/ploomber/ploomber/pull/876 and remove the warning
|
non_test
|
adding warning on python deprecation we won t be supporting python beginning in ploomber there s a pr that removes everything related to it but we haven t sent any warnings to users we should add one here essentially if we detect they re running we should display a message that should be released in the next release on we merge and remove the warning
| 0
|
23,461
| 11,887,090,231
|
IssuesEvent
|
2020-03-28 00:06:52
|
MicrosoftDocs/azure-docs
|
https://api.github.com/repos/MicrosoftDocs/azure-docs
|
closed
|
How exactly does CoreDNS know of the configmap without having it as configVolume?
|
Pri2 container-service/svc cxp product-question triaged
|
I tried the various examples with our installation but to no avail. I asked myself how CoreDNS even knows of the ConfigMap without having it mounted into the pod as ConfigVolume? The guide doesn't mention it and thus I didn't do it either....
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 2f95537e-770a-739c-0175-4447a995f8b2
* Version Independent ID: 6c9a1132-05af-70f1-5a2b-8dad56de9cc3
* Content: [Customize CoreDNS for Azure Kubernetes Service (AKS) - Azure Kubernetes Service](https://docs.microsoft.com/en-us/azure/aks/coredns-custom#feedback)
* Content Source: [articles/aks/coredns-custom.md](https://github.com/Microsoft/azure-docs/blob/master/articles/aks/coredns-custom.md)
* Service: **container-service**
* GitHub Login: @jnoller
* Microsoft Alias: **jenoller**
|
1.0
|
How exactly does CoreDNS know of the configmap without having it as configVolume? - I tried the various examples with our installation but to no avail. I asked myself how CoreDNS even knows of the ConfigMap without having it mounted into the pod as ConfigVolume? The guide doesn't mention it and thus I didn't do it either....
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 2f95537e-770a-739c-0175-4447a995f8b2
* Version Independent ID: 6c9a1132-05af-70f1-5a2b-8dad56de9cc3
* Content: [Customize CoreDNS for Azure Kubernetes Service (AKS) - Azure Kubernetes Service](https://docs.microsoft.com/en-us/azure/aks/coredns-custom#feedback)
* Content Source: [articles/aks/coredns-custom.md](https://github.com/Microsoft/azure-docs/blob/master/articles/aks/coredns-custom.md)
* Service: **container-service**
* GitHub Login: @jnoller
* Microsoft Alias: **jenoller**
|
non_test
|
how exactly does coredns know of the configmap without having it as configvolume i tried the various examples with our installation but to no avail i asked myself how coredns even knows of the configmap without having it mounted into the pod as configvolume the guide doesn t mention it and thus i didn t do it either document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source service container service github login jnoller microsoft alias jenoller
| 0
|
1,794
| 3,962,157,034
|
IssuesEvent
|
2016-05-02 15:46:06
|
IBM-Bluemix/logistics-wizard
|
https://api.github.com/repos/IBM-Bluemix/logistics-wizard
|
opened
|
Controller-ERP Interface
|
controller-service erp-service task
|
Determine how the controller service will be interfacing with the ERP API
|
2.0
|
Controller-ERP Interface - Determine how the controller service will be interfacing with the ERP API
|
non_test
|
controller erp interface determine how the controller service will be interfacing with the erp api
| 0
|
185,494
| 21,791,045,117
|
IssuesEvent
|
2022-05-14 22:46:51
|
CliffCrerar/brendons-cat
|
https://api.github.com/repos/CliffCrerar/brendons-cat
|
closed
|
CVE-2021-23343 (High) detected in path-parse-1.0.6.tgz - autoclosed
|
security vulnerability
|
## CVE-2021-23343 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>path-parse-1.0.6.tgz</b></p></summary>
<p>Node.js path.parse() ponyfill</p>
<p>Library home page: <a href="https://registry.npmjs.org/path-parse/-/path-parse-1.0.6.tgz">https://registry.npmjs.org/path-parse/-/path-parse-1.0.6.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/path-parse/package.json</p>
<p>
Dependency Hierarchy:
- node-sass-4.14.1.tgz (Root Library)
- meow-3.7.0.tgz
- normalize-package-data-2.5.0.tgz
- resolve-1.17.0.tgz
- :x: **path-parse-1.0.6.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/CliffCrerar/brendons-cat/commit/665b78166390b5e3881e43ae42cf1bc6cf1f6486">665b78166390b5e3881e43ae42cf1bc6cf1f6486</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>
All versions of package path-parse are vulnerable to Regular Expression Denial of Service (ReDoS) via splitDeviceRe, splitTailRe, and splitPathRe regular expressions. ReDoS exhibits polynomial worst-case time complexity.
<p>Publish Date: 2021-05-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23343>CVE-2021-23343</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/jbgutierrez/path-parse/issues/8">https://github.com/jbgutierrez/path-parse/issues/8</a></p>
<p>Release Date: 2021-05-04</p>
<p>Fix Resolution (path-parse): 1.0.7</p>
<p>Direct dependency fix Resolution (node-sass): 5.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2021-23343 (High) detected in path-parse-1.0.6.tgz - autoclosed - ## CVE-2021-23343 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>path-parse-1.0.6.tgz</b></p></summary>
<p>Node.js path.parse() ponyfill</p>
<p>Library home page: <a href="https://registry.npmjs.org/path-parse/-/path-parse-1.0.6.tgz">https://registry.npmjs.org/path-parse/-/path-parse-1.0.6.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/path-parse/package.json</p>
<p>
Dependency Hierarchy:
- node-sass-4.14.1.tgz (Root Library)
- meow-3.7.0.tgz
- normalize-package-data-2.5.0.tgz
- resolve-1.17.0.tgz
- :x: **path-parse-1.0.6.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/CliffCrerar/brendons-cat/commit/665b78166390b5e3881e43ae42cf1bc6cf1f6486">665b78166390b5e3881e43ae42cf1bc6cf1f6486</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>
All versions of package path-parse are vulnerable to Regular Expression Denial of Service (ReDoS) via splitDeviceRe, splitTailRe, and splitPathRe regular expressions. ReDoS exhibits polynomial worst-case time complexity.
<p>Publish Date: 2021-05-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23343>CVE-2021-23343</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/jbgutierrez/path-parse/issues/8">https://github.com/jbgutierrez/path-parse/issues/8</a></p>
<p>Release Date: 2021-05-04</p>
<p>Fix Resolution (path-parse): 1.0.7</p>
<p>Direct dependency fix Resolution (node-sass): 5.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_test
|
cve high detected in path parse tgz autoclosed cve high severity vulnerability vulnerable library path parse tgz node js path parse ponyfill library home page a href path to dependency file package json path to vulnerable library node modules path parse package json dependency hierarchy node sass tgz root library meow tgz normalize package data tgz resolve tgz x path parse tgz vulnerable library found in head commit a href found in base branch master vulnerability details all versions of package path parse are vulnerable to regular expression denial of service redos via splitdevicere splittailre and splitpathre regular expressions redos exhibits polynomial worst case time complexity publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution path parse direct dependency fix resolution node sass step up your open source security game with whitesource
| 0
|
210,504
| 23,754,807,505
|
IssuesEvent
|
2022-09-01 01:18:00
|
turkdevops/sourcegraph
|
https://api.github.com/repos/turkdevops/sourcegraph
|
closed
|
CVE-2021-37713 (High) detected in tar-4.4.13.tgz - autoclosed
|
security vulnerability
|
## CVE-2021-37713 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tar-4.4.13.tgz</b></p></summary>
<p>tar for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-4.4.13.tgz">https://registry.npmjs.org/tar/-/tar-4.4.13.tgz</a></p>
<p>
Dependency Hierarchy:
- open-color-1.7.0.tgz (Root Library)
- npm-6.13.4.tgz
- :x: **tar-4.4.13.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/turkdevops/sourcegraph/commit/5a4a7def9ddff6354e22069c494feb0f30196e36">5a4a7def9ddff6354e22069c494feb0f30196e36</a></p>
<p>Found in base branch: <b>dev/seed-tool</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The npm package "tar" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted. This is, in part, accomplished by sanitizing absolute paths of entries within the archive, skipping archive entries that contain `..` path portions, and resolving the sanitized paths against the extraction target directory. This logic was insufficient on Windows systems when extracting tar files that contained a path that was not an absolute path, but specified a drive letter different from the extraction target, such as `C:some\path`. If the drive letter does not match the extraction target, for example `D:\extraction\dir`, then the result of `path.resolve(extractionDirectory, entryPath)` would resolve against the current working directory on the `C:` drive, rather than the extraction target directory. Additionally, a `..` portion of the path could occur immediately after the drive letter, such as `C:../foo`, and was not properly sanitized by the logic that checked for `..` within the normalized and split portions of the path. This only affects users of `node-tar` on Windows systems. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. There is no reasonable way to work around this issue without performing the same path normalization procedures that node-tar now does. Users are encouraged to upgrade to the latest patched versions of node-tar, rather than attempt to sanitize paths themselves.
<p>Publish Date: 2021-08-31
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-37713>CVE-2021-37713</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/npm/node-tar/security/advisories/GHSA-5955-9wpr-37jh">https://github.com/npm/node-tar/security/advisories/GHSA-5955-9wpr-37jh</a></p>
<p>Release Date: 2021-08-31</p>
<p>Fix Resolution (tar): 4.4.18</p>
<p>Direct dependency fix Resolution (open-color): 1.8.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2021-37713 (High) detected in tar-4.4.13.tgz - autoclosed - ## CVE-2021-37713 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tar-4.4.13.tgz</b></p></summary>
<p>tar for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-4.4.13.tgz">https://registry.npmjs.org/tar/-/tar-4.4.13.tgz</a></p>
<p>
Dependency Hierarchy:
- open-color-1.7.0.tgz (Root Library)
- npm-6.13.4.tgz
- :x: **tar-4.4.13.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/turkdevops/sourcegraph/commit/5a4a7def9ddff6354e22069c494feb0f30196e36">5a4a7def9ddff6354e22069c494feb0f30196e36</a></p>
<p>Found in base branch: <b>dev/seed-tool</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The npm package "tar" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted. This is, in part, accomplished by sanitizing absolute paths of entries within the archive, skipping archive entries that contain `..` path portions, and resolving the sanitized paths against the extraction target directory. This logic was insufficient on Windows systems when extracting tar files that contained a path that was not an absolute path, but specified a drive letter different from the extraction target, such as `C:some\path`. If the drive letter does not match the extraction target, for example `D:\extraction\dir`, then the result of `path.resolve(extractionDirectory, entryPath)` would resolve against the current working directory on the `C:` drive, rather than the extraction target directory. Additionally, a `..` portion of the path could occur immediately after the drive letter, such as `C:../foo`, and was not properly sanitized by the logic that checked for `..` within the normalized and split portions of the path. This only affects users of `node-tar` on Windows systems. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. There is no reasonable way to work around this issue without performing the same path normalization procedures that node-tar now does. Users are encouraged to upgrade to the latest patched versions of node-tar, rather than attempt to sanitize paths themselves.
<p>Publish Date: 2021-08-31
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-37713>CVE-2021-37713</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/npm/node-tar/security/advisories/GHSA-5955-9wpr-37jh">https://github.com/npm/node-tar/security/advisories/GHSA-5955-9wpr-37jh</a></p>
<p>Release Date: 2021-08-31</p>
<p>Fix Resolution (tar): 4.4.18</p>
<p>Direct dependency fix Resolution (open-color): 1.8.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_test
|
cve high detected in tar tgz autoclosed cve high severity vulnerability vulnerable library tar tgz tar for node library home page a href dependency hierarchy open color tgz root library npm tgz x tar tgz vulnerable library found in head commit a href found in base branch dev seed tool vulnerability details the npm package tar aka node tar before versions and has an arbitrary file creation overwrite and arbitrary code execution vulnerability node tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted this is in part accomplished by sanitizing absolute paths of entries within the archive skipping archive entries that contain path portions and resolving the sanitized paths against the extraction target directory this logic was insufficient on windows systems when extracting tar files that contained a path that was not an absolute path but specified a drive letter different from the extraction target such as c some path if the drive letter does not match the extraction target for example d extraction dir then the result of path resolve extractiondirectory entrypath would resolve against the current working directory on the c drive rather than the extraction target directory additionally a portion of the path could occur immediately after the drive letter such as c foo and was not properly sanitized by the logic that checked for within the normalized and split portions of the path this only affects users of node tar on windows systems these issues were addressed in releases and the branch of node tar has been deprecated and did not receive patches for these issues if you are still using a release we recommend you update to a more recent version of node tar there is no reasonable way to work around this issue without performing the same path normalization procedures that node tar now does users are encouraged to upgrade to the latest patched versions of node tar rather than attempt to sanitize paths themselves publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution tar direct dependency fix resolution open color step up your open source security game with mend
| 0
|
113,966
| 9,669,728,254
|
IssuesEvent
|
2019-05-21 18:05:55
|
rancher/rancher
|
https://api.github.com/repos/rancher/rancher
|
closed
|
UI Shows only 1000 nodes on a fresh load
|
[zube]: To Test internal kind/bug priority/1 status/ready-for-review status/resolved status/to-test status/triaged team/cn
|
**Rancher versions:**
rancher/server or rancher/rancher: 2.0.x
**Infrastructure Stack versions:**
If you add more then 1000 nodes across all clusters and do a hard refresh on the global clusters tab you will only see the sum of all nodes equal a 1000.
|
2.0
|
UI Shows only 1000 nodes on a fresh load - **Rancher versions:**
rancher/server or rancher/rancher: 2.0.x
**Infrastructure Stack versions:**
If you add more then 1000 nodes across all clusters and do a hard refresh on the global clusters tab you will only see the sum of all nodes equal a 1000.
|
test
|
ui shows only nodes on a fresh load rancher versions rancher server or rancher rancher x infrastructure stack versions if you add more then nodes across all clusters and do a hard refresh on the global clusters tab you will only see the sum of all nodes equal a
| 1
|
44,888
| 5,659,063,980
|
IssuesEvent
|
2017-04-10 11:57:44
|
tgstation/tgstation
|
https://api.github.com/repos/tgstation/tgstation
|
closed
|
People with flashlight eyes can still see.
|
Bug Needs Reproducing/Testing
|
Right. So after I disconnected for thirty minutes, I came back to find I had been rather vividly abused. My arms were removed and my eyes had been replaced with flashlights.
More importantly, I was not blind as expected when possessing flashlight eyes. Or was that a joke when Kor said flashlight people can't see?
|
1.0
|
People with flashlight eyes can still see. - Right. So after I disconnected for thirty minutes, I came back to find I had been rather vividly abused. My arms were removed and my eyes had been replaced with flashlights.
More importantly, I was not blind as expected when possessing flashlight eyes. Or was that a joke when Kor said flashlight people can't see?
|
test
|
people with flashlight eyes can still see right so after i disconnected for thirty minutes i came back to find i had been rather vividly abused my arms were removed and my eyes had been replaced with flashlights more importantly i was not blind as expected when possessing flashlight eyes or was that a joke when kor said flashlight people can t see
| 1
|
1,955
| 30,634,560,649
|
IssuesEvent
|
2023-07-24 16:44:32
|
alcionai/corso
|
https://api.github.com/repos/alcionai/corso
|
opened
|
[Bug]: some data still unmasked when `--mask-sensitive-data` passed
|
bug supportability
|
### What happened?
when using the `--mask-sensitive-data` flag some information like the user display name (for OneDrive/Exchange) is still visible. For full and incremental backup shows the user display name still appears when connecting to the repo (progress output) and at the end of the run (unclear what's printing it)
Additionally, the tenant ID and user ID is found in some places in the logs when printing collection info/info about items being backed up
### Corso Version?
Corso v0.11.1 dev
### Where are you running Corso?
N/A
### Relevant log output
_No response_
|
True
|
[Bug]: some data still unmasked when `--mask-sensitive-data` passed - ### What happened?
when using the `--mask-sensitive-data` flag some information like the user display name (for OneDrive/Exchange) is still visible. For full and incremental backup shows the user display name still appears when connecting to the repo (progress output) and at the end of the run (unclear what's printing it)
Additionally, the tenant ID and user ID is found in some places in the logs when printing collection info/info about items being backed up
### Corso Version?
Corso v0.11.1 dev
### Where are you running Corso?
N/A
### Relevant log output
_No response_
|
non_test
|
some data still unmasked when mask sensitive data passed what happened when using the mask sensitive data flag some information like the user display name for onedrive exchange is still visible for full and incremental backup shows the user display name still appears when connecting to the repo progress output and at the end of the run unclear what s printing it additionally the tenant id and user id is found in some places in the logs when printing collection info info about items being backed up corso version corso dev where are you running corso n a relevant log output no response
| 0
|
91,511
| 8,306,649,504
|
IssuesEvent
|
2018-09-22 21:09:21
|
kartoza/LEDET_BIMS
|
https://api.github.com/repos/kartoza/LEDET_BIMS
|
closed
|
Links upload and links display don't correspond
|
bug testing
|
When I added BIMS links on the staging server and assigned them to categories, only the first one was added to the links page. Also, the information displayed for each link should be the name and not the description. The amount of characters allowed in the name should perhaps be increased too.
|
1.0
|
Links upload and links display don't correspond - When I added BIMS links on the staging server and assigned them to categories, only the first one was added to the links page. Also, the information displayed for each link should be the name and not the description. The amount of characters allowed in the name should perhaps be increased too.
|
test
|
links upload and links display don t correspond when i added bims links on the staging server and assigned them to categories only the first one was added to the links page also the information displayed for each link should be the name and not the description the amount of characters allowed in the name should perhaps be increased too
| 1
|
431,638
| 30,243,721,679
|
IssuesEvent
|
2023-07-06 15:02:46
|
FusionAuth/fusionauth-issues
|
https://api.github.com/repos/FusionAuth/fusionauth-issues
|
closed
|
Verification email is sent during registration although the user.create webhook failed
|
bug documentation already fixed
|
## Verification email is sent during registration although the user.create webhook failed
### Description
Verification email is sent during registration although the `user.create` webhook failed by returning a non-successful HTTP status code.
### Affects versions
- 1.32.1
- 1.32.0
### Steps to reproduce
Steps to reproduce the behavior:
1. Create a webhook for the event `user.create` that always returns a non-successful HTTP status code such as `400`
2. Configure a tenant to use this webhook with "All the webhooks must succeed"
3. Setup a valid SMTP server and registration verification using a code for the tenant
4. Try to create a register a new account
5. See that the account registration is blocked by the webhook failure
6. See that the user stills receives an verification code by email
### Expected behavior
I would expect the user not receiving a verification code by email as the registration process failed.
### Platform
- Device: Desktop
- OS: Windows 10
- Browser: Chrome 97
- PostgreSQL 11.9
### Related
- https://github.com/FusionAuth/fusionauth-issues/issues/2287
|
1.0
|
Verification email is sent during registration although the user.create webhook failed - ## Verification email is sent during registration although the user.create webhook failed
### Description
Verification email is sent during registration although the `user.create` webhook failed by returning a non-successful HTTP status code.
### Affects versions
- 1.32.1
- 1.32.0
### Steps to reproduce
Steps to reproduce the behavior:
1. Create a webhook for the event `user.create` that always returns a non-successful HTTP status code such as `400`
2. Configure a tenant to use this webhook with "All the webhooks must succeed"
3. Setup a valid SMTP server and registration verification using a code for the tenant
4. Try to create a register a new account
5. See that the account registration is blocked by the webhook failure
6. See that the user stills receives an verification code by email
### Expected behavior
I would expect the user not receiving a verification code by email as the registration process failed.
### Platform
- Device: Desktop
- OS: Windows 10
- Browser: Chrome 97
- PostgreSQL 11.9
### Related
- https://github.com/FusionAuth/fusionauth-issues/issues/2287
|
non_test
|
verification email is sent during registration although the user create webhook failed verification email is sent during registration although the user create webhook failed description verification email is sent during registration although the user create webhook failed by returning a non successful http status code affects versions steps to reproduce steps to reproduce the behavior create a webhook for the event user create that always returns a non successful http status code such as configure a tenant to use this webhook with all the webhooks must succeed setup a valid smtp server and registration verification using a code for the tenant try to create a register a new account see that the account registration is blocked by the webhook failure see that the user stills receives an verification code by email expected behavior i would expect the user not receiving a verification code by email as the registration process failed platform device desktop os windows browser chrome postgresql related
| 0
|
11,507
| 7,574,534,649
|
IssuesEvent
|
2018-04-23 21:17:50
|
TopicFriends/TopicFriends
|
https://api.github.com/repos/TopicFriends/TopicFriends
|
closed
|
Performance: Users List: disable the "fancy" CSS animation when items appear
|
Mobile optimization performance
|
The animation can be quite costly, especially on mobile.
|
True
|
Performance: Users List: disable the "fancy" CSS animation when items appear - The animation can be quite costly, especially on mobile.
|
non_test
|
performance users list disable the fancy css animation when items appear the animation can be quite costly especially on mobile
| 0
|
91,979
| 8,335,737,731
|
IssuesEvent
|
2018-09-28 04:10:41
|
m4n3dw0lf/pythem
|
https://api.github.com/repos/m4n3dw0lf/pythem
|
closed
|
Tests for module imports
|
enhancement tests
|
Simple initial tests and docs, example of run:
running: `python setup.py test`
example of output:
Success:
```
* Test: pythem/tests/test_module_imports.py
✔ Can import <x> class
✔ Can import <y> class
```
Error:
```
* Test: pythem/tests/test_module_imports.py
✔ Can import <x> class
✔ Can import <y> class
✖ Test: pythem/tests/test_module_imports.py failed, reason:
Traceback (most recent call last):
```
|
1.0
|
Tests for module imports - Simple initial tests and docs, example of run:
running: `python setup.py test`
example of output:
Success:
```
* Test: pythem/tests/test_module_imports.py
✔ Can import <x> class
✔ Can import <y> class
```
Error:
```
* Test: pythem/tests/test_module_imports.py
✔ Can import <x> class
✔ Can import <y> class
✖ Test: pythem/tests/test_module_imports.py failed, reason:
Traceback (most recent call last):
```
|
test
|
tests for module imports simple initial tests and docs example of run running python setup py test example of output success test pythem tests test module imports py ✔ can import class ✔ can import class error test pythem tests test module imports py ✔ can import class ✔ can import class ✖ test pythem tests test module imports py failed reason traceback most recent call last
| 1
|
4,909
| 2,755,386,822
|
IssuesEvent
|
2015-04-26 16:09:03
|
BugBuster1701/banner
|
https://api.github.com/repos/BugBuster1701/banner
|
closed
|
[Insight] Unused method, property, variable or parameter - in modules/ModuleBannerStatistics.php, line 377
|
Insight Test is running
|
**[in modules/ModuleBannerStatistics.php, line 377](https://github.com/BugBuster1701/banner/blob/50c7a9adb3cff1a591f403f8a67a5333a1f43c52/modules/ModuleBannerStatistics.php#L377)**
> This `oriSize` local variable is declared but never used. You should remove it.
```php
default:
break;
}
$intWidth = $arrNewBannerImageSize[0];
$intHeight = $arrNewBannerImageSize[1];
$oriSize = $arrNewBannerImageSize[2];
switch ($arrImageSize[2])
{
case 1: // GIF
case 2: // JPG
```
---------------------
_Posted from [SensioLabsInsight](https://insight.sensiolabs.com/projects/288d9e0d-3710-438a-b8b1-ecfcc697ea86/analyses/2?status=violations)_
|
1.0
|
[Insight] Unused method, property, variable or parameter - in modules/ModuleBannerStatistics.php, line 377 - **[in modules/ModuleBannerStatistics.php, line 377](https://github.com/BugBuster1701/banner/blob/50c7a9adb3cff1a591f403f8a67a5333a1f43c52/modules/ModuleBannerStatistics.php#L377)**
> This `oriSize` local variable is declared but never used. You should remove it.
```php
default:
break;
}
$intWidth = $arrNewBannerImageSize[0];
$intHeight = $arrNewBannerImageSize[1];
$oriSize = $arrNewBannerImageSize[2];
switch ($arrImageSize[2])
{
case 1: // GIF
case 2: // JPG
```
---------------------
_Posted from [SensioLabsInsight](https://insight.sensiolabs.com/projects/288d9e0d-3710-438a-b8b1-ecfcc697ea86/analyses/2?status=violations)_
|
test
|
unused method property variable or parameter in modules modulebannerstatistics php line this orisize local variable is declared but never used you should remove it php default break intwidth arrnewbannerimagesize intheight arrnewbannerimagesize orisize arrnewbannerimagesize switch arrimagesize case gif case jpg posted from
| 1
|
15,398
| 2,851,438,552
|
IssuesEvent
|
2015-06-01 06:48:46
|
hazelcast/hazelcast
|
https://api.github.com/repos/hazelcast/hazelcast
|
reopened
|
[TEST-FAILURE] QueryIndexMigrationTest.testQueryWithIndexDuringJoin
|
Team: Core Type: Defect
|
```
java.lang.AssertionError: expected:<500> but was:<493>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:555)
at org.junit.Assert.assertEquals(Assert.java:542)
at com.hazelcast.map.query.QueryIndexMigrationTest.testQueryWithIndexDuringJoin(QueryIndexMigrationTest.java:232)
```
https://hazelcast-l337.ci.cloudbees.com/job/Hazelcast-3.x-OracleJDK1.6/com.hazelcast$hazelcast/429/testReport/junit/com.hazelcast.map.query/QueryIndexMigrationTest/testQueryWithIndexDuringJoin/
|
1.0
|
[TEST-FAILURE] QueryIndexMigrationTest.testQueryWithIndexDuringJoin - ```
java.lang.AssertionError: expected:<500> but was:<493>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:555)
at org.junit.Assert.assertEquals(Assert.java:542)
at com.hazelcast.map.query.QueryIndexMigrationTest.testQueryWithIndexDuringJoin(QueryIndexMigrationTest.java:232)
```
https://hazelcast-l337.ci.cloudbees.com/job/Hazelcast-3.x-OracleJDK1.6/com.hazelcast$hazelcast/429/testReport/junit/com.hazelcast.map.query/QueryIndexMigrationTest/testQueryWithIndexDuringJoin/
|
non_test
|
queryindexmigrationtest testquerywithindexduringjoin java lang assertionerror expected but was at org junit assert fail assert java at org junit assert failnotequals assert java at org junit assert assertequals assert java at org junit assert assertequals assert java at org junit assert assertequals assert java at com hazelcast map query queryindexmigrationtest testquerywithindexduringjoin queryindexmigrationtest java
| 0
|
41,986
| 10,735,703,851
|
IssuesEvent
|
2019-10-29 09:21:18
|
hazelcast/hazelcast
|
https://api.github.com/repos/hazelcast/hazelcast
|
closed
|
IMap.removeAll without index updates last access time and expiry time for all records
|
Module: IMap Team: Core Type: Defect
|
Calling IMap.removeAll without index updates last access time for all records. As a result expiration time is also updated when maxIdle eviction is used. If removeAll is called frequently then records are never removed by maxIdle.
Hazelcast version: 3.12.2
Attached unit test demonstrating this behaviour.
[IMapRemoveAllTest.java.zip](https://github.com/hazelcast/hazelcast/files/3573133/IMapRemoveAllTest.java.zip)
|
1.0
|
IMap.removeAll without index updates last access time and expiry time for all records - Calling IMap.removeAll without index updates last access time for all records. As a result expiration time is also updated when maxIdle eviction is used. If removeAll is called frequently then records are never removed by maxIdle.
Hazelcast version: 3.12.2
Attached unit test demonstrating this behaviour.
[IMapRemoveAllTest.java.zip](https://github.com/hazelcast/hazelcast/files/3573133/IMapRemoveAllTest.java.zip)
|
non_test
|
imap removeall without index updates last access time and expiry time for all records calling imap removeall without index updates last access time for all records as a result expiration time is also updated when maxidle eviction is used if removeall is called frequently then records are never removed by maxidle hazelcast version attached unit test demonstrating this behaviour
| 0
|
5,115
| 4,791,482,386
|
IssuesEvent
|
2016-10-31 12:45:02
|
Automattic/jetpack
|
https://api.github.com/repos/Automattic/jetpack
|
closed
|
Twenty Sixteen compat file loaded in the dashboard.
|
Performance Theme Tools [Team] tdiv [Type] Enhancement [Type] Good First Bug
|
I have jetpack loaded on a fresh wordpress install using development mode. I ran the audit tool and noticed that a file called `twentysixteen.css`.
Currently this file loads in the WordPress admin, but I can't find any page admin page where it is used.
I also noticed it is loading a non-minified file:
https://github.com/Automattic/jetpack/blob/a15e5028bc2fd10af3b8740ec69d0a3c0ab6eff9/modules/theme-tools/compat/twentysixteen.php#L15-L28
I suggest we load a minified version, and not in the WordPress Admin. Looks like the same might happen with the `twentyfifteen.css` file.
|
True
|
Twenty Sixteen compat file loaded in the dashboard. - I have jetpack loaded on a fresh wordpress install using development mode. I ran the audit tool and noticed that a file called `twentysixteen.css`.
Currently this file loads in the WordPress admin, but I can't find any page admin page where it is used.
I also noticed it is loading a non-minified file:
https://github.com/Automattic/jetpack/blob/a15e5028bc2fd10af3b8740ec69d0a3c0ab6eff9/modules/theme-tools/compat/twentysixteen.php#L15-L28
I suggest we load a minified version, and not in the WordPress Admin. Looks like the same might happen with the `twentyfifteen.css` file.
|
non_test
|
twenty sixteen compat file loaded in the dashboard i have jetpack loaded on a fresh wordpress install using development mode i ran the audit tool and noticed that a file called twentysixteen css currently this file loads in the wordpress admin but i can t find any page admin page where it is used i also noticed it is loading a non minified file i suggest we load a minified version and not in the wordpress admin looks like the same might happen with the twentyfifteen css file
| 0
|
292,385
| 21,965,420,305
|
IssuesEvent
|
2022-05-24 19:46:04
|
golang/go
|
https://api.github.com/repos/golang/go
|
closed
|
builtin: description of close behavior of reading from closed channel is vague
|
Documentation NeedsFix
|
<!--
Please answer these questions before submitting your issue. Thanks!
-->
### What is the URL of the page with the issue?
https://pkg.go.dev/builtin#close
The documentation of the built in close function states explicitly:
```
The form
x, ok := <-c
will also set ok to false for a closed channel.
```
This comes after the sentence that states after every item has been read from the channel, but it does not seem clear to me that applies to this statement as well.
When reading from a closed channel that has unread elements in it. It seems intuitive that the behavior that currently exists should be the actual behavior of the language ie. reading from the channel should read all of the available elements, but the documentation currently suggests that is not the case and should be amended.
Wrote a small unit test:
```
func TestReadClosedChannel(t *testing.T) {
c := make(chan struct{}, 1)
c <- struct{}{}
close(c)
_, ok := <-c
assert.True(t, ok)
}
```
It seems that this was always the intention of the language to work this way, so this issue is just to ask that the documentation be made a little more clear for the close function.
|
1.0
|
builtin: description of close behavior of reading from closed channel is vague - <!--
Please answer these questions before submitting your issue. Thanks!
-->
### What is the URL of the page with the issue?
https://pkg.go.dev/builtin#close
The documentation of the built in close function states explicitly:
```
The form
x, ok := <-c
will also set ok to false for a closed channel.
```
This comes after the sentence that states after every item has been read from the channel, but it does not seem clear to me that applies to this statement as well.
When reading from a closed channel that has unread elements in it. It seems intuitive that the behavior that currently exists should be the actual behavior of the language ie. reading from the channel should read all of the available elements, but the documentation currently suggests that is not the case and should be amended.
Wrote a small unit test:
```
func TestReadClosedChannel(t *testing.T) {
c := make(chan struct{}, 1)
c <- struct{}{}
close(c)
_, ok := <-c
assert.True(t, ok)
}
```
It seems that this was always the intention of the language to work this way, so this issue is just to ask that the documentation be made a little more clear for the close function.
|
non_test
|
builtin description of close behavior of reading from closed channel is vague please answer these questions before submitting your issue thanks what is the url of the page with the issue the documentation of the built in close function states explicitly the form x ok c will also set ok to false for a closed channel this comes after the sentence that states after every item has been read from the channel but it does not seem clear to me that applies to this statement as well when reading from a closed channel that has unread elements in it it seems intuitive that the behavior that currently exists should be the actual behavior of the language ie reading from the channel should read all of the available elements but the documentation currently suggests that is not the case and should be amended wrote a small unit test func testreadclosedchannel t testing t c make chan struct c struct close c ok c assert true t ok it seems that this was always the intention of the language to work this way so this issue is just to ask that the documentation be made a little more clear for the close function
| 0
|
354
| 2,533,936,134
|
IssuesEvent
|
2015-01-24 11:42:34
|
jOOQ/jOOQ
|
https://api.github.com/repos/jOOQ/jOOQ
|
closed
|
Meta.getTables() also returns entries for indexes for PostgreSQL
|
C: DB: PostgreSQL C: Functionality P: Medium R: Fixed T: Defect
|
In PostgreSQL, `DatabaseMetaData.getTables()` also returns records for tables of type `INDEX`. jOOQ reproduces this weird behaviour when querying meta information through `Meta.getTables()`, which is wrong, of course
|
1.0
|
Meta.getTables() also returns entries for indexes for PostgreSQL - In PostgreSQL, `DatabaseMetaData.getTables()` also returns records for tables of type `INDEX`. jOOQ reproduces this weird behaviour when querying meta information through `Meta.getTables()`, which is wrong, of course
|
non_test
|
meta gettables also returns entries for indexes for postgresql in postgresql databasemetadata gettables also returns records for tables of type index jooq reproduces this weird behaviour when querying meta information through meta gettables which is wrong of course
| 0
|
30,717
| 7,245,845,239
|
IssuesEvent
|
2018-02-14 19:30:04
|
Fake-Api/FakeApi
|
https://api.github.com/repos/Fake-Api/FakeApi
|
closed
|
Remove duplicated validation
|
code duplicate
|
Similar blocks of code found in 2 locations. Consider refactoring.
|
1.0
|
Remove duplicated validation - Similar blocks of code found in 2 locations. Consider refactoring.
|
non_test
|
remove duplicated validation similar blocks of code found in locations consider refactoring
| 0
|
39,611
| 5,241,008,814
|
IssuesEvent
|
2017-01-31 14:42:41
|
ValveSoftware/Source-1-Games
|
https://api.github.com/repos/ValveSoftware/Source-1-Games
|
closed
|
[TF2] Some demos do not work anymore.
|
Need Retest Reviewed Team Fortress 2
|
This update seems to have partially broke the demo system as some demos no longer work.
It seems like only demos recorded while tournament mode is active still work.
Here is a demo recorded in a normal pub, which was used to test frame rate at high loads: https://dl.dropboxusercontent.com/u/31103105/benchmark1.dem
Here is a STV demo from an ESEA match (pov demos in tournament mode also work): https://dl.dropboxusercontent.com/u/31103105/esea_match_3333384.dem
While this isn't a huge deal (unlucky for the people who had replays they were planning on editing), it might be nice to look into it.
|
1.0
|
[TF2] Some demos do not work anymore. - This update seems to have partially broke the demo system as some demos no longer work.
It seems like only demos recorded while tournament mode is active still work.
Here is a demo recorded in a normal pub, which was used to test frame rate at high loads: https://dl.dropboxusercontent.com/u/31103105/benchmark1.dem
Here is a STV demo from an ESEA match (pov demos in tournament mode also work): https://dl.dropboxusercontent.com/u/31103105/esea_match_3333384.dem
While this isn't a huge deal (unlucky for the people who had replays they were planning on editing), it might be nice to look into it.
|
test
|
some demos do not work anymore this update seems to have partially broke the demo system as some demos no longer work it seems like only demos recorded while tournament mode is active still work here is a demo recorded in a normal pub which was used to test frame rate at high loads here is a stv demo from an esea match pov demos in tournament mode also work while this isn t a huge deal unlucky for the people who had replays they were planning on editing it might be nice to look into it
| 1
|
193,762
| 6,887,816,514
|
IssuesEvent
|
2017-11-22 01:42:16
|
minio/minio-go
|
https://api.github.com/repos/minio/minio-go
|
opened
|
gateway-gcs: testRemoveMultipleObjects functional test fails since gcs server cannot handle the requested number of files
|
priority: medium
|
When minio-go functional test `testRemoveMultipleObjects` is run against gateway-gcs, it creates 1100 files, each 8 bytes in size, and then tries to remove them. However, gcs server cannot handle the load and fails with `We encountered an internal error, please try again.` error message.
We just simply don't need to push the gcs server to the edge and use a much smaller number of files to test multiple object removal functionality.
|
1.0
|
gateway-gcs: testRemoveMultipleObjects functional test fails since gcs server cannot handle the requested number of files - When minio-go functional test `testRemoveMultipleObjects` is run against gateway-gcs, it creates 1100 files, each 8 bytes in size, and then tries to remove them. However, gcs server cannot handle the load and fails with `We encountered an internal error, please try again.` error message.
We just simply don't need to push the gcs server to the edge and use a much smaller number of files to test multiple object removal functionality.
|
non_test
|
gateway gcs testremovemultipleobjects functional test fails since gcs server cannot handle the requested number of files when minio go functional test testremovemultipleobjects is run against gateway gcs it creates files each bytes in size and then tries to remove them however gcs server cannot handle the load and fails with we encountered an internal error please try again error message we just simply don t need to push the gcs server to the edge and use a much smaller number of files to test multiple object removal functionality
| 0
|
302,035
| 26,118,919,799
|
IssuesEvent
|
2022-12-28 10:07:04
|
streamnative/pulsar
|
https://api.github.com/repos/streamnative/pulsar
|
opened
|
ISSUE-19089: Flaky-test: TopicFromMessageTest.testMultiTopicConsumerNoBatchShortName
|
component/test flaky-tests
|
Original Issue: apache/pulsar#19089
---
### Search before asking
- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.
### Example failure
https://github.com/apache/pulsar/actions/runs/3791285394/jobs/6446689017#step:10:1222
### Exception stacktrace
```
java.lang.AssertionError: expected [persistent://public/default/topic1] but found [persistent://public/default/topic2]
at org.testng.Assert.fail(Assert.java:110)
at org.testng.Assert.failNotEquals(Assert.java:1413)
at org.testng.Assert.assertEqualsImpl(Assert.java:149)
at org.testng.Assert.assertEquals(Assert.java:131)
at org.testng.Assert.assertEquals(Assert.java:655)
at org.testng.Assert.assertEquals(Assert.java:665)
at org.apache.pulsar.client.impl.TopicFromMessageTest.testMultiTopicConsumerNoBatchShortName(TopicFromMessageTest.java:81)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at org.testng.internal.invokers.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:139)
at org.testng.internal.invokers.InvokeMethodRunnable.runOne(InvokeMethodRunnable.java:47)
at org.testng.internal.invokers.InvokeMethodRunnable.call(InvokeMethodRunnable.java:76)
at org.testng.internal.invokers.InvokeMethodRunnable.call(InvokeMethodRunnable.java:11)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:833)
```
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
|
2.0
|
ISSUE-19089: Flaky-test: TopicFromMessageTest.testMultiTopicConsumerNoBatchShortName - Original Issue: apache/pulsar#19089
---
### Search before asking
- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.
### Example failure
https://github.com/apache/pulsar/actions/runs/3791285394/jobs/6446689017#step:10:1222
### Exception stacktrace
```
java.lang.AssertionError: expected [persistent://public/default/topic1] but found [persistent://public/default/topic2]
at org.testng.Assert.fail(Assert.java:110)
at org.testng.Assert.failNotEquals(Assert.java:1413)
at org.testng.Assert.assertEqualsImpl(Assert.java:149)
at org.testng.Assert.assertEquals(Assert.java:131)
at org.testng.Assert.assertEquals(Assert.java:655)
at org.testng.Assert.assertEquals(Assert.java:665)
at org.apache.pulsar.client.impl.TopicFromMessageTest.testMultiTopicConsumerNoBatchShortName(TopicFromMessageTest.java:81)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at org.testng.internal.invokers.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:139)
at org.testng.internal.invokers.InvokeMethodRunnable.runOne(InvokeMethodRunnable.java:47)
at org.testng.internal.invokers.InvokeMethodRunnable.call(InvokeMethodRunnable.java:76)
at org.testng.internal.invokers.InvokeMethodRunnable.call(InvokeMethodRunnable.java:11)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:833)
```
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
|
test
|
issue flaky test topicfrommessagetest testmultitopicconsumernobatchshortname original issue apache pulsar search before asking i searched in the and found nothing similar example failure exception stacktrace java lang assertionerror expected but found at org testng assert fail assert java at org testng assert failnotequals assert java at org testng assert assertequalsimpl assert java at org testng assert assertequals assert java at org testng assert assertequals assert java at org testng assert assertequals assert java at org apache pulsar client impl topicfrommessagetest testmultitopicconsumernobatchshortname topicfrommessagetest java at java base jdk internal reflect nativemethodaccessorimpl native method at java base jdk internal reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at java base jdk internal reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java base java lang reflect method invoke method java at org testng internal invokers methodinvocationhelper invokemethod methodinvocationhelper java at org testng internal invokers invokemethodrunnable runone invokemethodrunnable java at org testng internal invokers invokemethodrunnable call invokemethodrunnable java at org testng internal invokers invokemethodrunnable call invokemethodrunnable java at java base java util concurrent futuretask run futuretask java at java base java util concurrent threadpoolexecutor runworker threadpoolexecutor java at java base java util concurrent threadpoolexecutor worker run threadpoolexecutor java at java base java lang thread run thread java are you willing to submit a pr i m willing to submit a pr
| 1
|
916
| 2,519,954,690
|
IssuesEvent
|
2015-01-18 15:43:18
|
feelpp/feelpp
|
https://api.github.com/repos/feelpp/feelpp
|
closed
|
Add local/global interpolant tests
|
module:discr module:testsuite prio:high status:in development type:feature
|
In `feature/interpolate`, we have a new framework to deal with local/global interpolant for any finite element and not only Lagrange element like in develop.
tests should be added to `testsuite/feelinterpolation`
|
1.0
|
Add local/global interpolant tests - In `feature/interpolate`, we have a new framework to deal with local/global interpolant for any finite element and not only Lagrange element like in develop.
tests should be added to `testsuite/feelinterpolation`
|
test
|
add local global interpolant tests in feature interpolate we have a new framework to deal with local global interpolant for any finite element and not only lagrange element like in develop tests should be added to testsuite feelinterpolation
| 1
|
168,626
| 13,097,748,348
|
IssuesEvent
|
2020-08-03 18:03:59
|
cockroachdb/cockroach
|
https://api.github.com/repos/cockroachdb/cockroach
|
closed
|
roachtest: decommission/nodes=4/duration=1h0m0s failed
|
C-test-failure O-roachtest O-robot branch-master release-blocker
|
[(roachtest).decommission/nodes=4/duration=1h0m0s failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=2123156&tab=buildLog) on [master@0570f1a5a38536dddaec69f68a74ad6ce85b827d](https://github.com/cockroachdb/cockroach/commits/0570f1a5a38536dddaec69f68a74ad6ce85b827d):
```
The test failed on branch=master, cloud=gce:
test artifacts and logs in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/decommission/nodes=4/duration=1h0m0s/run_1
test_runner.go:801: test timed out (10h0m0s)
```
<details><summary>More</summary><p>
Artifacts: [/decommission/nodes=4/duration=1h0m0s](https://teamcity.cockroachdb.com/viewLog.html?buildId=2123156&tab=artifacts#/decommission/nodes=4/duration=1h0m0s)
[See this test on roachdash](https://roachdash.crdb.dev/?filter=status%3Aopen+t%3A.%2Adecommission%2Fnodes%3D4%2Fduration%3D1h0m0s.%2A&sort=title&restgroup=false&display=lastcommented+project)
<sub>powered by [pkg/cmd/internal/issues](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)</sub></p></details>
|
2.0
|
roachtest: decommission/nodes=4/duration=1h0m0s failed - [(roachtest).decommission/nodes=4/duration=1h0m0s failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=2123156&tab=buildLog) on [master@0570f1a5a38536dddaec69f68a74ad6ce85b827d](https://github.com/cockroachdb/cockroach/commits/0570f1a5a38536dddaec69f68a74ad6ce85b827d):
```
The test failed on branch=master, cloud=gce:
test artifacts and logs in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/decommission/nodes=4/duration=1h0m0s/run_1
test_runner.go:801: test timed out (10h0m0s)
```
<details><summary>More</summary><p>
Artifacts: [/decommission/nodes=4/duration=1h0m0s](https://teamcity.cockroachdb.com/viewLog.html?buildId=2123156&tab=artifacts#/decommission/nodes=4/duration=1h0m0s)
[See this test on roachdash](https://roachdash.crdb.dev/?filter=status%3Aopen+t%3A.%2Adecommission%2Fnodes%3D4%2Fduration%3D1h0m0s.%2A&sort=title&restgroup=false&display=lastcommented+project)
<sub>powered by [pkg/cmd/internal/issues](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)</sub></p></details>
|
test
|
roachtest decommission nodes duration failed on the test failed on branch master cloud gce test artifacts and logs in home agent work go src github com cockroachdb cockroach artifacts decommission nodes duration run test runner go test timed out more artifacts powered by
| 1
|
18,556
| 24,555,473,162
|
IssuesEvent
|
2022-10-12 15:32:42
|
GoogleCloudPlatform/fda-mystudies
|
https://api.github.com/repos/GoogleCloudPlatform/fda-mystudies
|
closed
|
[Android] [Offline indicator] Delete app account > I do not wish to delete my account button should be disabled in the confirmation screen
|
Bug P2 Android Process: Fixed Process: Tested QA Process: Tested dev
|
Delete app account > I do not wish to delete my account button should be disabled in the confirmation screen
|
3.0
|
[Android] [Offline indicator] Delete app account > I do not wish to delete my account button should be disabled in the confirmation screen - Delete app account > I do not wish to delete my account button should be disabled in the confirmation screen
|
non_test
|
delete app account i do not wish to delete my account button should be disabled in the confirmation screen delete app account i do not wish to delete my account button should be disabled in the confirmation screen
| 0
|
249,811
| 18,858,239,426
|
IssuesEvent
|
2021-11-12 09:32:27
|
xiongjya/pe
|
https://api.github.com/repos/xiongjya/pe
|
opened
|
Destroy marker in the Developer Guide
|
type.DocumentationBug severity.VeryLow
|
In the DG, the diagram in the screenshot below should show that the ShowCommand (and CommandResult) should be destroyed with a destroy marker.
However, there is no disclaimer given even if the diagram could not fit the destroy marker.
<!--session: 1636703730246-d6ea0c17-fe3a-4e0d-a03e-de7cd730cfe1-->
<!--Version: Web v3.4.1-->
|
1.0
|
Destroy marker in the Developer Guide - In the DG, the diagram in the screenshot below should show that the ShowCommand (and CommandResult) should be destroyed with a destroy marker.
However, there is no disclaimer given even if the diagram could not fit the destroy marker.
<!--session: 1636703730246-d6ea0c17-fe3a-4e0d-a03e-de7cd730cfe1-->
<!--Version: Web v3.4.1-->
|
non_test
|
destroy marker in the developer guide in the dg the diagram in the screenshot below should show that the showcommand and commandresult should be destroyed with a destroy marker however there is no disclaimer given even if the diagram could not fit the destroy marker
| 0
|
204,351
| 7,087,199,877
|
IssuesEvent
|
2018-01-11 17:01:07
|
DakuTree/manga-tracker
|
https://api.github.com/repos/DakuTree/manga-tracker
|
closed
|
Add custom updater support to myMangaReaderCMS
|
enhancement high-priority
|
More sites seem to be using this now. Could probably just scrape the latest page to make this work.
|
1.0
|
Add custom updater support to myMangaReaderCMS - More sites seem to be using this now. Could probably just scrape the latest page to make this work.
|
non_test
|
add custom updater support to mymangareadercms more sites seem to be using this now could probably just scrape the latest page to make this work
| 0
|
77,806
| 27,172,243,210
|
IssuesEvent
|
2023-02-17 20:35:22
|
primefaces/primefaces
|
https://api.github.com/repos/primefaces/primefaces
|
closed
|
ColorPicker: Incorrect Translation of Inputs
|
:lady_beetle: defect third-party
|
**Describe the defect**
I have a user complaining that some colors are not selectable and I confirmed even on the showcase : https://www.primefaces.org/showcase/ui/input/colorPicker.xhtml
If you try to input `RGB 0,48,108` or its hex value `00306C` you get `0,49,108` and `00316C`.
Not sure what happens here but I was expecting an input color to input my color without altering it !
after digging into colorPicker.js it looks like it always ends up setting values from HSB conversion, no mater where the user is updating value.
```javascript
if (ev) {
fillRGBFields(col, cal.get(0));
fillHexFields(col, cal.get(0));
fillHSBFields(col, cal.get(0));
}
```
where col is the HSB version of the selected color
|
1.0
|
ColorPicker: Incorrect Translation of Inputs - **Describe the defect**
I have a user complaining that some colors are not selectable and I confirmed even on the showcase : https://www.primefaces.org/showcase/ui/input/colorPicker.xhtml
If you try to input `RGB 0,48,108` or its hex value `00306C` you get `0,49,108` and `00316C`.
Not sure what happens here but I was expecting an input color to input my color without altering it !
after digging into colorPicker.js it looks like it always ends up setting values from HSB conversion, no mater where the user is updating value.
```javascript
if (ev) {
fillRGBFields(col, cal.get(0));
fillHexFields(col, cal.get(0));
fillHSBFields(col, cal.get(0));
}
```
where col is the HSB version of the selected color
|
non_test
|
colorpicker incorrect translation of inputs describe the defect i have a user complaining that some colors are not selectable and i confirmed even on the showcase if you try to input rgb or its hex value you get and not sure what happens here but i was expecting an input color to input my color without altering it after digging into colorpicker js it looks like it always ends up setting values from hsb conversion no mater where the user is updating value javascript if ev fillrgbfields col cal get fillhexfields col cal get fillhsbfields col cal get where col is the hsb version of the selected color
| 0
|
230,235
| 18,523,094,885
|
IssuesEvent
|
2021-10-20 17:05:20
|
Exa-Networks/exabgp
|
https://api.github.com/repos/Exa-Networks/exabgp
|
reopened
|
BGP-LS link NLRI not parsed
|
bug fixed-need-testing
|
**Describe the bug**
ExaBGP throws an python TypeError when receiving a bgp-ls link nlri update from a Huawei speaker
**To Reproduce**
Configure bgp-ls between Huawei router and ExaBGP, announce link nlri.
**Expected behavior**
I'd expect ExaBGP to correclty parse the update and not throw a traceback.
**Environment (please complete the following information):**
- OS: Ubuntu 20.04.3 LTS
- Version 4.2.4 and 4.2.11 behaves the same
```
fredrlon@ban-ztp:~$ env exabgp.log.all=true ./exabgp-4.2.11/sbin/exabgp -d ./conf.ini
fatal: not a git repository (or any of the parent directories): .git
17:57:05 | 840316 | welcome | Thank you for using ExaBGP
17:57:05 | 840316 | version | 4.2.11
17:57:05 | 840316 | interpreter | 3.8.10 (default, Jun 2 2021, 10:49:15) [GCC 9.4.0]
17:57:05 | 840316 | os | Linux ban-ztp 5.4.0-60-generic #67-Ubuntu SMP Tue Jan 5 18:31:36 UTC 2021 x86_64
17:57:05 | 840316 | installation | /home/fredrlon/exabgp-4.2.11
17:57:05 | 840316 | advice | environment file missing
17:57:05 | 840316 | advice | generate it using "exabgp --fi > /home/fredrlon/exabgp-4.2.11/etc/exabgp/exabgp.env"
17:57:05 | 840316 | cli control | named pipes for the cli are:
17:57:05 | 840316 | cli control | to send commands /run/exabgp/exabgp.in
17:57:05 | 840316 | cli control | to read responses /run/exabgp/exabgp.out
17:57:05 | 840316 | configuration | performing reload of exabgp 4.2.11
17:57:05 | 840316 | configuration | > neighbor | '130.244.96.1'
17:57:05 | 840316 | configuration | . local-address | '130.244.98.51'
17:57:05 | 840316 | configuration | . local-as | '1257'
17:57:05 | 840316 | configuration | . peer-as | '1257'
17:57:05 | 840316 | configuration | > family |
17:57:05 | 840316 | configuration | . bgp-ls | 'bgp-ls'
17:57:05 | 840316 | configuration | < family |
17:57:05 | 840316 | configuration | < neighbor |
17:57:05 | 840316 | reactor | new peer: neighbor 130.244.96.1 local-ip 130.244.98.51 local-as 1257 peer-as 1257 router-id 130.244.98.51 family-allowed in-open
17:57:05 | 840316 | reactor | loaded new configuration successfully
17:57:05 | 840316 | process | forked process api-internal-cli-e7fa4210
17:57:05 | 840316 | reactor | initialising connection to peer-1
17:57:05 | 840316 | outgoing-1 | attempting connection to 130.244.96.1:179
17:57:05 | 840316 | outgoing-1 | sending TCP payload ( 49) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0031 0104 04E9 00B4 82F4 6233 1402 0601 0440 0400 4702 0641 0400 0004 E902 0206 00
17:57:05 | 840316 | outgoing-1 | >> OPEN version=4 asn=1257 hold_time=180 router_id=130.244.98.51 capabilities=[Multiprotocol(bgp-ls bgp-ls), Extended Message(65535), ASN4(1257)]
17:57:05 | 840316 | outgoing-1 | received TCP payload ( 19) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 002D 01
17:57:05 | 840316 | outgoing-1 | received TCP payload ( 26) 0404 E900 B482 F460 0110 020E 0104 4004 0047 0200 4104 0000 04E9
17:57:05 | 840316 | outgoing-1 | << message of type OPEN
17:57:05 | 840316 | outgoing-1 | << OPEN version=4 asn=1257 hold_time=180 router_id=130.244.96.1 capabilities=[Multiprotocol(bgp-ls bgp-ls), Route Refresh, ASN4(1257)]
17:57:05 | 840316 | ka-outgoing-1 | receive-timer 60 second(s) left
17:57:05 | 840316 | outgoing-1 | sending TCP payload ( 19) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0013 04
17:57:05 | 840316 | outgoing-1 | >> KEEPALIVE (OPENCONFIRM)
17:57:05 | 840316 | outgoing-1 | received TCP payload ( 19) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0013 04
17:57:05 | 840316 | outgoing-1 | << message of type KEEPALIVE
17:57:05 | 840316 | ka-outgoing-1 | receive-timer 180 second(s) left
17:57:05 | 840316 | reactor | connected to peer-1 with outgoing-1 130.244.98.51-130.244.96.1
17:57:05 | 840316 | outgoing-1 | sending TCP payload ( 30) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 001E 0200 0000 0790 0F00 0340 0447
17:57:05 | 840316 | outgoing-1 | >> EOR bgp-ls bgp-ls
17:57:05 | 840316 | peer-1 | >> EOR(s)
17:57:05 | 840316 | outgoing-1 | received TCP payload ( 19) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 006A 02
17:57:05 | 840316 | outgoing-1 | received TCP payload ( 87) 0000 0053 4001 0102 4002 0080 0404 0000 0000 4005 0400 0000 6490 0E00 3A40 0447 0482 F460 0100 0001 002D 0300 0000 0000 0000 0001 0000 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 01
17:57:05 | 840316 | outgoing-1 | << message of type UPDATE
17:57:05 | 840316 | parser | parsing UPDATE ( 87) 0000 0053 4001 0102 4002 0080 0404 0000 0000 4005 0400 0000 6490 0E00 3A40 0447 0482 F460 0100 0001 002D 0300 0000 0000 0000 0001 0000 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 01
17:57:05 | 840316 | routes | withdrawn NLRI none
17:57:05 | 840316 | parser | attribute origin flag 0x40 type 0x01 len 0x01 payload 02
17:57:05 | 840316 | parser | attribute as-path flag 0x40 type 0x02 len 0x00
17:57:05 | 840316 | parser | attribute med flag 0x80 type 0x04 len 0x04 payload 0000 0000
17:57:05 | 840316 | parser | attribute local-preference flag 0x40 type 0x05 len 0x04 payload 0000 0064
17:57:05 | 840316 | parser | attribute mp-reach-nlri flag 0x90 type 0x0e len 0x3a payload 4004 4704 82F4 6001 0000 0100 2D03 0000 0000 0000 0000 0100 0020 0200 0004 0000 04E9 0201 0004 82F4 6001 0202 0004 0000 0011 0203 0004 82F4 6001
17:57:05 | 840316 | parser | NLRI bgp-ls bgp-ls without path-information payload 0001 002D 0300 0000 0000 0000 0001 0000 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 01
17:57:05 | 840316 | routes | announced NLRI none
17:57:05 | 840316 | parser | decoded UPDATE ( 0) json { "exabgp": "4.0.1", "time": 1631894225.9785688, "host" : "ban-ztp", "pid" : 840316, "ppid" : 839294, "counter": 1, "type": "update", "neighbor": { "address": { "local": "130.244.98.51", "peer": "130.244.96.1" }, "asn": { "local": 1257, "peer": 1257 } , "direction": "in", "message": { "update": { "attribute": { "origin": "incomplete", "med": 0, "local-preference": 100 }, "announce": { "bgp-ls bgp-ls": { "130.244.96.1": [ { "ls-nlri-type": "bgpls-node", "l3-routing-topology": 0, "protocol-id": 3, "node-descriptors": { "autonomous-system": 1257, "bgp-ls-identifier": "2197053441", "ospf-area-id": "0.0.0.17", "router-id": "130.244.96.1" }, "nexthop": "130.244.96.1" } ] } } } } } }
17:57:05 | 840316 | peer-1 | << UPDATE #1
17:57:05 | 840316 | peer-1 | UPDATE #1 nlri ( 2) { "ls-nlri-type": "bgpls-node", "l3-routing-topology": 0, "protocol-id": 3, "node-descriptors": { "autonomous-system": 1257, "bgp-ls-identifier": "2197053441", "ospf-area-id": "0.0.0.17", "router-id": "130.244.96.1" }, "nexthop": "130.244.96.1" }
17:57:05 | 840316 | outgoing-1 | received TCP payload ( 19) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0072 02
17:57:05 | 840316 | outgoing-1 | received TCP payload ( 95) 0000 005B 4001 0102 4002 0080 0404 0000 0000 4005 0400 0000 6480 1D05 0400 0001 2090 0E00 3A40 0447 0482 F460 0100 0001 002D 0300 0000 0000 0000 0001 0000 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 0D
17:57:05 | 840316 | outgoing-1 | << message of type UPDATE
17:57:05 | 840316 | parser | parsing UPDATE ( 95) 0000 005B 4001 0102 4002 0080 0404 0000 0000 4005 0400 0000 6480 1D05 0400 0001 2090 0E00 3A40 0447 0482 F460 0100 0001 002D 0300 0000 0000 0000 0001 0000 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 0D
17:57:05 | 840316 | routes | withdrawn NLRI none
17:57:05 | 840316 | parser | attribute origin flag 0x40 type 0x01 len 0x01 payload 02
17:57:05 | 840316 | parser | attribute as-path flag 0x40 type 0x02 len 0x00
17:57:05 | 840316 | parser | attribute med flag 0x80 type 0x04 len 0x04 payload 0000 0000
17:57:05 | 840316 | parser | attribute local-preference flag 0x40 type 0x05 len 0x04 payload 0000 0064
17:57:05 | 840316 | parser | attribute bgp-ls flag 0x80 type 0x1d len 0x05 payload 0400 0001 20
17:57:05 | 840316 | parser | attribute mp-reach-nlri flag 0x90 type 0x0e len 0x3a payload 4004 4704 82F4 6001 0000 0100 2D03 0000 0000 0000 0000 0100 0020 0200 0004 0000 04E9 0201 0004 82F4 6001 0202 0004 0000 0011 0203 0004 82F4 600D
17:57:05 | 840316 | parser | NLRI bgp-ls bgp-ls without path-information payload 0001 002D 0300 0000 0000 0000 0001 0000 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 0D
17:57:05 | 840316 | routes | announced NLRI none
17:57:05 | 840316 | parser | decoded UPDATE ( 0) json { "exabgp": "4.0.1", "time": 1631894225.986203, "host" : "ban-ztp", "pid" : 840316, "ppid" : 839294, "counter": 2, "type": "update", "neighbor": { "address": { "local": "130.244.98.51", "peer": "130.244.96.1" }, "asn": { "local": 1257, "peer": 1257 } , "direction": "in", "message": { "update": { "attribute": { "origin": "incomplete", "med": 0, "local-preference": 100, "bgp-ls": { "node-flags": {"O": 0, "T": 0, "E": 1, "B": 0, "R": 0, "V": 0, "RSV": 0} } }, "announce": { "bgp-ls bgp-ls": { "130.244.96.1": [ { "ls-nlri-type": "bgpls-node", "l3-routing-topology": 0, "protocol-id": 3, "node-descriptors": { "autonomous-system": 1257, "bgp-ls-identifier": "2197053441", "ospf-area-id": "0.0.0.17", "router-id": "130.244.96.13" }, "nexthop": "130.244.96.1" } ] } } } } } }
17:57:05 | 840316 | peer-1 | << UPDATE #2
17:57:05 | 840316 | peer-1 | UPDATE #2 nlri ( 2) { "ls-nlri-type": "bgpls-node", "l3-routing-topology": 0, "protocol-id": 3, "node-descriptors": { "autonomous-system": 1257, "bgp-ls-identifier": "2197053441", "ospf-area-id": "0.0.0.17", "router-id": "130.244.96.13" }, "nexthop": "130.244.96.1" }
17:57:05 | 840316 | outgoing-1 | received TCP payload ( 19) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0105 02
17:57:05 | 840316 | outgoing-1 | received TCP payload ( 242) 0000 00EE 4001 0102 4002 0080 0404 0000 0000 4005 0400 0000 6480 1D07 0447 0003 0003 E890 0E00 CB40 0447 0482 F460 0100 0002 005D 0300 0000 0000 0000 0001 0000 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 0101 0100 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 0D01 0200 0882 F460 5E82 F460 5F00 0200 5D03 0000 0000 0000 0000 0100 0020 0200 0004 0000 04E9 0201 0004 82F4 6001 0202 0004 0000 0011 0203 0004 82F4 600D 0101 0020 0200 0004 0000 04E9 0201 0004 82F4 6001 0202 0004 0000 0011 0203 0004 82F4 6001 0102 0008 82F4 605F 82F4 605E
17:57:05 | 840316 | outgoing-1 | << message of type UPDATE
17:57:05 | 840316 | parser | parsing UPDATE ( 242) 0000 00EE 4001 0102 4002 0080 0404 0000 0000 4005 0400 0000 6480 1D07 0447 0003 0003 E890 0E00 CB40 0447 0482 F460 0100 0002 005D 0300 0000 0000 0000 0001 0000 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 0101 0100 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 0D01 0200 0882 F460 5E82 F460 5F00 0200 5D03 0000 0000 0000 0000 0100 0020 0200 0004 0000 04E9 0201 0004 82F4 6001 0202 0004 0000 0011 0203 0004 82F4 600D 0101 0020 0200 0004 0000 04E9 0201 0004 82F4 6001 0202 0004 0000 0011 0203 0004 82F4 6001 0102 0008 82F4 605F 82F4 605E
17:57:05 | 840316 | routes | withdrawn NLRI none
17:57:05 | 840316 | parser | attribute origin flag 0x40 type 0x01 len 0x01 payload 02
17:57:05 | 840316 | parser | attribute as-path flag 0x40 type 0x02 len 0x00
17:57:05 | 840316 | parser | attribute med flag 0x80 type 0x04 len 0x04 payload 0000 0000
17:57:05 | 840316 | parser | attribute local-preference flag 0x40 type 0x05 len 0x04 payload 0000 0064
17:57:05 | 840316 | parser | attribute bgp-ls flag 0x80 type 0x1d len 0x07 payload 0447 0003 0003 E8
17:57:05 | 840316 | parser | attribute mp-reach-nlri flag 0x90 type 0x0e len 0xcb payload 4004 4704 82F4 6001 0000 0200 5D03 0000 0000 0000 0000 0100 0020 0200 0004 0000 04E9 0201 0004 82F4 6001 0202 0004 0000 0011 0203 0004 82F4 6001 0101 0020 0200 0004 0000 04E9 0201 0004 82F4 6001 0202 0004 0000 0011 0203 0004 82F4 600D 0102 0008 82F4 605E 82F4 605F 0002 005D 0300 0000 0000 0000 0001 0000 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 0D01 0100 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 0101 0200 0882 F460 5F82 F460 5E
17:57:05 | 840316 | parser | NLRI bgp-ls bgp-ls without path-information payload 0002 005D 0300 0000 0000 0000 0001 0000 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 0101 0100 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 0D01 0200 0882 F460 5E82 F460 5F00 0200 5D03 0000 0000 0000 0000 0100 0020 0200 0004 0000 04E9 0201 0004 82F4 6001 0202 0004 0000 0011 0203 0004 82F4 600D 0101 0020 0200 0004 0000 04E9 0201 0004 82F4 6001 0202 0004 0000 0011 0203 0004 82F4 6001 0102 0008 82F4 605F 82F4 605E
17:57:05 | 840316 | parser | NLRI bgp-ls bgp-ls without path-information payload 0002 005D 0300 0000 0000 0000 0001 0000 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 0D01 0100 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 0101 0200 0882 F460 5F82 F460 5E
17:57:05 | 840316 | routes | announced NLRI none
17:57:05 | 840316 | outgoing-1 | could not decode message "2"
17:57:05 | 840316 | outgoing-1 | object of type 'NoneType' has no len()
17:57:05 | 840316 | outgoing-1 | Traceback (most recent call last):
17:57:05 | 840316 | outgoing-1 | File "/home/fredrlon/exabgp-4.2.11/lib/exabgp/reactor/protocol.py", line 238, in read_message
17:57:05 | 840316 | outgoing-1 | message = Message.unpack(msg_id, body, self.negotiated)
17:57:05 | 840316 | outgoing-1 | File "/home/fredrlon/exabgp-4.2.11/lib/exabgp/bgp/message/message.py", line 180, in unpack
17:57:05 | 840316 | outgoing-1 | return cls.klass(message).unpack_message(data, negotiated)
17:57:05 | 840316 | outgoing-1 | File "/home/fredrlon/exabgp-4.2.11/lib/exabgp/bgp/message/update/__init__.py", line 291, in unpack_message
17:57:05 | 840316 | outgoing-1 | logger.debug(LazyFormat('decoded UPDATE', '', parsed), 'parser')
17:57:05 | 840316 | outgoing-1 | File "/home/fredrlon/exabgp-4.2.11/lib/exabgp/logger.py", line 355, in debug
17:57:05 | 840316 | outgoing-1 | self._report(message, source, level)
17:57:05 | 840316 | outgoing-1 | File "/home/fredrlon/exabgp-4.2.11/lib/exabgp/logger.py", line 347, in _report
17:57:05 | 840316 | outgoing-1 | for line in message.split('\n'):
17:57:05 | 840316 | outgoing-1 | File "/home/fredrlon/exabgp-4.2.11/lib/exabgp/logger.py", line 53, in split
17:57:05 | 840316 | outgoing-1 | return str(self).split(char)
17:57:05 | 840316 | outgoing-1 | File "/home/fredrlon/exabgp-4.2.11/lib/exabgp/logger.py", line 56, in __str__
17:57:05 | 840316 | outgoing-1 | formated = self.formater(self.message)
17:57:05 | 840316 | outgoing-1 | File "/home/fredrlon/exabgp-4.2.11/lib/exabgp/bgp/message/update/__init__.py", line 289, in parsed
17:57:05 | 840316 | outgoing-1 | return 'json %s' % Response.JSON(json_version).update(negotiated.neighbor, 'in', update, None, '', '')
17:57:05 | 840316 | outgoing-1 | File "/home/fredrlon/exabgp-4.2.11/lib/exabgp/reactor/api/response/json.py", line 321, in update
17:57:05 | 840316 | outgoing-1 | message = self._update(update)
17:57:05 | 840316 | outgoing-1 | File "/home/fredrlon/exabgp-4.2.11/lib/exabgp/reactor/api/response/json.py", line 287, in _update
17:57:05 | 840316 | outgoing-1 | m += ', '.join('%s' % nlri.json(compact=self.compact) for nlri in nlris)
17:57:05 | 840316 | outgoing-1 | File "/home/fredrlon/exabgp-4.2.11/lib/exabgp/reactor/api/response/json.py", line 287, in <genexpr>
17:57:05 | 840316 | outgoing-1 | m += ', '.join('%s' % nlri.json(compact=self.compact) for nlri in nlris)
17:57:05 | 840316 | outgoing-1 | File "/home/fredrlon/exabgp-4.2.11/lib/exabgp/bgp/message/update/nlri/bgpls/link.py", line 192, in json
17:57:05 | 840316 | outgoing-1 | if self.link_ids:
17:57:05 | 840316 | outgoing-1 | File "/home/fredrlon/exabgp-4.2.11/lib/exabgp/bgp/message/update/nlri/bgpls/tlvs/linkid.py", line 68, in __len__
17:57:05 | 840316 | outgoing-1 | return len(self._packed)
17:57:05 | 840316 | outgoing-1 | TypeError: object of type 'NoneType' has no len()
17:57:05 | 840316 | outgoing-1 |
17:57:05 | 840316 | outgoing-1 | sending TCP payload ( 62) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 003E 0301 0063 616E 206E 6F74 2064 6563 6F64 6520 7570 6461 7465 206D 6573 7361 6765 206F 6620 7479 7065 2022 3222
17:57:05 | 840316 | outgoing-1 | >> NOTIFICATION (1,0,"can not decode update message of type "2"")
17:57:05 | 840316 | outgoing-1 | peer reset, message [notification sent (1,0)] error[Message header error / Unspecific / can not decode update message of type "2"]
17:57:05 | 840316 | outgoing-1 | outgoing-1 130.244.98.51-130.244.96.1, closing connection
17:57:05 | 840316 | reactor | initialising connection to peer-1
17:57:06 | 840316 | outgoing-2 | attempting connection to 130.244.96.1:179
17:57:06 | 840316 | outgoing-2 | sending TCP payload ( 49) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0031 0104 04E9 00B4 82F4 6233 1402 0601 0440 0400 4702 0641 0400 0004 E902 0206 00
17:57:06 | 840316 | outgoing-2 | outgoing-2 130.244.98.51-130.244.96.1, closing connection
17:57:06 | 840316 | outgoing-2 | peer reset, message [closing connection] error[Broken TCP connection]
17:57:06 | 840316 | outgoing-2 | outgoing-2 130.244.98.51-130.244.96.1, closing connection
17:57:07 | 840316 | reactor | initialising connection to peer-1
17:57:07 | 840316 | outgoing-3 | attempting connection to 130.244.96.1:179
17:57:07 | 840316 | outgoing-3 | sending TCP payload ( 49) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0031 0104 04E9 00B4 82F4 6233 1402 0601 0440 0400 4702 0641 0400 0004 E902 0206 00
17:57:07 | 840316 | outgoing-3 | outgoing-3 130.244.98.51-130.244.96.1, closing connection
17:57:07 | 840316 | outgoing-3 | peer reset, message [closing connection] error[Broken TCP connection]
17:57:07 | 840316 | outgoing-3 | outgoing-3 130.244.98.51-130.244.96.1, closing connection
^C17:57:07 | 840316 | reactor | ^C received
17:57:07 | 840316 | reactor | performing shutdown
17:57:07 | 840316 | process | terminating process api-internal-cli-e7fa4210
fredrlon@ban-ztp:~$ [A^C
```
|
1.0
|
BGP-LS link NLRI not parsed - **Describe the bug**
ExaBGP throws an python TypeError when receiving a bgp-ls link nlri update from a Huawei speaker
**To Reproduce**
Configure bgp-ls between Huawei router and ExaBGP, announce link nlri.
**Expected behavior**
I'd expect ExaBGP to correclty parse the update and not throw a traceback.
**Environment (please complete the following information):**
- OS: Ubuntu 20.04.3 LTS
- Version 4.2.4 and 4.2.11 behaves the same
```
fredrlon@ban-ztp:~$ env exabgp.log.all=true ./exabgp-4.2.11/sbin/exabgp -d ./conf.ini
fatal: not a git repository (or any of the parent directories): .git
17:57:05 | 840316 | welcome | Thank you for using ExaBGP
17:57:05 | 840316 | version | 4.2.11
17:57:05 | 840316 | interpreter | 3.8.10 (default, Jun 2 2021, 10:49:15) [GCC 9.4.0]
17:57:05 | 840316 | os | Linux ban-ztp 5.4.0-60-generic #67-Ubuntu SMP Tue Jan 5 18:31:36 UTC 2021 x86_64
17:57:05 | 840316 | installation | /home/fredrlon/exabgp-4.2.11
17:57:05 | 840316 | advice | environment file missing
17:57:05 | 840316 | advice | generate it using "exabgp --fi > /home/fredrlon/exabgp-4.2.11/etc/exabgp/exabgp.env"
17:57:05 | 840316 | cli control | named pipes for the cli are:
17:57:05 | 840316 | cli control | to send commands /run/exabgp/exabgp.in
17:57:05 | 840316 | cli control | to read responses /run/exabgp/exabgp.out
17:57:05 | 840316 | configuration | performing reload of exabgp 4.2.11
17:57:05 | 840316 | configuration | > neighbor | '130.244.96.1'
17:57:05 | 840316 | configuration | . local-address | '130.244.98.51'
17:57:05 | 840316 | configuration | . local-as | '1257'
17:57:05 | 840316 | configuration | . peer-as | '1257'
17:57:05 | 840316 | configuration | > family |
17:57:05 | 840316 | configuration | . bgp-ls | 'bgp-ls'
17:57:05 | 840316 | configuration | < family |
17:57:05 | 840316 | configuration | < neighbor |
17:57:05 | 840316 | reactor | new peer: neighbor 130.244.96.1 local-ip 130.244.98.51 local-as 1257 peer-as 1257 router-id 130.244.98.51 family-allowed in-open
17:57:05 | 840316 | reactor | loaded new configuration successfully
17:57:05 | 840316 | process | forked process api-internal-cli-e7fa4210
17:57:05 | 840316 | reactor | initialising connection to peer-1
17:57:05 | 840316 | outgoing-1 | attempting connection to 130.244.96.1:179
17:57:05 | 840316 | outgoing-1 | sending TCP payload ( 49) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0031 0104 04E9 00B4 82F4 6233 1402 0601 0440 0400 4702 0641 0400 0004 E902 0206 00
17:57:05 | 840316 | outgoing-1 | >> OPEN version=4 asn=1257 hold_time=180 router_id=130.244.98.51 capabilities=[Multiprotocol(bgp-ls bgp-ls), Extended Message(65535), ASN4(1257)]
17:57:05 | 840316 | outgoing-1 | received TCP payload ( 19) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 002D 01
17:57:05 | 840316 | outgoing-1 | received TCP payload ( 26) 0404 E900 B482 F460 0110 020E 0104 4004 0047 0200 4104 0000 04E9
17:57:05 | 840316 | outgoing-1 | << message of type OPEN
17:57:05 | 840316 | outgoing-1 | << OPEN version=4 asn=1257 hold_time=180 router_id=130.244.96.1 capabilities=[Multiprotocol(bgp-ls bgp-ls), Route Refresh, ASN4(1257)]
17:57:05 | 840316 | ka-outgoing-1 | receive-timer 60 second(s) left
17:57:05 | 840316 | outgoing-1 | sending TCP payload ( 19) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0013 04
17:57:05 | 840316 | outgoing-1 | >> KEEPALIVE (OPENCONFIRM)
17:57:05 | 840316 | outgoing-1 | received TCP payload ( 19) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0013 04
17:57:05 | 840316 | outgoing-1 | << message of type KEEPALIVE
17:57:05 | 840316 | ka-outgoing-1 | receive-timer 180 second(s) left
17:57:05 | 840316 | reactor | connected to peer-1 with outgoing-1 130.244.98.51-130.244.96.1
17:57:05 | 840316 | outgoing-1 | sending TCP payload ( 30) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 001E 0200 0000 0790 0F00 0340 0447
17:57:05 | 840316 | outgoing-1 | >> EOR bgp-ls bgp-ls
17:57:05 | 840316 | peer-1 | >> EOR(s)
17:57:05 | 840316 | outgoing-1 | received TCP payload ( 19) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 006A 02
17:57:05 | 840316 | outgoing-1 | received TCP payload ( 87) 0000 0053 4001 0102 4002 0080 0404 0000 0000 4005 0400 0000 6490 0E00 3A40 0447 0482 F460 0100 0001 002D 0300 0000 0000 0000 0001 0000 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 01
17:57:05 | 840316 | outgoing-1 | << message of type UPDATE
17:57:05 | 840316 | parser | parsing UPDATE ( 87) 0000 0053 4001 0102 4002 0080 0404 0000 0000 4005 0400 0000 6490 0E00 3A40 0447 0482 F460 0100 0001 002D 0300 0000 0000 0000 0001 0000 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 01
17:57:05 | 840316 | routes | withdrawn NLRI none
17:57:05 | 840316 | parser | attribute origin flag 0x40 type 0x01 len 0x01 payload 02
17:57:05 | 840316 | parser | attribute as-path flag 0x40 type 0x02 len 0x00
17:57:05 | 840316 | parser | attribute med flag 0x80 type 0x04 len 0x04 payload 0000 0000
17:57:05 | 840316 | parser | attribute local-preference flag 0x40 type 0x05 len 0x04 payload 0000 0064
17:57:05 | 840316 | parser | attribute mp-reach-nlri flag 0x90 type 0x0e len 0x3a payload 4004 4704 82F4 6001 0000 0100 2D03 0000 0000 0000 0000 0100 0020 0200 0004 0000 04E9 0201 0004 82F4 6001 0202 0004 0000 0011 0203 0004 82F4 6001
17:57:05 | 840316 | parser | NLRI bgp-ls bgp-ls without path-information payload 0001 002D 0300 0000 0000 0000 0001 0000 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 01
17:57:05 | 840316 | routes | announced NLRI none
17:57:05 | 840316 | parser | decoded UPDATE ( 0) json { "exabgp": "4.0.1", "time": 1631894225.9785688, "host" : "ban-ztp", "pid" : 840316, "ppid" : 839294, "counter": 1, "type": "update", "neighbor": { "address": { "local": "130.244.98.51", "peer": "130.244.96.1" }, "asn": { "local": 1257, "peer": 1257 } , "direction": "in", "message": { "update": { "attribute": { "origin": "incomplete", "med": 0, "local-preference": 100 }, "announce": { "bgp-ls bgp-ls": { "130.244.96.1": [ { "ls-nlri-type": "bgpls-node", "l3-routing-topology": 0, "protocol-id": 3, "node-descriptors": { "autonomous-system": 1257, "bgp-ls-identifier": "2197053441", "ospf-area-id": "0.0.0.17", "router-id": "130.244.96.1" }, "nexthop": "130.244.96.1" } ] } } } } } }
17:57:05 | 840316 | peer-1 | << UPDATE #1
17:57:05 | 840316 | peer-1 | UPDATE #1 nlri ( 2) { "ls-nlri-type": "bgpls-node", "l3-routing-topology": 0, "protocol-id": 3, "node-descriptors": { "autonomous-system": 1257, "bgp-ls-identifier": "2197053441", "ospf-area-id": "0.0.0.17", "router-id": "130.244.96.1" }, "nexthop": "130.244.96.1" }
17:57:05 | 840316 | outgoing-1 | received TCP payload ( 19) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0072 02
17:57:05 | 840316 | outgoing-1 | received TCP payload ( 95) 0000 005B 4001 0102 4002 0080 0404 0000 0000 4005 0400 0000 6480 1D05 0400 0001 2090 0E00 3A40 0447 0482 F460 0100 0001 002D 0300 0000 0000 0000 0001 0000 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 0D
17:57:05 | 840316 | outgoing-1 | << message of type UPDATE
17:57:05 | 840316 | parser | parsing UPDATE ( 95) 0000 005B 4001 0102 4002 0080 0404 0000 0000 4005 0400 0000 6480 1D05 0400 0001 2090 0E00 3A40 0447 0482 F460 0100 0001 002D 0300 0000 0000 0000 0001 0000 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 0D
17:57:05 | 840316 | routes | withdrawn NLRI none
17:57:05 | 840316 | parser | attribute origin flag 0x40 type 0x01 len 0x01 payload 02
17:57:05 | 840316 | parser | attribute as-path flag 0x40 type 0x02 len 0x00
17:57:05 | 840316 | parser | attribute med flag 0x80 type 0x04 len 0x04 payload 0000 0000
17:57:05 | 840316 | parser | attribute local-preference flag 0x40 type 0x05 len 0x04 payload 0000 0064
17:57:05 | 840316 | parser | attribute bgp-ls flag 0x80 type 0x1d len 0x05 payload 0400 0001 20
17:57:05 | 840316 | parser | attribute mp-reach-nlri flag 0x90 type 0x0e len 0x3a payload 4004 4704 82F4 6001 0000 0100 2D03 0000 0000 0000 0000 0100 0020 0200 0004 0000 04E9 0201 0004 82F4 6001 0202 0004 0000 0011 0203 0004 82F4 600D
17:57:05 | 840316 | parser | NLRI bgp-ls bgp-ls without path-information payload 0001 002D 0300 0000 0000 0000 0001 0000 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 0D
17:57:05 | 840316 | routes | announced NLRI none
17:57:05 | 840316 | parser | decoded UPDATE ( 0) json { "exabgp": "4.0.1", "time": 1631894225.986203, "host" : "ban-ztp", "pid" : 840316, "ppid" : 839294, "counter": 2, "type": "update", "neighbor": { "address": { "local": "130.244.98.51", "peer": "130.244.96.1" }, "asn": { "local": 1257, "peer": 1257 } , "direction": "in", "message": { "update": { "attribute": { "origin": "incomplete", "med": 0, "local-preference": 100, "bgp-ls": { "node-flags": {"O": 0, "T": 0, "E": 1, "B": 0, "R": 0, "V": 0, "RSV": 0} } }, "announce": { "bgp-ls bgp-ls": { "130.244.96.1": [ { "ls-nlri-type": "bgpls-node", "l3-routing-topology": 0, "protocol-id": 3, "node-descriptors": { "autonomous-system": 1257, "bgp-ls-identifier": "2197053441", "ospf-area-id": "0.0.0.17", "router-id": "130.244.96.13" }, "nexthop": "130.244.96.1" } ] } } } } } }
17:57:05 | 840316 | peer-1 | << UPDATE #2
17:57:05 | 840316 | peer-1 | UPDATE #2 nlri ( 2) { "ls-nlri-type": "bgpls-node", "l3-routing-topology": 0, "protocol-id": 3, "node-descriptors": { "autonomous-system": 1257, "bgp-ls-identifier": "2197053441", "ospf-area-id": "0.0.0.17", "router-id": "130.244.96.13" }, "nexthop": "130.244.96.1" }
17:57:05 | 840316 | outgoing-1 | received TCP payload ( 19) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0105 02
17:57:05 | 840316 | outgoing-1 | received TCP payload ( 242) 0000 00EE 4001 0102 4002 0080 0404 0000 0000 4005 0400 0000 6480 1D07 0447 0003 0003 E890 0E00 CB40 0447 0482 F460 0100 0002 005D 0300 0000 0000 0000 0001 0000 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 0101 0100 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 0D01 0200 0882 F460 5E82 F460 5F00 0200 5D03 0000 0000 0000 0000 0100 0020 0200 0004 0000 04E9 0201 0004 82F4 6001 0202 0004 0000 0011 0203 0004 82F4 600D 0101 0020 0200 0004 0000 04E9 0201 0004 82F4 6001 0202 0004 0000 0011 0203 0004 82F4 6001 0102 0008 82F4 605F 82F4 605E
17:57:05 | 840316 | outgoing-1 | << message of type UPDATE
17:57:05 | 840316 | parser | parsing UPDATE ( 242) 0000 00EE 4001 0102 4002 0080 0404 0000 0000 4005 0400 0000 6480 1D07 0447 0003 0003 E890 0E00 CB40 0447 0482 F460 0100 0002 005D 0300 0000 0000 0000 0001 0000 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 0101 0100 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 0D01 0200 0882 F460 5E82 F460 5F00 0200 5D03 0000 0000 0000 0000 0100 0020 0200 0004 0000 04E9 0201 0004 82F4 6001 0202 0004 0000 0011 0203 0004 82F4 600D 0101 0020 0200 0004 0000 04E9 0201 0004 82F4 6001 0202 0004 0000 0011 0203 0004 82F4 6001 0102 0008 82F4 605F 82F4 605E
17:57:05 | 840316 | routes | withdrawn NLRI none
17:57:05 | 840316 | parser | attribute origin flag 0x40 type 0x01 len 0x01 payload 02
17:57:05 | 840316 | parser | attribute as-path flag 0x40 type 0x02 len 0x00
17:57:05 | 840316 | parser | attribute med flag 0x80 type 0x04 len 0x04 payload 0000 0000
17:57:05 | 840316 | parser | attribute local-preference flag 0x40 type 0x05 len 0x04 payload 0000 0064
17:57:05 | 840316 | parser | attribute bgp-ls flag 0x80 type 0x1d len 0x07 payload 0447 0003 0003 E8
17:57:05 | 840316 | parser | attribute mp-reach-nlri flag 0x90 type 0x0e len 0xcb payload 4004 4704 82F4 6001 0000 0200 5D03 0000 0000 0000 0000 0100 0020 0200 0004 0000 04E9 0201 0004 82F4 6001 0202 0004 0000 0011 0203 0004 82F4 6001 0101 0020 0200 0004 0000 04E9 0201 0004 82F4 6001 0202 0004 0000 0011 0203 0004 82F4 600D 0102 0008 82F4 605E 82F4 605F 0002 005D 0300 0000 0000 0000 0001 0000 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 0D01 0100 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 0101 0200 0882 F460 5F82 F460 5E
17:57:05 | 840316 | parser | NLRI bgp-ls bgp-ls without path-information payload 0002 005D 0300 0000 0000 0000 0001 0000 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 0101 0100 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 0D01 0200 0882 F460 5E82 F460 5F00 0200 5D03 0000 0000 0000 0000 0100 0020 0200 0004 0000 04E9 0201 0004 82F4 6001 0202 0004 0000 0011 0203 0004 82F4 600D 0101 0020 0200 0004 0000 04E9 0201 0004 82F4 6001 0202 0004 0000 0011 0203 0004 82F4 6001 0102 0008 82F4 605F 82F4 605E
17:57:05 | 840316 | parser | NLRI bgp-ls bgp-ls without path-information payload 0002 005D 0300 0000 0000 0000 0001 0000 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 0D01 0100 2002 0000 0400 0004 E902 0100 0482 F460 0102 0200 0400 0000 1102 0300 0482 F460 0101 0200 0882 F460 5F82 F460 5E
17:57:05 | 840316 | routes | announced NLRI none
17:57:05 | 840316 | outgoing-1 | could not decode message "2"
17:57:05 | 840316 | outgoing-1 | object of type 'NoneType' has no len()
17:57:05 | 840316 | outgoing-1 | Traceback (most recent call last):
17:57:05 | 840316 | outgoing-1 | File "/home/fredrlon/exabgp-4.2.11/lib/exabgp/reactor/protocol.py", line 238, in read_message
17:57:05 | 840316 | outgoing-1 | message = Message.unpack(msg_id, body, self.negotiated)
17:57:05 | 840316 | outgoing-1 | File "/home/fredrlon/exabgp-4.2.11/lib/exabgp/bgp/message/message.py", line 180, in unpack
17:57:05 | 840316 | outgoing-1 | return cls.klass(message).unpack_message(data, negotiated)
17:57:05 | 840316 | outgoing-1 | File "/home/fredrlon/exabgp-4.2.11/lib/exabgp/bgp/message/update/__init__.py", line 291, in unpack_message
17:57:05 | 840316 | outgoing-1 | logger.debug(LazyFormat('decoded UPDATE', '', parsed), 'parser')
17:57:05 | 840316 | outgoing-1 | File "/home/fredrlon/exabgp-4.2.11/lib/exabgp/logger.py", line 355, in debug
17:57:05 | 840316 | outgoing-1 | self._report(message, source, level)
17:57:05 | 840316 | outgoing-1 | File "/home/fredrlon/exabgp-4.2.11/lib/exabgp/logger.py", line 347, in _report
17:57:05 | 840316 | outgoing-1 | for line in message.split('\n'):
17:57:05 | 840316 | outgoing-1 | File "/home/fredrlon/exabgp-4.2.11/lib/exabgp/logger.py", line 53, in split
17:57:05 | 840316 | outgoing-1 | return str(self).split(char)
17:57:05 | 840316 | outgoing-1 | File "/home/fredrlon/exabgp-4.2.11/lib/exabgp/logger.py", line 56, in __str__
17:57:05 | 840316 | outgoing-1 | formated = self.formater(self.message)
17:57:05 | 840316 | outgoing-1 | File "/home/fredrlon/exabgp-4.2.11/lib/exabgp/bgp/message/update/__init__.py", line 289, in parsed
17:57:05 | 840316 | outgoing-1 | return 'json %s' % Response.JSON(json_version).update(negotiated.neighbor, 'in', update, None, '', '')
17:57:05 | 840316 | outgoing-1 | File "/home/fredrlon/exabgp-4.2.11/lib/exabgp/reactor/api/response/json.py", line 321, in update
17:57:05 | 840316 | outgoing-1 | message = self._update(update)
17:57:05 | 840316 | outgoing-1 | File "/home/fredrlon/exabgp-4.2.11/lib/exabgp/reactor/api/response/json.py", line 287, in _update
17:57:05 | 840316 | outgoing-1 | m += ', '.join('%s' % nlri.json(compact=self.compact) for nlri in nlris)
17:57:05 | 840316 | outgoing-1 | File "/home/fredrlon/exabgp-4.2.11/lib/exabgp/reactor/api/response/json.py", line 287, in <genexpr>
17:57:05 | 840316 | outgoing-1 | m += ', '.join('%s' % nlri.json(compact=self.compact) for nlri in nlris)
17:57:05 | 840316 | outgoing-1 | File "/home/fredrlon/exabgp-4.2.11/lib/exabgp/bgp/message/update/nlri/bgpls/link.py", line 192, in json
17:57:05 | 840316 | outgoing-1 | if self.link_ids:
17:57:05 | 840316 | outgoing-1 | File "/home/fredrlon/exabgp-4.2.11/lib/exabgp/bgp/message/update/nlri/bgpls/tlvs/linkid.py", line 68, in __len__
17:57:05 | 840316 | outgoing-1 | return len(self._packed)
17:57:05 | 840316 | outgoing-1 | TypeError: object of type 'NoneType' has no len()
17:57:05 | 840316 | outgoing-1 |
17:57:05 | 840316 | outgoing-1 | sending TCP payload ( 62) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 003E 0301 0063 616E 206E 6F74 2064 6563 6F64 6520 7570 6461 7465 206D 6573 7361 6765 206F 6620 7479 7065 2022 3222
17:57:05 | 840316 | outgoing-1 | >> NOTIFICATION (1,0,"can not decode update message of type "2"")
17:57:05 | 840316 | outgoing-1 | peer reset, message [notification sent (1,0)] error[Message header error / Unspecific / can not decode update message of type "2"]
17:57:05 | 840316 | outgoing-1 | outgoing-1 130.244.98.51-130.244.96.1, closing connection
17:57:05 | 840316 | reactor | initialising connection to peer-1
17:57:06 | 840316 | outgoing-2 | attempting connection to 130.244.96.1:179
17:57:06 | 840316 | outgoing-2 | sending TCP payload ( 49) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0031 0104 04E9 00B4 82F4 6233 1402 0601 0440 0400 4702 0641 0400 0004 E902 0206 00
17:57:06 | 840316 | outgoing-2 | outgoing-2 130.244.98.51-130.244.96.1, closing connection
17:57:06 | 840316 | outgoing-2 | peer reset, message [closing connection] error[Broken TCP connection]
17:57:06 | 840316 | outgoing-2 | outgoing-2 130.244.98.51-130.244.96.1, closing connection
17:57:07 | 840316 | reactor | initialising connection to peer-1
17:57:07 | 840316 | outgoing-3 | attempting connection to 130.244.96.1:179
17:57:07 | 840316 | outgoing-3 | sending TCP payload ( 49) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0031 0104 04E9 00B4 82F4 6233 1402 0601 0440 0400 4702 0641 0400 0004 E902 0206 00
17:57:07 | 840316 | outgoing-3 | outgoing-3 130.244.98.51-130.244.96.1, closing connection
17:57:07 | 840316 | outgoing-3 | peer reset, message [closing connection] error[Broken TCP connection]
17:57:07 | 840316 | outgoing-3 | outgoing-3 130.244.98.51-130.244.96.1, closing connection
^C17:57:07 | 840316 | reactor | ^C received
17:57:07 | 840316 | reactor | performing shutdown
17:57:07 | 840316 | process | terminating process api-internal-cli-e7fa4210
fredrlon@ban-ztp:~$ [A^C
```
|
test
|
bgp ls link nlri not parsed describe the bug exabgp throws an python typeerror when receiving a bgp ls link nlri update from a huawei speaker to reproduce configure bgp ls between huawei router and exabgp announce link nlri expected behavior i d expect exabgp to correclty parse the update and not throw a traceback environment please complete the following information os ubuntu lts version and behaves the same fredrlon ban ztp env exabgp log all true exabgp sbin exabgp d conf ini fatal not a git repository or any of the parent directories git welcome thank you for using exabgp version interpreter default jun os linux ban ztp generic ubuntu smp tue jan utc installation home fredrlon exabgp advice environment file missing advice generate it using exabgp fi home fredrlon exabgp etc exabgp exabgp env cli control named pipes for the cli are cli control to send commands run exabgp exabgp in cli control to read responses run exabgp exabgp out configuration performing reload of exabgp configuration neighbor configuration local address configuration local as configuration peer as configuration family configuration bgp ls bgp ls configuration family configuration neighbor reactor new peer neighbor local ip local as peer as router id family allowed in open reactor loaded new configuration successfully process forked process api internal cli reactor initialising connection to peer outgoing attempting connection to outgoing sending tcp payload ffff ffff ffff ffff ffff ffff ffff ffff outgoing open version asn hold time router id capabilities outgoing received tcp payload ffff ffff ffff ffff ffff ffff ffff ffff outgoing received tcp payload outgoing message of type open outgoing open version asn hold time router id capabilities ka outgoing receive timer second s left outgoing sending tcp payload ffff ffff ffff ffff ffff ffff ffff ffff outgoing keepalive openconfirm outgoing received tcp payload ffff ffff ffff ffff ffff ffff ffff ffff outgoing message of type keepalive ka outgoing receive timer second s left reactor connected to peer with outgoing outgoing sending tcp payload ffff ffff ffff ffff ffff ffff ffff ffff outgoing eor bgp ls bgp ls peer eor s outgoing received tcp payload ffff ffff ffff ffff ffff ffff ffff ffff outgoing received tcp payload outgoing message of type update parser parsing update routes withdrawn nlri none parser attribute origin flag type len payload parser attribute as path flag type len parser attribute med flag type len payload parser attribute local preference flag type len payload parser attribute mp reach nlri flag type len payload parser nlri bgp ls bgp ls without path information payload routes announced nlri none parser decoded update json exabgp time host ban ztp pid ppid counter type update neighbor address local peer asn local peer direction in message update attribute origin incomplete med local preference announce bgp ls bgp ls peer update peer update nlri ls nlri type bgpls node routing topology protocol id node descriptors autonomous system bgp ls identifier ospf area id router id nexthop outgoing received tcp payload ffff ffff ffff ffff ffff ffff ffff ffff outgoing received tcp payload outgoing message of type update parser parsing update routes withdrawn nlri none parser attribute origin flag type len payload parser attribute as path flag type len parser attribute med flag type len payload parser attribute local preference flag type len payload parser attribute bgp ls flag type len payload parser attribute mp reach nlri flag type len payload parser nlri bgp ls bgp ls without path information payload routes announced nlri none parser decoded update json exabgp time host ban ztp pid ppid counter type update neighbor address local peer asn local peer direction in message update attribute origin incomplete med local preference bgp ls node flags o t e b r v rsv announce bgp ls bgp ls peer update peer update nlri ls nlri type bgpls node routing topology protocol id node descriptors autonomous system bgp ls identifier ospf area id router id nexthop outgoing received tcp payload ffff ffff ffff ffff ffff ffff ffff ffff outgoing received tcp payload outgoing message of type update parser parsing update routes withdrawn nlri none parser attribute origin flag type len payload parser attribute as path flag type len parser attribute med flag type len payload parser attribute local preference flag type len payload parser attribute bgp ls flag type len payload parser attribute mp reach nlri flag type len payload parser nlri bgp ls bgp ls without path information payload parser nlri bgp ls bgp ls without path information payload routes announced nlri none outgoing could not decode message outgoing object of type nonetype has no len outgoing traceback most recent call last outgoing file home fredrlon exabgp lib exabgp reactor protocol py line in read message outgoing message message unpack msg id body self negotiated outgoing file home fredrlon exabgp lib exabgp bgp message message py line in unpack outgoing return cls klass message unpack message data negotiated outgoing file home fredrlon exabgp lib exabgp bgp message update init py line in unpack message outgoing logger debug lazyformat decoded update parsed parser outgoing file home fredrlon exabgp lib exabgp logger py line in debug outgoing self report message source level outgoing file home fredrlon exabgp lib exabgp logger py line in report outgoing for line in message split n outgoing file home fredrlon exabgp lib exabgp logger py line in split outgoing return str self split char outgoing file home fredrlon exabgp lib exabgp logger py line in str outgoing formated self formater self message outgoing file home fredrlon exabgp lib exabgp bgp message update init py line in parsed outgoing return json s response json json version update negotiated neighbor in update none outgoing file home fredrlon exabgp lib exabgp reactor api response json py line in update outgoing message self update update outgoing file home fredrlon exabgp lib exabgp reactor api response json py line in update outgoing m join s nlri json compact self compact for nlri in nlris outgoing file home fredrlon exabgp lib exabgp reactor api response json py line in outgoing m join s nlri json compact self compact for nlri in nlris outgoing file home fredrlon exabgp lib exabgp bgp message update nlri bgpls link py line in json outgoing if self link ids outgoing file home fredrlon exabgp lib exabgp bgp message update nlri bgpls tlvs linkid py line in len outgoing return len self packed outgoing typeerror object of type nonetype has no len outgoing outgoing sending tcp payload ffff ffff ffff ffff ffff ffff ffff ffff outgoing notification can not decode update message of type outgoing peer reset message error outgoing outgoing closing connection reactor initialising connection to peer outgoing attempting connection to outgoing sending tcp payload ffff ffff ffff ffff ffff ffff ffff ffff outgoing outgoing closing connection outgoing peer reset message error outgoing outgoing closing connection reactor initialising connection to peer outgoing attempting connection to outgoing sending tcp payload ffff ffff ffff ffff ffff ffff ffff ffff outgoing outgoing closing connection outgoing peer reset message error outgoing outgoing closing connection reactor c received reactor performing shutdown process terminating process api internal cli fredrlon ban ztp a c
| 1
|
81,403
| 7,780,505,588
|
IssuesEvent
|
2018-06-05 20:16:22
|
CCSI-Toolset/FOQUS
|
https://api.github.com/repos/CCSI-Toolset/FOQUS
|
opened
|
Test Script Recognize Error Message
|
Testing bug
|
Testing script will hang when an error message appears. If the "OK" button is pushed script proceeds as it normally would. Ideally the appearance of an error message would save the contents of the error message to a log file and exit the testing script.
|
1.0
|
Test Script Recognize Error Message - Testing script will hang when an error message appears. If the "OK" button is pushed script proceeds as it normally would. Ideally the appearance of an error message would save the contents of the error message to a log file and exit the testing script.
|
test
|
test script recognize error message testing script will hang when an error message appears if the ok button is pushed script proceeds as it normally would ideally the appearance of an error message would save the contents of the error message to a log file and exit the testing script
| 1
|
649,262
| 21,261,529,079
|
IssuesEvent
|
2022-04-13 05:10:58
|
lorenarojas1/CDMX012-lab-notes
|
https://api.github.com/repos/lorenarojas1/CDMX012-lab-notes
|
opened
|
Crear vista principal de la app al loguearse.
|
low priority
|
En la vista principal se mostrará un botón cerrar sesión de Firebase y se mostrá mensaje de "Página en construcción"
|
1.0
|
Crear vista principal de la app al loguearse. - En la vista principal se mostrará un botón cerrar sesión de Firebase y se mostrá mensaje de "Página en construcción"
|
non_test
|
crear vista principal de la app al loguearse en la vista principal se mostrará un botón cerrar sesión de firebase y se mostrá mensaje de página en construcción
| 0
|
144,888
| 11,634,535,840
|
IssuesEvent
|
2020-02-28 10:33:54
|
aliasrobotics/RVD
|
https://api.github.com/repos/aliasrobotics/RVD
|
opened
|
(error) Uninitialized variable
|
bug cppcheck static analysis testing triage
|
```yaml
{
"id": 1,
"title": "(error) Uninitialized variable",
"type": "bug",
"description": "[src/ompl/demos/CForestCircleGridBenchmark.cpp:81]: (error) Uninitialized variable: runCount",
"cwe": "None",
"cve": "None",
"keywords": [
"cppcheck",
"static analysis",
"testing",
"triage",
"bug"
],
"system": "src/ompl/demos/CForestCircleGridBenchmark.cpp",
"vendor": null,
"severity": {
"rvss-score": 0,
"rvss-vector": "",
"severity-description": "",
"cvss-score": 0,
"cvss-vector": ""
},
"links": "",
"flaw": {
"phase": "testing",
"specificity": "N/A",
"architectural-location": "N/A",
"application": "N/A",
"subsystem": "N/A",
"package": "N/A",
"languages": "None",
"date-detected": "2020-02-28 (10:33)",
"detected-by": "Alias Robotics",
"detected-by-method": "testing static",
"date-reported": "2020-02-28 (10:33)",
"reported-by": "Alias Robotics",
"reported-by-relationship": "automatic",
"issue": "",
"reproducibility": "always",
"trace": "",
"reproduction": "See artifacts below (if available)",
"reproduction-image": "gitlab.com/aliasrobotics/offensive/alurity/pipelines/active/pipeline_ros2_ros_industrial/-/jobs/453590484/artifacts/download"
},
"exploitation": {
"description": "",
"exploitation-image": "",
"exploitation-vector": ""
},
"mitigation": {
"description": "",
"pull-request": "",
"date-mitigation": ""
}
}
```
|
1.0
|
(error) Uninitialized variable - ```yaml
{
"id": 1,
"title": "(error) Uninitialized variable",
"type": "bug",
"description": "[src/ompl/demos/CForestCircleGridBenchmark.cpp:81]: (error) Uninitialized variable: runCount",
"cwe": "None",
"cve": "None",
"keywords": [
"cppcheck",
"static analysis",
"testing",
"triage",
"bug"
],
"system": "src/ompl/demos/CForestCircleGridBenchmark.cpp",
"vendor": null,
"severity": {
"rvss-score": 0,
"rvss-vector": "",
"severity-description": "",
"cvss-score": 0,
"cvss-vector": ""
},
"links": "",
"flaw": {
"phase": "testing",
"specificity": "N/A",
"architectural-location": "N/A",
"application": "N/A",
"subsystem": "N/A",
"package": "N/A",
"languages": "None",
"date-detected": "2020-02-28 (10:33)",
"detected-by": "Alias Robotics",
"detected-by-method": "testing static",
"date-reported": "2020-02-28 (10:33)",
"reported-by": "Alias Robotics",
"reported-by-relationship": "automatic",
"issue": "",
"reproducibility": "always",
"trace": "",
"reproduction": "See artifacts below (if available)",
"reproduction-image": "gitlab.com/aliasrobotics/offensive/alurity/pipelines/active/pipeline_ros2_ros_industrial/-/jobs/453590484/artifacts/download"
},
"exploitation": {
"description": "",
"exploitation-image": "",
"exploitation-vector": ""
},
"mitigation": {
"description": "",
"pull-request": "",
"date-mitigation": ""
}
}
```
|
test
|
error uninitialized variable yaml id title error uninitialized variable type bug description error uninitialized variable runcount cwe none cve none keywords cppcheck static analysis testing triage bug system src ompl demos cforestcirclegridbenchmark cpp vendor null severity rvss score rvss vector severity description cvss score cvss vector links flaw phase testing specificity n a architectural location n a application n a subsystem n a package n a languages none date detected detected by alias robotics detected by method testing static date reported reported by alias robotics reported by relationship automatic issue reproducibility always trace reproduction see artifacts below if available reproduction image gitlab com aliasrobotics offensive alurity pipelines active pipeline ros industrial jobs artifacts download exploitation description exploitation image exploitation vector mitigation description pull request date mitigation
| 1
|
262,029
| 22,787,004,617
|
IssuesEvent
|
2022-07-09 12:08:24
|
streamnative/pulsar
|
https://api.github.com/repos/streamnative/pulsar
|
opened
|
ISSUE-16496: Flaky-test: NonPersistentTopicE2ETest.testGC
|
component/test flaky-tests
|
Original Issue: apache/pulsar#16496
---
Stack Trace
```
Error: Tests run: 10, Failures: 1, Errors: 0, Skipped: 9, Time elapsed: 65.361 s <<< FAILURE! - in org.apache.pulsar.broker.service.NonPersistentTopicE2ETest
Error: testGC(org.apache.pulsar.broker.service.NonPersistentTopicE2ETest) Time elapsed: 0.403 s <<< FAILURE!
java.lang.AssertionError: expected [false] but found [true]
at org.testng.Assert.fail(Assert.java:99)
at org.testng.Assert.failNotEquals(Assert.java:1037)
at org.testng.Assert.assertFalse(Assert.java:67)
at org.testng.Assert.assertFalse(Assert.java:77)
at org.apache.pulsar.broker.service.NonPersistentTopicE2ETest.testGC(NonPersistentTopicE2ETest.java:202)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:132)
at org.testng.internal.InvokeMethodRunnable.runOne(InvokeMethodRunnable.java:45)
at org.testng.internal.InvokeMethodRunnable.call(InvokeMethodRunnable.java:73)
at org.testng.internal.InvokeMethodRunnable.call(InvokeMethodRunnable.java:11)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:833)</summary>
```
|
2.0
|
ISSUE-16496: Flaky-test: NonPersistentTopicE2ETest.testGC - Original Issue: apache/pulsar#16496
---
Stack Trace
```
Error: Tests run: 10, Failures: 1, Errors: 0, Skipped: 9, Time elapsed: 65.361 s <<< FAILURE! - in org.apache.pulsar.broker.service.NonPersistentTopicE2ETest
Error: testGC(org.apache.pulsar.broker.service.NonPersistentTopicE2ETest) Time elapsed: 0.403 s <<< FAILURE!
java.lang.AssertionError: expected [false] but found [true]
at org.testng.Assert.fail(Assert.java:99)
at org.testng.Assert.failNotEquals(Assert.java:1037)
at org.testng.Assert.assertFalse(Assert.java:67)
at org.testng.Assert.assertFalse(Assert.java:77)
at org.apache.pulsar.broker.service.NonPersistentTopicE2ETest.testGC(NonPersistentTopicE2ETest.java:202)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:132)
at org.testng.internal.InvokeMethodRunnable.runOne(InvokeMethodRunnable.java:45)
at org.testng.internal.InvokeMethodRunnable.call(InvokeMethodRunnable.java:73)
at org.testng.internal.InvokeMethodRunnable.call(InvokeMethodRunnable.java:11)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:833)</summary>
```
|
test
|
issue flaky test testgc original issue apache pulsar stack trace error tests run failures errors skipped time elapsed s failure in org apache pulsar broker service error testgc org apache pulsar broker service time elapsed s failure java lang assertionerror expected but found at org testng assert fail assert java at org testng assert failnotequals assert java at org testng assert assertfalse assert java at org testng assert assertfalse assert java at org apache pulsar broker service testgc java at java base jdk internal reflect nativemethodaccessorimpl native method at java base jdk internal reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at java base jdk internal reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java base java lang reflect method invoke method java at org testng internal methodinvocationhelper invokemethod methodinvocationhelper java at org testng internal invokemethodrunnable runone invokemethodrunnable java at org testng internal invokemethodrunnable call invokemethodrunnable java at org testng internal invokemethodrunnable call invokemethodrunnable java at java base java util concurrent futuretask run futuretask java at java base java util concurrent threadpoolexecutor runworker threadpoolexecutor java at java base java util concurrent threadpoolexecutor worker run threadpoolexecutor java at java base java lang thread run thread java
| 1
|
318,531
| 27,311,084,930
|
IssuesEvent
|
2023-02-24 12:14:52
|
gavv/httpexpect
|
https://api.github.com/repos/gavv/httpexpect
|
closed
|
Refactor some unit tests
|
tests help wanted refactoring good first issue
|
Some of our tests declare multiple variables and then do various checks on each variable, like this:
```go
value1 := NewMatch(reporter, []string{"m"}, nil)
value2 := NewMatch(reporter, []string{}, nil)
value1.IsEmpty()
value1.chain.assertFailed(t)
value1.chain.clearFailed()
value2.IsEmpty()
value2.chain.assertNotFailed(t)
value2.chain.clearFailed()
```
This approach is error-prone: it's easy to make a check on wrong variable and often it can remain unnoticed.
----
This tests need to be refactored in one of the following ways:
1. In simple tests, instead of declaring multiple vars, we can reuse a single one, like this:
```go
var value *Match
value = NewMatch(reporter, []string{"m"}, nil)
value.IsEmpty()
value.chain.assertFailed(t)
value.chain.clearFailed()
value = NewMatch(reporter, []string{}, nil)
value.IsEmpty()
value.chain.assertNotFailed(t)
value.chain.clearFailed()
```
2. In more complicated tests, we can split the test into subtests, and isolate local vars there.
3. We can also convert tests to table-driven style.
----
Feel free to choose one of the approaches for each test based on your own judgement.
Tests to be refactored:
* [x] TestMatch_Empty
* [x] TestMatch_ValuesEmpty
* [x] TestNumber_EqualNaN
* [x] TestArray_IsEqual/types (split into subtests)
* [x] TestString_Empty
* [x] TestString_IsAscii
* [x] TestString_NotAscii
* [x] TestString_AsNumber
* [x] TestString_AsDateTime
* [x] TestValue_GetObject
* [x] TestValue_GetArray
* [x] TestValue_GetNumber
* [x] TestValue_GetBoolean
* [x] TestValue_IsObject
* [x] TestValue_IsArray
* [x] TestValue_IsString
* [x] TestValue_IsNumber
* [x] TestValue_IsBoolean
* [x] TestWebsocketMessage_CodeAndType
* [x] TestWebsocketMessage_NoContent
----
Pull requests that address only part of this issue are welcome too!
Related: https://github.com/gavv/httpexpect/issues/283
|
1.0
|
Refactor some unit tests - Some of our tests declare multiple variables and then do various checks on each variable, like this:
```go
value1 := NewMatch(reporter, []string{"m"}, nil)
value2 := NewMatch(reporter, []string{}, nil)
value1.IsEmpty()
value1.chain.assertFailed(t)
value1.chain.clearFailed()
value2.IsEmpty()
value2.chain.assertNotFailed(t)
value2.chain.clearFailed()
```
This approach is error-prone: it's easy to make a check on wrong variable and often it can remain unnoticed.
----
This tests need to be refactored in one of the following ways:
1. In simple tests, instead of declaring multiple vars, we can reuse a single one, like this:
```go
var value *Match
value = NewMatch(reporter, []string{"m"}, nil)
value.IsEmpty()
value.chain.assertFailed(t)
value.chain.clearFailed()
value = NewMatch(reporter, []string{}, nil)
value.IsEmpty()
value.chain.assertNotFailed(t)
value.chain.clearFailed()
```
2. In more complicated tests, we can split the test into subtests, and isolate local vars there.
3. We can also convert tests to table-driven style.
----
Feel free to choose one of the approaches for each test based on your own judgement.
Tests to be refactored:
* [x] TestMatch_Empty
* [x] TestMatch_ValuesEmpty
* [x] TestNumber_EqualNaN
* [x] TestArray_IsEqual/types (split into subtests)
* [x] TestString_Empty
* [x] TestString_IsAscii
* [x] TestString_NotAscii
* [x] TestString_AsNumber
* [x] TestString_AsDateTime
* [x] TestValue_GetObject
* [x] TestValue_GetArray
* [x] TestValue_GetNumber
* [x] TestValue_GetBoolean
* [x] TestValue_IsObject
* [x] TestValue_IsArray
* [x] TestValue_IsString
* [x] TestValue_IsNumber
* [x] TestValue_IsBoolean
* [x] TestWebsocketMessage_CodeAndType
* [x] TestWebsocketMessage_NoContent
----
Pull requests that address only part of this issue are welcome too!
Related: https://github.com/gavv/httpexpect/issues/283
|
test
|
refactor some unit tests some of our tests declare multiple variables and then do various checks on each variable like this go newmatch reporter string m nil newmatch reporter string nil isempty chain assertfailed t chain clearfailed isempty chain assertnotfailed t chain clearfailed this approach is error prone it s easy to make a check on wrong variable and often it can remain unnoticed this tests need to be refactored in one of the following ways in simple tests instead of declaring multiple vars we can reuse a single one like this go var value match value newmatch reporter string m nil value isempty value chain assertfailed t value chain clearfailed value newmatch reporter string nil value isempty value chain assertnotfailed t value chain clearfailed in more complicated tests we can split the test into subtests and isolate local vars there we can also convert tests to table driven style feel free to choose one of the approaches for each test based on your own judgement tests to be refactored testmatch empty testmatch valuesempty testnumber equalnan testarray isequal types split into subtests teststring empty teststring isascii teststring notascii teststring asnumber teststring asdatetime testvalue getobject testvalue getarray testvalue getnumber testvalue getboolean testvalue isobject testvalue isarray testvalue isstring testvalue isnumber testvalue isboolean testwebsocketmessage codeandtype testwebsocketmessage nocontent pull requests that address only part of this issue are welcome too related
| 1
|
170,012
| 6,423,219,620
|
IssuesEvent
|
2017-08-09 10:25:17
|
jiscdev/data-explorer
|
https://api.github.com/repos/jiscdev/data-explorer
|
opened
|
tables under UDD overview need paginating
|
accepted @ high priority bug
|
USW raised, see https://jisclearninganalytics.freshdesk.com/helpdesk/tickets/326
e.g. site admin, UDD Overview, studentassessmentinstance -- page ends at page ends at 05032318 but there are many more records in the UDD beyond that. Suspect similar for other UDD tables with larger amounts of data.
|
1.0
|
tables under UDD overview need paginating - USW raised, see https://jisclearninganalytics.freshdesk.com/helpdesk/tickets/326
e.g. site admin, UDD Overview, studentassessmentinstance -- page ends at page ends at 05032318 but there are many more records in the UDD beyond that. Suspect similar for other UDD tables with larger amounts of data.
|
non_test
|
tables under udd overview need paginating usw raised see e g site admin udd overview studentassessmentinstance page ends at page ends at but there are many more records in the udd beyond that suspect similar for other udd tables with larger amounts of data
| 0
|
216,517
| 16,768,255,758
|
IssuesEvent
|
2021-06-14 11:46:03
|
mennaelkashef/eShop
|
https://api.github.com/repos/mennaelkashef/eShop
|
opened
|
No description entered by the user.
|
DOES-NOT-CONTAIN-STRING Hello! RULE-GOT-APPLIED Rule-works-on-convert-to-bug instabug test
|
# :clipboard: Bug Details
>No description entered by the user.
key | value
--|--
Reported At | 2021-06-14 11:36:58 UTC
Email | imohamady@instabug.com
Categories | Report a bug, Cat 1, hggjh
Tags | test, Hello!, RULE-GOT-APPLIED, DOES-NOT-CONTAIN-STRING, Rule-works-on-convert-to-bug, instabug
App Version | 1.0-kotlin (1)
Session Duration | 28
Device | Google AOSP on IA Emulator, OS Level 28
Display | 1080x2220 (xhdpi)
Location | Cairo, Egypt (en)
## :point_right: [View Full Bug Report on Instabug](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7940?utm_source=github&utm_medium=integrations) :point_left:
___
# :iphone: View Hierarchy
This bug was reported from **com.example.app.main.MainFragment**
Find its interactive view hierarchy with all its subviews here: :point_right: **[Check View Hierarchy](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7940?show-hierarchy-view=true&utm_source=github&utm_medium=integrations)** :point_left:
___
# :chart_with_downwards_trend: Session Profiler
Here is what the app was doing right before the bug was reported:
Key | Value
--|--
Used Memory | 65.9% - 0.96/1.46 GB
Used Storage | 9.8% - 0.57/5.81 GB
Connectivity | no_connection
Battery | 100% - unplugged
Orientation | portrait
Find all the changes that happened in the parameters mentioned above during the last 60 seconds before the bug was reported here: :point_right: **[View Full Session Profiler](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7940?show-session-profiler=true&utm_source=github&utm_medium=integrations)** :point_left:
___
# :bust_in_silhouette: User Info
### User Attributes
```
key_name -1394358796: key value bla bla bla la
key_name 1733924589: key value bla bla bla la
key_name -848543674: key value bla bla bla la
```
___
# :mag_right: Logs
### User Steps
Here are the last 10 steps done by the user right before the bug was reported:
```
11:36:42 Tap in "androidx.constraintlayout.widget.ConstraintLayout" in "com.example.app.main.MainActivity"
11:36:43 Tap in "androidx.constraintlayout.widget.ConstraintLayout" in "com.example.app.main.MainActivity"
11:36:44 Tap in "androidx.constraintlayout.widget.ConstraintLayout" in "com.example.app.main.MainActivity"
11:36:47 Tap in "include" of type "androidx.appcompat.widget.Toolbar" in "com.example.app.main.MainActivity"
11:36:54 Tap in "Sdk version: 10..." of type "androidx.appcompat.widget.AppCompatTextView" in "com.example.app.main.MainActivity"
11:36:54 com.example.app.main.MainActivity was paused.
11:36:54 In activity com.example.app.main.MainActivity: fragment com.example.app.main.MainFragment was paused.
11:36:55 Tap in "androidx.constraintlayout.widget.ConstraintLayout" in "com.example.app.main.MainActivity"
11:36:56 Tap in "androidx.constraintlayout.widget.ConstraintLayout" in "com.example.app.main.MainActivity"
11:36:57 Tap in "androidx.constraintlayout.widget.ConstraintLayout" in "com.example.app.main.MainActivity"
```
Find all the user steps done by the user throughout the session here: :point_right: **[View All User Steps](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7940?show-logs=user_steps&utm_source=github&utm_medium=integrations)** :point_left:
### Console Log
Here are the last 10 console logs logged right before the bug was reported:
```
11:37:00 D/IB-ActivityViewInspector( 4660): bug ! null,converting>json ended
11:37:00 D/IB-ActivityViewInspector( 4660): bug ! null,set inspection state
11:37:00 D/IB-BaseReportingPresenter( 4660): receive a view hierarchy inspection action, action value: COMPLETED
11:37:00 D/IB-BaseReportingPresenter( 4660): receive a view hierarchy inspection action, action value: COMPLETED
11:37:00 D/EGL_emulation( 4660): eglMakeCurrent: 0xdb0fd4c0: ver 3 0 (tinfo 0xc9327280)
11:37:00 D/IB-BaseReportingPresenter( 4660): checkUserEmailValid :imohamady@instabug.com
11:37:00 V/IB-PoolProvider( 4660): postTask
11:37:00 D/IB-ActionsOrchestrator( 4660): runAction
11:37:00 D/IB-AttachmentsUtility( 4660): encryptAttachments
11:37:01 D/EGL_emulation( 4660): eglMakeCurrent: 0xdb0fd4c0: ver 3 0 (tinfo 0xc9327280)
```
Find all the logged console logs throughout the session here: :point_right: **[View All Console Log](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7940?show-logs=console_log&utm_source=github&utm_medium=integrations)** :point_left:
___
# :camera: Images
[](https://d38gnqwzxziyyy.cloudfront.net/attachments/bugs/15934772/393a96c3c68b56057deb1135bf619a3d_original/21330624/bug_1623670614181_.jpg?Expires=4779344762&Signature=IYQLkM~dUxqaf3T~48RGb0RF7CblgbB0nyi7ZHeIAFm6W585qbiJrsSpudsoQKm53izOpLgjaBAKpQeNKgizjFPzjw5pMDW4Y6gePINCRCmYser-DR1rZyisMCKIno2uJP9POTdtZy-n1p8u0SrKOBpbf35fo8QANfuZAujaK76tHVzalJJUVEefxnSrKkFEVpLQXlRDqhV0K0jUbYymoMYMpldYSpj2OU41orspVJmMGzSJzSOSXuoWMriJ4iz~R930oYolw3PC63yt5jRpYAF041OoxlnQv-60XuqPe5seC~AX-bxiiaia7X9HUu1jonygq-avBAff75Woc2ET3w__&Key-Pair-Id=APKAIXAG65U6UUX7JAQQ)
[](https://d38gnqwzxziyyy.cloudfront.net/attachments/bugs/15934772/b427b83c1bbf0764e5cd9db7cef6433f_original/21330625/bug_1623670614181_.jpg?Expires=4779344762&Signature=NbsdOROVcPZrD~u2W2aqgygTUHv6HAJT4k4CVNpSl-ht3NxUFTbnD-5i-O1o~3dX2gWmAtSrfZvl9oIUIu-mepSuUyd-MhQcWUVT4jp~gay-qxs4WJDfyG4D~zmSN5525oWIODev8J37kTjTyfkW-eYMEwnVSJrRRxbRzl9wB0uQbF-4x4nzXQDa8ZWua64x8tNbEyZ0JfGL2n197-MyAujYiRBOnbf13VVIyEfd3jjA2w8JAcOOhpFQGc2FB8ucAJpdIZTD9-idmvIQ7m~safOVzFDtjDvUru4-BmFmuTduRZi9zxqW9N30XU0TdRJZt8TblQIz7LE~S1hI8pu9Uw__&Key-Pair-Id=APKAIXAG65U6UUX7JAQQ)
___
# :warning: Looking for More Details?
1. **Network Log**: we are unable to capture your network requests automatically. If you are using HttpUrlConnection or Okhttp requests, [**check the details mentioned here**](https://docs.instabug.com/docs/android-logging?utm_source=github&utm_medium=integrations#section-network-logs).
2. **User Events**: start capturing custom User Events to send them along with each report. [**Find all the details in the docs**](https://docs.instabug.com/docs/android-logging?utm_source=github&utm_medium=integrations).
3. **Instabug Log**: start adding Instabug logs to see them right inside each report you receive. [**Find all the details in the docs**](https://docs.instabug.com/docs/android-logging?utm_source=github&utm_medium=integrations).
|
1.0
|
No description entered by the user. - # :clipboard: Bug Details
>No description entered by the user.
key | value
--|--
Reported At | 2021-06-14 11:36:58 UTC
Email | imohamady@instabug.com
Categories | Report a bug, Cat 1, hggjh
Tags | test, Hello!, RULE-GOT-APPLIED, DOES-NOT-CONTAIN-STRING, Rule-works-on-convert-to-bug, instabug
App Version | 1.0-kotlin (1)
Session Duration | 28
Device | Google AOSP on IA Emulator, OS Level 28
Display | 1080x2220 (xhdpi)
Location | Cairo, Egypt (en)
## :point_right: [View Full Bug Report on Instabug](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7940?utm_source=github&utm_medium=integrations) :point_left:
___
# :iphone: View Hierarchy
This bug was reported from **com.example.app.main.MainFragment**
Find its interactive view hierarchy with all its subviews here: :point_right: **[Check View Hierarchy](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7940?show-hierarchy-view=true&utm_source=github&utm_medium=integrations)** :point_left:
___
# :chart_with_downwards_trend: Session Profiler
Here is what the app was doing right before the bug was reported:
Key | Value
--|--
Used Memory | 65.9% - 0.96/1.46 GB
Used Storage | 9.8% - 0.57/5.81 GB
Connectivity | no_connection
Battery | 100% - unplugged
Orientation | portrait
Find all the changes that happened in the parameters mentioned above during the last 60 seconds before the bug was reported here: :point_right: **[View Full Session Profiler](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7940?show-session-profiler=true&utm_source=github&utm_medium=integrations)** :point_left:
___
# :bust_in_silhouette: User Info
### User Attributes
```
key_name -1394358796: key value bla bla bla la
key_name 1733924589: key value bla bla bla la
key_name -848543674: key value bla bla bla la
```
___
# :mag_right: Logs
### User Steps
Here are the last 10 steps done by the user right before the bug was reported:
```
11:36:42 Tap in "androidx.constraintlayout.widget.ConstraintLayout" in "com.example.app.main.MainActivity"
11:36:43 Tap in "androidx.constraintlayout.widget.ConstraintLayout" in "com.example.app.main.MainActivity"
11:36:44 Tap in "androidx.constraintlayout.widget.ConstraintLayout" in "com.example.app.main.MainActivity"
11:36:47 Tap in "include" of type "androidx.appcompat.widget.Toolbar" in "com.example.app.main.MainActivity"
11:36:54 Tap in "Sdk version: 10..." of type "androidx.appcompat.widget.AppCompatTextView" in "com.example.app.main.MainActivity"
11:36:54 com.example.app.main.MainActivity was paused.
11:36:54 In activity com.example.app.main.MainActivity: fragment com.example.app.main.MainFragment was paused.
11:36:55 Tap in "androidx.constraintlayout.widget.ConstraintLayout" in "com.example.app.main.MainActivity"
11:36:56 Tap in "androidx.constraintlayout.widget.ConstraintLayout" in "com.example.app.main.MainActivity"
11:36:57 Tap in "androidx.constraintlayout.widget.ConstraintLayout" in "com.example.app.main.MainActivity"
```
Find all the user steps done by the user throughout the session here: :point_right: **[View All User Steps](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7940?show-logs=user_steps&utm_source=github&utm_medium=integrations)** :point_left:
### Console Log
Here are the last 10 console logs logged right before the bug was reported:
```
11:37:00 D/IB-ActivityViewInspector( 4660): bug ! null,converting>json ended
11:37:00 D/IB-ActivityViewInspector( 4660): bug ! null,set inspection state
11:37:00 D/IB-BaseReportingPresenter( 4660): receive a view hierarchy inspection action, action value: COMPLETED
11:37:00 D/IB-BaseReportingPresenter( 4660): receive a view hierarchy inspection action, action value: COMPLETED
11:37:00 D/EGL_emulation( 4660): eglMakeCurrent: 0xdb0fd4c0: ver 3 0 (tinfo 0xc9327280)
11:37:00 D/IB-BaseReportingPresenter( 4660): checkUserEmailValid :imohamady@instabug.com
11:37:00 V/IB-PoolProvider( 4660): postTask
11:37:00 D/IB-ActionsOrchestrator( 4660): runAction
11:37:00 D/IB-AttachmentsUtility( 4660): encryptAttachments
11:37:01 D/EGL_emulation( 4660): eglMakeCurrent: 0xdb0fd4c0: ver 3 0 (tinfo 0xc9327280)
```
Find all the logged console logs throughout the session here: :point_right: **[View All Console Log](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7940?show-logs=console_log&utm_source=github&utm_medium=integrations)** :point_left:
___
# :camera: Images
[](https://d38gnqwzxziyyy.cloudfront.net/attachments/bugs/15934772/393a96c3c68b56057deb1135bf619a3d_original/21330624/bug_1623670614181_.jpg?Expires=4779344762&Signature=IYQLkM~dUxqaf3T~48RGb0RF7CblgbB0nyi7ZHeIAFm6W585qbiJrsSpudsoQKm53izOpLgjaBAKpQeNKgizjFPzjw5pMDW4Y6gePINCRCmYser-DR1rZyisMCKIno2uJP9POTdtZy-n1p8u0SrKOBpbf35fo8QANfuZAujaK76tHVzalJJUVEefxnSrKkFEVpLQXlRDqhV0K0jUbYymoMYMpldYSpj2OU41orspVJmMGzSJzSOSXuoWMriJ4iz~R930oYolw3PC63yt5jRpYAF041OoxlnQv-60XuqPe5seC~AX-bxiiaia7X9HUu1jonygq-avBAff75Woc2ET3w__&Key-Pair-Id=APKAIXAG65U6UUX7JAQQ)
[](https://d38gnqwzxziyyy.cloudfront.net/attachments/bugs/15934772/b427b83c1bbf0764e5cd9db7cef6433f_original/21330625/bug_1623670614181_.jpg?Expires=4779344762&Signature=NbsdOROVcPZrD~u2W2aqgygTUHv6HAJT4k4CVNpSl-ht3NxUFTbnD-5i-O1o~3dX2gWmAtSrfZvl9oIUIu-mepSuUyd-MhQcWUVT4jp~gay-qxs4WJDfyG4D~zmSN5525oWIODev8J37kTjTyfkW-eYMEwnVSJrRRxbRzl9wB0uQbF-4x4nzXQDa8ZWua64x8tNbEyZ0JfGL2n197-MyAujYiRBOnbf13VVIyEfd3jjA2w8JAcOOhpFQGc2FB8ucAJpdIZTD9-idmvIQ7m~safOVzFDtjDvUru4-BmFmuTduRZi9zxqW9N30XU0TdRJZt8TblQIz7LE~S1hI8pu9Uw__&Key-Pair-Id=APKAIXAG65U6UUX7JAQQ)
___
# :warning: Looking for More Details?
1. **Network Log**: we are unable to capture your network requests automatically. If you are using HttpUrlConnection or Okhttp requests, [**check the details mentioned here**](https://docs.instabug.com/docs/android-logging?utm_source=github&utm_medium=integrations#section-network-logs).
2. **User Events**: start capturing custom User Events to send them along with each report. [**Find all the details in the docs**](https://docs.instabug.com/docs/android-logging?utm_source=github&utm_medium=integrations).
3. **Instabug Log**: start adding Instabug logs to see them right inside each report you receive. [**Find all the details in the docs**](https://docs.instabug.com/docs/android-logging?utm_source=github&utm_medium=integrations).
|
test
|
no description entered by the user clipboard bug details no description entered by the user key value reported at utc email imohamady instabug com categories report a bug cat hggjh tags test hello rule got applied does not contain string rule works on convert to bug instabug app version kotlin session duration device google aosp on ia emulator os level display xhdpi location cairo egypt en point right point left iphone view hierarchy this bug was reported from com example app main mainfragment find its interactive view hierarchy with all its subviews here point right point left chart with downwards trend session profiler here is what the app was doing right before the bug was reported key value used memory gb used storage gb connectivity no connection battery unplugged orientation portrait find all the changes that happened in the parameters mentioned above during the last seconds before the bug was reported here point right point left bust in silhouette user info user attributes key name key value bla bla bla la key name key value bla bla bla la key name key value bla bla bla la mag right logs user steps here are the last steps done by the user right before the bug was reported tap in androidx constraintlayout widget constraintlayout in com example app main mainactivity tap in androidx constraintlayout widget constraintlayout in com example app main mainactivity tap in androidx constraintlayout widget constraintlayout in com example app main mainactivity tap in include of type androidx appcompat widget toolbar in com example app main mainactivity tap in sdk version of type androidx appcompat widget appcompattextview in com example app main mainactivity com example app main mainactivity was paused in activity com example app main mainactivity fragment com example app main mainfragment was paused tap in androidx constraintlayout widget constraintlayout in com example app main mainactivity tap in androidx constraintlayout widget constraintlayout in com example app main mainactivity tap in androidx constraintlayout widget constraintlayout in com example app main mainactivity find all the user steps done by the user throughout the session here point right point left console log here are the last console logs logged right before the bug was reported d ib activityviewinspector bug null converting json ended d ib activityviewinspector bug null set inspection state d ib basereportingpresenter receive a view hierarchy inspection action action value completed d ib basereportingpresenter receive a view hierarchy inspection action action value completed d egl emulation eglmakecurrent ver tinfo d ib basereportingpresenter checkuseremailvalid imohamady instabug com v ib poolprovider posttask d ib actionsorchestrator runaction d ib attachmentsutility encryptattachments d egl emulation eglmakecurrent ver tinfo find all the logged console logs throughout the session here point right point left camera images warning looking for more details network log we are unable to capture your network requests automatically if you are using httpurlconnection or okhttp requests user events start capturing custom user events to send them along with each report instabug log start adding instabug logs to see them right inside each report you receive
| 1
|
255,122
| 21,901,068,666
|
IssuesEvent
|
2022-05-20 13:28:21
|
status-im/status-desktop
|
https://api.github.com/repos/status-im/status-desktop
|
closed
|
[very hard to replicate] 1 to 1 chat window contains messages from other contacts
|
bug Chat testing priority 0: blocker hard-to-replicate
|
# Bug Report
## Description
1 to 1 chats seem to contain messages from other contacts.
Also, @PascalPrecht noticed this discrepancy where a public chat msg was seen on a 1 to 1 chat -> [here](https://discord.com/channels/624205794384281629/697843216048717905/971327104698449960)
## Steps to reproduce
1. Launch app, sign in (Usr-1) and send a contact request to a user (Usr-2)
2. Sign out and sign in as Usr-2 and accept the contact request from Usr-1
3. Send a msg to Usr-1 and then sign out
4. Sign in as another user (Usr-3) and send a contact request and then a msg to Usr-1
5. Sign out and sign back in as Usr-1
6. Accept the contact request from Usr-3
7. Check the 1 to 1 chat from Usr-2
#### Expected behavior
The user must only see the msg from the selected user
#### Actual behavior
The chat window also shows msg from another 1 to 1 chat
### Additional Information
- Status desktop version: Master : d4ef0ff5e864d342857b51f58cea67c5db5004c2
|
1.0
|
[very hard to replicate] 1 to 1 chat window contains messages from other contacts - # Bug Report
## Description
1 to 1 chats seem to contain messages from other contacts.
Also, @PascalPrecht noticed this discrepancy where a public chat msg was seen on a 1 to 1 chat -> [here](https://discord.com/channels/624205794384281629/697843216048717905/971327104698449960)
## Steps to reproduce
1. Launch app, sign in (Usr-1) and send a contact request to a user (Usr-2)
2. Sign out and sign in as Usr-2 and accept the contact request from Usr-1
3. Send a msg to Usr-1 and then sign out
4. Sign in as another user (Usr-3) and send a contact request and then a msg to Usr-1
5. Sign out and sign back in as Usr-1
6. Accept the contact request from Usr-3
7. Check the 1 to 1 chat from Usr-2
#### Expected behavior
The user must only see the msg from the selected user
#### Actual behavior
The chat window also shows msg from another 1 to 1 chat
### Additional Information
- Status desktop version: Master : d4ef0ff5e864d342857b51f58cea67c5db5004c2
|
test
|
to chat window contains messages from other contacts bug report description to chats seem to contain messages from other contacts also pascalprecht noticed this discrepancy where a public chat msg was seen on a to chat steps to reproduce launch app sign in usr and send a contact request to a user usr sign out and sign in as usr and accept the contact request from usr send a msg to usr and then sign out sign in as another user usr and send a contact request and then a msg to usr sign out and sign back in as usr accept the contact request from usr check the to chat from usr expected behavior the user must only see the msg from the selected user actual behavior the chat window also shows msg from another to chat additional information status desktop version master
| 1
|
15,234
| 19,342,258,846
|
IssuesEvent
|
2021-12-15 06:45:03
|
evhub/coconut
|
https://api.github.com/repos/evhub/coconut
|
closed
|
Write xontrib to allow Coconut in xonsh
|
compatibility resolved tooling
|
See: https://xon.sh/
Should be pretty easy, all we have to do is run Coconut over the original command string before xonsh gets it and pass any lines that Coconut doesn't know how to handle directly through to xonsh.
|
True
|
Write xontrib to allow Coconut in xonsh - See: https://xon.sh/
Should be pretty easy, all we have to do is run Coconut over the original command string before xonsh gets it and pass any lines that Coconut doesn't know how to handle directly through to xonsh.
|
non_test
|
write xontrib to allow coconut in xonsh see should be pretty easy all we have to do is run coconut over the original command string before xonsh gets it and pass any lines that coconut doesn t know how to handle directly through to xonsh
| 0
|
208,635
| 16,132,730,005
|
IssuesEvent
|
2021-04-29 07:52:37
|
Sqrdelta/Programming_Languages
|
https://api.github.com/repos/Sqrdelta/Programming_Languages
|
closed
|
Add basic examples in C++
|
C++ Good For Beginners documentation wip
|
See the C folder, the samples can be the same in there, divided in chapters starting from 1 - (name of folder).
|
1.0
|
Add basic examples in C++ - See the C folder, the samples can be the same in there, divided in chapters starting from 1 - (name of folder).
|
non_test
|
add basic examples in c see the c folder the samples can be the same in there divided in chapters starting from name of folder
| 0
|
192,135
| 14,600,173,702
|
IssuesEvent
|
2020-12-21 06:14:45
|
dromara/soul
|
https://api.github.com/repos/dromara/soul
|
closed
|
Improve code coverage in soul-plugin-waf
|
in: test
|
- [ ] WafPluginDataHandler @HoldDie
- [ ] WafPlugin @HoldDie
Please read the Contribution Guideline before submitting the PR
|
1.0
|
Improve code coverage in soul-plugin-waf - - [ ] WafPluginDataHandler @HoldDie
- [ ] WafPlugin @HoldDie
Please read the Contribution Guideline before submitting the PR
|
test
|
improve code coverage in soul plugin waf wafplugindatahandler holddie wafplugin holddie please read the contribution guideline before submitting the pr
| 1
|
106,350
| 9,126,504,215
|
IssuesEvent
|
2019-02-24 22:02:48
|
Raptoer/F3
|
https://api.github.com/repos/Raptoer/F3
|
closed
|
JIP issues
|
S5:Tested; Awaiting Release T:Bug T:Bug (BI's fault)
|
Currently not all components are JIP-safe, this should be changed. Because reconnects do happen and it would be nice if this wouldn't break anything.
List of components with known JIP issues:
#### Zeus
- blank black screen is shown (BI Bug?)
issue: the curator is no longer linked with the player when JIP.
https://feedback.bistudio.com/T119801
https://feedback.bistudio.com/T123886
un-assigning and re-assigning the curator does work, but fnc_zeusInit only gets called by the curator (module) and we don't know which player was assigned to which curator object. Additionally we would need to make sure the event handlers don't break.
#### ~~Fireteam Member Markers~~
- ~~No colors. Fixed in #156. Merged~~
#### ~~setTeamColours~~
- ~~since Arma 3 1.62 `assignTeam` has global effect, which leads to the "problem" that teamcolors are reset when someone reconnects. Fixed in #163. Merged~~
#### ~~groupMakers~~
- ~~Groups that didn't exist when the mission started (no ai in slot) don't have a group marker. But they probably should have markers to handle reinforcements on the fly. Fixed in #182.~~
Ideally we should check all components for any JIP-related issues and document them here.
|
1.0
|
JIP issues - Currently not all components are JIP-safe, this should be changed. Because reconnects do happen and it would be nice if this wouldn't break anything.
List of components with known JIP issues:
#### Zeus
- blank black screen is shown (BI Bug?)
issue: the curator is no longer linked with the player when JIP.
https://feedback.bistudio.com/T119801
https://feedback.bistudio.com/T123886
un-assigning and re-assigning the curator does work, but fnc_zeusInit only gets called by the curator (module) and we don't know which player was assigned to which curator object. Additionally we would need to make sure the event handlers don't break.
#### ~~Fireteam Member Markers~~
- ~~No colors. Fixed in #156. Merged~~
#### ~~setTeamColours~~
- ~~since Arma 3 1.62 `assignTeam` has global effect, which leads to the "problem" that teamcolors are reset when someone reconnects. Fixed in #163. Merged~~
#### ~~groupMakers~~
- ~~Groups that didn't exist when the mission started (no ai in slot) don't have a group marker. But they probably should have markers to handle reinforcements on the fly. Fixed in #182.~~
Ideally we should check all components for any JIP-related issues and document them here.
|
test
|
jip issues currently not all components are jip safe this should be changed because reconnects do happen and it would be nice if this wouldn t break anything list of components with known jip issues zeus blank black screen is shown bi bug issue the curator is no longer linked with the player when jip un assigning and re assigning the curator does work but fnc zeusinit only gets called by the curator module and we don t know which player was assigned to which curator object additionally we would need to make sure the event handlers don t break fireteam member markers no colors fixed in merged setteamcolours since arma assignteam has global effect which leads to the problem that teamcolors are reset when someone reconnects fixed in merged groupmakers groups that didn t exist when the mission started no ai in slot don t have a group marker but they probably should have markers to handle reinforcements on the fly fixed in ideally we should check all components for any jip related issues and document them here
| 1
|
74,903
| 20,405,673,666
|
IssuesEvent
|
2022-02-23 04:55:17
|
CodeChain-io/codechain
|
https://api.github.com/repos/CodeChain-io/codechain
|
closed
|
Use repoducible build for release binary
|
build
|
If the binary is built from the environment having a higher glibc version than the target machine, it returns an error similar to the following:
```
./codechain: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by ./codechain)
```
It's acceptible in the dev environment, but it should be avoided for the release builds.
We need to ensure that the release builds always have the same dependency.
|
1.0
|
Use repoducible build for release binary - If the binary is built from the environment having a higher glibc version than the target machine, it returns an error similar to the following:
```
./codechain: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by ./codechain)
```
It's acceptible in the dev environment, but it should be avoided for the release builds.
We need to ensure that the release builds always have the same dependency.
|
non_test
|
use repoducible build for release binary if the binary is built from the environment having a higher glibc version than the target machine it returns an error similar to the following codechain lib linux gnu libm so version glibc not found required by codechain it s acceptible in the dev environment but it should be avoided for the release builds we need to ensure that the release builds always have the same dependency
| 0
|
216,644
| 24,285,624,886
|
IssuesEvent
|
2022-09-28 21:48:01
|
project-chip/connectedhomeip
|
https://api.github.com/repos/project-chip/connectedhomeip
|
closed
|
TestCaseSession.cpp fails with is_asan=true
|
security V1.X
|
```
READ of size 20 at 0x616000000af2 thread T0
#0 0x102d695b5 in MemcmpInterceptorCommon(void*, int (*)(void const*, void const*, unsigned long), void const*, void const*, unsigned long)+0x155 (libclang_rt.asan_osx_dynamic.dylib:x86_64h+0x195b5)
#1 0x102d69ab9 in wrap_memcmp+0x69 (libclang_rt.asan_osx_dynamic.dylib:x86_64h+0x19ab9)
#2 0x10294985d in chip::Credentials::CertificateKeyId::IsEqual(chip::Credentials::CertificateKeyId const&) const CHIPCert.cpp:787
#3 0x10294ae7f in chip::Credentials::ChipCertificateSet::FindValidCert(chip::Credentials::ChipDN const&, chip::Credentials::CertificateKeyId const&, chip::Credentials::ValidationContext&, chip::BitFlags<chip::Credentials::CertValidateFlags, unsigned char>, unsigned char, chip::Credentials::ChipCertificateData*&) CHIPCert.cpp:570
#4 0x10294aa6f in chip::Credentials::ChipCertificateSet::FindValidCert(chip::Credentials::ChipDN const&, chip::Credentials::CertificateKeyId const&, chip::Credentials::ValidationContext&, chip::Credentials::ChipCertificateData*&) CHIPCert.cpp:372
#5 0x102956561 in chip::Credentials::OperationalCredentialSet::FindValidCert(chip::Credentials::CertificateKeyId const&, chip::Credentials::ChipDN const&, chip::Credentials::CertificateKeyId const&, chip::Credentials::ValidationContext&, chip::Credentials::ChipCertificateData*&) CHIPOperationalCredentials.cpp:206
#6 0x1029ae409 in chip::CASESession::Validate_and_RetrieveResponderID(unsigned char const**, chip::Crypto::P256PublicKey&, unsigned char const**, unsigned short&) CASESession.cpp:1015
#7 0x1029ac053 in chip::CASESession::HandleSigmaR2(chip::System::PacketBufferHandle const&) CASESession.cpp:653
#8 0x1029ab524 in chip::CASESession::HandleSigmaR2_and_SendSigmaR3(chip::System::PacketBufferHandle const&) CASESession.cpp:557
#9 0x1029b0895 in chip::CASESession::OnMessageReceived(chip::Messaging::ExchangeContext*, chip::PacketHeader const&, chip::PayloadHeader const&, chip::System::PacketBufferHandle) CASESession.cpp:1152
#10 0x10297cbd4 in chip::Messaging::ExchangeContext::HandleMessage(chip::PacketHeader const&, chip::PayloadHeader const&, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) ExchangeContext.cpp:419
#11 0x102981c60 in chip::Messaging::ExchangeManager::OnMessageReceived(chip::PacketHeader const&, chip::PayloadHeader const&, chip::SecureSessionHandle, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle, chip::SecureSessionMgr*) ExchangeMgr.cpp:243
#12 0x10299da21 in chip::SecureSessionMgr::MessageDispatch(chip::PacketHeader const&, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) SecureSessionMgr.cpp:317
#13 0x10299c4ec in chip::SecureSessionMgr::OnMessageReceived(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) SecureSessionMgr.cpp:306
#14 0x1029a047a in chip::TransportMgrBase::HandleMessageReceived(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) TransportMgrBase.cpp:57
#15 0x1029447ed in chip::Transport::Base::HandleMessageReceived(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle&&) Base.h:92
#16 0x1029445bd in LoopbackTransport::SendMessage(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) TestCASESession.cpp:59
#17 0x10299ff9d in chip::TransportMgrBase::SendMessage(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle&&) TransportMgrBase.cpp:27
#18 0x1029b23db in chip::SessionEstablishmentExchangeDispatch::SendMessageImpl(chip::SecureSessionHandle, chip::PayloadHeader&, chip::System::PacketBufferHandle&&, chip::EncryptedPacketBufferHandle*) SessionEstablishmentExchangeDispatch.cpp:42
#19 0x10297df04 in chip::Messaging::ExchangeMessageDispatch::SendMessage(chip::SecureSessionHandle, unsigned short, bool, chip::Messaging::ReliableMessageContext*, bool, chip::Protocols::Id, unsigned char, chip::System::PacketBufferHandle) ExchangeMessageDispatch.cpp:95
#20 0x10297b063 in chip::Messaging::ExchangeContext::SendMessageImpl(chip::Protocols::Id, unsigned char, chip::System::PacketBufferHandle, chip::BitFlags<chip::Messaging::SendMessageFlags, unsigned short> const&, chip::Transport::PeerConnectionState*) ExchangeContext.cpp:163
#21 0x10297a75f in chip::Messaging::ExchangeContext::SendMessage(chip::Protocols::Id, unsigned char, chip::System::PacketBufferHandle, chip::BitFlags<chip::Messaging::SendMessageFlags, unsigned short> const&) ExchangeContext.cpp:107
#22 0x1029a83e8 in int chip::Messaging::ExchangeContext::SendMessage<chip::Protocols::SecureChannel::MsgType, void>(chip::Protocols::SecureChannel::MsgType, chip::System::PacketBufferHandle&&, chip::BitFlags<chip::Messaging::SendMessageFlags, unsigned short> const&) ExchangeContext.h:105
#23 0x1029aa264 in chip::CASESession::SendSigmaR2() CASESession.cpp:540
#24 0x1029a8522 in chip::CASESession::HandleSigmaR1_and_SendSigmaR2(chip::System::PacketBufferHandle const&) CASESession.cpp:348
#25 0x1029b0880 in chip::CASESession::OnMessageReceived(chip::Messaging::ExchangeContext*, chip::PacketHeader const&, chip::PayloadHeader const&, chip::System::PacketBufferHandle) CASESession.cpp:1148
#26 0x10297cbd4 in chip::Messaging::ExchangeContext::HandleMessage(chip::PacketHeader const&, chip::PayloadHeader const&, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) ExchangeContext.cpp:419
#27 0x10298237f in chip::Messaging::ExchangeManager::OnMessageReceived(chip::PacketHeader const&, chip::PayloadHeader const&, chip::SecureSessionHandle, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle, chip::SecureSessionMgr*) ExchangeMgr.cpp:308
#28 0x10299da21 in chip::SecureSessionMgr::MessageDispatch(chip::PacketHeader const&, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) SecureSessionMgr.cpp:317
#29 0x10299c4ec in chip::SecureSessionMgr::OnMessageReceived(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) SecureSessionMgr.cpp:306
#30 0x1029a047a in chip::TransportMgrBase::HandleMessageReceived(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) TransportMgrBase.cpp:57
#31 0x1029447ed in chip::Transport::Base::HandleMessageReceived(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle&&) Base.h:92
#32 0x1029445bd in LoopbackTransport::SendMessage(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) TestCASESession.cpp:59
#33 0x10299ff9d in chip::TransportMgrBase::SendMessage(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle&&) TransportMgrBase.cpp:27
#34 0x1029b23db in chip::SessionEstablishmentExchangeDispatch::SendMessageImpl(chip::SecureSessionHandle, chip::PayloadHeader&, chip::System::PacketBufferHandle&&, chip::EncryptedPacketBufferHandle*) SessionEstablishmentExchangeDispatch.cpp:42
#35 0x10297df04 in chip::Messaging::ExchangeMessageDispatch::SendMessage(chip::SecureSessionHandle, unsigned short, bool, chip::Messaging::ReliableMessageContext*, bool, chip::Protocols::Id, unsigned char, chip::System::PacketBufferHandle) ExchangeMessageDispatch.cpp:95
#36 0x10297b063 in chip::Messaging::ExchangeContext::SendMessageImpl(chip::Protocols::Id, unsigned char, chip::System::PacketBufferHandle, chip::BitFlags<chip::Messaging::SendMessageFlags, unsigned short> const&, chip::Transport::PeerConnectionState*) ExchangeContext.cpp:163
#37 0x10297a75f in chip::Messaging::ExchangeContext::SendMessage(chip::Protocols::Id, unsigned char, chip::System::PacketBufferHandle, chip::BitFlags<chip::Messaging::SendMessageFlags, unsigned short> const&) ExchangeContext.cpp:107
#38 0x1029a83e8 in int chip::Messaging::ExchangeContext::SendMessage<chip::Protocols::SecureChannel::MsgType, void>(chip::Protocols::SecureChannel::MsgType, chip::System::PacketBufferHandle&&, chip::BitFlags<chip::Messaging::SendMessageFlags, unsigned short> const&) ExchangeContext.h:105
#39 0x1029a7255 in chip::CASESession::SendSigmaR1() CASESession.cpp:337
#40 0x1029a686a in chip::CASESession::EstablishSession(chip::Transport::PeerAddress, chip::Credentials::OperationalCredentialSet*, unsigned long long, unsigned short, chip::Messaging::ExchangeContext*, chip::SessionEstablishmentDelegate*) CASESession.cpp:240
#41 0x10294070a in CASE_SecurePairingHandshakeTestCommon(_nlTestSuite*, void*, chip::CASESession&, TestCASESecurePairingDelegate&) TestCASESession.cpp:173
#42 0x1029421a2 in CASE_SecurePairingSerializeTest(_nlTestSuite*, void*) TestCASESession.cpp:218
#43 0x1029b30c0 in nlTestRunner nlunit-test.c:213
#44 0x102944256 in TestCASESession() TestCASESession.cpp:395
#45 0x10293deca in main TestCASESession.driver.cpp:32
#46 0x7fff6c7eecc8 in start+0x0 (libdyld.dylib:x86_64+0x1acc8)
0x616000000af2 is located 370 bytes inside of 575-byte region [0x616000000980,0x616000000bbf)
freed by thread T0 here:
#0 0x102d94689 in wrap_free+0xa9 (libclang_rt.asan_osx_dynamic.dylib:x86_64h+0x44689)
#1 0x10296d327 in chip::Platform::MemoryFree(void*) CHIPMem-Malloc.cpp:126
#2 0x102970795 in chip::System::PacketBuffer::Free(chip::System::PacketBuffer*) SystemPacketBuffer.cpp:575
#3 0x102944a3f in chip::System::PacketBufferHandle::operator=(std::nullptr_t) SystemPacketBuffer.h:466
#4 0x1029449b8 in chip::System::PacketBufferHandle::~PacketBufferHandle() SystemPacketBuffer.h:443
#5 0x1029448c4 in chip::System::PacketBufferHandle::~PacketBufferHandle() SystemPacketBuffer.h:443
#6 0x10297cbe0 in chip::Messaging::ExchangeContext::HandleMessage(chip::PacketHeader const&, chip::PayloadHeader const&, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) ExchangeContext.cpp:419
#7 0x102981c60 in chip::Messaging::ExchangeManager::OnMessageReceived(chip::PacketHeader const&, chip::PayloadHeader const&, chip::SecureSessionHandle, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle, chip::SecureSessionMgr*) ExchangeMgr.cpp:243
#8 0x10299da21 in chip::SecureSessionMgr::MessageDispatch(chip::PacketHeader const&, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) SecureSessionMgr.cpp:317
#9 0x10299c4ec in chip::SecureSessionMgr::OnMessageReceived(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) SecureSessionMgr.cpp:306
#10 0x1029a047a in chip::TransportMgrBase::HandleMessageReceived(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) TransportMgrBase.cpp:57
#11 0x1029447ed in chip::Transport::Base::HandleMessageReceived(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle&&) Base.h:92
#12 0x1029445bd in LoopbackTransport::SendMessage(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) TestCASESession.cpp:59
#13 0x10299ff9d in chip::TransportMgrBase::SendMessage(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle&&) TransportMgrBase.cpp:27
#14 0x1029b23db in chip::SessionEstablishmentExchangeDispatch::SendMessageImpl(chip::SecureSessionHandle, chip::PayloadHeader&, chip::System::PacketBufferHandle&&, chip::EncryptedPacketBufferHandle*) SessionEstablishmentExchangeDispatch.cpp:42
#15 0x10297df04 in chip::Messaging::ExchangeMessageDispatch::SendMessage(chip::SecureSessionHandle, unsigned short, bool, chip::Messaging::ReliableMessageContext*, bool, chip::Protocols::Id, unsigned char, chip::System::PacketBufferHandle) ExchangeMessageDispatch.cpp:95
#16 0x10297b063 in chip::Messaging::ExchangeContext::SendMessageImpl(chip::Protocols::Id, unsigned char, chip::System::PacketBufferHandle, chip::BitFlags<chip::Messaging::SendMessageFlags, unsigned short> const&, chip::Transport::PeerConnectionState*) ExchangeContext.cpp:163
#17 0x10297a75f in chip::Messaging::ExchangeContext::SendMessage(chip::Protocols::Id, unsigned char, chip::System::PacketBufferHandle, chip::BitFlags<chip::Messaging::SendMessageFlags, unsigned short> const&) ExchangeContext.cpp:107
#18 0x1029a83e8 in int chip::Messaging::ExchangeContext::SendMessage<chip::Protocols::SecureChannel::MsgType, void>(chip::Protocols::SecureChannel::MsgType, chip::System::PacketBufferHandle&&, chip::BitFlags<chip::Messaging::SendMessageFlags, unsigned short> const&) ExchangeContext.h:105
#19 0x1029aa264 in chip::CASESession::SendSigmaR2() CASESession.cpp:540
#20 0x1029a8522 in chip::CASESession::HandleSigmaR1_and_SendSigmaR2(chip::System::PacketBufferHandle const&) CASESession.cpp:348
#21 0x1029b0880 in chip::CASESession::OnMessageReceived(chip::Messaging::ExchangeContext*, chip::PacketHeader const&, chip::PayloadHeader const&, chip::System::PacketBufferHandle) CASESession.cpp:1148
#22 0x10297cbd4 in chip::Messaging::ExchangeContext::HandleMessage(chip::PacketHeader const&, chip::PayloadHeader const&, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) ExchangeContext.cpp:419
#23 0x10298237f in chip::Messaging::ExchangeManager::OnMessageReceived(chip::PacketHeader const&, chip::PayloadHeader const&, chip::SecureSessionHandle, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle, chip::SecureSessionMgr*) ExchangeMgr.cpp:308
#24 0x10299da21 in chip::SecureSessionMgr::MessageDispatch(chip::PacketHeader const&, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) SecureSessionMgr.cpp:317
#25 0x10299c4ec in chip::SecureSessionMgr::OnMessageReceived(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) SecureSessionMgr.cpp:306
#26 0x1029a047a in chip::TransportMgrBase::HandleMessageReceived(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) TransportMgrBase.cpp:57
#27 0x1029447ed in chip::Transport::Base::HandleMessageReceived(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle&&) Base.h:92
#28 0x1029445bd in LoopbackTransport::SendMessage(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) TestCASESession.cpp:59
#29 0x10299ff9d in chip::TransportMgrBase::SendMessage(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle&&) TransportMgrBase.cpp:27
previously allocated by thread T0 here:
#0 0x102d94540 in wrap_malloc+0xa0 (libclang_rt.asan_osx_dynamic.dylib:x86_64h+0x44540)
#1 0x10296d1f0 in chip::Platform::MemoryAlloc(unsigned long) CHIPMem-Malloc.cpp:106
#2 0x102971767 in chip::System::PacketBufferHandle::New(unsigned long, unsigned short) SystemPacketBuffer.cpp:488
#3 0x1029a9ce3 in chip::CASESession::SendSigmaR2() CASESession.cpp:512
#4 0x1029a8522 in chip::CASESession::HandleSigmaR1_and_SendSigmaR2(chip::System::PacketBufferHandle const&) CASESession.cpp:348
#5 0x1029b0880 in chip::CASESession::OnMessageReceived(chip::Messaging::ExchangeContext*, chip::PacketHeader const&, chip::PayloadHeader const&, chip::System::PacketBufferHandle) CASESession.cpp:1148
#6 0x10297cbd4 in chip::Messaging::ExchangeContext::HandleMessage(chip::PacketHeader const&, chip::PayloadHeader const&, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) ExchangeContext.cpp:419
#7 0x10298237f in chip::Messaging::ExchangeManager::OnMessageReceived(chip::PacketHeader const&, chip::PayloadHeader const&, chip::SecureSessionHandle, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle, chip::SecureSessionMgr*) ExchangeMgr.cpp:308
#8 0x10299da21 in chip::SecureSessionMgr::MessageDispatch(chip::PacketHeader const&, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) SecureSessionMgr.cpp:317
#9 0x10299c4ec in chip::SecureSessionMgr::OnMessageReceived(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) SecureSessionMgr.cpp:306
#10 0x1029a047a in chip::TransportMgrBase::HandleMessageReceived(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) TransportMgrBase.cpp:57
#11 0x1029447ed in chip::Transport::Base::HandleMessageReceived(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle&&) Base.h:92
#12 0x1029445bd in LoopbackTransport::SendMessage(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) TestCASESession.cpp:59
#13 0x10299ff9d in chip::TransportMgrBase::SendMessage(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle&&) TransportMgrBase.cpp:27
#14 0x1029b23db in chip::SessionEstablishmentExchangeDispatch::SendMessageImpl(chip::SecureSessionHandle, chip::PayloadHeader&, chip::System::PacketBufferHandle&&, chip::EncryptedPacketBufferHandle*) SessionEstablishmentExchangeDispatch.cpp:42
#15 0x10297df04 in chip::Messaging::ExchangeMessageDispatch::SendMessage(chip::SecureSessionHandle, unsigned short, bool, chip::Messaging::ReliableMessageContext*, bool, chip::Protocols::Id, unsigned char, chip::System::PacketBufferHandle) ExchangeMessageDispatch.cpp:95
#16 0x10297b063 in chip::Messaging::ExchangeContext::SendMessageImpl(chip::Protocols::Id, unsigned char, chip::System::PacketBufferHandle, chip::BitFlags<chip::Messaging::SendMessageFlags, unsigned short> const&, chip::Transport::PeerConnectionState*) ExchangeContext.cpp:163
#17 0x10297a75f in chip::Messaging::ExchangeContext::SendMessage(chip::Protocols::Id, unsigned char, chip::System::PacketBufferHandle, chip::BitFlags<chip::Messaging::SendMessageFlags, unsigned short> const&) ExchangeContext.cpp:107
#18 0x1029a83e8 in int chip::Messaging::ExchangeContext::SendMessage<chip::Protocols::SecureChannel::MsgType, void>(chip::Protocols::SecureChannel::MsgType, chip::System::PacketBufferHandle&&, chip::BitFlags<chip::Messaging::SendMessageFlags, unsigned short> const&) ExchangeContext.h:105
#19 0x1029a7255 in chip::CASESession::SendSigmaR1() CASESession.cpp:337
#20 0x1029a686a in chip::CASESession::EstablishSession(chip::Transport::PeerAddress, chip::Credentials::OperationalCredentialSet*, unsigned long long, unsigned short, chip::Messaging::ExchangeContext*, chip::SessionEstablishmentDelegate*) CASESession.cpp:240
#21 0x10294070a in CASE_SecurePairingHandshakeTestCommon(_nlTestSuite*, void*, chip::CASESession&, TestCASESecurePairingDelegate&) TestCASESession.cpp:173
#22 0x1029416aa in CASE_SecurePairingHandshakeTest(_nlTestSuite*, void*) TestCASESession.cpp:192
#23 0x1029b30c0 in nlTestRunner nlunit-test.c:213
#24 0x102944256 in TestCASESession() TestCASESession.cpp:395
#25 0x10293deca in main TestCASESession.driver.cpp:32
#26 0x7fff6c7eecc8 in start+0x0 (libdyld.dylib:x86_64+0x1acc8)
SUMMARY: AddressSanitizer: heap-use-after-free (libclang_rt.asan_osx_dynamic.dylib:x86_64h+0x195b5) in MemcmpInterceptorCommon(void*, int (*)(void const*, void const*, unsigned long), void const*, void const*, unsigned long)+0x155
Shadow bytes around the buggy address:
0x1c2c00000100: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1c2c00000110: 00 00 00 00 00 00 00 00 00 fa fa fa fa fa fa fa
0x1c2c00000120: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x1c2c00000130: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x1c2c00000140: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
=>0x1c2c00000150: fd fd fd fd fd fd fd fd fd fd fd fd fd fd[fd]fd
0x1c2c00000160: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x1c2c00000170: fd fd fd fd fd fd fd fd fa fa fa fa fa fa fa fa
0x1c2c00000180: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x1c2c00000190: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1c2c000001a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==29092==ABORTING
'#0:','Test-CHIP-SecurePairing'
```
|
True
|
TestCaseSession.cpp fails with is_asan=true - ```
READ of size 20 at 0x616000000af2 thread T0
#0 0x102d695b5 in MemcmpInterceptorCommon(void*, int (*)(void const*, void const*, unsigned long), void const*, void const*, unsigned long)+0x155 (libclang_rt.asan_osx_dynamic.dylib:x86_64h+0x195b5)
#1 0x102d69ab9 in wrap_memcmp+0x69 (libclang_rt.asan_osx_dynamic.dylib:x86_64h+0x19ab9)
#2 0x10294985d in chip::Credentials::CertificateKeyId::IsEqual(chip::Credentials::CertificateKeyId const&) const CHIPCert.cpp:787
#3 0x10294ae7f in chip::Credentials::ChipCertificateSet::FindValidCert(chip::Credentials::ChipDN const&, chip::Credentials::CertificateKeyId const&, chip::Credentials::ValidationContext&, chip::BitFlags<chip::Credentials::CertValidateFlags, unsigned char>, unsigned char, chip::Credentials::ChipCertificateData*&) CHIPCert.cpp:570
#4 0x10294aa6f in chip::Credentials::ChipCertificateSet::FindValidCert(chip::Credentials::ChipDN const&, chip::Credentials::CertificateKeyId const&, chip::Credentials::ValidationContext&, chip::Credentials::ChipCertificateData*&) CHIPCert.cpp:372
#5 0x102956561 in chip::Credentials::OperationalCredentialSet::FindValidCert(chip::Credentials::CertificateKeyId const&, chip::Credentials::ChipDN const&, chip::Credentials::CertificateKeyId const&, chip::Credentials::ValidationContext&, chip::Credentials::ChipCertificateData*&) CHIPOperationalCredentials.cpp:206
#6 0x1029ae409 in chip::CASESession::Validate_and_RetrieveResponderID(unsigned char const**, chip::Crypto::P256PublicKey&, unsigned char const**, unsigned short&) CASESession.cpp:1015
#7 0x1029ac053 in chip::CASESession::HandleSigmaR2(chip::System::PacketBufferHandle const&) CASESession.cpp:653
#8 0x1029ab524 in chip::CASESession::HandleSigmaR2_and_SendSigmaR3(chip::System::PacketBufferHandle const&) CASESession.cpp:557
#9 0x1029b0895 in chip::CASESession::OnMessageReceived(chip::Messaging::ExchangeContext*, chip::PacketHeader const&, chip::PayloadHeader const&, chip::System::PacketBufferHandle) CASESession.cpp:1152
#10 0x10297cbd4 in chip::Messaging::ExchangeContext::HandleMessage(chip::PacketHeader const&, chip::PayloadHeader const&, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) ExchangeContext.cpp:419
#11 0x102981c60 in chip::Messaging::ExchangeManager::OnMessageReceived(chip::PacketHeader const&, chip::PayloadHeader const&, chip::SecureSessionHandle, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle, chip::SecureSessionMgr*) ExchangeMgr.cpp:243
#12 0x10299da21 in chip::SecureSessionMgr::MessageDispatch(chip::PacketHeader const&, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) SecureSessionMgr.cpp:317
#13 0x10299c4ec in chip::SecureSessionMgr::OnMessageReceived(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) SecureSessionMgr.cpp:306
#14 0x1029a047a in chip::TransportMgrBase::HandleMessageReceived(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) TransportMgrBase.cpp:57
#15 0x1029447ed in chip::Transport::Base::HandleMessageReceived(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle&&) Base.h:92
#16 0x1029445bd in LoopbackTransport::SendMessage(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) TestCASESession.cpp:59
#17 0x10299ff9d in chip::TransportMgrBase::SendMessage(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle&&) TransportMgrBase.cpp:27
#18 0x1029b23db in chip::SessionEstablishmentExchangeDispatch::SendMessageImpl(chip::SecureSessionHandle, chip::PayloadHeader&, chip::System::PacketBufferHandle&&, chip::EncryptedPacketBufferHandle*) SessionEstablishmentExchangeDispatch.cpp:42
#19 0x10297df04 in chip::Messaging::ExchangeMessageDispatch::SendMessage(chip::SecureSessionHandle, unsigned short, bool, chip::Messaging::ReliableMessageContext*, bool, chip::Protocols::Id, unsigned char, chip::System::PacketBufferHandle) ExchangeMessageDispatch.cpp:95
#20 0x10297b063 in chip::Messaging::ExchangeContext::SendMessageImpl(chip::Protocols::Id, unsigned char, chip::System::PacketBufferHandle, chip::BitFlags<chip::Messaging::SendMessageFlags, unsigned short> const&, chip::Transport::PeerConnectionState*) ExchangeContext.cpp:163
#21 0x10297a75f in chip::Messaging::ExchangeContext::SendMessage(chip::Protocols::Id, unsigned char, chip::System::PacketBufferHandle, chip::BitFlags<chip::Messaging::SendMessageFlags, unsigned short> const&) ExchangeContext.cpp:107
#22 0x1029a83e8 in int chip::Messaging::ExchangeContext::SendMessage<chip::Protocols::SecureChannel::MsgType, void>(chip::Protocols::SecureChannel::MsgType, chip::System::PacketBufferHandle&&, chip::BitFlags<chip::Messaging::SendMessageFlags, unsigned short> const&) ExchangeContext.h:105
#23 0x1029aa264 in chip::CASESession::SendSigmaR2() CASESession.cpp:540
#24 0x1029a8522 in chip::CASESession::HandleSigmaR1_and_SendSigmaR2(chip::System::PacketBufferHandle const&) CASESession.cpp:348
#25 0x1029b0880 in chip::CASESession::OnMessageReceived(chip::Messaging::ExchangeContext*, chip::PacketHeader const&, chip::PayloadHeader const&, chip::System::PacketBufferHandle) CASESession.cpp:1148
#26 0x10297cbd4 in chip::Messaging::ExchangeContext::HandleMessage(chip::PacketHeader const&, chip::PayloadHeader const&, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) ExchangeContext.cpp:419
#27 0x10298237f in chip::Messaging::ExchangeManager::OnMessageReceived(chip::PacketHeader const&, chip::PayloadHeader const&, chip::SecureSessionHandle, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle, chip::SecureSessionMgr*) ExchangeMgr.cpp:308
#28 0x10299da21 in chip::SecureSessionMgr::MessageDispatch(chip::PacketHeader const&, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) SecureSessionMgr.cpp:317
#29 0x10299c4ec in chip::SecureSessionMgr::OnMessageReceived(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) SecureSessionMgr.cpp:306
#30 0x1029a047a in chip::TransportMgrBase::HandleMessageReceived(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) TransportMgrBase.cpp:57
#31 0x1029447ed in chip::Transport::Base::HandleMessageReceived(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle&&) Base.h:92
#32 0x1029445bd in LoopbackTransport::SendMessage(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) TestCASESession.cpp:59
#33 0x10299ff9d in chip::TransportMgrBase::SendMessage(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle&&) TransportMgrBase.cpp:27
#34 0x1029b23db in chip::SessionEstablishmentExchangeDispatch::SendMessageImpl(chip::SecureSessionHandle, chip::PayloadHeader&, chip::System::PacketBufferHandle&&, chip::EncryptedPacketBufferHandle*) SessionEstablishmentExchangeDispatch.cpp:42
#35 0x10297df04 in chip::Messaging::ExchangeMessageDispatch::SendMessage(chip::SecureSessionHandle, unsigned short, bool, chip::Messaging::ReliableMessageContext*, bool, chip::Protocols::Id, unsigned char, chip::System::PacketBufferHandle) ExchangeMessageDispatch.cpp:95
#36 0x10297b063 in chip::Messaging::ExchangeContext::SendMessageImpl(chip::Protocols::Id, unsigned char, chip::System::PacketBufferHandle, chip::BitFlags<chip::Messaging::SendMessageFlags, unsigned short> const&, chip::Transport::PeerConnectionState*) ExchangeContext.cpp:163
#37 0x10297a75f in chip::Messaging::ExchangeContext::SendMessage(chip::Protocols::Id, unsigned char, chip::System::PacketBufferHandle, chip::BitFlags<chip::Messaging::SendMessageFlags, unsigned short> const&) ExchangeContext.cpp:107
#38 0x1029a83e8 in int chip::Messaging::ExchangeContext::SendMessage<chip::Protocols::SecureChannel::MsgType, void>(chip::Protocols::SecureChannel::MsgType, chip::System::PacketBufferHandle&&, chip::BitFlags<chip::Messaging::SendMessageFlags, unsigned short> const&) ExchangeContext.h:105
#39 0x1029a7255 in chip::CASESession::SendSigmaR1() CASESession.cpp:337
#40 0x1029a686a in chip::CASESession::EstablishSession(chip::Transport::PeerAddress, chip::Credentials::OperationalCredentialSet*, unsigned long long, unsigned short, chip::Messaging::ExchangeContext*, chip::SessionEstablishmentDelegate*) CASESession.cpp:240
#41 0x10294070a in CASE_SecurePairingHandshakeTestCommon(_nlTestSuite*, void*, chip::CASESession&, TestCASESecurePairingDelegate&) TestCASESession.cpp:173
#42 0x1029421a2 in CASE_SecurePairingSerializeTest(_nlTestSuite*, void*) TestCASESession.cpp:218
#43 0x1029b30c0 in nlTestRunner nlunit-test.c:213
#44 0x102944256 in TestCASESession() TestCASESession.cpp:395
#45 0x10293deca in main TestCASESession.driver.cpp:32
#46 0x7fff6c7eecc8 in start+0x0 (libdyld.dylib:x86_64+0x1acc8)
0x616000000af2 is located 370 bytes inside of 575-byte region [0x616000000980,0x616000000bbf)
freed by thread T0 here:
#0 0x102d94689 in wrap_free+0xa9 (libclang_rt.asan_osx_dynamic.dylib:x86_64h+0x44689)
#1 0x10296d327 in chip::Platform::MemoryFree(void*) CHIPMem-Malloc.cpp:126
#2 0x102970795 in chip::System::PacketBuffer::Free(chip::System::PacketBuffer*) SystemPacketBuffer.cpp:575
#3 0x102944a3f in chip::System::PacketBufferHandle::operator=(std::nullptr_t) SystemPacketBuffer.h:466
#4 0x1029449b8 in chip::System::PacketBufferHandle::~PacketBufferHandle() SystemPacketBuffer.h:443
#5 0x1029448c4 in chip::System::PacketBufferHandle::~PacketBufferHandle() SystemPacketBuffer.h:443
#6 0x10297cbe0 in chip::Messaging::ExchangeContext::HandleMessage(chip::PacketHeader const&, chip::PayloadHeader const&, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) ExchangeContext.cpp:419
#7 0x102981c60 in chip::Messaging::ExchangeManager::OnMessageReceived(chip::PacketHeader const&, chip::PayloadHeader const&, chip::SecureSessionHandle, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle, chip::SecureSessionMgr*) ExchangeMgr.cpp:243
#8 0x10299da21 in chip::SecureSessionMgr::MessageDispatch(chip::PacketHeader const&, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) SecureSessionMgr.cpp:317
#9 0x10299c4ec in chip::SecureSessionMgr::OnMessageReceived(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) SecureSessionMgr.cpp:306
#10 0x1029a047a in chip::TransportMgrBase::HandleMessageReceived(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) TransportMgrBase.cpp:57
#11 0x1029447ed in chip::Transport::Base::HandleMessageReceived(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle&&) Base.h:92
#12 0x1029445bd in LoopbackTransport::SendMessage(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) TestCASESession.cpp:59
#13 0x10299ff9d in chip::TransportMgrBase::SendMessage(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle&&) TransportMgrBase.cpp:27
#14 0x1029b23db in chip::SessionEstablishmentExchangeDispatch::SendMessageImpl(chip::SecureSessionHandle, chip::PayloadHeader&, chip::System::PacketBufferHandle&&, chip::EncryptedPacketBufferHandle*) SessionEstablishmentExchangeDispatch.cpp:42
#15 0x10297df04 in chip::Messaging::ExchangeMessageDispatch::SendMessage(chip::SecureSessionHandle, unsigned short, bool, chip::Messaging::ReliableMessageContext*, bool, chip::Protocols::Id, unsigned char, chip::System::PacketBufferHandle) ExchangeMessageDispatch.cpp:95
#16 0x10297b063 in chip::Messaging::ExchangeContext::SendMessageImpl(chip::Protocols::Id, unsigned char, chip::System::PacketBufferHandle, chip::BitFlags<chip::Messaging::SendMessageFlags, unsigned short> const&, chip::Transport::PeerConnectionState*) ExchangeContext.cpp:163
#17 0x10297a75f in chip::Messaging::ExchangeContext::SendMessage(chip::Protocols::Id, unsigned char, chip::System::PacketBufferHandle, chip::BitFlags<chip::Messaging::SendMessageFlags, unsigned short> const&) ExchangeContext.cpp:107
#18 0x1029a83e8 in int chip::Messaging::ExchangeContext::SendMessage<chip::Protocols::SecureChannel::MsgType, void>(chip::Protocols::SecureChannel::MsgType, chip::System::PacketBufferHandle&&, chip::BitFlags<chip::Messaging::SendMessageFlags, unsigned short> const&) ExchangeContext.h:105
#19 0x1029aa264 in chip::CASESession::SendSigmaR2() CASESession.cpp:540
#20 0x1029a8522 in chip::CASESession::HandleSigmaR1_and_SendSigmaR2(chip::System::PacketBufferHandle const&) CASESession.cpp:348
#21 0x1029b0880 in chip::CASESession::OnMessageReceived(chip::Messaging::ExchangeContext*, chip::PacketHeader const&, chip::PayloadHeader const&, chip::System::PacketBufferHandle) CASESession.cpp:1148
#22 0x10297cbd4 in chip::Messaging::ExchangeContext::HandleMessage(chip::PacketHeader const&, chip::PayloadHeader const&, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) ExchangeContext.cpp:419
#23 0x10298237f in chip::Messaging::ExchangeManager::OnMessageReceived(chip::PacketHeader const&, chip::PayloadHeader const&, chip::SecureSessionHandle, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle, chip::SecureSessionMgr*) ExchangeMgr.cpp:308
#24 0x10299da21 in chip::SecureSessionMgr::MessageDispatch(chip::PacketHeader const&, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) SecureSessionMgr.cpp:317
#25 0x10299c4ec in chip::SecureSessionMgr::OnMessageReceived(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) SecureSessionMgr.cpp:306
#26 0x1029a047a in chip::TransportMgrBase::HandleMessageReceived(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) TransportMgrBase.cpp:57
#27 0x1029447ed in chip::Transport::Base::HandleMessageReceived(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle&&) Base.h:92
#28 0x1029445bd in LoopbackTransport::SendMessage(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) TestCASESession.cpp:59
#29 0x10299ff9d in chip::TransportMgrBase::SendMessage(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle&&) TransportMgrBase.cpp:27
previously allocated by thread T0 here:
#0 0x102d94540 in wrap_malloc+0xa0 (libclang_rt.asan_osx_dynamic.dylib:x86_64h+0x44540)
#1 0x10296d1f0 in chip::Platform::MemoryAlloc(unsigned long) CHIPMem-Malloc.cpp:106
#2 0x102971767 in chip::System::PacketBufferHandle::New(unsigned long, unsigned short) SystemPacketBuffer.cpp:488
#3 0x1029a9ce3 in chip::CASESession::SendSigmaR2() CASESession.cpp:512
#4 0x1029a8522 in chip::CASESession::HandleSigmaR1_and_SendSigmaR2(chip::System::PacketBufferHandle const&) CASESession.cpp:348
#5 0x1029b0880 in chip::CASESession::OnMessageReceived(chip::Messaging::ExchangeContext*, chip::PacketHeader const&, chip::PayloadHeader const&, chip::System::PacketBufferHandle) CASESession.cpp:1148
#6 0x10297cbd4 in chip::Messaging::ExchangeContext::HandleMessage(chip::PacketHeader const&, chip::PayloadHeader const&, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) ExchangeContext.cpp:419
#7 0x10298237f in chip::Messaging::ExchangeManager::OnMessageReceived(chip::PacketHeader const&, chip::PayloadHeader const&, chip::SecureSessionHandle, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle, chip::SecureSessionMgr*) ExchangeMgr.cpp:308
#8 0x10299da21 in chip::SecureSessionMgr::MessageDispatch(chip::PacketHeader const&, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) SecureSessionMgr.cpp:317
#9 0x10299c4ec in chip::SecureSessionMgr::OnMessageReceived(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) SecureSessionMgr.cpp:306
#10 0x1029a047a in chip::TransportMgrBase::HandleMessageReceived(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) TransportMgrBase.cpp:57
#11 0x1029447ed in chip::Transport::Base::HandleMessageReceived(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle&&) Base.h:92
#12 0x1029445bd in LoopbackTransport::SendMessage(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) TestCASESession.cpp:59
#13 0x10299ff9d in chip::TransportMgrBase::SendMessage(chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle&&) TransportMgrBase.cpp:27
#14 0x1029b23db in chip::SessionEstablishmentExchangeDispatch::SendMessageImpl(chip::SecureSessionHandle, chip::PayloadHeader&, chip::System::PacketBufferHandle&&, chip::EncryptedPacketBufferHandle*) SessionEstablishmentExchangeDispatch.cpp:42
#15 0x10297df04 in chip::Messaging::ExchangeMessageDispatch::SendMessage(chip::SecureSessionHandle, unsigned short, bool, chip::Messaging::ReliableMessageContext*, bool, chip::Protocols::Id, unsigned char, chip::System::PacketBufferHandle) ExchangeMessageDispatch.cpp:95
#16 0x10297b063 in chip::Messaging::ExchangeContext::SendMessageImpl(chip::Protocols::Id, unsigned char, chip::System::PacketBufferHandle, chip::BitFlags<chip::Messaging::SendMessageFlags, unsigned short> const&, chip::Transport::PeerConnectionState*) ExchangeContext.cpp:163
#17 0x10297a75f in chip::Messaging::ExchangeContext::SendMessage(chip::Protocols::Id, unsigned char, chip::System::PacketBufferHandle, chip::BitFlags<chip::Messaging::SendMessageFlags, unsigned short> const&) ExchangeContext.cpp:107
#18 0x1029a83e8 in int chip::Messaging::ExchangeContext::SendMessage<chip::Protocols::SecureChannel::MsgType, void>(chip::Protocols::SecureChannel::MsgType, chip::System::PacketBufferHandle&&, chip::BitFlags<chip::Messaging::SendMessageFlags, unsigned short> const&) ExchangeContext.h:105
#19 0x1029a7255 in chip::CASESession::SendSigmaR1() CASESession.cpp:337
#20 0x1029a686a in chip::CASESession::EstablishSession(chip::Transport::PeerAddress, chip::Credentials::OperationalCredentialSet*, unsigned long long, unsigned short, chip::Messaging::ExchangeContext*, chip::SessionEstablishmentDelegate*) CASESession.cpp:240
#21 0x10294070a in CASE_SecurePairingHandshakeTestCommon(_nlTestSuite*, void*, chip::CASESession&, TestCASESecurePairingDelegate&) TestCASESession.cpp:173
#22 0x1029416aa in CASE_SecurePairingHandshakeTest(_nlTestSuite*, void*) TestCASESession.cpp:192
#23 0x1029b30c0 in nlTestRunner nlunit-test.c:213
#24 0x102944256 in TestCASESession() TestCASESession.cpp:395
#25 0x10293deca in main TestCASESession.driver.cpp:32
#26 0x7fff6c7eecc8 in start+0x0 (libdyld.dylib:x86_64+0x1acc8)
SUMMARY: AddressSanitizer: heap-use-after-free (libclang_rt.asan_osx_dynamic.dylib:x86_64h+0x195b5) in MemcmpInterceptorCommon(void*, int (*)(void const*, void const*, unsigned long), void const*, void const*, unsigned long)+0x155
Shadow bytes around the buggy address:
0x1c2c00000100: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1c2c00000110: 00 00 00 00 00 00 00 00 00 fa fa fa fa fa fa fa
0x1c2c00000120: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x1c2c00000130: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x1c2c00000140: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
=>0x1c2c00000150: fd fd fd fd fd fd fd fd fd fd fd fd fd fd[fd]fd
0x1c2c00000160: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x1c2c00000170: fd fd fd fd fd fd fd fd fa fa fa fa fa fa fa fa
0x1c2c00000180: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x1c2c00000190: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1c2c000001a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==29092==ABORTING
'#0:','Test-CHIP-SecurePairing'
```
|
non_test
|
testcasesession cpp fails with is asan true read of size at thread in memcmpinterceptorcommon void int void const void const unsigned long void const void const unsigned long libclang rt asan osx dynamic dylib in wrap memcmp libclang rt asan osx dynamic dylib in chip credentials certificatekeyid isequal chip credentials certificatekeyid const const chipcert cpp in chip credentials chipcertificateset findvalidcert chip credentials chipdn const chip credentials certificatekeyid const chip credentials validationcontext chip bitflags unsigned char chip credentials chipcertificatedata chipcert cpp in chip credentials chipcertificateset findvalidcert chip credentials chipdn const chip credentials certificatekeyid const chip credentials validationcontext chip credentials chipcertificatedata chipcert cpp in chip credentials operationalcredentialset findvalidcert chip credentials certificatekeyid const chip credentials chipdn const chip credentials certificatekeyid const chip credentials validationcontext chip credentials chipcertificatedata chipoperationalcredentials cpp in chip casesession validate and retrieveresponderid unsigned char const chip crypto unsigned char const unsigned short casesession cpp in chip casesession chip system packetbufferhandle const casesession cpp in chip casesession and chip system packetbufferhandle const casesession cpp in chip casesession onmessagereceived chip messaging exchangecontext chip packetheader const chip payloadheader const chip system packetbufferhandle casesession cpp in chip messaging exchangecontext handlemessage chip packetheader const chip payloadheader const chip transport peeraddress const chip system packetbufferhandle exchangecontext cpp in chip messaging exchangemanager onmessagereceived chip packetheader const chip payloadheader const chip securesessionhandle chip transport peeraddress const chip system packetbufferhandle chip securesessionmgr exchangemgr cpp in chip securesessionmgr messagedispatch chip packetheader const chip transport peeraddress const chip system packetbufferhandle securesessionmgr cpp in chip securesessionmgr onmessagereceived chip transport peeraddress const chip system packetbufferhandle securesessionmgr cpp in chip transportmgrbase handlemessagereceived chip transport peeraddress const chip system packetbufferhandle transportmgrbase cpp in chip transport base handlemessagereceived chip transport peeraddress const chip system packetbufferhandle base h in loopbacktransport sendmessage chip transport peeraddress const chip system packetbufferhandle testcasesession cpp in chip transportmgrbase sendmessage chip transport peeraddress const chip system packetbufferhandle transportmgrbase cpp in chip sessionestablishmentexchangedispatch sendmessageimpl chip securesessionhandle chip payloadheader chip system packetbufferhandle chip encryptedpacketbufferhandle sessionestablishmentexchangedispatch cpp in chip messaging exchangemessagedispatch sendmessage chip securesessionhandle unsigned short bool chip messaging reliablemessagecontext bool chip protocols id unsigned char chip system packetbufferhandle exchangemessagedispatch cpp in chip messaging exchangecontext sendmessageimpl chip protocols id unsigned char chip system packetbufferhandle chip bitflags const chip transport peerconnectionstate exchangecontext cpp in chip messaging exchangecontext sendmessage chip protocols id unsigned char chip system packetbufferhandle chip bitflags const exchangecontext cpp in int chip messaging exchangecontext sendmessage chip protocols securechannel msgtype chip system packetbufferhandle chip bitflags const exchangecontext h in chip casesession casesession cpp in chip casesession and chip system packetbufferhandle const casesession cpp in chip casesession onmessagereceived chip messaging exchangecontext chip packetheader const chip payloadheader const chip system packetbufferhandle casesession cpp in chip messaging exchangecontext handlemessage chip packetheader const chip payloadheader const chip transport peeraddress const chip system packetbufferhandle exchangecontext cpp in chip messaging exchangemanager onmessagereceived chip packetheader const chip payloadheader const chip securesessionhandle chip transport peeraddress const chip system packetbufferhandle chip securesessionmgr exchangemgr cpp in chip securesessionmgr messagedispatch chip packetheader const chip transport peeraddress const chip system packetbufferhandle securesessionmgr cpp in chip securesessionmgr onmessagereceived chip transport peeraddress const chip system packetbufferhandle securesessionmgr cpp in chip transportmgrbase handlemessagereceived chip transport peeraddress const chip system packetbufferhandle transportmgrbase cpp in chip transport base handlemessagereceived chip transport peeraddress const chip system packetbufferhandle base h in loopbacktransport sendmessage chip transport peeraddress const chip system packetbufferhandle testcasesession cpp in chip transportmgrbase sendmessage chip transport peeraddress const chip system packetbufferhandle transportmgrbase cpp in chip sessionestablishmentexchangedispatch sendmessageimpl chip securesessionhandle chip payloadheader chip system packetbufferhandle chip encryptedpacketbufferhandle sessionestablishmentexchangedispatch cpp in chip messaging exchangemessagedispatch sendmessage chip securesessionhandle unsigned short bool chip messaging reliablemessagecontext bool chip protocols id unsigned char chip system packetbufferhandle exchangemessagedispatch cpp in chip messaging exchangecontext sendmessageimpl chip protocols id unsigned char chip system packetbufferhandle chip bitflags const chip transport peerconnectionstate exchangecontext cpp in chip messaging exchangecontext sendmessage chip protocols id unsigned char chip system packetbufferhandle chip bitflags const exchangecontext cpp in int chip messaging exchangecontext sendmessage chip protocols securechannel msgtype chip system packetbufferhandle chip bitflags const exchangecontext h in chip casesession casesession cpp in chip casesession establishsession chip transport peeraddress chip credentials operationalcredentialset unsigned long long unsigned short chip messaging exchangecontext chip sessionestablishmentdelegate casesession cpp in case securepairinghandshaketestcommon nltestsuite void chip casesession testcasesecurepairingdelegate testcasesession cpp in case securepairingserializetest nltestsuite void testcasesession cpp in nltestrunner nlunit test c in testcasesession testcasesession cpp in main testcasesession driver cpp in start libdyld dylib is located bytes inside of byte region freed by thread here in wrap free libclang rt asan osx dynamic dylib in chip platform memoryfree void chipmem malloc cpp in chip system packetbuffer free chip system packetbuffer systempacketbuffer cpp in chip system packetbufferhandle operator std nullptr t systempacketbuffer h in chip system packetbufferhandle packetbufferhandle systempacketbuffer h in chip system packetbufferhandle packetbufferhandle systempacketbuffer h in chip messaging exchangecontext handlemessage chip packetheader const chip payloadheader const chip transport peeraddress const chip system packetbufferhandle exchangecontext cpp in chip messaging exchangemanager onmessagereceived chip packetheader const chip payloadheader const chip securesessionhandle chip transport peeraddress const chip system packetbufferhandle chip securesessionmgr exchangemgr cpp in chip securesessionmgr messagedispatch chip packetheader const chip transport peeraddress const chip system packetbufferhandle securesessionmgr cpp in chip securesessionmgr onmessagereceived chip transport peeraddress const chip system packetbufferhandle securesessionmgr cpp in chip transportmgrbase handlemessagereceived chip transport peeraddress const chip system packetbufferhandle transportmgrbase cpp in chip transport base handlemessagereceived chip transport peeraddress const chip system packetbufferhandle base h in loopbacktransport sendmessage chip transport peeraddress const chip system packetbufferhandle testcasesession cpp in chip transportmgrbase sendmessage chip transport peeraddress const chip system packetbufferhandle transportmgrbase cpp in chip sessionestablishmentexchangedispatch sendmessageimpl chip securesessionhandle chip payloadheader chip system packetbufferhandle chip encryptedpacketbufferhandle sessionestablishmentexchangedispatch cpp in chip messaging exchangemessagedispatch sendmessage chip securesessionhandle unsigned short bool chip messaging reliablemessagecontext bool chip protocols id unsigned char chip system packetbufferhandle exchangemessagedispatch cpp in chip messaging exchangecontext sendmessageimpl chip protocols id unsigned char chip system packetbufferhandle chip bitflags const chip transport peerconnectionstate exchangecontext cpp in chip messaging exchangecontext sendmessage chip protocols id unsigned char chip system packetbufferhandle chip bitflags const exchangecontext cpp in int chip messaging exchangecontext sendmessage chip protocols securechannel msgtype chip system packetbufferhandle chip bitflags const exchangecontext h in chip casesession casesession cpp in chip casesession and chip system packetbufferhandle const casesession cpp in chip casesession onmessagereceived chip messaging exchangecontext chip packetheader const chip payloadheader const chip system packetbufferhandle casesession cpp in chip messaging exchangecontext handlemessage chip packetheader const chip payloadheader const chip transport peeraddress const chip system packetbufferhandle exchangecontext cpp in chip messaging exchangemanager onmessagereceived chip packetheader const chip payloadheader const chip securesessionhandle chip transport peeraddress const chip system packetbufferhandle chip securesessionmgr exchangemgr cpp in chip securesessionmgr messagedispatch chip packetheader const chip transport peeraddress const chip system packetbufferhandle securesessionmgr cpp in chip securesessionmgr onmessagereceived chip transport peeraddress const chip system packetbufferhandle securesessionmgr cpp in chip transportmgrbase handlemessagereceived chip transport peeraddress const chip system packetbufferhandle transportmgrbase cpp in chip transport base handlemessagereceived chip transport peeraddress const chip system packetbufferhandle base h in loopbacktransport sendmessage chip transport peeraddress const chip system packetbufferhandle testcasesession cpp in chip transportmgrbase sendmessage chip transport peeraddress const chip system packetbufferhandle transportmgrbase cpp previously allocated by thread here in wrap malloc libclang rt asan osx dynamic dylib in chip platform memoryalloc unsigned long chipmem malloc cpp in chip system packetbufferhandle new unsigned long unsigned short systempacketbuffer cpp in chip casesession casesession cpp in chip casesession and chip system packetbufferhandle const casesession cpp in chip casesession onmessagereceived chip messaging exchangecontext chip packetheader const chip payloadheader const chip system packetbufferhandle casesession cpp in chip messaging exchangecontext handlemessage chip packetheader const chip payloadheader const chip transport peeraddress const chip system packetbufferhandle exchangecontext cpp in chip messaging exchangemanager onmessagereceived chip packetheader const chip payloadheader const chip securesessionhandle chip transport peeraddress const chip system packetbufferhandle chip securesessionmgr exchangemgr cpp in chip securesessionmgr messagedispatch chip packetheader const chip transport peeraddress const chip system packetbufferhandle securesessionmgr cpp in chip securesessionmgr onmessagereceived chip transport peeraddress const chip system packetbufferhandle securesessionmgr cpp in chip transportmgrbase handlemessagereceived chip transport peeraddress const chip system packetbufferhandle transportmgrbase cpp in chip transport base handlemessagereceived chip transport peeraddress const chip system packetbufferhandle base h in loopbacktransport sendmessage chip transport peeraddress const chip system packetbufferhandle testcasesession cpp in chip transportmgrbase sendmessage chip transport peeraddress const chip system packetbufferhandle transportmgrbase cpp in chip sessionestablishmentexchangedispatch sendmessageimpl chip securesessionhandle chip payloadheader chip system packetbufferhandle chip encryptedpacketbufferhandle sessionestablishmentexchangedispatch cpp in chip messaging exchangemessagedispatch sendmessage chip securesessionhandle unsigned short bool chip messaging reliablemessagecontext bool chip protocols id unsigned char chip system packetbufferhandle exchangemessagedispatch cpp in chip messaging exchangecontext sendmessageimpl chip protocols id unsigned char chip system packetbufferhandle chip bitflags const chip transport peerconnectionstate exchangecontext cpp in chip messaging exchangecontext sendmessage chip protocols id unsigned char chip system packetbufferhandle chip bitflags const exchangecontext cpp in int chip messaging exchangecontext sendmessage chip protocols securechannel msgtype chip system packetbufferhandle chip bitflags const exchangecontext h in chip casesession casesession cpp in chip casesession establishsession chip transport peeraddress chip credentials operationalcredentialset unsigned long long unsigned short chip messaging exchangecontext chip sessionestablishmentdelegate casesession cpp in case securepairinghandshaketestcommon nltestsuite void chip casesession testcasesecurepairingdelegate testcasesession cpp in case securepairinghandshaketest nltestsuite void testcasesession cpp in nltestrunner nlunit test c in testcasesession testcasesession cpp in main testcasesession driver cpp in start libdyld dylib summary addresssanitizer heap use after free libclang rt asan osx dynamic dylib in memcmpinterceptorcommon void int void const void const unsigned long void const void const unsigned long shadow bytes around the buggy address fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa shadow byte legend one shadow byte represents application bytes addressable partially addressable heap left redzone fa freed heap region fd stack left redzone stack mid redzone stack right redzone stack after return stack use after scope global redzone global init order poisoned by user container overflow fc array cookie ac intra object redzone bb asan internal fe left alloca redzone ca right alloca redzone cb shadow gap cc aborting test chip securepairing
| 0
|
82,703
| 16,016,965,923
|
IssuesEvent
|
2021-04-20 17:13:31
|
ESCOMP/CTSM
|
https://api.github.com/repos/ESCOMP/CTSM
|
closed
|
Remove some dead code
|
tag: simple bfb type: code cleanup
|
We should remove this dead code:
https://github.com/ESCOMP/CTSM/blob/30ca18494d320ba0af15212d0a26b2bfa3ef13ca/src/cpl/utils/lnd_import_export_utils.F90#L87-L94
@swensosc says:
> I also noticed something that may have come in from one of my code changes a long while ago [referencing the above code]:
> 1) this was some code that I think was from when we were looking at why the humidity was so low during days with rain, and I think we decided it was due to the older cruncep forcing having some inconsistencies. But it was really just to see what would happen to things like transpiration if humidity was higher. 2) it is never triggered due to the if-block.
> So maybe that could be removed at some point.
|
1.0
|
Remove some dead code - We should remove this dead code:
https://github.com/ESCOMP/CTSM/blob/30ca18494d320ba0af15212d0a26b2bfa3ef13ca/src/cpl/utils/lnd_import_export_utils.F90#L87-L94
@swensosc says:
> I also noticed something that may have come in from one of my code changes a long while ago [referencing the above code]:
> 1) this was some code that I think was from when we were looking at why the humidity was so low during days with rain, and I think we decided it was due to the older cruncep forcing having some inconsistencies. But it was really just to see what would happen to things like transpiration if humidity was higher. 2) it is never triggered due to the if-block.
> So maybe that could be removed at some point.
|
non_test
|
remove some dead code we should remove this dead code swensosc says i also noticed something that may have come in from one of my code changes a long while ago this was some code that i think was from when we were looking at why the humidity was so low during days with rain and i think we decided it was due to the older cruncep forcing having some inconsistencies but it was really just to see what would happen to things like transpiration if humidity was higher it is never triggered due to the if block so maybe that could be removed at some point
| 0
|
142,604
| 19,099,368,669
|
IssuesEvent
|
2021-11-29 20:27:34
|
harrinry/stream-chat-react
|
https://api.github.com/repos/harrinry/stream-chat-react
|
opened
|
CVE-2020-15168 (Medium) detected in node-fetch-1.7.3.tgz
|
security vulnerability
|
## CVE-2020-15168 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-fetch-1.7.3.tgz</b></p></summary>
<p>A light-weight module that brings window.fetch to node.js and io.js</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-fetch/-/node-fetch-1.7.3.tgz">https://registry.npmjs.org/node-fetch/-/node-fetch-1.7.3.tgz</a></p>
<p>Path to dependency file: stream-chat-react/package.json</p>
<p>Path to vulnerable library: stream-chat-react/node_modules/node-fetch/package.json</p>
<p>
Dependency Hierarchy:
- react-images-1.1.7.tgz (Root Library)
- glam-5.0.1.tgz
- fbjs-0.8.17.tgz
- isomorphic-fetch-2.2.1.tgz
- :x: **node-fetch-1.7.3.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/harrinry/stream-chat-react/commit/a80df0ece7581dc566b7c05d5f5ae6ecc66b730f">a80df0ece7581dc566b7c05d5f5ae6ecc66b730f</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>
node-fetch before versions 2.6.1 and 3.0.0-beta.9 did not honor the size option after following a redirect, which means that when a content size was over the limit, a FetchError would never get thrown and the process would end without failure. For most people, this fix will have a little or no impact. However, if you are relying on node-fetch to gate files above a size, the impact could be significant, for example: If you don't double-check the size of the data after fetch() has completed, your JS thread could get tied up doing work on a large file (DoS) and/or cost you money in computing.
<p>Publish Date: 2020-09-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15168>CVE-2020-15168</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/node-fetch/node-fetch/security/advisories/GHSA-w7rc-rwvf-8q5r">https://github.com/node-fetch/node-fetch/security/advisories/GHSA-w7rc-rwvf-8q5r</a></p>
<p>Release Date: 2020-09-17</p>
<p>Fix Resolution: 2.6.1,3.0.0-beta.9</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"node-fetch","packageVersion":"1.7.3","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"react-images:1.1.7;glam:5.0.1;fbjs:0.8.17;isomorphic-fetch:2.2.1;node-fetch:1.7.3","isMinimumFixVersionAvailable":true,"minimumFixVersion":"2.6.1,3.0.0-beta.9","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-15168","vulnerabilityDetails":"node-fetch before versions 2.6.1 and 3.0.0-beta.9 did not honor the size option after following a redirect, which means that when a content size was over the limit, a FetchError would never get thrown and the process would end without failure. For most people, this fix will have a little or no impact. However, if you are relying on node-fetch to gate files above a size, the impact could be significant, for example: If you don\u0027t double-check the size of the data after fetch() has completed, your JS thread could get tied up doing work on a large file (DoS) and/or cost you money in computing.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15168","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"Low","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> -->
|
True
|
CVE-2020-15168 (Medium) detected in node-fetch-1.7.3.tgz - ## CVE-2020-15168 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-fetch-1.7.3.tgz</b></p></summary>
<p>A light-weight module that brings window.fetch to node.js and io.js</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-fetch/-/node-fetch-1.7.3.tgz">https://registry.npmjs.org/node-fetch/-/node-fetch-1.7.3.tgz</a></p>
<p>Path to dependency file: stream-chat-react/package.json</p>
<p>Path to vulnerable library: stream-chat-react/node_modules/node-fetch/package.json</p>
<p>
Dependency Hierarchy:
- react-images-1.1.7.tgz (Root Library)
- glam-5.0.1.tgz
- fbjs-0.8.17.tgz
- isomorphic-fetch-2.2.1.tgz
- :x: **node-fetch-1.7.3.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/harrinry/stream-chat-react/commit/a80df0ece7581dc566b7c05d5f5ae6ecc66b730f">a80df0ece7581dc566b7c05d5f5ae6ecc66b730f</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>
node-fetch before versions 2.6.1 and 3.0.0-beta.9 did not honor the size option after following a redirect, which means that when a content size was over the limit, a FetchError would never get thrown and the process would end without failure. For most people, this fix will have a little or no impact. However, if you are relying on node-fetch to gate files above a size, the impact could be significant, for example: If you don't double-check the size of the data after fetch() has completed, your JS thread could get tied up doing work on a large file (DoS) and/or cost you money in computing.
<p>Publish Date: 2020-09-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15168>CVE-2020-15168</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/node-fetch/node-fetch/security/advisories/GHSA-w7rc-rwvf-8q5r">https://github.com/node-fetch/node-fetch/security/advisories/GHSA-w7rc-rwvf-8q5r</a></p>
<p>Release Date: 2020-09-17</p>
<p>Fix Resolution: 2.6.1,3.0.0-beta.9</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"node-fetch","packageVersion":"1.7.3","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"react-images:1.1.7;glam:5.0.1;fbjs:0.8.17;isomorphic-fetch:2.2.1;node-fetch:1.7.3","isMinimumFixVersionAvailable":true,"minimumFixVersion":"2.6.1,3.0.0-beta.9","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-15168","vulnerabilityDetails":"node-fetch before versions 2.6.1 and 3.0.0-beta.9 did not honor the size option after following a redirect, which means that when a content size was over the limit, a FetchError would never get thrown and the process would end without failure. For most people, this fix will have a little or no impact. However, if you are relying on node-fetch to gate files above a size, the impact could be significant, for example: If you don\u0027t double-check the size of the data after fetch() has completed, your JS thread could get tied up doing work on a large file (DoS) and/or cost you money in computing.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15168","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"Low","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> -->
|
non_test
|
cve medium detected in node fetch tgz cve medium severity vulnerability vulnerable library node fetch tgz a light weight module that brings window fetch to node js and io js library home page a href path to dependency file stream chat react package json path to vulnerable library stream chat react node modules node fetch package json dependency hierarchy react images tgz root library glam tgz fbjs tgz isomorphic fetch tgz x node fetch tgz vulnerable library found in head commit a href found in base branch master vulnerability details node fetch before versions and beta did not honor the size option after following a redirect which means that when a content size was over the limit a fetcherror would never get thrown and the process would end without failure for most people this fix will have a little or no impact however if you are relying on node fetch to gate files above a size the impact could be significant for example if you don t double check the size of the data after fetch has completed your js thread could get tied up doing work on a large file dos and or cost you money in computing publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution beta isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree react images glam fbjs isomorphic fetch node fetch isminimumfixversionavailable true minimumfixversion beta isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails node fetch before versions and beta did not honor the size option after following a redirect which means that when a content size was over the limit a fetcherror would never get thrown and the process would end without failure for most people this fix will have a little or no impact however if you are relying on node fetch to gate files above a size the impact could be significant for example if you don double check the size of the data after fetch has completed your js thread could get tied up doing work on a large file dos and or cost you money in computing vulnerabilityurl
| 0
|
80,185
| 7,741,940,523
|
IssuesEvent
|
2018-05-29 07:57:50
|
Geeksltd/GCop
|
https://api.github.com/repos/Geeksltd/GCop
|
closed
|
Remove GCop403
|
Released ready to test
|
It seems like Visual Studio now has this rule built-in, so there is no need for it anymore:
https://github.com/Geeksltd/GCop/blob/master/Rules/GCop403.md
|
1.0
|
Remove GCop403 - It seems like Visual Studio now has this rule built-in, so there is no need for it anymore:
https://github.com/Geeksltd/GCop/blob/master/Rules/GCop403.md
|
test
|
remove it seems like visual studio now has this rule built in so there is no need for it anymore
| 1
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.