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

Improved error handling so that binding to a ProvisionedService object no longer swallows errors #952

Conversation

ncarlson
Copy link
Contributor

Fixed error handling on readProvisionedServiceDuckType. Added additional test coverage.

@codecov-commenter
Copy link

codecov-commenter commented Apr 18, 2022

Codecov Report

Merging #952 (c11612b) into main (67e1231) will increase coverage by 0.25%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##             main     #952      +/-   ##
==========================================
+ Coverage   69.75%   70.00%   +0.25%     
==========================================
  Files         120      120              
  Lines        5475     5475              
==========================================
+ Hits         3819     3833      +14     
+ Misses       1285     1271      -14     
  Partials      371      371              
Impacted Files Coverage Δ
pkg/buildpod/generator.go 77.27% <50.00%> (+10.60%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 67e1231...c11612b. Read the comment docs.

@matthewmcnew matthewmcnew merged commit eb84c15 into main Apr 26, 2022
@matthewmcnew matthewmcnew deleted the 921-binding-to-a-provisionedservice-object-swallows-errors-and-proceeds-with-no-logging branch April 26, 2022 18:35
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.

Binding to a ProvisionedService object swallows errors and proceeds with no logging
4 participants