'Getting the tree for 1 either results to cycle or is very long' error


#1

Hi!

Since yesterday I keep getting a Getting the tree for 1 either results to cycle or is very long’ error every time Insync tries to sync a file or a folder.

I haven’t change anyhting in my drive account configuration. Is there any fix for this?

I work with the latest version of Insync on Windows Server 2008 R2

I already sent to support my log file

Thanks


#2

Noted. Thanks for reporting this. We’re currently investigating as we speak.


#3

We’re getting this as well - Windows 10 Pro. Now have 44 sync errors.


#4

Having the same problem since this morning. Almost 5000 errors like this…


#5

Hello,

It would be much appreciated if we do have a timeline for the fixing.

Thanks,


#6

I have 27,952 errors like this! AND I spent hours yesterday trying to sort it out thinking it was something I had done, and now I see it’s happening to others too. So, yes please a timeline for a fix! Thanks


#7

Same here. Windows 7 Enterprise. Behind a company proxy. 5000-something errors.


#8

Same here on Windows 7 pro. This happened since version 1.3.19
Log says:

Thread 0x00002460:
File “isyncd\win\main.pyo”, line 106 in dispatch
File “isyncd\win\main.pyo”, line 43 in init
File “main.py”, line 30 in main
File “main.py”, line 39 in
Traceback (most recent call last):
File “display_handler_cef3.pyx”, line 37, in cefpython_py27.DisplayHandler_OnTitleChange (cefpython.cpp:42620)
File “isyncd\win\htmlui_impl.pyo”, line 203, in __OnTitleChange
File “ideskui\htmlui.pyo”, line 123, in on_title_change
File “ideskui\appui.pyo”, line 215, in _select_work_file
File “ideskmain\client.pyo”, line 321, in select_work_file
File “idesksyncer\gdsyncer.pyo”, line 309, in select_work_file
File “idesksyncer\syncworks.pyo”, line 225, in select_work_file
File “idesksyncer\syncworks.pyo”, line 590, in __open_gd_file
File “idesksyncer\gddb.pyo”, line 1086, in get_fs_path
RuntimeError: Getting the path of 554812 either results to cycle or is very long
Traceback (most recent call last):
File “display_handler_cef3.pyx”, line 37, in cefpython_py27.DisplayHandler_OnTitleChange (cefpython.cpp:42620)
File “isyncd\win\htmlui_impl.pyo”, line 203, in __OnTitleChange
File “ideskui\htmlui.pyo”, line 123, in on_title_change
File “ideskui\appui.pyo”, line 215, in _select_work_file
File “ideskmain\client.pyo”, line 321, in select_work_file
File “idesksyncer\gdsyncer.pyo”, line 309, in select_work_file
File “idesksyncer\syncworks.pyo”, line 225, in select_work_file
File “idesksyncer\syncworks.pyo”, line 590, in __open_gd_file
File “idesksyncer\gddb.pyo”, line 1086, in get_fs_path
RuntimeError: Getting the path of 554812 either results to cycle or is very long
Traceback (most recent call last):
File “display_handler_cef3.pyx”, line 37, in cefpython_py27.DisplayHandler_OnTitleChange (cefpython.cpp:42620)
File “isyncd\win\htmlui_impl.pyo”, line 203, in __OnTitleChange
File “ideskui\htmlui.pyo”, line 123, in on_title_change
File “ideskui\appui.pyo”, line 215, in _select_work_file
File “ideskmain\client.pyo”, line 321, in select_work_file
File “idesksyncer\gdsyncer.pyo”, line 309, in select_work_file
File “idesksyncer\syncworks.pyo”, line 225, in select_work_file
File “idesksyncer\syncworks.pyo”, line 590, in __open_gd_file
File “idesksyncer\gddb.pyo”, line 1086, in get_fs_path
RuntimeError: Getting the path of 554812 either results to cycle or is very long
Fatal Python error: Aborted


#9

I have exactly the same error as well.


#10

Same issue. ‘Getting the tree for [x] either results to cycle or is very long’ error


#11

Having the same problem, please a timeline for a fix!


#12

A fix is going to be out soon. Sorry about that.


#13

Same problem here. It isn’t even syncing the only folder (and respective subfolders) that I had selected for it. Do you have a fix timeline you can share please?


#14

Hi guys. Here are instructions from our engineer @dipesh to resolve this issue:

  1. Remove account (How to remove a Google account from Insync)
  2. Install this build: Insync 1.3.20
  3. Add account again and select the same local Insync folder

Let us know if this helps. We’ll release an update for Windows soon as @marte said :+1:


Getting the path of [number] either results to cycle or is very long
#15

What helped in my case was that path to folder was incorrect…which is strange as it worked for months…I’ve corrected it…and voila!

Albeit it’s strange situation…


#16

Didn’t Help. Any other solutions?


#17

@Andrea_Keeler Did you remove account and set it up again on Insync 1.3.20? What OS are you on?


#18

This seems to work like a charm- thank you for the fast turnaround! Was completely unable to sync earlier today.


#19

I did yes. I am using windows 10


#20

@Andrea_Keeler Did you start experiencing the issue with 1.3.19 or did you experience it previously too? Could you send across the Insync logs and dbs to support@insynchq.com?

Thanks