sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: material-ui
Issue: [Button][material-ui] Button href TypeScript error
Labels: component: button,typescript

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Hi, I found issue that really looks like mine : https://github.com/mui/material-ui/issues/22699
Steps:

1. Developing in typescript 
2. Use <Button with href
3. add target="_blank" property to it
4. I get error ;
TS2769: No overload matches this call.
  Overload 1 of 3, '(props: { href: string; } & ButtonOwnProps & Omit<ButtonBaseOwnProps, "classes"> & CommonProps & Omit<Omit<DetailedHTMLProps<AnchorHTMLAttributes<HTMLAnchorElement>, HTMLAnchorElement>, "ref"> & { ...; }, "color" | ... 24 more ... | "startIcon">): Element', gave the following error.
    Type 'string | undefined' is not assignable to type 'string'.
      Type 'undefined' is not assignable to type 'string'.

Trying to set strictNullChecks: true in tsconfig.json does not solve the problem


### Current behavior 😯

typescript transpile error

### Expected behavior 🤔

_No response_

### Context 🔦

_No response_

### Your environment 🌎

  System:
    OS: Linux 5.19 Ubuntu 22.04.3 LTS 22.04.3 LTS (Jammy Jellyfish)
  Binaries:
    Node: 16.18.0 - /usr/local/bin/node
    Yarn: 1.22.19 - ~/.yarn/bin/yarn
    npm: 9.6.4 - /usr/local/bin/npm
  Browsers:
    Chrome: 117.0.5938.132
  npmPackages:
    @emotion/react: ^11.11.1 => 11.11.1 
    @emotion/styled: ^11.11.0 => 11.11.0 
    @mui/base:  5.0.0-beta.17 
    @mui/core-downloads-tracker:  5.14.11 
    @mui/icons-material: ^5.14.11 => 5.14.11 
    @mui/material: ^5.14.11 => 5.14.11 
    @mui/private-theming:  5.14.11 
    @mui/styled-engine:  5.14.11 
    @mui/system:  5.14.11 
    @mui/types:  7.2.4 
    @mui/utils:  5.14.11 
    @types/react: ^18.2.12 => 18.2.12 
    react: ^18.2.0 => 18.2.0 
    react-dom: ^18.2.0 => 18.2.0 
    typescript: ^4.9.5 => 4.9.5
Repository: kubernetes
Issue: Kubernetes ephemeral storage exhausted by a pod, rendering the cluster unusable
Labels: kind/bug,sig/storage,kind/feature,triage/accepted

### What happened?

https://kubernetes.io/docs/concepts/policy/resource-quotas/
When several users or teams share a cluster with a fixed number of nodes, there is a concern that one team could use more than its fair share of resources.
Resource quotas are a tool for administrators to address this concern.
AND

https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#meaning-of-cpu
If the user doesn't specify the ephemeral-storage resource limit in the Pod spec, the resource quota is not enforced on ephemeral-storage.

This is FATAL to production level use of a Kubernetes cluster.
In one occurrence a pod using a web based file browser interface allowed uploading files.
Uploading a real big file e.g. 5 GB causes the NGINX pod(s) to exhaust ephemeral storage.

This renders ANY application running on the cluster to become UNREACHABLE through the NGINX ingress controller.

A pod should not be allowed to do this - especially if there is a resource quota already introduced.

However "If the user doesn't specify the ephemeral-storage resource limit in the Pod spec, the resource quota is not enforced on ephemeral-storage." totally cripples this safety mechanism.

### What did you expect to happen?

Not to have Nginx become unavailable due to one pod exhausting ephemeral storage.


### How can we reproduce it (as minimally and precisely as possible)?

deploy a pod that allows uploading files using e.g.
image: filebrowser/filebrowser:v2.22.4

Use the Webgui to upload a file that is larger than the ephemeral storage available to node running the (E.g) nginx pod 

Watch the memory of nginx grow along with the size of the file uploaded and eventually "blow up"

### Anything else we need to know?

_No response_

### Kubernetes version

v1.26.2


### Cloud provider

bare metal K8s

### OS version

OS
linux (amd64)
OS Image
Ubuntu 22.04.2 LTS
Kernel version
5.15.0-69-generic
Container runtime
containerd://1.6.15
Kubelet version
v1.26.2

### Install tools

kubeadm


### Container runtime (CRI) and version (if applicable)

Container runtime
containerd://1.6.15

### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: PowerToys
Issue: Text Extractor: Change language by switching input method.
Labels: Idea-Enhancement,Needs-Triage,Needs-Team-Response,Product-Text Extractor

### Description of the new feature / enhancement

Change language by switching input method. When your input method switched to English, it will recognize English text.

### Scenario when this would be used?

When there are different languages on your screen, and you don't want to change the language manually.

### Supporting information

![Untitled](https://github.com/microsoft/PowerToys/assets/114793567/e16bb1cf-1a6f-4389-b55c-013f95082765)
Try to copy this text by Text Extractor. It's inconvenient.
Repository: go
Issue: x/tools/internal/refactor/inline: good starter projects
Labels: help wanted,NeedsFix,Tools,Refactoring

Below is a list of starter projects for anyone who wants to get their hands dirty in the inliner logic. Before starting work on any item, please fork it off into a separate issue, briefly stating the approach you plan to take.

- [x] allow conversions (other than []byte(string), which observably allocates) to be considered duplicable (#67589).
- [x] omit unnecessary interface conversions in argument passing (#68554).
- [ ] simplify "binding decl" to use `param := arg` when it's not necessary to state the type.
- [x] improve precision of check of whether arg elimination removes last ref to a caller var...
    ...and instead of preventing elimination, blank out the var decl.
- [ ] avoid imports.Process by reimplementing just the algorithm we need.
- [ ] choose better local names for renaming imports
- [x] ~~avoid unnecessarily renaming imports (may need additional inputs?)~~ (#67281)
- [ ] implement "void tail call" strategy (i.e. f() statement before return stmt). If the return stmt is pure, this is sound even if the callee uses defer.
- [ ] implement parameterless call to { stmt; return expr } from one of these contexts:
```
        //    x, y     = f()
        //    x, y    := f()
        //    var x, y = f()
```
- [x] use binding decls even with the literalization strategy: it's easier and more natural to read `func() { var param=arg; ... } ()` than `func(param) { ... } (arg)`. (Beware: binding decls cover params and named result vars; they may need to be teased apart.)
- [ ] clean-up (?): unify pure, duplicable, and effects into a single pass.
- [ ] use callee's FileSet (calleeFset) to format the new node (res.new), as it is mostly callee code. This should reduce comment loss. (Beware: it seems to introduce spurious newlines. Why?)

See also:
- https://github.com/golang/go/issues/68236
- https://github.com/golang/go/issues/63717
- https://github.com/golang/go/issues/70759

More challenging projects:
- [ ] Translate `if f(); cond { ... }` to `{ fbody; if cond { ... } }` when the inlining of f() is not a simple expression.- [ ] Add a control flow analysis that is more precise than the current "single assignment" predicate. Currently, a binding declaration is required if an argument is a variable that is not "single assignment". But if all the assignments can be proved to occur before or after the call (but not during it using lambdas) then a binding declaration may not be needed.
- [ ] Add an alias analysis so that effects on memory by the callee can be localized to particular variables, allowing writes to commute with reads if they cannot alias.
- [ ] Better handling of spread calls (`f(g())` where g returns >1 result).
Repository: go
Issue: runtime: TestDebugCallGrowStack failures
Labels: NeedsInvestigation,compiler/runtime

```
#!watchflakes
post <- pkg == "runtime" && test == "TestDebugCallGrowStack" && log ~ `morestack on g0`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/1f5d351a65339bf3159ee59ea6602d3ed393ce6a)):

    fatal: morestack on g0
    trap in unknown function runtime.abort
    SIGTRAP: trace trap
    PC=0x70a99c42f662 m=12 sigcode=128
    
    rax    0x17
    rbx    0x70a99c767be2
    rcx    0x70a99c430fd5
    rdx    0x17
    rdi    0x2
    ...
    fs     0x0
    gs     0x0
    
    runtime.notetsleepg(0x70a900000064?, 0x30?)
    	/workdir/go/src/runtime/lock_futex.go:236 +0x29 fp=0xc00091be78 sp=0xc00091be40 pc=0x70a99c3c37e9
    runtime.InjectDebugCall(0xc0000c3040, {0x70a99c82d7c0, 0x70a99c8c2cb8}, 0x0, {0x0, 0x0}, 0x70a99c8c31e0, 0x0)
    	/workdir/go/src/runtime/export_debug_test.go:68 +0x3c5 fp=0xc00091bf00 sp=0xc00091be78 pc=0x70a99c4200c5
    runtime_test.TestDebugCallGrowStack(0xc000304340)
    	/workdir/go/src/runtime/debug_test.go:221 +0x56 fp=0xc00091bf70 sp=0xc00091bf00 pc=0x70a99c6b0a76
    testing.tRunner(0xc000304340, 0x70a99c8c15c0)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: next.js
Issue: Styles are not removed when navigating away from a page, app router
Labels: bug

### Link to the code that reproduces this issue

https://github.com/Specy/next-style-bug

### To Reproduce

1. Start the dev server 
2. Go to `localhost:3000` (the button is red, the button has a default green background and it was overridden by a local style module in the page)
3. Click the link at the bottom of the page to visit the `/layer` page (here the button has the default green color)
4. Click the link at the bottom of the page to go back to the root page
5. Now the button is green (the style from button of the `/layer` page overrides the one in the main page)

https://github.com/Specy/next-style-bug/assets/59029985/466936c5-650b-417d-9cee-2e0236905df5


### Current vs. Expected behavior

Current:
The style of the button gets overridden by the styles of `/layer` page

Expected:
The styles of the `/layer` do not override the ones in the main page

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Home
Binaries:
  Node: 20.2.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 13.5.4-canary.11
  eslint-config-next: 13.5.4
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.2.2
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

App Router

### Additional context

_No response_
Repository: PowerToys
Issue: Color Picker - view and copy options
Labels: Idea-Enhancement,Needs-Triage,Product-Color Picker

### Description of the new feature / enhancement

This tool is great, but could be slightly better. 
Currently you can only choose one Default Color format. This is the format that is both viewed and copied.
You gave the option to show the color name as well, also quite useful.
But it would be nice to be able to show other formats as well. I would like the hex value copied and shown, along with the color name, but I would also like to see the RGB float values listed and would also like to see the total value listed as well.

### Scenario when this would be used?

 This is useful for inspecting several values around the screen just to see how they shift over time or wanting to quickly calculate how far the value of two colors are from each other. For instance, full green and full red are painful to see next to each other. But they are fine so long as the value is far enough apart. Or you might be looking at a bunch of grey colors to make sure there is enough contrast between them for an interface. 

### Supporting information

_No response_
Repository: godot
Issue: Bug: When engine automatically re-imports GLB it adds copy of imported 3d model to every opened 3d scene
Labels: bug,topic:editor,topic:import,topic:3d

### Godot version

4.1 rc2 https://github.com/godotengine/godot/commit/46424488edc341b65467ee7fd3ac423e4d49ad34

### System information

win 10

### Issue description

When engine automatically re-imports GLB it adds "ghost" copy of imported 3d model to every opened 3d scene. 



### Steps to reproduce

Please watch video of me trying to reproduce it. Bug occurs in the end of video:

https://github.com/godotengine/godot/assets/3350340/0da1eabd-fdc0-49b2-96a3-e3a7bf456026

1. Create Empty 3D scenes.
2. Open them up.
3. import glb file
4. add inherited scene from glb file, dont save it
5. add glb file to one of scenes
6. add glb file to another scene and make it local
7. add another empty 3d scece:
7.1 add a mesh to third scene, 
7.2 add animation player
7.3 add animation library and add some animations exported from glb
8. Don't close Dodot, keep all scenes open, edit mesh in blender and resave it. focus godot window, godot will reimport glb model
9. bug should occur.

### Minimal reproduction project

N/A. 
You need a simple mesh with skeleton, and several empty 3d scenes, and interact with blender.
Repository: vscode
Issue: New Debug Controls In Command Center Needs Some Layout Changes
Labels: debug,under-discussion,command-center

Type: <b>Bug</b>

This is about #192592 

Currently the debug controls in the command center look like this. And its really not pretty, since you have one side loaded with elements and the other side wide empty:

<img width="907" src="https://github.com/microsoft/vscode/assets/2157285/83b81dbb-d7c9-4a0f-bd74-c980ede7fa6b">

I propose that you change the &bullet; with a flexible space and have the `monaco-toolbar`'s flex direction set to `row-reverse` and have this look:

<img width="907" src="https://github.com/microsoft/vscode/assets/2157285/42bd19a5-3700-46b1-ae50-c2d02f4d4671">

It feels more spacious and even on the both sides. Also the window title is clearly divided from the debug controls.


VS Code version: Code - Insiders 1.83.0-insider (4268e464763087044d0c1b5bdd37ebbe683cadfa, 2023-09-29T20:44:05.310Z)
OS version: Darwin arm64 23.0.0
Modes:
Repository: pytorch
Issue: Explore Hybrid (CPU+GPU) Graphs in Scalar parameters
Labels: feature,triaged,oncall: pt2,module: inductor

### 🚀 The feature, motivation and pitch

As observed across https://github.com/pytorch/pytorch/issues/107006#issuecomment-1741841283, https://github.com/pytorch/pytorch/pull/110345#discussion_r1344183030
Inductor currently is unable to reason properly about graphs that have tensors spread across CPU and GPU.

This forces us to coerce to GPU the scalar computations and corresponding scalar inputs in Adam-like and Adagrad/Adamax. Inductor then launches a single small prelude kernel. This choice may be suboptimal as this small kernel launch is unlikely to saturate the GPU. 

https://github.com/pytorch/pytorch/blob/ff96f6d04f062e660224e7ba1f00da867d25d0de/test/inductor/test_compiled_optimizers.py#L128

One possible solution would be to have inductor generate CPU kernels for the scalar part of the computation, and GPU kernels for the main optimizer step.

### Alternatives

It is unclear if this incurs a large enough cost to justify the effort. 

It is also unclear if saturating the GPU with this kernel is necessary - if multiple chunks/groups are launched, then a small kernel can be running concurrently alongside a big kernel launch.

@mlazos @janeyx99 for advice on whether this direction does deserve more investigation.

cc @ezyang @msaroufim @wconstab @bdhirsh @anijain2305 @zou3519 @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @peterbell10 @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @aakhundov @ColinPeppler @Xia-Weiwen
Repository: next.js
Issue: Next.js TypeError: Cannot read properties of undefined (reading 'bind') - caused by middleware.ts
Labels: linear: next

### 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: x64
  Version: Darwin Kernel Version 22.6.0: Wed Jul  5 22:21:56 PDT 2023; root:xnu-8796.141.3~6/RELEASE_X86_64
Binaries:
  Node: 16.13.1
  npm: 8.19.2
  Yarn: 1.22.11
  pnpm: N/A
Relevant Packages:
  next: 13.5.4
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: N/A
Next.js Config:
  output: standalone
```


### Which example does this report relate to?

https://github.com/vercel/next.js/blob/canary/examples/with-docker/README.md

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

_No response_

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

_No response_

### Describe the Bug

I getting   following error on run next app after `npm run build` 
 
```
(node:50480) ExperimentalWarning: stream/web is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
 ⚠ "next start" does not work with "output: standalone" configuration. Use "node .next/standalone/server.js" instead.
  ▲ Next.js 13.5.4
  - Local:        http://localhost:3000

 ✓ Ready in 257ms
TypeError: Cannot read properties of undefined (reading 'bind')
    at NextNodeServer.handleRequestImpl (/Users/michal.stys/OwnProjects/next13-test/node_modules/next/dist/server/base-server.js:389:50)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
TypeError: Cannot read properties of undefined (reading 'bind')
    at NextNodeServer.handleRequestImpl (/Users/michal.stys/OwnProjects/next13-test/node_modules/next/dist/server/base-server.js:389:50)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
```

My middleware.ts from next.js docs. 

```
import { NextRequest, NextResponse } from "next/server";

const PUBLIC_FILE = /\.(.*)$/;

export async function middleware(req: NextRequest) {
  if (
    req.nextUrl.pathname.startsWith("/_next") ||
    req.nextUrl.pathname.includes("/api/") ||
    PUBLIC_FILE.test(req.nextUrl.pathname)
  ) {
    return;
  }

  if (req.nextUrl.locale === "default") {
    const locale = "en";
    return NextResponse.redirect(
      new URL(`/${locale}${req.nextUrl.pathname}${req.nextUrl.search}`, req.url)
    );
  }
}
```

PS. all works perfect without this middleware


### Expected Behavior

Type error doesn't exists if using middleware.ts

### To Reproduce

```
npx create-next-app --example with-docker nextjs-docker
```
// add middleware.ts added above

```
npm run build
npm start
```

<sub>[NEXT-1739](https://linear.app/vercel/issue/NEXT-1739/nextjs-typeerror-cannot-read-properties-of-undefined-reading-bind)</sub>
Repository: create-react-app
Issue: npm ERR! code ENOENT while creating reactapp
Labels: needs triage

C:\Users\Lenovo>npx create-react-app hello
npm ERR! code ENOENT
npm ERR! syscall spawn C:\Users\Lenovo\AppData\Local\Programs\Python\Python311\
npm ERR! path C:\Users\Lenovo
npm ERR! errno -4058
npm ERR! enoent spawn C:\Users\Lenovo\AppData\Local\Programs\Python\Python311\ ENOENT
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in: C:\Users\Lenovo\AppData\Local\npm-cache\_logs\2023-10-03T15_31_35_328Z-debug-0.log
Repository: TypeScript
Issue: Implementation signatures that do not contain all overloaded signatures are allowed in class definitions
Labels: Bug

### 🔎 Search Terms

implementation contain overloaded class member

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about overloading class member functions


### ⏯ Playground Link

https://www.typescriptlang.org/play?ts=5.2.2#code/FAYwNghgzlAEDCwDexZtgMwPZYBSwgH5YAuWAOwFcBbAIwFMAnWASlNgDcsBLAEwG5U6bHgLsqdJgBpYtcTQbM2ZLn0HpMOfBHmTGM2sTITFrdqt5C0KDRpBZyULGHoA6MFgDm+AC4BPAAd6LAwxFn5YAHpI2H8gkLFuOBMmK1gAX2BM4HJ6AHcEXBZXESKIqJiAxm5yHzgAIkpyXnoMGvpeeuAgA

### 💻 Code

```ts
class C
{
    foo( a? : number ) : void;
    foo( a : number, b : number ) : void;
    foo( a : number, b? : number ) : void
    {
        console.log( typeof a ); // typeof a is number
    }
}

new C().foo();  // prints "undefined"
```


### 🙁 Actual behavior

The compilation succeeded.

The type of argument "a" in function foo is number but prints "undefined" which is wrong.

Because the implementation signature of foo does not include all overload signatures, so compilation should fail.


### 🙂 Expected behavior

The compilation should fail.

### Additional information about the issue

This bug is only reproduced with class member functions.
Repository: next.js
Issue: Vercel deployment issue for favicon
Labels: bug

### Link to the code that reproduces this issue

https://github.com/Eshwar1212-maker/Sports-Sync/tree/development

### To Reproduce

Start the appllicaiton in the dev server, then get your env variables from the required websites listed in the README, all of them are free

### Current vs. Expected behavior

Im having a huge issue with changing my favicon in Next 13, it showed in development, but not in production, and Vercel is giving me wierd logs saying "odule not found: Can't resolve '/vercel/path0/app/favicon.ico?__next_metadata__'". I dont know why.

### Verify canary release

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

### Provide environment information

```bash
Nextjs 13 app router
```


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

App Router

### Additional context

_No response_
Repository: vscode
Issue: "Realtime performance" does not appear to be localized
Labels: debug,debt



![Image](https://github.com/microsoft/vscode-js-debug/assets/2193314/2415a88f-ad7e-4ff6-8589-7755a438abcb)
Repository: godot
Issue: In WebGL, CharacterBody3D gets stuck on trying to slide over RigidBody3D kinematic even if move_and_slide has been called
Labels: bug,platform:web,topic:porting,topic:physics,needs testing

### Godot version

v4.1.1.stable.official [bd6af8e0e]

### System information
**Found originally with:**
Godot v4.1.1.stable - Windows 10.0.22621 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3080 Laptop GPU (NVIDIA; 31.0.15.3742) - 12th Gen Intel(R) Core(TM) i9-12900H (20 Threads)

**Most recently reproduced with:**
Godot v4.2.beta2 - Windows 10.0.22621 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3080 Laptop GPU (NVIDIA; 31.0.15.4584) - 12th Gen Intel(R) Core(TM) i9-12900H (20 Threads)
 
### Issue description

This happens only on the WebGL build, not on PC Desktop.
A CharacterBody3D character won't slide along a wall with a kinematic RigidBody3D and will get stuck until the player changes direction. This doesn't happen immediately, though, but only if player doesn't touch a wall for a while. This makes me suspect that perhaps this has to do with the sleeping settings? The RigidBody3D wall has the sleeping and can sleep settings set as false.

### Steps to reproduce

- Build the project as WebGL
- Launch it and select Start on the intro scene
- Move with WASD and try to slide along the edge of the field. It will work.
- Relaunch and this time wait a minute or two before trying to slide along the edge of the play field
- Character will get stuck

### Minimal reproduction project
[CollisionTestWebGL.zip](https://github.com/godotengine/godot/files/13072895/CollisionTestWebGL.zip)