Node.js version error #1
Comments
|
Getting a lot of different errors this is just one of them. |
|
sorry for the late reply I was not anticipating usage yet. I just have the auto coder ready, it is on fire. I am on mac and cannot test it in windows. I had that issue also and doing a full rebuild solved it. first do then then the robotjs is not actually in use but it will be soon to physically act as an agent on your pc, supervised and/or auto. I don't believe in autoGPT but with user supervision, guidance and intervention it works very well. I am just at the point that it reads its own code and makes documentation. The only limit is the 25 messages per 3 hours of gpt4, otherwise the whole project would be documented already. Check the latest readme for what I mean. I hope you can get it up and running, otherwise I have binaries also for windows. You can build all binaries also with npm run build |
|
ps I added all info in the readme beginning, hopefully an improvement for a stable install, which is a challenge |
|
OK that is great good work on the documentation. I tried however to get it working in WSL2 Ubuntu and natively on Windows. The issue seems to be in WSL2 with dbus: The error message suggests that there is an issue connecting to the D-Bus system bus socket in your WSL2 environment. D-Bus is a system message bus that allows communication between different processes on the system. Please note that using Electron in WSL2 might have limitations or unexpected behavior due to the differences in the underlying system architecture. It is recommended to develop and run Electron applications on a native Linux or Windows environment whenever possible. I also tried it in Windows and can't get it to install because of all the dependencies. The commands I used to get it working on Ubuntu that should work on bare metal hardware are below in no paticular order I just copied them as I was using them. I got help from GPT4 on getting this as far as I did :) sudo apt-get install libx11-dev npm install electron-is-dev Are you running it on OSX did you say? Could you bootcamp get it running on Windows? I could get it running in a VMware virtual machine but I wanted GPU access (if it's even needed?). Be good to get this working. |
|
(base) chronic@Nemesis:~/KITT-AI-Browser$ npm install dmg-license npm ERR! A complete log of this run can be found in: /home/chronic/.npm/_logs/2023-05-02T11_41_40_237Z-debug-0.log I was debugging getting npm run build to work and ended up with this when I tried to install one of the dependencies it needs. |
|
Are you able to do a npm run build? I have all binaries on my pc. I can make a torrent link for them. The autoupdate should preferable work so that everybody is always on the latest version. If you want I can upload binaries to icloud and give you the links for windows and linux. I should be able to find linux and windows machines online. I used to work with nwjs but that was constantly crashing. I learned quite a lot about Electron in short time but I am by no means an Electron specialist. Yes I am on mac M1, usually mac is the hardest to install stuff on. Why are you installing npm install dmg-license? please update me if you have some progress with installing stuff and encounter new issues, I might have also had them. Great that you are putting effort in getting it up and running! |
|
(base) chronic@Nemesis:~/KITT-AI-Browser$ npm run build
• electron-builder version=24.3.0 os=5.15.90.1-microsoft-standard-WSL2
That is as far as I have got it to go. I managed to get past npm install with the help of GPT but the npm run build resulted in the above error. I have bashed other bugs with getting npm run build working however before getting to this point. I think I already included everything I installed to get to this point but it looks like this is as far as I can go as this package requires a mac :( I could spin up my emulator but I am a PC guy it runs so awfully even on my machine I can't bring myself to do it :) |
|
I was trying to get dmg-builder and dmg-license packages to install. Seemed like they were required to go futher. |
|
ah ok that is so that you can build for mac, like I can build for win and lin also |
|
Aha ok. Could you not upload the binaries as a release to github? |
|
they are to big but I can maybe make it a complete empty node_modules and get it under 100mb. There is also a release section on github, not sure if the 100mb max also applies there. |
Not sure, if not just whack a magnet link here |
|
I forgot something vital, I update the readme and added the remove package-lock.json. rm -rf node_modules |
|
I will also try to remove the build stuff so that these issues are solved. I can pushed it to a test branch. You can try it too if you want, I removed and rebuild everything and it startsup ok. I am just now thinking I should do that in a conda env so that nothing is pre installed { }, |
|
hi, i did a little more cleaning. It installs and runs ok in a clean env { |
|
Does the EXE keep logs I can send you anywhere? I am getting a lot of errors here in Windows land. |
|
Is it meant to come up with all this text at the start? I don't seem to be able to type anywhere either it's like the box loads of the bottom of the screen and I can't get to it. |
|
When I run it in Ubuntu from cloning the github repo it seems to get further I have got a text box to type in but get this error when saying hi: Me : It doesn't have any of the options at the top either looks pretty broken still but loads up at least now :) Getting further. |
|
√ Rebuild Complete E:\KITT-AI-Browser>npm install up to date, audited 300 packages in 969ms 45 packages are looking for funding found 0 vulnerabilities E:\KITT-AI-Browser>npm start
Debugger listening on ws://127.0.0.1:9229/e640c324-7ba4-4cb2-8f09-a44826281df8 E:\KITT-AI-Browser>npm start
Debugger listening on ws://127.0.0.1:9229/f27717ad-04e4-484c-ab2f-8448cc40b4e6 E:\KITT-AI-Browser> Got it running again and got some error logs this time |
|
On native Windows this time. I found out it won't run on WSL2 because DBUS kernel access doesn't exist in WSL2. |
|
Hey that is more starting to look like it. There might be an issue with me renaming the repo to KITT-AI-Browser instead of just KITT. I will do a fresh git init and see what goes down.
it moved all to plugins, stt and tts are in the path when needed, like eg »stt»gpt»tts would make both talk I changed tts to the more realtime, and free, html5 tts. The browser can also do better stt than whisper even I noticed. Elevenlabs has much better voices but during development with all the cycles credits are gone quickly. For demo's it is great though and it could be like eg »stt»gpt»11 would use elevenlabs I am thinking that I can reuse all these instruction to learn KITT about the prompt path domain language. I added parameters like eg »file . »feed from=1 to=5 »gpt will only send the first 5 16k chunks. last thing I did yesterday was testing the bash plugin ok. When you want that gpt is allowed to try something 3 times you can do eg ###make a bash script that writes a C source file, compiles it and executes it »bsh will only return the result to you and ###make a bash script that writes a C source file, compiles it and executes it »bsh»gpt will return the result to gpt and when there is an error it will reply with a fix to you for now you can manually define the amounts of attempts by doing ###make a bash script that writes a C source file, compiles it and executes it »bsh»gpt»bsh»gpt would give it 2 chances to make it work, I had it on automatic at errors but you do want to set some boundaries. I am thinking to control it with a parameter max like ###make a bash script that writes a C source file, compiles it and executes it »bsh max=3 »gpt |
|
btw I uploaded all binaries, it is quite a drag to upload it all. Most are under 100mb now so much is removed and can be hosted in the repo. KITT needs github contol and run the whole thing. With robotjs and html5 text from image I can probably give it kindof physical mouse and key control. It seems there is already some kind of neuralnetwork installed in the Chromium browser. I will make a video about how to deal with all the logging and debugging when the plugin cannot be found |
|
|
|
yeah we have an issue here ~/git/KITT/front-end/plugin.js: ~/git/KITT/lib/shared.js: ~/git/KITT/plugins/elevenlabs/main.js: I'am at this point not sure how the binaries deal with this but for npm it should fix that you have no active plugins. I think I understand better what you mean now with nothing showing, also not the plugin tabbar. My screen looks like this now when I startup. When you have it like that then you should be able to work with it. First time go into the webview to logon to your account at openAI, thereafter you can close the webview when you want.
|
|
Some debug info for my electron-rebuild I just done from a fresh clone. C:\Users\chron\Script Work\KITT-AI-Browser>node_modules.bin\electron-rebuild.cmd \ Searching dependency treeAttempting to build a module with a space in the path
C:\Users\chron\Script Work\KITT-AI-Browser> |
|
Results of npm start, stuff disappears when I click on it. C:\Users\chron\Script Work\KITT-AI-Browser>npm start
Debugger listening on ws://127.0.0.1:9229/2cdeecd1-701f-4d29-86fa-9987f2c29f87 |
|
ok I removed node-py, it is a leftover from the start with the first alpaca model. Maybe it is needed later but it seems to only be in the way now. I added a useGl false to the browserwindow init, and just pushed it |
Error: The module '\?\C:\Users\chron\KITT\node_modules\robotjs\build\Release\robotjs.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 108. This version of Node.js requires
NODE_MODULE_VERSION 113. Please try re-compiling or re-installing
the module (for instance, using
npm rebuildornpm install).Do I just need a different version of node.js? I am using the latest version node-v18.16.0-x64.msi Should I be using an older version? If I can get this working I will knock up a tutorial on setting it up.
The text was updated successfully, but these errors were encountered: