sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Toggle open/close by double clicking on the notification icon
Labels: Needs-Triage

### Description of the new feature / enhancement

When PowerToys are running i have an icon in the notification area. To open PowerToys settings i double click on the icon, but there is no way to minimize the settings window again from the icon.

### Scenario when this would be used?

So, instead of double clicking again to minimize the window i need to find the X to close the window or use the right mouse click on the taskbar icon and select close.

If i open PowerToys on another screen i will have to move the mouse pointer all the way to the X for closing the window.

Clicking on the notification icon to close the application is a very common behavior, so why can't PowerToys have it too?

Btw, because `Settings` is the default behaviour when double clicking, `Settings` should be in bold to indicate it is the default action.

### Supporting information

_No response_
Repository: godot
Issue: Classes that are exposed but lead to empty docs pages.
Labels: bug,topic:core,topic:gdscript,topic:editor

### Godot version

4.0.2

### System information

Ubuntu 22.04.1 LTS

### Issue description

I found two classes are exposed to scripting. They are highlighted as such:

![image](https://github.com/godotengine/godot/assets/85438892/16fc88e5-d090-4b91-a459-7c99688b96ed)

But they are undocumented - nothing in F1, and Ctrl+LMB leads here:

![image](https://github.com/godotengine/godot/assets/85438892/f993194c-c165-40c3-9e82-17d970c53d3b)

I also noticed that GodotSharp is listed in GlobalScope's documentation, yet leads to a similar empty documentation page, but it might not be related.

I know that the GDScriptNative class can show up like this:
```gdscript
print(Node)  # <GDScriptNativeClass#-9223372027929296496>
```

I know nothing about the other class, though.

### Steps to reproduce

Here are all such classes I discovered:

```
EditorHelp
FramebufferCacheRD
GodotPhysicsServer2D
GodotPhysicsServer3D
GDScriptEditorTranslationParserPlugin
GDScriptNativeClass
IPUnix
ResourceImporterOggVorbis
ResourceImporterMP3
ResourceFormatImporterSaver
UniformSetCacheRD
```

### Minimal reproduction project

N/A
Repository: flutter
Issue: Tests flaking on tool artifact extraction on Windows
Labels: tool,P2,team-tool,triaged-tool

[This issue](https://github.com/flutter/flutter/issues/123519) is happening again on CI.

https://github.com/flutter/flutter/issues/126408
https://github.com/flutter/flutter/issues/126410
https://github.com/flutter/flutter/issues/126418

cc folks from the previous instance: @gspencergoog @christopherfujino @Hixie. From the thread on the previous GitHub issue, it sounds like there may be new logging to examine. Provisionally assigning to @christopherfujino to investigate that, and marking P1 to match the elevated flake rate.
Repository: next.js
Issue: [NEXT-1170] Headers are not applied for trailing slash redirects when deployed in Vercel
Labels: bug,Runtime,linear: next

### Verify canary release

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

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.4.0: Mon Mar  6 20:59:28 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.15.0
      npm: 9.5.0
      Yarn: 1.22.19
      pnpm: 8.1.0
    Relevant packages:
      next: 13.4.2-canary.4
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 4.9.5
```


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

Middleware / Edge (API routes, runtime)

### Link to the code that reproduces this issue

https://github.com/apledger/trailing-slash-headers-sandbox

### To Reproduce

1. Run the [repo](https://github.com/apledger/trailing-slash-headers-sandbox) locally
2. Check the network tab on the index page for the requests to `/api/hello`
3. Verify `x-hello` header is present
![CleanShot 2023-05-10 at 12 18 50@2x](https://github.com/vercel/next.js/assets/399146/ea5ea0e3-7218-4eb3-868f-5aea3e496159)
4. Deploy repo to Vercel. [Here is a link to my deployment](https://trailing-slash-headers-sandbox.vercel.app/).
5. Check the network tab on the index page for the requests to `/api/hello`
6. Verify `x-hello` header is missing
<img width="766" alt="CleanShot 2023-05-10 at 12 20 43@2x" src="https://github.com/vercel/next.js/assets/399146/f38e250a-b07b-4e13-8a7c-b4ed90a0bc43">



### Describe the Bug

Headers defined in`next.config.js` are missing from redirected requests via the `trailingSlash` config option in `next.config.js` when deployed to Vercel.

### Expected Behavior

It appears that the intended [execution order](https://nextjs.org/docs/app/building-your-application/routing/middleware#matching-paths) of headers being applied before redirects is working as intended locally, but not when [deployed](https://trailing-slash-headers-sandbox.vercel.app/) to Vercel.

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

Chrome Version 112.0.5615.137 (Official Build) (arm64)

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

Vercel

<sub>[NEXT-1170](https://linear.app/vercel/issue/NEXT-1170/headers-are-not-applied-for-trailing-slash-redirects-when-deployed-in)</sub>
Repository: go
Issue: cmd/go/internal/modfetch: TestCodeRepoVersions failures
Labels: Testing,NeedsInvestigation,GoCommand,modules

```
#!watchflakes
post <- pkg == "cmd/go/internal/modfetch" && `test timed out` && `^cmd/go/internal/web\.Get`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/8fe0e0c615fa5710782b9416dfc38bcab9d273b0)):

    vcs-test.golang.org rerouted to http://127.0.0.1:40375
    https://vcs-test.golang.org rerouted to https://127.0.0.1:38347
    panic: test timed out after 15m0s
    running tests:
    	TestCodeRepoVersions (14m27s)
    	TestCodeRepoVersions/parallel (14m27s)
    	TestCodeRepoVersions/parallel/swtch.com_testmod (14m27s)
    
    runtime.gopark(0xc000079e00?, 0x40dec5?, 0x50?, 0x36?, 0x18?)
    	/workdir/go/src/runtime/proc.go:387 +0xce fp=0xc000079d98 sp=0xc000079d78 pc=0x43ae4e
    runtime.chanrecv(0xc00030a3f0, 0xc000079e7f, 0x1)
    	/workdir/go/src/runtime/chan.go:583 +0x3cd fp=0xc000079e10 sp=0xc000079d98 pc=0x40752d
    runtime.chanrecv1(0xb43700?, 0x7b0de0?)
    	/workdir/go/src/runtime/chan.go:442 +0x12 fp=0xc000079e38 sp=0xc000079e10 pc=0x407152
    testing.(*T).Run(0xc0002bd1e0, {0x839a87?, 0x83ea2f?}, 0x876e48)
    	/workdir/go/src/testing/testing.go:1649 +0x3c8 fp=0xc000079ef8 sp=0xc000079e38 pc=0x501548
    cmd/go/internal/modfetch.TestCodeRepoVersions(0xc0002bd1e0)
    	/workdir/go/src/cmd/go/internal/modfetch/coderepo_test.go:825 +0xe5 fp=0xc000079f70 sp=0xc000079ef8 pc=0x7812e5
    testing.tRunner(0xc0002bd1e0, 0x876c98)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: x/pkgsite: slow to download std when running locally
Labels: Performance,pkgsite

Steps to reproduce:
- `$ go run golang.org/x/pkgsite/cmd/pkgsite@master & `
- `$ open http://localhost:8080`
- Enter "fmt", hit Return, see search results page.
- Click first link for package fmt
- Wait 17s for download of std@latest.
- See documentation for fmt.

Ideally we would eliminate step 5. Is it necessary to select std@latest when there's a recent version of std already already installed?

Perhaps std@installedversion could also be offered on the "Or browse local modules:" menu, since just as it is desirable for the docs to reflect the local edits to modules, so too it is desirable to show the version of Go that is installed locally.

Loosely related:
- https://github.com/golang/go/issues/51564
- https://github.com/golang/go/issues/38892
Repository: react-native
Issue: Wrong types in RCTDeviceEventEmitter
Labels: Needs: Triage :mag:,Newer Patch Available,Never gets stale

### Description

On a recent update of React Native we noticed that the export of `RCTDeviceEventEmitter` types is wrong.

After the update, the export in `.d.ts` has been changed to `export const`:

https://github.com/facebook/react-native/blob/cbc28da666c2d103242ad36caad577c69ecc430b/packages/react-native/Libraries/EventEmitter/RCTDeviceEventEmitter.d.ts#L28-L29

But in the `.js` file, the export still with `export default`:

https://github.com/facebook/react-native/blob/cbc28da666c2d103242ad36caad577c69ecc430b/packages/react-native/Libraries/EventEmitter/RCTDeviceEventEmitter.js#L31-L32


### React Native Version

0.71.8

### Output of `npx react-native info`

System:
    OS: macOS 13.2.1
    CPU: (8) arm64 Apple M1
    Memory: 102.47 MB / 8.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.16.0 - ~/.nvm/versions/node/v16.16.0/bin/node
    Yarn: 3.3.1 - ~/.nvm/versions/node/v16.16.0/bin/yarn
    npm: 8.11.0 - ~/.nvm/versions/node/v16.16.0/bin/npm
    Watchman: 2023.04.24.00 - /opt/homebrew/bin/watchman
  Managers:
    CocoaPods: 1.12.0 - /Users/douglas.junior/.rbenv/shims/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
    Android SDK:
      API Levels: 30, 31, 33, 33
      Build Tools: 30.0.2, 30.0.3, 31.0.0, 33.0.0, 34.0.0
      System Images: android-32 | Google APIs ARM 64 v8a, android-32 | Google Play ARM 64 v8a
      Android NDK: Not Found
  IDEs:
    Android Studio: 2022.1 AI-221.6008.13.2211.9477386
    Xcode: 14.2/14C18 - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.19 - /opt/homebrew/opt/openjdk@11/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 18.2.0 => 18.2.0 
    react-native: 0.71.7 => 0.71.7 
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

### Steps to reproduce

N/A

### Snack, code example, screenshot, or link to a repository

N/A
Repository: vscode
Issue: Support setting a badge-only color in file decorations
Labels: feature-request,tree-views

Today we can provide a `ThemeColor` to a file decoration, but it automatically applies to the text of the file as well as the badge.

There are cases where I really want the badge to have a color, but not affect the text itself.

Here is an example from the SCM view today that has color on the badges but not the text:

![image](https://github.com/microsoft/vscode/assets/641685/293164f2-1f31-424c-89df-b789e52ceb2a)

While in GitLens I want the `M` to be colored like the SCM view above, but not apply the same color to the text -- which I can't do today:

![image](https://github.com/microsoft/vscode/assets/641685/978ce375-7d16-4507-b0a4-77b7db684982)

My guess is that we don't want to add the ability to have a `badgeColor`, since then you could end up with different text colors and badge colors (though in some cases it would be nice, could lead to not great experiences), but rather add a `colorAppliesTo` property (or something similarly named) with values of `all` (default), `text`, `badge`.

/cc @alexr00 pinging you as I believe you are looking into badge changes for codicons in May
Repository: react
Issue: Bug: Don't crash the app if an async component is accidentally used on the client
Labels: Component: Suspense,React Core Team

We don't yet officially support async/await in client components. (Refer to the RFC for more details: https://github.com/acdlite/rfcs/blob/first-class-promises/text/0000-first-class-support-for-promises.md#why-cant-client-components-be-async-functions)


Confusingly, though, it does sometimes work, because the primitives are there to support it in the future.

However, if you accidentally render an async component on the client (for example, when refactoring a Server Component to a client one), React should fail gracefully. Right now, in some cases, it will instead crash the app by falling into an infinite loop.

Let's use this issue to track how we'll improve the DX for preventing async components (and async/await data fetching more generally) on the client.

This is _not_ about implementing support for async/await on the client. Although we will probably do that eventually, for now we're just focused on making it fail more gracefully.

In the meantime, if you're using a Server Components enabled framework like Next.js, you should prefer to do as much data fetching as possible in Server Components. For the remaining client cases, use an established framework like useSWR or React Query.

- [ ] Detect and prevent an infinite loop caused by when uncached promise is rendered outside of a Suspense boundary.
- [ ] Add a warning if an uncached promise is detected outside of a transition.
Repository: yt-dlp
Issue: Abort on playlist page error but not on playlist entry download error
Labels: bug,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 asking a question and **not** reporting a bug or requesting a feature
- [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 questions **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)

### Please make sure the question is worded well enough to be understood

Currently using ef8fb7f029b816dfc95600727d84400591a3b5c5

When downloading playlists/channels it sometimes happens that downloading the playlist pages (getting all the playlist metadata/playlist entries) has an error while trying to get one of those pages. I would like for yt-dlp do abort when that happens.
I know that can be achieved using `--abort-on-error`, however that has the downside that it also aborts when there is an error while trying to download a playlist entry. I would like for it to continue when there is an error with a playlist entry, but abort when there is an error while downloading the playlist pages.

Is there some way to achieve that?

Aborting when a playlist entry can't be downloaded is problematic for my use case, because some playlists/channels have entries that never or rarely work, and so aborting on those would mean that all the later entries that actually do work would never get downloaded.
The problem with not aborting on playlist page error is that the `playlist_index`/`playlist_autonumber` as well as the `playlist_count` are then wrong, which I use as part as the filename.

If there is currently no way to achieve that, this can be considered a feature request.

### Provide verbose output that clearly demonstrates the problem

- [ ] Run **your** yt-dlp command with **-vU** flag added (`yt-dlp -vU <your command line>`)
- [ ] If using API, add `'verbose': True` to `YoutubeDL` params instead
- [ ] Copy the WHOLE output (starting with `[debug] Command-line config`) and insert it below

### Complete Verbose Output

_No response_
Repository: pytorch
Issue: addmv doesn't do type promotion correctly,
Labels: triaged,module: type promotion,module: linear algebra

Google colab test:

Input:
```
input = torch.rand([3], dtype=torch.complex128, requires_grad=True)
vec1 = torch.rand([3, 2], dtype=torch.float64, requires_grad=True)
vec2 = torch.rand([2], dtype=torch.float64, requires_grad=True)

res = torch.Tensor.addmv(input, vec1, vec2)
desired_dtype = torch.promote_types(torch.complex128, torch.float64)
print(res.dtype)
print(desired_dtype)
```

Output:
```
torch.float64
torch.complex128
<ipython-input-3-e284f66968e0>:5: UserWarning: Casting complex values to real discards the imaginary part (Triggered internally at ../aten/src/ATen/native/Copy.cpp:276.)
  res = torch.Tensor.addmv(input, vec1, vec2)
```

_Originally posted by @gerhean in https://github.com/pytorch/pytorch/issues/99984#issuecomment-1542566779_
            

cc @nairbv @mruberry @jianyuh @nikitaved @pearu @walterddr @IvanYashchuk @xwang233 @Lezcano
Repository: rust
Issue: Tracking issue for MIR simplification opportunities
Labels: C-enhancement,A-mir-opt,C-optimization

This issue is designed to be a list of ideas to simplify MIR during optimization passes. Contributors are welcome to enhance this list.

Note: not all optimizations on this list are desirable. Some are put there to track why they were not implemented.

----
# Instruction simplification

Avoid calling `Index::index` for slices of arrays and subslices, and replace if with a direct projection:
- [ ] `slice[constant1..constant2]` to use `Subslice { from: constant1, to: constant2, from_end: false}`;
- [ ] `slice[..constant2]` to use `Subslice { from: 0, to: constant2, from_end: false}`;
- [ ] `slice[constant1..]` to use `Subslice { from: constant1, to: 0, from_end: true}`;
- [ ] `slice[..]` to directly reuse `slice`;
- [ ] `slice[constant1..slice.len() - constant2]` to use `Subslice { from: constant1, to: constant2, from_end: true}`;
- [ ] `slice[..slice.len() - constant2]` to use `Subslice { from: 0, to: constant2, from_end: true}`.
- [ ] replace manual pointer offset computations with `Index` projection https://github.com/rust-lang/rust/issues/111442#issuecomment-1555873794

Simple operations:
- [ ] replace `i binop j` by a statement directly in MIR, instead of inlining the trait method `<T as BinOp>::bin_op` https://github.com/rust-lang/rust/issues/111442#issuecomment-1543033549

Aggregates:
- [ ] Avoid constructing an aggregate just to project from it https://github.com/rust-lang/rust/issues/111442#issuecomment-1546960075
- [ ] Ensure calls to ADT constructors are always inlined.

Perform simplifications listed in clippy's perf lints https://github.com/rust-lang/rust/issues/111442#issuecomment-1546856748.

# Compile-time evaluation

- [ ] Pre-compute more in formatting internals https://github.com/rust-lang/rust/issues/111442#issuecomment-1543030481

# Control-flow graph

- [ ] Avoid an enum to switch on its discriminant just after https://github.com/rust-lang/rust/issues/111442#issuecomment-1546958336
- [x] Replace `SwitchInt(operand, [x -> bb, unreachable])` by assume + goto --> https://github.com/rust-lang/rust/pull/113970
- [ ] Merge switchInt-assert https://github.com/rust-lang/rust/issues/111442#issuecomment-1571569900
Repository: pytorch
Issue: Tensorboard graph tracing with torch fx API
Labels: triaged,module: tensorboard,module: fx

### 🚀 The feature, motivation and pitch

The current implementation of adding a model graph to tensorboard is not perfect:
- A brittle heuristic is used to assemble the scopes, in- and outputs of Modules and operations in the graph, based on strings extracted from the trace
- This leads to [silently](https://github.com/pytorch/pytorch/issues/33691) [wrong](https://github.com/pytorch/pytorch/issues/65652), [confusing](https://github.com/pytorch/pytorch/issues/39292) or [useless](https://github.com/pytorch/pytorch/issues/37387) graphs sometimes
- sometimes operations have duplicate inputs / outputs in the graph
- operations are labeled with a meaningless number instead of the name of the operation 
- in general, pytorch model graphs are just subpar compared to tensorflow models
- [The graphing breaks completely with zero-dim tensors](https://github.com/pytorch/pytorch/issues/88707)

🚀 My idea / feature request is now to build the tensorboard graph from a symbolic trace using the newer `torch.fx` API.
As I understand it, it contains all the necessary information and good scopes that help correct nesting of modules in the graph.
Graphing a general `fx` IR to a tensorboard may also be an excellent way of visually debugging `fx` transformations.

This maybe can also help with this issue, where some users want a model graph without having to provide concrete inputs values: #37334.

### Alternatives

- Continue using the status quo with the buggy parsing of torch jit traces
- Currently, the trace parsing discards `ClassType` nodes. Investigate if including information from these nodes may help create more accurate graphs

### Additional context

See some of the linked issues for images where the tensorboard graph is not satisfactory. 
The code for parsing the jit trace is here: https://github.com/pytorch/pytorch/blob/e9ebda29d87ce0916ab08c06ab26fd3766a870e5/torch/utils/tensorboard/_pytorch_graph.py#L236

cc @ezyang @SherlockNoMad @soumith @EikanWang @jgong5 @wenzhe-nrv
Repository: flutter
Issue: Check if existing successful build before triggering a new build in GitHub presubmit
Labels: team-infra,P2,triaged-infra

Github Presubmit check runs may miss updated even if they finish running, either due to cocoon backend issue, or GitHub incidents (more likely).

Current API `/api/reset-try-task` provides a way to trigger a new build to enable a status refresh. However, this API doesn't care if we have any successful build already.

To optimize the process, we can add a check. If there already an earlier passed build (on the same commit), we can simply update the status instead of waiting another build cycle.

Related: https://github.com/flutter/flutter/issues/126450
Repository: storybook
Issue: [Bug]: Vite builder assumes that root directory is parent directory of config dir
Labels: bug,has workaround,builder-vite,sev:S3

### Describe the bug

Vite builder incorrectly assumes that root directory for vite is the parent directory of the config directory:
https://github.com/storybookjs/storybook/blob/v7.0.10/code/lib/builder-vite/src/vite-config.ts#L55

However, you can have a directory layout like `.storybook/custom/main.ts` with the command `storybook dev -c .storybook/custom` which would cause the root directory to be set improperly.

In this case we would get the config:
```
root: path.resolve('.storybook/custom/', '..'),
```
instead of the expected resolved value of:
```
root: path.resolve('.storybook/', '..'),
```

### To Reproduce

_No response_

### System

```shell
Environment Info:

  System:
    OS: Windows 10 10.0.19044
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz
  Binaries:
    Node: 19.7.0 - C:\Program Files\nodejs\node.EXE
    npm: 9.6.5 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (113.0.1774.35)
  npmPackages:
    @storybook/addon-essentials: ^7.0.8 => 7.0.8
    @storybook/addon-interactions: ^7.0.8 => 7.0.8
    @storybook/addon-links: ^7.0.8 => 7.0.8
    @storybook/addon-storysource: ^7.0.8 => 7.0.8
    @storybook/react: ^7.0.8 => 7.0.8
    @storybook/react-vite: ^7.0.8 => 7.0.8
    @storybook/testing-library: ^0.1.0 => 0.1.0
```


### Additional context

_No response_