search

ulixee / hero

The web browser built for scraping
MIT License
649 stars 32 forks source link

Target for command not available (Events) #204

Closed soundofspace closed 1 year ago

soundofspace commented 1 year ago

See this error happening pretty much all the time. I think this happens when a hero instance, together with its connections is closed and the core is still doing some cleanup/work. This should detect a close and stop/ignore this. This is probably related to #203 

Error: Target for command not available (Events)
    at new CommandRunner (/app/.yarn/cache/@ulixee-hero-core-npm-2.0.0-alpha.16-b4152c72e1-55ca8f31a6.zip/node_modules/core/lib/CommandRunner.ts:16:13)
    at ConnectionToHeroClient.executeCommand (/app/.yarn/cache/@ulixee-hero-core-npm-2.0.0-alpha.16-b4152c72e1-55ca8f31a6.zip/node_modules/core/connections/ConnectionToHeroClient.ts:236:27)
    at ConnectionToHeroClient.handleRequest (/app/.yarn/cache/@ulixee-hero-core-npm-2.0.0-alpha.16-b4152c72e1-55ca8f31a6.zip/node_modules/core/connections/ConnectionToHeroClient.ts:63:25)
    at EmittingTransportToClient.<anonymous> (/app/.yarn/cache/@ulixee-hero-core-npm-2.0.0-alpha.16-b4152c72e1-55ca8f31a6.zip/node_modules/core/connections/ConnectionToHeroClient.ts:43:45)"
blakebyrnes commented 1 year ago

Do you have a session database showing this error? Also, is this just a matter of this logging to logs? Or is it crashing something?

soundofspace commented 1 year ago

It was a logging issue. But upgrading to 2.0.0-alpha.17 seems to have fixed this.

soundofspace commented 1 year ago

Actually it is still popping up quite a lot. Will upgrade to latest version next week, and if it is still there I will provide a session db.