sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: [TRACKER] Navigation Roadmap
Labels: enhancement,tracker,topic:navigation

Here is a list of the major items the navigation team is aiming to tackle in the 4.x time frame.  It will not contain every issue we plan to fix or enhancement we want to add, but is intended to communicate major changes and reworks we have planned.

```[tasklist]
### 4.4
- [ ] https://github.com/godotengine/godot/pull/100497
- [ ] https://github.com/godotengine/godot/pull/100129
- [ ] https://github.com/godotengine/godot/pull/96092
- [ ] https://github.com/godotengine/godot/pull/98866
- [ ] https://github.com/godotengine/godot/pull/98957
```

```[tasklist]
### 4.3
- [ ] https://github.com/godotengine/godot/pull/90434
- [ ] https://github.com/godotengine/godot/pull/75098
- [ ] https://github.com/godotengine/godot/pull/89034
- [ ] https://github.com/godotengine/godot/pull/88221
- [ ] https://github.com/godotengine/godot/pull/87961
- [ ] https://github.com/godotengine/godot/pull/87378
- [ ] https://github.com/godotengine/godot/pull/88047
- [ ] https://github.com/godotengine/godot/pull/82561
```

```[tasklist]
### 4.2
- [ ] #80796
- [ ] #79643 
```

```[tasklist]
### 4.1
- [ ] #69988
```

```[tasklist]
### 4.x
- [ ] https://github.com/godotengine/godot-proposals/issues/8939
- [ ] https://github.com/godotengine/godot-proposals/issues/7208
- [ ] https://github.com/godotengine/godot-proposals/issues/5635
- [ ] https://github.com/godotengine/godot-proposals/issues/5542
- [ ] #66891
- [ ] #69881
- [ ] https://github.com/godotengine/godot-proposals/issues/6317
- [ ] https://github.com/godotengine/godot-proposals/issues/5116
- [ ] https://github.com/godotengine/godot-proposals/issues/7504
```

Anything in the 4.x bucket may be moved up if the work is completed and accepted in time.

Plans are subject to change, please let us know if there is something major that you see missing from the list.  Please make sure that you have an open proposal for any such changes.
Repository: PowerToys
Issue: Tired from scrolling
Labels: Needs-Triage,Needs-Team-Response

### Description of the new feature / enhancement

The app design requires so much scrolling.  It would be great if more settings could be fit in a smaller area.  

### Scenario when this would be used?

Daily use of product.  This would be especially helpful for those with physical disabilities where scrolling is more work because of limited movement of fingers.  (especially those working in the IT field with disabilities)

### Supporting information

Anyone that has used control panels with compact views versus more 'pretty' views can understand this.  One may be pleased with the novelty of pretty interfaces, but when software teams confuse design as being something pretty instead of efficient functionality we get many of the awkward trends of the past 5-10 years.  There is a way to balance the newer clean design of Microsoft Software with the functionality of the past and it lies somewhere in the middle.  Thank you for your time and efforts.
Repository: youtube-dl
Issue: New Release?
Labels: question

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- Look through the README (http://yt-dl.org/readme) and FAQ (http://yt-dl.org/faq) for similar questions
- Search the bugtracker for similar questions: http://yt-dl.org/search-issues
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm asking a question
- [x] I've looked through the README and FAQ for similar questions
- [x] I've searched the bugtracker for similar questions including closed ones


## Question

<!--
Ask your question in an arbitrary form. Please make sure it's worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient.
-->

Preface: 
There have been a number of fixes done since the last release (2021-12-17) {over a years worth} The error messages refer using youtube-dl -U (which is already in place). All the errors I am experiencing are already closed issues, but no no release so youtube-dl -U won't fix it. [Issue #31583 ](https://github.com/ytdl-org/youtube-dl/issues/31583)

Question:
Can either the instructions be updated (and the error message refering to youtube-dl -U be dropped) to "install" via a github pull from Master

or

Can a new release be cut?

Thanks
Repository: rust
Issue: bizarre error message for one of the universal constructor syntaxes
Labels: A-diagnostics,T-compiler,C-bug

<!--
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
#![allow(dead_code)]
#![allow(unused_variables)]
enum Enum<'l, F> {
    Tuple(&'l F),
    Struct { f: &'l F },
}
fn main(){
    let v = 42u32;
    let t = Enum::<u32>::Struct { f: &v };
}
```

I expected to see this happen: it compiles.

Instead, this happened (on the [playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=8410c281e538e90c9a3ba32bb4b58df0), with stable and with nightly):

```
error[E0109]: lifetime arguments are not allowed on variant `Struct`
 --> src/main.rs:9:26
  |
9 |     let t = Enum::<u32>::Struct { f: &v };
  |                          ^^^^^^
  |                          |
  |                          lifetime argument not allowed
  |                          not allowed on variant `Struct`
  |
  = note: enum variants can't have type parameters

error[E0107]: this enum takes 1 lifetime argument but 0 lifetime arguments were supplied
 --> src/main.rs:9:13
  |
9 |     let t = Enum::<u32>::Struct { f: &v };
  |             ^^^^ expected 1 lifetime argument
  |
note: enum defined here, with 1 lifetime parameter: `'l`
 --> src/main.rs:3:6
  |
3 | enum Enum<'l, F> {
  |      ^^^^ --
help: add missing lifetime argument
  |
9 |     let t = Enum::<'l, u32>::Struct { f: &v };
  |                    +++
```

It's not 100% clear to me that this syntax, with the generics applied to the enum type rather than the variant, is intended to be accepted.  I think it probably ought to be, though.  On this point I found #69363/#69356.  The Reference doesn't seem to discuss it.

Also, the error messages are nonsensical, and the suggestion doesn't compile.

Variations:
```
    let t = Enum::<'l, u32>::Tuple { 0: &v }; // use of undeclared lifetime name `'l`  [obviously]
    let t = Enum::<u32>::Tuple { 0: &v }; //  lifetime arguments are not allowed on variant `Tuple`
    let t = Enum::<'_, u32>::Tuple { 0: &v }; // //  lifetime arguments are not allowed on variant `Tuple`
    let t = Enum::<u32>::Tuple(&v);; // compiles, but of course you can't use this for a named-fields variant
    let t = Enum::Struct::<u32> { f: &v }; // compiles
    let t = Enum::Tuple::<u32> { 0: &v }; // compiles
```

</p>
</details>
Repository: next.js
Issue: API config for bodyparser doesn't respect extended:true
Labels: bug,TypeScript

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Home
    Binaries:
      Node: 18.12.1
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.1.7-canary.21
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0

### Which area(s) of Next.js are affected? (leave empty if unsure)

Middleware / Edge (API routes, runtime), TypeScript

### Link to the code that reproduces this issue

https://github.com/rdylina/bodyparser-bug

### To Reproduce

set api config as follows

When passing deeply nested JSON to a NextJS API you need to enable extended:true in the bodyparser config otherwise nested objects will just be discarded and substituted for empty arrays or objects. setting extended to true in the body parser configuration as below is not respected and as such nested data continues to be truncated. 

export const config = {
  api: {
    bodyParser: {
      sizeLimit: '10mb',
      extended: true,
    },
  },
}

pass a deeply nested object via fetch.

### Describe the Bug

When passing deeply nested JSON to a NextJS API you need to enable extended:true in the bodyparser config otherwise nested objects will just be discarded and substituted for empty arrays or objects. setting extended to true in the body parser configuration as below is not respected and as such nested data continues to be truncated. 

export const config = {
  api: {
    bodyParser: {
      sizeLimit: '10mb',
      extended: true,
    },
  },
}

### Expected Behavior

I wold expect the full non-truncated JSON object to be available on API side after setting extended:true

### Which browser are you using? (if relevant)

Chrome Version 110.0.5481.104 (Official Build) (64-bit)

### How are you deploying your application? (if relevant)

localhost
Repository: godot
Issue: Animation Resource empty after moving nodes to another Scene
Labels: bug,topic:editor,usability,topic:animation

### Godot version

4.0 RC 2 / 3.5

### System information

Windows 10

### Issue description

Everything you did in the Animation resource (e.g a cut-scene) is lost as soon as you move nodes and tries to play it in another scene. It'd be nice if those resources retained what you did in them, regardless of where the animated nodes are located.

https://user-images.githubusercontent.com/124409014/219901410-99a9ac81-d37f-4684-a4a8-f121e7444741.mp4

![image](https://user-images.githubusercontent.com/124409014/219902127-b026eaef-e73b-482a-82c1-a4056784a3c9.png)



### Steps to reproduce

1- Animate a Node in Scene01 (e.g move player) with the Animation Player
2- Save Animation (Eg. MyCutscene.tres)
3- Cut-and-paste the Node to Scene02
4- Add animation player node in the scene and load the animation. It will be blank 


### Minimal reproduction project

N/A
Repository: vscode
Issue: Add missing commands for list expansion
Labels: feature-request,tree-widget

Type: <b>Feature Request</b>

Lists have a couple of built-in commands for collapsing that have no analog for expanding. This makes consistent keybindings for interacting with lists difficult or impossible. I attempted to implement the missing commands with an extension, but there's no API for interacting with lists or search results.

| Command                | Collapse                | Expand      |
|------------------------|-------------------------|-------------|
| Current Node           | list.collapse           | list.expand |
| Current Node Recursive | list.collapseAllToFocus | :x:         |
| Entire Tree Recursive  | list.collapseAll        | :x:         |

Search specifically has an extra command equivalent to "Expand Entire Tree Recursive", but there's nothing for the other missing case and ideally it's possible to create these keybindings for any old list and not limited to just search results.

VS Code version: Code - Insiders 1.76.0-insider (96a795cc0b1cd62f9ff66c347637f917c6dde3da, 2023-02-17T22:22:55.538Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Sandboxed: Yes


<!-- generated by issue reporter -->
Repository: godot
Issue: Space bar swiping on Android doesn't work
Labels: bug,platform:android,topic:porting

### Godot version

4.0.rc2

### System information

Android 13, Google Pixel 6

### Issue description

Space bar swiping to move your text cursor works on all apps that I have on my phone except Godot. I was trying out the Android version of the Godot Editor and while making a script, I realized that I couldn't swipe the space bar to move my text cursor.

Example of space bar swiping in Google Keep Notes:

https://user-images.githubusercontent.com/122237633/219932908-5f9f0e50-c543-4a6b-8d09-70adc9050ef7.mp4

Attempted space bar swiping in Godot:

https://user-images.githubusercontent.com/122237633/219932930-a40ce539-02ad-4eb9-b7b9-f3c49acd3de7.mp4

### Steps to reproduce

- Open the Godot Editor on Android
- Make a script, or go to anything text related
- Try to move the text cursor by space bar swiping

### Minimal reproduction project

N/A
Repository: pytorch
Issue: Default value of `validate_args` is set to `True` when passed as `None` in `Multinomial`
Labels: module: distributions,triaged

Running
https://github.com/pytorch/pytorch/blob/17d0b7f532c4b3cd4af22ee0cb25ff12dada85cb/torch/distributions/multinomial.py#L40-L41

produces
```
ValueError: Expected value argument (Tensor of shape (4,)) to be within the support (Multinomial()) of the distribution Multinomial(), but found invalid values:
tensor([2, 5, 2, 1])
```

I believe it is because the default value of `validate_args` is set to `True`.

cc @fritzo @neerajprad @alicanb @nikitaved
Repository: pytorch
Issue: Differentiate with regard a subset of the input
Labels: feature,module: autograd,triaged

### 🚀 The feature, motivation and pitch

Hi,

When I want to differentiate with regard to the first element in a batch, I get an error, as shown in the following example:

```python
n, d = 10, 3
lin1 = nn.Linear(d, d)

# case 1
x = torch.randn(d).requires_grad_()
y = lin1(x)
vec = torch.ones(d)
gr = torch.autograd.grad(y, x, vec, retain_graph=True)[0]
print(gr.shape)  # returns: torch.Size([3])

# case 2
x = torch.randn(n, d).requires_grad_()
y = lin1(x)
vec = torch.ones(d)
gr = torch.autograd.grad(y[0], x[0], vec, retain_graph=True)[0]

# Raises Error:
# RuntimeError: One of the differentiated Tensors appears to not have been used in the graph. Set allow_unused=True if this is the desired behavior.
```
so taking x[i] removes it from the computation graph, I tried to clone it or to use .narrow but in vain!

y[0] only depends on x[0], so I don’t want to compute the gradient with regard to the full input!

Is there a way to do this efficiently?

### Alternatives

_No response_

### Additional context

_No response_

cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7
Repository: create-react-app
Issue: CREATE REACT APP
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

<!--
  Provide a clear and concise description of what the problem is.
  For example, "I'm always frustrated when..."
-->

(Write your answer here.)

### Describe the solution you'd like

<!--
  Provide a clear and concise description of what you want to happen.
-->

(Describe your proposed solution here.)

### Describe alternatives you've considered

<!--
  Let us know about other solutions you've tried or researched.
-->

(Write your answer here.)

### Additional context

<!--
  Is there anything else you can add about the proposal?
  You might want to link to related issues here, if you haven't already.
-->

(Write your answer here.)
Repository: PowerToys
Issue: FancyZones - "Overwrite Windows Snap" not working after Windows startup
Labels: Issue-Bug,Product-FancyZones,Needs-Triage

### Microsoft PowerToys version

0.67.1

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

FancyZones

### Steps to reproduce

-> FancyZones - ON
-> Overwrite Windows Snap - ON
-> Reboot / Turn on computer
-> Wait for the PowerToys to run
->Open two apps on "Portrait-oriented" display
-> The apps will open with vertical split (not handy on Portrait-oriented displays)

To fix it:
-> Open PowerToys & FancyZones
-> Re-Enable "I have to turn off and back on "Overwrite Windows Snap" to use custom layouts on my two "Portrait-oriented" monitors¨ after Windows startup if I want to move an app with keyboard shortcuts."
=> Ability to use Windows keyboard shortcuts to split apps on Portrait-oriented displays is back



[PowerToysReport_2023-02-19-11-09-24.zip](https://github.com/microsoft/PowerToys/files/10776689/PowerToysReport_2023-02-19-11-09-24.zip)


### ✔️ Expected Behavior

To have "Overwrite Windows Snap" on and working automatically to be able to move an app with keyboard shortcuts.
(Apply custom zones and replace default Windows Snap after Windows Startup) 

### ❌ Actual Behavior

I have to turn off and back on "Overwrite Windows Snap" to use custom layouts on my two "Portrait-oriented" monitors¨ after Windows startup if I want to move an app with keyboard shortcuts.

### Other Software

_No response_
Repository: rust
Issue: "function cannot return without recursing" should deny by default
Labels: A-lints,A-diagnostics,T-lang,T-compiler,L-unconditional_recursion

### Code

```Rust
#[derive(Default)]
struct VariantA {
    pub name: String
}

#[derive(Default)]
struct VariantB {
    pub name: String
}

enum DefaultEnum {
    A(VariantA),
    B(VariantB)
}

impl Default for DefaultEnum {
    fn default() -> Self {
        Default::default()
    }
}

fn main() {
    let default_enum: DefaultEnum = Default::default();
}
```


### Current output

```Shell
Compiling playground v0.0.1 (/playground)
warning: function cannot return without recursing
  --> src/main.rs:19:5
   |
19 |     fn default() -> Self {
   |     ^^^^^^^^^^^^^^^^^^^^ cannot return without recursing
20 |         Default::default()
   |         ------------------ recursive call site
   |
   = help: a `loop` may express intention better if this is on purpose
   = note: `#[warn(unconditional_recursion)]` on by default

warning: `playground` (bin "playground") generated 1 warning
    Finished dev [unoptimized + debuginfo] target(s) in 0.63s
     Running `target/debug/playground`
```


### Desired output

```Shell
should be an error instead of a warning
```


### Rationale and extra context

This causes a stack overflow and should not compile 

### Other cases

_No response_

### Anything else?

_No response_
Repository: PowerToys
Issue: Calculator is showing result even if no operator is provided
Labels: Idea-Enhancement,Run-Plugin

### Microsoft PowerToys version

0.67.1

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

Suppose you have a file named "doc103.pdf", and you type "103" to search it, the calculator result shows up at the top followed by the actual search result. I know we can change the order, but the result should not be there at the first place

### ✔️ Expected Behavior

The calculator result should not show up if no operator like + - * / is given.
Just typing a number should not give any result by calculator module.

### ❌ Actual Behavior

![image](https://user-images.githubusercontent.com/63805243/219946406-cc9ee51c-efa2-433f-bbfb-f0d927f04a8a.png)
The calculator result shows up.

### Other Software

_No response_
Repository: pytorch
Issue: Add local version identifier to wheel file names
Labels: module: build,triaged

### 🚀 The feature, motivation and pitch

Hello 👋  Thank you for maintaining pytorch 🙇 It's a joy to use and I'm very excited about the 2.0 release!
I've found a tiny quality of life improvement surrounding the precompiled wheel available at https://download.pytorch.org/whl/ .

Currently users are unable to tell `pip` that a specific compiled version of torch should be re-installed from a different whl.
For example; 

```
# Install torch
$ pip install 'torch>=1.13.0+cpu' --find-links https://download.pytorch.org/whl/cpu/torch_stable.html
Looking in indexes: https://alexander.vaneck:****@artifactory.paigeai.net/artifactory/api/pypi/pypi/simple
Looking in links: https://download.pytorch.org/whl/cpu/torch_stable.html
Collecting torch>=1.13.0+cpu
  Using cached https://artifactory.paigeai.net/artifactory/api/pypi/pypi/packages/packages/82/d8/0547f8a22a0c8aeb7e7e5e321892f1dcf93ea021829a99f1a25f1f535871/torch-1.13.1-cp310-none-macosx_10_9_x86_64.whl (135.3 MB)
...
Installing collected packages: typing-extensions, torch
Successfully installed torch-1.13.1 typing-extensions-4.5.0
# Then later install torch for cu116
$ pip install 'torch>=1.13.0+cu116' --find-links https://download.pytorch.org/whl/cu116/torch_stable.html
Looking in indexes: https://alexander.vaneck:****@artifactory.paigeai.net/artifactory/api/pypi/pypi/simple
Looking in links: https://download.pytorch.org/whl/cu116/torch_stable.html
Requirement already satisfied: torch>=1.13.0+cu116 in ./.virtualenvs/torch-links/lib/python3.10/site-packages (1.13.1)
Requirement already satisfied: typing-extensions in ./.virtualenvs/torch-links/lib/python3.10/site-packages (from torch>=1.13.0+cu116) (4.5.0)
# We now hold CPU torch for CUDA 11.6 enabled environment.
```

It would be mighty handy if the wheels provided would include the [local version identifiers](https://peps.python.org/pep-0440/#local-version-identifiers) for the environment they are built in, f.e. `torch-1.13.1+cu116-cp39-cp39-manylinux2014_aarch64.whl`. And as local version identifiers are optional it would have no impact on the current dependency resolution. 

### Alternatives

_No response_

### Additional context

_No response_

cc @malfet @seemethere
Repository: vscode
Issue: Git - Support `git diftool -d`, AKA Git directory diff
Labels: feature-request,git

<!-- ⚠️⚠️ 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. -->
When VS Code is set as the difftool for Git, make it work nicely with `git difftool -d`, AKA a directory diff. VS Code doesn't know how to handle that scenario well ATM.
Repository: opencv
Issue: Add an API to retrieve the metadata_props field from ONNX files
Labels: feature,RFC,category: dnn (onnx)

### Descripe the feature and motivation

The ONNX file format reserves the metadata_props field for user defined metadata, stored in a 'key, value' strings. It is very useful for storing input preprocessing info, model tags and other stuff. I couldn't find any C++ library that can load ONNX models that supports reading the metadata_props field, even though it is trivial to do so. As a proof-of-concept I modified OpenCV to provide an overloaded `readNetFromONNX` function that extracts the metadata and stores it in a std::map<std::string, std::string> object:

[https://github.com/Palmitoxico/opencv/commit/c4479b33efff063b426c1067c0997b5aaec508a2](https://github.com/Palmitoxico/opencv/commit/c4479b33efff063b426c1067c0997b5aaec508a2)

The `readNetFromONNX(const String &onnxFile, std::map<std::string, std::string> &metadata)` still left to do. Also I didn't create python wrappers for it yet.

I would like to hear your comments about the API before I open a PR.

Thanks,
Augusto.

### Additional context

_No response_