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

Add interpretation for Pi-hole message type RATE_LIMIT #1859

Merged
merged 1 commit into from
Aug 8, 2021

Conversation

DL6ER
Copy link
Member

@DL6ER DL6ER commented Aug 6, 2021

By submitting this pull request, I confirm the following:

  • I have read and understood the contributors guide, as well as this entire template.
  • I have made only one major change in my proposed changes.
  • I have commented my proposed changes within the code.
  • I have tested my proposed changes, and have included unit tests where possible.
  • I am willing to help maintain this change if there are issues with it later.
  • I give this submission freely and claim no ownership.
  • It is compatible with the EUPL 1.2 license
  • I have squashed any insignificant commits. (git rebase)

What does this PR aim to accomplish?:

Accompany pi-hole/FTL#1155

How does this PR accomplish the above?:

Adding code necessary to pretty-print RATE_LIMIT database messages.

Example:

Screenshot from 2021-08-06 21-34-16

What documentation changes (if any) are needed to support this PR?:

None

@DL6ER DL6ER requested review from a team and yubiuser August 6, 2021 19:41
@DL6ER DL6ER merged commit eb4b88d into release/v5.6 Aug 8, 2021
@DL6ER DL6ER deleted the new/rate_limit_message branch August 8, 2021 06:21
@pralor-bot
Copy link

This pull request has been mentioned on Pi-hole Userspace. There might be relevant details there:

https://discourse.pi-hole.net/t/pi-hole-ftl-v5-9-web-v5-6-and-core-v5-4-released/49544/1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants