7 ms·
None of these backends currently fsync() correctly on MacOS, due to a Go bug fixed in 1.12.
by networkimprov 8y ago
None of these backends currently fsync() correctly on MacOS, due to a Go bug fixed in 1.12.
- fulafel 8y agoTo split hairs, the bug is in MacOS - its fsync() does not flush data to stable storage. Go 1.12 includes a workaround for this MacOS bug.
- networkimprov 8y agoTo split further, it's a MacOS design flaw, with a published workaround. It is a bug to fail to use the workaround :-)
- fulafel 8y agoI don't know if Apoke really acknowledges it as a bug or flaw. Their man page for fsync reads like an intentional misunderstanding of fsync semantics.