u/lppedd

A couple weeks ago I posted https://www.reddit.com/r/steelseries/s/BWjuCjPzES

Turns out it's a real issue with the GameHub memory, but it happens *only* when no headset is connected. Basically, the internal memory has a 10 seconds delay.

Apart from that, I have nothing but positive comments on the Omni headset. Looks good, super comfortable, amazing mic. Plus the wireless connection doesn't drop even when I'm three brick walls away from the GameHub (perfect for useless work meetings).

I don't use GG for advanced configurations, so can't really comment on that.

Is there a way to auto-approve certain git commands? I'd like to approve commits explicitly, for example, but stuff like diffs should be auto-approved.

Hey folks. For the last couple of days I've been investigating how to approach storing in-memory and persistent data in my VS Code extension, which is deployed both on desktop and browser. The built-in state management (i.e., global/workspace Memento) is too limited, so I'm looking at solutions such as sql.js, or RxDB.

RxDB seemed like the perfect project, but the Node.js FS and IndexedDB persistences are paywalled.

sql.js is basically a wrapper over a JS-compatible SQLite artifact, so it can run SQL queries which is pretty nice, but there is no schema or type-safety built-in.

Do you have any suggestion to offer or experience with sql.js and/or RxDB?

Stavo riflettendo su come anche per il settore IT Agosto sia un mese particolare, almeno in Italia. Ogni anno 3/4 del personale va in ferie e si è costretti a rimandare una buona parte dei task a Settembre (soprattutto quelli che richiedono un minimo di collaborazione). L'unica soluzione sembra quella di prendere ferie in Agosto. Insomma, un circolo vizioso.

Mi viene in mente un video in cui Marchionne parla esattamente di questo problema, e credo avesse parzialmente ragione.

I'm not sure whether I'm doing something wrong myself, but what I've done is:

1. Attach the base station to the PC
2. Go to System Settings > Display > (change any setting)
3. Go back to the main screen
4. Disconnect the USB from the PC
5. Connect the USB again, and the previously set setting is back to the previous value

This happens 99% of the times. The 1% actually persists the value for some reason. Anyone else is experiencing the same issue?

Workaround: enter and exit Settings one more time. Edit: doesn't work reliably.

Edit 2: even the volume itself is lost from time to time.

Before I spend time creating a reproducer and opening an issue I'd like to be sure others are seeing the same problem, or a similar one at least.

In 2026.2.x, in a Nx Angular monorepo, invoking the Reformat action (CTRL+ALT+L on Windows) for a decently big component takes more than 4-5 seconds to complete. It seems related to Optimize imports, as invoking Prettier through the Reformat with Prettier action doesn't exhibit the same problem.

2026.1.4 works as expected.

Just seen it's been published. Still unlisted, but visible.

I've been using VS Code and IJ parallely for the last week (I'm using the nightly channel in IJ) and while Copilot has consistently improved with the latest plugin releases, NES still seem extremely inferior.

Over the same code, suggestions don't appear, appear with major lags, or with lower quality.

Is this "by design", in the sense that different models or knowledge base is used?

For some reason the response gets cut abruptly. The model returns "Thinking..." and then simply stops.

Is this a known issue on VS Code Insiders? How do I debug the root cause?

On Windows, it looks like Copilot uses PowerShell and the integrated terminal interchangeably. Well, to be honest I've noticed it tends to prefer opening the integrated terminal instead of running PS directly in the chat session in newest releases.

What's the best way to instruct it to always run PowerShell commands in the chat session itself? If there is any that doesn't involve adding yet another point to the copilot-instructions file as it's already too big.

Next Edit Suggestions in VS Code are great, probably one of the better implementations around.

However, what bothers me is ghost suggestions do not take into account a max line length, so the workflow is always accepting + manually wrapping if required. This is valid especially for comments.

It would be nice to be able to configure a max line length. Or, is there a way to do so already?

As you may know at this point, VS Code releases have shifted from monthly (+ recoveries) to weekly (+ hotfixes) starting from March.

I'm still skeptical about whether that's a good change, but most posts I see tend to revolve around "hey now it's all AI slop". So I had a quick look at milestones, both monthly ones and weekly ones.

On average we have the following number of closed issues/PRs:

• monthly: 1500 (including all month-specific recovery releases)
• weekly: 500 (there has been a limited number of hotfix releases since April, some only related to LLM availability)

I've also peaked at some of those PRs, and as far as I could see they are still pretty small/focuses and accompanied by test cases most of the times.

In the end it seems it did not change as much as I thought it would. We get changes sooner, albeit with an higher chance of bugs slipping through since people might say "let's fix this next week". Although, people were probably saying "let's fix this in next recovery" anyways in the past.

I had a pretty long session with GPT 5.4. Left VS Code open overnight with no connectivity. Reconnected this morning and prompted on the same open session.

The model began doing all kind of actions like opening the GitHub PR tool window, opening a PR view, scanning the entire codebase, applying code to unrelated files or at incorrect location.

Well, wasted a bunch of credits.

Restarted the laptop and it was all good again. Anyone has experienced something similar?

Has anyone experimented with tools like rtk to compress input tokens?

Before attempting to add it to my pipeline, I'd like to see whether other users are happy with it.