Devon icon indicating copy to clipboard operation
Devon copied to clipboard

Stuck on initializing

Open mberman84 opened this issue 1 year ago • 11 comments

I installed everything and when I ran the command "devon" it gets stuck on initailizing.

mberman84 avatar May 13 '24 16:05 mberman84

@mberman84 Hey thanks for raising this issue! Currently it doesn't handle all errors well so it might have crashed somewhere along the way. Are there any logs above the "Initializing..." UI?

ObjectJosh avatar May 13 '24 17:05 ObjectJosh

@ObjectJosh no logs

mberman84 avatar May 13 '24 21:05 mberman84

@mberman84 Hm, interesting. What OS are you on? And does it happen consistently (it hasn't been able to respond after restarting?)

ObjectJosh avatar May 13 '24 21:05 ObjectJosh

I am experiencing the same thing on Mac Pro M3

businistry avatar May 16 '24 15:05 businistry

Ok, theres going to be a big refactor we are packaging today that should fix the hanging. Will also include openai support. @mberman84 @businistry

akiradev0x avatar May 16 '24 16:05 akiradev0x

Same issue on Macbook Pro M3

SuperMohit avatar May 17 '24 10:05 SuperMohit

Interesting. Another person tried it and had an issue on M3. Taking a dive tomorrow.

akiradev0x avatar May 18 '24 02:05 akiradev0x

Hey @mberman84 did it end up working for you? We just pushed a new version that seems to be better.

akiradev0x avatar May 18 '24 20:05 akiradev0x

Same here on Manjaro

drupalshift avatar May 20 '24 17:05 drupalshift

I'm on an M3 Mac. To get it to work, I deleted the "devon-agent" folder in "/Users/your_home_directory/.local/pipx/venvs" and then reinstalled it using the installation script.

1of13 avatar May 20 '24 21:05 1of13

Hey all, heres a couple things you can try:

  1. uninstall via pipx and reinstall the latest version
  2. upgrade nodejs version to 22, I tested this yesterday (I found a failure in nodejs 18 that we haven't quite solved yet)
  3. run in debug mode, that may help us understand whats going on

@drupalshift @SuperMohit

akiradev0x avatar May 20 '24 21:05 akiradev0x

This worked for me. I deleted the agent, uninstalled and reinstalled, and upgraded node from 18. but now theres an issue where when its generates a PATH. will likely add a new issue for this.

businistry avatar May 21 '24 17:05 businistry

awesome! @businistry glad to hear it. I think for now, we can close this issue.

akiradev0x avatar May 21 '24 18:05 akiradev0x

for me it stuck like this. i uninstalled everthing then install again, updated npm and node. devon

dada-mhmd avatar Jun 09 '24 14:06 dada-mhmd