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'm not sure if this is resolvable. And it's not a huge deal, IMO. But I wanted to register it because I saw it.
After tying into the pendingAttachments capability of direct uploads, I noticed that if I cancel an upload the pendingAttachments array is still populated until [some point when it gets cleared].
pendingAttachments
Here's a video proving it (the alert happens when pendingAttachments.length > 0):
pendingAttachments.length > 0
https://share.cleanshot.com/5RPZrJdf
The text was updated successfully, but these errors were encountered:
Oh hang on. I believe I know the fix for this. There's an appendTransaction in Rhino that needs to clear this.
Sorry, something went wrong.
Fixed in 0.14.2! If its still giving you problems, feel free to re-open this or open a new issue.
Just did a quick check and I think it's working. Thank you!
Successfully merging a pull request may close this issue.
I'm not sure if this is resolvable. And it's not a huge deal, IMO. But I wanted to register it because I saw it.
After tying into the
pendingAttachments
capability of direct uploads, I noticed that if I cancel an upload thependingAttachments
array is still populated until [some point when it gets cleared].Here's a video proving it (the alert happens when
pendingAttachments.length > 0
):https://share.cleanshot.com/5RPZrJdf
The text was updated successfully, but these errors were encountered: