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

[BUG] An unknown error is displayed when the user try to create a peer with no assets created #3046

Open
Emanuel-Palestino opened this issue Oct 25, 2024 · 0 comments · May be fixed by #3095
Assignees
Labels
good first issue Good for newcomers type: bug Something isn't working

Comments

@Emanuel-Palestino
Copy link
Contributor

Bug Report

Describe the bug

Using a clean installation of Rafiki (no wallets, no peers, no assets). The user get an unknown error (internal server error) when it tries to create a new peer with no peers in Rafiki.

To Reproduce

  1. Use a clean Rafiki instance.
  2. Go to peers page
  3. Click on 'create peer'
  4. You got the error

Expected behavior

Rafiki should say to the user that an asset should be created before to create a peer.
Or maybe would be better to allow the user to create a new peer and automatically create a new asset.

Desktop (please complete the following information):

Rafiki version: v1.0.0-alpha.20

Screenshots

@Emanuel-Palestino Emanuel-Palestino added the type: bug Something isn't working label Oct 25, 2024
@github-project-automation github-project-automation bot moved this to Backlog in Rafiki Oct 25, 2024
@mkurapov mkurapov added the good first issue Good for newcomers label Oct 29, 2024
@oana-lolea oana-lolea self-assigned this Oct 29, 2024
@oana-lolea oana-lolea moved this from Todo to In Progress in Rafiki Oct 29, 2024
@oana-lolea oana-lolea moved this from In Progress to Ready for Review in Rafiki Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers type: bug Something isn't working
Projects
Status: Ready for Review
Development

Successfully merging a pull request may close this issue.

3 participants