thank you & welcome back! 🫡
does the following mean strfry will be continuing to relay when there is an import (in the past it was stopping to relay):
- Switch import to use WriterPipeline
I just tagged 2 strfry releases: 0.9.7 and 1.0.0-beta1
1.0.0-beta1 is a candidate release of strfry 1.0.0 -- help is needed testing!
The internal strfry DB version has been increased to 3, which means that you will need to rebuild your DBs to use this new version.
0.9.7 has some bugfixes and changes that accumulated in master, and has a "strfry export --fried" feature that can be used to create DB exports that can be rapidly imported by 1.0.0 series releases.
The full changelogs are available here: https://github.com/hoytech/strfry/blob/1f34794945cf380035822278c46070a9923129f3/CHANGES
Thank you to everyone who contributed and helps testing! If you need help or run into any issues, reply on nostr or stop by our telegram channel.
thank you & welcome back! 🫡
does the following mean strfry will be continuing to relay when there is an import (in the past it was stopping to relay):
- Switch import to use WriterPipeline
Thanks!
This change shouldn't make much difference in import's behaviour. Because import pretty much constantly has a writer lock, relay *write* operations will be blocked/delayed (and may timeout), but *read* operations should continue as normal.
We could make import release its lock for a few milliseconds periodically so that write operations can go through. I'll look into doing that.