Locally runnable server with built-in data caching, providing both tick-level historical and consolidated real-time cryptocurrency market data via HTTP and WebSocket APIs
I got the error:
tardis-dev:machine WebSocket /ws-stream-normalized binance-futures WS connection error: Error: Opening handshake has timed out at ClientRequest. (/usr/local/lib/node_modules/tardis-machine/node_modules/ws/lib/websocket.js:872:7) at ClientRequest.emit (node:events:517:28) at TLSSocket.emitRequestTimeout (node:_http_client:847:9) at Object.onceWrapper (node:events:631:28) at TLSSocket.emit (node:events:517:28) at Socket._onTimeout (node:net:598:8) at listOnTimeout (node:internal/timers:569:17) at process.processTimers (node:internal/timers:512:7)
When the tardis-machine try to reconnect after running properly for few hours, then I have to restart docker completely to be able to reconnect to a websocket stream (apply to any exchange)
I got the error: tardis-dev:machine WebSocket /ws-stream-normalized binance-futures WS connection error: Error: Opening handshake has timed out at ClientRequest. (/usr/local/lib/node_modules/tardis-machine/node_modules/ws/lib/websocket.js:872:7) at ClientRequest.emit (node:events:517:28) at TLSSocket.emitRequestTimeout (node:_http_client:847:9) at Object.onceWrapper (node:events:631:28) at TLSSocket.emit (node:events:517:28) at Socket._onTimeout (node:net:598:8) at listOnTimeout (node:internal/timers:569:17) at process.processTimers (node:internal/timers:512:7)
When the tardis-machine try to reconnect after running properly for few hours, then I have to restart docker completely to be able to reconnect to a websocket stream (apply to any exchange)