-
Notifications
You must be signed in to change notification settings - Fork 126
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
Function log replay correlation #4087
Conversation
Thanks for your contribution! Depending on what you are working on, you may want to request a review from a Shopify team:
|
We detected some changes at either packages/*/src or packages/cli-kit/assets/cli-ruby/** and there are no updates in the .changeset. |
Coverage report
Show files with reduced coverage 🔻
Test suite run success1715 tests passing in 794 suites. Report generated by 🧪jest coverage report action from 91ad416 |
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.
Overall looks pretty good! Just have a few minor suggestions.
272feb1
to
dbf0741
Compare
0c18220
to
65a8807
Compare
65a8807
to
91ad416
Compare
Going to wait until the log command ships, to avoid introducing any conflicts. |
WHY are these changes introduced?
Fixes https://github.com/Shopify/shopify-functions/issues/245
Makes it easier to go from seeing a function execution in
app dev
, to using it inreplay
.WHAT is this pull request doing?
Adds the log "identifier" to the
app dev
output, to further differentiate each execution:... and provide a string that can be used when searching for logs in
replay
:... or to feed into the new
--log
argument ofreplay
to bypass the manual selection:How to test your changes?
Use
app dev
, then copy the identifier into areplay
execution using the--log
argument.Checklist
dev
ordeploy
have been reflected in the internal flowchart.