Skip to content

Conversation

@Pietfried
Copy link
Contributor

Describe your changes

Fixed issue in V2G CSR generation, where getCpoName().value() always evaluated and could cause a bad optional access

Issue ticket number and link

Checklist before requesting a review

  • I have performed a self-review of my code
  • I have made corresponding changes to the documentation
  • If OCPP 2.0.1 or OCPP2.1: I have updated the OCPP 2.x status document
  • I read the contribution documentation and made sure that my changes meet its requirements

…evaluated and could cause a bad optional access

Signed-off-by: Piet Gömpel <[email protected]>
@Pietfried Pietfried merged commit bd1015b into main Jun 3, 2025
9 of 10 checks passed
@Pietfried Pietfried deleted the fix/v2g-csr-cpo-name branch June 3, 2025 09:09
mlitre pushed a commit that referenced this pull request Jul 16, 2025
…evaluated and could cause a bad optional access (#1089)

Signed-off-by: Piet Gömpel <[email protected]>
Pietfried added a commit that referenced this pull request Nov 19, 2025
…evaluated and could cause a bad optional access (#1089)

Signed-off-by: Piet Gömpel <[email protected]>
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.

3 participants