Skip to content

pool: fix notify on remove a connection #385

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

Conversation

oleg-jukovec
Copy link
Collaborator

@oleg-jukovec oleg-jukovec commented Feb 29, 2024

ConnectionPool.Remove() does not notify a ConnectionHandler on an instance removing from the pool.

I didn't forget about (remove if it is not applicable):

ConnectionPool.Remove() does not notify a ConnectionHandler on
an instance removing from the pool.
@oleg-jukovec oleg-jukovec force-pushed the oleg-jukovec/pool-remove-does-not-call-deactivated branch from 677532a to ebb4c08 Compare February 29, 2024 07:38
@oleg-jukovec oleg-jukovec marked this pull request as ready for review February 29, 2024 08:41
@oleg-jukovec oleg-jukovec requested review from better0fdead and removed request for psergee February 29, 2024 11:01
@oleg-jukovec oleg-jukovec merged commit c070b26 into master Feb 29, 2024
@oleg-jukovec oleg-jukovec deleted the oleg-jukovec/pool-remove-does-not-call-deactivated branch February 29, 2024 13:51
oleg-jukovec added a commit that referenced this pull request Mar 6, 2024
Overview

    The small release improves the ConnectionPool. The ConnectionPool
    is no longer required execute access for `box.info` from a user
    for Tarantool >= 3.0.0.

Breaking changes

    There are no breaking changes in the release.

New features

    `execute` access for `box.info` is no longer required for
    ConnectionPool for a Tarantool version >= 3.0.0 (#380).

Bugfixes

    `ConnectionPool.Remove()` does not notify a `ConnectionHandler`
    after an instance is already removed from the pool (#385).
@oleg-jukovec oleg-jukovec mentioned this pull request Mar 6, 2024
oleg-jukovec added a commit that referenced this pull request Mar 6, 2024
Overview

    The small release improves the ConnectionPool. The ConnectionPool
    is no longer required execute access for `box.info` from a user
    for Tarantool >= 3.0.0.

Breaking changes

    There are no breaking changes in the release.

New features

    `execute` access for `box.info` is no longer required for
    ConnectionPool for a Tarantool version >= 3.0.0 (#380).

Bugfixes

    `ConnectionPool.Remove()` does not notify a `ConnectionHandler`
    after an instance is already removed from the pool (#385).
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