sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: When C#'s ToString is not implemented, it still overrides GDExtension's _to_string
Labels: discussion,topic:dotnet

### Tested versions

v4.2.2.stable.mono.official [15073afe3]

### System information

Godot v4.2.2.stable.mono - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1650 (NVIDIA; 32.0.15.5612) - Intel(R) Core(TM) i5-9300H CPU @ 2.40GHz (8 Threads)

### Issue description

I was testing with overriding `_to_string` method in GDExtension class and when I attached C# script on that node, GDExtension's `_to_string` stopped working. `ToString` in C# was not overriden. When I tested the same script, but in GDScript it worked as expected, GDExtension's `_to_string` got called and printed. C# `GetNode` also can't access GDExtension's `_to_string`

I expect GDExtension `_to_string` to get called when C# script does not override it. At least to stop it from overriding C++ side
![image](https://github.com/godotengine/godot/assets/22471296/42a28559-2f29-46d6-ae49-3f0a4f841b59)


### Steps to reproduce

1. Create GDExtension class with overriden `_to_string`
2. Attach C# script to it (it needs to extend the closest to GDExtension Godot's class)
3. Try to pass itself to `GD.Print`, or try to use `to_string` from GDExtension side, it now doesn't work

### Minimal reproduction project (MRP)

[to_string_repro.zip](https://github.com/user-attachments/files/16176202/to_string_repro.zip)
Repository: node
Issue: v22.4.1 C++ addon incurs segmentation faults
Labels: node-api,v22.x

### Version

v22.4.1

### Platform

```text
Linux Debian 6.1.0-22-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.94-1 (2024-06-21) x86_64 GNU/Linux
```


### Subsystem

node-addon-api

### What steps will reproduce the bug?

Run a simple hello-world C++ wrapper addon test by following https://www.npmjs.com/package/generator-napi-module, it returns "segmentation faults" runtime error; there is no such an error for v20.15.1 and v20.14.0 which are only other two versions tested.

### How often does it reproduce? Is there a required condition?

Every time

### What is the expected behavior? Why is that the expected behavior?

No runtime error

### What do you see instead?

Segmentation faults

### Additional information

_No response_
Repository: rust
Issue: File truncation is slow on Windows 
Labels: T-libs,A-filesystem

hello, I found that the std::fs::write function is quite slow when writing to the same file, I was very surprised why this is so and then I used open options and found that if I put truncate true then that was the cause of the slowdown and then I created a function where I changed the length of the file only at the end after writing, but only if the new length of the data was smaller than the original file size, and therefore I want to ask if it is possible to apply something like this in the std::fs::write method?
Repository: pytorch
Issue: Clarify invariants established by torch.fx.passes.runtime_asserts or factor so we can have a pre-pass that reestablishes them
Labels: triaged,oncall: pt2,module: dynamic shapes

### 🐛 Describe the bug

TODO

### Versions

main

cc @anijain2305 @chauhang @penguinwu
Repository: flutter
Issue: [webview_flutter] [NavigationRequest] Add a property to tell if the navigation request is POST or GET
Labels: c: new feature,p: webview,package,c: proposal,team-ecosystem,P2,triaged-ecosystem

### Use case

Sometime we need to prevent or perform the NavigationDecision according to the HTTP method used. 
For example, I would like to prevent every POST call inside the webview. 


### Proposal

Add a property` LoadRequestMethod method `in the NavigationRequest class to inform if the url is requested with post or get method.
Repository: vscode
Issue: Accessibility issue with screen reader and vscode keep saying name of project and WSL env (program title bar value)
Labels: bug,accessibility

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No
yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.91.0
- OS Version: WSL 2 / Ubuntu 20.04 / Windows 10

Steps to Reproduce:

1. Search by Name CTRL+P

or

1. Typing a function and open paren so the intellisence / function argument appear `abc(` 
Both triggers the same very verbose info which is not required as we're already in the app.

The screen reader will say:

[File name] - [Project name] - WLS Ubuntu 20.04 - Visual Srudio Code - Document

**And than will repeat that a second time** with "Application" instead of "Document".

And finally "Search file by name".

It's the same for the function arguments, it's saying all of this twice before finally starting to announce the arguments.

Basically the screen reader says the same as when the vscode application gets the main OS focus with the following difference:

When I ALT+TAB to vscode or return from a different virtual desktop it will say all info, but instead of "Document" will say "Desktop 2" and repeat with the "Application"

When ALT-Tabing I'm all good / can live with what the screen reader is saying.

But for CTRL+P and also for intellisence, is there a way to remove this long and superflus info?

Because I either have to wait to get the function arguments or the confirmation that CTRL+P is open, and if I hit a key to skip, I than need to redo the operation.

Thank you.
Repository: vscode
Issue: Move left buttons in working changes window
Labels: 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. -->

tldr: I suggest to move left buttons like 'Stage Change' or 'Revert Change' in working view.

To open working changes window you should click on "added lines" at first on left side of screen. So then you can 'stage' or 'revert' your changes. But these buttons are located on the right side of the screen and you should move over right the entire screen to them and back left to open next change. It's quite too much movements.

![Screenshot from 2024-07-11 17-21-58](https://github.com/microsoft/vscode/assets/7109350/0793d970-3f7e-4cb4-94a0-601ea4c34125)
Repository: godot
Issue: Editor window resizing on Wayland doesn't work (GNOME with tiled window)
Labels: bug,platform:linuxbsd,regression,topic:gui

### Tested versions

- Reproducible in: 4.3-beta3
- Not reproducible in: 4.3-beta2

### System information

Fedora 40 - Godot 4.3-beta3 (custom built 64 bit  with c# enabled)- Vulkan (forward +) - Wayland - AMD Ryzen™ 7 6800HS with Radeon™ Graphics × 16

### Issue description

A bunch of 
`platform/linuxbsd/wayland/wayland_thread.cpp:2053 - Parameter "ws" is null.`
message appears in the editor output, and I cannot resize the editor window anymore. 
I don't know what else is broken, I'm still testing, but this "feature" :smile: arrived with pr #94021.

### Steps to reproduce

I just compiled a custom version from the fresh Godot 4.3-beta3, and starting the editor the problem appeared.
This issue also appeared on the released binaries.

### Minimal reproduction project (MRP)

I don't know if this thing appears on Ubuntu or other Linux distribution. But on Fedora 40 (workstation) just download the binary from Godot builds.
Repository: deno
Issue: Deno panics when detailed coverage output is piped to quiet grep on macos terminal
Labels: bug


Steps to reproduce:

```
% deno test -A --coverage

...

% deno coverage --detailed | grep '100[.]'

cover file:///... ... 100.000% (1/1)
cover file:///... ... 100.000% (1/1)
cover file:///... ... 100.000% (28/28)

% deno coverage --detailed | grep -q '100[.]'


============================================================
Deno has panicked. This is a bug in Deno. Please report this
at https://github.com/denoland/deno/issues/new.
If you can reliably reproduce this panic, include the
reproduction steps and re-run with the RUST_BACKTRACE=1 env
var set and include the backtrace in your report.

Platform: macos x86_64
Version: 1.45.0
Args: ["deno", "coverage", "--detailed"]

thread 'main' panicked at library/std/src/io/stdio.rs:1118:9:
failed printing to stdout: Broken pipe (os error 32)
stack backtrace:
   0: _rust_begin_unwind
   1: core::panicking::panic_fmt
   2: std::io::stdio::_print
   3: <deno::tools::coverage::reporter::DetailedCoverageReporter as deno::tools::coverage::reporter::CoverageReporter>::report
   4: deno::tools::coverage::cover_files::{{closure}}
   5: deno::spawn_subcommand::{{closure}}
   6: <deno_unsync::task::MaskFutureAsSend<F> as core::future::future::Future>::poll
   7: tokio::runtime::task::raw::poll
   8: deno::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
```
Repository: rust
Issue: `ast::mut_visit::MutVisitor` and `ast::visit::Visitor` do not have corresponding methods for all their methods
Labels: C-cleanup,T-compiler,E-medium,A-technical-debt,A-ast

In contrast to the MIR mut and immut visitors

https://github.com/rust-lang/rust/blob/c92a8e4d4d7e8da53aa05309ef8d4fac2c9af52f/compiler/rustc_middle/src/mir/visit.rs#L1235-L1236

which are generated from a single macro, and are thus exactly the same except for mutation, the ast visitors are each handwritten. Their method naming scheme doesn't even match up, so changing from a `Visitor` to a `MutVisitor` requires extensive changes.

### Work items

* [x] Adjust names so everything has the `visit_*` vs `walk_*` naming scheme
* [ ] Give every `MutVisitor::visit_*` method a corresponding `flat_map_*` method. https://github.com/rust-lang/rust/labels/E-medium
    * we can make it so implementors can override either `visit_foo` or `flat_map_foo` without there being problems. The `walk_bar` functions must invoke `flat_map_foo`, so that they can pick up on more/fewer items being produced. So `walk_flat_map_foo` (which only ever maps to a single output element) needs to invoke `visit_foo`, not `walk_foo`. Otherwise overriding `visit_foo` will do nothing.
    * This should be using macros similar to what https://github.com/rust-lang/rust/pull/127371 did, so you don't repeat yourself
* [ ] ~~(Optional): move all the `walk_` functions to defaulted methods on the trait (not sure this should be done, discuss on zulip first!)~~ discussed, should not be done
* [ ] Give every `MutVisitor::visit_*` method a corresponding `Visitor` method and vice versa https://github.com/rust-lang/rust/labels/E-easy
* [ ] Create a macro that generates both visitors, including the `walk_` functions in one go, just like with the MIR visitors https://github.com/rust-lang/rust/labels/E-hard

### Previous work

* https://github.com/rust-lang/rust/pull/127524

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"obeis"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: angular
Issue: [i18n] Merge generated file with existing file using `ng extract-i18n` 
Labels: area: i18n

### Which @angular/* package(s) are relevant/related to the feature request?

localize

### Description

When you generate a translation file (XLF, JSON, ARB or XMB) using `ng extract-i18n` you get a new file without any target translation. If you already have a translation file, you would have to manually merge your existing file with the generated one.

This solution is inadequate for large scale project and often involves writing a custom merge tool or spending a lot of time doing it manually, leading to errors and/or oversights.

### Proposed solution

When running `ng extract-i18n`, if the target file already exists, instead of creating a new file, update the existing one to:
- Remove unused ID (this could be disabled by default for safety)
- Add new ID without target
- Update metadata (ID, description and meaning) and keep target

### Alternatives considered

We can use the following plugin but it only support XLF format: https://github.com/daniel-sc/ng-extract-i18n-merge

For existing i18n features to be useful in a real project, it's missing the merge operation, which is why I think it needs to be integrated natively.
Repository: pytorch
Issue: Ensuring caching is disabled on einops from Dynamo
Labels: high priority,triaged,actionable,ezyang's list,oncall: pt2,module: dynamic shapes

### 🐛 Describe the bug

It should be permissible to change the behavior of `hash(symint)` to just cause a specialization. However, this causes previously OK to be dynamic code with einops to stop working, because einops is specifically looking for the TypeError here https://github.com/arogozhnikov/einops/blob/6181e1e95dc58c00a3143c1726da1c6ee0463164/einops/einops.py#L237

Need to figure out how to force uncached behavior here....

Sample stack:

```
torch/_dynamo/variables/builder.py:1900 in wrap_fx_proxy_cls
torch/_dynamo/utils.py:1815 in get_fake_value
torch/_dynamo/utils.py:1311 in wrap_fake_exception
torch/_dynamo/utils.py:1816 in <lambda>
torch/_dynamo/utils.py:1933 in run_node
einops/einops.py:591 in rearrange
einops/einops.py:523 in reduce
einops/einops.py:234 in _apply_recipe
torch/__init__.py:518 in __hash__
torch/__init__.py:380 in __int__
torch/fx/experimental/sym_node.py:380 in int_
torch/fx/experimental/sym_node.py:386 in guard_int
torch/fx/experimental/recording.py:245 in wrapper
torch/fx/experimental/symbolic_shapes.py:5130 in evaluate_expr
torch/fx/experimental/symbolic_shapes.py:5292 in _evaluate_expr
torch/fx/experimental/symbolic_shapes.py:4935 in _maybe_guard_rel
torch/fx/experimental/symbolic_shapes.py:5479 in _refine_ranges
torch/fx/experimental/symbolic_shapes.py:4850 in _set_replacement
torch/_logging/_internal.py:1085 in trace_structured
```

Internal xref: https://fb.workplace.com/groups/1075192433118967/posts/1462584834379723/

### Versions

main

cc @gchanan @zou3519 @kadeng @msaroufim @chauhang @penguinwu @bobrenjc93 @anijain2305
Repository: godot
Issue: Button hover does not work when you run a scene with Input.mouse_mode = Input.MOUSE_MODE_CONFINED in _ready()
Labels: bug,topic:input

### Tested versions

4.2.2 stable

### System information

Xubuntu 24.04

### Issue description

Case 1: When you run a scene with `Input.mouse_mode = Input.MOUSE_MODE_CONFINED` in _ready() and hover a button with the mouse cursor nothing happen. It works again if you change the mode.

Case 2: But if you do not change the mouse_mode at the start and do it in the _process() after it works well.

Case 3: If you wait a frame at the start it works well. This workaround worked https://github.com/godotengine/godot/issues/84389#issuecomment-2020277165

Same when you run the entire project.

Same when you export the entire project.

### Steps to reproduce

- Create a new control scene
- Add Button child
- Add a script to the control
```
extends Control


# Called when the node enters the scene tree for the first time.
func _ready():
        # un/comment the next lines to test the different cases
        #await get_tree().process_frame
	Input.mouse_mode = Input.MOUSE_MODE_CONFINED
	pass # Replace with function body.


# Called every frame. 'delta' is the elapsed time since the previous frame.
func _process(delta):
	if Input.is_action_just_pressed("ui_cancel"):
		get_tree().quit()
		
	if Input.is_action_just_pressed("ui_select"):
		if Input.mouse_mode == Input.MOUSE_MODE_CONFINED:
			Input.mouse_mode = Input.MOUSE_MODE_VISIBLE
		else:
			Input.mouse_mode = Input.MOUSE_MODE_CONFINED
	pass
```

### Minimal reproduction project (MRP)

[NewProject.zip](https://github.com/user-attachments/files/16181427/NewProject.zip)
Repository: rust
Issue: NixOS build should be tested in CI
Labels: T-infra,O-NixOS,A-CI

rustc bootstrap contains a lot of code specifically for making builds work smoothly on nixos... however, none of this code seems to be tested by CI.

recently, it seems that the addition of libstdc++ as a dependency of rustc has broken builds on nixos.  i think stage1 should be built for nixos as part of CI to prevent this from happening in the future.
Repository: go
Issue: encoding/xml: accepts XML with no space between attributes
Labels: NeedsInvestigation

### Go version

1.22.5 (this is from `pkg.go.dev`)

### Output of `go env` in your module/workspace:

```shell
Whatever is on `pkg.go.dev` as of the filing of this issue
```


### What did you do?

https://go.dev/play/p/_xXpPKU-YWQ

```go
package main

import "encoding/xml"

func main() {
	err := xml.Unmarshal([]byte(`<a b="c" c="d"/>`), new(interface{}))
	if err != nil {
		panic("well-formed XML rejected")
	}
	err = xml.Unmarshal([]byte(`<a b="c"c="d"/>`), new(interface{}))
	if err == nil {
		panic("missing space before attribute name accepted")
	}
}
```

### What did you see happen?

Unmarshaling the XML succeeds, even though there is a missing space between `b="c"` and `c="d"`.

### What did you expect to see?

Unmarshaling `<a b="c"c="d"/>` fails.  libxml2 correctly rejects this.
Repository: godot
Issue: Array created in Editor for PackedScene is shared by all instances
Labels: bug,topic:core

### Tested versions

- Reproducible in: 4.0.stable, 4.2.2.stable, 4.3.beta3

### System information

Windows 10 - Godot 4.2.2.stable

### Issue description

Arrays created in the editor for a PackedScene will be shared by all instances of that PackedScene.



### Steps to reproduce

1. Create a PackedScene which declares an exported array.
2. Edit the array in the editor and save the scene.
3. Instantiate this PackedScene multiple times somewhere else.
4. Edit the array of one of the packed scenes. These updates will appear in all instances of the PackedScene since all instances share the same array.

### Minimal reproduction project (MRP)

[Playground - Copy.zip](https://github.com/user-attachments/files/16181472/Playground.-.Copy.zip)
Repository: go
Issue: encoding/xml: does not require whitespace before processing instruction value
Labels: NeedsInvestigation

### Go version

1.22.5 (this is from `pkg.go.dev`)

### Output of `go env` in your module/workspace:

```shell
Whatever pkg.go.dev uses when this issue is filed
```


### What did you do?

https://go.dev/play/p/rzV-FdleVIV

```go
package main

import "encoding/xml"

func main() {
	err := xml.Unmarshal([]byte(`<?a /b?><a/>`), new(interface{}))
	if err != nil {
		panic("well-formed XML rejected")
	}
	err = xml.Unmarshal([]byte(`<?a/b?><a/>`), new(interface{}))
	if err == nil {
		panic("missing space before processing instruction value accepted")
	}
}
```

### What did you see happen?

`<?a/b?><a/>` is parsed successfully.

### What did you expect to see?

Error because `<?a/b?>` is not a well-formed processing instruction.  There must be whitespace between the processing instruction target and value.
Repository: neovim
Issue: vim.lsp.util.open_floating_preview should recycle its buffer(s)
Labels: enhancement,lsp,editor-state

`vim.lsp.util.open_floating_preview` creates a new buffer each time it's called, which can drive up the buffer numbers pretty aggressively, esp. for diagnostics, where the window and buffer tend to be pretty transient. Can some logic be added to allow an existing buffer to be passed through that will be overwritten instead of a fresh one being created?

https://github.com/neovim/neovim/blob/45b7a2c50335e1943a36715101e40eda5a1423f3/runtime/lua/vim/lsp/util.lua#L1606
Repository: pytorch
Issue: torch.export.export re-export preserving metadata for output node
Labels: oncall: export

### 🐛 Describe the bug

Currently the metadata in output node is not preserved when re-exporting the model, you can re-enable `test_re_export_preserve_handle` in https://github.com/pytorch/pytorch/pull/129287 to confirm.

### Versions

main branch

cc @avikchaudhuri @gmagogsfm @zhxchen17 @tugsbayasgalan @angelayi @suo @ydwu4 @penguinwu
Repository: rust
Issue: [bootstrap]: fix stage1 build on nixos and improve download robustness
Labels: T-bootstrap,C-bug,O-NixOS,C-discussion

sorry for not formatting this as a PR, but i'm in the middle of drafting another PR, and i don't think i can split this into its own branch without making that pr unmergable.

this fixes an error where building stage1 on nixos would produce a `rustc` binary that is dynamically linked to `libstdc++`, but this dependency does not get patched, so the executable cannot be run without using `LD_LIBRARY_PATH` hacks.

```diff
diff --git a/src/bootstrap/src/core/download.rs b/src/bootstrap/src/core/download.rs
index a7f4bb0cf..2fa47cc6c 100644
--- a/src/bootstrap/src/core/download.rs
+++ b/src/bootstrap/src/core/download.rs
@@ -154,6 +154,7 @@ fn fix_bin_or_dylib(&self, fname: &Path) {
                     zlib
                     patchelf
                     stdenv.cc.bintools
+                    stdenv.cc.cc.lib
                 ];
             }
             ";
@@ -224,6 +225,7 @@ fn download_http_with_retries(&self, tempfile: &Path, url: &str, help_on_error:
             tempfile.to_str().unwrap(),
             "--retry",
             "3",
+            "--retry-all-errors",
             "-SRf",
         ]);
         // Don't print progress in CI; the \r wrapping looks bad and downloads don't take long enough for progress to be useful.
```
Repository: vscode
Issue: Search editor shows the wrong results when running multiple
Labels: bug,search,confirmed

Does this issue occur when all extensions are disabled?: Yes

- VS Code Version: 1.91.1
- OS Version: MacOS 13.6.7

Steps to Reproduce:

1. Open a large workspace.
2. Set `search.mode` to "newEditor".
3. Quickly do a project-wide search for two different things. Make sure they are running concurrently. When the search finishes for one, check the results of the other search editor. The search results in both editors are the same. It seems to match the last search completed (or maybe it's the results of the search in focus when it competes).

I've been noticing this for at least a few months now, so it's not related to the newest version. I can also duplicate this in the Insiders build.
Repository: pytorch
Issue: Build Triton for aarch64
Labels: module: cuda,module: ci,triaged,enhancement,module: arm

### 🚀 The feature, motivation and pitch

Currently, Triton is not being build for `aarch64` that make `torch.compile` unavailable on any ARM machine including Grace-Hopper and Graviton+GPU.

### Additional context

My experiments show that LLVM also needs to be built in manylinux container, in spite of its `aarch64` binaries being available. The reason for that is GCC conflicts with pre-built package.

cc @ptrblck @msaroufim @seemethere @malfet @pytorch/pytorch-dev-infra @snadampal @milpuz01 @atalman