Point project references at the laboratory #2

Merged
ClaudiuSchuster merged 7 commits from oss-oo/lab-links-rt20260926 into main 2026-09-26 20:21:25 +00:00
Owner

Laboratory migration step 2 (the link migration, chatgpt-usage PR #3 pattern).

  • All github.com self-references become oss-oo.io references: README checks badge (Forgejo badge endpoint) and release badge (shields.io gitea endpoint), clone URLs, sibling-project link, issue-tracker routes, systemd unit Documentation links, packaging source URL, About dialog (project URL, organization link, website label in English and German), documentation viewer online fallback.
  • Security reporting reworded honestly: the laboratory has no private advisory form, so contact the owner privately; SECURITY.md linked.
  • Social preview overlay text migrated and re-rendered (make check-social-preview green).
  • docs/PORTABILITY.md now describes the laboratory CI runner and the local rootless-Podman distribution gates that replace the retired GitHub compatibility workflow.
  • KEPT on purpose: upstream rclone/Proton-API-Bridge references, historical GitHub receipts (issue #42, PR #66, the v0.8.3 release attachment), personal author/collaborator links, the pinned rclone build's release download URL (the laboratory rclone repository publishes no releases), and the legacy pre-organization route guards.

Local evidence: make verify fully green; local Super-Linter run (pinned slim v8.7.0, the project's 13-lane set) fully green. This PR is also the first real runner verification for .forgejo/workflows/check.yml.

Laboratory migration step 2 (the link migration, chatgpt-usage PR #3 pattern). - All github.com self-references become oss-oo.io references: README checks badge (Forgejo badge endpoint) and release badge (shields.io gitea endpoint), clone URLs, sibling-project link, issue-tracker routes, systemd unit Documentation links, packaging source URL, About dialog (project URL, organization link, website label in English and German), documentation viewer online fallback. - Security reporting reworded honestly: the laboratory has no private advisory form, so contact the owner privately; SECURITY.md linked. - Social preview overlay text migrated and re-rendered (`make check-social-preview` green). - `docs/PORTABILITY.md` now describes the laboratory CI runner and the local rootless-Podman distribution gates that replace the retired GitHub compatibility workflow. - KEPT on purpose: upstream rclone/Proton-API-Bridge references, historical GitHub receipts (issue #42, PR #66, the v0.8.3 release attachment), personal author/collaborator links, the pinned rclone build's release download URL (the laboratory rclone repository publishes no releases), and the legacy pre-organization route guards. Local evidence: `make verify` fully green; local Super-Linter run (pinned slim v8.7.0, the project's 13-lane set) fully green. This PR is also the first real runner verification for `.forgejo/workflows/check.yml`.
Point project references at the laboratory
Some checks failed
Checks / Functional checks (pull_request) Failing after 57s
d96cefba08
All github.com self-references become oss-oo.io references: README
checks badge (Forgejo badge endpoint) and release badge (shields.io
gitea endpoint), clone URLs, sibling-project link, issue-tracker routes,
systemd unit Documentation links, packaging source URL, the Control
Center About dialog (project URL, organization link, website label in
English and German) and the native documentation viewer's online
fallback. Security reporting is reworded for the laboratory, which has
no private advisory form: contact the owner privately, SECURITY.md
linked. Social preview overlay text migrated and re-rendered.

Kept on purpose: upstream rclone and Proton-API-Bridge references,
historical GitHub receipts (issue #42, pull request #66, the v0.8.3
release attachment), personal author and collaborator links, the pinned
rclone build's release download URL (the laboratory rclone repository
publishes no releases), and the legacy pre-organization route guards.

docs/PORTABILITY.md now describes the laboratory CI runner and the
local rootless-Podman distribution gates that replace the retired
GitHub compatibility workflow.
Keep fontconfig cache noise out of the help-path HOME audit
Some checks failed
Checks / Functional checks (pull_request) Failing after 55s
932805e192
The containerized laboratory runner initializes GTK as root, where
pdrive-ui --help lets fontconfig create a user cache directory inside
the tested HOME. Pin XDG_CACHE_HOME to the scratch root so library
environment noise cannot appear as a helper side effect; the audit
itself stays as strict as before.
Complete the laboratory CI tool environment
Some checks failed
Checks / Functional checks (pull_request) Failing after 1m18s
3be0ac2aa7
The containerized runner has no user session and misses tools the
GitHub-hosted image preinstalled: pin XDG_RUNTIME_DIR for offline
systemd-analyze verification (tolerating the offline bus probe noise
next to the known system-bus variants) and install curl, iproute2, jq,
libglib2.0-bin and xdg-utils explicitly. The full suite passes inside
the exact CI container image.
Stop the demo dashboard timer during widget assertions
Some checks failed
Checks / Functional checks (pull_request) Failing after 1m15s
d37c890625
Demo mode re-applies demo state through a background dashboard timer
every refresh interval regardless of window visibility. Under
continuous CI load the timer can fire between a stress apply_state and
its queue-card assertion, overwriting the applied state and failing the
check. Remove the timer source right after window creation so the
widget suite asserts pure state transitions.
Report the actual queue card value when the stress assertion fails
Some checks failed
Checks / Functional checks (pull_request) Failing after 1m15s
6d191bc2ec
Report the actual recent row count when the direction assertion fails
Some checks failed
Checks / Functional checks (pull_request) Failing after 1m16s
3491f4c4e6
Quiesce every demo refresh source in the widget suite
All checks were successful
Checks / Functional checks (pull_request) Successful in 1m13s
8d98143562
The dashboard timer was only one refresh source: the constructor
refresh and each completed dialog also re-apply demo state through an
asynchronous refresh thread, which landed inside stress and direction
assertions under continuous runner load. Make request_refresh inert
after window creation and drain the initial refresh, so the suite
asserts pure state transitions without background interference.
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
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
OSS-Singularity/proton-drive-linux!2
No description provided.