sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: TypeScript
Issue: "const" was transformed to "var" when target is "esnext"
Labels: Bug,Help Wanted

### 🔎 Search Terms

transform, const, var, target, ECMA, esnext

### 🕗 Version & Regression Information

- This is the behavior in every version I tried from Version 5.4 to Version 5.7.0-dev.20240904


### ⏯ Playground Link

_No response_

### 💻 Code

```ts
export const cilBlurLinear : string [ ] = [  ,  ] 
const [ ,  ] = cilBlurLinear;
```


### 🙁 Actual behavior

The JS code generated by tsc is as follows:
```js
"use strict";
Object.defineProperty(exports, "__esModule", { value: true });
exports.cilBlurLinear = void 0;
exports.cilBlurLinear = [,];
var ;
```

### 🙂 Expected behavior

“const” should be translated as "const" instead of "var", as the target in my configuration file is "esnext".

### Additional information about the issue

tsconfig.json:
```json
{
  "compilerOptions": {
    "target": "ESNext",
    "module": "esnext",
    "moduleResolution": "Node",
    "esModuleInterop": true,
    "skipLibCheck": true,
    "forceConsistentCasingInFileNames": true,
    "lib": ["es2023","dom"],
    "noEmitOnError":true,
    "force":true,
    "strict":true
  },
  "include": [
    "TScorpus/*"
  ],
  "exclude": [
    "node_modules"
  ]
}

```
Repository: material-ui
Issue: [icons] Breaking changes in icons package layout
Labels: package: icons,enhancement

_Assuming https://github.com/mui/material-ui/pull/43624 has been merged consider all or some of the following breaking changes in the next major._

- [ ] Remove `./esm/*` and `./esm/*.js` exports
- [ ] (To be decided) Remove commonjs (18.7MB => 6.1MB) #26310 #26240
- [ ] Remove  support for top-level import `.`, it's a footgun, we could just disallow importing from it altogether. It would reduce package size as well to be able to remove the barrel file. (minus 2.3MB)
- [ ] Add a negative export for `./utils`
    ```json
    "./utils/*": null,
    ```
- [ ] Use a single type declaration file for all icons instead of one for each icon. This could also reduce install size.
- [ ] Remove the `node` condition once we fully support ESM https://github.com/mui/material-ui/pull/43264

**Search keywords**:
Repository: pytorch
Issue: Add restrictions so that Inductor never uses more memory than eager
Labels: triaged,oncall: pt2,module: inductor

### 🚀 The feature, motivation and pitch

IMO, we should do something so that we never use more memory than eager-mode in Inductor. Certain patterns can lead to fairly pathological fusion decision in Inductor that lead to a much higher memory mark.

### Alternatives

_No response_

### Additional context

_No response_

cc @ezyang @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire
Repository: flutter
Issue: [camera_android] Reland the Impeller support and apply a proper rotation fix
Labels: platform-android,p: camera,package,c: proposal,P3,e: impeller,team-android,triaged-android

### What happened

Previous attempts of Impeller support broke the camera preview; see https://github.com/flutter/flutter/issues/150549. The revert has landed. However, no further actions were taken and the library did not gain valid support, such as https://github.com/flutter/packages/pull/7044.

### Proposal

Apply a similar fix like https://github.com/flutter/packages/pull/7044 or fix the previous Impeller support changes then reland.
Repository: terminal
Issue: CTRL+ALT+left / right does not work in hyper-v session
Labels: Area-Input,Issue-Bug,Product-Terminal,Priority-3

### Windows Terminal version

1.21.2361.0

### Windows build number

10.0.22631.0

### Other Software

Hyper-V - I didn't do anything but enable it from stock Windows - version says 10.0.22621.1

I installed the Windows Terminal from winget

I'm using keyviz from `scoop install keyviz` to visualize the keypresses.

### Steps to reproduce

Open up a split screen using alt+click
![image](https://github.com/user-attachments/assets/a114e687-746b-446d-b8c1-c56cd7ae2de0)



### Expected Behavior

When I hold down alt+shift+left to resize the pane I expect to resize the screen

Instead pushes these keys:
![image](https://github.com/user-attachments/assets/f3b73c2a-87ca-4e14-bc93-a42351fc92c6)

also, in general, alt+left is sending alt+home on repeated presses
![image](https://github.com/user-attachments/assets/222002db-16f4-441e-8f25-ce8b7fb0d0be)

Also, I face no such issue in my host machine. And even in Hyper-V, when I use `alt+left` in Konsole (for Windows - downloaded from https://cdn.kde.org/ci-builds/utilities/konsole/master/windows/ ) - I don't get the `alt+home` - nor do I get that in VSCode running in Hyper-V.

### Actual Behavior

See above
Repository: flutter
Issue: Enable `CupertinoPopupSurface`'s backdrop filter test on skwasm once the Skia bug is fixed
Labels: f: cupertino,P3,team-design,triaged-design

https://github.com/flutter/flutter/pull/151430 added a backdrop filter to `CupertinoPopupSurface`, but the filter does not work on skwasm due to a Skia bug https://github.com/flutter/flutter/issues/152026. Once the issue is closed, we should unskip these tests.
Repository: next.js
Issue: app router does not resolve routes according to `generateStaticParams` constraints
Labels: bug

### Link to the code that reproduces this issue

https://stackblitz.com/edit/stackblitz-starters-941nyd

### To Reproduce

1. click on "post 2" → it's a post
1. click on "post 1" → it's a post
1. click on "page 2" → **it's a post**
1. click on "page 1" → **it's a post**

### Current vs. Expected behavior

the "pages" urls should resolve with the page route, not the post route.

### Provide environment information

```bash
irrelevant, happens in stackblitz too.
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

_No response_
Repository: rust
Issue: Error on bounds for unused lifetime
Labels: A-lifetimes,P-low,regression-from-stable-to-stable,C-bug,T-types

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

The following fails to build:

```rust
struct Foo<'a, 'b: 'a, 'c: 'a>(&'a mut &'a (), &'b (), &'c ());
fn with_foo<'b>(_f: impl FnOnce(Foo<'_, 'b, '_>)) {}

struct Bar;
impl Bar {
    fn baz<'a>(&'a self, _foo: Foo<'a, '_, '_>) {}

    fn call_baz<'b>(&'b self) {
        with_foo::<'b>(|foo| self.baz(foo))
    }
}
```

```
error[E0521]: borrowed data escapes outside of method
 --> src/lib.rs:9:30
  |
8 |     fn call_baz<'b>(&'b self) {
  |                 --  -------- `self` is a reference that is only valid in the method body
  |                 |
  |                 lifetime `'b` defined here
9 |         with_foo::<'b>(|foo| self.baz(foo))
  |                              ^^^^^^^^^^^^^
  |                              |
  |                              `self` escapes the method body here
  |                              argument requires that `'b` must outlive `'static`

For more information about this error, try `rustc --explain E0521`.
error: could not compile `playground` (lib) due to 1 previous error
```

However, it works if the bounds on `'c` argument on the declaration of `Foo` are changed to either `'c: 'b`, or simply an unbounded lifetime `'c`. This seems unexpected because `'c: 'b` is a stricter bound than `'c: 'a` (and `'c` is a weaker bound than `'c: 'a`). It's even stranger because the `'c` lifetime is unused in this example.

This seems to be either a bug, unexpected limitation, or as another user suggested, an NLL regression. I created a [post on URLO](https://users.rust-lang.org/t/lifetime-bound-causing-error/117075/11?u=coder-256) that has some further discussion.

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.81.0 (eeb90cda1 2024-09-04)
binary: rustc
commit-hash: eeb90cda1969383f56a2637cbd3037bdf598841c
commit-date: 2024-09-04
host: x86_64-unknown-linux-gnu
release: 1.81.0
LLVM version: 18.1.7
```
Repository: node
Issue: await filehandle.close() never return when using with filehandle.createWriteStream({autoClose:false}) and await pipeline()
Labels: fs

### Version

v20.15.1

### Platform

```text
macos Darwin Kernel Version 21.6.0
```


### Subsystem

_No response_

### What steps will reproduce the bug?

```js
const { createReadStream } = require("node:fs");
const { pipeline } = require("node:stream/promises");
const fsPromise = require("node:fs/promises");

const r = createReadStream("/bin/cp");

async function test() {
  let fd;
  try {
    console.log("before file open");
    fd = await fsPromise.open("/tmp/cp", "w+");
    console.log("after file open");

    const destination = fd.createWriteStream({ autoClose: false });

    console.log("before pipeline");
    await pipeline(r, destination);
    console.log("done pipeline");
  } catch (e) {
    console.log("error", e);
  } finally {
    console.log("before close");
    await fd?.close();
    console.log("after close");
  }

  console.log("done");
}

test()
  .then(() => console.log("test done"))
  .catch((e) => console.log("test error", e));

```

### How often does it reproduce? Is there a required condition?

```bash
node test.js
```
log prints end with "before close", never print "after close"

And If I add this test function to electron main process, await fd?.close() will never return.

### What is the expected behavior? Why is that the expected behavior?

await fd?.close() could return normally when using with createWriteStream({autoClose:false})

### What do you see instead?


```
#> node test.js
before file open
after file open
before pipeline
done pipeline
before close
```

### Additional information

_No response_
Repository: go
Issue: regexp/syntax: character class negation is slow 
Labels: Performance,NeedsInvestigation,FixPending

I've submitted a benchmark and a fix at https://github.com/golang/go/pull/69304. 

New benchmark:

```
goos: darwin
goarch: arm64
pkg: regexp/syntax
cpu: Apple M1
BenchmarkString/^(.*);$|^;(.*)-8                 4972814               232.1 ns/op            56 B/op          3 allocs/op
BenchmarkString/(foo|bar$)x*-8                   5602014               212.6 ns/op            56 B/op          3 allocs/op
BenchmarkString/[^=,]-8                         21872083                53.84 ns/op            8 B/op          1 allocs/op
BenchmarkString/([^=,]+)=([^=,]+)-8              5726475               207.3 ns/op            56 B/op          3 allocs/op
BenchmarkString/([^=,]+)=([^=,]+),.*-8           4588252               259.2 ns/op            56 B/op          3 allocs/op
PASS
ok      regexp/syntax   7.603s
```

### Go version

1.23 darwin/arm64

### What did you do?

I received a report at https://github.com/VictoriaMetrics/VictoriaMetrics/issues/6911 and ran a benchmark for `Regexp.String()`.

### What did you see happen?

Some regexes are extremely slow, even when they're simple. The negate `[^]` causes `calcFlags` to run over a large character space to find a fold case.

```bash
goos: darwin
goarch: arm64
pkg: regexp/syntax
cpu: Apple M1
BenchmarkString/^(.*);$|^;(.*)-8                 4594401               253.2 ns/op            56 B/op          3 allocs/op
BenchmarkString/(foo|bar$)x*-8                   5006730               236.1 ns/op            56 B/op          3 allocs/op
BenchmarkString/[^=,]-8                              256           4227434 ns/op               8 B/op          1 allocs/op
BenchmarkString/([^=,]+)=([^=,]+)-8                  151           8032660 ns/op              56 B/op          3 allocs/op
BenchmarkString/([^=,]+)=([^=,]+),.*-8               146           8095255 ns/op              56 B/op          3 allocs/op
PASS
ok      regexp/syntax   9.011s
```
Repository: pytorch
Issue: DISABLED test_inplace_custom_op_intermediate (__main__.InplacingTests)
Labels: triaged,module: flaky-tests,skipped,oncall: pt2,module: inductor

Platforms: linux

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

Over the past 3 hours, it has been determined flaky in 5 workflow(s) with 5 failures and 5 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_inplace_custom_op_intermediate`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.



<details><summary>Sample error message</summary>

```
Traceback (most recent call last):
  File "/var/lib/jenkins/workspace/test/inductor/test_perf.py", line 1016, in test_inplace_custom_op_intermediate
    self.assertExpectedInline(count_numel(f, x, out), """21""")
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/testing/_internal/common_utils.py", line 2925, in assertExpectedInline
    return super().assertExpectedInline(actual if isinstance(actual, str) else str(actual), expect, skip + 1)
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/expecttest/__init__.py", line 351, in assertExpectedInline
    assert_expected_inline(
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/expecttest/__init__.py", line 316, in assert_expected_inline
    assert_eq(expect, actual, msg=help_text)
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/expecttest/__init__.py", line 388, in assertMultiLineEqualMaybeCppStack
    self.assertMultiLineEqual(expect, actual, *args, **kwargs)
  File "/opt/conda/envs/py_3.10/lib/python3.10/unittest/case.py", line 1226, in assertMultiLineEqual
    self.fail(self._formatMessage(msg, standardMsg))
  File "/opt/conda/envs/py_3.10/lib/python3.10/unittest/case.py", line 675, in fail
    raise self.failureException(msg)
AssertionError: '21' != '0'
- 21
+ 0
 : To accept the new output, re-run test with envvar EXPECTTEST_ACCEPT=1 (we recommend staging/committing your changes before doing this)

To execute this test, run the following from the base repo dir:
    python test/inductor/test_perf.py InplacingTests.test_inplace_custom_op_intermediate

This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0
```

</details>


Test file path: `inductor/test_perf.py`

cc @clee2000 @ezyang @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire
Repository: godot
Issue: Can't import specific DDS textures
Labels: enhancement,topic:import

### Tested versions

4.3

### System information

Godot v4.3.stable.mono - Linux Mint 21.3 (Virginia) - X11 - Vulkan (Forward+) - dedicated AMD Radeon RX 6600 (RADV NAVI23) - AMD Ryzen 7 5800X3D 8-Core Processor (16 Threads)

### Issue description

I have some DDS textures which don't import properly in Godot, but work in GIMP and Tacent View. These textures are also grouped with other DDS textures that import fine.
Trying to import one of the textures results in this error.
```
ERROR: Expected Image data size of 256x256x1 (DXT5 RGBA8 with 8 mipmaps) = 87408 bytes, got 87360 bytes instead.
```

### Steps to reproduce

Import the texture, and try to open them in the inspector or use them in a script

### Minimal reproduction project (MRP)

[textures.zip](https://github.com/user-attachments/files/16902450/textures.zip)
This has one of the functional textures, and one of the 'broken' ones.
Repository: three.js
Issue: WebGPURenderer with WebGPU Backend: Clear color is not set correctly
Labels: Needs Investigation

### Description

Clear Color is not set correctly when clear alpha < 1.

Compare `WebGPURenderer` with both `WebGLRenderer` and `WebGPURenderer/WebGLBackend`. The latter two appear to render the same, and I think they are correct.



### Reproduction steps

Set clear alpha to less than 1.

### Code

See fiddles.


### Live example

WebGLRenderer (dev): https://jsfiddle.net/ofyu03vc/

WebGPURenderer (dev): https://jsfiddle.net/fbk0d8s9/


### Screenshots

_No response_

### Version

r169dev

### Device

Desktop

### Browser

Chrome

### OS

MacOS
Repository: go
Issue: net: TestLookupGoogleHost failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "net" && test == "TestLookupGoogleHost"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8737575885378853953)):

    === RUN   TestLookupGoogleHost
        lookup_test.go:408: lookup google.com: no such host
    --- FAIL: TestLookupGoogleHost (11.11s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: vscode
Issue: Sticky scroll "Max line count" setting affects window position
Labels: bug,editor-sticky-scroll

<!-- ⚠️⚠️ 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. -->

# Sticky scroll "Max line count" setting affects window position

## Summary
When updating to version 1.93.0, the Editor > Sticky Scroll: Max Line Count setting affects the position of the window by keeping the cursor in the center of the editor.
This also affects navigation with the up/down arrow keys.
I suspect this to be caused by 52b2f67e96b4e757e8ff8e1e009dfffd70da91f5.

- VS Code Version: 1.93
- OS Version: Windows 10



## Screen recording showing the bug
This video shows the bug in action, and proves that the "Max line count" sticky scroll setting is responsible.
This was recorded on vscode.dev on version 1.93.0.

[vscode 1.93 sticky scroll bug.webm](https://github.com/user-attachments/assets/4b2ee8cf-276c-4b8b-b517-6a690903e852)

## Steps to Reproduce:
1. Open a file with many indentation levels. Make sure Editor > Sticky Scroll: Enabled is toggled and Editor > Sticky Scroll: Max Line Count set to 15.
2. Scroll down until there are >5 lines stuck to the top.
3.  Try to type something in the highest non-sticky line, and try moving up and down with the arrow keys.
<details>
<summary>Example file</summary>
<code>{
	"a": {
		"a": {
			"a": {
				"a": {
					"a": {
						"a": {
							"a": {
								"a": {
									"a": {
										"a": {
											"a": {
												"a": {
													"a": {
														"a": {
															"a": {}
														}
													}
												}
											}
										}
									}
								}
							}
						}
					}
				}
			}
		}
	}
}
</code>
</details>

## Expected result:
The window will stay where it is and only move if the cursor is outside the viewport.
## Observed result:
The window will move to place the cursor in the very center of the screen.
Repository: ui
Issue: [bug]: Cannot initialize components.json using `npx shadcn@latest init` after manual installation of shadcn (for my React app)
Labels: bug

### Describe the bug

I cannot intialize the component.json by following manual installation followed by `npx shadcn@latest init`.

### Affected component/components

components.json

### How to reproduce

1. Install shadcn from - https://ui.shadcn.com/docs/installation/manual
2. Setup components.json - https://ui.shadcn.com/docs/components-json

### Codesandbox/StackBlitz link

_No response_

### Logs

```bash
npx shadcn@latest init
⠙
✔ Preflight checks.
✖ Verifying framework.

We could not detect a supported framework at /my-app/frontend.
Visit https://ui.shadcn.com/docs/installation/manual to manually configure your project.
Once configured, you can use the cli to add components.
```


### System Info

```bash
GitHub Workspaces
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues