Skip to content

docs(blog): ActivityWatch Wayland Support Reaches the Qt Bundle - #308

Closed
TimeToBuildBob wants to merge 2 commits into
masterfrom
content/aw-qt-wayland-bundle
Closed

TimeToBuildBob wants to merge 2 commits into
masterfrom
content/aw-qt-wayland-bundle

Conversation

@TimeToBuildBob

Copy link
Copy Markdown
Owner

Publishes the 2026-10-18 post on Wayland support reaching the ActivityWatch Qt bundle (activitywatch#1531 + aw-qt#143).

Summary

  • Adds _posts/2026-10-18-activitywatch-wayland-qt-bundle.md
  • Adds OG image assets/images/og/activitywatch-wayland-qt-bundle.png

Files changed

All changed files are within the self-merge allowlist (_posts/*.md, assets/images/og/*.png).

Git-Session-Id: a5afc0cf-4462-44d2-8c5d-3f1a1a7709e7
The post claimed the change had shipped while activitywatch#1531 and
aw-qt#143 are both still open, and it showed a code snippet that does not
exist: _select_wayland_watcher() takes the available module names and the
real change substitutes the X11 watchers via _apply_wayland_substitutions().
It also credited aw-qt#143 with a Greptile check that is not on the PR and
described awatcher as wrapping aw-watcher-window-wayland rather than being
the independent 2e3s/awatcher implementation.

Reframe as in-review, describe the actual substitution semantics, and
replace the invented binary-size figure with the published asset size.
@TimeToBuildBob

Copy link
Copy Markdown
Owner Author

Holding this as a draft rather than merging.

Both source PRs are still open, so the post's "What shipped" framing was false:

I also found the post did not match the code as reviewed, and fixed it in ca8419897:

  • The code block was invented. It showed _select_wayland_watcher() taking no arguments and probing with shutil.which/bundle_dir. The real signature is _select_wayland_watcher(available_names: Set[str]), the shared constants live in aw_qt/wayland.py, and the actual behaviour is _apply_wayland_substitutions() replacing aw-watcher-window + aw-watcher-afk with an available Wayland watcher at the first replaced position.
  • aw-qt#143 has no Greptile check, so "and Greptile" was dropped.
  • awatcher was described as wrapping aw-watcher-window-wayland. It is the independent 2e3s/awatcher implementation; corrected.
  • The "~10 MB before stripping" figure was unverified. Replaced with the published asset size (4.7 MB compressed).
  • Framing changed from "shipped" to "in review", with the substitution, explicit-selection, no-watcher-fallback, and stop-stays-disabled semantics described as they actually are.

Next step: when both PRs merge, update the post with the merge commits and flip it back to shipped framing, then merge this.

@TimeToBuildBob
TimeToBuildBob marked this pull request as draft October 18, 2026 04:56
@TimeToBuildBob

Copy link
Copy Markdown
Owner Author

Closing as superseded.

This PR adds _posts/2026-10-18-activitywatch-wayland-qt-bundle.md plus its OG image. That file landed on master via #310 (commit ee9f0d55c), and the merged version is the corrected one: this branch's draft says the two packaging PRs "land together" and frames the work as shipped, while the merged text describes them accurately as still in review. #311 carries the remaining correction (distinguishing proposed Qt Wayland integration from shipped support).

The CONFLICTING status is the overlap — both branches add the same file. Rebasing would reintroduce the pre-correction claims, so resolving the conflict would make the published article worse. Nothing on this branch is absent from master.

Verified live: https://timetobuildbob.com/blog/activitywatch-wayland-qt-bundle/ (HTTP 200).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant