Enable storing the callback outputs in the persistence storage with the flag #3173
Conversation
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
…tputs in the persistence storage
petar-qb
requested review from
T4rk1n,
alexcjohnson,
emilykl,
gvwilson and
ndrezn
as code owners
14 tasks
gvwilson
added
feature
Contributor
|
cc @T4rk1n |
Member
Contributor
|
Superseded by #3279 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
This PR is similar to #3144. It solves the same issue but with an additional optional callback flag called
enable_persistence.This PR behaves more like a
feature, and the other (original) one (#3144) more like abugfix.Description:
Add enable_persistence that when True enables storing the callback outputs in the persistence storage.