sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: ice when implementing `Try` trait
Labels: I-ICE,T-compiler,A-incr-comp,C-bug,S-needs-repro

`rustc-ice`

this is the project i was working on https://github.com/zahash/fullstack/commit/2c2bb78e2b742c2125e7b4c816ad65cb378064fa

i don't exactly know what caused this but i was trying to implement the `Try` trait for one of my structs.
this is the final result

```rust
pub struct Redacted<T>(T);

impl<T, E> Try for Redacted<Result<T, E>> {
    type Output = Redacted<T>;
    type Residual = Result<Infallible, E>;

    fn from_output(output: Self::Output) -> Self {
        Redacted(Ok(output.0))
    }

    fn branch(self) -> std::ops::ControlFlow<Self::Residual, Self::Output> {
        match self.0 {
            Ok(value) => ControlFlow::Continue(Redacted(value)),
            Err(err) => ControlFlow::Break(Err(err)),
        }
    }
}

impl<T, E> FromResidual<Result<Infallible, E>> for Redacted<Result<T, E>> {
    fn from_residual(residual: Result<Infallible, E>) -> Self {
        Redacted(residual.map(|v| match v {}))
    }
}
```

the goal is to do somthing like this

```rust
fn foo() -> Result<(), Error> {
    let r: Redacted<Result<String, Error>> = ... ;
    let s: Redacted<String> = r?;
    // ...
}
```

i tried to recreate the issue but couldn't but luckily i still had the undo history on the editor. so i made a video of me cycling through that history if someone wants it.https://github.com/user-attachments/assets/db6d3775-ef60-48a8-ab26-ed9bac918be7
[rustc-ice-2024-10-16T09_27_38-1800.txt](https://github.com/user-attachments/files/17395735/rustc-ice-2024-10-16T09_27_38-1800.txt)
[rustc-ice-2024-10-16T09_27_38-22104.txt](https://github.com/user-attachments/files/17395738/rustc-ice-2024-10-16T09_27_38-22104.txt)
[rustc-ice-2024-10-16T09_38_46-19516.txt](https://github.com/user-attachments/files/17395737/rustc-ice-2024-10-16T09_38_46-19516.txt)
[rustc-ice-2024-10-16T09_38_46-24188.txt](https://github.com/user-attachments/files/17395736/rustc-ice-2024-10-16T09_38_46-24188.txt)
Repository: deno
Issue: Deno is not able to resolve npm workspace dependency types
Labels: bug,tsc,workspaces

Version: Deno 2.0.0

tldr: Deno seems to be having problems resolving npm workspace dependency types with packages having only `package.json`; Maybe because the exports uses `*`? 

My current structure is:

`project/apps/project` -> Remix app with a package.json. Runtime runs vite w/ deno, and the imports are resolved just fine. Points to `project/packages/ui` via `"@project/ui": "^1.0.0"` in package.json.

`project/packages/ui` -> React library exporting some components. Includes a `package.json`, but i've noticed that adding a deno.json kind of solves the type resolving (i'd have a package.json AND a deno.json just to be able to use deno check etc.; i've already done this for another package). 

But also ends up introducing another problem: exports using a wildcard (`*`) seems to make all exports in deno.json stop being detected. I've tested in different packages here, and everything works until you have any export using a wildcard. In `project/packages/ui/package.json`, i have an exports map like that:

```json
  "exports": {
    "./globals.css": "./globals.css",
    "./postcss.config.mjs": "./postcss.config.mjs",
    "./tailwind.config.ts": "./tailwind.config.ts",
    "./lib/*": "./src/lib/*",
    "./hooks/*": "./src/hooks/*",
    "./components/*": "./src/components/*"
  }
```

This does not work in deno.json, so i have to either put an export for all files, or create a barrel file, that i'd really prefer not to.

Output of `deno check .` at root:

```sh
error: Failed resolving types. [ERR_TYPES_NOT_FOUND] Could not find types for 'file:///Users/viktor/repos/project/packages/ui/src/components/button.tsx' imported from 'file:///Users/viktor/repos/project/apps/project/app/components/Chat.tsx'
    at file:///Users/viktor/repos/project/apps/project/app/components/Chat.tsx:6:24
```

Hovering the import, the Deno LSP shows me:

```
Resolved Dependency

Code: file​:///Users/viktor/repos/project/packages/ui/src/components/button.tsx

Types: [errored]
```
Repository: angular
Issue: Give an error/warning when testing for falsy against signal functions in the template
Labels: area: compiler,compiler: extended diagnostics

### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

Consider the following code:

```ts
@Component({
  //...
  template: `
    <!-- not doing the correct !isFalsy() check -->
    @if (!isFalsy) {
      Hello world!
    }
  `,
  //...
})
export class ExampleComponent {
  isFalsy = signal<boolean>(true);
}
```

This code compiles without giving any errors/warnings, and while it obviously would be normal to, testing for falsy against the signal functions *should* be a mistake unless there are some legit use cases I'm unaware of.

### Proposed solution

Either error or give a warning saying that what you are doing might be a mistake when this happens.

### Alternatives considered

Couldn't think of other alternatives, but anything to help point these out in our code is a welcome change.
Repository: opencv
Issue: the cv::cuda::transpose crash when CV_32F rows exceed 1048560
Labels: bug,category: gpu/cuda (contrib)

### System Information

OpenCV: 4.10.0
compiler: clang 17.0.6
Platform: almalinux9
cuda sdk: 12.3

### Detailed description

```
exception message: OpenCV(4.10.0) opencv-4.10.0/contrib/modules/cudev/include/opencv2/cudev/grid/detail/transpose.hpp:118: error: (-217:Gpu API call) invalid configuration argument in function 'transpose
```


### Steps to reproduce

```cpp
for (int i = 1048555; i <= 1048561; i += 1)
    {
        cv::Mat src(i, 4, CV_32F, cv::Scalar{2});
        cv::Mat dst;
        cv::RNG rng{};
        rng.fill(
            src,
            cv::RNG::UNIFORM,
            0,
            200
        );

        // CPU works
        cv::transpose(src, dst);

        // GPU works
        cv::cuda::GpuMat d_src(src);
        cv::cuda::GpuMat d_dst;
        cv::cuda::GpuMat d_dst2{src.cols, src.rows, src.type(), cv::Scalar{10}};
        std::cout << cv::cuda::sum(d_src) << "| " << cv::cuda::sum(d_dst2) << std::endl; 
        cv::cuda::transpose(d_src, d_dst);
        cv::cuda::transpose(d_src, d_dst2);
        std::cout << cv::cuda::sum(d_src) << "| " << cv::cuda::sum(d_dst) << "| " << cv::cuda::sum(d_dst2) << std::endl; 
        // Check results
        bool passed = cv::norm(dst - cv::Mat(d_dst), cv::NORM_INF) < 1e-3;
        bool passed2 = cv::norm(dst - cv::Mat(d_dst2), cv::NORM_INF) < 1e-3;
        std::cout<< "i=" << i << " dst without memory initalized:" << (passed ? "passed" : "FAILED") << std::endl;
        std::cout<< "i=" << i <<  "dst with memory initalized:" << (passed2 ? "passed" : "FAILED") << std::endl;

        // Deallocate data here, otherwise deallocation will be performed
        // after context is extracted from the stack
        d_src.release();
        d_dst.release();
        d_dst2.release();
        std::cout << "released\n";
    }
```

### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: deno
Issue: Deno lint ignores the `ignore` and `exclude` options
Labels: bug,lint

Version: Deno 2.0.0

I'm using deno in a workspace that includes a npm package `project/packages/ui` which is a collection of React components, that use tailwind. In this package, i have a `globals.css` file that is not valid for the default Deno CSS linter, since i have a setup that uses postcss to process it (for tailwind) etc. 

Problem is, i cannot seem to ignore this file in any way. I've tried using --ignore, putting it inside lint: { exclude: [*.css] } inside a deno.json file at the root of the project and at the package, and using a comment at the top of the css file with deno-lint-ignore-file.

Besides all that, deno lint keeps breaking on this file, trying to check it.
Repository: vscode
Issue: SCM - Git commit view: Show message on top of diffs
Labels: feature-request,scm

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->

It is great that since the last update (I did), the git history in the side-panel finally shows the full commit message in the tool-tip! However, when I continue working/reviewing code, that display obviously quickly vanishes and even though I can copy the message there (thanks for the button!), it's tedious to do so.

So, my wish would be that at the top of the commit diff view, there would be a permanent, collapsible view with a max height and scrolling if too small in which the full commit message can be displayed - in fact similar to what `git show` would give you on the command line.
Repository: excalidraw
Issue: Space's link
Labels: enhancement

Is there in excalidraw anything similar to a "space's link"?
I don't know if this feature exist in any application to draw at all.
I want something like a link that when you press bring you to some coordinates of the whiteboard.

Is that a stupid idea?
I think that can be really useful in diagrams of big dimension.
Repository: rust
Issue: Diagnostics differ between regular execution and ui tests
Labels: A-diagnostics,T-compiler,T-bootstrap,D-diagnostic-infra,A-compiletest

Consider this example:
```rust
fn main() {
    let val = 2;
    let ptr = std::ptr::addr_of!(val);
    unsafe { *ptr = 3; }
}
```
On the playground and when I run it locally, this produces:
```
error[E0594]: cannot assign to `*ptr`, which is behind a `*const` pointer
 --> src/main.rs:6:14
  |
6 |     unsafe { *ptr = 3; }
  |              ^^^^^^^^ `ptr` is a `*const` pointer, so the data it refers to cannot be written
  |
help: consider changing this to be a mutable pointer
 --> /playground/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ptr/mod.rs:2207:6
  |
22|     &mut raw const $place
  |      +++
```
However, when I make this a ui test, I get different output:
```
error[E0594]: cannot assign to `*ptr`, which is behind a `*const` pointer
  --> /home/r/src/rust/rustc.2/tests/ui/mytest.rs:5:14
   |
LL |     unsafe { *ptr = 3; }
   |              ^^^^^^^^ `ptr` is a `*const` pointer, so the data it refers to cannot be written
   |
help: consider specifying this binding's type
   |
LL |     let ptr: *mut i32 = std::ptr::addr_of!(val);
   |            ++++++++++
```
That's... not great? We're supposed to test what users see, and something seems to be going wrong.

Cc @rust-lang/wg-diagnostics
Repository: go
Issue: proposal: x/crypto/ssh: support parsing sk-* private keys
Labels: Proposal,Proposal-Crypto

### Proposal Details

Support for sk-* key types on the server-side was added in 2019: https://github.com/golang/crypto/commit/86a70503ff7e82ffc18c7b0de83db35da4791e6a

While working on a FIDO2 for SSH project I noticed that the library supports parsing sk-ecdsa-sha2-nistp256@openssh.com and sk-ed25519@openssh.com public keys, but seems to have no corresponding support for parsing private keys for these key types (i.e. in https://github.com/golang/crypto/blob/7cfb9161e8d828fd6d9f34560e78460435b63503/ssh/keys.go#L1488).

Perhaps this is because sk-* private keys are not true private keys but just contain a key handle which references the private key on the security key (as mentioned in https://developers.yubico.com/SSH/Securing_SSH_with_FIDO2.html). However, I believe we should still be able to parse the private key and extract the key handle + the public key part.

Just curious if there's any reason support was not added for this already?
Repository: vscode
Issue: RGB alpha on terminal cursor has no effect after changing settings
Labels: help wanted,upstream,good first issue,upstream-issue-linked,terminal-rendering

<!-- ⚠️⚠️ 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:
```
Version: 1.94.2 (system setup)
Commit: 384ff7382de624fb94dbaf6da11977bba1ecd427
Date: 2024-10-09T16:08:44.566Z
Electron: 30.5.1
ElectronBuildId: 10262041
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.22631
```
- OS Version: Windows 11 23H2 22631.4317

Steps to Reproduce:

1. Put this customization in your settings.json
![Image](https://github.com/user-attachments/assets/20360021-7e1d-4cda-9818-2162dcd018b9)
2. See the difference in cursors in the editor and in the terminal:
    - Editor
    ![Image](https://github.com/user-attachments/assets/fa05a971-f6a8-4272-a8d9-28fcc45fdab4)
    - Terminal
    ![Image](https://github.com/user-attachments/assets/d6c1998f-542c-4274-a263-094b0a3c19b5)
Repository: vscode
Issue: Contribution Points documentation is missing notebooks
Labels: debt,notebook

https://code.visualstudio.com/api/references/contribution-points does not include any information about the `notebooks` contribution point.
Repository: ollama
Issue: Library tags not present in model information - RFC
Labels: feature request

Today, I was using a third party software along Ollma (Msty). That program has support for text and vision models. As I was trying MiniCPM-V, a vision model, it was not detected by the program. Somehow I assumed that the Vision tag present on the library would be also present in the Model information. But that does not seem the case.

Would it make sense to add that information to the model description?

Sample vision model information on the Ollama library: 

![image](https://github.com/user-attachments/assets/7f14e5d9-e17a-42f9-80ec-c522ac9ad04e)

Sample output using ollama show modelname:

![image](https://github.com/user-attachments/assets/90f0a35a-9bf6-449b-8c4e-cf48156bded0)

As you can see, the Vision tag on the Library is not present on the model information. (I assume it could be infered from the projector section).

This issue could be related to #5682.
Repository: vscode
Issue: Chinese not fully supported.
Labels: bug,notebook-output

<!-- ⚠️⚠️ 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?: No

<!-- 🪓 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: 
Version: 1.94.2
Commit: 384ff7382de624fb94dbaf6da11977bba1ecd427
Date: 2024-10-09T16:08:44.566Z
Electron: 30.5.1
ElectronBuildId: 10262041
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Darwin arm64 20.6.0
- OS Version: 
macOS Big Sur 11.7.10, Mac mini M1

Steps to Reproduce:

1. VScode + Jupyter + R
2. The Chinese characters are automatically translated into "<U+????><U+????>" like code. 
3. This code is UTF-8 encoding. 
4. ![Image](https://github.com/user-attachments/assets/aa9271a6-47e5-4a50-9b87-a2fe60f2f2db)
5. However, in Python kernel, the Chinese characters are displayed correctly. 
6. You can try to reproduce by this code: `print('数据')` in R kernel.
7. ![Image](https://github.com/user-attachments/assets/74a02fbf-03fb-4380-a835-2e7517344f1b)
Repository: flutter
Issue: Iframed flutter web in a fixed position with a ListView in a SingleChildScrollView will share scrolling with the parent page
Labels: framework,f: scrolling,platform-web,has reproducible steps,P2,team-web,triaged-web,found in release: 3.24,found in release: 3.27

### Steps to reproduce

1. Wrap a ListView in a SingleChildScrollView
2. Embed the flutter app on another website in a fixed position
3. Hover over the flutter app and scroll

### Expected results

Just the flutter app scrolls.

### Actual results

The flutter app AND the parent website scrolls.

### Code sample

<details open><summary>Code sample</summary>

Here is the flutter app: https://dartpad.dev/?id=a2e11707d9d8b33fae7d1aa737feaf80
Here is an example of it embedded in a website: https://codepen.io/erik-wayhaven/pen/gOVWXzq
You may need to resize your window to get it to scroll.

</details>


### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>


https://github.com/user-attachments/assets/4fe14652-bd54-496c-9ed3-5cdc94892e5e



</details>


### Logs

_No response_

### 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.1, on macOS 14.6.1 23G93 darwin-x64, locale en-US)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 16.0)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.2)
[✓] VS Code (version 1.94.1)
[✓] Connected device (2 available)
[✓] Network resources

• No issues found!
```

</details>
Repository: godot
Issue: Autoloads in editor are loaded before GDExtensions
Labels: bug,topic:editor,topic:gdextension

### Tested versions

Godot v4.4.dev3 - Windows 10.0.19045 - Single-window, 1 monitor - OpenGL 3 (Compatibility) - NVIDIA GeForce RTX 4050 Laptop GPU (NVIDIA; 32.0.15.6070) - 13th Gen Intel(R) Core(TM) i5-13500HX (20 threads)

### System information

Godot v4.4.dev3 - Windows 10.0.19045 - Single-window, 1 monitor - OpenGL 3 (Compatibility) - NVIDIA GeForce RTX 4050 Laptop GPU (NVIDIA; 32.0.15.6070) - 13th Gen Intel(R) Core(TM) i5-13500HX (20 threads)

### Issue description

When in the editor and the editor initially starts up, autoload scripts are loaded before GDExtensions are initialized
![image](https://github.com/user-attachments/assets/2d10443d-cca5-4f42-b47a-c0333784abee)
I currently have this Autoload script that extends from my GDExtension class:
```gdscript
@tool # Ensures this singleton runs in editor
extends BopimoGame
```

This also seems to cause errors when exporting headlessly, it constantly spams prints from gdscript scripts about the gdextension classes not being found

### Steps to reproduce

- Create a script that references GDExtension classes
- Put the script as an autoload - make sure the @tool annotation is there so it can run in editor
- Notice the script can't compile because it doesn't know the GDExtension class
- Therefore the autoload won't load inside the editor
- Opening the project settings dialogue after the GDExtension has loaded recompiles (i think?) the script and then allows it to work inside the editor

### Minimal reproduction project (MRP)

see above
Repository: deno
Issue: Deno + Vite: cannot resolve deno dependencies
Labels: bug,bundler-resolution

Version: Deno 2.0.0 & Deno 2.0.0-f94cdd1

I have followed both docs on creating a vite app with react:
- https://docs.deno.com/deploy/tutorials/vite/
- https://docs.deno.com/runtime/tutorials/how_to_with_npm/react/

Both tutorials work until you add a package. for example `@std/text` from `jsr`.
The first one uses a third-party vite template which fully uses a `deno.json` file.
The second one simply uses the `package.json`.

If the package is added through `deno.json`, It kind of gets the `mod.ts` file of the package and nothing more. so it prints an error pointing to the first `export * from "..."` line. in this case for `@std/text` it's the [levenshtein_distance.ts](https://github.com/denoland/std/blob/45be5d319dde70c3901ca24294936e95a8a7f0be/text/mod.ts#L22C1-L22C43) file.

And if the package is added through `package.json`, it simply fails with `Failed to resolve "package"`

I'm even using the deno's official [deno-vite-plugin](https://github.com/denoland/deno-vite-plugin) which should resolve `jsr`, `node`, `https` packages. But one thing I noticed is that inside the code some of the types have V1 in their name which may indicate the package is not updated for version 2.0.0 [here](https://github.com/denoland/deno-vite-plugin/blob/895724634320eb5946c8c606f2e6f342976b4c0c/src/resolver.ts#L38)

Here is a reproduction repo using the `deno.json` method: https://github.com/WerdoxDev/deno-vite-bug
Repository: ollama
Issue: Ministral-8B-Instruct-2410
Labels: model request

https://huggingface.co/mistralai/Ministral-8B-Instruct-2410

<img width="1633" alt="instruct_table_with_gemma" src="https://github.com/user-attachments/assets/23eb1742-ee5e-475a-bf7b-5853f781c4f7">
Repository: terminal
Issue: Keybind to suppress all keybinds
Labels: Area-TerminalControl,Area-Settings,Product-Terminal,Issue-Task

# Description of the new feature/enhancement

We have a lot of programs like vim or others which could have keybinds that map to the same which is in terminal the keyboard is kind of limited for all the possible keybinds to not be used when running this command
# Proposed technical implementation details (optional)
In general we could have a keybind that maps to one key combination when pressed would disable all keybinds and when task is done we can come back
Repository: go
Issue: proposal: x/image/webp: errInvalidFormat should be exported
Labels: Proposal

### Proposal Details

When an unknown image type gets decoded in the x/image/webp a unexported error is returned .   This should probably be exported.

This would allow us to catch it better than doing string parsing to catch the error type.

https://cs.opensource.google/go/x/image/+/refs/tags/v0.21.0:webp/decode.go;l=19


A separate error with the same message is used here as well and should be updated to use the same type. 
https://cs.opensource.google/go/x/image/+/refs/tags/v0.21.0:webp/decode.go;l=176