>> > 2. This tracker issue doesn't mention invalid Blob ID. The failure
>> > mentioned... how does it present itself if it is not invalid BLOB ID?
>>
>> IIRC, some people have "invalid blob id" error before this was
>> fixed.
>>
>
> I think that we had the error the cause was left as unidentified. So we
> cannot say for sure if we are speaking about the same issue or a different
> one.

I never said it *is* your case.

> I was defintely getting invalid blob ID exception then I changed to ASCII
> (away from NONE) and the exception is gone.

But my idea was helpful to you, isn't is ?

> It's quite reproducible moving from 2.1.2 to 2.1.3

Then create reproducible test case and register it in the tracker.

Regards,
Vlad