When deploying: TypeError: incompatible marshal file format (can't be read) format version 4.8 required; 60.60 given #409
Comments
|
Ok, found a solution but don't know what happened. So if someone can explain please do. But what resolved the issue was: EDIT: stupid typo: rm tmp/compiled_content tmp/checksums |
|
Thanks, I have the exact same issue. I think you meant: rm -f tmp/compiled_content /tmp/checksums |
|
Did this happen after upgrading from one Ruby version to another? nanoc uses PStore to store information that speeds up compilation. The error seems to indicate that this information got corrupted somehow. I don’t know how that could happen; nanoc did not modify the file format, and this seems to indicate something more fundamental going wrong. Being able to reproduce this problem would help immensely. |
|
No upgrade of anything. But we were checking in the tmp folder into git while committing. After we created the .gitignore and added tmp to exclude this error came. As said removing those 2 files did the trick. |
|
Hmm, do you by chance have |
|
By the way, the |
|
No upgrade done on ruby: |
|
It can be triggered by just accidentally checking in tmp/ in git. So on a working nanoc install, it's enough to check out a project where the tmp/* wasn't excluded in .gitignore (e.g. |
|
Hmm, looks like the “incompatible marshal file format” error is not always avoidable:
(from http://ruby-doc.org/core/Marshal.html) However, the latest version of Marshal’s file format is 4.8, and definitely not 60.60. |
|
@gplv2 Ahh, that is quite interesting. I cannot reproduce that issue locally, however. Do you mind sharing your ~/.gitconfig? (Be sure not to include sensitive data.) |
|
If you try to google that exact 60.60 line it turns out this has been seen in the wild, but kind of strange that it is a game that throws them: http://sb2revival.lefora.com/reply/46985259#.UznFnJAW30o Not exactly the kind of hit I expected: I took out the github url, it's a private project |
|
Yep, spotted that one as well, but doesn’t give any useful information. The |
|
I'm on ubuntu , @gtheys looks to be on macbook. |
|
Oh yeah, I could’ve derived that from the information you posted, my mistake. Seems like an okay plan of action would be to let nanoc catch that error and recreate the files if they cannot be read. It’s not the best approach, but it will at least prevent having to manually nuke |
|
No problem on the version, it's no trouble. Tx for picking this up so fast. I put my money on an issue within PStore. I checked a long list of loose hits and it pretty much came back to pstore, just as the error actually says. Don't think it's a nanoc issue but a workaround is the noble approach. |
|
Yeah, PStore is kinda icky (and slow) and I’m evaluating alternatives for it in nanoc 4.0. |
|
Let me know if you need a tester, I'm a 2day nanoc noob ;-) |
|
I would consider sqlite3 as a temp store, I build the biggest apps with it a lot on PHP, it's very fast and portable. Just my 2c. Every project I build with it keeps running :) |
Reset corrupted PStore (fixes #409)
|
#409 causes the store to be reset on error, which should avoid these issues. |
I try to deploy to the server and got this error:
EDIT: when I run any nanoc command inside a existing nanoc project. When I create a new project I don't have a problem.
EDIT2: Al versions are the same: ruby, gems, nanoc, etc. So I'm certain it's has to do with my site content.
The text was updated successfully, but these errors were encountered: