Skip to content

Add ruby error assertion for test_rejects_uuid_result - #725

Open
klobuczek wants to merge 2 commits into
neo4j-drivers:6.xfrom
klobuczek:ruby-uuid-result-error
Open

Add ruby error assertion for test_rejects_uuid_result#725
klobuczek wants to merge 2 commits into
neo4j-drivers:6.xfrom
klobuczek:ruby-uuid-result-error

Conversation

@klobuczek

Copy link
Copy Markdown
Contributor

test_rejects_uuid_result (UUID over Bolt 6.0) branches on driver_name for the expected error, but has no ruby case, so the Ruby driver hits raise NotImplementedError(f"Add error assertion for {driver_name}").

The Ruby driver's JRuby implementation wraps the official Java driver, so a UUID PackStream marker (0xE0) received over Bolt 6.0 surfaces the same error as the Java driver. This adds "ruby" alongside "java", asserting "unknown packstream" and "e0".

All other UUID tests (test_uuid, test_uuid_as_node_property, test_uuid_in_list, test_uuid_in_map, test_rejects_uuid_parameter) already pass for the Ruby driver unchanged.

Copilot AI review requested due to automatic review settings July 22, 2026 04:54

Copilot AI 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.

Pull request overview

Adds the missing Ruby-specific error assertion in test_rejects_uuid_result so the Ruby driver no longer falls into the NotImplementedError branch when receiving a UUID PackStream marker (0xE0) over Bolt 6.0.

Changes:

  • Extend the Java error-assertion branch to also cover the Ruby driver.
  • Assert Ruby error message contains "unknown packstream" and "e0" (matching the Java/JRuby-wrapped behavior described in the PR).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@robsdedude robsdedude left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

💎

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