Recommended actions
No repository changes recommended.
This run gave the model no documentation, so it measured only what the base model already knew about the current TypeScript SpacetimeDB module API. Every shown failure traces to the model writing outdated or invented API shapes that differ from the golden answers. Nothing in the evidence shows a defect in the eval, skill, docs or API.
One diagnostic gap affects interpretation. Each shown publish_error contains only the first stderr line (Saving config to ...), so the compiler or publish message is not visible. The root causes below are inferred from the code differences, not from the error text. The evidence does not show whether the eval itself drops this output or the failure summary cuts it.
Failure patterns
Old-style reducer signature with a string name (3 tasks)
- Classification: Model limitation
- Confidence: High
- What the model wrote:
spacetimedb.reducer('delete_author', { authorId: t.u64() }, (ctx, { authorId }) => { ... })
spacetime.reducer('seed', {}, (ctx) => { ... })
The t_028 code also called ctx.db.post.delete(p).
- What was expected:
spacetimedb.reducer({ authorId: t.u64() }, (ctx, { authorId }) => { ... })
spacetimedb.reducer(ctx => { ... })
ctx.db.post.id.delete(p.id);
- What the error says:
publish_error: spacetime publish (typescript) failed (exit=2). Exit code 2 is consistent with a TypeScript compile failure.
- Why this happened: The model used an older or invented signature where the reducer name is passed as a string. In the current API, the reducer name comes from the exported binding. In t_028, the model also deleted by row rather than through the primary-key index.
- Suggested action: None
- Suggested area: None
- Affected tasks: t_028_cascade_delete, t_015_product_type_columns, t_062_semijoin_intersection
Invented index syntax and tables without names (4 tasks)
- Classification: Model limitation
- Confidence: High
- What the model wrote:
table({ public: true }, { ... }).index('byParent', ['parentId'])
table({ public: true }, { ... }).index('byUserDay', { algorithm: 'btree', columns: ['userId', 'day'] })
indexes: [{ name: 'byCategory', algorithm: 'btree', columns: ['categoryId'] }]
Tables were also defined inline inside schema({...}) with no name option.
- What was expected:
table({ name: 'child', public: true,
indexes: [{ accessor: 'byParent', algorithm: 'btree', columns: ['parentId'] }] }, { ... })
- What the error says:
publish_error ... (exit=2)
- Why this happened: The model either chained a
.index() method onto the table, which does not exist, or keyed index entries with name instead of accessor. It also left out the table name option.
- Suggested action: None
- Suggested area: None
- Affected tasks: t_052_autoinc_reference, t_021_multi_column_index, t_051_denormalized_index, t_018_constraints
Wrong ScheduleAt construction and import (3 tasks)
- Classification: Model limitation
- Confidence: High
- What the model wrote:
ScheduleAt.time(new Timestamp(ctx.timestamp.microsSinceUnixEpoch + 1000n))
import { schema, table, t, ScheduleAt, Timestamp } from 'spacetimedb/server';
scheduledAt: { tag: 'Interval', value: { micros: 50_000n } },
- What was expected:
import { ScheduleAt } from 'spacetimedb';
ScheduleAt.time(ctx.timestamp.microsSinceUnixEpoch + 1_000n)
scheduledAt: ScheduleAt.interval(50_000n),
- What the error says:
publish_error ... (exit=2)
- Why this happened: The model guessed the wrong form for scheduling values:
- It passed a
Timestamp object where the API takes a bigint of microseconds.
- It imported
ScheduleAt from the wrong module.
- It wrote the interval as a hand-built object literal instead of calling
ScheduleAt.interval.
- Suggested action: None
- Suggested area: None
- Affected tasks: t_069_scheduled_materialization, t_071_scheduled_private, t_017_scheduled_columns
Views not exported or misnamed (2 tasks)
- Classification: Model limitation
- Confidence: High
- What the model wrote:
spacetimedb.anonymousView({ name: 'activeAnnouncements', public: true }, ...)
spacetimedb.view({ name: 'my_profile', public: true }, ...)
- What was expected:
export const activeAnnouncements = spacetimedb.anonymousView({ name: 'active_announcements', public: true }, ...)
export const my_profile = spacetimedb.view({ name: 'my_profile', public: true }, ...)
- What the error says:
HTTP 400: no such table: 'active_announcements' and no such table: 'my_profile'
- Why this happened: In both tasks the view was not exported. t_023 used the correct name and still failed, which suggests that unexported views are never registered. In t_022, the view name was also camelCase instead of the required snake_case.
- Suggested action: None
- Suggested area: None
- Affected tasks: t_022_view_basic, t_023_view_per_user
Query-builder views written with index iterators or invented join methods (2 tasks)
- Classification: Model limitation
- Confidence: Medium
- What the model wrote:
ctx => ctx.db.ticket.status.filter('open')
ctx.from.member.semiJoin(ctx.from.eligibility, (m, e) => m.id.eq(e.memberId))
- What was expected:
ctx => ctx.from.ticket.where(ticket => ticket.status.eq('open'))
ctx.from.eligibility.rightSemijoin(ctx.from.member, (eligibility, member) => eligibility.memberId.eq(member.id))
- What the error says:
publish_error ... (exit=2)
- Why this happened: In t_066, the model returned an index iterator where the view expected an array or query, and it omitted the view and table names. In t_062, it invented a
semiJoin method instead of using rightSemijoin, and it also used the string-named reducer signature from the first pattern.
- Suggested action: None
- Suggested area: None
- Affected tasks: t_066_query_builder_view, t_062_semijoin_intersection (also listed in the first pattern)
Insert missing autoInc primary-key fields (1 task)
- Classification: Model limitation
- Confidence: High
- What the model wrote:
ctx.db.user.insert({ name: 'Alice' });
ctx.db.membership.insert({ userId: 1n, groupId: 1n });
- What was expected:
ctx.db.user.insert({ userId: 0n, name: 'Alice' });
ctx.db.membership.insert({ id: 0n, userId: 1n, groupId: 1n });
- What the error says:
publish_error ... (exit=2)
- Why this happened: The model assumed that autoInc columns can be left out of an insert. The API requires a placeholder value of
0n for these columns.
- Suggested action: None
- Suggested area: None
- Affected tasks: t_019_many_to_many
Exported type definitions in the module (1 task)
- Classification: Model limitation
- Confidence: Low
- What the model wrote:
export const Rect = t.object('Rect', { ... });
export const Shape = t.enum('Shape', { ... });
- What was expected:
const Rect = t.object('Rect', { ... });
const Shape = t.enum('Shape', { ... });
- What the error says:
publish_error ... (exit=1). The different exit code points to a failure after compilation rather than a compile error.
- Why this happened: The likely cause is that the module exported values that are neither reducers nor views, which publish rejects. The rest of the code matches the golden answer. The stderr is truncated, so this cause cannot be confirmed.
- Suggested action: None
- Suggested area: None
- Affected tasks: t_013_spacetime_sum_type
The 25 additional failures were not shown and are not analyzed here.