[PATCH] IO#read behaves incorrectly
Reported by Le Huy | February 9th, 2008 @ 01:58 AM | in 1.0 preview
bug can be observed by looking at result of the following snippet, which copy attached file to /tmp
require 'fileutils'
FileUtils::copy_file('source_index.rb','/tmp/source_index.rb')
the result file missed few hundred bytes at the end
Comments and changes to this ticket
-
Le Huy February 9th, 2008 @ 01:41 AM
- → Title changed from “[BUG] IO#read behaves incorrectly” to “[PATH] IO#read behaves incorrectly”
-
Dirkjan Bussink February 9th, 2008 @ 02:18 AM
- → State changed from “new” to “open”
Could you also create a spec for this besides the bugfix? I think your example could be translated into a spec very easy :).
-
Le Huy February 9th, 2008 @ 11:15 PM
- no changes were found...
-
-
Le Huy February 12th, 2008 @ 01:50 AM
- no changes were found...
-
Le Huy February 12th, 2008 @ 02:05 AM
modify spec/ruby/1.8/core/io/read_spec.rb to return IO::BufferSize to original value after running the spec
-
Brian Ford February 24th, 2008 @ 07:31 PM
The specs for IO::BufferSize should go in spec/core/io. There is a somewhat fuzzy line for when to include specs guarded with extended_on. IO::Buffer and related stuff is quite a bit, so there should be Rubinius specific specs for it. The extended_on guard should only be for extending the behavior of a method or perhaps adding a method to an existing class.
-
Ryan Davis February 29th, 2008 @ 04:17 PM
- → Assigned user changed from “” to “Eric Hodel”
-
Eero Saynatkari March 30th, 2008 @ 08:52 PM
- → Title changed from “[PATH] IO#read behaves incorrectly” to “[PATCH] IO#read behaves incorrectly”
- → Assigned user changed from “Eric Hodel” to “Eero Saynatkari”
-
Eero Saynatkari March 31st, 2008 @ 12:45 AM
- → State changed from “open” to “resolved”
I applied the simple test case in e258a2bc but moved it to spec/core/io/, thanks. The spec runs successfully and the second patch to IO does not currently apply cleanly so that one is not used. Please open a new ticket if there are still issues.
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
