-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Check realtime mode in remote clock interceptor #6985
Conversation
Check that the request is using realtime before using the remote-clock start and end timestamps for telemetry requests
Current Playwright Test Results Summary✅ 14 Passing - Run may still be in progress, this comment will be updated as current testing workflow or job completes... (Last updated on 10/03/2023 08:40:29pm UTC) Run DetailsRunning Workflow e2e-couchdb on Github Actions Commit: 4dce3aa Started: 10/03/2023 08:37:32pm UTC
|
Test Case | Last 7 days Failures | Last 7 days Flakes |
---|---|---|
Notebook Tests with CouchDB @couchdb Inspect Notebook Entry Network Requests
Retry 1 • Initial Attempt |
0% (0)0 / 47 runsfailed over last 7 days |
4.26% (2)2 / 47 runsflaked over last 7 days |
Current Playwright Test Results Summary
✅ 141 Passing -
Run may still be in progress, this comment will be updated as current testing workflow or job completes...
(Last updated on 10/03/2023 08:40:29pm UTC)
⚠️ Flakes
📄 functional/plugins/notebook/restrictedNotebook.e2e.spec.js • 2 Flakes
Top 1 Common Error Messages
|
2 Test Cases Affected |
Test Case Results
Test Case | Last 7 days Failures | Last 7 days Flakes |
---|---|---|
Restricted Notebook with a page locked and with an embed @addinit Allows embeds to be deleted if page unlocked @addinit
Retry 1 • Initial Attempt |
7.53% (7)7 / 93 runsfailed over last 7 days |
49.46% (46)46 / 93 runsflaked over last 7 days |
Restricted Notebook with a page locked and with an embed @addinit Disallows embeds to be deleted if page locked @addinit
Retry 1 • Initial Attempt |
0% (0)0 / 85 runsfailed over last 7 days |
43.53% (37)37 / 85 runsflaked over last 7 days |
📄 functional/planning/timelist.e2e.spec.js • 1 Flake
Test Case Results
Test Case | Last 7 days Failures | Last 7 days Flakes |
---|---|---|
Time List Create a Time List, add a single Plan to it and verify all the activities are displayed with no milliseconds
Retry 1 • Initial Attempt |
0% (0)0 / 132 runsfailed over last 7 days |
56.82% (75)75 / 132 runsflaked over last 7 days |
📄 functional/plugins/notebook/notebookSnapshots.e2e.spec.js • 1 Flake
Test Case Results
Test Case | Last 7 days Failures | Last 7 days Flakes |
---|---|---|
Snapshot image tests Can drop an image onto a notebook and create a new entry
Retry 1 • Initial Attempt |
17.35% (17)17 / 98 runsfailed over last 7 days |
55.10% (54)54 / 98 runsflaked over last 7 days |
Codecov Report
@@ Coverage Diff @@
## master #6985 +/- ##
==========================================
- Coverage 57.18% 55.57% -1.62%
==========================================
Files 413 650 +237
Lines 12805 26102 +13297
Branches 0 2549 +2549
==========================================
+ Hits 7323 14506 +7183
- Misses 5482 10895 +5413
- Partials 0 701 +701
*This pull request uses carry forward flags. Click here to find out more.
... and 402 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
remoteClockLoaded = true; | ||
request.start = start; | ||
request.end = end; | ||
const timeContext = request?.timeContext ?? openmct.time; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
❤️
request.end = end; | ||
const timeContext = request?.timeContext ?? openmct.time; | ||
//if we're not in realtime mode, we will use the fixed time bounds provided by the request | ||
if (timeContext.isRealTime()) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be if (!timeContext.isRealTime())
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No. We only want to take the bounds from waitForBounds()
if we're in realtime mode
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we clarify the comment? The way it reads seems confusing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I agree, I think this is good to go after making this comment more clear.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one small change @ozyx pointed out.
request.end = end; | ||
const timeContext = request?.timeContext ?? openmct.time; | ||
//if we're not in realtime mode, we will use the fixed time bounds provided by the request | ||
if (timeContext.isRealTime()) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I agree, I think this is good to go after making this comment more clear.
VIPEROMCT-397 was closed by this PR - akhenry/openmct-yamcs#369. Do we still need this PR? |
Yes we still need this. It was found while I was investigating that bug and you will get incorrect data if you use remote-clock. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Closes VIPEROMCT-397
Describe your changes:
Check that the request is using realtime before using the remote-clock start and end timestamps for telemetry requests
All Submissions:
Author Checklist
Reviewer Checklist