Skip to content

docs: repair API navigation and capture PostgreSQL CI waits - #417

Draft
ywatanabe1989 wants to merge 9 commits into
developfrom
fix/reconcile-accepted-docs-and-cohort-1120
Draft

ywatanabe1989 wants to merge 9 commits into
developfrom
fix/reconcile-accepted-docs-and-cohort-1120

Conversation

@ywatanabe1989

@ywatanabe1989 ywatanabe1989 commented Nov 20, 2026 •

Copy link
Copy Markdown
Member

Repair the umbrella's broken API-document links and capture the missing PostgreSQL wait evidence behind native CI failures.

The documentation change points 67 stale references at existing authored API pages, routes retired notify to notification, and directs utils readers to path/string/I/O owners. It preserves the accepted main README and five skills through the original reconciliation with current develop. Runtime code and dependency metadata remain unchanged.

The failed native saves reach Clew's observer and wait inside Dev Store schema construction; the connection closes as the 60-second failure unwinds, leaving no blocker evidence. Add an opt-in parent-process observer for the disposable CI database. It uses read-only activity/lock queries to record wait types, blocker PIDs, relation locks and fixed command classifications. It never records SQL text, parameters or credentials. Nested pytest processes and xdist workers do not start extra observers. Requested diagnostics that fail do not produce a false pass. CI enables the observer through its existing preparation step; no worker, test, deadline, store semantics, admission, durability or audit setting is relaxed.

Scoped validation:

  • Fresh normal documentation environment: 263 packages pass dependency checks; real HTML rendering verifies 72 authored references against actual links and physical destinations. Broader warnings remain unaccepted.
  • Two real PostgreSQL observer/privacy controls pass, including a held relation lock, SQL-literal canary redaction and an actual refused connection. All 20 existing fleet-isolation/child-process controls also pass with the observer enabled. Test tables are removed and the database table inventory remains unchanged.
  • Independent cold Clew constructors and actual I/O save/load controls pass using the same PostgreSQL 16 image digest and I/O 0.7.0, Clew 0.36.0, Dev 0.65.0 and FigRecipe 0.45.1 as CI. A deliberately held lock is captured and the missing index is recreated after release. These focused cases do not reproduce or diagnose the original suite's blocker.
  • Project audit: zero errors, 151 warnings and one info.

Keep this draft held for new original CI and unresolved native/source/release acceptance. The 3b14 head's original Python 3.11 and 3.12 jobs each retain two 60-second failures and 757 passes, with 93 skips, 42 xfails and 19 xpasses. All original workflows completed before this substantive diagnostic source advance. No failed fixture was force-replayed or job force-rerun/cancelled. A later pass alone does not explain those failures. No publication or development-service rollout occurred; superseded private same-version wheels remain NEVER_UPLOAD.

ywatanabe1989 and others added 8 commits June 20, 2026 23:52
promote(develop->main): umbrella 2.30.2 release-prep — drop 120MB blob + reconcile leaf pins
The operative legal terms (sections 0-17) already govern under AGPL-3.0;
this only removes the FSF template's generic "or any later version"
placeholder from the non-operative How-to-Apply section, matching
pyproject.toml's license = "AGPL-3.0-only" declaration.
chore(release): promote develop → main
release: promote SciTeX 2.30.9 to main
…h-1105

docs: refresh public README and umbrella skill guides
@ywatanabe1989 ywatanabe1989 changed the title docs: reconcile accepted main guides with current develop docs: fix API reference navigation and reconcile accepted guides Nov 20, 2026
@ywatanabe1989 ywatanabe1989 changed the title docs: fix API reference navigation and reconcile accepted guides docs: repair API navigation and capture PostgreSQL CI waits Nov 20, 2026

This branch has not been deployed

No deployments
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