As I mentioned in 4dc603b#r54080150, using prepend doesn't guarantee conflict-free.

in fact, I used prepend over alias when patching Net::HTTP. but the conflicts aren't that few, you can see #1427 for more detail.

I choose alias for the rake integration because display_error_message was patched this way since the sentry-raven era and it seemed to work fine. so I didn't want to change it and potentially introduce another set of conflicts.

Can you tell me what caused the conflicts in your application?

@st0012

Can you tell me what caused the conflicts in your application?

My other gem extends Rake::Task with prepend, what doesn't cooperates with aliasing and getting a stack level too deep (SystemStackError). It's basically same case as in the example I shared .

Codecov Report

❌ Patch coverage is 50.00000% with 8 lines in your changes missing coverage. Please review.
✅ Project coverage is 98.75%. Comparing base (8387282) to head (040ed70).
⚠️ Report is 848 commits behind head on master.

@@            Coverage Diff             @@
##           master    #1517      +/-   ##
==========================================
+ Coverage   98.20%   98.75%   +0.55%     
==========================================
  Files         218      123      -95     
  Lines       10607     6771    -3836     
==========================================
- Hits        10417     6687    -3730     
+ Misses        190       84     -106     

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