-
Notifications
You must be signed in to change notification settings - Fork 24
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
RuntimeError: Job not found on printer #17
Comments
I see this is also happening when sending remote jobs:
|
I agree that this is a better way to handle statuses. But the API change would break deployments so I haven't made the change. |
I see, maybe then add a hash options when sending the print_file to specify what return value I expect ? that would also be cool and can be default for exception which wont heart running deployments |
That could work. Other APIs (particularly I'm thinking of HTTP REST APIs) do something semantically similar where the caller can request the return results in various formats. This would be a bit different though in that a "format" choice would include a flow control operation -- exception. I'll do some thinking about this. |
Sounds good, thanks for giving this a thought :) |
Maybe instead of returning an exception is is better to return this in the status ?
as in:
The text was updated successfully, but these errors were encountered: