sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: When upgaring C# project -> add "EnableDynamicLoading" to .csproj
Labels: bug,topic:editor,needs testing,topic:dotnet

### Godot version

Godot4 Beta2 net6

### System information

Windows10, Vulkan, RTX2080

### Issue description

When upgrading an existing C# project to Godot4,
"\<EnableDynamicLoading>true</EnableDynamicLoading\>" wont get added automatically, which seems to be prerequisite to run c# scripts in general. Else Godot wont be able to find the classes.
This should be done automatically i think.

### Steps to reproduce

Have a C# project without "EnableDynamicLoading" enabled in .csproj.

### Minimal reproduction project

_No response_
Repository: godot
Issue: Texture2D.GetSize() returns a Vector2 instead of a Vector2i
Labels: enhancement,discussion,topic:2d

### Godot version

v4.0.beta2.mono.official [f8745f2f7]

### System information

Windows 10 64-bit

### Issue description

Texture2D.GetSize() returns a Vector2 instead of the expected Vector2i.

### Steps to reproduce

N/A

### Minimal reproduction project

N/A
Repository: flutter
Issue: Documenation example anchor links are obstructed
Labels: framework,f: material design,d: api docs,P2,team-design,triaged-design

I'm not sure how to capture a screenshot that includes the mouse pointer, but if you go to https://api.flutter.dev/flutter/material/DataTable-class.html#material.DataTable.2 and attempt to click the example anchor you can see that the activation area is obstructed. As shown in the screenshot, it appears the obstruction may be the `longSnippet2` div.

When attempting to use the anchor, I thought it didn't work at all at first, but I discovered there is an area above the anchor image and also to the right of it where it can be activated.

![image](https://user-images.githubusercontent.com/797824/193427684-3bca8699-dca9-4c23-97d1-d8d094c1ee73.png)
Repository: go
Issue: cmd/gofmt: nested list reformatting removes explicitly-written hierarchies in existing comments
Labels: NeedsInvestigation

When saving some existing complex comments in some existing Go code that used nested lists inside a preformatted text block, I was quite astonished to find the list was flattened and the hierarchical information thus stripped.

The documentation states that nested lists aren't supported, which is fine, the rationale for the new syntax during the proposal phase made sense to me (at least as far as I was keeping up), but the formatter should leave the nested lists it finds well alone, especially as the author's original intent was already "preformatted block". It's the job of the renderer to fail to render nested lists if they're not supported, not the job of the formatter to strip valuable information on the presumption that the nested list should not have been there in the first place.

For anyone else astonished by this, I have been playing with two specific workarounds (I'm sure there are more):

Prepending `>` to the start of each line, markdown-quote-style. This fails to render, but rendering is not a problem I actually have, and the intent is very clear, so this is what I'm trying out for now:
```
> - foo
>   - bar
>     - baz
>   - qux
> - yep
```

Putting a non-list line at the start of the comment also inhibits the auto-flattening:
```
  Nobork:
  - foo
    - bar
      - baz
    - qux
  - yep
```

### What version of Go are you using (`go version`)?

<pre>
$ go version go1.19 darwin/arm64

</pre>

### Does this issue reproduce with the latest release?

Yes

### What did you do?

I saved a file with an existing comment that looked like this (with a few levels deeper)

```
Here is a hierarchical explanation using nested lists of something complex
that nested lists were a good way to demonstrate:

  - foo
    - bar
      - baz
    - qux
  - yep
```


### What did you see instead?

```
Here is a hierarchical explanation using nested lists of something complex
that nested lists were a good way to demonstrate:

  - foo
  - bar
  - baz
  - qux
  - yep
```
Repository: vscode
Issue: Clarification of acceptable use cases in the Visual Studio Code license terms
Labels: under-discussion,license

From the Microsoft Software License Terms for Microsoft Visual Studio Code:

> a. General. You may use any number of copies of the software to develop and test your applications, including deployment within your internal corporate network.
>
> b. Demo use. The uses permitted above include use of the software in demonstrating your applications.

The initial interpretation I'm getting from this is that Visual Studio Code can only be used for development, testing, and demonstration of applications. So what if I happened to really like VSCode as a general purpose text editor and decided to write a book in it? How about a personal to-do list? What about all of the other uses people have for a text editor? Would these use cases be against the license terms?

Is this intentional? Is VSCode really supposed to be used only for software development, testing, and demonstration, and that's it? If not, it might be helpful to relax the terms somewhat so that people who stick to the license terms for dear life (like me) are happy.

(For now I'm sticking to the initial interpretation of the terms and am only using VSCode for the use cases specifically spelled out in the license agreement.)
Repository: godot
Issue: Using ``[url=...]`` breaks ``get_character_paragraph`` and ``get_character_line``
Labels: bug,topic:gui

### Godot version

4.0.beta2

### System information

Linux

### Issue description

``RichTextLabel`` fails to account for the characters taken up by the URL (I think) when ``[url=...]`` tags are used.  This causes ``get_character_paragraph`` and ``get_character_line`` to return incorrect values when several long URLs are used.

### Steps to reproduce

Please see https://github.com/nerdbeard/RichTextLabel-offset/blob/main/anchor.gd for a minimal example.

### Minimal reproduction project

https://github.com/nerdbeard/RichTextLabel-offset
Repository: PowerToys
Issue: ocr in chinese languages adapt issue
Labels: Needs-Triage

### Description of the new feature / enhancement

I wish the future powerToy can provide `A replace all blank place switch`.

### Scenario when this would be used?

  in English, words are separated by white space, but in Chinese languages, words are only separated by word self,  when I use powerToy to check the screen of  Chinese character from a video or another, I need to replace all white space with an empty strings,  it's troublesome.
incorrect Chinese : 日 照 香 炉 生 紫 烟
right way: 日照香炉生紫烟

### Supporting information

when using powertoy to recognize an Chinese ppt from video,you will find it
Repository: godot
Issue: Window resizing temporarily exhibits black areas when increasing the window size
Labels: enhancement,topic:rendering,confirmed

### Godot version

4.0 beta 2

### System information

Win11 22H2, Intel UHD Graphics 730, 31.0.101.3413

### Issue description

调整窗口时
如果持续调整窗口
被调整的这段区域是一片黑
只有停止的时候才会被显示

When adjusting windows
If you continue to adjust the window
The adjusted area is black
It will be displayed only when it stops

---
我觉得可能和我之前发的
No response when resizing the panel (调整面板大小时未响应) #66498
https://github.com/godotengine/godot/issues/66498
有关
(补充了命令行的报错信息)
那个是影响了预览窗口就会未响应

I think it might be
No response when resizing the panel # 66498
https://github.com/godotengine/godot/issues/66498
relevant
(Added the error message from the command line)
The preview window will not respond if it is affected

---
我在用云电脑的时候 (RTX3060, 没有核显) 没有以上两个问题
所以我觉得可能是Godot对核显的支持不太好
或者反过来

When I use the cloud computer (RTX3060, no check and display), the above two problems do not exist
So I think it may be that Godot doesn't support the nuclear display very well
Or vice versa

---
(Use Baidu Translation)

### Steps to reproduce

Uploading 2022-10-02 11-25-09.mp4…



### Minimal reproduction project

本机
Native

https://user-images.githubusercontent.com/72609054/193436705-284b70d2-0cd7-4ca7-8d66-1c82c8ff8b98.mp4
---
云电脑 (RTX3060)
Cloud computer (RTX3060)

https://user-images.githubusercontent.com/72609054/193436699-c387f3ac-4743-4392-8bc7-ff57a8d61f6b.mp4
Repository: rust
Issue: Mock environment testing for bootstrap
Labels: A-testsuite,C-enhancement,T-bootstrap,A-technical-debt

There are lots of config knobs in bootstrap, and it is hard to understand how they interact. Consider two recent examples off the top of my head:

* https://github.com/rust-lang/rust/pull/101833#discussion_r984872396
    * Broke the flag `is_rust_llvm`
* https://github.com/rust-lang/rust/pull/101072#discussion_r956528035
    * Implemented the aforementioned flag
    * (Nearly) broke the flag `llvm_from_ci`
    * Caught in review by someone who knew the implementation details of that flag

We should really catch these issues in tests, not review, and avoid relying too much on specific reviewers who know parts of the code.

Since bootstrap does I/O and interacts with external tooling, it is inherently difficult to test. The strategy I know involves mocking out the build environment (enough to make tests run in <~1s). From there you can record what the implementation does and take two approaches for the test:

* Assert on specific conditions, like "the flag `-D FOO` was passed to LLVM cmake" or "foo/bar/baz was moved to foo/bar/quux".
* Record everything in a golden file for some "representative" set of configurations. You can update these with `--bless`. This helps guard against unexpected behavior changes.

I think both are helpful. In fact, combining the two is exactly what we do in ui tests.

cc @jyn514 @Mark-Simulacrum
Repository: react
Issue: eslint-plugin-react-hooks: lint rule to enforce that `useMemo` returns a value
Labels: Type: Feature Request,Component: ESLint Rules

Nothing prevents developers from calling `useMemo` without a `return`:

```ts
import { useMemo } from "react";

useMemo(() => {
    console.log("Yippee!");
}, []);
```

[[TypeScript playground showing no errors](https://www.typescriptlang.org/play?#code/JYWwDg9gTgLgBAbzgVwM4FMCy6QTgXzgDMoIQ4AiKdAQwGMYKBuAWACh20scIAKXgJRwAvAD5E7OFLh0IAO1QQANugB0SiAHNeFAJrAwYdOgCEFAazb4ANHADaAXQtA)]

Calling `useMemo` without a returned value is somewhat equivalent to calling `useEffect` without a returned value. Judging by the few times I've seen it happen, it's likely a case of a developer either confusing the two hooks or forgetting to `return` the memoized value.

Suggestion: can we add a lint rule to flag `useMemo` calls that don't definitely return a value? It could have a _suggestion_ fixer to switch to `useEffect`.
Repository: godot
Issue: Popup not respecting exclusive
Labels: documentation,topic:gui

### Godot version

v4.0-beta2_mono

### System information

Windows 10

### Issue description

The documentation says: 

Popups are sub-windows that don't show as separate windows in system's window manager's window list and will send close request when anything is clicked outside of them (unless [exclusive](https://docs.godotengine.org/en/latest/classes/class_window.html?highlight=window#class-window-property-exclusive) is enabled)

But even with exclusive set to true the popup closes when clicked outside.

### Steps to reproduce

1. Add a popup - like PopupMenu - node
2. Set "Exclusive" to true
3. Show the popup using one of the popup_* methods
4. Click outside of the popup

### Minimal reproduction project

[ExclusivePopup.zip](https://github.com/godotengine/godot/files/9691967/ExclusivePopup.zip)
Repository: godot
Issue: Executing `OS.set_window_mouse_passthrough` crashes Godot
Labels: bug,platform:linuxbsd,topic:porting,crash

### Godot version

3.6.beta.custom_build. 4d4c6c187 also 4.0 beta 14

### System information

Ubuntu 22.04 - Nvidia GTX 970, Gnome shell 42 X11

### Issue description

When executing
```
	var temp_variable46 = PoolVector2Array([Vector2(4582.095215, -8184.232422), Vector2(-6349.516113, -3290.224609), Vector2(-4122.603516, -9989.516602), Vector2(86.708069, 4782.494141), Vector2(0.528031, 0.849225), Vector2(9923.588867, -8939.932617), Vector2(-4111.895996, -8778.6875), Vector2(-0.535473, 0.844552), Vector2(-993.892578, 1047.707764), Vector2(0.803347, 0.595511), Vector2(-2124.481689, -8147.757324), Vector2(0.512661, -0.858591), Vector2(-5681.995605, 9009.335938), Vector2(2022.489258, -4121.172852), Vector2(0.962892, 0.269887), Vector2(-0.801489, -0.59801), Vector2(5092.568359, -8187.380371), Vector2(-4371.64502, 543.010254), Vector2(4274.128906, 4509.780273), Vector2(4130.637695, -9446.897461), Vector2(0.912633, 0.408781), Vector2(0.688457, -0.725277), Vector2(-8882.805664, 7725.44043), Vector2(285.182007, -754.191895), Vector2(6239.073242, 4191.052734)])
	OS.set_window_mouse_passthrough(temp_variable46)
```
with Godot 4
```
	var temp_variable_f530806 = PackedVector2Array([Vector2(0.88047856092453, 0.47408586740494), Vector2(-9400.484375, 8671.0693359375), Vector2(-6969.140625, 3061.0810546875), Vector2(-0.14871756732464, -0.98887968063354), Vector2(-0.80392795801163, 0.59472668170929), Vector2(8797.4248046875, 5097.203125), Vector2(2096.00561523438, -2727.16455078125), Vector2(-1280.58435058594, -3182.6103515625), Vector2(-0.9998933672905, 0.01460513472557), Vector2(9280.626953125, 8921.626953125), Vector2(6162.91748046875, 9981.0517578125), Vector2(-9654.8974609375, 9465.5107421875), Vector2(-0.95531040430069, 0.29560446739197), Vector2(-0.01638326607645, 0.99986577033997), Vector2(4711.69970703125, -6653.04931640625), Vector2(-8311.0380859375, 4318.837890625), Vector2(-0.32173463702202, 0.94682985544205), Vector2(-0.69657826423645, 0.71748077869415), Vector2(0, -1), Vector2(-4111.56005859375, 3312.28125), Vector2(5357.8271484375, -6186.0927734375), Vector2(-1221.62219238281, 5621.5537109375), Vector2(0.51378482580185, -0.85791903734207), Vector2(8485.75390625, 1752.98693847656), Vector2(0.99965840578079, -0.02613575384021)])
	var temp_variable_f530807 = 0
	DisplayServer.window_set_mouse_passthrough(temp_variable_f530806,temp_variable_f530807)
```

Godot crashes:
```
[xcb] Unknown sequence number while processing queue
[xcb] You called XInitThreads, this is not your fault
[xcb] Aborting, sorry about that.
godots: ../../src/xcb_io.c:278: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Aborted (core dumped)
```


This example was found by Godot fuzzer - [Qarminer](https://github.com/qarmin/Qarminer), so it is quite unlikelly that this code could be used in real project, but still this should be handled gracefully.


### Steps to reproduce

Above

### Minimal reproduction project

_No response_
Repository: PowerToys
Issue: 快速打开特定路径
Labels: Idea-Enhancement,Product-PowerToys Run,Needs-Triage

### Description of the new feature / enhancement

使用关键字直接打开一个或者多个特定常用路径，比如在powertoys run中输入关键字F,它会列出你希望快速打开的路径列表，
然后你可以通过鼠标或者键盘选择你要直接打开的路径。

### Scenario when this would be used?

快速打开特定路径，有些路径比较深,，比如C:\Program Files\PowerToys\modules\AlwaysOnTop，这样一步一步打开太慢了，如果能使用快捷按键就能拿很方便进入这个目录

### Supporting information

_No response_
Repository: godot
Issue: Cannot close Godot, when AudioServer is locked
Labels: bug,topic:audio

### Godot version

3.6.beta.custom_build. 4d4c6c187

### System information

Ubuntu 22.04 - Nvidia GTX 970, Gnome shell 42 X11

### Issue description

After executing 
```
AudioServer.lock()
```
attempt to close Godot freeze app here
```
Thread 1 "godot" received signal SIGINT, Interrupt.
__futex_abstimed_wait_common64 (private=128, cancel=true, abstime=0x0, op=265, expected=8592, futex_word=0x7fffcd8aa910) at ./nptl/futex-internal.c:57
57	./nptl/futex-internal.c: No such file or directory.
(gdb) backtrace
#0  __futex_abstimed_wait_common64 (private=128, cancel=true, abstime=0x0, op=265, expected=8592, futex_word=0x7fffcd8aa910) at ./nptl/futex-internal.c:57
#1  __futex_abstimed_wait_common (cancel=true, private=128, abstime=0x0, clockid=0, expected=8592, futex_word=0x7fffcd8aa910) at ./nptl/futex-internal.c:87
#2  __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x7fffcd8aa910, expected=8592, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=128)
    at ./nptl/futex-internal.c:139
#3  0x00007ffff7af66a4 in __pthread_clockjoin_ex (threadid=140736641803840, thread_return=0x0, clockid=0, abstime=0x0, block=<optimized out>) at ./nptl/pthread_join_common.c:105
#4  0x0000000005118e77 in std::thread::join() ()
#5  0x0000000004c970ec in Thread::wait_to_finish (this=0x7fffffffdad0) at core/os/thread.cpp:106
#6  0x0000000002b7fff2 in AudioDriverPulseAudio::finish (this=0x7fffffffda90) at drivers/pulseaudio/audio_driver_pulseaudio.cpp:664
#7  0x00000000045e92d3 in AudioServer::finish (this=0x9e2c170) at servers/audio_server.cpp:1058
#8  0x00000000018c5d98 in Main::cleanup (p_force=false) at main/main.cpp:2519
```

### Steps to reproduce

- Run project from command line

### Minimal reproduction project
[rrr.zip](https://github.com/godotengine/godot/files/9693290/rrr.zip)
Repository: terminal
Issue: Improve `file://` hyperlinks support - local/remote hostname
Labels: Issue-Feature,Area-UserInterface,Product-Terminal,Priority-3

# Description of the new feature/enhancement

Currently, Windows Terminal supports the following `file://` URI patterns:

- `file:///C:/SomeDir/SomeFile.txt`
- `file://localhost/C:/SomeDir/SomeFile.txt`

The following patterns are rejected with a *"This link type is currently not supported"* message:

- `file://wsl$/Ubuntu/SomeDir/SomeFile.txt` 
- `file://remote_host/SomeDir/SomeFile.txt`
- `file://local_hostname/SomeDir/SomeFile.txt`

Please add support for these cases. Note that [the hyperlinks (OSC 8) spec](https://gist.github.com/egmontkob/eb114294efbcd5adb1944c9f3cb5feda) requests for the hostname to be present in file URIs.

# Proposed technical implementation details

The following justification is provided in the code:

https://github.com/microsoft/terminal/blob/54dc2c4432857919a6a87682a09bca06608155ed/src/cascadia/TerminalApp/TerminalPage.cpp#L2304-L2309

After testing with `ShellExecuteEx` (more precisely with `Process.Start` with `UseShellExecute` in .NET), I noticed the following:
- Remote hostnames (including `wsl$`) are supported just fine by the shell
- The *local hostname* results in the following error: *"The system cannot find the file specified"*

Therefore, I think the Windows Terminal should:
- Substitute the hostname in the URI with `localhost` if it happens to match the local hostname
- Maybe also support the FQDN?
- Try to open URIs with a remote hostname as-is

---

This relates to #7699 and #5001.

See also the discussion in https://github.com/BurntSushi/ripgrep/issues/665 for the problems this feature would solve.

Another example of a really useful usage this would enable would be oh-my-posh WSL links:

![image](https://user-images.githubusercontent.com/7913492/193453435-40869283-4aa0-4a97-bcc2-a2828ef36e74.png)
Repository: neovim
Issue: Clickable and customizable extmark
Labels: enhancement,mouse,marks

### Feature already in Vim?

No

### Feature description

Follow the sign column feature request.
Now, extmark can only show information, can't interact with it. It's awesome if we can interact extmark.

Scenarios:
Lsp Codelens
- Show all references
<img width="1068" alt="image" src="https://user-images.githubusercontent.com/8556349/193453568-212f366a-8157-4c15-8617-6bf1f715934c.png">
<img width="1025" alt="image" src="https://user-images.githubusercontent.com/8556349/193453632-c52f7770-17e1-47df-8af7-6cd1e4cb5f0f.png">

- Start or debug
<img width="677" alt="image" src="https://user-images.githubusercontent.com/8556349/193453528-f4e009bc-225d-4679-a9f3-d7bb346b9682.png">
Repository: rust
Issue: Overflow when deriving Clone on a struct with a recursive GAT
Labels: A-trait-system,A-associated-items,C-bug,T-types,fixed-by-next-solver,A-GATs

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code:

```rust
trait Trait: Clone {
    type Type<T: Clone>: Clone;
}

#[derive(Clone)]
struct Struct<T: Trait>(Option<T::Type<Self>>);

// impl<T: Trait> Clone for Struct<T> {
//     fn clone(&self) -> Self {
//         Self(self.0.clone())
//     }
// }
```

I expected the derive to happen successfully without issue, like the manual implementation that I commented out.

Instead the derive resulted in an overflow error.

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.66.0-nightly (57f097ea2 2022-10-01)
binary: rustc
commit-hash: 57f097ea25f2c05f424fc9b9dc50dbd6d399845c
commit-date: 2022-10-01
host: x86_64-unknown-linux-gnu
release: 1.66.0-nightly
LLVM version: 15.0.2
```

<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Backtrace</summary>
<p>

```
error[E0275]: overflow evaluating the requirement `<T as Trait>::Type<Struct<T>>: Clone`
   --> src/lib.rs:6:25
    |
6   | struct Struct<T: Trait>(Option<T::Type<Self>>);
    |                         ^^^^^^^^^^^^^^^^^^^^^
    |
note: required for `Struct<T>` to implement `Clone`
   --> src/lib.rs:5:10
    |
5   | #[derive(Clone)]
    |          ^^^^^
    |          |
    |          in this derive macro expansion
    |          in this derive macro expansion
    |
   ::: /home/user/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/clone.rs:144:1
    |
144 | pub macro Clone($item:item) {
    | ---------------
    | |
    | in this expansion of `#[derive(Clone)]`
    | in this expansion of `#[derive(Clone)]`
note: required by a bound in `Trait::Type`
   --> src/lib.rs:2:18
    |
2   |     type Type<T: Clone>: Clone;
    |                  ^^^^^ required by this bound in `Trait::Type`

For more information about this error, try `rustc --explain E0275`.
```

</p>
</details>
Repository: rust
Issue: try_blocks type inference failure suggests illegal code
Labels: A-diagnostics,E-needs-test,T-compiler,D-invalid-suggestion

I have the [following code](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=91394c69ee1a2d9b3bbe9aa2220e42c3):

```rust
#![feature(try_blocks)]

fn main() {
    println!(
        "{:?}",
        try {
            if true {
                Ok(0usize)
            } else {
                Err(true)
            }
        }
    );
}
```

I get the following error:

```text
error[[E0282]](https://doc.rust-lang.org/nightly/error-index.html#E0282): type annotations needed
  --> src/main.rs:6:9
   |
6  | /         try {
7  | |             if true {
8  | |                 Ok(0usize)
9  | |             } else {
10 | |                 Err(true)
11 | |             }
12 | |         }
   | |_________^ cannot infer type of the type parameter `T` declared on the associated function `new_debug`
   |
   = note: this error originates in the macro `$crate::format_args_nl` which comes from the expansion of the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider specifying the generic argument
   |
12 |         }::<T>
   |          +++++
```

If I try to follow the compiler's advice by adding a trailing `::<Result<usize, bool>>` on line 12, it results in [code that can't be parsed](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=73d307c548efa8623dcbd59c4b9651c6):

```text
error: expected one of `,`, `.`, `?`, `catch`, or an operator, found `::`
  --> src/main.rs:12:10
   |
12 |         }::<Result<usize, bool>>
   |          ^^ expected one of `,`, `.`, `?`, `catch`, or an operator
```

### Version
Current nightly (2022-10-01 57f097ea25f2c05f424f)