Closed sean-duffy closed 10 years ago
No, from here.
It could come about from SheetWriter.Close
or SheetWriter.WriteHeader
, or elsewhere. I've had a bit of a look and I don't immediately see the problem. Let me know if you want to chat face-to-face about it.
The thing that's puzzling me is that if I run it locally, using the same CGI variables and the same database, it works fine.
same go version? definitely compiling the same code?
Same go version and same code, except of course darwin here and linux on the box. It's only the go version where I'm compiling that matters, right?
That is pretty puzzling. I think the only thing for it is to instrument every place where streams are written to and closed and try and identify where the erroneous write to closed stream is coming from.
Never mind, I found the problem. I hadn't git pull
ed in the xlsx repository on the box, I don't know how I didn't think of that! It works now so we can merge the pull request.
Classic problem :)
Write fails on box with the error
zip: write to closed file
, I have been unable to replicate this on my local machine. This appears to happen when the second sheet is being written.