sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: E0597: `lock` does not live long enough (surprising error, the message could be more helpful)
Labels: A-borrow-checker,T-compiler,C-bug

I tried compiling this code:

```rust
fn main() {
    let lock = std::sync::Mutex::new(10);
    if let Ok(_) = lock.try_lock() {}
}
```

Error:

```
error[E0597]: `lock` does not live long enough
 --> src/main.rs:3:20
  |
3 |     if let Ok(_) = lock.try_lock() {}
  |                    ^^^^-----------
  |                    |
  |                    borrowed value does not live long enough
  |                    a temporary with access to the borrow is created here ...
4 | }
  | -
  | |
  | `lock` dropped here while still borrowed
  | ... and the borrow might be used here, when that temporary is dropped and runs the destructor for type `std::result::Result<std::sync::MutexGuard<'_, i32>, std::sync::TryLockError<std::sync::MutexGuard<'_, i32>>>`
  |
  = note: The temporary is part of an expression at the end of a block. Consider adding semicolon after the expression so its temporaries are dropped sooner, before the local variables declared by the block are dropped.

error: aborting due to previous error

For more information about this error, try `rustc --explain E0597`.
error: could not compile `tmp`.

To learn more, run the command again with --verbose.
```

I'm surprised that this does not compile!

The error message suggests adding a semicolon after the expression, but it's not obvious to me what exactly the expression is and where the semicolon should go. A suggestion on where to place the semicolon would be helpful.

The solution is this and compiles just fine:

```rust
fn main() {
    let lock = std::sync::Mutex::new(10);
    if let Ok(_) = lock.try_lock() {};
}
```
Repository: pytorch
Issue: RuntimeError CUDA error despite CUDA available and GPU supported
Labels: module: binaries,module: cuda,module: error checking,triaged

Got the following error (on Ubuntu 18.04 with PyTorch 1.14, Nvidia driver version 440.64, CUDA toolkit 10.1, GPU GeForce GTX Titan) despite PyTorch saying CUDA and CUDNN are available:

RuntimeError: CUDA error: no kernel image is available for execution on the device

Script to reproduce:

```
import torch
print(torch.__version__)
print(torch.cuda.is_available())
print(torch.backends.cudnn.enabled)
device = torch.device('cuda')
print(torch.cuda.get_device_properties(device))
print(torch.tensor([1.0, 2.0]).cuda())
```

Output:

```
1.4.0
True
True
_CudaDeviceProperties(name='GeForce GTX TITAN', major=3, minor=5, total_memory=6082MB, multi_processor_count=14)
Traceback (most recent call last):
  File "test_pytorch_cuda.py", line 7, in <module>
    print(torch.tensor([1.0, 2.0]).cuda())
  File "/home/deepstation/anaconda3/envs/pytorch/lib/python3.8/site-packages/torch/tensor.py", line 159, in __repr__
    return torch._tensor_str._str(self)
  File "/home/deepstation/anaconda3/envs/pytorch/lib/python3.8/site-packages/torch/_tensor_str.py", line 311, in _str
    tensor_str = _tensor_str(self, indent)
  File "/home/deepstation/anaconda3/envs/pytorch/lib/python3.8/site-packages/torch/_tensor_str.py", line 209, in _tensor_str
    formatter = _Formatter(get_summarized_data(self) if summarize else self)
  File "/home/deepstation/anaconda3/envs/pytorch/lib/python3.8/site-packages/torch/_tensor_str.py", line 87, in __init__
    nonzero_finite_vals = torch.masked_select(tensor_view, torch.isfinite(tensor_view) & tensor_view.ne(0))
RuntimeError: CUDA error: no kernel image is available for execution on the device
```

cc @ezyang @seemethere @ngimel
Repository: flutter
Issue: Cupertino route/transition should block touch events
Labels: platform-ios,framework,a: fidelity,f: cupertino,f: routes,c: proposal,P2,has partial patch,team-design,triaged-design

I think block any touch events during Cupertino transition is reasonable.
Repository: flutter
Issue: TabSwitchingView should cache tabs
Labels: framework,f: cupertino,c: proposal,P3,team-design,triaged-design

## Issue 

Currently, the `TabSwitchingView` creates a new list of children on every build. Wouldn't it be more performant if we cache that list and only recreate it when the active tab changes? 

## Context

I am currently using a `CupertinoTabScaffold` which depends on `MediaQuery`. If the MediaQuery changes a new `TabSwitchingView` is created with identical configuration, which results in recalling the `tabBuilder` for at least the active index. So if I, for example, open the keyboard big parts of my active page are rebuilt.

From https://api.flutter.dev/flutter/widgets/StatefulWidget-class.html#performance-considerations:
>If a subtree does not change, cache the widget that represents that subtree and re-use it each time it can be used. It is massively more efficient for a widget to be re-used than for a new (but identically-configured) widget to be created.


Can please someone confirm that I am right? I would work on that.
Repository: pytorch
Issue: Add Specific Warning/Error For Unsupported GPU or Systems
Labels: module: cuda,triaged,enhancement

## 🚀 Feature
Add specific Warning/Error message for unsupported GPU or Systems 

## Motivation

Currently prebuilt binaries only support specific cuda versions and systems. When an unsupported device install pytorch and try to use cuda, it gets generic error "RuntimeError: CUDA error: no kernel image is available for execution on the device" This error is very confusing for beginners and easy to miss original reason.

## Pitch

Instead of getting generic error. More specific error would be nice. Briefly explaining current binary is not supports GPU or system. Maybe it can also include some FAQ link for further details or solutions

## Alternatives


## Additional context

Original bug report [#31285](https://github.com/pytorch/pytorch/issues/31285)


cc @ngimel
Repository: go
Issue: x/tools/gopls: use telemetry library to check if completion exceeded its timeout
Labels: help wanted,gopls,Tools

As part of debugging https://github.com/golang/go/issues/38269, we've been discussing how we can indicate in tests that completion failed because of a timeout instead of a genuine failure. We don't want to return an error in this case because we still want to return whatever completion items we were able to produce before the timeout. @findleyr suggested that we could use the telemetry library for this.

/cc @ianthehat
Repository: PowerToys
Issue: Detect when apps that can conflict and alert users
Labels: Idea-Enhancement,Area-Quality,Needs-Spec

On startup, we should alert users that there are known apps that can interfere with PowerToys.  "PowerToys has detected a known app, APP_THAT_IS_AFFECTING, running that could impact your experience"

I know we have others but from #1943, #1493:

- AutoHotkey 
- start10
- Dell  Display manager
- Rivatuner Statistics Server (https://github.com/microsoft/PowerToys/issues/1872)
- Corperate app causing SentryBay #5414
Repository: flutter
Issue: TextFields (and TextFormFields) should allow displaying error state without error text
Labels: a: text input,c: new feature,framework,f: material design,c: proposal,P2,team-design,triaged-design

<!-- 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 our the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Use case

There are occasions where multiple `TextField` (or more likely `TextFormField`) are used on a page and the UX could call for a custom error solution instead of each textfield displaying an error message. We want to maintain the validate logic that exists on the Form but allow the developer to decide whether each textfield should show its error text.

## Proposal

Adding a new parameter to `InputDecoration` that tells TextFields they should not display their error text but still display any other error specific content (errorBorder, etc)

This would have to also work with the validate logic of `TextFormField` as well so that if a form is validated the error text can choose to not be displayed on each text field.

cc @justinmc 
Similar to https://github.com/flutter/flutter/issues/52634
Repository: flutter
Issue: Test that defer-loading flutter_localizations is effective
Labels: framework,c: performance,a: internationalization,a: size,platform-web,perf: app size,P2,team-web,triaged-web

According to @perclasson's research loading all localizations eagerly costs us >1 MB in gzipped code size (>7 MB of ungzipped JavaScript). Defer-loading localizations removes all that cost. For example, the new Flutter Gallery goes from 2.2 MB down to 0.9 MB gzipped (or from 11 MB to 3.6 MB ungzipped).

We should write a test that verifies that defer-loading localizations is effective. This test will protect us from accidentally loading localizations eagerly due changes in the framework or in the compiler.
Repository: flutter
Issue: Document how to write a speed performance test
Labels: a: tests,framework,c: performance,d: wiki,perf: speed,P2,team-framework,triaged-framework

See https://github.com/flutter/flutter/pull/52063 for an example speed performance test. We should document that in README or wiki so future test writers don't have to dig out a PR to learn how to write a test.
Repository: flutter
Issue: Document how to write an app size performance test
Labels: a: tests,framework,c: performance,d: api docs,perf: app size,P2,team-framework,triaged-framework

See https://github.com/flutter/flutter/pull/18522 for an example speed performance test. We should document that in README or wiki so future test writers don't have to dig out a PR to learn how to write a test.
Repository: flutter
Issue: Document how to write an energy performance test
Labels: a: tests,framework,c: performance,d: api docs,perf: energy,P3,team-framework,triaged-framework

See https://github.com/flutter/flutter/pull/41578 for an example speed performance test. We should document that in README or wiki so future test writers don't have to dig out a PR to learn how to write a test.

This is currently blocked by https://github.com/flutter/flutter/issues/45435
Repository: flutter
Issue: Consider a different strategy of launching and embedding devtools
Labels: c: new feature,tool,d: devtools,P3,team-tool,triaged-tool

Currently the tool can launch dev_tools via calling dev_tools server directly. This is advantageous, because all of the devtools resources will be bundled into flutter and can be accessed without additional downloads.

On the other hand, the devtools version used from the command line is now tied to the flutter release. While devtools is still in the process of maturing, pinning to an older version delays bug fixes and feature updates. 

devtools and the flutter tool only interact through the vm service protocol, so even major changes in the devtools app should not effect the flutter tool.

Another approach would be something like `pub global activate devtools`, which would always pull the latest version.

fyi @jacob314 @zanderso
Repository: excalidraw
Issue: Explore migrating to IndexedDB for data storage
Labels: enhancement,discussion

Based on https://github.com/excalidraw/excalidraw/issues/1245#issuecomment-609481939  it might be worthwhile to consider IndexedDB for an asynchronous API to store data. 

~Also need to evaluate if libraries like [localForage](https://github.com/localForage/localForage) that has options for IndexDB ~~,WebSQL~~ and falls back to localStorage.~ cc @dwelle
Repository: terminal
Issue: Feature request: Input focus follows mouse
Labels: Help Wanted,Area-UserInterface,Product-Terminal,Issue-Task

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

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

Focus follows mouse allows one to direct input into the exposed terminal tab while another window is selected so long as the mouse pointer is positioned anywhere over the Windows Terminal window.

<!-- 
A clear and concise description of what the problem is that the new feature would solve.
Describe why and how a user would use this new functionality (if applicable).
-->

This will reduce extra mouse clicks and make switching input focus more streamlined.

# Proposed technical implementation details (optional)

<!-- 
A clear and concise description of what you want to happen.
-->
Given that another window is selected and active, focus follows mouse allows one to direct input into the exposed terminal tab when the mouse pointer is positioned anywhere over the Windows Terminal window. One does not have to click on the Windows Terminal window to active input focus.
Repository: react-native
Issue: ESLint does not find React Native components
Labels: Needs: Repro,Needs: Attention

Please provide all the information requested. Issues that do not follow this format are likely to stall.

## Description

I'm getting these ESLint errors in all of my js files, which import React Native components. Imports from all other libraries work just fine and the app also compiles and runs without problems. Any idea what could be the reason?

```
  3:3  error  Text not found in 'react-native'        import/named
  4:3  error  View not found in 'react-native'        import/named
  5:3  error  ScrollView not found in 'react-native'  import/named
  6:3  error  StyleSheet not found in 'react-native'  import/named
```

```
import {
  Text,
  View,
  ScrollView,
  StyleSheet 
} from 'react-native';

```

```
"react-native": "0.62.0",
"eslint": "6.8.0",
"eslint-plugin-react-native": "3.8.1",
"@react-native-community/eslint-config": "1.0.0",
"flow-bin": "0.121.0" (not using in my code)
```

## React Native version:

```
System:
    OS: macOS 10.15.3
    CPU: (4) x64 Intel(R) Core(TM) i7-6567U CPU @ 3.30GHz
    Memory: 1.27 GB / 16.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 12.16.1 - /usr/local/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.13.4 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 13.4, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
    Android SDK:
      API Levels: 28, 29
      Build Tools: 21.1.1, 21.1.2, 22.0.0, 22.0.1, 23.0.1, 23.0.2, 23.0.3, 24.0.1, 25.0.0, 25.0.2, 25.0.3, 26.0.0, 26.0.2, 27.0.3, 28.0.0, 28.0.2, 28.0.3, 29.0.2
      Android NDK: Not Found
  IDEs:
    Android Studio: 3.6 AI-192.7142.36.36.6241897
    Xcode: 11.4/11E146 - /usr/bin/xcodebuild
  Languages:
    Python: 2.7.17 - /usr/local/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1 
    react-native: 0.62.1 => 0.62.1 
  npmGlobalPackages:
    *react-native*: Not Found
```

## Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

1. eslint

## Expected Results
Describe what you expected to happen.

No errors.

## Snack, code example, screenshot, or link to a repository:
https://stackoverflow.com/questions/60973737/eslint-does-not-find-react-native-components
Repository: vscode
Issue: Trim Final Newlines integrates poorly with EditorConfig for Windows files
Labels: feature-request,editor-core

Overall VSCode does a decent job integrating with EditorConfig. Including the Trim Final Newlines setting once enabled.

However, where final EOLs are disabled (such as for .AHK and other Windows-centric files), then Trim Final Newlines fails to delete final EOLs. How can we make sure that VSCode respects more EditorConfig configurations?

In particular:

* Binary files should be ignored/preserved as-is.
* .PATCH files should be ignored/preserved as-is.
* Text files with contents consisting of exactly one EOL (CRLF, LF, or CR) should be ignored/preserved as-is.
* .CS, .FS, .FSX, .VBS, .BAT, .COM, .PS1, .AHK, and other Windows-centric files should have zero trailing EOLs at the end of the buffer.
* All other files should have exactly one (LF) EOL at the end of the buffer.

VSCode 1.43.2
Windows 10
Repository: flutter
Issue: Various flutter tool commands neglect to document positional arguments
Labels: tool,d: api docs,has reproducible steps,P3,team-tool,triaged-tool,found in release: 3.19,found in release: 3.20

A number of `flutter` tool commands neglect to document positional arguments.  For example:

```$ flutter help version
List or switch flutter versions.

Usage: flutter version [arguments]
-h, --help          Print this usage information.
-f, --[no-]force    Force switch to older Flutter versions that do not include a
                    version command

Run "flutter help" to see global options.
```
It just lists `[arguments]` without specifying what they are.  One can deduce that you can pass a version number, but does it require a `v` prefix? `[arguments]` also implies that there can be more than one.

Contrast to `flutter help channel` which instead specifies `Usage: flutter channel [<channel-name>]`.

`flutter install` also neglects to document positional arguments.

The help for any of the `flutter build` subcommands also neglect to mention positional arguments, but it seems like they accept filenames.  Without looking at the code, I don't know what happens or what's intended to happen.

I'm sure there are others, but it's hard to tell which commands expect positional arguments.
Repository: pytorch
Issue: [quantization] torch.quantized_lstm and torch.quantized_gru not documented
Labels: module: docs,oncall: quantization,low priority,triaged

These functions don't seem to have docstrings associated with them. I noticed this after moving them to c10 dispatch and aliasing the names in the `torch` namespace to those.

Currently added to the whitelist in `test_docs_coverage.py`


cc @svekars @carljparker @jerryzh168 @jianyuh @raghuramank100 @vkuzo @jgong5 @Xia-Weiwen @leslie-fang-intel @dzhulgakov @jamesr66a
Repository: godot
Issue: SetCell and atlas not work
Labels: documentation

**Godot version:**
3.2.1 mono 64

**OS/device including version:**
win10 64

**Issue description:**
A tile that is part of an atlas cannot be referenced with SetCell.
For example, you cannot use SetCell with a tile that is part of an atlas, you cannot refer to a tile that is part of an atlas.

**Steps to reproduce:**
Build an atlas with some tiles.
Try using SetCell and print some of those tiles on the screen.
You will not be able to because there is no way to reference the tiles in an atlas.

**Minimal reproduction project:**
[testAtlas.zip](https://github.com/godotengine/godot/files/4440560/testAtlas.zip)
Repository: flutter
Issue: Add `-Werror=undeclared-selector` to engine builds
Labels: engine,c: proposal,P3,team-engine,triaged-engine

This seems to be on for g3 builds but not local builds/

See also: https://github.com/flutter/engine/pull/17535
Repository: flutter
Issue: iOS: Add `-Werror=overriding-method-mismatch` to engine builds
Labels: engine,c: proposal,P3,team-engine,triaged-engine

This should be a pretty benign warning to follow.  I ran into one place where we were violating it.
Repository: opencv
Issue: matchShapes turns large mismatches into perfect matches
Labels: feature,category: imgproc,Hackathon

https://github.com/opencv/opencv/blob/master/modules/imgproc/src/matchcontours.cpp

An issue was described in StackOverflow with OpenCV matchShapes not well matching a given (supposedly unknown) shape to a shape in a set of known, predefined shapes (various computer related device connecting plugs).
https://stackoverflow.com/questions/55529371/opencv-shape-matching-between-two-similar-shapes/
It was obvious what shape the test "unknown" was supposed to match but matchShapes wasn't reporting the right answer.

There were helpful hints given for matching shapes but I thought macthShapes should have done this particular matching without having to force substantial preprocessing.  The HuMoments are intended to remove scale differences but matchShapes wasn't picking that up.

I coded a Java translation of matchShapes and changed the "eps" variable to a much smaller number (1.e-20 is plenty small enough for these data).

matchShapes works correctly with a smaller "eps."

I could not find the basis for the current value of 1.e-5 and it apparently is intended to protect the Log10 from a 0 argument and ignore too big of discrepancies.  Unfortunately the true large discrepancy then appears as a perfect match resulting in incorrect matching.

If this were my code with limited distribution, I'd fix the eps with value no more than 1.e-20.

There is a chance there is usage somewhere that is now relying on the inappropriate value of eps.  So what to do?

If it is your policy not to make such corrections and you can't correct eps now, then please at least document the restriction and ramification of the too small value wherever matchShapes is referenced.

Another possibility is to add eps to the parameter list and make it the default of 1.e-5. I use Java and I'm not sure how that would flow through to my usage but I am hopeful you could take care of the problem that way.

The other method of correction is to make the eps a parameter with a default small value say 1.e-20 on a new method called matchShapes2.
Repository: pytorch
Issue: In AutogradContext, get_saved_variables() should be renamed to get_saved_tensors()
Labels: module: cpp,triaged

This is to better match the Python API `ctx.saved_tensors`.

I believe we originally named it `get_saved_variables()` because there was still a Tensor vs. Variable distinction at that time. Now that Tensor and Variable are the same, we can deprecate `get_saved_variables()` and replace it with `get_saved_tensors()`.

cc @yf225
Repository: PowerToys
Issue: [FZ Editor] GridResizer is not centrally aligned
Labels: Good first issue,FancyZones-Editor,Product-FancyZones,Area-Quality,Priority-3

# Steps to reproduce
Use the FancyZones grid editor.

# Expected behavior
The GridResizer thumbs should be horizontally and vertically aligned with the zone.

# Actual behavior
The GridResizers are added, but should have a negative Left (horizontal) or Top (vertical) margin so they are in the center of the zone. This results in a bad visual representation where the zone label and GridResizer are not aligned.

# Screenshots
<img width="846" alt="Annotation 2020-04-06 232708" src="https://user-images.githubusercontent.com/9866362/78607083-acd32880-785e-11ea-97eb-e822c781c511.png">