Comment 12 for bug 1607814

Revision history for this message
Rabi Mishra (rabi) wrote :

oh! probably between resource.py L1806 and L1807, atomic key is getting updated by metadata update that's why the misleading lock for update error.