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
Low quality piece of shit #360
Comments
Could you follow suggestions about changelog written here and improve the readme file? |
@mainameiz Wow, that's a very rude issue title. May I suggest you rephrase it? Please realise that maintainers don't owe you anything. If I was the maintainer, I would go out of my way not to help someone if they expressed themselves this way. |
Nice, definitely someone with anger issues. But he probably didn't understand what it meant since he wrote Peace instead of Piece 🤣 |
@mainameiz You need to have a piece of mind |
Ok guys, sorry, I was in rage when I wrote it. |
You could have published that and saved the next person. But I wouldn't expect that from someone with the title you gave. |
😂 Glad that offensive typo was fixed. |
I just started an upgrade from v3 to latest version in my project and can't find anything useful from changelog or readme.
From Changelog
What was broken between v3 and v4? What was changed?
Which parameters are passed to
unique_args
proc/method, just job arguments or worker_class+queue_name+argsHere
unique_args
method acceptsname
,id
andoptions
. What does it mean? Whichname
? Whichid
? Whatoptions
?But when you use
unique_args
in real project, it accepts only one parameter - job arguments.Is it changed between v3 and v4 or not?
unique: true
was removed, but with which mode it must be replaced?The text was updated successfully, but these errors were encountered: