-
Notifications
You must be signed in to change notification settings - Fork 1.2k
refactor engine tracking and simplify it #3893
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
Conversation
Test Results 313 files 313 suites 53s ⏱️ Results for commit 59195c1. ♻️ This comment has been updated with latest results. |
| // allow instrumentation to tweak the result | ||
| executionResult = executionResult.thenCompose(result -> instrumentation.instrumentExecutionResult(result, instrumentationParameters, instrumentationState)); | ||
| return executionResult; | ||
| return instrumentation.instrumentExecutionResult(abortException.toExecutionResult(), instrumentationParameters, instrumentationState); |
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 that was weird code
bbakerman
left a comment
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.
I approve generally but some code to be cleaned up
This simplifies the engine tracking:
We really only need to take care of CF that are externally contributed to the engine and the sync code in start. This means we don't need most call/run code, but rather need to handle the CF returned by DataFetcher or instrumentation correctly.
Also: this changes the code to have zero impact when no EngineStateObserver is registered.