Wes McNamee

I'm apparently not on the absolute latest. Currently running this commit: ``` commit be20375d30c2c5d715dd09c11b3046b835b0366d (HEAD -> main, origin/main, origin/HEAD) Author: Extraltodeus Date: Wed May 15 01:56:07 2024 +0200 Update README.md...

Ah, I see. You just did a bit of digging then to figure out how to modify a backend node with more frontend code?

:+1:

after finding this: https://www.reddit.com/r/assholedesign/comments/1566g5a/afdian_a_chinese_website_doesnt_allow_users_to/ including the disclaimer at the top, that they can "terminate the cancellation without my consent". This sounds like a huge scam. It also sounds like it...

if you have any other mechanism, let me know. E.g. direct through PayPal.

thanks! I'll try that out.

I'll try not running the server from VSCode and see if that helps. Right now I don't have another machine. That may come later.

I noticed this `queue.when_empty(callback)` I suppose I'd need to write a function that wrapped `queue.cancel_all()` to also remove this callback?

``` --------------------------------------------------------------------------- RuntimeError Traceback (most recent call last) Cell In[16], [line 65](vscode-notebook-cell:?execution_count=16&line=65) [62](vscode-notebook-cell:?execution_count=16&line=62) seed = 64712465704704 [63](vscode-notebook-cell:?execution_count=16&line=63) ctx = Context ---> [65](vscode-notebook-cell:?execution_count=16&line=65) with Workflow(): [66](vscode-notebook-cell:?execution_count=16&line=66) ctx.seed = seed [67](vscode-notebook-cell:?execution_count=16&line=67) ctx.cfg...

ok, so the issue I found, is that if the callback function definition was wrong (didn't accept a single parameter, the workflow), first it would error when trying to call...