-
Notifications
You must be signed in to change notification settings - Fork 317
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
Conversation
Signed-off-by: Denis Demchenko <[email protected]>
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. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
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
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Interesting, in CI it seems to fail. I'll investigate. |
Yes, sorry for not linking the PR with the issue proactively
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 |
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. |
Digging deeper, looks like this is related to Ruby calling native |
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. |
Thanks! I'll test it with my project today. |
TBD if the test works out
Please ensure that your pull request adheres to our contribution guidelines. Thank you!