Tweak checkpoint data for TutorBotOutput #309
Open
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
mbertrand
force-pushed
the
mb/tutorbout_checkpoint_fix
branch
from
bf10313 to
8f94a77
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What are the relevant tickets?
Related to #301
Description (What does it do?)
Tweaks TutorBotOutput checkpoint data to be more in line with other bot checkpoints
How can this be tested?
TutorBotOutput, theDjangoCheckpoint.checkpointmessage format matches theDjangoCheckpoint.metadatamessages format, and allstepvalues are sequential.TutortBotOutputs, run./manage.py backpopulate_tutor_checkpoints --overwriteand verify the above for allTutorBotOutputs