sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: FancyZone
Labels: Product-FancyZones,Needs-Triage

### Description of the new feature / enhancement

It would be great if you could scale application windows published on terminal servers (terminal server, citrix, parallels, azure remote desktops, etc.) to zones.

Sorry if this is not the right forum for this request. But I felt the need to ask because I am a big fan of Power Toys. You guys do a fantastic job!!

### Scenario when this would be used?

It's obvious

### Supporting information

_No response_
Repository: vscode
Issue: Opening a folder in `vscode.dev` with a domain (i.e. *.com) as its name through Remote Tunnels returns a “blocked” page
Labels: vscode.dev


Type: <b>Bug</b>

1. Open https://vscode.dev
2. Connect to a Remote Tunnel
3. Attempt to open a folder like `/home/demo/sime.demo.com`
4. Observe the page being blocked
5. Manually change the page URL to add a trailing slash
6. Observe the page loading successfully

VS Code version: Code 1.95.3 (f1a4fb101478ce6ec82fe9627c43efbf9e98c813, 2024-11-13T20:05:02.650Z)
OS version:   
Modes:

System Info: Mozilla/5.0 (iPad; CPU OS 18_1_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.1.1 Mobile/15E148 Safari/604.1Extensions: none
<!-- generated by issue reporter -->
Repository: flutter
Issue: [in_app_purchase_storekit] Make StoreKit2 the default for all supported devices. 
Labels: p: in_app_purchase,package,P2,team-ios,triaged-ios

Once most of the bugs have been ironed out, we should make Storekit 2 APIs default for supported devices. Devices below Mac 10 and ios 15 should continue to use the original storekit api.
Repository: angular
Issue: Improve Lifecycle Hooks Documentation with Expanded Examples and Error Handling
Labels: area: docs

### Describe the problem that you experienced

The documentation provides good insights into lifecycle hooks but lacks depth in certain areas. Key concerns include:

1. Insufficient examples for real-world scenarios (e.g., combining hooks effectively).
2. Limited guidance on debugging errors such as `ExpressionChangedAfterItHasBeenCheckedError`.
3. No recommendations for testing lifecycle hooks.

### Enter the URL of the topic with the problem

https://angular.dev/guide/components/lifecycle

### Describe what you were looking for in the documentation

I was looking for:

1. Clear examples of how to use lifecycle hooks in realistic scenarios.
2. Debugging strategies for common errors (e.g., `ExpressionChangedAfterItHasBeenCheckedError`).
3. A section on testing lifecycle hooks for developers writing unit tests.

### Describe the actions that led you to experience the problem

1. Navigated to the Lifecycle Hooks documentation to understand ngOnChanges and ngOnInit.
2. Attempted to find guidance on debugging `ExpressionChangedAfterItHasBeenCheckedError`.
3. Looked for examples of testing hooks but found none.

### Describe what you want to experience that would fix the problem

To address the gaps, I propose the following:

1. Add detailed examples demonstrating real-world usage for hooks like `ngOnChanges `and `ngAfterViewInit`.
2. Introduce a debugging section for common lifecycle-related errors.
3. Include a section with sample unit tests for lifecycle hooks.

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true
No direct error was caused by this problem, but the lack of debugging guidance for `ExpressionChangedAfterItHasBeenCheckedError` is a significant gap.
```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true
Not applicable for this documentation issue.
```

### Provide any additional information here in as much as detail as you can

```true
Adding examples and debugging guidance will significantly improve the usability of this documentation, helping both novice and advanced developers. Suggestions for debugging errors can also include practical tips like isolating changes to earlier hooks or deferring state changes to subsequent lifecycle phases.
```
Repository: rust
Issue: Compiling `#[derive(Debug)] enum` + `dbg!` is quadratic with enum variants
Labels: I-compiletime,A-macros,T-compiler,C-bug

I tried compiling this code: [lib.rs.zip](https://github.com/user-attachments/files/18032518/lib.rs.zip)

The code above was generated with the following python script:
```python
print(
    """#[derive(Debug)]
pub enum Sprites {"""
)
for i in range(10000):
    print(f"    Sprite{i},")
print(
    """}
pub fn foo() {
   println!("{:?}", Sprites::Sprite1);
}"""
)
```

I then compiled the code with `cargo build --release`. It takes 21.00s to compile on my machine, which is rather slow. It would be nice if it compiled faster.

Note that reducing the number of variants from 10000 to 1000 makes the compilation take only 0.20s to compile on my machine. I suspect that something in the Debug trait impl is taking quadratic time, but only if you actually try to debug-print something.

This issue was discovered by tongke on the rust community discord.

### Meta

`rustc --version --verbose`:
```
rustc 1.83.0 (90b35a623 2024-11-26)
binary: rustc
commit-hash: 90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf
commit-date: 2024-11-26
host: aarch64-apple-darwin
release: 1.83.0
LLVM version: 19.1.1
```
Repository: pytorch
Issue: [CI] Manywheel image should use hash based on `.ci/docker` directory
Labels: module: ci,triaged

The CI docker images use the hash based on `.ci/docker` directory (default param for docker-build-dir [here](https://github.com/pytorch/pytorch/blob/39425feac799905402abe4d15667fa47c344f2d7/.github/workflows/docker-builds.yml#L105)), but the manywheel docker images use the hash based on `.ci/docker/manywheel` directory [here](https://github.com/pytorch/pytorch/blob/39425feac799905402abe4d15667fa47c344f2d7/.github/workflows/build-manywheel-images.yml#L68). 

This is incorrect because [build-manywheel-images.yml](https://github.com/pytorch/pytorch/blob/39425feac799905402abe4d15667fa47c344f2d7/.github/workflows/build-manywheel-images.yml) uses scripts from `.ci/docker/common` and therefore should take into account any changes in that directory as well. This will also ensure that both CI and manywheel docker images have the same tag when any changes are made in `.ci/docker`.

cc @seemethere @malfet @pytorch/pytorch-dev-infra
Repository: pytorch
Issue: [MPS] nansum crashes with scalar input
Labels: module: crash,triaged,module: mps

### 🐛 Describe the bug

The following `test_ops` test crashes on MPS and has been skipped. Checkout the following branch to repro: https://github.com/pytorch/pytorch/pull/142202

`pytest test/test_ops.py -v -k test_out_nansum_mps_float32`

### Versions

Versions of relevant libraries:
[pip3] flake8==6.1.0
[pip3] flake8-bugbear==23.3.23
[pip3] flake8-comprehensions==3.15.0
[pip3] flake8-executable==2.1.3
[pip3] flake8-logging-format==0.9.0
[pip3] flake8-pyi==23.3.1
[pip3] flake8-simplify==0.19.3
[pip3] mypy==1.11.2
[pip3] mypy-extensions==1.0.0
[pip3] numpy==1.26.4
[pip3] optree==0.13.0
[pip3] torch==2.6.0a0+git1841c2c
[conda] numpy 1.26.4 pypi_0 pypi
[conda] optree 0.13.0 pypi_0 pypi
[conda] torch 2.6.0a0+git51e0996 pypi_0 pypi
[conda] torchfix 0.4.0 pypi_0 pypi

cc @kulinseth @albanD @malfet @DenisVieriu97 @jhavukainen
Repository: next.js
Issue: Monorepo build failing after version 15.0.3 onwards
Labels: bug,Output (export/standalone),Module Resolution

### Link to the code that reproduces this issue

https://github.com/t3-oss/create-t3-turbo

### To Reproduce

1. Clone repo and install the deps with `pnpm`
2. Update to version `15.0.2`, build it and it works
OBS: change the root `package.json` to include the build command  to only build nextjs
`"build:next": "CI=true turbo run build -F @acme/nextjs...",`
3. Update to version `15.0.3` or `15.0.4`, build it again and you will see that the external `packages` are not found and the build fails, for example:
```bash
@acme/nextjs:build:    Creating an optimized production build ...
@acme/nextjs:build: Failed to compile.
@acme/nextjs:build:
@acme/nextjs:build: ./src/app/layout.tsx
@acme/nextjs:build: Module not found: Can't resolve '@acme/ui/theme'
@acme/nextjs:build:
@acme/nextjs:build: https://nextjs.org/docs/messages/module-not-found
@acme/nextjs:build:
@acme/nextjs:build: ./src/app/layout.tsx
@acme/nextjs:build: Module not found: Can't resolve '@acme/ui/toast'
@acme/nextjs:build:
@acme/nextjs:build: https://nextjs.org/docs/messages/module-not-found
```

### Current vs. Expected behavior

I expected to build it normally like in the `15.0.2` version

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:03:15 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T6000
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 22.12.0
  npm: 10.9.2
  Yarn: N/A
  pnpm: 9.14.4
Relevant Packages:
  next: 15.0.4 // Latest available version is detected (15.0.4).
  eslint-config-next: N/A
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.6.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Module Resolution, Output (export/standalone), Webpack

### Which stage(s) are affected? (Select all that apply)

next build (local)

### Additional context

_No response_
Repository: deno
Issue: Deno requests env access to unspecified env var
Labels: question

Version: Deno 2.1.2

```ts
import AnthropicBedrock from '@anthropic-ai/bedrock-sdk';

const clientBedrock = new AnthropicBedrock();

async function consecutiveRoles(client: AnthropicBedrock, model = 'anthropic.claude-3-haiku-20240307-v1:0') {
  const response = await client.messages.create({
    max_tokens: 10,
    stream: false,
    messages: [
      { role: 'user', content: 'What is the color of the sky' },
    ],
    model,
  });
  console.log('Response content: ', response.content);
}

await consecutiveRoles(clientBedrock);  // [ { type: 'text', text: 'Blue' } ]
```

Output:

```
$ deno run --env-file --allow-env=ANTHROPIC_*,AWS_*,DEBUG --allow-net bed-deno.ts 
┏ ⚠  Deno requests env access.
┠─ To see a stack trace for this prompt, set the DENO_TRACE_PERMISSIONS environmental variable.
┠─ Learn more at: https://docs.deno.com/go/--allow-env
┠─ Run again with --allow-env to bypass this prompt.
┗ Allow? [y/n/A] (y = yes, allow; n = no, deny; A = allow all env permissions) > 
```

This reproduces without a `.env` file, with an empty one, or with one containing valid AWS_ credentials.

I expected Deno to specify which env var it wants access to, as it does for (most) other environment variables.
Repository: deno
Issue: More BrotliDecompress error info
Labels: node compat,dx

I getting some BrotliDecompress error on several YT clients. It fails somewhere inside deno nodejs compat files.

```ts
import { Innertube } from "npm:youtubei.js";
const yt = await Innertube.create();
```

Error:
```sh
error: Uncaught TypeError: Failed to decompress
    at BrotliDecompress.transform [as _transform] (ext:deno_node/_brotli.js:69:23)
    at BrotliDecompress.Transform._write (ext:deno_node/_stream.mjs:4563:12)
    at writeOrBuffer (ext:deno_node/_stream.mjs:3520:16)
    at _write (ext:deno_node/_stream.mjs:3465:14)
    at BrotliDecompress.Writable.write (ext:deno_node/_stream.mjs:3468:14)
    at Readable.ondata (ext:deno_node/_stream.mjs:2744:26)
    at Readable.emit (ext:deno_node/_events.mjs:393:28)
    at Readable.read (ext:deno_node/_stream.mjs:2597:14)
    at flow (ext:deno_node/_stream.mjs:2933:38)
    at resume_ (ext:deno_node/_stream.mjs:2915:7)
```

deno:  2.1.3
Repository: storybook
Issue: [Bug]: Storybook hangs/doesn't finish building 8.4.6/8.4.7
Labels: bug,has workaround,build-storybook,sev:S2

### Describe the bug

We're using Storybook (with React) in version 8.4.5. I noticed that our Renovate update failed for 8.4.6 and now 8.4.7 as well. I didn't create a bug ticket so far, because I cannot reproduce it locally and only see it in our CI (Gitlab).

I decided to create a ticket now as I was checking if someone else has the same problem, but I couldn't find something related. Maybe it helps someone else to jump into the discussion (and ideally a solution later). (https://github.com/storybookjs/storybook/issues/29715 seems to about a different issue.)

### Reproduction link

#sorry-:-(

### Reproduction steps

_No response_

### System

Storybook in the mentioned versions, Gitlab CI and `$ node -v v22.11.0`.

### Additional context

The last output I get after running `$ storybook build--output-dir storybook` is this:

> Generate File to /builds/xxx/yyy/storybook/meta.json
info => Preview built (1.33 min)
info => Output directory: /builds/xxx/yyy/storybook
attention => Storybook now collects completely anonymous telemetry regarding usage.
This information is used to shape Storybook's roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://storybook.js.org/telemetry

Afterwards my CI job runs into a timeout. As far as

I tried to get more information by using different log levels and --debug, but I couldn't get more information. I will try to debug more and if I find a solution/workaround I will update (and close) this issue.
Repository: vscode
Issue: registerCodeLensProvider
Labels: info-needed,code-lens


Version: 1.95.3 (user setup)
Commit: f1a4fb101478ce6ec82fe9627c43efbf9e98c813
Date: 2024-11-13T14:50:04.152Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.22631


Steps to Reproduce:

1. Installing the register-codelens-provider extension. Please download the extension register-codelens-provider-0.0.1.vsix from https://github.com/1684838553/store.
2. Open the Java file, activate the extension, and display the codelens. The editor starts from the third line of code. When you enter characters, the visible area of the editing area changes.

![Image](https://github.com/user-attachments/assets/881e3119-7686-4d19-ba6b-3f7ad4819f27)

The top of the editing page is displayed from the third line. This problem can be reproduced only after codelens is hidden.
Repository: godot
Issue: Wrong path to cached files in service worker for web export.
Labels: bug,platform:web,topic:buildsystem,topic:export

### Tested versions

- Reproducable in version 4.3 stable

### System information

Mac os Sonoma - Macbook Pro M1 Pro (Apple Silicon)

### Issue description

When exporting with the HTML Web-template, the project produces an service worker with the filename **index.service.worker.js**.
Inside the script is a constant defined as CACHED_FILES. One of those items inside the array is **index.worker.js**

The file index.worker.js does not exist and therefore the PWA register fails in the browser.
When deleting the file in the array, the PWA registers correctly.

I think it should be either index.service.worker.js or completely removed from the array since the browser handles caching of the service worker.

Looks like this in the exported service worker file:
```javascript
// Files that will be cached on load.
/** @type {string[]} */
const CACHED_FILES = ["index.html","index.js","index.offline.html","index.icon.png","index.apple-touch-icon.png","index.worker.js","index.audio.worklet.js"];
``` 

### Steps to reproduce

- Create project
- Download latest export templates
- Export to web

### Minimal reproduction project (MRP)

Since this is about the export templates, project files don't matter.
Repository: vscode
Issue: Support `"regex"` in `"quickSuggestions"`
Labels: feature-request,suggest

I would like `"regex"` to be added to `"editor.quickSuggestions"`

Currently `"editor.quickSuggestions"` supports `"other"`, `"comments"` and `"strings"`
`"regex"` is currently defaulted to `"off"` and cannot be changed
Currently it is impossible to automatically show inline snippet suggestions within regular expressions

```jsonc
"editor.quickSuggestions": {
	"other": "inline",
	"comments": "off",
	"strings": "inline",
	"regex": "inline" // New!
},
```

https://github.com/microsoft/vscode/blob/main/src/vs/editor/common/config/editorOptions.ts#L3502-L3584
https://github.com/microsoft/vscode/blob/main/src/vs/editor/contrib/suggest/browser/suggest.ts#L453-L470
https://github.com/microsoft/vscode/blob/main/src/vs/editor/contrib/suggest/browser/suggestInlineCompletions.ts#L148
Repository: ant-design
Issue: Checkbox 下使用 Typography 无法省略
Labels: Inactive,improvement

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/yu-fa-tang-antd-5-22-3-forked-sl47c6?file=%2Fdemo.tsx%3A8%2C8-8%2C18)

### Steps to reproduce

查看示例

### What is expected?

可以省略

### What is actually happening?

没有省略

| Environment | Info |
| --- | --- |
| antd | 5.22.3 |
| React | latest |
| System | mac |
| Browser | chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: material-ui
Issue: [Dialog] narrator will automatically jump back to dialog content start when navigate to a button in dialog.
Labels: accessibility,component: dialog,package: material-ui

### Search keywords

accesibility narrator dialog button

### Latest version

- [X] I have tested the latest version

### Steps to reproduce

Steps:
1. visit https://mui.com/material-ui/react-dialog/
2. enable Window Narrator
3. enable scan mode
4. use capslock + arrow navigate to any sample open dialog button
5. press enter
6. use capslock + arrow navigate to button in dialog
7. it will jump back to dialog content automatically when focus on the button

### Current behavior

7. it will jump back to dialog content automatically when focus on the button

https://github.com/user-attachments/assets/9f36336c-4e97-478d-9dbf-5caf3a215938


### Expected behavior

7. it should keep focusing on the button but not jump to any other place.

### Context

_No response_

### Your environment

You can reproduce it in the official document website.
Repository: ui
Issue: [bug]: require is not defined while setting up the shadcn-ui with vite.
Labels: bug

### Describe the bug

I am getting an error that `require is not defined while setting up the shadcn-ui with vite.`
PFA
![Screenshot (3)](https://github.com/user-attachments/assets/c1a9478e-c676-4708-aa97-cfab28ec56db)
![Screenshot (4)](https://github.com/user-attachments/assets/ca42eeee-4ce3-4459-ac11-ae15193ea1dc)


### Affected component/components

na

### How to reproduce

setup the shadcn-ui with vite
https://ui.shadcn.com/docs/installation/vite

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
node: v22.12.0
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: deno
Issue: error: [ERR_MODULE_NOT_FOUND] Cannot find module 
Labels: needs info

Version: `Deno 2.1.3`
And I use `fastify` `postgres` `Prisma`

**My massage:**

error: [ERR_MODULE_NOT_FOUND] Cannot find module 'file:///home/raqeb/.cache/deno/npm/registry.npmjs.org/undici-types/6.19.8/dispatcher' imported from 'file:///home/raqeb/.cache/deno/npm/registry.npmjs.org/undici-types/6.19.8/fetch.d.ts'
    at file:///home/raqeb/.cache/deno/npm/registry.npmjs.org/undici-types/6.19.8/fetch.d.ts:10:24
Repository: vscode
Issue: line numbers are not highlighted on the wrapped parts of long lines
Labels: bug,polish,editor-wrapping


Type: <b>Bug</b>

when line warpping is enabled and the cursor is placed on the wrapped portion of the line, the line numbers that usually turn bold to indicate selection are not

![highlight on short line](https://github.com/user-attachments/assets/2e2af4a1-1ab2-470c-924e-fc51c301e4d3)
![highlight on main part of long line](https://github.com/user-attachments/assets/0eeea22f-f20c-4f89-bd6f-0ac188894288)
![no highlight on wrapped part](https://github.com/user-attachments/assets/1694d4b2-454a-44be-941f-0a0cdb2a93d4)


VS Code version: Code 1.95.3 (f1a4fb101478ce6ec82fe9627c43efbf9e98c813, 2024-11-13T14:50:04.152Z)
OS version: Windows_NT x64 10.0.22631
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz (16 x 2904)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|15.72GB (4.33GB free)|
|Process Argv|--crash-reporter-id f1ede49c-e57c-4921-bbff-13fec967fa80|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (2)</summary>

Extension|Author (truncated)|Version
---|---|---
git-graph|mhu|1.30.0
remote-ssh|ms-|0.115.1


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
vscaac:30438847
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
jg8ic977:31013176
dvdeprecation:31068756
dwnewjupytercf:31046870
impr_priority:31102340
nativerepl1:31139838
pythonrstrctxt:31112756
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
j44ff735:31181874

```

</details>

<!-- generated by issue reporter -->
Repository: puppeteer
Issue: [Feature]: new deprecations should show up in the changelog
Labels: feature,good first issue,P3

### Feature description

currently, if the depreciation happens as the part of the `docs:` change, it will not be reflected in the changelog because all `docs:` changes are excluded. At the same time, deprecations are neither fixes or features. Perhaps, we need to find a way to automatically get the list of new deprecated APIs for each release.
Repository: vscode
Issue: `IgnoreFile` compares file paths in a case-sensitive way on windows/macOS
Labels: bug,search

`IgnoreFile` checks if a path belongs to a folder in the following way:

`if (!path.startsWith(dirPath)) { return false; }`

This does not take into account that paths are not case-sensitive on windows and macOS. Should it?

https://github.com/microsoft/vscode/blob/f9ec787a7770b07b72b76e8dbdd56ef949fa2f70/src/vs/workbench/services/search/common/ignoreFile.ts#L117-L125
Repository: vscode
Issue: Color Picker shows in comments for github issue numbers
Labels: polish,under-discussion,editor-color-picker

![Image](https://github.com/user-attachments/assets/89b118ce-645f-416b-ae09-e008404f26f7)

Are we able to tell if the HEX code is located inside a comment? If so, could we not show the color picker in that case?