The files were binary and of what appeared to be the correct file sizes. A `file `call just returned `data`.
However, I checked just now and it is working again this evening. For what it's worth, this problem occurred on multiple geographically-distributed machines running various Linux-based operating systems all using the same script that suddenly stopped working, so I'm confident that the problem was on the neo4j servers. All's well that ends well, I suppose. Thanks for checking! Josh -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
