sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Missing explicit lifetime in associated type suggests introducing invalid higher-ranked lifetime
Labels: A-diagnostics,T-compiler,A-suggestion-diagnostics,D-invalid-suggestion,S-has-mcve

### Code

```Rust
trait T {
    type Assoc;
}

fn foo<F>(t: F) where F: T<Assoc=&str> {}
```


### Current output

```Shell
error[E0637]: `&` without an explicit lifetime name cannot be used here
 --> src/main.rs:5:34
  |
5 | fn foo<F>(t: F) where F: T<Assoc=&str> {}
  |                                  ^ explicit lifetime name needed here
  |
help: consider introducing a higher-ranked lifetime here
  |
5 | fn foo<F>(t: F) where F: for<'a> T<Assoc=&'a str> {}
  |                          +++++++          ++
```


### Desired output

```Shell
error[E0637]: `&` without an explicit lifetime name cannot be used here
 --> src/main.rs:5:34
  |
5 | fn foo<F>(t: F) where F: T<Assoc=&str> {}
  |                                  ^ explicit lifetime name needed here
  |
help: consider adding an explicit lifetime here
  |
5 | fn foo<'a, F>(t: F) where F: T<Assoc=&'a str> {}
  |        ++                             ++
```


### Rationale and extra context

If you try to follow the suggested help text, it just gets you another error:
```
error[E0582]: binding for associated type `Assoc` references lifetime `'a`, which does not appear in the trait input types
  --> src/lib.rs:17:36
   |
5  | fn foo<F>(t: F) where F: for<'a> T<Assoc=&'a str> {}
   |                                    ^^^^^^^^^^^^^
```
i.e. it's not the correct course of action here

### Other cases

_No response_

### Rust Version

```Shell
❯ rustc --version --verbose
rustc 1.76.0 (07dca489a 2024-02-04)
binary: rustc
commit-hash: 07dca489ac2d933c78d3c5158e3f43beefeb02ce
commit-date: 2024-02-04
host: x86_64-pc-windows-msvc
release: 1.76.0
LLVM version: 17.0.6

But also verified to behave the same on nightly (2024-03-04 d18480b84fdbf1efc34f) on the playground
```


### Anything else?

_No response_

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: next.js
Issue: Metadata does not get generated for intercepting route if "useless" page file is missing
Labels: bug,Navigation

Edit:
- I have updated the reproduction code to include the latest canary version. 
- Also, the workaround differs to my initially proposed one. Thank you @felipedeboni!
  Oddly, the title of the issue still matches the problem. Although, you need to rename the `default.tsx` page to `page.tsx`.
- It looks like you need to have a page matching the root route as well as what you are intercepting, and default doesn't work.

### Link to the code that reproduces this issue

https://github.com/michaelschufi/nextjs-nextgram-intercepting-routes-metadata

### To Reproduce

1. Clone the repo and install it using, preferably, `pnpm`. I've used `pnpm@9.7.1`
2. Run the dev server.
3. Open the root page and click on an image.
4. Observe the browser tab's title not changing.

Closing and reopening a different modal does not work either.

You can also view the deployed non-working version here:
https://nextjs-nextgram-intercepting-routes-metadata.vercel.app/

To make it work:
1. Rename the `src/app/@modal/rename-me.tsx` file to `page.tsx`
2. Important: ⚠ Restart the dev server.
3. Open the root page and click on an image.
4. Observe the browser tab's title changing like intended.
6. Close the modal
7. Observe the browser tab's title changing back as intended.

### Current vs. Expected behavior

I expected the intercepting route to change the metadata regardless if I have a "useless" `page`-file in a catch-all route inside the slot.

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Fri Mar 29 23:14:13 UTC 2024
  Available memory (MB): 11967
  Available CPU cores: 8
Binaries:
  Node: 18.19.0
  npm: 10.2.3
  Yarn: N/A
  pnpm: 9.7.1
Relevant Packages:
  next: 15.0.0-canary.123
  eslint-config-next: N/A
  react: 19.0.0-rc-1eaccd82-20240816
  react-dom: 19.0.0-rc-1eaccd82-20240816
  typescript: 5.1.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

App Router, Metadata (metadata, generateMetadata, next/head), Routing (next/router, next/navigation, next/link)

### Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local), Vercel (Deployed)

### Additional context

Possibly related to the fixed #58123 issue.
Repository: PowerToys
Issue: Window placement and zones messed up on secondary monitor state change (but not even used for the desktop)
Labels: Issue-Bug,Product-FancyZones,Needs-Triage

### Microsoft PowerToys version

0.79.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

FancyZones

### Steps to reproduce

Main monitor connected and only one in actual use by the OS.
Secondary monitor (TV with an HDMI ARC AV receiver) connected but not in use with by the OS.

TV out of stand by (thus turning the receiver on), secondary monitor handshakes as usual with the PC. 
Same goes if putting TV in standby (thus turning the receiver off), secondary monitor handshaking again.

### ✔️ Expected Behavior

Windows and zones not to be messed up at all, just like prior to 0.79.0

### ❌ Actual Behavior

Since 0.79.0, On this very event window placement (+ size and zoom levels) and zones then get all messed up despite no actual OS level desktop settings changes.. (nor any changeq in NVCP)

By messed up regarding the zones themselves, I mean moving the windows back to their targeted zones (win+left/right) isn't always effective (maybe depending on the selected layout - didn't test further than that).
[PowerToysReport_2024-03-05-16-14-27.zip](https://github.com/microsoft/PowerToys/files/14497391/PowerToysReport_2024-03-05-16-14-27.zip)


### Other Software

_No response_
Repository: transformers
Issue: Make model compatible with `torch.func`
Labels: Feature request

Hi there,

I am trying to use DebertaV3 as an alternative to BERT for an experiment that requires `torch.func` transformations. However, since Deberta implementation relies on a [`torch.autograd.Function`](https://pytorch.org/docs/master/autograd.html#torch.autograd.Function), `torch.func` is not able to transform it. I get the following error

```bash
RuntimeError: In order to use an autograd.Function with functorch transforms 
  (vmap, grad, jvp, jacrev, ...), it must override the setup_context staticmethod. 
  For more details, please see https://pytorch.org/docs/master/notes/extending.func.html
```

The responsible lines are the classes implementing a `torch.autograd.Function`, for example

https://github.com/huggingface/transformers/blob/a69cbf4e64c7bc054d814d64f6877180f7cd3a25/src/transformers/models/deberta_v2/modeling_deberta_v2.py#L79

which according to the PyTorch documentation ([https://pytorch.org/docs/master/notes/extending.func.html](https://pytorch.org/docs/master/notes/extending.func.html)) must implement a

```python
@staticmethod
    def setup_context(ctx, inputs, output):
        ...
```

method. 

Would it be possible to update this implementation to make it compatible with function transformations?
Repository: TypeScript
Issue: Error message displays computed name '[attr]' instead of key value 
Labels: Suggestion,Help Wanted,Experience Enhancement

### 🔎 Search Terms

computed property, error message

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about computed properties


### ⏯ Playground Link

https://tsplay.dev/WyV2bw

### 💻 Code

```ts
type Unit =
  | {
      name: string;
      stength: number;
    }
  | {
      name: string;
      magic: number;
    };

const createUnit = (
  name: string,
  attr: "strength" | "magic",
  power: number,
): Unit => {
  return attr === "strength"
    ? { name, [attr]: power } // <-- error here
    : { name, [attr]: power };
};
```


### 🙁 Actual behavior

Error message displays "Object literal may only specify known properties, and '[attr]' does not exist in type 'Unit'".

### 🙂 Expected behavior

Error message should display that "strength" doesn't exist on Unit. (and possibly even recommend "stength" instead)

### Additional information about the issue

_No response_
Repository: transformers
Issue: Implementing the features of the TextStreamer into the pipeline
Labels: Feature request

### Feature request

It should be possible to format the output of a transformers.pipeline.

```
streamer = TextStreamer(tokenizer, skip_prompt=True, skip_special_tokens=True)

llm = pipeline(
    task="text-generation",
    model=model,
    tokenizer=tokenizer,
    return_full_text=True,
    generation_config=generation_config,
    eos_token_id=tokenizer.eos_token_id,
    pad_token_id=tokenizer.eos_token_id,
    streamer=streamer
)

prompt = "
 ... 
"

result = llm(prompt)
```
The problem is that the result variable contains the prompt and the special tokens.

### Motivation

When you use a transformers.pipeline, you can use a TextStreamer object to skip the prompt and the special tokens. **The problem is that the result is print on the standard output**. I haven't found a way to have this result as the output of the pipeline. I tried to apply batch_decode from the tokenizer on the model output, but the parameter skip_special_tokens didn't work.

### Your contribution

N/A
Repository: go
Issue: cmd/go/internal/modload: `MainModuleSet.DirImportPath` does not check module boundaries
Labels: GoCommand,modules,FixPending

### Go version

5dcc04aeacdaa78cc431e3f8b2119d2f351685b5

### Output of `go env` in your module/workspace:

```shell
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/usr/local/google/home/bcmills/.cache/go-build'
GOENV='/usr/local/google/home/bcmills/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/tmp/tmp.JAmBbk4Nn9/.gopath/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/tmp/tmp.JAmBbk4Nn9/.gopath'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/usr/local/google/home/bcmills/sdk/gotip'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='local'
GOTOOLDIR='/usr/local/google/home/bcmills/sdk/gotip/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='devel go1.23-5dcc04ae Mon Mar 4 21:01:23 2024 +0000'
GODEBUG=''
GCCGO='/usr/bin/gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='c++'
CGO_ENABLED='1'
GOMOD='/tmp/tmp.JAmBbk4Nn9/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build4217272553=/tmp/go-build -gno-record-gcc-switches'
```


### What did you do?

Reviewed test failures on pending https://go.dev/cl/567435.

Noticed an existing bug in `modload.MainModuleSet.DirImportPath` introduced in https://go.dev/cl/129798 (for #27022).

Reproduced the bug as follows:
```
go build testdata/q/q.go

-- go.mod --
module example

go 1.23

require (
	testdata/q v0.1.0
)

replace (
	testdata/q => ./testdata/q
)
-- internal/p/p.go --
package p
-- testdata/q/go.mod --
module testdata/q

go 1.23
-- testdata/q/q.go --
package q

import _ "example/internal/p"
```

### What did you see happen?

```
$ go build ./testdata/q/q.go

```
(no error)

### What did you expect to see?

An error, because (per the behavior agreed upon in #23970) a package in the module `testdata/q` should not be allowed to import an `internal` module from a module that does not share its import path.

Per https://go.dev/cl/129798:
> In GOPATH mode the rule has always been that 'go run x.go' can
> import whatever the package in x.go's directory would be able to
> import. Apply the same rule here.

`go build testdata/q` confirms that the package in `q.go`'s directory is _not_ allowed to import that package:
```
$ go build testdata/q
package testdata/q
        testdata/q/q.go:3:8: use of internal package example/internal/p not allowed
```

The underlying problem is that `DirImportPath` is just checking for a file path prefix, not using `modload.dirInModule` to properly check that the directory is contained in the module without intervening `go.mod` files carving out module boundaries.

(CC @matloob @samthanawalla)
Repository: vscode
Issue: Add context menu to comments in comments panel to un/resolve conversation
Labels: feature-request,api,api-finalization

It would be nice to be able to right click a comment in the comments panel to resolve it. This is especially useful when the file got deleted in which the comment is located.
Repository: flutter
Issue: [embedder api] Vulkan External Resources
Labels: c: new feature,engine,e: embedder,c: proposal,P3,team-engine,triaged-engine

### Use case

Per discussion on Discord - Use case gaps in order to switch to external embedder Vulkan backend

Vulkan external VkImage Support
1.  GL interop.  Same or different process.  Source could be anything that inherently requires GL/GLES/EGL.
2.  GStreamer pipeline output. Pipeline creates Vulkan objects directly via vulkanupload pipeline stage.   Same or different process.  Example pipeline which exposes VkImage to CPU:
https://gist.github.com/jwinarske/dda0f7154a0bf34c3e7b6606907ad0f7
3.  Present render target (VkImage) from (Unity, Filament, etc).
4.  libcamera - source format is determined by the Camera sensor, and has to be determined at runtime.

External processes would have an array of VkImages available to present.

### Proposal

The proposal is to adopt the OpenGL external Texture pattern for Vulkan.  This would allow re-use of the TextureWidget.  

GL Texture API:

    FlutterEngineRegisterExternalTexture
    FlutterEngineUnregisterExternalTexture
    FlutterEngineMarkExternalTextureFrameAvailable

TextureFrameCallback would need to be updated to include VkImageInfo which describes the backing VkImage.  Skia GrVkImageInfo is used to construct a GrBackendTexture.
Repository: PowerToys
Issue: Color picker -  enable scrolling mouse in color picker
Labels: Idea-Enhancement,Status-In progress,Area-User Interface,Product-Color Picker

### Description of the new feature / enhancement

Now, to select a previous color you have to use the scroll bar, It would be great if it also works with mouse scrolling

### Scenario when this would be used?

in all

### Supporting information

_No response_
```[tasklist]
### Tasks
```
Repository: material-ui
Issue: [material-ui] Restructure so nested slots are not needed
Labels: package: material-ui

Raised in https://github.com/mui/material-ui/issues/41205#issuecomment-1960706713

Restructure components, so none have nested slots (i.e., `slotProps.<levelOneSlot>.slots.<levelTwoSlot>`). This is to make the API more straightforward to use and maintain. Joy UI follows this pattern.

**Search keywords**:
Repository: vscode
Issue: Programmatically setting focus causes custom hover to show
Labels: bug,workbench-actions,workbench-hover

![Recording 2024-03-05 at 19 24 57](https://github.com/microsoft/vscode/assets/900690/305ab228-f37d-45ad-9d5f-6542577fb351)
Repository: opencv
Issue: Oak-D DepthAI with OpenCV 4.9.0 on Windows
Labels: bug,category: build/install,category: g-api / gapi

### System Information

OpenCV version: 4.9.0
Operating System: Windows 10
depthai-core: https://github.com/luxonis/depthai-core/releases/tag/v2.24.0

### Detailed description

I'm attempting to utilize OpenCV with Oak-D integration (depthai-core), and to do so, I'm following this tutorial: https://docs.opencv.org/4.9.0/df/d88/tutorial_gapi_oak_devices.html

However, upon running CMake with the -DWITH_OAK=ON flag, I don't see any mention of "oak" in the CMake log. It seems like it's not even attempting to search for it. Could you provide some assistance?

### Steps to reproduce

This is the cmake flags that I'm using:

cmake .. -DBUILD_opencv_apps=OFF -DBUILD_opencv_aruco=ON -DBUILD_opencv_bgsegm=OFF -DBUILD_opencv_bioinspired=OFF -DBUILD_opencv_calib3d=ON -DBUILD_opencv_ccalib=ON -DBUILD_opencv_core=ON -DBUILD_opencv_datasets=OFF -DBUILD_opencv_dnn=ON -DBUILD_opencv_dnn_objdetect=OFF -DBUILD_opencv_dnn_superres=OFF -DBUILD_opencv_dpm=OFF -DBUILD_opencv_face=OFF -DBUILD_opencv_features2d=ON -DBUILD_opencv_flann=ON -DBUILD_opencv_fuzzy=OFF -DBUILD_opencv_gapi=OFF -DBUILD_opencv_hfs=OFF -DBUILD_opencv_highgui=ON -DBUILD_opencv_img_hash=ON -DBUILD_opencv_imgcodecs=ON -DBUILD_opencv_imgproc=ON -DBUILD_opencv_intensity_transform=OFF -DBUILD_java_bindings_generator=OFF -DBUILD_opencv_js=OFF -DBUILD_opencv_line_descriptor=OFF -DBUILD_opencv_mcc=OFF -DBUILD_opencv_ml=ON -DBUILD_opencv_objc_bindings_generator=OFF -DBUILD_opencv_objdetect=ON -DBUILD_opencv_optflow=OFF -DBUILD_opencv_phase_unwrapping=OFF -DBUILD_opencv_photo=ON -DBUILD_opencv_plot=ON -DBUILD_opencv_python3=OFF -DBUILD_opencv_python_bindings_generator=OFF -DBUILD_opencv_python_tests=OFF -DBUILD_opencv_quality=OFF -DBUILD_opencv_rapid=OFF -DBUILD_opencv_reg=OFF -DBUILD_opencv_rgdb=OFF -DBUILD_opencv_saliency=OFF -DBUILD_opencv_shape=OFF -DBUILD_opencv_stereo=OFF -DBUILD_opencv_stitching=OFF -DBUILD_opencv_structured_light=OFF -DBUILD_opencv_superres=OFF -DBUILD_opencv_surface_matching=OFF -DBUILD_opencv_text=OFF -DBUILD_opencv_tracking=ON -DBUILD_opencv_ts=OFF -DBUILD_opencv_video=ON -DBUILD_opencv_videoio=ON -DBUILD_opencv_videostab=OFF -DBUILD_opencv_world=ON -DBUILD_opencv_xfeatures2d=ON -DBUILD_opencv_ximgproc=ON -DBUILD_opencv_xobjdetect=ON -DBUILD_opencv_xphoto=ON -DCMAKE_CONFIGURATION_TYPES=Release -DCMAKE_GENERATOR_PLATFORM=x64 -T v142 -DWITH_FFMPEG=ON -DWITH_INF_ENGINE=ON -DENABLE_CXX11=ON -DOPENCV_ENABLE_NONFREE=OFF -DBUILD_JAVA=OFF -DWITH_MSMF=OFF -DWITH_MSMF_DXVA=OFF -DOPENCV_EXTRA_MODULES_PATH="C:/Users/cesar.gouveia/Projects/OpenCV-Package/opencv_contrib/modules" -DBUILD_ZLIB=ON -DBUILD_opencv_hdf=OFF **-DWITH_OAK=ON**

### 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: transformers
Issue: BASED 
Labels: New model

### Model description

BASED is an attention model which combines sliding window attention and global linear attention to capture similar dependencies to transformers in a subquadratic model.  

It outperforms other similar models such as Mamba.



### Open source status

- [X] The model implementation is available
- [X] The model weights are available

### Provide useful links for the implementation

- [GitHub Repository](https://github.com/HazyResearch/based)
- Model Weights: [360m](https://huggingface.co/hazyresearch/based-360m), [1b](https://huggingface.co/hazyresearch/based-1b)
Repository: PowerToys
Issue: A Way To Collect and Print Power Toys Shortcuts For Reference
Labels: Idea-Enhancement,Idea-New PowerToy,Product-Shortcut Guide,Status-In progress,Needs-Triage,Needs-Team-Response

### Description of the new feature / enhancement

There are so many cool features in here but there's no way to memorize all the short cuts and having to manually assemble a document, either thru screen grabs or lifting text, seems kind of counter intuitive for software meant to make Windows more user friendly

### Scenario when this would be used?

When getting familiar with all the app has to offer and then every day after, by having a printed reference of ONLY the shortcuts/features one wants.

### Supporting information

_No response_
Repository: flutter
Issue: [Impeller] Android Hardware Buffer with YUV conversion tests are incorrect.
Labels: P2,team-engine,triaged-engine

Triaged as positive in https://github.com/flutter/engine/pull/50730, the external texture tests are known to be incorrect but still marked positive to work around the emulator issues tracked in https://github.com/flutter/flutter/issues/144232.

Once the emulator issues are fixed and/or the cause is determined to be an issue in the implementation, the digests must be marked negative.

The following tests should have their digests reviewed:

* ExternalTextureTests_testCanvasSurface
* ExternalTextureTests_testMediaSurface
* ExternalTextureTests_testRotatedMediaSurface_90
* ExternalTextureTests_testRotatedMediaSurface_180
* ExternalTextureTests_testRotatedMediaSurface_270
* ExternalTextureTests_testCroppedMediaSurface_bottomLeft
* ExternalTextureTests_testCroppedMediaSurface_topRight
* ExternalTextureTests_testCroppedRotatedMediaSurface_bottomLeft_90

The errors should look like the following:
<img width="1818" alt="309916442-c22669f0-c0a4-4a57-82be-e883728c9b57" src="https://github.com/flutter/flutter/assets/44085/d04e8638-f693-40e3-8842-12660e641d19">
Repository: vscode
Issue: Sticky Scroll: Rust functions with multiple lines
Labels: under-discussion,editor-sticky-scroll

Functions in Rust that span multiple lines are not shown correctly, regardless of the `editor.stickyScroll.maxLineCount` setting. For example, this:
<img width="443" alt="image" src="https://github.com/microsoft/vscode/assets/6652853/d7ea3a09-7c88-46c1-8e49-7515778f4159">

Shows up as this, which makes the parameters disappear completely:
<img width="396" alt="image" src="https://github.com/microsoft/vscode/assets/6652853/37470d45-6825-4c98-8a44-1e27ff9bac8d">

The same occurs with functions that contain a `where` clause:
<img width="667" alt="image" src="https://github.com/microsoft/vscode/assets/6652853/c2fe6dc1-ff88-4740-b3e4-cbe86dfd777c">

Shows up as this, which makes the type bounds disappear completely:
<img width="685" alt="image" src="https://github.com/microsoft/vscode/assets/6652853/e88f2981-d848-4131-8cb8-3c65f5153b67">

Both are very bad and ruin the feature.
Can it be fixed, please?
Repository: flutter
Issue: Allow apps to disable the implicit view
Labels: a: desktop,P3,a: multi window,team-engine,triaged-engine

See these design docs:

1. https://flutter.dev/go/desktop-multi-view-runner-apis
1. https://flutter.dev/go/multi-view-embedder-apis
Repository: PowerToys
Issue: Make the color picker compatible with mica
Labels: Needs-Triage,Product-Color Picker

### Description of the new feature / enhancement

Make the color picker mouse box and manual selector with a mica background

### Scenario when this would be used?

everytime

### Supporting information

_No response_
Repository: scrcpy
Issue: can scrcpy give me notification on the pc that notify me some one touch my phone
Labels: feature request

 that app is amazing , i love it, my question about get notification from my phone to my pc that some one touch my phone, that notification may be automatic raising for the scrcpy window or my be sound or message