Activity
From 06/22/2022 to 06/28/2022
06/28/2022
-
06:25 PM Revision a16de43f (git): [rubygems/rubygems] Add `gem env user_gemhome` and `gem env user_gemdir`
- https://github.com/rubygems/rubygems/commit/14d3f80df6
-
- https://github.com/rubygems/rubygems/commit/5ab8aa2a45
-
- https://github.com/rubygems/rubygems/commit/6d841ccbd4
-
- I think `gem env home` and `gem env path` read very nice.
https://github.com/rubygems/rubygems/commit/b89da79456 -
03:39 PM Revision 59273ff6 (git): [ruby/fileutils] [DOC] Changes to examples (https://github.com/ruby/fileutils/pull/96)
- * Changes to examples
https://github.com/ruby/fileutils/commit/346a71b2cb - 03:23 PM Revision 364b5e75 (git): * 2022-06-29 [ci skip]
-
03:23 PM Revision a415a3de (git): [ruby/irb] Properly reset USE_COLORIZE after changing it in tests
- Some context tests assigns USE_COLORIZE to false and never change it
back. This can potentially affect other tests' result as the default
should be nil (activated) instead.
https://github.com/ruby/irb/commit/986eb16ece - 02:31 PM Revision 69337a65 (git): [rubygems/rubygems] Fix test_install_location_extra_slash on alpine
- Under POSIX behavior of leading // is implementation defined. Musl does
preserve it in realpath, glibc does not. That means the test was failing
when executed on alpine linux. Original issue #508 was about // in the
path, not about leadi... -
02:10 PM Revision ca85bd81 (git): [ci skip] Improve man page docs around --dump options
-
- ruby/debug uses `irb/color` selectively:
https://github.com/ruby/debug/blob/0ac22406bb8f65bc76f9f5576a00c729cac693af/lib/debug/color.rb#L4
And in that case, `IRB.conf` won't be defined. So Color.colorable? needs
to consider that.
This ... -
- * Use colorable: argument as the only coloring control
* Centalize color controling logic at Color.colorable?
There are 2 requirements for coloring output:
1. It's supported on the platform
2. The user wants it: `IRB.conf[:USE_COLORIZ... -
01:21 PM Feature #18885 (Closed): End of boot advisory API for RubyVM
- ### Context
Many optimizations in the Ruby VM rely on lazily computed caches: Strings coderange, constant caches, method caches, etc etc.
As such even without JIT, some operations need a bit of a warm up, and might be flushed if new ... -
12:24 PM Revision 5ccdcd81 (git): [ruby/rdoc] Remove dead code
- https://github.com/ruby/rdoc/commit/f727854bd5
-
- So I tried adding a `frame` before the ISeq is compiled: https://github.com/ruby/ruby/pull/5998
It somewhat works for regular `require` but:
- It's awkward to put an uncompiled ISeq in the stack, there is even an `assert` to prev... -
-
- https://github.com/ruby/rdoc/commit/854b370763
-
07:25 AM Bug #18883: parse.y: trailing comma cannot coexist with star
- As far as I understand, trailing comma is an equivalent of `*_` (unpack the rest and drop it):
```ruby
x, = [1, 2, 3]
# is the same as
x, *_ = [1, 2, 3]
# put 1 in x, ignore the rest, it is the shortest way to do it
```
So the fac... -
03:44 AM Bug #18883 (Rejected): parse.y: trailing comma cannot coexist with star
- The following code is a syntax error:
```ruby
*x, y, = 1, 2 # syntax error, unexpected '='
```
although the following:
```ruby
x, y = 1, 2 # OK
x, y, = 1, 2 # OK
*x, y = 1, 2 # OK
# *x, y, = 1, 2
```
In my understandi... -
- https://github.com/ruby/rdoc/commit/c051eb90d1
-
- Initialization depending on VM is separated.
https://github.com/ruby/rdoc/commit/030d10fccd -
- There is a corner case where `if` inconsistently causes a syntax error:
```ruby
# syntax error, unexpected `if' modifier
class if 1; Object end::Object
end
```
compare the following:
```ruby
# Parses
module if 1; Object e... -
- > Is there a more descriptive error message, or is `SyntaxError` the only output provided?
This is the actual error message:
```
% ruby -e 'Foo::Bar {}'
-e:1: syntax error, unexpected '{'
Foo::Bar {}
``` -
- You can use `File.binread`.
-
12:17 AM Bug #18876 (Closed): OpenSSL fails to autoload in --with-static-linked-ext builds
06/27/2022
-
04:48 PM Bug #18878: parse.y: Foo::Bar {} is inconsistently rejected
- Is there a more descriptive error message, or is `SyntaxError` the only output provided?
-
04:40 PM Bug #18882: File.read cuts off a text file with special characters when reading it on MS Windows
- Huh, Ruby might be exposing a C runtime behavior here.
Assuming I'm reading the call graph right, and there
isn't some Ruby level defaulting going on, a `File.read()`
with just a path and no mode maps to a call to `_wopen()`
with neither... -
03:10 PM Bug #18882: File.read cuts off a text file with special characters when reading it on MS Windows
- magynhard (Matthäus Johannes Beyrle) wrote in #note-7:
> alanwu (Alan Wu) wrote in #note-5:
> ...
There is no way to throw an error in this case, because there’s no error condition. `0x1a` is read just fine on non-Windows systems in "t... -
02:46 PM Bug #18882: File.read cuts off a text file with special characters when reading it on MS Windows
- alanwu (Alan Wu) wrote in #note-5:
> `File.read` (actually `IO.read`) interprets the file based on the
> ...
Added it to the script, both have the same output in this case:
```
[#<Encoding:UTF-8>, #<Encoding:UTF-8>]
```
But as ... -
- alanwu (Alan Wu) wrote in #note-5:
> `File.read` (actually `IO.read`) interprets the file based on the
> ...
This is true, but not the source of the problem here. See https://docs.microsoft.com/en-us/cpp/c-runtime-library/text-and-bina... -
- `File.read` (actually `IO.read`) interprets the file based on the
external encoding, which is a function of the platform and the environment.
If you put a `p [content.encoding, ::Encoding.default_external]` in your script
I think you... -
02:14 PM Bug #18882: File.read cuts off a text file with special characters when reading it on MS Windows
- > it behaves correctly on Linux, i expect not to need to use binary mode
I think binary mode is a no-op on Linux though? Different systems behave differently - Ruby can't completely remove those differences when you're doing IO. -
- This is Windows-specific, and there is not an error condition to check for reporting on this.
The distinction between "binary" and "text" mode is simply the way that DOS works (yes, that’s how old this behaviour is), and the definition ... -
- chrisseaton (Chris Seaton) wrote in #note-1:
> Don't you need to use binary mode to read these characters?
As it is a text file and reading from it behaves correctly on Linux, i expect not to need to use binary mode.
Otherwise, sh... -
- Don't you need to use binary mode to read these characters?
-
- When using File.read to read a text file (in this case a javascript file) with special characters, the content is cut off at special characters.
It occurs only when running ruby on Windows, tried several versions, including the latest... - 04:26 PM Revision aba804ef (git): * 2022-06-28 [ci skip]
- 04:26 PM Revision 5da31b62 (git): Make sure string-operation assertions happen inside a method to be sure YJIT will JIT them.
- 04:25 PM Revision 0fab06f3 (git): Separate Type::String into Type::CString and Type::TString.
- Also slightly broaden the cases where << on two strings will generate
specialised code rather than a plain method call. -
- When running a command with the `--verbose` flag that ends up raising a
`BundlerError`, Bundler will unnecessarily print the error twice.
This commit fixes the issue by removing the duplicate logging.
https://github.com/rubygems/rubyge... - 01:28 PM Revision 8c6c3e30 (git): [ruby/reline] Enable to change the background color of dialogs. (https://github.com/ruby/reline/pull/413)
- https://github.com/ruby/reline/commit/bd49537964
-
-
- Not to generate .dSYM directories by MJIT runs, which are left in
large numbers after each test. -
- Show an absolute path instead of an unhelpful relative path.
https://github.com/rubygems/rubygems/commit/f1eed36e2f -
06:59 AM Bug #18876: OpenSSL fails to autoload in --with-static-linked-ext builds
- i install cocoapods succeed, tks.
so i only need update opessl.rb file in `destroot/bundle/lib/ruby/site_ruby/3.1.0/rubygems/` when finished `update_rubygems`
-
- Try the patch I posted on:
/Users/didi/Documents/CocoaPods-app/destroot/bundle/lib/ruby/site_ruby/3.1.0/rubygems/openssl.rb
After `update_rubygems`. The update probably reverts the patch against the bundled version.
You can ch... -
- and [11:01:21] [rubygems-update-3.3.15] Patching: destroot/bundle/bin/gem is replace `#!/Users/didi/Documents/CocoaPods-app/destroot/bundle/bin/ruby` by #!/usr/bin/env ruby.
-
- ruby version changed to 3.1.2 still error ~
Here is the file I refer to, https://github.com/CocoaPods/CocoaPods-app/blob/master/Rakefile.
---
here is my rake file, step by step execution command.
``` shell
[10:47:51] [pkg-c... -
- I had some [issues](https://github.com/ruby/openssl/pull/520) building OpenSSL
and the Ruby wrapper, but I was able to reproduce this problem.
RubyGems sets an `autoload` for OpenSSL and then immediately triggers it with a
`defined?... -
04:00 AM Revision 232e2f59 (git): Skip TupleSpaceProxyTest on MINGW64 too
- It wasn't specific to UCRT64
https://github.com/ruby/ruby/runs/7062992464 -
12:28 AM Bug #14246: Inconsistent C source code indentation
- ioquatix (Samuel Williams) wrote in #note-16:
> Does this policy apply to the formatting of default gems too?
I don't think so. One good thing about splitting things into gems is they can have their own policies (release timing etc.... -
- Not looking at the implementation but sounds like an issue of Linux side to me. The error message seems intentional.
06/26/2022
-
07:39 PM Revision c3eb0437 (git): Fix Process.clock_gettime specs on OpenBSD
-
04:35 PM Bug #18881 (Rejected): IO#read_nonblock raises IOError when called following buffered character IO
- The following example code works as expected on Linux but raises an `IOError` on Windows:
``` ruby
r, w = IO.pipe
w.write("foobar")
c = r.getc
r.ungetc(c)
r.read_nonblock(3)
```
The error message is:
```
IOError: byte ori... -
- When passing an invalid number of bytes to read, such as `-1` , to `IO#sysread` on Linux, an `ArgumentError` is raised. On Windows `Errno::EINVAL` is raised instead.
``` ruby
r, w = IO.pipe
r.sysread(-1)
```
This raises `Argume... -
- Applied in changeset commit:git|fc8020c68eb9f640185a1bce322eba6605bde151.
----------
[Bug #18879] Fix macOS version detections
macOS's AvailabilityMacros.h does not contain macros for future
versions. If a version macro is not defined... -
01:19 PM Bug #18879 (Closed): missing linker flag "-framework Security" for macOS 10.7 .. 10.9
- it looks target OS version detection in ./configure fails. (10.7 <= ver < 10.10)
macOS's AvailabilityMacros.h does not contain macros for future versions.
a version number to compare with "MAC_OS_X_VERSION_MIN_REQUIRED" should be a n... - 04:09 PM Revision 63134551 (git): * 2022-06-27 [ci skip]
-
- macOS's AvailabilityMacros.h does not contain macros for future
versions. If a version macro is not defined, consider only earlier
versions to be targeted. -
- New test failures on MINGW appeared after
c2e37c8ff7da395f33fae546d9ae9e2408fc9236.
1) Error:
Rinda::TupleSpaceProxyTest#test_00_template:
NoMethodError: undefined method `stop_service' for nil:NilClass
D:/a/ruby/r... -
- The following source doesn't parse:
```ruby
Foo::Bar {}
```
despite the following:
```ruby
bar # local variable or method call
Bar # constant
bar() # method call
Bar() # method call
bar... -
- The following source inconsistently parses:
```ruby
x = \ 42
```
though this one not:
```ruby
\ 42
```
nor:
```ruby
x = \(tab) 42
```
-
12:50 PM Revision d3d5ef0c (git): Update to ruby/spec@ab32a1a
-
-
-
- YJIT_BUILD is more relevant outside of YJIT.
-
- As you all know, MinGW UCRT64 CI has randomly got stuck despite its
"Finished tests" output.
Looking at the logs closely, it seems like all of the recent such
reproductions end with the following output:
```
Retrying hung up testcase... -
- Fix https://github.com/ruby/irb/pull/353
https://github.com/ruby/irb/commit/7db93f9326 -
- https://github.com/ruby/irb/commit/e024ab716b
- 05:40 AM Revision e0bfdb23 (git): [ruby/irb] Ensure stdout is a TTY before calling winsize
- When outputting a (possibly truncated) value, IRB will query the
window size. However, if IRB was piped to another process, stdout
will no longer be a TTY and will not support the `winsize` method.
This fix ensure that stdout is a TTY.... -
05:17 AM Revision 846a6bb6 (git): [DOC] Fix a typo [ci skip]
-
- When testing under the ruby/ruby setup, mkmf.rb needs to the `$extout`
global variable set properly.
This is because, in this particular case, the `ruby.h` header needed to
compile extensions is constructed from
`$(extout)/include($arch... - 02:15 AM Revision 967624bc (git): * 2022-06-26 [ci skip]
- 02:15 AM Revision 56809537 (git): [rubygems/rubygems] Clean up temporary directory after generate_index --update
- While generate_index did clean up temporary directory, when running with
--update flag, that did not happen and the temporary directory was left
behind.
This commit fixes that and modifies tests in order to make sure this is
not reintro...
06/25/2022
-
-
09:21 AM Feature #18566: Merge `io-wait` and `io-nonblock` gems into core IO
- We've moved `#wait`, `#wait_readable`, `#wait_writable`, `#wait_priority` into core.
I'll make a PR for `io-nonblock` gem and we can discuss in more detail. -
- This is now completed.
- 09:17 AM Revision d2166c09 (git): Copy `IO#wait*` methods from `io-wait` gem to `io.c`.
- 09:11 AM Revision c0b51240 (git): Update default gems list at 50e13870bffa3561be13faa31c3fcb [ci skip]
-
- https://github.com/ruby/io-wait/commit/0fa6e3f7ba
-
- Fix https://github.com/ruby/io-wait/pull/11
https://github.com/ruby/io-wait/commit/845f9a1f55 - 08:12 AM Revision d281347a (git): [ruby/io-wait] Fix usage of `assert_raises` -> `assert_raise`. (https://github.com/ruby/io-wait/pull/20)
- https://github.com/ruby/io-wait/commit/c5c6abbb5c
- 07:22 AM Revision 7e687624 (git): * remove trailing spaces. [ci skip]
- 07:21 AM Revision f9c8d808 (git): [ruby/io-wait] Don't add `IO#wait*` methods when `RUBY_IO_WAIT_METHODS` is defined by Ruby. (https://github.com/ruby/io-wait/pull/19)
- * Fix return value compatibility with Ruby 2.x.
* Don't add `IO#wait*` methods in Ruby 3.2+.
https://github.com/ruby/io-wait/commit/54c504d089
06/24/2022
-
11:29 PM Revision 2b4a1ad5 (git): Fix a variable name typo in the docs
-
- 10:04 PM Revision 362d6d9a (git): * 2022-06-25 [ci skip]
-
10:04 PM Revision 87e2e3f3 (git): Dump inline storage partition information to binary format
- ISeqs loaded from binary were breaking because the storage partition
calculation had bugs in it. Specifically it couldn't take in to account
the case when inline storage was overallocated (for example when we
allocate inline storage for... -
07:21 AM Feature #18773: deconstruct to receive a range
- As a designer of pattern matching, I also understand your motivation.
However, I have the following concerns in addition to the ones mame pointed out.
* In the current implementation, when a pattern match fails in one-line pattern ma... -
- Does this policy apply to the formatting of default gems too?
-
- `bundle-env`'s ruby is new installed , not my local version
-
- my local version is 3.1.1 too, and run `ruby -v` , got `ruby 3.1.1p18 (2022-02-18 revision 53f5fc4236) [x86_64-darwin20]`.
and i tried some different version with add `RUBYOPT=-v` and `RUBYOPT=-vd` to make a comparison.
----
with 3.... -
-
- The test in [1] was removed because it stopped working when we limited
the power of Kernel#binding in [2]. However, the underlying issue could
still be reproduced using blocks. Add back a regression test.
I tested the test by commenting...
06/23/2022
-
- If the iseqs don't have any objects in them that need marking, then
immediately free the bitmap buffer -
- We can avoid allocating a bitmap when the number of elements in the iseq
is fewer than the size of an iseq_bits_t -
- YJIT is now a build-time opt-in so on platforms that YJIT could support
it could still be unavailable due to user discretion. Use MJIT for --jit
and don't display YJIT related command line options in --help when YJIT
is not included in t... -
- Applied in changeset commit:git|e23540e5666664e23f2adecdc2cc591f3ff6fe2f.
----------
Speed up ISeq by marking via bitmaps and IC rearranging
This commit adds a bitfield to the iseq body that stores offsets inside
the iseq buffer that c... - 09:01 PM Revision 1ccdb1a2 (git): Update vm_core.h
- Co-authored-by: Tomás Coêlho <36938811+tomascco@users.noreply.github.com>
-
- This commit adds a bitfield to the iseq body that stores offsets inside
the iseq buffer that contain values we need to mark. We can use this
bitfield to mark objects instead of disassembling the instructions.
This commit also groups in... - 08:51 PM Revision 6fd9cb80 (git): * 2022-06-24 [ci skip]
-
08:50 PM Revision 962a3247 (git): Correct documentation for protected methods [ci skip]
-
-
- Since `bundle-env ruby -ropenssl` works, I suspect it has something to
do with `--env-shebang`. Maybe the `gem` command isn't running with
the Ruby you want. Try running `RUBYOPT=-v bundle-env gem` and
comparing that with `ruby -v` (w... -
- i try use ruby + gem in my macos app with .a framework, i need install ruby in a custom location.
so i make & make install openssl with this configure:
``` shell
/usr/bin/perl Configure --prefix="......./local/dependencies" no-shared ... -
- * Use PRIxSIZE instead of "z"
* Fix sign-compare warning
* Suppress unused-but-set-variable warning -
-
-
-
- https://github.com/rubygems/rubygems/commit/4d0d7b3c97
-
- This is a regression from https://github.com/rubygems/rubygems/commit/cf749f8ffabd. The
funny thing is that we have a spec for this feature, so it was unclear
how we regressed here. It turns out there was a bug in one of our
negative mat... - 07:45 AM Revision 0b11eac2 (git): * 2022-06-23 [ci skip]
-
-
- On platforms not having `typeof`, `ccan_container_off_var()` macro
subtracts the pointer variable from the member address pointed by that
variable.
06/22/2022
-
- A large percentage of major GC time is spent marking instruction sequence objects. This PR aims to speed up major GC by speeding up marking instruction sequence objects.
## Marking ISeq objects
Today we have to disassemble instruc... -
04:10 PM Feature #17326: Add Kernel#must! to the standard library
- I would rather have ruby use the type system to check monad type and provide syntactic sugar for monad method. Much rather have a Monad Result type or Option type that short circuits with None or Result on nil but provides fast syntacti...
-
- Applied in changeset commit:git|744d17ff6c33b09334508e8110007ea2a82252f5.
----------
Fix infinite loop when b_return TracePoint throws
Previously, we didn't pop the frame that runs the TracePoint hook for
b_return events for blocks run... -
- Previously, we didn't pop the frame that runs the TracePoint hook for
b_return events for blocks running as methods (bmethods). In case the
hook raises, that formed an infinite loop during stack unwinding in
hook_before_rewind().
[Bug #... -
- Now some entries need multiple variables for customization, and only
one environment variable per entry is not enough.
To solve it, dccfff943c3e has introduced overriding variables by `env`
key for each entries.
This commit uses `env` ke... -
07:58 AM Bug #18061: Execshield test: libruby.so.N.N.N: FAIL: property-note test because no .note.gnu.property section found
- I got useful info from the helpful annocheck upstream maintainer to fix the annocheck gaps and pie tests.
Bug 29269 - annocheck: gaps test: question for the flag: -Wa,--generate-missing-build-notes=yes .
https://sourceware.org/bugzil... -
- I think the backport is to apply the 3 commits on the master branch in the chronological order below to a stable branch.
https://github.com/ruby/ruby/commit/52d42e702375446746164a0251e1a10bce813b78
https://github.com/ruby/ruby/commit/7... -
- ioquatix (Samuel Williams) wrote in #note-6:
> I've made a PR to move `wait`, `wait_readable`, `wait_writable`, `wait_priority` to `io.c` with some minor compatibility and documentation improvements.
> ...
This mixes the fix for compat... -
12:52 AM Feature #18655: Copy `IO#wait_readable`, `IO#wait_writable`, `IO#wait_priority` and `IO#wait` into core.
- If @nobu and @akr are OK, I am OK.
Matz.
- 04:40 AM Revision 812354ac (git): [rubygems/rubygems] Bundler: fix man page for bundle-add
- Follows up https://github.com/rubygems/bundler/pull/5610
Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
https://github.com/rubygems/rubygems/commit/0c4df2b8ca -
-
-
- If we are making an FCALL, we know we are calling a method on self. This
is the same check made for private method visibility, so it should also
guarantee we can call a protected method. -
01:16 AM Revision 87a560a0 (git): Add T_STRUCT to lldb inspect helper
-
-
-