-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
Associate reporter logs with activity #19024
Comments
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here. Thanks for being a part of the Gatsby community! 💪💜 |
@sidharthachatterjee anything you want to add here? should we mark not stale? Or is this sort of not a priority and we could just let this silently go away? 😆 |
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here. Thanks for being a part of the Gatsby community! 💪💜 |
Hey again! It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it. Thanks again for being part of the Gatsby community! 💪💜 |
Some logs (ones that are output in plugin code for instance) occur within an activity. We should associate these logs with the activity so that we're able to group (or filter) these in the CLI
We should be able to do this by setting an activityId on every log.
The best place to do this is likely in
runAPI
where we can bindlog
,info
,warn
functions to the activity instance.Follow up to #18383
The text was updated successfully, but these errors were encountered: