sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: @next/mdx doesn't work as expected in production (on vercel)
Labels: bug,Internationalization (i18n),Runtime,Markdown (MDX)

### Link to the code that reproduces this issue

https://github.com/Patrik-Tkacik/Nextjs-reproduction

### To Reproduce

Clone the repository, `npm install`  and run `npm run dev`, go on the root/localized pag
e which will most likely be /en for you, and check out the CaseStudies function, on localhost, whether you're running dev mode or build it and start it, it works. This is how it should look like: <img width="1249" alt="Screenshot 2024-05-05 at 17 48 31" src="https://github.com/vercel/next.js/assets/157832795/ffb2f804-0972-46e1-aa8e-3d094ccae19f">

now check it out from my vercel hosted app [here]( https://kukk-dev.vercel.app/en).

### Current vs. Expected behavior

Those projects you see in the CaseStudies function, are individual MDX pages that get collected by the lib/mdx.ts file. That should give the data to all components and it does, it also gives the info to make the pages. Now my issue is when running this in production it generates the mdx pages into normal tsx pages no problem, but it doesn't give the data to the components like CaseStudies. When I debugged it a little it was because the CaseStudies function doesn't get anything in the array. I have found a [stackoverflow answer](https://stackoverflow.com/questions/77689122/cant-find-files-in-production-using-fast-glob-and-process-cwd-with-dynami) which I hoped would help me, because it worked fine before I localized this project (I modified a template) so I thought that was it but it cant be, maybe its glob, maybe its mdx, it doesn't make sense to me. The stackoverflow indicated the blob is the issue, but it didnt have any issues giving data to generate the static pages at build time on vercel. What could it be?

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.3.0: Wed Dec 20 21:33:31 PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T8112
  Available memory (MB): 8192
  Available CPU cores: 8
Binaries:
  Node: 21.4.0
  npm: 10.2.5
  Yarn: 1.22.21
  pnpm: 8.12.1
Relevant Packages:
  next: 14.2.3 // Latest available version is detected (14.2.3).
  eslint-config-next: 14.0.4
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


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

Developer Experience, Internationalization (i18n), Markdown (MDX), Runtime

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

Vercel (Deployed)

### Additional context

_No response_
Repository: godot
Issue: Incorrect winding order for imported GLTF with PRIMITIVE_TRIANGLE_STRIP
Labels: bug,needs testing,topic:import

### Tested versions

4.2.1

### System information

debian

### Issue description

Inside `gltf_document.cpp` I can see conversions CCW->CW for Triangles but not for Triangle Strips, causing imported gltf with triangle strip primitives to have flipped face winding, causing inverted face culling.

### Steps to reproduce

Import any GLTF with Triangle Strip mode for mesh primitives

### Minimal reproduction project (MRP)

Test model: 
[test_model.zip](https://github.com/godotengine/godot/files/15327640/test_model.zip)
Repository: godot
Issue: Can't load textures in gray color space
Labels: bug,enhancement,needs testing,topic:import

### Tested versions

v4.3.dev6.official [89850d553]

### System information

Godot v4.3.dev6 - macOS 14.4.1 - Vulkan (Forward+) - integrated Apple M1 Max - Apple M1 Max (10 Threads)

### Issue description

<img width="1303" alt="image" src="https://github.com/godotengine/godot/assets/60579014/4316f7f4-a634-4a7b-9bfd-feabf427d011"><br>

This is what macos tells me about them:

<img width="288" alt="image" src="https://github.com/godotengine/godot/assets/60579014/4b3b85c5-e65a-4881-b37f-fb7071b02ab7"><br>

This is what some online analyzer tells:

<img width="500" alt="image" src="https://github.com/godotengine/godot/assets/60579014/abab1cb6-d244-4e77-81b4-6e1339d63bc9">

<img width="500" alt="image" src="https://github.com/godotengine/godot/assets/60579014/991cf354-68c9-47ce-9a3d-91781e16641b">

<img width="500" alt="image" src="https://github.com/godotengine/godot/assets/60579014/0fb045aa-3111-4eb5-9f76-0e62ab2e29c8"><br>

RGB textures load with no problem

### Steps to reproduce

MRP

### Minimal reproduction project (MRP)

Image that gives an identical error provided by @theraot:

https://github.com/user-attachments/files/15511511/new_test.zip
Repository: PowerToys
Issue: Always on Top frame not matching window size when snapping it to the side of the screen (Windows 11 only)
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.80.1

### Installation method

Microsoft Store

### Running as admin

No

### Area(s) with issue?

Always on Top

### Steps to reproduce

![image](https://github.com/microsoft/PowerToys/assets/168993001/fdd146a4-1759-4946-beac-8498cfb7cc77)
[PowerToysReport_2024-05-05-21-01-11.zip](https://github.com/microsoft/PowerToys/files/15214181/PowerToysReport_2024-05-05-21-01-11.zip)
When I snap an Always-on-Top window to a part of the screen (Windows 11), the orange frame doesn't match the window size.

### ✔️ Expected Behavior

Window frame should shrink to the size of the window while snapping it to the side of the screen.

### ❌ Actual Behavior

Window frame didn't change the size to match the window while snapping it to the side of the screen.

### Other Software

_No response_
Repository: godot
Issue: Pixel artifacts on model in 3D - Gets more prevalent the lower the resolution
Labels: discussion,topic:rendering,documentation,topic:3d

### Tested versions

- Tested in 4.2.2.stable

### System information

MacOS 14.4.1 - M1 Pro - Vulkan (Forward+) / Windows 11 23H2 - GTX 1060 6GB

### Issue description

Pixel artifacts appear on the player character model in the 3D scene. The rogue pixels appear to be behaving with an "X-ray" effect, where it shows color of the geometry behind what should be rendered in front.

Notice how the artifacts become much more frequent and noticeable the lower resolution the game is set at. Videos of tested resolutions are as follows:

https://github.com/godotengine/godot/assets/65742713/c16ec3e8-9962-4426-963a-aa463621df21


https://github.com/godotengine/godot/assets/65742713/5098d100-6ae2-45f1-965a-6b11c9a5d48f


https://github.com/godotengine/godot/assets/65742713/0b9316a7-cc60-44b7-a942-821757c5695d


https://github.com/godotengine/godot/assets/65742713/f5619b1f-cbcb-4e30-ad02-ca270bd1034c



### Steps to reproduce

1. Open the attached MRP and run the game.
2. Walk around with A/D and jump with Space.
3. Observe artifacts as the player model animates.
4. Experiment with the resolution in Project > Project Settings > Window > Size.

I worked with the Godot Discord community to troubleshoot for a few days, including ensuring model LODs were turned off, changing rendering and AA settings, but nothing fixed the issue.

### Minimal reproduction project (MRP)

[Pixel Artifacts.zip](https://github.com/godotengine/godot/files/15214415/Pixel.Artifacts.zip)
Repository: PowerToys
Issue: Menu in English/french when language is set to french
Labels: Issue-Bug,Area-Runner,Needs-Triage,Issue-Translation

### Microsoft PowerToys version

0.80.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

General

### Steps to reproduce

When right click in task bar, the menu is in french, except "settings" instead of "paramètres"
[PowerToysReport_2024-05-05-22-33-07.zip](https://github.com/microsoft/PowerToys/files/15214492/PowerToysReport_2024-05-05-22-33-07.zip)


### ✔️ Expected Behavior

all menu should be in french

### ❌ Actual Behavior

part of menu is in english

### Other Software

_No response_
Repository: pytorch
Issue: DISABLED test_train_parity_2d_mlp (__main__.TestFullyShard2DTraining)
Labels: module: rocm,triaged,skipped

Platforms: rocm

This test was disabled because it is failing on main branch ([recent examples](https://torch-ci.com/failure?failureCaptures=%5B%22test%2Fdistributed%2F_composable%2Ffsdp%2Ftest_fully_shard_training.py%3A%3ATestFullyShard2DTraining%3A%3Atest_train_parity_2d_mlp%22%5D)).

cc @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang
Repository: puppeteer
Issue: [Feature]: Add ability to exclude web sockets from WaitForNetworkIdle
Labels: feature,P3

### Minimal, reproducible example

```TypeScript
Minimal example is go to any website (chat.openai.com, google oauth page, etc) the uses websockets and use waitForNetworkIdle.
```


### Error string

Timeout error

### Bug behavior

- [ ] Flaky
- [ ] PDF

### Background

Websockets is not a valid "pending" connection and should be considered network idle or there should be an option to ignore websockets. Using networkidle0 or networkidle2 events of page.goto is not a solution due to the full page navigation requirement which is not compatible with app-like interfaces of modern web that use SPA or ajax.

### Expectation

waitForNetworkIdle should return regardless of WebSocket connections.

### Reality

waitForNetworkIdle does not return and will timeout even with concurrency set to some arbitrary number.

### Puppeteer configuration file (if used)

```TypeScript
Default config.
```


### Puppeteer version

22.6.2

### Node version

18.18.0

### Package manager

npm

### Package manager version

9.8.1

### Operating system

Windows
Repository: PowerToys
Issue: Add a quick open new enviroment with vscode
Labels: Needs-Triage

### Description of the new feature / enhancement

Sometime when you have to want to create a quick POC or create a new project and open it in vscode. You have to create a folder then go to vscode open it the from power toy you are able to access it.

I want a feature like when you type `{{ `or `{ {test_project` it should able to create a folder in default specified directory and able to open folder in vscode

SO basically create a new folder & open it in vscode

### Scenario when this would be used?

When you need to run a quick script or make a quick POC or don't want to navigate to folder to just create & open folder in vscode

### Supporting information

_No response_
Repository: godot
Issue: `AudioStreamPolyphonic` ignores the `AudioStreamPlayer` pitch and volume properties
Labels: bug,topic:audio

### Tested versions

Reproducible in 4.2.1.stable (haven't had time to reproduce in other versions, sorry. If needed I can do in a couple of days)

### System information

Godot v4.2.1.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1080 Ti (NVIDIA; 31.0.15.5212) - Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz (8 Threads)

### Issue description

While using the AnimationPlayer to change the pitch scale property of an AudioStreamPlayer, the pitch is unaltered, both in editor and at runtime.

### Steps to reproduce

Play an animation that changes the pitch scale property of an AudioStreamPlayer node and plays an AudioStream res.

### Minimal reproduction project (MRP)

[pitch_bug_test_project.zip](https://github.com/godotengine/godot/files/15215231/pitch_bug_test_project.zip)
Repository: next.js
Issue: Server Actions don't respect the `NextResponse.redirect` from Middleware
Labels: bug,Middleware

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/server-action-and-middleware-redirect-j54l2f

### To Reproduce

See the reproduction link. 

TL;DR:
1. Have a server action that gets called from a client component's button
2. Add a middleware that returns `NextResponse.redirect()` when `request.method === 'POST'` (P.S. the condition could be authenticating the user session)
3. Click the button to trigger the server action
4. The page doesn't redirect as instructed in the middleware

### Current vs. Expected behavior

**Current**: The page doesn't redirect
**Expected**: The page redirects as instructed in the middleware

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 4102
  Available CPU cores: 2
Binaries:
  Node: 20.11.1
  npm: 10.2.4
  Yarn: 1.22.19
  pnpm: 8.15.4
Relevant Packages:
  next: 14.3.0-canary.40 // Latest available version is detected (14.3.0-canary.40).
  eslint-config-next: 14.2.1
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.5
Next.js Config:
  output: N/A
```


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

Middleware

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

next dev (local)

### Additional context

The reason is that the server action's fetch call follows the redirect:
https://github.com/vercel/next.js/blob/1ae14bafdb197a712c0bbb9b6570f4d04bd849e3/packages/next/src/client/components/router-reducer/reducers/server-action-reducer.ts#L62-L80

There is also no consistent way to handle it (catching the server action errors) on the client side. If the redirected page responds 2xx, the server action doesn't throw an error.

A workaround would be mimicking the server actions' `redirect()` response in the middleware:

```typescript
  if (request.headers.get('Accept') === 'text/x-component') {
    return new NextResponse(null, {
      status: 303,
      headers: {
        'X-Action-Redirect': url
      }
    });
  }
``` 

However, this workaround feels very hacky.

Related issue: #62469
Repository: vscode
Issue: Introduce NotebookDocumentChangeEvent#reason 
Labels: debt,notebook-api

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

Had a discussion with @dbaeumer and learnt that adding `reason` was perhaps not sufficient or not what was required.
Salient points of the meeting:
* Existing event is unfortunately a little complex and difficult to use/understand, as this event can be triggered for a number of reasons related to notebook content and notebook execution state changes.
    * Hence consumers will likely make assumptions when consuming this event.
* When consuming this event (at least in the case of LSP)
    * Difficult to understand the current execution state (starting, executing, stopped, etc)
    * Are changes a result of execution or other


A follow up discussion will be required with @dbaeumer and a few others to some of the above issues (& possibly others, if any) are addressed


For https://github.com/microsoft/vscode/issues/211142
Repository: PowerToys
Issue: PT-Run calculator: disable number formats for the input
Labels: Idea-Enhancement,Status-In progress,Needs-Triage,Run-Plugin

### Description of the new feature / enhancement

Add a toggle to disable number formatting requirement for the input, so we would use numbers like 123,456.78 and 123 456,78 - note that period and comma in the decimal part are interchangeable.

### Scenario when this would be used?

I am one of those people who have both English and Russian keyboard layouts with English regional formats. As such, when I am inputting numbers from the numpad it is coin toss if I am going to input "123.45" or "123,45" - English and Russian float formatting respectively. This is where the proposed feature comes in, providing user with a toggle to disable formatting to treat both "2.5" and "2,5" as "two and a half", rather than "two and a half" and "twenty five".

### Supporting information

Related, but old with no solution: #12121 #13562 #25285
Repository: ant-design
Issue: Tooltip 从空字符到有值后，不会马上渲染，需要鼠标移出后再移入才显示
Labels: Inactive,🧶 Low Priority

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/edit/react-wubjtr?file=demo.tsx)

### Steps to reproduce

点击文字、观察 Tooltip 是否显示

### What is expected?

Tooltip 显示

### What is actually happening?

Tooltip 不显示，需要移出再移入才显示

| Environment | Info |
| --- | --- |
| antd | 5.17.0 |
| React | latest |
| System | mac |
| Browser | chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: next.js
Issue: Event Propagation Inconsistency: `stopPropagation` Fails in App Router (but not Pages router)
Labels: create-next-app,bug

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/vigorous-water-ffzkny?file=%2Fapp%2Fpage.tsx%3A4%2C29

### To Reproduce

1. start the application in development
2. hover your cursor over the red box (see attached photo)
3. note that the despite `e.stopPropagation()` on the red box, a `mouseover` event is still logged due to the native body `mouseover` listener

<img width="638" alt="Screenshot 2024-05-05 at 11 14 46 PM" src="https://github.com/vercel/next.js/assets/107879266/6754b06d-402e-4217-8549-adb489e0fedf">


### Current vs. Expected behavior

Current Behavior:
- `e.stopPropagation()` is ignored and the `mouseover` event bubbles up to the `body` mouseover listener

Expected Behavior:
-  the `body` mouseover listener should never fire while hovering over the red box
- the same code behaves as expected with the pages router, i.e. a mouseover event on the red box does not trigger a body mouseover event
- see this link for the pages router example: https://codesandbox.io/p/devbox/vibrant-moser-2cz5ks

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 4102
  Available CPU cores: 2
Binaries:
  Node: 20.9.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.10.2
Relevant Packages:
  next: 14.3.0-canary.40 // Latest available version is detected (14.3.0-canary.40).
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

create-next-app, Developer Experience

### Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local)

### Additional context

I tested in latest Chrome and Safari and with both dev and prod builds. The bug happens every time with the app router, but not with the pages router.
Repository: rust
Issue: The const-eval interpreter is called on incomplete/invalid/ill-formed code
Labels: T-compiler,C-bug,A-const-eval

It looks like https://github.com/rust-lang/rust/issues/76064 is back. This is the source of countless ICEs. Just in the last few weeks:
- https://github.com/rust-lang/rust/issues/121858
- https://github.com/rust-lang/rust/issues/123690
- https://github.com/rust-lang/rust/issues/124436
- https://github.com/rust-lang/rust/issues/124164

As member of @rust-lang/wg-const-eval my position is that generally these are not const-eval bugs, but bugs in whatever part of the compiler is passing invalid data to const-eval. However, which part would that be? I am not sure whom to ping for this.^^
Repository: rust
Issue: `u128::midpoint`'s implementation could be better
Labels: I-slow,requires-nightly,T-libs

Today it uses the hackers delight trick

https://github.com/rust-lang/rust/blob/96f1da82687f499dd3f57006ae71548714532382/library/core/src/num/mod.rs#L127-L131

but
```rust
#![feature(num_midpoint)]
#[no_mangle] pub fn demo(x: u128, y: u128) -> u128 { x.midpoint(y) }
```
gives
```x86
demo:
        mov     rax, rdx
        xor     rax, rdi
        mov     r8, rcx
        xor     r8, rsi
        shrd    rax, r8, 1
        shr     r8
        and     rcx, rsi
        and     rdx, rdi
        add     rax, rdx
        adc     r8, rcx
        mov     rdx, r8
        ret
```

Whereas if it was instead 
```rust
#[no_mangle] pub fn demo(x: u128, y: u128) -> u128 {
    let (z, c) = x.overflowing_add(y);
    (z >> 1) | (u128::from(c) << 127)
}
```
that compiles to
```x86
demo:
        mov     rax, rdi
        add     rax, rdx
        adc     rsi, rcx
        setb    cl
        shrd    rax, rsi, 1
        movzx   edx, cl
        shld    rdx, rsi, 63
        ret
```
which seems strictly better.

(Alternatively you could try making it an intrinsic with a fallback body, since the obvious LLVM -- <https://llvm.godbolt.org/z/c56YrMz8c> -- seems to work decently.)
Repository: node
Issue: Prevent [ERR_STREAM_PREMATURE_CLOSE] error log when intentionally closing a stream before end
Labels: question,stream

### Version

18.18.0

### Platform

Darwin arm64

### Subsystem

node:internal/streams

### What steps will reproduce the bug?

I have a call to a database which returns a stream. When consuming the stream, I need to end it prematurely if a certain condition is met:

```javascript
import {pipeline} from 'stream/promises';
import {createWriteStream} from 'fs';

async function* myAsyncGenerator() {
	const stream = await someCalltoDb();

	for await (const rows of stream) {
		for (const row of rows) {
			// Stop consuming the stream if a certain condition is true
			if (someConditionIsTrue) {
				return stream.destroy();
			}

			yield row;
		}
	}
}

(async () => {
	const asyncGen = myAsyncGenerator();
	const outputStream = createWriteStream('output.txt');
	await pipeline(asyncGen, outputStream);
})();
```

This code terminates successfully (exit code 0) but it logs the following`[ERR_STREAM_PREMATURE_CLOSE]` error on the console:

![image](https://github.com/nodejs/node/assets/12783208/397b445c-dde9-46c2-ae5f-a29dd819fa65)




### How often does it reproduce? Is there a required condition?

_No response_

### What is the expected behavior? Why is that the expected behavior?

I could be wrong, but this `[ERR_STREAM_PREMATURE_CLOSE]` error doesn't seem to originate on the stream object received from the call to the database, I suspect instead that this can orginate from another stream that is writing on this one (e.g. a stream from the socket who is writing the data?).

In this case I am voluntarily closing the stream before consuming all the data, so I don't want to see this `[ERR_STREAM_PREMATURE_CLOSE]` logged on the console. Also it doesn't seem to be an error, but just the log of an error, because the program terminates with success (exit code 0).

Is there any way to prevent this `[ERR_STREAM_PREMATURE_CLOSE]` error log to appear in the console?

### What do you see instead?

```
Error [ERR_STREAM_PREMATURE_CLOSE]: Premature close
    at new NodeError (node:internal/errors:405:5)
    at Transform.onclose (node:internal/streams/end-of-stream:159:30)
    at Transform.emit (node:events:529:35)
    at Transform.emit (node:domain:489:12)
    at emitCloseNT (node:internal/streams/destroy:132:10)
    at processTicksAndRejections (node:internal/process/task_queues:81:21) {
  code: 'ERR_STREAM_PREMATURE_CLOSE'
}

Process finished with exit code 0
```

### Additional information

_No response_
Repository: vscode
Issue: Color-highlight popups
Labels: bug,quick-pick,under-discussion

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

The credential popup (and similar input-requiring popups) would deserve some more contrast color, it is unnecessarily easy to overlook.
<img width="412" alt="image" src="https://github.com/microsoft/vscode/assets/16520646/8f0e054e-db7a-4cbc-aa6a-5c231178a89b">

It's just a small lean-approach improvement that should be too easy to implement to even talk about - just make it red/yellow.

<details>
  <summary>Why...</summary>
I was patiently waiting 5 minutes for a seemingly hanging `git pull` in terminal before killing it. Went on to `printenv | grepi -i proxy`, `wget https://github`, updating token in `./git-credentials` without noticing it's for wrong server url, and even ask a friend, until I noticed the creds popup. :) 
</details>