sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: [Bug]: Smoke Test broken on 8.0.5, works fine on 8.0.4
Labels: bug,cli,sev:S3,test utilities,upgrade:8.0

### Describe the bug

Running with `--smoke-test` yields an error on 8.0.5, was working fine on prior versions, including 8.0.4.

```
SB_BUILDER-VITE_0001 (NoStatsForViteDevError): Unable to write preview stats as the Vite builder does not support stats in dev mode.

Please remove the `--stats-json` flag when running in dev mode.
    at Object.toJson (/node_modules/@storybook/builder-vite/dist/index.js:58:1486)
    at buildDevStandalone (/node_modules/@storybook/core-server/dist/index.js:66:1832)
    at async withTelemetry (/node_modules/@storybook/core-server/dist/index.js:28:3579)
    at async dev (/node_modules/@storybook/cli/dist/generate.js:663:563)
    at async Command.<anonymous> (/node_modules/@storybook/cli/dist/generate.js:665:250)
```

### To Reproduce

Run storybook with `--smoke-test` 

### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 14.4
    CPU: (16) x64 Intel(R) Xeon(R) W-2140B CPU @ 3.20GHz
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.12.0 - ~/.nvm/versions/node/v18.12.0/bin/node
    Yarn: 3.5.1 - /usr/local/bin/yarn <----- active
    npm: 8.19.2 - ~/.nvm/versions/node/v18.12.0/bin/npm
  Browsers:
    Chrome: 123.0.6312.87
    Edge: 123.0.2420.65
    Safari: 17.4
```


### Additional context

_No response_
Repository: pytorch
Issue: Track the accurate check regress for DebertaForQuestionAnswering and nanogpt
Labels: triaged,oncall: pt2,module: pt2 accuracy,pt2-pass-rate-regression

### 🐛 Describe the bug

I could repro locally.

```
time python benchmarks/dynamo/huggingface.py --backend inductor --amp --accuracy --only DebertaForQuestionAnswering --training 
```

The error message: 
```
E0329 13:56:13.126000 139908396307456 torch/_dynamo/utils.py:1405] RMSE (res-fp64): 0.01772, (ref-fp64): 0.00543 and shape=torch.Size([2]). res.dtype: torch.float32, multiplier: 3.000000, tol: 0.010000
```
indicate that increasing tolerance to 0.02 can make the test pass.

But on the other hand, dashboard run uses a different cuda version (12.1. Local server uses 12.0) and cause different numerical results. According to the error message on the dashboard run
```
2024-03-28T19:23:00.3165713Z E0328 19:23:00.315000 140426862847168 torch/_dynamo/utils.py:1405] RMSE (res-fp64): 0.01778, (ref-fp64): 0.00506 and shape=torch.Size([2]). res.dtype: torch.float32, multiplier: 3.000000, tol: 0.010000
```
we need tolerance 0.03 to pass the test.

I've also done ablation test. I'm on commit 57a9a64e10b84fa8d932482ae9417aa3fc3fbf44 (clean trunk) and then revert #122848, #122841, #121692 in that order, than the test pass again locally.


nanogpt fail for the same reasons.

Update: DebertaForQuestionAnswering starts passing the accurate test from June14 2024.

### Error logs

.

### Minified repro

_No response_

### Versions

.

cc @ezyang @chauhang @penguinwu @msaroufim @bdhirsh @anijain2305 @zou3519 @Chillee
Repository: godot
Issue: Godot cannot create folder in "new project" dialog if there are invalid characters in the name and doesn't scrub input for folders
Labels: enhancement,feature proposal,topic:editor

### Tested versions

- Found in v4.2.1.stable.official, likely reproducible in other versions

### System information

Godot v4.2.1.stable - Windows 10.0.19045 - Vulkan (Forward+) - integrated Intel(R) HD Graphics 530 (Intel Corporation; 31.0.101.2111) - Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz (4 Threads)

### Issue description

If you attempt to create a project with the name having invalid folder characters in the name and press "Create folder", then it will say "cannot create folder". If you manually make a folder without special characters(or temporarily change the name of the project, create the folder, then change the name back), then everything functions normally. What I would expect is for Godot to do some input scrubbing and remove/replace invalid characters in the name,

### Steps to reproduce

1. Attempt to create a project.
2. Name it something with an invalid character(such as a question mark ? in it).
3. Press "Create folder".

### Minimal reproduction project (MRP)

N/A
Repository: pytorch
Issue: [AOTI] error: no match fo r ‘operator=’
Labels: triaged,oncall: pt2,module: aotinductor

### 🐛 Describe the bug

How to repro:

comment out the lines below:

https://github.com/pytorch/pytorch/blob/57a9a64e10b84fa8d932482ae9417aa3fc3fbf44/test/inductor/test_aot_inductor.py#L2328-L2330

and run the following command:

```
$ python test/inductor/test_aot_inductor.py -k test_cond_non_tensor_predicates_dynamic_False_abi_compatible_cpu_with_stack_allocation_and_minimal_arrayref_interface
```

### Versions

PyTorch version: 2.3.0a0+git57a9a6
Is debug build: True
CUDA used to build PyTorch: 12.0
ROCM used to build PyTorch: N/A

cc @ezyang @msaroufim @bdhirsh @anijain2305 @zou3519 @chauhang @desertfire
Repository: vscode
Issue: Selecting symbol from notebook outline doesn't highlight in editor properly
Labels: bug,notebook-toc-outline


Type: <b>Bug</b>

* Single click or double click on a symbol under a code cell in the notebook outline view
* It navigates to the cell
* However it doesn't highlight the line or selects the symbol like text editor

VS Code version: Code - Insiders 1.88.0-insider (aa25485166449aa0f9eb8ebd8d0b70376108633c, 2024-03-28T22:10:25.599Z)
OS version: Windows_NT x64 10.0.22631
Modes:

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

|Item|Value|
|---|---|
|CPUs|AMD Ryzen 5 7600X 6-Core Processor              (12 x 4700)|
|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>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|undefined|
|Memory (System)|31.16GB (5.59GB free)|
|Process Argv|--enable-proposed-api ms-vscode.dscopilot-agent --enable-proposed-api ms-toolsai.datawrangler --crash-reporter-id acfa600b-65c9-4131-81cf-ad8200ffb7d3|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (27)</summary>

Extension|Author (truncated)|Version
---|---|---
esbuild-problem-matchers|con|0.0.3
vscode-eslint|dba|2.4.4
vscode-deno|den|3.36.0
gitlens|eam|2024.3.2805
EditorConfig|Edi|0.16.4
prettier-vscode|esb|10.4.0
copilot|Git|1.176.0
copilot-chat|Git|0.14.2024032701
vscode-pull-request-github|Git|0.85.2024032704
vscode-mocha-test-adapter|hbe|2.14.1
vscode-test-explorer|hbe|2.21.1
vscode-dotnet-runtime|ms-|2.0.3
black-formatter|ms-|2024.1.10861010
debugpy|ms-|2024.2.0
isort|ms-|2023.10.1
python|ms-|2024.3.10871011
vscode-pylance|ms-|2024.3.102
datawrangler|ms-|0.29.6
jupyter|ms-|2024.3.2024032701
jupyter-keymap|ms-|1.1.2
jupyter-renderers|ms-|1.0.17
vscode-jupyter-cell-tags|ms-|0.1.8
vscode-jupyter-slideshow|ms-|0.1.5
remote-containers|ms-|0.353.0
extension-test-runner|ms-|0.0.6
test-adapter-converter|ms-|0.1.9
vscode-github-issue-notebooks|ms-|0.0.130


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

```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
vsaa593:30376534
py29gd2263:30784851
vscaat:30438846
c4g48928:30535728
962ge761:30841072
pythongtdpath:30726887
welcomedialogc:30812479
pythonidxpt:30768918
pythonnoceb:30776497
asynctok:30898717
dsvsc013:30777762
dsvsc014:30777825
dsvsc015:30821418
pythontestfixt:30866404
pythonregdiag2:30926734
pyreplss1:30879911
pythonmypyd1:30859725
pythoncet0:30859736
h48ei257:31000450
pythontbext0:30879054
accentitlementst:30870582
dsvsc016:30879898
dsvsc017:30880771
dsvsc018:30880772
bf62j303:30968145
cppperfnew:30980852
d34g3935:30961436
fegfb526:30952798
bg6jg535:30979844
ccp2r3:30958153
pythonait:30973460
gee8j676:30988845
g1icg217:30999571

```

</details>

<!-- generated by issue reporter -->
Repository: pytorch
Issue: [AOTI] KeyError: 'torch.complex32
Labels: triaged,oncall: pt2,module: aotinductor

### 🐛 Describe the bug

How to repro:

comment out the line below:

https://github.com/pytorch/pytorch/blob/57a9a64e10b84fa8d932482ae9417aa3fc3fbf44/test/inductor/test_aot_inductor.py#L2332

and run the following command:

```
$ python test/inductor/test_aot_inductor.py -k test_runtime_checks_complex_abi_compatible_cpu_with_stack_allocation_and_minimal_arrayref_interface
```

### Versions

PyTorch version: 2.3.0a0+git57a9a6
Is debug build: True
CUDA used to build PyTorch: 12.0
ROCM used to build PyTorch: N/A

cc @ezyang @msaroufim @bdhirsh @anijain2305 @zou3519 @chauhang @desertfire
Repository: rust
Issue: Consider splitting unused_import's glob re-export visibility warning into its own lint
Labels: A-lints,A-diagnostics,T-lang,T-compiler,C-bug,L-unused_imports

### Code

```Rust
mod foo {
    pub use bar::*;
    mod bar {
        pub(crate) fn baz() {}
    }
}

fn main() {
    foo::baz();
}
```


### Current output

```Shell
warning: glob import doesn't reexport anything because no candidate is public enough
 --> src/main.rs:2:13
  |
2 |     pub use bar::*;
  |             ^^^^^^
  |
  = note: `#[warn(unused_imports)]` on by default
```


### Desired output

_No response_

### Rationale and extra context

An unused import lint feels wrong to be because i am using `baz`.

### Other cases

_No response_

### Rust Version

```Shell
rustc 1.75.0 (82e1608df 2023-12-21)
binary: rustc
commit-hash: 82e1608dfa6e0b5569232559e3d385fea5a93112
commit-date: 2023-12-21
host: aarch64-apple-darwin
release: 1.75.0
LLVM version: 17.0.6
```


### Anything else?

_No response_
Repository: flutter
Issue: [Windows] Improve performance by removing intermediary texture & blit
Labels: engine,platform-windows,P3,team-windows,triaged-windows

### Background
The engine asks the Windows embedder for "backing stores" to render into. Today, the engine treats backing stores of the same size as fully interchangeable.

This is a problem as Windows's EGL surfaces are specific to a view. As a result, Windows's EGL surfaces cannot be used directly as a backing store. Instead, the Windows embedder creates intermediary textures for the engine's backing stores. The Windows embedder then blits these intermediary textures to the correct window surface.

This approach has drawbacks:

1. It greatly increases memory usage (a window needs a front buffer, a back buffer, and an intermediary texture).
2. It requires a blit from the intermediary texture to the back buffer.

### Solution

This design https://github.com/flutter/flutter/issues/145522 makes the Flutter engine's backing stores view specific.

Once this lands, the Windows embedder should use the window's back buffer as the backing store.

Part of https://github.com/flutter/flutter/issues/142845
Repository: go
Issue: crypto/ecdh: TestLinker failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "crypto/ecdh" && test == "TestLinker"
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/abcf922a843e1c6c85d567d63904df6807e3b3d8)):

    --- FAIL: TestLinker (0.36s)
        ecdh_test.go:481: unexpected symbol in program using only ecdh.P384: crypto/internal/nistec.NewP256Point
        ecdh_test.go:481: unexpected symbol in program using only ecdh.P384: crypto/internal/nistec.NewP521Point


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: flutter
Issue: [Impeller] `advanced_blend.frag` is handling `dst_input_alpha` incorrectly
Labels: P2,e: impeller,team-engine,triaged-engine

In `advanced_blend.frag` the following math is happening with `dst_input_alpha`.

```glsl
    f16vec4 dst = IPHalfUnpremultiply(premultiplied_dst);
    dst *= blend_info.dst_input_alpha;
    //...
    frag_color = IPApplyBlendedColor(dst, src, blend_result);
```

That is effectively turning `dst` to a premultiplied color, but `IPApplyBlendedColor` is assuming it's inputs are unpremultiplied.

There doesn't seem to be a test for this and the hard part is reproducing it in a test.  It is speculated that this can be hit on all backends with the the "foreground" advanced blend path.

cc @bdero
Repository: vscode
Issue: Notebook>Outline: Show Code Cell Markdown
Labels: feature-request,notebook-toc-outline


Type: <b>Feature Request</b>

It is possible to generate markdown by a code cell, which is rendered in the output, and displayed after the cell. (This is how plots are rendered.)
Jupyterlab accepts titles in this output for its Outline, along with markdown cells.  A use case it that this can be dynamic, as it is generated by the code in the cell. 
So my request is for an option to do this--or to just behave like Jupterlab.


VS Code version: Code 1.87.2 (863d2581ecda6849923a2118d93a088b0745d9d6, 2024-03-08T15:20:17.278Z)
OS version: Windows_NT x64 10.0.26085
Modes:
Remote OS version: Linux x64 4.18.0-372.32.1.el8_6.x86_64
Remote OS version: Linux x64 5.15.150.1-microsoft-standard-WSL2


<!-- generated by issue reporter -->
Repository: kubernetes
Issue: apimachinery resource.Quantity primitive values should be public for recursive hashing
Labels: sig/api-machinery,kind/feature,triage/accepted

### What would you like to be added?

API Machinery resource.Quantity{} has primitive values that represent the quantity of the resource it represents [here](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apimachinery/pkg/api/resource/quantity.go#L101-L106), represented through private variables. Since these are private, not public, this prevents controllers that hash CRDs with libraries like https://github.com/mitchellh/hashstructure, which recursively walk through the structs, from properly identifying changes made to the quantity.

### Why is this needed?

In github.com/kubernetes-sigs/karpenter, we hash our CRDs and use hash comparisons to detect spec-Drift, similar to pods/deployments. We use this for fields like kubeReserved and systemReserved, which impacts the allocatable resources on bin-packing. If a user defines a different kubeReserved memory value, we want to be able to detect this as a change in our hashing/caching logic, but since it's private, we just have to wait for our cache values to expire before it's refreshed.

As a workaround, we're changing our v1.ResourceList type variables to type map[string]string where we then have to parse + validate each of the key value pairs as resource quantities, but it would be nice if this type of workflow was supported natively by making the values public, or at least making a public facing value that's generated from the private values.

Is there a reason these fields are private? Is this something that would be supported?
Repository: go
Issue: x/tools/go/packages: Consider giving consumers control over type-checking behaviour
Labels: NeedsInvestigation,FeatureRequest,Tools

The doc comment for the field `packages.Config.ParseFile` says:

> An application may supply a custom implementation of ParseFile
> to change the effective file contents or the behavior of the parser,
> or to modify the syntax tree. For example, selectively eliminating
> unwanted function bodies can significantly accelerate type checking.

However, doing so (even when preserving semantic correctness) easily results in a bunch of errors being emitted about unused imports and other global identifiers.

Since the type-checker has an option `types.Config.IgnoreFuncBodies` that controls whether function bodies are checked, it would be nice if consumers of the package loader were able to configure that either per package (ideally) or at least globally.
At the moment, the flag is only used internally for dependencies when NeedDeps is not set.

Another nice addition would be the ability to have distinct but overlapping calls to `packages.Load` (with the same config) share the same type-checking `Object`s (see #61418, #61412 for related, but different issues) and maybe even the same package graph. Such a feature would allow incremental, on-demand refinement of package information while still keeping the ability to reason about types globally, and avoiding duplicated work.
Repository: go
Issue: gonum.org/v1/plot/plotter: unrecognized failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "gonum.org/v1/plot/plotter" && test == ""
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/acb3a6859f792f10561bde8df7222a1fa3ce6733)):

    ../../../../pkg/mod/gonum.org/v1/plot@v0.10.1/plotter/conrec.go:79:2: internal compiler error: 'conrec': conrec h (type [5]float64) recorded as live on entry
    
    goroutine 355 [running]:
    runtime/debug.Stack()
    	runtime/debug/stack.go:26 +0x78
    cmd/compile/internal/base.FatalfAt({0x2e, 0x4f021}, {0x40a37d0, 0x25}, {0x43be0c0, 0x3, 0x3})
    	cmd/compile/internal/base/print.go:225 +0x288
    cmd/compile/internal/base.Fatalf(...)
    	cmd/compile/internal/base/print.go:194
    cmd/compile/internal/ssagen.(*ssafn).Fatalf(0x3d23b00, {0x2e, 0x4f021}, {0xac9f51, 0x1f}, {0x43b89a0, 0x2, 0x2})
    	cmd/compile/internal/ssagen/ssa.go:8201 +0x1a0
    cmd/compile/internal/ssa.(*Func).Fatalf(0x3e11968, {0xac9f51, 0x1f}, {0x43b89a0, 0x2, 0x2})
    	cmd/compile/internal/ssa/func.go:741 +0x2b8
    cmd/compile/internal/liveness.computeIntervals(0x3d41748, 0x4319b10)
    	cmd/compile/internal/liveness/mergelocals.go:656 +0xcd8
    cmd/compile/internal/liveness.MergeLocals(0x28cf6b8, 0x3e11968)
    	cmd/compile/internal/liveness/mergelocals.go:86 +0x10c
    cmd/compile/internal/ssagen.(*ssafn).AllocFrame(0x3d23b00, 0x3e11968)
    	cmd/compile/internal/ssagen/pgen.go:157 +0x2dc
    cmd/compile/internal/ssagen.buildssa(0x28cf6b8, 0x3)
    	cmd/compile/internal/ssagen/ssa.go:576 +0x2818
    cmd/compile/internal/ssagen.Compile(0x28cf6b8, 0x3)
    	cmd/compile/internal/ssagen/pgen.go:278 +0x38
    cmd/compile/internal/gc.compileFunctions.func5.1(0x3)
    	cmd/compile/internal/gc/compile.go:182 +0x38
    cmd/compile/internal/gc.compileFunctions.func3.1()
    	cmd/compile/internal/gc/compile.go:164 +0x38
    created by cmd/compile/internal/gc.compileFunctions.func3 in goroutine 33
    	cmd/compile/internal/gc/compile.go:163 +0x250


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: x/mod/sumdb/tlog: TestClientLookup failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "golang.org/x/mod/sumdb/tlog" && test == "TestClientLookup"
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/5f6a71352bc4becbf9120a3a97eb51b14cf65ad9)):

    --- FAIL: TestClientLookup (0.00s)
        client_test.go:29: rsc.io/sampler@v1.3.0: checking tree#1 against tree#3: downloaded inconsistent tile


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: x/mod/sumdb/tlog: TestClientBadTiles failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "golang.org/x/mod/sumdb/tlog" && test == "TestClientBadTiles"
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/626fda3ab8e246ef9b4525c02d3f558a52e2f60f)):

    --- FAIL: TestClientBadTiles (0.00s)
        client_test.go:72: rsc.io/sampler@v1.3.0: checking tree#1 against tree#3: downloaded inconsistent tile


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: x/mod/sumdb/tlog: TestClientFork failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "golang.org/x/mod/sumdb/tlog" && test == "TestClientFork"
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/5f6a71352bc4becbf9120a3a97eb51b14cf65ad9)):

    --- FAIL: TestClientFork (0.00s)
        client_test.go:102: rsc.io/pkg1@v1.5.2: checking tree#1 against tree#5: downloaded inconsistent tile


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: crypto/ecdsa: TestECDH failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "crypto/ecdsa" && test == "TestECDH"
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/5c845cea3853528121a86e43e50deb7aac0b8ac0)):

    --- FAIL: TestECDH (0.00s)
        --- FAIL: TestECDH/P256 (0.00s)
            ecdh_test.go:51: P256 point not on curve
    panic: runtime error: invalid memory address or nil pointer dereference [recovered]
    	panic: runtime error: invalid memory address or nil pointer dereference
    [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x15726c]
    
    goroutine 7 gp=0xc0000036c0 m=0 mp=0x2ee960 [running]:
    panic({0x179140?, 0x2e3c10?})
    	/workdir/go/src/runtime/panic.go:778 +0x188 fp=0xc0000ad868 sp=0xc0000ad7a8 pc=0x4d428
    ...
    crypto/ecdh_test.TestECDH(0xc00008c680?)
    	/workdir/go/src/crypto/ecdh/ecdh_test.go:39 +0x34 fp=0xc00006bf30 sp=0xc00006bf00 pc=0x154214
    testing.tRunner(0xc00008c680, 0x1c3d80)
    	/workdir/go/src/testing/testing.go:1689 +0x118 fp=0xc00006bf90 sp=0xc00006bf30 pc=0xf9ee8
    testing.(*T).Run.gowrap1()
    	/workdir/go/src/testing/testing.go:1742 +0x50 fp=0xc00006bfc0 sp=0xc00006bf90 pc=0xfae30
    runtime.goexit({})
    	/workdir/go/src/runtime/asm_ppc64x.s:1018 +0x4 fp=0xc00006bfc0 sp=0xc00006bfc0 pc=0x8c5e4
    created by testing.(*T).Run in goroutine 1
    	/workdir/go/src/testing/testing.go:1742 +0x398


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: rust
Issue: Redundant instructions involving indexing with `bool`s
Labels: A-LLVM,I-slow,A-codegen,E-needs-test,T-compiler,I-heavy,C-optimization

I tried this code:

```rust
fn f(a: u32, b: bool, c: bool, d: &mut [u128; 2]) {
    let mut a = a & 1 != 0;
    if b {
        a ^= c;
        d[0] |= 1;
    }
    d[a as usize] |= 1;
}
```

It compiles to the following assembly:

```asm
f:
        test    esi, esi
        je      .LBB0_1
        xor     dil, dl
        or      byte ptr [rcx], 1
        jmp     .LBB0_3
.LBB0_1:
        and     dil, 1
.LBB0_3:
        movzx   eax, dil
        and     eax, 1
        shl     eax, 4
        or      byte ptr [rcx + rax], 1
        ret
```

The `jmp .LBB0_3` and `and dil, 1` instructions are useless, because `dil` is moved to `eax` and `and`ed with `1` there anyway, and `dil` is not used anywhere.

The output improves if you avoid using `bool`s.

[godbolt](https://godbolt.org/z/6KE6jd15x)

### Meta

`rustc --version --verbose`:
```
rustc 1.79.0-nightly (c9f8f3438 2024-03-27)
binary: rustc
commit-hash: c9f8f3438a8134a413aa5d4903e0196e44e37bbc
commit-date: 2024-03-27
host: x86_64-unknown-linux-gnu
release: 1.79.0-nightly
LLVM version: 18.1.2
Compiler returned: 0
```

@rustbot modify labels: -C-bug +C-optimization +A-codegen +A-LLVM +I-slow +I-heavy
Repository: go
Issue: crypto/ecdsa: TestSignAndVerify failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "crypto/ecdsa" && test == "TestSignAndVerify"
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/5c845cea3853528121a86e43e50deb7aac0b8ac0)):

    --- FAIL: TestSignAndVerify (0.00s)
        --- FAIL: TestSignAndVerify/P256 (0.00s)
            ecdsa_test.go:87: Verify failed


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: ollama
Issue: Qwen1.5-MoE
Labels: model request

### What model would you like?

The code of Qwen1.5-MoE has been in the latest Hugging face transformers and we advise you to build from source with command , or you might encounter the following error:pip install git+https://github.com/huggingface/transformers