Closed sci-42ver closed 6 months ago
This is one weird problem. Temporarily for one workaround in Fcitx5 (maybe not for others like hamster where it doesn't say 'LOCK: already held by process' but still says "Error opening db '...' read-only."), I switch to one fake schema which doesn't use any translator, therefore no LOCKs are held. Then re-deploy. Now sync doesn't throw one error.
It is due to the Memory(...)
in lua
which preempts the LOCK which occurs also in hamster
. Probably weasel solves with this inherently.
In weasel 0.15.0, currently it doesn't have the above error when sync although it used to. I checked by Resource Monitor that the LOCK is held by
WeaselServer.exe
.In archlinux,
melt_eng
is the primary translator of the current used schema which also uses theeasy_en
dict. I use the same yaml cfgs in Fcitx5 as weasel.