Skip to content

fix: CHF panics on wrong ChargingDataRef in partial-record reopen#71

Merged
Alonza0314 merged 1 commit into
free5gc:mainfrom
solar224:fix/chf-convergedcharging-wrong-ref-partial-reopen-guard
Apr 9, 2026
Merged

fix: CHF panics on wrong ChargingDataRef in partial-record reopen#71
Alonza0314 merged 1 commit into
free5gc:mainfrom
solar224:fix/chf-convergedcharging-wrong-ref-partial-reopen-guard

Conversation

@solar224

Copy link
Copy Markdown
Contributor
  • Fixes a panic when a wrong ChargingDataRef is used in partial-record flows.
  • Adds session validation in ChargingDataUpdate: unknown or nil charging-session context returns a controlled 404 ProblemDetails.
  • Removes the unsafe fallback to the latest record and keeps ue.Cdr[chargingSessionId] aligned during partial-record rollover.
  • Hardens OpenCDR(..., partialRecord=true) with defensive nil/session checks.
  • Adds tests.

Fixes: free5gc/free5gc#950

@d11nn d11nn left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Comment thread internal/sbi/processor/converged_charging.go
@Alonza0314
Alonza0314 merged commit dce8ddc into free5gc:main Apr 9, 2026
3 checks passed
@solar224
solar224 deleted the fix/chf-convergedcharging-wrong-ref-partial-reopen-guard branch April 20, 2026 17:06
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.

Bugs] CHF POST /nchf-convergedcharging/v3/chargingdata/{ChargingDataRef}/update panics on wrong ChargingDataRef in partial-record reopen

3 participants