Self variable - Issue #55 #60
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi, @danielmichalichyn! A little request, it would be better if there are some use cases or descriptions to show how to use it with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello @actumn, how are you?
Description
Regarding the issue #55, I've created this PR to suggest to you a simple way to achieve the result mentioned in the issue. A "self" variable within the task, so we can have information about task ID, and some other configurations made in the Celery Client. With this we can, from the worker, implement some others functions, like log the task ID, retry a task, and so on...
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Adding a SELF variable to the task function.
**What is the current behavior? ** (You can also link to an open issue here)
Equivalent of "SELF" within the task in Celery-Node Workers #55
I'm open to suggestion and we can discuss if this is the better way.