Webhook is sent for issue update event even though updated_at is in the past
Summary
Our triage-ops
service receives webhook events from gitlab-org
and gitlab-com
for various events, including issue update.
We receive issue.update
events for issues that have an updated_at
attribute in the past.
For instance, the service received a webhook event for https://gitlab.com/gitlab-org/build/CNG/-/issues/513 today 2024-06-20
but the updated_at
of the issue is currently 2024-06-02T03:05:32.324Z
, based on https://gitlab.com/api/v4/projects/4359271/issues/513.
- Could it be related to the fact that the issue is confidential?
- Maybe the problem is that
updated_at
is not updated in certain cases (there's also no system note hinting that there was an actual update to the issue, and thechanges
attribute of the webhook event is also empty)?
Steps to reproduce
It's hard to reproduce as you have to set up a webhook receiver, but I can come up with a lot of examples.
Example Project
This happens for several projects under gitlab-org
(we receive all webhook events from this group).
What is the current bug behavior?
Webhook events are sent for issue updates that are in the past.
What is the expected correct behavior?
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)