This bug has been the bane of my existence for almost four years now: https://issuetracker.google.com/issues/204650736
This bug has been the bane of my existence for almost four years now: https://issuetracker.google.com/issues/204650736
The Android version of the app still has the zoom/cursor offset bug when using a software keyboard from when they sunset RDP 8. That has been a severe usability bug for over three years now.
CSV only exports data, not formulas. I don’t really consider it a proper spreadsheet interchange format.
Whether a jury feels a charge is fair is the whole reason trial by a jury of peers exists.
It’s a feature of the system, not a bug.
It’ll probably be there, but at least it can be disabled in the settings now. It won’t go away on its own.
This was when I stopped using it for a while. I sent multiple feedback messages as it really irritated me.
I was using .local, but it ran into too many conflicts with an mDNS service I host and vice versa. I switched to .lan, but I’m certainly not going to switch to .internal unless another conflict surfaces.
I’ve also developed a host-monitoring solution that uses mDNS, so I’m not about to break my own software. 😅
Try a dry soft bristle toothbrush. I keep a few around to clean various electronics.
Not with this announcement, but it was.
It depends on the model you run. Mistral, Gemma, or Phi are great for a majority of devices, even with CPU or integrated graphics inference.
There are hidden files and directories in Linux that begin with a period (.). You can show them with Ctrl + h
if you have a keyboard.
In case you weren’t aware as well, Steam stores game files in a hidden directory in your home folder.
Show me a music store I can purchase music from on my phone through an app, and I’ll purchase it.
We all mess up! I hope that helps - let me know if you see improvements!
I think there was a special process to get Nvidia working in WSL. Let me check… (I’m running natively on Linux, so my experience doing it with WSL is limited.)
https://docs.nvidia.com/cuda/wsl-user-guide/index.html - I’m sure you’ve followed this already, but according to this, it looks like you don’t want to install the Nvidia drivers, and only want to install the cuda-toolkit metapackage. I’d follow the instructions from that link closely.
You may also run into performance issues within WSL due to the virtual machine overhead.
Good luck! I’m definitely willing to spend a few minutes offering advice/double checking some configuration settings if things go awry again. Let me know how things go. :-)
It should be split between VRAM and regular RAM, at least if it’s a GGUF model. Maybe it’s not, and that’s what’s wrong?
Ok, so using my “older” 2070 Super, I was able to get a response from a 70B parameter model in 9-12 minutes. (Llama 3 in this case.)
I’m fairly certain that you’re using your CPU or having another issue. Would you like to try and debug your configuration together?
No offense intended, but are you sure it’s using your GPU? Twenty minutes is about how long my CPU-locked instance takes to run some 70B parameter models.
On my RTX 3060, I generally get responses in seconds.
Or maybe just let me focus on who I choose to follow? I’m not there for content discovery, though I know that’s why most people are.
I still have it on my Pixel 8 Pro. It requires a double tap to occur in less than 300 seconds.