Recommended actions
No repository changes recommended.
The model received no documentation, so these failures measure what it already knows about the SpacetimeDB TypeScript module API. The visible failures all use API shapes that do not compile against the expected API. Most of them look like older or invented forms. None of the evidence points to a defect in the evals, skills, docs, or API. Only one captured error (t_081) shows a compiler diagnostic. The other scorer outputs stop after the Saving config to ... line. Several root causes below are therefore inferred from comparing the generated code with the golden answers. This analysis covers the 15 failures shown; the other 74 were not supplied.
Failure patterns
Positional schema(...) arguments instead of an object map (10 tasks)
- Classification: Model limitation
- Confidence: High
- What the model wrote:
const spacetimedb = schema(player);
export default schema(user_profile, connection_presence);
const spacetimedb = schema(order, category_stats);
Many of these tasks also contain secondary errors:
- Index definitions use
name: instead of accessor:: { name: 'byUser', algorithm: 'btree', columns: [...] }.
- t_050 passes a third callback argument to
table(...) to define indexes.
- Reducers are registered by string name:
spacetimedb.reducer('compute_stats', {...}, ...).
- Empty argument objects are passed to reducers:
reducer('seed', {}, ...).
- t_025 uses
t.string().optional().
- t_025 and t_024 omit
export default spacetimedb.
- t_069 uses
scheduled: 'refreshMaterialized' as a string and imports ScheduleAt and Timestamp from spacetimedb/server.
- What was expected:
const spacetimedb = schema({ player });
export default spacetimedb;
indexes: [{ accessor: 'byUser', algorithm: 'btree', columns: ['userIdentity'] }]
nickname: t.option(t.string())
scheduled: (): any => refreshMaterialized
export const seed = spacetimedb.reducer(ctx => { ... });
- What the error says:
publish_error: spacetime publish (typescript) failed (exit=2). The captured stderr stops at the config line, so no specific diagnostic is visible.
- Why this happened: Without documentation, the model fell back on a variadic
schema() signature and other API shapes that the current TypeScript server API does not accept. t_054 is the clearest case: its only deviation from the golden answer is schema(special_value) versus schema({ specialValue }).
- Suggested action: None
- Suggested area: None
- Affected tasks: t_025_optional_fields, t_024_event_table, t_029_filter_and_aggregate, t_031_unique_constraint, t_048_heartbeat_isolation, t_054_special_types, t_047_normalized_collection, t_050_normalized_schema, t_021_multi_column_index, t_069_scheduled_materialization
String-named reducer registration (2 tasks)
- Classification: Model limitation
- Confidence: High
- What the model wrote:
export const dual_write = spacetimedb.reducer(
'dual_write',
{ id: t.u64(), value: t.string() },
(ctx, { id, value }) => { ... }
);
spacetimedb.reducer('delete_author', { authorId: t.u64() }, (ctx, { authorId }) => { ... });
t_028 also omits export default spacetimedb and does not export the reducer.
- What was expected:
export const dual_write = spacetimedb.reducer(
{ id: t.u64(), value: t.string() },
(ctx, { id, value }) => { ... }
);
- What the error says:
src/index.ts(27,3): error TS2559: Type '"dual_write"' has no properties ...
- Why this happened: The model passed the reducer name as the first argument. The current API instead takes the name from the exported binding, and the first argument must be the parameter object or the handler.
- Suggested action: None
- Suggested area: None
- Affected tasks: t_081_incremental_migration, t_028_cascade_delete
Wrong import path and missing default export (1 task)
- Classification: Model limitation
- Confidence: Medium
- What the model wrote:
import { schema, table, t } from 'spacetimedb';
const spacetimedb = schema({ customer: table(...), ... });
// no export default
- What was expected:
import { schema, table, t } from 'spacetimedb/server';
export default spacetimedb;
- What the error says:
publish_error: spacetime publish (typescript) failed (exit=2). The output is truncated with no diagnostic.
- Why this happened: The model imported the server-side builders from the client package root and never exported the schema.
- Suggested action: None
- Suggested area: None
- Affected tasks: t_030_two_table_join
Invented type-builder and table-definition shapes (2 tasks)
- Classification: Model limitation
- Confidence: Medium
- What the model wrote:
- In t_049, the
table(...) arguments are swapped, so the columns come first and the options second.
- In t_049, the byte array is written as a chained method:
data: t.u8().array().
- In t_013, the table is defined with
table({ public: true }, ...), which has no name option.
- In t_013, the enum value is built with
Shape.circle(radius).
- In t_013, the reducer is registered by string name:
reducer("setCircle", ...).
- What was expected:
table({ name: 'blob_record', public: true, indexes: [{ accessor: 'byOwner', ... }] }, { ... })
data: t.array(t.u8())
ctx.db.result.insert({ id, value: { tag: 'circle', value: radius } });
- What the error says:
publish_error: spacetime publish (typescript) failed (exit=2). The output is truncated with no diagnostic.
- Why this happened: The model guessed at builder chaining, argument order, and sum-type constructors that the actual API does not have.
- Suggested action: None
- Suggested area: None
- Affected tasks: t_049_binary_storage, t_013_spacetime_sum_type