sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Highlighted line in terminal moving with resizing the window
Labels: bug,confirmed,terminal-rendering


Type: <b>Bug</b>

When I highlight a line printed in the terminal and then resize the terminal window, the selected line moves up and down along the resizing, changing the selected line. 

VS Code version: Code 1.94.2 (Universal) (384ff7382de624fb94dbaf6da11977bba1ecd427, 2024-10-09T16:08:44.566Z)
OS version: Darwin arm64 23.6.0
Modes:

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

|Item|Value|
|---|---|
|CPUs|Apple M1 Pro (8 x 2400)|
|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>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|3, 3, 3|
|Memory (System)|16.00GB (0.05GB free)|
|Process Argv|--crash-reporter-id 4f2899d4-95f0-49d7-9a3b-f8229a52caf2|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (21)</summary>

Extension|Author (truncated)|Version
---|---|---
csdevkit|ms-|1.14.14
csharp|ms-|2.55.29
vscode-dotnet-runtime|ms-|2.2.3
debugpy|ms-|2024.12.0
python|ms-|2024.20.0
vscode-pylance|ms-|2024.12.1
jupyter|ms-|2024.9.1
jupyter-keymap|ms-|1.1.2
jupyter-renderers|ms-|1.0.19
vscode-jupyter-cell-tags|ms-|0.1.9
vscode-jupyter-slideshow|ms-|0.1.6
fabric8-analytics|red|0.9.5
java|red|1.37.0
intellicode-api-usage-examples|Vis|0.2.9
vscodeintellicode|Vis|1.3.2
vscode-gradle|vsc|3.16.4
vscode-java-debug|vsc|0.58.1
vscode-java-dependency|vsc|0.24.1
vscode-java-pack|vsc|0.29.0
vscode-java-test|vsc|0.43.0
vscode-maven|vsc|0.44.0


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

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
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
945dj816:31013170
dvdeprecation:31068756
dwnewjupytercf:31046870
nativerepl1:31139838
pythonrstrctxt:31112756
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530

```

</details>

<!-- generated by issue reporter -->
Repository: godot
Issue: _input: No InputEventMouse after click and drag when mouse is outside game window in the first window focus
Labels: bug,topic:porting,topic:input,topic:gui

### Tested versions

Reproducible in: v4.4.dev6.official [1f47e4c4e], v4.3.stable.official [77dcf97d8]

### System information

Godot v4.4.dev6 - Windows 10.0.19045 - Multi-window, 2 monitors - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1660 SUPER (NVIDIA; 31.0.15.3713) - AMD Ryzen 5 3600 6-Core Processor (12 threads)

### Issue description

Any mouse interaction outside the game window will correctly not fire any `InputEventMouse`. But if the user clicks and drags something inside the window, an `InputEventMouse` is always fired, even when the mouse leaves the window, which is to be expected.
https://github.com/user-attachments/assets/b690596e-b2de-4e1b-8f53-249ef093cd54
Code in this example:
```gdscript
var pressed: bool

func _input(event: InputEvent) -> void:
	if event is InputEventMouseButton:
		if event.button_index == MOUSE_BUTTON_LEFT:
			pressed = event.pressed
			print(pressed)
	if pressed:
		$Icon.global_position = get_global_mouse_position()
```

However, if the window is not focused _before_ the click and drag, no `InputEventMouse` is fired when the mouse leaves the window.
This can lead to an unexpected situation when a user clicks inside and releases outside the window; Since no `InputMouseEventButton` is fired outside the window, `pressed` is never updated.
https://github.com/user-attachments/assets/de45b373-b411-46c0-8f4e-c8f971094df5

As a workaround, you can do your mouse logic inside `_process` instead of `_input`.
```gdscript
func _process(_delta: float) -> void:
	if Input.is_mouse_button_pressed(MOUSE_BUTTON_LEFT):
		$Icon.global_position = get_global_mouse_position()
```

### Steps to reproduce

- Add this snippet into any script:
```gdscript
func _input(event: InputEvent) -> void:
	print(event)
```
- Run the project and see that if the window is not focused before, clicking and dragging does not fire any `InputMouseEvent` when the mouse is outside the window.

### Minimal reproduction project (MRP)

[MouseEventOutsideWindowBug.zip](https://github.com/user-attachments/files/18094418/MouseEventOutsideWindowBug.zip)
Repository: godot
Issue: Web builds with Scenes containing a SubViewportContainer lead to "WebGL context lost" errors on iOS Devices
Labels: bug,platform:web,platform:ios,topic:rendering,topic:porting,needs testing

### Tested versions

- Reproducible in 4.3 stable and 4.4-dev*
- Tested on iPhones and iPads running iOS Version 17 and 18
- Behaves the same on all Browsers

### System information

Godot v4.3.stable - Windows 10.0.22631 - GLES3 (Compatibility) - NVIDIA GeForce RTX 3060 (NVIDIA; 32.0.15.6094) - 13th Gen Intel(R) Core(TM) i7-13700K (24 Threads)

### Issue description

Browsers on iOS Devices stop with a generic "OpenGL context lost" error when running a Web build with a SubViewportContainer in it.


### Steps to reproduce

- open attached MRP or create a new Project containing a Scene with a SubViewportContainer
- build to Web
- open in any Broswer on iOS

### Minimal reproduction project (MRP)

[ios-wasm-bug.zip](https://github.com/user-attachments/files/18094598/ios-wasm-bug.zip)
Repository: react
Issue: Bug: Updating state during render when using `useSyncExternalStore` throws `Cannot update a component (Component) while rendering a different component (Component)`
Labels: Status: Unconfirmed

React version: 19.0.0

## Steps To Reproduce

1. Open the Console before you work with the page
2. Click the "increment" button 5 times
3. You will see the error in the Console

Link to code example:

https://codesandbox.io/p/sandbox/polished-wind-d9dyvj

## The current behavior

When updating the store it throws `Cannot update a component (`Component`) while rendering a different component (`Component`)`.

## The expected behavior

It should work the same way `useState` works when calling `setState` during render.

## Notes

This is coming from a user of `use-local-storage-state` hook that has around ~500k monthly downloads — https://github.com/astoilkov/use-local-storage-state/issues/77.
Repository: PowerToys
Issue: MWB: Delete Device
Labels: Idea-Enhancement,Needs-Triage,Product-Mouse Without Borders

### Description of the new feature / enhancement

Can you please add a feature to delete a device from MWB?

### Scenario when this would be used?

I used to have three computers. I removed one. I should be able to remove that device from MWB as well, since connecting to that device no longer needed.

### Supporting information

_No response_
Repository: pytorch
Issue: DISABLED test_flip_cpu (__main__.CpuTests)
Labels: triaged,module: flaky-tests,module: macos,skipped,oncall: pt2,module: inductor,oncall: cpu inductor

Platforms: mac, macos

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_flip_cpu&suite=CpuTests&limit=100) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/34233139841).

Over the past 3 hours, it has been determined flaky in 6 workflow(s) with 12 failures and 6 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_flip_cpu`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.


Test file path: `inductor/test_torchinductor.py`

cc @ezyang @gchanan @zou3519 @kadeng @msaroufim @clee2000 @wdvr @malfet @albanD @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @muchulee8 @ColinPeppler @amjames @desertfire @aakhundov
Repository: storybook
Issue: [Bug]: Focused Test results leak to global results
Labels: bug,sev:S2,addon: test

When running Focused Tests and they _pass_, the global Testing Module UI will show Component Tests as passing/green, even though there are still failing tests other places. (The reverse is probably also true)

https://github.com/user-attachments/assets/5ebab7b5-476f-4201-8a2f-fc97c299af97
Repository: create-react-app
Issue: web-vital.js compatibility issue <with solution>
Labels: needs triage,issue: bug report

# step 1: Run
```bash
npm install web-vitals@latest
```

I found the web-vitals have changed its export variables; resulting in a web-vital.js crash with the latest updates.


# Step 2: change the file "reportWebVitals"

```typscript
// reportWebVitals.ts
import { onCLS, onFCP, onLCP, onTTFB } from 'web-vitals';

const reportWebVitals = (onPerfEntry?: (metric: any) => void) => {
  if (onPerfEntry && typeof onPerfEntry === 'function') {
    onCLS(onPerfEntry);
    onFCP(onPerfEntry);
    onLCP(onPerfEntry);
    onTTFB(onPerfEntry);
  }
};

export default reportWebVitals;
```
The code above would resolve the web-vitals issues with the latest update.
Repository: three.js
Issue: For reference: glTF Extension `KHR_gaussian_splatting` for 3DGS scene representation
Labels: Loaders

### Description

Following thread https://github.com/NASA-AMMOS/3DTilesRendererJS/issues/863 I just opened, @gkjohnson suggested I should cross-post it directly on the three.js repo. Feel free to close this and anyone interested can watch the universal splat thread instead - link [below](https://github.com/mkkellogg/GaussianSplats3D/issues/47) - since this 3DGS feature might be out-of-scope for the threejs library at the moment. 



### Solution

Here https://github.com/mkkellogg/GaussianSplats3D/issues/47 is a mega discussion regarding a universal gaussian-splat format, with a lot of great takes and mentions - mostly regarding compression, like Niantic SPZ, and standardization. 

An interesting recent [comment](https://github.com/mkkellogg/GaussianSplats3D/issues/47#issuecomment-2532791378) by lilleyse (Cesium team member) redirects to the draft [KHR_gaussian_splatting](https://github.com/CesiumGS/glTF/tree/proposal-KHR_gaussian_splatting/extensions/2.0/Khronos/KHR_gaussian_splatting) glTF extension as well as an implementation within CesiumJS in the experimental [splat-shader branch](https://github.com/CesiumGS/cesium/tree/splat-shader). This extension adds `_ROTATION` and `_SCALE` attributes to a glTF `POINTS`, so these can be used to represent a gaussian-splat scene. If or once that standard settles and makes its way to official KHR_extension, it would be uesful for threejs to interpret this extension and give access to these extra attributes. 

The Cesiumjs implementation extends that `KHR_gaussian_splatting` extension to a HLOD (Hierarchical LoD) tileset container of mesh scenes, OGC-3D-tiles, where every leaf node tile is a glTF scene that supports that gaussian-splat extension. 

### Alternatives

CesiumJS viewer will probably be the first reference implementation for that `KHR_gaussian_splatting extension + OGC-3D-tiles` 

### Additional context

Following the original release of the [3DGS paper](https://repo-sam.inria.fr/fungraph/3d-gaussian-splatting/) by INRIA team at SIGGRAPH 2023, there have been multiple JS renderers and viewers implemented, some based on threejs like [mkkellogg/GaussianSplats3D ](https://github.com/mkkellogg/GaussianSplats3D/) and some others which aren't, eg [antimatter15/splat](https://github.com/antimatter15/splat) [lumalabs](https://lumalabs.ai/luma-web-library) or [babylonjs](https://forum.babylonjs.com/t/gaussian-splatting-in-babylon-js/45027).
Repository: react
Issue: Bug: "reject is not a function" in react-server
Labels: Status: Unconfirmed

We've been investigating a `t is not a function` error in production logs of our Next.js application. After some digging, we found that the `t` corresponds to `reject` in [react-server/src/ReactFlightReplyServer.js:166](https://github.com/facebook/react/blob/79ddf5b574db085104d917c24a964cbd5b824e09/packages/react-server/src/ReactFlightReplyServer.js#L166).   

The error is our case appears when someone (likely a bot) sends a POST request to a server action, as if it was submitting a form on our page, but it sends the JSON values for `$ACTION_1:0` and `$ACTION_1:1` with the quotation marks encoded as HTML entities (probably this is the trigger for the error, could be something with newline characters though, not sure). 

React version: 19.0.0-rc.1

## Steps To Reproduce

1. Download/fork [this sandbox](https://codesandbox.io/p/devbox/blissful-gauss-6cvc8v) locally. 
2. Install dependencies `npm i --legacy-peer-deps --force`
3. Run in development `npm run dev`
4. Download, unzip and put this [requestBody.zip](https://github.com/user-attachments/files/18098248/requestBody.zip) into the project.
5. Send a curl request using the requestBody file: 
```
curl -X POST http://localhost:3000/ -H 'Content-Type: multipart/form-data; boundary=60eb717e9b0dc' --data-binary @requestBody
```
6. Watch the logs of the application, you should see the mentioned error: 
![image](https://github.com/user-attachments/assets/ac3b9665-c7f9-49a7-96d3-291e5c18dbc0)


## The current behavior
There's an unhandled error in the logs when action's metadata comes in unexpected format.

## The expected behavior
The situation is handled, and there's no errors in the logs. 

## Possible solution
Similar to what's been added by @sebmarkbage in [ReactFlightClient.js](https://github.com/facebook/react/blob/79ddf5b574db085104d917c24a964cbd5b824e09/packages/react-client/src/ReactFlightClient.js#L262) in [this commit](https://github.com/facebook/react/pull/28847/commits/8e33e92aee3c00def90d2ab189eca8bca7380703#diff-4bc3e2f66cfadc63bd7abcc0387fcc7c1373092f832cac1b34614d8cddca5eacR229-R231), wrap the reject call in a `if (reject)`. Additionally, the underlying error which is thrown by this reject (`SyntaxError: Expected property name or '}' in JSON at position 1`), should also be handled.
Repository: rust
Issue: Tracking Issue for rustdoc `--doctest-compilation-args` command line option
Labels: T-rustdoc,C-tracking-issue

### Steps

[Original issue](https://github.com/rust-lang/rust/issues/67533)

- [ ] [Implementation PR](https://github.com/rust-lang/rust/pull/128780)
- [ ] Stabilization PR ([see instructions on rustc-dev-guide][stabilization-guide])

[stabilization-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr

### Unresolved Questions

* [ ] Should argument parsing be closer to what already exists for [RUSTFLAGS](https://doc.rust-lang.org/nightly/cargo/reference/environment-variables.html?highlight=rustflags) (whitespace splitting and nothing else) or should it be closer to how shell parses input (take into account escaped characters and quote characters)? Or should we offer two options, one that works like RUSTFLAGS for human users and one that works like CARGO_ENCODED_RUSTLFAGS for tool usage?
Repository: pytorch
Issue: onnx export broken for Upsample layers when using deterministic algorithms
Labels: module: onnx,triaged

### 🐛 Describe the bug

Using torch==2.5.1+cu121 I get the following  error 
```
Exception has occurred: RuntimeError       
(note: full exception trace is shown but execution is paused at: _run_module_as_main)
Expected all tensors to be on the same device, but found at least two devices, cuda:0 and 
cpu! (when checking argument for argument max in method wrapper_CUDA_clamp_Tensor)
torch\_decomp\decompositions.py line 3657
xp1 = (x + 1).clamp(max=inp_size - 1)
```
When running
```
import torch
import torch.nn as nn

torch.use_deterministic_algorithms(True)
upsample = nn.Upsample(scale_factor=2, mode="bilinear", align_corners=True)
x = torch.randn(1, 3, 64, 64).to("cuda:0")
type(x.size()[0])
y = upsample(x)
torch.onnx.export(
    upsample,
    (x,),
    "test.onnx",
    input_names=["x"],
    output_names=["y"],
    opset_version=18,
)
```
While the export works when using `torch.use_deterministic_algorithms(False)`

For some reason 
`osize`  in the function `_upsample_linear_vec` in `torch\_decomp\decompositions.py` is a list of single element tensors `[tensor(128), tensor(128)]` that are on the cpu instead of a list of integers, causing the error down the line



### Versions

I am using torch==2.5.1+cu121 on windows
Repository: PowerToys
Issue: Outlook Reminders Pop-Up not possible to exclude from snap area full screen with FancyZones
Labels: Issue-Bug,Product-FancyZones,Needs-Triage

### Microsoft PowerToys version

0.86.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

FancyZones

### Steps to reproduce

This problem returned a few days ago, Exclusion of "Reminders" used to work keeping reminders pop-up original size, now the small fixed reminders pop-up window is again expanding to the area full screen, even when listed in exclusions.

### ✔️ Expected Behavior

Outlook Reminders pop-up should not expand when listed under FancyZones exclusions.

### ❌ Actual Behavior

Outlook Reminders pop-up expands

### Other Software

_No response_
Repository: angular
Issue: Canonical: Data Dependencies on Views and Components
Labels: area: core,canonical

### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

Currently there's no way to identify the data dependencies of a component or a view since we do not have a data primitive like a suspense boundary. `Resource` is a good start, but in order to solve things like when to invalidate hydration data caches independently for incremental hydration, we'll need some solution for this problem.
Repository: next.js
Issue: [bug]: intercepting routes cannot go back outside dynamic params
Labels: bug,Parallel & Intercepting Routes

### Link to the code that reproduces this issue

https://github.com/juliusmarminge/next-intercepting-routes

### To Reproduce

1. Deploy the project. This issue works when running locally (both `next dev` and `next start`).
2. Navigate down the tree until you get to an "app"-segment (e.g. https://next-intercepting-routes-one.vercel.app/dashboard/1/1)
3. Click on a card, it should open as a modal but instead it hard navigates


### Current vs. Expected behavior

Locally it does what you expect, deployed it hard-navigates and checking server logs reveals this error:

![CleanShot 2024-12-11 at 16 55 38](https://github.com/user-attachments/assets/449ce58c-29f7-4acf-bf68-4a4eb2a57539)

But that doesn't make any sense since the `/dashboard/[team]/audit` page doesn't expect the `appId` param, and on the `/dashboard/[team]/[appId]` page it should be present. Are you only tracking 1 URL?

Demo: 
https://github.com/user-attachments/assets/22a21b29-a18f-4d62-8db6-f469f80fc014

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.2.0: Fri Nov 15 19:28:48 PST 2024; root:xnu-11215.61.3~1/RELEASE_ARM64_T6000
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 20.18.0
  npm: 10.8.2
  Yarn: N/A
  pnpm: 10.0.0-alpha.0
Relevant Packages:
  next: 15.1.1-canary.0 // Latest available version is detected (15.1.1-canary.0).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.5.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Parallel & Intercepting Routes

### Which stage(s) are affected? (Select all that apply)

Vercel (Deployed)

### Additional context

I cannot move the modal up above the `appId` segment since I don't want the modal to show when navigating from `/[team]` to `/[team]/audit` for example.

Also tried to create a route group between the two and mounting the modal there, without success.

At the end I even tried with a hacky workaround to do conditional hard navigations but that resulted in a whole other class of problems
Repository: go
Issue: x/crypto/x509roots/fallback: should not exclude roots with Distrust After dates
Labels: NeedsInvestigation

Due to <https://github.com/golang/crypto/blob/7042ebcbe097f305ba3a93f9a22b4befa4b83d29/x509roots/gen_fallback_bundle.go#L129-L134>, roots in the Mozilla trust store with Distrust After dates, such as Entrust, are being excluded from the fallback bundle, meaning certificates that Firefox would accept will be incorrectly rejected by Go programs which use x509roots/fallback.  I believe this creates a compatibility risk for the WebPKI and the correct thing to do until #70623 is fixed is to include roots with constraints.

This does mean that Distrust After dates would be ignored, but the security value of Distrust After is practically nil due to backdating, and the real point of Distrust After is to pave the way for an uneventful root removal 398 days in the future.

(Apologies for not filing this sooner; when I [did my review last month](https://sslmate.com/blog/post/entrust_distrust_more_disruptive_than_intended) I unfortunately looked only at x509roots/nss/parser.go and missed the code in gen_fallback_bundle.go)

cc @rolandshoemaker @FiloSottile
Repository: godot
Issue: A type error reported when GDScript preload an scene that used this GDScript
Labels: bug,topic:gdscript

### Tested versions

- 4.3 stable

### System information

MacOS 15, develop enviroment

### Issue description

hex_grid.gd
```gdscript
class_name HexGrid
extends Node2D
# the hex_grid.tscn used this GDScript
const HEX_GRID = preload("res://scene/hex_grid.tscn")
```

test.gd
```gdscript
class_name Module
extends Node2D
# the $HexGrid is hex_grid.tscn
@onready var hex_grid: HexGrid = $HexGrid
```

the Editor report: Trying to assign value of type 'Node2D' to a variable of type 'hex_grid.gd'
![Image](https://github.com/user-attachments/assets/29ea4b56-de65-4a08-b105-c472375eee97)


### Steps to reproduce

as reported above

### Minimal reproduction project (MRP)

NA
Repository: go
Issue: proposal: regexp/syntax: recognize Unicode category aliases
Labels: Proposal

The Unicode specification defines aliases for some of the general category names. For example the category "L" has alias "Letter".
	
The regexp package supports \p{L} but not \p{Letter}, because there is nothing in the Unicode tables that lets regexp know about Letter.
	
Package regexp would be a permitted implementation for use in JSON-API Schema implementations except that there are tests with usage of aliases like \p{Letter} instead of \p{L}.

In #70780 I proposed adding a new CategoryAliases table to package unicode.

If that is accepted, I propose to also recognize the category aliases in regexp/syntax, which will make them work in package regexp.