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

feat: surface warehouse reconciliation errors in DAG -- release-0.5 edition #1744

Conversation

krancour
Copy link
Member

@krancour krancour commented Apr 2, 2024

This cherry-picks #1736 into the release-0.5 branch.

Signed-off-by: Remington Breeze <remington@breeze.software>
@krancour krancour added this to the v0.5.0 milestone Apr 2, 2024
@krancour krancour requested a review from rbreeze April 2, 2024 23:38
@krancour krancour self-assigned this Apr 2, 2024
@krancour krancour requested a review from a team as a code owner April 2, 2024 23:38
Copy link

codecov bot commented Apr 2, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 43.43%. Comparing base (2baed56) to head (3a45f1c).

Additional details and impacted files
@@             Coverage Diff              @@
##           release-0.5    #1744   +/-   ##
============================================
  Coverage        43.43%   43.43%           
============================================
  Files              211      211           
  Lines            13359    13359           
============================================
  Hits              5803     5803           
  Misses            7311     7311           
  Partials           245      245           

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

@krancour krancour merged commit db2195d into akuity:release-0.5 Apr 2, 2024
16 checks passed
@krancour krancour deleted the krancour/warehouse-errors-release-0.5-edition branch April 2, 2024 23:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants