The dataset viewer is not available for this split.
Error code: StreamingRowsError
Exception: CastError
Message: Couldn't cast
files: list<item: null>
child 0, item: null
references: list<item: struct<path: string>>
child 0, item: struct<path: string>
child 0, path: string
type: string
devDependencies: struct<@types/node: string, @types/react: string, @types/react-dom: string, @wasp.sh/spec: string, @ (... 82 chars omitted)
child 0, @types/node: string
child 1, @types/react: string
child 2, @types/react-dom: string
child 3, @wasp.sh/spec: string
child 4, @wasp.sh/wasp-app-runner: string
child 5, prisma: string
child 6, typescript: string
child 7, vite: string
dependencies: struct<react: string, react-dom: string, react-router: string>
child 0, react: string
child 1, react-dom: string
child 2, react-router: string
name: string
workspaces: list<item: string>
child 0, item: string
to
{'name': Value('string'), 'type': Value('string'), 'workspaces': List(Value('string')), 'dependencies': {'react': Value('string'), 'react-dom': Value('string'), 'react-router': Value('string')}, 'devDependencies': {'@types/node': Value('string'), '@types/react': Value('string'), '@types/react-dom': Value('string'), '@wasp.sh/spec': Value('string'), '@wasp.sh/wasp-app-runner': Value('string'), 'prisma': Value('string'), 'typescript': Value('string'), 'vite': Value('string')}}
because column names don't match
Traceback: Traceback (most recent call last):
File "/src/services/worker/src/worker/utils.py", line 147, in get_rows_or_raise
return get_rows(
dataset=dataset,
...<4 lines>...
column_names=column_names,
)
File "/src/libs/libcommon/src/libcommon/utils.py", line 272, in decorator
return func(*args, **kwargs)
File "/src/services/worker/src/worker/utils.py", line 127, in get_rows
rows_plus_one = list(itertools.islice(safe_iter(ds, dataset=dataset), rows_max_number + 1))
File "/src/services/worker/src/worker/utils.py", line 483, in safe_iter
yield from ds.decode(False) if ds.features else ds
File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 2840, in __iter__
for key, example in ex_iterable:
^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 2373, in __iter__
for key, pa_table in self._iter_arrow():
~~~~~~~~~~~~~~~~^^
File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 2398, in _iter_arrow
for key, pa_table in self.ex_iterable._iter_arrow():
~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 536, in _iter_arrow
for key, pa_table in iterator:
^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 419, in _iter_arrow
for key, pa_table in self.generate_tables_fn(**gen_kwags):
~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/json/json.py", line 343, in _generate_tables
self._cast_table(pa_table, json_field_paths=json_field_paths),
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/json/json.py", line 132, in _cast_table
pa_table = table_cast(pa_table, self.info.features.arrow_schema)
File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2378, in table_cast
return cast_table_to_schema(table, schema)
File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2306, in cast_table_to_schema
raise CastError(
...<3 lines>...
)
datasets.table.CastError: Couldn't cast
files: list<item: null>
child 0, item: null
references: list<item: struct<path: string>>
child 0, item: struct<path: string>
child 0, path: string
type: string
devDependencies: struct<@types/node: string, @types/react: string, @types/react-dom: string, @wasp.sh/spec: string, @ (... 82 chars omitted)
child 0, @types/node: string
child 1, @types/react: string
child 2, @types/react-dom: string
child 3, @wasp.sh/spec: string
child 4, @wasp.sh/wasp-app-runner: string
child 5, prisma: string
child 6, typescript: string
child 7, vite: string
dependencies: struct<react: string, react-dom: string, react-router: string>
child 0, react: string
child 1, react-dom: string
child 2, react-router: string
name: string
workspaces: list<item: string>
child 0, item: string
to
{'name': Value('string'), 'type': Value('string'), 'workspaces': List(Value('string')), 'dependencies': {'react': Value('string'), 'react-dom': Value('string'), 'react-router': Value('string')}, 'devDependencies': {'@types/node': Value('string'), '@types/react': Value('string'), '@types/react-dom': Value('string'), '@wasp.sh/spec': Value('string'), '@wasp.sh/wasp-app-runner': Value('string'), 'prisma': Value('string'), 'typescript': Value('string'), 'vite': Value('string')}}
because column names don't matchNeed help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.
YAML Metadata Warning:empty or missing yaml metadata in repo card
Check out the documentation for more information.
SpecForge — full-stack Wasp app
The tech-spec writing tool from the SpecForge conversation, rebuilt on Wasp as a real full-stack app: specs persisted in a database, per-section editing with autosave, the 12 harness-ready sections with done-detection, and full Markdown export. Structure follows wasp-lang/wasp@main examples/tutorials/TodoApp (Wasp TS Spec era, pinned 0.26.0).
Stack
- Wasp 0.26 TS Spec (
main.wasp.ts) — routes, auth, 6 operations declared - Prisma + SQLite in dev (schema.prisma at root); switch to
postgresqlfor production - React 19 client; username/password auth via
wasp/client/auth - Server operations:
getSpecs,getSpec(queries) ·createSpec,updateSection,resetSection,deleteSpec(actions) — all ownership-checked againstcontext.user
Run locally
Prereqs: Node.js ≥ 24.14.1, npm.
npm install -g @wasp.sh/wasp-cli@latest
git clone <this repo> specforge-wasp && cd specforge-wasp
wasp install # generates .wasp/ + the @wasp.sh/spec package (first run only)
wasp db migrate-dev # creates migrations/ + dev SQLite db
wasp start # → http://localhost:3000
Sign up, create a spec — it seeds all 12 sections server-side; edits autosave to the DB; the chip turns READY FOR HARNESS when all sections pass the done-check. wasp compile typechecks fast.
Deploy (Fly.io)
Prereqs: flyctl installed, fly auth signup/login, and a Postgres-capable app (SQLite is dev-only).
- In
schema.prisma, changeprovider = "sqlite"→provider = "postgresql". - Then, from the app root:
wasp deploy fly launch specforge-app dfw # region example: dfw / iad / lhr
This creates specforge-app-{client,server,db}, sets DATABASE_URL, JWT_SECRET, WASP_WEB_CLIENT_URL, WASP_SERVER_URL, and runs migrations. Commit the generated fly-server.toml / fly-client.toml. To redeploy after changes: wasp deploy fly deploy. Client env vars must be passed as shell env on every deploy. Health check endpoint is GET /up (Wasp ≥ 0.26).
Railway works too: wasp deploy railway launch.
Repo layout
main.wasp.ts # Wasp TS Spec: routes, auth, operations
schema.prisma # User, Spec, Section (cascade delete)
src/
sections.js # the 12 sections: hints, starters, shared done-check
queries.js # getSpecs / getSpec (ownership-scoped)
actions.js # createSpec (seeds 12 sections) / updateSection / resetSection / deleteSpec
SpecsPage.jsx # list + create + progress chips + delete
SpecPage.jsx # editor: 12-section sidenav, autosave, preview, Copy Markdown
LoginPage.jsx / SignupPage.jsx
styles.css
Notes & caveats
migrations/are generated bywasp db migrate-devlocally; they are not committed here yet (fresh clone generates its own).- Verified statically against the upstream TodoApp example (spec syntax, imports, config files) as of Wasp
0.26.0; no compile run was executed for this scaffold — runwasp install && wasp compilefirst after cloning and fix any drift if the CLI reports version drift. - The 12 sections, hints, starters and done-check are the same harness-ready scaffold from the SPECWORKS methodology — a spec completed here exports as the input table for an agent build harness.
- Downloads last month
- 60