GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Join GitHub todaySign up
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
Commentscommented Nov 9, 2017â¢
edited
commented Nov 9, 2017
commented Nov 10, 2017
commented Nov 11, 2017â¢
edited
commented Nov 11, 2017added a commit that referenced this issue Nov 11, 2017commented Nov 11, 2017
commented Nov 11, 2017
commented Nov 11, 2017â¢
edited
commented Nov 12, 2017â¢
edited
changed the title
|
Had the same problem, still a bug at v0.10.212. @radoslawoska fix works.
CSV attachments sent with yagmail can't be read properly on gmail client running on apple systems on current version. Its really important ^^. cheers! |
commented May 4, 2018
I have missed this one, thanks for bringing it back to attention. Feel free to make a PR as you've already found the fix, I'd gladly accept it and put it on pypi!
|
added a commit to amrutadotorg/yagmail that referenced this issue Nov 5, 2018
csv files proper handling in the Mac mail client
This commit was created on GitHub.com and signed with a verified signature using GitHubâs key.
GPG key ID: 4AEE18F83AFDEB23Learn about signing commits
referenced this issue Nov 5, 2018
Opencsv files proper handling in the Mac mail client #129
commented Nov 5, 2018
thank you, PR created
|
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment
Join GitHub today
Free Octet Stream Download
Sign up
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
Comments
commented Nov 16, 2017
I have a server that responds with binary data and an octet-stream header:
The Ultimate PCB Design Software Comparison Guide Comparing the Top 6 PCB CAD Programs. PCB design: you need a CAD program for your project, but which is best? There are already tons of articles like this available - and theyâll all bore you to death with the same mundane details (with the exception of. So, with that disclaimer out of the way, the following are widely considered the best free PCB design software platforms, listed in alphabetical order: DesignSpark PCB DesignSpark PCB is one of the worldâs most popular and easily accessible electronics design software platforms. And for good reason â the program is easy-to-use and learn. Best pcb design software. Best Free PCB design software Express PCB design software Express-PCB is available to download from the link express PCB official site. It is a good tool for. There is another PCB design software called EasyEDA you has not discussed. But I think it is the best circuit design tool for me, free, zero-install, easy to use and brings you easier EDA experience. It integrates powerful schematic capture, mixed-mode circuit simulation and PCB layout.
The response is a Buffer, so nock converts it to hex before storing in a file. I've truncated the response here and above, but it should be enough to get the idea.
When reading back from the file, I expect it to be converted back into a Buffer via Buffer.from(response.body, 'hex'). Instead it gets converted into a normal Buffer, e.g. the first byte is 'f', the second byte is '0', instead of one byte
0xf0 .
I can work around this for the time being by setting
Content-Encoding: identity , which triggers the right nock logic. But it would seem preferable to e.g. read the application/octet-stream response header and try to convert from hex based on that.
|
added a commit that referenced this issue Feb 20, 2018
referenced this issue Feb 20, 2018
MergedRecord & replay binary file response correctly #1067
commented Feb 20, 2018
Hey @kevinburke can you check if #1067 fixes your problem?
|
commented Feb 20, 2018
Apologies but I've since moved on from that engagement and probably won't have time to test :( best of luck!
A way to test would probably be to start with the JSON I put up above, read it back into memory, and verify the length of the buffer in memory matches the Content-Length header.
|
bot commented Sep 13, 2018
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue and add a reference to this one if itâs related. Thank you!
|
bot locked as resolved and limited conversation to collaborators Sep 13, 2018
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.
Comments are closed.
Author
Write something about yourself. No need to be fancy, just an overview.