)]}'
{"web/src/actions/build.js":[{"author":{"_account_id":1,"name":"James E. Blair","email":"jim@acmegating.com","username":"corvus"},"change_message_id":"2b6a43f8dd2e24c959350f653829764cb6ef6f40","unresolved":false,"context_lines":[{"line_number":198,"context_line":"\t\t    .catch(error \u003d\u003e dispatch(failedView(error)))"},{"line_number":199,"context_line":"\t\t//}"},{"line_number":200,"context_line":"\t      }"},{"line_number":201,"context_line":"\t    })"},{"line_number":202,"context_line":"            .catch(error \u003d\u003e console.error("},{"line_number":203,"context_line":"              \u0027Couldn\\\u0027t decode manifest...\u0027, error))"},{"line_number":204,"context_line":"        }"}],"source_content_type":"text/javascript","patch_set":1,"id":"7faddb67_c6eeb7b3","line":201,"updated":"2019-07-22 14:25:06.000000000","message":"Having this in here feels wrong because it\u0027s getting way too complicated for a chain of functions, and it also doesn\u0027t have access to the processed data on the state object which we need.  We could move this out to its own function, but this is all tied to dispatching events to the reducer.  Should we put some logic in the reducer so that once the manifest has arrived, if we\u0027re also looking for a log file, the reducer starts the process to fetch that?","commit_id":"e055d82e68dd5274810e73a885f39986d1315429"}]}