Activity
From 10/29/2023 to 11/04/2023
11/04/2023
-
05:14 PM Revision 368a1cb3 (git): Do not use non-ASCII chars in sources
- No encodings are guaranteed in C compilers, and other than UTF-8
encodings may be assumed in some platforms, e.g., CP932 on Windows
Japanese edition, and may result in compilation errors. -
-
05:01 PM Bug #19985: Confusing error message when nonexistent `Pathname` for `require`
- martinemde (Martin Emde) wrote in #note-8:
> rubygems has been accepting ducks for years for 99% of Rubyists.
During the years, I had already enough fights where Ruby upstream claimed that RubyGems are integral parts of Ruby and usin... -
04:04 PM Bug #19985: Confusing error message when nonexistent `Pathname` for `require`
- It seems like you’re suggesting that required features don’t use a path name based hierarchy for organization.
I’m guessing you’re thinking of pathnames as something strictly tied to the filesystem, but Pathname is a useful class for ... -
03:54 PM Revision 8ed733f8 (git): ast.rb: Fix bug for source of multibyte characters
- first_column and last_column return byte positions, but existing implementations
did not consider multibyte. -
-
- https://github.com/ruby/stringio/commit/4400bf3380
-
- https://github.com/ruby/stringio/commit/3f90a0d619
- 07:01 AM Revision 9106ac45 (git): Update bundled gems list as of 2023-11-04
-
05:18 AM Revision 9f95b6eb (git): Skip a test that is flaky with RJIT
- It's crashing inside the bug reporter after a crash, so not sure why
it's crashing. It's not really useful for maintaining RJIT to flag this
test failure, so let's just ignore it until we figure out why it fails.
https://github.com/ruby... -
11/03/2023
-
09:07 PM Revision 6e38076b (git): YJIT: implement two-step call threshold (#8839)
- * YJIT: implement two-step call threshold
Automatically switch call threshold to a larger value for
larger, production-sized apps, while still allowing smaller apps
and command-line programs to start with a lower threshold.
* Update yj... -
06:47 PM Revision 38bdb9d0 (git): YJIT: Delete some dead code and enable lints
- 06:00 PM Revision bc4d1c09 (git): Update default gems list at 5a132c78641c252a7b04ca8a5a493f [ci skip]
-
05:59 PM Revision 5a132c78 (git): Update prism to v0.17.1
- 05:53 PM Revision dd033024 (git): [ruby/prism] Always fully qualify types for RBIs and avoid using attributes
- https://github.com/ruby/prism/commit/0d0d039f8e
- 04:12 PM Revision 9d308ad4 (git): .travis.yml: Add a RubyGems issue ticket link.
- Add a RubyGems issue ticket link. The issue happend in Travis arm32 at once.
- 04:12 PM Revision d4045b06 (git): .travis.yml: Add Ruby and RubyGems version info.
- The version information is useful to report issues to Ruby and RubyGems
projects. -
- https://github.com/ruby/prism/commit/145a67d1c3
- 03:19 PM Revision fff7a3c8 (git): Update default gems list at c44c982c9332a2671d65d48273629f [ci skip]
-
03:19 PM Revision cdb410f6 (git): [PRISM] Fix stack consistency with Popped begin
- When a begin node is popped it only needs to putnil if that nil is going
to be the return value, otherwise it can successfully be optimised out. -
- https://github.com/ruby/prism/commit/61a306cd5c
-
03:04 PM Revision e010bf16 (git): Fix typo in variable.c
-
- 02:54 PM Revision e345bf31 (git): .travis.yml: s390x: Use GCC 11.4.0.
- Use GCC version 11.4.0 (gcc-11 package) instead of the default GCC 11.3.0 to
align with the GCC used in the RubyCI s390x server below.
```
$ /usr/bin/gcc --version
gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Copyright (C) 2021 Free Softwa... -
- https://github.com/ruby/prism/commit/fbb30216ca
-
- We were previously holding a type field on Comment to tell what
kind of comment it was. Instead, let's just use actual classes for
this.
https://github.com/ruby/prism/commit/e76830ca6e -
- This commit changes generic ivars to respect the capacity transition in
shapes rather than growing the capacity independently. -
-
- https://github.com/ruby/prism/commit/4f3a3e3ec1
-
- https://github.com/ruby/prism/commit/81a9b2817f
-
- https://github.com/ruby/prism/commit/13fa262669
-
- https://github.com/ruby/prism/commit/33cc75a4b7
-
- https://github.com/ruby/prism/commit/84229529d7
-
- https://github.com/ruby/prism/commit/4b538af20f
-
- https://github.com/ruby/prism/commit/5a2252e3ac
-
- https://github.com/ruby/prism/commit/f0aa8ad93b
-
- https://github.com/ruby/prism/commit/8582d372a3
-
- https://github.com/ruby/prism/commit/99e81619de
-
- I'm +1 on this proposal. Anything that makes the implicit block more explicit.
On the static analysis point, a static analyzer can't detect that without knowing if `raise` and `block_given?` are not overridden. With `&nil` it would be... - 12:56 PM Revision a43a52d4 (git): .travis.yml: Reduce the parallel job number.
- I think the "1+$(nproc)" is too much.
-
- Should I go back to RubyGems / Bundler and ask them to "break" my first example? Or is there any reason why RubyGems / Bundler should behave differently?
-
05:44 AM Bug #19985: Confusing error message when nonexistent `Pathname` for `require`
- martinemde (Martin Emde) wrote in #note-5:
> It is funny to me that you would say it’s not a path just because not all paths are valid. What else could it possibly be?
What the argument to `require` actually is is a feature name. Th... -
- It is funny to me that you would say it’s not a path just because not all paths are valid. What else could it possibly be?
Ruby docs for require:
> If the filename neither resolves to an absolute path nor starts with ‘./’ or ‘../’, the... -
11:47 AM Revision b92b9e1e (git): vm_getivar: assume the cached shape_id like have a common ancestor
- When an inline cache misses, it is very likely that the stale shape_id
and the current instance shape_id have a close common ancestor.
For example if the instance variable is sometimes frozen sometimes
not, one of the two shape will be ... - 11:39 AM Revision 0ae6a2a1 (git): .travis.yml: Disable ppc64le allow_failures.
- Now I expect that Travis ppc64le always passes without any random failures by
the commit 1f1b9b0942ec12dde1af8000f8cb84692904fccc that is
a workaround to pass the `test/rdoc/test_rdoc_generator_json_index.rb` in
Travis ppc64le case. -
-
- It was assuming only objects can be complex.
- 10:30 AM Revision 1f1b9b09 (git): [ruby/rdoc] test/rdoc/test_rdoc_generator_json_index.rb: pend in test_generate in ppc64le.
- We observed that this test randomly fails in the ruby/ruby Travis ppc64le case.
This commit is to pend the test_generate if the assertion for the generated
file's modified time fails in a ppc64le environment.
Note that I didn't use the ... -
- >> I suppose that the `./miniruby` (`/builddir/build/BUILD/ruby-3.3.0-a1e24ab484/miniruby`) should be used instead of the `./ruby` in the command `make test-bundler-parallel` above.
> ...
Actually, this is incorrect. From the log, it is... -
- jaruga (Jun Aruga) wrote in #note-1:
> > ```
> ...
I can assume it was change in Ruby build system. If I knew more, I'd submitted PR.
> In Fedora's RPM build, we build Ruby without setting `BASERUBY` (`HAVE_BASERUBY=no`) (without th... -
- Previously emitting a call node with an argument followed by another
node would cause the argument to be mistakenly omitted from the argument
list causing a stack underflow.
```
PRISM: **************************************************
... -
- Co-authored-by: Adam Hess <HParker@github.com>
-
- Wait for the worker thread to finish.
11/02/2023
-
10:45 PM Bug #19984: `make test-bundler-parallel` fails with ` --enable-shared`
- > ```
> ...
Maybe you know what triggered this issue. In Fedora's RPM build, we build Ruby without setting `BASERUBY` (`HAVE_BASERUBY=no`) (without the installed `ruby`). And I suppose that issue comes form this case.
Why don't you expl... -
- ~~~
+ ./configure --enable-shared
checking for ruby... false
... snip ...
config.status: creating Makefile
---
Configuration summary for ruby version 3.3.0
* Installation prefix: /usr/local
* exec prefix: ${pr... -
- If the required capacity would fit in an embded string,
returns one.
This can reduce malloc churn for code that use string buffers. -
- It's possible for us to parse a constant that is invalid in the
current encoding. To fix this, we wrap the intern function in an
rb_protect to ensure we always put a valid symbol into the AST.
https://github.com/ruby/prism/commit/e78398... -
08:46 PM Revision c6f5c646 (git): [PRISM] Fix popped for ForNode
-
-
-
-
-
-
-
-
-
-
-
- Unfortunately, 84dfa0fa5e451adb87beaf497165cb5a1bc93770 introduced
a bug where we were no longer testing the "popped" case because the
"; 1" meant to be appended to the source was no longer functioning
as intended.
This commit re-introd... -
-
- This commit changes class ivars to respect the capacity transition in
shapes rather than growing the capacity independently. -
- This commit makes every initial size pool shape a root shape and assigns
it a capacity of 0. -
-
03:44 PM Bug #19985: Confusing error message when nonexistent `Pathname` for `require`
- > That's not funny, it's expected, as load deals exclusively with paths, and require does not generally deal with paths.
Yeah, makes sense.
> ...
Makes sense. Then, probably, it is up to RubyGems to remove this false conversion. -
- zverok (Victor Shepelev) wrote in #note-2:
> Even funnier that bare `load` does support the convention:
> ...
That's not funny, it's expected, as `load` deals exclusively with paths, and `require` does not generally deal with paths. E... -
- Even funnier that bare `load` does support the convention:
```
$ ruby --disable-gems -r pathname -e "load Pathname.new('test')"
-e:1:in `load': cannot load such file -- test (LoadError)
``` -
- Actually, it seems kinda weird that Pathname doesn't have an implicit conversion to a String (`#to_str`).
OTOH, [Pathname#to_path](https://docs.ruby-lang.org/en/3.2/Pathname.html#method-i-to_path) docs seem to claim that having `#to_path... -
- It seems that RubyGems / Bundler `require` method overrides of accept `Pathname` as and argument
~~~
$ ruby -rpathname -e '
pa = Pathname.new("test")
require pa
'
<internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>... -
-
- There is a duplicated check for the object is too complex.
-
-
08:07 AM Feature #16476 (Closed): Socket.getaddrinfo cannot be interrupted by Timeout.timeout
- #19965 solved the problem, so I'll close it.
I completely forgot this ticket, but the concept (pthread_create on every call to getaddrinfo(3)) was the same as in #19965. Just for case, #19965 is a bit more elaborate:
* It works as ... -
06:48 AM Revision 42f368ea (git): Surpressing additional message if it missed to detect gem name
-
- https://github.com/ioquatix/bake/pull/15#issuecomment-1777985097
-
06:16 AM Revision 7523ede7 (git): Windows: Fix description of runtimes
- `mswin` platform links to `vcruntimeXXX.dll` but `mingw-ucrt` doesn't.
-
-
06:10 AM Revision 1925c6d5 (git): test/ripper: nest helper classes under TestRipper module
- Generic names like Node and NodeList should be namespaced properly.
-
-
-
-
-
- `rb_file_open_str` calls `FilePathValue`, and the converted result is
not used in this function.
11/01/2023
-
06:40 PM Revision d3ea9070 (git): YJIT: skip to_a in format_number (#8815)
- String#chars returns an array instead of an enumerator since Ruby 2.0.
-
-
- https://github.com/ruby/prism/commit/ec419422f8
-
-
-
- https://github.com/ruby/prism/commit/77d4056766
-
- https://github.com/ruby/prism/commit/e327449db6
-
- https://github.com/ruby/prism/commit/83f737ce17
-
- https://github.com/ruby/prism/commit/84e22c5581
-
- https://github.com/ruby/prism/commit/9c648ce615
-
- https://github.com/ruby/prism/commit/69323d3df4
-
- https://github.com/ruby/prism/commit/271f3bf628
-
- https://github.com/ruby/prism/commit/857f72e1f4
-
- https://github.com/ruby/prism/commit/e2e29bef2d
-
- https://github.com/ruby/prism/commit/16e0579044
-
- https://github.com/ruby/prism/commit/76af64eb21
-
- https://github.com/ruby/prism/commit/52a0d80a15
-
- https://github.com/ruby/prism/commit/26934263b7
-
- https://github.com/ruby/prism/commit/88336e7d9f
-
- https://github.com/ruby/prism/commit/97b3cc0af8
-
- https://github.com/ruby/prism/commit/ff1d2ec579
-
- https://github.com/ruby/prism/commit/bec5ca37a0
-
- https://github.com/ruby/prism/commit/2b6e661bbc
-
- https://github.com/ruby/prism/commit/dfdcc98a3c
-
- https://github.com/ruby/prism/commit/ca9a660f52
-
- https://github.com/ruby/prism/commit/085da4feb9
-
- https://github.com/ruby/prism/commit/3abd09c803
-
- https://github.com/ruby/prism/commit/c2b7724d91
-
- https://github.com/ruby/prism/commit/cfd4431c3e
-
- https://github.com/ruby/prism/commit/8062849d0d
-
- https://github.com/ruby/prism/commit/2a11bfee76
-
- https://github.com/ruby/prism/commit/e13f2e4590
-
-
03:33 PM Feature #19979: Allow methods to declare that they don't accept a block via `&nil`
- Eregon (Benoit Daloze) wrote in #note-7:
> A static analyzer could detect a `raise ... if block_given?` if at the start of a method/not under any other control flow.
I understand your position and respect it, but I can't help but fee... -
-
02:41 PM Bug #19983: Nested `*` seems incorrect
- Agreed, I think supporting `*` fully for blocks would be a good way to solve this.
If that's deemed not desirable, then I think such code should be SyntaxError to avoid confusion and make it clear what works and does not. -
- I honestly believe it would be more reasonable to allow anonymous argument handling for procs, too.
It would be consistent and clear, no special edge cases due to, say, code copying (yes, there would be edge cases to demonstrate "how ... -
- Right, maybe it should be SyntaxError only if there is a `*` used inside a lambda/proc body (as a value), where the lambda/proc declares a `*` parameter (like `def m(*); ->(*) { p(*) }; end`).
IOW when using `*` both in method and block ... -
- `->(*) {}` being a syntax error would break backward compatibility, since `->(*) {}` has always been allowed. It's not different from `->(foo, *, bar) {}`.
-
- If procs don't support `*` then `def m(*); ->(*) { p(*) }; end` should be SyntaxError.
It is incredibly confusing indeed that the `*` parameter in the method and lambda has completely different behavior here. -
- Procs don't support anonymous arguments (e.g. to pass them further), see #19370.
```ruby
->(*) { p(*) }.call(1)
# no anonymous rest parameter (SyntaxError)
```
So, the code is equivalent to
```ruby
def m(*); ->(_) { p(*) }; e... -
- I don't think you can forward arguments from lambdas at all, which is making this confusing.
``` ruby
->(*) { foo(*) }
# => (irb):1: no anonymous rest parameter (SyntaxError)
``` -
- ```
$ ruby -v -e 'def m(*); ->(*) { p(*) }; end; m(1).call(2)'
ruby 3.3.0dev (2023-10-30T09:27:06Z master 14fa5e39d7) [x86_64-linux]
1
```
But I would expect `2`.
Much like:
```
$ ruby -e 'def m(a); ->(a) { p(a) }; end; m(1... -
- https://github.com/ruby/prism/commit/c31f61e898
-
- Prior to this commit, KeywordParameterNode included both optional
and required keywords. With this commit, it is split in two, with
`OptionalKeywordParameterNode`s no longer having a value field.
https://github.com/ruby/prism/commit/890... -
- 02:29 PM Revision e3b4fe1b (git): thread_pthread.c: unbreak 10.5 Intel by restoring accidentally deleted macro
-
- `remove_shape_recursive` wasn't considering that if we run out of
shapes, it might have to transition to SHAPE_TOO_COMPLEX.
When this happens, we now return with an error and the caller
initiates the evacuation. -
- (Alternative to the above)
* [Feature #19370] Anonymous parameters for blocks?
* I argue that we should just allow that for consistency; the resulting behavior would be not more confusing than the regular variable shadowing. -
- * [Bug #19983] Nested * seems incorrect (eregon)
* `def m(*); ->(*) { p(*) }; end` is not SyntaxError but uses the "wrong" `*`.
* Could we make that SyntaxError, or could we support anonymous rest in blocks?
-
01:08 AM Misc #19925: DevMeeting-2023-11-07
- * [Feature #18551] Make Range#reverse_each to raise an exception if endless (kyanagi)
* I mentioned this issue for the last meeting, but it seems that it was missed.
* Since [Feature #18515] has been merged, could you please make a... -
- After considering some examples, I believe it would be more consistent to just allow anonymous parameters in blocks, without further restrictions.
The example of "confusing" example above:
```ruby
def test(*)
# ...
proc { |*... -
-
-
- As for `snprintf`, we avoid system provided implementations not to be affected by locales.
- 02:29 AM Revision a1e24ab4 (git): [rubygems/rubygems] avoid dependency on set
- it was a performance improvement only, but it causes failures in
unrelated tests
https://github.com/rubygems/rubygems/commit/b4149cb9bf - 02:29 AM Revision 836d9fe4 (git): [rubygems/rubygems] Add Bundler::Plugin.loaded? helper
- Useful if your plugin introduces new methods to the DSL, so that
Gemfiles can easily abort if the plugin hasn't loaded yet
https://github.com/rubygems/rubygems/commit/b733055c6e
10/31/2023
-
-
-
-
-
-
- Visual Studio 2013 is finally being EOL'd next April. (https://learn.microsoft.com/en-us/visualstudio/productinfo/vs-servicing#older-versions-of-visual-studio) Let's drop support for it after Ruby 3.3 is released.
If we bump the requi... -
-
- On 32-bit systems, we must store the shape ID in the gen_ivtbl to not
lose the shape. If we directly store the ST table into the generic
ivar table, then we lose the shape. This makes it impossible to
determine the shape of the object an... -
-
04:07 PM Revision 6f5e3780 (git): Fix "too complex" iv sets on generic ivar objects
- We weren't taking in to account that objects with generic IV tables
could go "too complex" in the IV set code. This commit takes that in to
account and also ensures FL_EXIVAR is set when a geniv object
transitions to "too complex"
Co-A... -
-
- There is a handful of call sites where we may transition to
OBJ_TOO_COMPLEX_SHAPE if we just ran out of shapes, but that
weren't handling it properly. -
- This commit implements compilation for the PostExeuctionNode by
using the ScopeNode to create child iseqs where appropriate. - 01:53 PM Revision b5d54fc1 (git): [rubygems/rubygems] Only remove bundler plugin gem when it's inside the cache
- https://github.com/rubygems/rubygems/commit/8d51390ca4
-
- 12:54 PM Revision 3801503f (git): [ruby/prism] Fix a possible malloc(0)
- https://github.com/ruby/prism/commit/fa108b8626
-
- https://github.com/ruby/prism/commit/6e5556dbdf
-
- ufuk (Ufuk Kayserilioglu) wrote in #note-6:
> A static analyzer will be able to consume a `&nil` annotation and act on it, but won't be able to do the same for implicit `raise ArgumentError` code.
A static analyzer could detect a `ra... - 11:14 AM Revision 322755a0 (git): [ruby/prism] Fix a possible null dereference
- https://github.com/ruby/prism/commit/7dbb8c7e3e
-
10:01 AM Revision d8a92455 (git): Add defined array node
-
-
-
08:49 AM Revision 51149f33 (git): Keep unused literal nodes
- For static analysis, it’s better to keep unused literal nodes.
If simply change `block_append` to fall through, both "unused literal ignored"
and "possibly useless use of a literal in void context" warnings
are shown for the same line. B... - 07:00 AM Revision eff59e93 (git): Update bundled gems list as of 2023-10-30
-
05:12 AM Revision d22767fd (git): Add a --disable-yjit job for Ubuntu CI
- Currently, we do not have an amd64 job that runs with YJIT disabled
and runs the full check task. Most amd64 jobs implicitly have YJIT
enabled, even though --enable-yjit was not specified. This makes it
easier to determine whether a pr... -
02:16 AM Feature #10602 (Closed): Support multithreaded profiling - Applied in changeset commit:git|4adf418be963b3554962b2f27057be81486c57d9.
----------
[Feature #10602] Add new API rb_profile_thread_frames()
Add a new API rb_profile_thread_frames(), which is essentialy a
per-thread version of rb_profi... - 02:16 AM Revision 4adf418b (git): [Feature #10602] Add new API rb_profile_thread_frames()
- Add a new API rb_profile_thread_frames(), which is essentialy a
per-thread version of rb_profile_frames().
While the original rb_profile_frames() always returns results about the
current active thread obtained by GET_EC(), this new API ... -
10/30/2023
-
-
- > Is this a frequent error?
I would not say that it is frequent but for the case where it happens the resulting behaviour is confusing and misleading. I have caught some instances in Shopify's code base, most of them in tests for mock... -
01:56 PM Feature #19979: Allow methods to declare that they don't accept a block via `&nil`
- > Is this a frequent error?
> ...
Personally I never saw such an error and can not recall having made
such an error either. I also never had a need to prevent passing of
blocks, but I also agree that there may be situations where on... -
- > Is this a frequent error?
I saw some, but most of them were about mistaking one method for another, or mis-guessing what the method should do without reading docs.
The example of the former is using `Time.freeze { some code }` in ... -
- Regarding #15554 I think that has the significant advantage that it does not require any changes in gems to be useful. It just automatically knows if a method accepts a block or not.
-
- > This leads to subtle user errors, where the author of some code assumes a method call uses a block, but the block passed to the method call is silently ignored.
Is this a frequent error?
I think the only times I saw it is due to confu... -
-
-
-
- Fixes ruby/prism#1648
-
-
06:22 PM Revision 85beca6e (git): [ruby/irb] Use IRB's own doc for doc dialog tests
- (https://github.com/ruby/irb/pull/743)
* Use IRB's own doc for doc dialog tests
* Run doc dialog tests for older Rubies too
* Remove unnecessary CI setups
https://github.com/ruby/irb/commit/97a2b86f0a - 04:37 PM Revision 83911002 (git): Update default gems list at b413760d66e4de5670148b01a6a207 [ci skip]
-
-
- 04:21 PM Revision 674db715 (git): [ruby/rdoc] test/rdoc/test_rdoc_generator_json_index.rb: Use assert_equal instead of assert.
- It's better because assert_equal prints the values when it fails.
https://github.com/ruby/rdoc/commit/91d40ce8f8 - 04:19 PM Revision 3a21da95 (git): [ruby/prism] Faster lex_identifier
- https://github.com/ruby/prism/commit/e44a9ae742
-
- Do not use a variable as a format string. Also we usually don't
expect non-ascii data in C string literals. -
- https://github.com/ruby/prism/commit/bd4d248fd6
-
-
-
- This reverts commit d434765faead1583ca9008bb579067a288085b93.
-
-
- https://github.com/ruby/prism/commit/4a7be1fc50
-
- It seems that this issue was gone by removing the `optflags=-O1` in Travis ppc64le on this PR's 2nd commit https://github.com/ruby/ruby/commit/ca7296767b5db9a401bc64738984f35880061a73 .
- 02:23 PM Revision ebb8da54 (git): .travis.yml: Refactor.
- * Add notes.
* When you see Travis issue, please check the link below.
https://github.com/ruby/ruby/wiki/CI-Servers#travis-ci
* Added the following random failure.
The ppc64le failure has been happening randomly in Travis foc... - 02:23 PM Revision 753b1ab1 (git): .travis.yml: Disable s390x allow_failures.
- To avoid unintentional new failures. Feel free to enable it again when the case
is unstable. - 02:23 PM Revision ca729676 (git): .travis.yml: Remove optflags=-O1 except arm32.
- We want to align the used build flags with RubyCI ppc64le Ubuntu jammy server
as much as possible to avoid Travis specific issues.
Still keep the -O1 for only arm32 due to the following issue.
https://bugs.ruby-lang.org/issues/19981 - 02:23 PM Revision 5d7904ff (git): .travis.yml: Upgrade the Ubuntu ppc64le to 22.04 (Jammy).
- Seeing the recent successes on RubyCI ppc64le Ubuntu jammy servers, it's time
to upgrade Travis ppc64le to jammy.
http://rubyci.s3.amazonaws.com/ppc64le/ruby-master/recent.html
Upgrade the gcc version to the latest version 11.4.0 to al... - 02:15 PM Revision 1d51e4ca (git): [ruby/prism] Improve comment generation in templates
- The existing comment generation was hard to read and was making a lot of string manipulation. However, ERB files are already designed to do string manipulation, so we can use that instead.
So, instead of doing a split and a map, I opted... -
- I faced the following segmentation fault on Ubuntu jammy arm32 (emulated environment by `SETARCH='setarch linux32 --verbose --32bit'`) in both Travis CI arm64 [log](https://app.travis-ci.com/github/ruby/ruby/jobs/612418476#L2422
) and R... -
- 09:27 AM Revision 14fa5e39 (git): [ruby/net-http] fix no_proxy behaviour
- https://github.com/ruby/net-http/commit/f4951dc42a
- 09:27 AM Revision f109269a (git): [ruby/net-http] fix a false-negative test
- * no_proxy is meant to operate on the destination address, not on the name of the proxy
* if both end with `'.example'`, the test does not nail down the behaviour
https://github.com/ruby/net-http/commit/bb9a5cfa3d -
- https://github.com/ruby/yaml/commit/b4b72ae0b4
-
- * [Bug #19969] Regression of memory usage with Ruby 3.1
* Revert or enable `rehash` with only large Hash?
* [www.ruby-lang.org needs a Privacy Policy page](https://github.com/ruby/www.ruby-lang.org/issues/3134)
* https://www.php.net/... - 06:25 AM Revision 18b7c768 (git): * 2023-10-30 [ci skip]
-
- [rubygems/rubygems] Relax matching pattern for rake version
https://github.com/rubygems/rubygems/commit/a89f74c27e -
- https://github.com/rubygems/rubygems/commit/a89f74c27e
-
04:10 AM Revision 34cb1748 (git): Optimize regexp matching for look-around and atomic groups (#7931)
10/29/2023
-
- Matz had taken the decision to make `(nil..nil) === any_object #=> true` in DevMeeting-2023-04-11.
Therefore, we can conclude that this behavior is a bug.
https://github.com/ruby/dev-meeting-log/blob/master/2023/DevMeeting-2023-04-11... -
- The fix will likely be https://github.com/kyanagi/ruby/tree/bug_19977.
-
06:46 PM Misc #19980 (Closed): Is the Ruby 3.3 ABI frozen?
- I'm a co-maintainer of [rake-compiler-dock](https://github.com/rake-compiler/rake-compiler-dock) which is used to build precompiled native packages for some gems, including nokogiri, sqlite3, grpc, re2, and ruby-magic.
In the past, pr... -
-
-
- ## Abstract
This feature proposes new syntax to allow methods to explicitly declare that they don't accept blocks, and makes passing of a block to such methods an error.
## Background
In #15554, it was proposed to automatically ... -
11:38 AM Bug #18743: Enumerator#next / peek re-use each others stacktraces
- Hi @nobu, and @ko1. The change was merged in July. Shouldn't this issue be closed?
- 07:16 AM Revision 7f2809b0 (git): Update default gems list at 88f1d380ea431bc807e221fa07f4ac [ci skip]
-
- https://github.com/ruby/etc/commit/a9e4d4730d
-
- The behavior will be changed at Ruby 3.3. See #18285.
-
05:51 AM Feature #19978: NoMethodError and large objects should not create unwieldy error messages
- If displaying the instance is not important for a NoMethodError, then getting rid of it entirely may make it simpler.
```rb
-e:1:in `<main>': undefined method `/' for Array instance (NoMethodError)
(1..1e3).to_a/=3
^... -
- Do you intend the elided inspect form to be defined for each class, or should it be a result of simple string ellipsis on a fully expanded inspect string (e.g., take the first ten and last seventeen characters from inspection, as in your...
-
04:07 AM Feature #19978 (Closed): NoMethodError and large objects should not create unwieldy error messages
- # Description
Currently, in the error message for `NoMethodError`, the object in question is inspected and displayed to the user. This results in unwieldy error messages for large objects. This comes up most often for me when working wi... -
01:52 AM Feature #19744: Namespace on read
- Eregon (Benoit Daloze) wrote in #note-24:
> @deivid @hsbt and other RubyGems/Bundler maintainers:
Hello, Josef (https://github.com/simi) from RubyGems team here.
> ...
Even I do like the basic idea of the proposal (and I do see be...