Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Testing adding a comment to a Gemfile #8643

Closed
wants to merge 1 commit into from

Conversation

lancedikson
Copy link

TBD if the test works out
Please ensure that your pull request adheres to our contribution guidelines. Thank you!

Signed-off-by: Denis Demchenko <[email protected]>
@sschuberth
Copy link
Member

I guess this PR related to this comment of yours. I ran the same test locally (as that's much faster) and it passes for me.

Copy link

codecov bot commented May 14, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 67.92%. Comparing base (43131ad) to head (ec163dd).

Additional details and impacted files
@@            Coverage Diff            @@
##               main    #8643   +/-   ##
=========================================
  Coverage     67.92%   67.92%           
  Complexity     1005     1005           
=========================================
  Files           244      244           
  Lines          7772     7772           
  Branches        876      876           
=========================================
  Hits           5279     5279           
  Misses         2110     2110           
  Partials        383      383           
Flag Coverage Δ
funTest-non-docker 34.79% <ø> (ø)
test 37.84% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@sschuberth
Copy link
Member

I guess this PR related to this comment of yours. I ran the same test locally (as that's much faster) and it passes for me.

Interesting, in CI it seems to fail. I'll investigate.

@lancedikson
Copy link
Author

I guess this PR related to #7478 (comment) of yours.

Yes, sorry for not linking the PR with the issue proactively

Interesting, in CI it seems to fail. I'll investigate.

Thanks! 🙌 Though the problem is hardly related to the open issue, but most likely to the comment only.

@sschuberth
Copy link
Member

Thanks! 🙌 Though the problem is hardly related to the open issue, but most likely to the comment only.

Actually, I can reproduce the problem also without the comment, so it's not related to that (and explains why I could not reproduce the problem by just adding a comment to an existing file). Instead, the problem seems to be related to the github dependency type.

@lancedikson
Copy link
Author

Okay, interesting :) It somehow works without a comment for me in my actual project and doesn't work with a comment. That's why I thought it was a comment-related issue.

@sschuberth
Copy link
Member

Digging deeper, looks like this is related to Ruby calling native git to fetch from GitHub underneath, and then running into jruby/jruby#6721. Actually, we already apply some of the work-arounds mentioned there. I'll investigate why they seem to have no effect.

@sschuberth
Copy link
Member

and then running into jruby/jruby#6721.

That was a red herring. The real cause was slightly different leading console output when fetching from GitHub, and that output was not stripped properly before parsing. #8644 fixes this.

@sschuberth sschuberth closed this May 14, 2024
@lancedikson
Copy link
Author

Thanks! I'll test it with my project today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants