Javier Palacios

No hurry from my side, as I'm already using it ...

KeycloakAdmin gives me a 401 when using either realm_name or user_realm_name (my admin is in master realm). But you don't need to patch to apply your solution, as you can...

> My histories are always restored properly. Just wondering why this change would make this any better. Maybe if you reorder panes, or delete some but the last one, or...

Not completelly sure whehther is related to this particular issue, but with 1.11.17/3.2.0 for django/django-mysql, I've need to patch following https://jira.mongodb.org/browse/PYMODM-77. With that change, I can successfully run [...].annotate(members=GroupConcat('user_id', output_field=SetCharField(CharField))).[...]...

I wasn't even aware that it was mongodb for django. Just finding matches for the exception I got. I'll fork and submit the changes.

The PR is there (adamchainz/django-mysql#646). It cannot be merged because i started from tag v3.2.0 but you can see changes there. And it is even more funnier. With the original...

I believe that all functional tests succeed, but have no idea neither why the py38-multilint complains nor how to fix that particular error.

Finally !!!! Regarding releasing, I agree with the mayor approach because this is not backwards compatible. In any case we'll make an internal release based on 3.2.0, because we're still...

Not sure if I understand right, but looks like the "commit notification" flag is not project wide but set on a repository level. If that is the case, I'm unsure...

As you suppose, the information sent is enough. I'm not sure about your detailed project setup, but I'm afraid that the point is that the plugin does not currently behaves...