Skip to content

Access vector_data without risk of panicking#7469

Merged
timvisee merged 2 commits intodevfrom
segment-get-vector-checked
Oct 29, 2025
Merged

Access vector_data without risk of panicking#7469
timvisee merged 2 commits intodevfrom
segment-get-vector-checked

Conversation

@timvisee
Copy link
Member

When accessing vector_data, always use .get() rather than [] to not risk panicking.

Semi-related: #7463 (comment)

All Submissions:

  • Contributions should target the dev branch. Did you create your branch from dev?
  • Have you followed the guidelines in our Contributing document?
  • Have you checked to ensure there aren't other open Pull Requests for the same update/change?

@timvisee timvisee changed the title Segment get vector checked Access vector_data without risk of panicking Oct 29, 2025
coderabbitai[bot]

This comment was marked as resolved.

@qdrant qdrant deleted a comment from coderabbitai bot Oct 29, 2025
@timvisee timvisee merged commit 4557975 into dev Oct 29, 2025
15 checks passed
@timvisee timvisee deleted the segment-get-vector-checked branch October 29, 2025 09:35
timvisee added a commit that referenced this pull request Nov 14, 2025
* Get vector data checked to prevent panic

* Add invalid vector name error helper
@timvisee timvisee mentioned this pull request Nov 14, 2025
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