Daniel Azuma

@ruliana Feel free to take a shot at implementing this if you're interested.

The `:exec` mixin already logs all commands by default, but at the INFO level (which will not show up by default because the verbosity defaults to WARN). If you pass...

You can change the logger by constructing a new logger with whatever formatter you want, and passing it in the `logger:` keyword argument. However, I admit this is not convenient....

Exec is the only standard mixin that makes heavy use of the logger. But any tool can log: ```ruby tool "foo" do def run logger.info "Hello, world!" logger.warn "This is...

This one is still happening and is still flaky, having failed once in the past three runs as of this writing. The deployment failure error is: ``` ERROR: (gcloud.app.deploy) INVALID_ARGUMENT:...

Seems to be happening consistently now. ``` Failures: 1) Metadata server on Google App Engine displays IP address read from metadata server Failure/Error: visit @url Capybara::Poltergeist::StatusFailError: Request to '' failed...

We also need to move off of the unsupported gcr.io/google-appengine/ruby base image, and onto a usable base image such as one of the official Ruby images from dockerhub.

Yeah I don't have any plans to deprecate `alias_tool`. Not every feature is described in detail in the user's guide, but you're right, it's probably a good idea to mention...

We're now working on updating the base image to 20.04 (#221), and have added `libvips-dev` to it. I just got finished doing general end-to-end testing on the image, and we...

How are you reproducing this error? The current image is based on Ubuntu, not Debian, and should not be using Jessie-related repositories at all.