Skip to content

Ignore misses for lock requests#49

Merged
cezmunsta merged 1 commit into
masterfrom
issue48
Jun 24, 2021
Merged

Ignore misses for lock requests#49
cezmunsta merged 1 commit into
masterfrom
issue48

Conversation

@cezmunsta
Copy link
Copy Markdown
Owner

Due to the locks using the same code as the config requests,
warning messages previously appeared when there is no lock, which
is the scenario that you want to have. The message is no longer
emitted when making a lock request.

  • Updated cmd.getRawConnection to check if the key is prefixed
    with the LockPrefix, returning 'no lock found' instead of
    'no match found' when true
  • Updated cmd.TestGetRawConnection to ensure that a lock request
    returns 'no lock found'

Fixes #48

Due to the locks using the same code as the config requests,
warning messages previously appeared when there is no lock, which
is the scenario that you want to have. The message is no longer
emitted when making a lock request.

* Updated `cmd.getRawConnection` to check if the key is prefixed
  with the `LockPrefix`, returning 'no lock found' instead of
  'no match found' when true
* Updated `cmd.TestGetRawConnection` to ensure that a lock request
  returns 'no lock found'

Fixes #48
@cezmunsta cezmunsta added the enhancement New feature or request label Jun 24, 2021
@cezmunsta cezmunsta self-assigned this Jun 24, 2021
@cezmunsta cezmunsta merged commit cc14e0a into master Jun 24, 2021
@cezmunsta cezmunsta deleted the issue48 branch June 24, 2021 09:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Hide "Unable to find connection for" messages for locks

1 participant