-
Notifications
You must be signed in to change notification settings - Fork 88
No error on failure to parse TcOpts #244
Comments
Hello @DieracDelta This is a problem I'm aware of but don't have time to dedicate to properly fix. There are actually two problems:
The first issue really is a terrible limitation which is going to bite many people but fixing it is not trivial :( The second issue is more easily fixable. I'm not sure whether I'm going to have time though. Maybe next Sunday, but no promise. Otherwise, it's going to be in April at best since I'll be AFK for three weeks from March 18th. |
Hi, @little-dude Is it possible to release a new version before you AFK? |
Sorry, @wllenyj I didn't manage to find time to do it. The last two weeks have been crazy at work, and I spent the little free time I had to help out some of the many Ukrainians refugees who are arriving in Berlin. |
@little-dude Wow, It's so cool. |
If the TcOpts fail to parse in one of the qdiscs here, the entire qdisc is skipped. I see the error being generated with the
.context()
here, but for some reason it's not making its way back up to the stream. Any advice on how to access the errors without dropping in a bunch of print statements?The text was updated successfully, but these errors were encountered: