8 of 13 OIDs were pointing to wrong MIB columns:
- RSSI: was reading ubntWlStatSignal(.5), now ubntWlStatRssi(.6)
- Quality: was reading ubntWlStatSignal(.5), now ubntAirMaxQuality(.6.1.3)
- Tx Rate: was reading ubntWlStatSsid(.2), now ubntWlStatTxRate(.9)
- Rx Rate: was reading ubntWlStatHideSsid(.3), now ubntWlStatRxRate(.10)
- Capacity: was reading ubntWlStatTxRate(.9), now ubntAirMaxCapacity(.6.1.4)
- Distance: was reading ubntWlStatSecurity(.11), now ubntRadioDistance(.1.1.7)
- Utilization: was reading WDS/Repeater booleans(.12/.13), now ubntAirMaxAirtime(.6.1.7)
- Added Signal Level sensor from ubntWlStatSignal(.5)
All 7 OIDs were reading from wrong SNMP table/columns. Frequency and
power config values pointed at the status table instead of the config
table, and capacity/signal columns pointed at unrelated fields like
radio temperature and boolean flags.
Corrected OIDs to match UBNT-AirFIBER-MIB structure:
- Frequency/power: config table (.3.1) entries 5, 6, 9
- Signal: status table (.3.2) entries 11, 14
- Capacity: status table (.3.2) entries 5, 6 with 1M divisor
The test makes a real HTTP call to GitHub which can fail or return
different responses depending on network conditions, rate limits, etc.
Tagged as :integration to exclude from normal test runs, consistent
with other GitHub API tests in ReleaseCheckerTest.
- Prefix unused variables with underscore in subscriber_matching_test.exs
- Fix unused integration_id parameters in gaiia_fixtures.ex
- Remove duplicate site_fixture/1 from access_control_test.exs
- Use public site_fixture/2 from OrganizationsFixtures instead
- Remove unused Sites alias from access_control_test.exs
All 19 subscriber matching tests passing with no warnings.
- Made normalize_mac/1 public with comprehensive documentation
- Enhanced normalize_mac to handle:
- Binary MAC addresses (6 bytes) with proper hex conversion
- Short MAC addresses with zero-padding (e.g., 'A:B' -> '0a:0b')
- Colons, dashes, and no-separator formats
- Fixed refresh_links_for_device/1 to return :ok when device not found
(was returning nil, causing test failures)
- Fixed site fallback test to use assigned_network_site_gaiia_id
(string field) instead of network_site_id (FK)
- Simplified account lookup optimization test to remove
non-existent Repo.query_count/1 dependency
All 19 subscriber matching tests now passing:
- 7 normalize_mac/1 tests (binary, colons, dashes, padding, etc.)
- 12 refresh_device_links/1 tests (all match methods, prioritization,
cross-org isolation, etc.)
The ActivityFeed groups sync logs by minute, so when creating test data with
random timestamps, multiple logs could fall within the same minute and get
grouped together, causing the test to fail. Now ensures each sync log is
exactly 60 seconds apart (different minutes).
Add CapacityInsightWorker (every 15 min) that generates critical/warning
insights when backhaul utilization exceeds 90%/75% and auto-resolves
when it drops below 70%.
Add capacity and utilization columns to the device ports tab with
set/clear capacity controls. Add organization-level /capacity page
with summary cards and per-site capacity table. Add capacity summary
card to site show page. Add Capacity link to nav menu.
- Fix ApplicationSetting duplicate key constraint errors in BillingTest and AdminTest
by deleting existing records before inserting new ones in tests
- Increase timeouts for agent_channel debounce tests from 75ms to 200ms
to prevent flaky failures on slower systems (50ms debounce + processing time)
All 7633 tests now pass consistently across multiple runs.
Connection counts (IPv4/IPv6, DHCP leases) were showing as floats
(e.g. 1270.0) in executor output, change detection messages, and
chart tooltips/axes. Now displayed as integers everywhere.
Allow superadmins to override free device limits and per-device pricing
on a per-organization basis. Overrides cascade through subscription
limits, billing calculations, and user-facing settings display.
- Add custom_free_device_limit and custom_price_per_device to organizations
- Add billing_override_changeset with validation
- Update SubscriptionLimits.effective_device_limit to respect overrides
- Update Billing to use effective free count and price per device
- Add Admin.update_billing_overrides with audit logging
- Add override editing UI to /admin/organizations
- Update org settings page to show effective limits/pricing
- Test empty activity list
- Test preseem sync logs with correct DateTime format
- Test duration formatting with integer precision
- Test sync logs without duration
- Test grouping by minute
- Test sorting by timestamp descending
- Test limit parameter
- Test date range filtering
- Test organization isolation
- Test different sync statuses (success, failed, partial)
- Test count_by_type functionality
Reduce Process.sleep delays in event_logger_test from 25ms to 10ms.
These sleeps wait for async event logging to complete.
All tests still pass with shorter delay.
Reduce various test timeouts that were unnecessarily long:
- assert_push timeouts: 150ms → 75ms (6 tests in agent_channel_test)
- refute_receive timeouts: 200ms → 50ms (3 tests in worker tests)
With 50ms channel debounce, 75ms is sufficient for assert_push.
For refute_receive (expecting no message), 50ms is plenty.
Estimated savings: ~600ms across affected tests
- Remove all 25ms and 50ms sleeps from agent_channel_test
- Add poll_until helper for async DB operations (early exit on success)
- Reduce timeout test sleeps from 100ms to 60ms
- Reduce polling delays from 10ms to 5ms in multiple tests
- Remove unnecessary timestamp and background task sleeps
- Reduce circuit breaker recovery sleep from 150ms to 110ms
Performance: 30.3s → 28.3s (6.6% faster)
Total improvement from baseline: 52s → 28.3s (45.6% faster)
My changes added database queries for stuck alert resolution on every poll,
which slightly increased processing time. Increased timeouts from 500ms to 1000ms
and 100ms to 200ms to account for this.
When agents poll devices via SNMP and get successful results, the code was
only processing sensor/interface data without updating device status or
resolving alerts. This caused device_down alerts to persist even after
devices came back online.
This fix:
- Updates device status to 'up' when SNMP polling succeeds
- Auto-resolves any active device_down alerts
- Creates device_up alert (matching DeviceMonitorWorker behavior)
- Broadcasts device_status_changed via PubSub
Also fixes device_up alert creation to include resolved_at timestamp
(matching DeviceMonitorWorker behavior).
Test coverage: Added test verifying auto-resolution when device recovers.
