Skip to content
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

typo:Log the worker name when starting the task #1837

Merged
merged 1 commit into from Jan 27, 2023

Conversation

bazzargh
Copy link
Contributor

in 7d0b20e the code was refactored to move the startup of workers into the worker class. As part of this, most of the references were changed from 'worker' to 'self'. This also happened to the line logging worker startup, but that line did not move into the worker, so now it just logs "Starting worker main", taking the name main from rake. You can still see the old behaviour in the documentation:

*** Starting worker hostname:90185:default

There was no explanation for this change so it just looks like a typo to me? It came up for us reading logs and trying to understand where the 'Starting worker main' came from, since it didn't match up to the workers we had crashing.

in resque@7d0b20e
the code was refactored to move the startup of workers into the worker class. As part of this,
most of the references were changed from 'worker' to 'self'. This also happened to the line logging worker
startup, but that line did not move into the worker, so now it just logs "Starting worker main", taking the name
main from `rake`. You can still see the old behaviour in the documentation:
https://github.com/resque/resque/blob/7f6b88404dd18698f6f4023e18fdc1ae8318e5e5/examples/demo/README.markdown#L29

There was no explanation for this change so it just looks like a typo to me? It came up for us reading logs and trying
to understand where the 'Starting worker main' came from, since it didn't match up to the workers we had crashing.
@PatrickTulskie
Copy link
Contributor

@bazzargh hey yeah this looks like a good fix to me. Mind rebasing so we can get specs to run with the latest changes and we can tee it up for the next release.

@PatrickTulskie PatrickTulskie merged commit f923e66 into resque:master Jan 27, 2023
@bazzargh bazzargh deleted the patch-1 branch May 5, 2023 08:25
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.

None yet

2 participants