2.2.5 release api-1.1 500 errors

[Daniel Axtens]

Hi Konstantin,

Thanks for your bug reports. Fixes to both for upstream are on the
list. Fixes for the first (v1.1 errors) should apply directly to
stable/2.2; the second one will require a minor backport.

It's now very late so I'm going to leave this for now. Stephen feel free
to take the wheel, take the patches for a spin and apply them and cut a
new release if you feel like it. Otherwise I'll do it next week. If
you've got better ideas for how to do the fixes I'd also be very open to
that!

Kind regards,
Daniel


> Hello:
>
> After the 2.2.2->2.2.5 upgrade, we seem to be getting lots of /api/1.1/ errors
> for PATCH calls:
>
>     PATCH /api/1.1/patches/{id}/
>
> switching to /api/1.2/ seems to fix it, but requires other client app fixes
> for API incompatibility.
>
> Some of the others returning 500 errors are:
>
>     GET /api/patches/{msgid}/comments/ 
>
> I'd be happy to provide tracebacks if I can figure out how to get them.
>
> -K
> _______________________________________________
> Patchwork mailing list
> Patchwork at lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/patchwork