sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: Vercel Edge function sometimes cannot get chunks
Labels: bug,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: x64
      Version: Darwin Kernel Version 22.3.0: Mon Jan 30 20:42:11 PST 2023; root:xnu-8792.81.3~2/RELEASE_X86_64
    Binaries:
      Node: 16.13.1
      npm: 8.1.2
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.4.2
      eslint-config-next: 13.4.2
      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)

Middleware / Edge (API routes, runtime)

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/Rigtch/rigtch-music-www

### To Reproduce

Fetch [repository](https://github.com/Rigtch/rigtch-music-www). Configure deployment on vercel. Go on production deployment. Or just go to https://rigtch-music.vercel.app and check console for errors.

### Describe the Bug

Sometimes nextjs edge function throws this errors.
<img width="1125" alt="Screenshot 2023-06-04 at 14 55 39" src="https://github.com/vercel/next.js/assets/56691628/7c529c59-0a1f-4ba1-9278-f080a57cc15b">

This usually happens on mobile, but sometimes also on desktop. This is really weird, because sometimes I get proper response(but page is loading suspiciously long even if everything on page is rendered).

### Expected Behavior

Page should load content without any error with loading chunks, manifests etc.

### Which browser are you using? (if relevant)

Version 1.52.117 Chromium: 114.0.5735.90 (Official Build) (x86_64)

### How are you deploying your application? (if relevant)

Vercel
Repository: puppeteer
Issue: [Feature]: Browser stack local file upload
Labels: feature

### Feature description

Hi,

I am using browser stack local to run my puppeteer scripts. I have browserstack.local set to true in my capabilities list and I have a secure tunnel created between browser stack and my local system. But I am not able to upload a file that is in my project repository. Browser stack is not reading this file. Please help me to solve this issue. How can I upload a file present on my system in my script?
Repository: next.js
Issue: CSS module styling is removed too early on route changes with app directory
Labels: CSS

### 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.16.0
      npm: 9.5.1
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.4.5-canary.4
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 4.9.5
```


### 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

NA

### To Reproduce

NA

### Describe the Bug

I have a next js project with CSS module stylings built entirely from scratch which I import in the different components. However when I try to change the current route by performing a router.push(), the css styling for the current page (not the new one) is removed too early, thus resulting in a flash of unstyled content. Since I am not using any external provider for stylings but just bare css this cannot be caused by any third parties.

Please note I am currently noticing this bug in development and that this error only takes place when I try to simulate slower network environments and not while working normally. Below you'll find an image example of what I am experiencing.

If you have any suggestions, please let me know.
Thanks,
Riccardo

<img width="1728" alt="Screenshot 2023-06-04 at 16 07 50" src="https://github.com/vercel/next.js/assets/29000662/f4897025-92e8-47af-ae43-4faadbc069e9">

### Expected Behavior

The CSS should be unmounted at the right time with no flashes of unstyled content.

### Which browser are you using? (if relevant)

Chrome (latest version)

### How are you deploying your application? (if relevant)

NA
Repository: stable-diffusion-webui
Issue: [Bug]: using parameters --nowebui --api 
Labels: bug-report

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What happened?

When using parameters `--nowebui --api` ， Unable to use **LoRA**, it prompts Skipping unknown extra network: lora, and the **/sdapi/v1/scripts** api service returns empty after starting 
```
{
    "txt2img": [],
     "img2img": []
}
```
, but the result can be returned normally after calling the image generation once, and there will be no such situation without the `--nowebui `parameter

### Steps to reproduce the problem

1. Go to .... 
2. Press ....
3. ...


### What should have happened?

1. when using `--nowebui `  LoRa is available
2. The **/sdapi/v1/scripts** api is available when the project is just started

### Commit where the problem happens

b6af0a3809ea869fb180633f9affcae4b199ffcf

### What Python version are you running on ?

Python 3.10.x

### What platforms do you use to access the UI ?

Windows

### What device are you running WebUI on?

Nvidia GPUs (RTX 20 above)

### What browsers do you use to access the UI ?

Google Chrome

### Command Line Arguments

```Shell
--medvram --theme light --xformers --api --autolaunch --nowebui
```


### List of extensions

used [a1111-sd-webui-locon](https://github.com/KohakuBlueleaf/a1111-sd-webui-locon)

### Console logs

```Shell
Skipping unknown extra network: lora
```


### Additional information

_No response_
Repository: pytorch
Issue: torch.cuda.is_available() returns False on GTX 1650 with cuda 11.7 and torch==2.0.0+cpu
Labels: module: build,triaged

### 🐛 Describe the bug

i get False when i run torch.cuda.is_available() 

nvidia-smi
**+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 535.98                 Driver Version: 535.98       CUDA Version: 12.2     |
|-----------------------------------------+----------------------+----------------------+
| GPU  Name                     TCC/WDDM  | Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |         Memory-Usage | GPU-Util  Compute M. |
|                                         |                      |               MIG M. |
|=========================================+======================+======================|
|   0  NVIDIA GeForce GTX 1650      WDDM  | 00000000:01:00.0  On |                  N/A |
| 30%   39C    P0              15W /  75W |   1145MiB /  4096MiB |      1%      Default |
|                                         |                      |                  N/A |
+-----------------------------------------+----------------------+----------------------+**

i even installed 11.7 and it still shows 12.2




when i run pip show torch it gives me version 2.0.1 + cu117 which is why i installed cuda 11.7 but i previously had 12.2
**C:\Users\ambsu>pip show torch
Name: torch
Version: 2.0.1+cu117**


py -m torch.utils.collect_env
gives 
**Versions of relevant libraries:
[pip3] numpy==1.24.3
[pip3] torch==2.0.0+cpu
[pip3] torchaudio==2.0.2+cu118
[pip3] torchvision==0.15.2
[conda] Could not collect**


everything is showing different versions









### Error logs

**Versions of relevant libraries:
[pip3] numpy==1.24.3
[pip3] torch==2.0.0+cpu
[pip3] torchaudio==2.0.2+cu118
[pip3] torchvision==0.15.2
[conda] Could not collect**

nvidia-smi
**+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 535.98                 Driver Version: 535.98       CUDA Version: 12.2     |
|-----------------------------------------+----------------------+----------------------+
| GPU  Name                     TCC/WDDM  | Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |         Memory-Usage | GPU-Util  Compute M. |
|                                         |                      |               MIG M. |
|=========================================+======================+======================|
|   0  NVIDIA GeForce GTX 1650      WDDM  | 00000000:01:00.0  On |                  N/A |
| 30%   39C    P0              15W /  75W |   1145MiB /  4096MiB |      1%      Default |
|                                         |                      |                  N/A |
+-----------------------------------------+----------------------+----------------------+**

### Minified repro

import torch

print(torch.cuda.is_available()) # False

### Versions

cuda 11.7 gtx
torch 2.0.1 and 2.0.0

cc @malfet @seemethere @ezyang @msaroufim @wconstab @bdhirsh @anijain2305
Repository: next.js
Issue: Docs: ability to make parallel route to be bound to url segment
Labels: Parallel & Intercepting Routes

### What is the improvement or update you wish to see?

Currently I see this in the docs:

> Slots are not route segments and do not affect the URL structure. The file path /@team/members would be accessible at /members.

However I guess it is a valid use case and pattern in plain react, when you have nested route which renders on the same page. You just use `<Outlet />` (for react router) as many times as needed, to render child route on the same page in response to url change.

Simplified example:
`products` - shows list of products
`products/:productId` - shows product information and stays on the same page, meaning both products list and product info are shown.

Is this possible? It would be nice to have it explicitly stated and if it's possible, have an example.

I know that there is a route intercept + parallel routes, but it's not something which is needed fro this use case.



### Is there any context that might help us understand?

Let's say there is a page called products. When user goes to this page, it shows a list of products.
The structure would be smth like

app/
-- products/
---- page.tsx
In UI it will look like this
![image](https://github.com/vercel/next.js/assets/34350867/d105130b-91c3-46a7-95bc-09f82b43210c)

Then, when user clicks on a specific product it should show that product details on the same page on the right side and url should change to products/:id
In UI it will look like this:
![image](https://github.com/vercel/next.js/assets/34350867/4850560b-8707-4fa9-8a63-a19e9a65d10a)

In react world you would just have one top lvl <Outlet /> to render /products and then you'd have a nested route and nested <Outlet /> to render product information. Like this:

```
const routes = [
  {
    path: '/products'
    element: <ProductsList />
    children: [
      {
        path: '/:id',
        element: <ProductDetails />
      }
    ]
  }
]

// ProductsList component

return (
  ... showing products list
  <Outlet /> <--- to show product details on the same page
)
```

Is it possible to do it in next.js world? If I created another page like

app/
-- products/
---- page.tsx
---- [id]
------ page.tsx
It will be a completely separate page.

If next.js provides smth similar, would be good to have it in the docs. If not, still would be nice too see alternatives.
Currently I could achieve smth close by using query param, parallel routes and then checking route query param and showing one of two parallel routes

### Does the docs page already exist? Please link to it.

https://nextjs.org/docs/app/building-your-application/routing/intercepting-routes

<sub>[DX-1697](https://linear.app/vercel/issue/DX-1697/docs-ability-to-make-parallel-route-to-be-bound-to-url-segment)</sub>
Repository: godot
Issue: set_name() invalidates the multilayer property previously set by the node
Labels: bug,topic:multiplayer

### Godot version

4.1.dev

### System information

Window 10

### Issue description

set_name() invalidates the multilayer property previously set by the node

### Steps to reproduce

N/A

### Minimal reproduction project

#
Repository: stable-diffusion-webui
Issue: [Bug]: Gradio, generate button in img2img tab not responding
Labels: bug-report

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What happened?

Using WebUI in kaggle.

Go to i2i, upload a picture, set up the parameters and click "generate". The UI will show "Waiting" but in the terminal nothing will show up. After a while (10~30s) the generate button will be back but won't responds to clicks anymore. Even worse, the interface will become unaccessable after these steps. Restarting the UI multiple times seems to have a chance to fix this problem for one or two i2i generations.

### Steps to reproduce the problem

1. Start an instance in kaggle gradio environment.
2. Do the steps metioned above.

### What should have happened?

Just like running in the local environment.

### Commit where the problem happens

b6af0a3

### What Python version are you running on ?

Python 3.10.x

### What platforms do you use to access the UI ?

Linux

### What device are you running WebUI on?

Nvidia GPUs (RTX 20 above)

### What browsers do you use to access the UI ?

Google Chrome

### Command Line Arguments

```Shell
--share --disable-safe-unpickle --no-half-vae --xformers --enable-insecure-extension-access
```


### List of extensions

ultimate-upscale-for-automatic1111
sd-webui-controlnet


### Console logs

```Shell
/kaggle/working/content/stable-diffusion-webui
Python 3.10.10 | packaged by conda-forge | (main, Mar 24 2023, 20:08:06) [GCC 11.3.0]
Version: v1.3.1
Commit hash: b6af0a3809ea869fb180633f9affcae4b199ffcf
Installing requirements


Installing sd-webui-infinite-image-browsing requirement: python-dotenv
Installing sd-webui-infinite-image-browsing requirement: Pillow

Launching Web UI with arguments: --share --disable-safe-unpickle --no-half-vae --xformers --enable-insecure-extension-access
2023-06-04 18:34:14,814 - ControlNet - INFO - ControlNet v1.1.215
2023-06-04 18:34:15,072 - ControlNet - INFO - ControlNet v1.1.215
Loading weights [xxx] from /kaggle/working/content/stable-diffusion-webui/models/Stable-diffusion/xxx.safetensors
Creating model from config: /kaggle/working/content/stable-diffusion-webui/configs/v1-inference.yaml
LatentDiffusion: Running in eps-prediction mode
DiffusionWrapper has 859.52 M params.
Running on local URL:  http://127.0.0.1:7860
Running on public URL: https://xxxxx.gradio.live

This share link expires in 72 hours. For free permanent hosting and GPU upgrades (NEW!), check out Spaces: https://huggingface.co/spaces
Startup time: 19.4s (import torch: 6.3s, import gradio: 1.3s, import ldm: 1.3s, other imports: 0.8s, setup codeformer: 0.1s, load scripts: 3.9s, create ui: 1.3s, gradio launch: 4.2s).
Applying optimization: xformers... done.
Model loaded in 10.4s (load weights from disk: 1.6s, create model: 1.1s, apply weights to model: 3.0s, apply half(): 1.3s, load VAE: 2.7s, move model to device: 0.6s).
```


### Additional information

_No response_
Repository: rust
Issue: Suggest code correction for E0446 - private type in public interface
Labels: A-diagnostics,A-visibility,T-compiler,A-suggestion-diagnostics

### Code

```Rust
struct MyStruct;
pub fn my_test(_v: &MyStruct) {}
fn main() {}
```


### Current output

```Shell
error[E0446]: private type `MyStruct` in public interface
 --> src/bin/main.rs:2:1
  |
1 | struct MyStruct;
  | --------------- `MyStruct` declared as private
2 | pub fn my_test(_v: &MyStruct) {}
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ can't leak private type
```


### Desired output

```Shell
error[E0446]: private type `MyStruct` in public interface
 --> src/bin/main.rs:2:1
  |
1 | struct MyStruct;
  | --------------- `MyStruct` declared as private
2 | pub fn my_test(_v: &MyStruct) {}
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ can't leak private type

Help:
* Either remove the `pub` in `pub fn my_test`
* Or add `pub` to `struct MyStruct;`
```


### Rationale and extra context

Novice developers might be confused by the current wording of "leaking private type", and this seems like an easy help message fix.

### Other cases

_No response_

### Anything else?

_No response_

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"aryan-debug"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: flutter
Issue: Keyboard flickering while moving cursor pointer in Split screen mode
Labels: a: text input,platform-android,framework,engine,has reproducible steps,P2,found in release: 3.10,found in release: 3.11,team-android,triaged-android


#91605

Keyboard flicker occurs while moving the text field pointer when 2 applications are open at the same time.





https://github.com/flutter/flutter/assets/102767277/e6d08ae3-ade9-4a01-9814-16a4681fff5d
Repository: TypeScript
Issue: OOME/Excessively deep type on upgrade from 4.9.4 to 5.x, introduced in 5.0.0-dev.20230203
Labels: Needs Investigation

# Bug Report

### 🔎 Search Terms

tsc 5.x Out of Memory Heap

### 🕗 Version & Regression Information

- This is a crash
- This changed between versions 5.0.0-dev.20230202 and 5.0.0-dev.20230203

### ⏯ Playground Link

Unavailable, as I'm trying to compile an internal codebase, but I can provide access to our github repo if possible.

### 💻 Code

The "Type is excessively deep" is being triggered in code that calls this function:

```
export type LoadedCollaboration = Loaded<Collaboration, "parent">;
export async function getCollaborationMetadata(c: LoadedCollaboration): Promise<CollaborationMetadata> {
  ...
}
```

Where `Loaded` is a mapped type (which is available in our open source project):

https://github.com/stephenh/joist-ts/blob/main/packages/orm/src/loadHints.ts#L168

And the `Collaboration` `"parent"` key (from our internal project) is a union type with ~20 different types in it:

```
export type CollaborationParent =
  | ScheduleSubPhase
  | Approval
  ...15 others...
  | ToDo
  | SchedulePhase;
```

### 🙁 Actual behavior

In TS 4.9.4, our codebase compiled fine, in about 50 seconds.

I tried upgrading to TS 5.1.3, and the compile now OOMEs, and if given enough RAM, eventually after ~10-15 minutes, fails with a "Type instantiation is excessively deep and possibly infinite" error.

By using the 5.0.0 nightlies published to npm, I was able to bisect that version 5.0.0-dev.20230203 is what introducing the issue, and caused our compile times to jump from ~50 seconds -> 10+ minutes & fail with the type error.

### 🙂 Expected behavior
Repository: pytorch
Issue: Support for efficiently processing categorical distributions with varying dimensions
Labels: module: distributions,feature,triaged,needs research

### 🚀 The feature, motivation and pitch

Say I have a list of probability distribution tensors of varying size. It would be nice if `Categorical` could accept a flattened tensor `probs_flat` containing all the distributions, along with a pointer `ptr` that indicates the starting index of each distribution. Standard functions can efficiently be computed, e.g. entropy can be computed as `-segment(probs_flat.log() * probs_flat, ptr)`, where `segment` is something like `segment_add_csr` from `torch_scatter` (I'm not sure if torch provides this function out of the box).

I'm not too sure of the best way to integrate this with the existing code. Just an idea!

### Alternatives

Let `probs_list` be a list of probability distribution tensors, and `xs` be a list of samples from their respective distributions. There are currently two options to e.g. evaluate the log-probabilities of the samples:
1. (evaluate for each)
```Python
log_probs = torch.stack([
    Categorical(probs=probs).log_prob(x)
    for probs, x in zip(probs_list, xs)
])
```
2. (pad, stack, evaluate)
```Python
max_size = max(probs.numel() for probs in probs_list)
probs_padded_list = []
for probs in probs_list:
    probs_padded = probs.new_zeros(max_size)
    probs_padded[:probs.numel()] = probs
    probs_padded_list += [probs_padded]
pi = Categorical(torch.stack(probs_padded_list))
log_probs = pi.log_prob(torch.stack(xs))
```

### Additional context

This can be useful in RL, where the number of possible actions varies between environment steps, as a less wasteful alternative to action masking.

cc @fritzo @neerajprad @alicanb @nikitaved
Repository: vscode
Issue: Allow separate `when` clauses for each command in a keybinding with multiple commands
Labels: feature-request,runCommands

<!-- ⚠️⚠️ 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. -->

Currently, it seems that 'when' clauses in keybindings are associated with an entire keybinding rather than the individual commands within it. I suggest associating `when` clauses with commands so that it would be possible in a keybinding with multiple commands to have separate `when` clauses for each, and whether each command is run in a particular instance depends on whether its respective `when` clause is fulfilled.

So a keybinding would look something like:

```
{
    "key": "key",
    "command": "runCommands",
    "args": {
        "commands": [
            {
                "command": "command1",
                "args": {
                    "arg1": "value1",
                    "arg2": "value2"
                },
                "when": "condition1"
            },
            {
                "command": "command2",
                "when": "condition2"
            },
            {
                "command": "command3",
                "when": "condition3",
            },
        ]
    }
}
```

so upon pressing `key`, if only `condition2` is fulfilled and not `condition1` and `condition3`, then only `command2` gets run, and if `condition1` and `condition2` are both fulfilled and not `condition3`, then `command1` gets run, and then `command2` gets run (i.e. sequentially as usual), etc.
Repository: rust
Issue: field is never read warning doesn't consider Drop implementation
Labels: A-diagnostics,T-compiler,C-feature-request

### Code

```Rust
struct PrintOnDrop(&'static str);
impl Drop for PrintOnDrop {
    fn drop(&mut self) {
        println!("{}", self.0);
    }
}

pub struct A {
    act_on_drop: PrintOnDrop,
}

impl A {
    pub fn new(msg: &'static str) -> A {
        A {
            act_on_drop: PrintOnDrop(msg),
        }
    }
}
```


### Current output

```Shell
warning: field `act_on_drop` is never read
 --> <source>:9:5
  |
8 | pub struct A {
  |            - field in this struct
9 |     act_on_drop: PrintOnDrop,
  |     ^^^^^^^^^^^
  |
  = note: `#[warn(dead_code)]` on by default

warning: 1 warning emitted

Compiler returned: 0
```


### Desired output

```Shell
Nothing.
```


### Rationale and extra context

Since the struct `A` is public and constructible, the compiler should assume that the drop for all its `Drop` fields will be called, which in this case makes the issued warning wrong.

### Other cases

_No response_

### Anything else?

Tested on 1.70.0 and on today's nightly (398fa2187 2023-06-03).