sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Unclear error message when using recursive future with tokio::spawn
Labels: A-diagnostics,T-compiler,E-help-wanted,A-async-await,AsyncAwait-Triaged

### Code

```Rust
async fn tokio_fact(n: u32)  -> u32 {
    if n <= 1 {
        return n;
    } else {
        let jh = tokio::spawn(tokio_fact(n-1));
        jh.await.unwrap() * n
    }
}
```


### Current output

```Shell
error[E0391]: cycle detected when computing type of `tokio_fact::{opaque#0}`
   --> a/src/main.rs:99:33
    |
99  | async fn tokio_fact(n: u32)  -> u32 {
    |                                 ^^^
    |
note: ...which requires borrow-checking `tokio_fact`...
   --> a/src/main.rs:99:1
    |
99  | async fn tokio_fact(n: u32)  -> u32 {
    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: ...which requires promoting constants in MIR for `tokio_fact`...
   --> a/src/main.rs:99:1
    |
99  | async fn tokio_fact(n: u32)  -> u32 {
    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: ...which requires preparing `tokio_fact` for borrow checking...
   --> a/src/main.rs:99:1
    |
99  | async fn tokio_fact(n: u32)  -> u32 {
    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: ...which requires unsafety-checking `tokio_fact`...
   --> a/src/main.rs:99:1
    |
99  | async fn tokio_fact(n: u32)  -> u32 {
    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: ...which requires building MIR for `tokio_fact`...
   --> a/src/main.rs:99:1
    |
99  | async fn tokio_fact(n: u32)  -> u32 {
    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: ...which requires match-checking `tokio_fact`...
   --> a/src/main.rs:99:1
    |
99  | async fn tokio_fact(n: u32)  -> u32 {
    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: ...which requires building THIR for `tokio_fact`...
   --> a/src/main.rs:99:1
    |
99  | async fn tokio_fact(n: u32)  -> u32 {
    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: ...which requires type-checking `tokio_fact`...
   --> a/src/main.rs:103:18
    |
103 |         let jh = tokio::spawn(tokio_fact(n-1));
    |                  ^^^^^^^^^^^^
    = note: ...which requires evaluating trait selection obligation `tokio_fact::{opaque#0}: core::marker::Send`...
    = note: ...which again requires computing type of `tokio_fact::{opaque#0}`, completing the cycle
```


### Desired output


I'm not sure what should be the proper error message. Because of the `tokio::spawn` this is not the same problem as in [E0733](https://doc.rust-lang.org/error_codes/E0733.html).

The workaround often proposed by @Darksonn on various forums is to use a wrapping non-async function:

```rust
async fn tokio_fact_bis(n: u32)  -> u32 {
    if n <= 1 {
        return n;
    } else {
        fn tokio_fact_wrap(n : u32) -> JoinHandle<u32> {
            tokio::spawn(tokio_fact_bis(n))
        }
        let jh = tokio_fact_wrap(n-1);
        jh.await.unwrap() * n
    }
}
```


### Rationale and extra context

_No response_

### Other cases

_No response_

### Anything else?

_No response_
Repository: pytorch
Issue: Building NCCL with `make -l $MAX_JOBS` slows down builds
Labels: module: build,triaged

We build NCCL with a cpu load limit (see https://github.com/pytorch/pytorch/blame/main/cmake/External/nccl.cmake#L37) to avoid OOMs, but this has some unfortunate consequences for devs using Meta-managed devservers.  Mine has lots of RAM and CPU, but is very "noisy" with background processes (I currently have a 3% cpu utilization but a load average of 137).  I think `make -l` inspects the latter number, and essentially decides to play it safe and build NCCL serially.

The end result?  My e2e clean build time is 17m50s, but if I remove `-l` it drops to 6m20s.  (This is with no particular build time optimizations either!)

I'd like to find a way to keep the OOM-avoidance properties of `-l` for users that need them, while not unnecessarily penalizing developers with big, noisy boxes (i.e. most Meta engineers :-p )

cc @malfet @seemethere @peterbell10 @huydhn since y'all have worked on this area in the past :-)
Repository: PowerToys
Issue: [MWB] Reduce logs size
Labels: Issue-Bug,Idea-Enhancement,Product-Mouse Without Borders

### Microsoft PowerToys version

0.70.1

### Installation method

GitHub, PowerToys auto-update, Microsoft Store, Chocolatey, Scoop, Dev build in Visual Studio, Other (please specify in "Steps to Reproduce")

### Running as admin

No

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

Mouse Without Borders produces 5MB daily logs due to how settings.json is handled atm. However, we cannot just disable this log message because it's in the common code. A better way to fix this would be to change the access pattern to that file to reduce the error count in the first place.

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: terminal
Issue: Allow changing the browser/app used to open clicked hyperlinks
Labels: Issue-Feature,Area-Extensibility,Product-Terminal

# Description of the new feature/enhancement

I'd like to be able to change the browser used by a Terminal's profile when clicking links. I use my laptop frequently to SSH into my development machine for work. Most all of our tools require 2FA and will print links to authenticate when their tokens expire. I have a separate browser for work stuff that has a profile managed by our IT team. I don't want to change my default browser so that links from Terminal open in the right place, since that would affect Outlook and stuff.

# Proposed technical implementation details (optional)

Looking at the code, I see all it does is essentially shell out to `open` with the URI in TermainalPage.cpp. I'd like a configuration option 
 to change this to explicitly use a browser or call my own powershell script to handle it. The default should probably just stay as a shell to `open`, especially if people are wanting to open e.g. `vscode://` or other URIs.

There's a feature request for custom URI handlers that I think could be used in combination with this to leverage the smarter dispatch in Terminal itself, basically "if URI matches pattern, open via this app". 

If this seems relatively straightforward and there's a couple PRs you can point me at for adding a configuration option, I can take a stab at a PR to implement this, since this is a daily itch I'd like scratched. But what would take me a couple days would probably take the team a few hours to do better, so if this requires more nuance in the implementation, feel free to triage this as normal.
Repository: pytorch
Issue: Unlocking PyTorch's Power: README.md in Multiple Languages! 
Labels: triaged,topic: new features,topic: docs

### 📚 The doc issue

We are a diverse group of students, each with different cultural backgrounds. As newcomers to the world of PyTorch, we realized the importance of having the README documentation available in our native languages.


### Suggest a potential alternative/fix

If you find our idea interesting and relevant, we would be happy to submit a pull request with the completed translations from our forked version of the project. We have already taken the initiative to translate the documentation into different languages, including German, Portuguese, Arabic, and Turkish, to ensure that beginners from diverse backgrounds can benefit from a localized experience.

By merging our translations into the main project, we can contribute to making PyTorch more accessible and user-friendly for a wider audience. We believe that providing comprehensive documentation in multiple languages will empower individuals to grasp the concepts more efficiently and foster a sense of inclusivity within the PyTorch community.

We look forward to your response and the opportunity to collaborate in making PyTorch a globally accessible resource for aspiring learners.

We encourage individuals from other nationalities to join us in this effort, extending the benefits to their own communities and facilitating the learning experience for everyone. Let's collaborate and contribute to a more inclusive and user-friendly PyTorch community.
Repository: next.js
Issue: Route handler responses not cached statically
Labels: bug

### 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: x64
      Version: Darwin Kernel Version 22.5.0: Mon Apr 24 20:51:50 PDT 2023; root:xnu-8796.121.2~5/RELEASE_X86_64
    Binaries:
      Node: 16.14.0
      npm: 8.19.2
      Yarn: 1.22.19
      pnpm: 8.2.0
    Relevant packages:
      next: 13.4.5-canary.2
      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)

_No response_

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/rijk/repro-handler-routing

### To Reproduce

1. Go to https://repro-handler-routing.vercel.app/b/test.txt
2. Note header `x-vercel-cache: STALE` (no matter the age)
3. Reload, observe timestamp changing

### Describe the Bug

Per the [revalidate docs](https://nextjs.org/docs/app/api-reference/file-conventions/route-segment-config#revalidate), the default value of `false` should behave as follows:

> Semantically equivalent to `revalidate: Infinity` which effectively means the resource should be cached indefinitely.

However, this result is revalidated on every request, even though no dynamic functions or fetch calls are done. This seems more like the behavior described for `revalidate: 0`.

### Expected Behavior

After the first request, the timestamp should never changed and always be returned from cache.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

Vercel
Repository: vscode
Issue: Disable global replace all if all files are readonly
Labels: bug,search,confirmed

>  The file-specific button is gone, but I'm wondering whether the general Replace All button next to the replace inputbox can also be disabled? Otherwise I can do the following:
> 
> 1. Open a GitHub Issues Notebook.
> 2. Search for a string specifically only in the output. Add a string in the replace inputbox.
> 3. Press the replace all button.
> 4. :bug: It claims that it was able to replace the string.
> 
> ![The file-specific button is gone, but there's still an enabled Replace All button](https://github.com/microsoft/vscode/assets/7199958/e603d77a-734d-4f81-8e7d-7177c43b2eb6)

_Originally posted by @rzhao271 in https://github.com/microsoft/vscode/issues/177808#issuecomment-1571046345_
Repository: flutter
Issue: [Web] CanvasKit error on web app after hot restart/hot reload
Labels: tool,engine,t: hot reload,customer: crowd,platform-web,e: web_canvaskit,has reproducible steps,P2,found in release: 3.10,found in release: 3.11,team-web,triaged-web

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Steps to reproduce

After performing multiple hot restarts or hot reloads in web app occurs error of CanvasKit. It doesn't crash the app, but it always persists in console.

I have seen old issues from 2021:
#https://github.com/flutter/flutter/issues/90231
#https://github.com/flutter/flutter/issues/90236
Both are closed as resolved in:
#flutter/engine#28675 

But in my case problem occurs now with the latest version of Flutter.

### Expected results

No errors

### Actual results

Error of CanvasKit

### Code sample

Just run any Flutter web app and preform multiple restarts/reloads. The problem occurs randomly after these steps.

### Screenshots or Video

<details>
<summary>Screenshots / Video demonstration</summary>

[Upload media here]

</details>


### Logs

<details><summary>Logs</summary>

```console
Error: Assertion failed: org-dartlang-sdk:///lib/_engine/engine/canvaskit/surface_factory.dart:148:12
_cache.contains(surface)
is not true
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 288:49      throw_
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 29:3        assertFailed
lib/_engine/engine/canvaskit/surface_factory.dart 148:35                          isLive
lib/_engine/engine/canvaskit/surface.dart 277:16                                  [_contextLostListener]
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 367:37  _checkAndCall
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 372:39  dcall
```

</details>


### Flutter Doctor output

<details><summary>Doctor output</summary>

```console
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.10.2, on macOS 13.3.1 22E261 darwin-arm64, locale ru-RU)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.1)
[✓] IntelliJ IDEA Ultimate Edition (version 2023.1.2)
[✓] IntelliJ IDEA Community Edition (version 2022.2)
[✓] VS Code (version 1.78.0)
[✓] Connected device (3 available)
[✓] Network resources

• No issues found!

```

</details>
Repository: flutter
Issue: Remove remaining uses of SkPictureRecorder and SkRTree
Labels: engine,P3,team-engine,triaged-engine

We should be using DisplayList mechanisms throughout all platforms and code paths. There are still a couple of platform modules that use the Skia mechanisms.

This will also allow us to remove flow/rtree.h,cc
Repository: godot
Issue: Crash when using GraphEdit `arrange_nodes()`
Labels: bug,needs testing,crash,topic:gui

### Godot version

v4.0.1.stable.official [cacf49999]
EDIT: v4.0.3.stable.official [5222a99f5] (I tested this error on 4.0.3, 4.0.2, and 4.0.1)

### System information

Linux 20.04 intel i7, Mac intel i7, Mac M1 (Compatibility and GLES2)

### Issue description

I can't find a way to request the feature. I'd like to request the feature to display the detail error. I'm using gdscript and I don't even know how to use C at all. 

The error is only able to display the error using command line. It doesn't show on the godot editor. See the video here:


https://github.com/godotengine/godot/assets/65916520/34b5cd24-6dad-4636-88f5-66dc886911ff

I'm able to see the error below:
![image](https://github.com/godotengine/godot/assets/65916520/05d4119f-28e1-4178-a639-c01bea163247)

```
javascript ip: <null> port: <null> full: <null>
connecting to: ws://127.0.0.1:9050
CORE FEAGI ROOTADDRESS: 127.0.0.1:8000
ERROR: Viewport Texture must be set to use it.
   at: get_size (scene/main/viewport.cpp:126)

```

Those are print from me plus the last error is known for so long time. It's been there since 3.1. It'snot the error I want to focus on.

The actual error is here:
`Segmentation fault (core dumped)`

I want to find the root of cause. I can't do that unless I go to C for that which I'm not quite familiar with C. I don't even know where to start.

So, I tried the log. See here:
```
bwuk@robots:~/ko/feagi/third_party/godot/godot_source$ cat .here.log 
{
	"core": 0.01215,
	"servers": 0.386833,
	"scene": 0.114149,
	"load_autoloads": 0.009495,
	"game_load": 0.461491,
	"total_time": 0.984909

```

Which doesn't tell me anything.

My request is to be able to provide more details than just this error.

### Steps to reproduce

Unfortunately, this occurs on my own code only. I was not able to re-produce the error on a new and simple project. 

### Minimal reproduction project

If you really need this as this code is only from my project: https://github.com/feagi/feagi/tree/feature-update-new-menu/third_party/godot/godot_source

Branch: *feature-update-new-menu*

It won't happen to others project, I doubt. I think this is not belong to request feature. Let me know if you are still wanting to use this godot project, I can give you a short list to make it running.
Repository: pytorch
Issue: Pytorch Build images for RISCV64 Devices in the nightly builds
Labels: module: build,feature,triaged

### 🚀 The feature, motivation and pitch

Please provide Nightly Builds for the RISCV64 CPU's in a similar fashion to the other nightly builds you provide.

### Alternatives

_No response_

### Additional context

_No response_

cc @malfet @seemethere
Repository: PowerToys
Issue: Installer crashes without any prompt when low disk space
Labels: Issue-Bug,Area-Setup/Install,Priority-3

### Microsoft PowerToys version

0.70.0

### Installation method

GitHub, PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

General

### Steps to reproduce

When running the update feature to update PowerToys to version 0.70.0, my disk C had very little free space.
During the update, the update window appeared, loaded a little and then closed down without any information. PowerToys was closed as well, without restart.

### ✔️ Expected Behavior

Inform the user that the installation/update cannot proceed due to low disk space.

### ❌ Actual Behavior

Updater together with the app crashes with no information whatsoever.

### Other Software

_No response_
Repository: go
Issue: cmd/go: document process for tagging and deleting a package from a module
Labels: Documentation,NeedsFix,modules

On occasions when we must delete a package from a repo, we would like to provide existing clients some way to continue to use it, even though it will never be updated again. One way to achieve that is to carve out a subdirectory of the repo module as a separate module, tag it with a version, and then delete it from the repo. This way the package is available indefinitely at its latest version even though it no longer exists in the main branch of the repo. This process was used for the cmd/cover tool (see #56783) and the go/pointer package (see #59676), both within the golang.org/x/tools repo.

However, the process requires a sequence of several rather subtle CLs and the creation of many tags (each of which carries a risk of hard-to-fix mistakes). We should document the theory and practice of this approach to make it easier in future, perhaps in https://go.dev/ref/mod, or in the Go wiki.

@bcmills
Repository: pytorch
Issue: Followup on the extra graph breaks for yolov3 model caused by layout optimization
Labels: triaged,module: inductor

### 🚀 The feature, motivation and pitch

Layout optimization increase graph breaks for yolov3 from 12 to 13. But number of unique graph breaks does not change.

Run 
```
python benchmarks/dynamo/torchbench.py --backend inductor --amp --accuracy --only yolov3 --training
```
And found the number of graph breaks to be 13 in the csv file. (unique number of graph breaks to be 7)

Disable layout optimization and rerun:
```
TORCHINDUCTOR_LAYOUT_OPTIMIZATION=0 python benchmarks/dynamo/torchbench.py --backend inductor --amp --accuracy --only yolov3 --training
```
We can found the number of graph breaks to be 12 in the csv file (unique number of graph breaks still to be 7).


### Alternatives

_No response_

### Additional context

_No response_

cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @Xia-Weiwen @wenzhe-nrv @jiayisunx @peterbell10 @ipiszy @ngimel
Repository: PowerToys
Issue: Screen Ruler
Labels: Idea-Enhancement,Needs-Triage,Product-Screen Ruler

### Description of the new feature / enhancement

This is good, how about the ability to measure an arbitrary area and not just a rectangular space?

### Scenario when this would be used?

measuring arbitrary shapes in images.

### Supporting information

_No response_
Repository: pytorch
Issue: Support In-place Triangular Matrix Multiplication
Labels: triaged,enhancement,module: linear algebra

### 🚀 The feature, motivation and pitch

The cuBLAS API supports Triangular Matrix Multiplication (trmm) https://docs.nvidia.com/cuda/cublas/index.html?highlight=trmm#cublasxt-t-trmm which is particularly cool because you can do `X = T X` _in-place!_.
The trmm function supports both upper and lower triangular matrices, and they can be stored in the same tensor T. (Using upper and lower half.)
This gives a nice way to do general matrix multiplication in-place using the LU-decomposition. Alternatively, if we are using an MLP we may just learn the triangular matrices L and U directly.

### Alternatives

For systems without cuda support, I believe BLAS also supports trmm.
It's always possible to just fall back to normal matrix mult and allocate a new matrix.

### Additional context

See also the discussion here about in-place matrix multiplication: https://stackoverflow.com/questions/25450809/is-there-an-algorithm-to-multiply-square-matrices-in-place

cc @jianyuh @nikitaved @pearu @mruberry @walterddr @IvanYashchuk @xwang233 @Lezcano
Repository: angular
Issue: ng-template gets rendered twice during hydration (when anchor comment node is not projected)
Labels: area: core,P4,core: hydration

### Which @angular/* package(s) are the source of the bug?

platform-browser

### Is this a regression?

No

### Description

when hydration is enabled and a component uses `ngTemplateOutlet` to render a template passed from a parent e.g. via `ContentChild` then its getting rendered twice for the duration of the hydration.

So it looks the like this if 'abc' is the template content
received from server
`abc`

during hydration
`abc abc` <-- this looks sometimes a bit ugly

after hydration
`abc`

So is it possible that the passed template gets just once rendered during the hydration process?


The relevant code parts for reprodruction:
```
<app-shell>
  <ng-template #customTemplate>
    <p>template</p>
  </ng-template>
</app-shell>
```

```
@Component({
  selector: 'app-shell',
  template: `<ng-container
    *ngIf="customTemplate"
    [ngTemplateOutlet]="customTemplate"
  ></ng-container>`,
  styles: [],
})
export class ShellComponent {
  @ContentChild('customTemplate', { static: true })
  customTemplate: TemplateRef<any> | null = null;
}

```

### Please provide a link to a minimal reproduction of the bug

https://github.com/michael-hein/hydration-ng-template

### Please provide the exception or error you saw

```true
N/A
```


### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 16.0.4        
Node: 18.16.0
Package Manager: npm 8.19.3
OS: win32 x64

Angular: 16.0.4
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, platform-server
... router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1600.4
@angular-devkit/build-angular   16.0.4
@angular-devkit/core            16.0.4
@angular-devkit/schematics      16.0.4
@nguniversal/builders           16.0.2
@nguniversal/express-engine     16.0.2
@schematics/angular             16.0.4
rxjs                            7.8.1
typescript                      4.9.5
```


### Anything else?

_No response_