[#97086] [Ruby master Bug#16612] Enumerator::ArithmeticSequence#last with float range produces incorrect value — muraken@...
Issue #16612 has been updated by mrkn (Kenta Murata).
4 messages
2020/02/07
[#97095] [PATCH] Modify shebang of libexec/y2racc and libexec/racc2y. — Wang Mingyu <wangmy@...>
change /usr/local/bin/ruby to /usr/bin/env ruby.
3 messages
2020/02/08
[#97307] [Ruby master Feature#16663] Add block or filtered forms of Kernel#caller to allow early bail-out — headius@...
Issue #16663 has been reported by headius (Charles Nutter).
29 messages
2020/02/28
[ruby-core:97046] [Ruby master Misc#16515] one of authoritative name server of ruby-lang.org "pichu.netlab.jp" not responding DNS query
From:
shugo@...
Date:
2020-02-03 07:17:24 UTC
List:
ruby-core #97046
Issue #16515 has been updated by shugo (Shugo Maeda). Status changed from Open to Closed Sorry for the delay. We have changed the secondary DNS server of ruby-lang.org to ns.tokyo.netlab.jp. ---------------------------------------- Misc #16515: one of authoritative name server of ruby-lang.org "pichu.netlab.jp" not responding DNS query https://bugs.ruby-lang.org/issues/16515#change-84140 * Author: [email protected] (Koichiro Iwao) * Status: Closed * Priority: Normal ---------------------------------------- I'm reporting issue about ruby-lang.org network infrastructure. If here's not the place to report such issues, I'd appreciate if let me know appropriate place to report such issues. I've notified one of name servers of ruby-lang.org seems not working properly. Two name servers are registered as authority name servers of ruby-lang.org. * support.netlab.jp * pichu.netlab.jp The latter one `pichu.netlab.jp` is tardy in its DNS response. It often cause timeouts. ``` % drill docs.ruby-lang.org @pichu.netlab.jp Error: error sending query: Could not send or receive, because of network error % drill docs.ruby-lang.org @pichu.netlab.jp Error: error sending query: Could not send or receive, because of network error % drill docs.ruby-lang.org @pichu.netlab.jp Error: error sending query: Could not send or receive, because of network error ``` The other one `support.netlab.jp` seems to be working fine. ``` % drill docs.ruby-lang.org @support.netlab.jp ;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 31189 ;; flags: qr aa rd ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;; docs.ruby-lang.org. IN A ;; ANSWER SECTION: docs.ruby-lang.org. 600 IN CNAME dualstack.m.shared.global.fastly.net. ;; AUTHORITY SECTION: ;; ADDITIONAL SECTION: ;; Query time: 62 msec ;; SERVER: 153.246.96.163 ;; WHEN: Fri Jan 17 18:48:47 2020 ;; MSG SIZE rcvd: 86 ``` This causes faliure in name resolution when my local dns cache is expired. Specifically, name resolution of `docs.ruby-lang.org` will fail at 50% chance every 600 minutes. I've performed above `drill` test via 3 different ISPs and got the same result. So I suppose this is your NaCl's name server side issue. Thanks, -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:[email protected]?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>