Closed absane closed 1 year ago
unfortunately windows training is the purview of @devilismyfriend and I cannot really do much about it
He personally said he would be working on it a bit ago, so stay tuned :)
https://github.com/152334H/DL-Art-School/issues/8#issuecomment-1442536426
I also added a temp commit so that casual windows users don't get an error on the latest commit, but 8bit will not be enabled until it happens
All good, thank you. Works for now with the roll back, but I did decide to move over to Collab for the majority of the work after I found my 3090 wasn't as fast as Collab. Though, Windows was nice because I was getting tired of all the tabs and terminals I had open ;)
Thank you!
I did decide to move over to Collab for the majority of the work after I found my 3090 wasn't as fast as Collab
This is very weird and shouldn't be happening honestly. I'll test it on my own to check
Yesterday and this morning I was troubleshooting a training issue, but nonetheless DLAS was working. This afternoon I saw an update in the Windows GUI, so I applied it. Ever since then, I've been running into this issue:
Initially I thought maybe it was CUDA, Miniconda, or Python since I had so many different versions installed and probably broken libraries/packages. I uninstalled everything, started with a clean slate, and I still get this error. The longer I look into it, the more it seems to be related to 'bitsandbytes' given the stack trace and the commit history in the last push showing that it was recently added
Reverting back to a previous commit works:
git checkout 83b901c656447126d5a0877639d394335204e1ac
This is Windows 10, Python 10, CUDA 11.7.