sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: node
Issue: Windows installer bug with chocolatey
Labels: windows,install

### Version

all

### Platform

_No response_

### Subsystem

_No response_

### What steps will reproduce the bug?

folders that are not deleted after you remove them

### How often does it reproduce? Is there a required condition?

_No response_

### What is the expected behavior?

_No response_

### What do you see instead?

chocolate automatic deletion

### Additional information

Chocolate library nodejs are sometimes not removed when removing them, which leads to problems. For example, in the latest version, when I downgrade the version while the npm install command is causing problems, powershell commands are already installed when I install. This is why my question, which can be solved with degrade, cannot be solved.
I just wanted to give you some information. After deleting it, you also need to set up the "choco.exe" file after you go to the location and delete the folder in the program there. That's the only way I solved my problem.
Repository: PowerToys
Issue: Add unit tests for developer preview
Labels: Area-Tests,Status-In progress,Product-File Explorer

### Description of the new feature / enhancement

Add unit tests for developer previewer

### Scenario when this would be used?

Add unit tests for developer previewer

### Supporting information

_No response_
Repository: next.js
Issue: Internationalized routes don't work with dynamic routes without getStaticPaths
Labels: Internationalization (i18n)

### Run `next info` (available from version 12.0.8 and up)

Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 20.6.0: Wed Nov 10 22:23:07 PST 2021; root:xnu-7195.141.14~1/RELEASE_X86_64
    Binaries:
      Node: 16.13.0
      npm: 8.1.0
      Yarn: 1.22.10
      pnpm: N/A
    Relevant packages:
      next: 12.0.8
      react: 17.0.2
      react-dom: 17.0.2

### What version of Next.js are you using?

12.0.8 (latest)

### What version of Node.js are you using?

16.13.0

### What browser are you using?

Chrome

### What operating system are you using?

macOS

### How are you deploying your application?

next start

### Describe the Bug

dynamic routes with i18n routing fall into an infinite redirect loop.

### Expected Behavior

When creating a dynamic route I should be able to access the link with no infinite redirect loop.

### To Reproduce

in a basic next.js app, add the dummy example from the docs as to build a dynamic page: 
1. pages/post/[pid].tsx
2. Then make this the content of the page, as per the docs:

```js
        import { useRouter } from 'next/router'

            const Post = () => {
              const router = useRouter()
              const { pid } = router.query

              return <p>Post: {pid}</p>
            }

        export default Post
```

3. Now create a next.config.js file to introduce i18n internationalized routes per domain:

```js
   
      module.exports = {
          basePath: "/app",
      i18n: {
        localeDetection: false,
        locales: [
          "de-DE",
          "de-AT",
          "en-US",
        ],
        defaultLocale: "en-US",

        domains: [
          {
            domain: 'localhost:3000',
            locales: [
          "de-DE",
          "de-AT",
          "en-US",
        ],
            defaultLocale: process.env.APP_LOCALE || "en-US",
            http: true,
          },
        ],
      },
    };
```
4. Now run yarn build && yarn start to run the app
5. Navigate to localhost:3000/app/post/1

You should be able to see printed in the screen: Post 1, but instead, you see `Post` and the page keeps refreshing.

I prepared this simple example based on the docs: https://github.com/sergioviniciuss/next-dynamic-routing-i18n
Repository: flutter
Issue: multicast_dns scan for all the mDNS devices in the network
Labels: c: new feature,package,c: proposal,p: multicast_dns,team-ecosystem,P3,triaged-ecosystem

<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill out the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Use case

<!--
     Please tell us the problem you are running into that led to you wanting
     a new feature.

     Is your feature request related to a problem? Please give a clear and
     concise description of what the problem is.

     Describe the alternative solutions you've considered. Is there a package
     on pub.dev/flutter that already solves this?
-->

I am interested to scan for all NSD / DNS-SD / Bonjour / mDNS devices in the network and notify the user if a new one has joined.

I saw that there is an option to search a specific serviceType but not all at once.

## Proposal

<!--
     Briefly but precisely describe what you would like Flutter to be able to do.

     Consider attaching something showing what you are imagining:
      * images
      * videos
      * code samples

     Does this have to be provided by Flutter directly, or can it be provided
     by a package on pub.dev/flutter? If so, maybe consider implementing and
     publishing such a package rather than filing a bug.
-->

As written in [DNS-SD specification](https://datatracker.ietf.org/doc/html/rfc6763#section-9) chapter 9 there is a special type `_services._dns-sd._udp` that retrieve all current types in the network.


I suggest that we add two new functions.
1. Function to get all current serviceType on the network using `_services._dns-sd._udp`.
2. A function that retrieves all the devices in the local network, this function will use the first function and will run on each serviceType result.
Repository: yt-dlp
Issue: VEEJOY
Labels: site-request,account-needed

### Checklist

- [X] I'm reporting a new site support request
- [X] I've verified that I'm running yt-dlp version **2022.01.21**. ([update instructions](https://github.com/yt-dlp/yt-dlp#update))
- [X] I've checked that all provided URLs are alive and playable in a browser
- [X] I've checked that none of provided URLs [violate any copyrights](https://github.com/ytdl-org/youtube-dl#can-you-add-support-for-this-anime-video-site-or-site-which-shows-current-movies-for-free) or contain any [DRM](https://en.wikipedia.org/wiki/Digital_rights_management) to the best of my knowledge
- [X] I've searched the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar issues including closed ones. DO NOT post duplicates
- [X] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)
- [ ] I've read about [sharing account credentials](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#are-you-willing-to-share-account-details-if-needed) and am willing to share it if required

### Region

Germany

### Example URLs

- Single video: https://www.veejoy.de/de/serien/die-europa-park-geschichte/die-weite-welt-ist-mein-feld
- Single video: https://www.veejoy.de/de/serien/die-europa-park-geschichte/von-italien-nach-europa
- Single video: https://www.veejoy.de/de/serien/die-europa-park-geschichte/nur-das-gute-bricht-sich-bahn

### Description

New streaming service with videos from the Europa-Park in Germany.

### Verbose log

```shell
[debug] Command-line config: ['-vU', 'https://www.veejoy.de/de/serien/die-europa-park-geschichte/nur-das-gute-bricht-sich-bahn']
[debug] Encodings: locale cp1252, fs utf-8, out utf-8, err utf-8, pref cp1252
[debug] yt-dlp version 2022.01.21 [f20d607] (win_exe)
[debug] Python version 3.8.10 (CPython 64bit) - Windows-10-10.0.19042-SP0
[debug] exe versions: none
[debug] Optional libraries: Cryptodome, mutagen, sqlite, websockets
[debug] Proxy map: {}
Latest version: 2022.01.21, Current version: 2022.01.21
yt-dlp is up to date (2022.01.21)
[debug] [generic] Extracting URL: https://www.veejoy.de/de/serien/die-europa-park-geschichte/nur-das-gute-bricht-sich-bahn
[generic] nur-das-gute-bricht-sich-bahn: Requesting header
WARNING: [generic] Falling back on generic information extractor.
[generic] nur-das-gute-bricht-sich-bahn: Downloading webpage
[generic] nur-das-gute-bricht-sich-bahn: Extracting information
[debug] Looking for video embeds
ERROR: Unsupported URL: https://www.veejoy.de/de/serien/die-europa-park-geschichte/nur-das-gute-bricht-sich-bahn
Traceback (most recent call last):
  File "yt_dlp\YoutubeDL.py", line 1367, in wrapper
  File "yt_dlp\YoutubeDL.py", line 1437, in __extract_info
  File "yt_dlp\extractor\common.py", line 612, in extract
  File "yt_dlp\extractor\generic.py", line 3966, in _real_extract
yt_dlp.utils.UnsupportedError: Unsupported URL: https://www.veejoy.de/de/serien/die-europa-park-geschichte/nur-das-gute-bricht-sich-bahn
```
Repository: godot
Issue: New TileSet editor: Rendering issue when zooming out on close zoom
Labels: bug,topic:rendering,confirmed,topic:2d

### Godot version

4.0 Alpha 1

### System information

Fedora 34 with i3 desktop, Ryzen 5 2400g APU

### Issue description

In tileset editor when I zoom out, the entire transparency grid turns grey. It only happens when the zoom is already significant.

https://user-images.githubusercontent.com/70446098/151020224-f6ddd675-80e1-4626-9b19-5bd8cf31e16e.mp4

Tileset used: https://kenney-assets.itch.io/1-bit-pack

### Steps to reproduce

Create a tileset resource.
Add a texture.
Zoom in very close.
Start zooming out (sometimes zooming out a few times makes the issue disappear, so if your mouse wheel isn't "smooth" try applying only one "jump").

### Minimal reproduction project

[bug_report.zip](https://github.com/godotengine/godot/files/7935537/bug_report.zip)
Repository: TypeScript
Issue: Inability to use typeof on an ES private property
Labels: Suggestion,Help Wanted,Experience Enhancement

# Bug Report

### 🔎 Search Terms

- typeof
- private

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about private and typeof

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?#code/MYGwhgzhAECiAeYC2AHEBTaBvAsAKGmgGIUAnASwDcwAXdABVIHsVoBeaAcgAt0QQmnANz58hYEwB2EGqQCuwGk1IAKAJTYxhaBOk1oKAFzQaATxTomAMxPdyEAHQkK1OoxbsuAd2UgAJsJa4lIyBgBMxgjIaOgA2pzOVLQMzCicALqenD6k-oEE0AC++MV4QA)

### 💻 Code

```ts
class Example {
  #privateProp = 'hello';

  constructor() {
    const p: typeof this.#privateProp = 'world';
    const p2: Example['#privateProp'] = 'world';
  }
}
```

The example is kept short for reproduction, but in practice this is more for cases where you would want to use `keyof this.#someProperty` and similar constructs (since here the type could just be inferred).

### 🙁 Actual behavior

Specifying a type using `const name: typeof this.#anESprivateProperty` is not possible.

For `p`, the error is that an identifier is expected (because it's a `PrivateIdentifier` and not an `Identifier` from the compiler's pov?).

For `p2`, the error is that the property does not exist on the type, which is logical when done from "outside" the class where the property should not be visible.

### 🙂 Expected behavior

Having the ability to use typeof on an ES private property from "inside" the class itself where that property is visible, e.g. like in the example code above.
Repository: flutter
Issue: Proposal to rename ChoiceChip's `onSelected` method to be `onTap` / `onChanged` / `onSelectionChanged`
Labels: framework,f: material design,c: proposal,team-design,triaged-design

The ChoiceChip has onSelected parameter which takes a closure which is called every time the ChoiceChip is tapped! If it is to be called every time the user taps on the chip then why not rename it to something like 'onTap' or 'onChanged' or 'onSelectionChanged'?

## Steps to Reproduce

**Expected results:** 
```
ChoiceChip(
          onChanged: (value) {
        
          },
          label: Text(service),
          selected: true,
        );
```

**Actual results:** 

```
ChoiceChip(
          onSelected: (value) {
        
          },
          label: Text(service),
          selected: true,
        );
```
Repository: vscode
Issue: Disable extension action on setting and make setting read only when it is overridden
Labels: bug,settings-editor

Testing #141320

When I toggle this setting, nothing happens. Maybe when an extension overrides the value of a setting, we should make that checkbox read only?

![Screen Shot 2022-01-25 at 11 33 38 AM](https://user-images.githubusercontent.com/29464607/151028833-365b6fe3-f475-4c4d-b2ff-5c487b1f7c1f.png)

When I right clicked the setting, I expected to be able to disable the extension that is overriding its value. Have there been discussions about that?
Repository: vscode
Issue: Featured extensions on the Marketplace
Labels: under-discussion,marketplace

The VS Marketplace has 6 featured extensions which are shown prominently on the [MP site](https://marketplace.visualstudio.com/). We try to update this list every 1-2 months and we aim to showcase some new and interesting extensions.

So my ask for the community is to share your suggestions on what extension should be featured. Please provide a short reason why you think the extension is interesting.

Keep in mind the following:
* If an extension is suggested to be featured it does not mean we will feature it
* We do not want to feature extensions which have been featured in the past
* We do not want to update the featured list too often
* We do not want to feature extensions which are already popular
Repository: flutter
Issue: Windows tool_integration_tests_2_5 tests flake
Labels: tool,P2,c: flake,team-tool,triaged-tool

(part of https://github.com/flutter/flutter/issues/97036)
These data is based Q4 2021 flakes that happened from 10/01/2021 to 01/13/2022

- [ ] 1 [flutter_adapter_test.dart flake](https://ci.chromium.org/ui/p/flutter/builders/prod/Windows%20tool_integration_tests_2_5/2224/overview)
```
01:09 +3: test\integration.shard\debug_adapter\flutter_adapter_test.dart: can run and terminate a Flutter app in debug mode                                                                            
01:09 +3: test\integration.shard\debug_adapter\flutter_adapter_test.dart: can hot reload                                                                                                               
01:09 +2 -1: test\integration.shard\debug_adapter\flutter_adapter_test.dart: can run and terminate a Flutter app in debug mode [E]                                                                     
  
  
  unparsed  test\integration.shard\debug_adapter\test_server.dart 82:7  new OutOfProcessDapTestServer._.<fn>
  
  This test failed after it had already completed. Make sure to use [expectAsync]
  or the [completes] matcher when testing async code.
  unparsed  test\integration.shard\debug_adapter\test_server.dart 82:7  new OutOfProcessDapTestServer._.<fn>
  
  Oops; flutter has exited unexpectedly: "FileSystemException: writeFrom failed, path = '' (OS Error: The pipe is being closed.
  , errno = 232)".
  
  unparsed  test\integration.shard\debug_adapter\test_server.dart 82:7  new OutOfProcessDapTestServer._.<fn>
```

- [ ] [1 deferred_components_test flake](https://ci.chromium.org/ui/p/flutter/builders/prod/Windows%20tool_integration_tests_2_5/2523/overview)

```
11:18 +18 -1: test\integration.shard\deferred_components_test.dart: simple build appbundle no-deferred-components succeeds [E]                                                                         
  Expected: <true>
    Actual: <false>
  
  package:test_api                                            expect
  test\integration.shard\deferred_components_test.dart 119:5  main.<fn>
```
Repository: vscode
Issue: Auto save behaviour might be unexpected here
Labels: feature-request,debug,polish

Testing #141347

I have auto save enabled. This makes sense when editing files, but feels different when editing memory during debugging.
Repository: deno
Issue: inspector_break_on_first_line_in_test sometimes hangs
Labels: flaky

https://github.com/denoland/deno/runs/4939598278?check_suite_focus=true

https://pipelines.actions.githubusercontent.com/VUhSaxof0o5fzWxZXZdkcOpeiuLaMllr0ELnHiP0l5PjgHedmO/_apis/pipelines/1/runs/29492/signedlogcontent/5?urlExpires=2022-01-25T19%3A28%3A02.7613227Z&urlSigningMethod=HMACV1&urlSignature=L3YCAnRDvaIcjcrbIV7W8YCbc9zYSEOMJbQlIwOyqIU%3D

```
2022-01-25T16:10:41.5597776Z test timerMaxCpuBug ...test integration::inspector::inspector_break_on_first_line_in_test has been running for over 60 seconds
...
2022-01-25T17:34:24.0481508Z ##[error]The operation was canceled.
```
Repository: vscode
Issue: Explore file watcher handling of verbose VS Code CLI commands
Labels: help wanted,debt,macos,engineering,workbench-cli,macos-big-sur

Ref https://github.com/microsoft/vscode/issues/141053

Currently:
- The CLI process on macOS (Big Sur and above) spawns the main process using the `open` command so that VS Code is launched with the correct entitlements.
- the `open` command can only redirect stdout and stderr to files, so we currently create temp files for the `open` command, and then set up file watchers on the CLI process to detect when those files are being written to.
- `code-insiders --status` and `code-insiders --verbose` both require the setup with the file watchers.
- :bug: When the main process exits, the CLI process cancels the filewatching, but the watcher might not have finished reading through the file yet. Therefore, some of the expected output is cut off early at the end.

A mitigation is to add in a timeout so that there is a delay between the main process exiting and the filewatcher being cancelled, but there should be a better way to detect when to stop watching. Actually, the issue reminds me a bit of `flush()` methods in other contexts.
Repository: next.js
Issue: Ensure rewrites, i18n and middleware are working properly with the web server
Labels: Navigation,Runtime

With #33635, we now have a full next server running in the edge runtime. We need to ensure that rewrites, i18n and middleware are working properly with this mode by adding tests.
Repository: vscode
Issue: QuickPick allow the mixing of checkbox items with non-checkbox items
Labels: feature-request,quick-pick

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

I think this only makes sense with the concept of separators to say that a particular group is a "checkbox" group or a normal group.
Repository: vscode
Issue: Support radio buttons in the QuickPick
Labels: feature-request,quick-pick

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
We already support normal checkboxes, we should see what supporting radio buttons would look like.

I'd like to do #141500 before this one though.
Repository: TypeScript
Issue: Inconsistent behaviour when accessing setters between TypeScript (.ts files) and TypeScript in JSDoc.
Labels: Bug,Help Wanted,checkJs

# Bug Report

### 🔎 Search Terms
Most major ones is these but haven't had much luck in finding anyone with the same issue.
- Inconsistent behaviour between Typescript and TypeScript in JSDoc
- Inconsistent behaviour when accessing setters between TypeScript and JSDoc

Could be good to note that I've made an [StackOverflow question](https://stackoverflow.com/questions/70722021/inconsistent-behaviour-when-accessing-setters-between-ts-and-using-ts-in-js). So if you try searching yourself and you find that one, that one was from me.

### 🕗 Version & Regression Information
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about the issue

I tried the following versions:
- v4.6.0-dev.20220125
- v4.5.5
- v4.5.4
- v4.4.4

### ⏯ Playground Link
Since my problem lies in the TypeScript in JSDoc, it will have to be a [repo](https://github.com/DennisSkoko/typescript-problem). But I promise it is very simple.

### 💻 Code

Simple showcase of the problem, please note that this is a JavaScript file:
```javascript
export class Input extends HTMLElement {
  static get observedAttributes() {
    return ['label']
  }

  /**
   * @param {string} text
   */
  set label(text) {
    const span = this.shadowRoot?.querySelector('span')
    if (span) span.textContent = text
  }

  /**
   * @param {'label'} name
   * @param {string | null} _oldValue
   * @param {string | null} newValue
   */
  attributeChangedCallback(name, _oldValue, newValue) {
    this[name] = newValue || '' // Duplicate property 'label' ts(2718)

    // This line works fine but note the `this.label` instead of `this[name]` which I prefer.
    // this.label = newValue || ''
  }
}
```

### 🙁 Actual behavior

Typescript can't seem to recognize that `label` is a setter when using a variable for specifying the property name. My guess is that it is thinks that I'm trying to define a property named `label`.

### 🙂 Expected behavior

I expect no `Duplicare property 'label'`. Reason for expecting this is that I tried converting my file to TypeScript and I received no errors.

They are very similar but the difference is that instead of specifying the parameter types in JSDoc, I did it what we usually do in TypeScript like this (you can find the whole TypeScript file in the repo):

```typescript
attributeChangedCallback(name: 'label', _oldValue: string | null, newValue: string | null) {
  this[name] = newValue || '' // works fine
}
```