sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Assert if an invisible widget is continuing to cause rebuilds, at least in some cases
Labels: framework,a: animation,a: error message,P2,team-framework,triaged-framework

Related idea to #51000 

Related to https://github.com/flutter/flutter/pull/50842

It would be nice if the framework warned you when you if you caused a widget to rebuild while it is invisible, perhaps with a directive to consider using a `Visibility` widget for this case. This can be a somewhat confusing thing to diagnose, as it's easy to imagine that your animated GIF or animated widget is not doing work once you can't see it anymore - and it can be particularly confusing if you're consuming the animation from third party package and not sure about whether the package is doing this automatically or not.

/cc @goderbauer @shihaohong @digiter @liyuqian
Repository: pytorch
Issue: Tensor.random_ is not implemented for bfloat16 on CPU(but implemented on CUDA)
Labels: module: cpu,triaged,module: random


```
In [1]: import torch

In [2]: t = torch.empty(100, dtype=torch.bfloat16, device='cpu')

In [3]: t.random_()
---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
<ipython-input-3-19301e232e42> in <module>
----> 1 t.random_()

RuntimeError: _th_random_ not supported on CPUType for BFloat16

In [4]: t = torch.empty(100, dtype=torch.bfloat16, device='cuda')

In [5]: t.random_()
Out[5]:
tensor([154., 228.,  30.,  46., 229., 165., 194.,   0., 138.,  97., 159.,  49.,
        126., 242.,  20.,  37., 121., 248.,  96., 250., 145., 142., 189., 200.,
         33., 210., 225.,  44., 189., 207., 165., 169., 251., 191.,   2.,  59.,
         33.,  75., 155.,  73., 175., 173., 209.,  50., 222., 116., 256., 229.,
        198., 208., 135., 218., 163., 235.,  21., 107., 134., 178.,  16.,  39.,
        124., 104., 231., 242., 157., 108., 177., 238.,  67., 225.,  33., 129.,
        193., 204., 195.,  64.,  94.,  72., 216., 189., 232., 207., 102., 107.,
        187.,  55.,  74.,  87., 220., 211.,   3.,  83.,  86.,  74., 149., 186.,
         85.,  29., 155.,  31.], device='cuda:0', dtype=torch.bfloat16)

```

cc @VitalyFedyunin
Repository: pytorch
Issue: Support pipelining the backward pass and optimizer.step() for distributed autograd.
Labels: oncall: distributed,triaged,module: rpc

## 🚀 Feature

## Motivation

Some pseudocode for what a training loop looks like when using distributed autograd today:

```
for data in iterator:
  loss = model.forward()
  dist_autograd.backward([loss])
  optim.step()
```

Distributed backward runs on multiple nodes and accumulates gradients on different nodes via RPC. Once the complete backward pass is done, only then we run `DistributedOptimizer.step()` which basically does an RPC to all of those nodes again and updates the parameters on those nodes. There is an opportunity here to pipeline these two operations such that they overlap and avoid additional RPCs.

## Pitch

Enhance the distributed backward pass to overlap with the optimizer. Once the distributed backward pass has computed all the gradients necessary for a particular parameter, we should just run the optimizer for that parameter inline as well (instead of waiting for the entire backward pass to be done and running the optimizer separately).

A couple of options in terms of how this can be done in the API:

1. Allow distributed backward to take a DistributedOptimizer instance as part of the backward API to execute the optimizer in parallel.
2. Register post hooks for the parameters we need to optimize, run the optimizer in the post hooks and enable post hooks for distributed autograd.

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @xush6528 @osalpekar @jjlilley
Repository: rust
Issue: rustc's -W/A/D/F options should ignore clippy:: lints
Labels: A-lints,C-bug

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

In code, rustc will ignore:
```
#![allow(clippy::foo)]
```

But it fails with:
```
$ rustc --crate-type lib --emit metadata -Aclippy::foo t.rs
error[E0602]: unknown lint: `clippy::foo`
  |
  = note: requested on the command line with `-A clippy::foo`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0602`.
```

It should ignore unknown options consistent with directives in source code.
The current behaviour means that one can't share the same command line when invoking `rustc` vs `clippy-driver`.

### 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-nightly (8aa9d2014 2020-02-21)
binary: rustc
commit-hash: 8aa9d2014f4e5258f83b907e8431c59a33acdae7
commit-date: 2020-02-21
host: x86_64-unknown-linux-gnu
release: 1.43.0-nightly
LLVM version: 9.0
```
Repository: create-react-app
Issue: Control TSC's noEmit or emitDeclarationOnly when using composite projects
Labels: issue: proposal,needs triage

`create-react-app` doesn't work in composite typescript projects, because for composite projects `emitDeclarationOnly` must be used instead of `noEmit` (when using noEmit: true and composite: true typescript compiler throws an error). I suggest to add a check - if typescript project is composite-based, use `emitDeclarationOnly` flag instead of `noEmit`.

See https://github.com/microsoft/TypeScript/issues/36917 for more information.
Repository: ant-design
Issue: dataIndex with dot notation returns undefined when getting value  on EditCell example [Table Component]
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/cool-leaf-7mnjj)

### Steps to reproduce
Set `dataIndex` to a nested object property

### What is expected?
`record[dataIndex]` should return the nested object value when trying to edit the cell value.

### What is actually happening?
It returns `undefined`

| Environment | Info |
|---|---|
| antd | 3.26.12 |
| React | 16.12.0 |
| System | MacOS 10.15.3 |
| Browser | Chrome 79.0 |

---
Take a look at console in sandbox link, temp workaround  is to add `object-path` npm package in order to get the record value at current nested path.


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: vscode
Issue: Undo/Redo: consider to show global undo/redo as label in menu
Labels: feature-request,undo-redo

Refs: #91248

I think we should indicate to the user that the next Undo or Redo triggers as global undo/redo by showing this in the Edit menu. E.g. `Undo (Rename)` and `Redo (Rename)`. 

I would not change the labels for operations that happened from user typing and not refactorings.
Repository: terminal
Issue: Add title to split window
Labels: Help Wanted,Area-UserInterface,Product-Terminal,Issue-Task

# Description of the new feature/enhancement

When doing split windows in a tab, there's no header per window, rather the last command given is used int he TAB header. See attached example
![WindowsTerminal](https://user-images.githubusercontent.com/61461157/75248606-c18abe00-57d4-11ea-96f1-9c19bdccbd85.png)
Can you provide per split window a header with the command?

This is when using alt-shift-+ to open e.g. multiple Command prompts to perform pings.
<!-- 
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).
-->

# Proposed technical implementation details (optional)
Add a header to split windows with the command given


<!-- 
A clear and concise description of what you want to happen.
-->
Repository: vscode
Issue: Define a `vscode.executeSemanticHighlightProvider` command
Labels: feature-request,semantic-tokens

Providers also define a command so that extensions can use them. See
https://code.visualstudio.com/api/references/commands
for examples.

The semantic highlight provider should offer something similar.

Uses cases:
- get semantic highlighting for a virtual document
Repository: opencv
Issue: [Proposal] imread and imdecode RGB data
Labels: category: imgcodecs,RFC

- OpenCV => 4.2
- Operating System / Platform => Any
- Compiler => Any

##### Detailed description

For main DNN frameworks it need to read RGB (not BGR!) data from jpeg files. But now OpenCV can decode images only in BGR colour space. So cv::imread:
1. [auto in imgcodecs] Decode from jpeg to YUVxxx
2. [auto in imgcodecs] Convert from YUVxxx to RGB and memory allocation
3. [auto in imgcodecs] Convert from RGB to BGR and memory allocation (JpegDecoder::readData):
```
if( cinfo->out_color_components == 3 )
                        icvCvt_RGB2BGR_8u_C3R( buffer[0], 0, data, 0, Size(m_width,1) );
```
4. [manual in user code] Convert from RGB to BGR and memory allocation:
`cv::cvtColor(imgBGR, imgRGB, cv::COLOR_BGR2RGB);`
5. [automatic in DNN framework] split RGB to [3 x W x H]

But for cv::imread we can use cv::IMREAD_UNCHANGED option. I advice to use this option in JpegDecoder::readData to reduce memory allocations and color conversions:
1. with cv::IMREAD_COLOR function returns BGR image;
2. with cv::IMREAD_UNCHANGED function returns RGB image for 3 channels (memcpy( data, buffer[0], step );).

Now for fastest jpeg decoding cv::imread is the worst choise.
Repository: ant-design
Issue: Virtual list example in documentation has broken layout
Labels: help wanted,Inactive,rtl

- [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
[https://next.ant.design/components/table/#components-table-demo-virtual-list](https://next.ant.design/components/table/#components-table-demo-virtual-list)

### Steps to reproduce
Select "RTL" at the top of the screen. Try scrolling the virtual list horizontally.

### What is expected?
Headers are aligned with cells

### What is actually happening?
Headers are not aligned with cells

| Environment | Info |
|---|---|
| antd | 4.0.0-rc.6 |
| React | Any |
| System | Windows 10 |
| Browser | Chrome 79 |


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: create-react-app
Issue: Update workbox-webpack-plugin to strip deprecated core-js@2.6.11
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

Update `workbox-webpack-plugin` to strip deprecated `core-js@2.6.11`.

### Describe the solution you'd like

```bash
└─┬ react-scripts@3.4.0
  └─┬ workbox-webpack-plugin@4.3.1
    └─┬ workbox-build@4.3.1
      └─┬ strip-comments@1.0.2
        └─┬ babel-plugin-transform-object-rest-spread@6.26.0
          └─┬ babel-runtime@6.26.0
            └── core-js@2.6.11
```

https://www.npmjs.com/package/workbox-webpack-plugin
Repository: vscode
Issue: Task instanceLimit doesn't work when depending on long running tasks
Labels: bug,tasks

Re #91154

```
		{
			"label": "Run Mock",
			"type": "shell",
			"command": "./scripts/test.sh",
			"windows": {
				"command": ".\\scripts\\test.bat"
			},
			"group": "test",
			"presentation": {
				"echo": true,
				"reveal": "always"
			},
			"dependsOn": [
				"Run tests"
			],
			"runOptions": {
				"instanceLimit": 3
			}
		},
		{
			"label": "Run tests",
			"type": "shell",
			"command": "./scripts/test.sh",
			"windows": {
				"command": ".\\scripts\\test.bat"
			},
			"group": "test",
			"presentation": {
				"echo": true,
				"reveal": "always"
			}
		},
```

Run `Run Mock` 6 times, there is only one terminal open which runs `Run tests` and no hinting at all about how many `Run Mock` tasks are initialized. Once `Run tests` finishes, 6 `Run Mock` tasks are created, which ignores the instance limit.
Repository: rust
Issue: False warning: "unused logical operation that must be used"
Labels: A-lints,T-compiler,C-bug

In a loop, in some cases, rustc seems to not understand that a boolean expression was used for sideeffects, and warns about unused logical operation.  The following code can quickly replicate the problem.

```rust
use std::sync::{atomic::{AtomicBool, Ordering}, Arc};


fn main() {
    let running = Arc::new(AtomicBool::from(true));
    
    {
        let running = Arc::clone(&running);
        std::thread::spawn(move || {
            running.swap(false, Ordering::Relaxed);
        });
    }
    
    loop {
        // ...
        println!("Running....");
        
        !running.load(Ordering::Relaxed) && break;
    }
    
    println!("Exhausted >.>");
}

```

The expected result is that rustc doesn't output a warning in this case.

### Meta

* rustc version: 1.41.0
Repository: flutter
Issue: `flutter test` fails to clean up if the process is interrupted
Labels: a: tests,team,tool,a: quality,P2,c: flake,team-tool,triaged-tool

The easiest way to reproduce this is to run `flutter test --start-paused path\to\test.dart`, wait for it to generate its temp files, and hit ctrl+C

This leaks files into the temp directory, which can get pretty full.

Related to #51421
Repository: go
Issue: x/tools/gopls: go/parser work-arounds
Labels: Thinking,gopls,Tools

This issue tracks all of the workarounds implemented in `gopls` to handle places where go/parser loses information. Most of this code can be found in [`golang.org/x/tools/internal/lsp/cache/parse.go`](https://github.com/golang/tools/blob/fefc8d187781328d218f957bacb7632909acab8f/internal/lsp/cache/parse.go#L220) and was written by @muirdm.

The current list of workarounds includes handling:

- Missing curly braces in `if` statements (`if foo` -> `if foo {}`)
- Missing selectors (`x.` -> `x._`)
- Partial identifiers that are keywords (`foo.var` -> `foo._`)
- Missing conditional statements in `if` statements with initialization statements (`if i := 0`)
- Unexpected array types (`[]int` -> `[]int{}`)
- Incomplete `go` or `defer` statements (`go foo` -> `go foo()`).
- Dangling selectors in `go` or `defer` statements

```go
go foo.
y := 1
```

becomes 

```go
go foo._
y := 1
```
Repository: go
Issue: x/build: add slowbots heuristics
Labels: help wanted,Builders,NeedsInvestigation,FeatureRequest

Slowbots are awesome, but manual, and thus error-prone.

We could add some heuristics to automatically trigger appropriate slowbots. For example, any change that touches cmd/compile/internal/ssa/rewrite_ARCH.go should trigger slowbots for that arch (or set of arches). Similarly for any file named whatever_ARCH.s. Probably something similar for files named whatever_OS.go.

We could start small and improve heuristics over time. There'd be a few false positives, but probably few enough that it'd be worth it.

cc @bcmills @dmitshur
Repository: terminal
Issue: COOKED_READ with prompt the width of the buffer places the cursor inside prompt, mangles prompt
Labels: Product-Conhost,Area-Input,Issue-Bug,Priority-3

Migrated from MSFT:25341382.

Original description:
> If the command prompt is as long as the terminal window is wide, then hitting Escape clips off the > character at the end of the prompt.

/cc @bviglietta
Repository: flutter
Issue: [google_maps_flutter] API for setting GMSServices.provideAPIKey
Labels: platform-ios,p: maps,package,c: proposal,team-ecosystem,P3,triaged-ecosystem

Can we get an API for setting `GMSServices.provideAPIKey` so that we can avoid baking hard-coded values in `AppDelegate` (as described [here](https://pub.dev/packages/google_maps_flutter#ios))?

## Use case

Avoid hard-coding sensitive API keys in `AppDelegate` (as described [here](https://pub.dev/packages/google_maps_flutter#ios)).

## Proposal

If there was an API exposed to Dart, one could get the API key from the database after authentication or _Firebase Remote Config_, and then pass it to _Google Maps_ before instantiating a widget.

_Will this approach work for [Android](https://pub.dev/packages/google_maps_flutter#android) too?_  (Obviously, a uniform solution is ideal.)
Repository: opencv
Issue: Pre-built iOS frameworks have bad structure
Labels: category: build/install,platform: ios/osx

##### System information (version)
- OpenCV => 4.1.1 or higher
- Operating System / Platform => macOS 10.15.3
- Compiler => Xcode 11.3.1 (11C504)

##### Detailed description

The pre-built frameworks seem to all lack a proper Info.plist at the top level of the framework bundle, and the overall structure is incorrect in some way that Xcode 11 refuses. The Info.plist file in the Resources folder seems to be incomplete. It looks like this:

```
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>CFBundleName</key>
    <string>OpenCV</string>
    <key>CFBundleIdentifier</key>
    <string>org.opencv</string>
    <key>CFBundleVersion</key>
    <string>4.2.0</string>
    <key>CFBundleShortVersionString</key>
    <string>4.2.0</string>
    <key>CFBundleSignature</key>
    <string>????</string>
    <key>CFBundlePackageType</key>
    <string>FMWK</string>
</dict>
</plist>
```

But a proper Info.plist should look more like this:

```
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>BuildMachineOSBuild</key>
	<string>18G103</string>
	<key>CFBundleDevelopmentRegion</key>
	<string>en</string>
	<key>CFBundleExecutable</key>
	<string>FileKit</string>
	<key>CFBundleIdentifier</key>
	<string>com.nikolaivazquez.FileKit</string>
	<key>CFBundleInfoDictionaryVersion</key>
	<string>6.0</string>
	<key>CFBundleName</key>
	<string>FileKit</string>
	<key>CFBundlePackageType</key>
	<string>FMWK</string>
	<key>CFBundleShortVersionString</key>
	<string>4.0.1</string>
	<key>CFBundleSignature</key>
	<string>????</string>
	<key>CFBundleSupportedPlatforms</key>
	<array>
		<string>iPhoneOS</string>
	</array>
	<key>CFBundleVersion</key>
	<string>12</string>
	<key>DTCompiler</key>
	<string>com.apple.compilers.llvm.clang.1_0</string>
	<key>DTPlatformBuild</key>
	<string>17B102</string>
	<key>DTPlatformName</key>
	<string>iphoneos</string>
	<key>DTPlatformVersion</key>
	<string>13.2</string>
	<key>DTSDKBuild</key>
	<string>17B102</string>
	<key>DTSDKName</key>
	<string>iphoneos13.2</string>
	<key>DTXcode</key>
	<string>1120</string>
	<key>DTXcodeBuild</key>
	<string>11B53</string>
	<key>MinimumOSVersion</key>
	<string>8.0</string>
	<key>UIDeviceFamily</key>
	<array>
		<integer>1</integer>
		<integer>2</integer>
	</array>
</dict>
</plist>
```

It ends up being much simpler to structure the framework like this:

```
$ tree opencv2.framework
├── Headers
├── Info.plist
└── opencv2
```

Doing all of the above allows Xcode to sign the framework without the discouraged `--deep`, and it allows the iOS loader to succeed.

##### Steps to reproduce

n/a
Repository: pytorch
Issue: [JIT] BroadcastingList annotations don't work with ignore'd functions
Labels: oncall: jit,triaged

## 🐛 Bug

```
        @torch.jit.ignore
        def foo(x):
            # type: (BroadcastingList1[float]) -> List[float]
            return x

        @torch.jit.script
        def hi():
            return foo(1.)
```


cc @suo
Repository: TypeScript
Issue: Add a modifier for "closed" blocks and functions
Labels: Suggestion,Awaiting More Feedback

## Search Terms

puppeteer, worker, webpack

## Suggestion

Add a `closed` clause to create blocks/functions that cannot capture any value outside the scope of the block. Any dependencies must be imported explicitly within the block. These dependencies can be inlined to form a self-contained block (using an extra `inline` keyword in the `closed` statement or through a boolean field in the compiler options). The resulting inline block can be optimized and unused code can be removed.

## Use Cases

### Serialize functions

Tools like [puppeteer](https://github.com/puppeteer/puppeteer) provide functions to perform a callback in the browser context. These callbacks are serialized. This can cause problems with functions in TypeScript, since the language uses `tslib` and errors like `awaiter is not defined` can occur. Also, the compiler will not report an error when any value is captured within the callback, but these values will not be available within the browser context.

### Workers in webpack

There are some problems when using workers with webpack. The emitted code for the `import|require` statements contains functions that will not be available in the worker scope. With a `closed inline block`, these problems are resolved without needs to use any extra plugin or loader.

## Examples

```typescript
const path = require('path')

closed {
  const pathSeparator = path.sep // Compiler error - `path` is not defined

  import('path').then(module => { // The right way
    // ...
  })
}

closed inline {
  const pathSeparator = path.sep // Compiler error - `path` is not defined

  import('path').then(module => { // The right way
    // The path module will be inlined within the `closed inline` block
  })
}

closed function foo() {
  const pathSeparator = path.sep // Compiler error - `path` is not defined

  import('path').then(module => { // The right way
    // ...
  })
}

closed inline foo() {
  const pathSeparator = path.sep // Compiler error - `path` is not defined

  import('path').then(module => { // The right way
    // The path module will be inlined within the `closed inline` function
  })
}

```
Repository: pytorch
Issue: MSE Loss Implementation
Labels: triaged

During the implementation of ONNX export of mse loss function I encountered a problem with broadcastable tensors (not supported in ONNX), and I have a couple of questions about certain implementation details of mse loss in Pytorch.

1. Documentation of MSELoss states that input and target tensors should be of the same shape:
https://pytorch.org/docs/stable/nn.html#mseloss, so I don't understand why are broadcastable tensors used in mse_loss function: https://github.com/pytorch/pytorch/blob/a9cef05f5d6ca2a74f993feb191531a03e445d40/torch/nn/functional.py#L2523

2. When required_grad is set to True for target tensor, tensors don't need to be broadcastable: https://github.com/pytorch/pytorch/blob/a9cef05f5d6ca2a74f993feb191531a03e445d40/torch/nn/functional.py#L2518. Why is the condition of requires grad only applied for target and not for input as well?

@houseroad


cc @houseroad @spandantiwari @lara-hdr @BowenBao @neginraoof