I noticed a weird thing not previously observed: if accepting an iRODS data request fails due to the project being locked, we first get an OK status before ending up with FAILED. That is obviously wrong. There must be something wrong with the timeline event update logic, I'll look into it.
This may be caused by a user rapidly accepting multiple requests in the UI instead of using the batch accept feature. That's just a guess though.
We should also improve the whole project locking feature and its visibility in the UI, but that's another story (see e.g. #1512)
I noticed a weird thing not previously observed: if accepting an iRODS data request fails due to the project being locked, we first get an
OKstatus before ending up withFAILED. That is obviously wrong. There must be something wrong with the timeline event update logic, I'll look into it.This may be caused by a user rapidly accepting multiple requests in the UI instead of using the batch accept feature. That's just a guess though.
We should also improve the whole project locking feature and its visibility in the UI, but that's another story (see e.g. #1512)
Screenshot of this below.