sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: [Impeller] Audit instances where sizes of intermediate render targets can get bigger than the max supported texture size.
Labels: engine,P2,e: impeller,team-engine,triaged-engine

This happens relatively infrequently but there is no way of reliably testing we don't run into such situations and cause the allocator to bail.
Repository: flutter
Issue: Improve docs for debugDoingThisLayoutWithCallback
Labels: framework,d: api docs,P2,team-framework,triaged-framework

Came up in #128910 

This part of the API was added in https://github.com/flutter/flutter/pull/74402 and could use more context as to what it means. The PR that added it stated `the EditableTextState will access RenderBox.size during rebuilding` but it is not clear whether it strictly means rebuild is happening.

From @matthew-carroll https://github.com/flutter/flutter/pull/128910#discussion_r1230250627

> invokeLayoutCallback is quite a bit more diverse than just the concept of "rebuild", I believe.

> invokeLayoutCallback may run by a RenderObject any number of times within that RenderObject's layout() behavior. Inside of that callback, you're permitted to mutate the element and render tree during layout, which is otherwise prohibited.

> The double and triple negatives are throwing me, so I still can't tell the intention. It looks like if we're in a layout callback, we don't bother checking any conditions? We let the size access go through no matter what? This is the kind of stuff I was trying to improve. The intention of these conditions is really hard to figure out.
Repository: terminal
Issue: Updating GPU drivers closed all terminals
Labels: Area-Rendering,Issue-Bug,Severity-Crash,Product-Terminal

### Windows Terminal version

 1.18.1462.0

### Windows build number

Version 10.0.19045.2965

### Other Software

_No response_

### Steps to reproduce

Open a terminal and have some work in progress.
Install new nvidia drivers.

### Expected Behavior

Terminal windows don't close when updating GPU drivers.

### Actual Behavior

 During the GPU driver reset as part of the upgrade (when screen blanks), all terminal windows close and you lose all of your work.
Repository: react-native
Issue: onTextLayOut is not getting triggered
Labels: Issue: Author Provided Repro

### Description

For a text component <Text>, if we specify onTextLayout and write log statement, its not getting triggered.

i wanted to use the onTextLayout to get the no of lines being rendered for a given text width. The no of lines might change based on the width prop in style. 

Therefor, i would like to get the no of lines to do some operation on text when it exceeds max lines limit.




### React Native Version

0.70.2

### Output of `npx react-native info`

N/A

### Steps to reproduce

Write a text component and define "onTextLayout" prop to send in the handler.

The handler doesn't get triggered even during the first layout render.

### Snack, code example, screenshot, or link to a repository

https://snack.expo.dev/Wff9zMnHx
Repository: rust
Issue: Matching on Pythonic boolean symbols (`True`, `False`) should result in better diags
Labels: A-diagnostics,T-compiler

### Code

```Rust
fn main() {
    match false {
        True => println!("I am true!"),
        False => println!("I am false!"),
    }
}
```


### Current output

```Shell
Compiling playground v0.0.1 (/playground)
warning: unreachable pattern
 --> src/main.rs:4:9
  |
3 |         True => println!("I am true!"),
  |         ---- matches any value
4 |         False => println!("I am false!"),
  |         ^^^^^ unreachable pattern
  |
  = note: `#[warn(unreachable_patterns)]` on by default

warning: unused variable: `True`
 --> src/main.rs:3:9
  |
3 |         True => println!("I am true!"),
  |         ^^^^ help: if this is intentional, prefix it with an underscore: `_True`
  |
  = note: `#[warn(unused_variables)]` on by default

warning: unused variable: `False`
 --> src/main.rs:4:9
  |
4 |         False => println!("I am false!"),
  |         ^^^^^ help: if this is intentional, prefix it with an underscore: `_False`

warning: variable `True` should have a snake case name
 --> src/main.rs:3:9
  |
3 |         True => println!("I am true!"),
  |         ^^^^
  |
  = note: `#[warn(non_snake_case)]` on by default
help: rename the identifier or convert it to a snake case raw identifier
  |
3 |         r#true => println!("I am true!"),
  |         ~~~~~~

warning: variable `False` should have a snake case name
 --> src/main.rs:4:9
  |
4 |         False => println!("I am false!"),
  |         ^^^^^
  |
help: rename the identifier or convert it to a snake case raw identifier
  |
4 |         r#false => println!("I am false!"),
  |         ~~~~~~~

warning: `playground` (bin "playground") generated 5 warnings (run `cargo fix --bin "playground"` to apply 2 suggestions)
    Finished dev [unoptimized + debuginfo] target(s) in 0.40s
     Running `target/debug/playground`
```


### Desired output

```Shell
error: `True` will unconditionally match both `true` and `false` values.
 --> src/main.rs:3:9
  |
3 |         True => println!("I am true!"),
  |         ^^^^
  |
note: to pattern match on booleans in Rust, use `true` or `false` instead (note the capitalization)
 --> src/main.rs:3:9
  |
3 |         true => println!("I am true!"),
  |         ^^^^
  |
```


### Rationale and extra context

For new Rustaceans coming from Python, none of the warnings actually explain the logical error here and do not indicate that there is almost certainly a logical bug going on here.

I'm not sure if this is worthwhile to add a correctness lint (deny-by-default), but this is almost certainly will be confusing for folks who are expecting `True` to be a value, not a pattern.

### Other cases

This should probably error if a boolean is matched on `False` as well.

### Anything else?

Tested on Nightly version: 1.72.0-nightly (2023-06-12 df77afbcaf3365a32066)
Repository: vscode
Issue: Unable to launch sandboxed process from when application is started from a UNC path
Labels: bug,upstream,under-discussion,chromium,sandbox

From @roblourens 

```
when I launch it from the terminal, I get “GPU process launch failed”. If I start with --disable-gpu-sandbox
I get a window but it has a “terminated unexpectedly” dialog at startup.
```

It was confirmed that launching with `--no-sandbox --disable-gpu-sandbox` resolves the issue but the author was not running the application as elevated, so I am doubtful it is related to https://github.com/microsoft/vscode/issues/122951.

@roblourens can you confirm the following,

1) Does the archive application launch fine when you use `code --user-data-dir <some-path>`
2) Does it launch when you use the portable mode https://code.visualstudio.com/docs/editor/portable#_windows-linux
Repository: stable-diffusion-webui
Issue: [Bug]: Grid is off-screen and is unaccessible
Labels: enhancement

### Is there an existing issue for this?

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

### What happened?

![Screenshot_2023-06-15-04-02-05-46](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/69055294/ec404849-6350-4a04-8213-6ccc0fd9cf75)
I can't scroll left to open the grid. I can get to it if i open a pic, then press left.

### Steps to reproduce the problem

1. Go to public URL via your phone
2. Generate 9 pics
3. Try to access the grid


### What should have happened?

Grid should have appeared

### Commit where the problem happens

https://github.com/AUTOMATIC1111/stable-diffusion-webui/commit/baf6946e06249c5af9851c60171692c44ef633e0

### What Python version are you running on ?

Python 3.10.x

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

Android

### 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
--xformers --share
```


### List of extensions

No

### Console logs

```Shell
Python 3.10.6 (tags/v3.10.6:9c7b4bd, Aug  1 2022, 21:53:49) [MSC v.1932 64 bit (AMD64)]
Version: v1.3.2
Commit hash: baf6946e06249c5af9851c60171692c44ef633e0
Installing requirements
Launching Web UI with arguments: --xformers --share
Calculating sha256 for C:\webui\models\Stable-diffusion\AbyssOrangeMix v3.safetensors: Running on local URL:  http://127.0.0.1:7860
5493a0ec491f5961dbdc1c861404088a6ae9bd4007f6a3a7c5dee8789cdc1361
Loading weights [5493a0ec49] from C:\webui\models\Stable-diffusion\AbyssOrangeMix v3.safetensors
Creating model from config: C:\webui\configs\v1-inference.yaml
LatentDiffusion: Running in eps-prediction mode
DiffusionWrapper has 859.52 M params.
Running on public URL: https://7807ab80ebf0217b0b.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: 7.7s (import torch: 0.9s, import gradio: 0.9s, import ldm: 0.3s, other imports: 0.7s, load scripts: 0.8s, create ui: 0.3s, gradio launch: 3.7s).
Applying optimization: xformers... done.
Textual inversion embeddings loaded(0):
Model loaded in 5.2s (calculate hash: 2.3s, load weights from disk: 0.1s, create model: 0.3s, apply weights to model: 0.5s, apply half(): 0.6s, move model to device: 0.5s, load textual inversion embeddings: 0.8s).
Calculating sha256 for C:\webui\models\Stable-diffusion\aurora_v10.safetensors: 1b5f8211ec04926035ac81033518c802db9964e93630ab4698b6365b9811c7eb
Loading weights [1b5f8211ec] from C:\webui\models\Stable-diffusion\aurora_v10.safetensors
Applying optimization: xformers... done.
Weights loaded in 2.4s (calculate hash: 1.5s, load weights from disk: 0.2s, apply weights to model: 0.3s, move model to device: 0.5s).
```


### Additional information

_No response_
Repository: pytorch
Issue: Disclose C++ ATen ops type promotion rules under OpOverload in Python
Labels: module: docs,triaged

### 🚀 The feature, motivation and pitch

As title, is it possible or good idea?

Motivation is to enable doing fx aten -> fx aten transformation with casts explicitly inserted. 

### Alternatives

_No response_

### Additional context

_No response_

cc @svekars @carljparker
Repository: pytorch
Issue: "addmm_out_sparse_csr_impl_mkl" not implemented for 'Byte'
Labels: module: sparse,triaged

### 🐛 Describe the bug

```
import torch
a =torch.zeros(128, 12288*4, dtype=torch.uint8)                                                                                                                                                                                                                                                                                                                              
                                                                                                                                                                                                           
a = a.to_sparse_csr()                                                                                                                                                                                      
# b = torch.rand(12288*4, 4096, dtype=torch.int8)                                                                                                                                                          
b = torch.randint(high=255, size=(12288*4,12288), dtype=torch.uint8)                                                                                                                                       
torch.sparse.mm(a,b)
```

### Versions

PyTorch version: 2.0.1+cu117
Is debug build: False
CUDA used to build PyTorch: 11.7
ROCM used to build PyTorch: N/A

OS: CentOS Linux 7 (Core) (x86_64)
GCC version: (GCC) 9.3.0
Clang version: Could not collect
CMake version: version 3.26.3
Libc version: glibc-2.17

Versions of relevant libraries:
[pip3] intel-extension-for-pytorch==2.0.100
[pip3] numpy==1.24.1
[pip3] torch==2.0.1
[pip3] torch-scatter==2.1.1
[pip3] torch-sparse==0.6.17
[pip3] torchaudio==2.0.2
[pip3] torchvision==0.15.2
[pip3] triton==2.0.0
[conda] intel-extension-for-pytorch 2.0.100                  pypi_0    pypi
[conda] numpy                     1.24.1                   pypi_0    pypi
[conda] torch                     2.0.1                    pypi_0    pypi
[conda] torch-scatter             2.1.1                    pypi_0    pypi
[conda] torch-sparse              0.6.17                   pypi_0    pypi
[conda] torchaudio                2.0.2                    pypi_0    pypi
[conda] torchvision               0.15.2                   pypi_0    pypi
[conda] triton                    2.0.0                    pypi_0    pypi

cc @alexsamardzic @nikitaved @pearu @cpuhrsch @amjames @bhosmer
Repository: godot
Issue: Unable to accept value for an edit field by clicking outside of it
Labels: bug,topic:editor,usability

### Godot version

v4.1.beta.custom_build [a3c49ad2f]

### System information

Windows 11

### Issue description

In 4.1

![1](https://github.com/godotengine/godot/assets/28705694/d2a8dd6c-62bd-485a-90a2-2e59d6c6eff6)

In 3.5.2

![2](https://github.com/godotengine/godot/assets/28705694/e3627601-8585-417a-84ed-624e454a5252)

In 4.1, you can only make a UI node lose focus by clicking on another UI node that can grab focus. For example, since a panel cannot grab focus, you cannot make the LineEdit lose focus by clicking on the panel in the following scene:

![3](https://github.com/godotengine/godot/assets/28705694/3825b22d-9930-472a-b014-e5edf5e16001)

This is really inconvenient, especially when working in the editor.

### Steps to reproduce

See above.

### Minimal reproduction project

It's simple to reproduce.
Repository: stable-diffusion-webui
Issue: [Feature Request]: 噪声计算方式
Labels: question

### Is there an existing issue for this?

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

### What would your feature do ?

根据Compositional Visual Generation with Composable Diffusion Models, 下边这个denoised不应该context为None模型的预测吗？ 

denoised = torch.clone(denoised_uncond)
denoised[i] += (x_out[cond_index] - denoised_uncond[i]) * (weight * cond_scale)

### Proposed workflow

1. 请帮忙解答一下...


### Additional information

_No response_
Repository: godot
Issue: Light cull mask updates incorrectly when changing VisualInstance3D layers
Labels: bug,topic:rendering,confirmed,topic:3d

### Godot version

v4.1.beta2.official [a2575cba4]

### System information

Windows 10, GL Compatibility, NVIDIA GeForce GTX 1050 Ti (528.24)

### Issue description

When you change the cull mask of a Light3D (tested with both OmniLight3D and SpotLight3D), the meshes in that layer will not update correctly and will remain lit/unlit even if they are on a different mask. It is a bit complicated to explain so I attach a video as well:

https://github.com/godotengine/godot/assets/6643844/24824656-4126-441e-a952-d8493cdcb4f3

It's like they are "one step behind". Additionally, if you follow the steps in "steps to reproduce" you will see that the cull mask is not respected at first, until you update the cull mask again, the changes are applied. See a video of this:

https://github.com/godotengine/godot/assets/6643844/b3fa8ea1-6ea9-4c49-b750-603b074721a6

One last example, if you hide the lights and the meshes, and then show them again, the cull mask is not respected either. See the following example:

https://github.com/godotengine/godot/assets/6643844/9f6ddb42-649d-455c-a4c3-44c2328e4a36

For reference:
- The cubes are in layer 4
- The spheres are in layer 1
- The light only have cull mask 1 enabled

Only tested on GL Compatibility renderer.


### Steps to reproduce

- Add an OmniLight3D
- Set the OmniLight3D cull mask only to 4 for example
- Add a MeshInstance3D with any mesh
- Set the MeshInstance3D layer to 1 for example
- You will see that the cull mask is not applied/used

### Minimal reproduction project

[GodotLights.zip](https://github.com/godotengine/godot/files/11752286/GodotLights.zip)
Repository: storybook
Issue: [Bug]: Vue3 Automatic inferenced argTypes don't work well
Labels: bug,vue3,docgen

### Describe the bug

I'm using latest storybook whose verison is 7.0.20.
I'm using vite+vue preset.
I have a Component, and I wrote stories for it, but the automatic inferenced argTypes don't work well:
<img width="1028" alt="image" src="https://github.com/storybookjs/storybook/assets/13799160/e4d865e7-cb41-456f-8c8b-6f88593418a1">
There are events, but I can't see any log in `Actions` Panel.
In order to see logs, I need to manually write:
```ts
const meta: Meta<typeof Editor> = {
  component: Component,
  argTypes: {
    onReady: {},
  },
}
```
Now, there are logs, however, the `Controls` panel looks no ok:
<img width="1159" alt="image" src="https://github.com/storybookjs/storybook/assets/13799160/032eb77f-bedb-4aa9-b718-10e660f03daa">

I think, the auto inferenced argTypes are like this:
```ts
{
  ready: {
    table: {
      category: 'events'
    }
  }
}
```
Maybe, we can improve it to:
```ts
{
  onReady: {
    name: 'ready',
    table: {
      category: 'events'
    }
  }
}
```

so the `parameters.actions.argTypesRegex: "^on[A-Z].*"` can automatically catch all events.

### To Reproduce

_No response_

### System

_No response_

### Additional context

_No response_
Repository: material-ui
Issue: MenuList doesn't recognize scrollbar size correctly.
Labels: bug 🐛,component: menu,package: material-ui

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example:
https://mui.com/material-ui/react-menu/#max-height-menu

Steps:

1. check MuiList's style on developer tools.
2. you can find element.style is set to padding-right:0px.
![스크린샷 2023-06-15 오후 12 54 29](https://github.com/mui/material-ui/assets/62272445/4ae7bf96-87f5-4fac-be84-b1dd030c4767)


### Current behavior 😯

I found that MenuList is using `getScrollbarSize()` utils and [set scrollbar size as paddingRight (on rtl mode).](https://github.com/mui/material-ui/blob/acf9fc4312b6cf9473fbd9959bb3515f89758af2/packages/mui-material/src/MenuList/MenuList.js#L133).

I think scrollbar size is not measured accurately. so when I set maxHeight to Menu and it render options with scrollbar, the padding-right is removed.
MenuList set `element.style` so I can't override that style on theme level (styleOverrides)

![스크린샷 2023-06-15 오후 12 54 40](https://github.com/mui/material-ui/assets/62272445/4f07d17d-178d-42e2-90be-b68dd300988f)

### Expected behavior 🤔

If scrollbar size is measured to 0px, I think it should not override menu list's right padding. because default padding can be bigger than zero.

### Context 🔦

_No response_

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>
Repository: pytorch
Issue: AOT autograd: Avoid dependency on strides for manual regeneration of outputs that are aliased to inputs
Labels: feature,triaged,oncall: pt2,module: aotdispatch,module: pt2-dispatcher

### 🐛 Describe the bug

AOT autograd's manual regeneration of outputs assumes strided output tensor  support. But backends like Habana (https://docs.habana.ai/en/latest/index.html) produces contiguous tensor outputs. As a result, examples like the below one results in accuracy issues

 ```
def fn(a):
  b = a.t()
  b.mul_(1.0)
  return b   

x = torch.arange(6).reshape([2, 3]).to('hpu')

print("x ", x.cpu())

compiled_fn = torch.compile(fn, backend="aot_hpu_training_backend")        
y = compiled_fn(x)

print("y ", y.cpu())

```

**Console prints:**

x  tensor([[0, 1, 2],
        [3, 4, 5]])
		
y  tensor([[0, 1],
        [2, 3],
        [4, 5]])
		
Tensor y has incorrect values. Expected output is 
y  tensor([[0, 3],
        [1, 4],
        [2, 5]])
		
Our analysis suggests that the issue occurs in step 4 of runtime_wrapper(), inside gen_alias_from_base(). This function assumes strided tensor for mul's output. Related bug for TPU backend: https://github.com/pytorch/xla/issues/5179

**Request:** 
Please avoid dependency on the tensor strides for output regeneration. Instead the information regarding the original alias operation (transpose in the above example) should be used. 



### Versions

Collecting environment information...
PyTorch version: 2.0.1a0+git7f346ef
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: Ubuntu 20.04.3 LTS (x86_64)
GCC version: (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
Clang version: 14.0.5 (ssh://gerrit:29418/tpc_llvm10 38f3bfdbf5b8581125aa7ac5a2605c9674624566)
CMake version: version 3.26.3
Libc version: glibc-2.31

Python version: 3.8.11 (default, Aug  3 2021, 15:09:35)  [GCC 7.5.0] (64-bit runtime)
Python platform: Linux-5.4.0-137-generic-x86_64-with-glibc2.17
Is CUDA available: False
CUDA runtime version: No CUDA
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

cc @ezyang @msaroufim @bdhirsh @anijain2305 @zou3519 @chauhang @wconstab