FIX: Eager execution correctly respects execute method #102
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.
Contents (#102)
IMPORTANT: There is 1 breaking change.
Fixes
Upgrade instructions
💥 Eager execution correctly respects execute method
When using *Task.enqueue() and *Task.enqueue_later() with GCP_TASKS_EAGER_EXECUTE=True, the returned value will now be the status of the task handler response, rather than the calculated result itself. This allows consistent execution between eager and async tasks in cases where the public execute() method of the *Task class has been overridden