Skip to content

Comments

suppress duplicate reports with -c/-C and -q/-Q#392

Merged
auerswal merged 1 commit intoschweikert:developfrom
auerswal:issue389
Jul 18, 2025
Merged

suppress duplicate reports with -c/-C and -q/-Q#392
auerswal merged 1 commit intoschweikert:developfrom
auerswal:issue389

Conversation

@auerswal
Copy link
Collaborator

@auerswal auerswal commented May 4, 2025

If fping receives a duplicate Echo Reply packet, it reports this. This report was suppressed for loop mode, and for other operating modes where each receive event is reported. Now, this duplicate report is also suppressed when in count mode with options -q, --quiet or -Q, --squiet.

This addresses GitHub issue #389.

@auerswal
Copy link
Collaborator Author

auerswal commented May 4, 2025

I have created this as a draft, because I am not sure if there was a reason to treat loop mode and count mode differently regarding duplicate reporting.

@coveralls
Copy link

coveralls commented May 4, 2025

Coverage Status

coverage: 86.427% (+0.1%) from 86.308%
when pulling 3b7878e on auerswal:issue389
into 6a67865 on schweikert:develop.

@auerswal auerswal linked an issue May 4, 2025 that may be closed by this pull request
@auerswal auerswal marked this pull request as ready for review June 7, 2025 18:45
@auerswal
Copy link
Collaborator Author

Any reasons against aligning duplicate report suppression in count mode with that of loop mode?

Copy link
Collaborator

@gsnw-sebast gsnw-sebast left a comment

Choose a reason for hiding this comment

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

From my point of view, we can take it from there.

If fping receives a duplicate Echo Reply packet, it reports
this.  This report was suppressed for loop mode, and for
other operating modes where each receive event is reported.
Now, this duplicate report is also suppressed when in count
mode with options -q, --quiet or -Q, --squiet.

This addresses GitHub issue schweikert#389.
@auerswal
Copy link
Collaborator Author

While rebasing, I noticed that I had introduced blank lines between changelog items in a block. This was inconsistent with older changelog entries, so I removed those blank lines while solving the CHANGELOG.md merge conflict. I hope that is OK.

@auerswal auerswal merged commit 05b8f45 into schweikert:develop Jul 18, 2025
9 checks passed
@auerswal auerswal deleted the issue389 branch July 18, 2025 17:03
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.

How to prevent fping from displaying duplicate response information?

3 participants