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

The transfer screen should show an error to the user if it occurs in the process #1651

Closed
agatsoh opened this issue Jun 9, 2020 · 1 comment · Fixed by #1655
Closed

The transfer screen should show an error to the user if it occurs in the process #1651

agatsoh opened this issue Jun 9, 2020 · 1 comment · Fixed by #1655
Assignees
Labels
bug 🕷️ Something isn't working

Comments

@agatsoh
Copy link
Contributor

agatsoh commented Jun 9, 2020

Thanks for filing a bug report :-)

Steps to Reproduce

  1. make a mediated transfer
  2. Press continue on the transfer screen here
    transfer_screen

Expected Result

  • Screen should show an error which happens on user action and take him out

Actual Result

  • The spinner keeps spinning without showing any error to the user.
    light_client_pfs_not_available
    light_client_console_error_pfs

Additional Infos (Optional)

- Browser & version
Chrome Version 83.0.4103.97 (Official Build) (64-bit)
- Browser console errors
Screenshots are given above
`type: "path/find/failure", payload: RaidenError: Pathfinding Service is disabled and no direct route is available.`
- Device / OS
Linux mint

raiden_2020-06-09T11_10_08.828Z.log

@christianbrb christianbrb added the bug 🕷️ Something isn't working label Jun 9, 2020
@christianbrb christianbrb added this to the Product Backlog milestone Jun 9, 2020
@christianbrb christianbrb removed this from the Product Backlog milestone Jun 9, 2020
@andrevmatos
Copy link
Contributor

This is not an error. That PFS "failure" action/log is actually just the response to the direct route check, which happens before the actual PFS request. Your issue is actually that the PFS was disabled from VUE_APP_PFS env var missing from my guide and actually being passed as undefined and that disabled the PFS fetching, which made the transfer gets stuck waiting for a PFS to show up.
My PR will fix that by also supporting undefined as pfs auto mode. In the meantime, you can just export VUE_APP_PFS="" on the terminal before serving the dApp, and this will enable PFS again, as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🕷️ Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants