Skip to content

When an operation fails, suggest checking Known Issues #7126

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

Closed
zooba opened this issue Aug 28, 2019 · 2 comments
Closed

When an operation fails, suggest checking Known Issues #7126

zooba opened this issue Aug 28, 2019 · 2 comments
Assignees
Labels
area-testing feature-request Request for new features or functionality needs proposal Need to make some design decisions

Comments

@zooba
Copy link
Member

zooba commented Aug 28, 2019

I'm using the Insiders build of VSC and vscode-python, and some operations are failing because of known issues (most recently this morning, #6990).

As a "naive user", I don't necessarily realise that these are known issues, so I have no idea what the status is.

It would be nice if any failed operation (even if it's my fault, such as misconfigured settings) included a link to a Known Issues page, ideally one that is manually curated to include only the current known issues, rather than forcing me to search through the full issues list (since I may not know the right keywords to find my issue, and will probably fall back on just reporting a new one).

This would help me quickly get a resolution or workaround, or at worst would leave me somewhere with an actionable follow-up.

@zooba zooba added triage-needed Needs assignment to the proper sub-team feature-request Request for new features or functionality labels Aug 28, 2019
@zooba
Copy link
Member Author

zooba commented Aug 28, 2019

To be clear, this can totally be a false positive message (at least in Insiders). "Did you expect this to fail? Check our Known Issues at https:.."

I wouldn't expect it if, say, my test run succeeds with failed tests. But if an error causes us to bail out of the test run completely then I need some way to follow up.

@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Aug 28, 2019
@luabud luabud added needs proposal Need to make some design decisions feature-* and removed needs decision labels Oct 30, 2019
@luabud luabud added area-editor-* User-facing catch-all and removed feature-* labels May 13, 2020
@karrtikr karrtikr added area-testing and removed area-editor-* User-facing catch-all labels Dec 20, 2022
@karrtikr
Copy link

Such an operation would have to a manual one, I think testing (discovery or execution) is one of the only few manual ops we now have. The originally linked issue #6990 is also related to testing.

@eleanorjboyd Do you think there're error prompts or other UIs in testing which could make use of this idea? I can't find any, feel to reopen this in that case.

@karrtikr karrtikr closed this as not planned Won't fix, can't repro, duplicate, stale Dec 20, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 20, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-testing feature-request Request for new features or functionality needs proposal Need to make some design decisions
Projects
None yet
Development

No branches or pull requests

4 participants