You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
there appears #158 to be an issue with multithreading, where several API requests by the same machine (same IP) appear to lock one another.
Potentially because of issues with the handle #158.
If that can be reprexed, the solutions are, in order of preference:
use shiny promises to queue the render jobs in the background, so there's always only one of them working at any one time.
(If that is possible, I am not sure)
To clarify, the issue here is not whether the Alice's shiny session is blocked by Bob, or by Alice, but whether a job started by Alice can wait for all other jobs to be finished.
hack around this limitation with purrr and exp backoff.
Call crossref directly with httr, though it would need to be reprexed whether this is an issue.
The text was updated successfully, but these errors were encountered:
there appears #158 to be an issue with multithreading, where several API requests by the same machine (same IP) appear to lock one another.
Potentially because of issues with the handle #158.
If that can be reprexed, the solutions are, in order of preference:
(If that is possible, I am not sure)
To clarify, the issue here is not whether the Alice's shiny session is blocked by Bob, or by Alice, but whether a job started by Alice can wait for all other jobs to be finished.
The text was updated successfully, but these errors were encountered: