You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It can take a significant amount of time (about a minute) for a synced server to get complete ledgers.
When using rippled, clients should generally wait for complete_ledgers to be non-empty before proceeding with RPC calls/queries. This should be clarified in the docs.
This issue is for the potential fix of making a change to the definition of server_state: full. This change would be to not report full until complete_ledgers is non-empty. This would prevent some edge cases that result in unintuitive behavior for clients.
It can take a significant amount of time (about a minute) for a synced server to get complete ledgers.
When using
rippled
, clients should generally wait forcomplete_ledgers
to be non-empty before proceeding with RPC calls/queries. This should be clarified in the docs.This issue is for the potential fix of making a change to the definition of server_state: full. This change would be to not report
full
untilcomplete_ledgers
is non-empty. This would prevent some edge cases that result in unintuitive behavior for clients.Originally posted by @intelliot in #4913 (comment)
The text was updated successfully, but these errors were encountered: