THE PROGRAM WAS WORKING PRIOR TO THE LATEST UPDATE, WELL I WAS GETTING A ERROR CLONING REPO BUT NOW I CANT EVEN GET TO THAT STEP I AM ON WINDOWS 11 AN HAVE DOCKER & UBUNTU
Please provide the following info (tick the boxes after creating this topic):
Submission Type
[YES] Bug or Error
Feature Request
Documentation Issue
Question
Other
Workbench Version
[YES] Desktop App Version 0.50.16
CLI v0.21.3
Other
Host Machine operating system and location
[YES] Local Windows 11
Local Windows 10
Local macOS
[YES] Local Ubuntu 22.04
Remote Ubuntu 22.04
Other
cd /home/workbench/.nvwb/project-runtime-info
workbench@DESKTOP-8HLJ666:~/.nvwb/project-runtime-info$ ls
OpenDevin-OpenDevin-38eda83696a829ea541f5bf416a66ea6d89ccc1f
OpenDevin-dce53b538b0b686fbbbca7c724cf3488aa6824ff
OpenDevin1-92e69422548d7f8086f6e0cced072f6e3626a7e8
OpenDevin2-c7a4586b2e4ad612b3ea34fc730f2b5c1a8a953e
OpenDevinN-dee253d22ca7b0fab8c0ca97601978d62da72deb
flexdinero-OpenDevin-13f34f619ebeab9b6b391c641bbd6f8291de4854
cat /home/workbench/.nvwb/logs/nvwb.log
{“level”:“info”,“gitServerUrl”:“https://github.com”,“status”:“”,“time”:“2024-05-10T13:37:49-05:00”,“message”:“Detected git server with valid credentials during auto git author configuration.”}
{“level”:“error”,“error”:“timed out getting token”,“isWrapped”:false,“isInteractive”:false,“engine”:“json”,“detail”:“detail”,“time”:“2024-05-10T13:41:57-05:00”,“message”:“timed out getting token”}
{“level”:“error”,“error”:“timed out getting token”,“isWrapped”:false,“isInteractive”:false,“engine”:“json”,“detail”:“detail”,“time”:“2024-05-23T15:29:04-05:00”,“message”:“timed out getting token”}
Thanks for providing the logs, we are looking into the issue. Apologies, and thanks for your patience.
From the logs it appears that AI Workbench had erroneously determined your OS was unsupported. Can you confirm (Windows Search tool > “About your PC”) that the following is your Windows version?
“WSL2Info”:{“WindowsProduct”:“Microsoft Windows 11 Home”,“WindowsVersion”:“10.0.22631”,“WindowsWSLDistroName”:“NVIDIA-Workbench”}
Does the issue persist after rebooting your system? Or is it a one-off occurrence?
