[#81999] [Ruby trunk Bug#13737] "can't modify frozen String" when installing bundled gems — ko1@...
Issue #13737 has been updated by ko1 (Koichi Sasada).
4 messages
2017/07/11
[#82005] [Ruby trunk Bug#13737] "can't modify frozen String" when installing bundled gems — nobu@...
Issue #13737 has been updated by nobu (Nobuyoshi Nakada).
3 messages
2017/07/12
[#82102] Re: register_fstring_tainted:FL_TEST_RAW(str, RSTRING_FSTR) — Eric Wong <normalperson@...>
Koichi Sasada <ko1@atdot.net> wrote:
4 messages
2017/07/18
[#82151] [Ruby trunk Feature#13637] [PATCH] tool/runruby.rb: test with smallest possible machine stack — Rei.Odaira@...
Issue #13637 has been updated by ReiOdaira (Rei Odaira).
3 messages
2017/07/24
[ruby-core:81969] [Ruby trunk Bug#13726] PATCH: Windows builds - fractional second file times
From:
kubo@...
Date:
2017-07-08 05:47:03 UTC
List:
ruby-core #81969
Issue #13726 has been updated by kubo (Takehiro Kubo). 01-time-subsec.patch changes declarations in include/ruby/win32.h. IMO, it could be in ruby 2.5.x but could not be backported to ruby 2.4.x because of ABI incompatibility. It also deletes meaningless TZ checking I pointed at #13702. ---------------------------------------- Bug #13726: PATCH: Windows builds - fractional second file times https://bugs.ruby-lang.org/issues/13726#change-65693 * Author: MSP-Greg (Greg L) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: trunk * Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN ---------------------------------------- At present, I believe Windows builds have integer seconds resolution on File times. Attached are three patches that seem to correct the issue. The numbered patches are best applied in order. The c source patches were created by kubo (Kubo Takehiro); I created the spec patch, along with some testing. All related tests (run parallel) pass on my system for MinGW builds and x64-mswin64_140 builds. I did some checks with Appveyor, and there may be issues with the logger tests, due to the fact that the tests are very time sensitive (I ran -j3 on a quad system, Appveyor runs -j2 on a dual core). I believe file time values are stored with 100 ns resolution, but times have 100 袖s resolution. This was the reason for some of the changes to the tests, as time appears to be truncated (floor), as opposed to round. I would appreciate if consideration could be given to adding this (or similar) code. Thank you. ---Files-------------------------------- 02-file-utime.patch (5.53 KB) spec-rubyspec-core-file-time.patch (2.99 KB) 01-time-subsec.patch (15.2 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>