Yes, sorry about this. This is priority number 1 for me right now - I've been working for the last few days on fixing this. It has turned out to be harder to fix than I anticipated. Some sort of GPU memory error due to particular driver versions or something. That said, I should be able to fix it within the next day and a half (~36 hours from the time of this comment) unless something goes terribly wrong. I'm going to upgrade the whole stack, which should fix this issue, and also give a bit of a performance boost (slightly faster text generation) as a bonus.
Thank you 🫡 I will eventually get around to all your great suggestions (and the feedback from other users here) once I've got a handle on this issue and a few other important things. As always, feel free to re-ping me in comments and/or repost your most important feature requests and bug reports (once every couple of weeks or so) so I can bump them up the priority list.
5 replies
Yes, sorry about this. This is priority number 1 for me right now - I've been working for the last few days on fixing this. It has turned out to be harder to fix than I anticipated. Some sort of GPU memory error due to particular driver versions or something. That said, I should be able to fix it within the next day and a half (~36 hours from the time of this comment) unless something goes terribly wrong. I'm going to upgrade the whole stack, which should fix this issue, and also give a bit of a performance boost (slightly faster text generation) as a bonus.
Thanks for your hard work mate 👍
Thank you 🫡 I will eventually get around to all your great suggestions (and the feedback from other users here) once I've got a handle on this issue and a few other important things. As always, feel free to re-ping me in comments and/or repost your most important feature requests and bug reports (once every couple of weeks or so) so I can bump them up the priority list.
Cool cool, will do 👍
thanks for the help man