sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: Multiple errors on https://app-dir.vercel.app/
Labels: bug

### Verify canary release

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

### Provide environment information

```bash
I happens with my own code as well, but this is not mine
```


### 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://app-dir.vercel.app

### To Reproduce

Go to https://app-dir.vercel.app/, reload the page multiple times either in Firefox or Safari. Chrome seems fine.

### Describe the Bug

In console log I get multiple errors:

<img width="1692" alt="Screenshot 2023-06-02 at 11 13 02" src="https://github.com/vercel/next.js/assets/357974/a1cea511-a888-4622-9c5d-74a720877169">
<img width="1702" alt="Screenshot 2023-06-02 at 11 13 19" src="https://github.com/vercel/next.js/assets/357974/f66341d2-e525-405d-bead-879c4baca951">
<img width="1319" alt="Screenshot 2023-06-02 at 11 17 18" src="https://github.com/vercel/next.js/assets/357974/190bd214-75de-4970-ae23-00e96ae2890a">


### Expected Behavior

It shouldn't

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

Firefox, Safari

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

Vercel
Repository: pytorch
Issue: LibTorch-Lite 1.13.0.1 Crash on iOS 12 on app startup
Labels: triaged,module: ios

### 🐛 Describe the bug

When app start on iOS 12.5.7 (latest version for iphone 5s, 6 and some iPad), the app crash with the following logs: 

```
dyld: Symbol not found: ___chkstk_darwin
  Referenced from: /var/containers/Bundle/Application/XXXX/PlantNet.app/PlantNet
  Expected in: /usr/lib/libSystem.B.dylib
 in /var/containers/Bundle/Application/XXXX/PlantNet.app/PlantNet
(lldb) 
```

The [Podspec](https://github.com/CocoaPods/Specs/blob/master/Specs/c/c/3/LibTorch-Lite/1.13.0.1/LibTorch-Lite.podspec.json) indicate iOS 12.0 

#### Impact

All iOS Users on 12.5.7 cannot use the app as the app crash on start after the update. 
Potential workaround are time consuming involving releasing a specific version for them on the App Store before publishing a new app dropping the support for iOS 12

Stacktrace as follow: 
```
# 0 __abort_with_payload
dyld`:
    0x1087f2410 <+0>:  mov    x16, #0x209
    0x1087f2414 <+4>:  svc    #0x80
->  0x1087f2418 <+8>:  b.lo   0x1087f2430               ; <+32>
    0x1087f241c <+12>: stp    x29, x30, [sp, #-0x10]!
    0x1087f2420 <+16>: mov    x29, sp
    0x1087f2424 <+20>: bl     0x1087f1850               ; cerror_nocancel
    0x1087f2428 <+24>: mov    sp, x29
    0x1087f242c <+28>: ldp    x29, x30, [sp], #0x10
    0x1087f2430 <+32>: ret    
```

```
# 5 _dyld_start
dyld`:
    0x1087b1000 <+0>:   mov    x28, sp
    0x1087b1004 <+4>:   and    sp, x28, #0xfffffffffffffff0
    0x1087b1008 <+8>:   mov    x0, #0x0
    0x1087b100c <+12>:  mov    x1, #0x0
    0x1087b1010 <+16>:  stp    x1, x0, [sp, #-0x10]!
    0x1087b1014 <+20>:  mov    x29, sp
    0x1087b1018 <+24>:  sub    sp, sp, #0x10
    0x1087b101c <+28>:  ldr    x0, [x28]
    0x1087b1020 <+32>:  ldr    x1, [x28, #0x8]
    0x1087b1024 <+36>:  add    x2, x28, #0x10
    0x1087b1028 <+40>:  adrp   x4, -1
    0x1087b102c <+44>:  add    x4, x4, #0x0
    0x1087b1030 <+48>:  adrp   x3, 90
    0x1087b1034 <+52>:  ldr    x3, [x3, #0xad8]
    0x1087b1038 <+56>:  sub    x3, x4, x3
    0x1087b103c <+60>:  mov    x5, sp
    0x1087b1040 <+64>:  bl     0x1087b1088               ; dyldbootstrap::start(macho_header const*, int, char const**, long, macho_header const*, unsigned long*)
->  0x1087b1044 <+68>:  mov    x16, x0
    0x1087b1048 <+72>:  ldr    x1, [sp]
    0x1087b104c <+76>:  cmp    x1, #0x0
    0x1087b1050 <+80>:  b.ne   0x1087b105c               ; <+92>
    0x1087b1054 <+84>:  add    sp, x28, #0x8
    0x1087b1058 <+88>:  br     x16
    0x1087b105c <+92>:  mov    x30, x1
    0x1087b1060 <+96>:  ldr    x0, [x28, #0x8]
    0x1087b1064 <+100>: add    x1, x28, #0x10
    0x1087b1068 <+104>: add    x2, x1, x0, lsl #3
    0x1087b106c <+108>: add    x2, x2, #0x8
    0x1087b1070 <+112>: mov    x3, x2
    0x1087b1074 <+116>: ldr    x4, [x3]
    0x1087b1078 <+120>: add    x3, x3, #0x8
    0x1087b107c <+124>: cmp    x4, #0x0
    0x1087b1080 <+128>: b.ne   0x1087b1074               ; <+116>
    0x1087b1084 <+132>: br     x16

```

### Versions

LibTorch-Lite 1.13.0.1
React Native 0.70.9
Repository: tensorflow
Issue: Inconsistency-bug in `tf.raw_ops.Acos` between jit mode and normal mode
Labels: stat:awaiting tensorflower,type:bug,comp:ops,TF 2.12

<details><summary>Click to expand!</summary> 
 
 ### Issue Type

Bug

### Have you reproduced the bug with TF nightly?

Yes

### Source

source

### Tensorflow Version

2.14.0

### Custom Code

Yes

### OS Platform and Distribution

Ubuntu 20.04

### Mobile device

Ubuntu 20.04

### Python version

3.8.10

### Bazel version

_No response_

### GCC/Compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current Behaviour?

There is an inconsistency bug between **jit compile mode** and **normal mode** in `tf.raw_ops.Acos` which result in inconsistent computational result (mainly occur while dtype is complex, it seems that there are something wrong in the support of complex number).
But expectedly, the computational result have to be the same.

### Standalone code to reproduce the issue

```shell
import os 
os.environ['TF_CPP_MIN_LOG_LEVEL'] = '2'
import tensorflow as tf
import numpy as np

x = tf.cast(tf.random.uniform([2, 1, 3, 4], dtype=tf.dtypes.float32, maxval=60000), dtype=tf.complex128)

@tf.function(jit_compile=True)
def fuzz_jit():
    y = tf.raw_ops.Acos(
        x = x
    )
    return y

def fuzz_normal():
    y = tf.raw_ops.Acos(
        x = x
    )
    return y

y1 = fuzz_jit()
print('[+] JIT ok')
y2 = fuzz_normal()
print('[+] Normal ok')
np.testing.assert_allclose(y1.numpy(), y2.numpy(), rtol=1e-4, atol=1e-4)
```


### Relevant log output

```shell
% python test.py
[+] JIT ok
[+] Normal ok
Traceback (most recent call last):
  File "test.py", line 25, in <module>
    np.testing.assert_allclose(y1.numpy(), y2.numpy(), rtol=1e-4, atol=1e-4)
  File "/usr/local/lib/python3.8/dist-packages/numpy/testing/_private/utils.py", line 1530, in assert_allclose
    assert_array_compare(compare, actual, desired, err_msg=str(err_msg),
  File "/usr/local/lib/python3.8/dist-packages/numpy/testing/_private/utils.py", line 844, in assert_array_compare
    raise AssertionError(msg)
AssertionError: 
Not equal to tolerance rtol=0.0001, atol=0.0001

Mismatched elements: 24 / 24 (100%)
Max absolute difference: 23.34874158
Max relative difference: 2.00000002
 x: array([[[[4.020810e-07+11.649195j, 3.918355e-07+11.63629j ,
          6.167066e-09 +9.56048j , 2.750275e-10 +8.005427j],
         [3.286194e-07+11.548319j, 8.673153e-08+10.882277j,...
 y: array([[[[0.-11.649196j, 0.-11.63629j , 0. -9.56048j , 0. -8.005427j],
         [0.-11.548319j, 0.-10.882278j, 0.-10.521193j, 0.-10.125081j],
         [0.-10.732039j, 0. -7.92731j , 0.-11.674371j, 0.-11.332818j]]],...
```
</details>
Repository: tensorflow
Issue: Inconsistency-bug in `tf.raw_ops.AddN` between jit mode and normal mode
Labels: stat:awaiting tensorflower,type:bug,comp:ops,TF 2.13

<details><summary>Click to expand!</summary> 
 
 ### Issue Type

Bug

### Have you reproduced the bug with TF nightly?

Yes

### Source

source

### Tensorflow Version

2.14.0

### Custom Code

Yes

### OS Platform and Distribution

Ubuntu 20.04

### Mobile device

Ubuntu 20.04

### Python version

3.8.10

### Bazel version

_No response_

### GCC/Compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current Behaviour?

There is an inconsistency bug between **jit compile mode** and **normal mode** in `tf.raw_ops.AddN` which result in inconsistent computational result especially when the data type is `half`. But expectedly, the computational result have to be the same.

### Standalone code to reproduce the issue

```shell
import os 
os.environ['TF_CPP_MIN_LOG_LEVEL'] = '2'
import tensorflow as tf
import numpy as np

inputs = 44 * [tf.random.uniform([1, 2, 4, 3], dtype=tf.dtypes.half, maxval=1000)] # the half datatype!

@tf.function(jit_compile=True)
def fuzz_jit():
    y = tf.raw_ops.AddN(
        inputs = inputs
    )
    return y

def fuzz_normal():
    y = tf.raw_ops.AddN(
        inputs = inputs
    )
    return y

y1 = fuzz_jit()
print('[+] JIT ok')
y2 = fuzz_normal()
print('[+] Normal ok')
np.testing.assert_allclose(y1.numpy(), y2.numpy(), rtol=1e-4, atol=1e-4)
```


### Relevant log output

```shell
% python test.py
[+] JIT ok
[+] Normal ok
Traceback (most recent call last):
  File "test.py", line 25, in <module>
    np.testing.assert_allclose(y1.numpy(), y2.numpy(), rtol=1e-4, atol=1e-4)
  File "/usr/local/lib/python3.8/dist-packages/numpy/testing/_private/utils.py", line 1530, in assert_allclose
    assert_array_compare(compare, actual, desired, err_msg=str(err_msg),
  File "/usr/local/lib/python3.8/dist-packages/numpy/testing/_private/utils.py", line 844, in assert_array_compare
    raise AssertionError(msg)
AssertionError: 
Not equal to tolerance rtol=0.0001, atol=0.0001

Mismatched elements: 20 / 24 (83.3%)
Max absolute difference: 160.
Max relative difference: 0.004887
 x: array([[[[14864., 41344., 39872.],
         [ 2492.,  6852., 17664.],
         [17344., 33216., 39968.],...
 y: array([[[[14912., 41376., 39808.],
         [ 2488.,  6824., 17696.],
         [17408., 33280., 40096.],...
```
</details>
Repository: material-ui
Issue: Grid2 nested Grids - missing variables
Labels: component: Grid

I use nested Grid2 grids in my component.
The nested grids get variables for each level with the number of level. Instead of just using the values of the parent grid, it mirrors the values in new variables.
In my case, this results in the following variable being used but never being assigned.
`var(--Grid-columnsLevel2)`
<img width="281" alt="image" src="https://github.com/mui/material-ui/assets/121259031/3098806f-86ba-4c15-9727-b12d4121e6c1">

This is another grid inside another grid as an example. In the width property, the variable --Grid-columnsLevel1 is used but never assigned:
`<Grid2 container justifyContent="space-between" alignItems="center">
<DatePicker sx={{width: "70%"}} label="Versandtag" value={props.datum} onChange={props.onChange} disablePast={true}/>
<FormGroup>
<FormControlLabel control={<Switch checked={props.lieferterminFix} onChange={(event) => props.onChangeLieferterminFix(event.target.checked)}/>} label="Fix"/>
</FormGroup>
</Grid2>`

I do not know when this error occurred, because at the beginning it all worked fine. Switch back to previous commits does not help, so i do not think it's an error in my code.

Any suggestions?

Version: 5.13.3
Repository: next.js
Issue: Cannot generate static assets with non-latin names
Labels: bug

### Verify canary release

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

### Provide environment information

```bash
> next info


    Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Pro   
    Binaries:
      Node: 18.12.1
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 12.3.4
      eslint-config-next: 11.1.4
      react: 17.0.2
      react-dom: 17.0.2
```


### 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

npm run build

### To Reproduce

If you have page urls with non-latin characters (arabic, russian, hindi, korean, etc.), nextjs fails the build because it cannot save these files in .next folder.

### Describe the Bug

We have pages with non-latin characters in URL. For example:
/home/حقائق-سريعة-قضايا-صحَّة-المرأة/مُضَاعَفاتُ-المَخاضِ-والوِلادة/الولادة-القيصريَّة-c-section

When we build the app, nextjs got correct static paths, got correct data from the server to render page, but when it saves html/json file it escapes non-latin characters and hit the file system name length limit.

`Error occurred prerendering page "/ar/home/%D8%AD%D9%82%D8%A7%D8%A6%D9%82-%D8%B3%D8%B1%D9%8A%D8%B9%D8%A9-%D9%82%D8%B6%D8%A7%D9%8A%D8%A7-%D8%B5%D8%AD%D9%91%D9%8E%D8%A9-%D8%A7%D9%84%D9%85%D8%B1%D8%A3%D8%A9/%D8%A7%D9%84%D8%B9%D9%8E%D8%AF%D9%88%D9%89-%D8%A7%D9%84%D9%85%D9%87%D8%A8%D9%84%D9%8A%D9%91%D9%8E%D8%A9-%D9%88%D8%A7%D9%84%D8%AF%D9%91%D9%8E%D8%A7%D8%A1-%D8%A7%D9%84%D8%A7%D9%84%D8%AA%D9%90%D9%87%D8%A7%D8%A8%D9%8A%D9%91-%D8%A7%D9%84%D8%AD%D9%88%D8%B6%D9%8A%D9%91/%D8%A7%D9%84%D8%AA%D9%87%D8%A7%D8%A8-%D8%A7%D9%84%D9%81%D8%B1%D8%AC". Read more: https://nextjs.org/docs/messages/prerender-error Error: ENAMETOOLONG: name too long, mkdir`

### Expected Behavior

We expect nextjs save html/json with the same name as in url without escaping.
For example:

static path url: /حقائق-سريعة-قضايا-صحَّة-المرأة/مُضَاعَفاتُ-المَخاضِ-والوِلادة/الولادة-القيصريَّة
static file/folder name should follow the same naming without escaping it.

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

_No response_

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

_No response_
Repository: next.js
Issue: Clicking `Link` to external URLs will cause browser to load infinitely
Labels: Navigation

### 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 22.2.0: Sun Oct 16 18:11:16 PDT 2022; root:xnu-8792.60.32.0.1~11/RELEASE_ARM64_T8103
    Binaries:
      Node: 16.17.0
      npm: 8.15.0
      Yarn: 1.22.10
      pnpm: 8.6.0
    Relevant packages:
      next: 13.4.4
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.3
```


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

App directory (appDir: true), Routing (next/router, next/navigation, next/link)

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

https://github.com/unixzii/nextjs-mpa-infinite-loads-issue

### To Reproduce

1. Serve the project, and open the index page with Network Inspector.
2. Click "External Link" and see whether the URL can be loaded normally.
3. Then click "Start Spinning" button to schedule a periodic update, and click "External Link" again to reproduce the issue.

### Describe the Bug

When an external link is clicked while there are frequent updates happen in any component, the browser keep reloading the target URL (cancelling the previous one and initiate another one).

### Expected Behavior

The target link can be navigated normally.

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

Chrome 113.0.5672.126

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

_No response_
Repository: nvm
Issue: nvm errors out with exit status 3 in aws code build
Labels: needs followup

Error message -
[Container] 2023/06/02 12:24:31 Command did not exit successfully . "$NVM_DIR/nvm.sh" && nvm use 14.17.0 exit status 3

We have aws pipeline with nodejs runtime in it.
We have done below -
1. Installed nvm and all required node version within pipeline and copied the same in S3 bucket (reason for copy as we are getting 5xx error from nvm, caching mechanism to not install again for every build in cicd pipeline). Script below -
```
version: 0.2
env:
  shell: bash
phases:
  install:
    runtime-versions:
      nodejs: 14
    commands:
      - /usr/local/bin/aws --version
  pre_build:
    commands:
      - bash ./sh-files/retry.sh 3 "curl -o install.sh --write-out "%{http_code}" https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh"
      - export NVM_DIR="$HOME/.nvm"
      - '[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"'
      - '[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"'
      - . "$NVM_DIR/nvm.sh" && bash ./sh-files/retry.sh 3 "nvm install 12.22.2"
      - . "$NVM_DIR/nvm.sh" && bash ./sh-files/retry.sh 3 "nvm install 14.17.0"
      - . "$NVM_DIR/nvm.sh" && bash ./sh-files/retry.sh 3 "nvm install 10"
      - . "$NVM_DIR/nvm.sh" && bash ./sh-files/retry.sh 3 "nvm install 14.17.6"
      - aws s3 cp $HOME/.nvm s3://<bucket_name>/cicd-pipeline-nb/dependencies/.nvm --region us-west-2 --recursive
      - echo successfully copied dependencies code
```
It works fine in aws code build. But when runs other script to copy the S3 .nvm folder in aws code build(other pipeline) instance causes exist 3 issue. Refer script below -
```
  version: 0.2
  env:
    shell: bash
  phases:
    install:
      on-failure: ABORT
      runtime-versions:
        nodejs: 12
      commands:
        - aws s3 cp s3://<bucket_name>/cicd-pipeline-nb/customer-customization/ . --region us-west-2 --recursive
        - aws s3 cp s3://<bucket_name>/cicd-pipeline-nb/dependencies/.nvm $HOME/.nvm --region us-west-2 --recursive
        - echo ENABLE_SCANS Value $ENABLE_SCANS
        - export NVM_DIR="$HOME/.nvm"
        - '[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"'
        - '[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"'
        - . "$NVM_DIR/nvm.sh" && nvm use 14.17.0
        - export NODE_OPTIONS="--max-old-space-size=8192"
        - node --version
        - echo Installing yarn...
```
Repository: pytorch
Issue: Dynamo should only unroll loops by a preset factor (unless otherwise explicitly instructed)
Labels: triaged,oncall: pt2,module: dynamo,module: startup-tracing-compile

### 🐛 Describe the bug

Today, dynamo is willing to unroll loops for arbitrarily long. This can lead to extremely large graphs which in turn lead to slow compile times, for example, https://github.com/pytorch/pytorch/issues/102622

Instead, we should unroll only by a pre-set factor, e.g., 5 or something. If we notice that we have looped too many times (and the loop is generating graph), we should graph break, forcing us to generate separate code for the loop body. (In the further future, we could automatically host side loop'ify the graph, so we could avoid having to do guard tests on entry.) 

### Versions

main

cc @msaroufim @bdhirsh @anijain2305 @zou3519 @chauhang @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @wconstab
Repository: kubernetes
Issue: Support a list of AppProtocols
Labels: sig/network,kind/feature,triage/accepted

The Kubernetes Service API allow us to specify an Application Protocol for each Service port. This is used as a hint for implementations to offer richer behavior for protocols that they understand.

According to the [docs](https://kubernetes.io/docs/concepts/services-networking/service/#application-protocol) one of the valid values can be `Implementation-defined prefixed names such as mycompany.com/my-custom-protocol`.

There are cases where different implementations installed in the same cluster and different behaviors may be needed for the same ports.

Starting a discussion to gather thoughts, ideas and use-cases about the need for multiple appProtocols support for the same port.
Repository: storybook
Issue: [Bug]: Making stories non-inline (iframe) in docs will autoplay them when they shouldn't
Labels: bug,addon: docs

### Describe the bug

When setting a story to display in iframe (_not_ inline), the play function will fire when defined.

### To Reproduce

https://stackblitz.com/edit/github-wssgsy?file=src%2Fstories%2FPage.stories.js

Going to the Page docs page, the Logged In story play function plays

### System

_No response_

### Additional context

_No response_
Repository: node
Issue: test-child-process-pipe-dataflow failing on Windows
Labels: windows,flaky-test


```
not ok 106 parallel/test-child-process-pipe-dataflow
  ---
  duration_ms: 221.12800
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:125
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
    + actual - expected
    
    + '130086'
    - '1048577'
        at process.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-child-process-pipe-dataflow.js:71:12)
        at process.emit (node:events:523:35) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: '130086',
      expected: '1048577',
      operator: 'strictEqual'
    }
    
    Node.js v21.0.0-pre
  ...
```

It's also failing on `v16.x-staging`, so I don't think it's related to a recent change on `main`, maybe a change with the infra?
Repository: next.js
Issue: [NEXT-1251] App Router `page.tsx`'s `searchParams` is incorrectly including path `params` when using Edge runtime
Labels: Runtime

### 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 22.5.0: Mon Apr 24 20:52:24 PDT 2023; root:xnu-8796.121.2~5/RELEASE_ARM64_T6000
Binaries:
  Node: 18.12.1
  npm: 8.19.2
  Yarn: 1.22.19
  pnpm: 7.32.2
Relevant packages:
  next: 13.4.5-canary.3
  eslint-config-next: 13.4.4
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
```


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

App directory (appDir: true), Middleware / Edge (API routes, runtime)

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

https://github.com/manovotny/search-params-minimal-repro

### To Reproduce

1. Create an App Router route that has a dynamic path segment and uses the `edge` runtime.
2. In a browser, navigate to that url and add some query parameters.
3. `console.log` both `params` and `searchParams` that get passed to the page as props.
4. See that `searchParams` incorrectly includes the path `params` in the `searchParams`.

### Describe the Bug

Path `params` are incorrectly being included in the `searchParams`.

> Note: this is an Edge runtime issue only. This does not reproduce on `nodejs` runtime.

### Expected Behavior

Path `params` should not be included in the `searchParams`.

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

Google Chrome Version 114.0.5735.90 (Official Build) (arm64)

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

Vercel

<sub>[NEXT-1251](https://linear.app/vercel/issue/NEXT-1251/app-router-pagetsxs-searchparams-is-incorrectly-including-path-params)</sub>
Repository: vscode
Issue: API to access the product configuration
Labels: feature-request,remote-tunnel

We should add API to access the product configuration. In the Web there's currently now way to do that, and on the desktop, extension make assumption about the file layout of the VS Code install.

Properties of interest for WSL:
`commit`, `quality`, `serverDataFolderName`, `serverApplicationName`, `updateURL`.