Open lunkwill42 opened 1 week ago
Descriptor | Linter | Files | Fixed | Errors | Elapsed time |
---|---|---|---|---|---|
✅ PYTHON | black | 2 | 0 | 0.54s | |
✅ PYTHON | isort | 2 | 0 | 0.21s | |
✅ PYTHON | ruff | 2 | 0 | 0.01s |
See detailed report in MegaLinter reports
_Set VALIDATE_ALL_CODEBASE: true
in mega-linter.yml to validate all sources, not only the diff_
3 files 3 suites 53s :stopwatch: 407 tests 407 :white_check_mark: 0 :zzz: 0 :x: 1 221 runs 1 219 :white_check_mark: 2 :zzz: 0 :x:
Results for commit bbcb5be5.
:recycle: This comment has been updated with latest results.
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 98.90%. Comparing base (
58bf6f8
) to head (bbcb5be
).
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
Scope and purpose
The original Zino code will sometimes alter already closed events. Apparently, the reasoning goes that operators sometimes prematurely close events for flapping ports (which Håvard E argues that we should maybe disallow in the future). The original Zino therefore takes care to update both a closed flapping event and the currently open flapping event whenever the link trap code handles a flapping state.
A limitation I immediately see is that multiple closed events could exist for a flapping state (until they are expired/scavenged), but we can only index one of them. As with the original code, there is a bias towards only indexing the latest event.
As a side note: Zino 1 used the terms "pre-closed" and "closed" for events. The former refers to events that have been given a state of CLOSED by an operator. The latter refers to events that have been evicted completely from the running state.
This pull request
get_closed_event()
method to theEvents
class.Events
class.Contributor Checklist