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

Link to status page in API error response might be helpful? #3260

Open
bixu opened this issue Sep 21, 2017 · 5 comments
Open

Link to status page in API error response might be helpful? #3260

bixu opened this issue Sep 21, 2017 · 5 comments
Labels
Stale Type: Chore Issues for general code and infrastructure maintenance

Comments

@bixu
Copy link
Contributor

bixu commented Sep 21, 2017

Currently, an error from the API when installing a package gives fairly terse response:

» Installing core/<dependency_package> from channel 'stable'
✗✗✗
✗✗✗ [504 Gateway Timeout]
✗✗✗
   <my_package>: WARN No installed packages of 'core/<dependency_package>' were found

Adding a status url to this response would help user find authoritative information about the upstream depot/neighborhood, for example:

» Installing core/<dependency_package> from channel 'stable'
✗✗✗
✗✗✗ [504 Gateway Timeout]
✗✗✗ See http://habitat.statuspage.io
✗✗✗
   <my_package>: WARN No installed packages of 'core/<dependency_package>' were found
@predominant
Copy link
Contributor

How would this work when bound to a different depot? Private depot doesn't have a nice status page that you can link to.

@bixu
Copy link
Contributor Author

bixu commented Oct 10, 2017

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

@predominant
Copy link
Contributor

Agreed @bixu

@stale
Copy link

stale bot commented Apr 3, 2020

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.

@stale stale bot added the Stale label Apr 3, 2020
@christophermaier christophermaier added Type: Chore Issues for general code and infrastructure maintenance and removed C-chore labels Jul 24, 2020
@stale stale bot removed the Stale label Jul 24, 2020
@stale
Copy link

stale bot commented Jul 31, 2022

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.

@stale stale bot added the Stale label Jul 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Stale Type: Chore Issues for general code and infrastructure maintenance
Projects
None yet
Development

No branches or pull requests

5 participants