-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Adjust error for already locked db and prevent level db lock on malformed connstr #18923
Merged
zeripath
merged 5 commits into
go-gitea:main
from
zeripath:improve-warning-for-wrapped-queues
Feb 27, 2022
Merged
Changes from 1 commit
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
a5677e8
Adjust error for already locked db and prevent level db lock on malfo…
zeripath 2a52daf
Merge branch 'main' into improve-warning-for-wrapped-queues
6543 4e58ab2
Merge branch 'main' into improve-warning-for-wrapped-queues
zeripath b125ad2
On close also check datadir
zeripath 58ffaa4
Merge branch 'main' into improve-warning-for-wrapped-queues
zeripath File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we run into this
if
, then neitherconnection
noruri
exists in theLevelDBConnections
.But here the code only append the
connection
to the name list, but nouri
, is it by purpose?In my opinion:
connection
anduri
into the name listSince the old code works, this comment is not a blocker.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It prevents the repeated logging of the same message
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But it's not complete.
Current code It only prevents repeated logging for the new
connection
, but not for the newuri
with the same directory. (that the case 1)And I do not think there will be repeated loggings, the queues call
GetLevelDB
foropen the db
, there seems no repeated calls (so that why case 2 is also fine because there seems to be no repeated log messages)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes it absolutely does prevent repeated logging of the same message. The log message doesn't contain the inferred URI. The point is to tell the server user which strings in their configuration are incorrect.
There are multiple queues. Depending on the order of initialisation and state of the incorrect configuration without this you face repeatedly seeing the same warning message.