spawning command loop

Question

spawning command loop

maxilosgundam opened this issue a year ago · 2 comments

maxilosgundam commented a year ago

Tried the c.ai spawn command and getting a loop input according to the command prompt console.

Launching browser... OK
Opening character.ai page... OK

Answer 1 · 2023-11-05T18:51:01.000Z

Does the problem still persist for you? If so, please, provide more details of what you have done step by step.

Answer 2 · 2024-01-05T02:40:47.000Z

Does the problem still persist for you? If so, please, provide more details of what you have done step by step.

Different person but I am having a similar issue. I tried to use the /spawn command to bring in a character from c.ai via search query. On discord it's stuck at "Wait...", but in the command prompt it's spamming the same thing. I have gotten some red text in between a couple times.

The best overloaded method match for 'CharacterAI.Services.PuppeteerService.RequestPostAsync(string, string, object, string)' has some invalid arguments

and

Failed to kill browser. This error won't affect the workflow of the application, but if you will relaunch it and see this error again, it will mean that the old Puppeteer browser process probably is still running in the background and consumes the RAM on your machine.

Exception details:
System.ComponentModel.Win32Exception (5): Access is denied.
at System.Diagnostics.ProcessManager.OpenProcess(Int32 processId, Int32 access, Boolean throwIfExited)
at System.Diagnostics.NtProcessManager.GetModules(Int32 processId, Boolean firstModuleOnly)
at System.Diagnostics.NtProcessManager.GetFirstModule(Int32 processId)
at CharacterAI.Services.PuppeteerService.KillBrowser()

Eventually, it just stops saying: Launching browser... Stack overflow.
I have no real experience in coding, so I might be completely wrong, but I think it has something to do with
"puppeteer_browser_directory": null,
"puppeteer_browser_executable_path": null,

on the config.json, are both those lines supposed to say "null"?

EDIT: Okay figured out it was the puppeteer browser stuff. I went over and reassigned the directory from "null" to the folder containing chrome.exe and I set the executable path to chrome.exe. Or for people who are having this issue in the future, just assign it to whatever browser you use.