-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
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
AssemblyInfo.bytes_expected
can be null
#26
Comments
Thanks for the detailed report, @andreyvit! This is not really a bug in the Go SDK but Transloadit's API is returning unexpected data. The |
Added to my todo. |
Hi. Please has there been a fix to this issue. I am experiencing the exact problem right now. Trying something like "info.Results["resize"][0].SSLURL" after a call to WaitForAssembly() the exact error message. |
@D-sense What exact values in the expression If the problem persists, please open a new issue as this seems unrelated or contact us at support@transloadit.com |
@Acconut ,
I still get the same error result. I have also tried polling on my end (by wrapping the login inside a for loop.) |
@D-sense You code looks incorrect. You must check the array length before accessing its items. Something like:
|
@Acconut, |
@D-sense Please open a new issue or contact us at support@transloadit.com and include the code for reproduction. |
Is there an ETA of this issue being fixed? I have the exact same behavior as @andreyvit. Just to be clear, I am using the sdk via its intended API and no custom or special way. |
@SaschaPWittwer Thank you for the report! We haven´t had a customer mentioning this in the last months, but now we will start investigation again. Could you share a bit more details on your setup and details? i.e. how many files are you upload, what is their size? Is this happening repeatedly or just during some periods? Is your network condition reliable or rather inconsistent? Does WaitForAssembly return the error directly after starting or just after a few seconds? Any information would help! |
@Acconut Thanks for the reply! I know that those information's aren't as detailed as you might have hoped, but it is as it is. We tested our own application quit some time to analyze the error but could find any real indicator on why the error appears. |
@tim-kos In the CI tests, I noticed that this error resurfaced in another fashion:
This means that the bytes_expected property in the API response is a string, and therefore the JSON parser cannot, by default, convert it into an integer. Here is an example response I captured, showing what the assembly response looked like:
Any idea, why this might happen? |
Even more interesting: When I fetch the assembly status, now that the assembly is complete, the bytes_expected property is null (see https://api2.transloadit.com/assemblies/ee98ab33118849d1992d3b057c4515f1):
|
I remember that the CI tests are try to replay an Assembly. Could the incorrect values be caused by replaying an Assembly? |
Doesn't seems like it. I disabled the test on the CI for replaying assemblies and the error is still occurring. |
I'm getting this error as well. |
Hey!
WaitAssembly
fails for me with the following error:failed unmarshal http request: json: cannot unmarshal string into Go struct field AssemblyInfo.bytes_expected of type int
The corresponding assembly response is below. You can clearly see that
bytes_expected
is null.The code producing the error is really nothing special:
and it fails at
WaitForAssembly
call.Note: I think I've redacted all private data. The image itself isn't private, just my userpic.
The text was updated successfully, but these errors were encountered: