Sean P. Kane

Are there any updates on the status of this work? What are the next steps that are needed? @mastercactapus @maaslalani

> @spkane I updated and resolved the conflicts, the main remaining issue is that there's no good way to have a command return an error (i.e., other than panic), which...

@CryoByte33 I ran into this error as well. I _worked around it_ it by running `sudo mkdir -p /root/.cryo_utilities/` once. Using `sudo -E` is another option until there is a...

I initially was using ```yaml - name: Detect Pull Request uses: jwalton/gh-find-current-pr@v1 id: findPr with: state: closed ``` But that did not work any differently.

So, in my use case it turns out that simply using: ```yaml env: PR_NUM: ${{ github.event.pull_request.number }} ``` instead of this action works as expected.

I got something very similar using postgresql: Running migrations for djangopypi: - Migrating forwards to 0005_allow_null_distribution_uploader. > djangopypi:0001_initial > djangopypi:0002_refactoring FATAL ERROR - The following SQL query failed: ALTER TABLE...

ALTER TABLE djangopypi_release ADD COLUMN package_id varchar(255) NOT NULL; seems to work whereas: ALTER TABLE "djangopypi_release" ADD COLUMN "package_id" varchar(255) NOT NULL DEFAULT None; does not

@thaJeztah It would be really useful to start with "simply" making the default dark blue that is used by buildkit output, configurable via the docker client config and CLI. It...

This being the post I am talking about: https://coreos.com/blog/coreos-and-xhyve-tech-preview/

Is the **markdown-it** issue also causing the **DeprecationWarning** for `fs.Stats constructor`?