-
Notifications
You must be signed in to change notification settings - Fork 316
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
Link to status page in API error response might be helpful? #3260
Comments
How would this work when bound to a different depot? Private depot doesn't have a nice status page that you can link to. |
@predominant, not sure about that, and since we have private origins now (as of yesterday ;), maybe it's not as important? Also, I think there is still discussion around private 'neighborhood' builders, so maybe until that stuff is finalized it doesn't make sense to worry about responses from a privately-hosted Builder API? |
Agreed @bixu |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you. |
Currently, an error from the API when installing a package gives fairly terse response:
Adding a status url to this response would help user find authoritative information about the upstream depot/neighborhood, for example:
The text was updated successfully, but these errors were encountered: