sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: terminal
Issue: [Extension Idea] Password Manager integration
Labels: Issue-Feature,Area-Extensibility,Product-Terminal

# Description of the new feature/enhancement

An extension idea would be to allow for password manager integration, for example through the command pallette or a hotkey. After searching the entry to fill out (in a command pallette-alike dropdown with search) it would then fill out the username, password, or any other field. Some password managers like 1Password already have some form of desktop integration, but it's not excellent. Native incorporation in Windows Terminal would be amazing.

# Proposed technical implementation details (optional)

We will probably first need extension support for this, but then it should be relatively easy.
Repository: rust
Issue: Derive on a struct with missing field types reports trait bound error
Labels: A-diagnostics,T-compiler

<https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=70642a5cf44cba9b2976e7853dedbb24>

If you try to derive a trait such as Debug on a struct where some of the types for the fields are missing it ends up reporting a trait bound error.

Instead, the compiler should only report the error about some of the field types not being defined.
Repository: pytorch
Issue: `/var/lib/jenkins/workspace/xla/test/test_mp_rendezvous.py` potentially flaky
Labels: high priority,triage review,triaged,module: flaky-tests,module: xla

### 🐛 Describe the bug

In CI, for the ci/circleci: pytorch_xla_linux_bionic_py3_6_clang9_test job, we recently had a failure here that did not persist past that one commit. The rendezvous test could be flaky OR XLA may have submitted a fix very fast. Filing this issue to raise the concern.

https://hud.pytorch.org/commit/pytorch/pytorch/62feadd76fb5760faccd526d9064b9ba5de13083 
```
*** End stack trace ***
Oct 28 13:20:46 Core 1 waiting for rendezvous ...
Oct 28 13:20:46 Exception in device=CPU:1: tensorflow/compiler/xla/xla_client/mesh_service.cc:364 : Failed to meet rendezvous 'rendezvous_test.0':  (12)
Oct 28 13:20:46 Traceback (most recent call last):
Oct 28 13:20:46   File \"/opt/conda/lib/python3.6/site-packages/torch_xla-1.11-py3.6-linux-x86_64.egg/torch_xla/distributed/xla_multiprocessing.py\", line 329, in _mp_start_fn
Oct 28 13:20:46     _start_fn(index, pf_cfg, fn, args)
Oct 28 13:20:46   File \"/opt/conda/lib/python3.6/site-packages/torch_xla-1.11-py3.6-linux-x86_64.egg/torch_xla/distributed/xla_multiprocessing.py\", line 323, in _start_fn
Oct 28 13:20:46     fn(gindex, *args)
Oct 28 13:20:46   File \"/var/lib/jenkins/workspace/xla/test/test_mp_rendezvous.py\", line 22, in _mp_fn
Oct 28 13:20:46     replicas=replicas)
Oct 28 13:20:46   File \"/opt/conda/lib/python3.6/site-packages/torch_xla-1.11-py3.6-linux-x86_64.egg/torch_xla/core/xla_model.py\", line 910, in rendezvous
Oct 28 13:20:46     return torch_xla._XLAC._xla_rendezvous(get_ordinal(), tag, payload, replicas)
Oct 28 13:20:46 RuntimeError: tensorflow/compiler/xla/xla_client/mesh_service.cc:364 : Failed to meet rendezvous 'rendezvous_test.0':  (12)
Oct 28 13:20:47 Traceback (most recent call last):
Oct 28 13:20:47   File \"/var/lib/jenkins/workspace/xla/test/test_mp_rendezvous.py\", line 35, in <module>
Oct 28 13:20:47     xmp.spawn(_mp_fn, args=())
Oct 28 13:20:47   File \"/opt/conda/lib/python3.6/site-packages/torch_xla-1.11-py3.6-linux-x86_64.egg/torch_xla/distributed/xla_multiprocessing.py\", line 394, in spawn
Oct 28 13:20:47     start_method=start_method)
Oct 28 13:20:47   File \"/opt/conda/lib/python3.6/site-packages/torch/multiprocessing/spawn.py\", line 188, in start_processes
Oct 28 13:20:47     while not context.join():
Oct 28 13:20:47   File \"/opt/conda/lib/python3.6/site-packages/torch/multiprocessing/spawn.py\", line 144, in join
Oct 28 13:20:47     exit_code=exitcode
Oct 28 13:20:47 torch.multiprocessing.spawn.ProcessExitedException: process 1 terminated with exit code 17
Oct 28 13:20:47 + cleanup
Oct 28 13:20:47 + retcode=1
Oct 28 13:20:47 + set +x
```

### Versions

pytorch_xla_linux_bionic_py3_6_clang9_test

cc @ezyang @gchanan @zou3519 @bdhirsh @jbschlosser
Repository: pytorch
Issue: Deadlock in test_multiprocessing_spawn.py
Labels: high priority,module: multiprocessing,triaged,module: deadlock

### 🐛 Describe the bug

For an example: https://app.circleci.com/pipelines/github/pytorch/pytorch/401476/workflows/2c0c5a93-be38-4a33-88ea-034d9e56fb86/jobs/16604711

It looks like the tests here deadlocked, but I'm not sure what the culprit is.


### Versions

pytorch_linux_xenial_py3_6_gcc5_4_test

cc @ezyang @gchanan @zou3519 @bdhirsh @jbschlosser @VitalyFedyunin
Repository: pytorch
Issue: CUDA gradcheck tests can occasionally leak memory in HUD CI
Labels: high priority,module: cuda,module: memory usage,module: tests,triaged


TestGradientsCUDA.test_fn_grad_fft_hfft_cuda_complex128 leaked memory on a commit but then passed on the next: 
https://hud.pytorch.org/commit/pytorch/pytorch/3a1aa31a2f21f584fb82c850d2c23d6f6c47b33d
```
Traceback (most recent call last):
  File "/opt/conda/lib/python3.6/site-packages/torch/testing/_internal/common_utils.py", line 1422, in wrapper
    method(*args, **kwargs)
  File "/opt/conda/lib/python3.6/site-packages/torch/testing/_internal/common_utils.py", line 1422, in wrapper
    method(*args, **kwargs)
  File "/opt/conda/lib/python3.6/site-packages/torch/testing/_internal/common_utils.py", line 1187, in __exit__
    self.name, after - before, i))
  File "/opt/conda/lib/python3.6/site-packages/torch/testing/_internal/common_utils.py", line 1983, in assertEqual
    super().assertTrue(result, msg=self._get_assert_msg(msg, debug_msg=debug_msg))
AssertionError: False is not true : Scalars failed to compare as equal! 0 != 7168
__main__.TestGradientsCUDA.test_fn_grad_fft_hfft_cuda_complex128 leaked 7168 bytes CUDA memory on device 0
```

### Versions

Happened on the linux-xenial-cuda11.3-py3.6-gcc7 config.

cc @ezyang @gchanan @zou3519 @bdhirsh @jbschlosser @ngimel @mruberry
Repository: ant-design
Issue: Responsive Column Title does not Appear in RTL test 
Labels: Inactive

- [x] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### Reproduction link
[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/responsive-antd-4-17-0-alpha-7-forked-wvgur?file=/index.test.js)

### Steps to reproduce
Press the "Tests" tab to see the test failure

### What is expected?
Both "Age" and "Address" Columns should be found by RLT. 

### What is actually happening?
The "Age" column is successfully found by the test because it DOES NOT specify a "responsive: " property in its Column definition.

The "Address" column is not found because it DOES specify a "responsive: " property in its column definition. (All breakpoints are specified so it's not an issue of window sizing by RTL)

| Environment | Info |
|---|---|
| antd | 4.16.13 |
| React | 17.0.2 |
| System | React testing library 12.1.2 |
| Browser | Rtl jsdom |

---
Additionally, I noticed that all breakpoints returned by "useBreakpoint()" are false during test execution https://ant.design/components/grid/#components-grid-demo-useBreakpoint


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: flutter
Issue: [flutter_plugin_tools] ci should make sure all plugins are published.
Labels: team,p: tooling,package,team-ecosystem,P2,triaged-ecosystem

The release ci fails silently since it sometimes fails to block the tree. This causes plugins fail to be published and it requires real people to check the "release ci" in all the past commits to make sure they are published.

There are 2 things (or more) we can do:

1. When release ci fails, send an email to the plugin/ecosystem team to notify the failure.
2. Add a new ci check to make sure all the plugins are published at HEAD~.
Repository: kubernetes
Issue: PodTopologySpread DoNotSchedule-to-ScheduleAnyway fallback mode
Labels: sig/scheduling,sig/autoscaling,kind/feature,needs-triage

### What would you like to be added?

A mode of operation for PodTopologySpread that allows users to express the flexibility to fallback from DoNotSchedule to ScheduleAnyway after a specific condition is met (e.g., after a defined period of time).

### Why is this needed?

This is needed to force the cluster autoscaler to bring up new nodes in under scaled zones, but fallback to schedule anyway if CA can't because of zonal failure or more commonly stockouts.

/sig scheduling
Repository: pytorch
Issue: Reductions on zero-size dims: 1) by accepting a custom default value, 2) if tensor has another non-reduced zero-size dim
Labels: triaged,enhancement,module: reductions

### 🐛 Describe the bug

```python
torch.empty((0, 0)).amax(dim = 1)
# IndexError: amax(): Expected reduction dim 1 to have non-zero size.
```

but in theory it could just have deleted this dimension and return a `torch.empty((0, ))`. Anyway, there are no data in the tensor, so reducing doesn't create any bogus data.

### Versions

N/A
Repository: pytorch
Issue: OpInfo JIT tests fail for torch.nonzero
Labels: oncall: jit

### 🐛 Describe the bug

`test_variant_consistency_jit` cannot call `torch.nonzero` when providing an `as_tuple` kwarg:

```
RuntimeError:
Arguments for call are not valid.
The following variants are available:

  aten::nonzero(Tensor self) -> (Tensor):
  Keyword argument as_tuple unknown.

  aten::nonzero.out(Tensor self, *, Tensor(a!) out) -> (Tensor(a!)):
  Argument out not provided.

The original call is:
  File "<string>", line 3

def the_method(i0):
    return torch.nonzero(i0, as_tuple=False)
           ~~~~~~~~~~~~~ <--- HERE
```

This may be because the `as_tuple` argument isn't defined in [native_functions.yaml](https://github.com/pytorch/pytorch/blob/master/aten/src/ATen/native/native_functions.yaml#L6689) but rather in [torch/fx/operator_schemas.py](https://github.com/pytorch/pytorch/blob/master/torch/fx/operator_schemas.py#L24).

To reproduce check out the OpInfo added in https://github.com/pytorch/pytorch/pull/67459 and remove the skip for test_variant_consistency_jit.

### Versions

PyTorch version: 1.11.0a0+git90b722c
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: macOS 11.6 (x86_64)
GCC version: Could not collect
Clang version: 12.0.0 (clang-1200.0.32.29)
CMake version: version 3.19.6
Libc version: N/A

Python version: 3.8.8 (default, Apr 13 2021, 12:59:45)  [Clang 10.0.0 ] (64-bit runtime)
Python platform: macOS-10.16-x86_64-i386-64bit
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

Versions of relevant libraries:
[pip3] mypy==0.812
[pip3] mypy-extensions==0.4.3
[pip3] numpy==1.20.1
[pip3] numpydoc==1.1.0
[pip3] torch==1.11.0a0+gite3989e6
[conda] blas                      1.0                         mkl
[conda] mkl                       2021.2.0           hecd8cb5_269
[conda] mkl-include               2021.2.0           hecd8cb5_269
[conda] mkl-service               2.3.0            py38h9ed2024_1
[conda] mkl_fft                   1.3.0            py38h4a7008c_2
[conda] mkl_random                1.2.1            py38hb2f4e1b_2
[conda] mypy                      0.812                    pypi_0    pypi
[conda] mypy_extensions           0.4.3                    py38_0
[conda] numpy                     1.20.1           py38hd6e1bb9_0
[conda] numpy-base                1.20.1           py38h585ceec_0
[conda] numpydoc                  1.1.0              pyhd3eb1b0_1
[conda] torch                     1.10.0a0+git808725b          pypi_0    pypi
Repository: flutter
Issue: flutter tool should place a `flutter.version` file in the build output next to the license file
Labels: c: new feature,tool,P2,team-tool,triaged-tool

Let's make this a trivial file to parse, maybe just starting with literally the version of Flutter, in the same format as we currently use for the `version` file we already generate.

Context here is making the version number available to other tooling that has been combined with the application but maybe not directly linked to the Flutter parts of the system, e.g. an Android or iOS third-party analytics package.
Repository: flutter
Issue: Document Android tool version policies/processes
Labels: platform-android,d: wiki,P2,team-android,triaged-android

It would be useful if we had a wiki page documenting things like:
- What version of Gradle should we be using (in the templates, in flutter/plugins, in samples, etc.)
  - What is the process for updating that; what are the places that should be checked/updated?
- What compilation SDK should we be using for flutter/plugins and samples (hard-coded? rolling?)
  - When should we update it?
- What Android versions should we be testing on, in which repositories?
  - When do we update that?

Right now a lot of this is ad hoc and/or institutional knowledge. It's hard for someone to look at, e.g., the gradle versions version in use in flutter/plugins and know if it's intentional, or just legacy based on what happened to be checked in and never updated.

The problems we had with the gradle 7 update in flutter/plugins also shows that the can be non-obvious aspects to doing one of these updates, and having a place to document that for future rolls would be useful.

/cc @blasten
Repository: PowerToys
Issue: Option to ignore monitor/taskbar edge borders when setting space around zones
Labels: Idea-Enhancement,FancyZones-Editor,FancyZones-Layouts,Product-FancyZones

### Description of the new feature / enhancement

I want to set space between my zones but when I do so, it adds space between the edge borders of my screen and taskbar as well.  It would be nice to have an option to either include or exclude those borders when configuring spacing.

### Scenario when this would be used?

Space between zones have been clearly deemed important and is an available option, but I dislike a lot of wasted space.  I'd like to have space between zones, but keep the zones flush to my monitor/taskbar edge borders.

### Supporting information

_No response_
Repository: pytorch
Issue: Jacobian mismatch for `nn.functional.ctc_loss`
Labels: high priority,module: autograd,module: nn,triaged,actionable,module: correctness (silent)

### 🐛 Describe the bug

When adding `OpInfo` for nn.functional.ctc_loss in https://github.com/pytorch/pytorch/pull/67464, `test_fn_grad` is failed with `GradcheckError: Jacobian mismatch for output 0 with respect to input 0`

### Versions

viable/strict

cc @ezyang @gchanan @zou3519 @bdhirsh @jbschlosser @albanD @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7 @mruberry @walterddr
Repository: pytorch
Issue: `test_forward_mode_AD` hangs for `nn.functional.cosine_embedding_loss`
Labels: module: autograd,module: nn,triaged,module: deadlock,module: forward ad

### 🐛 Describe the bug

When adding `OpInfo` for `nn.functional.cosine_embedding_loss` in https://github.com/pytorch/pytorch/pull/67465, `test_forward_AD` is enabled even though `supports_forward_ad` is `False` by default.
And `test_forward_AD` hangs forever during my local tests.

### Versions

viable/strict

cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7 @mruberry @jbschlosser @walterddr @kshitij12345
Repository: pytorch
Issue: integer (and possibly float16) matmul fails test_noncontiguous_samples on CPU (and all backward dtypes, too?)
Labels: high priority,triaged,module: linear algebra,module: correctness (silent)

### 🐛 Describe the bug

This causes the following tests to fail:

- test_noncontiguous_samples___rmatmul___cpu_int64
- test_noncontiguous_samples_linalg_multi_dot_cpu_int64
- test_noncontiguous_samples_matmul_cpu_int64

Skips will need to be removed to run these tests.

The test doesn't validate all data types. @ngimel points out this is likely our native matmul implementation, which is also used for float16 (so that's likely broken, too). 

Update: looks like backward fails for additional dtypes! Updated title too. The entire test is now skipped.

### Versions

This doesn't reproduce for me locally. The issue may be that CI does (or doesn't?) have FBGEMM but my local CI doesn't (or does). 

cc @ezyang @gchanan @zou3519 @bdhirsh @jbschlosser @jianyuh @nikitaved @pearu @mruberry @walterddr @IvanYashchuk @xwang233 @Lezcano
Repository: pytorch
Issue: [Feature] Separate, Queryable Alias Parser 
Labels: oncall: jit

### 🚀 

It is often the case within JIT passes that you might want to query an operator aliasing behavior - for example, this operator is functional, are there any aliased sets in the output that might alias the input, etc. Right now this is embedded within alias_analysis.cpp, so the only way to access this information is to analyze the whole graph.

There is also a need for the same parser within autograd, see https://github.com/pytorch/pytorch/blob/93d326c86847ed688b8c19f6a27bd984ee47dc80/torch/csrc/autograd/autograd_not_implemented_fallback.cpp#L46. It would be great to have a mechanism that would parse this information in one central repository, and potentially cache it per operator as needed (this would be useful for the autograd case, which is invoked on every invocation of the operator).  We should centralize alias parsing in one location to avoid divergent semantics. 

### Versions

current
Repository: flutter
Issue: [IOS] onPlatformBrightnessChanged is called twice when the app goes to the background
Labels: platform-ios,engine,has reproducible steps,P2,found in release: 2.5,found in release: 2.6,team-ios,triaged-ios

The [onPlatformBrightnessChanged](https://api.flutter.dev/flutter/dart-ui/SingletonFlutterWindow/onPlatformBrightnessChanged.html) callback is called twice when the app goes to the background despite the fact that there is no change made to the brightness mode of the platform. The brightness is always incorrect in the first call. I can confirm that the problem occurs on both iOS Simulator and the real device.

## Steps to Reproduce

1. Execute `flutter run` on the code sample.
2. Switch to another app or send the app to the background. (`onPlatformBrightnessChanged` will be called twice.)
3. Return to the app.

<details>
<summary>Code sample</summary>

```dart
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatefulWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  State<MyApp> createState() => _MyAppState();
}

class _MyAppState extends State<MyApp> {
  @override
  void initState() {
    final window = WidgetsBinding.instance?.window;

    if (window != null) {
      window.onPlatformBrightnessChanged = () {
        print(window.platformBrightness);
      };
    }

    super.initState();
  }

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter App',
      darkTheme: ThemeData(
        scaffoldBackgroundColor: Colors.black,
        textTheme: const TextTheme(
          bodyText2: TextStyle(
            color: Colors.white,
          ),
        ),
      ),
      home: Scaffold(
        appBar: AppBar(
          title: const Text("Flutter App"),
        ),
        body: Builder(
          builder: (context) => Center(
            child: Text(
              "Platform Brightness: ${MediaQuery.of(context).platformBrightness}",
            ),
          ),
        ),
      ),
    );
  }
}

```

</details>
Repository: pytorch
Issue: [JIT][Feature] Runtime Verifier of Alias Annotations
Labels: oncall: jit

### 

Currently, we have a [testing pass](https://github.com/pytorch/pytorch/blob/master/torch/csrc/jit/passes/utils/check_alias_annotation.cpp) that checks for alias annotation errors, which include failure to specify writes, and bad aliasing annotations. However, it's limited in the tests that it understands, and is not attachable to a model, which limits its ability to test aliasing more broadly.

We should write a verification pass that replaces the current opinfo test and can also be hooked up to a model to verify all of its aliasing properties.
Repository: flutter
Issue: Flutter Web app not resizing on iframe on Firefox
Labels: engine,platform-web,has reproducible steps,browser: firefox,P2,found in release: 2.5,found in release: 2.6,team-web,triaged-web

<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill out the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

Flutter Web apps do not resize with the browser window when embedded in an iframe on Firefox. It also does not resize when going fullscreen in Firefox, leaving part of the screen black. This functionality works correctly in Chrome.

## Steps to Reproduce

<!-- Please include full steps to reproduce so that we can reproduce the problem. -->

1. Embed Flutter Web app in iframe with dynamic width or height (width:100%)
2. Resize browser window or go fullscreen
3. Iframe resizes but Flutter does not

<details>
<summary>Code sample</summary>

<!--
      Please create a minimal reproducible sample that shows the problem
      and attach it below between the lines with the backticks.

      To create it you can use `flutter create bug` command and update the `main.dart` file.

      Alternatively, you can use https://dartpad.dev/
      which is capable of creating and running small Flutter apps.

      Without this we will unlikely be able to progress on the issue, and because of that
      we regretfully will have to close it.
-->

```dart
```
<html>
<body>
  <iframe src="https://gallery.flutter.dev/" style="border:none; width:100%;height:100%;" scrolling="no">
  
</iframe>


</body>
</html>

</details>

<details>
  <summary>Logs</summary>

</details>


<!--
      Consider also attaching screenshots and/or videos to better
      illustrate the issue.

      You can upload them directly on GitHub.
      Beware that video file size is limited to 10MB.
-->
Repository: godot
Issue: VisualScript: "found sequence bit but not the node in the stack" error printed to console
Labels: bug,topic:visualscript

### Godot version

3.3.4.stable

### System information

windows 10 home

### Issue description

my game started throwing the error 
"found sequence bit but not the node in the stack" 
and highlighting a visual script node during debugging.

i couldn't find any thing wrong with my code,
and when i tried to redo the nodes connections it kept giving me an error along the lines of 

"E 0:18:16.801   sequence_connect: Condition "instances.size()" is true.
  <C++ Source>  modules/visual_script/visual_script.cpp:445 @ sequence_connect()"

### Steps to reproduce

it should give the error immediately upon running the code
if not, you can move the kinematic body with the arrow keys
and rotate with enter

### Minimal reproduction project

[New folder.zip](https://github.com/godotengine/godot/files/7437300/New.folder.zip)