sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: material-ui
Issue: [Button] Text wrap issue
Labels: good first issue,component: button,package: material-ui,package: joy-ui,enhancement

### Steps to reproduce 🕹

Link to live example:

Steps:

1. https://codesandbox.io/s/inspiring-browser-c7qmv7?file=/Demo.tsx


### Current behavior 😯

<img width="121" alt="Screenshot 2023-08-27 at 20 33 12" src="https://github.com/mui/material-ui/assets/3165635/81ba91eb-305d-4294-af8e-2f05cb7d202a">


### Expected behavior 🤔

<img width="117" alt="Screenshot 2023-08-27 at 20 33 05" src="https://github.com/mui/material-ui/assets/3165635/ec285c90-a60d-4a04-9c23-729709340bba">


### Context 🔦

It looks more correct on Material UI:

<img width="121" alt="Screenshot 2023-08-27 at 20 38 13" src="https://github.com/mui/material-ui/assets/3165635/6d870915-e108-4e66-a41b-3e2a431048cc">

https://codesandbox.io/s/peaceful-khorana-27gct9

but a lower line-height would I think feel better.

### 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: rust
Issue: Performance regression in 1.72 related to normalization of opaques with late-bound vars
Labels: P-medium,I-compiletime,T-compiler,regression-from-stable-to-stable,C-bug,WG-compiler-performance

Upgrade from 1.71 to 1.72 has made compilation time of my async-heavy actix server 350 times slower (from under 5s to 30 minutes, on a 32GB M1 Max CPU).

I've bisected it to commit a20a04e5d68e85935539c16c945f1947559ad3ce (#113108).

The slowdown is still in the latest nightly (1.74.0 69e97df5c 2023-08-26). 1.72 and the nightly spend 30% of all compilation time in `Interners::intern_ty`, mainly called by `<rustc_middle[b15c2eca62e7285b]::ty::Ty as rustc_type_ir[f43ddb3fb00a443c]::fold::TypeSuperFoldable<rustc_middle[b15c2eca62e7285b]::ty::context::TyCtxt>>::try_super_fold_with::<rustc_middle[b15c2eca62e7285b]::ty::generic_args::ArgFolder>` and `<rustc_middle[b15c2eca62e7285b]::ty::Ty as rustc_type_ir[f43ddb3fb00a443c]::fold::TypeSuperFoldable<rustc_middle[b15c2eca62e7285b]::ty::context::TyCtxt>>::try_super_fold_with::<rustc_trait_selection[961e83e42176765a]::traits::project::AssocTypeNormalizer>`.

The reduced code is in: https://gitlab.com/lib.rs/main/-/commits/reproducer

<details><summary>outdated info</summary>
Apologies for a big spaghetti reproducer. Let me know if it'd be useful to reduce it.

```bash
git clone --recursive https://gitlab.com/lib.rs/main
cd main
git reset --hard 81c612b
cargo build -p crates-server
```

I suspect the culprit is this function, which is used in several places in `server/src/main.rs`:

```rust
async fn with_file_cache<F: Send>(state: &AServerState, cache_file_name: &str, cache_time: u32, allow_stale: bool, generate: F) -> Result<Rendered, anyhow::Error>
    where F: Future<Output=Result<Rendered, anyhow::Error>> + 'static {
```

</details>

@rustbot modify labels: +regression-from-stable-to-stable -regression-untriaged
Repository: godot
Issue: Pressing a mouse button bound to an action causes a noticeable lag spike
Labels: platform:linuxbsd,topic:core,needs testing,performance

### Godot version

4.1.1

### System information

Godot v4.1.1.stable.mono - Arch Linux #1 ZEN SMP PREEMPT_DYNAMIC Sat, 19 Aug 2023 15:38:10 +0000 - Vulkan (Mobile) - dedicated NVIDIA GeForce GTX 1050 Ti (nvidia; 535.98) - AMD Ryzen 5 3600 6-Core Processor (12 Threads)

### Issue description

Pressing a mouse button bound to an action causes a noticeable lag spike. This happens both when the window has and does not have focus 

### Steps to reproduce

* Create a new project
* Add a new action
* Add any mouse button to the action
* Launch the project
* Press the mouse button bound to the action
* Observe a lag spike

### Minimal reproduction project

[MouseAction.zip](https://github.com/godotengine/godot/files/12448599/MouseAction.zip)
Written in GDScript.
The sprite rotates by the frame delta.
The left and right mouse buttons are bound to an action, pressing them causes the lag spike. The space bar is also bound to this action but does not cause a lag spike.
Repository: ollama
Issue: Add a way for user to approve CORS requests from origins without running a separate `ollama serve`
Labels: feature request

Quite a few tools built on Ollama are hosted on alternate origins like `chrome-extension://` (chrome extensions) or `http://example.com` (websites that want to use the user's local Ollama instance).

Tools like Figma, Zoom and Slack have a way to "allow" the browser clients to interact with a server hosted on `localhost` by prompting the user once to approve an origin and then remembering this decision. We would need to be careful with the form factor here, but a dialog window (similar to Apple's [universal links](https://developer.apple.com/documentation/xcode/allowing-apps-and-websites-to-link-to-your-content)) could be a helpful starting point.
Repository: rust
Issue: Only a single error is emitted for multiple equal unmet bounds arising from distinct generic parameters on the same item
Labels: A-diagnostics,T-compiler,D-terse

Uplifted from https://github.com/rust-lang/rust/issues/105306#issuecomment-1518136153 & https://github.com/rust-lang/rust/issues/105306#issuecomment-1693645473.
CC @estebank

For the following erroneous code, rustc only emits a single error while ideally it should emit two errors. Presumably, this happens because the two predicate obligations for `String: Copy` have the same cause span (namely of the entire path) before any fulfillment error adjustment takes place and therefore they get deduplicated early on. Details may vary.

Original reproducer (involving projections):

```rs
trait Trait {
    type P<T: Copy, U: Copy>;
}
impl Trait for () {
    type P<T: Copy, U: Copy> = ();
}
fn main() {
    let _: <() as Trait>::P<String, String>;
}
```

Current output (1 error):

```
error[E0277]: the trait bound `String: Copy` is not satisfied
 --> src/main.rs:8:29
  |
8 |     let _: <() as Trait>::P<String, String>;
  |                             ^^^^^^ the trait `Copy` is not implemented for `String`
  |
note: required by a bound in `Trait::P`
 --> src/main.rs:2:15
  |
2 |     type P<T: Copy, U: Copy>;
  |               ^^^^ required by this bound in `Trait::P`
```

Expected output (2 errors):

```
error[E0277]: the trait bound `String: Copy` is not satisfied
 --> src/main.rs:8:12
  |
8 |     let _: <() as Trait>::P<String, String>;
  |                             ^^^^^^ the trait `Copy` is not implemented for `String`
  |
note: required by a bound in `Trait::P`
 --> src/main.rs:2:15
  |
2 |     type P<T: Copy, U: Copy>;
  |               ^^^^ required by this bound in `Trait::P`

error[E0277]: the trait bound `String: Copy` is not satisfied
 --> src/main.rs:8:12
  |
8 |     let _: <() as Trait>::P<String, String>;
  |                                     ^^^^^^ the trait `Copy` is not implemented for `String`
  |
note: required by a bound in `Trait::P`
 --> src/main.rs:2:24
  |
2 |     type P<T: Copy, U: Copy>;
  |                        ^^^^ required by this bound in `Trait::P`

```

Another very similar reproducer (involving ADTs) which probably takes a slightly different execution path in the compiler:

```rs
struct S<T: Copy, U: Copy>(T, U);

fn main() {
    let _: S<String, String>;
}
```

### Meta

<details><summary><code>rustc -Vv</code></summary>

```
rustc 1.74.0-nightly (668bf8c59 2023-08-27)
binary: rustc
commit-hash: 668bf8c5932933255ba278f50fdbe308f7abe60f
commit-date: 2023-08-27
host: x86_64-unknown-linux-gnu
release: 1.74.0-nightly
LLVM version: 17.0.0
```

</details>

@rustbot label T-compiler A-diagnostics D-incorrect
Repository: vscode
Issue: PHP function comment not working after change auto indent in setting
Labels: php,editor-autoindent,under-discussion

<!-- ⚠️⚠️ 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. -->
Version: 1.81.1 (user setup)
Commit: 6c3e3dba23e8fadc360aed75ce363ba185c49794
Date: 2023-08-09T22:22:42.175Z (2 wks ago)
Electron: 22.3.18
ElectronBuildld: 22689846
Chromium: 108.0.5359,215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Windows NT x64 10.0.19044

Steps to Reproduce:

1.set auto indent to **brackets**
![image](https://github.com/microsoft/vscode/assets/103372013/1d76ddb3-3da2-46d4-af2a-e67b2c8de6a8)

2.type `/**` mark and enter then have newline, the function comment not auto complete `*` star mark
![image](https://github.com/microsoft/vscode/assets/103372013/f1b752e7-6b0d-48a3-871e-b9afda435da0)

3.reset auto indent to **full**
![image](https://github.com/microsoft/vscode/assets/103372013/8b975f4e-3ac5-4770-a2ab-58e9c8350b5b)

4.funcion comment has been restored to normal.
![image](https://github.com/microsoft/vscode/assets/103372013/94449a5e-22e8-4fd2-9ed9-0d00305d5d34)
Repository: tauri
Issue: How to show the button zoom in/out when fullscreen
Labels: type: question,platform: Windows

Hello brothers,

My app run perfect except one thing in Windows.
When the app is fullscreen, which I set "fullscreen": true, the app start at fullscreen mode without zooming button.
It is a bit inconvenient to exit the fullscreen mode. The ESC keyword not works as well.
Currently my user have to press Alt + F4 to turn off the app, or Window + Tab to switch to other application.
Of course many user don't know this unless we add instruction. Many user complain that this is not a good user experience.

What I am expecting is to show something like button Zoom in/ Zoom out so that user can quickly and easily exit the fullscreen. But this only shown when the fullscreen config is set to false. But if set to false, the window taskbar is not hidden when app fullscreen.

On Safari, this problem not happen.

I am actually don't know how to fix this. I would be very gratefull for any advice/ solution.

My app version:
-  "@tauri-apps/cli": "^1.4.0"
- "@tauri-apps/api": "^1.4.0"
- "vue": "^3.2.45"


Below is my config file. Thank you.
```
{
  "build": {
    "beforeDevCommand": "yarn dev",
    "beforeBuildCommand": "yarn build",
    "devPath": "http://localhost:8080",
    "distDir": "../dist",
    "withGlobalTauri": false
  },
  "package": {
    "productName": "FPTPLAY",
    "version": "0.0.0"
  },
  "tauri": {
    "macOSPrivateApi": true,
    "allowlist": {
      "all": true,
      "shell": {
        "all": true,
        "open": true
      },
    },
    "bundle": {
      "active": true,
      "targets": "all",
      "identifier": "fptplay.vn",
      "icon": [
        "icons/32x32.png",
        "icons/128x128.png",
        "icons/128x128@2x.png",
        "icons/icon.icns",
        "icons/icon.ico"
      ]
    },
    "security": {
      "csp": null
    },
    "windows": [
      {
        "fullscreen": true,
        "resizable": true,
        "title": "FPTPLAY",
        "width": 1024,
        "height": 800,
        "minWidth": 1024,
        "minHeight": 700,
        "x": 0,
        "y": 0
      }
    ]
  }
}
```
Repository: svelte
Issue: Support `<template>` as custom element root for class directives, event handlers etc
Labels: feature request,custom element

### Describe the bug

With a Svelte custom element, if you export variables and then bind them to attributes on a root `<template>` tag, then those attributes are automatically reflected to the host element (i.e. this works):

```svelte
<svelte:options customElement={{ tag: "my-tab" }} />

<script>
  export let role = "tab"
</script>

<template {role}>
  <svelte:element this="slot" />
</template>
```

This results in...

```html
<my-tab role="tab">The "[role='tab']" bit is automatically reflected.</my-tab>
```

If you try to leverage this binding behavior further in ways that follow conventional Svelte patterns, the consistency ends there.

### Reproduction

Judging from the initial binding behavior, I would then expect all of the following to also work with the root `<template>` element.

```svelte
<svelte:options customElement={{ tag: "my-tab", props: {
  expanded: { reflect: true, type: 'Boolean' }
}}} />

<script>
  export let expanded = false;

  function onClick() {
    expanded = !expanded;
    console.log("my-tab was clicked!");
  }
</script>

<template
  {expanded}
  class:expanded
  aria-expanded={expanded ? "true" : undefined}
  on:click={() => expanded = !expanded}
  on:click={onClick}
  >
  <svelte:element this="slot" />
</template>
```

The only one that *did* work for me was the first feature (the `{expanded}` bit):

- No class named "expanded" was added or removed from the `my-tab` element's `class` attribute in response to state changes.
- Attempting to do so with attributes that include dashes, like `aria-expanded`, merely has no effect whatsoever.
- Attempting to bind an inline event handler actually resulted in some sort of parse error in my experience. All text after the `=>` just ends becoming part of a text node prepended to the element's shadow DOM (in this case, it would contain `expanded = !expanded}>`, including the curly brace and angled bracket). I could only fix it by switching to a direct function reference; however...
- Attempting to bind an event handler with a direct function reference never actually triggers the event handler.

As it stands, I am having to fetch a reference to the host element via the new `extends` feature and do a bunch of reactive statements to handle the desired sync operations, but it would be ideal if I could make use of the declarative and succinct Svelte syntax I'm used to.

### Logs

_No response_

### System Info

```shell
System:
    OS: Windows 10 10.0.22000
    CPU: (20) x64 13th Gen Intel(R) Core(TM) i9-13900H
    Memory: 16.82 GB / 63.66 GB
  Binaries:
    Node: 20.2.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - C:\Program Files\nodejs\yarn.CMD
    npm: 9.6.6 - C:\Program Files\nodejs\npm.CMD
    pnpm: 8.6.9 - C:\Program Files\nodejs\pnpm.CMD
  Browsers:
    Edge: Spartan (44.22000.120.0), Chromium (115.0.1901.203)
    Internet Explorer: 11.0.22000.120
  npmPackages:
    svelte: ^4.0.0 => 4.1.1
```


### Severity

annoyance
Repository: next.js
Issue: Not having a robots.txt defined causes it to be passed as a dynamic route
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.5.0: Thu Jun  8 22:22:20 PDT 2023; root:xnu-8796.121.3~7/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.16.0
      npm: 9.5.1
      Yarn: 1.22.19
      pnpm: N/A
    Relevant Packages:
      next: 13.4.20-canary.9
      eslint-config-next: 13.4.19
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.2.2
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App Router

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/JamesSingleton/photage

### To Reproduce

1. Create a next application without a `robots.txt`
2. create some nested dynamic routes (i.e. `[category]/[year]/[event]/page.tsx`)
3. Put a console.log logging the params in the `[category]/page.tsx`
4. Go to that last dynamic route `[event]/page.tsx`
5. See that the `console.log(params)` shows `{ category: 'robots.txt' }`

### Describe the Bug

While making sure my 404s were working with `notFound()` from `next/navigation`, I noticed that if you don't have a `robots.txt` defined and have dynamic routes, `robots.txt` will get passed as that dynamic route.

I have the following route structure:

![Screenshot 2023-08-27 at 10 49 19 PM](https://github.com/vercel/next.js/assets/21000200/2f30fe30-c68b-47e7-9bf4-6daf98b3439a)

In my `app/(website)/[category]/page.tsx` I did a `console.log(params)` and I set a `console.log(params)` in `app/(website)/[category]/[year]/[event]/page.tsx`. 

If I go to a page like `localhost:3000/sports/2022/dual-meet-vs-casteel-and-desert-sunrise`, I will get `{ category: 'robots.txt' }` in my `console.log` from `[category]/page.tsx`. However, in my `[event]/page.tsx`, I get:

```json
{
  category: 'sports',
  year: '2022',
  event: 'dual-meet-vs-casteel-and-desert-sunrise'
}
```

I currently don't have a `robots.txt` configured in my Next.js application. This is causing the function to call Sanity in my `[category]/page.tsx` to be called even though I'm not even on that page. 

### Expected Behavior

Not defining a `robots.txt` should not cause it to be passed as a dynamic route

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: PowerToys
Issue: Seemless mouse transition between different size displays
Labels: Idea-New PowerToy,Needs-Triage

### Description of the new feature / enhancement

When moving the mouse between different size displays the cursor can sometimes get "stuck" if the target display is smaller than the source display and the exit point on the source screen is out of bounds for the target screen. With the "seemless mouse transition" feature enabled the mouse would simply transition to the closest top or bottom edge of the target display rather than getting stuck in the "seem" between the two displays.

### Scenario when this would be used?

When using multiple displays of different size, e.g. a laptop connected to a desktop display.

### Supporting information

_No response_
Repository: pytorch
Issue: Undefined Symobl: pybind11::detail::type_caster<at::Tensor, void>::load(pybind11::handle, bool)
Labels: needs reproduction,triaged,module: pybind

### 🐛 Describe the bug

This bug report is a derivation of what was reported on the pybind/pybind11 GitHub repo:
[pybind issue #4696](https://github.com/pybind/pybind11/issues/4696)

The traceback I got was:
Traceback (most recent call last):
File "run.py", line 25, in 
import cfvpy.tasks
File "/home/usrname/rebel-main/cfvpy/tasks.py", line 15, in 
import cfvpy.selfplay
File "/home/usrname/rebel-main/cfvpy/selfplay.py", line 27, in 
import cfvpy.rela
ImportError: /home/usrname/rebel-main/cfvpy/rela.cpython-37m-x86_64-linux-gnu.so: undefined symbol: _ZN8pybind116detail11type_casterIN2at6TensorEvE4loadENS_6handleEb

To reproduce, please follow the steps as outlined by me in a comment of the pybind issue above:
[reproduction procedure](https://github.com/pybind/pybind11/issues/4696#issuecomment-1678574353)

And one of pybind's contributors, rwgk, suggested that this might be a bug/issue of PyTorch,
[rwgk's comment](https://github.com/pybind/pybind11/issues/4696#issuecomment-1679013574)



### Versions

PyTorch: 1.4.1
pybind: [a1b71df](https://github.com/pybind/pybind11/tree/a1b71df137e015d44f7e31f7b6d4807253fb7871)
Repository: flutter
Issue: Code to transfer the fine-grained bounds in DrawDisplayList should have a cap
Labels: engine,c: proposal,P2,team-engine,triaged-engine

Currently the code that transfers the bounds of a DisplayList that has an RTree into another that also has an RTree will [iterate over all bounds of all ops](https://github.com/flutter/engine/blob/d89824ab018f1718e5f54e840a816f3e4634e387/display_list/dl_canvas_to_receiver.cc#L776), even if they don't fit inside the current clip or cull rect of the target DisplayList. For one app that generated a picture with 300,000 DrawLine calls that extended hundreds of thousands of pixels off of the screen, it depends on proper culling of the DisplayLists in order to achieve decent performance on small screens.

The code in that method should pass the current cull rect of the DisplayList to the search-and-consolidate method to avoid a huge potentially quadratic consolidation of rectangles far outside the current view.

Another possible solution is described in https://github.com/flutter/flutter/issues/139323 which avoids copying all of the rects during the build phase of a DL.
Repository: rust
Issue: Closure field capturing leads to inconsistent MIR printing
Labels: A-MIR

I am trying to learn what closure field capturing *exactly* does by studying the dumped MIR for a couple of interesting cases. Unfortunately that MIR contradicts itself:
```rust
fn call(f: impl FnOnce()) { f() }

#[derive(Default)]
struct S {
    field0: u8,
    field1: u8,
    field2: u8,
}

fn test() {
    let s = S::default();
    call(|| {
        let _v = &s.field1;
        let _v = &s.field2;
    })
}
```
prints this for the call site:
```
    let _1: S;

    bb1: {
        _3 = &(_1.1: u8);
        _4 = &(_1.2: u8);
        _2 = [closure@src/lib.rs:12:10: 12:12] { s: move _3 };
        _0 = call::<[closure@src/lib.rs:12:10: 12:12]>(move _2) -> [return: bb2, unwind continue];
    }
```
and this for the closure body
```
fn test::{closure#0}(_1: [closure@src/lib.rs:12:10: 12:12]) -> () {
    let mut _0: ();
    let mut _2: &u8;
    let mut _3: &u8;

    bb0: {
        _2 = deref_copy (_1.0: &u8);
        _3 = deref_copy (_1.1: &u8);
        return;
    }
}
```
So at the call site it seems like the closure type has a single field called `s` of type `&u8`. But in the body it looks like it has 2 fields (MIR as usual only shows their indices, `0` and `1`) that each have type `&u8`. Which one is true?

[This test case](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=07a02c918e196f59b31c9773cbf1e951) prints "16" so it looks like there really are two reference-typed fields. That makes the printing at the site where the closure values are being captured rather misleading.
Repository: three.js
Issue: Camera: Consequences of applying scaling.
Labels: Enhancement

### Description

Scaling the camera on spotlight or pointlights affects the light intensity

### Reproduction steps

1. open spotlight or pointlights example
2. change the camera scale
3. see light intensity change


### Code

```js

```


### Live example

https://jsfiddle.net/bmqe9fuy/10/

### Screenshots


https://github.com/mrdoob/three.js/assets/5083203/e16eb760-26fb-4db8-9d30-b0e419f983e7


https://github.com/mrdoob/three.js/assets/5083203/202e4287-a390-4d20-8d42-cf6bc98dfc2f



### Version

155

### Device

_No response_

### Browser

_No response_

### OS

_No response_
Repository: kubernetes
Issue: Is the audit log permission configurable?
Labels: sig/api-machinery,triage/accepted

The default permission of the log file to which audit logs are being written is 600. The permission of the compressed log file is the same as that of the log file to which audit logs are being written. The default permission is 600.

In some scenarios, for security purposes, you are advised not to have the write permission on compressed log files. You are advised to provide permission configuration parameters.

The code is at line 468 of lumberjack.go.