[#81492] [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid — normalperson@...
Issue #13618 has been reported by normalperson (Eric Wong).
12 messages
2017/06/01
[#88695] Re: [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
— Eric Wong <normalperson@...>
2018/08/27
> https://bugs.ruby-lang.org/issues/13618
[#81569] [Ruby trunk Feature#12589] VM performance improvement proposal — vmakarov@...
Issue #12589 has been updated by vmakarov (Vladimir Makarov).
3 messages
2017/06/04
[#81581] [Ruby trunk Bug#13632] Not processable interrupt queue for a thread after it's notified that FD is closed in some other thread. — sir.nickolas@...
Issue #13632 has been reported by nvashchenko (Nikolay Vashchenko).
4 messages
2017/06/05
[#81590] Re: [ruby-cvs:66197] ko1:r59023 (trunk): revert r59020 because it may fail some tests sometimes on some environment (http://ci.rvm.jp/). This revert is to check the reason of failures. — Eric Wong <normalperson@...>
ko1@ruby-lang.org wrote:
5 messages
2017/06/06
[#81591] Re: [ruby-cvs:66197] ko1:r59023 (trunk): revert r59020 because it may fail some tests sometimes on some environment (http://ci.rvm.jp/). This revert is to check the reason of failures.
— Eric Wong <normalperson@...>
2017/06/06
Eric Wong <normalperson@yhbt.net> wrote:
[#81596] Re: [ruby-cvs:66203] Re: Re: ko1:r59023 (trunk): revert r59020 because it may fail some tests sometimes on some environment (http://ci.rvm.jp/). This revert is to check the reason of failures.
— Eric Wong <normalperson@...>
2017/06/06
Eric Wong <normalperson@yhbt.net> wrote:
[#81825] [Ruby trunk Feature#13697] [PATCH]: futex based thread primitives — normalperson@...
Issue #13697 has been reported by normalperson (Eric Wong).
3 messages
2017/06/29
[ruby-core:81661] [Ruby trunk Bug#13654] irb save-history extension is not concurrency-safe
From:
charles.cooke@...
Date:
2017-06-13 13:17:09 UTC
List:
ruby-core #81661
Issue #13654 has been reported by charles.cooke (Charles Cooke). ---------------------------------------- Bug #13654: irb save-history extension is not concurrency-safe https://bugs.ruby-lang.org/issues/13654 * Author: charles.cooke (Charles Cooke) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-linux] * Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN ---------------------------------------- ## Issue If 2 simultaneous irb sessions are running with save-history enabled, the history will be overwritten in full by the last irb session to exit and history will be lost. The save-history extension currently loads the existing file on session start, maintains history throughout the session, then regenerates the history file with the preloaded + new history from the current session. Therefore if the file contents are changed while the irb session is running, those changes are not overwritten when the session exits. As many systems have logrotate and could manage the file buffering independently, one idea would be to just append the history from current session, rather than recreating the history file. ## Steps to reproduce 1. Enable the save-history extension to log to a file 1. Start an irb session (Session #1) 1. Start a second irb session (Session #2) 1. In Session #1, execute commands and exit - verify that the output is generated correctly 1. In Session #2, execute commands and exit - PROBLEM - the output from Session #1 has been deleted See output below: ~~~ [current]$ cat .irbrc require 'irb/ext/save-history' IRB.conf[:SAVE_HISTORY] = 1000 IRB.conf[:HISTORY_FILE] = File.join(Dir.pwd, 'log', 'irb.log') ==== START SESSION #1# ==== [current]$ irb irb(main):001:0> puts 'Session #1 - Output' Session #1 - Output => nil irb(main):002:0> [1]+ Stopped irb ==== BACKGROUND SESSION #1# ==== ==== START SESSION #2# ==== [current]$ irb irb(main):001:0> puts 'Session #2 - Output' Session #2 - Output => nil irb(main):002:0> exit ==== STOP SESSION #2# ==== ==== OUTPUT IS EXPECTED ==== [current]$ cat log/irb.log puts 'Session #2 - Output' exit ==== RESUME SESSION #1 ==== [current]$ fg irb(main):003:0* puts 'Session #1 - Overwrites everything' Session #1 - Overwrites everything => nil irb(main):004:0> exit ==== PROBLEM - OUTPUT FROM SESSION #1 ONLY ==== [current]$ cat log/irb.log puts 'Session #1 - Output' puts 'Session #1 - Overwrites everything' exit ~~~ -- 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>