When the input has byte order mark, the YAML parser stops processing the input upon seeing the first newline. I believe this is a violation of YAML specification. [[http://www.yaml.org/spec/1.2/spec.html#id2771184]] ~~~ [1] pry(ma...hasari (Hiro Asari)
The current stacktrace is misleading. Without line 4 in it, the implication is that the exception was found on line 2, and was not caught by `rescue`. In this simple case, the stack trace should contain lines `[4,7]`, not `[2,7]`. I a...hasari (Hiro Asari)
Given: ~~~ $ cat -n foo.rb 1 def foo 2 raise StandardError 3 rescue StandardError => e 4 raise e 5 end 6 7 foo ~~~ one would reasonably expect to see line 4 to be in the back t...hasari (Hiro Asari)
My Mac has the disk reformatted so that it is case-sensitive (HFS+): ~~~ $ touch foo.txt foo.TXT FOO.txt FOO.TXT $ ls -li foo.* FOO.* 286444732 -rw-r--r-- 1 asari staff 0 Jan 6 08:00 FOO.TXT 286444731...hasari (Hiro Asari)
On a second thought, this seems to be a poorly chosen "example". You can close this ticket. If I come across a better example, I'll open a new one. Sorry for the noise.hasari (Hiro Asari)
There are some tests that depend on timing of the execution, and fail sporadically. I have not surveyed the entire suite, but one is pointed out in https://github.com/jruby/jruby/issues/618. https://github.com/ruby/ruby/blob/v1_8_7...hasari (Hiro Asari)
hasari (Hiro Asari)02:39 PM Ruby Bug #13615: YAML parser stops processing at the first newline when byte order mark is present