Fabien Boucher

Hi, thanks you to have confirmed this. We can just keep that issue for us to investigate the fact that the crawler stop when a no longer existing is still...

It seems that a workaround solution could be to set `export DOCKER_DEFAULT_PLATFORM=linux/amd64` to add a layer of emulation for Docker.

Unfortunately I don't have such platform to test it. Perhaps you could share the error you get ? The other solution might be the full virtualization where you could start...

It seems that, regarding the GitHub crawler: - CONVERT_TO_DRAFT event: https://docs.github.com/en/graphql/reference/objects#converttodraftevent - READY_FOR_REVIEW event: https://docs.github.com/en/graphql/reference/objects#readyforreviewevent could be handled to set a `ready_at` field. Then we could leverage that field when...

Hi, the duration field is optional and according to the code only merged or closed PRs got the duration field. https://github.com/change-metrics/monocle/blob/master/src/Lentille/GitHub/Utils.hs#L183

Yes when the PR is merged or closed then the duration is added to the Change object and related Event objects.

Yes we could set the duration for not merged/closed Changes however the duration won't be accurate most of the time if the Change is not merged or closed. That sounds...

The `duration` on the `Event` object is the same as the `duration` on a `Change` object. Perhaps what you would like is a two new fields: - delay_for_first_comment - delay_for_first_review...

Hi, thanks for the feedback There no plan to change the way the OIDC Client ID is passed to Monocle, however if you'd like to propose a change to add...

Hi, Monocle fetches assignees info for each PRs, however the query language does not provide a way to use that information to filter search results. I might be wrong be...