-
Notifications
You must be signed in to change notification settings - Fork 8
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
Display payjoin errors within the UI #50
Comments
I think it makes the most sense to keep the errors via Push API (Service Workers), but that requires https so I'm not sure it's going to work in the umbrel environment. Without a service worker, if an error propagates while you're not looking at the web page you're going to miss it unless it's stored on the server until requested. |
Can we use web sockets or worse-case polling? The first thing the webapp does is acquire pj state. |
payjoin receiver errors are sent back to the sender which is done now in #57. to show them in the receiver it sounds like Armin's on the right track |
closed by #93 |
It would be great for UX and testing if we could see errors within the UI.
Usually this would not be so important for testing, since you can just read the logs. However fetching the logs on umbrel is very slow and makes for a bad experience when payjoins are failing.
A user should be able to know immediately if a node rejected a channel for , e.g. too small.
The text was updated successfully, but these errors were encountered: