New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] [POC] Awesome runner #178
base: master
Are you sure you want to change the base?
Conversation
66d040b
to
f6c4259
Compare
updates:
|
update:
|
require "concurrent/array" | ||
|
||
module Floe | ||
class AwesomeProcess < Thread |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would have preferred not using a thread per process and not using an AwesomeSpan
centric model.
436600d
to
af7918d
Compare
Checked commits kbrock/floe@0a563b3~...53b4b70 with ruby 2.7.8, rubocop 1.56.3, haml-lint 0.51.0, and yamllint |
depends upon:
Overview
So that begs to ask the question on how to implement a runner that manages its own subprocesses.
Implementation
commits:
Issues
This doesn't work perfectly since
AwesomeSpawn
escapes$VAR
and that makes this pretty useless.But the goal was more focused on the Threads and stuff rather than the actual awesome spawn part.