http://permalink.gmane.org/gmane.comp.lang.ruby.core hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.lang.ruby.core/44544 <pre> Issue #1873 has been updated by boris_stitnicky (Boris Stitnicky). Hi everyone. I am a newbie user of computer languages (&lt; 1 year), and I am providing my feedback from this position. Summary: I find that this feature proposal is basically an extension of Regex state machine functionality. I am against it. I think, that the current behavior is natural: When one uses the same capture group name again, the old value is lost, just like when one assigns a new value to the same variable name. In Regex machine, I value simplicity and memorizeability over abundance of features. Moreover, as runpaint points out himself, this feature is really not missing: "lost" captures are available via #to_a and #capture methods. Rationale: As a newbie, I still remember hard time that I had learning Regex. I find the learning overhead for Ruby acceptable to make it usefull as a tool for people, who are not programmers by profession. But I found that to actually solve even simple domain-specific programming tasks, one has to </pre> boris_stitnicky (Boris Stitnicky 2012-05-25T21:48:06 http://permalink.gmane.org/gmane.comp.lang.ruby.core/44543 <pre> Issue #905 has been updated by boris_stitnicky (Boris Stitnicky). Uh oh, this discussion is already a pain to read. ---------------------------------------- Feature #905: Add String.new(fixnum) to preallocate large buffer https://bugs.ruby-lang.org/issues/905#change-26828 Author: headius (Charles Nutter) Status: Feedback Priority: Normal Assignee: matz (Yukihiro Matsumoto) Category: Target version: 2.0.0 =begin Because Strings are used in ruby as arbitrary byte buffers, and because the cost of growing a String increases as it gets larger (especially when it starts small), String.new should support a form that takes a fixnum and ensures the backing store will have at least that much room. This is analogous to Array.new(fixnum) which does the same thing. The simple implementation of this would just add a Fixnum check to the String.new method, and the result would be an empty string with that size buffer. This would allow heavy string-appending algorithms and libraries (like ERb) to avoid doing so ma</pre> boris_stitnicky (Boris Stitnicky 2012-05-25T19:25:54 http://permalink.gmane.org/gmane.comp.lang.ruby.core/44542 <pre> Issue #6496 has been reported by vbatts (Vincent Batts). ---------------------------------------- Bug #6496: Adding a bit of DL and friends documentation https://bugs.ruby-lang.org/issues/6496 Author: vbatts (Vincent Batts) Status: Open Priority: Normal Assignee: drbrain (Eric Hodel) Category: DOC Target version: ruby -v: head Here is a little bit of documentation for DL. Overall it add 0.15% documentation coverage. \o/ </pre> vbatts (Vincent Batts 2012-05-25T18:31:31 http://permalink.gmane.org/gmane.comp.lang.ruby.core/44541 <pre> Issue #6495 has been reported by vbatts (Vincent Batts). ---------------------------------------- Bug #6495: uninitialized constant due to missing require https://bugs.ruby-lang.org/issues/6495 Author: vbatts (Vincent Batts) Status: Open Priority: Normal Assignee: Category: ext Target version: ruby -v: ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux &lt;issue&gt; irb(main):022:0&gt; require 'dl/struct' NameError: uninitialized constant DL::CStructEntity::ValueUtil from /usr/lib64/ruby/1.9.1/dl/struct.rb:48:in `&lt;class:CStructEntity&gt;' from /usr/lib64/ruby/1.9.1/dl/struct.rb:46:in `&lt;module:DL&gt;' from /usr/lib64/ruby/1.9.1/dl/struct.rb:4:in `&lt;top (required)&gt;' from /usr/lib64/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib64/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from (irb):22 from /usr/bin/irb:12:in `&lt;main&gt;' &lt;/issue&gt; the attached patch fixes this failure. </pre> vbatts (Vincent Batts 2012-05-25T17:19:18 http://permalink.gmane.org/gmane.comp.lang.ruby.core/44540 <pre> Issue #6492 has been updated by drbrain (Eric Hodel). naruse (Yui NARUSE) wrote: I hadn't thought of that, I will implement it. The response must contain Content-Length or Transfer-Encoding: chunked to be persistent, so this is OK. Net::HTTP already handles this. ---------------------------------------- Feature #6492: Inflate all HTTP Content-Encoding: deflate, gzip, x-gzip responses by default https://bugs.ruby-lang.org/issues/6492#change-26827 Author: drbrain (Eric Hodel) Status: Open Priority: Normal Assignee: Category: lib Target version: 2.0.0 =begin This patch moves the compression-handling code from Net::HTTP#get to Net::HTTPResponse to allow decompression to occur by default on any response body. (A future patch will set the Accept-Encoding on all requests that allow response bodies by default.) Instead of having separate decompression code for deflate and gzip-encoded responses, (({Zlib::Inflate.new(32 + Zlib::MAX_WBITS)})) is used which automatically detects and inflated gzip-wrapped st</pre> drbrain (Eric Hodel 2012-05-25T17:06:07 http://permalink.gmane.org/gmane.comp.lang.ruby.core/44539 <pre> Issue #4802 has been updated by luislavena (Luis Lavena). Status changed from Open to Assigned ---------------------------------------- Backport #4802: Please backport r31742 https://bugs.ruby-lang.org/issues/4802#change-26826 Author: luislavena (Luis Lavena) Status: Assigned Priority: Normal Assignee: yugui (Yuki Sonoda) Category: ext Target version: Please backport r31742 from trunk into ruby_1_9_2 branch These modifications were required to solve Issue #4141 and are required for the successful inclusion of Tcl/Tk on RubyInstaller for Windows. Thank you. </pre> luislavena (Luis Lavena 2012-05-25T16:25:31 http://permalink.gmane.org/gmane.comp.lang.ruby.core/44538 <pre> Issue #1688 has been updated by luislavena (Luis Lavena). Tracker changed from Bug to Backport Description updated Status changed from Open to Closed Closing this out since I'm unable to reproduce the issue expressed here on newer versions of Ruby and RubyInstaller releases. ---------------------------------------- Backport #1688: Zlib raises a buffer error when inflating some kinds of data https://bugs.ruby-lang.org/issues/1688#change-26825 Author: luislavena (Luis Lavena) Status: Closed Priority: High Assignee: Category: Target version: =begin This issue was originally reported to One-Click Installer project by Jeremy Bopp: http://rubyforge.org//tracker/?func=detail&amp;atid=715&amp;aid=26404&amp;group_id=167 Description: While extracting compressed entries from a ZIP archive, I came across a particular file entry which when read in using a 4096 byte buffer which was then sent to be inflated would cause Zlib to raise a buffer error. This affects affects versions 186-26, 186-27-rc1, and 186-27-rc2</pre> luislavena (Luis Lavena 2012-05-25T16:25:00 http://permalink.gmane.org/gmane.comp.lang.ruby.core/44537 <pre> Issue #1941 has been updated by luislavena (Luis Lavena). Status changed from Assigned to Closed ---------------------------------------- Backport #1941: Issues with Ruby 1.8.6 patchlevel 383 and any package installation https://bugs.ruby-lang.org/issues/1941#change-26824 Author: luislavena (Luis Lavena) Status: Closed Priority: High Assignee: wyhaines (Kirk Haines) Category: Target version: =begin Working on updating RubyInstaller packages to recently released patchlevel 383, found that my patching strategies over rbconfig no longer works. On previous patchlevel (368), I configure ruby with my sandbox path, and once installed, gsub it from rbconfig, leaving this: CONFIG["prefix"] = (TOPDIR || DESTDIR + "") Where my path was inside "". Since TOPDIR refers to rbconfig.rb itself (but with stripped path), prefix end being always the path where Ruby ends installed/copied. DESTDIR ends not being used for the prefix, and it's value turns to be "C:" Now, bear with me for a second, on p36</pre> luislavena (Luis Lavena 2012-05-25T16:23:23 http://permalink.gmane.org/gmane.comp.lang.ruby.core/44536 <pre> Issue #1941 has been updated by luislavena (Luis Lavena). Tracker changed from Bug to Backport Description updated Closing this out since Ruby 1.8.6 EOL has already passed and 1.8.6 is no longer maintained/support neither by Core or RubyInstaller. ---------------------------------------- Backport #1941: Issues with Ruby 1.8.6 patchlevel 383 and any package installation https://bugs.ruby-lang.org/issues/1941#change-26823 Author: luislavena (Luis Lavena) Status: Assigned Priority: High Assignee: wyhaines (Kirk Haines) Category: Target version: =begin Working on updating RubyInstaller packages to recently released patchlevel 383, found that my patching strategies over rbconfig no longer works. On previous patchlevel (368), I configure ruby with my sandbox path, and once installed, gsub it from rbconfig, leaving this: CONFIG["prefix"] = (TOPDIR || DESTDIR + "") Where my path was inside "". Since TOPDIR refers to rbconfig.rb itself (but with stripped path), prefix end being always the path wh</pre> luislavena (Luis Lavena 2012-05-25T16:23:15 http://permalink.gmane.org/gmane.comp.lang.ruby.core/44535 <pre> Issue #1940 has been updated by luislavena (Luis Lavena). Tracker changed from Bug to Backport Description updated Status changed from Assigned to Closed Closing this out since 1.9.1 is no longer maintained/updated. ---------------------------------------- Backport #1940: Segmentation fault on TestFiber#test_many_fibers_with_threads (make check) https://bugs.ruby-lang.org/issues/1940#change-26822 Author: luislavena (Luis Lavena) Status: Closed Priority: High Assignee: nobu (Nobuyoshi Nakada) Category: core Target version: =begin When executing make check for 1.9.1-p243, TestFiber with threads generated a failure and silently terminated. There is no backtrace of such event. Going to plug GDB to trace it (since is a MinGW built). Is someone there that made or complete executing Ruby 1.9.1 tests? =end </pre> luislavena (Luis Lavena 2012-05-25T16:22:30 http://permalink.gmane.org/gmane.comp.lang.ruby.core/44534 <pre> Issue #6492 has been updated by naruse (Yui NARUSE). drbrain (Eric Hodel) wrote: I see, If Inflater's &lt; at &gt;socket.read returns nil or a string shorter than clen, it means the input is finished and &lt; at &gt;inflate can finish. So at that time, you can call &lt; at &gt;inflate.finish. But on persistent connection current simple read all may eat another content, mustn't it? I suspect they must see content body. ---------------------------------------- Feature #6492: Inflate all HTTP Content-Encoding: deflate, gzip, x-gzip responses by default https://bugs.ruby-lang.org/issues/6492#change-26821 Author: drbrain (Eric Hodel) Status: Open Priority: Normal Assignee: Category: lib Target version: 2.0.0 =begin This patch moves the compression-handling code from Net::HTTP#get to Net::HTTPResponse to allow decompression to occur by default on any response body. (A future patch will set the Accept-Encoding on all requests that allow response bodies by default.) Instead of having separate decompression code for deflate and gzip-enco</pre> naruse (Yui NARUSE 2012-05-25T06:38:48 http://permalink.gmane.org/gmane.comp.lang.ruby.core/44533 <pre> Issue #6492 has been updated by drbrain (Eric Hodel). naruse (Yui NARUSE) wrote: I considered this, but calling #close would also terminate a persistent connection which is undesirable. I don't see a way to cleanly finish the inflate stream without an if-clause. I will submit a new patch that includes fixes for the rest of your comments. ---------------------------------------- Feature #6492: Inflate all HTTP Content-Encoding: deflate, gzip, x-gzip responses by default https://bugs.ruby-lang.org/issues/6492#change-26820 Author: drbrain (Eric Hodel) Status: Open Priority: Normal Assignee: Category: lib Target version: 2.0.0 =begin This patch moves the compression-handling code from Net::HTTP#get to Net::HTTPResponse to allow decompression to occur by default on any response body. (A future patch will set the Accept-Encoding on all requests that allow response bodies by default.) Instead of having separate decompression code for deflate and gzip-encoded responses, (({Zlib::Inflate.new(32 + Zlib::</pre> drbrain (Eric Hodel 2012-05-25T06:15:10 http://permalink.gmane.org/gmane.comp.lang.ruby.core/44532 <pre> Issue #6491 has been updated by naruse (Yui NARUSE). Status changed from Open to Assigned Assignee set to tadf (tadayoshi funaba) ---------------------------------------- Bug #6491: DateTime.strftime('%Z') output is incorrect format https://bugs.ruby-lang.org/issues/6491#change-26818 Author: zombor (Jeremy Bush) Status: Assigned Priority: Normal Assignee: tadf (tadayoshi funaba) Category: Target version: ruby -v: ruby 1.9.3p125 (2012-02-16 revision 34643) [x86_64-darwin11] DateTime.parse('2012/05/23').strftime('%Z') should output 'GMT' (or a similar string). It outputs "+00:00" (or a similar offset string). </pre> naruse (Yui NARUSE 2012-05-25T02:39:19 http://permalink.gmane.org/gmane.comp.lang.ruby.core/44531 <pre> Issue #6488 has been updated by shyouhei (Shyouhei Urabe). Category set to DOC Status changed from Open to Assigned Assignee set to drbrain (Eric Hodel) Seems this is a renderer issue. Eric, what do you think? ---------------------------------------- Bug #6488: String#slice example has a syntax error https://bugs.ruby-lang.org/issues/6488#change-26817 Author: amorsen (Benny Lyne Amorsen) Status: Assigned Priority: Normal Assignee: drbrain (Eric Hodel) Category: DOC Target version: 1.9.3 ruby -v: ruby 1.9.3p0 (2011-10-30) [x86_64-linux] http://www.ruby-doc.org/core-1.9.3/String.html#method-i-slice has a syntax error: a[%r[aeiou](.)\11//] #=&gt; "ell" a[%r[aeiou](.)\11//, 0] #=&gt; "ell" a[%r[aeiou](.)\11//, 1] #=&gt; "l" a[%r[aeiou](.)\11//, 2] #=&gt; nil Oh, I have just realized that similar problems exist in the other regexp examples on the page, not just for slice. </pre> shyouhei (Shyouhei Urabe 2012-05-25T02:21:45 http://permalink.gmane.org/gmane.comp.lang.ruby.core/44530 <pre> Issue #6492 has been updated by naruse (Yui NARUSE). I agree with the concept of the patch, but When &lt; at &gt;socket is Socket-like object, the object should behave like a socket. Inflater#finish should be Inflater#shutdown or Inflater#close and this if-clause is not needed. this variable inflater is confusing with the inflater method. This read method return a string whose length is not clen, this is wrong. Other IO-like object for example Zlib::GzipReader returns a string whose length is clen. So Inflater should have a internal buffer and return the string whose length is just clen. ---------------------------------------- Feature #6492: Inflate all HTTP Content-Encoding: deflate, gzip, x-gzip responses by default https://bugs.ruby-lang.org/issues/6492#change-26812 Author: drbrain (Eric Hodel) Status: Open Priority: Normal Assignee: Category: lib Target version: 2.0.0 =begin This patch moves the compression-handling code from Net::HTTP#get to Net::HTTPResponse to allow decompression to occur by defaul</pre> naruse (Yui NARUSE 2012-05-25T01:25:55 http://permalink.gmane.org/gmane.comp.lang.ruby.core/44529 <pre> Issue #6493 has been updated by MartinBosslet (Martin Bosslet). Status changed from Assigned to Feedback Priority changed from Normal to Low RFC 3280 was obsoleted by 5280 and there, the wording is slightly different: 8&lt;-------- 4.2.1.6. Subject Alternative Name The subject alternative name extension allows identities to be bound to the subject of the certificate. These identities may be included in addition to or in place of the identity in the subject field of the certificate. But I think we should orient ourselves at RFC 6125 [1], which explicitly addresses how to do hostname verification for TLS services. There, it says: 8&lt;------ 6.4.4. Checking of Common Names As noted, a client MUST NOT seek a match for a reference identifier of CN-ID if the presented identifiers include a DNS-ID, SRV-ID, URI-ID, or any application-specific identifier types supported by the client. Therefore current behavior is in line with this and correct in doing so. But what's missing is verification of the service</pre> MartinBosslet (Martin Bosslet 2012-05-25T00:48:26 http://permalink.gmane.org/gmane.comp.lang.ruby.core/44528 <pre> Issue #6492 has been updated by drbrain (Eric Hodel). File net.http.inflate_by_default.patch added Opps, forgot patch. ---------------------------------------- Feature #6492: Inflate all HTTP Content-Encoding: deflate, gzip, x-gzip responses by default https://bugs.ruby-lang.org/issues/6492#change-26810 Author: drbrain (Eric Hodel) Status: Open Priority: Normal Assignee: Category: lib Target version: 2.0.0 =begin This patch moves the compression-handling code from Net::HTTP#get to Net::HTTPResponse to allow decompression to occur by default on any response body. (A future patch will set the Accept-Encoding on all requests that allow response bodies by default.) Instead of having separate decompression code for deflate and gzip-encoded responses, (({Zlib::Inflate.new(32 + Zlib::MAX_WBITS)})) is used which automatically detects and inflated gzip-wrapped streams which allows for simpler processing of gzip bodies (no need to create a StringIO). =end </pre> drbrain (Eric Hodel 2012-05-25T00:15:30 http://permalink.gmane.org/gmane.comp.lang.ruby.core/44527 <pre> Issue #6493 has been updated by drbrain (Eric Hodel). Category set to ext Status changed from Open to Assigned Assignee set to MartinBosslet (Martin Bosslet) Target version set to 2.0.0 ---------------------------------------- Bug #6493: OpenSSL::SSL ignores DN if subjectAltName is specified https://bugs.ruby-lang.org/issues/6493#change-26808 Author: djmitche (Dustin Mitchell) Status: Assigned Priority: Normal Assignee: MartinBosslet (Martin Bosslet) Category: ext Target version: 2.0.0 ruby -v: trunk In ext/openssl/lib/openssl/ssl.rb, verify_certificate_identity seems to intentionally *not* check the DN if any subjectAltName extensions are found. RFC3280 says &lt;pre&gt; The subject alternative names extension allows additional identities to be bound to the subject of the certificate. ... &lt;/pre&gt; which suggests that it contains *additional* identities, and thus does not exclude the subject. This functionality was added way back in 2005, r7970: * ext/openssl/lib/openssl/ssl.rb (OpenSSL::S</pre> drbrain (Eric Hodel 2012-05-24T23:23:07 http://permalink.gmane.org/gmane.comp.lang.ruby.core/44526 <pre> Issue #6494 has been updated by drbrain (Eric Hodel). File net.http.accept_gzip_deflate_by_default.patch added Oops, forgot patch. ---------------------------------------- Feature #6494: Send Accept-Encoding for all HTTP requests https://bugs.ruby-lang.org/issues/6494#change-26807 Author: drbrain (Eric Hodel) Status: Open Priority: Normal Assignee: Category: lib Target version: 2.0.0 This patch builds atop #6492 to enable Accept-Encoding by default for all HTTP requests that permit bodies. (Without #6492 it will break Net::HTTP.) This patch moves setting the Accept-Encoding header from Net::HTTP#get to Net::HTTP::GenericRequest#initialize. </pre> drbrain (Eric Hodel 2012-05-24T23:22:09 http://permalink.gmane.org/gmane.comp.lang.ruby.core/44525 <pre> Issue #6494 has been reported by drbrain (Eric Hodel). ---------------------------------------- Feature #6494: Send Accept-Encoding for all HTTP requests https://bugs.ruby-lang.org/issues/6494 Author: drbrain (Eric Hodel) Status: Open Priority: Normal Assignee: Category: lib Target version: 2.0.0 This patch builds atop #6492 to enable Accept-Encoding by default for all HTTP requests that permit bodies. (Without #6492 it will break Net::HTTP.) This patch moves setting the Accept-Encoding header from Net::HTTP#get to Net::HTTP::GenericRequest#initialize. </pre> drbrain (Eric Hodel 2012-05-24T23:21:36 http://permalink.gmane.org/gmane.comp.lang.ruby.core/44524 <pre> Issue #6493 has been reported by djmitche (Dustin Mitchell). ---------------------------------------- Bug #6493: OpenSSL::SSL ignores DN if subjectAltName is specified https://bugs.ruby-lang.org/issues/6493 Author: djmitche (Dustin Mitchell) Status: Open Priority: Normal Assignee: Category: Target version: ruby -v: trunk In ext/openssl/lib/openssl/ssl.rb, verify_certificate_identity seems to intentionally *not* check the DN if any subjectAltName extensions are found. RFC3280 says &lt;pre&gt; The subject alternative names extension allows additional identities to be bound to the subject of the certificate. ... &lt;/pre&gt; which suggests that it contains *additional* identities, and thus does not exclude the subject. This functionality was added way back in 2005, r7970: * ext/openssl/lib/openssl/ssl.rb (OpenSSL::SSL::SSLSocket#post_connection_check): new method. and moved around several times since then. </pre> djmitche (Dustin Mitchell 2012-05-24T22:46:53 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.lang.ruby.core