I just ran into this again, so I'm confirming it as a bug now. Sometimes, our hubot doesn't update the metadata document with the latest date, and so clients relying on that cannot find the latest messages, but show outdated ones, despite the newer message archives existing.
I haven't been able to find the cause yet, so I guess the first step would be to see if we can add more logging, e.g. for RS conflict events.
I just ran into this again, so I'm confirming it as a bug now. Sometimes, our hubot doesn't update the metadata document with the latest date, and so clients relying on that cannot find the latest messages, but show outdated ones, despite the newer message archives existing.
I haven't been able to find the cause yet, so I guess the first step would be to see if we can add more logging, e.g. for RS conflict events.
raucao
added the bug label 2022-02-08 20:54:32 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I just ran into this again, so I'm confirming it as a bug now. Sometimes, our hubot doesn't update the metadata document with the latest date, and so clients relying on that cannot find the latest messages, but show outdated ones, despite the newer message archives existing.
I haven't been able to find the cause yet, so I guess the first step would be to see if we can add more logging, e.g. for RS conflict events.