Skip to content

Conversation

@bigmontz
Copy link
Contributor

@bigmontz bigmontz commented Sep 8, 2025

This status represents invalid elements on Packstream messages.

@bigmontz bigmontz added documentation Improvements or additions to documentation gqlstatus-errors labels Sep 8, 2025
@renetapopova renetapopova self-assigned this Sep 8, 2025
@renetapopova renetapopova added 2025.09 and removed documentation Improvements or additions to documentation gqlstatus-errors labels Sep 9, 2025
= 22N60

== Status Description
error: data exception - illegal element. Encountered illegal `{ <<item>> }` element: `{ <<msg>> }`.
Copy link
Collaborator

Choose a reason for hiding this comment

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

When we use { <<msg>> }, we omit the full stop. You'll need to update the codebase as well.

Suggested change
error: data exception - illegal element. Encountered illegal `{ <<item>> }` element: `{ <<msg>> }`.
error: data exception - illegal element. Encountered illegal `{ <<item>> }` element. Reason: `{ <<msg>> }`

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This will need to update the code. I will create another PR in the other repo also.

Copy link
Contributor Author

@bigmontz bigmontz Sep 9, 2025

Choose a reason for hiding this comment

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

@renetapopova Actually, the current message templates leads to message like 22N60: Encountered illegal root element: Expected struct.. In case of updating the message, the same message will look like this 22N60: Encountered illegal root element. Reason: Expected struct.

@renetapopova renetapopova force-pushed the dev-22N60 branch 2 times, most recently from 2c4b932 to ab8b6eb Compare September 10, 2025 15:13
@renetapopova renetapopova self-requested a review September 10, 2025 15:17
Copy link
Collaborator

@renetapopova renetapopova left a comment

Choose a reason for hiding this comment

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

I added a suggestion. What do you think?

@neo4j-docops-agent
Copy link
Collaborator

neo4j-docops-agent commented Sep 11, 2025

Thanks for the documentation updates.

The preview documentation has now been torn down - reopening this PR will republish it.

@renetapopova renetapopova merged commit be4de65 into dev Sep 11, 2025
4 checks passed
@renetapopova renetapopova deleted the dev-22N60 branch September 11, 2025 09:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants