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
As per documentation, to do synchronous processing
# loop until processing is finisheduntilresponse.finished?sleep1;response.reload!# you'll want to implement a timeout in your production append
I use this code but it locks up the ruby thread indefinitely (even though Assembly has completed) only when i upload large files ~ 3GB
< 1 gb files works fine which makes this a very odd problem
Is there an internal timeout which is not caught?
The text was updated successfully, but these errors were encountered:
Does this happen for every upload that is 3GB big or just a particular one? It's interesting to see, as we just query the assembly status all the time so the only time this code can lock up is when the assembly never returns the status finished. Can you check what the assembly status is? response['ok'] is where it should be in. Maybe log that out in every nth loop.
The implementation of finished? is actually pretty simple, so I suspect that we don't get the right status back as response.
Maybe @tim-kos or @kvz also can look into the specific assembly on the backend side of things.
As per documentation, to do synchronous processing
I use this code but it locks up the ruby thread indefinitely (even though Assembly has completed) only when i upload large files ~ 3GB
< 1 gb files works fine which makes this a very odd problem
Is there an internal timeout which is not caught?
The text was updated successfully, but these errors were encountered: