[#102652] [Ruby master Bug#17664] Behavior of sockets changed in Ruby 3.0 to non-blocking — ciconia@...
Issue #17664 has been reported by ciconia (Sharon Rosner).
23 messages
2021/02/28
[ruby-core:102568] [Ruby master Bug#16338] gemspec stub EOF separators throw warning
From:
nobu@...
Date:
2021-02-22 11:51:34 UTC
List:
ruby-core #102568
Issue #16338 has been updated by nobu (Nobuyoshi Nakada). Backport changed from 2.5: UNKNOWN, 2.6: UNKNOWN to 2.5: DONTNEED, 2.6: DONTNEED, 2.7: DONTNEED, 3.0: DONTNEED It's commit:69ec3f70fab0c1c537c68fb135cc315181b1d750, and had been reverted already soon. ---------------------------------------- Bug #16338: gemspec stub EOF separators throw warning https://bugs.ruby-lang.org/issues/16338#change-90548 * Author: MSP-Greg (Greg L) * Status: Closed * Priority: Normal * Assignee: hsbt (Hiroshi SHIBATA) * ruby -v: ruby 2.7.0dev (2019-11-11T03:09:19Z master 6f9be8505d) [x64-mingw32] * Backport: 2.5: DONTNEED, 2.6: DONTNEED, 2.7: DONTNEED, 3.0: DONTNEED ---------------------------------------- Some recent commits generate a warning when comments contain EOF characters, and any extension gems that create more than one *.so file have EOF characters in the stub portion of the gemspec. I noticed it with ruby-loco logs when json is loaded. This may be intentional, but I hate seeing warning generated by files included with master. There are comments in RubyGems about it, but I didn't see a resolution. Also, I didn't look thru the CI logs here, and often RubyGems is disabled. (?) Please close if intentional... -- 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>