Activity
From 07/27/2022 to 08/02/2022
08/02/2022
- 09:56 PM Revision 4f00ee8d (git): [rubygems/rubygems] fix platform matching for index specs
- https://github.com/rubygems/rubygems/commit/f087f1b590
-
09:56 PM Revision 20936eb3 (git): [rubygems/rubygems] Warn (rather than crash) when setting `nil` specification versions
- https://github.com/rubygems/rubygems/commit/a4ba1a4d97
-
08:17 PM Revision eaf6189f (git): [ruby/date] Enhanced RDoc (https://github.com/ruby/date/pull/69)
- Treats:
::_strptime
::strptime
Adds 'Related' entry to some methods' doc.
https://github.com/ruby/date/commit/a6c2129273 -
05:48 PM Feature #18910: Improve maintainability of LLDB helpers
- eightbitraptor (Matthew Valentine-House) wrote in #note-2:
> ianks (Ian Ker-Seymer) wrote in #note-1:
> ...
👍🏻 -
- Treats:
::_httpdate
::_iso8601
::_jisx0301
::_parse
::_rfc2822
::_rfc3339
::_xmlschema
::httpdate
::iso8601
::jisx0301
::parse
::rfc2822
::rfc3339
::xmlschema
https://github.com/ru... - 04:04 PM Revision 4ba611ab (git): * 2022-08-03 [ci skip]
-
04:04 PM Revision e4e054e3 (git): Speed up setting the backref match object
- This patch speeds up setting the backref match object by avoiding some
memcopies. Take the following code for example:
```ruby
"hello world" =~ /hello/
p $~
```
When the RE matches the string, we have to set the Match object in the
ba... -
01:40 PM Revision da00243d (git): [DOC] Specify ways to run bootstrap tests
-
- https://github.com/rubygems/rubygems/commit/3212ae14b7
-
12:42 PM Bug #18952: rb_aligned_free: munmap failed
- I note that the process has 65531 regions in the process memory map, which is basically identical to the default runtime limit vm.max_map_count = 65530. Our runtime environment is AWS Fargate, so it's unlikely we can raise this limit. Ot...
-
- Over the same 2-week period, I've seen two other logs that appear to be related:
[BUG] rb_aligned_malloc: munmap failed for end -
09:58 AM Feature #18559: Allocation tracing: Objects created by the parser are attributed to Kernel.require
- > @ko1: Because the precise implementation for it is hard, I like foo.rb:0. I will ask the original poster if the lineno is really important
The `lineno` isn't essential, if you think it's too much, I'll still be happy with `lineno=0`... -
- > How about the following?
Sounds good to me at first sight. I can work on a patch for it soon, if I notice any issue when implementing it I'll report it back here.
And thank you for the meeting notes, it's incredibly useful or me. -
09:27 AM Feature #18822: Ruby lack a proper method to percent-encode strings for URIs (RFC 3986)
- We discussed this issue at the dev meeting. How about the following?
* Introduce `CGI.escapeURIComponent(str)` that behaves like `CGI.escape`, except that a space is encoded as `%20` instead of `+` (as @byroot proposed)
* Introduce `... - 09:35 AM Revision b81858cf (git): [rubygems/rubygems] Fix arguments for bundle-config(1) docs
- Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
https://github.com/rubygems/rubygems/commit/3e62ca776d -
- Pull Request: https://github.com/ruby/ruby/pull/6207
-
- Applied in changeset commit:git|e3aabe93aae87a60ba7b8f1a0fd590534647e352.
----------
Implement Queue#pop(timeout: sec)
[Feature #18774]
As well as `SizedQueue#pop(timeout: sec)`
If both `non_block=true` and `timeout:` are supplied, A... -
- [Feature #18774]
As well as `SizedQueue#pop(timeout: sec)`
If both `non_block=true` and `timeout:` are supplied, ArgumentError
is raised. -
- @mame
> it would be nice to be properly confirm this advantage before introduction.
https://bugs.ruby-lang.org/issues/11164 is an example of how bad things can go without nakayoshi_fork (or similar). I can get production data from... -
- We discussed this issue at the dev meeting. We did not reach any conclusion, but I'd like to share some comments.
### What and how efficient is this proposal?
Some attendees wanted to confirm quantitative evaluation of the benefits... -
07:40 AM Revision ec3f5930 (git): [Bug #17767] Now `ENV.clone` raises `TypeError` as well as `ENV.dup`
- One year ago, the former method has been deprecated while the latter
has become an error. Then the 3.1 released, it is enough time to make
also the former an error. -
- https://github.com/rubygems/rubygems/commit/6e35a6edfe
-
- https://github.com/rubygems/rubygems/commit/7b0f7804f2
-
- Do dependency filtering and materialization in one step. Before,
dependency filtering would not consider ruby metadata so it would
discard variants that end up not being materializable in the end.
https://github.com/rubygems/rubygems/co... -
- https://github.com/rubygems/rubygems/commit/9f4ba9ebb0
-
- https://github.com/rubygems/rubygems/commit/a997210473
-
- https://github.com/rubygems/rubygems/commit/ffb161bb69
-
- https://github.com/rubygems/rubygems/commit/9d878cbda0
-
- https://github.com/rubygems/rubygems/commit/087e3e4e3b
-
- https://github.com/rubygems/rubygems/commit/08e1554fb6
-
- It was just working by chance.
(cherry picked from commit https://github.com/rubygems/rubygems/commit/16b2d6bfe893)
https://github.com/rubygems/rubygems/commit/8f922d980f -
- https://github.com/rubygems/rubygems/commit/2777e79b8e
-
- https://github.com/rubygems/rubygems/commit/5e100df7c9
-
07:00 AM Feature #18930 (Rejected): Officially deprecate class variables
- I admit class variables semantics are a bit complex and sometimes misunderstood.
But removing them should cause serious compatibility issues.
Class variables are somewhat similar to global variables. We don't recommend using/abusing ... -
02:15 AM Bug #18953 (Rejected): `Array#uniq` doesn't evaluate the given block when the size of the array is one
- `Array#uniq` doesn't evaluate the given block when the size of the array is one. Is this expected behavior?
```
$ ruby -e '[42, 43].uniq { _1.foo }; puts true'
-e:1:in `block in <main>': undefined method `foo' for 42:Integer (NoMeth... -
01:48 AM Feature #18949 (Rejected): Deprecate and remove replicate and dummy encodings
- String is a container and an encoding is a label of it. While data whose encoding is an encoding categorized in dummy encodings in Ruby, we cannot avoid such encodings.
-
01:04 AM Feature #18949: Deprecate and remove replicate and dummy encodings
- I think ISO-2022-JP is used for mail archives, and IRCnet even now.
08/01/2022
-
- Over the past several weeks, our Linux ruby 3.1.2 application has failed repeatedly with:
[BUG] rb_aligned_free: munmap failed
Ruby tracebacks indicate failures in many libraries and functions, due to the garbage collector running ... - 07:14 PM Revision 24204d54 (git): [rubygems/rubygems] Bump rb-sys in /test/rubygems/test_gem_ext_cargo_builder/custom_name
- Bumps [rb-sys](https://github.com/oxidize-rb/rb-sys) from 0.9.26 to 0.9.28.
- [Release notes](https://github.com/oxidize-rb/rb-sys/releases)
- [Commits](https://github.com/oxidize-rb/rb-sys/compare/v0.9.26...v0.9.28)
---
updated-depende... -
- ### Use case
A very common pattern in Ruby, especially in testing is to save the value of an attribute, set a new value, and then restore the old value in an `ensure` clause.
e.g. in unit tests
```ruby
def test_something_when_e... - 05:38 PM Revision 00777a9b (git): * 2022-08-02 [ci skip]
- 05:37 PM Revision 25022bad (git): [rubygems/rubygems] Bump rb-sys
- Bumps [rb-sys](https://github.com/oxidize-rb/rb-sys) from 0.9.26 to 0.9.28.
- [Release notes](https://github.com/oxidize-rb/rb-sys/releases)
- [Commits](https://github.com/oxidize-rb/rb-sys/compare/v0.9.26...v0.9.28)
---
updated-depende... -
05:33 PM Feature #18949: Deprecate and remove replicate and dummy encodings
- > But on the other hand, ISO-2022-JP, UTF-16, and UTF-32 definitely have their uses. They are not so much used directly when processing strings (because indeed for these encodings, most string operations don't work, or don't work correct...
-
07:01 AM Feature #18949: Deprecate and remove replicate and dummy encodings
- For `Encoding.list.filter { |e| e.dummy? }`, I get the following list:
```
#<Encoding:UTF-16 (dummy)>,
#<Encoding:UTF-32 (dummy)>,
#<Encoding:IBM037 (dummy)>,
#<Encoding:ISO-2022-JP (dummy)>,
#<Encoding:ISO-2022-JP-2 (dummy)>,
#... -
04:21 PM Bug #10820: Win32 Registry Delete uses ANSI instead of Wide APIs
- Late to the party, but why was `RegQueryInfoKey` also update to use `W`? I am working on https://github.com/jruby/jruby/issues/7106 and cannot figure out how CRuby manages to locate `RegQueryInfoKey` when only the `A` and `W` versions sh...
-
- Previously it would crash like this:
````
$ /Users/deivid/.asdf/installs/ruby/3.1.2/bin/ruby -I/Users/deivid/Code/rubygems/rubygems/bundler/spec -r/Users/deivid/Code/rubygems/rubygems/bundler/spec/support/artifice/fail.rb -r/Users/deivi... -
- https://github.com/rubygems/rubygems/commit/9be5eae9cf
-
08:48 AM Revision 5bbba764 (git): respect current frame of `rb_eval_string`
- `self` is nearest Ruby method's `self`.
If there is no ruby frame, use toplevel `self` (`main`).
https://bugs.ruby-lang.org/issues/18780 -
06:23 AM Bug #18912 (Assigned): Build failure with Xcode 14 and macOS 13 (Ventura) Beta
-
- I tried https://github.com/ruby/ruby/pull/6193 .
The first try is failed. Because my environment mixed the homebrew `binutils` built by macOS 12.0(monterey).
I could build ruby after removing GNU `binutils` from `PATH`. and it cou... -
-
- Thank you very much, merged!
> Sidenote: It's bit shame one has to read and understand this https://docs.github.com/en/site-policy/github-terms/github-terms-of-service fairly long document before sending a patch.
Thank you for your... -
01:36 AM Revision c69ad738 (git): Initialize node_id
- In some causes node_id might have been left uninitialized leading to
undefined behavior on access. So always set it to -1, so we have *some*
valid value in there.
07/31/2022
-
05:06 PM Feature #18930: Officially deprecate class variables
- Eregon (Benoit Daloze) wrote in #note-15:
> Regarding @austin's example, there is Class#subclasses now which might be an easier way to do that.
Not really, because that would require some sort of runtime filter of said subclasses. Th... -
04:15 PM Feature #18930: Officially deprecate class variables
- (Playing for both sides here, hehe)
Actually, I believe that the culprit might be just the name. E.g., we have two camps, basically saying:
1. The behavior of [however it is named] is useful, and it matches my expectations of [this t... -
02:23 PM Feature #18930: Officially deprecate class variables
- Regarding @austin's example, there is Class#subclasses now which might be an easier way to do that.
Using class variables for that only works based on a fairly subtle constraint that Base needs to be inherited before any Base subclass c... -
12:03 PM Feature #18930: Officially deprecate class variables
- Eregon (Benoit Daloze) wrote in #note-8:
> ```ruby
> ...
This is exactly the behavior that I want and expect from class variables. If I wanted one 'foo' per subclass I would use class instance variables.
It's not like I use class variab... -
- austin (Austin Ziegler) wrote in #note-12:
> > > but `Rand.dependents` producing `{1=>V1}` and `Timestamp.dependents` producing `{2=>V2,3=>V3,4=>V4}`.
> ...
Well, it depends on the task. I have met several times with architecture li... -
- jeremyevans0 (Jeremy Evans) wrote in #note-10:
> austin (Austin Ziegler) wrote in #note-9:
> ...
It doesn’t—as such. This was something I coded up and was *surprised* that it didn’t work the way that I expected, and exploring it result... - 04:31 PM Revision 3b8279e9 (git): * 2022-08-01 [ci skip]
- 04:31 PM Revision b0e6d07c (git): [rubygems/rubygems] Update bundle-platform(1) man
- Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
https://github.com/rubygems/rubygems/commit/1c3736f5af -
- I have updated the issue description with a `To Decide` section to summarize for the dev meeting: https://bugs.ruby-lang.org/issues/18949#To-Decide
07/30/2022
-
- @austin
About your example
I'd say that referencing a class method in another class method in inheritance hierarchy always makes one ask whether you meant the method/data of the base class or of the current one.
Because, like
... -
10:55 PM Feature #18930: Officially deprecate class variables
- austin (Austin Ziegler) wrote in #note-9:
> If we’re going to deprecate them, we need something that effectively replaces them—and class instance variables aren’t it.
The particular approach given may not work (I don't see how it tri... -
- If we’re going to deprecate them, we need something that effectively replaces them—and class instance variables aren’t it. I was experimenting with something along the lines of:
```ruby
class Base
def self.dependents
@depende... -
- @Dan0042 It seems likely you might not know well their semantics then and how much a trap they are.
Using @byroot's example from https://bugs.ruby-lang.org/issues/14541#note-25:
```ruby
class A
@@foo = 1
def self.foo
@@... -
- I am 100% opposed to deprecation. I use class variables regularly. As long as you initialize them in the class definition, there is no issue with shadowing. They're inherited in subclasses. They work perfectly fine.
-
- Hash#slice documentation states it returns a new hash object, not a modified copy of the receiver. A new hash object by default does not have a default value or block. Hash#slice doesn't copy the default value either: `Hash.new(0).slice...
-
07:23 PM Feature #18950 (Open): Hash#slice fails to copy default block
- An intense weekend debugging session discovered the following root cause of a bug: `Hash#slice` returns a new Hash, which has no default block set, even if the source Hash did have a default block set.
Simplified code to reproduce:
... - 06:18 PM Revision 118368c1 (git): * 2022-07-31 [ci skip]
-
- Treats:
::httpdate
#to_date
#to_time
#to_datetime
In behalf of ::httpdate, I've introduced section "Argument limit" that can be pointed to by various Date methods (similar to existing section "Argument start"). This will ... -
- I have looked at usage of `Encoding#replicate` and `rb_define_dummy_encoding()`.
`Encoding#replicate` seems only used in 1 CRuby test, 1 ruby/spec file and exactly 1 gem (!), using the command below:
```
$ gem-codesearch '\.replicate\b'... -
- @mame Could you give an example in Ruby code?
I don't understand your concern, of course `p` changes behavior because it calls `inspect` (which can do anything) and prints, but that seems fully expected. - 11:05 AM Revision d050f162 (git): Mention Enumerator.product/Enumerator::Product in the NEWS.md
- 11:05 AM Revision 1a73a6cd (git): Implement Enumerator::Product and Enumerator.product [Feature #18685]
-
-
- This reverts commit 0d842fecb4f75ab3b1d4097ebdb8e88f51558041.
- 08:26 AM Revision 0d842fec (git): * expand tabs. [ci skip]
- Tabs were expanded because the file did not have any tab indentation in unedited lines.
Please update your editor config, and use misc/expand_tabs.rb in the pre-commit hook. -
-
-
-
- This reverts commit 8a65cf3b61c60e4cb886f59a73ff6db44364bfa9.
- 07:41 AM Revision 8a65cf3b (git): * expand tabs. [ci skip]
- Tabs were expanded because the file did not have any tab indentation in unedited lines.
Please update your editor config, and use misc/expand_tabs.rb in the pre-commit hook. -
- https://github.com/ruby/digest/commit/5ca2b5b91e
-
- > the state of Copy-on-Write is already pretty decent,
It depends how you look at it. In the few apps on which I optimized CoW as much as I could, only between 50% and 60% of the parent process memory is shared. That really isn't that... -
- I think the state of Copy-on-Write is already pretty decent, but any improvement is of course very welcome. As to naming, since this is mainly for preforking servers, what about `Process.prefork`?
-
- https://github.com/ruby/rdoc/commit/75eee668a5
07/29/2022
-
- noahgibbs (Noah Gibbs) wrote in #note-2:
> I've been working on YJIT string handling. At this point our string handling is so simple that I don't think this would affect us either way. For encodings, we mostly call CRuby functions that ... -
08:17 PM Feature #18949: Deprecate and remove replicate and dummy encodings
- I've been working on YJIT string handling. At this point our string handling is so simple that I don't think this would affect us either way. For encodings, we mostly call CRuby functions that handle them. So short-term, I don't think th...
-
- Based on my recent work on `String#<<` performance, I concur that encoding management often takes longer than the actual string operation, and that `get_actual_encoding()` is a very big offender.
I'm also curious what was the intended... -
- Ruby has a lot of accidental complexity.
Sometimes it becomes clear some features bring a lot of complexity and yet provide little value or are used very rarely.
Also most Ruby users do not even know about these features.
Replicate an... -
11:32 PM Revision 0e85586e (git): Add --enable-yjit=dev_nodebug configure option
-
-
- `Time#to_datetime` does not operate the same way, which seems like an undesirable inconsistency:
```ruby
Time.local(1499, 12, 27).to_datetime
=> #<DateTime: 1499-12-27T00:00:00-07:52 ((2268928j,28378s,0n),-28378s,2299161j)>
Time.... -
08:26 AM Bug #18946: Time#to_date returns incorrect date
- > Time seems to use a proleptic Gregorian calendar (the Gregorian calendar extended to before the Gregorian reform, see https://en.wikipedia.org/wiki/Proleptic_Gregorian_calendar) while Date seems to be using the Julian calendar before t...
-
- This may be due to the Gregorian calendar reform (see https://en.wikipedia.org/wiki/Gregorian_calendar#Gregorian_reform, which says: "Julian Thursday, 4 October 1582, being followed by Gregorian Friday, 15 October").
Time seems to use... -
- Time#to_date returns incorrect date.
Actual Behavior:
```
Time.local(1499, 12, 27).to_date
=> #<Date: 1499-12-18 ((2268919j,0s,0n),+0s,2299161j)>
```
Expected Behavior:
```
Time.local(1499, 12, 27).to_date
=> #<Date: 1499-12... -
- Treats:
#===
#to_s
#inspect
#strftme
#asctime
#iso3601
#rfc3339
#rfc2822
#httpdate
#jisx0301
https://github.com/ruby/date/commit/aed66fedf6 - 07:24 PM Revision 2346f3be (git): * 2022-07-30 [ci skip]
-
- I'm not sure if using relative paths in the generated script is best for
this case, since it makes the script not movable, but that can be
improved later.
https://github.com/rubygems/rubygems/commit/7f5bdbb842 -
- https://github.com/rubygems/rubygems/commit/d695c8da3e
-
- I hope I did everything correctly: https://github.com/ruby/ruby/pull/6202
Sidenote: It's bit shame one has to read and understand this https://docs.github.com/en/site-policy/github-terms/github-terms-of-service fairly long document be... -
- Good catch! Your first patch looks great to me. Can you send a PR to https://github.com/ruby/ruby/? Thank you!
-
- > the last time I tried something like that it was rejected: #14541.
#14541 proposed to change their semantic, which is a hard proposition for backward compatibility. What I'm alluding to would be to introduce another syntax for true... -
- @shan Agreed.
If we are not yet ready to deprecate them, could we at least discourage them in official docs?
@byroot:
> Yes that's what I say in my comment, and I see how some users may find this unsatisfactory.
I think it is a... -
- Posting here since there is no ticket for the next meeting yet (@mame Could you copy this when creating the next dev meeting ticket?).
* [Feature #18949] Deprecate and remove replicate and dummy encodings (eregon)
* What do you thi... -
03:28 PM Bug #18947: Unexpected Errno::ENAMETOOLONG on Windows
- austin (Austin Ziegler) wrote in #note-1:
> If Ruby does not have an application manifest (I don’t know whether it does or not)
As I understand it was added here — [[Win32] long path name support [Bug #12551]](https://github.com/ruby... -
- inversion (Yura Babak) wrote:
> Pathname and FileUtils work fine for me until there is a folder with a **very long path** (>260 chars).
> ...
It’s been a long time since I’ve done anything in Windows, but the article you posted indica... -
- On Windows 10, I am working on a script to copy a complex folder structure.
Pathname and FileUtils work fine for me until there is a folder with a **very long path** (>260 chars).
Normally you cannot access such a folder with Ruby.... -
-
-
-
-
-
-
-
- okuramasafumi (Masafumi OKURA) wrote in #note-2:
> In a real world code I'm facing, `M1` contains lots of other methods so including it in `InstanceMethods` causes confusion.
You should be able to work around this by making sure the ... -
02:41 PM Feature #18948: Add `with_private_method` option to `private_constant`
- In a real world code I'm facing, `M1` contains lots of other methods so including it in `InstanceMethods` causes confusion.
I pushed my code on GitHub.
https://github.com/okuramasafumi/alba/blob/jsonapi/lib/alba/resource.rb#L299-L301... -
- How about calling `include M1` in `M2::InstanceMethods`?
```
module M1
CONST = 'CONST'.freeze
private_constant :CONST
end
module M2
def self.included(base)
base.include InstanceMethods
end
module InstanceMet... -
- ## Problem
I have the following code:
```ruby
module M1
CONST = 'CONST'.freeze
end
module M2
def self.included(base)
base.include M1
base.include InstanceMethods
end
module InstanceMethods
def cons... -
- Also adjusts which blocks may be nested.
https://github.com/ruby/rdoc/commit/dde1860441 -
01:54 PM Bug #18743: Enumerator#next / peek re-use each others stacktraces
- This issue is part of Ruby for a long time now:
https://github.com/ruby/ruby/commit/3a855da47b867e24428582b0a20aa1ea7e4dc2af
Proposed fix here:
https://github.com/ruby/ruby/pull/6201 -
-
-
10:10 AM Revision b2cc74a5 (git): [flori/json] test parsing of unicode, mixing literal characters with escaped
- https://github.com/flori/json/commit/82fe866da2
-
- It makes testing for JSON errors very tedious. You either have
to use a Regexp or to regularly update all your assertions
when JSON is upgraded.
https://github.com/flori/json/commit/de9eb1d28e - 10:10 AM Revision 4bf97a8e (git): fix typo in Time#xmlschema documentation
-
10:10 AM Revision 419ad1e1 (git): [ruby/optparse] Also accept '-' as an optional argument (https://github.com/ruby/optparse/pull/35)
- https://github.com/ruby/optparse/commit/f2b8318631
-
- 10:06 AM Revision d1e726cc (git): [rubygems/rubygems] Fix dead links to deprecated bundle-package(1) with bundler-cache(1)
- Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
https://github.com/rubygems/rubygems/commit/9c2e80a10f -
08:29 AM Feature #18685: Enumerator.product: Cartesian product of enumerables
- https://github.com/ruby/ruby/pull/6197
- 07:31 AM Revision def1d44a (git): [rubygems/rubygems] Add package/pack aliases to man pages for cache
- Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
https://github.com/rubygems/rubygems/commit/1685e3a9dc -
-
- Reported at https://github.com/ruby/rdoc/pull/907#discussion_r932505816
https://github.com/ruby/rdoc/commit/86384ac7f9
07/28/2022
-
11:26 PM Feature #18930: Officially deprecate class variables
- In the Ruby communities on IRC and Slack we frequently have to convince new Rubyists to just treat class variables as deprecated rather than wasting time learning all about them to find they'll never use them or get them through a code r...
-
- > If you don't want that to be public API it could be :nodoc: or made private + using send.
Yes that's what I say in my comment, and I see how some users may find this unsatisfactory. -
- For such a case it seems fine to use instance variables on the class and expose e.g. `SomeThingNeverInherited#some_config?`.
If you don't want that to be public API it could be `:nodoc:` or made private + using `send`.
```ruby
class... -
- Even though I don't remember adding any new class variable in the last half decade, I'm not sure we can deprecate them, as IMO deprecations should be actionable, and some of these may not be.
I think the main use case for class variab... -
11:12 PM Revision 0d68286b (git): Revert "Try reproducing the MinGW hang on time command (#6168)"
- This reverts commit bee5089d6789401f265f87b2f23f1bd7ec63cec8.
Looking at https://github.com/ruby/ruby/runs/7564065637?check_suite_focus=true,
we concluded that the ruby process for test-all is stuck before exit
when this issue reproduce... -
- I am trying to compile ruby in a reproducible way, but libruby always has a
different hash. After two days of digging I've reached the conclusion that
node_id is used when not initialized, leading to an undefined behaviour. In my
case... -
- https://github.com/ruby/date/commit/0cdbaa92e9
-
- Recently new RDoc::MarkupReference replaces Markup Reference in RDoc::Markup (which was always the goal).
https://github.com/ruby/rdoc/commit/825be7eaf4 - 03:38 PM Revision 68655c62 (git): * 2022-07-29 [ci skip]
-
03:38 PM Revision ab08a43e (git): YJIT: Teach getblockparamproxy to handle the no-block case without exiting (#6191)
- Teach getblockparamproxy to handle the no-block case without exiting
Co-authored-by: John Hawthorn <john@hawthorn.email>
Co-authored-by: John Hawthorn <john@hawthorn.email> -
- https://github.com/ruby/rdoc/commit/c02645364f
-
-
-
-
02:41 PM Feature #18159: Integrate functionality of syntax_suggest gem into Ruby
- Without any additional patches by Nobu here are the known limitations:
- Does not work with streaming code from STDIN (i.e. `echo 'def bad' | ruby` )
- Does not work when executing a file directly (i.e. `ruby bad.rb`)
- Does not wor... -
- Can we merge `syntax_suggest` into ruby/ruby now? Is there any blocker?
-
- When using Ractors, rb_gc_writebarrier_unprotect requries a VM lock
since it modifies the bitmaps. -
- Before this commit, if the slice fits in VWA, it would make a copy
rather than a view. This is slower as it requires a memcpy of the
contents. -
-
01:03 PM Feature #18910: Improve maintainability of LLDB helpers
- ianks (Ian Ker-Seymer) wrote in #note-1:
> On a related note, I’ve often found myself wanting access to these helpers when developing native extensions. I’ve copy-pasta’d them in the past, but I wonder if Ruby could support including th... -
12:01 PM Bug #18912: Build failure with Xcode 14 and macOS 13 (Ventura) Beta
- @hsbt Thanks for the logs. Some symbols are
indeed not found due to link errors. For example,
`rb_complex_real()` is provided but not found.
The linker error contradicts itself:
```
have_func: checking for rb_complex_real() in r... -
- @katei Thanks! I will test your patch when it's complete.
FYI: Xcode 14 beta 3 with macOS 13.0 public beta is still same results.
-
09:04 AM Bug #18912: Build failure with Xcode 14 and macOS 13 (Ventura) Beta
- I've made a patch to address the linking failure issue by replacing `-undefined dynamic_lookup` with `-bundle_loader`.
https://github.com/ruby/ruby/pull/6193
The patch has been tested with Xcode 14 beta2 toolchain on macOS 12.4 Monte... -
- @alanwu full log is here https://gist.github.com/hsbt/293250f86a2731b4f76ceea4d903bd64
-
11:57 AM Bug #18933: Dir.tmpdir implemented in non-Ractor-safe manner
- Attached is a possible solution for this
-
-
-
-
-
- I created https://bugs.ruby-lang.org/issues/18944
-
- While implementing [Feature #18774] It appeared to me that adding this timeout was quite obvious.
And @matz explicitly asked for a separate ticket to be opened for that feature if someone wanted it: https://github.com/ruby/dev-meeting... -
-
- to see if it really exits correctly.
GitHub Support asked me to confirm the command is exiting correctly. -
-
- I'd like to propose the change to the bytecode for constant caching.
I've submitted this improvement via pull request at https://github.com/ruby/ruby/pull/6187 and also attached a patch to this issue.
Previously YARV bytecode impleme... -
-
07/27/2022
-
10:31 PM Bug #18920 (Closed): Documentation on ARGF.inplace_mode and ARGF.inplace_mode= is wrong
- Applied in changeset commit:git|4ad69899b7db1e384665dec090d5cdc0c3b3c9b2.
----------
Fix documentation for ARGF.inplace_mode{,=}
The value affects the name of the backup file created, not the
name of the file modified (as the file is m... -
- The value affects the name of the backup file created, not the
name of the file modified (as the file is modified in place).
Fixes [Bug #18920] -
-
06:42 PM Misc #18942: String splitting handling of empty fields is incorrect or insufficiently documented (SOLVED)
- austin (Austin Ziegler) wrote in #note-1:
> scub8040 (Saverio M.) wrote:
> ...
Uh, ok! Thanks.
EDIT: I've tried to close the issue, but couldn't. -
- scub8040 (Saverio M.) wrote:
> There are other cases though, which I think are either incorrectly handled, or at least, they should documented.
> ...
This is neither a behaviour bug nor a documentation bug.
From `ri String#split`:
... -
- Hello!
The string splitting needs to deal with some edge cases when it comes to empty strings/fields, for example, an emptry string always returns an empty array.
There are other cases though, which I think are either incorrectly h... -
- @mame thanks for bringing this out, I definitely missed it. I'll open another ticket tomorrow then.
-
- According to the dev meeting log, @matz said "Create another ticket for SizedQueue#push if someone wants it".
https://github.com/ruby/dev-meeting-log/blob/master/DevMeeting-2022-05-19.md#feature-18774-add-queuepoptimeout-eregon -
- > I think it'd be fine to add, and I don't think that needs to be discussed in a dev meeting again since it's so similar.
Agreed. Also `SizedQueue#push` already has `non_block=false` like `Queue#pop`, so it makes perfect sense. I'll i... -
- byroot (Jean Boussier) wrote in #note-12:
> So I started to implement `Queue#pop(timeout:)` and `SizedQueue#pop(timeout:)` https://github.com/ruby/ruby/pull/6185
Thanks!
> ...
I think it'd be fine to add, and I don't think that ne... -
- So I started to implement `Queue#pop(timeout:)` and `SizedQueue#pop(timeout:)` https://github.com/ruby/ruby/pull/6185
As pointed by @ioquatix, I believe that `SizedQueue#push` should have a timeout as well. -
- Another optimization that could be invoked from this method is `malloc_trim`.
- 03:24 PM Revision 708d06f3 (git): * 2022-07-28 [ci skip]
-
-
-
- I've rebased to change the name of the project from `DeadEnd` to `SyntaxSuggest`. All checks are passing except for "Code scanning results / CodeQL" which doesn't appear to be related to my code change.
I've got no other pending chan... -
01:55 PM Revision 9b9704f9 (git): merge revision(s) 456e1d1eaa9bb11adaed1acde488d7da3c88704b:
- Try the tag without "v" prefix to checkout upstream repositories
---
gems/bundled_gems | 4 ++--
tool/fetch-bundled_gems.rb | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-) -
-
- Should not be `Pathname::FileUtils`.
https://github.com/ruby/pathname/commit/d1eb366e73 -
-
-
-
- What we want to test should be the bundled and to be installed files,
but not the upstream. -
- Thank you for your report. The behavior was indeed changed between 3.0 and 3.1: https://github.com/ruby/fileutils/pull/60
-
- On Windows 10 with Ruby `3.1.2p20 (2022-04-12 revision 4491bb740a) [x64-mingw-ucrt]`,
an attempt to create a path on the offline external drive stuck with a memory leak:
``` ruby
require 'fileutils'
FileUtils.mkpath 'W:/new_dir'
```... -