Skip to content

[packet-slapper]: Bump version to 1.0.4 - #445

Merged
dispatcharr-plugins-bot[bot] merged 10 commits into
Dispatcharr:mainfrom
write-erase:packet-slapper
Oct 15, 2026
Merged

dispatcharr-plugins-bot[bot] merged 10 commits into
Dispatcharr:mainfrom
write-erase:packet-slapper

Conversation

@write-erase

Copy link
Copy Markdown
Contributor

Small cleanups and hardening

  • The plugin now keeps the Ookla speedtest CLI up to date by itself. On the first speedtest after Dispatcharr starts, it checks Ookla's download server for a newer release and installs it, so a restart is all it takes. A new release is test-started before it replaces the working one, and if the check or download fails the installed CLI keeps being used. SPEEDTEST_CLI_VERSION is gone; SPEEDTEST_CLI_BASE_VERSION is only the starting point for a first install.
  • The default timezone is now UTC instead of US Central. Installs that already saved a timezone keep it; installs that never touched the setting will now see UTC.
  • The Discord webhook response is now closed after each post instead of being left for garbage collection.
  • The "can't read saved settings" warning now says what it actually knows (no saved settings found, or the database is unreachable), and it can fire again if the problem comes back.
  • Removed an unused stat import.
  • A scheduled run that is skipped because someone is watching now retries after 30 minutes instead of waiting a full interval (never longer than the interval itself).
  • Skipped runs no longer replace the last real result in Status. Status shows "Last run" for the last actual test, plus a separate note such as "Skipped 3 times in a row because someone was watching". After three skips in a row it suggests the Check Active Streams button, in case something is being detected that shouldn't be. A real run resets the count.
  • Status now shows which speedtest CLI version is installed.
  • The "check that Dispatcharr can reach install.speedtest.net" hint now appears only on download failures, not when a new CLI fails its startup test.
  • The settings the background scheduler falls back on are now swapped in one step instead of cleared and refilled, which removes a very small window where the scheduler could see them empty.

About this submission

Pre-submission checklist

If this is a new plugin:

  • Plugin folder is named lowercase-kebab-case
  • plugin.json contains all required fields (name, version, description, author or maintainers, license)
  • My GitHub username is in author or maintainers
  • license is a valid OSI-approved SPDX identifier (e.g. MIT, Apache-2.0)
  • I have tested the plugin against a running Dispatcharr instance

If this is an update to an existing plugin:

  • version in plugin.json is incremented (unless this is a metadata-only change - see Versioning)
  • I am listed in author or maintainers of the existing plugin

write-erase and others added 9 commits September 27, 2026 12:12
* Add Packet Slapper plugin
- Packet loss shows N/A when the Ookla server doesn't report it. It used to show 0%, which isn't the same thing.

- Discord embed fields are inline now, so the card is two rows of three instead of one tall stack. That was the original layout, it just never got switched on.

- Plain-text Discord error messages are cut at 1900 characters. A long error could go over Discord's 2000 limit and get rejected.

- Server ID only accepts 0-9. `str.isdigit()` lets things like superscript digits through.

- The speedtest CLI gets re-downloaded when `SPEEDTEST_CLI_VERSION` changes. The installed version is saved in `bin/speedtest.version`. Upgrading from 1.0.0 does one fresh download since there's no version file yet.

- The CLI is written to a temp file in `bin/` and swapped in with `os.replace`, so a download that dies partway can't leave a broken `speedtest` that passes the executable check forever.

- If the settings can't be read from the DB and nobody has clicked a button yet, the scheduler waits and tries again instead of assuming it's enabled. `stop()` also clears the cached settings.

- A scheduled run that finds another test already running retries after 60 seconds. Before, it waited a full interval, which on a 24 hour schedule means a lost day.

- Removed the Tips entry from `actions` in plugin.json. It isn't an action, so it showed up as a button that did nothing but return "Unknown action". The Scheduler Status and Run Now descriptions already say the same thing.
- Introduced a new logo.
@dispatcharr-plugins-bot dispatcharr-plugins-bot Bot added the Plugin Update A plugin already in the repository is being updated. label Oct 15, 2026
@dispatcharr-plugins-bot

This comment has been minimized.

1 similar comment
@dispatcharr-plugins-bot

Copy link
Copy Markdown

Plugin Validation Results

Modified plugins: 1

Plugin: packet-slapper

Runs scheduled or on-demand Ookla Speedtests through Dispatcharr to measure speed and latency.

Source Repository

Check Status Details
Required fields ✅ All required fields present
Release artifact ✅ Artifact reachable at resolved URL
Maintainers ✅ write-erase
License ✅ MIT - MIT License
Permission ✅ You have permission to modify this plugin
Version ✅ 1.0.4
Version bump ✅ 1.0.3 → 1.0.4

View release v1.0.4 on GitHub · Compare v1.0.3...v1.0.4


🎉 All validation checks passed!

This PR modifies 1 plugin(s) and all checks have passed.

@dispatcharr-plugins-bot
dispatcharr-plugins-bot Bot merged commit 172f4b4 into Dispatcharr:main Oct 15, 2026
12 checks passed
@dispatcharr-plugins-bot dispatcharr-plugins-bot Bot added the Auto Merged PR was merged automatically after validation label Oct 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Auto Merged PR was merged automatically after validation Plugin Update A plugin already in the repository is being updated.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant