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

Browse Source

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

...

This commit is contained in:

jackyu66git

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

parent e04a165d69

commit 2ed6ffc747

5 changed files with 45246 additions and 22 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

exchange-monitor.log.bak

+45004

File diff suppressed because it is too large Load Diff