In the spirit of release early, release often.... Err no, actually more in the spirit of, let's not try to lose data during file resolution... Coda 6.0.10 is out After running the new servers for a couple of days, Satya discovered this morning that some recently reintegrated files would sometimes show up as empty. This was caused by a subtle error in the file-resolution code in 6.0.9, where we would always propage the data from the server with index 1 instead of the dominant server (which is index i). As a result there is a 50% chance with double replication that everything is perfectly find, but a 50% chance that one server will have the actual file data, while the other is perfectly happy with a 0-length file. It just depends on which server the clients asks, so in the end we'd get a 25% chance that the client is unable to see the file contents after runt resolution.