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
Using Ruby 3.1 and Rails 7.01 to do a Direct Upload, we know we have to Monkeypatch out any of the Direct Upload token code. Failure to do so results in the dreaded:
Interestingly, while we get uploads working by removing this token, if we have an exception in our code, and then re-use the same upload to try again after fixing the exception, this error is indeed part of the cycle again. So as an example, when saving the attachment from a direct upload, we then try and run a background job to process it, and we blew that. If we fix the background job call, and just re-up a file, boom:
Yes. AFAIK that did not make any major changes to direct uploads. This is a strange one though. I get it. If I have an exception, everything about the form is probably borked, and for sure, trying to re-use it is not likely to work as Rails has now reset itself after the exception. Maybe this is all just smoke.
Using Ruby 3.1 and Rails 7.01 to do a Direct Upload, we know we have to Monkeypatch out any of the Direct Upload token code. Failure to do so results in the dreaded:
Interestingly, while we get uploads working by removing this token, if we have an exception in our code, and then re-use the same upload to try again after fixing the exception, this error is indeed part of the cycle again. So as an example, when saving the attachment from a direct upload, we then try and run a background job to process it, and we blew that. If we fix the background job call, and just re-up a file, boom:
I would love for this to be fixed!! I
The text was updated successfully, but these errors were encountered: