C Anthony Risinger
C Anthony Risinger
`--fs-atomic-write` docs suggest > New files will be written to temp file and renamed but `fs.NewFSStorage` (the sole consumer of `cli.args.FSAtomicWrite`) ignores its incoming `atomicWrite` bool.
It looks like this repo isn't too `go install` friendly -- anyway we can resolve that? I was able to remove workarounds and easily go-install nvidia-container-toolkit (and drop nvidia-container-runtime! 😌)...
I'm not sure if this is a bug/feature-request in pesos/compactor, but since it affects how pesos can be deployed, and since docker is a standard Mesos executor, I'm documenting here....
``` Traceback (most recent call last): File "/lib/python2.7/site-packages/tornado/ioloop.py", line 568, in _run_callback ret = callback() File "/lib/python2.7/site-packages/tornado/stack_context.py", line 275, in null_wrapper return fn(*args, **kwargs) File "/lib/python2.7/site-packages/pesos/scheduler.py", line 304, in launch_tasks...
With the current impl, it's not possible to handle signals like `SIGINT` (KeyboardInterrupt) because `join()` calls `self.lock.wait()` with no timeout -- the signal is caught and queued for handling but...
while trying to adapt the Mesos official python example to use pesos instead, I triggered this: ``` Traceback (most recent call last): File "example_framework.py", line 159, in status = 0...
At some point someone complained this hook was outdated and didn't use ondemand this or that. They were probably right. Review.
This is a little bit of a plug, so I'll keep it short! I'm trying to nail down _**exactly** what's going on here_. https://riprompt.com https://riprompt.com/spe-rip.txt https://chatgpt.com/g/g-9H7ASwa9r-recursive-insights-prompt After a long adventure...