sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Add GeckoDriver and EdgeDriver support to package:integration_test
Labels: a: tests,framework,c: proposal,f: integration_test,P3,team-framework,triaged-framework

It seems like ChromeDriver is the only member of the WebDriver family that [package:integration_test](https://github.com/flutter/flutter/tree/master/packages/integration_test) supports. It would be great if we could support [GeckoDriver](https://github.com/mozilla/geckodriver) and [EdgeDriver](https://developer.microsoft.com/en-us/microsoft-edge/tools/webdriver/) too.

## Steps to reproduce (GeckoDriver)
[Install GeckoDriver](https://github.com/mozilla/geckodriver/releases) and run in a separate shell or process:

```
geckodriver
```

output:

```
flutter drive \
  --driver=test_driver/integration_test.dart \
  --target=integration_test/app_test.dart \
  -d web-server
Running "flutter pub get" in integration_test_experiments...        590ms
Launching integration_test/app_test.dart on Web Server in debug mode...
Waiting for connection from debug service on Web Server...         16.8s
integration_test/app_test.dart is being served at http://localhost:59592
The web-server device requires the Dart Debug Chrome extension for debugging. Consider using the Chrome or
Edge devices for an improved development workflow.
Unable to start WebDriver Session for Flutter for Web testing.
Make sure you have the correct WebDriver Server running at 4444.
Make sure the WebDriver Server matches option --browser-name.
For more information see: https://flutter.dev/docs/testing/integration-tests#running-in-a-browser
InvalidArgumentException (400): chromeOptions is not the name of a known capability or extension capability
```

## Steps to reproduce (EdgeDriver)
[Install EdgeDriver](https://developer.microsoft.com/en-us/microsoft-edge/tools/webdriver/) and run in a separate shell or process:

```
msedgedriver --port=4444
```

output:

```
flutter drive \
  --driver=test_driver/integration_test.dart \
  --target=integration_test/app_test.dart \
  -d web-server
Running "flutter pub get" in integration_test_experiments...        592ms
Launching integration_test/app_test.dart on Web Server in debug mode...
Waiting for connection from debug service on Web Server...         16.9s
integration_test/app_test.dart is being served at http://localhost:59321
The web-server device requires the Dart Debug Chrome extension for debugging. Consider using the Chrome or
Edge devices for an improved development workflow.
Unable to start WebDriver Session for Flutter for Web testing.
Make sure you have the correct WebDriver Server running at 4444.
Make sure the WebDriver Server matches option --browser-name.
For more information see: https://flutter.dev/docs/testing/integration-tests#running-in-a-browser
InvalidArgumentException (400): invalid argument: unrecognized capability: chromeOptions
```

cc: @csells @dnfield
Repository: pytorch
Issue: [Comment] remove torch.cuda.synchronize() in state_dict()
Labels: triaged,better-engineering,module: fsdp

https://github.com/pytorch/pytorch/pull/63881#discussion_r709562923

cc @zhaojuanmao @mrshenli @rohan-varma
Repository: svelte
Issue: flip animation causes layout thrashing
Labels: perf,runtime

### Describe the bug

I have a grid with a large number of elements that I'm animating using flip.  It looks great, but it causes the page to freeze up for a few seconds.  It seems like `fix_position()` and `create_rule()` are causing forced reflows every time they run: fix_position() by interleaving reads to getElementBoundingRect() and getComputedStyle().width, and writes to style.position, and create_rule() by interleaving reads to getElementBoundingRect() and adding style rules.

### Reproduction

https://svelte.dev/repl/06ac8d7e24264c5998082b168364df7d?version=3.42.4

### Logs

```shell
https://share.firefox.dev/3l28BC1
```


### System Info

```shell
System:
    OS: macOS 10.15.7
    CPU: (8) x64 Intel(R) Core(TM) i7-4750HQ CPU @ 2.00GHz
    Memory: 64.80 MB / 8.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 16.9.0 - /usr/local/bin/node
    Yarn: 1.22.11 - /usr/local/bin/yarn
    npm: 7.21.1 - /usr/local/bin/npm
    Watchman: 2021.08.30.00 - /usr/local/bin/watchman
  npmPackages:
    rollup: ^2.3.4 => 2.56.3
    svelte: ^3.0.0 => 3.42.4
```


### Severity

annoyance
Repository: create-react-app
Issue: wasm support in integrated webserver
Labels: stale,needs triage,issue: bug report

The webserver integrated in react-scripts does not permit to load wasm files.

Because it must return the mime type application/wasm for these files. (refs https://www.w3.org/TR/wasm-web-api-1/)


Note: Full wasm support in application can only be achieved using craco and a webpack config modification at the moment.
Repository: pytorch
Issue: Adding a device variable to a `torch.Tensor` subclass fails
Labels: triaged,module: xla

Even though `XLATensor` is a subclass of `torch.Tensor`, adding `xm.xla_device()` as an input parameter to select TPU backend causes the error below. Any input to resolve this issue is appreciated.

```
>> class XLATensor(torch.Tensor):
>>    def __init__(self, data, device, **kwargs):
>>    …
>> t = XLATensor([[1], [2], [3]], device=xm.xla_device())


Traceback (most recent call last):
  File "xla_tensor.py", line 56, in <module>
    t = XLATensor([[1], [2], [3]], device=xm.xla_device())
RuntimeError: legacy constructor expects device type: cpu but device type: xla was passed
```

This [`document`](https://docs.google.com/document/d/1u5kJ18HKnoJ-i8shymt__wRrnw-eYII3c-AHUlnky-s/edit?resourcekey=0-THFZXxHHehVBA-oBsLU0Jw#heading=h.9iwsbbqufptx) summarizes the details of our `XLATensor` concept.

CC @albanD, @wconstab, @ezyang

cc @bdhirsh
Repository: pytorch
Issue: How to reference a tensor variable from a superclass of `torch.Tensor`?
Labels: triaged,module: xla

Consider I have the following code where I subclass `torch.Tensor`. I'd like to avoid using `self.t_` and instead access the tensor variable in the superclass. Though, when looking at the PyTorch code, I don't seem to identify how that can be done. Your help is appreciated.

```
class XLATensor(torch.Tensor):
    def __init__(self, data, **kwargs):
        self.t_ = torch.as_tensor(data, dtype=torch.float32, **kwargs)
```

This [`document`](https://docs.google.com/document/d/1u5kJ18HKnoJ-i8shymt__wRrnw-eYII3c-AHUlnky-s/edit?resourcekey=0-THFZXxHHehVBA-oBsLU0Jw#heading=h.9iwsbbqufptx) contains more details regarding my question.

CC @albanD, @wconstab, @ezyang 


cc @bdhirsh
Repository: terminal
Issue: [Settings]: All Text which is visually appearing as heading is not defined in heading programmatically throughout the settings page.
Labels: Issue-Bug,Area-Accessibility,Product-Terminal,Priority-3,HCL-E+D,A11yWCAG,HCL-WindowsTerminal,A11yCO,A11ySev3

### Windows Terminal version (or Windows build number)

1.10.2383.0

### Other Software

**Test Environment:**
OS: Windows 11 Version 21H2 (OS Build 22000.168)
Screen Reader: Narrator
Tool: Accessibility Insight for Windows

### Steps to reproduce

**Repro Steps:**
Open Windows Terminal.
Open Settings page using "Ctrl + ',' ".
Open Narrator and ensure Scan mode is ON using 'Caps lock + Space' key.
Navigate through all tabs and verify that visually appearing heading is announced as heading or not by navigate through heading shortcut key 'h' or 'Shift + H'.

**User Experience:** 
Screen Reader user are impacted here as visually appearing heading is conveyed to them as heading as results, they will not experience same experience same structure which visual user is able.

**Guideline Reference:**
https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships

**Attachments:**
[Text which is visually appearing as heading is not defined in heading programmatically..zip](https://github.com/microsoft/terminal/files/7175799/Text.which.is.visually.appearing.as.heading.is.not.defined.in.heading.programmatically.zip)


### Expected Behavior

All Text which is visually appearing as heading should be defined in heading programmatically. i.e. 'Startup' text which is visually appearing as heading should be defined as heading.

### Actual Behavior

All Text which is visually appearing as heading is not defined in heading programmatically. Issue repro throughout the Settings page. i.e. 'Startup' text which is visually appearing as heading is not defined as heading.

Observation: Same issue repro with NVDA Screen Reader.
Repository: terminal
Issue: Provide shell completions for `wt`
Labels: Issue-Feature,Help Wanted,Product-Terminal,Area-Commandline

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.

All good? Then proceed!
-->

# Description of the new feature/enhancement
Many apps/tools nowadays provide shell completion files (for bash/zsh/powershell). They help in easy discovery of commandline arguments and are overall a QoL enhancement. 

Since `wt` supports a plethora of commandline args, it'be pretty nice to have completion files for PowerShell and CMD (through Clink, if possible). 

# Proposed technical implementation details (optional)

All shells have their own way of defining completions. (For powershell it's `Register-ArgumentCompleter`).

Almost all CLI utilities provide the files (examples - ripgrep, gh (CLI), hyperfine). Alacritty, too provides [completion files](https://github.com/alacritty/alacritty/releases) for bash, zsh and fish as a part of their release.
Repository: tensorflow
Issue: eigen_mkldnn_contraction_kernel_test has ambigious select
Labels: stat:awaiting tensorflower,type:build/install,comp:mkl,2.6.0

**System information**
- OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
- Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
- TensorFlow installed from (source or binary): source
- TensorFlow version: 2.6.0

**Describe the problem**

The build fails when using `--config=mkl_aarch64` with 

```
Analyzing: 913 targets (107 packages loaded, 28576 targets configured)
INFO: Repository remote_java_tools_linux instantiated at:
  /DEFAULT.WORKSPACE.SUFFIX:237:6: in <toplevel>
  /tmp/tmpon64uebn-bazel-tf/a0cb78cfb3034d90b816abe220cf6cc9/external/bazel_tools/tools/build_defs/repo/utils.bzl:201:18: in maybe
Repository rule http_archive defined at:
  /tmp/tmpon64uebn-bazel-tf/a0cb78cfb3034d90b816abe220cf6cc9/external/bazel_tools/tools/build_defs/repo/http.bzl:336:31: in <toplevel>
ERROR: Analysis of target '//tensorflow/core/kernels:eigen_mkldnn_contraction_kernel_test' failed; build aborted: /tmp/boegel/TensorFlow/2.6.0/foss-2021a/TensorFlow/tensorflow-2.6.0/tensorflow/core/kernels/BUILD:2957:11: Illegal ambiguous match on configurable attribute "srcs" in //tensorflow/core/kernels:eigen_mkldnn_contraction_kernel_test:
//tensorflow:arm_any
//tensorflow/core/kernels:no_mkldnn_contraction_kernel
Multiple matches are not allowed unless one is unambiguously more specialized.
```

**Any other info / logs**

Issue is simple: https://github.com/tensorflow/tensorflow/blob/72fd2bfa42a8ad909baf8d2b7b674563d256514d/tensorflow/core/kernels/BUILD#L3028-L3034 is faulty as `no_mkldnn_contraction_kernel` and any of the arch-selects can match, in this case the `arm_any` which makes this invalid
Repository: vscode
Issue: Webview editors are not registered editors?
Labels: debt,webview

While working on https://github.com/microsoft/vscode/issues/131587 I noticed that webview editors such as `mainThreadWebview-markdown.preview` does not appear to be registered in the `IEditorResolverService`. As such, I have to do an ugly hack to still offer this editor for the user to configure:

https://github.com/microsoft/vscode/blob/69f8d940e2de132c170240acf665869df9bece3a/src/vs/workbench/browser/parts/editor/editorConfiguration.ts#L19-L29

I am not sure what I can do here, is there an alternative service I can use to figure out the contributed webview editors? Can these custom webview editors register to the editor resolver, maybe in a way that they appear in the registry but cannot be picked by the user?
Repository: storybook
Issue: Docs doesn't have `diff` support
Labels: bug,has workaround,addon: docs,block: source,sev:S3

**Describe the bug**

Addon docs doesn't support diff.

```diff
- myChange
+ myOtherChange
```

Current state:
![image](https://user-images.githubusercontent.com/10364836/133572688-4f4ad397-4ca4-44c2-b4c5-7efeadee6900.png)


**To Reproduce**

https://github.com/rajzik/sb-repro

Other deployed SB can be found: https://next-storybook.oriflame.com/?path=/story/general-changelog--page

**System**

```
Environment Info:

  System:
    OS: Windows 10 10.0.22000
    CPU: (24) x64 AMD Ryzen 9 5900X 12-Core Processor
  Binaries:
    Node: 14.17.6 - C:\Program Files\nodejs\node.EXE
    Yarn: 3.0.2 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 7.21.1 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.22000.120.0), Chromium (93.0.961.47)
  npmPackages:
    @storybook/addon-actions: ^6.4.0-alpha.37 => 6.4.0-alpha.37
    @storybook/addon-docs: ^6.4.0-alpha.37 => 6.4.0-alpha.37
    @storybook/addon-essentials: ^6.4.0-alpha.37 => 6.4.0-alpha.37
    @storybook/addon-links: ^6.4.0-alpha.37 => 6.4.0-alpha.37
    @storybook/react: ^6.4.0-alpha.37 => 6.4.0-alpha.37
```

**Additional context**

It would be great to have at least some support for diff.
Repository: vscode
Issue: Support remote extension host profiling
Labels: feature-request,extensions,perf,perf-profile

Version: 1.61.0-insider

- open a remote window (e.g. WSL)
- open the 'Running Extension' editor, press the `Start Extension Host Profile` button
- CPU profile is created, Looking at it it turns out to be from local extension host where nothing is running.

Would be cool if profiling the remote extension host is possible
Repository: pytorch
Issue: profiler_legacy `_parse_legacy_records` deduplication logic has false-positive.
Labels: triaged

## 🐛 Bug

The deduplication core logic in https://github.com/pytorch/pytorch/blob/f69cf3cf2ff392d7791b7efbc069a66494492a77/torch/autograd/profiler_legacy.py#L185-L193

might false-positively mark two consecutive profiling records as duplicated.

If previous records have the same name, kind and run on same machine (node), then they will be marked as duplicated. It was originally added because redispatch might generate a sequence of this kind of duplication.

It affect a simple refactor in #62710.
See https://github.com/pytorch/pytorch/pull/62710#discussion_r694506381 and its follow-ups.

```python
import torch

from torch.autograd.profiler import record_function
from torch.autograd.profiler_legacy import profile
with profile() as prof:
    with record_function("record_function a") as a1:
        with record_function("record_function a") as a2:
            pass
    a = torch.empty([3,3])
    b = torch.empty([3,3])

print(prof.table())
```
prints
```
---------------------  ------------  ------------  ------------  ------------  ------------  ------------  
                 Name    Self CPU %      Self CPU   CPU total %     CPU total  CPU time avg    # of Calls  
---------------------  ------------  ------------  ------------  ------------  ------------  ------------  
    record_function a        92.07%     418.512us        92.07%     418.512us     418.512us             1  
          aten::empty         7.51%      34.160us         7.51%      34.160us      34.160us             1  
          aten::empty         0.42%       1.906us         0.42%       1.906us       1.906us             1  
---------------------  ------------  ------------  ------------  ------------  ------------  ------------  
```

The full record trace (via `print(record.name(), record.kind(), record.node_id())`) is
```
__start_profile mark -1
record_function a push -1
record_function a push -1
 pop -1
 pop -1
aten::empty push -1
 pop -1
aten::empty push -1
 pop -1
__stop_profile mark -1
```

This kind of false-positivse are super rare. It only affect recursive aten ops which does not exisit at all and consectively nested `record_function`s with **same name**. Due to its rareness and legaciness, I don't think it worth a fix.


cc @ezyang @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7 @ilia-cher @robieta @chaekit @gdankel @bitfort @ngimel @orionr @nbcsm @guotuofeng @guyang3532 @gaoteng-git
Repository: rust
Issue: Suboptimal diagnostic with a missing fn const
Labels: A-diagnostics,T-compiler

(This is a spinoff of Issue 88424).
Here the signature of new_unchecked lacks a "const" and the compiler doesn't give me enough help to see/fix the problem:

```rust
#![feature(
    const_fn_trait_bound,
    const_panic,
    const_trait_impl,
    generic_const_exprs,
)]

#![allow(incomplete_features)]

pub trait ToFromUsize {
    fn to_usize(self) -> usize;
    fn from_usize(x: usize) -> Self;
    const MAX: Self;
}
impl const ToFromUsize for usize {
    fn to_usize(self) -> usize { self }
    fn from_usize(x: usize) -> Self { x }
    const MAX: Self = Self::MAX;
}

pub const fn assert_nonzero(n: usize) -> usize {
    assert!(n > 0);
    n
}

pub const fn is_contained(n: usize, m: usize) -> usize {
    assert!(n <= m);
    n
}

pub const fn is_representable<Ti: ~const ToFromUsize>(n: usize) -> usize {
    assert!(n <= Ti::MAX.to_usize());
    n
}

#[derive(Debug, Copy, Clone, PartialEq, Eq, PartialOrd, Ord, Default)]
#[repr(transparent)]
pub struct Foo<Ti: ToFromUsize + Copy, const N: usize>(Ti)
where [(); assert_nonzero(N)]:,
      [(); is_representable::<Ti>(N - 1)]:;

impl<Ti: ToFromUsize + Copy, const N: usize> Foo<Ti, N>
where [(); assert_nonzero(N)]:,
      [(); is_representable::<Ti>(N - 1)]: {

    pub unsafe fn new_unchecked(i: Ti) -> Self where Ti: ~const ToFromUsize {
        Self(i)
    }
}

fn main() {}
```

It gives:

```rust
error: `~const` is not allowed here
  --> ...\test2.rs:46:58
   |
46 |     pub unsafe fn new_unchecked(i: Ti) -> Self where Ti: ~const ToFromUsize {
   |                                                          ^^^^^^^^^^^^^^^^^^
   |
   = note: only allowed on bounds on traits' associated types and functions, const fns, const impls and its associated functions
```
Repository: TypeScript
Issue: Code fix spelling suggestions for class fields based on lexical scope
Labels: Suggestion,Needs More Info

# Suggestion

_Issue raised to separately track discussion started here: https://github.com/microsoft/TypeScript/pull/44648/files#r709632217 as suggested by @sandersn_ 

Right now code fix spelling suggestions for property names are based on the receiver type. When the receiver type is wide, perhaps unknown, further correct candidate names could be collected from the fields in any surrounding classes. This could potentially only apply to private fields, where they can only be used within the class, or extended to all fields.

## 🔍 Search Terms

spelling, suggestion, code fix, class fields, private fields

## ✅ 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

<!-- A summary of what you'd like to see added or changed -->

## 📃 Motivating Example

```ts
class MyClass {
  #brand;
  
  static isMyClass(v: object): v is MyClass {
    return #brad in v; // provide code-fix here: change 'brad' to 'brand'
  }
}
```

Private field lookup, unlike traditional property look up, is scoped to within the class. This provides a finite, and lexically discoverable, set of candidate field names.

## 💻 Use Cases

The reciever type can be too wide to use for candidate names in these cases:

- type narrowing checks https://github.com/tc39/proposal-private-fields-in-in
- JavaScript files where static type information has not been added with JSDoc comments.

## ❔ Questions

[from here](https://github.com/microsoft/TypeScript/pull/44648/files#r709632217)

- How much does it improve real-world recall?
- How much does it hurt precision?
- Should it only apply to #privates?
- Does iterated lookup hurt performance? (Probably not, but worth thinking about a little.)
- When the type is explicitly any or unknown, shouldn't the editor first suggest a specific type or narrowing for the receiver?
Repository: vscode
Issue: Adopt onDidCloseEditor context in terminal
Labels: debt,terminal-editors

We can now differentiate closing vs moving editor tabs https://github.com/microsoft/vscode/commit/0f0db5773a96fa9a2fcbb832f49efa00c322291d#commitcomment-56569912, this would probably make moving terminals more solid and involve less work.
Repository: pytorch
Issue: jit.trace's returned module returns a tuple instead of a named tuple
Labels: oncall: jit

The following code creates a module with a `forward` function that returns a `namedtuple`. I trace the module with `jit.trace`. The results is a module that returns a `tuple` instead of a `namedtuple`. Why is that?

Code:
```
from collections import namedtuple
import torch
from torch import nn

Output = namedtuple("output", "x x_squared")

class Model(nn.Module):

    def forward(self, x):
        return Output(x=x, x_squared=x**2)


model = Model()
print(model(2))
model_script = torch.jit.trace(model, torch.Tensor([2]))
print(model_script(torch.Tensor([2])))
```
Output:
```
output(x=2, x_squared=4)
(tensor([2.]), tensor([4.]))
```
I am running `torch==1.9.0`.
Thank you!
Repository: angular
Issue: Rendering of ShadowDom components is way slower than with other type of encapsulation
Labels: area: core,core: CSS encapsulation,P3

### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

No

### Description

Rendering of ShadowDom components is way slower than with other type of encapsulation. Especially this is noticeable with complex components.

### Please provide a link to a minimal reproduction of the bug

 https://codesandbox.io/s/encapsulation-types-benchmark-angular-12-wyxmq

### Please provide the exception or error you saw

_No response_

### Please provide the environment you discovered this bug in

```true
Angular 10 and 12
```


### Anything else?

_No response_
Repository: godot
Issue: The button for changing from HEX values to code values in the colorpicker disappears on runtime
Labels: bug,topic:gui

### Godot version

3.4-beta4

### System information

Windows 10

### Issue description

![image](https://user-images.githubusercontent.com/69117768/133651261-98b32ca5-57bd-45c9-b5d0-f0d92a8cbfc2.png)
![image](https://user-images.githubusercontent.com/69117768/133651279-219a6afd-3cfb-46bb-a46e-83f439114e0f.png)
Where did it go?

### Steps to reproduce

Make a colorpicker and run the scene.

### Minimal reproduction project

_No response_