fix: traceroot import issue

[a7m-1st]

Description

fixes #590

Todo:

• I haven't tested if logging still works

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

[Wendong-Fan]

Thanks, @a7m-1st It looks like this is a path issue specific to Windows.

I'm concerned that maintaining two separate traceroute wrappers (one in backend and one in server) isn't ideal for long-term maintenance. Could we explore resolving the Windows path issue directly instead?

[a7m-1st]

oh all right didn't know that. In Linux too.

I think its related to the pycache getting generated. Converted to draft for now.
Thanks @Wendong-Fan

[a7m-1st]

Btw thus it may affect the next merge to the server

[LuoPengcheng12138]

I also encountered this issue when fixing the terminal_toolkit. My system is macOS—can project maintain only one file by changing the import path or using other methods?

[a7m-1st]

Thanks @LuoPengcheng12138 .
Then can I ask @Wendong-Fan is your init.py empty (in /eigent/utils)?

In the main branch it's empty, thus utils doesn't route to traceroot wrapper.

[a7m-1st]

Centralized trace_root wrapper at /eigent/utils:

1. Backend works fine
2. Server:
   a. Alembic path resolved to find /utils on root directory. Try alembic current
   b. Gave docker context of the parent directory and transferred eigent/utils to it
3. Removed redundant files