synctv/.sqlx/query-5c5bcf45557b2582901e2...

{
  "db_name": "PostgreSQL",
  "query": "UPDATE email_outbox SET next_attempt_at = NOW() WHERE id = 'retry-budget'",
  "describe": {
    "columns": [],
    "parameters": {
      "Left": []
    },
    "nullable": []
  },
  "hash": "5c5bcf45557b2582901e2c2907ff611d1ce6cc7b8e14aaa9113da5a17a762e06"
}
fix: harden Bilibili playback reliability (#412) ## Summary - Treat explicit null collection fields in Bilibili VOD playback responses as empty collections. - Cover DASH streams, backup URLs, Dolby audio, supported formats, DURL responses, subtitles, video pages, UGC collections, and PGC episodes. - Resolve Bilibili DASH resources from versioned playback metadata and provide every equivalent CDN URL to the existing candidate executor. - Prefer the URL selected by the player, then retry primary and backup CDNs before committing the downstream response. ## Root cause Bilibili occasionally emits explicit null for fields normally represented as JSON arrays, which caused playback/start deserialization errors. Proxy DASH resource requests also used a single CDN even though the provider response included backup URLs. ## Validation - cargo fmt --all -- --check - cargo check for synctv-api-common, synctv-api-http, and synctv-api-grpc - synctv-media-providers Bilibili tests: 91 passed - synctv-core Bilibili tests: 17 passed, 2 ignored - candidate executor tests: 2 passed - Real playback/start, proxy MPD, Range request, CDN fault injection, dev build, and dev smoke checks 1 month ago			`{`
			`"db_name": "PostgreSQL",`
			`"query": "UPDATE email_outbox SET next_attempt_at = NOW() WHERE id = 'retry-budget'",`
			`"describe": {`
			`"columns": [],`
			`"parameters": {`
			`"Left": []`
			`},`
			`"nullable": []`
			`},`
			`"hash": "5c5bcf45557b2582901e2c2907ff611d1ce6cc7b8e14aaa9113da5a17a762e06"`
			`}`