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

Add debug logs for data loading and processing steps #353

Merged
merged 1 commit into from
Dec 10, 2024

Conversation

ludeknovy
Copy link
Owner

No description provided.

Copy link

codecov bot commented Dec 10, 2024

Codecov Report

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

Project coverage is 52.56%. Comparing base (e914265) to head (f462016).
Report is 1 commits behind head on master.

Files with missing lines Patch % Lines
...er/controllers/item/shared/item-data-processing.ts 0.00% 17 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #353      +/-   ##
==========================================
- Coverage   53.09%   52.56%   -0.53%     
==========================================
  Files         102      102              
  Lines        1699     1716      +17     
  Branches      155      155              
==========================================
  Hits          902      902              
- Misses        778      795      +17     
  Partials       19       19              
Flag Coverage Δ
unittests 52.56% <0.00%> (-0.53%) ⬇️

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.

@ludeknovy ludeknovy merged commit 5cd23f3 into master Dec 10, 2024
4 of 6 checks passed
@ludeknovy ludeknovy deleted the feature/item-processing-logs branch December 10, 2024 20:10
@ddennerline3
Copy link

Thanks so much for creating this PR. It'll be very helpful for identifying the root cause of the OoM issue.
I don't have access to the database logs right now because we use TimscaleDB SaaS.

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