Progress RPC requests fail with "cannot load field "Analyzers" into "track.WorkflowRun". |
||
Issue description
Example log errors:
progress failed: failed to get WorkflowRun: gae: cannot load field "Analyzers" into a "track.WorkflowRun": no such struct field (and 2 other errors), run ID: 5431575093182464 :: {"error":"failed to get WorkflowRun: gae: cannot load field \"Analyzers\" into a \"track.WorkflowRun\": no such struct field (and 2 other errors)"}
progress failed: failed to get WorkflowRun: gae: cannot load field "Analyzers" into a "track.WorkflowRun": no such struct field (and 2 other errors), run ID: 5138801131257856 :: {"error":"failed to get WorkflowRun: gae: cannot load field \"Analyzers\" into a \"track.WorkflowRun\": no such struct field (and 2 other errors)"}
,
Jan 23 2018
Right. One unexpected thing though is that new runs after the field name change are also affected. For example, the newly-created https://chromium-review.googlesource.com/c/playground/gerrit-tricium/+/881643 has run ID 4844312940511232, and the WorkflowRun entity for that run, which should be newly-created, has a property Analyzers but no property Functions. As an experiment, I temporarily deployed a tainted version with the property `Analyzers` added back to the WorkflowRun struct, and the result was: no error, but empty function progress returned.
,
Jan 23 2018
Mystery solved: I had used the web UI to change to a new version, but hadn't changed all modules to the new version. After switching all to the new version, progress display works on new issues again: https://chromium-review.googlesource.com/c/playground/gerrit-tricium/+/881643 |
||
►
Sign in to add a comment |
||
Comment 1 by emso@chromium.org
, Jan 23 2018