nobu (Nobuyoshi Nakada) wrote in #note-2: > Seems same as #19292. In #19292 it is said that 3.0 and 2.7 don't need while they do.akostadinov (Aleksandar Kostadinov)
This issue happens since Ruby 2.7, since `Z` and `UTC` are allowed for a zone. ``` ruby [1] pry(main)> Time.new(2023, 1,3,0,0,0,"UTC").wday => 7 [2] pry(main)> Time.new(2023, 1,3,0,0,0,"Z").wday => 7 ``` This also breaks all w...akostadinov (Aleksandar Kostadinov)
StringScanner#matched_size seems to be byte oriented. But that is not documented. Better be documented to avoid confusion. [1] pry(main)> ss = StringScanner.new([1024].pack("U*")) [3] pry(main)> ss.skip_until(/./) [4] pry(main)> ss....akostadinov (Aleksandar Kostadinov)
Hello, I am right now having difficulties to understand why one thread I have is dead. Seems been killed by something (rails/puma). But there is no way I can see to understand what and why did it. That's why I'm proposing a new featur...akostadinov (Aleksandar Kostadinov)
It would be beneficial if one could do: my_method(**hash_with_string_keys) This for example you can read a hash from MongoDB and pass it as parameters to your method without additional processing. For example to implement per...akostadinov (Aleksandar Kostadinov)
"If offset is not given, the file is truncated. Otherwise, it is not truncated." The above is NOT true when 'a' mode is used. I'd suggest to clarify in documentation that offset is usually 0 if not specified but in 'a' mode it is at e...akostadinov (Aleksandar Kostadinov)
e.g. if you do xmlrpc_client.http.ca_file = @options[:ca_file] Then `xmlrpc_client.call(...)` will work but not the following: xmlrpc_client.call_async(...) At the moment I'm using a monkey patch workaround like ...akostadinov (Aleksandar Kostadinov)
In relation to #8461 It's now easy to set SSL options like `ca_path` but doing an `_async` call creates a new connection without these options present. I think SSL options should be configurable in the xmlrpc client itself and it pas...akostadinov (Aleksandar Kostadinov)
I rather think it is actually a bug because it hides very important information from the user. It's like showing your error cut in half or on more pieces. It's just confusing to use `causes` this way. So I call it a bug as the initial fe...akostadinov (Aleksandar Kostadinov)
Hello, errors with `cause` are an important and very useful feature for debugging. It seems though default reporting is not showing the `cause` and nested causes to user. Here's a test file: ~~~ruby raise "GAHGAH" rescue raise "error...akostadinov (Aleksandar Kostadinov)
akostadinov (Aleksandar Kostadinov)03:06 PM Ruby Bug #19295: Time#wday returns 7