sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: SizedBox calculates intrinsic dimensions incorrectly
Labels: framework,customer: crowd,has reproducible steps,P2,has partial patch,team-framework,triaged-framework,found in release: 3.13,found in release: 3.16

Let's start with example, you can paste it into https://dartpad.dev

```dart
import 'package:flutter/material.dart';
import 'package:flutter/rendering.dart';

void main() {
  debugPaintSizeEnabled = true;   
  
  runApp(
    const MaterialApp(
      home: Scaffold(
        body: Center(
          child: IntrinsicHeight(
            child: SizedBox(
              width: 100,
              child: Column(
                children: [
                  Text(lipsum),
                ],
              ),
            ),
          ),
        ),
      ),
    ),
  );
}

const lipsum =
    'Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam malesuada vulputate efficitur. Curabitur a nulla et nulla bibendum rhoncus. Duis nec porttitor nunc, vitae pharetra sapien. Ut et vulputate velit, eget porttitor nulla. Curabitur maximus dui id nunc ornare lacinia.';
```

The `Column` has height equal to intrinsic heigth of its child. But it's wrong. The `computeMinIntrinsicHeight` doesn't take into account the `SizedBox`'s `width` when it should. It calculates the intrinsic height with the height it receives from the parent. You can see this height by commenting out the `width` line.

Reproducible both on Flutter stable (`3.13.7`) and master (`3.16.0-11.0.pre.3`).

| Expected | Actual | What intrinsic height "sees" as width |
|-|-|-|
| ![image](https://github.com/flutter/flutter/assets/4085280/eade5a08-7351-4518-a278-365a24d9c1e0) | ![image](https://github.com/flutter/flutter/assets/4085280/a39183d4-5c3b-4238-87e8-2b007e459ba0) | ![image](https://github.com/flutter/flutter/assets/4085280/e34bbf33-49bf-4291-838e-0c567cdc89bf) |

The faulty code is in `RenderConstrainedBox`, so it touches not only `SizedBox`, but also `ConstrainedBox` and possibly other widgets. It's both in compute intrinsic height and width methods.

```dart
  @override
  double computeMinIntrinsicHeight(double width) {
    if (_additionalConstraints.hasBoundedHeight && _additionalConstraints.hasTightHeight) {
      return _additionalConstraints.minHeight;
    }
    final double height = super.computeMinIntrinsicHeight(width);
    assert(height.isFinite);
    if (!_additionalConstraints.hasInfiniteHeight) {
      return _additionalConstraints.constrainHeight(height);
    }
    return height;
  }
```
Repository: godot
Issue: Removing @export var customResource: CustomResource does not delete ExtResource from tscn
Labels: topic:core,topic:gdscript,topic:editor,needs testing

### Godot version

v4.2.beta2.official [f8818f85e]

### System information

Linux pop-os 6.5.4-76060504-generic, RTX3060

### Issue description

I have deleted `@export var soil_data: Soil` but tscn file still have `soil_data = ExtResource("2_0ywxf")`. It is not showing the field in the editor thou.

Might be related to https://github.com/godotengine/godot/issues/47253

Sometimes I see also this not being cleaned up
`[ext_resource type="Resource" uid="uid://dp2dhx8g53x5a" path="res://World/Soil/Soil_resource.tres" id="2_mrpfg"]`
### Steps to reproduce

1. Create new custom resource
2. Create new scene and script that will reference that custom resource with @export
`@export var your_resource: CustomResourceName`
3. Delete the above line
4. Inspect the scene file

### Minimal reproduction project

Not included
Repository: tauri
Issue: [feat] Custom back button/gesture behavior on Android
Labels: type: feature request,platform: iOS,platform: Android

### Describe the problem

Currently, on Tauri v2, if the back button or gesture is used on Android, and the app is a single page app (e.g., manages everything on the same page without managing custom history), the app just closes.

### Describe the solution you'd like

I would like to be able to implement custom behavior for the Android back button/gesture. This could possibly be done through a global event that can be listened for, but there should also be a way to disable the default behavior for it. There could also be a way to register a handler while initializing Tauri.

### Alternatives considered

This could also be done by giving Tauri a way to manage the custom browser history, and telling the frontend or backend when the back/forward browser events are triggered. This could also be managed through the developer's frontend framework of choice, but it might require a refactor if the app framework isn't already using custom routing or separate browser pages.

### Additional context

[The Discord support thread that prompted this feature request](https://discord.com/channels/616186924390023171/1167318179043868772)
Repository: PowerToys
Issue: display-switch: Automatically switch monitor source when switching to another computer
Labels: Issue-Feature,Product-Mouse Without Borders

### Description of the new feature / enhancement

While MWB provides the functionality to use input devices across multiple devices, I would to get [display-switch](https://github.com/haimgel/display-switch) included in PowerToys.
display-switch monitors USB-devices. Whenever a specific device is connect (or disconnected) it "tells" the monitor(s) to switch to another source.



### Scenario when this would be used?

I am using 2 computers and 3 monitors, I never use both computers simultaneously, but I always use all displays at the same time.

### Supporting information

You'll find lots of info at the project's page on Github: https://github.com/haimgel/display-switch#turn-a-30-usb-switch-into-a-full-featured-kvm
Repository: neovim
Issue: "zi" does not trigger OptionSet foldenable
Labels: bug-vim,needs:vim-patch,normal-mode

### Problem

The normal mode `zi` command toggles the state of the `'foldenable'` option. However, an autocmd listening on `OptionSet foldenable` is not being triggered when this happens.

### Steps to reproduce

1. `nvim --clean`
2. `:au OptionSet foldenable echo "foldenable: " .. &foldenable`
3. Hit `zi` multiple times. Nothing is being printed. You can `set fen?` to see that every `zi` toggles its state.
4. Do `:set fen!`. The autocmd will trigger and print a message.

### Expected behavior

I would expect the autocmd to fire when pressing `zi`.

As a workaround, `:nnoremap <silent> zi :set fen!<CR>` seems to work, but I'd say this is a bug nevertheless.

### Neovim version (nvim -v)

0.9.4 via AppImage, but 0.7.2 via the Debian 12 package behaves the same

### Vim (not Nvim) behaves the same?

yes, 9.0.1499

### Operating system/version

Debian 12

### Terminal name/version

kitty 0.26.5

### $TERM environment variable

xterm-kitty

### Installation

Debian package & AppImage
Repository: go
Issue: cmd/compile: type sets are not correctly deduced for type conversion on type params
Labels: compiler/runtime

### What version of Go are you using (`go version`)?

Go Playground, 1.21

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

N/A, Go Playground

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is best.
-->

https://go.dev/play/p/Jhx6YGrz21s

### What did you expect to see?

Both `convert()` and `convert2()` are accepted by the compiler and are semantically equivalent.

### What did you see instead?

`convert2()` is rejected by the compiler: `cannot convert x (variable of type srcType constrained by string) to type dstType: cannot convert string (in srcType) to type []elType (in dstType)`

### Details

[The spec](https://go.dev/ref/spec#Conversions) says the following about type conversions of type params:

> Additionally, if T or x's type V are type parameters, x can also be converted to type T if one of the following conditions applies:
>
>  - Both V and T are type parameters and a value of each type in V's type set can be converted to each type in T's type set.

Consider the following code:

```go
type charLike interface{ byte | rune }

func convert2[elType charLike, srcType string, dstType []elType](x srcType) dstType {
	return dstType(x) // ERROR: cannot convert x (variable of type srcType constrained by string) to type dstType: cannot convert string (in srcType) to type []elType (in dstType)
}
```

Here `srcType`'s type set should be just `string`, and `dstType`'s type set is `[]rune|[]byte`. As per spec, `string` can be converted to both `[]rune` and `[]byte`:

> A non-constant value x can be converted to type T in any of these cases:
>
> - ...
> - x is a string and T is a slice of bytes or runes.

So, conversion should be allowed, assuming the compiler is able to correctly deduce type set for `dstType`.

The simplest example of the issue I was able to find:

```go
func convert2[elType byte, dstType []elType](x string) dstType {
	return dstType(x) // ERROR: cannot convert x (variable of type string) to type dstType: cannot convert string to type []elType (in dstType)
}
```

The next step of eliminating elType makes the error disappear:

```go
func convert2[dstType []byte](x string) dstType {
	return dstType(x)}
```

So it seems the compiler fails to flatten `dstType`'s type set with indirection from `elType`.

Also, @Merovius was able to construct the following two semantically equivalent examples that hint that the issue is somehow specific to the type conversion operation:

 - Rejected: https://go.dev/play/p/WH_JH6Gwim-
 - Accepted: https://go.dev/play/p/p2n0fc1QoBj
Repository: TypeScript
Issue: Invalid synthesized import specifiers on infered types in declarations
Labels: Needs Investigation

### 🔎 Search Terms

"import specifiers in declarations", "import nested files"

### 🕗 Version & Regression Information

Can reproduce on version 5.2.2 and "next" (5.3.0-dev.20231030).

### ⏯ Playground Link

_No response_

### 💻 Code

```ts
// @file a.ts

import { forwardRef, type PropsWithChildren } from "react";

import { type ExportedType } from "@ts-bug/b";

export type Props = PropsWithChildren<{
  // Tile props.
  active?: ExportedType;
}>;

export const Component = forwardRef<HTMLLIElement, Props>(() => {
  return null;
});

// @file @ts-bug/src/index.ts

import { type ExportedType as NaturalExportedType } from './type'

export type ExportedType = NaturalExportedType;

// @file @ts-bug/src/type.ts

export type ExportedType = 'overlay' | 'rearrange' | 'origin' | 'destination';

```


### 🙁 Actual behavior

The generated declarations for `a.ts` contain an invalid import into one of the nested declaration files instead of using the main package export.

```ts
// @file a.d.ts

import { type PropsWithChildren } from "react";
import { type ExportedType } from "@ts-bug/b";
export type Props = PropsWithChildren<{
    active?: ExportedType;
}>;
export declare const Component: import("react").ForwardRefExoticComponent<{
    active?: import("b/dist/types/src/type").ExportedType | undefined;
} & {
    children?: import("react").ReactNode;
} & import("react").RefAttributes<HTMLLIElement>>;
//# sourceMappingURL=index.d.ts.map
```


### 🙂 Expected behavior

The declarations should use the main package export.

```ts
    active?: import("@ts-bug/b").ExportedType | undefined;
```


### Additional information about the issue

Repoduction repo:
https://github.com/dmaretskyi/ts-bug
Repository: opencv
Issue: Enabling OpenEXR after python module import
Labels: feature

### Describe the feature and motivation


**Problem**
The current method to enable OpenEXR image reading in python is to add a line with `os.environ["OPENCV_IO_ENABLE_OPENEXR"] = "1"`  before the import of opencv using `import cv2`.

This goes against the pep8 guideline that "Imports are always put at the top of the file, just after any module comments and docstrings, and before module globals and constants." (see https://peps.python.org/pep-0008/#imports).
As a consequence linters such as ruff,  pycodestyle or flake8 generate errors . 
One can add comments to ignore the specific linting error in the lines following the line that contains ` os.environ["OPENCV_IO_ENABLE_OPENEXR"] = "1"` but this make the linting weaker and pollutes the code with comments to ignore the errors. 

**Feature**
It would be great if we could import opencv first using  `import cv2` and then enable OpenEXR within the code following the imports section using a method `cv2.enable_openexr()` for example.





### Additional context

_No response_
Repository: godot
Issue: .cs is not an option in POT generation files
Labels: enhancement,topic:editor,topic:dotnet

### Godot version

4.1.2-stable

### System information

Godot v4.1.2.stable.mono - Arch Linux #1 SMP PREEMPT_DYNAMIC Thu, 26 Oct 2023 00:52:20 +0000 - Tty - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1050 Ti (nvidia; 535.113.01) - Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz (8 Threads)

### Issue description

Currently cannot add cs files to pot generation.

### Steps to reproduce

Go to Project Settings, Select Localization in the Settings Screen.  Click on POT Generation in the subscreen.  Click on Add.
Go to the bottom right drop down and click to show the options and .cs does not exist.

### Minimal reproduction project

Can do this with a new project.
Repository: pytorch
Issue: torch.jit.trace output changes when I add comments to the file
Labels: oncall: jit

### 🐛 Describe the bug

I'm trying to compute a hash of a serialized torchscript object to check if it's equal to some other torchscript object.

However, I've found this to be very flaky, and that the serialized model changes when I do something as simple as adding a comment to the file. Here's an example:

```
import torch
import hashlib
from io import BytesIO

class MyModel(torch.nn.Module):
    def forward(self, x):
        return x * 2

model = MyModel()
x = torch.ones(1, 10, 10)
traced_script_1 = torch.jit.trace(model, x)
buffer_1 = BytesIO()
torch.jit.save(traced_script_1, buffer_1)
hash_1 = hashlib.sha256(buffer_1.getvalue()).hexdigest()
print(hash_1)

> prints 4853c8f7da11cd2b4f2062f8f367b558d710b7963a4a81613ab5c99bb8bcb97e
```

```
import torch
import hashlib
from io import BytesIO

class MyModel(torch.nn.Module):
    def forward(self, x):
        return x * 2

model = MyModel()
x = torch.ones(1, 10, 10)
# Adding this comment changes the serialized trace
traced_script_1 = torch.jit.trace(model, x)
buffer_1 = BytesIO()
torch.jit.save(traced_script_1, buffer_1)
hash_1 = hashlib.sha256(buffer_1.getvalue()).hexdigest()
print(hash_1)

> prints b4659f86164204f2197f919feaa61e33cdb00f148200dc5d020e0cad2ab7b256
```

I assume the line number is getting baked into the trace somehow, but this seems unnecessary? The actual computation graph hasn't changed, so I'd expect the serialized trace not to change. Any ideas how to make this more consistent and produce a hash that changes iff the actual computation graph changes. Thanks!

### Versions

Collecting environment information...
PyTorch version: 1.13.1
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: macOS 14.0 (arm64)
GCC version: Could not collect
Clang version: 15.0.0 (clang-1500.0.40.1)
CMake version: version 3.27.7
Libc version: N/A

Python version: 3.8.18 (default, Aug 25 2023, 02:07:22)  [Clang 14.0.3 (clang-1403.0.22.14.1)] (64-bit runtime)
Python platform: macOS-14.0-arm64-arm-64bit
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

CPU:
Apple M2 Pro

Versions of relevant libraries:
[pip3] mypy-extensions==1.0.0
[pip3] numpy==1.23.1
[pip3] torch==1.13.1
[pip3] torchvision==0.14.1
[conda] Could not collect

cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel
Repository: stable-diffusion-webui
Issue: Support rdna3
Labels: enhancement,platform:amd

### 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 ?

RDNA 3 CARDS


### Proposed workflow

HSA_OVERRIDE_GFX_VERSION=11.0.0
pip install --pre torch torchvision --index-url https://download.pytorch.org/whl/nightly/rocm5.7

![image](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/22727137/cb1985c0-3936-4c1f-916f-d925d70e460e)
working very well with rocm5.7

### Additional information

_No response_
Repository: storybook
Issue: [Documentation]: Semantics for "How to write stories" doc
Labels: documentation

### Describe the problem

In line 58 in [/storybook/docs/writing-stories/introduction.md](https://github.com/storybookjs/storybook/blob/next/docs/writing-stories/introduction.md)

"We recommend you use UpperCamelCase for your story exports."

Why does the sentence use the word 'UpperCamelCase' instead of 'PascalCase', I though PascalCase is more commonly used for this context.

### Additional context

This is just a small nitpick, but if there is a reason for the word selection, please just ignore this issue.
Repository: godot
Issue: Forward+ renderer crashes godot for any project
Labels: bug,topic:rendering,needs testing,crash

### Godot version

4.1.2.stable

### System information

Godot v4.1.2.stable - Windows 10.0.14393 Vulkan (Compatibility) - AMD A10-8700P Radeon R6, 10 Compute Cores 4C + 6G (4 Threads)

### Issue description

Whenever i use the forward+ renderer a message shows godot has stopped working then it closes.

### Steps to reproduce

The issue is when i make a new project with forward + renderer godot stops working

### Minimal reproduction project

The issue is when i make a new project with forward + renderer godot stops working
Repository: PowerToys
Issue: Always on Top - Auto-size Maximize
Labels: Product-Always On Top,Needs-Triage

### Description of the new feature / enhancement

When using Always on Top, if you maximize a window, it'll only maximize against the edges of the pinned window (so it doesn't go behind it)

### Scenario when this would be used?

Window is marked as always on top. You want to maximize another window, but don't want it to go behind the pinned window.

### Supporting information

_No response_
Repository: neovim
Issue: Pass Window ID as event argument for autocommands
Labels: enhancement,api,events

### Problem

I'm writing a plugin which uses autocommands for the `WinNew` and `WinClosed` events, and I need the window ID of opened and closed windows. It would be nice if the window IDs were passed in the callback argument table.

Examples:
- It's sort of done in `WinClosed`, with the ID of the window to be closed being passed in as a string in `ev.file` and `ev.match`. I'm not sure why it does this, perhaps an oversight when they were originally implemented in vim?

- `WinClosed` doesn't pass the ID at all.

Is there a reason this isn't already a thing? Am I misunderstanding the use of the callback argument?

### Expected behavior

Window ID of window to be opened/closed should be passed as an integer in the callback event argument table.
I found the documentation quite unclear on this, but I believe it should be passed as an integer in `ev.data`. This shouldn't break backwards compatibility, as this would simply be an addition to the current argument table.
Repository: godot
Issue: Android Godot Editor doesn't detect screen touches.
Labels: bug,platform:android,topic:input

### Godot version

v3.6.beta3.official [21ab700f2]

### System information

Android 8.0.0 - Godot v3.6.beta3.official [21ab700f2] - OpenGL ES 3.0

### Issue description

Setting the `emulate mouse from touch` configuration turn off makes Android Godot Editor no longer detects any motion on the screen after opening it again.

https://github.com/godotengine/godot/assets/147288128/65f52d27-331e-495b-9d71-5fcfa1844bef

This shouldn't affect the editor.

### Steps to reproduce

1. Create a new project.
2. When open go to project settings.
3. Turn off `emulate mouse from touch`

### Minimal reproduction project

Due to this bug is caused by a project configuration it can be reproduced with a simple new project, and that's why a minimal reproduction project it's not necessary.
Repository: deno
Issue: Feat: `Image` class
Labels: web,suggestion

Adding the `Image` class makes it easier to pass images from the client to Deno and back and forth easily.
Repository: go
Issue: x/build/maintner/maintnerd/gcslog: TestGCSLogWakeup_Activity failures
Labels: Builders,NeedsInvestigation

```
#!watchflakes
post <- pkg == "golang.org/x/build/maintner/maintnerd/gcslog" && test == "TestGCSLogWakeup_Activity"
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/31267ed5ce15ec01721cb681ebf512c06a43e9a3)):

    2023/10/30 16:25:16 wrote record; flush timer registered.
    --- FAIL: TestGCSLogWakeup_Activity (0.57s)
        gcslog_test.go:39: changed = false; want true


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: pytorch
Issue: torch.export emits node outside of Core ATen IR
Labels: triaged,export-triaged,export-triage-review,oncall: export

### 🐛 Describe the bug

```python
import torch

def func(x):
    return x.nonzero()

input = torch.randn(3, 4)

ep = torch.export.export(func, args=(input,))
ep = ep.run_decompositions()
ep.graph_module.print_readable()
```

the produced model has unexpected `torch.ops.aten._assert_async.msg` nodes which dont belong to the [Core ATen IR](https://pytorch.org/docs/main/torch.compiler_ir.html):

```bash
class GraphModule(torch.nn.Module):
    def forward(self, arg0_1: f32[3, 4]):
        # File: test_log_sigmoid.py:4, code: return x.nonzero()
        nonzero: i64[i2, 2] = torch.ops.aten.nonzero.default(arg0_1);  arg0_1 = None
        
        # File: /opt/pytorch/torch/_export/pass_base.py:45, code: return NodeMetadata({"stack_trace": "".join(traceback.format_stack(limit=1))})
        sym_size: Sym(i2) = torch.ops.aten.sym_size.int(nonzero, 0)
        ge: Sym(i2 >= 2) = sym_size >= 2
        scalar_tensor: f32[] = torch.ops.aten.scalar_tensor.default(ge);  ge = None
        _assert_async = torch.ops.aten._assert_async.msg(scalar_tensor, 'nonzero.shape[0] is outside of inline constraint [2, 12].');  scalar_tensor = None
        le: Sym(i2 <= 12) = sym_size <= 12;  sym_size = None
        scalar_tensor_1: f32[] = torch.ops.aten.scalar_tensor.default(le);  le = None
        _assert_async_1 = torch.ops.aten._assert_async.msg(scalar_tensor_1, 'nonzero.shape[0] is outside of inline constraint [2, 12].');  scalar_tensor_1 = None
        sym_size_1: Sym(i2) = torch.ops.aten.sym_size.int(nonzero, 0)
        ge_1: Sym(i2 >= 0) = sym_size_1 >= 0
        scalar_tensor_2: f32[] = torch.ops.aten.scalar_tensor.default(ge_1);  ge_1 = None
        _assert_async_2 = torch.ops.aten._assert_async.msg(scalar_tensor_2, 'nonzero.shape[0] is outside of inline constraint [0, 12].');  scalar_tensor_2 = None
        le_1: Sym(i2 <= 12) = sym_size_1 <= 12;  sym_size_1 = None
        scalar_tensor_3: f32[] = torch.ops.aten.scalar_tensor.default(le_1);  le_1 = None
        _assert_async_3 = torch.ops.aten._assert_async.msg(scalar_tensor_3, 'nonzero.shape[0] is outside of inline constraint [0, 12].');  scalar_tensor_3 = None
        return (nonzero,)
```

### Versions

pytorch main

cc @avikchaudhuri @gmagogsfm @zhxchen17 @tugsbayasgalan @angelayi @suo