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

send user/ip blocked signal only once #137

Merged
merged 1 commit into from
Sep 16, 2019

Conversation

horida
Copy link

@horida horida commented Sep 9, 2019

Only send the username/IP blocked signal if the user/IP is actually blocked.

Like this multiple sending of the signal is avoid. The block is set even though to avoid race conditions. There is still a slight chance the signal is send twice, but that should be OK.

@williamboman
Copy link
Contributor

Perhaps a unit test could be nice? There's already a SignalTest-somethingsomething test class ;)

@coveralls
Copy link

coveralls commented Sep 9, 2019

Coverage Status

Coverage increased (+0.1%) to 90.237% when pulling b47eed5 on horida:send_blocked_signal_only_once into fcfa88d on kencochrane:master.

@horida horida force-pushed the send_blocked_signal_only_once branch from 5112cb7 to b47eed5 Compare September 9, 2019 12:45
Copy link
Collaborator

@kencochrane kencochrane left a comment

Choose a reason for hiding this comment

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

LGTM

@kencochrane kencochrane merged commit ce95906 into jazzband:master Sep 16, 2019
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.

None yet

4 participants