Backport #776
closedFile#flush doesn't flush in windows
Description
=begin
In windows, File#flush flushes ruby's internal buffers, however, the result is different from Linux.
I'd recommend adding an arbitrary fsync if you're in windows to ensure the buffers are actually flushed, to avoid unexpected cross platform bugs [such as one that attachment_fu has].
[ruby-core:19940]
This in 1.9/1.8.x
Thanks!
-=Roger
=end
Updated by matz (Yukihiro Matsumoto) almost 16 years ago
- Assignee set to usa (Usaku NAKAMURA)
=begin
=end
Updated by usa (Usaku NAKAMURA) almost 16 years ago
- Status changed from Open to Closed
- % Done changed from 0 to 100
=begin
Applied in changeset r20982.
=end
Updated by rogerdpack (Roger Pack) almost 16 years ago
=begin
Thanks for doing that. Would it be possible to backport these to 1.8 branch, too?
=end
Updated by rogerdpack (Roger Pack) almost 16 years ago
=begin
Wonder if it's related to recent zlib difficulties:
http://www.misuse.org/science/2007/09/07/ruby-zlib-buffer-error-on-windows/`
=end
Updated by shyouhei (Shyouhei Urabe) almost 16 years ago
- Status changed from Closed to Open
- % Done changed from 100 to 0
=begin
Moved to backport/1.8
=end
Updated by usa (Usaku NAKAMURA) over 15 years ago
- Status changed from Assigned to Closed
- % Done changed from 0 to 100
=begin
Applied in changeset r24223.
=end
Updated by rogerdpack (Roger Pack) over 15 years ago
=begin
thanks for doing that.
=r
=end
Updated by shyouhei (Shyouhei Urabe) over 15 years ago
- Status changed from Closed to Assigned
- Assignee changed from usa (Usaku NAKAMURA) to shyouhei (Shyouhei Urabe)
=begin
=end
Updated by shyouhei (Shyouhei Urabe) over 15 years ago
- Status changed from Assigned to Closed
=begin
Applied in changeset r24406.
=end
Updated by shyouhei (Shyouhei Urabe) over 15 years ago
- Status changed from Closed to Assigned
- Assignee changed from shyouhei (Shyouhei Urabe) to wyhaines (Kirk Haines)
=begin
=end
Updated by wyhaines (Kirk Haines) over 14 years ago
- Status changed from Assigned to Closed
=begin
This issue was solved with changeset r28003.
Roger, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
=end