Closed haseebab closed 1 year ago
❌ @haseebab the signed-off-by
was not found in the following 1 commits:
All proposed commits should include a sign-off in their messages, ideally at the end.
The Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
By making a contribution to this project, I certify that:
a. The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or
b. The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or
c. The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.
d. I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.
Contributors sign-off that they adhere to these requirements by adding a Signed-off-by
line to commit messages.
This is my commit message
Signed-off-by: Random Developer <randomdeveloper@example.com>
Git even has a -s
command line option to append this automatically to your commit message:
$ git commit -s -m 'This is my commit message'
Hi
Thank you for taking the initative on this! In general the existing test jobs with Ruby 2.7 pass fine, on Ruby 2.6 it appears that we have a breaking issue:
::Instana.agent.spawn_background_thread
is called in lib/instana.rb:18
which goes through@delegate.public_send(mth, *args, **kwargs, &block)
in lib/instana/backend/agent.rb:38
and here an extra argument is being passed on to the next frame:spawn_background_thread
in host_agent.rb:19
and that doesn't like that extra argument:
wrong number of arguments (given 1, expected 0) (ArgumentError)
Hi
Thank you for taking the initative on this! In general the existing test jobs with Ruby 2.7 pass fine, on Ruby 2.6 it appears that we have a breaking issue:
::Instana.agent.spawn_background_thread
is called inlib/instana.rb:18
which goes through@delegate.public_send(mth, *args, **kwargs, &block)
inlib/instana/backend/agent.rb:38
and here an extra argument is being passed on to the next frame:spawn_background_thread
inhost_agent.rb:19
and that doesn't like that extra argument:wrong number of arguments (given 1, expected 0) (ArgumentError)
@Ferenc- I've read over the guidelines again, and there's a section on A compatible delegation that works on Ruby 2.6, 2.7 and Ruby 3
.
I've added a new commit that utilizes Module#ruby2_keywords
to support delegation across all ruby versions, as the guidelines recommend. I think all the test suites should pass now.
Hi, Thank you for you for taking the initiative. We believe that the 3.0 support is complete, so I am closing this issue now. We can re-open if needed.
Ruby 3.0 introduced the separation of positional and keyword arguments:
Handling argument delegation
Ruby 2.6 or prior
In Ruby 2, you can write a delegation method by accepting a
*rest
argument and a&block
argument, and passing the two to the target method. In this behavior, the keyword arguments are also implicitly handled by the automatic conversion between positional and keyword arguments.Ruby 3
You need to explicitly delegate keyword arguments.
Changes in this pull request
This is a proposal to update delegate methods in this codebase (non-exhaustive), where the explicit delegation of keyword arguments is warranted, as per the Ruby 3.0 guidelines.