fix(fulltext): bump model version to 0.7.423 to match deployed workspaces#10848
Closed
MichaelUray wants to merge 284 commits into
Closed
fix(fulltext): bump model version to 0.7.423 to match deployed workspaces#10848MichaelUray wants to merge 284 commits into
MichaelUray wants to merge 284 commits into
Conversation
Implements 8 of the 9 action items from the Stitch (Gemini 3.1 Pro)
redesign review. Item 8 (Geist font swap) skipped — would override
Huly's global Inter and is out of PR2 scope.
1. Today-marker date pill: small red rounded label at the top of the
today line showing "10. May" so the marker speaks for itself.
2. Active-status bars get a stronger fill (#f59e0b amber + white
text), Won bars green with white text, ToDo bars sky-blue with
navy text — bars now read at a glance.
3. Sidebar gains a date-range subheader strip ("Feb 2026 – Mar 2027"
with « » page-nav and click-to-jump-to-today behaviour). Header
row height grows from 40 to 56px to fit the stacked layout.
4. Hover spotlight: when any row is hovered, non-hovered rows fade
to 0.55 opacity (Stitch-style focus).
5. Milestone reference lines shrink from full-canvas dashed lines
to a tick + filled triangle in the top 14px of the canvas —
less visual noise behind the bars.
6. Toolbar Unicode glyphs (⏮ « » ⏭) replaced with Huly's own
ArrowLeft/NavPrev/NavNext/ArrowRight icons; date input wrapped
in a label with a Calendar icon.
9. Scrollbars slimmed from 14px to 10px tracks with semi-transparent
thumbs (opacity 0.45 → 0.85 on hover, 1 on drag).
Item 7 (theme-aware bar colors) was already wired via statusCategory
Map in v25 — this commit just verifies the path.
Plane-style: dashed-top-border "+ Add issue" row at the bottom of
GanttSidebar opens the standard CreateIssue popup via showPopup.
- GanttSidebar dispatches `addIssue` from a keyboard- and click-
accessible row using the existing tracker.string.AddIssue label.
- GanttView wires it to showPopup(CreateIssue, { space, shouldSaveDraft }).
- Row is hidden when no space is available (defensive guard in
newIssue handler).
Verified on dk3 huly_v7 (gantt-v28): row renders, click opens
"New issue" dialog with Issue title field focused.
Adds Issue.startDate and Issue.dueDate to the ClassFilters mixin for tracker.class.Issue. Both attributes are TypeDate, which view-model already wires to view-resources DateFilter (with built-in range support), so this is the minimal change to expose date-range filtering in the Tracker filter dropdown — works in List, Kanban, and Gantt. NB: deploy of this model change is batched with the PR3 multi-pod deploy (transactor + workspace + tool image + workspace upgrade); front:gantt-v28 alone is not enough since the ClassFilters mixin TX lives in the workspace model store.
GanttView computes hHasOverflow but never gated the bar on it — the
sticky-bottom scrollbar was rendered unconditionally, including in
empty workspaces where it was just visual noise. In addition, when
totalCanvasWidth was barely larger than the track, hThumbWidth could
exceed hTrackWidth and the thumb would visually overflow its container.
Fixes:
- Wrap the .gantt-hscrollbar element in `{#if hHasOverflow}` so it
disappears in the no-overflow case.
- Clamp the rendered thumb width to `Math.min(hThumbWidth, hTrackWidth)`
to defuse the degenerate over-track case.
in Playwright: empty workspace no longer renders the scrollbar.
…comments
Strips reviewer-attribution markers ('review-N <date>') from source-code
comments. Comments are kept and rephrased as 'review note' so the noted
constraint or hidden invariant survives, only the internal attribution
is dropped.
The drag-controller reducer only accepted mousedown-bar from hover-bar state, but no DOM event ever transitioned idle → hover-bar (we never wired the mouseenter-bar event from GanttBar to the reducer). The hover state was dead code, and the first mousedown on a freshly-rendered bar was silently dropped — Playwright integration test surfaced this. Fix: reduceFromIdle accepts mousedown-bar directly with the same edge-discriminator logic as reduceFromHover. Real users always go through hover-bar first (mouseenter fires before mousedown), but synthetic event dispatch and re-render edge cases can skip it. Adds 2 tests: - mousedown-bar from idle → dragging-body - mousedown-bar (edge=left) from idle → resizing-left
…sion 1. Context menu is too tall (~19 entries from auto-resolved Huly actions). Restructured via includedActions allow-list to 9 curated entries that make sense for a Gantt bar: - Open (Edit issue) - Status / Priority / Assignee (existing actionPopup submenus, ›) - Set start date / Set due date - Copy issue ID / URL - Duplicate / Delete Component, Milestone, Labels, SubIssue, SetParent, Relations, Move-to-project and time-report stay accessible from the standard List/Kanban menu but are hidden from Gantt's right-click. 2. Unscheduled-drag-grip in the sidebar shared pointerdown with the canvas pan handler. Pan would start before the grip's mousedown|stopPropagation fired, swallowing the drag. Extended onCanvasPanStart exclusion: now also bails on .sidebar-cell, .drag-grip, .resize-handle. The grip's pointerdown no longer triggers a stray pan.
…Sub-Issue User UX feedback 2026-05-11: the allow-list approach hid Open (Edit issue) because tracker registers a custom Open action for tracker.class.Issue with an auto-generated ID, and it also hid Set parent issue / Add sub-issue which the user explicitly needs to manage issue hierarchy from the Gantt. Switch from includedActions to excludedActions. Hide only the genuinely noisy entries for a Gantt right-click: Component, Milestone, Labels, CopyIssueTitle, Relations, NewRelatedIssue, EditRelatedTargets, MoveToProject, CopyAsMarkdownTable, UnsetParent. Result: Open / Status / Priority / Assignee / Set start date / Set due date / Add sub-issue / Set parent issue / Copy ID / Copy URL / Duplicate / Delete remain — 12 entries instead of 18, with the expandable submenus (Status, Priority, Assignee ›) keeping the visible menu compact.
…pra labels
User requirements 2026-05-11:
1. Restructure Gantt right-click menu: "Sub-issue & Parent" as a single
collapsed Hierarchy ▸ submenu containing
- Set parent issue…
- Add sub-issue
- Link existing as sub-issue… (NEW)
The old flat SetParent + NewSubIssue entries are hidden from the
parent menu (excludedActions) so the Gantt context menu stays compact.
2. EditIssue panel: add a "Set parent issue…" button visible when the
issue has no parent — previously this was only reachable via right-
click context menu, not from the open issue itself.
3. SubIssues panel: add a "Link existing as sub-issue" button next to
the existing "Add sub-issue" button so the user can attach an
already-existing issue without first opening it.
4. GanttHeader two-row labels (user feedback: "year/month above"):
- day view: month name above day number
- week view: year above Wnn
- month view: year above month name (was entirely missing)
- quarter view: year split out above Q1/Q2/… (was side-by-side
"Q1 2026" — visually noisy at dense zoom)
Supra-label renders only at segment boundaries (1st of month, first
week of year, January, Q1) so it doesn't repeat in every column.
3 new jest tests cover day/week/quarter supra cases.
- Hierarchy UiAction missing required `action` field — added no-op
(Menu.svelte routes the click via `component:` when present).
- dragging-unscheduled no longer shifts existing descendants — the
synthetic "today" origin would have shifted them by a wildly
unrelated delta. Unscheduled-drag now only commits the parent.
- LinkSubIssueActionPopup: full ancestor + transitive descendant
ignore set so the picker can't create cycles (BFS over the
parents[0].parentId edge, matching scheduler.descendantsWithDates).
- releasePointerCapture now guarded by hasPointerCapture(pointerId)
to avoid InvalidStateError when a pointerup bubbles from an
excluded child (resize-handle, drag-grip).
- openSetStartDate (context menu) now surfaces commit failures via
NotificationSeverity.Error, matching commitDrag's error handling.
- i18n: drag-grip tooltip and duration tooltip pulled out of hardcoded
English into tracker.string.GanttDragToSchedule + GanttDurationTooltip.
New files:
- plugins/tracker-resources/src/components/LinkSubIssueActionPopup.svelte
- plugins/tracker-resources/src/components/gantt/GanttHierarchySubmenu.svelte
i18n: 5 new keys (Hierarchy, LinkExistingSubIssue, SetParentIssueLabel,
GanttDragToSchedule, GanttDurationTooltip).
…mmary-bar interactivity
User UX requirements 2026-05-11:
1. Click-to-select gate: a bar must be clicked once to become "selected"
(solid blue outline, .bar.selected) before the next mousedown
actually starts a drag/resize. Prevents accidentally dragging an
issue while panning the canvas horizontally — earlier feedback was
that fast horizontal pans would catch a bar by mistake. Plane-style
UX. Clicking the canvas background clears the selection.
2. Confirmation popup before commit: GanttConfirmCommitPopup shows a
"Move X to Y – Z?" / "Change X to Y – Z?" dialog with Cancel/Apply
buttons. Two independent ViewOption toggles (Customize-View → Display)
gate whether the popup appears:
- ganttConfirmMove (default-on) — drag-body
- ganttConfirmResize (default-on) — resize-left/right
Saves to the same per-viewlet option store as ganttShowStatus, so
each user gets their own preference. Skip the popup entirely when
the preview is unchanged (zero-delta drag).
sub-issues it renders as the MS-Project claw rather than a regular
rect. Previously the claw had no mousedown/contextmenu, so commitDrag's
parent-pulls-children path was unreachable from the UI. A transparent
`summary-hit` rect now spans the claw and wires the standard
onBarDown / onBarContextMenu handlers, plus the two resize-handles.
Milestone summaries (issueObj === undefined) stay read-only.
- Split GanttConfirm{Move,Resize} setting label from dialog title.
New keys: GanttConfirmMoveTitle = "Move issue?", GanttConfirmResizeTitle
= "Change issue dates?". Setting labels remain "Confirm before moving an
issue" etc.
- Drop unused GanttClickToSelect string.
- New jest suite `link-sub-issue-cycle.test.ts` (6 tests) fences the
ancestor/descendant/self/cycle ignore logic so future refactors can't
silently regress cycle protection.
Deploy:
- models/tracker + models/all rebuilt to ship the new ViewOption keys.
- front/transactor/workspace/tool images at gantt-v35.
- Workspace upgrade applied to all 3 dk3 workspaces — toggles appear in
Customize-View → Display.
…et + a11y roles
per explicit user preference for both select-first + confirm-popup
default-on):
1. Parent-drag now shifts the FULL descendant tree, not just children
that happen to be in the view's filtered `issues` array. Previously
a Tracker filter that hid some sub-issues caused them to stay at
the old date while their parent moved — silent tree drift. commitDrag
and shiftFocused both now run `client.findAll(tracker.class.Issue,
{ space: issue.space })` to query the full space before walking
descendantsWithDates. One extra query per commit, no impact on drag-
interactive frame rate.
2. computeCanvasX (unscheduled drag) now offsets by sidebarWidthPx +
5 px instead of just sidebarWidthPx. The 5 px is the resize-cell
column between sidebar and canvas (.resize-cell). The hscrollbar
has always used this offset (style="padding-left: {sidebarWidthPx +
5}px"); unscheduled-drag was the only consumer that missed it,
causing drops to land a few pixels off at high zoom.
3. A11y: the 6 interactive <rect>s on GanttBar (regular + summary +
resize handles, both branches) now carry role="button",
tabindex="-1", and aria-label so screen readers announce them as
actionable. The a11y-click-events-have-key-events warning is
suppressed per-rect with svelte-ignore plus a banner comment
explaining that keyboard support lives at the GanttView level
(Tab/ArrowLeft/Right). 94 → 88 warnings.
Tests: 5 suites / 60 passed.
…bels
friction observation about select-first + confirm-popup left as-is
per explicit user preference, the parent-drag performance note is a
future-large-space concern):
1. .settings-btn / .settings-popover removed from GanttView.svelte.
They were leftover from an earlier custom-popover prototype that
was replaced by Huly's standard ToggleViewOption pattern in PR2;
the CSS was orphaned. Drops 4 svelte-check warnings.
2. Resize handle ARIA labels were hardcoded English ("Resize start" /
"Resize end"). Now translated via tracker.string.GanttAriaResizeStart
and GanttAriaResizeEnd. Translation resolves async on themeStore
language change; falls back to the English default until resolved.
84 warnings (was 88).
…comments
Strips reviewer-attribution markers ('review-N <date>') from source-code
comments. Comments are kept and rephrased as 'review note' so the noted
constraint or hidden invariant survives, only the internal attribution
is dropped.
…marked invariant - cursor: pointer when editable+unselected, grab when selected, grabbing during active drag (same state machine for summary claw) - .bar.selected: 3px stroke + stronger glow, paint-order stroke fill so the armed state is unmistakable on every status fill color - .bar.focused: 1px dashed (was 2px solid) — visually distinct from .selected so the two states never look identical - handleBarMouseDown syncs focusedIssueId to selectedIssueId on first-click and onBackgroundClick clears both; eliminates the 'multiple bars marked' visual where Tab-focus + click-select highlighted two bars simultaneously - resize handles only render when the bar is selected (avoids accidental edge-grabs on unarmed bars; minimal surface for the ew-resize cursor) User feedback 2026-05-11 from dk3 deployment: single click did not visibly mark the bar and multiple bars appeared selected at once.
…rtualization Pure-logic Y-axis virtualization surface (computeYViewport, rowIndexToY, yToRowIndex, sliceVisibleRows) — mirrors the runtime virtualizer's decisions so the sidebar + canvas + dependency layer can be tested deterministically without a browser. Supersedes Phase 3a's computeVisibleRowRange() helper as the single source of truth for visible-range + spacer math.
… y-viewport Pure-logic classifyArrowVisibility() + clippedEndpointPx() helpers tell the dependency layer which arrows to render in full, which to clip at the viewport edge with an off-screen indicator, and which to cull. Both endpoints on the same off-edge side → none. Endpoints straddling opposite edges → both-off (arrow path still crosses the viewport). Single-pixel overlap with bounds counts as visible.
Synthetic sweep over 100 / 50 scroll positions on a generated 1000 / 5000 row dataset. Budgets are loose (500 ms / 1500 ms) so the test doesn't flake under rush parallel test execution; actual runtime is single-digit ms on modern CPUs. The gate exists to flag catastrophic regressions (10× slowdown) in the pure-logic virtualization path.
…te, sidebar-virtualization)
…line comments Strips internal-tracking phrases from source-code comments (Tier-N Item M, Tier-N #M, v121.NN, per Tier-N spec, Gemini/Stitch/Codex stragglers). Comments themselves are preserved — only the attribution labels are dropped.
…ed by localStorage
Adds an opt-in 'Predecessors' column to the Tracker issue list, so
power users can see dependency relationships without switching to the
Gantt view. Spec
docs/superpowers/specs/2026-05-14-huly-gantt-predecessor-column-design.md.
Rendering (spec-mandated):
- Identifier + Kind + Lag notation, e.g. 'PROJ-3 FS+2d'.
- Zero lag drops the +0d suffix ('PROJ-3 FS').
- Multiple predecessors collapse to 'first +N more' with a hover
tooltip listing every upstream issue.
- Click on the identifier navigates to the predecessor issue via
DocNavLink -> EditIssue (standard Tracker navigation).
- Empty cell when the issue has no incoming relations.
Files:
- plugins/tracker-resources/src/components/issues/
PredecessorsColumnPresenter.svelte -- live-query relation + sources
PredecessorsTooltip.svelte -- +N more hover body
- plugins/tracker-resources/src/plugin.ts -- PredecessorsColumn component id
- plugins/tracker-resources/src/index.ts -- register component
- models/tracker/src/viewlets.ts -- column entry (optional, hidden by default)
i18n strings 'Predecessors'/'Vorgaenger' already exist in en+de from
the Gantt sidebar column work, no new strings needed.
Tests: 518 -> 531 (13 helper tests added in previous commit).
svelte-check: 0 errors on new components.
…uping by recipient
…yChangeKind for Visual DependencyEditor Adds tooltip strings (one per kind) plus the picker aria-label and the 'Change type' link label in EN + DE. Keys match existing convention.
…m picker Replaces the dropdown in DependencyEditor with a 2x2 grid of clickable SVG mini-diagrams (FS / SS / FF / SF). After a pick the grid collapses to a compact single-diagram view plus an inline -14..+14d lag slider and a 'Change type' link that re-expands the grid. The existing NumberInput stays as fallback for values outside the slider range (-30..+90 storage clamp unchanged). Per spec 2026-05-14-huly-gantt-visual-dependency-editor-design.md: - 2x2 layout (FS/SS top, FF/SF bottom) - lag slider embedded in the picked diagram view - collapse-after-pick UX with re-expand button - role=radio + arrow-key keyboard navigation between diagrams - aria-label + title tooltips with full kind-hint i18n strings
…d notification type
Adds pure-TS helpers for the upcoming 2x2-grid mini-diagram picker: - DIAGRAM_KINDS in spec-mandated grid order (FS/SS/FF/SF) - diagramGridIndex() for keyboard navigation (Arrow keys) - clampLagSlider() for the inline -14..+14d slider - getDiagramSvgPaths() returns rects + arrow polyline per kind, with FS/FF distinguishable by arrow endpoint (left vs right of S) 18 new tests, 549 total.
…fset
Two small follow-ups discovered during the final pass:
- GanttBar .bar gets touch-action: none so iOS Safari does not
hijack pointerdown on a bar with native pan-zoom (Spec §"iOS-
Safari Edge-Cases"). Without this the long-press timer never
fires because Safari steals the gesture before pointerup.
- The drawer's top offset was hardcoded to 32 px via a non-existent
--gantt-header-height variable. HEADER_HEIGHT is 56 in
GanttView.svelte; the drawer now matches, with a comment to keep
it in sync. height: calc(100% - 56px) so the drawer doesn't
overflow under the bottom of the canvas-cell either.
Tests: 631 / 631. svelte-check: 0 errors.
Phone-mode (≤640 px) gets:
- Hamburger button in the toolbar that toggles a slide-out drawer
overlay carrying the issue list (Spec §"Phone": Sidebar Phone =
Slide-out-Drawer auf Tap).
- Sidebar-cell goes absolute + translateX(-100%) by default; the
.drawer-open class slides it to 0. Tap-anywhere-on-canvas
backdrop dismisses it; the onJump handler also closes it once
the user has scrolled to the picked row (Spec §"Phone": Tap
schließt Drawer).
- Resize-corner / resize-cell are hidden — finger-width column
resize is fiddly and the drawer covers the viewport anyway.
Tablet-mode (641–1024 px) gets:
- .nav-btn / .gantt-toolbar-icon-btn / .zoom-btn min-44x44 px hit
targets so touch-tap is reliable (Spec §"Tablet": Hit-Targets
min 44x44 px).
Confirm popups become responsive (Spec §"Risks": 600 px popups
overflow 320 px screens): max-width: min(480px, 95vw) + box-sizing
border-box. On Phone the popup is read-only so this is belt-and-
braces, but the cap also helps narrow-window desktop users.
i18n strings (EN + DE) added for hamburger aria-label and the
read-only hint. Tests: 631 / 631. svelte-check: 0 errors.
Close the coverage gap surfaced by the 2026-05-15 regression audit: - cascade-token.ts: 9 tests covering default + custom prefix, the <date>-<counter> suffix shape, monotonic counter increment and 1000-call uniqueness. - dependency-shift-send.ts: 5 tests around early-return paths (empty primaries+shifts, empty bundle, missing PersonSpace) and the onError / silent-swallow contract. The Tx-create bundle remains untested by design (pure IO glue with no behaviour to assert). - menu-actions.ts: 14 tests covering the ganttExtraActions array shape (group, icon, component, props) plus the openSetStartDate popup wiring and the four callback branches (dismiss, clear, auto-fill-due, no-auto-fill). exporter.ts stays untested: every export is bound to the DOM / canvas / html2canvas / jsPDF and cannot run under the node Jest env without either refactoring or pulling in jsdom. Audit report appended with the rationale. 645 -> 673 tests.
…line comments Strips internal-tracking phrases from source-code comments (Tier-N Item M, Tier-N #M, v121.NN, per Tier-N spec, Gemini/Stitch/Codex stragglers). Comments themselves are preserved — only the attribution labels are dropped.
Lift the gantt-toolbar controls (Group-by, Date-Nav, Zoom preset + days input, Undo/Redo, Hamburger, Fullscreen) out of GanttView and into the SpaceHeader's row 2 so the user sees a single unified toolbar instead of three stacked strips. Render order matches the spec: Filter -> Group-by -> Lupe -> Date-Nav -> Week -> days -> Undo/Redo -> All/Active/Backlog -> Hamburger -> Fullscreen (Hamburger now before Fullscreen, swapped from legacy). State bridges across the parent/child boundary via a writable Svelte store (ganttToolbarSnapshot): GanttView keeps owning the values and handlers, writes a snapshot on every reactive update, and clears it on destroy. A standalone GanttToolbarBar component subscribes to the store and renders the controls in two clusters, one per slot. SpaceHeader gains: - overrideSearch prop + search slot to let consumers replace the built-in SearchInput + FilterButton when needed - extra-trailing slot rendered after the ModeSelector Non-gantt viewlets (List, Kanban) keep the SpaceHeader default exactly as before.
The SpaceHeader's row-2 search cluster uses flex-direction: row-reverse, so markup order is reversed from visual L→R. Split GanttToolbarBar's search section into search-mid (Group-by only) and search-end (the rest) and reverse the internal markup order so the user sees: Filter → Group-by → Lupe → Date-Nav → Week → days → Undo/Redo The extra cluster keeps row direction so the trailing section's Hamburger-before-Fullscreen markup matches the visual order.
…s in extended sidebar - Move the Fullscreen toggle out of the gantt-toolbar trailing slot into the global status bar (packages/ui Root.svelte, next to the gear icon) so it's reachable from every viewlet, not only Gantt. The button switches Maximize/Minimize icon based on document.fullscreenState. - Swap the search-row ordering so the Lupe (SearchInput) sits leftmost and Filter sits next to it: visual L→R is now Lupe → Filter → Group-by → Date-Nav → Week → days → Undo/Redo. - Restore milestone labels (and start/due dates) in the extended-columns sidebar. The Phase-3a renderer fell through to an empty placeholder for any non-issue row; the user reported milestone text vanished as soon as Extended Sidebar Columns was enabled. Now the title column shows the milestone label (italic, matching the legacy compact sidebar), and the startDate/dueDate/deadline columns show the milestone's startDate/targetDate.
3 tasks
|
Connected to Huly®: UBERF-16438 |
…aces The fulltext-pod's compiled model version (baked into bundle/model.json via common/scripts/version.txt at build time) was 0.7.422 while the deployed workspace pods had been migrated to 0.7.423. The fulltext-pod rejected every incoming Tx with a 'wrong version' warning, so newer issues — including the user-reported OSKOS-51 'Telescopic loader' — were never indexed and search returned empty results. Bumping version.txt aligns the compiled model with the workspaces. All future builds (front, transactor, workspace, tool, fulltext) will emit 0.7.423. Adds plugins/view-resources/src/__tests__/README-search-rootcause.md as the regression marker — pure-TS tests cannot exercise the ES round-trip, so the README points future PRs to the live verification in the Task 6 Playwright case. Co-finding during the investigation: huly_v7-redpanda-1 had exited the same morning, causing fulltext-pod to lose its queue consumer for ~3h. Restarting redpanda + the new fulltext image cleared both issues. The redpanda restart is operational, not in this commit. Signed-off-by: Michael Uray <michaeluray@users.noreply.github.com>
MichaelUray
force-pushed
the
fix/tracker-search-rootcause
branch
from
eb5fd20 to
7735bca
Compare
Author
|
Closing — this PR's diff was unintentionally scoped against I'll reopen this as a focused PR cherry-picked onto a fresh branch off |
Author
|
The fulltext version bump ( |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The compiled
MODEL_VERSIONin fulltext-pod was0.7.422while workspaces arealready on
0.7.423. Tx events were rejected with awrong versionwarning atthe indexer, so every new document landed in ES with a missing entry — the
symptom was that a Tracker title-search would return zero hits even for issues
that exist in the workspace.
This patch bumps
common/scripts/version.txtfrom0.7.422to0.7.423. Thesame file is the build-time source-of-truth for
MODEL_VERSIONviacommon/scripts/show_version.js, so rebuilding any pod from this branch willembed
0.7.423in itsbundle/model.json.Root-cause investigation
After the `0.7.422 → 0.7.423` model migration was applied to workspaces,
deploys that hadn't bumped `version.txt` continued to ship a fulltext-pod
compiled for `0.7.422`. The pod connects to the Tx queue fine, but every
incoming event for a workspace on a higher patch is rejected with:
```
supportedVersion: 0.7.422 (compiled into fulltext-pod)
version: 0.7.423 (workspace tx payload)
workspace:
```
No retries, no indexing. New workspaces never get their documents indexed; old
workspaces miss every post-migration document. Search silently returns zero hits
for any term that only appears in post-migration documents.
Acceptance criterion
After deploying a fulltext-pod built from this branch, the workspaces that were
upgraded to `0.7.423` start indexing their backlog. Direct ES verification:
```
curl -s -X POST localhost:9200/huly_storage_index_v2/_search \
-H 'Content-Type: application/json' \
-d '{"query":{"multi_match":{"query":"",
"fields":["searchTitle","fulltextSummary","identifier"]}}}'
```
returns hits within a few minutes of the pod restart (no manual reindex needed
— the pod re-consumes the buffered queue).
Future-prevention (out of scope for this PR)
The deploy pipeline does not currently fail when a workspace's persisted
`core:class:Version` patch exceeds the patch baked into any deployed pod's
`bundle/model.json`. A version-skew detector that refuses to publish in that
state would catch this class of bug at CI time. Tracking that separately.
Test plan