Skip to content

Do not return NULL when failing to parse a key provider config#562

Open
jeltz wants to merge 2 commits intopercona:mainfrom
jeltz:do-not-return-null-parse-error
Open

Do not return NULL when failing to parse a key provider config#562
jeltz wants to merge 2 commits intopercona:mainfrom
jeltz:do-not-return-null-parse-error

Conversation

@jeltz
Copy link
Copy Markdown
Collaborator

@jeltz jeltz commented Apr 2, 2026

The bad habit of returning NULL when we fail to parse a value from the key provider has a high risk of hiding bugs and data corrupt by just making it seem like the key provider never existed in the first place.

jeltz added 2 commits April 2, 2026 20:49
The bad habit of returning NULL when we fail to parse a value from the
key provider has a high risk of hiding bugs and data corrupt by just
making it seem like the key provider never existed in the first place.
These two functions being separate made the code harder to read.
@codecov-commenter
Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 61.90476% with 8 lines in your changes missing coverage. Please review.
✅ Project coverage is 57.51%. Comparing base (6ca54ed) to head (c0055ea).

❌ Your project status has failed because the head coverage (76.02%) is below the target coverage (90.00%). You can increase the head coverage or adjust the target coverage.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #562      +/-   ##
==========================================
+ Coverage   57.47%   57.51%   +0.04%     
==========================================
  Files          68       68              
  Lines       10709    10703       -6     
  Branches     2640     2637       -3     
==========================================
+ Hits         6155     6156       +1     
+ Misses       3292     3288       -4     
+ Partials     1262     1259       -3     
Components Coverage Δ
access 80.67% <ø> (ø)
bin 63.76% <ø> (ø)
catalog 78.42% <61.90%> (+0.55%) ⬆️
common 76.47% <ø> (ø)
encryption 57.98% <ø> (ø)
keyring 65.12% <ø> (ø)
src 87.33% <ø> (ø)
smgr 89.54% <ø> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

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