Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@gl3nn
Copy link
Contributor

@gl3nn gl3nn commented Oct 30, 2019

By doing this we can catch the TaskException higher up and still have access to the task_id. Otherwise we need to catch the exception at every place where we try to fetch a result in order to be able to fetch the task_id from the result object.

I don't think adding this extra meta information has any downsides.

@coleifer
Copy link
Owner

Eehhh... Since the result is only keyed by the task ID already, this seems kind-of gross/unnecessary. Going to pass for now.

@coleifer coleifer closed this Oct 30, 2019
@gl3nn
Copy link
Contributor Author

gl3nn commented Oct 30, 2019

Is there an option to fetch the task ID in a TaskException that I'm missing then? The result object does indeed have it but ideally I would be able to get the task ID wherever the exception is caught in the application.

@coleifer coleifer reopened this Oct 30, 2019
@coleifer
Copy link
Owner

Fair enough, let's merge it.

@coleifer coleifer merged commit e6710bd into coleifer:master Oct 30, 2019
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.

2 participants