virtuallyunknown

I'm starting to get this error almost every day, and the "Learn more" button leads to [this particular page](https://docs.github.com/en/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/managing-copilot-policies-as-an-individual-subscriber#enabling-or-disabling-duplication-detection) but if you pay attention to the URL, you will see...

Nice finds @Silloky > According to [this](https://docs.github.com/en/copilot/using-github-copilot/finding-public-code-that-matches-github-copilot-suggestions) page, step 3, if you head into the Copilot output in the terminal, you should see the link to the repo Copilot was...

Also, it looks like the issue has been going on [at least since February](https://github.com/orgs/community/discussions/107059).

If I may voice my personal opinion, I would love to have an option such as (or similar to) the `prefixOutput` in this PR. When I have turbowatch run a...

Hey gajus. First, I just want to say thank you for developing this library. I don't consider myself knowledgeable enough to provide an opinion on your most of what you...

> @NickHeiner In that case, you will need to either adopt esm or use something like `node --loader tsx your-script.ts` Hey @gajus, do you mind taking a look at this...

I was previously using `node --loader tsx turbowatch.ts` because for some reason when you use the `turbowatch` binary you have to `ctrl+c` twice to terminate the process, the first time...

> The first time you send a signal with ctrl+c it initiates graceful termination and waits for all services to shutdown. > > If you don't wait and press again,...

You said that the first signal is graceful termination, and the second signal is forceful termination. So I was asking if there is a way I can instead configure the...

> You could, but depending on what services you are running, there is no guarantee that it will shutdown all the services. I would not do it as a default...