sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: [Focus] When Focus cycles in a Scrollable, the focused item should be scrolled into view
Labels: framework,a: accessibility,a: desktop,f: focus,has reproducible steps,P2,found in release: 3.3,found in release: 3.5,team-framework,triaged-framework

```dart
void main() => runApp(App());

class App extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Material(
        child: ListViewFocusRepro(),
      ),
    );
  }
}

class ListViewFocusRepro extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: ListView(
        padding: EdgeInsets.zero,
        children: [
          Container(
            height: 300,
            child: FlatButton(child: Text('Button 1'), onPressed: () {}),
          ),
          Container(
            height: 300,
            child: FlatButton(child: Text('Button 2'), onPressed: () {}),
          ),
          Container(
            height: 300,
            child: FlatButton(child: Text('Button 3'), onPressed: () {}),
          ),
        ],
      ),
    );
  }
}
```

On desktop, notice that pressing tab when 'Button 3' is focused sets the focus to 'Button 1', as expected, but it isn't visible. 

The same issue occurs when shift-tabbing from 'Button 1' to 'Button 3'.

In both cases, the focused element should be scrolled into view

For a more complex example, see https://gallery.flutter.dev/#/crane
Repository: pytorch
Issue: Resnet Model always predicting same label
Labels: triaged,module: vision

I am currently playing around with PyTorch trying to successfully attempt facial recognition on a custom dataset of 48 classes with over 5000 images using Resnet50. During training my training and validation set accuracies are fairly high in the regions of 99% for both sets, however when I attempt to test my model on a number of unseen test images, I always get the same label? Would you know what the reason for this is?Is this a bug?


cc @fmassa
Repository: PowerToys
Issue: Path Shortener
Labels: Idea-New PowerToy

 A "**Destination path too long**" fix tool
 
When copying folders sometimes the new location exceeds the max character length

Goal: 
- Visualize and shorten long paths exceeding X characters.
- Additionally, search for folders/file names longer than X.
Repository: pytorch
Issue: Split more pages into sub-topics
Labels: module: docs,triaged,module: doc infra,open source

## 📚 Documentation

gh-37419 split up the "heaviest" pages into a leading pages and subpages. More can be done to split up pages (these have the most lines of HTML):
- [ ] [`docs/source/quantization.rst](https://pytorch.org/docs/stable/quantization.html)
- [ ] [`docs/source/tensors.rst`](https://pytorch.org/docs/stable/tensors.html#torch.Tensor)
- [ ] [`docs/source/nn.fuctional.rst`](https://pytorch.org/docs/stable/nn.functional.html)
- [ ] [`docs/source/distributions.rst`](https://pytorch.org/docs/stable/distributions.html)
- [ ] [`docs/source/autograd.rst`](https://pytorch.org/docs/stable/autograd.html)

The strategy would start with using `autosummary` like in gh-37419, but more work might be needed to split up classes with many methods. 

cc @ezyang @zou3519
Repository: pytorch
Issue: Formatting of topic and sub-topic pages
Labels: module: docs,triaged,module: doc infra

## 📚 Documentation

After gh-37419, there are now [subtopic pages](https://pytorch.org/docs/master/generated/torch.is_tensor.html#torch.is_tensor) underneath the [main topic pages](https://pytorch.org/docs/master/torch.html). 

Should the subtopic pages have a right-navbar to indicate where they fall inside the topic pages?

In any case, the left- and right- navbars are quite long without alot of visual formatting to indicate where the current page is located. Indenting or color or other clues could help users see where they are.

cc @ezyang @zou3519
Repository: electron
Issue: Child window minimizes to a black rectangle
Labels: platform/windows,bug :beetle:,8-x-y,11-x-y

<!--  As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->

### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->

* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

### Issue Details

* **Electron Version:**
  * 5.0.x
  * 8.x.y
* **Operating System:**
  * platform/windows 10

### Expected Behavior
Show some sort of identification for the child window when it is minimized (title, id or custom text) with buttons.

### Actual Behavior
Window minimizes in to a black rectangle.

### To Reproduce
Create frame-less windows:

let mainWin = new BrowserWindow({
    width:500,
    height:500,
    frame: false
});

let childWin = new BrowserWindow({
    width:500,
    height:500,
    frame: false,
    parent: mainWin // To relate the windows 
});

minimize the child window and it will turn into a black rectangle. 

### Screenshots
![window issue](https://user-images.githubusercontent.com/14168151/81297100-79f99b80-907b-11ea-8b2a-382a25bb06b9.png)


### Additional Information
I have been experiencing this issue in windows since electron 3.0.x. Currently on the latest v.8.2.5
Repository: nvm
Issue: Document that curl is required for nvm to work
Labels: needs followup,installing nvm

## Use case

I tried `nvm install 12.16.2` on an Ubuntu install that didn’t come with curl and nvm hung. (Oddly, `nvm install --lts` worked.) 

## Workaround

If curl is required (and my error was not due to some other issue), it should be documented in the readme. e.g.,

```
## Prerequisites

 - curl
```

Happy to issue a PR if necessary.
Repository: PowerToys
Issue: Share a zone for video conference apps
Labels: Idea-Enhancement,FancyZones-Layouts,Product-FancyZones

# Summary of the new feature/enhancement

It would be great to be able to share a zone in Fancyzones in Teams/Skype

crutkas: strongly believe #279 is the correct solution here
Repository: rust
Issue: Confusing error message "this doc comment doesn't document anything" when there is a syntax error right after a comment
Labels: C-enhancement,A-diagnostics,A-parser,T-compiler

I tried this code:

```rust
/// Some documentation. Below "async" is before "pub" by mistake.
async pub fn hello() {}

fn main() {
}
```

I expected to see this happen: a clear error message telling me about the mistake (`async` before `pub`).

Instead, this happened:

```
error: expected item after doc comment
 --> src/main.rs:1:1
  |
1 | /// Some documentation. Below "async" is before "pub" by mistake.
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ this doc comment doesn't document anything
```

This is a confusing error message. Without the comment, the error is clearer (though arguably still not completely obvious):

```
error: expected item, found keyword `async`
 --> src/main.rs:1:1
  |
1 | async pub fn hello() {}
  | ^^^^^ expected item
```

### 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.43.0
binary: rustc
commit-hash: unknown
commit-date: unknown
host: x86_64-unknown-linux-gnu
release: 1.43.0
LLVM version: 10.0
```

<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Backtrace</summary>
<p>

```
No backtrace.
```

</p>
</details>
Repository: terminal
Issue: Method to suppress the default CTRL+C/CTRL+V mapping specifically for WSL; profile-specific keybindings?
Labels: Issue-Feature,Area-Settings,Product-Terminal

Editor's Note (@DHowett-MSFT): This may be a good place to track profile-specific keybindings?

With the _classic_ Windows terminal, <kbd>Ctrl</kbd>+<kbd>c</kbd> and <kbd>Ctrl</kbd>+<kbd>v</kbd> can be used for copy and paste when working within a Windows shell just as I would expect/prefer. However, when using WSL, this is typically not the case and those keys are available for use by Linux applications such as Vim.

How can I replicate this same behavior with the new Windows Terminal?

Background:
When working specifically within the WSL environment, Vim is my primary editor and the presence of any <kbd>Ctrl</kbd>+<kbd>v</kbd> mapping effectively blocks the use of blockwise Visual mode (http://vimdoc.sourceforge.net/htmldoc/visual.html#CTRL-V).

Removal of these mappings in a global scope is undesirable since I do not want to lose the use of <kbd>Ctrl</kbd>+<kbd>c</kbd> and <kbd>Ctrl</kbd>+<kbd>v</kbd> for copy and paste when working within a Windows shell.

I realize that similar issues have been discussed at length and that any choice here is somewhat of a compromise, but the ability to replicate the current behavior of the _classic_ Windows terminal in this regard is a tradeoff that I find acceptable/desirable.
Repository: vscode
Issue: Use contentEditable for our hidden accessibility textArea
Labels: accessibility,editor-core,under-discussion

Investigate into using `contenteditable` instead of a plain `textArea` for our hidden accessibility field.
It migh have performance implications, but it would allow us to have richer accessibility content on each line. Including line number, breakpoints etc..
Repository: TypeScript
Issue: `typeChecker.getTypeArguments` returns unexpected extra type argument
Labels: Bug,Help Wanted

**TypeScript Version:**  3.8.3

**Search Terms:** getTypeArguments

**Code**

Given input like

```ts
class X extends Y<string> {}
```

Call `typeChecker.getTypeArguments(typeChecker.getTypeAtLocation(...))` on the `Y<string>` node.

**Expected behavior:**
You get back one type argument (string).

**Actual behavior:**
You get back two, `string` and `X`.

I imagine this is maybe something around how TS handles `this` typing internally, but as a user of the API I'm not sure I can predict when this function returns these or not.

**Playground Link:** <!-- A link to a TypeScript Playground "Share" link which demonstrates this behavior -->

**Related Issues:** <!-- Did you find other bugs that looked similar? -->
https://github.com/microsoft/TypeScript/issues/33693 suggests this API changed recently
Repository: go
Issue: Gerrit: messy merge commits created when merges are not fresh
Labels: Unfortunate,NeedsDecision

Gerrit took it upon itself to create a merge commit to merge CL 227650, itself a merge commit, because there was a commit on the target branch after the parent of the merge under review.

392a746b15 was created by Gerrit because d41987bb5b was on master after the parent of e067ce5225.

```
* 49367815c7 - (dev.boringcrypto) [dev.boringcrypto] crypto/internal/boring: reject short signatures in VerifyRSAPKCS1v15 (4 weeks ago) <Filippo Valsorda>
*   392a746b15 - Merge "[dev.boringcrypto] all: merge master into dev.boringcrypto" into dev.boringcrypto (4 weeks ago) <Gerrit Code Review>
|\
| *   e067ce5225 - [dev.boringcrypto] all: merge master into dev.boringcrypto (4 weeks ago) <Filippo Valsorda>
| |\
| | * 9baafabac9 - crypto/rsa: refactor RSA-PSS signing and verification (5 weeks ago) <Filippo Valsorda>
| | * aa4d92b8aa - cmd/link: skip symbol references when looking for missing symbols (5 weeks ago) <Joel Sing>
| | [...]
| | * 72e043e48b - cmd/doc: show variables of unexported types for -all (6 months ago) <Agniva De Sarker>
| | * c2edcf4b12 - crypto/tls: take key size into account in signature algorithm selection (6 months ago) <Filippo Valsorda>
* | | d41987bb5b - [dev.boringcrypto] misc/boring: add new releases to RELEASES file (6 weeks ago) <Filippo Valsorda>
|/ /
* | 79284c2873 - [dev.boringcrypto] crypto/internal/boring: make accesses to RSA types with finalizers safer (9 weeks ago) <Filippo Valsorda>
* | 6c64b188a5 - [dev.boringcrypto] crypto/internal/boring: update BoringCrypto module to certificate 3318 (9 weeks ago) <Filippo Valsorda>
```

I am tempted to rewrite history, as the dev.boringcrypto branch is confusing enough as is, and we need it to be clean enough for it to be possible to easily flatten into a patchset.

Gerrit should definitely refuse to merge an out of date merge commit, or update it, not make a merge commit for the merge commit. Regrettably, this also happened a number of times on master for dev.link merges: f092be8fd8, 00753d5232, da33f9c78a, cd42fa581a.

`git log --graph --oneline master` is now an unreadable maze, in part because of this and in part because it's unavoidable for long-running branches that get multiple merges from master before being merged multiple times into master. Not sure what we should do about that.

/cc @golang/osp-team
Repository: godot
Issue: Light2D not working on rotated polygon on bones
Labels: bug,topic:rendering

ver. 3.2.1  (gle3)
win 10

Moving Light2D over polygon stops working if bones are rotated or in certain position.

I have attached TSCN - mostly light works, but if you rotate polygon to some extent it stops working.
-> open TSCN
-> player (KinematicBody2D with bones and polygons) is rotated 90 degrees
-> Select Light 2D and move it to left or right, light disappears on far left or right side
[light2d_b13.zip](https://github.com/godotengine/godot/files/4594365/light2d_b13.zip)
Repository: rust
Issue: Bors links to the wrong build in GitHub Actions
Labels: T-infra,A-github-actions

When bors reports that a build failed in GitHub Actions, it links to the "bors build finished" meta-job instead of the actual job tha failed. This makes the UX for our contributors worse.
Repository: TypeScript
Issue: Suggestion: short-circuit type inference for ternary operators when both branches have the same type
Labels: Domain: Performance

From https://github.com/squidfunk/typescript-issue-38339-repro (courtesy of @squidfunk)

**TypeScript Version:**  3.9.1-rc

**Search Terms:** 

Subtype reduction, ternary

**Code**

```ts
import { JSX } from "preact"

type IntrinsicElements = JSX.IntrinsicElements[keyof JSX.IntrinsicElements]

export type IntrinsicElements2<
  T = IntrinsicElements
> = {
  [K in keyof T]: K extends "accept"
    ? T[K] | [string]
    : T[K]
}

export type IntrinsicElements3<
  T = IntrinsicElements2
> = {
  [K in keyof T]: K extends "class"
    ? T[K] | [boolean]
    : T[K]
}

export type IntrinsicElements4<
  T = IntrinsicElements3
> = {
  [K in keyof T]: K extends "id"
    ? T[K] | [number]
    : T[K]
}

export function foo(): IntrinsicElements4 | undefined {
  let t: IntrinsicElements4 | undefined
  // this takes 2 seconds to check
  return t
  // this takes 10 seconds to check
  // return true ? t : t
}
```

**Expected behavior:** `return t` and `return true ? t : t` check in a comparable amount of time

**Actual behavior:** the ternary is much slower

**Playground Link:** https://www.typescriptlang.org/play/?ts=Nightly#code/JYWwDg9gTgLgBAbzgKQMoA04F84DMoQhwBEYUApgIYDGMxAUPTAJ5jlwCSAdjFMFwGdg1AKIAbciHI8BcALwoMAOm69+Q0RKkyA2gGtyzCLkXoVPPoOHjJ0mAIC6jcgA9IsOCzacL661rsBACYAHno4OAAVeR81K01bGXoAPhiEcLgdAGk4fjgDIxNIhwAuOBzXGGkAE1liGmpyMDoMiIB+KOyHOAAfTIE4gHMnCIiyyK76LGc3aHgvdlVLDRttewBmMIjohSW-BLXglLSM7NyufMNjKNLyuEqauuoxSgEBBlG4Doms7r6dABGEAgEkoXBGo3Gk2m9Fc7nmrEWvniq0CABYtlEYnsUQEZOtjgp0hEznkCtdimUKi4qlxaiRgNUPqNvl1epkuABXEAA8hQCFjTq-KYzeF4TlcWjACAXXDAgAUAEoyjiVnj7Gj2RLquRcPxyNVEBkJPMVci1YkNVq6br9dUMgB6B0UGCcqAXeBOuAAMVeMAyLrdHqgnPYHXgZU9DrgqDEEAA7iKgA

**Related Issues:** #38339
Repository: pytorch
Issue: Quantile Regression Loss
Labels: module: nn,triaged,OSS contribution wanted

When interested in fitting an unknown probability distribution using a neural network model, we are sometimes interested in quantile regression. I suggest we add the quantile regression loss to the losses we have in pytorch.

* Example implementation [here](https://medium.com/the-artificial-impostor/quantile-regression-part-2-6fdbc26b2629).
* Relates to pytorch/audio#267

cc @albanD @mruberry
Repository: go
Issue: x/tools/present: no section headers in Markdown syntax
Labels: NeedsInvestigation

IIRC we used to be able to use `*` and `**` for section and subsection headers. It appears as though that's no longer the case: `#` terminates the content [1] (without an error...?), and `##` is a subsection header.

Not sure if this is a bug or feature request.

1: As in, no header is displayed and no content is displayed after that point.
Repository: terminal
Issue: MongoDB linewrap isn't working.
Labels: Product-Conpty,Area-Server,Issue-Bug,Priority-2,Impact-Correctness

# Environment

```none
Windows build number: [run `[Environment]::Replicable in CMD and Powershell]
Windows Terminal version (if applicable): 0.11.1251.0

Any other software?
None.
```

# Steps to reproduce

Run Mongo in the windows terminal and fill the first line with text.

# Expected behavior
Linewrap so that you can continue in the next line.
![imagen](https://user-images.githubusercontent.com/13491373/81338865-eb811c00-9072-11ea-87a5-74fc11ff48f8.png)


# Actual behavior
Linewrapping continues over itself.
![imagen](https://user-images.githubusercontent.com/13491373/81338669-a0670900-9072-11ea-8e1f-13cff8e4c5b5.png)
Repository: flutter
Issue: Strip plugins created from `dev_dependencies` from release-mode apps
Labels: a: tests,tool,a: build,f: integration_test,P2,blocked,a: plugins,team-tool,triaged-tool

2024-11-21 update from @matanlurey:

- Android work https://github.com/flutter/flutter/issues/157949 /cc @camsim99 
- iOS/macOS work https://github.com/flutter/flutter/issues/74274 /cc @cbracken 

---

Currently the flutter tool creates a plugin for all package dependencies, even though in the dev_dependencies section. We'd like to remove this behavior, since it can lead to plugins used for testing accidentally getting included in released builds. This will be a breaking change, so we can proceed in several steps.

1. Compute both the current and dependencies-only plugin list and use the current strategy. If discrepancies are found, print a warning that this will be disabled in a future release and how to fix.

2. Compute both the current and dependencies-only plugin list and use the dependencies only strategy. If discrepancies are found, print a warning/notification that certain plugins have been disabled and include how to fix.

3. Remove the current strategy, remove the warning.
Repository: flutter
Issue: SceneDisplayLag events have incorrect duration on Fuchsia
Labels: customer: fuchsia,framework,dependency: fuchsia,platform-fuchsia,P2,team-framework,triaged-framework

Sample measurements:
```
frame_target_time	
"610779766332"
current_frame_target_time	
"16666666"
vsync_transitions_missed	
"-36646"
```
Repository: pytorch
Issue: Div by zero error not triggered and inf not returned when dividing by 0 for some dtypes
Labels: module: numerical-stability,triaged,module: type promotion

## 🐛 Bug

For some combinations of types, division by an integer tensor with value zero neither throws an error nor returns inf, instead returning either -2^63 or 2^63-1 (for dtype torch.int64), with the sign either consistent with the sign of the numerator or not depending on if the operation is done on the GPU or not.

## To Reproduce

Steps to reproduce the behavior:

```
>>> 1 / torch.tensor(0.0)
tensor(inf)

>>> 1 / torch.tensor(0)
tensor(-9223372036854775808)

>>> 1.0 / torch.tensor(0)
tensor(-9223372036854775808)

>>> (-1) / torch.tensor(0)
tensor(-9223372036854775808)

>>> 1 / torch.tensor(0).cuda()
tensor(9223372036854775807, device='cuda:0')

>>> (-1) / torch.tensor(0).cuda()
tensor(-9223372036854775808, device='cuda:0')

>>> 1 / torch.tensor(0, dtype=torch.int32)
tensor(-2147483648, dtype=torch.int32)

>>> 1 / torch.tensor(0, dtype=torch.int32).cuda()
tensor(2147483647, dtype=torch.int32)

>>> torch.tensor(1.0) / torch.tensor(0)
tensor(inf)
```

## Expected behavior

Either tensor(inf) to be returned, with the sign consistent with the sign of the numerator, or for this error to be thrown: https://github.com/pytorch/pytorch/blob/f0f587366c1953755782f862c61e8772e10db971/aten/src/ATen/native/cpu/BinaryOpsKernel.cpp#L75.

## Environment

PyTorch version: 1.5.0+cu101
Is debug build: No
CUDA used to build PyTorch: 10.1

OS: Ubuntu 18.04 LTS
GCC version: (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
CMake version: Could not collect

Python version: 3.6
Is CUDA available: Yes
CUDA runtime version: 9.1.85
GPU models and configuration: GPU 0: GeForce GTX 1050 Ti
Nvidia driver version: 435.21
cuDNN version: Could not collect

Versions of relevant libraries:
[pip3] numpy==1.18.3
[pip3] torch==1.5.0+cu101
[pip3] torchaudio==0.5.0
[pip3] torchvision==0.6.0+cu101
[conda] Could not collect

cc @ezyang @gchanan @zou3519 @nairbv