Denise

Branch: refs/heads/main Home: https://github.com/dreamwidth/dreamwidth Commit: 472e7ca0671a6f37896549ef3e935b8cfdd52f03 https://github.com/dreamwidth/dreamwidth/commit/472e7ca0671a6f37896549ef3e935b8cfdd52f03 Author: Mark Smith mark@dreamwidth.org Date: 2026-02-16 (Mon, 16 Feb 2026)

Changed paths: M bin/worker/ses-incoming-email

Log Message:

Fix SES worker to expect S3 action notifications

The SNS notification now comes from the S3 action's topic_arn (terraform change), so receipt.action will always be type S3. Revert the non-S3 skip to a proper error since it would indicate a misconfiguration.

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com

Commit: 4895912982e33afbf41b439bc7d38d1a625b25b7 https://github.com/dreamwidth/dreamwidth/commit/4895912982e33afbf41b439bc7d38d1a625b25b7 Author: Mark Smith mark@dreamwidth.org Date: 2026-02-17 (Tue, 17 Feb 2026)

Changed paths: M bin/worker/dw-embeds M cgi-bin/DW/Task.pm M cgi-bin/DW/TaskQueue.pm M cgi-bin/DW/TaskQueue/SQS.pm M t/taskqueue-dedup.t

Log Message:

Add max_retries support to TaskQueue to avoid DLQ pileup

Failed SQS tasks that exceed the receive count threshold are now marked complete instead of being left for the dead letter queue. The SQS layer passes ApproximateReceiveCount through to tasks, and start_work checks it against a configurable max_retries option. Applied to dw-embeds where unreachable remote hosts cause repeated failures that fill the DLQ.

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com

Compare: https://github.com/dreamwidth/dreamwidth/compare/6792621c5547...4895912982e3

To unsubscribe from these emails, change your notification settings at https://github.com/dreamwidth/dreamwidth/settings/notifications

Branch: refs/heads/main Home: https://github.com/dreamwidth/dreamwidth Commit: def63d7f03f190bc1a99d4fd648fa0f1424b6960 https://github.com/dreamwidth/dreamwidth/commit/def63d7f03f190bc1a99d4fd648fa0f1424b6960 Author: Mark Smith mark@dreamwidth.org Date: 2026-02-16 (Mon, 16 Feb 2026)

Changed paths: A .github/workflows/tasks/worker-ses-incoming-email-service.json R .github/workflows/worker-build.yml R .github/workflows/worker-deploy.yml M .github/workflows/worker22-deploy.yml M config/update-workflows.py

Log Message:

Deprecate 18.04 workers

Also add deploy for new ses-incoming-email worker.

To unsubscribe from these emails, change your notification settings at https://github.com/dreamwidth/dreamwidth/settings/notifications

Branch: refs/heads/main Home: https://github.com/dreamwidth/dreamwidth Commit: 09b2fa09012b1edc5f23883029cf12a5a045bcc4 https://github.com/dreamwidth/dreamwidth/commit/09b2fa09012b1edc5f23883029cf12a5a045bcc4 Author: Mark Smith mark@dreamwidth.org Date: 2026-02-16 (Mon, 16 Feb 2026)

Changed paths: M config/workers.json

Log Message:

Add SQS queue names, so we can target autoscaling to queue depth

To unsubscribe from these emails, change your notification settings at https://github.com/dreamwidth/dreamwidth/settings/notifications

Branch: refs/heads/main Home: https://github.com/dreamwidth/dreamwidth Commit: 7f5a36ba49391219cb773eeb2ee5248be3b9ac09 https://github.com/dreamwidth/dreamwidth/commit/7f5a36ba49391219cb773eeb2ee5248be3b9ac09 Author: Mark Smith mark@dreamwidth.org Date: 2026-02-16 (Mon, 16 Feb 2026)

Changed paths: M cgi-bin/Plack/Middleware/DW/Auth.pm M t/plack-auth.t

Log Message:

Fix domain session cookie bounce not firing under Plack

When a user's domain session cookie is stale (e.g. after re-login gives them a new session ID), the Plack Auth middleware detected the mismatch and set the bounce URL but never actually redirected. The page would render as logged-out instead of bouncing through /misc/get_domain_session to refresh the cookie.

Add the redirect check to the Auth middleware's else branch so all Plack-served pages (journal views, controllers, etc.) get the bounce. Also fix pre-existing test failures in plack-auth.t where MockUser was missing the userid method needed by the RateLimit middleware.

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com

To unsubscribe from these emails, change your notification settings at https://github.com/dreamwidth/dreamwidth/settings/notifications

Branch: refs/heads/main Home: https://github.com/dreamwidth/dreamwidth Commit: 3fd45fe55656253ccaed8ddc4c334fbbe58dea9c https://github.com/dreamwidth/dreamwidth/commit/3fd45fe55656253ccaed8ddc4c334fbbe58dea9c Author: Mark Smith mark@dreamwidth.org Date: 2026-02-16 (Mon, 16 Feb 2026)

Changed paths: M .gitignore R terraform/cluster.tf R terraform/iam.tf R terraform/import.sh R terraform/load-balancing.tf R terraform/locals.tf R terraform/providers.tf R terraform/proxy.tf R terraform/security-groups.tf R terraform/web.tf R terraform/workers.tf

Log Message:

Remove terraform from repo

Moving to a private repo. This has limited utility for public viewing, and I want to import our more sensitive configurations.

To unsubscribe from these emails, change your notification settings at https://github.com/dreamwidth/dreamwidth/settings/notifications

Branch: refs/heads/main Home: https://github.com/dreamwidth/dreamwidth Commit: 081042e7a5b88b3eae282f82dcb6bf1bfcd4fc3c https://github.com/dreamwidth/dreamwidth/commit/081042e7a5b88b3eae282f82dcb6bf1bfcd4fc3c Author: Mark Smith mark@dreamwidth.org Date: 2026-02-15 (Sun, 15 Feb 2026)

Changed paths: M app.psgi M t/plack-subdomain.t

Log Message:

Fix journal subdomain root URI showing homepage instead of journal

DW::Routing->call() in app.psgi was called without a username, so it always used the 'app' role. The homepage route (registered as app-only via /index) matched '/' on journal subdomains, returning a defined value that prevented the journal rendering block from running.

Pass the journal username (from dw.journal_user, set by SubdomainFunction middleware) to routing so it uses the 'user' role, where app-only routes like the homepage don't match.

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com

To unsubscribe from these emails, change your notification settings at https://github.com/dreamwidth/dreamwidth/settings/notifications

Branch: refs/heads/main Home: https://github.com/dreamwidth/dreamwidth Commit: 55d1983593d30fd637a0f5303249894099cc5790 https://github.com/dreamwidth/dreamwidth/commit/55d1983593d30fd637a0f5303249894099cc5790 Author: Mark Smith mark@dreamwidth.org Date: 2026-02-15 (Sun, 15 Feb 2026)

Changed paths: R bin/maint/synsuck.pl M bin/maint/taskinfo.txt M bin/upgrading/update-db-general.pl M cgi-bin/DW/Controller/Misc.pm M cgi-bin/DW/Task/SynSuck.pm M cgi-bin/LJ/Console/Command/SynEdit.pm M cgi-bin/LJ/Feed.pm M cgi-bin/LJ/SynSuck.pm

Log Message:

Add exponential backoff for dead syndicated feeds

Dead feeds (HTTP errors, DNS failures, parse errors) were polled every 1-3 hours forever with no escalation. Add a failcount column to the syndicated table and apply exponential backoff: base_delay * 2^min(failcount, 7), capped at 30 days. Dead feeds settle into ~monthly polling instead of ~2,920 wasted requests per year.

Three backoff modes: escalate (feed/account errors), reset (success or not-modified), hold (our infrastructure issues like nodb/posterror). Reset failcount on URL change (syn_edit), feed merge, and REST ping.

Also converts SynSuck verbose print statements to Log::Log4perl, removes the now-drained legacy synsuck.pl maint worker, and fixes an out-of-scope $user reference in parse_items_from_feed().

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com

To unsubscribe from these emails, change your notification settings at https://github.com/dreamwidth/dreamwidth/settings/notifications

Branch: refs/heads/main Home: https://github.com/dreamwidth/dreamwidth Commit: 1b24c1ccf3b8b16e581c478bde4c70c0af428f01 https://github.com/dreamwidth/dreamwidth/commit/1b24c1ccf3b8b16e581c478bde4c70c0af428f01 Author: Mark Smith mark@dreamwidth.org Date: 2026-02-15 (Sun, 15 Feb 2026)

Changed paths: M cgi-bin/DW/Task/SynSuck.pm

Log Message:

Handle unhandled exceptions in SynSuck worker via delay()

When LJ::SynSuck::update_feed() dies with an unhandled exception (e.g. "Hour '24' out of range"), the normal delay() call is never reached, so checknext is never updated. The scheduler immediately re-enqueues the same feed, creating a tight infinite retry loop.

Now the worker catches the exception, calls delay() to push checknext 6 hours into the future with laststatus='exception', and returns COMPLETED. This matches how every other error path in SynSuck already works and is better than the old TheSchwartz behavior (which retried 3 times over 90 minutes then silently gave up without updating checknext or laststatus).

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com

To unsubscribe from these emails, change your notification settings at https://github.com/dreamwidth/dreamwidth/settings/notifications

Branch: refs/heads/main Home: https://github.com/dreamwidth/dreamwidth Commit: ac3bc65f616384cc864ba3fc33836ea2dac5cc1b https://github.com/dreamwidth/dreamwidth/commit/ac3bc65f616384cc864ba3fc33836ea2dac5cc1b Author: Mark Smith mark@dreamwidth.org Date: 2026-02-15 (Sun, 15 Feb 2026)

Changed paths: M .github/workflows/base-build.yml M .github/workflows/base22-build.yml M .github/workflows/devcontainer-build.yml M .github/workflows/proxy-build.yml M .github/workflows/web-build.yml M .github/workflows/web22-build.yml M .github/workflows/worker-build.yml M .github/workflows/worker22-build.yml

Log Message:

Disable Docker BuildKit provenance attestations in all build workflows

Docker 25+ enables provenance attestations by default, which creates 3 manifests per build in GHCR (image index + platform manifest + attestation). This clutters the package registry and makes dwtool's image selection UI show 3x entries per build. Since we build and deploy internally, provenance adds no value here.

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com

To unsubscribe from these emails, change your notification settings at https://github.com/dreamwidth/dreamwidth/settings/notifications

Branch: refs/heads/main Home: https://github.com/dreamwidth/dreamwidth Commit: 1ea3fb90458e9829e0c4425f8b8fd5755bea0571 https://github.com/dreamwidth/dreamwidth/commit/1ea3fb90458e9829e0c4425f8b8fd5755bea0571 Author: Mark Smith mark@dreamwidth.org Date: 2026-02-15 (Sun, 15 Feb 2026)

Changed paths: M src/dwtool/go.mod M src/dwtool/go.sum M src/dwtool/internal/aws/ecs.go A src/dwtool/internal/aws/sqs.go M src/dwtool/internal/config/config.go M src/dwtool/internal/config/workers.go M src/dwtool/internal/github/github.go M src/dwtool/internal/model/types.go M src/dwtool/internal/ui/app.go M src/dwtool/internal/ui/deploy.go M src/dwtool/internal/ui/help.go M src/dwtool/internal/ui/logs.go A src/dwtool/internal/ui/sqs.go M src/dwtool/main.go

Log Message:

Add SQS dashboard page to dwtool

Second top-level page (right arrow from ECS dashboard) showing SQS queue health: pending messages, in-flight, delayed, and throughput via CloudWatch NumberOfMessagesReceived metrics. Queues are discovered by configurable prefix (--sqs-prefix) and grouped into task queues vs dead letter queues.

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com

To unsubscribe from these emails, change your notification settings at https://github.com/dreamwidth/dreamwidth/settings/notifications