sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: powertoys Run garbled code
Labels: Issue-Bug,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.75.1

### Installation method

Scoop

### Running as admin

None

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

![image](https://github.com/microsoft/PowerToys/assets/51876176/50c1f389-c8f8-468b-a2a8-6f98c3fe2324)
Candidate item, the character to be matched is garbled. If that character is typed out, the garbled character will disappear.

### ✔️ Expected Behavior

No garbled characters

### ❌ Actual Behavior

Display garbled characters

### Other Software

none
Repository: tauri
Issue: [bug] On Windows, the default app mode in custom color mode reverses the theme colors
Labels: type: bug,platform: Windows,status: needs triage

### Describe the bug

Only when Windows is in `custom color mode`. Changing the `default app mode` will cause Tauri to use the opposite theme colors.

If the color mode is `Light` or `Dark`, then Tauri is also the corresponding theme color.

![theme-color](https://github.com/tauri-apps/tauri/assets/13819168/e2ed9209-8533-4ccd-8dcc-e8babdfb1453)


### Reproduction

1. Windows colors: https://support.microsoft.com/en-us/windows/change-colors-in-windows-d26ef4d6-819a-581c-1581-493cfcc005fe#WindowsVersion=Windows_11
2. Select a custom color mode.
3. Try switching the default app mode and observe the title bar of the Tauri application.

### Expected behavior

Should match the theme color of the default app mode.

### Platform and versions

```text
[✔] Environment
    - OS: Windows 10.0.22631 X64
    ✔ WebView2: 119.0.2151.44
    ✔ MSVC: Visual Studio 生成工具 2022
    ✔ rustc: 1.73.0 (cc66ad468 2023-10-03)
    ✔ cargo: 1.73.0 (9c4383fb5 2023-08-26)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 18.16.0
    - pnpm: 8.10.0
    - npm: 9.6.5

[-] Packages
    - tauri [RUST]: 1.5.2
    - tauri-build [RUST]: 1.5.0
    - wry [RUST]: 0.24.4
    - tao [RUST]: 0.16.5
    - @tauri-apps/api [NPM]: 1.5.1
    - @tauri-apps/cli [NPM]: 1.5.6

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../dist
    - devPath: http://localhost:1420/
    - framework: React
    - bundler: Vite
```


### Stack trace

_No response_

### Additional context

The registry can get the theme color used by the app:

`HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Themes\Personalize`

Default app mode: `AppsUseLightTheme`
Default windows mode: `SystemUsesLightTheme`
Repository: angular
Issue: Angular 16: Array of nested Proxy object with ngFor/ngModel cause call stack overflow or timeout the page
Labels: area: common

### Which @angular/* package(s) are the source of the bug?

common

### Is this a regression?

I don't know

### Description

For debugging purpose I have created this function for proxy nested object with a listener for log property value changes.

```ts
function buildProxy(poj: any, callback = console.log, tree = []): any {
  return new Proxy(poj, {
    get(target, prop) {
      const value = Reflect.get(target, prop);
      if (
        value !== null &&
        typeof value === 'object' &&
        ['Array', 'Object'].includes(value.constructor.name)
      ) {
        return buildProxy(value, callback, tree.concat(prop as any));
      }
      return value;
    },
    set(target, prop, value) {
      callback({
        action: 'set',
        path: tree.concat(prop as any).join('.'),
        newValue: value,
        preValue: Reflect.get(target, prop, value),
      });
      return Reflect.set(target, prop, value);
    },
  });
}
```

This works well in angular (https://stackblitz.com/edit/stackblitz-starters-rqsl2q ), eg:

```ts
@Component({
  selector: 'my-app',
  standalone: true,
  imports: [CommonModule, FormsModule],
  template: `
  <input type="text" [(ngModel)]="singleObj.foo.name"> `,
})
export class App 
  singleObj = buildProxy({ foo: { name: 'Angular 15' } });
}
```
![uploading](https://github.com/angular/angular/assets/6096678/cbf3d1c9-4f63-48af-ab72-5741a09ed192)


the problem happen if a proxy object is used in a ngFor, in this case the result is a call stack overflow or timeout the page (see https://stackblitz.com/edit/stackblitz-starters-652pf3 ), eg:

```ts
@Component({
  selector: 'my-app',
  standalone: true,
  imports: [CommonModule, FormsModule],
  template: `
  <div *ngFor="let obj of arrayObj">
    <input type="text" [(ngModel)]="obj.foo.name">  
  </div> `,
})
export class App {
  arrayObj = buildProxy([
    { foo: { name: 'Angular 15' } },
    { foo: { name: 'Angular 16' } },
  ]);
}
```

![image](https://github.com/angular/angular/assets/6096678/df24f135-805b-42f5-bffe-0d222d99159a)


### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-rqsl2q?file=src%2Fmain.ts

### Please provide the exception or error you saw

call stack overflow or timeout the page


### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular 16 (see example: https://stackblitz.com/edit/stackblitz-starters-rqsl2q)
```


### Anything else?

_No response_
Repository: neovim
Issue: job control: robust process management, teardown
Labels: enhancement,status:blocked-external,job-control

# Problem

(This is currently just a placeholder... corrections/insights are welcome, though.)

https://catern.com/process.html explains numerous problems with the unix process interface, and mentions Linux's `pidfd` as a solution for robustly sending signals to children (section 3) handling child exit (section 4) as an alternative to PIDs.

We are using PIDs to stop processes: 

- https://github.com/neovim/neovim/blob/0774d0cfe1d5efb4bdd34cc8cf3799af5c947d2e/src/nvim/event/process.c#L233

Notes:

- we always detach child processes on unix (so we can [kill the process group](https://github.com/neovim/neovim/pull/8107) instead of traversing the descendants):  https://github.com/neovim/neovim/blob/0774d0cfe1d5efb4bdd34cc8cf3799af5c947d2e/src/nvim/event/libuv_process.c#L40-L41
- we always try to kill all children when Nvim exits: https://github.com/neovim/neovim/blob/0774d0cfe1d5efb4bdd34cc8cf3799af5c947d2e/src/nvim/event/process.c#L136-L145

# Expected behavior

Killing a process tree via `os_proc_tree_kill`, and on Nvim exit, is fast and correct.

- Because we are only(?) dealing with processes that we started, it's probably ok that we are using PIDs--because if any of the children died beforehand, then Nvim would have already handled that and evicted the process from its jobs list.
    - TODO: confirm if this intuition is correct.
- On linux we could try to use `pidfd` but that would be an unpleasant workaround. So presumably we're blocked until libuv offers an API.

# Related

- https://github.com/libuv/libuv/issues/4179
- https://github.com/catern/supervise (from the author of https://catern.com/process.html )
  > Guaranteed termination of all the transitive children of a child process
Repository: next.js
Issue: [Next 14] Partial Pre-Rendering (`ppr`) causes duplicate fetch calls on page revalidation
Labels: bug

### Link to the code that reproduces this issue

https://github.com/better-salmon/next14-ppr-double-revalidation-bug

### To Reproduce

1. Run backend server with `npm run backend`.
2. In the separate terminal build and start the app with `npm run build && npm run start`.
3. Open [http://localhost:3000/count](http://localhost:3000/count) in the browser.
4. Wait for the `Cache state` field to change to `stale`.
5. Reload the page twice to see the revalidated page with `Cache state: fresh`.
6. Optionally, open the terminal with the backend and see that in logs `/count` route was triggered twice.

### Current vs. Expected behavior

**Expected behavior:**

When `ppr` option is enabled or disabled, the value should be greater than before by 1 after each revalidation.

**Actual behavior:**

When `ppr` option is enabled, the value is greater than before by 2 after each revalidation, meaning that the fetch was triggered twice.

### 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 23.1.0: Mon Oct  9 21:28:31 PDT 2023; root:xnu-10002.41.9~6/RELEASE_ARM64_T8112
Binaries:
  Node: 20.9.0
  npm: 10.1.0
  Yarn: N/A
  pnpm: 8.10.0
Relevant Packages:
  next: 14.0.2-canary.13
  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)

App Router

### Additional context

_No response_
Repository: vscode
Issue: Merge Editor: Accept Combination When Edits replace same range with same new text
Labels: feature-request,merge-conflict

This is a special case of https://github.com/microsoft/vscode/issues/165685, in which the edits are exactly the same.
Here, the edits are not the same, but there would be a canonical way to auto-merge both edits:

![Code_-_Insiders_bkLMB4IMSN](https://github.com/microsoft/vscode/assets/2931520/fa39240f-14fd-4bff-86c4-7ba593d89aab)


```json
{
    "languageId": "typescript",
    "base": "\tfilter(element: TreeElement): boolean {\n\t\tif (ResourceTree.isResourceNode(element)) {\n\t\t\treturn true;\n\t\t} else if (isSCMResourceGroup(element)) {\n\t\t\treturn element.elements.length > 0 || !element.hideWhenEmpty;\n\t\t} else {\n\t\t\treturn true;\n\t\t}\n\t}",
    "input1": "\tfilter(element: TreeElement): boolean {\n\t\tif (ResourceTree.isResourceNode(element)) {\n\t\t\treturn true;\n\t\t} else if (isSCMResourceGroup(element)) {\n\t\t\treturn element.resources.length > 0 || !element.hideWhenEmpty;\n\t\t} else {\n\t\t\treturn true;\n\t\t}\n\t}",
    "input2": "\tfilter(element: TreeElement): boolean {\n\t\tif (ResourceTree.isResourceNode(element)) {\n\t\t\treturn true;\n\t\t} else if (isSCMResourceGroup(element)) {\n\t\t\treturn element.resources.length > 0 || !element.hideWhenEmpty;\n\t\t} else if (isSCMHistoryItemGroupTreeElement(element)) {\n\t\t\treturn (element.count ?? 0) > 0;\n\t\t} else {\n\t\t\treturn true;\n\t\t}\n\t}",
    "result": "\tfilter(element: TreeElement): boolean {\n\t\tif (ResourceTree.isResourceNode(element)) {\n\t\t\treturn true;\n\t\t} else if (isSCMResourceGroup(element)) {\n\t\t\treturn element.elements.length > 0 || !element.hideWhenEmpty;\n\t\t} else {\n\t\t\treturn true;\n\t\t}\n\t}",
    "initialResult": "\tfilter(element: TreeElement): boolean {\n\t\tif (ResourceTree.isResourceNode(element)) {\n\t\t\treturn true;\n\t\t} else if (isSCMResourceGroup(element)) {\n\t\t\treturn element.elements.length > 0 || !element.hideWhenEmpty;\n\t\t} else {\n\t\t\treturn true;\n\t\t}\n\t}"
}
```
Repository: godot
Issue: Static while looping audio using AudioStreamPlayer3D
Labels: bug,topic:audio

### Godot version

4.1.2.stable

### System information

Windows 10 - 4.1.2.stable

### Issue description

Using the AudioStreamPlayer3D or AudioStreamPlayer node to play audio has a noticeable static noise after some period of looping.


Here is a video from a minimal project that showcases this:

https://clipchamp.com/watch/FiPJFo5YdQ6

### Steps to reproduce

1) Import a audio file and then re-import with `Looping` enabled. In my test case I am using `.wav` format
2) Create a basic 3D scene with a `Node3D` as the root node and a `AudioStreamPlayer3D` as a child. 
3) Add the imported audio file as the `Stream` of the AudioStreamPlayer3D
4) Add a `Camera3D` as a child of the root `Node3D`
5) Start that scene

The audio file that I used will be in the Minimal reproduction below.

### Minimal reproduction project

[AudioTest.zip](https://github.com/godotengine/godot/files/13267093/AudioTest.zip)

Just add the audio file to the `Stream` section of the `AudioStreamPlayer3D` and hit start.
Repository: vscode
Issue: Diff Algorithm: Common words are not aligned
Labels: bug,diff-editor

Align Common Words:


![Image](https://github.com/microsoft/vscode/assets/2931520/2bb46aa3-96c3-44e5-98ac-e9e26269187c)


[Monaco Editor Playground Repro](https://microsoft.github.io/monaco-editor/playground.html?source=v0.45.0-dev-20231025#XQAAAAITBQAAAAAAAABBqQkHQ5NjdMjwa-jY7SIQ9S7DNlzs5W-mwj0fe1ZCDRFc9ws9XQE0SJE1jc2VKxhaLFIw9vEWSxW3yscw7pIAaAEiAJM8XEuX7Os378jBGtVLkr6ryuhqvky-XZ9Sy0vyFSI1m9lYQpwqOsaKmhydYWIo-9hGbv_4wlPFQRH2_ZKdnYQM8wfm0XJ7mLtINxEywCME2hrZMAQoyRFUi4Vrs5nKvswePn9kVfycFKUjU_PkaI1IHEiuF5fKDjYNb_auHdn2X_6NTdE-9FKPzCup648OErU3A6fXVblP2l-0IJuP7EU6g-CYc0kpt1LcWUPSgoGBwHNnSovh5R2qnmqj43JubDQ8ipoT7AzXTJS32mL-wVpR-YjdmvcT8RAss0DeJEzIsGoOnyamNtGupZmQ0VGmoNgBlqDHFpM04NFLxlMy6k0PSnsMw1Mr20AFuc14-o5GbHlgac5uud9Gmyb9b0j_kidCbYuSdnE1NK8hFgDovsfdYxeJPucedKHrnDc4IkrHPCYbt0iZk8KF0qT5hnPSlwI_Yv00nBkPnhR6kPfpItjhcnqJoAPkwDcXxYiezGtCQt2rhdf7bYL6r6k7hmqnHYQeGO6G6pQkEgAQ57Bqir1CTRjZ2-FXTEwj4ZQNbj3O5FRZQuAHTR7rCwOA2YVtBE1cQu4ZCKUzbleBDfe7tRKgL7fUj89Isq0Zv_b6wutXpaiI4I_AZVnK8kbbcpoaCFf8gyxTMcaW5eeQYVZ6lfx4eYOHs4jF41ULvJB-VwAAt21MCjQ0ABWt0bH_D6U_AA)
Repository: vscode
Issue: Merge Editor: Improve Experience For This Conflict
Labels: polish,merge-conflict

Try to solve this conflict using the merge editor:

[merge-conflict.json](https://github.com/microsoft/vscode/files/13267302/merge-conflict.json)

It might be a good idea to try solving this conflict using other tools as well.

This conflict happened like this:
* `fb1 := main o c1 o c2`
* `fb2 := fb1 o c3 o c4`
* `main' := merge(main o squash(c1 o c2), main o ...)`

Now, when merging `main'` into `fb2`, there is conflict.

These conflicts could be resolved by squashing `c1` and `c2` in `fb2` and then rebasing `fb2` onto `main'`.

FYI @lszomoru
Repository: storybook
Issue: [Documentation]: Use React Context "default" values for low-overhead container mocking
Labels: documentation

### Describe the problem

https://storybook.js.org/docs/react/writing-stories/build-pages-with-storybook#avoiding-mocking-dependencies

In the "Avoiding Mocking Dependencies section of the docs, the suggested strategy is to provide the component via Context, so that Storybook can pass in mock versions of the container component and the app can pass down the real one.

The approach described in the Docs requires wrapping the app in a context that provides the original container component, which is impractical and cumbersome when scaling the strategy across many components.

Instead, the docs should suggest creating a context that simply uses the real container component as the default value, so the app falls back to it when there is no provider. 

For example:

```js
/** components/SearchForm/SearchFormContainer.jsx
 *  A container that handles business logic and data transactions, and 
 *  accepts a Presenter component in a Render function
 */

export function SearchFormContainer ({ render }) {
  async function handleSubmit (value) {
     // ...handle submit logic
  }

  return render({ onSubmit: handleSubmit })
}

export const SearchFormContainerContext = createContext(SearchFormContainer)

/** components/SearchForm/index.js
 *  A single component that connects the container to the presenter in a way that
 *  makes the container interchangeable with a mock container.
 */

export function SearchForm() {
  const SearchFormContainer = useContext(SearchFormContainerContext)

  return (
    <SearchFormContainer
      render={({ onSubmit }) => <SearchFormPresenter onSubmit={onSubmit} />}
    />
  )
}

```



No additional configuration is necessary.

This variation greatly simplifies the process of using a container/presenter division strategy when developing interfaces in Storybook.

### Additional context

_No response_
Repository: vscode
Issue: Diff Editor, Unchanged Code Widget: Consider not setting background to grey
Labels: polish,diff-editor

This could make it easier to understand how the splitter works.
Repository: PowerToys
Issue: Enable/Disable animations
Labels: Needs-Triage,Needs-Team-Response

### Description of the new feature / enhancement

A way to choose which animations to enable or disable.
Standard you can choose to turn everything on or off, but it would be nice to be able to choose what to turn on.

### Scenario when this would be used?

Showing a hidden taskbar uses an animation that isn't too jarring or slow. In the same vein, showing the start menu isn't annoying. But switching virtual desktops (ctrl + windows key + arrows) takes a while and the animation isn't smooth.

Being able to choose what animations can be turned on or off would make the user experience a lot nicer.

### Supporting information

_No response_
Repository: ollama
Issue: Support AMD GPUs on Intel Macs
Labels: feature request,amd,macos

I'm currently trying out the ollama app on my iMac (i7/Vega64) and I can't seem to get it to use my GPU.

I have tried running it with num_gpu 1 but that generated the warnings below.

`
2023/11/06 16:06:33 llama.go:384: starting llama runner
2023/11/06 16:06:33 llama.go:386: error starting the external llama runner: fork/exec /var/folders/2z/r_0t221x2blbq02n5dp2m5fr0000gn/T/ollama1975281143/llama.cpp/gguf/build/metal/bin/ollama-runner: bad CPU type in executable
2023/11/06 16:06:33 llama.go:384: starting llama runner
2023/11/06 16:06:33 llama.go:442: waiting for llama runner to start responding
{"timestamp":1699283193,"level":"WARNING","function":"server_params_parse","line":873,"message":"Not compiled with GPU offload support, --n-gpu-layers option will be ignored. See main README.md for information on enabling GPU BLAS support","n_gpu_layers":-1}
{"timestamp":1699283193,"level":"INFO","function":"main","line":1324,"message":"build info","build":219,"commit":"9e70cc0"}
{"timestamp":1699283193,"level":"INFO","function":"main","line":1330,"message":"system info","n_threads":6,"n_threads_batch":-1,"total_threads":12,"system_info":"AVX = 0 | AVX2 = 0 | AVX512 = 0 | AVX512_VBMI = 0 | AVX512_VNNI = 0 | FMA = 0 | NEON = 0 | ARM_FMA = 0 | F16C = 0 | FP16_VA = 0 | WASM_SIMD = 0 | BLAS = 1 | SSE3 = 1 | SSSE3 = 1 | VSX = 0 | "}
`
Repository: transformers
Issue: audio pipeline support for initial_prompt?
Labels: Feature request

### System Info

Is there a parameter someplace for audio pipeline support for initial_prompt?

like this: https://github.com/openai/whisper/discussions/963

$ whisper --help
optional arguments:
--initial_prompt INITIAL_PROMPT
optional text to provide as a prompt for the first window. (default: None)

$ whisper-ctranslate2 --help
optional arguments:
--initial_prompt INITIAL_PROMPT
optional text to provide as a prompt for the first window. (default: None)

### Who can help?

_No response_

### Information

- [X] The official example scripts
- [ ] My own modified scripts

### Tasks

- [X] An officially supported task in the `examples` folder (such as GLUE/SQuAD, ...)
- [ ] My own task or dataset (give details below)

### Reproduction

audio pipeline-initial_paremeter

### Expected behavior

audio pipeline-initial_paremeter
Repository: godot
Issue: There's no way to preview FogVolumes without throw away WorldEnvironment nodes
Labels: discussion,topic:rendering,topic:editor,usability,topic:3d

### Godot version

4.2.b4

### System information

Win 10

### Issue description

There's no way to see a FogVolume you create without creating a WorldEnvironment to enable volumetric fog which would clash if spawned in another scene.. so I end up putting a script on them to delete them as soon as possible as they're for editor only. Ideally, there would be an option in the preview environment dialog to both enable it and change the default density (as default is too dense for editing imo).

### Steps to reproduce

Create a Node3D based scene. Add a FogVolume. Nothing is displayed on screen; at least there's a warning about it on the node (yellow triangle !).

### Minimal reproduction project

n/a
Repository: go
Issue: x/pkgsite: duplicate escaping on error page
Labels: NeedsFix,pkgsite

Via @rsc, who encountered the following broken escaping on pkgsite:
![image](https://github.com/golang/go/assets/57144380/0f3a74b9-71e4-4ba1-9e77-762691f3240a)

Repro steps:
1. Visit https://pkg.go.dev/rsc.io/tmp/nonexist
2. Click "Fetch" button.
3. Wait for the load to fail.
Repository: terminal
Issue: Mouse cannot select text with pyautogui
Labels: Issue-Bug,Area-UserInterface,Product-Terminal,Priority-3

### Windows Terminal version

1.17.11461.0

### Windows build number

10.0.19045.3570

### Other Software

python 3.10,  pyautogui 0.9.5 (The exact versions doesn't matter actually)

### Steps to reproduce

Install the pyautogui library (The version doesn't matter).
Execute the following code and you have 3 seconds to switch to the terminal and position the cursor on any text. 
```
from time import sleep

import pyautogui
from pyautogui import Point

sleep(3)
pyautogui.click()
pyautogui.mouseDown(button='left')
for i in range(50):
    position: Point = pyautogui.position()
    pyautogui.moveTo(position.x + 4, position.y)
pyautogui.mouseUp(button='left')
```

### Expected Behavior

The text where the cursor is positioned starts to be selected towards the right.
FYI : I tested that code on other terminals like classic windows terminal,  Git Bash and WSL2 and the problem doesn't occur.


### Actual Behavior

The cursor is positioned at the right place and progress to the right as expected but no selection happens.
![ezgif-1-639c7a0728](https://github.com/microsoft/terminal/assets/15986712/8cc1a893-dc52-46b8-86eb-6526e8cd7435)
Repository: neovim
Issue: Wrong cursor position when conceal char display width is larger than 1
Labels: bug-vim,has:repro,unicode  💩,conceal

### Problem

When we conceal a text with a char that has a display width larger than one (like an emoji), the cursor position is not right.

### Steps to reproduce

`nvim --clean`
`:edit test.txt`
Type: `:wrench: test`
`:lua vim.fn.matchadd("Conceal", ":wrench:", 0, 12, { conceal = "🔧" })`
`:set conceallevel=1`
`:set concealcursor=ni`
Type `$`

### Expected behavior

The cursor should be positioned at the end of the line, at the character `t`. Instead, it is positioned at the character `s`. Probably, the algorithm is assuming that the conceal char display width is always 1, which is not the case here.

### Neovim version (nvim -v)

NVIM v0.9.4

### Vim (not Nvim) behaves the same?

Yes, Vim 9.0.1544

### Operating system/version

macOS 14.0

### Terminal name/version

iTerm2

### $TERM environment variable

xterm-256color

### Installation

homebrew
Repository: next.js
Issue: [Next 14] Next.js with custom cache handler fails to serve pre-rendered pages
Labels: bug

### Link to the code that reproduces this issue

https://github.com/better-salmon/custom-cache-404-for-ssg-pages

### To Reproduce

1. Build and start the app with `npm run build && npm run start`.
2. Open http://localhost:3000/should-work in the browser.

### Current vs. Expected behavior

**Expected behavior:**

The page is loaded with content and status code 200.

**Actual behavior:**

404 page is shown.

### 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 23.1.0: Mon Oct  9 21:28:31 PDT 2023; root:xnu-10002.41.9~6/RELEASE_ARM64_T8112
Binaries:
  Node: 20.9.0
  npm: 10.1.0
  Yarn: N/A
  pnpm: 8.10.0
Relevant Packages:
  next: 14.0.2-canary.13
  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)

Not sure

### Additional context

In the examples, there is a lack of reading static HTML from the disk, and the cache is empty; the app fails to serve such pages and shows 404 page.