You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 21, 2022. It is now read-only.
A lot of mistakes or wrong configs will lead failed running result of a Stack, and currently there is no way to get what happend when user runnint stack, but which is very important to help up improve Stack.
As maintainer team of Stack, we should import a way to help us seek out why user get failed when running Stack,
Solution
We could collect user environment info && error stack || error info, and then send to us. go bug is a good example that we can learn from, The user will make decisition wether to report or not.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Background
A lot of mistakes or wrong configs will lead failed running result of a Stack, and currently there is no way to get what happend when user runnint stack, but which is very important to help up improve Stack.
As maintainer team of Stack, we should import a way to help us seek out why user get failed when running Stack,
Solution
We could collect user environment info && error stack || error info, and then send to us.
go bug
is a good example that we can learn from, The user will make decisition wether to report or not.The text was updated successfully, but these errors were encountered: