sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: all: test failures with `EBADF` from fork/exec on NetBSD
Labels: OS-NetBSD,NeedsInvestigation,arch-arm,compiler/runtime

```
#!watchflakes
post <- goos == "netbsd" && (log ~ `fork/exec .*: bad file descriptor` || `fork/exec .*: bad file descriptor`)
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/b2bb0586b8a68265847baab33be7234f83959150)):

    fork/exec /var/gobuilder/buildlet/tmp/go-build1315313087/b144/syntax.test: bad file descriptor


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: TypeScript
Issue: `this` parameter not correctly inferred when unrelated type parameter has no inference candidates
Labels: Bug,Help Wanted

### 🔎 Search Terms

generics bug

### 🕗 Version & Regression Information

- This is a crash
- This changed between versions ______ and _______
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about _________
- I was unable to test this on prior versions because _______


### ⏯ Playground Link

_No response_

### 💻 Code

```ts
function test<
  Data1 extends Record<string, number>,
  Data2 extends Record<string, ()=>number>,
  Func extends Record<string, (this: Data2)=>void>,
>(options: {
  data1?: Data1,
  data2: Data2,
  func: Func,
}) {
    console.log(options);
};

test({
    data1: {
        a1: 1
    },
    data2: {
        a2 () {return 2;}
    },
    func: {
        f1 () {
            this.a2; // this.a2 has no type hints
        }
    }
});
```


### 🙁 Actual behavior

this.a2 has no type hints

### 🙂 Expected behavior

this.a2 has type hints

### Additional information about the issue

If you comment out data1, then type hints appear

```ts
function test<
  Data1 extends Record<string, number>,
  Data2 extends Record<string, ()=>number>,
  Func extends Record<string, (this: Data2)=>void>,
>(options: {
  data1?: Data1,
  data2: Data2,
  func: Func,
}) {
    console.log(options);
};

test({
    // data1: {
    //     a1: 1
    // },
    data2: {
        a2 () {return 2;}
    },
    func: {
        f1 () {
            this.a2; // If you comment out data1, then type hints appear
        }
    }
});
```
Repository: terminal
Issue: System Error dialog cannot display with Command Prompt
Labels: Product-Conpty,Issue-Bug,Area-Windowing

### Windows Terminal version

1.18.2681.0/1.19.2682.0

### Windows build number

10.0.19045.3516/10.0.22631.2361

### Other Software

_No response_

### Steps to reproduce

1. Launch Windows Terminal using "Open with Terminal" in explorer context menu.
2. Switch to Command Prompt.
3. Execute a dll missing or runtime error CLI program binary using Command Prompt.
4. System Error dialog cannot display. (no error information display, but process exited)

### Expected Behavior

Display a system error dialog. (if launch cmd.exe or Windows Terminal in Win+R direct, and execute a dll missing or runtime error CLI program binary, it can display system error dialog)

### Actual Behavior

System Error dialog cannot display.
Repository: ant-design
Issue: Tour组件placement功能在指引元素高度或者宽度长一点的情况下 topLeft,rightTop这种无预期效果
Labels: 🐛 Bug,Inactive

### Reproduction link

[https://codepen.io/lv900901/pen/RwEExPW](https://codepen.io/lv900901/pen/RwEExPW)

### Steps to reproduce

指引元素高度或者宽度长一点

### What is expected?

Tour组件placement功能和 Tooltip组件的placement效果一致

### What is actually happening?

Tour组件placement功能和 Tooltip组件的placement效果一致

| Environment | Info |
| --- | --- |
| antd | 5.9.4 |
| React | react |
| System | mac |
| Browser | chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: godot
Issue: Calling a static method from a static method in autoload, emits unnecessary warnings
Labels: bug,discussion,topic:gdscript

### Godot version

6916349697a4339216469e9bf5899b983d78db07

### System information

Windows 11

### Issue description

Consider placing the static call in static mathod in autoloaded script (ex `Globals`):

![image](https://github.com/godotengine/godot/assets/3036176/6cd06693-ca4a-4751-ab4f-13ee2c9baa81)

and later call it in the common script:

![image](https://github.com/godotengine/godot/assets/3036176/addbfe18-549d-4d9a-968a-b3f8d234ded8)

emits the warning on the project startup:

![image](https://github.com/godotengine/godot/assets/3036176/43ec62c9-0e1c-4337-bf47-43b0f914f7c5)

I think it's unnecessary and incorrect.

### Steps to reproduce

^^

### Minimal reproduction project

[Test.zip](https://github.com/godotengine/godot/files/12840713/Test.zip)
Repository: material-ui
Issue: [docs-infra] Demo overflow strategy 
Labels: discussion,scope: docs-infra

### What's the problem? 🤔

Today, the Base UI introduction demo uses a different overflow strategy than the rest of the page. See #39225.

It's relatively frequent for a demo to break the mobile layout, e.g. https://github.com/mui/mui-x/pull/10455 recently. Today, when this happens, it's quite easy to spot, the whole page is broken. So it's great because it's easy to identify. Now, it's also not so great because it breaks the whole docs experience, it's not isolated to one demo that is broken.

### What are the requirements? ❓

Some demos need to overflow their container, e.g. https://mui.com/material-ui/react-autocomplete/#combo-box can't have an `overflow` property today, not until the root problem of https://github.com/mui/material-ui/pull/23263 is fixed.

### What are our options? 💡

1. No change: `overflow: auto` like in Base UI introduction demo + no overflow on the other demos
2. No overflow on all the demos
3. `overflow: auto` everywhere + a warning in the console that flags the demo with a scrollbar + a prop to disable the overflow.
Repository: PowerToys
Issue: PowerToys should restart after an update
Labels: Idea-Enhancement,Area-Setup/Install,Needs-Triage

### Description of the new feature / enhancement

The program does not automatically restart after it is updated. It should.

### Scenario when this would be used?

I extensively use FancyZones. I should not have to 'relaunch' PowerToys for FancyZones to work after the update has installed.

### Supporting information

_No response_
Repository: rust
Issue: Confusing error about using struct method as function pointer
Labels: A-diagnostics,A-lifetimes,T-compiler

### Code

```Rust
fn main() {
    let f: Func = Foo::bar;
}

type Func = fn(&mut Foo<'_>);

struct Foo<'a> {
    s: &'a str
}

impl Foo<'_> {
    fn bar(&mut self) {}
}
```


### Current output

```Shell
error[E0308]: mismatched types
 --> src/main.rs:2:19
  |
2 |     let f: Func = Foo::bar;
  |            ----   ^^^^^^^^ one type is more general than the other
  |            |
  |            expected due to this
  |
  = note: expected fn pointer `for<'a, 'b> fn(&'a mut Foo<'b>)`
                found fn item `for<'a> fn(&'a mut Foo<'_>) {Foo::<'_>::bar}`

For more information about this error, try `rustc --explain E0308`.
```


### Desired output

```Shell
Not sure. I think it should just work.
```


### Rationale and extra context


Because this works:

```rust
fn main() {
    let f: Func = baz;
}

type Func = fn(&mut Foo<'_>);

struct Foo<'a> {
    s: &'a str
}

impl Foo<'_> {
    fn bar(&mut self) {}
}

fn baz(foo: &mut Foo<'_>) {}
```

### Other cases

_No response_

### Anything else?

_No response_
Repository: rust
Issue: `unused_braces` false positive with assignment to wildcard
Labels: A-lints,T-compiler,C-bug,D-invalid-suggestion,L-unused_braces

This code:
```rust
fn main() {
    let e = std::iter::empty::<()>();
    _ = { e };
    // for _ in e {} // uncomment to verify that e was dropped
}
```

Gives this warning:
```
warning: unnecessary braces around assigned value
 --> src/main.rs:3:9
  |
3 |     _ = { e };
  |         ^^ ^^
  |
  = note: `#[warn(unused_braces)]` on by default
help: remove these braces
  |
3 -     _ = { e };
3 +     _ = e;
  |
```

However, the braces are not unnecessary. `_ = { e };` does the same thing as `drop(e);`, but `_ = e;` doesn't do anything (not even move `e`).
You also can't just write `{ e };`, that would trigger a `unused_must_use` warning.
I think the lint shouldn't trigger here.

There are also more complicated examples like this:

```rust
use std::fmt::Error;

fn main() {
    let e = (std::iter::empty::<()>(), Error);
    (_, Error) = { e };
    // for _ in e.0 {} // uncomment to verify that e was dropped
}
```

Where it isn't even possible to tell if the braces are unnecessary just based on the AST. But surely no-one writes code like that :)

## Version
`rustc 1.75.0-nightly (2023-10-07)`

@rustbot label: T-compiler A-lint
Repository: TypeScript
Issue: Having a `pedantic` option in TSConfig in addtion to `strict`
Labels: Suggestion,Awaiting More Feedback

### 🔍 Search Terms

"tsconfig pedantic" "tsconfig setting" "tsconfig noimplicitreturn" "tsconfig noimplicitreturn pedantic" 

### ✅ Viability Checklist

- [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [X] This wouldn't change the runtime behavior of existing JavaScript code
- [X] This could be implemented without emitting different JS based on the types of the expressions
- [X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

It would be nice to have a `pedantic` option in `tsconfig.json`, along the lines of `strict`, but basically turning on _everything_.

I currently have the following, for instance:

```json
"strict": true,
"allowUnreachableCode": false,
"allowUnusedLabels": false,
"exactOptionalPropertyTypes": true,
"noFallthroughCasesInSwitch": true,
"noImplicitOverride": true,
"noImplicitReturns": true,
"noPropertyAccessFromIndexSignature": true,
"noUncheckedIndexedAccess": true,
"noUnusedParameters": true,
"noUnusedLocals": true,
```

This turns on _all_ checks listed in the documentation, but it was a bit of a slog to figure out which options weren't covered by the first line (`"strict": true`). Also, if new Type Checking settings were introduced, I would have to figure that out and add them manually.

I would propose a simple option `pedantic`, which sets all of the options to their most strict option. Basically replacing the whole list above with a single line of `"pedantic": true`. When new settings are added, they would automatically be covered by this. 


### 📃 Motivating Example

If `strict` is good, `pedantic` should be better. Not everybody can use it in all situations, but these settings exist for a reason, and this would be the easiest way to turn them all on.

Of course individual settings can still be overridden, in case specific code needs that. But programmers striving to write TypeScript as clean as possible will be able to have the compiler help them as much as possible with this. 

All of the Type Checking settings exist for good reasons, let's make it easy for people to use them all.

### 💻 Use Cases

1. What do you want to use this for?
Learning to write the cleanest of TypeScript code.

2. What shortcomings exist with current approaches?
Having to manually scour the documentation/changelog for TypeScript to find out what Type Checking settings aren't covered by `strict`

3. What workarounds are you using in the meantime?
See the previous point
Repository: godot
Issue: Fixing late start in OpenXR
Labels: discussion,topic:xr

### Godot version

4.2 dev 6

### System information

Windows 10 Godot Engine v4.2.dev6 - https://godotengine.org OpenGL API 3.3.0 NVIDIA 536.67 - Compatibility - Using Device: NVIDIA - NVIDIA GeForce GTX 980 Ti

### Issue description

If you go to the steam VR advance frame timings (You need to have developer mode enable in steam VR). You will see about 5ms+ of late start in VR depending and hardware and scene complexity

My assumption is that it is pulling the view matrix at the start of godot update or something like it when it should do most of the work like physics and pipeline order stuff and before submitting the command list it updates the view then submits the frame update the view at the very last second when nothing else

[Docs](https://developer.valvesoftware.com/wiki/SteamVR/Frame_Timing)
'Late Start' is a special case where the application has exceeded its cpu budget for the frame, but has not yet dropped a frame due to this. This extra wiggle room comes from what we call 'running start'; it provides a 3ms buffer before the frame starts (i.e. vsync), for the application to begin feeding the gpu render commands for that frame.

More on this here: http://www.gdcvault.com/play/1021771/Advanced-VR. 

### Steps to reproduce

Running a VR/XR project in Steam VR

### Minimal reproduction project

Any VR project
Repository: neovim
Issue: Update "report docs bug..." link on the website (create doc issue template)
Labels: bug,documentation

The issue originated from https://github.com/neovim/doc/pull/46#issuecomment-1752129918. Basically, the link at the bottom of any documentation page is probably broken as it has a few key=values in the URL query which are all ignored (because it redirects to https://github.com/neovim/neovim/issues/new/choose). And I'm writing this issue under "Bug Report" template, which should be about Neovim (program) and not about documentation. So the "Report documentation bug" template should be added, because I can't create a blank issue.
Repository: rust
Issue: Missed optimization: RVO isn't applied
Labels: A-codegen,T-compiler,A-mir-opt,A-mir-opt-nrvo,C-optimization

Consider the code below. At the first glace, it looks like RVO/destination propagation isn't applied, resulting in a stack overflow.

### File structure
`tree .`
```
.
├── bin
│   └── rvo.rs
├── Cargo.toml
├── src
│   └── lib.rs
```
### Code
`Cargo.toml`
```Toml
[package]
name = "rvo"
version = "0.1.0"
edition = "2021"

[[bin]]
name = "rvo"
path = "bin/rvo.rs"

[dependencies]

[profile.release]
lto = "fat"
```

`bin/rvo.rs`
```Rust
use rvo::Outer;

fn main() {
    let _foo = Box::new(Outer::new());
}
```

`src/lib.rs`
```Rust
#![allow(unused)]

const SIZE: usize = 1024 * 1024 * 1024;

pub struct Outer {
    a: LargeStruct,
}

impl Outer {
    #[inline(always)]
    pub fn new() -> Self {
        let a = LargeStruct::new();

        Self { a }
    }
}

pub struct LargeStruct {
    d0: Option<Box<u128>>,
    d1: Option<Box<u128>>,
    d2: Option<Box<u128>>,
    d3: Option<Box<u128>>,
    d4: Option<Box<u128>>,
    huge: [u8; SIZE],
}

impl LargeStruct {
    #[inline(always)]
    pub fn new() -> Self {
        Self {
            d0: None,
            d1: None,
            d2: None,
            d3: None,
            d4: None,
            huge: [0; SIZE],
        }
    }
}
```

Running `cargo run --release` results in:
```
    Finished release [optimized] target(s) in 0.01s
     Running `target/release/rvo`

thread 'main' has overflowed its stack
fatal runtime error: stack overflow
Aborted (core dumped)
```

Compiler version:
`rustc --version --verbose`
```
rustc 1.73.0 (cc66ad468 2023-10-03)
binary: rustc
commit-hash: cc66ad468955717ab92600c770da8c1601a4ff33
commit-date: 2023-10-03
host: x86_64-unknown-linux-gnu
release: 1.73.0
LLVM version: 17.0.2
```
Repository: angular
Issue: Exhaustive @switch type-checking
Labels: feature,area: core,compiler: template type-checking,core: control flow

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

common

### Description

I think it would be a great addition to the type-safety of templates if `@switch` were checked to be exhaustive.

Currently, if you have a field with 3 possible values:

```ts
type UserType = 'admin' | 'logged' | 'anonymous'
```

and then use a `@switch` in the template:

```html
@switch (userType) {
  @case ('admin') {
    Hello admin
  }
  @case ('logged') {
    Hello user
  }
}
```

the template compiles just fine, whereas the `'anonymous'` case is not covered.

### Proposed solution

It would be great to get a compiler error if a case is missing (when no default is provided of course). 

TypeScript would complain about a missing case, if the switch was used to return a value in a function:

```ts
function s(userType: UserType): boolean {
  switch (userType) {
    case 'admin': return true;
    case 'logged': return true;
  }
}
```

The generated TCB could maybe be code along those lines instead of a "simple" switch?

### Alternatives considered

I don't think we can work around that easily?
Repository: material-ui
Issue: [DX] Rename error prefix to use open-source project name?
Labels: discussion,dx

### What's the problem? 🤔

Most of the codebase (MUI X included) throws errors with this convention: `throw new MuiError('MUI: `. This feels strange. Even if we make MUI the UI library, that has a Joy Design theme, and a Material Design theme, it still feels strange to have an error about Base UI or MUI X prefixed with MUI.

So my proposal would be to replace these prefixes to be more specific. The side benefit is that it will train developers to learn about these different projects.

I was inspired to open this issue from https://github.com/mui/mui-x/issues/10611, which was opened on the wrong repository.
Repository: PowerToys
Issue: Apps do not stick to same zone if app has multiple windows steam + steam chat or Firefox + picture in picture
Labels: Issue-Bug,Product-FancyZones,Needs-Triage

### Microsoft PowerToys version

0.74.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

FancyZones

### Steps to reproduce

Snap picture in picture 2e zone browser to 1e zone, close picture in picture re open picture in picture is now in zone1 instead of last zone2

### ✔️ Expected Behavior

If picture in picture is closed in zone 2e zone it should re open in 2e zone, regardless of firefox snapping previously to zone 1

### ❌ Actual Behavior

If previously firefox was snapped to zone 1 and picture picture is on zone 2 and closed and re opent it re opens in zone 1

### Other Software

Firefox 118.0.1
Steam
Repository: material-ui
Issue: [docs-infra] Improve footer links
Labels: enhancement,scope: docs-infra

### Context 🔦

A continuation of https://github.com/mui/material-ui/pull/36556. I would propose these changes.

### Steps to reproduce 🕹

Steps:

Open https://mui.com/material-ui/react-switch/#api

### Current behavior 😯

<img width="809" alt="Screenshot 2023-10-08 at 23 37 48" src="https://github.com/mui/material-ui/assets/3165635/217fd487-05bc-427e-9f5c-1c4586f92c0d">


### Expected behavior 🤔

<img width="802" alt="Screenshot 2023-10-08 at 23 47 03" src="https://github.com/mui/material-ui/assets/3165635/d2e29729-79d5-49cc-b62d-ddf150e4f70e">

- [x] 1. I wouldn't expect to see "Careers". As far as we have tried to list job ads from the docs, the conversion rate was pretty bad. By the nature of our business model, people using Material UI are most likely to be on the opposite spectrum of who we need to hire (statistically speaking). Per https://docs.google.com/document/d/1Bj7f6xIufued0R-oxCsViguUoik8MwrDrCrrISWys58/edit where we see too many applications, I think making finding the roles harder is the way to go. #39709
- [x] 2. Not link to LinkedIn. The docs is a space for developers, I think the goal is to make it feel as much as possible a pure open-source vibe, this link creates a commercial license vibe. #39709
- [ ] 3. The link to "Store" feels too broad. I think it would be more coherent to reference "Templates" that we have in the side nav.
More broadly, I think we should push toward killing the noting of "Store". https://webflow.com/templates makes more sense to me, as for X, it should have its own space, and the same goes for our Figma kit.

---

Ideally, in the future:

- the link to the blog would link to the open-source project-specific blog post, e.g. https://www.hashicorp.com/blog/products/terraform
- the link to the template would link to its own space for the technology used, e.g. https://github.com/mui/mui-private/issues/103

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>
Repository: vscode
Issue: Enable accepting an Emmet abbreviation suggestion without expanding it
Labels: feature-request,emmet

<!-- ⚠️⚠️ 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. -->

This feature request is motivated by / posted on behalf of the example use-case in https://stackoverflow.com/q/77250067/11107541. Say I want to write the following abbreviation and then expand it: `input:checkbox#my-id.my-class[name=my-name]`. While I have only written `input:ch`, VS Code helpfully suggests that I might want to use the `input:checkbox` abbreviation and expand it (related setting: `emmet.showAbbreviationSuggestions`). However, in this scenario, I would want a way / an option to accept a completion that results in `input:checkbox` instead of the Emmet expansion of `input:checkbox`.

I'm not sure what the best way to go about solving this is / what is the most feasible given the suggestion architecture.

- Is it possible for a suggestion to have multiple "types" of acceptance? [`CompletionItem`](https://code.visualstudio.com/api/references/vscode-api#CompletionItem) only has a singular `command` property...
  - I suppose you could have separate suggestions for abbreviation suggestions and for abbreviation expansion suggestions, but that feels a little bloaty in terms of visual space usage and possibly confusing or overwhelming to users. Imagine typing `input:ch` and then you get a suggestion to accept `input:checkbox` but not Emmet-expand, a suggestion to Emmet-expand `input:ch`, and a suggestion to Emmet-expand `input:checkbox`. And how would you even clearly convey that? I find it hard to imagine icon differences being a good way of doing that.
- I considered the option of there could be a setting that makes it so that if a suggestion is for an abbreviation, then accepting it accepts the abbreviation suggestion and doesn't expand it (basically, you can only accept the abbreviation suggestion and expand it, or accept the abbreviation suggestion and not expand it, depending on the value of the setting you choose), but I don't think that would make for a great UX. If you selected the setting value that makes them not expand, then to get expansion, you'd need to manually invoke the expansion command, or bind it to another keyboard shortcut
Repository: go
Issue: x/pkgsite: search doesn't find "std"
Labels: FeatureRequest,pkgsite,pkgsite/search

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What is the URL of the page with the issue?

https://pkg.go.dev/search?q=std

### What is your user agent?

Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0 Safari/537.36

### Screenshot

### What did you do?

Searched for "std".

### What did you expect to see?

The standard library page, with the list of packages in the standard library, should be listed in the search results.  By strong preference, it should be the first search result.

Admittedly, the standard library is not a package named std.  But Its page has the address pkg.go.dev/std, and it's not unreasonable to search for std and expect to find it.

### What did you see instead?

A bunch of third party packages with "std" in the name, but not the standard library.