Comment 1 for bug 1477910

When listing images, images are returned from the server in batches of, eg, 25.

Currently the v2 client validates the returned image metadata against the image schema for the first image in each batch.

(Originally all images were checked against the schema, but that was found to give poor performance.)

I'm not sure anymore if validating the schema for a subset of images when listing is a good idea.

It can give behaviour such as adding a 'good' image can break image listing if it means that a 'bad' image is now the first in a batch. Basically it can lead to unpredictable behaviour and bugs like this one.

I think removing all schema validation (at least by default) when doing v2 listing may make sense.