sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: TypeScript
Issue: Non-null assertion operator whitespace allowances can create confusing conditional statements
Labels: Suggestion,Help Wanted,Experience Enhancement

### 🔎 Search Terms

You can write a non-null assertion operator with whitespace after a variable name and no white space before certain keywords such as `in` and `instanceof` and the type checker doesn't fail but instead strips the operator creating the opposite condition as it appears.

To a someone not familiar with TypeScript/JavaScript `key !in obj` reads like `if key not in obj` .  To them this might be if the tsc treated `key !== 'a'` as `key == 'a'`






### 🕗 Version & Regression Information

- This changed between versions N/A and N/A
- This changed in commit or PR N/A
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about Common "Bugs" That Aren't Bugs
- I was unable to test this on prior versions because N/A


### ⏯ Playground Link

https://www.typescriptlang.org/play/?ts=5.8.0-dev.20241116#code/MYewdgzgLgBAZiEAuGBvAhgfhdATgSzAHMBfGAXjXRQHIAjdXGkgbgChRJYBrAUwE8KMGuhox0EGJ2js2+ODAAUfQQEJC8RAEo0bGFPAQQAG14A6YyCKKEIANoqAulvYk2chTcQx1XdGGBeEAUAeToAK15gKB1UPQNIE3NLayh+AAcghVsXNhIgA

### 💻 Code

```ts
const foo: {a?: string} = {a: 'bar'};
const key = 'a' as const;

if (key !in foo) {
  // non-null operator stripped and key exists in obj
  console.log(foo[key]);
}

if (foo !instanceof Object) {
  // non-null operator stripped and obj is Object
  console.log(typeof foo);
}
```


### 🙁 Actual behavior

The TSC stripped the non-null assertion, the operator should not be considered a non-null operator at all in this situation.

### 🙂 Expected behavior

I would expect a syntax error in this situation.

### Additional information about the issue

This is a real problem not just hypothetical, I noticed a discussion started by a person learning typescript complaining about how their code was evaluating true regardless of the "negation operator" being used before the `in` keyword.

![Image](https://github.com/user-attachments/assets/2bcee7a1-af19-4dd4-a510-55db1ce77c85)
Repository: rust
Issue: debuginfo: does the debugger annotations support revisions?
Labels: A-debuginfo,T-compiler,T-bootstrap,C-bug,A-compiletest

Noticed while working on #133115.
Repository: rust
Issue: add a note if a type implements a trait with the same name as the required trait
Labels: A-diagnostics,A-trait-system,T-compiler

### Code

```Rust
trait Trait {}

mod m {
    pub trait Trait {}
    pub struct St;
    impl Trait for St {}
}

fn func<T: Trait>(_: T) {}

fn main() {
    func(m::St);
}
```

### Current output

```Shell
Compiling playground v0.0.1 (/playground)
error[E0277]: the trait bound `St: Trait` is not satisfied
  --> src/main.rs:12:10
   |
12 |     func(m::St);
   |     ---- ^^^^^ the trait `Trait` is not implemented for `St`
   |     |
   |     required by a bound introduced by this call
   |
help: this trait has no implementations, consider adding one
  --> src/main.rs:1:1
   |
1  | trait Trait {}
   | ^^^^^^^^^^^
note: required by a bound in `func`
  --> src/main.rs:9:12
   |
9  | fn func<T: Trait>(_: T) {}
   |            ^^^^^ required by this bound in `func`
```

### Desired output

```Shell
Compiling playground v0.0.1 (/playground)
error[E0277]: the trait bound `St: Trait` is not satisfied
  --> src/main.rs:12:10
   |
12 |     func(m::St);
   |     ---- ^^^^^ the trait `Trait` is not implemented for `St`
   |     |
   |     required by a bound introduced by this call
   |
note: `St` implements similarly named `crate::m::Trait`, but not `crate::Trait`
help: this trait has no implementations, consider adding one
  --> src/main.rs:1:1
   |
1  | trait Trait {}
   | ^^^^^^^^^^^
note: required by a bound in `func`
  --> src/main.rs:9:12
   |
9  | fn func<T: Trait>(_: T) {}
   |            ^^^^^ required by this bound in `func`
```

### Rationale and extra context

This can easily happen if you accidentally have two different versions of the same crate in your dependency tree (see [this URLO thread](https://users.rust-lang.org/t/rust-lacks-a-comprehensive-crypto-library-for-common-algorithms/121209/10)), or have two dependencies that use different trait for the same thing (eg. `tokio::io::AsyncRead` and `futures_io::AsyncRead`)

### Other cases

```Rust
Should also probably trigger if the implemented trait has a small enough edit distance between it and the desired trait, similar to the help messages for misspelled methods and types.
```

### Rust Version

```Shell
1.82.0
```

### Anything else?

_No response_
Repository: neovim
Issue: Lua: clone object/table (like js structuredClone)
Labels: enhancement,lua

### Problem

(Not fully formed yet, this is just a tracking/reference issue.) 

js has `structuredClone` and https://developer.mozilla.org/en-US/docs/Web/API/Window/structuredClone related concepts of serializability and equality. 

### Expected behavior

The Nvim Lua stdlib has `vim.deepcopy` but no way to override its "hydrator" algorithm.

- do we need a "transferable objects" concept (as opposed to "cloned objects"). cf. js docs: https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm
- detailed documentation of how the clone is performed, what is/isn't serializable
- do we need a table hashing util function (for equality/comparison)?
Repository: pytorch
Issue: Replace reduce(operator.mul) with math.prod for computing product of dimensions
Labels: module: onnx,triaged

The current implementation within the autograd _functions utils.py [file](https://github.com/pytorch/pytorch/blob/main/torch/autograd/_functions/utils.py) relies on reduce and operator.mul to compute the product of a list of dimensions, which can be replaced with the more modern and readable math.prod.

cc @chauhang @penguinwu @avikchaudhuri @gmagogsfm @zhxchen17 @tugsbayasgalan @angelayi @suo @ydwu4
Repository: vscode
Issue: Request: Git reset from the CLI should not remove files from the "Go to File..." dialog's "recently opened" section
Labels: feature-request,workbench-history

<!-- ⚠️⚠️ 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 consider this to be a minor UX improvement. 

Steps to Reproduce:

1. Create a new VSCode project in a git repo
1. Create a bunch of files with similar names. Open them all so they show up in the "Go to File..." dialog's "recently opened" section
1. Commit
1. Create a new directory in VSCode
1. Drag a file from step 2 to the new directory
1. Open a terminal to your project root
1. Run `git add .; git reset --hard`
1. Focus a different VS Code tab 
1. Search for the original file with the the "Go to File..." dialog (ctrl+p)

### Expected:
The original file appears in the "recently opened" section

### Actual:
The file will not be in the "recently opened" section

### Workaround:
You can still find the file in VS Code explorer. If you open it from there, the file will appear in the "Go to File..." dialog's "recently opened" section

## Note: 
1. Restarting VS Code does not make a difference
5. If you change step 8 to click on the deleted tab, the deleted file (i.e., the file with in invalid path) will appear in the "Go to File..." dialog thereafter.
Repository: material-ui
Issue: Extending the outer theme with a nested ThemeProvider throws an error if css variables are active
Labels: docs,customization: theme

### Steps to reproduce

Steps:
1. Open this link to live example: (required) https://codesandbox.io/p/sandbox/exciting-rhodes-zk9kwk 
2. Enable css variables in the outer ThemeProvider
3. Nest a ThemeProvider within the outer ThemeProvider
4. Attempt to extend the outer theme following the guidance in [Theming](https://mui.com/material-ui/customization/theming/#nesting-the-theme) (the codesandbox is adapted straight from that example)
5. When `createTheme` is called with the outer theme spread into it, an error is thrown. This seems to be because the outer theme has a `vars` field, which is not allowed as an input to `createTheme`.


### Current behavior

The following error is thrown: 

```
MUI: `vars` is a private field used for CSS variables support.
Please use another name.
```

### Expected behavior

An error should not be thrown and the outer theme should be able to be extended even if CSS variables are enabled.

### Context

We're trying to extend the outer theme with additional styles, as described in the docs. 

I'm happy to raise a PR to address this issue, once a fix has been agreed.

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>


**Search keywords**: Extending theme
Repository: godot
Issue: GLTF Root Scale does not apply to Collision Shapes generated from Meshes
Labels: bug,topic:import,topic:3d

### Tested versions

- Reproducible in: 4.4.dev4.mono [36e6207bb]

### System information

Godot v4.4.dev4.mono - macOS 15.2.0 - Multi-window, 1 monitor - Metal (Forward+) - integrated Apple M1 (Apple7) - Apple M1 (8 threads)

### Issue description

Using the `Create Collision Shape...` button

<img width="235" alt="Screenshot 2024-11-17 at 01 17 20" src="https://github.com/user-attachments/assets/5a9db141-ba6d-420e-bea7-9793df8d495b">

On a mesh imported from GLTF with a modified root scale, the collision shape will be generated at the original scale of the GLTF.


### Steps to reproduce

1. Import a GLTF and modify the root scale
2. Generate a collision shape from a selected mesh in the GLTF
3. Collision shape will be wrong size

### Minimal reproduction project (MRP)

[mrp.zip](https://github.com/user-attachments/files/17788321/mrp.zip)
Repository: deno
Issue: Deno v2 throws error on simple Mysql2 snippet
Labels: needs info

Deno Version: Deno 2.0.1.

Trying to run the following snippet from the Mysql2 [documentation](https://sidorares.github.io/node-mysql2/docs):

```typescript
// Get the client
import mysql from "mysql2/promise";

// Create the connection to database
const connection = await mysql.createConnection({
  host: "localhost",
  user: "me"
});

// A simple SELECT query
try {
  const [results, fields] = await connection.query("SELECT 1 + 1");
  console.log(results); // results contains rows returned by server
  console.log(fields); // fields contains extra meta data about results, if available
} catch (err) {
  console.log(err);
}
```

Throws the following:

```text
error: Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'setNoDelay')
    at TCP.setNoDelay (ext:deno_node/internal_binding/tcp_wrap.ts:229:28)
    at Socket.setNoDelay (node:net:595:20)
    at new Connection (file:///Users/andres/Library/Caches/deno/npm/registry.npmjs.org/mysql2/3.11.4/lib/connection.js:64:21)
    at Object.exports.createConnection (file:///Users/andres/Library/Caches/deno/npm/registry.npmjs.org/mysql2/3.11.4/index.js:10:10)
    at Object.createConnection (file:///Users/andres/Library/Caches/deno/npm/registry.npmjs.org/mysql2/3.11.4/promise.js:252:31)
    at file:///Users/andres/.../test/mysql2.ts:7:32
```
Repository: godot
Issue: Sub-window graphics issues with Forward+ on Raspberry Pi
Labels: bug,platform:linuxbsd,topic:porting

### Tested versions

- Reproducible in 4.3-stable

### System information

Godot v4.3.stable - Debian GNU/Linux 12 (bookworm) 12 - Wayland - Vulkan (Forward+) - integrated V3D 7.1.7 - ARM Cortex-A76 (4 Threads)

### Issue description

Whenever I have a 3d scene open (even a blank one), the menus and sub-windows have a graphical glitch. I've attached a couple images.
![20241116_17h53m33s_grim](https://github.com/user-attachments/assets/ef858e2a-3fbf-4db9-af42-9cfce82161ad)
![20241116_17h53m39s_grim](https://github.com/user-attachments/assets/a5633c12-fe9a-407a-9cb7-e61ff5c39aa1)
![20241116_17h54m01s_grim](https://github.com/user-attachments/assets/22bcc7c2-0d8c-4805-82cc-3132a8a7852d)
![20241116_17h54m07s_grim](https://github.com/user-attachments/assets/7ae0c1e4-7809-454b-9dd5-db81442b2212)


### Steps to reproduce

Absolutely no specific project is necessary. Just start a 3d scene and open a menu or try to add a node.

### Minimal reproduction project (MRP)

N/A
Repository: godot
Issue: The material of a CSGShape3D as child of a CSGCombiner3D does not obey local triplanar coordinates
Labels: bug,topic:3d

### Tested versions

- Reproducible in: v4.3.stable.mono.official [77dcf97d8]

### System information

Godot v4.3.stable.mono - macOS 14.7.1 - Vulkan (Forward+) - integrated Apple M1 Pro - Apple M1 Pro (10 Threads)

### Issue description

When assigning a material (with local triplanar mapping enabled) to a `CSGShape3D` that is a child of a `CSGCombiner3D`, then the material does not stay in place when the shape is being moved relative to the combiner. It only does so if the combiner itself is moved. This issue does not arise if no `CSGCombiner3D` is present.

### Steps to reproduce

Create a new 3D scene with a `CSGCombiner3D` and a `CSGShape3D` (e.g. a `CSGBox3D`) as its child. Assign a `StandardMaterial3D` to the `CSGShape3D` with a placeholder texture and (local) triplanar coordinates enabled. Move the shape around and observe that the texture does not stay in place. Compare to moving around the combiner itself, or the same shape but not as child of a `CSGCombiner3D`.

### Minimal reproduction project (MRP)

[triplanar-csgcombiner-mrp.zip](https://github.com/user-attachments/files/17788632/triplanar-csgcombiner-mrp.zip)
Repository: rust
Issue: Tracking Issue for String::into_chars
Labels: T-libs-api,C-tracking-issue

Feature gate: `#![feature(string_into_chars)]`

This is a tracking issue for:

* `String::into_chars`

### Public API

```rust
impl String {
    pub fn into_chars(self) -> IntoChars {
        IntoChars { bytes: self.into_bytes().into_iter() }
    }
}

impl Iterator for IntoChars {
    type Item = char;
}
```

### Steps / History

- [x] ACP: https://github.com/rust-lang/libs-team/issues/268
- [ ] Implementation: https://github.com/rust-lang/rust/pull/133057
- [ ] Final comment period (FCP)[^1]
- [ ] Stabilization PR

### Unresolved Questions

- None yet.

[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html
Repository: neovim
Issue: `<Cmd>` keys not handled properly when used with `--remote-send`
Labels: bug,input,event-loop,remote

### Problem

`<Cmd>` keys are not handled properly when used with `--remote-send`. Keys wrapped in between `<Cmd>` and `<CR>` can be interpreted as if they are typed in normal mode instead of part of a command.

For example, if an nvim instance is in the middle of a `gi` keymap, after pressing `g`, if we send it `<Cmd>if v:true | echo 'msg from remote' | endif<CR>`, it will insert `f v:true | echo 'msg from remote' | endif` in the current buffer.

### Steps to reproduce

1. `nvim --clean` to enter nvim
2. `:echo v:servername` to find the listen address
3. Press `g` to put nvim in the middle of the `gi` keymap
4. From another terminal, run `nvim --clean --headless --server <servername> --remote-send "<Cmd>if v:true | echo 'msg from remote' | endif<CR>" +'qa!'`
5. String "f v:true | echo 'msg from remote' | endif" is inserted in the buffer

### Expected behavior

nvim should execute the command instead of entering insert mode on the first 'i' and insert the rest of the command in the buffer.

### Nvim version (nvim -v)

v0.10.2

### Vim (not Nvim) behaves the same?

N/A

### Operating system/version

Linux 6.11.6

### Terminal name/version

alacritty 0.14.0 + tmux next-3.6

### $TERM environment variable

tmux-256color

### Installation

AUR
Repository: node
Issue: --experimental-test-module-mocks is not working as expected
Labels: test_runner

### Version

v24.0.0-pre

### Platform

```text
Linux fedora 6.11.6-200.fc40.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Nov  1 16:09:34 UTC 2024 x86_64 GNU/Linux
```


### Subsystem

_No response_

### What steps will reproduce the bug?

This issue was observed inside the nodejs source code, when tying to create a benchmark
create a file `benchmark/test_runner/mock-module.js` 

now copy this code

```js
"use strict";

const { test } = require("node:test");

function main() {
  test(async (t) => {
    console.log("benchmark");

    try {
    // Create a mock module
    t.mock.module('axios', {
      namedExports: {
        get: (url) => url
      }
    });

    } catch (e) {
      console.error(e);
    }

    console.log("end");
  });
}

main()
```


now run this using `./node --experimental-test-module-mocks benchmark/test_runner/mock-module.js`

You will get this output

```
benchmark
Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'axios' imported from /home/ankan/Documents/git/me/node/benchmark/test_runner/mock-module.js
    at Object.getPackageJSONURL (node:internal/modules/package_json_reader:267:9)
    at packageResolve (node:internal/modules/esm/resolve:768:81)
    at moduleResolve (node:internal/modules/esm/resolve:854:18)
    at defaultResolve (node:internal/modules/esm/resolve:984:11)
    at nextResolve (node:internal/modules/esm/hooks:748:28)
    at resolve (node:internal/test_runner/mock/loader:78:35)
    at nextResolve (node:internal/modules/esm/hooks:748:28)
    at Hooks.resolve (node:internal/modules/esm/hooks:240:30)
    at handleMessage (node:internal/modules/esm/worker:199:24)
    at Immediate.checkForMessages (node:internal/modules/esm/worker:141:28) {
  code: 'ERR_MODULE_NOT_FOUND'
}
end
✔ <anonymous> (42.524333ms)
(node:91728) ExperimentalWarning: Module mocking is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
ℹ tests 1
ℹ suites 0
ℹ pass 1
ℹ fail 0
ℹ cancelled 0
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 48.749785
```

As you can we we are trying to create a mock 'axios' module but we receive the error `Cannot find package 'axios'`, which is **unexpected as we are not even importing** the module. The error is occurring because of the line `t.mock.module`




### How often does it reproduce? Is there a required condition?

dose not need any special condition

### What is the expected behavior? Why is that the expected behavior?

should create a mock module called `axios`

### What do you see instead?

their is an error, saying package 'axios' not found, which is very unexpected

### Additional information

_No response_
Repository: vscode
Issue: Some references.view shortcuts not working
Labels: feature-request,references-viewlet

<!-- ⚠️⚠️ 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.95.3
- OS Version:  Fedora 41

Steps to Reproduce:

1. Open the `Keyboard Shortcuts` preferences window. 
2. Attempt to bind `references-view.removeReferenceItem` (Dismiss) to a keybinding
3. Right click some field or other code construct, click "Find All References."
4. Press `references-view.removeReferenceItem` keybind. 
5. The keybinding does not work.

Expected behavior:

I'd expect this keybinding to execute "Dismiss" on the currently selected reference item, similar to when you right click -> Dismiss in the reference view.

Other info:

* I have tested various keybindings, ensured no clashing keybindings, restarted vscode, and messed with the "when" conditionals quite a bit.
* I cannot get `references-view.removeReferencesItem`, `references-view.removeCallItem` or `references-view.removeTypeItem` to do anything regardless of my keybinding or editor state.
* I can't get `references-view.refind` to work either.
* `references-view.next`, `references-view.previous`, and `references-view.findReferences` work fine (and are very handy!)
* I installed latest VS Code in a Windows 11 VM and tested there with the exact same results.

Am I doing something wrong? I'm real interested in those removeReferences bindings but I just can't get them to do anything for the life of me.
Repository: flutter
Issue: Flutter doesn't honor archivesBaseName
Labels: c: new feature,platform-android,tool,t: gradle,a: build,has reproducible steps,P2,team-android,triaged-android,found in release: 3.24,found in release: 3.27

### Steps to reproduce

When using `archivesBaseName` with app/build.gradle, 

Run `flutter build apk --release`




### Expected results

Expect to find `MyApp***-v0.0.1-release.apk` at `build/app/outputs/flutter-apk/` instead of `app-release.apk`

### Actual results

Produces two identical apks 

```console
Running Gradle task 'assembleRelease'...                           20.8s
✓ Built build\app\outputs\flutter-apk\app-release.apk (20.9MB)
```
After that 
```console
$ find . -name "*.apk" -exec sha256sum {} \;
16cda043ff14797af902b07060f7fdc375f44e5580ca95d4dc55ad4e9658c7f5 *./build/app/outputs/apk/release/MyApp-v0.0.1-release.apk
16cda043ff14797af902b07060f7fdc375f44e5580ca95d4dc55ad4e9658c7f5 *./build/app/outputs/flutter-apk/app-release.apk
```

### Code sample

<details open><summary>Code sample</summary>

```gradle
android {
    namespace = "com.example.myapp"
    archivesBaseName = "MyApp-v${flutter.versionName}"
```

</details>


### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

[Upload media here]

</details>


### Logs

<details open><summary>Logs</summary>

```console
[Paste your logs here]
```

</details>


### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.24.5, on Microsoft Windows [Version 10.0.22631.4460], locale en-US)
[✓] Windows Version (Installed version of Windows is version 10 or higher)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Chrome - develop for the web
[✓] Visual Studio - develop Windows apps (Visual Studio Build Tools 2022 17.11.5)
[✓] Android Studio (version 2024.2)
[✓] VS Code, 64-bit edition (version 1.94.2)
[✓] Connected device (4 available)
[✓] Network resources

• No issues found!
```

</details>
Repository: svelte
Issue: Improved error message for @render containing invalid html
Labels: awaiting submitter

### Describe the problem

I spent hours debugging from errors about illegal invocation and node type and tried googling and searching svelte docs and found nothing. Below are the errors I got:

![image](https://github.com/user-attachments/assets/15e65043-cd86-46bc-8e13-c22e5dea7382)

![image](https://github.com/user-attachments/assets/6b33ed7d-01e0-4648-b3fa-49c11cb93503)


### Describe the proposed solution

The error should be clear that the html node wrapping the @render call cannot wrap the contents of the `@render`, eg. a `<p>` containing a `@render` containing a `<p>`. The error messages were not clear at all and me and my friend who have used svelte for years and svelte 5 for months spent a long time debugging to figure this out. A simple, readable error message would have saved us many hours.

### Importance

would make my life easier