sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: When I create a new project using Next.js and run it without making any changes, I receive the following warning message in my terminal:
Labels: create-next-app,bug

### Verify canary release

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

### Provide environment information

```bash
warn ./node_modules/next/dist/client/add-base-path.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:
* C:\Users\PROLINE\Documents\Builds\swiftlybox\ama\node_modules\next\dist\compiled\@next\react-refresh-utils\dist\loader.js!C:\Users\PROLINE\Documents\Builds\swiftlybox\ama\node_modules\next\dist\build\webpack\loaders\next-swc-loader.js??ruleSet[1].rules[1].oneOf[2].use[1]!C:\Users\PROLINE\Documents\Builds\swiftlybox\ama\node_modules\next\dist\client\add-base-path.js
    Used by 2 module(s), i. e.
```


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

CLI (create-next-app)

### Link to the code that reproduces this issue

https://github.com/christopher-codespaces/nextjs-issue/tree/main

### To Reproduce

Create a new project using Next.js.
Run the project using the command npm run dev.
Observe the warning message displayed in the terminal.

### Describe the Bug

When I create a new project using Next.js and run it without making any changes, I receive the following warning message in my terminal:
warn ./node_modules/next/dist/client/add-base-path.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:
* C:\Users\PROLINE\Documents\Builds\swiftlybox\ama\node_modules\next\dist\compiled\@next\react-refresh-utils\dist\loader.js!C:\Users\PROLINE\Documents\Builds\swiftlybox\ama\node_modules\next\dist\build\webpack\loaders\next-swc-loader.js??ruleSet[1].rules[1].oneOf[2].use[1]!C:\Users\PROLINE\Documents\Builds\swiftlybox\ama\node_modules\next\dist\client\add-base-path.js
    Used by 2 module(s), i. e.

### Expected Behavior

I expect the project to run without any warnings or errors, as I have not made any changes to the code.


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

_No response_

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

_No response_
Repository: flutter
Issue: [tool] Let flutter doctor print the monicker next to the Android Studio version
Labels: tool,t: flutter doctor,c: proposal,P3,team-tool,triaged-tool

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

Sometimes when troubleshooting issues with your Android installation, it is handy to know which version of Android Studio you have installed. Personally I first think about the monicker that comes with the version (i.e. `Electric Eel` or `Flamingo`)
when asking someone else what version they have installed. Just because I don't know what version number is which installation exactly.

However `flutter doctor (-v)` only prints the version number of Android Studio (i.e. `2022.2`).

Example:

```
flutter doctor

[✓] Android Studio (version 2022.2)

flutter doctor -v

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      17.0.6+0-17.0.6b802.4-9586694)
```

### Proposal

Add the monicker that comes with Android Studio releases (if any) to the output of `flutter doctor`.

(with monicker) `Android Studio Flamingo (version 2022.2)`
(without monicker, as it is today) `Android Studio (version 2022.2)`

@andrewkolos Do we also need a list of monickers in the output?
Repository: go
Issue: x/tools/gopls: support textDocument/diagnostic
Labels: Documentation,NeedsInvestigation,gopls,Tools

gopls commands use a `gopls/diagnoseFiles` "non standard request" to implement file diagnostics for commands and testing. Unfortunately, this still publishes diagnostics asynchronously, and so suffers from syncronization problems (e.g. #59475).

There is now a [`textDocument/diagnostic`](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_diagnostic) LSP method that does exactly what we want: return diagnostics for a requested file. We should implement this method and use it instead.

Furthermore, we should remove support for non-standard requests. `workspace/executeCommand` is a better extensibility mechanism.

Implementing `textDocument/diagnostic` should be done with some care: if we advertise this capability, some clients may start requesting diagnostics rather than letting gopls compute them asynchronously. This may have lifecycle and performance implications.

CC @adonovan
Repository: TypeScript
Issue: `infer` not returning expected inner type if another inner type is used in the outer type result
Labels: Possible Improvement

# Bug Report

Given a generic outer type with 2 or more inner types, e.g. `Foo<A, B>`, that does an intersection involving multiple inner types, then `infer` won't return a specific inner type, it will return the intersection of the desired type plus the entire outer type. This is difficult for me to explain since I don't know the correct terms for everything, so please see the example.

### 🔎 Search Terms

infer intersection

### 🕗 Version & Regression Information

- This changed between versions 4.1.5 and 4.2.3

### ⏯ Playground Link

[playground link](https://www.typescriptlang.org/play?ts=5.0.4#code/C4TwDgpgBAYg9nAPAFShAHsCA7AJgZygG8BfAGigDk1McCp9gAnAS2wHMA+KAXilQBkxAFBQoAIwCGTAFxRsAVwC24iEwDcoqJPy4AZnMqaSm4WyxM9kgMbQAgiLHAAFm3b45ilWuPDhoSCgAWRB4OF5YBEQ7CgByHX1YzlMA6ABJbGw1GCY4JTDEGG4+GBosPEICtj01KDSKRlYObgB+OqhPCAA3Hz9UqDYspgiMoZy8gpCw5L9rOGxGbTlB2r4iLRc3DygAJgBmYRMgA)

### 💻 Code

```ts
type Foo<T extends {}, N extends string> = T & {
  bar: number;
  asdf: N;
};

interface A {
  things: number;
}

type MyFoo = Foo<A, 'asdf'>;

type InnerFromFoo<F> = F extends Foo<infer I, string> ? I : never;

type inner = InnerFromFoo<MyFoo>;

const a: inner = {
  things: 23
};
```

### 🙁 Actual behavior

The type `inner` is the intersection of A and `{ bar: number, asdf: string }`

### 🙂 Expected behavior

`inner` should just be `A`
Repository: vscode
Issue: TS problems stick around in problems view even after file is closed/deleted
Labels: bug,javascript

1. Have a TS file open with some error that gets surfaced in the problems view
2. Delete the file
4. :bug: problems are still visible in the problems view

Also saw this for the Copilot suggestions editor after accidentally hitting ctrl+enter in a TS file. The editor's language with all the suggestions gets autodetected as TS, then the problems stick around even after closing the editor
Repository: flutter
Issue: [Impeller] Remove the FLTEnableWideGamut flag.
Labels: engine,P2,e: impeller,team-engine,triaged-engine

This should remove it from the engine and also internal infastructure (see cl/531015044).

The actual timeline for this isn't determined but we want it ASAP.  When it is removed, wide gamut will just be enabled for everyone.
Repository: neovim
Issue: wasm (webassembly) plugins
Labels: enhancement,plugin

### Problem

- Not easy to share C/rust/go plugins without cross-compiling to numerous platforms.
- No builtin way to load a wasm plugin.
- No way to restrict or control plugin [capabilities](https://github.com/bytecodealliance/wasmtime/blob/main/docs/WASI-capabilities.md).

Related vim issue: https://github.com/vim/vim/issues/4604

This is just a tracking issue. Not planned.

### Expected behavior

Nvim can load `.wasm` files conforming to some spec as editor plugins.

### Related

- https://github.com/ziglang/zig/pull/13560
- https://github.com/Borwe/wasm_nvim
- https://github.com/microsoft/vscode-wasm : "WASI implementation that uses the vscode extension host as the implementing API"
    - [from the vscode team](https://github.com/microsoft/language-server-protocol/issues/1264#issuecomment-1324838008): "maps the whole WASI API to the VS Code API. So you can write normal Rust/C/C++ code with normal file system operations and it will transparently be mapped to the VS Code file system API."
Repository: godot
Issue: TileMap: Unexpected offset when painting multiple tiles
Labels: enhancement,topic:editor,usability,topic:2d

### Godot version

4.0.2.stable

### System information

Arch Linux

### Issue description

I have two tiles:

* The purple one is a simple 64x64 tile.
* The blue one is a 64x128 tile. Its Texture Origin is set to (0, 32) so it aligns with the purple one.

![image](https://github.com/godotengine/godot/assets/372476/31f12aaa-de81-451f-b728-91d84cc815fa)

When painting both of them in the editor (Shift select both of them), I expect them to be painted as shown in TileSet/TileMap dock, but the blue one has an unexpected offset.

![image](https://github.com/godotengine/godot/assets/372476/7166d2d1-6022-478d-94d6-3644d44c9367)

I understand that the blue tile is actually located at (64, 0), but the behavior is counterintuitive.

### Steps to reproduce

1. Use the MRP.
2. Select both tiles in the TileMap dock and paint them in the editor.

### Minimal reproduction project

[test-4.zip](https://github.com/godotengine/godot/files/11447532/test-4.zip)
Repository: neovim
Issue: Give autocmd callback arg a `win` field
Labels: enhancement,api,events

### Problem

Autocmd callbacks don't receive a window or win id. For example, this makes it very difficult, if not impossible, to correctly detect which window an option was set in when using an `OptionSet` autocmd.

I have a couple different use-cases atm. One is to refrain from setting (window) options if the opt in question was last set from a modeline. AFAIK, the only way to detect this is to use an `OptionSet` autocmd, which will tell you how the option was set (e.g. `modeline`), but not which window it was set on (am I to assume that it will simply always be the current window within/during the callback?). Yes, it already gives a buffer id as `buf`, but a buffer may have multiple windows, each with different window options, so a window id would be helpful here.

### Expected behavior

Similar to how we already have a `buf` field, give autocmd callback argument tables a `win` field denoting the relevant window. Optionally, do this for all autocmd events (or all where it would make sense), but at the very least, do it for `OptionSet`.

---

It would also be helpful if `vim.api.nvim_get_option_info2()` included a field on the returned table/dict denoting whether the opt was last set from a modeline or not. It seems that the only way to do this currently is to either:

- parse the string output of the vim cmd `verbose setlocal opt?`, or 
- manually keep a record by utilizing an `OptionSet` autocmd
Repository: three.js
Issue: Some coordinate errors after fbx import
Labels: Loaders

### Description

If Inscribe

### Reproduction steps



If Inscribe

### Code

```js
loadModel(name) {
        var scene = this.scene;
        var loader = new FBXLoader();
        loader.load('/model/' + name + ".fbx", function (object) {

            scene.add(object);
            // Try this, but the result is messier
            // object.traverse(function (child) {
            //     if (child.isMesh)
            //         scene.add(child);
            // });
        });
    }
```


### Live example

If Inscribe

### Screenshots

![2023-05-11_103949](https://github.com/mrdoob/three.js/assets/36830623/f3374ecb-146a-449d-bffd-a40c02f3d15a)
![2023-05-11_104049](https://github.com/mrdoob/three.js/assets/36830623/8a771065-844c-459b-82af-2072d5919292)
![2023-05-11_104732](https://github.com/mrdoob/three.js/assets/36830623/651fa638-16d3-451d-9a6f-48bff1c85164)
![2023-05-11_104754](https://github.com/mrdoob/three.js/assets/36830623/39edda67-f789-4c2b-8086-25e2981f6abd)


### Version

    "three": "^0.152.2",

### Device

Desktop

### Browser

Chrome, Safari, Edge

### OS

Windows, MacOS
Repository: tensorflow
Issue: [TFLite] flatbuffer64 support for TFlite
Labels: stat:awaiting tensorflower,type:feature,TFLiteConverter,TF 2.12

Dear,
flatbuffer has limit of 2G size.
but for now, many models like stable-diffusion, llama has the size larger than 2G, can not be convertted to tflite.
Is there any plan TFlite update to flatbuffer64 ?

Thanks
Repository: next.js
Issue: with-relay-modern doesn't bootstrap correctly
Labels: examples

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release
- This little checkbox makes zero sense for my bug report

### Provide environment information

```bash
Operating System:
      Platform: linux
      Arch: x64
      Version: #1 SMP PREEMPT_DYNAMIC Mon, 01 May 2023 17:42:39 +0000
    Binaries:
      Node: 19.9.0
      npm: 8.19.2
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.4.1
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
```


### Which example does this report relate to?

with-relay-modern

### Describe the Bug

The README specifies this command for bootstrapping the project:
```
npx create-next-app --example with-relay-modern with-relay-modern-app
```

And here's the output on my machine:
```
Creating a new Next.js app in /home/brandon/src/with-relay-modern-app.

Downloading files for example with-relay-modern. This might take a moment.

Installing packages. This might take a couple of minutes.

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: undefined@undefined
npm ERR! Found: react@18.2.0
npm ERR! node_modules/react
npm ERR!   react@"^18.2.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.9.0" from react-relay@9.1.0
npm ERR! node_modules/react-relay
npm ERR!   react-relay@"^9.0.0" 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! See /home/brandon/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/brandon/.npm/_logs/2023-05-11T03_05_18_925Z-debug-0.log

Aborting installation.
  npm install has failed.
```

### Expected Behavior

The example app works without error, in `with-relay-modern-app/`.

### To Reproduce

Open a shell and run the bootstrap command, e.g.
```
npx create-next-app --example with-relay-modern with-relay-modern-app
```
Repository: deno
Issue: error: Could not resolve 'npm:@swc/wasm-web@1.3.57'
Labels: bug,needs investigation,node compat

Attempting to import [swc-wasm](https://www.npmjs.com/package/@swc/wasm-web) fails with the following error message:


```shell
> deno run main.ts
error: Could not resolve 'npm:@swc/wasm-web@1.3.57'.

Caused by:
    not found

> deno run --node-modules-dir main.ts
error: Could not resolve 'npm:@swc/wasm-web@1.3.57'.

Caused by:
    not found
```

Below is the content of `main.ts`.

```ts
import * as swc from "npm:@swc/wasm-web@1.3.57";
console.log(swc);
```

related(?): #17424 #17257
Repository: flutter
Issue: [Impeller] ☂️ Tie up loose ends in the wide-gamut support transition.
Labels: engine,P2,e: impeller,team-engine,triaged-engine

This is an umbrella issue detailing the steps we need to follow to finish up remaining action items to enable wide-gamut support and transition existing users. This was discussed in the last Impeller Weekly on May 10, 2023. Just enumerating the action items here. The action items must roughly be completed in this order.

- [x] https://github.com/flutter/flutter/issues/126499
- [ ] https://github.com/flutter/flutter/issues/126501
- [x] https://github.com/flutter/flutter/issues/126500
- [ ] https://github.com/flutter/flutter/issues/126476
Repository: flutter
Issue: [Impeller] Opt internal Google3 customers in to using wide-gamut support on iOS after manual testing.
Labels: engine,P2,e: impeller,team-engine,triaged-engine

Part of https://github.com/flutter/flutter/issues/126498
Repository: flutter
Issue: M3 NavigationBar's NavigationDestinations are not making space for docked FAB
Labels: framework,f: material design,a: fidelity,c: proposal,P2,team-design,triaged-design

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

### Introduction
To create space for the docked FAB, one of the way is to use a SizedBox widget in between NavigationDestinations.

For example, the following code shows how to create a NavigationBar with five destinations and a docked FAB:

```
NavigationBar(
  destinations: [
    navDestination1,
    navDestination2,
    SizedBox(),
    navDestination3,
    navDestination4,
  ],
  onDestinationSelected: (int index) {
    // Handle navigation
  },
);
```
This code will create a NavigationBar with five destinations and a docked FAB. The FAB will be centered between the second and third destinations.

<img width="300" alt="Screenshot 2023-05-11 at 2 19 48 PM" src="https://github.com/flutter/flutter/assets/12880287/71edab9f-ad68-4c0f-9e5c-d6324e7f2cb3">

### The Problem
However, this solution does not work when the app is in a larger screen device like an iPad mini. When the app is rotated into horizontal orientation, it will switch to NavigationRail. In this scenario, the FAB is no longer docked on NavigationBar and will be at the leading part of NavigationRail.

Because the list of destinations changed from 5 items (NavigationBar) to 4 items (NavigationRail), we get a range error:
`Another exception was thrown: RangeError (index): Invalid value: Not in inclusive range 0..3: 4
`

### Reproducible code:
[https://dartpad.dev/?id=628d12c0793418e8c35d41c098c3c64b](https://dartpad.dev/?id=628d12c0793418e8c35d41c098c3c64b)

### Proposal

I was hoping that the NavigationDestination widget would automatically make space for the FAB, without the need to add an additional SizedBox to the destinations list. Alternatively, I would like to see the NavigationRail widget accept a List of `Widgets` .

Material 3 Navigation Bar Placement: 
[https://m3.material.io/components/navigation-bar/guidelines#c5a1eb4e-7837-4063-8e11-9b3ce1879d6a](https://m3.material.io/components/navigation-bar/guidelines#c5a1eb4e-7837-4063-8e11-9b3ce1879d6a)

<img width="1072" alt="Screenshot 2023-05-11 at 1 33 37 PM" src="https://github.com/flutter/flutter/assets/12880287/f39898f8-7356-463c-a7ab-a27aed753c1c">
Repository: next.js
Issue: [NEXT-1163] App dir dynamic routes treats '%2F' in page params as '/' when deployed to Vercel
Labels: bug,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.4.0: Mon Mar  6 21:00:17 PST 2023; root:xnu-8796.101.5~3/RELEASE_X86_64
    Binaries:
      Node: 19.6.0
      npm: 9.4.0
      Yarn: 1.22.18
      pnpm: 7.27.0
    Relevant packages:
      next: 13.4.2-canary.5
      eslint-config-next: 13.3.4
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.0.4
```


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

_No response_

### Link to the code that reproduces this issue

https://github.com/eBakken/next-13-page-params

### To Reproduce

Clone repo and deploy to Vercel.

It can also be seen here:
[https://next-13-page-params.vercel.app/app/foo/bar/foo%2Fbar](https://next-13-page-params.vercel.app/app/foo/bar/foo%2Fbar)

### Describe the Bug

Dynamic routing in `/app` directory treats `%2F` as `/`.

`encodeURIComponent("foo/bar")` gives `"foo%2Fbar"`

But the page params for the URL `/foo/bar/foo%2Fbar` gives `["foo","bar","foo","bar"]` when deployed to Vercel.
See [https://next-13-page-params.vercel.app/app/foo/bar/foo%2Fbar](https://next-13-page-params.vercel.app/app/foo/bar/foo%2Fbar)

The problem does not appear locally when running `yarn dev`.

### Expected Behavior

I would expect the behavior to be the same as when using `/pages`: `["foo","bar","foo/bar"]`.
See [https://next-13-page-params.vercel.app/pages/foo/bar/foo%2Fbar](https://next-13-page-params.vercel.app/pages/foo/bar/foo%2Fbar)

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

_No response_

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

Vercel

<sub>[NEXT-1163](https://linear.app/vercel/issue/NEXT-1163/app-dir-dynamic-routes-treats-percent2f-in-page-params-as-when)</sub>
Repository: vscode
Issue: Editor languate status busy icon, most distracting thing ever!!
Labels: languages-basic,under-discussion,workbench-status

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->


i believe this is the a busy icon create but "Editor Lanaguate Status" feature in the status bar 
the fact that this thing jumps up and down, appearing the dissappearing is completely distracting
because if you have several other status label they are shifted right and left. 
this thing should be pushed to the far most right corner, and should have a blank space..
or it shouldn't be spinning, everything to keep all the labels in their current position. 

![image](https://github.com/microsoft/vscode/assets/13434544/503eb6f8-a75d-4848-a52e-a8bd781cc3ad)
Repository: godot
Issue: Reloading material doesn't reload saved shader parameters
Labels: discussion,topic:editor,topic:shaders

### Godot version

v4.1.dev2.official [668cf3c66]

### System information

Windows 10

### Issue description

Reloading material doesn't reload saved shader parameters.

### Steps to reproduce

1. Load «polygon_2d.tscn».
2. Select «Polygon2D».
3. Change Shader Parameters:
   - C to red;
   - F to 10;
   - B to false.
4. Don't save anything.
5. Load/Quick Load «material.material».

Expected result:
- C is yellow;
- F is 5;
- B is true.

Actual result:
- C is red;
- F is 10;
- B is false.

### Minimal reproduction project

[Bug.zip](https://github.com/godotengine/godot/files/11449611/Bug.zip)
Repository: pytorch
Issue: round float16 calculation error in mps backend
Labels: triaged,module: correctness (silent),module: mps

### 🐛 Describe the bug

import torch
x = torch.tensor([8.5], dtype=torch.half).to("mps")
y = torch.round(x)

y is 9 but should be 8 (According to the rules of "round half to even" in the [doc](https://pytorch.org/docs/stable/generated/torch.round.html?highlight=torch+round#torch.round))

### Versions

This issue was found in pre-ci, and I don't have a mac to reproduce this bug. For details please see https://github.com/pytorch/pytorch/actions/runs/4944088105/jobs/8839307876

cc @kulinseth @albanD @malfet @DenisVieriu97 @jhavukainen @razarmehr @abhudev