In imapsync, it fails to show me "Tasks"!

Bug
, ,
1

Well the subject says it all.
Going to imapsync and clicking “Tasks” fails.
Settings and Status work ok and the actual tasks seem to run as I DO get email.

The error is this:

Task module/imapsync1/list-tasks failed
Subtask module/mail1/list-user-mailboxes completed

module/imapsync1/list-tasks
Task ID: 
ef6d92c5-0fcb-44e2-958d-57338d05c06f
Validation errors: [user_properties.0.cron: user_properties.0.cron must be one of the following: "", "5m", "10m", "15m", "30m", "45m", "1h" user_properties.2.cron: user_properties.2.cron must be one of the following: "", "5m", "10m", "15m", "30m", "45m", "1h"]

module/mail1/list-user-mailboxes
Task ID: 
2df10c1e-e387-4903-bdb2-43674447798c

…I suspect this comes from my original NS7 install where I had manually set “3m” or “1m” (I don’t remember) to check the external mailboxes, not one of the values it expects here.
It should allow me to set whatever number I want, but in any case NOT fail if it is not set in one of the values it expects!

(btw whether I have “3m” or “1m” it DOES work both in NS7 and NS8 and DOES follow my setting - so…)

1 Like
2

let me have a look :stuck_out_tongue:

1 Like
3

image
image600×631 32.1 KB

I went back to NS7, and I do not understand, it was just a one run, we do not have implemented cron for NS7
:-?

4

but we migrated properties from getmail to imasync, let me check

5

hum let me try to investigate

  • you set getmail with a custom Time to a user, lets say 3 minutes but our UI set static interval 5,10,15,30,60 minutes

  • you migrated the mail and the connectors has been migrated to ns8-imasync

  • the migration should be fine because you can do fetch the imap account with the correct time cron interval

  • however when you open the ns8-imapsync UI you have an error because the get-configuration block you (from your error string)

does it sound correct @NLS ?

two ways to fix it

  • manually find the cron of the guilty user and adjust to what we expect '',5,10,15,30,45,60 ('' to remove the cron)

find /home -iname *.cron

  • we could remove the strict validation of get-configuration and just validate a string, when you will save the form again, you will hit the validation of what we expect

as a side effect we could introduce 1 and 3 minutes cron intervals it has been asked, even better we could add a slider with the value you want

cc @davidep

2 Likes
6

Yes this sounds exactly right.
I would very much prefer if you could allow a slider or a value set by user (they should know what they are doing).
I set it to 3 (or 1) minutes because it was too slow for me to get new mail every 5 minutes.
I think that was the default in NS7 without ability to change it from GUI?
I know my (upstream) server wouldn’t bother getting more sync requests so I set it 1-2 years ago and it worked fine.
So please don’t make me edit it back.
(after all it works, it just doesn’t know how to display it)

1 Like
7

yeah, this is the issue, I think I would like to play with the slider, from 1 to 60

even that if the input box is really simple

8

Capture d’écran du 2024-09-24 22-50-18
Capture d’écran du 2024-09-24 22-50-18888×1036 41.6 KB

Capture d’écran du 2024-09-24 22-49-52
Capture d’écran du 2024-09-24 22-49-52888×989 40.7 KB

1 Like
9
1 Like
10

hello Nick

could please test something for me

upgrade to the testing version you should be able to open and save again your forms

verify once you delete a task that all the relevant sync files are removed

you have two tests to do on this

11

OK reverting
where are the sync files?

12

in the table of task you have an ID, find it by the ID

find / -iname *ID*

13

Yes works!
I can see the tasks and if I create a new task and then delete it, relevant files are deleted also.

1 Like
14

the cron is well accepted with your previous cron, no issue to see them, no issue to save the form again ?

15

Yes all ok, including editing.

1 Like
16

If I revert to non-testing repository, I keep the test fix, but will update normally when this is officially updated, right?
(and why it isn’t out yet?)

17

When released you will have the stable version. No time yet but i think we will release next week