Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge dev into 5.x #1929

Merged
merged 909 commits into from
Oct 31, 2024
Merged

Merge dev into 5.x #1929

merged 909 commits into from
Oct 31, 2024

Conversation

renetapopova
Copy link
Contributor

No description provided.

NataliaIvakina and others added 30 commits April 19, 2024 15:08
To make it consistent with the main website page.
Some of the fields in SHOW DATABASES will always be null for databases
that are not running. Update the documentation to reflect this.
Change the `--array-delimiter` example to be set using the code point
for the character `|` (the same used before, so we don't need to change
the CSV content).

This was based on a user feedback, that it was not clear from the
examples that they could have used (and how they could have used)
unicode code points to set the delimiter to arbitrary characters,
including non-printable ones.
This is to avoid confusion, since we *don't* support passing the
delimiter with the `0x` prefix.
…ader`, `server.http.transaction_idle_timeout` (neo4j#1592)

…ader`, `server.http.transaction_idle_timeout`

---------

Co-authored-by: gjmwoods <[email protected]>
Slightly restructure locking section to accommodate these changes.

---------

Co-authored-by: Reneta Popova <[email protected]>
There is a known situation in which a previously `DEALLOCATED` offline
server will transiently show as `DEALLOCATING` when restarting. In
short, it doesn't know it has had it's user databases allocated away so
starts them up, but it will eventually go back to `DEALLOCATED`. This PR
makes this clear and updates the server state diagram.

---------

Co-authored-by: Reneta Popova <[email protected]>
renetapopova and others added 23 commits October 22, 2024 10:18
Reverts neo4j#1920
Wrong branch, should be 5.x
@renetapopova renetapopova changed the title 5.x merge dev Merge dev into 5.x Oct 31, 2024
@neo-technology-commit-status-publisher
Copy link
Collaborator

Thanks for the documentation updates.

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

Copy link
Contributor

@NataliaIvakina NataliaIvakina left a comment

Choose a reason for hiding this comment

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

Looks good! I see all the PRs I've merged earlier 🙂

@renetapopova renetapopova merged commit b109926 into neo4j:5.x Oct 31, 2024
4 checks passed
@renetapopova renetapopova deleted the 5.x-merge-dev branch October 31, 2024 10:47
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.