IRC channel logs

2026-02-16.log

back to list of logs

<pukkamustard>hello spritely!
<identity>hello pukkamustard
<pukkamustard>i'm wondering if (spawn-fiber) is ok to use from a vat?
<pukkamustard>im trying to use existing fibers code from spritely
<pukkamustard>it seems to work, but wonder if this is recommended or will break when running in hoot or other environments?
<identity>pukkamustard: hoot uses fibers anyway?
<identity>so it should work
<identity>but it might be a good idea to goblins-ify the fibers code, depending on a number of factors
<identity>or a number of actors…
<pukkamustard>hehe, yeah. maybe also good exercise to get into goblins.
<jfred>pukkamustard: You might need to use `syscaller-free-fiber` - there's an example of that in the recent blog post on Mandy: https://spritely.institute/news/mandy-activitypub-on-goblins.html
<jfred>along with a bit of explanation of when/why you might use it
<pukkamustard>jfred: thanks!
<jfred>no problem :)
<dthompson>hey pukkamustard
<dthompson>jfred is right that you should use syscaller-free-fiber
<dthompson>it will ensure that the dynamic state within the vat fiber is not carried into the new fiber
<dthompson>the thing you want to be careful with when using fibers with goblins is NEVER BLOCK THE VAT FIBER
<dthompson>do not call get-message, put-message, or perform any fibers operation from within the vat
<dthompson>don't read from a nonblocking port, etc.
<dthompson>the reward is that once you've successfully wrapped a fibers-based operation in an actor, you can use it safely in lots of places