computerquip-work
computerquip-work
I might be mistaken but doesn't the proposed solution require devspace to be installed? I think the intention of the issue is that devspace shouldn't need to be installed in...
After a bit of research, there's already a waitn implementation internally. forx and gang use that which I then realized allows the `-p` argument which means I can run commands...
I'm going to open this back up since I couldn't get this working. I'm not sure if this is an intended use or not. Basically, all I'm doing is this:...
The problem I'm having with `wait { $PID1 $PID2 }` is that I want to exit if either `$PID1` exits or `$PID2` exits, not when both exit.
Just my two cents on the matter: * Currently, asio's notify_fork isn't async-signal-safe which causes undefined behavior. * Setting FD_CLOEXEC via fnctl is impossible without a race condition. At the...
> > At the least, the other UNIX-like systems provided closefrom, close_range, or some fnctl method. Linux developers literally just refused, expecting everyone to set CLOEXEC flags for every single...
Let's say I have a bash script that wants to build an image with `docker build`, take the resulting image id, and then run it. With non-BuildKit, the command `docker...
> Got hit by this today, after enabling BuildKit in an Azure DevOps pipeline, as AzDo fails tasks by default if anything is written to stderr. AzDo's default has never...
> > The whole point is that when meaningful output is possible, you use stderr as a means of human-readable output and stdout as a means for pragmatic output. >...
> Yes, I absolutely agree. The question is, we have the year 2022, why are easy and obvious changes like this not being made? > > EDIT: and of course...