-
-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Todoist sync creating multiple of the same todos with every sync #312
Comments
Will it be reproduced every time? I guess it might be that the first button was clicked, and the network request had not been successful yet when the second button was clicked, resulting in the same task being requested twice. |
Well probably but a considerable time passes with no notification so as a result its clicked again. So yes it will be reproduced every time |
🎉 This issue has been resolved in version 3.10.5 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Version 3.10.5 added prompts during synchronization, welcome to test. |
Updated now and will revert with feedback in the coming days. Thanks for this |
Search first
What Happened?
When I click on the sync button on the logseq ba
![Screenshot 2024-05-08 105533](https://private-user-images.githubusercontent.com/86377241/328844348-89608804-e6b8-4585-ac19-b7be76905ad3.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjE0OTgzMDAsIm5iZiI6MTcyMTQ5ODAwMCwicGF0aCI6Ii84NjM3NzI0MS8zMjg4NDQzNDgtODk2MDg4MDQtZTZiOC00NTg1LWFjMTktYjdiZTc2OTA1YWQzLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MjAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzIwVDE3NTMyMFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWQ3MDRlNTczZmZhOWY5Mzg4OWE2MDQ3OTQyNzAyMGJiZDc2NTk4ODZjMjUyY2QxMDU2ZTA3ZGRjMzJiNjFiNjcmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.uZQb7LRWks-eycG4v_w3Hml6ykpiVmjM9VGRSLnxGXA)
r it brings in the todos taht are already in logseq.
Reproduce the Bug
Screenshots
No response
Environment Information
logseq 0.10.9 Windows 11
Additional Context
No response
Are you willing to submit a PR? If you know how to fix the bug.
The text was updated successfully, but these errors were encountered: