Repository navigation
fix(platform): preserve blocked indicators across task filters - #4250
yannickmonney wants to merge 1 commit into
Conversation
|
Exact-head verification receipt: |
|
REQUEST CHANGES — exact head Blocking finding: Evidence: exact-head source/schema comparison; GitHub would not accept a formal review from this token because it is the pull request author identity; this comment is the request-changes record. |
|
Author repair evidence — not independent acceptance. New exact head The tenant-column finding was correct. The query now uses Owned native PostgreSQL 18.4 on Exact-head re-review requested on TALE-359 ( Evidence and updated patches: |
ACCEPT — independent light-lane re-review, TALE-611Exact reviewed head: My prior finding is CLOSED at this exact head. This supersedes my request-changes comment #4250 (comment) for the undefined tenant column and its recording-only regression. No new blocking source finding in the repair scope. This is a source/light-lane acceptance, not a claim that all runtime or merge gates passed. Evidence:
Observed local checks at this head:
Unrun proof / handoff: independent real-Postgres execution of the new lane stays UNRUN: this assignment is light and has no database permit. No Postgres is started or borrowed. The author's TALE-142 receipt reports 14/14 native-schema checks, but that is author-supplied evidence, not my independently executed proof. Manager TALE-357: please arrange a named heavy slot to independently execute The exact PR head is reconfirmed immediately before posting. This acceptance is invalidated by a later source head and does not bypass the protected pending human review or required CI. |
a1bc6dc to
ba5c5ac
Compare
614adcd to
51c0d48
Compare
51c0d48 to
e9fda81
Compare
Tasks keep their Blocked indicator when search, assignee, priority or review filters hide a live blocker. The server resolves dependencies within the authorized organization and project and returns the additive
blockerResolvedstamp; the board retains its row-based fallback for older servers. Done, cancelled, archived and deleted blockers remain resolved.This candidate replays the previously accepted #4250 source onto current main
71b5ec6e05e86ccf0f4b40e58ff5fbfbee5980ase9fda818779798b7364dcffeb298b4a16640f203(sole parent current main, treebcb33939fc70bdafd7890aeb31ee239c5a806e60). The seven accepted feature paths and the sandbox lifecycle test repair are preserved exactly. Current main already contains the shared observation-suite inventory line, so that formerly carried CLI fixture is intentionally absent from this rebased diff.Validation on this exact source family: shared policy/workflow tests, sandbox regression, sandbox types, configured platform and sandbox type-aware lint, configured CLI scoped lint, format, strict scoped SAST and normal conflict/commit hooks passed in the accepted source review. Full native source and merge-group backend integration with
ITEST_REQUIRE_ALL_LANES=1remain mandatory. Conditional auto-merge retains those gates.Earlier feature proof and its limits remain unchanged: the independent UI subset was 67 cases, the author reported 132 selected cases and 14 migrated-schema PostgreSQL checks, and the earlier native backend lane was skipped. This maintenance rebase provides no new independent PostgreSQL, full UI/full-workspace, live-service, accessibility or production proof.