sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: [torch.fx] Upgrade on node info
Labels: triaged,module: fx

### 🚀 The feature, motivation and pitch

Torch.fx is a very useful tool capable of analysing and understanding deep models, but from an analysis perspective it would be interesting to know the dimensions of the tensors that have passed through the nodes. In order to understand where there might be memory space problems, for example.

What I'd like to see is for each node to have two additional arguments, input_size and output_size so that this information can be easily retrieved during an analysis using torch.fx

I've see something in torch.passes.shape_prop that seems to analyze tensors but I don't see anything on how to use it. And same for the proxy, I see that it have some useful information in but no way to use it.

Maybe the solution already exist but I prefer suggest if it doesn't

### Alternatives

_No response_

### Additional context

_No response_

cc @ezyang @SherlockNoMad @soumith @EikanWang @jgong5 @wenzhe-nrv
Repository: flutter
Issue: [go_router] return Future<T?> in pushReplacement, pushReplacementNamed, replace and replaceNamed
Labels: package,c: proposal,P3,p: go_router,team-go_router,triaged-go_router

I am currently working on incorporating the `go_router` into our application. However, I have noticed some discrepancies between its imperative API of the `go_router` package and the `NavigatorState` approach. Specifically, the following methods return `void` rather than `Future<T?>`:
* `pushReplacement`
* `pushReplacementNamed`
* `replace`
* `replaceNamed`
I am curious to know if there are any particular reasons for not providing the results. From my analysis of the code, it appears relatively straightforward to reintroduce these results. Furthermore, aligning the API with the `NavigatorState` API could potentially enhance the package's ease of adoption.
Repository: PowerToys
Issue: Auto Detect Repeating Name Pattern in PowerRename
Labels: Idea-Enhancement,Product-PowerRename

### Description of the new feature / enhancement

Lets say i have 5 files. for example :
1. [NAME] chair [asd]
2. [NAME] table [asd]
3. [NAME] spoon [asd]
4. [NAME] spleen [asd]
5. [NAME] sploon [asd]

to make renaming lots of file faster, PowerRename should auto detect string "[NAME] " in "search for" bar. Not only in the front of a file name, but back of file name too. Also add change all file name to 1, 2, 3, ... or a, b, c, ...

### Scenario when this would be used?

If you download pictures, movies and maybe songs from a web. Usually they add something like "[www.web.com]" in each of the file. Detecting that prefix will makes renaming all of them faster espescially when that prefix is hard to type.

### Supporting information

_No response_
Repository: PowerToys
Issue: Minor Idea/Request for PowerToys Run
Labels: Needs-Triage

### Description of the new feature / enhancement

The text prompt that automatically appears in the input area reads, "Start typing..." It may be a nice little feature to be able to change the the prompt wording, or perhaps the option of having no prompt text at all. Another possibility to consider is showing the most recent search input string as a quick reminder in the prompt (without showing all the results).

### Scenario when this would be used?

Admittedly, this is a somewhat trivial and cosmetic feature that essentially has no impact on functionality, but there are basically two parts to my rationale (and by extension, scenarios for usage):
1. Some people prefer a simple, minimalist aesthetic, especially in an interface they use numerous times each day.
2. I would like to be able to change the prompt wording to something insulting (or perhaps even vulgar) on the computers of my friends and colleagues who are dumb enough to leave their computer unlocked around me.

### Supporting information

_No response_
Repository: pytorch
Issue: Add `torch.cat`  support for torch native sparse tensors. (Need for PyG)
Labels: module: sparse,feature,triaged

### 🚀 The feature, motivation and pitch

Up until recently PyG required torch-sparse which provided functionality for sparse tensor math for GNNs. PyG 2.3+ has the goal of dropping torch-sparse and other legacy torch-* packages that PyG used to require. However, for dropping torch-sparse, we are relying on upstream pytorch native sparse tensors. One required functionality of these tensors is the ability to `torch.cat` them together. Currently this is not supported:
This issue tracks the failure w/ reproduction steps: https://github.com/pytorch/pytorch/issues/98861

### Alternatives

_No response_

### Additional context

_No response_

cc @alexsamardzic @nikitaved @pearu @cpuhrsch @amjames @bhosmer
Repository: PowerToys
Issue: Paste as plain text ignores right alt button
Labels: Issue-Bug,Priority-3,Status-Reproducible,Product-Advanced Paste

### Microsoft PowerToys version

0.69.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Paste as Plain Text

### Steps to reproduce

- Change keyboard shortcut to "control alt V" by pressing left control, right alt and V. 
- Copy formatted text.
- Press left control, right alt and V
- nothing is pasted
- Press left control, left alt and V
- plain text is pasted as expected

Users should be able to use the right alt and left alt buttons interchangeably. If not, then right alt button should be captured as right alt button when creating the keyboard shortcut

### ✔️ Expected Behavior

Plain text pasted pressing left control, right alt and V

### ❌ Actual Behavior

Nothing pasted

### Other Software

_No response_
Repository: react
Issue: Bug: Suspense should hide Portals deeper in the tree
Labels: Type: Bug,Component: Suspense

When Portal is a direct child of Suspense, suspending hides the portal: https://codesandbox.io/s/cocky-boyd-mlq2ko?file=/src/App.js

But when a Portal is deeper in the tree, suspending fails to hide the portal nodes: https://codesandbox.io/s/nostalgic-fog-udyhuz?file=/src/App.js

We need to fix this to recursively hide portals. There's a question of which traversal to use, and how it combines with existing traversal. E.g. does "hiding" happen before layout effects run?

We would also need to decide what to do with legacy mode. One option is to "fix" it there too. But that might be difficult to roll out. It might also be tricky to implement. Another option is to leave it as is (the current behavior is leaving a "hole" in place of the suspended component: https://codesandbox.io/s/elastic-ptolemy-2u6qel?file=/src/App.js). Then we'd need to make sure we at least keep that buggy behavior.

We might want to add an internal-only warning (to be muted but logged on devservers) to track _newly hidden_ nodes portals that wouldn't have been hidden with the previous algorithm. Then maybe this would let us know where to fix the UI and avoid the UI regression caused by modals disappearing.

Summary of work that needs to be done:

- [ ] Port sandboxes to failing tests
- [ ] Implement new behavior behind a flag
  - [ ] Figure out where hiding/showing happens during the commit phase
  - [ ] Add new behavior (all direct children of portals, no matter how deep, get auto-shown/hidden)
  - [ ] Decide what legacy renderer should do, write tests for that too
  - [ ] (Maybe) add internal-only muted logging for content that would be hidden with new behavior
Repository: storybook
Issue: [Bug]: Installation issue tied to cloud storage and/or file path with ampersand
Labels: bug,core

### Describe the bug

I had big problems trying to install and run a react app with storybook. After experimenting, it appears it has something to do with placing my code in a folder backed up by MS OneDrive... OR... perhaps the fact that the path name of that drive uses an ampersand character in it.

Doing an install in another location (not backed up by MS OneDrive) was successful.

To be specific, the installation appears to work, but `npm run storybook` generates this error every time:
![image](https://user-images.githubusercontent.com/127144197/231535284-3f6e5e27-3d4e-4681-917f-45ac05a623f8.png)

To reproduce the issue, notice that this set of commands (on a Mac) works fine unless it is run from any directory that is a child directory of the "OneDrive-Name&Company" that seems to be the culprit.

![image](https://user-images.githubusercontent.com/127144197/231536644-047270ab-96f5-4489-a662-6bad4b2b2013.png)






### To Reproduce

_No response_

### System

```shell
Environment Info:

  System:
    OS: macOS 13.3.1
    CPU: (10) arm64 Apple M1 Max
  Binaries:
    Node: 16.13.0 - ~/.nvm/versions/node/v16.13.0/bin/node
    npm: 9.5.0 - /opt/homebrew/bin/npm
  Browsers:
    Chrome: 110.0.5481.177
    Safari: 16.4
  npmPackages:
    @storybook/addon-actions: ^7.0.4 => 7.0.4 
    @storybook/addon-essentials: ^7.0.4 => 7.0.4 
    @storybook/addon-interactions: ^7.0.4 => 7.0.4 
    @storybook/addon-links: ^7.0.4 => 7.0.4 
    @storybook/addon-mdx-gfm: ^7.0.4 => 7.0.4 
    @storybook/blocks: ^7.0.4 => 7.0.4 
    @storybook/node-logger: ^7.0.4 => 7.0.4 
    @storybook/preset-create-react-app: ^7.0.4 => 7.0.4 
    @storybook/react: ^7.0.4 => 7.0.4 
    @storybook/react-webpack5: ^7.0.4 => 7.0.4 
    @storybook/testing-library: ^0.1.0 => 0.1.0
```


### Additional context

I must have installed and reinstalled 20+ times, trying to get this  to work. I had an older installation of storybook 6.5.x running fine from the "OneDrive-Name&Company" folder with no issues, but the error msg made me suspicious because the ampersand was displayed as an HTML escape code. Anyway, installing in "/Users/user_name/projects/app-name/" works fine using the exact same steps that failed in the other directory.
Repository: storybook
Issue: [Bug]: `--loglevel` has no impact on output during build
Labels: bug,good first issue,help wanted,cli,sev:S4

### Describe the bug

Adding the loglevel flag:

```yarn build-storybook --loglevel verbose```

seems to not change the output at all, only `info` level is ever shown. If a random string matching no available parameters is used, no error is shown either.

### To Reproduce

https://github.com/pm0u/storybook-enhanced-resolve-repro

run `yarn build-storybook --loglevel verbose`
run `yarn build-storybook --loglevel silent`
run `yarn build-storybook --loglevel lskdjflkdjs`

None of the above changes the output

### System

```shell
Environment Info:

  System:
    OS: macOS 12.6.3
    CPU: (10) arm64 Apple M1 Max
  Binaries:
    Node: 18.15.0 - ~/.nvm/versions/node/v18.15.0/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v18.15.0/bin/yarn
    npm: 9.5.0 - ~/.nvm/versions/node/v18.15.0/bin/npm
  Browsers:
    Chrome: 112.0.5615.49
    Firefox: 111.0.1
    Safari: 16.3
  npmPackages:
    @storybook/addon-actions: ^7.0.4 => 7.0.4 
    @storybook/addon-essentials: ^7.0.4 => 7.0.4 
    @storybook/addon-interactions: ^7.0.4 => 7.0.4 
    @storybook/addon-links: ^7.0.4 => 7.0.4 
    @storybook/addon-mdx-gfm: ^7.0.4 => 7.0.4 
    @storybook/react: ^7.0.4 => 7.0.4 
    @storybook/react-webpack5: ^7.0.4 => 7.0.4 
    @storybook/testing-library: ^0.1.0 => 0.1.0
```


### Additional context

_No response_
Repository: storybook
Issue: [Bug]: Unicode characters in <Markdown> not rendered
Labels: bug,mdx

### Describe the bug

In Version 7.0.2, using the Markdown component to import a .MD file, fails to render unicode characters when displayed in storybook.

https://storybook.js.org/docs/react/api/doc-block-markdown#markdown

Note: I am NOT using the github markdown plugin, and I'm able to work around the issue by using the square brackets with the x as needed.

### To Reproduce

Clone the sandbox for version 7.0.2, Add the following 2 files:

MyReadme.stories.mdx:
```
import { Meta, Markdown } from '@storybook/addon-docs';
import Readme from './MyReadme.md?raw';

<Meta title="Issue/MyReadme" />

<Markdown>{Readme}</Markdown>
```

MyReadme.md
```
This should show a unicode checkbox in a table:

| Checked?    | Character |
| ------------| --------- |
| No          | &#9744;   |
| Yes         | &#9745;   |

This should show a unicode character outside of the table: &#9745;

This was working with the previous mdx 1 implementation, and I've confirmed that is the correct setup for unicode characters according to markdown docs, it also works in other viewers I have tried using.

```


### System

```shell
Environment Info:

  System:
    OS: Windows 10 10.0.19045
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
  Binaries:
    Node: 16.18.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.15 - C:\Program Files (x86)\Yarn\bin\yarn.CMD   
    npm: 8.19.2 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (112.0.1722.39)
```


### Additional context

_No response_
Repository: rust
Issue: Help to use dot operator does not take into account auto-dereferencing
Labels: A-diagnostics,T-compiler,D-invalid-suggestion

### Code

```Rust
struct A;

impl A {
    fn a(self) {}
}

fn main() {
    let x = &A;
    a(*x);
}
```


### Current output

```Shell
error[E0425]: cannot find function `a` in this scope
 --> src/main.rs:9:5
  |
1 | struct A;
  | --------- similarly named unit struct `A` defined here
...
9 |     a(*x);
  |     ^
  |
help: a unit struct with a similar name exists
  |
9 |     A(*x);
  |     ~
help: use the `.` operator to call the method `a` on `A`
  |
9 |     (*x).a();
  |     ~  ~~~~~

For more information about this error, try `rustc --explain E0425`.
```


### Desired output

```Shell
error[E0425]: cannot find function `a` in this scope
 --> src/main.rs:9:5
  |
1 | struct A;
  | --------- similarly named unit struct `A` defined here
...
9 |     a(*x);
  |     ^
  |
help: a unit struct with a similar name exists
  |
9 |     A(*x);
  |     ~
help: use the `.` operator to call the method `a` on `A`
  |
9 |     x.a();
  |      ~~~~

For more information about this error, try `rustc --explain E0425`.
```


### Rationale and extra context

`.` auto-dereferences, but this is not taken into account when one dereferences in the existing function call.

### Other cases

_No response_

### Anything else?

If a method exists on the reference that would shadow the method on the object, then the existing help is fine.
Repository: yt-dlp
Issue: provide and populate "watchtime" field in youtube json output
Labels: site-enhancement,triage

### DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

- [X] I understand that I will be **blocked** if I *intentionally* remove or skip any mandatory\* field

### Checklist

- [X] I'm requesting a feature unrelated to a specific site
- [X] I've looked through the [README](https://github.com/yt-dlp/yt-dlp#readme)
- [X] I've verified that I'm running yt-dlp version **2023.03.04** ([update instructions](https://github.com/yt-dlp/yt-dlp#update)) or later (specify commit)
- [X] I've searched [known issues](https://github.com/yt-dlp/yt-dlp/issues/3766) and the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar issues **including closed ones**. DO NOT post duplicates
- [X] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)

### Provide a description that is worded well enough to be understood

When running with login credentials (--cookies[-from-browser]), it would be handy to include the viewed/watched status of YouTube videos reported from, for example, :ytsubs in the output JSON generated with -j like:

  yt-dlp -v -i --cookies youtube.com_cookies.txt :ytsubs --no-download -j --lazy-playlist --dateafter now-1day --break-on-reject

Currently, there is no indication of watched/unwatched status reported anywhere that I can find.

This functionality could be extended perhaps to new filter options, something like--watched-only or --unwatched-only, though those don't apply to my intended use. I'm just looking to have the watchtime included in the JSON output.
Repository: storybook
Issue: [Bug]: Gatsby link and Storybook
Labels: bug,help wanted,compatibility with other tools,gatsby,sev:S3

### Describe the bug

Storybook is great, we've just upgraded gatsby and need to upgrade storybook. Both normally work absolutely fine.

Looking at gatsby's documentation, this hasn't been updated for storybook v7 yet, and parts of the systems working together doesn't work.

I've tried in existing and a fresh gatsby and storybook installation (github linked below)

Example, when using a gatsby `<Link>` component in a story, the system errors.

<img width="885" alt="image" src="https://user-images.githubusercontent.com/2240744/231571511-65a8b999-dcc7-4f60-96b5-80b4fd7d1736.png">


### To Reproduce

https://github.com/darylthornhill/test-gatsby-storybook-error

All i've done is set up a gatsby Link and put it in the `Header.tsx` in the `src/stories` folder.

### System

```shell
Environment Info:

  System:
    OS: macOS 13.2.1
    CPU: (10) arm64 Apple M2 Pro
  Binaries:
    Node: 18.15.0 - ~/.nvm/versions/node/v18.15.0/bin/node
    npm: 9.5.0 - ~/.nvm/versions/node/v18.15.0/bin/npm
  Browsers:
    Safari: 16.3
  npmPackages:
    @storybook/addon-essentials: ^7.0.4 => 7.0.4 
    @storybook/addon-interactions: ^7.0.4 => 7.0.4 
    @storybook/addon-links: ^7.0.4 => 7.0.4 
    @storybook/blocks: ^7.0.4 => 7.0.4 
    @storybook/react: ^7.0.4 => 7.0.4 
    @storybook/react-webpack5: ^7.0.4 => 7.0.4 
    @storybook/testing-library: ^0.0.14-next.2 => 0.0.14-next.2
```


### Additional context

_No response_
Repository: vscode
Issue: Git - merge is canceled when removing an untracked file
Labels: bug,git

Does this issue occur when all extensions are disabled?: Yes
- VS Code Version:  1.77.3
- OS Version: Windows 10 22H2

Steps to Reproduce:

1. Perform a Git merge with conflicts (from the command line, in or outside of VSCode - I'm using git bash as it shows the merge state by default, but I've tried this using CMD with the same results)
2. Note that from a git-bash command line we see that we are "_branch|MERGING_"
3. Note VSCode is showing a suggested merge Message (that includes branch names, etc) as normal in the Source Control tab.
4. Add an untracked file during this process.
5. Remove that untracked file from the Changes (not Staged) section of VSCode's Source Control tab.
6. Note now in git-bash we're not merging anymore. Also note that the suggested commit Message in the Source Control tab is gone. **This should not have happened!**
7. If I commit this change it results in a regular commit and not a merge.

The act of adding an untracked file is typical when running `git mergetool`. Git backs-up merged files with an ".orig" extension. I typically remove them before commiting. If I do this removal with VSCode's Source Control tab it aborts the commit. Well, not an "abort" so much as a `git checkout` with no specific filename given - which seems to stop the merge process, but keeps the files staged.  Here's a complete dump of the Git commands VSCode is running:

(From **OUTPUT > Git** in VSCode's terminals)
```
2023-04-12 15:30:51.736 [info] > git show --textconv HEAD:libs/graphql-console/src/graphql-explorer/graphql-type/graphql-top-level-type/graphql-top-level-type.component.html.orig [162ms]
2023-04-12 15:30:51.845 [info] > git ls-tree -l HEAD -- C:\Users\<my-file-path>.orig [265ms]
2023-04-12 15:30:57.467 [info] > git clean -f -q -- C:\Users\<my-file-path>.orig [209ms]
2023-04-12 15:30:57.579 [info] > git ls-tree -l HEAD -- C:\Users\<my-file-path>.orig [328ms]
2023-04-12 15:30:59.558 [info] > git ls-tree -l HEAD -- C:\Users\<my-file-path>.orig [140ms]
2023-04-12 15:30:59.712 [info] > git show --textconv HEAD:libs/graphql-console/src/graphql-explorer/graphql-type/graphql-top-level-type/graphql-top-level-type.component.html.orig [150ms]
2023-04-12 15:31:00.968 [info] > git checkout -q [3498ms]
2023-04-12 15:31:00.968 [info] husky > post-checkout (node v18.15.0)
2023-04-12 15:31:01.148 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/testmerge refs/remotes/testmerge [171ms]
2023-04-12 15:31:01.154 [info] > git config --get commit.template [182ms]
2023-04-12 15:31:01.892 [info] > git status -z -uall [734ms]
2023-04-12 15:31:32.165 [info] > git check-ignore -v -z --stdin [140ms]
```

(Looking at VSCode's source [git.ts and respository.ts] it seems like maybe we're not pushing the path of the untracked file into the clean() functions in this case?)
Repository: rust
Issue: Tracking issue for dejargonification
Labels: C-cleanup,C-tracking-issue,A-contributor-roadblock,T-types

There are some things in rustc that are named historically or just really oddly. This issue tracks renaming them to reflect what they are without having to understand Rust's history and/or programming language design/theory jargon.

* [ ] Region -> Lifetime in general. While Region kinda makes more sense, we use Lifetime in the language
* [ ] `EarlyBoundRegion` -> `GenericLifetime` (to reflect what they are in the language)
* [ ] `LateBoundRegion `->`HigherRankedLifetime` (")
* [ ] `*Folder` and `fold_*` -> `*Replacer` and `replace_*`
* [x] #110793
* [ ] `subst` -> `replace_generics`

These changes have an accepted MCP at https://github.com/rust-lang/compiler-team/issues/451

**Note: please do not pick up any of these work items without first checking in with me. These renamings aren't universally liked and we should make sure everyone stays on board.**

I'm not gonna move on these things quickly, and I'm fine closing PRs even after putting in lotsa work. So if anyone has concerns, please raise them on a zulip thread or directly with me.
Repository: godot
Issue: Smart autowrap text on label wraps each character into 1 column
Labels: bug,topic:gui

### Godot version

4.02

### System information

Windows 10

### Issue description

If the label get's squished into a 0 size inside a HBoxContainer control, it squishes the text into 1 column when the autowrap is set to "Word (Smart)". I've seen this also in the documentation, in godot, in various places.

![godot4_text_display_bug1](https://user-images.githubusercontent.com/46553425/231578682-9a327643-de6f-424d-a0d3-0968aa0d74f5.jpg)


### Steps to reproduce

Create a new Control based scene. Add a HBoxControl. Add a Label as child of HBoxControl. Type a few words into the Label text property. Set the Label's Autowrap mode to  "Arbitrary" or "Word (Smart)".

### Minimal reproduction project

[TestProject.zip](https://github.com/godotengine/godot/files/11215807/TestProject.zip)
Repository: PowerToys
Issue: Discussion/Suggestion thread for Run ChatGPT plugin v2
Labels: Product-PowerToys Run,Needs-Triage,Run-Plugin

### Description of the new feature / enhancement

Since a PowerToys Run Plugin for ChatGPT is being made ([#25441](https://github.com/microsoft/PowerToys/pull/25411)), and someone already started making suggestions for v2, here's an issue to avoid cluttering the Draft PR for v1.

Please send your suggestions here if you have any! Thanks!

### Scenario when this would be used?

This will be needed after v1 of said plugin gets released.

### Supporting information

_No response_
Repository: pytorch
Issue: [BE] Dedup the functorch skipOps mechanism and the common_method_invocations one
Labels: triaged,module: testing

This code was original in functorch out-of-tree. Then, we [copy-pasted it into PyTorch](https://github.com/pytorch/pytorch/blob/1149ba5553dc3467afed7e1867dffc7065c742c7/torch/testing/_internal/common_methods_invocations.py#L20288-L20321). Since then, there's been a number of improvements to the functorch version and functorch was upstreamed into PyTorch. However, we have not yet consolidated [the functorch version](https://github.com/pytorch/pytorch/blob/master/test/functorch/common_utils.py#L355) with the one in common_method_invocations.

We should consolidate the two, likely just by moving the functorch pieces into common_method_invocations.