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

Change _Submit Debug Logs_ dialog not to require GitHub issue #28394

Open
grinapo opened this issue Nov 6, 2024 · 7 comments
Open

Change _Submit Debug Logs_ dialog not to require GitHub issue #28394

grinapo opened this issue Nov 6, 2024 · 7 comments

Comments

@grinapo
Copy link

grinapo commented Nov 6, 2024

Description

Right now Submit Debug Logs contain only this:

Before submitting logs, you must create a GitHub issue to describe your problem.

According to @richvdh the text should read something like that:

If you want us to be able to respond or ask for more details you should create a GitHub issue to describe your problem before submitting logs. Otherwise you can just send the logs without filling the "Issue" field, but try to provide as much details in the "Notes" as possible.

Outcome

Inexperienced users cannot simply report UTD problems, for example, while they are really suggested to do so.

@t3chguy
Copy link
Member

t3chguy commented Nov 6, 2024

We don't look through rageshakes unless they are linked to a github issue we are triaging, so you can send them, but unless one of the devs asked you to, they won't be looked at so might as well be going into the abyss. Not changing this as it is as designed.

@t3chguy t3chguy closed this as not planned Won't fix, can't repro, duplicate, stale Nov 6, 2024
@grinapo
Copy link
Author

grinapo commented Nov 6, 2024

It's been fun to be a messenger between you, guys. Keep on the good work!

@richvdh
Copy link
Member

richvdh commented Nov 6, 2024

According to @richvdh the text should read something like that:

If you want us to be able to respond or ask for more details you should create a GitHub issue to describe your problem before submitting logs. Otherwise you can just send the logs without filling the "Issue" field, but try to provide as much details in the "Notes" as possible.

This is not a direct quote, to be clear.

@richvdh
Copy link
Member

richvdh commented Nov 6, 2024

We don't look through rageshakes unless they are linked to a github issue we are triaging,

I don't agree. Plenty of rageshakes do get looked at; in particular they are an extremely valuable resource for investigating and triaging sources of UTD errors.

My experience is that people are deterred from submitting debug reports due to this text. I agree that it's time for this text to be reconsidered.

@richvdh richvdh reopened this Nov 6, 2024
@t3chguy
Copy link
Member

t3chguy commented Nov 6, 2024

I have been told by Product & my manager to not spend any further time on investigating rageshakes unless they concern an issue we are looking at since at least 12 months ago. It used to be part of the triage rota but no longer. So whilst some other teams might periodically look at them, there is zero guarantee that the rageshake is not going into the abyss, especially when it doesn't concern the failure mode that team is interested in (e.g. UTDs in this case)

@richvdh
Copy link
Member

richvdh commented Nov 6, 2024

no disagreement with that. Just hoping we can reword the dialog to be slightly less off-putting. Let's discuss in tomorrow's call.

@t3chguy
Copy link
Member

t3chguy commented Nov 6, 2024

The dialog as it stands was implemented to match designs, this isn't something we should be going behind their back on

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants