Skip to content

Conversation

gefjon
Copy link
Contributor

@gefjon gefjon commented Oct 9, 2025

Description of Changes

API and ABI breaking changes

Expected complexity level and risk

Testing

gefjon and others added 30 commits July 23, 2025 17:19
Discussion in other forums has yielded a better design,
where procedure code can programmatically register `on_abort` handlers at runtime.
I even called some myself to try it!
No implementation; linking will fail.
At this stage, changes are not integrated, so build is broken.
But these are never supposed to block, so use a custom "executor" which only calls `poll` once.
This reverts commit b26d447.

These changes are now in a separate branch, `phoebe/skippable-tests`.
Co-authored-by: Mazdak Farrokhzad <twingoow@gmail.com>
Co-authored-by: joshua-spacetime <josh@clockworklabs.io>
Signed-off-by: Phoebe Goldman <phoebe@goldman-tribe.org>
So that we can determine whether we should be running this on the database core or not
And fix typo that mis-categorized `Module::Js` as `ModuleType::Wasm`.
It's not used in private either, and no one knew what it was for, so I'm cutting it.
and resolve just a whole boatload of merge conflicts
I successfully called this:

```bash
[phoebe@phoebe-desktop:~/clockworklabs/SpacetimeDB/modules/module-test]$ curl -H "Content-Type:application/json" -X POST -d '[]' http://localhost:3000/v1/database/module-test/procedure/this_procedure_sleeps
"Started at 2025-10-02T14:46:22.288936+00:00, requested to sleep until 2025-10-02T14:46:23.288936+00:00, woke at 2025-10-02T14:46:23.290299+00:00"
```
Prior to this commit, when shutting down SpacetimeDB-standalone via C-c / SIGINT,
the process would print a panic message and backtrace (if enabled)
due to dropping nested Tokio runtimes.
This commit avoids doing so in SpacetimeDB-standalone,
and adds a note to `JobCores` instructing how to avoid it in other uses.
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