I would be interested to see the patch regardless. I saw this issue running in container too.
ok, I think I understand where the problem is. Let me make a unit test and fix and you can merge that into this pr?
Basically, you should end up in same situation. A race condition, ie. you add a review trigger that is not seen in timeline, means that the timeline is modified asynchronously after requests…
I think this is correct. The timeline could be behind rawReviews, but those rawReviews that are not on the timeline should be ignored.
It's sadly used. It's a global in the application. It makes sense in the app, but it's confusing here.
Most of the changes here are related to tests. Commits should be reviewed one at a time, as dependency injection accounts for majority of the main.go changes and should be separated from the logic…