fix(integrations/ray): Correctly pass keyword arguments to ray.remote function

[svartalf]

Monkey-patched implementation was passing the provided keyword arguments incorrectly due to a typo - "*kwargs" was used instead of "**kwargs" twice.

Fixed integration started hitting an assert in the Ray codebase that requires for users to use "@ray.remote" decorator either with no arguments and no parentheses, or with some of the arguments provided.

An additional wrapper function was added to support both scenarios.

---

Thank you for contributing to sentry-python! Please add tests to validate your changes, and lint your code using tox -e linters.

Running the test suite on your PR might require maintainer approval.

[codecov]

Codecov Report

Attention: Patch coverage is 54.05405% with 17 lines in your changes missing coverage. Please review.

Project coverage is 80.70%. Comparing base (dae0218) to head (99f5fcf).
Report is 3 commits behind head on master.

Files with missing lines	Patch %	Lines
sentry_sdk/integrations/ray.py	54.05%	17 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #4430      +/-   ##
==========================================
+ Coverage   80.68%   80.70%   +0.01%     
==========================================
  Files         156      156              
  Lines       16473    16479       +6     
  Branches     2799     2801       +2     
==========================================
+ Hits        13291    13299       +8     
+ Misses       2297     2296       -1     
+ Partials      885      884       -1     

Files with missing lines	Coverage Δ
sentry_sdk/integrations/ray.py	61.33% <54.05%> (+3.36%)	⬆️

... and 4 files with indirect coverage changes

[svartalf]

@sentrivana thank you for merging the master branch!

I fixed the mypy errors (and added a missing functools.wraps() call for better dev UX), should we do anything about the failing Codecov workflow?

[sentrivana]

Hey @svartalf, thanks for the PR!

We still have to properly review this but until then could I ask you to please:

• take a look at the failing Tasks tests -- looks like the last change introduced some breakage
• fix the remaining mypy error (sentry_sdk/integrations/ray.py:122: error: Unused "type: ignore" comment [unused-ignore])

Re: the codecov warning, we can reevaluate if we need more test coverage afterwards too, but I think this should already be properly covered, will check when reviewing.

[svartalf]

take a look at the failing Tasks tests -- looks like the last change introduced some breakage

Done! It looks like adding the @functools.wraps() decorator was a mistake, as we injecting an additional _tracing parameter to the user function, but wraps omits it somehow (?). Not sure about its behavior, it would be nice to explore it later.

fix the remaining mypy error (sentry_sdk/integrations/ray.py:122: error: Unused "type: ignore" comment [unused-ignore])

I removed this type: comment, but I'm still puzzled why mypy is unhappy about it:

• ray package is not installed by default, so I would expect mypy to correctly raise an import-not-found error
• And the comment itself was introduced 10 months ago in the original implementation, and it hasn't triggered any errors until this PR

Anyway, I guess, as long as mypy is happy… :)

[sentrivana]

Sorry for the wait! Looking at this properly now.

And the comment itself was introduced 10 months ago in the original implementation, and it hasn't triggered any errors until this PR

Stuff like this is usually due to a mypy update since we don't pin. Thanks for fixing it, even if it had nothing to do with your PR. Now it's unhappy again 😭 but I'll fix that, don't worry about it.