Jonatan Heyman

It seems like USER is a reserved environment variable in phusion/baseimage. See https://github.com/phusion/baseimage-docker/blob/master/image/bin/my_init#L81 and https://github.com/phusion/baseimage-docker/commit/18a7fe26ec13235db66e37e9c0f3ca24bc0116ed I had the same problem, and modified the first line in `first_run.sh` to: `USER=${DB_USER:-super}`, and...

@github-actions not stale, still awaiting response from maintainer I think

I was thinking about the second scenario. It probably has to be something you can turn on/off for a check, since you still want to support checks for jobs that...

The minimum time between runs could either be defaulted to 0s, in which case it wouldn't solve scenario 1. Or, it could be defaulted to something like 75% of Period,...

I'm also interested in this, and would greatly appreciate any pointers on where to start.

I'm also interested in this. Were you able to get open-elevation to work with the 30m data? Also, does anyone know what the disk size requirements would be for the...

I'm interested in this as well (the ultimate goal for me is also to achieve full zero downtime deployments).

Haven't used cx_Oracle myself, but this might be what you're looking for: https://github.com/oracle/python-cx_Oracle/issues/126

Yes, this sounds like a good idea. You should also be able to choose if new blocks should have auto detection turned on or off.

Auto-detection *is* detecting on the fly, but for performance reasons, it's not done on every single keystroke. Instead, the auto-detection only runs when a significant portion of the block has...