themekit: Receiving malformed response (bad response or corrupted JSON)
Is your feature request related to a problem? Please describe.
Using version 1.0.0 windows 10 64 bit
When downloading theme files, using themekit get -t=THEMEID, you may get the following message output:
error downloading asset: received a malformed response
Which seems to be from ErrMalformedResponse
Without the verbose (-v) flag after the download process finishes this may be displayed multiple times.
And the progress count indicates all files have downloaded but some files are actually missing when checking the folders&files on the OS.
With the verbose flag I will see the above error in between messages of “Successfully wrote X to disk” so creates an ambiguity because what does that mean when following an error?
- A) the file displayed after the error message was the one erroring and finally downloaded successfully?
- B) that a file got skipped silently and next message are other files downloading and wrote to disk successfully?
- ???
Without the filename or a checksum system you have to download the theme zip and do a comparison if you want to soothe the file paranoia, and then copy any missing files
Describe the solution you’d like Included the relevant filename so interpretation of the message is easier. Or clarifying if a file needs to be redownloaded either in the console or in the documentation. Or provide a log of affected files to then pipe back into themekit for individual download. Or prompt user to retry missing files
Describe alternatives you’ve considered Alternative is to manually download theme zip from the store admin via email kinda rendering themekits download capability pointless when these errors occur.
Additional context I’m not able to reliably reproduce the same output with the -v flag or narrow down if it’s specific file types, or as a problem on shopifys end or my end. The theme was created less than an hour before running command Increasing the timeout to 1minute doesn’t make it go away.
About this issue
- Original URL
- State: open
- Created 5 years ago
- Comments: 36 (13 by maintainers)
Context Cancelled
is worriesome. Right now I am cancelling requests with context when we get a 499 status response. I did not think that this would effect responses that have already completed. I think I might be able to make a work around for this.Probably unrelated and merely a coincidence but that js file indicates it’s the same theme that first gave me these types of errors. Which at the time seemed like a combo of the wifi portal used and maybe the large images assets.
Unfortunately I think repeatability is the problem here, I’ve not seen it again since themekit was updated with #544 thanks to tanema, however I also haven’t touched that theme again but I made a laundry list to go through if it happened again since it kills productivity when it happens. To rule out cases such as specific themes being culprits anyone wanting to hunt this down could try:
That at least narrows it more to the theme itself or some themekit bug and not single network oddness Make a backup export of the theme:
theme download
->theme deploy
either over the problem theme or a new foldertheme new
to generate a theme and repeat themekit commands either over the problem theme or a new folderTheme trials do not let you access the themes code neither through the admin or the api AFAIK , though this seems like this should be a 403 access forbidden instead of this error.
On Wed, Apr 8, 2020, 4:33 AM oscarsan notifications@github.com wrote: