[Backend] Persist transcript segment rows and render the text format as a view #335

New issue

Closed

opened 2026-08-25 20:38:54 +00:00 by claude-bot · 1 comment

claude-bot commented 2026-08-25 20:38:54 +00:00

Collaborator

Copy link

Severity: HIGH. Found in the August 2026 session lifecycle review (#319).

The defect

The transcript is persisted as a single flat Text column (webapp/backend/app/models/session.py:152) with no segment rows. Four places then re-parse that text format, which makes the rendering format a load-bearing data contract:

• reminder_tasks.py:2786 — member erasure regex-parses the blob (_TRANSCRIPT_LINE_RE)
• audio_service.py:1052-1067 — highlight quotes validated by substring against the blob, while the stored speaker and timestamp_ref are LLM-asserted and never checked
• lore_service.py:236-285 — chunk_text hard-cuts by character count and can split mid-line, so a chunk can open with unattributed text
• SessionDetail.jsx:373-408 — the GM free-edits the raw blob, and a hand edit can break the erasure regex

Proposed fix

Add a segment table: session_id, track_owner_id, speaker_label, start, end, text, span_idx. Write it in process_audio; make merge_attributed_transcript a renderer over those rows.

Note the justification has shifted since the capture fix: this is no longer about timeline fidelity, it is about structural robustness. Erasure operates on rows instead of a regex. Highlights become validatable. Per-speaker QA ("this track had 40 minutes of speech and zero segments") becomes a query. track_owner_id makes a server-side speaker-label override detectable. And the text format can be re-rendered — ranges, scene blocks, anything — without re-transcribing.

Decide explicitly how GM free-editing interacts: either edits write back to rows, or the blob overrides rows with rows frozen as provenance. Do not leave it implicit.

Acceptance criteria

• Segment rows are written by process_audio and backfilled where a transcript exists
• merge_attributed_transcript renders from rows
• Member erasure operates on rows, and _TRANSCRIPT_LINE_RE is deleted
• Lore chunking splits on segment boundaries, never mid-line
• GM edit semantics are documented and tested
• A per-speaker QA query exists

**Severity: HIGH.** Found in the August 2026 session lifecycle review (#319). ## The defect The transcript is persisted as a single flat `Text` column (`webapp/backend/app/models/session.py:152`) with no segment rows. Four places then re-parse that text format, which makes the rendering format a load-bearing data contract: - `reminder_tasks.py:2786` — member erasure regex-parses the blob (`_TRANSCRIPT_LINE_RE`) - `audio_service.py:1052-1067` — highlight quotes validated by substring against the blob, while the stored `speaker` and `timestamp_ref` are LLM-asserted and never checked - `lore_service.py:236-285` — `chunk_text` hard-cuts by character count and can split mid-line, so a chunk can open with unattributed text - `SessionDetail.jsx:373-408` — the GM free-edits the raw blob, and a hand edit can break the erasure regex ## Proposed fix Add a segment table: `session_id`, `track_owner_id`, `speaker_label`, `start`, `end`, `text`, `span_idx`. Write it in `process_audio`; make `merge_attributed_transcript` a **renderer** over those rows. Note the justification has shifted since the capture fix: this is no longer about timeline fidelity, it is about **structural robustness**. Erasure operates on rows instead of a regex. Highlights become validatable. Per-speaker QA ("this track had 40 minutes of speech and zero segments") becomes a query. `track_owner_id` makes a server-side speaker-label override detectable. And the text format can be re-rendered — ranges, scene blocks, anything — without re-transcribing. Decide explicitly how GM free-editing interacts: either edits write back to rows, or the blob overrides rows with rows frozen as provenance. Do not leave it implicit. ## Acceptance criteria - [ ] Segment rows are written by `process_audio` and backfilled where a transcript exists - [ ] `merge_attributed_transcript` renders from rows - [ ] Member erasure operates on rows, and `_TRANSCRIPT_LINE_RE` is deleted - [ ] Lore chunking splits on segment boundaries, never mid-line - [ ] GM edit semantics are documented and tested - [ ] A per-speaker QA query exists

claude-bot added this to the v4.0.0 - Session Pipeline Accuracy milestone 2026-08-25 20:38:54 +00:00

claude-bot added the

bug

backend

labels 2026-08-25 20:38:54 +00:00

claude-bot referenced this issue 2026-08-26 00:12:42 +00:00

[Backend] Verify the returned speaker set matches the tracks that were sent #343

rbrooks referenced this issue from a commit 2026-08-26 01:46:55 +00:00

feat(backend): persist transcript segment rows (#335, part of #345)

claude-bot referenced this issue 2026-08-26 01:47:08 +00:00

[Backend] Emit start-end ranges and a deterministic tie-break in the merge #345

rbrooks referenced this issue from a commit 2026-08-26 02:05:23 +00:00

fix(backend): erase a member by track, not by guessing their name (#335)

rbrooks referenced this issue from a commit 2026-08-26 02:31:00 +00:00

perf(backend): merge same-speaker runs before prompting (#341)

claude-bot referenced this issue 2026-08-26 02:31:20 +00:00

[Backend] Compact the transcript prompt — merge same-speaker runs and use block timestamps #341

claude-bot referenced this issue 2026-08-27 23:28:05 +00:00

[Backend] Verify the returned speaker set matches the tracks that were sent #343

rbrooks referenced this issue from a commit 2026-08-28 00:45:01 +00:00

feat(backend): persist the events a summary was built from (#332, #333, #329)

rbrooks referenced this issue from a commit 2026-08-28 01:38:24 +00:00

feat(backend): chunk lore extraction on segment boundaries (#335)

rbrooks referenced this issue from a commit 2026-08-28 19:12:45 +00:00

feat(backend): close #335's remaining gaps — chunking, rendering, QA, docs

claude-bot commented 2026-08-28 19:15:06 +00:00

Author

Collaborator

Copy link

Verified; remaining gaps closed in 9dd7122. Two criteria are recorded as deliberately-not-done rather than met.

Criteria

• Segment rows are written by process_audio and backfilled where a transcript exists — writing yes; backfill deliberately refused, see below.
• merge_attributed_transcript renders from rows — not as written, see below.
• Member erasure operates on rows, and _TRANSCRIPT_LINE_RE is deleted — first half met; the regex stays, deliberately.
• Lore chunking splits on segment boundaries, never mid-line — was true on multi-pass, false on single-pass. Fixed.
• GM edit semantics are documented and tested — tested, and now documented.
• A per-speaker QA query exists — was not built. Now is.

The single-pass path never chunked on boundaries at all

Multi-pass packs whole TranscriptSegment rows, so a chunk can only begin and end between utterances. Single-pass — admin-selectable via LORE_PIPELINE_SINGLE_PASS — ran sample_evenly straight over the raw transcript characters, cutting mid-utterance freely. Exactly the defect this issue exists to prevent, on the path nobody looked at.

sample_evenly_over_segments keeps the property that matters for single-pass — coverage across the whole session, not the first twenty minutes — while only ever cutting between whole lines. Sessions with no rows keep the old behaviour.

The test first asserts the character sampler does produce a mid-line cut on that fixture, so it cannot pass vacuously.

chunk_segments had silently dropped chunk_text's overlap

chunk_text takes overlap_chars, documented as existing "so entities mentioned at chunk edges are not missed". The row-based replacement took no overlap parameter, so every post-#335 session lost that property with nothing saying so. Now carried as whole segments, and dropped rather than padded when it would push a chunk past its budget — an overlap that overflows the prompt would reintroduce the risk the chunker exists to remove.

Chunk text did not match the transcript for simultaneous speech

_render_segment_line always emitted a single [HH:MM:SS], while the stored transcript renders an overlapping line as [start-end] (#345). The extractor read a different rendering than the GM sees, for precisely the lines where two people talked at once. It now goes through audio_service.mark_overlapping — the same function the transcript renderer uses, not a second copy of the rule — and the test asserts byte equality with render_transcript_from_rows.

Two criteria that will not be met, and should be closed as such

"Backfilled where a transcript exists" was refused by migration a2b3c4d5e6f8, and the reasoning is right: the structure old blobs would need was never captured, and a best-effort re-parse produces rows that look authoritative and are not. Same call as #328's pre_timeline_fix marker. The criterion should be struck rather than left open.

"_TRANSCRIPT_LINE_RE is deleted" cannot follow while that holds. It still runs for sessions recorded before rows existed, and for a transcript a GM has hand-edited away from its rows. Rows are primary — _scrub_session_transcript scrubs by track_owner_id — but the regex is the fallback for a corpus that will never have rows.

"merge_attributed_transcript renders from rows" is likewise not literally true: there are two renderers, merge_attributed_transcript over in-memory dicts and render_transcript_from_rows over rows, kept byte-identical by a test. The "text is a view of the rows, one renderer" refactor did not happen. Recording it plainly rather than ticking the box — the property holds, the structure the criterion asked for does not.

GM edit semantics

Implemented and tested, documented only in code comments; docs/ mentioned none of this. Now in docs/API.md, and flagged as what it actually is: a third option, neither of the two the issue proposed. On erasure of a hand-edited transcript the code writes to both — redacting the rows and separately scrubbing the text — so rows are not "frozen as provenance", they are mutated. Defensible for a legal erasure, and now written down.

Per-speaker QA

transcript_qa_service plus a GM-only endpoint, grouped by (track_owner_id, speaker_label) so a mid-session rename cannot merge two people.

It states its own limitation rather than overselling: audio duration per track is not stored beside the rows, so it answers "how much did each speaker's transcript contain" and can show a track that looks thin — but it cannot alone confirm the motivating case, "this track had 40 minutes of speech and zero segments". It raises the suspicion; resolving it needs the source audio.

Also added the two summarisation-runs endpoints from #333/#424, which docs/API.md had never mentioned.

Closing, on the understanding that the three struck criteria are closed as won't-do rather than done.

**Verified; remaining gaps closed in `9dd7122`.** Two criteria are recorded as deliberately-not-done rather than met. ## Criteria - [ ] **Segment rows are written by `process_audio` and backfilled where a transcript exists** — writing yes; **backfill deliberately refused**, see below. - [ ] **`merge_attributed_transcript` renders from rows** — **not as written**, see below. - [ ] **Member erasure operates on rows, and `_TRANSCRIPT_LINE_RE` is deleted** — first half met; the regex **stays**, deliberately. - [x] **Lore chunking splits on segment boundaries, never mid-line** — was true on multi-pass, **false on single-pass**. Fixed. - [x] **GM edit semantics are documented and tested** — tested, and now documented. - [x] **A per-speaker QA query exists** — **was not built.** Now is. ## The single-pass path never chunked on boundaries at all Multi-pass packs whole `TranscriptSegment` rows, so a chunk can only begin and end between utterances. Single-pass — admin-selectable via `LORE_PIPELINE_SINGLE_PASS` — ran `sample_evenly` straight over the raw transcript **characters**, cutting mid-utterance freely. Exactly the defect this issue exists to prevent, on the path nobody looked at. `sample_evenly_over_segments` keeps the property that matters for single-pass — coverage across the whole session, not the first twenty minutes — while only ever cutting between whole lines. Sessions with no rows keep the old behaviour. The test first asserts the **character** sampler *does* produce a mid-line cut on that fixture, so it cannot pass vacuously. ## chunk_segments had silently dropped chunk_text's overlap `chunk_text` takes `overlap_chars`, documented as existing "so entities mentioned at chunk edges are not missed". The row-based replacement took no overlap parameter, so **every post-#335 session lost that property** with nothing saying so. Now carried as whole segments, and dropped rather than padded when it would push a chunk past its budget — an overlap that overflows the prompt would reintroduce the risk the chunker exists to remove. ## Chunk text did not match the transcript for simultaneous speech `_render_segment_line` always emitted a single `[HH:MM:SS]`, while the stored transcript renders an overlapping line as `[start-end]` (#345). The extractor read a different rendering than the GM sees, for precisely the lines where two people talked at once. It now goes through `audio_service.mark_overlapping` — the same function the transcript renderer uses, not a second copy of the rule — and the test asserts byte equality with `render_transcript_from_rows`. ## Two criteria that will not be met, and should be closed as such **"Backfilled where a transcript exists"** was refused by migration `a2b3c4d5e6f8`, and the reasoning is right: the structure old blobs would need was never captured, and a best-effort re-parse produces rows that *look authoritative and are not*. Same call as #328's `pre_timeline_fix` marker. The criterion should be struck rather than left open. **"`_TRANSCRIPT_LINE_RE` is deleted"** cannot follow while that holds. It still runs for sessions recorded before rows existed, and for a transcript a GM has hand-edited away from its rows. Rows *are* primary — `_scrub_session_transcript` scrubs by `track_owner_id` — but the regex is the fallback for a corpus that will never have rows. **"`merge_attributed_transcript` renders from rows"** is likewise not literally true: there are two renderers, `merge_attributed_transcript` over in-memory dicts and `render_transcript_from_rows` over rows, kept byte-identical by a test. The "text is a view of the rows, one renderer" refactor did not happen. Recording it plainly rather than ticking the box — the *property* holds, the structure the criterion asked for does not. ## GM edit semantics Implemented and tested, documented only in code comments; `docs/` mentioned none of this. Now in `docs/API.md`, and flagged as what it actually is: a **third** option, neither of the two the issue proposed. On erasure of a hand-edited transcript the code writes to **both** — redacting the rows and separately scrubbing the text — so rows are not "frozen as provenance", they are mutated. Defensible for a legal erasure, and now written down. ## Per-speaker QA `transcript_qa_service` plus a GM-only endpoint, grouped by `(track_owner_id, speaker_label)` so a mid-session rename cannot merge two people. It states its own limitation rather than overselling: audio duration per track is not stored beside the rows, so it answers "how much did each speaker's transcript contain" and can show a track that looks thin — but it cannot alone confirm the motivating case, *"this track had 40 minutes of speech and zero segments"*. It raises the suspicion; resolving it needs the source audio. Also added the two `summarisation-runs` endpoints from #333/#424, which `docs/API.md` had never mentioned. Closing, on the understanding that the three struck criteria are closed as won't-do rather than done.

claude-bot closed this issue 2026-08-28 19:16:10 +00:00

rbrooks referenced this issue from a commit 2026-09-01 00:45:52 +00:00

fix(privacy): stop erasure scrubbing a member who shares a name (#407)

claude-bot referenced this issue 2026-09-01 00:46:13 +00:00

fix(privacy): stop erasure scrubbing a member who shares a name (#407) #475

claude-bot referenced this issue 2026-09-01 02:37:03 +00:00

[Backend] Disambiguate per-member erasure so it can't scrub the wrong person #407

claude-bot referenced this issue 2026-09-17 17:50:07 +00:00

[Backend][Data loss] Shortening transcript retention destroys transcripts with no trash, no grace and no warning #680

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

feat/1328-fill-it-in

feat/1328-fill-frontend

feat/1328-fill-backend

feat/9-foundry-push

fix/9-foundry-live

feat/9-foundry-push-frontend

renovate/celery-5.x

feat/5-foundry-connect

feat/9-foundry-push-backend

feat/9-foundry-push-module

feat/5-foundry-frontend

feat/5-foundry-backend

feat/5-foundry-module

release/v4.8.0-rc1

docs/d341-convert-draft

feat/958-update-to-version

feat/958-convert-sheet

feat/958-pathbuilder-import-frontend

fix/1360-heading-order

feat/958-pathbuilder-import-backend

feat/11-weekly-digest

feat/1341-auto-update

docs/d332-superseded

chore/1345-names-cleanup

feat/1342-mentioned-pages

feat/1328-recipes

fix/1346-pgdg-key

perf/1247-shared-recording-stream

chore/132-gitleaks-allowlist

release/v4.7.1

spike/foundry-module

release/v4.7.1-rc1

docs/decisions-d332-d337

fix/bot-certifi

chore/release-4.7.0

chore/release-4.7.0-rc4

chore/deps-4.7.0

chore/release-4.7.0-rc3

fix/1280-quote-must-say-it

fix/1257-names-row-squeeze

chore/release-4.7.0-rc2

fix/1245-pg-upgrade-count

chore/release-4.7.0-rc1

feat/1257-names-in-prep

feat/1257-be

feat/1257-fe

feat/1257-rating-fixes

design/1328-fill-it-in

feat/1257-name-splits

fix/1326-redis-503

feat/1280-fact-suggestions

feat/1280-be

feat/1280-fe

design/1280-fact-suggestions

feat/1279-infobox

feat/1279-be

feat/1279-fe

feat/1321-shelf-copies

design/1279-infobox

feat/1243-table-find

feat/1257-who-rated

feat/1243-prep-drawer

feat/1243-sheet-pickers

design/1243-browse-in-place

feat/1315-hotwords-default

feat/1242-system-filters

feat/1257-more-name-styles

feat/506-leg3-hotwords

design/1242-system-filters

fix/1302-packs-polish

feat/1241-rules-library

design/1241-rules-library

feat/1245-postgres-18

integ/4.6.2

fix/1263-map-ui-2

fix/1263-map-server

fix/1263-map-ui-1

fix/1261-editor-link-menu

fix/1229-axe-4.14-name-mismatch

renovate/axllent-mailpit-1.x

renovate/eslint-monorepo

renovate/authlib-1.x

chore/release-4.6.0

chore/release-4.6.0-rc2

fix/460-rc2-screens

fix/460-rc2-server

fix/release-prerelease-exit

chore/release-4.6.0-rc1

feat/125-campaign-templates

feat/126-calendar

feat/1181-pictures-and-files

feat/1190-event-people

integ/4.6.0

feat/1191-line-of-the-night

feat/1200-starter-packs

chore/bot-multidict-and-playwright-group

fix/1202-this-week-answered-count

fix/122-124-leftovers

fix/1178-get-routes-that-write

fix/1203-journeys-check-names

design/125-campaign-templates

feat/126-calendar-engine

design/126-in-world-calendar

fix/1189-cited-stamp-in-range

fix/1189-v4-looser-check

fix/1189-richer-beats

fix/1113-export-bind-lists

fix/1154-release-notes-by-file

chore/release-4.5.0

chore/release-4.5.0-rc12

fix/1135-wiki-markup-as-text

fix/demo-usage-cost-in-window

chore/release-4.5.0-rc11

fix/1121-sheet-consistency

fix/1121-sheet-5e-terms-and-card-hp

copy/1122-busiest-pages

fix/1121-relevant-choices

fix/1121-wiki-create-npc-save-sheet-links

fix/1029-menu-stays-on-screen

docs/prototype-transcript-bin-wording

fix/1023-editor-save-row-back-scroll

fix/1020-search-exact-first

fix/1020-table-prep

fix/1020-shell-wordmark-footer-bell

fix/1020-wiki-article-party

fix/872-admin-kept-until-phone-tables

feat/l13-milestone-level-waiting

fix/1000-1001-bell-older-setup-context

fix/999-pronouns-in-prompts

fix/l19-other-class-feats

fix/1010-transcript-window-ordinary-confirm

docs/d254-d269-decisions

fix/702-member-search

fix/680-transcript-bin

fix/993-unidentified-prompts

fix/841-redis-timeouts

fix/990-binned-not-exported

fix/830-export-prep-shelf

fix/deps-audit-2026-10-01

fix/877-title-reads

fix/798-audio-received-at

build/lane11-17-j7

build/lane11-16-levelup

build/lane11-14-seams

build/lane11-14-seed

build/lane11-15-start

build/lane11-13-old-block-out

fix/980-review-r3

build/lane11-12-block

build/lane11-8-packs

fix/demo-seed-canonical-names

build/lane11-11-hot-half

docs/l11-decisions

build/lane11-7-convert

build/lane11-10-editing

fix/npm-audit-brace-expansion

build/lane11-9-sheet-page

fix/bot-pyjwt

build/lane11-6-content

fix/lane11-rank-names

build/lane11-2b-language

build/lane11-4-js-evaluator

build/lane11-3-server

build/lane11-5a-pf2e

build/lane11-5b-5e

feat/design-admin

build/lane11-2-evaluator

build/lane11-1-sheet-pieces

build/lane11-0-drawing

fix/943-quest-objectives-fk

fix/prepsheet-shelf-flake

fix/945-leftovers

build/demo-gm-copy

fix/901-email-landings

build/lane10-8-journeys

build/demo-seed-lanes-8-10

fix/887-gm-own-confirmation

build/lane9-5-j1-admin

fix/918-audience-click

fix/useasync-overtaken

ci/939-critical-path

test/937-backend-suite-speed

chore/claude-orchestration

fix/924-xp-gm-only

fix/session-stale-poll

docs/decisions-d239-d242

fix/930-pypdf

build/lane8-journeys

build/925-quest-editor

fix/894-private-page-pictures

build/lane8-p4-drafts

build/lane8-p7-map

build/lane8-p6-handouts-rules

fix/wiki-fixture-names

build/lane10-d227-test-usage

fix/rsvp-horizon-test-tuesday

fix/media-volume-owner

build/lane8-p3-editor

fix/912-unidentified-rename

build/lane8-p5-party-quests

build/lane8-handout-takeback

build/lane10-pickers

build/lane8-p2-article

build/lane8-6-map

build/lane10-7b-email-pages

build/lane8-5-handouts

build/lane10-7a-test-the-bot-pages

build/lane8-p1-pages

build/lane8-4-quests

build/lane8-2b-feeds

build/lane8-3-parties

build/lane8-2a-links

build/lane10-5-commands

build/lane9-6-seed

build/lane10-4b-reactions

build/lane9-4d-pages

build/lane9-4c-pages

build/lane10-4a-posts

build/lane10-3-email

fix/891-web-fonts

build/lane9-4b-pages

build/lane10-6-test-the-bot

build/lane10-2-notify-out

build/lane8-1-wiki-text

build/lane9-4a-frame

design/lane10-drawings

fix/j6-budget

fix/j5-phone-flake

fix/869-test-leaks

fix/843-record-start-followups

build/lane7-all

build/lane6-all

build/lane9-b2-server

chore/changelog-fragments

docs/decisions-d218

build/lane9-a-owner-overview

fix/rule-card-level-label

fix/834-retention-semantics

fix/o3c-record-without-announcement

docs/decisions-d179

docs/decisions-d131-d170

fix/851-commit-before-response

build/lane6-j3-seed

build/lane9-b1-d67-identity

fix/841-blocking-loop

build/lane9-c-backups-audit

fix/vote-race-and-start-commit

fix/recording-announcement

fix/proposal-read-leak

fix/last-admin-guard

build/lane6-p4c-planning

build/lane6-p4b-margin

build/lane6-p4a-sheet

build/lane5-j4-seed

build/lane6-base

build/lane7-pages-talk

build/lane5-pages

build/lane7-pages-safety

build/lane7-p3-safety

build/lane7-p2-notify

build/lane6-p3-planning

build/lane6-p2-history

build/lane6-p1b-items

build/lane7-p1-threads

build/lane5-p6-faces

build/lane6-p1a-sheet

build/lane5-p5-find

build/lane5-p4a-board

build/lane5-p4b-scenes

build/lane5-p3-live

build/lane5-base

build/lane5-p2-cards

docs/lane5-decisions

build/review-r2-wide

fix/review-r1

build/lane5-p1-scenes

build/demo-seed

build/lane4-journeys-j5

build/lane4-page-review-b

build/lane4-page-review-a

build/lane4-page-read

build/lane4-journeys

build/lane4-page-sess2

build/lane4-page-sess1

build/lane4-notes

build/lane4-discord-on-approval

build/lane4-scheduling

build/lane4-versions

build/760-session-number

build/lane4-decisions

build/797-erase-no-regenerate

build/test-race-audit

build/lane3-completions

build/794-dark-only

build/796-titles-scroll

build/791-retention-anchor

build/a11y-sweep

build/shell-followups

build/retention-preview

build/753-backup-readback

docs/d91-d93

build/lane3-j1

build/ci-harness-paths-selftest

fix/useauth-test-race

build/ci-harness-paths

build/777-ai-settings-read

build/lane3-settings-c

build/lane3-settings-b

build/lane3-j6

build/lane3-sessionform

build/lane3-settings-a

build/lane3-members

build/lane3-thisweek

build/lane3-story

chore/87-align-python-3.12

v4.8.0-rc1

v4.7.1

v4.7.1-rc1

v4.7.0

v4.7.0-rc4

v4.7.0-rc3

v4.7.0-rc2

v4.7.0-rc1

v4.6.2

v4.6.2-rc4

v4.6.2-rc3

v4.6.2-rc2

v4.6.2-rc1

v4.6.1

v4.6.1-rc1

v4.6.0

v4.6.0-rc2

v4.6.0-rc1

v4.5.3

v4.5.3-rc1

v4.5.2

v4.5.2-rc1

v4.5.1

v4.5.1-rc2

v4.5.1-rc1

v4.5.0

v4.5.0-rc12

v4.5.0-rc11

v4.5.0-rc10

v4.5.0-rc9

v4.5.0-rc8

v4.5.0-rc7

v4.5.0-rc6

v4.5.0-rc5

v4.5.0-rc4

v4.5.0-rc3

v4.5.0-rc2

v4.5.0-rc1

v4.4.1

v4.4.0

v4.3.0

v4.2.3

v4.2.2

v4.2.1

v4.2.0

v4.1.2

v4.1.1

v4.1.0

v4.0.1

v4.0.0

v3.11.4

v3.11.3

v3.11.2

v3.11.1

v3.11.0

v3.10.0

v3.9.1

v3.9.0

v3.8.0

v3.7.0

v3.6.1

v3.6.0

v3.5.0

v3.4.1

v3.4.0

v3.3.0

v3.2.0

v3.1.0

v3.0.0

v2.1.0

v2.0.0

v1.1.0

v1.0.0

v0.12.0

v0.11.0

v0.10.0

v0.9.1

v0.3.3

v0.9.0

v0.8.0

v0.3.2

v0.3.1

v0.3.0

v0.7.0

v0.6.0

v0.5.0

v0.4.0

v0.2.1

v0.2.0

v0.1.1

v0.1.0

Labels

Clear labels   

backend

Issue related to the backend

  

bot

Issue related to the bot

  

bug

Something is not working

  

duplicate

This issue or pull request already exists

  

enhancement

New feature

  

frontend

Issue related to the frontend

  

help wanted

Need some help

  

invalid

Something is wrong

  

question

More information is needed

  

recording

Issue related to the recording system

  

security

Security hardening / vulnerability work

  

wontfix

This won't be fixed

No labels

backend

bot

bug

duplicate

enhancement

frontend

help wanted

invalid

question

recording

security

wontfix

Milestone

Clear milestone

No items

No milestone

v4.0.0 - Session Pipeline Accuracy

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

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

rbrooks/Quest-Board#335

No description provided.