🤑 Indie game store🙌 Free games😂 Fun games😨 Horror games
👷 Game development🎨 Assets📚 Comics
🎉 Sales🎁 Bundles

Keep getting *errors.errorString unexpected EOF (0x405e751) in Butler Mac

A topic by TetraStudios created 72 days ago Views: 199 Replies: 21
Viewing posts 1 to 2

Hello! I keep getting this error whenever I try to push an existing build in butler. It goes to 100%, then the program starts glitching and the progress percentage goes into the minus and counts backwards.  Does anyone know how to fix this? Full error:

*errors.errorString unexpected EOF
/usr/local/Cellar/go/1.9.2/libexec/src/runtime/asm_amd64.s:2337 (0x405e751)

Thanks! 

ProjectTetraDev

Admin

That sounds pretty bad.

Which version of butler are you using? You can find out by doing "butler -V'.

I am using version: 

head, built on Feb 11 2018 @ 05:11:42, ref f1d16431c612b5ece5b46bffed7316e3d9b9cb2d

It keeps coming up on Mac and PC, but only when uploading to a certain channel. It keeps working until I push to that channel (osx-universal), and then the bug keeps appearing.

Admin

Thanks for the additional info. Are you seeing the same issue with butler v10.4.0 ?

You can download it from:

Also, can you upload what you're trying to push somewhere else so I can try to reproduce the issue? Thanks!

Admin

Also, please let me know

  1. Which operating system you're using, and which version
  2. The complete output of the butler push command (if there's any more lines when the error is displayed: that would be really useful).

Thanks!

Admin

I tried pushing exactly the contents of osx-universal again to the same channel, and it worked fine:


I did this test from Linux though - if you're uploading some Windows and there are symlinks involved, things might be different.

I have additional questions:

  • Are you pushing a folder or a .zip file ?
  • How long does it take for butler to fail with "unexpected EOF" ?
  • What's the CPU usage like while you're waiting for it to finish? Close to 100% or close to 0% ?

I downloaded the older version and it worked!

I used the channel osx-new and make sure that the file was not a zipped one. 

With the newer version, it would be about 5-10 minutes of the progressbar stuck at 100% until the program glitched out for another 5 minutes.

Thanks!

ProjectTetraDev

Admin

Alright, I'm going to try and find the bug, because if you had it with the latest master, then the next stable release will have that problem too!

Could you respond to my other questions to help me figure out the source of the bug? Thanks!

Ok!

Command:  Desktop/Project-TetraV1.1.zip tetrastudios/project-tetra:osx-universal

Operating System (I also tried on High Sierra and Windows 10):

I'll try and give you the other info later. 

Thanks!

ProjectTetraDev

Admin

Thanks for all the additional info!

I see you're pushing to new channels in the meantime: I would recommend not doing that, as users who installed the older channel will have to redownload the full version instead of just applying the patch. I'll let you know as soon as I'm able to reproduce the issue, find out what caused it, and push a butler update for you.

Admin

Wait, so the first time it failed for you, you were pushing a .zip? Can you upload that exact .zip somewhere and link me to it? (A draft itch.io page works for me, just give me the URL once it's up)

Admin

Note: if you do upload the .zip to an itch.io page, use the regular web upload, not butler - I need the exact same file you used to reproduce the issue.

It does not work:

butler push Desktop/ProjectTetraAlpha.zip tetrastudios/test4butler:osx-universal

That is how the issue happens: I think it's a combination of a zip file and osx-universal.

Admin

Now I really want to take a look at that .zip file :)

Can you use web upload to put i on the test4butler page, so I can download it as-is and test pushing it myself? Thanks!

Admin

Quick update: I'm not able to reproduce the error right now, pushing (what you pushed to osx-new) to (an equivalent of the osx-universal) channel from linux with the latest butler works just fine:

I'm going to try it all again from macOS with the exact version you mentioned.