[#67346] Future of test suites for Ruby — Charles Oliver Nutter <headius@...>
I'll try to be brief so we can discuss all this. tl;dr: RubySpec is
19 messages
2015/01/05
[#67353] Re: Future of test suites for Ruby
— Tanaka Akira <akr@...>
2015/01/05
2015-01-06 7:18 GMT+09:00 Charles Oliver Nutter <headius@headius.com>:
[#67444] [ruby-trunk - Feature #10718] [Open] IO#close should not raise IOError on closed IO objects. — akr@...
Issue #10718 has been reported by Akira Tanaka.
3 messages
2015/01/09
[#67689] Keyword Arguments — Anthony Crumley <anthony.crumley@...>
Please forgive my ignorance as I am new to MRI development and am still
5 messages
2015/01/20
[#67733] [ruby-trunk - Bug #10761] Marshal.dump 100% slower in 2.2.0 vs 2.1.5 — normalperson@...
Issue #10761 has been updated by Eric Wong.
4 messages
2015/01/21
[#67736] Re: [ruby-trunk - Bug #10761] Marshal.dump 100% slower in 2.2.0 vs 2.1.5
— Eric Wong <normalperson@...>
2015/01/22
normalperson@yhbt.net wrote:
[#67772] Preventing Redundant Email Messages — Jeremy Evans <code@...>
For a long time, I've wondered why I sometimes receive redundant email
5 messages
2015/01/23
[ruby-core:67772] Preventing Redundant Email Messages
From:
Jeremy Evans <code@...>
Date:
2015-01-23 20:32:54 UTC
List:
ruby-core #67772
For a long time, I've wondered why I sometimes receive redundant email messages when a ticket is updated in Redmine. For example, just a few minutes ago: [ruby-core:67768] Re: [ruby-trunk - Misc #10754] Tiny optimisation of Set#include? [ruby-core:67769] [ruby-trunk - Misc #10754] Tiny optimisation of Set#include? The first one appears to be Erik's response (coming from Eric's email server), and the second one is a ticket update from Redmine (coming from an application running on Heroku via Sendgrid). I'm guessing that the scenario is: Eric responds to an email, and there is a program running which takes his response, updates a ticket, and updating a ticket sends out another response. Assuming that is the case, is there any way to avoid this? Can we have the program that updates the ticket set a flag to not send out the duplicate email? Or change something so that Eric's initial email is not sent out to ruby-core, it just updates a ticket, which causes the second email to be sent out? Thanks, Jeremy