[#84867] [Ruby trunk Bug#14357] thread_safe tests suite segfaults — v.ondruch@...
Issue #14357 has been reported by vo.x (Vit Ondruch).
11 messages
2018/01/15
[#85364] Re: [Ruby trunk Bug#14357] thread_safe tests suite segfaults
— Eric Wong <normalperson@...>
2018/02/03
v.ondruch@tiscali.cz wrote:
[#85368] Re: [Ruby trunk Bug#14357] thread_safe tests suite segfaults
— Eric Wong <normalperson@...>
2018/02/03
Eric Wong wrote:
[#85442] Re: [Ruby trunk Bug#14357] thread_safe tests suite segfaults
— Eric Wong <normalperson@...>
2018/02/06
Eric Wong <normalperson@yhbt.net> wrote:
[#85451] Re: [Ruby trunk Bug#14357] thread_safe tests suite segfaults
— Vladimir Makarov <vmakarov@...>
2018/02/06
On 02/06/2018 05:00 AM, Eric Wong wrote:
[#84874] [Ruby trunk Bug#14360] Regression CSV#open method for writing from Ruby 2.4.3 to 2.5.0 — shevegen@...
Issue #14360 has been updated by shevegen (Robert A. Heiler).
3 messages
2018/01/15
[#84980] [Ruby trunk Feature#13618][Assigned] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid — hsbt@...
Issue #13618 has been updated by hsbt (Hiroshi SHIBATA).
10 messages
2018/01/23
[#85012] Re: [Ruby trunk Feature#13618][Assigned] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
— Eric Wong <normalperson@...>
2018/01/23
hsbt@ruby-lang.org wrote:
[#85081] Re: [Ruby trunk Feature#13618][Assigned] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
— Eric Wong <normalperson@...>
2018/01/24
Eric Wong <normalperson@yhbt.net> wrote:
[#85082] Re: [Ruby trunk Feature#13618][Assigned] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
— Eric Wong <normalperson@...>
2018/01/24
> Thinking about this even more; I don't think it's possible to
[#85088] [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid — danieldasilvaferreira@...
Issue #13618 has been updated by dsferreira (Daniel Ferreira).
3 messages
2018/01/25
[#85107] [Ruby trunk Misc#14222] Mutex.lock is not safe inside signal handler: what is? — eregontp@...
Issue #14222 has been updated by Eregon (Benoit Daloze).
3 messages
2018/01/25
[#85136] Re: [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid — Eric Wong <normalperson@...>
samuel@oriontransfer.org wrote:
3 messages
2018/01/26
[ruby-core:85292] [Ruby trunk Bug#13649] Net::IMAP doesn't support response from a Microsoft Exchange server (which is not compliant with RFC standards)
From:
usa@...
Date:
2018-01-31 11:26:13 UTC
List:
ruby-core #85292
Issue #13649 has been updated by usa (Usaku NAKAMURA).
Backport changed from 2.2: WONTFIX, 2.3: REQUIRED, 2.4: DONE to 2.2: WONTFIX, 2.3: DONE, 2.4: DONE
ruby_2_3 r62131 merged revision(s) 59372.
----------------------------------------
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#change-70073
* Author: keysen (J辿r辿my Carlier)
* Status: Closed
* Priority: Normal
* Assignee: shugo (Shugo Maeda)
* Target version:
* ruby -v: 2.3.1
* Backport: 2.2: WONTFIX, 2.3: DONE, 2.4: DONE
----------------------------------------
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>