search

go-vikunja / vikunja

Mirror of vikunja from https://code.vikunja.io/api
GNU Affero General Public License v3.0
758 stars 55 forks source link

Integration microsoft to do list import function does not import #238

Closed inuonly closed 2 months ago

inuonly commented 3 months ago

Description

The import option in menu leads to a page where microsoft to do list can be imported, once the process completes we are greeted with a successful message and are informed that it will happen in background and we will notify. Even after days we still dont se any list imported from microsoft to do. Same is applid to trello just to check but it still is not working. It never fails both methods microsoft to do and trello are completing successfully. But nothign is imported.

Vikunja Version

Version: v0.23.0

Browser and version

123.0.1 (64-bit)

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

Vikunja Version : image Browser Version : image

Steps :

  1. Import page options: image
  2. individual microsoft to do import page image
  3. microsoft login page image
  4. redirected back to result page in vikunja after logging in image
kolaente commented 3 months ago

What do you see in the logs?

inuonly commented 3 months ago

What do you see in the logs? image

It shows something like this but even if I scroll I see no error message or anything specific to import or similar info or error message.

kolaente commented 3 months ago

If you search the log for Error, do you see anything?

inuonly commented 3 months ago

If I search error , then there is 0 entries . If i search for microsoft then I get only this entry and I just now tried to import once to get this in logs. image Apart from this entry everythign else is just a 200 or 304 log in approximately 1000 lines of logs.

kolaente commented 3 months ago

What is the log level?

inuonly commented 3 months ago

I dont have any idea what level log is it, since I have not changed the config, it should be the default. Let me look into hot to manually changing the log level.

inuonly commented 3 months ago

So by default the logs go to info level, as per instructions here - https://vikunja.io/docs/config-options/ . I went further and changed log level manually to debug and here is the screenshot . I restarted my vikunja instance but still there is no sign of error in logs and the import option completes with the same message that it was successful and will be carried in background. But nothign shows up related to any import from my microsoft to do account. image This is the log , after changing to debug level now.

kolaente commented 3 months ago

This is the log , after changing to debug level now.

This looks like the import did not actually start - did it tell you "you already did the import once, do you really want to do this again?" - in that case you need to confirm the import. The debug log should give you plenty of information while the import is running, in your case it looks like it didn't start.

inuonly commented 3 months ago

No it does not spill any such message for confirming to do again as you mentioned. The result is same means the screenshot in step 4 always appears. Logs only show same thing over and over again.

kolaente commented 3 months ago

Okay, then that's the bug. I'll take a look.

inuonly commented 3 months ago

If it helps, I am available on discord and also not deleting the instance I have just in case if it cannot be reproduced. Hope you find it.

kolaente commented 3 months ago

I'm heading off on vacation tomorrow for a week, will ping you back after that when I find something.

kolaente commented 2 months ago

The message not showing is fixed in https://github.com/go-vikunja/vikunja/commit/0b9ef27d04f388b86acad854ad118c870fead02a. Please check with the next unstable build (should be ready for deployment in ~45min, also on try).

inuonly commented 2 months ago

Since I am running in docker environment, can I manually change those two lines in respective two files? ( https://github.com/go-vikunja/vikunja/commit/0b9ef27d04f388b86acad854ad118c870fead02a one I think is optional being a comment); as I suppose these changes will take time to reach docker images. I am trying to find the location of these files in docker instance but not able to find the path to the MigrationHandler.vue file or am I doing this wrong way.

The message not showing is fixed in 0b9ef27. Please check with the next unstable build (should be ready for deployment in ~45min, also on try).

kolaente commented 2 months ago

as I suppose these changes will take time to reach docker images

The change is already in the latest unstable build. You can just use the :unstable tag for the docker image, pull and restart your stack and you should be good to go. Make a backup first! You can learn more about the different versions here.

I am trying to find the location of these files in docker instance but not able to find the path to the MigrationHandler.vue file or am I doing this wrong way.

You can't edit the file in the docker container because they only contain the final compiled binary with the frontend and api bundled, not the source files. If you still want to edit the files, you need to build Vikunja from sources manuall. In your case, it's a lot easier to just switch to unstable though.

inuonly commented 2 months ago

Hey thanks for the tip. just used unstable tag for docker image and now migration part works. It went in the very first attempt. Also if I revisit, it warns me about duplicate entries possibility before confirming just like you asked earlier. One question, do i need to keep using unstable or does these changes reflect in latest tag docker image after some time. Thank you so much <3 . I believe we could close this issue. Also hope your vacations went well. [forgor that] .

kolaente commented 2 months ago

Unstable builds are built from the latest commit in the main branch. In irregular intervals a release is made from that and then the changes will be cut into a release. In your case, that means you can keep using unstable and then switch to the next release once that's out.