-
Notifications
You must be signed in to change notification settings - Fork 18
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
feat: allow to use any configured engine to replay tracking logs #362
Conversation
Thanks for the pull request, @Ian2012! Please note that it may take us up to several weeks or months to complete a review and merge your PR. Feel free to add as much of the following information to the ticket as you can:
All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here. Please let us know once your PR is ready for our review and all tests are green. |
5fd42a5
to
3e724fd
Compare
cb0476d
to
14df49d
Compare
3a21781
to
9d5e704
Compare
Hi @Ian2012! Just checking in to see if this PR is still in progress? |
@mphilbrick211 Yes, once this PR is merged #388 I will take care of updating this PR. |
a0bde69
to
19cfc78
Compare
bd3fc1f
to
7e4e263
Compare
7e4e263
to
e60215a
Compare
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.
Nice, I've been meaning to get back to that for a while. Thanks for knocking it out
@Ian2012 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future. |
Description: This PR uses the already configured backends to replay tracking logs
Merge checklist:
Post merge:
finished.
Author concerns: List any concerns about this PR - inelegant
solutions, hacks, quick-and-dirty implementations, concerns about
migrations, etc.