Hi, Flavio! Could you give more information on how to reproduce the bug?
My first thought was that on some quota violation (image size\locations) the bad location remains in image.locations list, but I've tried to reproduce this behaviour in api tests and everything works as expected.
Hi, Flavio! Could you give more information on how to reproduce the bug?
My first thought was that on some quota violation (image size\locations) the bad location remains in image.locations list, but I've tried to reproduce this behaviour in api tests and everything works as expected.