[#64210] Asking for clarification for exception handling usage — Rodrigo Rosenfeld Rosas <rr.rosas@...>
I've created a ticket for that but didn't get any feedback so I decided
[#64517] Fw: Re: Ruby and Rails to become Apache Incubator Project — Tetsuya Kitahata <kitahata@99.alumni.u-tokyo.ac.jp>
What do you think? >> Ruby developers
What benefits are there to this? I have a feeling that adding unnecessary
On Sat, 23 Aug 2014 22:43:46 -0700
Here I am a Japanese. Before moving anywhere else answer to our question first: what benefits?
tax issue with each other.
Forgot to assert my opinions:
[#64614] cowspace (work-in-progress) — Eric Wong <normalperson@...>
Hi all, I started working on a cowspace branch. Based on the mspace API
[#64615] [ruby-trunk - Feature #10181] [Open] New method File.openat() — oss-ruby-lang@...
Issue #10181 has been reported by Technorama Ltd..
I like this feature.
On 08/28/2014 02:53 PM, Eric Wong wrote:
Joel VanderWerf <joelvanderwerf@gmail.com> wrote:
On 08/29/2014 12:55 AM, Eric Wong wrote:
Joel VanderWerf <joelvanderwerf@gmail.com> wrote:
[#64627] [ruby-trunk - Feature #10182] [PATCH] string.c: move frozen_strings table to rb_vm_t — ko1@...
Issue #10182 has been updated by Koichi Sasada.
[#64671] Fwd: [ruby-changes:35240] normal:r47322 (trunk): symbol.c (rb_sym2id): do not return garbage object — SASADA Koichi <ko1@...>
Why this fix solve your problem?
(2014/08/30 8:50), SASADA Koichi wrote:
SASADA Koichi <ko1@atdot.net> wrote:
Eric Wong <normalperson@yhbt.net> wrote:
(2014/08/31 0:18), Eric Wong wrote:
[ruby-core:64677] [ruby-trunk - Bug #10101] Zlib::GzipReader produce different outputs for different methods applied
Issue #10101 has been updated by cremno phobia. `read` returns a string with external encoding. In your case it seems to be `UTF-8`. The encodings of the given `IO` object are ignored. Using `Zlib::GzipReader.open` doesn't work either, by the way. It still ignores the b`, but as a workaround you can change the encoding of the returned string, pass `external_encoding: Encoding::ASCII_8BIT` as new argument, call `String#bytesize`, etc. After some rearranging and duplicating of the remaining two cases, I can't say why `each_byte` *sometimes* fails. But with the following lines, `[-2048, 1]` (2048 looks interesting) is printed by `f_gz.rewind` when it fails. ~~~ruby def f.seek(*args) p args super end ~~~ ---------------------------------------- Bug #10101: Zlib::GzipReader produce different outputs for different methods applied https://bugs.ruby-lang.org/issues/10101#change-48572 * Author: Rafael Manzo * Status: Open * Priority: Normal * Assignee: * Category: ext * Target version: * ruby -v: ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-linux] * Backport: 2.0.0: REQUIRED, 2.1: REQUIRED ---------------------------------------- The methods `read`, `readbyte` and `each_byte` are producing different outputs. Comparing with the unziped file, only the result of readbyte is correct according to the size but comparing byte per byte with the original file sometimes gives differences at the same positions. This part of the differences I couldn't reproduce in a way that I could share on the internet because the original file is a magnetic resonance image subject to confidentiality. But fortunately I was able to reproduce the bug on input size. I've attached a script that illustrates the problem and here is the link for the file that I've used for the following sample output: https://drive.google.com/file/d/0B3O0CbLN-q0TcmhGR0RGeWM2UHM/edit?usp=sharing Sorry about the size, but I couldn't produce a smaller file. <code> [manzo@WALL-A gz_debug]$ ruby -v ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-linux] [manzo@WALL-A gz_debug]$ ruby test1.rb sample.gz Size of read: 45102570 Size of each_byte: 4668 Size of readbyte: 45158752 </code> I hope I'm right on this report and thank you a lot for your time! ---Files-------------------------------- test1.rb (316 Bytes) -- https://bugs.ruby-lang.org/