Skip to content

Conversation

@rosa
Copy link
Member

@rosa rosa commented Aug 24, 2024

Two improvements:

  • Use default configuration when the one given is empty, W¡which happens for example when you have solid queue configuration for an environment but not for others, so you can't find the workers and dispatchers keys.
  • Don't try to start a supervisor on an empty configuration. It leads to weird errors, especially when forking, such as
    Errno::ECHILD when trying to check on the children status without having forked any children.

I want to improve this with a generic configuration validation step, that would check this and other things, and abort/raise if there are any problems, but this will do for now.

Closes #298

rosa added 2 commits August 24, 2024 15:36
Which happens for example when you have solid queue configuration for an
environment but not for others, so you can't find the `workers` and
`dispatchers` keys.
It leads to weird errors, especially when forking, such as
`Errno::ECHILD` when trying to check on the children status without
having forked any children.

I want to improve this with a generic configuration validation step,
that would check this and other things, and abort/raise if there are any
problems, but this will do for now.
@rosa rosa force-pushed the handle-empty-config-better branch from 1bb2084 to 525f04b Compare August 24, 2024 15:32
@rosa rosa merged commit 418f885 into main Aug 24, 2024
@rosa rosa deleted the handle-empty-config-better branch August 24, 2024 18:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Errno::ECHILD: No child processes error when starting SolidQueue with rake solid_queue:start

2 participants