sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: [video_player_web] "video playback lifecycle" integration test is flaky
Labels: team,platform-web,p: video_player,package,P2,team-web,triaged-web

The integration test `video playback lifecycle` [code](https://github.com/flutter/plugins/blob/2ca342c22777a5ecb63999bcb969382af00f9f43/packages/video_player/video_player_web/example/integration_test/video_player_web_test.dart#L178) is flaky. 

It is currently giving the browser ~1 second between video events, but if the `initialized` event takes longer than 1 second to be received, the test fails. It is failing enough that I've had to restart it a few times, so it should be fixed.

The most probable cause is network issues / throttling which make the test video take > 1s to download.

Possible fixes:
* (easy) bump the timeout from 1s to something longer. This will make the test take a few more seconds to run, and doesn't really resolve the flakinesss
* (more involved) deliver the video from a local web-server, so network access is not an issue (there's another plugins issue related to this)

Example of failure:

```
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞═════════════════
The following TestFailure was thrown running a test:
Expected: [
            VideoEventType:VideoEventType.bufferingStart,
            VideoEventType:VideoEventType.bufferingUpdate,
            VideoEventType:VideoEventType.initialized,
            VideoEventType:VideoEventType.bufferingEnd
          ]
  Actual: MappedListIterable<VideoEvent, VideoEventType>:[
            VideoEventType:VideoEventType.bufferingStart,
            VideoEventType:VideoEventType.bufferingUpdate
          ]
   Which: at location [2] is MappedListIterable<VideoEvent,
VideoEventType>:[
            VideoEventType:VideoEventType.bufferingStart,
            VideoEventType:VideoEventType.bufferingUpdate
          ] which shorter than expected
```

* Failed build: https://cirrus-ci.com/task/4680720818896896?logs=drive#L348
Repository: rust
Issue: Always-inline closure passed via `impl FnOnce` doesn't inline
Labels: A-codegen,A-closures,C-bug

An example (try it in debug configuration)

```rust
use std::arch::asm;

#[inline(always)]
fn call<T>(f: impl FnOnce() -> T) -> T {
    f()
}

#[inline(always)]
const fn identity<T>(f: T) -> T {
    f
}

pub fn f() {
    let closure = identity(#[inline(always)] || unsafe { asm!("pause") });
    call(closure)
}
```
https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=17e7dce927938012e15cd503caeb0cce

I expected to see this happen: `call_once` marked `alwaysinline`

Instead, this happened: `call_once` marked `inlinehint`

The closure itself is inlined, however the `call_once` is not, and when using `impl FnOnce`, effectively defeats the purpose of the `#[inline(always)]`.  `Fn` and `FnMut` don't appear to have this issue (or LLVM is more likely to inline them, at least).

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.60.0 (7737e0b5c 2022-04-04)
binary: rustc
commit-hash: 7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c
commit-date: 2022-04-04
host: x86_64-unknown-linux-gnu
release: 1.60.0
LLVM version: 14.0.0
```
Repository: pytorch
Issue: [primTorch] Reduction references don't return views consistent with their original operators
Labels: triaged,module: primTorch

This occurs because the reduction references model the keepdim arg as a broadcast following the reduction. This makes a lot of sense but causes view inconsistency. For example:

```
a = torch.randn(2, 2)
result = torch.amin(a, keepdim=True, dim=0)
print(result._is_view())
: False

result = refs.amin(a, keepdim=True, dim=0)
print(result._is_view())
: True
```

We should think about a way to resolve this -- making the operations consistent is one option, but maybe primTorch can have a different view behavior in this case. 

cc @ezyang @mruberry @ngimel
Repository: pytorch
Issue: torch.ops.aten.ceil(1.5) returns Tensor rather than scalar
Labels: triaged,module: type promotion

### 🐛 Describe the bug

```
torch.ops.aten.ceil(1.5) 
```
gives `tensor(2., dtype=torch.float64)` 

However, the result is expected to be scalar type since the input is scalar type.

Moreover, when using this operator in torchscript
```
import torch

@torch.jit.script
def forward(self, lhs, rhs):
  return torch.ops.aten.ceil(float(lhs-rhs))

print(forward.graph)
```

The torchscript IR shows
```
graph(%self : Tensor,
      %lhs.1 : Tensor,
      %rhs.1 : Tensor):
  %5 : int = prim::Constant[value=1]()
  %6 : Tensor = aten::sub(%lhs.1, %rhs.1, %5) # /usr/local/google/home/cathyzhyi/items/test/test.py:5:35
  %8 : float = aten::Float(%6) # /usr/local/google/home/cathyzhyi/items/test/test.py:5:29
  %9 : int = aten::ceil(%8) # /usr/local/google/home/cathyzhyi/items/test/test.py:5:9
  return (%9)
```

It seems the output is supposed to be an int scalar not the Tensor dtype `torch.float64`

### Versions

Collecting environment information...
PyTorch version: 1.12.0.dev20220510+cpu
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: Debian GNU/Linux rodete (x86_64)
GCC version: (Debian 11.2.0-16+build1) 11.2.0
Clang version: 13.0.1-3+build2
CMake version: version 3.22.1
Libc version: glibc-2.33

Python version: 3.9.7 (default, Sep 16 2021, 13:09:58)  [GCC 7.5.0] (64-bit runtime)
Python platform: Linux-5.15.15-1rodete2-amd64-x86_64-with-glibc2.33
Is CUDA available: False
CUDA runtime version: No CUDA
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

Versions of relevant libraries:
[pip3] numpy==1.22.3
[pip3] torch==1.12.0.dev20220510+cpu
[pip3] torchvision==0.13.0.dev20220510+cpu
[conda] numpy                     1.22.3                   pypi_0    pypi
[conda] torch                     1.12.0.dev20220510+cpu          pypi_0    pypi
[conda] torchvision               0.13.0.dev20220510+cpu          pypi_0    pypi

cc @nairbv @mruberry
Repository: flutter
Issue: Consider implementing ImmutableBuffer.fromAsset on the web
Labels: platform-web,P3,team-web,triaged-web

See https://github.com/flutter/engine/pull/32999

On mobile/desktop platforms this is advantageous because we avoid round-tripping image bytes through the dart heap. Is there a similar way we could utilize this trick on the web?

FYI @yjbanov
Repository: kubernetes
Issue: kubectl edit fail, since deploy contains imagePullSecrets: - {} 
Labels: kind/bug,sig/api-machinery,help wanted,sig/cli,triage/accepted

### What happened?

if a deploy contains:
  spec:
      imagePullSecrets:
      - {}
 it will cause `kubectl edit` fail, although `kubectl create` success.
some people meet the same problem: 
https://stackoverflow.com/questions/49694153/kubernetes-error-kubectl-edit-deployment
the scheduler suffer the problem, happen and fix in 1.20.x
https://github.com/kubernetes/kubernetes/commit/bd5c54805d4fef12cf056440cbd3b7f06afef8e5
although patchStatus can fix the scheduler problem, it can not fix demand that patch spec.

### What did you expect to happen?

consistency: if `kubectl edit` fail, means patch fail, the `kubectl create` need fail too.

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

valid deploy create, and stop using "-: {}"

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
# paste output here
```

</details>
1.22.3，1.20.4，1.20.11

### 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 version (if applicable)

<details>

</details>


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

<details>

</details>
Repository: pytorch
Issue: fast `gradcheck` fails when outputs that do not require grad precede outputs that do
Labels: module: autograd,triaged,module: linear algebra,actionable

### 🐛 Describe the bug

`gradcheck` fails for `torch.linalg.slogdet` when `fast_mode=True`

```python
import torch
from torch.autograd import gradcheck

A = torch.rand([1, 1], dtype=torch.float64, requires_grad=True)
gradcheck(torch.linalg.slogdet, (A), fast_mode=True)
```

### Versions

pytorch: 1.11.0

cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7 @jianyuh @mruberry @walterddr @IvanYashchuk @xwang233
Repository: flutter
Issue: [Windows] `FloatingActionButton` `tooltip` not seen by screen readers
Labels: a: accessibility,platform-windows,a: desktop,has reproducible steps,P2,found in release: 2.10,found in release: 2.13,team-windows,triaged-windows

Hi,
Using the latest Flutter from master (see below), when creating an instance of `FloatingActionButton`, the included `tooltip` is not seen by screenreaders.

To reproduce, create an app, the default code for which helpfully includes a floating action button with a supplied tooltip of "Increment", and using the tab key, navigate to said button with your screen reader enabled.

Using NVDA 2021.3.5, I hear (and see in braille) only "Button".

Here's my flutter details:

```shell
[ÔêÜ] Flutter (Channel master, 2.13.0-0.0.pre.1023, on Microsoft Windows [Version 10.0.22000.613], locale en-GB)
    ÔÇó Flutter version 2.13.0-0.0.pre.1023 at C:\Users\chris\flutter
    ÔÇó Upstream repository https://github.com/flutter/flutter.git
    ÔÇó Framework revision a259fcb64e (42 minutes ago), 2022-05-11 00:14:06 -0400
    ÔÇó Engine revision 6291508027
    ÔÇó Dart version 2.18.0 (build 2.18.0-103.0.dev)
    ÔÇó DevTools version 2.13.1

[ÔêÜ] Android toolchain - develop for Android devices (Android SDK version 31.0.0-rc2)
    ÔÇó Android SDK at C:\Users\chris\AppData\Local\Android\sdk
    ÔÇó Platform android-31, build-tools 31.0.0-rc2
    ÔÇó Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    ÔÇó Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    ÔÇó All Android licenses accepted.

[ÔêÜ] Chrome - develop for the web
    ÔÇó Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[ÔêÜ] Visual Studio - develop for Windows (Visual Studio Enterprise 2022 17.1.0)
    ÔÇó Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Enterprise
    ÔÇó Visual Studio Enterprise 2022 version 17.1.32210.238
    ÔÇó Windows 10 SDK version 10.0.22000.0

[ÔêÜ] Android Studio (version 2020.3)
    ÔÇó Android Studio at C:\Program Files\Android\Android Studio
    ÔÇó Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    ÔÇó Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    ÔÇó Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[ÔêÜ] VS Code, 64-bit edition (version 1.67.0)
    ÔÇó VS Code at C:\Program Files\Microsoft VS Code
    ÔÇó Flutter extension version 3.27.0

[ÔêÜ] Connected device (3 available)
    ÔÇó Windows (desktop) ÔÇó windows ÔÇó windows-x64    ÔÇó Microsoft Windows [Version 10.0.22000.613]
    ÔÇó Chrome (web)      ÔÇó chrome  ÔÇó web-javascript ÔÇó Google Chrome 101.0.4951.54
    ÔÇó Edge (web)        ÔÇó edge    ÔÇó web-javascript ÔÇó Microsoft Edge 100.0.1185.44

[ÔêÜ] HTTP Host Availability
    ÔÇó All required HTTP hosts are available

ÔÇó No issues found!
```

Thank you for reading.
Repository: flutter
Issue: See if we can build CanvasKit with -msimd128
Labels: engine,c: performance,platform-web,perf: speed,e: web_canvaskit,P2,team-web,triaged-web

Per https://v8.dev/features/simd this should be available for new versions of Chrome. When using that flag, it will allow actual SIMD operations in WASM. Operationalizing this might require some kind of browser version detection, but it'd at least be good to know the performance characteristics.

/cc @hterkelsen @yjbanov 

@jonahwilliams fyi
Repository: pytorch
Issue: `torch.scatter_add` will succeed when the `index` is a complex tensor
Labels: triaged,module: scatter & gather ops

### 🐛 Describe the bug

`torch.scatter_add` will succeed when the `index` is a complex tensor without any elements.

```python
import torch

input_tensor = torch.rand([10, 5], dtype=torch.float64)
index_tensor = torch.rand([13, 0], dtype=torch.complex128)
src_tensor = torch.rand([10, 2], dtype=torch.float64)

def fn(input, index, src):
    dim = -1
    fn_res = torch.scatter_add(input, dim, index, src, )
    return fn_res

fn(input_tensor, index_tensor, src_tensor)
# tensor([[0.9610, 0.2629, 0.8555, 0.7965, 0.3472],
#         [0.7140, 0.6187, 0.4872, 0.3589, 0.7170],
#         [0.3184, 0.3303, 0.8061, 0.6865, 0.5176],
#         [0.6451, 0.1152, 0.4974, 0.0535, 0.0350],
#         [0.1497, 0.7439, 0.7563, 0.8654, 0.6401],
#         [0.1090, 0.9057, 0.2156, 0.3272, 0.6849],
#         [0.8402, 0.4956, 0.4937, 0.9882, 0.1275],
#         [0.0889, 0.8429, 0.3421, 0.1373, 0.1697],
#         [0.1318, 0.0984, 0.1662, 0.4122, 0.1132],
#         [0.9094, 0.2276, 0.8924, 0.3781, 0.7588]], dtype=torch.float64)
```

However, when trying to compute the gradient

```python
import torch
from torch.autograd import gradcheck

input_tensor = torch.rand([10, 5], dtype=torch.float64, requires_grad=True)
index_tensor = torch.rand([13, 0], dtype=torch.complex128, requires_grad=True)
src_tensor = torch.rand([10, 2], dtype=torch.float64, requires_grad=True)

def fn(input, index, src):
    dim = -1
    fn_res = torch.scatter_add(input, dim, index, src, )
    return fn_res

gradcheck(fn, (input_tensor, index_tensor, src_tensor))
# RuntimeError: Function ScatterAddBackward0 returned an invalid gradient at index 1 - got [13, 0] but expected shape compatible with [10, 2]
```

### Versions

pytorch: 1.11.0

cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7
Repository: vscode
Issue: Git - Prune On Fetch
Labels: bug,git

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: No

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.67
- OS Version: Windows 10 64 Bits, 2009.19044
- Extensions list:
![image](https://user-images.githubusercontent.com/35725131/167804506-45bfc3b7-5110-4e38-97a2-6ccb5f66aa93.png)

Note: In my setup code repo tool is AzureDevOps.

Steps to Reproduce:

1. Verify your VS Code settings to make sure Git: Prune on Fetch is enabled
![image](https://user-images.githubusercontent.com/35725131/167803117-0542fe03-a810-4c4a-8c99-b2b3c374d978.png)
2. Synch remote and local branch within Visual Studio workspace.
![image](https://user-images.githubusercontent.com/35725131/167803174-0e9cc778-c9de-43bc-aa78-b96c7d195a45.png)
4. Create a branch pull request on the remote server. Set it with auto-complete options (including branch removal and related work items closure)
6. Kick-off a synch inside VS Code once AzureDevOps Pull-Request has been successfully completed and remote branch deled.
7. Synch VS Code (either fetch all from Remote or refresh) to keeps things in synch. Local branches won't be disappearing. VS code will show them in red, but they don't go away automatically. To fix the issue run ![image](https://user-images.githubusercontent.com/35725131/167803838-7ee162f7-b576-4f18-a706-4164105173d7.png)

This feature was working like a charm in previous release 1.66.x :-(
Repository: excalidraw
Issue: zooming in on the canvas with two fingers triggers drawing
Labels: bug

On my phone, zooming in on the canvas with two fingers triggers drawing

https://user-images.githubusercontent.com/4253172/167809726-c65d994d-3c28-4bdd-817a-bcb6706e08a1.mp4
Repository: node
Issue: Http request hangup after server sends "res.writeProcessing"
Labels: https

### Version

16.13.2

### Platform

Darwin Kernel Version 20.6.0

### Subsystem

_No response_

### What steps will reproduce the bug?

Run the client code with Node.js v16:
```js
const https = require('https');
const req = https.request('https://stage1trustifieventsbackend.herokuapp.com', {
    method: 'POST',
    rejectUnauthorized: false
}, (res) => {
    res.on('data', d => {
        console.log(d.toString());
    });
}).on('error', error => {
    console.error(error);
});

req.write('');
req.end();
```

### How often does it reproduce? Is there a required condition?

The code works well when it is run against AWS EC2 backend by both Nodejs v14/v16 clients and when it is run against Heroku backend (stack 20) by the Nodejs v14 client.
This request also works well when it is run by the Postman app.

This code fails only when it is run against Heroku (stack 20) server by the Nodejs v16 client.
The Heroku point is that its servers run unsecure on the port "80" and the Heroku itself translates http requests to https.
I think the issue here is in the Heroku SSL certificates that become incompatible to the nodejs client.
What is the difference between v14/v16 `https` library? How this issue can be debugged?

### What is the expected behavior?

Return 200 status.

### What do you see instead?

```console
Error: socket hang up
    at connResetException (node:internal/errors:691:14)
    at TLSSocket.socketOnEnd (node:_http_client:471:23)
    at TLSSocket.emit (node:events:402:35)
    at endReadableNT (node:internal/streams/readable:1343:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
```

### Additional information

The server-side code is:
```js
const express = require('express');
const app = express();

app.use((req, res, next) => {
    console.log('request received');

    setTimeout(function () {
        res.writeProcessing();
    }, 1000);
    setTimeout(function () {
        res.writeProcessing();
    }, 2000);
    setTimeout(function () {
        res.status(200).send({value:'ok'});
    }, 3000);
});

const port = process.env.PORT || 8080;
app.listen(port, function () {
    console.log('server started');
});
```
Repository: pytorch
Issue: libtorch1.8 torch::sigmoid is wrong
Labels: module: cpp,triaged,module: jetson

### 🐛 Describe the bug

when I use libtorch1.8 for NVIDIA Jetson AGX,  I find the problem that torch::sigmoid() function is wrong. When I use libtorch1.7, the result is currect!

```
#include <torch/torch.h>
#include<torch/csrc/autograd/function.h>
#include <iostream>
using namespace std;

int main(){
    // at::Tensor input = torch::tensor(5.5);
    at::Tensor input = torch::ones({1, 2, 152, 152});
    at::Tensor output = input.sigmoid_();
    cout << output.sum() << endl;
    return 0;
}
```
the result:

libtorch1.8
```
27271.1
[ CPUFloatType{} ]
```

libtorch1.7
```
33780.8
[ CPUFloatType{} ]
```

### Versions

libtorch1.8 for NVIDIA Jetson AGX

cc @jbschlosser @ptrblck @puririshi98
Repository: neovim
Issue: Use absolute file paths for opening files when opening files via --remote
Labels: enhancement,remote

### Feature already in Vim?

_No response_

### Feature description

Files opened via `--remote` are interpreted as relative to neovim `cwd`.

```
/my_app -> neovim cwd
/my_app/client -> cwd of shell executing --remote
/my_app/...
```
Files opened via `--remote`in `/my_app/client`, e.g. by a linter running in this subdirectory, are resolved with the wrong directory (`/my_app`).

Files opened via `--remote` should be interpreted with a absolute path. `neovim-remote` supports this since 2016: https://github.com/mhinz/neovim-remote/pull/2
Repository: flutter
Issue: [Multiple Flutter] Occasional MissingPluginException
Labels: c: crash,platform-android,engine,P2,team-android,triaged-android

We found occasional MissingPluginException occurs when our application used the multi-flutter feature.

And we analyzed the source code of the swap engine and found swap engine may run before plugin register：

```
// 1. The engine is run immediately when FlutterJNI.swap is executed
    FlutterJNI newFlutterJNI =
        flutterJNI.spawn(
            dartEntrypoint.dartEntrypointFunctionName,
            dartEntrypoint.dartEntrypointLibrary,
            initialRoute,
            dartEntrypointArgs);

 // 2. Plugin register in FlutterEngine Constructor
    return new FlutterEngine(
        context, // Context.
        null, // FlutterLoader. A null value passed here causes the constructor to get it from the
        // FlutterInjector.
        newFlutterJNI); // FlutterJNI.
  }
```

These two steps run in different threads，so it may cause an error.
Is there any way we can avoid this error？
Repository: rust
Issue: Spurious "error: could not find native static library `objc`, perhaps an -L flag is missing?" on macOS Big Sur
Labels: O-macos,C-bug

Hi 👋 

I'm experiencing this issue on macOS Big Sur when [libusb1-sys crate's `build.rs`](https://github.com/a1ien/rusb/blob/master/libusb1-sys/build.rs) invokes `pkg-config` and gets this:

```
$ pkg-config --static --libs /usr/local/Cellar/libusb/1.0.26/lib/pkgconfig/libusb-1.0.pc
-L/usr/local/Cellar/libusb/1.0.26/lib -lusb-1.0 -lobjc -Wl,-framework,IOKit -Wl,-framework,CoreFoundation -Wl,-framework,Security
```

rustc seems then proceed to try to link `libobjc`:

```
$ [...] cargo build
   Compiling libusb1-sys v0.6.2 (/Users/adaszko/repos/rusb/libusb1-sys)
   Compiling rusb v0.9.1
error: could not find native static library `objc`, perhaps an -L flag is missing?
```

This issue is preventing me from building a statically linked libusb1-sys.  Linking itself should still work, it's just that rustc's erroring out prevents the pipeline from getting to the linking step AFAICT.

**EDIT**: Sorry, I've removed a misleading points about dynamic linking stemming from my misunderstanding of the issue.

[1]: https://web.archive.org/web/20220317152936/https://developer.apple.com/documentation/macos-release-notes/macos-big-sur-11-beta-release-notes