WWill GreenbergForbid ??= in the codebase
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
Forbid ??= in the codebase | 12 天前 | |
UI: Enforce snake case for functions It's more common to write functions in camelCase in JS, so some people started doing it, including me. But the majority of the codebase is snake_case, so let's enforce that. | 7 个月前 | |
Add error reporting to the daemon web UI This error reporting comes in two forms: - Errors updating the UI - Errors with user actions The former is displayed as one error until a refresh succeeds again. The latter creates an number of persistent errors until they are cleared by the user. | 1 年前 | |
Add no-NAS analyzer and no-diag UI alert (#1132) * Add no-NAS analyzer and no-diag alerts Fix https://github.com/EFForg/rayhunter/issues/882 An alternative to https://github.com/EFForg/rayhunter/pull/1107 where the no-NAS analyzer is stripped down, and the analyzer interface is kept minimal to not use system time. This simplifies code but prevents the analyzer from emitting alerts if there are no packets at all. Instead, we add a bespoke alerting component to the UI that compares packet timestamps with current system time. If the two are far apart, there is a warning in the UI. The warning goes away if we see packets again. Display or ntfy is not implemented. * Address no-NAS analyzer review feedback * add newline * Only update timestamps for skipped packets * Assert event and analyzer counts match * roll back changes to gsmtap_parser, add timestamp to analyze_.. functions, simplify analyzer * fix bugs in rayhunter-check and UI that would hide findings on skipped messages (past recordings only) * Fix prettier formatting in analysis.svelte.ts | 26 天前 | |
Add no-NAS analyzer and no-diag UI alert (#1132) * Add no-NAS analyzer and no-diag alerts Fix https://github.com/EFForg/rayhunter/issues/882 An alternative to https://github.com/EFForg/rayhunter/pull/1107 where the no-NAS analyzer is stripped down, and the analyzer interface is kept minimal to not use system time. This simplifies code but prevents the analyzer from emitting alerts if there are no packets at all. Instead, we add a bespoke alerting component to the UI that compares packet timestamps with current system time. If the two are far apart, there is a warning in the UI. The warning goes away if we see packets again. Display or ntfy is not implemented. * Address no-NAS analyzer review feedback * add newline * Only update timestamps for skipped packets * Assert event and analyzer counts match * roll back changes to gsmtap_parser, add timestamp to analyze_.. functions, simplify analyzer * fix bugs in rayhunter-check and UI that would hide findings on skipped messages (past recordings only) * Fix prettier formatting in analysis.svelte.ts | 26 天前 | |
Add reanalyze button Add a reanalyze button for individual recordings in the analysis dropdown As part of this, split out ApiRequestButton so that state transitions (clickable -> loading/disabled -> done) can be shared across start/stop recording and this new button. Other buttons might benefit from this as well. Also fix a broken checkbox while we're here. | 1 年前 | |
Split bin dir into separate daemon and check dirs This lets us manage their increasingly disparate dependencies separately | 1 年前 | |
requests addressed, better error handling, more logging, small text corrections | 4 个月前 | |
Split bin dir into separate daemon and check dirs This lets us manage their increasingly disparate dependencies separately | 1 年前 | |
downgrade tailwind for now, and fix build errors | 5 个月前 | |
Add visual for GUI; fix clippy issue. | 7 个月前 | |
Load analyzers from backend, unify names Remove all checkboxes from the frontend and load available analyzers + descriptions from Rust. This also aligns all analyzer names across documentation, config form and recording metadata. | 12 天前 |