Closed yoyurec closed 1 year ago
Seems this is a Logseq Core issue. Many plugins throw this kind of errors.
@vipzhicheng, the same error for me. It disappears, with plugin disabling → I guess it relates to some setTimeout handlers
Thanks to all of u. I have fixed this issue. Please update.