[#103241] [Ruby master Bug#17777] 2.6.7 fails to build on macOS: implicit declaration of function 'rb_native_mutex_destroy' is invalid in C99 — eregontp@...
Issue #17777 has been reported by Eregon (Benoit Daloze).
17 messages
2021/04/05
[#103305] [Ruby master Feature#17785] Allow named parameters to be keywords — marcandre-ruby-core@...
Issue #17785 has been reported by marcandre (Marc-Andre Lafortune).
21 messages
2021/04/08
[#103342] [Ruby master Feature#17790] Have a way to clear a String without resetting its capacity — jean.boussier@...
Issue #17790 has been reported by byroot (Jean Boussier).
14 messages
2021/04/09
[#103388] [ANN] Multi-factor Authentication of bugs.ruby-lang.org — SHIBATA Hiroshi <hsbt@...>
Hello,
5 messages
2021/04/12
[#103414] Re: [ANN] Multi-factor Authentication of bugs.ruby-lang.org
— Martin J. Dürst <duerst@...>
2021/04/13
Is there a way to use this multi-factor authentication for (like me)
[#103547] List of CI sites to check — Martin J. Dürst <duerst@...>
Hello everybody,
4 messages
2021/04/22
[#103596] [Ruby master Feature#17830] Add Integer#previous and Integer#prev — rafasoaresms@...
Issue #17830 has been reported by rafasoares (Rafael Soares).
9 messages
2021/04/26
[ruby-core:103559] [Ruby master Bug#17820] `Errno::EINVAL` from `Process.kill` with available signal on Windows
From:
alex.wayfer@...
Date:
2021-04-22 19:40:21 UTC
List:
ruby-core #103559
Issue #17820 has been updated by AlexWayfer (Alexander Popov). xtkoba (Tee KOBAYASHI) wrote in #note-1: > This seems to be a well-known restriction. Only `KILL` (`9`) works for Windows. > > https://blog.simplificator.com/2016/01/18/how-to-kill-processes-on-windows-using-ruby/ Yes, I found this article, and wanted to add the link to the issue description, but didn't find an ability to edit the description. So, about this article and behavior: 1. This behavior doesn't seem "well-known restriction", there is no explanation or details (why?) in the article or somewhere. 2. Article highlights that even `KILL` signal works incorrect on Windows (but I guess it should be a separate issue). 3. Article suggests system command instead of Ruby method. 4. There is should be consistency and understandable behavior in Ruby, even in Windows (as I know, Ruby should works on Windows). So, either `Signal.list` should return only `KILL` and something else working, or `Process.kill` should works with `TERM` and other signals. Anyway, `Signal.list` output and `Process.kill` input should be synced. ---------------------------------------- Bug #17820: `Errno::EINVAL` from `Process.kill` with available signal on Windows https://bugs.ruby-lang.org/issues/17820#change-91660 * Author: AlexWayfer (Alexander Popov) * Status: Open * Priority: Normal * ruby -v: ruby 3.0.1p64 (2021-04-05 revision 0fb782ee38) [x64-mingw32] * Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN ---------------------------------------- Hello. I've installed Ruby on Windows via [Chocolatey](https://community.chocolatey.org/packages/ruby). I receive `Errno::EINVAL` from `Process.kill` with almost every signal. Only `0` seems working. `TERM` (`15`), `INT` (`2`) — don't. Although they're in `Signal.list` output:  ---Files-------------------------------- clipboard-202104222051-b64xq.png (63.9 KB) -- 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>