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

Failing API calls (spotbit.info/api is offline): Update CCXT and improve error handling #105

Open
nochiel opened this issue Sep 20, 2023 · 0 comments
Assignees
Labels
bug Something isn't working spotbit.info API is offline The spotbit.info API will be offline until this issue is resolved.

Comments

@nochiel
Copy link
Contributor

nochiel commented Sep 20, 2023

The https://spotbit.info API is offline.

As noted in #103 (comment), Spotbit is currently crashing because API calls to exchanges are continuously failing.

The result is that either API calls fail immediately or, when attempting to get results for a range of dates, Spotbit keeps trying until it runs out of memory. The system then kills Spotbit. Restarting Spotbit then causes the same error.

We should:

  • Update to the latest CCXT which hopefully reflects whatever changes have occurred with exchange APIs.
  • Improve error handling so that Spotbit immediately stops retrying when unknown errors occur. That is, if an error we don't specifically handle occurs then Spotbit should always fail and report that error instead of attempting other requests.
  • Blacklist failing exchanges and report them for the Spotbit administrator to manually verify the bug.
@nochiel nochiel self-assigned this Sep 20, 2023
@nochiel nochiel added bug Something isn't working spotbit.info API is offline The spotbit.info API will be offline until this issue is resolved. labels Sep 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working spotbit.info API is offline The spotbit.info API will be offline until this issue is resolved.
Projects
Status: 2025 Backlog
Development

No branches or pull requests

1 participant