sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Minimap #region headers are in the wrong locations when "Vertical size" not set to "Proportional"
Labels: bug,editor-minimap


Type: <b>Bug</b>

Make a file so long that the minimap moves when you scroll.
Right click minimap -> Vertical size -> Fill.
Add a #region to the file.
Notice that its header shows up in the wrong place in the minimap.

VS Code version: Code 1.88.0 (Universal) (5c3e652f63e798a5ac2f31ffd0d863669328dc4c, 2024-04-03T13:28:18.899Z)
OS version: Darwin arm64 23.4.0
Modes:

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

|Item|Value|
|---|---|
|CPUs|Apple M2 Pro (12 x 24)|
|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|
|Load (avg)|3, 3, 3|
|Memory (System)|32.00GB (0.10GB free)|
|Process Argv|--crash-reporter-id 5a7031c2-f284-4b75-a263-7c9f3f994bb2|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (14)</summary>

Extension|Author (truncated)|Version
---|---|---
rails|bun|0.17.8
vscode-gemfile|bun|0.4.2
gitlens|eam|14.9.0
prettier-vscode|esb|10.4.0
copilot|Git|1.179.0
copilot-chat|Git|0.14.1
graphql|mqu|0.1.2
vscode-scss|mrm|0.10.0
debugpy|ms-|2024.4.0
python|ms-|2024.4.1
vscode-pylance|ms-|2024.4.1
slim|sia|0.1.2
json-schema-validator|tbe|0.1.0
pretty-ts-errors|Yoa|0.5.4


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

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:30899288
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:31000450
pythontbext0:30879054
accentitlementst:30995554
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
d34g3935:30971562
fegfb526:30981948
bg6jg535:30979843
ccp2r3:30993541
dsvsc020:30976470
pythonait:31006305
gee8j676:31009558
dsvsc021:30996838
gd77d436:30999572
vstestt:31010881

```

</details>

<!-- generated by issue reporter -->
Repository: next.js
Issue: Adding headers in middleware response is inconstant between dev and running on vercel edge
Labels: bug,Runtime

### Link to the code that reproduces this issue

https://github.com/Xanacas/next-js-header-bug/

### To Reproduce

run nextjs locally and on vercel
click the button to execute the serveraction
have a look at the console


### Current vs. Expected behavior

### Current behavior
adding a header via set() to an Headers instance and passing that to a NextResponse does work locally in dev mode and on vercel edge.
```ts
    const headers = new Headers(req.headers);
    headers.set('set-header', 'this always works');
    const res = NextResponse.next({
        request: {
            headers: headers,
        },
    });
```
however, this only works locally in dev mode (with and without ---turbo)
```ts
    const headers = new Headers(req.headers);
    const res = NextResponse.next({
        request: {
            headers: headers,
        },
    });
    res.headers.append('add-to-response', 'this only works in dev mode');
```

### Expected behavior
vercel edge should behave the same way as dev mode. If that's not possible, the return of NextResponse shouldn't  have a headers.append() Function.

### Provide environment information

```bash
Local Dev Environment:
Windows 10
Node: v21.1.0
Nextjs: canary
```


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

Middleware / Edge (API routes, runtime)

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

next dev (local), Vercel (Deployed)

### Additional context

_No response_
Repository: rust
Issue: `f32::from(<untyped float>)` inference with `f16` and `f128`
Labels: T-lang,T-libs,F-f16_and_f128

Adding a `From<f16> for f32` impl breaks some inference that currently works. From https://github.com/rust-lang/rust/issues/123824:

```rust
fn main() {
    let x = f32::from(3.14);
}
``` 

The new float types are a long way from being stable, but it may be good to decide how to handle things if we would like this implementation one day. Per @fmease at https://github.com/rust-lang/rust/issues/123824#issuecomment-2050628184, there are three options:

1. Accept this regression since technically, no stable API is broken
2. Say that we do not want `From<f16> for f32`
3. Make this implementation available starting with the new edition

I'll mark this with the edition label so it can at least come into consideration, but this is the lowest priority thing on any list.

Known failure points from adding this directly:
- Fuchsia: https://cs.opensource.google/fuchsia/fuchsia/+/main:src/recovery/lib/recovery-ui/src/keyboard.rs;l=111;drc=e1ed8a47e77b0ea1d6f83b93830c4e975a8a6089 (from https://github.com/rust-lang/rust/issues/123824#issuecomment-2050836467)
-  `taffy`: https://github.com/DioxusLabs/taffy/blob/f1e4edab96ee13f7d1fbc2536ac31633b0e620d6/src/style_helpers.rs#L58 (from https://github.com/rust-lang/rust/issues/123824#issuecomment-2052506991)
- `contour-rs`: https://github.com/mthh/contour-rs/blob/08c1d83a1461aa19543ed402d23908eb55234fd1/src/lib.rs#L488-L491 (from https://github.com/mthh/contour-rs/pull/13#issuecomment-2051652708)
- Bevy: https://github.com/rust-lang/rust/issues/123831#issuecomment-2052981580
- egui: https://github.com/emilk/egui/issues/4352

@rustbot label +T-lang +T-libs +A-edition-2024 +F-f16_and_f128
Repository: godot
Issue: AnimationPlayerEditor crashes sometimes when switching scene tabs
Labels: bug,topic:editor,crash,topic:animation

### Tested versions

Godot v4.3.dev (b2f425fe6)

### System information

Godot v4.3.dev (b2f425fe6) - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3060 (NVIDIA; 31.0.15.1748) - 11th Gen Intel(R) Core(TM) i7-11700F @ 2.50GHz (16 Threads)

### Issue description

With this simple script, you can accidentally crash your editor:
```gdscript
@tool
extends AnimationPlayer

func _process(delta):
	stop()
```
The editor will crash if the Animation editor view displays an animation from the AnimationPlayer node with the script, and the Scene view is selecting a different node then the AnimationPlayer node, if you switch to a different scene tab and back to the current.

### Steps to reproduce

* Open the provided scene
* Click on the AnimationPlayer node in the Scene view
* Click on the Node2D node in the Scene view
* Click the "Add a new scene" button next to the current scene's tab
* Click back to original the "Test" scene
* Editor crashes

### Minimal reproduction project (MRP)

[EditorAnimationPlayerCrash.zip](https://github.com/godotengine/godot/files/14951843/EditorAnimationPlayerCrash.zip)
Repository: ollama
Issue: multilingual-e5-large and multilingual-e5-base Embedding Model Support
Labels: model request

### What are you trying to do?

I want use multilingual-e5-large or multilingual-e5-base as embedding model, because all other embed models dont work for other languages as english.

### How should we solve this?

Convert multilingual-e5-large and multilingual-e5-base (https://huggingface.co/intfloat/multilingual-e5-base) to gguf and integrate it as models in ollama.

### What is the impact of not solving this?

You cannot use ollama for RAG Application with languages other then english.

### Anything else?

_No response_
Repository: PowerToys
Issue: Preview
Labels: Issue-Bug,Product-File Explorer,Needs-Triage

### Microsoft PowerToys version

0.79.0

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

File Explorer: Thumbnail preview

### Steps to reproduce

No funciona la vista previa en explorador de archivos

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: pytorch
Issue: DISABLED test_torchvision_models_efficientnet_b7 (__main__.TestVisionTracing)
Labels: triaged,module: flaky-tests,skipped,module: fx

Platforms: asan, linux, rocm, slow



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

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


Test file path: `test_fx.py`

cc @clee2000 @ezyang @SherlockNoMad @EikanWang @jgong5 @wenzhe-nrv
Repository: PowerToys
Issue: File Explorer Add-ons Support for Email (*.eml) files
Labels: Product-File Explorer

### Description of the new feature / enhancement

Support *.eml (Email message) file format in File Explorer Preview add-ons. 
Possibly also include support for Outlook *.msg format.

### Scenario when this would be used?

Preview the content of email files when saved to File Explorer.

### Supporting information

- Appropriate filtering would need to be in place to disable remote/embedded content and scripts for privacy/security reasons. 
- Option to toggle between Plain-text and HTML-formatted emails.
- Possible use of Message Header Analysis API? (see https://mha.azurewebsites.net)
Repository: rust
Issue: Failed to vectorize the for_each iteration with min function
Labels: A-LLVM,I-slow,A-codegen,C-optimization

<!--
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.
-->

I tried this code:

```rust
#[inline]
fn min_update(dst: &mut u32, lhs: u32){
    if *dst > lhs{
        *dst = lhs;
    }
}

#[inline]
fn min(mut dst: u32, lhs: u32) -> u32 {
    min_update(&mut dst, lhs);
    dst
}

pub fn vectorize_fail(lhs: &[u32], dst: &mut u32)  {
    lhs.iter().for_each(|&x|{
        min_update(dst, x);
    });

}

pub fn vectorize(lhs: &[u32], dst: &mut u32){
    lhs.iter().for_each(|&x|{
        *dst = min(*dst, x);
    });
}

```

I expected to see this happen:  The `vectorize_fail` function will get vectorized

Instead, this happened: The auto-vectorization is not performed, see [godbolt](https://godbolt.org/z/on8E7rv86) for details

### 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`:
```
1.77.0
```

<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Backtrace</summary>
<p>

```
<backtrace>
```

</p>
</details>
Repository: rust
Issue: Borrow checking should identify function returns
Labels: A-borrow-checker,C-bug,NLL-polonius,T-types,fixed-by-polonius

<!--
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.
-->

I tried this code:

```rust
struct Foo {
    val: i32,
    status: i32,
    err_str: String,
}

impl Foo {
    fn bar(self: &mut Self) -> Result<(), &str> {
        if self.val == 0 {
            self.status = -1;
            Err("val is zero")
        } else if self.val < 0 {
            self.status = -2;
            self.err_str = format!("unexpected negative val {}", self.val);
            Err(&self.err_str)
        } else {
            Ok(())
        }
    }
    fn foo(self: &mut Self) -> Result<(), &str> {
        self.bar()?;      // rust reports this line conflicts with the next line
        self.status = 1;  // and this line is the victim
        Ok(())
    }
}

```

I expected to see this happen: *code successful compiles*

Instead, this happened: *code failed to compile because borrow conflicts*

### 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`:
```
binary: rustc
commit-hash: 07dca489ac2d933c78d3c5158e3f43beefeb02ce
commit-date: 2024-02-04
host: x86_64-pc-windows-msvc
release: 1.76.0
LLVM version: 17.0.6
```

### My opnion on this issue
I think rust's borrowing check is too rough and lacks checking of branch capabilities.

As in this example, Rust assumes that returning a value means borrowing from that line to the end of the function, when the reality is that returning means that when return happens, that line is the end of the function. The return value of the previous line should not affect the operation of the following line. In principle, they will not conflict.

<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Reported Error</summary>
<p>

```
error[E0506]: cannot assign to `self.status` because it is borrowed
  --> src\main.rs:22:9
   |
20 |     fn foo(self: &mut Self) -> Result<(), &str> {
   |                  - let's call the lifetime of this reference `'1`
21 |         self.bar()?;      // rust reports this line conflicts with the next line
   |         -----------
   |         |
   |         `self.status` is borrowed here
   |         returning this value requires that `*self` is borrowed for `'1`
22 |         self.status = 1;  // and this line is the victim
   |         ^^^^^^^^^^^^^^^ `self.status` is assigned to here but it was already borrowed
```

</p>
</details>
Repository: godot
Issue: The return value of the function "get_slide_collision()" is not right
Labels: topic:physics,needs testing,topic:2d

### Tested versions

4.0-4.3 versions

### System information

windows 10

### Issue description

I wrote a simple program that uses the keyboard to control the movement of the characterbody2d, and it will apply a force to the rigidbody2d in the direction of movement. When it is in contact with only one rigidbody2d, everything is fine, but when it is sandwiched between rigidbody2d and staticbody2d, it will not be able to move, and the return value of the get_slide_collision() is only staticbody2d, so it cannot push rigidbody2d.

### Steps to reproduce


https://github.com/godotengine/godot/assets/61172240/05fb4b73-f574-4674-9a11-9b928e228533

If the video doesn't play, you can download it

### Minimal reproduction project (MRP)

[test1.zip](https://github.com/godotengine/godot/files/14953550/test1.zip)
Repository: tauri
Issue: [bug] module loading order
Labels: type: bug,status: needs triage

### Describe the bug

In the tauri+vue3+ts project, it is found that the module loading order is not main.ts,App.vue, and then other custom modules, but the custom module will be loaded first.  The pure vue3+ts project did not find this problem.  
 
I created a tauri+vue+ts project with pnpm create Tauri-app, then created a module named xxxhook, and imported this module in App.vue.  The loading sequence is xxxhook.ts -> main.ts -> App.vue.  How to solve this problem 

```
"dependencies": {
    "vue": "^3.3.4",
    "@tauri-apps/api": "^1"
  },
  "devDependencies": {
    "@vitejs/plugin-vue": "^5.0.4",
    "typescript": "^5.0.2",
    "vite": "^5.0.0",
    "vue-tsc": "^1.8.5",
    "@tauri-apps/cli": "^1"
  }
```

### Reproduction

_No response_

### Expected behavior

_No response_

### Full `tauri info` output

```text
No error message is generated
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: ui
Issue: [bug]: Missing TooltipProvider in dashboard-7 block
Labels: bug

### Describe the bug

When I copy/paste the code of this block https://ui.shadcn.com/blocks#dashboard-07 in my nextjs14 app it gives me this error
`Error: Missing TooltipProvider`

I solved it by going to the documentation and wrapped the `Tooltip` component with `TooltipProvider`

### Affected component/components

Tooltip

### How to reproduce

1. Go to https://ui.shadcn.com/blocks#dashboard-07
2. copy code of the block
3. run your application
4. you now should see this error `Error: Missing TooltipProvider`

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Nextjs14
Edge latest version
Shadcn/ui latest version of tooltip component
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: material-ui
Issue: [website] Improve products navbar
Labels: website

### Related page

https://mui.com/material-ui/

### Kind of issue

Broken demo

### Issue description

The Docs page in the navbar in the Documentation is pointless since it serves the same purpose as the products page, it's even worse than the Docs, docs provides buttons to very organized and clear pages that shows all the products available

### Context

I suggest merging these two links into one clear button that offers all users a simpler and straight to the point experience, yes it might be a no brainer for an expert but it might offer a better UX for all types of users.

**Search keywords**: navbar , products, Docs
Repository: flutter
Issue: Add tooling to prevent iOS XCTests tests that do not match the pattern `-(void)test*`
Labels: platform-ios,engine,P2,team-ios,triaged-ios

I noticed two XCTests tests that are not running because their return types are not the expected `void` (fixed in https://github.com/flutter/engine/pull/51983):
```objc
- (bool)testSetWarnsOnOverflow
```
https://github.com/flutter/engine/blob/76a270f6cc31ba3e83cc602f983eb2302dbbe1e8/shell/platform/darwin/common/framework/Source/FlutterChannelsTest.m#L171
```objc
- (bool)testNextResponderShouldThrowOnPressesEnded
```
https://github.com/flutter/engine/blob/76a270f6cc31ba3e83cc602f983eb2302dbbe1e8/shell/platform/darwin/ios/framework/Source/FlutterKeyboardManagerTest.mm#L151

https://developer.apple.com/documentation/xctest/defining_test_cases_and_test_methods?language=objc

Add some kind of lint or tooling check to the engine to detect this case.
Repository: stable-diffusion-webui
Issue: [Feature Request]: Button for 'Respect Preferred VAE" in XYZ plot
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

When using XYZ plot, it seems to use whatever VAE is selected in the UI, not the preferred VAE per checkpoint (as specified in JSON files etc).

Example case: Testing some checkpoints across 1.5 and SDXL. XL model has no VAE (or I get error results), 1.5 checkpoints have a couple different VAEs. While 1.5s can also use the same VAE generally fine, definitely need to switch between 1.5 and XL, and the option to respect preferred even for 1.5 checkpoints would be nice.

### Proposed workflow

1. Go to XYZ plot
2. Press checkbox "respect preferred VAE". If no VAE specified as preferred in JSON, use current selected (ie, same as now).
3. Compare 1.5 and XL checkpoints without image generation glitches or errors! Success. Or, compare models using their specified VAEs, ie, comparing models "best outputs".


### Additional information

Thanks
Repository: tauri
Issue: [bug] v2 tauri - Weird drag behavior on windows
Labels: type: bug,status: needs triage

### Describe the bug

I'm using the library [pragmatic-drag-and-drop](https://www.npmjs.com/package/@atlaskit/pragmatic-drag-and-drop) and trying to allow having a resizable sidebar.  If I don't have the setting `dragDropEnabled` set to false, the onDrag event is never fired. If I do have it set I can drag but the webview isn't updated until the drag event is finished which doesn't look good in the app.

![construct_GfUsOT9naH](https://github.com/tauri-apps/tauri/assets/9022106/1b22f743-f24b-4870-8726-a8ae0b897418)

I'm only concerned with having the drag within the app working if external drop events need to be disabled that's fine. Just not sure what configuration is needed for that. Any advice would be helpful. 

### Reproduction

_No response_

### Expected behavior

I'd expected drag and drop events within the web frontend to work for ondragstart ondrag and ondragend. With and function events in ondrag being run and reflected in the UI as its happening.

### Full `tauri info` output

```text
> tauri "info"


[✔] Environment
    - OS: Windows 10.0.19045 X64
    ✔ WebView2: 123.0.2420.65
    ✔ MSVC: Visual Studio Build Tools 2022
    ✔ rustc: 1.77.1 (7cf61ebde 2024-03-27)
    ✔ cargo: 1.77.1 (e52e36006 2024-03-26)
    ✔ rustup: 1.27.0 (bbb9276d2 2024-03-08)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 20.9.0
    - pnpm: 8.15.1 - using pnpm
    - yarn: 1.22.19
    - npm: 10.2.4
    - bun: 1.1.3

[-] Packages
    - tauri [RUST]: 2.0.0-beta.14
    - tauri-build [RUST]: 2.0.0-beta.11
    - wry [RUST]: 0.39.0
    - tao [RUST]: 0.27.0
    - @tauri-apps/api [NPM]: 2.0.0-beta.7
    - @tauri-apps/cli [NPM]: 2.0.0-beta.12

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: React
    - bundler: Rollup
```


### Stack trace

_No response_

### Additional context

This is the pragmatic drag and drop sample I used as the foundation in case this can provide any help.
https://atlassian.design/components/pragmatic-drag-and-drop/examples/#list
Repository: ui
Issue: [bug]: pagination next icon acting weird
Labels: bug

### Describe the bug

I am using shadecn-vue, on page load next icon is showing in reverse, after using for sometimes it shows correct

### Affected component/components

Pagination

### How to reproduce

add PaginationNext component from shadcn-nuxt/shadcn-vue
<PaginationNext :page="page" />

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Windows 10
Google Chrome
```


### Before submitting

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