Skip to content

GT-363 Improve ArangoDB version detection #356

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

Merged
merged 4 commits into from
Mar 27, 2023

Conversation

nikita-vanyasin
Copy link
Contributor

log.force-direct option forces arangod to write output using main thread - ensuring the whole log output will be flushed before return

Also some refactoring of DatabaseVersion to improve readability.

The retry logic probably can be deleted, but let's wait if this warning will disappear completely.

log.force-direct option forces arangod to write output using main thread - ensuring the whole log output will be flushed before return

Also some refactoring of DatabaseVersion to improve readability
@nikita-vanyasin nikita-vanyasin requested a review from ajanikow March 6, 2023 15:58
Copy link
Contributor

@informalict informalict left a comment

Choose a reason for hiding this comment

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

lgtm with one comment

Copy link
Contributor

@informalict informalict left a comment

Choose a reason for hiding this comment

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

lgtm

@ajanikow ajanikow merged commit b023d5d into master Mar 27, 2023
@ajanikow ajanikow deleted the improvement/version-detection branch March 28, 2023 01:00
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