sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Resolution issue with dual monitors with different DPI
Labels: platform:windows,topic:porting,needs testing

### Godot version

4.1.2.stable

### System information

Vulkan API 1.3.224 - Forward+ - Using Vulkan Device #0: NVIDIA - NVIDIA GeForce GTX 1060 with Max-Q Design

### Issue description

I have two screens: 
- my laptop's one, 1920x1080, 120 DPI, 125% Windows scale 
- and an external one, 1920x1080, 96 DPI, 100% Windows scale

I work on a 2D pixel perfect game. When I display it fullscreen on my laptop everything is nice and sharp, but not on the external screen where I have scaling issues (the pixel art is altered). I logged the screen resolution according to Godot and I got this:
- laptop: 1920x1080
- external: 2400x1350 (which is 125% of 1920x1080...)

I tried to disable the "allow_hidpi" settings, then I got this: 
- laptop: 1536x864 (125% of this gives 1920x1080...)
- external: 1920x1080

Finally I put back the "allow_hidpi" settings and disabled the 125% scaling in windows settings: 
- laptop: 1920x1080
- external: 1920x1080

As I understand these results I'd say that Godot is handling well the Windows scaling through the "allow_hidpi" setting, but is failign to handle correctly the case where the two screens have a different scaling value in the Windows settings. I expected Godot to use a 1920x1080 resolution for the two screens in this case.

### Steps to reproduce

- Have two screens with a same resolution
- Give screen 1 a 125% scaling in Windows settings
- Give screen 2 a 100% scaling in Windows settings
- Launch any Godot scene and print "DisplayServer.screen_get_size()"
- Move the window to a screen to another and notice the displayed value changes.

### Minimal reproduction project

[minimal_reproduction_project.zip](https://github.com/godotengine/godot/files/13389496/minimal_reproduction_project.zip)
Repository: go
Issue: proposal: cmd/go: include the raw import path in the output of `go list -json`
Labels: Unfortunate,Proposal,GoCommand

### Background

The `ImportPath` field in the output of `go list -json` is not quite [what it says on the tin](http://thecodelesscode.com/case/84). Instead of a package import path, it contains an import path augmented with a suffix for uniqueness.

This has led to several bugs and some confusion in the past:
- #26722
- #43380
- #44963
- #60454

It also adds complexity in tools that deal with the output of `go list`. For example, [`golang.org/x/tools/go/packages`](https://cs.opensource.google/go/x/tools/+/master:go/packages/golist.go;l=544-549;drc=f60f2e6aa42c945111053771ea53938694791d83) renames the field to `ID` and parses out the package path in an ad-hoc manner:
https://cs.opensource.google/go/x/tools/+/master:go/packages/golist.go;l=544-549;drc=f60f2e6aa42c945111053771ea53938694791d83

Since the way one interacts with the `go` command is by passing it package import paths, the need for this kind of ad-hoc parsing requires that users building tools on top of `cmd/go` must implement their own ad-hoc parsing, with varying degrees of accuracy.

Unfortunately, too many tools already expect the `ImportPath` field to contain this extra information. We cannot feasibly rename `ImportPath` itself to be clearer.

### Proposal

I propose that we add a new field to the `Package` struct format produced by `go list`, containing the original, unmodified path by which the package's source code was located (in `GOROOT`, `GOPATH`, or the module cache).

I suggest that we name the new field `PackagePath`, along the lines of the existing `PkgPath` field reported by `x/tools/go/packages`.

Specifically:
- The path should not contain the suffix `.test` or `_test` unless that suffix is literally included in the directory or module path containing the package source code.
- The path should not contain suffixes to denote test or PGO variants.
- As a result, multiple packages reported by `go list` may share the same `PackagePath`. They can be distinguished using the (misnamed) `ImportPath` field, whose semantics remain unchanged.
Repository: TypeScript
Issue: Types that depend on constants are not narrowing correctly
Labels: Bug,Help Wanted

### 🔎 Search Terms

"ternary narrowing", "ternary constant", "constant narrowing", "constant dependent"

### 🕗 Version & Regression Information

- This is the behavior in every version I tried (including nightly), and I reviewed the FAQ.



### ⏯ Playground Link

https://www.typescriptlang.org/play?ts=5.2.2#code/MYewdgzgLgBAQgeQQGRgXhlATgVwKYwCGEMokUAUBVAJ4AOBAKgPqO4EYDeMAHgFwxoWAJZgA5gBoYjAUNFiYAX2r0mzAGKEANhA4xu-QdnlT1s4+KVVaDaehgAKG3hAAzeEmQBKGHh5Q8MAATEmx8GAB+aVZ2GAEWTR08KgpXHDBgKGFwGFcHL3j9ChgS0nBoGAA3QiwZaLZwrl4BAHJq2papOpaxEBAglqtSsvIqmrNoxN17A1b29U6YCZaQAGtCGkHlYtKsPCgcLDAPFEix2rjz9QpFIA

### 💻 Code

```ts
const BOOL = true as const

type T_True = { x: string, T: string }
type T_False = { x: string, F: string }

type T = (typeof BOOL) extends true ? T_True : T_False

function f(): T {
    const varT: T_True = { x: 'varT', T: 'good' }
    const varF: T_False = { x: 'varF', F: 'okay' }

    return BOOL ? varT : varF
}
```

### 🙁 Actual behavior

Typechecking fails with the error `Type 'T_True | T_False' is not assignable to type 'T_True'. Property 'T' is missing in type 'T_False' but required in type 'T_True'.` on the return statement.

### 🙂 Expected behavior

Typechecking should pass, since the `const BOOL = true as const` should mark the `false` ternary case as unreachable. 

I also tried making T generic with respect to BOOL, and splitting the ternary operator into an if/else, but the same error persisted regardless. 

### Additional information about the issue

_No response_
Repository: go
Issue: proposal: encoding/json: allow using different tag
Labels: Proposal

I think it should be possible to specify a different tag name that should be used when marshallng JSON.

An example use case would be a proxy renaming fields between an internal and external API:

```go
type Example struct {
    CustomerAccountId string `jsonInternal:"kundenKontoId" json:"customerAccountId"`
}
```

When unmarshaling, the tag `jsonInternal` could be specified to unmarshal using the internal names, while when marshaling the normal `json` tag would be used (by default).

The current workaround is having two structs with identical fields but different tags, which feels messy.
Repository: flutter
Issue: Add XCUITests for in_app_purchase_storekit
Labels: platform-ios,p: in_app_purchase,P2,team-ios,triaged-ios

in_app_purchase_storekit's example app has a StoreKit Test config file that can be used to locally test end to end flow without connecting to Storekit server.

We can use this config file to run XCUITests
Repository: godot
Issue: Can't load internal materials on export
Labels: bug,needs testing,topic:export

### Godot version

v4.2.beta5.mono.official [4c96e9676]

### System information

Godot v4.2.beta5.mono - Windows 10.0.22621 (Windows 11 22H2) - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3070 Laptop GPU (NVIDIA; 31.0.15.4584) - 12th Gen Intel(R) Core(TM) i7-12650H (16 Threads)

### Issue description

Load materials at runtine works when running in the editor, but not in the exported build

### Steps to reproduce

- Run the project in editor, notice the glowing cube.
- Export the project
- Run the exported project, notice the cube isn't glowing.

### Minimal reproduction project

[reproduction.zip](https://github.com/godotengine/godot/files/13370579/reproduction.zip)
Repository: go
Issue: x/build/cmd/gomote: `gettar` with a single file generates an invalid tarball
Labels: Builders,NeedsFix

When using `gomote gettar -dir=file` to get a single file (not a directory), it generates an invalid tarball.
```
$ gomote gettar -dir=hello.go $VM
# Downloading tarball for "cherryyz-linux-amd64-0" to "cherryyz-linux-amd64-0.tar.gz"...
$ tar tf cherryyz-linux-amd64-0.tar.gz 
tar: Archive entry has empty or unreadable filename ... skipping.
tar: Error exit delayed from previous errors.
```

Getting a directory works fine, resulting in a valid tarball.

The racebuild command has code that uses `gettar` to retrieve a single file https://cs.opensource.google/go/x/build/+/master:cmd/racebuild/racebuild.go;l=526 , so I think it worked before, and regressed at some point.

If we decide that getting a single file is not supported and must be directory (for racebuild that is fine, we can arrange it to do that), it should emit an error, instead of silently producing a bad tar file.
Repository: godot
Issue: bytes_to_var_with_objects returns null value for custom objects
Labels: topic:core

### Godot version

v4.1.2.stable.official [399c9dc39]

### System information

Godot v4.1.2.stable - Windows 10.0.22621 - Vulkan (Compatibility) - NVIDIA GeForce RTX 2060 (NVIDIA; 31.0.15.3713) - Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz (12 Threads)

### Issue description

I've been working on networking in Godot, and am having a lot of issues with serialization, in that none of the built in serialization APIs seem to be able to handle custom objects. I'm raising this single issue for bytes_to_var_with_objects so as not to risk lumping in a bunch of separate problems into one GitHub issue, but I can post code showing four Godot serialization APIs (var_to_bytes, var_to_bytes_with_objects, var_to_str, and inst_to_dict) failing with basic tests involving custom objects, let me know if I should update the description on this issue with these snippets or raise a separate issue.

With respect to bytes_to_var_with_objects, I've written up a basic test case showing the issue (see minimal reproduction), which is that when passing in an instance of a basic custom class, the de-serialization function returns a null value.
After a brief look into the code I suspect that the issue is that instances of my custom class aren't considered as objects at the C++ level of the engine in the [Variant::get_validated_object](https://github.com/godotengine/godot/blob/56a2b143a2d8868fdbaba798b7b0145516397f48/core/variant/variant.cpp#L2159) method called by [encode_variant](https://github.com/godotengine/godot/blob/56a2b143a2d8868fdbaba798b7b0145516397f48/core/io/marshalls.cpp#L1141), but I'm not sure what would be causing this.



### Steps to reproduce

See minimal reproduction project code

### Minimal reproduction project

```
class TestClass:
	var a : int
	
	func _init(a : int):
		self.a = a

static func simple_bytes_to_var_test():

	var some_object : TestClass = TestClass.new(5)
	var bytes = var_to_bytes_with_objects(some_object)
	print(bytes)
	var deserialised = bytes_to_var_with_objects(bytes)
	assert(deserialised != null, "Deserialisation produced a null value")
```

EDIT: Note that the above test case also fails even with an empty constructor defined for the TestClass:

```
class TestClass:
	var a : int
	
	func _init():
		self.a = 0

static func simple_bytes_to_var_test():
	var some_object : TestClass = TestClass.new()
	var bytes = var_to_bytes_with_objects(some_object)
	print(bytes)
	var deserialised = bytes_to_var_with_objects(bytes)
	assert(deserialised != null, "Deserialisation produced a null value")
```
Repository: vscode
Issue: Provide ability to ignore all line breaks in diff editor (feature request) 
Labels: feature-request,diff-editor

<!-- ⚠️⚠️ 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. -->
Similar to #43026 i would like to have a setting to ignore all line breaks

**New Feature**
- In settings it's possible to set `"diffEditor.ignoreLineBreak": true`

**Current status**
 - to my knowledge there's no option to ignore all line breaks in the diffEditor,

### Example and benefit

The screenshot below compares two versions of a file. Currently it is not easy to see at a glance if the code was changed or only line breaks were added. 
With the new feature this code lines would not be highlighted and therefore the reviewer could see at first glance that nothing must be reviewed here. 

![image](https://github.com/microsoft/vscode/assets/1271555/93c3cbea-c28e-42f7-9b9c-5bb9a37cd31c)
Repository: pytorch
Issue: Update _scaled_mm to support addmm with bias.size == out.size
Labels: triaged,module: float8

# Sumary
We currently have this TORCH_CHECK which is overly restrictive: https://github.com/pytorch/pytorch/blob/c5f26a409a66711e653f4c34c67cb9e690b60d90/aten/src/ATen/native/cuda/Blas.cpp#L740

we should allow for bias/input to be equal to the output size.

I will fix this up


### Repro
``` Python
import torch

t = torch.eye(32,32, device='cuda').to(torch.float8_e4m3fn)
s = torch.ones(32,32, device='cuda').to(torch.float8_e4m3fn)

bias = torch.ones(32, 32, device='cuda').to(torch.bfloat16)
out1 = torch._scaled_mm(t, s.t(), bias=bias)
print(out1)
```

cc @yanbing-j @vkuzo @albanD @kadeng
Repository: TypeScript
Issue: Object union member functions that return never are incorrectly narrowed
Labels: Suggestion,Awaiting More Feedback

### 🔎 Search Terms

"never", "class union", "narrowing unions", "never union"

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about never

### ⏯ Playground Link

[Playground Link](https://www.typescriptlang.org/play?ts=5.3.1-rc#code/LAKAxgNghgzjAEAxA9s+BvU9vwCYFMAzVACgEoAueAO3wDd8AnDLHNgFwAtHkB3G-PwCijHoxIAiYmiZiJZVtgC+oFSFCRYCAEJRmmEGwLTyGeGrWh2ATwAO+eLoBe8ALxJU8AD6O9AblBQQgBXajB2AEtkajwiVCYSACMoJypnMhZDHGSnADpjUgzFeAB6ErZ4AD0AfmKy+CgAayh4EloGZh86ZAjcBXUs7EZ8dmDGGJy68rYaqfgYTmRgiFwaPR5+djRdRlVQIA)

### 💻 Code

```ts
class Foo {
    defoo(): never {
        throw new Error("foo error")
    }
}

class Bar {
    defoo() { }
}

type Baz = Foo | Bar;

function defooer(baz: Baz) {
    baz.defoo() 
    // type = void
    // aka (never | void)

    return baz
    // type = Baz
    // should narrow to Bar
}
```


### 🙁 Actual behavior

`baz` doesn't get narrowed after calling `.defoo()`, even though it's impossible for any value after that point to be `Foo`. This seems to happen because the type of `Baz["defoo"]` is equal to `Foo["defoo"] | Bar["defoo"]` or `() => never | void`.

### 🙂 Expected behavior

`baz` should narrow to `Bar` after calling `.defoo()` because the return type of `Foo.defoo` is `never`. 

### Additional information about the issue

_No response_
Repository: godot
Issue: Spatial Editor Freelook Jitter - Godot v4.2.beta6
Labels: topic:editor,needs testing,topic:3d

### Godot version

4.2.beta6

### System information

Godot v4.2.beta6 - Windows 10.0.22621 - GLES3 (Compatibility) - Radeon RX 580 Series (Advanced Micro Devices, Inc.; 31.0.21902.5) - Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz (12 Threads)

### Issue description

Whenever you go into freelook mode in the spatial editor (by right clicking or pressing shift+f), and you look around or move. It kind of jitters.

### Steps to reproduce

1. Open a project in this version.
2. Enter Freelook mode in the spatial editor (right click in the middle window or press shift+f)
3. Move around with WASD or look around with mouse or trackpad.

### Minimal reproduction project

N/A
Repository: PowerToys
Issue: Power RUN 无法运行
Labels: Issue-Bug,Product-PowerToys Run

### Microsoft PowerToys version

0.75.1

### Installation method

PowerToys auto-update, Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

[PowerToysReport_2023-11-16-10-40-27.zip](https://github.com/microsoft/PowerToys/files/13371759/PowerToysReport_2023-11-16-10-40-27.zip)


### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: opencv
Issue: (-215:Assertion failed) inv_scale_x > 0 in function 'resize'
Labels: category: imgproc,incomplete

### System Information

OpenCV version: 4.5.5
Operating System / Platform: Ubuntu 18.04
Compiler & compiler version: GCC 7.5.0
Build op:cmake .. -DEXECUTABLE_OUTPUT_PATH:PATH=$(pwd) -DCMAKE_INSTALL_PREFIX=$(pwd)/install -DBUILD_SHARED_LIBS=ON -DCMAKE_BUILD_TYPE=RELEASE -DOPENCV_EXTRA_MODULES_PATH=../opencv_contrib-4.5.5/modules -DBUILD_opencv_world=ON -DOPENCV_ENABLE_NONFREE=ON


### Detailed description

terminate called after throwing an instance of 'cv::Exception'
  what():  OpenCV(4.5.5) /home/zhubin/opencv-4.5.5/modules/imgproc/src/resize.cpp:4055: error: (-215:Assertion failed) inv_scale_x > 0 in function 'resize'

![image](https://github.com/opencv/opencv/assets/59795424/5146f9df-3266-4588-a44d-ad077289a60d)


### Steps to reproduce
```
cv::Mat test_main = cv::imread(image_filename);
cv::Mat test_resize(cv::Size(299, 299), CV_8UC3);
if(test_main.empty())
{
        printf("test_main.empty()\n");
}
cv::resize(test_main,test_resize,cv::Size(299,299));
```

### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [ ] I updated to the latest OpenCV version and the issue is still there
- [ ] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: flutter
Issue: Add parameter to BoxDecoration to allow gradient to work with color
Labels: c: new feature,framework,c: proposal,P3,team-framework,triaged-framework

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

I'm trying to have a `gradient` and a `color` together using a single `BoxDecoration` and while it compiles, in the docs it notes that `color` does nothing if `gradient` is specified. To overcome this, you can use nested `DecoratedBox`s or a `Stack` widget but that's messy.

### Proposal

My proposal is to add a new property to `BoxDecoration`. It's type will be an enum, with a name similar to `GradientPaintMode` with 3 possible values, `under`, `override`, `over`.

- `under` means the gradient will draw under the color (for example, if `color` is partially transparent)
- `override` is the current behavior where the color isn't painted at all
- `over` means the gradient will draw over the color (for example, if the `gradient` is partially transparent)

Alternative value names for `GradientPaintMode`: `background`, `override`, `foreground` (to keep it in line with other naming conventions).

Or, instead of having the enum be for the gradient, it could be for the color like `ColorPaintMode`.

![image](https://github.com/flutter/flutter/assets/25782944/50c7458c-969b-4608-b479-231e6046466a)
Repository: pytorch
Issue: torch.einsum is stuck in mp.Process
Labels: needs reproduction,module: multiprocessing,triaged

### 🐛 Describe the bug

When PyTorch multi-process uses Process, the Linux system will be stuck because of the fork used by default, there is no problem with Windows using spwan, and Linux set spwan can also run normally.

```python
import torch
import torch.multiprocessing as mp

def foo(i):
    print(f'begin {i}')
    x = torch.ones(2,50,10)
    torch.einsum('ijl,ikl -> ijk', x, x)
    print(f'begin {i}')

if __name__ == '__main__':
    foo(1)

    # mp.set_start_method('spwan')

    p = mp.Process(target=foo, args=(2,))
    p.start()
    p.join()
```

### Versions

2.1 linux cpu

cc @VitalyFedyunin
Repository: TypeScript
Issue: improvements for non-experimental decorator types 
Labels: Suggestion,Domain: Decorators,Awaiting More Feedback

### 🔍 Search Terms

github typescript decorator value type

### ✅ Viability Checklist

- [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [X] This wouldn't change the runtime behavior of existing JavaScript code
- [X] This could be implemented without emitting different JS based on the types of the expressions
- [X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [X] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- [X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

> This is a request to add a new utility type because TypeScript added one for decorator contexts but not for values

The `DecoratorContext` type is nice for catching all context types:

```js
function decorator(value: unknown, context: DecoratorContext) { // optionally use a more specific type.
  // ...
}
```

But for `value`, there is not a good catch-all type.

### 📃 Motivating Example


If we have a context catch all type, why not also have a value catch all type, f.e. something like :

```ts
export type DecoratedValue = Constructor | Function | ClassAccessorDecoratorTarget<object, unknown> | undefined
```

### 💻 Use Cases

1. What do you want to use this for? decorators whose code handles any value type
3. What shortcomings exist with current approaches? we have to make the catchall for value ourselves, but we don't have to do that for context
4. What workarounds are you using in the meantime? I make my own catchall (not that big a deal, but neither would making `DecoratorContext` myself be
Repository: svelte
Issue: Allow `role="separator"` as an interactive ARIA role
Labels: a11y

### Describe the bug

When creating an element with the `role` attribute with the value of "separator" and adding a `tabindex` attribute with the value of "0" and a key down event listener, I get the following errors: `A11y: noninteractive element cannot have nonnegative tabIndex value` and `A11y: Non-interactive element <span> should not be assigned mouse or keyboard event listeners.`. This is not correct according to the [Mozilla Developer Network](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/separator_role#focusable_separator) and [W3C's Aria Authoring Practices guide](https://www.w3.org/WAI/ARIA/apg/patterns/windowsplitter/).

The only fix is to ignore these issues with: `<!-- svelte-ignore a11y-no-noninteractive-element-interactions -->` and `<!-- svelte-ignore a11y-no-noninteractive-tabindex -->`

### Reproduction

https://stackblitz.com/edit/vitejs-vite-pfawto?file=Separator.svelte

### Logs

```shell
9:46:46 PM [vite-plugin-svelte] /home/projects/vitejs-vite-pfawto/src/lib/Separator.svelte:10:0 A11y: noninteractive element cannot have nonnegative tabIndex value
9:46:46 PM [vite-plugin-svelte] /home/projects/vitejs-vite-pfawto/src/lib/Separator.svelte:10:0 A11y: Non-interactive element <span> should not be assigned mouse or keyboard event listeners.
```


### System Info

```shell
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.18.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 9.4.2 - /usr/local/bin/npm
    pnpm: 8.9.2 - /usr/local/bin/pnpm
  npmPackages:
    svelte: ^4.2.3 => 4.2.3
```


### Severity

annoyance