Skip to content

Conversation

@harikrishna-patnala
Copy link
Contributor

Description

This PR fixes an NPE in case during the development or any other case when there is an extra column in the tables that are not there in the corresponding VO.

Types of changes

  • Breaking change (fix or feature that would cause existing functionality to change)
  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Enhancement (improves an existing feature and functionality)
  • Cleanup (Code refactoring and cleanup, that may add test cases)
  • Build/CI
  • Test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

  • Major
  • Minor

Bug Severity

  • BLOCKER
  • Critical
  • Major
  • Minor
  • Trivial

Screenshots (if appropriate):

How Has This Been Tested?

How did you try to break this feature and the system with this change?

@harikrishna-patnala
Copy link
Contributor Author

@blueorangutan package

@blueorangutan
Copy link

@harikrishna-patnala a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

@codecov
Copy link

codecov bot commented Jan 19, 2026

Codecov Report

❌ Patch coverage is 0% with 9 lines in your changes missing coverage. Please review.
✅ Project coverage is 16.23%. Comparing base (a4b1a27) to head (0679607).
⚠️ Report is 1 commits behind head on 4.20.

Files with missing lines Patch % Lines
...c/main/java/com/cloud/utils/db/GenericDaoBase.java 0.00% 9 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff            @@
##               4.20   #12464   +/-   ##
=========================================
  Coverage     16.23%   16.23%           
- Complexity    13380    13382    +2     
=========================================
  Files          5657     5657           
  Lines        499035   499044    +9     
  Branches      60567    60568    +1     
=========================================
+ Hits          81029    81036    +7     
- Misses       408969   408972    +3     
+ Partials       9037     9036    -1     
Flag Coverage Δ
uitests 4.03% <ø> (ø)
unittests 17.09% <0.00%> (+<0.01%) ⬆️

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.

🚀 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.

@blueorangutan
Copy link

Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✖️ debian ✔️ suse15. SL-JID 16417

@DaanHoogland DaanHoogland added this to the 4.20.3 milestone Jan 19, 2026
Copy link
Contributor

@DaanHoogland DaanHoogland left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@harikrishna-patnala , I don’t see any of the possible NPEs in the old code being mitigated in the new code. Am I missing something?

@harikrishna-patnala
Copy link
Contributor Author

@harikrishna-patnala , I don’t see any of the possible NPEs in the old code being mitigated in the new code. Am I missing something?

This is happening during any development or when an extra column was added in the table and no reference in the VO. Here few safe checks are added for that.

}
assert (attr != null) : "How come I can't find " + meta.getCatalogName(index) + "." + meta.getColumnName(index);
setField(entity, attr.field, rs, index);
assert (attr != null) : "How come I can't find " + tableName + "." + columnName;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can remove the assert

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.

3 participants