v3.0.0 #1

Merged

zevaryx merged 46 commits from dev into main 2026-11-03 23:28:46 +00:00

Conversation 0 Commits 46 Files changed 39 +3142 -2804

zevaryx commented 2026-11-03 05:54:20 +00:00

Owner

• Copy link
• Copy Markdown

Companion release for the JARVIS 3.0.0 release

Companion release for the JARVIS 3.0.0 release

zevaryx added 37 commits 2026-11-03 05:54:20 +00:00

refactor!: remove the unused reddit and twitter tasks ... 22f08473ba

Neither module was imported, their dependencies were already commented out, and both referenced config.reddit/config.twitter, which do not exist on Config, so they could not even be imported. Also drop their (and Mastodon's) unused settings from sample.env.

BREAKING CHANGE: the reddit and twitter sync tasks are gone.

build: switch from Poetry to uv ... 0da5b9974d

Move metadata to the PEP 621 [project] table and dev tools to a PEP 735 dependency group, replace poetry.lock with uv.lock, and build the Docker image with uv. The project is not packaged (run.py imports it in place), so uv only installs its dependencies.

jarvis-core now comes from its current home, git.zevaryx.com/jarvis/jarvis-core (the old stark-industries path no longer exists), pinned to the same commit the Poetry lock used. Other constraints are unchanged.

fix(deps): declare pytz ... 6ace5f041f

The reminder task imports pytz but it was never declared; it only arrived transitively through older croniter releases, and croniter 6 no longer depends on it.

refactor: remove the unused Prometheus metrics stub ... 3510a7e0f2

StatTracker was never started, so nothing ever exposed the metrics, and most of them belonged to the removed reddit/twitter tasks. Drop the module, the reminder counter call (which also crashed for reminders without a guild channel), and the uvicorn and prometheus-client dependencies.

build(deps)!: upgrade to jarvis-core 2.0 and the latest dependencies ... 4f89b6ce52

jarvis-core 2.0 (Beanie 2 on PyMongo's async client, IDs stored as int64), interactions-py 5.16, croniter 6, pydantic 2.14, pydantic-settings 2.16 and aiohttp 3.14; pytest 9 and black 26 for development. Beanie is now declared directly since the tasks import beanie.operators.

BREAKING CHANGE: requires a database migrated with jarvis-core 2.0's jarvis-migrate.

fix(config): read Mongo settings from MONGO_* variables and ignore unrelated keys ... a84005186e

Mongo was a BaseSettings without an env prefix, instantiated at import time, so it read the unprefixed HOST/USERNAME/PASSWORD/PORT variables (on Windows, USERNAME is the OS login name) while the MONGO_* names documented in sample.env were ignored. Loading sample.env also failed outright because keys meant for other services were rejected as extra inputs.

Mongo now uses the MONGO_ prefix and a per-instance default, extra keys are ignored, empty values fall back to defaults, and MONGO_DATABASE/MONGO_AUTH_SOURCE are passed through to connect(). sample.env lists only what the tasks read, and the config is covered by tests.

fix(tasks): keep scheduled jobs referenced and always clear their queue entry ... f7b362b85d

Jobs were started with a bare asyncio.create_task(runat(...)), which only holds a weak reference, so a sleeping job could be garbage-collected. A job that raised also skipped its queue.remove(), leaving that document stuck as "already scheduled" until restart, and the exception was lost as "Task exception was never retrieved".

Replace runat() with schedule(), which keeps a strong reference, logs failures, and removes the key from the pending set in a finally block. Queues are now sets.

fix(tasks): keep polling loops alive when a pass fails ... 1cd9140f39

None of the task loops caught exceptions, so a single error (a guild the bot left, a deleted channel, a bad document) ended that task for the life of the process. The entry point also awaited the tasks one at a time, so a dead task was never noticed while an earlier one was still running, and its KeyboardInterrupt handler could reference an unbound name.

Each loop body is now a _poll() run by run_forever(), which logs a failed pass and tries again after the usual interval, and the entry point gathers all loops.

fix(ban): lift expired temporary bans ... 2d198605d4

The poll compared Ban.duration (hours, an int) to a datetime, which MongoDB never matches, so temp bans never expired; and had one matched, _unban() was called with five arguments for four parameters. Select bans by the new Ban.expires_at instead, pass the right arguments, and record the Unban from the stored ban when the guild or user can no longer be fetched.

fix(lock): unlock channels even when the guild or channel is gone ... fb6d072abd

The job looked up the guild and channel at schedule time: a guild the bot had left returned None and crashed the loop on guild.fetch_channel, and Guild.fetch_channel raises NotFound for a deleted channel. Fetch the channel when the job fires (Client.fetch_channel returns None for deleted channels), fall back to the channel's guild for locks saved before Lock.guild existed, log permission errors, and always close the lock.

fix(lockdown): lift lockdowns even when the guild is gone ... d9d0e1772d

As with locks, the guild and @everyone role were fetched at schedule time and a guild the bot had left crashed the loop. Resolve them when the lift fires, log permission errors, and always close the lockdown.

fix(tasks): re-check documents when a scheduled job fires ... 7515d19cb2

Jobs acted on the copy loaded when they were queued, up to an hour earlier, so a manual /unlock, /unban or /lockdown end did not cancel them: the lock job re-applied stale permissions, and an expired temp ban unbanned a user who had since been banned again. Each job now reloads its document and skips it if it was lifted, removed or rescheduled; an expired temp ban is closed without unbanning while the user has another active ban.

fix(reminder): handle DM and deleted origin channels and keep undelivered reminders ... 38474c630b

When the DM failed, the fallback assumed a guild text channel and crashed for reminders set in DMs (DMChannel has no guild) or whose channel was deleted (None). A reminder that could not be delivered anywhere was deleted outright, so it was lost.

The fallback now only uses guild channels, undelivered reminders are disabled and kept so /reminders fetch can still show them (the notice also named a nonexistent /reminder fetch command), repeating reminders with an unknown timezone fall back to UTC, and the embed no longer appends the legacy #0 discriminator.

fix(autokick): kick members who have not verified within the grace period ... e691f74a16

The comparison was inverted, so it would have kicked members who joined recently rather than overdue ones; it read role.members from a gateway cache the REST-only tasks client never fills; the member pages it fetched were discarded and the resync timestamps never updated; the kick reason was not an f-string; and a non-numeric setting crashed the loop.

Members are now listed over the REST API and those still holding the unverified role more than N days after joining are kicked. Invalid settings are removed.

fix(util): timestamp embeds in UTC ... de3fc96861

build_embed() defaulted to a naive datetime.now(), which Discord renders as if it were UTC, so embeds showed the server's local time with the wrong offset.

refactor: load the config once and tidy the entry point ... 0e3827387c

start() and _start() each loaded the config, start() declared an unused global, the docstrings described a config path that is not taken, and the login message appended the legacy #0 discriminator. Pass the loaded config through instead, and let interactions.py manage its own event loop.

refactor: replace deprecated Logger.warn() with warning() 8cfb21c8de

build(docker): run the tasks container as an unprivileged user ... 4bdf7d87f8

The image ran the service as root. It only needs to read /app, so run it as a dedicated system user.

docs: describe every task, configuration and development with uv 6fbd9921d8

build(pre-commit): update hooks to their latest releases ... eae6e9c447

pre-commit-hooks 6.0.0, black 26.10.1, isort 9.0.2 and flake8 7.5.0, and pre-commit 4.7.0 itself. isort moves from the archived mirrors-isort repo to PyCQA/isort.

fix: install the project so it reports its real version ... c37581f25b

const.__version__ reads the installed package metadata, but the project was not installed as a package, so it always reported 0.0.0. Build it with uv_build, install it into the environment, and install it non-editable in the Docker image (after a cached dependency-only layer).

chore(release): 0.12.0 99197ad050

test: leave server-managed system collections alone when cleaning up ... 7c28dc1d71

Creating a time-series collection adds system.views, which ordinary users cannot drop, so wiping the test database failed once one existed.

ci: move from GitLab CI to Forgejo Actions ... 4913d83334

Replace the GitLab pipeline with a Forgejo Actions workflow: pre-commit, the test suite against a Mongo service, and a Docker build and push to both registries on main, dev and tags. Secrets used: ZEVARYX_REGISTRY_URL/USERNAME/PASSWORD and DOCKERHUB_REGISTRY_USERNAME/PASSWORD.

build: pin the latest jarvis-core ... 502f0f3f2f

Move the jarvis-core pin from the 2.0.0 release commit to the current rewrite head, matching jarvis-bot. Relock.

ci: run workflows on ubuntu-latest ... bce7ddc7d6

Use the ubuntu-latest runner label instead of docker.

ci: run jobs in the runner image instead of python containers ... 92e065de28

The python job containers have no Node, which actions/checkout needs. Drop them, install uv in the ubuntu-latest image and let it fetch Python, and build Docker images on ubuntu-full-latest.

style: format with black 26 and fix the flake8 findings ... f05899e026

CI runs pre-commit over the whole tree. Apply black 26's formatting and isort, and add the missing docstring to run.py.

ci: Test against Python 3.12-3.15 30cf89cdb8

test: wait for scheduled jobs instead of sleeping a fixed time ... e4a7a85e87

The task tests waited 50 to 200 milliseconds for background jobs, which is too short when MongoDB round trips are slower, as on CI, and they passed or failed depending on timing. Wait on the jobs themselves (or poll for the condition) with a ten second ceiling, so they finish as soon as the work does and cannot race.

ci: also test against interactions-py 6.0.0rc1 ... aae5bbdd38

Add one extra matrix entry (Python 3.12) that installs interactions-py 6.0.0rc1 over the locked version before running the tests. Locally, jarvis-bot's 214 tests and jarvis-tasks' 28 pass on it. The tests run with --no-sync so uv does not put the locked version back.

ci: build images on ubuntu-latest instead of the 16GB full image ... 01d8a16459

The slim act-latest runner image already ships the Docker CLI and buildx plugin, so the full image is not needed to build and push.

ci: raise the open-file limit of the Mongo service container ... 9d48f5087a

On a runner host whose containers default to a 1024 open-file limit, mongod aborts with WiredTiger 'Too many open files' partway through the suite and every later test fails with connection errors. Start the service with --ulimit nofile=64000:64000, the limit MongoDB recommends.

ci: run every test job against interactions-py 6.0.0rc1 ... 2590e4ad3d

Replace the single rc1 matrix entry with rc1 for all Python versions, so the tests no longer run against the locked 5.x release. Locally both suites pass on rc1.

ci: fix the image tag and publish dev builds as :dev ... 969ff382e7

The image job built an invalid reference when the registry secret was saved with a scheme, trailing slash or whitespace. Normalise the host, check it before building, and pass secrets through the environment instead of expanding them into the script. Tags are now: dev branch -> :dev, main -> :latest, git tags -> the tag, so people on :latest no longer get development builds. The old :stable tag is no longer published.

build(deps): require interactions-py 6.0.0rc1 ... 02003a505c

Make the 6.0 release candidate the real dependency instead of overriding it in CI: allow >=6.0.0rc1,<7 and relock. The 28 tests pass on it.

ci: drop the interactions-py override now that the lock uses 6.0.0rc1 ... 9b50b17ace

The test jobs install the locked dependencies as-is, so the matrix no longer needs an interactions version or a pip override step.

zevaryx added 3 commits 2026-11-03 06:32:58 +00:00

feat(reminders): add snooze buttons to delivered reminders ... 5327d0379e

Attach Snooze 10 minutes, 1 hour and 1 day buttons to a reminder delivered by DM or in its channel. jarvis-bot handles the press (custom id snooze|N). The notice sent when a private reminder cannot be delivered has no buttons, since there is nothing to snooze.

chore(release): 3.0.0 ... d8673f4da7

Move jarvis-tasks from 0.12.0 to 3.0.0 so it shares a version with jarvis-bot and jarvis-core, require jarvis-core >=3.0.0,<4 and pin the 3.0.0 commit, and say in the README that 3.x of each work together.

style: format the snooze button code ... 932bc6ddc2

Black formatting for the code added with the snooze buttons, so pre-commit passes in CI.

zevaryx added 1 commit 2026-11-03 14:40:33 +00:00

docs: describe the website, its cookies and sessions in the privacy policy and terms 6234d951d6

zevaryx added 3 commits 2026-11-03 17:01:51 +00:00

docs: bring the privacy policy up to date with the bot's, adding the audit trail and data export f42252585d

docs: describe raid and spam alerts in the privacy policy 9bc4aba81f

docs: describe ban appeals in the privacy policy 9b51adc37b

zevaryx added 2 commits 2026-11-03 17:48:09 +00:00

chore: normalise line endings to LF b21b53540e

docs: describe retention and appeal notices in the privacy policy 52593b5012

zevaryx merged commit 52593b5012 into main 2026-11-03 23:28:46 +00:00

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

jarvis/jarvis-tasks!1

No description provided.