-
-
Notifications
You must be signed in to change notification settings - Fork 216
Comparing changes
Open a pull request
base repository: alexjustesen/speedtest-tracker
base: 1.x
head repository: NodoBTCboricua/speedtest-tracker
compare: 1.x
- 14 commits
- 518 files changed
- 1 contributor
Commits on Feb 21, 2026
-
Configuration menu - View commit details
-
Copy full SHA for fdb4ef4 - Browse repository at this point
Copy the full SHA fdb4ef4View commit details -
Enhance ping monitoring feature with additional scheduling options an…
…d improved error handling
Configuration menu - View commit details
-
Copy full SHA for 770429b - Browse repository at this point
Copy the full SHA 770429bView commit details -
Configuration menu - View commit details
-
Copy full SHA for 8abf189 - Browse repository at this point
Copy the full SHA 8abf189View commit details -
Refactor ping monitoring feature to streamline scheduling logic and e…
…nhance error reporting
Configuration menu - View commit details
-
Copy full SHA for a64442c - Browse repository at this point
Copy the full SHA a64442cView commit details -
Refactor ping monitoring feature to optimize scheduling logic and imp…
…rove overall performance
Configuration menu - View commit details
-
Copy full SHA for 8675205 - Browse repository at this point
Copy the full SHA 8675205View commit details -
Refactor ping monitoring feature to enhance scheduling efficiency and…
… improve error handling mechanisms
Configuration menu - View commit details
-
Copy full SHA for e2dfcbe - Browse repository at this point
Copy the full SHA e2dfcbeView commit details
Commits on Feb 22, 2026
-
chore: update file permissions to executable (755)
Update file modes from 100644 to 100755 across the repository. This change grants execute permissions to configuration files, source code, assets, and documentation to ensure consistent access rights.
Configuration menu - View commit details
-
Copy full SHA for df941fb - Browse repository at this point
Copy the full SHA df941fbView commit details
Commits on Feb 23, 2026
-
feat(ping): add configurable packet count to ping targets
Introduces the ability to define the number of packets sent per ping execution for specific targets. This improves flexibility for latency and stability monitoring. Changes include: - Added `packet_count` column to `ping_targets` table via migration. - Updated `PingTarget` model with fillable and cast definitions. - Added input field to the Filament `PingTargetForm`. - Updated `RunPingTargetJob` to utilize the configured packet count. - Added translation strings for English and Spanish.
Configuration menu - View commit details
-
Copy full SHA for 4e93e99 - Browse repository at this point
Copy the full SHA 4e93e99View commit details -
feat: add packet loss tracking and update ping configuration
- Update `PingTargetForm` to use `Select` components for `interval_seconds` and `packet_count` with predefined options instead of free-text inputs. - Add `packet_loss` attribute to the `PingResult` model and casts. - Capture and store packet loss percentage in `RunPingTargetJob` during ping execution. - Add a dedicated `scheduler` service to `compose.yaml` to run `php artisan schedule:work`.
Configuration menu - View commit details
-
Copy full SHA for 06bb8de - Browse repository at this point
Copy the full SHA 06bb8deView commit details -
fix(widgets): remove static modifier from pollingInterval
The `$pollingInterval` property in `IcmpStatusWidget` was incorrectly defined as static. This change removes the static modifier to ensure it functions correctly as an instance property within the Filament widget lifecycle.
Configuration menu - View commit details
-
Copy full SHA for ef76480 - Browse repository at this point
Copy the full SHA ef76480View commit details -
feat: add queue worker and enhance ping visualization
- Add dedicated `queue` service to `compose.yaml` for background processing - Update `PingTargetTable` to dynamically format intervals in hours, minutes, or seconds - Include average latency statistics in `IcmpStatusWidget` description - Enable average line for all targets and add `spanGaps` support in `PingLatencyChartWidget` - Update translation labels to reflect dynamic interval formatting
Configuration menu - View commit details
-
Copy full SHA for b3a07ab - Browse repository at this point
Copy the full SHA b3a07abView commit details -
feat(results): enhance table actions, persistence, and form schemas
- Enable session persistence for `ResultTable` filters and columns to retain user preferences across reloads. - Add bulk delete and export actions to the `PingResultTable` toolbar to improve data management. - Fix component usage in `ResultForm` by replacing `TextEntry` (infolist) with `Placeholder` (form) for correctly displaying read-only metadata.
Configuration menu - View commit details
-
Copy full SHA for a9912ee - Browse repository at this point
Copy the full SHA a9912eeView commit details -
feat(results): update table column visibility and state persistence
- Set 'External IP' and 'Service' columns to be visible by default instead of hidden. - Enable session persistence for sorting, global search, and column searches to improve user experience by retaining table state across reloads.
Configuration menu - View commit details
-
Copy full SHA for b42b160 - Browse repository at this point
Copy the full SHA b42b160View commit details
Commits on Feb 25, 2026
-
feat(widgets): enhance ICMP status info and chart average visibility
- Added the last run timestamp to the ICMP status widget description to provide context on when the target was last checked. - Replaced static flat average lines in the Recent Download, Upload, and Ping charts with dynamic moving averages for better trend analysis. - Removed the average line from the multi-target Ping Latency chart to reduce visual clutter.
Configuration menu - View commit details
-
Copy full SHA for cf0a0bd - Browse repository at this point
Copy the full SHA cf0a0bdView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 1.x...1.x