sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: create-react-app
Issue: Peer dependency issue happens when npm install
Labels: needs triage,issue: bug report

```
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: react-scripts@5.0.1
npm ERR! Found: typescript@5.1.6
```

### Describe the bug
```
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: react-scripts@5.0.1
npm ERR! Found: typescript@5.1.6
npm ERR! node_modules/typescript
npm ERR!   typescript@"^5.1.6" from the root project
npm ERR!   peer typescript@">= 2.7" from fork-ts-checker-webpack-plugin@6.5.3
npm ERR!   node_modules/fork-ts-checker-webpack-plugin
npm ERR!     fork-ts-checker-webpack-plugin@"^6.5.0" from react-dev-utils@12.0.1
npm ERR!     node_modules/react-dev-utils
npm ERR!       react-dev-utils@"^12.0.1" from react-scripts@5.0.1
npm ERR!       node_modules/react-scripts
npm ERR!         react-scripts@"5.0.1" from the root project
npm ERR!   1 more (tsutils)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peerOptional typescript@"^3.2.1 || ^4" from react-scripts@5.0.1
npm ERR! node_modules/react-scripts
npm ERR!   react-scripts@"5.0.1" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: typescript@4.9.5
npm ERR! node_modules/typescript
npm ERR!   peerOptional typescript@"^3.2.1 || ^4" from react-scripts@5.0.1
npm ERR!   node_modules/react-scripts
npm ERR!     react-scripts@"5.0.1" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! C:\Users\betim\AppData\Local\npm-cache\_logs\2023-06-29T04_51_46_119Z-eresolve-report.txt
```

### Did you try recovering your dependencies?

Yes. Have removed package-lock.json and node_modules, then reinstall, the issue is the same.


### Environment

OS: Windows 11
Node: 18.16.1
Npm: 9.7.2


### Steps to reproduce

`npm install`


### Expected behavior

No error

### Actual behavior

```
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: react-scripts@5.0.1
npm ERR! Found: typescript@5.1.6
```
Repository: material-ui
Issue: Switch drawing over sticky table headers
Labels: discussion,component: switch

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

I have a plain HTML table with a sticky header on my REACT app. If you want to know, the <th> is made sticky using this class:

.main-th {
	position: sticky;
	top: 0px;
}

It works just fine. However, the <Switch> component draws over the header:

![Screenshot 2023-06-29 131153](https://github.com/mui/material-ui/assets/84360664/8d7f6dc7-f53d-4e26-8ded-3a01e39152cd)

I have tried setting the z-index of the component to -1, which works, but then I can't click on the component. 

Is there a property that I need to set to make it behave correctly?

### Current behavior 😯

_No response_

### Expected behavior 🤔

_No response_

### Context 🔦

_No response_

### 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: opencv
Issue: Barcode detection with EAN8 codes is not working reliably
Labels: bug,category: objdetect

### System Information

OpenCV version 4.6.0-4.8.x
Operating System / Platform: Ubuntu 23.04
Compiler & compiler version: GCC 12.2.0

### Detailed description

We are trying to read and decode several Barcodes with OpenCV. We have great success with EAN13 codes, but EAN8 are not working reliably. We provided an image in the attachments, which is read successfully by Halcon, ZBar and ZXing, but OpenCV does neither detect nor decode the barcode. We have this issue with several similar images.

### Steps to reproduce

```cpp
#include <iostream>
#include <vector>
#include <string>
#include <opencv2/imgcodecs.hpp>

#if CV_MINOR_VERSION >= 8
#include <opencv2/objdetect/barcode.hpp>
#else
#include <opencv2/barcode.hpp>
#endif

std::vector<std::string> read(const cv::Mat &image)
{
    cv::barcode::BarcodeDetector detector;
    std::vector<cv::Point> corners;
#if CV_MINOR_VERSION >= 8
    std::vector<std::string> decode_info;
    std::vector<std::string> decoded_type;
    detector.detectAndDecodeWithType(image, decode_info, decoded_type, corners);
#else
    std::vector<cv::String> decode_info;
    std::vector<cv::barcode::BarcodeType> decoded_type;
    detector.detectAndDecode(image, decode_info, decoded_type, corners);
#endif

    return decode_info;
}

int main() {
    auto img = cv::imread("foo.png", cv::IMREAD_GRAYSCALE);

    for (const auto& res : read(img))
    {
        std::cout << res << std::endl;
    }
    return 0;
}
```
![foo](https://github.com/opencv/opencv/assets/33417919/0d567f3f-a586-429c-bb24-285bea871786)


### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: godot
Issue: Crash of editor on Linux with inner classes and dictionaries (signal 11)
Labels: bug,topic:gdscript,topic:editor,crash

### Godot version

Godot Engine v4.0.3.stable.arch_linux

### System information

Arch Linux kernel: 6.3.6-arch1-1

### Issue description

I started a new resource and begin a dictionary in it, then I tried to use field of inner class, defined in another file as key in dictionary.

Its supposed to be like this:
`var dict = { OuterClass.InnerClass.field: value}`

At the moment when I type point after InnerClass editor crashed.

BUT, if I put any mention of OuterClass.InnerClass in same file before dictionary, crash don't happens.



handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.0.3.stable.arch_linux
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[1] /usr/lib/libc.so.6(+0x39ab0) [0x7fcf5c6dcab0] (??:0)
[2] /usr/bin/godot(+0x1481116) [0x556afb9f9116] (??:?)
[3] /usr/bin/godot(+0x147e969) [0x556afb9f6969] (??:?)
[4] /usr/bin/godot(+0x149ca4c) [0x556afba14a4c] (??:?)
[5] /usr/bin/godot(+0x265885f) [0x556afcbd085f] (??:?)
[6] /usr/bin/godot(+0x2a4ddbe) [0x556afcfc5dbe] (??:?)
[7] /usr/bin/godot(+0x49081ea) [0x556afee801ea] (??:?)
[8] /usr/bin/godot(+0x2f2753d) [0x556afd49f53d] (??:?)
[9] /usr/bin/godot(+0x49081ea) [0x556afee801ea] (??:?)
[10] /usr/bin/godot(+0x2e614d5) [0x556afd3d94d5] (??:?)
[11] /usr/bin/godot(+0x48ba7a8) [0x556afee327a8] (??:?)
[12] /usr/bin/godot(+0x2e2d545) [0x556afd3a5545] (??:?)
[13] /usr/bin/godot(+0x2e89776) [0x556afd401776] (??:?)
[14] /usr/bin/godot(+0x10fc227) [0x556afb674227] (??:?)
[15] /usr/bin/godot(+0x10a18b9) [0x556afb6198b9] (??:?)
[16] /usr/lib/libc.so.6(+0x23850) [0x7fcf5c6c6850] (??:0)
[17] /usr/lib/libc.so.6(__libc_start_main+0x8a) [0x7fcf5c6c690a] (??:0)
[18] /usr/bin/godot(+0x10afda5) [0x556afb627da5] (??:?)

### Steps to reproduce

1. Open any project or start a new one
2.  Create script with an inner class
3.  Create another script with a new dictionary
4.  Try to use any field of inner class as key


### Minimal reproduction project

[crush.zip](https://github.com/godotengine/godot/files/11902365/crush.zip)
Repository: TypeScript
Issue: Should `lib` support `disposable`? Should `decorators` be merged with `esnext.decorators`?
Labels: Needs Investigation

Currently, you can access all the explicit resource management stuff via the following `lib` option:

```json
    "lib": ["es2022", "esnext.disposable"],
```

However, the following doesn't work:

```json
    "lib": ["es2022", "disposable"],
```

Should it? It is kind of weird that there is no `disposable` setting whereas you can for `decorators`.

When I looked into this, I realized an oddity - that there is both a `decorators` and `esnext.decorators`, but that they are not the same thing despite both being part of `esnext`. The only difference is that `esnext.decorators` defines `Symbol.metadata`.

These are both part of `esnext`, so should they be merged?
Repository: ant-design
Issue: Menu - Submenu remains visible even after closing the parent menu
Labels: 🐛 Bug,Inactive

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/antd-reproduction-template-forked-mlq88x?file=/index.js)

### Steps to reproduce

1. Click on the "Click me" button to open the dropdown menu
2. Click on the "Submenu" item
3. Press the Esc key to close the parent menu

### What is expected?

Submenu is closed

### What is actually happening?

Submenu remains visible

| Environment | Info |
| --- | --- |
| antd | 5.6.3 |
| React | 18.2.0 |
| System | Pop!_OS 22.04 LTS |
| Browser | Version 114.0.5735.198 |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: TypeScript
Issue: Unsound calls allowed on a function coming from a deferred indexed access when intersection is involved
Labels: Help Wanted,Possible Improvement

# Bug Report

### 🔎 Search Terms

deferred index access unsound call union intersection

### 🕗 Version & Regression Information

- This is the behavior in every version I tried

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?ts=5.2.0-dev.20230629#code/C4TwDgpgBAglC8UDeAoKVSQFxQEQ1wG40oA3AQwBsBXCHAZ2ACcBLAOwHNiBfYlTaACEEyEgJy5BREhRp0obagFsARhCY8+AqAFkI9euQ7REcAD5RBfCAA8wAeybAoAM2psAxsBb22UABbkbAAmlBAAPDpQtsAQIfS6+obGAHwAFB5UlCrkHgDW9Dio6ADaANJQ7LoluAK4ALr1OGlK9BzNUQBkyBjg8hXcAJQ1srQNgwgpUO55bPYA7mw8E8VQ8+zBCwB05MHBAKKkccAAMiyMceppuEpJRhC4ADRQaRBHbMAT8FOr6B6+jCgrQ4Ijexy2wXIwHIUHICR0xHQ6AA9MioPR-PZqJRglA1LC-OomI48RBMtR6NAWMAAOQJYD2exQSBMJTnegsI4kP5ZHL5eglYFbbRwqB5CAgewuXqQKVQTKUbK5Ar1FptLajCCDPhIqCoqC+aAk4D+I0m9RAinOfHzYmcALqCDc+W85UCoUihLiyXSgRyhVK-mq3C4bXOgN8gqC9WesUSuV+6URt2qgCMAAZ02H0EMeCggA)

### 💻 Code

```ts
type A = {
  type: "A";
  value: string;
};

type B = {
  type: "B";
  value: number;
};

type Message = A | B;

export function handle<M extends Message>(callbacks: {
  [K in M["type"]]: (msg: (M & { type: K })["value"]) => unknown;
}) {
  window.addEventListener("message", (event) => {
    const msg = event.data as M;
    // should be an error because it's too permissive
    callbacks[msg.type as keyof typeof callbacks](msg.value);

    // one or the other must be wrong here
    callbacks[msg.type as keyof typeof callbacks]("");
    callbacks[msg.type as keyof typeof callbacks](100);
  });
}
```

### 🙁 Actual behavior

There is no error even though it should be based on Ander's comment [here](https://github.com/microsoft/TypeScript/issues/54680#issuecomment-1606396717). Note that the comment is about a different variant of this signature, one using `Extract`. Both the `Extract` and intersection variants are essentially the same though - one errors today and one doesn't.

### 🙂 Expected behavior

I would expect to get an error here, just like in the `Extract`-based variant ([TS playground](https://www.typescriptlang.org/play?ts=5.2.0-dev.20230629#code/C4TwDgpgBAglC8UDeAoKVSQFxQEQ1wG40oA3AQwBsBXCHAZ2ACcBLAOwHNiBfYlTaACEEyEgJy5BREhRp0obagFsARhCY8+AqAFkI9euQ7REcAD5RBfCAA8wAeybAoAM2psAxsBb22UABbkbAAmlBAAPDpQtsAQIfS6+obGAHwAFB5UlCrkHgDW9Dio6ADaANJQ7LoluAK4ALr1OGlK9Bw4AKI2zLnAkQA0yBjg8hXcKTWytA0AlAgpUO55bPYA7mw8c8VQq+zBawB05MHBHaRxwAAyLIxx6mm4SklGELiDaRDnbMBz8Avb6A8vkYUFaHBEnwuB2C5GA5Cg5ASOmI6HQAHo0VB6P57NRKMEoGoEX51ExHISIJlqPRoCxgAByBLAez2KCQJhKG70FjnEiArI5fL0Epgg7aRFQPIQED2FzDSCyqCZSjZXIFeotNoHKYQGZ8VFQDFQXzQcnAfym83qUHU5xE1ZkzgBdQQPlKgVq4Wi8UJKUyuUCRXK1VCjW4XB6t3BwUFEVan2S6WKwNy6OejUARgADFnI+huJHuCggA))
Repository: next.js
Issue: After rendering pages using SSG (Static Site Generation) in NestJS and running npm run start, the data is blank when navigating to other pages.
Labels: bug,Pages Router

### 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 21.6.0: Sat Jun 18 17:05:47 PDT 2022; root:xnu-8020.140.41~1/RELEASE_ARM64_T8101
    Binaries:
      Node: 18.0.0
      npm: 8.6.0
      Yarn: 1.22.17
      pnpm: 7.5.0
    Relevant packages:
      next: 13.4.7
      eslint-config-next: N/A
      react: N/A
      react-dom: N/A
      typescript: 4.9.4
```


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

Data fetching (gS(S)P, getInitialProps)

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

https://github.com/bosens-China/blog/tree/dev

### To Reproduce

After running `pnpm install`, building the app from the `app` directory, and starting it, you may notice that pagination does not work correctly when clicking on a preview link. However, it works fine after refreshing the page. The navigation component uses the `<Link />` tag.

### Describe the Bug

When navigating to the second page, the data is not rendered correctly according to the expected behavior. However, when inspecting the source code, the data is present but not being rendered on the page.

### Expected Behavior

To maintain consistency with the development environment or achieve the same effect as a page refresh, you need to ensure that the data is rendered correctly when navigating to the second page. Although the source code contains the data, it is not being displayed/rendered on the page.

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

114.0.5735.198

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

_No response_
Repository: vscode
Issue: Grid: distribute split views evenly even when one view requires a larger width
Labels: bug,grid-widget

When you have 2 editors opened side by side where one of the 2 requires a bit more width (for example settings editor or diff editor) and you split to a third editor group, we try to distribute the available width evenly. 

However, if the one editor requires more width, we steal that from the last editor group instead of evenly distribute this across all groups:

![Recording 2023-06-29 at 11 13 50](https://github.com/microsoft/vscode/assets/900690/313e85d6-08cb-4b51-94a2-88b3cfcee534)
Repository: storybook
Issue: [Bug]: Typescript 5.1.3 breaks components using forwardRef
Labels: bug,question / support,has workaround,typescript

### Describe the bug

Hello, since our upgrade from Typescript 5.0.4 to 5.1.3 we have the following errors during our build.

```
src/components/Button/index.stories.tsx:7:3 - error TS2322: Type 'ForwardRefExoticComponent<Props & RefAttributes<HTMLButtonElement>>' is not assignable to type 'ComponentType<ForwardRefExoticComponent<Props & RefAttributes<HTMLButtonElement>>> | undefined'.
  Type 'ForwardRefExoticComponent<Props & RefAttributes<HTMLButtonElement>>' is not assignable to type 'FunctionComponent<ForwardRefExoticComponent<Props & RefAttributes<HTMLButtonElement>>>'.
    Types of property 'propTypes' are incompatible.
      Type 'WeakValidationMap<Props & RefAttributes<HTMLButtonElement>> | undefined' is not assignable to type 'WeakValidationMap<ForwardRefExoticComponent<Props & RefAttributes<HTMLButtonElement>>> | undefined'.
        Type 'WeakValidationMap<Props & RefAttributes<HTMLButtonElement>>' has no properties in common with type 'WeakValidationMap<ForwardRefExoticComponent<Props & RefAttributes<HTMLButtonElement>>>'.

7   component: Button,
    ~~~~~~~~~

  ../../node_modules/@storybook/types/dist/index.d.ts:1221:5
    1221     component?: (TRenderer & {
             ~~~~~~~~~
    The expected type comes from property 'component' which is declared here on type 'ComponentAnnotations<ReactRenderer, ForwardRefExoticComponent<Props & RefAttributes<HTMLButtonElement>>>'

...

```

It seems to only concern components using `fowardRef`.

Please note that only shows up when building our project ( that runs Typescript over all the TS files in `src` ) with `yarn build` but this doesn't occur when running Storybook `yarn storybook`. 

The source code is here https://github.com/openfun/cunningham/tree/93bfaae502dc6fedb1b11f4ce1438d218ce8c5fb/packages/react

It's not a blocking issue but anyway it seems that something is broken since the Typescript upgrade.

Thank you :) 

### To Reproduce

https://github.com/openfun/cunningham/tree/93bfaae502dc6fedb1b11f4ce1438d218ce8c5fb/packages/react

### System

```shell
Environment Info:

  System:
    OS: macOS 13.0.1
    CPU: (10) arm64 Apple M1 Pro
  Binaries:
    Node: 16.20.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 8.19.4 - /usr/local/bin/npm
  Browsers:
    Chrome: 114.0.5735.198
    Edge: 113.0.1774.57
    Safari: 16.1
```


### Additional context

_No response_
Repository: next.js
Issue: SSR-page in App Router doesn't serve the page with compression in 'next start' prod server
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: linux (Arch Linux through WSL2 mount)
      Arch: x64
      Version: #1 SMP Fri Jan 27 02:56:13 UTC 2023
    Binaries:
      Node: 18.16.1
      npm: 9.5.1
      Yarn: 1.22.19
      pnpm: 8.6.5
    Relevant Packages:
      next: 13.4.8-canary.8
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 4.9.4
    Next.js Config:
      output: N/A
```


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

_No response_

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

https://github.com/JesseKoldewijn/Next.js-compression-issue

### To Reproduce

Install the dependencies, build the project and start it using the "next start" command. Or do these steps in a Dockerfile if you want. 

### Describe the Bug

The core issue I've found probably lies in how we deploy our projects at my dayjob. I noticed that, while partially refactoring our Next.js app to the App Router that the html the App Router sends down doesn't get compressed when running the app using the "next start" command. It does however get compressed when deploying to Vercel but not in Docker containers where we use the start script.

### Expected Behavior

I'd expect the production server to send down html compressed either with gzip or brotli.

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

Crome 116.0.5845.4

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

Local & Docker (Azure pipeline)
Repository: TypeScript
Issue: Dead code typecheck elimination
Labels: Suggestion,Awaiting More Feedback

# Suggestion

<!--
  Please fill in each section completely. Thank you!
-->

## 🔍 Search Terms

dead code typecheck elimination

## ✅ Viability Checklist

My suggestion meets these guidelines:

* [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 [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).

## ⭐ Suggestion

When the `include` field is set, TypeScript will only typecheck the given files ... and their dependencies, and transitive dependencies. It can grow unwieldy pretty fast.

It'd be good for performances to if TS could have a `skipDeadCodeTypechecks` call that would cause it to skip the typecheck of all statements that aren't part of the execution tree of the files listed inside `include`.

## 📃 Motivating Example

If you were announcing this feature in a blog post, what's a short explanation that shows
a developer why this feature improves the language?

> In the new TypeScript update, we're excited to introduce the `skipDeadCodeTypechecks` feature. This was born out of the need for a more efficient type-checking process. Previously, when setting the `include` field, TypeScript would typecheck all given files, their dependencies, and their transitive dependencies. This could quickly get out of hand, resulting in a typechecking process that would run over many more files than the author intended!
>
> The `skipDeadCodeTypechecks` feature aims to solve this issue. Instead of typechecking every single file and their dependencies, this new feature will only typecheck the code that is actually executed when the files listed inside include are run. This means that TypeScript will skip typechecking for code that is not part of the execution tree for these files, hence "dead" code.

## 💻 Use Cases

We have a very large repository we're trying to split into reference workspaces. But until we get there, we'd like to selectively pick the folders to typecheck. We do that with the `include` field, but it's still very slow (30s to typecheck what's supposed to be a relatively small part of the application).
Repository: go
Issue: proposal: net/http: support PAC proxy configuration via libproxy
Labels: Proposal


### What version of Go are you using (`go version`)?

go version go1.20.5

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br>
GOARCH="amd64"
GOOS="linux"
</details>

### What did you do?
Trying to access a page behinde a pac proxy.

### What did you expect to see?
Page can be fetched.


### What did you see instead?
Abort.



Please add libproxy support to take care of this.
Repository: vscode
Issue: Enable COI for desktop with `credentialless `
Labels: feature-request,electron,engineering,workbench-electron

For desktop we can enable COI with `COEP: credentialless`. That's possible because chromium supports this new/proposed header value which relaxed loading cross-origin resources lacking the CORP header.
Repository: rust
Issue: Inconsistent naming for '#'
Labels: A-parser,T-compiler,A-docs

### Location

`compiler/rustc_lexer/src/lib.rs`


### Summary


`#` Token is refered to as `Pound`, but it's also refered to as hash sometimes. `n_hashes`

This is a really minor problem, but I just wanted to point it out.