Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
In the documentation of JobQueue
The example shows a one parameter constructor while actually its a two parameter method.
You are right. Once changed there is also the issue that the sample with threading as parallelisation method doesn't work because threads don't have an exitcode.
I am completely new to the internals of fabric but shouldn't a try/catch block within the WrappedCallableTask (or Task for that matter) class solve this so that we get an exit code depending on if an exception was thrown during the task execution or not?
Or is threading at this point not really a use-case anymore?
Additionally, would it make sense to move this whole sample code into a bunch of unittests?