andelf
commented
8 months ago Could you check the recent nightly release? I've added a simple fix. https://github.com/logseq/logseq/releases/tag/nightly
Closed stucash closed 1 week ago
andelf
commented
8 months ago Could you check the recent nightly release? I've added a simple fix. https://github.com/logseq/logseq/releases/tag/nightly
stucash
commented
8 months ago @andelf Thanks for the swift response; I tried the alpha+nightly 0.10.7 AppImage; unforunately it didn't fix the issue on my end.
I reproduced it with exactly the same steps detailed earlier, but with the nightly version.
Looks like this time a different error manifested; the S3 token is expired.
Here's the new error log from dev console:
[01b1f34f-8489-4276-9d78-95b5af6a68db] setting sync age-encryption passphrase...
instrument.js:191 [SyncManager] need-password -> idle :reason nil :local-txid 252 :args nil :now 2024-03-06T14:20:38.530Z
instrument.js:191 [SyncManager] idle -> remote->local-full-sync :reason nil :local-txid 252 :args nil :now 2024-03-06T14:20:38.531Z
instrument.js:191 :frontend.fs.sync/diff-file-metadata-sets-elapsed-time 7.399999998509884 ms
instrument.js:191 [full-sync(remote->local)] 1 files need to sync
instrument.js:191 update-local-files 01b1f34f-8489-4276-9d78-95b5af6a68db /home/demo/Live-usb-storage/PKM/Logseq (pages/读书___笔记___马拉松训练指南.md)
instrument.js:191 [SyncManager] remote->local-full-sync -> idle :reason nil :local-txid 252 :args nil :now 2024-03-06T14:20:39.568Z
instrument.js:191 [SyncManager] idle -> local->remote-full-sync :reason nil :local-txid 252 :args nil :now 2024-03-06T14:20:39.569Z
instrument.js:191 [full-sync(local->remote)] 26 files need to sync and 0 local files need to delete
instrument.js:191 :sync-local->remote change [pages/读书___疑问___马拉松训练指南.md assets/strength_stage_three_beginner.jpeg assets/拉伸动作2.jpeg assets/训练量表格3.jpeg assets/training_cycle_two.jpeg assets/拉伸动作1.jpeg assets/training_cycle_three.jpeg assets/strength_stage_three_advanced.jpeg assets/拉伸动作5.jpeg assets/strength_stage_one_advanced.jpeg journals/2024_03_04.md assets/训练量表格2.jpeg assets/单边动作1.jpeg assets/strength_stage_two_2.jpeg assets/training_cycle_one.jpeg assets/strength_stage_two_1.jpeg assets/训练量表格1.jpeg assets/training_cycle_four.jpeg assets/strength_stage_two_intensity.jpeg assets/Electric-Blues-DanielsTables-3-01-02.xlsm]
instrument.js:191 Parsing start: pages/读书___笔记___马拉松训练指南.md
instrument.js:191 Parsing finished: pages/读书___笔记___马拉松训练指南.md
instrument.js:191 rsapi error: Error: Error invoking remote method 'main': Error: ExpiredToken: s3 token expired
instrument.js:191 sync-local->remote unknown: #error {:message Promise error, :data {:error :promise-error}, :cause #object[Error Error: Error invoking remote method 'main': Error: ExpiredToken: s3 token expired]}
instrument.js:191 [SyncManager] local->remote-full-sync -> idle :reason nil :local-txid 252 :args nil :now 2024-03-06T14:20:42.218Z
instrument.js:191 TypeError: Cannot read properties of undefined (reading 'data')
at sentry.cljs:45:40
at sentry.cljs:45:26
at request.js:1:1
at Array.<anonymous> (promisebuffer.js:47:14)
at promisebuffer.js:33:17
at Array.forEach (<anonymous>)
at y._executeHandlers (promisebuffer.js:93:9)
at promisebuffer.js:52:16
at new y (promisebuffer.js:35:20)
at y.then (promisebuffer.js:40:20)
at A._processEvent (baseclient.js:1:63)
at A._captureEvent (baseclient.js:461:62)
at baseclient.js:137:26
at Array.<anonymous> (promisebuffer.js:47:14)
at promisebuffer.js:33:17
at Array.forEach (<anonymous>)
at y._executeHandlers (promisebuffer.js:93:9)
at promisebuffer.js:52:16
at new y (promisebuffer.js:35:20)
at y.then (promisebuffer.js:40:20)
at A.captureException (baseclient.js:132:16)
at g._invokeClient (hub.js:467:78)
at g.captureException (hub.js:204:29)
at w (index.js:169:1)
at Q.captureException (index.js:1:63)
at events.cljs:456:1
at $APP.$JSCompiler_prototypeAlias$$.$cljs$core$IFn$_invoke$arity$1$ (core.cljs:11345:18)
at $switch__29499__auto__$jscomp$187$$ (events.cljs:973:5)
at Function.$frontend$handler$events$run_BANG__$_state_machine__29500__auto____1$$ [as $cljs$core$IFn$_invoke$arity$1$] (events.cljs:973:5)
at $cljs$core$async$impl$ioc_helpers$run_state_machine_wrapped$$ (ioc_helpers.cljs:46:3)
at ioc_helpers.cljs:53:3
at channels.cljs:65:72
at $cljs$core$async$impl$dispatch$process_messages$$ (dispatch.cljs:29:23)
at $channel$jscomp$1$$.port1.onmessage (nexttick.js:190:5)
atYuguo
commented
7 months ago I have the same problem, looking forward to a solution, thanks.
github-actions[bot]
commented
1 month ago Hi There! 👋
We haven't seen any activity on this issue in a while :sleeping:, and we just wanted to make sure that it's still relevant. If you're still experiencing this issue, you might find it helpful to update to the latest version of Logseq. The latest version includes bug fixes and new features that may help to resolve this issue, and you can download it from our website. If updating to the latest version doesn't help, please let us know by adding a comment 💬. We're here to help!
If the issue has been resolved or is no longer relevant, that's great news! 🎉 We'll go ahead and close this issue to keep our backlog organized. Please note that this issue will be closed automatically in 20 days if there is no further activity. If you need more time to resolve the issue or provide more information, please just let us know by adding a comment.
Access additional Logseq 🚀 resources:
Thanks for your contributions to Logseq! If you have any other issues or feature requests, please don't hesitate to let us know. We always welcome pull requests too!
Search first
What Happened?
Yesterday after I’ve updated some of my notes I found the syncing stopped working abruptly (part of my update went through), the icon was kept in orange status and when drilled into details I could see that my files kept being processed. If I delete this file, then Logseq would pick another file, which was kept in processing status.
Reproduce the Bug
Log off Log on Turn on Sync and smart syncing Click on Sync icon and type in password Syncing starts.
Expected Behavior
I expected the syncing to finish soon as it was just a small batch of files.
Screenshots
No response
Desktop or Mobile Platform Information
Additional Context
Error Log from dev console:
Are you willing to submit a PR? If you know how to fix the bug.