Skip to content

Conversation

@Dimfacion
Copy link
Member

Proposed changes

Testing Instructions

  1. Step-by-step how to test
  2. Environment or config notes

Related issues

Checklist

  • I consider the submitted work as finished
  • I tested the code for its functionality
  • I wrote test cases for the relevant uses case
  • I added/update the relevant documentation (either on github or on notion)
  • Where necessary I refactored code to improve the overall quality
  • For bug fix -> I implemented a test that covers the bug

@codecov
Copy link

codecov bot commented Oct 30, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 49.48%. Comparing base (37a5d39) to head (6e70359).
⚠️ Report is 109 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #4343      +/-   ##
============================================
- Coverage     49.49%   49.48%   -0.02%     
+ Complexity     3570     3567       -3     
============================================
  Files           886      886              
  Lines         26421    26421              
  Branches       1964     1964              
============================================
- Hits          13077    13074       -3     
  Misses        12558    12558              
- Partials        786      789       +3     

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@RomuDeuxfois
Copy link
Member

@Dimfacion why are we removing this ?

@Dimfacion
Copy link
Member Author

@RomuDeuxfois
This should not be in the basic configuration since it will impact log for customers too. We would like to remove it from the application.properties and add it in prerelease and testing environment as env variables.

@savacano28 savacano28 changed the title [backend] Removing the leak detection for prod environment [backend] fix: removing the leak detection for prod environment Nov 19, 2025
@Dimfacion Dimfacion changed the title [backend] fix: removing the leak detection for prod environment [backend] fix: removing the leak detection for prod environment (#4457) Nov 28, 2025
@Dimfacion Dimfacion merged commit c0be543 into master Nov 28, 2025
12 of 13 checks passed
@Dimfacion Dimfacion deleted the fix/remove_leak_detection branch November 28, 2025 13:07
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.

3 participants