Building on #112 and in conjunction with https://github.com/filecoin-project/autoretrieve-deploy/issues/8, let's make the retrieval events posting api accept an array of events, instead of a single event. Based on the architecture of #112, it should be possible to just make the reportChan on the event recorder an array of reports, and then in the ingestReports go routine just forward the whole array of queued events rather than a single event.
Goal
Building on #112 and in conjunction with https://github.com/filecoin-project/autoretrieve-deploy/issues/8, let's make the retrieval events posting api accept an array of events, instead of a single event. Based on the architecture of #112, it should be possible to just make the
reportChan
on the event recorder an array of reports, and then in the ingestReports go routine just forward the whole array of queued events rather than a single event.We'll need to figure out timing so we can launch this at the same time as https://github.com/filecoin-project/autoretrieve-deploy/issues/8