We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I though it was a a parallelism thing, but it seems that after some timeout value, XL just assumes that it finished.
I think this is the same code that doesn't wait for blocks to return. After 2 seconds or so, it just assumes they "returned 0" and are hence a-ok.
Now that I think about it, this is a mess. This block thing always was a mess, but I never though it "bleeded" into other areas.
The text was updated successfully, but these errors were encountered:
jorgeazevedo
No branches or pull requests
I though it was a a parallelism thing, but it seems that after some timeout value, XL just assumes that it finished.
I think this is the same code that doesn't wait for blocks to return. After 2 seconds or so, it just assumes they "returned 0" and are hence a-ok.
Now that I think about it, this is a mess. This block thing always was a mess, but I never though it "bleeded" into other areas.
The text was updated successfully, but these errors were encountered: