jan
jan copied to clipboard
feat: trouble shooting in-app
Problem
Problem #1 Something's amiss error or failed to fetch error
Problem #2 From @tikikun As hard as we try, there will always be issues with inference service in the tiniest edge case (some time upstream repo has memory leak issue or some low level issue we might not know) and the inference service will crash in the background. We will try the hardest to avoid this situation but giving user a choice to restart this process is needed to avoid them having to resort to quitting the app. Suggestion from Alan: A red button to restart inference service will be useful for these edge cases. ex: "Restart Inference Extension"
Solution
Standardize trouble shooting in-app for automatic trouble-shooting, let users report their problem directly & we can collect logs, clearer data for bugs
Design
Figma link: https://www.figma.com/file/ytn1nRZ17FUmJHTlhmZB9f/Jan-App?type=design&node-id=2684-175159&mode=design&t=bQyiFG80Dcr1XlBm-4
Preview
needs info
Users to send issues:
- Send logs (app, API, nitro)
- Custom message
Notify:
- Dont collect user's info etc
App pod approved.