You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We already have DANDI_TESTS_PERSIST_DOCKER_COMPOSE and let's add DANDI_TESTS_PULL_DOCKER_COMPOSE (or anything else really) which would default to 1 but allow for 0 and then would be used as a bool (or some other way allowing to disable) to disable docker compose pull introduced in #1121 to fix #1120 and which lead to dandi-archive integration testing not using freshly built docker image as discovered in dandi/dandi-archive#1336 (comment) .
The text was updated successfully, but these errors were encountered:
We already have
DANDI_TESTS_PERSIST_DOCKER_COMPOSE
and let's addDANDI_TESTS_PULL_DOCKER_COMPOSE
(or anything else really) which would default to1
but allow for0
and then would be used as a bool (or some other way allowing to disable) to disabledocker compose pull
introduced in #1121 to fix #1120 and which lead to dandi-archive integration testing not using freshly built docker image as discovered in dandi/dandi-archive#1336 (comment) .The text was updated successfully, but these errors were encountered: