sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: E0623 Lifetime elision error emitted twice
Labels: A-diagnostics,T-compiler

Given the following code: <!-- Please provide a link to play.rust-lang.org -->

```rust
fn foo(slice_a: &mut [u8], slice_b: &mut [u8]) {
    core::mem::swap(&mut slice_a, &mut slice_b);
}
```

The current output is:

```
error[E0623]: lifetime mismatch
 --> test.rs:2:35
  |
1 | fn foo(slice_a: &mut [u8], slice_b: &mut [u8]) {
  |                 ---------           --------- these two types are declared with different lifetimes...
2 |     core::mem::swap(&mut slice_a, &mut slice_b);
  |                                   ^^^^^^^^^^^^ ...but data from `slice_b` flows into `slice_a` here

error[E0623]: lifetime mismatch
 --> test.rs:2:35
  |
1 | fn foo(slice_a: &mut [u8], slice_b: &mut [u8]) {
  |                 ---------           ---------
  |                 |
  |                 these two types are declared with different lifetimes...
2 |     core::mem::swap(&mut slice_a, &mut slice_b);
  |                                   ^^^^^^^^^^^^ ...but data from `slice_a` flows into `slice_b` here
```

This error is emitted twice, event though both errors have the same cause.

Ideally it would only be emitted for one direction.

Related: https://github.com/rust-lang/rust/pull/90179
Repository: rust
Issue: [ER] Add searches with steps growing exponentially or sub-exponentially to stdlib
Labels: C-feature-request,T-libs

This blog post has reminded me that it's probably a good idea to add some exponential search functions to the Rust Stdlib:
https://quickwit.io/blog/search-a-sorted-block/

The D language std lib shows several things:
https://dlang.org/phobos/std_range.html#.SearchPolicy.gallop

Beside a linear search and a binary search (already present in Rust stdlib) the D stdlib has in forward and backwards versions two different searches (so in total they are six), in one of them the step grows linearly (followed by a binary search), useful when the element to find is near the start or the end of the sequence, and in the other the step doubles in length at each step (again, once the search overshoots, a binary search is done).
Repository: godot
Issue: Distant coloured billboards fade out on Android due to incorrect mipmap generation or rendering
Labels: bug,platform:android,topic:rendering,confirmed,topic:3d

### Godot version

v3.3.3.stable.official [b973f997f]

### System information

Android 8.1.0  (Nexus 5X) - GLES2

### Issue description

Billboards that use coloured textures fade out as they move away from the camera on Android 8.1.0. Bizarrely billboards with black and white textures do not exhibit this behaviour. The following videos were captured using the minimal sample project attached below.

Windows (expected behaviour):

https://user-images.githubusercontent.com/1178335/138663638-7ec76533-1391-4f64-bbf4-bbdf8e406dbd.mp4

Android (unexpected behaviour):

https://user-images.githubusercontent.com/1178335/138663642-1319c277-d575-44b7-86ca-08bd67f6ceb5.mp4




### Steps to reproduce

1. Add a Sprite3D, set to billboard mode, to a scene.
2. Use the default Godot icon.png as a texture for the billboard.
2. Add a Camera to the scene, facing the billboard. 
2. Have a script move the two apart.
3. Notice that, only on Android, the billboard fades out as it moves away from the camera. 

### Minimal reproduction project

[GodotAndroidBugMinimal.zip](https://github.com/godotengine/godot/files/7408562/GodotAndroidBugMinimal.zip)
Repository: godot
Issue: [Godot 4] - "New Inherited Scene" doesn't work as expected
Labels: discussion,topic:editor

### Godot version

v4.0.dev.custom_build [7d907ea90]

### System information

manjaro 21, AMD Radeon r7 200 series, Vulkan, 8GB Memory

### Issue description

When you have a 3d model and want to modify it, the engine doesnt work as expected:

What happens:
![image](https://user-images.githubusercontent.com/58845030/138685815-ba88ddeb-ce30-495a-908d-4e8277d478ea.png)


Expected:
![image](https://user-images.githubusercontent.com/58845030/138685905-867e4924-504d-4681-9ef8-5189a86387d9.png)


Video showing the weirdness:

https://user-images.githubusercontent.com/58845030/138686042-85b210e3-6ac3-4918-af9d-57b0848c9649.mp4





### Steps to reproduce

* Import a 3d Model
* Right click at it on FileSystem Dock
* Click "New inherited scene"
* The new scene will not be modifiable!

### Minimal reproduction project

[model_map_village.glb.zip](https://github.com/godotengine/godot/files/7409999/model_map_village.glb.zip)
Repository: storybook
Issue: SVG with linearGradient are not filled in Docs tab
Labels: bug,addon: docs

## Describe the bug
SVG images with linear gradients are not shown on the Docs tab when it's opened after the **Canvas** tab is rendered.

## To Reproduce
1. Clone the repo https://github.com/pahan35/storybook-repro.
2. Switch to **bug/not-filled-with-linear-gradient** branch.
3. Start storybook.
4. Go to story http://localhost:6006/?path=/docs/icons-with-gradient--default with a bug.
5. Switch to **Canvas** tab and back.

### What is the expected result?
I expect to see a rectangle with a gradient background, as it was on the initial opening.

### What happened instead?
I don't see any gradient.

## System

> Environment Info:
> 
>   System:
>     OS: macOS 11.6
>     CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
>   Binaries:
>     Node: 14.17.6 - /usr/local/opt/node@14/bin/node
>     Yarn: 3.0.2 - /usr/local/bin/yarn
>     npm: 6.14.15 - /usr/local/opt/node@14/bin/npm
>   Browsers:
>     Chrome: 94.0.4606.81
>     Safari: 15.0
>   npmPackages:
>     @storybook/addon-actions: ^6.4.0-beta.19 => 6.4.0-beta.19 
>     @storybook/addon-docs: ^6.4.0-beta.19 => 6.4.0-beta.19 
>     @storybook/addon-essentials: ^6.4.0-beta.19 => 6.4.0-beta.19 
>     @storybook/addon-links: ^6.4.0-beta.19 => 6.4.0-beta.19 
>     @storybook/react: ^6.4.0-beta.19 => 6.4.0-beta.19 
> 

## Additional context
I was looking for a reason and found that this happens because of ids overlap which happens because we keep Canvas markup in the DOM, but just hide it with `hidden=true` for canvas container.
If we either remove canvas markup from the DOM or remove `hidden=true` from the canvas container, we can see linearGradient background again.

[Recorded screencast](https://recordit.co/yKvns5cIid)
Repository: rust
Issue: Rustc passes syntactically invalid input to attribute macros
Labels: P-high,T-compiler,regression-from-stable-to-stable,WG-diagnostics,A-proc-macros

It used to be the case that attribute macros would only ever be invoked with syntactically valid input. Rustc would snip out or otherwise fix up invalid syntax prior to dispatching the macro invocation. This ensures that rustc's recovery from the invalid syntax, and any diagnostics emitted by rustc to that effect, are consistent with any subsequent diagnostics emitted by the macro, rather than requiring both to perform independent and inconsistent heuristics to recover from the invalid input.

However, it looks like recent rustc versions (1.51+) have begun invoking attribute macros on invalid syntax. Can we find out whether this behavior is intended or a regression from recent Span-related work (#43081 &mdash; @Aaron1011)? IMO the newfangled behavior is not necessarily desirable so I have filed this as a regression.

```rust
// src/lib.rs

use proc_macro::TokenStream;

#[proc_macro_attribute]
pub fn repro(_args: TokenStream, input: TokenStream) -> TokenStream {
    eprintln!("{:#?}", input);
    TokenStream::new()
}
```

```rust
// src/main.rs

#[repro::repro]
trait T {
    fn run(&);
}

fn main() {}
```

```toml
# Cargo.toml

[package]
name = "repro"
version = "0.0.0"
edition = "2018"
publish = false

[lib]
proc-macro = true
```

- 1.31 through 1.39: macro is invoked with `trait T {}` as input. Invalid syntax has been snipped out.
- 1.40 through 1.50: macro is invoked with `trait T { fn run(); }` as input, invalid syntax snipped out with finer granularity.
- 1.51+: macro is invoked with `trait T { fn run(&); }` which is invalid syntax and not necessarily desirable.
Repository: go
Issue: proxy.golang.org: stop serving /@v/branchname.info when the branch is deleted
Labels: NeedsInvestigation,modules,proxy.golang.org

I just had a very confusing experience using modules for a solid hour, which was all caused because one of the tools I use renamed their HEAD branch from `master` to `main` and I hadn't noticed.

I was happily running `go install github.com/kyleconroy/sqlc/cmd/sqlc@master`, and it was working. I ran into some weird behaviors which should have been fixed in the latest development version, which was odd. I later found out via `go version -m $(which sqlc)` that my version was half a year old, even though HEAD had a commit just days ago.

Ah! The HEAD branch is now `main`. But why is `@master` still happily giving me an old version, when upstream deleted their branch? Surely, upstream deleting their old HEAD branch is as much as they should do to make things right.

Turns out that the problem is that `proxy.golang.org` is remembering the last `master` version it saw, presumably forever:

```
$ go list -m github.com/kyleconroy/sqlc@master
github.com/kyleconroy/sqlc v1.8.1-0.20210503000056-ec35f225dfed
$ go list -m github.com/kyleconroy/sqlc@main
github.com/kyleconroy/sqlc v1.10.1-0.20211019050806-6ee39cb62526
$ GOPROXY=direct go list -m github.com/kyleconroy/sqlc@master
go: github.com/kyleconroy/sqlc@master: invalid version: unknown revision master
$ GOPROXY=direct go list -m github.com/kyleconroy/sqlc@main
github.com/kyleconroy/sqlc v1.10.1-0.20211019050806-6ee39cb62526
```

You can see it frozen in time at https://proxy.golang.org/github.com/kyleconroy/sqlc/@v/master.info.

I strongly believe the proxy server should not do this. I realise that tagged versions are effectively treated as read-only once pushed by the proxy and index servers, but I understand that branches aren't meant to work that way. If a branch vanishes from upstream, I think its `.info` file should reflect that, just like `/@v/missing.info` gives `invalid version: unknown revision missing`.

This issue is slightly similar to https://github.com/golang/go/issues/39007, but also different - in my case, the module is healthy, but just not at that branch anymore.
Repository: rust
Issue: Fix negative traits coherence checks compile error message for type aliases
Labels: A-diagnostics,T-compiler,F-rustc_attrs,D-incorrect,F-negative_impls

Follow up of [this comment on #90104](https://github.com/rust-lang/rust/pull/90104#discussion_r733963942)

This test https://github.com/rust-lang/rust/pull/90104/files#diff-2c291b05493bf924a05c167ef3923655ca244b6fd8bc2303ffdc2ed2132498cc is giving an ungreat error message.

```rust
#![feature(rustc_attrs)]
#![feature(trait_alias)]

trait A {}
trait B {}
trait AB = A + B;

impl A for u32 {}
impl B for u32 {}

trait C {}
#[rustc_strict_coherence]
impl<T: AB> C for T {}
#[rustc_strict_coherence]
impl C for u32 {}
//~^ ERROR
// FIXME it's giving an ungreat error but unsure if we care given that it's using an internal rustc
// attribute and an artificial code path for testing purposes

fn main() {}
```

fails with ...

```
error[E0283]: type annotations needed
  --> $DIR/coherence-overlap-trait-alias.rs:15:6
   |
LL | impl C for u32 {}
   |      ^ cannot infer type for type `u32`
   |
   = note: cannot satisfy `u32: C`
note: required by a bound in `C`
  --> $DIR/coherence-overlap-trait-alias.rs:11:1
   |
LL | trait C {}
   | ^^^^^^^ required by this bound in `C`

error: aborting due to previous error
```

Error should mention about conflicting implementations for `u32` or something like that. More similar to what happens without using the `rustc_strict_coherence` attribute.
Repository: TypeScript
Issue: Support different moveToNewFile file name conventions
Labels: Suggestion,In Discussion,Awaiting More Feedback,Domain: Refactorings

# Suggestion

Support additional file naming conventions when refactoring.

## 🔍 Search Terms

moveToNewFile move to file "move to a new file"

## ✅ Viability Checklist

My suggestion meets these guidelines:

* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [x] This could be implemented without emitting different JS based on the types of the expressions
* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).

## ⭐ Suggestion

Specify project file naming conventions in tsconfig.json and use the rule [here](https://github.com/microsoft/TypeScript/blob/main/src/services/refactors/moveToNewFile.ts).

## 📃 Motivating Example

Angular projects use the file name convention some-example.component.ts. The refactor action "Move to a new file" uses the convention SomeNewFile.ts. Ideally, there would be a way to specify the naming convention of the new file. In this case, some-new-file.ts would be the desirable outcome.

## 💻 Use Cases

1. Create a TS interface in the same file where it's being used called SomeExampleInterface
2. Extract the interface using "Move to a new file" in VS Code
3. Notice the created file is SomeExampleInterface.ts, which needs to be renamed to some-example-interface.ts to follow project naming conventions
Repository: TypeScript
Issue: `stripInternal` should work on single-line comments
Labels: Bug,Help Wanted,Experimentation Needed,Effort: Casual

# Bug Report

### 🔎 Search Terms

`stripInternal`

### 🕗 Version & Regression Information

- This is a crash
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about `stripInternal`

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?stripInternal=true&ts=3.3.3#code/PQKhAIAEEsDsBcCmAnWBDANuEwBQiAPABwHtl5x4BPIxcAFQAs4BzcAXnAGd5lWBuXLmDBKzLuGgTYJCjAQp0WABQBXLq3BoKAY0ZpkaHUmQBKfMTIVqtBs1gsATB3CxVAWwBGKQcNHxxSQlMLhJXWUkFVExwZRkKdU1tcD0DIxNzQlJySho6JlYAZhdPEhIMRDRYQSA)

### 💻 Code

_/module.ts_

```ts
/** @internal */
export type Thing = string;

// this is not @internal (using at character)
export type Thing2 = number;

// this is also not internal (not using at character)
export type Thing3 = boolean;
```

### 🙁 Actual behavior

_/module.d.ts_

```ts
export declare type Thing3 = boolean;
```

### 🙂 Expected behavior

_/module.d.ts_

```ts
export declare type Thing2 = number;
export declare type Thing3 = boolean;
```
Repository: deno
Issue: Add `DENO_CACHED_ONLY` env var
Labels: cli,suggestion

This environment variable would have the same effect as setting `--cached-only` in `deno run`.

It would be very useful to use in CI when vendoring DENO_DIR: I don't want certain CI flows to ever pull from the web.
Repository: deno
Issue: Support `--cached-only` to `deno cache`
Labels: cli,suggestion

`deno cache` does not just download dependencies, but it also does TS transpilation. Adding `--cached-only` from`deno run` to `deno cache` would allow supporting "transpilation only".

Same reasoning as #12536
Repository: material-ui
Issue: [Tabs] Export scroll logic and disable logic
Labels: new feature,component: tabs

<!-- Provide a general summary of the feature in the Title above -->

<!--
  Thank you very much for contributing to MUI by creating an issue! ❤️
  To avoid duplicate issues we ask you to check off the following list.
-->

<!-- Checked checkbox should look like this: [x] -->
- [x] The issue is present in the latest release.
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.

## Summary 💡

Via `TabScrollButtonProps={{ onClick: handleScrollButtonClick }}` I am able to override the custom scroll button behaviour, which is nice. At the same time I loose the scroll logic natively provided with no way to add it again, which is sub-optimal.  

Ideally, I would like to trigger additional logic upon click without overriding the native mui scroll. 

Additionally, I want to override when the scroll buttons become disabled. Currently I can do so with
`TabScrollButtonProps={{ onClick: handleScrollButtonDisable}}`. The disable method must then select both scroll buttons and check whether the current state necessitates one of them to be disabled. The best handle to differentiate between both buttons is currently via` document.querySelectorAll('[data-testid="KeyboardArrowRightIcon"]');` (Which doesn't look official, stable or like the "mui way" at all.)

Ideally, I would like to use dedicated attributes to finetune the behaviour of each button individually. 

## Motivation 🔦

I use tabs to display dates. I want to load additional dates when I have reached the end of the scrollable tabs. I want to scroll normally whenerver I haven't reached the end. If there are now more dates to load, I want to disable the scroll buttons
Currently, when reaching the end, the scroll buttons are disabled. 
Also, when overriding the click listener the native scroll logic gets lost.
Repository: youtube-dl
Issue: Include playlist description and view count when using youtube-dl with `--flat-playlist -J` on a YouTube playlist
Labels: request

<!--

######################################################################
  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.06.06. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Search the bugtracker for similar feature 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 feature request
- [x] I've verified that I'm running youtube-dl version **2021.06.06**
- [x] I've searched the bugtracker for similar feature requests including closed ones


## Description

<!--
Provide an explanation of your issue in an arbitrary form. Please make sure the description is worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient. Provide any additional information, suggested solution and as much context and examples as possible.
-->

I have been trying to find a way to quickly get information and video URLs/titles from a YouTube playlist, so far I have found that using `youtube-dl <playlist URL> -J --flatplaylist` is the closest to what I want, returning a list of all videos as well as the uploader of the playlist and the playlist name.  
However, it would be extremely useful if it could also return even more information about the playlist, like the playlist's Description & view count.
Repository: puppeteer
Issue: Allow additional aria attributes to be specified in aria/ queries
Labels: feature,confirmed

I know there's probably an upstream issue involved here since this feature is reliant on the CDP endpoint being improved, but since that CDP endpoint was originally implemented for Puppeteer I thought it was worth adding here.

Currently, only `[role="rolename"]` and label are permitted in `aria/` queries. This is a bit of a hindrance in certain circumstances. For instance, let's say I want to select the row label for the 4th row in a grid. To do this at the moment, I need to use a query for all the rows in the grid and then use array indexing to pick the 4th item.

For example:

```javascript
const grid = await page.$('aria/Users[role="grid"]');
const rowHeadings = await grid.$$('aria/[role="rowheading"]');
expect(await rowHeadings[3].getProperty("textContent")).toEqual("Andy");
```

However, this code will fail if the grid is only a partial rendering (e.g. a grid that uses virtual scrolling to improve page performance). Instead, I need to be able to query by row index:

```javascript
const grid = await page.$('aria/Users[role="grid"]');
const rowHeading4 = await grid.$('aria/[role="rowheading"][rowindex="4"]');
expect(await rowHeading4.getProperty("textContent")).toEqual("Andy");
```

I could fallback to CSS selectors and query by `aria-rowindex` but this requires extra hoops if `aria-rowindex` is set on the `role="row"` nodes and not on the `role="rowheading"` nodes.

Another, perhaps more egregious example might be a radiogroup. I want to get the currently selected option, but instead of 

```javascript
const group = await scope.$('aria/Text alignment[role="radiogroup"]');
const selected = await group.$('aria/[checked="true"]');
```

I have to do

```javascript
const group = await scope.$('aria/Text alignment[role="radiogroup"]');
const radios = await scope.$('aria/[role="radio"]');
let selected;
for (const radio of radios) {
    if (await radio.evaluate(r => r.checked || (r.ariaChecked === "true"))) {
        selected = radio;
        break;
    }
}
```
Repository: kubernetes
Issue: Make sure that underlying goroutine finishes when requests times out
Labels: kind/bug,sig/api-machinery,triage/accepted

### What happened?

Spin off from #105611 as requested in https://github.com/kubernetes/kubernetes/pull/105734#discussion_r732852756

Currently, timeout filter doesn't force underlying goroutine to finish. This can potentially cause hard to debug race conditions as showed in #105734 




### What did you expect to happen?

Timeout goroutine should wait for underlying goroutine to finish first.

### How can we reproduce it (as minimally and precisely as possible)?

N/A

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
# paste output here
```

</details>


### Cloud provider

<details>

</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: pytorch
Issue: Expose `isDifferentiableType` to python
Labels: module: autograd,triaged,better-engineering,actionable

This is a useful function in general.
That would reduce hardcode list like the one in `is_differentiable_dtype` in `gradcheck.py`.



cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7
Repository: terminal
Issue: Closing a pane that summoned the "termination behavior" infobar should probably just dismiss it
Labels: Help Wanted,Issue-Bug,Area-UserInterface,Product-Terminal,Priority-3

_From @KalleOlaviNiemitalo in https://github.com/microsoft/terminal/issues/10798#issuecomment-950857104_

> I then pressed Ctrl+Shift+W to close the tab, but the info bar remained there.
Repository: terminal
Issue: The info bar shows up on nonzero exit codes even with ` "closeOnExit": "always"`
Labels: Help Wanted,Issue-Bug,Area-UserInterface,Product-Terminal,Priority-2

_From @KalleOlaviNiemitalo in https://github.com/microsoft/terminal/issues/10798#issuecomment-950857104_


![infobar-on-closeonexit-always](https://user-images.githubusercontent.com/18356694/138726802-1c830939-d587-444b-b54d-ce5d27355d9d.gif)

This might just go away if we do #11607 first, but it might not. Tracking this separately regardless