Skip to content

SCHEMA CHANGE (draft, not for merge without a ruling): the Polis 2 permission can be recorded in Postgres, one new table, switched off - #3451

Draft
colinmegill wants to merge 5 commits into
edgefrom
server/delphi-entitlement-table
Draft

colinmegill wants to merge 5 commits into
edgefrom
server/delphi-entitlement-table

Conversation

@colinmegill

Copy link
Copy Markdown
Member

SCHEMA CHANGE: one new table

The Polis 2 permission can be recorded in Postgres: one new table, one server function behind a setting that is off, and a read route for the signed-in caller

Observable changes

  • A new table, delphi_entitlements (migration 000048), created at the next deploy. Nothing reads or writes it with the default setting. Its creation holds a lock on users for a few milliseconds, once; if users is being written at that instant it waits at most 0.2 s and then gives up, failing the deploy cleanly (below).
  • A new route, GET /api/v3/delphi/me. A signed-in caller gets {"delphi_entitled": true} or {"delphi_entitled": false}; without a token, 401 {"error":"No authentication token found"}, as every signed-in route answers. With the default setting the answer is the access token's delphi_enabled claim, so it says exactly what the Polis 2 routes would decide before their owner check. No client calls it yet.
  • A new setting, POLIS_DELPHI_ENTITLEMENT, default claim. Unset or blank is claim. Any value other than claim, claim_or_db or db stops the server at startup.

Nothing else changes with the default. Every reply of the four Polis 2 routes (POST /api/v3/delphi/jobs, POST /api/v3/delphi/batchReports, POST /api/v3/collectiveStatement, GET /api/v3/reportNarrative) is byte for byte what it was, and the database is never read for the permission. The collective-statement and Delphi recordings replay unchanged.

The table

CREATE TABLE public.delphi_entitlements(
 uid integer PRIMARY KEY REFERENCES public.users(uid) ON DELETE CASCADE,
 granted_at bigint NOT NULL DEFAULT public.now_as_millis(),
 granted_by integer REFERENCES public.users(uid) ON DELETE SET NULL,
 source text NOT NULL CHECK(source IN ('auth0_role','site_admin'))
);

One row per account that may use Polis 2: when it was granted, who granted it, and whether it was carried over from the identity provider's role or granted by a site administrator. Deleting an account deletes its row; deleting the granter keeps the row and clears granted_by. No existing table, column, index, constraint, function, rule or grant changes, and the migration creates no function, trigger or rule of its own (the two foreign keys add PostgreSQL's internal referential triggers on users and on the new table). Declared additive: a release without it runs beside it unchanged.

Locks at the deploy (measured on PostgreSQL 17.11): the two foreign keys take SHARE ROW EXCLUSIVE on users until the migration commits, 5 ms median and 9 ms at most over 40 runs. Reads of users do not wait for that lock, and neither do votes, comments and the next comment from people who already have an account. Creating a users row does: a new anonymous voter's first vote or comment, and a first sign-in.

Who can wait, and for how long. If another session holds a conflicting lock on users at the instant the migration starts (a transaction that has written users and not yet committed, such as an import or another first sign-in, or a vacuum of users), the migration waits for its lock and every new users row queues behind it. The migration's own lock timeout is 0.2 s, not the migration runner's 5 s, because a first sign-in gives up on a lock after 0.5 s and is answered HTTP 500, and that request can be a vote or a comment. So the longest anyone waits is about 0.2 s: new accounts (a new anonymous voter's first vote or comment, a first sign-in) and, because each waiting first vote holds one of the box's vote connections, briefly other votes on that box. Nobody is refused. Measured 20 times beside an open transaction writing users, with three new accounts' first votes queued behind the migration (one signed in, two anonymous) and an existing participant's vote waiting for a vote connection: the migration gave up within 0.33 s (it waits 0.2 s; the rest is the runner starting), every vote was answered (the test also checks that each is stored), and the longest wait was 0.27 s (signed-in first votes 0.22 to 0.27 s, anonymous first votes 0.22 to 0.27 s, the existing participant's votes 0.20 to 0.25 s). With the runner's 5 s instead, the signed-in account's first vote was answered HTTP 500 in all 20 runs, the anonymous first votes waited 5.0 s, and the existing participant's vote 0.5 s.

On a busy instant the migration gives up after 0.2 s with nothing changed: no table and no history row. Nothing on that box has been stopped yet: the hooks before it stop no service, and the migration runs before any service is replaced (scripts/after_install.sh, which stops on the failure). The box was already taken out of the load balancer, so the deploy fails there and goes no further, and the other web boxes keep serving the previous release. CodeDeploy's automatic rollback on a failed deployment (on for both deployment groups) then redeploys the previous release, one box at a time, like any deploy. The deploy is then run again.

Nothing on the vote, comment or next-comment path ever reads the table.

Reversal: down/000048_drop_delphi_entitlements.sql drops the table only while it is empty and is never run automatically. It takes ACCESS EXCLUSIVE on users for milliseconds, under the same 0.2 s bound: while users is busy it gives up with nothing changed (the table, its rows and the history row stay) and is run again later.

The setting

POLIS_DELPHI_ENTITLEMENT Who may use Polis 2 Database read
claim (default) the token's delphi_enabled claim, as today none
claim_or_db the claim, or a row in delphi_entitlements one, only when the claim is absent
db a row only one

The read is SELECT 1 FROM delphi_entitlements WHERE uid = ($1); on the server's ordinary read-write pool, on the four Polis 2 routes and the new route only. Those routes never run on the participation pools, so votes, comments and the next comment never make the read and cannot wait on it; the read holds its connection for that one statement. A failed read answers through each route's existing error reply, and nothing starts. The owner rule after it (the conversation's owner or a site administrator) is unchanged in every mode.

Not moved

The vote CSV import, POST /api/v3/votes-bulk, still reads the claim directly under every value of the setting. Changing that handler is proposed separately. Until it is, an account recorded only in the table can start Delphi work but not import votes, and under db a claim holder can still import into its own conversation.

Rust

polis-auth's OIDC profile no longer carries the namespaced delphi_enabled claim. Nothing read it (no polis-api route uses the profile); a Rust test now checks that no source file of polis-auth or polis-api names the claim.

Commits

  1. migration 000048: the table; release.txt, compat.txt (additive), docs/migrations.md (the declaration and its lock measurement), the forward-compatibility ledger, the regenerated first-deploy report; the reversal; the coordinator schema census (measured on PostgreSQL 17.11) follows the new table; an integration test of the table's constraints. The characterization schema catalog, which only the recorder reads, is refreshed in its own change after this one, as the recording rules require.
  2. server: isDelphiEntitled (server/src/routes/delphi/entitlement.ts) and the four routes asking it; the setting (server/src/config.ts); GET /api/v3/delphi/me; docs (docs/configuration.md, "Polis 2 permission") and example.env; the route census; unit tests of the function, the routes and the setting under every value, a test that the vote import is unchanged under every value, and an integration test of the route and the setting against the real stack. The collective-statement mutation check follows the moved line and gains a mutation of the function's default; both are caught by the recordings.
  3. polis-auth: the claim removed from the profile, with its test and README.
  4. migration 000048, lock timeout: the file's lock timeout is 0.2 s instead of the migration runner's 5 s, and so is its reversal's; the file header, its declaration in docs/migrations.md, the schema census (checksum and line pointers) and the first-deploy report follow. A test, server/__tests__/participation-pg/delphi-entitlements-migration.pgtest.ts, holds a transaction writing users, starts the deploy with the real migration runner, and while it waits sends a signed-in account's first vote, anonymous first votes and an existing participant's vote through the server's own middleware for POST /api/v3/votes.

Tests

Written before the code; on edge the new server suites fail (the vote-import one pins today's behaviour and passes) and the Rust test fails naming the file that mapped the claim.

Run locally, on the work machines: every check these paths trigger (38), including the migration runner checks (fresh image: 38 receipts), the coordinator schema census, the server unit and integration suites (191 suites, 3144 tests), the route census, every recording replay (collective statements with their mutation check, Delphi characterization, identity, post-comments, treevite, routing), the CLI differential, the API checks (1351 Rust tests), the queue and authority checks, the vote-sign lint and the six end-to-end shards. One end-to-end test that also fails intermittently on other branches (the alpha client's anonymous-session reload) failed once and passed twice when run again; the result-reads check failed once while its database was starting and passed when run again.

The lock timeout has its own test, written first: run against the 5 s file it failed (the signed-in account's first vote was answered 500, and the reversal waited 5 s); with 0.2 s it passes. After that change these ran again on the work machines: the migration runner checks (fresh image: 38 receipts), the coordinator schema census test, the result-reads and participation suites where the new test lives (17 suites, 97 tests) and the server unit and integration suites (191 suites, 3144 tests). The full set above was not run again for a changed timeout, its comments and a test.

🤖 Generated with Claude Code

https://claude.ai/code/session_01KvftUAdasWzxmMYdioZJWs

🤖 Generated with Claude Code

https://claude.ai/code/session_01KvftUAdasWzxmMYdioZJWs

colinmegill and others added 5 commits November 18, 2026 19:15
… accounts may use Polis 2 (not yet read)

One table and nothing else: no existing table, column, index, constraint,
function, trigger, rule or grant changes, and the file creates no function,
trigger or rule.

  delphi_entitlements
    uid         integer primary key, references users(uid) on delete cascade
    granted_at  bigint not null, default now_as_millis()
    granted_by  integer, references users(uid) on delete set null
    source      text not null, check in ('auth0_role', 'site_admin')

Nothing reads or writes it in this commit. The server reads it only under a
setting that is off by default, added in the next commit.

Locks, measured on PostgreSQL 17.11: the two foreign keys take SHARE ROW
EXCLUSIVE on users until commit, 3 ms median and 6 ms at most over 20 runs.
While it is held, reads of users, inserts into participants and writes to
conversations went on without waiting; inserts and updates of users (a new
anonymous participant's account, a first sign-in) waited for the commit.
Beside an open transaction writing users the file waits its 5 s lock_timeout
and fails with nothing changed, once, at the deploy. Nothing on the vote,
comment or next-comment path reads the table.

Declared additive (compat.txt, with its evidence in docs/migrations.md); listed
in release.txt; the forward proof's additive ledger and the first-deploy
report's release list include it, and the report is regenerated. The
reversal, down/000048_drop_delphi_entitlements.sql, refuses while any row is
stored; dropping the foreign keys takes ACCESS EXCLUSIVE on users until
commit (milliseconds, 5 s at most).

The coordinator schema census follows the new table: catalog.json measured
by coordinator-rs/tools/schema_census.py on a fresh PostgreSQL 17.11 (the new
table, its index and four constraints, and the file's checksum); the row type
and table entry in rows.rs; 770 columns (was 766) in the census test, the
mapping example and the README. The characterization schema catalog
(server/characterization/catalog.json, read only when recording) is refreshed
in its own change, as the recording rules require.

Test: an integration test against the migrated test database checks the four
columns, types, nullability and default; no trigger and no rule; a grant from
each source; one row per account; a source outside the closed set, a missing
source or time, and an absent account or granter refused; deleting an
account deletes its row, deleting its granter keeps the row and clears
granted_by.

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KvftUAdasWzxmMYdioZJWs
…nd POLIS_DELPHI_ENTITLEMENT (default claim: unchanged); GET /api/v3/delphi/me answers it

isDelphiEntitled (server/src/routes/delphi/entitlement.ts) answers whether an
account may use Polis 2. The four routes that start Delphi work ask it first,
in place of reading req.p.delphiEnabled themselves:

  POST /api/v3/delphi/jobs          (routes/delphi/jobs.ts)
  POST /api/v3/delphi/batchReports  (routes/delphi/batchReports.ts)
  POST /api/v3/collectiveStatement  (routes/collectiveStatement.ts)
  GET  /api/v3/reportNarrative      (routes/reportNarrative.ts)

and then apply the conversation-owner rule (generationOwner.ts) exactly as
before. A refusal is the reply each route already gave a caller without the
claim, byte for byte.

POLIS_DELPHI_ENTITLEMENT (config.ts, delphiEntitlement) says where the answer
comes from:
- claim (unset or blank: the default): the token's delphi_enabled claim, as
  these routes always read it. The database is never read for this.
- claim_or_db: the claim, or else a row for the account in
  delphi_entitlements (migration 000048).
- db: a row only.
Any other value stops the server at startup.

Under claim_or_db and db the read is one SELECT by primary key
(SELECT 1 FROM delphi_entitlements WHERE uid = ($1);) on the ordinary
read-write pool, on these routes only; it holds its connection for that
statement and nothing else. These routes never run in participation scope,
so votes, comments and the next comment never make it and cannot wait on it.
A failed read answers through each route's existing error reply and nothing
starts.

New route: GET /api/v3/delphi/me, signed-in callers only (hybridAuth: 401
without a token, as every such route), answers {"delphi_entitled": true|false}
through the same function. Its path is made of words the client error
reporters already know, so no client copy changes; no nginx Rust selector
matches it (the /api/v3/delphi selectors are exact paths, and the one pattern
is /api/v3/delphi/runs/<id>). The route census gains it (id 211).

Not moved: the vote CSV import, POST /api/v3/votes-bulk (routes/votes.ts),
still reads req.p.delphiEnabled directly under every value of the setting. A
change to that handler is proposed separately.

Documented in docs/configuration.md ("Polis 2 permission") and example.env.

Tests (written first; on edge the new suites fail and the import's passes):
- unit, delphiEntitlement.test.ts: the function under each value (no read of
  any kind under claim, whatever the claim; one read by primary key on the
  read-write pool otherwise; no read for an account number that is not one; a
  failed read throws; an unknown value answers as claim); the four routes
  under each value (under claim, the owner with the claim proceeds after only
  the owner read, and an account with a row but no claim gets today's
  refusal with nothing read; under claim_or_db and db, a row admits its owner
  and does not reach another's conversation, the claim alone is refused under
  db, a failed read starts nothing); the new route under each value.
- unit, delphiEntitlementSetting.test.ts: blank and unset are claim; the three
  values are taken as written; anything else stops the server.
- unit, votesBulkEntitlementUnchanged.test.ts: under every value the import
  refuses an account without the claim and admits a claim holder to its owner
  check, reading no entitlement.
- integration, delphi-entitlement.test.ts, against the real stack: 401
  without a token; under claim the claim decides and a row is ignored; under
  claim_or_db either one; under db the row decides, and an owner with a row
  starts a pipeline run while the same owner without it gets today's 403.
The existing tests of these routes (delphiGenerationOwner, votesBulkOwner,
the generation-owner and claim integration tests) are unchanged and pass.
- The collective-statement mutation check: the mutation that drops the
  permission check in collectiveStatement.ts now finds the new line (its text
  moved; the same five cases fail), and a new mutation, ENTITLEMENT-DEFAULT,
  makes the function's default answer yes for everyone and fails the same
  five cases.

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KvftUAdasWzxmMYdioZJWs
… claim

Profile (queue-rs/polis-auth/src/oidc.rs) mapped the namespaced
delphi_enabled claim as request metadata. Nothing read it: no polis-api route
calls Profile, and the only callers are this crate's own tests. It is removed,
so no Rust route can be written that reads the claim; whether an account may
use Polis 2 is recorded by Polis (the delphi_entitlements table), and a Rust
route that needs it reads it there. A token that carries the claim is mapped
exactly as before, minus that field.

Test (written first; it failed on the previous source, naming oidc.rs): no
source file of polis-auth, and none of polis-api, contains the claim's name.
The claim-fallback test still feeds the claim and no longer reads it back.
The README says the claim is not mapped.

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KvftUAdasWzxmMYdioZJWs
Brings in edge up to the 2.45.2 preparation: the Delphi shadow's comment
selection. No conflicts; no file of this branch changed on edge.

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KvftUAdasWzxmMYdioZJWs
…runner's 5 s, so no vote or comment is refused while it waits

Creating delphi_entitlements takes SHARE ROW EXCLUSIVE on users (its two
foreign keys). While the migration waits for that lock, behind a session
holding a conflicting lock on users (a transaction that wrote users, or a
vacuum of it), every new writer of users queues behind it. A signed-in
account's first request creates its users row in a transaction that gives
up on a lock after 500 ms (server/src/db/pg-query.ts) and is then answered
HTTP 500, and that request can be a vote or a comment. With the runner's
5 s, such a first vote sent during the wait was refused.

The file now sets lock_timeout to 200 ms. On a busy instant the migration
gives up after about 0.2 s with nothing changed (no table, no history row),
the deploy stops on that box before any service is replaced, and it is run
again. Nobody waits longer than that and nobody is refused. The table and
both foreign keys are unchanged. The reversal
(down/000048_drop_delphi_entitlements.sql), which takes ACCESS EXCLUSIVE on
users, gets the same bound; a refused down changes nothing.

The file header and its declaration in docs/migrations.md now say what it
locks, for how long and why 200 ms (they said nothing was refused), and that
the foreign keys add PostgreSQL's internal referential triggers. The
coordinator schema census follows the new bytes (the checksum, re-measured on
a fresh PostgreSQL 17.11, and the declaration pointers, seven lines lower), as
does the first-deploy report.

Test: server/__tests__/participation-pg/delphi-entitlements-migration.pgtest.ts,
run by scripts/test-delphi-result-reads.sh. An open transaction writes users;
the real runner's deploy waits on it; while it waits, a signed-in account's
first vote, two anonymous first votes and, once they have queued, an existing
participant's vote run the middleware of POST /api/v3/votes in order
(onParticipationPools, the token step, ensureParticipant, handle_POST_votes),
with the participation pools at 3 connections. Without the file's own bound
(the runner's 5 s) the signed-in first vote is answered 500 and not recorded.
With 200 ms every vote is answered and recorded, the migration fails with
nothing changed, and the next deploy applies it. The reversal, under the same
bound, gives up with nothing changed beside a transaction reading users, and
drops the empty table once it can. Run against the 5 s file, the released
case and the reversal case failed; with 200 ms all three pass.

Measured on PostgreSQL 17.11, 20 runs with each file: with 200 ms every vote
was answered, the longest after 0.27 s; with 5 s the signed-in first vote was
answered 500 in all 20, and the anonymous first votes waited 5 s.

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KvftUAdasWzxmMYdioZJWs
@github-actions

Copy link
Copy Markdown
Contributor

Delphi Coverage Report

File Stmts Miss Cover
polismath/init.py 2 0 100%
polismath/benchmarks/bench_pca.py 128 107 16%
polismath/benchmarks/bench_repness.py 81 65 20%
polismath/benchmarks/bench_update_votes.py 38 28 26%
polismath/benchmarks/benchmark_utils.py 34 0 100%
polismath/components/init.py 1 0 100%
polismath/components/config.py 165 70 58%
polismath/conversation/init.py 2 0 100%
polismath/conversation/conversation.py 1293 264 80%
polismath/conversation/group_vote_counts.py 38 2 95%
polismath/conversation/manager.py 131 42 68%
polismath/database/init.py 1 0 100%
polismath/database/dynamodb.py 392 176 55%
polismath/database/postgres.py 414 95 77%
polismath/delphi_storage/init.py 1 0 100%
polismath/delphi_storage/codec.py 295 22 93%
polismath/delphi_storage/embedding_spool.py 58 6 90%
polismath/delphi_storage/golden_corpus.py 60 9 85%
polismath/delphi_storage/import_report.py 51 3 94%
polismath/delphi_storage/legacy_import.py 171 16 91%
polismath/delphi_storage/postgres.py 49 22 55%
polismath/delphi_storage/production_import.py 614 131 79%
polismath/delphi_storage/resource.py 179 32 82%
polismath/delphi_storage/scan_pacing.py 77 0 100%
polismath/delphi_storage/writer.py 196 13 93%
polismath/embedding_model.py 197 49 75%
polismath/empty_output.py 29 2 93%
polismath/engine_adapter.py 317 265 16%
polismath/job_child/init.py 364 51 86%
polismath/job_child/census.py 74 9 88%
polismath/job_child/input_bundle.py 106 7 93%
polismath/pca_kmeans_rep/init.py 5 0 100%
polismath/pca_kmeans_rep/clusters.py 257 38 85%
polismath/pca_kmeans_rep/corr.py 98 17 83%
polismath/pca_kmeans_rep/group_k_smoother.py 28 0 100%
polismath/pca_kmeans_rep/legacy_kmeans.py 197 7 96%
polismath/pca_kmeans_rep/pca.py 162 19 88%
polismath/pca_kmeans_rep/repness.py 226 5 98%
polismath/poller/init.py 4 0 100%
polismath/poller/admission.py 318 15 95%
polismath/poller/backfill.py 936 32 97%
polismath/poller/capacity.py 485 27 94%
polismath/poller/capacity_queue.py 248 13 95%
polismath/poller/coordinator_bridge.py 317 317 0%
polismath/poller/math_writer.py 120 3 98%
polismath/poller/promotion.py 112 4 96%
polismath/poller/readiness.py 368 13 96%
polismath/poller/rebuild_child.py 133 5 96%
polismath/poller/recompute_line.py 141 9 94%
polismath/poller/service.py 760 50 93%
polismath/poller/worker_pool.py 143 0 100%
polismath/queue/executor.py 221 111 50%
polismath/regression/init.py 4 0 100%
polismath/regression/clojure_comparer.py 188 20 89%
polismath/regression/comparer.py 891 640 28%
polismath/regression/datasets.py 126 27 79%
polismath/regression/recorder.py 36 27 25%
polismath/regression/utils.py 130 85 35%
polismath/replay/init.py 2 0 100%
polismath/replay/attribution_capture.py 49 0 100%
polismath/replay/axis_continuity.py 347 24 93%
polismath/replay/certify.py 999 59 94%
polismath/replay/crosslang.py 128 2 98%
polismath/replay/decision_ties.py 51 8 84%
polismath/replay/diagnostics.py 50 7 86%
polismath/replay/driver.py 73 1 99%
polismath/replay/dsn_admission.py 36 1 97%
polismath/replay/equiv_query.py 10 0 100%
polismath/replay/event_ingress.py 95 1 99%
polismath/replay/fixture_bundle.py 815 62 92%
polismath/replay/fixture_config.py 266 11 96%
polismath/replay/fixture_extract.py 285 12 96%
polismath/replay/fixture_generate.py 103 1 99%
polismath/replay/fixture_samples.py 157 14 91%
polismath/replay/fixture_selection.py 119 0 100%
polismath/replay/fixture_survey.py 147 11 93%
polismath/replay/legacy_pca.py 29 17 41%
polismath/replay/polarity.py 319 25 92%
polismath/replay/poller_equiv.py 776 99 87%
polismath/replay/prodclone.py 193 2 99%
polismath/replay/real_data.py 146 10 93%
polismath/replay/schedule.py 205 10 95%
polismath/replay/served_math.py 159 4 97%
polismath/replay/shard_bench.py 189 65 66%
polismath/replay/stagecompare.py 890 161 82%
polismath/replay/stages.py 256 40 84%
polismath/replay/stepcompare.py 86 1 99%
polismath/replay/store.py 120 11 91%
polismath/replay/tie_capture.py 107 19 82%
polismath/replay/types.py 58 6 90%
polismath/run_math_pipeline.py 284 93 67%
polismath/selection.py 48 0 100%
polismath/step_log.py 95 8 92%
polismath/tools/engine_rebuild.py 230 11 95%
polismath/types.py 6 0 100%
polismath/utils/cli_flags.py 15 0 100%
polismath/utils/clj_hash.py 44 0 100%
polismath/utils/env_flags.py 13 0 100%
polismath/utils/general.py 63 39 38%
polismath/utils/output_profile.py 66 2 97%
polismath/utils/serialization.py 10 5 50%
polismath/utils/vote_convention.py 159 5 97%
umap_narrative/700_datamapplot_for_layer.py 514 470 9%
umap_narrative/701_static_datamapplot_for_layer.py 310 310 0%
umap_narrative/702_consensus_divisive_datamapplot.py 435 275 37%
umap_narrative/801_narrative_report_batch.py 657 209 68%
umap_narrative/803_check_batch_status.py 268 148 45%
umap_narrative/llm_factory_constructor/init.py 2 0 100%
umap_narrative/llm_factory_constructor/model_provider.py 232 106 54%
umap_narrative/narrative_data.py 178 55 69%
umap_narrative/numerical_stages.py 97 17 82%
umap_narrative/polismath_commentgraph/init.py 1 0 100%
umap_narrative/polismath_commentgraph/cli.py 268 268 0%
umap_narrative/polismath_commentgraph/core/init.py 3 3 0%
umap_narrative/polismath_commentgraph/core/clustering.py 108 108 0%
umap_narrative/polismath_commentgraph/core/embedding.py 104 104 0%
umap_narrative/polismath_commentgraph/lambda_handler.py 219 219 0%
umap_narrative/polismath_commentgraph/schemas/init.py 2 0 100%
umap_narrative/polismath_commentgraph/schemas/dynamo_models.py 80 6 92%
umap_narrative/polismath_commentgraph/tests/conftest.py 17 17 0%
umap_narrative/polismath_commentgraph/tests/test_clustering.py 74 74 0%
umap_narrative/polismath_commentgraph/tests/test_embedding.py 55 55 0%
umap_narrative/polismath_commentgraph/tests/test_storage.py 87 87 0%
umap_narrative/polismath_commentgraph/utils/init.py 9 7 22%
umap_narrative/polismath_commentgraph/utils/converter.py 283 50 82%
umap_narrative/polismath_commentgraph/utils/group_data.py 332 279 16%
umap_narrative/polismath_commentgraph/utils/storage.py 616 486 21%
umap_narrative/reset_conversation.py 162 53 67%
umap_narrative/run_pipeline.py 459 158 66%
umap_narrative/topic_naming.py 148 11 93%
Total 26230 7392 72%

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