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.

Sign up for GitHub

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

Jump to bottom

Add notice that API is not accessible during initialization #4734

Closed
NoahMaizels opened this issue Jul 24, 2024 · 2 comments · Fixed by #4869
Closed

Add notice that API is not accessible during initialization #4734

NoahMaizels opened this issue Jul 24, 2024 · 2 comments · Fixed by #4869
Assignees
@gacevicljubisa
Labels
good first issue Good for newcomers

Comments

@NoahMaizels
Copy link
Contributor

Summary

Currently when a new node is initialized, while syncing batch data, the Bee API is not accessible. However, there is no message returned from the API stating that the node is syncing batch data, it simply appears that the API endpoint is not working properly. It would be good if a descriptive message is returned instead that states the node is currently syncing batch data, so that it's clear there is no malfunction. The message could be something like "Currently syncing batch data, API is not available while syncing. Try again in a few minutes."

Motivation

Make the user experience easier.
@darkobas2 darkobas2 mentioned this issue Aug 1, 2024
Open
@martinconic martinconic self-assigned this Aug 7, 2024
@nugaon
Copy link
Member

nugaon commented Sep 2, 2024

would be better to give back another response for requests than 404. it is more like a 503.

@NoahMaizels NoahMaizels changed the title Add notice while syncing batch data Add notice that API is not accessible during initialization Sep 20, 2024
@NoahMaizels
Copy link
Contributor Author

would be better to give back another response for requests than 404. it is more like a 503.

I think that whatever the response is, it needs to indicate whether the API is not available since the node is in the process of starting up, or whether it is not available due to some other reason / error

@istae istae added the good first issue Good for newcomers label Oct 16, 2024
@gacevicljubisa gacevicljubisa linked a pull request Oct 22, 2024 that will close this issue
fix(api): add api initialization notice #4869
Merged
4 tasks
@gacevicljubisa gacevicljubisa mentioned this issue Oct 22, 2024
Merged
4 tasks
@martinconic martinconic mentioned this issue Nov 29, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gacevicljubisa gacevicljubisa

Labels
good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(api): add api initialization notice ethersphere/bee
5 participants
@martinconic @istae @NoahMaizels @gacevicljubisa @nugaon