sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: [Bug]: npx sb@latest upgrade unpins pinned dependencies
Labels: bug,cli,sev:S2

### Describe the bug

If you have pinned dependencies in `package.json`
```json
"@storybook/addon-essentials": "8.1.5",
"@storybook/addon-interactions": "8.1.5",
"@storybook/addon-links": "8.1.5",
"@storybook/blocks": "8.1.5",
"@storybook/preview-api": "8.1.5",
"@storybook/react": "8.1.5",
"@storybook/react-vite": "8.1.5",
"@storybook/test": "8.1.5",
"@storybook/theming": "8.1.5",
"@storybook/types": "8.1.5",
"storybook": "8.1.5",
```
When `npx sb@latest upgrade` is run, the dependencies should remain pinned.
```json
"@storybook/addon-essentials": "8.2.2",
"@storybook/addon-interactions": "8.2.2",
"@storybook/addon-links": "8.2.2",
"@storybook/blocks": "8.2.2",
"@storybook/preview-api": "8.2.2",
"@storybook/react": "8.2.2",
"@storybook/react-vite": "8.2.2",
"@storybook/test": "8.2.2",
"@storybook/theming": "8.2.2",
"@storybook/types": "8.2.2",
"storybook": "8.2.2",
```
But it currently adds a `^` caret before the version:
```json
"@storybook/addon-essentials": "^8.2.2",
"@storybook/addon-interactions": "^8.2.2",
"@storybook/addon-links": "^8.2.2",
"@storybook/blocks": "^8.2.2",
"@storybook/preview-api": "^8.2.2",
"@storybook/react": "^8.2.2",
"@storybook/react-vite": "^8.2.2",
"@storybook/test": "^8.2.2",
"@storybook/theming": "^8.2.2",
"@storybook/types": "^8.2.2",
"storybook": "^8.2.2",
```

### Reproduction link

https://storybook.js.org/docs/configure/upgrading

### Reproduction steps

1. Pin dependencies in package.json with previous version of storybook
2. Run `npx sb@latest upgrade`

### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 14.5
    CPU: (12) arm64 Apple M2 Pro
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.11.0 - ~/.nvm/versions/node/v20.11.0/bin/node
    npm: 10.8.1 - ~/.nvm/versions/node/v20.11.0/bin/npm <----- active
    pnpm: 8.1.0 - ~/.nvm/versions/node/v20.11.0/bin/pnpm
  Browsers:
    Chrome: 126.0.6478.127
    Safari: 17.5
  npmPackages:
    @storybook/addon-essentials: 8.2.2 => 8.2.2 
    @storybook/addon-interactions: 8.2.2 => 8.2.2 
    @storybook/addon-links: 8.2.2 => 8.2.2 
    @storybook/blocks: 8.2.2 => 8.2.2 
    @storybook/preview-api: 8.2.2 => 8.2.2 
    @storybook/react: 8.2.2 => 8.2.2 
    @storybook/react-vite: 8.2.2 => 8.2.2 
    @storybook/test: 8.2.2 => 8.2.2 
    @storybook/theming: 8.2.2 => 8.2.2 
    @storybook/types: 8.2.2 => 8.2.2 
    chromatic: 11.5.5 => 11.5.5 
    eslint-plugin-storybook: 0.8.0 => 0.8.0 
    storybook: 8.2.2 => 8.2.2 
    storybook-dark-mode: 4.0.2 => 4.0.2 
    storybook-react-i18next: 3.1.1 => 3.1.1
```


### Additional context

_No response_
Repository: next.js
Issue: Unnecessary styles for multi tenant style app
Labels: bug,Webpack,Lazy Loading

### Link to the code that reproduces this issue

https://github.com/G3EORG3E/multi-tenant

### To Reproduce

1. build app
2. start app
3. see that resulting styles for page includes also styles of components that is not rendered in page

### Current vs. Expected behavior

I am trying to implement multi tenant app. And each app instance can have different component depending on its configured theme. For example we can see I have a parent `<Header/>` server component that imports `<MinimalisticHeader/>` and `<ModernHeader/>` and decides which component to render depending on app theme.

Currently the page includes styles of both `<MinimalisticHeader/>` and `<ModernHeader/>` but only `<ModernHeader/>` is rendered in server component.

I would expect that the page would have styles only for components that are actually rendered in server component (at least when they are dynamically imported there) otherwise its not possible to build such apps with Next.js, its unacceptable to have styles for every theme loaded.

Edit: Additionally, I observed that the client components are also being added to the bundle. A mechanism to prevent this inclusion is necessary. This is unusable for bigger more complex apps.

### Provide environment information

```bash
Not related to environment
```


### Which area(s) are affected? (Select all that apply)

Lazy Loading, Webpack

### Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local)

### Additional context

_No response_
Repository: vscode
Issue: Wrong syntax coloring in PHP with string 'AND ['
Labels: bug,grammar

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.92.0-insider (user setup)
Commit: a35380d6f0ff65f7c35345baafcf1c3f8a378d38
Date: 2024-07-12T05:08:08.550Z
Electron: 30.1.2
ElectronBuildId: 9759760
Chromium: 124.0.6367.243
Node.js: 20.14.0
V8: 12.4.254.20-electron.0
- OS Version:  Windows_NT x64 10.0.22631

Steps to Reproduce:
1. I use insider build fresh installed, no changes
2. Use this code

```
<?php

$value = ' ANDRE [' . $test . ']';

echo 'abc';
$value = ' AND [' . $test;
$value = ' AND [' . $test . ']';
$value = ' AND [' . $test[1] . ']';

$value = ' ANDRE [' . $test . ']';

```
Shows in VSCode Inside and v1.91.1 this:
![image](https://github.com/user-attachments/assets/29252fd7-10fa-4614-9a8e-e9be4f555851)

php sandbox
![image](https://github.com/user-attachments/assets/1079c8ce-0114-435c-9d34-921f893a4663)

In vscode is a issue with string "AND ["?

EDIT: For clarification; Its "AND" with "[" in a string. This also applies to something like this:
" AND abc [ abc"
but this line shows correct coloring, if something comes before "AND" 
"abc AND abc [ abc"
Repository: TypeScript
Issue: RangeError: Maximum call stack size in getTypeAtLocation in files importing in series with template literals
Labels: Bug

### 🔎 Search Terms

getTypeAtLocation getTypeOfNode checkNonNullExpression

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about type checking and APIs

### ⏯ Playground Link

https://github.com/JoshuaKGoldberg/repros/blob/typescript-eslint-rangeerror-170

### 💻 Code

Files are set up in a singly linked list of `export`s and `import`s.
Within each case:

- `src/index.ts` imports a `pipe0` function from `src/pipe0.ts`
- `src/pipe0.ts` imports a `pipe1` function from `src/pipe1.ts`
- ...
- The last pipe file `N` exports a `pipe${N}` function

[typescript-eslint's typed linting](https://typescript-eslint.io/getting-started/typed-linting) is then run on the `src/` directory.

### 🙂 Expected behavior

Types should be retrieved successfully at scales of 100+ files importing in a row _and_ using template literal expressions.

### 🙁 Actual behavior

```plaintext
Oops! Something went wrong! :(

ESLint: 9.6.0

RangeError: Maximum call stack size exceeded
Occurred while linting /repros/cases/files-170-types-project/src/pipe0.ts:5
Rule: "@typescript-eslint/no-unsafe-return"
    at checkTemplateExpression (/repros/node_modules/typescript/lib/typescript.js:82916:11)
    at checkExpressionWorker (/repros/node_modules/typescript/lib/typescript.js:83375:16)
    at checkExpression (/repros/node_modules/typescript/lib/typescript.js:83303:32)
    at checkNonNullExpression (/repros/node_modules/typescript/lib/typescript.js:77538:29)
    at checkPropertyAccessExpression (/repros/node_modules/typescript/lib/typescript.js:77617:162)
    at checkExpressionWorker (/repros/node_modules/typescript/lib/typescript.js:83383:16)
    at checkExpression (/repros/node_modules/typescript/lib/typescript.js:83303:32)
    at resolveCallExpression (/repros/node_modules/typescript/lib/typescript.js:79548:20)
    at resolveSignature (/repros/node_modules/typescript/lib/typescript.js:79997:16)
    at getResolvedSignature (/repros/node_modules/typescript/lib/typescript.js:80023:18)
    ...
```

### Additional information about the issue

Running `tsc` on the CLI works just fine at this scale. It's the type checker API that's crashing.

https://github.com/JoshuaKGoldberg/repros/blob/typescript-eslint-rangeerror-170/README.md#full-error-stack contains the full error stack. Looking at the last lines in it (the first functions called):

* The first TypeScript API called is `getTypeAtLocation`, and it only shows up once
* The next few APIs called are also only called once: `getTypeOfNode`, `getRegularTypeOfExpression`, `checkNonNullExpression`
* `checkExpression` is called around 875+ times

Also copying from https://github.com/JoshuaKGoldberg/repros/blob/typescript-eslint-rangeerror-170/README.md#testing-notes:
* Tested on TypeScript 4.7.3, 5.1.3, and 5.3.3: all reproduce the issue.
* Avoiding template literal strings fixes the errors.
Repository: vscode
Issue: Copy paste indent
Labels: bug,editor-autoindent


Type: <b>Feature Request</b>

Copy pasting code breaks the indentation. Every time I have to copy and paste a block, I'm spending precious flow-breaking moments reformatting the pasted code, because VSCode cannot retain the correct indentation. Take a look at how Sublime does it. I can focus on work, not hitting tab and backspace a bunch of times just because the editor cannot do it.

VS Code version: Code 1.91.1 (f1e16e1e6214d7c44d078b1f0607b2388f29d729, 2024-07-09T22:06:49.809Z)
OS version: Windows_NT x64 10.0.19045
Modes:


<!-- generated by issue reporter -->
Repository: PowerToys
Issue: Change log file extension
Labels: Idea-Enhancement,Status-In progress,Area-Logging

### Description of the new feature / enhancement

Instead of the current `.txt` extension for log files, I'd like to move it to `.log`. This allows for user-defined file associations to be honored, such as CMTrace. It will also automatically enable syntax highlighting in VSCode.

### Scenario when this would be used?

For all logs generated by PowerToys.

### Supporting information

![image](https://github.com/user-attachments/assets/f5138efd-9493-43cb-97b3-7ea39773b2fe)
Repository: PowerToys
Issue: MWB - Failed to read settings: The process cannot access the file 'FILE.json' because it is being used by another process errors in Event Viewer
Labels: Issue-Bug,Needs-Triage,Needs-Team-Response,Product-Mouse Without Borders

### Microsoft PowerToys version

0.82.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

For MWB, I am seeing an average of 150 Errors a day in the event event viewer. 

The errors are always the same:

Failed to read settings: The process cannot access the file 'C:\Users\USER\AppData\Local\Microsoft\PowerToys\MouseWithoutBorders\settings.json' because it is being used by another process.

Note: I do see 2 process named Powertoys.MouseWithoutBNorders running simultaneously in Task Manager. 

As far as I know, It's not affecting the usability of Mouse Without Borders. But I've been getting some system crashes from time to time. Not sure if it's related. That's why I went into my event viewer to look for a anything. The amount of MWB Errors stood out.  

### ✔️ Expected Behavior

Not having 150 errors a day in event viewer

### ❌ Actual Behavior

Having 2500 Errors in 17 days since I installed PowerToys

### Other Software

_No response_
Repository: pytorch
Issue: [Bug Report] Choosing the network interface to use
Labels: oncall: distributed,triaged

https://github.com/pytorch/pytorch/blob/6f54e961eaffd323ef31b88bf2cfa170f589ddbc/torch/csrc/distributed/rpc/tensorpipe_agent.cpp#L30

https://pytorch.org/docs/stable/distributed.html#common-environment-variables

seems there are some issues in the comment and document, I can't use the NCCL_SOCKET_IFNAME / GLOO_SOCKET_IFNAME to specify the interfaces.

the code shows only TP_SOCKET_IFNAME can.

cc @XilunWu @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o
Repository: godot
Issue: Vibration not working with Google Stadia controller
Labels: bug,topic:input

### Tested versions

v4.2.2.stable.official [15073afe3]

### System information

Godot v4.2.2.stable - Ubuntu 22.04.4 LTS 22.04 - Wayland - Vulkan (Forward+) - integrated AMD Unknown (RADV RENOIR) () - AMD Ryzen 7 4800U with Radeon Graphics (16 Threads)

### Issue description

When trying to use Input.start_joy_vibration() to trigger vibrations/rumble for my (bluetooth connected) Google Stadia controller it doesn't seem to do anything.

I've tried different values but I couldn't get any vibrations working, the controller works just fine for all other input.
In my MRP I've linked the vibration call to a button but it doesn't work either when used in other functions like _physics_process().

### Steps to reproduce

- Connect Stadia controller using bluetooth
- Map one of the controller buttons to ui_menu in the input map(ui_menu can be found in built-in actions)
- Make a Node2D root node and add the MRP as a script to this node
- Start a game and press the button a few times and notice it does not make the controller rumble

### Minimal reproduction project (MRP)

```gdscript
extends  Node2D

func _input(_event):
	if Input.is_action_pressed("ui_menu"):
		Input.start_joy_vibration(0, 1, 1, 100)
```
Repository: go
Issue: runtime: findrunnableGCWorker consumed much higher CPU under 64c AWS instance (ARM64), comparing to 32c
Labels: Performance,NeedsInvestigation,compiler/runtime,Scalability

### Go version

go1.19.13 linux/arm64

### Output of `go env` in your module/workspace:

```shell
GOARCH="arm64"
```


### What did you do?

* We put one binary (developed/compiled by golang) in an AWS EKS instance, it runs as a gRpc server.
* Lately we changed this instance type, increasing CPU cores from 32c to 64c.

### What did you see happen?

* We found that this process had much higher P999 latency comparing to previous.
* From flame graph, We found out `findrunnableGCWorker` consumed much higher CPU comparing to previous.

Here are the graphs:
* ARM64 32c:
![20240712-220344](https://github.com/user-attachments/assets/8c3d4fd9-e9d6-404f-9223-aced7b1432ea)
* ARM64 64c:
![20240712-220359](https://github.com/user-attachments/assets/105b9863-bdac-4fc5-bbad-4405e15a889c)

### What did you expect to see?

The latency of this server process shouldn't change much when we changed from 32c instance to 64c instance.
Repository: flutter
Issue: Fix and re-enable rfw tests
Labels: a: tests,package,team-ecosystem,P1,c: disabled test,p: rfw,triaged-ecosystem

They were disabled in https://github.com/flutter/tests/pull/386 for https://github.com/flutter/flutter/issues/151611.
Repository: deno
Issue: test: `--doc` and `--watch` don't play well together
Labels: bug,testing

Version:

```txt
deno 1.45.1 (release, aarch64-apple-darwin)
v8 12.7.224.12
typescript 5.5.2
```

README.md:

````md
# demo

## Example

```ts
console.log("Hello world");
```
````

Demo:

```console
% deno test --doc --watch | pbcopy
Watcher Test started.
error: The module's source code could not be parsed: Expected ident at file:///path/to/README.md:3:2

  ## Example
   ~
Watcher Test failed. Restarting on file change...
```

It looks to me as if `--watch` is not accounting for watching code blocks in Markdown.
Repository: vscode
Issue: [File Watcher (node.js)] Error: ENAMETOOLONG: name too long
Labels: bug,typescript,file-watcher

See this in the console of insiders.. Looks like some ad-hoc chat model is ending up being file watched

```
ERR [File Watcher (node.js)] Error: ENAMETOOLONG: name too long, stat '/^/vscode-copilot-chat-code-block/4b3e2ea8-fd64-4d09-b875-d9770d5e94d4/response_0/0#{"references":[{"uri":{"$mid":1,"fsPath":"/Users/jrieken/Code/vscode/src/vs/workbench/contrib/inlineChat/browser/inlineChatNotebook.ts","external":"file:/Users/jrieken/Code/vscode/src/vs/workbench/contrib/inlineChat/browser/inlineChatNotebook.ts","path":"/Users/jrieken/Code/vscode/src/vs/workbench/contrib/inlineChat/browser/inlineChatNotebook.ts","scheme":"file"},"range":{"startLineNumber":21,"startColumn":3,"endLineNumber":21,"endColumn":72}},{"uri":{"$mid":1,"fsPath":"/Users/jrieken/Code/vscode/src/vs/workbench/api/browser/mainThreadWorkspace.ts","external":"file:/Users/jrieken/Code/vscode/src/vs/workbench/api/browser/mainThreadWorkspace.ts","path":"/Users/jrieken/Code/vscode/src/vs/workbench/api/browser/mainThreadWorkspace.ts","scheme":"file"},"range":{"startLineNumber":1,"startColumn":1,"endLineNumber":297,"endColumn":1}},{"uri":{"$mid":1,"fsPath":"/Users/jrieken/Code/vscode/src/vs/workbench/api/common/extHostWorkspace.ts","external":"file:/Users/jrieken/Code/vscode/src/vs/workbench/api/common/extHostWorkspace.ts","path":"/Users/jrieken/Code/vscode/src/vs/workbench/api/common/extHostWorkspace.ts","scheme":"file"},"range":{"startLineNumber":238,"startColumn":1,"endLineNumber":250,"endColumn":3}},{"uri":{"$mid":1,"fsPath":"/Users/jrieken/Code/vscode/src/vs/workbench/browser/web.main.ts","external":"file:/Users/jrieken/Code/vscode/src/vs/workbench/browser/web.main.ts","path":"/Users/jrieken/Code/vscode/src/vs/workbench/browser/path/to/inlineChatSessionService'
```
Repository: pytorch
Issue: Size-like unbacked symbol whose upper bound < 2 causes problems for nonzero
Labels: triaged,oncall: pt2,module: dynamic shapes

### 🐛 Describe the bug

https://github.com/pytorch/pytorch/pull/130440  updates `torch.nonzero` to now produce an output with strides containing unbacked symints. When nonzero is called with an input with numel == 1, its unbacked symint has an upperbound of 1. The error happens when we later do a elementwise operation which performs a size_oblivious guard.

Repro when linked PR checked out. 
```python
import torch

def fn(x):
    nz = torch.nonzero(x)  # introduce unbacked symint
    squared = nz * nz

with torch._dynamo.config.patch({"capture_dynamic_output_shape_ops": True}):
    example_inputs = (torch.randn(1, 1, 1, 1),)
    actual = torch.compile(fn, fullgraph=True, backend="aot_eager")(*example_inputs)
    expected = fn(*example_inputs)

```
```
  File "/data/users/jw3468/a/pytorch/torch/_prims/__init__.py", line 386, in _prim_elementwise_meta
    l2p_perm = utils.compute_elementwise_output_logical_to_physical_perm(*args_)
  File "/data/users/jw3468/a/pytorch/torch/_prims_common/__init__.py", line 504, in compute_elementwise_output_logical_to_physical_perm
    comparison = should_swap(perm[dim0], perm[dim1])
  File "/data/users/jw3468/a/pytorch/torch/_prims_common/__init__.py", line 481, in should_swap
    if guard_size_oblivious(stride_a > stride_b):
  File "/data/users/jw3468/a/pytorch/torch/fx/experimental/symbolic_shapes.py", line 248, in guard_size_oblivious
    return expr.node.guard_size_oblivious("", 0)
  File "/data/users/jw3468/a/pytorch/torch/fx/experimental/sym_node.py", line 460, in guard_size_oblivious
    r = self.shape_env.evaluate_expr(
  File "/data/users/jw3468/a/pytorch/torch/fx/experimental/recording.py", line 245, in wrapper
    return fn(*args, **kwargs)
  File "/data/users/jw3468/a/pytorch/torch/fx/experimental/symbolic_shapes.py", line 5145, in evaluate_expr
    return self._evaluate_expr(orig_expr, hint, fx_node, expect_rational, size_oblivious, forcing_spec=forcing_spec)
  File "/data/users/jw3468/a/pytorch/torch/fx/experimental/symbolic_shapes.py", line 5227, in _evaluate_expr
    assert static_expr == hint, f"{static_expr} != {hint}"
torch._dynamo.exc.TorchRuntimeError: Failed running call_function <built-in function mul>(*(FakeTensor(..., size=(u0, 4), dtype=torch.int64), FakeTensor(..., size=(u0, 4), dtype=torch.int64)), **{}):
True != False

```

The following comment seems related:
https://github.com/pytorch/pytorch/blob/d443fbc025ae7974877431e3caced747c5551820/torch/fx/experimental/symbolic_shapes.py#L4511-L4514

### Versions

https://github.com/pytorch/pytorch/pull/130440 

cc @ezyang @anijain2305 @chauhang @penguinwu
Repository: terminal
Issue: Scroll up/down (SU/SD) don't copy wide glyph padding spaces
Labels: Area-Output,Issue-Bug,Product-Terminal,Priority-3

### Windows Terminal version

_No response_

### Windows build number

_No response_

### Other Software

_No response_

### Steps to reproduce

* pwsh
  ```pwsh
  "`e[?1049h`e[Hbefore scroll`e[999C`e[2Dfoo`r`n`e[999C`e[2D✨✨"; sleep 1; "`e[S`e[Hafter scroll "; sleep 3; "`e[?1049l"
  ```
* bash
  ```sh
  printf "\e[?1049h\e[Hbefore scroll\e[999C\e[2Dfoo\r\n\e[999C\e[2D✨✨"; sleep 1; printf "\e[S\e[Hafter scroll "; sleep 3; printf "\e[?1049l"
  ```

### Expected Behavior

![image](https://github.com/user-attachments/assets/1513e270-92d7-4980-9977-a5334ec088ef)

### Actual Behavior

![image](https://github.com/user-attachments/assets/0605aa49-3673-434a-bfb2-a263b2b5255d)

The fundamental problem is that `ROW::CopyFrom` doesn't clear to the end of the line (like CSI K).