-
Notifications
You must be signed in to change notification settings - Fork 8.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
[Reporting] Fix missing force now behaviour for v2 reports #114516
Merged
jloleysens
merged 4 commits into
elastic:master
from
jloleysens:reporting/fix-use-of-force-now
Oct 12, 2021
Merged
[Reporting] Fix missing force now behaviour for v2 reports #114516
jloleysens
merged 4 commits into
elastic:master
from
jloleysens:reporting/fix-use-of-force-now
Oct 12, 2021
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jloleysens
added
(Deprecated) Feature:Reporting
Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead
v8.0.0
release_note:skip
Skip the PR/issue when compiling release notes
Team:Reporting Services
v7.16.0
labels
Oct 11, 2021
Pinging @elastic/kibana-reporting-services (Team:Reporting Services) |
jloleysens
changed the title
fix missing force now behaviour for v2 reports
Fix missing force now behaviour for v2 reports
Oct 11, 2021
@elasticmachine merge upstream |
jloleysens
changed the title
Fix missing force now behaviour for v2 reports
[Reporting] Fix missing force now behaviour for v2 reports
Oct 12, 2021
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: |
dokmic
approved these changes
Oct 12, 2021
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 👍
jloleysens
added a commit
to jloleysens/kibana
that referenced
this pull request
Oct 12, 2021
…14516) * fix missing force now behaviour for v2 reports * added jest test * updated jest test snapshot to match removal of forceNow injection from locator params Co-authored-by: Kibana Machine <[email protected]>
jloleysens
added a commit
that referenced
this pull request
Oct 12, 2021
…114634) * fix missing force now behaviour for v2 reports * added jest test * updated jest test snapshot to match removal of forceNow injection from locator params Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: Kibana Machine <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
(Deprecated) Feature:Reporting
Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead
release_note:skip
Skip the PR/issue when compiling release notes
v7.16.0
v8.0.0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fix #114193
Adds the
forceNow
parameter to the reporting's redirect app which fixes potential time drift issues.Also removes the
forceNow
parameters from locators.Checklist