sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: net/http: TestServerCancelsReadTimeoutWhenIdle/h2 failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "net/http" && test == "TestServerCancelsReadTimeoutWhenIdle/h2"
```

Issue created automatically to collect these failures.

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

    === RUN   TestServerCancelsReadTimeoutWhenIdle/h2
    === PAUSE TestServerCancelsReadTimeoutWhenIdle/h2
    === CONT  TestServerCancelsReadTimeoutWhenIdle/h2
        serve_test.go:5942: Server.Config.ReadTimeout = 10ms
        clientserver_test.go:282: server log: http: TLS handshake error from 127.0.0.1:63166: write tcp 127.0.0.1:63167->127.0.0.1:63166: i/o timeout
        serve_test.go:6038: retrying after error with duration 10ms: Get: Get "https://127.0.0.1:63167": EOF
        serve_test.go:5942: Server.Config.ReadTimeout = 50ms
        clientserver_test.go:282: server log: http: TLS handshake error from 127.0.0.1:63161: write tcp 127.0.0.1:63162->127.0.0.1:63161: i/o timeout
        serve_test.go:6038: retrying after error with duration 50ms: Get: Get "https://127.0.0.1:63162": EOF
        serve_test.go:5942: Server.Config.ReadTimeout = 250ms
        clientserver_test.go:282: server log: http: TLS handshake error from 127.0.0.1:63159: write tcp 127.0.0.1:63160->127.0.0.1:63159: i/o timeout
        serve_test.go:6038: retrying after error with duration 250ms: Get: Get "https://127.0.0.1:63160": EOF
        serve_test.go:5942: Server.Config.ReadTimeout = 1s
        clientserver_test.go:282: server log: http: TLS handshake error from 127.0.0.1:63155: write tcp 127.0.0.1:63156->127.0.0.1:63155: i/o timeout
        serve_test.go:6038: retrying after error with duration 1s: Get: Get "https://127.0.0.1:63156": EOF
        serve_test.go:5942: Server.Config.ReadTimeout = 2s
        clientserver_test.go:282: server log: http: TLS handshake error from 127.0.0.1:63132: write tcp 127.0.0.1:63133->127.0.0.1:63132: i/o timeout
        serve_test.go:6036: failed with duration 2s: Get: Get "https://127.0.0.1:63133": EOF
    --- FAIL: TestServerCancelsReadTimeoutWhenIdle/h2 (5.77s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: rust
Issue: Tracking Issue for de-stabilizing (and eventually removing?) the old serialization infrastructure (feature gate: rustc_encodable_decodable)
Labels: T-libs-api,C-tracking-issue

This tracks the progress on https://github.com/rust-lang/libs-team/issues/272. That issue says that  #105572 will cause  `rustc-serialize` to stop building; it seems like a semver-compatible update was released to avoid that, so currently that crate can still be used on stable. Since Rust 1.79, the future compatibility report shows this as a warning (even for dependencies).

Implementation:
- https://github.com/rust-lang/rust/pull/116016
- https://github.com/rust-lang/rust/pull/134272
Repository: vscode
Issue: Swap button in replace modal
Labels: feature-request,editor-find

<!-- ⚠️⚠️ 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 think there should be a button in the replace modal to switch Find ↔️ Replace

E.g:

![Image](https://github.com/user-attachments/assets/7247e8dc-fdc0-4ffc-8656-0417dd33bce7)

In the context of the above image, there should be a button like `↔️`. When clicked, the value in the 'find' field should swap with the value in the 'replace' field. For example, in our case: clicking the 'Swap' button would result in 'that' becoming 'this' and 'this' becoming 'that'.
Repository: ollama
Issue: Using structured output with tools always produces empty tool_calls array
Labels: bug,needs more info

### What is the issue?

With OpenAI API, you can pass both tools and response_format. In case model wants to call tools, message will be `null` and tools will be called.

With Ollama, it appears that when response_format is present as JSON schema, the tool calls is an empty array, despite model wanting to call the tools.



### OS

macOS

### GPU

Apple

### CPU

Apple

### Ollama version

0.5.1
Repository: ui
Issue: [feat]: Implement components that are present in nextui, but not in shadcn
Labels: area: request

### Feature description

From https://github.com/mikesol/purescript-deku/issues/134#issue-2569970444

- **Only in nextui**: Components like Autocomplete, Chip, Circular Progress, Code, Date Input, Image, Kbd, Navbar, Range Calendar, Scroll Shadow, and User are specific to nextui.


### Affected component/components

Components like Autocomplete, Chip, Circular Progress, Code, Date Input, Image, Kbd, Navbar, Range Calendar, Scroll Shadow, and User

### Additional Context

_No response_

### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues and PRs
Repository: pytorch
Issue: Proper support for optionals in TorchScript
Labels: oncall: jit

### 🚀 The feature, motivation and pitch

This came up as part of https://github.com/pytorch/pytorch/pull/142326.

TorchScript should support `Optional[T]` or `T | None` annotations correctly. Currently something basic like the following fails:

```py
import torch

class MyScriptModule(torch.nn.Module):
    bias: torch.Tensor | None

    def __init__(self, use_bias: bool = True):
        super().__init__()
        if use_bias:
            self.bias = torch.nn.Parameter(torch.tensor(1.0))
        else:
            self.bias = None

    def forward(self, input):
        if self.bias is not None:
            return input + self.bias
        else:
            return input

my_script_module = torch.jit.script(MyScriptModule())
```

The TorchScript compilation here fails, because TorchScript does not handle `bias: Optional[torch.Tensor]` correctly. Note that this is a fairly common pattern, so supporting it properly would be quite valuable.

What's even worse: The example can be compiled by using a **wrong** type annotation `bias: torch.Tensor` or omitting the type annotation, which implicitly also results in a **wrong** type annotation due to how `__getattr__` is typed (falsely promising non-optionality). Of course that is pretty bad, because we are forced to lie to the type checker, sweeping bugs under the carpet.

---

Possibly related to https://github.com/pytorch/pytorch/issues/75002


cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel
Repository: rust
Issue: Tracking issue for release notes of #133392: Fix ICE when multiple supertrait substitutions need assoc but only one is provided
Labels: relnotes,T-types,relnotes-tracking-issue


This issue tracks the release notes text for #133392.

### Steps

- [ ] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [ ] Issue is nominated for release team review of clarity for wider audience.
- [ ] Release team includes text in release notes/blog posts.

### Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

````markdown
# Compatibility Notes
- [Error if multiple super-trait instantiations of `dyn Trait` need assoc but only one is provided](https://github.com/rust-lang/rust/pull/133392)
````

> [!TIP]
> Use the [previous releases](https://doc.rust-lang.org/nightly/releases.html) categories to help choose which one(s) to use.
> The category will be de-duplicated with all the other ones by the release team.
>
> *More than one section can be included if needed.*

### Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
*Otherwise leave it empty.*

````markdown
````

cc @compiler-errors, @lcnr -- origin issue/PR authors and assignees for starting to draft text
Repository: rust
Issue: Tracking issue for release notes of #132325: rework winnowing to sensibly handle global where-bounds
Labels: relnotes,T-types,relnotes-tracking-issue


This issue tracks the release notes text for #132325.

### Steps

- [ ] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [ ] Issue is nominated for release team review of clarity for wider audience.
- [ ] Release team includes text in release notes/blog posts.

### Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

````markdown
# Compatibility notes
- [Disable potentially incorrect type inference if there are trivial and non-trivial where-clauses](https://github.com/rust-lang/rust/pull/132325)
````

> [!TIP]
> Use the [previous releases](https://doc.rust-lang.org/nightly/releases.html) categories to help choose which one(s) to use.
> The category will be de-duplicated with all the other ones by the release team.
>
> *More than one section can be included if needed.*

### Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
*Otherwise leave it empty.*

````markdown
````

cc @lcnr, @compiler-errors -- origin issue/PR authors and assignees for starting to draft text
Repository: vscode
Issue: Breakpoint over line number
Labels: feature-request,debug

<!-- ⚠️⚠️ 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. -->

Hello vscode developers,

I would like the option to have my breakpoints on the line numbers instead of on the side, similar to intellij ide.

# Example
![Image](https://github.com/user-attachments/assets/ceb7681d-71f2-464a-8cb9-a96f33498bd8)

My current vs code version: 1.95

Thank you
Repository: go
Issue: slices: redundant comparison in BinarySearchFunc
Labels: Performance,WaitingForInfo,NeedsInvestigation

### Go version

go version go1.23.4 windows/amd64

### Output of `go env` in your module/workspace:

```shell
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\telic\AppData\Local\go-build
set GOENV=C:\Users\telic\AppData\Roaming\go\env
set GOEXE=.exe
set GOEXPERIMENT=aliastypeparams
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=C:\Users\telic\go\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\telic\go
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=C:\Program Files\Go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLCHAIN=auto
set GOTOOLDIR=C:\Program Files\Go\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.23.4
set GODEBUG=gotypesalias=1
set GOTELEMETRY=local
set GOTELEMETRYDIR=C:\Users\telic\AppData\Roaming\go\telemetry
set GCCGO=gccgo
set GOAMD64=v1
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=C:\Code\Go\playground\go.mod
set GOWORK=C:\Code\Go\go.work
set CGO_CFLAGS=-O2 -g
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-O2 -g
set CGO_FFLAGS=-O2 -g
set CGO_LDFLAGS=-O2 -g
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=C:\Users\telic\AppData\Local\Temp\go-build1876904163=/tmp/go-build -gno-record-gcc-switches
```


### What did you do?

Ran [this code](https://go.dev/play/p/MFinklsK3-g).

### What did you see happen?

Three comparisons being made.

### What did you expect to see?

Two comparisons.

BinarySearchFunc always does a final comparison for its boolean return value, even though the slice element in question and the target might already have been compared. Since the comparison function could potentially be costly, this should be avoided.
Repository: ui
Issue: [bug]: ShadCN Installer asking for tailwind.config.ts but it Version 4
Labels: bug

### Describe the bug

auto install is asking for `tailwind.config.ts` and I moved on tailwindcss v4

### Affected component/components

Accordion

### How to reproduce

1.  ➜  pnpm dlx shadcn@latest add accordion

✔ Checking registry.
⠋ Updating tailwind.config.ts
Something went wrong. Please check the error below for more details.
If the problem persists, please open an issue on GitHub.

ENOENT: no such file or directory, open '/Users/gio/Dev/nextjs15-template/tailwind.config.ts'

➜   git:(master) ✗ npx shadcn@latest add accordion

Need to install the following packages:
shadcn@2.1.7
Ok to proceed? (y) npm ERR! canceled

npm ERR! A complete log of this run can be found in: /Users/gio/.npm/_logs/2024-12-14T15_27_57_257Z-debug-0.log
➜  git:(master) ✗ 



### Codesandbox/StackBlitz link

the installer is looking  tailwind.config.ts but it Version 4

### Logs

```bash
➜  nextjs15-template git:(master) ✗ pnpm dlx shadcn@latest add accordion

✔ Checking registry.
⠋ Updating tailwind.config.ts
Something went wrong. Please check the error below for more details.
If the problem persists, please open an issue on GitHub.

ENOENT: no such file or directory, open '/Users/gio/Dev/nextjs15-template/tailwind.config.ts'

➜  nextjs15-template git:(master) ✗ npx shadcn@latest add accordion

Need to install the following packages:
shadcn@2.1.7
Ok to proceed? (y) npm ERR! canceled

npm ERR! A complete log of this run can be found in: /Users/gio/.npm/_logs/2024-12-14T15_27_57_257Z-debug-0.log
➜  nextjs15-template git:(master) ✗
```


### System Info

```bash
No binaries necessary
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: godot
Issue: set_deferred does not throw error with invalid arguments
Labels: bug,topic:core

### Tested versions

v4.3.stable.mono.official [77dcf97d8]

v4.3.stable.official [77dcf97d8]

v4.0.stable.mono.official [92bee43ad]

v4.4.dev.custom_build [dc5f1b7a2]

### System information

Godot v4.3.stable.mono - Ubuntu 22.04.5 LTS 22.04 - X11 - GLES3 (Compatibility) - RENOIR (renoir, LLVM 15.0.7, DRM 3.57, 6.8.0-49-generic) - AMD Ryzen 5 5500U with Radeon Graphics (12 Threads)

### Issue description

When using `set_deferred` with an non-existent property, or with an invalid value no error message gets thrown.
For example calling `set_deferred("Disabled", true)` in a CollisionShape2D will not make the shape disabled, due to property names not being capitalized, and thus the correct name being `"disabled"`. However this will not throw an error during runtime, making the issue needlessly hard to debug. 

Similarly using an invalid value on a property, like `set_deferred("position", "abc")` also doesn't throw an error, while also not affecting the provided property.

This issue is especially annoying when coding in C#, due to C# Properites using PascalCase, making it more likely to accidentally misspell a Property.

### Steps to reproduce

create a Sprite2D Node, add a Texture and add the following script 

```gdscript
extends Sprite2D

func _process(delta: float) -> void:
	if (Input.is_action_just_pressed("ui_accept")):
		# doesn't change the visibility of the node
		# due to the property name being "visible" (not capitalized) and not "Visible" (capitalized)
		set_deferred("Visible", !visible)

		# uncommenting the following line toggles the Visibility as expected
		# set_deferred("visible", !visible)
		
		# doesn't do anything due to the Property 'asdf' not existing
		set_deferred("asdf", true)
		
		# doesn't do anything, due to material not accepting floats
		set_deferred("material", 1.0)
```
Pressing 'Enter' does effectively nothing, and no error will be thrown during runtime or in the editor.

----
The provided MRP contains 2 Sprite2Ds, the one on the left has the script above attached, while the one on the right has a functioning script, which toggles the visibility as expected, attached.

### Minimal reproduction project (MRP)

[set_deferred_problem_MRP.zip](https://github.com/user-attachments/files/18136450/set_deferred_problem_MRP.zip)
Repository: godot
Issue: VisualShader: Naming Texture2DParameter "AO" breaks shader
Labels: bug,topic:editor,topic:shaders

### Tested versions

4.4 dev6

### System information

Godot v4.4.dev6 - Windows 10.0.19045 - Multi-window, 1 monitor - Vulkan (Forward+) - dedicated AMD Radeon RX 580 2048SP (Advanced Micro Devices, Inc.; 31.0.21921.1000) - Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz (4 threads)

### Issue description

Naming texture2DParameter "AO" breaks the shader, as seen in the first image. Second image is the same node setup with the name changed.

![Image](https://github.com/user-attachments/assets/9c6e9eb8-cead-4645-9575-89b03c0e3bb7)

![Image](https://github.com/user-attachments/assets/2b88e575-17cc-45e1-b385-35fc60f1028e)


### Steps to reproduce

Texture2DParameter connected to samplerPort, name Texture2DParameter "AO"

### Minimal reproduction project (MRP)

Any project
Repository: go
Issue: x/website: automatic URL fragments for sub-sections of 'Minor changes to the library' are overly repetitive
Labels: help wanted,NeedsInvestigation,website

Is something duplicating the fragment names in the release notes?

https://tip.golang.org/doc/go1.24#gotypespkggotypes
https://tip.golang.org/doc/go1.24#encodingjsonpkgencodingjson
https://tip.golang.org/doc/go1.24#archivepkgarchive

I'd expect just `archive` or `pkgarchive` at most.

Others are pretty: https://tip.golang.org/doc/go1.24#runtime (which is why I guess the `pkg` is in there, to distinguish it from https://tip.golang.org/doc/go1.24#runtimepkgruntime ... but that's two `runtime` in that fragment)

/cc @dmitshur
Repository: svelte
Issue: Unify `intro`/`outro` defaults
Labels: breaking change,needs discussion

### Describe the problem

[`5.13.0`](https://github.com/sveltejs/svelte/releases/tag/svelte%405.13.0) adds the `outro` option for `unmount` with default `false`.
`mount` has an `intro` option with default `true`.

### Describe the proposed solution

Use the same default for both options.

(Probably would need to happen in a major release.)

### Importance

nice to have
Repository: vscode
Issue: RPM %post scriplet deletes /usr/local/bin/code
Labels: bug,install-update,rpm

<!-- ⚠️⚠️ 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.96.0 (RPM from the Microsoft repo)
- OS Version: Fedora 41

The `%post` scriptlet in the RPM spec file deletes `/usr/local/bin/code` even if it doesn't belong to a previous vscode installation. This is very irritating because it's the easiest way to append arbitrary command line arguments such as `--ozone-platform=wayland` **system-wide**. Please either add some validation before deleting it, or just stop deleting it altogether.

https://github.com/microsoft/vscode/blob/1.96.0/resources/linux/rpm/code.spec.template#L48-L51

Steps to Reproduce:

1. Install a script at `/usr/local/bin/code` which launches `/usr/bin/code` with extra arguments
2. Reinstall the RPM file provided by Microsoft
3. `/usr/local/bin/code` is now deleted
Repository: angular
Issue: Add more granular scope to @let syntax
Labels: area: core

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

compiler-cli

### Description

Currently, the scope for a local variable in Angular is limited to each block such as @for, @if, or @switch. Because of this, it's not possible to reuse variables in a more generic way, as I showed in the example. Initially, I would like to use @addressFormControls for multiple individual mat-form-field elements, so that in each of them I could use a nested variable with a generic name like controls. Unfortunately, I get an error because the name repeats what is defined above.

```
    <!-- First variable -->
    @let addressFormControls = employeeOffboardForm.controls.address.controls; 
    <div class="offboard__form-row">
      <mat-form-field subscriptSizing="dynamic">
        // it's ok to use nested variable
        @let control = addressFormControls.streetLine; 
        <mat-label>Street line</mat-label>
        <input [formControl]="addressFormControls.streetLine" matInput />
        @if (control.hasError("required")) {
          <mat-error>To pole jest wymagane</mat-error>
        }
        @if (control.hasError("maxlength")) {
          <mat-error>Maksymalna długość to 50 znaków</mat-error>
        }
      </mat-form-field>

      <mat-form-field subscriptSizing="dynamic">
        <!-- here is an error becouse of repeated variable name -->
        @let control = addressFormControls.streetLine;
        <mat-label>Postal code</mat-label>
        <input [formControl]="addressFormControls.postalCode" matInput />
        @if (control.hasError("required")) {
          <mat-error>To pole jest wymagane</mat-error>
        }
        @if (control.hasError("pattern")) {
          <mat-error>Nieprawidłowy kod pocztowy</mat-error>
        }
      </mat-form-field>
    </div>

```

### Proposed solution

It would be very useful if the scope was applied to HTML tags. Currently, I am forced to give specific names for each one, which is not always convenient. However, if the reason for this is performance, I would understand, but I would appreciate it if you could explain why this particular model was adopted.

### Alternatives considered

An alternative is to leave it as it is now.