sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: x/pkgsite: wrong file links for submodules
Labels: pkgsite

### What is the URL of the page with the issue?
https://pkg.go.dev/dagger.io/dagger@v0.3.1#section-sourcefiles


### What is your user agent?

Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:106.0) Gecko/20100101 Firefox/106.0


### Screenshot
![Capture d’écran de 2022-11-09 12-27-37](https://user-images.githubusercontent.com/928722/200819164-7eab39ed-c246-405c-ac55-eacff5a85b27.png)



### What did you do?

Clicked on the `error.go` file link

### What did you expect to see?

It should have led me to: https://github.com/dagger/dagger/blob/sdk/go/v0.4.0/sdk/go/error.go

### What did you see instead?
https://github.com/dagger/dagger/tree/main/sdk/go/blob/v0.4.0/error.go

### Fix

```diff
- https://github.com/dagger/dagger/tree/main/sdk/go/blob/v0.4.0/error.go
+ https://github.com/dagger/dagger/blob/sdk/go/v0.4.0/sdk/go/error.go
```

### Issue

it seems when using a submodule with the correct way of tagging it (with a tag containing its subdirectory location), the pkgsite doesn't concatenate the relative to repository root path of the file, but only relative to its respective `go.mod` submodule.
Repository: go
Issue: runtime: threads and their Ms aren't released promptly enough in some case
Labels: NeedsInvestigation

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ 1.17

</pre>

### Does this issue reproduce with the latest release?

i don't know

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOOS="linux"
GOPATH="/root/go"
GOVERSION="go1.17"
GOHOSTARCH="amd64"
GOARCH="amd64"
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is best.
-->
Use pprof find thread is more than goroutine
![image](https://user-images.githubusercontent.com/68258235/200833010-9114cf30-1ed2-4260-a017-2d1eacbb2e29.png)
confirm the thread is 35 in os
![image](https://user-images.githubusercontent.com/68258235/200833088-346f0fdd-176a-4366-a8ae-e5bc4038deb6.png)

It result in the memory increase caused by runtime.allocm and it is not released
![image](https://user-images.githubusercontent.com/68258235/200833243-58c6bf6e-81b4-4eb6-8597-58cd68305ab7.png)


### What did you expect to see?
1、The number of threads decreases. 
2、Memory growth caused by runtime.allocm no longer occurs
### What did you see instead?
1、The number of threads is more than goroutine and not destroy. 
2、Memory growth caused by runtime.allocm  occurs
Repository: neovim
Issue: shada: cannot clear search register
Labels: bug,editor-state

### Neovim version (nvim -v)

v0.9.0-dev-1402+g49fbcb5b8-dirty

### Vim (not Nvim) behaves the same?

no

### Operating system/version

macOS 12.6

### Terminal name/version

alacritty

### $TERM environment variable

xterm-256color

### Installation

homebrew

### How to reproduce the issue

`let @/=''` is not clearing the search register.  When I press `n` it repopulates with the previous text.

I've tried putting in on an auto command for `VimEnter` and `VimLeave` to clear it but it can't be cleared.

I've also tried modifying and deleting main.shada but it is apparently not stored there because it comes back even if main.shada is deleted.

Where are registers saved to between nvim instances if they're not in main.shada?  I can't find any information about `@/` persistence in the `:help` pages.

### Expected behavior

I'm expecting the search register (`@/`) to be cleared.

### Actual behavior

It is not cleared and it persists between sessions.
Repository: next.js
Issue: Proxy rewrites don't work since NextJS@13
Labels: bug

### Verify canary release

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

### Provide environment information

```
   Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 22.1.0: Sun Oct  9 20:14:54 PDT 2022; root:xnu-8792.41.9~2/RELEASE_X86_64
    Binaries:
      Node: 16.18.0
      npm: 8.19.2
      Yarn: 1.22.19
      pnpm: 7.14.2
    Relevant packages:
      next: 13.0.3-canary.2
      eslint-config-next: 12.3.1
      react: 18.2.0
      react-dom: 18.2.0
```

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

Chrome 107.0.5304.87

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

_No response_

### Describe the Bug

We use several "rewrites" in the Next-Config to fetch data on client-side from the development domains. This worked in NextJS@12 like a charm, but since NextJS@13 the same config logs errors like these:

```
Failed to proxy https://app.development.<private>/api/search/attributes/query Error: read ECONNRESET
    at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20) {
  errno: -54,
  code: 'ECONNRESET',
  syscall: 'read'
}
```

The `<private>` was inserted by me, because it contains sensitive information. Opening the printed link in the browser works perfectly, too.

### Expected Behavior

The "rewrites" and proxies work as well as before the update to NextJS@13.

### Link to reproduction - Issues with a link to complete (but minimal) reproduction code will be addressed faster

https://stackblitz.com/edit/vercel-next-js-wv5cxn?file=next.config.js

### To Reproduce

1. Add in Next-Config:

```
rewrites: async () => [{
   source: '/api/:path*',
   destination: 'https://app.development.<private>/api/:path*',
   basePath: false,
}]
```

2. Add some code doing a GET request on client side with e.g. `fetch('/api/foo')`.
3. Start NextJS app and see that the proxy error appears.
Repository: PowerToys
Issue: Keyboard Manger key remap doesn't correctly apply to the Windows + V clipboard shortcut.
Labels: Issue-Bug,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.64.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

I have Left Control and Caps lock rebound using the Keyboard Manager Remap setting. this works as intended when opening the windows + V clipboard menu with zero issues. when selecting an object to paste, whether via enter or clicking via the mouse, it doesn't paste - instead opting to: toggle capslock, and simply put the character V.  Running as administrator makes no difference.

This to me suggests that windows isn't respecting the keyboard manager remapping, but I'm not familiar enough with either the program or it's codebase to make a more estimated guess than that. 

for Context, I have a Unicomp terminal keyboard, which doesn't abide by typical keycode layouts, hence me swapping ctrl and capslock.

### ✔️ Expected Behavior

Using the windows + v clipboard menu should abide by the remapped keys.


### ❌ Actual Behavior

it ignores it, resulting in an odd combo if your keyboard uses non standard key mapping.

### Other Software

_No response_
Repository: opencv
Issue: Using VAAPI decode and encode at the same time causes exception
Labels: bug,optimization,category: videoio

### System Information

OpenCV version: OpenCV 4.x branch (https://github.com/opencv/opencv/commit/2aad039b4f64d8e4a6136388c48d1368c120feec)
Operating System / Platform: openSUSE Tumbleweed (Version: 20221102)
Compiler & compiler version: g++ (SUSE Linux) 12.2.1 20221020 [revision 0aaef83351473e8f4eb774f8f999bbe87a4866d7]

### Detailed description

I would like to use VAAPI hardware acceleration for decoding and encoding at the same time but VAAPI context creation fails:

In short:
```
[ INFO:0@0.030] global /home/elchaschab/devel/opencv/modules/videoio/src/cap_ffmpeg_hw.hpp (580) hw_create_device FFMPEG: Exception creating OpenCL context with vaapi video acceleration
```

I dug throught the code and understood that, this was due to restrictions on using concurrent VADisplays (thought they might be displays of the same device). 

### Steps to reproduce

Build OpenCV 4.x with:
```bash
ccmake -DCMAKE_BUILD_TYPE=Debug -DWITH_OPENGL=ON -DWITH_FFMPEG=ON -DWITH_QT=ON -DOPENCV_FFMPEG_SKIP_BUILD_CHECK=ON -DWITH_VA=ON -DWITH_VA_INTEL=ON -DBUILD_PERF_TESTS=OFF -DBUILD_TESTS=OFF -DOPENCV_EXTRA_MODULES_PATH=../../opencv_contrib-4.x/modules/ ..
```

Clone and build my [example](https://github.com/kallaballa/OpenCV-Issues/blob/main/src/vaapi-decode-encode/vaapi-decode-encode.cpp):
```bash
git clone https://github.com/kallaballa/OpenCV-Issues.git
cd OpenCV-Issues
make
```
Run it on an example (attached) MJPEG file (stream copied from V4l2).
```bash
src/vaapi-decode-encode/vaapi-decode-encode example.mkv
```

The example file was created with following command:
```bash
ffmpeg -y -t 10 -video_size 1280x720 -input_format mjpeg -framerate 30 -i /dev/video1 -f matroska -c:v copy example.mkv
```

**Please rename to [example.mkv](https://user-images.githubusercontent.com/287266/200735621-e9788638-3fca-4c94-8708-1a93f3c9fb84.mp4)**

### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: rust
Issue: Casting to `dyn Trait` implies `'static` lifetime, but "lifetime may not live long enough" does not prompt
Labels: A-diagnostics,A-lifetimes,T-compiler,D-terse,A-trait-objects

<!--
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.

If you cannot produce a minimal reproduction case (something that would work in
isolation), please provide the steps or even link to a repository that causes
the problematic output to occur.
-->
This is taken from https://users.rust-lang.org/t/why-cant-i-use-reference-of-a-reference-in-the-current-scope-cast-requires-that-1-must-outlive-static/83983, but I think it's worth an issue to improve the diagnostic hints.

Given the following code: [Playground link](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=08abbe0e089f86d6ce42dbaf93c30b4f)

```rust
fn do_something<P: View>(parent: &Hierarchical<P>) {
    let h: &dyn View = parent;
}
```

The current output is: 

```
error: lifetime may not live long enough
  --> src/main.rs:62:24
   |
61 | fn do_something<P: View>(parent: &Hierarchical<P>) {
   |                          ------ has type `&Hierarchical<'1, P>`
62 |     let h: &dyn View = parent;
   |                        ^^^^^^ cast requires that `'1` must outlive `'static`
```

Ideally the output should look like:

```
error: lifetime may not live long enough
  --> src/main.rs:62:24
   |
61 | fn do_something<P: View>(parent: &Hierarchical<P>) {
   |                          ------ has type `&Hierarchical<'1, P>`
62 |     let h: &dyn View = parent;
   |                        ^^^^^^ cast requires that `'1` must outlive `'static`
   = note: `dyn View` without an explicit lifetime implies 'static, not '_
```

The idea is to have a note that tells you where `'static` came from in the error message, so that if a shorter lifetime is intended, the user is told where the problem comes from.
Repository: material-ui
Issue: [core] Scripts can't be used in other repositories
Labels: core,scope: code-infra

A continuation of https://github.com/mui/material-ui/pull/35036#discussion_r1017765723

Summary: some of our infrastructure scripts assume they are being run in the mui/material-ui repo. This makes it impossible to run them in the MUI X or Toolpad repos. Scripts should have the workspace root configurable.

Additionally, one way of making the scripts less coupled to Material UI would be to extract them into their own repository. All projects could then import them as a package (either from npm or using git).
Repository: rust
Issue: Support individual files for clippy tests
Labels: A-testsuite,E-mentor,T-bootstrap,E-medium,A-clippy

Clippy is a special snowflake and uses `TESTNAME` to tell it how to run individual tests instead of an argument to compiletest. Currently the only way to run individual tests is with `TESTNAME=ice-6250 x test src/tools/clippy --bless`. We should support `x test src/tools/clippy/tests/ice-6250.rs` as well.

https://github.com/rust-lang/rust/pull/103266 will help simplify this a little by supporting the same test arguments as in-tree compiletest, but it won't solve suite paths automatically. Suite code lives around https://github.com/rust-lang/rust/blob/51de2387dc8b0871a7bbb58f0c73ea7ca1d339e4/src/bootstrap/builder.rs#L480 - maybe we need to change `impl Step for Clippy` to use `suite_path`?

_Originally posted by @jyn514 in https://github.com/rust-lang/rust/issues/103636#issuecomment-1308928374_
      

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"reez12g"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: flutter
Issue: display_util does not show subbbuild duration
Labels: team-infra,P3,triaged-infra

Now that flutter builds are making heavy use of subbuilds we need to bring as much subbuild information as we can to the main build. One useful piece of information that is missing is subbuild duration.

![image](https://user-images.githubusercontent.com/54371434/200871938-c3364b71-9c30-46d0-8865-8264bd8cfe9b.png)
Repository: go
Issue: x/build: use cloud build to update docker images
Labels: Builders,NeedsFix

A number of our buildlets on Google Cloud Platform run in docker images. Rather than running manual commands for each image, we could kick off periodic cloud build jobs to build images, and then update builder configurations as necessary.

Regularly updating images would also help us match what user's are more likely using, and also allow us to create builders that are up to date with upcoming OS releases.
Repository: flutter
Issue: Skip adding multidex dependencies when targeting min android SDK >= 20
Labels: platform-android,P2,team-android,triaged-android

In https://github.com/flutter/flutter/pull/114660, it was discovered that `project.android.defaultConfig.minSdkVersion` returns null, thereby making the sdk version check always true. Always enabling multidex support is not harmful but is not necessary for Android API 20+
Repository: node
Issue: Replacing benchmark/compare.R with a JavaScript implementation
Labels: meta,benchmark

Since I updated to macOS Monterey and R 4.2+ I am no longer able to install the packages required by `compare.R`. I recently found out about https://github.com/targos/node-benchmark-compare (h/t @targos) and gave it a try, it worked very well for me. I think in the past we had discussion about replacing this script with a JS implementation, it didn't end up fruitful because of the lack of implementation of the statistical distribution required by the script. Now that seems to be solved already by https://github.com/nearform/node-cephes  (see https://github.com/nodejs/node/pull/44974#issuecomment-1275661186). So I am wondering if it's time to reopen the discussion.

I think we can basically just vendor in the node-benchmark-compare package into `tools/` or `benchmark/` and replace the command `cat results.csv | Rscript benchmark/compare.R` with `node-benchmark-compare results.csv` (both [the benchmark guide](https://github.com/nodejs/node/blob/main/doc/contributing/writing-and-running-benchmarks.md) and [the script used by the CI](https://github.com/nodejs/benchmarking/blob/master/experimental/benchmarks/community-benchmark/run.sh) need to be updated, though in the case of the latter we might have to un-archive the repo, or edit the CI config to point to somewhere else?)
Repository: vscode
Issue: New Color customization option editor.activeBackground
Labels: feature-request,themes,workbench-editors

<!-- ⚠️⚠️ 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. -->
Would it be possible to add a ```workbench.colorCustomizations ``` that only effects the background color for the active editor. So in addition to having editor.background which is the default editor background we can highlight the active editor with a different color so its easier to see which editor has focus. The tab active color customizations aren't a good solution.
Repository: svelte
Issue: Binded volume parameter returning undefined
Labels: bug,media elements

### Describe the bug

When using `bind:volume` on video (did not test on audio track), it returns undefined instead of a number from 0-1.

### Reproduction

REPL for reproduction based on media element bindings tutorial
REPL: https://svelte.dev/repl/d4acb0c4bf3e42efbc41d289f33ee359?version=3.52.0
^ Click on video and check console, you can keep clicking to see that it only returns undefined.
Tutorial: https://svelte.dev/tutorial/media-elements

### Logs

_No response_

### System Info

```shell
System:
    OS: macOS 13.0
    CPU: (8) arm64 Apple M1
    Memory: 687.88 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.0.0 - /usr/local/bin/node
    Yarn: 1.22.19 - ~/.yarn/bin/yarn
    npm: 8.6.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 107.0.5304.110
    Safari: 16.1
  npmPackages:
    svelte: ^3.52.0 => 3.52.0
```


### Severity

annoyance
Repository: youtube-dl
Issue: [archiveorg] BuzzVideo
Labels: site-support-request,patch-available

<!--

######################################################################
  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:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2021.12.17. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that site you are requesting is not dedicated to copyright infringement, see https://yt-dl.org/copyright-infringement. youtube-dl does not support such sites. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
- Search the bugtracker for similar site support requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm reporting a new site support request
- [x] I've verified that I'm running youtube-dl version **2021.12.17**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [x] I've checked that none of provided URLs violate any copyrights
- [x] I've searched the bugtracker for similar site support requests including closed ones


## Example URLs

<!--
Provide all kinds of example URLs support for which should be included. Replace following example URLs by yours.
-->

- https://www.buzzvideo.com/article/i7157121376749797894?referer=foryou&pid=website_feed (Video)
- https://www.buzzvideo.com/feed/foryou (For You Page)

## Description

<!--
Provide any additional information.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->

Buzzvideo is a video sharing site that is shutting down on December, 31, 2022. For me, the primary use of this future extractor will to archive the videos and metadata. The ArchiveTeam already knows about this site, and I got the news from them. It is really hard to archive a fragment-based video site without youtube-dl (or it's forks).
Repository: vscode
Issue: Allow more control of the status bar text for a LanguageStatusItem
Labels: feature-request,languages-basic,ux,under-discussion

I'm trying to adopt the LanguageStatusItem API for some things that were previously just standard status bar entries, however the way the text is rendering makes it a much worse experience than before even if when items are pinned.

For example, in Flutter we currently show the selected device on the status bar:

<img width="251" alt="Screenshot 2022-11-09 at 18 07 26" src="https://user-images.githubusercontent.com/1078012/200906940-4fd66eac-1689-4e76-bb8c-980f54c6d5c5.png">

There's a tooltip that tells you how many devices are connected. It isn't prefixed with "Flutter" because that consumers more space.

Using the new API, it's natural to set `text` to something like "Flutter Device" and `detail` to the device name:

![image](https://user-images.githubusercontent.com/1078012/200907278-0ea4a64b-5408-4083-82ae-dfa1ef1a22e0.png)

However if you want the original behaviour and you _pin_ the item, you just get "Flutter Device" and not what you really wanted:

![Screenshot 2022-11-09 at 18 10 03](https://user-images.githubusercontent.com/1078012/200907408-95352feb-af93-4a17-aae3-3fcfc16612cf.png)

And if we just set `text` to the device name, then the main flyout doesn't look so good because it doesn't have a description of what it is.

It would be nice if we could control the status bar text separately, otherwise we have to decide between a better experience, or users being able to collapse the item into the flyout. Right now for Flutter devices it feels like status bars are better (even though I'd like for users to be able to move it into the flyout).

Slightly related (and I can raise separate issues if worthy), things I'd also love:

- Add tooltips
- The ability for text/detail to be display like columns rather than just joined with a hyphen. The current layout in my screenshot above looks a bit messy and I think would look better if the `detail` fields were all lined up.
Repository: PowerToys
Issue: File comparison tool
Labels: Needs-Triage

### Description of the new feature / enhancement

There are many tools around that can do a file comparison (binary or text) around the web. Even tools like VSCode or VS have them. It may be useful to have some of those simple tools quickly around to compare different type of files, at least it's metadata when we talk about multimedia files, and text comparison for any code/text file.

### Scenario when this would be used?

For every file on our Windows system.

### Supporting information

_No response_
Repository: PowerToys
Issue: Locate "In Use" process or app when dismounting a USB drive.
Labels: Needs-Triage

### Description of the new feature / enhancement

Show user what process or application is preventing dismount of a USB drive.
Allow user to terminate that process, or force it to disconnect from the drive.

### Scenario when this would be used?

Frequently, when dismounting a USB stick or external drive, the OS claims the drive is "in use" by some unspecified process. Often this appears to be untrue. For example, a VeraCrypt file is mounted and then dismounted, and no other action was performed on the USB stick. But the OS claims the stick is still in use. Since there is no known process attached to the drive, I end up removing it, always without any apparent consequences. But this may be risky, and it would be preferable to know WHY the OS thinks the drive is in use!

### Supporting information

_No response_