sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: x/tools/gopls: Tooltip shows distracting documentation for append() function when writing a struct literal
Labels: gopls,Tools,gopls/completion

### gopls version

golang.org/x/tools/gopls v0.14.2

### go env

```shell
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/usr/local/google/home/davidben/.cache/go-build'
GOENV='/usr/local/google/home/davidben/.config/go/env'
GOEXE=''
GOEXPERIMENT='fieldtrack,boringcrypto'
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/usr/local/google/home/davidben/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/usr/local/google/home/davidben/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/usr/lib/google-golang'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/usr/lib/google-golang/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.22-20240109-RC01 cl/597041403 +dcbe772469 X:fieldtrack,boringcrypto'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='clang'
CXX='clang++'
CGO_ENABLED='1'
GOMOD='/usr/local/google/home/davidben/tmp/gopls-tooltip/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build427257999=/tmp/go-build -gno-record-gcc-switches'
```


### What did you do?

Say you're building up some list of some complex struct. It's reasonable to write expressions of the form:
```
	l = append(l, Foo{
		A: "hello",
		B: "world",
	})
```

Here's a longer example.

```
package main

type Foo struct {
	A, B, C, D, E, F, G, H, I, J string
}

func distractingPopup() {
	var l []Foo
	l = append(l, Foo{
		A: "hello",
		B: "world",
	})

	l = append(l, Foo{
		A: "hello",
		B: "world",
		// Start adding fields here.
	})

	l = append(l, Foo{
		A: "hello",
		B: "world",
	})

	l = append(l, Foo{
		A: "hello",
		B: "world",
	})

	l = append(l, Foo{
		A: "hello",
		B: "world",
	})
}
```

### What did you see happen?

gopls in VS Code will keep the very, very long documentation for `append` persistently on screen. This is not very helpful because I'd rather have information about the struct I'm filing in. More importantly, it's distracting because the `append` documentation is very very long and invariably covers up all the context I need. I end up needing to press Esc after every few keystrokes to code effectively.

See attached screenshot.
![Screenshot from 2024-02-12 14-04-32](https://github.com/golang/go/assets/109690/98f6d0d0-ff6a-4c16-a460-7635b0a42e0a)


### What did you expect to see?

gopls does not cover up my code and instead displays useful information about the struct I'm filling in, not `append`. If showing `append` is unavoidable, it should be much, _much_ shorter so that it doesn't cover up important context.

### Editor and settings

_No response_

### Logs

_No response_
Repository: TypeScript
Issue: Google feedback on TS 5.4-beta
Labels: Discussion

### Acknowledgement

- [X] I acknowledge that issues using this template may be closed without further explanation at the maintainer's discretion.

### Comment

This GitHub issue contains feedback on the TS 5.4-beta release from the team
that is responsible for keeping Google's internal software working with the
latest version of TypeScript.

## Executive summary

*   We do not expect to have significant difficulty in upgrading Google to TS
    5.4.
*   Some changes to our TypeScript code are required to make it compile with TS
    5.4.
*   Detail sections below explain the changes to our code we expect to make to
    unblock the upgrade.

## Impact summary

| Change description                          | Announced | Libraries affected |
| ------------------------------------------- | --------: | -----------------: |
| lib/d.ts changes                            | yes       | 0.016%             |
| Errors When Type-Only Imports Conflict with | yes       | 0.0004%            |


The **Announced** column indicates whether we were able to connect the observed
change with a section in the
[TS5.4-beta announcement](https://devblogs.microsoft.com/typescript/announcing-typescript-5-4-beta/).

The following sections give more detailed explanations of the changes listed
above.

## Changes which were announced

### lib/d.ts Changes

We support the typing improvements. Generally it's clear what's changing and the
changes seems minimal this time.

For the TSC changes, we expect to fix our codebase to comply to the new API and
for other typing changes, we expect to `// @ts-ignore` to silence the errors.

We observed the following types of errors:

*   TS2345: Argument of type X is not assignable to parameter of type Y
    *   .005% of libraries affected
*   TS2769: No overload matches this call.
    *   .001% of libraries affected
*   TS2322: Type X is not assignable to type Y.
    *   .003% of libraries affected
*   TS2344: Type X does not satisfy the constraint Y.
    *   .001% of libraries affected
*   TS2552: Cannot find name X. Did you mean Y?
    *   .001% of libraries affected
*   TS2430: Interface X incorrectly extends interface Y.
    *   .001% of libraries affected
*   TS2339: Property X does not exist on type Y.
    *   .001% of libraries affected
Repository: next.js
Issue: Next.JS 14.1.0 and azure/msal... relaods too much and never authenticate
Labels: bug,Navigation

### Link to the code that reproduces this issue

https://github.com/FrancisBoudreau/bogue-reproduction-app

### To Reproduce

1. I updated the v14.0.3 to the v 14.1.0 and after I got a import { useRouter } from "next/navigation" ERROR, 
2. Deleted the line and put it back and the error disapeared.
3. Lauched the dev and the page was reloading many times untel MS login display message that it can't log in. 
4. Dowgraded back to v 14.0.3, Next and msal authication working again like suposed to. 

### Current vs. Expected behavior

realoding in a loop, 
should login with  msale. 

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Education
Binaries:
  Node: 20.10.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.1.0
  eslint-config-next: 14.1.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: export
```


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

Not sure, App Router, Routing (next/router, next/navigation, next/link)

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

next dev (local)

### Additional context

I tested my reproduction against different canary releases, and **the first one that introduced the bug was 14.0.5-canary.54**, reverting to 14.0.5-canary.53 workds.
Repository: pytorch
Issue: torch.sparse.spdiags must support integer offsets
Labels: module: sparse,triaged

### 🐛 Describe the bug

Hi,

Just like in scipy's sparse, I think spdiags should also support integer diagonal offsets. 

The error i get is,

```
TypeError: _spdiags(): argument 'offsets' must be Tensor, not int
```

Cheers,

### Versions

pip3] neural-renderer-pytorch==1.1.3
[pip3] numpy==1.23.5
[pip3] pytorch-lightning==1.3.8
[pip3] pytorch3d==0.7.4
[pip3] torch==2.2.0
[pip3] torch-sparse-solve==0.0.5
[pip3] torchmeta==1.4.0
[pip3] torchmetrics==0.5.0
[pip3] torchvision==0.17.0
[pip3] triton==2.2.0
[conda] blas                      1.0                         mkl  
[conda] cudatoolkit               11.3.1               h2bc3f7f_2  
[conda] ffmpeg                    4.3                  hf484d3e_0    pytorch
[conda] libblas                   3.9.0            12_linux64_mkl    conda-forge
[conda] libcblas                  3.9.0            12_linux64_mkl    conda-forge
[conda] libjpeg-turbo             2.0.0                h9bf148f_0    pytorch
[conda] mkl                       2021.4.0           h06a4308_640  
[conda] mkl-service               2.4.0            py39h7f8727e_0  
[conda] mkl_fft                   1.3.1            py39hd3c417c_0  
[conda] mkl_random                1.2.2            py39h51133e4_0  
[conda] neural-renderer-pytorch   1.1.3                    pypi_0    pypi
[conda] numpy                     1.23.5           py39h14f4228_0  
[conda] numpy-base                1.23.5           py39h31eccc5_0  
[conda] pytorch                   2.2.0           py3.9_cuda12.1_cudnn8.9.2_0    pytorch
[conda] pytorch-cuda              12.1                 ha16c6d3_5    pytorch
[conda] pytorch-lightning         1.3.8                    pypi_0    pypi
[conda] pytorch-mutex             1.0                        cuda    pytorch
[conda] pytorch3d                 0.7.4                    pypi_0    pypi
[conda] torch-sparse-solve        0.0.5                    pypi_0    pypi
[conda] torchmeta                 1.4.0                    pypi_0    pypi
[conda] torchmetrics              0.5.0                    pypi_0    pypi
[conda] torchtriton               2.2.0                      py39    pytorch
[conda] torchvision               0.17.0               py39_cu121    pytorch


cc @alexsamardzic @nikitaved @pearu @cpuhrsch @amjames @bhosmer @jcaip
Repository: stable-diffusion-webui
Issue: [Bug]: Binaries
Labels: bug-report

### Checklist

- [X] The issue exists after disabling all extensions
- [X] The issue exists on a clean installation of webui
- [ ] The issue is caused by an extension, but I believe it is caused by a bug in the webui
- [X] The issue exists in the current version of the webui
- [X] The issue has not been reported before recently
- [ ] The issue has been reported before but has not been fixed yet

### What happened?

When running `webui-user.bat` with an incorrect python version, it mentions binaries as an alternative. There are no binaries in the github releases.

### Steps to reproduce the problem

none

### What should have happened?

none

### What browsers do you use to access the UI ?

_No response_

### Sysinfo

none

### Console logs

```Shell
none
```


### Additional information

_No response_
Repository: godot
Issue: (Possible Engine Bug) Rarely Freezing And Pinning GPU to 100% on Launch for long periods of time, Leading To a System Driver Refresh.
Labels: topic:rendering,topic:editor,needs testing

### Tested versions

- Not Reproducible In Previous Godot Versions, Only 4.2.1, Even Then It Rarely Occurs Just By Opening

### System information

Godot v4.2.1.stable - Windows 10.0.22621 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1650 (NVIDIA; 31.0.15.3770) - Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz (12 Threads)

### Issue description

I Assumed It Was A Driver Issue, But Even After Updating Drivers, The Issue Still Persisted.

I Noticed my GPU Usage Would Randomly Spike from 5-10% to well over 90% nearing 100% Just by loading the project list (with 3 projects) Which Sometimes Would Lead To My Computer Freezing, Forcing it to do a Driver Refresh.

However I Never Had It Happen While in a Project Before, But When I Went to Run a 3D Scene With A Camera (With The Default Clear Color Environment) To Test Textures On Meshes, The Application Hadn't Gotten To The Point of Showing The "Godot Engine" Loading Screen. 

Simply Showed The Background And Stayed There For 1-2 Seconds. (Which Was Fairly Common, I Got Used To It) But This Time My GPU Usage Spiked back up to 100%, Stayed There, Then My Entire Computer Froze, Audio Stopped, Then My Driver Refreshed And When It Finished, The Application Closed, Godot Was Fully Frozen, And I Had To Use Task Manager To Close it.



### Steps to reproduce

- Unsure, Happens While Opening.

### Minimal reproduction project (MRP)

N/A
Repository: pytorch
Issue: [NestedSubTensor] add communication operators support
Labels: oncall: distributed,triaged,module: nestedtensor,module: dtensor

### 🚀 The feature, motivation and pitch

I'm trying to combine DTensor and NestedTensor to support the sharding of variable length sequences. Therefore, it is essential to make NestedTensor support communication ops.

### Alternatives

I'd love to contribute. The straightforward way to support this seems to add code in the \_\_torch_function\_\_ of NestedTensor.

But when I `print(func)` in \_\_torch_function\_\_, I got `<method-wrapper '__get__' of getset_descriptor object at 0x7f76721e57c0>`. My question is that if I want to support `dist.scatter` on the python side, I need to get the op type first. Now it's a method-wrapper, which makes me difficult to know its type.

Below is the code to test the case:
```
import torch
from torch.testing._internal.distributed.fake_pg import FakeStore
import torch.distributed as dist
from torch.nested import nested_tensor

hidden_size = 2
device = "cpu"
seq_lengths = [2, 3, 4, 5]
input_tensors = []
world_size = 2
for seqlen in seq_lengths:
    input_tensor = torch.randn(seqlen, hidden_size, device=device, requires_grad=False)
    input_tensor = input_tensor.detach().clone()
    input_tensors.append(input_tensor)


store = FakeStore()
dist.init_process_group(backend="fake", rank=0, world_size=world_size, store=store)

nested_input_tensor = nested_tensor(input_tensors, layout=torch.jagged)
nested_output_tensor = dist.scatter(nested_input_tensor, src=1)
```

### Additional context

_No response_


cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu @penguinwu @fegin @XilunWu @wanchaol @fduwjj @wz337 @tianyu-l @wconstab @yf225 @cpuhrsch @jbschlosser @bhosmer @drisspg @soulitzer @YuqingJ
Repository: PowerToys
Issue: Restore all Windows
Labels: Status-In progress

### Description of the new feature / enhancement

Add the ability to restore all minimized or minimized windows for a specific application using a hot key or pop-up menu item from the task bar.

### Scenario when this would be used?

Power users commonly open multiple windows in the same application (e.g., Teams, Edge). I will go to minimize all windows for a specific application but have to individually restore each child window.

### Supporting information

_No response_
Repository: flutter
Issue: HTML renderer paragraph reports an empty line when the text is empty
Labels: a: text input,engine,platform-web,e: web_html,has reproducible steps,P3,team-web,triaged-web,found in release: 3.20

## Repro steps:

```dart
  test('empty paragraph is empty', () {
    final TextPainter painter = TextPainter(
      textDirection: TextDirection.ltr,
      text: const TextSpan(),
    )..layout();

    expect(painter.computeLineMetrics(), isEmpty);
  });
```

Run `flutter test test/painting/text_painter_test.dart --platform=chrome --web-renderer=html --plain-name='empty paragraph is empty'`

it fails with error message:
```
Expected: empty
Actual: [
  EngineLineMetrics:LineMetrics(hardBreak: true, ascent: 10, descent: 4, unscaledAscent: 10, height: 14, width: 0, left: 0, baseline: 10, lineNumber: 0)
]
```

The behavior is reasonable but it's inconsistent with what SkParagraph reports.
Repository: next.js
Issue: Error when nextjs tries to warn about non-plain object prop binding - Error: Cannot convert a Symbol value to a string
Labels: bug

### Link to the code that reproduces this issue

https://github.com/jon-ressio/vercel-prop-warn-error

### To Reproduce

1. Start the application in dev mode
2. Load the app in a browser
3. See Error page

Note: This only happens when running under `next dev`, `next build && next start` works as expected

### Current vs. Expected behavior

From page.tsx, `<Thing>` is included twice.  The first instance causes `Warning: Only plain objects can be passed to Client Components from Server Components. URL objects are not supported.` to show up in the server console, but the second instance causes the page to error out with: `TypeError: Cannot convert a Symbol value to a string`

The `as={SomeLink}` prop seems to not be handled by the Next/react warning, so the code trying to generate/show the warning causes a runtime error.

Expected: To render the same warning for the second `<Thing>` as done for the first.

### Provide environment information

```bash
NOTE: I did test this in 4.1.1-canary.50 and the issue still exists

Operating System:
  Platform: linux
  Arch: x64
  Version: #1 ZEN SMP PREEMPT_DYNAMIC Mon, 05 Feb 2024 22:07:37 +0000
Binaries:
  Node: 18.19.0
  npm: 10.2.3
  Yarn: 1.22.21
  pnpm: 8.15.1
Relevant Packages:
  next: 14.1.0
  eslint-config-next: 14.0.4
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.2.2
Next.js Config:
  output: N/A


warn  - Latest canary version not detected, detected: "14.1.0", newest: "14.1.1-canary.50".
        Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
        Read more - https://nextjs.org/docs/messages/opening-an-issue
```


### Which area(s) are affected? (Select all that apply)

App Router

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

Issue does not exist in 13.5.6, does exist in 14.0.0
Repository: material-ui
Issue: [docs-infra] Improve type naming on the API pages
Labels: enhancement,scope: docs-infra

We're using a shorthand notation to mention to type names that seem to be about [React's prop-types](https://legacy.reactjs.org/docs/typechecking-with-proptypes.html#proptypes), like `bool`.

<img width="202" alt="Screenshot 2023-08-21 at 23 37 53" src="https://github.com/mui/material-ui/assets/3165635/22cc08bc-fef3-4486-9973-5e4baa7c457c">

https://mui.com/material-ui/api/fade/#fade-prop-appear

But it seems to make more sense to use the full name for it to be more accurate with [how TypeScript refers to them](https://www.typescriptlang.org/docs/handbook/declaration-files/do-s-and-don-ts.html#general-types.) — e.g., `boolean`.

This naming design optimizes for a time when most developers would write "propType". Today, these developers are a lot more likely to write TypeScript types, so it will bring a more intuitive DX to make the change:

- bool → boolean
- func → function
- etc.

**Search keywords**: type naming, api page
Repository: godot
Issue: MultiplayerSpawner shows a node configuration warning when given its own path as spawn path
Labels: bug,topic:editor,topic:multiplayer

### Tested versions

4.3.dev3
4.2.1.stable

### System information

Godot v4.3.dev3 - Windows 10.0.22621 - GLES3 (Compatibility) - Intel(R) Iris(R) Plus Graphics (Intel Corporation; 31.0.101.2125) - Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz (8 Threads)

### Issue description

When creating a MultiplayerSpawner and giving it its own path as spawn path, a warning icon shows up in the scene dock, with its tooltip being 'A valid NodePath must be set in the "Spawn Path" property in order for MultiplayerSpawner to be able to spawn Nodes.'
Clicking this kind of warning icon usually opens a small window specifying the warning, for instance when there is no spawn path but it does not happen here.

### Steps to reproduce

- create a MultiplayerSpawner
- give it its own path as spawnpath

### Minimal reproduction project (MRP)

N/A
Repository: flutter
Issue: Improve the tools/process around tracking and minimizing technical debt
Labels: team,c: proposal,P2,c: tech-debt,monorepo

Forked from https://github.com/flutter/flutter/issues/143312.

This is a catch-all issue/wishlist for having better tooling or process for minimizing and reducing usages of deprecated _stuff_[^1].

Anyone is welcome to add their thoughts, but:

1. Please be respectful.
2. These are for tools and process for Flutter **contributors**, not users, i.e. for the Flutter framework _itself_.
3. When possible, explain the problem you're trying to solve before suggesting a solution.

It's also not clear _who_ or _when_ this work will get done, but we can discuss priorities as a team.

[^1]: I'd say _code_, but perhaps you could extend this to "using Groovy instead of Kotlin for Gradle", etc.

---

I'll start with a few seeded ideas:

## 1-time allow-listing all existing deprecations and making future ones breaking

Imagine the following API:

```dart
// package:foo/foo.dart

final class Foo {
  void bar() {}
}
```

In a roll, the following happens:

```diff
// package:foo/foo.dart

final class Foo {
+  @Deprecated('Use baz() instead')
  void bar() {}
+  void baz() {}
}
```

... a bot could automatically add:

```diff
+ // ignore: deprecated_member_use
foo.bar();
```

... to all existing call-sites, and then make that symbol breaking for future usages.

## Create a dashboard that tracks deprecated member usages

... potentially with WoW or MoM changes.

| Import | Symbol | Current | Last 30 Days
| ------ | -------- | -------- | --------------
| `package:foo/foo.dart` | `Foo.bar` | 3 | +1 (33%)
Repository: rust
Issue: rustdoc: generic constant expressions not displayed (and where clauses using said gces)
Labels: T-rustdoc,C-bug,A-const-generics,F-generic_const_exprs

This code

```rust
#![feature(generic_const_exprs)]
pub const fn assert_zero(x: usize) -> usize {
    if x != 0 {
        panic!("expected zero");
    } else {
        0
    }
}

pub fn chunked<const C: usize, const N: usize, T>(x: [T; N]) -> [[T; C]; N / C]
where
    [(); assert_zero(N % C)]:,
{
    unsafe {
        core::mem::ManuallyDrop::new(x)
            .as_ptr()
            .cast::<[[T; C]; N / C]>()
            .read()
    }
}
```

Produces this documentation

![image](https://github.com/rust-lang/rust/assets/70787919/e36f493e-db3e-4ce5-8d5a-4584983f41ce)

This is what i want

![image](https://github.com/rust-lang/rust/assets/70787919/86822dca-c49d-4033-8ff8-e827df716b3d)

### Meta
rustdoc 1.78.0-nightly (1a648b397 2024-02-11)

@GuillaumeGomez @fmease