James Addison

The [`_transaction` fixture](https://github.com/jeancochrane/pytest-flask-sqlalchemy/blob/3a550b6f9f6673f643efe8ca71106469a3289931/pytest_flask_sqlalchemy/fixtures.py#L26) might have something to do with this. I've noticed that removing the `binds` option [here](https://github.com/jeancochrane/pytest-flask-sqlalchemy/blob/3a550b6f9f6673f643efe8ca71106469a3289931/pytest_flask_sqlalchemy/fixtures.py#L37) or removing the no-op stubs for close/rollback methods [here](https://github.com/jeancochrane/pytest-flask-sqlalchemy/blob/3a550b6f9f6673f643efe8ca71106469a3289931/pytest_flask_sqlalchemy/fixtures.py#L45-L47) allow the unit...

(NB: there's also a `sqlalchemy` mailing list thread describing some connection close and rollback behaviour that could be relevant - it's closely related to the changes that introduced this warning...

The linked pull request attempts to address these warnings but only removes them fully for `sqlalchemy` in master (i.e. version `1.4` onwards).

@yobuntu Have you tried adding the `db_session` fixture to the `test_post_chore_should_add_a_chore` test case? Without that fixture, I don't know whether the plugin will wrap your test case in a transaction.

This only seems to be a problem when using `multiple`-select mode _and_ when using option groups (as with `Group 1` and `Group 2` in the example). The cause seems to...

@kevin-brown I was taking a look into this separately, and arrived at the same conclusion that the cache lookups for item data fail, resulting in a missing `data.element` property to...

> See: https://github.com/select2/select2/commit/82585672888eead67610556baa46bd7d7b35fdcf Sorry, ignore this attempt at a fix. I was testing it again using a hand-written `select2` example, and this time it isn't working (the `option` elements do...

This would be an API-breaking change, but another idea could be to reconsider the concept of [`locations`](https://github.com/GIScience/openrouteservice/blob/85f503dd0959a49396657850066b203eaed91d90/openrouteservice/src/main/java/org/heigit/ors/api/requests/isochrones/IsochronesRequest.java#L55-L61) in `IsochroneRequests`. It's nice that the API supports multiple locations, but correlating two...

Just adding a note that I'm interested in this functionality too. While I mostly agree with @issuefiler's desired behaviour (`a` is null, `a=` is an empty string, 'undefined' implies key-not-present,...

It's been a while since I looked at this branch, but I thought I should mention that `container_name` entries have been re-added to the `docker-compose.yml` file in fde4b1a084d182a4fcd01e15a1795e9070ce8946, since that...