-
Notifications
You must be signed in to change notification settings - Fork 23
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
feat: job employer #152
Labels
enhancement
New feature or request
Comments
TorchedSammy
added a commit
that referenced
this issue
May 13, 2022
this is mainly to accomodate for the employer handler (#152)
i don't think this function/handler in specific will provide any practical use, #154 is kinda similar to the initial idea i had but actually makes sense |
TorchedSammy
added a commit
that referenced
this issue
May 22, 2022
* feat: add hilbish.job.add function this is mainly to accomodate for the employer handler (#152) * feat!: add start function to jobs the commit itself adds a few things but the main purpose is to facilitate a lua side start function that can restart the job there is a breaking change in the hilbish.job.add function; it is now required to provide an extra table for arguments, since the first cmd table isnt really what's actually ran * fix: reuse standard files for jobs * fix: deadlock in lua job add function and not taking proper amount of args * fix: assign binary path to job * feat: emit job.add hook when job is added * chore: update modules * fix: use setpgid on cmd procattr for background jobs * fix: use right procattr on correct os * fix: set bg proc attr in build tagged file * feat: add disown function * fix: stop jobs on exit * feat: add disown command * feat: add jobs.last function to get last job * feat: make disown command get last job if id isnt suppied as arg * chore: remove unused code * feat: add job output * chore: fix comments * fix!: make exec path in job add explicit in lua side * docs: add docs and changelogs relating to jobs
this should maybe be revisited to allow a custom job handler when using an alternative runner mode |
this would be more involved that just adding a single handler to spawn jobs, so ill revisit and it wont be in 2.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
this would just be a specific handler for interactive jobs. it'll start new jobs and do whatever with them
use would be overwriting the
hilbish.job.employer
functionThe text was updated successfully, but these errors were encountered: