persisting parsed messages: ERROR #22P05 unsupported Unicode escape sequence

[placer14]

Describe the bug:

message message/message.go:136  failed to process tipset        {"error": "process tipset: persist: persisting parsed messages: ERROR #22P05 unsupported Unicode escape sequence", "height": 66551}
2020-10-30T20:36:36.459Z        ESC[31mERRORESC[0m      schedule        schedule/scheduler.go:134       task exited with failure        {"task": "MessageProcessor000", "error": "process item: process tipset: persist: persisting parsed messages: ERROR #22P05 unsupported Unicode escape sequence"}
2020-10-30T20:57:18.644Z        ERROR   message message/message.go:136  failed to process tipset        {"error": "process tipset: persist: persisting parsed messages: ERROR #22P05 unsupported Unicode escape sequence", "height": 44811}
2020-10-30T20:57:18.647Z        ERROR   schedule        schedule/scheduler.go:134       task exited with failure        {"task": "MessageProcessor000", "error": "process item: process tipset: persist: persisting parsed messages: ERROR #22P05 unsupported Unicode escape sequence"}
2020-10-30T20:57:18.647Z        INFO    schedule        schedule/scheduler.go:120       restarting task {"task": "MessageProcessor000", "delay": 60}
2020-10-30T20:58:35.583Z        ERROR   message message/message.go:136  failed to process tipset        {"error": "process tipset: persist: persisting parsed messages: ERROR #22P05 unsupported Unicode escape sequence", "height": 43794}
2020-10-30T20:58:35.586Z        ERROR   schedule        schedule/scheduler.go:134       task exited with failure        {"task": "MessageProcessor000", "error": "process item: process tipset: persist: persisting parsed messages: ERROR #22P05 unsupported Unicode escape sequence"}
2020-10-30T20:58:35.586Z        INFO    schedule        schedule/scheduler.go:120       restarting task {"task": "MessageProcessor000", "delay": 60}

Postgres can support unicode characters just fine, with the exception of the null character \\u0000. Need to identify the message which causes this and confirm it is a NULL character. If it is a NULL character, it would ideal if we could sanitize it for analysis before insert. If it isn't a NULL, would like to know what it is so we can see about supporting it in the DB schema.

Steps to Reproduce:

• Processing tipset messages with --dmp=true

Visor Version: v0.2.0+56-g360ce23 (sha not published, derived from master merged onto mg/optimzed-lease)

[willscott]

yep. this can indeed happen

[willscott]

Should get confirmation if #185 is sufficient to fix this

[frrist]

Considered resolved as we haven't hit this recently, will reopen new issue in the event that this occurs again.