You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When deleting a task, the cron files associated with imapsync are not automatically removed. Additionally, the current cron UI is not ideal, offering limited settings for scheduling synchronization times. A more flexible approach, such as implementing a slider or input box, would allow system administrators to configure synchronization times more easily.
Furthermore, we discovered that some users have modified the default synchronization settings in getmail, using values not originally available in its UI. Although these custom settings are successfully migrated to ns8-imapsync, the list-tasks feature fails to display the available tasks due to a strict JSON validator. As a result, while the tasks are still functional, the ns8-imapsync UI appears broken.
Steps to reproduce
After installing ns8-imapsync with the mail and account provider:
Create a task.
Set up a cron job.
Everything works as expected.
Delete the task.
Expected behavior
I expect the task, along with all associated files required for its creation, to be fully removed.
Actual behavior
When a task is deleted, the task files are successfully removed, but the associated cron files remain. These cron files can still be found using the command:
find /home/imapsync1 -iname *idOfTheTask.cron.
Additionally, the current UI for configuring cron settings is not user-friendly. The limited options make it difficult to customize sync times effectively. Introducing a slider or more intuitive input could significantly improve the user experience for configuring these settings.
configure mail and create some tasks with cron enabled
save somewhere the different settings you did on the cron to verify after the upgrade it will be the same
upgrade to ghcr.io/nethserver/imapsync:1.0.4-dev.1 api-cli run update-module --data '{"module_url":"ghcr.io/nethserver/imapsync:1.0.4-dev.1","instances":["imapsync1"],"force":true}'
once upgraded, verify you can open the task and the cron settings are relevant with the settings you had before the upgrade
verify you can save again the same task
verify you can create another task with cron enabled
test 2
on the same module of test 1
note the ID of the task for example here : 7r0wtx
delete the task
verify the files with the ID does not exist anymore : find / -iname *7r0wtx*
When deleting a task, the cron files associated with imapsync are not automatically removed. Additionally, the current cron UI is not ideal, offering limited settings for scheduling synchronization times. A more flexible approach, such as implementing a slider or input box, would allow system administrators to configure synchronization times more easily.
Furthermore, we discovered that some users have modified the default synchronization settings in getmail, using values not originally available in its UI. Although these custom settings are successfully migrated to ns8-imapsync, the list-tasks feature fails to display the available tasks due to a strict JSON validator. As a result, while the tasks are still functional, the ns8-imapsync UI appears broken.
Steps to reproduce
After installing ns8-imapsync with the mail and account provider:
Expected behavior
I expect the task, along with all associated files required for its creation, to be fully removed.
Actual behavior
When a task is deleted, the task files are successfully removed, but the associated cron files remain. These cron files can still be found using the command:
find /home/imapsync1 -iname *idOfTheTask.cron.
Additionally, the current UI for configuring cron settings is not user-friendly. The limited options make it difficult to customize sync times effectively. Introducing a slider or more intuitive input could significantly improve the user experience for configuring these settings.
Components
ns8-imapsync 1.0.3
See also
https://community.nethserver.org/t/in-imapsync-it-fails-to-show-me-tasks/24572/8
thank Nick Sardelianos
The text was updated successfully, but these errors were encountered: