[#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:81641] [Ruby trunk Bug#13649] Net::IMAP doesn't support response from a Microsoft Exchange server (which is not compliant with RFC standards)
From:
carlier.jeremy@...
Date:
2017-06-09 17:35:16 UTC
List:
ruby-core #81641
Issue #13649 has been reported by keysen (J辿r辿my Carlier).
----------------------------------------
Bug #13649: Net::IMAP doesn't support response from a Microsoft Exchange server (which is not compliant with RFC standards)
https://bugs.ruby-lang.org/issues/13649
* Author: keysen (J辿r辿my Carlier)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: 2.3.1
* Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN
----------------------------------------
Hello,
This day I wanted to use a mailbox hosted on a Microsoft Exchange server and it was not working.
I found this nice article relating the issue: http://claudiofloreani.blogspot.fr/2012/01/monkeypatching-ruby-imap-class-to-build.html
My solution to support those crappy server:
```ruby
module Net
class IMAP
class ResponseParser
def response
token = lookahead
case token.symbol
when T_PLUS
result = continue_req
when T_STAR
result = response_untagged
else
result = response_tagged
end
match(T_SPACE) if lookahead.symbol == T_SPACE
match(T_CRLF)
match(T_EOF)
return result
end
end
end
end
```
Step to reproduce: (require an horrible server :))
```ruby
imap_connexion = Net::IMAP.new(localhost, 993, true, nil, false)
imap_connexion.status('INBOX', ["UIDNEXT", "UIDVALIDITY"])
```
Then the server should reply with:
"* STATUS INBOX (UIDNEXT 1 UIDVALIDITY 1585372) \r\n"
And the bug occurs because we have a space at the end of the line which is not in the RFC, but as usual Microsoft makes its own RFC...
If you have any questions, suggestions just ask, if I can help.
--
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>