Skip to content
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

Closed
sidharthachatterjee opened this issue Oct 25, 2019 · 4 comments
Closed

Associate reporter logs with activity #19024

sidharthachatterjee opened this issue Oct 25, 2019 · 4 comments
Labels
stale? Issue that may be closed soon due to the original author not responding any more.

Comments

@sidharthachatterjee
Copy link
Contributor

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 bind log, info, warn functions to the activity instance.

Follow up to #18383

@github-actions
Copy link

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.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

@github-actions github-actions bot added the stale? Issue that may be closed soon due to the original author not responding any more. label Jun 17, 2020
@blainekasten
Copy link
Contributor

@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? 😆

@github-actions github-actions bot removed the stale? Issue that may be closed soon due to the original author not responding any more. label Jun 18, 2020
@github-actions
Copy link

github-actions bot commented Jul 8, 2020

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.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

@github-actions github-actions bot added the stale? Issue that may be closed soon due to the original author not responding any more. label Jul 8, 2020
@github-actions
Copy link

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.
Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m HUMAN_EMOTION_SORRY. Please feel free to reopen this issue or create a new one if you need anything else.
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks again for being part of the Gatsby community! 💪💜

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale? Issue that may be closed soon due to the original author not responding any more.
Projects
None yet
Development

No branches or pull requests

4 participants