jackyu66git 2ed6ffc747 fix: Bitget WS keepalive — send text ping, not WebSocket PingMessage ...

Bitget v2 WS requires a text message "ping" every 30s, not a WebSocket
PingMessage control frame (opcode 0x9). Using the wrong ping type caused
a silent failure: connection stays up and subscription succeeds, but NO
ticker data is pushed — zero errors, zero reconnection logs.

Changes:
- connector.go: Add TextPing bool flag, send text 'ping' when set
- bitget.go: Set TextPing=true, handle text 'pong', add debug logging
- scanner.go: Expand to 179 overlapping Bitget+HL coins

2026-05-04 00:33:03 +08:00

..

binance.go

Initial commit

2026-05-03 16:54:36 +08:00

bitget_trade.go

Fix 8 bugs from code review

2026-05-03 17:48:06 +08:00

bitget.go

fix: Bitget WS keepalive — send text ping, not WebSocket PingMessage

2026-05-04 00:33:03 +08:00

connector.go

fix: Bitget WS keepalive — send text ping, not WebSocket PingMessage

2026-05-04 00:33:03 +08:00

dydx.go

Fix 8 bugs from code review

2026-05-03 17:48:06 +08:00

helpers.go

fix: data race, scale-in PnL, nonce mutex, dead code, hourly check

2026-05-03 18:31:14 +08:00

hyperliquid_trade.go

fix: 4 bugfixes for production readiness

2026-05-03 23:13:44 +08:00

hyperliquid.go

Initial commit

2026-05-03 16:54:36 +08:00

ping.go

Initial commit

2026-05-03 16:54:36 +08:00