Dave Myron
Dave Myron
Would it make sense to create a LockFailure (or LockGrantFailure) that extends from MongoError or DoNotDisconnect? Where and what mechanism would retry things? Would it be the Moped::Failover::Retry strategy? Or...
Same issue on macOS Mojave.
This still applies to 1.5.1 _except_ for the usage of the clipboard data. Useful defaults would be a boon.
@artf Is your comment still true? Does adding `overflow: auto` (especially in a "designer mode" / "absolute mode" canvas) still cause problems?
@ndeloof I don't see how one can argue that `-e` should _not_ apply to `up` and simultaneously support that an environment _file_ should. An .env file that contains `FOO=test` is...
It's inconsistent as is. Either remove support for env files (no… don't really…) or support `-e` for `docker compose up`. I, for one, certainly expected `-e` to work to override...
> An .env file that contains FOO=test _can_ be used within compose.yaml for interpolation _or_ to be propagated in container's environment if the definition includes `environment: FOO`, otherwise it has...
> This would then be very confusing : What would you expect `docker compose -e FOO=BAR run -e FOO=BAZ service` to do? Seems straight forward to go with the last...
> variables in shell environment and `.env` file are used for interpolation in compose.yaml, they not **NOT** impact the container environment until you have explicitly configured your compose.yaml definition with...
@antagon: The 1.4 branch compiles and appears to work. Thanks!