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
Documentation - specify that worker must import function in the same way as when it was inserted #37
Labels
documentation
Adds or modifies documentation.
Comments
This is a great point. I'll add something to the README. I'm sure this has
been confusing many people who tried it but didn't post an issue.
…On Tue, Sep 14, 2021, 5:38 PM emjoyce ***@***.***> wrote:
It may be helpful someone in the future to specify that functions must be
imported in the same way for the worker and for insertion (readme or a
special error message).
I had a function from a module of mine that I copied into a notebook to
troubleshoot and edit. I added the queueable decorator right there in the
notebook and used that function for my task insertion. I copied that edited
function back into my module, and imported from there for the worker.
I was getting the error 'not registered as a queueable function' and could
not figure out what the issue was for a while. I had to import the function
from my module for the insertion as well and then it worked.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#37>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AATGQSK24VC7FYFPVK2MZKLUB66FNANCNFSM5EBBVL6A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
I wonder if it might be easier to just automatically import the functions. The data payload includes both the module and function to call, so that's something we could do. I'm just wondering if doing so would cause any security concerns. |
Yea, there would be. A compromised queue could then pull in functions that are not meant to be run. I'll stick with the warning. |
Thanks for opening the issue! Fixed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It may be helpful someone in the future to specify that functions must be imported in the same way for the worker and for insertion (readme or a special error message).
I had a function from a module of mine that I copied into a notebook to troubleshoot and edit. I added the queueable decorator right there in the notebook and used that function for my task insertion. I copied that edited function back into my module, and imported from there for the worker.
I was getting the error 'not registered as a queueable function' and could not figure out what the issue was for a while. I had to import the function from my module for the insertion as well and then it worked.
The text was updated successfully, but these errors were encountered: