Chris Evich

After a week of using a token generated at runtime by a dedicated/private Github App, I've observed no new occurrences of this issue.

Excellent, thanks for the report @pbatard

I must admit I'm tempted to, I'm simply afraid I may not be able to get to it soon-ish. I'll put it on my TODO list, but if anybody else...

Update: Don't bother trying to reference any of these build args in podman or buildah. Tested with podman 4.9.4 and 5.1.1, neither work. Example `Containerfile`: ```Containerfile FROM registry.fedoraproject.org/fedora-minimal:latest ENV TARGETPLATFORM=${TARGETPLATFORM}...

> I would say this should just be documented better. I would be okay with that. The confusing parsing caught at least one user off-guard - meaning, there are probably...

Oh! That's wrong, there should always be a "latest" tag there. Checking podman and buildah, it's the same deal. Something is wrong. I'll look into it.

Idea re: workaround non-ephemeral `$HOME` (or `$TEMPDIR`): Would it make sense to somehow apply an 'expiration date/time' to the files? Another idea: Somehow systemd/journald know when the system has been...

Right...so maybe having potentially "stale" runtime things persist on disk is something we need to live with? In my mind, having the library check if the system has rebooted upon...

> any risks to using it? That filesystem is intended for coordinating share-memory access between processes. So security risks are mostly bound by standard unix file-access permissions. However, using it...

> mostly bound by Clarification: When this filesystem is used as intended...both parties to the shared memory file have it's name pre-defined in some way. So as long as we...