-
Notifications
You must be signed in to change notification settings - Fork 2.8k
[ZEPPELIN-6600] Refresh the cron scheduler only when the expression changes #5442
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
Open
renechoi
wants to merge
1
commit into
apache:master
Choose a base branch
from
renechoi:ZEPPELIN-6600
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+53
−10
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
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.
The fix itself checks out. Reverting only the production change and running this test leaves exactly one failure, at line 503, so the regression test lands on the right spot.
That one assertion, though, passes under broader conditions than intended.
updateNotehas several exits before it reachesisCronUpdated(line 978): a failedcheckPermission(914-917), a missing note (922), invalid settings while cron is disabled (941), and the three cron execution permission checks (953, 959, 965). None of them throw. They callcallback.onFailureand return quietly, and none of them callrefreshCron, so they all satisfy thisnever(). In other words, the assertion holds just as well when the update fails outright.I reproduced it. Passing a copy with
cronExecutingUserset to"wrong_user"at this step only makesupdateNotebail at line 959 without ever reaching 978, and the test still goes green. The code this PR fixes never runs, and the build still succeeds. (Mutating the sharedconfigmap itself breaks steps 3 and 4 as well, so the sabotage has to stay local to this step for the hole to show.)Steps 1, 3 and 4 are fine.
schedulerService.refreshCronis called from a single place, line 985, which sits below 978, so the call itself proves execution got past the decision point.never()is the only assertion that needs a companion proving it got there.callback.onSuccessat line 982 sits betweenisCronUpdatedandrefreshCron, which makes it a good companion:reset(callback)is needed as well, sincecallbackis a field mock that already recordedonSuccessfromcreateNoteand from step 1. I checked that this combination fails under the sabotage above and passes on the current code.testNoteUpdatein the same file follows the same shape, resettingcallbackper step and verifyingonSuccess.Not a merge blocker, just a suggestion to make the regression test a bit sturdier.