That's not how you motivate people to fix things. Piling on to a bug report just obscures relevant information and makes it *less* likely to get fixed.
I understand that it's frustrating to not see progress on your pet bug, but pile-ons do not make progress more likely.
I've seen them do exactly that. It depends on the situation of course, but "nobody remembering there was something" isn't all that unlikely.
Yep, that's fishy indeed. Still, doing it right won't solve the problem here either (see PR, there are workarounds solving it). Something prevents putting a vtnet interface in promisc mode when it's up. Adding to the mystery is nobody could tell so far why it worked on 12.x.
This isn't an attack. It's an observation of what actually works, in the general case, to get things fixed. Any given bug competes for time and attention against literally thousands of others. There are more bugs that FreeBSD volunteers have time to deal with. Making it more noisy just reduces the overall amount of work that gets done, and reduces the value of the bug tracker. Don't.
That's almost always the case. (In my spare time, I do what I can to help, I just concentrate on ports…)
PRs rotting unnoticed don't add value, either. My current weirdest example: 7yo bug, 3yo PR, found it by accident and the fix is hilariously trivial. I really think some nudging might have helped it. I'm definitely not the only one capable of coming up with this "elaborate" patch
There's always some risk involved.
