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
As per the DeepBookV3 Indexer documentation, the endpoint should return a JSON array containing summary objects for all trading pairs in DeepBook, with each object having the following structure:
The request consistently fails with a 502 Bad Gateway error after approximately 60 seconds of waiting. This makes it impossible to reliably fetch and cache trading pair summaries.
This endpoint is critical for applications that need to display trading pair information. While slow response times could be managed through caching, the consistent 502 errors make it impossible to implement reliable caching strategies. Other DeepBook Indexer endpoints appear to work as expected.
The text was updated successfully, but these errors were encountered:
As per the DeepBookV3 Indexer documentation, the endpoint should return a JSON array containing summary objects for all trading pairs in DeepBook, with each object having the following structure:
The request consistently fails with a 502 Bad Gateway error after approximately 60 seconds of waiting. This makes it impossible to reliably fetch and cache trading pair summaries.
This endpoint is critical for applications that need to display trading pair information. While slow response times could be managed through caching, the consistent 502 errors make it impossible to implement reliable caching strategies. Other DeepBook Indexer endpoints appear to work as expected.
Hey, we're aware of this issue and currently working on improving this endpoint, thanks for flagging
Steps to Reproduce Issue
/summary
endpoint:Expected Result
As per the DeepBookV3 Indexer documentation, the endpoint should return a JSON array containing summary objects for all trading pairs in DeepBook, with each object having the following structure:
Actual Result
The request consistently fails with a 502 Bad Gateway error after approximately 60 seconds of waiting. This makes it impossible to reliably fetch and cache trading pair summaries.
Error details:
System Information
Additional Context
This endpoint is critical for applications that need to display trading pair information. While slow response times could be managed through caching, the consistent 502 errors make it impossible to implement reliable caching strategies. Other DeepBook Indexer endpoints appear to work as expected.
The text was updated successfully, but these errors were encountered: