sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: [bug] the output shape from torch::mean and torch::var is different  in libtorch
Labels: module: cpp,triaged

### 🐛 Describe the bug

~~~
#include <torch/torch.h>
#include <ATen/ATen.h>

torch::Tensor x = torch::randn({3,4,5});

at::IntArrayRef dim{{0,2}};

std::cout << x.mean(dim, 1).sizes() << std::endl;
/*
[1, 4, 1]
*/

std::cout << x.var(dim, 1).sizes() << std::endl;
/*
[4]
*/
~~~

the shape of output from mean and var is not compatible.


### Versions

libtorch: 1.11.0+cu113

cc @jbschlosser
Repository: pytorch
Issue: DISABLED test_profiler (test_jit.TestJit)
Labels: oncall: jit,module: flaky-tests,skipped

Platforms: linux

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_profiler&suite=test_jit.TestJit&file=test_jit.py) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/7381856543).

Over the past 3 hours, it has been determined flaky in 1 workflow(s) with 1 red and 1 green.
Repository: svelte
Issue: CSS Component Selector
Labels: feature request,css

### Describe the problem

It's a common thing using components to have personalized HTML elements.
For example `<img />` element, i can make a `<Image>` component that uses `<picture>` by default or `loading="lazy"` attribute. So it's easier to re-use or change.

The problem is its still common to add custom styles to image element, like `background-color` `object-fit` and many other stuff, like `aspect-ratio`, `width` etc.

Svelte components doesn't allow that unless you make somehow `:global()` hacks. Which doesn't give warnings when invalid and looks hacky. And when you not try to use `:global()` it becomes even more hacky and makes you use a lot of boilerplate code.

### Describe the proposed solution

A CSS component selector to select all of the root elements in the component.

**Example:**
*foo.svelte*
```svelte
<div>
  <img />
<div/>
<a />
```
<br />

*bar.svelte*
```svelte
<div>
  <Foo />
</div>
<Foo />

<style>
  div > $Foo { /* Selects `div` and `a` element in the `Foo` component, because they are in the root  */
    ...
  }
<style />
```
syntax can change.

### Alternatives considered

An option to bind everything(attributes(class), events...) in a root element in the component.

**Example:**
*foo.svelte*
```svelte
<div bind:$$root>
   <img />
<div />
<div />
```

<br />

*bar.svelte*
```svelte
<Foo class="thing" on:click={() => alert()}>

<style>
.thing { /* this would only select the first `div` element in the `Foo` component
  ...
}
<style />
```

<br />
<br />

if none of these are applicable at least having a way to bind/pass/inherit all of the events would be cool.

### Importance

would make my life easier
Repository: rust
Issue: Misplacing question mark operator throws `field expressions cannot have generic arguments`
Labels: A-diagnostics,T-compiler

Given the following code:

```rust
fn foo() -> Result<Vec<()>, ()> {
    let foos = []
        .into_iter()
        .collect::<Result<_, ()>>?();
    
    Ok(foos)
}
```

([playground link](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=b5a29a229b0ec891805824f83ec0460f))

The current output is:

```
error: field expressions cannot have generic arguments
 --> src/lib.rs:4:19
  |
4 |         .collect::<Result<_, ()>>?();
  |                   ^^^^^^^^^^^^^^^

error[E0615]: attempted to take value of method `collect` on type `std::array::IntoIter<_, 0_usize>`
 --> src/lib.rs:4:10
  |
4 |         .collect::<Result<_, ()>>?();
  |          ^^^^^^^ method, not a field
  |
help: use parentheses to call the method
  |
4 |         .collect::<Result<_, ()>>()?();
  |                                  ++
```

Ideally the output could look like:

```
error: field expressions cannot have generic arguments
 --> src/lib.rs:4:19
  |
4 |         .collect::<Result<_, ()>>?();
  |                   ^^^^^^^^^^^^^^^

hint: move the question mark operator after the parentheses:
 --> src/lib.rs:4:19
  |
4 |         .collect::<Result<_, ()>>?();
  -                                  ^
4 |         .collect::<Result<_, ()>>()?;
  +                                    ^
```

I'd consider myself a seasoned programmer, but with the current error message it nonetheless took me a while to notice the error, especially since I swear it's the first time I see the `field expressions cannot have generic arguments` message 😅
Repository: rust
Issue: Trait method takes precedence over inherent method on ambiguous numeric type
Labels: A-type-system,A-trait-system,T-lang,T-compiler,A-inference,C-discussion,T-types

This is arguably quite confusing:
```rs
trait Trait {
    fn abs(self) -> Self;
}

impl Trait for i64 {
    fn abs(self) -> Self {
        2 * self
    }
}

fn main() {
    let x = 42;
    println!("{}", x.abs());
    println!("{}", x.abs());
}
```
Ouput:
```
84
42
```

---

So the first `x.abs()` call resolves to the trait method, which is then used to influence type inference to make `x` an `i64`. With `x` being `i64`, the second `x.abs()` call calls the inherent method.

@rustbot label T-compiler, T-lang, A-traits, A-typesystem
Repository: electron
Issue: [Feature Request]: `BrowserView` → Support Window Controls Overlay
Labels: enhancement :sparkles:,component/BrowserView,component/wco

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a feature request that matches the one I want to file, without success.

### Problem Description

Currently, there is no obvious way to use the [Window Controls Overlay](https://github.com/WICG/window-controls-overlay/blob/main/explainer.md) (WCO) API from `BrowserView`s or `webContents` therein.

This is particularly inconvenient when using `BrowserView`s within `BrowserWindow`s that have had the WCO API enabled using steps outlined [here](https://www.electronjs.org/docs/latest/tutorial/window-customization#window-controls-overlay-macos-windows).

When this is the case, window controls are prone to be rendered over `BrowserView` content.

Currently, the WCO API isn't exposed to `BrowserView`s that have been added by way of [`BrowserWindow.addBrowserView`](https://www.electronjs.org/docs/latest/api/browser-window#winaddbrowserviewbrowserview-experimental)/equivalent to `BrowserWindow`s that have it enabled.

As a result, there is no obvious/OOTB way of signalling to `BrowserView`s/their contents when window controls are visible or how large they are.



### Proposed Solution

Introduce means for enabling Window Controls API for `BrowserView`s/their `webContents` — ideally, with options for controlling whether window controls themselves are actually visible.

Optional: Automatically do this when `BrowserView`s are associated with `BrowserWindow`s using `addBrowserView` or similar.

### Alternatives Considered

Thinking out loud:

- Expose key Window Controls API values from `BrowserWindow`s via some additional methods; e.g. `BrowserWindow:: getTitlebarAreaRect()` and/or `BrowserWindow::getWindowControlsAreaRect()`

### Additional Information

A GitHub Gist that demonstrates the availability of the WCO API in `BrowserWindow`, but not associated `BrowserView`s: https://gist.github.com/2d5e4dfa9f9a02644c9cf1f8fd04848b
Repository: vscode
Issue: Use modal dialog for open repo message
Labels: git,ux,under-discussion

* start with an empty window
* from the explorer select the clone from repo flow
* select a repo and (local) folder
* 😕 when clone is done a notification, not a modal is shown


<img width="1136" alt="Screenshot 2022-07-18 at 10 34 20" src="https://user-images.githubusercontent.com/1794099/179473899-a6aed957-7ce9-4da2-8530-386a7723c5e1.png">
Repository: material-ui
Issue: MUI 5.9.0 build fails with typescript 3.9
Labels: bug 🐛,component: Grid,regression

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯


![MUI_5 9 0_BUILD_ERROR_TYPESCRIPT_3 9](https://user-images.githubusercontent.com/1915529/179472724-17a3c6fe-d94a-473c-b5d5-65869018ef79.png)


I got this error after upgrading to MUI 5.9.0.
This error happens if a typescript version smaller then 4 is used.

### Expected behavior 🤔

MUI 5 should support all older versions up to 3.5.

### Steps to reproduce 🕹

Steps:

npm start or npm run build

### Context 🔦

## Codeparts of the error messages from the build log

### **@mui/system/Unstable_Grid/GridProps.d.ts(95,90)**
![image](https://user-images.githubusercontent.com/1915529/179473693-e00995a7-2eec-41f9-865e-85b4176e9728.png)

### **@mui/material/styles/experimental_extendTheme.d.ts (304,22), (304,43)**
![image](https://user-images.githubusercontent.com/1915529/179474049-754875fd-50de-4020-a4f4-61249272b737.png)

### **@mui/material/styles/experimental_extendTheme.d.ts (398,1)**
![image](https://user-images.githubusercontent.com/1915529/179474407-3016fc5c-238a-4c03-bc5c-8979fb66b9f3.png)




### Your environment 🌎

<details>
  <summary><code>MUI Packages</code></summary>

```
    "@emotion/styled": "^11.9.3",
    "@mui/material": "^5.9.0",
```
</details>
<details>
  <summary><code>Node Environment</code></summary>

```
    Node 16.14.2
    Typescript 3.9
    React 18
```
</details>
Repository: rust
Issue: public extern "C" symbols are not public in cdylib target
Labels: A-linkage

(Background: using SWIG requires adding _and exporting_ the contents of a single .o file into the resulting .so/.dll)

Using `cc` in `build.rs` I add a small C library to my crate:
```rust
    let out_dir = std::env::var("OUT_DIR").expect("cannot build in non-UTF8 target directory");
    cc::Build::new()
        .cargo_metadata(false)
        .file("automerge_wrap.c")
        .compile("automerge_wrap");
    println!("cargo:rustc-link-lib=static:+whole-archive=automerge_wrap");
    println!("cargo:rustc-link-search={}", out_dir);
```

This results in the required symbols being exported from `target/debug/libmycrate.a`, like so:

```
> nm target/debug/libmycrate.a
...
0000000000000000 T CSharp_new_AMvalue
```

However, the dynamic library `target/debug/libmycrate.so` does not contain this symbol. I can add it by using it:
```rust
pub mod other_sym {
    extern "C" {
        pub fn CSharp_new_AMvalue();
    }
    #[no_mangle] pub unsafe fn __dummy() {
        CSharp_new_AMvalue();
    }
}
```

The result is that the symbol is present, but it is not exported (note the small `t` instead of a capital `T`):

```
> nm target/debug/libmycrate.so
...
0000000000130eef t CSharp_new_AMvalue
```

I tried with Rust 1.61 and 1.62, played with linker options, e.g. by linking `automerge_wrap.o` instead of the library, but I found no way to change this. Adding wrapper functions is impossible (well, hard at least) because the symbols already have the exact name in the auto-generated .c file that I have to use in the .so file.

To me, this qualifies as a bug. If this is not a bug, then please let me know how I can get an `extern "C"` symbol into the cdylib with public visibility.
Repository: godot
Issue: "Too many warnings! Ignoring warnings for up to 1 second." message gets printed without end when the number of warnings exceeds "Max Warnings Per Second" in the project settings
Labels: bug,topic:editor

### Godot version

3.3.4.stable, 3.4.0.stable, 3.4.4.stable

### System information

Windows 11

### Issue description

Related to #43710. Happens on 3.3.4.stable, 3.4.0.stable, 3.4.4.stable. See title and the following gif:

3.4.4.stable:
<img src="https://user-images.githubusercontent.com/26558776/179487027-6a21a38f-76a8-48c4-b682-70edbff1139b.gif" width=75% height=75%/>

Analogous on the other versions.




### Steps to reproduce

1. Set "Max Warnings Per Second" in the project settings to 1.
2. Have a script with two functions that each have one parameter that is not used.

### Minimal reproduction project

[godot.3.3.4.stable.test.zip](https://github.com/godotengine/godot/files/9131076/godot.3.3.4.stable.test.zip)
[godot.3.4.0.stable.test.zip](https://github.com/godotengine/godot/files/9131077/godot.3.4.0.stable.test.zip)
[godot.3.4.4.stable.test.zip](https://github.com/godotengine/godot/files/9131078/godot.3.4.4.stable.test.zip)
Repository: godot
Issue: PathFollow2D does not update child AnimatableBody2D's collision
Labels: bug,topic:physics,needs testing,topic:2d

### Godot version

4.0.alpha11

### System information

M1 MBP, MacOS Monterey

### Issue description

When nesting an AnimatableBody2D under a PathFollow2D, and changing the offset of the PathFollow node, the AnimatableBody node moves along the path, but the collision for that node stays at the origin.

For instance, take this scene:
![image](https://user-images.githubusercontent.com/6681893/179487409-0793d802-d6b0-4680-858a-95c80eebf7e9.png)

And let's run it with paths and collision shapes visible:
![image](https://user-images.githubusercontent.com/6681893/179487628-d8b53347-665c-4606-95be-02292262022c.png)

As you can see, the animatable body **and** its child collision shape move along, but the collision detection still uses the origin point as where the platform really is.

#### Workaround
After updating the PathFollow2D offset, set the position of the AnimatableBody2D to itself:
![image](https://user-images.githubusercontent.com/6681893/179488100-673b8edb-71e1-4779-89bc-dd0b4ff97754.png)

Now the engine recognizes the new location of the collision shape, and updates accordingly:
![image](https://user-images.githubusercontent.com/6681893/179488277-aa6e7840-3b49-44f7-b832-69cf046385a4.png)


### Steps to reproduce

First, create a tree similar that contains a Path2D, PathFollow2D and a fully configured AnimatableBody2D:
![image](https://user-images.githubusercontent.com/6681893/179488908-eb812647-8c61-4553-bbd3-0be6f90fb1cb.png)

Move the PathFollow2D node along the path using offset:
![image](https://user-images.githubusercontent.com/6681893/179489001-7e19a112-6105-4890-a0a1-943ff7f1f4f7.png)

The collision of the AnimatableBody2D node did not update according to its new location.

#### Step to workaround

Right after you update the offset, assign the body's own global_position to iself. Now the collision is updated:
![image](https://user-images.githubusercontent.com/6681893/179488100-673b8edb-71e1-4779-89bc-dd0b4ff97754.png)

### Minimal reproduction project

_No response_
Repository: rust
Issue: Tracking issue for tracking licensing metadata with REUSE
Labels: C-tracking-issue,A-licensing

This is a tracking issue for [MCP 519: track licensing metadata with REUSE](https://github.com/rust-lang/compiler-team/issues/519)

### Steps

- [x] Implement scaffolding to track metadata with REUSE
- [x] Add step in CI to verify REUSE can parse all the metadata in the repository.
- [x] Import copyright metadata from the Debian rustc package.
- [x] Enhance the metadata with the existing text in the `COPYRIGHT` file and [issues labeled `A-licensing`](https://github.com/rust-lang/rust/labels/A-licensing).
- [x] https://github.com/rust-lang/rust/issues/127361
- [x] https://github.com/rust-lang/rustc-perf/issues/1939
- [ ] Automatically include dependencies licensing in tarballs' `.reuse/dep5` in rustbuild.
- [ ] Remove `LICENSE-MIT` and `LICENSE-APACHE`.
- [ ] Auto-generate `src/librustdoc/html/static/COPYRIGHT.txt`
- [ ] Auto-generate `COPYRIGHT` in source distributions and tarballs
- [ ] Replace `COPYRIGHT` to explain we're using REUSE and instructions on how to lookup actual metadata. 

### Implementation history

* https://github.com/rust-lang/rust/pull/99415
* https://github.com/rust-lang/rust/pull/104139
* https://github.com/rust-lang/rust/pull/104439
* https://github.com/rust-lang/rust/pull/104527
* https://github.com/rust-lang/rust/pull/118445
* https://github.com/rust-lang/rust/pull/127923
* https://github.com/rust-lang/rustc-perf/pull/1951
Repository: kubernetes
Issue: SSA is very inefficient with huge number of labels/annotations/...
Labels: kind/bug,sig/api-machinery,priority/important-longterm,triage/accepted

As shown here:
https://github.com/kubernetes/kubernetes/pull/110569/files#diff-c9661ce6b32ebf6604536c747826c618fa7d057248f4dffe11d576063a3b480bR358-R363

SSA (computing ManagedFields) is highly inefficient for huge number of labels/annotations and with high enough numbers (the original test had 130,000 labels) could easily exceed 10s.
As pointed in the comment thread there, I don't perceive it as a top priority as it doesn't seem to be a usecase that is really used in production usecases, but it's probably worth discussing that explicitly and making a conscious decision.

/sig api-machinery
/priority important-longterm
/kind bug

@apelisse 

@aojea - FYI
Repository: angular
Issue: Pipe `keyvalue` does not allow objects with optional keys.
Labels: area: common,P3

### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

An error occurs in HTML when using an interface (object) with option keys. 

**app.component.ts**
```ts
import { Component } from '@angular/core';

export interface MyInterface {
  one?: string;
  two?: string;
  three?: string;
}

@Component({
  selector: 'app-root',
  templateUrl: './app.component.html',
  styleUrls: ['./app.component.scss'],
})
export class AppComponent {
  myData: MyInterface = {
    one: 'One',
    two: 'Two',
  };
}
```

**app.component.html**
```html
<ng-container *ngFor="let entry of myData | keyvalue">
  <div>{{ entry.key }}: {{ entry.value }}</div>
</ng-container>
```

**VSCode with Angular Language Service**
![image](https://user-images.githubusercontent.com/60390085/179497371-a66c31d9-b16e-4c47-923e-87f1ea8c2fa4.png)

No error when using `serve` but on `build` (prod). The VSCode extension Angular Language Service also shows this error in HTML. Never seen before. So I'm not 100% if this is a regression. But maybe I never worked with interface with an optional key here. Anyway, the code works during runtime. It seems to be a type interference. We need to allow optional keys (undefined).


### Please provide a link to a minimal reproduction of the bug

https://github.com/infacto/issue-angular-keyvalue-optional/tree/main

### Please provide the exception or error you saw

```true
No overload matches this call.
  The last overload gave the following error.
    Argument of type 'MyInterface' is not assignable to parameter of type 'Record<keyof MyInterface, string> | ReadonlyMap<keyof MyInterface, string>'.ngtsc(2769)
```


### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 13.3.8
Node: 14.19.0
Package Manager: npm 6.14.16
OS: win32 x64

Angular: 13.3.11
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1202.15
@angular-devkit/build-angular   13.3.8
@angular-devkit/core            12.2.15
@angular-devkit/schematics      12.2.15
@angular/cli                    13.3.8
@schematics/angular             12.2.15
rxjs                            6.6.7
typescript                      4.6.4
```


### Anything else?

I tested this in the latest Angular 12, 13 and 14. I see no error on StackBlitz (no Language Service ext.) and the code works well during runtime.

The error disappears when allow additional keys like this:

```ts

export interface MyInterface {
  one?: string;
  two?: string;
  three?: string;
  [key: string]: string;
}
```
Or casting to any. But these is just ugly and against clean or professional code.
Repository: bitcoin
Issue: linter to check omitted fields when constructing aggregate types?
Labels: Feature

It would be nice to have a linter/tidy/whatever to enforce all non-defaulted fields in an aggregate type are initialized.

Assuming the code:

```cpp
struct A {
    struct Options {
        unsigned cache_size;
        signed delta;
        bool in_memory = false;
    };
    A(const Options&) {} // unsafe (may have fields uninitialized)
    A(unsigned cache_size, signed delta, bool in_memory = false) {}  // safe, all non-default args are initialized
};

int main() {
    (void)A{
        A::Options{
            .delta = -1,
        },
    };
}
```

This leaves `cache_size` uninitialized when using designated initializers. (The problem exists even without designated initializers, but with designated initializers recently enabled it seems likely that we'll increase the use of aggregate types)
Repository: flutter
Issue: Implement iOS keyboard track pad selection for TextField widget
Labels: a: text input,platform-ios,engine,a: fidelity,c: proposal,P3,team-ios,triaged-ios

## Use case
On iOS system fields and in natively developed iOS applications, one can press and hold the space bar to go into trackpad mode, then put another finger on the trackpad to be able to select specific texts (this is the replacement of 3D touch selection) 

With Flutter, the keyboard only transforms in the trackpad to move the cursor, but it is *not* possible to also select text. 

## Proposal
Flutter should be able to select text in a textfield in trackpad mode, as demonstrated in the sample video below: 


https://user-images.githubusercontent.com/8842565/179538899-b6af75dd-fe72-4fed-ae26-b938ea8ae222.MP4


## Additional information 
More detailed descriptions on the usage in iOS can be found online, for example [here](https://www.igeeksblog.com/how-to-use-iphone-keyboard-as-trackpad/).
Repository: transformers
Issue: Test summary with previous PyTorch/TensorFlow versions
Labels: Tests,WIP

Initialized by @LysandreJik, we ran the tests with previous PyTorch/TensorFlow versions. The goal is to determine if we should drop (some) earlier PyTorch/TensorFlow versions.

- This is not exactly the same as the scheduled daily CI (`torch-scatter`, `accelerate` not installed, etc.)
- Currently we only have the global summary (i.e. there is no number of test failures per model)

Here is the results (running on ~June 20, 2022):
- PyTorch testing has ~27100 tests
- TensorFlow testing has ~15700 tests

|     Framework | No. Failures |
| :--------------- | ----------: |
|  PyTorch 1.10 |           50 |
|  PyTorch  1.9 |          710 |
|  PyTorch  1.8 |         1301 |
|  PyTorch  1.7 |         1567 |
|  PyTorch  1.6 |         2342 |
|  PyTorch  1.5 |         3315 |
|  PyTorch  1.4 |         3949 |
| TensorFlow 2.8 |          118 |
| TensorFlow 2.7 |          122 |
| TensorFlow 2.6 |          122 |
| TensorFlow 2.5 |          128 |
| TensorFlow 2.4 |          167 |

It looks like the number of failures in TensorFlow testing doesn't increase much.

### So far my thoughts:
- All TF >= 2.4 should be (still) kept in the list of supported versions

### Questions
- What's you opinion regarding which versions to drop support?
- Would you like to see the number of test failures per model?
- TensorFlow 2.3 needs CUDA 10.1 and requires the build of a special docker image. Do you think we should make the effort on it to have the results for `TF 2.3`?